[go: up one dir, main page]

WO2021232306A1 - Charges utiles multi-utilisateurs semi-persistantes - Google Patents

Charges utiles multi-utilisateurs semi-persistantes Download PDF

Info

Publication number
WO2021232306A1
WO2021232306A1 PCT/CN2020/091366 CN2020091366W WO2021232306A1 WO 2021232306 A1 WO2021232306 A1 WO 2021232306A1 CN 2020091366 W CN2020091366 W CN 2020091366W WO 2021232306 A1 WO2021232306 A1 WO 2021232306A1
Authority
WO
WIPO (PCT)
Prior art keywords
header
user
payload
semi
dci
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/CN2020/091366
Other languages
English (en)
Inventor
Changlong Xu
Jing Sun
Xiaoxia Zhang
Tao Luo
Peter Gaal
Juan Montojo
Yisheng Xue
Chih-Hao Liu
Mostafa KHOSHNEVISAN
Ozcan Ozturk
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.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2020/091366 priority Critical patent/WO2021232306A1/fr
Publication of WO2021232306A1 publication Critical patent/WO2021232306A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

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 technology discussed below relates generally to wireless communication and, more particularly, to communication that uses semi-persistent multi-user payloads.
  • Next-generation wireless communication systems may include a 5G core network and a 5G radio access network (RAN) , such as a New Radio (NR) -RAN.
  • the NR-RAN supports communication via one or more cells.
  • a wireless communication device such as a user equipment (UE) may access a first cell of a first base station (BS) such as a gNB and/or access a second cell of a second base station.
  • BS base station
  • gNB gNode B
  • a base station may schedule access to a cell to support access by multiple UEs. For example, a base station may allocate different resources (e.g., time domain and frequency domain resources) for different UEs operating within a cell of the base station.
  • resources e.g., time domain and frequency domain resources
  • a base station may use semi-persistent scheduling (SPS) to schedule transmissions of multi-user packets during multiple SPS occasions.
  • SPS semi-persistent scheduling
  • each multi-user packet may include aggregated payloads for different users (e.g., different wireless communication devices) .
  • each multi-user packet may include a header with several sub-headers, where each sub-header identifies a corresponding user that has a payload in the multi-user packet.
  • the base station may transmit downlink control information (DCI) that indicates that multi-user packets are scheduled for semi-persistent transmission.
  • this DCI may be scrambled with a radio network temporary identifier (RNTI) that is designated for multi-user SPS traffic.
  • RNTI radio network temporary identifier
  • the base station may provide this RNTI to a group of users to enable the users to receive multi-user packets according to the SPS.
  • An SPS transmission may be activated in different ways in different examples.
  • a UE determines that an SPS transmission is activated upon receipt of a DCI encoded with a multi-user SPS RNTI.
  • a UE determines that an SPS transmission is activated upon receipt of a DCI encoded with a multi-user SPS RNTI along with a multi-user payload sub-header that identifies the UE.
  • An SPS transmission may be deactivated in different ways in different examples.
  • a UE determines that an SPS transmission is deactivated upon receipt of a DCI encoded with a multi-user SPS RNTI that indicates deactivation of the SPS transmission.
  • a UE determines that an SPS transmission is deactivated for that UE upon receipt of a DCI encoded with a multi-user SPS RNTI along with a multi-user payload sub-header that identifies the UE.
  • the sub-header may indicate that the SPS transmission is being deactivated for that UE.
  • a base station may dynamically change the payload allocation for different SPS occasions. For example, the base station may indicate in the sub-headers for one SPS occasion that the corresponding multi-user transmission includes a first payload for a first UE and a second payload for a second UE. The base station may then indicate in the sub-headers for a subsequent SPS occasion that the corresponding multi-user transmission includes, for example, a first payload for the second UE and a second payload for a third UE.
  • the payload allocation may remain static for several SPS occasions (e.g., for all SPS allocations of a given activation of SPS) .
  • the base station might only send a single header (e.g., in conjunction with SPS activation) to indicate which UEs will be served by the SPS and to indicate where the payload for a given UE will be located in all of the SPS occasions.
  • a method of wireless communication at a wireless communication device may include receiving a first downlink control information (DCI) indicating a periodicity between a plurality of semi-persistent transmission occasions for a plurality of multi-user payloads.
  • the plurality of multi-user payloads may include a first multi-user payload including a first payload for a first user and a second payload for a second user.
  • the method may also include determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after receiving the first DCI and selectively receiving the first multi-user payload after determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • a wireless communication device may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory.
  • the processor and the memory may be configured to receive a first downlink control information (DCI) indicating a periodicity between a plurality of semi-persistent transmission occasions for a plurality of multi-user payloads via the transceiver.
  • DCI downlink control information
  • the plurality of multi-user payloads may include a first multi-user payload including a first payload for a first user and a second payload for a second user.
  • the processor and the memory may also be configured to determine whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after receiving the first DCI and selectively receive the first multi-user payload via the transceiver after determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • a wireless communication device may include means for receiving a first downlink control information (DCI) indicating a periodicity between a plurality of semi-persistent transmission occasions for a plurality of multi-user payloads.
  • the plurality of multi-user payloads may include a first multi-user payload including a first payload for a first user and a second payload for a second user.
  • the wireless communication device may also include means for determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after receiving the first DCI and means for selectively receiving the first multi-user payload after determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • an article of manufacture for use by a wireless communication device includes a computer-readable medium having stored therein instructions executable by one or more processors of the wireless communication device to receive a first downlink control information (DCI) indicating a periodicity between a plurality of semi-persistent transmission occasions for a plurality of multi-user payloads.
  • the plurality of multi-user payloads may include a first multi-user payload including a first payload for a first user and a second payload for a second user.
  • the computer-readable medium may also have stored therein instructions executable by one or more processors of the wireless communication device to determine whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after receiving the first DCI and selectively receive the first multi-user payload after determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • a method of wireless communication at a base station may include generating a first downlink control information (DCI) indicating a periodicity between a plurality of semi-persistent transmission occasions for a plurality of multi-user payloads, transmitting the first DCI, and transmitting a first multi-user payload of the plurality of multi-user payloads during a first semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions.
  • the first multi-user payload may include a first payload for a first user and a second payload for a second user.
  • the method may also include transmitting a second multi-user payload of the plurality of multi-user payloads during a second semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions.
  • the second multi-user payload may include a third payload for the first user and a fourth payload for the second user.
  • a base station may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory.
  • the processor and the memory may be configured to generate a first downlink control information (DCI) indicating a periodicity between a plurality of semi-persistent transmission occasions for a plurality of multi-user payloads, transmit the first DCI via the transceiver, and transmit a first multi-user payload of the plurality of multi-user payloads during a first semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions via the transceiver.
  • the first multi-user payload may include a first payload for a first user and a second payload for a second user.
  • the processor and the memory may also be configured to transmit a second multi-user payload of the plurality of multi-user payloads during a second semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions via the transceiver.
  • the second multi-user payload may include a third payload for the first user and a fourth payload for the second user.
  • a base station may include means for generating a first downlink control information (DCI) indicating a periodicity between a plurality of semi-persistent transmission occasions for a plurality of multi-user payloads, first means for transmitting the first DCI, and second means for transmitting a first multi-user payload of the plurality of multi-user payloads during a first semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions.
  • the first multi-user payload may include a first payload for a first user and a second payload for a second user.
  • the second means for transmitting may also be for transmitting a second multi-user payload of the plurality of multi-user payloads during a second semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions.
  • the second multi-user payload may include a third payload for the first user and a fourth payload for the second user.
  • an article of manufacture for use by a base station includes a computer-readable medium having stored therein instructions executable by one or more processors of the base station to generate a first downlink control information (DCI) indicating a periodicity between a plurality of semi-persistent transmission occasions for a plurality of multi-user payloads, transmit the first DCI, and transmit a first multi-user payload of the plurality of multi-user payloads during a first semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions.
  • the first multi-user payload may include a first payload for a first user and a second payload for a second user.
  • the computer-readable medium may also have stored therein instructions executable by one or more processors of the base station to transmit a second multi-user payload of the plurality of multi-user payloads during a second semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions.
  • the second multi-user payload may include a third payload for the first user and a fourth payload for the second user.
  • FIG. 1 is a schematic illustration of a wireless communication system according to some aspects.
  • FIG. 2 is a conceptual illustration of an example of a radio access network according to some aspects.
  • FIG. 3 is a schematic illustration of wireless resources in an air interface utilizing orthogonal frequency divisional multiplexing (OFDM) according to some aspects.
  • OFDM orthogonal frequency divisional multiplexing
  • FIG. 4 is a diagram of an example of downlink channels according to some aspects.
  • FIG. 5 is a conceptual illustration of an example of downlink control information scheduling a multi-user packet according to some aspects.
  • FIG. 6 is a schematic illustration of a wireless communication system that communicates a multi-user packet according to some aspects.
  • FIG. 7 is a conceptual illustration of an example of downlink control information separately scheduling aggregated transport blocks and a header for the aggregated transport blocks according to some aspects.
  • FIG. 8 is a conceptual illustration of an example of semi-persistent scheduling (SPS) occasions according to some aspects.
  • FIG. 9 is a conceptual illustration of an example of SPS occasions for a multi-user communication according to some aspects.
  • FIG. 10 is a conceptual illustration of another example of SPS occasions for a multi-user communication according to some aspects.
  • FIG. 11 is a schematic illustration of a wireless communication system that performs acknowledgement-related operations for a multi-user packet according to some aspects of the disclosure.
  • FIG. 12 is a block diagram conceptually illustrating an example of a hardware implementation for a communication device employing a processing system according to some aspects of the disclosure.
  • FIG. 13 is a flow chart illustrating an example wireless communication process for a multi-user payload according to some aspects of the disclosure.
  • FIG. 14 is a block diagram conceptually illustrating an example of a hardware implementation for a communication device employing a processing system according to some aspects of the disclosure.
  • FIG. 15 is a flow chart illustrating an example wireless communication process for a multi-user payload according to some aspects of the disclosure.
  • Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations.
  • devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments.
  • transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) .
  • innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes and constitution.
  • the various concepts presented throughout this disclosure may be implemented across a broad variety of telecommunication systems, network architectures, and communication standards.
  • the wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and at least one scheduled entity 106.
  • the at least one scheduled entity 106 may be referred to as a user equipment (UE) 106 in the discussion that follows.
  • the RAN 104 includes at least one scheduling entity 108.
  • the at least one scheduling entity 108 may be referred to as a base station (BS) 108 in the discussion that follows.
  • the UE 106 may be enabled to carry out data communication with an external data network 110, such as (but not limited to) the Internet.
  • an external data network 110 such as (but not limited to) the Internet.
  • the RAN 104 may implement any suitable wireless communication technology or technologies to provide radio access to the UE 106.
  • the RAN 104 may operate according to 3 rd Generation Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G.
  • 3GPP 3 rd Generation Partnership Project
  • NR New Radio
  • the RAN 104 may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE.
  • eUTRAN Evolved Universal Terrestrial Radio Access Network
  • the 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN.
  • NG-RAN next-generation RAN
  • a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE.
  • a base station may variously be referred to by those skilled in the art as a base transceiver station (BTS) , a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , an access point (AP) , a Node B (NB) , an eNode B (eNB) , a gNode B (gNB) , or some other suitable terminology.
  • BTS base transceiver station
  • BSS basic service set
  • ESS extended service set
  • AP access point
  • NB Node B
  • eNB eNode B
  • gNB gNode B
  • the radio access network 104 is further illustrated supporting wireless communication for multiple mobile apparatuses.
  • a mobile apparatus may be referred to as user equipment (UE) in 3GPP standards, but may also be referred to by those skilled in the art as a mobile station (MS) , a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT) , a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.
  • a UE may be an apparatus that provides a user with access to network services.
  • a “mobile” apparatus need not necessarily have a capability to move, and may be stationary.
  • the term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies.
  • UEs may include a number of hardware structural components sized, shaped, and arranged to help in communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other.
  • a mobile apparatus examples include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC) , a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA) , and a broad array of embedded systems, e.g., corresponding to an “Internet of Things” (IoT) .
  • IoT Internet of Things
  • a mobile apparatus may additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player) , a camera, a game console, etc.
  • GPS global positioning system
  • a mobile apparatus may additionally be a digital home or smart home device such as a home audio, video, and/or multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc.
  • a mobile apparatus may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid) , lighting, water, etc.; an industrial automation and enterprise device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weaponry, etc.
  • a mobile apparatus may provide for connected medicine or telemedicine support, i.e., health care at a distance.
  • Telehealth devices may include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information, e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data.
  • Wireless communication between a RAN 104 and a UE 106 may be described as utilizing an air interface.
  • Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) may be referred to as downlink (DL) transmission.
  • DL downlink
  • the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station 108) .
  • Another way to describe this scheme may be to use the term broadcast channel multiplexing.
  • Uplink Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions.
  • UL uplink
  • the term uplink may refer to a point-to-point transmission originating at a scheduled entity (described further below; e.g., UE 106) .
  • a scheduling entity e.g., a base station 108 allocates resources for communication among some or all devices and equipment within its service area or cell.
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UEs 106, which may be scheduled entities, may utilize resources allocated by the scheduling entity 108.
  • Base stations 108 are not the only entities that may function as scheduling entities. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs) .
  • a scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106.
  • the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including the downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108.
  • the scheduled entity 106 is a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., a grant) , synchronization or timing information, or other control information from another entity in the wireless communication network such as the scheduling entity 108.
  • the uplink and/or downlink control information and/or traffic information may be time-divided into frames, subframes, slots, and/or symbols.
  • a symbol may refer to a unit of time that, in an orthogonal frequency division multiplexed (OFDM) waveform, carries one resource element (RE) per sub-carrier.
  • a slot may carry 7 or 14 OFDM symbols.
  • a subframe may refer to a duration of 1ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame.
  • OFDM orthogonal frequency division multiplexed
  • a slot may carry 7 or 14 OFDM symbols.
  • a subframe may refer to a duration of 1ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame.
  • these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and various time divisions of the waveform may have any suitable duration.
  • base stations 108 may include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system.
  • the backhaul 120 may provide a link between a base station 108 and the core network 102.
  • a backhaul network may provide interconnection between the respective base stations 108.
  • Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.
  • the core network 102 may be a part of the wireless communication system 100, and may be independent of the radio access technology used in the RAN 104.
  • the core network 102 may be configured according to 5G standards (e.g., 5GC) .
  • the core network 102 may be configured according to a 4G evolved packet core (EPC) , or any other suitable standard or configuration.
  • 5G standards e.g., 5GC
  • EPC 4G evolved packet core
  • FIG. 2 a schematic illustration of a RAN 200 is provided.
  • the RAN 200 may be the same as the RAN 104 described above and illustrated in FIG. 1.
  • the geographic area covered by the RAN 200 may be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted from one access point or base station.
  • FIG. 2 illustrates macrocells 202, 204, and 206, and a small cell 208, each of which may include one or more sectors (not shown) .
  • a sector is a sub- area of a cell. All sectors within one cell are served by the same base station.
  • a radio link within a sector can be identified by a single logical identification belonging to that sector.
  • the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell.
  • FIG. 2 two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206.
  • a base station can have an integrated antenna or can be connected to an antenna or RRH by feeder cables.
  • the cells 202, 204, and 206 may be referred to as macrocells, as the base stations 210, 212, and 214 support cells having a large size.
  • a base station 218 is shown in the small cell 208 (e.g., a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc.
  • the cell 208 may be referred to as a small cell, as the base station 218 supports a cell having a relatively small size.
  • Cell sizing can be done according to system design as well as component constraints.
  • the radio access network 200 may include any number of wireless base stations and cells. Further, a relay node may be deployed to extend the size or coverage area of a given cell.
  • the base stations 210, 212, 214, 218 provide wireless access points to a core network for any number of mobile apparatuses. In some examples, the base stations 210, 212, 214, and/or 218 may be the same as the base station/scheduling entity 108 described above and illustrated in FIG. 1.
  • the cells may include UEs that may be in communication with one or more sectors of each cell.
  • each base station 210, 212, 214, and 218 may be configured to provide an access point to a core network (e.g., as illustrated in FIG. 1) for all the UEs in the respective cells.
  • UEs 222 and 224 may be in communication with base station 210; UEs 226 and 228 may be in communication with base station 212; UEs 230 and 232 may be in communication with base station 214 by way of RRH 216; and UE 234 may be in communication with base station 218.
  • the UEs 222, 224, 226, 228, 230, 232, 234, 238, 240, and/or 242 may be the same as the UE/scheduled entity 106 described above and illustrated in FIG. 1.
  • an unmanned aerial vehicle (UAV) 220 which may be a drone or quadcopter, can be a mobile network node and may be configured to function as a UE.
  • the UAV 220 may operate within cell 202 by communicating with base station 210.
  • sidelink signals may be used between UEs without necessarily relying on scheduling or control information from a base station.
  • two or more UEs e.g., UEs 226 and 228, may communicate with each other using peer to peer (P2P) or sidelink signals 227 without relaying that communication through a base station (e.g., base station 212) .
  • P2P peer to peer
  • UE 238 is illustrated communicating with UEs 240 and 242.
  • the UE 238 may function as a scheduling entity or a primary sidelink device
  • UEs 240 and 242 may function as a scheduled entity or a non-primary (e.g., secondary) sidelink device.
  • a UE may function as a scheduling entity in a device-to-device (D2D) , peer-to-peer (P2P) , or vehicle-to-vehicle (V2V) network, and/or in a mesh network.
  • D2D device-to-device
  • P2P peer-to-peer
  • V2V vehicle-to-vehicle
  • UEs 240 and 242 may optionally communicate directly with one another in addition to communicating with the UE 238 (e.g., functioning as a scheduling entity) .
  • a scheduling entity and one or more scheduled entities may communicate utilizing the scheduled resources.
  • the sidelink signals 227 include sidelink traffic (e.g., a physical sidelink shared channel) and sidelink control (e.g., a physical sidelink control channel) .
  • the various physical channels between the UE and the radio access network are generally set up, maintained, and released under the control of an access and mobility management function (AMF) .
  • the AMF (not shown in FIG. 2) may include a security context management function (SCMF) that manages the security context for both the control plane and the user plane functionality, and a security anchor function (SEAF) that performs authentication.
  • SCMF security context management function
  • SEAF security anchor function
  • a radio access network 200 may utilize DL-based mobility or UL-based mobility to enable mobility and handovers (i.e., the transfer of a UE’s connection from one radio channel to another) .
  • a UE may monitor various parameters of the signal from its serving cell as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells.
  • the UE may undertake a handoff or handover from the serving cell to the neighboring (target) cell.
  • UE 224 illustrated as a vehicle, although any suitable form of UE may be used
  • the UE 224 may transmit a reporting message to its serving base station 210 indicating this condition.
  • the UE 224 may receive a handover command, and the UE may undergo a handover to the cell 206.
  • UL reference signals from each UE may be utilized by the network to select a serving cell for each UE.
  • the base stations 210, 212, and 214/216 may broadcast unified synchronization signals (e.g., unified Primary Synchronization Signals (PSSs) , unified Secondary Synchronization Signals (SSSs) and unified Physical Broadcast Channels (PBCH) ) .
  • PSSs Primary Synchronization Signals
  • SSSs unified Secondary Synchronization Signals
  • PBCH Physical Broadcast Channels
  • the UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and in response to deriving timing, transmit an uplink pilot or reference signal.
  • the uplink pilot signal transmitted by a UE may be concurrently received by two or more cells (e.g., base stations 210 and 214/216) within the radio access network 200.
  • Each of the cells may measure a strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214/216 and/or a central node within the core network) may determine a serving cell for the UE 224.
  • the radio access network e.g., one or more of the base stations 210 and 214/216 and/or a central node within the core network
  • the network may continue to monitor the uplink pilot signal transmitted by the UE 224.
  • the network 200 may handover the UE 224 from the serving cell to the neighboring cell, with or without informing the UE 224.
  • the synchronization signal transmitted by the base stations 210, 212, and 214/216 may be unified, the synchronization signal may not identify a particular cell, but rather may identify a zone of multiple cells operating on the same frequency and/or with the same timing.
  • the use of zones in 5G networks or other next generation communication networks enables the uplink-based mobility framework and improves the efficiency of both the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network may be reduced.
  • the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum.
  • Licensed spectrum provides for exclusive use of a portion of the spectrum, generally by virtue of a mobile network operator purchasing a license from a government regulatory body.
  • Unlicensed spectrum provides for shared use of a portion of the spectrum without need for a government-granted license. While compliance with some technical rules is generally still required to access unlicensed spectrum, generally, any operator or device may gain access.
  • Shared spectrum may fall between licensed and unlicensed spectrum, wherein technical rules or limitations may be required to access the spectrum, but the spectrum may still be shared by multiple operators and/or multiple RATs.
  • the holder of a license for a portion of licensed spectrum may provide licensed shared access (LSA) to share that spectrum with other parties, e.g., with suitable licensee-determined conditions to gain access.
  • LSA licensed shared access
  • the air interface in the radio access network 200 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices.
  • 5G NR specifications provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and for multiplexing for DL transmissions from base station 210 to one or more UEs 222 and 224, utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) .
  • OFDM orthogonal frequency division multiplexing
  • CP cyclic prefix
  • 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA) ) .
  • DFT-s-OFDM discrete Fourier transform-spread-OFDM
  • SC-FDMA single-carrier FDMA
  • multiplexing and multiple access are not limited to the above schemes, and may be provided utilizing time division multiple access (TDMA) , code division multiple access (CDMA) , frequency division multiple access (FDMA) , sparse code multiple access (SCMA) , resource spread multiple access (RSMA) , or other suitable multiple access schemes.
  • multiplexing DL transmissions from the base station 210 to UEs 222 and 224 may be provided utilizing time division multiplexing (TDM) , code division multiplexing (CDM) , frequency division multiplexing (FDM) , orthogonal frequency division multiplexing (OFDM) , sparse code multiplexing (SCM) , or other suitable multiplexing schemes.
  • the air interface in the radio access network 200 may further utilize one or more duplexing algorithms.
  • Duplex refers to a point-to-point communication link where both endpoints can communicate with one another in both directions.
  • Full duplex means both endpoints can simultaneously communicate with one another.
  • Half duplex means only one endpoint can send information to the other at a time.
  • a full duplex channel generally relies on physical isolation of a transmitter and receiver, and suitable interference cancelation technologies.
  • Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD) .
  • FDD frequency division duplex
  • TDD time division duplex
  • transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, at some times the channel is dedicated for transmissions in one direction, while at other times the channel is dedicated for transmissions in the other direction, where the direction may change very rapidly, e.g., several times per slot.
  • FIG. 3 an expanded view of an example DL subframe (SF) 302A is illustrated, showing an OFDM resource grid.
  • SF DL subframe
  • the PHY transmission structure for any particular application may vary from the example described here, depending on any number of factors.
  • time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of subcarriers.
  • the resource grid 304 may be used to schematically represent time–frequency resources for a given antenna port. That is, in a multiple-input-multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding multiple number of resource grids 304 may be available for communication.
  • the resource grid 304 is divided into multiple resource elements (REs) 306.
  • An RE which is 1 subcarrier ⁇ 1 symbol, is the smallest discrete part of the time–frequency grid, and contains a single complex value representing data from a physical channel or signal.
  • each RE may represent one or more bits of information.
  • a block of REs may be referred to as a physical resource block (PRB) or more simply a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain.
  • an RB may include 12 subcarriers, a number independent of the numerology used.
  • an RB may include any suitable number of consecutive OFDM symbols in the time domain.
  • Scheduling of UEs typically involves scheduling one or more resource elements 306 within one or more bandwidth parts (BWPs) , where each BWP includes two or more contiguous or consecutive RBs.
  • BWPs bandwidth parts
  • a UE generally utilizes only a subset of the resource grid 304.
  • an RB may be the smallest unit of resources that can be allocated to a UE.
  • the RB 308 is shown as occupying less than the entire bandwidth of the subframe 302A, with some subcarriers illustrated above and below the RB 308.
  • the subframe 302A may have a bandwidth corresponding to any number of one or more RBs 308.
  • the RB 308 is shown as occupying less than the entire duration of the subframe 302A, although this is merely one possible example.
  • Each 1 ms subframe 302A may consist of one or multiple adjacent slots.
  • one subframe 302B includes four slots 310, as an illustrative example.
  • a slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length.
  • CP cyclic prefix
  • a slot may include 7 or 14 OFDM symbols with a nominal CP.
  • Additional examples may include mini-slots having a shorter duration (e.g., one or two OFDM symbols) . These mini-slots may in some cases be transmitted occupying resources scheduled for ongoing slot transmissions for the same or for different UEs.
  • An expanded view of one of the slots 310 illustrates the slot 310 including a control region 312 and a data region 314.
  • the control region 312 may carry control channels (e.g., PDCCH)
  • the data region 314 may carry data channels (e.g., PDSCH or PUSCH) .
  • a slot may contain all DL, all UL, or at least one DL portion and at least one UL portion.
  • the structure illustrated in FIG. 3 is merely exemplary in nature, and different slot structures may be utilized, and may include one or more of each of the control region (s) and data region (s) .
  • the various REs 306 within a RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc.
  • Other REs 306 within the RB 308 may also carry pilots or reference signals, including but not limited to a demodulation reference signal (DMRS) or a sounding reference signal (SRS) .
  • DMRS demodulation reference signal
  • SRS sounding reference signal
  • pilots or reference signals may provide for a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation/detection of the control and/or data channels within the RB 308.
  • the transmitting device may allocate one or more REs 306 (e.g., within a control region 312) to carry DL control information including one or more DL control channels, such as a PBCH; a physical control format indicator channel (PCFICH) ; a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH) ; and/or a physical downlink control channel (PDCCH) , etc., to one or more scheduled entities.
  • DL control channels such as a PBCH; a physical control format indicator channel (PCFICH) ; a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH) ; and/or a physical downlink control channel (PDCCH) , etc.
  • the transmitting device may further allocate one or more REs 306 to carry other DL signals, such as a DMRS; a phase-tracking reference signal (PT-RS) ; a channel state information –reference signal (CSI-RS) ; a primary synchronization signal (PSS) ; and a secondary synchronization signal (SSS) .
  • a DMRS a DMRS
  • PT-RS phase-tracking reference signal
  • CSI-RS channel state information –reference signal
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • the synchronization signals PSS and SSS may be transmitted in a synchronization signal block (SSB) that includes 3 consecutive OFDM symbols, numbered via a time index in increasing order from 0 to 3.
  • SSB synchronization signal block
  • the SSB may extend over 240 contiguous subcarriers, with the subcarriers being numbered via a frequency index in increasing order from 0 to 239.
  • the present disclosure is not limited to this specific SSB configuration.
  • Nonlimiting examples may utilize greater or fewer than two synchronization signals; may include one or more supplemental channels in addition to the PBCH; may omit a PBCH; and/or may utilize a different number of symbols and/or nonconsecutive symbols for an SSB, within the scope of the present disclosure.
  • the PCFICH provides information to assist a receiving device in receiving and decoding the PDCCH.
  • the PDCCH may carry downlink control information (DCI) including but not limited to power control commands, scheduling information, a grant, and/or an assignment of REs for DL and UL transmissions.
  • DCI downlink control information
  • the PHICH carries HARQ feedback transmissions such as an acknowledgment (ACK) or negative acknowledgment (NACK) .
  • HARQ is a technique well-known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked at the receiving side for accuracy, e.g., utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC) .
  • CRC cyclic redundancy check
  • an ACK may be transmitted, whereas if not confirmed, a NACK may be transmitted.
  • the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc.
  • a BS may transmit synchronization signals (e.g., including PSS and SSS) in the network to enable UEs to synchronize with the BS, as well as SI (e.g., including a MIB, RMSI, and OSI) to facilitate initial network access.
  • the BS may transmit the PSS, the SSS, and/or the MIB via SSBs over PBCH and may broadcast the RMSI and/or the OSI over the PDSCH.
  • a UE attempting to access the network may perform an initial cell search by detecting a PSS from a BS (e.g., the PSS of a cell of the BS) .
  • the PSS may enable the UE to synchronize to period timing of the BS and may indicate a physical layer identity value assigned to the cell.
  • the UE may also receive an SSS from the BS that enables the UE to synchronize on the radio frame level with the cell.
  • the SSS may also provide a cell identity value, which the UE may combine with the physical layer identity value to identify the cell.
  • the UE may receive SI from the BS.
  • the SI may take the form of a master information block (MIB) and system information blocks (SIBs) .
  • the system information includes essential or critical information for a UE to access the network such as downlink (DL) channel configuration information, uplink (UL) channel configuration information, access class information, and cell barring information, as well as other less critical information.
  • the MIB may include system information for initial network access and scheduling information for RMSI and/or OSI.
  • the UE may receive RMSI and/or OSI.
  • the RMSI and/or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource set (CORESET) for physical downlink control channel (PDCCH) monitoring, physical uplink control channel (PUCCH) , physical uplink shared channel (PUSCH) , power control, and SRS.
  • RRC radio resource control
  • CORESET control resource set
  • PDCCH physical downlink control channel
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • SRS power control
  • SIB type one SIB1 provides scheduling information and/or availability of other SIB types and/or information (e.g., PLMN information and/or cell barring information) that can guide a UE in performing cell selection and/or cell reselection.
  • a UE may search for a suitable cell based on SIB1 information received from the BS.
  • SIB2 SIB type two
  • SIB3 SIB type three
  • SIB4 SIB type four
  • SIB5 SIB type five
  • the UE may perform a random access procedure for initial access to a RAN (e.g., the RAN 200 of FIG. 2) .
  • the RAN e.g., a base station
  • This information may include a configuration for a random access channel (RACH) that the UE uses to communicate with the RAN during initial access.
  • RACH random access channel
  • the RACH configuration may indicate, for example, the resources allocated by the RAN for the RACH.
  • the UE may transmit a random access preamble and the BS may respond with a random access response.
  • the UE may transmit a connection request to the BS and the BS may respond with a connection response (e.g., contention resolution message) .
  • a connection response e.g., contention resolution message
  • the UE and the BS may enter a normal operation stage, where operational data may be exchanged.
  • the BS may schedule the UE for UL communication and/or DL communication.
  • a UE under the coverage area of a RAN may operate in one of several defined operating states (also referred to as modes) .
  • these states include an idle state, an inactive state, and a connected state.
  • these operating states are defined as radio resource control (RRC) states: RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED.
  • RRC radio resource control
  • a UE will be in an idle state when it first powers up.
  • the UE may transition to a connected state with a RAN by performing a random access procedure with that RAN.
  • the UE may communicate with the RAN via dedicated signaling (e.g., dedicated channels) .
  • a UE may switch to idle state or inactive state under certain circumstances. For example, a UE that does not have data to send to the RAN and that is not receiving data from the RAN may elect to switch to the idle state or the inactive state to conserve battery power.
  • the UE since the UE is not actively communicating with the RAN, the UE may power off some of its components (e.g., radio components) . That is, the UE enters a lower power state.
  • the UE will periodically wake up from the low power state to monitor for signaling from the RAN (e.g., to determine whether the RAN has data to send to the UE) .
  • This periodicity is based on a discontinuous reception (DRX) cycle specified by the RAN.
  • DRX discontinuous reception
  • the RAN will page the UE according to the DRX cycle (i.e., during the time intervals when the UE periodically wakes up from the lower power state) .
  • the RAN sends a paging message via a paging channel (e.g., via a paging frame) .
  • the RAN may define different paging opportunities that can be used by different UEs to receive a paging message. That is, UEs remain in the lower power state until their own paging opportunities occur.
  • the use of different paging opportunities for different UEs allows the RAN to direct paging to a particular UE or a small subset of UEs. This reduces the likelihood that a UE will need to expend battery power to process paging that is directed to another UE.
  • the UE may resume full operations (e.g., turn on all radio components) and, if needed, reestablish a connected state with the RAN.
  • the RAN may configure a UE (e.g., via broadcast) with information that enables a UE to receive different types of messages. For example, the RAN may use different RNTIs to scramble different information sent to UEs. This enables a UE to ignore transmitted information (e.g., information transmitted using a different RNTI) that does not concern that UE.
  • An RNTI table specifies the RNTI values designated by the network as needed to transmit information over different channels. For example, the RAN may designate one of these values for a random access RNTI (RA-RNTI) , the RAN may designate another one of these values for a transmit power control RNTI (TPC-PUCCH-RNTI) , and so on.
  • a fixed RNTI value FFFE
  • P-RNTI paging message
  • the transmitting device may utilize one or more REs 306 to carry UL control information including one or more UL control channels, such as a physical uplink control channel (PUCCH) , to the scheduling entity.
  • UL control information may include a variety of packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions.
  • the UL control information may include a DMRS or SRS.
  • the control information may include a scheduling request (SR) , i.e., request for the scheduling entity to schedule uplink transmissions.
  • SR scheduling request
  • the scheduling entity may transmit downlink control information that may schedule resources for uplink packet transmissions.
  • UL control information may also include HARQ feedback, channel state feedback (CSF) , or any other suitable UL control information.
  • one or more REs 306 may be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as, for a DL transmission, a PDSCH; or for an UL transmission, a physical uplink shared channel (PUSCH) .
  • one or more REs 306 within the data region 314 may be configured to carry SIBs (e.g., SIB1) , carrying system information that may enable access to a given cell.
  • Transport channels carry blocks of information called transport blocks (TB) .
  • TBS transport block size
  • MCS modulation and coding scheme
  • channels or carriers described above with reference to FIGs. 1 -3 are not necessarily all of the channels or carriers that may be utilized between a scheduling entity and scheduled entities, and those of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.
  • FIG. 4 is a diagram 400 illustrating an example of DL channels within a 5G/NR subframe.
  • each slot may include 14 symbols.
  • a first arrowed line indicates a subset of the system bandwidth RBs 402 (e.g., a subset of the resource grid 304 of FIG. 3) .
  • the symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols in some examples.
  • a physical downlink control channel (PDCCH) 404 may carry a DCI within one or more control channel elements (CCEs) .
  • Each CCE may include nine resource element (RE) groups (REGs) , where each REG may include four consecutive REs in an OFDM symbol.
  • REGs resource element groups
  • a primary synchronization signal (PSS) 406 is shown in symbol 2 of the subframe.
  • the PSS 406 may be used by a UE to determine subframe/symbol timing and a physical layer identity.
  • a secondary synchronization signal (SSS) 408 is shown in symbol 4 of the subframe.
  • the SSS 408 may be used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DMRS.
  • PCI physical cell identifier
  • a physical broadcast channel (PBCH) 410 which carries a master information block (MIB) as discussed above, may be logically grouped with the PSS 406 and the SSS 408 to form an SS/PBCH block 412.
  • the MIB may indicate the number of RBs in the system bandwidth and a system frame number (SFN) .
  • SFN system frame number
  • the length of the SS/PBCH block 412 is 20 RBs 414 in this example.
  • a physical downlink shared channel (PDSCH) 416 carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.
  • the PDSCH 416 may carry a DCI (e.g., control-related information) in some examples. Transmitting a DCI in a PDSCH may be referred to as piggy-backing the DCI in the PDSCH.
  • a DCI may be transmitted in the PDSCH in situations where the PDCCH may not have adequate resources to carry all of the control-related information.
  • the coreset is reduced (e.g., when a base station is operating in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, etc. ) and cannot accommodate all of the control-related information.
  • the delivery of the control-related information in the PDSCH may be more efficient than transmitting the information in a PDCCH (where a UE may need to perform blind decoding on the DCI) .
  • a multi-user packet may include data for multiple users (e.g., UEs) multiplexed together in a combined payload of the packet.
  • UEs e.g., UEs
  • performance may be improved by aggregating the data in a multi-user packet as opposed to transmitting the data in a large number of small packets.
  • such aggregation or concatenation of data for multiple UEs in a multi-user packet may result in a better coding gain as compared to a scenario that transmits separate packets to the individual UEs.
  • downlink control overhead may be reduced in the aggregation scenario because downlink control information (DCI) may be transmitted only for the multi-user packet in this case instead of sending multiple DCIs for different packets sent to different UEs.
  • DCI downlink control information
  • the multi-user packet may be referred to herein as a multi-user PDSCH communication (MUPC) or, more briefly, a multi-user PDSCH (MUP) .
  • MUPC multi-user PDSCH communication
  • MUP multi-user PDSCH
  • FIG. 5 is a diagram illustrating an example of a multi-user packet 502.
  • a DCI 504 may schedule the transmission of the multi-user packet 502 (e.g., on a PDSCH) .
  • the multi-user packet 502 includes multiple payload portions that correspond to multiple UEs.
  • a first payload portion 506 e.g., at least one transport block, TB
  • a second payload portion 508 may carry data for a second UE (UE 1)
  • a third payload portion 510 may carry data for a third UE (UE 2) .
  • a multi-user packet may include a different number of payloads in other examples.
  • the multi-user packet 502 also includes a header 512 that includes, in turn, multiple sub-headers.
  • a sub-header may include a UE identifier that identifies a specific UE, such as a cell radio network temporary identifier (C-RNTI) or the like.
  • C-RNTI cell radio network temporary identifier
  • Different sub-headers may include different UE identifiers that identify different UEs. For example, a first sub-header (e.g., shown as sub-header h0) may identify a first UE, a second sub-header (e.g., shown as sub-header h1) may identify a second UE, a third sub-header (e.g., shown as sub-header h2) may identify a third UE.
  • different sub-headers of the multi-user packet 502 may correspond to different UEs.
  • a multi-user packet may include a different number of sub-headers in other examples.
  • a UE may determine whether the multi-user packet 502 includes data for that UE by decoding the packet to determine whether a sub-header includes a UE identifier for that UE. If there is such a UE identifier, the UE may identify a payload portion that corresponds to that sub-header. For example, each sub-header may include information that maps to (e.g., indicates a location of) a particular payload. For example, in FIG. 5, the sub-header h0 maps to the first payload portion 506 as represented by the dashed line 514. Once the UE identifies a payload portion that includes data intended for the UE, the UE may obtain the data included in that payload portion.
  • a sub-header may include a length field that indicates a length (e.g., a size, a number of bits, a number of bytes, and/or the like) of a corresponding payload portion. Additionally, or alternatively, a sub-header may include a field that indicates whether that sub-header is the last sub-header (e.g., a “last sub-header indicator” ) . One or more of these fields may be used to identify an end of the sub-headers and a start of the payload portions.
  • a UE may identify a start of a payload portion intended for the UE based at least in part on the start of the payload portions and a sum of all of the lengths indicated in sub-headers that occur before the sub-header that identifies the UE.
  • the UE may identify an end of the payload portion intended for the UE using the length indicated in the sub-header that identifies the UE.
  • FIG. 6 illustrates an example of multi-user packet communication 600 between a base station (BS) 602 and multiple UEs (e.g., a UE A 604) .
  • the UE 604 may correspond to one or more of the scheduled entity 106 (e.g., a UE, etc. ) of FIG. 1, or the UE 222, 224, 226, 228, 230, 232, 234, 238, 240, or 242 of FIG. 2.
  • the base station 602 may correspond to one or more of the scheduling entity 108 (e.g., a gNB, a transmit receive point, a UE, etc. ) of FIG. 1, or the base station 210, 212, 214, or 218 of FIG. 2.
  • the scheduling entity 108 e.g., a gNB, a transmit receive point, a UE, etc.
  • the base station 602 may generate a multi-user packet 606 that includes sub-headers and corresponding payload portions for multiple UEs (e.g., UE A 604 -UE X) .
  • the multi-user packet 606 may include a first sub-header (e.g., shown as “sub-header A” ) that identifies a first UE (e.g., using “UE ID A” ) and a corresponding payload portion (e.g., “payload portion A” ) for the first UE, a second sub-header (e.g., shown as “sub-header B” ) that identifies a second UE (e.g., using “UE ID B” ) and a corresponding payload portion (e.g., “payload portion B” ) for the second UE, and so on.
  • a first sub-header e.g., shown as “sub-header A”
  • a second sub-header e.g.
  • the base station 602 Prior to transmitting the multi-user packet 606, the base station 602 schedules the transmission and issues a DCI 608 that informs the UEs of the transmission.
  • the base station 602 may also schedule a set of PUCCH resources for ACK/NACK feedback from the target UEs for the multi-user packet 606 (e.g., UEs identified in the sub-headers of the multi-user packet 606 and/or UEs for which the multi-user packet 606 includes a payload portion) .
  • different PUCCH resources, in a set of PUCCH resources may be associated with different UEs.
  • the base station 602 may schedule a first PUCCH resource for a first UE, a second PUCCH resource for a second UE, and so on.
  • the base station 602 may transmit, and the UEs may receive, the multi-user packet 606 generated by the base station 602.
  • the multi-user packet 606 may include multiple sub-headers.
  • a UE may determine that a UE identifier of the UE (e.g., a C-RNTI, another type of RNTI, or the like) is included in a sub-header.
  • a UE may decode and read all of the sub-headers to determine whether any of the sub-headers include a UE identifier of that UE.
  • a UE may deliver (e.g., provide) the payload portion to an upper layer of the UE for processing (e.g., an application layer or the like) .
  • the UE may deliver only the payload portion intended for the UE, without delivering other payload portions, thereby conserving computing resources of the UE.
  • the UE may ignore (e.g., refrain from processing) one or more payload portions not intended for the UE, thereby conserving computing resources of the UE.
  • a UE may transmit an acknowledgment 610 to the base station 602 after decoding or attempting to decide a payload portion. For example, the UE may transmit a positive acknowledgement (e.g., an ACK) if the UE successfully decoded the payload portion. Otherwise, the UE may transmit a negative acknowledgement (e.g., a NACK) .
  • the base station 602 may send at least one retransmission 612 including at least one payload of the multi-user packet 606 (e.g., according to a HARQ process) .
  • a multi-user packet may be particularly useful for some types of traffic (e.g., IIoT traffic where the data packets are typically small) .
  • traffic e.g., IIoT traffic where the data packets are typically small
  • coding gain may be improved since multiple packets may be concatenated together across UEs into a single packet.
  • DL control overhead may be lower as well since one DL grant (e.g., DCI) may be sent for a group of UEs, instead of sending one grant per UE.
  • transport blocks (TBs) for multiple UEs may aggregated together and a PHY header added to the TBs to form an aggregated TB (also referred to herein as a combination TB, or a combo TB for short) .
  • the header includes several sub-headers, where each sub-header is for one UE.
  • a sub-header may carry UE-ID information and the range of (e.g., the location of or distance to) the user’s TB in the combo TB.
  • the combo TB may be carried in a PDSCH.
  • a DCI (e.g., with a group-RNTI) may be received by all of the UEs in the group, and the UEs may decode the DCI (e.g., using the group-RNTI) to determine whether there is a combo TB in a PDSCH. If the DCI indicates that there is a combo TB in a PDSCH, all of the UEs configured with the group-RNTI may decode the PDSCH.
  • a particular UE can determine whether it is being addressed and, if so, which part of the combo TB is for that UE.
  • the sub-headers may be sent separately from the combo TB.
  • the traffic e.g., TBs
  • the combo TB may be transmitted in a data channel (e.g., PDSCH) .
  • a header for the TBs includes several sub-headers, where each sub-header is for one UE.
  • a sub-header may carry UE-ID information and the range of (e.g., the location of or distance to) the user’s TB in the combo TB.
  • the header may be transmitted via a PDSCH or some other channel.
  • a BS may send a DCI (e.g., encoded with a group-RNTI) that can be received by all of the UEs in the group.
  • the DCI may indicate whether a PDSCH for the combo TB is scheduled and, if applicable, provide information regarding the header (e.g., information indicative of where the header is transmitted) .
  • a UE configured with the group-RNTI can decode the DCI to obtain the header information.
  • the UE can then parse the header to identify the sub-headers, and determine whether there is a sub-header that identifies that UE. That is, by parsing the header of the combo TB, a particular UE can determine whether it is being addressed and, if so, which part of the combo TB is for that UE. If a UE determines that the combo TB includes a payload for the UE, the UE may then attempt to decode that payload (e.g., by attempting to decode all or a portion of the combo TB) .
  • FIG. 7 is a diagram illustrating an example of a multi-user packet 702 in accordance with some aspects of the disclosure.
  • a downlink control information (DCI) 704 may schedule the transmission of the multi-user packet 702 (e.g., on a PDSCH) .
  • the DCI 704 may separately schedule the transmission of the header 706 for the multi-user packet 702 (e.g., on a PDSCH) .
  • the multi-user packet 702 includes multiple payload portions that correspond to multiple UEs.
  • a first payload portion 708 e.g., a transport block, TB
  • a second payload portion 710 may carry data for a second UE (UE 1)
  • a third payload portion 712 may carry data for a third UE (UE 2) .
  • a multi-user packet may include a different number of payloads in other examples.
  • the header 706 includes multiple sub-headers as discussed herein.
  • a first sub-header e.g., shown as sub-header h0
  • a second sub-header e.g., shown as sub-header h1
  • a third sub-header e.g., shown as sub-header h2
  • a multi-user packet may include a different number of sub-headers in other examples.
  • the DCI 704 may carry legacy information for PDSCH, including a frequency domain resource allocation (FDRA) , a time domain resource allocation (TDRA) , a HARQ process ID, a new data indicator (NDI) , a MCS, etc.
  • the DCI may also carry information about the header (e.g., in the PDSCH) . In some examples, this information is in the form of beta control and size control.
  • the size information may enable a degree of size control to adjust the size of the header depending on how many sub-headers there are in the header (e.g., to reduce or avoid zero padding in the header) .
  • Beta control can control the coding rate of the header for reliable delivery to all targeted UEs. Given this information, all of the UEs in the group can calculate how many resource elements (REs) are used for the header and locate those REs for its decoding.
  • REs resource elements
  • the DCI may target a specific group of UEs, all these UEs may be configured to decode the DCI using blind decoding (e.g., a type 3 common search space may be configured for this DCI monitoring) .
  • the header is polar encoded with a CRC.
  • the length of the CRC may be 24 bits in some examples, but may be shorter in other examples (e.g., 8 or 16 bits) when there is no blind decoding for the header.
  • the CRC can be unscrambled or scrambled with the group-RNTI, as all UEs that monitor for the header are configured to descramble the CRC.
  • each sub-header may contain one or more of the following information parameters.
  • a UE-ID identifies a UE. This UE-ID may be a C-RNTI or a shorter UE-ID. Payload location information indicates where in the combo TB a UE can locate a TB destined for the UE.
  • a PUCCH resource indicator may indicate resources for each UE to independently send an ACK/NACK (A/N) . If a sub-header PRI is used, the PRI in the DCI may be discarded or the PRI field may be repurposed for some other use.
  • Downlink assignment index (DAI) information (e.g., a counter and a total) may be included if a dynamic HARQ codebook is used. This field may take the same form as in the case where the UE is scheduled via a UE-specific DCI in a slot. If a sub-header DAI is used, the DAI in the DCI may be discarded or the DAI field may be repurposed for some other use.
  • a sub-header may include a K1 field to control the A/N reporting timing separately per UE. Alternatively, the common K1 field of the DCI in the PDCCH region may be used, whereby UEs will report A/N with this common K1-indicated timing.
  • a sub-header can change for each retransmissions (hence, the PRI and/or DAI information may be changed per sub-header) . It should be appreciated, however, that if a sub-header is in a combo TB and used for soft-combining based retransmission, the sub-header would generally not be changed in that scenario.
  • sub-headers can provide a per-UE TB size that enables the UEs to locate their respective content in the combo TB.
  • an MCS and resource allocation technique may be used calculate the total transport block size (TBS) (e.g., using a conventional TBS calculation) . As there may duplications from the two above procedures, some compression may be possible.
  • a network may configure a UE with a group-RNTI in addition to a C-RNTI.
  • a UE may monitor for a DCI using this group-RNTI. For example, the UE may perform blind decoding on the PDCCH (e.g., on a designated search space) . After detecting a DCI with a group-RNTI, the UE may perform another decoding (e.g., polar decoding) on the header.
  • another decoding e.g., polar decoding
  • the disclosure relates in some aspects to using semi-persistent scheduling (SPS) to schedule transmissions of multi-user payloads.
  • SPS semi-persistent scheduling
  • a base station may use SPS where a single DCI may schedule multiple transmissions (e.g., on PDSCH) .
  • an SPS DL can be configured and activated with the same DCI format as a DL grant, except that a configured scheduling (CS) RNTI (CS-RNTI) may be used for the SPS DL.
  • CS configured scheduling
  • a BS transmits an RRC message to configure an SPS (e.g., for a particular cell and a particular BWP) .
  • the base station may then send a DCI to activate the SPS.
  • the SPS configuration may indicate an SPS periodicity between SPS occasions. In this way, the SPS configuration may schedule multiple SPS occasions at the indicated periodicity.
  • the periodicity may be referenced to a system frame number (SFN) and a sub-frame number of the DCI that initializes the SPS.
  • SFN system frame number
  • a UE can monitor the PDSCH at the SPS occasions according to the scheduled SPS periodicity to periodically obtain data from the base station.
  • the base station may send a DCI to deactivate the SPS.
  • the base station may send a DCI to reactivate the SPS.
  • FIG. 8 is a conceptual illustration of an example of SPS occasions 800 according to some aspects of the disclosure.
  • Three SPS occasions 802, 804, and 806 are shown separated by a period of time T that is based on the configured SPS periodicity.
  • the SPS thus schedules a transmission (e.g., of DL traffic) at each SPS occasion, referenced to a starting time (e.g., the initializing DCI) as discussed above.
  • SPS may be used for the MUP techniques described herein.
  • a base station may use multi-user SPS if the base station needs to repeatedly send many small packets to a set of UEs. In some examples, this use case may apply where the transmissions of the small packets to the UEs are not necessarily periodic.
  • a base station may configure a specific RNTI to be used for multi-user SPS transmissions to a group of users. For examples, instead of or in addition to a group RNTI configured for a multi-user dynamic grant transmission (e.g., an MUP-RNTI for an MUP-PDSCH dynamic grant) , a base station may configure a multi-user SPS RNTI (e.g., a MUP-CS-RNTI for SPS DL transmission) .
  • a multi-user SPS RNTI e.g., a MUP-CS-RNTI for SPS DL transmission
  • the UE may determine that an MUP-PDSCH SPS is activated.
  • the SPS DL parameters may be indicated by the MUP-CS-RNTI DCI and/or a sub-header.
  • the DCI may include time domain resource allocation information, frequency domain resource allocation information, and other information as discussed herein.
  • a sub-header may include a UE-ID, TB location information, a PRI, and other information as discussed herein.
  • the UE may monitor the MUP-PDSCH directly in the subsequent SPS occasions that follow the configuration period.
  • the base station might not need to send another DCI for the SPS in the PDCCH region until the base station decides to terminate the SPS.
  • a base station may use a header with sub-headers that dynamically assign UEs to different shares of the payload.
  • a UE may monitor for these headers (e.g., in the MUP-PUSCH) during one or more SPS occasions to determine whether a combo TB of a particular SPS occasion includes a TB for the UE.
  • the UE may attempt to decode the combo TB and then send A/N information as appropriate (e.g., using the PRI resource information included in the sub-header as discussed above) . If a UE does not decode a sub-header that addresses the UE, the UE may treat the MUP-PDSCH as not addressing the UE, and therefore refrain from sending A/N information (e.g., in a PUCCH) . On the other hand, a UE may include A/N information in a dynamic codebook if triggered by the UE’s decoding of the PDSCH (e.g., one or more payloads of a combo TB) .
  • FIG. 9 is a conceptual illustration of an example of SPS occasions 900 for multi-user transmissions according to some aspects of the disclosure.
  • a base station (not shown) transmits a DCI 902 to activate an SPS for transmissions of combo TBs 904.
  • the base station may encode the DCI 902 based on an MUP-CS-RNTI as discussed herein.
  • the base station may polar encode the DCI 902 using CRC that is based on an MUP-CS-RNTI that the base station designated for a group of users that are to receive the transmissions of the combo TBs 904.
  • CRC CRC that is based on an MUP-CS-RNTI that the base station designated for a group of users that are to receive the transmissions of the combo TBs 904.
  • this RNTI a user of this group will be able to decode the DCI 902 to determine whether the base station has activated a multi-user SPS that may include a payload for the user.
  • the DCI 902 may indicate the SPS interval that defines the timing of SPS occasions.
  • the time at which the base station transmits the DCI 902 may be referred to as an activation time 906 for the SPS being activated by the DCI 902.
  • a second occasion 908 for the SPS may occur a period of time as specified by the SPS interval following the activation time 906.
  • a third occasion 910 for the SPS may occur a period of time as specified by the SPS interval following the second occasion 908.
  • the base station transmits a first combo TB based on the activation time 906 (e.g., during a PDSCH that follows the PDCCH that carries the DCI 902) .
  • the base station then transmits a second combo TB at the second occasion 908, transmits a third combo TB at the third occasion 910, and so on.
  • the base station transmits headers 912 in conjunction with the transmissions of the combo TBs 904.
  • the base station may transmit each header as part of a combo TB (e.g., encoded with the combo TB) as discussed above, for example, in conjunction with FIG. 5.
  • the base station may transmit a header separately from an associated combo TB as discussed above, for example, in conjunction with FIG. 7.
  • the base station may transmit a header in the same PDSCH as the associated combo TB.
  • a user may be able to determine at each SPS occasion whether the corresponding combo TB includes a payload for the user. For example, at the activation time 906, a UE of a user may decode the corresponding header to determine whether any of the sub-headers h0, h1, or h2 identifies the user. If so, the UE will attempt to decode that payload in the corresponding combo TB. Then, at the second occasion 908, the UE may decode the header at that occasion to determine whether any of the sub-headers h0, h1, or h2 identifies the user. If so, the UE will attempt to decode that payload in the corresponding combo TB for that occasion. This process may thus be repeated for each SPS occasion until the base station sends a DCI (not shown) that deactivates the SPS.
  • a DCI not shown
  • the base station may transmit different payloads for different users in different SPS occasions. For example, for the third occasion 910, the base station may transmit another DCI 902A that may indicate a change in the combo TBs 904. As a specific example, a fourth user (UE 3) may monitor the header for the third occasion 910 after decoding the DCI 902A. In this case, the header (e.g., sub-header h2) may indicate that the combo TB for this SPS occasion includes a TB for UE 3. The UE 3 may therefore attempt to decode that TB.
  • the header e.g., sub-header h2
  • the UE 3 may therefore attempt to decode that TB.
  • the disclosure relates in some aspects to techniques for activating an SPS. Several examples of these techniques follow.
  • an SPS is activated (e.g., a UE is activated for receiving an SPS transmission) if a UE receives a DCI that is encoded with an MUP-CS-RNTI.
  • a UE might only monitor for an MUP-CS-RNTI-based DCI (e.g., not monitor the sub-headers) to determine whether an SPS transmission is activated.
  • the UE may deem an SPS as activated even if the sub-headers for the corresponding combo TB do not identify (e.g., address) the UE. Consequently, the UE may commence monitoring the SPS occasions for payloads directed to the UE in this case.
  • an SPS is activated based on both MUP-CS-RNTI-based DCI detection and detection of a sub-header addressing the UE.
  • a UE detects an MUP-CS-RNTI-based DCI and also detects a sub-header addressing the UE, the UE will treat this as an activation. Consequently, the UE may commence monitoring the SPS occasions for payloads directed to the UE.
  • the UE may treat this as an activation for other UEs. Consequently, the UE might not monitor the SPS occasions in this case.
  • the first example and the second example may support activation of a new UE (or new UEs) to an existing MUP-PDSCH.
  • a base station may initially activate UE 0 and UE 1 in an MUP-PDSCH DL SPS. Then, in a subsequent SPS occasion, the base station may activate UE 2 and UE 3 in the same MUP-PDSCH DL SPS. At this point, UE 0, UE 1, UE 2, and UE 3 may each monitor the MUP-PDSCH DL SPS for a TB directed to that UE.
  • the techniques described above also may be used to reactivate an SPS DL. For example, after activating a configured SPS for a group of UEs, a base station may elect to deactivate the SPS (e.g., by transmitting a DCI that indicates that the SPS is being deactivated) at some point (e.g., if the base station no longer has data to send to the group of UEs) . Subsequently (e.g., if the base station again has data to send to the group of UEs) , the base station may use one or more of the above techniques to reactivate the SPS for the group of UEs.
  • deactivate the SPS e.g., by transmitting a DCI that indicates that the SPS is being deactivated
  • some point e.g., if the base station no longer has data to send to the group of UEs
  • the base station may use one or more of the above techniques to reactivate the SPS for the group of UE
  • a header might only be sent in conjunction with the initial transmission of a combo TB. That is, a header might not be sent in conjunction with subsequent SPS occasions.
  • the header may be considered as fixed. This implies that the UEs scheduled by the header will continue being scheduled in the same manner during subsequent SPS occasions.
  • an SPS DL with a MUP-PDSCH may involve not using a header in the MUP-PDSCH (e.g., after the initial activation) .
  • a base station may configure a specific RNTI to be used for multi-user SPS transmissions to a group of users.
  • a base station may configure a multi-user SPS RNTI (e.g., a MUP-CS-RNTI for SPS DL transmission) .
  • a UE may parse the associated header and determine whether a sub-header identifies the UE. If so, the UE may determine that an MUP-PDSCH SPS is activated.
  • the SPS DL parameters may be indicated by the MUP-CS-RNTI DCI and/or a sub-header.
  • the DCI may include time domain resource allocation information, frequency domain resource allocation information, and other information as discussed herein.
  • a sub-header may include a UE-ID, TB location information, PRI, and other information as discussed herein.
  • the UE may monitor the MUP-PDSCH directly in the subsequent SPS occasions that follow the configuration period.
  • the base station might not need to send another DCI for the SPS in the PDCCH region until the base station decides to terminate the SPS.
  • the base station need not send a header for the SPS in the MUP-PDSCH after activation in this example.
  • a UE may report A/N information as discussed herein. For example, a UE may transmit A/N information via the PUCCH resource indicated by the K1 and PRI parameters during activation (e.g., indicated in the DCI and/or a sub-header at activation) .
  • FIG. 10 illustrates an example of the alternative approach where a header is only sent in conjunction with the initial transmission of a combo TB.
  • a base station transmits a DCI 1002 (e.g., encoded based on an MUP-CS-RNTI) to activate an SPS for transmissions of combo TBs 1004.
  • the DCI 1002 may indicate an SPS interval that defines the timing of SPS occasions 1008 and 1010 relative to an activation time 1006.
  • the base station transmits a first combo TB based on the activation time 1006 (e.g., during a PDSCH that follows the PDCCH that carries the DCI 1002) , transmits a second combo TB at the second occasion 1008, transmits a third combo TB at the third occasion 1010, and so on.
  • the base station only transmits a header 1012 in conjunction with the initial transmission of a combo TB associated with the activation time 1006.
  • the base station may transmit the header 1012 as part of the associated combo TB (e.g., encoded with the combo TB) as discussed above, for example, in conjunction with FIG. 5.
  • the base station may transmit the header 1012 separately from the associated combo TB as discussed above, for example, in conjunction with FIG. 7.
  • the base station does not transmit different payloads for different users in different SPS occasions. Rather, the combo TBs for each SPS occasion include TBs for the same set of users. In addition, the TB for a given user may be located at the same location of the combo TB for each SPS occasion. Thus, a UE need only decode the header 1012 to determine whether each of the combo TBs 1004 will include a payload for the UE. In addition, a UE only needs to decode the header 1012 to determine where the UE’s payload will be located in each combo TB.
  • the example of FIG. 10 may be more efficient from a signaling stand-point.
  • the base station need not transmit and the UEs need not monitor for a header during the second and later SPS occasions.
  • the disclosure relates in some aspects to techniques for deactivating (e.g., releasing) an SPS.
  • deactivating e.g., releasing
  • an SPS is deactivated (e.g., a UE is related from monitoring SPS transmissions) if a UE receives a DCI that is encoded with an MUP-CS-RNTI, where the DCI indicates deactivation of the SPS.
  • a UE might only monitor for an MUP-CS-RNTI-based DCI (e.g., not monitor the sub-headers) to determine whether an SPS is being deactivated.
  • the UE may deem an SPS as deactivated even if the sub-headers for the corresponding combo TB do not identify (e.g., address) the UE. Consequently, the UE may terminate its monitoring or the SPS occasions.
  • validation of an SPS deactivation may involve setting a HARQ process ID and/or an NDI (or some other parameter (s) ) in the DCI to a value that is defined to indicate the deactivation of an SPS. Any UEs that decode this MUP-CS-RNTI-based DCI will be deactivated (with respect to the SPS) . In situations where multiple configurations of an SPS DL are active, these techniques (or any other suitable techniques) may be used to deactivate one of these SPS DL processes or several of these SPS DL processes.
  • an SPS is deactivated based on both MUP-CS-RNTI-based DCI detection and detection of a sub-header addressing the UE.
  • a UE detects an MUP-CS-RNTI-based DCI and also detects a sub-header addressing the UE (that indicates deactivation of the SPS) , the UE will treat this as a deactivation. Consequently, the UE may terminate its monitoring of the SPS occasions.
  • the UE may treat this as a deactivation for other UEs. Consequently, the UE may continue to monitor the SPS occasions for payloads directed to the UE in this case.
  • the sub-header may indicate whether the SPS is deactivated for that UE. That is, a sub-header may include a UE-ID (e.g., a C-RNTI or a hashed UE-ID) as well as release information.
  • a UE-ID e.g., a C-RNTI or a hashed UE-ID
  • the use of a sub-header that has a structure that is different from the structure of a sub-header used for TB allocation may serve as an indication that the SPS is deactivated for the UE identified by the sub-header.
  • a sub-header that indicates deactivation of an SPS may include different fields than a sub-header that is normally sent during an activated SPS.
  • one or more parameters carried by a sub-header may be used to indicate that an SPS is being deactivated.
  • a sub-header that includes a TB size (TBS) indication a value of zero for the TBS may serve as an indication that the SPS is being deactivated.
  • a UE can check whether the sub-header includes other fields indicative of deactivation (e.g., NDI) .
  • PRI information e.g., in a sub-header
  • the disclosure also relates in some aspects to retransmission for multi-user SPS transmission. If a base station decodes an erasure or a NACK from a UE served by an SPS MUP-PDSCH, the base station may conduct a retransmission. A retransmission may be performed in different ways in different implementations (e.g., using per UE A/N feedback) .
  • a base station may perform a retransmission for an MUP-PDSCH with the same composition as the MUP-PDSCH initial transmission. For example, a base station may perform a full combo TB retransmission. In some examples, the retransmission be performed using a dynamic grant based on the MUP-CS-RNTI used for the original transmission. A full retransmission enables a UE to do soft-combining decoding since the retransmission will carry the complete payload. This approach may be more advantageous if a larger number of UEs in the combo TB send a NACK.
  • UEs that already sent an ACK e.g., UEs that already received their part of the combo TB
  • one of the following options may be used in some examples.
  • the UE sends an ACK again.
  • the UE ignores the packet and does not transmit A/N feedback.
  • a base station may perform a reconstructed TB retransmission (e.g., using the MUP-CS-RNTI) .
  • the base station may use a different HARQ process ID and/or flip the NDI.
  • the retransmission may be UE-specific.
  • the base station may do a per UE retransmission.
  • the base station may use the UE’s C-RNTI. There is no soft combining in this case since the TB has changed.
  • FIG. 11 illustrates one or more aspects of these retransmission schemes in an example of multi-user packet communication 1100 between a base station (BS) 1102 and multiple UEs (e.g., a UE A 1104) .
  • the UE 1104 may correspond to one or more of the scheduled entity 106 (e.g., a UE, etc. ) of FIG. 1, the UE 222, 224, 226, 228, 230, 232, 234, 238, 240, or 242 of FIG. 2, or the UE 604 of FIG. 6.
  • the base station 1102 may correspond to one or more of the scheduling entity 108 (e.g., a gNB, a transmit receive point, a UE, etc. ) of FIG. 1, the base station 210, 212, 214, or 218 of FIG. 2, or the base station 602 of FIG. 6.
  • the scheduling entity 108 e.g., a gNB, a transmit receive point, a UE, etc.
  • the base station 1102 may transmit an multi-user packet for a given SPS occasion to a first group of UEs, shown as UE A 1104, UE B, UE C, through UE X. As shown by a bracket 1106, the base station 1102 may configure UE PUCCH resources for feedback, may transmit a DCI for the multi-user packet, and may transmit the multi-user packet. A first group of UEs may process the multi-user packet and may selectively transmit feedback 1108 for the multi-user packet.
  • the feedback 1108 for a particular UE may include an ACK or a NACK, or may be empty and not include a transmission for the UE (e.g., when the UE refrains from transmitting an ACK and refrains from transmitting a NACK) .
  • the base station 1102 may monitor the feedback 1108 to map ACK/NACK feedback to the UEs in the first group of UEs. For example, the base station 1102 may identify UEs from which an ACK was received, may identify UEs from which a NACK was received, and/or may identify UEs from which neither an ACK nor a NACK was received. The base station 1102 may selectively retransmit the multi-user packet based at least in part on the ACK/NACK feedback from the first group of UEs. For example, if the base station 1102 receives an ACK from all of the UEs in the first group, then the base station may refrain from retransmitting the multi-user packet.
  • the base station 1102 may perform a retransmission.
  • the manner in which the base station 1102 performs the retransmission may depend on a configuration of the base station 1102 and/or one or more of the UEs (e.g., a retransmission configuration) . Additionally, or alternatively, the manner in which the base station 1102 performs the retransmission may depend on a number, a percentage, a ratio, and/or the like of UEs, included in the first group, from which an ACK is received.
  • the base station 1102 may retransmit the multi-user packet, with the same payload (e.g., the same sub-headers and the same payload portions) , to the same group of UEs (e.g., the first group of UEs) . This may result in some UEs that acknowledged the multi-user packet receiving the retransmission.
  • the base station 1102 may transmit a different redundancy version of the multi-user packet (e.g., using the same HARQ process identifier with a new redundancy version identifier, and without changing a new data indicator field from DCI of the prior multi-user packet) .
  • the base station 1102 may retransmit the multi-user packet in this manner when a large quantity (e.g., number, percentage, ratio, and/or the like) of UEs (e.g., greater than or equal to a first threshold and/or a second threshold) did not receive the prior multi-user packet, as indicated by the ACK/NACK feedback. This may waste fewer network resources as compared to retransmitting in this manner when a smaller quantity of UEs did not receive the prior multi-user packet.
  • a large quantity e.g., number, percentage, ratio, and/or the like
  • the base station 1102 may retransmit an multi-user packet, with a different payload (e.g., a different set of sub-headers and/or a different set of payload portions) , to a different group of UEs, such as a second group of UEs shown as UE A, UE B, UE D, through UE N.
  • a different group of UEs such as a second group of UEs shown as UE A, UE B, UE D, through UE N.
  • the second group of UEs may be a subset of the first group of UEs.
  • the second group of UEs may include the UEs, from the first group, from which an ACK was not received.
  • the second group of UEs may include one or more UEs from the first group and one or more UEs that were not in the first group.
  • the base station 1102 may avoid wasting resources by avoiding retransmissions to UEs that received a prior multi-user packet.
  • the base station 1102 may change a new data indicator field and/or may indicate a new HARQ process identifier to prevent the UEs from combining the prior multi-user packet and the retransmission.
  • the base station 1102 may retransmit the multi-user packet in this manner when a medium quantity (e.g., number, percentage, ratio, and/or the like) of UEs (e.g., less than or equal to a first threshold, and greater than or equal to a second threshold) did not receive the prior multi-user packet, as indicated by the ACK/NACK feedback.
  • a medium quantity e.g., number, percentage, ratio, and/or the like
  • the base station 1102 may retransmit a payload portion of the multi-user packet using a unicast transmission to a UE for which the payload portion is intended. In this way, the base station may avoid wasting resources by avoiding retransmissions to UEs that received a prior multi-user packet. In some aspects, the base station 1102 may change a new data indicator field and/or may indicate a new HARQ process identifier to prevent the UEs from combining the prior multi-user packet and the retransmission.
  • the base station 1102 may retransmit the multi-user packet in this manner when a small quantity (e.g., number, percentage, ratio, and/or the like) of UEs (e.g., less than or equal to a first threshold and/or a second threshold) did not receive the prior multi-user packet, as indicated by the ACK/NACK feedback.
  • a small quantity e.g., number, percentage, ratio, and/or the like
  • the base station 1102 may be able to map ACK/NACK feedback received in those PUCCH resources to the appropriate UEs, thereby reducing or eliminating ambiguity in ACK/NACK feedback for the multi-user packet. In this way, the base station 1102 may be capable of selectively retransmitting multi-user packets according to the received and mapped ACK/NACK feedback, and/or may be capable of configuring such retransmissions to achieve improved network performance.
  • FIG. 12 is a diagram illustrating an example of a hardware implementation for a wireless communication device 1200 employing a processing system 1214.
  • the wireless communication device 1200 may be a user equipment (UE) or other device configured to wirelessly communicate with a base station, as discussed in any one or more of FIGs. 1 -11.
  • UE user equipment
  • an element, or any portion of an element, or any combination of elements may be implemented with a processing system 1214 that includes one or more processors 1204.
  • the wireless communication device 1200 may correspond to one or more of the scheduled entity 106 (e.g., a UE, etc. ) of FIG. 1, the UE 222, 224, 226, 228, 230, 232, 234, 238, 240, or 242 of FIG. 2, the UE 604 of FIG. 6, or the UE 1104 of FIG. 11.
  • the scheduled entity 106 e.g., a UE, etc.
  • the wireless communication device 1200 may be implemented with a processing system 1214 that includes one or more processors 1204.
  • processors 1204 include microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • the wireless communication device 1200 may be configured to perform any one or more of the functions described herein. That is, the processor 1204, as utilized in a wireless communication device 1200, may be used to implement any one or more of the processes and procedures described below.
  • the processing system 1214 may be implemented with a bus architecture, represented generally by the bus 1202.
  • the bus 1202 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1214 and the overall design constraints.
  • the bus 1202 communicatively couples together various circuits including one or more processors (represented generally by the processor 1204) , a memory 1205, and computer-readable media (represented generally by the computer-readable medium 1206) .
  • the bus 1202 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • a bus interface 1208 provides an interface between the bus 1202 and a transceiver 1210 and between the bus 1202 and an interface 1230.
  • the transceiver 1210 provides a communication interface or means for communicating with various other apparatus over a wireless transmission medium.
  • the wireless communication device may include two or more transceivers 1210, each configured to communicate with a respective network type (e.g., terrestrial or non-terrestrial) .
  • the interface 1230 provides a communication interface or means of communicating with various other apparatuses and devices (e.g., other devices housed within the same apparatus as the wireless communication device or other external apparatuses) over an internal bus or external transmission medium, such as an Ethernet cable.
  • the interface 1230 may include a user interface (e.g., keypad, display, speaker, microphone, joystick) .
  • a user interface is optional, and may be omitted in some examples, such as an IoT device.
  • the processor 1204 is responsible for managing the bus 1202 and general processing, including the execution of software stored on the computer-readable medium 1206.
  • the software when executed by the processor 1204, causes the processing system 1214 to perform the various functions described below for any particular apparatus.
  • the computer-readable medium 1206 and the memory 1205 may also be used for storing data that is manipulated by the processor 1204 when executing software.
  • One or more processors 1204 in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the software may reside on a computer-readable medium 1206.
  • the computer-readable medium 1206 may be a non-transitory computer-readable medium.
  • a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip) , an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD) ) , a smart card, a flash memory device (e.g., a card, a stick, or a key drive) , a random access memory (RAM) , a read only memory (ROM) , a programmable ROM (PROM) , an erasable PROM (EPROM) , an electrically erasable PROM (EEPROM) , a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer.
  • a magnetic storage device e.g., hard disk, floppy disk, magnetic strip
  • an optical disk e.g.
  • the computer-readable medium 1206 may reside in the processing system 1214, external to the processing system 1214, or distributed across multiple entities including the processing system 1214.
  • the computer-readable medium 1206 may be embodied in a computer program product.
  • a computer program product may include a computer-readable medium in packaging materials.
  • the wireless communication device 1200 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with FIGs. 1 -11 and as described below in conjunction with FIG. 13) .
  • the processor 1204, as utilized in the wireless communication device 1200 may include circuitry configured for various functions.
  • the processor 1204 may include communication and processing circuitry 1241.
  • the communication and processing circuitry 1241 may include one or more hardware components that provide the physical structure that performs various processes related to wireless communication (e.g., signal reception and/or signal transmission) as described herein.
  • the communication and processing circuitry 1241 may further include one or more hardware components that provide the physical structure that performs various processes related to signal processing (e.g., processing a received signal and/or processing a signal for transmission) as described herein.
  • the communication and processing circuitry 1241 may include two or more transmit/receive chains, each configured to process signals in a different RAT (or RAN) type.
  • the communication and processing circuitry 1241 may further be configured to execute communication and processing software 1251 included on the computer-readable medium 1206 to implement one or more functions described herein.
  • the communication and processing circuitry 1241 may obtain information from a component of the wireless communication device 1200 (e.g., from the transceiver 1210 that receives the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium) , process (e.g., decode) the information, and output the processed information.
  • the communication and processing circuitry 1241 may output the information to another component of the processor 1204, to the memory 1205, or to the bus interface 1208.
  • the communication and processing circuitry 1241 may receive one or more of signals, messages, other information, or any combination thereof.
  • the communication and processing circuitry 1241 may receive information via one or more channels.
  • the communication and processing circuitry 1241 may include functionality for a means for receiving.
  • the communication and processing circuitry 1241 may obtain information (e.g., from another component of the processor 1204, the memory 1205, or the bus interface 1208) , process (e.g., encode) the information, and output the processed information.
  • the communication and processing circuitry 1241 may output the information to the transceiver 1210 (e.g., that transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium) .
  • the communication and processing circuitry 1241 may send one or more of signals, messages, other information, or any combination thereof.
  • the communication and processing circuitry 1241 may send information via one or more channels.
  • the communication and processing circuitry 1241 may include functionality for a means for sending (e.g., means for transmitting) .
  • the processor 1204 may include DCI processing circuitry 1242 configured to perform DCI processing-related operations as discussed herein.
  • the DCI processing circuitry 1242 may include functionality for a means for receiving a DCI.
  • the DCI processing circuitry 1242 may monitor a search space for a DCI (e.g., using a G-RNTI) and parse the DCI to determine whether these is a header and a combo TB scheduled in a PDSCH, and to obtain from the DCI information regarding the header and/or the combo TB.
  • the DCI processing circuitry 1242 may further be configured to execute DCI processing software 1252 included on the computer-readable medium 1206 to implement one or more functions described herein.
  • the processor 1204 may include multi-user payload processing circuitry 1243 configured to perform multi-user payload processing-related operations as discussed herein.
  • the multi-user payload processing circuitry 1243 may include functionality for a means for determining whether to monitor semi-persistent transmission occasions.
  • the multi-user payload processing circuitry 1243 may include functionality for a means for determining that a sub-header indicates that a payload is for a wireless communication device (e.g., by parsing the sub-header to determine whether the sub-header includes an identifier of the wireless communication device, to determine a size of the header, to determine a location of a TB, and so on) .
  • the multi-user payload processing circuitry 1243 may include functionality for a means for selectively receiving a multi-user payload.
  • the multi-user payload processing circuitry 1243 may include functionality for a means for processing a payload (e.g., decoding the payload and/or using the payload at an upper layer application) .
  • the multi-user payload processing circuitry 1243 may include functionality for a means for decoding.
  • decoding may involve using CRC information to decode a payload and/or a header.
  • decoding may involve polar decoding on a header and/or control information.
  • decoding may involve LDPC decoding on a multi-user packet and/or other data.
  • decoding may involve decoding code blocks and de-segmenting the code blocks.
  • the multi-user payload processing circuitry 1243 may further be configured to execute multi-user payload processing software 1253 included on the computer-readable medium 1206 to implement one or more functions described herein.
  • FIG. 13 is a flow chart illustrating an example process 1300 for a wireless communication system in accordance with some aspects of the present disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments.
  • the process 1300 may be carried out by the wireless communication device 1200 illustrated in FIG. 12.
  • the wireless communication device may be a user equipment.
  • the process 1300 may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.
  • a wireless communication device may receive a first downlink control information (DCI) indicating a periodicity between a plurality of semi-persistent transmission occasions for a plurality of multi-user payloads.
  • the plurality of multi-user payloads may include a first multi-user payload including a first payload for a first user and a second payload for a second user.
  • the DCI processing circuitry 1242 in cooperation with the communication and processing circuitry 1241 and transceiver 1210, shown and described above in connection with FIG. 12, may monitor a control channel for a DCI (e.g., perform blind decoding on a PDCCH using a particular RNTI and a designate search space) .
  • receiving the first DCI may include decoding the first DCI using a radio network temporary identifier (RNTI) designated for the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • RNTI radio network temporary identifier
  • the wireless communication device may determine whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after receiving the first DCI.
  • the multi-user payload processing circuitry 1243 in cooperation with the communication and processing circuitry 1241 and transceiver 1210, shown and described above in connection with FIG. 12, may monitor a data channel for a header (e.g., monitor a PDSCH using a particular RNTI based on SPS indicated in a DCI) to determine whether the semi-persistent transmission occasions will carry payloads for a UE.
  • determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads may include detecting the first DCI using a radio network temporary identifier (RNTI) designated for the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads and commencing monitoring of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after detecting the DCI using the RNTI.
  • RNTI radio network temporary identifier
  • the process may further include receiving a second DCI indicating deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads and terminating the monitoring of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after receiving the second DCI.
  • the wireless communication device may selectively receive the first multi-user payload after determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • the multi-user payload processing circuitry 1243 in cooperation with the communication and processing circuitry 1241 and transceiver 1210, shown and described above in connection with FIG. 129, may monitor a data channel (e.g., monitor a PDSCH using a particular RNTI based on SPS indicated in a DCI) .
  • selectively receiving the first multi-user payload may include decoding the first payload.
  • the process may further include transmitting a negative acknowledgement after decoding the first payload and decoding a second DCI using a radio network temporary identifier (RNTI) designated for the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after transmitting the negative acknowledgement, where the second DCI may indicate a retransmission of at least the first payload.
  • RNTI radio network temporary identifier
  • determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads may include commencing monitoring of the plurality of semi-persistent transmission occasions.
  • selectively receiving the first multi-user payload may include receiving a first header indicated by the first DCI, wherein the first header may include a first sub-header that identifies a first location of the first payload and a second sub-header that identifies a second location of the second payload, determining that the first sub-header indicates that the first payload is for the wireless communication device, and decoding the first payload after determining that the first sub-header indicates that the first payload is for the wireless communication device.
  • selectively receiving the first multi-user payload may include receiving a first header indicated by the first DCI, wherein the first header may include a first sub-header that identifies a first location of the first payload and a second sub-header that identifies a second location of the second payload, determining that the first sub-header and the second sub-header do not identify the wireless communication device, and abstaining from decoding the first payload and the second payload after determining that the first sub-header and the second sub-header do not identify the wireless communication device.
  • the first DCI may further indicate a transmission of a first header for a first semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions.
  • the method may further include receiving the first header.
  • the first header may include a first sub-header that identifies a first location of the first payload and a second sub-header that identifies a second location of the second payload.
  • determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads may include determining that the first sub-header identifies the wireless communication device and commencing monitoring of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after determining that the first sub-header identifies the wireless communication device.
  • the process may further include receiving a second DCI after receiving the first DCI.
  • the second DCI may indicate a transmission of a second header for a second semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions.
  • the process may also include receiving the second header, where the second header may include a third sub-header, and determining that the third sub-header identifies the wireless communication device.
  • the process may further include determining that the third sub-header indicates, for at least one user, deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • the process may include terminating monitoring of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after determining that the third sub-header identifies the wireless communication device and after determining that the third sub-header indicates, for at least one user, deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • determining that the third sub-header indicates, for at least one user, deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads may include determining that the third sub-header may include a first structure that is different from a second structure of the first sub-header.
  • determining that the third sub-header indicates, for at least one user, deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads may include determining that the third sub-header indicates a transport block size of zero.
  • the process may further include receiving a second DCI after receiving the first DCI.
  • the second DCI may indicate a transmission of a second header for a second semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions; receiving the second header.
  • the process may also include determining that the second header does not identify the wireless communication device and determining that the second header indicates, for at least one user, deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • the process may further include continuing the monitoring of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after determining that the second header does not identify the wireless communication device and after determining that the second header indicates, for at least one user, deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads may include determining that the first header does not identify the wireless communication device and electing to not monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after determining that the first header does not identify the wireless communication device.
  • the process may further include receiving a second DCI after receiving the first DCI.
  • the second DCI may indicate a transmission of a second header for a second semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions.
  • the process may also include receiving the second header, where the second header may include a third sub-header.
  • determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads further may include determining that the third sub-header identifies the wireless communication device and commencing monitoring of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after determining that the third sub-header identifies the wireless communication device.
  • determining whether to monitor the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads may include receiving a first header indicated by the first DCI, where the first header may include a first sub-header that identifies a first location of the first payload and a second sub-header that identifies a second location of the second payload, and determining that the first sub-header identifies the wireless communication device.
  • selectively receiving the first multi-user payload may include decoding the first payload during a first semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions after determining that the first sub-header identifies the wireless communication device.
  • the process may further include receiving a second header after receiving the first header, where the second header may include a third sub-header, and where the third sub-header may identify a third location of a third payload of a second multi-user payload of the plurality of multi-user payloads.
  • the process may also include determining that the third sub-header identifies the wireless communication device and decoding the third payload during a second semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions after determining that the third sub-header identifies the wireless communication device.
  • the process may further include using the first location to receive a third payload during a second semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions after determining that the first sub-header identifies the wireless communication device.
  • FIG. 14 is a conceptual diagram illustrating an example of a hardware implementation for base station (BS) 1400 employing a processing system 1414.
  • BS base station
  • an element, or any portion of an element, or any combination of elements may be implemented with a processing system 1414 that includes one or more processors 1404.
  • the BS 1400 may correspond to one or more of the scheduling entity 108 (e.g., a gNB, a transmit receive point, a UE, etc. ) of FIG. 1, the base station 210, 212, 214, or 218 of FIG. 2, the base station 602 of FIG. 6, or the base station 1102 of FIG. 11.
  • the scheduling entity 108 e.g., a gNB, a transmit receive point, a UE, etc.
  • the processing system 1414 may be substantially the same as the processing system 1214 illustrated in FIG. 12, including a bus interface 1408, a bus 1402, memory 1405, a processor 1404, and a computer-readable medium 1406.
  • the BS 1400 may include an interface 1430 (e.g., a network interface) that provides a means for communicating with at least one other apparatus within a core network and with at least one radio access network.
  • the BS 1400 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with FIGs. 1 -11 and as described below in conjunction with FIG. 15) .
  • the processor 1404 as utilized in the BS 1400, may include circuitry configured for various functions.
  • the processor 1404 may include communication and processing circuitry 1441.
  • the communication and processing circuitry 1441 may include one or more hardware components that provide the physical structure that performs various processes related to communication (e.g., signal reception and/or signal transmission) as described herein.
  • the communication and processing circuitry 1441 may further include one or more hardware components that provide the physical structure that performs various processes related to signal processing (e.g., processing a received signal and/or processing a signal for transmission) as described herein.
  • the communication and processing circuitry 1441 may further be configured to execute communication and processing software 1451 included on the computer-readable medium 1406 to implement one or more functions described herein.
  • the communication and processing circuitry 1441 may obtain information from a component of the BS 1400 (e.g., from the transceiver 1410 that receives the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium) , process (e.g., decode) the information, and output the processed information.
  • the communication and processing circuitry 1441 may output the information to another component of the processor 1404, to the memory 1405, or to the bus interface 1408.
  • the communication and processing circuitry 1441 may receive one or more of signals, messages, other information, or any combination thereof.
  • the communication and processing circuitry 1441 may receive information via one or more channels.
  • the communication and processing circuitry 1441 may include functionality for a means for receiving.
  • the communication and processing circuitry 1441 may obtain information (e.g., from another component of the processor 1404, the memory 1405, or the bus interface 1408) , process (e.g., encode) the information, and output the processed information.
  • the communication and processing circuitry 1441 may output the information to the transceiver 1410 (e.g., that transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium) .
  • the communication and processing circuitry 1441 may send one or more of signals, messages, other information, or any combination thereof.
  • the communication and processing circuitry 1441 may send information via one or more channels.
  • the communication and processing circuitry 1441 may include functionality for a means for sending (e.g., means for transmitting) .
  • the processor 1404 may include multi-user payload generation circuitry 1442 configured to perform multi-user payload generation-related operations as discussed herein.
  • the multi-user payload generation circuitry 1442 may include functionality for a means for generating a payload (e.g., generating a first payload for a first user, a second payload for a second user, and so on) .
  • the multi-user payload generation circuitry 1442 may include functionality for a means for generating a header (e.g., generating a first sub-header that identifies a first user and/or a location of a first payload, a second sub-header that identifies a second user and/or a location of a second payload, and so on) .
  • the multi-user payload generation circuitry 1442 may include functionality for a means for generating CRC information (e.g., generating a first CRC information for a header, second CRC information for a first payload, third CRC information for a second payload, and so on) .
  • the multi-user payload generation circuitry 1442 may include functionality for a means for generating a packet (e.g., aggregating payloads into a combo TB) .
  • the multi-user payload generation circuitry 1442 may further be configured to execute multi-user payload generation software 1452 included on the computer-readable medium 1406 to implement one or more functions described herein.
  • the processor 1404 may include scheduling circuitry 1443 configured to perform scheduling-related operations as discussed herein (e.g., scheduling the transmission of a header and/or a combo TB) .
  • the scheduling circuitry 1443 may include functionality for a means for transmitting a DCI.
  • the scheduling circuitry 1443 may further be configured to execute scheduling software 1453 included on the computer-readable medium 1406 to implement one or more functions described herein.
  • FIG. 15 is a flow chart illustrating another example process 1500 for a wireless communication system in accordance with some aspects of the present disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments.
  • the process 1500 may be carried out by the BS 1400 illustrated in FIG. 14. In some examples, the process 1500 may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.
  • a BS may generate a first downlink control information (DCI) indicating a periodicity between a plurality of semi-persistent transmission occasions for a plurality of multi-user payloads.
  • DCI downlink control information
  • the scheduling circuitry 1443 shown and described above in connection with FIG. 14, may schedule SPS transmissions of headers and/or combo TBs and generate a DCI that includes information about the headers and/or the combo TBs as discussed herein.
  • generating the first DCI may include encoding the first DCI using a radio network temporary identifier (RNTI) designated for the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • RNTI radio network temporary identifier
  • the BS may transmit the first DCI.
  • the scheduling circuitry 1443 in cooperation with the communication and processing circuitry 1441 and the transceiver 1410, shown and described above in connection with FIG. 14, may transmit the DCI (e.g., using an MUP-CS-RNTI and a designated search space) .
  • transmitting the first DCI may activate the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • the process may further include transmitting a second DCI that may indicate deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • the BS may transmit a first multi-user payload of the plurality of multi-user payloads during a first semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions, the first multi-user payload including a first payload for a first user and a second payload for a second user.
  • the multi-user payload generation circuitry 1442 in cooperation with the communication and processing circuitry 1441 and the transceiver 1410, shown and described above in connection with FIG. 14, may transmit a multi-user packet via a data channel during an SPS occasion (e.g., transmit the packet via a PDSCH using a particular RNTI according to SPS indicated in a DCI transmitted by the BS) .
  • the BS may transmit a second multi-user payload of the plurality of multi-user payloads during a second semi-persistent transmission occasion of the plurality of semi-persistent transmission occasions, the second multi-user payload including a third payload for the first user and a fourth payload for the second user.
  • the multi-user payload generation circuitry 1442 in cooperation with the communication and processing circuitry 1441 and the transceiver 1410, shown and described above in connection with FIG. 14, may transmit a multi-user packet via a data channel during an SPS occasion (e.g., transmit the packet via a PDSCH using a particular RNTI according to SPS indicated in a DCI transmitted by the BS) .
  • the process may further include generating a first header and transmitting the first header.
  • the first header may include a first sub-header that identifies a first location of the first payload and a second sub-header that identifies a second location of the second payload.
  • transmitting the first DCI and transmitting the first header may activate the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • the process may further include generating a second DCI.
  • the second DCI may indicate a transmission of a second header.
  • the second header may include a third sub-header.
  • the third sub-header may identify the first user and may indicate, for at least one user, deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payload.
  • the process may also include transmitting the second DCI after transmitting the first DCI and transmitting the second header after transmitting the second DCI.
  • the process may further include generating the third sub-header with a first structure that is different from a second structure of the first sub-header to indicate, for the at least one user, the deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • the process may further include generating the third sub-header with an indication of a transport block size of zero to indicate, for the at least one user, the deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads.
  • the process may further include generating a second DCI.
  • the second DCI may indicate a transmission of a second header.
  • the second header does not identify the first user and may indicate, for at least one user, deactivation of the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads; transmitting the second DCI after transmitting the first DCI; and transmitting the second header after transmitting the second DCI.
  • the process may further include generating a second DCI indicating a transmission of a second header, wherein the second header identifies a third user and the second multi-user payload further includes a fifth payload for the third user.
  • the process may further include transmitting the second DCI after transmitting the first DCI and transmitting the second header after transmitting the second DCI.
  • the process may further include generating a first header and transmitting the first header.
  • the first header may include a first sub-header that identifies a first location of the first payload and a second sub-header that identifies a second location of the second payload.
  • the process may further include generating a second header and transmitting the second header after transmitting the first header.
  • the second header may include a third sub-header and the third sub-header may identify a third location of the third payload.
  • the first location may identify a location of the third payload in the second multi-user payload.
  • the process may further include receiving a negative acknowledgement for the first payload and generating a second DCI using a radio network temporary identifier (RNTI) designated for the plurality of semi-persistent transmission occasions for the plurality of multi-user payloads after receiving the negative acknowledgement.
  • RNTI radio network temporary identifier
  • the second DCI may indicate a retransmission of at least the first payload.
  • the process may also include transmitting the second DCI.
  • various aspects may be implemented within other systems defined by 3GPP, such as Long-Term Evolution (LTE) , the Evolved Packet System (EPS) , the Universal Mobile Telecommunication System (UMTS) , and/or the Global System for Mobile (GSM) .
  • LTE Long-Term Evolution
  • EPS Evolved Packet System
  • UMTS Universal Mobile Telecommunication System
  • GSM Global System for Mobile
  • Various aspects may also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2) , such as CDMA2000 and/or Evolution-Data Optimized (EV-DO) .
  • 3GPP2 3rd Generation Partnership Project 2
  • EV-DO Evolution-Data Optimized
  • Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Ultra-Wideband (UWB) , Bluetooth, and/or other suitable systems.
  • Wi-Fi IEEE 802.11
  • WiMAX IEEE 8
  • the word “exemplary” is used to mean “serving as an example, instance, or illustration. ” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term “aspects” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.
  • the term “coupled” is used herein to refer to the direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, then objects A and C may still be considered coupled to one another-even if they do not directly physically touch each other. For instance, a first object may be coupled to a second object even though the first object is never directly physically in contact with the second object.
  • circuit and “circuitry” are used broadly, and intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in the present disclosure, without limitation as to the type of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in the present disclosure.
  • determining may include, for example, ascertaining, resolving, selecting, choosing, establishing, calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , and the like. Also, “determining” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) , and the like.
  • FIGs. 1 -15 may be rearranged and/or combined into a single component, step, feature or function or embodied in several components, steps, or functions. Additional elements, components, steps, and/or functions may also be added without departing from novel features disclosed herein.
  • the apparatus, devices, and/or components illustrated in FIGs. 1, 2, 6, 11, 12, and 14 may be configured to perform one or more of the methods, features, or steps escribed herein.
  • the novel algorithms described herein may also be efficiently implemented in software and/or embedded in hardware.
  • “at least one of: a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Landscapes

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

