Dynamically enable and disable physical downlink shared channel scheduling using downlink control information

Abstract

Aspects of the present disclosure relate to a method of wireless communication. An exemplary method includes formatting a first downlink control information (DCI) to schedule a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells and sending the first DCI to a scheduling entity in a first physical downlink control channel (PDCCH). Another method includes: identifying a search space in a resource element grid where a control region set (CORESET) is located; decoding the CORESET to obtain a first downlink control information (DCI); determining from the first DCI a location in the resource element grid containing a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells scheduled for a scheduled entity; and decoding data located in the first plurality of PDSCHs. Other aspects and features are also claimed and described.

Description

Technical Field

[0001] The techniques discussed in this disclosure relate generally to wireless communication systems, and more particularly to dynamically enabling and disabling physical downlink shared channel (PDSCH) scheduling using downlink control information (DCI). Background Art

[0002] Given the continuously increasing demand for mobile broadband access, research and development continue to advance wireless communication technologies, not only to meet the growing demand for mobile broadband access, but also to advance and enhance the user experience of mobile communications. Summary of the invention

[0003] One or more aspects of the present disclosure are briefly summarized below to provide a basic understanding of these aspects. The present invention summary section is not an extensive overview of all contemplated aspects of the present disclosure, and is neither intended to identify important or key elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a simplified form as a prelude to a more detailed description presented later.

[0004] In one example, a wireless communication method operating at a scheduling entity is disclosed. The method includes formatting a first downlink control information (DCI) to schedule a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells and sending the first DCI to a scheduled entity in a first physical downlink control channel (PDCCH). According to one aspect, a device for wireless communication is disclosed. The device includes: a formatting component for formatting a first downlink control information (DCI) to schedule a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells; and a sending component for sending the first DCI to a scheduled entity in a first physical downlink control channel (PDCCH). According to one example, a non-transitory computer-readable medium storing computer executable code is disclosed. According to one example, the code causes the computer to format a first downlink control information (DCI) to schedule a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells and send the first DCI to a scheduled entity in a first physical downlink control channel (PDCCH). According to another aspect, an apparatus for wireless communication includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. In one example, the processor is configured to format first downlink control information (DCI) to schedule a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells and send the first DCI to a scheduled entity in a first physical downlink control channel (PDCCH).

[0005] In another example, a wireless communication method operating at a scheduled entity is disclosed. According to one aspect, the method includes: identifying a search space in a resource element grid where a control region set (CORESET) is located; decoding the CORESET to obtain a first downlink control information (DCI); determining from the first DCI the location of a resource element grid containing a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells scheduled for the scheduled entity; and decoding data located in the first plurality of PDSCHs. According to one aspect, an apparatus for wireless communication includes: an identification component for identifying a search space in a resource element grid where a control region set (CORESET) is located; a decoding component for decoding the CORESET to obtain a first downlink control information (DCI); a determination component for determining from the first DCI the location of a resource element grid containing a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells scheduled for the scheduled entity; and a decoding component for decoding data located in the first plurality of PDSCHs. In one example, a non-transitory computer-readable medium storing computer executable code is disclosed. According to one aspect, the code causes a computer to: identify a search space in a resource element grid where a control region set (CORESET) is located; decode the CORESET to obtain a first downlink control information (DCI); determine from the first DCI a location in the resource element grid containing a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells scheduled for a scheduled entity; and decode data located in the first plurality of PDSCHs. In another example, an apparatus for wireless communication is disclosed, comprising a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. In one example, the processor is configured to: identify a search space in a resource element grid where a control region set (CORESET) is located; decode the CORESET to obtain a first downlink control information (DCI); determine from the first DCI a location in the resource element grid containing a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells scheduled for a scheduled entity; and decode data located in the first plurality of PDSCHs.

[0006] After reading the detailed description below, these and other aspects of the present invention can be more fully understood. After reading the description of the following specific exemplary embodiments in conjunction with the accompanying drawings, other aspects, features and embodiments will become apparent to those of ordinary skill in the art. Although features can be discussed with respect to certain embodiments and drawings below, all embodiments may include one or more advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of these features may also be used according to the various embodiments discussed herein. In a similar manner, although exemplary embodiments may be discussed below as device, system or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 is a schematic diagram of a wireless communication system according to some aspects.

[0008] Figure 2 is a conceptual illustration of an example of a radio access network in accordance with some aspects.

[0009] Figure 3 is a block diagram illustrating a wireless communication system supporting multiple-input multiple-output (MIMO) communications.

[0010] Figure 4 is a diagram of radio resource organization in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects.

[0011] Figure 5 is a diagram of an OFDM air interface utilizing scalable numerology according to some aspects of the present disclosure.

[0012] Figure 6 is a block diagram conceptually illustrating an example of a hardware implementation of a scheduling entity employing a processing system according to some aspects of the present disclosure.

[0013] Figure 7 is a block diagram conceptually illustrating an example of a hardware implementation of a scheduled entity employing a processing system according to some aspects of the present disclosure.

[0014] Fig. 8A is a call flow diagram illustrating message exchanges between a scheduling entity and a scheduled entity and scheduling of multiple physical downlink shared channels (PDSCHs) on multiple cells (eg, carriers, component carriers) according to some aspects.

[0015] Figure 8B

[0026] One aspect of a transmission scheduling and retransmission scheme that may be implemented in a network adapted to schedule multiple PDSCHs on multiple cells using a single DCI is graphically depicted in accordance with some aspects of the present disclosure.

[0016] Figure 8C Also graphically depicted is one aspect of a transmission scheduling and retransmission scheme that may be implemented in a network adapted to schedule multiple PDSCHs on multiple cells using a single DCI in accordance with some aspects of the present disclosure.

[0017] Fig. 9 is a block diagram illustrating scheduling of a physical downlink shared channel (PDSCH) and retransmission of a PDCCH associated with a negative acknowledgement (NACK) according to some aspects of the present disclosure.

[0018] Fig.10 is a call flow diagram depicting message exchanges between a scheduling entity and a scheduled entity and a truth table for determining conditions under which a scheduled downlink channel is retransmitted in accordance with some aspects of the present disclosure.

[0019] Fig.11 is a flow chart illustrating an exemplary process for wireless communications operating at a scheduling entity in accordance with some aspects of the present disclosure.

[0020] Fig.12 is a flow chart illustrating an exemplary process operational at a scheduling entity for wireless communications in accordance with some aspects of the present disclosure. DETAILED DESCRIPTION

[0021] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it is apparent to one skilled in the art that these concepts may be practiced without these specific details. In some cases, well-known structures and components are presented in block diagram form to avoid obfuscation of these concepts.

[0022] Although aspects and embodiments are described in this application by illustrating some examples, it should be understood by those skilled in the art that additional implementation schemes and use cases may occur in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or use cases can be implemented by integrated chip embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing equipment, medical equipment, artificial intelligence-enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, various applicability of the described innovations may occur. The implementation scheme can be chip-level or modular components, to non-modular, non-chip-level implementation schemes, to aggregated, distributed, or OEM devices or systems that incorporate one or more aspects of the described innovations. In some practical settings, the devices incorporating the described aspects and features may also have to include additional components and features for the embodiments claimed and described in the implementation schemes and practices. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components, including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of various sizes, shapes, and configurations.

[0023] Various aspects described herein may relate to dynamic spectrum sharing (DSS) and the use of a single downlink control information (DCI) signal to schedule PDSCH or PUSCH on multiple cells (e.g., multiple component carriers). When multiple PDSCHs can be scheduled by the same DCI, the aspects described herein may additionally or alternatively relate to transmission scheme selection. For example, the carrier indicator field (CIF) in the DCI may be configured to correspond to a given cell or a group of cells (e.g., the CIF corresponds to {cell A}, {cell B}, {cell A and cell B}). A greater number of cells are within the scope of the present disclosure. For example, if CIF = cell A, the DCI may schedule a single PDSCH on cell A. In addition, if the new data indicator (NDI) in the DCI is not switched, the DCI may reschedule the PDSCH of the same HARQ ID previously sent on cell A. In another example, if CIF = cell B, the DCI may schedule a single PDSCH on cell B. In addition, if the NDI in the DCI is not switched, the DCI may reschedule the PDSCH of the same HARQ ID previously transmitted on cell B. In another example, if CIF=cells A and B, the DCI may schedule separate PDSCHs on cell A and cell B. In addition, if the NDI in the DCI is not switched, the DCI may reschedule the PDSCH of the same HARQ ID previously transmitted on cells A and B.

[0024] According to another aspect, search space (e.g., frequency domain and time domain spatial search) sharing can be implemented. For example, the same CORESET or search space and a set of control channel elements (CCE) can be configured with DCIs with CIF={cell A}, {cell B}, and {cell A, B}. In one aspect, each cell can indicate at most one DCI per PDCCH opportunity with CIF={cell A}, {cell B}, and {cell A, B}. As an example, using E-UTRA for exemplary and non-restrictive purposes, CCE can be a set of resources that can be used to send PDCCH. CCEs can be grouped (e.g., one, two, four, or eight CCEs) to support larger messages. Similarly, for exemplary purposes only, a CCE can be composed of nine resource element groups (REGs).

[0025] According to another aspect, if the downlink allocation index (DAI) counter (C-DAI) increases by 1 per DCI, a maximum of one DCI can be indicated by CIF = {cell A}, {cell B} and {cell A, B} per PDCCH opportunity per cell, and the number of ACK / NACK bits in the PUCCH of the cell can be based on multiple PDSCH scheduling. The value of the counter downlink allocation indicator (C-DAI) field in the DCI indicates the cumulative number of {serving cell, PDCCH monitoring opportunity}-pairs in which PDSCH reception or SPS PDSCH release exists, up to the current serving cell and the current PDCCH monitoring opportunity. When present, the value of the total DAI (T-DAI) in the DCI indicates the total number of {serving cell, PDCCH monitoring opportunity}-pairs in which PDSCH reception or SPS PDSCH release exists, up to the current PDCCH monitoring opportunity, and is updated from the PDCCH monitoring opportunity to the PDCCH monitoring opportunity. As understood by those skilled in the art, DAI is an index communicated by the gNB (or eNB, or access node) to the UE to prevent ACK / NACK reporting errors due to the HARQ ACK / NACK bundling process performed by the UE.

