System and method for mapping between different types of bandwidth portions - Patents.com

Abstract

Disclosed are embodiments of a system, device, and method for mapping between different types of BWPs. In some aspects, a wireless communication method includes receiving, by a wireless communication device, wireless configuration information from a wireless communication node, the wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence between the second type of BWP and a plurality of BWPs. In some aspects, the wireless communication method includes allocating, by the wireless communication device, a plurality of resources for transmission or reception based on the wireless configuration information.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE The present disclosure relates generally to wireless communications, and more particularly to systems and methods for mapping between different types of bandwidth portions for transmission or reception resource allocation. [Background technology]

[0002] The standardization organization, the 3rd Generation Partnership Project (3GPP), is currently defining a new radio interface called 5G New Radio (5G NR) and the Next Generation Packet Core Network (NG-CN or NGC). 5G NR has three main components: 5G Access Network (5G-AN), 5G Core Network (5GC), and User Equipment (UE). To realize different data services and requirements, the elements of 5GC, also called network functions, are simplified, some of them are software-based and some are hardware-based, so that they can be adapted as needed. Summary of the Invention [Means for solving the problem]

[0003] The exemplary embodiments disclosed herein aim to solve one or more problems associated with the prior art and provide additional features that will be readily apparent from the following detailed description taken in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not by way of limitation, and that those skilled in the art who read this disclosure may make various modifications to the disclosed embodiments and still fall within the scope of the present disclosure.

[0004] Disclosed are embodiments of a system, device, and method for mapping between different types of BWPs. In some aspects, a wireless communication method includes receiving, by a wireless communication device, wireless configuration information from a wireless communication node, the wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence between the second type of BWP and a plurality of BWPs. In some aspects, the wireless communication method includes allocating, by the wireless communication device, a plurality of resources for transmission or reception based on the wireless configuration information.

[0005] In some embodiments, the multiple BWPs correspond to multiple carriers. In some embodiments, a first portion of the BWP of the second type is mapped to a first BWP of the multiple BWPs, and a second portion of the BWP of the second type is mapped to a second BWP of the multiple BWPs. In some embodiments, a bandwidth of the BWP of the second type is a sum of the respective bandwidths of the multiple BWPs. In some embodiments, the wireless communication device receives scheduling information including frequency resource information based on a BWP of the second type, and the wireless communication device allocates frequency resources in the multiple BWPs to transmit or receive data.

[0006] In some aspects, a wireless communication method includes transmitting, by a wireless communication node, wireless configuration information to a wireless communication device, the wireless communication device allocating a plurality of resources for transmission or reception based on the wireless configuration information, the wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence relationship between the second type of BWP and a plurality of BWPs.

[0007] In some embodiments, the plurality of BWPs correspond to a plurality of carriers. In some embodiments, a first portion of the second type BWP is mapped to a first BWP of the plurality of BWPs, and a second portion of the second type BWP is mapped to a second BWP of the plurality of BWPs. In some embodiments, a bandwidth of the second type BWP is a sum of respective bandwidths of the plurality of BWPs. In some aspects, the wireless communication node transmits scheduling information including frequency resource information based on the second type BWP.

[0008] In some aspects, a wireless communication apparatus includes at least one processor and a memory. In some aspects, the memory includes instructions. In some aspects, the at least one processor executes instructions to receive wireless configuration information from a wireless communication node, the wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence between the second type of BWP and a plurality of BWPs. In some aspects, the at least one processor executes the instructions to allocate a plurality of resources for transmission or reception of a wireless communication device communicating with the wireless communication node based on the wireless configuration information.

[0009] In some embodiments, the multiple BWPs correspond to multiple carriers. In some embodiments, a first portion of the second type BWP is mapped to a first BWP of the multiple BWPs and a second portion of the second type BWP is mapped to a second BWP of the multiple BWPs. In some embodiments, a bandwidth of the second type BWP is a sum of the bandwidths of each of the multiple BWPs. In some embodiments, the wireless communication device receives scheduling information including frequency resource information based on a second type BWP, and the wireless communication device allocates frequency resources in the multiple BWPs for data transmission or reception.

[0010] In some aspects, a wireless communication apparatus includes at least one processor and a memory. In some aspects, the memory includes instructions. In some aspects, the at least one processor executes the instructions to transmit, to a wireless communication device, wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence between the second type of BWP and a plurality of BWPs. In some aspects, the wireless communication device allocates a plurality of resources for transmission or reception based on the wireless configuration information.

[0011] In some embodiments, the plurality of BWPs correspond to a plurality of carriers. In some embodiments, a first portion of the second type BWP is mapped to a first BWP of the plurality of BWPs, and a second portion of the second type BWP is mapped to a second BWP of the plurality of BWPs. In some embodiments, a bandwidth of the second type BWP is a sum of respective bandwidths of the plurality of BWPs. In some aspects, the wireless communication node transmits scheduling information including frequency resource information based on the second type BWP.

[0012] In some aspects, a wireless communications apparatus includes at least one processor and a memory, the at least one processor configured to read code from the memory and perform a method according to any of the preceding embodiments.

[0013] In some aspects, a computer program product includes computer readable program medium code stored therein, which when executed by at least one processor causes the at least one processor to perform a method as described in any of the above embodiments.

[0014] These and other aspects and their implementations are described in further detail in the drawings, specification, and claims. [Brief description of the drawings]

[0015] Various exemplary embodiments of the present invention will be described in detail below with reference to the figures or drawings. The drawings are provided for illustrative purposes only and merely depict exemplary embodiments of the present invention to facilitate the reader's understanding of the present invention. Thus, the drawings should not be considered as limiting the breadth, scope, or applicability of the present invention. It should be noted that for clarity and ease of illustration, the drawings are not necessarily drawn to scale. [Figure 1] 1 illustrates an example cellular communication network in which the techniques and other aspects disclosed herein may be implemented in accordance with embodiments of the present disclosure. [Diagram 2] 1 illustrates a block diagram of an example base station and user equipment device according to some embodiments of the present disclosure. [Figure 3A] FIG. 1 is a schematic diagram of carrier aggregation according to some embodiments. [Figure 3B] FIG. 2 is a schematic diagram of a second type of BWP according to some embodiments of the present disclosure. [Figure 4] A schematic diagram of a second type of BWP corresponding to two BWPs according to some embodiments of the present disclosure, and the two BWPs corresponding to two carriers. [Diagram 5] 1 is a flowchart of a UE-side process of a method according to some embodiments of the present disclosure. [Figure 6] FIG. 2 is a schematic diagram of a second type of BWP associated with a scheduler or scheduling entity according to some embodiments of the present disclosure. [Figure 7] 11 is a flowchart of a scheduling process performed by a UE based on a second type of BWP according to some embodiments of the present disclosure. [Figure 8] 1 illustrates a method for mapping between different types of BWPs according to some embodiments of the present disclosure. [Figure 9] 1 illustrates a method for mapping between different types of BWPs according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Various exemplary embodiments of the present invention will now be described with reference to the drawings to enable those skilled in the art to make and use the invention. As will be apparent to those skilled in the art upon reading this disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of the present invention.

[0017] Accordingly, the present invention is not limited to the exemplary embodiments and applications described and illustrated herein.

