Method and apparatus for downlink control information communication and interpretation

Abstract

A method and an apparatus for wireless communication are provided in which downlink control information (DCI) is transmitted in a physical downlink control channel (PDCCH) in a first bandwidth portion (BWP). The UE is responsible for determining a starting resource block (RB) for data transmission allocated by the DCI based on a value of a frequency domain resource allocation field in the DCI, a reference resource block (RB) and a reference size of a second BWP. The UE may then transmit the data transmission in the case of, for example, a PUSCH, or receive the data transmission in the case of, for example, a PDSCH.

Description

[0001] This application is a divisional application. The application number of the original application is 201980014587.2, and the original application date is April 1, 2019. The entire contents of the original application are incorporated into this application by reference.

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 652,490, filed on April 4, 2018, entitled “Method and Apparatus for Downlink Control Information Communication and Interpretation,” and U.S. Non-Provisional Patent Application No. 16 / 216,191, filed on December 11, 2018, entitled “Method and Apparatus for Downlink Control Information Communication and Interpretation,” the contents of which are incorporated herein by reference. Technical Field

[0003] The present invention generally relates to systems and methods for wireless communications, and in particular embodiments, to systems and methods for determining the location of transmission resources allocated in downlink control information (DCI). Background Art

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

[0005] Configuring communication devices with the same air interface parameters allows the communication devices to reliably identify, organize and use physical resources, such as time, frequency or time-frequency resources. Therefore, in current wireless communication systems, communication is usually performed according to a predefined configuration of the air interface.

[0006] However, modern wireless networks are increasingly used to support communications of various traffic types, which may have different characteristics and quality of service (QoS) requirements, such as latency, throughput, and simultaneous connections. Therefore, the different traffic types of modern wireless networks are not suitable for a universal air interface configuration.

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

[0008] An ED is configured with one or more bandwidth parts (BWPs) within the carrier bandwidth. Each BWP consists of multiple contiguous resource blocks (RBs) within the carrier. In some cases, only one configured BWP is active for an ED at a given time. In other cases, more than one configured BWP is active for an ED at the same time.

[0009] In each configured BWP of the ED, the ED is configured with multiple control resource sets (CORESETs), each CORESET being a set of physical time-frequency resources for possible transmission of a PDCCH. Multiple search spaces are configured and associated with each CORESET. Each search space associated with a CORESET corresponds to multiple resource subsets in the CORESET, each subset corresponding to a PDCCH candidate.

[0010] The ED reads the information in the DCI through a process called "blind decoding". The location of the PDCCH containing the DCI in the physical time-frequency transmission resources is not previously known to the ED. Therefore, the ED must "blindly" search for PDCCHs in a specified area of ​​the physical time-frequency resources (the above-mentioned resource subset in the search space) by repeatedly trying to decode the PDCCH candidates in the search space.

[0011] For each PDCCH candidate, the ED may need to try different decoding parameters to decode the DCI. For example, different payload sizes may be used to send the DCI. For a given PDCCH candidate, different DCI payload sizes may result in different encoding / decoding rates. The ED can only decode the candidate DCI if the ED uses the correct payload size. In practice, due to time and processing constraints, the ED cannot truly try an infinite number of different combinations of DCI payload sizes during blind decoding. For example, in cellular communications such as New Radio (NR), the ED may be limited to trying only a few (e.g., a total of four per time slot) different DCI payload sizes during blind decoding.

[0012] In some scenarios, an ED may be configured in an activated BWP of a carrier bandwidth to attempt to decode a DCI whose payload size is based on another bandwidth portion of the carrier bandwidth. However, in this case, the ED may not be aware of the content of the DCI or may misunderstand the content of the DCI because the DCI field whose size is based on the BWP (size1) needs to be interpreted to schedule data in another BWP (size2), where size2≠size1. Summary of the invention

[0013] Technical advantages are generally achieved through embodiments of the present disclosure, which describe systems and methods for determining the location of transmission resources allocated in downlink control information (DCI). Examples of technical benefits may include efficient resource utilization for common DCI and common data, because a group of UEs can access the same physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) location using the same DCI transmission.

[0014] According to one aspect of the present disclosure, a method for wireless communication is provided. The method includes: a user equipment (UE) receives downlink control information (DCI) in a physical downlink control channel (PDCCH) of an activated downlink (DL) bandwidth part (BWP), the DCI being used to schedule data transmission, the DCI including a frequency domain resource allocation field; and the UE receives the data transmission in a time-frequency resource defined by at least a starting resource block (RB) and a length of consecutively allocated RBs, the starting RB being based on: a value of the frequency domain resource allocation field in the DCI, a reference RB, and the number of RBs of a first control resource set (CORESET), and the length of the consecutively allocated RBs being based on: a value of the frequency domain resource allocation field in the DCI and the number of RBs of the first CORESET.

[0015] In some embodiments, the reference RB is a physical resource block (PRB) with the smallest number in a second CORESET, and the UE has decoded the DCI in the second CORESET.

[0016] In some embodiments, the method further comprises the UE determining that: the DCI is a fallback DCI for the data transmission with non-interleaved VRB to PRB mapping; the fallback DCI is decoded in a common search space; and for the data transmission, virtual RB n is mapped to in It is the PRB with the smallest number in the CORESET, and the UE decodes the fallback DCI in the CORESET.

[0017] In some embodiments, the activated DL BWP includes RB allocation for the data transmission, the RB allocation being based on an interleaving mapping of VRB bundles to interleaved PRB bundles, wherein the starting RB is a virtual starting RB, and the length of the consecutively allocated RBs is the length of the consecutively allocated virtual RBs, and wherein the virtual starting RB defines the start of the length of the consecutively allocated virtual RBs.

[0018] In some embodiments, receiving the data transmission includes receiving the data transmission in a time-frequency resource defined by the interleaved physical RB bundle, wherein the interleaved physical RB bundle is based on: the virtual starting RB, the length of the consecutively allocated virtual RBs, the interleaving mapping, and a reference physical RB bundle.

[0019] In some embodiments, the reference physical RB bundle is a physical RB bundle containing a smallest numbered physical resource block (PRB) in a second CORESET, and the UE has decoded the DCI in the second CORESET.

[0020] In some embodiments, the DCI is a fallback DCI.

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

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

[0023] According to another aspect of the present disclosure, a user equipment (UE) is provided, comprising a processor and a computer-readable medium having computer-executable instructions stored thereon. The instructions, when executed by the processor, cause the UE to: receive downlink control information (DCI) in a physical downlink control channel (PDCCH) of an activated downlink (DL) bandwidth part (BWP), the DCI being used to schedule data transmission, the DCI comprising a frequency domain resource allocation field; and receive the data transmission in a time-frequency resource defined by at least a starting resource block (RB) and a length of consecutively allocated RBs, the starting RB being based on: a value of the frequency domain resource allocation field in the DCI, a reference RB, and the number of RBs of a first control resource set (CORESET), and the length of the consecutively allocated RBs being based on: a value of the frequency domain resource allocation field in the DCI and the number of RBs of the first CORESET.

[0024] In some embodiments, the reference RB is a physical resource block (PRB) with the smallest number in a second CORESET, and the UE has decoded the DCI in the second CORESET.

[0025] In some embodiments, the computer executable instructions, when executed by the processor, cause the UE to determine: the DCI is a fallback DCI for the data transmission with non-interleaved VRB to PRB mapping; the fallback DCI is decoded in a common search space; and for the data transmission, virtual RB n is mapped to in It is the PRB with the smallest number in the CORESET, and the UE decodes the fallback DCI in the CORESET.

[0026] In some embodiments, the activated DL BWP includes RB allocation for the data transmission, the RB allocation being based on an interleaving mapping of virtual RB bundles to interleaved physical RB bundles, wherein the starting RB is a virtual starting RB, and the length of the consecutively allocated RBs is the length of the consecutively allocated virtual RBs, and wherein the virtual starting RB defines the start of the length of the consecutively allocated virtual RBs.

[0027] In some embodiments, the computer executable instructions that cause the UE to receive the data transmission cause the UE to receive the data transmission in time-frequency resources defined by the interleaved physical RB bundle, wherein the interleaved physical RB bundle is based on: the virtual starting RB, the length of the consecutively allocated virtual RBs, the interleaving mapping, and a reference physical RB bundle.

[0028] In some embodiments, the reference physical RB bundle is a physical RB bundle containing a smallest numbered physical resource block (PRB) in a second CORESET, and the UE has decoded the DCI in the second CORESET.

[0029] In some embodiments, the DCI is a fallback DCI.

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

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

[0032] According to another aspect of the present disclosure, a method for wireless communication is provided. The method includes: a base station sends downlink control information (DCI) in a physical downlink control channel (PDCCH) of an activated downlink (DL) bandwidth part (BWP), the DCI being used to schedule data transmission, the DCI including a frequency domain resource allocation field; and the base station sends the data transmission in a time-frequency resource defined by at least a starting resource block (RB) and a length of consecutively allocated RBs to a user equipment (UE), the starting RB being based on: a value of the frequency domain resource allocation field in the DCI, a reference RB, and the number of RBs of a first control resource set (CORESET), and the length of the consecutively allocated RBs being based on: a value of the frequency domain resource allocation field in the DCI and the number of RBs of the first CORESET.

[0033] In some embodiments, the reference RB is a physical resource block (PRB) with the smallest number in a second CORESET, where the second CORESET is the CORESET in which the DCI has been decoded by the UE.

[0034] In some embodiments, the activated DL BWP includes RB allocation for the data transmission, the RB allocation being based on an interleaving mapping of virtual RB bundles to interleaved physical RB bundles, wherein the starting RB is a virtual starting RB, and the length of the consecutively allocated RBs is the length of the consecutively allocated virtual RBs, and wherein the virtual starting RB defines the start of the length of the consecutively allocated virtual RBs.

[0035] In some embodiments, sending the data transmission includes sending the data transmission in time-frequency resources defined by the interleaved physical RB bundle, and the interleaved physical RB bundle is based on: the virtual starting RB, the length of the consecutively allocated virtual RBs, the interleaving mapping, and the reference physical RB bundle.

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

