RU2776428C2 - Method and device for transmission and interpretation of downlink control information - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: method contains stages, at which: downlink control information (hereinafter – DCI) is received by means of user equipment (hereinafter – UE) in the second control resource set (hereinafter – CORESET) in the active bandwidth part (hereinafter – BWP) of a downlink (hereinafter – DL) within a carrier, wherein DCI contains a field of allocation of time domain resources for indication of frequency resources allocated for data transmission within the active BWP DL; and data transmission in a frequency-time resource is received by means of UE based on a value of the field of allocation of time domain resources to DCI, a number of resource blocks (hereinafter – RB) of the first CORESET, and support RB determined by means of a physical resource block (PRB) with the least number in the second CORESET.

EFFECT: providing the determination of location of a transmission resource allocated in DCI.

28 cl, 14 dwg, 1 tbl

Description

Cross-reference to related applications

[1] This application claims the benefit of priority of U.S. Provisional Application No. 62/652,490, filed April 4, 2018, entitled "Method and Apparatus for Transmitting and Interpreting Downlink Control Information" and U.S. Non-Provisional Application No. 16/216,191, filed December 11, 2018, and entitled "METHOD AND DEVICE FOR TRANSMISSION AND INTERPRETATION OF DOWNLINK CONTROL INFORMATION", the contents of which are incorporated herein by reference.

Technical field to which the INVENTION RELATES

[2] The present invention relates generally to a wireless communication system and method, and in specific embodiments, to a system and method for determining the location of a transmission resource allocated in Downlink Control Information (DCI).

State of the art

[3] An air interface is a wireless communication channel between two or more communication devices, such as a radio access network device (e.g., base station, NodeB, evolved NodeB, transfer point) and an electronic device (ED - electronic device) (e.g., user equipment ( UE - user equipment), mobile phone, sensor, camera). Typically, both communication devices need to know specific air interface parameters in order to successfully transmit and receive a transmission.

[4] Executing communication devices with the same air interface parameters allows communication devices to reliably identify, organize, and use physical resources such as time, frequency, or time-frequency resources. Therefore, in modern wireless communication systems, transmissions are typically transmitted according to one predefined configuration for an air interface.

[5] However, modern wireless networks are increasingly being used to support communication with different types of traffic, which may have different characteristics and quality of service (QoS) requirements, such as delay, throughput, and simultaneous connections. Therefore, the various types of traffic in today's wireless networks are not suitable for a universal air interface configuration.

[6] In a cellular communication such as New Radio (NR), downlink control information (DCI) is transmitted via a physical downlink control channel (PDCCH) from a radio access network device to an ED to provide the ED with information about specific physical layer parameters such as downlink or uplink data scheduling and other configuration parameters.

[7] ED performed with one or more parts of the bandwidth (BWP - bandwidth part) within the carrier bandwidth. Each BWP consists of several contiguous resource blocks (RB - resource block) within the carrier. In certain scenarios, only one of the configured BWPs is active for the ED at a given time. In other scenarios, multiple configured BWPs are active at the same time for an ED.

[8] The ED is implemented with multiple control resource set (CORESET) in each of the configured BWP EDs, with each CORESET representing a set of physical time and frequency resources for a possible PDCCH transmission. A number of search spaces are configured and associated with each CORESET. Each search space associated with a CORESET corresponds to the number of resource subsets in the CORESET, with each subset corresponding to a possible PDCCH.

[9] The ED reads the information into the DCI through a process known as "blind decoding". The location of the PDCCH containing the DCI in the physical transmission time and frequency resources was not previously known to the ED. Therefore, the ED must blindly search for PDCCHs in the assigned physical time and frequency resource area (the aforementioned subsets of resources in the search space), making repeated attempts to decode candidate PDCCHs in the search space.

[10] For each possible PDCCH ED, it may be necessary to try different decoding parameters for DCI decoding. For example, DCI may be transmitted with different payload sizes. For a given candidate PDCCH, different DCI payload sizes may result in different coding/decoding rates. The ED can only decode the possible DCI if the ED has used the correct payload size. In practice, ED cannot realistically try an infinite number of different combinations of DCI payload sizes during blind decoding due to time and processing constraints. For example, in cellular communications such as New Radio (NR), ED may be limited to trying only a few (eg, only four per interval) different DCI payload sizes during blind decoding.

[11] In certain scenarios, an ED may be configured in an active bandwidth carrier BWP to attempt to decode a DCI whose payload size is based on a different bandwidth portion of the bandwidth carrier. However, in this case, the DCI content may not be clear to the ED or may be misinterpreted because a DCI field whose size is based on a BWP (of size 1) needs to be interpreted to schedule data to another BWP (of size 2) where size 2 ≠ size 1 .

The essence of the invention

[12] Technical advantages are typically achieved through embodiments of the present disclosure that describe a system and method for determining the location of a transmission resource allocated in downlink control information (DCI). Examples of technical benefits may include efficient use of resources for shared DCI and shared data since a group of UEs can access the same physical downlink shared channel (PDSCH) or physical uplink shared channel location. communication lines (PUSCH - physical uplink shared channel) with the same DCI transmission.

[13] According to an aspect of the disclosure, a wireless communication method is provided. The method includes: receiving, by a user equipment (UE), downlink control information (DCI) on a physical downlink control channel (PDCCH) in a downlink active bandwidth (BWP) (DL - downlink) , a DCI for scheduling data transmission, and a DCI containing a frequency domain resource allocation field; and receiving, by the UE, a data transmission on a time-frequency resource determined by at least an initial resource block (RB) and a length of contiguous allocated RBs, wherein the initial RB is based on: a frequency domain resource allocation field value in DCI, a reference RB, and also the number of RBs of the first control resource set (CORESET), and the length of the adjacent allocated RBs is based on: the value of the frequency domain resource allocation field in the DCI and the number of RBs of the first CORESET.

[14] In some embodiments, the reference RB is the lowest numbered physical resource block (PRB) in the second CORESET, and where the second CORESET is a CORESET where the DCI has been decoded by the UE.

, где PRB

является PRB с наименьшим номером в CORESET, где резервная DCI была декодирован посредством UE. [15] In some embodiments, the method further includes determining, by the UE, that the DCI is a backup DCI for data transmission with non-interleaved VRB-PRB mapping, the backup DCI is decoded in a common search space, and for data transmission a virtual RB n mapped to PRB

, where PRB

is the lowest numbered PRB in CORESET, where the standby DCI has been decoded by the UE.

[16] In some embodiments, the Active BWP DL includes allocating RBs for data transmission based on an interleaved mapping of virtual RB packets to interleaved physical RB packets, where the start RB is the virtual start RB and the length of the contiguously allocated RBs is the length of the contiguously allocated virtual RBs, wherein the virtual initial RB defines the start of the length of the adjacent allocated virtual RBs.

[17] In some embodiments, the step of receiving a data transmission includes receiving a data transmission on a frequency-time resource determined by interleaved physical RB bursts, the interleaved physical RB bursts being based on: virtual initial RB, length of contiguous allocated virtual RB, interleaved mapping, and a reference packet of physical RBs.

[18] In some embodiments, the Physical RB Reference Packet is a Physical RB Packet that contains the lowest numbered Physical Resource Block (PRB) in the second CORESET, and where the second CORESET is a CORESET where the DCI has been decoded by the UE.

[19] In some embodiments, the implementation of the DCI is a backup DCI.

[20] In some embodiments, the first CORESET is associated with a CORESET identifier of "0".

[21] In some embodiments, the DCI is associated with a group of UEs, and the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time frequency resource for all UEs in the UE group.

[22] In accordance with another aspect of the disclosure, a user equipment (UE) is provided, including a processor and a computer-readable storage medium that stores computer-executable instructions. When the instructions are executed by the processor, they cause the UE to: receive, by the UE, downlink control information (DCI) on the physical downlink control channel (PDCCH) in the active part of the downlink (DL) bandwidth (BWP), DCI for transmission scheduling data, and a DCI containing a frequency domain resource allocation field; and receive, by the UE, a data transmission in a time-frequency resource determined by at least an initial resource block (RB) and a length of contiguous allocated RBs, wherein the initial RB is based on: the DCI frequency domain resource allocation field value, the reference RB, and the number RB of the first control resource set (CORESET), and the length of the adjacent allocated RBs is based on: the value of the frequency domain resource allocation field in the DCI and the number of RBs of the first CORESET.

[23] In some embodiments, the reference RB is the lowest numbered physical resource block (PRB) in the second CORESET, and where the second CORESET is a CORESET where the DCI has been decoded by the UE.

, где PRB

является PRB с наименьшим номером в CORESET, где резервная DCI была декодирована посредством UE. [24] In some embodiments, the computer-executable instructions, when executed by the processor, further cause the UE to: determine that: the DCI is a standby DCI for non-interleaved VRB-PRB mapping data transmission; the standby DCI is decoded in the common search space and for data transmission the virtual RB n is mapped onto the PRB

, where PRB

is the lowest numbered PRB in CORESET where the standby DCI has been decoded by the UE.

[25] In some embodiments, the active BWP D includes allocating RBs for data transmission based on an interleaved mapping of virtual RB packets to interleaved physical RB packets, where the start RB is the virtual start RB and the length of the contiguously allocated RBs is the length of the contiguously allocated virtual RBs, wherein the virtual initial RB defines the start of the length of the adjacent allocated virtual RBs.

[26] In some embodiments, computer-executable instructions that cause a UE to receive a data transmission cause the UE to receive a transmission in a frequency-time resource determined by interleaved physical RB bursts, interleaved physical RB bursts based on: virtual initial RB, length of contiguous allocated virtual RB, interleaved mappings, and a reference packet of physical RBs.

[27] In some embodiments, the Physical RB Reference Packet is the Physical RB Packet that contains the lowest numbered Physical Resource Block (PRB) in the second CORESET, and where the second CORESET is a CORESET where the DCI has been decoded by the UE.

[28] In some embodiments, the implementation of the DCI is a backup DCI.

[29] In some embodiments, the first CORESET is associated with a CORESET identifier of "0".

[30] In some embodiments, the DCI is associated with a group of UEs, and the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time frequency resource for all UEs in the UE group.

[31] According to another aspect of the disclosure, a wireless communication method is provided. The method includes: transmitting, by a base station, downlink control information (DCI) on a physical downlink control channel (PDCCH) in a downlink (DL) active bandwidth (BWP), DCI for data transmission scheduling and DCI containing a frequency domain resource allocation field; and transmitting, by means of the base station, to the user equipment (UE) a data transmission in a frequency-time resource determined by at least an initial resource block (RB) and a length of contiguous allocated RBs, the initial RB being based on: the value of the frequency domain resource allocation field in the DCI, the reference RB and the number of RBs of the first control resource set (CORESET), and the length of the adjacent allocated RBs is based on: the value of the frequency domain resource allocation field in the DCI and the number of RBs of the first CORESET.

[32] In some embodiments, the reference RB is the lowest numbered physical resource block (PRB) in the second CORESET, and where the second CORESET is a CORESET where the DCI has been decoded by the UE.

[33] In some embodiments, the Active BWP DL includes allocating RBs for data transmission based on an interleaved mapping of virtual RB packets to interleaved physical RB packets, where the start RB is the virtual start RB and the length of the contiguously allocated RBs is the length of the contiguously allocated virtual RBs, wherein the virtual initial RB defines the start of the length of the adjacent allocated virtual RBs.

[34] In some embodiments, the data transmission step includes a step of transmitting a data transmission in a frequency-time resource determined by interleaved physical RB bursts, the interleaved physical RB bursts being based on: virtual initial RB, length of contiguous allocated virtual RBs , interleaved mapping, and a physical RB reference burst.

[35] In some embodiments, the Physical RB Reference Packet is the Physical RB Packet that contains the lowest numbered Physical Resource Block (PRB) in the second CORESET, and where the second CORESET is a CORESET where the DCI has been decoded by the UE.