[0018] Additionally, any specific order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based upon design preferences, the specific order or hierarchy of steps in any disclosed method or process may be rearranged and still be within the scope of the present invention.

[0019] Thus, one skilled in the art will understand that while the methods and techniques disclosed herein are presented in a sample order of the various steps or acts, unless expressly stated otherwise, the invention is not limited to the specific order or hierarchy presented.

[0020] A. Network and Computing Environment 1 illustrates an example wireless communication network and / or system 100 in which the techniques disclosed herein may be implemented according to embodiments of the present disclosure. In the following description, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NE-IoT) network, and is referred to herein as "network 100."

[0021] Such an exemplary network 100 includes a base station 102 (hereinafter "BS 102") and user equipment devices 104 (hereinafter "UE 104") that can communicate with each other using communications links 110 (e.g., wireless communication channels), as well as a cluster of cells 126, 130, 132, 134, 136, 138, and 140 that overlay a geographic area 101. In FIG. 1, BS 102 and UE 104 are contained within respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station that operates within its allocated bandwidth and provides sufficient wireless coverage to its intended users.

[0022] For example, the BS 102 may operate with an allocated channel transmission bandwidth to provide sufficient coverage to the UE 104. The BS 102 and the UE 104 may communicate using a downlink radio frame 118 and an uplink radio frame 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, the BS 102 and the UE 104 are generally described herein as non-limiting examples of "communication nodes" capable of practicing the methods disclosed herein. Such communication nodes may be capable of wireless and / or wired communication according to various embodiments of the present invention.

[0023] 2 illustrates a block diagram of an exemplary wireless communication system 200 for transmitting and receiving wireless communication signals, e.g., OFDM / OFDMA signals, in accordance with some embodiments of the present invention. System 200 may include components and elements configured to support known or conventional operational features that need not be described in detail herein. In one illustrative embodiment, system 200 may be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment, such as wireless communication environment 100 of FIG. 1, as described above.

[0024] The system 200 generally includes a base station 202 (hereinafter "BS 202") and a user equipment device 204 (hereinafter "UE 204"). The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled and interconnected with each other, as needed, via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled and interconnected with each other, as needed, via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250, which may be any wireless channel or other medium adapted for the transmission of data as described herein.

[0025] It will be appreciated by those skilled in the art that system 200 may further include any number of modules other than those illustrated in Figure 2. It will be appreciated by those skilled in the art that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer readable software, firmware, or any practical combination thereof.

[0026] To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software may depend on the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be construed as limiting the scope of the present disclosure.

[0027] According to some embodiments, the UE transceiver 230 may be referred to herein as an “uplink” transceiver 230 and includes a radio frequency (RF) transmitter and an RF receiver, each with circuitry coupled to an antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-duplex manner.

[0028] Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each with circuitry coupled to the antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time-duplex manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time, with the uplink receiver circuitry being coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. In some embodiments, there is close time synchronization, with minimal guard time between changes in duplex direction.

[0029] The UE transceiver 230 and base station transceiver 210 are configured to communicate over a wireless data communication link 250 and cooperate with suitably configured RF antenna arrangements 212 / 232 capable of supporting a particular wireless communication protocol and modulation scheme. In some demonstrative embodiments, the UE transceiver 210 and base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and the emerging 5G standard. However, it should be understood that the present disclosure is not necessarily limited in application to a particular standard and associated protocol. Rather, the UE transceiver 230 and base station transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0030] According to various embodiments, the BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, the UE 204 may be embodied in various types of user devices, such as a mobile phone, a smartphone, a personal digital assistant (PDA), a tablet, a laptop computer, a wearable computing device, etc.

[0031] The processor modules 214 and 236 may be implemented or realized with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.

[0032] Thus, a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, etc. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

[0033] Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, firmware, a software module, or any practical combination thereof, executed by processor modules 214 and 236, respectively. Memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0034] In this regard, memory modules 216 and 234 are coupled to processor modules 210 and 230, respectively, such that processor modules 210 and 230 may read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 may be integrated within their respective processor modules 210 and 230.

[0035] In some embodiments, each of memory modules 216 and 234 may include cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively. Each of memory modules 216 and 234 also includes non-volatile memory, respectively, that stores instructions for execution by processor modules 210 and 230.

[0036] The network communications module 218 generally represents hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bidirectional communications between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communications module 218 may be configured to support Internet or WiMAX traffic.

[0037] In a typical deployment, but not limited to, the network communications module 218 provides an 802.3 Ethernet interface to enable the base station transceiver 210 to communicate with conventional Ethernet-based computer networks.

[0038] As such, the network communications module 218 may include a physical interface for connection to a computer network (e.g., a Mobile Switching Center (MSC)). The terms "configured for," "configured to," and conjugations thereof, with respect to a specified operation or function, as used herein, refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0039] B. Mapping between different types of BWPs Carrier aggregation (CA) can be used to address the poor scheduling efficiency of multi-spectral resource fusion. The present disclosure proposes embodiments of a system and method for more efficient scheduling for multi-spectral resource fusion.

[0040] Radio spectrum can be used for communication coverage of mobile networks. Many factors, including different radio spectrum policies in different countries, market-oriented radio spectrum trading, and the reallocation of spectrum resources in previous generations of mobile networks (2G and 3G networks), may lead to the fragmentation of current global spectrum resources. It may be difficult to find contiguous large-bandwidth spectrum resources, especially at low frequencies. With the acceleration of 5G commercial use and the emergence of new 6G services, new scenarios, and new applications, it may be necessary to improve the spectrum usage efficiency, especially the usage efficiency of fragmented spectrum. Efficient use of fragmented spectrum can greatly alleviate the shortage of global spectrum resources.

[0041] Carrier aggregation (CA) can be used to fuse multiple spectrum resources to improve spectrum. However, carrier aggregation has some drawbacks. Each carrier corresponds to a cellular cell, which means that CA can be equivalent to an aggregation of multiple cellular cells. Each carrier (cell) may be associated with a scheduling process, and the terminal (UE) needs to perform the scheduling process independently for each carrier, and the scheduling processes between carriers in CA may be the same or similar, which may reduce the scheduling efficiency.

[0042] When the number of aggregated carriers becomes large, the scheduling efficiency is low. Since a carrier is associated with one or more BWPs, the scheduling process may be based on the BWPs of each carrier in the CA. It may be very inefficient for a terminal (UE) to perform a scheduling process based on multiple BWPs for multiple carriers in a CA.

[0043] In some embodiments, a bandwidth portion (BWP) of a second (e.g., new, novel, aggregate, etc.) type corresponds to multiple BWPs, and these BWPs correspond to multiple carriers. In some embodiments, frequency domain resources of a BWP of the second type are mapped to frequency domain resources of multiple BWPs, a portion of the frequency domain resources of a BWP of the second type is mapped to frequency domain resources of a BWP, and another portion of the frequency domain resources of a BWP of the second type is mapped to frequency domain resources of another BWP.

[0044] In some aspects, the bandwidth of the second type BWP is equal to the sum of the bandwidths of the multiple BWPs. In some embodiments, the scheduling for the multiple BWPs for multi-spectrum fusion may be based on the second type BWP corresponding to the multiple BWPs. It may be more efficient for the terminal (UE) to perform the scheduling process for multi-spectrum fusion in the above manner.

