Techniques for retransmission of cancelled and dropped HARQ feedback

Abstract

An apparatus and system for providing enhanced Type-3 HARQ-ACK codebook transmission is described. A gNB configures a UE for hybrid automatic repeat request (HARQ)-acknowledgement (ACK) (HARQ-ACK) retransmission using an enhanced Type-3 codebook using radio resource control signaling. The enhanced Type-3 codebook is triggered by downlink control information (DCI) format 1_1 or 1_2 and is transmitted using a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). Information in the DCI includes whether to use a configured, activated, or indicated carrier, a cell index of the carrier, whether to use all HARQ processes, only semi-persistent scheduling (SPS) processes, or only non-SPS processes, whether to use all priority HARQ processes, only high priority HARQ processes, or only low priority HARQ processes, and the HARQ process range.

Description

[Technical Field]

[0001] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 187,324, filed May 11, 2021, which is incorporated herein by reference in its entirety.

[0002] FIELD OF THE INVENTION

[0002] Embodiments relate to next generation wireless communications. In particular, some embodiments relate to retransmission of Hybrid Automatic Repeat Request (HARQ) feedback. [Background technology]

[0003] The use and complexity of Next Generation (NG) or New Radio (NR) wireless systems, including 5G networks and beginning to include sixth generation (6G) networks, among others, is increasing due to both the increasing types of user equipment (UE) devices using network resources and the amount of data and bandwidth used by various applications, such as video streaming, running on these UEs. The significant increase in the number and variety of communication devices has led to an increasingly complex corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers. As expected, with the emergence of any new technology, numerous problems arise. [Brief explanation of the drawings]

[0004] In the figures, which are not necessarily drawn to scale, like reference numbers may describe like components in different figures. Like reference numbers with different subscripts may represent different instances of like components. The figures generally illustrate various embodiments discussed herein by way of example, but not by way of limitation.

[0005] [Figure 1A] 1 illustrates a network architecture, according to some aspects.

[0006] [Figure 1B]1 illustrates a non-roaming 5G system architecture, according to some aspects.

[0007] [Figure 1C] 1 illustrates a non-roaming 5G system architecture, according to some aspects.

[0008] [Figure 2] 1 illustrates a block diagram of a communication device according to some embodiments.

[0009] [Figure 3] 1 illustrates a HARQ retransmission process according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0010] The following description and drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice the embodiments. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, portions and features of other embodiments. Claimed embodiments encompass all available equivalents of such claims.

[0011] 1A illustrates a network architecture according to some aspects. Network 140A includes 3GPP® LTE / 4G and NG network functions that may extend to 6G capabilities. Thus, while reference is made to 5G, it should be understood that this extends to 6G structures, systems, and capabilities as possible. Network functions can be implemented as separate network elements on dedicated hardware, as software instances running on dedicated hardware, and / or as virtual functions instantiated on a suitable platform, e.g., dedicated hardware or cloud infrastructure.

[0012] Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and 102 are shown as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may include any mobile or non-mobile computing device, such as a portable (laptop) or desktop computer, a wireless handset, a drone, or any other computing device that includes a wired and / or wireless communication interface. UE 101 and 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

[0013] Any of the wireless links described herein (e.g., used in network 140A or any other illustrated network) may operate according to any exemplary wireless communication technology and / or standard. Any spectrum management scheme may be used, including, for example, dedicated licensed spectrum, unlicensed spectrum, or (licensed) shared spectrum (such as Licensed Shared Access (LSA) at 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies, and Spectrum Access System (SAS) at 3.55-3.7 GHz and other frequencies). Different single-carrier or orthogonal frequency domain multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, and the like), particularly 3GPP NR, may be used by assigning OFDM carrier data bit vectors to corresponding symbol resources.

[0014] In some aspects, either of the UEs 101 and 102 may comprise an Internet of Things (IoT) UE or a Cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. In some aspects, either of the UEs 101 and 102 may comprise a Narrowband (NB) IoT UE (e.g., an enhanced NB-IoT (eNB-IoT) UE and a further enhanced (FeNB-IoT) UE, etc.). The IoT UE may utilize technologies such as a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communications, a sensor network, or machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with an MTC server or device over an IoT network. The M2M or MTC exchange of data may be a machine-initiated exchange of data. The IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UE may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network. In some aspects, either of the UEs 101 and 102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0015] The UEs 101 and 102 may be configured to be connected, e.g., communicatively coupled, to a Radio Access Network (RAN) 110. The RAN 110 may be, e.g., an Evolved Universal Mobile Telecommunications System (UMTS), a Universal Terrestrial Radio Access Network (E-UTRAN), a Next Generation RAN (NG RAN), or some other type of RAN. The RAN 110 may include one or more gNBs, one or more of which may be implemented by multiple units. It should be noted that although a gNB may be referred to herein, the same aspects may apply to other generations of NodeBs, e.g., a 6th generation NodeB, and thus more generally referred to as a Radio Access Network node (RAN node).

[0016] Each gNB may implement protocol entities in the 3GPP protocol stack, which is considered to have layers ordered from bottom to top (for the control plane / user plane): Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Control (PDCP), and Radio Resource Control (RRC) / Service Data Adaptation Protocol (SDAP). The protocol layers of each gNB may be distributed to different units: a Central Unit (CU), at least one Distributed Unit (DU), and Remote Radio Heads (RRHs). The CU provides functions such as user data forwarding control, mobility control, radio access network sharing, positioning, and session management, except for functions allocated only to the DU.

[0017] The higher protocol layers (PDCP and RRC in the control plane / PDCP and SDAP in the user plane) may be implemented in the CU, and the RLC and MAC layers may be implemented in the DU. The PHY layer may be split, with the higher PHY layers also implemented in the DU, while the lower PHY layers are implemented in the RRH. The CU, DU, and RRH may be implemented by different manufacturers but may still be connected by appropriate interfaces between them. A CU may be connected to multiple DUs.

[0018] Interfaces within the gNB include E1 and fronthaul (F)F1 interfaces. The E1 interface may be between the CU control plane (gNB-CU-CP) and the CU user plane (gNB-CU-UP), and thus may support the exchange of signaling information between the control plane and the user plane via E1AP services. The E1 interface may separate the radio network layer and the transport network layer and enable the exchange of UE-related and non-UE-related information. E1AP services may be UE-non-associated services that pertain to the entire instance of the E1 interface between the gNB-CU-CP and the gNB-CU-UP using a UE-non-associated signaling connection, and UE-related services that pertain to a single UE and pertain to a UE-associated signaling connection maintained for that UE.

[0019] The F1 interface may be located between the CU and the DU. The CU may control the operation of the DU via the F1 interface. Because signaling in the gNB is divided into control plane and user plane signaling, the F1 interface may be divided into an F1-C interface for control plane signaling between the gNB-DU and the gNB-CU-CP and an F1-U interface for user plane signaling between the gNB-DU and the gNB-CU-UP, which support the separation of the control plane and the user plane. The F1 interface may separate the radio network and transport network layers and enable the exchange of UE-related and non-UE-related information. Furthermore, the F2 interface may be between the lower and upper parts of the NR PHY layer. The F2 interface may also be separated into F2-C and F2-U interfaces based on the control plane and user plane functions.

