CN115942487A

CN115942487A - Resource allocation method and communication device

Info

Publication number: CN115942487A
Application number: CN202111198557.7A
Authority: CN
Inventors: 温容慧; 金哲; 余政; 侯海龙; 王轶
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-09-30
Filing date: 2021-10-14
Publication date: 2023-04-07

Abstract

The application provides a resource allocation method and a communication device, wherein the method comprises the following steps: the terminal equipment acquires configuration information of a first downlink BWP and configuration information of a first uplink BWP, and determines the first downlink BWP and the first uplink BWP; wherein, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a connected state, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP; or, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, where the non-connected state is an idle state or an inactive state. The flexibility of the network configuration BWP can be increased, so that the network can meet the communication requirements of various application scenarios.

Description

Resource allocation method and communication device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a resource configuration method and a communications apparatus.

Background

The new generation mobile communication system defines three application scenarios, enhanced mobile broadband (eMBB), high-reliability and low-latency communications (URLLC), and massive machine type communications (mtc). Currently, a corresponding communication mechanism is mainly designed for an eMB and URLLC scene, for example, for the eMB scene, the communication bandwidth can reach the hundred megabytes level, and an ultrahigh data transmission rate can be realized.

Currently, research is conducted on an mtc scenario, and a low-energy (REDCAP) terminal device, as a type of terminal device in the mtc scenario, has the characteristics of narrower communication bandwidth, lower power consumption, fewer antennas, and the like, compared with an existing terminal device. The current system also lacks a corresponding communication mechanism that enables the REDCAP terminal devices to communicate using network bandwidth resources. Therefore, the performance requirements of various application scenarios cannot be met by the current communication system.

Disclosure of Invention

The application provides a resource allocation method and a communication device, which are used for solving the problem that the current communication system cannot meet the performance requirements of various application scenarios.

In a first aspect, the present application provides a resource allocation method, where an execution subject of the method may be a terminal device, and may also be a chip applied in the terminal device. The following description will be made taking as an example that the execution subject is a terminal device.

The method comprises the following steps: the terminal device acquires configuration information of the first downlink BWP and configuration information of the first uplink BWP. The terminal device determines a first downlink BWP according to the configuration information of the first downlink BWP, and determines a first uplink BWP according to the configuration information of the first uplink BWP. Wherein the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a connected state, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP. And/or the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, and the non-connected state is an idle state or an inactive state.

In the above manner, the network device may configure the terminal device with the same or different center frequencies of the uplink BWP and the downlink BWP based on the state (including one or more of the connected state, the idle state, and the inactive state) in which the terminal device is located. The low-power terminal equipment can be accessed to the network, and the system bandwidth resource of the network equipment is utilized to communicate with the network equipment. The flexibility of configuring BWP for network devices is increased, enabling the system to meet the communication needs of a variety of application scenarios.

With reference to the first aspect, in a possible design, when the terminal device is in the unconnected state, the center frequencies (center frequencies) of the initial downlink BWP and the initial uplink BWP used by the terminal device to communicate with the network device are different. When the terminal device is in the connected state, the center frequencies of the initial downlink BWP and the initial uplink BWP used when the terminal device communicates with the network device are the same.

When the terminal device is in the non-connection state, determining an initial BWP (including an initial upstream BWP and/or an initial downstream BWP) used by the terminal device to communicate with the network device when the terminal device is in the non-connection state according to configuration information of the initial BWP when the terminal device is in the non-connection state, where a center frequency of the initial downstream BWP is different from a center frequency of the initial upstream BWP.

After the terminal device leaves the non-connected state or enters the connected state, the terminal device may determine, according to configuration information of an initial BWP used by the terminal device in the connected state, an initial BWP used by the terminal device for communicating with the network device when the terminal device is in the connected state, where a center frequency of the initial downlink BWP is the same as a center frequency of the initial uplink BWP.

That is, the configuration of the initial BWP used when the terminal device is in the unconnected state is different from the configuration of the initial BWP used when the terminal device is in the connected state.

With reference to the first aspect, in a possible design, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a connected state, where the first downlink BWP is an independent initial downlink BWP, and the first uplink BWP is an independent initial uplink BWP, or the first downlink BWP is an dependent initial downlink BWP, and the first uplink BWP is an independent initial uplink BWP, or the first downlink BWP is an independent initial downlink BWP, and the first uplink BWP is a dependent initial uplink BWP, or the first downlink BWP is a dependent initial downlink BWP, and the first uplink BWP is a dependent initial uplink BWP.

In the above manner, the first downlink BWP may be an independent initial downlink BWP or a non-independent initial downlink BWP, and the first uplink BWP may be an independent initial uplink BWP or a non-independent initial uplink BWP. The center frequencies of the upstream BWP and the downstream BWP used by the network device for the terminal device when the terminal device is in the connected state are the same. When the terminal equipment in the connection state is communicated with the network equipment, the radio frequency point does not need to be readjusted when the uplink and the downlink are mutually converted, the power consumption of the terminal equipment can be reduced, and the increase of communication delay caused by frequent conversion is avoided.

With reference to the first aspect, in one possible design, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, including: the first downlink BWP is an independent initial downlink BWP, the first uplink BWP is an independent initial uplink BWP, the center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP, and/or the first downlink BWP is an dependent initial downlink BWP, the first uplink BWP is an independent initial uplink BWP, the center frequencies of the first downlink BWP and the first uplink BWP are the same or different, and/or the first downlink BWP is an independent initial downlink BWP, the first uplink BWP is a dependent initial uplink BWP, the center frequencies of the first downlink BWP and the first uplink BWP are the same or different, and/or the first downlink BWP is a dependent initial downlink BWP, the first uplink BWP is a dependent initial uplink BWP, the center frequencies of the first downlink BWP and the first uplink BWP are the same or different.

In the above manner, when the first downlink BWP is an initial downlink BWP, the first uplink BWP is an initial uplink BWP, and the network device configures the first downlink BWP and the first uplink BWP used in the non-connected state for the terminal device, the central frequency of the first downlink BWP and the central frequency of the first uplink BWP may be configured to be the same or different based on whether the first downlink BWP and/or the first uplink BWP are independent initial BWPs. The flexibility of the network configuration BWP is increased, so that the network can meet the communication requirements of various application scenes. The network device may configure, for the terminal device, that the center frequency of the first downlink BWP used when the terminal device is in the non-connected state is the same as the center frequency of the first uplink BWP, which may avoid readjusting the radio frequency point when the terminal device switches between uplink and downlink when the terminal device is in the non-connected state, and may reduce power consumption of the terminal device.

With reference to the first aspect, in a possible design, the non-standalone initial downlink BWP is an initial downlink BWP configured by a master information block MIB, or the non-standalone initial downlink BWP is an initial downlink BWP configured by a system information block SIB 1.

With reference to the first aspect, in one possible design, the BWP IDs of the first downlink BWP and the first uplink BWP are the same.

In the above manner, the first downstream BWP and the first upstream BWP may be a group of BWPs that are simultaneously active for the network device to communicate with the end device. The terminal device receives the downlink information from the network device on the resource in the downlink BWP, and transmits the uplink information to the network device on the resource in the uplink BWP. Wherein, the BWP IDs of the upstream BWP and the downstream BWP in the active state at the same time are the same.

With reference to the first aspect, in one possible design, a center frequency of the first downlink BWP is different from a center frequency of the first uplink BWP, and the method further includes: the terminal device obtains configuration information of a second downlink BWP, wherein the center frequency of the second downlink BWP is the same as the center frequency of the first uplink BWP, and the BWP ID of the second downlink BWP is the same as the BWP ID of the first uplink BWP.

For example, the second downlink BWP and the first uplink BWP may be BWPs used by the terminal device in a connected state.

With reference to the first aspect, in one possible design, a center frequency of the first uplink BWP is different from a center frequency of the first downlink BWP, and the method further includes: the terminal device obtains configuration information of a second uplink BWP, the center frequency of the first downlink BWP is the same as the center frequency of the second uplink BWP, and the BWP ID of the second uplink BWP is the same as the BWP ID of the first downlink BWP.

In the above manner, the first downlink BWP and the first uplink BWP may be the initial BWP used by the terminal device in the non-connected state, and the network device may reconfigure the uplink initial BWP and/or the downlink initial BWP used by the terminal device in the connected state for the terminal device, so that the central frequency point of the initial uplink BWP used by the terminal device in the connected state is the same as the central frequency point of the initial downlink BWP. The center frequency point of the initial uplink BWP used by the terminal device not expecting the terminal device configured by the network device to be in the connection state is different from that of the initial downlink BWP. When the terminal equipment is in a connected state and uses the initial uplink BWP and the initial downlink BWP, the radio frequency point does not need to be readjusted when the uplink and the downlink are switched with each other, and the power consumption of the terminal equipment can be reduced.

With reference to the first aspect, in one possible design, the method further includes: and the terminal equipment reports first information, wherein the first information indicates that the center frequency of the uplink BWP supported by the first terminal equipment is different from the center frequency of the downlink BWP.

In the above manner, the terminal device may report the capability of the terminal device to the network device, and if the center frequency of the uplink BWP supported by the terminal device is different from the center frequency of the downlink BWP, the center frequencies of the first downlink BWP and the first uplink BWP configured by the network device for the terminal device may be the same or different. If the center frequency of the upstream BWP that is not supported by the terminal device is different from the center frequency of the downstream BWP, the network device configures the first downstream BWP and the first upstream BWP with the same center frequency for the terminal device. The method and the system can realize that the network device configures the BWP meeting the capability of the terminal device for the terminal device based on the capability of the terminal device, avoid the condition that the network device configures the BWP not meeting the processing capability for the terminal device so as to cause the communication incapability, and improve the communication efficiency of the system.

In a second aspect, the present application provides a resource allocation method, where an execution subject of the method may be a network device or a chip applied to the network device. The following description will be given taking as an example that the execution subject is a network device.

The method comprises the following steps: the network device determines configuration information for the first downstream BWP and determines configuration information for the first upstream BWP. And the network equipment sends the configuration information of the first downlink BWP and the configuration information of the first uplink BWP. Wherein, the first downlink BWP and the first uplink BWP are BWPs used by a terminal device in a connected state, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP; and/or the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, and the non-connected state is an idle state or an inactive state.

With reference to the second aspect, in one possible design, the first downstream BWP and the first upstream BWP are BWPs used by the terminal device in a connected state, where,

the first downstream BWP is an independent initial downstream BWP, the first upstream BWP is an independent initial upstream BWP, or,

the first downlink BWP is a dependent initial downlink BWP, the first uplink BWP is an independent initial uplink BWP, or,

the first downstream BWP is an independent initial downstream BWP, the first upstream BWP is a non-independent initial upstream BWP, or,

the first downlink BWP is a dependent initial downlink BWP, and the first uplink BWP is a dependent initial uplink BWP.

With reference to the second aspect, in one possible design, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP and a center frequency of the first uplink BWP are the same or different, including:

the first downlink BWP is an independent initial downlink BWP, the first uplink BWP is an independent initial uplink BWP, and the center frequency of the first downlink BWP is the same as that of the first uplink BWP; and/or the presence of a gas in the atmosphere,

the first downstream BWP is a dependent initial downstream BWP, the first upstream BWP is a dependent initial upstream BWP, the first downstream BWP and the first upstream BWP have the same or different center frequency, and/or,

the first downlink BWP is an independent initial downlink BWP, the first uplink BWP is a dependent initial uplink BWP, the center frequencies of the first downlink BWP and the first uplink BWP are the same or different, and/or,

the first downlink BWP is a dependent initial downlink BWP, the first uplink BWP is a dependent initial uplink BWP, and the center frequencies of the first downlink BWP and the first uplink BWP are the same or different.

With reference to the second aspect, in one possible design, the dependent initial downlink BWP is an initial downlink BWP configured by a master information block MIB, or the dependent initial downlink BWP is an initial downlink BWP configured by a system information block SIB 1.

With reference to the second aspect, in one possible design, the BWP IDs of the first downstream BWP and the first upstream BWP are the same.

With reference to the second aspect, in one possible design, a center frequency of the first downstream BWP and a center frequency of the first upstream BWP are different, and the method further includes: the network device sends configuration information of a second downlink BWP, where a center frequency of the second downlink BWP is the same as a center frequency of the first uplink BWP, and a BWP ID of the second downlink BWP is the same as a BWP ID of the first uplink BWP.

With reference to the second aspect, in one possible design, the center frequency of the first upstream BWP and the center frequency of the first downstream BWP are different, and the method further includes: the network device sends configuration information of a second uplink BWP, where a center frequency of the first downlink BWP is different from a center frequency of the second uplink BWP, and a BWP ID of the second uplink BWP is the same as a BWP ID of the first downlink BWP.

