WO2022087620A1 - Rétroaction harq-ack pour transmissions pdsch de multidiffusion - Google Patents

Rétroaction harq-ack pour transmissions pdsch de multidiffusion Download PDF

Info

Publication number
WO2022087620A1
WO2022087620A1 PCT/US2021/071972 US2021071972W WO2022087620A1 WO 2022087620 A1 WO2022087620 A1 WO 2022087620A1 US 2021071972 W US2021071972 W US 2021071972W WO 2022087620 A1 WO2022087620 A1 WO 2022087620A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
ack feedback
rrc
mbs
transmissions
Prior art date
Application number
PCT/US2021/071972
Other languages
English (en)
Inventor
Debdeep CHATTERJEE
Alexei Davydov
Yingyang Li
Avik SENGUPTA
Gang Xiong
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 EP21884104.7A priority Critical patent/EP4233243A1/fr
Publication of WO2022087620A1 publication Critical patent/WO2022087620A1/fr

Links

Classifications

    • 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/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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • 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
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint

Definitions

  • Some embodiments relate to wireless networks including 3GPP (Third Generation Partnership Project) and fifth-generation (5G) networks including 5Gnew radio (NR) (or 5G-NR) networks.
  • 5G fifth-generation
  • 5G-NR 5Gnew radio
  • Some embodiments pertain to hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback for broadcast-multicast service (MBS) transmissions from a generation Node B (gNB) via a physical downlink shared channel (PDSCH) in a 5G NR networks.
  • HARQ hybrid automatic repeat request
  • ACK acknowledgement
  • MMS broadcast-multicast service
  • mmWave millimeter wave
  • FIG. 1A illustrates an architecture of a network, in accordance with some embodiments.
  • FIG. IB and FIG. 1C illustrate a non-roaming 5G system architecture in accordance with some embodiments.
  • FIG. 2 is a functional block diagram of a wireless communication device in accordance with some embodiments.
  • Some embodiments are directed to a User Equipment (UE) configured for operation in a 5G NR network.
  • UE User Equipment
  • MBS single-cell broadcast-multicast service
  • gNB generation Node B
  • PDSCH physical downlink shared channel
  • the UE may decode UE-specific radio-resource control (RRC) signalling to configure the UE to provide hybrid automatic repeat request acknowledge (HARQ-ACK) feedback for the MBS transmissions.
  • RRC radio-resource control
  • the UE may encode the HARQ-ACK feedback for the MBS transmissions for transmission via a physical uplink control channel (PUCCH) resource to the gNB when the UE is in an RRC_CONNECTED state.
  • PUCCH physical uplink control channel
  • the UE may include memory to store an RRC configuration for the HARQ-ACK feedback for the MBS transmissions.
  • the RRC signalling configures the UE with a dedicated PUCCH resource from a PUCCH resource set for the HARQ-ACK feedback for the MBS transmissions.
  • the HARQ-ACK feedback may include ACK and negative acknowledge (NACK) feedback.
  • the UE may refrain from providing the HARQ-ACK feedback for the MBS transmissions when the UE is in an RRC IDLE or an RRC INACTIVE state (i.e., when the UE is not in the RRC CONNECTED state).
  • the HARQ-ACK feedback for the MBS transmissions is a first uplink control information (UCI) type.
  • the UE may drop one of the PUCCH resources depending on a priority order of the UCI types.
  • the UE may decode signalling that dynamically switches on and switches off the HARQ-ACK feedback for the MBS transmissions for the UE when in the RRC CONNECTED state.
  • the UE may decode RRC signalling from the gNB to enable HARQ-ACK feedback with NACK only transmissions on a shared PUCCH resource configured by the gNB for a group of more than one UE.
  • one of PUCCH format 0 or PUCCH format 1 may be used for the NACK only feedback mode.
  • the UE is configured to use one of a Type 1 and a Type 2 HARQ-ACK codebook for the HARQ-ACK feedback for the MBS transmissions and a different HARQ-ACK codebook for HARQ-ACK feedback for unicast transmissions.
  • the UE may multiplex the HARQ-ACK feedback on the PUSCH.
  • the UE may provide the HARQ-ACK feedback for the MBS transmissions in accordance with on the stored RRC configuration for the HARQ-ACK feedback for the MBS transmissions.
  • the UE may provide the HARQ-ACK feedback for the MBS transmissions, in accordance with on the stored RRC configuration for HARQ-ACK feedback for the MBS transmissions when conditions are met. In some of these embodiments, the UE may be configured to refrain from providing the HARQ-ACK feedback for the MBS transmissions when the conditions are not met.
  • the conditions are met when: the UE is still camping a same cell when last in the RRC CONNECTED state; a difference in DL RSRP from when the UE was last in the RRC CONNECTED state is less than a configured RSRP threshold; and a time since the UE was last in the RRC_CONNECTED state is less than a configured time threshold.
  • the UE may drop the PUCCH carrying the HARQ-ACK feedback for the MBS transmissions.
  • the UE when the UE is in an RRC IDLE or an RRC INACTIVE state, the UE may refrain from providing the HARQ-ACK feedback via the PUCCH resource for the MBS transmissions and may provide NACK only feedback via a PRACH using one or more PRACH preambles. In these embodiments, the UE may provide only NACK feedback on the PRACH and does not provide HARQ-ACK.
  • Some embodiments are directed to a non-transitory computer- readable storage medium that stores instructions for execution by processing circuitry to perform operations to configure a UE to provide hybrid automatic repeat request acknowledge (HARQ-ACK) feedback for reception of single-cell broadcast-multicast service (MBS) transmissions from a generation Node B (gNB) via a physical downlink shared channel (PDSCH) when the UE is in an RRC CONNECTED state.
  • HARQ-ACK hybrid automatic repeat request acknowledge
  • MMS broadcast-multicast service
  • gNB generation Node B
  • PDSCH physical downlink shared channel
  • Some embodiments are directed to a generation node B (gNB) configured for operation in a 5G NR network.
  • the gNB for singlecell broadcast-multicast service (MBS) transmissions via a PDSCH to a plurality of UEs, the gNB is configured to encode UE-specific RRC signalling to configure the UEs of the plurality that are in an RRC CONNECTED state for HARQ-ACK feedback, the HARQ-ACK feedback for the MBS transmissions.
  • the gNB may decode the HARQ-ACK feedback for the MBS transmissions from the UEs, received via a PUCCH resource.
  • the RRC signalling configures the UEs with a dedicated PUCCH resource from a PUCCH resource set for the HARQ- ACK feedback for the MBS transmissions.
  • the HARQ-ACK feedback may include positive ACK and negative acknowledge (NACK) feedback.
  • NACK negative acknowledge
  • the gNB does not expect HARQ-ACK feedback for the MBS transmissions when the UEs are in an RRC IDLE or an RRC INACTIVE state.
  • FIG. 1 A illustrates an architecture of a network in accordance with some embodiments.
  • the network 140 A is shown to include user equipment (UE) 101 and UE 102.
  • the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface.
  • PDAs Personal Data Assistants
  • the UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.
  • LTE and LTE- Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones.
  • carrier aggregation is a technology according to which multiple carrier signals operating on different frequencies may be used to carry communications for a single UE, thus increasing the bandwidth available to a single device.
  • carrier aggregation may be used where one or more component carriers operate on unlicensed frequencies.
  • Embodiments described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).
  • LSA Licensed Shared Access
  • SAS Spectrum Access System
  • Embodiments described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.
  • CP-OFDM Single Carrier or OFDM flavors
  • SC-FDMA SC-FDMA
  • SC-OFDM filter bank-based multicarrier
  • OFDMA filter bank-based multicarrier
  • 3GPP NR New Radio
  • any of the UEs 101 and 102 can comprise an Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections.
  • any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB- loT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB- loT
  • FeNB-IoT Further Enhanced
  • An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity -Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.
  • any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
  • eMTC enhanced MTC
  • FeMTC enhanced MTC
  • the UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110.
  • the RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), aNextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to- Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to- Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth-generation
  • NR New Radio
  • the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105.
  • the ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 102 is shown to be configured to access an access point (AP) 106 via connection 107.
  • the connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi) router.
  • WiFi wireless fidelity
  • the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 110 can include one or more access nodes that enable the connections 103 and 104.
  • ANs access nodes
  • BSs base stations
  • eNBs evolved NodeBs
  • gNBs Next Generation NodeBs
  • RAN nodes and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the communication nodes 111 and 112 can be transmission/reception points (TRPs).
  • TRPs transmission/reception points
  • the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs)
  • one or more TRPs can function within the communication cell of the NodeBs.
  • the RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro-RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.
  • macro-RAN node 111 e.g., macro-RAN node 111
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • any of the nodes 111 and/or 112 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of RAN node.
  • gNB Node-B
  • eNB evolved node-B
  • the RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113.
  • the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C).
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.
  • S-GW serving gateway
  • MME Sl-mobility management entity
  • the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124.
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 121 may manage mobility embodiments in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120.
  • the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility.
  • Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a PDN.
  • the P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • the P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks.
  • the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125.
  • the application server 184 can also be configured to support one or more communication services (e.g., Voice-over- Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.
  • VoIP Voice-over- Internet Protocol
  • the P-GW 123 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120.
  • PCRF Policy and Charging Rules Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • PCRFs there may be two PCRFs associated with a UE's IP- CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN).
  • the PCRF 126 may be communicatively coupled to the application server 184 via the P- GW 123.
  • the communication network 140 A can be an loT network or a 5G network, including 5G new radio network using communications in the licensed (5GNR) and the unlicensed (5GNR-U) spectrum.
  • One of the current enablers of loT is the narrowband-IoT (NB-IoT).
  • An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120.
  • the NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs.
  • the core network 120 e.g., a 5G core network or 5GC
  • AMF access and mobility function
  • UPF user plane function
  • the AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some embodiments, the gNBs and the NG-eNBs can be connected to the AMF by NG- C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.
  • the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12).
  • TS 3GPP Technical Specification
  • each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
  • MN master node
  • SN secondary node
  • FIG. IB illustrates a non-roaming 5G system architecture in accordance with some embodiments.
  • a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities.
  • 5GC 5G core
  • the 5G system architecture 140B includes a plurality of network functions (NFs), such as access and mobility management function (AMF) 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)Zhome subscriber server (HSS) 146.
  • the UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services.
  • DN data network
  • the AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality.
  • the SMF 136 can be configured to set up and manage various sessions according to network policy.
  • the UPF 134 can be deployed in one or more configurations according to the desired service type.
  • the PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system).
  • the UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).
  • the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B.
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B.
  • the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain embodiments of emergency sessions such as routing an emergency request to the correct emergency center or PSAP.
  • the I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area.
  • the I-CSCF 166B can be connected to another IP multimedia network 170E (e.g., an IMS operated by a different network operator).
  • the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS).
  • the AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.
  • FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Ni l (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM
  • FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation.
  • system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.
  • NEF network exposure function
  • NRF network repository function
  • 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.
  • service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services.
  • 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), aNudm 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AU
  • any of the UEs or base stations described in connection with FIGS. 1A-1C can be configured to perform the functionalities described herein.
  • NR next generation wireless communication system
  • 5G next generation wireless communication system
  • NR new radio
  • 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions.
  • RATs Radio Access Technologies
  • NR-unlicensed a short-hand notation of the NR-based access to unlicensed spectrum, is a technology that enables the operation of NR systems on the unlicensed spectrum.
  • Embodiments herein relate to 3GPP 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.
  • the Rel-17 WID [1] has the following objectives with respect to physical layer enhancements to support reliability improvements in multicast and broadcast transmissions in NR:
  • This disclosure proposes HARQ feedback schemes and related configuration options for NR MBS for both RRC CONNECTED and RRC IDLE/INACTIVE UEs.
  • 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.
  • HARQ feedback can be configured on and off for UE in RRC CONNECTED, RRC IDLE or RRC INACTIVE mode.
  • HARQ-ACK feedback in response to multicast PDSCH may be limited to UEs in RRC CONNECTED mode and the configuration of HARQ on/off can be semi-static, provided via UE-specific RRC signaling.
  • the UE can retain such configuration from RRC signaling in CONNECTED state.
  • HARQ-ACK feedback configuration provided to the UE via dedicated RRC configuration in prior CONNECTED state may be reused by a UE in RRC INACTIVE or RRC IDLE modes only when one or more of the following conditions are satisfied:
  • the UE is still camping on the same cell as when it was last in RRC CONNECTED mode;
  • the difference in the DL RSRP from when the UE was last in RRC CONNECTED mode is within a specified or configured threshold
  • the time since the UE was in RRC CONNECTED state is within a specified or configured threshold.
  • the RRC IDLE/INACTIVE UEs can be configured with HARQ feedback on or off through RMSI signaling.
  • RRC INACTIVE/IDLE UEs may transmit PUCCH with HARQ- ACK feedback using a timing advance (TA) value of 0, e.g., following DL timing.
  • TA timing advance
  • the HARQ-ACK feedback in response to multicast PDSCH is defined by NACK-only feedback and is carried by a configured PRACH format and using a preamble from a set of one or more PRACH preambles that may be configured for the corresponding PRACH format.
  • the configuration of HARQ on/off for a multicast PDSCH can be dynamically indicated to the UEs through a single bit in the DCI scheduling the multicast PDSCH.
  • multicast PDSCH group common PDSCH
  • MCS PDSCH MBS PDSCH
  • the same mode of HARQ-ACK feedback (e.g., either NACK-only or differentiating ACK and NACK) is configured for all RRC_CONNECTED and
  • a RRC CONNECTED UE supports HARQ operation with both ACK and NACK feedback over a dedicated PUCCH resource from a PUCCH resource set configured by RRC signaling.
  • the PUCCH resource indicator is common for all the UEs in the group receiving the multicast transmission but can point to different PUCCH resources based on configuration of the UE-specific PUCCH resource set.
  • RRC CONNECTED and RRC IDLE/INACTIVE UEs support HARQ feedback with NACK only transmission on the PUCCH.
  • NACK only feedback mode can be enabled in an SFN like manner wherein multiple UEs transmit NACK only signal on a shared PUCCH resource.
  • the gNB can configure a common PUCCH resource to the group of UEs. The common resource needs to be indicated by the same PRI and hence should be mapped to the same index for all UEs receiving the groupcast transmission.
  • the NACK only feedback mode can be supported on pre-defined cell-specific PUCCH resource set from which 4 bit-RMSI indication selects 16 cell-specific resources and DCI indicates the PUCCH resource using the PRI and starting CCE index used for receiving the scheduling PDCCH.
  • RRC IDLE/INACTIVE UEs may be configured to report NACK-only based HARQ- ACK feedback using PUCCH resources that are separately configured for RRC CONNECTED UEs.
  • PUCCH resources for RRC CONNECTED UEs may be provided separately from those for RRC INACTIVE/IDLE UEs.
  • separate PUCCH resources for the NACK-only based HARQ-ACK feedback could be configured for a UE that is synchronized to gNB in uplink and a UE that is not synchronized to gNB in uplink.
  • the above separate PUCCH resources may have different PUCCH formats. Specifically, a legacy PUCCH format may be configured for a UE synchronized in uplink, while a PRACH resource may be configured for a UE not synchronized in uplink.
  • the configured PUCCH resource can additionally include the indication to the UE for NACK only transmission which tells the UE to transmit only NACK on the configured resource.
  • X number of additional HARQ process IDs are defined in addition to current number of unicast HARQ processes.
  • the value of X can be 2.
  • NR MBS shares the 16 HARQ process defined in Rel-15 NR for unicast transmission.
  • which HARQ processes are used for NR MBS can be configured by higher layers via RRC signalling or predefined in the specification.
  • the first Y HARQ process IDs within unicast HARQ processes can be used for NR MBS.
  • one field in the DCI may be included to indicate whether the scheduled PDSCH is for MBS or unicast transmission.
  • some known states in one or more existing fields in the DCI format 1 0, 1 1 or 1 2 may be used to indicate whether the scheduled PDSCH is for MBS or unicast transmission.
  • NR MBS uses a separate Type 1 and Type 2 HARQ-ACK codebook compared to unicast transmission.
  • Type 1 and Type 2 HARQ-ACK codebook may include HARQ-ACK feedback of MBS transmission. Further, ordering of HARQ-ACK feedback for MBS transmission may be predefined in the specification. For example, HARQ-ACK feedback of MBS transmission may correspond to the MSB or LSB bits in the HARQ-ACK codebook. [0080] In another embodiment, if PUCCH resource carrying HARQ- ACK feedback for NR MBS overlaps in time with a PUCCH carrying HARQ ACK information for a unicast transmission, the PUCCH carrying the MBS HARQ feedback is dropped.
  • PUCCH carrying HARQ-ACK feedback of MBS service overlaps with one or more PUCCHs carrying same or other UCI types, including CSI report and SR
  • PUCCH carrying HARQ-ACK feedback of MBS is dropped.
  • whether to drop one or more PUCCHs may depend on the priority order of UCI type.
  • the priority order of UCI ordering may be defined as in a descending ordering as HARQ-ACK feedback of unicast transmission > HARQ-ACK feedback of MBS transmission > SR > CSI report, where HARQ- ACK feedback of unicast transmission is considered as highest order.
  • UE shall transmit PUCCH carrying HARQ-ACK feedback of MBS and drop PUCCH carrying SR.
  • the existing UCI multiplexing mechanism as defined in Rel-15 and Rel-16 may be reused in case of timedomain overlaps with PUSCH or PUCCH.
  • NACK is used for HARQ-ACK feedback of MBS transmission when the HARQ-ACK feedback is not overlapped with a PUSCH or PUCCH. Otherwise, in case of time-domain overlaps with a PUSCH or PUCCH a, the HARQ-ACK feedback of MBS transmission can be multiplexed with the PUSCH or PUCCH.
  • the existing UCI multiplexing mechanism as defined in Rel-15 and Rel-16 may be reused. In the latter case, UE can report ACK or NACK based on the reception status of the MBS transmission.
  • PUCCH resource carrying HARQ-ACK feedback of MBS transmission can be considered as lower priority. More specifically, when PUCCH resource carrying HARQ-ACK feedback of MBS transmission overlaps with PUSCH or PUCCH with higher priority, PUCCH resource carrying HARQ-ACK feedback of MBS transmission is dropped.
  • simultaneous reception of group common PDSCH and unicast PDSCH may be supported by a UE as an optional UE capability when the PDSCHs are multiplexed at least in frequency domain.
  • simultaneous reception of group common and unicast PDSCHs is supported only when the group common PDSCH is scheduled with a transport block size (TBS) less than a specified value TBSmax MBS.
  • TBSmax MBS may be reported by the UE as part of UE capability reporting, that may be reported per frequency band or band combination or per UE.
  • simultaneous reception of MBS PDSCH and legacy broadcast/groupcast PDSCH may be supported by a UE as an optional UE capability when the PDSCHs are multiplexed at least in frequency domain.
  • simultaneous reception of MBS and legacy broadcast/groupcast PDSCHs is supported only when the MBS PDSCH is scheduled with a TBS less than a specified value X.
  • the value of X may be reported by the UE as part of UE capability reporting, that may be reported per frequency band or band combination or per UE.
  • simultaneous reception of MBS and legacy broadcast/groupcast PDSCHs is supported only when the MBS PDSCH is scheduled with a TBS less than a value XI and the legacy broadcast/multicast PDSCH is scheduled with a TBS less than a value X2.
  • XI and X2 can be the same.
  • XI and X2 can be predefined or configured by high layer signaling or may be reported by the UE as part of UE capability reporting.
  • the minimum UE processing time for processing of a group common PDSCH and transmission of PUCCH or PUSCH with HARQ-ACK feedback follows the minimum UE processing time per Capability #1 as defined in Rel-15 NR specifications.
  • the additional margin of ‘d_MBS’ symbols is applied only when the group common PDSCH may overlap with a unicast PDSCH with an overlap of at least one OFDM symbol.
  • FIG. 2 illustrates a functional block diagram of a wireless communication device, in accordance with some embodiments.
  • Wireless communication device 200 may be suitable for use as a UE or gNB configured for operation in a 5GNR network.
  • the communication device 200 may include communications circuitry 202 and a transceiver 210 for transmitting and receiving signals to and from other communication devices using one or more antennas 201.
  • the communications circuitry 202 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals.
  • the communication device 200 may also include processing circuitry 206 and memory 208 arranged to perform the operations described herein.
  • the communications circuitry 202 and the processing circuitry 206 may be configured to perform operations detailed in the above figures, diagrams, and flows.
  • the communications circuitry 202 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium.
  • the communications circuitry 202 may be arranged to transmit and receive signals.
  • the communications circuitry 202 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc.
  • the processing circuitry 206 of the communication device 200 may include one or more processors.
  • two or more antennas 201 may be coupled to the communications circuitry 202 arranged for sending and receiving signals.
  • the memory 208 may store information for configuring the processing circuitry 206 to perform operations for configuring and transmitting message frames and performing the various operations described herein.
  • the memory 208 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer).
  • the memory 208 may include a computer-readable storage device, read-only memory (ROM), randomaccess memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.
  • the communication device 200 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • PDA personal digital assistant
  • laptop or portable computer with wireless communication capability such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • the communication device 200 may include one or more antennas 201.
  • the antennas 201 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals.
  • a single antenna with multiple apertures may be used instead of two or more antennas.
  • each aperture may be considered a separate antenna.
  • MIMO multiple-input multiple-output
  • the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting device.
  • the communication device 200 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements.
  • the display may be an LCD screen including a touch screen.
  • the communication device 200 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • DSPs digital signal processors
  • some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements of the communication device 200 may refer to one or more processes operating on one or more processing elements.
  • Example 1 may include a method for HARQ-ACK feedback indication for multicast PDSCH reception by a group of UEs where UEs in the group are possibly in RRC CONNECTED mode or RRC IDLE/IN ACTIVE mode.
  • Example 2 may include the method of example 1 or some other example herein, wherein the HARQ feedback can be configured on and off.
  • Example 3 may include the method of examples 1-2 or some other example herein, wherein the HARQ feedback may limited to RRC CONNECTED UEs and the configuration of HARQ feedback can be semi-static through UE specific RRC signaling.
  • Example 4 may include the method of examples 1-2 or some other example herein, wherein RRC INACTIVE or IDLE UEs can retain such configuration from a prior RRC CONNECTED mode indication for example when the UE is still camped on the same cell, has a Ll-RSRP difference below a configured threshold and the time since the UE was in RRC CONNECTED mode is below a configured threshold.
  • Example 5 may include the method of examples 1-2 or some other example herein, wherein the configuration can be through RMSI or dynamically via a bit in DCI.
  • Example 6 may include the method of examples 1-5 or some other example herein, wherein the UEs can transmit HARQ feedback using a TA value of 0 e.g., following DL Timing.
  • Example 7 may include the method of examples 1-6 or some other example herein, wherein the feedback mode can be ACK/NACK based or NACK only for RRC CONNECTED UEs and NACK-only for
  • RRC INACTIVE/IDLE mode UEs and the mode of feedback is configurable to the UEs either explicitly by RRC or SIB or implicitly through PUCCH resource configuration which includes additionally the feedback mode.
  • Example 8 may include the method of example 7 or some other example herein, wherein the NACK only feedback can be provided over cellspecific PUCCH resource for RRC CONNECTED/IDLE/INACTIVE UEs and over UE specifically configured PUCCH resources for RRC CONNECTED UEs.
  • Example 9 may include the method of example 8 or some other example herein, wherein PUCCH format 0 and 1 can be used for NACK only feedback mode.
  • Example 10 may include the methods of examples 1-9 or some other example herein, wherein MBS specific HARQ process IDs can be configured, which may be in addition to the existing 16 HARQ processes for unicast transmission.
  • Example 11 may include the methods of examples 1-10 or some other example herein, wherein MBS uses separate HARQ-ACK codebook compared to unicast transmission.
  • Example 12 may include the methods of examples 1-11 or some other example herein, wherein PUCCH resource carrying the HARQ-ACK feedback for MBS has lower priority than unicast.
  • Example 13 may include the methods of examples 1-12 or some other example herein wherein the UE processing time for a group common PDSCH and transmission of PUCCH with HARQ-ACK feedback is determined based on UE processing time Capability 1 with a potentially additional margin for MBS when MBS PDSCH overlaps with unicast PDSCH.
  • Example 14 may include a method comprising: receiving configuration information for HARQ feedback for receiving a multicast PDSCH; and receiving an indication of whether the HARQ feedback is on or off.
  • Example 15 may include the method of example 14 or some other example herein, further comprising turning off the HARQ feedback when the UE is in an RRC INACTIVE state and/or a RRC IDLE state.
  • Example 16 may include the method of example 15 or some other example herein, further comprising retaining the configuration information while the UE is in the RRC IN ACTIVE state and/or a RRC IDLE state and using the configuration information when the UE enters a RRC CONNECTED state.
  • Example 17 may include the method of example 14-16 or some other example herein, further comprising receiving the multicast PDSCH; and providing HARQ feedback or determining not to provide HARQ feedback based on the indication.