Abstract

L'invention concerne une station de base qui peut utiliser un ordonnancement semi-persistant pour ordonnancer des communications multi-utilisateurs (par exemple des paquets multi-utilisateurs). Selon certains aspects, chaque paquet multi-utilisateur peut contenir des charges utiles groupées pour différents utilisateurs (par exemple différents dispositifs de communication sans fil). Dans certains exemples, un paquet multi-utilisateur peut contenir un en-tête ayant plusieurs sous-en-têtes, chaque sous-en-tête identifiant un utilisateur correspondant qui possède une charge utile dans le paquet multi-utilisateur. Pour permettre à un dispositif de communication sans fil de déterminer que la station de base transmet des paquets multi-utilisateurs d'une manière semi-persistante, la station de base peut transmettre des informations de commande de liaison descendante (DCI) qui indiquent que des paquets multi-utilisateurs sont ordonnancés pour une transmission, les DCI étant embrouillées avec un identificateur temporaire de réseau radio (RNTI) qui est conçu pour un trafic SPS multi-utilisateur. La station de base peut fournir ce RNTI à un groupe d'utilisateurs pour permettre aux utilisateurs de recevoir des paquets multi-utilisateurs selon le SPS.
PCT/CN2020/091366 2020-05-20 2020-05-20 Charges utiles multi-utilisateurs semi-persistantes Ceased WO2021232306A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/091366 WO2021232306A1 (fr) 2020-05-20 2020-05-20 Charges utiles multi-utilisateurs semi-persistantes

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/091366 WO2021232306A1 (fr) 2020-05-20 2020-05-20 Charges utiles multi-utilisateurs semi-persistantes