[0020] UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communication interface or layer (discussed in more detail below); in this example, connections 103 and 104 are illustrated as air interfaces for enabling communication coupling and may be compatible with cellular communication protocols, such as the 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 5G protocol, a 6G protocol, etc.

[0021] In an aspect, 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 (SL) interface, which includes 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), a physical sidelink broadcast channel (PSBCH), and a physical sidelink feedback channel (PSFCH).

[0022] The UE 102 is shown as configured to access an access point (AP) 106 via a connection 107. The connection 107 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, such that the AP 106 may include a Wireless Fidelity (WiFi) router. In this example, the AP 106 is shown as connected to the Internet without being connected to a core network of a wireless system (described in more detail below).

[0023] The RAN 110 may include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN nodes, etc., and may include earth stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 may be transmission / reception points (TRPs). When the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may function within the communication cell of the NodeB. The RAN 110 may include one or more RAN nodes, such as a macro RAN node 111, for providing a macrocell, and one or more RAN nodes, such as a low-power (LP) RAN node 112, for providing a femtocell or picocell (e.g., a cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell).

[0024] Either of the RAN nodes 111 and 112 may terminate air interface protocols and may be the first point of contact for the UEs 101 and 102. In some aspects, either of the RAN nodes 111 and 112 may perform various logical functions for the RAN 110, including, but not limited to, radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and radio network controller (RNC) functions such as mobility management. In examples, either of the nodes 111 and / or 112 may be a gNB, an eNB, or another type of RAN node.

[0025] The RAN 110 is shown as communicatively coupled to a core network (CN) 120 via an S1 interface 113. In an aspect, the CN 120 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN (e.g., as shown with reference to FIGS. 1B-1C ). In this aspect, the S1 interface 113 is divided into two parts: an S1-U interface 114 that carries traffic data between the RAN nodes 111 and 112 and a serving gateway (S-GW) 122, and an S1-mobility management entity (MME) interface 115 that is a signaling interface between the RAN nodes 111 and 112 and the MME 121.

[0026] In this aspect, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network (PDN) Gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124. The MME 121 may be similar in function to the control plane of a legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 121 may manage mobility aspects during access, such as gateway selection and tracking area list management. The HSS 124 may include a database of network users containing subscription-related information to support network entity handling of communication sessions. The CN 120 may include one or several HSSs 124s, depending on the number of mobile subscribers, equipment capabilities, network organization, etc. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc.

[0027] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. Additionally, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other roles of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0028] The P-GW 123 may terminate the SGi interface toward the PDN. The P-GW 123 may route data packets between the CN 120 and external networks, such as a network including an application server 184 (alternatively referred to as an application function (AF)), via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data to other external networks 131A, which may include the Internet, an IP Multimedia Subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element providing applications (e.g., a UMTS packet service (PS) domain, LTE PS data services, etc.) that use IP bearer resources with the core network. In this aspect, the P-GW 123 is shown as communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., a voice over Internet Protocol (VoIP) session, a PTT session, a group communication session, a social networking service, etc.) for the UEs 101 and 102 via the CN 120.

[0029] The P-GW 123 may further be a policy enforcement and charging data collection node. The Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in a Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0030] In some aspects, the communications network 140A may be an IoT network or a 5G or 6G network, including a 5G New Radio network that uses communications in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is narrowband IoT (NB-IoT). Operation in unlicensed spectrum may include dual connectivity (DC) operation in unlicensed spectrum and standalone LTE systems, according to which LTE-based technologies operate exclusively in unlicensed spectrum without the use of an "anchor" in licensed spectrum, called MuLTEFire. Further enhanced operation of LTE systems in licensed and unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operation may include techniques for sidelink resource allocation and UE processing behavior for NR sidelink V2X communications.

[0031] The NG system architecture (or 6G system architecture) may include a RAN 110 and a core network (CN) 120. The NG-RAN 110 may include multiple nodes such as a gNB and an NG-eNB. The CN 120 (e.g., a 5G core network (5GC)) may include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and UPF may be communicatively coupled to the gNB and the NG-eNB via an NG interface. More specifically, in some aspects, the gNB and the NG-eNB may be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNB and the NG-eNB may be coupled to each other via an Xn interface.

[0032] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each of the gNB and NG-eNB can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so on. In some aspects, the gNB can be a master node (MN), and the NG-eNB can be a secondary node (SN) in the 5G architecture.

[0033] 1B illustrates a non-roaming 5G system architecture according to some aspects. In particular, FIG. 1B illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture. More specifically, a UE 102 can communicate with a RAN 110 and one or more other CN network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as an AMF 132, a session management function (SMF) 136, a policy control function (PCF) 148, an application function (AF) 150, a UPF 134, a network slice selection function (NSSF) 142, an authentication server function (AUSF) 144, and a unified data management (UDM) / home subscriber server (HSS) 146.

[0034] The UPF 134 can provide connectivity to the data network (DN) 152, which may include, for example, operator services, Internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and may also include a network slice selection function. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of access technology. The SMF 136 can be configured to set up and manage various sessions according to network policies. As such, the SMF 136 may be responsible for session management and assigning IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of the UE 101 or multiple sessions of the UE 101. That is, the UE 101 may have multiple 5G sessions. A different SMF may be assigned to each session. The use of a different SMF may allow each session to be managed individually. As a result, the functionality of each session may be independent of each other.

[0035] The UPF 134 can be deployed in one or more configurations according to the desired service type and can be connected to a data network. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to a 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).

[0036] The AF 150 may provide information about packet flows to the PCF 148, which is responsible for policy control to support the desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine appropriate policies for appropriate operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[0037] In some aspects, the 5G system architecture 140B includes multiple IP multimedia core network subsystem entities, such as an IP Multimedia Subsystem (IMS) 168B and a Call Session Control Function (CSCF). More specifically, the IMS 168B includes a CSCF, which can operate as a Proxy CSCF (P-CSCF) 162B, a Serving CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an Interrogate CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first point of contact for the UE 102 within the IM Subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session state in the network, and the E-CSCF can be configured to handle certain aspects of the emergency session, such as routing the emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to serve as the point of contact within an operator's network for all IMS connections destined for that network operator's subscribers or roaming subscribers currently located within the network operator's service area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network 170B, e.g., an IMS operated by a different network operator.

[0038] In some aspects, the UDM / HSS 146 can be coupled to an application server (AS) 160B, which can include a telephony application server (TAS) or another application server. The AS 160B can be coupled to an IMS 168B via an S-CSCF 164B or an I-CSCF 166B.

[0039] The reference point representation indicates that interactions may exist between corresponding NF services. For example, Figure 1B illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), and N10 (between the UDM 146 and the SMF 136, not shown). 1B , 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 UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in the case of a non-roaming scenario, or between the PCF 148, the visited network, and the AMF 132 in the case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between the AMF 132 and the NSSF 142, not shown). Other reference point representations not shown in FIG. 1B may also be used.

[0040] 1C illustrates a 5G system architecture 140C and a service-based representation. In addition to the network entities illustrated in FIG. 1B, the system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, the 5G system architecture can be service-based, and interactions between network functions can be represented by corresponding point-to-point reference points N or service-based interfaces.