Landscapes

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

Abstract

L'invention concerne un équipement utilisateur (UE) destiné à fonctionner dans un réseau de nouvelle radio de cinquième génération (5G NR) est configuré pour fournir un retour d'information de demande de répétition automatique hybride (HARQ-ACK) pour la réception de transmissions de service de diffusion et de multidiffusion à cellule unique (MBS) provenant d'un nœud de génération B (gNB) via un canal physique partagé de liaison descendante (PDSCH) (c'est-à-dire des transmissions PDSCH de multidiffusion) lorsque l'UE est dans un état RRC CONNECTED. L'UE peut s'abstenir de fournir le retour d'information HARQ-ACK pour les transmissions MBS lorsque l'UE est dans un état RRC IDLE ou RRC INACTIVE.
PCT/US2021/071972 2020-10-23 2021-10-21 Rétroaction harq-ack pour transmissions pdsch de multidiffusion WO2022087620A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP21884104.7A EP4233243A1 (fr) 2020-10-23 2021-10-21 Rétroaction harq-ack pour transmissions pdsch de multidiffusion

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063105120P 2020-10-23 2020-10-23
US63/105,120 2020-10-23

Publications (1)

Publication Number Publication Date
WO2022087620A1 true WO2022087620A1 (fr) 2022-04-28

