Redundancy gap indication for improved data transmission

Abstract

The techniques discussed herein may facilitate successful decoding of a physical downlink shared channel (PDSCH) based on a reduced number of retransmissions. Based on a given PDSCH, the embodiments discussed herein may transmit feedback (e.g., hybrid automatic repeat request (HARQ) feedback, channel state information (CSI) feedback) that indicates an amount of additional information that may allow a user equipment (UE) to successfully decode the PDSCH. In some embodiments, the feedback may indicate a requested redundant version (RV) sequence that may allow the UE to successfully decode the PDSCH. In other embodiments, the feedback may indicate the amount of additional information, and a receiving base station (BS) may select an RV sequence based on the amount of additional information.

Description

Background Art

[0001] Mobile communications in the next generation wireless communication system 5G or New Radio (NR) networks will provide ubiquitous connectivity and access to information and the ability to share data around the world. 5G networks and network slices will be unified, service-based frameworks that will target common and sometimes conflicting performance standards and provide services to extremely diverse application domains ranging from enhanced mobile broadband (eMBB) to massive machine type communications (mMTC), ultra-reliable low latency communications (URLLC) and other communications. In general, NR will evolve based on the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) Advanced technology and additional enhanced radio access technologies (RATs) to achieve seamless and faster wireless connectivity solutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Figure 1 is a block diagram illustrating the architecture of a system including a core network (CN), such as a fifth generation (5G) CN (5GC), according to various embodiments.

[0003] Figure 2 is a diagram illustrating example components of an apparatus that may be employed in accordance with various aspects discussed herein.

[0004] Figure 3 is a diagram illustrating an example interface of baseband circuitry that may be employed in accordance with various aspects discussed herein.

[0005] Figure 4 is a block diagram illustrating a system that facilitates enhanced feedback (e.g., hybrid automatic repeat request (HARQ), channel state information (CSI), etc.) to reduce the number of transmissions for a complete communication on a physical downlink shared channel (PDSCH) in accordance with various embodiments discussed herein.

[0006] Figure 5 is a diagram illustrating a first exemplary transmission scenario involving a single transmission of a PDSCH in conjunction with various aspects discussed herein.

[0007] Figure 6 is a diagram illustrating a second exemplary transmission scenario involving multiple transmissions of a PDSCH from one redundant version (RV) sequence from multiple transmit / receive points (TRPs) in conjunction with various aspects discussed herein.

[0008] Figure 7 is a diagram illustrating a third exemplary transmission scenario involving multiple transmissions of a PDSCH from one RV sequence with slot aggregation in conjunction with various aspects discussed herein.

[0009] Figure 8 is a diagram showing two different retransmission scenarios based on existing HARQ-ACK feedback in conjunction with various aspects discussed herein.

[0010] Fig. 9 is a diagram illustrating a first exemplary retransmission scenario involving a single initial transmission of a PDSCH and HARQ feedback indicating a suggested RV sequence according to various embodiments discussed herein.

[0011] Fig.10 is a diagram illustrating a second exemplary retransmission scenario involving initial transmission of multiple PDSCHs (eg, two RVs of an RV sequence) and HARQ feedback indicating a suggested RV sequence according to various embodiments discussed herein.

[0012] Fig.11 is a flow chart illustrating an example method that can be employed at a user equipment (UE) to facilitate generating HARQ feedback to a PDSCH indicating a redundancy gap associated with the PDSCH in accordance with various embodiments discussed herein.

[0013] Fig.12 is a flow chart illustrating an exemplary method that can be employed at a base station (BS) to facilitate retransmission of a PDSCH based on HARQ feedback indicating a redundancy gap associated with the PDSCH in accordance with various embodiments discussed herein.

[0014] Fig.13 is a flow chart illustrating an example method that can be employed at a UE to facilitate generating CSI feedback based on a reference PDSCH indicating a redundancy gap associated with the PDSCH in accordance with various embodiments discussed herein.

[0015] Fig.14 is a flow chart illustrating an example method that can be employed at a BS to facilitate receiving CSI feedback based on a reference PDSCH indicating a redundancy gap associated with the PDSCH in accordance with various embodiments discussed herein.

[0016] Fig.15 is a flow chart illustrating an example method that can be employed at a UE to facilitate generating enhanced feedback based on a PDSCH that facilitates a BS in determining a redundancy gap associated with the PDSCH in accordance with various embodiments discussed herein.

[0017] Fig.16is a flow chart illustrating an exemplary method that can be employed at a BS to facilitate the BS in determining a redundancy gap associated with a PDSCH based on enhanced feedback associated with the PDSCH in accordance with various embodiments discussed herein. DETAILED DESCRIPTION

[0018] The present disclosure will now be described with reference to the accompanying drawings, wherein throughout the text, similar figure numerals are used to refer to similar elements, and the structures and devices shown therein need not be drawn to scale. As used herein, the terms "component", "system", "interface", etc. are intended to refer to entities, hardware, software (e.g., in execution) and / or firmware related to computers. For example, a component may be a processor (e.g., a microprocessor, a controller or other processing device), a process running on a processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet computer, and / or a user equipment with a processing device (e.g., a mobile phone or other devices configured to communicate via a 3GPP RAN, etc.). By way of example, an application program and a server running on a server may also be a component. One or more components may reside in a process, and a component may be located on a computer and / or distributed between two or more computers. A group of elements or a group of other components may be described herein, wherein the term "group" may be interpreted as "one or more", unless the context otherwise indicates (e.g., "empty group", "a group of two or more Xs", etc.).

[0019] In addition, the components can execute from various computer-readable storage media having various data structures stored thereon, such as using modules, for example. The components can communicate via local and / or remote processes, such as according to signals having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or throughout a network, such as the Internet, a local area network, a wide area network, or a similar network with other systems via signals).

[0020] As another example, a component may be a device having a specific function provided by a mechanical component operated by electrical or electronic circuitry, wherein the electrical or electronic circuitry may be operated by a software application or firmware application executed by one or more processors. The one or more processors may be internal or external to the device and may execute at least a portion of the software or firmware application. As another example, a component may be a device that provides a specific function by an electronic component without the need for a mechanical component; the electronic component may include one or more processors therein to execute at least a portion of the software and / or firmware that imparts the function to the electronic component.

[0021] The use of the word "exemplary" is intended to present concepts in a specific way. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive arrangement. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing cases. In addition, the articles "one" and "an" used in this application and the appended claims should generally be interpreted as meaning "one or more" unless otherwise specified or clear from the context to point to a singular form. In addition, to the extent that the terms "including", "comprising", "having", "having", "with" or variations thereof are used in the detailed description and claims, such terms are intended to be included in a manner similar to the term "comprising". In addition, in the case of discussing one or more numbered items (e.g., "first X", "second X", etc.), generally, one or more numbered items may be different or they may be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0022] As used herein, the term "circuit" may refer to, may be part of, or may include an application specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or group), and / or memory (shared, dedicated, or group) that executes one or more software or firmware programs, combinational logic circuits, and / or other suitable hardware components that provide the described functionality. In some embodiments, a circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, a circuit may include logic that is at least partially operable in hardware.

[0023]

[0013] Various aspects discussed herein may be directed to facilitating wireless communications, and the nature of these communications may vary.

[0024] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0025] The embodiments described herein may be implemented into a system using any suitably configured hardware and / or software. Figure 1The architecture of a system 100 including a core network (CN) 120 (e.g., a fifth generation (5G) CN (5GC)) according to various embodiments is shown. The system 100 is shown to include: a UE 101, which may be the same or similar to one or more other UEs discussed herein; a third generation partnership project (3GPP) radio access network (radio AN or RAN) or other (e.g., non-3GPP) AN, (R) AN 210, which may include one or more RAN nodes (e.g., evolved Node B (eNB)), next generation Node B (gNB and / or other nodes) or other nodes or access points; and a data network (DN) 203, which may be, for example, an operator service, Internet access, or a third party service; and a fifth generation core network (5GC) 120. 5GC 120 may include one or more of the following functions and network components: authentication server function (AUSF) 122; access and mobility management function (AMF) 121; session management function (SMF) 124; network exposure function (NEF) 123; policy control function (PCF) 126; network repository function (NRF) 125; unified data management (UDM) 127; application function (AF) 128; user plane (UP) function (UPF) 102; and network slice selection function (NSSF) 129.