[0026] According to yet another aspect, ACK / NAK bundling may be applied to multiple PDSCHs scheduled by the same DCI. For example, one ACK / NAK bit may be generated for multiple PDSCHs scheduled by the same DCI, per code block group (CBG), or per transport block (TB). The following functions may be implemented:

[0027] If all PDSCHs are decoded correctly, ACK / NACK = 1,

[0028] If any PDSCH is decoded incorrectly, A / N = 0, and

[0029] If ACK / NACK=0 (i.e., if any PDSCH is erroneously decoded), the access node (e.g., gNB, eNB) reschedules all PDSCHs of the same CBG or TB through the same DCI.

[0030] definition

[0031] RAT: Radio Access Technology. A type of technology or communication standard used for radio access and communication over a wireless air interface. Several examples of RATs include GSM, UTRA, E-UTRA (LTE), Bluetooth, and Wi-Fi.

[0032] NR: New Radio. Generally refers to 5G technology and new radio access technology, which was defined and standardized by 3GPP in Release 15.

[0033] Legacy compatibility: can refer to the ability of 5G networks to provide connectivity to pre-5G devices, and the ability of 5G devices to obtain connectivity to pre-5G networks.

[0034] Multimode devices: Devices that can provide simultaneous connections across different networks, such as 5G, 4G, and Wi-Fi networks.

[0035] CA: Carrier Aggregation. 5G networks can provide aggregation of sub-6GHz carriers, above-6GHz carriers, millimeter wave carriers, etc., all controlled by a single integrated MAC layer.

[0036] MR-AN: Multi-RAT Radio Access Network. A single radio access network can provide one or more cells for each of multiple RATs and can support inter-RAT and intra-RAT mobility and aggregation.

[0037] MR-CN: Multi-RAT Core Network. A single common core network can support multiple RATs (e.g., 5G, LTE, and WLAN). In some instances, a single 5G control plane can support user planes of multiple RATs by leveraging software-defined networking (SDN) technology in the core network.

[0038] SDN: Software Defined Networking. A dynamic, adaptable network architecture that can be managed by abstracting various low-level functions of the network, making the control of network functions directly programmable.

[0039] SDR: Software Defined Radio. A dynamic, adaptable radio architecture in which many of the signal processing components of the radio, such as amplifiers, modulators, demodulators, etc., are replaced by software functions. SDR enables a single radio device to communicate using a variety of different waveforms and RATs by simply reprogramming the device.

[0040] mmWave: millimeter wave. Generally refers to high frequency bands above 24 GHz, which can provide very large bandwidth.

[0041] Beamforming: Directional signal transmission or reception. For beamformed transmission, the amplitude and phase of each antenna in an antenna array can be precoded or controlled to create a desired (e.g., directional) constructive and destructive interference pattern in the wavefront.

[0042] MIMO: Multiple Input Multiple Output. MIMO is a multi-antenna technology that exploits multipath signal propagation and can multiply the information carrying capacity of a wireless link by using multiple antennas at both the transmitter and the receiver to send multiple streams simultaneously. At the multi-antenna transmitter, an appropriate precoding algorithm (scaling the amplitude and phase of the respective streams) is applied (in some instances, based on known channel state information). At the multi-antenna receiver, the different spatial characteristics of the respective streams (and, in some instances, known channel state information) can separate the streams from each other.

[0043] 1. In single-user MIMO, the transmitter sends one or more streams to the same receiver, taking advantage of the capacity gains associated with using multiple Tx, Rx antennas in a rich scattering environment that can track channel variations.

[0044] 2. The receiver can track these channel changes and provide corresponding feedback to the transmitter. The feedback can include channel quality information (CQI), the number of preferred data streams (eg, rate control, rank indicator (RI)), and precoding matrix index (PMI).

[0045] Massive MIMO: A MIMO system with a large number of antennas (e.g., larger than an 8×8 array).

[0046] MU-MIMO: A multi-antenna technology in which a base station, when communicating with a large number of UEs, can exploit multipath signal propagation to increase overall network capacity by improving throughput and spectral efficiency and reducing the required transmit energy.

[0047] 1. The transmitter may try to increase capacity by using its multiple transmit antennas simultaneously and transmitting to multiple users using the same allocated time-frequency resources. The receiver may send feedback including a quantized version of the channel so that the transmitter can schedule receivers with good channel separation. The data being transmitted is precoded to maximize the user's throughput and minimize inter-user interference.

[0048] AS: Access Stratum. A functional grouping consisting of parts in the radio access network and the UE, and access technology-specific protocols between these parts (i.e. the specific physical medium between the UE and the radio access network used to carry information).

[0049] NAS: Non-Access Stratum. Protocols between the UE and the core network that are not terminated in the Radio Access Network.

[0050] RAB: Radio Access Bearer. The service provided by the access layer to the non-access layer is used to transfer user information between the UE and the core network.

[0051] Network slicing: A wireless communication network can be divided into multiple virtual service networks (VSNs) or network slices, which are configured separately to better meet the needs of different types of services. For example, some wireless communication networks may be separated according to eMBB, IoT and URLLC services.

[0052] eMBB: enhanced mobile broadband. Generally, eMBB refers to continued improvements to existing broadband wireless communication technologies such as LTE. eMBB provides (usually continuous) data rate increases and network capacity increases.

[0053] IoT: Internet of Things. Generally, this refers to the convergence of numerous technologies with different use cases into a single common infrastructure. Most discussions of IoT focus on machine type communication (MTC) devices.

[0054] URLLC: Ultra-Reliable and Low-Latency Communications. Sometimes equivalently referred to as Mission Critical Communications. Reliability refers to the probability of successfully sending a given number of bytes within 1ms given channel quality. Ultra-reliable refers to high target reliability, for example, packet success rate greater than 99.999%. Latency refers to the time it takes to successfully deliver an application layer packet or message. Low latency refers to low target latency, such as 1ms or even 0.5ms (for comparison, the target for eMBB may be 4ms).

[0055] MTC: Machine Type Communication. A form of data communication involving one or more entities that does not necessarily require human interaction. MTC services are optimized differently than human-to-human communications because MTC services typically involve different market scenarios, data communications, lower cost and effort, potentially very large numbers of communicating terminals, and, to a large extent, very little traffic per terminal. (See 3GPP TS 22.368.)

[0056] Duplex: A point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that both endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can send information to the other endpoint at a time. In wireless links, full-duplex channels usually rely on physical separation of the transmitter and receiver and interference cancellation techniques. Full-duplex emulation is often achieved for wireless links by utilizing frequency division duplexing (FDD) or time division duplexing (TDD). In FDD, the transmitter and receiver at each endpoint operate on different carrier frequencies. In TDD, time division multiplexing is used to separate transmissions in different directions on a given channel from each other. That is, sometimes the channel is dedicated to transmissions in one direction, and at other times the channel is dedicated to transmissions in the other direction.

[0057] OFDM: Orthogonal Frequency Division Multiplexing. The air interface can be defined in terms of a two-dimensional grid of resource elements defined by resource separation in frequency by defining a set of closely spaced frequency tones or subcarriers and by separation in time by defining sequences of symbols with a given duration. By setting the spacing between tones based on the symbol rate, inter-symbol interference can be eliminated. OFDM channels provide high data rates by distributing data streams in parallel over multiple subcarriers.

[0058] CP: Cyclic Prefix. A multipath environment can reduce the orthogonality between subcarriers because symbols received from reflected or delayed paths can overlap into the next symbol. CP solves this problem by copying the tail of each symbol and pasting it to the front of the OFDM symbol. In this way, any multipath components from the previous symbol fall within the effective guard time at the beginning of each symbol and can be discarded.

[0059] Scalable parameter: In OFDM, to maintain orthogonality of the subcarriers or tones, the subcarrier spacing is equal to the inverse of the symbol period. The scalable parameter refers to the ability of the network to select different subcarrier spacings, and therefore, for each spacing, a corresponding symbol period. The symbol period should be short enough that the channel does not change significantly within each period to maintain orthogonality and limit inter-subcarrier interference.

[0060] RSMA: Resource Spread Multiple Access. A non-orthogonal multiple access scheme typically characterized by small, grant-free data bursts in the uplink where signaling overhead is a critical issue, e.g. for IoT.

[0061] LBT: Listen Before Talk. A non-scheduled, contention-based multiple access technology in which a device monitors or senses a carrier to determine if it is available before transmitting over it. Some LBT technologies utilize signaling such as Request to Send (RTS) and Clear to Send (CTS) to reserve a channel for a given duration.

[0062] D2D: Device to Device. Also known as peer-to-peer (P2P). D2D enables discovery and communication of nearby devices using direct links between devices (i.e., not through base stations, relays, or other nodes). D2D can enable mesh networking and device-to-network relay capabilities. Some examples of D2D technologies include Bluetooth pairing, Wi-Fi Direct, Miracast, and LTE-D.

[0063] IAB: Integrated Access and Backhaul. Some base stations can be configured as IAB nodes, where the radio spectrum can be used for both the access link (i.e., the radio link with the UE) and the backhaul link. This scheme is sometimes referred to as wireless self-backhaul. By using wireless self-backhaul, rather than requiring each new base station deployment to be equipped with its own hard-wired backhaul connection, the radio spectrum used for communications between the base station and the UE can be used for backhaul communications, enabling the quick and easy deployment of high-density small cell networks.