Publications (1)

Publication Number Publication Date
WO2021232306A1 true WO2021232306A1 (fr) 2021-11-25

Family

ID=78709061

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/091366 Ceased WO2021232306A1 (fr) 2020-05-20 2020-05-20 Charges utiles multi-utilisateurs semi-persistantes

Country Status (1)

Country Link
WO (1) WO2021232306A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024178695A1 (fr) * 2023-03-01 2024-09-06 Huawei Technologies Co., Ltd. Transmission de flux de données communs dans un système de communication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018032000A1 (fr) * 2016-08-12 2018-02-15 Ofinno Technologies, Llc Attribution de ressources périodiques dans un réseau sans fil, et dispositif
CN108696941A (zh) * 2017-04-06 2018-10-23 株式会社Ntt都科摩 半永久性调度方法以及用户终端
EP3550875A1 (fr) * 2016-12-02 2019-10-09 Sony Corporation Dispositif dans un système de communication sans fil, et procédé de communication sans fil

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018032000A1 (fr) * 2016-08-12 2018-02-15 Ofinno Technologies, Llc Attribution de ressources périodiques dans un réseau sans fil, et dispositif
EP3550875A1 (fr) * 2016-12-02 2019-10-09 Sony Corporation Dispositif dans un système de communication sans fil, et procédé de communication sans fil
CN108696941A (zh) * 2017-04-06 2018-10-23 株式会社Ntt都科摩 半永久性调度方法以及用户终端

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Considerations for PDCCH Monitoring Reduction and Power Saving of RedCap Devices", 3GPP DRAFT; R1-2004494, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200525 - 20200605, 16 May 2020 (2020-05-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051886223 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024178695A1 (fr) * 2023-03-01 2024-09-06 Huawei Technologies Co., Ltd. Transmission de flux de données communs dans un système de communication