[0026] The UPF 102 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external protocol data unit (PDU) session point interconnected with the DN 103, and a branch point to support multi-homed PDU sessions. The UPF 102 may also perform packet routing and forwarding, perform packet inspection, perform the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing on the user plane (e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement), perform uplink traffic verification (e.g., service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 102 may include an uplink classifier for supporting routing of traffic to a data network. The DN 103 may represent various network operator services, Internet access, or third-party services. The DN 103 may include or be similar to an application server. UPF 102 may interact with SMF 124 via an N4 reference point between SMF 124 and UPF 102.

[0027] AUSF 122 may store data for authentication of UE 101 and handle authentication-related functions. AUSF 122 may facilitate a common authentication framework for various access types. AUSF 122 may communicate with AMF 121 via an N12 reference point between AMF 121 and AUSF 122; and may communicate with UDM 127 via an N13 reference point between UDM 127 and AUSF 122. In addition, AUSF 122 may present an interface based on Nausf services.

[0028] AMF 121 may be responsible for registration management (e.g., responsible for registering UE 101, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. AMF 121 may be the termination point of the N11 reference point between AMF 121 and SMF 124. AMF 121 may provide transport for SM messages between UE 101 and SMF 124, and act as a transparent proxy for routing SM messages. AMF 121 may also provide communication between UE 101 and Short Message Service (SMS) Function (SMSF) ( Figure 1 101). The AMF 121 may provide transport for SMS messages between the (R)AN 110 and the AMF 121. The AMF 121 may act as a security anchor function (SEAF), which may include interaction with the AUSF 122 and the UE 101 and / or receiving intermediate keys established as a result of the UE 101 authentication process. In the case of using authentication based on the Universal Subscriber Identity Module (USIM), the AMF 121 may retrieve security material from the AUSF 122. The AMF 121 may also include a single connection mode (SCM) function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF 121 may be a termination point for a RAN control plane (CP) interface, which may include or be an N2 reference point between the (R)AN 110 and the AMF 121; and the AMF 121 may be a termination point for non-access stratum (NAS) (N1) signaling, and perform NAS encryption and integrity protection.

[0029] The AMF 121 may also support NAS signaling with the UE 101 over a non-3GPP (N3) interworking function (IWF) interface. The N3IWF may be used to provide access to untrusted entities. The N3IWF may be the termination point for the N2 interface between the (R)AN 110 and the AMF 121 for the control plane, and may be the termination point for the N3 reference point between the (R)AN 110 and the UPF 102 for the user plane. Thus, the AMF 121 may process N2 signaling for PDU sessions and QoS from the SMF 124 and the AMF 121, encapsulate / decapsulate packets for Internet Protocol (IP) Security (IPSec) and N3 tunnels, mark N3 user plane packets in the uplink, and enforce QoS requirements corresponding to N3 packet markings, thereby taking into account QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 101 and the AMF 121 via the N1 reference point between the UE 101 and the AMF 121, and relay uplink and downlink user plane packets between the UE 101 and the UPF 102. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 101. The AMF 121 may present an interface based on the Namf service, and may be an N14 reference point between the two AMFs 121 and an N14 reference point between the AMF 121 and the 5G Equipment Identity Register (5G-EIR) ( Figure 1 The termination point of the N17 reference point between (not shown).

[0030] UE 101 may register with AMF 121 in order to receive network services. Registration Management (RM) is used to register UE 101 with the network (e.g., AMF 121) or deregister UE 101, and to establish a UE context in the network (e.g., AMF 121). UE 101 may operate in an RM-REGISTRED state or an RM-DEREGISTRED state. In the RM-DEREGISTERED state, UE 101 is not registered with the network, and the UE context in AMF 121 does not maintain valid location or routing information of UE 101, so AMF 121 cannot reach UE 101. In the RM-REGISTERED state, UE 101 is registered with the network, and the UE context in AMF 121 may maintain valid location or routing information of UE 101, so AMF 121 can reach UE 101. In the RM-REGISTERED state, UE 101 may perform a mobility registration update procedure, perform a periodic registration update procedure triggered by expiration of a periodic update timer (e.g., to notify the network that UE 101 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.

[0031] AMF 121 may store one or more RM contexts for UE 101, each RM context being associated with a specific access to the network. An RM context may be a data structure, a database object, or the like, which in particular indicates or stores a registration status and a periodic update timer for each access type. AMF 121 may also store a 5GC Mobility Management (MM) context, which may be the same or similar to an (Enhanced Packet System (EPS)) MM ((E)MM) context. In various embodiments, AMF 121 may store coverage enhancement (CE) mode B restriction parameters for UE 101 in an associated MM context or RM context. AMF 121 may also derive values ​​from usage setting parameters of the UE already stored in the UE context (and / or MM / RM context) when necessary.

[0032] Connection Management (CM) may be used to establish and release a signaling connection between the UE 101 and the AMF 121 through the N1 interface. The signaling connection is used to implement NAS signaling exchanges between the UE 101 and the CN 120, and includes a signaling connection between the UE and the AN (e.g., an RRC connection or a UE-N3IWF connection for non-3GPP access) and an N2 connection between the UE 101 in the AN (e.g., the RAN 110) and the AMF 121. The UE 101 may operate in one of two CM states (CM IDLE mode or CM-CONNECTED mode). When the UE 101 operates in the CM-IDLE state / mode, the UE 101 may not have a NAS signaling connection established with the AMF 121 through the N1 interface, and there may be a (R)AN 110 signaling connection (e.g., N2 and / or N3 connection) for the UE 101. When the UE 101 operates in the CM-CONNECTED state / mode, the UE 101 may have a NAS signaling connection established with the AMF 121 through the N1 interface, and there may be a (R)AN 110 signaling connection (e.g., N2 and / or N3 connection) for the UE 101. Establishing an N2 connection between the (R)AN 110 and the AMF 121 may cause the UE 101 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the (R)AN 110 and the AMF 121 is released, the UE 101 may transition from the CM-CONNECTED mode to the CM-IDLE mode.

[0033] SMF 124 may be responsible for session management (SM) (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering of the UPF to route traffic to the correct destination; terminating the interface toward the policy control function; control portion of policy enforcement and QoS; lawful interception (for SM events and interface with the lawful interception (LI) system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to the AN via the AMF over N2; and determining the session and service continuity (SSC) mode for the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or implements the exchange of PDUs between a UE 101 and a data network (DN) 103 identified by a data network name (DNN). The PDU session may be established upon request by UE 101, modified upon request by UE 101 and 5GC 120, and released upon request by UE 101 and 5GC 120 using NAS SM signaling exchanged between UE 101 and SMF 124 over the N1 reference point. Upon request from an application server, 5GC 120 may trigger a specific application in UE 101. In response to receiving a trigger message, UE 101 may deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 101. The identified applications in UE 101 may establish a PDU session with a specific DNN. SMF 124 may check whether the UE 101 request complies with user subscription information associated with UE 101. In this regard, SMF 124 may retrieve and / or request to receive update notifications about SMF 124 level subscription data from UDM 127.

[0034] SMF 124 may include the following roaming functions: handling local execution to apply QoS service level agreements (SLAs) (visited public land mobile network (VPLMN)); charging data collection and charging interface (VPLMN); lawful interception (for SM events and interface with LI system, in VPLMN); and support interaction with external DN to transmit signaling for PDU session authorization / authentication through external DN. In a roaming scenario, an N16 reference point between two SMFs 124 may be included in the system 100, which may be located between an SMF 124 in a visited network and another SMF 124 in a home network. In addition, SMF 124 may present an interface based on Nsmf services.

[0035] NEF 123 may provide components for securely exposing services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, application functions (e.g., AF 128), edge computing or fog computing systems, etc. In such embodiments, NEF 123 may authenticate, authorize and / or restrict AF. NEF 123 may also convert information exchanged with AF 128 and information exchanged with internal network functions. For example, NEF 123 may convert between AF service identifiers and internal 5GC information. NEF 123 may also receive information from other network functions (NFs) based on the exposure capabilities of other network functions. The information may be stored at NEF 123 as structured data, or stored at a data storage NF using a standardized interface. The stored information may then be re-exposed to other NFs and AFs by NEF 123, and / or used for other purposes such as analysis. In addition, NEF 123 may present an interface based on Nnef services.

[0036] NRF 125 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 125 also maintains information of available NF instances and the services they support. As used herein, the term "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, which may occur, for example, during the execution of a program code. In addition, NRF 125 may present an interface based on Nnrf services.

[0037] The PCF 126 may provide for control plane functions to enforce their policy rules, and may also support a unified policy framework for managing network behavior. The PCF 126 may also implement FEs to access subscription information related to policy decisions in the UDR of the UDM 127. The PCF 126 may communicate with the AMF 121 via the N15 reference point between the PCF 126 and the AMF 121, which may include the PCF 126 in the visited network and the AMF 121 in the case of a roaming scenario. The PCF 126 may communicate with the AF 128 via the N5 reference point between the PCF 126 and the AF 128; and communicate with the SMF 124 via the N7 reference point between the PCF 126 and the SMF 124. The system 100 and / or the CN 120 may also include an N24 reference point between the PCF 126 (in the home network) and the PCF 126 in the visited network. In addition, the PCF 126 may present an interface based on Npcf services.

[0038] The UDM 127 may process subscription-related information to support the handling of communication sessions by network entities, and may store subscription data of the UE 101. For example, subscription data may be transferred between the UDM 127 and the AMF 121 via an N8 reference point between the UDM 127 and the AMF. The UDM 127 may include two parts: an application function entity (FE) and a unified data repository (UDR) (the FE and the UDR are in Figure 1 126). The UDR may store subscription data and policy data of the UDM 127 and PCF 126, and / or structured data for exposure of the NEF 123 and application data (including packet flow descriptions (PFDs) for application detection, application request information of multiple UEs 101). The Nudr service-based interface may be presented by the UDR 221 to allow the UDM 127, PCF 126, and NEF 123 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in the UDR. The UDM may include a UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different FEs may serve the same user. The UDM-FE accesses the subscription information stored in the UDR, and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. The UDR may interact with the SMF 124 via the N10 reference point between the UDM 127 and the SMF 124. UDM 127 may also support SMS management, where SMS-FE implements similar application logic as discussed elsewhere herein.In addition, UDM 127 may present an interface based on Nudm services.

[0039] AF 128 can provide application influence on traffic routing, provide access to NEF 123, and interact with the policy framework for policy control. 5GC 120 and AF 128 can provide information to each other via NEF 123, which can be used for edge computing implementation. In such implementation, network operators and third-party services can be hosted near the UE101 access point of the attachment to achieve effective service delivery through reduced end-to-end delay and load on the transmission network. For edge computing implementation, 5GC can select UPF 102 near UE 101 and perform traffic steering from UPF 102 to DN 103 via N6 interface. This can be based on UE subscription data, UE location and information provided by AF 128. In this way, AF 128 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 128 is considered a trusted entity, the network operator can allow AF128 to interact directly with the relevant NF. In addition, AF 128 can present an interface based on Naf services.

[0040] NSSF 129 may select a set of network slice instances to serve UE 101. NSSF 129 may also appropriately determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI). NSSF 129 may also determine the set of AMFs to be used to serve UE 101, or a list of candidate AMFs 121, based on appropriate configuration and possibly by querying NRF 125. The selection of a set of network slice instances for UE 101 may be triggered by AMF 121, where UE 101 registers by interacting with NSSF 129, which may result in changes to AMF 121. NSSF 129 may interact with AMF 121 via the N22 reference point between AMF 121 and NSSF 129; and may communicate via the N31 reference point ( Figure 1 129 in the visited network. In addition, the NSSF 129 may present an interface based on the Nnssf service.

[0041] As discussed previously, CN 120 may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages from / to other entities, such as an SMS-Gateway Mobile Services Switching Center (GMSC) / Interworking MSC (IWMSC) / SMS router, to / from UE 101. The SMSF may also interact with AMF 121 and UDM 127 for notification procedures that UE 101 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 127 when UE 101 is available for SMS).

[0042] CN 120 may also include Figure 1 Other elements not shown, such as data storage system / architecture, 5G-EIR, security edge protection proxy (SEPP), etc. The data storage system may include structured data storage function (SDSF), unstructured data storage function (UDSF), etc. Any NF can communicate with any NF and UDSF ( Figure 1 The N18 reference point between the NFs (not shown) stores or retrieves unstructured data in or from the UDSF (e.g., UE context). Each NF may share a UDSF for storing its corresponding unstructured data, or each NF may each have its own UDSF located at or near each NF. In addition, the UDSF may present an interface based on the Nudsf service ( Figure 15G-EIR may be a NF that checks the status of a Permanent Equipment Identifier (PEI) to determine whether to blacklist a specific equipment / entity from the network; and SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.

[0043] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Figure 1 These interfaces and reference points are omitted. In one example, CN 120 may include an Nx interface, which is an inter-CN interface between an MME (e.g., a non-5G MME) and AMF 121, to enable interworking between CN 120 and a non-5G CN. Other exemplary interfaces / reference points may include an interface based on N5g-EIR services presented by 5G-EIR, an N27 reference point between a network repository function (NRF) in a visited network and an NRF in a home network; and an N31 reference point between an NSSF in a visited network and an NSSF in a home network.

[0044] Figure 2 Exemplary components of a device 200 according to some embodiments are shown. In some embodiments, the device 200 may include at least an application circuit 202, a baseband circuit 204, a radio frequency (RF) circuit 206, a front-end module (FEM) circuit 208, one or more antennas 210, and a power management circuit (PMC) 212 coupled together as shown. The components of the illustrated device 200 may be included in a UE or a RAN node. In some embodiments, the device 200 may include fewer elements (e.g., the RAN node cannot utilize the application circuit 202, but includes a processor / controller to process IP data received from a CN such as a 5GC 120 or an evolved packet core (EPC)). In some embodiments, the device 200 may include additional elements, such as a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the following components may be included in more than one device (e.g., the circuit may be separately included in more than one device for a specific implementation of a cloud-RAN (C-RAN)).

[0045] The application circuit 202 may include one or more application processors. For example, the application circuit 202 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the device 200. In some embodiments, the processor of the application circuit 202 may process IP data packets received from the EPC.

[0046] The baseband circuit 204 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 204 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 206 and generate baseband signals for the transmit signal path of the RF circuit 206. The baseband circuit 204 may interface with the application circuit 202 to generate and process baseband signals and control the operation of the RF circuit 206. For example, in some embodiments, the baseband circuit 204 may include a third generation (3G) baseband processor 204A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or other baseband processors 204D of other existing generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 204 (e.g., one or more baseband processors 204A-D) may handle various radio control functions that may communicate with one or more radio networks via the RF circuit 206. In other embodiments, some or all of the functions of the baseband processors 204A-D may be included in a module stored in the memory 204G and executed via the central processing unit (CPU) 204E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 204 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0047] In some embodiments, the baseband circuit 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSP 204F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 204 and the application circuit 202 may be implemented together, such as, for example, on a system on a chip (SOC).

[0048] In some embodiments, the baseband circuitry 204 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 204 may support communications with NG-RAN, Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), wireless personal area networks (WPANs), etc. Embodiments in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0049] RF circuit 206 can communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 206 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 206 may include a receive signal path, which may include circuits that down-convert RF signals received from FEM circuit 208 and provide baseband signals to baseband circuit 204. RF circuit 206 may also include a transmit signal path, which may include circuits that up-convert baseband signals provided by baseband circuit 204 and provide RF output signals to FEM circuit 208 for transmission.

[0050] In some embodiments, the receive signal path of the RF circuit 206 may include a mixer circuit 206a, an amplifier circuit 206b, and a filter circuit 206c. In some embodiments, the transmit signal path of the RF circuit 206 may include a filter circuit 206c and a mixer circuit 206a. The RF circuit 206 may also include a synthesizer circuit 206d for synthesizing the frequencies used by the mixer circuit 206a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 206a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 208 based on the synthesized frequency provided by the synthesizer circuit 206d. The amplifier circuit 206b may be configured to amplify the down-converted signal, and the filter circuit 206c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 204 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 206a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0051] In some embodiments, mixer circuit 206a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 206d to generate an RF output signal for FEM circuit 208. The baseband signal can be provided by baseband circuit 204 and can be filtered by filter circuit 206c.

[0052] In some embodiments, the mixer circuit 206a of the receiving signal path and the mixer circuit 206a of the transmission signal path may include two or more mixers and may be arranged for orthogonal down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 206a of the receiving signal path and the mixer circuit 206a of the transmission signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 206a of the receiving signal path and the mixer circuit 206a of the transmission signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 206a of the receiving signal path and the mixer circuit 206a of the transmission signal path may be configured for superheterodyne operation.

[0053] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuit 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 204 may include a digital baseband interface to communicate with RF circuit 206.

[0054] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0055] In some embodiments, synthesizer circuit 206d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, synthesizer circuit 206d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0056] Synthesizer circuit 206d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 206a of RF circuit 206. In some embodiments, synthesizer circuit 206d may be a fractional-N / N+1 synthesizer.

[0057] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 204 or application circuitry 202 depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application circuitry 202.

[0058] The synthesizer circuit 206d of the RF circuit 206 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a D-type flip-flop set. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0059] In some embodiments, the synthesizer circuit 206d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 206 can include an IQ / polarity converter.