[0045] In some embodiments, a user equipment (UE, e.g., UE 104, UE 204, mobile device, wireless communication device, terminal, etc.) schedules data transmission or reception processing based on the second type of BWP. In some embodiments, data on the second type of BWP and frequency domain resources (including but not limited to resource blocks (RBs), resource units (REs), and control channel elements (CCEs)) assigned to the data in the second type of BWP are mapped to multiple BWPs. The UE can perform physical layer processing, including transmission and reception of data and signals, based on the BWP.

[0046] In some aspects, a BWP is a subset of a contiguous block of common resources (CRBs) that corresponds to a particular subcarrier interval on a given carrier. In some embodiments, the start of the frequency domain and the number of RBs included in the BWP must respectively satisfy the following formula:

[0047]

number

[0048]

number

[0049] For a downlink carrier, the UE configures up to four downlink BWPs and activates up to one BWP at a given time. In some aspects, the UE is configured not to receive a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), or a channel state information reference signal (CSI-RS) (except for radio resource management (RRM)) in a frequency region outside the BWP.

[0050] For an uplink carrier, the UE configures up to four uplink BWPs and activates up to one BWP in a given time. If the UE is configured with a supplemental uplink (SUL), the UE can additionally configure up to four uplink BWPs on the SUL carrier and activate up to one BWP in a given time. In some embodiments, the UE does not transmit a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH) in a frequency region outside the activated BWP. In some aspects, for an activated carrier, the UE does not transmit a sounding reference signal (SRS) in a frequency region outside the activated BWP.

[0051] In some aspects, for each carrier and each subcarrier spacing, a resource grid is defined in the uplink or downlink transmission direction, respectively, where the resource grid comprises a series of consecutive subcarriers and a series of consecutive time domain OFDM symbols. The carrierBandwidth of the radio resource control RRC information element IE SCS-SpecificCarrier configures the bandwidth of the resource grid, and the offsetToCarrier of the radio resource control information element (RRC IE) SCS-SpecificCarrier configures the frequency domain starting position of the resource grid.

[0052] Furthermore, txDirectCurrentLocation in the RRC IE UplinkTxDirectCurrentBWP and txDirectCurrentLocation in the SCS-SpecificCarrier configure the frequency domain location of the DC subcarrier on the upstream and downstream sides of the resource grid, respectively.

[0053] The RRC IE SCS-SpecificCarrier provides configuration parameters for the carrier bandwidth at the subcarrier spacing level, which determine the frequency domain location of the carrier bandwidth (see point A) and the width of the frequency domain range of the carrier bandwidth. For each subcarrier spacing corresponding to a BWP, an RRC IE SCS-SpecificCarrier is configured.

[0054] Carrier aggregation (CA) aggregates multiple carriers to improve the throughput of UEs with a wider bandwidth of frequency domain resources. However, carrier aggregation has some drawbacks. Each carrier is associated with a scheduling process. The terminal (UE) needs to perform the scheduling process for data transmission or reception for each carrier independently. In some scenarios, the cross-carrier scheduling process is repeated, which may increase the scheduling overhead of the terminal (UE) and reduce the scheduling efficiency. Since the scheduling process is performed based on one or more BWPs for each carrier in CA, it may be very inefficient for the terminal (UE) to perform the scheduling process based on multiple BWPs in CA.

[0055] The UE may need to perform a scheduling process, including frequency domain resource allocation for data transmission or reception on each carrier based on the bandwidth and frequency location of each carrier. In addition, the UE may need to receive scheduling indication information for each carrier. Although cross-carrier scheduling helps CA save scheduling resources, when the number of carriers is large, the overhead of scheduling resources is still large and the scheduling efficiency is still too low.

[0056] As mentioned above, the scheduling process for carriers in CA may be the same or similar, and the UE may perform multiple repeated processes, which may consume (e.g., over-consumption, waste, etc.) the scheduling and processing resources of the terminal, resulting in reduced scheduling efficiency. Figure 3A is a schematic diagram of carrier aggregation according to some embodiments. Compared with the independent scheduling process for each carrier in CA, the one scheduling process for multiple carriers in the fusion of multi-spectrum resources may improve the scheduling efficiency to a higher degree.

[0057] In the present disclosure, a second type of BWP is disclosed. The second type of BWP, also called a virtual BWP, corresponds to a set of consecutive resource blocks (RBs) with a certain subcarrier interval, corresponds to multiple carriers or multiple BWPs, and corresponds to a scheduling process for data transmission and reception. Within the second type of BWP, the UE can perform a scheduling process indicated by the scheduling information. In some embodiments in which the UE performs the scheduling process, the UE allocates frequency domain resources (RB resources) for data in the frequency domain of the second type of BWP, and then the data and frequency domain resources on the second type of BWP are mapped to multiple BWPs for transmission.

[0058] These BWPs are on or correspond to multiple carriers. In some embodiments in which the UE performs the scheduling process according to the mapping between the frequency domain resources (RB resources) on the second type BWP indicated by the scheduling information and the second type BWP and multiple BWPs on or corresponding to multiple carriers, the UE receives data on the BWP and maps the data to the second type BWP based on the frequency domain resources of the BWP mapped from the indicated frequency domain resources of the second type BWP. The UE can then perform subsequent processing of the data on the second type BWP.

[0059] Multiple BWPs (carriers) can be mapped to continuous frequency domain resources (second type BWPs). In some embodiments, the UE performs scheduling or resource allocation based only on the continuous frequency domain resources, thereby simplifying the iterative process, reducing processing overhead, and improving scheduling efficiency.

[0060] Some embodiments of the present disclosure may also save processing overhead of a base station (BS, e.g., BS102, BS202, next-generation Node B (gNB), evolved Node B (eNB), wireless communication node, cell tower, 3GPP wireless access device, non-3GPP wireless access device, etc.). In some embodiments, multiple BWPs correspond to a second type of BWP (e.g., multiple carriers correspond to multiple BWPs, multiple BWPs correspond to one BWP, and one second type BWP corresponds to one cell), thereby reducing the workload of cell management. FIG. 3B is a schematic diagram of one embodiment of a second type of BWP in the present disclosure.

[0061] One embodiment provides a second type BWP corresponding to multiple BWPs, each BWP corresponding to one or more carriers. FIG. 4 is a schematic diagram of a second type BWP corresponding to two BWPs, these two BWPs corresponding to two carriers. In the embodiment of FIG. 4, the second type BWP1 corresponds (e.g., maps, converts, points, associates, etc.) to BWP1 and BWP2. In the embodiment of FIG. 4, Bandwidth3 (bandwidth of the second type BWP1) is equal to the sum of Bandwidth1 (bandwidth of BWP1) and Bandwidth2 (bandwidth of BWP2). In the embodiment of FIG. 4, BWP1 corresponds to carrier 1, and BWP2 corresponds to carrier 2.

[0062] In some embodiments, the second type of BWP corresponds to a subcarrier spacing (SCS), and the subcarrier spacing configuration μ can be 0, 1, 2, ..., each representing a multiple of a reference subcarrier spacing, including but not limited to 15KHz. In some embodiments, the BWP corresponds to a subcarrier spacing (SCS). The subcarrier spacing configuration μ can be 0, 1, 2, ..., each representing a multiple of a reference subcarrier spacing, including but not limited to 15KHz.

