WO2022051738A1 - Rétroaction harq pour transmissions de données de liaison descendante - Google Patents

Rétroaction harq pour transmissions de données de liaison descendante Download PDF

Info

Publication number
WO2022051738A1
WO2022051738A1 PCT/US2021/071014 US2021071014W WO2022051738A1 WO 2022051738 A1 WO2022051738 A1 WO 2022051738A1 US 2021071014 W US2021071014 W US 2021071014W WO 2022051738 A1 WO2022051738 A1 WO 2022051738A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdsch
harq
dci
dai
ack feedback
Prior art date
Application number
PCT/US2021/071014
Other languages
English (en)
Inventor
Yingyang Li
Gang Xiong
Daewon Lee
Alexei Davydov
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
Publication of WO2022051738A1 publication Critical patent/WO2022051738A1/fr

Links

Classifications

    • 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/1854—Scheduling and prioritising 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/1607—Details of the supervisory signal
    • H04L1/1614—Details of the supervisory signal using bitmaps
    • 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/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0219—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave where the power saving management affects multiple terminals

Definitions

  • aspects pertain to wireless communications. Some aspects relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3 GPP LTE (Long Term Evolution) networks, 3 GPP LTE-A (LTE Advanced) networks, (MulteFire, LTE-U), and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks such as 5G NR unlicensed spectrum (NR-U) networks and other unlicensed networks including Wi-Fi, CBRS (OnGo), etc.
  • 5G networks including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks such as 5G NR unlicensed spectrum (NR-U) networks and other unlicensed networks including Wi-Fi, CBRS (OnGo), etc.
  • Other aspects are directed to systems and methods for hybrid automatic repeat request (HAR.Q) acknowledgment (HARQ- ACK) feedback for physical downlink shared channel (PDSCH) transmission with early termination. Additional aspects are related to early feedback of downlink data transmissions.
  • LTE-NR networks will continue to evolve based on 3GPP LTE- Advanced with additional potential new radio access technologies (RATs) to enrich people’s lives with seamless wireless connectivity solutions delivering fast, rich content and services.
  • RATs new radio access technologies
  • Potential LTE operation in the unlicensed spectrum includes (and is not limited to) the LTE operation in the unlicensed spectrum via dual connectivity (DC), or DC-based LAA, and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in the unlicensed spectrum without requiring an “anchor” in the licensed spectrum, called MulteFire.
  • MulteFire combines the performance benefits of LTE technology with the simplicity of Wi-Fi-like deployments,
  • FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.
  • FIG. IB and FIG. 1C illustrate a non-roaming 5G system architecture in accordance with some aspects.
  • FIG. 2, FIG. 3, and FIG. 4 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG. 5 is an illustration of a long PDSCH transmission duration, according to an example embodiment.
  • FIG. 6 is an illustration of early termination of a PDSCH transmission, according to an example embodiment.
  • FIG. 7, FIG. 8, FIG. 9, and FIG. 10 are illustrations of a PDSCH to HARQ feedback timing, according to example embodiments.
  • FIG. 11 is an illustration of the determination of PUCCH timing, according to an example embodiment.
  • FIG. 12 and FIG. 13 are illustrations of counter downlink assignment index (C-DAI) determination, according to example embodiments.
  • FIG. 14 and FIG. 15 are illustrations of early ACK feedback to PDCCH, according to example embodiments.
  • FIG. 16 and FIG. 17 are illustrations of early HARQ-ACK feedback for first PDSCH(s), according to example embodiments.
  • FIG. 18 is an illustration of a PDCCH retransmission scheduling all PDSCH(s), according to an example embodiment.
  • FIG. 19 is an illustration of PDCCH retransmission that does not schedule the first PDSCH(s), according to an example embodiment.
  • FIG. 20 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB) (or another RAN node), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), in accordance with some aspects.
  • eNB evolved Node-B
  • gNB new generation Node-B
  • AP access point
  • STA wireless station
  • MS mobile station
  • UE user equipment
  • FIG. 1A illustrates an architecture of a network in accordance with some aspects.
  • the network 140A is shown to include user equipment (LIE)
  • LIE user equipment
  • 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 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
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets wireless handsets
  • drones or any other computing device including a wired and/or wireless communications interface.
  • UE 101 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.
  • Any of the radio links described herein may operate according to any exemplary radio communication technology and/or standard.
  • 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 cany 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.
  • aspects 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
  • any of the UEs 101 and 102 can comprise an Intemet-of-Things (loT) UE or a Cellular lo'T (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections.
  • any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB-IoT
  • 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., keepalive 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, a Universal Mobile Telecommunications System (UMTS), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • 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 1 10 can include one or more access nodes that enable connections 103 and 104.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN network 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 11 1 and 112 can be transmission/reception points (TRPs).
  • the RAN 110 may include one or more ILAN nodes for providing macrocells, e.g., macro RAN node 11 1, 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 or an unlicensed spectrum based secondary RAN node 112.
  • 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 user traffic data between the RAN nodes 111 and 1 12 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which i s 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 aspects 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 termmate the SI interface 113 towards the RAN 110, and route data packets between the RAN 110 and the C’N 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-3GPP mobility. Other responsibilities of the S-GW 122 may include 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 sendees (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
  • the PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.
  • the communication network 140A can be an loT network or a 5G network, including a 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
  • NB-IoT narrowband-IoT
  • An NG system architecture can include the RAN 1 10 and a 5G network core (5GC) 120.
  • the NG-RAN 110 can include a plurality of nodes, such as yNBs 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 aspects, 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, a RAN network node, and so forth.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
  • the master/primary node may operate in a licensed band and the secondary node may operate in an unlicensed band.
  • FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • 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)/home 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.
  • IMS IP multimedia subsystem
  • CSCFs call session control functions
  • P-CSCF proxy CSCF
  • S-CSCF seiwing CSCF
  • E-CSCF emergency CSCF
  • I-CSCF interrogating CSCF
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the W 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 aspects 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 UDMZHSS 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 1 10 and the AMF 132), N3 (between the RAN 1 10 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), N11 (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 UMF
  • FIG. 1C illustrates a 5G system architecture 140C and a service- based 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 sendee-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 servicebased interfaces: Namf 158H (a sendee-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a sendee-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a sendeebased interface exhibited by the UDM 146), Naf 158F (a senice-based interface exhibited by the AF 150), Nnrf 158C (a sendee-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a sendee-
  • FIG. 2 illustrates a network 200 m accordance with various embodiments.
  • the network 200 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 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 200 may include a LIE 202, which may include any mobile or non-mobile computing device designed to communicate with a RAN 204 via an over-the-air connection.
  • the UE 202 may be, but is not limited to, a smartphone, tablet computer, wearable computing 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 200 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 202 may additionally communicate with an AP 206 via an over-the-air connection.
  • the AP 206 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 204.
  • the connection between the LIE 202 and the AP 206 may be consistent with any IEEE 802.11 protocol, wherein the AP 206 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 202, RAN 204, and AP 206 may utilize cellular-WLAN aggregation (for example, LWA/LWIP).
  • Cellular-WLAN aggregation may involve the UE 202 being configured by the RAN 204 to utilize both cellular radio resources and W'LAN resources.
  • the RAN 204 may include one or more access nodes, for example, access node (AN) 208.
  • AN 208 may terminate air-interface protocols for the UE 202 by providing access stratum protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and LI protocols.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • LI protocols Low Latency Control
  • the AN 208 may enable data/voice connectivity between the core network (CN) 220 and the UE 202.
  • the AN 208 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 208 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 208 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 204 includes a plurality of
  • the ANs may be coupled with one another via an X2 interface (if the RAN 204 is an LIE RAN) or an Xn interface (if the RAN 204 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 204 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 202 with an air interface for network access.
  • the UE 202 may be simultaneously connected with a plurality of cells provided by the same or different.
  • ANs of the RAN 204 may use carrier aggregation to allow the UE 202 to connect with a plurality of component carriers, each corresponding to a
  • a first /kN may be a master node that provides an MCG and a second AN may be a secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 204 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 PCells/Scells.
  • the nodes Before accessing the unlicensed spectrum, the nodes may perform medium/camer-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 202 or AN 208 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications.
  • RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”, a gNB may be referred to as a “gNB-type RSU”; and the like.
  • 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 sendees.
  • 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 204 may be an LTE RAN 210 with eNBs, for example, eNB 212.
  • the LTE RAN 210 may provide an LTE air interface with the following characteristics: sub-carrier spacing (SCS) of 15 kHz, CP-OFDM waveform for downlink (DL) and SC-FDMA waveform for uplink (UL); turbo codes for data and TBCC for control; etc.
  • SCS sub-carrier spacing
  • DL downlink
  • UL uplink
  • turbo codes for data and TBCC for control
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management;
  • the LTE air interface may operate on sub-6 GHz bands.
  • the RAN 204 may be an NG-RAN 214 with gNBs, for example, gNB 216, or ng-eNBs, for example, ng-eNB 218.
  • the gNB 216 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 216 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 218 may also connect with the 5G core through an NG interface but may connect with a UE via an LTE air interface.
  • the gNB 216 and the ng-eNB 218 may connect 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 214 and a UPF 248 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN214 and an AMF 244 (e.g., N2 interface).
  • NG-U NG user plane
  • N-C NG control plane
  • the NG-RAN 214 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 operate 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 (bandwidth parts) for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 202 can be configured with multiple BWPs where each BWiP configuration has a different SCS. When a BWP change is indicated to the UE 202, 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 202 with different amounts of frequency resources (for example, PRBs) to support, data transmission under different traffic loading scenarios.
  • the RAN 204 is communicatively coupled to CN 220 that includes network elements to provide various functions to support data and telecommunications services to customers/ subscribers (for example, users of UE 202).
  • the components of the CN 220 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 220 onto physical compute/ storage resources in servers, switches, etc.
  • a logical instantiation of the CN 220 may be referred to as a network slice, and a logical instantiation of a portion of the CN 220 may be referred to as a network sub- slice.
  • the CN 220 may be connected to the LTE radio network as part, of the Enhanced Packet System (EPS) 222, which may also be referred to as an EPC (or enhanced packet core).
  • the EPC 222 may include MME 224, SGW 226, SGSN 228, HSS 230, PGW 232, and PCRF 234 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the EPC 222 may be briefly introduced as follows.
  • the MME 224 may implement mobility management functions to track the current location of the UE 202 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 226 may terminate an SI interface toward the RAN and route data packets between the RAN and the EPC 222.
  • the SGW 226 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 228 may track the location of the UE 202 and perform security functions and access control.
  • the SGSN 228 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 224; MME selection for handovers; etc.
  • the S3 reference point between the MME 224 and the SGSN 228 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.
  • the HSS 230 may include a database for network users, including subscription-related information to support, the network entities’ handling of communication sessions.
  • the HSS 230 can provide support for routmg/roammg. authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 230 and the MME 224 may enable the transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 220.
  • the PGW 232 may terminate an SGi interface toward a data network (DN) 236 that may include an application/ content server 238.
  • the PGW 232 may route data packets between the LTE CN 222 and the data network 236.
  • the PGW 232 may be coupled with the SGW 226 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 232 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 232 and the data network 236 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 232 may be coupled with a PCRF 234 via a Gx reference point.
  • the PCRF 234 is the policy and charging control element of the LTE CN 222.
  • the PCRF 234 may be communicatively coupled to the app/content server 238 to determine appropriate QoS and charging parameters for sendee flow's.
  • the PCRF 232 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 220 may be a 5GC 240.
  • the 5GC 240 may include an AUSF 242, AMF 244, SMF 246, UPF 248, NSSF 250, NEF 252, NRF 254, PCF 256, UDM 258, and AF 260 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 240 may be briefly introduced as follow's.
  • the AUSF 242 may store data for authentication of UE 202 and handle authentication-related functionality.
  • the AUSF 242 may facilitate a common authentication framework for various access types.
  • the AUSF 242 may exhibit a Nausf service-based interface.
  • the AMF 244 may allow other functions of the 5GC 240 to communicate with the UE 202 and the RAN 204 and to subscribe to notifications about mobility events with respect to the UE 202.
  • the AMF 244 may be responsible for registration management (for example, for registering UE 202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 244 may provide transport for SM messages between the UE 202 and the SME 246, and act as a transparent proxy for routing SM messages.
  • AMF 244 may also provide transport for SMS messages between UE 202 and an SMSF.
  • AMF 244 may interact with the AUSF 242 and the UE 202 to perform various security anchor and context management functions.
  • AMF 244 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 204 and the AMF 244; and the AMF 244 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 244 may also support NAS signaling with the UE 202 over an N3 IWF interface.
  • the SMF 246 may be responsible for SM (for example, session establishment, tunnel management between UPF 248 and AN 208); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 248 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 244 over N2 to AN 208, and determining SSC mode of a session.
  • SM may refer to the 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 202 and the data network 236.
  • the UPF 248 may act as an anchor point for intra-RAT and inter- RAT mobility, an external PDU session point of interconnecting to data network 236, and a branching point to support multi-homed PDU sessions.
  • the UPF 248 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 m the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 248 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 250 may select a set of network slice instances serving the UE 202.
  • the NSSF 250 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs if needed.
  • the NSSF 250 may also determine the AMF set to be used to serve the UE 202, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 254.
  • the selection of a set of network slice instances for the UE 202 may be triggered by the AMF 244 with which the UE 202 is registered by interacting with the NSSF 250, which may lead to a change of AMF.
  • the NSSF 250 may interact with the AMF 244 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 250 may exhibit an Nnssf service-based interface.
  • the NEF 252 may securely expose services and capabilities provided by 3GPP network functions for the third party, internal exposure/re- exposure, AFs (e.g., AF 260), edge computing or fog computing systems, etc.
  • the NEF 252 may authenticate, authorize, or throttle the AFs.
  • NEF 252 may also translate information exchanged with the AF 260 and information exchanged with internal network functions. For example, the NEF 252 may translate between an AF-Service- Identifier and an internal 5GC information.
  • NEF 252 may also receive information from other NF s based on the exposed capabilities of other NFs. This information may be stored at the NEF 252 as structured data, or a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 252 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 252 may exhibit a Nnef service-based interface.
  • the NRF 254 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 254 also maintains information on 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 the execution of program code. Additionally, the NRF 254 may exhibit the Nnrf service-based interface.
  • the PCF 256 may provide policy rules to control plane functions to enforce them, and may also support a unified policy framework to govern network behavior.
  • the PCF 256 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 258.
  • the PCF 256 exhibits an Npcf service-based interface.
  • the UDM 258 may handle subscription-related information to support the network entities’ handling of communication sessions and may store the subscription data of UE 202.
  • subscription data may be communicated via an N8 reference point between the UDM 258 and the AMF 244.
  • the UDM 258 may include two parts, an application front end, and a UDR.
  • the UDR may store subscription data and policy data for the UDM 258 and the PCF 256, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 202) for the NEF 252.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 258, PCF 256, and NEF 252 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to the 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 258 may exhibit the Nudm service-based interface.
  • the AF 260 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 240 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 202 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 240 may select a UPF 248 close to the UE 202 and execute traffic steering from the UPF 248 to data network 236 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 260. In this way, the AF 260 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 260 to interact directly with relevant NFs. Additionally, the AF 260 may exhibit a Naf service-based interface.
  • the data network 236 may represent various network operator sendees, Internet access, or third-party sendees that may be provided by one or more servers including, for example, application/content server 238.
  • FIG. 3 schematically illustrates a wireless network 300 in accordance with various embodiments.
  • the wireless network 300 may include a UE 302 in wireless communication with AN 304.
  • the UE 302 and AN 304 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 302 may be communicatively coupled with the AN 304 via connection 306.
  • the connection 306 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 5GNR protocol operating at mm Wave or sub-6 GHz frequencies.
  • the UE 302 may include a host platform 308 coupled with a modem platform 310.
  • the host platform 308 may include application processing circuitry 312, which may be coupled with protocol processing circuitry 314 of the modem platform 310.
  • the application processing circuitry 312 may run various applications for the UE 302 that source/sink application data.
  • the application processing circuitry 312 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 314 may implement one or more layer operations to facilitate transmission or reception of data over the connection 306.
  • the layer operations implemented by the protocol processing circuitry 314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.
  • the modem platform 310 may further include digital baseband circuitry’ 316 that may implement one or more layer operations that are ‘"below” layer operations performed by the protocol processing circuitry' 314 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, spacefrequency 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/ de
  • the modem platform 310 may further include transmit circuitry' 318, receive circuitry 320, RF circuitry 322, and RF front end (RFFE) 324, which may include or connect to one or more antenna panels 326.
  • the transmit circuitry 318 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 320 may include an analog ⁇ to ⁇ digital converter, mixer, IF components, etc.
  • the RF circuitry' 322 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 324 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 the communication is TDM or FDM, in mmWave or sub-6 GHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed of in the same or different chips/modules, etc.
  • the protocol processing circuitry 314 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 326, RFFE 324, RF circuitry' 322, receive circuitry 320, digital baseband circuitry 316, and protocol processing circuitry 314.
  • the antenna panels 326 may receive a transmission from the AN 304 by receivebeamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 326.
  • a UE transmission may be established by and via the protocol processing circuitry 314, digital baseband circuitry 316, transmit circuitry' 318, RF circuitry 322, RFFE 324, and antenna panels 326.
  • the transmit components of the UE 302 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 326.
  • the AN 304 may include a host platform 328 coupled with a modem platform 330.
  • the host platform 328 may include application processing circuitry 7 332 coupled with protocol processing circuitry 334 of the modem platform 330.
  • the modem platform may further include digital baseband circuitry 336, transmit circuitry' 338, receive circuitry 340, RF circuitry 342, RFFE circuitry 344, and antenna panels 346.
  • the components of the AN 304 may be similar to and substantially interchangeable with like-named components of the UE 302.
  • the components of the AN 304 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • FIG. 4 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.
  • FIG. 4 shows a diagrammatic representation of hardware resources 400 including one or more processors (or processor cores) 410, one or more memory/ storage devices 420, and one or more communication resources 430, each of which may be communicatively coupled via a bus 440 or other interface circuitry.
  • a hypervisor 402 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 400.
  • the processors 410 may include, for example, a processor 412 and a processor 414.
  • the processors 410 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 radiofrequency 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 radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 420 may include a main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 420 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 430 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 404 or one or more databases 406 or other network elements via a network 408.
  • the communication resources 430 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, WiFi® components, and other communication components.
  • Instructions 450 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 410 to perform any one or more of the methodologies discussed herein.
  • the instructions 450 may reside, completely or partially, within at least one of the processors 410 (e.g., within the processor’s cache memory), the memory/storage devices 420, or any suitable combination thereof.
  • any portion of the instructions 450 may be transferred to the hardware resources 400 from any combination of the peripheral devices 404 or the databases 406.
  • the memory of processors 410, the memory/storage devices 420, the peripheral devices 404, and the databases 406 are examples of computer-readable and machine-readable media.
  • At least one of the components outlined in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as outlined in the example sections 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 LIE, 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.
  • AI/ML application may refer to a complete and deployable package, environment to achieve a certain function in an operational environment.
  • AI/ML application or the like may be an application that contains some artificial intelligence (AI)/machine learning (ML) models and application-level descriptions.
  • AI/ML application may be used for configuring or implementing one or more of the disclosed aspects.
  • machine learning refers to the use of computer systems implementing algorithms and/or statistical models to perform a specific task(s) without using explicit instructions but instead relying on patterns and inferences.
  • ML algorithms build or estimate mathematical modeh's) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) to make predictions or decisions without being explicitly programmed to perform such tasks.
  • an AH., algorithm is a computer program that leams from experience with respect to some task and some performance measure
  • an ML model may be any object or data structure created after an AIL. algorithm is trained with one or more training datasets. After training, an AIL model may be used to make predictions on new datasets.
  • ML algorithm refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the present disclosure.
  • ML model may also refer to ML methods and concepts used by an ML-assisted solution.
  • An “ML-assisted solution” is a solution that addresses a specific use case using AIL algorithms during operation.
  • ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, and the like.
  • An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution, an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor.
  • the “actor” is an entity that hosts an ML-assisted solution using the output of the ML model inference).
  • ML training host refers to an entity, such as a network function, that hosts the training of the model .
  • ML inference host refers to an entity, such as a network function, that hosts the model during inference mode (which includes both the model execution as well as any online learning if applicable).
  • the ML-host informs the actor about the output of the ML algorithm, and the actor decides for an action (an “action” is performed by an actor as a result of the output of an ML-assisted solution).
  • model inference information refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.
  • 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
  • FIG. 5 illustrates one example of long physical downlink shared channel (PDSCH) transmission duration. More specifically, FIG. 5 is an illustration of a long PDSCH transmission duration 500, according to an example embodiment.
  • PDSCH physical downlink shared channel
  • DL downlink
  • DCI downlink control information
  • a previous PDSCH transmission is still ongoing.
  • the gNB has to send a new DL DCI to schedule a PDSCH which results in the delay of data transmissions.
  • One solution could be to allow a gNB to schedule more DL resources than that required to transmit the current DL data in the buffer. Consequently, if new DL traffic arrives, a gNB can continue the PDSCH transmission for the new DL traffic on the scheduled DL resource. On the other hand, if there is no new incoming DL traffic, the scheduled DL resources need to be released earlier, i.e.
  • FIG. 6 illustrates an example for which the allocated DL resources could carry 10 code blocks (CBs). However, the DL transmission may be terminated only after the transmission of 6 CBs.
  • FIG. 6 is an illustration of the early termination of a PDSCH transmission 600, according to an example embodiment.
  • the disclosed techniques may be used for HARQ-ACK feedback for PDSCH transmissions with early termination operation.
  • KI PDSCH-to- HARQ feedback timing
  • the timing of PUCCH may be determined by the maximum length of PDSCH transmission or a reference point inside the PDSCH transmission of maximum length.
  • indicator KI is defined as the gap between the ending symbol of the PDSCH with maximum length and starting symbol of PUCCH carrying HARQ- ACK feedback, regardless of early termination of PDSCH.
  • a set of K I values could be configured by high layer signaling, then one KI value may be dynamically indicated in the DCI.
  • the maximum number of transport blocks (TBs) or code block groups (CBGs) of the PDSCH transmission scheduled by the DCI can be predefined or configured by high layer signaling. KI could be in the number of symbols or symbol groups.
  • FIG. 7, FIG. 8, FIG. 9, and FIG. 10 are illustrations of a PDSCH to HARQ feedback timing, according to example embodiments.
  • FIG. 7 illustrates an example 700 of PDSCH to HARQ feedback timing.
  • the PDCCH to PDSCH scheduling delay (K0) could be 0 or more than 0 symbols.
  • the timing of PUCCH is derived by the ending symbol of the maximum time resource of PDSCH and KI, irrespective of early termination or not.
  • KI is defined as the gap between the ending symbol of the actual PDSCH scheduled by the DCI and starting symbol of PUCCH carrying HARQ-ACK feedback.
  • the set of KI values could be configured by high layer signaling, then one KI value is dynamically indicated in the DCI format.
  • K I could be in the number of symbols or symbol groups.
  • the maximum number of TBs or CBGs of the PDSCH transmission scheduled by the DCI can be predefined or configured by high- layer signaling.
  • the actual number of TBs or CBGs of the PDSCH transmission due to early termination could be explicitly indicated or implicitly derived, e.g. based on cyclic redundancy check (CRC) masking, demodulation reference signal (DMRS) scrambling, etc.
  • CRC cyclic redundancy check
  • DMRS demodulation reference signal
  • FIG. 8 illustrates an example 800 of PDSCH to HARQ feedback timing.
  • Indicator K0 could be 0 or more than 0 symbols.
  • the timing of PUCCH is derived by the ending symbol of the actual time resource of the PDSCH transmission and indicator KI. Supporting a reliable detection of the ending symbol of the actual PDSCH transmission may be used, so that UE could know the correct PUCCH timing.
  • K I is defined as the gap between the ending symbol of a specific TB or CBG of the PDSCH and starting symbol of PUCCH carrying HARQ-ACK feedback.
  • CBG could be the first scheduled TB or CBG.
  • the above specific TB or CBG could be the N-th scheduled TB or CBG, where N is predefined or configured by high layer signaling.
  • gNB may transmit at least N TBs or CBGs in the PDSCH scheduled by the DCI.
  • the set of KI values could be configured by high layer signaling, then one KI value is dynamically indicated in the DCI format. KI could be in the number of symbols or symbol groups.
  • the number of TBs or CBGs transmitted by gNB can be up to min(M, X):
  • M is the maximum number of TBs or CBGs of the PDSCH transmission scheduled by the DCI, which can be predefined or configured by high layer signaling, and
  • X is the number of TBs or CBGs that can be transmitted in the time resource from the starting symbol of the PDSCH until an ending symbol of a last TB or CBG.
  • the last TB or CBG is determined by the KI value and a gap between the ending symbol of the last TB or CBG and the starting symbol of the PUCCH, which is not less than a minimum gap G.
  • G can be determined by the UE processing time for PDSCH, e.g. N1 symbols in NR.
  • G could be determined by the minimum configured value of KI by higher layer signaling.
  • G could be a value directly configured by higher layer signaling.
  • the actual number of TBs or CBGs of the PDSCH transmission could be explicitly indicated or implicitly derived, e.g. based on CRC masking, DMRS scrambling, etc.
  • FIG. 9 illustrates an example 900 of PDSCH to HARQ feedback timing.
  • Indicator K0 could be 0 or more than 0 symbols.
  • the timing of PUCCH is derived by the ending symbol of the last TB/CBG that is fixedly transmitted and the KI indicator. In this way, the timing of PUCCH can be determined.
  • gNB may continuously transmit additional TB/CBG in the same allocated resource. The last additional TB/CBG can be determined so that the gap between the ending symbol of the last TB/CBG and the start of the PUCCH is no shorter than a minimum gap.
  • KI is defined as the gap between starting symbol of the PDSCH transmission and starting symbol of PUCCH carrying HARQ-ACK feedback. Equivalently, the timing of PUCCH is determined by the ending symbol of PDCCH and the start symbol of PUCCH, i.e. a delay of K 0+K 1.
  • the set of KI values could be configured by high layer signaling, then one KI value is dynamically indicated in the DCI format. KI could be provided as a number of symbols or symbol groups.
  • the number of TBs or CBGs transmitted by gNB can be up to min(M, X):
  • M is the maximum number of TBs or CBGs of the PDSCH transmission scheduled by the DCI, which can be predefined or configured by high layer signaling;
  • X is the number of TBs or CBGs that can be transmitted in the time resource from the starting symbol of the PDSCH until an ending symbol of a last TB or CBG.
  • the last TB or CBG is determined by the KI value and a gap between the ending symbol of the last TB or CBG and the starting symbol of the PUCCH, winch is not less than a minimum gap G.
  • G can be determined by the UE processing time for PDSCH, e.g., N1 symbols in NR.
  • G could be determined by the minimum configured value of K I by high layer signaling minus Y symbols, where Y is the number of symbols for a TB or CBG, Alternatively, G could be a value directly configured by higher layer signaling.
  • the actual number of TBs or CBGs of the PDSCH transmission could be explicitly indicated or implicitly derived, e.g., based on CRC masking, DMRS scrambling, etc.
  • FIG. 10 illustrates an example 1000 of PDSCH to HARQ feedback timing.
  • K0 could be 0 or more than 0 symbols.
  • the timing of PUCCH is derived by the first, symbol of PDSCH and KI . In this way, the timing of PUCCH can be determined.
  • the last TB/CBG can be determined the gap between the ending symbol of the last TB/CBG and the start of the PUCCH is no shorter than a minimum gap.
  • the feedback delay is determined by a gap between the ending symbol of the PDCCH that schedules the PDSCH transmission and a starting symbol of the PUCCH carrying HARQ-ACK feedback, denoted as D.
  • the set of D values could be configured by high layer signaling, then one D value is dynamically indicated in the DCI format. D could be provided as a number of symbols or symbol groups.
  • the number of TBs or CBGs transmitted by gNB can be up to min(M, X):
  • M is the maximum number of TBs or CBGs of the PDSCH transmission scheduled by the DCI, which can be predefined or configured by high layer signaling;
  • X is the number of TBs or CBGs that can be transmitted in the time resource from the starting symbol of the PDSCH until an ending symbol of a last TB or CBG.
  • the last TB or CBG is determined by the D value and a gap between the ending symbol of the last TB or CBG and the starting symbol of the PUCCH, which is not less than a minimum gap G.
  • G can be determined by the UE processing time for PDSCH, e.g. N1 symbols in NR.
  • G could be determined by the minimum configured value of K I by high layer signaling minus KO Y symbols, where KO is the delay between PDCCH and the PDSCH, Y is the number of symbols for a TB or CBG.
  • G could be a value directly configured by higher layer signaling.
  • the actual number of TBs or CBGs of the PDSCH transmission could be explicitly indicated or implicitly derived, e.g. based on CRC masking, DMRS scrambling, etc.
  • FIG. 11 is an illustration of the determination of PUCCH timing, according to an example embodiment. More specifically, FIG. 11 illustrates an example 1100 of PDSCH to HARQ_feedback timing. K0 could be 0 or more than 0 symbols.
  • the timing of PUCCH is derived by the ending symbol of PDCCH and KI. In this way, the timing of PUCCH can be determined.
  • the last TB/CBG can be determined so that the gap between the ending symbol of the last TB/CBG and the start of the PUCCH is no shorter than a minimum gap.
  • the actual number of TBs or CBGs in a PDSCH scheduled by a DCI can be different, whi ch impacts the design of the HARQ- ACK codebook.
  • the maximum number of TBs or CBGs of the PDSCH transmission scheduled by the DCI with early termination enabled, denoted as M, can be predefined or configured by higher layer signaling.
  • the number of HARQ-ACK bits reported for a PDSCH scheduled by a DCI is fixed to M. If the number of TBs or CBGs for a PDSCH is less than M, it is padding to M bits for the PDSCH.
  • M the number of TBs or CBGs for a PDSCH
  • the codes of nonoverlapped PDSCHs in each slot in the DL association set can be determined. Denote the number of occasions as N, the codebook size is M-N.
  • a fallback operation may be supported if only one PDSCH is scheduled in the DL association set. In the fallback case, only one HARQ-ACK bit is included in the HARQ-ACK codebook.
  • the number of HARQ-ACK bits for a PDSCH in the sub-codebook is fixed.
  • the definition of counter DCI e.g., counter downlink assignment index, or C-DAI
  • C-DAI counter downlink assignment index
  • T-DAI total DAI
  • two HARQ-ACK sub-codebooks are used and concatenated to get the HARQ-ACK codebook.
  • a first sub-codebook includes HARQ-ACK bits for TB-based PDSCH transmissions with early termination disabled, e.g. a PDSCH scheduled on a cell configured with TB- based transmission without early termination, or a PDSCH scheduled by a fallback DCI on a cell configured with CBG based transmission or early termination.
  • the number of HARQ-ACK bits for a PDSCH in the first subcodebook could be 1 or 2.
  • a second sub-codebook includes HARQ-ACK bits for other PDSCH transmissions. The number of HARQ-ACK bits for a PDSCH in the second sub-codebook is fixed to M.
  • a first sub-codebook includes HARQ-ACK bits for TB-based PDSCH transmissions with early termination disabled, e.g. a PDSCH scheduled on a cell configured with TB- based transmission without early termination, or a PDSCH scheduled by a fallback DCI on a cell configured with CBG based transmission or early termination.
  • the number of HARQ-ACK bits for a PDSCH in the first subcodebook could be 1 or 2.
  • a second sub-codebook includes CBG based PDSCH transmissions with early termination disabled.
  • the number of HARQ-ACK bits for a PDSCH in the second sub-codebook is determined by the configured maximum number of CBG for a PDSCH with early termination disabled.
  • a third sub-codebook includes other PDSCH transmissions with early termination enabled.
  • the number of HARQ-ACK bits for a PDSCH in the third subcodebook is fixed to M.
  • FIG. 12 and FIG. 13 are illustrations of counter downlink assignment index (C-DAI) determination, according to example embodiments.
  • C-DAI in a DCI indicates the total number of TBs or CBGs before the PDSCH scheduled by the DCI.
  • the above total number of TBs or CBGs may be equal to or larger than the number of actual transmitted TB or CBGs.
  • the bit size of C-DAI may need to be increased.
  • C-DAI m a later DCI can serve as an indication of early termination of a PDSCH scheduled by an earlier DCI.
  • C-DAI in a DCI can indicate the position in the codebook for the HARQ-ACK bit of the first. TB or CBG of the PDSCH scheduled by the DCI.
  • a second DCI may be transmitted after the PDSCH scheduled by a first DCI (Cl ).
  • Cl there may exist enough processing time, so that gNB can set the value of C-DAI in C2 to reflect the actual number of TBs or CBGs transmitted in the PDSCH scheduled by Cl. Therefore, C-DAI in C2 serves as an indication of the number of actual transmitted TBs or CBGs in PDSCH scheduled by CI .
  • a second DCI may be transmitted right after a first DCI (Cl), however, it may be before the PDSCH scheduled by Cl, or there is no enough processing time between the PDSCH scheduled by Cl and the start symbol of C2.
  • gNB may conservatively set C-DAI in C2 according to the maximum number of TBs or CBGs of the PDSCH scheduled by Cl, or gNB may predict the actual number of transmitted TBs or CBGs in PDSCH scheduled by Cl and set C-DAI in C2 accordingly.
  • the exact method to set C-DAI in C2 is up to gNB implementation.
  • the UE will do HARQ-ACK bit ordering for the TB or CBG of the PDSCH scheduled by C2 according to the value of C-DAI in C2.
  • a single HARQ-ACK codebook is used, C-DAI in a DCI, no matter fallback DCI or non-fallback DCI, indicates the total number of TBs or CBGs before the PDSCH scheduled by the DCI.
  • two HARQ-ACK sub-codebooks are used and concatenated to get the HARQ-ACK codebook.
  • a first sub-codebook only includes HARQ-ACK bits for TB-based PDSCH transmissions with early termination disabled, e.g, a PDSCH scheduled on a cell configured with TB- based transmission without early termination, or a PDSCH scheduled by a fallback DCI on a cell configured with CBG based transmission or early termination.
  • C-DAI indicates the number of PDCCHs till the current PDCCH as defined in legacy NR.
  • the size of C-DAI for the first sub-codebook may be 2 bits, which is the same as legacy NR.
  • a second sub-codebook includes HARQ- ACK bits for other PDSCH transmissions.
  • C-DAI m a DCI for the second subcodebook indicates the total number of TBs or CBGs before the PDSCH scheduled by the DCI scheduling PDSCH with potential early termination.
  • three HARQ-ACK sub-codebooks are used and concatenated to get the HARQ-ACK codebook.
  • a first sub-codebook only includes HARQ-ACK bits for TB-based PDSCH transmissions with early termination disabled, e.g. a PDSCH scheduled on a cell configured with TB- based transmission without early termination, or a PDSCH scheduled by a fallback DCI on a cell configured with CBG based transmission or early termination.
  • C-DAI indicates the number of PDCCHs till the current PDCCH as defined in legacy NR.
  • the size of C-DAI for the first sub-codebook may be 2 bits, which is the same as legacy NR.
  • a second sub-codebook only includes HARQ-ACK bits for CBG based PDSCH transmissions with early termination disabled.
  • C-DAI indicates the number of PDCCHs till the current PDCCH as defined in legacy NR, or C-DAI in a DCI for the second sub-codebook indicates the total number of CBGs including the CBGs of current PDSCH scheduled by the DCI.
  • a third sub-codebook includes HARQ-ACK for other PDSCH transmissions with early termination enabled.
  • C-DAI in a DCI for the third subcodebook indicates the total number of TBs or CBGs before the PDSCH scheduled by the DCI scheduling PDSCH with early termination.
  • T-DAI in a DCI indicates the total number of TBs or CBGs of the PDSCHs scheduled by the DCI and all earlier DCIs. If the last DCI schedules a PDSCH with potential early termination, gNB may conservatively set the T-DAI according to the maximum number of TBs or CBGs of the PDSCH, or gNB may predict the actual number of transmitted TBs or CBGs in PDSCH and set the T- DAI accordingly. Alternately, the exact method to set the T-DAI is up to gNB implementation. In some aspects, the UE derives the size of the sub-codebook based on the T-DAI in the last DCI.
  • the HARQ-ACK codebook size is determined without T-DAI, That is, T-DAI is not included in a DCI.
  • the UE may conservatively assume M HARQ-ACK bits for the PDSCH scheduled by the last DCI.
  • the UE could detect the actual number of transmitted TBs or CBGs in the last PDSCH.
  • the LIE can derive the HARQ-ACK codebook size based on the C-DAI value in the last DCI and the number of TBs or CBGs in the last PDSCH.
  • the definition of counter DCI (C-DAI) and total DAI (T-DAI) and codebook generation defined in legacy NR may be reused.
  • the C-DAI field and T-DAI field in a DCI could be reinterpreted by the type of scheduled PDSCH by the DCI.
  • a single DCI format could schedule a PDSCH with or without early termination depending on the indication of one or more fields in the DCI.
  • both C-DAI and T-DAI are included in the DCI.
  • the total overhead is 4 bits assuming 2 bits for C-DAI and T-DAI respectively.
  • C-DAI is included in the DCI. It is possible to use 4 bits for the C-DAI since the 2 bits of T-DAI can be repurposed.
  • both C-DAI and T-DAI are included in the DCI.
  • the total overhead is 4 bits assuming 2 bits for C-DAI and T-DAI respectively.
  • the DCI schedules other PDSCH transmissions only C-DAI is included in the DCI.
  • HARQ-ACK feedback may be designed using the disclosed techniques for efficient DL data transmission.
  • the disclosed techniques may include systems and methods for HARQ-ACK feedback for long PDSCH transmissions.
  • gNB transmits a PDCCH which schedules a PDSCH with a scheduling delay K0. Then the UE detects the PDCCH, receives the PDSCH, and reports a HARQ- ACK for the PDSCH with a feedback delay K I . If the PDCCH is missed at the UE side, the UE may not receive the PDSCH that is transmitted by gNB. Consequently, the PDSCH resource is wasted. Specifically, with the increase of the time duration of the PDSCH transmission, the DL resource waste becomes larger. Therefore, the disclosed techniques include means for gNB to quickly identify the case when the UE misses the PDCCH.
  • the LIE may transmit early feedback, i.e. ACK, to indicate the PDCCH is received.
  • a delay KI in the DL assignment can be used to indicate a PUCCH resource for the early feedback, which is similar to the handling of the SPS release.
  • the gNB After the reception of the ACK (by the gNB), the gNB continues the DL. data transmission.
  • the gNB may transmit a PDCCH 2 to schedule DL data transmission on the overlapping resource as the DL data transmission that is scheduled by PDCCH 1.
  • FIG. 14 and FIG. 15 are illustrations of early ACK feedback to PDCCH, according to example embodiments.
  • FIG. 14 illustrates an example 1400 when the early ACK feedback can be transmitted before any DL data transmission. If there is enough processing time for gNB between the PUCCH 1 and the PDSCH 1, the gNB may not transmit any PDSCH if an ACK is not received on PUCCH 1. Otherwise, gNB may transmit one or more first PDSCH(s) until gNB knows that an ACK is not received on PUCCH 1.
  • FIG. 15 illustrates an example 1500 when the early ACK feedback can be transmitted after the transmission of one or more PDSCHs. In the example, PUCCH 1 is allocated after PDSCH 1. PDSCH 1 anyway needs to be transmitted by gNB since it is before PUCCH 1.
  • the gNB may not transmit any PDSCH other than PDSCH I if an ACK is not received on PUCCH 1. Otherwise, the gNB may transmit one or more PDSCHs starting from PDSCH 2 until gNB knows that an ACK is not received on PUCCH 1 .
  • the PDCCH may indicate two UL resources, e.g. two PUCCH resources.
  • the first UL resource may be used for the early ACK feedback to indicate the PDCCH is received.
  • the second UL resource may be used for the HARQ-ACK feedback of the DL data transmission that is scheduled by the PDCCH.
  • the early ACK feedback to indicate the PDCCH is received is not multiplexed with other HARQ-ACK information, e.g. for DL data transmission that is scheduled by other PDCCH or for SPS release.
  • the following information may be needed in the DL assignment for the early ACK feedback:
  • the DL assignment may indicate the following information for the HARQ-ACK feedback of the DL data transmission that is scheduled by the PDCCH:
  • T-DAI Total DAI
  • the early ACK feedback to indicate the PDCCH is received can be multiplexed with other HARQ-ACK information, e.g. for DL data transmission that is scheduled by other PDCCH or for SPS release.
  • the following information may be needed m the DL assignment for the early ACK feedback:
  • HARQ-ACK codebook is configured.
  • the DL assignment may indicate the folkwing information for the H ARQ-ACK feedback of the DL data transmission that is scheduled by the PDCCH:
  • HARQ-ACK codebook is configured except for fallback DCI.
  • the PDCCH may indicate only one UL resource, e.g. PUCCH resource which is used for the early ACK feedback to indicate the PDCCH is received. There is no indication for the UL resource to carry the HARQ-ACK feedback of the DL data transmission that is scheduled by the PDCCH. In this case, the UL resource to cany the HARQ-ACK feedback of the DL data transmission could be derived by a later PDCCH.
  • the PDCCH may indicate only one PUCCH resource which is used for HARQ-ACK feedback of DL data transmission that is scheduled by the PDCCH.
  • the feedback delay and/or PUCCH resource indicator for PUCCH carry i ng early HARQ-ACK feedback can be configured by higher layers via remaining minimum system information (RMSI), other system information (OSI), or dedicated radio resource control (RRC) signaling.
  • RMSI remaining minimum system information
  • OSI system information
  • RRC dedicated radio resource control
  • only one feedback delay KI is included in the PDCCH, where the same feedback delay is applied for PUCCH carrying early HARQ-ACK feedback and PUCCH carrying HARQ- ACK feedback for the DL data transmission that is scheduled by the PDCCH.
  • the early ACK feedback to indicate the PDCCH is received is not multiplexed with other HARQ-ACK information, e.g. for DL data transmission that is scheduled by other PDCCH or for SPS release.
  • the following information may be needed in the DL assignment for the early ACK feedback:
  • the DL assignment may indicate the following information for the HARQ-ACK feedback of the DL data transmission that is scheduled by the PDCCH:
  • T-DAI Total DAI
  • the early ACK feedback to indicate the PDCCH is received can be multiplexed with other HARQ-ACK information, e.g. for DL data transmission that is scheduled by other PDCCH or for SPS release.
  • the following information may be needed in the DL assignment for the early ACK feedback:
  • HARQ-ACK codebook is configured.
  • the DL assignment may indicate the following information for the HARQ-ACK feedback of the DL data transmission that is scheduled by the PDCCH:
  • HARQ-ACK codebook is configured except for fallback DCI.
  • the early ACK feedback to indicate the PDCCH can be multiplexed with other HARQ-ACK information in a Type3 HARQ-ACK codebook, and a HARQ process number can be derived and used by the early ACK feedback,
  • the HARQ process number that is used by the early ACK feedback can be indicated by the HARQ process number field in the PDCCH. If the value of the HARQ process number field is denoted as h, then a HARQ process number h is used by the early ACK feedback, and the PDSCH transmission(s) uses the HARQ process number starting from value h+l . Alternatively, the PDSCH transmission(s) uses the HARQ process number starting from value h too. In the latter option, since the early HARQ feedback needs to be reported earlier than the HARQ-ACK transmission for the PDSCH transmission, there is no confusion on the interpretation of HARQ process number h.
  • a HARQ process number that is different from the HARQ process number field in the PDCCH is used by the early ACK feedback. If the value of the HARQ process number field is denoted as h, the PDSCH transmi ssion(s) uses the HARQ process number starting from value h. HARQ process number that is used by the early ACK feedback could be value h- 1.
  • the HARQ process number that is used by the early ACK feedback can be indicated by a new field in the PDCCH.
  • the UE may report early ACK feedback to indicate the PDCCH is received if a certain condition is satisfied. Otherwise, no early ACK feedback is not applicable and the PDCCH only indicates necessary information for HARQ-ACK transmission of the DL data transmission.
  • reporting early ACK feedback to indicate the PDCCH is received is only done when the number of symbols or slots for the DL data transmission is larger than a threshold.
  • the threshold could be predefined or configured by higher layer signaling.
  • reporting early ACK feedback to indicate the PDCCH is received is only done when the number of PDSCHs for the DL data transmission is larger than a threshold.
  • the threshold could be predefined or configured by higher layer signaling.
  • Each PDSCH carries one TB or two TBs by spatial multiplexing.
  • reporting early ACK feedback to indicate the PDCCH is received is only done when DL data transmission with potential early termination is scheduled.
  • the DCI format for the DL assignment may schedule DL data transmission with potential early termination.
  • one field in the DL assignment may indicate DL data transmission with potential early termination.
  • two transmit power control commands for PUCCHs can be indicated in the PDCCH, where the first transmit power control command is used for PUCCH cartying early ACK feedback while the second transmit power control command is used for PUCCH cartying HARQ-ACK feedback for the DL data transmission that is scheduled by the PDCCH.
  • only one transmit power control command is included in the PDCCH, where the transmit power control command is applied for PUCCH carrying early ACK feedback and PUCCH carrying HARQ- ACK feedback for the DL data transmission that is scheduled by the PDCCH. Effectively, the transmit power control command is applied twice in the determination of the transmission power of the PUCCH carrying HARQ-ACK feedback for the DL data transmission that is scheduled by the PDCCH.
  • only one transmit power control command is included in the PDCCH, where the transmit power control command is only applied for PUCCH carrying early ACK feedback.
  • a transmit power control command of 0 dB applies to PUCCH carrying HARQ-ACK feedback for the DL data transmission that is scheduled by the PDCCH.
  • a positive early H ARQ- ACK feedback may be at least one ACK for the first X PDSCH(s).
  • a positive early HARQ-ACK feedback may be at least one ACK or all NACK(s) for the first X PDSCH(s).
  • gNB can terminate the DL data transmission.
  • gNB may transmit a PDCCH 2 to schedule DL data transmission on the overlapping resource as the DL data transmission that is scheduled by PDCCH 1.
  • FIG. 16 and FIG. 17 are illustrations of early HARQ-ACK feedback for first PDSCH(s), according to example embodiments.
  • FIG. 16 illustrates an example 1600 that the early HARQ-ACK feedback of the first X PDSCH(s) with X ::: I .
  • the gNB suspends DL data transmission after the transmission of PDSCH 1 and waits for the UE feedback for PDSCH 1.
  • the gNB may not transmit any PDSCH if the positive early HARQ-ACK feedback for PDSCH 1 is not received on PUCCH 1.
  • FIG. 17 illustrates an example 1700 that early HARQ-ACK feedback of the first X PDSCH(s) with X :::: l ,
  • the gNB may not suspend DL data transmission after the transmission of PDSCH 1. Before the gNB can receive the early HARQ-ACK feedback for PDSCH 1 on PUCCH 1, the gNB may already transmit some additional PDSCHs, e.g. PDSCH 2. The gNB may not transmit any further PDSCH if the positive early HARQ-ACK feedback for PDSCH 1 is not received on PUCCH 1.
  • the PDCCH may indicate two UL resources, e.g. two PUCCH resources.
  • the first UL resource is used for the early HARQ-ACK feedback for the first X PDSCH(s).
  • the second UL resource is used for the HARQ-ACK feedback of the DL data transmission except for the first X PDSCH(s).
  • the early HARQ-ACK feedback is not multiplexed with other HARQ-ACK information.
  • the following information may be needed in the DL assignment for the early HARQ-ACK feedback:
  • the DL assignment may indicate the following information for the HARQ-ACK feedback of the DL data transmission except the first X PDSCH(s):
  • T-DAI Total DAI
  • the early HARQ-ACK feedback can be multiplexed with other HARQ-ACK information.
  • the following information may be needed in the DL assignment for the early HARQ-ACK feedback:
  • HARQ-ACK codebook is configured.
  • the DL assignment may indicate the following information for the HARQ-ACK feedback of the DL data transmission except the first X PDSCH(s):
  • HARQ-ACK codebook is configured except for fallback DCI.
  • the PDCCH may indicate only one UL resource, e.g. PUCCH resource which is used for the early HARQ-ACK feedback for the first X PDSCH(s). There is no indication for the UL resource to carry' the HARQ- ACK feedback of the DL data transmission except the first X PDSCH(s). In this case, the UL resource to cany the HARQ-ACK feedback of the DL data transmission except for the first X PDSCH(s) could be derived by a later PDCCH.
  • one PUCCH resource including feedback delay KI and PUCCH resource indicator is included in the PDCCH, where the same feedback delay and PUCCH resource indicator applied for PUCCH carrying early HARQ-ACK feedback and PUCCH carrying HARQ-ACK feedback for the DL data transmission except the first X PDSCH(s).
  • the transmit power control command is applied twice in the determination of the transmission power of the PUCCH carrying HARQ-ACK feedback for the DL data transmission except for the first X PDSCH(s).
  • transmit power control command is included in the PDCCH, where the transmit power control command is only applied for PUCCH carrying early ACK feedback, A transmit power control command of 0 dB applies to PUCCH carrying HARQ-ACK feedback for the DL data transmission except for the first X PDSCH(s).
  • the early HARQ-ACK feedback is not multiplexed with other HARQ-ACK information.
  • the following information may be needed in the DL assignment for the early HARQ-ACK feedback: [00237] (a) A feedback delay KI; and
  • the DL assignment may indicate the following information for the HARQ-ACK feedback of the DL data transmission except the first X PDSCH(s):
  • T-DAI Total DAI
  • the early HARQ-ACK feedback can be multiplexed with other HARQ-ACK information.
  • the following information may be needed in the DL assignment for the early HARQ-ACK feedback: [00243] (a) A feedback delay KI;
  • T-DAI Total DAI
  • the DL assignment may indicate the following information for the HARQ-ACK feedback of the DL data transmission except the first X PDSCH(s):
  • HARQ-ACK codebook is configured except for fallback DCL
  • two transmit power control commands for PUCCHs can be indicated in the PDCCH, where the first transmit power control command is used for PUCCH carrying early HARQ-ACK feedback while the second transmit power control command is used for PUCCH carrying HARQ- ACK feedback for the DL data transmission except the first X PDSCH(s).
  • one transmit power control command is included in the PDCCH, where the transmit power control command is applied for PUCCH carrying early HARQ-ACK feedback and PUCCH carrying HARQ- ACK feedback for the DL data transmission except the first X PDSCH(s).
  • the UE may report early HARQ-ACK feedback for the first X PDSCH(s) if a certain condition is satisfied.
  • reporting early HARQ-ACK feedback is only done when the number of symbols or slots for the DI., data transmission is larger than a threshold.
  • the threshold could be predefined or configured by higher layer signaling.
  • reporting early HARQ-ACK feedback is only done when the number of PDSCHs for the DL data transmission is larger than a threshold.
  • the threshold could be predefined or configured by higher layer signaling.
  • Each PDSCH carries one TB or two TBs by spatial multiplexing.
  • reporting early HARQ-ACK feedback is only done when DL data transmission with potential early termination is scheduled.
  • the DCI format, for the DL assignment may schedule DL data transmission with potential early termination.
  • one field in the DL assignment may indicate DL data transmission with potential early termination.
  • the gNB may retransmit the DL. control information that schedules the DI., transmission to mitigate the DL resource waste. If the UE miss the initial PDCCH, however, the UE receives the PDCCH retransmission, the UE can still do PDSCH reception according to the PDCCH retransmission.
  • the interval between the retransmitted PDCCH and the first PDSCH that is scheduled by the initial PDCCH must the timeline requirement of PDSCH processing time. In this way, if only UE receives one from the initial PDCCH and retransmitted PDCCH, UE can receive all the scheduled PDSCHs, so that there is no waste on PDSCH resources.
  • FIG. 18 illustrates an example of this option. More specifically, FIG. 18 is an illustration 1800 of a PDCCH retransmission scheduling all PDSCH(s), according to an example embodiment.
  • the initial PDCCH and the retransmitted PDCCH allocates the same PDSCH resources.
  • the PDCCH to PDSCH scheduling delay K0 and K0’ is expected to be different.
  • the HARQ-ACK feedback delay, i.e. KI can be the same or different in the two PDCCHs. If the K I values are different, it means different HARQ-ACK codebooks are generated and transmitted on different PUCCHs corresponding to two PDCCHs.
  • a Type2 HARQ-ACK codebook since the C-DAI/T-DAI in the two PDCCHs are different, two positions in the codebook are allocated for the same HARQ-ACK bit(s) if a single codebook is generated. If the UE receives both PDCCHs, the UE may transmit the same HARQ-ACK information on the two positions or only on one of the two positions.
  • the transmission power control command in the two PDCCHs may be accumulated to determine the transmission power of the PUCCH.
  • the value of the transmission power control command in the two PDCCHs must be the same, and the value is used to determine the transmission power of the PUCCH.
  • only the transmission power control command in the retransmitted PDCCH is used to determine the transmission power of the PUCCH.
  • the first X PDSCH(s) may not be scheduled by the retransmitted PDCCH, considering the timeline requirement of PDSCH processing time. In this way, if the UE only receives the retransmitted PDCCH, the UE may not receive the first X PDSCH(s) which causes resource waste. On the other hand, it is helpful to reduce the DL transmission delay if the initial PDCCH can be received by the UE.
  • the retransmitted PDCCH may include information to help UE know it is a retransmitted PDCCH. Further, the information may help UE know the number of missed PDSCHs that are scheduled by the UE.
  • the retransmitted PDCCH allocates the same PDSCH resources except the first X PDSCH(s) that is scheduled by the initial PDCCH.
  • the PDCCH to PDSCH scheduling delay K0 and K0’ is expected to be different.
  • the HARQ-ACK feedback delay, i.e. KI can be the same or different in the two PDCCHs. If the KI values are different, it means different HARQ-ACK codebooks are generated and transmitted on different PUCCHs corresponding to trvo PDCCHs.
  • a Type2 HARQ-ACK codebook since the C-DAI/T-DAI in the two PDCCHs are different, two positions in the codebook are allocated for the same HARQ-ACK bit(s) if a single codebook is generated . If the UE receives the initial PDCCH, the UE may transmit IIARQ- ACK for all the PDSCHs in the position corresponding to the initial PDCCH. If the UE receives the retransmitted PDCCH, the UE may transmit HARQ-ACK for all the PDSCHs except the first X PDSCH(s) in the position corresponding to retransmitted PDCCH.
  • the transmission power control command in the two PDCCHs may be accumulated to determine the transmission power of the PUCCH.
  • the value of the transmission power control command in the two PDCCHs must be the same, and the value is used to determine the transmission power of the PUCCH.
  • only the transmission power control command in the retransmitted PDCCH is used to determine the transmission powder of the PUCCH.
  • FIG. 20 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB) (or another RAN node), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), in accordance with some aspects and to perform one or more of the techniques disclosed herein.
  • the communication device 2000 may operate as a standalone device or may be connected (e.g., networked) to other communication devices.
  • Circuitry' e.g., processing circuitry
  • circuitry is a collection of circuits implemented in tangible entities of the device 2000 that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership may be flexible over time. Circuitries include members that may, alone or in combination, perform specified operations when operating. In an example, the hardware of the circuitry may be immutably designed to carry out a specific operation (e.g., hardwired).
  • the hardware of the circuitry may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine-readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instractions of the specific operation.
  • variably connected physical components e.g., execution units, transistors, simple circuits, etc.
  • machine-readable medium e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.
  • the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa.
  • the instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation.
  • the machine-readable medium elements are part of the circuitry or are communicatively coupled to the other components of the circuitry when the device is operating.
  • any of the physical components may be used in more than one member of more than one circuitry.
  • execution units may be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the device 2000 follow.
  • the device 2000 may operate as a standalone device or may be connected (e.g., networked) to other devices.
  • the communication device 2000 may operate in the capacity of a server communication device, a client communication device, or both in server- client network environments.
  • the communication device 2000 may act as a peer communication device in a peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the communication device 2000 may be a UE, eNB, PC, a tablet PC, an STB, a PDA, a mobile telephone, a smartphone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device.
  • the term "communication device” shall also be taken to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems (e.g., a standalone, client, or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a communication device-readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using the software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • the software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at. a different instance of time.
  • the communication device (e.g., UE) 2000 may include a hardware processor 2002 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 2004, a static memory 2006, and a storage device 2007 (e.g., hard drive, tape drive, flash storage, or other block or storage devices), some or all of which may communicate with each other via an interlink (e.g., bus) 2008.
  • the communication device 2000 may further include a display device 2010, an alphanumeric input device 2012 (e.g., a keyboard), and a user interface (UI) navigation device 2014 (e.g., a mouse).
  • UI user interface
  • the display device 2010, input device 2012, and UI navigation device 2014 may be a touchscreen display.
  • the communication device 2000 may additionally include a signal generation device 2018 (e.g., a speaker), a network interface device 2020, and one or more sensors 2021 , such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor.
  • the communication device 2000 may include an output controller 2028, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • USB universal
  • the storage device 2007 may include a communication device- readable medium 2022, on which is stored one or more sets of data structures or instructions 2024 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • registers of the processor 2002, the main memory 2004, the static memory 2006, and/or the storage device 2007 may be, or include (completely or at least partially), the device-readable medium 2022, on which is stored the one or more sets of data structures or instructions 2024, embodying or utilized by any one or more of the techniques or functions described herein.
  • one or any combination of the hardware processor 2002, the main memory 2004, the static memory 2006, or the mass storage 2016 may constitute the device-readable medium 2022.
  • the term "device-readable medium” is interchangeable with “computer-readable medium” or “machine-readable medium”. While the communication device-readable medium 2022 is illustrated as a single medium, the term “communication device-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers ⁇ configured to store the one or more instructions 2024.
  • communication device-readable medium is inclusive of the terms “machine-readable medium” or “computer-readable medium”, and may include any medium that is capable of storing, encoding, or carrying instructions (e.g., instructions 2024) for execution by the communication device 2000 and that causes the communication device 2000 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting communication device-readable medium examples may include solid-state memories and optical and magnetic media.
  • communication device-readable media may include nonvolatile memory', such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory 7 (EEPROM)) and flash memory' devices; magnetic disks, such as internal hard disks and removable disks; magneto- optical disks; Random Access Memory (RAM), and CD-ROM and DVD-ROM disks.
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory 7
  • flash memory' devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory 7 (EEPROM)
  • flash memory' devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory 7 (EEPROM)
  • flash memory' devices e.g., Electrically Erasable Programmable Read-Only Memory 7 (EEPROM)
  • Instructions 2024 may further be transmitted or received over a communications network 2026 using a transmission medium via the network interface device 2020 utilizing any one of a number of transfer protocols.
  • the network interface device 2020 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the communications network 2026.
  • the network interface device 2020 may include a plurality of antennas to wirelessly communicate using at least one of single-input-multiple-output (SIMO), MIMO, or multiple- input-single-output (MISO) techniques.
  • SIMO single-input-multiple-output
  • MIMO multiple-input-multiple-output
  • MISO multiple- input-single-output
  • the network interface device 2020 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 2000, and includes digital or analog communications signals or another intangible medium to facilitate communication of such software.
  • a transmission medium in the context of this disclosure is a device-readable medium.
  • Example 1 is an apparatus for a user equipment (UE) configured for operation in a 5G NR system, the apparatus comprising: processing circuitry, where to configure the UE for hybrid automatic repeat request acknowledgment (HARQ-ACK) in the 5G NR system, the processing circuitry' is to: decode downlink control information (DCI) received from a base station, the DCI including scheduling information for a physical downlink shared channel (PDSCH) and a PDSCH-to-HARQ feedback timing (kl ) indicator; decode the PDSCH based on the scheduling information; determine physical uplink control channel (PUCCH) timing information based on the kl indicator; and encode HARQ-ACK feedback information for transmission to the base station based on the PUCCH timing information, the HARQ-ACK feedback information providing an acknowledgment of the decoded PDSCH; and a memory coupled to the processing circuitry and configured to store the scheduling information and the kl indicator.
  • DCI downlink control information
  • PDSCH physical downlink shared channel
  • kl PD
  • Example 2 the subject matter of Example 1 includes, the indicator provides a number of slots from completion of transmission of the PDSCH to a first slot of transmission of the PUCCH.
  • Example 3 the subject matter of Example 2 includes subject matter where the processing circuitry is to: determine the PUCCH timing information based on an ending symbol of a physical downlink control channel (PDCCH) carrying the DCI and the kl indicator.
  • PUCCH physical downlink control channel
  • Example 4 the subject matter of Examples 2-3 includes subject mater where the processing circuitry is to: determine the PUCCH timing information based on a configured ending symbol of the PDSCH and the kl indicator.
  • Example 5 the subject matter of Examples 2-4 includes subject matter where the processing circuitry is to: determine the PUCCH timing information based on an actual ending symbol of the PDSCH and the kl indicator.
  • Example 6 the subject matter of Examples 1-5 includes subject matter where the processing circuitry is to: decode a second DCI received from the base station after the PDSCH, the second DCI including a counter downlink assignment index (C-DAI), the C-DAI indicating a number of transport blocks (TBs) or code block groups (CBGs) transmited in the PDSCH, wherein the HARQ-ACK feedback information provides an acknowledgment of the number of TBs or CBGs indicated by the C-DAI.
  • C-DAI counter downlink assignment index
  • CBGs code block groups
  • Example 7 the subject matter of Examples 1-6 includes subject matter where the processing circuitry is to: decode a second DCI received from the base station after the DCI and before the PDSCH, the second
  • DCI including a counter downlink assignment index (C-DAI), the C-DAI indicating a number of transport blocks (TBs) or code block groups (CBGs) to be transmitted in the PDSCH, wherein the HARQ-ACK feedback information provides an acknowledgment of the number of TBs or CBGs indicated by the C- DAI.
  • C-DAI counter downlink assignment index
  • CBGs code block groups
  • Example 8 the subject matter of Examples 1-7 includes subject matter where the processing circuitry is to: encode the HARQ-ACK feedback information for transmission to the base station after reception of the DCI and before reception of the PDSCH, the HARQ-ACK feedback information providing an acknowledgment of the decoded DCI; and encode second HARQ- ACK feedback information for transmission to the base station based on the PUCCH timing information, the second HARQ-ACK feedback information providing an acknowledgment of the decoded PDSCH, wherein the PDSCH is received based on successful transmission of the HARQ-ACK feedback information.
  • Example 9 the subject matter of Examples 1-8 includes subject matter where the processing circuitry is to: encode the HARQ-ACK feedback information for transmission to the base station after reception of the PDSCH and before reception of a second PDSCH, the HARQ-ACK feedback information providing an acknowledgment of the decoded PDSCH; and encode second HARQ-ACK feedback information for transmission to the base station after decoding at least a second PDSCH, the second HARQ-ACK feedback information providing an acknowledgment of the at least second PDSCH.
  • Example 10 the subject matter of Examples 1-9 includes, transceiver circuitry coupled to the processing circuitry; and one or more antennas coupled to the transceiver circuitry'.
  • Example 1 1 is a computer-readable storage medium that stores instructions for execution by one or more processors of user equipment (UE), the instructions to configure the UE for hybrid automatic repeat request acknowledgment (HARQ-ACK) in a 5G NR system and to cause the UE to perform operations comprising: decoding downlink control information (DCI) received from a base station, the DCI including scheduling information for a physical downlink shared channel (PDSCH) and a PDSCH-to-HARQ feedback timing (kl) indicator; decoding the PDSCH based on the scheduling information; determining physical uplink control channel (PUCCH) timing information based on the kl indicator; and encoding HARQ-ACK feedback information for transmission to the base station based on the PUCCH timing information, the HARQ-ACK feedback information providing an acknowledgment of the decoded PDSCH.
  • DCI downlink control information
  • PDSCH physical downlink shared channel
  • kl PDSCH-to-HARQ feedback timing
  • PUCCH physical uplink control channel
  • Example 12 the subject matter of Example 1 1 includes, the indicator provides a number of slots from completion of transmission of the PDSCH to a first slot of transmission of the PUCCH.
  • Example 13 the subject matter of Example 12 includes subject matter where the instructions further cause the UE to perform operations comprising: determining the PUCCH timing information based on an ending symbol of a physical downlink control channel (PDCCH) carrying the DCI and the kl indicator.
  • PUCCH physical downlink control channel
  • Example 14 the subject matter of Examples 12-13 includes subject matter where the instructions further cause the UE to perform operations comprising: determining the PUCCH timing information based on a configured ending symbol of the PDSCH and the kl indicator.
  • Example 15 the subject matter of Examples 12-14 includes subject matter where the instructions further cause the UE to perform operations comprising: determining the PUCCH timing information based on an actual ending symbol of the PDSCH and the kl indicator.
  • Example 16 the subject matter of Examples 1 1-15 includes subject matter where the instructions further cause the UE to perform operations comprising: decoding a second DCI received from the base station after the PDSCH, the second DCI including a counter downlink assignment index (C- DAI), the C-DAI indicating a number of transport blocks (TBs) or code block groups (CBGs) transmitted in the PDSCH, wherein the HARQ-ACK feedback information provides an acknowledgment of the number of TBs or CBGs indicated by the C-DAI.
  • C- DAI counter downlink assignment index
  • CBGs code block groups
  • Example 17 the subject matter of Examples 1 1—16 includes subject matter where the instructions further cause the UE to perform operations comprising: decoding a second DCI received from the base station after the DCI and before the PDSCH, the second DCI including a counter downlink assignment index (C-DAI), the C-DAI indicating a number of transport blocks (TBs) or code block groups (CBGs) to be transmitted in the PDSCH, wherein the HARQ-ACK feedback information provides an acknowledgment of the number of TBs or CBGs indicated by the C-DAI.
  • C-DAI counter downlink assignment index
  • CBGs code block groups
  • Example 18 is a computer-readable storage medium that stores instructions for execution by one or more processors of a base station configured for operation in a 5G NR system, the instructions to configure the base station for processing of a hybrid automatic repeat request acknowledgement (HARQ- ACK) in the 5G NR system and to cause the base station to perform operations comprising: encoding downlink control information (DCI) for transmission to user equipment (UE), the DCI including scheduling information for a physical downlink shared channel (PDSCH) and a PDSCH-to-HARQ feedback timing (kl) indicator; encoding the PDSCH for transmission to the UE based on the scheduling information, and decoding HARQ-ACK feedback information received from the UE using a physical uplink control channel (PUCCH), a reception slot of the HARQ-ACK feedback information based on the kl indicator, and the HARQ-ACK feedback information providing an acknowledgement of successful decoding by the UE of the PDSCH.
  • DCI downlink control information
  • UE user equipment
  • PDSCH
  • Example 19 the subject matter of Example 18 includes subject matter where the instructions further cause the base station to perform operations comprising: encoding a second DCI for transmission to the UE after the PDSCH, the second DCI including a counter downlink assignment index (C-DAI), the C- DAI indicating a number of transport blocks (TBs) or code block groups (CBGs) transmitted in the PDSCH, wherein the HARQ-ACK feedback information provides an acknowledgment of the number of TBs or CBGs indicated by the C- DAI.
  • C-DAI counter downlink assignment index
  • CBGs code block groups
  • Example 20 the subject matter of Examples 18 -19 includes subject matter where the instructions further cause the base station to perform operations comprising: encoding a second DCI for transmission to the UE after the DCI and before the PDSCH, the second DCI including a counter downlink assignment index (C-DAI), the C-DAI indicating a number of transport blocks (TBs) or code block groups (CBGs) to be transmitted in the PDSCH, wherein the HARQ-ACK feedback information provides an acknowledgment of the number of TBs or CBGs indicated by the C-DAI.
  • C-DAI counter downlink assignment index
  • CBGs code block groups
  • Example 21 is at least one machine-readable medium including instructions that, when executed by processing circuitry/, cause the processing circuitry’ to perform operations to implement any of Examples 1-20.
  • Example 22 is an apparatus comprising means to implement any of Examples 1-20.
  • Example 23 is a system to implement any of Examples 1—20.
  • Example 24 is a method to implement any of Examples I -20.