[0060] The FEM circuitry 208 may include a receive signal path that may include circuitry configured to operate on RF signals received from the one or more antennas 210, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 206 for further processing. The FEM circuitry 208 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 206 for transmission via one or more of the one or more antennas 210. In various embodiments, amplification by either the transmit or receive signal path may be accomplished only in the RF circuitry 206, only in the FEM circuitry 208, or in both the RF circuitry 206 and the FEM circuitry 208.

[0061] In some embodiments, the FEM circuit 208 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 206). The transmit signal path of the FEM circuit 208 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuit 206), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 210).

[0062] In some embodiments, PMC 212 can manage the power provided to baseband circuit 204. Specifically, PMC 212 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When device 200 is capable of being powered by a battery, for example, when the device is included in a UE, PMC 212 can generally be included. PMC 212 can improve power conversion efficiency while providing a desired implementation size and heat dissipation characteristics.

[0063] Although Figure 2PMC 212 is shown coupled only to baseband circuit 204. However, in other embodiments, PMC 212 may be additionally or alternatively coupled to other components (such as, but not limited to, application circuit 202, RF circuit 206, or FEM circuit 208) and perform similar power management operations.

[0064] In some embodiments, the PMC 212 may control or otherwise be part of various power saving mechanisms of the device 200. For example, if the device 200 is in the RRC_Connected state, where it is still connected to the RAN node as expected to receive traffic soon, then after a period of inactivity, it may enter a state known as discontinuous reception mode (DRX). During this state, the device 200 may be powered off for short time intervals, thereby saving power.

[0065] If there is no data traffic activity for an extended period of time, the device 200 may transition to the RRC_Idle state, in which it is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 200 enters a very low power state, and it performs paging, in which it wakes up periodically again to listen to the network, and then powers down again. The device 200 may not receive data in this state; in order to receive data, the device may transition back to the RRC_Connected state.

[0066] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0067] The processor of the application circuit 202 and the processor of the baseband circuit 204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 204 can be used alone or in combination to perform the functions of Layer 3, Layer 2, or Layer 1, while the processor of the application circuit 202 can utilize data received from these layers (e.g., packet data) and further perform the functions of Layer 4 (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, Layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, Layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0068] Figure 3An exemplary interface of a baseband circuit according to some embodiments is shown. As discussed above, Figure 2 The baseband circuit 204 may include processors 204A-204E and a memory 204G used by the processors. Each of the processors 204A-204E may include a memory interface 304A-304E, respectively, to send / receive data to / from the memory 204G.

[0069] The baseband circuit 204 may also include: one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 312 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204); an application circuit interface 314 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 204); Figure 2 RF circuit interface 316 (for example, for sending / receiving data to / from the application circuit 202); Figure 2 an interface for sending / receiving data to / from a RF circuit 206); a wireless hardware connection interface 318 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Parts (e.g. Low Energy), components and other communication components to send / receive data); and a power management interface 320 (eg, an interface for sending / receiving power or control signals to / from PMC212).

[0070] As discussed in more detail herein, various embodiments that may be employed, for example, at a UE or a base station (e.g., a node of a RAN, such as a next-generation Node B (gNB), an evolved Node B (eNB), etc.) may transmit enhanced feedback (e.g., HARQ (hybrid automatic repeat request), CSI (channel state information), etc.) in accordance with the techniques discussed in more detail below, which may facilitate data communication based on fewer transmissions. In various embodiments, the UE may transmit and the BS may receive feedback (e.g., HARQ, CSI, etc.) associated with a physical downlink shared channel (PDSCH) transmission that indicates the number of additional coded bits that will allow the UE to decode the PDSCH based on current transmission parameters. In some embodiments, the feedback may indicate one or more redundancy versions (RVs) that the BS may transmit to facilitate the UE to decode the PDSCH. In the same or other embodiments, enhanced CSI feedback may be provided in accordance with the techniques discussed herein, which may facilitate more accurate MCS (modulation and coding scheme) selection.

[0071] refer to Figure 4, a block diagram of a system 400 that can be employed at a UE (user equipment), a next generation Node B (gNodeB or gNB) or other BS (base station) / TRP (transmission / reception point) or another component of a 3GPP (third generation partnership project) network (e.g., a 5GC (fifth generation core network)) component or function such as a UPF (user plane function)) according to various embodiments discussed herein, the system facilitates enhanced feedback (e.g., HARQ, CSI, etc.) to reduce the number of transmissions of a complete communication of a PDSCH. The system 400 may include a processor 410, a communication circuit 420, and a memory 430. The processor 410 (e.g., which may include one or more of 202 and / or 204A-204F, etc.) may include processing circuits and associated interfaces (e.g., a communication interface (e.g., RF circuit interface 316) for communicating with the communication circuit 420, a memory interface (e.g., memory interface 312) for communicating with the memory 430, etc.). The communication circuit 420 may include, for example, circuits for wired and / or wireless connections (e.g., 206 and / or 208), which may include a transmitter circuit (e.g., associated with one or more transmission chains) and / or a receiver circuit (e.g., associated with one or more reception chains), wherein the transmitter circuit and the receiver circuit may employ common and / or different circuit elements, or a combination thereof. The memory 430 may include one or more memory devices (e.g., memory 204G, local memory (e.g., including CPU registers of the processor discussed herein), etc.), which may have any of a variety of storage media (e.g., volatile and / or non-volatile according to any of a variety of technologies / constructions, etc.), and may store instructions and / or data associated with one or more of the processor 410 or the communication circuit 420.