[0063] The second type of BWP may be associated with control operations for data transmission and reception, such as scheduling operations, radio resource configuration, etc. The second type of BWP may be associated with a Medium Access Control (MAC) entity, a scheduler, a Radio Resource Control (RRC) entity, or a Radio Resource Management entity.

[0064] In some embodiments, the second type of BWP is associated with physical resource configurations, including physical channel configurations and physical reference signal configurations. The physical channel configurations include a physical uplink shared channel or a physical downlink shared channel (PUSCH or PDSCH) configuration, a physical uplink control channel or a physical downlink control channel (PUCCH or PDCCH) configuration, and a physical random access channel (PRACH) configuration. Among them, the physical uplink shared channel or the physical downlink shared channel configuration includes, but is not limited to, a time domain resource allocation configuration, a frequency domain resource allocation type configuration, a modulation and coding scheme table configuration, and an uplink power control related configuration.

[0065] The physical uplink control channel or physical downlink control channel includes, but is not limited to, a downlink control resource set (CORESET) configuration, a search space configuration, a PUCCH resource set configuration, a scheduling request configuration, and a downlink feedback timing sequence configuration. The physical reference signal configuration includes, but is not limited to, a demodulation reference signal (DMRS) configuration, a channel state information (CSI) measurement configuration, a sounding reference signal (SRS) configuration, and a phase tracking reference signal (PTRS) configuration.

[0066] The second type of BWP may include one physical channel configuration for one or more same-type physical channels, including one or more PUSCH / PDSCH, one or more PUCCH / PDCCH, and one or more PRACH. The second type of BWP may include one physical reference signal configuration for one or more same-type physical reference signals, including one or more DMRS, one or more CSI measurements, one or more SRS, and one or more PTRS.

[0067] One BWP may correspond to one or more carriers, and one carrier may correspond to one or more BWPs.

[0068] In one embodiment, one second type BWP corresponds to multiple BWPs, and these BWPs correspond to multiple carriers. The second type BWP may be mapped to multiple BWPs. A part of the set of RBs of the second type BWP may be mapped to the set of RBs of one BWP. Another part of the set of RBs of the second type BWP may be mapped to the set of RBs of another BWP. The bandwidth of the second type BWP may be equal to the sum of the bandwidths of the BWPs corresponding to the multiple BWPs.

[0069] In one example, the second type BWP corresponds to two BWPs, and the bandwidths of the two BWPs are 60 MHz and 40 MHz, respectively. The second type BWP can be mapped to these two BWPs. The bandwidth of the second type BWP is equal to the sum of the bandwidths of the two BWPs, which is 60 MHz + 40 MHz = 100 MHz. 60% of the frequency domain resources of the second type BWP can be mapped to the BWP with a bandwidth of 60 MHz, and 40% of the frequency domain resources of the second type BWP can be mapped to the BWP with a bandwidth of 40 MHz.

[0070] In some embodiments, the UE performs a scheduling process indicated by the scheduling information in the second type BWP, including allocating frequency domain resource blocks (RBs) for one or more PUSCHs or determining frequency domain resource blocks (RBs) for one or more PDSCHs. The RB resources allocated to one or more PUSCHs in the second type BWP are used to map to the RB resources of the corresponding BWP to transmit one or more PUSCHs.

[0071] According to the RB resources for one or more PDSCHs on the second type BWP indicated by the scheduling information and the mapping between the second type BWP and the BWP, the UE can receive one or more PDSCHs on the BWP and map it to the second type BWP. The following processing for one or more PDSCHs can be performed based on the second type BWP.

[0072] For a communication node such as a base station or a terminal, the mapping between the second type BWP and the BWP may be performed within a module (e.g., a processor, a component, a system on chip, etc.) responsible for baseband processing. The baseband processing may include, but is not limited to, radio resource management, radio resource allocation, or scheduling. Within the module, the second type BWP may be mapped to multiple BWPs, and data and signals on the second type BWP may be mapped to corresponding BWPs.

[0073] FIG. 5 is a flowchart of the UE side processing of the method of the present disclosure in one embodiment.

[0074] Step 1: A UE receives configuration information, where the configuration information includes a BWP configuration, a configuration of a second type of BWP, and a carrier configuration. In some embodiments, the configuration information includes a correspondence relationship between the second type of BWP and the BWP. The correspondence relationship may be in the configuration information of the second type of BWP, in the BWP configuration information, or may be indicated separately.

[0075] In some embodiments, the correspondence between the second type BWPs and the BWPs in the configuration information includes one second type BWP corresponding to multiple BWPs. In some aspects, these BWPs are for multiple carriers. In some aspects, one or more second type BWPs may be configured according to a configuration of the second type BWP included in the configuration information. In some aspects, multiple BWPs may be configured according to a configuration of the BWP included in the configuration information. In some aspects, multiple carriers may be configured according to a carrier configuration included in the configuration information. In some embodiments, the bandwidth of the second type BWP is equal to the sum of the bandwidths of the multiple BWPs.

[0076]

number

[0077] In some embodiments of the present disclosure, the correspondence between the second type of BWP and the BWP includes a correspondence between the second type of BWP and a plurality of BWPs having the same subcarrier spacing. In some embodiments, the correspondence between the second type of BWP and the BWP includes a correspondence between the second type of BWP and a plurality of BWPs having different subcarrier spacing.

[0078] In the prior art, up to four BWPs can be configured in one direction (uplink or downlink) of a serving cell configuration. The BWP configuration includes, but is not limited to, the context included in the radio resource control information element (RRC IE) BWP.

[0079] BWP::=SEQUENCE { locationAndBandwidth, subcarrierSpacing, ... }, Here, locationAndBandwidth represents the frequency domain location and bandwidth of the BWP, and subcarrierSpacing represents the subcarrier spacing of the BWP.

[0080] In the prior art, in one direction (uplink or downlink) of a serving cell configuration, multiple carriers with different subcarrier spacings can be configured, but only one carrier can be configured for each subcarrier spacing.

[0081] The carrier configuration may include a context contained in the radio resource control information element (RRC IE) SCS-SpecificCarrier.

[0082] SCS-SpecificCarrier::=SEQUENCE{ offsetToCarrier, subcarrierSpacing, carrierBandwidth, ... },

[0083] Here, SCS-SpecificCarrier represents the subcarrier spacing-specific configuration of the carrier, offsetToCarrier represents the frequency domain offset between the carrier and the frequency domain reference point PointA, which determines the frequency domain location of the carrier, subcarrierSpacing represents the subcarrier spacing of the carrier, and carrierBandwidth represents the bandwidth of the carrier.

[0084] In some embodiments of the present disclosure, the configuration of the second type BWP is included in a cell configuration, and the cell configuration may include a serving cell configuration (which is the same as or similar to the configuration information indicated by the ServingCellConfig IE) and a serving cell configuration common part (which is the same as or similar to the configuration information indicated by the ServingCellConfigCommon IE). The configuration of the second type BWP may include a second type BWP index, a subcarrier spacing, and a bandwidth.