[0064] QoS: Quality of Service. The collective effect of service performance that determines the satisfaction of service users. QoS is characterized by combined performance factors applicable to all services, such as: service operability performance; service accessibility performance; service retention performance; service integrity performance; and other factors specific to each service.

[0065] Blockchain: A distributed database and transaction processing technology with certain features that provide a secure and reliable record of transactions in a way that is very resistant to fraud or other attacks. When a transaction occurs, many copies of the transaction record are sent to other participants in the network, and each participant simultaneously confirms the transaction through mathematical calculations. Blocks are accepted through a scoring algorithm based on these confirmations. A block is a group or batch of transaction records, including a timestamp and a hash of the previous block, which links the blocks to each other. This string of blocks forms a blockchain. In wireless communication networks, especially those with a large number of IoT devices, blockchain can improve security and trust in the ability to conduct any type of transaction or instruction between devices.

[0066] The various concepts presented throughout this disclosure may be implemented across a variety of telecommunication systems, network architectures and communication standards. Figure 1 , various aspects of the present disclosure are described with reference to a wireless communication system 100 as a non-limiting illustrative example. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By virtue of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110 such as (but not limited to) the Internet.

[0067] The RAN 104 may implement any suitable wireless communication technology or technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate under a combination of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, commonly referred to as LTE. 3GPP refers to such a hybrid RAN as the Next Generation RAN, or NG-RAN. Of course, many other examples may be used within the scope of the present disclosure.

[0068] As shown, the RAN 104 includes a plurality of base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from UEs in one or more cells. In different technologies, standards, or contexts, a base station may be referred to differently by those skilled in the art as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), or some other suitable terminology.

[0069] The radio access network 104 is further illustrated as supporting wireless communications for multiple mobile devices. A mobile device may be referred to as a user equipment (UE) in the 3GPP standard, but may also be referred to as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology by those skilled in the art. A UE may be a device (e.g., a mobile device) that provides a user with access to network services.

[0070] In this document, a "mobile" device does not necessarily have the ability to move and can be stationary. The term mobile device or mobile device refers to a wide range of devices and technologies. A UE may include many hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile phones, cellular network (cellular) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide array of embedded systems, for example, corresponding to the "Internet of Things" (IoT). A mobile device may also be a car or other means of transportation, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device, such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may also be a digital home or smart home device, such as home audio, video and / or multimedia devices, appliances, vending machines, smart lighting, home security systems, smart meters, etc. The mobile device may also be a smart energy device, security device, solar panel or solar array, municipal infrastructure equipment that controls electricity (e.g., smart grid), lighting, water; industrial automation and enterprise equipment; logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships and weapons, etc. In addition, the mobile device may provide interconnected medical or telemedicine support, such as remote medical care. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, which may give priority or priority access to communications over other types of information, for example, in terms of priority access to transmit critical service data and / or related QoS for transmission of critical service data.

[0071] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a scheduling entity (further described below; e.g., base station 108). Another way to describe the scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink can refer to point-to-point transmissions originating from a scheduled entity (further described below; e.g., UE 106).

[0072] In some instances, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communications between some or all devices and equipment within its service area or cell. In the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE 106, which may be a scheduled entity, may utilize resources allocated by the scheduling entity 108.

[0073] Base station 108 is not the only entity that can function as a scheduling entity. That is, in some instances, a UE can function as a scheduling entity that schedules resources for one or more scheduled entities (eg, one or more other UEs).

[0074] like Figure 1 As shown, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities 106. Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including downlink traffic 112 and, in some instances, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, the scheduled entity 106 is a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network, such as the scheduling entity 108.

[0075] Typically, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the base stations 108 and the core network 102. Additionally, in some instances, the backhaul network may provide interconnections between the respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, etc.

[0076] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some instances, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other instances, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0077] Now refer to Figure 2 , a schematic diagram of RAN 200 is provided as an example and not as a limitation. In some instances, RAN 200 may be similar to the one described above with reference to Figure 1 The depicted and illustrated RAN 104 is the same. The geographic area covered by the RAN 200 may be divided into cellular areas (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206 and small cells 208 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antenna groups, each antenna being responsible for communicating with UEs in a portion of the cell.

[0078] Figure 2 202 and 204; and a third base station 214 is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna or may be connected to an antenna or RRH by a feeder cable. In the illustrated example, cells 202, 204, and 126 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is illustrated in a small cell 208 (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home eNode B, etc.) that may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell because base station 218 supports a cell with a relatively small size. The cell size may be determined based on system design and component constraints.

[0079] It should be understood that the radio access network 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and Figure 1 The base stations / scheduling entities 108 shown are identical.

[0080] Figure 2 Also included is a quadcopter or drone 220 that can be configured to function as a base station. That is, in some instances, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move based on the location of a mobile base station such as a quadcopter 220.

[0081] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide a core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some instances, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the above-described and Figure 1 The UE / scheduling entity 106 shown is identical.

[0082] In some examples, a mobile network node (eg, quadcopter 220 ) may be configured to function as a UE. For example, quadcopter 220 may operate within cell 202 by communicating with base station 210 .

[0083] In another aspect of RAN 200, sidelink signals can be used between UEs without having to rely on scheduling or control information from a base station. For example, two or more UEs (e.g., UE 226 and 228) can communicate with each other using peer-to-peer (P2P) or sidelink signals 227 without relaying the communication through a base station (e.g., base station 212). In another example, UE 238 is illustrated as communicating with UE 240 and 242. Here, UE 238 can be used as a scheduling entity or a primary sidelink device, and UE 240 and 242 can be used as a scheduled entity or a non-primary (e.g., secondary) sidelink device. In yet another example, a UE can be used as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P) or vehicle-to-vehicle (V2V) network and / or a mesh network. In a mesh network example, in addition to communicating with the scheduling entity 238, UE 240 and 242 can also optionally communicate directly with each other. Thus, in a wireless communication system having scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, or a mesh configuration, a scheduling entity and one or more scheduled entities may communicate using the scheduled resources.

[0084] In the radio access network 200, the ability of a UE to communicate while moving independently of its location is called mobility. The various physical channels between the UE and the radio access network are typically managed by an access and mobility management function (AMF, not shown). Figure 1 The security context management function (SCMF) is established, maintained and released under the control of the core network 102, which may include managing the security context of the control plane and user plane functions, and the security anchor function (SEAF) that performs authentication.

[0085] In various aspects of the present disclosure, the radio access network 200 can utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., transferring the UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this period, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given time, the UE can perform a handover or handover from the serving cell to the neighboring (target) cell. For example, a UE 224 (illustrated as a vehicle, although any suitable form of UE can be used) can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighboring cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 can send a report message to its serving base station 210 to indicate this situation. In response, UE 224 may receive a handover command, and the UE may undergo a handover to cell 206 .

[0086] In a network configured for UL-based mobility, the UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some instances, base stations 210, 212, and 214 / 216 can broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the unified synchronization signal, derive carrier frequency and slot timing from the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) can be received simultaneously by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each cell can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell of UE 224. As UE 224 moves through radio access network 200, the network may continue to monitor uplink pilot signals sent by UE 224. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, network 200 may handover UE 224 from the serving cell to the neighboring cell, with or without notifying UE 224.

[0087] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signals may not identify a specific cell, but may identify a region of multiple cells operating on the same frequency and / or with the same timing. The use of regions in 5G networks or other next generation communication networks enables an uplink-based mobility framework and improves the efficiency of the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network may be reduced.

[0088] In various embodiments, the air interface in the radio access network 200 may use licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although some technical rules generally still need to be followed to access the unlicensed spectrum, typically any operator or device can obtain access. Shared spectrum may be between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of the licensed spectrum may provide Licensed Shared Access (LSA) to share the spectrum with other parties, for example, with conditions for obtaining access determined by the appropriate licensee.

[0089] The air interface in the radio access network 200 may utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can send information to the other endpoint at a time. In wireless links, full-duplex channels usually rely on physical isolation of the transmitter and receiver and appropriate interference cancellation techniques. Full-duplex simulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD). In FDD, transmissions in different directions operate on different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, sometimes the channel is dedicated to transmission in one direction, and at other times the channel is dedicated to transmission in another direction, where the direction may change very quickly, for example, several times per time slot.

[0090] In some aspects of the present disclosure, the scheduling entity and / or the scheduled entity may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 3An example of a wireless communication system 300 supporting MIMO is illustrated. In a MIMO system, a transmitter 302 includes multiple transmit antennas 304 (e.g., N transmit antennas), and a receiver 306 includes multiple receive antennas 308 (e.g., M receive antennas). Therefore, there are N×M signal paths 310 based on the transmit antennas 304 to the receive antennas 308. Each of the transmitter 302 and the receiver 306 can be implemented, for example, within the scheduling entity 108, the scheduled entity 106, or any other suitable wireless communication device.

[0091] The use of this multiple antenna technology enables wireless communication systems to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to send different data streams, also known as layers, simultaneously on the same time-frequency resources. Data streams can be sent to a single UE to increase the data rate, or to multiple UEs to increase the overall system capacity, the latter of which is called multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data streams with different weights and phase shifts) and then sending each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UEs with different spatial signatures, which enables each UE to recover one or more data streams destined for that UE. On the uplink, each UE sends a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.

[0092] The number of data streams or layers corresponds to the rank of transmission. Typically, the rank of the MIMO system 300 is limited by the number of transmit or receive antennas 304 or 308, whichever is lower. In addition, other considerations such as the channel conditions of the UE and the available resources of the base station may also affect the transmission rank. For example, the rank (and therefore the number of data streams) assigned to a particular UE on the downlink can be determined based on a rank indicator (RI) sent from the UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the signal to interference and noise ratio (SINR) measured at each receive antenna. The RI can indicate, for example, the number of layers that can be supported under current channel conditions. The base station can use the RI as well as resource information (e.g., the available resources and amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0093] In a time division duplex (TDD) system, UL and DL are reciprocal because each uses different time slots of the same frequency bandwidth. Therefore, in a TDD system, the base station can assign a rank for DL ​​MIMO transmissions based on UL SINR measurements (e.g., based on a sounding reference signal (SRS) or other pilot signal sent from the UE). Based on the assigned rank, the base station can then send a CSI-RS with a separate C-RS sequence for each layer to provide multi-layer channel estimates. From the CSI-RS, the UE can measure the channel quality across layers and resource blocks and feed back CQI and RI values ​​to the base station for updating the rank and allocating REs for future downlink transmissions.