In combination with the second aspect, in one possible design, the method further includes: the network device obtains first information indicating that the center frequency of uplink BWP supported by the terminal device is different from the center frequency of downlink BWP.

In a third aspect, the present application provides a resource allocation method, where an execution subject of the method may be a terminal device or a chip applied to the terminal device. The following description will be made taking as an example that the execution subject is a terminal device.

The method comprises the following steps: the terminal device acquires configuration information of the first downlink BWP and configuration information of the first uplink BWP. The terminal device determines a first downlink BWP according to the configuration information of the first downlink BWP, and determines a first uplink BWP according to the configuration information of the first uplink BWP. Wherein the first downlink BWP and the first uplink BWP are BWPs used after initial access or random access of the terminal device, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP. And/or the first downlink BWP and the first uplink BWP are BWPs used in the initial access process or the random access process of the terminal device, and the center frequency of the first downlink BWP is the same as or different from the center frequency of the first uplink BWP.

In the above manner, the network device may configure the terminal device with the same or different center frequencies of the uplink BWP and the downlink BWP based on the state (including one or more of after random access, after initial access, during random access, and after initial access) of the terminal device. The low-energy terminal equipment can be accessed to the network, and the system bandwidth resources of the network equipment are utilized to communicate with the network equipment. The flexibility of configuring BWP by the network equipment is increased, so that the system can meet the communication requirements of various application scenes. The center frequencies of the downlink BWP and the uplink BWP used after the initial access are the same, because the general terminal device enters the service transmission process, and the service generally has a requirement of time delay, such as 1ms, so that the uplink and downlink center frequency points need to be aligned to reduce the time delay influence caused by frequency tuning. The center frequencies of the downlink BWP and the uplink BWP used in the initial access may be different because the requirement for the service reception delay is smaller, and the influence of the frequency tuning caused by the misalignment of the uplink and downlink center frequency points is smaller.

Herein, the initial access is immediately after the initial access procedure. The random access is followed by a random access procedure. No distinction is made.

In a fourth aspect, the present application provides a resource allocation method, where an execution subject of the method may be a terminal device or a chip applied to the terminal device. The following description will be given taking as an example that the execution main body is a terminal device.

The method comprises the following steps: the terminal device acquires configuration information of the first downlink BWP and configuration information of the first uplink BWP. The terminal device determines a first downlink BWP according to the configuration information of the first downlink BWP, and determines a first uplink BWP according to the configuration information of the first uplink BWP. Wherein the first downlink BWP is a non-initial downlink BWP of the terminal device, the first uplink BWP is a non-initial uplink BWP of the terminal device, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP. And/or, wherein the first downlink BWP is an initial downlink BWP of the terminal device, the first uplink BWP is an initial uplink BWP of the terminal device, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP.

In the above manner, the network device may configure the terminal device with the same or different center frequencies of the upstream BWP and the downstream BWP based on the usage of the BWP of the terminal device (including one or more of the initial BWP and the non-initial BWP). The low-energy terminal equipment can be accessed to the network, and the system bandwidth resources of the network equipment are utilized to communicate with the network equipment. The flexibility of configuring BWP for network devices is increased, enabling the system to meet the communication needs of a variety of application scenarios.

In a fifth aspect, the present application provides a resource allocation method, where an execution subject of the method may be a network device or a chip applied to the network device. The following description will be given taking as an example that the execution subject is a network device.

The method comprises the following steps: the first downlink BWP is an independent initial downlink BWP, and the terminal device does not expect the first downlink BWP to include one or more of a cell-defined SSB, a non-cell-defined SSB, CORESET0, and a system information block. And/or the first downlink BWP is an active BWP configured by a radio resource control RRC, and the terminal device expects the first downlink BWP to include one or more of a cell-defined SSB, a non-cell-defined SSB, and a channel state information reference signal CSI-RS.

In a sixth aspect, a communication apparatus is provided, and beneficial effects may be seen from the description of the first aspect, which is not described herein again. The communication device has the functionality to implement the actions in the method instance of the first aspect described above. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. In one possible design, the communication device includes: and the transceiver module is used for acquiring the configuration information of the first downlink BWP and the configuration information of the first uplink BWP. And the processing module is used for determining a first downlink BWP according to the configuration information of the first downlink BWP and determining a first uplink BWP according to the configuration information of the first uplink BWP. Wherein, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in the connected state, and the center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP; and/or the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, and the non-connected state is an idle state or an inactive state.

The modules included in the communication device may perform corresponding functions in the method example of the first aspect, for which specific reference is made to detailed description in the method example, which is not described herein again.

In a seventh aspect, a communication apparatus is provided, and beneficial effects may be found in the description of the second aspect and will not be described herein again. The communication device has the functionality to implement the actions in the method example of the second aspect described above. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above. In one possible design, the communication device includes: a processing module configured to determine configuration information of the first downlink BWP and determine configuration information of the first uplink BWP. And the transceiver module is configured to send configuration information of the first downlink BWP and configuration information of the first uplink BWP. Wherein, the first downlink BWP and the first uplink BWP are BWPs used by a terminal device in a connected state, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP; and/or the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, and the non-connected state is an idle state or an inactive state.

The modules included in the communication device may perform corresponding functions in the method example of the second aspect, which is specifically described in detail in the method example, and details are not repeated here.

In an eighth aspect, a communication apparatus is provided, and the communication apparatus may be the terminal device in the above method embodiment, or a chip provided in the terminal device. The communication device comprises a communication interface, a processor and optionally a memory. Wherein the memory is adapted to store a computer program or instructions, and the processor is coupled to the memory and the communication interface, and when the processor executes the computer program or instructions, the communication apparatus is adapted to perform the method performed by the terminal device in the above-mentioned method embodiments.

In a ninth aspect, a communication apparatus is provided, and the communication apparatus may be the network device in the above method embodiment, or a chip provided in the network device. The communication device comprises a communication interface, a processor and optionally a memory. Wherein the memory is used for storing a computer program or instructions, and the processor is coupled with the memory and the communication interface, and when the processor executes the computer program or instructions, the communication device is caused to execute the method executed by the network device in the above method embodiment.

In a tenth aspect, there is provided a computer program product comprising: computer program code which, when run, causes the method performed by the terminal device in the above aspects to be performed.

In an eleventh aspect, there is provided a computer program product comprising: computer program code which, when executed, causes the method performed by the network device in the above aspects to be performed.

In a twelfth aspect, the present application provides a chip system, which includes a processor, and is configured to implement the functions of the terminal device in the methods of the above aspects. In one possible design, the system-on-chip further includes a memory for storing program instructions and/or data. The chip system may be formed by a chip, or may include a chip and other discrete devices.

In a thirteenth aspect, the present application provides a chip system, which includes a processor for implementing the functions of the network device in the method of the above aspects. In one possible design, the system-on-chip further includes a memory for storing program instructions and/or data. The chip system may be formed by a chip, or may include a chip and other discrete devices.

In a fourteenth aspect, the present application provides a computer-readable storage medium storing a computer program that, when executed, implements the method performed by a terminal device in the above-described aspects.

In a fifteenth aspect, the present application provides a computer-readable storage medium storing a computer program that, when executed, implements the method performed by a network device in the above aspects.

Drawings

Fig. 1 is a schematic diagram of a communication system provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of an initial BWP provided by an embodiment of the present application;

FIG. 3 is another schematic diagram of an initial BWP provided by an embodiment of the present application;

FIG. 4 is a schematic flow chart diagram of a resource allocation method provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a first downstream BWP and a first upstream BWP provided by an embodiment of the present application;

fig. 6 is another schematic diagram of the first downstream BWP and the first upstream BWP provided in the embodiments of the present application;

fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;

fig. 9 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

Fig. 1 is a schematic diagram of a possible network architecture applicable to the embodiment of the present application, which includes a terminal device 110 and an access network device 120. The terminal device 110 and the access network device 120 may communicate via a Uu air interface, where the Uu air interface may be understood as a universal UE to network interface (universal UE to network interface) between the terminal device and the network device. The transmission of the Uu air interface comprises uplink transmission and downlink transmission.

For example, uplink transmission refers to terminal device 110 sending uplink information to access network device 120. The uplink information may include one or more of uplink data information, uplink control information, and a Reference Signal (RS). A channel for transmitting uplink information is called an uplink channel, and the uplink channel may be a Physical Uplink Shared Channel (PUSCH) or a Physical Uplink Control Channel (PUCCH). The PUSCH is used to carry uplink data, which may also be referred to as uplink data information. The PUCCH is used to carry Uplink Control Information (UCI) fed back by the terminal device. The UCI may include Channel State Information (CSI), acknowledgement (ACK)/Negative Acknowledgement (NACK), and the like.

Illustratively, downlink transmission refers to access network device 120 sending downlink information to terminal device 110. The downlink information may include one or more of downlink data information, downlink control information, and downlink reference signals. The downlink reference signal may be a channel state information reference signal (CSI-RS) or a Phase Tracking Reference Signal (PTRS). A channel for transmitting downlink information is called a downlink channel, and the downlink channel may be a Physical Downlink Shared Channel (PDSCH) or a Physical Downlink Control Channel (PDCCH). The PDCCH is used to carry Downlink Control Information (DCI), and the PDSCH is used to carry downlink data, where the downlink data may also be referred to as downlink data information.

Optionally, in the network architecture shown in fig. 1, a core network device 130 may also be included. Wherein, the terminal equipment 110

The access network device 120 may be connected to the access network device 120 in a wireless manner, and the access network device 120 may be connected to the core network device 130 in a wired or wireless manner. Core network device 130 and access network device 120 may be separate and distinct physical devices, or core network device 130 and access network device 120 may be the same physical device with all/part of the logical functions of core network device 130 and access network device 120 integrated thereon.

It should be noted that, in the network architecture shown in fig. 1, the terminal device 110 may be in a fixed location, or may also be in a fixed location

Is movable and is not limited. The network architecture shown in fig. 1 may further include other network devices, such as a wireless relay device and a wireless backhaul device, without limitation. In the architecture shown in fig. 1, the number of terminal devices, access network devices, and core network devices is not limited.

The technical scheme in the embodiment of the application can be applied to various communication systems. Such as a Long Term Evolution (LTE) system, a fifth generation (5 th generation,5 g) mobile communication system, a future mobile communication system, and the like.

Some terms or terms used in the present application are explained below, and the terms or terms are also included as part of the summary of the invention.

1. Terminal device

A terminal device, which may be referred to as a terminal for short, also called a User Equipment (UE), is a device with a wireless transceiving function. The terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, drones, balloons, satellites, etc.). The terminal equipment can be a mobile phone, a tablet personal computer, a computer with a wireless transceiving function, virtual reality terminal equipment, augmented reality terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in unmanned driving, wireless terminal equipment in telemedicine, wireless terminal equipment in a smart grid, wireless terminal equipment in transportation safety, wireless terminal equipment in a smart city and wireless terminal equipment in a smart family. The terminal equipment may also be fixed or mobile. The embodiments of the present application do not limit this.

In the embodiment of the present application, the apparatus for implementing the function of the terminal may be a terminal device; it may also be an apparatus, such as a system-on-chip, capable of supporting the terminal device to implement the function, and the apparatus may be installed in the terminal device. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices. In the technical solution provided in the embodiment of the present application, a device for implementing a function of a terminal device is taken as an example of a terminal device, and the technical solution provided in the embodiment of the present application is described.

2. Network device

The network device may be an access network device, and the access network device may also be referred to as a Radio Access Network (RAN) device, which is a device that provides a wireless communication function for the terminal device. Access network equipment includes, for example but is not limited to: a next generation base station (gbb) in 5G, an evolved node B (eNB), a baseband unit (BBU), a Transmit and Receive Point (TRP), a Transmission Point (TP), a base station in a future mobile communication system or an access point in a WiFi system, and the like. The access network device may also be a wireless controller, a Centralized Unit (CU), and/or a Distributed Unit (DU) in a Cloud Radio Access Network (CRAN) scenario, or the network device may be a relay station, a vehicle-mounted device, a network device in a PLMN network that is evolved in the future, and the like.

The terminal device may communicate with multiple access network devices of different technologies, for example, the terminal device may communicate with an access network device supporting Long Term Evolution (LTE), may communicate with an access network device supporting 5G, and may simultaneously communicate with an access network device supporting LTE and an access network device supporting 5G. The embodiments of the present application are not limited.