[36] In some embodiments, the implementation of the DCI is a backup DCI.

[37] In some embodiments, the first CORESET is associated with a CORESET identifier of "0".

[38] In some embodiments, the DCI is associated with a group of UEs, and the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time frequency resource for all UEs in the UE group.

[39] In accordance with yet another aspect of the disclosure, an apparatus is provided, including a processor and a computer-readable storage medium that stores computer-executable instructions. When executed by the processor, the instructions cause the device to: transmit downlink control information (DCI) on a physical downlink control channel (PDCCH) in a downlink (DL) active bandwidth portion (BWP), DCI for data transmission scheduling, and DCI , containing a frequency domain resource allocation field; and transmit to the user equipment (UE) a data transmission in a frequency-time resource determined by at least an initial resource block (RB) and a length of contiguous allocated RBs, wherein the initial RB is based on: the value of the frequency domain resource allocation field in the DCI, the reference RB and the number of RBs of the first control resource set (CORESET), and the length of the adjacent allocated RBs is based on: the value of the frequency domain resource allocation field in the DCI and the number of RBs of the first CORESET.

[40] In some embodiments, the reference RB is the lowest numbered physical resource block (PRB) in the second CORESET, and where the second CORESET is a CORESET where the DCI has been decoded by the UE.

[41] In some embodiments, the Active BWP DL includes allocating RBs for data transmission based on an interleaved mapping of virtual RB packets to interleaved physical RB packets, where the start RB is the virtual start RB and the length of the contiguously allocated RBs is the length of the contiguously allocated virtual RBs, wherein the virtual initial RB defines the start of the length of the adjacent allocated virtual RBs.

[42] In some embodiments, the data transmission step includes a step of transmitting a data transmission in a frequency-time resource determined by interleaved physical RB bursts, the interleaved physical RB bursts being based on: virtual initial RB, length of contiguous allocated virtual RBs , interleaved mapping, and a physical RB reference burst.

[43] In some embodiments, the Physical RB Reference Packet is the Physical RB Packet that contains the lowest numbered Physical Resource Block (PRB) in the second CORESET, and where the second CORESET is a CORESET where the DCI has been decoded by the UE.

[44] In some embodiments, the implementation of the DCI is a backup DCI.

[45] In some embodiments, the first CORESET is associated with a CORESET identifier of "0".

[46] In some embodiments, the DCI is associated with a group of UEs, and the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time frequency resource for all UEs in the UE group.

Brief description of the drawings

[47] For a more complete understanding of the present invention and its advantages, reference is made here to the following description in conjunction with the accompanying drawings, in which:

[48] FIG. 1 - network diagram of the communication system.

[49] FIG. 2 is a block diagram of an air interface manager for configuring a software defined air interface.

[50] FIG. 3A is a block diagram of an exemplary client-side electronic device.

[51] FIG. 3B is a block diagram of an exemplary network side electronic device.

[52] FIG. 4A is an example of a set of virtual resource blocks (VRBs) including a subset of VRBs scheduled for a particular transmission type.

[53] FIG. 4B is an example of an interleaved display of a set of VRBs including a subset of the VRBs in FIG. 4A to a set of physical resource blocks (PRBs).

[54] FIG. 5 is an example of a non-interleaved mapping of a VRB set including a VRB subset to a PRB set for three different user equipments (UEs) having different active bandwidth portions (BWPs).

[55] FIG. 6 is an example of a non-interleaved mapping of a VRB set including a VRB subset to a PRB set for three different UEs having different active BWPs and a non-VRB subcarrier spacing configuration.

[56] FIG. 7 is an example of an interleaved mapping of a VRB set, including a VRB subset, to a PRB set for three different UEs having different active BWPs.

[57] FIG. 8 is an example of interleaved mapping of a VRB set including a VRB subset onto a PRB set for three different UEs having different active BWPs and a non-VRB subcarrier spacing configuration.

[58] FIG. 9 is a flowchart describing a method for use by a UE in determining the location of a transmission resource allocated in downlink control information (DCI).

[59] FIG. 10 is a flowchart describing a method for use by a network-side device when allocating a transmission resource.

[60] FIG. 11 is a flowchart describing another method for use by a UE in determining the location of a transmission resource allocated in downlink control information (DCI).

[61] FIG. 12 is a flowchart describing another method for use by a network-side device when allocating a transmission resource.

[62] The corresponding numbers and symbols in the various figures generally refer to the respective parts, unless otherwise indicated. The drawings are made to clearly illustrate relevant aspects of the embodiments and are not necessarily drawn to scale.

Detailed Description of Illustrative Embodiments

[63] The structure, manufacture, and use of the currently preferred embodiments are discussed in detail below. However, it should be understood that the present invention provides many applicable inventive ideas that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways of making and using the invention and do not limit the scope of the invention.

[64] FIG. 1 illustrates an exemplary communications system 100 in which embodiments of the present disclosure may be implemented. In general, communication system 100 allows a plurality of wireless or wired elements to exchange data and other content. The purpose of the communication system 100 may be to provide content (voice, data, video, text) via broadcast, narrowcast, from user device to user device, and so on. Communication system 100 may operate by sharing resources such as bandwidth.

[65] In this example, communication system 100 includes electronic devices (ED) 110a-110c, radio access networks (RAN - radio access network) 120a-120b, core network 130, public switched telephone network (PSTN - public switched telephone network ) 140, the Internet 150, and other networks 160. Although the specific numbers of these components or elements are shown in FIG. 1, any reasonable number of these components or elements may be included in communication system 100.

[66] ED 110a-110c are configured to function, communicate, or both in the communication system 100. For example, EDs 110a-110c are configured to transmit, receive, or both over wireless or wired communication channels. Each ED 110a-110c represents any suitable end user device for wireless operation and may include (or may be referred to as) a user equipment/device (UE), a wireless transmit/receive unit (WTRU), mobile station, fixed or mobile user device, cell phone, station (STA - station), machine type communication device (MTC - machine type communication), personal digital assistant (PDA - personal digital assistant), smartphone, laptop, computer, tablet, wireless sensor or consumer electronics device.

[67] FIG. 1, RANs 120a-120b include base stations 170a-170b, respectively. Each base station 170a-170b is configured to wirelessly communicate with one or more EDs 110a-110c to provide access to any other base station 170a-170b, core network 130, PSTN 140, internet 150, and/or other networks 160. For example, base stations 170a-170b may include (or be) one or more of several well-known devices, such as a base transceiver station (BTS), Node-B (NodeB), advanced NodeB (eNodeB), home eNodeB, gNodeB , transmission point (TP), site controller, access point (AP) or wireless router. Any ED 110a-110c may alternatively or additionally be configured to interact with, access, or communicate with any other base station 170a-170b, internet 150, core network 130, PSTN 140, other networks 160, or any combination of the foregoing. Communication system 100 may include RANs such as RAN 120b, where a corresponding base station 170b accesses core network 130 via internet 150 as shown.

[68] ED 110a-110c and base stations 170a-170b are examples of a communication device that may be configured to implement some or all of the functionality and/or embodiments described herein. In the embodiment shown in FIG. 1, base station 170a forms part of RAN 120a, which may include other base stations, base station controller(s), base station controller(s), radio network controller(s), radio network controller(s), relay nodes, and/or devices. Any base station 170a, 170b may be a single element as shown, or multiple elements distributed in the respective RAN, or otherwise. Also, base station 170b forms part of RAN 120b, which may include other base stations, elements, and/or devices. Each base station 170a-170b transmits and/or receives wireless signals in a specific geographic area or area, sometimes referred to as a "cell" or "coverage area". The cell may be further divided into cell sectors, and the base station 170a-170b may, for example, use multiple transceivers to provide service to multiple sectors. In some embodiments, pico or femtocells may be installed where the radio access technology supports them. In some embodiments, multiple transceivers may be used for each cell, such as using multiple-input multiple-output (MIMO) technology. RAN number 120a-120b is shown as an example only. Any number of RANs may be envisaged in the development of communication system 100.

[69] Base stations 170a-170b communicate with one or more EDs 110a-110c over one or more radio interfaces 190 using wireless links such as radio frequency (RF - radio frequency), microwave, infrared (IR - infrared), etc. d. The radio interfaces 190 may use any suitable radio access technology. For example, the communication system 100 may implement one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), time division multiple access, frequency division multiple access (FDMA), orthogonal FDMA (OFDMA) or single-carrier FDMA (SC-FDMA) in radio interfaces 190.

[70] The base station 170a-170b may implement terrestrial radio access (UTRA - Universal Mobile Telecommunication System) to establish a radio interface 190 using wideband CDMA (WCDMA - wideband CDMA). Meanwhile, the base station 170a-170b can implement protocols such as High Speed Packet Access (HSPA), Enhanced HPSA (HSPA+), further including High Speed Downlink Packet Access (HSDPA). ), High Speed Packet Uplink Access (HSUPA), or both. Alternatively, the base station 170a-170b may establish an E-UTRA - Evolved UTMS Terrestrial Radio Access (E-UTRA) air interface 190 using Long-Term Evolution (LTE), LTE-A and/or LTE-B. It is contemplated that communication system 100 may utilize multi-channel access functionality, including such schemes as described above. Other radio technologies for implementing radio interfaces include IEEE 802.11, 802.15, 802.16, CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, IS-2000, IS-95, IS-856, GSM, EDGE, and GERAN. Of course, other multiple access schemes and wireless protocols may be used.

[71] RANs 120a-120b are connected to core network 130 to provide EDs 110a-110c with various services such as voice, data, and other services. RANs 120a-120b and/or core network 130 may be in direct or indirect communication with one or more other RANs (not shown) that may or may not be served directly by core network 130 and may or may not use the same radio access technology as and RAN 120a, RAN 120b, or both. Core network 130 may also serve as a gateway for access between (i) RANs 120a-120b or EDs 110a-110c or both, and (ii) other networks (such as PSTN 140, Internet 150, and other networks 160). In addition, some or all of the EDs 110a-110c may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies and/or protocols. Instead of (or in addition to) wireless communications, EDs may communicate over wired links with a service provider or switch (not shown) as well as the Internet 150. PSTN 140 may include circuit switched telephone networks to provide traditional telephony ( POTS - plain old telephone service). The Internet 150 may include a network of computers and subnets (intranets), or both, and include protocols such as internet protocol (IP), transmission control protocol (TCP), user datagram (UDP). protocol). EDs 110a-110c may be multimode devices capable of operating in accordance with a variety of radio access technologies and include a variety of transceivers necessary to support them.

[72] In embodiments of the present invention, communication system 100 is a heterogeneous communication system with different types of transmission sources and/or different types of transmission destinations. Different types of transmission sources may have different transmission capabilities. Different types of transmission destinations may have different reception capabilities.

[73] In the heterogeneous communication system ED 110a-110c of FIG. 1 include various types of devices having different capabilities and requirements. More specifically, each ED 110a-110c may be associated with a different type of traffic having specific requirements for quality of service (QoS), latency, throughput, concurrent connections, and so on. Exemplary EDs 110a-110c associated with various types of traffic may include a smartphone, a computer, a television, a security camera, a sensor, a thermostat, a heart rate monitor, and so on. In a specific example, ED 110a is a computer, ED 110b is a sensor, and ED 110c is a heart rate sensor. Each of the EDs 110a-110c may have different wireless capabilities and requirements.

[74] In addition, in a heterogeneous communication system, base stations 170a-170b may communicate with one or more EDs 110a-110c over one or more software-defined air interfaces 190 using wireless links. Different radio access network devices (eg, base stations 170a-170b) and electronic devices (eg, EDs 110a-110c) may have different transmission capabilities and/or transmission requirements. As an example, an eNB may have multiple transmit antennas. A pico cell may have only one transmit antenna or a relatively small number of transmit antennas. In addition, a pico cell can transmit at a lower maximum power level compared to an eNB. Similarly, a computer may have much higher data bandwidth requirements and signal processing capabilities than a sensor. In another example, a heart rate sensor may have much tighter latency and reliability requirements than a TV.