[0041] 1C , a service-based representation can be used to represent network functions in the control plane that allow other authorized network functions to access those services. In this regard, the 5G system architecture 140C can include the following service-based interfaces: Namf 158H (service-based interface indicated by AMF 132), Nsmf 158I (service-based interface indicated by SMF 136), Nnef 158B (service-based interface indicated by NEF 154), Npcf 158D (service-based interface indicated by PCF 148), Nudm 158E (service-based interface indicated by UDM 146), Naf 158F (service-based interface indicated by AF 150), Nnrf 158C (service-based interface indicated by NRF 156), Nnssf 158A (service-based interface indicated by NSSF 142), and Nausf 158G (service-based interface indicated by AUSF 144). Other service-based interfaces not shown in FIG. 1C (eg, Nudr, N5g-eir, and Nudsf) can also be used.

[0042] The NR-V2X architecture can support reliable, low-latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The techniques disclosed herein can be used to support high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[0043] 2 illustrates a block diagram of a communications device according to some embodiments. Communications device 200 may be dedicated network equipment such as a dedicated computer, a personal or laptop computer (PC), a UE such as a tablet PC or smartphone, an eNB, software running on a server to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequentially or otherwise) that specify actions to be taken by that machine. For example, communications device 200 may be implemented as one or more of the devices illustrated in FIGS. 1A through 1C. It should be noted that communications described herein may be encoded prior to transmission by transmitting entities (e.g., UE, gNB) for reception by the receiving entity (e.g., UE, gNB) and decoded after receipt by the receiving entity.

[0044] As described herein, examples may include or operate on logic or multiple components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a specified manner. In examples, circuitry may be arranged in a specified manner (e.g., internally or relative to external entities such as other circuits) as modules. In examples, all or part of one or more computer systems (e.g., standalone, client, or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application portions, or applications) as modules that operate to perform specified operations. In examples, software may reside on a machine-readable medium. In examples, the software, when executed by underlying hardware of a module, causes the hardware to perform specified operations.

[0045] Thus, the terms "module" (and "component") are understood to encompass tangible entities that are physically constructed entities, specifically configured (e.g., hardwired) or temporarily (e.g., transiently) configured (e.g., programmed) to operate in a specified manner or to perform some or all of the operations described herein. Considering examples where modules are temporarily configured, each of the modules need not be instantiated at any one time. For example, if the modules include a general-purpose hardware processor that is configured using software, the general-purpose hardware processor may be configured as different modules at different times. Thus, the software may configure the hardware processor, for example, to configure a particular module at one time and a different module at a different time.

[0046] The communications device 200 may include a hardware processor (or equivalent processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204, and a static memory 206, some or all of which may be in communication with each other via an interlink (e.g., a bus) 208. The main memory 204 may include any or all of removable and non-removable storage, volatile memory, or non-volatile memory. The communications device 200 may further include a display unit 210, such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, the input device 212, and the UI navigation device 214 may be touchscreen displays. Communications device 200 may additionally include a storage device (e.g., a drive unit) 216, a signal generating device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. Communications device 200 may further include an output controller, 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, for communicating with or controlling one or more peripheral devices (e.g., a printer, a card reader, etc.).

[0047] Storage device 216 may include a non-transitory machine-readable medium 222 (hereinafter simply referred to as machine-readable medium) that stores one or more data structures or sets of instructions 224 (e.g., software) that embody or are utilized by any one or more of the techniques or functions described herein. Instructions 224 may reside, completely or at least partially, within main memory 204, static memory 206, and / or hardware processor 202 during execution thereof by communications device 200. While machine-readable medium 222 is depicted as a single medium, the term "machine-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 one or more instructions 224.

[0048] The term "machine-readable medium" may include any medium capable of storing, encoding, or carrying instructions for execution by communication device 200 and causing communication device 200 to perform any one or more of the techniques of this disclosure, or any medium capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of machine-readable media may include solid-state memories and optical / magnetic media. Specific examples of machine-readable media may include non-volatile memory such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (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.

[0049] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via a network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transport protocols (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Exemplary communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, and a wireless data network. Communications over the network may include one or more different protocols, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, the IEEE 802.16 family of standards known as WiMAX®, the IEEE 802.15.4 family of standards, the Long Term Evolution (LTE) family of standards, the Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, next generation (NG) / fifth generation (5G) standards, among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jack) or one or more antennas to connect to the transmission medium 226.

[0050] It should be noted that the term “circuitry” as used herein refers to, is part of, or includes hardware components configured to provide a described functionality, such as electronic circuits, logic circuits, processors (shared, dedicated, or groups) and / or memories (shared, dedicated, or groups), application-specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc. In some embodiments, a circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0051] The term "processor circuitry" or "processor," as used herein, therefore, refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The term "processor circuitry" or "processor" may refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single or multi-core processors, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes.

[0052] Any of the wireless links described herein may operate according to any one or more of the following wireless communication technologies and / or standards, including, but not limited to, the following: a Global System for Mobile Communications (GSM) wireless communication technology, a General Packet Radio Service (GPRS) wireless communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) wireless communication technology, and / or a Third Generation Partnership Project (3GPP) wireless communication technology, such as Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code Division Multiple Access 2000 (CDMA2000), Cellular Digital Packet Data (CDMA), and the like. CDPD), Mobitex, third generation (3G), circuit-switched data (CSD), high-speed circuit-switched data (HSCSD), Universal Mobile Telecommunications System (3rd Generation) (UMTS (3G)), wideband code division multiple access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), high-speed packet access (HSPA), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), high-speed packet access plus (HSPA+), Universal Mobile Telecommunications System time division duplex (UMTS-TDD), time division-code division multiple access (TD-CDMA), time division synchronous code division multiple access (TD-CDMA), 3rd Generation Partnership Project Release 8 (pre-4th Generation) (3GPP Rel.8 (Pre-4G)), 3GPP Rel.9 (3rd Generation Partnership Project Release 9), 3GPP Rel.10 (3rd Generation Partnership Project Release 10), 3GPP Rel.11 (3rd Generation Partnership Project Release 11), 3GPP Rel.12 (3rd Generation Partnership Project Release 12), 3GPP Rel.13 (3rd Generation Partnership Project Release 13), 3GPP Rel.14 (3rd Generation Partnership Project Release 14), 3GPP Rel.15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17), and subsequent releases (e.g., Rel. 18, Rel.19, etc.), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE Advanced Pro, LTE Licensed Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), CDMA One (2G), Code Division Multiple Access 2000 (3rd Generation) (CDMA2000 (3G)), Evolution Data Optimized or Evolution Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System / Enhanced Total Access Communication System (TACS / ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-Talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Offentlig Landmobile in Norwegian) Telefoni, Public Land Mobile Telephony, MTD (Swedish: Mobiltelefonisystem) Short for D, or Mobile Telephony System D), Public Automatic Land Mobile (Autotel / PALM), ARP (Finnish Autoradiopuhelin, "car radio telephone"), NMT (Nordic Mobile Telephony), NTT's (Nippon Telegraph and Telephone) high-capacity version (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, Data TAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Broadband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also known as the 3GPP Generic Access Network or GAN standard, Zigbee, Bluetooth, Wireless Gigabit Alliance (WiGig) standard, general millimeter wave standards (wireless systems operating at 10-300 GHz and above, e.g., WiGig, IEEE 802.11ad, IEEE 802.11ay, etc.), technologies operating above 300 GHz and THz bands, (3GPP / LTE based or IEEE802.11p or IEEE802.11bd and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (I2V) communication technologies, 3GPP Cellular V2X, DSRC (Dedicated Short Range Communications) communication systems, e.g., Intelligent Transport Systems and others (typically operating at or above 5850 MHz to 5925 MHz (variables in CEPT Report 71) After the proposal, this will typically be up to 5935 MHz), European ITS-G5 systems (i.e., European flavors of DSRC based on IEEE 802.11p, including ITS-G5A (i.e., ITS-G5 operation in the European ITS frequency band dedicated to ITS for safety-related applications in the frequency range 5875 GHz to 5905 GHz), ITS-G5B (i.e., operation in the European ITS frequency band dedicated to ITS non-safety applications in the frequency range 5855 GHz to 5875 GHz), and ITS-G5C (i.e., operation for ITS applications in the frequency range 5470 GHz to 5725 GHz), Japanese DSRC in the 700 MHz band (including 715 MHz to 725 MHz), IEEE 802.11bd-based systems, etc.).

