Physical uplink control channel format for single uplink operation in dual connectivity mode with time division duplex primary cell
By using the equal-to-allocated index and DAI field value in the downlink control information in the dual-connection mode of the TDD main cell, the PUCCH format and resources are determined, and the concurrent transmission of HARQ feedback and additional control information in a single uplink operation is solved. The problem of improving communication efficiency and flexibility.
Patent Information
- Application Number
- CN202080070095.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-09-01
- Filing Date
- 2020-09-02
- Publication Date
- 2024-12-20
- Estimated Expiration
- 2040-09-02
AI Technical Summary
In dual-connection modes with time division duplex (TDD) primary cells, prior art is difficult to effectively determine physical uplink control channel (PUCCH) formats and resources for single uplink operation, especially in hybrid automatic retransmission In the case of requesting (HARQ) feedback and adding line control information to be sent concurrently.
PUCCH format and resources are determined by using downlink allocation index equal to one in the downlink control information, combined with the DAI field value, the appropriate PUCCH format and resources are selected to support HARQ feedback and concurrent transmission of the attached line control information. .
It realizes a single uplink operation in the TDD PCell environment, improves the flexibility and efficiency of PUCCH format and resources, supports HARQ feedback and concurrent transmission of attached line control information, and enhances the communication capabilities of the system.
Smart Images