[0037] In some embodiments, the DCI is a fallback DCI.

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

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

[0040] According to another aspect of the present disclosure, a device is provided, comprising a processor and a computer-readable medium having computer-executable instructions stored thereon. The instructions, when executed by the processor, cause the device to: send downlink control information (DCI) in a physical downlink control channel (PDCCH) in an activated downlink (DL) bandwidth part (BWP), the DCI being used to schedule data transmission, and the DCI including a frequency domain resource allocation field; and send the data transmission in a time-frequency resource defined by at least a starting resource block (RB) and a length of consecutively allocated RBs to a user equipment (UE), the starting RB being based on: a value of the frequency domain resource allocation field in the DCI, a reference RB, and the number of RBs of a first control resource set (CORESET), and the length of the consecutively allocated RBs being based on: a value of the frequency domain resource allocation field in the DCI and the number of RBs of the first CORESET.

[0041] In some embodiments, the reference RB is a physical resource block (PRB) with the smallest number in a second CORESET, and the UE has decoded the DCI in the second CORESET.

[0042] In some embodiments, the activated DL BWP includes RB allocation for the data transmission, the RB allocation being based on an interleaving mapping of virtual RB bundles to interleaved physical RB bundles, wherein the starting RB is a virtual starting RB, the length of the consecutively allocated RBs is a consecutively allocated virtual RB length, and wherein the virtual starting RB defines the start of the consecutively allocated virtual RB length.

[0043] In some embodiments, sending the data transmission includes sending the data transmission in a time-frequency resource defined by the interleaved physical RB bundle, wherein the interleaved physical RB bundle is based on: the virtual starting RB, the continuously allocated virtual RB length, the interleaved mapping, and a reference physical RB bundle.

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

[0045] In some embodiments, the DCI is a fallback DCI.

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

[0047] In some embodiments, the DCI is associated with a group of UEs, and for all UEs in the group of UEs, the data transmission scheduled by the DCI is a downlink data transmission allocated in the same time-frequency resources. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0049] Figure 1 It is a network diagram of a communication system;

[0050] Figure 2 is a block diagram of an air interface manager for configuring a software configurable air interface;

[0051] Figure 3A is a block diagram of an example of client-side electronic equipment;

[0052] Figure 3B is a block diagram of an example of network-side electronic equipment;

[0053] Figure 4A is an example of a VRB set including a subset of virtual resource blocks (VRBs) for a specific type of transmission scheduling;

[0054] Figure 4B Yes Figure 4A An example of interleaving and mapping a VRB set of a VRB subset to a physical resource block (PRB) set;

[0055] Figure 5 An example of non-interleaved mapping of a VRB set including VRB subsets to PRB sets of three different user equipments (UEs), wherein the three different UEs have different activated bandwidth parts (BWPs);

[0056] Figure 6 is an example of non-interleaved mapping of a VRB set including a VRB subset to a PRB set of three different UEs, the three different UEs having different activated BWPs, and the PRB set having a different subcarrier spacing configuration from the VRB;

[0057] Figure 7is an example of interleaved mapping of a VRB set including VRB subsets onto PRB sets of three different UEs, the three different UEs having different activated BWPs;

[0058] Figure 8 An example of interleaving and mapping a VRB set including a VRB subset onto a PRB set of three different UEs, wherein the three different UEs have different activated BWPs, and the PRB set and the VRB have different subcarrier spacing configurations;

[0059] Fig. 9 is a flow chart describing a method used by a UE in locating transmission resources allocated in downlink control information (DCI);

[0060] Fig.10 is a flow chart describing a method used by a network side device when allocating transmission resources;

[0061] Fig.11 is a flow chart describing another method used by a UE in locating transmission resources allocated in downlink control information (DCI);

[0062] Fig.12 is a flowchart describing another method used by a network-side device when allocating transmission resources.

[0063] Corresponding numerals and symbols in the different figures generally refer to corresponding parts unless otherwise indicated.The figures are drawn to clearly illustrate the relevant aspects of the embodiments and are not necessarily drawn to scale. DETAILED DESCRIPTION

[0064] 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 a number of applicable inventive concepts that can be embodied in various specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the present invention, and do not limit the scope of the present invention.

[0065] Figure 1 An example communication system 100 is shown in which embodiments of the present disclosure may be implemented. In general, the communication system 100 enables multiple wireless or wired elements to transmit data and other content. The purpose of the communication system 100 may be to provide content (voice, data, video, text) to user devices via broadcast, narrowcast, user devices, etc. The communication system 100 may operate by sharing resources such as bandwidth.

[0066] In this example, the communication system 100 includes electronic devices (EDs) 110a to 110c, radio access networks (RANs) 120a to 120b, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. Figure 1 Some number of these components or elements are shown in FIG. 1 , but any reasonable number of these components or elements may be included in the communication system 100 .

[0067] The EDs 110a to 110c are used to operate, communicate, or operate and communicate in the communication system 100. For example, the EDs 110a to 110c are used to transmit, receive, or both transmit and receive via a wireless or wired communication channel. Each ED 110a to 110c represents any suitable end-user device for wireless operation, and may include (or may be referred to as) such devices as user equipment / device (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smart phone, laptop, computer, tablet, wireless sensor, or consumer electronic device.

[0068] exist Figure 1In the embodiment, RAN 120a to 120b include base stations 170a to 170b, respectively. Each base station 170a to 170b is used to wirelessly connect to one or more of ED 110a to 110c to enable access to any other base stations 170a to 170b, core network 130, PSTN 140, Internet 150 and / or other networks 160. For example, base stations 170a to 170b may include (or be) one or more of several well-known devices, such as base transceiver stations (BTS), Node-B (NodeB), evolved NodeB (eNodeB), home eNodeB, gNodeB, transmission point (TP), site controller, access point (AP) or wireless router. Any ED 110a to 110c may alternatively or additionally be used to interface, access, or communicate with any other base station 170a to 170b, the Internet 150, the core network 130, the PSTN 140, other networks 160, or any combination of the foregoing. The communication system 100 may include a RAN, such as the RAN 120b, in which the corresponding base station 170b accesses the core network 130 via the Internet 150, as shown.

[0069] EDs 110a to 110c and base stations 170a to 170b are examples of communication devices that may be used to implement some or all of the functions and / or embodiments described herein. Figure 1In the illustrated embodiment, base station 170a forms part of RAN 120a, which may include other base stations, base station controllers (BSC), radio network controllers (RNC), relay nodes, elements and / or devices. Any base station 170a, 170b may be a single element as shown, or multiple elements distributed in the corresponding RAN, or otherwise. In addition, base station 170b forms part of RAN 120b, which may include other base stations, elements and / or devices. Each base station 170a to 170b sends and / or receives wireless signals in a specific geographic area or region, which is sometimes referred to as a "cell" or "coverage area". The cell can be further divided into cell sectors, and base stations 170a to 170b can, for example, use multiple transceivers to provide services to multiple sectors. In some embodiments, a micro or femto cell can be established, where the radio access technology supports such a micro or femto cell. In some embodiments, multiple transceivers can be used for each cell, for example, using multiple-input multiple-output (MIMO) technology. The number of RANs 120a-120b shown is exemplary only. Any number of RANs may be contemplated when designing the communication system 100.

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

[0071] The base stations 170a to 170b may implement UMTS Terrestrial Radio Access (UTRA) to establish the air interface 190 using wideband CDMA (WCDMA). In this case, the base stations 170a to 170b may implement protocols such as HSPA, HSPA+, and optionally HSDPA, HSUPA, or HSDPA and HSUPA. Alternatively, the base stations 170a to 170b may establish the air interface 190 using LTE, LTE-A and / or LTE-B and E-UTRA. It is contemplated that the communication system 100 may use multi-channel access functionality, including such schemes as described above. Other wireless technologies used to implement the air interface 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, a variety of other access schemes and wireless protocols may be utilized.

[0072] The RANs 120a to 120b communicate with the core network 130 to provide various services, such as voice, data, and other services to the EDs 110a to 110c. The RANs 120a to 120b and / or the core network 130 may communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by the core network 130 and may or may not use the same radio access technology as the RANs 120a, RANs 120b, or both. The core network 130 may also serve as a gateway access between (i) the RANs 120a to 120b, or the EDs 110a to 110c, or both, and (ii) other networks, such as the PSTN 140, the Internet 150, and other networks 160. In addition, some or all of the EDs 110a to 110c may include functionality for communicating with different wireless networks over different radio links using different radio technologies and / or protocols. Instead of (or in addition to) wireless communications, the EDs 110a to 110c may communicate with a service provider or switch (not shown) and the Internet 150 via a wired communications channel. The PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include a computer network and a subnet (intranet) or both, and include internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP). The EDs 110a to 110c may be multi-mode devices capable of operating according to a variety of wireless access technologies, and include a number of transceivers necessary to support such technologies.

[0073] In an embodiment of the present invention, the communication system 100 is a heterogeneous communication system having different transmission source types and / or different transmission destination types. Different transmission source types may have different transmission capabilities. Different transmission destination types may have different receiving capabilities.

[0074] In heterogeneous communication systems, Figure 1EDs 110a to 110c include different types of devices with different capabilities and requirements. More specifically, each ED 110a to 110c may be associated with a different traffic type with specific requirements for Quality of Service (QoS), latency, throughput, simultaneous connections, etc. Example EDs 110a to 110c associated with different traffic types may include smartphones, computers, televisions, security cameras, sensors, thermostats, heart rate monitors, etc. In a specific example, ED 110a is a computer, ED 110b is a sensor, and ED 110c is a heart rate monitor. Each of EDs 110a to 110c may have different wireless communication capabilities and requirements.

[0075] In addition, in a heterogeneous communication system, the base stations 170a to 170b can communicate with one or more of the EDs 110a to 110c using wireless communication links through one or more software configurable air interfaces 190. Different radio access network devices (e.g., base stations 170a to 170b) and electronic devices (e.g., EDs 110a to 110c) may have different transmission capabilities and / or requirements. For example, an eNB may have multiple transmit antennas. A picocell may have only one transmit antenna or a relatively small number of transmit antennas. In addition, a picocell may transmit at a lower maximum power level than an eNB. Similarly, a computer may have much higher data bandwidth requirements and signal processing capabilities than a sensor. For another example, a heart rate monitor may have more stringent delay and reliability requirements than a television.