[75] Therefore, in a heterogeneous communication system such as heterogeneous communication system 100, different pairs of communication devices (i.e., a network device and an electronic device; or a network device and another network device; or an electronic device and another electronic device) may have different transfer capabilities and/or transfer requirements. Different transmission capabilities and/or transmission requirements may be satisfied by having a choice of different air interface configurations for different devices, communications, or requirements.

[76] FIG. 2 illustrates a schematic diagram of an air interface manager 200 for configuring a software defined air interface 190. The air interface manager 200 may be, for example, a module containing a number of components or building blocks that define the parameters of the air interface 190 and collectively determine how a transmission is to be performed and/or received via radio interface 190.

[77] The components of the air interface manager 200 include at least one of a waveform component 205, a frame structure component 210, a multiple access scheme component 215, a protocol component 220, and a coding and modulation component 225.

[78] The waveform component 205 may indicate the waveform of the transmitted signal. Waveform options may include orthogonal multiple access signals and non-orthogonal multiple access signals. Non-limiting examples of such waveform options include Orthogonal Frequency Division Multiplexing (OFDM), Filtered OFDM (f-OFDM), Time Framed OFDM, Filtered Multi-Frequency (FBMC) Filter Bank Multicarrier), Universal Filtered Multicarrier (UFMC), Generalized Frequency Division Multiplexing (GFDM), Wavelet Packet Modulation (WPM), transmission at a rate faster than Nyquist speed (FTN - Faster Than Nyquist), and a low peak to average power ratio waveform (low PAPR WF - low Peak to Average Power Ratio Waveform).

[79] The frame structure component 210 may indicate the configuration of a frame or group of frames. Frame structure component 210 may indicate one or more of time, frequency, pilot signature, code, or other parameter of a frame or group of frames.

[80] Non-limiting examples of frame structure options include: the number of symbols in a time slot, the number of time slots in a frame, and the duration of each time slot (sometimes referred to as a transmission time interval, TTI, or transmission time unit, TTU ( transmission time unit)). The frame structure component may also indicate whether the timeslot is a configurable multi-level TTI, a fixed TTI, or a configurable single-level TTI. The frame structure component may further define a coexistence mechanism for different frame structure configurations.

[81] For some waveforms, such as certain OFDM-based waveforms, the frame structure component may also indicate one or more associated signal parameters, such as subcarrier spacing width, symbol duration, cyclic prefix length (CP), width channel bandwidths, guardbands/subcarriers, and sample size and frequency.

[82] In addition, the frame structure component 210 may further indicate whether the frame structure is used in time division duplex or frequency division duplex.

[83] Together, the descriptions of the waveform component and the frame structure component are sometimes referred to as "numerology". Thus, air interface 190 may include a numerology component 230 defining a number of air interface configuration parameters such as subcarrier spacing, CP length, symbol length, slot length, and symbols per slot.

[84] These numerologies, also known as subcarrier spacing patterns, can be scalable in the sense that subcarrier spacings of different numerologies are multiples of each other, and slot lengths of different numerologies are also multiples of each other. Such a scalable scheme for multiple numerologies provides implementation benefits such as scalable total OFDM symbol duration in the context of time division duplex (TDD).

[85] Frames may be configured using one or a combination of scalable numerologies. For example, 60 kHz subcarrier spacing numerology has a relatively short OFDM symbol duration (because OFDM symbol duration varies inversely with subcarrier spacing), which makes 60 kHz numerology particularly suitable for ultra-low latency communications such as vehicle-to-all (V2X) - Vehicle-to-Any). An additional example of a numerology with a relatively short OFDM symbol duration suitable for low latency communication is 30 kHz subcarrier spacing numerology. The 15 kHz subcarrier spacing numerology can be compatible with LTE or serve as the default numerology for the device's initial network access. This 15 kHz numerology may also be suitable for broadband services. Numerology with 7.5 kHz spacing, which has a relatively long OFDM symbol duration, can be particularly useful for improving coverage and broadcast. Additional applications of these numerologies will or will become apparent to those skilled in the art. Of the four listed numerologies, those with sub-carrier spacings of 30 kHz and 60 kHz are more robust to Doppler spread (fast moving conditions) due to the wider sub-carrier spacing. It is further contemplated that different numerologies may use different values for other physical layer parameters such as the same subcarrier spacing and different cyclic prefix lengths.

[86] In addition, it is contemplated that other subcarrier spacings, such as higher or lower subcarrier spacings, may be used. For example, other subcarrier spacings varying by a factor of 2ⁿ, include 120 kHz and 3.75 kHz.

[87] In other examples, more limited scalability can be implemented in which all two or more numerologies have subcarrier spacings that are integer multiples of the smallest subcarrier spacing without necessarily being associated with a factor of 2ⁿ. Examples include sub-carrier spacings of 15 kHz, 30 kHz, 45 kHz, 60 kHz.

[88] Other examples may use non-scalable subcarrier spacings that are not integer multiples of the smallest subcarrier spacing, eg 15 kHz, 20 kHz, 30 kHz, 60 kHz.

[89] OFDM-based signals can be used to transmit a signal in which multiple numerologies coexist simultaneously. More specifically, multiple subband OFDM signals may be generated in parallel, each within a different subband, and each subband has a different subcarrier spacing (and, more generally, with a different numerology). The plurality of subband signals are combined into one signal for transmission, eg for downlink transmissions. Alternatively, multiple subband signals may be transmitted from separate transmitters, eg for uplink transmissions from multiple electronic devices (EDs), which may be user equipments (UEs).

[90] The use of different numerologies can allow air interface 190 to support the coexistence of a diverse set of use cases having a wide range of quality of service (QoS) requirements, such as different levels of delay or reliability tolerance, as well as different bandwidth requirements or signaling overhead. In one example, the base station may signal to the ED an index representing the selected numerology, or one parameter (eg, subcarrier spacing) of the selected numerology. Based on this signaling, the ED may determine the parameters of the selected numerology from other information, such as a lookup table of possible numerologies stored in memory.

[91] Continuing with the components of the air interface 190, the component 215 scheme multiple access may indicate how access to the channel for one or more ED. Non-limiting examples of variants of multiple access techniques include technologies defining how EDs share a common physical channel, such as: time division multiple access (TDMA), frequency division multiple access (FDMA), code division multiple access (CDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Low Density Signature Multicarrier Code Division Multiple Access (LDS-MC-CDMA), Non-Orthogonal Multiple Access access (NOMA - Non-Orthogonal Multiple Access), multiple access with pattern division (PDMA - Pattern Division Multiple Access), multiple access with structural division (LPMA - Lattice Partition Multiple Access), multiple access with resource allocation (RSMA - Resource Spread Multiple Access) and Sparse Code Multiple Access (SCM A - Sparse Code Multiple Access). In addition, variants of multiple access techniques may include scheduled access, unscheduled access, also known as unauthorized access, non-orthogonal multiple access, orthogonal multiple access, e.g. contention-based common channel resource, non-contention-based common channel resource, and radio-based cognitive access.

[92] Protocol component 220 may indicate how transmission and/or retransmission should be performed. Non-limiting examples of transmission and/or retransmission mechanism options include those specifying a scheduled data channel size, a signaling mechanism for transmission, and/or a signaling mechanism for retransmission.

[93] The coding and modulation component 225 may indicate how the transmitted information may be encoded/decoded and modulated/demodulated for transmission/reception purposes. Coding can refer to methods for error detection and forward error correction. Non-limiting examples of coding options include turbo trellis codes, turbo composite codes, fountain codes, low density parity codes, and polar codes. Modulation may refer simply to constellation (including, for example, modulation technique and order), or more specifically to various types of advanced modulation techniques such as hierarchical modulation and low PAPR modulation.

[94] Since the air interface contains many components or building blocks, and each component can have many possible technologies (also referred to herein as radio interface capabilities options), the air interface manager 200 can configure and store a large number of different types of air interface profiles, where each air interface profile defines the corresponding set of radio interface capability parameters.

[95] For example, in each air interface profile defining a corresponding set of radio interface capability options, an air interface capability option is selected for each of the air interface component building blocks. Each of the different air interface profiles may be designed to satisfy a different set of transmission requirements, including transmission content, transmission condition, and reception condition.

[96] In accordance with the transmission requirements of the pair of communication transceivers, one of the various air interface profiles that best suits the transmission requirements may be selected from the air interface manager 200 and used for communication between the pair of communication transceivers.

[97] In further embodiments, air interface manager 200 may modify or update its components, profiles, or capability options. For example, air interface manager 200 may replace waveform and frame structure components 205, 210 with a single numerology component 230. Conversely, the air interface manager 200 may separate the coding and modulation component 225 into a separate coding component and a separate modulation component. In addition, the air interface manager 200 may add a new air interface configuration component to be defined in the future.

[98] The air interface manager 200 may also update certain components to modify the capability options of any given component. For example, air interface manager 200 may update modulation and coding component 225 to include a higher order modulation scheme.

[99] By updating the stored components, profiles, and possible options, the air interface manager 200 can adapt flexibly to better accommodate different types and services of wireless traffic. Modification or updating of components, profiles, and possible options may allow the air interface manager 200 to provide suitable air interface profiles for traffic types or services other than those already provided for ultra-reliable low latency communications (URLLC), advanced mobile broadband communications (eMBB - enhanced mobile broadband) and streaming machine-type communications (mMTC - massive machine-type communications).

[100] FIG. 3A and 3B illustrate exemplary devices that may implement the methods and ideas of this disclosure. In particular, FIG. 3A illustrates an example ED 110 and FIG. 3B illustrates an exemplary base station 170. These components may be used in communications system 100 or any other suitable system.

[101] As shown in FIG. 3A, ED 110 includes at least one processing unit 300. Processing unit 300 implements various processing operations of ED 110. For example, processing unit 300 may perform signal coding, data processing, power control, I/O processing, or any other functionality that allows ED 110 to function in communication system 100. The processing unit 300 may also be configured to implement some or all of the functionality and/or embodiments described in more detail above. Each processing unit 300 includes any suitable processing device or computing device configured to perform one or more operations. Each processing unit 300 may, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or ASIC.

[102] ED 110 also includes at least one transceiver 302. The transceiver 302 is configured to modulate data or other content for transmission via at least one antenna 304 or Network Interface Controller (NIC). The transceiver 302 is also configured to demodulate data or other content received via at least one antenna 304. Each transceiver 302 includes any suitable structure for generating signals for wireless or wired transmission and/or processing signals received wirelessly or wired. Each antenna 304 includes any suitable structure for transmitting and/or receiving wireless or wired signals. One or more transceivers 302 may be used in ED 110. One or more antennas 304 may be used in ED 110. Although transceiver 302 is shown as a single functional unit, it may also be implemented using at least one transmitter and at least one separate receiver.

[103] ED 110 further includes one or more input/output devices 306 or interfaces (such as a wired interface to the internet 150). I/O devices 306 allow interaction with the user or other devices on the network. Each input/output device 306 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communication.

[104] In addition, ED 110 includes at least one memory 308. Memory 308 stores instructions and data used, generated, or collected by ED 110. For example, memory 308 may store program instructions or modules configured to implement certain or all of the functionality and/or embodiments described above, and which are performed by the block(s) 300 processing. Each memory 308 includes any suitable volatile and/or non-volatile storage(s) and retrieval(s) device(s). Any suitable type of memory can be used, such as random access memory (RAM), read only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory, secure digital (SD - secure digital) memory card, and the like.

[105] As shown in FIG. 3B, base station 170 includes at least one processing unit 350, at least one transmitter (TX, transmitter) 352, at least one receiver (RX, receiver) 354, one or more antennas 356, at least one memory 358; and one or more input/output devices or interfaces 366. A transceiver, not shown, may be used in place of transmitter 352 and receiver 354. Scheduler 353 may be associated with processing unit 350. Scheduler 353 may be included in or operate separately from base station 170. Processing unit 350 implements various processing operations of base station 170 such as signal coding, data processing, power control, input/output processing, or any other functionality. Processing unit 350 may also be configured to implement some or all of the functionality and/or embodiments described in more detail above. Each processing unit 350 includes any suitable processing device or computing device configured to perform one or more operations. Each processing unit 350 may, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or ASIC.

[106] Each transmitter 352 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each receiver 354 includes any suitable structure for processing signals received wirelessly or wired from one or more EDs or other devices. Although they are shown as separate components, at least one transmitter 352 and at least one receiver 354 may be combined into a transceiver. Each antenna 356 includes any suitable structure for transmitting and/or receiving wireless or wired signals. Although a common antenna 356 is shown here connected to both transmitter 352 and receiver 354, one or more antennas 356 may be connected to transmitter(s) 352 and one or more individual antennas 356 may be connected to receiver(s). ) 354. Each memory 358 includes any suitable volatile and/or non-volatile storage and retrieval device(s), such as those described above in connection with ED 110. Memory 358 stores instructions and data used, generated, or collected by base station 170. For example, memory 358 may store program instructions or modules configured to implement some or all of the functionality and/or embodiments described above, and which are executed by block(s). ) 350 processing.