In the embodiment of the present application, the apparatus for implementing the function of the network device may be a network device; or may be a device, such as a system-on-chip, capable of supporting the network device to implement the function, and the device may be installed in the network device. In the technical solution provided in the embodiment of the present application, a device for implementing a function of a network device is taken as an example of a network device, and the technical solution provided in the embodiment of the present application is described.

At present in the fifth generation (5) ^th generation, 5G) mobile communication system, the communication bandwidth can reach the hundred megabytes level for the eMBB scenario, and an ultra-high data transmission rate can be achieved. In addition, in order to serve UEs of different bandwidth capabilities, a concept of a partial Bandwidth (BWP) is also introduced, which may be a part of a carrier bandwidth of a network device. The network equipment can configure one or more uplink channels for the UE based on the capability of the UEThe uplink BWP is a bandwidth for transmitting uplink information, the downlink BWP is a bandwidth for transmitting downlink information, and different uplink BWPs or different downlink BWPs may be different in frequency domain position and/or different in bandwidth size. In the BWP configured by the network device for the terminal device, an uplink BWP and a downlink BWP with the same Identifier (ID) may be activated for the network device to communicate with the terminal device, and the protocol provides that in a Time Division Duplex (TDD) system, the center frequencies of the uplink BWP and the downlink BWP with the same ID are consistent. This provision causes the center frequency of the upstream active BWP and the center frequency of the downstream active BWP used by the network device and the terminal device to be the same.

In the initial access process, the UE may perform time domain synchronization and frequency domain synchronization through a Synchronization Signal Block (SSB) sent by the network device to obtain a Master Information Block (MIB), and then blindly detect Downlink Control Information (DCI) in a control resource set (core set) 0, where the DCI is used to schedule a Physical Downlink Shared Channel (PDSCH) of a System Information Block (SIB) 1. SSB and CORESET0 are contiguous in the time domain, and the frequency domain bandwidth of CORESET0 in the frequency domain includes the frequency domain bandwidth of SSB. The terminal device may acquire SIB1, and acquire relevant configuration information for an initial access procedure according to SIB1, where the configuration information includes configuration information of an initial downlink BWP and configuration information of an initial uplink BWP. The protocol specifies that the center frequencies of the initial downlink BWP and the initial uplink BWP are consistent, the initial downlink BWP needs to include the bandwidths of SSB and CORESET0, for example, in the carrier bandwidth of the network device shown in fig. 2, SSB and CORESET0 occupy the resources near the carrier center frequency, the initial downlink BWP configured in SIB1 includes the bandwidths of SSB and CORESET0, and the center frequencies of the downlink BWP and the uplink BWP configured in SIB1 are the same, where the DCI corresponding to SIB1 is carried in CORESET 0. In the initial access process, the terminal device may receive downlink information from the network device using the initial downlink BWP, specifically, may receive the downlink information using the bandwidth size occupied by core set0 in the initial downlink BWP, and the terminal device may send the uplink information in the initial access process to the network device using the initial uplink BWP. The terminal device may also use the initial BWP when in the connected state, e.g., the terminal device may initiate a random access procedure acquisition system message using the initial downlink BWP and the initial uplink BWP.

Compared with the existing terminal equipment, the REDCAP UE in the mMTC scene has the characteristics of narrower communication bandwidth, lower power consumption, fewer antennas and the like. The REDCAP UE may also be referred to as a low complexity UE or a lightweight version UE, such as a lightweight (light) version UE in a 5G New Radio (NR) system, which may be referred to as an NRL UE.

The maximum bandwidth that the redaccp UE can support is 20MHz, and the maximum bandwidth that the UE can support in the eMBB scenario is 100MHz, and in order not to affect the continuity of the frequency domain resources of the eMBB UE, the network device needs to configure the BWP of the REDCAP UE at the edge of the carrier bandwidth of the network device. If the center frequency of the downlink BWP and the uplink BWP specified in the current protocol is the same and the initial downlink BWP needs the bandwidth unit including SSB and CORESET0, the downlink initial BWP, the uplink initial BWP, the SSB, and the CORESET0 are all at the edge of the carrier as shown in fig. 3. The SSB and CORESET0 belong to important resources of UE access networks, are configured at the edge of a carrier, and are easily interfered by adjacent frequency to influence the access performance. In addition, limiting SSB and core set0 to the edge of the carrier bandwidth for the REDCAP UE to access the network may affect the flexibility of the overall resource configuration of the network, so that the performance requirements of other terminal devices may not be met.

The present invention provides a resource allocation method and a communication device, so as to solve the problem that the current communication system cannot meet the performance requirements of various application scenarios.

The resource allocation method provided by the embodiment of the present application is described below with reference to the drawings.

As shown in fig. 4, an embodiment of the present application provides a flowchart of a resource configuration method, where the method may be executed by a terminal device and a network device, or may also be executed by a chip in the terminal device and a chip in the network device. The network device in fig. 4 may be the access network device 120 in fig. 1 and the terminal device may be the terminal device 110 in fig. 1. The method illustrated in fig. 4 may include the following operations.

S401, the network device sends the configuration information of the first downlink BWP to the terminal device, and sends the configuration information of the first uplink BWP to the terminal device.

Accordingly, the terminal device receives the configuration information of the first downlink BWP from the network device, and receives the configuration information of the first uplink BWP from the network device.

The network device may send the configuration information of the first downlink BWP to the terminal device after determining the configuration information of the first downlink BWP, and send the configuration information of the first uplink BWP to the terminal device after determining the configuration information of the first uplink BWP.

It should be noted that the configuration information of the first downlink BWP and the configuration information of the first uplink BWP may be carried in the same message sent by the network device to the terminal device, or may be carried in different messages sent by the network device to the terminal device. It should be understood that, when the configuration information of the first downlink BWP and the configuration information of the first uplink BWP are carried in different messages, the present embodiment does not limit the sequence of the network device sending the configuration information of the first downlink BWP and sending the configuration information of the first uplink BWP to the terminal device. The network device may send the configuration information of the first downlink BWP to the terminal device, and then send the configuration information of the first uplink BWP to the terminal device, or send the configuration information of the first uplink BWP to the terminal device first, and then send the configuration information of the first downlink BWP to the terminal device.

The first downstream BWP and the first upstream BWP may be a set of BWPs that are simultaneously active for the network device to communicate with the end device. The terminal device receives the downlink information from the network device on the resource in the downlink BWP, and transmits the uplink information to the network device on the resource in the uplink BWP.

Illustratively, the BWP Identification (ID) of the first downlink BWP is the same as the BWP ID of the first uplink BWP.

The upstream BWP and downstream BWP of the same BWP ID may be in an active state simultaneously for communication between the network device and the end device.

The network device may configure the uplink BWP and the downlink BWP with the same or different center frequencies for the terminal device based on a state in which the terminal device is in (including one or more of a connected mode (RRC _ connected mode), an IDLE mode (IDLE mode) or an RRC _ IDLE mode), and an INACTIVE mode (INACTIVE mode or RRC _ INACTIVE mode).

The first downlink BWP and the first uplink BWP may be BWPs used by the terminal device in the connected state, and the center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP.

The first downlink BWP and the first uplink BWP may be BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, where the non-connected state is an idle state or an inactive state.

Wherein,

for the uplink BWP and the downlink BWP used when the terminal device is in the unconnected state, the network device may configure the uplink BWP and the downlink BWP with the same center frequency for the terminal device, or configure the uplink BWP and the downlink BWP with different center frequencies for the terminal device.

For example, when the first downlink BWP is an initial downlink BWP, the first uplink BWP is an initial uplink BWP, and the network device configures the first downlink BWP and the first uplink BWP used in the non-connected state for the terminal device, the center frequency of the first downlink BWP and the center frequency of the first uplink BWP may be configured to be the same or different based on whether the first downlink BWP and/or the first uplink BWP are independent initial BWPs.

The embodiment of the present application proposes that, with respect to the BWP configured by the network device for the existing (legacy) terminal device (referred to as the first type of terminal device), the network device may configure a separate BWP for the terminal device of the specified type (referred to as the second type of terminal device). The independent BWP may be referred to as an independent initial downlink BWP if it is an initial downlink BWP, or as an independent initial uplink BWP if it is an initial uplink BWP.

For example, the independent initial BWP (standalone initial BWP) is a specific (or proprietary) BWP for the first terminal device, or a BWP configured for the network device only for the first terminal device. For example, the independent initial BWP includes an independent initial upstream BWP and an independent initial downstream BWP. For example, the independent initial BWP is a BWP that is not shared with the second terminal device. The first terminal device and the second terminal device are different types of terminal devices. For example, the first terminal device is a second type of terminal device. The second terminal device is a first type of terminal device.

Illustratively, the independent initial BWP is a different BWP than the BWP currently configured by the terminal device. For example, the dependent initial BWP is any of: the method comprises the steps that BWPs shared by multiple types of terminal devices, BWPs configured by MIB, BWPs configured by SIB, BWPs configured by RRC, BWPs not configured for MIB, BWPs configured or used in an initial access process, BWPs configured or used after the initial access process or CORESET0 (resource).

For example, the distinction between a first type of terminal device and a second type of terminal device may include one or more of the following a to g:

a. the maximum bandwidth supported by the terminal device of the first type is greater than the maximum bandwidth supported by the terminal device of the second type, wherein the maximum bandwidth supported by the terminal device may be one or more of a maximum transmission bandwidth, a maximum reception bandwidth, or a maximum channel bandwidth, but the application is not limited thereto.

b. The maximum number of antennas supported by the terminal device of the first type is greater than the maximum number of antennas supported by the terminal device of the second type, and the maximum number of antennas supported by the terminal device may be the maximum number of transmit antennas and/or the maximum number of receive antennas, but the application is not limited thereto.

c. The maximum number of radio frequency channels supported by the terminal equipment of the first type is larger than the maximum number of radio frequency channels supported by the terminal equipment of the second type.

d. The maximum modulation and demodulation mode supported by the first type of terminal equipment is larger than the maximum modulation and demodulation mode supported by the second type of terminal equipment.

e. The maximum number of Multiple Input Multiple Output (MIMO) data layers (alternatively referred to as the number of data streams) supported by the terminal device of the first type is greater than the maximum number of MIMO data layers supported by the terminal device of the second type.

f. The first type of terminal device supports a full duplex communication mode and the second type of terminal device supports only a half duplex communication mode.

g. The minimum data processing time supported by the terminal device of the first type is less than the minimum data processing time supported by the terminal device of the second type.

Illustratively, the specified type of terminal device may include, but is not limited to, a REDCAP UE, and the existing terminal device may include, but is not limited to, an eMBB UE, a terminal device defined by the third generation partnership project (3 GPP) standard release 15, a terminal device defined by the 3GPP standard release 16. For example, the REDCAP terminal device defined by 3GPP standard release 18 may be a specified type of terminal device for which the REDCAP terminal device defined by release 17 may be an existing terminal device.

It should be noted that the non-independent BWP may be defined as the BWP used by the first type of terminal device in the implementation, or the type of the terminal device using the non-independent BWP may not be limited in the implementation. For example, a terminal device of the first type and a terminal device of the second type may each be configured or use non-independent BWP.

For example, the configuration information of the BWP may include indication information indicating that the BWP is an independent BWP or a non-independent BWP.

In one example, the indication information may be an indication field. The indication field includes at least one bit. When the indication field indicates the first state value, the BWP is indicated as an independent BWP. When the indication field indicates the second state value, the BWP is indicated to be a dependent BWP.

For example, the indication information is a 1-bit indication field. The BWP is identified as an independent BWP when the 1 bit indicates "1". When the 1 bit indicates "0", the BWP is identified as a dependent BWP. Or conversely, when the 1 bit indicates "0", the BWP is identified as the independent BWP. The BWP is identified as a dependent BWP when the 1 bit indicates "1". The terminal device may determine the BWP configured by the configuration information as an independent BWP or a non-independent BWP according to the indication information.

In another example, the network device may indicate that the BWP is an independent or non-independent BWP by whether the configuration information of the BWP includes the indication information.

For example, the indication information indicates that the BWP is an independent BWP, and when the indication information is included in the configuration information of the BWP, the terminal device may determine that the BWP is an independent BWP. When the indication information is not included in the configuration information of the BWP, the terminal device may determine that the BWP is a dependent BWP. Or the indication information may indicate that the BWP is a non-BWP. This is not a limitation of the present application.

The first downstream BWP may be an independent initial downstream BWP or a non-independent initial downstream BWP, and the first upstream BWP may be an independent initial upstream BWP or a non-independent initial upstream BWP, which may include the following:

in case one, the first downlink BWP is an independent initial downlink BWP, the first uplink BWP is an independent initial uplink BWP, and the center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP.