[0053] Aspects described herein can be used in the context of any spectrum management scheme, including dedicated licensed spectrum, unlicensed spectrum, license-exempt spectrum, (licensed) shared spectrum (e.g., LSA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies, and SAS = Spectrum Access System / CBRS = Citizens Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include: IMT (International Mobile Telecommunications) spectrum, as well as other types of spectrum / bands, such as bands with national allocations (450-470 MHz, 902-928 MHz (Note: e.g., allocations within the United States (FCC Part 15)), 863-868.6 MHz (Note: e.g., allocations within the European Union (ETSI EN300)). 220), 915.9-929.7MHz (Note: e.g., allocations within Japan), 917-923.5MHz (Note: e.g., allocations within South Korea), 755-779MHz and 779-787MHz (Note: e.g., allocations within China), 790-960MHz, 1710-2025MHz, 2110-2200MHz, 2300-2400MHz, 2.4-2.4835GHz (Note: globally available ISM band, also used by Wi-Fi technology suite (11b / g / n / ax) and by Bluetooth), 2500-2690MHz, 6 98-790MHz, 610-790MHz, 3400-3600MHz, 3400-3800MHz, 3800-4200MHz, 3.55-3.7GHz (Note: e.g., allocated in the US for Citizens Broadband Wireless Service), 5.15-5.25GHz, 5.25-5.35GHz, 5.47-5.725GHz, and 5.725-5.85GHz bands (Note: e.g., allocated in the US (FCC Part 15) comprising four U-NII bands totaling 500MHz of spectrum), 5.725-5.875GHz (Note: e.g., allocated in Europe (ETSI EN 301 893)), 5.47-5.65GHz (Note: e.g., allocated in South Korea), 5925-7125MHz, and 5925-6425MHz bands (Note: under consideration in the US and Europe, respectively).Next-generation Wi-Fi systems are expected to include the 6 GHz spectrum as an operating band, but as of December 2017, Wi-Fi systems are not yet permitted in this band (regulations are expected to expire in the 2019-2020 timeframe), IMT Advanced spectrum, IMT 2020 spectrum (which is expected to include 3600-3800 MHz, 3800-4200 MHz, the 3.5 GHz band, the 700 MHz band, and bands in the 24.25-86 GHz range, etc.), spectrum made available under the FCC's "Spectrum Frontier" 5G initiative (which includes 27.5-28.35 GHz, 29.1-29.25 GHz, 31-31.3 GHz, 37-38.6 GHz, 38.6-40 GHz, 42-42.5 GHz, 57-64 GHz, 71-76 GHz, 81-86 GHz, and 92-94 GHz, etc.), and TS (Intelligent Transport Systems) bands 5.9 GHz (usually 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig, such as WiGig band 1 (57.24-59.40 GHz), WiGig band 2 (59.40-61.56 GHz), WiGig band 3 (61.56-63.72 GHz), and WiGig band 4 (63.72-65.88 GHz), 57-64 / 66 GHz (Note: This band has a near-global designation for Multi-Gigabit Wireless Systems (MGWS) / WiGig, with a total of 14 GHz spectrum allocated in the US (FCC Part 15), while Europe (ETSI for fixed P2P) This includes the 70.2 GHz-71 GHz band, any band between 65.88 GHz and 71 GHz (EN302 567 and ETSI EN301 217-2) which allocate a total of 9 GHz of spectrum, bands currently allocated for automotive radar applications, such as 76-81 GHz, and future bands including 94-300 GHz and above. Additionally, this scheme can be used secondarily in bands such as TV unused frequency bands (typically below 790 MHz), with the 400 MHz and 700 MHz bands being particularly attractive candidates. In addition to cellular applications, vertical market-specific applications, such as PMSE (Program Production and Special Events), medical, health, surgery, automotive, low latency, and drone applications, may be addressed.

[0054] Aspects described herein may also implement hierarchical application of schemes, for example, based on prioritized access to spectrum, enabled by introducing hierarchical prioritization of usage (e.g., low / medium / high priority, etc.) for different types of users, e.g., highest priority for Tier 1 users, then Tier 2, then Tier 3 users, etc.

[0055] The aspects described herein can also be applied to different single carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank Based Multi-Carrier (FBMC), OFDMA, etc.), particularly 3GPP NR (New Radio), by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0056] 5G networks extend beyond traditional mobile broadband services to provide a variety of new services, such as the Internet of Things (IoT), industrial control, autonomous driving, and mission-critical communications, which may have requirements for ultra-low latency, ultra-high reliability, and high data capacity due to safety and performance considerations. Note that some of the features herein are defined in terms of the network side, such as AP, eNB, NR, or gNB, as this term is typically used in the context of 3GPP 5G and 6G communication systems, etc. Furthermore, a UE may also play this role and function as an AP, eNB, or gNB; that is, some or all of the features defined for network equipment may be implemented by a UE.

[0057] As mentioned above, with the advent of NR, the achievable latency and reliability performance of NR systems has expanded from 4G systems to support use cases with more stringent requirements. To expand the applicability of NR to various vertical markets, Rel. 16 NR has evolved to support use cases that include improvements over Rel. 15, including augmented reality / virtual reality (AR / VR). Rel. 16 use cases with more stringent requirements include factory automation, transportation, and power distribution. In Rel. 17, NR technology will be enhanced to support ultra-reliable low-latency communications (URLLC), ushering in the Industrial Internet of Things (IIoT). One objective is to enhance HARQ feedback from UEs.

[0058] For example, enhancements to Rel-17 are desired to configure systems to avoid acknowledgments of semi-persistent scheduling (SPS) physical downlink shared channel transmissions (SPS HARQ ACK) being dropped for time-domain duplex (TDD) systems due to PUCCH collisions with at least one downlink (DL) or flexible symbol. Additional enhancements include SPS HARQ skipping for "skipped" SPS physical downlink shared channel (PDSCH) transmissions, PUCCH recursive enhancements (at least for HARQ-ACK), e.g., subslot-based retransmission of canceled HARQ transmissions, SPS HARQ payload size reduction and / or skipping for "non-skipped" SPS PDSCH transmissions, type 1 HARQ codebook implementation based on subslot PUCCH configuration, and PUCCH carrier switching for HARQ feedback. Therefore, determining whether a deferral condition for a potential PUCCH (also referred to herein as a hypothetical PUCCH) occurs and SPS configuration order handling for deferral are described herein. Figure 3 illustrates a HARQ retransmission process according to some embodiments.