[0094] In the simplest case, Figure 3 As shown, rank 2 spatial multiplexing transmission on a 2×2 MIMO antenna configuration will send one data stream from each transmit antenna 304. Each data stream arrives at each receive antenna 308 along a different signal path 310. The receiver 306 can then reconstruct the data stream using the received signal from each receive antenna 308.

[0095] In order to transmit over the radio access network 200 to obtain a low block error rate (BLER) while still achieving very high data rates, channel coding can be used. That is, wireless communications can typically utilize suitable error-correcting block codes. In a typical block code, an information message or sequence is divided into code blocks (CBs), and then an encoder (e.g., CODEC) at the transmitting device mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message can improve the reliability of the message, thereby being able to correct any bit errors that may occur due to noise.

[0096] In early 5G NR specifications, user data is encoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one for large code blocks and / or high code rates, and another for use in other ways. Control information and the physical broadcast channel (PBCH) are encoded using polarization (Polar) coding based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0097] However, it will be appreciated by those skilled in the art that aspects of the present disclosure may be implemented using any suitable channel code. Multiple implementations of the scheduling entity 108 and the scheduled entity 106 may include appropriate hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communications.

[0098] The air interface in the radio access network 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of multiple devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexes DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and can be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. In addition, multiplexed DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0099] Various aspects of the present disclosure will be described with reference to OFDM waveforms. Figure 4 Schematically shown in FIG. A person of ordinary skill in the art will appreciate that various aspects of the present disclosure may be applied to DFT-s-OFDMA waveforms in substantially the same manner as described below. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles may also be applied to DFT-s-OFDMA waveforms.

[0100] In this disclosure, a frame refers to a duration of 10 ms for wireless transmission, each frame consisting of 10 1 ms subframes. On a given carrier, there may be one set of frames in the UL and another set of frames in the DL. Figure 4 , shows an expanded view of an exemplary DL subframe 402, and further shows an OFDM resource grid 404. However, as those skilled in the art will readily appreciate, the PHY transmission structure of any particular application may differ from the example described herein, depending on any number of factors. Here, time is in the horizontal direction, in units of OFDM symbols; frequency is in the vertical direction, in units of subcarriers or tones.

[0101] Resource grid 404 can be used to schematically represent the time-frequency resources of a given antenna port. That is, in a MIMO implementation with multiple available antenna ports, corresponding multiple resource grids 404 can be used for communication. Resource grid 404 is divided into multiple resource elements (RE) 406. RE is 1 subcarrier × 1 symbol, is the smallest discrete part of the time-frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a specific implementation, each RE can represent one or more information bits. In some instances, RE blocks can be referred to as physical resource blocks (PRBs) or more simply as resource blocks (RBs) 408, which include any suitable number of consecutive subcarriers in the frequency domain. In one instance, an RB can include 12 subcarriers, which number of carriers is independent of the parameters used. In some instances, depending on the parameters, an RB can include any suitable number of consecutive OFDM symbols in the time domain. In the present disclosure, it is assumed that a single RB such as RB 408 corresponds entirely to a single communication direction (transmission or reception of a given device).

[0102] A UE typically uses only a subset of the resource grid 404. An RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs scheduled for a UE, the higher the modulation scheme selected for the air interface, and the higher the data rate for the UE.

[0103] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers shown above and below RB 408. In a given embodiment, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Furthermore, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, although this is merely one possible example.

[0104] Each subframe 402 (eg, a 1 ms subframe) may be composed of one or more adjacent time slots. Figure 4 In the example shown, as an illustrative example, a subframe 402 includes four time slots 410. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Other examples can include mini-slots with shorter durations (e.g., 1, 2, 4, or 7 OFDM symbols). In some cases, these mini-slots may be transmitted occupying resources scheduled for ongoing time slot transmissions of the same or different UEs.

[0105] The enlarged view of one of the time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. In general, the control region 412 may carry a control channel (e.g., PDCCH), and the data region 414 may carry a data channel (e.g., PDSCH or PUSCH). Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 4 The simple structure shown is merely exemplary in nature, and different slot structures may be used and may include one or more of each of the control region and the data region.

[0106] Despite Figure 4 Not shown in the figure, various REs 406 within RB 408 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 406 within RB 408 can also carry pilot or reference signals. These pilot or reference signals can be provided to a receiving device to perform channel estimation of the corresponding channel, which can achieve coherent demodulation / detection of the control and / or data channels within RB 408.

[0107] In a DL transmission, a transmitting device (e.g., a scheduling entity 108) may allocate one or more REs 406 (e.g., within a control region 412) to carry DL control information 114, including one or more DL control channels, which typically carry information to be sent from higher layers such as a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc. to one or more scheduled entities 106. In addition, DL REs may be allocated to carry DL physical signals that typically do not carry information originating from higher layers. These DL physical signals may include: a primary synchronization signal (PSS); a secondary synchronization signal (SSS); a demodulation reference signal (DM-RS); a phase tracking reference signal (PT-RS); a channel state information reference signal (CSI-RS); etc.

[0108] The synchronization signals PSS and SSS (collectively referred to as SS), and in some instances the PBCH, may be sent in an SS block comprising 4 consecutive OFDM symbols, which are numbered in increasing order from 0 to 3 by time index. In the frequency domain, the SS block may extend over 240 consecutive subcarriers, which are numbered in increasing order from 0 to 239 by frequency index. Of course, the present disclosure is not limited to this particular SS block configuration. Other non-limiting examples may use more or less than two synchronization signals; may include one or more supplemental channels in addition to the PBCH; may omit the PBCH; and / or may use non-contiguous symbols for the SS block within the scope of the present disclosure.

[0109] The PDCCH may carry downlink control information (DCI) for one or more UEs in a cell. This may include, but is not limited to, power control commands, scheduling information, grants, and / or allocation of REs for DL ​​and UL transmissions.

[0110] In an UL transmission, a transmitting device (e.g., a scheduled entity 106) may utilize one or more REs 406 to carry UL control information 118 (UCI). The UCI may originate from higher layers to the scheduling entity 108 via one or more UL control channels, such as a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc. In addition, the UL REs may carry UL physical signals that typically do not carry information originating from higher layers, such as a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), a sounding reference signal (SRS), etc. In some instances, the control information 118 may include a scheduling request (SR), i.e., a request to the scheduling entity 108 to schedule an uplink transmission. Here, in response to the SR sent on the control channel 118, the scheduling entity 108 may send downlink control information 114 that may schedule resources for uplink packet transmission.

[0111] The UL control information may also include hybrid automatic repeat request (HARQ) feedback, such as an acknowledgement (ACK) or negative acknowledgement (NACK), channel state information (CSI), or any other suitable UL control information. HARQ is a technique well known to those of ordinary skill in the art, where the integrity of packet transmissions may be checked on the receiving side to ensure accuracy, for example, using any suitable integrity check mechanism, such as a checksum or cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if not, a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may enable chase combining, incremental redundancy, and the like.

[0112] In addition to control information, one or more REs 406 (e.g., within the data region 414) may be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as a physical downlink shared channel (PDSCH) for DL ​​transmissions or a physical uplink shared channel (PUSCH) for UL transmissions.

[0113] In order for the UE to obtain initial access to a cell, the RAN may provide system information (SI) that characterizes the cell. The system information may be provided using minimum system information (MSI) and other system information (OSI). MSI may be broadcast periodically on the cell to provide the most basic information required for initial cell access, as well as to obtain any OSI that may be broadcast periodically or sent on demand. In some instances, MSI may be provided over two different downlink channels. For example, the PBCH may carry a master information block (MIB) and the PDSCH may carry a system information block type 1 (SIB1). In the art, SIB1 may be referred to as remaining minimum system information (RMSI).

[0114] The OSI may include any SI not broadcast in the MSI. In some instances, the PDSCH may carry multiple SIBs, not limited to SIB1 discussed above. Here, the OSI may be provided in these SIBs, such as SIB2 and above.

[0115] The above description and Figure 1 and 4 The channels or carriers illustrated in are not necessarily all channels or carriers that may be used between the scheduling entity 108 and the scheduled entity 106, and a person of ordinary skill in the art will recognize that other channels or carriers may be used in addition to the channels or carriers shown, such as other traffic, control, and feedback channels.

[0116] These physical channels are typically multiplexed and mapped to transport channels for processing at the media access control (MAC) layer. Transport channels carry blocks of information called transport blocks (TBs). The transport block size (TBS), which can correspond to a number of bits of information, can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0117] In OFDM, in order to maintain the orthogonality of the subcarriers or tones, the subcarrier spacing can be equal to the inverse of the symbol period. The parameters of the OFDM waveform refer to its specific subcarrier spacing and cyclic prefix (CP) overhead. Scalable parameters refer to the ability of the network to select different subcarrier spacings, and therefore, for each spacing, a corresponding symbol duration, including the CP length. Using scalable parameters, the nominal subcarrier spacing (SCS) can be scaled up or down by integer multiples. In this way, regardless of the CP overhead and the selected SCS, the symbol boundaries can be aligned at certain common multiples of the symbol (for example, at the boundaries of each 1ms subframe). The range of SCSs can include any suitable SCS. For example, scalable parameters can support SCSs from 15kHz to 480kHz.