[0076] Therefore, in a heterogeneous communication system, for example, in the 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 transmission capabilities and / or transmission requirements. Different transmission capabilities and / or transmission requirements may be met by selecting the availability of different air interface configurations for different devices, communications, or requirements.

[0077] Figure 2 A schematic diagram of an air interface manager 200 for configuring a software configurable air interface 190 is shown. The air interface manager 200 may be, for example, a module including a plurality of components or building blocks that define parameters of the air interface 190 and collectively specify how the air interface 190 transmits and / or receives.

[0078] 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 .

[0079] The waveform component 205 can specify the shape and form of the signal being sent. The waveform options can include orthogonal multiple access waveforms and non-orthogonal multiple access waveforms. Non-limiting examples of such waveform options include Orthogonal Frequency Division Multiplexing (OFDM), Filtered OFDM (f-OFDM), Time Domain Windowed OFDM, Filter Bank Multicarrier (FBMC), Universal Filtered Multicarrier (UFMC), Generalized Frequency Division Multiplexing (GFDM), Wavelet Packet Modulation (WPM), Faster Than Nyquist (FTN) waveform, and low Peak to Average Power Ratio Waveform (low PAPR WF).

[0080] The frame structure component 210 may specify a configuration of a frame or a group of frames. The frame structure component 210 may indicate one or more of a time, frequency, pilot signature, code, or other parameters of a frame or a group of frames.

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

[0082] For certain waveforms, such as certain OFDM-based waveforms, the frame structure component may also specify one or more associated waveform parameters, such as subcarrier spacing width, symbol duration, cyclic prefix (CP) length, channel bandwidth, guard band / subcarrier, and sampling size and frequency.

[0083] Additionally, the frame structure component 210 can further specify whether the frame structure is for time division duplex communication or frequency division duplex communication.

[0084] The specifications of the waveform component and the frame structure component together are sometimes referred to as a “parameter set.” Thus, the air interface 190 may include a parameter set component 230 that defines a number of air interface configuration parameters, such as subcarrier spacing, CP length, symbol length, slot length, and symbols per slot.

[0085] These parameter sets, also referred to as subcarrier spacing configurations, can be scalable in the sense that the subcarrier spacings of different parameter sets are multiples of each other, and the slot lengths of different parameter sets are also multiples of each other. This scalable design across multiple parameter sets provides implementation advantages, such as scalable total OFDM symbol duration in the context of time division duplex (TDD).

[0086] A frame can be configured using one or a combination of scalable parameter sets. For example, a parameter set with a 60kHz subcarrier spacing has a relatively short OFDM symbol duration (because the OFDM symbol duration is inversely proportional to the subcarrier spacing), which makes the 60kHz parameter set particularly suitable for ultra-low latency communications, such as Vehicle-to-Any (V2X) communications. Another example of a parameter set with a relatively short OFDM symbol duration suitable for low-latency communications is a parameter set with a 30kHz subcarrier spacing. A parameter set with a 15kHz subcarrier spacing can be compatible with LTE or used as a default parameter set for initial access to a network by a device. This 15kHz parameter set can also be suitable for broadband services. A parameter set with a 7.5kHz spacing has a relatively long OFDM symbol duration, which may be particularly useful for coverage enhancement and broadcasting. Other uses of these parameter sets will be or will become apparent to those of ordinary skill in the art. Among the four parameter sets listed, those with 30kHz and 60kHz subcarrier spacing are more robust under Doppler spread (fast moving conditions) because the subcarrier spacing is wider. It is further contemplated that different parameter sets may use different values ​​for other physical layer parameters, such as the same subcarrier spacing and different cyclic prefix lengths.

[0087] It is further contemplated that other subcarrier spacings may be used, such as higher or lower subcarrier spacings. For example, other subcarrier spacings that vary by a factor of 2n include 120 kHz and 3.75 kHz.

[0088] In other examples, more limited scalability may be achieved where two or more parameter sets both have subcarrier spacings that are integer multiples of the minimum subcarrier spacing, not necessarily related to 2n. Examples include subcarrier spacings of 15kHz, 30kHz, 45kHz, 60kHz.

[0089] In other examples, non-scalable subcarrier spacings that are not integer multiples of the minimum subcarrier spacing may be used, such as 15 kHz, 20 kHz, 30 kHz, 60 kHz.

[0090] OFDM-based signals may be used to transmit signals in which multiple parameter sets coexist simultaneously. More specifically, multiple sub-band OFDM signals may be generated in parallel, each sub-band OFDM signal being in a different sub-band and each sub-band having a different subcarrier spacing (and more generally, a different parameter set). Multiple sub-band signals are combined into a single signal for transmission, such as for downlink transmission. Alternatively, multiple sub-band signals may be transmitted from separate transmitters, such as for uplink transmission from multiple electronic devices (EDs), which may be user equipment (UEs).

[0091] Using different parameter sets can allow the air interface 190 to support the coexistence of various use case sets with a wide range of quality of service (QoS) requirements, such as different levels of delay or reliability tolerance, and different bandwidth or signaling overhead requirements. In one example, the base station can signal the ED an index representing the selected parameter set, or a single parameter of the selected parameter set (e.g., subcarrier spacing). Based on this signaling, the ED can determine the parameters of the selected parameter set from other information, such as a lookup table of candidate parameter sets stored in a memory.

[0092] Continuing with the components of the air interface 190, the multiple access scheme component 215 can specify how to grant access to a channel to one or more EDs. Non-limiting examples of multiple access technology options include technologies that define 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 (NOMA), pattern division multiple access (PDMA), lattice partition multiple access (LPMA), resource spread multiple access (RSMA), and sparse code multiple access (SCMA). In addition, multiple access technology options may include scheduled access, unscheduled access, also known as unauthorized access, non-orthogonal multiple access, orthogonal multiple access, for example, via dedicated channel resources (i.e., not shared between multiple EDs), contention-based shared channel resources, non-contention-based shared channel resources, and cognitive wireless-based access.

[0093] The protocol component 220 may specify how transmission and / or retransmissions are performed. Non-limiting examples of transmission and / or retransmission mechanism options include those mechanisms that specify a scheduled data pipe size, a signaling mechanism for transmission, and / or a signaling mechanism for retransmission.

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

[0095] Because the air interface includes multiple components or building blocks, and each component may have multiple candidate technologies (also referred to herein as air interface capability options), the air interface manager 200 may configure and store a large number of different air interface profiles, each of which defines a corresponding set of air interface capability options.

[0096] For example, in each air interface profile that defines a corresponding set of air interface capability options, an air interface capability option is selected for each component building block of the air interface. Different sets of transmission requirements, including transmission content, sending conditions, and receiving conditions, can be met for each different air interface profile.

[0097] According to the transmission requirements of a pair of communication transmitting-receiving devices, one of the different air interface profiles that best meets the transmission requirements may be selected from the air interface manager 200 and used for the communication between the pair of communication transmitting-receiving devices.

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

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

[0100] By updating the stored components, profiles, and candidate options, the air interface manager 200 can flexibly adapt to better accommodate various wireless traffic types and services. Modifying or updating the components, profiles, and candidate options can allow the air interface manager 200 to provide suitable air interface profiles for traffic types or services other than those envisioned for ultra-reliable low latency communication (URLLC), enhanced mobile broadband (eMBB), and massive machine-type communications (mMTC).

[0101] Figure 3A and 3B An example device is shown in which the methods and teachings according to the present disclosure can be implemented. Specifically, Figure 3AAn example ED 110 is shown, Figure 3B An example base station 170 is shown. These components may be used in the communication system 100 or any other suitable system.

[0102] like Figure 3A As shown, ED 110 includes at least one processing unit 300. Processing unit 300 implements various processing operations of ED 110. For example, processing unit 300 can perform signal encoding, data processing, power control, input / output processing, or any other function that enables ED 110 to operate in communication system 100. Processing unit 300 can also be used to implement some or all of the functions and / or embodiments described in more detail above. Each processing unit 300 includes any suitable processing or computing device for performing one or more operations. Each processing unit 300 can, for example, include a microprocessor, a microcontroller, a digital signal processor, a field programmable gate array, or an application specific integrated circuit.

[0103] ED 110 also includes at least one transceiver 302. Transceiver 302 is used to modulate data or other content that is sent through at least one antenna 304 or a network interface controller (NIC). Transceiver 302 is also used to demodulate data or other content received by at least one antenna 304. Each transceiver 302 includes any suitable structure for generating signals for wireless or wired transmission and / or processing signals for wireless or wired reception. Each antenna 304 includes any suitable structure for transmitting and / or receiving wireless or wired signals. One or more transceivers 302 can be used in ED 110. One or more antennas 304 can be used in ED 110. Although shown as a single functional unit, transceiver 302 can also be implemented using at least one transmitter and at least one separate receiver.

[0104] ED 110 also includes one or more input / output devices 306 or interfaces (e.g., a wired interface to Internet 150). Input / output devices 306 allow interaction with a user or other devices in the network. Each input / output device 306 includes any suitable structure for providing information to or receiving information from a user, including network interface communications, such as a speaker, microphone, keypad, keyboard, display, or touch screen.

[0105] In addition, ED 110 includes at least one memory 308. The memory 308 stores instructions and data used, generated, or collected by ED 110. For example, the memory 308 may store software instructions or modules for implementing some or all of the functions and / or embodiments described above and executed by the processing unit 300. Each memory 308 includes any suitable volatile and / or non-volatile storage devices and retrieval devices. Any suitable type of memory may be used, such as random access memory (RAM), read only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, etc.