That is, the first downlink BWP may be an independent initial downlink BWP configured by the network device for the second type of terminal device, with the terminal device in a non-connected state. The first upstream BWP may be a separate initial upstream BWP for the terminal device in the unconnected state, configured by the network device for the second type of terminal device. The center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP.

The central frequency of the first downlink BWP configured for the terminal equipment by the network equipment is the same as the central frequency of the first uplink BWP, so that the radio frequency point can be prevented from being readjusted when the terminal equipment is in a non-connection state and the uplink and downlink are mutually switched, and the power consumption of the terminal equipment can be reduced.

For example, the first downlink BWP configured for the UE by the network device may be an independent initial downlink BWP, and the first uplink BWP configured with the same center frequency as the first downlink BWP may be an independent initial uplink BWP. For example, the network device configures an independent initial BWP for the terminal device. The independent initial BWP may be the first initial BWP for the terminal device. The UE may enter the connected state by performing a random access procedure using the first downlink BWP and the first uplink BWP when the UE is in the non-connected state after receiving the configuration information and determining the first downlink BWP and the first uplink BWP. Specifically, the terminal device uses the first uplink BWP to send uplink information during random access to the network device, and uses the first downlink BWP to receive downlink information during random access from the network device, and since the center frequencies of the first uplink BWP and the first downlink BWP are the same, the terminal device does not need to re-tune when performing mutual handover between uplink and downlink during random access, which can reduce power consumption of the terminal device.

For example, the network device may configure the first downlink BWP and/or the first uplink BWP for the terminal device through one or more of MIB, SIB, or Radio Resource Control (RRC) message.

For example, when the terminal device is in a non-connected state, the UE performs time-frequency synchronization through the SSB sent by the network device, and blindly detects DCI in CORESET0, and obtains SIB1 according to the DCI, where the SIB1 is configured with an independent initial downlink BWP (i.e., a first downlink BWP) and an independent initial uplink BWP (i.e., a first uplink BWP). The terminal device may perform a random access procedure using the independent initial downlink BWP (i.e., the first downlink BWP) and the independent initial uplink BWP (i.e., the first uplink BWP).

For example, the CORESET0 may not belong to the independent initial downstream BWP.

For example, as shown in fig. 5, the independent initial downstream BWP (i.e., the first downstream BWP) and the independent initial upstream BWP (i.e., the first upstream BWP) may be configured at the edge of the carrier bandwidth of the network device. CORESET0 may be configured around the carrier bandwidth center frequency. That is, the independent initial downlink BWP frequency domain resource may not include the SSB and CORESET0 resources. The resource may be a frequency domain resource, a bandwidth of a carrier, a bandwidth of a BWP, a time domain resource, or a time-frequency domain resource. The SSB and the CORESET0 may not be located at the edge of the carrier bandwidth along with the independent initial downlink BWP, and performance requirements of cell search, time-frequency synchronization, and the like of other terminal devices in the network can be ensured. And the initial BWP of the terminal equipment can be configured at the edge of the carrier, so that the terminal equipment can use the initial BWP at the edge of the carrier to carry out random access without influencing the continuity of frequency domain resources of other large-bandwidth UE, and the congestion of the existing UE caused by the network access of the terminal equipment is avoided.

The BWP configured at the edge of the carrier bandwidth may be a BWP configured in a frequency domain range where a frequency domain distance from an edge frequency of the carrier bandwidth is not greater than a preset threshold. The following examples are provided in the embodiments of the present application, and it should be understood that the present application is not limited thereto, and the BWP configured at the edge of the carrier bandwidth may be defined in combination with actual situations in specific implementations.

For example, if the carrier bandwidth of the network device is 100MHz, the BWP of the frequency domain resource belonging to the frequency band of 0 to 20MHz in the carrier bandwidth may be referred to as the BWP configured at the edge of the carrier bandwidth, and/or the BWP of the frequency domain resource belonging to the frequency band of 80MHz to 100MHz in the carrier bandwidth may be referred to as the BWP configured at the edge of the carrier bandwidth.

For another example, the network device configures BWPs in units of Resource Blocks (RBs), and when a subcarrier spacing (SCS) is 15kHz, a maximum sequence number of RBs included in a BWP is less than or equal to 106, the BWP may be referred to as a BWP at a carrier bandwidth edge; and/or the minimum sequence number of RB contained in one BWP is greater than or equal to (N) _RBmax 106), the BWP can be said to be a BWP at the edge of the carrier bandwidth, where N _RBmax The maximum sequence number of the RB included in the carrier bandwidth.

For another example, the network device configures BWPs in units of RBs, and when SCS is 30kHz, a maximum sequence number of RBs included in a BWP is less than or equal to 51, the BWP may be referred to as a BWP at the edge of the carrier bandwidth; and/or the minimum sequence number of RB contained in one BWP is greater than or equal to (N) _RBmax 51), the BWP can be said to be a BWP at the edge of the carrier bandwidth, where N _RBmax The maximum sequence number of the RB included in the carrier bandwidth.

For example, it may be specified that if the network device configures, for the terminal device, an independent initial downlink BWP and an independent initial uplink BWP used when the terminal device is in the non-connected state, the center frequencies of the independent initial downlink BWP and the independent initial uplink BWP are the same.

The center frequencies of the independent initial downlink BWP and the independent initial uplink BWP used by the terminal device in the unconnected state, which are not desired to be configured by the network device by the terminal device, are different.

For example, if the network device configures an independent initial downlink BWP and an independent initial uplink BWP for the terminal device, the center frequencies of the independent initial downlink BWP and the independent initial uplink BWP are the same.

The center frequencies of the independent initial downstream BWP and the independent initial upstream BWP configured by the network device are not expected to be different by the terminal device.

In case two, the first downstream BWP is a dependent initial downstream BWP, the first upstream BWP is a dependent initial upstream BWP, and the center frequencies of the first downstream BWP and the first upstream BWP are the same or different.

The network device may configure the independent initial upstream BWP for the second type of terminal device only in the unconnected state, and the second type of terminal device may perform a random access procedure using the independent initial downstream BWP and the independent initial upstream BWP in the unconnected state, thereby accessing the network.

In one example, the first downstream BWP and the first upstream BWP have different center frequencies. For example, if the network device configures the dependent initial downlink BWP in SIB1, and SIB1 further configures the independent initial uplink BWP at the edge of the carrier bandwidth for the UE, the terminal device may perform the random access procedure using the dependent initial downlink BWP and the independent initial uplink BWP, and receive downlink information in the random access procedure on the dependent initial downlink BWP. Specifically, the downlink information in the random access process may be received within the CORESET0 bandwidth, and the uplink information in the random access process may be sent to the network device on an independent initial uplink BWP at the edge of the carrier bandwidth. Wherein, the BWP ID of the dependent initial downstream BWP is the same as the BWP ID of the independent initial upstream BWP, for example, both are 0. But the application is not limited thereto. The network device configures the independent initial uplink BWP for the terminal device, so that the independent initial uplink BWP of the terminal device can be configured at the edge of the carrier bandwidth, the uplink frequency domain resource continuity of other large-bandwidth UEs can be prevented from being affected, and uplink data congestion of the large-bandwidth UE caused by network access of the small-bandwidth terminal device can be prevented. The flexibility of network configuration BWP is increased, enabling the network to meet the communication needs of a variety of application scenarios.

Or the center frequencies of the first downlink BWP and the first uplink BWP configured for the terminal device by the network device may also be the same.

In case three, the first downstream BWP is an independent initial downstream BWP, the first upstream BWP is a non-independent initial upstream BWP, and the center frequencies of the first downstream BWP and the first upstream BWP are the same or different.

In one example, the network device may configure the dependent initial upstream BWP at the edge of the carrier, and when the dependent initial downstream BWP configured by the network device is configured near the center of the carrier, the network device may further configure the dependent initial downstream BWP such that the center frequencies of the dependent initial downstream BWP (i.e., the first downstream BWP) and the dependent initial upstream BWP (i.e., the first upstream BWP) are the same, so that the terminal device of the second type may communicate with the network device using the dependent initial downstream BWP at the edge of the carrier and the dependent initial upstream BWP when the terminal device is in the non-connected state.

For example, as shown in fig. 6, the network device may configure, through an SIB, a dependent initial downlink BWP near a central frequency point of a carrier and a dependent initial uplink BWP (i.e., a first uplink BWP) at a carrier edge corresponding to the dependent initial downlink BWP, and may further configure an independent initial downlink BWP (i.e., a first downlink BWP) corresponding to the dependent initial uplink BWP. After receiving the SIB, the first type of non-connected terminal device may perform a random access procedure using the dependent initial downlink BWP and the dependent initial uplink BWP configured by the SIB to establish a communication connection with the network to enter a connected state according to the SIB. After receiving the SIB, the second type terminal device may perform a random access procedure according to the SIB using the independent initial downlink BWP and the dependent initial uplink BWP configured by the SIB to establish a communication connection with the network into a connected state. For example, the network device configures only the non-independent initial upstream BWP to be used by multiple types of terminal devices in the non-connected state according to the resource utilization condition. However, the present application is not limited to this, and the network device may also adopt the configuration of the case three in other cases.

In case four, the first downlink BWP is a dependent initial downlink BWP, the first uplink BWP is a dependent initial uplink BWP, and the center frequencies of the first downlink BWP and the first uplink BWP are the same or different.

In one example, the first downlink BWP is an initial downlink BWP configured for the MIB, i.e., CORESET 0. The first upstream BWP is the initial upstream BWP of the SIB configuration. The existing protocol only requires that the center frequencies of the initial downlink BWP configured by the SIB and the initial uplink BWP configured by the SIB are the same, and the bandwidth of the initial downlink BWP configured by the SIB includes the bandwidth of the initial downlink BWP configured by the MIB. The first type UE and the second type UE share the non-independent initial downlink BWP and the non-independent initial uplink BWP, which is beneficial to reducing the overhead of common signaling and common channels under the condition of light network load.

In the foregoing manner, the network device may configure the independent initial downlink BWP or the non-independent initial downlink BWP for the terminal device in the non-connected state according to the specific implementation, and configure the independent initial uplink BWP or the non-independent initial uplink BWP, and the center frequencies of the initial uplink BWP and the initial downlink BWP configured based on the implementation may be the same or different, so as to increase the flexibility of network configuration BWP, and enable the network to meet the communication requirements of various application scenarios.

If the central frequency points of the initial downlink BWP and the initial uplink BWP used by the terminal device in the non-connected state are different, the network device may reconfigure one of the BWPs for the terminal device by using the configuration information so that the central frequency points of the initial downlink BWP and the initial uplink BWP are the same, or the network device may reconfigure the initial downlink BWP and the initial uplink BWP with the same central frequency points for the terminal device by using the configuration information.

In one example, if the center frequencies of the first downlink BWP and the first uplink BWP used by the terminal device in the non-connected state are different, the network device may send configuration information of a second downlink BWP to the terminal device, where the center frequency of the second downlink BWP is the same as the center frequency of the first uplink BWP, and the BWP ID of the second downlink BWP is the same as the BWP ID of the first uplink BWP.

For example, the first downlink BWP is an initial downlink BWP, the first uplink BWP is an initial uplink BWP, the center frequencies of the first downlink BWP and the first uplink BWP are different, and the BWP IDs are both 0. The network device may send configuration information of the second downlink BWP to the terminal device, where the configuration information indicates that the center frequency of the second downlink BWP is the same as the center frequency of the first uplink BWP and the BWP ID of the second downlink BWP is 0. After receiving the configuration information, the terminal device may determine that the initial downlink BWP is updated from the first downlink BWP to the second downlink BWP. The second downstream BWP and the first upstream BWP may be initial BWPs used by the terminal device in the connected state.

The terminal device does not expect the center frequency of the second downstream BWP to be different from the center frequency of the first upstream BWP. That is, the terminal device expects the second downstream BWP to have the same center frequency as the first upstream BWP.

For example, the network device does not send a configuration message to the terminal device, and configures that the center frequency of the second downlink BWP used when the terminal device is in the connected state is different from the center frequency of the first downlink BWP, and the BWP ID of the second downlink BWP is the same as the BWP ID of the first uplink BWP.

For another example, if the terminal device receives a configuration information that configures a second downlink BWP used when the terminal device is in a connected state, and the BWP ID of the downlink BWP is the same as the BWP ID of the first uplink BWP in the existing configuration of the terminal device, if the center frequency of the second downlink BWP is different from the center frequency of the first uplink BWP, the terminal device considers that the configuration information is received incorrectly (e.g., the configuration information receives a channel interference decoding error), and the terminal device may discard the configuration information or not configure the second downlink BWP based on the configuration information.