[0118] To illustrate the concept of extensible parameters, Figure 55 shows a first RB 502 with nominal parameters and a second RB 504 with scaled parameters. As an example, the first RB 502 may have a “nominal” subcarrier spacing (SCS) of 30 kHz. n ) and a "nominal" symbol duration of 333 μs n Here, in the second RB 504, the extended parameters include an extended SCS that is twice the nominal SCS, or 2×SCS n =60kHz. Since this provides twice the bandwidth for each symbol, the symbol duration can be shortened to carry the same information. Therefore, in the second RB 504, the extension parameters include an extended symbol duration of half the nominal symbol duration, or (symbol duration n )÷2=167μs.

[0119] Scheduling Entity

[0120] Figure 6 is a block diagram conceptually illustrating an example of a hardware implementation of a scheduling entity 600 using a processing system 614 according to some aspects of the present disclosure. For example, the scheduling entity 600 may be Figure 1 , Figure 2 and / or Figure 3 In another example, the scheduling entity 600 may be any one or more of the user equipments (UEs) shown in FIG. Figure 1 , Figure 2 and / or Figure 3 Any one or more of the base stations shown in .

[0121] The scheduling entity 600 may be implemented using a processing system 614 including one or more processors 604. Examples of processor 604 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described in the present disclosure. In various examples, the scheduling entity 600 may be configured to perform any one or more of the functions described herein. That is, the processor 604 used in the scheduling entity 600 may be used to implement the various functions described below and in FIG. 8 through FIG. Fig.12 Any one or more of the processes and procedures shown.

[0122] In this example, the processing system 614 can be implemented with a bus architecture generally represented by bus 602. Depending on the specific application and overall design constraints of the processing system 614, the bus 602 may include any number of interconnecting buses and bridges. The bus 602 communicatively couples various circuits including one or more processors (generally represented by processor 604), memory 605, and computer-readable media (generally represented by computer-readable media 606). The bus 602 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further. The bus interface 608 provides an interface between the bus 602 and the transceiver 610. The transceiver 610 provides a communication interface or component for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 612 (e.g., a keypad, a display, a speaker, a microphone, a joystick) may also be provided. Of course, such a user interface 612 is optional and may be omitted in some examples such as a base station.

[0123] In some aspects of the present disclosure, the processor 604 may include a DCI formatting circuit 640 configured for various functions, including, for example, formatting a first DCI to schedule a first plurality of PDSCHs in a first plurality of cells. The processor 604 may also include, for example, a DCI transmission circuit 642 configured for various functions, including, for example, transmitting a first DCI to a scheduled entity in a first PDCCH. The processor 604 may also include, for example, a CORESET / search space circuit 644 configured for various functions, including, for example, configuring a set of CCEs as DCIs with CIF field indications for each cell (e.g., component carrier, {cell A}, {cell B}, {cell A, B}, etc.). The processor 604 may also include, for example, a C-DAI circuit 646 configured for various functions, including, for example, setting and incrementing a C-DAI counter, where, for example, if the C-DAI is increased by 1 per DCI, then each cell may indicate at most one DCI per PDCCH opportunity with CIF={cell A}, {cell B}, and {cell A, B}. The processor 604 may also include, for example, an ACK / NACK bundling circuit 648 configured for various functions, including, for example, applying ACK / NACK bundling to multiple PDSCHs scheduled by the same DCI. For example, the DCI formatting circuit 640, the CIF field circuit 642, the CORESET / search space circuit 644, the C-DAI circuit 646, the ACK / NACK bundling circuit 648 may be configured to implement the following with respect to FIG. 8 to Fig.12 One or more of the functions described, including for example Fig.11 .

[0124] The processor 604 is responsible for managing the bus 602 and general processing, including the execution of software stored on the computer-readable medium 606. This software, when executed by the processor 604, causes the processing system 614 to perform the various functions described below for any particular device. The computer-readable medium 606 and memory 605 may also be used to store data that is manipulated by the processor 604 when executing the software.

[0125] One or more processors 604 in the processing system can execute software. Software should be broadly interpreted as representing instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc., whether referring to software, firmware, middleware, microcode, hardware description language or other means. The software can reside on a computer-readable medium 606. The computer-readable medium 606 can be a non-transient computer-readable medium. The non-transient computer-readable medium includes, for example, a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic strip), an optical disk (e.g., a compact disk (CD) or a digital versatile disk (DVD)), a smart card, a flash memory device (e.g., a card, a stick or a key drive), a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 606 may reside in processing system 614, external to processing system 614, or distributed among multiple entities including processing system 614. Computer readable medium 606 may be embedded in a computer program product. For example, a computer program product may include a computer readable medium in packaging materials. Those skilled in the art will recognize how to best implement the functionality described throughout this disclosure depending on the specific application and the overall design constraints imposed on the entire system.

[0126] In one or more instances, the computer-readable storage medium 606 may include, for example, DCI formatting instructions 652 (e.g., software) configured for various functions, including, for example, formatting a first DCI to schedule a first plurality of PDSCHs in a first plurality of cells. The computer-readable storage medium 606 may also include, for example, DCI sending instructions 654 (e.g., software), which are configured for various functions, including, for example, sending a first DCI to a scheduled entity in a first PDCCH. The computer-readable storage medium 606 may also include, for example, CORESET or search space instructions 656 (e.g., software) configured for various functions, including, for example, configuring a set of CCEs as DCIs with CIF field indications for each cell. The computer-readable storage medium 606 may also include, for example, C-DAI instructions 658 (e.g., software) configured for various functions, including, for example, setting and incrementing a C-DAI counter. The computer-readable storage medium 606 may also include, for example, ACK / NACK bundling instructions 660 (e.g., software) configured for various functions, including, for example, applying ACK / NACK bundling to multiple PDSCHs scheduled by the same DCI. The same and / or additional instructions (eg, software) may be configured to implement the following including, for example Fig.11 The block 1102 of FIG. 8 to Fig.12 One or more of the described functions.

[0127] Scheduled Entity

[0128] Figure 7 704 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity 700 using a processing system 714. According to aspects of the present disclosure, a processing system 714 including one or more processors 704 may be utilized to implement an element or any combination of elements, portions of elements, or elements. For example, the scheduled entity 700 may be Figure 1 , Figure 2 and / or Figure 3 Any one or more of the user equipments (UEs) shown in .

[0129] The processing system 714 can be used with Figure 6 The processing system 614 shown is substantially the same, including a bus interface 708, a bus 702, a memory 705, a processor 704, and a computer readable medium 706. In addition, the scheduling entity 700 may include the same Figure 6 That is, the processor 704 used in the scheduling entity 700 can be used to implement any one or more of the processes described below and shown in the accompanying figures.

[0130] In some aspects of the present disclosure, the processor 704 may include, for example, a CORESET / search space circuit 740 configured for various functions, including, for example, identifying a search space in a resource element grid within which a control region set (CORESET) is located, and / or configuring a set of CCEs as a DCI with a CIF field indication for each cell (e.g., component carrier, {cell A}, {cell B}, {cell A, B}, etc.). The processor 704 may also include, for example, a CORESET decoding circuit 742 configured for various functions, including, for example, decoding the CORESET to obtain a first DCI. The processor 704 may also include, for example, a PDSCH position determination circuit 744 configured for various functions, including, for example, determining from the first DCI a position in a resource element grid containing a first plurality of PDSCHs in a first plurality of cells scheduled for a scheduled entity. The processor 704 may also include, for example, a data decoding circuit 746 configured for various functions, including, for example, decoding data located in the first plurality of PDSCHs. The processor 704 may further include, for example, a C-DAI circuit 748 configured for various functions, including, for example, setting and incrementing a C-DAI counter, where, for example, if the C-DAI increases by 1 per DCI, then each cell per PDCCH opportunity may indicate a maximum of one DCI with CIF={cell A}, {cell B}, and {cell A, B}. The processor 704 may also include, for example, an ACK / NACK bundling circuit 750 configured for various functions, including, for example, applying ACK / NACK bundling to multiple PDSCHs scheduled by the same DCI. For example, the CORESET and / or search space circuit 740, the CORESET decoding circuit 742, the PDSCH position determination circuit 744, the data decoding circuit 746, the C-DAI circuit 748, the ACK / NACK bundling circuit 750 may be configured to implement, for example Fig.12 One or more of block 1202 below in conjunction with FIG. 8 to Fig.12 The functions described.

[0131] In one or more instances, the computer-readable storage medium 706 may include CORESET and / or search space instructions 752 (e.g., software) configured for various functions, including, for example, identifying a search space in a resource element grid within which a control region set (CORESET) is located, and / or configuring a set of CCEs as DCIs with CIF field indications for each cell (e.g., component carrier, {cell A}, {cell B}, {cell A, B}, etc.). The computer-readable storage medium 706 may also include, for example, CORESET decoding instructions 754 (e.g., software) configured for various functions, including, for example, decoding the CORESET to obtain a first DCI. The computer-readable storage medium 706 may also include, for example, PDSCH position determination instructions 756 (e.g., software) configured for various functions, including, for example, determining from the first DCI a position in a resource element grid containing a first plurality of PDSCHs in a first plurality of cells scheduled for a scheduled entity. The computer-readable storage medium 706 may also include, for example, data decoding instructions (e.g., software) 758 configured for various functions, including, for example, decoding data located in the first plurality of PDSCHs. The computer-readable storage medium 706 may also include, for example, C-DAI instructions 760 (e.g., software) configured for various functions, including, for example, setting and incrementing a C-DAI counter. The computer-readable storage medium 706 may also include, for example, ACK / NACK bundling instructions 762 (e.g., software) configured for various functions, including, for example, applying ACK / NACK bundling to multiple PDSCHs scheduled by the same DCI. The same and / or additional instructions (e.g., software) may be configured to implement, for example, Fig.12 The block 1202 of FIG. 8 to Fig.12 One or more of the described functions.