[0072] A particular type of implementation of system 400 (eg, UE implementation) may be indicated via a subscript (eg, system 400 UE Including processor 410 UE , communication circuit 420 UE and memory 430 UE In some embodiments, such as BS embodiments (eg, system 400 gNB ) and network components (eg, UPF (User Plane Function), etc.) implementation scheme (eg, system 400 UPF ), processor 410 gNB (etc.), communication circuits (eg, 420 gNB etc.) and memory (e.g., 430 gNBThe signaling or messaging between different embodiments of system 400 (e.g., 4001 and 4002) may be generated by processor 4101, transmitted by communication circuit 4201 over a suitable interface or reference point (e.g., 3GPP air interface N3, N4, etc.), received by communication circuit 4202, and processed by processor 4102. Depending on the type of interface, additional components (e.g., antennas, network ports, etc. associated with systems 4001 and 4002) may participate in the communication.

[0073] In various aspects discussed herein, signals and / or messages may be generated and output for transmission, and / or transmitted messages may be received and processed. Depending on the type of signal or message generated, outputting for transmission (e.g., by processor 410, etc.) may include one or more of generating a set of associated bits indicating the content of the signal or message, encoding (e.g., which may include adding a cyclic redundancy check (CRC) and / or encoding via one or more of a turbo code, a low-density parity check (LDPC) code, a tail-biting convolutional code (TBCC), etc.), scrambling (e.g., based on a scrambling seed), modulation (e.g., via one of binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), or some form of quadrature amplitude modulation (QAM), etc.), and / or resource mapping to one or more resource elements (REs) (e.g., a scheduled resource set, a set of time and frequency resources authorized for uplink transmission, etc.), where each RE may span one subcarrier in the frequency domain and one symbol in the time domain (e.g., where a symbol may be according to any of a variety of access schemes, such as orthogonal frequency division multiplexing (OFDM), single carrier frequency division multiple access (SC-FDMA), etc.). Depending on the type of signal or message received, processing (e.g., by processor 410, etc.) may include one or more of the following operations: identifying physical resources associated with the signal / message, detecting the signal / message, resource element group deinterleaving, demodulating, descrambling and / or decoding.

[0074] In various aspects, one or more of information (e.g., system information, resources associated with signaling, etc.), features, parameters, etc., may be received from a gNB or other access point (e.g., via a processor 410) via signaling (e.g., associated with one or more layers, such as L1 signaling or higher layer signaling (e.g., MAC, RRC, etc.) gNB Generate, by the communication circuit 420 gNB Transmission, by communication circuit 420 UE received and processed by processor 410 UEThe type of signaling employed and / or the exact details of the operations performed at the UE and / or gNB in ​​the process (e.g., signaling structure, processing of PDUs / SDUs, etc.) may vary depending on the type of information, features, parameters, etc. However, for convenience, such operations may be referred to herein as configuring information / features / parameters / etc. to the UE, generating or processing configuration signaling, or by similar terminology.

[0075] At RAN#86 (3GPP (3rd Generation Partnership Project) RAN (Radio Access Network) Meeting Number 86), a new work item "Enhanced Industrial IoT and URLLC support" was approved. The approved work item has five objectives.

[0076] The first objective is to study, identify and, if needed, specify appropriate physical layer feedback enhancements to meet URLLC ("Ultra-Reliable and Low-Latency Communications") requirements and / or target coverage: (a) UE feedback enhancements for Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) [RAN1 (RAN WG1 (Working Group 1))] and (b) CSI (Channel State Information) feedback enhancements to allow more accurate MCS (Modulation and Coding Scheme) selection [RAN1].

[0077] The second objective is to identify potential enhancements to ensure Release 16 functionality is compatible with unlicensed band URLLC / IIoT (Industrial IoT) operations in a controlled environment [RAN1, RAN2] and to clarify the detailed objectives in RAN#87 based on the basic issues identified in RAN#87 (if any).

[0078] The third objective is to perform intra-UE multiplexing and prioritization of traffic with different priorities, building on the work done in Rel-16 [RAN1], including specifying the multiplexing behavior between HARQ-ACK / SR (Scheduling Request) / CSI and PUSCH (Physical Uplink Shared Channel) for traffic with different priorities, including the case of UCI (Uplink Control Information) on PUCCH (Physical Uplink Control Channel) and UCI on PUSCH.

[0079] The fourth objective is to enhance support for time synchronization, including (a) RAN impact of SA2 on uplink time synchronization of TSN (Transmission Sequence Number) (if any) [RAN2]; and (b) propagation delay compensation enhancements (including mobility issues, if any) [RAN2, RAN1, RAN3, RAN4].

[0080] The fifth objective is RAN enhancements (if any) based on new QoS (Quality of Service) related parameters, such as Time to Live, decided by SA2 [RAN2, RAN3].

[0081] Under the first objective, HARQ feedback enhancement and CSI feedback enhancement should be studied.

[0082] Various implementations may provide enhanced HARQ feedback and enhanced CSI feedback capable of meeting URLLC / IIoT requirements / goals.

[0083] During the URLLC / IIoT study item phase of Rel-16, companies studied the processing timelines for URLLC / IIoT and the evaluation results are presented in 3GPP Technical Report (TR) 38.824. To support URLLC / IIoT with stringent latency requirements / targets, in one approach, the network may conservatively select the MCS level and ensure that the UE is likely to receive a single transmission and successfully decode the transmitted data packets. With this transmission approach, the number of UEs that can be supported in the network may be very small, as each UE consumes a lot of resources while the MCS level is allocated low, resulting in low system spectral efficiency of the network. Given that spectrum may be quite scarce, serving a small number of UEs while meeting the latency and reliability requirements of URLLC may not be an economically viable solution. In another approach, the network may not select the MCS level too conservatively for the first transmission, for example setting the block error rate (BER) to 10 -1 (10%) or 10 -2 (1%), not 10 -6 ; Then, for most cases, the first transmission of a transport block has a non-trivial probability (1-10 -1 ) or (1-10 -2 ) leads to successful decoding at the UE; then, only for a small fraction of cases (10 -1 (10%) or 10 -2 ), HARQ retransmission will occur. For retransmission, the base station can choose a robust transmission to ensure high reliability (for example, the error rate after retransmission is 10 -6 ). Compared with the first method, the second method can achieve higher system spectrum efficiency.

[0084] It can also be seen from the evaluation of the research project phase that in many cases, the second transmission (or the first retransmission) is the only opportunity for the network to retransmit the transport block, because the latency requirement / target may be very strict (e.g., 1 ms). Therefore, how the UE provides useful feedback information to the network becomes a key issue.

[0085] There are two problems with the current NR framework of hybrid ARQ (Automatic Repeat Request) transmission scheme and CSI feedback framework.

[0086] The first problem is that in the existing hybrid ARQ (HARQ) transmission scheme, the UE responds to the successful or failed decoding of the transport block with an ACK or NACK feedback HARQ-ACK; the network retransmits the transport block with an additional PDSCH; and the UE tests whether the transport block can be successfully decoded with the new available soft bits, thereby generating another HARQ-ACK feedback. The hybrid feedback retransmission scheme can be performed for multiple rounds until the UE finally successfully receives the transport block. For URLLC applications, the network and the UE do not always have the opportunity to perform multiple rounds of information exchange between them. Therefore, in various embodiments, the techniques discussed in this article can be used to provide enhanced HARQ feedback.

[0087] The second problem is that with existing CSI feedback, based on measurements of the desired channel (from CMR (Channel Measurement Resources)) and interference (from ZP IMR (Zero Power Interference Measurement Resources), also referred to as CSI-IM in the NR specification) as well as potential structured interference from NZPIMR (Non-Zero Power Interference Measurement Resources), the UE generates feedback including full or partial CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), and RI (Rank Indicator) for a hypothetical transmission with a target block error rate (BER) on a reference resource. However, this CSI feedback is based on a reference resource that has no relationship to the ongoing URLLC transmission itself and is feedback from which the gNB cannot easily infer actionable information. Therefore, various implementations may employ the techniques discussed herein to enhance CSI feedback.

[0088] Enhanced HARQ feedback

[0089] Figures 5 to 7 Various existing transmission scenarios and accompanying HARQ feedback in Rel-15 and / or Rel-16 are shown. Figure 5 , shows a first exemplary transmission scenario 500 incorporating various aspects discussed herein, the first exemplary transmission scenario involving a single transmission of a PDSCH 530. The PDSCH 530 may be scheduled by a PDCCH 510 and transmitted along with an accompanying PDSCH DMRS (demodulation reference signal) 520, in response to which the UE may transmit HARQ feedback 540 (e.g., indicating ACK or NACK (negative ACK)) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) as appropriate. Reference Figure 6, shows a second exemplary transmission scenario 600 incorporating various aspects discussed herein, the second exemplary transmission scenario involving multiple transmissions of PDSCH 6301 and 6302 from one redundancy version (RV) sequence. The PDSCH 6301 and 6302 may be scheduled by the PDCCH 610 and transmitted along with accompanying PDSCH DMRS (demodulation reference signals) 6201 and 6202 from multiple transmission / reception points (TRPs) (TRP1 and TRP2), in response to which the UE may transmit HARQ feedback 640 (e.g., indicating ACK or NACK) via the PUCCH or PUSCH as appropriate. Reference Figure 7 , a third exemplary transmission scenario 700 is shown in conjunction with various aspects discussed herein, the third exemplary transmission scenario involving multiple transmissions of PDSCH 7301 and 7302 from one RV sequence with slot aggregation. PDSCH 7301 and 7302 (e.g., with slot aggregation) may be scheduled by PDCCH 710 and transmitted in multiple slots (slot n and slot n+1) along with accompanying PDSCH DMRS (demodulation reference signals) 7201 and 7202, in response to which the UE may transmit HARQ feedback 740 (e.g., indicating ACK or NACK) via PUCCH or PUSCH as appropriate.

[0090] The retransmission in the existing transmission scenario (eg, 500, 600, or 700) may be in response to HARQ ACK / NACK, and may be performed based at least on a dynamic grant of the PDSCH. Figure 8 , a diagram illustrating two different retransmission scenarios 8001 and 8002 based on existing HARQ ACK feedback is shown in conjunction with various aspects discussed herein. In the first scenario 8001, a dynamic grant schedules PDSCH for an initial transmission 8101, which may be, for example, according to any of the transmission scenarios 500, 600, or 700. Based on the initial transmission 8101, the UE may transmit HARQ feedback 8201 indicating ACK / NACK, in response to which the BS (e.g., gNB, etc.) may schedule retransmissions of the PDSCH based on the dynamic grant at 8301. The second scenario 8002 is similar to the first scenario 8001, but the initial transmission 8102 may be based on semi-persistent scheduling (SPS).

[0091] In existing hybrid ARQ schemes, since the latency requirements / targets may be more relaxed than URLLC (e.g., for eMBB (enhanced mobile broadband)), the network and UE may use minimalistic feedback information (HARQ feedback consisting of a single feedback bit) for each round of feedback, and may do so over multiple rounds to explore and ultimately find the number of retransmissions that are successfully decoded.

[0092] In URLLC, in many cases, due to stringent latency requirements / targets, the second transmission is the only opportunity for the gNB to provide more coded bits to the UE so they can be combined with previously received coded bits (LLRs) for successful decoding. Therefore, if the UE does not successfully decode the PDSCH for the first transmission or retransmission when the latency bound is in danger of being exceeded, more relevant information for the UE to provide is not just the fact that the UE failed to decode the transport block, but how much redundancy from the gNB can allow the UE to decode the transport block in the next attempt. Therefore, in various embodiments (e.g., for URLLC, etc.), a first set of techniques may be employed in which the UE may provide an indication of how much redundancy can allow the UE to decode the transport block as feedback (e.g., HARQ, etc.) associated with a PDSCH transport block (TB).

[0093] In various aspects, information related to the number of additional coded bits that allow a UE to decode a PDSCH using current transmission parameters is referred to herein as a "redundancy gap." Additionally, in some aspects (e.g., in conjunction with CSI-related implementations), a "redundancy gap" may also be defined for conventional CSI measurement resources, as explained in more detail below.

[0094] The quality of the soft bits at the UE (e.g., based on LLR, etc.) may be affected by many factors, including: (1) previously transmitted RV; (2) missed physical downlink control channel (PDCCH) reception; (3) interference from other cells; or (4) aged CSI (which may lead to suboptimal MCS selection).

[0095] Assuming that the same MCS level and / or precoding of the gNB is used as a reference for future transmissions expected by the UE, in various embodiments, the redundancy gap may be quantified as the number of repetitions (e.g., possibly with different RVs) that allow the UE to successfully decode the coded transport block.

[0096] Although some specific examples and implementations discuss URLLC, the techniques discussed herein may be employed in conjunction with various communications (including but not limited to URLLC). Various implementations may employ one or more of the several techniques discussed herein for UE feedback prior to retransmission.