[0106] like Figure 3B As shown, the base station 170 includes at least one processing unit 350, at least one transmitter (TX) 352, at least one receiver (RX) 354, one or more antennas 356, at least one memory 358, and one or more input / output devices or interfaces 366. Transceivers not shown may be used to replace the transmitter 352 and the receiver 354. A scheduler 353 may be coupled to the processing unit 350. The scheduler 353 may be included in the base station 170 or operate separately from the base station. The processing unit 350 implements various processing operations of the base station 170, such as signal encoding, data processing, power control, input / output processing, or any other function. The processing unit 350 may also be used to implement some or all of the functions and / or embodiments described in more detail above. Each processing unit 350 includes any suitable processing or computing device for performing one or more operations. Each processing unit 350 may, for example, include a microprocessor, a microcontroller, a digital signal processor, a field programmable gate array, or an application-specific integrated circuit.

[0107] Each transmitter 352 includes any suitable structure for generating a signal that is wirelessly or wired to one or more EDs or other devices. Each receiver 354 includes any suitable structure for processing a signal that is wirelessly or wired received from one or more EDs or other devices. Although shown as separate components, at least one transmitter 352 and at least one receiver 354 can be combined into a transceiver. Each antenna 356 includes any suitable structure for sending and / or receiving wireless or wired signals. Although a common antenna 356 is shown here coupled to both the transmitter 352 and the receiver 354, one or more antennas 356 can be coupled to the transmitter 352, and one or more separate antennas 356 can be coupled to the receiver 354. Each memory 358 includes any suitable volatile and / or non-volatile storage and retrieval devices, such as those described above in conjunction with ED 110. The memory 358 stores instructions and data used, generated or collected by the base station 170. For example, the memory 358 can store software instructions or modules for implementing some or all of the functions and / or embodiments described above and executed by the processing unit 350.

[0108] Each input / output device 366 allows interaction with a user or other devices in the network. Each input / output device 366 includes any suitable structure for providing information to a user or receiving / providing information from a user and including network interface communications.

[0109] As described above, downlink control information (DCI) is sent from the network side device to the ED via the physical downlink control channel (PDCCH) to provide the ED with information about specific physical layer parameters such as downlink or uplink data scheduling, as well as other configuration parameters. DCI can be sent using different DCI formats designed for different purposes. Table 1 below shows examples of eight different DCI formats for eight different purposes.

[0110] Table 1: DCI format

[0111]

[0112]

[0113] DCI formats 0_0 and 1_0 are referred to as "fallback" DCI formats for scheduling uplink data and downlink data, respectively. Fallback DCI formats are intended for performing basic radio link establishment or reconfiguration, or transmission of system messages. They may include less information than other DCI formats (i.e., the minimum amount of information that allows basic radio link establishment or reconfiguration).

[0114] DCI formats 0_1 and 1_1 are referred to as "non-fallback" DCI formats for scheduling uplink data and downlink data, respectively. DCI formats 2_0 and 2_1 are DCI formats for notifying the ED of time slot format information and information preemption, respectively. DCI formats 2_2 and 2_3 are DCI formats for notifying the ED of transmission power control information. Although embodiments of the present application may be described below with specific reference to fallback DCI, it should be understood that, more generally, aspects of the present disclosure may be used with many different types of DCI.

[0115] The payload size of the fallback DCI format can be determined based on the initial downlink BWP instead of the activated downlink BWP. The initial downlink BWP is the frequency domain size of the time-frequency resources allocated to the UE when the UE initially accesses the network. The initial BWP can be used after the initial network access, but when the network is further used, the UE will generally be configured with an activated BWP. The activated BWP can be reconfigured appropriately. The initial downlink BWP size (in terms of the number of resource blocks) may be different from the activated downlink BWP. In the case where the activated BWP has a different size from the initial 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, then when the DCI is used for resource allocation in the activated BWP, this may produce uncertainty or misinterpretation of the content of the fallback DCI. Embodiments of the present disclosure seek to resolve this uncertainty.

[0116] In addition to transmitting frequency domain resource allocation in the fallback DCI format, embodiments of the present disclosure may also provide higher spectrum efficiency when the fallback DCI is used for multiple UEs.

[0117] In New Radio (NR), resource allocation can be performed based on a resource indication value (RIV) using a frequency domain resource allocation field included in a DCI format. Resource allocation can be performed with or without interleaving mapping of virtual resource blocks (VRBs) to physical resource blocks (PRBs). A form of RIV-based resource allocation is utilized in LTE. However, in LTE RIV, resource allocation is based on the entire carrier size rather than a portion of the carrier size, i.e., BWP. This example of resource allocation can be performed using resource allocation type 1.

[0118] Figure 4AA virtual resource block (VRB) set is shown, wherein a subset of VRBs is allocated for data transmission, and the VRB subset may include, for example, a PDSCH for transmission to one or more UEs or a PUSCH for transmission from the UE to a base station. The entire VRB set 410 is of length resource blocks, numbered from 0 to The resources allocated for data transmission are indicated in resource blocks (RBs). start Starts at and has a length of L RBs A VRB subset 412 of RBs.

[0119] With RIV-based resource allocation, a single RIV value represents two values, namely the starting resource block RB start value and the number of allocated RBs L RBs In aspects of the present disclosure, when the RIV value is used in conjunction with a reference starting virtual resource block, i.e. VRB=0, and the overall size of the frequency band (defined in the number of RBs) Can be used to determine RB star t value and L RBs .

[0120] In an example where there is no interleaved mapping between VRBs and PRBs, VRB n is mapped to PRB n.

[0121] Figure 4B An example of how the VRB set 410 of FIG. 4 can be mapped to a PRB set 420 having the same number of RBs as the VRB set is shown, and there is an interleaved mapping between the VRBs and the PRBs. In the PRB set 420, the VRB subset 412 is spread in a RB bundle with two RBs 422, 424, 426, 428. The specific manner in which the bundles are distributed is not described in detail here. In this example, the VRBs are mapped to the same number of PRBs. However, as will be described below with respect to Figure 5 , 6 As seen in the examples of , 7 and 8, a VRB set can be mapped to a PRB set that is part of a different PRB set, i.e. an activated BWP. In this case, for example Figure 7 and 8 As shown, it can be Figure 4B The diagram is regarded as an intermediate stage of the mapping of VRB to PRB.

[0122] In some embodiments, the DCI is sent in a common search space and the DCI may be for more than one UE. If the DCI is intended to be decoded by a group of UEs, the group of UEs should have the same understanding of the DCI content. The DCI received by all UEs in the group is a single DCI with a payload size. Therefore, it would be beneficial to have a common payload size that is known to all UEs. This is one reason why the payload size of DCI format 0_0 / 1_0 (fallback DCI) can be determined based on the initial downlink bandwidth part (initial DL BWP), which is the same for all UEs accessing the network. This means that, for example, it can be assumed that The size is the number of resource blocks in the initial DL BWP. In some embodiments, a group of UEs are assigned the same scheduled PDSCH to provide efficient spectrum utilization. This means that the group of UEs will each access the same resource element (RE) for PDSCH. In other words, all UEs in the group should have the same interpretation of the DCI fields, especially the frequency domain resource allocation field including the RIV, regardless of the activated DL BWP of a given UE. If the DCI size is determined by a value that is not common to all UEs, for example, by a value other than the initial BWP, UEs with different activated BWPs will have difficulty interpreting the frequency domain resource allocation field in the DCI. The result may be that the interpreted PDSCH frequency position will be within the frequency range of the activated BWP of each UE in the group of UEs; and all UEs in the group of UEs will interpret the DCI and obtain the same PDSCH frequency position.

[0123] For frequency domain resource allocation, when the fallback DCI (DCI format 1_0 or 0_0) is decoded in the common search space, the reference RB (when interleaved mapping is not used) or the reference RB bundle (when interleaved mapping is used) is used to determine the starting physical resource block of the scheduled resources for data transmission. For example, for non-interleaved VRB to PRB mapping, virtual resource block n is mapped to physical resource block n+n_reference_RB. 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 BWP size used for interleaving is the reference PRB band size defined as X in this document. The RB bundle size is fixed. Two non-limiting examples of RB bundle sizes are 2 RBs or 4 RBs.

[0124] For common scheduling resources for multiple UEs, the reference RB or reference RB bundle has the same physical frequency location for the group of UEs. However, the reference RB or reference RB bundle may have a different PRB index or PRB bundle index in the activated BWP of each UE in a group of UEs, because the individual UEs may have activated BWPs of different sizes occurring at different starting RBs. This may be done, for example, in Figure 5 As seen in the activated BWP of UE1, UE2 and UE3. The UEs should have an overlap of physical frequency locations at least equal to the size of the common scheduling resource.

