EP3994833A1 - Dci based xcarrier repetition & beam sweep - Google Patents
Dci based xcarrier repetition & beam sweepInfo
- Publication number
- EP3994833A1 EP3994833A1 EP20743004.2A EP20743004A EP3994833A1 EP 3994833 A1 EP3994833 A1 EP 3994833A1 EP 20743004 A EP20743004 A EP 20743004A EP 3994833 A1 EP3994833 A1 EP 3994833A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- dci
- entities
- entity
- combination
- channel
- 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.)
- Pending
Links
- 230000005540 biological transmission Effects 0.000 claims abstract description 158
- 238000004891 communication Methods 0.000 claims abstract description 89
- 238000000034 method Methods 0.000 claims abstract description 82
- 230000015654 memory Effects 0.000 claims description 33
- 230000008569 process Effects 0.000 claims description 18
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 claims description 15
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 claims description 15
- 230000006978 adaptation Effects 0.000 claims description 9
- 230000002596 correlated effect Effects 0.000 claims description 7
- 230000004044 response Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 24
- 238000001228 spectrum Methods 0.000 description 16
- 238000005516 engineering process Methods 0.000 description 10
- 238000013461 design Methods 0.000 description 9
- 230000000875 corresponding effect Effects 0.000 description 7
- 230000008901 benefit Effects 0.000 description 6
- 238000007796 conventional method Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000000903 blocking effect Effects 0.000 description 4
- 230000011664 signaling Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000002452 interceptive effect Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 230000010267 cellular communication Effects 0.000 description 2
- 230000001276 controlling effect Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 239000002245 particle Substances 0.000 description 2
- 238000000638 solvent extraction Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000009529 body temperature measurement Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000002950 deficient Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 230000003595 spectral effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
- H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
- H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
- H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
- H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
- H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
-
- 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/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0072—Error control for data other than payload data, e.g. control data
-
- 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/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
-
- 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]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0014—Three-dimensional division
- H04L5/0023—Time-frequency-space
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0058—Allocation criteria
- H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
-
- 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/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
-
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access, e.g. scheduled or random access
- H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
- H04W74/0833—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using a random access procedure
-
- 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/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
-
- 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
Definitions
- aspects of the present disclosure relate generally to wireless communication systems, and more particularly, use of downlink control information (DCI) for scheduling.
- DCI downlink control information
- Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, and the like. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks, which are usually multiple access networks, support communications for multiple users by sharing the available network resources.
- UTRAN Universal Terrestrial Radio Access Network
- the UTRAN is the radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), a third generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3GPP).
- UMTS Universal Mobile Telecommunications System
- 3GPP 3rd Generation Partnership Project
- multiple-access network formats include Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, and Single-Carrier FDMA (SC- FDMA) networks.
- CDMA Code Division Multiple Access
- TDMA Time Division Multiple Access
- FDMA Frequency Division Multiple Access
- OFDMA Orthogonal FDMA
- SC- FDMA Single-Carrier FDMA
- a wireless communication network may include a number of base stations or node Bs that can support communication for a number of user equipments (UEs).
- a UE may communicate with a base station via downlink and uplink.
- the downlink (or forward link) refers to the communication link from the base station to the UE
- the uplink (or reverse link) refers to the communication link from the UE to the base station.
- a base station may transmit data and control information on the downlink to a UE or may receive data and control information on the uplink from the UE.
- a transmission from the base station may encounter interference due to transmissions from neighbor base stations or from other wireless radio frequency (RF) transmitters.
- RF radio frequency
- On the uplink a transmission from the UE may encounter interference from uplink transmissions of other UEs communicating with the neighbor base stations or from other wireless RF transmitters. This interference may degrade performance on both the downlink and uplink.
- 5G NR may use one or more frequency ranges, such as frequency range 1 (FR1) or multiple frequency range (FR2).
- FR1 for 5G NR which includes frequencies from 450 megahertz (MHz) to 6 gigahertz (GH) in sub-6 GHz, is absent or otherwise unavailable for a transmission
- medium access control (MAC) can be reschedule the transmission on multiple frequency range (FR2) component carries (CCs) for 5G NR.
- FR2 includes frequencies from 24.25 GHz to 52.6 GHz in mm-Wave, such with the same time block (TB)/code block group (CBG) on the multiple CCs.
- TB time block
- CBG code block group
- the same TB can be rescheduled on each TB with a corresponding downlink control information (DCI) as a new transmission with a particular hybrid automatic repeat request (HARQ) identifier (ID). Accordingly, multiple DCIs are needed for the transmission to be rescheduled on each of the multiple CCs. Additionally, with the conventional techniques, an ACK/NACK is communicated on an associated Physical Uplink Control Channel (PUCCH) cell.
- DCI downlink control information
- ID hybrid automatic repeat request
- PUCCH Physical Uplink Control Channel
- a method of wireless communication includes receiving, by a user equipment (UE), downlink control information (DCI) via an entity of a plurality of entities. The method also includes determining, by the UE based on the DCI, scheduling information for multiple transmissions on different entities of the plurality of entities.
- DCI downlink control information
- an apparatus configured for wireless communication includes means for receiving, by a UE, DCI via an entity of a plurality of entities; and means for identifying, by the UE based on the DCI, scheduling information associated with multiple transmissions on different entities of the plurality of entities.
- a non-transitory computer-readable medium having program code recorded thereon.
- the program code includes code to receive, by a UE, DCI via an entity of a plurality of entities; and determine, by the UE based on the DCI, scheduling information for multiple transmissions on different entities of the plurality of entities.
- an apparatus configured for wireless communication.
- the apparatus includes at least one processor, and a memory coupled to the processor.
- the processor is configured to receive, by a UE, DCI via an entity of a plurality of entities; and determine, by the UE based on the DCI, scheduling information for multiple transmissions on different entities of the plurality of entities.
- a method of wireless communication includes identifying, by a base station, DCI communicated via an entity of a plurality of entities. The method also includes scheduling, by the base station based on the DCI, multiple transmissions on different entities of the plurality of entities.
- an apparatus configured for wireless communication includes means identifying, by a base station, DCI communicated via an entity of a plurality of entities; and means for scheduling, by the base station based on the DCI, multiple transmissions on different entities of the plurality of entities.
- a non-transitory computer-readable medium having program code recorded thereon includes code to identify, by a base station, DCI communicated via an entity of a plurality of entities; and schedule, by the base station based on the DCI, multiple transmissions on different entities of the plurality of entities.
- an apparatus configured for wireless communication.
- the apparatus includes at least one processor, and a memory coupled to the processor.
- the processor is configured to identify, by a base station, DCI communicated via an entity of a plurality of entities; and schedule, by the base station based on the DCI, multiple transmissions on different entities of the plurality of entities.
- a method for wireless communication includes identifying, by a device (e.g., a base station or a UE), DCI communicated via a first entity of plurality of entities.
- the method also includes scheduling, by the device, one or more transmission via a second entity of the plurality of entities, the second entity different from the first entity.
- FIG. l is a block diagram illustrating details of a wireless communication system.
- FIG. 2 is a block diagram illustrating a design of a base station and a UE configured according to one aspect of the present disclosure.
- FIG. 3 is a diagram illustrating a wireless communication system including base stations that use directional wireless beams.
- FIG. 4 is a diagram illustrating wireless communication that supports scheduling based on DCI.
- FIG. 5 is a diagram illustrating wireless communication that supports scheduling based on DCI.
- FIG. 6 is a diagram illustrating wireless communication that supports scheduling based on DCI.
- FIG. 7 is a diagram illustrating wireless communication that supports scheduling based on DCI.
- FIG. 8 is a diagram illustrating wireless communication that supports scheduling based on DCI.
- FIG. 9 is a diagram illustrating wireless communication that supports scheduling based on DCI.
- FIG. 10 is a block diagram illustrating example blocks executed by a UE configured according to an aspect of the present disclosure.
- FIG. 11 is a block diagram illustrating example blocks executed by a base station configured according to an aspect of the present disclosure.
- FIG. 12 is a block diagram conceptually illustrating a design of a UE according to some aspects of the present disclosure.
- FIG. 13 is a block diagram conceptually illustrating a design of a base station configured according to some aspects of the present disclosure.
- the described techniques relate to improved methods, systems, devices, and apparatuses for scheduling one or more transmissions using downlink control information (DCI).
- the one or more transmission may be scheduled by a device (e.g., a base station or UE), based on the DCI, on one or more entities different from the entity via which the DCI is transmitted.
- the entity may include a component carrier, a cell, or a frequency allocation. If the DCI is received via a first entity, such as a first CC, the one or more transmission may be scheduled on a second entity (different from the first entity) based on the DCI. In some implementations, a transmission may also be scheduled on the first entity in addition to the second entity.
- a UE may receive DCI via an entity of a plurality of entities and schedule, based on the DCI, multiple transmissions on different entities of the plurality of entities.
- each of the multiple transmissions scheduled on the different entities includes the same content.
- each of the multiple transmissions scheduled on the different entities include content correlated to content of the other of the multiple transmissions.
- each of the multiple transmissions scheduled on the different entities include independent content from the other of the multiple transmissions.
- the one or more transmissions may correspond to a channel, which may include Physical Downlink Shared Channel (PDSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), or Physical Random Access Channel (PRACH), as illustrative, non-limiting examples.
- the DCI is a single DCI used to schedule multiple transactions across multiple entities (e.g., multiple CCs) such that identical, correlated, or independent information is communicated per transmission. Additionally, or alternatively, the same, single DCI can be repeated over a set of two or more CCs to facilitate UE combining.
- scheduling, based on the DCI, multiple transmissions on different entities may be scrambled by a dedicated radio network temporary identifier (RNTI).
- RNTI radio network temporary identifier
- the dedicated RNTI is different from the RNTI for scrambling the DCI scheduling a single transmission on a single entity.
- the DCI such as a single DCI, can include or indicate scheduling information.
- the DCI may include scheduling information for each of multiple transmission.
- the scheduling information may include a frequency domain allocation (e.g., a number of resource blocks (RBs), a location of one or more RBs, or both), a time domain allocation (e.g., a start time, a duration, or both), a beam indication (e.g., a transmission configuration indicator (TCI) state, a spatial relation, or a beam sweep pattern - a time division multiplexed (TDMed) beam, a frequency division multiplexed (FDMed) beam, a spatial division multiplexed (SDMed) beam, or a combination thereof), a demodulation reference signal (DMRS) configuration (e.g., typeA/typeB, an initialization sequence, one or more antenna portions, or a combination thereof), a cell identifier (ID), a bandwidth part (BWP) ID, or a combination thereof.
- a frequency domain allocation e.g., a number of resource blocks (RBs), a location of one or more RBs, or both
- the scheduling information may include a hybrid automatic repeat request (HARQ) information (e.g,. a HARQ process ID, code block group (CBG) information, redundancy version, or a combination thereof), uplink (UL) feedback information (e.g., a PUCCH resource indicator, time distance from PDSCH to PUCCH, downlink (DL) assignment index, or a combination thereof), link adaptation information (e.g., a modulation code scheme (MCS), Transmission Power Control (TPC) command, sounding reference signal (SRS)/channel state information (CSI) request, or a combination thereof), or a combination thereof.
- HARQ hybrid automatic repeat request
- HARQ uplink
- UL feedback information e.g., a PUCCH resource indicator, time distance from PDSCH to PUCCH, downlink (DL) assignment index, or a combination thereof
- link adaptation information e.g., a modulation code scheme (MCS), Transmission Power Control (TPC) command, sounding reference signal (SRS)/channel state
- a UE may identify the scheduling information included in the DCI. Additionally, the UE may schedule on or more transmissions (e.g., multiple transmission) based on the identified scheduling information. Additionally, or alternatively, the UE may transmit a common ACK/NACK using multiple transmissions on the different entities of the plurality of entities.
- the UE may decode the DCI and, based on the decoded
- a single DCI can schedule xCarrier repetition of PDSCH.
- the DCI can include an index of a pre configured repetition pattern, such as a candidate repetition pattern that includes a non repetition pattern with one transmission on one entity.
- the repetition pattern indicates a channel is repeated over a set of one of one or more entities and a format/location of the channel per entity.
- xCarrier repetition can be scheduled with a pre-configured pattern, such as a pre-configured pattern indicated by one or more bits (e.g., a single bit) of the DCI.
- the same DCI can be repeated over a set of CCs to facilitate UE combining.
- a single DCI can schedule xCarrier repetition of
- a single DCI can schedule xCarrier repetition and beam sweep for PDSCH/PUCCH/PUSCH.
- xCarrier PDCCH repetition can be further configured with beam sweep to mitigate blocking.
- the different entities include entities of different quasi co located (QCL) groups.
- the DCI may indicate carrier repetition, a beam sweep pattern, or both, per QCL group.
- a UE supports multiple xCarrier QCL groups.
- a single DCI can indicate xCarrier repetition and beam sweep pattern per QCL group for PDSCH/PUCCH/PUSCH.
- a DCI scheduling xCarrier repetition and beam sweep in presence of a frequency range, such as FR1 in 5G, can also be sent on the first frequency range at least in addition to those sent on a frequency range, such as FR2 in 5G, to improve control robustness, while minimizing resource usage on the first frequency range.
- the same DCI on the first frequency range can also schedule repetitions on the first frequency range, whose resource can be canceled or reassigned if ACK is received on the second frequency range.
- the UE may perform, based on the DCI, beam sweep for a channel, such as PDSCH, PUCCH, PUSCH, or a combination thereof, as illustrative, non limiting examples.
- the beam sweep may be applied to each entity of the different entities or may be scheduled per entity.
- the beam sweep includes a beam sweep pattern that includes a TDMed beam, a FDMed beam, a SDMed beam, or a combination thereof.
- the present disclosure describes techniques relate to improved methods, systems, devices, and apparatuses for scheduling one or more transmissions using DCI. Accordingly, as compared to conventional techniques in which one transmission is scheduled per DCI on an entity (e.g., a CC) via which the DCI was received, the present techniques provide scheduling of one or more transmissions on at least one entity different from the entity via which the DCI was communicated, thereby improving performance, reliability, and scheduling.
- entity e.g., a CC
- This disclosure relates generally to providing or participating in authorized shared access between two or more wireless communications systems, also referred to as wireless communications networks.
- the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, Global System for Mobile Communications (GSM) networks, 5 th Generation (5G) or new radio (NR) networks (sometimes referred to as“5G NR” networks/systems/devices), as well as other communications networks.
- CDMA code division multiple access
- TDMA time division multiple access
- FDMA frequency division multiple access
- OFDMA orthogonal FDMA
- SC-FDMA single-carrier FDMA
- LTE Long Term Evolution
- GSM Global System for Mobile Communications
- 5G 5 th Generation
- NR new radio
- An OFDMA network may implement a radio technology such as evolved UTRA (E-
- UTRA universal mobile telecommunication system
- LTE long term evolution
- 3GPP 3rd Generation Partnership Project
- cdma2000 3rd Generation Partnership Project 2
- 3GPP 3rd Generation Partnership Project
- 3GPP long term evolution LTE
- UMTS universal mobile telecommunications system
- the 3 GPP may define specifications for the next generation of mobile networks, mobile systems, and mobile devices.
- the present disclosure is concerned with the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond with shared access to wireless spectrum between networks using a collection of new and different radio access technologies or radio air interfaces.
- 5G networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified, air interface. To achieve these goals, further enhancements to LTE and LTE-A are considered in addition to development of the new radio technology for 5G NR networks.
- the 5G NR will be capable of scaling to provide coverage (1) to a massive Internet of things (IoTs) with an ultra- high density (e.g., ⁇ 1M nodes/km 2 ), ultra-low complexity (e.g., ⁇ 10s of bits/sec), ultra-low energy (e.g., -10+ years of battery life), and deep coverage with the capability to reach challenging locations; (2) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (e.g., -99.9999% reliability), ultra-low latency (e.g., - 1 ms), and users with wide ranges of mobility or lack thereof; and (3) with enhanced mobile broadband including extreme high capacity (e.g., ⁇ 10 Tbps/km 2 ), extreme data rates (e.g., multi-Gbps rate, 100+ Mbps user experienced rates), and deep awareness with advanced discovery and optimizations.
- IoTs Internet of things
- ultra-high density e.g., ⁇ 1M nodes/km 2
- 5G NR devices, networks, and systems may be implemented to use optimized OFDM- based waveform features. These features may include scalable numerology and transmission time intervals (TTIs); having a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD)/frequency division duplex (FDD) design; and with advanced wireless technologies, such as massive multiple input, multiple output (MIMO), robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility.
- TTIs transmission time intervals
- TDD dynamic, low-latency time division duplex
- FDD frequency division duplex
- MIMO massive multiple input, multiple output
- mmWave millimeter wave
- Scalability of the numerology in 5G NR with scaling of subcarrier spacing, may efficiently address operating diverse services across diverse spectrum and diverse deployments.
- subcarrier spacing may occur with 15 kHz, for example over 1, 5, 10, 20 MHz, and the like bandwidth.
- subcarrier spacing may occur with 30 kHz over 80/100 MHz bandwidth.
- the subcarrier spacing may occur with 60 kHz over a 160 MHz bandwidth.
- subcarrier spacing may occur with 120 kHz over a 500MHz bandwidth.
- the scalable numerology of the 5G NR facilitates scalable TTI for diverse latency and quality of service (QoS) requirements. For example, shorter TTI may be used for low latency and high reliability, while longer TTI may be used for higher spectral efficiency.
- QoS quality of service
- 5G NR also contemplates a self-contained integrated subframe design with uplink/downlink scheduling information, data, and acknowledgement in the same subframe.
- the self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink/downlink that may be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet the current traffic needs.
- FIG. 1 is a block diagram illustrating 5G network 100 including various base stations and UEs configured according to aspects of the present disclosure.
- the 5G network 100 includes a number of base stations 105 and other network entities.
- a base station may be a station that communicates with the UEs and may also be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, and the like.
- eNB evolved node B
- gNB next generation eNB
- Each base station 105 may provide communication coverage for a particular geographic area.
- the term “cell” can refer to this particular geographic coverage area of a base station or a base station subsystem serving the coverage area, depending on the context in which the term is used.
- a base station may provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, other types of cell, or a combination thereof.
- a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider.
- a small cell, such as a pico cell would generally cover a relatively smaller geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider.
- a small cell such as a femto cell, would also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, and the like).
- a base station for a macro cell may be referred to as a macro base station.
- a base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station or a home base station. In the example shown in FIG.
- the base stations 105d and 105e are regular macro base stations, while base stations 105a- 105c are macro base stations enabled with one of 3 dimension (3D), full dimension (FD), or massive MIMO.
- Base stations 105a- 105c take advantage of their higher dimension MIMO capabilities to exploit 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity.
- Base station 105f is a small cell base station which may be a home node or portable access point.
- a base station may support one or multiple (e.g., two, three, four, and the like) cells.
- the 5G network 100 may support synchronous or asynchronous operation.
- the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time.
- the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time.
- the UEs 115 are dispersed throughout the wireless network 100, and each UE may be stationary or mobile.
- a UE may also be referred to as a terminal, a mobile station, a subscriber unit, a station, or the like.
- a UE may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, or the like.
- PDA personal digital assistant
- WLL wireless local loop
- a UE may be a device that includes a Universal Integrated Circuit Card (UICC).
- a UE may be a device that does not include a UICC.
- UICC Universal Integrated Circuit Card
- UEs that do not include UICCs may also be referred to as internet of everything (IoE) or internet of things (IoT) devices.
- UEs 115a-115d are examples of mobile smart phone-type devices accessing 5G network 100
- a UE may also be a machine specifically configured for connected communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like.
- UEs 115e-l 15k are examples of various machines configured for communication that access 5G network 100.
- a UE may be able to communicate with any type of the base stations, whether macro base station, small cell, or the like. In FIG.
- a lightning bolt (e.g., communication links) indicates wireless transmissions between a UE and a serving base station, which is a base station designated to serve the UE on the downlink or uplink, or desired transmission between base stations, and backhaul transmissions between base stations.
- base stations 105a-105c serve UEs 115a and 115b using 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity.
- Macro base station 105d performs backhaul communications with base stations 105a- 105c, as well as small cell, base station 105f.
- Macro base station 105d also transmits multicast services which are subscribed to and received by UEs 115c and 115d.
- Such multicast services may include mobile television or stream video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.
- 5G network 100 also support mission critical communications with ultra-reliable and redundant links for mission critical devices, such UE 115e, which is a drone. Redundant communication links with UE 115e include from macro base stations 105d and 105e, as well as small cell base station 105f.
- UE 115f thermometer
- UE 115g smart meter
- UE 115h wearable device
- 5G network 100 may also provide additional network efficiency through dynamic, low-latency TDD/FDD communications, such as in a vehicle-to- vehicle (V2V) mesh network between UEs 115i-l 15k communicating with macro base station 105e.
- V2V vehicle-to- vehicle
- FIG. 2 shows a block diagram of a design of a base station 105 and a UE 115, which may be one of the base station and one of the UEs in FIG. 1.
- a transmit processor 220 may receive data from a data source 212 and control information from a controller/processor 240.
- the control information may be for the PBCH, PCFICH, PHICH, PDCCH, EPDCCH, MPDCCH etc.
- the data may be for the PDSCH, etc.
- the transmit processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively.
- the transmit processor 220 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal.
- a transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 232a through 232t.
- Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream.
- Each modulator 232 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 232a through 232t may be transmitted via the antennas 234a through 234t, respectively.
- the antennas 252a through 252r may receive the downlink signals from the base station 105 and may provide received signals to the demodulators (DEMODs) 254a through 254r, respectively.
- Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
- Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols.
- a MIMO detector 256 may obtain received symbols from all the demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
- a receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 115 to a data sink 260, and provide decoded control information to a controller/processor 280.
- a transmit processor 264 may receive and process data
- the transmit processor 264 may also generate reference symbols for a reference signal. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by the modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105.
- the uplink signals from the UE 115 may be received by the antennas 234, processed by the demodulators 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 115.
- the processor 238 may provide the decoded data to a data sink 239 and the decoded control information to the controller/processor 240.
- the controllers/processors 240 and 280 may direct the operation at the base station
- the controller/processor 240 or other processors and modules at the base station 105 may perform or direct the execution of various processes for the techniques described herein, such as perform or direct the execution of the function blocks illustrate in FIGs. 9-10.
- the controllers/processor 280 or other processors and modules at the UE 115 may also perform or direct the execution of the functional blocks illustrated in FIGs. 7-8, or other processes for the techniques described herein.
- the memories 242 and 282 may store data and program codes for the base station 105 and the UE 115, respectively.
- a scheduler 244 may schedule UEs for data transmission on the downlink or uplink.
- a network operating entity may be configured to use an entirety of a designated shared spectrum for at least a period of time before another network operating entity uses the entirety of the designated shared spectrum for a different period of time.
- certain resources e.g., time
- a network operating entity may be allocated certain time resources reserved for exclusive communication by the network operating entity using the entirety of the shared spectrum.
- the network operating entity may also be allocated other time resources where the entity is given priority over other network operating entities to communicate using the shared spectrum.
- These time resources, prioritized for use by the network operating entity may be utilized by other network operating entities on an opportunistic basis if the prioritized network operating entity does not utilize the resources. Additional time resources may be allocated for any network operator to use on an opportunistic basis.
- Access to the shared spectrum and the arbitration of time resources among different network operating entities may be centrally controlled by a separate entity, autonomously determined by a predefined arbitration scheme, or dynamically determined based on interactions between wireless nodes of the network operators.
- UE 115 and base station 105 may operate in a shared radio frequency spectrum band, which may include licensed or unlicensed (e.g., contention-based) frequency spectrum.
- UEs 115 or base stations 105 may traditionally perform a medium-sensing procedure to contend for access to the frequency spectrum.
- UE 115 or base station 105 may perform a listen before talk (LBT) procedure such as a clear channel assessment (CCA) prior to communicating in order to determine whether the shared channel is available.
- LBT listen before talk
- CCA clear channel assessment
- a CCA may include an energy detection procedure to determine whether there are any other active transmissions.
- a device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that a channel is occupied.
- RSSI received signal strength indicator
- a CCA also may include detection of specific sequences that indicate use of the channel.
- another device may transmit a specific preamble prior to transmitting a data sequence.
- an LBT procedure may include a wireless node adjusting its own backoff window based on the amount of energy detected on a channel or the acknowledge/negative-acknowledge (ACK/NACK) feedback for its own transmitted packets as a proxy for collisions.
- ACK/NACK acknowledge/negative-acknowledge
- base stations 105 and UEs 115 may be operated by the same or different network operating entities. In some examples, an individual base station 105 or UE 115 may be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 may be operated by a single network operating entity. Requiring each base station 105 and UE 115 of different network operating entities to contend for shared resources may result in increased signaling overhead and communication latency.
- FIG. 3 illustrates an example of a timing diagram 300 for coordinated resource partitioning.
- the timing diagram 300 includes a superframe 305, which may represent a fixed duration of time (e.g., 20 ms).
- Superframe 305 may be repeated for a given communication session and may be used by a wireless system such as 5G network 100 described with reference to FIG. 1.
- the superframe 305 may be divided into intervals such as an acquisition interval (A-INT) 310 and an arbitration interval 315.
- A-INT acquisition interval
- arbitration interval 315 As described in more detail below, the A-INT 310 and arbitration interval 315 may be subdivided into sub intervals, designated for certain resource types, and allocated to different network operating entities to facilitate coordinated communications between the different network operating entities.
- the arbitration interval 315 may be divided into a plurality of sub intervals 320.
- the superframe 305 may be further divided into a plurality of subframes 325 with a fixed duration (e.g., 1 ms). While timing diagram 300 illustrates three different network operating entities (e.g., Operator A, Operator B, Operator C), the number of network operating entities using the superframe 305 for coordinated communications may be greater than or fewer than the number illustrated in timing diagram 300.
- the A-INT 310 may be a dedicated interval of the superframe 305 that is reserved for exclusive communications by the network operating entities.
- each network operating entity may be allocated certain resources within the A-INT 310 for exclusive communications.
- resources 330-a may be reserved for exclusive communications by Operator A, such as through base station 105a
- resources 330-b may be reserved for exclusive communications by Operator B, such as through base station 105b
- resources 330-c may be reserved for exclusive communications by Operator C, such as through base station 105c. Since the resources 330-a are reserved for exclusive communications by Operator A, neither Operator B nor Operator C can communicate during resources 330-a, even if Operator A chooses not to communicate during those resources.
- the wireless nodes of Operator A may communicate any information desired during their exclusive resources 330-a, such as control information or data.
- the A-INT 310 is used to transmit control information, such as synchronization signals (e.g., SYNC signals), system information (e.g., system information blocks (SIBs)), paging information (e.g., physical broadcast channel (PBCH) messages), or random access information (e.g., random access channel (RACH) signals).
- control information such as synchronization signals (e.g., SYNC signals), system information (e.g., system information blocks (SIBs)), paging information (e.g., physical broadcast channel (PBCH) messages), or random access information (e.g., random access channel (RACH) signals).
- SIBs system information blocks
- PBCH physical broadcast channel
- RACH random access channel
- resources may be classified as prioritized for certain network operating entities.
- Resources that are assigned with priority for a certain network operating entity may be referred to as a guaranteed interval (G-INT) for that network operating entity.
- G-INT guaranteed interval
- the interval of resources used by the network operating entity during the G-INT may be referred to as a prioritized sub-interval.
- resources 335-a may be prioritized for use by Operator A and may therefore be referred to as a G-INT for Operator A (e.g., G-INT- OpA).
- resources 335-b may be prioritized for Operator B
- resources 335-c may be prioritized for Operator C
- resources 335-d may be prioritized for Operator A
- resources 335- e may be prioritized for Operator B
- resources 335-f may be prioritized for operator C.
- the various G-INT resources illustrated in FIG. 3 appear to be staggered to illustrate their association with their respective network operating entities, but these resources may all be on the same frequency bandwidth. Thus, if viewed along a time-frequency grid, the G- INT resources may appear as a contiguous line within the superframe 305. This partitioning of data may be an example of time division multiplexing (TDM). Also, when resources appear in the same sub-interval (e.g., resources 340-a and resources 335-b), these resources represent the same time resources with respect to the superframe 305 (e.g., the resources occupy the same sub-interval 320), but the resources are separately designated to illustrate that the same time resources can be classified differently for different operators.
- TDM time division multiplexing
- resources are assigned with priority for a certain network operating entity (e.g., a G-INT)
- that network operating entity may communicate using those resources without having to wait or perform any medium sensing procedures (e.g., LBT or CCA).
- LBT or CCA medium sensing procedures
- the wireless nodes of Operator A are free to communicate any data or control information during resources 335-a without interference from the wireless nodes of Operator B or Operator C.
- a network operating entity may additionally signal to another operator that it intends to use a particular G-INT. For example, referring to resources 335-a, Operator A may signal to Operator B and Operator C that it intends to use resources 335-a. Such signaling may be referred to as an activity indication. Moreover, since Operator A has priority over resources 335-a, Operator A may be considered as a higher priority operator than both Operator B and Operator C. However, as discussed above, Operator A does not have to send signaling to the other network operating entities to ensure interference-free transmission during resources 335-a because the resources 335-a are assigned with priority to Operator A.
- a network operating entity may signal to another network operating entity that it intends not to use a particular G-INT. This signaling may also be referred to as an activity indication.
- Operator B may signal to Operator A and Operator C that it intends not to use the resources 335-b for communication, even though the resources are assigned with priority to Operator B.
- Operator B may be considered a higher priority network operating entity than Operator A and Operator C. In such cases, Operators A and C may attempt to use resources of sub-interval 320 on an opportunistic basis.
- the sub-interval 320 that contains resources 335-b may be considered an opportunistic interval (O-INT) for Operator A (e.g., O-INT-OpA).
- O-INT opportunistic interval
- resources 340-a may represent the O-INT for Operator A.
- the same sub-interval 320 may represent an O-INT for Operator C with corresponding resources 340-b.
- Resources 340-a, 335-b, and 340-b all represent the same time resources (e.g., a particular sub-interval 320), but are identified separately to signify that the same resources may be considered as a G-INT for some network operating entities and yet as an O-INT for others.
- Operator A and Operator C may perform medium-sensing procedures to check for communications on a particular channel before transmitting data. For example, if Operator B decides not to use resources 335-b (e.g., G-INT-OpB), then Operator A may use those same resources (e.g., represented by resources 340-a) by first checking the channel for interference (e.g., LBT) and then transmitting data if the channel was determined to be clear.
- resources 335-b e.g., G-INT-OpB
- Operator C may perform a medium sensing procedure and access the resources if available.
- two operators e.g., Operator A and Operator C
- the operators may also have sub-priorities assigned to them designed to determine which operator may gain access to resources if more than operator is attempting access simultaneously.
- a network operating entity may intend not to use a particular G-
- lower priority operating entities may be configured to monitor the channel to determine whether a higher priority operating entity is using the resources. If a lower priority operating entity determines through LBT or similar method that a higher priority operating entity is not going to use its G-INT resources, then the lower priority operating entities may attempt to access the resources on an opportunistic basis as described above.
- access to a G-INT or O-INT may be preceded by a reservation signal (e.g., request-to-send (RTS)/clear-to-send (CTS)), and the contention window (CW) may be randomly chosen between one and the total number of operating entities.
- a reservation signal e.g., request-to-send (RTS)/clear-to-send (CTS)
- CW contention window
- an operating entity may employ or be compatible with coordinated multipoint (CoMP) communications.
- CoMP coordinated multipoint
- an operating entity may employ CoMP and dynamic time division duplex (TDD) in a G-INT and opportunistic CoMP in an O-INT as needed.
- TDD dynamic time division duplex
- each sub-interval 320 includes a G-INT for one of Operator A, B, or C.
- one or more sub-intervals 320 may include resources that are neither reserved for exclusive use nor reserved for prioritized use (e.g., unassigned resources). Such unassigned resources may be considered an O-INT for any network operating entity, and may be accessed on an opportunistic basis as described above.
- each subframe 325 may contain 14 symbols (e.g., 250-ps for 60 kHz tone spacing). These subframes 325 may be standalone, self-contained Interval-Cs (ITCs) or the subframes 325 may be a part of a long ITC.
- An ITC may be a self-contained transmission starting with a downlink transmission and ending with a uplink transmission.
- an ITC may contain one or more subframes 325 operating contiguously upon medium occupation. In some cases, there may be a maximum of eight network operators in an A-INT 310 (e.g., with duration of 2 ms) assuming a 250-ps transmission opportunity.
- each sub-interval 320 may be occupied by a G-INT for that single network operating entity, or the sub-intervals 320 may alternate between G-INTs for that network operating entity and O-INTs to allow other network operating entities to enter.
- the sub-intervals 320 may alternate between G-INTs for the first network operating entity and G-INTs for the second network operating entity. If there are three network operating entities, the G-INT and O-INTs for each network operating entity may be designed as illustrated in FIG. 3. If there are four network operating entities, the first four sub-intervals 320 may include consecutive G-INTs for the four network operating entities and the remaining two sub-intervals 320 may contain O-INTs. Similarly, if there are five network operating entities, the first five sub-intervals 320 may contain consecutive G- INTs for the five network operating entities and the remaining sub-interval 320 may contain an O-INT. If there are six network operating entities, all six sub-intervals 320 may include consecutive G-INTs for each network operating entity. It should be understood that these examples are for illustrative purposes only and that other autonomously determined interval allocations may be used.
- FIG. 3 is for illustration purposes only.
- the duration of superframe 305 may be more or less than 20 ms.
- the number, duration, and location of sub-intervals 320 and subframes 325 may differ from the configuration illustrated.
- the types of resource designations e.g., exclusive, prioritized, unassigned
- FIG. 4 illustrates an example of a wireless communications system 400 that supports scheduling using DCI, in accordance with aspects of the present disclosure.
- wireless communications system 400 may implement aspects of wireless communication system 100.
- wireless communications system 400 may include base station 105 and UE 115.
- Base station 105 and UE 115 and base station 105 may be configured to communicate via one or more entities, such as a component carrier, a cell, or a frequency allocation.
- communications e.g., transmissions
- channels such as PDSCH, PUCCH, PUSCH, or PRACH, as illustrative, non-limiting examples.
- Base station 105 and UE 115 may be configured to communicate via frequency bands, such as FR1 having a frequency of 450 to 6000 MHz for Sub-6 GHz or FR2 having a frequency of 24250 to 2600 MHz for mm-Wave. It is noted that sub-carrier spacing (SCS) may be equal to 15, 30, 60, or 120 kHz for some data channels, as illustrative, non-limiting examples.
- Base station 105 and UE 115 may be configured to communicate via one or more CCs, such as representative first CC 481, second CC 482, third CC 483, and fourth CC 484. Although four CCs are shown, this is for illustration only, and more or fewer than four CCs may be used.
- One or more CCs may be used to communicate Physical Downlink Control Channel (PDCCH), PDSCH, PUCCH, or PUSCH.
- PDCH Physical Downlink Control Channel
- PDSCH Physical Downlink Control Channel
- PUCCH Physical Downlink Control Channel
- PUSCH Physical Downlink Control Channel
- one or more CCs such as CCs 481, 482, may be included in FR2
- one or more other CCs such as CCs 483, 483 may be included in FR1.
- Each CC may have a corresponding configuration, such as configuration parameters/settings.
- the configuration may include bandwidth, bandwidth part, HARQ process, TCI state, RS, control channel resources, data channel resources, or a combination thereof.
- one or more CCs may have or be assigned to a cell ID, a BWP ID, or both.
- the cell ID may include a unique cell ID for the CC, a virtual cell ID, or a particular cell ID of a particular CC of the plurality of CCs.
- one or more CCs may have or be assigned to a HARQ ID.
- Each CC may also have corresponding management functionalities, such as, beam management, BWP switching functionality, or both.
- each CC may include one or more corresponding beam patterns, a beam sweep pattern, a communication (e.g., transmission/reception) schedule, or a combination thereof.
- two or more CCs are quasi co-located, such that the CCs have the same beam or same symbol.
- CCs may be grouped as a set of one or more CCs, such as a xCarrier coreset. Each CC in a coreset may have the same cell ID, the same HARQ ID, or both.
- control information may be communicated via base station
- control information may be communicated suing MAC- CE transmissions, RRC transmissions, DCI, transmissions, another transmission, or a combination thereof.
- a DCI 448 is communicated from base station 105 to UE 115.
- DCI 448 includes one or more bits 449.
- the one or more bits is a single bit.
- One or more bits 449 may include or indicate schedule information, also referred to as scheduling information.
- the schedule information may include or correspond to a frequency domain allocation (e.g., a number of RBs, a location of one or more RBs, or both), a time domain allocation (e.g., a start time, a duration, or both), a beam indication (e.g., a TCI state, a spatial relation, or a beam sweep pattern - a TDMed beam, a FDMed beam, a SDMed beam, or a combination thereof), a DMRS configuration (e.g., typeA/typeB, an initialization sequence, one or more antenna portions, or a combination thereof), a cell ID, a BWP ID, or a combination thereof.
- a frequency domain allocation e.g., a number of RBs, a location of one or more RBs, or both
- a time domain allocation e.g., a start time, a duration, or both
- a beam indication e.g., a TCI state, a spatial relation, or
- the schedule information may include or correspond to HARQ information (e.g,. a HARQ ID, a HARQ process ID, CBG information, redundancy version, or a combination thereof), UL feedback information (e.g., a PUCCH resource indicator, time distance from PDSCH to PUCCH, DL assignment index, or a combination thereof), link adaptation information (e.g., a MCS, Transmission Control Protocol (TCP) command, SRS/channel state information (SCI) request, or a combination thereof), or a combination thereof.
- the one or more bits 449 may include or correspond to schedule information stored or set at base station 105, UE 115, or both.
- the schedule information is pre-configured, such as based on one or more standards.
- the schedule information may include or correspond to schedule information 443 at or accessible to base station, schedule information 423 at or accessible to UE 115, or both.
- a device e.g., base station 105 or UE 115
- a device e.g., base station 105 or UE 115
- the device is further configured to schedule one or more transmission via a second entity (e.g., 482) of the plurality of entities (e.g., 481-484), the second entity (e.g., 482) different from the first entity (e.g., 481). Additional functionality with respect to the device is described herein at least with reference to FIGs. 4-13.
- Base station 105 includes processor 430, memory 432, transmitter 434, receiver 436, an encoder 437, decoder 438, combiner 439, and 234a-t.
- Processor 430 may be configured to execute instructions 440 stored at memory 432 to perform the operations described herein.
- processor 430 includes or corresponds to controller/processor 240
- memory 432 includes or corresponds to memory 242.
- Memory 432 may also be configured to store one or more configurations 441, one or more IDs values 442, schedule information 443, or both, as further described herein.
- the one or more configurations 441 may be bandwidth, bandwidth part, HARQ process, TCI state, RS, control channel resources, data channel resources, or a combination thereof.
- the one or more configurations 441 may include or correspond to the one or more bits 449 - e.g., the one or more configurations 441 may include or correspond to one or more pre-configured configurations.
- the one or more IDs 442 may be a common cell ID (e.g., a virtual cell ID or a particular cell ID of a particular CC of the plurality of CCs) or a common BWP ID.
- Transmitter 434 is configured to transmit data to one or more other devices
- receiver 436 is configured to receive data from one or more other devices.
- transmitter 434 may transmit data
- receiver 436 may receive data, via a network, such as a wired network, a wireless network, or a combination thereof.
- base station 105 may be configured to transmit or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate.
- LAN local area network
- WAN wide area network
- modem-to-modem connection the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate.
- transmitter 434 and receiver 436 may be replaced with a transceiver. Additionally, or alternatively, transmitter 434, receiver, 436, or both may include or correspond to one or more components of base station 105 described with reference to FIG. 2. In some implementations, transmitter 434, receiver, 436, or both may be included in one more wireless radios, as described with reference to FIG. 15.
- Encoder 437 and decoder 438 may be configured to encode and decode, such as jointly encoding and jointly decoding, respectively.
- Combiner 439 may be configured to combine xCarrier data to generate combined data, such as combined data for decoding.
- base station 105 may also include a scheduler configured to perform one or more operations herein described with reference to DCI 448 or scheduling one or more transmissions based on DCI 448.
- UE 115 includes processor 402, memory 404, transmitter 410, receiver 412, an encoder 413, decoder 414, combiner 415, and 252a-r.
- Processor 402 may be configured to execute instructions 420 stored at memory 404 to perform the operations described herein.
- processor 402 includes or corresponds to controller/processor 280
- memory 404 includes or corresponds to memory 282.
- Memory 432 may also be configured to store one or more configurations 421, one or more IDs values 422, or both, as further described herein.
- the one or more configurations 421 may be bandwidth, bandwidth part, HARQ process, TCI state, RS, control channel resources, data channel resources, or a combination thereof.
- the one or more configurations 421 may include or correspond to the one or more bits 449 - e.g., the one or more configurations 421 may include or correspond to one or more pre-configured configurations.
- the one or more IDs 422 may be a common cell ID (e.g., a virtual cell ID or a particular cell ID of a particular CC of the plurality of CCs) or a common BWP ID.
- the configurations 421 and ID(s) 422 may correspond to configurations 41 and ID(s) 442, respectively.
- Transmitter 410 is configured to transmit data to one or more other devices
- receiver 412 is configured to receive data from one or more other devices.
- transmitter 410 may transmit data
- receiver 412 may receive data, via a network, such as a wired network, a wireless network, or a combination thereof.
- UE 115 may be configured to transmit or receive data via a direct device-to-device connection, a LAN, a WAN, a modem-to-modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate.
- transmitter 410 and receiver 412 may be replaced with a transceiver. Additionally, or alternatively, transmitter 410, receiver, 412, or both may include or correspond to one or more components of UE 115 described with reference to FIG. 2. In some implementations, transmitter 410, receiver, 412, or both may be included in one more wireless radios, as described with reference to FIG. 14. Encoder 413, decoder 414, and combiner 415 may include the same functionality as described with reference to encoder 437, decoder 438, and combiner 439, respectively. In some implementations, UE 115 may also include a scheduler configured to perform one or more operations herein described with reference to DCI 448 or scheduling one or more transmissions based on DCI 448.
- base station 105 may identify or generate DCI 448. For example, base station 105 may generate and transmit DCI 448 including one or more bits 449. DCI 448 (e.g., the one or more bits 449) may include or correspond to (e.g., indicate) schedule information (e.g., 443, 423). In some implementations, base station 105 sends DCI 448 to UE 115 to schedule one or more transmissions.
- DCI 448 e.g., the one or more bits 449
- schedule information e.g., 443, 423
- Base station 105 may jointly encode PDCCH to be transmitted via multiple CCs - e.g., xCarrier repetition. For example, base station 105 may transmit first PDCCH 450 via first CC 481 and may transmit second PDCCH 460 via second CC 482. Additionally, base station 105 may jointly encode PDSCH to be transmitted via multiple CCs - e.g., xCarrier repetition. For example, base station 105 may transmit first PDSCH 452 via first CC 481 and may transmit second PDSCH 462 via second CC 482.
- UE 115 receives the multiple PDCCH (e.g., 450, 460) and generates a combined PDCCH (e.g., 450, 460) and generates a combined PDCCH (e.g., 450, 460)
- combiner 415 may be configured to combine energies of the multiple PDCCH to generate combined PDCCH 416. Decoder 414 may decode the combined PDCCH 416.
- UE 115 receives the multiple PDSCH (e.g., 452, 462) corresponding to the multiple PDCCH (e.g., 450, 460) and generates a combined PDSCH 417.
- combiner 415 may be configured to combine energies of the multiple PDSCH to generate combined PDSCH 417. Decoder 414 may decode the combined PDSCH 417.
- UE 115 Based on the decoding of combined PDSCH 417, UE 115 sends PUCCH to base station 105. For example, UE 115 may use encoder 413 to jointly encode PUCCH into first PUCCH 454 and second PUCCH 464 which are sent to base station 105. To illustrate, first PUCCH 454 may be sent via first CC 481 and second PUCCH 464 may be sent via second CC 482.
- PUCCH may include or correspond to an acknowledgment message, such as an ACK/NACK.
- UE 115 may send an ACK or a NACK base on a determination of whether combined PUSCH was successfully decoded. To illustrate, the ACK is communicated if decoding is successful and the NACK is communicated if decoding is unsuccessful.
- Base station 105 receives the multiple PUCCH (e.g., 454, 464) and generates a combined PUCCH 4345 based on the multiple PUCCH.
- combiner 439 may be configured to combine energies of the multiple PUCCH to generate combined PUCCH 435.
- Decoder 438 may decode the combined PUCCH 435.
- FIG. 4 Operations of FIG. 4 are described further herein with reference to FIGs. 5-9. FIGs.
- FIGs. 5-9 include examples of wireless communication, scheduled based on DCI 448, between base station 105 and UE 115.
- DCI 448 DCI based xCarrier repetition on downlink or beam sweep.
- FIGs. 5-9 show multiple CCs over an illustrative cycle, such as a 1 ms cycle.
- Each of FIGs. 5-9 shows one or more transmissions via the CCs.
- At least one of the transmission may be scheduled according to a DCI (e.g., 448).
- the at least one transmission may include or correspond to a channel, such as PDSCH, PUCCH, PUSCH, or PRACH, as illustrative, non-limiting examples.
- a channel such as PDSCH, PUCCH, PUSCH, or PRACH
- the wireless communication may include DCI based xCarrier repetition on DL channels.
- a DCI e.g., 484
- UE e.g. 115
- UE can determine a whole set of multi-CC repetition as long as one DCI is decoded.
- xCarrier repetition can be scheduled with a pre-configured pattern, e.g. a single bit can indicate the PDSCH is repeated over a set of CCs with same format/location per CC.
- the pre-configured pattern may be included in configurations 421, 441 or schedule information 423, 443.
- search space with xCarrier PDCCH repetition can be configured such that the same DCI is repeated over a set of CCs to facilitate UE combining.
- the wireless communication may include DCI based xCarrier repetition on UL channels.
- a common A/N is generated based on combining or individual decoding, and can be sent by PUCCH cell configured per PDSCH repetition receiving cell.
- a DCI e.g., 484
- a single DCI can also schedule xCarrier repetition of PUCCH/PUSCH.
- the PUCCH per PUCCH group can be repeated over a set of CCs.
- same indicator can indicate xCarrier PDSCH and PUCCH repetition.
- the wireless communication may include DCI based xCarrier repetition and beam sweep.
- a DCI e.g., 484
- a single DCI can schedule xCarrier repetition and beam sweep for PDSCH/PUCCH/PUSCH.
- the same beam sweep pattern on one CC can be applied to each CC of a set of CCs.
- the beam sweep pattern per channel on one CC can be TDMed, SDMed, FDMed.
- xCarrier PDCCH repetition (not shown) can be configured with beam sweep to mitigate blocking.
- the wireless communication may include DCI based xCarrier repetition and beam sweep.
- a UE e.g., 115
- multiple xCarrier QCL groups such as a first QCL group (e.g.,“QCL group 1”) and a second QCL group (e.g.,“QCL group 2”).
- a DCI e.g., 484
- a common ACK/NACK can be carried by each of PUCCHs with xCarrier repetition and beam sweep. In other implementations, a common ACK/NACK can be carried by each of PUCCHs with xCarrier repetition without beam sweep. It is noted that, if UE does not support simultaneous PUCCH Tx by multiple beams, PUCCH Tx per QCL group may have to be TDMed.
- the wireless communication may include DCI based xCarrier repetition and beam sweep.
- FR1 and FR2 are present.
- a DCI e.g., 484
- DCI scheduling xCarrier repetition and beam sweep can be sent on FR1 at least in addition to those sent on FR2 to improve control robustness, while minimizing resource usage on FR1.
- the same DCI on FR1 can also schedule repetitions on FR1, whose resource can be canceled or reassigned if ACK has been received on FR2.
- the described techniques relate to improved methods, systems, devices, and apparatuses for scheduling one or more transmissions using DCI (e.g., 448).
- the one or more transmission may be scheduled, based on the DCI, on one or more entities different from the entity via which the DCI is transmitted.
- the entity may include a component carrier, a cell, or a frequency allocation. If the DCI is received via a first entity, such as a first CC, the one or more transmission may be scheduled on a second entity (different from the first entity) based on the DCI. In some implementations, a transmission may also be scheduled on the first entity in addition to the second entity.
- a UE may receive DCI via an entity of a plurality of entities and schedule, based on the DCI, multiple transmissions on different entities of the plurality of entities.
- each of the multiple transmissions scheduled on the different entities includes the same content.
- each of the multiple transmissions scheduled on the different entities include content correlated to content of the other of the multiple transmissions.
- each of the multiple transmissions scheduled on the different entities include independent content from the other of the multiple transmissions.
- the one or more transmissions may correspond to a channel, which may include PDSCH, PUCCH, PUSCH, or PRACH, as illustrative, non limiting examples.
- the DCI is a single DCI used to schedule multiple transactions across multiple entities (e.g., multiple CCs) such that identical, correlated, or independent information is communicated per transmission. Additionally, or alternatively, the same, single DCI can be repeated over a set of two or more CCs to facilitate UE combining.
- scheduling, based on the DCI, multiple transmissions on different entities may be scrambled by a dedicated RNTI.
- the dedicated RNTI is different from the RNTI for scrambling the DCI scheduling a single transmission on a single entity.
- a device e.g., a base station or a UE may identify DCI communicated via a first entity of plurality of entities, and schedule one or more transmission via a second entity of the plurality of entities, the second entity different from the first entity.
- the entity may include a component carrier, a cell, or a frequency allocation.
- the DCI can include or indicate scheduling information.
- the DCI may include scheduling information for each of multiple transmission.
- the scheduling information may include a frequency domain allocation (e.g., a number of RBs, a location of one or more RBs, or both), a time domain allocation (e.g., a start time, a duration, or both), a beam indication (e.g., a TCI state, a spatial relation, or a beam sweep pattern - a TDMed beam, a FDMed beam, a SDMed beam, or a combination thereof), a DMRS configuration (e.g., typeA/typeB, an initialization sequence, one or more antenna portions, or a combination thereof), a cell ID, a BWP ID, or a combination thereof.
- a frequency domain allocation e.g., a number of RBs, a location of one or more RBs, or both
- a time domain allocation e.g., a start time, a duration, or both
- the scheduling information may include HARQ information (e.g,. a HARQ ID, a HARQ process ID, CBG information, redundancy version, or a combination thereof), UL feedback information (e.g., a PUCCH resource indicator, time distance from PDSCH to PUCCH, DL assignment index, or a combination thereof), link adaptation information (e.g., a MCS, TPC command, SRS/CSI request, or a combination thereof), or a combination thereof.
- HARQ information e.g,. a HARQ ID, a HARQ process ID, CBG information, redundancy version, or a combination thereof
- UL feedback information e.g., a PUCCH resource indicator, time distance from PDSCH to PUCCH, DL assignment index, or a combination thereof
- link adaptation information e.g., a MCS, TPC command, SRS/CSI request, or a combination thereof
- a common ACK/NACK may be generated based on combining or individual
- a UE may identify the scheduling information included in the DCI. Additionally, the UE may schedule on or more transmissions (e.g., multiple transmission) based on the identified scheduling information. Additionally, or alternatively, the UE may transmit a common ACK/NACK using multiple transmissions on the different entities of the plurality of entities. [00113] In some implementations, the UE may decode the DCI and, based on the decoded DCI, identify a repetition pattern. For example, in some implementations, a single DCI can schedule xCarrier repetition of PDSCH. For example, the DCI can include an index of a pre configured repetition pattern, such as a candidate repetition pattern that includes a non repetition pattern with one transmission on one entity.
- the repetition pattern indicates a channel is repeated over a set of one of one or more entities and a format/location of the channel per entity.
- xCarrier repetition can be scheduled with a pre-configured pattern, such as a pre-configured pattern indicated by one or more bits (e.g., a single bit) of the DCI.
- the same DCI can repeated over a set of CCs to facilitate UE combining.
- a single DCI can schedule xCarrier repetition of PUCCH/PUSCH. In other implementations, a single DCI can schedule xCarrier repetition and beam sweep for PDSCH/PUCCH/PUSCH. In some such implementations, xCarrier PDCCH repetition can be further configured with beam sweep to mitigate blocking.
- a UE supports multiple xCarrier QCL groups.
- a single DCI can indicate xCarrier repetition and beam sweep pattern per QCL group for PDSCH/PUCCH/PUSCH.
- a DCI scheduling xCarrier repetition and beam sweep in presence of a frequency range, such as FR1 in 5G, can also be sent on the first frequency range at least in addition to those sent on a frequency range, such as FR2 in 5G, to improve control robustness, while minimizing resource usage on the first frequency range.
- the same DCI on the first frequency range can also schedule repetitions on the first frequency range, whose resource can be canceled or reassigned if ACK is been received on the second frequency range.
- the UE may perform, based on the DCI, beam sweep for a channel, such as PDSCH, PUCCH, PUSCH, or a combination thereof, as illustrative, non limiting examples.
- the beam sweep may be applied to each entity of the different entities or may be scheduled per entity.
- the beam sweep includes a beam sweep pattern that includes a TDMed beam, a FDMed beam, a SDMed beam, or a combination thereof.
- the DCI is received via a different entity from the entities via which the multiple transmission are scheduled. Additionally, or alternatively, some implementations may include receiving the DCI, decoding the DCI, and identifying a repetition pattern based on the decoded DCI. In other implementations, the repetition pattern may be identified based on the DCI. The repetition pattern may be indicated by one or more bits (e.g., a single bit) included in the DCI. Additionally, or alternatively, the repetition pattern indicates a set of one or more entities and a format/location per entity.
- the same DCI is repeated over a set of entities of the plurality of entities.
- a common ACK/NACK may be communicated (e.g., transmitted or received) using the multiple transmissions on the different entities of the plurality of entities.
- a beam sweep for a channel may be scheduled based on the DCI.
- the channel includes PDSCH, PUCCH, PUSCH, or a combination thereof, as illustrative, non-limiting examples.
- the beam sweep may be applied to each entity of the different entities or may be scheduled per entity.
- the beam sweep includes a beam sweep pattern that includes a TDMed beam, a FDMed beam, a SDMed beam, or a combination thereof, as illustrative, non-limiting examples.
- different entities of the plurality of entities include entities of different QCL groups.
- the DCI indicates carrier repetition, a beam sweep pattern, or both, per QCL group.
- FIGs. 4-9 describes scheduling using DCI.
- scheduling using DCI may be used with mmWave for communication between base station 105 and UE 115.
- the present techniques provide scheduling of one or more transmissions on at least one entity different from the entity via which the DCI was communicated, thereby improving performance, reliability, and scheduling.
- FIG. 10 is a block diagrams illustrating example blocks executed by a UE configured according to an aspect of the present disclosure. The example blocks will also be described with respect to UE 115 as illustrated in FIG. 12.
- FIG. 12 is a block diagram illustrating UE 115 configured according to one aspect of the present disclosure.
- UE 115 includes the structure, hardware, and components as illustrated for UE 115 of FIGs. 2 or 4.
- UE 115 includes controller/processor 280, which operates to execute logic or computer instructions stored in memory 282, as well as controlling the components of UE 115 that provide the features and functionality of UE 115.
- UE 115 under control of controller/processor 280, transmits and receives signals via wireless radios 1201a-r and antennas 252a-r.
- Wireless radios 1201a-r includes various components and hardware, as illustrated in FIG. 2 for UE 115, including modulator/demodulators 254a-r, MIMO detector 256, receive processor 258, transmit processor 264, and TX MIMO processor 266.
- memory 282 may include one or more configurations 1202, one or more IDs 1203, encoder logic 1204, decoder logic 1205, combination logic 1206, and schedule information 1207.
- Configurations 1202 and IDs 1203 may include or correspond to configurations 421 and ID(s) 422, respectively.
- Schedule information 1207 may include or correspond to schedule information 423.
- memory 242 may also include scheduler logic configured to parse DCI, identify schedule information (e.g., schedule information included in a DCI), access configurations 1202, access or set schedule information 1207, configure one or more of wireless radios 1201a-r, or a combination thereof.
- Encoder logic 1204, decoder logic 1205, combination logic 1206, or the scheduler logic may include or correspond to encoder 413, decoder 414, and combination 415, respectively.
- encoder logic 1204, decoder logic 1205, and combination logic 1406 may include or correspond to processor(s) 402.
- UE 115 may receive signals from or transmit signal to a base station, such as base station 105 as illustrated in FIG. 13.
- the UE receives DCI via an entity of a plurality of entities.
- UE 115 may execute, under control of controller/processor 280, one or more instructions, stored in memory 282 to receive the DCI.
- the UE determines schedule information for multiple transmissions on different entities of the plurality of entities.
- the UE may identify scheduling information included in or indicated by the DCI and may, based on the scheduling information, schedule receipt or configure the UE to receive at least one of the multiple transmissions.
- UE 115 may execute, under control of controller/processor 280, one or more instructions, stored in memory 282 to schedule the multiple transmissions.
- one or more blocks (or operations) described with reference to FIG. 10 may be combined with one or more blocks (or operations) of another of figure.
- one or more blocks of FIG. 1000 may be combined with one or more blocks (or operations) of another of FIGs. 2, 4, or 112.
- one or more operations described above with reference to FIGs. 1-9 may be combine with one or more operations described with reference to FIG. 10.
- FIG. 11 is a block diagrams illustrating example blocks executed by a base station configured according to an aspect of the present disclosure. The example blocks will also be described with respect to base station 105 as illustrated in FIG. 13.
- FIG. 13 is a block diagram illustrating base station 105 configured according to one aspect of the present disclosure.
- Base station 105 includes the structure, hardware, and components as illustrated for base station 105 of FIGs. 2 or 4.
- base station 105 includes controller/processor 240, which operates to execute logic or computer instructions stored in memory 242, as well as controlling the components of base station 105 that provide the features and functionality of base station 105.
- Base station 105 under control of controller/processor 240, transmits and receives signals via wireless radios 1301a-t and antennas 234a-t.
- Wireless radios 1301a-t includes various components and hardware, as illustrated in FIG. 2 for base station 105, including modulator/demodulators 232a-t, transmit processor 220, TX MIMO processor 230, MIMO detector 236, and receive processor 238.
- memory 242 may include one or more configurations 1302, one or more IDs 1303, encoder logic 1304, decoder logic 1305, combination logic 1306, and schedule information 1307.
- CC configurations 1302 and IDs 1303 may include or correspond to CC configurations 441 and ID(s) 442, respectively.
- Schedule information 1307 may include or correspond to schedule information 443.
- Encoder logic 1304, decoder logic 1305, and combination logic 1306 may include or correspond to encoder 437, decoder 438, and combination 439, respectively.
- memory 242 may also include scheduler logic configured to parse DCI, identify schedule information (e.g., schedule information included in a DCI), access configurations 1302, access or set schedule information 1307, configure one or more of wireless radios 1301a-t, or a combination thereof.
- encoder logic 1304, decoder logic 1305, combination logic 1306, or the scheduler logic may include or correspond to processor(s) 430.
- Base station 105 may receive signals from or transmit signal to a UE, such as UE 115 as illustrated in FIG. 12.
- the base station identifies DCI communicated via an entity of a plurality of entities.
- base station 105 may execute, under control of controller/processor 240, one or more instructions, stored in memory 242 to identify the DCI.
- the base station schedules, based on the DCI, multiple transmissions on different entities of the plurality of entities.
- base station 105 may execute, under control of controller/processor 240, one or more instructions, stored in memory 242 to schedule the multiple transmission.
- one or more blocks (or operations) described with reference to one of FIG. 11 may be combined with one or more blocks (or operations) of another figure.
- one or more blocks of FIG. 11 may be combined with one or more blocks (or operations) of another of FIGs. 2, 4, or 13.
- one or more operations described above with reference to FIGs. 1-9 may be combine with one or more operations described with reference to FIG. 11.
- techniques for scheduling one or more transmissions using DCI may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes or devices described elsewhere herein.
- scheduling one or more transmissions using DCI may include an apparatus receiving DCI via an entity of a plurality of entities; and determining, based on the DCI, scheduling information for multiple transmissions on different entities of the plurality of entities.
- the apparatus includes a wireless device, such as a UE.
- the apparatus may include at least one processor, and a memory coupled to the processor.
- the processor may be configured to perform operations described herein with respect to the wireless device.
- the apparatus may include a non-transitory computer-readable medium having program code recorded thereon and the program code may be executable by a computer for causing the computer to perform operations described herein with reference to the wireless device.
- the apparatus may include one or more means configured to perform operations described herein.
- operations described with reference to the apparatus may include a method for wireless communication.
- the DCI includes the scheduling information for the multiple transmissions on different entities is scrambled by a dedicated RNTI.
- the dedicated RNTI is different from the RNTI for scrambling the DCI scheduling a single transmission on a single entity.
- the multiple transmissions correspond to a channel.
- the channel includes PDSCH, PUCCH, PUSCH, or PRACH.
- each of the multiple transmissions scheduled on the different entities include the same content.
- each of the multiple transmissions scheduled on the different entities include content correlated to content of the other of the multiple transmissions.
- each of the multiple transmissions scheduled on the different entities include independent content from the other of the multiple transmissions.
- the DCI includes the scheduling information for each of the multiple transmissions.
- the apparatus identifies the scheduling information included in the DCI; and schedules receipt of at least one of the multiple transmission based on the identified scheduling information.
- the scheduling information indicates a frequency domain allocation.
- the frequency domain allocation includes a number of RBs, a location of one or more RBs, or both.
- the scheduling information indicates a time domain allocation.
- the time domain allocation includes a start time, a duration, or both.
- the scheduling information includes a beam indication.
- the beam indication indicates a TCI state, a spatial relation, a beam sweep pattern, or a combination thereof.
- the beam sweep pattern includes a TDMed beam, a FDMed beam, a SDMed beam, or a combination thereof.
- the scheduling information includes a DMRS configuration.
- the DMRS configuration includes typeA/typeB, an initialization sequence, one or more antenna portions, or a combination thereof.
- the scheduling information includes a cell ID, a BWP ID, or both.
- the scheduling information includes HARQ information.
- the HARQ information includes a HARQ process ID, CBG information, redundancy version, or a combination thereof.
- the scheduling information includes UL feedback information.
- the UL feedback information includes a PUCCH resource indicator, time distance from PDSCH to PUCCH, DL assignment index, or a combination thereof.
- the scheduling information includes link adaptation information.
- the link adaptation information includes a MCS, TPC command, SRS/CSI request, or a combination thereof.
- the DCI is received via a different entity from the entities via which the multiple transmissions are scheduled.
- the apparatus decodes the DCI, and identifies a repetition pattern based on the decoded DCI.
- the repetition pattern is indicated in the DCI by an index of a pre-configured candidate repetition pattern.
- the candidate repetition pattern includes a non-repetition pattern with one transmission on one entity.
- the repetition pattern indicates a channel is repeated over a set of one or more entities and a format/location of the channel per entity.
- the same DCI is repeated over a set of entities of the plurality of entities.
- the entity includes a component carrier, a cell, or a frequency allocation.
- the apparatus transmits a common ACK/NACK using the multiple transmissions on the different entities of the plurality of entities.
- the apparatus performs, based on the DCI, beam sweep for a channel.
- the channel in combination with the thirty-fourth aspect, includes PDSCH, PUCCH, PUSCH, or a combination thereof.
- the beam sweep is scheduled per entity.
- the beam sweep includes a beam sweep pattern that includes a TDMed beam, a FDMed beam, a SDMed beam, or a combination thereof.
- the different entities include entities of different QCL groups.
- the DCI indicates carrier repetition, a beam sweep pattern, or both, per QCL group.
- the different entities include entities in a first frequency range and a second frequency range.
- the DCI indicates carrier repetition, a beam sweep pattern, or both, on entities of the first frequency range; and one or more transmissions on the second frequency range are canceled or reassigned in response to an ACK received on the second frequency range.
- an apparatus configured for wireless communication is configured to identifying DCI communicated via an entity of a plurality of entities; and scheduling, based on the DCI, multiple transmissions on different entities of the plurality of entities.
- the apparatus includes a wireless device, such as a base station.
- the apparatus may include at least one processor, and a memory coupled to the processor.
- the processor may be configured to perform operations described herein with respect to the wireless device.
- the apparatus may include a non-transitory computer-readable medium having program code recorded thereon and the program code may be executable by a computer for causing the computer to perform operations described herein with reference to the wireless device.
- the apparatus may include one or more means configured to perform operations described herein.
- operations described with reference to the apparatus may include a method for wireless communication.
- the DCI scheduling multiple transmissions on different entities is scrambled by a dedicated RNTI.
- the dedicated RNTI is different from the RNTI for scrambling the DCI scheduling a single transmission on a single entity.
- the multiple transmissions correspond to a channel.
- the channel in combination with the forty-fifth aspect, includes
- PDSCH Physical Downlink Control Channel
- PUCCH Physical Downlink Control Channel
- PUSCH Physical Uplink Control Channel
- PRACH Physical Downlink Control Channel
- each of the multiple transmissions scheduled on the different entities include the same content.
- each of the multiple transmissions scheduled on the different entities include content correlated to content of the other of the multiple transmissions.
- each of the multiple transmissions scheduled on the different entities include independent content from the other of the multiple transmissions.
- the DCI includes scheduling information for each of the multiple transmissions.
- the apparatus transmits the DCI to a UE.
- the scheduling information indicates a frequency domain allocation.
- the frequency domain allocation includes a number of RBs, a location of one or more RBs, or both.
- the scheduling information indicates a time domain allocation.
- the time domain allocation includes a start time, a duration, or both.
- the scheduling information includes a beam indication.
- the beam indication indicates a TCI state, a spatial relation, a beam sweep pattern, or a combination thereof.
- the beam sweep pattern includes a TDMed beam, a FDMed beam, a SDMed beam, or a combination thereof.
- the scheduling information includes a DMRS configuration.
- the DMRS configuration in combination with the fifty-ninth aspect, includes typeA/typeB, an initialization sequence, one or more antenna portions, or a combination thereof.
- the scheduling information includes a cell ID, a BWP ID, or both.
- the scheduling information includes HARQ information.
- the HARQ information includes a HARQ process ID, CBG information, redundancy version, or a combination thereof.
- the scheduling information includes UL feedback information.
- the UL feedback information includes a PUCCH resource indicator, time distance from PDSCH to PUCCH, DL assignment index, or a combination thereof.
- the scheduling information includes link adaptation information.
- the link adaptation information includes a MCS, TPC command, SRS/CSI request, or a combination thereof.
- the DCI is received via a different entity from the entities via which the multiple transmission are scheduled.
- the apparatus decodes the DCI, and identifies a repetition pattern based on the decoded DCI.
- the repetition pattern is indicated in the DCI by an index of a pre-configured candidate repetition pattern.
- the candidate repetition pattern includes a non-repetition pattern with one transmission on one entity.
- the repetition pattern indicates a channel is repeated over a set of one or more entities and a format/location of the channel per entity.
- the same DCI is repeated over a set of entities of the plurality of entities.
- the entity includes a component carrier, a cell, or a frequency allocation.
- the apparatus receives a common ACK/NACK using the multiple transmissions on the different entities of the plurality of entities.
- the apparatus performs, based on the DCI, beam sweep for a channel.
- the channel in combination with the seventy-sixth aspect, includes PDSCH, PUCCH, PUSCH, or a combination thereof.
- the same beam sweep is applied to each entity of the different entities.
- the beam sweep is scheduled per entity.
- the beam sweep includes a beam sweep pattern that includes a TDMed beam, a FDMed beam, a SDMed beam, or a combination thereof.
- the different entities include entities of different QCL groups.
- the DCI indicates carrier repetition, a beam sweep pattern, or both, per QCL group.
- the different entities include entities of frequency range and frequency range.
- the DCI indicates carrier repetition, a beam sweep pattern, or both, on entities of the first frequency range; and one or more transmissions on the second frequency range are canceled or reassigned in response to an ACK received on the second frequency range.
- the functional blocks and modules described herein may include processors, electronics devices, hardware devices, electronics components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof.
- the functional blocks and modules in FIGs. 10-11 may include processors, electronics devices, hardware devices, electronics components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof.
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional 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.
- a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
- An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
- the storage medium may be integral to the processor.
- the processor and the storage medium may reside in an ASIC.
- the ASIC may reside in a user terminal.
- the processor and the storage medium may reside as discrete components in a user terminal.
- the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
- Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Computer-readable storage media may be any available media that can be accessed by a general purpose or special purpose computer.
- such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general- purpose or special-purpose computer, or a general-purpose or special-purpose processor.
- a connection may be 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, or digital subscriber line (DSL), then the coaxial cable, fiber optic cable, twisted pair, or DSL, are included in the definition of medium.
- DSL digital subscriber line
- Disk and disc includes 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. Combinations of the above should also be included within the scope of computer-readable media.
- the term“and/or,” when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed.
- the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.
- “or” as used in a list of items prefaced by“at least one of’ indicates a disjunctive list such that, for example, a list of“at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any of these in any combination thereof.
Abstract
Description
Claims
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201962871126P | 2019-07-06 | 2019-07-06 | |
US201962872096P | 2019-07-09 | 2019-07-09 | |
US16/911,053 US20210007124A1 (en) | 2019-07-06 | 2020-06-24 | Dci based xcarrier repetition & beam sweep |
PCT/US2020/039628 WO2021007041A1 (en) | 2019-07-06 | 2020-06-25 | Dci based xcarrier repetition & beam sweep |
Publications (1)
Publication Number | Publication Date |
---|---|
EP3994833A1 true EP3994833A1 (en) | 2022-05-11 |
Family
ID=74065930
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP20743004.2A Pending EP3994833A1 (en) | 2019-07-06 | 2020-06-25 | Dci based xcarrier repetition & beam sweep |
Country Status (4)
Country | Link |
---|---|
US (1) | US20210007124A1 (en) |
EP (1) | EP3994833A1 (en) |
CN (1) | CN114080853A (en) |
WO (1) | WO2021007041A1 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11115241B2 (en) * | 2017-03-24 | 2021-09-07 | Apple Inc. | DM-RS grouping and CSI reporting for CoMP |
US20220046688A1 (en) * | 2020-08-06 | 2022-02-10 | Lg Electronics Inc. | Method and apparatus for transmitting/receiving wireless signal in wireless communication system |
JP2024512899A (en) * | 2021-03-02 | 2024-03-21 | インテル コーポレイション | Configuration of multi-configuration carrier repetitive transmission |
Family Cites Families (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101877887B (en) * | 2009-04-30 | 2012-12-05 | 中国移动通信集团公司 | Downlink transmission control method and device of cooperative multicast system |
MX2011012582A (en) * | 2009-05-26 | 2011-12-14 | Sharp Kk | Mobile communication system, base station apparatus, mobile station apparatus, and mobile communication method. |
US8804639B2 (en) * | 2010-10-04 | 2014-08-12 | Qualcomm Incorporated | Control channel resources for multi-bit ACK/NAK |
CN102833053A (en) * | 2011-06-13 | 2012-12-19 | 华为技术有限公司 | CoMP (coordinated multiple point transmission/reception) retransmitting method, device and system |
WO2013117011A1 (en) * | 2012-02-10 | 2013-08-15 | Renesas Mobile Corporation | Apparatuses and methods for signaling bundling scheduling |
WO2014204128A1 (en) * | 2013-06-19 | 2014-12-24 | 엘지전자 주식회사 | Reception method of mtc device |
CN104348580A (en) * | 2013-08-06 | 2015-02-11 | 夏普株式会社 | Downlink physical channel transmitting and receiving methods, base station and user equipment |
WO2015030523A1 (en) * | 2013-08-29 | 2015-03-05 | 엘지전자 주식회사 | Method and device for transmitting channel state information in wireless access system supporting machine type communication |
US9591649B1 (en) * | 2014-09-29 | 2017-03-07 | Sprint Spectrum L.P. | Method and system of reducing load on a downlink control channel |
WO2016175576A1 (en) * | 2015-04-29 | 2016-11-03 | 엘지전자 주식회사 | Method and device for feeding back channel state information in wireless access system supporting machine type communication |
WO2017078299A1 (en) * | 2015-11-06 | 2017-05-11 | Lg Electronics Inc. | Method for handling of drx timers for multiple repetition transmission in wireless communication system and a device therefor |
US10524244B2 (en) * | 2016-05-11 | 2019-12-31 | Convida Wireless, Llc | Radio PDCCH to facilitate numerology operations |
US10757690B2 (en) * | 2016-11-03 | 2020-08-25 | Qualcomm Incorporated | Control information piggyback in shared channel |
US10285172B2 (en) * | 2016-11-06 | 2019-05-07 | Qualcomm Incorporated | Search space design for semi-persistent scheduling (SPS) in enhanced machine-type communications |
US11140562B2 (en) * | 2017-01-11 | 2021-10-05 | Huawei Technologies Co., Ltd. | Antenna beam management for multi-connection communications |
US20200213978A1 (en) * | 2017-06-15 | 2020-07-02 | Convida Wireless, Llc | Beam based downlink control signaling |
EP3704886A4 (en) * | 2017-10-30 | 2021-06-09 | Nokia Solutions and Networks Oy | Methods and apparatuses for repetition transmission |
WO2019244218A1 (en) * | 2018-06-18 | 2019-12-26 | 株式会社Nttドコモ | User terminal |
US11095415B2 (en) * | 2018-07-02 | 2021-08-17 | Samsung Electronics Co., Ltd. | Enhancements to reception reliability for data and control information |
US10701679B2 (en) * | 2018-07-05 | 2020-06-30 | Huawei Technologies Co., Ltd. | Method and system for enhancing data channel reliability using multiple transmit receive points |
US10790892B2 (en) * | 2018-08-06 | 2020-09-29 | Qualcomm Incorporated | Rate matching of reference signal resources in multiple transmit receive point (TRP) scenarios |
JPWO2020075233A1 (en) * | 2018-10-10 | 2021-09-02 | 株式会社Nttドコモ | Terminals, wireless communication methods, base stations and systems |
WO2020143908A1 (en) * | 2019-01-09 | 2020-07-16 | Huawei Technologies Co., Ltd. | Network access node and client device for indication of multiple data channels in a single control message |
EP3944662A1 (en) * | 2019-03-22 | 2022-01-26 | Ntt Docomo, Inc. | User terminal and wireless communication method |
CN113812200B (en) * | 2019-04-30 | 2024-03-26 | 日本电气株式会社 | Downlink retransmission of multiple TRP/face transmissions |
US20210136802A1 (en) * | 2019-11-05 | 2021-05-06 | Comcast Cable Communications, Llc | Wireless communications for scheduling transmissions |
CN115039470A (en) * | 2019-11-28 | 2022-09-09 | 株式会社Ntt都科摩 | Terminal and wireless communication method |
US20230147122A1 (en) * | 2020-04-08 | 2023-05-11 | Idac Holdings, Inc. | Enhancements of physical channels in multi-trp |
US11895648B2 (en) * | 2020-10-09 | 2024-02-06 | Samsung Electronics Co., Ltd | Method and device for PDCCH repetition in multi-TRP system |
CN114828236A (en) * | 2021-01-29 | 2022-07-29 | 展讯半导体(南京)有限公司 | Cross-carrier channel repeated transmission method and device, storage medium, terminal and network equipment |
-
2020
- 2020-06-24 US US16/911,053 patent/US20210007124A1/en active Pending
- 2020-06-25 WO PCT/US2020/039628 patent/WO2021007041A1/en unknown
- 2020-06-25 CN CN202080049414.7A patent/CN114080853A/en active Pending
- 2020-06-25 EP EP20743004.2A patent/EP3994833A1/en active Pending
Also Published As
Publication number | Publication date |
---|---|
CN114080853A (en) | 2022-02-22 |
WO2021007041A1 (en) | 2021-01-14 |
US20210007124A1 (en) | 2021-01-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11356989B2 (en) | Reporting aperiodic CSI via PUCCH | |
US10772132B2 (en) | PRACH configuration on NR-U | |
US20200022029A1 (en) | Nr-ss unified operation mode in coordinated and uncoordinated bands | |
WO2019023586A1 (en) | Rach configurations for nr shared spectrum | |
AU2018401846B2 (en) | Timing considerations for AUL-DFI | |
US10218785B2 (en) | Opportunistic sync block transmission for mm wave NR-SS | |
WO2018194795A1 (en) | Precoded channel state information reference signals (csi-rs) for phase synchronization for reciprocity-based coordinated multipoint(comp) joint transmission operations | |
US20210007124A1 (en) | Dci based xcarrier repetition & beam sweep | |
WO2020205273A1 (en) | Reference signal designs for beam management in non-terrestrial networks in 5g systems | |
US20200366440A1 (en) | Long term evolution common reference signal-assisted new radio tracking | |
US20220141832A1 (en) | Cbg indication with multi-tti grant | |
US11368259B2 (en) | Xcarrier virtual single cell operation | |
US11362718B2 (en) | Sidelink TX power control | |
US20220110156A1 (en) | Category 2 (cat2) listen-before-transmit (lbt) operations for wireless communications | |
US11729825B2 (en) | Channel access enhancement for new radio-unlicensed | |
US20220104156A1 (en) | Multi-bandwidth operation for a wireless communication system | |
US11438922B2 (en) | MAC-CE duplication in packet duplication |
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: 20211220 |
|
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 |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
PUAG | Search results despatched under rule 164(2) epc together with communication from examining division |
Free format text: ORIGINAL CODE: 0009017 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20240207 |
|
B565 | Issuance of search results under rule 164(2) epc |
Effective date: 20240207 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 27/26 20060101ALN20240202BHEP Ipc: H04W 72/044 20230101ALN20240202BHEP Ipc: H04L 1/1822 20230101ALN20240202BHEP Ipc: H04L 1/00 20060101ALI20240202BHEP Ipc: H04L 1/08 20060101ALI20240202BHEP Ipc: H04B 7/06 20060101ALI20240202BHEP Ipc: H04W 72/23 20230101ALI20240202BHEP Ipc: H04L 5/00 20060101AFI20240202BHEP |