[107] Each I/O device 366 allows interaction with the user or other devices on the network. Each input/output device 366 includes any suitable structure for providing information to a user or receiving/providing information from a user, including communications over a network interface.

[108] As described above, downlink control information (DCI) is transmitted via a physical downlink control channel (PDCCH) from a network-side device such as a base station to an ED to provide the ED with information about specific physical layer parameters such as like scheduling downlink or uplink data and other configuration parameters. DCI may be transmitted using different DCI formats that serve different purposes. Table 1 below provides examples of eight different DCI formats used for eight different purposes.

Table 1: DCI Formats

DCI format Application 0_0 Scheduling a physical uplink shared channel (PUSCH) in one cell 0_1 Single cell PUSCH scheduling 1_0 Scheduling a physical downlink shared channel (PDSCH) in one cell 1_1 Single cell PDSCH scheduling 2_0 UE group notification of slot format 2_1 UE group notification of orthogonal frequency division multiplexed (OFDM) physical resource block(s) (PRB) and symbol(s), where the UE may assume that the transmission is not intended for the UE 2_2 Transmission of transmit power control (TPC) commands for the physical uplink control channel (PUCCH) and PUSCH 2_3 Sending a group of TPC commands for transmitting a sounding reference signal (SRS) by one or more UEs

[109] DCI formats 0_0 and 1_0 are known as "backup" DCI formats for scheduling uplink data and downlink data, respectively. The DCI fallback formats are intended to be used when performing basic radio setup or reconfiguration or transmission of system information. They may include less information than other DCI formats (i.e., the minimum amount of information required to establish a radio baseline or perform reconfiguration).

[110] DCI formats 0_1 and 1_1 are known as "non-backup" DCI formats for scheduling uplink data and downlink data, respectively. The DCI formats 2_0 and 2_1 are DCI formats for notifying the ED of slot format information and benefit information, respectively. DCI formats 2_2 and 2_3 are DCI formats for notifying an ED of transmission power control information. While embodiments of the present application may be described below with specific reference to a reserved DCI, it should be understood that, more generally, aspects of the disclosure may be used with many different types of DCIs.

[111] The payload size of the DCI fallback formats may be determined based on the initial downlink BWP rather than the active downlink BWP. The initial downlink BWP is the frequency domain size of the time-frequency resource allocated to the UE when it initially accesses the network. The initial BWP may be used after initial network access, but often the UE will be configured with an active BWP on further network usage. The active BWP can be reconfigured accordingly. The initial size of the downlink BWP (in terms of the number of resource blocks) may be different from the active downlink BWP. If the size of the frequency domain resource allocation field in the DCI is determined by the number of resource blocks in the initial downlink BWP, this may create ambiguity or misinterpretation of the standby DCI content when the DCI is used to allocate resources in the active BWP if the active BWP has a size other than the original downlink BWP. Embodiments of the present disclosure seek to resolve such uncertainty.

[112] In addition to transmitting a frequency domain resource allocation in a standby DCI format, embodiments of the present disclosure may also provide greater spectral efficiency when a standby DCI is used for multiple UEs.

[113] In New Radio (NR), resource allocation can be performed based on the use of a resource indication value (RIV) for a frequency domain resource allocation field included in DCI formats. Resource allocation may be performed with or without a virtual resource block (VRB) to physical resource block (PRB) interleaved mapping. A form of resource allocation based on RIV is used in LTE. However, in LTE RIV, resource allocation is based on the full carrier size and not on a fraction of the carrier size, i.e. bwp. An example of such resource allocation can be performed using resource allocation type 1.

ресурсных блоков в длину, пронумерованных от 0 до

-1. Ресурс, выделенный для передачи данных, является поднабором VRB 412, указанным для начала в ресурсном блоке

, и являющимся

RB в длину.[114] FIG. 4A illustrates a set of Virtual Resource Blocks (VRBs) in which a VRB subset is allocated for data transmission, which may, for example, include a PDSCH to be used to transmit to one or more UEs, or a PUSCH to be used to transmit from a UE to base station. The whole set of VRB 410 has

resource blocks in length, numbered from 0 to

-one. The resource allocated for data transmission is a subset of the VRB 412 specified to start in the resource block

, and being

RB in length.

начального ресурсного блока и количество

выделенных RB. В аспектах настоящего раскрытия значение RIV при использовании вместе с опорным начальным виртуальным ресурсным блоком, т.е. VRB=0, и общий размер (определенный в количестве RB) полосы частот

может использоваться для определения значения

и

. [115] In RIV-based resource allocation, one value, RIV, represents two values: the value

initial resource block and quantity

allocated RB. In aspects of the present disclosure, the RIV value when used in conjunction with a reference initial virtual resource block, i. e. VRB=0, and the total size (defined in number of RBs) of the frequency band

can be used to determine the value

and

.

[116] In an example for which there is no interleaved mapping between VRB and PRB, VRB n is mapped to PRB n.

[117] FIG. 4B illustrates an example of how the VRB set 410 in FIG. 4A may be mapped to a set of PRBs 420 having the same number of RBs as the VRB set and for which there is an interleaved mapping between VRBs and PRBs. In PRB set 420, a subset of VRB 412 is distributed in RB packets of two RBs 422, 424, 426, 428. The specific packet distribution method is not described in detail here. In this example, VRBs are mapped to an equal number of PRBs. However, as will be seen from the examples below with respect to FIGS. 5, 6, 7, and 8, a VRB set may be mapped to a PRB set that is part of another PRB set, ie, the active BWP. In such cases, the representation of FIG. 4B may be considered as an intermediate step in the VRB to PRB mapping, such as shown in FIG. 7 and 8.

можно принять равным количеству ресурсных блоков в начальной BWP DL. В некоторых вариантах осуществления один и тот же запланированный PDSCH выделен для группы UE в обеспечение эффективного использования спектра. Это означает, что каждая группа UE будет обращаться к одним и тем же ресурсным элементам (RE - resource element) для PDSCH. Другими словами, все UE в группе должны иметь одинаковую интерпретацию полей DCI, особенно поля выделения ресурсов частотной области, которое включает в себя RIV, независимо от активной BWP DL данного UE. Если бы размер DCI должен был быть определен по значению, которое не является общим для всех UE, например, чем-то отличным от начальной BWP, для UE с различными активными BWP было бы трудно интерпретировать поле выделения ресурсов частотной области в DCI. Результатом может быть то, что: интерпретированное частотное расположение PDSCH будет в пределах диапазона частот активной BWP каждого UE в группе UE; и все UE в группе UE будут интерпретировать DCI таким образом, чтобы они все получали одно и то же частотное расположение PDSCH.[118] In some embodiments, the DCI is sent in a common search space, and the DCI may be for more than one UE. If DCI is supposed to be decoded by a UE group, the UE group should have the same understanding of the DCI content. The DCI received by all UEs in the group is one DCI having a payload size. Therefore, it would be useful to have a total payload size that is known to all UEs. This is one reason why the payload size in DCI format 0_0/1_0 (backup DCI) can be determined based on the initial part of the downlink bandwidth (initial BWP DL) which is the same for all UEs accessing the network. This means, for example, that the size

can be taken equal to the number of resource blocks in the initial BWP DL. In some embodiments, the same scheduled PDSCH is allocated to a group of UEs to ensure efficient spectrum use. This means that each group of UEs will access the same resource elements (RE - resource element) for the PDSCH. In other words, all UEs in a group must have the same interpretation of the DCI fields, especially the frequency domain resource allocation field that includes the RIV, regardless of the UE's active BWP DL. If the DCI size were to be determined by a value that is not common to all UEs, such as something other than the initial BWP, it would be difficult for UEs with different active BWPs to interpret the frequency domain resource allocation field in the DCI. The result may be that: the interpreted PDSCH frequency location will be within the active BWP frequency band of each UE in the UE group; and all UEs in the UE group will interpret the DCI such that they all receive the same PDSCH frequency location.

[119] To allocate a frequency domain resource, when a spare DCI (DCI format 1_0 or 0_0) is decoded in a common search space, a reference RB (when interleaved mapping is not used) or a reference RB packet (when interleaved mapping is used) is used to determine the initial physical resource block of the scheduled resource for data transfer. For example, for a non-interleaved VRB-PRB mapping, virtual resource block n is mapped to physical resource block n+n_reference_RB. Whereas, in the case of interleaved VRB to PRB mapping, virtual resource block bundle j is mapped to physical resource block bundle f(j)+j_reference_RB_bundle . The size of the BWP used for interleaving is the bandwidth size of the reference PRB, defined herein as X. The RB packet size is fixed. Two non-limiting examples of RB packet size are 2 RB or 4 RB.

[120] For a common scheduled resource for multiple UEs, the reference RB or reference burst RB has the same physical frequency location for the group for the UE. However, a reference RB or a reference burst RB may have a different PRB index or burst index PRB in the active BWP of each UE in the UE group because different UEs may have different size active BWPs occurring in different initial RBs. This can be seen, for example, in Fig. 5 in active BWPs UE1, UE2 and UE3. The UEs must have at least the overlap of physical frequency locations equivalent to the size of the shared scheduling resource.