[0125] Various aspects of the present disclosure each provide an alternative selection of reference RBs for VRB to PRB mapping. In a first embodiment, the reference RB is selected as the lowest resource element group (REG) of the PDCCH in which the fallback DCI (DCI format 0_0 or 1_0) has been decoded by the UE. In a second embodiment, the reference RB is selected as the lowest numbered PRB in the CORESET in which the fallback DCI (DCI format 0_0 or 1_0) has been decoded by the UE. In a third embodiment, the reference RB is selected as the lowest numbered PRB in the configured CORESET with the smallest CORESET ID in the activated BWP. In a fourth embodiment, the reference RB is selected as the lowest numbered PRB of the initial DL BWP (or CORESET#0). In a fifth embodiment, the reference RB is selected as the lowest numbered PRB of the configured BWP with the smallest BWP ID. In a sixth embodiment, the reference RB is selected as the lowest numbered PRB of the default BWP. In a seventh embodiment, the reference RB is a PRB configured by high-level signaling.

[0126] The following is a more detailed description of the above-mentioned first to seventh embodiments involving selecting a reference RB to be used for mapping from a virtual resource block to a physical resource block.

[0127] First embodiment

[0128] For non-interleaved VRB-to-PRB mapping, virtual resource block n is mapped to physical resource block n, except when the fallback DCI is decoded in the common search space, in which case virtual resource block n is mapped to physical resource block n+nREG, where physical resource block nREG corresponds to the smallest REG of the PDCCH in which the fallback DCI has been decoded by the UE.

[0129] Second embodiment

[0130] For non-interleaved VRB-to-PRB mapping, virtual resource block n is mapped to physical resource block n, except when the fallback DCI is decoded in the common search space, in which case virtual resource block n is mapped to physical resource block The physical resource block Corresponding to the smallest numbered physical resource block in the control resource set, in which the fallback DCI has been decoded by the UE.

[0131] Third embodiment

[0132] For non-interleaved VRB-to-PRB mapping, virtual resource block n is mapped to physical resource block n, except when the fallback DCI is decoded in the common search space, in which case virtual resource block n is mapped to physical resource block The physical resource block Corresponding to the physical resource block with the smallest number in the control resource set with the smallest ID configured in the active bandwidth part.

[0133] Fourth embodiment

[0134] For non-interleaved VRB-to-PRB mapping, virtual resource block n is mapped to physical resource block n, except when the fallback DCI is decoded in the common search space, in which case virtual resource block n is mapped to physical resource block The physical resource block Corresponds to the common resource blocks that are the same as physical resource block 0 of the initial DL bandwidth part.

[0135] Fifth embodiment

[0136] For non-interleaved VRB-to-PRB mapping, virtual resource block n is mapped to physical resource block n, except when the fallback DCI is decoded in the common search space, in which case virtual resource block n is mapped to physical resource block n+n PRB0 , where physical resource block n PRB0 Corresponds to the common resource block that is the same as physical resource block 0 of the bandwidth part configured with the smallest BWP ID.

[0137] Sixth embodiment

[0138] For non-interleaved VRB-to-PRB mapping, virtual resource block n is mapped to physical resource block n, except when the fallback DCI is decoded in the common search space, in which case virtual resource block n is mapped to physical resource block The physical resource block Corresponds to the common resource blocks that are the same as physical resource block 0 of the default DL bandwidth part.

[0139] Seventh embodiment

[0140] PRBs are configured for the UE via higher layer signaling. For non-interleaved VRB to PRB mapping, virtual resource block n is mapped to physical resource block n, except when the fallback DCI is decoded in the common search space, in which case virtual resource block n is mapped to physical resource block n+n0, where n0 is configured by higher layer signaling.

[0141] Various aspects of the present disclosure each provide an alternative selection of reference RB bundles used on interleaved VRB to PRB mapping. In an eighth embodiment, the reference RB bundle is selected as an RB bundle containing the reference RB of any one of the first to seventh embodiments described above. In a ninth embodiment, the reference RB bundle is selected as an RB bundle containing the smallest resource element group (REG) of a PDCCH, where the fallback DCI (DCI format 0_0 or 1_0) has been decoded by the UE in the PDCCH. In a tenth embodiment, the reference RB bundle is selected as an RB bundle containing the smallest numbered PRB in a CORESET, where the fallback DCI (DCI format 0_0 or 1_0) has been decoded by the UE in the CORESET. In an eleventh embodiment, the reference RB bundle is selected as an RB bundle containing the smallest numbered PRB in a configured CORESET with the smallest CORESET ID in an activated BWP. In a twelfth embodiment, the reference RB bundle is selected as an RB bundle containing the smallest numbered PRB of an initial DL BWP (or CORESET#0). In the thirteenth embodiment, the reference RB bundle is selected as the RB bundle containing the smallest numbered PRB of the configured BWP with the smallest BWP ID. In the fourteenth embodiment, the reference RB bundle is selected as the RB bundle containing the smallest numbered PRB of the default BWP. In the fifteenth embodiment, the reference RB bundle is the RB bundle configured by higher layer signaling.

[0142] The following is a more detailed description of the above-mentioned ninth to fifteenth embodiments involving selecting a reference RB to be used for mapping from a virtual resource block to a physical resource block.

[0143] Ninth embodiment

[0144] For interleaved VRB to PRB mapping, the mapping process is defined per resource block bundle. If the fallback DCI is decoded in the common search space, the UE shall assume Li = 2 and the virtual resource block bundle j∈{0,1,…,Nbundle-2} is mapped to the physical resource block bundle f(j)+j REG , where physical resource block bundle j REG The smallest REG containing the PDCCH in which the fallback DCI has been decoded by the UE.

[0145] Tenth embodiment

[0146] For interleaved VRB to PRB mapping, the mapping process is defined per resource block bundle. If the fallback DCI is decoded in the common search space, the UE shall assume Li = 2 and the virtual resource block bundle j∈{0,1,…,Nbundle-2} is mapped to the physical resource block bundle Physical Resource Block Bundle Contains the smallest numbered physical resource block in the control resource set, in which the fallback DCI has been decoded by the UE.

[0147] Eleventh Embodiment

[0148] For interleaved VRB to PRB mapping, the mapping process is defined per resource block bundle. If the fallback DCI is decoded in the common search space, the UE shall assume Li = 2 and the virtual resource block bundle j∈{0,1,…,Nbundle-2} is mapped to the physical resource block bundle Physical Resource Block Bundle Contains the smallest numbered physical resource block in the control resource set with the smallest ID configured in the activated bandwidth part.

[0149] Twelfth Embodiment

[0150] For interleaved VRB to PRB mapping, the mapping process is defined per resource block bundle. If the fallback DCI is decoded in the common search space, the UE shall assume Li = 2 and the virtual resource block bundle j∈{0,1,…,Nbundle-2} is mapped to the physical resource block bundle Physical Resource Block Bundle Physical resource block 0 containing the initial DL bandwidth portion.

[0151] Thirteenth Embodiment

[0152] For interleaved VRB to PRB mapping, the mapping process is defined per resource block bundle. If the fallback DCI is decoded in the common search space, the UE shall assume Li = 2 and the virtual resource block bundle j∈{0,1,…,Nbundle-2} is mapped to the physical resource block bundle f(j)+j PRB0 , where physical resource block bundle j PRB0 Physical resource block 0 containing the bandwidth portion configured with the smallest BWP ID.

[0153] Fourteenth Embodiment

[0154] For interleaved VRB to PRB mapping, the mapping process is defined per resource block bundle. If the fallback DCI is decoded in the common search space, the UE shall assume Li = 2 and the virtual resource block bundle j∈{0,1,…,Nbundle-2} is mapped to the physical resource block bundle Physical Resource Block Bundle Physical resource block 0 containing the default DL bandwidth portion.

[0155] Fifteenth Embodiment

[0156] For interleaved VRB to PRB mapping, the mapping process is defined based on resource block bundles. If the fallback DCI is decoded in the common search space, the UE shall use Li=2, and the virtual resource block bundle j∈{0,1,…,Nbundle-2} is mapped to the physical resource block bundle f(j)+j0, where the physical resource block bundle j0 is configured by higher layer signaling.

[0157] In some embodiments, for example when resource allocation type 1 is used, when fallback DCI (DCI format 1_0 or 0_0) is decoded in the common search space, a reference RB band size (X) is used to determine the BWP size. The reference PRB band size is used for RIV calculation or VRB to PRB mapping or both. In some embodiments, a first reference RB band size (X1) is used for RIV calculation and a second reference RB band size (X2) is used for VRB to PRB mapping.

[0158] If group information is provided to all UEs of a group of UEs through fallback DCI, the reference PRB band size (X) may be the same for the group of UEs.

[0159] Each of the various aspects of the present disclosure provides an alternative selection of the PRB band size (X) for RIV calculation or VRB to PRB mapping or both. In a first embodiment, the PRB band size (X) is selected as the size of the initial DL BWP (i.e., the size of CORESET#0). In a second embodiment, the PRB band size (X) is selected as the frequency size of the CORESET in which the fallback DCI has been decoded by the UE. The frequency size of the CORESET refers to the number of PRBs from the minimum numbered PRB of the CORESET to the maximum numbered PRB of the CORESET. In a third embodiment, the PRB band size (X) is selected as the frequency size of the configured CORESET with the minimum CORESET ID in the activated BWP. In a fourth embodiment, the PRB band size (X) is selected as the size of the configured BWP with the minimum BWP ID. In a fifth embodiment, the PRB band size (X) is selected as the size of the default BWP. In a sixth embodiment, the PRB band size (X) is configured by high-layer signaling. In some embodiments, where the first reference RB band size (X1) is used for RIV calculation and the second reference RB band size (X2) is used for VRB to PRB mapping, any one of the first to sixth embodiments described above may be used for the first RB band size (X1) or the second RB band size (X2) or both.

[0160] The following is a more detailed description of the above-mentioned first to sixth embodiments involving selecting a PRB band size to be used for RIV calculation or mapping from virtual resource blocks to physical resource blocks. Any of the first to fifteenth embodiments for selecting a reference RB to be used on VRB to PRB mapping can be combined with the first to sixth embodiments for selecting a PRB band size.

[0161] First embodiment

[0162] For RIV calculation or VRB to PRB mapping, the BWP size is equal to the number of resource blocks of the initial DL BWP. Optionally, for interleaved VRB to PRB mapping, the mapping process is further defined in terms of resource block bundles. If the fallback DCI is decoded in the common search space, the UE shall use a bundle size of L=2.

[0163] Second embodiment

[0164] For RIV calculation or VRB to PRB mapping, the BWP size is equal to the number of resource blocks from the smallest numbered resource block to the largest numbered resource block of the control resource set in which the fallback DCI has been decoded by the UE. Optionally, for interleaved VRB to PRB mapping, the mapping process is further defined based on resource block bundles. If the fallback DCI is decoded in the common search space, the UE shall use a bundle size of L=2.

[0165] Third embodiment

[0166] For RIV calculation or VRB to PRB mapping, the BWP size is equal to the number of resource blocks from the smallest numbered resource block to the largest numbered resource block of the control resource set with the smallest ID configured in the activated bandwidth part. Optionally, for interleaved VRB to PRB mapping, the mapping process is further defined based on resource block bundles. If the fallback DCI is decoded in the common search space, the UE shall use a bundle size of L=2.

[0167] Fourth embodiment

[0168] For RIV calculation or VRB to PRB mapping, the BWP size is equal to the number of resource blocks in the bandwidth part configured with the smallest BWP ID. Optionally, for interleaved VRB to PRB mapping, the mapping process is further defined in terms of resource block bundles. If the fallback DCI is decoded in the common search space, the UE shall assume a bundle size of L=2.

[0169] Fifth embodiment

[0170] For RIV calculation or VRB to PRB mapping, 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 bundles. If the fallback DCI is decoded in the common search space, the UE shall assume a bundle size of L=2.

[0171] Sixth embodiment

[0172] 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 bundles. If the fallback DCI is decoded in the common search space, the UE shall adopt a bundle size of L=2.

[0173] Figure 5 , 6 , 7 and 8 include examples of how the mapping from virtual resource blocks (VRBs) to physical resource blocks (PRBs) can be performed. The base station is responsible for allocating VRBs and sending DCI, which notifies the UE or UE group of the allocated resources available to the UE or UE group. The UE or UE group receives the DCI and, once decoded, accesses the allocated resources in the case of the PDSCH to receive data, or sends data back to the base station in the case of the PUSCH. The four figures show VRBs that can be considered to be processed at the base station, and PRBs in the corresponding activated bandwidth part (BWP) of each of the three corresponding UEs.

[0174] Figure 5 An example of mapping one VRB set to three different PRB sets is shown, one PRB set for each of three UEs. In this example, there is no interleaved mapping in the mapping portion of VRBs and PRBs. The VRB set 510 with the VRB subset 512 scheduled for data transmission is substantially the same as Figure 4A The VRB sets in the same. Data transmission can be for uplink (PUSCH) or downlink (PDSCH). Each PRB set 520, 530, 540 corresponds to an activated bandwidth part, and these activated bandwidth parts are used for different UEs. Each PRB set has a corresponding number of PRBs. Figure 5In the example of , in each activated BWP, the number of PRBs, i.e., the BWP size is different. More generally, it should be understood that the number of PRBs in the corresponding UE BWP can be UE-specific. The first PRB in each PRB set 520, 530, 540 has a starting PRB=0. All three PRB sets 520, 530, 540 have the same reference PRB relative to each other, but this reference PRB is at a different PRB in the activated BWP relative to PRB=0. Therefore, it should be understood that for all three UEs, the reference PRB is the same physical frequency position. In all three PRB sets 520, 530, 540, the PRB sets 522, 532, 542 allocated for a specific transmission 510 fall within the activated BWP of each corresponding UE.

[0175] In the first PRB set 520, PRB set 524, corresponding to VRB set 514, falls within the activated BWP of UE1. In the third PRB set 540, PRB set 544, corresponding to VRB set 514, falls within the activated BWP of UE3. In the second PRB set 530, PRB set 534, corresponding to VRB set 514, extends beyond the activated BWP of UE2. Although PRB set 534 may extend outside the activated 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 controlling network, is the base station that ultimately allocates the size of the activated BWP for the UE, defines the size of the VRB set 514, and schedules the size of the VRB 512. Therefore, the base station is smart enough not to schedule and transmit information to any given UE on resources outside the activated BWP that it has also allocated.

[0176] Figure 6 Another example of mapping one VRB set to three different PRB sets is shown, one PRB set for each of three UEs. In this example, there is no interleaved mapping in the mapping portion of the VRBs and PRBs. In this example, the subcarrier spacing configuration of the VRBs is different from the subcarrier spacing configuration of the PRBs. It can be seen that the height of the corresponding PRBs in the PRB sets 620, 630, 640 is approximately twice the height of the VRBs in the VRB set 610. This can, for example, mean that the subcarrier spacing of a single PRB is wider than the subcarrier spacing of a single VRB. The VRB set 610 with the VRB subset 612 scheduled for data transmission is substantially the same as Figure 4A The VRB sets in the same. Data transmission can be for uplink or downlink. Each PRB set 620, 630, 640 corresponds to an activated bandwidth part, and these activated bandwidth parts are used for different UEs. Each PRB set has a corresponding number of PRBs. Figure 6In the example of , in each activated BWP, the number of PRBs is different. More generally, it should be understood that the number of PRBs in the corresponding UE BWP can be UE-specific. The first PRB in each PRB set 620, 630, 640 has a starting PRB=0. All three PRB sets 620, 630, 640 have the same reference PRB relative to each other, but this reference PRB is at a different PRB in the activated BWP relative to PRB=0. Therefore, it should be understood that for all three UEs, the reference PRB is the same physical frequency position. In all three PRB sets 620, 630, 640, the PRB sets 622, 632, 642 allocated for a specific transmission 610 fall within the activated BWP of each corresponding UE.

[0177] In the first PRB set 620, PRB set 624, corresponding to VRB set 614, falls within the activated BWP of UE1. In the third PRB set 640, PRB set 644, corresponding to VRB set 614, falls within the activated BWP of UE3. In the second PRB set 630, PRB set 634, corresponding to VRB set 614, extends beyond the activated BWP of UE2. Although PRB set 634 may extend outside the activated 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 controlling network, is the base station that ultimately allocates the size of the activated BWP for the UE, defines the size of the VRB set 614, and schedules the size of the VRB 612. Therefore, the base station is smart enough not to schedule and transmit information to any given UE on resources outside the activated BWP that it has also allocated.

[0178] Figure 7 Another example of mapping one VRB set to three different PRB sets is shown, one for each of three UEs. In this example, there is an interleaved mapping in the mapping portion of VRBs and PRBs. VRB set 710 with a subset of VRBs 712 scheduled for data transmission is interleaved as part of the VRB to PRB mapping, as can be seen in 715. Data transmission can be for uplink or downlink. The subset of VRBs 712 scheduled for data transmission can be mapped into RB bundle sets 716, 717, 718, and 719 of 2 RBs, which is similar to Figure 4B Each PRB set 720, 730, 740 corresponds to an activated bandwidth part, and these activated bandwidth parts are used for different UEs. Each PRB set has a corresponding number of PRBs. Figure 7In the example of , the number of PRBs is different in each activated BWP. More generally, it should be understood that the number of PRBs in the corresponding UE BWP may be UE-specific. The first PRB in each PRB set 720, 730, 740 has a starting PRB=0. All three PRB sets 720, 730, 740 have the same reference PRB relative to each other, but this reference PRB is at a different PRB in the activated BWP relative to PRB=0. The grid for positioning the PRB bundles may be configured in a fixed manner in the system, and the position of the reference PRB will also be configured accordingly within the bundle. Therefore, the reference PRB may or may not be the first PRB in the PRB bundle. Figure 7 In the example of , the reference PRB in each activated BWP is the second PRB of the bundle of 2 PRBs. Again, it should be understood that the reference PRB, and more generally the reference PRB bundle, is the same physical frequency location for all three UEs. In all three PRB sets 720, 730, 740, the interleaved PRB bundles (e.g., 726, 727, 728, 729 in 720) corresponding to the interleaved VRB bundles (716, 717, 718, 719 in 715) fall within the activated BWP of each respective UE.

[0179] In the first PRB set 720, PRB set 724, corresponding to VRB set 714, falls within the activated BWP of UE1. In the third PRB set 740, PRB set 744, corresponding to VRB set 714, falls within the activated BWP of UE3. In the second PRB set 730, PRB set 734, corresponding to VRB set 714, extends beyond the activated BWP of UE2. Although PRB set 734 may extend outside the activated 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 controlling network, is the base station that ultimately allocates the size of the effective BWP for the UE, defines the size of the VRB set 714, defines the interleaving mapping used, the size of the packet, and the size of the scheduling VRB 712. Therefore, the base station is smart enough not to schedule and transmit information any given UE on resources outside the activated BWP that it has also allocated.

[0180] Figure 8Another example of mapping one VRB set to three different PRB sets is shown, one PRB set for each of three UEs. In this example, there is an interleaved mapping in the mapping portion of the VRBs and PRBs. In this example, the subcarrier spacing configuration of the VRBs is different from the subcarrier spacing configuration of the PRBs. It can be seen that the height of the corresponding PRBs in the PRB sets 820, 830, 840 is approximately twice the height of the VRBs in the VRB set 810. This can, for example, mean that the subcarrier spacing of a single PRB is wider than the subcarrier spacing of a single VRB. The VRB set 810 with the VRB subset 812 scheduled for data transmission is interleaved as part of the VRB to PRB mapping, as can be seen in 815. The data transmission can be for uplink or downlink. The VRB subset 812 scheduled for data transmission can be set to be mapped into RB bundle sets 816, 817 and 818 of 2 RBs, which is consistent with Figure 4B Each PRB set 820, 830, 840 corresponds to an activated bandwidth part, and these activated bandwidth parts are used for different UEs. Each PRB set has a corresponding number of PRBs. Figure 8 In the example of , the number of PRBs is different in each activated BWP. More generally, it will be appreciated that the number of PRBs in a corresponding UE BWP may be UE-specific. The first PRB in each PRB set 820, 830, 840 has a starting PRB=0. All three PRB sets 820, 830, 840 have the same reference PRB relative to each other, but this reference PRB is at a different PRB in the activated BWP relative to PRB=0. The grid for positioning the PRB bundles may be configured in a fixed manner in the system, and the position of the reference PRB will also be configured accordingly within the bundle. Thus, the reference PRB may or may not be the first PRB in the PRB package. In Figure 8 In the example of , the reference PRB in each activated BWP is the second PRB of the bundle of 2 PRBs. Again, it should be understood that the reference PRB, and more generally the reference PRB bundle, is the same physical frequency location for all three UEs. In all three PRB sets 820, 830, 840, the interleaved PRB bundles corresponding to the interleaved VRB bundles 816, 817, 818 in 815 (e.g., 826, 827, 828 in 820) fall within the activated BWP of each corresponding UE.

[0181] In the first PRB set 820, PRB set 824 corresponding to VRB set 814 falls within the activated BWP of UE1. In the third PRB set 840, PRB set 844 corresponding to VRB set 814 falls within the activated BWP of UE3. In the second PRB set 830, PRB set 834 corresponding to VRB set 814 extends beyond the activated BWP of UE2. Although PRB set 834 may extend outside the activated 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 controlling network, is the base station that ultimately allocates the size of the activated BWP for the UE, defines the size of the VRB set 814, defines the interleaving mapping used, the size of the packet, and the size of the scheduling VRB 812. Therefore, the base station is smart enough not to schedule and transmit information to any given UE on resources outside the activated BWP that it has also allocated.

[0182] Fig. 9 A flow chart describing an example method 900 for wireless communication according to an embodiment of the present disclosure is shown. The method includes receiving 910 downlink control information (DCI) in a physical downlink control channel (PDCCH) in a first bandwidth part (BWP) by a user equipment (UE).

[0183] Another step 920 includes the UE determining a starting 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.

[0184] The reference RB may be at least one of the following:

[0185] (a) The resource element group (REG) with the smallest number in the PDCCH, in which the DCI has been decoded by the UE;

[0186] (b) the smallest numbered physical resource block (PRB) in the control resource set (CORESET) in which the DCI has been decoded by the UE;

[0187] (c) Activate the smallest numbered PRB in the configured CORESET with the smallest CORESET identifier (ID) in the BWP;

[0188] (d) the smallest numbered PRB in the initial DL BWP used by the UE;

[0189] (e) the lowest numbered PRB in the configured BWP with the lowest BWP ID;

[0190] (f) the smallest numbered PRB of the default BWP; and

[0191] (g) PRB configured by higher layer signaling.

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

[0193] (a) The number of RBs in the initial DL BWP;

[0194] (b) defining the number of RBs in a control resource set (CORESET) in which the DCI has been decoded by the UE;

[0195] (c) define the number of RBs of the configured CORESET with the smallest CORESET identifier (ID) in the activated BWP;

[0196] (d) The number of RBs defining the size of the configured BWP with the smallest BWP ID;

[0197] (e) the number of RBs defining the size of the default BWP; and

[0198] (f) The number of RBs configured by higher layer signaling.

[0199] Optional step 930 may include the UE determining the length of consecutively allocated RBs for data transmission based on the value of the frequency domain resource allocation field in the DCI and a reference size of the second BWP.

[0200] Once the time-frequency resources defined by at least the starting RB and the length of the consecutively allocated RBs are established, the UE may 940 send data transmissions, for example in a PUSCH, or receive data transmissions, for example in a PDSCH, in the established time-frequency resources.

[0201] 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 resources for all UEs in the group of UEs.

[0202] In some embodiments, the first BWP is an activation BWP and the second BWP is an initial downlink (DL) BWP.

[0203] In some embodiments, the RBs allocated for data transmission are distributed on the first BWP based on an interleaved mapping of VRB bundles to interleaved PRB bundles. In this case, the start RB is a virtual start RB, and the reference RB is a virtual reference RB.

[0204] In some embodiments, the UE further determines an interleaved PRB bundle for data transmission based at least on the virtual starting RB, the interleaved mapping, and the reference PRB bundle. In this case, sending or receiving data transmission includes sending or receiving data transmission allocated in a time-frequency resource defined at least in part by the interleaved PRB bundle.

[0205] In some embodiments, the virtual start RB defines a start of a contiguously allocated VRB length, and determining the interleaved PRB bundle comprises determining the interleaved PRB bundle further based on the contiguously allocated VRB length.

[0206] Fig.10 A flow chart describing an example method 1000 for wireless communication according to an embodiment of the present disclosure is shown. The method includes transmitting 1010 downlink control information (DCI) in a physical downlink control channel (PDCCH) in a first bandwidth part (BWP). The DCI includes a frequency domain resource allocation field, the field having a value for defining a starting resource block (RB) for data transmission to be allocated by the DCI, the starting RB being defined in conjunction with a reference RB and a reference size of a second BWP. Another step 1020 includes sending or receiving data transmission between a base station and a user equipment (UE).

[0207] In some embodiments, the value of the frequency domain resource allocation field further defines the length of the consecutively allocated RBs for data transmission. The sending or receiving of data transmission in 1020 includes sending or receiving data transmission allocated in the time-frequency resources defined by at least the starting RB and the length of the consecutively allocated RBs.

[0208] In some embodiments, the RBs allocated for data transmission are distributed on the first BWP based on an interleaved mapping of VRB bundles to interleaved PRB bundles. In this case, the start RB is a virtual start RB and the reference RB is a virtual reference RB.

[0209] In some embodiments, the interleaved PRB bundle for data transmission is defined by a virtual starting RB, an interleaving map, a continuously allocated virtual RB length, and a reference physical RB package. In this case, sending or receiving data transmission in 1020 includes sending or receiving data transmission allocated in a time-frequency resource defined at least in part by the interleaved PRB package.

[0210] Fig.11 A flow chart describing another example method 1100 for wireless communication according to an embodiment of the present disclosure is shown. The method includes a UE receiving 1110 downlink control information (DCI) in a physical downlink control channel (PDCCH) in an activated downlink (DL) bandwidth part (BWP). The DCI is used to schedule data transmission, and the DCI includes a frequency domain resource allocation field.

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

[0212] In some embodiments, receiving the data transmission includes receiving the data transmission in time-frequency resources defined by an interleaved PRB bundle, the interleaved PRB bundle being based on: a virtual starting RB, the contiguously allocated VRB length, an interleaving map, and a reference physical RB bundle.

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

[0214] Optional further step 1130 includes the UE determining that: the DCI is a fallback DCI for data transmission with non-interleaved VRB to PRB mapping; the fallback DCI is decoded in the common search space; and for data transmission, virtual RB n is mapped to in It is the smallest numbered PRB in the CORESET in which the fallback DCI has been decoded by the UE in the CORESET.

[0215] In some embodiments, activating the DL BWP includes allocating RBs for data transmission based on an interleaved mapping of VRB bundles to interleaved PRB bundles, wherein the starting RB is a virtual starting RB, and the length of the consecutively allocated RBs is the consecutively allocated VRB length, and wherein the virtual starting RB defines the start of the consecutively allocated virtual RB length.

[0216] In some embodiments, the reference PRB bundle is a PRB bundle containing a smallest numbered physical resource block (PRB) in a second CORESET, wherein the second CORESET is the CORESET in which the fallback DCI has been decoded by the UE.

[0217] In some embodiments, the DCI is a fallback DCI.

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

[0219] 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 resources for all UEs in the group of UEs.

[0220] Fig.12 A flow chart describing another example method 1200 for wireless communication according to an embodiment of the present disclosure is shown. The method 1200 includes a device transmitting 1210 downlink control information (DCI) in a physical downlink control channel (PDCCH) in an activated downlink (DL) bandwidth part (BWP). The DCI is used to schedule data transmission, and the DCI includes a frequency domain resource allocation field. For example, the device can be a network access point, such as a base station.

[0221] Another step 1220 includes the device sending a data transmission in a time-frequency resource defined by at least a starting resource block (RB) and a length of consecutively allocated RBs to the UE. The starting RB is based on: a value of a frequency domain resource allocation field in a DCI, a reference RB, and a number of RBs in a first control resource set (CORESET). The length of the consecutively allocated RBs is based on: a value of a frequency domain resource allocation field in a DCI and a number of RBs in a first CORESET.

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

[0223] In some embodiments, activating the DL BWP includes allocating RBs for data transmission based on an interleaved mapping of VRB bundles to interleaved PRB bundles, wherein the starting RB is a virtual starting RB, and the length of the consecutively allocated RBs is the consecutively allocated virtual RB length, and wherein the virtual starting RB defines the start of the consecutively allocated virtual RB length.

[0224] In some embodiments, sending the data transmission includes sending the data transmission in time-frequency resources defined by an interleaved PRB bundle, the interleaved PRB bundle being based on: a virtual starting RB, the contiguously allocated virtual RB length, an interleaving map, and a reference physical RB bundle.

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

[0226] In some embodiments, the DCI is a fallback DCI.

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

[0228] 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 resources for all UEs in the group of UEs.

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

[0230] In some embodiments, the method also includes the UE determining the length of consecutively 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, wherein sending or receiving data transmission includes sending or receiving data transmission allocated in time-frequency resources defined by at least a starting RB and the length of the consecutively allocated RBs.

[0231] 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 resources for all UEs in the group of UEs.

[0232] In some embodiments, the first BWP is an activation BWP and the second BWP is an initial downlink (DL) BWP.

[0233] In some embodiments, the reference RB is at least one of: the resource element group (REG) with the smallest number in the PDCCH, in which the DCI has been decoded by the UE in the PDCCH; the physical resource block (PRB) with the smallest number in the control resource set (CORESET), in which the DCI has been decoded by the UE in the CORESET; the PRB with the smallest number in the configured CORESET with the smallest CORESET identifier (ID) in the activated BWP; the PRB with the smallest number in the initial DL BWP used by the UE; the PRB with the smallest number in the configured BWP with the smallest BWP ID; the PRB with the smallest number in the default BWP; and the PRB configured by higher-layer signaling.

[0234] In some embodiments, the reference size of the second BWP is equal to the number of RBs of at least one of the following: the number of RBs of the initial DLBWP; the number of RBs defining a control resource set (CORESET) in which the DCI has been decoded by the UE in the CORESET; the number of RBs defining a configured CORESET having a minimum CORESET identifier (ID) in the activated BWP; the number of RBs defining the size of the configured BWP having a minimum BWP ID; the number of RBs defining the size of the default BWP; and the number of RBs configured by higher layer signaling.

[0235] In some embodiments, RBs allocated for data transmission are distributed on a first BWP based on an interleaved mapping of VRB bundles to interleaved PRB bundles, wherein the start RB is a virtual start RB and the reference RB is a virtual reference RB.

[0236] In some embodiments, the method also includes the UE determining an interleaved PRB bundle for data transmission based at least on the virtual starting RB, the interleaved mapping, and the reference PRB bundle, wherein sending or receiving data transmission includes sending or receiving data transmission allocated in time-frequency resources at least partially defined by the interleaved PRB bundle.

[0237] In some embodiments, the virtual start RB defines a start of a contiguously allocated VRB length, and determining the interleaved PRB bundle comprises determining the interleaved PRB bundle further based on the contiguously allocated VRB length.

[0238] In some embodiments, the DCI is a fallback DCI.

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

[0240] In some embodiments, the computer executable instructions, when executed by the processor, further cause the UE to: determine the length of consecutively 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, wherein sending or receiving data transmission includes sending or receiving data transmission allocated in time-frequency resources defined by at least a starting RB and the length of the consecutively allocated RBs.

[0241] 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 resources for all UEs in the group of UEs.

[0242] In some embodiments, the first BWP is an activation BWP and the second BWP is an initial downlink (DL) BWP.

[0243] In some embodiments, the reference RB is at least one of: the resource element group (REG) with the smallest number in the PDCCH, in which the DCI has been decoded by the UE in the PDCCH; the physical resource block (PRB) with the smallest number in the control resource set (CORESET), in which the DCI has been decoded by the UE in the CORESET; the PRB with the smallest number in the configured CORESET with the smallest CORESET identifier (ID) in the activated BWP; the PRB with the smallest number in the initial DL BWP used by the UE; the PRB with the smallest number in the configured BWP with the smallest BWP ID; the PRB with the smallest number in the default BWP; and the PRB configured by higher-layer signaling.

[0244] In some embodiments, the reference size of the second BWP is equal to the number of RBs of at least one of the following: the number of RBs of the initial DLBWP; the number of RBs defining a control resource set (CORESET) in which the DCI has been decoded by the UE in the CORESET; the number of RBs defining a configured CORESET having a minimum CORESET identifier (ID) in the activated BWP; the number of RBs defining the size of the configured BWP having a minimum BWP ID; the number of RBs defining the size of the default BWP; and the number of RBs configured by higher layer signaling.

[0245] In some embodiments, RBs allocated for data transmission are distributed on a first BWP based on an interleaved mapping of VRB bundles to interleaved PRB bundles, wherein the start RB is a virtual start RB and the reference RB is a virtual reference RB.

[0246] In some embodiments, the computer executable instructions, when executed by the processor, further cause the UE to: determine an interleaved PRB bundle for data transmission based at least on a virtual starting RB, an interleaved mapping, and a reference PRB bundle, wherein sending or receiving data transmission comprises sending or receiving data transmission allocated in time-frequency resources at least partially defined by the interleaved PRB bundle.

[0247] In some embodiments, the virtual starting RB defines a start of a consecutively allocated virtual RB length, and determining the interleaved PRB bundle comprises determining the interleaved PRB bundle further based on the consecutively allocated VRB length.

[0248] In some embodiments, the DCI is a fallback DCI.

[0249] According to another aspect of the present disclosure, a method for wireless communication is provided. The method includes: transmitting downlink control information (DCI) in a physical downlink control channel (PDCCH) in a first bandwidth part (BWP), the DCI including a frequency domain resource allocation field, the field having a value for defining a starting resource block (RB) for data transmission to be allocated by the DCI, the starting RB being defined in combination with a reference RB and a reference size of a second BWP; and sending or receiving data transmission between a base station and a user equipment (UE).

[0250] In some embodiments, the value of the frequency domain resource allocation field further defines the length of the consecutively allocated RBs for data transmission, and wherein sending or receiving data transmission includes sending or receiving data transmission allocated in the time-frequency resources defined by at least the starting RB and the length of the consecutively allocated RBs.

[0251] In some embodiments, RBs allocated for data transmission are distributed on a first BWP based on an interleaved mapping of VRB bundles to interleaved PRB bundles, wherein the start RB is a virtual start RB and the reference RB is a virtual reference RB.

[0252] In some embodiments, an interleaved PRB bundle for data transmission is defined by a virtual starting RB, an interleaving map, a continuously allocated virtual RB length, and a reference PRB bundle, wherein transmitting or receiving data transmission includes sending or receiving data transmission allocated in time-frequency resources at least partially defined by the interleaved PRB bundle.

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

[0254] According to another aspect of the present disclosure, a device is provided, comprising a processor and a computer-readable medium having computer-executable instructions stored thereon. The computer-executable instructions, when executed by the processor, cause the device to: transmit downlink control information (DCI) in a physical downlink control channel (PDCCH) in a first bandwidth part (BWP), the DCI comprising a frequency domain resource allocation field having a value for defining a starting resource block (RB) for data transmission to be allocated by the DCI, the starting RB being defined in conjunction with a reference RB and a reference size of a second BWP; and send or receive data transmission between a base station and a user equipment (UE).

[0255] In some embodiments, the value of the frequency domain resource allocation field further defines the length of the consecutively allocated RBs for data transmission, and wherein sending or receiving data transmission includes sending or receiving data transmission allocated in the time-frequency resources defined by at least the starting RB and the length of the consecutively allocated RBs.

[0256] In some embodiments, RBs allocated for data transmission are distributed on a first BWP based on an interleaved mapping of virtual RB bundles to interleaved PRB bundles, wherein the start RB is a virtual start RB and the reference RB is a virtual reference RB.

[0257] In some embodiments, an interleaved PRB bundle for data transmission is defined by a virtual starting RB, an interleaving map, a continuously allocated VRB length, and a reference PRB bundle, wherein sending or receiving data transmission includes sending or receiving data transmission allocated in time-frequency resources at least partially defined by the interleaved PRB bundle.

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

[0259] Although the present invention has been described with reference to illustrative embodiments, this description is not intended to limit the present invention. Those skilled in the art will appreciate various modifications and combinations of the illustrative embodiments, as well as other embodiments of the present invention, after referring to this description. Therefore, the appended claims are intended to cover any such modifications or embodiments.

Claims

1. A communication method, characterized in that: The method comprises: receiving downlink control information DCI in a physical downlink control channel PDCCH of the first bandwidth part BWP, wherein the DCI includes a frequency domain resource allocation field; and, A data transmission is received, wherein resources of the data transmission are determined according to a value of the frequency domain resource allocation field, a size of the second BWP, and a reference RB.

2. The method according to claim 1, characterized in that The first BWP is an activated downlink BWP.

3. The method according to claim 1 or 2, characterized in that: The size of the second BWP is the size of the first control resource set CORESET, and the first CORESET has the smallest CORESET identifier.

4. The method according to claim 3, characterized in that The first CORESET is CORESET 0.

5. The method according to any one of claims 1 to 4, characterized in that: The reference RB is a physical resource block (PRB) with the smallest number in a second CORESET in which the DCI is received.

6. The method according to claim 5, characterized in that The reference RB is numbered as 7. The method according to claim 6, characterized in that The data transmission is a data transmission with non-interleaved virtual resource blocks VRB to physical resource blocks PRB mapping, wherein VRB n is mapped to PRB 8. The method according to any one of claims 1 to 7, characterized in that: The resource for data transmission is determined according to the value of the frequency domain resource allocation field, the size of the second BWP, and the reference RB, including: The starting RB for data transmission is determined according to the value of the frequency domain resource allocation field, the size of the second BWP and the reference RB.

9. The method according to any one of claims 1 to 8, characterized in that: The resource for data transmission is determined according to the value of the frequency domain resource allocation field, the size of the second BWP, and the reference RB, including: The length of the continuously allocated RBs for data transmission is determined according to the value of the frequency domain resource allocation field and the size of the second BWP.

10. The method according to any one of claims 1 to 9, characterized in that: The format of the DCI is DCI format 1_0.

11. The method according to any one of claims 1 to 10, characterized in that: The DCI is associated with a group of user equipments UE.

12. A communication method, characterized in that: The method comprises Sending downlink control information DCI in a physical downlink control channel PDCCH of the first bandwidth part BWP, wherein the DCI includes a frequency domain resource allocation field; as well as Sending data transmission, where resources of the data transmission are determined according to the value of the frequency domain resource allocation field, the size of the second BWP, and the reference RB.

13. The method according to claim 12, characterized in that The first BWP is an activated downlink BWP.

14. The method according to claim 12 or 13, characterized in that: The size of the second BWP is the size of the first control resource set CORESET, and the first CORESET has the smallest CORESET identifier.

15. The method according to claim 14, characterized in that The first CORESET is CORESET 0.

16. The method according to any one of claims 12 to 15, characterized in that: The reference RB is a physical resource block (PRB) with the smallest number in a second CORESET in which the DCI is received.

17. The method according to claim 16, characterized in that The reference RB is numbered as 18. The method according to claim 17, characterized in that The data transmission is a data transmission with non-interleaved virtual resource blocks VRB to physical resource blocks PRB mapping, wherein VRB n is mapped to PRB 19. The method according to any one of claims 12 to 18, characterized in that: The resource for data transmission is determined according to the value of the frequency domain resource allocation field, the size of the second BWP, and the reference RB, including: The starting RB for data transmission is determined according to the value of the frequency domain resource allocation field, the size of the second BWP and the reference RB.

20. The method according to any one of claims 12 to 19, characterized in that: The resource for data transmission is determined according to the value of the frequency domain resource allocation field, the size of the second BWP, and the reference RB, including: The length of the continuously allocated RBs for data transmission is determined according to the value of the frequency domain resource allocation field and the size of the second BWP.

21. The method according to any one of claims 12 to 20, characterized in that: The format of the DCI is DCI format 1_0.

22. The method according to any one of claims 1 to 10, characterized in that: The DCI is associated with a group of user equipments UE.

23. A device, characterized in that: Comprising means for performing the method according to any one of claims 1 to 11.

24. A device, characterized in that: Comprising means for performing the method according to any one of claims 12 to 22.

25. A device, characterized in that: include: processor; as well as A computer-readable medium having computer-executable instructions stored thereon, which, when executed by the processor, cause the UE to perform the method according to any one of claims 1 to 11.

26. A device, characterized in that include: processor; as well as A computer-readable medium having computer-executable instructions stored thereon, which, when executed by the processor, cause the UE to perform the method according to any one of claims 12 to 22.

27. A computer-readable medium storing computer-executable instructions, characterized in that: The computer executable instructions, when executed by a processor, cause an apparatus to perform a method according to any one of claims 1 to 11, 12 to 22.

28. A computer program product, characterized in that Comprising instructions for executing the method according to any one of claims 1 to 11, 12 to 22.

Images