[0132] Fig. 8A is a call flow diagram illustrating message exchanges between a scheduling entity 802 and a scheduled entity 804 and scheduling of multiple physical downlink shared channels (PDSCHs) on multiple cells (eg, carriers, component carriers) according to some aspects of the present disclosure. Fig. 8A One aspect of a transmission scheduling and retransmission scheme that may be implemented in a network adapted to schedule multiple PDSCHs on multiple cells using a single DCI is graphically depicted in accordance with some aspects of the present disclosure.A first frequency versus time graph 800 is presented, with frequency represented on the vertical axis and time represented on the horizontal axis.

[0133] The scheduling entity 802 may send a first message 806 (message 1) to the scheduled entity 804. The first message 806 may be in the form of downlink control information (DCI); i.e., a single DCI. The first message may be sent on a physical downlink control channel (PDCCH). The first message 806 may include, for example, a carrier information field (CIF) value, a HARQ process identifier value, and a new data indicator (NDI) value. The CIF value may be configured to identify a cell set (e.g., {cell 1} (a set of one cell), {cell 2} (a set of another cell), {cell 1&2} (a set of two cells)). Other groups of two or more cells are within the scope of the present disclosure.

[0134] exist Fig. 8A In the example of , the CIF value is "1&2", which indicates a command given in a first message 806 (e.g., a single DCI) to schedule multiple PDSCHs (e.g., PDSCH_1 808 and PDSCH_2 810) on multiple cells (e.g., cell 1 and cell 2). The scheduling of multiple PDSCHs according to the first message (e.g., a single DCI) is represented by the dashed arrows that originate from the first message (or from the PDCCH that transmits the first message 806) and terminate at PDSCH_1 808 and PDSCH_2 810.

[0135] After receiving the first message 806 and scheduling multiple PDSCHs (PDSCH_1 808 and PDSCH_2 810) on multiple cells (cell 1 and cell 2), the scheduling entity 802 can send a second message 812 (message 2) to the scheduled entity 804. The second message 812 can also be in the form of downlink control information (DCI); that is, a second single DCI. As described above, the first message 806 can be sent on a physical downlink control channel (PDCCH). The second message 812 can also include, for example, a carrier information field (CIF) value, a HARQ process identifier value, and a new data indicator (NDI) value.

[0136] exist Fig. 8A In the example of , the CIF value is changed to "1" and indicates that the command given in the second message 812 (e.g., the second single DCI) is to schedule a PDSCH (e.g., PDSCH_3 814) on a cell (e.g., cell 1). The scheduling of a PDSCH (PDSCH_3 814) by the second message (e.g., the second single DCI) is represented by a dotted arrow that is sent from the second message 812 (or from the PDCCH that transmits the second message 812) and ends at PDSCH_3 814.

[0137] Therefore, the first part of the transmission scheme can be expressed as follows: if the CIF value represents any given set of cells (e.g., {cell 1}, {cell 2}, {cell 1&2}), then the message carrying the CIF (or some other field that can be configured to identify the cell set) indicates that the message reflects the scheduling of the cell set on the corresponding number of PDSCHs. In addition, if the NDI in the second message (e.g., the second single DCI) is not switched relative to the first message (e.g., relative to the first single DCI), the second message 812 (DCI) indicates that the PDSCH of the same HARQ ID previously transmitted on the given cell will be retransmitted.

[0138] Can be compared to Figure 8B Repetition relative to Fig. 8A Accordingly, go to Figure 8B , Figure 8B Also graphically depicted is one aspect of a transmission scheduling and retransmission scheme that may be implemented in a network adapted to schedule multiple PDSCHs on multiple cells using a single DCI in accordance with some aspects of the present disclosure. Figure 8B , a graph 820 of the second frequency versus time is presented.

[0139] The scheduling entity 802 may send a first message 826 (message 1) to the scheduled entity 804. The first message 826 may be in the form of downlink control information (DCI); i.e., a single DCI. The first message 826 may be sent on a physical downlink control channel (PDCCH). The first message 826 may include, for example, a carrier information field (CIF) value, a HARQ ID value, and a new data indicator (NDI) value. As described above, the CIF value may be configured to identify a cell set.

[0140] exist Figure 8B In the example of , the CIF value is "1&2", which indicates a command given in a first message 826 (e.g., a single DCI) for scheduling multiple PDSCHs (e.g., PDSCH_1 828 and PDSCH_2 830) on multiple cells (e.g., cell 1 and cell 2). The scheduling of multiple PDSCHs according to the first message 826 is represented by the dashed arrows that originate from the first message 826 (or from the PDCCH that transmits the first message 826) and terminate at PDSCH_1 828 and PDSCH_2 830.

[0141] After receiving the first message 826 and scheduling multiple PDSCHs (PDSCH_1 828 and PDSCH_2 830) on multiple cells (cell 1 and cell 2), the scheduling entity 802 may send a second message 832 (message 2) to the scheduled entity 804. The second message 832 may also include, for example, a carrier information field (CIF) value, a HARQ ID value, and a new data indicator (NDI) value.

[0142] exist Figure 8B In the example of , the CIF value is changed to "2" and indicates that the command given in the second message 832 is to schedule a PDCCH (e.g., PDSCH_3 834) on a cell (e.g., cell 2). The scheduling of a PDSCH (PDSCH_3 834) by the second message 812 is represented by a dotted arrow that is sent from the second message 832 (or from the PDCCH that transmits the second message 832) and ends at PDSCH_3 834.

[0143] Therefore, the first part of the transmission scheme can be restated again, noting that if the CIF value represents any given set of cells (e.g., {cell 1}, {cell 2}, {cell 1&2}), then the message carrying the CIF (or some other field that can be configured to identify the cell set) indicates that the message reflects the scheduling of the cell set on the corresponding number of PDSCHs. In addition, if the NDI in the second message 832 is not switched relative to the first message 826, the second message indicates that the PDSCH of the same HARQ ID previously transmitted on the given cell will be retransmitted.

[0144] You can refer to it again Figure 8C Repeat relative to Fig. 8A and 8B Accordingly, go to Figure 8C , Figure 8C Also graphically depicted is one aspect of a transmission scheduling and retransmission scheme that may be implemented in a network adapted to schedule multiple PDSCHs on multiple cells using a single DCI in accordance with some aspects of the present disclosure. Figure 8C , a graph 840 of a third frequency versus time is presented.

[0145] The scheduling entity 802 may send a first message 846 (message 1) to the scheduled entity 804. The first message 846 may be in the form of downlink control information (DCI); i.e., a single DCI. The first message 846 may be sent on a physical downlink control channel (PDCCH). The first message 846 may include, for example, a carrier information field (CIF) value, a HARQ ID value, and a new data indicator (NDI) value. As described above, the CIF value may be configured to identify a cell set.

[0146] exist Figure 8C In the example of , the CIF value is "1&2", which indicates a command given in a first message 826 (e.g., a single DCI) to schedule multiple PDSCHs (e.g., PDSCH_1 828 and PDSCH_2 830) on multiple cells (e.g., cell 1 and cell 2). The scheduling of multiple PDSCHs according to the first message 846 is represented by the dashed arrows that originate from the first message 846 (or from the PDCCH that transmits the first message 846) and terminate at PDSCH_1 848 and PDSCH_2 850.

[0147] After receiving the first message 846 and scheduling multiple PDSCHs (PDSCH_1 848 and PDSCH_2 850) on multiple cells (cell 1 and cell 2), the scheduling entity 802 may send a second message 852 (message 2) to the scheduled entity 804. The second message 852 may also include, for example, a carrier information field (CIF) value, a HARQ ID value, and a new data indicator (NDI) value.

[0148] exist Figure 8C In the example of , the CIF value remains at "1&2" and indicates that the command given in the second message 852 is to schedule two PDCCHs (e.g., PDSCH_3 854 and PDSCH_4 856) on two cells (e.g., cell 1 and cell 2). The scheduling of the two PDSCHs (PDSCH_3 854 and PDSCH_4 856) by the second message 852 is represented by the dotted arrows that are sent from the second message 852 (or from the PDCCH that sends the second message 852) and terminate at PDSCH_3 854 and PDSCH_4 856.

[0149] Therefore, the first part of the transmission scheme can be restated again, noting that if the CIF value represents any given set of cells (e.g., {cell 1}, {cell 2}, {cell 1&2}), then the message carrying the CIF (or some other field that can be configured to identify the cell set) indicates that the message reflects the scheduling of the cell set on the corresponding number of PDSCHs. In addition, if the NDI in the second message 832 is not switched relative to the first message 846, the second message 852 indicates that the PDSCH of the same HARQ ID previously transmitted on the given cell will be retransmitted.

[0150] Fig. 9 is a block diagram illustrating scheduling of a physical downlink shared channel (PDSCH) and retransmission of a PDCCH associated with a negative acknowledgement (NACK) according to some aspects of the present disclosure. Fig. 9A graph 900 of frequency versus time is presented in FIG. The vertical axis represents frequency and the horizontal axis represents time. A control resource set (CORESET) may be associated with a first search space 906. The first search space 906 may be positioned in association with a first PDCCH_1 904. A CORESET / search space is a set of physical resources and a set of parameters for PDCCH / DCI monitoring. The search space may include a set of CCEs that may be configured to monitor a PDCCH / DCI having a CIF applicable to an indication of a set of cells ({cell y}, {cell x}, {cell x&y}). According to Fig. 9 As shown in the illustration, a first search space 906 (defined in frequency and time) can be associated with a first PDCCH_1 904. The first PDCCH 904 can be located in a PDCCH monitoring opportunity within a first time interval (e.g., a time slot or a mini-slot) depicted from time = t0 that is predetermined by the search space 906 and the associated CORESET. A DCI with a CIF field can be detected from a CORESET in the first search space 906. As previously described, a single DCI can be used to schedule multiple PDSCHs (e.g., PDSCH_1 908 and PDSCH_2 910), as shown by the dashed arrows that are sent from the first PDCCH_1 904 and terminate at PDSCH_1 908 and PDSCH_2 910. Multiple PDSCHs in the second time interval t1-t2 can be scheduled by the DCI in the first PDCCH_1 904 in the first time interval t0-t1.