[0097] In various implementations according to the first set of techniques, in response to receiving a PDSCH, a UE (eg, using system 400 UEThe UE may generate feedback of quantized redundant gaps, as described herein. Based on at least the DMRS and / or PDSCH LLR and / or PDSCH SINR received for the current PDSCH, the UE may determine the redundant gaps (e.g., based on the reception quality of the transmitted RV), and may quantize the redundant gaps for successful decoding, as described herein. In various embodiments, the UE may indicate (e.g., via HARQ) the starting RV, the length of the RV sequence, and the UE may do one of the following: assume the configured RV sequence; or indicate a preferred RV sequence (e.g., [0 3 0 3] (repeat) versus [02 3 1] (repeat), etc.).

[0098] In a first set of implementations, for a given RV (e.g., "0"), the UE may suggest a number of repetitions (e.g., 1, 2, 3, 4, etc.) that would allow successful decoding. For example, if there are 2 repetitions, then the BS (e.g., gNB, etc.) may be suggested to retransmit the PDSCH using 2 transmissions of a given RV (e.g., "0"). In some such implementations, the UE may represent the suggested RV sequence as [0] for one repetition, [0, 0] for 2 repetitions, [0, 0, 0] for 3 repetitions, etc. The suggested HARQ RV may be used for reference transmission.

[0099] In a first set of embodiments, the reference transmission may be: (1) the current transmission of the PDSCH (if PDSCH slot aggregation or mTRP (multiple transmission reception point) scheme 3 or scheme 4 is used, one option is to use only one PDSCH (e.g., counted from TRP1 or TRP2; counted from slot n or slot n+1) as the reference transmission, or another option is to use all PDSCHs from PDSCH slot aggregation or mTRP scheme 3, mTRP scheme 4); or (2) the first transmission of a transport block; or (3) a PRB (physical resource block) in a full BWP (bandwidth part) on multiple OFDM (orthogonal frequency division multiplexing) symbols, which may be configured / indicated to the UE or determined by a table lookup of the PRB allocation and time domain allocation of the current transmission.

[0100] In a second set of implementations, the UE may suggest an RV sequence to the BS (e.g., gNB), such as [3], [0 3], [0 3 03], [0 3 3], etc. In order to reduce the assumptions for UE testing and to reduce signaling overhead, the allowed RVs may be limited to a subset of {0, 1, 2, 3}, such as {0, 3}.

[0101] refer to Fig. 9, shows a first exemplary retransmission scenario 900 according to various embodiments discussed herein, which involves a single initial transmission of a PDSCH 9301 and HARQ feedback 940 indicating a suggested RV sequence. The initial PDSCH 9301 (RV0 in exemplary scenario 900) may be scheduled by PDCCH 9101 and transmitted with an accompanying PDSCH DMRS (demodulation reference signal) 9201, in response to which the UE may transmit HARQ feedback 940 indicating a suggested RV sequence via PUCCH or PUSCH as appropriate according to the techniques described herein. In exemplary scenario 900, the suggested RV sequence may include RV0 and RV3, which may be indicated via any of the techniques discussed herein (e.g., as RV sequence [0 3], as a starting RV [0] and length 2 based on a configured or indicated (e.g., via HARQ feedback 940) RV sequence (e.g., [0 3 0 3], etc.). In response to the HARQ feedback 940, the BS (e.g., a gNB, etc.) may schedule via the PDCCH 9102 a PDSCH retransmission including an RV (e.g., PDSCH 9302 of RV0 and PDSCH 9303 of RV3) that may be selected based at least on the HARQ feedback 940, and may transmit the PDSCHs 9302 and 9303 and the accompanying PDSCH DMRSs 9202 and 9203.

[0102] In the first or second group of embodiments (e.g., Fig. 9 As shown), the UE may indicate (for redundancy gaps, e.g., in HARQ) a specific sequence of RVs to be transmitted by the BS (e.g., gNB, etc.) by explicitly indicating each RV of the requested sequence, such as Fig. 9 As shown in the following examples: (0) the UE may indicate the RV sequence [0 3], in response to which the BS may transmit RV 0 and RV 3 (as shown at 9302 and 9303); (1) the UE may indicate the RV sequence [0 0 0 0], in response to which the BS may transmit RV 0 four times; (2) the UE may indicate the RV sequence [0 1], in response to which the BS may transmit RV 0 and RV 1 (as shown at Fig. 9 (3) the UE may indicate an RV sequence of [0], in response to which the BS may transmit RV 0; or (4) the UE may indicate an RV sequence of [0 3 0 3], in response to which the BS may transmit RV 0, RV 3, RV 0, and RV 3. Other exemplary scenarios are also possible.

[0103] In a third set of implementations, a basic RV sequence may be pre-agreed between a BS (e.g., a gNB) and a UE (e.g., configured to the UE, etc.), wherein the UE-recommended RV sequence is read out on the basic RV sequence based on an indicated length and optionally an indicated starting position. If the last element of the basic RV sequence is reached before the indicated length is met, wrapping may be used. For example, assuming that the basic RV sequence is [0 2 3 1], the UE may suggest a starting position of "3" and a length of 3 (e.g., 3 RVs), which is equivalent to explicitly indicating [3 1 0] to the BS (e.g., gNB) (as shown in the second set of implementations). In various implementations, any one of a plurality of basic RV sequences may be employed (e.g., [0 2 3 1], [0 3 0 3], etc.).

[0104] In order to establish a basic RV sequence between a BS (e.g., a gNB) and a UE, in some embodiments, a basic RV sequence may be predefined (e.g., in a 3GPP specification, such as [0 2 3 1], etc.), while in other embodiments, the basic RV sequence may be signaled to the UE by the BS (e.g., a gNB) through RRC (Radio Resource Control) signaling as a single basic RV sequence or a basic RV sequence selected from a plurality of basic RV sequences. In a scenario where a plurality of basic RV sequences are signaled to the UE through RRC signaling, a MAC CE from the gNB may be used to inform the UE which sequence is selected. When the basic RV sequence is established, the UE may indicate the RV sequence length and optionally the starting version of the RV sequence without specifying the RV sequence. Assuming that the basic RV sequence is [0 2 3 1] (with wrapping repetition if necessary), according to the third group of implementation schemes, the following are examples of RV sequences that can be indicated via signaling: (a) [0 2], by indicating a starting version "0" and a length of 2; (b) [0 2 3 1], by indicating a starting version "0" and a length of 4; (c) [2 3 1], by indicating a starting version "2" and a length of 3; and (d) [3], by indicating a starting version "3" and a length of 1.

[0105] Providing the UE with the ability to indicate a starting RV may provide advantages, as can be clearly seen in the following exemplary scenarios. In the first exemplary scenario, the first transmission is made with RV "0", the UE receives a PDSCH with benign channel / interference conditions, and the UE assesses that slightly more redundant information from the gNB will allow it to successfully decode the transport block, so that in this case, the UE may indicate "1" for retransmission (e.g., for reduced code rate). In the second exemplary scenario, the first transmission is made with RV "0", the UE receives a PDSCH with severe interference and / or channel fading, making the soft bits of the systematic bits of the code block unreliable, and the UE may then request that the retransmission start with RV "0" to ensure that the systematic bits are retransmitted. As shown in the first and second exemplary scenarios, depending on the scenario, different starting versions of the recommended RV sequence may be more beneficial to the UE, depending on the current state of its soft bits.

[0106] In a fourth set of implementations, the UE may suggest a starting position for the retransmission via HARQ RV, as well as a suggested number of coded bits. The coded bits may be measured relative to the number of coded bits in a reference transmission.

[0107] The reference transmission can be: (1) the current transmission of PDSCH (if PDSCH time slot aggregation or mTRP (multiple transmission reception point) scheme 3 or scheme 4 is used, one option is to use only one PDSCH (for example, counted from TRP1 or TRP2; counted from time slot n or time slot n+1) as the reference transmission, or another option is to use all PDSCHs from PDSCH time slot aggregation or mTRP scheme 3, mTRP scheme 4); or (2) the first transmission of the transport block; or (3) a PRB (physical resource block) in the full BWP (bandwidth part) on multiple OFDM (orthogonal frequency division multiplexing) symbols, which can be configured / indicated to the UE or determined by a table lookup of the PRB allocation and time domain allocation of the current transmission.

[0108] The suggested number of coded bits may be an integer multiple or quantized multiple (eg, 2.5, 3, 3.5 or 2.75, 3, 3.25) of the number of coded bits in the reference transmission.

[0109] refer to Fig.10, shows a second exemplary retransmission scenario 1000 according to various embodiments discussed herein, which involves initial transmission of multiple PDSCHs 10301 and 10302 (e.g., two RVs of an RV sequence) and HARQ feedback 1040 indicating a recommended RV sequence. The initial PDSCHs 10301 (RV0 in the exemplary scenario 1000) and 10302 (RV3 in the exemplary scenario 1000) may be scheduled by the PDCCH 10101 and transmitted with accompanying PDSCH DMRS 10201 and 10202, respectively, in response to which the UE may transmit HARQ feedback 1040 indicating a recommended RV sequence via a PUCCH or PUSCH according to the techniques described herein, as appropriate. In the exemplary scenario 1000, the recommended RV sequences may include RV0 and RV3, which may be indicated via any of the techniques discussed herein (e.g., as an RV sequence [0 3], as a starting RV [0] and a length 2 based on a configured or indicated (e.g., via HARQ feedback 940) RV sequence (e.g., [0 3 0 3], etc.). In response to the HARQ feedback 1040, the BS (e.g., a gNB, etc.) may schedule a PDSCH retransmission including a RV (e.g., PDSCH 10303 of RV0) that may be selected based at least on the HARQ feedback 1040 via PDCCH 10102, and may transmit the PDSCH 10303 and an accompanying PDSCH DMRS 10203.

[0110] In the third or fourth group of embodiments (e.g., Fig.10 ), the UE may indicate (for redundancy gaps, e.g., in HARQ) the length of an RV sequence (e.g., as the number of RVs or the number of coded bits as a multiple of a reference transmission) and a starting RV, where the RV sequence may be one of: a predefined RV sequence, a configured RV sequence (e.g., the BS (e.g., gNB, etc.) may configure

[0303] or

[0231] to the UE), or an indicated RV sequence (e.g., the UE may indicate

[0303] or

[0231] (or some other sequence) as the selected RV sequence to the BS (e.g., gNB) via one or more bits).

[0111] exist Fig.10 In the fourth group of implementation examples 5-8 are shown. For example 8, Fig.10As shown in the lower right corner, the UE can propose a starting position from RV "0" and can request 2 times the coded bits of the reference transmission. In response to the UE's request, if the reference transmission includes X PRBs on Y symbols, the BS (e.g., gNB) can retransmit to the UE using 2X PRBs on Y symbols of RV "0". Note that depending on the number of coded bits in the current PDSCH transmission, there may be gaps or overlaps between the coded bits of RV "0" and "1", such as Fig. 9 As shown in Example 2 in (shown as two bars with a gap between them); on the contrary, for the fourth group of embodiments, when a single RV is used as the starting position (shown as two bars side by side), gaps or overlaps between the coded bits of different RVs can be avoided. Fig.10 The following additional examples are also shown (assuming a reference transmission of X PRBs over Y symbols): (5) the UE may indicate that the RV sequence starts at RV[0] and has a length of 3 (e.g., 3 times the number of coded bits of the reference transmission), in response to which the BS (e.g., gNB) may retransmit to the UE on Y symbols of RV “0” using 3X PRBs; (6) the UE may indicate that the RV sequence starts at RV[0] and has a length of 1, in response to which the BS (e.g., gNB) may retransmit to the UE on Y symbols of RV “0” using X PRBs; and (7) the UE may indicate that the RV sequence starts at RV[2] and has a length of 3, in response to which the BS (e.g., gNB) may retransmit to the UE on Y symbols of RV “2” using 2X PRBs. Other exemplary scenarios are also possible.

[0112] In various implementations according to the first set of techniques (e.g., involving HARQ feedback), if the UE does not successfully and correctly receive a transport block (TB) in the original transmission, the UE may suggest a HARQ redundancy version (RV) sequence to the BS (e.g., gNB) in response to the initial transmission. In conjunction with the first set of techniques, if the UE correctly receives a given TB in the initial PDSCH transmission, the UE may feedback "ACK" as HARQ feedback in response to the initial PDSCH transmission. If the UE does not receive the TB correctly, the UE may feedback a HARQ RV sequence, which may include: (1) a sequence having an RV from {0, 1, 2, 3} or a subset thereof (e.g., {0, 3}, etc.) (as shown in the first or second group of implementation schemes); or (2) an RV sequence, which may be indicated as a length (optionally, a starting RV), which may be read out through a basic redundant version sequence (e.g., [0 2 3 1], [0 3 0 3], etc.), which may be predefined in the specification or configured RRC signaling / MAC CE (as shown in the third group of implementation schemes); or (3) an RV sequence including a starting position in a reference transmission and coded bits of an integer or quantization multiple (as shown in the fourth group of implementation schemes).

[0113] refer to Fig.11 , shows a flow chart of an exemplary method 1100 that can be employed at a UE according to various embodiments discussed herein, the exemplary method facilitating generating HARQ feedback to a PDSCH indicating a redundancy gap associated with the PDSCH. In other aspects, a machine-readable medium may store instructions associated with the method 1100 that, when executed, may cause a UE (e.g., employing the system 400 UE )Execute the actions of method 1100.

[0114] At 1110, an initial PDSCH transmission or retransmission of one or more RVs of a TB may be received.

[0115] At 1120, it may be determined whether the TB is correctly received or whether additional coded bits are needed to correctly receive the TB based on the initial PDSCH transmission or retransmission.

[0116] At 1130, in response to determining that the TB was not correctly received, HARQ feedback indicating a requested RV sequence for the TB (e.g., according to any of the techniques or implementations discussed herein) may be transmitted, which may be based on UE calculations of additional coded bits that may facilitate correct reception of the TB. Alternatively, in response to determining that the TB was correctly received, HARQ feedback indicating an ACK may be transmitted, and method 1100 may end.

[0117] At 1140, a PDSCH retransmission including the requested RV sequence for the TB may be received.

[0118] Additionally or alternatively, the method 1100 may include the following: UE Various embodiments and one or more other actions described by the first set of techniques.

[0119] The enhanced HARQ feedback scheme disclosed herein may be applied to situations where the UE fails initial transmission through network configuration. Another possibility that may also be considered is that the gNB may send an indication explicitly requesting enhanced feedback. In one example, a trigger field for enhanced HARQ feedback is included in a downlink DCI scheduling an initial transmission or a retransmission, and the trigger field may indicate "0" or "1", where "0" indicates that the gNB requests conventional HARQ feedback, where a single-bit feedback of a transport block is generated; where "1" indicates that the gNB requests enhanced HARQ feedback. As indicated by the trigger field, there may be different PUCCH resources / PUCCH resource sets associated with these two situations, so multi-bit feedback with the enhanced HARQ feedback scheme may be transmitted together with PUCCH resources with appropriate protection, rather than being compressed into the PUCCH resources to obtain a smaller payload (e.g., for single-bit feedback).

[0120] refer to Fig.12 , a flow chart of an exemplary method 1200 that can be employed at a BS (e.g., a gNB) according to various embodiments discussed herein to facilitate retransmission of a PDSCH based on HARQ feedback indicating a redundancy gap associated with the PDSCH. In other aspects, a machine-readable medium may store instructions associated with the method 1200 that, when executed, may cause a BS (e.g., employing the system 400 gNB 、System 400 eNB etc.) to execute the actions of method 1200.

[0121] At 1210, an initial PDSCH transmission or retransmission of one or more RVs of a TB may be transmitted to a UE.

[0122] At 1220, HARQ feedback indicating a requested RV sequence for the TB may be received (eg, in accordance with any of the techniques or implementations discussed herein). Alternatively, HARQ feedback indicating an ACK may be received, and method 1200 may end.

[0123] At 1230, a PDSCH retransmission including the requested RV sequence for the TB may be transmitted.

[0124] Additionally or alternatively, the method 1200 may include the following: gNB 、System 400 eNB Various embodiments of the present invention and one or more other actions described in the first group of techniques.

[0125] Enhanced CSI feedback

[0126] The second set of techniques facilitates enhanced CSI feedback, which may provide information about redundant gaps associated with PDSCH transmissions.

[0127] In various implementations employing the second set of techniques, the UE may generate CSI feedback indicating a number of additional coded bits that may allow the UE to correctly receive the transmission.

[0128] In some such embodiments, based on CSI measurement resources that may include NZP CSI-RS resources for channel measurement, NZP CSI-RS resources for interference measurement, ZP IMR (zero-power CSI resources for interference measurement), the UE may feedback RI (rank indication), PMI (precoding matrix indicator), and information related to the redundant gap instead of feeding back CQI, wherein the UE may quantize the redundant gap by indicating a requested RV sequence for successful decoding, which RV sequence may be indicated similarly to any technique discussed in conjunction with embodiments employing the first group of techniques (e.g., for HARQ feedback) or as discussed elsewhere herein.

[0129] For example, in some embodiments employing the second group of techniques, the UE may indicate the length of the starting RV and the requested RV sequence in the CSI feedback, where the UE may assume a configured RV sequence (e.g., a basic RV sequence, etc.), or may indicate a preferred RV sequence (e.g., [0 3 0 3] versus [0 23 1], etc.), as shown in the following examples: (1) the UE indicates an RV sequence [0]; (2) the UE indicates an RV sequence [3]; (3) the UE indicates an RV sequence [0 3 0]; (4) the UE indicates an RV sequence [0 3 0 3 0]; or (5) the UE indicates an RV sequence [3 1 0 2 3].

[0130] As another example, in other embodiments employing the second group of techniques, the UE may indicate the desired number of repetitions (K) and a starting RV of a predefined RV sequence, a configured RV sequence (e.g., the gNB configures

[0303] or

[0231] to the UE), or a UE-indicated RV sequence (e.g., the UE indicates to the gNB that

[0303] or

[0231] is preferred).

[0131] In various embodiments employing the second set of techniques, the UE may feed back the requested RV sequence to the BS (e.g., gNB) as part of the CSI report. For example, the UE may indicate an RV sequence including X RV at "0", where X is fed back by the UE via CSI. As another example, the UE may indicate an RV sequence by indicating a starting RV and length (e.g., a starting RV and length of a basic RV sequence) via CSI, e.g., starting at "2", and the sequence is given by [2 3]. The basic RV sequence may be predefined, configured, selected, and indicated by the UE (e.g., from a predefined RV sequence and / or a preconfigured potential RV sequence), etc. In embodiments where there is more than one potential basic RV sequence, the basic RV sequence is configured to the UE or selected by the UE, and the potential basic RV sequence may include predefined and / or previously configured RV sequences, such as [0 2 3 1], [0 3 0 3], [0 0 0 0], etc.

[0132] In some embodiments of the second set of techniques, as discussed above, the UE may feedback RI, PMI, and redundancy gaps, which are of immediate value to ongoing transmissions. Optionally, in various embodiments, the UE may also feedback CQI (e.g., wideband and / or subband), which may provide feedback that, while not valuable in retransmissions of TBs indicated by the redundancy gaps, may be valuable for other transmissions. Thus, in various such embodiments, the UE may generate a CSI indicating {RI, PMI, CQI, redundancy gap}.

[0133] In various implementations employing the second set of techniques, CSI feedback may be triggered by downlink DCI (downlink control information) or by uplink DCI.

[0134] If the feedback is triggered by downlink DCI, a CSI triggering status field may be added to the downlink DCI, so the downlink DCI may indicate both PDSCH and CSI measurement resources, and rate matching may be performed around the indicated CSI measurement source.

[0135] If the feedback is triggered by an uplink DCI, in order to create a link between the uplink DCI and a previous (e.g., reference) PDSCH transmission, various embodiments may adopt one of the following options. In the first option, the reference PDSCH transmission may be the latest PDSCH transmission before the triggering transmission (via PUSCH or PUCCH) of the uplink CSI feedback. In the second option, the reference PDSCH transmission may be the latest PDSCH that meets certain timing requirements, for example, at least the latest PDSCH transmission before the uplink DCI. In the third option, for URLLC, there may be PDSCHs for different traffic types, and priority indications and / or traffic type indications may be used to explicitly match the triggered feedback and reference PDSCH transmissions. In an example of the third option, in time slot n, PDSCH-1 is used for eMBB and PDSCH-2 is used for URLLC (e.g., where the traffic type / priority is implicitly or explicitly indicated), and if the uplink DCI triggers feedback according to the second set of techniques, the traffic type indication / priority indication may be attached to the uplink DCI itself or the transmission it indicates (e.g., if URLLC is indicated, PDSCH-2 is the reference PDSCH, not PDSCH-1).

[0136] In various implementations employing the second set of techniques, a BS (e.g., a gNB) may indicate to a UE the number of repetitions and the starting RV for PDSCH reception.

[0137] refer to Fig.13, shows a flow chart of an exemplary method 1300 that can be employed at a UE according to various embodiments discussed herein, the exemplary method facilitating generating CSI feedback based on a reference PDSCH indicating a redundancy gap associated with a PDSCH. In other aspects, a machine-readable medium may store instructions associated with the method 1300 that, when executed, may cause a UE (e.g., employing the system 400) to UE )Execute the actions of method 1300.

[0138] At 1310, it is assumed that a reference PDSCH transmission for one or more RVs of a TB is from a BS.

[0139] At 1320, a DCI (eg, uplink or downlink, as discussed herein) may be received that triggers a CSI report associated with a reference PDSCH (eg, via an explicit indication or an implicit association).

[0140] At 1330, a CSI report indicating the RI, one or more PMIs, a redundancy gap associated with a reference PDSCH (eg, via a requested RV sequence, etc.), and optionally one or more CQIs can be transmitted to the BS.

[0141] Additionally or alternatively, the method 1300 may include the following: UE Various embodiments and one or more other actions described by the second set of techniques.

[0142] refer to Fig.14 , a flow chart of an exemplary method 1400 that can be employed at a BS (e.g., a gNB) according to various embodiments discussed herein, the exemplary method facilitating receiving CSI feedback based on a reference PDSCH indicating a redundant gap associated with a PDSCH. In other aspects, a machine-readable medium may store instructions associated with the method 1400 that, when executed, may cause a BS (e.g., employing the system 400 gNB 、System 400 eNB etc.) to execute the actions of method 1400.

[0143] At 1410, a reference PDSCH transmission of one or more RVs of a TB may be transmitted to a UE.

[0144] At 1420, a DCI (eg, uplink or downlink, as discussed herein) may be transmitted to trigger a CSI report associated with a reference PDSCH (eg, via an explicit indication or an implicit association).

[0145] At 1430, a CSI report may be received from the UE, the CSI report indicating the RI, one or more PMIs, a redundancy gap associated with a reference PDSCH (eg, via a requested RV sequence, etc.), and optionally one or more CQIs.

[0146] Additionally or alternatively, the method 1400 may include the following: gNB 、System 400 eNB Various embodiments of the present invention and one or more other actions described in the third group of technologies.

[0147] Enhanced ACK / NACK

[0148] Various embodiments may employ a third set of techniques, wherein the UE may provide enhanced ACK / NACK feedback as described herein, based on which a receiving BS (e.g., a gNB) may determine an additional number of coded bits or an additional amount of redundancy, based on which the UE may successfully decode the transport block.

[0149] The UE receives the PDSCH with an initial spectral efficiency R (as given by the modulation and coding rate of the MCS).

[0150] In the existing ACK / NACK feedback, the UE will report the ACK / NACK of the PDSCH, and the network will retransmit until the PDSCH is confirmed (ACK). In the simplified model, ACK will be achieved when R≤(I+L(n)), where I is the instantaneous mutual information on the PDSCH region, and L(n) is the accumulated mutual information from the previous n retransmissions.

[0151] One problem with this approach is that if the initially transmitted R is far from the current channel conditions, existing methods may result in a large number of retransmissions until the gap is bridged.

[0152] Furthermore, if the initial transmission is lost or severely affected by strong interference, it may result in a large number of retransmissions, since the initial transmission carries a large number of systematic bits and takes longer to recover after being lost.

[0153] In various implementations of the third set of techniques in parallel with PDSCH decoding, the UE may extract the DMRS and may calculate I. Based at least on I, the UE may calculate D=K(I+L(n)–R), where K is a scaling factor, and where D indicates the amount of information sufficient for the UE to successfully complete TB reception. Enhanced ACK / NACK feedback (eAN) may be defined as eAN=D(1–AN), where AN={0,1} when the CRCs are {FAIL, PASS} respectively (thus, eAN is D when the CRC is FAIL, and eAN is 0 when the CRC is PASS). In various implementations of the third set of techniques, the UE may feed back eAN instead of ACK / NACK in HARQ feedback according to prior art.

[0154] Using eAN, the BS (e.g., gNB) can calculate the additional redundancy required for successful decoding, so the likelihood of an ACK after the second retransmission increases as eAN eliminates uncertainties caused by CSI aging or external factors that affect the reception of the initial transmission.

[0155] In addition, using eAN, the BS (e.g., gNB) can detect whether the received RVid is in better / worse condition and decide to retransmit the same (or different) RVid when appropriate. The UE can also discard a (re)transmission if the quality of the soft bits is too low to avoid corrupting the content in the HARQ.

[0156] In various implementations employing the third set of techniques, D = K(I + L(n) - R), where K is a scaling factor, may be carried as part of the CSI feedback. In various such implementations, D may be normalized by a reference spectral efficiency (e.g., R derived from one of the current MCS level or the initial MCS level), and a quantized version of D / R may be fed back to the network, e.g., Use 6 bits to indicate the gap (or upper limit (2 N × D / R), with N bits indicating the gap, for some other values ​​of N).

[0157] refer to Fig.15 , shows a flow chart of an exemplary method 1500 that can be employed at a UE according to various embodiments discussed herein, the exemplary method facilitating the generation of enhanced feedback based on a PDSCH, the enhanced feedback facilitating a BS to determine a redundancy gap associated with the PDSCH. In other aspects, a machine-readable medium may store instructions associated with the method 1500, which when executed may cause a UE (e.g., employing the system 400) to UE )Execute the actions of method 1500.

[0158] At 1510, a reference PDSCH transmission for one or more RVs of a TB may be received from a BS.

[0159] At 1520, the amount of information sufficient for the UE to successfully decode the TB may be calculated (eg, D = K(I + L(n) - R)).

[0160] At 1530, an amount of information sufficient for the UE to successfully decode the TB (eg, D = K(I + L(n) - R)) may be transmitted to the BS (eg, via HARQ feedback or CSI feedback).

[0161] Additionally or alternatively, the method 1500 may include the following: UE One or more other actions described in various embodiments and the third group of techniques.

[0162] refer to Fig.16 , a flow chart of an exemplary method 1600 that can be employed at a BS (e.g., a gNB) according to various embodiments discussed herein, the method facilitating the BS to determine a redundant gap associated with a PDSCH based on enhanced feedback associated with the PDSCH. In other aspects, a machine-readable medium may store instructions associated with the method 1600 that, when executed, may cause a BS (e.g., employing the system 400 gNB 、System 400 eNB etc.) to execute the actions of method 1600.

[0163] At 1610, a reference PDSCH transmission of one or more RVs of a TB may be transmitted to a UE.

[0164] At 1620, an amount of information sufficient for the UE to successfully decode the TB (eg, D = K(I + L(n) - R)) may be received (eg, via HARQ feedback or CSI feedback).

[0165] At 1630, one or more additional RVs may be determined and transmitted that may assist the UE in successfully decoding the TB.

[0166] Additionally or alternatively, the method 1600 may include the following: gNB 、System 400 eNB Various embodiments of the present invention and one or more other actions described in the third group of technologies.

[0167] Additional Embodiments

[0168] The examples herein may include subject matter, such as a method, components for performing actions or blocks of the method, and at least one machine-readable medium including executable instructions that, when executed by a machine (e.g., a processor with memory, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), cause the machine to perform actions of a method or apparatus or system for concurrent communication using multiple communication technologies according to the described embodiments and examples.

[0169] Embodiment 1 is a device configured to be employed in a user equipment (UE), the device comprising: one or more processors, the one or more processors being configured to: process an initial physical downlink shared channel (PDSCH) transmission, the initial PDSCH transmission comprising one or more redundant versions (RVs) of a transport block (TB); determine whether the TB is correctly received based at least on the initial PDSCH transmission or retransmission; and generate a hybrid automatic repeat request (HARQ) feedback in response to determining that the TB is not correctly received based on the initial PDSCH transmission or retransmission, the HARQ feedback indicating a requested RV sequence for the TB.

[0170] Embodiment 2 includes the subject matter of any variation of any one of Embodiment 1, wherein the one or more processors are further configured to process a PDSCH retransmission including the requested RV sequence for the TB.

[0171] Embodiment 3 includes the subject matter of any variation of any one of Embodiment 1, wherein the one or more processors are configured to select the requested RV sequence based at least on calculation of multiple additional coded bits to decode the TB based on a set of transmission parameters associated with the initial PDSCH transmission or retransmission.

[0172] Embodiment 4 includes the subject matter of any variation of any one of Embodiments 1 to 3, wherein the requested RV sequence is indicated based at least on an explicit indication of each RV of the requested RV sequence.

[0173] Embodiment 5 includes the subject matter of any variation of any one of Embodiment 4, wherein the one or more processors are further configured to select each RV of the requested RV sequence as one of RV 0, RV 1, RV 2, or RV 3.

[0174] Embodiment 6 includes the subject matter of any variation of any one of Embodiment 4, wherein the one or more processors are further configured to select each RV of the requested RV sequence as an element of a group of three or less of RV 0, RV 1, RV 2, or RV 3.

[0175] Embodiment 7 includes the subject matter of any variation of any of Embodiments 1 to 3, wherein the requested RV sequence is indicated based at least on an indication of a length of a base RV sequence.

[0176] Embodiment 8 includes the subject matter of any variation of any one of Embodiment 7, wherein the requested RV sequence is indicated based at least on an indication of a starting RV of a base RV sequence.

[0177] Embodiment 9 includes the subject matter of any variation of any one of embodiments 7 to 8, wherein the basic RV sequence is predefined.

[0178] Embodiment 10 includes the subject matter of any variation of any one of Embodiments 7 to 8, wherein the basic RV sequence is configured via one or more of radio resource control (RRC) signaling or medium access control (MAC) control elements (CEs).

[0179] Embodiment 11 includes the subject matter of any variation of any one of Embodiments 1 to 3, wherein the requested RV sequence is indicated based on at least an indication of a starting RV and an indication of a multiple of a number of coded bits of a reference transmission.

[0180] Embodiment 12 is a device configured to be employed in a base station (BS), the device comprising: one or more processors, the one or more processors configured to: generate an initial physical downlink shared channel (PDSCH) transmission, the initial PDSCH transmission comprising one or more redundant versions (RVs) of a transport block (TB); process hybrid automatic repeat request (HARQ) feedback, the HARQ feedback indicating a requested RV sequence for the TB; and generate a PDSCH retransmission, the PDSCH retransmission comprising a requested RV sequence for the TB.

[0181] Embodiment 13 includes the subject matter of any variation of any of Embodiment 12, wherein the requested RV sequence is indicated based at least on an explicit indication of each RV of the requested RV sequence.

[0182] Embodiment 14 includes the subject matter of any variation of any one of Embodiment 13, wherein the one or more processors are further configured to select each RV of the requested RV sequence as one of RV 0, RV 1, RV 2, or RV 3.

[0183] Embodiment 15 includes the subject matter of any variation of any one of Embodiment 13, wherein the one or more processors are further configured to select each RV of the requested RV sequence as an element of a group of three or less of RV 0, RV 1, RV 2, or RV 3.

[0184] Embodiment 16 includes the subject matter of any variation of any of Embodiment 12, wherein the requested RV sequence is indicated based at least on an indication of a length of a base RV sequence.

[0185] Embodiment 17 includes the subject matter of any variation of any of Embodiment 16, wherein the requested RV sequence is indicated based at least on an indication of a starting RV of a base RV sequence.

[0186] Embodiment 18 includes the subject matter of any variation of any one of Embodiments 16 to 17, wherein the basic RV sequence is predefined.

[0187] Embodiment 19 includes the subject matter of any variation of any one of Embodiments 16 to 17, wherein the one or more processors are further configured to configure the basic RV sequence via one or more of radio resource control (RRC) signaling or medium access control (MAC) control elements (CEs).

[0188] Embodiment 20 includes the subject matter of any variation of any one of Embodiment 12, wherein the requested RV sequence is indicated based on at least an indication of a starting RV and an indication of a multiple of a number of coded bits of a reference transmission.

[0189] Embodiment 21 is a device configured to be employed in a user equipment (UE), the device comprising: one or more processors, the one or more processors configured to: process a reference physical downlink shared channel (PDSCH) transmission, the reference PDSCH transmission comprising one or more redundant versions (RVs) of a transport block (TB); process downlink control information (DCI), the DCI triggering a channel state information (CSI) report associated with the reference PDSCH; and generate a CSI report indicating a rank indication (RI), at least one precoding matrix indicator (PMI), and a requested RV sequence for the TB.

[0190] Embodiment 22 includes the subject matter of any variation of any one of Embodiment 21, wherein the CSI report further indicates at least one channel quality indicator (CQI).

[0191] Embodiment 23 includes the subject matter of any variation of any one of Embodiments 21 to 22, wherein the DCI is a downlink DCI that indicates both the reference PDSCH and a set of CSI measurement resources.

[0192] Embodiment 24 includes the subject matter of any variation of any one of Embodiments 21 to 22, wherein the DCI is an uplink DCI, and wherein the reference PDSCH is the latest PDSCH before transmitting the CSI report.

[0193] Embodiment 25 includes the subject matter of any variation of any one of Embodiments 21 to 22, wherein the DCI is an uplink DCI, and wherein the reference PDSCH is the latest PDSCH preceding the DCI.

[0194] Embodiment 26 includes the subject matter of any variation of any one of Embodiments 21 to 22, wherein the DCI includes one or more of a priority indication or a traffic type indication indicating the reference PDSCH.

[0195] Embodiment 27 includes the subject matter of any variation of any one of Embodiments 21 to 26, wherein the requested RV sequence is indicated based at least on an explicit indication of each RV of the requested RV sequence.

[0196] Embodiment 28 includes the subject matter of any variation of any one of Embodiment 27, wherein the one or more processors are further configured to select each RV of the requested RV sequence as one of RV 0, RV 1, RV 2, or RV 3.

[0197] Embodiment 29 includes the subject matter of any variation of any one of Embodiment 27, wherein the one or more processors are further configured to select each RV of the requested RV sequence as an element of a group of three or less of RV 0, RV 1, RV 2, or RV 3.

[0198] Embodiment 30 includes the subject matter of any variation of any of Embodiments 21 to 26, wherein the requested RV sequence is indicated based at least on an indication of a length of a base RV sequence.

[0199] Embodiment 31 includes the subject matter of any variation of any one of Embodiment 30, wherein the requested RV sequence is indicated based at least on an indication of a starting RV of a base RV sequence.

[0200] Embodiment 32 includes the subject matter of any variation of any one of Embodiment 30, wherein the basic RV sequence is predefined.

[0201] Embodiment 33 includes the subject matter of any variation of any one of Embodiment 30, wherein the one or more processors are further configured to configure the basic RV sequence via one or more of radio resource control (RRC) signaling or medium access control (MAC) control elements (CEs).

[0202] Embodiment 34 includes the subject matter of any variation of any one of Embodiments 21 to 26, wherein the requested RV sequence is indicated based on at least an indication of a starting RV and an indication of a multiple of a number of coded bits of a reference transmission.

[0203] Embodiment 35 is a device configured to be employed in a next generation Node B (gNB), the device comprising: one or more processors, the one or more processors configured to: generate a reference physical downlink shared channel (PDSCH) transmission, the reference PDSCH transmission comprising one or more redundant versions (RVs) of a transport block (TB); generate downlink control information (DCI), the DCI triggering a channel state information (CSI) report associated with the reference PDSCH; and process a CSI report indicating a rank indication (RI), at least one precoding matrix indicator (PMI), and a requested RV sequence for the TB.

[0204] Embodiment 36 includes the subject matter of any variation of any one of Embodiment 35, wherein the CSI report further indicates at least one channel quality indicator (CQI).

[0205] Embodiment 37 includes the subject matter of any variation of any one of Embodiments 35 to 36, wherein the DCI is a downlink DCI that indicates both the reference PDSCH and a set of CSI measurement resources.

[0206] Embodiment 38 includes the subject matter of any variation of any one of Embodiments 35 to 36, wherein the DCI is an uplink DCI, and wherein the reference PDSCH is the latest PDSCH prior to transmission of the CSI report.

[0207] Embodiment 39 includes the subject matter of any variation of any one of Embodiments 35 to 36, wherein the DCI is an uplink DCI, and wherein the reference PDSCH is the latest PDSCH preceding the DCI.

[0208] Embodiment 40 includes the subject matter of any variation of any one of Embodiments 35 to 36, wherein the DCI includes one or more of a priority indication or a traffic type indication indicating the reference PDSCH.

[0209] Embodiment 41 includes the subject matter of any variation of any one of Embodiments 35 to 40, wherein the requested RV sequence is indicated based at least on an explicit indication of each RV of the requested RV sequence.

[0210] Embodiment 42 includes the subject matter of any variation of any one of Embodiment 41, wherein the one or more processors are further configured to select each RV of the requested RV sequence as one of RV 0, RV 1, RV 2, or RV 3.

[0211] Embodiment 43 includes the subject matter of any variation of any one of Embodiment 41, wherein the one or more processors are further configured to select each RV of the requested RV sequence as an element of a group of three or less of RV 0, RV 1, RV 2, or RV 3.

[0212] Embodiment 44 includes the subject matter of any variation of any of Embodiments 35 to 40, wherein the requested RV sequence is indicated based at least on an indication of a length of a base RV sequence.

[0213] Embodiment 45 includes the subject matter of any variation of any of Embodiment 44, wherein the requested RV sequence is indicated based at least on an indication of a starting RV of a base RV sequence.

[0214] Embodiment 46 includes the subject matter of any variation of any of Embodiment 44, wherein the basic RV sequence is predefined.

[0215] Embodiment 47 includes the subject matter of any variation of any one of Embodiment 44, wherein the one or more processors are further configured to configure the basic RV sequence via one or more of radio resource control (RRC) signaling or medium access control (MAC) control elements (CEs).

[0216] Embodiment 48 includes the subject matter of any variation of any one of Embodiments 35 to 40, wherein the requested RV sequence is indicated based on at least an indication of a starting RV and an indication of a multiple of a number of coded bits of a reference transmission.

[0217] Embodiment 49 is a device configured to be employed in a user equipment (UE), the device comprising: one or more processors configured to: process a reference physical downlink shared channel (PDSCH) transmission, the reference PDSCH transmission comprising one or more redundant versions (RVs) of a transport block (TB); calculate an amount of additional information sufficient to successfully decode the TB; and generate feedback indicating the amount of additional information sufficient to successfully decode the TB.

[0218] Embodiment 50 includes the subject matter of any variation of any one of Embodiment 49, wherein the feedback is hybrid automatic repeat request (HARQ) feedback.

[0219] Embodiment 51 includes the subject matter of any variation of any one of Embodiment 49, wherein the feedback is channel state information (CSI) feedback.

[0220] Embodiment 52 includes the subject matter of any variation of any one of Embodiments 49 to 51, wherein the feedback indicates the amount of additional information sufficient to successfully decode the TB as a quantized ratio of the amount of additional information sufficient to successfully decode the TB relative to a reference spectral efficiency.

[0221] Embodiment 53 is a device configured to be employed in a user equipment (UE), the device comprising: one or more processors, the one or more processors configured to: generate a reference physical downlink shared channel (PDSCH) transmission, the reference PDSCH transmission comprising one or more redundant versions (RVs) of a transport block (TB); receive feedback indicating an additional amount of information sufficient to successfully decode the TB; and generate one or more additional RVs for the TB based at least on the feedback.

[0222] Embodiment 54 includes the subject matter of any variation of any one of Embodiment 53, wherein the feedback is hybrid automatic repeat request (HARQ) feedback.

[0223] Embodiment 55 includes the subject matter of any variation of any one of Embodiment 53, wherein the feedback is channel state information (CSI) feedback.

[0224] Embodiment 56 includes the subject matter of any variation of any one of Embodiments 53 to 55, wherein the feedback indicates the amount of additional information sufficient to successfully decode the TB as a quantized ratio of the amount of additional information sufficient to successfully decode the TB relative to a reference spectral efficiency.

[0225] Embodiment 57 includes an apparatus comprising means for performing any of the described operations of embodiments 1-56.

[0226] Embodiment 58 includes a machine-readable medium storing instructions for execution by a processor to perform any of the described operations of Embodiments 1 to 56.

[0227] Embodiment 59 includes an apparatus comprising: a memory interface; and a processing circuit configured to: perform any of the described operations of embodiments 1 to 56.

[0228] The above description of the exemplary embodiments of the disclosed subject matter, including the contents described in the abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. Although specific embodiments and examples are described herein for illustrative purposes, various modifications can be considered within the scope of such embodiments and examples as can be appreciated by those skilled in the relevant art.

[0229] In this regard, although the subject matter disclosed in the present invention has been described in conjunction with various embodiments and corresponding drawings, it should be understood that other similar embodiments may be used or modifications and additions may be made to the described embodiments to perform the same, similar, alternative or alternative functions of the disclosed subject matter without departing from the described embodiments. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but should be interpreted according to the breadth and scope of the following claims.

[0230] In particular, with respect to the various functions performed by the above-described components or structures (assemblies, devices, circuits, systems, etc.), unless otherwise specified, the terms used to describe such components (including references to "members") are intended to correspond to any component or structure that performs the specified functions of the components (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structures that perform the functions in the exemplary implementations shown herein. In addition, while particular features have been disclosed with respect to only one of a plurality of implementations, for any given or particular application, such features may be combined with one or more other features of other implementations, which may be desirable and advantageous.

Claims

1. A baseband processor, the baseband processor comprising: One or more processors configured to: Processing an initial physical downlink shared channel (PDSCH) transmission or retransmission including one or more redundancy versions (RVs) of a transport block (TB); determining whether the TB is correctly received based at least on the initial PDSCH transmission or retransmission; and In response to determining that the TB is not correctly received based on the initial PDSCH transmission or retransmission, a hybrid automatic repeat request (HARQ) feedback is output for transmission, the HARQ feedback indicating a requested RV sequence for the TB, the requested RV sequence in the HARQ feedback including multiple RVs to be transmitted at different times within the requested RV sequence.

2. The baseband processor of claim 1, wherein the one or more processors are further configured to process a PDSCH retransmission including the requested RV sequence for the TB.

3. A baseband processor according to claim 1, wherein the one or more processors are configured to select the requested RV sequence based at least on calculation of a plurality of additional coded bits to decode the TB based on a set of transmission parameters associated with the initial PDSCH transmission or retransmission.

4. The baseband processor according to any one of claims 1 to 3, wherein the requested RV sequence is indicated based at least on an explicit indication of each RV of the requested RV sequence. 5 . The baseband processor of claim 4 , wherein the one or more processors are further configured to select each RV of the requested RV sequence as one of RV 0, RV 1, RV 2, or RV 3. 6 .

6. The baseband processor of claim 4, wherein the one or more processors are further configured to select each RV of the requested RV sequence as an element of a group of three or less of RV 0, RV 1, RV 2, or RV 3.

7. The baseband processor according to any one of claims 1 to 3, wherein the requested RV sequence is indicated based at least on an indication of a length of a basic RV sequence.

8. The baseband processor of claim 7, wherein the requested RV sequence is indicated based on at least an indication of a starting RV of a basic RV sequence.

9. The baseband processor of claim 7, wherein the basic RV sequence is predefined.

10. The baseband processor of claim 7, wherein the basic RV sequence is configured via one or more of radio resource control (RRC) signaling or a medium access control (MAC) control element (CE).

11. The baseband processor according to any one of claims 1 to 3, wherein the requested RV sequence is indicated based on at least an indication of a starting RV and an indication of a multiple of a number of coded bits of a reference transmission.

12. A base station (BS), the BS comprising: Memory interface; and one or more processors coupled to the memory interface and configured to: generating an initial physical downlink shared channel (PDSCH) transmission, the initial PDSCH transmission comprising one or more redundancy versions (RVs) of a transport block (TB); processing a hybrid automatic repeat request (HARQ) feedback indicating a requested RV sequence for the TB, the requested RV sequence in the HARQ feedback comprising a plurality of RVs to be transmitted at different times within the requested RV sequence; as well as A PDSCH retransmission is transmitted by a radio frequency (RF) circuit, the PDSCH retransmission including the requested RV sequence for the TB.

13. The BS of claim 12, wherein the requested RV sequence is indicated based on at least an indication of a starting RV and an indication of a multiple of a number of coded bits of a reference transmission.

14. A user equipment (UE), the UE comprising: Memory interface; and one or more processors coupled to the memory interface and configured to: Processing a reference physical downlink shared channel (PDSCH) transmission, the reference PDSCH transmission comprising one or more redundancy versions (RVs) of a transport block (TB); processing downlink control information (DCI) that triggers a channel state information (CSI) report associated with the reference PDSCH transmission; as well as A CSI report is transmitted by a radio frequency (RF) circuit, the CSI report indicating a rank indication (RI), at least one precoding matrix indicator (PMI), and a requested RV sequence for the TB, the requested RV sequence including multiple RVs to be transmitted at different times within the requested RV sequence.

15. The UE of claim 14, wherein the CSI report further indicates at least one channel quality indicator (CQI). 16 . The UE of claim 14 , wherein the DCI is a downlink DCI indicating both the reference PDSCH transmission and a set of CSI measurement resources.

17. The UE of claim 14, wherein the DCI is an uplink DCI, and wherein the reference PDSCH transmission is a latest PDSCH transmission prior to transmission of the CSI report.

18. The UE of claim 14, wherein the DCI is an uplink DCI, and wherein the reference PDSCH transmission is a latest PDSCH transmission preceding the DCI.

19. The UE of claim 14, wherein the DCI comprises one or more of a priority indication or a traffic type indication indicating the reference PDSCH transmission.

20. The UE according to any one of claims 14 to 19, wherein the requested RV sequence is indicated based at least on an explicit indication of each RV of the requested RV sequence.

Images