In another example, if the center frequencies of the first downlink BWP and the first uplink BWP used by the terminal device in the non-connected state are different, the network device may send configuration information of a second uplink BWP to the terminal device, where the center frequency of the second uplink BWP is the same as the center frequency of the first downlink BWP, and the BWP ID of the second uplink BWP is the same as the BWP ID of the first downlink BWP.

For example, the first downlink BWP is an initial downlink BWP, the first uplink BWP is an initial uplink BWP, the center frequencies of the first downlink BWP and the first uplink BWP are different, and the BWP IDs are both 0. The network device may send configuration information of the second upstream BWP to the terminal device, where the configuration information indicates that the center frequency of the second upstream BWP is the same as the center frequency of the first downstream BWP, and the BWP ID of the second upstream BWP is 0. After receiving the configuration information, the terminal device may determine that the initial upstream BWP is updated from the first upstream BWP to the second upstream BWP. The first downstream BWP and the second upstream BWP may be initial BWPs used by the terminal device when in the connected state.

The terminal device does not expect the second upstream BWP to have a different center frequency than the first downstream BWP. That is, the terminal device expects the second upstream BWP to have the same center frequency as the first downstream BWP.

In another example, if the center frequencies of the first downlink BWP and the first uplink BWP used by the terminal device in the non-connected state are different, and the BWP IDs of the first downlink BWP and the first uplink BWP are the same (note as the first BWP ID, for example, the first BWP ID is 0), the network device may send the configuration information of the second downlink BWP and the configuration information of the second uplink BWP to the terminal device, where the BWP ID of the second downlink BWP and the BWP ID of the second uplink BWP are both the first BWP ID, and the center frequency of the second downlink BWP is the same as the center frequency of the second uplink BWP. After receiving the configuration information of the second downlink BWP and the configuration information of the second uplink BWP, the terminal device replaces the first downlink BWP with the first downlink BWP ID and replaces the first uplink BWP with the first uplink BWP ID, where the second downlink BWP and the second uplink BWP may be the initial BWP used when the terminal device is in the connected state.

As an example and not by way of limitation, the configuration information of the second downlink BWP and/or the configuration information of the second uplink BWP is an RRC message or an SIB. It should be noted that the second downlink BWP and the second uplink BWP may be BWPs used when the terminal device is in the connected state. However, the present application does not limit the state of the terminal device when the terminal device receives the configuration information of the second downlink BWP and receives the configuration information of the second uplink BWP.

The terminal device may receive the configuration information of the second downlink BWP and/or the configuration information of the second uplink BWP in a non-connected state. For example, the network device may configure the second downlink BWP and/or the second uplink BWP for the terminal device through message 4 (message 4, msg.4), message 5 (message 5, msg.5), DCI of the scheduling message 4, DCI of the scheduling message 5, DCI of the scheduling message B, or message B (message B, msg.b) in the random access procedure. The terminal device may enter the connected state from the unconnected state after receiving the message 4 or the message B.

The terminal device may also receive configuration information of the second downlink BWP and/or configuration information of the second uplink BWP when the terminal device is in the connected state. For example, after entering the connected state, the terminal device continues to receive the downlink information from the network device using the first downlink BWP used when the terminal device is in the unconnected state before receiving the configuration information of the second downlink BWP. The network device may configure the second downlink BWP for the terminal device through an RRC message after the terminal device enters the connected state. And the terminal equipment switches from the first downlink BWP to the second downlink BWP at the moment according to the received configuration information. For another example, after entering the connected state, the terminal device continues to send the upstream information to the network device using the first upstream BWP used when the terminal device is in the unconnected state before receiving the configuration information of the second upstream BWP. The network device may configure the second uplink BWP for the terminal device through an RRC message after the terminal device enters the connected state. And the terminal equipment switches from the first uplink BWP to the second uplink BWP at the moment II according to the received configuration information.

For example, time one may be predefined. For example, the time is the end time of X time units after the terminal device receives the configuration information of the second downlink BWP, where X is a positive integer. Or, the time is the starting time or the ending time of the yth time unit after the terminal device receives the configuration information of the second downlink BWP. Wherein Y is a positive integer.

Illustratively, time two may be predefined. For example, the time is the end time of M time units after the terminal device receives the configuration information of the second uplink BWP, where M is a positive integer. Or, the time is a starting time or an ending time of an nth time unit after the terminal device receives the configuration information of the second downlink BWP, where N is a positive integer.

By way of example and not limitation, the time unit may be one or more of a frame, a radio frame, a subframe, a slot, or a transmission cycle.

It should be noted that X and M may be the same or different, and Y and N may be the same or different, that is, the time required for the terminal device to switch the uplink BWP may be the same or different from the time required for switching the downlink BWP.

For example, the time point two may be predetermined. For example, time two is X time units after the configuration information of the second downlink BWP is received or Y time unit after the configuration information of the second downlink BWP is received. For example, a time unit is a frame, radio frame, subframe, slot, or transmission cycle. For example, X is a positive integer. For example, Y is a positive integer.

In another embodiment, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a connected mode (connected mode), and the center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP.

For example, it may be specified that the center frequencies of the upstream BWP and the downstream BWP used by the network device when the terminal device is in the connected state, configured for the terminal device by the network device, are the same. When the terminal equipment in the connection state is communicated with the network equipment, the radio frequency point does not need to be readjusted when the uplink and the downlink are mutually converted, the power consumption of the terminal equipment can be reduced, and the increase of communication delay caused by frequent conversion is avoided.

The first downlink BWP may be an independent initial downlink BWP or a non-independent initial downlink BWP, and the first uplink BWP may be an independent initial uplink BWP or a non-independent initial uplink BWP, which may include the following:

in a first mode, the first downlink BWP is a separate initial downlink BWP, and the first uplink BWP is a separate initial uplink BWP.

For example, the first downlink BWP may be an independent initial downlink BWP configured by the network device for the second type of terminal device, and the first uplink BWP may be an independent initial uplink BWP configured by the network device for the second type of terminal device. The center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP.

The center frequency of the first downlink BWP is the same as that of the first uplink BWP, so that the radio frequency point can be prevented from being readjusted when the terminal equipment performs mutual switching between uplink and downlink, and the power consumption of the terminal equipment can be reduced.

For example, for a low-capability terminal device of the second type, the network device may configure the first downlink BWP and the first uplink BWP at the edge of the carrier bandwidth, which can avoid that the narrower bandwidth of the low-capability terminal device affects the frequency domain resource continuity of other high-bandwidth terminal devices.

For example, it may be specified that the center frequency of the initial downlink BWP used by the network device in the connected state configured for the second type of terminal device is the same as the center frequency of the initial uplink BWP.

The second type of terminal device does not expect the center frequency of a set of initial downstream BWPs and initial upstream BWPs used by the terminal device when the terminal device is in the connected state to be different for the network device configuration.

In a second mode, the first downlink BWP is a dependent initial downlink BWP, and the first uplink BWP is a dependent initial uplink BWP.

That is, the first downlink BWP may be a non-independent initial downlink BWP used by the network device when the multiple types of terminal devices configured by the network device are in the connected state, and the first uplink BWP may be a non-independent initial uplink BWP used by the network device when the multiple types of terminal devices are in the connected state. The center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP.

For example, it may be specified that the center frequency of the initial downlink BWP used by the network device in the connected state configured for the terminal device is the same as the center frequency of the initial uplink BWP.

The terminal device does not expect that the center frequencies of the initial downlink BWP and the initial uplink BWP used when the network device is configured for the terminal device and in the connected state are different. The terminal device expects that the center frequencies of the initial downlink BWP and the initial uplink BWP used by the network device in the connected state, which are configured for the terminal device, are the same.

That is, in this alternative embodiment, whether the type of the terminal device is the first type or the second type, the center frequency of the downlink initial BWP used by the network device in the connected state, configured for the terminal device by the network device, needs to be consistent with the center frequency of the uplink initial BWP, that is, the center frequency is the same.

In a third way, the first downlink BWP is a dependent initial downlink BWP, and the first uplink BWP is an independent initial uplink BWP.

In a fourth way, the first downstream BWP is an independent initial downstream BWP, and the first upstream BWP is a dependent initial upstream BWP.

In another embodiment, the first downlink BWP and the first uplink BWP are BWPs that can be used by the terminal device in both connected mode and unconnected mode.

Illustratively, the first downlink BWP is an initial downlink BWP and the first uplink BWP is an initial uplink BWP.

For example, the network device notifies the terminal device of the first downlink BWP being the initial downlink BWP through the configuration information of the first downlink BWP, and notifies the terminal device of the first uplink BWP being the initial uplink BWP through the configuration information of the second uplink BWP, and the terminal device may use the first downlink BWP and the first uplink BWP when in the connected state, or may use the first downlink BWP and the first uplink BWP when in the unconnected state.

For example, before S401, the terminal device may report to the network device that the center frequency of the uplink BWP supported or not supported by the terminal device is different from the center frequency of the downlink BWP.

In one example, the terminal device may send capability information to the network device, where the capability information indicates that the center frequency of the uplink BWP supported or not supported by the terminal device is different from the center frequency of the downlink BWP.

Accordingly, the network device receives the capability information from the terminal device, and if the capability information indicates that the center frequency of the uplink BWP supported by the terminal device is different from the center frequency of the downlink BWP, the center frequencies of the first downlink BWP and the first uplink BWP configured by the network device for the terminal device may be the same or different. If the capability information indicates that the center frequency of the uplink BWP that is not supported by the terminal device is different from the center frequency of the downlink BWP, the network device configures the first downlink BWP and the first uplink BWP with the same center frequency for the terminal device.

In another example, if the terminal device supports the difference between the center frequencies of the first downlink BWP and the first uplink BWP, the terminal device reports first information to the network device, where the first information is used to indicate that the center frequency of the terminal device supporting the uplink BWP is different from the center frequency of the downlink BWP. If the center frequencies of the first downlink BWP and the first uplink BWP are not supported to be different, the terminal device does not report the first information to the network device.

The network device obtains the first information from the terminal device, and the network device may determine that the center frequency of the uplink BWP supported by the terminal device is different from the center frequency of the downlink BWP, and the center frequencies of the first downlink BWP and the first uplink BWP configured for the terminal device by the network device may be the same or different. If the network device does not receive the first information from the terminal device, the network device considers that the center frequency of the uplink BWP that is not supported by the terminal device is different from the center frequency of the downlink BWP, and the network device configures the first downlink BWP and the first uplink BWP with the same center frequency for the terminal device. If the center frequency point of the uplink BWP is different from the center frequency point of the downlink BWP, the terminal device needs to be configured with two Phase Lock Loops (PLLs) in hardware for clock synchronization of the uplink information and clock synchronization of the downlink information, respectively. Therefore, whether the terminal device supports the uplink BWP with a different center frequency point from that of the downlink BWP is the same as whether the terminal device is configured with 2 PLLs. If the terminal device is configured with only one PLL, the terminal device only supports that the center frequency point of the uplink BWP is the same as the center frequency point of the downlink BWP, and the clock synchronization of the uplink information and the clock synchronization of the downlink information share the one PLL configured in the terminal device. However, the present application is not limited to this, and whether the terminal device supports the difference between the center frequency point of the uplink BWP and the center frequency point of the downlink BWP may also be determined based on other conditions.

S402, the terminal device determines the first downlink BWP according to the configuration information of the first downlink BWP, and determines the first uplink BWP according to the configuration information of the second downlink BWP.

After receiving the configuration information of the first downlink BWP, the terminal device determines the first downlink BWP according to the configuration information of the first downlink BWP, and after receiving the configuration information of the first uplink BWP, the terminal device determines the first uplink BWP according to the configuration information of the first uplink BWP. It should be noted that, in the embodiment of the present application, the order of determining the first downlink BWP and the first uplink BWP by the terminal device is not limited. The terminal device may determine the first downlink BWP and the first uplink BWP after receiving the two configuration information in the same message. Or the two pieces of configuration information may be received in different messages, and the corresponding BWP may be determined based on the received configuration information.

If the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in the connected state, the terminal device may receive downlink information from the network device using the first downlink BWP and send uplink information to the network device using the first uplink BWP while in the connected state.

If the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in the unconnected state, the terminal device may use the first downlink BWP to receive downlink information from the network device and use the first uplink BWP to send uplink information to the network device when the terminal device is in the unconnected state.