[121] Various aspects of the present invention each provide alternative choices for a reference RB to be used when mapping a VRB to a PRB. In the first embodiment, the reference RB is selected as the lowest resource element group (REG) of the PDCCH where the standby DCI (DCI format 0_0 or 1_0) has been decoded by the UE. In the second embodiment, the reference RB is selected as the lowest numbered PRB in the CORESET where the standby DCI (DCI format 0_0 or 1_0) has been decoded by the UE. In the third embodiment, the reference RB is selected as the PRB with the lowest configured CORESET number with the lowest CORESET ID in the active BWP. In the fourth embodiment, the reference RB is selected as the PRB with the lowest number of the original BWP DL (or CORESET #0). In the fifth embodiment, the reference RB is selected as the PRB with the lowest configured BWP number with the lowest BWP ID. In the sixth embodiment, the reference RB is selected as the lowest numbered PRB of the default BWP. In the seventh embodiment, the reference RB is a PRB configured by higher layer signaling.

[122] The following is a more detailed description of the first to seventh embodiments described above related to the selection of a reference RB to be used for mapping from virtual resource blocks to physical ones.

First Embodiment

[123] For non-interleaved VRB-PRB mapping, the virtual resource blockn mapped to a physical resource blockn, except when the reserved DCI is decoded in a common search space, in which case case virtual resource blockn displayed on physical resource blockn+n _{REG ,}where is the physical resource blockn _REG corresponds to the smallest REG of the PDCCH where the standby DCI has been decoded by the UE.

Second Embodiment

, где физический ресурсный блок

- это физический ресурсный блок с наименьшим номером в наборе ресурсов управления, где резервная DCI была декодирована посредством UE. [124] For non-interleaved VRB-PRB mapping, the virtual resource blockn mapped to a physical resource blockn, except when the standby DCI is decodedincommon search space, in which case the virtual resource blockn mapped to a physical resource block

, where the physical resource block

is a physical resource block with the lowest number in the control resource set where the standby DCI has been decoded by the UE.

Third Embodiment

, где физический ресурсный блок

- это физический ресурсный блок с наименьшим номером в наборе ресурсов управления с наименьшим ID, сконфигурированным в активной части полосы пропускания. [125] For non-interleaved VRB-PRB mapping, the virtual resource blockn mapped to a physical resource blockn, except when the standby DCI is decodedincommon search space, in which case the virtual resource blockn mapped to a physical resource block

, where the physical resource block

is the physical resource block with the smallest the number in the control resource set with the lowest ID configured in the active portion of the bandwidth.

Fourth Embodiment

, где физический ресурсный блок

соответствует тому же общему ресурсному блоку, что и физический ресурсный блок 0 начальной части полосы пропускания DL.[126] For non-interleaved VRB-PRB mapping, the virtual resource blockn displayed per physical resource blockn, with the exception of case where the reserved DCI is decoded in the common search space, in which case the virtual resource blockn mapped to a physical resource block

, where the physical resource block

corresponds to the same common resource block as the physical resource block 0 of the initial portion of the DL bandwidth.

Fifth Embodiment

, где физический ресурсный блок

соответствует тому же общему ресурсному блоку, что и физический ресурсный блок 0 части полосы пропускания, сконфигурированной с наименьшим ID BWP. [127] For non-interleaved VRB-PRB mapping, virtual resource block n is mapped to physical resource block n , except when the standby DCI is decoded in a common search space, in which case virtual resource block n is mapped to physical resource block

, where the physical resource block

corresponds to the same common resource block as physical resource block 0 of the bandwidth portion configured with the lowest BWP ID.

Sixth Embodiment

, где физический ресурсный блок

соответствует тому же общему ресурсному блоку, что и физический ресурсный блок 0 части полосы пропускания DL по умолчанию. [128] For non-interleaved VRB-PRB mapping, virtual resource block n is mapped to physical resource block n , except when the standby DCI is decoded in a common search space, in which case virtual resource block n is mapped to physical resource block

, where the physical resource block

corresponds to the same common resource block as physical resource block 0 of the default DL bandwidth portion.

Seventh Embodiment

, где

конфигурируется посредством сигнализации более высокого уровня. [129] A PRB configured for the UE by higher layer signaling. For non-interleaved VRB-PRB mapping, virtual resource blockn displayed on physical resource blockn, except for the case when the standby DCI is decoded in the common search space, in which case the virtual resource blockn mapped to a physical resource block

, where

configurable via higher level signaling.

[130] Various aspects of the present invention each provide alternative choices for the RB reference burst to be used in mapping VRB to PRB interleaved. In the eighth embodiment, the reference RB burst is selected as the RB burst that contains the reference RB of any of the first to seventh embodiments described above. In the ninth embodiment, the reference RB burst is selected as the RB burst that contains the lowest PDCCH Resource Element Group (REG) where the standby DCI (DCI format 0_0 or 1_0) has been decoded by the UE. In the tenth embodiment, the reference RB burst is selected as the RB burst that contains the lowest numbered PRB in the CORESET where the standby DCI (DCI format 0_0 or 1_0) has been decoded by the UE. In the eleventh embodiment, the reference RB packet is selected as the RB packet that contains the lowest configured CORESET number PRB with the lowest CORESET ID in the active BWP. In the twelfth embodiment, the reference RB packet is selected as the RB packet that contains the PRB with the lowest number of the original BWP DL (or CORESET #0). In the thirteenth embodiment, the reference RB packet is selected as the RB packet that contains the PRB with the lowest configured BWP number with the lowest BWP ID. In the fourteenth embodiment, the reference RB packet is selected as the RB packet that contains the lowest numbered PRB of the default BWP. In the fifteenth embodiment, the reference RB burst is an RB burst configured by higher layer signaling.

[131] The following is a more detailed description of the ninth to fifteenth embodiments described above related to the selection of a reference RB to be used for mapping from virtual resource blocks to physical ones.

Ninth Embodiment

, и пакет

виртуальных ресурсных блоков отображается на пакет

физических ресурсных блоков, где пакет

физических ресурсных блоков содержит самый низкий REG из PDCCH, где резервная DCI была декодирована посредством UE. [132] For interleaved VRB-PRB mapping, the mapping process is defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE shall accept

, and package

virtual resource blocks mapped per package

physical resource blocks where the package

physical resource blocks contains the lowest REG of the PDCCH where the reserved DCI has been decoded by the UE.

Tenth Embodiment

, и пакет

виртуальных ресурсных блоков отображается на пакет

физических ресурсных блоков, где пакет физических ресурсных блоков

содержит физический ресурсный блок с наименьшим номером в наборе ресурсов управления, где резервная DCI была декодирована посредством UE. [133] For interleaved VRB-PRB mapping, the mapping process is defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE shall accept

, and package

virtual resource blocks mapped per package

physical resource blocks, where the package of physical resource blocks

contains the lowest numbered physical resource block in the control resource set where the reserved DCI has been decoded by the UE.

Eleventh Embodiment

, и пакет

виртуальных ресурсных блоков отображается на пакет

физических ресурсных блоков, где пакет

физических ресурсных блоков содержит физический ресурсный блок с наименьшим номером в наборе ресурса управления с самым низким ID, сконфигурированным в активной части полосы пропускания.[134] For interleaved VRB-PRB mapping, the mapping process is defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE shall accept

, and package

virtual resource blocks mapped per package

physical resource blocks where the package

physical resource blocks contains the lowest numbered physical resource block in the control resource set with the lowest ID configured in the active portion of the bandwidth.

Twelfth Embodiment

, и пакет

виртуальных ресурсных блоков отображается на пакет

физических ресурсных блоков, где пакет

физических ресурсных блоков содержит физический ресурсный блок 0 начальной части полосы пропускания DL. [135] For interleaved VRB-PRB mapping, the mapping process is defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE shall accept

, and package

virtual resource blocks mapped per package

physical resource blocks where the package

physical resource blocks contains the physical resource block 0 of the initial portion of the DL bandwidth.

Thirteenth Embodiment

, пакет

виртуальных ресурсных блоков отображается на пакет

+

физических ресурсных блоков, где пакет

физических ресурсных блоков содержит физический ресурсный блок 0 части полосы пропускания, сконфигурированной с самым маленьким ID BWP.[136] For interleaved VRB-PRB mapping, the mapping process is defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE shall accept

, package

virtual resource blocks mapped per package

+

physical resource blocks where the package

physical resource blocks contains the physical resource block 0 of the bandwidth portion configured with the smallest BWP ID.

Fourteenth Embodiment

, и пакет

виртуальных ресурсных блоков отображается на пакет

физических ресурсных блоков, где пакет

физических ресурсных блоков содержит физический ресурсный блок 0 части полосы пропускания DL по умолчанию. [137] For interleaved VRB-PRB mapping, the mapping process is defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE shall accept

, and package

virtual resource blocks mapped per package

physical resource blocks where the package

physical resource blocks contains a physical resource block 0 part of the DL bandwidth by default.

Fifteenth Embodiment

, и пакет

виртуальных ресурсных блоков отображается на пакет

физических ресурсных блоков, где пакет

физических ресурсных блоков сконфигурирован посредством сигнализации более высокого уровня .[138] For interleaved VRB-PRB mapping, the mapping process is defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE shall accept

, and package

virtual resource blocks mapped per package

physical resource blocks where the package

The physical resource blocks are configured through higher layer signaling.

[139] In some embodiments, for example, when using resource allocation type 1, when the standby DCI (DCI format 1_0 or 0_0) is decoded in the common search space, the size (X) of the reference RB is used to determine the BWP size. The reference PRB bandwidth is used to calculate the RIV or map the VRB to the PRB, or both. In some embodiments, the first dimension (X1) of the reference RB is used to calculate the RIV, and the second dimension (X2) of the reference RB is used to map the VRB to the PRB.

[140] The bandwidth size (X) of the reference PRB may be the same for a group of UEs if the entire group of UEs is provided with group information via a standby DCI.

[141] Each of the various aspects of the present disclosure provides alternative choices for the size (X) of the PRB that should be used to calculate RIV or map VRB to PRB, or both. In the first embodiment, the size (X) of the PRB is chosen to be equal to the size of the original BWP DL (ie, the size of CORESET #0). In the second embodiment, the size (X) of the PRB is chosen to be the size of the CORESET frequency where the standby DCI has been decoded by the UE. The CORESET frequency size refers to the number of PRBs from the lowest numbered PRB in CORESET to the highest numbered PRB in CORESET. In the third embodiment, the size (X) of the PRB is chosen to be equal to the frequency size of the configured CORESET with the smallest CORESET ID in the active BWP. In the fourth embodiment, the size (X) of the PRB is chosen to be the size of the configured BWP with the smallest BWP ID. In the fifth embodiment, the size (X) of the PRB is chosen to be equal to the default BWP size. In the sixth embodiment, the PRB size (X) is configured by higher layer signaling. In some embodiments in which the first dimension (X1) of the reference RB group is used to calculate the RIV and the second dimension (X2) of the reference RB band is used to map the VRB to the PRB, any of the first through sixth embodiments described above may be used for the first dimension (X1) of the RB strip or the second dimension (X2) of the RB strip, or both.

[142] The following is a more detailed description of the first to sixth embodiments described above, related to the selection of the PRB size to be used to calculate RIV or map virtual resource blocks to physical ones. Any of the first through fifteenth embodiments for selecting the reference RB to be used in the VRB-to-PRB mapping may be combined with the first through sixth embodiments for selecting the PRB band size.

First Embodiment

[143] For calculating RIV or mapping VRB to PRB, the size of the BWP is equal to the number of resource blocks of the original BWP DL. Optionally, for interleaved VRB to PRB mapping, the mapping process is further defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE should accept the packet size L=2.

Second Embodiment

[144] For RIV calculation or VRB to PRB mapping, the BWP size is equal to the number of resource blocks from the lowest numbered resource block to the highest numbered resource block of the control resource set where the standby DCI was decoded by the UE. Optionally, for interleaved VRB to PRB mapping, the mapping process is further defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE should accept the packet size L=2.

Third Embodiment

[145] For RIV calculation or VRB-to-PRB mapping, the BWP size is equal to the number of resource blocks from the smallest number of resource blocks to the highest number of resource blocks in the lowest ID resource set configured in the active bandwidth portion. Optionally, for interleaved VRB to PRB mapping, the mapping process is further defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE should accept the packet size L=2.

Fourth Embodiment

[146] For RIV calculation or VRB-to-PRB mapping, the BWP size is equal to the number of resource blocks in the bandwidth portion configured with the smallest BWP ID. Optionally, for interleaved VRB to PRB mapping, the mapping process is further defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE should accept the packet size L=2.

Fifth Embodiment

[147] To calculate RIV or map VRB to PRB, the BWP size is equal to the number of resource blocks in the default bandwidth part. Optionally, for interleaved VRB to PRB mapping, the mapping process is further defined in terms of resource block packets. If the standby DCI is decoded in the common search space, the UE should accept the packet size L=2.

Sixth Embodiment

[148] For RIV calculation or VRB to PRB mapping, the BWP size is equal to the number of resource blocks configured by higher layer signaling. Optionally, for interleaved VRB to PRB mapping, the mapping process is further defined in terms of resource block bursts. If the standby DCI is decoded in the common search space, the UE should accept the packet size L=2.

[149] FIG. 5, 6, 7, and 8 include examples of how mapping can be performed from virtual resource blocks (VRBs) to physical resource blocks (PRBs). The base station is responsible for allocating the VRB and transmitting the DCI, which notifies the UE or group of UEs of the allocated resources available to the UEs or groups of UEs. The UE or a group of UEs receive the DCI and, after decoding, access the allocated resource to receive data in the case of PDSCH, or transmit the data back to the base station in the case of PUSCH. These four figures illustrate the VRBs that can be considered to be processed at the base station and the PRBs in the respective active portions of the bandwidth (BWP) for each of the three respective UEs.

[150] FIG. 5 illustrates an example of mapping a VRB set to three different PRB sets, one PRB set for each of the three UEs. In this example, there is no interleaved mapping within the mapping from VRB to PRB. The VRB set 510 with the VRB subset 512 scheduled for data transmission is essentially the same as the VRB set in FIG. 4A. Data transmission can be either for uplink (PUSCH) or downlink (PDSCH). Each set of PRBs 520, 530, 540 corresponds to an active portion of the bandwidth for different respective UEs. Each of the PRB sets has a corresponding number of PRBs. On the example of Fig. 5 number of PRBs, i.e. BWP size is different in each active BWP. More generally, it should be understood that the number of PRBs in a respective UE BWP may be UE specific. The first PRB in each set of PRBs 520, 530, 540 has an initial PRB=0. All three sets of PRBs 520, 530, 540 have the same reference PRB with respect to each other, but this reference PRB is in a different PRB in the active BWP with respect to PRB=0. Thus, it should be understood that the reference PRB is the same physical frequency location for all three UEs. In all three sets of PRBs 520, 530, 540, the set of PRBs 522, 532, 542 that are allocated for a particular transmission 510 fall into the active BWP of each respective UE.

[151] In the first set of PRBs 520, the set of PRBs 524 corresponding to the set of VRBs 514 refers to the active BWP of UE1. In the third set of PRBs 540, the set of PRBs 544 corresponding to the set of VRBs 514 refers to the active BWP UE3. In the second set of PRBs 530, the set of PRBs 534 that correspond to the set of VRBs 514 are outside the active BWP of UE2. Although the set of PRBs 534 may go beyond the active BWP in the case of UE2, it should be understood that this is only because the base station serving the UE, or more generally the control network, is the one that ultimately allocates the size of the active The BWP for the UE determines the size of the set of VRBs 514 and the size of the scheduled VRBs 512. As a result, the base station is smart enough not to schedule or transmit information to any given UE it serves outside of the active BWP that the base station has also allocated.

[152] FIG. 6 illustrates another example of mapping a VRB set to three different PRB sets, one PRB set for each of the three UEs. In this example, there is no interleaved mapping within the mapping from VRB to PRB. In this example, the VRB subcarrier spacing configuration is not the same as the PRB subcarrier spacing configuration. It can be seen that the height of the respective PRBs in the PRB sets 620, 630, 640 is approximately twice the height of the VRBs in the VRB set 610. This may, for example, represent a wider subcarrier spacing of individual PRBs than individual VRBs. A set of VRBs 610 having a subset of VRBs 612 scheduled for data transmission is essentially the same as the set of VRBs in FIG. 4A. The data transmission may be for uplink or downlink. Each set of PRBs 620, 630, 640 corresponds to an active portion of the bandwidth for a different corresponding UE. Each of the PRB sets has a corresponding number of PRBs. In the example in FIG. 6, the number of PRBs is different in each active BWP. More generally, it should be understood that the number of PRBs in a respective UE BWP may be UE specific. The first PRB in each set of PRBs 620, 630, 640 has an initial PRB=0. All three sets of PRBs 620, 630, 640 have the same reference PRB relative to each other, but this reference PRB is in a different PRB in the active BWP with respect to PRB=0. Therefore, it should be understood that the reference PRB is the same physical frequency location for all three UEs. In all three sets of PRBs 620, 630, 640, the set of PRBs 622, 632, 642 that are allocated to a particular transmission 610 fall into the active BWP of each respective UE.

[153] In the first set of PRBs 620, the set of PRBs 624 that correspond to the set of VRBs 614 fall into the active BWP of UE1. In the third set of PRBs 640, the set of PRBs 644 that correspond to the VRBs 614 fall into the active BWP UE3. In the second set of PRBs 630, the set of PRBs 634 that correspond to the set of VRBs 614 is outside the active BWP of UE2. Although the set of PRBs 634 may go beyond the active BWP in the case of UE2, it should be understood that this is only because the base station serving the UE, or more generally the control network, is the one that ultimately allocates the active BWP size. The BWP for the UE determines the size of the VRB set 614 and the size of the scheduled VRBs 612. As a result, the base station is smart enough not to schedule or transmit information to any given UE it serves outside of the active BWP that the base station has also assigned.

[154] FIG. 7 illustrates another example of mapping a VRB set to three different PRB sets, one PRB set for each of the three UEs. In this example, there is an interleaved mapping in the mapping cradles from VRB to PRB. A set of VRBs 710 having a subset of VRBs 712 scheduled for data transmission is interleaved within the VRB to PRB mapping, as can be seen at 715. The data transmission may be for uplink or downlink. A subset of VRBs 712 scheduled for data transmission may be mapped to RB burst sets of 2 RBs 716, 717, 718, and 719, which is essentially the same as in FIG. 4B. Each set of PRBs 720, 730, 740 corresponds to an active portion of the bandwidth for a different corresponding UE. Each of the PRB sets has a corresponding number of PRBs. In the example in FIG. 7, the number of PRBs is different in each active BWP. More generally, it should be understood that the number of PRBs in a corresponding BWP of a UE may be specific to the UE. The first PRB in each set of PRBs 720, 730, 740 has an initial PRB=0. All three sets of PRBs 720, 730, 740 have the same reference PRB relative to each other, but this reference PRB is in a different PRB in the active BWP with respect to PRB=0. The grid that is used to position the PRB packets can be configured in the system in a fixed manner, and the location of the reference PRB will take place within the packet, respectively. Therefore, the reference PRB may or may not be the first PRB in the PRB burst. In the example in FIG. 7, the reference PRB in each of the active BWPs is the second PRB in a burst of 2 PRBs. Again, it should be understood that the reference PRB, and more generally the reference PRB burst, is the same physical frequency location for all three UEs. In all three sets of PRBs 720, 730, 740, interleaved PRB bursts (e.g., 726, 727, 728, 729 in 720) that correspond to interleaved VRB bursts (716, 717, 718, 719 in 715) fall within the active BWP of each corresponding UE.

[155] In the first set of PRBs 720, a set of PRBs 724 that correspond to a set of VRBs 714 fall into the active BWP of UE1. In the third set of PRBs 740, a set of PRBs 744 that correspond to a set of VRBs 714 fall into the active BWP of UE3. In the second set of PRBs 730, the set of PRBs 734 that correspond to the set of VRBs 714 is outside the active BWP of UE2. Although the set of PRBs 734 may go beyond the active BWP in the case of UE2, it should be understood that this is only because the base station serving the UE, or more generally the control network, is the one that ultimately allocates the active BWP size. BWP for the UE, determines the size of the VRB set 714, determines the interleaved mapping used, and the size of the packets and the size of the scheduled VRBs 712. an active BWP that the base station has also allocated.

[156] FIG. 8 illustrates another example of mapping a VRB set to three different PRB sets, one PRB set for each of the three UEs. In this example, there is an interleaved mapping within the mapping from VRB to PRB. In this example, the VRB subcarrier diversity configuration is not the same as the PRB subcarrier diversity configuration. It can be seen that the height of the respective PRBs in the PRB sets 820, 830, 840 is approximately twice the height of the VRBs in the VRB set 810. This may, for example, represent a wider subcarrier spacing of individual PRBs than individual VRBs. A set of VRBs 810 having a subset of VRBs 812 scheduled for data transmission is interleaved within the VRB to PRB mapping, as can be seen at 815. The data transmission may be for uplink or downlink. A subset of VRBs 812 scheduled for data transmission may be configured to be displayed in RB burst sets of 2 RBs 816, 817, and 818, which is essentially the same as in FIG. 4B. Each set of PRBs 820, 830, 840 corresponds to an active portion of the bandwidth for another corresponding UE. Each of the PRB sets has a corresponding number of PRBs. In the example in FIG. 8, the number of PRBs is different in each active BWP. More generally, it should be understood that the number of PRBs in a corresponding BWP of a UE may be specific to the UE. The first PRB in each set of PRBs 820, 830, 840 has an initial PRB=0. All three sets of PRBs 820, 830, 840 have the same reference PRB relative to each other, but this reference PRB is in a different PRB in the active BWP with respect to PRB=0. The grid that is used to position the PRB packets can be configured in the system in a fixed manner, and the location of the reference PRB will take place within the packet, respectively. Therefore, the reference PRB may or may not be the first PRB in the PRB burst. In the example in FIG. The 8 reference PRB in each of the active BWPs is the second PRB of the 2 PRB burst. Again, it should be understood that the reference PRB, and more generally the reference PRB burst, is the same physical frequency location for all three UEs. In all three sets of PRBs 820, 830, 840, interleaved PRB packets (eg, 826, 827, 828 in 820) that correspond to interleaved VRB packets 816, 817, 818 in 815 fall into the active BWP of each respective UE.

[157] In the first set of PRBs 820, a set of PRBs 824 that correspond to a set of VRBs 814 fall into the active BWP of UE1. In the third set of PRBs 840, the set of PRBs 844 that correspond to the VRBs 814 fall into the active BWP UE3. In the second set of PRBs 830, the set of PRBs 834 that correspond to the set of VRBs 814 is outside the active BWP of UE2. Although the set of PRBs 834 may go beyond the active BWP in the case of UE2, it should be understood that this is only because the base station serving the UE, or more generally the control network, is the one that ultimately allocates the size of the active BWP for the UE, determines the size of the VRB 814 set, determines the interleaved mapping used, and the size of the packets and the size of the scheduled VRBs 812. an active BWP that the base station has also allocated.

[158] FIG. 9 illustrates a flowchart describing an exemplary method 900 for wireless communication in accordance with an embodiment of the disclosure. The method includes a user equipment (UE) receiving 910 downlink control information (DCI) on a physical downlink control channel (PDCCH) in a first part of a bandwidth (BWP).

[159] Another step 920 includes the following: the UE determines an initial resource block (RB) for transmitting data allocated by the DCI based on the value of the frequency domain resource allocation field in the DCI, the reference RB, and the reference size of the second BWP.

[160] The reference RB may be at least one of:

the Resource Element Group (REG) with the lowest PDCCH number, where the DCI has been decoded by the UE;

the lowest numbered physical resource block (PRB) of the control resource set (CORESET) where the DCI has been decoded by the UE;

the PRB with the lowest configured CORESET number with the lowest CORESET ID in the active BWP;

PRB with the lowest number of the original BWP DL used by the UE;

the PRB with the lowest configured BWP number with the lowest BWP ID;

PRB with the lowest default BWP number; as well as

PRB configured by higher layer signaling.

[161] The reference dimension of the second BWP is the number of RBs equal to at least one of:

the number of RBs of the initial BWP DL;

a number of RBs defining a control resource set (CORESET) where the DCI has been decoded by the UE;

the number of RBs defining the configured CORESET with the smallest CORESET ID in the active BWP;

a number of RBs defining the size of the configured BWP with the smallest BWP ID;

the number of RBs defining the default BWP size; as well as

the number of RBs configured by higher layer signaling.

[162] An optional step 930 may include the following: The UE determines the length of the contiguous allocated RBs for data transmission based on the value of the frequency domain resource allocation field in the DCI and the reference size of the second BWP.

[163] Once a time-frequency resource is established, defined by at least an initial RB and a length of contiguous allocated RBs, the UE may either 940 transmit a data transmission on a PUSCH example or receive a data transmission on a PDSCH example, in the established time-frequency resource.

[164] In some embodiments, a DCI is associated with a group of UEs, and a data transmission dedicated by the DCI is a downlink data transmission allocated on the same time-frequency resource for all UEs in the UE group.

[165] In some embodiments, the first BWP is the active BWP and the second BWP is the initial downlink (DL) BWP.

[166] In some embodiments, RBs that are allocated for data transmission are allocated across the first BWP based on an interleaved mapping of virtual RB packets to interleaved physical RB packets. In such a scenario, the initial RB is a virtual initial RB and the reference RB is a virtual reference RB.

[167] In some embodiments, the UE also determines interleaved physical RB bursts for data transmission based on at least a virtual initial RB, an interleaved mapping, and a reference physical RB burst. In such a scenario, transmitting or receiving a data transmission includes transmitting or receiving a data transmission allocated in a time-frequency resource that is at least partially determined by interleaved bursts of physical RBs.

[168] In some embodiments, the virtual start RB determines the start of the length of the contiguously allocated virtual RBs, and determining interleaved physical RB bursts includes determining interleaved physical RB bursts further based on the length of the contiguously allocated virtual RBs.

[169] FIG. 10 illustrates a flowchart describing an exemplary method 1000 for wireless communication according to an embodiment of the disclosure. The method includes transmitting 1010 downlink control information (DCI) on a physical downlink control channel (PDCCH) in a first portion of a bandwidth (BWP). The DCI includes a frequency domain resource allocation field having a value for determining an initial resource block (RB) for a data transmission to be allocated by the DCI, the initial RB being determined together with the reference RB and the reference size of the second BWP. An additional step 1020 includes transmitting or receiving a data transmission between a base station and a user equipment (UE).

[170] In some embodiments, the value of the frequency domain resource allocation field further determines the length of contiguous allocated RBs for data transmission. Transmitting or receiving a data transmission at 1020 includes transmitting or receiving a data transmission allocated in a time-frequency resource defined by at least an initial RB and a length of contiguous allocated RBs.

[171] In some embodiments, RBs that are allocated for data transmission are allocated across the first BWP based on an interleaved mapping of virtual RB packets to interleaved physical RB packets. In such a scenario, the initial RB is a virtual initial RB and the reference RB is a virtual reference RB.

[172] In some embodiments, the interleaved bursts of physical RBs for data transmission are determined by a virtual initial RB, an interleaved mapping, a length of contiguously assigned virtual RBs, and a reference burst of physical RBs. In such a scenario, transmitting or receiving a data transmission at 1020 includes transmitting or receiving a data transmission allocated in a time-frequency resource that is at least partially determined by interleaved bursts of physical RBs.

[173] FIG. 11 illustrates a flowchart describing another exemplary method 1100 for wireless communication in accordance with an embodiment of the disclosure. The method includes a step in which the UE receives 1110 downlink control (DCI) information on a physical downlink control channel (PDCCH) in a downlink (DL) active bandwidth (BWP). The DCI is for data transmission scheduling, and the DCI includes a frequency domain resource allocation field.

[174] Another step 1120 includes receiving, by the UE, data transmission in a time-frequency resource determined by at least an initial resource block (RB) and a length of contiguous allocated RBs. The initial RB is based on: the value of the frequency domain resource allocation field in the DCI, the reference RB, and the number of RBs of the first control resource set (CORESET). The length of the adjacent allocated RBs is based on: the value of the frequency domain resource allocation field in the DCI and the number of RBs of the first CORESET.

[175] In some embodiments, receiving a data transmission includes receiving a data transmission on a time-frequency resource determined by interleaved physical RB bursts, the interleaved physical RB bursts being based on: virtual start RB, length of contiguously allocated virtual RBs, interleaved mapping and a reference packet of physical RBs.

[176] In some embodiments, the reference RB is the lowest numbered physical resource block (PRB) in the second CORESET, where the second CORESET is a CORESET where the DCI has been decoded by the UE.

, где PRB

является PRB с наименьшим номером в CORESET, где резервная DCI была декодирована посредством UE. [177] An additional step 1130, which is optional, includes determining, by the UE, that: the DCI is a standby DCI for non-interleaved VRB-to-PRB-mapped data transmission; the standby DCI is decoded in the common search space; and for data transfer virtual RB n is mapped to PRB

, where PRB

is the lowest numbered PRB in CORESET where the standby DCI has been decoded by the UE.

[178] In some embodiments, the active BWP DL includes allocating RBs for data transmission based on an interleaved mapping of virtual RB packets to interleaved physical RB packets, wherein the start RB is a virtual start RB, and the length of the contiguous allocated RBs is the length of the contiguous allocated virtual RBs, wherein the virtual start RB defines the start of the length of the adjacent allocated virtual RBs.

[179] In some embodiments, a Physical RB Reference Packet is a Physical RB Packet that contains the lowest numbered Physical Resource Block (PRB) in the second CORESET, where the second CORESET is a CORESET where the DCI has been decoded by the UE.

[180] In some embodiments, the implementation of the DCI is a backup DCI.

[181] In some embodiments, the first CORESET is associated with a CORESET identifier of "0".

[182] In some embodiments, the DCI is associated with a group of UEs, and the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time frequency resource for all UEs in the UE group.

[183] FIG. 12 illustrates a flowchart describing another exemplary method 1200 for wireless communication in accordance with an embodiment of the disclosure. Method 1200 includes: a device transmits 1210 downlink control information (DCI) on a physical downlink control channel (PDCCH) in a downlink (DL) active bandwidth (BWP). The DCI is for data transmission scheduling, and the DCI includes a frequency domain resource allocation field. The device may be a network access point such as, for example, a base station.

[184] Another step 1220 includes transmitting, by a device to a UE, data in a time-frequency resource determined by at least an initial resource block (RB) and a length of contiguous allocated RBs. The initial RB is based on: the value of the frequency domain resource allocation field in the DCI, the reference RB, and the number of RBs of the first control resource set (CORESET). The length of the adjacent allocated RBs is based on: the value of the frequency domain resource allocation field in the DCI and the number of RBs of the first CORESET.

[185] In some embodiments, the reference RB is the lowest numbered physical resource block (PRB) in the second CORESET, where the second CORESET is a CORESET where the DCI has been decoded by the UE.

[186] In some embodiments, the active BWP DL includes allocating RBs for data transmission based on an interleaved mapping of virtual RB packets to interleaved physical RB packets, wherein the start RB is a virtual start RB, and the length of contiguous allocated RBs is the length of contiguous allocated virtual RBs, wherein the virtual start RB defines the start of the length of the adjacent allocated virtual RBs.

[187] In some embodiments, the data transmission step includes transmitting a data transmission on a frequency-time resource determined by interleaved physical RB bursts, the interleaved physical RB bursts being based on: virtual start RB, length of contiguously allocated virtual RBs, interleaved mapping and a reference packet of physical RBs.

[188] In some embodiments, a Physical RB Reference Packet is a Physical RB Packet that contains the lowest numbered Physical Resource Block (PRB) in the second CORESET, where the second CORESET is a CORESET where the DCI has been decoded by the UE.

[189] In some embodiments, the implementation of the DCI is a backup DCI.

[190] In some embodiments, the first CORESET is associated with a CORESET identifier of "0".

[191] In some embodiments, the DCI is associated with a group of UEs, and the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time frequency resource for all UEs in the UE group.

[192] According to an aspect of the disclosure, a wireless communication method is provided. The method includes receiving, by a user equipment (UE), downlink control information (DCI) on a physical downlink control channel (PDCCH) in a first part of a bandwidth (BWP); determining, by the UE, an initial resource block (RB) for data transmission allocated by the DCI based on the value of the frequency domain resource allocation field in the DCI, the reference RB, and the reference size of the second BWP; and transmitting or receiving, by the UE, a data transmission.

[193] In some embodiments, the method further includes determining, by the UE, the length of the contiguous allocated RBs for data transmission based on the value of the frequency domain resource allocation field in the DCI and the reference size of the second BWP, where the transmission or reception of the data transmission is comprises transmitting or receiving a data transmission allocated in a time-frequency resource determined by at least an initial RB and a length of contiguous allocated RBs.

[194] In some embodiments, the DCI is associated with a group of UEs, and the data transmission allocated by the DCI is a downlink data transmission allocated in the same time frequency resource for all UEs in the UE group.

[195] In some embodiments, the first BWP is the active BWP and the second BWP is the initial downlink (DL) BWP.

[196] In some embodiments, the reference RB is at least one of: the lowest PDCCH number Resource Element Group (REG) where the DCI has been decoded by the UE; the lowest numbered physical resource block (PRB) of the control resource set (CORESET) where the DCI has been decoded by the UE; the PRB with the lowest configured CORESET number with the lowest CORESET ID in the active BWP; PRB with the lowest number of initial BWP DL used by the UE; the PRB with the lowest configured BWP number with the lowest BWP ID; PRB with the lowest default BWP number; and a PRB configured by higher layer signaling.

[197] In some embodiments, the reference size of the second BWP is a number of RBs equal to at least one of: the number of RBs of the original BWP DL; a number of RBs defining a control resource set (CORESET) in which the DCI has been decoded by the UE; the number of RBs defining the configured CORESET with the smallest CORESET ID in the active BWP; a number of RBs defining the size of the configured BWP with the smallest BWP ID; the number of RBs defining the default BWP size; and the number of RBs configured by higher layer signaling.

[198] In some embodiments, RBs allocated for data transmission are allocated across the first BWP based on an interleaved mapping of virtual RB packets to interleaved physical RB packets, with the initial RB being the virtual initial RB and the reference RB being the virtual reference RB.

[199] In some embodiments, the method further includes determining, by the UE, interleaved physical RB bursts for data transmission based on at least a virtual initial RB, an interleaved mapping, and a reference physical RB burst, wherein transmitting or receiving a data transmission comprises transmitting or receiving a data transmission allocated in a time-frequency resource that is at least partially determined by interleaved bursts of physical RBs.

[200] In some embodiments, the virtual start RB determines the start of the length of the contiguously allocated virtual RBs, and the interleaved physical RB burst determination comprises determining the interleaved physical RB bursts, further based on the length of the contiguously allocated virtual RBs.

[201] In some embodiments, the implementation of the DCI is a backup DCI.

[202] According to another aspect of the disclosure, a user equipment (UE) is provided, including: a processor and a computer-readable storage medium that stores computer-executable instructions. When executed by the processor, the computer-executable instructions cause the UE to: receive, by the user equipment (UE), downlink control information (DCI) on the physical downlink control channel (PDCCH) in the first part of the bandwidth (BWP); determine by the UE an initial resource block (RB) for data transmission allocated by the DCI based on the value of the frequency domain resource allocation field in the DCI, the reference RB, and the reference size of the second BWP; and transmit or receive, by the UE, a data transmission.

[203] In some embodiments, computer-executable instructions, when executed by the processor, further cause the UE to: determine, by the UE, the length of contiguous allocated RBs for data transmission based on the value of the frequency domain resource allocation field in the DCI and the second BWP reference size, wherein transmission or reception a data transmission comprises transmitting or receiving a data transmission allocated in a time-frequency resource determined by at least an initial RB and a length of contiguous allocated RBs.

[204] In some embodiments, a DCI is associated with a group of UEs, and a data transmission dedicated by the DCI is a downlink data transmission allocated on the same time frequency resource for all UEs in the UE group.

[205] In some embodiments, the first BWP is the active BWP and the second BWP is the initial downlink (DL) BWP.

[206] In some embodiments, the reference RB is at least one of: the lowest PDCCH number Resource Element Group (REG) where the DCI has been decoded by the UE; the lowest numbered physical resource block (PRB) of the control resource set (CORESET) where the DCI has been decoded by the UE; the PRB with the lowest configured CORESET number with the lowest CORESET ID in the active BWP; PRB with the lowest number of initial BWP DL used by the UE; the PRB with the lowest configured BWP number with the lowest BWP ID; PRB with the lowest default BWP number; and a PRB configured by higher layer signaling.

[207] In some embodiments, the reference size of the second BWP is a number of RBs equal to at least one of: the number of RBs of the initial BWP DL; a number of RBs defining a control resource set (CORESET) where the DCI has been decoded by the UE; the number of RBs defining the configured CORESET with the smallest CORESET ID in the active BWP; a number of RBs determining the size of the configured BWP with the smallest BWP ID; the number of RBs defining the default BWP size; and the number of RBs configured by higher layer signaling.

[208] In some embodiments, RBs allocated for data transmission are allocated across the first BWP based on an interleaved mapping of virtual RB packets to interleaved physical RB packets, with the initial RB being the virtual initial RB and the reference RB being the virtual reference RB.

[209] In some embodiments, computer-executable instructions, when executed by the processor, further cause the UE to: determine interleaved physical RB bursts for data transmission based on at least a virtual initial RB, an interleaved mapping, and a reference physical RB bursts, wherein transmitting or receiving a data transmission comprises transmitting or receiving a data transmission allocated in a time-frequency resource that is at least partially determined by interleaved bursts of physical RBs.

[210] In some embodiments, the virtual start RB determines the start of the length of the contiguously allocated virtual RBs, and the interleaved physical RB burst determination comprises determining the interleaved physical RB bursts, further based on the length of the contiguously allocated virtual RBs.

[211] In some embodiments, the implementation of the DCI is a backup DCI.

[212] In accordance with a further aspect of the disclosure, a wireless communication method is provided. The method includes: transmitting downlink control information (DCI) on a physical downlink control channel (PDCCH) in a first portion of a bandwidth (BWP), the DCI comprising a frequency domain resource allocation field having a value for determining an initial resource block (RB) for a data transmission to be allocated by the DCI, the initial RB being determined together with the reference RB and the reference size of the second BWP; and transmitting or receiving a data transmission between the base station and the user equipment (UE).

[213] In some embodiments, the value of the frequency domain resource allocation field further defines the length of the contiguous allocated RBs for data transmission, wherein the transmission or reception of a data transmission comprises transmitting or receiving a data transmission allocated in a time-frequency resource determined by at least initial RB and the length of adjacent allocated RBs.

[214] In some embodiments, RBs allocated for data transmission are allocated across the first BWP based on an interleaved mapping of virtual RB packets to interleaved physical RB packets, with the initial RB being the virtual initial RB and the reference RB being the virtual reference RB.

[215] In some embodiments, the interleaved bursts of physical RBs for data transmission are defined by a virtual initial RB, an interleaved mapping, a length of contiguously allocated virtual RBs, and a reference burst of physical RBs, wherein the transmission or reception of the data transmission comprises the transmission or reception of the data transmission allocated in a time-frequency resource determined at least in part by the interleaved bursts of physical RBs.

[216] In some embodiments, the VRBs have a different subcarrier spacing configuration than the PRBs.

[217] According to another aspect of the disclosure, an apparatus is provided, including a processor and a computer-readable storage medium that stores computer-executable instructions. When executed by the processor, computer-executable instructions cause the device to: transmit downlink control information (DCI) on a physical downlink control channel (PDCCH) in the first part of the bandwidth (BWP), wherein the DCI contains a frequency domain resource allocation field having a value for determining an initial resource block (RB) for a data transmission to be allocated by the DCI, the initial RB being determined together with the reference RB and the reference size of the second BWP; and transmit or receive a data transmission between the base station and the user equipment (UE).

[218] In some embodiments, the value of the frequency domain resource allocation field further defines the length of the contiguous allocated RBs for the data transmission, wherein the transmission or reception of a data transmission comprises transmitting or receiving a data transmission allocated in a time-frequency resource determined by at least initial RB and the length of adjacent allocated RBs.

[219] In some embodiments, RBs allocated for data transmission are allocated across the first BWP based on an interleaved mapping of virtual RB packets to interleaved physical RB packets, with the initial RB being the virtual initial RB and the reference RB being the virtual reference RB.

[220] In some embodiments, the interleaved bursts of physical RBs for data transmission are defined by a virtual initial RB, an interleaved mapping, a length of contiguously assigned virtual RBs, and a reference burst of physical RBs, wherein the transmission or reception of the data transmission comprises the transmission or reception of the data transmission allocated in a time-frequency resource determined at least in part by the interleaved bursts of physical RBs.

[221] In some embodiments, the VRBs have a different subcarrier spacing configuration than the PRBs.

[222] Although this invention has been described with reference to illustrative embodiments, this description is not intended to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention, will become apparent to those skilled in the art upon reference to the description. Therefore, the appended claims are intended to cover any such modifications or embodiments.

Claims (48)

1. A wireless communication method, comprising the steps of: receive, by the user equipment (UE), downlink control information (DCI) in the second set (CORESET) of control resources in the active part of the downlink (DL) bandwidth (BWP) within the carrier, and the DCI contains a frequency resource allocation field areas for indicating frequency resources allocated for data transmission within the active BWP DL; and receiving, by the UE, data transmission in the time-frequency resource based on the value of the frequency domain resource allocation field in the DCI, the number of resource blocks (RB) of the first CORESET, and the reference RB determined by the lowest-numbered physical resource block (PRB) in the second CORESET. 2. The method of claim 1, wherein the step of receiving a data transmission comprises receiving a data transmission in a frequency resource based on an initial PRB and a length of contiguous allocated PRBs, wherein the initial PRB is based on: a DCI frequency domain resource allocation field value, a reference RB, and a number RB in the first CORESET, and the length of the adjacent allocated PRBs is based on: the value of the frequency domain resource allocation field in the DCI and the number of RBs in the first CORESET. 3. The method according to claim 2, in which: DCI is a back-up DCI for data transmission with virtual RB (VRB) non-interleaved mapping on PRB, the standby DCI is decoded in the common search space, and for data transfer virtual RB n is mapped to PRB

, where PRB

is the lowest numbered PRB in CORESET where the standby DCI was decoded by the UE, and the second CORESET is a CORESET in which the standby DCI has been decoded by the UE and the reference RB is

. 4. The method according to any one of paragraphs. 1-3, in which the DCI is a backup DCI. 5. The method of claim 4, wherein the standby DCI has a DCI format of "1_0". 6. The method according to any one of paragraphs. 1-5, in which the first CORESET is associated with a CORESET ID of "0". 7. The method according to any one of paragraphs. 1-6, in which the DCI is associated with a group of UEs, and the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time frequency resource to all UEs in the UE group. 8. A wireless communication method, comprising the steps of: receive by the user equipment (UE) downlink control information (DCI) in the second set (CORESET) of control resources in the active part of the downlink (DL) bandwidth (BWP) within the carrier, and the DCI contains a frequency domain resource allocation field for indicating frequency resources allocated for data transmission within the active BWP DL, and wherein the active BWP DL comprises allocation of resource blocks (RB) for data transmission based on an interleaved mapping of virtual RB (VRB) packets to interleaved physical RB (PRB) packets; receiving, by the UE, a data transmission in the time-frequency resource based on the interleaved mapping, the value of the frequency domain resource allocation field, the number of RBs in the first CORESET, and the PRB reference burst in the second CORESET, the PRB reference burst containing the lowest numbered PRB in the second CORESET . 9. The method of claim 8, wherein the step of receiving a data transmission comprises receiving a data transmission in a frequency resource based on an initial VRB and a length of contiguous allocated VRBs, wherein the initial VRB is based on: a value of a frequency domain resource allocation field in the DCI and a number of RBs in the first CORESET, and the length of the adjacent allocated VRBs is based on: the value of the frequency domain resource allocation field in the DCI and the number of RBs in the first CORESET. 10. The method according to any one of paragraphs. 8, 9, in which the DCI is a backup DCI. 11. The method of claim 10, wherein the standby DCI has a DCI format of "1_0". 12. The method according to any one of paragraphs. 8-11, in which the first CORESET is associated with a CORESET ID of "0". 13. The method according to any one of paragraphs. 8-12, in which the DCI is associated with a group of UEs, and the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time frequency resource for all UEs in the UE group. 14. User equipment (UE), containing: CPU; and a computer-readable storage medium that stores computer-executable instructions that, when executed by the processor, cause the UE to perform the method in accordance with any one of claims. 1-13. 15. A wireless communication method, comprising the steps of: transmitting, by the base station, downlink control information (DCI) in a second downlink (DL) bandwidth active part (BWP) control resource set (CORESET) within a carrier, the DCI comprising a frequency domain resource allocation field for indicating frequency resources allocated for data transmission within the active BWP DL; and transmitting, by the base station, to the user equipment (UE) a data transmission in the frequency-time resource, based on the value of the frequency domain resource allocation field in the DCI, the number of resource blocks (RB) of the first CORESET, and the reference RB determined by the physical resource block (PRB) ) with the lowest number in the second CORESET. 16. The method of claim 15, wherein the step of transmitting the data comprises transmitting a data transmission in a frequency resource based on an initial PRB and a length of contiguous allocated PRBs, wherein the initial PRB is based on: a DCI frequency domain resource allocation field value, a reference RB, and a number of RBs. in the first CORESET, and the length of the adjacent allocated PRBs is based on: the value of the frequency domain resource allocation field in the DCI and the number of RBs in the first CORESET. 17. The method according to claim 16, in which: DCI is a back-up DCI for data transmission with virtual RB (VRB) non-interleaved mapping on PRB, the standby DCI is decoded in the common search space, for data transfer virtual RB n is mapped to PRB

, where PRB

is the lowest numbered PRB in CORESET where the standby DCI was decoded by the UE, and the second CORESET is a CORESET in which the standby DCI has been decoded by the UE and the reference RB is

. 18. The method according to any one of paragraphs. 15-17, in which the DCI is a backup DCI. 19. The method of claim 18, wherein the standby DCI has a DCI format of "1_0". 20. The method according to any one of paragraphs. 15-19, in which the first CORESET is associated with a CORESET ID of "0". 21. The method according to any one of paragraphs. 15-20, in which the DCI is associated with a group of UEs, and the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time frequency resource to all UEs in the UE group. 22. A wireless communication method, comprising the steps of: transmitting, by the base station, downlink control information (DCI) in a second downlink (DL) bandwidth active part (BWP) control resource set (CORESET) within a carrier, the DCI comprising a frequency domain resource allocation field for indicating frequency resources allocated for data transmission within the active BWP DL, and wherein the active BWP DL comprises an allocation of resource blocks (RB) for data transmission based on an interleaved mapping of virtual RB (VRB) packets to interleaved physical RB (PRB) packets; and transmitting, by the base station, to the user equipment (UE) a data transmission in the time-frequency resource based on the interleaved mapping, the value of the frequency domain resource allocation field, the number of RBs in the first CORESET, and the reference PRB burst in the second CORESET, the reference PRB packet comprising The lowest numbered PRB in the second CORESET. 23. The method of claim 22, wherein the step of transmitting data comprises transmitting a data transmission in a frequency resource based on an initial VRB and a length of contiguous allocated VRBs, wherein the initial VRB is based on: a value of a frequency domain resource allocation field in the DCI and a number of RBs in the first CORESET , and the length of the adjacent allocated VRBs is based on: the value of the frequency domain resource allocation field in the DCI and the number of RBs in the first CORESET. 24. The method according to any one of paragraphs. 22, 23, in which the DCI is the backup DCI. 25. The method of claim 24, wherein the standby DCI has a DCI format of "1_0". 26. The method according to any one of paragraphs. 22-25, in which the first CORESET is associated with a CORESET ID of "0". 27. The method according to any one of paragraphs. 22-26, in which the DCI is associated with a group of UEs, and the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time frequency resource to all UEs in the UE group. 28. Device, containing: CPU; a computer-readable storage medium that stores computer-executable instructions that, when executed by the processor, cause the device to perform the method of any one of claims. 15-27.

Images