[0085] The representation of the correspondence between the second type of BWP and the BWP may include: (a) a configuration of the second type of BWP includes an index of the BWP; or (b) a configuration of the BWP includes an index of the second type of BWP; or (c) a single configuration information includes an index of the second type of BWP and an index of the BWP.

[0086] In some embodiments, the carrier configuration list is included in a subcarrier spacing-specific carrier configuration (same or similar to the configuration information indicated by the SCS-SpecificCarrier IE). The carrier configuration list may include one or more carrier configurations. That is, the carrier configuration list may include one or more carriers with the same subcarrier spacing. The carrier configuration may include a carrier index, a frequency domain location (lowest frequency point, center frequency point, or offset relative to a reference point), a bandwidth, and a subcarrier spacing.

[0087] The representation of the correspondence between the carrier and the BWP may include: (a) a configuration of the carrier includes an index of the BWP; or (b) a configuration of the BWP includes an index of the carrier; or (c) a single configuration information includes a carrier index and a BWP index.

[0088] In this embodiment, the configuration of the carrier, the configuration of the second type BWP, the configuration of the correspondence between the second type BWP and the BWP, and the representation of the correspondence between the carrier and the BWP in a radio resource control information element (RRC IE) include at least one of the following methods:

[0089] Method 1: The first RRC IE represents the configuration information of the second type BWP, including the second type BWP index, the bandwidth, and the corresponding BWP index list. The second RRC IE represents the configuration information of the BWP, including the BWP index, the bandwidth, and the corresponding carrier index. The third RRC IE represents the configuration information of the carrier, including the carrier index, the frequency domain location, and the bandwidth. The method can be shown in the following pseudo code.

[0090] Second type BWP configuration::=SEQUENCE{ Second type BWP index INTEGER(1..max number of second type BWP index), Bandwidth INTEGER(1..max number of RB), CorrespondingBWP index list SEQUENCE(SIZE (1..max number of BWP index)) OF BWP index, ... }, BWP configuration::=SEQUENCE BWP index INTEGER(1..max number of BWP index), Bandwidth INTEGER(1..max number of RB), Corresponding carrier index INTEGER(1..max number of carrier index), ... }, Carrier configuration::=SEQUENCE{ Carrier index INTEGER(1..max number of carrier index), Bandwidth INTEGER(1..max number of RB), Frequency domain position INTEGER(1...N), ... }

[0091] The configuration of the second type of BWP, the BWP configuration, and the carrier configuration are not limited to the above. The frequency domain position in the carrier configuration can be the lowest frequency point, the center frequency point, or an offset relative to a reference point. N can be used to indicate the value range of the frequency domain position.

[0092] Method 2: The first RRC IE represents the configuration information of the second type BWP, including the second type BWP index and the bandwidth. The second RRC IE represents the configuration information of the BWP, including the BWP index, the bandwidth, and the index of the corresponding second type BWP. The third RRC IE represents the configuration information of the carrier, including the carrier index, the frequency domain location, the bandwidth, and the corresponding BWP index list. The method can be shown in the following pseudo code.

[0093] Second type BWP configuration::=SEQUENCE{ Second type BWP index INTEGER(1..max number of second type BWP index), Bandwidth INTEGER(1..max number of RB), ... }, BWP configuration::=SEQUENCE BWP index INTEGER(1..max number of BWP index), Bandwidth INTEGER(1..max number of RB), Corresponding second type BWP index INTEGER(1..max number of second type BWP index), ... }, Carrier configuration::=SEQUENCE{ Carrier index INTEGER(1..max number of carrier index), Bandwidth INTEGER(1..max number of RB), Frequency domain position INTEGER(1...N), The corresponding BWP index list SEQUENCE (SIZE (1..max number of BWP index)) OF BWP index, ... }

[0094] The configuration of the second type BWP, the BWP configuration, and the carrier configuration are not limited to the above. The frequency domain position in the carrier configuration can be the lowest frequency point, the center frequency point, and the offset relative to the reference point. N can be used to indicate the value range of the frequency domain position.

[0095] Method 3: The first RRC IE indicates configuration information of the second type BWP, including a second type BWP index and a bandwidth. The second RRC IE indicates configuration information of the BWP, including a BWP index and a bandwidth. The third RRC IE indicates configuration information of the carrier, including a carrier index, a frequency domain location, and a bandwidth. The fourth RRC IE indicates configuration information of the correspondence between the second type BWP and the BWP, including a second type BWP index and a BWP index list.

[0096] The RRC IE indicates a correspondence between a second type BWP (corresponding to a second type BWP index) and a BWP (corresponding to a BWP index in the BWP index list). A fifth RRC IE indicates configuration information of correspondence between BWPs and carriers, including a correspondence list including a plurality of correspondence configurations. Each correspondence configuration includes a BWP index and a carrier index. The correspondence configuration indicates a correspondence between a BWP (corresponding to a BWP index) and a carrier (corresponding to a carrier index). The method can be shown in the following pseudo code:

[0097] Second type BWP configuration::=SEQUENCE{ Second type BWP index INTEGER(1..max number of second type BWP index), Bandwidth INTEGER(1..max number of RB), ... }, BWP configuration::=SEQUENCE BWP index INTEGER(1..max number of BWP index), Bandwidth INTEGER(1..max number of RB), ... }, Carrier configuration::=SEQUENCE{ Carrier index INTEGER(1..max number of carrier index), Bandwidth INTEGER(1..max number of RB), Frequency domain position INTEGER(1...N), ... }, Correspondence between second type BWP and BWP configuration::=SEQUENCE{ second type BWP index INTEGER(1..max number of second type BWP index), BWP index list SEQUENCE(SIZE(1..max number of BWP index)) OF BWP index, ... }, Correspondence between BWP and carrier configuration::=SEQUENCE{ Correspondence list SEQUENCE(SIZE(1..max number of correspondences)) OF correspondence, Correspondence::=SEQUENCE{ BWP index INTEGER(1..max number of BWP index), Carrier index INTEGER(1..max number of carrier index), ... }, ... },

[0098] The configuration of the correspondence relationship between the second type BWP and the BWP indicates a correspondence relationship between the second type BWP (corresponding to the BWP index of the second type) and the BWP (corresponding to the BWP index in the BWP index list). The configuration of the correspondence relationship between the BWP and the carrier indicates a correspondence relationship between the BWP (corresponding to the BWP index) and the carrier (corresponding to the carrier index).

[0099] The configuration of the second type BWP, the BWP configuration, the carrier configuration, the correspondence between the second type BWP and the BWP configuration, and the correspondence between the BWP and the carrier configuration are not limited to the above. The frequency domain position in the carrier configuration can be the lowest frequency point, the center frequency point, or an offset relative to a reference point. N can be used to indicate the range of values ​​of the frequency domain position.

[0100] In an example of Method 1, a second type BWP with a bandwidth of 100 MHz corresponds to three BWPs, and the bandwidths of these BWPs are 50 MHz, 30 MHz, and 20 MHz, respectively. The configuration information of the second type BWP includes a second type BWP index field set to 1, a bandwidth field set to 100 MHz, and corresponding BWP index list fields set to 1, 2, and 3. The corresponding BWP index list fields correspond to the first BWP, the second BWP, and the third BWP, respectively.