Landscapes

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

Abstract

Appareil utilisé dans un équipement utilisateur (UE) comprenant des circuits de traitement et une mémoire. Afin de configurer l'UE pour un accusé de réception de demande de répétition automatique hybride (HARQ-ACK) dans un système de nouvelle radio de cinquième génération (NR 5G), les circuits de traitement doivent décoder des informations de commande de liaison descendante (DCI) reçues en provenance d'une station de base. Les DCI comprennent des informations de planification pour un canal partagé de liaison descendante physique (PDSCH) et un indicateur de synchronisation de rétroaction PDSCH-à-HARQ (k1). Le PDSCH est décodé sur la base des informations de planification. Les informations de synchronisation de canal de commande de liaison montante physique (PUCCH) sont déterminées sur la base de l'indicateur k1. Des informations de rétroaction HARQ-ACK sont codées pour une transmission à la station de base sur la base des informations de synchronisation de PUCCH, les informations de rétroaction HARQ-ACK fournissant un accusé de réception du PDSCH décodé.
PCT/US2021/071014 2020-09-01 2021-07-27 Rétroaction harq pour transmissions de données de liaison descendante WO2022051738A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202063073364P 2020-09-01 2020-09-01
US63/073,364 2020-09-01
US202163137002P 2021-01-13 2021-01-13
US63/137,002 2021-01-13