[0151] A new search space 914 may be established in the third time interval t2-t3. The CORESET of PDCCH_2 912 and the search space 914 may include a second PDCCH monitoring opportunity for a second single DCI. Fig. 8A , Figure 8B and Figure 8C The second single DCI may be used to schedule multiple PDSCHs in a fourth time interval t4-t3 according to the CIF value, HARQ ID and NDI described in . Fig. 9 In the illustration of , one PDSCH 916 is scheduled for the fourth time interval t4-t3 using the DCI and CIF, HARQ IQ, and NDI fields of PDSCCH_2 912. Similarly, one PDSCH 916 scheduled for the fourth time interval t4-t3 is a retransmission of PDSCH_1 908 from the second time interval t2-t1 using the CIF, HARQ IQ, and NDI fields associated with the second single DCI.

[0152] Yet another new search space 920 may be established in the fifth time interval t5-t4. The CORESET of PDCCH_3 918 and the search space 920 may include a third PDCCH monitoring opportunity for a third single DCI. Fig. 8A , Figure 8B and Figure 8C The third single DCI may be used to schedule multiple PDSCHs in the sixth time interval t6-t5 according to the CIF value, HARQ ID and NDI described in . Fig. 9 In the illustration of , one PDSCH 922 is scheduled for the sixth time interval t6-t5 using the DCI of PDSCH_3 918 and the CIF, HARQ IQ and NDI fields. Similarly, one PDSCH 922 scheduled for the sixth time interval t6-t5 is a retransmission of PDSCH_2 910 from the second time interval t2-t1 using the CIF, HARQ IQ and NDI fields associated with the third single DCI. The search spaces 906, 914, 920 may have the same search space ID and may also be associated with the same CORESET ID. PDCCH_1 904, PDCCH_2 912, PDCCH_3 918 may be detected on the same set of CCEs on the search space. As another example, the scheduled entity 1004 may configure the same PDCCH candidate with the same CCE aggregation level in the same CORESET of the same DCI format for the same payload associated with cell 1, cell 2, and cells 1 and 2, and may receive the corresponding PDCCH through the PDCCH candidate scheduled for cell 1, cell 2, or cells 1 and 2. It should be noted that at most one DCI may be indicated per PDCCH opportunity per cell with CIF={cell A}, {cell B}, and {cell A, B}.

[0153] Fig.10 is a call flow diagram depicting message exchanges between a scheduling entity 1002 and a scheduled entity 1004 and a truth table for determining conditions under which a scheduled downlink channel (PDSCH) is retransmitted in accordance with some aspects of the present disclosure. A frequency versus time graph 1000 is presented in Fig.10 Frequency is plotted on the vertical axis and time is plotted on the horizontal axis.

[0154] The scheduling entity 1002 may send a first message 1006 (message 1) to the scheduled entity 1004. The first message 1006 may be in the form of downlink control information (DCI); i.e., a single DCI. The first message may be sent on a physical downlink control channel (PDCCH). The first message 1006 may include, for example, a field indicating the total size of the HARQ-ACK payload (i.e., a total downlink allocation indicator or T-DAI, a counter-DAI (C-DAI), a HARQ process identifier value or a HARQ index value, and a new data indicator (NDI) value. If the C-DAI increases by 1 with each DCI, and a maximum of one DCI can be represented per cell per PDCCH opportunity using CIF = {cell 1}, {cell 2}, {cell 1, 2}, then the number of ACK / NACK bits in the PUCCH for a given cell should be based on the PDCCH monitoring opportunity The maximum number of multiple PDSCHs that may be scheduled on a cell. That is, for example, a single DCI is used to schedule multiple PDSCHs on multiple cells. For example, for CIF = {cell 1}, {cell 2} and {cell 1, 2} for each PDCCH opportunity in each cell, the maximum number of PDSCHs that may be scheduled is 2, and there may be two ACK / NACK bits in the PUCCH for the PDCCH monitoring opportunities on the cell. Therefore, the scheduling entity 1004 finds that there is a DCI loss on the cell based on the DAI mechanism, and sets two NACK bits at the corresponding position of the PUCCH to indicate the lost DCI.

[0155] exist Fig.10 In the example shown, in message 1 1006 (e.g., a first single DCI), the content of the message indicates C-DAI=0, T-DAI=2, HARQ=x, and NDI=0. The message notifies the scheduled entity that PDSCH_1 1010 is scheduled for cell 1 and PDSCH_2 1012 is scheduled for cell 2. In message 2 1008 (e.g., a second single DCI), the content of the message indicates C-DAI=1, T-DAI=2, HARQ=y, and NDI=0. The configuration notifies the scheduled entity that PDSCH_3 1014 is scheduled for cell 3 and PDSCH_4 1016 is scheduled for cell 4.

[0156] Referring to the PUCCH 1018 and table 1026, one ACK / NACK bit may be included in the PUCCH 1018 for message 1 1006. If the ACK / NAK of both PDSCH_1 1010 and PDSCH_2 1012 is ACK, the ACK / NACK bit = 1. If the ACK / NAK of one of PDSCH_1 1010 and PDSCH_2 1012 is NACK, the ACK / NACK bit = 0. Similarly, referring to the PUCCH 1018 and table 1028, one ACK / NACK bit may be included in the PUCCH 1018 for message 2 1008. If the ACK / NAK of both PDSCH_3 1014 and PDSCH_4 1016 is ACK, the ACK / NACK bit = 1. If the ACK / NAK of one of PDSCH_3 1014 and PDSCH_4 1016 is NACK, then the ACK / NACK bit=0.

[0157] Returning to the frequency versus time graph 1000, the scheduling of multiple PDSCHs (PDSCH_1 101 and PDCH_2 1012) according to the first message 1006 (e.g., a single DCI) is represented by the dashed arrows emanating from the first message 1006 (or from the PDCCH transmitting the first message 1006) and terminating at PDSCH_1 1008 and PDSCH_2 1010. In this example, for ACK / NACK_1, the ACK / NACK bit in PUCCH 1018 will be set to 1. However, for ACK / NACK_2, the ACK / NACK bit in PUCCH 1018 will be set to 0. Therefore, in message 3 1020, C-DAI=1, T-DAI=2, HARQ=x, and NDI=0. At least because NDI does not toggle between the values ​​in message 2 1008 and message 3 1020 , PDSCH_3 (from 1014 ) is retransmitted as PDSCH_3ReTx 1022 , and PDSCH_4 (from 1016 ) is retransmitted as PDSCH_4ReTx 1024 .

[0158] Fig.11 1 is a flow chart illustrating an exemplary process 1100 for wireless communications operating at a scheduling entity according to some aspects of the present disclosure. Process 1100 may be used to implement dynamic spectrum sharing. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and certain illustrated features may not be required for implementation of all embodiments. In some instances, process 1100 may be performed by Figure 6The scheduling entity 600 is shown to perform. In some examples, the process 1100 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0159] In block 1102, the scheduling entity 700 may format a first DCI to schedule a first plurality of PDSCHs in a first plurality of cells. In block 1104, the scheduling entity may send the first DCI to the scheduled entity in a first PDCCH. In block 1106, the scheduling entity may optionally use a carrier information field (CIF) in the first DCI to identify the first plurality of cells. Alternatively, in block 1008, the scheduling entity may optionally use a carrier information field (CIF) and a new data indicator (NDI) in the first DCI to identify a retransmission of at least one of the first plurality of PDSCHs.

[0160] Fig.12 1 is a flow chart illustrating an exemplary process 1200 for wireless communications operating at a scheduling entity according to some aspects of the present disclosure. Process 1200 may be used to implement dynamic spectrum sharing. As described below, within the scope of the present disclosure, some or all of the illustrated features may be omitted in certain implementations, and certain illustrated features may not be required for implementation of all embodiments. In some instances, process 1200 may be performed by Figure 7 The process 1100 is shown to be performed by the scheduled entity 700. In some examples, the process 1100 can be performed by any suitable device or component for performing the functions or algorithms described below.

[0161] In block 1202, the scheduled entity may identify a search space in a resource element grid where a control region set (CORESET) is located. In block 1204, the scheduled entity may decode the CORESET to obtain a first DCI. In block 1206, the scheduled entity may determine, based on the first DCI, locations in the resource element grid that contain a first plurality of PDSCHs in a first plurality of cells scheduled for the scheduled entity. In block 1206, the scheduling entity may decode data located in the first plurality of PDSCHs.

[0162] Several aspects of wireless communication networks have been presented with reference to exemplary embodiments. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0163] For example, various aspects may be implemented in other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented in systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other appropriate systems. The actual telecommunication standards, network architectures, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system.

[0164] In this disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as being preferred or advantageous over other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the discussed features, advantages, or modes of operation. The term "coupled" as used herein refers to a direct or indirect coupling between two objects. For example, if object A is in physical contact with object B, and object B is in contact with object C, objects A and C may still be considered to be coupled to each other even if they are not in direct physical contact. For example, a first object may be coupled to a second object even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include hardware implementations of electrical devices and conductors that, when connected and configured, are capable of performing the functions described in the disclosure without limitation to the type of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, are capable of performing the functions described in the disclosure.

[0165] One or more components, steps, features and / or functions are Figures 1 to 10 Can rearrange and / or combine into single component, step, feature or function, or be implemented in several components, steps or functions.Under the situation that does not deviate from the novel features disclosed herein, additional elements, components, steps and / or functions can also be added. Figures 1 to 10 The apparatus, devices and / or components illustrated in the figure may be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.

[0166] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. Based on design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in an example order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.