[0059] One of the issues identified for Rel. 17 is dropped or canceled HARQ feedback retransmissions, which can occur due to several issues. One of these issues is the inability to map uplink control information (UCI) with HARQ ACK to available uplink symbols due to collisions with semi-static or dynamic DL, signaling system block (SSB), or control resource set zero (CORESET#0) symbols. Furthermore, overlap with higher priority UL channels can cause dropped or canceled HARQ feedback retransmissions when multiplexing is not possible. The gNB can also cancel HARQ feedback retransmissions using UL cancellation indications or other mechanisms.

[0060] Among the retransmission HARQ feedback mechanisms, a potentially enhanced Type-3 HARQ codebook mechanism (one-shot feedback) or other mechanisms, such as scheduling retransmission of dropped feedback via DL assignment or UL grant, may be used. For this purpose, the indication of an enhanced Type-3 codebook (CB) based on activated cells, SPS processes, priorities, and other considerations, and the construction of an enhanced Type-3 CB, are described herein.

[0061] Enhanced Type-3 HARQ-ACK Codebook

[0062] It is assumed that the Type-3 HARQ-ACK codebook design for 5G New Radio Unlicensed (NR-U) to handle the impact from listen-before-talk (LBT) failures can be used for HARQ-ACK feedback retransmission in licensed spectrum operation. Currently, Type-3 CB operation can be enabled by the pdsch-HARQ-ACK-OneShotFeedback radio resource control (RRC) message. In this case, DCI format 1_1 also carries a 1-bit field "One Shot HARQ-ACK Request." If pdsch-HARQ-ACK-OneShotFeedback is not provided, this field is set to a value of "0." When DCI format 1_1 with "One Shot HARQ-ACK Request" set to a value of "1" is received, the UE constructs a Type-3 CB using the following parameters:

[0063]

number

[0064]

number

number

[0065]

number

number

number

[0066]

number

number

[0067] If pdsch-HARQ-ACK-OneShotFeedbackNDI is provided,

number

number

[0068] If the UE detects a DCI format including a one-shot HARQ-ACK request field with the value 1, the CRC of the DCI is scrambled with a cell radio network temporary identifier (C-RNTI) or modulation and coding scheme C-RNTI (MCS-C-RNTI) (UE identification used to indicate alternative MCS tables for PDSCH and PUSCH), and resourceAllocation=resourceAllocationType0 and all bits of the frequency-domain resource allocation field in the DCI format are equal to 0, or resourceAllocation=resourceAllocationType1 and all bits of the frequency-domain resource allocation field in the DCI format are equal to 1, or resourceAllocation=dynamicSwitch and all bits of the frequency-domain resource allocation field in the DCI format are equal to 0 or 1, then Type-3CB is triggered by the DCI format not scheduling a PDSCH. Otherwise, if the UE detects a DCI format that includes a one-shot HARQ-ACK request field with a value of 1 and the cyclic redundancy code (CRC) of the DCI is scrambled by the C-RNTI or MCS-C-RNTI, Type-3 CB is triggered by the DCI scheduling the PDSCH.

[0069] Distinction between Type-3CB (Type3CB) and enhanced Type-3CB (eType3CB)

[0070] In one embodiment, the UE may be provided with an optional RRC message as part of the PhysicalCellGroupConfig information element (IE) with an enumerated type example name type3CBType, with a possible value of "enhanced." If the value is provided and set to "enhanced," and if pdsch-HARQ-ACK-OneShotFeedback is also provided in the PhysicalCellGroupConfig IE, the Type-3CB behavior follows the enhanced version specified in Release 17 and later. Otherwise, if pdsch-HARQ-ACK-OneShotFeedback is not provided in the PhysicalCellGroupConfig IE, the Type-3CB behavior follows the Release 16 version.

[0071] In one embodiment, a dynamic switching flag in DCI format 1_1 and / or 1_2 may be provided to the UE indicating whether Release 16 or Release 17 Type3CB, Type3CB, or eType3CB is used.

[0072] Handling activated cells

[0073] In one embodiment, an optional RRC field may be provided to the UE as part of the PhysicalCellGroupConfig IE to indicate whether the eType-3 CB establishment should use all configured cells, all activated cells, or a subset of activated cells as the basis for CB establishment. In one example, the RRC field may have a single value, and if the RRC field is present, the value is

number

number

[0074] In another example, the RRC field may have two possible values:

number

number

number

[0075] Priority Handling

[0076] In one embodiment, if the priority field is present and DCI format 1_1 or 1_2 is provided to the UE, which triggers the eType3CB HARQ codebook, then eType3CB may be constructed from a subset of HARQ processes corresponding to a subset or all priorities.

[0077] In one option, if a DCI format 1_1 or 1_2 in which a priority field is present is provided to the UE and the DCI format does not schedule PDSCH, the priority field may be used for CB construction as follows: if the priority field is set to '1', only HARQ processes that are triggered by DCI or correspond to SPS configurations with priority '1' are multiplexed in the eType3CB; if the priority field is set to '0', only HARQ processes that are triggered by DCI or correspond to SPS configurations with priority '0' are multiplexed in the eType3CB.

[0078] Alternatively, if the priority field is set to "1", only HARQ processes that are triggered by DCI or that correspond to SPS configurations with priority "1" are multiplexed in eType3CB. In this case, if the priority field is set to "0", all HARQ processes that are triggered by DCI or that correspond to SPS configurations with priority "0" or "1" are multiplexed in eType3CB.

[0079] Whether the value "0" indicates multiplexing of HARQ feedback corresponding to priority "0" only or to both "0" and "1", the CB configuration may be configurable by RRC or using dynamic DCI.

[0080] For the above options, the existing priority field may not be utilized, but other unused fields in the DCI, such as MCS, Time Domain Resource Allocation (TDRA), HARQ Process ID, New Data Indicator (NDI), or priority, may be reinterpreted to indicate one or more bits of information, which may be used to switch between CB construction options, as discussed above, for example, multiplexing only HARQ-ACK bits for priority "1" or priority "0", or multiplexing HARQ-ACK bits for both "1" and "0". [Table 1]

[0081] Since the number of low priority (LP) and high priority (HP) processes is dynamic and varies depending on the actual scheduling situation, two options are possible: Option 1: A priority-based eType3CB is constructed based on the actual number of HARQ processes received for a given priority or combination of priorities. This option may lead to ambiguity in the CB size between the gNB and the UE due to missing DCI. Option 2: A priority-based eType3CB is constructed based on a nominal number of HARQ processes. The nominal number of HARQ processes for a priority can be configured by RRC signaling or a combination of RRC signaling and DCI.

[0082] In one option, if a UE is provided with DCI format 1_1 or 1_2 in which a priority field is present and the DCI format schedules a PDSCH, the priority field may not be used in eType3CB construction, since the priority is also relevant for the scheduled PDSCH. Instead, all HARQ processes triggered by the DCI or corresponding to an SPS configuration with priority "0" or "1" are multiplexed in eType3CB, regardless of whether the priority field is set to "1" or "0". Alternatively, the same handling as for a DCI that does not schedule a PDSCH, as described above, may be applied.

[0083] In some embodiments, the DCI may indicate whether the codebook is for multiplexing high and / or low priority information, regardless of whether the PDCCH schedules the PDSCH.

[0084] For example, the CB construction (mapping of HARQ IDs to bits in the HARQ-ACK CB) may be determined based on the nominal number of HARQ processes; the indicated priority determines that only bits corresponding to the priority for the indicated HARQ-ACK feedback convey information.

[0085] Handling of SPS HARQ processes

[0086] Another option for Type-3CB size optimization is to consider an SPS-only process for eType3CB construction to handle the typical case of SPS HARQ-ACK drops.

[0087] In one embodiment, the UE may be provided with an optional RRC message indicating that the eType3CB configuration uses only SPS HARQ processes.

number

[0088] In one embodiment, when DCI format 1_1 or 1_2 triggers eType3CB and does not schedule PDSCH, the unused fields in the DCI format (e.g., MCS, HARQ ID, TDRA) can be reinterpreted to indicate, via X least significant bits (LSBs) or most significant bits (MSBs), whether eType3CB is configured using only SPS HARQ processes, only dynamic HARQ processes, or both SPS and dynamic HARQ processes.

[0089] In one embodiment, when DCI format 1_1 or 1_2 triggers eType3CB to schedule PDSCH, eType3CB is configured for only one combination of HARQ processes, i.e., SPS only, dynamic only, or SPS and dynamic, since there are no unused fields that can be reinterpreted and utilized for dynamic switching.

[0090] General purpose dynamic switching between eType3CB building configurations

[0091] There are different attributes that can be inputs to the adaptation of the size of the eType3CB: activated cells, SPS vs. non-SPS processes, priority, etc. Each of these attributes can use dynamic indication in the DCI. A generic mechanism for eType3CB construction based on dynamic indication may be introduced as follows:

[0092] The RRC configuration may provide a table (RRC Table M) that provides a mapping of DCI field payloads to combinations of attributes used for eType3CB construction. The size of the RRC Table M may be flexible and may range from 1 (e.g., no dynamic configurability of eType3CB) to some maximum value predefined in the specification (e.g., 4, or 8, or 16, or any other natural value), depending on the gNB implementation. Each row of the table contains a structure with fields indicating parameters of eType3CB construction. Each entry may be one or a combination of the following: Carrier: {Configured, Activated, Indicated}, Carrier: Cell Index, SPS: {All, SPS, Non-SPS}, Priority: {All, HP, LP}, Nominal # of Processes for Priority: Integer, HARQ Process Range: Start Process ID - End Process ID.

[0093] An exemplary table is provided below. [Table 2]

[0094] In the above example table, the first entry indicates that HARQ processes from all configured cells are used, both dynamic and SPS processes are multiplexed, 16 SPS processes are used, all priorities are used, and the HARQ process ID range is 0-15.

[0095] A generic eType3CB indicator in a DCI of size log2(M) can be encoded into DCI format 1_1 or 1_2 as follows:

[0096] In one option, the generic eType3CB indicator is present only if DCI format 1_1 or 1_2 does not schedule a PDSCH and unused DCI fields (e.g., MCS, HARQ ID, NDI, TDRA) are reinterpreted for that purpose. If the DCI schedules a PDSCH, the first entry in the RRC configured table is taken.

[0097] In another option, the generic eType3CB indicator exists as a separate new field in DCI format 1_1 or 1_2 whenever an RRC table is provided.

[0098] Thus, in some embodiments, DCI format 1_1 or 1_2 may be used to trigger eType3CB. Separate presence configurations and common HARQ CB setting configurations may be used. A 1-bit "One-Shot HARQ-ACK Request" field may be used within the DCI to trigger eType3CB. A CB type indication may be included in the DCI to indicate the particular CB type to be used.

[0099] While the embodiments have been described with reference to certain exemplary embodiments, it will be apparent that various modifications and changes can be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative sense, and not a restrictive sense. The accompanying drawings, which form a part of this application, show, by way of example, and not by way of limitation, specific embodiments in which the subject matter may be practiced. The illustrated embodiments are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Therefore, this detailed description is not to be construed in a limiting sense, and the scope of various embodiments is defined only by the appended claims, including the full range of equivalents to which such claims are entitled.

[0100] Subject matter may be referred to herein by the term "embodiments," individually and / or collectively, merely for convenience and when more than one inventive concept is actually disclosed, without intending to intentionally limit the scope of the present application to any single inventive concept. Thus, while multiple specific embodiments have been shown and described herein, it should be understood that any configuration calculated to achieve the same purpose may be substituted for the multiple specific embodiments shown. The present disclosure is intended to cover any and all adaptations or modifications of the various embodiments. Combinations of the above embodiments, as well as other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

[0101] As used herein, the terms "a" or "an" are used to include one or more than one, as is common in patent documents, independently of any other instance or use of "at least one" or "one or more." As used herein, the term "or" is used to refer to something non-exclusive, or "A or B" is used to include "A but not B," "B but not A," and "A and B," unless otherwise stated. As used herein, the terms "including" and "in which" are used as the plain-language equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, i.e., a system, UE, article, composition, formulation, or process that includes multiple elements in addition to those listed after such term in a claim is still considered to be within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc., are used merely as labels and are not intended to impose numerical requirements on their objects.

[0102] The Abstract of the present disclosure is provided to comply with 37 C.F.R. 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Moreover, in the foregoing Detailed Description, various features may be found grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure should not be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter resides in fewer than all features of a single disclosed embodiment. Accordingly, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. 。 [Item 1] An apparatus for a user equipment (UE), comprising: decoding a radio resource control (RRC) configuration from a fifth generation NodeB (gNB) that includes at least one parameter indicating whether a Release 17 enhanced Type-3CB (eType3CB) or a Release 16 Type-3CB is used by the UE; decoding a physical downlink control channel (PDCCH) transmission from the gNB having a downlink control information (DCI) format that triggers transmission of an eType3CB codebook; constructing the eType3CB codebook in response to receiving the DCI format; Encoding the eType3CB codebook onto a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) for transmission to the gNB in ​​response to the DCI format. a processing circuit configured to: a memory configured to store the eType3CB codebook; An apparatus comprising: [Item 2] the DCI format is DCI format 1_1 or 1_2 and includes a priority field, triggering eType3CB and scheduling a physical downlink shared channel (PDSCH); Item 1, wherein all HARQ processes triggered by the DCI format or corresponding to a semi-persistent scheduling (SPS) configuration are multiplexed in the eType3CB. [Item 3] Item 1. The apparatus of item 1, wherein the RRC configuration includes a CB configuration field indicating that the eType3 CB configuration uses a set of DL cells selected from all configured downlink (DL) cells, all activated DL cells, and a subset of activated DL cells. [Item 4] the CB Construction field contains a single value; The presence of the CB Construction field indicates that the activated DL cell is used for the construction of the eType3 CB; 4. The apparatus of item 3, wherein the absence of the CB construction field indicates that a configured DL cell is used for the construction of the eType3 CB. [Item 5] the CB Configuration field has a value selected from two possible values; the presence of the CB Construction field having a first value of the two possible values ​​indicates that all activated DL cells are used to construct the eType3 CB; The presence of the CB Construction field having a second value of the two possible values ​​indicates that a corresponding DL cell indicated in a DCI format that triggers the eType3CB is used for the construction of the eType3CB; 4. The apparatus of item 3, wherein the absence of the CB construction field indicates that all configured DL cells are used for the construction of the eType3 CB. [Item 6] the DCI format is DCI format 1_1 or 1_2, includes a priority field, triggers eType3CB, and does not schedule a physical downlink shared channel (PDSCH); The device described in item 1, wherein the priority field is set to a value that indicates that only HARQ processes corresponding to a semi-persistent scheduling (SPS) configuration that is triggered by the DCI format or has a priority associated with the value are multiplexed in the eType3CB. [Item 7] the DCI format is DCI format 1_1 or 1_2, includes a priority field, triggers eType3CB, and does not schedule a physical downlink shared channel (PDSCH); Item 1. The device described in item 1, wherein the priority field is set to a first or second value, the first value indicating that only HARQ processes corresponding to a semi-persistent scheduling (SPS) configuration that is triggered by the DCI format or has a priority having the first value are multiplexed in the eType3CB, and the second value indicating that all HARQ processes corresponding to an SPS configuration that is triggered by the DCI format or has a priority having the first or second value are multiplexed in the eType3CB. [Item 8] the DCI format is DCI format 1_1 or 1_2, includes a priority field, triggers eType3CB, and does not schedule a physical downlink shared channel (PDSCH); the priority field is set to a first value, the first value indicating that only HARQ processes corresponding to a semi-persistent scheduling (SPS) configuration that is triggered by the DCI format or has a priority having the first value are multiplexed in the eType3CB; The processing circuitry is further configured to decode at least one of a radio resource control (RRC) message or a dynamic DCI format from the gNB to indicate a priority characteristic of the priority field set to a second value, the priority characteristic being: Only HARQ processes triggered by the DCI format or corresponding to an SPS configuration having a priority with the second value are multiplexed in the eType3CB; and All HARQ processes triggered by the DCI format or corresponding to the SPS configuration having a priority having the first or second value are multiplexed in the eType3CB. Item 1. The device according to item 1, shown among [Item 9] The DCI format is DCI format 1_1 or 1_2, includes unused fields, triggers eType3CB, and does not schedule a physical downlink shared channel (PDSCH); the unused field is selected from at least one of a modulation and coding scheme (MCS), a time domain resource allocation (TDRA), a HARQ process identification (ID), or a new data indicator (NDI); the unused field is set to one of a plurality of values ​​including: a first value indicating that only low-priority HARQ processes triggered by the DCI format or corresponding to a semi-persistent scheduling (SPS) configuration are multiplexed in the eType3CB; a second value indicating that only high-priority HARQ processes triggered by the DCI format or corresponding to the SPS configuration are multiplexed in the eType3CB; and a third value indicating that both low-priority and high-priority HARQ processes triggered by the DCI format or corresponding to the SPS configuration are multiplexed in the eType3CB; Item 1, wherein the eType3CB is constructed based on the actual number of received HARQ processes indicated by the unused field. [Item 10] The DCI format is DCI format 1_1 or 1_2, includes unused fields, triggers eType3CB, and does not schedule a physical downlink shared channel (PDSCH); the unused field is selected from at least one of a modulation and coding scheme (MCS), a time domain resource allocation (TDRA), a HARQ process identification (ID), or a new data indicator (NDI); the unused field is set to one of a plurality of values ​​including: a first value indicating that only low-priority HARQ processes triggered by the DCI format or corresponding to a semi-persistent scheduling (SPS) configuration are multiplexed in the eType3CB; a second value indicating that only high-priority HARQ processes triggered by the DCI format or corresponding to the SPS configuration are multiplexed in the eType3CB; and a third value indicating that both low-priority and high-priority HARQ processes triggered by the DCI format or corresponding to the SPS configuration are multiplexed in the eType3CB; The device described in item 1, wherein the eType3CB is constructed based on a nominal number of HARQ processes indicated by the unused field, and the nominal number of HARQ processes is configured by at least one of a radio resource control (RRC) message or a DCI format. [Item 11] the DCI format is DCI format 1_1 or 1_2, triggers eType3CB, and schedules a physical downlink shared channel (PDSCH); Item 1, wherein all HARQ processes triggered by the DCI format or corresponding to a semi-persistent scheduling (SPS) configuration are multiplexed in the eType3CB. [Item 12] Item 1, the processing circuitry is further configured to decode an RRC message from the gNB indicating that the eType3CB configuration uses only semi-persistent scheduling (SPS) HARQ processes. [Item 13] The DCI format is DCI format 1_1 or 1_2, includes unused fields, triggers eType3CB, and does not schedule a physical downlink shared channel (PDSCH); the unused field is selected from at least one of a modulation and coding scheme (MCS), a time domain resource allocation (TDRA), a HARQ process identification (ID), or a new data indicator (NDI); Item 1, wherein a predetermined number of least significant bits (LSBs) or most significant bits (MSBs) in the unused field indicate one eType3CB configuration selected from a plurality of possible eType3CB configurations, including using only semi-persistent scheduling (SPS) HARQ processes, using only dynamic HARQ processes, or using both SPS and dynamic HARQ processes. [Item 14] The processing circuitry is further configured to decode, from the gNB, an RRC message indicating a table providing a mapping of DCI field payloads to attribute combinations for eType3CB construction; Each row of the table contains a structure having fields indicating parameters for constructing an eType3CB; The parameters are: Carrier information, selectable between configured, activated, and indicated; a cell index of the carrier indicated by the carrier information; Semi-persistent scheduling (SPS) information, which can be selected from using all HARQ processes, using only SPS processes, and using only non-SPS processes; Priority information that can be selected between using all priority HARQ processes, using only high priority HARQ processes, and using only low priority HARQ processes; and HARQ process range including start process identifier (ID) and end process ID Item 1. The device according to item 1, comprising: [Item 15] Item 15. The apparatus of item 14, wherein the DCI format is DCI format 1_1 or 1_2, includes an unused field that provides the DCI field payload, triggers eType3CB, and does not schedule a physical downlink shared channel (PDSCH). [Item 16] Item 15. The device of item 14, wherein the DCI format is DCI format 1_1 or 1_2, includes a new field that provides the DCI field payload, and triggers eType3CB. [Item 17] An apparatus for a fifth generation NodeB (gNB), encoding a radio resource control (RRC) configuration for transmission to a user equipment (UE), the RRC configuration including at least one parameter indicating whether an enhanced Release 17 Type-3CB (eType3CB) or a Release 16 Type-3CB is to be used by the UE; encoding for transmission to the UE a physical downlink control channel (PDCCH) transmission having a downlink control information (DCI) format including an indication for a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) (HARQ-ACK) retransmission; decoding the HARQ-ACK retransmission from the UE in response to the DCI format; a processing circuit configured to a memory configured to store the HARQ-ACK retransmission; To prepare, equipment. [Item 18] the processing circuitry is further configured to encode for transmission to the UE a UE-specific configured RRC message indicating a row of a table providing a mapping of DCI field payloads to attribute combinations for eType3CB construction; Each row of the table contains a structure having fields indicating parameters for constructing an eType3CB; The parameters are: Carrier information, selectable between configured, activated, and indicated; a cell index of the carrier indicated by the carrier information; Semi-persistent scheduling (SPS) information, which can be selected from using all HARQ processes, using only SPS processes, and using only non-SPS processes; Priority information that can be selected between using all priority HARQ processes, using only high priority HARQ processes, and using only low priority HARQ processes; and HARQ process range including start process identifier (ID) and end process ID Item 18. The device according to item 17, comprising: [Item 19] 1. A non-transitory computer-readable storage medium storing instructions for execution by one or more processors of a fifth generation NodeB (gNB), the instructions, when executed, causing the one or more processors to: encoding a radio resource control (RRC) configuration for transmission to a user equipment (UE), the RRC configuration including at least one parameter indicating whether a Release 17 enhanced Type-3CB (eType3CB) or a Release 16 Type-3CB is to be used by the UE; encoding for transmission to the UE a physical downlink control channel (PDCCH) transmission having a downlink control information (DCI) format that triggers transmission of an eType3CB codebook; Decoding an eType3CB codebook from the UE to a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) in response to the DCI format. A non-transitory computer-readable storage medium configured to configure the gNB so as to [Item 20] When the instructions are executed, the one or more processors: and further configured to encode for transmission to the UE an RRC message indicating a row of a table providing a mapping of DCI field payloads to attribute combinations for eType3CB construction; Each row of the table contains a structure having fields indicating parameters for constructing an eType3CB; The parameters are: Carrier information, selectable between configured, activated, and indicated; a cell index of the carrier indicated by the carrier information; Semi-persistent scheduling (SPS) information, which can be selected from using all HARQ processes, using only SPS processes, and using only non-SPS processes; Priority information that can be selected between using all priority HARQ processes, using only high priority HARQ processes, and using only low priority HARQ processes; and HARQ process range including start process identifier (ID) and end process ID 20. The non-transitory computer-readable storage medium of item 19, comprising:

Claims

1. 1. An apparatus for a user equipment (UE) configured for operation in a fifth generation new radio (5G NR) network, the apparatus comprising: A processing circuit and a memory, the processing circuit Decoding radio resource control (RRC) configuration information received from a gNodeB (gNB) to enable an enhanced Type 3 HARQ-ACK codebook triggered by a downlink control information (DCI) format; Decoding the DCI format received from the gNB requesting a Type-3 HARQ-ACK codebook report; determining an index value from an enhanced Type 3 codebook indicator field in the DCI format, the index value indicating an index of the enhanced Type 3 HARQ-ACK codebook; If the DCI format does not schedule reception of a PDSCH and if the DCI format does not include the Enhanced Type 3 Codebook Indicator field, determining the index value from a value of a Modulation and Coding Scheme (MCS) field of the DCI format; Determine the enhanced Type 3 HARQ-ACK codebook based on the index value for transmission to the gNB. It is structured as follows: The DCI format is DCI format 1_2.

2. The processing circuit is configured to decode a one-shot HARQ-ACK request bit in the DCI format 1_2 to determine whether pdsch-HARQ-ACK-OneShotFeedback of the DCI format 1_2 is configured.

2. The device of claim 1 .

3. The apparatus of claim 2 , wherein a number of HARQ processes corresponds to the index value, and each bit of the enhanced Type 3 HARQ-ACK codebook is provided for each serving cell.