Publications (1)

Publication Number Publication Date
WO2022051738A1 true WO2022051738A1 (fr) 2022-03-10

Family

ID=80491576

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/071014 WO2022051738A1 (fr) 2020-09-01 2021-07-27 Rétroaction harq pour transmissions de données de liaison descendante

Country Status (1)

Country Link
WO (1) WO2022051738A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220303065A1 (en) * 2021-03-19 2022-09-22 Samsung Electronics Co., Ltd. Wireless transmissions with hybrid automatic repeat request (harq) feedback disabled
US20240015739A1 (en) * 2022-07-05 2024-01-11 Qualcomm Incorporated Early acknowledgement feedback
WO2024153099A1 (fr) * 2023-01-19 2024-07-25 大唐移动通信设备有限公司 Procédé et appareil de traitement de données, et terminal

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3079296A1 (fr) * 2014-01-07 2016-10-12 ZTE Corporation Procédé, système, terminal, et station de base, pour la transmission d'informations en retour d'accusé de réception de requête automatique de répétition hybride (harq-ack)
US20180241513A1 (en) * 2015-08-12 2018-08-23 Lg Electronics Inc. Method for transmitting ack/nack in wireless communication system and apparatus using same
US20190327755A1 (en) * 2018-02-15 2019-10-24 Intel Corporation Simultaneous harq-ack feedback and uplink transmission without dynamic grant
US20200106586A1 (en) * 2018-09-27 2020-04-02 Mediatek Singapore Pte. Ltd. Mechanisms For Feedback Of Multiple HARQ Procedures In A Slot In Mobile Communications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3079296A1 (fr) * 2014-01-07 2016-10-12 ZTE Corporation Procédé, système, terminal, et station de base, pour la transmission d'informations en retour d'accusé de réception de requête automatique de répétition hybride (harq-ack)
US20180241513A1 (en) * 2015-08-12 2018-08-23 Lg Electronics Inc. Method for transmitting ack/nack in wireless communication system and apparatus using same
US20190327755A1 (en) * 2018-02-15 2019-10-24 Intel Corporation Simultaneous harq-ack feedback and uplink transmission without dynamic grant
US20200106586A1 (en) * 2018-09-27 2020-04-02 Mediatek Singapore Pte. Ltd. Mechanisms For Feedback Of Multiple HARQ Procedures In A Slot In Mobile Communications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ETSI: "5G; NR; Physical layer procedures for control", ETSI TS 138 213 V15.5.0, 31 May 2019 (2019-05-31), pages 1 - 106, XP055906469 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220303065A1 (en) * 2021-03-19 2022-09-22 Samsung Electronics Co., Ltd. Wireless transmissions with hybrid automatic repeat request (harq) feedback disabled
US20240015739A1 (en) * 2022-07-05 2024-01-11 Qualcomm Incorporated Early acknowledgement feedback
WO2024153099A1 (fr) * 2023-01-19 2024-07-25 大唐移动通信设备有限公司 Procédé et appareil de traitement de données, et terminal