[0167] The above description is provided to enable any technician in the field to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein, unless otherwise specified, the elements mentioned in the singular are not intended to mean "one and only one", but "one or more". Unless otherwise expressly stated, the term "some" refers to one or more. The phrase "at least one" of a series of items refers to any combination of these items, including a single member. For example, "at least one of a, b or c" is intended to cover: a; b; c; a and c; b and c; and a, b and c. All structural and functional equivalents of the elements of the various aspects described in this disclosure are known or will be known to those of ordinary skill in the art, and are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be public, regardless of whether such disclosure is clearly stated in the claims.

Claims

1. A wireless communication method operating at a scheduling entity, the method comprising: formatting the first downlink control information DCI to schedule a first plurality of physical downlink shared channels PDSCH in the first plurality of cells using a first carrier information field CIF identifying a first subset of the first plurality of cells in the first downlink control information DCI; formatting the second DCI to schedule a second plurality of PDSCHs in the first plurality of cells using a second CIF in the second DCI identifying a second subset of the first plurality of cells different from the first subset of the first plurality of cells; Sending the first DCI to a scheduled entity in a first physical downlink control channel (PDCCH); as well as The second DCI is sent to the scheduled entity in a second PDCCH. 2 . The method of claim 1 , wherein there is a one-to-one relationship between the first plurality of PDSCHs and the first plurality of cells. 3 . The method of claim 1 , wherein there is a many-to-one relationship between the first plurality of PDSCHs and the first plurality of cells, respectively. 4 . The method of claim 1 , further comprising identifying a retransmission of at least one of the first plurality of PDSCHs using a carrier information field (CIF) and a new data indicator (NDI) in the first DCI.

5. The method according to claim 4, wherein: If an immediately preceding NDI in an immediately preceding DCI is equal to the NDI in the first DCI, the CIF identifies at least one of the first plurality of PDSCHs, and the NDI indicates that at least one of the first plurality of PDSCHs is a retransmission. 6 . The method of claim 4 , further comprising identifying content of the at least one of the first plurality of PDSCHs using a HARQ process identifier.

7. The method according to claim 1, further comprising: receiving an acknowledgement / negative acknowledgement ACK / NACK associated with the first DCI in a single PUCCH; If the ACK / NACK is NACK, formatting a second DCI to schedule retransmission of the first plurality of PDSCHs; as well as The second DCI is sent to the scheduled entity in a second PDCCH.

8. The method according to claim 1, further comprising: Receiving ACK / NACK associated with multiple DCIs in a single PUCCH; formatting a second DCI to schedule retransmission of any PDSCH sets associated with the NACK; and The second DCI is sent to the scheduled entity in a second PDCCH different from the first PDCCH.

9. The method according to claim 1, further comprising: formatting a second DCI to schedule a second plurality of PDSCHs in a second plurality of cells; sending the second DCI to a scheduled entity in a second PDCCH different from the first PDCCH; as well as Acknowledgement / negative acknowledgement ACK / NACK related to both the first DCI and the second DCI is received in a single PUCCH.

10. The method according to claim 9, further comprising: formatting a third DCI in response to receiving a NACK in a single PUCCH to reschedule at least one of the first plurality of PDSCHs or the second plurality of PDSCHs based on content of the NACK; as well as The third DCI is sent to the scheduled entity in a third PDCCH.

11. A wireless communication device, comprising: means for formatting the first downlink control information DCI to schedule a first plurality of physical downlink shared channels PDSCH in the first plurality of cells using a first carrier information field CIF identifying a first subset of the first plurality of cells in the first downlink control information DCI; means for formatting the second DCI to schedule a second plurality of PDSCHs in the first plurality of cells using a second CIF in a second DCI for a second subset of the first plurality of cells different from the first subset of the first plurality of cells; means for sending said first DCI to a scheduled entity in a first physical downlink control channel, PDCCH; as well as Means for sending the second DCI in a second PDCCH to the scheduled entity.

12. A non-transitory computer readable medium storing computer executable code, comprising code for causing a computer to: formatting the first downlink control information DCI to schedule a first plurality of physical downlink shared channels PDSCH in the first plurality of cells using a first carrier information field CIF identifying a first subset of the first plurality of cells in the first downlink control information DCI; formatting the second DCI to schedule a second plurality of PDSCHs in the first plurality of cells using a second CIF in a second DCI for a second subset of the first plurality of cells different from the first subset of the first plurality of cells; Sending the first DCI to a scheduled entity in a first physical downlink control channel (PDCCH); as well as The second DCI is sent to the scheduled entity in a second PDCCH.

13. A wireless communication device, comprising: processor; a transceiver communicatively coupled to the processor; as well as a memory communicatively coupled to the processor, wherein the processor is configured to: using a first carrier information field (CIF) in first downlink control information (DCI) identifying a first subset of a first plurality of cells to identify the first plurality of cells, formatting the first DCI to schedule a first plurality of physical downlink shared channels (PDSCHs) in the first plurality of cells; using a second CIF in a second DCI identifying a second subset of the first plurality of cells different from the first subset of the first plurality of cells, formatting the second DCI to schedule a second plurality of PDSCHs in the first plurality of cells; Sending the first DCI to a scheduled entity in a first physical downlink control channel (PDCCH); as well as The second DCI is sent to the scheduled entity in a second PDCCH.

14. A wireless communication method operating at a scheduled entity, the method comprising: Identify the search space in the resource element grid where the control region set CORESET is located; Decoding the CORESET to obtain first downlink control information DCI; determining, from the first DCI, locations in the resource element grid containing first plurality of physical downlink shared channels (PDSCHs) in first plurality of cells scheduled for the scheduled entity; as well as decoding data located in the first plurality of PDSCHs; wherein a first carrier information field CIF in the first DCI is used to identify a first subset of the first plurality of cells; and A second CIF in a second DCI is used to identify a second subset of the first plurality of cells different from the first subset of the first plurality of cells.

15. The method of claim 14, wherein there is a one-to-one relationship between the first plurality of PDSCHs and the first plurality of cells. 16 . The method of claim 14 , wherein there is a many-to-one relationship between the first plurality of PDSCHs and the first plurality of cells, respectively. 17 . The method of claim 14 , further comprising identifying a retransmission of at least one of the first plurality of PDSCHs using a carrier information field (CIF) and a new data indicator (NDI) in the first DCI.

18. The method of claim 17, further comprising decoding data located in at least one of the first plurality of PDSCHs received in the retransmission.

19. The method of claim 17, wherein when an NDI in an immediately preceding DCI is equal to the NDI in the first DCI, a CIF identifies at least one of the first plurality of PDSCHs, and the NDI indicates that at least one of the first plurality of PDSCHs is a retransmission.

20. The method of claim 17, further comprising using a HARQ process identifier to identify content of the at least one of the first plurality of PDSCHs.

21. The method of claim 14, further comprising: Sending an acknowledgement / negative acknowledgement ACK / NACK related to the first DCI in a single PUCCH; as well as If any PDSCH of the first plurality of PDSCHs is associated with a NACK, a second DCI scheduling a retransmission of the first plurality of PDSCHs is received.

22. The method of claim 14, further comprising: Identify a subsequent search space in the resource element grid where the subsequent control region set CORESET is located; Decode the subsequent CORESET to obtain the second DCI; determining, from the second DCI, a location in the resource element grid containing at least one second PDSCH in at least one second cell scheduled for the scheduled entity; as well as Data located in the second PDSCH is decoded.

23. The method of claim 22, further comprising identifying the at least one second cell using a carrier information field (CIF) in the second DCI.

24. The method of claim 14, further comprising identifying retransmission of at least one second PDSCH using a carrier information field (CIF) and a new data indicator (NDI) in the second DCI.

25. The method of claim 24, further comprising decoding data located in the at least one second PDSCH received in the retransmission.

26. The method of claim 24, wherein when the NDI in the first DCI is equal to the NDI in the second DCI, the CIF identifies the at least one second PDSCH, and the NDI indicates that the at least one second PDSCH is a retransmission.

27. The method of claim 24, further comprising using a HARQ process identifier to identify content in the at least one second PDSCH.

28. A wireless communication device, comprising: A component for identifying a search space in a resource element grid where a control region set CORESET is located; A component for decoding the CORESET to obtain first downlink control information DCI; means for determining from said first DCI locations in said resource element grid containing a first plurality of physical downlink shared channels (PDSCHs) in a first plurality of cells scheduled for a scheduled entity; as well as means for decoding data located in said first plurality of PDSCHs; wherein a first carrier information field CIF in the first DCI is used to identify a first subset of the first plurality of cells; and A second CIF in a second DCI is used to identify a second subset of the first plurality of cells different from the first subset of the first plurality of cells.

29. A non-transitory computer readable medium storing computer executable code, comprising code for causing a computer to execute: Identify the search space in the resource element grid where the control region set CORESET is located; Decoding the CORESET to obtain first downlink control information DCI; determining, from the first DCI, locations in the resource element grid containing first plurality of physical downlink shared channels (PDSCHs) in first plurality of cells scheduled for a scheduled entity; as well as decoding data located in the first plurality of PDSCHs; wherein a first carrier information field CIF in the first DCI is used to identify a first subset of the first plurality of cells; and A second CIF in a second DCI is used to identify a second subset of the first plurality of cells different from the first subset of the first plurality of cells.

30. A wireless communication device, comprising: processor; a transceiver communicatively coupled to the processor; as well as a memory communicatively coupled to the processor, wherein the processor is configured to: Identify the search space in the resource element grid where the control region set CORESET is located; Decoding the CORESET to obtain first downlink control information DCI; determining, from the first DCI, locations in the resource element grid containing first plurality of physical downlink shared channels (PDSCHs) in first plurality of cells scheduled for a scheduled entity; as well as decoding data located in the first plurality of PDSCHs; wherein a first carrier information field CIF in the first DCI is used to identify a first subset of the first plurality of cells; and A second CIF in a second DCI is used to identify a second subset of the first plurality of cells different from the first subset of the first plurality of cells.

Images