Family

ID=81290108

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/071972 WO2022087620A1 (fr) 2020-10-23 2021-10-21 Rétroaction harq-ack pour transmissions pdsch de multidiffusion

Country Status (2)

Country Link
EP (1) EP4233243A1 (fr)
WO (1) WO2022087620A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230071767A1 (en) * 2020-11-24 2023-03-09 Ofinno, Llc Group Scheduling of Multicast and Broadcast Services

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090286468A1 (en) * 2006-08-23 2009-11-19 Electronics And Telecommunications Research Institute Mbms data transmission and receiving in packet based on cellular system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090286468A1 (en) * 2006-08-23 2009-11-19 Electronics And Telecommunications Research Institute Mbms data transmission and receiving in packet based on cellular system

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CMCC: "Discussion on reliability improvement in NR MBS", 3GPP DRAFT; R1-2006234, vol. RAN WG1, 7 August 2020 (2020-08-07), pages 1 - 5, XP051915272 *
HUAWEI, HISILICON: "Mechanisms to improve reliability for RRC_CONNECTED UEs", 3GPP DRAFT; R1-2005250, vol. RAN WG1, 8 August 2020 (2020-08-08), pages 1 - 4, XP051917298 *
INTEL CORPORATION: "Mechanisms to Improve Reliability of NR MBS", 3GPP DRAFT; R1-2005899, vol. RAN WG1, 8 August 2020 (2020-08-08), pages 1 - 4, XP051917801 *
LG ELECTRONICS INC.: "Mechanisms to improve Reliability of Broadcast/Multicast service", 3GPP DRAFT; R1-2006321, vol. RAN WG1, 7 August 2020 (2020-08-07), pages 1 - 3, XP051915301 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230071767A1 (en) * 2020-11-24 2023-03-09 Ofinno, Llc Group Scheduling of Multicast and Broadcast Services
US11817960B2 (en) * 2020-11-24 2023-11-14 Ofinno, Llc Group scheduling of multicast and broadcast services

