WO2022032189A1 - System and method for reliability improvement in nr multicast transmissions, and for group scheduling in single cell nr multicast transmissions - Google Patents

System and method for reliability improvement in nr multicast transmissions, and for group scheduling in single cell nr multicast transmissions Download PDF

Info

Publication number
WO2022032189A1
WO2022032189A1 PCT/US2021/045097 US2021045097W WO2022032189A1 WO 2022032189 A1 WO2022032189 A1 WO 2022032189A1 US 2021045097 W US2021045097 W US 2021045097W WO 2022032189 A1 WO2022032189 A1 WO 2022032189A1
Authority
WO
WIPO (PCT)
Prior art keywords
ues
transmission
multicast
message
feedback
Prior art date
Application number
PCT/US2021/045097
Other languages
English (en)
French (fr)
Inventor
Debdeep CHATTERJEE
Alexei Vladimirovich Davydov
Bishwarup Mondal
Avik SENGUPTA
Original Assignee
Intel Corporation
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 Intel Corporation filed Critical Intel Corporation
Priority to CN202180048652.0A priority Critical patent/CN115804051A/zh
Publication of WO2022032189A1 publication Critical patent/WO2022032189A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
    • H04L12/1877—Measures taken prior to transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0041—Arrangements at the transmitter end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint

Definitions

  • Various embodiments generally may relate to the field of wireless communications, and in particular, to the field of communication in a cellular network compliant with one of more Third Generation Partnership Project (3GPP) specifications.
  • 3GPP Third Generation Partnership Project
  • FIG. 1 illustrates a NR network including a gNB and a group of UEs where an initial groupcast transmission is sent to 4 UEs, the transmission including codeblocks CB1 and CB2.
  • FIG. 2A illustrates the NR network of Fig. 1 after the initial groupcast transmission of Fig.
  • Fig. 2B shows the UEs of Fig. 2B after receipt of the retransmissions show in Fig. 2A and during decoding of the same, according to some embodiments.
  • FIG. 3 illustrates a wireless network in accordance with various embodiments.
  • Fig. 4 illustrates a User Equipment (UE) and a Radio Access Node (RAN) in wireless communication according to various embodiments.
  • Fig. 5 illustrates components according to some example embodiments, the components able to read instructions from a machine-readable or computer-readable medium and perform any one or more of the methodologies discussed herein.
  • FIG. 6 illustrates a flow chart for a process according to a first embodiment.
  • Fig. 7 illustrates a flow chart for a process according to a second embodiment.
  • Embodiments are directed to the Third Generation Partnership Projects (3GPP) New Radio (NR) Rel-17 work related to support of broadcast and multicast services within a single cell mainly targeting groupcast operations for the purpose of critical communications and commercial use cases such as popular video/app downloads.
  • 3GPP Third Generation Partnership Projects
  • NR New Radio
  • Radio access network RAN
  • RRC radio resource control
  • RRC_CONNECTED radio resource control
  • RANI, RAN2, RAN3 radio resource control
  • UL uplink
  • the level of reliability should be based on the requirements of the application/service provided.
  • some embodiments described herein are directed to improving the reliability for multicast and broadcast operation within an NR cell without the need for single frequency network (SFN) type operation.
  • SFN single frequency network
  • RP-193248 further has the following objectives with respect to physical layer enhancements to support multicast and broadcast transmissions in NR:
  • some embodiments described herein are directed to enable group scheduling for multicast and broadcast operation within an NR cell without the need for single frequency network (SFN) type operation.
  • SFN single frequency network
  • Embodiments described herein advantageously enable group scheduling for multicast and broadcast operations within an NR cell without the need for single frequency network (SFN) type operation. Additionally, details on multi-user scheduling and co-scheduling of multicast and unicast transmissions are also provided.
  • SFN single frequency network
  • the new work item on NR Support of Multicast and Broadcast Services has the objective of providing support of broadcast and multicast services within a single NR cell mainly targeting groupcast operations for the purpose of critical communications and commercial use cases such as popular video/app downloads.
  • 5G NR multicast can support multiple modes of operation wherein uplink feedback of channel quality indicator (CQI) and hybrid automatic repeat request/acknowledgement (HARQ/ACK) using physical uplink control channel (PUCCH) resources for the group of UEs receiving multicast or broadcast transmissions within an NR cell is configurable both by higher layer and dynamically using downlink control information (DCI).
  • the modes of operation may include:
  • the NR NodeB can choose a fixed modulation and coding scheme (MCS) for all UEs in the group receiving the multicast transmission based on providing minimum required data rate to the UE in the group with the worst coverage or channel conditions.
  • MCS modulation and coding scheme
  • the multicast transmission may operate such that no UE is expected to provide uplink feedback (CQI + HARQ/ACK), and the downlink multicast transmission is configured with repetition possibly multiple times within an NR slot or across multiple NR slots depending on the time domain duration of the PDSCH. In this case, the PDSCH repetitions may not cross the slot boundary.
  • CQI + HARQ/ACK uplink feedback
  • repetitions crossing the slot boundary are also allowed.
  • repetition-based downlink transmission with uplink CQI feedback but no HARQ/ACK feedback is possible wherein the MCS of the groupcast transmission is adapted based on the CQI feedback.
  • the multicast transmission can be configured with a fixed number of repetitions after which the HARQ/ACK feedback is generated and transmitted in the uplink.
  • such HARQ/ACK feedback can be configured such that it is UE specific, wherein the default option for all UEs in the group is not HARQ/ACK feedback.
  • the RRCJDLE UEs may not transmit HARQ/ACK by configuration while the RRC_CONNECTED UEs may be able to transmit HARQ feedback.
  • the UEs receiving the groupcast transmissions may transmit both ACK and NACK based on the status of the received PDSCH.
  • the UEs receiving the groupcast may only transmit NACK in the case that the PDSCH is failed.
  • the UEs can transmit NACK in UE specific PUCCH resources while in another example, the NACK can be transmitted over a shared PUCCH resource.
  • the NACKs from different UEs in the group transmitted on the shared PUCCH resource can be multiplexed using UE specific cyclic shifts.
  • Fig. 1 shows a NR network including a gNB 102 and a group of UEs 104.
  • Fig. 1 in particular shows an initial groupcast transmission to 4 UEs 104, where the transmission includes two codeblocks CB1 and CB2.
  • the failed transport blocks need to be retransmitted even if only one UE 104 in the group transmits a NACK.
  • advanced retransmission techniques using an outer code on top of the channel code can be used.
  • FIG. 2A and 2B pertain to a groupcast retransmission scheme according to an example embodiment.
  • FIG. 2A shows the NR network of Fig. 1 after the initial groupcast transmission of Fig. 1, and at a time of retransmission according to some embodiments.
  • Fig. 2B shows the UEs 104 of Fig. 2B after receipt of the retransmissions show in Fig. 2A and during decoding of the same.
  • network codes such as index coding can be used to jointly transmit failed codeblocks (CBs) to multiple UEs in the group.
  • CBs failed codeblocks
  • the transport block has two codeblocks CB1 and CB2 as shown in in Figs. 2A and 2B. If, of the four UEs 104 in the network of Fig. 2A, two UEs report NACK for the 1st CB of the transport block, CB1, and the two remaining UEs report NACK for the 2nd CB of the transport block, CB2, then the retransmission by the gNB 102 as shown in Fig.
  • the 2A can use an index code, as shown, which bitwise XORs the two CBs together in the retransmission.
  • the UEs which received CB1 correctly can use CB1 as available side information and XOR the received retransmission, along with the already received CB1, to recover CB2, which was not received in the original transmission.
  • the UEs which received CB2 correctly can use CB2 as side information and XOR the received retransmission along with the already received second CB2 to recover CB1.
  • the new work item on NR Support of Multicast and Broadcast Services has as one of its objectives to provide support of broadcast and multicast services within a single NR cell mainly targeting groupcast operations for the purpose of critical communications and commercial use cases such as popular video/app downloads.
  • SC-PTM single cell point-to-multipoint
  • MCSFN multimedia broadcast multicast service single frequency network
  • FDM frequency division multiplexing
  • CP cyclic prefix
  • the multimedia broadcast and multicast service (MBMS) control information including SCPTMConfiguration is obtained from the higher layer logical channel single carrier multicast control channel (SC-MCCH) and the actual SC-PTM traffic is carried in the logical channel single carrier multicast traffic channel (SC-MTCH). Both SC-MCCH and SC-MTCH are mapped to PDSCH in the physical layer.
  • SC-MCCH logical channel single carrier multicast control channel
  • SC-MTCH logical channel single carrier multicast traffic channel
  • the PDSCH carrying SC-MCCH is scheduled by downlink control information (DCI) format 1A with cyclic redundancy check (CRC) scrambled by a single carrier radio network temporary identifier (SC-RNTI) and the PDSCH carrying multicast traffic channel (MTCH) is scheduled by DCI format 1A with CRC scrambled by the group RNTI (G-RNTI) which is provided as a part of the SCPTMConfiguration message.
  • DCI downlink control information
  • CRC cyclic redundancy check
  • MTCH multicast traffic channel
  • G-RNTI group RNTI
  • configuration change notification is also indicated by PDCCH (without associated PDSCH) using DCI format 1C with CRC scrambled by single carrier notification RNTI (SC-N-RNTI).
  • the group of UEs which is receiving multicast and or broadcast transmission within an NR cell is determined by the higher layer and can contain UEs which are either in RRC_CONNECTED mode of RRCJDLE/RRCJNACTIVE mode or a combination of UEs in both states.
  • a new multicast RNTI named the M-RNTI is introduced in NR such that this RNTI is used for scrambling the CRC of the DCI which schedules the PDSCH containing the multicast configuration information of the UEs.
  • this RNTI can also be called the SC-RNTI for NR.
  • another new RNTI named the group or G-RNTI is introduced in NR such that this RNTI is used for scrambling the CRC of the DCI which schedules the PDSCH containing the multicast data to be delivered to the UEs which are part of the group of UEs receiving the multicast transmission within the NR cell.
  • another additional RNTI namely the M-N-RNTI or SC-M-RNTI can be defined to scramble the CRC of the DCI which informs the UE of configuration changes to multicast transmission.
  • PDDCH does schedule any additional PDSCH transmission.
  • the scheduled multicast PDSCH containing either the multicast configuration or the multicast data supports at least PDSCH Mapping Type A with demodulation reference signal (DM-RS) Type 1 and optionally PDSCH Mapping Type B with DM-RS Type 1 and 2.
  • common search space can be configured for monitoring the physical downlink control channel (PDCCH) which contains the scheduling DCI of the multicast configuration or data.
  • PDCH physical downlink control channel
  • Type3-PDCCH CSS set defined in NR 3GPP TS 38.213 V16.2.0, "NR Physical Layer Procedures for Control” (Release 16) can be used with added support for M- RNTI/SC-RNTI, G-RNTI and M-N-RNTI/SC-M-RNTL
  • Type3-PDCCH CSS set configuration is expanded to support DCI format 1_1 in addition to DCI format l_0.
  • a UE specific search space USS can also be used for monitoring PDCCH containing DCI formats related to any multicast/broadcast transmission within the cell. This may apply only to RRC_CONNECTED UEs.
  • the aggregation level (AL) or number of PDCCH candidates to monitor within the configured search space set will be determined based on the UE with the worst coverage or channel conditions among the UEs in the group which receives the multicast or broadcast transmission. Similarly, configuration of the CORESET associated with the search space set including the determination of precoder granularity is also based on the UE with the worst coverage.
  • NR multicast supports at least DCI format l_0 as a baseline for scheduling of multicast related transmissions at least in the case when RRCJDLE/INACTIVE UEs are part of the group of UEs receiving multicast transmission. Additionally, DCI format 1_1 can also be supported. In a variation of this embodiment, a new compact DCI format for multicast scheduling can also be defined in NR.
  • R RECONNECTED UEs may be able to receive both unicast and multicast transmission within the same slot.
  • transmission to the UE can be time division multiplexed (TDM) or frequency division multiplexed (FDM) within a slot.
  • TDM time division multiplexed
  • FDM frequency division multiplexed
  • such transmission can be received simultaneously on orthogonal DM-RS ports with potentially different precoding.
  • a UE should be able to receive two parallel streams at the same time in this example.
  • NR multicast transmissions can use multiple multiple input multiple output (MIMO) layers as supported in a unicast transmission case.
  • MIMO multiple input multiple output
  • Each layer of multicast is transmitted on an orthogonal DM-RS port.
  • the UEs within the group receiving the transmission share the same DM-RS port or ports.
  • multiplexing other unicast UEs on other orthogonal DM-RS ports not used by multicast transmission is also supported e.g., unicast and multicast transmissions in multi-user mode is supported in NR.
  • multi-user superposition coding can be used for multicast transmissions.
  • UEs in the group of users receiving the multicast transmission can be divided into two subgroups with good and adverse channel conditions or coverage, respectively.
  • the most significant bits (MSBs) of the modulation mapping is reserved for the so- called bad UE sub-group.
  • the sub-group of UEs with good channel conditions can additionally receive the least significant bits (LSBs) as well which can lead to additional information.
  • the same video stream can be transmitted using MUST wherein the MSBs correspond to a lower resolution video meant for a user with low coverage, while the LSB add higher resolution content meant for users with higher coverage. From a physical layer perspective, such transmission schemes can enhance the groupcast quality and improve the group spectral efficiency
  • Fig. 6 shows a process 600 according to an embodiment. At operation 602, the process includes **. At operation 602, the process includes **.
  • FIGs. 3-5 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • Fig. 3 illustrates a network 300 in accordance with various embodiments.
  • the network 800 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 300 may include a UE 302, which may include any mobile or non-mobile computing device designed to communicate with a RAN 304 via an over-the-air connection.
  • the UE 302 may be communicatively coupled with the RAN 304 by a Uu interface.
  • the UE 302 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
  • the network 300 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 302 may additionally communicate with an AP 306 via an over-the-air connection.
  • the AP 306 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 304.
  • the connection between the UE 302 and the AP 306 may be consistent with any IEEE 302.11 protocol, wherein the AP 306 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 302, RAN 304, and AP 306 may utilize cellular- WLAN aggregation (for example, LWA/LWIP).
  • Cellular-WLAN aggregation may involve the UE 302 being configured by the RAN 304 to utilize both cellular radio resources and WLAN resources.
  • the RAN 304 may include one or more access nodes, for example, AN 308.
  • AN 308 may terminate air-interface protocols for the UE 302 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 308 may enable data/voice connectivity between CN 320 and the UE 302.
  • the AN 308 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 308 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 308 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 304 may be coupled with one another via an X2 interface (if the RAN 304 is an LTE RAN) or an Xn interface (if the RAN 304 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 304 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 302 with an air interface for network access.
  • the UE 302 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 304.
  • the UE 302 and RAN 304 may use carrier aggregation to allow the UE 302 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 304 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCe I Is/Scel Is.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 302 or AN 308 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 304 may be an LTE RAN 310 with eNBs, for example, eNB 312.
  • the LTE RAN 310 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 304 may be an NG-RAN 314 with gNBs, for example, gNB 316, or ng-eNBs, for example, ng-eNB 318.
  • the gNB 316 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 316 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 318 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 316 and the ng-eNB 318 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 314 and a UPF 348 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN314 and an AMF 344 (e.g., N2 interface).
  • NG-U NG user plane
  • N3 interface e.g., N3 interface
  • N-C NG control plane
  • the NG-RAN 314 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 302 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 302, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 302 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 302 and in some cases at the gNB 316.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 304 is communicatively coupled to CN 320 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 302).
  • the components of the CN 320 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 320 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 320 may be referred to as a network slice, and a logical instantiation of a portion of the CN 320 may be referred to as a network sub-slice.
  • the CN 320 may be an LTE CN 322, which may also be referred to as an EPC.
  • the LTE CN 322 may include MME 324, SGW 326, SGSN 328, HSS 330, PGW 332, and PCRF 334 coupled with one another over interfaces (or "reference points") as shown. Functions of the elements of the LTE CN 322 may be briefly introduced as follows.
  • the MME 324 may implement mobility management functions to track a current location of the UE 302 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 326 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 322.
  • the SGW 326 may be a local mobility anchor point for inter- RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 328 may track a location of the UE 302 and perform security functions and access control. In addition, the SGSN 328 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 324; MME selection for handovers; etc.
  • the S3 reference point between the MME 324 and the SGSN 328 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 330 may include a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the HSS 330 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 330 and the MME 324 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 320.
  • the PGW 332 may terminate an SGi interface toward a data network (DN) 336 that may include an application/content server 338. The PGW 332 may route data packets between the LTE CN 322 and the data network 336.
  • DN data network
  • the PGW 332 may be coupled with the SGW 326 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 332 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • PCEF policy enforcement and charging data collection
  • the SGi reference point between the PGW 332 and the data network YX 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 332 may be coupled with a PCRF 334 via a Gx reference point.
  • the PCRF 334 is the policy and charging control element of the LTE CN 322.
  • the PCRF 334 may be communicatively coupled to the app/content server 338 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 332 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCL
  • the CN 320 may be a 5GC 340.
  • the 5GC 340 may include an AUSF 342, AMF 344, SMF 346, UPF 348, NSSF 350, NEF 352, NRF 354, PCF 356, UDM 358, and AF 360 coupled with one another over interfaces (or "reference points") as shown.
  • Functions of the elements of the 5GC 340 may be briefly introduced as follows.
  • the AUSF 342 may store data for authentication of UE 302 and handle authentication- related functionality.
  • the AUSF 342 may facilitate a common authentication framework for various access types.
  • the AUSF 342 may exhibit an Nausf service-based interface.
  • the AMF 344 may allow other functions of the 5GC 340 to communicate with the UE 302 and the RAN 304 and to subscribe to notifications about mobility events with respect to the UE 302.
  • the AMF 344 may be responsible for registration management (for example, for registering UE 302), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 344 may provide transport for SM messages between the UE 302 and the SMF 346, and act as a transparent proxy for routing SM messages.
  • AMF 344 may also provide transport for SMS messages between UE 302 and an SMSF.
  • AMF 344 may interact with the AUSF 342 and the UE 302 to perform various security anchor and context management functions.
  • AMF 344 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 304 and the AMF 344; and the AMF 344 may be a termination point of NAS (N 1) signaling, and perform NAS ciphering and integrity protection.
  • AMF 344 may also support NAS signaling with the UE 302 over an N3 IWF interface.
  • the SMF 346 may be responsible for SM (for example, session establishment, tunnel management between UPF 348 and AN 308); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 348 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 344 over N2 to AN 308; and determining SSC mode of a session.
  • SM may refer to management of a PDU session, and a PDU session or "session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 302 and the data network 336.
  • the UPF 348 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 336, and a branching point to support multi-homed PDU session.
  • the UPF 348 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 348 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 350 may select a set of network slice instances serving the UE 302.
  • the NSSF 350 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 350 may also determine the AMF set to be used to serve the UE 302, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 354.
  • the selection of a set of network slice instances for the UE 302 may be triggered by the AMF 344 with which the UE 302 is registered by interacting with the NSSF 350, which may lead to a change of AMF.
  • the NSSF 350 may interact with the AMF 344 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 350 may exhibit an Nnssf service-based interface.
  • the NEF 352 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 360), edge computing or fog computing systems, etc.
  • the NEF 352 may authenticate, authorize, or throttle the AFs.
  • NEF 352 may also translate information exchanged with the AF 360 and information exchanged with internal network functions. For example, the NEF 352 may translate between an AF-Service-ldentifier and an internal 5GC information.
  • NEF 352 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 352 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 352 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 352 may exhibit an Nnef service-based interface.
  • the NRF 354 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 354 also maintains information of available NF instances and their supported services. As used herein, the terms "instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 354 may exhibit the Nnrf service-based interface.
  • the PCF 356 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 356 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 358.
  • the PCF 356 exhibit an Npcf service-based interface.
  • the UDM 358 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 302. For example, subscription data may be communicated via an N8 reference point between the UDM 358 and the AMF 344.
  • the UDM 358 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 358 and the PCF 356, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 302) for the NEF 352.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 358, PCF 356, and NEF 352 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 358 may exhibit the Nudm service-based interface.
  • the AF 360 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 340 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 302 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 340 may select a UPF 348 close to the UE 302 and execute traffic steering from the UPF 348 to data network 336 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 360. In this way, the AF 360 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 360 to interact directly with relevant NFs. Additionally, the AF 360 may exhibit an Naf service-based interface.
  • the data network 336 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 338.
  • Fig. 4 schematically illustrates a wireless network 400 in accordance with various embodiments.
  • the wireless network 400 may include a UE 402 in wireless communication with an AN 404.
  • the UE 402 and AN 404 may be similar to, and substantially interchangeable with, like- named components described elsewhere herein.
  • the UE 402 may be communicatively coupled with the AN 404 via connection 406.
  • the connection 406 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 402 may include a host platform 408 coupled with a modem platform 410.
  • the host platform 408 may include application processing circuitry 412, which may be coupled with protocol processing circuitry 414 of the modem platform 410.
  • the application processing circuitry 412 may run various applications for the UE 402 that source/sink application data.
  • the application processing circuitry 412 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 414 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 406.
  • the layer operations implemented by the protocol processing circuitry 414 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 410 may further include digital baseband circuitry 416 that may implement one or more layer operations that are "below" layer operations performed by the protocol processing circuitry 414 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may
  • the modem platform 410 may further include transmit circuitry 418, receive circuitry 420, RF circuitry 422, and RF front end (RFFE) 424, which may include or connect to one or more antenna panels 426.
  • the transmit circuitry 418 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 420 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 422 may include a low- noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 424 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is time division multiplexed (TDM) or frequency division multiplexed (FDM), in mmWave or sub-6 gHz frequencies, etc.
  • TDM time division multiplexed
  • FDM frequency division multiplexed
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 414 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 426, RFFE 424, RF circuitry 422, receive circuitry 420, digital baseband circuitry 416, and protocol processing circuitry 414.
  • the antenna panels 426 may receive a transmission from the AN 404 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 426.
  • a UE transmission may be established by and via the protocol processing circuitry 414, digital baseband circuitry 416, transmit circuitry 418, RF circuitry 422, RFFE 424, and antenna panels 426.
  • the transmit components of the UE 404 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 426.
  • the AN 404 may include a host platform 428 coupled with a modem platform 430.
  • the host platform 428 may include application processing circuitry 432 coupled with protocol processing circuitry 434 of the modem platform 430.
  • the modem platform may further include digital baseband circuitry 436, transmit circuitry 438, receive circuitry 440, RF circuitry 442, RFFE circuitry 444, and antenna panels 446.
  • the components of the AN 404 may be similar to and substantially interchangeable with like-named components of the UE 402.
  • Fig. 5 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Fig.
  • FIG. 5 shows a diagrammatic representation of hardware resources 500 including one or more processors (or processor cores) 510, one or more memory/storage devices 520, and one or more communication resources 530, each of which may be communicatively coupled via a bus 540 or other interface circuitry.
  • a hypervisor 502 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 500.
  • the processors 510 may include, for example, a processor 512 and a processor 514.
  • the processors 510 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 520 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 520 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 530 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 504 or one or more databases 506 or other network elements via a network 508.
  • the communication resources 530 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
  • Instructions 550 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 510 to perform any one or more of the methodologies discussed herein.
  • the instructions 550 may reside, completely or partially, within at least one of the processors 510 (e.g., within the processor's cache memory), the memory/storage devices 520, or any suitable combination thereof.
  • any portion of the instructions 550 may be transferred to the hardware resources 500 from any combination of the peripheral devices 504 or the databases 506.
  • the memory of processors 510, the memory/storage devices 520, the peripheral devices 504, and the databases 506 are examples of computer-readable and machine-readable media.
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 includes an apparatus of a New Radio (NR) Node B (gNB), the apparatus including a memory, and one or more processors coupled to the memory, the memory storing instructions, and the one or more processors to implement the instructions to: encode a message for single cell multicast, broadcast or groupcast transmission to a group of User Equipments (UEs), the message to configure the UEs with respect to at least one of channel quality indicator (CQI) feedback or hybrid automatic repeat request acknowledgement (HARQ/ACK) feedback such that at least one of CQI feedback or HARQ/ACK feedback can be turned off, or such that CQI feedback and HARQ/ACK feedback can both be used; and send the message to communications resources of the gNB for transmission to the UEs.
  • CQI channel quality indicator
  • HARQ/ACK hybrid automatic repeat request acknowledgement
  • Example 2 includes the subject matter of Example 1, wherein, for groupcast transmission, the one or more processors are to further configure the UEs to receive multiple repetitions of the groupcast transmission within a slot, across slots, or across a slot boundary.
  • Example 3 includes the subject matter of Example 2, wherein the multiple repetitions are within a slot, across slots or across a slot boundary based on a length of a physical downlink shared channel (PDSCH) of the groupcast transmission.
  • PDSCH physical downlink shared channel
  • Example 4 includes the subject matter of Example 2, wherein the message is to configure the UEs to not provide any uplink feedback to the gNB.
  • Example 5 includes the subject matter of Example 2, wherein the message is a first message, the one or more processors to further configure the UEs to receive the multiple repetitions by encoding a second message for transmission to the UEs, the second message to configure the UEs to receive the multiple repetitions.
  • Example 6 includes the subject matter of Example 2, wherein the message is to configure the UEs to provide HARQ/ACK feedback.
  • Example 7 includes the subject matter of any one of Examples 1-6, wherein the one or more processors are to decode acknowledgment (ACK) and negative acknowledgement (NACK) feedback for the groupcast transmission from the UEs in a physical uplink control channel (PUCCH).
  • ACK decode acknowledgment
  • NACK negative acknowledgement
  • Example 8 includes the subject matter of any one of Examples 1-6, wherein the one or more processors are to decode a negative acknowledgement (NACK) feedback and not an acknowledgement (ACK) feedback for the groupcast transmission, the NACK from one or more UEs of the group that did not receive a physical downlink shared channel (PDSCH) transmission of the groupcast transmission.
  • NACK negative acknowledgement
  • ACK acknowledgement
  • Example 9 includes the subject matter of Example 8, wherein the NACK feedback is on a physical uplink control channel (PUCCH) resource shared by the UEs.
  • PUCCH physical uplink control channel
  • Example 10 includes the subject matter of Example 9, wherein the NACK feedback from the one or more UEs is multiplexed using UE-specific cyclic shifts.
  • Example 11 includes the subject matter of any one of Examples 1-7, wherein, for codeblock (CB) based HARQ retransmission, the one or more processors are to implement network coding across retransmission CBs, network coded retransmission CBs to be used by a UE of the UEs, in addition to CB information already received by the UE, to decode a desired CB corresponding to a CB not received by the UE in an initial transmission associated with the HARQ retransmission.
  • CB codeblock
  • Example 12 includes the subject matter of Example 11, wherein the network coding includes an exclusive OR (XOR) function applied, in the retransmission, to CBs of the initial transmission.
  • XOR exclusive OR
  • Example 13 includes the subject matter of Example 1, the one or more processors to encode for transmission to the UEs a multicast, broadcast or groupcast physical layer transmission mapped to a common service by higher layers.
  • Example 14 includes the subject matter of Example 13, wherein the group includes UEs that are either radio resource control-connected (RRC_CONNECTED), RRCJDLE/RRCJNACTIVE or both.
  • RRC_CONNECTED radio resource control-connected
  • RRCJDLE/RRCJNACTIVE radio resource control-connected
  • Example 15 includes the subject matter of Example 13, wherein the one or more processors are to encode a downlink control information (DCI) including a radio network temporary identifier for a scrambling of a cyclic redundancy check of the DCI, the DCI to a multicast or broadcast physical downlink shared channel (PDSCH) related to one of: delivery of a configuration or data; or updating of a previous multicast configuration.
  • DCI downlink control information
  • PDSCH physical downlink shared channel
  • Example 16 includes the subject matter of Example 13, the one or more processors are to encode for transmission to the UEs a message to configure a common search space to monitor a physical downlink control channel (PDCCH) containing scheduling DCI of the multicast or broadcast physical layer transmission.
  • PDCCH physical downlink control channel
  • Example 17 includes the subject matter of Example 16, wherein the common search space (CSS) corresponds to one of: a Type3-PDCCH CSS set along with a multicast RNTI; or a Type 4-PDCCH CSS set specific to monitoring multicast DCI.
  • SCS common search space
  • Example 18 includes the subject matter of Example 17, wherein the scheduling DCI is one of a DCI l_0 or 1_1.
  • Example 19 includes the subject matter of Example 13, the one or more processors are to encode for transmission to the UEs a message to configure a UE-specific search space to monitor a physical downlink control channel (PDCCH) containing scheduling DCI of the multicast or broadcast physical layer transmission.
  • PDCCH physical downlink control channel
  • Example 20 includes the subject matter of any one of Examples 13-19, wherein the one or more processors are to configure for a UE of the group an aggregation level for PDCCH monitoring and a precoder granularity for an associated control resource set (CORESET) configuration based on a UE of the group with a worst coverage.
  • Example 21 includes the subject matter of any one of Examples 13-19, wherein the physical layer transmission is one of unicast or multicast, are one of frequency divisional multiplexed, time division multiplexed, or transmitted simultaneously to the UEs on orthogonal demodulation reference signal (DM-RS) ports within a slot.
  • DM-RS orthogonal demodulation reference signal
  • Example 22 includes the subject matter of any one of Examples 13-19, wherein the physical layer transmission is multicast and use multiple multiple input multiple output (MIMO) layers with rank adaptation.
  • MIMO multiple input multiple output
  • Example 23 includes the subject matter of any one of Examples 13-19, wherein the physical layer transmission is a multicast transmission to be received by the UEs on one or more of the same demodulation reference signal (DM-RS) ports.
  • DM-RS demodulation reference signal
  • Example 24 includes the subject matter of any one of Examples 13-19, wherein the one or more processors are to co-schedule a unicast physical layer transmission to at least one of the UEs along with the multicast physical layer transmission using orthogonal demodulation reference signal (DM-RS) ports not used for the multicast physical layer transmission.
  • DM-RS orthogonal demodulation reference signal
  • Example 25 includes the subject matter of any one of Examples 13-19, wherein the one or more processors are to use multi-user superposition coding for the multicast physical layer transmission.
  • Example 26 includes the subject matter of any one of Examples 1-6 and 13-19, further including the communications resources to transmit messages to the UEs.
  • Example 27 includes a method to be performed at a New Radio (NR) Node B (gNB), the method including: encoding a message for single cell multicast, broadcast or groupcast transmission to a group of User Equipments (UEs), the message to configure the UEs with respect to at least one of channel quality indicator (CQI) feedback or hybrid automatic repeat request acknowledgement (HARQ/ACK) feedback such that at least one of CQI feedback or HARQ/ACK feedback can be turned off, or such that CQI feedback and HARQ/ACK feedback can both be used; and sending the message to communications resources of the gNB for transmission to the UEs.
  • Example 28 includes the subject matter of Example 27, wherein, for groupcast transmission, the method further includes configuring the UEs to receive multiple repetitions of the groupcast transmission within a slot, across slots, or across a slot boundary.
  • Example 29 includes the subject matter of Example 28, wherein the multiple repetitions are within a slot, across slots or across a slot boundary based on a length of a physical downlink shared channel (PDSCH) of the groupcast transmission.
  • PDSCH physical downlink shared channel
  • Example 30 includes the subject matter of Example 28, wherein the message is to configure the UEs to not provide any uplink feedback to the gNB.
  • Example 31 includes the subject matter of Example 28, wherein the message is a first message, the method further including configuring the UEs to receive the multiple repetitions by encoding a second message for transmission to the UEs, the second message to configure the UEs to receive the multiple repetitions.
  • Example 32 includes the subject matter of Example 28, wherein the message is to configure the UEs to provide HARQ/ACK feedback.
  • Example 33 includes the subject matter of any one of Examples 27-32, further including acknowledgment (ACK) and negative acknowledgement (NACK) feedback for the groupcast transmission from the UEs in a physical uplink control channel (PUCCH).
  • ACK acknowledgment
  • NACK negative acknowledgement
  • Example 34 includes the subject matter of any one of Examples 27-32, further including decoding a negative acknowledgement (NACK) feedback and not an acknowledgement (ACK) feedback for the groupcast transmission, the NACK from one or more UEs of the group that did not receive a physical downlink shared channel (PDSCH) transmission of the groupcast transmission.
  • NACK negative acknowledgement
  • ACK acknowledgement
  • Example 35 includes the subject matter of Example 34, wherein the NACK feedback is on a physical uplink control channel (PUCCH) resource shared by the UEs.
  • PUCCH physical uplink control channel
  • Example 36 includes the subject matter of Example 35, wherein the NACK feedback from the one or more UEs is multiplexed using UE-specific cyclic shifts.
  • Example 37 includes the subject matter of any one of Examples 27-33, wherein, for codeblock (CB) based HARQ retransmission, the method further includes implementing network coding across retransmission CBs, network coded retransmission CBs to be used by a UE of the UEs, in addition to CB information already received by the UE, to decode a desired CB corresponding to a CB not received by the UE in an initial transmission associated with the HARQ retransmission.
  • CB codeblock
  • Example 38 includes the subject matter of Example 37, wherein the network coding includes an exclusive OR (XOR) function applied, in the retransmission, to CBs of the initial transmission.
  • XOR exclusive OR
  • Example 39 includes the subject matter of Example 27, the method further including encoding for transmission to the UEs a multicast, broadcast or groupcast physical layer transmission mapped to a common service by higher layers.
  • Example 40 includes the subject matter of Example 39, wherein the group includes UEs that are either radio resource control-connected (RRC_CONNECTED), RRCJDLE/RRCJNACTIVE or both.
  • RRC_CONNECTED radio resource control-connected
  • RRCJDLE/RRCJNACTIVE radio resource control-connected
  • Example 41 includes the subject matter of Example 39, the method further including encoding a downlink control information (DCI) including a radio network temporary identifier for a scrambling of a cyclic redundancy check of the DCI, the DCI to a multicast or broadcast physical downlink shared channel (PDSCH) related to one of: delivery of a configuration or data; or updating of a previous multicast configuration.
  • DCI downlink control information
  • PDSCH physical downlink shared channel
  • Example 42 includes the subject matter of Example 39, further including encoding for transmission to the UEs a message to configure a common search space to monitor a physical downlink control channel (PDCCH) containing scheduling DCI of the multicast or broadcast physical layer transmission.
  • PDCCH physical downlink control channel
  • Example 43 includes the subject matter of Example 42, wherein the common search space (CSS) corresponds to one of: a Type3-PDCCH CSS set along with a multicast RNTI; or a Type 4-PDCCH CSS set specific to monitoring multicast DCI.
  • SCS common search space
  • Example 44 includes the subject matter of Example 43, wherein the scheduling DCI is one of a DCI l_0 or 1_1.
  • Example 45 includes the subject matter of Example 39, further including encoding for transmission to the UEs a message to configure a UE-specific search space to monitor a physical downlink control channel (PDCCH) containing scheduling DCI of the multicast or broadcast physical layer transmission.
  • PDCCH physical downlink control channel
  • Example 46 includes the subject matter of any one of Examples 39-45, further including configuring for a UE of the group an aggregation level for PDCCH monitoring and a precoder granularity for an associated control resource set (CORESET) configuration based on a UE of the group with a worst coverage.
  • CORESET control resource set
  • Example 47 includes the subject matter of any one of Examples 39-45, wherein the physical layer transmission is one of unicast or multicast, are one of frequency divisional multiplexed, time division multiplexed, or transmitted simultaneously to the UEs on orthogonal demodulation reference signal (DM-RS) ports within a slot.
  • DM-RS orthogonal demodulation reference signal
  • Example 48 includes the subject matter of any one of Examples 39-45, wherein the physical layer transmission is multicast and use multiple multiple input multiple output (MIMO) layers with rank adaptation.
  • MIMO multiple input multiple output
  • Example 49 includes the subject matter of any one of Examples 39-45, wherein the physical layer transmission is a multicast transmission to be received by the UEs on one or more of the same demodulation reference signal (DM-RS) ports.
  • DM-RS demodulation reference signal
  • Example 50 includes the subject matter of any one of Examples 39-45, further including co-scheduling a unicast physical layer transmission to at least one of the UEs along with the multicast physical layer transmission using orthogonal demodulation reference signal (DM-RS) ports not used for the multicast physical layer transmission.
  • DM-RS orthogonal demodulation reference signal
  • Example 51 includes the subject matter of any one of Examples 39-45, further including using multi-user superposition coding for the multicast physical layer transmission.
  • Example 52 includes an apparatus of a New Radio (NR) User Equipment (UE), the apparatus including a memory, and one or more processors coupled to the memory, the memory storing instructions, and the one or more processors to implement the instructions to: decode a message for single cell multicast, broadcast or groupcast transmission sent by a NR Node B (gNB) to a group of User Equipments (UEs), the message to configure the UE with respect to at least one of channel quality indicator (CQI) feedback or hybrid automatic repeat request acknowledgement (HARQ/ACK) feedback such that at least one of CQI feedback or HARQ/ACK feedback can be turned off, or such that CQI feedback and HARQ/ACK feedback can both be used; and configure the UE based on the message.
  • gNB NR Node B
  • UEs User Equipments
  • CQI channel quality indicator
  • HARQ/ACK hybrid automatic repeat request acknowledgement
  • Example 53 includes the subject matter of Example 52, wherein, for groupcast transmission, the one or more processors are to further configure the UE to receive multiple repetitions of the groupcast transmission within a slot, across slots, or across a slot boundary.
  • Example 54 includes the subject matter of Example 53, wherein the multiple repetitions are within a slot, across slots or across a slot boundary based on a length of a physical downlink shared channel (PDSCH) of the groupcast transmission.
  • Example 55 includes the subject matter of Example 54, wherein the message is to configure the UE to not provide any uplink feedback to the gNB.
  • PDSCH physical downlink shared channel
  • Example 56 includes the subject matter of Example 53, wherein the message is a first message, the one or more processors to further configure the UE to receive the multiple repetitions by decoding a second message from the gNB.
  • Example 57 includes the subject matter of Example 53, wherein the message is to configure the UE to provide HARQ/ACK feedback.
  • Example 58 includes the subject matter of any one of Examples 52-57, wherein the one or more processors are to encode for transmission to the gNB, in a physical uplink control channel (PUCCH), an acknowledgment (ACK) or a negative acknowledgement (NACK) feedback for the groupcast transmission.
  • PUCCH physical uplink control channel
  • ACK acknowledgment
  • NACK negative acknowledgement
  • Example 59 includes the subject matter of any one of Examples 52-57, wherein the one or more processors are to encode, for transmission to the gNB, a negative acknowledgement (NACK) feedback and not an acknowledgement (ACK) feedback for the groupcast transmission.
  • NACK negative acknowledgement
  • ACK acknowledgement
  • Example 60 includes the subject matter of Example 59, wherein the NACK feedback is on a physical uplink control channel (PUCCH) resource shared by the UEs.
  • PUCCH physical uplink control channel
  • Example 61 includes the subject matter of Example 60, wherein the NACK feedback is multiplexed using UE-specific cyclic shifts.
  • Example 62 includes the subject matter of any one of Examples 52-58, wherein, for codeblock (CB) based HARQ retransmission, the one or more processors are to use network coded retransmission CBs sent by the gNB, in addition to CB information already received by the UE, to decode a desired CB corresponding to a CB not received by the UE in an initial transmission associated with the HARQ retransmission.
  • CB codeblock
  • Example 63 includes the subject matter of Example 62, wherein network coding for the network coded retransmission CBs includes an exclusive OR (XOR) function applied, in the retransmission, to CBs of the initial transmission.
  • XOR exclusive OR
  • Example 64 includes the subject matter of Example 52, the one or more processors to decode a multicast, broadcast or groupcast physical layer transmission from the gNB mapped to a common service by higher layers.
  • Example 65 includes the subject matter of Example 64, wherein the UE is either radio resource control-connected (RRC_CONNECTED) or RRCJDLE/RRCJNACTIVE.
  • RRC_CONNECTED radio resource control-connected
  • RRCJDLE/RRCJNACTIVE radio resource control-connected
  • Example 66 includes the subject matter of Example 64, wherein the one or more processors are to decode a downlink control information (DCI) including a radio network temporary identifier for a scrambling of a cyclic redundancy check of the DCI, the DCI to a multicast or broadcast physical downlink shared channel (PDSCH) related to one of: delivery of a configuration or data; or updating of a previous multicast configuration.
  • DCI downlink control information
  • PDSCH physical downlink shared channel
  • Example 67 includes the subject matter of Example 64, wherein the one or more processors are to decode a message from the gNB to configure a common search space to monitor a physical downlink control channel (PDCCH) containing scheduling DCI of the multicast or broadcast physical layer transmission.
  • PDCCH physical downlink control channel
  • Example 68 includes the subject matter of Example 67, wherein the common search space (CSS) corresponds to one of: a Type3-PDCCH CSS set along with a multicast RNTI; or a Type 4-PDCCH CSS set specific to monitoring multicast DCI.
  • the common search space corresponds to one of: a Type3-PDCCH CSS set along with a multicast RNTI; or a Type 4-PDCCH CSS set specific to monitoring multicast DCI.
  • Example 69 includes the subject matter of Example 68, wherein the scheduling DCI is one of a DCI l_0 or 1_1.
  • Example 70 includes the subject matter of Example 64, wherein the one or more processors are to decode a message from the gNB to configure a UE-specific search space to monitor a physical downlink control channel (PDCCH) containing scheduling DCI of the multicast or broadcast physical layer transmission.
  • PDCCH physical downlink control channel
  • Example 71 includes the subject matter of any one of Examples 64-70, wherein the one or more processors are to configure the UE with an aggregation level for PDCCH monitoring and a precoder granularity for an associated control resource set (CORESET) configuration based on a UE of the group with a worst coverage.
  • the one or more processors are to configure the UE with an aggregation level for PDCCH monitoring and a precoder granularity for an associated control resource set (CORESET) configuration based on a UE of the group with a worst coverage.
  • CORESET control resource set
  • Example 72 includes the subject matter of any one of Examples 64-70, wherein the physical layer transmission is one of unicast or multicast, is one of frequency divisional multiplexed, time division multiplexed, or transmitted simultaneously to the UEs on orthogonal demodulation reference signal (DM-RS) ports within a slot.
  • DM-RS orthogonal demodulation reference signal
  • Example 73 includes the subject matter of any one of Examples 64-70, wherein the physical layer transmission is multicast and uses multiple multiple input multiple output (MIMO) layers with rank adaptation.
  • Example 74 includes the subject matter of any one of Examples 64-70, wherein the physical layer transmission is a multicast transmission to be received by the UEs on one or more of the same demodulation reference signal (DM-RS) ports.
  • DM-RS demodulation reference signal
  • Example 75 includes the subject matter of any one of Examples 64-70, wherein the one or more processors are to decode a unicast physical layer transmission to at least one of the UEs co-scheduled along with the multicast physical layer transmission using orthogonal demodulation reference signal (DM-RS) ports not used for the multicast physical layer transmission.
  • DM-RS orthogonal demodulation reference signal
  • Example 76 includes the subject matter of any one of Examples 64-70, wherein the one or more processors are to use multi-user superposition coding for the multicast physical layer transmission.
  • Example 77 includes the subject matter of any one of Examples 52-57 and 64-70, further including the communications resources to transmit messages to the UEs.
  • Example 78 includes a method to be performed at a New Radio (NR) User Equipment (UE), the method including: decoding a message for single cell multicast, broadcast or groupcast transmission sent by a NR Node B (gNB) to a group of User Equipments (UEs), the message to configure the UE with respect to at least one of channel quality indicator (CQI ) feedback or hybrid automatic repeat request acknowledgement (HARQ/ACK) feedback such that at least one of CQI feedback or HARQ/ACK feedback can be turned off, or such that CQI feedback and HARQ/ACK feedback can both be used; and configuring the UE based on the message.
  • CQI channel quality indicator
  • HARQ/ACK hybrid automatic repeat request acknowledgement
  • Example 79 includes the subject matter of Example 78, wherein, for groupcast transmission, the method further includes configuring the UE to receive multiple repetitions of the groupcast transmission within a slot, across slots, or across a slot boundary.
  • Example 80 includes the subject matter of Example 79, wherein the multiple repetitions are within a slot, across slots or across a slot boundary based on a length of a physical downlink shared channel (PDSCH) of the groupcast transmission.
  • PDSCH physical downlink shared channel
  • Example 81 includes the subject matter of Example 80, wherein the message is to configure the UE to not provide any uplink feedback to the gNB.
  • Example 82 includes the subject matter of Example 79, wherein the message is a first message, the method further including configuring the UE to receive the multiple repetitions by decoding a second message from the gNB.
  • Example 83 includes the subject matter of Example 79, wherein the message is to configure the UE to provide HARQ/ACK feedback.
  • Example 84 includes the subject matter of any one of Examples 78-83, further including encoding for transmission to the gNB, in a physical uplink control channel (PUCCH), an acknowledgment (ACK) or a negative acknowledgement (NACK) feedback for the groupcast transmission.
  • PUCCH physical uplink control channel
  • ACK acknowledgment
  • NACK negative acknowledgement
  • Example 85 includes the subject matter of any one of Examples 78-83, further including encoding a negative acknowledgement (NACK) feedback and not an acknowledgement (ACK) feedback for the groupcast transmission.
  • NACK negative acknowledgement
  • ACK acknowledgement
  • Example 86 includes the subject matter of Example 85, wherein the NACK feedback is on a physical uplink control channel (PUCCH) resource shared by the UEs.
  • PUCCH physical uplink control channel
  • Example 87 includes the subject matter of Example 86, wherein the NACK feedback is multiplexed using UE-specific cyclic shifts.
  • Example 88 includes the subject matter of any one of Examples 78-84, wherein, for codeblock (CB) based HARQ retransmission, the method further includes using network coded retransmission CBs sent by the gNB, in addition to CB information already received by the UE, to decode a desired CB corresponding to a CB not received by the UE in an initial transmission associated with the HARQ retransmission.
  • CB codeblock
  • Example 89 includes the subject matter of Example 88, wherein network coding for the network coded retransmission CBs includes an exclusive OR (XOR) function applied, in the retransmission, to CBs of the initial transmission.
  • XOR exclusive OR
  • Example 90 includes the subject matter of Example 78, further including decoding a multicast, broadcast or groupcast physical layer transmission from the gNB mapped to a common service by higher layers.
  • Example 91 includes the subject matter of Example 90, wherein the UE is either radio resource control-connected (RRC_CONNECTED) or RRCJDLE/RRCJNACTIVE.
  • RRC_CONNECTED radio resource control-connected
  • RRCJDLE/RRCJNACTIVE radio resource control-connected
  • Example 92 includes the subject matter of Example 90, further including decoding a downlink control information (DCI) including a radio network temporary identifier for a scrambling of a cyclic redundancy check of the DCI, the DCI to a multicast or broadcast physical downlink shared channel (PDSCH) related to one of: delivery of a configuration or data; or updating of a previous multicast configuration.
  • DCI downlink control information
  • PDSCH broadcast physical downlink shared channel
  • Example 93 includes the subject matter of Example 90, further including decoding a message from the gNB to configure a common search space to monitor a physical downlink control channel (PDCCH) containing scheduling DCI of the multicast or broadcast physical layer transmission.
  • PDCCH physical downlink control channel
  • Example 94 includes the subject matter of Example 93, wherein the common search space (CSS) corresponds to one of: a Type3-PDCCH CSS set along with a multicast RNTI; or a Type 4-PDCCH CSS set specific to monitoring multicast DCI.
  • SCS common search space
  • Example 95 includes the subject matter of Example 94, wherein the scheduling DCI is one of a DCI l_0 or 1_1.
  • Example 96 includes the subject matter of Example 90, the method further including decoding a message from the gNB to configure a UE-specific search space to monitor a physical downlink control channel (PDCCH) containing scheduling DCI of the multicast or broadcast physical layer transmission.
  • PDCCH physical downlink control channel
  • Example 96 includes the subject matter of any one of Examples 90-96, further including configuring the UE with an aggregation level for PDCCH monitoring and a precoder granularity for an associated control resource set (CORESET) configuration based on a UE of the group with a worst coverage.
  • CORESET control resource set
  • Example 97 includes the subject matter of any one of Examples 90-96, wherein the physical layer transmission is one of unicast or multicast, is one of frequency divisional multiplexed, time division multiplexed, or transmitted simultaneously to the UEs on orthogonal demodulation reference signal (DM-RS) ports within a slot.
  • DM-RS orthogonal demodulation reference signal
  • Example 98 includes the subject matter of any one of Examples 90-96, wherein the physical layer transmission is multicast and uses multiple multiple input multiple output (MIMO) layers with rank adaptation.
  • MIMO multiple input multiple output
  • Example 99 includes the subject matter of any one of Examples 90-96, wherein the physical layer transmission is a multicast transmission to be received by the UE on one or more of the same demodulation reference signal (DM-RS) ports.
  • DM-RS demodulation reference signal
  • Example 100 includes the subject matter of any one of Examples 90-96, further including decoding a unicast physical layer transmission co-scheduled along with the multicast physical layer transmission using orthogonal demodulation reference signal (DM-RS) ports not used for the multicast physical layer transmission.
  • DM-RS orthogonal demodulation reference signal
  • Example 101 includes the subject matter of any one of Examples 90-96, wherein the multicast physical layer transmission uses multi-user superposition coding.
  • Example 102 includes a machine readable medium including code, when executed, to cause a machine to perform Example X includes the subject matter of any one of Examples 27-51 and 78-101.
  • Example 103 includes an apparatus including means to perform the method of any one of Examples 27-51 and 78-101.
  • Example 1A may include the system and method for single cell multicast, broadcast or groupcast transmission in NR wherein a group of UEs within the coverage area of the cell receives the same downlink transmission.
  • Example 2A may include the method of example 1A or some other example herein, wherein uplink feedback for CQI and HARQ/ACK can be used to facilitate group transmission.
  • Example 3A may include the methods of examples 1A-2A or some other example herein, wherein both CQI and HARQ/ACK are configurable such that they can be turned off and can be used either individually or in combination with each other.
  • Example 4A may include the method of examples 1A-3A or some other example herein, wherein UEs in the group receiving groupcast may not provide any uplink feedback and they can be configured to receive multiple repetitions of the downlink groupcast transmission where the repetitions can be within a slot, across slots or may cross the slot boundary depending on the PDSCH length.
  • Example 5A may include the method of example 4A or some other example herein, wherein a UE configured to receive multiple repetitions of the downlink groupcast PDSCH may also be configured to provide HARQ/ACK feedback.
  • Example 6A may include the methods of examples 1A-3A or some other example herein, wherein, the UEs in the group receiving the groupcast may transmit both ACK and NACK feedback in the uplink using PUCCH resources.
  • Example 7A may include the methods of examples 1A-3A or some other example herein, wherein the UEs in the group receiving the groupcast may transmit only NACK feedback if the downlink PDSCH transmission is failed.
  • Example 8A may include the method of example 7A or some other example herein, wherein the NACK can be transmitted by all UEs in the group over a shared PUCCH resource.
  • Example 9A may include the method of example 8A or some other example herein, wherein the NACKs of the UEs on the shared PUCCH resource may be multiplexed using UE- specific cyclic shifts.
  • Example 10A may include the methods of examples 1A-9A or some other example herein, wherein for CBG based HARQ retransmission, network coding across retransmission CBs can be used to reduce retransmission overhead such that UEs in the group can use the received CBs as side information to decode their desired CBs from the retransmission similar to the example provided.
  • Example 11A is a method for implementing a gNB groupcast transmission in NR, the method comprising: identifying a downlink transmission; encoding a signal for transmission, the transmission including the identified downlink transmission; and transmitting the encoded signal that includes the downlink transmission to a group of UEs within the coverage area of the cell.
  • Example 12A may include the method of example 11A, or of any other example herein, further comprising: identifying uplink feedback for CQI and HARQ/ACK; and wherein transmitting the encoded signal to the group of UEs further includes transmitting the encoded signal to the group of UEs based at least in part on the identified uplink feedback.
  • Example 13A may include the method of example 11A, or of any other example herein, wherein the CQI and HARQ/ACK are configurable.
  • Example 14A may include the method of example 13A, or of any other example herein, wherein the CQI and HARQ/ACK are configurable further includes turning the CQI and HARQ/ACK off.
  • Example 15A may include the method of example 13A, or of any other example herein, wherein the CQI and HARQ/ACK are configurable further includes a selected one of: using the CQI alone, using the HARQ/ACK alone, or using the CQI and HARQ/ACK in combination with each other.
  • Example 16A may include the method of example 11A, or of any other example herein, further comprising: encoding a second signal for transmission to the UEs, the second signal including configuration instructions to receive multiple repetitions of the downlink transmission to the group of UEs.
  • Example 17A may include the method of example 16A, or of any other example herein, wherein the multiple repetitions of the downlink transmission are performed using a selected one of: within a slot, across slots, cross slot boundary.
  • Example 18A may include the method of example 17A, or of any other example herein, wherein the selection depends at least in part on a PDSCH length.
  • Example 19A may include the method of example 16A, or of any other example herein, wherein the configuration instructions include instructions to provide HARQ/ACK feedback.
  • Example 20A may include the method of example 19A, or of any other example herein, further comprising: receiving a signal from one of the group of UEs, the signal including a ACK and/or NACK feedback using PUCCH resources.
  • Example 21A may include a method for implementing a UE of a plurality of UEs in a group cast transmission in NR, the method comprising: receiving a group cast downlink transmission from a gNB; based upon the received a group cast downlink transmission, encoding a signal that includes uplink feedback for CQI and HARQ/ACK; and transmitting the signal to the gNB.
  • Example 22A may include the subject matter of example 21A, or of any other example herein, wherein the group cast downlink transmission includes configuration information for the UE to receive multiple repetitions of the downlink group cast transmission.
  • Example 23A may include the subject matter of example 22A, or of any other example herein, wherein the multiple repetitions of the downlink group cast transmission may occur over a selected one of: within a slot, across slots, or cross slot boundaries.
  • Example 24A may include the subject matter of example 23A, or of any other example herein, wherein the selections of the multiple repetitions of the downlink group cast transmission are based at least in part on PDSCH links.
  • Example 25A may include the subject matter of example 22A, or of any other example herein, wherein the configuration information includes configuration information for providing HARQ/ACK feedback.
  • Example IB may include the system and method for supporting multicast, broadcast or groupcast transmission within a 5G NR cell wherein a group of users within a cell simultaneously receive the same physical layer transmission mapped to a common service by higher layers.
  • Example 2B may include the method of example IB or some other example herein, wherein the grouping of UEs is determined by higher layer and can contain either RRC_CONNECTED or RRCJDLE/RRCJN ACTIVE UEs or a combination of both types of UEs.
  • Example 3B may include the method of examples 1B-2B or some other example herein, wherein new RNTIs are defined NR for scrambling the CRC of the DCIs which schedule PDSCHs related to delivery of multicast/broadcast configuration and/or data or of the DCIs which provide and update of previous multicast configurations.
  • Example 4B may include the method of examples 1B-3B or some other example herein, wherein common search space is used for monitoring multicast DCI and either NR Type3-PDCCH CSS set configuration is reused with addition of specific multicast RNTIs or a new Type4-PDCCH CSS set configuration is defined specifically for monitoring multicast DCIs.
  • Example 5B may include the method of example 4B or some other example herein, wherein the PDCCH CSS set configuration should allow monitoring of DCI l_0 and 1_1 or alternatively any new multicast DCI format defined in NR.
  • Example 6B may include the method of examples 1B-3B or some other example herein, wherein user specific search space can also be used for monitoring multicast DCI formats.
  • Example 7B may include the methods of examples 1B-6B or some other example herein, wherein the AL for PDCCH monitoring as well as the precoder granularity for the associated CORESET configuration is determined based on the UE in the group with the worst coverage.
  • Example 8B may include the methods of examples 1B-7B or some other example herein, wherein RRC_CONNECTED UEs are able to receive both unicast and multicast transmissions either in FDM, TDM or simultaneously on orthogonal DM-RS ports within a slot.
  • Example 9B may include the methods of examples 1B-8B or some other example herein, wherein multicast transmission can use multiple MIMO layers with rank adaptation.
  • Example 10B may include the methods of examples 1B-9B wherein or some other example herein, UEs receiving multicast transmission share the same DM-RS port(s)
  • Example 11B may include the methods of examples 1B-10B or some other example herein, wherein, unicast transmissions to same or other UEs can be co-scheduled using the orthogonal DM-RS ports which are not used by multicast
  • Example 12B may include the methods of examples 1B-10B or some other example herein, wherein multi-user superposition coding can be used to improve the efficiency of multicast delivery.
  • Example 13B may be a method for implementing a gNB to support multicast, broadcast, or group cast transmission within a NR, the method comprising: encoding a signal for simultaneous transmission to a group of UEs within a cell; and transmitting the encoded signal to the group of UEs, wherein a physical layer transmission is mapped to a common service by higher layers.
  • Example 14B may include the method of example 13B, or of any other example herein, wherein the group of UEs is determined by higher layers.
  • Example 15B may include the method of example 14B, or of any other example herein, wherein each of the UEs includes a selected one of: RRC_CONNECTED, RRCJDLE/RRCJN ACTIVE, or a combination of both.
  • Example 16B may include the method of example 13B, or of any other example herein, further comprising defining RNTIs for scrambling a CRC of DCIs.
  • Example 17B may include the method of example 16B, or of any other example herein, wherein the DCIs are used to schedule PDSCHs related to transmitting the encoded signal.
  • Example 18B may include the method of example 16B, or of any other example herein, wherein the DCIs provide and update previous configurations for UEs.
  • Example 19B may include the method of example 16B, or of any other example herein, further including a common search space, the common search space to monitor multicast DCIs.
  • Example 20B may include the method of example 19B, or of any other example herein, a user specific search space is used to monitor multicast DCI formats.
  • Example 21B may include the method of example 15B, or of any other example herein, wherein RRC_CONNECTED UEs are to receive both unicast and multicast transmissions in a selected one of: FDM, TDM, or simultaneously on orthogonal DM-RS ports within a slot.
  • Example 22B may include the method of example 13B, or of any other example herein, wherein transmitting the encoded signal uses multiple MIMO layers with red ink adaptation.
  • Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 12-23 and 26-45, or any other method or process described herein.
  • Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 12-23 and 26-45, or any other method or process described herein.
  • Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 12-23 and 26-45, or any other method or process described herein.
  • Example Z04 may include a method, technique, or process as described in or related to any of the examples above, or portions or parts thereof.
  • Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of the example above, or portions thereof.
  • Example Z06 may include a signal as described in or related to any of examples 1-8, or portions or parts thereof.
  • Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z08 may include a signal encoded with data as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-8, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-8, or portions thereof.
  • Example Zll may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-8, or portions thereof.
  • Example Z12 may include a signal in a wireless network as shown and described herein.
  • Example Z13 may include a method of communicating in a wireless network as shown and described herein.
  • Example Z14 may include a system for providing wireless communication as shown and described herein.
  • Example Z15 may include a device for providing wireless communication as shown and described herein.
  • any of the above-described Examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise.
  • Aspects described herein can also implement a hierarchical application of the scheme for example, by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g. with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.
  • Some of the features in the present disclosure are defined for network elements (or network equipment) such as Access Points (APs), eNBs, gNBs, core network elements (or network functions), application servers, application functions, etc. Any embodiment discussed herein as being performed by a network element may additionally or alternatively be performed by a UE, or the UE may take the role of the network element (e.g., some or all features defined for network equipment may be implemented by a UE).
  • APs Access Points

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/US2021/045097 2020-08-07 2021-08-06 System and method for reliability improvement in nr multicast transmissions, and for group scheduling in single cell nr multicast transmissions WO2022032189A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202180048652.0A CN115804051A (zh) 2020-08-07 2021-08-06 用于提高nr多播传输的可靠性，以及用于单小区nr多播传输的组调度的系统和方法

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202063063109P 2020-08-07 2020-08-07
US202063062928P 2020-08-07 2020-08-07
US63/063,109 2020-08-07
US63/062,928 2020-08-07

Publications (1)

Publication Number Publication Date
WO2022032189A1 true WO2022032189A1 (en) 2022-02-10

Family

ID=80117717

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/045097 WO2022032189A1 (en) 2020-08-07 2021-08-06 System and method for reliability improvement in nr multicast transmissions, and for group scheduling in single cell nr multicast transmissions

Country Status (2)

Country Link
CN (1) CN115804051A (zh)
WO (1) WO2022032189A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160261391A1 (en) * 2015-03-06 2016-09-08 Qualcomm Incorporated Simplified harq management
US20190268097A1 (en) * 2018-05-11 2019-08-29 Intel Corporation Systems and Methods for Physical Channel Repetition for Low Latency Communication
CN110677222A (zh) * 2018-07-03 2020-01-10 电信科学技术研究院有限公司 一种pdsch重复传输的harq反馈方法及装置
US20200044790A1 (en) * 2018-08-01 2020-02-06 Charter Communications Operating, Llc Disabling hybrid automatic repeat request (harq) acknowledgments for packets for which acknowledgements are supported at network or higher layer
WO2020089858A1 (en) * 2018-11-01 2020-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Lch mapping to harq process id for non-terrestrial networks

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160261391A1 (en) * 2015-03-06 2016-09-08 Qualcomm Incorporated Simplified harq management
US20190268097A1 (en) * 2018-05-11 2019-08-29 Intel Corporation Systems and Methods for Physical Channel Repetition for Low Latency Communication
CN110677222A (zh) * 2018-07-03 2020-01-10 电信科学技术研究院有限公司 一种pdsch重复传输的harq反馈方法及装置
US20200044790A1 (en) * 2018-08-01 2020-02-06 Charter Communications Operating, Llc Disabling hybrid automatic repeat request (harq) acknowledgments for packets for which acknowledgements are supported at network or higher layer
WO2020089858A1 (en) * 2018-11-01 2020-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Lch mapping to harq process id for non-terrestrial networks

Also Published As

Publication number Publication date
CN115804051A (zh) 2023-03-14

Similar Documents

Publication Publication Date Title
CN113473634A (zh) 用于为nr操作配置多小区调度的装置和方法
US20220046677A1 (en) Hybrid automatic repeat request (harq) enhancements for ultra-reliable low latency communication (urllc)
CN113473635A (zh) 用于nr操作的两小区调度
US11950267B2 (en) Mechanisms for transmission of multiple downlink control information
CN115997375A (zh) 在第五代（5g）系统中提供对本地化服务的接入（pals）
CN113825235A (zh) 用于多trp场景中的ul传输的装置和方法
CN113179551A (zh) 用于高速场景的下行链路传输
CN113766665A (zh) 用于多trp场景中基于码本的ul传输的装置和方法
EP4278814A1 (en) New radio multicast and broadcast service mac layer and group scheduling
CN113825234A (zh) 用在用户设备中的装置
CN113285790A (zh) 反馈资源配置的方法
CN114765485A (zh) 用在用户设备中的装置
WO2022154962A1 (en) Mitigation of time-domain overlaps involving transport block over multiple slots transmissions
CN113541902A (zh) 用在用户设备中的装置
WO2022015485A1 (en) Techniques for control channel transmission for slot-less operation and scheduling data transmissions
WO2022032189A1 (en) System and method for reliability improvement in nr multicast transmissions, and for group scheduling in single cell nr multicast transmissions
US20230164670A1 (en) Reduced complexity channel coding for reduced capability new radio user equipment
WO2022032158A1 (en) Mechanisms for pusch and for pucch multi trp repetition
WO2022032212A1 (en) Physical downlink control channel repetition configuration and physical downlink shared channel starting configuration and processing time indication
CN115333683A (zh) 用在通信设备中的装置
CN113852381A (zh) 无线发射机
WO2023154921A1 (en) Reception of new radio (nr) multicast and broadcast service (mbs) control and data in the downlink
JP2024513162A (ja) 新無線ブロードキャスト受信のための方法及び装置
CN114499802A (zh) 用在用户设备中的装置
CN113825233A (zh) 用在用户设备中的装置

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

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

Country of ref document: EP

Kind code of ref document: A1