Similar Documents

Publication Publication Date Title
WO2022031544A1 (fr) Dmrs pour des communications nr supérieures à 52,6 ghz
WO2022051738A1 (fr) Rétroaction harq pour transmissions de données de liaison descendante
US20240196379A1 (en) Streamlining protocol layers processing, and slotless operation
WO2022212500A1 (fr) Ressources de transmission de liaison latérale pour un retour de coordination inter-ue
WO2022155125A1 (fr) Procédure de partage de cot pour communications à bande sans licence
WO2022087094A1 (fr) Commande de puissance d'émission pour des unités distribuées d'un réseau iab
WO2022031541A1 (fr) Gestion de faisceau dans le cadre d'un fonctionnement multi-trp
US20230421222A1 (en) Subband reporting for full duplex operation
US20240292409A1 (en) Cell grouping for multi-cell scheduling
US20240284386A1 (en) New radio (nr) positioning measurement with reduced latency
WO2023205029A1 (fr) Transmission et réception améliorées pour dispositifs redcap
US20240179689A1 (en) Time domain window for joint channel estimation
US20240155607A1 (en) Configuration of multiple component carrier repetition transmissions
US20240155603A1 (en) Dl reception and ul transmission overlap for hd-fdd operations
WO2022086929A1 (fr) Configuration de temps de traitement dans des réseaux nr
WO2022212460A1 (fr) Détermination de collisions et de conflits pour des communications de liaison latérale
WO2022031507A1 (fr) Couche pdcp mbs et continuité de service
US20240188079A1 (en) Cross-carrier scheduling with different cell numerologies
US20240196239A1 (en) Uplink impact on pucch scell activation delay
US20230388997A1 (en) Techniques for uplink (ul) simultaneous transmission across multi-panels (stxmp)
US20240349309A1 (en) Dci enhancements for soft resource availability indication
WO2022155321A1 (fr) Schémas de transmission et configurations de fiabilité pour des mbs nr
WO2023205201A1 (fr) Configuration et synchronisation à duplexage par répartition dans le temps au niveau d'un répéteur
WO2022032155A1 (fr) Indication de détection directionnelle par l'intermédiaire d'une infrastructure de quasi-co-localisation (qcl)
WO2022150503A1 (fr) Indication de ressource srs et tpmi dans 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: 21865288

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

Country of ref document: EP

Kind code of ref document: A1