According to the scheme provided by the embodiment of the application, the network device may configure the uplink BWP and the downlink BWP with the same or different center frequencies for the terminal device based on the state (including one or more of the connected state, the idle state, and the inactive state) in which the terminal device is located. The low-power terminal equipment can be accessed into the network, and the system bandwidth resource of the network equipment is utilized to communicate with the network equipment. The flexibility of network configuration BWP is increased, enabling the network to meet the communication needs of a variety of application scenarios.

In one embodiment, the center frequencies of the initial downlink BWP and the initial uplink BWP used by the terminal device in the unconnected state may be different. The center frequencies of the initial downlink BWP and the initial uplink BWP used by the terminal device in the connected state are the same.

For example, when the terminal device is in the unconnected state, the center frequencies of the initial downlink BWP and the initial uplink BWP used by the terminal device to communicate with the network device may be different. That is, the center frequencies of the initial downlink BWP and the initial uplink BWP used by the terminal device in the unconnected state are different or the same. When the terminal device is in the connected state, the center frequencies of the initial downlink BWP and the initial uplink BWP used when the terminal device communicates with the network device are the same. When the terminal device is in the connected state, the terminal device does not expect the center frequency of the initial downlink BWP and the initial uplink BWP to be different.

For another example, when the terminal device is in the unconnected state, the center frequencies of the initial downlink BWP and the initial uplink BWP configured for the terminal device by the network device are the same or different. When the terminal device is in the unconnected state, the network device may configure the center frequencies of the initial downstream BWP and the initial upstream BWP of the terminal device to be different or the same. When the terminal device is in a connected state, the network device determines the configuration of an initial downlink BWP and an initial uplink BWP of the terminal device, where the center frequency of the initial downlink BWP is the same as the center frequency of the initial uplink BWP.

For another example, when the terminal device is in the unconnected state, the center frequencies (center frequencies) of the initial downlink BWP and the initial uplink BWP used for the terminal device to communicate with the network device are different. When the terminal device is in the connected state, the center frequencies of the initial downlink BWP and the initial uplink BWP used when the terminal device communicates with the network device are the same. After the terminal device leaves the non-connected state or enters the connected state, the terminal device determines the initial BWP used in communication with the network device according to the configuration of the initial BWP in the connected state. The configuration of the initial BWP used when the terminal device is in the unconnected state is different from the configuration of the initial BWP used when the terminal device is in the connected state. The initial BWP includes an initial upstream BWP and/or an initial downstream BWP. For example, the initial downlink BWP when the terminal device is in the unconnected state is configured for the MIB, and the initial downlink BWP when the terminal device is in the connected state is configured for the SIB. Or the initial downlink BWP when the terminal device is in the unconnected state is configured for the MIB, and the initial downlink BWP when the terminal device is in the connected state is configured for the RRC message. Or, the initial uplink BWP when the terminal device is in the non-connected state is configured with the SIB, and the initial uplink BWP when the terminal device is in the connected state is configured with the RRC message.

In one possible embodiment:

the terminal device obtains configuration information of the first downlink partial bandwidth BWP and configuration information of the first uplink BWP.

The terminal device determines a first downlink BWP according to the configuration information of the first downlink BWP, and determines a first uplink BWP according to the configuration information of the first uplink BWP.

For example, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a connected state or after initial access, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP. And/or the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state or initial access, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, where the non-connected state is an idle state or an inactive state.

For example, the first downlink BWP and the first uplink BWP are initial BWPs of the terminal device, and a center frequency of the first downlink BWP and a center frequency of the first uplink BWP are the same or different. And/or the first downlink BWP and the first uplink BWP are non-initial BWPs of the terminal device, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP.

For example, the first downlink BWP is an independent initial downlink BWP, and the first downlink BWP does not include the entire first resource, the first uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP, and the center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP. And/or the first downlink BWP is an independent initial downlink BWP, and the first downlink BWP includes the entire first resource, the first uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP. The first resource includes: CORESET0 and/or SSB bandwidth.

If the first downlink BWP is an independent initial downlink BWP, the terminal device does not expect the first downlink BWP to include one or more of cell-defined SSBs, non-cell-defined SSBs, CORESET0, and system information block. And/or the first downlink BWP is an active BWP configured by a radio resource control RRC, and the terminal device expects the first downlink BWP to include one or more of a cell-defined SSB, a non-cell-defined SSB, and a channel state information reference signal CSI-RS.

In another possible embodiment:

the network device determines configuration information for the first downstream fractional bandwidth BWP and determines configuration information for the first upstream BWP.

The network device transmits configuration information of the first downlink BWP and configuration information of the first uplink BWP.

For example, the first downlink BWP and the first uplink BWP are BWPs used by a terminal device in a connected state or after initial access, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP. And/or the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state or initial access, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, where the non-connected state is an idle state or an inactive state.

If the first downlink BWP is an independent initial downlink BWP and the first downlink BWP does not contain the entire first resource, the first uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP, and the center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP. And/or the first downlink BWP is an independent initial downlink BWP, and the first downlink BWP includes the entire first resource, the first uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP. The first resource includes: CORESET0 and/or SSB bandwidth.

If the first downlink BWP is an independent initial downlink BWP, the first downlink BWP configured by the network device for the terminal device does not include one or more of cell-defined SSB, non-cell-defined SSB, CORESET0, and system information block. And/or the first downlink BWP is an active BWP configured by radio resource control RRC, and the first downlink BWP configured by the network device for the terminal device includes one or more of cell-defined SSB, non-cell-defined SSB, and channel state information reference signal CSI-RS.

Another embodiment of the present invention is set forth below.

Not only whether the center frequency of the first downlink BWP and the center frequency of the first uplink BWP are the same may be agreed according to the RRC connection state of the terminal device, but also whether the center frequency of the first downlink BWP and the center frequency of the first uplink BWP are the same may be agreed according to whether the terminal device is in the initial access phase. For example, after the terminal device is in a connected state or initially connected, the center frequency of the first downlink BWP of the terminal device is the same as the center frequency of the first uplink BWP. That is, for the terminal device in the connected state or after initial access, the center frequency of the first downlink BWP configured for the terminal device by the network device is the same as the center frequency of the first uplink BWP. Therefore, the terminal equipment does not need to tune the central frequency during downlink receiving and uplink sending, the frequency tuning time is avoided, the power consumption of the terminal equipment and the complexity of information receiving/sending are reduced, and the resource utilization efficiency is improved.

Specifically, the terminal device is in a connected state or after initial access. The first downlink BWP is an independent initial downlink BWP and the first downlink BWP does not contain any or all of the first resources. The first upstream BWP is an independent initial upstream BWP or an independent initial upstream BWP. The center frequency of the first downstream BWP is the same as the center frequency of the first upstream BWP. The first resource comprises at least one of the bandwidths of CORESET0 and SSB. For example, when the terminal device does not expect the bandwidth of the first initial downlink BWP to include the first resource, the center frequencies of the first initial downlink BWP and the first initial uplink BWP are different. For example, the independent initial downlink BWP includes the first resource as at least one resource unit in the independent initial downlink BWP is not included in the first resource. E.g. the bandwidth of the independent initial downlink BWP is larger than the bandwidth of the first resource. E.g. the independent initial downlink BWP comprises the first resource. For example, a resource element is a Resource Block (RB), a Resource Element (RE), or a Control Channel Element (CCE).

Specifically, the terminal device is in a connected state or after initial access. The first downlink BWP is a downlink BWP (e.g., an independent initial downlink BWP or an initial downlink BWP that is not configured by the independent initial downlink BWP or the MIB) that receives { one or more of a random access response, a paging message, and system information }, and/or the first downlink BWP does not contain any or all of the first resources. The first uplink BWP is an uplink BWP (e.g., an independent initial uplink BWP or a non-independent initial uplink BWP) that transmits { one or more of physical random access channel, message 3, PUCCH feedback for message 4 }. The center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP. The first resource comprises at least one of CORESET0 and SSB bandwidth.

The terminal device is in a non-connected state or an initial access process, and a center frequency of the first downlink BWP and a center frequency of the first uplink BWP of the terminal device may be the same or different. That is, for a terminal device in a non-connected state or an initial access process, the center frequency of the first downlink BWP configured for the terminal device by the network device may be the same as or different from the center frequency of the first uplink BWP.

When the terminal device is in a non-connected state or in an initial access process, the terminal device and the network device do not communicate frequently, even if the center frequency of the first downlink BWP is different from the center frequency of the first uplink BWP, the center frequency tuning of the terminal device during downlink reception and uplink transmission is not frequent, and will not have a great influence on the power consumption and information processing (reception or transmission) complexity of the terminal device, but the flexibility of the configuration of the base station on the center frequency of the first downlink BWP and the center frequency of the first uplink BWP is improved, which is helpful for multiplexing the existing downlink resources (such as CORESET0 or SSB), maintaining the continuity of the uplink resources, and reducing the influence on the data transmission of the UE of the previous version. Moreover, for the terminal device in the unconnected state or the initial access process, the downlink reception and the uplink transmission are usually processed in series, and when the center frequency of the first downlink BWP is different from the center frequency of the first uplink BWP, the terminal device performs frequency tuning by using the interval time between the downlink reception and the uplink transmission, which also prevents the efficiency of using system resources from being reduced. Of course, when the terminal device is in the unconnected state or in the initial access process, the network device may configure the center frequency of the first downlink BWP to be the same as the center frequency of the first uplink BWP, so as to reduce the frequency tuning reduction between the uplink and the downlink of the low-complexity terminal device.

Specifically, the terminal device is in a non-connected state or an initial access process. The first downlink BWP is an independent initial downlink BWP and the first downlink BWP contains the entire first resource. For example, the first downlink BWP is an independent initial downlink BWP, and the first downlink BWP includes all the bandwidth occupied by the first resource. The first upstream BWP is an independent initial upstream BWP or a non-independent initial upstream BWP. The center frequency of the first downlink BWP and the center frequency of the first uplink BWP may be the same or different. The network device has more flexibility to configure the center frequency of the first downstream BWP and the center frequency of said first upstream BWP. For example, when the network device allows a low-complexity terminal device to reuse an existing downlink resource (e.g., coreset0 or SSB), and the network device keeps the uplink resource continuous as much as possible to reduce the impact on data transmission of UEs of previous releases, the network device may configure the center frequency of the first downlink BWP to be different from the center frequency of the first uplink BWP. For example, when the network device reduces the frequency of frequency tuning between the uplink and the downlink of the low-complexity terminal device, the network device may configure the center frequency of the first downlink BWP to be the same as the center frequency of the first uplink BWP.

Specifically, the terminal device is in a non-connected state or an initial access process. The first downlink BWP is a downlink BWP (e.g., an independent initial downlink BWP or an non-independent initial downlink BWP or an initial downlink BWP configured by the MIB) that receives { one or more of a random access response, a paging message, and system information }, and/or the first downlink BWP contains all of the first resources. The first uplink BWP is an uplink BWP (e.g., an independent initial uplink BWP or a non-independent initial uplink BWP) that sends { one or more of physical random access channel, message 3, and PUCCH feedback of message 4 }. The center frequency of the first downlink BWP and the center frequency of the first uplink BWP may be the same or different. The first resource comprises at least one of the bandwidths of CORESET0 and SSB.

To summarize, the center frequency of the first downstream BWP and the center frequency of the first upstream BWP of the terminal device satisfy the specifications for one or more of the following scenarios. The center frequency of the first downlink BWP and the center frequency of the first uplink BWP configured by the network device for the terminal device satisfy the requirements of one or more of the following scenarios.

Provision of scenario 1:

after the terminal device is in a connected state or initially accessed, the center frequency of the first downlink BWP of the terminal device is the same as the center frequency of the first uplink BWP. After the terminal device is in a connected state or initially accessed, the center frequency of the first downlink BWP configured for the terminal device by the network device is the same as the center frequency of the first uplink BWP. For example, the first downlink BWP is an independent initial downlink BWP. For example, the first upstream BWP is an independent initial upstream BWP or a non-independent initial upstream BWP.

Definition of scenario 2:

the terminal device is in a non-connection state or an initial access process, the first downlink BWP is an independent initial downlink BWP, the first downlink BWP does not include the whole first resource, the first uplink BWP is an independent initial uplink BWP or an independent initial uplink BWP, and a center frequency of the first downlink BWP of the terminal device is the same as a center frequency of the first uplink BWP. The center frequency of the first downlink BWP configured by the network device for the terminal device is the same as the center frequency of the first uplink BWP.

Provision of scenario 3:

the terminal device is in a non-connected state or an initial access process, the first downlink BWP is an independent initial downlink BWP, the first downlink BWP includes the entire first resource, the first uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP, and a center frequency of the first downlink BWP of the terminal device is the same as or different from a center frequency of the first uplink BWP. The center frequency of the first downlink BWP configured by the network device for the terminal device is the same as or different from the center frequency of the first uplink BWP.

