[go: up one dir, main page]

WO2022197223A1 - Attribution semi-persistante à ue multiples - Google Patents

Attribution semi-persistante à ue multiples Download PDF

Info

Publication number
WO2022197223A1
WO2022197223A1 PCT/SE2021/050238 SE2021050238W WO2022197223A1 WO 2022197223 A1 WO2022197223 A1 WO 2022197223A1 SE 2021050238 W SE2021050238 W SE 2021050238W WO 2022197223 A1 WO2022197223 A1 WO 2022197223A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
resource allocation
ues
activation
ran
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/SE2021/050238
Other languages
English (en)
Inventor
Bikramjit Singh
Massimo CONDOLUCI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/SE2021/050238 priority Critical patent/WO2022197223A1/fr
Publication of WO2022197223A1 publication Critical patent/WO2022197223A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present invention generally relates to wireless communication networks, and more specifically to techniques for reducing communication latency or delay for applications whose data transmission and/or reception patterns are irregular and/or non-periodic.
  • NR New Radio
  • 3GPP Third-Generation Partnership Project
  • eMBB enhanced mobile broadband
  • MTC machine type communications
  • URLLC ultra-reliable low latency communications
  • D2D side-link device-to-device
  • Rel-15 3GPP Release 15
  • NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the downlink (DL) from network to user equipment (UE), and both CP-OFDM and DFT-spread OFDM (DFT-S-OFDM) in the uplink (UL) from LIE to network.
  • CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing
  • DFT-S-OFDM DFT-spread OFDM
  • NR DL and UL time-domain physical resources are organized into equal-sized 1-ms subframes. A subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols.
  • time-frequency resources can be configured much more flexibly for an NR cell than for an LTE cell.
  • SCS 15-kHz OFDM sub-carrier spacing
  • NR SCS can range from 15 to 240 kHz, with even greater SCS considered for future NR releases.
  • NR networks In addition to providing coverage via cells as in LTE, NR networks also provide coverage via “beams.”
  • a downlink (DL, i.e., network to UE) “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured or monitored by a UE.
  • RS can include any of the following: synchronization signal/PBCH block (SSB), channel state information RS (CSI-RS), tertiary reference signals (or any other sync signal), positioning RS (PRS), demodulation RS (DMRS), phase-tracking reference signals (PTRS), etc.
  • SSB is available to all UEs regardless of the state of their connection with the network, while other RS (e.g CSI-RS, DM-RS, PTRS) are associated with specific UEs that have a network connection.
  • Figure 1 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks between a UE, a gNodeB (gNB, e.g., base station), and an access and mobility management function (AMF) in the 5G core network (5GC).
  • UP user plane
  • CP control plane
  • AMF access and mobility management function
  • Physical (PHY) Physical
  • MAC Medium Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • the PDCP layer provides ciphering/deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for CP and UP.
  • PDCP provides header compression and retransmission for UP data.
  • IP Internet protocol
  • SDUs service data units
  • PDUs protocol data units
  • SDAP Service Data Adaptation Protocol
  • QoS quality-of-service
  • DRBs Data Radio Bearers
  • QFI QoS flow identifiers
  • PDCP When each IP packet arrives, PDCP starts a discard timer. When this timer expires, PDCP discards the associated SDU and the corresponding PDU. If the PDU was delivered to RLC, PDCP also indicates the discard to RLC.
  • the RLC layer transfers PDCP PDUs to the MAC through logical channels (LCH).
  • LCH logical channels
  • RLC provides error detection/correction, concatenation, segmentation/reassembly, sequence numbering, reordering of data transferred to/from the upper layers. If RLC receives a discard indication from associated with a PDCP PDU, it will discard the corresponding RLC SDU (or any segment thereof) if it has not been sent to lower layers.
  • the MAC layer provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (on gNB side).
  • the PHY layer provides transport channel services to the MAC layer and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming.
  • the non-access stratum (NAS) layer is between UE and AMF and handles UE/gNB authentication, mobility management, and security control.
  • the RRC layer sits below NAS in the UE but terminates in the gNB rather than the AMF.
  • RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN.
  • RRC also broadcasts system information (SI) and establishes, configures, maintains, and releases DRBs and Signaling Radio Bearers (SRBs) used by UEs.
  • SI system information
  • SRBs Signaling Radio Bearers
  • RRC controls addition, modification, and release of carrier aggregation (CA) and dual -connectivity (DC) configurations for UEs.
  • CA carrier aggregation
  • DC dual -connectivity
  • RRC also performs various security functions such as key management.
  • a UE After a UE is powered ON it will be in the RRC IDLE state until an RRC connection is established with the netwOrk, at wiiich time the UE will transition to RRC_CONNECTED state (e.g., where data transfer can occur). The UE returns to RRC IDLE after the connection with the network is released.
  • RRC IDLE state the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers.
  • DRX discontinuous reception
  • an RRC IDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on physical DL control channel (PDCCH) for pages from 5GC via gNB.
  • PDCCH physical DL control channel
  • a UE in RRC IDLE state is not known to the gNB serving the cell where the UE is camping.
  • NR RRC includes an RRC INACTIVE state in which a UE is known (e.g., via context) by the serving gNB.
  • UL and DL data transmissions take place on physical UL shared channel (PUSCH) and physical DL shared channel (PDSCH), respectively. These data transmissions can take place with or without an explicit grant or assignment of resources by the network (e.g., gNB).
  • UL transmissions are usually referred to as being “granted” by the network (i.e., “UL grant”), while DL transmissions are usually referred to as being “assigned” by the network (i.e., “DL assignment”).
  • the gNB sends DL control information (DCI) to a UE informing it of specific resources to be used for the transmission.
  • DCI DL control information
  • the gNB scheduler issues the grant/assignment based on knowledge of DL data in the gNB buffer or UL data in the UE buffer, which the UE reports via buffer status report (BSR) and/or a one-bit scheduling request (SR).
  • BSR buffer status report
  • SR one-bit scheduling request
  • a transmission without an explicit grant/assignment is typically configured to occur with a defined periodicity.
  • the UE Given a periodic and/or recurring UL grant and/or DL assignment, the UE can then initiate a data transmission and/or receive data according to a predefined configuration.
  • Such transmissions can be referred to as semi-persistent scheduling (SPS, for DL), configured grant (CG, for UL), or grant-free transmissions.
  • Type-1 are configured via RRC signaling only, while for Type-2, some parameters are preconfigured via RRC signaling and some PHY parameters are dynamically indicated.
  • the RRC configuration of a UL configured grant includes various parameters, including a configuredGrantTimer value used for controlling operation of hybrid ARQ (HARQ) processes in the UL via a timer in the UE.
  • a related feature is Autonomous Uplink (AUL), which is intended to support autonomous HARQ retransmissions (i.e., of the same transport block, TB) using an UL configured grant.
  • AUL Autonomous Uplink
  • B5G -5G
  • 6G 6G timelines
  • new services and/or use cases will require both low latency (e.g., lower than in 5G) and high data rates (e.g., much higher than 5G).
  • Another expectation is that these services with strict requirements will have various traffic patterns, including periodic/regular and non-periodic/irregular.
  • An example low-latency B5G/6G use case is distributed artificial intelligence (AI) involving a group of (e.g., many) UEs that have inter-related, non-periodic data traffic patterns.
  • AI distributed artificial intelligence
  • Currently available techniques for dynamic and grant-free resource allocation are inadequate for such use cases with non-periodic traffic patterns and requirements for low latency.
  • Embodiments of the present disclosure provide specific improvements to low-latency, non-periodic communication between user equipment (UEs) and a wireless network (e.g., radio access network, RAN), such as by providing, enabling, and/or facilitating solutions to overcome exemplary problems summarized above and described in more detail below.
  • UEs user equipment
  • RAN radio access network
  • Embodiments include methods (e.g., procedures) for a user equipment (UE) operating in a radio access network (RAN) as one of a group of EIEs.
  • UE user equipment
  • RAN radio access network
  • These exemplary methods can include receiving a group resource allocation for the group of EIEs to transmit or receive data in the RAN.
  • the group resource allocation can include resources during a plurality of occasions.
  • These exemplary methods can also include receiving one or more activation indications of whether the group resource allocation is activated or deactivated for use by at least the TIE. Each particular activation indication is associated with all occasions subsequent to the particular activation indication.
  • receiving the one or more activation indications can include, for each particular activation indication: attempting to decode a message containing the particular activation indication; and sending, to the RAN, feedback indicating whether decoding the message was successful.
  • the one or more activation indications can include any of the following:
  • the one or more activation indications can include a first sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a first sub-group that includes the UE; and a subsequent second sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a second sub-group that includes the UE but differs from the first sub-group by at least one UE.
  • the one or more activation indications can include a first group activation indication, indicating that the group resource allocation is activated for use by all UEs of the group; and a subsequent second activation indication, which is one of the following:
  • the one or more activation indications can include UE-specific activation indication, indicating that the group resource allocation is activated for use by the UE; and a subsequent second activation indication, which is one of the following:
  • the group resource allocation can include a plurality of resource allocations associated with a respective plurality of identifiers.
  • Each particular activation indication can include an identifier of the resource allocation to which the particular activation indication applies.
  • the group resource allocation can include a transmission or reception configuration to be used by the group of UEs during the occasions.
  • these exemplary methods can also include receiving, after one of the occasions, a message including an updated transmission or reception configuration to be used by the group of UEs during occasions subsequent to the message.
  • these exemplary methods can also include receiving a message that schedules transmission or reception of data with the RAN.
  • the message includes a UE- specific resource allocation which implicitly indicates that the group resource allocation is deactivated for use by the UE during subsequent occasions.
  • these exemplary methods can also include, during each particular occasion, selectively transmitting or receiving data based on a most recently received activation indication associated with the particular occasion.
  • the group resource allocation can be for transmitting uplink (UL) data to the RAN.
  • selectively transmitting or receiving data can include refraining from transmitting UL data during an occasion when the group resource is activated for use by the UE based on one or more of the following:
  • these exemplary methods can also include receiving one or more allowance indications of whether the UE is allowed to transmit or receive during the occasions. Each particular allowance indication is associated with a consecutive subset of the occasions subsequent to the particular allowance indication.
  • each particular allowance indication includes a bitmap of a plurality of bits that indicate whether the UE is allowed to transmit or receive in a corresponding plurality of the occasions of the associated subset.
  • RAN radio access network
  • These exemplary methods can include transmitting, to a group of UEs, a group resource allocation for the group of UEs to transmit or receive data in the RAN.
  • the group resource allocation can include resources during a plurality of occasions.
  • These exemplary methods can also include transmitting one or more activation indications of whether the group resource allocation is activated or deactivated for use by at least one of the UEs. Each particular activation indication is associated with all occasions subsequent to the particular activation indication:
  • transmitting the one or more activation indications can include, in response to each particular activation indication, receiving feedback indicating whether a particular one of the UEs was successful in decoding a message including the particular activation indication.
  • these exemplary methods can also include selecting the UEs included in the group based on one or more of the following criteria:
  • RAN node • within a common coverage area of the RAN node (e.g., cell, cell sector, beam);
  • these exemplary methods can also include predicting traffic patterns for the one or more UEs based on one or more of the following:
  • SR scheduling requests
  • BSR buffer status reports
  • the group resource allocation for the one or more UEs can be based on the predicted traffic patterns.
  • the activation indications include first activation indications that are based on the respective predicted UE traffic patterns, and second activation indications that are transmitted after the first indications and are based on respective actual UE traffic patterns during occasions after transmitting the first activation indications.
  • the one or more activation indications can include any of the following:
  • the one or more activation indications can include a first sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a first sub-group that includes the particular UE; and a subsequent second sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a second sub-group that includes the particular UE but differs from the first sub-group by at least one UE.
  • the one or more activation indications can include a first group activation indication, indicating that the group resource allocation is activated for use by all UEs of the group; and a subsequent second activation indication, which is one of the following:
  • a sub-group activation indication indicating that the group resource allocation is deactivated for use by a sub-group that includes the particular UE
  • the one or more activation indications can include UE-specific activation indication, indicating that the group resource allocation is activated for use by the particular UE; and a subsequent second activation indication, which is one of the following:
  • the group resource allocation can include a plurality of resource allocations associated with a respective plurality of identifiers.
  • Each particular activation indication can include an identifier of the resource allocation to which the particular activation indication applies.
  • the group resource allocation can include a transmission or reception configuration to be used by the group of UEs during the occasions.
  • these exemplary methods can also include transmitting, after one of the occasions, a message including an updated transmission or reception configuration to be used by the group of UEs during occasions subsequent to the message.
  • these exemplary methods can also include transmitting a message that schedules transmission or reception of data by a particular UE (i.e., of the group) with the RAN.
  • the message includes a UE-specific resource allocation that implicitly indicates that the group resource allocation is deactivated for use by the particular UE during subsequent occasions.
  • these exemplary methods can also include, during each particular occasion, selectively receiving or transmitting data with one of the UEs of the group based on a most recently transmitted activation indication associated with the particular occasion.
  • the group resource allocation can be for receiving downlink (DL) data from the RAN.
  • selectively receiving or transmitting data can include refraining from transmitting a message scheduling DL data for a particular UE during an occasion when the group resource is activated for use by the particular UE, based on one or more of the following conditions related to the particular UE:
  • these exemplary methods can also include transmitting one or more allowance indications of whether the respective UEs are allowed to transmit or receive during the occasions.
  • Each particular allowance indication is associated with a consecutive subset of the occasions subsequent to the particular allowance indication.
  • selectively receiving or transmitting during each particular occasion is further based on a most recently received allowance indication associated with the particular occasion.
  • each allowance indication includes a bitmap of a plurality of bits that indicate whether a particular UE is allowed to transmit or receive in a corresponding plurality of the occasions of the associated subset.
  • UEs e.g., wireless devices
  • RAN nodes e.g ., base stations, eNBs, gNBs, ng-eNBs, etc. , or components thereof
  • Other embodiments include non-transitory, computer-readable media storing program instructions that, when executed by processing circuitry, configure such UEs or RAN nodes to perform operations corresponding to any of the exemplary methods described herein.
  • Figure 1 shows an exemplary NR user plane (UP) and control plane (CP) protocol stacks.
  • UP user plane
  • CP control plane
  • Figure 2 illustrates a high-level views of an exemplary 5G/NR network architecture.
  • Figure 3 shows an exemplary frequency-domain configuration for an NR user equipment
  • Figure 4 shows an exemplary time-frequency resource grid for an NR slot.
  • Figure 5 shows an exemplary mini-slot arrangement for NR.
  • Figure 6 shows an exemplary arrangement of control and data channels within an NR slot.
  • Figure 7 which includes Figures 7A-B, shows an exemplary ASN.l data structure for a ConfiguredGrantConfig information element (IE).
  • IE ConfiguredGrantConfig information element
  • Figure 8 shows an exemplary procedure for limiting autonomous uplink (AUL) transmissions for a hybrid ARQ (HARQ) process.
  • AUL autonomous uplink
  • HARQ hybrid ARQ
  • Figures 9-12 show various communications between a RAN node and a group of UEs (UE1, UE2, and UE3) that illustrate various embodiments of the present disclosure.
  • Figure 13 shows a flow diagram of an exemplary method for a UE (e.g, wireless device), according to various exemplary embodiments of the present disclosure.
  • a UE e.g, wireless device
  • Figure 14 shows a flow diagram of an exemplary method for a RAN node (e.g, base station, eNB, gNB, ng-eNB, etc.), according to various exemplary embodiments of the present disclosure.
  • a RAN node e.g, base station, eNB, gNB, ng-eNB, etc.
  • Figure 15 shows a block diagram of an exemplary UE (e.g., wireless device), according to various exemplary embodiments of the present disclosure.
  • Figure 16 shows a block diagram of an exemplary network node (e.g ., base station, eNB, gNB, ng-eNB, etc.), according to various exemplary embodiments of the present disclosure.
  • a network node e.g ., base station, eNB, gNB, ng-eNB, etc.
  • FIG 17 shows a block diagram of an exemplary network configured to provide over- the-top (OTT) data services between a host computer and a UE, according to various exemplary embodiments of the present disclosure.
  • OTT over-the-top
  • Radio Node can be either a radio access node or a wireless device.”
  • Node can be a network node or a wireless device.
  • Radio Access Node As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals.
  • RAN radio access network
  • a radio access node examples include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LTE network), base station distributed components (e.g, CU and DEI), a high-power or macro base station, a low-power base station (e.g ., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point, a remote radio unit (RRU or RRH), and a relay node.
  • a base station e.g., a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LTE network
  • base station distributed components e.g, CU and DEI
  • a “core network node” is any type of node in a core network.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a Packet Data Network Gateway (P-GW), an access and mobility management function (AMF), a session management function (AMF), a user plane function (UPF), a Service Capability Exposure Function (SCEF), or the like.
  • MME Mobility Management Entity
  • SGW serving gateway
  • P-GW Packet Data Network Gateway
  • AMF access and mobility management function
  • AMF access and mobility management function
  • AMF AMF
  • UPF user plane function
  • SCEF Service Capability Exposure Function
  • Wireless Device As used herein, a “wireless device” (or “WD” for short) is any type of device that has access to (i.e., is served by) a cellular communications network by communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • wireless device examples include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Internet-of-Things (IoT) devices, vehicle-mounted wireless terminal devices, etc.
  • the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short).
  • Network Node is any node that is either part of the radio access network (e.g, a radio access node or equivalent name discussed above) or of the core network (e.g, a core network node discussed above) of a cellular communications network.
  • a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g, administration) in the cellular communications network.
  • UP latency control plays a crucial role in meeting end-to-end (E2E) latency requirements for services in current and future wireless networks.
  • E2E end-to-end
  • the network scheduler e.g., in a base station
  • the scheduler practically dictates UP latency, and can be operated in various modes to meet different latency requirements.
  • FIG. 2 shows a high-level view of an exemplary 5G network architecture, including a Next Generation Radio Access Network (NG-RAN) 299 and a 5G Core (5GC) 298.
  • NG-RAN 299 can include gNBs 210 (e.g., 210a, b) and ng-eNBs 220 (e.g, 220a, b) that are interconnected with each other via respective Xn interfaces.
  • gNBs 210 e.g., 210a, b
  • ng-eNBs 220 e.g, 220a, b
  • the gNBs and ng-eNBs are also connected via the NG interfaces to 5GC 298, more specifically to the AMF (Access and Mobility Management Function) 230 (e.g, AMFs 230a, b) via respective NG-C interfaces and to the UPF (User Plane Function) 240 (e.g, UPFs 240a, b) via respective NG-U interfaces.
  • the AMFs 230a, b can communicate with one or more policy control functions (PCFs, e.g., PCFs 250a, b) and network exposure functions (NEFs, e.g., NEFs 260a, b).
  • PCFs policy control functions
  • NEFs network exposure functions
  • Each of the gNBs 210 can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • each of ng-eNBs 220 can support the LTE radio interface but, unlike conventional LTE eNodeBs (eNBs), connect to the 5GC via the NG interface.
  • Each of the gNBs and ng-eNBs can serve a geographic coverage area including one more cells, including cells 211a-b and 221a-b shown as exemplary in Figure 2.
  • the gNBs and ng-eNBs can also use various directional beams to provide coverage in the respective cells.
  • a UE 205 can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively.
  • the gNBs shown in Figure 2 can include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU), which can be viewed as logical nodes.
  • CUs host higher-layer protocols and perform various gNB functions such controlling the operation of DUs, which host lower-layer protocols and can include various subsets of the gNB functions.
  • each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, communication interface circuitry (e.g ., for communication via Xn, NG, radio, etc. interfaces), and power supply circuitry.
  • the terms “central unit” and “centralized unit” can be used interchangeably, as can the terms “distributed unit” and “decentralized unit.”
  • a CU connects to its associated DUs over respective FI logical interfaces.
  • a CU and associated DUs are only visible to other gNBs and the 5GC as a gNB, e.g., the FI interface is not visible beyond a CU.
  • a CU can host higher-layer protocols such as FI application part protocol (Fl-AP), Stream Control Transmission Protocol (SCTP), GPRS Tunneling Protocol (GTP), Packet Data Convergence Protocol (PDCP), User Datagram Protocol (UDP), Internet Protocol (IP), and Radio Resource Control (RRC) protocol.
  • a DU can host lower-layer protocols such as Radio Link Control (RLC), Medium Access Control (MAC), and physical-layer (PHY) protocols.
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY physical-layer
  • protocol distributions between CU and DU can exist, however, such as hosting the RRC, PDCP and part of the RLC protocol in the CU (e.g, Automatic Retransmission Request (ARQ) function), while hosting the remaining parts of the RLC protocol in the DU, together with MAC and PHY.
  • the CU can host RRC and PDCP, where PDCP is assumed to handle both UP traffic and CP traffic.
  • other exemplary embodiments may utilize other protocol splits that by hosting certain protocols in the CU and certain others in the DU.
  • NR DL and UL physical resources are organized into equal-sized 1-ms subframes.
  • a subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols.
  • An NR slot can include 14 OFDM symbols for normal cyclic prefix and 12 symbols for extended cyclic prefix.
  • a resource block (RB) consists of a group of 12 contiguous OFDM subcarriers for a duration of a 12- or 14-symbol slot.
  • a resource element (RE) corresponds to one OFDM subcarrier during one OFDM symbol interval.
  • FIG. 3 shows an exemplary frequency-domain configuration for an NR UE.
  • a UE can be configured with up to four carrier bandwidth parts (BWPs) in a DL carrier bandwidth with a single DL BWP being active at a given time.
  • BWPs carrier bandwidth parts
  • a UE can be configured with up to four BWPs in an UL carrier bandwidth with a single UL BWP being active at a given time.
  • the UE can be configured with up to four additional BWPs in the supplementary UL carrier bandwidth, with a single supplementary UL BWP being active at a given time.
  • Common RBs (CRBs) are numbered from 0 to the end of the carrier bandwidth.
  • Each BWP configured for a UE has a common reference of CRBO, such that a configured BWP may start at a CRB greater than zero.
  • CRBO can be identified by one of the following parameters provided by the network, as further defined in 3GPP TS 38.211 section 4.4:
  • PCell e.g., PCell or PSCell
  • a UE can be configured with a narrow BWP (e.g., 10 MHz) and a wide BWP (e.g, 100 MHz), each starting at a particular CRB, but only one BWP can be active for the UE at a given point in time.
  • BWP includes PRBs 0 to Nl
  • BWP1 includes PRBs 0 to N2
  • BWP2 includes PRBs 0 to N3.
  • Figure 4 shows an exemplary time-frequency resource grid for an NR slot within a carrier bandwidth.
  • a resource block (RB) consists of a group of 12 contiguous OFDM subcarriers for a duration of a 14-symbol slot.
  • a resource element (RE) consists of one subcarrier in one slot.
  • An NR slot can include 14 OFDM symbols for normal cyclic prefix ( e.g ., as shown in Figure 4) and 12 symbols for extended cyclic prefix.
  • NR includes Type-B scheduling, also known as “mini-slots.” These are shorter than slots, typically ranging from one symbol up to one less than the number of symbols in a slot (e.g., 13 or 11), and can start at any symbol of a slot. Mini-slots can be used if the transmission duration of a slot is too long and/or the occurrence of the next slot start (slot alignment) is too late.
  • Figure 5 shows an exemplary mini-slot arrangement in which the mini-slot begins in the third symbol of the slot and is two symbols in duration. Mini-slots can be used for unlicensed spectrum and latency -critical transmissions (e.g, URLLC). However, mini-slots are not service-specific and can also be used for eMBB or other services.
  • An NR slot can also be arranged with various time-division duplexing (TDD) arrangements of UL and DL symbols.
  • TDD time-division duplexing
  • Figure 6 shows another exemplary NR slot structure comprising 14 symbols.
  • PDCCH is confined to a region containing a particular number of symbols and a particular number of subcarriers, referred to as the control resource set (CORESET).
  • CORESET control resource set
  • the first two symbols contain PDCCH and each of the remaining 12 symbols contains physical data channels (PDCH), i.e., either PDSCH or PUSCH.
  • PDCH physical data channels
  • the first two slots can also carry PDSCH or other information, as required.
  • a CORESET includes multiple RBs (i.e., multiples of 12 REs) in the frequency domain and 1-3 OFDM symbols in the time domain.
  • the frequency bandwidth of the CORESET is variable.
  • CORESET resources can be indicated to a UE by RRC signaling.
  • the smallest unit used for defining CORESET is the REG, which spans one PRB in frequency and one OFDM symbol in time.
  • each REG contains demodulation reference signals (DM- RS) to aid in the estimation of the radio channel over which that REG was transmitted.
  • DM- RS demodulation reference signals
  • multiple REGs can be grouped together to form a REG bundle, and the REG bundle size (i.e., 2, 3, or 5 REGs) can be indicated to the UE.
  • the UE can assume that any precoder used for transmission of PDCCH is the same over an entire REG bundle.
  • An NR control channel element (CCE) consists of six REGs. These REGs may either be contiguous or distributed in frequency. When the REGs are distributed in frequency, the CORESET is said to use interleaved mapping of REGs to a CCE, while if the REGs are contiguous in frequency, a non-interleaved mapping is said to be used. Interleaving can provide frequency diversity. Not using interleaving is beneficial for cases where knowledge of the channel allows the use of a precoder in a particular part of the spectrum improve the SINR at the receiver.
  • NR data scheduling can be performed dynamically, e.g., on a per- slot basis.
  • the gNB transmits downlink control information (DCI) over PDCCH that indicates which UE is scheduled to receive data in that slot, as well as which RBs will carry that data.
  • DCI downlink control information
  • a UE first detects and decodes DCI and, if the DCI includes DL scheduling information for the UE, receives the corresponding PDSCH based on the DL scheduling information.
  • DCI formats 1 0 and 1 1 are used to convey PDSCH scheduling.
  • DCI on PDCCH can include UL grants that indicate which UE is scheduled to transmit data on PUCCH in that slot, as well as which RBs will carry that data.
  • a UE first detects and decodes DCI and, if the DCI includes an uplink grant for the UE, transmits the corresponding PUSCH on the resources indicated by the UL grant.
  • DCI formats 0 0 and 0 1 are used to convey UL grants for PUSCH, while Other DCI formats (2 0, 2 1, 2 2 and 2 3) are used for other purposes including transmission of slot format information, reserved resource, transmit power control information, etc.
  • a DCI includes a payload complemented with a Cyclic Redundancy Check (CRC) of the payload data. Since DCI is sent on PDCCH that is received by multiple UEs, an identifier of the targeted UE needs to be included. In NR, this is done by scrambling the CRC with a Radio Network Temporary Identifier (RNTI) assigned to the UE. Most commonly, the cell RNTI (C- RNTI) assigned to the targeted UE by the serving cell is used for this purpose.
  • CRC Cyclic Redundancy Check
  • DCI payload together with an identifier-scrambled CRC is encoded and transmitted on the PDCCH.
  • each UE tries to detect a PDCCH addressed to it according to multiple hypotheses (also referred to as “candidates”) in a process known as “blind decoding.”
  • PDCCH candidates span 1, 2, 4, 8, or 16 CCEs, with the number of CCEs referred to as the aggregation level (AL) of the PDCCH candidate. If more than one CCE is used, the information in the first CCE is repeated in the other CCEs.
  • AL aggregation level
  • PDCCH link adaptation can be performed by adjusting AL.
  • PDCCH candidates can be located at various time-frequency locations in the CORESET.
  • a UE decodes a DCI, it de-scrambles the CRC with RNTI(s) that is(are) assigned to it and/or associated with the particular PDCCH search space. In case of a match, the UE considers the detected DCI as being addressed to it, and follows the instructions (e.g scheduling information) in the DCI.
  • the UE first reads the five-bit modulation and coding scheme field (IMCS) in the DCI (e.g., formats 1 0 or 1 1) to determine the modulation order (Q m ) and target code rate ( R ) based on the procedure defined in 3GPP TS 38.214 (vl5.0.0) clause 5.1.3.1. Subsequently, the UE reads the redundancy version field (rv) in the DCI to determine the redundancy version.
  • IMCS modulation and coding scheme field
  • the UE determines the Transport Block Size (TBS) for the PDSCH according to the procedure defined in 3GPP TS 38.214 (vl5.0.0) clause 5.1.3.2.
  • dynamic scheduling provides a single grant or assignment of resources (i.e., via DCI) to individual devices for an upcoming transmit time interval (TTI, e.g., slot).
  • TTI transmit time interval
  • the grant or assignment tells UEs when and what transport format to use for an upcoming data transmission.
  • the scheduler issues UL resource grants based on knowledge of data stored in UE buffers via buffer status reports (BSRs).
  • BSRs buffer status reports
  • UEs may send BSRs using already-granted UL resources, or may send a one-bit scheduling request (SR) on PUCCH shared resources to request a grant of UL resources for BSR.
  • the gNB may grant UL resources in response to the SR and may grant additional UL resources in response to the BSR.
  • this process requires exchanging four messages and has two possible delays between request and grant.
  • dynamic scheduling is inadequate for services involving small but frequent delay-sensitive data transmissions, such as online game, ping, etc.
  • Prescheduling addresses these inadequacies by sending a (predictive) predefined grant of UL resources to a UE without knowledge of the UE’s actual buffer status. If the size is sufficient, the UE may the granted resources to transmit buffered UL data. Otherwise, the UE can used the granted resources to report buffer status, from which the UE can receive a dynamic UL grant to transmit the buffered UL data. In case the UE has no UL data buffered at the time of predefined grant, it can refrain from using the granted resources.
  • pre-scheduling is a configured grant (also called grant-free transmission).
  • the basic idea is to configure a (predictive) predefined grant to a UE, which may use it when data arrives at the UE’s buffer and no dynamic UL grant is available. Since the UE does not have to request UL resources when data arrives, a configured grant can be suitable for applications requiring low latency.
  • Period refers to how often granted resources are available and data size refers to how much data can be carried by each of the periodically-granted resources.
  • Configuration of these two parameters is usually a tradeoff between latency and resource utilization. Too large data size consumes resources very quickly as the number of UEs increases, but too small data size can cause segmentation of UE data (e.g., over multiple periods) and thus longer latency.
  • configured grants should be conservative, with reasonably small data size targeted to allow BSR or single ping packet transmission.
  • Different types of delay-sensitive services may have a range of traffic behavior, and it is desirable to adapt prescheduled resources according to service type.
  • One approach is dynamic TDD, in which the scheduler dynamically changes transmission direction in slots according to traffic needs.
  • the time duration in between two neighboring UL slots in dynamic TDD can vary from frame to frame. Periodic scheduling via configured grant must take this variation into account when setting grant parameters.
  • NR supports two types of pre-configured UL resources, both of which are similar to LTE semi-persistent scheduling (SPS) with some enhancements such as support for transport block (TB) repetitions.
  • SPS semi-persistent scheduling
  • TB transport block repetitions
  • UL data transmission with configured grant is based only on RRC configuration without any LI signaling.
  • Type 2 is similar to the LTE SPS feature, where some parameters are preconfigured via RRC and some physical layer parameters are configured via MAC scheduling.
  • LI signaling is used for activation/deactivation of a type-2 grant.
  • a gNB explicitly activates the configured resources on PDCCH and the UE confirms reception of the activation/deactivation grant using a MAC control element.
  • Figure 7 shows an exemplary ASN.l data structure for a ConfiguredGrantConfig information element (IE) used for RRC configuration of NR type- 1 and type-2 UL configured grants.
  • the IE shown in Figure 7A includes an srs-Resourcelndicator field that points to one of the UL sounding reference signal (SRS) resources in an SRS resource configuration provided by the network via RRC signaling.
  • the SRS resource can also be configured with a spatial relation to a DL RS (e.g., SSB or CSI-RS) or another UL SRS resource.
  • the UE should transmit PUSCH based on the UL configured grant using the same precoder or beamforming weights as used for the transmission of the SRS identified by the srs- Resourcelndicator field and the SRS resource configuration.
  • UL periodicity is configured via the periodicity field in Figure 7.
  • Table 2 summarizes periodicities (in symbols) supported for various subcarrier spacing (SCS).
  • a periodicityExt parameter was introduced to support finer granularities than periodicity , and is defined in 3GPP TS 38.331 v.16.2.0 as follows:
  • time resources are configured via RRC signalling:
  • the periodicity is configured by RRC in the same way as for Typel, but the slot offset is dynamically indicated by the slot in which the UE receives the DCI that activates the Type2 configured grant.
  • the time domain allocation of PUSCH is indicated dynamically by DCI via the time domain resource assignment field (i.e., slot/length indicator value, SLIV) in the same way as for scheduled (non-CG) PUSCH.
  • a configuredGrantTimer is used to prevent an UL CG from overriding and/or pre empting a TB scheduled with a dynamic grant (i.e., new transmission or retransmission), or an initial TB with another UL CG (i.e., new transmission).
  • a dynamic grant i.e., new transmission or retransmission
  • an initial TB with another UL CG i.e., new transmission.
  • the gNB implicitly indicates an ACK by providing an UL grant for a new transmission.
  • Expiration of the CGT indicates an ACK for a HARQ process associated with the UL CG.
  • the CGT is (re)started for an associated HARQ process upon PUSCH transmission based on a dynamic grant (i.e., new transmission or retransmission) or a configured grant (i.e., new transmission).
  • the CGT is stopped when the UE has received a PDCCH indicating configured grant Type 2 activation, or upon an implicit ACK for the associated HARQ process (i.e., a grant for a new transmission).
  • NR Rel-15 only an initial transmission of a TB is allowed to use either type of an UL CG.
  • any HARQ retransmissions of a TB must rely on dynamic UL grant, which is indicated via PDCCH addressed to the UE’s configured scheduling RNTI (CS-RNTI).
  • CS-RNTI configured scheduling RNTI
  • NR Rel- 16 introduced autonomous uplink (AUL), which supports autonomous HARQ retransmission using a CG.
  • AUL autonomous uplink
  • a new UE timer (referred to as “CG retransmission timer” or CGRT for short) is used to protect the HARQ procedure so that the retransmission can use the same HARQ process for both transmission and retransmission of a transport block (TB) of UL data.
  • CGRT is configured by the parameter cg-RetransmissionTimer shown in Figure 7. The CGRT is started for a HARQ process configured with AUL upon the data transmission using a configured grant, and a retransmission using another configured grant is triggered when the CGRT expires.
  • This functionality helps the UE to avoid a HARQ process being stalled in case a gNB has missed the HARQ transmission initiated by UE.
  • an observed issue is that a UE may just repetitively initiate autonomous HARQ retransmissions for a HARQ process for a long duration, but the gNB may not successfully receive the transmissions, e.g., due to bad radio channel quality or repetitive listen-before-talk (LBT) failures in case of a shared channel. This is undesirable since the data in the TB may no longer be useful and further retransmission attempts would unnecessarily congest the channel and affect the latency of other packets in the UL buffer.
  • LBT listen-before-talk
  • the UE may eventually trigger RLC-layer retransmission for an RLC PDU that is undergoing HARQ retransmissions.
  • the retransmitted RLC PDU would occupy a different HARQ process, such that the UE would then maintain two HARQ processes in transmission for the same RLC PDU and the gNB’s RLC receiver may receive duplicate RLC PDUs. This may create problems with wraparound of RLC sequence number.
  • the second received RLC PDU may be treated as new data and passed to upper layers rather than being dropped as a duplicate.
  • the existing CGT is configured to indicate the maximum amount of time for the UE to complete transmission of an HARQ process.
  • the UE should flush the HARQ buffer for this HARQ process and transmit new data associated with it.
  • both CGT and CGRT are configured for a HARQ process, both timers can be operated in parallel. In this way, the UE can perform HARQ retransmission using CG resources for a HARQ process while CGT is running for the process.
  • the value used for CGT should be longer than the value used for CGRT.
  • An initial transmission of a TB for HARQ process m occurs at tO using a CG resource, causing the UE to start CGT and CGRT.
  • the CGRT interval expires at tl while the CGT is still running, causing the UE to retransmit the TB for HARQ process m using the CG resource and restart the CGRT.
  • the same process occurs at t2.
  • the CGT interval expires at a subsequent time tk, causing the UE to flush the TB from the buffer for HARQ process m and make this HARQ process available for transmitting a new TB.
  • a UE can be provided with multiple active UL CGs for the UE’s active bandwidth part (BWP) in the UE’s serving cell.
  • BWP active bandwidth part
  • the availability of multiple CGs can, for example, enhance reliability and reduce latency for critical services.
  • NR operation in unlicensed spectrum e.g., NR-U
  • multiple CGs are under consideration as a means for allowing a UE to switch to slot-based transmissions after initiating the COT (channel occupancy time) to minimize DMRS and UCI overhead.
  • HARQ processes can be one or more HARQ processes in the HARQ process pool assigned to each CG configuration. There is also a separate CGT timer and CGRT setting associated with each CG configuration. HARQ processes can also be shared between CG configurations, which can increase flexibility and avoid depletion of limited HARQ process space for the UE.
  • a logical channel can be mapped to multiple CG configurations, such that the UE can transmit data of the LCH using multiple active CG resources at the same time. If a TB was transmitted using a CG resource, the TB can be retransmitted using the CG resource (among the set of CG resources mapped to the LCH) that comes earliest in the time, which helps to reduce the latency. However, the CG resource selected for retransmission should be the same size as the CG resource used for the initial transmission to avoid the need for rate-matching. In addition, the UE shall use the same HARQ process for transmission and retransmission of a TB.
  • the CGT timer for a HARQ process shall be started only when the TB using this HARQ process is initially transmitted.
  • the value of the CGT timer is set according to the configuration of the CG resource used for the initial transmission.
  • the CGRT shall be (re)started for every transmission/retransmission attempt. For example, if an initial TB transmission uses a resource in CG configuration 1, the CGRT is started using the timer value included in CG configuration 1. If the TB retransmission is performed with the resource in CG configuration 2, the CGRT need to be restarted using the timer value included in CG configuration 2.
  • the HARQ process number field in an UL DCI (e.g., formats 0 0 and 0 1) scrambled by CS-RNTI is used to indicate which CG configuration is to be activated/deactivated/reactivated and which CG configurations are to be released.
  • NDI in the received HARQ information is 0.
  • the UE Upon reception of an activation/deactivation/reactivation command, the UE sends the gNB a confirmation MAC CE that includes a bitmap in which each bit position corresponds to a particular one of the CG configurations, e.g., the bit position corresponds to the CG index.
  • the TB repetition is also supported in NR, with the same resource configuration being used for all K repetitions of a TB, where K also includes the initial transmission.
  • K Possible values of K are ⁇ 1, 2, 4, 8 ⁇ .
  • the parameters repK and repK-RV in Figure 7 define the K repetitions to be applied to the transmitted transport block and the redundancy version (RV) pattern to be applied to the repetitions, respectively.
  • the initial transmission of a transport block may start at:
  • the repetitions shall be terminated after transmitting K repetitions, or at the last transmission occasion among the K repetitions within a periodicity (P), or when a UL grant for scheduling the same TB is received within P, whichever condition is reached first.
  • the UE is not expected to be configured with the time duration for the transmission of K repetitions larger than the time duration derived by P.
  • Type 1 and Type 2 PUSCH transmissions with a configured grant when the UE is configured with repK > 1, the UE shall repeat the TB across the repK consecutive slots applying the same symbol allocation in each slot. If the UE determines that the symbols allocated for PUSCH are DL symbols according to the slot configuration, the multi-slot PUSCH transmission is omitted in that slot.
  • DL-SPS is a scheme similar to semipersi stent scheduling in LTE.
  • a semi-static resource scheduling pattern is signaled in advance to the device.
  • L1/L2 control signaling which also includes parameters such as the time-frequency resources and coding-and- modulation scheme to use, the device receives DL data transmissions according to the preconfigured pattern.
  • a periodicity of the DL data transmission is configured via RRC signaling and activation is via PDCCH similar to dynamic scheduling, but using CS-RNTI instead of C-RNTI.
  • PDCCH also provides time-frequency resources and other necessary parameters in a similar way as dynamic scheduling.
  • the HARQ process number is derived from the starting time of the DL data transmission according to a formula.
  • the UE Upon activation of DL-SPS, the UE receives DL data transmission periodically according to the RRC-configured periodicity using the transmission parameters indicated by the PDCCH DCI activating the transmission. Hence, control signaling is only used once and the overhead is reduced. After enabling SPS, the UE continues to monitor the set of candidates PDCCHs for UL and DL scheduling DCI. This is useful in the case that there are occasional transmissions of large amounts of data for which the DL-SPS allocation is insufficient. It is also used to handle HARQ retransmissions that are dynamically scheduled.
  • Configured UL grants and DL SPS can be particularly useful for ultra-reliable low- latency communications (URLLC) services. Additionally, several techniques are available to make URLLC more resilient to interference from enhanced mobile broadband (eMBB) services. These are summarized below.
  • One UL cancellation technique uses UL power control to increase the transmission power of UL URLLC data to make it more resilient to interference from the eMBB users.
  • the main advantage with this technique is that it does not require any changes to eMBB UEs, such that it will work with Rel-15 UEs.
  • the URLLC UE’s transmit power spectral density (PSD) may have to be increased significantly to guarantee performance with interfering eMBB traffic, which can cause interference to other cells.
  • PSD power spectral density
  • UEs not in close vicinity of the gNB may not have the power budget for such an increase, and thus will not have the Signal to Interference and Noise Ratio (SINR) necessary to maintain performance.
  • SINR Signal to Interference and Noise Ratio
  • a second technique is based on a cancellation indicator.
  • the gNB can transmit a cancellation indicator to the eMBB UE.
  • the eMBB UE Upon reception of this indicator, the eMBB UE will avoid transmitting on a set of preconfigured resources.
  • the mechanism for UL cancellation indication includes a reference time-frequency region that is configured for the UE by RRC signaling, and a DCI that indicates parts of the configured resources within which the transmission should be cancelled.
  • the reference time- frequency region is also referred to as “reference resource” (RR).
  • RR reference resource
  • the size of the cancellation indication DCI as well as the time-domain granularity are configurable. The frequency-domain granularity can then be determined from the total bit field size and the time-domain granularity.
  • a typical use case for the cancellation indicator is when eMBB traffic is scheduled on all PRBs for an entire slot and time sensitive URLLC traffic needs to be transmitted.
  • time sensitive means that the traffic requires instant access to the channel and waiting until the next slot will introduce unacceptable delay.
  • URLLC traffic maybe be scheduled on one or a few OFDM symbols in a slot, and with a significantly shorter scheduling delay between scheduling DCI and scheduled UL transmission.
  • eMBB users may already have been scheduled on all available time/frequency resources during the slot, but the gNB can send the cancellation indicator to cancel some of the eMBB traffic and reduce the interference to the URLLC UE.
  • a base station e.g., gNB, ng-eNB
  • a base station should choose the earliest moment of time when resources can be normally allocated without colliding with resources allocated for an ongoing DL transmission for the intended UE. This may be in the beginning of a slot or a mini-slot.
  • DL pre-emption may happen when long term allocation(s) (e.g., slot based) occupy resources (e.g., wideband resources) and there is no room for URLLC data transmission, which is often supported using a mini-slot.
  • the scheduler can send DCI to inform the intended URLLC UE that an override (also referred to as “pre-emption”) has been triggered for the ongoing DL transmission.
  • the pre-empted part of the original message pollutes the UE soft buffer, since only noise/interference is received. It is therefore important to flush the affected bits from the soft buffer to improve the likelihood of decoding the other, correctly-received eMBB data at the UE. If not, the pre-empted bits may negatively impact decoding in retransmissions, which will likely happen.
  • Rel-15 provides multiple options for DCI based indication of the pre-emption by explicit signaling.
  • This first option provides the indication as a 14-bit bitmap, which addresses reference DL resource domains in between two pre-emption indication messages. Highest resource resolution of this indication is one OFDM symbol and one-half BWP, but not at the same time. In general, the resolution becomes coarser as message periodicity increases. Since this is group-common signaling, all UEs using the BWP may read it.
  • CBG flushing out information As defined in 3GPP TS 38.213 (vl5.12.0) section 7.3.1.2.
  • This option provides user-specific signaling.
  • the HARQ retransmission DCI which contains a set of CB/CBGs, may have a special bit to indicate that the UE must overwrite (i.e., do not combine) existing bits in the soft buffer by retransmitted code block (CB) or CB group (CBG) soft bits.
  • CB code block
  • CBG CB group
  • Dynamic allocation is designed for flexibility to traffic demands and/or patterns, but it has signaling inefficiencies that increase latency. At a minimum, this requires a SR and DCI allocating subsequent grant before UL transmission. If the not grant is not fitting, the UE sends BSR and data transmission together, and the UE gets another grant in a second DCI for subsequent transmission. So, two or four signaling messages must be exchanged before data transmission can occur, which adds considerable latency can be problematic for ultra-low latency for a large variety of traffic.
  • Grant-free allocation is designed for low-latency periodic traffic when SPS/CG is allocated with frequent periodicity but is inefficient for non-periodic traffic, e.g., resources are wasted for allocation instances with no data to send.
  • the focus of 5G low-latency solutions is periodic traffic, e.g., in factory automation scenarios.
  • the network can use a longer period of the allocation to accommodate the fact that the UE doesn’t have a periodic pattern, but this increases latency since data arriving in the transmission buffer must wait longer for a transmission opportunity.
  • Applicant has recognized that there is no current solution that provides flexible resource grant/allocation with low signaling overhead for transmission patterns that are non-periodic but nonetheless are relatively known (e.g., somewhat regular, or at least not completely irregular). For such a pattern, a single allocation event similar to CG/SPS could be beneficial.
  • the scheduling DCI includes all information (e.g., resource allocation and transmission encoding/decoding parameters) about the resource allocation to be modified. For example, when cancellation/pre-emption DCIs are used to prohibit certain transmission (e.g., when higher-priority UEs are prioritized over a certain resource), the cancellation DCI must indicate all the reference resources for the cancelled or pre-empted occasions. This can cause significant signaling overhead if the occasions are spread over large range of reference resources. More generally, the signaling size or amount does not vary much between new and modified allocations, nor with amount of data to be transmitted.
  • Applicant has also recognized that many 6G use cases are based on distributed AI.
  • UEs involved in distributed AI (also referred to as AI agents in this context) intrinsically form a “group”, with some relationships among traffic patterns of these UEs.
  • an AI agent may transmit some data based on data transmission of another AI agent.
  • the network could leverage upon this relationship by sharing resources among AI agents of the group.
  • a group of AI agents are handled independently separately from a scheduling point of view, whereby each AI agent has a separate resource assignment with consequent high signaling overhead. Given a limited amount of signaling resources in a cell, this restriction may limit the number of distributed AI agents that a cell can support.
  • embodiments of the present disclosure provide flexible and efficient techniques to dynamically activate, deactivate, and/or modify a pre-configured resource allocation (e.g., CG/SPS) for a one or more UEs, such as a group of UEs.
  • a pre-configured resource allocation e.g., CG/SPS
  • CG/SPS resource allocation
  • UEs such as a group of UEs.
  • CG/SPS resource allocation
  • a network can send to one or more UEs indications of whether the respective UEs are allowed to transmit or receive during the occasions within the pre-configured allocation.
  • An example discussed in more detail below is a bitmap in which each bit indicates usage of a particular occasion, also referred as “bitmap DCI” for convenience.
  • bitmap DCI bitmap DCI
  • the number of occasions covered by the bitmap depends on its length, i.e., the number of bits that it contains.
  • the network indicates the occasions that are allowed and are not allowed to be used by the intended recipient UE(s).
  • each bitmap DCI can be unicast and/or dedicated to a particular UE, or a single bitmap DCI can contain multiple bitmaps corresponding to multiple UEs.
  • the network can arrange the respective bitmaps to maintain orthogonality of the resource allocation between multiple UEs, such that the UEs will not interfere or transmit during the same occasion.
  • these techniques facilitate dynamic resource allocation with much lower signaling overhead since the bitmap DCI does not carry resource-related information. In other words, there is no change of resource allocation but only an indication of allowed/not-allowed transmission occasions.
  • the bitmap DCI can be arranged in different ways discussed below, but generally based on knowledge of UE (non-periodic) traffic pattern over the applicable occasions.
  • a group- common activation message for a pre-configured allocation/grant. For example, after the network provides a pre-configured allocation that is common to a group of UEs, the network sends a group activation DCI to all group members. As such, there is no need to transmit UE-specific activation DCI (with resource information) to all UEs of the group.
  • the group activation DCI can be used independently of or together with the bitmap DCI embodiments discussed above. Embodiments of the present disclosure can provide various benefits and/or advantages, in addition to those discussed above.
  • embodiments can be more spectrally efficient than conventional CG/SPS, by allowing a group of UEs to share a single periodic grant or allocation. Since each UE’s traffic pattern is irregular, the spectral resources needed to meet application latency requirements are less than if each UE was allocated independent periodic resources. In other words, embodiments can avoid the waste of resource that occurs when conventional periodic resource allocations (e.g., CG or SPS) are used for non-periodic traffic.
  • conventional periodic resource allocations e.g., CG or SPS
  • embodiments can require less signal overhead in comparison to conventional dynamic resource allocation.
  • the usage of bitmap-based DCIs and/or group activation DCIs reduces the need for PDCCH resources.
  • a bitmap DCI indicates multiple occasions without including other transmission parameters, which remain as previously configured.
  • embodiments are more flexible and have lower overhead than conventional cancellation or pre-emption schemes used in 5G/NR
  • group activation DCIs avoid sending multiple activation DCIs to individual group members.
  • embodiments can facilitate improvements to group-based use cases, such as a group of cooperative UEs involved in a distributed AI model in an industrial scenario. All members of the group can be aware of group-allocated resources, based on a single common pre-configured grant and (optionally) a group activation DCI. Moreover, bitmap DCI(s) facilitate awareness and/or coordination among group members, thereby preventing and/or reducing interference while maintaining low latency that is important for such scenarios.
  • Certain advantages of the disclosed techniques in relation to conventional dynamic scheduling can be quantified as follows. Using a bitmap DCI that indicates and/or applies to N UL occasions, a minimum of two (2) signaling messages (initial allocation + initial bitmap DCI) and a maximum of N+l signaling messages (initial allocation + bitmap DCI per occasion) are required. In contrast, for dynamic UL resource allocation, a minimum 2N signaling messages (SR + scheduling DCI per occasion) and a maximum of 4N signaling messages (SR + BSR + 2 scheduling DCI per occasion) are required.
  • N DL occasions when using a bitmap DCI that indicates and/or applies to N DL occasions, a minimum of two (2) signaling messages (initial allocation + bitmap DCI depicting N occasions) and a maximum of N+l signaling messages (initial allocation + bitmap DCI per occasion) are required. In contrast, N signaling messages are required for dynamic DL resource allocation (scheduling DCI grant for each occasion).
  • Equals control signaling can also improve latency. Signaling messages that are incorrectly decoded by the recipient may need to be retransmitted, which can increase latency.
  • each signaling message will have a decoding error probability that is related to message size and channel conditions, among other things. As such, fewer signaling messages per occasion and/or smaller signaling messages (e.g., bitmap DCI) introduce fewer decoding errors per occasion, resulting in an overall reduction in average latency. Similarly, fewer and/or smaller signaling messages (including retransmissions) can free up constrained signaling capacity (e.g., PDCCH) for other needs and/or purposes.
  • constrained signaling capacity e.g., PDCCH
  • embodiments can facilitate tuning and/or adjusting a periodic resource allocation to be compatible with non-periodic traffic patterns of various UEs.
  • the network can allocate individual occasions of a periodic resource allocation to different UEs, thereby increasing utilization of periodic resource allocations as compared to conventional UL CG or DL SPS.
  • resource allocation can represent an UL pre-configured resource allocation (e.g., similar to UL CG) or a DL pre-configured resource allocation (e.g., similar to DL SPS).
  • resource allocation can represent an UL pre-configured resource allocation (e.g., similar to UL CG) or a DL pre-configured resource allocation (e.g., similar to DL SPS).
  • configured grant (or CG) may be used to refer to such an UL pre-configured resource allocation, which may be the same as or different from a conventional UL CG used in 5G/NR networks.
  • embodiments described herein are applicable to operation in either licensed or unlicensed (or shared-access) spectrum (e.g., NR or NR-U).
  • Figures 9-12 show various communications between a RAN node (e.g., gNB) 904 and a group of UEs (UE1 901, UE2902, and UE3 903) that illustrate various embodiments of the present disclosure.
  • UEs 1 and 2 are in a subgroup A and UEs 2 and 3 are in a subgroup B.
  • subgroups A and B overlap only by UE2.
  • the RAN node provides a group resource allocation to the group of UEs.
  • the group resource allocation is intended to be shared by the UEs of the group.
  • the resource allocation is for UL resources and includes eight (8) occasions (numbered 1-8). These occasions may be periodic occasions, e.g., as defined by a periodicity parameter included in the resource allocation.
  • the group resource allocation can also identify specific time resources (e.g., symbols and/or timeslots) and frequency resources (e.g., RBs and/or BWPs) during each of the occasions, in a similar manner as UL CGs discussed above.
  • Figure 10 shows an exemplary scenario involving a first sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a first sub-group that includes a particular UE, and a subsequent second sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a second sub-group that includes the UE but differs from the first sub-group by at least one UE.
  • the RAN node sends a first activation indication in the form of a DCI to sub-group B prior to occasion 1.
  • This activation DCI indicates that the group resource allocation is activated (“1”) for sub-group B members (i.e., UEs 2 and 3) for all subsequent occasions of the allocation. This is indicated by the bracket extending from before occasion 1 until after occasion 8. Since UE1 does not receive an activation DCI, it remains in a “default” state whereby the group resource allocation is deactivated for subsequent occasions 1- 8.
  • occasions 1-3 are shown as deactivated (“X”) in Figure 10, occasions 4-8 are also deactivated at this point but are later activated, as explained below.
  • UE3 transmits UL data (shown as “TX data”) during occasion 1 using the resources allocated.
  • the transmitted UL data may have arrived in UE3’s buffer before or after receiving the activation DCI.
  • UL data also arrives in UE2’s buffer before occasion 3. Since the group resource is activated for subgroup B, UE2 is able to transmit the buffered UL during occasion 3.
  • UL data also arrives in UEl’s buffer after occasion 1, but since the resource allocation has not been activated for UE1, UE1 cannot transmit in occasion 2.
  • UE1 may send a scheduling request (SR) or other traffic pattern indication to the RAN node.
  • SR scheduling request
  • SR will be used herein to refer to any type of indication of a UE’s UL traffic pattern that is relevant for subsequent indications of allowance.
  • the RAN node sends a second activation indication in the form of a DCI to sub-group A.
  • This activation DCI indicates that the group resource allocation is activated (“1”) for sub-group A members (i.e., UEs 1 and 2) for all subsequent occasions of the allocation. This is indicated by the bracket extending from before occasion 4 until after occasion 8 for UE1. Since UE3 does not receive an activation DCI, it remains in its current state whereby the group resource allocation was previously activated for subsequent occasions prior to occasion 1.
  • UE1 Based on the received activation DCI before occasion 4, UE1 transmits UL data (shown as “TX data”) during occasion 4 using the allocated resources. UL data also arrives in UE3’s buffer before occasion 6. Since the group resource is activated for subgroup B, UE3 is able to transmit the buffered UL during occasion 6.
  • TX data UL data
  • the RAN node sends a third activation indication in the form of a DCI to UE3.
  • This activation DCI indicates that the group resource allocation is deactivated (“0”) for UE3 for all subsequent occasions of the allocation. This is indicated by the bracket extending from before occasion 7 until after occasion 8 for UE3. Since UEs 1 and 2 do not receive an activation DCI, they remain in their current states whereby the group resource allocation was previously activated for subsequent occasions prior to occasion 4.
  • Figure 11 shows another exemplary scenario involving a first group activation indication followed by one or more subsequent second sub-group and/or individual UE activation indications.
  • the RAN node sends a first activation indication in the form of a DCI to the entire group prior to occasion 1.
  • This activation DCI indicates that the group resource allocation is activated (“1”) for all group members (i.e., UEs 1-3) for all subsequent occasions of the allocation. This is indicated by the bracket extending from before occasion 1 until after occasion 8.
  • UE3 transmits UL data (shown as “TX data”) during occasion 1 using the resources allocated.
  • the transmitted UL data may have arrived in UE3’s buffer before or after receiving the activation DCI.
  • UL data also arrives in UEl’s buffer before occasion 2. Since the group resource is activated for the entire group, UE1 is able to transmit the buffered UL during occasion 2.
  • UL data also arrives in UE2’s buffer before occasion 3. Since the group resource is activated for the entire group, UE2 is able to transmit the buffered UL during occasion 3.
  • the RAN node sends a second activation indication in the form of a DCI to sub-group A.
  • This activation DCI indicates that the group resource allocation is deactivated (“0”) for sub-group A members (i.e., UEs 1 and 2) for all subsequent occasions of the allocation. This is indicated by the bracket extending from before occasion 4 until after occasion 8 for UEs 1 and 2. Since UE3 does not receive an activation DCI, it remains in its current state whereby the group resource allocation was activated for subsequent occasions prior to occasion 1.
  • UL data arrives in UE3’s buffer before occasion 6. Since the group resource is activated for UE3, UE3 is able to transmit the buffered UL during occasion 6. Before occasion 7, the RAN node sends a third activation indication in the form of a DCI to UE3.
  • This activation DCI indicates that the group resource allocation is deactivated (“0”) for UE3 for all subsequent occasions of the allocation. This is indicated by the bracket extending from before occasion 7 until after occasion 8 for UE3.
  • the RAN node Before occasion 7, the RAN node also sends a fourth activation indication in the form of a DCI to sub-group A.
  • This activation DCI indicates that the group resource allocation is activated (“1”) for sub-group A members (i.e., UEs 1 and 2) for all subsequent occasions of the allocation. This is indicated by the bracket extending from before occasion 7 until after occasion 8 for UEs 1 and 2.
  • UL data arrives in UEl’s buffer before occasion 8. Since the group resource allocation is activated for sub-group A, UE1 is able to transmit the buffered UL during occasion 8.
  • Figure 12 shows another exemplary scenario involving a first activation indications to individual UEs of the group followed by a subsequent second group activation indication.
  • the RAN node sends a first activation indications in the form of DCIs to UEs 1 and 3 prior to occasion 1. Note that in this exemplary scenario, UEs 1 and 3 are not members of the same sub-group.
  • activation DCIs indicate that the group resource allocation is activated (“1”) for UEs 1 and 3, respectively, for all subsequent occasions of the allocation. This is indicated by the bracket extending from before occasion 1 until after occasion 8. Since UE2 does not receive an activation DCI, it remains in a “default” state whereby group resource allocation is deactivated for subsequent occasions 1-8. Although only occasions 1-5 are shown as deactivated (“X”) in Figure 12, occasions 6-8 are also deactivated at this point but are later activated, as explained below.
  • UE3 based on the received activation DCI before occasion 1, UE3 transmits UL data (“TX data”) during occasion 1 using the resources allocated.
  • the transmitted UL data may have arrived in UE3’s buffer before or after receiving the activation DCI.
  • UL data also arrives in UEl’s buffer before occasion 2. Since the group resource is activated for UE1, UE1 is able to transmit the buffered UL during occasion 2.
  • the RAN node Before occasion 4, the RAN node sends a second activation indication in the form of a DCI to the group.
  • This activation DCI indicates that the group resource allocation is deactivated (“0”) for all group members (i.e., UEs 1-3) for all subsequent occasions of the allocation. This is indicated by the brackets extending from before occasion 4 until after occasion 8 for UEs 1-3.
  • the RAN node sends a third activation indication in the form of a DCI to UE2.
  • This activation DCI indicates that the group resource allocation is activated (“1”) for UE2 for all subsequent occasions of the allocation. This is indicated by the bracket extending from before occasion 6 until after occasion 8 for UE2. Since UEs 1 and 3 do not receive an activation DCI, they remain in their current states whereby the group resource allocation was previously deactivated for subsequent occasions prior to occasion 4.
  • UL data arrives in UE2’s buffer before occasion 7. Since the group resource allocation was previously activated for UE2, UE2 is able to transmit the buffered UL during occasion 7.
  • each of these activation indication can also be in the form of UE-specific DCIs sent concurrently (e.g., in the same slot) to the members of a particular group (e.g., UE1- UE3) or a particular sub-group B (e.g., UE1 and UE2, or UE2 and UE3).
  • a particular group e.g., UE1- UE3
  • a particular sub-group B e.g., UE1 and UE2, or UE2 and UE3
  • the RAN node can deactivate a group resource allocation for a particular UE by sending a scheduling DCI with a UE- specific dynamic resource allocation for transmission or reception of data by that EE (i.e., on PDSCH or PUSCH)
  • the EE-specific dynamic resource allocation implicitly indicates that the group resource allocation is deactivated for use by the EE during subsequent occasions.
  • the group resource allocation can be transmitted/received in an RRC message and the activation indications can be DCI, as discussed above.
  • an activation indication can be implicit from the group resource allocation.
  • the UEs of the group can infer activation based on receiving the group resource allocation from the RAN node. Subsequently, the RAN node can send other activation DCIs that explicitly deactivate (and optionally reactivate) the group resource allocation for the group, one or more sub-groups, and/or one or more individual UEs.
  • the activation DCIs can include additional information about subsequent occasions that are activated, such as locations of occasions on a time-frequency resource grid, modulation and coding scheme (MCS), redundancy value (RV) pattern, etc.
  • MCS modulation and coding scheme
  • RV redundancy value
  • the RAN node can send an activation DCI that has updated transmission parameters. This can be useful if radio channel conditions affecting the group have changed since the initial group resource allocation.
  • the group of UEs can be configured with multiple resource allocations.
  • the RAN node can include with each activation DCI an indication of the associated resource allocation. For example, if each resource allocation is associated with a unique identifier recognizable by the UEs, the RAN node can include the associated identifier with the activation DCI.
  • the identifier can be an allocation index, e.g., based on order in which the allocations were configured.
  • a group of UEs could be configured with two periodic resource allocations, each having a different period such that the occasions of the two allocations do not (or at least only minimally) coincide.
  • the RAN node can select the most appropriate of the two allocations for activation/deactivation.
  • Each activation DCI can include an identifier of the allocation.
  • the RAN node can send activation DCIs as UE-specific (e.g., dedicated/unicast), sub-group, or group-common activation DCIs (i.e., broadcast/multicast).
  • UEs can apply various rules and/or criteria to determine priority between UE-specific, sub-group, or group-common activation DCIs that have conflicting activation indications.
  • rules and/or criteria can include any of the following:
  • UE-specific activation DCI always has priority over sub-group and/or group-common activation DCIs.
  • Sub-group activation DCIs have priority over group-common activation DCIs.
  • UEs of the group can be configured for how to handle priority between UE-specific and group-common activation DCIs. This can be done, for example, via RRC signaling, NAS signaling, or information with a activation DCI (as mentioned above).
  • a UE may be further restricted for transmitting in occasions indicated as activated by one or more rules and/or criteria related to the data available for transmission (i.e., in addition to availability of any data).
  • rules and/or criteria can be included with an activation DCI.
  • rules and/or criteria can be configured via RRC signaling (e.g., together with the resource allocation) or predetermined (e.g., specified by 3GPP).
  • RRC signaling e.g., together with the resource allocation
  • predetermined e.g., specified by 3GPP
  • LCHs logical channels
  • LCDs groups of logical channels
  • URLLC LCHs URLLC LCHs
  • Available data has a reliability requirement (e.g., eMBB) that is less than a reliability level associated with the resource allocation (e.g., URLLC); and/or
  • Available data has a latency requirement (e.g., eMBB) that is greater than a latency level associated with the resource allocation (e.g., URLLC).
  • eMBB latency requirement
  • URLLC resource allocation
  • the UE can use any remaining resources allocated during the activated occasion to transmit other available data that does not meet the rules and/or criteria (e.g., other lower-priority data). For example, if UE has insufficient URLLC data to fill the resources of an activated occasion, then UE can also transmit eMBB traffic in remaining resources of the activated occasion.
  • the RAN node can send a group-common activation DCI to the UEs of the group.
  • the group-common activation DCI can include N tuples (UE ID, activation flag ⁇ for a group of N UEs.
  • UE ID can be an explicit UE identifier or an index into a table of UE identifiers, where the table is known (e.g., previously configured) between the RAN node and the group of UEs.
  • Activation flag can be a Boolean variable, e.g., with “1” indicating activation and “0” indicating deactivation, as illustrated in Figures 10-12 above.
  • the UE ID can be implicit based on the ordering within the group-common bitmap DCI.
  • the first activation flag can be for the first group member (e.g., UE1 in Figures 9-12)
  • the second activation flag can be for the second group member (e.g., UE2), etc.
  • the activation indication can be a multi-bit value.
  • the activation indication can take on more than two values, with each of the values indicating a particular type of data traffic for which the group resource allocation is activated.
  • a value of “0” can indicate deactivation for all traffic
  • a value of “1” can indicate activation for only highest-priority traffic
  • a value of “2” can indicate activation for medium- or high-priority traffic
  • a value of “3” can indicate activation for all traffic.
  • a similar arrangement can be used for other traffic differentiators, including reliability, latency, logical channel, etc.
  • each UE can send feedback to the RAN node about whether each activation DCI was successfully decoded by the UE. This can prevent and/or mitigate uncertainty about which UEs of the group have decoded and applied their respective UE- specific, sub-group, or group-common activation DCIs.
  • the UEs can send the feedback as UCI over PUCCH or as MAC CE or other feedback message over PUSCH.
  • the feedback can be acknowledgement (ACK) only.
  • ACK acknowledgement
  • the RAN node becomes aware of which UEs of the group have not responded to an activation DCI and can resend an activation DCI to those as a group-common, sub-group, or UE-specific message.
  • ACK-only can be preferred in scenarios with small groups of UEs and/or relatively high reliability requirement (e.g, URLLC).
  • the feedback can be negative ACK (NACK) only.
  • NACK negative ACK
  • the RAN node becomes aware of which UEs of the group have responded to an activation and can resend an activation DCI to those as a group-common, sub-group, or UE-specific message.
  • NACK-only feedback can be preferred for scenarios with large groups of UEs (e.g., reduced feedback overhead assuming most UEs correctly decode activation DCIs) and/or relatively low reliability requirement.
  • ACK-only or ACK-NACK feedback can be used to address such scenarios.
  • no explicit feedback is used. If a UE has not decoded/received the activation DCI, then the UE does not perform any transmission on occasions indicated as activated for the UE by the activation DCI. This implicitly indicates that either the UE had no data to transmit or the UE did not correctly receive the activation DCI. In many cases, a UE having data to transmit may send a subsequent SR to the RAN node, which can then send another activation DCI.
  • UEs of the group can be configured with a activation DCI feedback mode (e.g., ACK-only, NACK-only, ACK-NACK, or no feedback). This can be done, for example, via RRC signaling, NAS signaling, or information included with an activation DCI.
  • the RAN node can flexibly configure activation DCI feedback mode based on particular scenarios and/or requirements. For example, if there is a group with a large number of UEs or a relatively low reliability requirement, the RAN node can configure UEs of the group for NACK-based feedback. However, if the number of UEs in the group later shrinks or a reliability requirement increases, the RAN node can reconfigure UEs remaining in the group for ACK-based feedback.
  • the RAN node can have information about traffic patterns of the UEs of the group, from which the RAN node can determine the group resource allocation and/or the occasions activated for each of the UEs.
  • One way the RAN node can obtain such information is directly from the UEs, such as the SR shown in Figure 10 or buffer status reports (BSRs) sent in the resources of the activated occasions.
  • BSRs buffer status reports
  • the RAN node can receive UE traffic pattern information from another network node or function, such as a UPF in the 5GC (or equivalent in a 6G network) or an application function (AF, e.g., server) that communicates with the group of UEs.
  • the RAN node can use artificial intelligence/machine learning (AI/ML) algorithms to predict UE traffic patterns. This can be based on SRs and/or BSRs received from the various UEs of the group, information provided by the DL scheduler, as well as other relevant traffic pattern information provided by another node or function, or by the UEs (e.g., application-related information).
  • AI/ML artificial intelligence/machine learning
  • the RAN node can estimate UL and/or DL traffic patterns for UEs of the group based on BSR/SR arrival periodicity, BSR size, DL data packet size and/or arrival periodicity, etc.
  • the RAN node can also estimate a variance or distribution of such traffic patterns.
  • the RAN node can determine the pre-configured resource allocation (e.g., UL CG or DL SPS) based on the estimated traffic patterns for the group of UEs. Moreover, if the traffic patterns of the group change with time, then the RAN node can provide updated UE-specific, sub-group, or group-common activation DCIs, which is much simpler and easier than deactivating and reactivating the pre-configured allocation in a conventional manner. This use can be particularly beneficial for Release-18 or beyond, e.g., extended reality (XR) traffic with a relatively fixed periodicity but varying amounts of data.
  • XR extended reality
  • the RAN node can select the UEs included in the group and/or in one or more sub-groups of the group. This selection can be based on one or more of the following criteria:
  • a common coverage area e.g., cell, cell sector, beam, etc.
  • An exemplary group of UEs with a correlated traffic pattern is two UEs that transmit with the same period but whose transmissions do not coincide and/or are out-of-phase.
  • An exemplary group of UEs with complementary latency requirements is a first UE requiring low latency and a second UE that can tolerate higher latency than the first UE.
  • a RAN node can manage a group resource allocation by a combination of activation indications (also referred to as “activation DCIs”) and allowance indications (also referred to as “bitmap DCIs”).
  • activation DCIs also referred to as “activation DCIs”
  • bitmap DCIs also referred to as “bitmap DCIs”.
  • the RAN node can send to UEs of the group respective bitmap DCIs that indicate of whether the respective UEs are allowed to transmit or receive during a particular subset of the occasions of the group resource allocation.
  • the number of occasions covered by the bitmap depends on its length, with one bit per occasion being exemplary.
  • the RAN node can activate a group resource allocation for all UEs of the group, but then use bitmap DCIs to control which UEs are allowed to transmit or receive in each of the occasions.
  • the RAN node can activate a group resource allocation for a sub-group of UEs, then use bitmap DCIs to control which UEs of the sub-group are allowed to transmit or receive in each of the occasions.
  • a particular UE can transmit or receive in a particular occasion only when the group resource allocation has been activated (at least for the UE) and a bitmap DCI (or other allowance indication) indicates that the UE is allowed to transmit or receive in that occasion.
  • Figures 13-14 show exemplary methods (e.g ., procedures) for a UE and a RAN node, respectively.
  • exemplary methods e.g ., procedures
  • various features of the operations described below correspond to various embodiments described above.
  • the exemplary methods shown in Figures 13-14 can be used cooperatively to provide various benefits, advantages, and/or solutions to problems described herein.
  • Figures 13-14 show specific blocks in particular orders, the operations of the exemplary methods can be performed in different orders than shown and can be combined and/or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines.
  • Figure 13 shows an exemplary method (e.g., procedure) for a user equipment (UE) operating in a RAN as one of a group of UEs, according to various exemplary embodiments of the present disclosure.
  • the exemplary method can be performed by a UE (e.g., wireless device, IoT device, etc.) configured according to other figures described herein.
  • a UE e.g., wireless device, IoT device, etc.
  • the exemplary method can include the operations of block 1310, where the UE can receive a group resource allocation for the group of UEs to transmit or receive data in the RAN.
  • the group resource allocation can include resources during a plurality of occasions, which can but are not required to be periodic.
  • the exemplary method can also include the operations of block 1320, where the UE can receive one or more activation indications of whether the group resource allocation is activated or deactivated for use by at least the UE. Each particular activation indication is associated with all occasions subsequent to (e.g., immediately following) the particular activation indication.
  • the UE can receive the group resource allocation and the one or more activation indications from a RAN node (e.g., gNB, ng-eNB, etc.) that provides a cell serving the UE.
  • a RAN node e.g., gNB, ng-eNB, etc.
  • the group resource allocation can be received as an RRC message and the activation indications can be received in respective DCI via a PDCCH.
  • receiving the one or more activation indications in block 1320 can include the operations of sub-block 1321-1322 for each particular activation indication.
  • the UE can attempt to decode a message containing the particular activation indication.
  • the UE can send, to the RAN, feedback indicating whether decoding the message was successful.
  • the feedback can be ACK-only (i.e., only when decoding was successful), NACK-only (i.e., only when decoding was unsuccessful), or both ACK-NACK, as discussed in more detail above.
  • the one or more activation indications can include any of the following:
  • the one or more activation indications can include a first sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a first sub-group that includes the UE; and a subsequent second sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a second sub-group that includes the UE but differs from the first sub-group by at least one UE.
  • a first sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a first sub-group that includes the UE a subsequent second sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a second sub-group that includes the UE but differs from the first sub-group by at least one UE.
  • the one or more activation indications can include a first group activation indication, indicating that the group resource allocation is activated for use by all UEs of the group; and a subsequent second activation indication, which is one of the following:
  • the one or more activation indications can include UE-specific activation indication, indicating that the group resource allocation is activated for use by the UE; and a subsequent second activation indication, which is one of the following:
  • the group resource allocation can include a plurality of resource allocations associated with a respective plurality of identifiers. Each particular activation indication can include an identifier of the resource allocation to which the particular activation indication applies.
  • the group resource allocation can include a transmission or reception configuration to be used by the group of UEs during the occasions.
  • the exemplary method can also include the operations of block 1330, where the UE can receive, after one of the occasions, a message including an updated transmission or reception configuration to be used by the group of UEs during occasions subsequent to the message.
  • the message does not include information describing the resources allocated during occasions subsequent to the message.
  • the message can include an activation indication.
  • an activation indication can be sent together with a new transmission or reception configuration, but without a resource allocation.
  • the activation indications can be “occasion-centric” instead of “resource-centric”, which facilitates smaller indicator size than conventional cancellation/pre-emption DCIs.
  • the exemplary method can also include the operations of block 1340, where the UE can receive a message that schedules transmission or reception of data with the RAN.
  • the message includes a UE-specific resource allocation which indicates that the group resource allocation is deactivated for use by the UE during subsequent occasions.
  • the reception of a dynamic UE-specific grant/assignment implicitly indicates that the group resource allocation has been deactivated for use by the UE (but not necessarily for other UEs of the group).
  • one of the activation indications can be implicit from the group resource allocation, indicating that the group resource allocation is activated for use by all UEs of the group.
  • the group resource allocation received in block 1310 can function and/or be interpreted as one of the activation indications received in block 1320, at least in these embodiments.
  • the exemplary method can also include the operations of block 1360, where during each particular occasion, the UE can selectively transmit or receive data based on a most recently received activation indication associated with the particular occasion.
  • the group resource allocation can be for transmitting uplink (UL) data to the RAN.
  • selectively transmitting or receiving data in block 1360 can include the operations of sub-block 1361, where the UE can refrain from transmitting UL data during an occasion when the group resource is activated for use by the UE based on one or more of the following:
  • the group resource allocation can be for receiving downlink (DL) data from the RAN.
  • selectively transmitting or receiving data in block 1360 can include the operations of sub-blocks 1362-1383.
  • the UE can monitor a control channel for respective messages scheduling DL data for reception during occasions when the group resource is activated for use by the UE.
  • the UE can refrain from receiving DL data during occasions when the group resource is activated for use by the UE, but during which no scheduling message was detected.
  • the exemplary method can also include the operations of block 1350, where the UE can receive one or more allowance indications of whether the UE is allowed to transmit or receive during the occasions.
  • Each particular allowance indication is associated with a consecutive subset of the occasions subsequent to (e.g., immediately following) the particular allowance indication.
  • selectively transmitting or receiving is further based on a most recently received allowance indication associated with the particular occasion.
  • the UE does not transmit or receive during an occasion unless the group resource allocation is activated (i.e., for at least the UE) and the occasion is allowed for the UE.
  • block 1350 is shown after block 1320 in Figure 13, the allowance indication(s) can be received at any time, with the UE selectively transmitting or receiving based on a most recent allowance indication (or a default state, if an applicable allowance indication has not been received).
  • each particular allowance indication includes a bitmap of a plurality of bits that indicate whether the UE is allowed to transmit or receive in a corresponding plurality of the occasions of the associated subset.
  • the bitmap DCI discussed above is an example of this type of indication.
  • each particular allowance indication can include one or more UE identifiers, and each UE identifier can correspond to one or more occasions of the particular subset associated with the particular allowance indication. Additionally, each UE identifier indicates that, in the corresponding occasions of the particular subset, the identified UE is allowed to transmit or receive but other UEs are not allowed to transmit or receive. For four occasions and UEs 1-3, an exemplary allowance indication according to these embodiments is (UEl, UE2, UE3, UE1 ⁇ .
  • Figure 14 shows an exemplary method (e.g., procedure) for allocating resources of a RAN, according to various exemplary embodiments of the present disclosure.
  • the exemplary method can be performed by a network node (e.g., base station, eNB, gNB, ng-eNB, etc., or component thereof) in the RAN (e.g, E-UTRAN, NG-RAN), such as network nodes configured according to other figures described herein.
  • the exemplary method can include the operations of block 1430, where the RAN node can transmit, to a group of UEs, a group resource allocation for the group of UEs to transmit or receive data in the RAN.
  • the group resource allocation can include resources during a plurality of occasions, which can but are not required to be periodic.
  • the exemplary method can include the operations of block 1440, where the RAN node can transmit one or more activation indications of whether the group resource allocation is activated or deactivated for use by at least one of the UEs.
  • Each particular activation indication is associated with all occasions subsequent to (e.g., immediately following) the particular activation indication:
  • the RAN node can provide a cell serving the group of UEs.
  • the group resource allocation can be transmitted as an RRC message and the activation indications can be transmitted in respective DCI via a PDCCH.
  • transmitting the one or more activation indications in block 1440 can include the operations of sub-block 1441, where in response to each particular activation indication, the RAN node can receive feedback indicating whether a particular one of the UEs was successful in decoding a message including the particular activation indication.
  • the feedback can be ACK-only (i.e., only when decoding was successful), NACK- only (i.e., only when decoding was unsuccessful), or both ACK-NACK, as discussed in more detail above.
  • the exemplary method can also include the operations of block 1410, where the network node can select the UEs included in the group based on one or more of the following criteria:
  • RAN node • within a common coverage area of the RAN node (e.g., cell, cell sector, beam);
  • the exemplary method can also include the operations of block
  • the RAN node can predict traffic patterns for the one or more UEs based on one or more of the following:
  • SR scheduling requests
  • BSR buffer status reports
  • the group resource allocation for the one or more UEs can be based on the predicted traffic patterns.
  • the activation indications include first activation indications that are based on the respective predicted UE traffic patterns, and second activation indications that are transmitted after the first indications and are based on respective actual UE traffic patterns during occasions after transmitting the first activation indications.
  • the RAN node can initially activate or deactivate the group resource allocation for the respective UEs of the group based on predicted traffic patterns and then (if needed) change the activation status for the respective UEs based on observed actual traffic patterns.
  • the one or more activation indications can include any of the following:
  • the one or more activation indications can include a first sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a first sub-group that includes the particular UE; and a subsequent second sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a second sub-group that includes the particular UE but differs from the first sub-group by at least one UE.
  • a first sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a first sub-group that includes the particular UE and a subsequent second sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a second sub-group that includes the particular UE but differs from the first sub-group by at least one UE.
  • the one or more activation indications can include a first group activation indication, indicating that the group resource allocation is activated for use by all UEs of the group; and a subsequent second activation indication, which is one of the following:
  • a sub-group activation indication indicating that the group resource allocation is deactivated for use by a sub-group that includes the particular UE
  • the one or more activation indications can include UE-specific activation indication, indicating that the group resource allocation is activated for use by the particular UE; and a subsequent second activation indication, which is one of the following: • a sub-group activation indication of whether the group resource allocation is activated or deactivated for use by a sub-group that includes the particular UE, or
  • the group resource allocation can include a plurality of resource allocations associated with a respective plurality of identifiers.
  • Each particular activation indication can include an identifier of the resource allocation to which the particular activation indication applies.
  • the group resource allocation can include a transmission or reception configuration to be used by the group of UEs during the occasions.
  • the exemplary method can also include the operations of block 1450, where the RAN node can transmit, after one of the occasions, a message including an updated transmission or reception configuration to be used by the group of UEs during occasions subsequent to the message.
  • the message does not include information describing the resources allocated during occasions subsequent to the message.
  • the message can include an activation indication.
  • an activation indication can be sent together with a new transmission or reception configuration, but without a resource allocation. In this manner, the activation indications can be “occasion-centric” instead of “resource-centric”, which facilitates smaller indicator size than conventional cancellation/pre emption DCIs.
  • the exemplary method can also include the operations of block 1460, where the RAN node can transmit a message that schedules transmission or reception of data by a particular UE (i.e., of the group) with the RAN.
  • the message includes a UE-specific resource allocation which indicates that the group resource allocation is deactivated for use by the particular UE during subsequent occasions.
  • the reception of a dynamic UE- specific grant/assignment implicitly indicates that the group resource allocation has been deactivated for use by the particular UE (but not necessarily for other UEs of the group).
  • one of the activation indications can be implicit from the group resource allocation, indicating that the group resource allocation is activated for use by all UEs of the group.
  • the group resource allocation transmitted in block 1430 can function and/or be interpreted as one of the activation indications transmitted in block 1440, at least in these embodiments.
  • the exemplary method can also include the operations of block 1480, where during each particular occasion, the RAN node can selectively receive or transmit data with one of the UEs of the group based on a most recently transmitted activation indication associated with the particular occasion.
  • the group resource allocation can be for transmitting uplink (UL) data to the RAN.
  • selectively receiving or transmitting data in block 1480 can include the operations of sub-block 1481, where the RAN node can receive no data during an occasion when the group resource is activated for use by a particular UE based on one or more of the following conditions at the particular UE:
  • the group resource allocation can be for receiving downlink (DL) data from the RAN.
  • selectively receiving or transmitting data in block 1480 can include the operations of sub-block 1482, where the RAN node can refrain from transmitting a message scheduling DL data for a particular UE during an occasion when the group resource is activated for use by the particular UE based on one or more of the following conditions related to the particular UE:
  • the exemplary method can also include the operations of block 1470, where the RAN node can transmit one or more allowance indications of whether the respective UEs are allowed to transmit or receive during the occasions.
  • Each particular allowance indication is associated with a consecutive subset of the occasions subsequent to (e.g., immediately following) the particular allowance indication.
  • selectively receiving or transmitting (e.g., in block 1480) during each particular is further based on a most recently received allowance indication associated with the particular occasion.
  • the RAN node does not transmit or receive with a particular UE during an occasion unless the group resource allocation is activated (i.e., for use by at least the particular UE) and the occasion is allowed for the particular UE.
  • block 1470 is shown after block 1440 in Figure 14, the allowance indication(s) can be transmitted at any time, with the RAN node selectively receiving or transmitting with a particular UE based on a most recent allowance indication (or a default state for the particular UE, if an applicable allowance indication has not been transmitted to the particular UE).
  • each allowance indication includes a bitmap of a plurality of bits that indicate whether a particular UE is allowed to transmit or receive in a corresponding plurality of the occasions of the associated subset.
  • the bitmap DCI discussed above is an example of this type of indication.
  • each allowance indication can include one or more UE identifiers, and each UE identifier can correspond to one or more occasions of the particular subset associated with the particular allowance indication. Additionally, each UE identifier indicates that, in the corresponding occasions of the particular subset, the identified UE is allowed to transmit or receive but other UEs are not allowed to transmit or receive. For four occasions and UEs 1-3, an exemplary allowance indication according to these embodiments is ⁇ UE1, UE2, UE3, UE1 ⁇ .
  • FIG. 15 shows a block diagram of an exemplary wireless device or user equipment (UE) 1500 (hereinafter referred to as “UE 1500”) according to various embodiments of the present disclosure, including those described above with reference to other figures.
  • UE 1500 can be configured by execution of instructions, stored on a computer-readable medium, to perform operations corresponding to one or more of the exemplary methods described herein.
  • UE 1500 can include a processor 1510 (also referred to as “processing circuitry”) that can be operably connected to a program memory 1520 and/or a data memory 1530 via a bus 1570 that can comprise parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art.
  • Program memory 1520 can store software code, programs, and/or instructions (collectively shown as computer program product 1521 in Figure 15) that, when executed by processor 1510, can configure and/or facilitate UE 1500 to perform various operations, including operations corresponding to various exemplary methods described herein.
  • execution of such instructions can configure and/or facilitate UE 1500 to communicate using one or more wired or wireless communication protocols, including one or more wireless communication protocols standardized by 3GPP, 3GPP2, or IEEE, such as those commonly known as 5G/NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, lxRTT, CDMA2000, 802.11 WiFi, HDMI, USB, Firewire, etc., or any other current or future protocols that can be utilized in conjunction with radio transceiver 1540, user interface 1550, and/or control interface 1560.
  • 3GPP 3GPP2
  • IEEE such as those commonly known as 5G/NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, lxRTT, CDMA2000, 802.11 WiFi, HDMI, USB, Firewire, etc., or any other current or future protocols that can be utilized in conjunction with radio transceiver 1540, user interface 1550, and/or control interface 1560.
  • processor 1510 can execute program code stored in program memory 1520 that corresponds to MAC, RLC, PDCP, SDAP, RRC, and NAS layer protocols standardized by 3GPP (e.g ., for NR and/or LTE).
  • processor 1510 can execute program code stored in program memory 1520 that, together with radio transceiver 1540, implements corresponding PHY layer protocols, such as Orthogonal Frequency Division Multiplexing (OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single-Carrier Frequency Division Multiple Access (SC-FDMA).
  • processor 1510 can execute program code stored in program memory 1520 that, together with radio transceiver 1540, implements device-to-device (D2D) communications with other compatible devices and/or UEs.
  • D2D device-to-device
  • Program memory 1520 can also include software code executed by processor 1510 to control the functions of UE 1500, including configuring and controlling various components such as radio transceiver 1540, user interface 1550, and/or control interface 1560.
  • Program memory 1520 can also comprise one or more application programs and/or modules comprising computer- executable instructions embodying any of the exemplary methods described herein.
  • Such software code can be specified or written using any known or future developed programming language, such as e.g., Java, C++, C, Objective C, HTML, XHTML, machine code, and Assembler, as long as the desired functionality, e.g, as defined by the implemented method steps, is preserved.
  • program memory 1520 can comprise an external storage arrangement (not shown) remote from UE 1500, from which the instructions can be downloaded into program memory 1520 located within or removably coupled to UE 1500, so as to enable execution of such instructions.
  • Data memory 1530 can include memory area for processor 1510 to store variables used in protocols, configuration, control, and other functions of UE 1500, including operations corresponding to, or comprising, any of the exemplary methods described herein.
  • program memory 1520 and/or data memory 1530 can include non-volatile memory (e.g, flash memory), volatile memory (e.g, static or dynamic RAM), or a combination thereof.
  • data memory 1530 can comprise a memory slot by which removable memory cards in one or more formats (e.g, SD Card, Memory Stick, Compact Flash, etc.) can be inserted and removed.
  • processor 1510 can include multiple individual processors (including, e.g, multi-core processors), each of which implements a portion of the functionality described above. In such cases, multiple individual processors can be commonly connected to program memory 1520 and data memory 1530 or individually connected to multiple individual program memories and or data memories. More generally, persons of ordinary skill in the art will recognize that various protocols and other functions of UE 1500 can be implemented in many different computer arrangements comprising different combinations of hardware and software including, but not limited to, application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed and/or programmable digital circuitry, analog baseband circuitry, radio-frequency circuitry, software, firmware, and middleware.
  • Radio transceiver 1540 can include radio-frequency transmitter and/or receiver functionality that facilitates the UE 1500 to communicate with other equipment supporting like wireless communication standards and/or protocols.
  • the radio transceiver 1540 includes one or more transmitters and one or more receivers that enable UE 1500 to communicate according to various protocols and/or methods proposed for standardization by 3GPP and/or other standards bodies.
  • such functionality can operate cooperatively with processor 1510 to implement a PHY layer based on OFDM, OFDMA, and/or SC-FDMA technologies, such as described herein with respect to other figures.
  • radio transceiver 1540 includes one or more transmitters and one or more receivers that can facilitate the UE 1500 to communicate with various LTE, LTE- Advanced (LTE- A), and/or NR networks according to standards promulgated by 3 GPP.
  • the radio transceiver 1540 includes circuitry, firmware, etc. necessary for the UE 1500 to communicate with various NR, NR-U, LTE, LTE- A, LTE-LAA, UMTS, and/or GSM/EDGE networks, also according to 3GPP standards.
  • radio transceiver 1540 can include circuitry supporting D2D communications between UE 1500 and other compatible devices.
  • radio transceiver 1540 includes circuitry, firmware, etc. necessary for the UE 1500 to communicate with various CDMA2000 networks, according to 3GPP2 standards.
  • the radio transceiver 1540 can be capable of communicating using radio technologies that operate in unlicensed frequency bands, such as IEEE 802.11 WiFi that operates using frequencies in the regions of 2.4, 5.6, and/or 60 GHz.
  • radio transceiver 1540 can include a transceiver that is capable of wired communication, such as by using IEEE 802.3 Ethernet technology.
  • the functionality particular to each of these embodiments can be coupled with and/or controlled by other circuitry in the UE 1500, such as the processor 1510 executing program code stored in program memory 1520 in conjunction with, and/or supported by, data memory 1530.
  • User interface 1550 can take various forms depending on the particular embodiment of UE 1500, or can be absent from UE 1500 entirely.
  • user interface 1550 can comprise a microphone, a loudspeaker, slidable buttons, depressible buttons, a display, a touchscreen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and/or any other user-interface features commonly found on mobile phones.
  • the UE 1500 can comprise a tablet computing device including a larger touchscreen display.
  • one or more of the mechanical features of the user interface 1550 can be replaced by comparable or functionally equivalent virtual user interface features (e.g ., virtual keypad, virtual buttons, etc.) implemented using the touchscreen display, as familiar to persons of ordinary skill in the art.
  • the UE 1500 can be a digital computing device, such as a laptop computer, desktop computer, workstation, etc. that comprises a mechanical keyboard that can be integrated, detached, or detachable depending on the particular exemplary embodiment.
  • a digital computing device can also comprise a touch screen display.
  • Many exemplary embodiments of the UE 1500 having a touch screen display are capable of receiving user inputs, such as inputs related to exemplary methods described herein or otherwise known to persons of ordinary skill.
  • UE 1500 can include an orientation sensor, which can be used in various ways by features and functions of UE 1500.
  • the UE 1500 can use outputs of the orientation sensor to determine when a user has changed the physical orientation of the UE 1500’s touch screen display.
  • An indication signal from the orientation sensor can be available to any application program executing on the UE 1500, such that an application program can change the orientation of a screen display (e.g., from portrait to landscape) automatically when the indication signal indicates an approximate 90-degree change in physical orientation of the device.
  • the application program can maintain the screen display in a manner that is readable by the user, regardless of the physical orientation of the device.
  • the output of the orientation sensor can be used in conjunction with various exemplary embodiments of the present disclosure.
  • a control interface 1560 of the UE 1500 can take various forms depending on the particular exemplary embodiment of UE 1500 and of the particular interface requirements of other devices that the UE 1500 is intended to communicate with and/or control.
  • the control interface 1560 can comprise an RS-232 interface, aUSB interface, an HDMI interface, a Bluetooth interface, an IEEE (“Firewire”) interface, an I 2 C interface, a PCMCIA interface, or the like.
  • control interface 1560 can comprise an IEEE 802.3 Ethernet interface such as described above.
  • the control interface 1560 can comprise analog interface circuitry including, for example, one or more digital-to-analog converters (DACs) and/or analog-to-digital converters (ADCs).
  • DACs digital-to-analog converters
  • ADCs analog-to-digital converters
  • the UE 1500 can comprise more functionality than is shown in Figure 15 including, for example, a video and/or still-image camera, microphone, media player and/or recorder, etc.
  • radio transceiver 1540 can include circuitry necessary to communicate using additional radio-frequency communication standards including Bluetooth, GPS, and/or others.
  • the processor 1510 can execute software code stored in the program memory 1520 to control such additional functionality.
  • directional velocity and/or position estimates output from a GPS receiver can be available to any application program executing on the UE 1500, including any program code corresponding to and/or embodying any exemplary embodiments ( e.g ., of methods) described herein.
  • FIG 16 shows a block diagram of an exemplary network node 1600 according to various embodiments of the present disclosure, including those described above with reference to other figures.
  • exemplary network node 1600 can be configured by execution of instructions, stored on a computer-readable medium, to perform operations corresponding to one or more of the exemplary methods described herein.
  • network node 1600 can comprise a base station, eNB, gNB, or one or more components thereof.
  • network node 1600 can be configured as a central unit (CU) and one or more distributed units (DUs) according to NR gNB architectures specified by 3GPP. More generally, the functionally of network node 1600 can be distributed across various physical devices and/or functional units, modules, etc.
  • CU central unit
  • DUs distributed units
  • Network node 1600 can include processor 1610 (also referred to as “processing circuitry”) that is operably connected to program memory 1620 and data memory 1630 via bus 1670, which can include parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art.
  • processor 1610 also referred to as “processing circuitry”
  • bus 1670 can include parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art.
  • Program memory 1620 can store software code, programs, and/or instructions (collectively shown as computer program product 1621 in Figure 16) that, when executed by processor 1610, can configure and/or facilitate network node 1600 to perform various operations, including operations corresponding to various exemplary methods described herein.
  • program memory 1620 can also include software code executed by processor 1610 that can configure and/or facilitate network node 1600 to communicate with one or more other UEs or network nodes using other protocols or protocol layers, such as one or more of the PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS layer protocols standardized by 3 GPP for LTE, LTE-A, and/or NR, or any other higher-layer protocols utilized in conjunction with radio network interface 1640 and/or core network interface 1650.
  • core network interface 1650 can comprise the SI or NG interface and radio network interface 1640 can comprise the Uu interface, as standardized by 3 GPP.
  • Program memory 1620 can also comprise software code executed by processor 1610 to control the functions of network node 1600, including configuring and controlling various components such as radio network interface 1640 and core network interface 1650.
  • Data memory 1630 can comprise memory area for processor 1610 to store variables used in protocols, configuration, control, and other functions of network node 1600.
  • program memory 1620 and data memory 1630 can comprise non-volatile memory (e.g ., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g, “cloud”) storage, or a combination thereof.
  • processor 1610 can include multiple individual processors (not shown), each of which implements a portion of the functionality described above. In such case, multiple individual processors may be commonly connected to program memory 1620 and data memory 1630 or individually connected to multiple individual program memories and/or data memories.
  • network node 1600 may be implemented in many different combinations of hardware and software including, but not limited to, application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed digital circuitry, programmable digital circuitry, analog baseband circuitry, radio-frequency circuitry, software, firmware, and middleware.
  • Radio network interface 1640 can comprise transmitters, receivers, signal processors, ASICs, antennas, beamforming units, and other circuitry that enables network node 1600 to communicate with other equipment such as, in some embodiments, a plurality of compatible user equipment (UE). In some embodiments, interface 1640 can also enable network node 1600 to communicate with compatible satellites of a satellite communication network. In some exemplary embodiments, radio network interface 1640 can comprise various protocols or protocol layers, such as the PHY, MAC, RLC, PDCP, and/or RRC layer protocols standardized by 3GPP for LTE, LTE-A, LTE-LAA, NR, NR-U, etc.
  • the radio network interface 1640 can comprise a PHY layer based on OFDM, OFDMA, and/or SC-FDMA technologies.
  • the functionality of such a PHY layer can be provided cooperatively by radio network interface 1640 and processor 1610 (including program code in memory 1620).
  • Core network interface 1650 can comprise transmitters, receivers, and other circuitry that enables network node 1600 to communicate with other equipment in a core network such as, in some embodiments, circuit-switched (CS) and/or packet-switched Core (PS) networks.
  • core network interface 1650 can comprise the SI interface standardized by 3GPP.
  • core network interface 1650 can comprise the NG interface standardized by 3GPP.
  • core network interface 1650 can comprise one or more interfaces to one or more AMFs, SMFs, SGWs, MMEs, SGSNs, GGSNs, and other physical devices that comprise functionality found in GERAN, UTRAN, EPC, 5GC, and CDMA2000 core networks that are known to persons of ordinary skill in the art. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface.
  • lower layers of core network interface 1650 can comprise one or more of asynchronous transfer mode (ATM), Internet Protocol (IP)-over-Ethemet, SDH over optical fiber, T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • ATM asynchronous transfer mode
  • IP Internet Protocol
  • SDH over optical fiber
  • T1/E1/PDH over a copper wire
  • microwave radio or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • network node 1600 can include hardware and/or software that configures and/or facilitates network node 1600 to communicate with other network nodes in a RAN, such as with other eNBs, gNBs, ng-eNBs, en-gNBs, IAB nodes, etc.
  • Such hardware and/or software can be part of radio network interface 1640 and/or core network interface 1650, or it can be a separate functional unit (not shown).
  • such hardware and/or software can configure and/or facilitate network node 1600 to communicate with other RAN nodes via the X2 or Xn interfaces, as standardized by 3 GPP.
  • OA&M interface 1660 can comprise transmitters, receivers, and other circuitry that enables network node 1600 to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of network node 1600 or other network equipment operably connected thereto.
  • Lower layers of OA&M interface 1660 can comprise one or more of asynchronous transfer mode (ATM), Internet Protocol (IP)-over- Ethemet, SDH over optical fiber, T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • ATM asynchronous transfer mode
  • IP Internet Protocol
  • SDH over optical fiber
  • T1/E1/PDH over optical fiber
  • T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • radio network interface 1640, core network interface 1650, and OA&M interface 1660 may be multiplexed together on a single physical interface, such as the examples listed above.
  • FIG 17 is a block diagram of an exemplary communication network configured to provide over-the-top (OTT) data services between a host computer and a user equipment (UE), according to one or more exemplary embodiments of the present disclosure.
  • UE 1710 can communicate with radio access network (RAN) 1730 over radio interface 1720, which can be based on protocols described above including, e.g., LTE, LTE-A, and 5G/NR.
  • RAN radio access network
  • UE 1710 can be configured and/or arranged as shown in other figures discussed above.
  • RAN 1730 can include one or more network nodes (e.g, base stations, eNBs, gNBs, controllers, etc.) operable in licensed spectrum bands, as well one or more network nodes operable in unlicensed spectrum (using, e.g, LAA or NR-U technology), such as a 2.4-GHz band and/or a 5-GHz band. In such cases, the network nodes comprising RAN 1730 can cooperatively operate using licensed and unlicensed spectrum.
  • RAN 1730 can include, or be capable of communication with, one or more satellites comprising a satellite access network.
  • RAN 1730 can further communicate with core network 1740 according to various protocols and interfaces described above.
  • one or more apparatus e.g ., base stations, eNBs, gNBs, ng-eNBs, etc.
  • RAN 1730 and core network 1740 can be configured and/or arranged as shown in other figures discussed above.
  • eNBs comprising an evolved UTRAN (E-UTRAN) 1730 can communicate with an evolved packet core (EPC) network 1740 via an SI interface.
  • EPC evolved packet core
  • gNBs and ng- eNBs comprising an NG-RAN 1730 can communicate with a 5GC network 1730 via an NG interface.
  • Core network 1740 can further communicate with an external packet data network, illustrated in Figure 17 as Internet 1750, according to various protocols and interfaces known to persons of ordinary skill in the art. Many other devices and/or networks can also connect to and communicate via Internet 1750, such as exemplary host computer 1760.
  • host computer 1760 can communicate with UE 1710 using Internet 1750, core network 1740, and RAN 1730 as intermediaries.
  • Host computer 1760 can be a server (e.g., an application server) under ownership and/or control of a service provider.
  • Host computer 1760 can be operated by the OTT service provider or by another entity on the service provider’s behalf.
  • host computer 1760 can provide an over-the-top (OTT) packet data service to UE 1710 using facilities of core network 1740 and RAN 1730, which can be unaware of the routing of an outgoing/incoming communication to/from host computer 1760.
  • host computer 1760 can be unaware of routing of a transmission from the host computer to the UE, e.g, the routing of the transmission through RAN 1730.
  • OTT services can be provided using the exemplary configuration shown in Figure 17 including, e.g, streaming (unidirectional) audio and/or video from host computer to UE, interactive (bidirectional) audio and/or video between host computer and UE, interactive messaging or social communication, interactive virtual or augmented reality, cloud gaming, etc.
  • the exemplary network shown in Figure 17 can also include measurement procedures and/or sensors that monitor network performance metrics including data rate, latency and other factors that are improved by exemplary embodiments disclosed herein.
  • the exemplary network can also include functionality for reconfiguring the link between the endpoints (e.g, host computer and UE) in response to variations in the measurement results.
  • Such procedures and functionalities are known and practiced; if the network hides or abstracts the radio interface from the OTT service provider, measurements can be facilitated by proprietary signaling between the UE and the host computer.
  • the exemplary embodiments described herein provide flexible and efficient techniques to dynamically activate, deactivate, and/or modify a pre-configured resource allocation (e.g., CG/SPS) for a one or more UEs, such as a group of ElEs.
  • a pre-configured resource allocation e.g., CG/SPS
  • Such techniques can be more spectrally efficient than conventional CG/SPS, by allowing a group of EEs to share a single periodic grant or allocation. Since each EE’s traffic pattern is irregular, the spectral resources needed to meet application latency requirements are less than if each EE was allocated independent periodic resources.
  • Embodiments also require less signaling overhead compare to conventional dynamic resource allocation.
  • NR EEs e.g., EE 1710
  • gNBs e.g, gNBs comprising RAN 1730
  • these improvements can increase the use of OTT data services - including XR applications - by providing better QoE to OTT service providers and end users. Consequently, this increases the benefits and/or value of such data services to end users and OTT service providers.
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor.
  • functionality of a device or apparatus can be implemented by any combination of hardware and software.
  • a device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other.
  • devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation comprennent des procédés destinés à un équipement d'utilisateur (UE) fonctionnant dans un réseau d'accès radioélectrique (RAN) en tant qu'un UE d'un groupe d'UE. De tels procédés consistent à recevoir une attribution de ressources de groupe pour le groupe d'UE, pour transmettre ou pour recevoir des données dans le RAN. L'attribution de ressources de groupe implique des ressources à une pluralité d'occasions. De tels procédés consistent également à recevoir une ou plusieurs indications d'activation indiquant si l'attribution de ressources de groupe est activée ou désactivée pour une utilisation par au moins l'UE. Chaque indication particulière d'activation est associée à toutes les occasions ultérieures à l'indication particulière d'activation. D'autres modes de réalisation comprennent des procédés complémentaires pour un nœud de RAN, ainsi que des UE et des nœuds de RAN configurés pour exécuter ces procédés.
PCT/SE2021/050238 2021-03-18 2021-03-18 Attribution semi-persistante à ue multiples Ceased WO2022197223A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2021/050238 WO2022197223A1 (fr) 2021-03-18 2021-03-18 Attribution semi-persistante à ue multiples

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2021/050238 WO2022197223A1 (fr) 2021-03-18 2021-03-18 Attribution semi-persistante à ue multiples

Publications (1)

Publication Number Publication Date
WO2022197223A1 true WO2022197223A1 (fr) 2022-09-22

Family

ID=75173425

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2021/050238 Ceased WO2022197223A1 (fr) 2021-03-18 2021-03-18 Attribution semi-persistante à ue multiples

Country Status (1)

Country Link
WO (1) WO2022197223A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240073886A1 (en) * 2021-03-18 2024-02-29 Telefonaktiebolaget Lm Ericsson (Publ) Pre-Configured Allocation for Non-Periodic Traffic Pattern
WO2024143940A1 (fr) * 2022-12-28 2024-07-04 삼성전자 주식회사 Procédé et station de base pour attribution de ressources sans fil

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180295651A1 (en) * 2017-04-06 2018-10-11 Huawei Technologies Co., Ltd. Flexible Grant-Free Resource Configuration Signaling

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180295651A1 (en) * 2017-04-06 2018-10-11 Huawei Technologies Co., Ltd. Flexible Grant-Free Resource Configuration Signaling

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "On support of non-integer multiple of CG/SPS periodicities", vol. RAN WG2, no. Reno, U.S.; 20191118 - 20191122, 7 November 2019 (2019-11-07), XP051815734, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_108/Docs/R2-1914750.zip R2-1914750> [retrieved on 20191107] *
PANASONIC: "Discussion on URLLC enhancements for grant-free transmission", vol. RAN WG1, no. Prague, CZ; 20190826 - 20190830, 16 August 2019 (2019-08-16), XP051765409, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_98/Docs/R1-1908801.zip> [retrieved on 20190816] *
ZTE ET AL: "Consideration on CG Confirmation MAC CE in case that multiple CG for a given BWP", vol. RAN WG2, no. Prague, Czech Republic; 20190826 - 20190830, 16 August 2019 (2019-08-16), XP051768176, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_107/Docs/R2-1910397.zip> [retrieved on 20190816] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240073886A1 (en) * 2021-03-18 2024-02-29 Telefonaktiebolaget Lm Ericsson (Publ) Pre-Configured Allocation for Non-Periodic Traffic Pattern
US12484046B2 (en) * 2021-03-18 2025-11-25 Telefonaktiebolaget Lm Ericsson (Publ) Pre-configured allocation for non-periodic traffic pattern
WO2024143940A1 (fr) * 2022-12-28 2024-07-04 삼성전자 주식회사 Procédé et station de base pour attribution de ressources sans fil

Similar Documents

Publication Publication Date Title
US20250184043A1 (en) Hybrid Automatic Repeat Request (HARQ) Mechanism for Multicast in NR
KR102553624B1 (ko) 다수의 뉴멀러지들을 위한 harq 절차를 관리하는 방법 및 사용자 장비(ue)
CN113287360B (zh) 用于nr用户设备的选择性跨时隙调度
JP7533667B2 (ja) 通信システム
US9295040B2 (en) Packet scheduling in communications
CN109997329B (zh) 用于harq定时配置的同步控制的系统和方法
US12381660B2 (en) Transport block repetition with multiple uplink configured grant configurations
US10098122B2 (en) System and method for resource allocation for device-to-device communications
JP2022526707A (ja) ネットワークノード、ユーザ装置（ｕｅ）、及びネットワークノードによるｕｅのスケジューリングのための関連する方法
US12041647B2 (en) Method and device for determining and configuring scheduling request resource, and storage medium
TWI865650B (zh) 用於處理多個通道的方法
WO2018036433A1 (fr) Procédés et dispositifs de transmission et de réception d&#39;informations, station de base et terminal
WO2018028269A1 (fr) Procédé et dispositif de planification de ressource
US9648599B2 (en) System and method for avoiding collisions between open discovery and cellular resources
CN115720132A (zh) 利用无线通信网络中的短传输时间间隔的方法及装置
EP4278766B1 (fr) Contrôle d&#39;encombrement pour des transmissions de liaison latérale
CN116566560A (zh) 信令传输方法、装置及存储介质
US20240172321A1 (en) Methods, Node, UE and Computer Readable Media for Aligning Partial Sensing Configuration with DRX Configuration
US12484046B2 (en) Pre-configured allocation for non-periodic traffic pattern
WO2021262071A1 (fr) Demande de répétition automatique (arq) hybride (harq) améliorée pour un réseau sans fil
WO2022197223A1 (fr) Attribution semi-persistante à ue multiples
US10455567B2 (en) Methods and nodes for controlling uplink transmissions
US20240187143A1 (en) Logical Channel Prioritization within Configured Grants

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21714031

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21714031

Country of ref document: EP

Kind code of ref document: A1