Similar Documents

Publication Publication Date Title
EP3900453B1 (fr) Planification semi-persistante avec de multiples points d'émission-réception
US11653327B2 (en) Paging indicating system information change
US11570808B2 (en) Two-step random access procedure in wireless communication
US20220022209A1 (en) Anchor and complementary bandwidth parts for full-duplex operations
US11722994B2 (en) Facilitating bandwidth part selection in wireless communication systems
US20250379706A1 (en) Validation for pre-configured uplink resource
US20230319901A1 (en) Improved monitoring for random access
US12022521B2 (en) Random access response message repetition
US11838917B2 (en) Cross-carrier downlink control information scheduling
US20230328794A1 (en) Service groups for random access
US12207293B2 (en) Random access channel procedures
US11805477B2 (en) Method to reduce recovery time from out-of-service event in dual receive (DR) or dual sim dual access (DSDA) capable user equipment
WO2021232277A1 (fr) Techniques d'adressage de données par paquets multi-utilisateurs
US11818724B2 (en) Communication after change in bandwidth part
EP4183093A2 (fr) Communication sans fil utilisant plusieurs parties de bande passante actives
EP4559121A1 (fr) Gestion de conflit de porteuses composantes au niveau d'un dispositif de communication sans fil avec de multiples abonnements
US20250175952A1 (en) Transmission configuration indicator for wireless communication
WO2022164571A1 (fr) Configurations pour une communication sans fil à bande étroite
WO2021232306A1 (fr) Charges utiles multi-utilisateurs semi-persistantes
US12328773B2 (en) Configurations for narrowband wireless communication
US12369222B2 (en) Discontinuous reception alignment grouping for sidelink and cellular communication
WO2021223197A1 (fr) Communication utilisant des charges utiles multi-utilisateur
WO2021223199A1 (fr) Schémas de communication pour des charges utiles de multiples utilisateurs
US20230224801A1 (en) Switching between search space set groupings

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: 20937088

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: 20937088

Country of ref document: EP

Kind code of ref document: A1