The first resource includes: CORESET0 and/or SSB bandwidth.

Another embodiment of the present invention is set forth below.

The first downlink BWP is an independent initial downlink BWP, and the terminal device does not expect the first downlink BWP to include one or more of cell-defined SSB, non-cell-defined SSB, CORESET0, and system information block. Or, the first downlink BWP is an independent initial downlink BWP in the initial access process, and the terminal device does not expect that the first downlink BWP includes one or more of SSB defined by the cell, SSB defined by a non-cell, CORESET0, and system information block.

Since the terminal device does not expect the first downlink BWP to include one or more of cell-defined SSB, non-cell-defined SSB, CORESET0, and system information block, the first downlink BWP may not include one or more of cell-defined SSB, non-cell-defined SSB, CORESET0, and system information block, thereby enabling saving of resources in the first downlink BWP. The terminal device may tune to another resource to receive one or more of the cell-defined SSB, the non-cell-defined SSB, CORESET0, and the system information block, thereby saving system overhead. It should be noted that the exclusion of the present invention is understood to not support transmission. Optionally, in order to reduce the limitation on the network device, the first downlink BWP configured by the network device may not include one or more of a cell-defined SSB, a non-cell-defined SSB, CORESET0, and a system information block, and may also include one or more of a cell-defined SSB, a non-cell-defined SSB, CORESET0, and a system information block.

The first downlink BWP is an active BWP configured by the radio resource control RRC, and the terminal device expects the first downlink BWP to include one or more of cell-defined SSBs, non-cell-defined SSBs, and channel state information reference signals CSI-RS. Or, the first downlink BWP is a downlink BWP (initial or non-initial) after the initial access process, and the terminal device expects the first downlink BWP to include one or more of a cell-defined SSB, a non-cell-defined SSB, and a channel state information reference signal CSI-RS.

For the active BWP configured by the radio resource control RRC or after the terminal device is in the initial access process, the communication between the terminal device and the network device is relatively frequent, if the first downlink BWP includes one or more of the SSB defined by the cell, the SSB defined by the non-cell, the CORESET0, and the system information block, the terminal device does not need to tune to another resource to receive one or more of the SSB defined by the cell, the SSB defined by the non-cell, the CORESET0, and the system information block, thereby avoiding frequent frequency tuning of the terminal device and saving power consumption of the terminal device. Optionally, in order to reduce the limitation on the network device, the first downlink BWP configured by the network device may include one or more of cell-defined SSB, non-cell-defined SSB, core set0, and system information block, or may not include one or more of cell-defined SSB, non-cell-defined SSB, core set0, and system information block.

Another embodiment of the present invention is set forth below.

The first downlink BWP and the first uplink BWP are the initial BWP of the terminal device, and the center frequency of the first downlink BWP and the center frequency of the first uplink BWP are the same or different. The center frequency of the first downlink BWP configured by the network device for the terminal device may be the same as or different from the center frequency of the first uplink BWP.

The first downlink BWP and the first uplink BWP are non-initial BWPs of the terminal device, and the center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP. The center frequency of the first downlink BWP configured by the network device for the terminal device is the same as the center frequency of the first uplink BWP.

For example, the first downstream BWP is an independent initial downstream BWP and the first upstream BWP is an independent initial upstream BWP.

For example, the first downstream BWP is an independent initial downstream BWP and the first upstream BWP is a non-independent initial upstream BWP.

For example, the first downstream BWP is a non-independent initial downstream BWP and the first upstream BWP is an independent initial upstream BWP.

For example, the first downstream BWP is a non-independent initial downstream BWP and the first upstream BWP is a non-independent initial upstream BWP.

In this way, the network device may configure the terminal device with the same or different center frequencies of the upstream BWP and the downstream BWP based on the usage (including one or more of the initial BWP and the non-initial BWP) of the BWP of the terminal device. The low-energy terminal equipment can be accessed to the network, and the system bandwidth resources of the network equipment are utilized to communicate with the network equipment. The flexibility of configuring BWP by the network equipment is increased, so that the system can meet the communication requirements of various application scenes.

Herein, the center frequency of the first downlink BWP and the center frequency of the first uplink BWP may be the same or different, that is, the center frequency of the first downlink BWP and the center frequency of the first uplink BWP may be different or the same. This provides greater flexibility in the configuration of the network devices. Because of the initial access process or the non-connection state, the transmission delay requirement of the terminal equipment is low, and the frequency tuning influence caused by the misalignment of the uplink and downlink central frequency points is small. The center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP, and the center frequency of the first downlink BWP is not expected to be different from the center frequency of the first uplink BWP for the terminal device, or the center frequency of the first downlink BWP and the center frequency of the first uplink BWP cannot be configured to be different by the network device. The flexibility of the resource allocation of the network equipment is limited, but the frequency tuning between the uplink and the downlink of the terminal equipment is avoided, the interruption of the transmission of the terminal equipment is avoided, and the time delay of the transmission is shortened.

In this way, when the terminal device is in the non-connected state, the network device does not obtain the relevant information of the terminal device sufficiently, the center frequencies of the initial downlink BWP and the initial uplink BWP used when the terminal device is in the non-connected state may be allowed to be different, and the terminal device may use multiple modes, such as the same or different uplink center frequencies and the different uplink center frequencies, to access the network as much as possible. When the terminal device is connected to the network, the center frequencies of the initial downlink BWP and the initial uplink BWP used when the terminal device is connected are required to be the same. The radio frequency points do not need to be readjusted when the terminal equipment in the connection state is switched between uplink and downlink in the communication process, the power consumption of the terminal equipment can be reduced, and the communication time delay increase caused by frequent switching is avoided.

In the embodiments provided in the present application, the method provided in the embodiments of the present application is introduced from the perspective of a network device, a terminal device, and interaction between the network device and the terminal device. In order to implement the functions in the method provided by the embodiments of the present application, the network device and the terminal device may include a hardware structure and/or a software module, and the functions are implemented in the form of a hardware structure, a software module, or a hardware structure and a software module. Whether any of the above functions is implemented as a hardware structure, a software module, or a combination of a hardware structure and a software module depends upon the particular application and design constraints imposed on the technical solution. The steps executed by the network device may also be implemented by different communication apparatuses. For example: the first device is configured to determine configuration information of the first downlink BWP and determine configuration information of the first uplink BWP, and the second device is configured to send the configuration information of the first downlink BWP and send the configuration information of the first uplink BWP to the terminal device, that is, the first device and the second device jointly complete the steps performed by the network device in the embodiment of the present application, which is not limited to a specific division manner. When the network architecture includes one or more DUs, one or more CUs, and one or more Radio Units (RUs), the steps performed by the network device described above may be implemented by a DU, a CU, and an RU, respectively. In order to implement the functions in the method provided by the embodiments of the present application, the terminal device and the network device may include a hardware structure and/or a software module, and the functions are implemented in the form of a hardware structure, a software module, or a hardware structure and a software module. Whether any of the above-described functions is implemented as a hardware structure, a software module, or a hardware structure plus a software module depends upon the particular application and design constraints imposed on the technical solution.

Fig. 7 is a schematic structural diagram of a possible communication device provided in an embodiment of the present application. The communication device can realize the functions of the terminal equipment or the network equipment in the method embodiment, so that the beneficial effects of the method embodiment can be realized. In this embodiment of the application, the communication apparatus may be the terminal device 110 shown in fig. 1, or may be the access network device 120 shown in fig. 1, or may be a module (e.g., a chip) applied to the terminal device or the access network device.

When the communication apparatus 700 is used to implement the functions of the terminal device in the method embodiment: the transceiver module 701 is configured to receive configuration information of a first downlink BWP and configuration information of a first uplink BWP from a network device. A processing module 702, configured to determine the first downlink BWP according to the configuration information of the first downlink BWP, determine the first uplink BWP according to the configuration information of the first uplink BWP, and invoke the transceiver module 701 to transmit or receive a signal to or from a network device.

When the communication apparatus 700 is used to implement the functions of the network device in the method embodiment: a processing module 702 is configured to determine configuration information for the first downstream BWP and to determine configuration information for the first upstream BWP. The transceiver module 701 is configured to send configuration information of the first downlink BWP to the terminal device, and send configuration information of the first uplink BWP.

For a more detailed description of the transceiver module 701 and the processing module 702, reference may be made to the description of the above method embodiments, and no further description is provided here.

Fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

The terminal device 800 shown in fig. 8 may be adapted for use in the system shown in fig. 1. For ease of illustration, fig. 8 shows only the main components of the terminal device 800. As shown in fig. 8, the terminal device 800 includes a processor, a memory, a control circuit, an antenna, and an input-output means. The processor is mainly used for processing a communication protocol and communication data, controlling the entire terminal device 800, executing a software program, and processing data of the software program. The memory is used primarily for storing software programs and data. The control circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, microphones, keyboards, etc., are mainly used for receiving data input by users and outputting data to users.

Taking the terminal device 800 as a mobile phone as an example, when the terminal device 800 is powered on, the processor may read the software program in the storage unit, interpret and execute the instruction of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor carries out baseband processing on the data to be sent and then outputs baseband signals to the control circuit, and the control circuit carries out radio frequency processing on the baseband signals and then sends the radio frequency signals to the outside in an electromagnetic wave mode through the antenna. When data is transmitted to the terminal device 800, the control circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.

Those skilled in the art will appreciate that fig. 8 shows only one memory and processor for ease of illustration. In some embodiments, terminal device 800 may include multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this respect in the embodiment of the present invention.

As an alternative implementation manner, the processor may include a baseband processor and a central processing unit, the baseband processor is mainly used for processing the communication protocol and the communication data, and the central processing unit is mainly used for controlling the whole terminal device 800, executing the software program, and processing the data of the software program. The processor in fig. 8 integrates the functions of the baseband processor and the central processing unit, and those skilled in the art will understand that the baseband processor and the central processing unit may also be independent processors, and are interconnected through a bus or the like. Terminal device 800 may include multiple baseband processors to accommodate different network formats, terminal device 800 may include multiple central processors to enhance its processing capabilities, and various components of terminal device 800 may be connected by various buses. The baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be built in the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.

In one example, the antenna and the control circuit having the transceiving function may be regarded as the transceiving unit 810 of the terminal device 800, and the processor having the processing function may be regarded as the processing unit 820 of the terminal device 800. As shown in fig. 8, the terminal device 800 includes a transceiving unit 810 and a processing unit 820. A transceiver unit may also be referred to as a transceiver, a transceiving device, etc. Optionally, a device used for implementing the receiving function in the transceiver 810 may be regarded as a receiving unit, and a device used for implementing the transmitting function in the transceiver 810 may be regarded as a transmitting unit, that is, the transceiver 810 includes a receiving unit and a transmitting unit. For example, the receiving unit may also be referred to as a receiver, a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitting circuit, etc.

The embodiment of the present application further provides a network device, which may be used in the foregoing embodiments. The network device comprises means (means), units and/or circuits to implement the functionality of the network device described in the embodiment shown in fig. 4. For example, the network device includes a transceiver module for supporting the terminal device to implement a transceiver function, and a processing module for supporting the network device to process the signal. It is to be understood that the first network device and the second network device are interchangeable with respect to a certain UE or UEs and with respect to other UEs.

Fig. 9 is a schematic structural diagram of a network device 20 according to an embodiment of the present application. As shown in fig. 9, network device 20 may be suitable for use in the system shown in fig. 1. The network device 20 is, for example, the network device shown in fig. 1. The network device 20 may function as a first network device for one or some UEs or as a second network device for one or some UEs. The network device includes: baseband device 201, rf device 202, antenna 203. In the uplink direction, rf apparatus 202 receives information transmitted by the terminal device through antenna 203, and transmits the information transmitted by the terminal device to baseband apparatus 201 for processing. In the downlink direction, the baseband device 201 processes the information of the terminal device and sends the information to the radio frequency device 202, and the radio frequency device 202 processes the information of the terminal device and sends the information to the terminal device through the antenna 203.

The baseband device 201 includes one or more processing units 2011, a storage unit 2012, and an interface 2013. Wherein the processing unit 2011 is configured to support the network device to perform the functions of the network device in the above method embodiments. The storage unit 2012 stores software programs and/or data. Interface 2013 is used to exchange information with RF device 202 and includes interface circuitry for the input and output of information. In one implementation, the processing units are integrated circuits, such as one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip. The memory unit 2012 and the processing unit 2011 may be located in the same chip, i.e., on-chip memory devices. Alternatively, the memory unit 2012 and the processing unit 2011 can be on a different chip than the processing unit 2011, i.e., an off-chip memory unit. The storage unit 2012 may be a single memory or a combination of multiple memories or storage elements.