[0101] In this example, the configuration information for the first BWP includes a BWP index field set to 1, a bandwidth field set to 50 MHz, and a corresponding carrier index field set to 1. The configuration information for the second BWP includes a BWP index field set to 2, a bandwidth field set to 30 MHz, and a corresponding carrier index field set to 2. The configuration information for the third BWP includes a BWP index field set to 3, a bandwidth field set to 20 MHz, and a corresponding carrier index field set to 3.

[0102] In this example, the carrier indexes in the corresponding carrier index fields correspond to a first carrier, a second carrier, and a third carrier, respectively. The configuration information of the first carrier includes a carrier index field set to 1 and a bandwidth field set to 50 MHz. The configuration information of the second carrier includes a carrier index field set to 2 and a bandwidth field set to 30 MHz. The configuration information of the third carrier includes a carrier index field set to 3 and a bandwidth field set to 20 MHz.

[0103] In this example, the UE obtains the above seven configuration information (e.g., the second type BWP, the first BWP, the second BWP, the third BWP, the first carrier, the second carrier, and the third carrier). The second type BWP1 with a bandwidth of 100 MHz corresponds to the first BWP with a bandwidth of 50 MHz, the second BWP with a bandwidth of 30 MHz, and the third BWP with a bandwidth of 20 MHz. The first BWP corresponds to the first carrier with a bandwidth of 50 MHz, the second carrier corresponds to the second carrier with a bandwidth of 30 MHz, and the third BWP corresponds to the third carrier with a bandwidth of 20 MHz.

[0104] In some embodiments, the correspondence between the second type BWP and the BWP is configured via an RRC message, the RRC message including an RRCsetup, an RRCReconfiguration, a ReconfigurationWithSync, or a system message. In some embodiments, the system message includes an SIB1. In some aspects, a system message received by a UE in an IDLE state or an INACTIVE state includes the correspondence, and an RRCsetup and / or an RRCReconfiguration received by a UE in a CONNECTED state includes the correspondence. In some embodiments, a ReconfigurationWithSync received by a UE during a handover process includes the correspondence. In some embodiments, the correspondence between the second type BWP and the BWP is changed via high layer signaling, the high layer signaling includes an RRCReconfiguration.

[0105] In some embodiments, the configuration of the correspondence between the second type BWP and the BWP may be a UE-specific configuration, or a cell group-specific configuration, or a cell-specific configuration. UE-specific configuration: The correspondence is used for all cells configured by the UE. Cell group-specific configuration: The correspondence is used for all cells in each cell group, but the correspondence between cell groups configured by the UE is configured independently. Cell-specific configuration: The correspondence between cells configured by the UE is configured independently.

[0106] Step 2: Referring to FIG. 5, the UE configures a BWP, a second type of BWP, and a carrier. The UE can configure a correspondence relationship between the second type of BWP and the BWP, and a correspondence relationship between the BWP and the carrier. The correspondence relationship between the second type of BWP and the BWP includes that the second type of BWP corresponds to multiple BWPs. The bandwidth of the second type of BWP may be equal to the sum of the bandwidths of the multiple BWPs. The correspondence relationship between the BWP and the carrier may include that each BWP corresponds to one carrier, or that multiple BWPs correspond to multiple carriers.

[0107] A BWP of the second type can be mapped to multiple BWPs. A part of the frequency domain resources of the BWP of the second type is mapped to the frequency domain resources of one BWP, and another part of the frequency domain resources is mapped to the frequency domain resources of another BWP. A BWP of the second type can be mapped to BWPs with the same subcarrier spacing or BWPs with different subcarrier spacing.

[0108] In some embodiments, the UE can perform a scheduling process based on the second type BWP and the correspondence between the second type BWP and the BWP. In some embodiments, the second type BWP is associated with a scheduler, or a scheduling entity, or a MAC entity. The scheduling process may include uplink scheduling and downlink scheduling. As shown in FIG. 6, the second type BWP is associated with the scheduler or the scheduling entity, and the UE receives scheduling information (DCI) for the second type BWP and receives or transmits data on the BWP.

[0109] FIG. 7 is a flowchart of a scheduling process performed by a UE based on a second type of BWP.

[0110] For uplink data transmission: In step 1, the UE may receive uplink scheduling information, including frequency domain resource information, based on a BWP of a second type. In some embodiments, the uplink scheduling information includes frequency domain resource information for data transmission, where the frequency domain resource information indicates a set of RBs of one or more BWPs on the second type.

[0111] In step 2, the UE may determine a set of RBs on the multiple BWPs, where the set of RBs is mapped from the set of RBs indicated in the second type BWP according to the mapping between the second type BWPs and the BWPs.

[0112] In step 3, the UE may transmit data for a set of RBs on multiple BWPs, which correspond to multiple carriers and thus are equivalent to transmitting data on multiple carriers.

[0113] For example, the second type BWP1 is mapped with two BWPs, BWP1 and BWP2. The second type BWP1 may have a bandwidth of 100 RBs. BWP1 may have a bandwidth of 50 RBs, and BWP2 may have a bandwidth of 50 RBs. The UE may receive uplink scheduling information and downlink control information (DCI) on the second type BWP1.

[0114] The DCI may indicate 100 RBs in BWP1 of the second type. The first 50 RBs on BWP1 of the second type may be mapped to 50 RBs on BWP1, and the remaining 50 RBs on BWP1 of the second type may be mapped to 50 RBs on BWP2. The UE may determine 50 RBs on BWP1 and 50 RBs on BWP2, totaling 100 RBs, to transmit data. The UE may transmit data in the 50 RBs in BWP1 and the 50 RBs in BWP2.

[0115] For downlink data reception: In step 1, the UE may receive downlink scheduling information including frequency domain resource information based on the second type BWP. In some embodiments, the downlink scheduling information includes frequency domain resource information for receiving data, and the frequency domain resource information indicates a set of RBs on the second type BWP.

[0116] In step 2, the UE may determine a set of RBs on multiple BWPs, where the set of RBs is mapped from the set of RBs indicated on the second type BWP according to the mapping between the second type BWPs and the BWPs.

[0117] In step 3, the UE may receive data for a set of RBs on multiple BWPs, which correspond to multiple carriers and thus are equivalent to receiving data on multiple carriers.

[0118] For example, the second type BWP1 is mapped with two BWPs, BWP1 and BWP2. The second type BWP1 may have a bandwidth of 100 RBs. BWP1 may have a bandwidth of 50 RBs, and BWP2 may have a bandwidth of 50 RBs. The UE may receive downlink scheduling information, downlink control information (DCI), on the second type BWP1. The DCI may indicate 100 RBs on the second type BWP1.

[0119] The first 50 RBs on BWP1 of the second type may be mapped to 50 RBs on BWP1, and the remaining 50 RBs on BWP1 of the second type may be mapped to 50 RBs on BWP2. The UE may determine 50 RBs on BWP1 and 50 RBs on BWP2, totaling 100 RBs, for receiving data. The UE may receive data in the 50 RBs of BWP1 and the 50 RBs of BWP2.

[0120] According to some embodiments, a method of frequency domain resource allocation based on a mapping between a BWP of a second type and a BWP is provided. In some embodiments, a UE can configure a mapping between a BWP of a second type and a BWP. The UE can receive scheduling information related to the BWP of the second type, and the scheduling information can include frequency domain resource allocation information.

