EP3744028B1 - Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc) - Google Patents
Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc) Download PDFInfo
- Publication number
- EP3744028B1 EP3744028B1 EP19703589.2A EP19703589A EP3744028B1 EP 3744028 B1 EP3744028 B1 EP 3744028B1 EP 19703589 A EP19703589 A EP 19703589A EP 3744028 B1 EP3744028 B1 EP 3744028B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- pdcch
- control information
- pdcchs
- pdschs
- time interval
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000004891 communication Methods 0.000 title claims description 64
- 238000000034 method Methods 0.000 claims description 66
- 230000005540 biological transmission Effects 0.000 claims description 43
- 238000013468 resource allocation Methods 0.000 claims description 21
- 238000012545 processing Methods 0.000 claims description 13
- 238000012544 monitoring process Methods 0.000 claims description 7
- 125000004122 cyclic group Chemical group 0.000 claims description 4
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 claims 3
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 claims 3
- 238000005516 engineering process Methods 0.000 description 24
- 238000010586 diagram Methods 0.000 description 16
- 238000003860 storage Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 13
- 230000008569 process Effects 0.000 description 10
- 230000008685 targeting Effects 0.000 description 9
- 230000015654 memory Effects 0.000 description 7
- 230000009471 action Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 5
- 230000007774 longterm Effects 0.000 description 4
- 238000000926 separation method Methods 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 4
- 230000001413 cellular effect Effects 0.000 description 3
- 238000001228 spectrum Methods 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 108010076504 Protein Sorting Signals Proteins 0.000 description 1
- 241000700159 Rattus Species 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 230000003595 spectral effect Effects 0.000 description 1
- 230000007480 spreading Effects 0.000 description 1
- 238000003892 spreading Methods 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
- 210000000707 wrist Anatomy 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1835—Buffer management
- H04L1/1845—Combining techniques, e.g. code combining
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
- H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
- H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
- H04W72/512—Allocation or scheduling criteria for wireless resources based on terminal or device properties for low-latency requirements, e.g. URLLC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/188—Time-out mechanisms
Definitions
- aspects of the present disclosure relate generally to wireless communications systems, methods as well as apparatus, and more particularly, to soft combining of control information.
- Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth and transmit power).
- multiple-access systems include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) systems, 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, and time division synchronous code division multiple access (TD-SCDMA) systems.
- 3GPP 3rd Generation Partnership Project
- LTE Long Term Evolution
- LTE-A LTE Advanced
- CDMA code division multiple access
- TDMA time division multiple access
- FDMA frequency division multiple access
- OFDMA orthogonal frequency division multiple access
- SC-FDMA single-carrier
- a wireless multiple-access communication system may include a number of base stations (BSs) that each can simultaneously support communication for multiple communication devices, otherwise known as user equipment (UEs).
- BSs base stations
- UEs user equipment
- a set of one or more gNBs may define an e NodeB (eNB).
- a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with a number of central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a set of one or more distributed units, in communication with a central unit, may define an access node (e.g., a NR BS, a NR NB, a network node, a 5G NB, a next generation NB (gNB), etc.).
- DUs distributed units
- EUs edge units
- ENs edge nodes
- RHs radio heads
- RHs smart radio heads
- TRPs transmission reception points
- CUs central units
- CNs central nodes
- ANCs access node controllers
- gNB next generation NB
- a gNB or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station or to a UE) and uplink channels (e.g., for transmissions from a UE to a gNB or DU).
- downlink channels e.g., for transmissions from a base station or to a UE
- uplink channels e.g., for transmissions from a UE to a gNB or DU.
- NR e.g., 5G radio access
- LTE long term evolution
- 3GPP 3rd Generation Partnership Project
- CP cyclic prefix
- DL downlink
- UL uplink
- MIMO multiple-input multiple-output
- US 2014/0185534 A1 discloses methods of error control in wireless communications and in particular to the use of hybrid automatic repeat request (HARM) within downlink control channels such as the physical downlink control channel (PDCCH) of Long Term Evolution (LTE) communication systems.
- HARM hybrid automatic repeat request
- PDCCH physical downlink control channel
- US 2015/0270931 A1 discloses a method of decoding of control channels for a User Equipment, UE, to decode a potential control channel, which includes receiving a transmission of a potential control channel in a first subframe from a base station on a first set of control resources, receiving at least one retransmission of the potential control channel in at least one second subframe subsequent to the first subframe from the base station on a second set of control resources, combining the transmission on the first subframe and the at least one retransmission on the at least one subsequent subframe for attempting to decode the potential control channel.
- EP 2 922 225 A1 discloses a method and apparatus for transmitting data and a method and apparatus for receiving data, wherein said methods transmit/receive a reference signal in subframes bundled for data transmission/reception using at least an identical precoding matrix, an identical reference signal sequence, an identical reference signal generating identifier, or an identical reference signal scrambling sequence.
- WO 2017/148510 A1 anticipates a technique that includes transmitting, by a transmitter, a packet during a first time interval via a first set of frequency resources to a receiver in a wireless network; making a decision to retransmit portions of the packet to the receiver over one or more subsequent time intervals; and retransmitting, by the transmitter during each of the one or more subsequent time intervals, a portion of the packet via a second set of frequency resources, wherein each portion of the packet is a subset of the packet, and wherein each second set of frequency resources includes fewer frequency resources than the first set of frequency resources; wherein the retransmitting by the transmitter continues until an acknowledgement, ACK, is received by the transmitter from the receiver that acknowledges receipt of the packet, or a predetermined number of retransmissions of portions of the packet are performed by the transmitter.
- ACK acknowledgement
- Certain aspects of the present disclosure generally relate to methods and apparatus for soft-combining control information.
- Certain aspects of the present disclosure provide a method for wireless communication according to claim 1.
- Certain aspects of the present disclosure provide a method for wireless communication according to claim 9.
- Certain aspects of the present disclosure provide an apparatus for wireless communication according to claim 14.
- the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
- the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
- NR new radio access technology or 5G technology
- NR may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 27 GHz or beyond), massive machine type communications (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC).
- eMBB enhanced mobile broadband
- mmW millimeter wave
- mMTC massive machine type communications
- URLLC ultra-reliable low-latency communications
- These services may include latency and reliability requirements.
- These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements.
- TTI transmission time intervals
- QoS quality of service
- these services may co-exist in the same subframe.
- enhanced machine type communications are supported, targeting low cost devices, often at the cost of lower throughput.
- eMTC may involve half-duplex (HD) operation in which uplink transmissions and downlink transmissions can both be performed-but not simultaneously.
- Some eMTC devices e.g., eMTC UEs
- eMTC UEs may look at (e.g., be configured with or monitor) no more than around 1 MHz or six resource blocks (RBs) of bandwidth at any given time.
- eMTC UEs may be configured to receive no more than around 1000 bits per subframe. For example, these eMTC UEs may support a max throughput of around 300 Kbits per second.
- This throughput may be sufficient for certain eMTC use cases, such as certain activity tracking, smart meter tracking, and/or updates, etc., which may consist of infrequent transmissions of small amounts of data; however, greater throughput for eMTC devices may be desirable for other cases, such as certain Internet-of-Things (IoT) use cases, wearables such as smart watches, etc.
- IoT Internet-of-Things
- a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc.
- UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
- cdma2000 covers IS-2000, IS-95 and IS-856 standards.
- a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM).
- GSM Global System for Mobile Communications
- An OFDMA network may implement a radio technology such as NR (e.g.
- E-UTRA Evolved UTRA
- UMB Ultra Mobile Broadband
- IEEE 802.11 Wi-Fi
- IEEE 802.16 WiMAX
- IEEE 802.20 Flash-OFDMA
- UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).
- NR is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF).
- 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA.
- LTE Long Term Evolution
- LTE-A LTE-Advanced
- UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
- cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
- 3GPP2 3rd Generation Partnership Project 2
- the techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies.
- aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies.
- FIG. 1 illustrates an example wireless network 100 in which aspects of the present disclosure may be performed.
- the wireless network 100 may be a new radio (NR) or 5G network.
- a UE 120 may be configured for enhanced machine type communications (eMTC).
- the UE 120 may be considered a low cost device, low cost UE, eMTC device, and/or eMTC UE.
- the UE 120 can be configured to support higher bandwidth and/or data rates (e.g., higher than 1 MHz).
- the UE 120 may be configured with a plurality of narrowband regions (e.g., 24 resource blocks (RBs) or 96 RBs).
- RBs resource blocks
- the UE 120 may receive a resource allocation, from a gNB 110, allocating frequency hopped resources within a system bandwidth for the UE 120 to monitor and/or transmit on.
- the resource allocation can indicate non-contiguous narrowband frequency resources for uplink transmission in at least one subframe.
- the resource allocation may indicate frequency resources are not contained within a bandwidth capability of the UE to monitor for downlink transmission.
- the UE 120 may determine, based on the resource allocation, different narrowband than the resources indicated in the resource allocation from the gNB 110 for uplink transmission or for monitoring.
- the resource allocation indication (e.g., such as that included in the downlink control information (DCI)) may include a set of allocated subframes, frequency hopping related parameters, and an explicit resource allocation on the first subframe of the allocated subframes.
- DCI downlink control information
- the frequency hopped resource allocation on subsequent subframes are obtained by applying the frequency hopping procedure based on the frequency hopping related parameters (which may also be partly included in the DCI and configured partly through radio resource control (RRC) signaling) starting from the resources allocated on the first subframe of the allocated subframes.
- RRC radio resource control
- the wireless network 100 may include a number of gNBs 110 and other network entities.
- a gNB may be a station that communicates with UEs.
- Each gNB 110 may provide communication coverage for a particular geographic area.
- the term "cell” can refer to a coverage area of a Node B and/or a NB subsystem serving this coverage area, depending on the context in which the term is used.
- the term "cell” and NB, next generation NB (gNB), 5G NB, access point (AP), BS, NR BS, or transmission reception point (TRP) may be interchangeable.
- a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile gNB.
- the gNBs may be interconnected to one another and/or to one or more other gNBs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, or the like using any suitable transport network.
- 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, an air interface, etc.
- a frequency may also be referred to as a carrier, a frequency channel, a tone, a subband, a subcarrier, etc.
- Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
- NR or 5G RAT networks may be deployed.
- a gNB may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell.
- 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 subscription.
- a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
- a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in the home, etc.).
- CSG Closed Subscriber Group
- a gNB for a macro cell may be referred to as a macro gNB.
- a gNB for a pico cell may be referred to as a pico gNB.
- a gNB for a femto cell may be referred to as a femto gNB or a home gNB.
- the gNBs 110a, 110b and 110c may be macro gNBs for the macro cells 102a, 102b and 102c, respectively.
- the gNB 110x may be a pico gNB for a pico cell 102x.
- the gNBs 110y and 110z may be femto gNB for the femto cells 102y and 102z, respectively.
- a gNB may support one or multiple (e.g., three) cells.
- the 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 gNB or a UE) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or a gNB).
- a relay station may also be a UE that relays transmissions for other UEs.
- a relay station 110r may communicate with the gNB 110a and a UE 120r in order to facilitate communication between the gNB 110a and the UE 120r.
- a relay station may also be referred to as a relay gNB, a relay, etc.
- the wireless network 100 may be a heterogeneous network that includes gNBs of different types, e.g., macro gNB, pico gNB, femto gNB, relays, etc. These different types of gNBs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100.
- gNBs of different types, e.g., macro gNB, pico gNB, femto gNB, relays, etc.
- These different types of gNBs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100.
- a macro gNB may have a high transmit power level (e.g., 20 Watts)
- pico gNB, femto gNB, and relays may have a lower transmit power level (e.g., 1 Watt).
- the wireless network 100 may support synchronous or asynchronous operation.
- the gNBs may have similar frame timing, and transmissions from different gNBs may be approximately aligned in time.
- the gNBs may have different frame timing, and transmissions from different gNBs may not be aligned in time.
- the techniques described herein may be used for both synchronous and asynchronous operation.
- a network controller 130 may couple to a set of gNBs and provide coordination and control for these gNBs.
- the network controller 130 may communicate with the gNBs 110 via a backhaul.
- the gNBs 110 may also communicate with one another, for example, directly or indirectly via wireless or wireline backhaul.
- the UEs 120 may be dispersed throughout the 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 Customer Premises Equipment (CPE), a cellular phone, 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, 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 smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a
- CPE Customer Premises Equipment
- Some UEs may be considered evolved or machine-type communication (MTC) devices or evolved MTC (eMTC) devices.
- MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a gNB, another device (e.g., remote device), or some other entity.
- a wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link.
- Some UEs may be considered Internet-of-Things (IoT) devices or narrowband IoT (NB-IoT) devices.
- IoT Internet-of-Things
- NB-IoT narrowband IoT
- a solid line with double arrows indicates desired transmissions between a UE and a serving gNB, which is a gNB designated to serve the UE on the downlink and/or uplink.
- a finely dashed line with double arrows indicates interfering transmissions between a UE and a gNB.
- Certain wireless networks 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, etc.
- K orthogonal subcarriers
- Each subcarrier may be modulated with data.
- modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM.
- the spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth.
- the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (e.g., an RB) may be 12 subcarriers (or 180 kHz). Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz), respectively.
- the system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.8 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.
- aspects of the examples described herein may be associated with LTE technologies, aspects of the present disclosure may be applicable with other wireless communications systems, such as NR.
- NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using TDD.
- a single component carrier bandwidth of 100 MHz may be supported.
- NR resource blocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1 ms duration.
- Each radio frame may consist of two half frames, each half frame consisting of 5 subframes, with a length of 10 ms. Consequently, each subframe may have a length of 1 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 as described in more detail below with respect to FIGs. 6 and 7 .
- Beamforming may be supported and beam direction may be dynamically configured.
- MIMO transmissions with precoding may also be supported.
- MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE.
- Multi-layer transmissions with up to 2 streams per UE may be supported.
- Aggregation of multiple cells may be supported with up to 8 serving cells.
- the basic transmission time interval (TTI) or packet duration is the 1 subframe.
- TTI transmission time interval
- a subframe is still 1 ms, but the basic TTI is referred to as a slot.
- a subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16,... slots) depending on the tone-spacing (e.g., 15, 30, 60, 120, 240... kHz).
- a scheduling entity e.g., a gNB
- the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity.
- gNBs are not the only entities that may function 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 functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication.
- a UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network. In a mesh network example, UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
- P2P peer-to-peer
- a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources.
- 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 .
- a 5G access node 206 may include an access node controller (ANC) 202.
- the ANC 202 may be a central unit (CU) of the distributed RAN 200.
- the backhaul interface to the next generation core network (NG-CN) 204 may terminate at the ANC 202.
- the backhaul interface to neighboring next generation access nodes (NG-ANs) 210 may terminate at the ANC 202.
- the ANC 202 may include one or more TRPs 208 (which may also be referred to as BSs, NR BSs, gNBs, or some other term).
- the TRPs 208 may be a DU.
- the TRPs may be connected to one ANC (ANC 202) or more than one ANC (not illustrated).
- ANC 202 ANC 202
- RaaS radio as a service
- a TRP may include one or more antenna ports.
- the TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.
- the logical architecture of the distributed RAN 200 may support fronthauling solutions across different deployment types.
- the logical architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter).
- the logical architecture may share features and/or components with LTE.
- the NG-AN 210 may support dual connectivity with NR.
- the NG-AN 210 may share a common fronthaul for LTE and NR.
- the logical architecture may enable cooperation between and among TRPs 208. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC 202. An inter-TRP interface may be present.
- the logical architecture of the distributed RAN 200 may support a dynamic configuration of split logical functions.
- the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layers may be adaptably placed at the DU or CU (e.g., TRP or ANC, respectively).
- RRC Radio Resource Control
- PDCP Packet Data Convergence Protocol
- RLC Radio Link Control
- MAC Medium Access Control
- PHY Physical
- FIG. 3 illustrates an example physical architecture of a distributed RAN 300, according to aspects of the present disclosure.
- a centralized core network unit (C-CU) 302 may host core network functions.
- the C-CU 302 may be centrally deployed.
- C-CU functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity.
- AWS advanced wireless services
- a centralized RAN unit (C-RU) 304 may host one or more ANC functions.
- the C-RU 304 may host core network functions locally.
- the C-RU 304 may have distributed deployment.
- the C-RU 304 may be closer to the network edge.
- a DU 306 may host one or more TRPs (e.g., an edge node (EN), an edge unit (EU), a radio head (RH), a smart radio head (SRH), or the like).
- the DU may be located at edges of the network with radio frequency (RF) functionality.
- RF radio frequency
- FIG. 4 illustrates example components of the gNB 110 and UE 120 illustrated in FIG. 1 , which may be used to implement aspects of the present disclosure for frequency hopping for large bandwidth allocations.
- antennas 452, Tx/Rx 222, processors 466, 458, 464, and/or controller/processor 480 of the UE 120 and/or antennas 434, processors 460, 420, 438, and/or controller/processor 440 of the gNB 110 may be used to perform the operations described herein and illustrated with reference to FIGs. 9-11 .
- FIG. 4 shows a block diagram of a design of a gNB 110 and a UE 120, which may be one of the gNBs and one of the UEs in FIG. 1 .
- the gNB 110 may be the macro gNB 110c in FIG. 1
- the UE 120 may be the UE 120y.
- the gNB 110 may also be gNB of some other type.
- the gNB 110 may be equipped with antennas 434a through 434t, and the UE 120 may be equipped with antennas 452a through 452r.
- 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 for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), etc.
- the data may be for the Physical Downlink Shared Channel (PDSCH), etc.
- the processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively.
- the processor 420 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal (CRS).
- CRS cell-specific reference signal
- 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 the modulators (MODs) 432a through 432t.
- 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 the antennas 434a through 434t, respectively.
- the antennas 452a through 452r may receive the downlink signals from the gNB 110 and may provide received signals to the 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 the demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
- 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.
- a transmit processor 464 may receive and process data (e.g., for the Physical Uplink Shared Channel (PUSCH)) from a data source 462 and control information (e.g., for the Physical Uplink Control Channel (PUCCH) from the controller/processor 480.
- 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 gNB 110.
- the uplink signals from the UE 120 may be received by the antennas 434, processed by the 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 the UE 120.
- the receive processor 438 may provide the decoded data to a data sink 439 and the decoded control information to the controller/processor 440.
- the controllers/processors 440 and 480 may direct the operation at the gNB 110 and the UE 120, respectively.
- the processor 440 and/or other processors and modules at the gNB 110 may perform or direct, e.g., the execution of various processes for the techniques described herein.
- the processor 480 and/or other processors and modules at the UE 120 may also perform or direct, e.g., the execution of the functional blocks illustrated in FIGs. 9 and 11 , and/or other processes for the techniques described herein.
- the processor 440 and/or other processors and modules at the gNB 110 may also perform or direct, e.g., the execution of the functional blocks illustrated in FIG. 10 , and/or other processes for the techniques described herein.
- the memories 442 and 482 may store data and program codes for the gNB 110 and the 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 examples for implementing a communications protocol stack, according to aspects of the present disclosure.
- the illustrated communications protocol stacks may be implemented by devices operating in a in a 5G system (e.g., a system that supports uplink-based mobility).
- Diagram 500 illustrates a communications 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.
- RRC Radio Resource Control
- PDCP Packet Data Convergence Protocol
- RLC Radio Link Control
- MAC Medium Access Control
- PHY Physical
- the layers of a protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device (e.g., ANs, CUs, and/or DUs) or a UE.
- a network access device e.g., ANs, CUs, and/or DUs
- a first option 505-a shows a split implementation of a protocol stack, in which implementation of the protocol stack is split between a centralized network access device (e.g., an ANC 202 in FIG. 2 ) and distributed network access device (e.g., DU 208 in FIG. 2 ).
- a centralized network access device e.g., an ANC 202 in FIG. 2
- distributed network access device e.g., DU 208 in FIG. 2
- an RRC layer 510 and a PDCP layer 515 may be implemented by the central unit
- an RLC layer 520, a MAC layer 525, and a PHY layer 530 may be implemented by the DU.
- the CU and the DU may be collocated or non-collocated.
- the first option 505-a may be useful in a macro cell, micro cell, or pico cell deployment.
- a second option 505-b shows a unified implementation of a protocol stack, in which the protocol stack is implemented in a single network access device (e.g., access node (AN), new radio base station (NR BS), a new radio Node-B (NR NB), a network node (NN), or the like.).
- the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 may each be implemented by the AN.
- the second option 505-b may be useful in a femto cell deployment.
- a UE may implement an entire protocol stack (e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530).
- an entire protocol stack e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530.
- FIG. 6 is a diagram showing an example format of a DL-centric subframe 600.
- the DL-centric subframe 600 may include a control portion 602.
- the control portion 602 may exist in the initial or beginning portion of the DL-centric subframe 600.
- the control portion 602 may include various scheduling information and/or control information corresponding to various portions of the DL-centric subframe 600.
- the control portion 602 may be a physical DL control channel (PDCCH), as indicated in FIG. 6 .
- the DL-centric subframe 600 may also include a DL data portion 604.
- the DL data portion 604 may sometimes be referred to as the payload of the DL-centric subframe 600.
- the DL data portion 604 may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or gNB) to the subordinate entity (e.g., UE).
- the DL data portion 604 may be a physical DL shared channel (PDSCH).
- PDSCH physical DL shared channel
- the DL-centric subframe 600 may also include a common UL portion 606.
- the 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 subframe.
- the common UL portion 606 may include feedback information corresponding to the control portion 602.
- Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information.
- the common UL portion 606 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs), and various other suitable types of information.
- RACH random access channel
- SRs scheduling requests
- 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, a guard period, a guard interval, and/or various other suitable terms.
- This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE)) to UL communication (e.g., transmission by the subordinate entity (e.g., UE)).
- DL communication e.g., reception operation by the subordinate entity (e.g., UE)
- UL communication e.g., transmission by the subordinate entity (e.g., UE)
- FIG. 7 is a diagram showing an example format of an UL-centric subframe 700.
- the UL -centric subframe 700 may include a control portion 702.
- the control portion 702 may exist in the initial or beginning portion of the UL-centric subframe 700.
- the control portion 702 in FIG. 7 may be similar to the control portion 602 described above with reference to FIG. 6 .
- the UL-centric subframe 700 may also include an UL data portion 704.
- the UL data portion 704 may sometimes be referred to as the payload of the UL-centric subframe 700.
- the UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or gNB).
- the control portion 702 may be a PDCCH.
- 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 separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity).
- the UL-centric subframe 700 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 .
- the common UL portion 706 may additional or alternative include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), and various other suitable types of information.
- CQI channel quality indicator
- SRSs sounding reference signals
- One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric subframe 700 and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.
- two or more subordinate entities may communicate with each other using sidelink signals.
- Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Intemet-of-Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications.
- a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or gNB), even though the scheduling entity may be utilized for scheduling and/or control purposes.
- the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).
- a UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc.).
- RRC radio resource control
- the UE may select a dedicated set of resources for transmitting a pilot signal to a network.
- the UE may select a common set of resources for transmitting a pilot signal to the network.
- a pilot signal transmitted by the UE may be received by one or more network access devices, such as an AN, or a DU, or portions thereof.
- Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE.
- One or more of the receiving network access devices, or a CU to which receiving network access device(s) transmit the measurements of the pilot signals may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs.
- New radio may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP)).
- NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC) service.
- the RAN may include a central unit (CU) and distributed units (DUs).
- a NR Node B e.g., 5G Node B
- TRPs transmission reception points
- Ultra-reliability low latency communication generally refers to relatively tight (e.g., stringent) requirements for successful delivery of a packet within a stringent deadline (e.g., 1 ms) with very high probability (e.g., 99.999%) of success.
- the reliability of a downlink (DL) transmission depends on the reliability of both the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH).
- the reliability of the PDSCH can be improved with the use of hybrid automatic repeat request (HARQ) (or automatic repeat request (ARQ)) that allows the receiver to combine different copies of the same data packet.
- HARQ hybrid automatic repeat request
- ARQ automatic repeat request
- the PDSCH packet data packet
- the control packet becomes the bottleneck of the overall communication.
- Certain aspects of the present disclosure provide apparatus and techniques for improving the reliability of PDCCH by repetition and spreading.
- FIG. 8 illustrates example operations 800 for wireless communication, in accordance with certain aspects of the present disclosure.
- the operations 800 are performed, for example, by a user-equipment (UE), such as the UE 120.
- UE user-equipment
- the operations 800 begin, at block 802, by monitoring for control information (e.g., downlink control information (DCI)) in each of a plurality of PDCCHs during a different one of a plurality of time intervals (e.g., a slot or mini-slot).
- control information e.g., downlink control information (DCI)
- the PDCCHs contain the same control information that indicates a resource allocation within a respective one of the time intervals for receiving one of a plurality of PDSCHs.
- the data in each of the plurality of PDSCHs is the same.
- the operations 800 continue by soft-combining the plurality of PDCCHs to decode the control information, and at block 806, decoding the control information based on the soft-combination of the plurality of PDCCHs.
- the operations 800 also include receiving each of the plurality of PDSCHs in a respective one of the plurality of time intervals, soft-combining the plurality of PDSCHs, and decoding data within the plurality of PDSCHs based on the soft-combination of the plurality of PDSCHs and the resource allocation.
- FIG. 9 illustrates example operations 900 for wireless communication, in accordance with certain aspects of the present disclosure.
- the operations 900 are performed, for example, by a base station (e.g., gNB), such as the gNB 110.
- a base station e.g., gNB
- gNB base station
- the operations 900 begin, at block 902, by determining a resource allocation within each of a plurality of time intervals for transmitting a respective one of a plurality of PDSCHs.
- the resource allocation may be the same within each of the plurality of time intervals.
- data in each of the plurality of PDSCHs is the same.
- the operations continue by transmitting control information in each of a plurality of PDCCHs, each of the PDCCHs being transmitted during one of the plurality of time intervals.
- the PDCCHs have the same control information that indicates the resource allocation within respective one of the plurality of time intervals.
- each of the plurality of PDSCHs is transmitted during one of the plurality of time intervals based on the resource allocation.
- the operations 800 and 900 are described in more detail below with respect to FIGs. 10-14 .
- FIG. 10 illustrates a flow diagram 1000 for transmitting a PDCCH and a PDSCH, in accordance with certain aspects of the present application.
- a DCI 1002 may be generated including a resource allocation for a PDSCH, and a cyclic redundancy check (CRC) 1004 may be appended onto the DCI, as illustrated.
- CRC cyclic redundancy check
- channel coding and rate matching may be performed, after which a PDCCH 1008 is generated having the DCI 1002 and CRC 1004.
- the PDCCH is repeated into K copies to generate PDCCH 1, PDCCH 2, to PDCCH K, as illustrated, each of which are scrambled at blocks 1018, 1020, and 1022, respectively.
- all the PDCCHs contain the same control information (e.g., point to the same PDSCH resources).
- the copies of the PDCCHs and PDSCHs are transmitted during different time intervals 1024, 1026, and 1028, each of which may correspond to a slot (e.g., 14 OFDM symbols) or a mini-slot (e.g., 2, 4, or 7 OFDM symbols).
- the PDCCH scrambling in different time intervals may use the same or different sequences, as will be described in more detail herein.
- the PDSCHs transmitted during the different time intervals 1024, 1026, and 1028 may be either repetitions of the same data packet, or are different self-decodable redundancy versions (RVs) of the same data packet, with a pre-defined redundancy version (RV) pattern over K repetitions.
- RVs self-decodable redundancy versions
- RV redundancy version
- the RVs are communicated to the UE by modulating each of the respective RVs on the demodulation reference signal (DMRS) for the corresponding PDSCH, or modulating the respective RVs on the scrambling sequence.
- the RV index may be mapped to a scrambling sequence index used to scramble the PDCCH.
- the index of the sequence also indicates the RV corresponding to the PDSCH.
- the index of a sequence used to scramble PDCCH 1 may correspond to an index of an RV of the PDSCH in the time interval 1024, and so on.
- the UE may be configured with PDCCH monitoring periodicity (e.g., slot/mini-slot) based on a number of PDCCH repetitions K. For example, the UE may be configured to monitor for PDCCH in each of K time intervals (e.g., slots or mini-slots). Thus, the UE monitors the PDCCH according to the configured PDCCH monitoring periodicity. If the PDCCH monitoring periodicity is, for example, one mini-slot, depending on whether PDCCH scrambling uses the same or different scrambling sequences, the UE may perform different operations within each mini-slot.
- PDCCH monitoring periodicity e.g., slot/mini-slot
- the UE may decode the PDCCH in time interval n, assuming that the PDCCH in time interval n is the first PDCCH transmission.
- the UE may soft-combine the PDCCH in time interval n with a PDCCH received during time interval n-1 assuming that the first PDCCH transmission is in time interval n-1.
- the UE may soft-combine the PDCCH in time interval n with PDCCHs from time interval n-K+1 to n-1, assuming that the first PDCCH transmission is in time interval n-K+1.
- the K operations may be performed in parallel or in a serial fashion.
- the UE may only perform some of the K operations based on the UE capability. In other words, since all the PDCCHs may include the same DCI, the UE may perform less than the K operations. For example, the UE may only combine at most two PDCCHs (e.g., may soft-combine PDCCHs received in time interval n and n-1).
- each of the operations (i.e., decoding attempts) described herein may be counted as a blind decode.
- the total number of blind decodes in a given time interval may not exceed a target threshold.
- the target threshold may correspond to the maximum number of blind decodes a UE is able to perform in the given time interval.
- the number of operations that the UE performs to decode a given DCI may be determined based on the target threshold.
- FIG. 11 is a table 1100 illustrating operations that may be performed by a UE for decoding PDCCHs that are scrambled using different sequences, in accordance with certain aspects of the present disclosure.
- Each entry (excluding the entries in the first column) in the table 1100 corresponds to one UE operation.
- the first entry in the second row may indicate the time interval indices (e.g., n-1 and n) in which PDCCH packets are to be soft-combined and the corresponding scrambling sequence indices.
- the PDCCH in time interval index n-1 is scrambled by scrambling sequence index 1
- the PDCCH in time interval index n is scrambled by scrambling sequence index 2.
- the UE may perform the K operations listed in one column (e.g., the second column of table 1100), or may perform the operations listed across m rows of the table 1100, where m is less than the K total number of rows.
- the operations performed by the UE may be performed either in parallel or in a serial fashion depending on the UEs capabilities.
- Each of the operations (e.g.,, decoding attempts) described herein may be counted as a blind decode.
- the total number of blind decodes in a given time interval may not exceed a target threshold corresponding to the maximum number of blind decodes a UE is able to perform in a given time interval.
- the number of operations that the UE performs in table 1100 for a given DCI may be determined based on the target threshold. If any of the operations previously described for decoding the PDCCH results in successful decoding (e.g., the decoded PDCCH passes CRC check performed based on the CRC 1004), then the UE may then proceed to decoding the PDSCH.
- the PDSCHs transmitted during the time intervals 1024, 1026 and 1028 may be repetitions of the same data packets.
- the UE soft-combines k of the PDSCHs, where k corresponds to the number of PDCCHs that were soft-combined to successfully decode the PDCCH.
- the UE may soft-combine the PDSCHs from time interval n-k+1 to time interval n.
- the PDSCHs transmitted during the time intervals 1024, 1026 and 1028 are different RVs of the same data packet.
- the UE determines the RV of the PDSCH based on the modulation of the DMRS, or in accordance with the scrambling sequence for the PDCCH, as previously described, and subsequently soft-combine the corresponding PDSCHs based on determined RVs.
- the UE may provide feedback to the gNB after each of the time intervals (e.g., slots or mini-slots) to indicate whether the PDCCH and the PDSCH were successfully decoded. For example, if the UE decodes both PDCCH and PDSCH in a first time interval, then the UE may feedback an acknowledgement (ACK) indicating that the PDSCH was successfully decoded. In this case, the gNB may terminate any following PDCCH and PDSCH transmissions in subsequent time intervals. In certain aspects, if the UE does not successfully decode the PDCCH, the UE may not provide any feedback to the gNB. In this case, the gNB may retransmit both the PDCCH and the PDSCH in the subsequent time interval (e.g., mini-slot 2 as described with respect to FIG. 10 ).
- the time intervals e.g., slots or mini-slots
- the UE may feedback a negative acknowledgement (NACK) indicating that the PDSCH was not successfully decoded.
- NACK negative acknowledgement
- the gNB may terminate transmission of the PDCCH in any subsequent time intervals, but continue the transmission of the PDSCH using the same resources as indicated by the previously transmitted, and successfully decoded, PDCCH. In some cases, the gNB may continue to transmit both the PDCCH and PDSCH after receiving a NACK.
- the gNB may terminate both PDCCH and PDSCH transmissions after receiving a NACK, and may reschedule a new PDSCH retransmission and a new PDCCH indicating new resources for the rescheduled PDSCH.
- FIG. 12 illustrates a flow diagram 1200 for transmitting multiple RVs of a PDCCH, in accordance with certain aspects of the present application.
- the gNB may segment, at block 1210, the PDCCH into K equal-sized self-decodable packets having different RVs, and transmit K RVs of the PDCCH (e.g., PDCCH RV1, PDCCH RV2, to PDCCH RV K), as illustrated.
- the UE monitors for the PDCCH during each time interval (e.g., slot or mini-slot) to decode the control information in the PDCCH assuming each of the plurality of RVs, as described with respect to FIG. 13 .
- time interval e.g., slot or mini-slot
- FIG. 13 is a table 1300 illustrating operations that may be performed by a UE for decoding PDCCHs having different RVs, in accordance with certain aspects of the present disclosure. Similar to table 1100, each entry (excluding the entries in the first column) in the table 1300 corresponds to one UE operation. For example, the first element in the second row indicates the time interval indices (e.g., n-1 and n) in which PDCCH packets are to be soft-combined and the corresponding RV indices (e.g., RV index 1 corresponds to mini-slot index n-1, and RV index 2 corresponds to the mini-slot index n).
- time interval indices e.g., n-1 and n
- RV index 1 corresponds to mini-slot index n-1
- RV index 2 corresponds to the mini-slot index n
- the UE may perform the K operations listed in one column (e.g., the first column of table 1300), or may perform the operations listed across m rows of the table 1300, where m is less than the K total number of rows.
- the operations performed by the UE may be performed either in parallel or in a serial fashion depending on the UEs capabilities.
- Each of the operations (e.g., decoding attempts) described herein may be counted as a blind decode.
- the total number of blind decodes in a given time interval may not exceed a target threshold corresponding to a maximum number of blind decodes a UE is able to perform in a given time interval.
- the number of operations that the UE performs in the table 1300 for a given DCI may be determined based on the target threshold. If any of the operations described herein for decoding the PDCCH results in successful decoding (e.g., the decoded PDCCH passes CRC check performed based on the CRC 1004), then the UE may then proceed to decoding the PDSCH.
- FIG. 14 illustrates a flow diagram 1400 for transmitting multiple RVs of a PDCCH having different sizes, in accordance with certain aspects of the present application.
- the gNB may segment, at block 1410, the PDCCH into K unequal-sized self-decodable packets having different RVs, as illustrated.
- the size of the PDCCH RVs may follow a pre-defined pattern that may be known by the both the gNB and the UE such that the UE can decode the PDCCH RVs based on the defined pattern.
- the size of the PDCCH RV1 may be one control channel element (CCE)
- the size of the PDCCH RV2 may be one CCE
- the size of the PDCCH RV3 may be two CCEs
- the size of the PDCCH RV4 may be two CCEs
- the PDSCHs transmitted in each of the time intervals 1024, 1026, and 1028 may also have different sizes and follow a pre-defined pattern known by both the gNB and the UE.
- 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.
- the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
- a phrase referring to "at least one of' a list of items refers to any combination of those items, including single members.
- "at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).
- determining encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, 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 various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
- the means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor.
- ASIC application specific integrated circuit
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- PLD programmable logic device
- 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.
- an example hardware configuration may comprise a processing system in a 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 a processor, machine-readable media, and a bus interface.
- the bus interface may be used to connect a network adapter, among other things, to the processing system via the bus.
- the network adapter may be used to implement the signal processing functions of the PHY layer.
- a user interface e.g., keypad, display, mouse, joystick, etc.
- 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.
- the processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system.
- the functions may be stored or transmitted over as one or more instructions or code on a computer-readable medium.
- Software shall 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 include 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 media.
- a computer-readable storage medium may be coupled to a 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.
- the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface.
- the machine-readable media, or any portion thereof may be integrated into the processor, such as the case may be with cache and/or general register files.
- machine-readable storage media may include, by way of example, 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 disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
- RAM Random Access Memory
- ROM Read Only Memory
- PROM PROM
- EPROM Erasable Programmable Read-Only Memory
- EEPROM Electrical Erasable Programmable Read-Only Memory
- registers magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
- the machine-readable media 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 media may comprise a number of software modules.
- the software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions.
- the software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices.
- a software module may be loaded into RAM from a hard drive when a triggering event occurs.
- the processor may load some of the instructions into cache to increase access speed.
- One or more cache lines may then be loaded into a general register file for execution by the processor.
- any connection is properly termed a computer-readable medium.
- the software is transmitted from a website, 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
- 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 and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray ® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
- computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media).
- computer-readable media may comprise transitory computer-readable media (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.
- certain aspects may comprise a computer program product for performing the operations presented herein.
- a computer program product may comprise 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.
- 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 as applicable.
- a user terminal and/or base station can be coupled to a server to facilitate the transfer of means for performing the methods described herein.
- various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device.
- storage means e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.
- CD compact disc
- floppy disk etc.
- any other suitable technique for providing the methods and techniques described herein to a device can be utilized.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Description
- Aspects of the present disclosure relate generally to wireless communications systems, methods as well as apparatus, and more particularly, to soft combining of control information.
- Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth and transmit power). Examples of such multiple-access systems include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) systems, 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, and time division synchronous code division multiple access (TD-SCDMA) systems.
- In some examples, a wireless multiple-access communication system may include a number of base stations (BSs) that each can simultaneously support communication for multiple communication devices, otherwise known as user equipment (UEs). In LTE or LTE-A network, a set of one or more gNBs may define an e NodeB (eNB). In other examples (e.g., in a next generation, new radio (NR), or 5G network), a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with a number of central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a set of one or more distributed units, in communication with a central unit, may define an access node (e.g., a NR BS, a NR NB, a network node, a 5G NB, a next generation NB (gNB), etc.). A gNB or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station or to a UE) and uplink channels (e.g., for transmissions from a UE to a gNB or DU).
- These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. NR (e.g., 5G radio access) is an example of an emerging telecommunication standard. NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP. It is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL) as well as support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
- However, as the demand for mobile broadband access continues to increase, there exists a need for further improvements in NR and LTE technology. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
-
US 2014/0185534 A1 discloses methods of error control in wireless communications and in particular to the use of hybrid automatic repeat request (HARM) within downlink control channels such as the physical downlink control channel (PDCCH) of Long Term Evolution (LTE) communication systems.US 2015/0270931 A1 discloses a method of decoding of control channels for a User Equipment, UE, to decode a potential control channel, which includes receiving a transmission of a potential control channel in a first subframe from a base station on a first set of control resources, receiving at least one retransmission of the potential control channel in at least one second subframe subsequent to the first subframe from the base station on a second set of control resources, combining the transmission on the first subframe and the at least one retransmission on the at least one subsequent subframe for attempting to decode the potential control channel. QUALCOMM INCORPORATED: "NB-PBCH design", 3GPP DRAFT R1-160875 of February 14, 2016 discusses views on the PBCH and MIB for NB-IoT for MTC.EP 2 922 225 A1WO 2017/148510 A1 anticipates a technique that includes transmitting, by a transmitter, a packet during a first time interval via a first set of frequency resources to a receiver in a wireless network; making a decision to retransmit portions of the packet to the receiver over one or more subsequent time intervals; and retransmitting, by the transmitter during each of the one or more subsequent time intervals, a portion of the packet via a second set of frequency resources, wherein each portion of the packet is a subset of the packet, and wherein each second set of frequency resources includes fewer frequency resources than the first set of frequency resources; wherein the retransmitting by the transmitter continues until an acknowledgement, ACK, is received by the transmitter from the receiver that acknowledges receipt of the packet, or a predetermined number of retransmissions of portions of the packet are performed by the transmitter. - The systems, methods, and devices of the disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure as expressed by the claims which follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled "Detailed Description" one will understand how the features of this disclosure provide advantages that include improved communications between access points and stations in a wireless network.
- Certain aspects of the present disclosure generally relate to methods and apparatus for soft-combining control information.
- Certain aspects of the present disclosure provide a method for wireless communication according to
claim 1. - Certain aspects of the present disclosure provide a method for wireless communication according to claim 9.
- Certain aspects of the present disclosure provide an apparatus for wireless communication according to claim 14.
- To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
- So that the manner in which the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.
-
FIG. 1 is a block diagram conceptually illustrating an example telecommunications system, in accordance with certain aspects of the present disclosure. -
FIG. 2 is a block diagram illustrating an example logical architecture of a distributed radio access network (RAN), in accordance with certain aspects of the present disclosure. -
FIG. 3 is a diagram illustrating an example physical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure. -
FIG. 4 is a block diagram conceptually illustrating a design of an example base station (BS) and user equipment (UE), in accordance with certain aspects of the present disclosure. -
FIG. 5 is a diagram showing examples for implementing a communication protocol stack, in accordance with certain aspects of the present disclosure. -
FIG. 6 illustrates an example of a downlink-centric subframe, in accordance with certain aspects of the present disclosure. -
FIG. 7 illustrates an example of an uplink-centric subframe, in accordance with certain aspects of the present disclosure. -
FIG. 8 illustrates example operations for wireless communication by a UE, in accordance with certain aspects of the present disclosure. -
FIG. 9 illustrates example operations for wireless communication by a gNB, in accordance with certain aspects of the present disclosure. -
FIG. 10 illustrates a flow diagram for transmitting a physical downlink control channel (PDCCH), in accordance with certain aspects of the present application. -
FIG. 11 is a table illustrating operations that may be performed by a UE for decoding PDCCHs that are scrambled using different sequences, in accordance with certain aspects of the present disclosure. -
FIG. 12 illustrates a flow diagram for transmitting multiple redundancy versions (RVs) of a PDCCH, in accordance with certain aspects of the present application. -
FIG. 13 is a table illustrating operations that may be performed by a UE for decoding PDCCHs having different RVs, in accordance with certain aspects of the present disclosure. -
FIG. 14 illustrates a flow diagram for transmitting multiple RVs of a PDCCH having different sizes, in accordance with certain aspects of the present application. - To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation.
- Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for NR (new radio access technology or 5G technology). NR may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 27 GHz or beyond), massive machine type communications (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC). These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements. In addition, these services may co-exist in the same subframe.
- In certain systems, (e.g., 3GPP Release-13 long term evolution (LTE) networks), enhanced machine type communications (eMTC) are supported, targeting low cost devices, often at the cost of lower throughput. eMTC may involve half-duplex (HD) operation in which uplink transmissions and downlink transmissions can both be performed-but not simultaneously. Some eMTC devices (e.g., eMTC UEs) may look at (e.g., be configured with or monitor) no more than around 1 MHz or six resource blocks (RBs) of bandwidth at any given time. eMTC UEs may be configured to receive no more than around 1000 bits per subframe. For example, these eMTC UEs may support a max throughput of around 300 Kbits per second. This throughput may be sufficient for certain eMTC use cases, such as certain activity tracking, smart meter tracking, and/or updates, etc., which may consist of infrequent transmissions of small amounts of data; however, greater throughput for eMTC devices may be desirable for other cases, such as certain Internet-of-Things (IoT) use cases, wearables such as smart watches, etc.
- The following description provides examples, and is not limiting of 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. It should be understood that any aspect of the disclosure disclosed herein may be embodied 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 a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology 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, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). NR is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization named "3rd
Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies. -
FIG. 1 illustrates anexample wireless network 100 in which aspects of the present disclosure may be performed. For example, thewireless network 100 may be a new radio (NR) or 5G network. AUE 120 may be configured for enhanced machine type communications (eMTC). TheUE 120 may be considered a low cost device, low cost UE, eMTC device, and/or eMTC UE. TheUE 120 can be configured to support higher bandwidth and/or data rates (e.g., higher than 1 MHz). TheUE 120 may be configured with a plurality of narrowband regions (e.g., 24 resource blocks (RBs) or 96 RBs). TheUE 120 may receive a resource allocation, from agNB 110, allocating frequency hopped resources within a system bandwidth for theUE 120 to monitor and/or transmit on. The resource allocation can indicate non-contiguous narrowband frequency resources for uplink transmission in at least one subframe. The resource allocation may indicate frequency resources are not contained within a bandwidth capability of the UE to monitor for downlink transmission. TheUE 120 may determine, based on the resource allocation, different narrowband than the resources indicated in the resource allocation from thegNB 110 for uplink transmission or for monitoring. The resource allocation indication (e.g., such as that included in the downlink control information (DCI)) may include a set of allocated subframes, frequency hopping related parameters, and an explicit resource allocation on the first subframe of the allocated subframes. The frequency hopped resource allocation on subsequent subframes are obtained by applying the frequency hopping procedure based on the frequency hopping related parameters (which may also be partly included in the DCI and configured partly through radio resource control (RRC) signaling) starting from the resources allocated on the first subframe of the allocated subframes. - As illustrated in
FIG. 1 , thewireless network 100 may include a number ofgNBs 110 and other network entities. A gNB may be a station that communicates with UEs. EachgNB 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 NB subsystem serving this coverage area, depending on the context in which the term is used. In NR systems, the term "cell" and NB, next generation NB (gNB), 5G NB, access point (AP), BS, NR BS, or transmission reception point (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 gNB. In some examples, the gNBs may be interconnected to one another and/or to one or more other gNBs or network nodes (not shown) in thewireless network 100 through 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, an air interface, etc. A frequency may also be referred to as a carrier, a frequency channel, a tone, a subband, a subcarrier, etc. Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
- A gNB may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell. 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 subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in the home, etc.). A gNB for a macro cell may be referred to as a macro gNB. A gNB for a pico cell may be referred to as a pico gNB. A gNB for a femto cell may be referred to as a femto gNB or a home gNB. In the example shown in
FIG. 1 , thegNBs macro cells gNB 110x may be a pico gNB for apico cell 102x. ThegNBs 110y and 110z may be femto gNB for thefemto cells - The
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 gNB or a UE) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or a gNB). A relay station may also be a UE that relays transmissions for other UEs. In the example shown inFIG. 1 , arelay station 110r may communicate with thegNB 110a and aUE 120r in order to facilitate communication between thegNB 110a and theUE 120r. A relay station may also be referred to as a relay gNB, a relay, etc. - The
wireless network 100 may be a heterogeneous network that includes gNBs of different types, e.g., macro gNB, pico gNB, femto gNB, relays, etc. These different types of gNBs may have different transmit power levels, different coverage areas, and different impact on interference in thewireless network 100. For example, a macro gNB may have a high transmit power level (e.g., 20 Watts) whereas pico gNB, femto gNB, and relays may have a lower transmit power level (e.g., 1 Watt). - The
wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the gNBs may have similar frame timing, and transmissions from different gNBs may be approximately aligned in time. For asynchronous operation, the gNBs may have different frame timing, and transmissions from different gNBs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation. - A
network controller 130 may couple to a set of gNBs and provide coordination and control for these gNBs. Thenetwork controller 130 may communicate with thegNBs 110 via a backhaul. ThegNBs 110 may also communicate with one another, for example, directly or indirectly via wireless or wireline backhaul. - The UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the
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 Customer Premises Equipment (CPE), a cellular phone, 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, 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 smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is 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, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a gNB, another device (e.g., remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet-of-Things (IoT) devices or narrowband IoT (NB-IoT) devices. - In
FIG. 1 , a solid line with double arrows indicates desired transmissions between a UE and a serving gNB, which is a gNB designated to serve the UE on the downlink and/or uplink. A finely dashed line with double arrows indicates interfering transmissions between a UE and a gNB. - Certain 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, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (e.g., an RB) may be 12 subcarriers (or 180 kHz). Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.8 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.
- While aspects of the examples described herein may be associated with LTE technologies, aspects of the present disclosure may be applicable with other wireless communications systems, such as NR.
- NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using TDD. A single component carrier bandwidth of 100 MHz may be supported. NR resource blocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1 ms duration. Each radio frame may consist of two half frames, each half frame consisting of 5 subframes, with a length of 10 ms. Consequently, each subframe may have a length of 1 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 as described in more detail below with respect to
FIGs. 6 and 7 . Beamforming may be supported and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells. - In LTE, the basic transmission time interval (TTI) or packet duration is the 1 subframe. In NR, a subframe is still 1 ms, but the basic TTI is referred to as a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16,... slots) depending on the tone-spacing (e.g., 15, 30, 60, 120, 240... kHz).
- In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a gNB) allocates resources for communication among some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity. gNBs are not the only entities that may function 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 functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication. A UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network. In a mesh network example, UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
- Thus, in a wireless communication network with a scheduled access to timefrequency 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.
-
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 inFIG. 1 . A5G access node 206 may include an access node controller (ANC) 202. TheANC 202 may be a central unit (CU) of the distributedRAN 200. The backhaul interface to the next generation core network (NG-CN) 204 may terminate at theANC 202. The backhaul interface to neighboring next generation access nodes (NG-ANs) 210 may terminate at theANC 202. TheANC 202 may include one or more TRPs 208 (which may also be referred to as BSs, NR BSs, gNBs, or some other term). - The
TRPs 208 may be a DU. The TRPs 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, theTRP 208 may be connected to more than one ANC. A TRP may include one or more antenna ports. The TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE. - The logical architecture of the distributed
RAN 200 may support fronthauling solutions across different deployment types. For example, the logical architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter). The logical architecture may share features and/or components with LTE. The NG-AN 210 may support dual connectivity with NR. The NG-AN 210 may share a common fronthaul for LTE and NR. The logical architecture may enable cooperation between and amongTRPs 208. For example, cooperation may be preset within a TRP and/or across TRPs via theANC 202. An inter-TRP interface may be present. - The logical architecture of the distributed
RAN 200 may support a dynamic configuration of split logical functions. As will be described in more detail with reference toFIG. 5 , the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layers may be adaptably placed at the DU or CU (e.g., TRP or ANC, respectively). -
FIG. 3 illustrates an example physical architecture of a distributedRAN 300, according to aspects of the present disclosure. A centralized core network unit (C-CU) 302 may host core network functions. The C-CU 302 may be centrally deployed. 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. The C-
RU 304 may host core network functions locally. The C-RU 304 may have distributed deployment. The C-RU 304 may be closer to the network edge. - A
DU 306 may host one or more TRPs (e.g., an edge node (EN), an edge unit (EU), a radio head (RH), a smart radio head (SRH), or the like). The DU may be located at edges of the network with radio frequency (RF) functionality. -
FIG. 4 illustrates example components of thegNB 110 andUE 120 illustrated inFIG. 1 , which may be used to implement aspects of the present disclosure for frequency hopping for large bandwidth allocations. For example, antennas 452, Tx/Rx 222,processors processor 480 of theUE 120 and/or antennas 434,processors processor 440 of thegNB 110 may be used to perform the operations described herein and illustrated with reference toFIGs. 9-11 . -
FIG. 4 shows a block diagram of a design of agNB 110 and aUE 120, which may be one of the gNBs and one of the UEs inFIG. 1 . For a restricted association scenario, thegNB 110 may be themacro gNB 110c inFIG. 1 , and theUE 120 may be the UE 120y. ThegNB 110 may also be gNB of some other type. ThegNB 110 may be equipped withantennas 434a through 434t, and theUE 120 may be equipped withantennas 452a through 452r. - At the
gNB 110, a transmitprocessor 420 may receive data from adata source 412 and control information from a controller/processor 440. The control information may be for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), etc. The data may be for the Physical Downlink Shared Channel (PDSCH), etc. Theprocessor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Theprocessor 420 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal (CRS). 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 the modulators (MODs) 432a through 432t. 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 frommodulators 432a through 432t may be transmitted via theantennas 434a through 434t, respectively. - At the
UE 120, theantennas 452a through 452r may receive the downlink signals from thegNB 110 and may provide received signals to the 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. AMIMO detector 456 may obtain received symbols from all thedemodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receiveprocessor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for theUE 120 to adata sink 460, and provide decoded control information to a controller/processor 480. - On the uplink, at the
UE 120, a transmitprocessor 464 may receive and process data (e.g., for the Physical Uplink Shared Channel (PUSCH)) from adata source 462 and control information (e.g., for the Physical Uplink Control Channel (PUCCH) from the controller/processor 480. The transmitprocessor 464 may also generate reference symbols for a reference signal. The symbols from the transmitprocessor 464 may be precoded by aTX MIMO processor 466 if applicable, further processed by thedemodulators 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to thegNB 110. At thegNB 110, the uplink signals from theUE 120 may be received by the antennas 434, processed by the modulators 432, detected by aMIMO detector 436 if applicable, and further processed by a receiveprocessor 438 to obtain decoded data and control information sent by theUE 120. The receiveprocessor 438 may provide the decoded data to adata sink 439 and the decoded control information to the controller/processor 440. - The controllers/
processors gNB 110 and theUE 120, respectively. Theprocessor 440 and/or other processors and modules at thegNB 110 may perform or direct, e.g., the execution of various processes for the techniques described herein. Theprocessor 480 and/or other processors and modules at theUE 120 may also perform or direct, e.g., the execution of the functional blocks illustrated inFIGs. 9 and11 , and/or other processes for the techniques described herein. Theprocessor 440 and/or other processors and modules at thegNB 110 may also perform or direct, e.g., the execution of the functional blocks illustrated inFIG. 10 , and/or other processes for the techniques described herein. Thememories gNB 110 and theUE 120, respectively. Ascheduler 444 may schedule UEs for data transmission on the downlink and/or uplink. -
FIG. 5 illustrates a diagram 500 showing examples for implementing a communications protocol stack, according to aspects of the present disclosure. The illustrated communications protocol stacks may be implemented by devices operating in a in a 5G system (e.g., a system that supports uplink-based mobility). Diagram 500 illustrates a communications 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 a protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device (e.g., ANs, CUs, and/or DUs) or a UE. - A first option 505-a shows a split implementation of a protocol stack, in which implementation of the protocol stack is split between a centralized network access device (e.g., an
ANC 202 inFIG. 2 ) and distributed network access device (e.g.,DU 208 inFIG. 2 ). In the first option 505-a, anRRC layer 510 and aPDCP layer 515 may be implemented by the central unit, and anRLC layer 520, aMAC layer 525, and aPHY layer 530 may be implemented by the DU. In various examples the CU and the DU may be collocated or non-collocated. The first option 505-a may be useful in a macro cell, micro cell, or pico cell deployment. - A second option 505-b shows a unified implementation of a protocol stack, in which the protocol stack is implemented in a single network access device (e.g., access node (AN), new radio base station (NR BS), a new radio Node-B (NR NB), a network node (NN), or the like.). In the second option, the
RRC layer 510, thePDCP layer 515, theRLC layer 520, theMAC layer 525, and thePHY layer 530 may each be implemented by the AN. The second option 505-b may be useful in a femto cell deployment. - Regardless of whether a network access device implements part or all of a protocol stack, a UE may implement an entire protocol stack (e.g., the
RRC layer 510, thePDCP layer 515, theRLC layer 520, theMAC layer 525, and the PHY layer 530). -
FIG. 6 is a diagram showing an example format of a DL-centric subframe 600. The DL-centric subframe 600 may include a control portion 602. The control portion 602 may exist in the initial or beginning portion of the DL-centric subframe 600. The control portion 602 may include various scheduling information and/or control information corresponding to various portions of the DL-centric subframe 600. In some configurations, the control portion 602 may be a physical DL control channel (PDCCH), as indicated inFIG. 6 . The DL-centric subframe 600 may also include aDL data portion 604. TheDL data portion 604 may sometimes be referred to as the payload of the DL-centric subframe 600. TheDL data portion 604 may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or gNB) to the subordinate entity (e.g., UE). In some configurations, theDL data portion 604 may be a physical DL shared channel (PDSCH). - The DL-
centric subframe 600 may also include a common UL portion 606. The 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 subframe. 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 an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information. The common UL portion 606 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs), and various other suitable types of information. As illustrated inFIG. 6 , the end of theDL 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, a guard period, a guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE)) to UL communication (e.g., transmission by the subordinate entity (e.g., UE)). One of ordinary skill in the art will understand that the foregoing is merely one example of a DL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein. -
FIG. 7 is a diagram showing an example format of an UL-centric subframe 700. The UL -centric subframe 700 may include acontrol portion 702. Thecontrol portion 702 may exist in the initial or beginning portion of the UL-centric subframe 700. Thecontrol portion 702 inFIG. 7 may be similar to the control portion 602 described above with reference toFIG. 6 . The UL-centric subframe 700 may also include an UL data portion 704. The UL data portion 704 may sometimes be referred to as the payload of the UL-centric subframe 700. The UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or gNB). In some configurations, thecontrol portion 702 may be a PDCCH. - As illustrated in
FIG. 7 , the end of thecontrol 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 separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity). The UL-centric subframe 700 may also include acommon UL portion 706. Thecommon UL portion 706 inFIG. 7 may be similar to thecommon UL portion 706 described above with reference toFIG. 7 . Thecommon UL portion 706 may additional or alternative include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), and various other suitable types of information. One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric subframe 700 and alternative structures having similar features may exist without necessarily deviating from the aspects described herein. - In some circumstances, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Intemet-of-Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications. Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or gNB), even though the scheduling entity may be utilized for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).
- A UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration 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 dedicated set of resources for transmitting a pilot signal to a network. When operating in the RRC common state, the UE may select a common set of resources for transmitting a pilot signal to the network. In either case, a pilot signal transmitted by the UE may be received by one or more network access devices, such as an AN, or a DU, or portions thereof. Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE. One or more of the receiving network access devices, or a CU to which receiving network access device(s) transmit the measurements of the pilot signals, may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs.
- Aspects of the present disclosure provide apparatus, methods, processing systems, and computer program products for new radio (NR) (new radio access technology or 5G technology). New radio (NR) may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP)). NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low latency communications (URLLC) service. The RAN may include a central unit (CU) and distributed units (DUs). A NR Node B (e.g., 5G Node B) may correspond to one or multiple transmission reception points (TRPs).
- Ultra-reliability low latency communication (URLLC) generally refers to relatively tight (e.g., stringent) requirements for successful delivery of a packet within a stringent deadline (e.g., 1 ms) with very high probability (e.g., 99.999%) of success. The reliability of a downlink (DL) transmission depends on the reliability of both the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH). The reliability of the PDSCH can be improved with the use of hybrid automatic repeat request (HARQ) (or automatic repeat request (ARQ)) that allows the receiver to combine different copies of the same data packet. However, the PDSCH packet (data packet) is not decodable if the corresponding PDCCH (control packet) is not detected. When the size of the data packet is comparable with that of the control packet (as in many URLLC applications), the control channel becomes the bottleneck of the overall communication. Certain aspects of the present disclosure provide apparatus and techniques for improving the reliability of PDCCH by repetition and spreading.
-
FIG. 8 illustratesexample operations 800 for wireless communication, in accordance with certain aspects of the present disclosure. Theoperations 800 are performed, for example, by a user-equipment (UE), such as theUE 120. - The
operations 800 begin, atblock 802, by monitoring for control information (e.g., downlink control information (DCI)) in each of a plurality of PDCCHs during a different one of a plurality of time intervals (e.g., a slot or mini-slot). In certain aspects, the PDCCHs contain the same control information that indicates a resource allocation within a respective one of the time intervals for receiving one of a plurality of PDSCHs. In certain aspects, the data in each of the plurality of PDSCHs is the same. Atblock 804, theoperations 800 continue by soft-combining the plurality of PDCCHs to decode the control information, and atblock 806, decoding the control information based on the soft-combination of the plurality of PDCCHs. In certain aspects, theoperations 800 also include receiving each of the plurality of PDSCHs in a respective one of the plurality of time intervals, soft-combining the plurality of PDSCHs, and decoding data within the plurality of PDSCHs based on the soft-combination of the plurality of PDSCHs and the resource allocation. -
FIG. 9 illustratesexample operations 900 for wireless communication, in accordance with certain aspects of the present disclosure. Theoperations 900 are performed, for example, by a base station (e.g., gNB), such as thegNB 110. - The
operations 900 begin, atblock 902, by determining a resource allocation within each of a plurality of time intervals for transmitting a respective one of a plurality of PDSCHs. In certain aspects, the resource allocation may be the same within each of the plurality of time intervals. In certain aspects, data in each of the plurality of PDSCHs is the same. Atblock 904, the operations continue by transmitting control information in each of a plurality of PDCCHs, each of the PDCCHs being transmitted during one of the plurality of time intervals. In certain aspects, the PDCCHs have the same control information that indicates the resource allocation within respective one of the plurality of time intervals. Atblock 906, each of the plurality of PDSCHs is transmitted during one of the plurality of time intervals based on the resource allocation. Theoperations FIGs. 10-14 . -
FIG. 10 illustrates a flow diagram 1000 for transmitting a PDCCH and a PDSCH, in accordance with certain aspects of the present application. For example, aDCI 1002 may be generated including a resource allocation for a PDSCH, and a cyclic redundancy check (CRC) 1004 may be appended onto the DCI, as illustrated. Atblock 1006, channel coding and rate matching may be performed, after which aPDCCH 1008 is generated having theDCI 1002 andCRC 1004. Atblock 1010, the PDCCH is repeated into K copies to generatePDCCH 1,PDCCH 2, to PDCCH K, as illustrated, each of which are scrambled atblocks different time intervals - The PDSCHs transmitted during the
different time intervals PDCCH 1 may correspond to an index of an RV of the PDSCH in thetime interval 1024, and so on. - The UE may be configured with PDCCH monitoring periodicity (e.g., slot/mini-slot) based on a number of PDCCH repetitions K. For example, the UE may be configured to monitor for PDCCH in each of K time intervals (e.g., slots or mini-slots). Thus, the UE monitors the PDCCH according to the configured PDCCH monitoring periodicity. If the PDCCH monitoring periodicity is, for example, one mini-slot, depending on whether PDCCH scrambling uses the same or different scrambling sequences, the UE may perform different operations within each mini-slot. If the same scrambling sequences are used for the repeated PDCCHs, the UE may decode the PDCCH in time interval n, assuming that the PDCCH in time interval n is the first PDCCH transmission. The UE may soft-combine the PDCCH in time interval n with a PDCCH received during time interval n-1 assuming that the first PDCCH transmission is in time interval n-1.
- This process is continued for all K repetitions. For example, the UE may soft-combine the PDCCH in time interval n with PDCCHs from time interval n-K+1 to n-1, assuming that the first PDCCH transmission is in time interval n-K+1. The K operations may be performed in parallel or in a serial fashion. The UE may only perform some of the K operations based on the UE capability. In other words, since all the PDCCHs may include the same DCI, the UE may perform less than the K operations. For example, the UE may only combine at most two PDCCHs (e.g., may soft-combine PDCCHs received in time interval n and n-1). For a given DCI transmission, each of the operations (i.e., decoding attempts) described herein may be counted as a blind decode. The total number of blind decodes in a given time interval may not exceed a target threshold. The target threshold may correspond to the maximum number of blind decodes a UE is able to perform in the given time interval. Thus, the number of operations that the UE performs to decode a given DCI may be determined based on the target threshold.
-
FIG. 11 is a table 1100 illustrating operations that may be performed by a UE for decoding PDCCHs that are scrambled using different sequences, in accordance with certain aspects of the present disclosure. Each entry (excluding the entries in the first column) in the table 1100 corresponds to one UE operation. For example, the first entry in the second row may indicate the time interval indices (e.g., n-1 and n) in which PDCCH packets are to be soft-combined and the corresponding scrambling sequence indices. For instance, in this case, the PDCCH in time interval index n-1 is scrambled by scramblingsequence index 1, and the PDCCH in time interval index n is scrambled by scramblingsequence index 2. - Depending on the capability of the UE, the UE may perform the K operations listed in one column (e.g., the second column of table 1100), or may perform the operations listed across m rows of the table 1100, where m is less than the K total number of rows. The operations performed by the UE may be performed either in parallel or in a serial fashion depending on the UEs capabilities. Each of the operations (e.g.,, decoding attempts) described herein may be counted as a blind decode. The total number of blind decodes in a given time interval may not exceed a target threshold corresponding to the maximum number of blind decodes a UE is able to perform in a given time interval. Thus, the number of operations that the UE performs in table 1100 for a given DCI may be determined based on the target threshold. If any of the operations previously described for decoding the PDCCH results in successful decoding (e.g., the decoded PDCCH passes CRC check performed based on the CRC 1004), then the UE may then proceed to decoding the PDSCH.
- In certain aspects, the PDSCHs transmitted during the
time intervals k+ 1 to time interval n. In certain aspects, the PDSCHs transmitted during thetime intervals - In certain aspects, the UE may provide feedback to the gNB after each of the time intervals (e.g., slots or mini-slots) to indicate whether the PDCCH and the PDSCH were successfully decoded. For example, if the UE decodes both PDCCH and PDSCH in a first time interval, then the UE may feedback an acknowledgement (ACK) indicating that the PDSCH was successfully decoded. In this case, the gNB may terminate any following PDCCH and PDSCH transmissions in subsequent time intervals. In certain aspects, if the UE does not successfully decode the PDCCH, the UE may not provide any feedback to the gNB. In this case, the gNB may retransmit both the PDCCH and the PDSCH in the subsequent time interval (e.g.,
mini-slot 2 as described with respect toFIG. 10 ). - If the UE decodes the PDCCH but fails to decode the PDSCH, then the UE may feedback a negative acknowledgement (NACK) indicating that the PDSCH was not successfully decoded. In this case, the gNB may terminate transmission of the PDCCH in any subsequent time intervals, but continue the transmission of the PDSCH using the same resources as indicated by the previously transmitted, and successfully decoded, PDCCH. In some cases, the gNB may continue to transmit both the PDCCH and PDSCH after receiving a NACK. In some cases, the gNB may terminate both PDCCH and PDSCH transmissions after receiving a NACK, and may reschedule a new PDSCH retransmission and a new PDCCH indicating new resources for the rescheduled PDSCH.
-
FIG. 12 illustrates a flow diagram 1200 for transmitting multiple RVs of a PDCCH, in accordance with certain aspects of the present application. In this case, the gNB may segment, atblock 1210, the PDCCH into K equal-sized self-decodable packets having different RVs, and transmit K RVs of the PDCCH (e.g., PDCCH RV1, PDCCH RV2, to PDCCH RV K), as illustrated. The UE monitors for the PDCCH during each time interval (e.g., slot or mini-slot) to decode the control information in the PDCCH assuming each of the plurality of RVs, as described with respect toFIG. 13 . -
FIG. 13 is a table 1300 illustrating operations that may be performed by a UE for decoding PDCCHs having different RVs, in accordance with certain aspects of the present disclosure. Similar to table 1100, each entry (excluding the entries in the first column) in the table 1300 corresponds to one UE operation. For example, the first element in the second row indicates the time interval indices (e.g., n-1 and n) in which PDCCH packets are to be soft-combined and the corresponding RV indices (e.g.,RV index 1 corresponds to mini-slot index n-1, andRV index 2 corresponds to the mini-slot index n). Depending on the capability of the UE, the UE may perform the K operations listed in one column (e.g., the first column of table 1300), or may perform the operations listed across m rows of the table 1300, where m is less than the K total number of rows. The operations performed by the UE may be performed either in parallel or in a serial fashion depending on the UEs capabilities. Each of the operations (e.g., decoding attempts) described herein may be counted as a blind decode. The total number of blind decodes in a given time interval may not exceed a target threshold corresponding to a maximum number of blind decodes a UE is able to perform in a given time interval. Thus, the number of operations that the UE performs in the table 1300 for a given DCI may be determined based on the target threshold. If any of the operations described herein for decoding the PDCCH results in successful decoding (e.g., the decoded PDCCH passes CRC check performed based on the CRC 1004), then the UE may then proceed to decoding the PDSCH. -
FIG. 14 illustrates a flow diagram 1400 for transmitting multiple RVs of a PDCCH having different sizes, in accordance with certain aspects of the present application. In other words, the gNB may segment, atblock 1410, the PDCCH into K unequal-sized self-decodable packets having different RVs, as illustrated. In certain aspects, the size of the PDCCH RVs may follow a pre-defined pattern that may be known by the both the gNB and the UE such that the UE can decode the PDCCH RVs based on the defined pattern. For example, the size of the PDCCH RV1, may be one control channel element (CCE), the size of the PDCCH RV2 may be one CCE, the size of the PDCCH RV3 may be two CCEs, the size of the PDCCH RV4 may be two CCEs, and so on. The PDSCHs transmitted in each of thetime intervals - 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 those items, including single members. As an example, "at least one of: a, b, or c" is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, 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" may include calculating, computing, processing, deriving, investigating, 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." Unless specifically stated otherwise, the term "some" refers to one or more.
- The various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components with similar numbering.
- The various illustrative logical blocks, modules and circuits described in connection with the present 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 comprise a processing system in a 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 a processor, machine-readable media, and a bus interface. The bus interface may be used to connect a network adapter, among other things, to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of a UE 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. The processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for 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 or transmitted over as one or more instructions or code on a computer-readable medium. Software shall 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 include 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 media. A computer-readable storage medium may be coupled to a 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 media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface. Alternatively, or in addition, the machine-readable media, or any portion thereof, may be integrated into the processor, such as the case may be with cache and/or general register files. Examples of machine-readable storage media may include, by way of example, 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 disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The machine-readable media 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 media may comprise a number of software modules. The software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions. The software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. By way of 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 of the instructions into 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 that software module.
- Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, 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 and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Thus, in some aspects computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media). In addition, for other aspects computer-readable media may comprise transitory computer-readable media (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 comprise 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.
- Further, it should 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 as applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device. Moreover, any other suitable technique for providing the methods and techniques described herein to a device can be utilized.
- It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.
Claims (14)
- A method (800) performed by a user equipment (120), UE, for wireless communication, comprising:monitoring (802), at a user-equipment (120), UE, for control information in each of a plurality of physical downlink control channels, PDCCHs, during a different one of a plurality of time intervals, wherein the PDCCHs contain the same control information that indicates a resource allocation within a respective one of the time intervals for receiving one of a plurality of physical downlink shared channels, PDSCHs, wherein data in each of the plurality of PDSCHs is the same;soft-combining (804) the plurality of PDCCHs to decode the control information;decoding (806) the control information based on the soft-combination of the plurality of PDCCHs;receiving each of the plurality of PDSCHs in a respective one of the plurality of time intervals based on the resource allocation,wherein each of the plurality of PDSCHs are encoded using a different redundancy version, RV, of the same data; determining an index corresponding to each of the RVs based on an indication from a node, wherein the plurality of PDSCHs are soft-combined based on the indices; decoding data within the plurality of PDSCHs based on the soft-combination of the plurality of PDSCHs; the method characterized in that the index corresponding to each of the RVs is modulated on a demodulation reference signal, DMRS, of a corresponding one of the plurality of PDSCHs.
- The method of claim 1, further comprising:
transmitting an indication, after at least one of the plurality of time intervals, of whether at least one of the control information or data within the preceding time interval was successfully decoded wherein preferably the indication comprises:a negative acknowledgement, NACK, if the control information in the PDCCH of the preceding time interval was successfully decoded and the data in the PDSCH of the preceding time interval is not successfully decoded; andan acknowledgement, ACK, if the control information and the data in the preceding time interval are successfully decoded. - The method of claim 2, wherein each of one or more time intervals of the plurality of time intervals after the preceding time interval comprises one of the plurality of PDSCHs if the indication comprises the NACK, and wherein the preceding time interval is the last time interval having one of the plurality of PDCCHs if the indication comprises the NACK.
- The method of claim 2, wherein the preceding time interval is the last time interval having one of the plurality of PDCCHs or one of the plurality of PDSCHs if the indication comprises the ACK.
- The method of claim 1, further comprising:
determining a number of PDCCHs that were soft-combined before the control information was successfully decoded, wherein a number of the PDSCHs that are soft-combined corresponds to the number of the PDCCHs that were soft-combined before the control information was successfully decoded. - The method of claim 1, wherein the plurality of PDCCHs are:scrambled using different scrambling sequences; orencoded using different RVs.
- The method of claim 6, further comprising decoding the control information in a first PDCCH of the plurality of PDCCHs assuming a first scrambling sequence, andperforming a cyclic redundancy check to determine whether the first PDCCH is decoded successfully; ordecoding the control information in a second PDCCH of the plurality of PDCCHs assuming a second scrambling sequence, wherein the second PDCCH is received prior to the first PDCCH.
- The method of claim 1 further comprising:decoding the control information in a first PDCCH of the plurality of PDCCHs assuming a first RV;performing a cyclic redundancy check to determine whether the first PDCCH is decoded successfully; anddecoding the control information in the first PDCCH assuming a second RV and decoding the control information in a second PDCCH of the plurality of PDCCHs assuming the first RV, wherein the second PDCCH is received prior to the first PDCCH.
- A method performed by a base station (110) for wireless communication, comprising:determining (902), at a base station (110), a resource allocation within each of a plurality of time intervals for transmitting a respective one of a plurality of physical downlink shared channels, PDSCHs, wherein data in each of the plurality of PDSCHs is the same;transmitting (904) control information in each of a plurality of physical downlink control channel, PDCCHs, each of the PDCCHs being transmitted during one of the plurality of time intervals, the PDCCHs having the same control information that indicates the resource allocation within respective one of the plurality of time intervals; andtransmitting (906) each of the plurality of PDSCHs during one of the plurality of time intervals based on the resource allocation, wherein each of the plurality of PDSCHs are encoded using a different redundancy version, RV, of the same data, the method characterized by: modulating an index corresponding to each of the RVs on a demodulation reference signal, DMRS, of a corresponding one of the plurality of PDSCHs.
- The method of claim 1 or 9, wherein a size of each of the RVs of the plurality of PDSCHs is different and is based on a pre-defined pattern.
- The method of claim 1or 9, wherein a size of each of the RVs of the plurality of PDCCHs is different and is based on a pre-defined pattern.
- The method of claim 9, further comprising determining, after each of the plurality of time intervals, whether at least one of the control information or data within the preceding time interval was successfully decoded by a user-equipment, UE, wherein preferably the determination is based on an indication from the UE.
- The method of claim 12, wherein the determination comprises:determining that the control information transmitted in the PDCCH transmitted during a first time interval of the plurality of time intervals was not successfully decoded by the UE if neither an acknowledgement, nor a negative acknowledgement, is received after the first time interval, method further comprising transmitting the PDCCH and the PDSCH in a second time interval of the plurality of time intervals based on the determination; ordetermining that the control information transmitted in the PDCCH transmitted during a first time interval of the plurality of time intervals was successfully decoded by the UE and that the data in the PDSCH transmitted during the first time interval was not successfully decoded, if a negative acknowledgement is received after the first time interval, the method further comprising transmitting the PDSCH in a second time interval of the plurality of time intervals, and ceasing transmission of the PDCCH in the second time interval, based on the determination.
- An apparatus for wireless communication, comprising:at least one antenna; anda processing system configured to:
perform the method of any preceding claim.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP22164948.6A EP4044481B1 (en) | 2018-01-22 | 2019-01-18 | Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc) |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862620038P | 2018-01-22 | 2018-01-22 | |
US16/250,377 US10980051B2 (en) | 2018-01-22 | 2019-01-17 | Physical downlink control channel (PDCCH) repetition and decoding for ultra-reliability low latency communication (URLLC) |
PCT/US2019/014262 WO2019143985A1 (en) | 2018-01-22 | 2019-01-18 | Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc) |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP22164948.6A Division EP4044481B1 (en) | 2018-01-22 | 2019-01-18 | Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc) |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3744028A1 EP3744028A1 (en) | 2020-12-02 |
EP3744028B1 true EP3744028B1 (en) | 2022-04-06 |
Family
ID=67299498
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19703589.2A Active EP3744028B1 (en) | 2018-01-22 | 2019-01-18 | Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc) |
EP22164948.6A Active EP4044481B1 (en) | 2018-01-22 | 2019-01-18 | Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc) |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP22164948.6A Active EP4044481B1 (en) | 2018-01-22 | 2019-01-18 | Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc) |
Country Status (4)
Country | Link |
---|---|
US (1) | US10980051B2 (en) |
EP (2) | EP3744028B1 (en) |
CN (2) | CN117478280A (en) |
WO (1) | WO2019143985A1 (en) |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019098667A1 (en) * | 2017-11-16 | 2019-05-23 | 엘지전자 주식회사 | Method for transmitting and receiving downlink control information and apparatus therefor |
BR112021003330A2 (en) | 2018-08-23 | 2021-05-11 | British Telecommunications Public Limited Company | cellular telecommunications network |
GB201815377D0 (en) * | 2018-09-21 | 2018-11-07 | British Telecomm | Cellular telecommunications network |
CN111865527B (en) * | 2019-04-29 | 2021-10-01 | 华为技术有限公司 | Communication method and device |
CN112399566B (en) * | 2019-08-14 | 2022-04-12 | 华为技术有限公司 | Method and communication device for processing data |
US11849473B2 (en) * | 2019-12-13 | 2023-12-19 | Qualcomm Incorporated | Beam ready time for downlink control information based beam activation command |
US11411779B2 (en) | 2020-03-31 | 2022-08-09 | XCOM Labs, Inc. | Reference signal channel estimation |
KR20220015839A (en) * | 2020-07-31 | 2022-02-08 | 삼성전자주식회사 | Method and apparatus for transmission and reception of control information in wireless cooperative communication system |
US20220312393A1 (en) * | 2020-08-06 | 2022-09-29 | Apple Inc. | Physical downlink control channel (pdcch) reliability enhancement |
WO2022032212A1 (en) * | 2020-08-07 | 2022-02-10 | Intel Corporation | Physical downlink control channel repetition configuration and physical downlink shared channel starting configuration and processing time indication |
EP4082266A4 (en) * | 2020-08-07 | 2023-09-13 | ZTE Corporation | Method and device for inactivating downlink channel |
US11962407B2 (en) * | 2020-09-24 | 2024-04-16 | Qualcomm Incorporated | Blind decoding counting for repetition-based physical downlink control channel candidates |
WO2022087569A1 (en) | 2020-10-19 | 2022-04-28 | XCOM Labs, Inc. | Reference signal for wireless communication systems |
WO2022093988A1 (en) | 2020-10-30 | 2022-05-05 | XCOM Labs, Inc. | Clustering and/or rate selection in multiple-input multiple-output communication systems |
WO2022150980A1 (en) * | 2021-01-12 | 2022-07-21 | 捷开通讯(深圳)有限公司 | Transmission enhancement method and communication device |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013183943A1 (en) * | 2012-06-05 | 2013-12-12 | 엘지전자 주식회사 | Method and apparatus for receiving control information in wireless communication system |
CN104769857B (en) * | 2012-11-01 | 2018-05-22 | Lg 电子株式会社 | The method and apparatus of the scheduling group of holding equipment characteristic in a wireless communication system |
CN104737487B (en) | 2012-11-02 | 2018-03-02 | 联发科技(新加坡)私人有限公司 | Decode the method and user equipment of control channel in multiple subframes |
WO2014077577A1 (en) | 2012-11-13 | 2014-05-22 | 엘지전자 주식회사 | Method and apparatus for transmitting data, and method and apparatus for transmitting data |
US9144066B2 (en) | 2012-12-28 | 2015-09-22 | Sierra Wireless, Inc. | Method and system for hybrid automatic repeat request combining on an lte downlink control channel |
US11316637B2 (en) * | 2015-04-09 | 2022-04-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Physical resource block allocation of physical downlink control and data channels |
WO2017148510A1 (en) | 2016-03-02 | 2017-09-08 | Nokia Solutions And Networks Oy | Use of tiny retransmission resource for partial packet retransmission for wireless networks |
US10804989B2 (en) * | 2016-07-20 | 2020-10-13 | Convida Wireless, Llc | Mobility for radio devices using beamforming and selection |
US11297674B2 (en) * | 2018-02-14 | 2022-04-05 | Samsung Electronics Co., Ltd. | Method and apparatus for power savings at a user equipment |
US11387942B2 (en) * | 2018-05-11 | 2022-07-12 | Apple Inc. | Systems and methods for physical channel repetition for low latency communication |
-
2019
- 2019-01-17 US US16/250,377 patent/US10980051B2/en active Active
- 2019-01-18 EP EP19703589.2A patent/EP3744028B1/en active Active
- 2019-01-18 CN CN202311234871.5A patent/CN117478280A/en active Pending
- 2019-01-18 WO PCT/US2019/014262 patent/WO2019143985A1/en unknown
- 2019-01-18 CN CN201980009193.8A patent/CN111615806B/en active Active
- 2019-01-18 EP EP22164948.6A patent/EP4044481B1/en active Active
Also Published As
Publication number | Publication date |
---|---|
EP3744028A1 (en) | 2020-12-02 |
WO2019143985A1 (en) | 2019-07-25 |
EP4044481C0 (en) | 2023-10-11 |
EP4044481A1 (en) | 2022-08-17 |
US10980051B2 (en) | 2021-04-13 |
US20190230697A1 (en) | 2019-07-25 |
CN111615806B (en) | 2023-09-29 |
CN111615806A (en) | 2020-09-01 |
CN117478280A (en) | 2024-01-30 |
EP4044481B1 (en) | 2023-10-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3744028B1 (en) | Physical downlink control channel (pdcch) repetition and decoding for ultra-reliability low latency communication (urllc) | |
EP3682569B1 (en) | Resource (re) mapping rule for uplink control information (uci) piggyback on physical uplink shared channel (pusch) | |
EP3777393B1 (en) | Pucch resource allocation before rrc setup | |
EP3782321B1 (en) | Demodulation reference signal (dmrs) time-domain bundling and multiple codeword transmission and processing | |
EP3577834B1 (en) | Resource allocation for physical uplink control channel (pucch) | |
CN111886826B (en) | Improved Physical Downlink Control Channel (PDCCH) reliability for ultra-reliable low latency communications (URLLC) | |
EP3704908A1 (en) | Timing advance granularity for uplink with different numerologies | |
WO2020056726A1 (en) | Uplink control information multiplexing on physical uplink control channel | |
EP3718354B1 (en) | Physical uplink control channel (pucch) resource allocation | |
WO2019192007A1 (en) | Collision handling for csi reporting on pusch | |
US11743925B2 (en) | Resource allocation for uplink control information (UCI) and data multiplexing on a physical uplink shared channel (PUSCH) | |
WO2020034055A1 (en) | Layer mapping for multi-trp transmission | |
WO2019105392A1 (en) | Example uplink control information (uci) layer mapping | |
EP3741074B1 (en) | Uplink control information (uci) to resource element (re) mapping | |
WO2020024080A1 (en) | Control channel repetition for uplink and downlink communication |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20200616 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20211020 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1482378 Country of ref document: AT Kind code of ref document: T Effective date: 20220415 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602019013412 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20220406 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1482378 Country of ref document: AT Kind code of ref document: T Effective date: 20220406 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220808 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220706 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220707 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220706 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220806 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602019013412 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20230110 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230118 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20230131 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230131 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230131 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230131 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20231218 Year of fee payment: 6 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230118 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20231214 Year of fee payment: 6 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20231128 Year of fee payment: 6 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20220406 |