4. The apparatus of claim 3, wherein the processing circuitry is configured to determine a set of downlink cells and HARQ process numbers for the downlink cells to determine the enhanced Type 3 HARQ-ACK codebook.

5. The apparatus of claim 2 , wherein the DCI format 1_2 includes a field that triggers the enhanced Type 3 HARQ-ACK codebook.

6. The apparatus of claim 2 , wherein the DCI format 1_2 includes a field that triggers the enhanced Type 3 HARQ-ACK codebook when the DCI format 1_2 does not schedule a PDSCH.

7. 3. The apparatus of claim 2, wherein the processing circuitry is configured to provide HARQ-ACK information in response to the request on a physical downlink control channel (PDCCH) having the DCI format.

8. The apparatus of claim 1 , wherein the memory is configured to store the enhanced Type 3 HARQ-ACK codebook.

9. A processing circuit of a user equipment (UE) configured for operation in a fifth generation new radio (5G NR) network, comprising: decoding radio resource control (RRC) configuration information received from a gNodeB (gNB) to enable an enhanced Type 3 HARQ-ACK codebook triggered by a downlink control information (DCI) format; A procedure for decoding the DCI format received from the gNB requesting a Type-3 HARQ-ACK codebook report; determining an index value from an Enhanced Type 3 Codebook Indicator field in the DCI format, the index value indicating an index of the Enhanced Type 3 HARQ-ACK codebook; determining the index value from a value of a modulation and coding scheme (MCS) field of the DCI format if the DCI format does not schedule reception of a PDSCH and if the DCI format does not include the Enhanced Type 3 Codebook Indicator field; determining the enhanced Type 3 HARQ-ACK codebook based on the index value for transmission to the gNB; A computer program for causing the execution of The computer program, wherein the DCI format is DCI format 1_2.