[0121] The frequency domain resource allocation information may indicate the frequency domain resource allocation by indicating the RB start and RB number of the frequency domain resource. A resource indication value (RIV) may be used to indicate the RB start and RB number. The RB start and RB number may be used to represent the frequency domain resource of the second type of BWP. The RB start and RB number are more suitable for representing the continuous frequency domain resource of the second type of BWP. The frequency domain resource indicated in the second type of BWP is mapped to the frequency domain resource on the BWP, i.e., a set of RBs.

[0122] For example, the second type BWP1 is mapped to two BWPs (BWP1 and BWP2). The second type BWP1 may have a bandwidth of 100 RBs (RB0 to RB99). BWP1 may have a bandwidth of 50 RBs, RB0 to RB49, and BWP2 may have a bandwidth of 50 RBs, RB0 to RB49. The frequency domain resource allocation information (RIV) may indicate that the RB start is 0 and the RB number is 100, which means that the 100 RBs (RB0 to RB99) on the second type BWP1 may be the frequency domain resources indicated by the RIV.

[0123] The first 50 RBs, RB0 to RB49, on the second type BWP1 may be mapped to frequency domain resources, RB0 to RB49, on BWP1, and the other 50 RBs, RB50 to RB99, on the second type BWP1 may be mapped to frequency domain resources, RB0 to RB49, on BWP2. For any RBx, the x in RBx is the RB index, and RBx represents the (x+1)th RB.

[0124] Another method of frequency domain resource allocation based on a mapping between a BWP of a second type and a BWP in some embodiments is provided. In some embodiments, the UE can configure a mapping between a BWP of a second type and a BWP. The UE can receive scheduling information related to the BWP of the second type, and the scheduling information can include frequency domain resource allocation information.

[0125] The frequency domain resource allocation information may indicate a resource block group (RBG) allocation, where an RBG may include one or more consecutive RBs. The bandwidth of the second type of BWP may be divided into several RBGs by RRC configuration or pre-definition of a standard specification. A set of frequency domain resources, RBGs, indicated on the second type of BWP may be mapped to a set of frequency domain resources, RBs, on the BWP.

[0126] For example, the second type BWP1 is mapped to two BWPs (BWP1 and BWP2). The second type BWP1 may have a bandwidth of 100 RBs (RB0 to RB99). BWP1 may have a bandwidth of 50 RBs, RB0 to RB49, and BWP2 may have a bandwidth of 50 RBs, RB0 to RB49. If the RBG size is 10, the bandwidth of the second type BWP1 may be divided into 10 RBGs, RBG0 to RBG9. The frequency domain resource allocation information may indicate five RBGs, RBG0, RBG2, RBG4, RBG5, and RBG7.

[0127] RBG0, RBG2, and RBG4 on the second type BWP1 may be mapped to frequency domain resources RB0-RB9, RB20-RB29, and RB40-RB49 on BWP1, and RBG5 and RBG7 on the second type BWP1 may be mapped to frequency domain resources RB0-RB9 and RB20-RB29 on BWP2. For any RBx, x in RBx is an RB index, and RBx represents the (x+1)th RB.

[0128] 8 illustrates a method 800 for mapping between different types of BWPs according to some embodiments of the present disclosure. With reference to FIGS. 1-7, in some embodiments, the method 800 may be performed by a wireless communication device (e.g., UE) and / or a wireless communication node (e.g., base station, gNB). Depending on the embodiment, additional, fewer, or different operations may be performed in the method 800.

[0129] In brief overview, in some embodiments, a wireless communication device receives 810 wireless configuration information from a wireless communication node, the wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence between the second type of BWP and multiple BWPs. In some aspects, the wireless communication device allocates 820 multiple resources for transmission or reception based on the wireless configuration information.

[0130] More specifically, at operation 810, in some embodiments, the wireless communication device receives wireless configuration information from a wireless communication node, the wireless communication device including a configuration of a second type of bandwidth portion (BWP) and a correspondence between the second type of BWP and multiple BWPs. In some embodiments, the wireless communication device is a UE and the wireless communication node is a BS.

[0131] In some embodiments, the multiple BWPs correspond to multiple carriers. In some embodiments, a first portion of the BWP of the second type is mapped to a first BWP of the multiple BWPs, and a second portion of the BWP of the second type is mapped to a second BWP of the multiple BWPs. In some embodiments, the bandwidth of the BWP of the second type is a sum of the respective bandwidths of the multiple BWPs. In some embodiments, the wireless communication device receives scheduling information including frequency resource information based on the BWP of the second type, and the wireless communication device allocates frequency resources in the multiple BWPs for data transmission or reception.

[0132] At operation 820, in some embodiments, the wireless communication device allocates a plurality of resources for transmission or reception based on the radio configuration information. In some embodiments, the wireless communication device allocates a plurality of resources for transmission or reception by determining a plurality of respective frequency domain resources in the BWP of the second type for a plurality of channels, respectively determining a plurality of frequency domain resources in the BWP mapped from the BWP of the second type, and respectively transmitting the plurality of channels on the plurality of BWPs. The frequency domain resources may include one or more resource blocks (RBs), resource units (REs), or control channel units (CCEs). The channels may include one or more uplink or downlink channels.

[0133] 9 illustrates a method 900 for mapping between different types of BWPs according to some embodiments of the present disclosure. With reference to FIGS. 1-7, in some embodiments, the method 900 may be performed by a wireless communication device (e.g., UE) and / or a wireless communication node (e.g., base station, gNB). Depending on the embodiment, additional, fewer, or different operations may be performed in the method 900.

[0134] In brief overview, in some embodiments, a wireless communication node transmits wireless configuration information to a wireless communication device, the wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence between the second type of BWP and the plurality of BWPs. In some aspects, the wireless communication device allocates a plurality of resources for transmission or reception based on the wireless configuration information.

[0135] More specifically, in operation 910, in some embodiments, the wireless communication node transmits wireless configuration information to the wireless communication device, the wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence relationship between the second type of BWP and the plurality of BWPs. In some embodiments, the wireless communication device is a UE and the wireless communication node is a BS.

[0136] In some embodiments, the multiple BWPs correspond to multiple carriers. In some embodiments, a first portion of the BWP of the second type is mapped to a first BWP of the multiple BWPs and a second portion of the BWP of the second type is mapped to a second BWP of the multiple BWPs. In some embodiments, the bandwidth of the BWP of the second type is a sum of the respective bandwidths of the multiple BWPs. In some aspects, the wireless communication node transmits scheduling information including frequency resource information based on the BWP of the second type.

[0137] In some embodiments, the second type of BWP is associated with a number of processes including at least one of scheduling, radio resource allocation, or radio resource management.

[0138] In some embodiments, the wireless configuration information indicates a correspondence between the second type of BWP and the plurality of BWPs. In some embodiments, the correspondence is indicated in a configuration of the second type of BWP, a configuration of the plurality of BWPs, or a separate configuration that is independent of the configuration of the second type of BWP and the configuration of the plurality of BWPs. In some aspects, the correspondence between the second type of BWP and the plurality of BWPs is indicated in the wireless configuration information through a manner in which the plurality of BWP indexes are included in the configuration of the second type of BWP.

