This application claims priority from us application No.15/887,908 filed on 2/2018, which claims the benefit of us application S/n.62/455,563 entitled "RESOURCE ALLOCATION FOR PUCCH (RESOURCE ALLOCATION FOR PUCCH)" filed on 6/2/2017. The foregoing application is incorporated herein by reference in its entirety.
Detailed Description
Aspects of the present disclosure relate to resource allocation for PUCCH.
Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable media for a New Radio (NR) (new radio access technology or 5G technology).
NR may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidths (e.g., over 80MHz), millimeter wave (mmW) targeting high carrier frequencies (e.g., 60GHz), massive MTC (MTC) targeting non-backward compatible MTC technologies, and/or mission critical targeting ultra-reliable low latency communication (URLLC). These services may include latency and reliability requirements. These services may also have different Transmission Time Intervals (TTIs) to meet corresponding quality of service (QoS) requirements. In addition, these services may coexist in the same subframe.
As described in embodiments herein, a new resource allocation scheme is defined for use by a UE (e.g., UE 120) when transmitting a Physical Uplink Control Channel (PUCCH) to a BS (e.g., BS 110) under the NR standard. The new resource allocation schemes discussed herein are defined to account for one or more potential changes to the LTE standard made with respect to transmission of the PUCCH, which may be reflected in the NR standard.
The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in an order different than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. Moreover, the scope of the present disclosure is intended to cover such an apparatus or method as practiced using other structure, functionality, or structure and functionality in addition to or in addition to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be implemented by one or more elements of a claim. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration. Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects.
The techniques described herein may be used for various wireless communication networks, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), CDMA2000, and so on. UTRA includes wideband CDMA (wcdma) and other CDMA variants. cdma2000 covers IS-2000, IS-95 and IS-856 standards. TDMA networks may implement radio technologies such as global system for mobile communications (GSM). An OFDMA network may implement radio technologies such as NR (e.g., 5G RA), evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDMA, and so on. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). NR is an emerging wireless communication technology that is being developed in conjunction with the 5G technology forum (5 GTF). 3GPP Long Term Evolution (LTE) and LTE-advanced (LTE-A) are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A and GSM are described in literature from an organization named "3 rd Generation partnership project" (3 GPP). cdma2000 and UMB are described in documents from an organization named "3 rd generation partnership project 2" (3GPP 2). The techniques described herein may be used for the above-mentioned wireless networks and radio technologies as well as other wireless networks and radio technologies. For clarity, although aspects may be described herein using terms commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure may be applied in other generation-based communication systems, including NR technologies, such as 5G and progeny.
Example Wireless communication System
Fig. 1 illustrates an example wireless network 100, such as a New Radio (NR) or 5G network, in which aspects of the present disclosure may be performed.
As illustrated in fig. 1, wireless network 100 may include a number of BSs 110 and other network entities. The BS may be a station communicating with the UE. Each BS 110 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a coverage area of a node B and/or a node B subsystem serving that coverage area, depending on the context in which the term is used. In an NR system, the term "cell" and eNB, node B, 5G NB, AP, NR BS, or TRP may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station. In some examples, the base stations may be interconnected to each other and/or to one or more other base stations or network nodes (not shown) in wireless network 100 by various types of backhaul interfaces, such as a direct physical connection, a virtual network, or the like using any suitable transport network.
In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular Radio Access Technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, air interface, etc. The frequencies may also be referred to as carriers, frequency channels, etc. Each frequency may 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 may be deployed.
The BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. Picocells may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a residence) and may be restrictively accessible by UEs associated with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in the residence, etc.). The BS for the macro cell may be referred to as a macro BS. A BS for a picocell may be referred to as a pico BS. The BS for the femtocell may be referred to as a femto BS or a home BS. In the example shown in fig. 1, BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for picocell 102 x. BSs 110y and 110z may be femto BSs of femto cells 102y and 102z, respectively. A BS may support one or more (e.g., three) cells.
Wireless network 100 may also include relay stations. A relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., a BS or a UE) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. In the example shown in fig. 1, relay 110r may communicate with BS 110a and UE 120r to facilitate communication between BS 110a and UE 120 r. The relay station may also be referred to as a relay BS, relay, etc.
The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relays, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 20 watts), while pico BSs, femto BSs, and relays may have lower transmit power levels (e.g., 1 watt).
Wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timings, and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operations.
Network controller 130 may be coupled to a set of BSs and provide coordination and control for these BSs. Network controller 130 may communicate with BS 110 via a backhaul. BSs 110 may also communicate with each other, directly or indirectly, e.g., via a wireless or wired backhaul.
UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a client equipment (CPE), a cellular phone, a smartphone, a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop, a cordless phone, a Wireless Local Loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or medical equipment, a biometric sensor/device, a wearable device (such as a smartwatch, a smart garment, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart necklace, etc.)), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicle component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, a smart meter/sensor, a smart meter, a smart manufacturing equipment, a global positioning system device, a wireless communication device, a wireless device, a, Or any other suitable device configured to communicate via a wireless or wired medium. Some UEs may be considered evolved or Machine Type Communication (MTC) devices or evolved MTC (emtc) devices. MTC and eMTC UEs include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, a location tag, etc., which may communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity for or to a network (e.g., a wide area network such as the internet or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered internet of things (IoT) devices.
In fig. 1, a solid line with double arrows indicates a desired transmission between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink. The dashed line with double arrows indicates the interfering transmission between the UE and the BS.
Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, and so on. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain under OFDM and in the time domain under SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may depend on the system bandwidth. For example, the spacing of the subcarriers may be 15kHz, and the minimum resource allocation (referred to as a 'resource block') may be 12 subcarriers (or 180 kHz). Thus, for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal FFT size may be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided into sub-bands. For example, a sub-band may cover 1.08MHz (i.e., 6 resource blocks), and for a system bandwidth of 1.25, 2.5, 5, 10, or 20MHz, there may be 1, 2, 4, 8, or 16 sub-bands, respectively.
Although aspects of the examples described herein may be associated with LTE technology, aspects of the disclosure may be applicable to other wireless communication systems, such as NRs. NR may utilize OFDM with CP on the uplink and downlink and include support for half-duplex operation using Time Division Duplex (TDD). A single component carrier bandwidth of 100MHz may be supported. The NR resource block may span 12 subcarriers with a subcarrier bandwidth of 75kHz over a 0.1ms duration. Each radio frame may include 50 subframes having a length of 10 ms. Thus, each subframe may have a length of 0.2 ms. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission, and the link direction for each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. UL and DL subframes for NR may be described in more detail below with reference to fig. 6 and 7. Beamforming may be supported and beam directions may be dynamically configured. MIMO transmission with precoding may also be supported. MIMO configuration in DL can support up to 8 transmit antennas (multi-layer DL transmission with up to 8 streams) and up to 2 streams per UE. Multi-layer transmission of up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported using up to 8 serving cells. Alternatively, the NR may support a different air interface than OFDM based. The NR network may comprise entities such as CUs and/or DUs.
In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communication between some or all of the devices and equipment within its service area or cell. Within the present disclosure, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities, as discussed further below. That is, for scheduled communications, the subordinate entity utilizes the resources allocated by the scheduling entity. The base station is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE is acting as a scheduling entity and other UEs utilize resources scheduled by the UE for wireless communications. The UE may act as a scheduling entity in a peer-to-peer (P2P) network and/or in a mesh network. In the mesh network example, the UEs may optionally communicate directly with each other in addition to communicating with the scheduling entity.
Thus, in a wireless communication network having scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, and a mesh configuration, a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources.
As mentioned above, the RAN may include CUs and DUs. An NR BS (e.g., eNB, 5G B node, node B, Transmission Reception Point (TRP), Access Point (AP)) may correspond to one or more BSs. The NR cell may be configured as an access cell (ACell) or a data-only cell (DCell). For example, the RAN (e.g., a central unit or a distributed unit) may configure the cells. The DCell may be a cell used for carrier aggregation or dual connectivity but not for initial access, cell selection/reselection, or handover. In some cases, the DCell may not transmit synchronization signals — in some cases, the DCell may transmit SSs. The NR BS may transmit a downlink signal to the UE to indicate the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine the NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.
Fig. 2 illustrates an example logical architecture of a distributed Radio Access Network (RAN)200, which may be implemented in the wireless communication system illustrated in fig. 1. The 5G access node 206 may include an Access Node Controller (ANC) 202. ANC may be a Central Unit (CU) of the distributed RAN 200. The backhaul interface to the next generation core network (NG-CN)204 may be terminated at the ANC. The backhaul interface to the neighboring next generation access node (NG-AN) may be terminated at the ANC. An ANC may include one or more TRPs 208 (which may also be referred to as a BS, NR BS, node B, 5G NB, AP, or some other terminology). As described above, TRP may be used interchangeably with "cell".
TRP 208 may be a DU. A TRP may be connected to one ANC (ANC 202) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), AND service-specific AND deployments, a TRP may be connected to more than one ANC. The TRP may include one or more antenna ports. The TRP may be configured to serve traffic to the UE individually (e.g., dynamic selection) or jointly (e.g., joint transmission).
The local architecture 200 may be used to illustrate a fronthaul (frontaul) definition. The architecture may be defined to support outbound solutions across different deployment types. For example, the architecture may be based on transport network capabilities (e.g., bandwidth, latency, and/or jitter).
The architecture may share features and/or components with LTE. According to aspects, the next generation AN (NG-AN)210 may support dual connectivity with NRs. NG-ANs may share a common fronthaul for LTE and NR.
The architecture may enable collaboration between and among TRPs 208. For example, cooperation may be preset within the TRP and/or across the TRPs via ANC 202. According to aspects, an inter-TRP interface may not be required/present.
According to aspects, dynamic configuration of split logic functionality may exist within architecture 200. As will be described in more detail with reference to fig. 5, a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer may be adaptively placed at the DU or CU (e.g., at the TRP or ANC, respectively). According to certain aspects, a BS may include a Central Unit (CU) (e.g., ANC 202) and/or one or more distributed units (e.g., one or more TRPs 208).
Fig. 3 illustrates an example physical architecture of a distributed RAN 300 in accordance with aspects of the present disclosure. A centralized core network unit (C-CU)302 may host core network functions. The C-CUs may be deployed centrally. The C-CU functionality may be offloaded (e.g., to Advanced Wireless Services (AWS)) in an effort to handle peak capacity.
A centralized RAN unit (C-RU)304 may host one or more ANC functions. Optionally, the C-RU may host the core network functions locally. The C-RU may have a distributed deployment. The C-RU may be closer to the network edge.
DU 306 may host one or more TRPs (edge node (EN), Edge Unit (EU), Radio Head (RH), Smart Radio Head (SRH), etc.). The DUs may be located at the edge of a network with Radio Frequency (RF) functionality.
Fig. 4 illustrates example components of BS 110 and UE 120 illustrated in fig. 1 that may be used to implement aspects of the present disclosure. As described above, the BS may include TRP. One or more components of BS 110 and UE 120 may be used to practice aspects of the present disclosure. For example, antenna 452, Tx/Rx 222, processors 466, 458, 464, and/or controller/processor 480 of UE 120, and/or antenna 434, processors 460, 420, 438, and/or controller/processor 440 of BS 110 may be used to perform the operations described herein and illustrated with reference to fig. 8.
FIG. 4 shows a block diagram of a design of BS 110 and UE 120, which may be one of the BSs and one of the UEs in FIG. 1. For the constrained association scenario, base station 110 may be macro BS 110c in fig. 1, and UE 120 may be UE 120 y. The base station 110 may also be some other type of base station. Base station 110 may be equipped with antennas 434a through 434t, and UE 120 may be equipped with antennas 452a through 452 r.
At base station 110, a transmit processor 420 may receive data from a data source 412 and control information from a controller/processor 440. The control information may be used for a Physical Broadcast Channel (PBCH), a Physical Control Format Indicator Channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a Physical Downlink Control Channel (PDCCH), etc. The data may be for a Physical Downlink Shared Channel (PDSCH), etc. Processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Processor 420 may also generate reference symbols (e.g., for PSS, SSS, and cell-specific reference signals). A Transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to Modulators (MODs) 432a through 432 t. For example, TX MIMO processor 430 may perform certain aspects described herein for RS multiplexing. Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 432 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 432a through 432t may be transmitted via antennas 434a through 434t, respectively.
At UE 120, antennas 452a through 452r may receive downlink signals from base station 110 and may provide received signals to demodulators (DEMODs) 454a through 454r, respectively. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 454 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtain received symbols from all demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. For example, MIMO detector 456 may provide detected RSs transmitted using techniques described herein. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller/processor 480. According to one or more scenarios, the CoMP aspects may include providing antennas and some Tx/Rx functionality such that they reside in a distributed unit. For example, some Tx/Rx processing may be done in a central unit, while other processing may be done at distributed units. For example, BS modulator/demodulator 432 may be in a distributed unit in accordance with one or more aspects as shown in the figure.
On the uplink, at UE 120, a transmit processor 464 may receive and process data from a data source 462 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from a controller/processor 480 (e.g., for the Physical Uplink Control Channel (PUCCH)). The transmit processor 464 may also generate reference symbols for a reference signal. The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by the demodulators 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At BS 110, the uplink signals from UE 120 may be received by antennas 434, processed by modulators 432, detected by a MIMO detector 436, if applicable, and further processed by a receive processor 438 to obtain decoded data and control information sent by UE 120. The receive processor 438 may provide decoded data to a data sink 439 and decoded control information to a controller/processor 440.
Controllers/processors 440 and 480 may direct the operation at base station 110 and UE 120, respectively. Processor 440 and/or other processors and modules at base station 110 may perform or direct, for example, execution of the functional blocks illustrated in fig. 8, and/or other processes for the techniques described herein. Processor 480 and/or other processors and modules at UE 120 may also perform or direct processes for the techniques described herein. Memories 442 and 482 may store data and program codes for BS 110 and UE 120, respectively. A scheduler 444 may schedule UEs for data transmission on the downlink and/or uplink.
Fig. 5 illustrates a diagram 500 showing an example for implementing a communication protocol stack in accordance with aspects of the present disclosure. The illustrated communication protocol stack may be implemented by a device operating in a 5G system (e.g., a system supporting uplink-based mobility). Diagram 500 illustrates a communication protocol stack including a Radio Resource Control (RRC) layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a Radio Link Control (RLC) layer 520, a Medium Access Control (MAC) layer 525, and a Physical (PHY) layer 530. In various examples, the layers of the protocol stack may be implemented as separate software modules, portions of a processor or ASIC, portions of non-co-located devices connected by a communication link, or various combinations thereof. Co-located and non-co-located implementations may be used, for example, in a protocol stack for a network access device (e.g., AN, CU, and/or DU) or UE.
A first option 505-a illustrates a split implementation of a protocol stack, where the implementation of the protocol stack is split between a centralized network access device (e.g., ANC 202 in fig. 2) and a distributed network access device (e.g., DU 208 in fig. 2). In the first option 505-a, the RRC layer 510 and the PDCP layer 515 may be implemented by a central unit, while the RLC layer 520, the MAC layer 525, and the PHY layer 530 may be implemented by DUs. In various examples, a CU and a DU may be co-located or non-co-located. The first option 505-a may be useful in a macro cell, micro cell, or pico cell deployment.
A second option 505-B illustrates a unified implementation of a protocol stack, wherein the protocol stack is implemented in a single network access device (e.g., Access Node (AN), new radio base station (NR BS), new radio node B (NR NB), Network Node (NN), etc.). In a second option, the RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530 may each be implemented by AN. The second option 505-b may be useful in femtocell deployments.
Regardless of whether the network access device implements part or all of the protocol stack, the UE may implement the entire protocol stack (e.g., RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530).
Fig. 6 is a diagram 600 illustrating an example of a DL centric sub-frame. The DL centric sub-frame may include a control portion 602. The control portion 602 may be present in an initial or beginning portion of the DL-centric sub-frame. The control portion 602 may include various scheduling information and/or control information corresponding to various portions of the DL-centric sub-frame. In some configurations, the control portion 602 may be a Physical DL Control Channel (PDCCH), as indicated in fig. 6. The DL centric sub-frame may also include a DL data portion 604. The DL data portion 604 may sometimes be referred to as the payload of a DL centric subframe. The DL data portion 604 may include communication resources for communicating DL data from a scheduling entity (e.g., a UE or BS) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 604 may be a Physical DL Shared Channel (PDSCH).
The DL centric sub-frame may also include a common UL portion 606. Common UL portion 606 may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms. The common UL portion 606 may include feedback information corresponding to various other portions of the DL-centric sub-frame. For example, the common UL portion 606 may include feedback information corresponding to the control portion 602. Non-limiting examples of feedback information may include ACK signals, NACK signals, HARQ indicators, and/or various other suitable types of information. The common UL portion 606 may include additional or alternative information, such as information related to Random Access Channel (RACH) procedures, Scheduling Requests (SRs), and various other suitable types of information. As illustrated in fig. 6, the end of the DL data portion 604 may be separated in time from the beginning of the common UL portion 606. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This interval provides time for a handover from DL communication (e.g., a receive operation by a subordinate entity (e.g., a UE)) to UL communication (e.g., a transmission by a subordinate entity (e.g., a UE)). Those of ordinary skill in the art will appreciate that the foregoing is merely one example of a DL centric sub-frame and that alternative structures having similar features may exist without necessarily departing from the aspects described herein.
Fig. 7 is a diagram 700 illustrating an example of a UL-centric subframe. The UL centric sub-frame may include a control portion 702. The control portion 702 may be present in an initial or beginning portion of the UL-centric sub-frame. The control portion 702 in fig. 7 may be similar to the control portion described above with reference to fig. 6. The UL centric sub-frame may also include a UL data portion 704. The UL data portion 704 may sometimes be referred to as the payload of a UL-centric subframe. The UL data 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, control portion 702 may be a Physical DL Control Channel (PDCCH).
As illustrated in fig. 7, the end of the control portion 702 may be separated in time from the beginning of the UL data portion 704. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This interval provides time for a handover from DL communication (e.g., a receive operation by the scheduling entity) to UL communication (e.g., a transmission by the scheduling entity). The UL-centric subframe may also include a common UL portion 706. The common UL portion 706 in fig. 7 may be similar to the common UL portion 706 described above with reference to fig. 7. Common UL portion 706 may additionally or alternatively include information related to Channel Quality Indicators (CQIs), Sounding Reference Signals (SRS), and various other suitable types of information. Those of ordinary skill in the art will appreciate that the foregoing is merely one example of a UL-centric sub-frame and that alternative structures having similar features may exist without necessarily departing from the aspects described herein.
In some environments, two or more subordinate entities (e.g., UEs) may communicate with each other using a side-link signal. Real-world applications for such sidelink communications may include public safety, proximity services, UE-to-network relays, vehicle-to-vehicle (V2V) communications, internet of everything (IoE) communications, IoT communications, mission critical meshes, and/or various other suitable applications. In general, sidelink signals may refer to signals communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even though the scheduling entity may be used for scheduling and/or control purposes. In some examples, sidelink signals may be communicated using licensed spectrum (unlike wireless local area networks, which typically use unlicensed spectrum).
The UE may operate in various radio resource configurations, including configurations associated with transmitting pilots using a dedicated set of resources (e.g., a Radio Resource Control (RRC) dedicated state, etc.), or configurations associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a set of dedicated resources for transmitting pilot signals to the network. When operating in the RRC shared state, the UE may select a common set of resources for transmitting pilot signals to the network. In either case, the pilot signal transmitted by the UE may be received by one or more network access devices (such as AN, or DU, or portions thereof). Each receiving network access device may be configured to receive and measure pilot signals transmitted on a common set of resources and also receive and measure pilot signals transmitted on a dedicated set of resources assigned to a UE, where the network access device is a member of a monitoring network access device set for the UE. The CU to which the receiving network access device(s) or the receiving network access device(s) transmit pilot signal measurements may use these measurements to identify the serving cell of the UE or initiate a change to the serving cell of the UE or UEs.
Example resource allocation for PUCCH
As described above, in some cases, the LTE PUCCH is a channel used to carry Uplink Control Information (UCI). The LTE PUCCH control signaling channel includes hybrid automatic repeat request (HARQ) Acknowledgement (ACK) or Negative Acknowledgement (NACK), Channel Quality Indicator (CQI), MIMO feedback (e.g., Rank Indicator (RI)), Precoding Matrix Indicator (PMI), etc.), scheduling request for uplink transmission, and Binary Phase Shift Keying (BPSK) or Quadrature Phase Shift Keying (QPSK) for PUCCH modulation. In some cases, LTE PUCCH resource allocation may be performed semi-statically or dynamically. Semi-static resource allocation enables periodic and semi-static reporting of CQI. In addition, semi-static resource allocation supports transmission of SR (i.e., status report) and ACK/NACK for semi-persistent Physical Downlink Shared Channel (PDSCH). Semi-static resource allocation generally has a small signaling overhead and is suitable for periodic transmissions.
Dynamic resource allocation, on the other hand, is more flexible and efficient, but may have a larger signaling overhead. Dynamic resource allocation supports dynamic ACK transmission. In some cases, the dynamic ACK resources may be implicitly mapped from a starting Control Channel Element (CCE) index of the PDCCH. In some cases, dynamic ACK resources may also be explicitly signaled in the PDCCH. In some cases, the dynamic ACK resources may include implicit mapping in the PDCCH and explicit signaling.
In some embodiments, one or more changes to the LTE communication standard (which may be implemented in the NR communication standard) may require the definition of a new resource allocation scheme for the PUCCH in the NR. Fig. 8-10 illustrate example operations that a UE may perform to communicate in accordance with these new resource allocation schemes.
Fig. 8 illustrates example operations 800 involving resource allocation for transmitting one or more Uplink Control Information (UCI) bits in the PUCCH according to aspects of the present disclosure. The operations 800 may be performed, for example, by a UE.
Operations 800 begin, at 802, by determining resources allocated to provide one or more Uplink Control Information (UCI) bits based at least on a type of service associated with the UE. At 804, the operations 800 continue by transmitting a Physical Uplink Control Channel (PUCCH) with the one or more UCI bits to the base station using the allocated resources.
Fig. 9 illustrates example operations 900 involving resource allocation for transmitting Buffer Status Report (BSR) PUCCH according to aspects of the present disclosure. The operations 900 may be performed, for example, by a UE.
Operation 900 begins at 902 with generating a Buffer Status Report (BSR). At 904, operation 900 continues by transmitting the BSR in a Physical Uplink Control Channel (PUCCH) transmission.
Fig. 10 illustrates example operations 1000 involving resource allocation for PUCCH according to aspects of the present disclosure. The operations 1000 may be performed, for example, by a UE.
Operation 1000 begins at 1002, determining resources allocated for transmitting a Buffer Status Report (BSR) based on at least one of: a type of uplink channel to be used for transmitting the BSR, or a service type of traffic corresponding to the BSR. At 1004, the operations 1000 continue by determining resources to be used for transmitting Buffer Status Reports (BSR) based on at least one of: a type of uplink channel to be used for transmitting the BSR, or a service type of traffic corresponding to the BSR.
As described above, one or more changes may be made to the LTE communication standard that may be mapped in the NR communication standard and require the definition of a new resource allocation scheme for the PUCCH in the NR. In some embodiments, the first change is that the ACK payload in the NR communication standard may be more than 1 or 2 bits. In some embodiments, the second change may be to include a Buffer Status Report (BSR) in the PUCCH. In LTE, the BSR is transmitted on the PUSCH. In some embodiments, the BSR may include a regular BSR, a periodic BSR, and a padding BSR. In some embodiments, including the BSR in the PUCCH may result in a reduction in turnaround time. Additionally, in some embodiments, the PUCCH-BSR may have a reduced payload size compared to the PUSCH-BSR (i.e., the payload content in the PUCCH-BSR may be different than the payload content in the PUSCH-BSR).
In some embodiments, the third change involves introducing different types of UEs and also introducing different types of services ("ToS") associated with the UEs. For example, as described above, NR may support eMBB UEs and URLLC UEs, each with different ToS requirements. More specifically, in some embodiments, the payload size and payload interpretation may be different depending on whether the UE is an eMBB UE or a URLLC UE. For example, a mission critical UE (e.g., URLLC UE) may have a smaller payload size than an eMBB UE. In addition, in some embodiments, the channel structure may also be different. For example, the frame structure of an eMBB UE may span the entire long duration, while the frame structure of a URLLC UE may only span 1 or 2 symbols. Further still, in some embodiments, the resource allocation types may be different. For example, resources for eMBB UEs may be dynamically allocated, while resources for URLLC UEs may be semi-statically allocated. Such semi-static allocation may reduce the turnaround time for URLLC UEs. Also, in embodiments where PUCCH includes a BSR, the difference between eMBB UEs and URLLC UEs may affect the resource allocation for transmission of BSRs (for both PUSCH-BSR and PUCCH-BSR).
Accordingly, described herein are embodiments related to NR PUCCH resource allocation that account for potential differences between NR and LTE communication standards. In some embodiments, the NR PUCCH resource allocation may be performed semi-statically or dynamically. In some embodiments, semi-static resource allocation allows for periodic CQI reporting, SR transmission, ACK transmission for semi-persistent PDSCH, periodic BSR reporting, and BSR for high priority UEs, such as URLLC UEs. On the other hand, in some embodiments, dynamic resource allocation may provide dynamic ACKs. In some embodiments, the ACK payload may be 1, 2, or more payload bits.
Although in some embodiments resources are allocated for the PUCCH with one or more bits of only one of the carousel ACK, CQI, SR, or BSR, in some other embodiments resources are allocated for the PUCCH with combined UCI. The combined UCI refers to UCI including two or more of ACK, CQI, SR, or BSR. For example, in some embodiments, a smaller payload ACK (e.g., 1 bit or 2 bits) may be transmitted on CQI resources in the same subframe (e.g., similar to format 2a/2 b). In some embodiments, if the ACK is dynamic, dynamic resource allocation may not be necessary. However, in embodiments where the ACK is semi-persistent, the ACK resources may be used by other UEs within the subframe. In some embodiments where the ACK has a higher payload, the CQI resources may not be sufficient for transmission of the ACK in the same subframe. In such embodiments, CQI resources may be overridden using dynamically allocated resources for the combined payload. In some embodiments, CQI resources and semi-persistent ACK resources may be released within the subframe.
In some embodiments, the dynamically allocated resources may be entirely new resources that do not have overlap with the CQI resources or the ACK resources. In some embodiments, the dynamically allocated resources may include CQI resources or ACK resources with a Resource Block (RB) extension (e.g., CQI or ACK resources with more RBs). In some embodiments, the combined payload may be transmitted using joint encoding of the ACK and CQI in the dynamically allocated resources. In some other embodiments, the combined payload may be transmitted using separate encoding of the ACK and CQI in the dynamically allocated resources. In some other embodiments, the ACK payload may be encoded jointly with a first portion of the CQI payload (e.g., a first one or more CQI bits) and separately from a second portion of the CQI payload (e.g., a second one or more bits).
In some embodiments, SR and CQI may be considered for transmission in the same subframe. In such embodiments, the transmission may be performed using at least two different techniques. According to a first technique, CQI may be transmitted on CQI resources if SR is negative. However, if the SR is affirmative, the SR may be transmitted on SR resources and the CQI may be discarded. According to a second technique, the SR may piggyback (piggyback) on the CQI resources. For example, a value of 0 may imply a negative SR or a normal CQI, while a value of 1 may imply a positive SR or a modulated DMSR. According to a second technique of transmitting the SR, the SR resources may be used by other UEs in the same subframe.
In some embodiments, SR and ACK may be considered for transmission in the same subframe. In such embodiments, the transmission may be performed using at least two different techniques. According to a first technique, if the SR is negative, an ACK may be transmitted on ACK resources. However, if the SR is positive, an ACK may be transmitted on the SR resources. In some embodiments, both ACK resources and SR resources may be reserved for blind detection of SRs. According to a second technique, the SR and ACK may be jointly encoded. In one example, a bit in the joint payload having values 0 and 1 may be mapped to a negative SR or a positive SR, respectively, and vice versa. In another example, a bit having a value of 1 in the joint payload may be mapped as a positive SR, while an absence of an SR bit in the joint payload may be mapped as a negative SR. Blind detection of payload size may be performed at the receiver side to detect SR.
In some embodiments, SR and BSR may be considered for transmission in the same subframe. However, this may not be effective because in some embodiments, the UE may only have either the SR or BSR, but not both.
In some embodiments, if the ACK has a smaller payload (e.g., 1 bit or 2 bits), the ACK and the semi-static BSR may be considered for transmission in the same subframe. In such embodiments, ACK resources may be released if the ACK is also semi-persistent. On the other hand, if the ACK has a higher payload (e.g., compared to 1 bit or 2 bits), the new resources may be overridden using dynamic allocation. In such embodiments, BSR resources may be released. The dynamically allocated resource may be a completely new resource that does not overlap with the BSR resource or the ACK resource, or it may be a BSR resource or an ACK resource with an extension (e.g., with more RBs). In some examples, the combined payload may be transmitted using joint coding of the ACK and BSR in dynamically allocated resources. In some other examples, the combined payload may be transmitted using separate coding of the ACK and BSR in dynamically allocated resources.
In some embodiments, the BSR and CQI may be considered for transmission in the same subframe. In such embodiments, the new resources may be overridden using dynamic allocation. Additionally, in embodiments where the BSR and CQI have different performance goals, a new channel structure/coding may be provided for the combined UCI. In some embodiments, CQI resources and semi-static BSR resources may be released. The dynamically allocated new resource may be a completely new resource that does not overlap with the CQI or BSR resource, or it may be a CQI or BSR resource with an extension (e.g., with more RBs). In some examples, the combined payload may be transmitted using joint coding of the BSR and CQI in the dynamically allocated resources. In some other examples, the combined payload may be transmitted using separate encoding of the BSR and CQI in the dynamically allocated resources.
As described above, in some embodiments, more than two types of UCI may be transmitted in the same subframe. The dynamically allocated new resources may override any semi-statically allocated resources for each individual UCI. The dynamically allocated new resources, when transmitted separately, may be entirely new resources that do not have an overlap with any of the UCI resources, or the dynamically allocated resources may include any of the UCI resources with an extension (e.g., with more RBs). The combined payload may be transmitted using joint coding in the dynamically allocated resources. In another example, the combined payload may be transmitted using separate encoding for each UCI type in dynamically allocated resources. In yet another example, the combined payload may be transmitted using separate encoding of some UCI types and joint encoding of some other UCI types in dynamically allocated resources.
Some embodiments described herein relate to dynamic resource allocation for ACKs. In some embodiments, dynamic resource allocation for ACKs may include implicit mapping and/or explicit signaling. In LTE, implicit mapping may be performed by setting the starting CCE index to ACK resources. In NR, in some embodiments, the UE may monitor only the sub-band PDCCH. In some embodiments, UEs from different subbands may see different CCE indices. In such embodiments, the same implicit mapping may be used for ACK resource mapping. In some embodiments, UEs from different subbands may see the same CCE index. Accordingly, the UEs may be mapped to the same ACK resources. In some embodiments, this may result in a conflict. However, to avoid collisions, in some embodiments, the implicit mapping may be subband dependent. In such embodiments, different subbands may be mapped to different ACK resource pools. For example, a subband-dependent offset above the starting CCE index may be added. In some embodiments, the subband-dependent resource pool/offset may be signaled in a SIB.
In NR, in some embodiments, the eNB may give scheduling for two or more slots within one PDCCH. Such cross-slot scheduling may also require different mapping functions from the starting CCE index to the UL ACK resources. In some embodiments, the implicit mapping may be dependent on cross-slot scheduling. In such embodiments, PDCCH for grants in different slots may be mapped to the same ACK resources. For example, a slot-dependent offset above the starting CCE index may be added. In some embodiments, slot-dependent resource offsets may be signaled in SIBs.
In NR, in some embodiments, the UE may need to transmit ACKs with different payload sizes (i.e., different numbers of payload bits). In some embodiments, different payload sizes may also need to be mapped to different resource pools to ensure certain performance requirements are met. In such embodiments, the implicit mapping may be dependent on the payload size. For example, a payload size dependent offset above the starting CCE index may be added. In some embodiments, a resource offset depending on the payload size may be signaled in the SIB.
As described above, in some embodiments, the dynamic allocation for ACKs may be explicit signaling. In such embodiments, the eNB may send a grant for an ACK in the PDCCH. In some embodiments, this may override the implicit mapping.
The methods disclosed herein comprise one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
As used herein, a phrase referring to "at least one of a list of items" refers to any combination of these items, including a single member. By way of example, "at least one of a, b, or c" is intended to encompass: a. b, c, a-b, a-c, b-c, and a-b-c, and any combination having a plurality of the same elements (e.g., a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b-b, b-b-c, c-c, and c-c-c, or any other ordering of a, b, and c).
As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" can include calculating, computing, processing, deriving, studying, looking up (e.g., looking up in a table, a database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, choosing, establishing, and the like.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. The term "some" refers to one or more unless specifically stated otherwise. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No element of the claims should be construed under the provisions of 35u.s.c. § 112 sixth clause, unless the element is explicitly recited using the wording "means for … …" or in the case of a method claim the element is recited using the wording "step for … …".
The various operations of the methods described above may be performed by any suitable means capable of performing the corresponding functions. These means may include various hardware and/or software components and/or modules, including but not limited to, circuits, Application Specific Integrated Circuits (ASICs), or processors. Generally, where there are operations illustrated in the figures, the operations may have corresponding counterpart means plus functional components with similar numbering.
For example, means for transmitting and/or means for receiving may include one or more of the transmit processor 420, the TX MIMO processor 430, the receive processor 438, or the antenna(s) 434 of the base station 110 and/or the transmit processor 464, the TX MIMO processor 466, the receive processor 458, or the antenna(s) 452 of the user equipment 120. Further, the means for generating, the means for multiplexing, and/or the means for applying may comprise one or more processors (such as controller/processor 440 of base station 110 and/or controller/processor 480 of user equipment 120).
The various illustrative logical blocks, modules, and circuits described in connection with the disclosure may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable Logic Device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
If implemented in hardware, an example hardware configuration may include a processing system in the wireless node. The processing system may be implemented with a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints. The bus may link together various circuits including the processor, the machine-readable medium, and the bus interface. A bus interface may be used to connect a network adapter or the like to the processing system via the bus. A network adapter may be used to implement the signal processing functions of the PHY layer. In the case of a user terminal 120 (see fig. 1), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further. A processor may be implemented with one or more general and/or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry capable of executing software. Those skilled in the art will recognize how best to implement the functionality described with respect to the processing system, depending on the particular application and the overall design constraints imposed on the overall system.
If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Software should be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage medium. A computer readable storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. By way of example, the machine-readable medium may comprise a transmission line, a carrier wave modulated by data, and/or a computer-readable storage medium separate from the wireless node having instructions stored thereon, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into a processor, such as a cache and/or a general register file, as may be the case. Examples of a machine-readable storage medium may include RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, magnetic disk, optical disk, hard drive, or any other suitable storage medium, or any combination thereof, as examples. The machine-readable medium may be embodied in a computer program product.
A software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media. The computer readable medium may include several software modules. These software modules include instructions that, when executed by a device, such as a processor, cause the processing system to perform various functions. These software modules may include a transmitting module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. As an example, a software module may be loaded into RAM from a hard drive when a triggering event occurs. During execution of the software module, the processor may load some instructions into the cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When referring to the functionality of a software module below, it will be understood that such functionality is implemented by the processor when executing instructions from the software module.
Any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as Infrared (IR), radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk (disk) and disc (disc), as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk, anddisks, where a disk (disk) usually reproduces data magnetically, and a disk (disc) reproduces data optically with a laser. Thus, in some aspects, computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, the computer-readable medium may comprise a transitory computer-readable medium (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.
Thus, certain aspects may comprise a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein. Such as instructions for performing the operations described herein and illustrated in fig. 8-10.
Further, it is to be appreciated that modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station where applicable. For example, such a device can be coupled to a server to facilitate the transfer of an apparatus for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a Compact Disc (CD) or floppy disk, etc.), such that upon coupling or providing the storage device to a user terminal and/or base station, the apparatus can obtain the various methods. Further, any other suitable technique suitable for providing the methods and techniques described herein to a device may be utilized.
It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various changes, substitutions and alterations in the arrangement, operation and details of the method and apparatus described above may be made without departing from the scope of the claims.