A network device may implement some or all of the steps in the above-described method embodiments in the form of one or more processing unit schedulers. For example to implement the corresponding functionality of the network device in fig. 4. The one or more processing units may support wireless access technologies of the same system, and may also support wireless access systems of different systems.

When the communication device is a chip-like device or circuit, the device may comprise a transceiver unit and a processing unit. The transceiver unit may be an input/output circuit and/or a communication interface; the processing unit is an integrated processor or microprocessor or integrated circuit.

The embodiment of the present application further provides a communication system, and specifically, the communication system includes a network device and a terminal device, or may further include more network devices and a plurality of terminal devices. Illustratively, the communication system includes a network device and a terminal device for implementing the related functions of fig. 4 described above.

The network devices are respectively used for realizing the functions of the related network part of the figure 4. The terminal device is configured to implement the function of the terminal device related to fig. 4. For details, please refer to the related description in the above method embodiments, which is not repeated herein.

Also provided in an embodiment of the present application is a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method performed by the network device in fig. 4; or when running on a computer, causes the computer to perform the method performed by the terminal device of fig. 4.

Also provided in an embodiment of the present application is a computer program product, which includes instructions that, when executed on a computer, cause the computer to perform the method performed by the network device in fig. 4; or when run on a computer, cause the computer to perform the method performed by the terminal device of fig. 4.

The embodiment of the application provides a chip system, which comprises a processor and a memory, and is used for realizing the functions of network equipment or a terminal in the method; or for implementing the functions of the network device and the terminal in the foregoing methods. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps (step) described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a portable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for resource allocation, comprising:

the terminal equipment acquires configuration information of a first downlink partial bandwidth BWP and configuration information of a first uplink BWP;

the terminal device determines a first downlink BWP according to the configuration information of the first downlink BWP, and determines a first uplink BWP according to the configuration information of the first uplink BWP;

wherein the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a connected state or after initial access, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP; or,

the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state or initial access, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, where the non-connected state is an idle state or an inactive state; or,

the first downlink BWP and the first uplink BWP are initial BWPs of the terminal device, and a center frequency of the first downlink BWP and a center frequency of the first uplink BWP are the same or different; or,

the first downlink BWP and the first uplink BWP are non-initial BWPs of the terminal device, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP.

2. The method according to claim 1, wherein the first downstream BWP and the first upstream BWP are BWPs with which the terminal device is in a connected state,

the first downlink BWP is an independent initial downlink BWP, and the first uplink BWP is an independent initial uplink BWP; or the like, or a combination thereof,

the first downlink BWP is a dependent initial downlink BWP, and the first uplink BWP is a dependent initial uplink BWP; or the like, or a combination thereof,

the first downlink BWP is an independent initial downlink BWP, and the first uplink BWP is a dependent initial uplink BWP; or,

the first downstream BWP is a dependent initial downstream BWP and the first upstream BWP is a dependent initial upstream BWP.

3. The method according to claim 1, wherein the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP and a center frequency of the first uplink BWP are the same or different, including:

the first downlink BWP is an independent initial downlink BWP, the first uplink BWP is an independent initial uplink BWP, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP; and/or the presence of a gas in the atmosphere,

the first downlink BWP is a dependent initial downlink BWP, the first uplink BWP is a dependent initial uplink BWP, and the center frequencies of the first downlink BWP and the first uplink BWP are the same or different; and/or the presence of a gas in the atmosphere,

the first downlink BWP is an independent initial downlink BWP, the first uplink BWP is a non-independent initial uplink BWP, and the center frequencies of the first downlink BWP and the first uplink BWP are the same or different; and/or the presence of a gas in the atmosphere,

4. The method according to claim 2 or 3,

the non-independent initial downlink BWP is an initial downlink BWP configured by a master information block MIB, or the non-independent initial downlink BWP is an initial downlink BWP configured by a system information block SIB 1.

5. The method according to any of claims 1-4 wherein the BWP ID of the first downstream BWP and the first upstream BWP are the same.

6. The method of any of claims 1-5, wherein a center frequency of the first downstream BWP is different from a center frequency of the first upstream BWP, the method further comprising:

the terminal device obtains configuration information of a second downlink BWP, where a center frequency of the second downlink BWP is the same as a center frequency of the first uplink BWP, and a BWP ID of the second downlink BWP is the same as a BWP ID of the first uplink BWP.

7. The method according to any of claims 1-6, wherein the center frequency of the first uplink BWP is different from the center frequency of the first downlink BWP, the method further comprising:

the terminal device obtains configuration information of a second uplink BWP, the center frequency of the first downlink BWP is the same as the center frequency of the second uplink BWP, and the BWP ID of the second uplink BWP is the same as the BWP ID of the first downlink BWP.

8. The method according to any one of claims 1-7, further comprising:

and the terminal equipment reports first information, wherein the first information indicates that the center frequency of the uplink BWP supported by the terminal equipment is different from the center frequency of the downlink BWP.

9. A method for resource allocation, comprising:

the network device determines the configuration information of the first downlink partial bandwidth BWP and determines the configuration information of the first uplink BWP;

the network device sends the configuration information of the first downlink BWP and the configuration information of the first uplink BWP;

wherein, the first downlink BWP and the first uplink BWP are BWPs used by a terminal device in a connected state, and a center frequency of the first downlink BWP is the same as a center frequency of the first uplink BWP; and/or the presence of a gas in the atmosphere,

the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, and the non-connected state is an idle state or an inactive state.

10. The method according to claim 9, wherein the first downstream BWP and the first upstream BWP are BWPs with which the terminal device is in a connected state,

11. The method according to claim 9, wherein the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP and a center frequency of the first uplink BWP are the same or different, including:

the first downlink BWP is an independent initial downlink BWP, the first uplink BWP is an independent initial uplink BWP, and the center frequencies of the first downlink BWP and the first uplink BWP are the same; and/or the presence of a gas in the gas,

the first downlink BWP is a dependent initial downlink BWP, the first uplink BWP is an independent initial uplink BWP, and the center frequencies of the first downlink BWP and the first uplink BWP are the same or different; and/or the presence of a gas in the gas,

the first downlink BWP is an independent initial downlink BWP, the first uplink BWP is a non-independent initial uplink BWP, and the center frequencies of the first downlink BWP and the first uplink BWP are the same or different; and/or the presence of a gas in the gas,

12. The method according to claim 10 or 11,

13. Method according to any of claims 9-12, wherein the BWP ID of the first downstream BWP and the first upstream BWP are the same.

14. The method according to any of claims 9-13, wherein the center frequency of the first downstream BWP and the center frequency of the first upstream BWP are different, the method further comprising:

the network device sends configuration information of a second downlink BWP, where a center frequency of the second downlink BWP is the same as a center frequency of the first uplink BWP, and a BWP ID of the second downlink BWP is the same as a BWP ID of the first uplink BWP.

15. The method according to any of claims 9-14, wherein the center frequency of the first uplink BWP and the center frequency of the first downlink BWP are different, the method further comprising:

the network device sends configuration information of a second uplink BWP, where a center frequency of the first downlink BWP is the same as a center frequency of the second uplink BWP, and a BWP ID of the second uplink BWP is the same as a BWP ID of the first downlink BWP.

16. The method according to any one of claims 9-15, further comprising:

the network device obtains first information, where the first information indicates that a center frequency of uplink BWP supported by the terminal device is different from a center frequency of downlink BWP supported by the terminal device.

17. A resource allocation apparatus, comprising:

a transceiver module, configured to obtain configuration information of a first downlink partial bandwidth BWP and configuration information of a first uplink BWP;

a processing module, configured to determine a first downlink BWP according to the configuration information of the first downlink BWP, and determine a first uplink BWP according to the configuration information of the first uplink BWP;

wherein, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in the connected state, and the center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP; and/or the presence of a gas in the gas,

the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and a center frequency of the first downlink BWP is the same as or different from a center frequency of the first uplink BWP, where the non-connected state is an idle state or an inactive state.

18. The apparatus of claim 17, wherein the first downstream BWP and the first upstream BWP are BWPs with which the terminal device is in a connected state,

the first downlink BWP is an independent initial downlink BWP, and the first uplink BWP is an independent initial uplink BWP; or,

the first downlink BWP is a dependent initial downlink BWP, and the first uplink BWP is an independent initial uplink BWP; or the like, or a combination thereof,

the first downlink BWP is an independent initial downlink BWP, and the first uplink BWP is a dependent initial uplink BWP; or the like, or a combination thereof,

19. The apparatus of claim 17, wherein the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and wherein a center frequency of the first downlink BWP and a center frequency of the first uplink BWP are the same or different, comprising:

20. The apparatus of claim 18 or 19,

21. The apparatus according to any of claims 17-20 wherein the BWP ID of the first downstream BWP and the first upstream BWP are the same.

22. The apparatus according to any of the claims 17-21, wherein the center frequency of the first downstream BWP and the center frequency of the first upstream BWP are different,

the transceiver module is further configured to acquire configuration information of a second downlink BWP, where a center frequency of the second downlink BWP is the same as a center frequency of the first uplink BWP, and a BWP ID of the second downlink BWP is the same as a BWP ID of the first uplink BWP.

23. The apparatus according to any of claims 17-22, wherein the center frequency of the first upstream BWP and the center frequency of the first downstream BWP are different,

the transceiver module is further configured to acquire configuration information of a second uplink BWP, where a center frequency of the first downlink BWP is the same as a center frequency of the second uplink BWP, and a BWP ID of the second uplink BWP is the same as a BWP ID of the first downlink BWP.

24. The apparatus of any one of claims 17-23,

the transceiver module is further configured to report first information, where the first information indicates that a center frequency of the uplink BWP supported by the terminal device is different from a center frequency of the downlink BWP.

25. A resource allocation apparatus, comprising:

a processing module, configured to determine configuration information of a first downlink partial bandwidth BWP, and determine configuration information of a first uplink BWP;

a transceiving module, configured to send configuration information of the first downlink BWP and configuration information of the first uplink BWP;

wherein, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in the connected state, and the center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP; and/or the presence of a gas in the atmosphere,

26. The apparatus of claim 25, wherein the first downstream BWP and the first upstream BWP are BWPs with which the terminal device is in a connected state,

the first downlink BWP is a dependent initial downlink BWP, and the first uplink BWP is a dependent initial uplink BWP; or,

27. The apparatus of claim 25, wherein the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and wherein a center frequency of the first downlink BWP and a center frequency of the first uplink BWP are the same or different, comprising:

the first downlink BWP is a dependent initial downlink BWP, the first uplink BWP is a dependent initial uplink BWP, and the center frequencies of the first downlink BWP and the first uplink BWP are the same or different; and/or the presence of a gas in the gas,

28. The apparatus of claim 26 or 27,

29. The apparatus according to any of claims 25-28 wherein the BWP ID of the first downstream BWP and the first upstream BWP are the same.

30. The apparatus according to any of the claims 25-29, wherein the center frequency of the first downstream BWP and the center frequency of the first upstream BWP are different,

the transceiver module is further configured to send configuration information of a second downlink BWP, where a center frequency of the second downlink BWP is the same as a center frequency of the first uplink BWP, and a BWP ID of the second downlink BWP is the same as a BWP ID of the first uplink BWP.

31. The apparatus according to any of the claims 25-30, wherein the center frequency of the first upstream BWP and the center frequency of the first downstream BWP are different,

the transceiver module is further configured to send configuration information of a second uplink BWP, where a center frequency of the first downlink BWP is the same as a center frequency of the second uplink BWP, and a BWP ID of the second uplink BWP is the same as a BWP ID of the first downlink BWP.

32. The apparatus of any one of claims 25-31,

the transceiver module is further configured to acquire first information, where the first information indicates that a center frequency of the uplink BWP supported by the terminal device is different from a center frequency of the downlink BWP.

33. A communications device comprising means for performing the method of any of claims 1 to 9, or any of claims 10 to 16.

34. A communications device comprising a processor and a communications interface for receiving and transmitting signals from or sending signals to other communications devices than the communications device, the processor being operable by logic circuitry or executing code instructions to implement the method of any of claims 1 to 9 or any of claims 10 to 16.

35. A computer-readable storage medium, characterized in that it stores a computer program which, when executed, implements the method of any of claims 1 to 9, or any of claims 10 to 16.

36. A computer program product, the computer program product comprising: computer program code which, when executed, implements the method of any of claims 1 to 9, or any of claims 10 to 16.