10. The processing circuitry includes: and performing a procedure of decoding a one-shot HARQ-ACK request bit in the DCI format 1_2 and determining whether pdsch-HARQ-ACK-OneShotFeedback of the DCI format 1_2 is configured.

10. The computer program of claim 9.

11. The computer program product of claim 10 , wherein a number of HARQ processes corresponds to the index value, and each bit of the enhanced Type 3 HARQ-ACK codebook is provided for each serving cell.

12. The computer program of claim 11, wherein the computer program causes the processing circuit to perform a procedure of determining a set of downlink cells and HARQ process numbers for the downlink cells to determine the enhanced Type 3 HARQ-ACK codebook.

13. A computer readable storage medium storing a computer program according to any one of claims 9 to 12.

14. 1. An apparatus for a gNodeB (gNB) configured for operation in a fifth generation new radio (5G NR) network, the apparatus comprising: A processing circuit and a memory, the processing circuit encoding radio resource control (RRC) configuration information for transmission to a user equipment (UE), the RRC configuration information enabling enhanced Type 3 HARQ-ACK codebook triggering by a downlink control information (DCI) format; encoding the DCI format for transmission to the UE, the DCI format requesting a Type-3 HARQ-ACK codebook report; and the processing circuitry is further configured to encode the DCI format to include an enhanced Type 3 codebook indicator field indicating an index of the enhanced Type 3 HARQ-ACK codebook for use by the UE in determining an index value; the processing circuitry further comprising: if the DCI format does not schedule reception of a PDSCH and if the DCI format does not include the Enhanced Type 3 Codebook Indicator field, encoding a Modulation and Coding Scheme (MCS) field of the DCI format for use by the UE in determining the index value; and decoding the Enhanced Type 3 HARQ-ACK codebook generated by the UE based on the index value, wherein the Enhanced Type 3 HARQ-ACK codebook is received from the UE; The DCI format is DCI format 1_2.

15. The processing circuit is configured to include a one-shot HARQ-ACK request bit in the DCI format 1_2 to indicate to the UE whether pdsch-HARQ-ACK-OneShotFeedback of the DCI format 1_2 is configured.

15. The apparatus of claim 14.

16. The apparatus of claim 15 , wherein a number of HARQ processes corresponds to the index value, and each bit of the enhanced Type 3 HARQ-ACK codebook is provided for each serving cell.

17. The apparatus of claim 16, wherein the enhanced Type 3 HARQ-ACK codebook includes a set of downlink cells and HARQ process numbers for the downlink cells are determined by the UE.

Images