Figure CN114503500B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. Provisional Patent Application Serial No. 62 / 910,159, filed on October 3, 2019, entitled “PHYSICAL UPLINK CONTROLCHANNEL FORMAT FOR SINGLE UPLINK OPERATION IN DUAL CONNECTIVITY MODE WITH TIME DIVISION DUPLEXING PRIMARY CELL,” and U.S. Non-Provisional Patent Application Serial No. 17 / 009,152, filed on September 1, 2020, entitled “PHYSICAL UPLINK CONTROL CHANNEL FORMAT FOR SINGLE UPLINK OPERATION IN DUAL CONNECTIVITY MODE WITH TIME DIVISION DUPLEXING PRIMARY CELL,” which are hereby expressly incorporated herein by reference. Technical Field
[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for determining a physical uplink control channel (PUCCH) format for single uplink operation in dual connectivity mode with a time division duplex (TDD) primary cell. Background Art
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
[0005] A wireless network may include multiple base stations (BSs) that may support communications for multiple user equipment (UEs). A user equipment (UE) may communicate with a base station (BS) via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a BS to a UE, while an uplink (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, etc.
[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate in municipal, national, regional and even global ranges. New Radio (NR) (which may also be referred to as 5G) is an enhanced set of LTE mobile standards promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL) and supporting beamforming, multiple input multiple output (MIMO) antenna technology. Further improvements in LTE, NR and other radio access technologies and telecommunication standards that adopt these technologies are still useful. Summary of the invention
[0007] In some aspects, a method of wireless communication performed by a user equipment (UE) may include: determining a physical uplink control channel (PUCCH) format and PUCCH resources to be used to concurrently send hybrid automatic repeat request (HARQ) feedback and additional uplink control information based at least in part on downlink control information including a downlink allocation index equal to one; and using the PUCCH format and the PUCCH resources to send one or more of the HARQ feedback or the additional uplink control information.
[0008] In some aspects, a UE for wireless communication may include a memory and one or more processors operably coupled to the memory. The memory and the one or more processors may be configured to: determine a PUCCH format and a PUCCH resource to be used for concurrently sending HARQ feedback and additional uplink control information based at least in part on downlink control information including a downlink allocation index equal to one; and use the PUCCH format and the PUCCH resource to send one or more of the HARQ feedback or the additional uplink control information.
[0009] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a UE, may cause the one or more processors to: determine a PUCCH format and a PUCCH resource to be used to concurrently send HARQ feedback and additional uplink control information based at least in part on downlink control information including a downlink allocation index equal to one; and send one or more of the HARQ feedback or the additional uplink control information using the PUCCH format and the PUCCH resource.
[0010] In some aspects, an apparatus for wireless communication may include: a component for determining a PUCCH format and a PUCCH resource to be used to concurrently send HARQ feedback and additional uplink control information based at least in part on downlink control information including a downlink allocation index equal to one; and a component for sending one or more of the HARQ feedback or the additional uplink control information using the PUCCH format and the PUCCH resource.
[0011] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as substantially described herein with reference to and as shown in the accompanying drawings and description.
[0012] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be readily used as a basis for modifying or designing other structures for performing the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein (both their organization and methods of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for illustrative and descriptive purposes and not as a definition of limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] In order that the above-mentioned features of the present disclosure may be understood in detail, a more specific description briefly summarized above may be obtained by reference to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and therefore should not be considered as limiting the scope thereof, as the description may allow for other equivalent aspects. The same reference numerals in different drawings may represent the same or similar elements.
[0014] Figure 1 is a diagram illustrating an example of a wireless network according to various aspects of the present disclosure.
[0015] Figure 2 is a diagram illustrating an example of a base station and a UE in communication in a wireless network according to various aspects of the present disclosure.
[0016] Figure 3A is a diagram illustrating an example of a frame structure in a wireless communication network according to various aspects of the present disclosure.
[0017] Figure 3B is a diagram illustrating an example synchronous communication hierarchy in a wireless communication network in accordance with various aspects of the present disclosure.
[0018] Figure 4 is a diagram illustrating an example slot format with a normal cyclic prefix in accordance with various aspects of the present disclosure.
[0019] Figure 5 is a diagram illustrating an example of downlink-dominant time slots according to various aspects of the present disclosure.
[0020] Figure 6 is a diagram illustrating an example of uplink-dominant time slots according to various aspects of the present disclosure.
[0021] Figure 7 is a diagram illustrating an example implementation of determining a physical uplink control channel format for single uplink operation in dual connectivity mode with a time division duplex primary cell in accordance with various aspects of the present disclosure.
[0022] Figure 8 is a diagram illustrating example processes performed, for example, by a UE according to various aspects of the present disclosure. DETAILED DESCRIPTION
[0023] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. More specifically, these aspects are provided so that the present disclosure will become thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. Based on the teachings herein, it should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether independent of any aspect of the present disclosure or implemented in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement a device or a method can be practiced. In addition, the scope of the present disclosure is intended to cover such a device or method practiced using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.
[0024] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.
[0025] It should be noted that although various aspects may be described herein using terminology generally associated with 5G or NR radio access technologies (RATs), various aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and / or RATs beyond 5G (e.g., 6G).
[0026] Figure 1 is a diagram showing an example of a wireless network 100 according to various aspects of the present disclosure. The wireless network 100 may be or may include elements of a 5G (NR) network, an LTE network, etc. The wireless network 100 may include a plurality of base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with a user equipment (UE) and may also be referred to as an NRBS, a Node B, a gNB, a 5G Node B (NB), an access point, a transmit receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.
[0027] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access to UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably herein.
[0028] In some aspects, the cell may not necessarily be fixed, and the geographic area of the cell may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces such as direct physical connections, virtual networks, etc. using any suitable transport network.
[0029] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and send transmissions of data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, a relay BS 110d may communicate with a macro BS 110a and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay BS may also be referred to as a relay station, a relay base station, a relay, or the like.
[0030] The wireless network 100 may be a heterogeneous network including different types of BSs, such as a macro BS, a pico BS, a femto BS, a relay BS, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).
[0031] A network controller 130 may be coupled to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other (eg, directly or indirectly) via a wireless or wired backhaul.
[0032] UE 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be fixed or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device / medical equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), an entertainment device (e.g., a music or video device, or a satellite radio, etc.), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.
[0033] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide a connection to, for example, a network (e.g., a wide area network such as the Internet or a cellular network) or provide a connection to a network via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120 (such as a processor component, a memory component, etc.). In some aspects, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, electrically coupled, etc.
[0034] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific RAT and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.
[0035] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary for communicating with each other). For example, UE 120 may use peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (e.g., which may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, etc.), mesh network, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.
[0036] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 can communicate using an operating band having a first frequency range (FR1), which can span from 410 MHz to 7.125 GHz, and / or can communicate using an operating band having a second frequency range (FR2), which can span from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as a "sub-6 GHz" band. Similarly, FR2 is often referred to as a "millimeter wave" band, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz), which is identified as a "millimeter wave" band by the International Telecommunication Union (ITU). Thus, unless otherwise specifically stated, it should be understood that the terms "sub-6 GHz" and the like, if used herein, may broadly refer to frequencies less than 6 GHz, frequencies within FR1, or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specifically stated, it should be understood that the terms "millimeter wave" and the like, if used herein, may broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). It is contemplated that the frequencies included in FR1 and FR2 may be modified, and the techniques described herein may be applicable to those modified frequency ranges.
[0037] As indicated above, Figure 1 are provided as examples. Other examples may differ from those described in Figure 1 An example of description.
[0038] Figure 2 2 is a diagram illustrating an example 200 of a base station 110 and a UE 120 in communication in a wireless network in accordance with various aspects of the present disclosure. The base station 110 may be equipped with T antennas 234a through 234t, and the UE 120 may be equipped with R antennas 252a through 252r, where in general T≥1 and R≥1.
[0039] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process data for each UE (e.g., encode and modulate the data) based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), etc.) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and may provide T output symbol streams to T modulators (MOD) 232a through 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process the output sample stream (e.g., convert it to analog, amplify it, filter it, and upconvert it) to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.
[0040] At UE 120, antennas 252a to 252r may receive downlink signals from base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition the received signal (e.g., filter, amplify, downconvert, and digitize it) to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 258 may process the detected symbols (e.g., demodulate and decode them), provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in housing 284.
[0041] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.
[0042] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.) and transmitted to the base station 110. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receive processors 258, transmit processors 264, and / or TX MIMO processors 266. The transceiver may be used by a processor (eg, controller / processor 280 ) and memory 282 to perform aspects of any of the methods described herein.
[0043] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the modulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule the UE 120 for downlink and / or uplink communication. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of the antenna 234, the modulator and / or demodulator 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and / or the TX MIMO processor 230. The transceiver may be used by a processor (eg, controller / processor 240 ) and memory 242 to perform aspects of any of the methods described herein.
[0044] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the base station 110 may perform one or more techniques associated with determining a physical uplink control channel (PUCCH) format for a single uplink operation in dual connectivity mode with a time division duplex (TDD) primary cell, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component may perform or direct e.g. Figure 8 The operations of process 800 and / or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, interpretation, etc.), may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example, Figure 8 The process 800 of and / or operations of other processes as described herein. In some aspects, executing instructions may include running instructions, converting instructions, compiling instructions, interpreting instructions, etc.
[0045] In some aspects, the UE 120 may include means for determining a PUCCH format and a PUCCH resource to be used to concurrently send hybrid automatic repeat request (HARQ) feedback and additional uplink control information based at least in part on the downlink control information including a downlink allocation index equal to one; means for sending one or more of the HARQ feedback or the additional uplink control information using the PUCCH format and the PUCCH resource; and so on. In some aspects, such means may include combining Figure 2 One or more components of UE 120 are depicted, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.
[0046] As indicated above, Figure 2 are provided as examples. Other examples may differ from those described in Figure 2 An example of description.
[0047] Figure 3A An example frame structure 300 for frequency division duplex (FDD) in a telecommunication system (e.g., NR) is shown. The transmission timeline for each of the downlink and uplink may be segmented into units of radio frames (sometimes referred to as frames). Each radio frame may have a predetermined duration (e.g., 10 milliseconds (ms)) and may be segmented into a set of Z (Z ≥ 1) subframes (e.g., with indices 0 to Z-1). Each subframe may have a predetermined duration (e.g., 1 ms) and may include a set of time slots (e.g., in Figure 3A The 2 m time slots, where m is a numerology for transmission, such as 0, 1, 2, 3, 4, etc.). Each time slot may include a set of L symbol periods. For example, each time slot may include fourteen symbol periods (e.g., Figure 3A In some aspects, the scheduling unit for FDD may be frame-based, subframe-based, slot-based, symbol-based, etc. ... subframe-based, subframe-based, slot-based, symbol-based, etc. In some aspects, the subframe-based, subframe-
[0048] Although some techniques are described herein in conjunction with frames, subframes, time slots, etc., these techniques may be equally applicable to other types of wireless communication structures, which may be referred to using terms other than "frames," "subframes," "time slots," etc. in 5G NR. In some aspects, a "wireless communication structure" may refer to a periodic, time-bounded communication unit defined by a wireless communication standard and / or protocol. Additionally or alternatively, a wireless communication structure may be used in conjunction with a wireless communication standard and / or protocol. Figure 3A The wireless communication structures shown are different wireless communication structures.
[0049] In some telecommunications (e.g., NR), a base station may send synchronization signals. For example, a base station may send a primary synchronization signal (PSS), a secondary synchronization signal (SSS), etc. on the downlink for each cell supported by the base station. The UE may use the PSS and SSS for cell search and acquisition. For example, the UE may use the PSS to determine symbol timing, and the UE may use the SSS to determine the physical cell identifier associated with the base station and the frame timing. The base station may also send a physical broadcast channel (PBCH). The PBCH may carry some system information, such as system information that supports initial access of the UE.
[0050] In some aspects, the base station may transmit the PSS, SSS, and / or PBCH according to a synchronization communication hierarchy (e.g., a synchronization signal (SS) hierarchy) including multiple synchronization communications (e.g., synchronization signal (SS) blocks), as described below in conjunction with Figure 3B Describing.
[0051] Figure 3B is a diagram showing an example SS hierarchy, which is an example of a synchronous communication hierarchy. Figure 3B As shown, the SS hierarchy may include an SS burst set, which may include a plurality of SS bursts (identified as SS burst 0 to SS burst B-1, where B is the maximum number of repetitions of the SS burst that may be sent by the base station). As further shown, each SS burst may include one or more SS blocks (identified as SS block 0 to SS block (b max_SS -1), where b max_SS -1 is the maximum number of SS blocks that can be carried by an SS burst). In some aspects, different SS blocks can be beamformed in different ways. Figure 3B As shown, the SS burst set may be sent by the wireless node periodically, such as once every X milliseconds. In some aspects, the SS burst set may have a fixed or dynamic length. Figure 3B is shown as Y milliseconds.
[0052] Figure 3B The SS burst sets shown in are examples of synchronous communication sets, and other synchronous communication sets may be used in conjunction with the techniques described herein. Figure 3B The SS blocks shown in are examples of synchronous communications, and other synchronous communications may be used in conjunction with the techniques described herein.
[0053] In some aspects, an SS block includes resources that carry PSS, SSS, PBCH, and / or other synchronization signals (e.g., a third synchronization signal (TSS)) and / or synchronization channels. In some aspects, multiple SS blocks are included in an SS burst, and the PSS, SSS, and / or PBCH may be identical for each SS block across an SS burst. In some aspects, a single SS block may be included in an SS burst. In some aspects, an SS block may be at least four symbol periods in length, with each symbol carrying one or more of a PSS (e.g., occupying one symbol), a SSS (e.g., occupying one symbol), and / or a PBCH (e.g., occupying two symbols).
[0054] In some aspects, such as Figure 3B As shown, the symbols of the SS blocks are continuous. In some aspects, the symbols of the SS blocks are non-continuous. Similarly, in some aspects, one or more SS blocks of an SS burst may be sent in continuous radio resources (e.g., continuous symbol periods) during one or more time slots. Additionally or alternatively, one or more SS blocks of an SS burst may be sent in non-continuous radio resources.
[0055] In some aspects, the SS burst may have a burst periodicity, whereby the base station transmits the SS blocks of the SS burst according to the burst periodicity. In other words, the SS blocks may be repeated during each SS burst. In some aspects, the SS burst set may have a burst set periodicity, whereby the base station transmits the SS bursts in the SS burst set according to a fixed burst set periodicity. In other words, the SS burst may be repeated during each SS burst set.
[0056] The base station may send system information, such as system information blocks (SIBs), on a physical downlink shared channel (PDSCH) in certain time slots. The base station may send control information / data on a physical downlink control channel (PDCCH) in C symbol periods of a time slot, where B may be configurable for each time slot. The base station may send traffic data and / or other data on the PDSCH in the remaining symbol periods of each time slot.
[0057] As indicated above, Figure 3A and 3B Provided as an example. Other examples may differ from Figure 3A and 3B An example of description.
[0058] Figure 4An example slot format 400 with a normal cyclic prefix is shown. The available time-frequency resources may be partitioned into resource blocks. Each resource block may cover a set of subcarriers (e.g., 12 subcarriers) in a slot and may include multiple resource elements. Each resource element may cover a subcarrier in a symbol period (e.g., in time) and may be used to transmit a modulation symbol, which may be a real value or a complex value.
[0059] In some telecommunication systems (e.g., NR), an interlace structure may be used for each of the downlink and uplink of FDD. For example, Q interlaces indexed from 0 to Q–1 may be defined, where Q may be equal to 4, 6, 8, 10, or some other value. Each interlace may include time slots spaced apart by Q frames. Specifically, interlace q may include time slots q, q+Q, q+2Q, etc., where q∈{0,…,Q–1}.
[0060] A UE may be located within the coverage of multiple BSs. One of these BSs may be selected to serve the UE. The serving BS may be selected based at least in part on various criteria such as received signal strength, received signal quality, path loss, etc. The received signal quality may be quantified by a signal to noise and interference ratio (SNIR) or a reference signal received quality (RSRQ) or some other metric. The UE may operate in a dominant interference scenario, in which the UE may observe high interference from one or more interfering BSs.
[0061] Although aspects of the examples described herein may be associated with NR or 5G technology, aspects of the present disclosure may be applicable to other wireless communication systems. New Radio (NR) may refer to a radio configured to operate according to a new air interface (e.g., in addition to an air interface based on Orthogonal Frequency Division Multiple Access (OFDMA)) or a fixed transport layer (e.g., in addition to the Internet Protocol (IP)). In some aspects, NR may utilize OFDM with CP (referred to herein as Cyclic Prefix OFDM or CP-OFDM) and / or SC-FDM on the uplink, may utilize CP-OFDM on the downlink, and include support for half-duplex operation using time division duplex (TDD). In some aspects, NR may utilize OFDM with CP (referred to herein as CP-OFDM) and / or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-s-OFDM), for example, on the uplink, may utilize CP-OFDM on the downlink, and include support for operation using TDD for half-duplex operation. NR may include enhanced mobile broadband (eMBB) services for wide bandwidth (e.g., 80 megahertz (MHz) and higher), millimeter wave (mmW) for high carrier frequencies (e.g., 60 gigahertz (GHz)), massive MTC (mMTC) for non-backward compatible MTC technologies, and / or mission critical ultra-reliable low latency communication (URLLC) services.
[0062] In some aspects, a single component carrier bandwidth of 100 MHz may be supported. NR resource blocks may span 12 subcarriers with a subcarrier bandwidth of 60 or 120 kilohertz (kHz) in a 0.1 ms duration. Each radio frame may include 40 time slots and may have a length of 10 ms. Thus, each time slot may have a length of 0.25 ms. Each time slot may indicate a link direction (e.g., downlink (DL) or uplink (UL)) for data transmission, and the link direction for each time slot may be switched dynamically. Each time slot may include DL / UL data as well as DL / UL control data.
[0063] Beamforming can be supported and the beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. MIMO configuration in DL can support up to 8 transmit antennas, with multi-layer DL transmission of up to 8 streams and up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE can be supported. Aggregation of multiple cells with up to 8 serving cells can be supported. Alternatively, NR can support different air interfaces in addition to OFDM-based interfaces. NR networks can include entities such as central units or distributed units.
[0064] As indicated above, Figure 4are provided as examples. Other examples may differ from those described in Figure 4 An example of description.
[0065] Figure 5 5 is a diagram 500 illustrating an example of a DL-centric time slot or wireless communication structure. The DL-centric time slot may include a control portion 502. The control portion 502 may be present in an initial or beginning portion of the DL-centric time slot. The control portion 502 may include various scheduling information and / or control information corresponding to various portions of the DL-centric time slot. In some configurations, the control portion 502 may be a physical DL control channel (PDCCH), such as Figure 5 In some aspects, the control portion 502 may include legacy PDCCH information, shortened PDCCH (sPDCCH) information, a control format indicator (CFI) value (e.g., carried on a physical control format indicator channel (PCFICH)), one or more grants (e.g., downlink grant, uplink grant, etc.), etc.
[0066] The DL-based time slot may also include a DL data portion 504. The DL data portion 504 may sometimes be referred to as the payload of the DL-based time slot. The DL data portion 504 may include communication resources for communicating DL data from a scheduling entity (e.g., UE or BS) to a subordinate entity (e.g., UE). In some configurations, the DL data portion 504 may be a physical DL shared channel (PDSCH).
[0067] The DL-based time slot may also include an uplink short burst portion 506. The UL short burst portion 506 may sometimes be referred to as an uplink burst, an uplink burst portion, a shared UL burst, a short burst, an uplink short burst, a shared UL short burst, a shared UL short burst portion, and / or various other suitable terms. In some aspects, the UL short burst portion 506 may include one or more reference signals. Additionally or alternatively, the UL short burst portion 506 may include feedback information corresponding to various other portions of the DL-based time slot. For example, the UL short burst portion 506 may include feedback information corresponding to the control portion 502 and / or the DL data portion 504. Non-limiting examples of information that may be included in the UL short burst portion 506 include an ACK signal (e.g., PUCCH ACK, PUSCH ACK, immediate ACK), a NACK signal (e.g., PUCCH NACK, PUSCH NACK, immediate NACK), a scheduling request (SR), channel state information (CSI), a buffer status report (BSR), a HARQ indicator, a channel quality indicator (CQI), a sounding reference signal (SRS), a demodulation reference signal (DMRS), PUSCH data, and / or various other suitable types of information. The UL short burst portion 506 may include additional or alternative information, such as information related to a random access channel (RACH) procedure, a scheduling request, and various other suitable types of information.
[0068] like Figure 5 As shown in , the end of the DL data portion 504 can be separated in time from the beginning of the UL short burst portion 506. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terms. This separation provides time for switching from DL communication (e.g., a reception operation performed by a subordinate entity (e.g., a UE)) to UL communication (e.g., a transmission performed by a subordinate entity (e.g., a UE)). The foregoing is an example of a DL-based wireless communication structure, and there may be alternative structures with similar features without departing from the aspects described herein.
[0069] As indicated above, Figure 5 are provided as examples. Other examples may differ from those described in Figure 5 An example of description.
[0070] Figure 6 600 is a diagram illustrating an example of an uplink-centric timeslot or wireless communication structure. A UL-centric timeslot may include a control portion 602. The control portion 602 may be present in an initial or beginning portion of a UL-centric timeslot. Figure 6 The control portion 602 in the embodiment may be similar to the above reference Figure 5The control portion 502 described. The UL-based time slot may also include an uplink long burst portion 604. The UL long burst portion 604 may sometimes be referred to as the payload of the UL-based time slot. The "UL portion" may refer to communication resources used to communicate UL data from a subordinate entity (e.g., a UE) to a scheduling entity (e.g., a UE or a BS). In some configurations, the control portion 602 may be a physical DL control channel (PDCCH).
[0071] like Figure 6 As shown in , the end of the control portion 602 can be separated in time from the beginning of the UL long burst portion 604. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terms. The separation provides time for switching from DL communication (e.g., reception operations performed by the scheduling entity) to UL communication (e.g., transmissions performed by the scheduling entity).
[0072] The UL-dominant time slot may also include an uplink short burst portion 606 . Figure 6 The UL short burst portion 606 in the above reference may be similar to Figure 5 The UL short burst portion 506 described above may include the above combination Figure 5 The foregoing is one example of an uplink-based wireless communication structure, and alternative structures with similar features may exist without departing from the aspects described herein.
[0073] In one example, a wireless communication structure (such as a frame) may include both UL-based time slots and DL-based time slots. In this example, the ratio of UL-based time slots to DL-based time slots in a frame may be dynamically adjusted based at least in part on the amount of UL data and the amount of DL data sent. For example, if there is more UL data, the ratio of UL-based time slots to DL-based time slots may be increased. Conversely, if there is more DL data, the ratio of UL-based time slots to DL-based time slots may be reduced.
[0074] As indicated above, Figure 6 are provided as examples. Other examples may differ from those described in Figure 6 An example of description.
[0075] Dual connectivity typically enables a UE to communicate using two or more radio access technologies (RATs). For example, a dual connectivity configuration is between an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) (such as 4G / LTE) and an NR network (such as 5G / NR), commonly referred to as E-UTRAN-NR Dual Connectivity (EN-DC). For a UE communicating according to an EN-DC configuration, data can be received on both a 4G / LTE connection and a 5G / NR connection, although other configurations may be used. These connections are sometimes referred to as "legs". In some cases, the primary cell (PCell) and secondary cell (SCell) for EN-DC may have different component carrier configurations. For example, 3GPP Release 15 includes support for PCells with a frequency division duplex (FDD) configuration, and this support is extended to PCells with a time division duplex (TDD) configuration in 3GPP Release 16. In the latter case, EN-DC can be associated with a single uplink configuration, where the TDD PCell and SCell follow a time division multiplexing (TDM) configuration, whereby the UE can only perform uplink transmissions on one uplink carrier at a time (e.g., in a specific symbol or time slot). Accordingly, in such a case, the UE can switch between communications via a 4G / LTE connection and a 5G / NR connection in a TDM manner.
[0076] Typically, because the PCell and SCell used for EN-DC may have different component carrier configurations, the PUCCH format and / or PUCCH resources used to send uplink control information may need to be appropriately configured (e.g., to take into account timing constraints due to coexistence of 4G / LTE and 5G / NR or due to other reasons). For example, in some cases, the uplink control information may include hybrid automatic repeat request (HARQ) feedback, in which the UE provides feedback to a transmitter (e.g., a base station) to indicate whether the UE has received certain transmissions (e.g., the UE may provide HARQ feedback that indicates an acknowledgment (ACK) value when the UE successfully receives a transmission, or a negative ACK (NACK) value when the UE does not receive a transmission or the transmission is not successfully received). In addition, in some cases, the uplink control information may include scheduling requests, periodic channel state information (P-CSI), and the like.
[0077] In legacy LTE networks, various techniques define UE behavior to implicitly determine the PUCCH format and / or PUCCH resources to be used to send uplink control information. For example, in legacy LTE networks, PUCCH resources for PUCCH formats 3, 4, or 5 are typically indicated by the ACK / NACK resource indicator (ARI) field. However, in some cases, the ARI field is not explicitly present in the downlink allocation. In contrast, if the UE receives a PDCCH that schedules a PDSCH on a SCell and / or a PDCCH that includes downlink control information (DCI) with a downlink allocation index (DAI) field greater than one (1), the transmit power control (TPC) field in the DCI is interpreted as the ARI field. However, if the UE does not receive a DCI with a DAI field greater than one (e.g., the DAI field is equal to zero or one), the UE may use PUCCH formats 1a or 1b to send HARQ feedback. In such cases, the PUCCH resources may be derived using an equation that utilizes the first control channel element (CCE) index on the detected PDCCH carrying the downlink assignment.
[0078] However, for single uplink operation in EN-DC with TDD PCell, the UE is configured with a downlink-reference uplink-downlink configuration. In such cases, single uplink operation in EN-DC with TDD PCell typically supports PUCCH formats 3, 4, and 5, but does not support PUCCH fallback operation based on implicit resource indication (e.g., interpreting the TPC field as an ARI field). Accordingly, for single uplink operation in EN-DC with TDD PCell, in the case where the DAI field has a value equal to one (1) (e.g., in the case where the UE has only one ACK / NACK bit or two ACK / NACK bits for one PDSCH), the techniques for determining the PUCCH format and PUCCH resources to be used for sending uplink control information suffer from various deficiencies.
[0079] For example, when the UE receives a PDCCH with a DAI field equal to one, one option for determining the PUCCH format and PUCCH resources for sending HARQ feedback may be to use only PUCCH formats 3, 4, and 5. In this case, the PUCCH format 3 resources corresponding to the ARI field with a value of '00' are used as the default value of the PUCCH resources, and no PUCCH resources are reserved for semi-persistent scheduling (SPS) PDSCH. Additionally or alternatively, the PUCCH format 3 resources may be configured by a higher layer (e.g., a radio resource control (RRC) layer), and in this case, the PUCCH resources may be different from the default resources associated with the ARI field '00'. Furthermore, when the UE receives a PDCCH with a DAI field equal to one, another option for determining the PUCCH format and PUCCH resources for sending HARQ feedback may be to use explicit PUCCH format 1a or 1b resources for HARQ feedback transmission. In this case, PUCCH resources for the SPSPDSCH can be reserved for the UE in a manner similar to legacy LTE networks, and when the UE receives a PDCCH with a DAI field equal to one, PUCCH format 1b with channel selection is used. Otherwise, if the DAI field is greater than one, PUCCH formats 3, 4, or 5 can be used. However, these options do not typically consider situations where there may be additional uplink control information to be sent concurrently with the HARQ feedback. For example, in legacy LTE networks, PUCCH format 1 is typically used to send scheduling requests, and PUCCH format 2 is typically used to send CSI feedback. Accordingly, existing options for determining PUCCH formats and PUCCH resources in EN-DC typically do not specify how to multiplex HARQ feedback with additional uplink control information when the UE receives a DCI with a DAI field equal to one.
[0080] Some aspects described herein provide techniques and apparatus for determining the PUCCH format and PUCCH resources that the UE is to use to concurrently send HARQ feedback and additional uplink control information (e.g., scheduling request, P-CSI, etc.) when the UE receives a DCI including a DAI field having a value equal to one. For example, as described in further detail herein, the UE may receive a DCI including a DAI field from a base station, the DAI field indicating the number of PDSCH communications that the UE has received until the current DCI. For example, the UE may receive an indication of a counter DAI and / or a total DAI. The value of the counter DAI may represent the cumulative number of serving cell PDCCH monitoring opportunities in which there is PDSCH reception or SPS PDSCH release until the current serving cell and the current PDCCH monitoring opportunity. The total DAI value (when present) may represent the total number of serving cell PDCCH monitoring opportunity pairs in which there is PDSCH reception and SPS PDSCH release until the current PDCCH monitoring opportunity.
[0081] In some aspects, the UE may determine uplink control information to be sent in the next feedback opportunity, wherein the uplink control information may include HARQ feedback, scheduling request, P-CSI, etc. Accordingly, as described herein, the UE may use one or more techniques to determine the PUCCH format and PUCCH resources to be used to send uplink control information in the next feedback opportunity based at least in part on the value of the DAI field contained in the DCI and the uplink control information to be sent in the next feedback opportunity. For example, in the absence of HARQ feedback to be sent, in the presence of HARQ feedback to be sent and the value of the DAI field is greater than one, and in the presence of HARQ feedback to be sent and additional uplink control information when the value of the DAI field is equal to one, different techniques may be used to select the PUCCH format and / or PUCCH resources. In addition, depending on whether the additional uplink control information includes a scheduling request, a positive scheduling request, a negative scheduling request, P-CSI, etc., different techniques may be used to determine the PUCCH format and / or PUCCH resources to be used to send uplink control information. In this way, the UE can determine the appropriate PUCCH format and / or resources to use when sending uplink control information based at least in part on the value of the DAI field, the uplink control information to be sent, etc., which enables support for single uplink operation in EN-DC with TDD PCell.
[0082] Figure 7 is a diagram illustrating an example implementation 700 of determining a PUCCH format for single uplink operation in dual connectivity mode with a TDD PCell in accordance with various aspects of the present disclosure. Figure 7As shown in , example implementation 700 includes a UE in communication with a base station. In addition, as described herein, the UE can communicate with the base station according to an EN-DC configuration in which a single uplink is used (e.g., switching between LTE and NR in a TDM manner, whereby the UE can only transmit on the uplink carrier at a particular time).
[0083] like Figure 7 In and as shown by reference mark 705, the base station can send and the UE can receive a PDCCH including a DCI with a DAI field, which the base station can use to track downlink communications scheduled for UE 120. For example, in some aspects, the DAI field can be a counter that the base station increments for each downlink transmission scheduled for the UE. In some aspects, the value of the DAI field can be incremented in a frequency-first, time-second manner. In some aspects, the base station can indicate the last two bits (e.g., the two least significant bits) of the DAI field to the UE in the DCI (e.g., in a downlink grant). In addition or alternatively, the base station can indicate the total number of downlink communications scheduled for the UE in an uplink grant for HARQ feedback corresponding to the downlink communication (e.g., the total number of downlink communications scheduled in a bundling window that needs to be confirmed or negatively confirmed by the UE in the HARQ feedback corresponding to the uplink grant). In this way, the UE can use the value of the DAI field to resolve lost downlink grants and / or unsuccessfully received downlink communications. For example, the value of the DAI field may generally indicate how many downlink allocations the UE should have received so far within the current bundling window, which may enable the UE to detect lost downlink grants, unsuccessful downlink communications, etc. when the UE detects that the value of the DAI field is different from the number of correctly received downlink allocations.
[0084] like Figure 7 As further shown by reference numeral 710, the UE may determine uplink control information to be sent in the next feedback opportunity. For example, in some aspects, the uplink control information to be sent in the next feedback opportunity may include HARQ feedback (e.g., including one or more ACK and / or NACK messages for one or more downlink communications). Additionally or alternatively, the uplink control information may include a scheduling request (e.g., a physical layer message requesting uplink resources to send a physical uplink shared channel (PUSCH)), periodic channel state information (P-CSI), etc.
[0085] like Figure 7As further shown by reference mark 715, the UE may determine the PUCCH format and PUCCH resources to be used in the next feedback opportunity based at least in part on the uplink control information to be sent in the next feedback opportunity and the value of the DAI field in the DCI received from the base station. In some aspects, as mentioned above, the UE may determine the PUCCH format and PUCCH resources using different techniques depending on whether the uplink control information to be sent in the next feedback opportunity does not include HARQ feedback, includes HARQ feedback and the value of the DAI field is greater than one, includes HARQ feedback and the value of the DAI field is equal to one, etc. In addition, in some aspects, as described herein, the PUCCH format and PUCCH resources to be used in the next feedback opportunity may depend on whether the uplink control information includes additional uplink control information (e.g., scheduling request, P-CSI, etc.) that overlaps with the HARQ feedback (e.g., to be sent concurrently with the HARQ feedback).
[0086] For example, in some aspects, a UE may be associated with a first configuration in which uplink control information is sent using PUCCH format 3, 4, or 5 and PUCCH resources associated with an ARI field having a value of '00' (e.g., resources associated with PUCCH format 3 corresponding to an ARI field having a value of '00'). Additionally or alternatively, the UE may be associated with a second configuration in which the UE uses explicit PUCCH format 1a or 1b resources to fall back to RRC configured PUCCH format 1a or 1b resources. Additionally or alternatively, the UE may be associated with a third configuration in which uplink control information is sent using PUCCH format 3, 4, or 5 and PUCCH resources are configured by a higher layer (e.g., an RRC layer) that may be the same as or different from PUCCH resources associated with an ARI field having a value of '00'. Furthermore, in each of the first, second, and third configurations, the scheduling request may be configured according to PUCCH format 1, the P-CSI may be configured according to PUCCH format 2, and so on.
[0087] In some aspects, when the uplink control information to be sent in the next feedback opportunity includes a scheduling request and the UE is associated with the first configuration and / or the third configuration, the UE may determine the PUCCH format and PUCCH resources based at least in part on whether there is also a value of the HARQ feedback and / or DAI field to be sent in the next feedback opportunity. For example, in some aspects, if there is no HARQ feedback to be sent concurrently with the scheduling request, the UE may use PUCCH format 1 (e.g., a default configuration for scheduling requests) to send a scheduling request. In some aspects, in the case where the UE has HARQ feedback to be sent concurrently with the scheduling request and the value of the DAI field is greater than one, the UE may use PUCCH format 3, 4, or 5 to send HARQ feedback and scheduling requests, and may append one or more bits for scheduling requests after one or more bits for HARQ feedback in PUCCH format 3, 4, or 5.
[0088] In some aspects, in the case where the UE has HARQ feedback to be sent concurrently with a scheduling request and the value of the DAI field is equal to one, the UE may determine the PUCCH format and / or PUCCH resources to be used based at least in part on whether the scheduling request is a positive scheduling request (e.g., an indication that uplink resources are requested) or a negative scheduling request (e.g., an indication that uplink resources are not requested). For example, in the case where the scheduling request is a positive scheduling request, the UE may send HARQ feedback on resources reserved for the scheduling request using PUCCH format 1a or 1b, and in the case where the scheduling request is a negative scheduling request, the UE may multiplex one or more bits for the scheduling request with one or more bits for the HARQ feedback in PUCCH format 3 (e.g., because the resources reserved for the scheduling request do not need to be used). Alternatively, in some aspects, when the UE has HARQ feedback to be sent concurrently with a scheduling request and the value of the DAI field is equal to one, the one or more bits for the scheduling request may be appended after the one or more bits for the HARQ feedback in PUCCH format 3, 4, or 5, regardless of whether the scheduling request is positive or negative.
[0089] In some aspects, when the uplink control information to be sent includes a scheduling request and the UE is associated with the second configuration, if there is no HARQ feedback to be sent concurrently with the scheduling request, the UE may send the scheduling request using PUCCH format 1 (e.g., a default configuration for scheduling requests). Alternatively, in the case where the UE has HARQ feedback to be sent concurrently with the scheduling request and the value of the DAI field is greater than one, the UE may send the HARQ feedback and the scheduling request using PUCCH formats 3, 4, or 5, and one or more bits for the scheduling request may be appended after one or more bits for the HARQ feedback in PUCCH formats 3, 4, or 5 in a manner similar to that described above with respect to the first and third configurations.
[0090] In some aspects, in the case where the UE is associated with the second configuration and there is HARQ feedback sent concurrently with the scheduling request when the value of the DAI field is equal to one, the UE may determine the PUCCH format and / or PUCCH resource to be used based at least in part on the RRC configuration associated with the PUCCH1a or 1b resource. For example, in the case where the scheduling request is a positive scheduling request, the UE may send HARQ feedback on resources reserved for the scheduling request using PUCCH format 1a or 1b, and in the case where the scheduling request is a negative scheduling request, the UE may send HARQ feedback on RRC-configured resources for PUCCH format 1a or 1b using PUCCH format 1a or 1b. Alternatively, in some aspects, a channel selection process associated with PUCCH format 1b may be used, and HARQ feedback and scheduling requests may be sent using scheduling request resources and RRC-configured resources for PUCCH format 1a or 1b, regardless of whether the scheduling request is positive or negative.
[0091] In some aspects, when the uplink control information to be sent in the next feedback opportunity includes P-CSI, the UE may determine the PUCCH format and PUCCH resource based at least in part on whether there is also HARQ feedback to be sent in the next feedback opportunity and / or the value of the DAI field. For example, in some aspects, if there is no HARQ feedback to be sent concurrently with the P-CSI, the UE may send the P-CSI using PUCCH format 2 (e.g., a default configuration for P-CSI). In some aspects, in the case where the UE has HARQ feedback to be sent concurrently with the P-CSI and the value of the DAI field is greater than one, the P-CSI may be multiplexed with one or more bits for HARQ feedback using PUCCH formats 3, 4, or 5.
[0092] In some aspects, when the UE has HARQ feedback to be sent concurrently with P-CSI and the value of the DAI field is equal to one, the UE may determine the PUCCH format and / or PUCCH resources to use based at least in part on whether the UE is associated with a first configuration (e.g., using PUCCH format 3, 4, or 5 and PUCCH resources associated with an ARI field having a value of '00'), a second configuration (e.g., using explicit PUCCH format 1a or 1b resources to fall back to RRC configured PUCCH format 1a or 1b resources), or a third configuration (e.g., using PUCCH format 3, 4, or 5 and PUCCH resources configured by higher layers, which may be the same as or different from the PUCCH resources associated with an ARI field having a value of '00').
[0093] For example, where the UE is associated with the first configuration and / or the third configuration, the UE may determine that P-CSI is to be dropped and that HARQ feedback is to be sent using PUCCH format 3. Alternatively, in some aspects, the UE may determine that P-CSI and HARQ feedback are to be multiplexed and sent using PUCCH format 2a, 2b, or 3. Where the UE is associated with the second configuration, the UE may determine that P-CSI and HARQ feedback are to be multiplexed and sent using PUCCH format 2a or 2b, or the UE may determine that P-CSI is to be dropped and HARQ feedback is to be sent using RRC configured resources associated with PUCCH format 1a or 1b.
[0094] like Figure 7 As further shown by reference mark 720, the UE may send uplink control information to the base station using the determined PUCCH format and the determined PUCCH resource. For example, when the uplink control information does not include HARQ feedback, the UE may use PUCCH format 1 to send a scheduling request, use PUCCH format 2 to send P-CSI, etc. In other examples, when the uplink control information includes HARQ feedback and additional uplink control information (e.g., scheduling request, P-CSI, etc.), when the DAI field has a value greater than one, one or more bits for the additional uplink control information may be attached to and / or multiplexed with one or more bits for HARQ feedback using PUCCH format 3, 4, or 5. Otherwise, when the uplink control information includes HARQ feedback and additional uplink control information and the DAI field has a value equal to one, various techniques may be used to send the uplink control information depending on whether the additional uplink control information includes a scheduling request and / or P-CSI.
[0095] For example, as described above, in the case where the additional uplink control information includes a positive scheduling request, PUCCH format 1a or 1b may be used to send HARQ feedback on resources reserved for the scheduling request, or in the case where the additional uplink control information includes a negative scheduling request, PUCCH format 3 may be used to multiplex one or more bits for the scheduling request with one or more bits for HARQ feedback. Additionally or alternatively, in some aspects, one or more bits for the additional uplink control information may be appended to one or more bits for HARQ feedback in PUCCH format 3, 4, or 5, regardless of whether the scheduling request is positive or negative (e.g., in a similar manner as when the DAI field has a value greater than one). Alternatively, in some aspects, HARQ feedback and scheduling requests may be sent concurrently based at least in part on falling back to RRC-configured PUCCH format 1a or 1b. For example, in the case where the scheduling request is negative, HARQ feedback can be sent on the PUCCH format 1a or 1b resources configured by RRC using PUCCH format 1a or 1b, or the channel selection process associated with PUCCH format 1b can be used to send HARQ feedback and scheduling requests using scheduling request resources and PUCCH format 1a or 1b resources configured by RRC, regardless of whether the scheduling request is positive or negative.
[0096] In some aspects, where the additional uplink control information includes P-CSI, sending the HARQ feedback and the additional uplink control information may include dropping the P-CSI and sending the HARQ feedback using PUCCH format 3 and / or RRC configured resources associated with PUCCH format 1a or 1b. Alternatively, in some aspects, sending the HARQ feedback and the additional uplink control information may include multiplexing the P-CSI and the HARQ feedback and sending the multiplexed P-CSI and HARQ feedback using PUCCH formats 2a, 2b, and / or 3.
[0097] As indicated above, Figure 7 are provided as examples. Other examples may differ from those described herein. Figure 7 An example of description.
[0098] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a UE in accordance with various aspects of the present disclosure. Example process 800 is an example of operations in which a UE (e.g., UE 120, etc.) performs operations associated with determining a PUCCH format for single uplink operation in dual connectivity mode with a TDD primary cell.
[0099] like Figure 8As shown in , in some aspects, process 800 may include determining, based at least in part on the downlink control information including a DAI equal to one, a PUCCH format and PUCCH resources to be used for concurrently sending the HARQ feedback and the additional uplink control information (block 810). For example, as described above, the UE may determine (e.g., using the controller / processor 280, etc.) a PUCCH format and PUCCH resources to be used for concurrently sending the HARQ feedback and the additional uplink control information based at least in part on the downlink control information including a DAI equal to one.
[0100] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include sending one or more of HARQ feedback or additional uplink control information using the PUCCH format and the PUCCH resource (block 820). For example, as described above, the UE may send (e.g., using the controller / processor 280, the transmit processor 264, the TX MIMO processor 266, the MOD 254, the antenna 252, etc.) one or more of HARQ feedback or additional uplink control information using the PUCCH format and the PUCCH resource.
[0101] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0102] In a first aspect, the additional uplink control information includes one or more of a scheduling request or P-CSI.
[0103] In a second aspect, alone or in combination with the first aspect, the PUCCH format is PUCCH format 1a or 1b and based at least in part on the additional uplink control information comprising a positive scheduling request, the PUCCH resource comprises one or more bits reserved for scheduling request.
[0104] In a third aspect, either alone or in combination with one or more of the first and second aspects, the PUCCH format is PUCCH format 3, and based at least in part on the additional uplink control information including a negative scheduling request, the PUCCH resources include one or more bits reserved for HARQ feedback.
[0105] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the PUCCH format is PUCCH format 3, 4 or 5, and includes a scheduling request based at least in part on additional uplink control information, the PUCCH resources including a scheduling request bit appended to one or more bits in the PUCCH format reserved for HARQ feedback.
[0106] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the PUCCH format is PUCCH format 1a or 1b, and sending one or more of the HARQ feedback or additional uplink control information includes sending the HARQ feedback and the negative scheduling request based at least in part on the RRC configuration associated with the PUCCH format 1a or 1b.
[0107] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, one or more of HARQ feedback or additional uplink control information is sent in a channel selection process associated with PUCCH format 1b using scheduling request resources.
[0108] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, at least in part based on the additional uplink control information including P-CSI, the PUCCH format is PUCCH format 3, and sending one or more of the HARQ feedback or the additional uplink control information includes discarding the P-CSI and using PUCCH format 3 to send the HARQ feedback.
[0109] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, at least in part based on the additional uplink control information including P-CSI, the PUCCH format is PUCCH format 2a, 2b or 3, and sending one or more of the HARQ feedback or additional uplink control information includes multiplexing the HARQ feedback with the P-CSI, and using PUCCH format 2a, 2b or 3 to send the HARQ feedback multiplexed with the P-CSI.
[0110] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the additional uplink control information includes P-CSI, the PUCCH format is PUCCH format 1a or 1b, and sending one or more of the HARQ feedback or the additional uplink control information includes discarding P-CSI, and sending the HARQ feedback is based at least in part on the RRC configuration associated with the PUCCH format 1a or 1b.
[0111] although Figure 8 Example blocks of process 800 are shown, but in some aspects, similar to Figure 8 Process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in . Additionally or alternatively, two or more blocks of process 800 may be performed in parallel.
[0112] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.
[0113] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software.
[0114] As used herein, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.
[0115] It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the aspects. Therefore, the operation and behavior of the systems and / or methods are not described herein with reference to specific software code - it should be understood that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.
[0116] Even if a specific combination of features is described in the claims and / or disclosed in the specification, these combinations are still not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically described in the claims and / or not specifically disclosed in the specification. Although each dependent claim listed below can directly depend on only one claim, the disclosure of various aspects includes each dependent claim combined with each other claim in the claim group. The phrase "at least one" referring to the list of items refers to any combination of those items, including a single member. For example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc and any combination with multiple identical elements (for example, aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc or any other ordering of a, b and c).
[0117] The elements, actions or instructions used herein should not be interpreted as being essential or necessary unless clearly described in this way. In addition, as used herein, the articles "a" and "an" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related items and unrelated items, etc.), and can be used interchangeably with "one or more". When it is expected that there is only one item, the phrase "only one" or similar language is used. In addition, as used herein, the terms "has", "have", "having" etc. are intended to be open terms. In addition, unless otherwise expressly stated, the phrase "based on" is intended to mean "based at least in part on".
Claims
1. A method for single uplink operation in dual connectivity mode with a time division duplex (TDD) primary cell, performed by a user equipment (UE), comprising: determining a physical uplink control channel (PUCCH) format and a PUCCH resource to be used for concurrently sending a hybrid automatic repeat request (HARQ) feedback and additional uplink control information, the additional uplink control information including a scheduling request (SR), based at least in part on the downlink control information including a downlink allocation index equal to one; as well as sending the HARQ feedback and the additional uplink control information using the PUCCH format and the PUCCH resource, wherein the PUCCH format is PUCCH format 4 or 5, and wherein, based at least in part on the additional uplink control information, the PUCCH resources include a scheduling request bit appended to one or more bits in the PUCCH format reserved for the HARQ feedback.
2. A method for single uplink operation in dual connectivity mode with a time division duplex (TDD) primary cell, performed by a user equipment (UE), comprising: determining a physical uplink control channel (PUCCH) format and a PUCCH resource to be used for concurrently sending hybrid automatic repeat request (HARQ) feedback and additional uplink control information including periodic channel state information (P-CSI) based at least in part on the downlink control information including a downlink allocation index equal to one; as well as sending the HARQ feedback and the additional uplink control information using the PUCCH format and the PUCCH resource, wherein, based at least in part on the additional uplink control information, the PUCCH format is PUCCH format 1a or 1b, and wherein sending the HARQ feedback and the additional uplink control information comprises: discarding the P-CSI; and The HARQ feedback is sent based at least in part on a radio resource control configuration associated with the PUCCH format 1a or 1b.
3. A user equipment (UE) for single uplink operation in dual connectivity mode with a time division duplex (TDD) primary cell, the UE comprising: Memory; as well as One or more processors operably coupled to the memory, the memory and the one or more processors configured to: determining a physical uplink control channel (PUCCH) format and a PUCCH resource to be used for concurrently sending hybrid automatic repeat request (HARQ) feedback and additional uplink control information, the additional uplink control information including a scheduling request (SR), based at least in part on the downlink control information including a downlink allocation index equal to one; as well as sending the HARQ feedback and the additional uplink control information using the PUCCH format and the PUCCH resource, wherein the PUCCH format is PUCCH format 4 or 5, and wherein, based at least in part on the additional uplink control information, the PUCCH resources include a scheduling request bit appended to one or more bits in the PUCCH format reserved for the HARQ feedback.
4. A user equipment (UE) for single uplink operation in dual connectivity mode with a time division duplex (TDD) primary cell, the UE comprising: Memory; as well as One or more processors operably coupled to the memory, the memory and the one or more processors configured to: determining a physical uplink control channel (PUCCH) format and a PUCCH resource to be used for concurrently sending hybrid automatic repeat request (HARQ) feedback and additional uplink control information, the additional uplink control information including periodic channel state information (P-CSI), based at least in part on the downlink control information including a downlink allocation index equal to one; as well as sending the HARQ feedback and the additional uplink control information using the PUCCH format and the PUCCH resource, wherein, based at least in part on the additional uplink control information, the PUCCH format is PUCCH format 1a or 1b, and wherein the memory and the one or more processors, when sending the HARQ feedback and the additional uplink control information, are further configured to: discarding the P-CSI; and The HARQ feedback is sent based at least in part on a radio resource control configuration associated with the PUCCH format 1a or 1b.
5. A non-transitory computer-readable medium having one or more instructions stored thereon, wherein the one or more instructions can be executed by one or more processors of a user equipment (UE) to implement the method of claim 1 or 2.
6. An apparatus for single uplink operation in dual connectivity mode with a time division duplex (TDD) primary cell at a user equipment (UE), the apparatus comprising: means for determining a physical uplink control channel (PUCCH) format and PUCCH resources to be used for concurrently sending hybrid automatic repeat request (HARQ) feedback and additional uplink control information, the additional uplink control information comprising a scheduling request (SR), based at least in part on the downlink control information comprising a downlink allocation index equal to one; as well as means for sending the HARQ feedback and the additional uplink control information using the PUCCH format and the PUCCH resources, wherein the PUCCH format is PUCCH format 4 or 5, and wherein, based at least in part on the additional uplink control information, the PUCCH resources include a scheduling request bit appended to one or more bits in the PUCCH format reserved for the HARQ feedback.
7. An apparatus for single uplink operation in dual connectivity mode with a time division duplex (TDD) primary cell at a user equipment (UE), the apparatus comprising: means for determining a physical uplink control channel (PUCCH) format and PUCCH resources to be used for concurrently transmitting hybrid automatic repeat request (HARQ) feedback and additional uplink control information, the additional uplink control information comprising periodic channel state information (P-CSI), based at least in part on the downlink control information comprising a downlink allocation index equal to one; as well as means for sending the HARQ feedback and the additional uplink control information using the PUCCH format and the PUCCH resources, wherein, based at least in part on the additional uplink control information, the PUCCH format is PUCCH format 1a or 1b, and wherein the means for sending the HARQ feedback and the additional uplink control information comprises: means for discarding the P-CSI; and Means for sending the HARQ feedback based at least in part on a radio resource control configuration associated with the PUCCH format 1a or 1b.
