Method, apparatus and system for UCI resource configuration in sub-band full duplex (SBFD)
SBFD-based UCI resource configuration dynamically allocates frequency and time resources for UCI transmission, addressing the inflexibility of existing channel coding schemes and enhancing communication performance by reducing latency and complexity.
Patent Information
- Application Number
- PCT/CN2024/123647
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-07-12
- Filing Date
- 2024-10-09
- Publication Date
- 2026-01-15
AI Technical Summary
Existing channel coding schemes in wireless communication systems fail to adapt flexibly to changing channel conditions in a fine-grained manner, leading to suboptimal performance and high complexity in encoding and decoding, which affects device cost, battery life, and communication efficiency.
Implementing Sub-Band Full Duplex (SBFD) for uplink control information (UCI) resource configuration, allowing for dynamic frequency and time resource allocation through signaling, including frequency location indication, HARQ feedback, and PUCCH configuration to enhance UCI transmission.
This approach reduces latency and improves communication performance by enabling flexible resource allocation, optimizing channel adaptation, and reducing complexity in encoding and decoding processes.
Smart Images

Figure CN2024123647_15012026_PF_FP_ABST
Abstract
Description
METHOD, APPARATUS AND SYSTEM FOR UCI RESOURCE CONFIGURATION IN SUB-BAND FULL DUPLEX (SBFD)
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. Provisional Application Serial No. 63 / 670, 396 filed on July 12, 2024, the entire contents of which are hereby incorporated by reference in its entirety.TECHNICAL FIELD
[0003] The application relates generally to wireless communications, and more specifically to uplink control information (UCI) resource configuration.BACKGROUND
[0004] In wireless communication systems, the quality of a communication channel may be subject to constant fluctuations due to the effects of fading which can occur on both fast and slow scales. As a result, the design of channel coding is such that it can adapt to different channel states. To address varying channel conditions, Modulation Coding Scheme (MCS) adaptation is used. This method allows for real-time adjustments to the modulation order, code length and coding rate, thereby optimizing the communication performance in response to the changing channel states. However, the channel coding scheme may not flexibly adapt to changes in the code length and code rate in a fine-grained manner, while simultaneously achieving high error correction performance across all configurations.
[0005] Furthermore, the complexity of both encoding and decoding algorithms should be sufficiently low. In hardware, this complexity can be evaluated by measuring chip area and energy efficiency, which are closely tied to a device’s cost and battery life, although they are also related to algorithmic complexity.SUMMARY
[0006] One or more implementations of the present application provide communication methods and communication apparatuses. The techniques described in the application can improve the performance of uplink control information (UCI) resource configuration.
[0007] According to a first aspect, a method is provided. The method includes transmitting signaling indicating a frequency location of a resource for UCI transmission in one or more symbols. Each symbol of the one or more symbols includes a first frequency subband for uplink (UL) transmission and a second frequency subband for downlink (DL) transmission. The frequency location of the resource for the UCI transmission is in the first frequency subband.
[0008] With reference to the first aspect, in some implementations, the frequency location of the resource for the UCI transmission is indicated as a frequency offset.
[0009] With reference to the first aspect, in some implementations, transmitting the signaling includes transmitting the signaling using higher layer signaling.
[0010] With reference to the first aspect, in some implementations, transmitting the signaling includes transmitting the signaling using downlink control information (DCI) .
[0011] With reference to the first aspect, in some implementations, the DCI overwrites a previous resource configuration for the UCI indicated using previous higher layer signaling.
[0012] With reference to the first aspect, in some implementations, the signaling further indicates a resource for at least one of an initial Hybrid Automatic Repeat Request (HARQ) transmission, a time offset between the initial HARQ transmission and a respective HARQ feedback, or a periodicity of the respective HARQ feedback.
[0013] With reference to the first aspect, in some implementations, the signaling indicates resources for transmission of at least one of a Scheduling Request (SR) or a Channel State Information (CSI) in the one or more symbols.
[0014] With reference to the first aspect, in some implementations, the signaling includes a physical uplink control channel (PUCCH) configuration, the PUCCH configuration includes a mapping type for a starting symbol of the resource scheduled for the UCI, and the starting symbol is configured through higher layer signaling or DCI.
[0015] With reference to the first aspect, in some implementations, the mapping type is a first mapping type, and a location of the starting symbol with respect to a slot boundary is configured using higher layer signaling.
[0016] According to a second aspect, a method is provided. The method includes receiving signaling indicating a frequency location of a resource for UCI transmission in one or more symbols. Each symbol of the one or more symbols includes a first frequency subband for uplink UL transmission and a second frequency subband for DL transmission. The frequency location of the resource for the UCI transmission is in the first frequency subband.
[0017] With reference to the second aspect, in some implementations, the frequency location of the resource for the UCI transmission is indicated as a frequency offset.
[0018] With reference to the second aspect, in some implementations, receiving the signaling includes receiving the signaling using higher layer signaling.
[0019] With reference to the second aspect, in some implementations, receiving the signaling includes receiving the signaling using DCI.
[0020] With reference to the second aspect, in some implementations, the DCI overwrites a previous resource configuration for the UCI indicated using previous higher layer signaling.
[0021] With reference to the second aspect, in some implementations, the signaling further indicates a resource for at least one of an initial HARQ transmission, a time offset between the initial HARQ transmission and a respective HARQ feedback, or a periodicity of the respective HARQ feedback.
[0022] With reference to the second aspect, in some implementations, the signaling indicates resources for transmission of at least one of a SR or CSI in the one or more symbols.
[0023] With reference to the second aspect, in some implementations, the signaling includes a PUCCH configuration, the PUCCH configuration includes a mapping type for a starting symbol of the resource scheduled for the UCI, and the starting symbol is configured through higher layer signaling or DCI.
[0024] With reference to the second aspect, in some implementations, the mapping type is a first mapping type, and a location of the starting symbol with respect to a slot boundary is configured using higher layer signaling.
[0025] With reference to the second aspect, in some implementations, the method further includes receiving a PDSCH scheduling that conflicts with UCI in the time domain.
[0026] With reference to the second aspect, in some implementations, the method includes skipping the UCI. The UCI includes a negative acknowledgement (NACK) .
[0027] With reference to the second aspect, in some implementations, the method includes transmitting the UCI and skipping DL reception. The UCI includes an acknowledgement (ACK) .
[0028] According to a third aspect, a communication apparatus is provided. The communication apparatus is configured to perform the method according to the first aspect or one or more implementations of the first aspect, or the second aspect or one or more implementations of the second aspect.
[0029] With reference to the third aspect, in some implementations, the communication apparatus includes a transmitting unit configured to transmit signaling indicating a frequency location of a resource for UCI transmission in one or more symbols. Each symbol of the one or more symbols includes a first frequency subband for UL transmission and a second frequency subband for DL transmission. The frequency location of the resource for the UCI transmission is in the first frequency subband.
[0030] With reference to the third aspect, in some implementations, the communication apparatus includes a receiving unit configured to receive signaling indicating a frequency location of a resource for UCI transmission in one or more symbols. Each symbol of the one or more symbols includes a first frequency subband for UL transmission and a second frequency subband for DL transmission. The frequency location of the resource for the UCI transmission is in the first frequency subband.
[0031] With reference to the third aspect, in some implementations, the communication apparatus includes one or more processors, and an interface circuit configured to transmit signaling indicating a frequency location of a resource for UCI transmission in one or more symbols. Each symbol of the one or more symbols includes a first frequency subband for UL transmission and a second frequency subband for DL transmission. The frequency location of the resource for the UCI transmission is in the first frequency subband.
[0032] With reference to the third aspect, in some implementations, the communication apparatus includes one or more processors, and an interface circuit configured to receive signaling indicating a frequency location of a resource for UCI transmission in one or more symbols. Each symbol of the one or more symbols includes a first frequency subband for UL transmission and a second frequency subband for DL transmission. The frequency location of the resource for the UCI transmission is in the first frequency subband.
[0033] With reference to the third aspect, in some implementations, the interface circuit includes one or more transceivers.
[0034] According to a fourth aspect, an apparatus is provided. The apparatus includes one or more processors and one or more memories. The one or more memories store instructions which, when executed by the one or more processors, cause the apparatus to perform the method according to the first aspect or one or more implementations of the first aspect, or the second aspect or one or more implementations of the second aspect.
[0035] According to a fifth aspect, a communication system is provided. The communication system includes a first communication apparatus configured to perform the method according to the first aspect or one or more implementations of the first aspect. The communication system further includes a second communication apparatus configured to perform the method according to the second aspect or one or more implementations of the second aspect.
[0036] According to a sixth aspect, a non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage has instructions stored thereon which, when executed by an apparatus, cause the apparatus to perform the method according to the first aspect or one or more implementations of the first aspect, or the second aspect or one or more implementations of the second aspect.
[0037] According to a seventh aspect, a computer program product is provided. The computer program product stores instructions which, when executed, cause an apparatus to perform the method according to the first aspect or one or more implementations of the first aspect, or the second aspect or one or more implementations of the second aspect.BRIEF DESCRIPTION OF THE DRAWINGS
[0038] FIG. 1 illustrates a schematic illustration of an example communication system.
[0039] FIG. 2 illustrates another example communication system.
[0040] FIG. 3 illustrates an example of an apparatus wirelessly communicating with another apparatus in a communication system.
[0041] FIG. 4 illustrates an example apparatus.
[0042] FIG. 5 illustrates another example apparatus.
[0043] FIG. 6 illustrates an overview of a Real-Time Acknowledgement Amid Transmissions (RAAT) scheme.
[0044] FIG. 7 illustrates an example RAAT scheme involving a downlink data channel and an uplink control channel.
[0045] FIG. 8 is a diagram illustrating an example algorithm performed at a base station (BS) .
[0046] FIG. 9 is an example schematic diagram illustrating BS resource scheduling.
[0047] FIG. 10 illustrates an example of scheduling using a single downlink control information (DCI) .
[0048] FIG. 11 illustrates an example of scheduling using two DCI.
[0049] FIG. 12 illustrates an example scheme where multiple transmission occasions (TOs) are spaced apart in the time domain.
[0050] FIG. 13 is a diagram illustrating an example timing of multiple Hybrid Automatic Repeat Request (HARQ) feedback TOs.
[0051] FIG. 14 includes diagrams illustrating examples of subband full duplex (SBFD) configurations.
[0052] FIG. 15 illustrates an example of physical uplink control channel (PUCCH) configuration for SBFD.
[0053] FIG. 16 illustrates an example uplink control information (UCI) configuration for SBFD and non-SBFD symbols.
[0054] FIG. 17A illustrates an example of multiple periodic HARQ feedback TOs.
[0055] FIG. 17B illustrates an example of consecutive multiple HARQ feedback TOs.
[0056] FIG. 18 illustrates an example of physical downlink shared channel (PDSCH) resource and Transport Block Size (TBS) determination.
[0057] FIG. 19 illustrates an example of user equipment (UE) behavior with respect to downlink (DL) / uplink (UL) conflict.DETAILED DESCRIPTION
[0058] In the context of future generations of communication systems, various scenarios may be supported, including immersive communication, massive communication, and hyper-reliable low-latency communication. Key Performance Indicators (KPIs) related to channel coding include, but are not limited to, coding gain, reliability, throughput, latency, and their trade-offs. For instance, the throughput requirement for a future generation communication system standard may exceed 1 TeraBits Per Second (Tbps) , and energy efficiency may improve to 1 picojoules per bit (pJ / bit) . Additionally, the coding scheme may be required to support flexible rate matching and Incremental Redundancy-Hybrid Automatic Repeat reQuest (IR-HARQ) schemes and the design of the code ensemble may be required to meet the KPIs and capabilities. Current HARQ solutions adopt a stop-and-go structure. However, this approach incurs significant delays and relies heavily on accurate Channel Quality Indicator (CQI) estimation to be effective.
[0059] Implementations of the present disclosure include methods, apparatus and systems for uplink control information (UCI) resource configuration through Sub-Band Full Duplex (SBFD) , to obtain low latency HARQ feedback.
[0060] Aspects of the present disclosure include configuration of the SBFD, configuration and determination of time and frequency resources for sending HARQ feedback and user equipment (UE) behavior associated with the transmissions.
[0061] The details of one or more implementations of the subject matter of this present disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.
[0062] FIG. 1 is a schematic illustration of an example communication system according to an implementation of the present disclosure, there is shown a communication system 100 that includes a radio access network (RAN) 120, one or more communication electronic devices (EDs) 10a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (collectively referred to as 110) , a core network 130, a Public Switched Telephone Network (PSTN) 140, the Internet 150, and other networks 160 . The RAN 120 may include, but is not limited to, a future generation RAN, or a legacy RAN such as, but not limited to, 5th generation (5G) , 4th generation (4G) , 3rd generation (3G) or 2nd generation (2G) radio access network. The RAN 120 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) , a NextGen RAN (NG RAN) , or some other type of RAN. Examples of RAN 120 based on the evolution of telecommunications standards include, but is not limited to, GSM (Global System for Mobile Communications) and CDMA (Code Division Multiple Access) for 2G, UMTS (Universal Mobile Telecommunications System) based on WCDMA (Wideband Code Division Multiple Access) and CDMA2000 for 3G, LTE (Long-Term Evolution) and WiMAX (Worldwide Interoperability for Microwave Access) for 4G, and NR (New Radio) for 5G. In some implementations, The RAN 120 may use any radio access technology (RAT) in the wireless interface between the one or more EDs 110 and the RAN 120. In some implementations, the term “radio access” may refer to the future generation air interface standards which may include both terrestrial networks (TNs) and non-terrestrial networks (NTNs) . These networks will be described in greater detail below in conjunction with various implementations. The one or more communication EDs 110 (also referred to as “user equipment” ) are configured to connect (e.g., communicatively couple) with each other or to one or more network nodes 170a, 170b (collectively referred to as 170) in the RAN 120. The core network (CN) 130 is a part of the communication system 100 and consists of network nodes (e.g., 170a, 170b) which provide support for the network features and telecommunication services. In some implementations, the CN 130 may be dependent on the RAT used in the communication system 100. In other implementations, the CN 130 may be access-agnostic, i.e., the CN 130 may be independent of the RAT used in the communication system 100. There are different types of CN 130, for different 3GPP system generations. For example, the CN 130 is the Evolved Packet Core (EPC) in 4G, also known as the Evolved Packet System (EPS) . In another example, the CN 130 is the 5G Core (5GC) which was developed as part of the 5G System (5GS) . The CN 130 also enables integration of different 3GPP and non-3GPP access types. In some implementations and referring to FIG. 1, the CN 130 also provides the interface towards external networks that may include the PSTN 140, the Internet 150, and other networks 160 in the communication system 100.
[0063] In general, the communication system 100 facilitates interaction between multiple wireless or wired elements. The communication system 100 may transmit different types of content, such as voice, data, video, and / or text, through different transmission methods such as, but not limited to, broadcast, multicast, groupcast, and unicast. Additionally, the communication system 100 operates by allocating and / or sharing resources, such as carrier spectrum bandwidth, among its constituent elements.
[0064] The communication system 100 may provide a wide range of communication services and applications including, but not limited to, Enhanced Mobile Broadband (eMBB) services, Ultra-Reliable Low-Latency Communication (URLLC) services, Massive Machine Type Communication (mMTC) services, Integrated Sensing And Communication (ISAC) , immersive communication, Ultra-massive Machine-Type Communication (uMTC) , hyper reliable and low-latency communication, ubiquitous connectivity, integrated AI and communication, and other services that can be provided by a future generation communication system. The communication system 100 may provide other services and applications such as, but not limited to, earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility and the like.
[0065] The communication system 100 may include a terrestrial communication system (or network) and / or a non-terrestrial communication system (or network) . The communication system 100 may provide a high degree of availability and robustness through a joint operation of the terrestrial communication system and the non-terrestrial communication system. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can result in a heterogeneous network including multiple layers. The heterogeneous network may achieve better overall performance through efficient multi-link joint operation, more flexible functionality sharing, and faster physical layer link switching between terrestrial networks and non-terrestrial networks. The terrestrial communication system and the non-terrestrial communication system could be considered as sub-systems of the communication system 100.
[0066] FIG. 2 illustrates another example communication system 100 according to an implementation of the present disclosure, there is shown the communication system 100 includes EDs 110a, 110b, 110c, 110d (collectively referred to as ED 110) , RANs 120a, 120b, one or more CNs 130, a PSTN 140, the Internet 150, and other networks 160. Additionally, the communication system 100 may also include a non-terrestrial network (NTN) 120c. The RANs 120a and120b may include network nodes 170a and 170b respectively. Examples of network nodes 170a, 170b include base stations, which can be generally referred to as terrestrial network (TN) devices or terrestrial transmit and receive points (T-TRPs) 170a and 170b (collectively referred to as 170) . In this context, the terms "TRP" and "base station" are used interchangeably unless otherwise specified. For simplicity, this disclosure primarily refers to network nodes as base stations; however, unless explicitly stated otherwise, references to TRP are considered non-limiting and interchangeable. The T-TRPs 170a, 170b may be base stations mounted on a building or tower. In one implementation, the NTN 120c includes a RAN node such as a base station 172, which may be generally referred to as an NTN device, a non-terrestrial node, a non-terrestrial network device, a non-terrestrial base station, or a non-terrestrial transmit and receive point (NT-TRP) 172.
[0067] In some implementations, the NT-TRP 172 is not attached to the ground, for example, as in the case of an airborne base station. An airborne base station may be implemented using communication equipment supported or carried by a flying device. For example, a flying device may include, but is not limited to, an airborne platform (such as a blimp or an airship) , balloon, drone (such as quadcopter) , and other types of aerial vehicles. In some implementations, an airborne base station may be supported or carried by an unmanned aerial system (UAS) or an unmanned aerial vehicle (UAV) , such as a drone. An airborne base station may be a moveable or mobile base station that can be flexibly deployed in different locations to meet network demand. A satellite base station is another example of a non-terrestrial base station. A satellite base station may be implemented using communication equipment supported or carried by a satellite. A satellite base station may also be referred to as an orbiting base station. High altitude platforms are yet another example of non-terrestrial base stations, including international mobile telecommunication base stations.
[0068] As referred to herein, and unless specified otherwise, a “TRP” may also refer to a T-TRP or an NT-TRP, a “T-TRP” may also refer to a “TN TRP” , and an “NT-TRP” may also refer to an “NTN TRP” . The NTN 120c may be considered a RAN, sharing operational aspects with RANs 120a, 120b. The NTN 120c may include at least one NTN device and at least one corresponding terrestrial network device. The at least one NTN device may function as a transport layer device and the at least one corresponding terrestrial network device may function as a RAN node, communicating with the ED 110 via the NTN device. Additionally, there may be an NTN gateway on the ground (referred to as a terrestrial network device) that also functions as a transport layer device facilitating communication with both the NTN device and the RAN node. The RAN node may communicate with the ED 110 via the NTN device and the NTN gateway. In some implementations, the NTN gateway and the RAN node may be located within the same device.
[0069] A base station 170 (also referred to as a TRP as stated above) is a network element within a radio access network responsible for radio transmission and reception in one or more cells to or from the ED (such as a user equipment) . In different implementations, the base station 170 may also be known as a base transceiver station (BTS) , a radio base station, a network node, a network device, a device on the network side, a transmit / receive node, a Node B, an evolved NodeB (eNodeB or eNB) , a Home eNodeB, a next Generation NodeB (gNB) , a transmission point (TP) , a site controller, an access point (AP) , a wireless router, a relay station, a terrestrial node, a terrestrial network device, a terrestrial base station, a non-terrestrial node, a non-terrestrial network device, a non-terrestrial base station, and a positioning node, among other possibilities. The base station 170 may be a macro base station (BS) , a pico BS, a relay node, a donor node, or combinations thereof. When the base station 170 performs (or is configured to perform) a method described herein, it may be interpreted as the base station itself, one or more modules (or units) in the base station, a circuit or chip, or a combination thereof, performing the method. For example, the circuit or chip may include a modem chip, also referred to as a baseband chip, a system on chip (SoC) including a modem core, system in package (SIP) ) , and the like, and may be responsible for one or more communication functions within the base station.
[0070] The EDs 110a-110d and TRPs 170a-170b, 172 are examples of communication equipment configured to implement some or all of the operations and / or implementations described herein. The T-TRP 170a forms part of the RAN 120a, which may include other TRPs, and / or other devices. Also, the TRP 170b forms part of the RAN 120b, which may include other TRPs, and / or devices. Each TRP 170a, 170b may transmit and / or receive wireless signals within a particular geographic region or area, sometimes referred to as a “cell” or a “coverage area” . The TRPs 170a-170b may be responsible for allocating and / or configuring resources and transmission and / or reception in a set of cell (s) . A cell is a radio network object that can be uniquely identified by a cell identification that is broadcasted over a geographical region or area from base stations associated with the cell. A cell can work in either FDD or TDD mode. A cell may be further divided into cell sectors, and a base station 170a-170b may, for example, employ one or more transceivers to provide services to one or more sectors. Some implementations may include pico or femto cells if supported by the radio access technology. In some implementations, one or more transceivers could be used for each cell, such as with Multiple-Input Multiple-Output (MIMO) technology. The number of RANs 120a-120b shown is merely an example. Any number of RANs may be contemplated when designing the communication system 100.
[0071] A base station may be a single element, as shown in the figures, or multiple elements distributed throughout the corresponding RAN, or otherwise configured. In some implementations, a plurality of RAN nodes coordinates to assist the ED 110 in implementing radio access, and different RAN nodes separately implement and handle different functions of the base station. For example, the RAN node may be a central unit (CU) , a distributed unit (DU) , a CU-control plane (CP) , a CU-user plane (UP) , or a radio unit (RU) etc. The CU and the DU may be separately deployed, or included within the same element (i.e., a baseband unit (BBU) ) . The RU may be included in a radio frequency device or a radio frequency unit (i.e., a remote radio unit (RRU) , an active antenna unit (AAU) , or a remote radio head (RRH) ) . In different systems, the CU (or the CU-CP and the CU-UP) , the DU, or the RU may be known by different names, but their functions are understood by person skilled in the art. For example, in an open radio access network (ORAN) system, a CU may be referred to as an open CU (O-CU) , a DU may be referred to as an open DU (O-DU) , and a CU-CP may be referred to as an open CU-CP (O-CU-CP) . The CU-UP may also be referred to as an open CU-UP (O-CU-UP) , and the RU may also be referred to as an open RU (O-RU) . Any one of the CU (or the CU-CP, the CU-UP) , the DU, and the RU may be implemented using a software module, a hardware module, or a combination of a software module and a hardware module.
[0072] Furthermore, communication between different devices / apparatuses in various implementations of this disclosure may refer to direct communication (that is, without the need of forwarding by another device / apparatus) or may refer to communication (s) between different devices / apparatuses via another device / apparatus (that is, requiring forwarding by another device / apparatus) . Alternatively, such communication (s) may involve one functional unit inside a device / apparatus using another functional unit within the device / apparatus to communicate with another device / apparatus. In other words, phrases such as "sending (or transmitting) information to... (an ED or a base station) " in this disclosure may be understood as a destination endpoint of the information being an ED or a base station, including, sending / transmitting information directly or indirectly to an ED or a base station. Similarly, phrases like "receiving information from... (an ED or a base station) " may be understood as a source endpoint of the information being an ED or a base station, including directly or indirectly receiving information from an ED or a base station. Between the source endpoint that sends the information and the destination endpoint, necessary processing such as, but not limited to, format conversion, digital-to-analog conversion, amplification, and filtering may be performed on the information. However, the destination endpoint may understand valid information from the source endpoint. A similar understanding applies to other descriptions in this disclosure without reiterating details already described. In the present disclosure, the terms "send" and "transmit" may be used interchangeably in different implementations of this disclosure.
[0073] The ED 110 is used to connect people, objects, machines, and other entities. The ED 110 may be widely used in various scenarios including, but not limited to, cellular communications, device-to-device (D2D) , vehicle to everything (V2X) , peer-to-peer (P2P) , machine-to-machine (M2M) , MTC, internet of things (IoT) , virtual reality (VR) , augmented reality (AR) , mixed reality (MR) , metaverse, digital twin, industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, and autonomous delivery and mobility.
[0074] Each ED 110 represents any suitable end user device for wireless operation and may include such devices (or may be referred to as, but not limited to) a user equipment (UE) or a user device or a terminal device, a wireless transmit / receive unit (WTRU) , a mobile station, a fixed or mobile subscriber unit, a cellular telephone, a station (STA) , an MTC device, a personal digital assistant (PDA) , a smartphone, a laptop, a computer, a tablet, a wireless sensor, a consumer electronics device, a smart book, a vehicle, a car, a truck, a bus, a train, or an IoT device, wearable devices (such as a watch, a pair of glasses, head mounted equipment, etc. ) , an industrial device, or an apparatus (such as a module, modem, or chip) in the forgoing devices, among other possibilities. Future generation EDs 110 may be referred to by other terms. When an ED 110 performs (or is configured to perform) a method described herein, it may be interpreted as the ED itself, one or more modules (or units) in the ED, a circuit or chip, or a combination thereof, performing the method. For example, the circuit or chip may include a modem chip, also referred to as a baseband chip, a system on chip (SoC) including a modem core, or system in package (SIP) ) , and the like, and may be responsible for one or more communication functions in the ED.
[0075] Each ED 110 connected to TRPs 170a-170b, and / or TRPs 172 can be dynamically or semi-statically turned-on (i.e., established, activated, or enabled) , turned-off (i.e., released, deactivated, or disabled) and / or configured in response to one of more of: connection availability and connection necessity.
[0076] Any ED 110 may be alternatively or additionally configured to interface, access, or communicate with any of the TRPs 170a, 170b and 172, the Internet 150, the CN 130, the PSTN 140, the other networks 160, or any combination thereof. In some examples, the ED 110a may communicate an uplink (UL) and / or downlink (DL) transmission over a terrestrial air interface 190a with station-TRP 170a. In some examples, the EDs 110a, 110b, 110c, and 110d may also communicate directly with one another via one or more sidelink (SL) air interfaces 190b. In some examples, the EDs 110a, 110d may communicate using an UL and / or DL transmission over a non-terrestrial air interface 190c with NT-TRP 172.
[0077] An air interface (such as, for example, 190a, 190b, 190c) generally includes a number of components and associated parameters that collectively specify how a transmission is to be sent and / or received over a wireless communications link between two or more communicating devices such as EDs and base station (s) . For example, an air interface may include one or more components defining the waveform (s) , frame structure (s) , multiple access scheme (s) , protocol (s) , coding scheme (s) and / or modulation scheme (s) for conveying information (such as, data) over a wireless communications link. The air interfaces 190a and 190b may use similar communication technology, that may include any suitable radio access technology.
[0078] The non-terrestrial air interface 190c can enable communication between the EDs 110a, 110d and one or more NT-TRPs 172 via a wireless link or simply a link. For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs 110 and one or more NT-TRPs 172 for multicast transmission.
[0079] The TRPs 170a-170b, 172 may communicate with one another over one or more air interfaces 190e, 190f using wireless communication links (such as radio frequency (RF) , microwave, infrared (IR) , etc. ) or wired communication links. The air interfaces 190e, 190f may utilize any suitable radio access technology, and may be substantially similar to the air interfaces 190a, 190c over which the EDs 110a-110d communicate with one or more of the TRP 170a-170b, 172 or they may be substantially different. For example, the communication system 100 may implement one or more channel access methods, such as Time Division Multiple Access (TDMA) , Frequency Division Multiple Access (FDMA) , Code Division Multiple Access (CDMA) , Single Carrier Frequency Division Multiple Access (SC-FDMA) , Low Density Signature Multicarrier Code Division Multiple Access (LDS-MC-CDMA) , Non-Orthogonal Multiple Access (NOMA) , Pattern Division Multiple Access (PDMA) , Lattice Partition Multiple Access (LPMA) , Resource Spread Multiple Access (RSMA) , and Sparse Code Multiple Access (SCMA) .
[0080] The RANs 120a and 120b are in communication with the CN 130 to provide the EDs 110a 110b, and 110c with various services such as voice, data, multimedia, and other services. The RANs 120a and 120b and / or the CN 130 may be in direct or indirect communication with one or more other RANs (not shown) , which may or may not be directly served by the CN 130, and may employ different radio access technologies from RAN 120a and / or RAN 120b. The CN 130 may also serve as a gateway access between (i) the RANs 120a and 120b and / or the EDs 110a 110b, and 110c, and (ii) other networks (such as the PSTN 140, the Internet 150, and the other networks 160) . In addition, some or all of the EDs 110a 110b, and 110c may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies and / or protocols. For example, the EDs 110a 110b, and 110c communicate using different cellular communications protocols, such as, but not limited to, a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like. Instead of wireless communication (or in addition thereto) , the EDs 110a 110b, and 110c may communicate using wired communication channels to a service provider or switch (not shown) , and / or to the Internet 150. The PSTN 140 may include circuit switched telephone networks for providing plain old telephone service (POTS) . The Internet 150 may include a network of computers and subnets (intranets) or both, and incorporate protocols, such as internet protocol (IP) , transmission control protocol (TCP) , user datagram protocol (UDP) . EDs 110a 110b, and 110c may be multimode devices capable of operation according to multiple radio access technologies, and may incorporate one or multiple transceivers necessary to support such.
[0081] In addition, the communication system 100 may comprise a sensing agent (not shown) to manage the sensed data from ED 110 and / or any one of TRPs 170a, 170b, 172. In one implementation, the sensing agent may be part of any one of TRPs 170a, 170b, 172. In another implementation, the sensing agent is a separate node that can communicate with the CN 130 and / or the RAN 120 (such as any one of TRPs 170a, 170b, 172) .
[0082] FIG. 3 is a schematic illustration showing an apparatus 310 wirelessly communicating with another apparatus 320 within a communication system (e.g., the communication system 100) according to an implementation of the present disclosure. The apparatus 310 may be an electronic device (such as ED 110) . The apparatus 320 may be a network node (e.g., the network node 170) such as T-TRP 170 or an NT-TRP 172. Although only one apparatus 310, and one apparatus 320 are shown in the figure, the number of apparatus 310 and / or number of apparatus 320 can vary, potentially including one or more of each. For example, a single ED 110 may be served by a single T-TRP 170 (or a single NT-TRP 172) , or by multiple T-TRPs 170 (or multiple NT-TRPs 172) . Similarly, a single ED 110 may be served by one or more T-TRPs 170 and one or more NT-TRPs 172. Similarly, a single T-TRP 170 (or a single NT-TRP 172) may serve one or more EDs 110.
[0083] The apparatus 310 may include one or more processors 210. For clarity and to avoid overcrowding the illustration, only a single processor 210 is illustrated. The apparatus 310 may further include a transmitter 201 and a receiver 203 coupled to one or more antennas 204. For clarity, only a single antenna 204 is illustrated. One, some, or all of the antennas 204 may alternatively be panels. In some implementations, the transmitter 201 and the receiver 203 are separate from each other. In other implementations, the transmitter 201 and the receiver 203 may be integrated into a single unit, for example, as a transceiver. The transceiver is configured to modulate data or other content for transmission by the one or more antennas 204 or a network interface controller (NIC) . The transceiver may also be configured to demodulate data or other content received by the one or more antennas 204. A transceiver may include any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received through wireless or wired communication. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals. The apparatus 310 may include a memory 208. In some implementations, the apparatus 310 may include multiple memories 208. Only a single transmitter 201, receiver 203, processor 210, memory 208, and antenna 204 is illustrated for simplicity, but the apparatus 310 may include one or more other components. In some implementations of the present disclosure, the transceiver (or transmitter 201 and / or receiver 203) may be viewed as an interface circuit.
[0084] The memory 208 is configured to store instructions used to perform operations described herein. The memory 208 may also be configured to store data that is used, generated, or collected by the apparatus 310. For example, the memory 208 can store software instructions or modules configured to implement some or all of the functionalities and / or operations described herein and that which are executed by the one or more processors 210.
[0085] The apparatus 310 may further include one or more input / output devices (not shown) or interfaces. The input / output devices or interfaces facilitate interaction with a user or other devices in the network. Each input / output device or interface includes suitable components for facilitating transmission of information to a user and reception of information from a user, and for various network interface communications. Such components may include, but are not limited to, a speaker, microphone, keypad, keyboard, display, touch screen, and the like.
[0086] The processor 210 may be configured to perform (or control the apparatus 310 to perform) operations (or methods) described herein as being performed by the apparatus 310. For example, the processor 210 performs or controls the apparatus 310 to perform the operations of: a) receiving one or more transport blocks (TBs) , b) using a resource for decoding at least one of the received TBs, c) releasing the resource for decoding another of the received TBs, and / or d) receiving configuration information configuring a resource. Specifically, the operations may include tasks related to: preparing a transmission for UL transmission to the apparatus 320, processing DL transmissions received from the apparatus 320, and handling SL transmission to and from another apparatus 310. Processing operations related to preparing a transmission for UL transmission may include operations such as, but not limited to, encoding, modulating, transmit beamforming, and generating symbols for transmission. Processing operations related to processing DL transmissions may include operations such as, but not limited to, receive beamforming, demodulating and decoding received symbols. Processing operations related to processing SL transmissions may include operations such as, but not limited to, transmit / receive beamforming, modulating / demodulating and encoding / decoding symbols. Depending upon the implementation, a DL transmission may be received by the receiver 203, possibly using receive beamforming, and the processor 210 may extract signaling from the DL transmission (such as by detecting and / or decoding the signaling) . An example of signaling may be a reference signal transmitted by the apparatus 320. In some implementations, the processor 210 implements the transmit beamforming and / or the receive beamforming based on the indication of beam direction, such as beam angle information (BAI) , received from the apparatus 320. In some implementations, the processor 210 may be configured to perform operations relating to network access (such as initial access) and / or downlink synchronization, which includes operations for detecting a synchronization sequence, decoding and obtaining the system information, and the like. In some implementations, the processor 210 may perform channel estimation, such as using a reference signal received from the apparatus 320.
[0087] Although not illustrated, in some implementations, the processor 210 may either be a part of the transmitter 201 or a part of the receiver 203 or a part of both the transmitter 201 and the receiver 203. Although not illustrated, in some implementations, the memory 208 may be a part of the processor 210.
[0088] The processor 210, along with the processing components of the transmitter 201 and the receiver 203 may each be implemented by one or more processors that may the same or different. These processors are configured to execute instructions stored in a memory (such as in the memory 208) .
[0089] The apparatus 320 includes one or more processors 260 (only one processor 260 is illustrated) . The apparatus 320 may further include one or more transmitters 252 and one or more receivers 254 coupled to one or more antennas 256. Only a single antenna 256 is illustrated to avoid clutter in the illustration. One, some, or all of the antennas 256 may alternatively be panels. In some implementations, the transmitter 252 and the receiver 254 are separate from each other. In other implementations, the transmitter 252 and the receiver 254 may be integrated into a single unit such as, for example, as a transceiver. The apparatus 320 may further include a memory 258. In some implementations, the apparatus 320 may include multiple memories 258. The apparatus 320 may further include a scheduler 253. Only a single transmitter 252, receiver 254, processor 260, memory 258, antenna 256 and scheduler 253 are illustrated for simplicity, however the apparatus 320 may include one or more other components. In the present disclosure, in some implementations, the transceiver (or transmitter 252 and / or receiver254) may be viewed as an interface circuit.
[0090] In some implementations, various components of the apparatus 320 may be distributed. For example, some of the modules of the apparatus 320 may be located remotely from the equipment housing the antennas 256 for the apparatus 320 (and therefore also can be viewed as one or more nodes) . These modules, which can be considered as one or more nodes, may be coupled to the equipment that houses the antennas 256 over a communication link (not shown) , sometimes referred to as front haul, such as the Common Public Radio Interface (CPRI) . Therefore, in some implementations, the term apparatus 320 may also refer to network-side nodes that perform processing operations such as, but not limited to, determining the location of the apparatus 310, resource allocation (scheduling) , message generation, and encoding / decoding, and that which are not necessarily part of the equipment that houses the antennas 256 of the apparatus 320. The nodes may also be coupled to other apparatuses 320. In some implementations, the apparatus 320 may actually be a plurality of nodes that are operating together to serve the apparatus 310, such as through the use of coordinated multipoint transmissions, or through the use of ORAN system as described above in the disclosure.
[0091] The processor 260 is configured to perform operations including those related to: preparing a transmission for DL transmission to the apparatus 310, processing an UL transmission received from the apparatus 310, preparing a transmission for backhaul transmission to another apparatus 320, and processing a transmission received over backhaul from another apparatus 320. Processing operations related to preparing a transmission for DL or backhaul transmission may include operations such as, but not limited to, encoding, modulating, precoding (such as MIMO precoding) , transmit beamforming, and generating symbols for transmission. Processing operations related to processing received transmissions in the UL or over backhaul may include operations such as, but not limited to, receive beamforming, demodulating received symbols, and decoding received symbols. The processor 260 may also be configured to perform operations relating to network access (such as initial access) and / or DL synchronization, such as generating the content of synchronization signal blocks (SSBs) , generating the system information, and the like. In some implementations, the processor 260 is further configured to generate an indication of beam direction, such as BAI, which may be scheduled for transmission by the scheduler 253 which will be described below. In some implementations, the processor 260 implements the transmit beamforming and / or receive beamforming based on beam direction information (such as BAI) received from another apparatus 320. The processor 260 is configured to perform other network side processing operations described herein, such as, but not limited to, determining the location of the apparatus 310, determining where to deploy another apparatus 320, and the like. In some implementations, the processor 260 may generate signaling data, to configure one or more parameters of the apparatus 310 and / or one or more parameters of another apparatus 320. Any signaling data generated by the processor 260 is sent by the transmitter 252. In some implementations, the apparatus 320 implements physical layer processing. In some implementations, the apparatus 320 may perform higher layer functions such as those at the Medium Access Control (MAC) or Radio Link Control (RLC) layers in addition to physical layer processing. In the apparatus 320, the scheduler 253 may be coupled to the processor 260 or integrated within the processor 260. In some implementations, the scheduler 253 may be integrated within the apparatus 320 or may be operated separately from the apparatus 320. The scheduler 253 may schedule UL, DL, SL, and / or backhaul transmissions, including issuing scheduling grants and / or configuring scheduling-free (such as “configured grant” ) resources.
[0092] The apparatus 320 may further include a memory 258 that is configured to store instructions for performing the operations described herein. The memory 258 may also store data that is used, generated, or collected by the apparatus 320. For example, the memory 258 can store software instructions or modules configured to implement some or all of the functionalities and / or implementations described herein and that which are executed by the processor 260.
[0093] Although not illustrated, the processor 260 may be implemented as part of the transmitter 252 and / or a part of the receiver 254. Although not illustrated, in some implementations, the processor 260 may implement the scheduler 253 and the memory 258 may be implemented as part of the processor 260.
[0094] The processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may each be implemented by the same or different processors that are configured to execute instructions stored in a memory, such as in the memory 258.
[0095] The apparatus 320 and / or the apparatus 310 may include other components, not shown or described herein for the sake of clarity.
[0096] Note that the term “signaling” , as used herein, may alternatively be referred to as control signaling, control message, control information, or message for simplicity. Signaling between a base station (such as the TRP 170a. 170b, 172) and a UE or sensing device (such as ED 110) , or signaling between a different UE or sensing device (such as between ED 110a and ED 110b) may be carried in physical layer signaling (also called as dynamic signaling) , which is transmitted in a physical layer control channel. For DL, the physical layer signaling may be known as downlink control information (DCI) which is transmitted in a physical downlink control channel (PDCCH) . For UL, the physical layer signaling may be known as uplink control information (UCI) which is transmitted in a physical uplink control channel (PUCCH) . For SL, signaling between different UEs or sensing devices (such as between ED 110a and ED 110b) may be known as SL control information (SCI) which is transmitted in a physical sidelink control channel (PSCCH) . Signaling may be carried in a higher layer (such as higher than physical layer) signaling, which is transmitted in a physical layer data channel, such as in a physical downlink shared channel (PDSCH) for downlink signaling, in a physical uplink shared channel (PUSCH) for uplink signaling, and in a physical sidelink shared channel (PSSCH) for SL signaling. Higher layer signaling may also be called static signaling, or semi-static signaling. The higher layer signaling may include radio resource control (RRC) protocol signaling or media access control -control element (MAC-CE) signaling. Signaling may be included in a combination of physical layer signaling and higher layer signaling.
[0097] It should be noted that in the present disclosure, “information” , when different from “message” , may be carried within a single message, or may be carried in multiple separate messages.
[0098] FIG. 4 illustrates an example apparatus 410 according to an implementation of the present disclosure. The apparatus 410 may be a communication device or an apparatus implemented in a communication device such as the ED 110 or the TRPs 170a, 170b, 172. For example, the apparatus 410 implemented in an ED may be an integrated circuit, which in some instances may be referred to as a chip, a modem, a modem chip, a baseband chip, or a baseband processor. In some implementations, one or more integrated circuits can be packaged into a system-on-chip, a system-in-package, or a multi-chip module. The apparatus 410 can include one or more integrated circuits and other discrete components. In some implementations, the apparatus 410 may be a module within the ED 110, or within the apparatus 310. In some implementations, the apparatus 410 may be a module within one of the TRPs 170a, 170b, 172, or the apparatus 320.
[0099] In an example, the apparatus 410 may include one or more processors 411, and an interface circuit 412. The apparatus 410 may further include a memory 413. The one or more processors 411 are configured to process signals and execute one or more communication protocols. The memory 413 is configured to store at least a part of corresponding computer program instructions and / or data. In an example, the one or more processors 411 execute the computer program instructions stored in the memory 413 to implement related operations (for example, inputting, outputting, receiving, and transmitting) in the method embodiments disclosed herein. In some implementations, the memory 413 being configured to store the corresponding computer program instructions and / or data may mean that the memory 413 is configured to store all of the corresponding computer program instructions and / or data for execution by the one or more processors 411. In some implementations, the memory 413 being configured to store the corresponding computer program instructions and / or data may mean that the memory 413 is configured to store a part of the corresponding computer program instructions and / or data. For example, the part of the corresponding computer program instructions and / or data may include computer program instructions and / or data that need to be currently executed by the one or more processors 411. Thus, the memory 413 may store different parts of computer program instructions and / or data for a plurality of times for the one or more processors 411 to perform related operations in the method embodiments disclosed herein. As a communication interface, the interface circuit 412 is configured to implement communication with another component. For example, the interface circuit 412 may communicate a signal with another apparatus or system, such as a radio frequency processing apparatus or another processor. The signal may include or carry information intended as a payload, such as user data, control information, etc. The signal may also include or carry information useful to a receiver, but not necessarily as a payload, such as a pilot signal or reference signal. Communicating the signal may include transmitting the signal to another component or device. Communicating the signal may additionally or alternatively include receiving the signal from another component or device. Transmitting the signal may include outputting the signal to a component or device that is directly or indirectly coupled to the interface circuit 412. Receiving the signal may include inputting or obtaining the signal from a component or device that is directly or indirectly coupled to the interface circuit 412. Optionally, to reduce a load of the one or more processors, a baseband signal processing circuit 414 may be also disposed to implement processing of at least a part of baseband signals, including signal demodulation, modulation, encoding, decoding, or the like.
[0100] The apparatus 410 may be the processor 210 (or 260) within the apparatus 310 (or 320) , in some scenarios, or may be included within the processor 210 (or 260) within the apparatus 310 (or 320) in some scenarios. The apparatus 410 may be a baseband chip or may include a baseband chip. In some implementations, the apparatus 410 may be independently packaged into a chip. In some implementations, the apparatus 310 (or 320) includes different types of chips. The apparatus 410 may be packaged into a processor chip (for example, an SoC chip or a SIP chip) with the different types of chips. In some implementations, the apparatus 410 may be packaged into a chip with some or all of circuits of a radio frequency processing system that may further be included in the apparatus 310 (or 320) .
[0101] FIG. 5 illustrates example apparatus 510 according to an implementation of the present disclosure. The apparatus 510 may include corresponding modules or units configured to implement methods and / or implementations described herein. In some implementations, the apparatus 510 includes a processing unit 512 and a communication unit 513. Optionally, the apparatus 510 may further include a storage unit 511 configured to store apparatus program code (or instructions) and / or data.
[0102] The apparatus 510 may be an ED side apparatus, for example, an ED or a module in an ED, or a circuit or a chip responsible for a communication function in an ED. In some implementations, apparatus 510 may be the apparatus 310. The processing unit 512 may be the processor 210. The communication unit 513 may comprise a receiving unit and / or a transmitting unit. The receiving unit and / or the transmitting unit may be the transmitter 201 and / or the receiver 203 respectively. The storage unit 511 may be the memory 208.
[0103] The apparatus 510 may be a base station side apparatus, for example, a base station or a module in a base station, or a circuit or a chip responsible for a communication function in a base station. In some implementations, apparatus 510 may be apparatus 320. The processing unit 512 may be the processor 260 (the scheduler 253 may also be included) . The communication unit 513 may comprise a receiving unit and / or a transmitting unit. The receiving unit and / or the transmitting unit may be the transmitter 252 and / or the receiver 254 respectively. The storage unit 511 may be the memory 258.
[0104] In some implementations, when the apparatus 510 is an ED 110 or a module in an ED 110, a function of the apparatus 510 may be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system on chip (SoC) chip or a SIP chip that includes a modem core. A function of the communication unit 513 may be implemented by a transceiver circuit.
[0105] In some implementations, when the apparatus 510 is a circuit or a chip that is responsible for a communication function in an ED 110, such as a modem chip, a system on chip (SoC) chip or a SIP chip that includes a modem core -a function of the processing unit 512 may be implemented by a circuit system within the chip which includes one or more processors. A function of the communication unit 513 may be implemented by an interface circuit or a data transceiver circuit on the chip.
[0106] It may be understood that the units in the apparatus 510 may be logical or functional. Each function may correspond to one functional unit, or two or more functions may be integrated into a single functional unit. In actual implementation, all or some of the units may be integrated into a single physical entity, or may be distributed across different physical entities. In addition, the functional units may be implemented in the form of hardware, software, or a combination of hardware and software. Whether a function is implemented in the form of hardware or software depends on particular applications and design constraint conditions of the technical solutions. A person skilled in the art may use different methods to implement the described functions for specific applications, but it should not be considered that the implementation goes beyond the scope of this disclosure.
[0107] In an example, a functional unit in any one of the apparatuses may be configured as one or more integrated circuits for implementing the methods disclosed herein, for example, as one or more application-specific integrated circuits (application-specific integrated circuits, ASICs) , one or more central processing units (CPUs) , one or more microprocessors or microprocessor units (MPUs) , one or more microcontrollers or microcontroller units (MCUs) , one or more digital signal processors (DSPs) , one or more field programmable gate arrays (FPGAs) , or a combination of these.
[0108] In an example, the storage unit 511 may include a random-access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, and / or a register.
[0109] A processor may be referred to as a processor system, an application processor, a baseband processor, a processor circuit, or a processor core. The processor may include one or a combination of one or more central processing units (CPUs) , one or more digital signal processors (DSPs) , one or more microprocessors (microprocessor units, MPUs) , one or more microcontrollers (microcontroller units, MCUs) , one or more graphics processing units (GPUs) , one or more field programmable gate arrays (FPGAs) , one or more artificial intelligence processors (AI processors) , or one or more neural network processing units (NPUs) .
[0110] Memory or a storage unit may include one or more of the following storage media: a random access memory (RAM) , a static random access memory (static RAM, SRAM) , a dynamic random access memory (dynamic RAM, DRAM) , a phase-change memory (PCM) , a resistive random access memory (resistive RAM, ReRAM) , a magneto-resistive random access memory (magneto-resistive RAM, MRAM) , a ferroelectric random access memory (ferroelectric RAM, FRAM) , a cache, a register, a read-only memory (ROM) , a flash memory (flash memory) , an erasable programmable read-only memory (erasable programmable ROM, EPROM) , a hard disk, and the like. In an example, computer program instructions used to execute embodiments may be stored in a non-volatile memory, for example, at least a part of a memory or storage unit (for example, one or more of a ROM, a flash memory, an EPROM, or a hard disk) . When a terminal runs, a part or all of corresponding computer program instructions may be loaded to a memory that has a higher transmission speed with the processor, for example, at least a part of a memory or a storage unit (for example, one or more of a RAM, an SRAM, a DRAM, a PCM, a RERAM, an MRAM, a FRAM, a cache, or a register) , so that the processor executes the computer program instructions to perform the steps in the method embodiments disclosed herein.
[0111] In communication systems, channel coding is used to encode K source bits into N code bits to provide error correction capabilities against adverse channel conditions such as noise and interference. The code rate is defined as R=K / N. In practice, the code rate R is selected based on channel quality.
[0112] Polar codes used in channel coding are capacity-achieving codes. As code length approaches infinity, the synthesized channels (or subchannels) become either noiseless or pure noise. The noiseless subchannels are utilized for the transmission of information, achieving the channel capacity defined by Shannon. This channel polarization phenomenon occurs under successive cancellation (SC) or SC-based decoding, which has a relatively low complexity.
[0113] Low-density parity-check (LDPC) codes, on the other hand, are capacity-approaching codes. The LDPC codes may be defined by a parity-check matrix, which has far more zeros than ones, thus attributing to low density. The positions of ones in the matrix may be effectively designed, to improve the decoding performance. Although LDPC codes can be viewed as a type of random code, hardware implementations are possible such as an encoder and a decoder, by introducing structures. Quasi-cyclic structures first define a smaller base matrix or base graph (BG) , and then perform “lifting” by replacing its ones with a cyclic shifted version of identity matrix.
[0114] Rate matching can be performed after channel encoding by either puncturing / shortening or repeating some code bits. The purpose of rate matching is to obtain a code bit sequence of desired length for transmission over limited channel resources.
[0115] A channel interleaver can be applied after channel encoding and rate matching for permuting the code bits, to achieve a stable and enhanced performance under high-order modulation or in a fading channel.
[0116] A frame structure is a feature of the wireless communication physical layer that defines the time domain signal transmission structure, to allow timing reference and timing alignment of basic time domain transmission units. Wireless communication between communicating devices may occur on time-frequency resources governed by such a frame structure. The frame structure may sometimes be referred to as a radio frame structure.
[0117] Depending on the frame structure and / or configuration of frames in the frame structure, frequency division duplex (FDD) and / or time division duplex (TDD) and / or full duplex (FD) communication may be possible. FDD communication is when transmissions in different directions (e.g. uplink vs. downlink) occur in different frequency bands. In TDD communication, transmissions in different directions (e.g., uplink vs. downlink) occur over different time durations. FD communication allows transmission and reception on the same time-frequency resource, enabling a device to transmit and receive concurrently on the same frequency resource.
[0118] One example of a frame structure is the Long-Term Evolution (LTE) frame structure having the following specifications.
[0119] 1. Each frame is 10 milliseconds (ms) in duration and consists of 10 subframes, each 1ms in duration.
[0120] 2. Each subframe includes two slots, each 0.5ms in duration.
[0121] 3. Each slot transmits 7 OFDM symbols (assuming normal cyclic prefix (CP) ) .
[0122] 4. Each OFDM symbol has a specific symbol duration and bandwidth (or partial bandwidth or bandwidth partition) related to the number of subcarriers and subcarrier spacing.
[0123] 5. The frame structure is based on OFDM waveform parameters such as subcarrier spacing and CP length (where the CP has either fixed length or limited length options) .
[0124] 6. The switching gap between uplink and downlink in TDD can be an integer multiple of the OFDM symbol duration / time.
[0125] Another example of a frame structure is the New Radio (NR) frame structure having the following specifications.
[0126] 1. Multiple subcarrier spacings are supported, each subcarrier spacing corresponding to a respective numerology.
[0127] 2. The frame structure depends on the numerology, but in any case, the frame length is set at 10ms, and consists of ten subframes of 1ms each.
[0128] 3. A slot is defined as 14 OFDM symbols, and the slot length depends upon the numerology. For example, the NR frame structure for a normal CP 15 Kilohertz (kHz) subcarrier spacing ( “numerology 1” ) and the NR frame structure for a normal CP 30 kHz subcarrier spacing ( “numerology 2” ) are different. For a 15 kHz subcarrier spacing, the slot length is 1ms, and for a 30 kHz subcarrier spacing, the slot length is 0.5ms. The NR frame structure may have more flexibility than the LTE frame structure.
[0129] Subcarrier spacing (SCS) is a parameter of scalable numerology which may allow the SCS to possibly range from 15 kHz to 480 kHz. The SCS may vary with the frequency of the spectrum and / or maximum UE speed to minimize the impact of Doppler shift and phase noise. In some examples, there may be separate transmission and reception frames, and the SCS of symbols in the reception frame structure may be configured independently from the SCS of symbols in the transmission frame structure. The SCS in a reception frame may be different from the SCS in a transmission frame. In some examples, the SCS of each transmission frame may be half the SCS of each reception frame. If the SCS between a reception frame and a transmission frame is different, the difference does not have to scale by a factor of two, especially if more flexible symbol durations are implemented using Inverse Discrete Fourier transform (IDFT) instead of Fast Fourier Transform (FFT) , for example. Additional frame structures can utilize different SCSs in various other implementations.
[0130] Wireless communication networks can use features such as cell, carrier, bandwidth parts (BWPs) , and occupied bandwidth. A device, such as a base station, may provide coverage over a cell. Wireless communication with the device may occur over one or more carrier frequencies. A carrier frequency is referred to as a carrier. A carrier may alternatively be called a component carrier (CC) . A carrier may be characterized by its bandwidth and a reference frequency, e.g., the center or lowest or highest frequency of the carrier. A carrier may be on a licensed or unlicensed spectrum. Wireless communication with the device may also or instead occur over one or more BWPs. For example, a carrier may have one or more BWPs. Generally, wireless communication with the device may occur over a spectrum. The spectrum may include one or more carriers and / or one or more BWPs.
[0131] A cell may include one or more downlink resources and optionally one or more uplink resources, or a cell may include one or more uplink resources and optionally one or more downlink resources, or a cell may include both, one or more downlink resources and one or more uplink resources. As an example, a cell may include only one downlink carrier / BWP, or may include one uplink carrier / BWP, or may include multiple downlink carriers / BWPs, or may include multiple uplink carriers / BWPs, or may include one downlink carrier / BWP and one uplink carrier / BWP, or may include one downlink carrier / BWP and multiple uplink carriers / BWPs, or may include multiple downlink carriers / BWPs and one uplink carrier / BWP, or may include multiple downlink carriers / BWPs and multiple uplink carriers / BWPs.
[0132] The NR telecommunication protocol supports both dynamic and semi-static UL-DL transmission direction configuration indication. The direction indication is used to configure transmission resources in either the UL or DL direction. Semi-static configuration, unlike the dynamic configuration which operates in every time slot, can be periodically updated within a given time period, such as, for example, every 200 or longer time slots. Semi-static configuration can also be configured only once or may be updated once in a while. Semi-static configuration often involves signaling that is not dynamic, such as broadcast signaling, RRC signaling, higher layer signaling, or non-DCI signaling.
[0133] Communications between the network and UEs are based on TDD, where uplink and downlink transmissions occur in different time slots. For example, each slot may contain 14 OFDM symbols and can include one or a combination of: downlink (DL) symbols; uplink (UL) symbols; guard symbols; and flexible, unknown or reserved symbols.
[0134] Alternatively, a slot may include one or a combination of DL symbols, UL symbols, and other symbols that are neither DL nor UL symbols for a particular UE, i.e., no transmission to and from the UE takes place on those symbols. The other symbols may be called “flexible” or “unknown” in general from a perspective of UEs that are receiving the information. One or more of the indicated “flexible” or “unknown” symbols may serve the purpose of guard period or gap between DL and UL symbol (s) . For example, there may not be any “guard” symbol (s) identified in a slot, instead, some symbols can be called “flexible” or “unknown” generally, one or more of which can be used as gap or can be overridden as DL or UL symbols by other dynamic signaling. To this end, a slot may include one or a combination of: downlink (DL) symbols; uplink (UL) symbols; and flexible or unknown symbols.
[0135] A user equipment (UE) can be semi-statically configured by higher layer signaling, such as a system information block (SIB) or using radio resource control (RRC) signaling that indicates the allocation of UL and DL symbols for different slots. Examples of such a higher layer signaling may include TDD UL-DL configuration, UL-DL-configuration-common (also known as TDD UL-DL configuration common) and UL-DL-configuration-dedicated (also known as TDD UL-DL configuration dedicated) . This type of semi-static configuration can be periodic. A semi-static UL-DL transmission direction configuration provides a slot format per slot over a number of slots, and can be repeated over different periods.
[0136] The UE interprets symbols in a slot indicated as downlink by the semi-static UL-DL transmission direction configuration (e.g., through a higher layer parameter such as UL-DL-configuration-common or UL-DL-configuration-dedicated) as available for reception. The UE considers symbols in a slot indicated as uplink by a semi-static UL-DL transmission direction configuration (i.e., through a higher layer parameter such as UL-DL-configuration-common or UL-DL-configuration-dedicated) as available for transmission. The UL-DL-configuration-dedicated may only be able to override the flexible symbol indicated in UL-DL-configuration-common. In some implementations, a grant-free enabled UE can detect a dynamic slot format indication (SFI) and can follow both dynamic and semi-static UL-DL configurations.
[0137] HARQ is a mechanism used in wireless communications to ensure reliable wireless transmission by combining forward error correction (FEC) and automatic repeat request (ARQ) . In HARQ, the initial transmission includes a FEC codeword with Cyclic Redundancy Check (CRC) bits to support error detection at the receiver. If a decoding error is detected, the receiver sends back a negative acknowledgement (NACK) signal to inform the transmitter of the error, and requests a retransmission. The retransmitted bits can be directly selected from the initially transmitted bits, referred to as chase-combining HARQ (CC-HARQ) , or can be selected from incrementally generated code bits forming a longer code word with the initially transmitted bits referred to as incremental-redundancy HARQ (IR-HARQ) .
[0138] For a DL transmission, a UE may send a HARQ feedback that either acknowledges successful decoding of the data (ACK) or indicates a non-successful decoding of data (NACK) . The HARQ feedback can be transmitted in a UL Physical Uplink Control Channel (PUCCH) or using Physical Uplink Shared Channel (PUSCH) resources. If a NACK is received, the base station (BS) may schedule a retransmission for HARQ combining.
[0139] Aspects of the present disclosure relate to a Real-Time Acknowledgement Amid Transmissions (RAAT) framework, which is an arrive-and-go transmission framework.
[0140] FIG. 6 illustrates an overview of the RAAT scheme according to an implementation of the present disclosure. Unlike the stop-and-go paradigm, the arrive-and-go paradigm does not wait for any ACK / NACK and keeps transmitting until successful reception (or decoding) of data packets. In such a case, a code block (CB) is further segmented into many smaller Redundancy Versions (RVs) , and these RVs are consecutively transmitted. For example, as shown in FIG. 6, five RVs are transmitted in one single transmission. In some implementations, a retransmission request may not be required between these RVs. When transmitting multiple short RVs in a single scheduled transmission, the NACK may not need to be fed back, and a 1-bit ACK is fed back upon successful decoding.
[0141] In some implementations, to support the RAAT scheme, one or more of following modifications may be required by some standard and protocol.
[0142] 1. A channel code that supports multiple RVs and the corresponding RV design.
[0143] 2. The feedback-and-stop transmission mechanism.
[0144] 3. Control signaling to manage the new RAAT mode.
[0145] 4. Association between data packet and feedback.
[0146] 5. New frame structure.
[0147] FIG. 7 illustrates the RAAT scheme involving a downlink data channel and an uplink control channel according to an implementation of the disclosure. The data transmission in the downlink can be scheduled in a certain time slot, virtual Transmission Time Interval (TTI) , but is not bounded by the slot boundaries. With a fast decoder that can decode while receiving, early termination may be possible once the received symbols are sufficiently reliable, and thus a data packet transmission does not necessarily occupy the whole slot. Advantages thus achieved include, but are not limited to, savings in transmission energy, reduction of inter-cell and inter-UE interference, and not requiring accurate CQI measurement and feedback. Also, due to the native rate adaptability of the channel codes, only long-term open loop measurement and feedback may be required instead of real-time and accurate CQI.
[0148] FIG. 8 is a diagram illustrating an algorithm performed at a BS according to an implementation of the present disclosure. The BS is responsible for scheduling, encoding and transmitting. The scheduling algorithm receives an open-loop CQI, ACK, and the current scheduled modulation and coding rate (e.g., adaptive modulation and coding (AMC) ) as inputs, and outputs a minimum transmission length. The minimum transmission length informs the UE to at least receive such a length before performing the first decoding attempt. In an example, the required transmission time is recorded in history and a margin is added to it if necessary, without introducing extra transceiver complexity. In some implementations, sophisticated algorithms involving machine learning and artificial intelligence (AI) may also be incorporated.
[0149] FIG. 9 is a schematic diagram illustrating BS resource scheduling according to an implementation of the present disclosure. The BS scheduling is not bounded by the slot boundaries, but depends on when the previous TB / CB is successfully decoded. In some implementations, the two consecutive TBs (e.g., TB1 and TB2) can be sent to the same UE. Alternatively, multi-user scheduling can also be supported, for example, TB1 and TB2 for user1 and user2 respectively.
[0150] To support encoding of the channel codes, aspects of the present disclosure utilize the following features.
[0151] 1. Rateless property, where the code word is encoded without specifying a particular code rate. The actual perceived code rate from the decoder depends on how many code bits are received.
[0152] 2. Fine-grained incremental redundancy, where the choice of transmitted code length can take any value below the maximum mother code length.
[0153] 3. Some repetition may be allowed during rate matching.
[0154] In some implementations, the RAAT scheme co-exists with the HARQ scheme. Therefore, the BS may indicate to the UE of either a HARQ mode or a RAAT mode using a field in RRC or DCI signaling.
[0155] Aspects of the present disclosure relate to one or more of the following different techniques of DCI scheduling for the progressive rateless coding schemes.
[0156] 1. A single DCI is used to schedule both the initial transmissions and the retransmissions.
[0157] 2. A first DCI is used to schedule the initial transmissions and a second DCI is used to schedule the retransmissions.
[0158] 3. Each initial transmission and retransmission are scheduled by a separate DCI.
[0159] In some implementations, each transmission (initial or retransmission) may be referred to as a transmission occasion (TO) . As the transmission (when in DL) is transmitted on a Physical Downlink Shared Channel (PDSCH) , each transmission may also be referred as a PDSCH.
[0160] FIG. 10 illustrates an example of a single DCI 1002 scheduling for an initial transmission and multiple retransmissions that are contiguous in time. FIG. 10 shows time-frequency resources (also referred to as resources) 1004, 1006, 1008, and 1010 scheduled for the initial transmission and the multiple retransmissions. The horizontal axis of FIG. 10 represents the time domain, and the vertical axis of FIG. 10 represents the frequency domain. As shown in FIG. 10, the resource 1004 is scheduled for the initial transmission, the resources 1006 is scheduled for the first retransmission, the resources 1008 is scheduled for the second retransmission, and the resources 1010 is scheduled for the third retransmission. The resources 1004, 1006, 1008, and 1010 can occupy the same frequence subband. In the time domain, the resources 1004 can occupy time units 1014, the resources 1006 can occupy time units 1016, the resources 1008 can occupy time units 1018, and the resources 1010 can occupy time units 1020. Each time unit (e.g., time unit 1014, 1016, 1018, or 1020) shown in the figure can be a symbol, a slot, a mini-slot or any time unit. A BS or a network (e.g., the network node 170 of FIGS. 1-2) can transmit one single DCI 1002 (e.g., in a PDCCH) to a UE (e.g., the ED 110 of FIGS. 1-2) to schedule the initial transmission and the multiple retransmissions. Accordingly, the UE can receive the DCI 1002 from the BS. In some implementations, the initial transmission and the multiple retransmissions (also referred to as retransmission occasions) may occupy different time durations. For example, a size of the resource 1004 can be larger than a size of the resource 1006 in the time domain. In some instances, the resources 1006, 1008, and 1010 can have the same size in the time domain. In some implementations, in addition to the initial transmission and the multiple retransmissions, the DCI 1002 may also schedule potential HARQ feedback transmission occasions (TO) for the UE to potentially send a HARQ feedback (e.g. ACK or NACK) to the BS. For example, the HARQ feedback TOs can be scheduled at locations 1022 in the time domain.
[0161] In some implementations, the initial transmission and the retransmission occasions may be contiguous over time. In other words, the resources 1004, 1006, 1008, and 1010 can be consecutive in the time domain. In some implementations, there may be time gaps between different transmission occasions (e.g., as described in detail with respect to FIG. 12) .
[0162] There may be different levels of time granularity for the initial transmission and the retransmissions. For the initial transmission, in order for the transmission to be decodable, a minimum code rate with respect to the channel condition is required. In other words, a minimum number of coded bits may be required to be sent for the data block to be decodable. However, after an initial transmission is sent, each retransmission may only add a small, or small as possible, amount of redundancy after the initial transmission is sent, if the receiver cannot decode the data block. With potentially only a small amount of additional redundancy bits, the receiver may be able to decode the block using IR combining. To reduce the amount of resources to be sent and to achieve an optimal code rate, the retransmission can use smaller time granularities or simply smaller time domain durations. Therefore, there may be multiple time domain granularities or durations for different transmission occasions scheduled with the single DCI. More specifically, for this example, there are two-time domain granularities: the initial transmission occupies a larger time domain duration including the time units 1014, while each retransmission occasion occupies a smaller time domain duration. For example, the first retransmission occupies a time domain duration including the time units 1016, the second retransmission occupies a time domain duration including the time units 1018, and the third retransmission occupies a time domain duration including the time units 1020. In some implementations, each time unit 1016 can be smaller than each time unit 1014. For example, the time unit 1016 can be a symbol, and the time unit 1014 can be a slot. In some implementations, the time units 1016, 1018, and 1020 can be of the same size. Each transmission occasion (initial transmission and the retransmission) represents a potential decoding opportunity for the receiver.
[0163] FIG. 11 illustrates an example of two DCI scheduling –a first DCI 1101 for scheduling the initial transmission and a second DCI 1102 for scheduling multiple retransmissions that are contiguous in time. For example, the DCI 1101 indicates a resource 1104 scheduled for the initial transmission, and the DCI 1102 indicates resources 1106, 1108, and 1110 scheduled for the multiple retransmissions. Similar to the example of FIG. 10, HARQ feedback TOs can also be scheduled by DCI (e.g., DCI 1101 or DCI 1102) . As shown in FIG. 11, the HARQ feedback TOs can be scheduled at locations 1122 in the time domain.
[0164] In some cases, the multiple transmission occasions of the progressive rateless coding scheme may not be contiguous in the time domain, i.e., they may be spaced apart with a gap between each transmission in the time domain. The gap allows the BS or the network to have enough time to stop the next transmission right away after receiving a potential ACK from the UE in response to a successful decoding after receiving the previous transmission.
[0165] FIG. 12 illustrates an example scheme where multiple transmission occasions are spaced apart in the time domain according to an implementation of the present disclosure. In some implementations, similar to the example of FIG. 10, a DCI can indicate a resource 1204 scheduled for an initial transmission and resources 1206, 1208, and 1210 scheduled for multiple retransmissions. In some implementations, similar to the example of FIG. 11, a first DCI can indicate the resource 1204 scheduled for the initial transmission, and a second DCI can indicate the resources 1206, 1208, and 1210 scheduled for the multiple retransmissions. In the example of FIG. 12, the DCI used to schedule the transmission occasions (e.g., the initial transmission and the multiple retransmissions) can also indicate a time gap (e.g., indicated as T0 in FIG. 12) between an initial transmission and a first retransmission, as well as a time gap (e.g., indicated as T1 in FIG. 12) between adjacent retransmissions. The DCI may also need to indicate resources 1222, 1224, and 1226 for HARQ feedback transmission opportunities or transmission occasions, which may indicate at least a time gap K1 between a data transmission (e.g., PDSCH) and a time location of the HARQ feedback. For example, as shown in FIG. 12, K1 represents an offset in the time domain between an ending location of the resource 1204 and a starting location of the resource 1222. In some implementations, each transmission or retransmission may correspond to a HARQ feedback transmission occasion.
[0166] The DCI to schedule a progressive rateless coding may include, but is not limited to, one or more of the following information.
[0167] 1. Time frequency resource allocation for initial transmission: This may include time and frequency resource allocations for the initial transmission (e.g., as shown in FIGS. 10-12) .
[0168] 2. Frequency domain resource assignment: Frequency resource allocation may indicate the physical resource blocks (PRB) used for each transmission. In some implementations, the frequency resource allocation may be indicated separately for each transmission occasion. In other implementations, e.g., as shown in FIGS. 10-12, in order to reduce the signaling overhead, the frequency resource allocation may be the same for the initial transmissions and the retransmissions such that only one indication is enough.
[0169] 3. Time domain resource assignment: The time domain resource allocation may indicate the time domain resources used for the initial transmission and the retransmissions. If the time domain resource durations of all transmission occasions are the same, then only a one-time duration needs to be indicated. In some cases, the time domain duration of the resource assignment for the initial transmission (e.g., the resource 1004 of FIG. 10) and the retransmissions (e.g., the resources 1006, 1008, and 1010 of FIG. 10) may be different. The time domain duration of the resource assignment for the retransmissions can be the same. In this case, both the time durations for the initial transmission and the retransmission need to be indicated. Therefore, two different time domain resource allocations may be used to indicate the initial transmission and retransmissions, respectively. If the DCI is scheduling a retransmission for a progressive rateless coding transmission or the DCI is a second DCI scheduling all the retransmission TOs of the progressive rateless coding scheme, only a single time duration and gap (e.g., the time duration of the resource 1006) may need to be indicated for all the retransmission TOs.
[0170] For the initial transmission, the starting time location (e.g. the starting symbol and slot) may be indicated, along with the time duration (e.g. number of symbols for the initial transmission) or the ending location (e.g. the ending symbol) . For instance, in the example of FIG. 10, the DCI can include a starting location of the resource 1004 in a time domain and an ending location of the resource 1004 in the time domain. In some implementations, to indicate the ending location of the resource 1004, the DCI can further include the ending location of the resource 1004 directly. In some other implementations, to indicate the ending location of the resource 1004, the DCI can further include a time duration, and the time duration can be determined based on the starting location of the resource 1004 and the ending location of the resource 1004. For example, the time duration can be a difference or a gap between the starting location and the ending location of the resource 1004. In this way, when the UE receives the DCI, the UE can determine the ending location of the resource 1004 based on the starting location of the resource 1004 and the time duration (e.g., by adding the time duration to the starting location of the resource 1004) .
[0171] For the retransmission, if the allocation is contiguous, the starting location of retransmission may immediately follow the ending location of the initial transmission (e.g., the next symbol after the initial transmission) . Each subsequent retransmission may immediately follow the previous retransmissions (e.g., the next symbol) . If the transmission occasions are spaced out (e.g., as illustrated in FIG. 12) , the gap between the initial transmission and retransmission T0 as well as the gap between the retransmissions T1 need to be indicated. The time duration of each retransmission may also be indicated.
[0172] 1. Number of retransmissions: The number of retransmissions may need to be indicated. Alternatively, the ending location (e.g. ending symbol) of the entire progressive rateless coding transmission can be indicated and the number of retransmissions can be then derived based on the ending location along with the starting location of the initial transmission or the retransmissions. In other implementations, both the ending location and the number of retransmissions is indicated, and the time duration for the retransmission may not be indicated but instead be derived based on the ending and initial location of retransmissions and number of retransmissions.
[0173] 2. MCS: A modulation and coding scheme (MCS) may be indicated for the initial transmission or the overall transmission (including initial transmission and retransmission occasions) . The MCS may be indicated as an MCS index from an MCS table or the modulation and code rate may be separately indicated.
[0174] 3. New data indicator (NDI) : The new data indicator may indicate whether it is a retransmission or a new transmission. For example, if NDI is toggled with respect to the same HARQ process, then it is a new transmission, else, it is a retransmission. In some implementations, if the progressive rateless coding transmission includes the initial transmission TO, then NDI indicates a new transmission. In some implementations, if the DCI is the second DCI (e.g., the DCI 1102 of FIG. 11) , then retransmission TOs are scheduled, and the NDI indicates retransmission.
[0175] 4. Redundancy version (RV) : There may be a RV indication to indicate whether retransmission is using progressive RV, where the starting point of rate matching follows a previous transmission or the starting point of rate matching is fixed and defined for each RV index.
[0176] 5. Whether UE should be transmitting ACK only for HARQ feedback or both ACK and NACK for HARQ feedback.
[0177] 6. Resource allocation for the HARQ feedback transmissions.
[0178] The timing location of the HARQ resource may be indicated by a time gap between the transmissions and the corresponding HARQ feedback transmission occasions. This time gap may be indicated as a PDSCH-to-HARQ_feedback timing, denoted as K1. The gap K1 is generally indicated as the number of slots, while the symbol location within the slot is determined by the semi-static configuration of the HARQ feedback resource. In some implementations, the gap K1 can be indicated using other time units such as symbols or mini-slots.
[0179] For the progressive rateless coding scheme, the HARQ feedback is usually transmitted with low latency, such that the BS or the network can stop transmission of the data block early. Therefore, the HARQ feedback may use low latency-based timing, for example, symbol based HARQ feedback timing. This may be implemented by indicating the time gap K1 in DCI, where K1 includes an option with symbol-based length. For example, K1 can be configured in multiple options in RRC, and DCI can indicate which K1 value among the RRC configured value set is chosen. The K1 value configured in RRC can include at least an option with 0 slot. In order to support 0 slot with different number of symbols, RRC configuration of K1 value may include multiple symbol values within the 0 slot options. For example, RRC configured K1 values can include 1, 2, 4, 8 slots, 0 slots with 7 symbols, 0 slots with 4 symbols, 0 slots with 2 symbols, and 0 slots with 1 symbol, and so on.
[0180] In some implementations, instead of indicating K1 in DCI, the HARQ feedback timing may be determined based on the UE’s processing time. For example, based on the UE’s processing time, the HARQ feedback timing is determined as the first UL symbol after the last symbol of PDSCH transmission plus Tproc, where Tproc is the processing time which includes both decoding processing and HARQ feedback preparation time.
[0181] Since there can be multiple transmissions scheduled by the DCI, each HARQ feedback TO may be associated with a data transmission (an initial transmission PDCSH or a retransmission PDSCH) . The timing of each HARQ feedback is calculated using the corresponding transmissions (e.g., the corresponding PDSCH) , via the K1 gap or processing time. In some implementations, the number of HARQ feedback TO may be equal to the number of transmissions. In some other implementations, the number of HARQ feedback TO may be larger than or smaller than the number of transmissions.
[0182] FIG. 13 is a diagram illustrating an example timing of multiple HARQ feedback TOs according to an implementation of the present disclosure. Referring to FIG. 13, a scenario is depicted where DL transmission occurs in a DL subband or a DL carrier 1301 while the HARQ feedback TO is located in an UL subband or an UL carrier 1302. A resource 1304 is scheduled in the DL subband 1301 for an initial transmission, and resources 1306, 1308, and 1310 are scheduled in the DL subband 1301 for multiple retransmissions. Resources 1322, 1324, and 1326 are scheduled in the UL subband 1302 for the HARQ feedback TOs. As shown in FIG. 13, K1 represents an offset in the time domain between an ending location of the resource 1304 and a starting location of the resource 1322. However, it is understood that other implementations for the location of the HARQ feedback TO is possible, and the timing relationships described are applicable to different scenarios. For example, the data transmission (e.g., the initial transmission and the multiple retransmissions) may be in a DL FDD carrier, while the HARQ feedback TO is located in a paired UL FDD carrier. In another example, the data transmission may be in DL time units (e.g. symbols / slots) of a TDD carrier, while the HARQ feedback TO is located in UL time units of a second TDD carrier. In yet another example, the data transmission is in DL time units (e.g. symbols / slots) of a TDD carrier, while the HARQ feedback TO is located in UL time units of the same TDD carrier. In yet another example, the data transmission is in DL time units (e.g. symbols / slots) of a TDD carrier, while the HARQ feedback TO is located in UL time units of a second FDD carrier. In yet another example, the data transmission is in DL subband of subband full duplex (SBFD) symbols of a TDD carrier, while the HARQ feedback TO is located in UL subband of subband full duplex (SBFD) symbols of the same TDD carrier.
[0183] In some implementations, the HARQ feedback TO may not be completely associated with each transmission. The number of corresponding timing locations of HARQ feedback TO may be configured semi-statically or indicated in the DCI. The timing location of the periodic TO can be determined based on timing of the starting TO, periodicity, and a number of HARQ feedback TOs.
[0184] Starting TO can be associated with the initial transmission occasion. Starting HARQ feedback TO can be determined based on the time gap K1 and UE processing time. In some other implementations, time location of starting TO may also be configured or dynamically indicated without direct association of the time location of the initial transmission occasion. Periodicity, which is the time gap between two HARQ feedback TO, can be determined by dynamic indication in DCI, semi-static configuration (e.g., in RRC) associated with the time duration of each retransmission occasion, or consecutive at every symbol.
[0185] The corresponding number of HARQ feedback TOs can also be determined based on a dynamic indication in DCI, semi-static configuration (e.g. in RRC) associated with number of transmission occasion, or implicitly determined based on the end of progressive rateless coding transmission. For the last scenario, if the end of progressive rateless coding (e.g., last PDSCH) transmission is known, the last HARQ feedback TO can first be determined using a time gap K1 or processing time from the end of the last retransmission; then based on the timing of starting and last HARQ feedback TO, along with the periodicity, the number of HARQ feedback TO can be determined.
[0186] In some implementations, the HARQ feedback timing is determined based on a reference point. For instance, the UE may wake up upon a packet arrival and wishes to transmit or receive the packet quickly in one-shot (referred to as a “one-shot” scenario) to save energy to switch back to sleep mode as soon as possible. In the one-shot scenario, when the UE wakes up, no DCI may be sent or a simplified DCI with low overhead may be sent for scheduling the data transmission. In case of low overhead DCI, there may be no indication of the HARQ feedback timing. In these scenarios, the HARQ feedback timing may depends on a reference timing. The reference timing may be a preconfigured reference point Tref. Tref can be a reference point in the time domain. If the UE is not in a connected state, the UE may still be able to identify the reference point through detecting the synchronization signal.
[0187] There may be multiple HARQ feedback TOs preconfigured with respect to Tref. For example, periodic HARQ feedback TO may be preconfigured at Tref +n× period, where period is the time gap between HARQ feedback TOs and it is preconfigured. The HARQ feedback TO may be sent on the first HARQ feedback TO after T0+ Tpro+delta, T0 denotes the time of reception of the DL transmission in PDSCH, delta is a predefined delay and can be 0, Tpro is the processing time for the PDSCH reception and the HARQ feedback preparation time.
[0188] In some implementations, the DCI can indicate a reference point for the HARQ feedback TOs in the time domain. For example, the reference point can be the ending location (in the time domain) of the resource 1204 of FIG. 12. In another example, the reference point can be the reference point Tref described above.
[0189] In some implementations, the DCI can indicate at least one of a starting point (e.g., the starting location of the resource 1222 of FIG. 12) , a periodicity (e.g., the time gap between two adjacent resources of the resources 1222, 1224, and 1226) , an ending point (e.g., the ending location of the resource 1226) , or a number of TOs for the HARQ feedback TOs in the time domain.
[0190] Aspects of the present disclosure relate to a SBFD configuration. In some implementations, TDD is widely used for NR deployment. In TDD, the time domain resource is divided into UL resources and DL resources. NR allows flexible allocation of the DL and UL in time domain, through both semi-static configuration and dynamic indication. SBFD is a duplexing scheme, which allows allocation of DL and UL resources in the same time domain resource but in different subbands of a cell.
[0191] FIG. 14 includes diagrams 1401 and 1402 illustrating examples of SBFD configurations according to an implementation of the present disclosure. Referring to FIG. 14, time domain resources 1403 have been divided into non-SBFD resources (which further includes DL and UL resources) and SBFD resources. Without loss of generality, symbol represents a time unit and encompasses DL symbols, UL symbols, and SBFD symbols. However, this can also be applicable to a slot or any other time unit. In other words, in the example of FIG. 14, each time domain resource 1403 is a symbol. In some other implementations, a time domain resource 1403 can be a slot, a mini-slot, or any other time units. In FIG. 14, D, X, and U represent DL symbols, SBFD symbols, and UL symbols, respectively. The SBFD symbols are further divided into DL subband, UL subband, and guard bands as illustrated in FIG. 14.
[0192] In some implementations, as shown in diagram 1402, SBFD symbols can be configured to be consecutive in the time domain. In some implementations, as shown in diagram 1401, multiple consecutive SBFD symbols can be configured to be between DL symbols and UL symbols in the time domain.
[0193] In an implementation, both the SBFD symbols and the DL / UL subband locations can be semi-statistically configured. In another implementation, the SBFD symbols are semi-statically configured, while the DL / UL subband locations are indicated dynamically. In yet another implementation, both the SBFD symbols as well as the DL / UL subband locations can be semi-statically configured. However, the base station can dynamically allocate UL / DL subband locations that may override the semi-static configurations.
[0194] Aspects of the present disclosure describe UCI (e.g., HARQ feedback) resource allocation. Traditionally, HARQ feedback (e.g., ACK or NACK) frequency and some other resources (such as a starting symbol and a number of symbols within a slot, codebook, format, sequence etc. ) are configured in Physical Uplink Control Channel (PUCCH) configurations. However, the slot number can be determined based on DCI indication.
[0195] FIG. 15 illustrates an example of PUCCH configuration for SBFD that is used for the UCI resource configuration for transmission of HARQ feedback, according to an implementation of the present disclosure.
[0196] For SBFD symbols, a frequency location of UCI 1501 in SBFD symbols 1503 can be flexible or SBFD dependent.
[0197] In PUCCH configuration, the frequency resources can be partially configured. For example, a number of PRBs may be configured. However, the overall frequency resource may depend on a starting frequency location or a frequency offset.
[0198] In some implementations, a starting frequency location 1502 of UCI 1501 may depend on a frequency location of the UL subband in SBFD. For example, the starting frequency location 1502 of UCI 1501 can be indicated as an offset (e.g., frequency offset) from a frequency location (e.g., a starting location, a center location, or an ending location) of the UL subband in the SBFD configuration. The frequency location of the UL subband in SBFD may be configured in either a semi-static configuration or a dynamic SBFD configuration. In some implementations, the frequency offset of the starting frequency location 1502 is an offset with respect to a boundary between UL subbands and DL subbands. In some implementations, the frequency offset of the starting frequency location 1502 is an offset with respect to a boundary of a carrier.
[0199] Alternatively, the starting frequency location (or frequency offset) 1502 of UCI 1501 may be dynamically signaled in DCI.
[0200] In some implementations, time location of UCI 1501 can be configured as below.
[0201] For low latency UCI applications, the PUCCH location within a slot is also flexible. The starting symbol of the PUCCH resources within a slot that are used for UCI transmission may depend on the PUCCH configuration. However, it is rather based on the timing of the UCI location indicated in the DCI (e.g., it may depend on a time gap K1, which is the time gap between the PDSCH and HARQ feedback) . In other words, a starting symbol of UCI 1501 can be flexible or can depend on the time gap K1.
[0202] Alternatively, periodic UCI resources (e.g., reserved HARQ-ACK, Scheduling Request (SR) , Channel State Information (CSI) ) may be configured in the UL subband of SBFD symbols in advance. The actual HARQ feedback resource can be the first available HARQ feedback resource from the RRC configuration after the time gap K1 or the UE’s processing time.
[0203] In some implementations, if HARQ feedback (e.g., ACK / NACK) is piggybacked as a UCI on the PUSCH, the HARQ feedback is mapped to a reserved location that depends on the location of the starting symbol.
[0204] In some implementations, the DCI can schedule specific resources and / or MCS for ACK / NACK in a manner similar to scheduling PUSCH.
[0205] Aspects of the present disclosure describe semi-static SBFD configuration as below.
[0206] The SBFD configuration can be configured using cell-specific or UE-specific semi-static signaling. For example, in RRC, the SBFD configuration can be configured in UL-DL-TDD-configuration-common for cell specific or group common configurations and / or UL-DL-TDD-configuration-dedicated for UE-specific configurations.
[0207] In some implementations, the configuration can include location of D, X, U, and F symbols, where D is DL symbol, X is SBFD symbol, U is UL symbol, and F is flexible symbol. F symbol can be overridden later by dynamic indication of one of the other D, U, or X symbols.
[0208] In some implementations, for SBFD symbols, the UL subband, guard band, and DL subband frequency locations are indicated. The UL subband can be located either in the middle (as depicted in the diagram 1401 of FIG. 14) or on one side (as depicted in the diagram 1402 of FIG. 14) of the band or Bandwidth Part (BWP) . The indication can be an explicit indication of two out of the three bandwidths including UL subband, DL subband, and guard band. And the third one can be derived from the other two.
[0209] As shown in FIG. 14, typical format for a frame or slot can be D.. DXX.. XU (e.g., as shown in diagram 1401) or XXX…X (e.g., as shown in diagram 1402) , where D, X, or U represent a symbol or a time domain resource in other time units.
[0210] Aspects of the present disclosure describe dynamic SBFD configuration as below.
[0211] In RRC / cell specific signaling, the semi-static TDD configuration may configure the SBFD symbol (e.g., DDXXXXXXU) . However, the division of UL and DL subband (i.e., UL / DL subband location configuration) in the SBFD symbols may have the following options:
[0212] 1. The division is not configured, so it can be dynamically indicated later.
[0213] 2. The division is configured, but is subject to override in dynamic signaling.
[0214] 3. The division is configured, and cannot be overridden in dynamic signaling.
[0215] In some implementations, in dynamic signaling (SFI or dynamic SBFD signaling) , DL / UL / guard band location configurations for SBFD symbols are provided.
[0216] Alternatively, when scheduling progressive rateless code transmission, the BS can indicate the SBFD UL / DL subband location configuration in the scheduling DCI, either explicitly or implicitly. This indication can override the semi-static configuration.
[0217] In some implementations, the DCI may directly indicate UL ACK / NACK resources including frequency locations which may or may not be consistent with the semi-static configuration of the UL / DL subband division. This resource indication in DCI can take priority over the semi-static configurations.
[0218] Aspects of the present disclosure provide further details on UCI resource configuration with SBFD, as well as HARQ feedback resource allocation for progressive rateless coding transmissions.
[0219] According to an aspect of the present disclosure, the PUCCH configuration for SBFD and non-SBFD symbols is provided.
[0220] Traditionally, UCI resources are configured with PUCCH format, starting symbol, starting PRB, number of PRBs, sequence, frequency hopping (FH) etc. However, for a UE configured with SBFD, the frequency allocation for an SBFD symbol and a non-SBFD UL symbol may be different for the UCI.
[0221] According to an implementation, separate configuration can be provided for the UCI or PUCCH in SBFD and non-SBFD symbols, where the frequency size can be different for SBFD and non-SBFD symbols.
[0222] According to another implementation, same configuration can be provided for the UCI or PUCCH in SBFD and non-SBFD symbols, except that different starting PRBs may be configured. For example, different starting PRBs can be configured for SBFD and non-SBFD symbols, or a frequency offset may be configured for SBFD symbols or indicated by the scheduling DCI. The frequency offset can be the frequency offset with respect to the UL subband locations (e.g., with respect to a starting PRB of the UL subband in SBFD symbols) , or it can be the frequency offset with a starting PRB of non-SBFD symbols.
[0223] FIG. 16 illustrates an example UCI configuration for SBFD and non-SBFD symbols, according to an implementation of the present disclosure. Referring to FIG. 16, many of the UCI resources are configured common for both UL symbols 1602 and SBFD symbols 1601. However, a starting PRB location can be configured differently for UCI in UL symbols 1602 and for UCI in SBFD symbols 1601. For UL symbols 1602, the starting PRB can be configured. For SBFD symbols 1601, the starting PRB location can be determined based on a frequency offset 1603 with respect to UL subband locations. The frequency offset can be semi-statically configured (e.g., in PUCCH configuration) or is dynamically indicated (e.g., in DCI) .
[0224] In some implementations, a starting frequency location of UCI may depend on a frequency location of the UL subband in SBFD. For example, the starting frequency location of the UCI can be indicated as an offset (e.g., frequency offset 1603) from a frequency location (e.g., a starting location, a center location, or an ending location) of the UL subband in the SBFD configuration. The frequency location of the UL subband in SBFD may be configured in either a semi-static configuration or a dynamic SBFD configuration. In some implementations, the frequency offset of the starting frequency location is an offset with respect to a boundary between UL subbands and DL subbands. In some implementations, the frequency offset of the starting frequency location is an offset with respect to a boundary of a carrier. Alternatively, the starting frequency location (or frequency offset 1603) of UCI may be dynamically signaled in DCI.
[0225] In some other implementations, the starting frequency location of UCI in SBFD symbols may be indicated as a frequency offset with respect to the starting frequency location of UCI in non-SBFD symbols.
[0226] In another implementation, the same basic configurations as well as additional configuration for SBFD symbols can be provided. The additional configuration can include additional time domain configuration (e.g., periodicity / offset) .
[0227] Some other implementations of the present disclosure relate to SBFD configuration for a dedicated UCI band.
[0228] Although an SBFD symbol is divided into DL and UL subbands, an UL subband can be used for at least one of UCI or PUSCH transmissions.
[0229] In some implementations, only a small UL subband (e.g., several subcarriers (SCs) within a PRB) is needed for low latency UCI transmission. In this case, the SBFD may be reserved for UCI transmission. The UL subband can be at sub-PRB level.
[0230] In some implementations, reserved HARQ-ACK, SR, CSI and other UCI resources may be configured periodically within an UL subband with less overhead (e.g., use all subcarriers, therefore there is no need for further frequency allocations) .
[0231] In some implementations, signaling that indicates resources for UCI can further indicate resources for transmission of at least one of a SR, CSI, or any other UCI. In some implementations, resources for transmission of SR, CSI, and UCI can be indicated by different signaling (e.g., using higher layer signaling such as RRC, or using DCI) .
[0232] Aspects of the present disclosure relate to different mapping type configurations, which may be useful for low latency UCI. The low latency UCI can be used, for example, to transmit HARQ feedback.
[0233] Low latency UCI mapping type is described as below.
[0234] Traditionally, the starting symbols for the UCI are configured in the PUCCH configuration. Table 1 illustrates examples of current NR PUCCH configurations for the symbols used in the transmission of PUCCH formats 0-2. Other formats follow the same or similar configurations. It can be seen that, following the PUCCH configuration, the starting symbol and the number of symbols within a slot are fixed.
[0235] With low latency UCI for progressive coding, flexibility is required in symbol locations within a slot for UCI transmissions. Therefore, the UCI timing can be dynamically indicated, including, but not limited to, the symbol location of the UCI. That is, the starting symbol of the UCI in a slot can change depending on the dynamic indication.
[0236] Therefore, similar to Demodulation Reference Signal (DMRS) and PDSCH mapping types, multiple (e.g., two) mapping types for UCI can be used.
[0237] Mapping type, Type A: the starting symbol location in a slot (e.g., with respect to a slot boundary) is semi-statically configured (e.g., using higher layer signaling) .
[0238] Mapping type, Type B: the starting symbol is not configured, but dynamically indicated (through the symbol level time gap K1) .
[0239] Mapping type may be determined based on one or more of the following methods.
[0240] 1. Explicit indication of mapping type in the PUCCH configuration. In some implementations, the PUCCH configuration includes the mapping type for a starting symbol of the resource scheduled for the UCI, and the starting symbol is configured through higher layer signaling (e.g., RRC) or DCI. For example, if the mapping type is Type B, then there is no starting symbol indication in RRC. In another example, the PUCCH configuration can indicate that the mapping type is Type A, and the starting symbol location in a slot can be indicated in RRC.
[0241] 2. Additional entry of the starting symbol in the PUCCH configuration indicating flexible through dynamic indication. In this case, the starting symbol field of the PUCCH configuration, has an additional value, which is “flexible, ” and the actual symbol location depends on the dynamic indication of time gap in DCI.
[0242] 3. No additional indication of mapping type, but if DCI indicates K1 to be one of the symbol level options (e.g., 0 slot and a number of symbols for the time gap) , then the starting symbol in RRC is invalid, and overridden by DCI with K1. In other words, the mapping type can be indicated implicitly. In some other implementations, DCI may indicate K1 to be one of the symbol level options with a number of symbols for the time gap that may not be 0 slot, which may also determine the starting symbol of UCI and may also indicate the mapping type implicitly.
[0243] Table 1
[0244] In some implementations, UCI can also be transmitted on PUSCH or be multiplexed with UL data transmission on a PUSCH. It is to be understood that the description of the mapping type is not limited to PUCCH transmission, but can also be applicable to UCI transmitted on PUSCH or just PUSCH transmission.
[0245] Aspects of the present disclosure describe timing of multiple HARQ feedback TOs in SBFD. For progressive rateless coding transmission (or just repetition transmissions) , there are multiple HARQ feedback TOs. The HARQ feedback TOs may be periodic.
[0246] FIG. 17A illustrates an example of multiple periodic HARQ feedback TO 1703, according to an implementation of the present disclosure. The multiple HARQ feedback TOs 1703 may be associated with different data transmission TOs (e.g., an initial transmission 1701 and retransmission 1702) . Alternatively, the potential HARQ feedback TOs may be semi-statically configured.
[0247] The semi-static configuration may include general configuration of each HARQ feedback resource, including a frequency resource configuration in the SBFD symbols. Therefore, the multiple HARQ feedback TOs 1703 may be configured using periodicity 1704 and offset (e.g., starting slots, starting symbol) . The actual HARQ feedback resource that is used may be the first HARQ feedback resource after decoding and processing time. Alternatively, the actual HARQ feedback resource that is used may be the first HARQ feedback available after the timing indicated by the time gap K1.
[0248] In some implementations, the available HARQ feedback TO or resource may be consecutive (e.g., in consecutive symbols) .
[0249] FIG. 17B illustrates an example of consecutive multiple HARQ feedback TOs 1705, according to an implementation of the present disclosure. In some implementations, the UE does not have to use every available HARQ feedback TO 1705. The first available HARQ feedback TO may still be indicated in the DCI, depending on a time gap K1, for example. As shown in FIG. 17B, the time gap K1 can be a time offset between an initial transmission 1706 (e.g., an ending time location of the initial transmission 1706) and a respective HARQ feedback 1705 (e.g., a starting time location of the respective HARQ feedback 1705) .
[0250] Aspects of the present disclosure describe PDSCH resource allocation and Transport Block Size (TBS) determination for the progressive rateless coding scheme, which includes the presence of SBFD symbols.
[0251] FIG. 18 illustrates an example of PDSCH resource and TBS determination, according to an implementation of the present disclosure.
[0252] TBS determination is described as below.
[0253] In some implementations, based on resource allocation and the target MCS, TBS of the initial burst is determined by counting resource elements (REs) from DL usable PRBs for SBFD-aware UEs. Non-SBFD aware UEs may count all the REs.
[0254] Alternatively, the TBS can be determined based on resource allocation of overall transmissions (for example, maximum Tx length or all the transmission and retransmission TOs scheduled by the single DCI) and corresponding target combined MCS.
[0255] In some other implementations, the TBS can be determined based on the resource allocation for overall transmissions, such as the maximum transmission (Tx) length or all the transmission and retransmission TOs scheduled by a single DCI, along with the corresponding target combined MCS.
[0256] In some implementations, the scheduled initial burst or initial transmission TO 1801 can be located in DL symbols, DL + SBFD symbols, or SBFD symbols only.
[0257] In some implementations, the PDSCH resource for the initial burst includes only REs from DL usable PRBs, and the number of REs used to determine TBS includes only DL usable resources.
[0258] Similarly, in some implementations, for the retransmission burst or retransmission TOs 1802, only the REs in the DL subband (DL usable PRBs) are used to calculate the number of coded bits for rate matching purposes.
[0259] Frequency resources for PDSCH, for the SBFD symbols, and the non-SBFD symbols may be scheduled separately, or non-DL resources from the SBFD symbols may be excluded.
[0260] Aspects of the present disclosure describe UE behavior with respect to UL / DL resource conflict in an SBFD implementation.
[0261] FIG. 19 illustrates an example of UE behavior with respect to DL / UL conflict, according to an implementation of the present disclosure. Due to the half-duplex constraint, the UE may continue receiving DL transmission and may not send a NACK, except in the last location, if the NACK transmission overlaps in the time domain with the DL transmission. In some implementations, in a typical SBFD configuration, the UE is not expected to receive both DL and UL scheduling overlapped in the time domain due to the half-duplex constraint for the UE. However, improved solutions of rateless coding, where only an ACK is needed to stop further transmission, may be used as described below.
[0262] 1. If a UE receives a DL PDSCH scheduling that overlaps with a UL UCI transmission in the time domain in an SBFD symbol or with a gap smaller than the UE UL / DL switching time, the UE skips the UL UCI transmission if it is a NACK. The UE transmits UL UCI if it is an ACK and skips DL reception.
[0263] 2. Once the UE sends the ACK, it skips the next ACK / NACK transmission.
[0264] 3. If the UE does not have enough preparation time, it skips the ACK / NACK.
[0265] 4. The UE expects the prescheduled retransmission TO to be canceled if the starting symbols of the retransmission arrive later than the ACK timing including the BS processing time. If another UL transmission overlaps with the retransmission, the UE can perform the UL transmission and skip the DL reception.
[0266] 5. Coding design may need to consider the state associated with no NACK transmission in the ACK / NACK TO.
[0267] The above-mentioned techniques may not be limited to progressive rateless coding transmission but can also be used for DL / UL conflict in an SBFD scenario.
[0268] In accordance with various implementations of the present disclosure, the progressive rateless coding transmission is also applicable to UL transmission by the UE in a PUSCH. If an UL transmission is performed, the BS can schedule the UL progressive rateless coding transmission in a single DCI. Most of the signaling and mechanism described for DL transmission is also applicable to UL except for the HARQ feedback TO which is different from that described for DL transmissions. In the UL, the BS may not be required to send any HARQ feedback to the UE as the retransmission is scheduled and controlled by the BS. In this case, the BS may only send HARQ feedback with an ACK if the BS needs to terminate early further retransmissions from the UE. In this case, the BS can send a HARQ feedback (e.g., the ACK) for early termination in a DCI, and the HARQ feedback resources do not need to be indicated in the scheduling DCI.
[0269] Although the disclosure is motivated by the progressive rateless coding scheme where each retransmission may add additional small redundancies to the previous transmission, the signaling and DCI format may be also applicable to general retransmission or repetition scheduling. In this case, each repetition or retransmission may still use RV with a fixed starting point. However, a single DCI can still schedule multiple retransmissions in advance with potential HARQ feedback reception, and the BS can early terminate or stop further retransmissions if an ACK from the UE is received. It should be understood that in other implementations, the signaling and HARQ feedback timing of the present disclosure may also be applicable to other scenarios that are not necessarily progressive rateless coding.
[0270] In the present disclosure, the terms “a” , “an” and “one” are defined to mean “at least one” , that is, these terms do not exclude a plural number of items, unless stated otherwise.
[0271] In the present disclosure, terms such as “substantially” , “generally” and “about” , which modify a value, condition or characteristic of a feature of an exemplary embodiment, should be understood to mean that the value, condition or characteristic is defined within tolerances that are acceptable for the proper operation of this exemplary embodiment for its intended application.
[0272] In the present disclosure, unless stated otherwise, the terms “connected” and “coupled” , and derivatives and variants thereof, refer herein to any structural or functional connection or coupling, either direct or indirect, between two or more elements. For example, the connection or coupling between the elements can be acoustical, mechanical, optical, electrical, thermal, logical, or any combinations thereof.
[0273] In the present disclosure, expressions such as “match” , “matching” and “matched” , including variants and derivatives thereof, are intended to refer herein to a condition in which two or more elements are either the same or within some predetermined tolerance of each other. That is, these terms are meant to encompass not only “exactly” or “identically” matching the two elements but also “substantially” , “approximately” or “subjectively” matching the two or more elements, as well as providing a higher or best match among a plurality of matching possibilities.
[0274] In the present disclosure, the expression “based on” is intended to mean “based at least partly on” , that is, this expression can mean “based solely on” or “based partially on” , and so should not be interpreted in a limited manner. More particularly, the expression “based on” could also be understood as meaning “depending on” , “representative of” , “indicative of” , “associated with” or similar expressions.
[0275] In the present disclosure, the terms “system” and “network” may be used interchangeably in embodiments of this application. “At least one” means one or more, and “aplurality of” means two or more. The term “and / or” describes an association relationship of associated objects, and indicates that three relationships may exist. For example, A and / or B may indicate the following three cases: Only A exists, both A and B exist, and only B exists, where A and B may be singular or plural. The character “ / ” usually indicates an “or” relationship between associated objects. “At least one of the following items (pieces) ” or a similar expression thereof indicates any combination of these items, including a single item (piece) or any combination of a plurality of items (pieces) . For example, “at least one of A, B, or C” includes A, B, C, A and B, A and C, B and C, or A, B, and C, and “at least one of A, B, and C” may also be understood as including A, B, C, A and B, A and C, B and C, or A, B, and C. In addition, unless otherwise specified, ordinal numbers such as “first” and “second” in embodiments of this application are used to distinguish between a plurality of objects, and are not used to limit a sequence, a time sequence, priorities, or importance of the plurality of objects.
[0276] A person skilled in the art should understand that embodiments of this application may be provided as a method, an apparatus (or system) , computer-readable storage medium, or a computer program product. Therefore, this application may use a form of a hardware-only embodiment, a software-only embodiment, or an embodiment with a combination of software and hardware. Moreover, this application may use a form of a computer program product that is implemented on one or more computer-usable storage media (including but not limited to a disk memory, an optical memory, and the like) that include computer-usable program code.
[0277] This application is described with reference to the flowcharts and / or block diagrams of the method, the device (system) , and the computer program product according to this application. It should be understood that computer program instructions may be used to implement each process and / or each block in the flowcharts and / or the block diagrams and a combination of a process and / or a block in the flowcharts and / or the block diagrams. The computer program instructions may be provided for a general-purpose computer, a dedicated computer, an embedded processor, or a processor of a programmable data processing device, and enable a machine to execute the instructions. When executed by the computer or the processor of the programmable data processing device, the instructions cause an apparatus to implement specific functions as described in one or more procedures in the flowcharts and / or one or more blocks in the block diagrams.
[0278] The computer program instructions may alternatively be stored in a computer-readable memory that can indicate a computer or another programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate an artifact that includes an instruction apparatus. The instruction apparatus implements a specific function in one or more procedures in the flowcharts and / or in one or more blocks in the block diagrams.
[0279] The computer program instructions may alternatively be loaded onto a computer or another programmable data processing device, so that a series of operations and steps are performed on the computer or the other programmable data processing device, so that computer-implemented processing is generated. Therefore, the instructions executed on the computer or the other programmable data processing device provide steps for implementing specific functions as described in one or more procedures in the flowcharts and / or one or more blocks in the block diagrams.
[0280] It is clear that a person skilled in the art can make various modifications and variations to this application without departing from the scope of this application. This application is intended to cover these modifications and variations of this application provided that they fall within the scope of protection defined by the following claims and their equivalent technologies.
[0281] Acronyms, Abbreviations, and Initialisms
Claims
1.A method comprising:transmitting signaling indicating a frequency location of a resource for uplink control information (UCI) transmission in one or more symbols, wherein each symbol of the one or more symbols comprises a first frequency subband for uplink (UL) transmission and a second frequency subband for downlink (DL) transmission, and the frequency location of the resource for the UCI transmission is in the first frequency subband.2.The method of claim 1, wherein the frequency location of the resource for the UCI transmission is indicated as a frequency offset.3.The method of claim 1 or claim 2, wherein transmitting the signaling comprises:transmitting the signaling using higher layer signaling.4.The method of claim 1 or claim 2, wherein transmitting the signaling comprises:transmitting the signaling using downlink control information (DCI) .5.The method of claim 4, wherein the DCI overwrites a previous resource configuration for the UCI indicated using previous higher layer signaling.6.The method of any one of claims 1 to 5, wherein the signaling further indicates a resource for at least one of an initial Hybrid Automatic Repeat Request (HARQ) transmission, a time offset between the initial HARQ transmission and a respective HARQ feedback, or a periodicity of the respective HARQ feedback.7.The method of any one of claims 1 to 6, wherein the signaling indicates resources for transmission of at least one of a Scheduling Request (SR) or a Channel State Information (CSI) in the one or more symbols.8.The method of any one of claims 1 to 7, wherein the signaling comprises a physical uplink control channel (PUCCH) configuration, the PUCCH configuration comprises a mapping type for a starting symbol of the resource scheduled for the UCI, and the starting symbol is configured through higher layer signaling or DCI.9.The method of claim 8, wherein the mapping type is a first mapping type, and a location of the starting symbol with respect to a slot boundary is configured using higher layer signaling.10.A method comprising:receiving signaling indicating a frequency location of a resource for uplink control information (UCI) transmission in one or more symbols, wherein each symbol of the one or more symbols comprises a first frequency subband for uplink (UL) transmission and a second frequency subband for downlink (DL) transmission, and the frequency location of the resource for the UCI transmission is in the first frequency subband.11.The method of claim 10, wherein the frequency location of the resource for the UCI transmission is indicated as a frequency offset.12.The method of claim 10 or claim 11, wherein receiving the signaling comprises:receiving the signaling using higher layer signaling.13.The method of claim 10 or claim 11, wherein receiving the signaling comprises:receiving the signaling using downlink control information (DCI) .14.The method of claim 13, wherein the DCI overwrites a previous resource configuration for the UCI indicated using previous higher layer signaling.15.The method of any one of claims 10 to 14, wherein the signaling further indicates a resource for at least one of an initial Hybrid Automatic Repeat Request (HARQ) transmission, a time offset between the initial HARQ transmission and a respective HARQ feedback, or a periodicity of the respective HARQ feedback.16.The method of any one of claims 10 to 15, wherein the signaling indicates resources for transmission of at least one of a Scheduling Request (SR) or Channel State Information (CSI) in the one or more symbols.17.The method of any one of claims 10 to 16, wherein the signaling comprises a physical uplink control channel (PUCCH) configuration, the PUCCH configuration comprises a mapping type for a starting symbol of the resource scheduled for the UCI, and the starting symbol is configured through higher layer signaling or DCI.18.The method of claim 17, wherein the mapping type is a first mapping type, and a location of the starting symbol with respect to a slot boundary is configured using higher layer signaling.19.The method of any one of claims 10 to 18, further comprising:receiving a physical downlink shared channel (PDSCH) scheduling that conflicts with uplink control information (UCI) in the time domain.20.The method of claim 19, comprising skipping the UCI, wherein the UCI comprises a negative acknowledgement (NACK) .21.The method of claim 19, comprising transmitting the UCI and skipping DL reception, wherein the UCI comprises an acknowledgement (ACK) .22.A communication apparatus, configured to perform the method of any one of claims 1 to 9 or claims 10 to 21.23.The communication apparatus of claim 22, comprising:a transmitting unit configured to transmit signaling indicating a frequency location of a resource for uplink control information (UCI) transmission in one or more symbols, wherein each symbol of the one or more symbols comprises a first frequency subband for uplink (UL) transmission and a second frequency subband for downlink (DL) transmission, and the frequency location of the resource for the UCI transmission is in the first frequency subband.24.The communication apparatus of claim 22, comprising:a receiving unit configured to receive signaling indicating a frequency location of a resource for uplink control information (UCI) transmission in one or more symbols, wherein each symbol of the one or more symbols comprises a first frequency subband for uplink (UL) transmission and a second frequency subband for downlink (DL) transmission, and the frequency location of the resource for the UCI transmission is in the first frequency subband.25.The communication apparatus of claim 22, comprising:one or more processors; andan interface circuit configured to transmit signaling indicating a frequency location of a resource for uplink control information (UCI) transmission in one or more symbols, wherein each symbol of the one or more symbols comprises a first frequency subband for uplink (UL) transmission and a second frequency subband for downlink (DL) transmission, and the frequency location of the resource for the UCI transmission is in the first frequency subband.26.The communication apparatus of claim 22, comprising:one or more processors; andan interface circuit configured to receive signaling indicating a frequency location of a resource for uplink control information (UCI) transmission in one or more symbols, wherein each symbol of the one or more symbols comprises a first frequency subband for uplink (UL) transmission and a second frequency subband for downlink (DL) transmission, and the frequency location of the resource for the UCI transmission is in the first frequency subband.27.The communication apparatus of claim 25 or claim 26, wherein the interface circuit comprises one or more transceivers.28.An apparatus comprising:one or more processors; andone or more memories storing instructions which, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1 to 9 or claims 10 to 21.29.A communication system, wherein the communication system comprises a first communication apparatus configured to perform the method of any one of claims 1 to 9 and a second communication apparatus configured to perform the method of any one of claims 10 to 21.30.A non-transitory computer-readable storage medium having instructions stored thereon which, when executed by an apparatus, cause the apparatus to perform the method of any one of claims 1 to 9 or claims 10 to 21.31.A computer program product storing instructions which, when executed, cause an apparatus to perform the method of any one of claims 1 to 9 or claims 10 to 21.
Citation Information
Patent Citations
Physical uplink control channel (PUCCH) configuration for new-radio-spectrum sharing (NR-SS)
CN111418245A
Uplink control information multiplexing for physical uplink shared channel repetitions in full duplex
US20230284212A1
Method and device for transmitting uplink feedback information
WO2017152664A1
Method and device for transmitting uplink in wireless network
WO2024030009A1