Also Published As

Publication number Publication date
EP4233243A1 (fr) 2023-08-30

Similar Documents

Publication Publication Date Title
US11888592B2 (en) UE configured for multiplexing HARQ-ACK bits of different priorities in a PUCCH transmission
US11871423B2 (en) Transmission on a PCell scheduled by an SCell PDCCH in a 5G NR network
US11838915B2 (en) One-shot feedback and SCell dormancy behavior in 5G NR networks
US11457511B2 (en) Enhanced downlink semi-persistent scheduling (SPS)
US20240155636A1 (en) Multi-slot pdcch monitoring in search space sets for higher carrier frequency operation
EP4201007A1 (fr) Indication de taille de faisceau de répétitions pour des transmissions de liaison montante dans un réseau nr 5g
US20220104235A1 (en) Aperiodic csi-rs resource set triggering by dci with aperiodic triggering offset
WO2022146637A1 (fr) Capacité d'équipement utilisateur (ue) pour un nombre maximal d'instances d'intervalle d'un motif d'intervalles simultanés multiples
EP4233243A1 (fr) Rétroaction harq-ack pour transmissions pdsch de multidiffusion
WO2022031617A1 (fr) Indication dmrs dans des créneaux spéciaux permettant des opérations de spectre non appariées
US20240114507A1 (en) Multi-tti scheduling of pdsch and pusch by dci
US20240155637A1 (en) Dci format configured for varied bit interpretations
US20240163026A1 (en) Type-1 harq-ack codebook generation for multi-pdsch scheduling
US20240187190A1 (en) Out-of-order handling for tboms scheduling in 5g nr
US20240163868A1 (en) Configured grant based small data transmission (cg-sdt) in multibeam operation
US20240014995A1 (en) Timing for non-overlapping sub-band full duplex (sbfd) operations in 5g nr
US20240172243A1 (en) Sounding reference signal (srs) transmissions triggered via downlink control information (dci) formats without scheduling information
WO2023158672A1 (fr) Transmission de canal pdsch basée sur accusé de réception harq-ack planifiée par plusieurs attributions de liaison descendante
WO2022087619A1 (fr) Hiérarchisation et multiplexage de pucch et pusch pour une transmission inter-porteuses
WO2023081161A1 (fr) Gestion de panne pour la programmation de tboms dans un nr 5g
EP4275384A1 (fr) Ue configurable pour prendre en charge de multiples intervalles de mesure
WO2024030378A1 (fr) Capacité d'ue pour des mesures inter-rat sans intervalles de mesure
WO2022150371A1 (fr) Harq-ack avec groupage dans le domaine temporel pour pdsch ordonnancés par dci à multi-tti
EP4278795A1 (fr) Bande passante de transmission de pucch étendue pour opération à fréquence porteuse élevée
WO2024030434A1 (fr) Détection de défaillance de faisceau et test de récupération de liaison pour une opération multi-trp

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021884104

Country of ref document: EP

Effective date: 20230523