[0139] In some embodiments, the correspondence between the second type BWP and the plurality of BWPs is indicated in the radio configuration information through a method in which a BWP index of the second type is included in a configuration of the plurality of BWPs. In some embodiments, the correspondence between the second type BWP and the plurality of BWPs is indicated in a separate configuration in the radio configuration information, the separate configuration including a BWP index of the second type and a plurality of BWP indexes.

[0140] In some embodiments, the radio configuration information includes a cell configuration including a configuration of a second type of BWP, and the cell configuration may be similar to the configuration information indicated by the ServingCellConfig IE or the ServingCellConfigCommon IE. In some embodiments, the configuration of the second type of BWP includes at least one of a second type of BWP index, a subcarrier spacing, or a bandwidth.

[0141] At operation 920, in some embodiments, the wireless communication device allocates resources for transmission or reception based on the radio configuration information. In some aspects, the wireless communication device allocates resources for transmission or reception by determining a plurality of respective frequency domain resources in a BWP of the second type for a plurality of channels, determining a plurality of frequency domain resources in the plurality of BWPs mapped from the BWP of the second type, and transmitting the plurality of channels on the plurality of BWPs. The frequency domain resources may include one or more resource blocks (RBs), resource units (REs), or control channel units (CCEs). The channels may include one or more uplink or downlink channels.

[0142] While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Similarly, various diagrams depict example architectures or configurations, which are provided to enable those skilled in the art to understand example features and functionality of the present invention. However, those skilled in the art will understand that the present invention is not limited to the example architectures or configurations shown, but can be implemented using a variety of alternative architectures and configurations.

[0143] Also, as can be understood by one of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the illustrative embodiments described above.

[0144] It will also be understood that any reference to elements in this application using a designation such as "first," "second," etc., does not generally limit the quantity or order of those elements. Rather, these designations may be used in this application as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some format.

[0145] Additionally, as will be appreciated by those skilled in the art, information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, and symbols described in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0146] Furthermore, as will be appreciated by those skilled in the art, any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital, analog, or a combination of the two), firmware, various forms of program or design code incorporating instructions (which may be referred to herein for convenience as "software" or "software modules"), or any combination of these technologies.

[0147] To clearly illustrate the interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system.

[0148] Those skilled in the art may implement the described functionality in a variety of ways for each particular application, but such implementation decisions do not depart from the scope of the present disclosure.

[0149] Furthermore, as will be appreciated by those skilled in the art, the various illustrative logic blocks, modules, devices, components, and circuits described herein can be realized within or implemented by integrated circuits (ICs), which may include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof.

[0150] The logic blocks, modules, and circuits may further include an antenna and / or a transceiver to communicate with various components in a network or device. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration for performing the functions described herein.

[0151] When implemented as software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any medium that can be enabled to transfer a computer program or code from one place to another.

[0152] A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0153] As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Also, for purposes of discussion, the various modules are described as separate modules. However, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according to embodiments of the present invention.

[0154] Also, memory or other storage and communication components may be employed in embodiments of the invention. As will be appreciated, for purposes of clarity, the above description describes embodiments of the invention with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without deviating from the invention.

[0155] For example, functionality illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units do not indicate a strict logical or physical structure or organization, but merely a reference to suitable means for providing the described functionality.

[0156] Various modifications of the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Thus, this disclosure is not intended to be limited to the implementations shown in this application, but is to be accorded the broadest scope consistent with the novel features and principles disclosed herein, as limited in the following claims.

Claims

1. 1. A wireless communication method, comprising: receiving, by a wireless communication device, wireless configuration information from a wireless communication node, the wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence between the second type of BWP and a plurality of BWPs; allocating, by the wireless communication device, a number of resources for transmission or reception based on the wireless configuration information. A wireless communication method.

2. The plurality of BWPs correspond to a plurality of carriers. The wireless communication method according to claim 1 .

3. a first portion of the second type BWP is mapped to a first BWP of the plurality of BWPs, and a second portion of the second type BWP is mapped to a second BWP of the plurality of BWPs; The wireless communication method according to claim 2.

4. the bandwidth of the second type BWP is the sum of the bandwidths of each of the plurality of BWPs; The wireless communication method according to claim 3.

5. The wireless communication device receives scheduling information including frequency resource information based on the second type BWP, and the wireless communication device allocates frequency resources in the plurality of BWPs for data transmission or reception. The wireless communication method according to claim 4.

6. 1. A wireless communication method, comprising: transmitting, by the wireless communication node, to the wireless communication device, wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence relationship between the second type of BWP and a plurality of BWPs; A wireless communication method.

7. The plurality of BWPs correspond to a plurality of carriers. The wireless communication method according to claim 6.

8. a first portion of the second type BWP is mapped to a first BWP of the plurality of BWPs, and a second portion of the second type BWP is mapped to a second BWP of the plurality of BWPs; The wireless communication method according to claim 7.

9. the bandwidth of the second type BWP is the sum of the bandwidths of each of the plurality of BWPs; The wireless communication method according to claim 8.

10. the wireless communication node transmits scheduling information including frequency resource information based on the second type of BWP; The wireless communication method according to claim 9.

11. 1. A wireless communication device comprising at least one processor and a memory containing instructions, the at least one processor executing the instructions to: receiving wireless configuration information from a wireless communication node, the wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence relationship between the second type of BWP and a plurality of BWPs; allocating a plurality of resources for transmission or reception based on the radio configuration information; Wireless communication device.

12. The plurality of BWPs correspond to a plurality of carriers.

12. The wireless communication device of claim 11.

13. a first portion of the second type BWP is mapped to a first BWP of the plurality of BWPs, and a second portion of the second type BWP is mapped to a second BWP of the plurality of BWPs; 13. The wireless communication device of claim 12.

14. the bandwidth of the second type BWP is the sum of the bandwidths of each of the plurality of BWPs; 14. The wireless communication device of claim 13.

15. a wireless communication device receiving scheduling information including frequency resource information based on the second type BWP, the wireless communication device allocating frequency resources in the plurality of BWPs for data transmission or reception; 15. The wireless communication device of claim 14.

16. 1. A wireless communication device including at least one processor and a memory including instructions, The at least one processor executes the instructions to: transmitting, to the wireless communication device, wireless configuration information including a configuration of a second type of bandwidth portion (BWP) and a correspondence relationship between the second type of BWP and a plurality of BWPs; Wireless communication device.

17. The plurality of BWPs correspond to a plurality of carriers.

17. The wireless communication device of claim 16.

18. a first portion of the second type BWP is mapped to a first BWP of the plurality of BWPs, and a second portion of the second type BWP is mapped to a second BWP of the plurality of BWPs; 20. The wireless communication device of claim 17.

19. the bandwidth of the second type BWP is the sum of the bandwidths of each of the plurality of BWPs; 20. The wireless communication device of claim 18.

20. the wireless communication node transmits scheduling information including frequency resource information based on the second type of BWP; 20. The wireless communication device of claim 19.

21. A wireless communication device comprising at least one processor and a memory, the at least one processor being configured to read code from the memory and to perform a method according to any one of claims 1 to 20. Wireless communication device.

22. A computer program product comprising computer readable program medium code stored therein, the code, when executed by at least one processor, causing the at least one processor to perform a method according to any one of claims 1 to 20. Computer program products.

Images