CN115942487A - Resource allocation method and communication device - Google Patents

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 technical field of communications, and more specifically, to a resource allocation method and a communications device.

Background technique

The new-generation mobile communication system defines three major categories: enhanced mobile broadband (eMBB), ultra reliable and low latency communications (URLLC) and massive machine type communications (mMTC). Application scenarios. At present, corresponding communication mechanisms are mainly designed for eMBB and URLLC scenarios. For example, for eMBB scenarios, the communication bandwidth can reach 100M level, and ultra-high data transmission rates can be achieved.

Research is currently being conducted on the mMTC scenario. As a type of terminal device in the mMTC scenario, low-capability (reduced capability, REDCAP) terminal devices have narrower communication bandwidth, lower power consumption, and fewer antennas than existing terminal devices. features. At present, the system still lacks a corresponding communication mechanism that enables REDCAP terminal equipment to use network bandwidth resources for communication. Therefore, the current communication system cannot meet the performance requirements of various application scenarios.

Contents of the invention

The present application provides a resource allocation method and a communication device, which are used to solve 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 method for configuring resources, and the execution subject of the method may be a terminal device, or may be a chip applied in the terminal device. The following description is made by taking the execution subject as a terminal device as an example.

The method includes: the terminal equipment acquires configuration information of the first downlink BWP and configuration information of the first uplink BWP. 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 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 the center frequency of the first downlink BWP and the first uplink BWP The center frequencies are the same or different, and the disconnected state is an idle state or an inactive state.

In the above manner, the network device can configure the center frequency of the uplink BWP and the downlink BWP for the terminal device to be the same or different based on the state of the terminal device (including one or more of connected state, idle state and inactive state). It can realize low-capability terminal equipment to access the network, and use the system bandwidth resources of the network equipment to communicate with the network equipment. The flexibility of configuring BWP on network devices is increased, so that the system can meet the communication requirements of various application scenarios.

In combination with the first aspect, in a possible design, when the terminal device is in a non-connected state, the center frequency (center frequency) 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 frequency of the initial downlink BWP and the initial uplink BWP used by the terminal device to communicate with the network device are the same.

When the terminal device is in the unconnected state, according to the configuration information of the initial BWP (including the initial uplink BWP and/or the initial downlink BWP) when the terminal device is in the unconnected state, determine the initial BWP used by the terminal device to communicate with the network device when it is in the unconnected state. BWP, where the center frequency of the initial downlink BWP is different from the center frequency of the initial uplink BWP.

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

That is to say, 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 the connected state, wherein the first downlink BWP is an independent The initial downlink BWP, the first uplink BWP is an independent initial uplink BWP, or, the first downlink BWP is a non-independent initial downlink BWP, and the first uplink BWP is an independent initial uplink BWP, or, the first The downlink BWP is an independent initial downlink BWP, and the first uplink BWP is a non-independent initial uplink BWP, or, the first downlink BWP is a non-independent initial downlink BWP, and the first uplink BWP is a non-independent initial uplink BWP .

In the manner described above, 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 frequency of the uplink BWP and the downlink BWP configured by the network device for the terminal device and used when the terminal device is in the connected state are the same. This enables connected terminal devices to communicate with network devices without readjusting the radio frequency when switching between uplink and downlink, which can reduce the power consumption of terminal devices and avoid the increase in communication delay caused by frequent switching .

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 non-connected state, and the center frequency of the first downlink BWP is The same as or different from the 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, and the center frequency of the first downlink BWP The frequency is the same as the center frequency of the first uplink BWP, and/or, the first downlink BWP is a non-independent initial downlink BWP, the first uplink BWP is an independent initial uplink BWP, and the first downlink BWP It is the same as or different from the center frequency of the first uplink BWP, and/or, the first downlink BWP is an independent initial downlink BWP, the first uplink BWP is a non-independent initial uplink BWP, and the first downlink The central frequencies of the BWP and the first uplink BWP are the same or different, and/or, the first downlink BWP is a non-independent initial downlink BWP, the first uplink BWP is a non-independent initial uplink BWP, and the first Center frequencies of the downlink BWP and the first uplink BWP are the same or different.

In the above method, the first downlink BWP is the initial downlink BWP, and the first uplink BWP is the initial uplink BWP. Whether the downlink BWP and/or the first uplink BWP are independent initial BWPs, the center frequency of the first downlink BWP is configured to be the same as or different from the center frequency of the first uplink BWP. The flexibility of configuring BWP on the network is increased, so that the network can meet the communication requirements of various application scenarios. Among them, the network device can configure the center frequency of the first downlink BWP used when the terminal device is in the unconnected state to be the same as the center frequency of the first uplink BWP, which can prevent the terminal device from performing mutual communication between uplink and downlink when the terminal device is in the unconnected state. Readjusting the radio frequency point during switching can reduce the power consumption of the terminal equipment.

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

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

In the manner described above, the first downlink BWP and the first uplink BWP may be a group of BWPs that are simultaneously activated and used for communication between the network device and the terminal device. The terminal device receives downlink information from the network device on the resources in the downlink BWP, and sends uplink information to the network device on the resources in the uplink BWP. Wherein, the BWP IDs of the uplink BWP and the downlink BWP that are activated at the same time are the same.

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

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

With reference to the first aspect, in a possible design, the center frequency of the first uplink BWP is different from the center frequency of the first downlink BWP, and the method further includes: the terminal device acquires the second uplink BWP configuration information, 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.

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

In the above manner, the first downlink BWP and the first uplink BWP can be the initial BWP used by the terminal device in the unconnected state, and the network device can 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 equipment in the connected state is the same as that of the initial downlink BWP. The terminal device does not expect the central frequency point of the initial uplink BWP used by the terminal device in the connected state configured by the network device to be different from that of the initial downlink BWP. It can realize that when the terminal equipment is in the connected state and uses the initial uplink BWP and the initial downlink BWP, there is no need to readjust the radio frequency point when switching between uplink and downlink, and the power consumption of the terminal equipment can be reduced.

With reference to the first aspect, in a possible design, the method further includes: the terminal device reports first information, and the first information indicates that the first terminal device supports the center frequency of the uplink BWP and the center frequency of the downlink BWP. The center frequencies are different.

In the above method, the terminal device can report the capability of the terminal device to the network device. If the center frequency of the uplink BWP 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 for the terminal device. The center frequencies can be the same or different. If the terminal device does not support the center frequency of the uplink BWP being 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. It can realize that the network equipment is based on the capability of the terminal equipment, configure the BWP for the terminal equipment that meets the terminal equipment capability, and prevent the network equipment from configuring the BWP that does not meet the processing capability for the terminal equipment, resulting in the failure of communication, and improving the communication efficiency of the system.

In a second aspect, the present application provides a method for configuring resources, and the execution body of the method may be a network device or a chip applied to the network device. The following description is made by taking the execution subject as an example of a network device.

The method includes: the network device determines the configuration information of the first downlink BWP, and determines the configuration information of the first uplink BWP. The network device sends 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 first downlink BWP and the first uplink BWP are the BWPs used by the terminal device in the unconnected state, and the center frequency of the first downlink BWP and the center frequency of the first uplink BWP The frequencies are the same or different, and the non-connected state is an idle state or an inactive state.

With reference to the second aspect, in a possible design, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in the 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 a non-independent 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 non-independent initial uplink BWP, or,

The first downlink BWP is a non-independent initial downlink BWP, and the first uplink BWP is a non-independent initial uplink BWP.

With reference to the second aspect, in a possible design, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state, and the center frequency of the first downlink BWP is The same as or different from the 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, and the first downlink BWP and the first uplink BWP have the same center frequency; and/or,

The first downlink BWP is a non-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 or different, and/or ,

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 first downlink BWP is a non-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.

With reference to the second aspect, in a possible design, the non-independent initial downlink BWP is an initial downlink BWP configured in a master information block MIB, or the non-independent initial downlink BWP is an initial downlink BWP configured in a system information block SIB1.

With reference to the second aspect, in a possible design, the BWPIDs of the first downlink BWP and the first uplink BWP are the same.

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

With reference to the second aspect, in a possible design, the center frequency of the first uplink BWP is different from the center frequency of the first downlink BWP, and the method further includes: the network device sending the second uplink BWP configuration information, the center frequency of the first downlink BWP is different from 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.

With reference to the second aspect, in a possible design, the method further includes: the network device acquiring first information, the first information indicating that the terminal device supports the center frequency of the uplink BWP and the center frequency of the downlink BWP different.

In a third aspect, the present application provides a method for configuring resources, and the execution body of the method may be a terminal device or a chip applied in the terminal device. The following description is made by taking the execution subject as a terminal device as an example.

The method includes: the terminal equipment acquires configuration information of the first downlink BWP and configuration information of the first uplink BWP. 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 first uplink BWP. Wherein, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device after initial access or random access, and the center frequency of the first downlink BWP and the first The center frequency of the uplink BWP is the same. And/or, the first downlink BWP and the first uplink BWP are BWPs used in the initial access process or random access process of the terminal device, and the center frequency of the first downlink BWP and Center frequencies of the first uplink BWPs are the same or different.

In the above manner, the network device can configure uplink BWP and The center frequencies of the downlink BWPs are the same or different. It can realize low-capability terminal equipment to access the network, and use the system bandwidth resources of the network equipment to communicate with the network equipment. The flexibility of configuring BWP on network devices is increased, so that the system can meet the communication requirements of various application scenarios. The center frequency of the downlink BWP and uplink BWP used after the initial access is the same, because the general terminal equipment enters the service transmission process, and the service generally requires a delay, such as 1ms, so the uplink and downlink center frequency points need to be aligned to reduce the frequency tuning band coming delay effects. The center frequencies of the downlink BWP and uplink BWP used in the initial access can be different, because at this time, the service receiving delay requirement is small, and the influence of frequency tuning caused by the misalignment of the uplink and downlink center frequencies is small.

Herein, after the initial access is after the initial access process. After the random access is after the random access procedure. No distinction is made.

In a fourth aspect, the present application provides a method for configuring resources. The subject of execution of the method may be a terminal device or a chip applied in the terminal device. The following description is made by taking the execution subject as a terminal device as an example.

The method includes: the terminal equipment acquires configuration information of the first downlink BWP and configuration information of the first uplink BWP. 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 first uplink BWP. Wherein, the first downlink BWP is the non-initial downlink BWP of the terminal device, the first uplink BWP is the non-initial uplink BWP of the terminal device, and the center frequency of the first downlink BWP and the The center frequency of the first uplink BWP is the same. And/or, wherein, the first downlink BWP is the initial downlink BWP of the terminal device, the first uplink BWP is the initial uplink BWP of the terminal device, and the center frequency of the first downlink BWP It is the same as or different from the center frequency of the first uplink BWP.

In the manner described above, the network device may configure the center frequency of the uplink BWP and downlink BWP for the terminal device to be the same or different based on the use of the BWP of the terminal device (including one or more items of initial BWP and non-initial BWP). It can realize low-capability terminal equipment to access the network, and use the system bandwidth resources of the network equipment to communicate with the network equipment. The flexibility of configuring BWP on network devices is increased, so that the system can meet the communication requirements of various application scenarios.

In a fifth aspect, the present application provides a method for configuring resources, and the execution body of the method may be a network device or a chip applied in the network device. The following description is made by taking the execution subject as an example of a network device.

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

In a sixth aspect, a communication device is provided, and the beneficial effects may refer to the description of the first aspect, which will not be repeated here. The communication device has the function of implementing the actions in the method example of the first aspect above. The functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions. In a possible design, the communication device includes: a transceiver module, configured to acquire configuration information of the first downlink BWP and configuration information of the first uplink BWP. A processing module, configured to determine a first downlink BWP according to configuration information of the first downlink BWP, and determine a first uplink BWP according to 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 the BWPs used by the terminal device in the unconnected state, and the center frequency of the first downlink BWP and the center frequency of the first uplink BWP The frequencies are the same or different, and the non-connected state is an idle state or an inactive state.

The modules included in the communication device can perform the corresponding functions in the method example of the first aspect, for details, refer to the detailed description in the method example, and details are not repeated here.

In a seventh aspect, a communication device is provided, and the beneficial effects may refer to the description of the second aspect, which will not be repeated here. The communication device has the function of implementing the actions in the method example of the second aspect above. The functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions. In a 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. A transceiver 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 first downlink BWP and the first uplink BWP are the BWPs used by the terminal device in the unconnected state, and the center frequency of the first downlink BWP and the center frequency of the first uplink BWP The frequencies are the same or different, and the non-connected state is an idle state or an inactive state.

The modules included in the communication device can perform the corresponding functions in the method example of the second aspect above, for details, refer to the detailed description in the method example, and details are not repeated here.

In an eighth aspect, a communication device is provided, and the communication device may be the terminal device in the foregoing method embodiment, or a chip provided in the terminal device. The communication device includes a communication interface, a processor, and optionally, a memory. Wherein, the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface. When the processor executes the computer programs or instructions, the communication device executes the method performed by the terminal device in the above method embodiments.

In a ninth aspect, a communication device is provided, and the communication device may be the network device in the above method embodiment, or a chip set in the network device. The communication device includes a communication interface, a processor, and optionally, a memory. Wherein, the memory is used to store computer programs or instructions, and the processor is coupled to the memory and the communication interface. When the processor executes the computer programs or instructions, the communication device executes the method performed by the network device in the above method embodiments.

In a tenth aspect, a computer program product is provided, the computer program product including: computer program code, when the computer program code is executed, the method performed by the terminal device in the above aspects is executed.

In an eleventh aspect, a computer program product is provided, and the computer program product includes: computer program code, when the computer program code is executed, the method performed by the network device in the above aspects is executed.

In a twelfth aspect, the present application provides a system-on-a-chip, where the system-on-a-chip includes a processor, configured to implement functions of the terminal device in the methods in the foregoing aspects. In a possible design, the chip system further includes a memory, configured to store program instructions and/or data. The system-on-a-chip may consist of chips, or may include chips and other discrete devices.

In a thirteenth aspect, the present application provides a system-on-a-chip, where the system-on-a-chip includes a processor, configured to implement the functions of the network device in the methods of the foregoing aspects. In a possible design, the chip system further includes a memory, configured to store program instructions and/or data. The system-on-a-chip may consist of chips, or may include chips and other discrete devices.

In a fourteenth aspect, the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is run, the method performed by the terminal device in the above aspects is implemented.

In a fifteenth aspect, the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method performed by the network device in the above aspects is realized.

Description of 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 the initial BWP provided by the embodiment of the present application;

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

FIG. 4 is a schematic flowchart of a resource configuration method provided in an embodiment of the present application;

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

FIG. 6 is another schematic diagram of the first downlink BWP and the first uplink BWP provided by the embodiment of the present application;

FIG. 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

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

FIG. 9 is a schematic structural diagram of a network device provided by an embodiment of the present application.

Detailed ways

As shown in FIG. 1 , it is a schematic diagram of a possible network architecture applicable to the embodiment of the present application, including a terminal device 110 and an access network device 120 . The terminal device 110 and the access network device 120 can communicate through the Uu air interface, and the Uu air interface can be understood as a universal interface between the terminal device and the network device (universal UE to network interface). The transmission of the Uu air interface includes uplink transmission and downlink transmission.

Exemplarily, uplink transmission means that the terminal device 110 sends uplink information to the access network device 120 . Wherein, the uplink information may include one or more of uplink data information, uplink control information, and reference signal (reference signal, RS). A channel used to transmit 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, and the uplink data may also be referred to as uplink data information. The PUCCH is used to carry uplink control information (uplink control information, UCI) fed back by the terminal equipment. The UCI may include channel state information (channel state information, CSI), positive acknowledgment (acknowledgment, ACK)/negative acknowledgment (negative acknowledgment, NACK), etc.

Exemplarily, downlink transmission refers to that the access network device 120 sends downlink information to the 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 (channel state information reference signal, CSI-RS) or a phase tracking reference signal (phase tracking reference signal, PTRS). The channel used to transmit downlink information is called a downlink channel, and the downlink channel can be a physical downlink shared channel (physical downlink shared channel, PDSCH) or a physical downlink control channel (physical downlink control channel, PDCCH). The PDCCH is used to carry downlink control information (DCI), the PDSCH is used to carry downlink data, and the downlink data may also be called downlink data information.

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

It 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. The core network device 130 and the access network device 120 may be independent and different physical devices, or the core network device 130 and the access network device 120 may be the same physical device, and the core network device 130 and the access network device are integrated on the physical device. All/part of the logical functions of the network access device 120.

It should be noted that, in the network architecture shown in FIG. 1 , the terminal device 110 may be fixed, or

It is movable and not limited. The network architecture shown in FIG. 1 may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not limited. In the architecture shown in FIG. 1 , the number of terminal devices, access network devices and core network devices is not limited.

The technical solutions in the embodiments of the present application can be applied to various communication systems. For example, the long term evolution (long termevolution, LTE) system, the fifth generation (5th generation, 5G) mobile communication system, and future mobile communication systems.

Some nouns or terms used in this application are explained below, and the nouns or terms are also part of the content of the invention.

1. Terminal equipment

A terminal device may be referred to as a terminal for short, and is also called a user equipment (UE), which is a device with a wireless transceiver function. Terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, drones, balloons and satellites, etc.). The terminal device can be a mobile phone, a tablet computer, a computer with a wireless transceiver function, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal device in industrial control, a wireless terminal device in unmanned driving, a wireless terminal device in telemedicine, etc. Terminal equipment, wireless terminal equipment in smart grid, wireless terminal equipment in transportation security, wireless terminal equipment in smart city, wireless terminal equipment in smart home. Terminal equipment can also be fixed or mobile. The embodiment of the present application does not limit this.

In the embodiment of the present application, the device for realizing the function of the terminal may be a terminal device; it may also be a device capable of supporting the terminal device to realize the function, such as a chip system, and the device may be installed in the terminal device. In the embodiment of the present application, the system-on-a-chip may be composed of chips, or may include chips and other discrete devices. In the technical solutions provided in the embodiments of the present application, the technical solutions provided in the embodiments of the present application will be described by taking the terminal device as an example for realizing the functions of the terminal device.

2. Network equipment

The network device may be an access network device, and the access network device may also be called a radio access network (radio access network, RAN) device, which is a device that provides a wireless communication function for a terminal device. Access network equipment includes, but is not limited to: 5G next-generation base station (generation nodeB, gNB), evolved node B (evolved node B, eNB), baseband unit (baseband unit, BBU), transceiver point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), the base station in the future mobile communication system or the access point in the WiFi system, etc. The access network device may also be a wireless controller, a centralized unit (centralized unit, CU), and/or a distributed unit (distributed unit, DU) in a cloud radio access network (cloud radio access network, CRAN) scenario, or a network The device may be a relay station, a vehicle device, and a network device in a future evolved PLMN network.

A terminal device can communicate with multiple access network devices of different technologies, for example, a terminal device can communicate with an access network device supporting long term evolution (LTE), and can also communicate with an access network device supporting 5G , and can also communicate with access network devices supporting LTE and access network devices supporting 5G at the same time. The embodiment of this application is not limited.

In the embodiment of the present application, the device for realizing the function of the network device may be a network device; it may also be a device capable of supporting the network device to realize the function, such as a chip system, and the device may be installed in the network device. In the technical solution provided by the embodiment of the present application, the technical solution provided by the embodiment of the present application is described by taking the network device as an example for realizing the function of the network device.

Currently, in the fifth generation ( ^5th generation, 5G) mobile communication system, for eMBB scenarios, the communication bandwidth can reach 100M level, which can achieve ultra-high data transmission rate. In addition, in order to serve UEs with different bandwidth capabilities, a concept of a partial bandwidth (bandwidth part, BWP) is also introduced, where the partial bandwidth may be part of the carrier bandwidth of the network device. Based on the capabilities of the UE, the network device can configure one or more uplink BWPs and one or more downlink BWPs for the UE. The uplink BWP is the bandwidth used to transmit uplink information, and the downlink BWP is the bandwidth used to transmit downlink information. Different uplink BWPs The BWP or different downlink BWPs may have different frequency domain positions and/or different bandwidth sizes. In the BWP configured by the network device for the terminal device, the uplink BWP and downlink BWP with the same identifier (ID) can be activated for communication between the network device and the terminal device, and the protocol stipulates that in time division duplexing (time division duplexing, TDD ) system, the center frequencies of the uplink BWP and downlink BWP with the same ID are the same. This regulation makes the center frequency of the uplink active BWP and the center frequency of the downlink active BWP used by the network equipment and the terminal equipment the same.

During the initial access process, the UE can perform time domain synchronization and frequency domain synchronization through the synchronization signal block (SSB) sent by the network device to obtain the master information block (MIB), and then blindly detect the control resource set (control The downlink control information (DCI) in resource set (CORESET) 0 is used to schedule the physical downlink shared channel (physical downlink shared channel, PDSCH) carrying the system information block (system information block, SIB) 1. SSB and CORESET 0 are continuous in the time domain, and the frequency domain bandwidth of CORESET 0 includes the frequency domain bandwidth of SSB in the frequency domain. The terminal device can obtain SIB 1, and obtain relevant configuration information for the initial access process according to SIB 1, including initial downlink BWP configuration information and initial uplink BWP configuration information. The agreement stipulates that the center frequency of the initial downlink BWP is the same as that of the initial uplink BWP. The initial downlink BWP needs to include the bandwidth of SSB and CORESET 0. For example, in the carrier bandwidth of network equipment as shown in Figure 2, SSB and CORESET 0 occupy resources near the center frequency of the carrier. , the initial downlink BWP configured by SIB 1 includes the bandwidth of SSB and CORESET 0, and the center frequency of the downlink BWP is the same as that of the uplink BWP configured by SIB 1, wherein the DCI corresponding to the SIB 1 is carried in the CORESET 0. During the initial access process, the terminal device can use the initial downlink BWP to receive downlink information from the network device, specifically, it can use the bandwidth size occupied by CORESET 0 in the initial downlink BWP to receive downlink information, and the terminal device can use the initial uplink BWP Send the uplink information during the initial access process to the network device. The terminal device can also use the initial BWP when it is in the connected state. For example, the terminal device can use the initial downlink BWP and the initial uplink BWP to initiate a random access process to obtain system information.

Compared with existing terminal equipment, REDCAP UE in the mMTC scenario has narrower communication bandwidth, lower power consumption, and fewer antennas. A REDCAP UE can also be called a low-complexity UE or a lightweight UE. For example, a lightweight (light) UE in a 5G new radio (NR) system can be referred to as an NRL UE.

The maximum bandwidth that REDCAP UE can support is 20MHz, while the maximum bandwidth that UE in eMBB scenario can support is 100MHz. In order not to affect the continuity of frequency domain resources of eMBB UE, the network device needs to configure the BWP of REDCAP UE on the carrier of the network device edge of bandwidth. If the center frequency of downlink BWP and uplink BWP stipulated in the current agreement are the same, and the initial downlink BWP needs to include bandwidth units of SSB and CORESET 0, as shown in Figure 3, the downlink initial BWP, uplink initial BWP, SSB, and CORESET 0 are all will be at the edge of the carrier. SSB and CORESET 0 are important resources for UE to access the network. They are configured on the edge of the carrier and are susceptible to adjacent frequency interference, which affects access performance. In addition, restricting SSB and CORESET 0 to the edge of the carrier bandwidth in order for REDCAP UEs to access the network will affect the flexibility of the overall resource allocation of the network, so that the performance requirements of other terminal equipment may not be met.

The current communication system cannot meet the performance requirements of various application scenarios. This application proposes a resource allocation method and a communication device to solve the problem that the current communication system cannot meet the performance requirements of various application scenarios.

The resource configuration method provided by the embodiment of the present application will be described below with reference to the accompanying drawings.

As shown in FIG. 4 , an embodiment of the present application provides a schematic flowchart of a method for configuring resources. 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 above, and the terminal device may be the terminal device 110 in FIG. 1 above. The method shown in FIG. 4 may include the following operations.

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

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

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

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, in this embodiment of the present application, the network device sends the configuration information of the first downlink BWP to the terminal device and sends the first The sequence of the configuration information of the uplink BWP is not limited. The network device can 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 can first send the configuration information of the first uplink BWP to the terminal device, and then send the configuration information of the first uplink BWP to the terminal device. Below is the configuration information of BWP.

The first downlink BWP and the first uplink BWP may be a group of BWPs that are simultaneously activated and used for communication between the network device and the terminal device. The terminal device receives downlink information from the network device on the resources in the downlink BWP, and sends uplink information to the network device on the resources in the uplink BWP.

Exemplarily, the BWP identifier (identifier, ID) of the first downlink BWP is the same as the BWP ID of the first uplink BWP.

The uplink BWP and downlink BWP with the same BWP ID can be active at the same time for communication between network devices and terminal devices.

The network device can be based on the state of the terminal device (including one or more of the connected state (connected mode or RRC_CONNECT mode), idle state (idle mode or RRC_IDLE mode) and inactive state (inactive mode or RRC_INACTIVE mode)) Configure the uplink BWP and downlink BWP with the same or different center frequencies for the terminal equipment.

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

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

in,

For the uplink BWP and downlink BWP used when the terminal device is in the non-connected state, the network device can configure the uplink BWP and downlink BWP with the same center frequency for the terminal device, or configure the uplink BWP and downlink BWP with different center frequencies for the terminal device.

Exemplarily, the first downlink BWP is the initial downlink BWP, and the first uplink BWP is the initial uplink BWP. Whether the downlink BWP and/or the first uplink BWP are independent initial BWPs, the center frequency of the first downlink BWP is configured to be the same as or different from the center frequency of the first uplink BWP.

The embodiment of the present application proposes that, compared to the BWP configured by the network device for the existing (legacy) terminal device (denoted as the first type of terminal device), the network device can be configured for a specified type of terminal device (denoted as the second type of terminal device) Separate BWP. If the independent BWP is an initial downlink BWP, it may be called an independent initial downlink BWP, and if the independent BWP is an initial uplink BWP, it may be called an independent initial uplink BWP.

Exemplarily, a separate initial BWP (separate initial BWP) is a specific (or exclusive) BWP of the first terminal device, or a BWP configured by the network device only for the first terminal device. For example, the independent initial BWP includes an independent initial uplink BWP and an independent initial downlink 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.

Exemplarily, the independent initial BWP is a BWP different from the BWP currently configured by the terminal device. For example, the non-independent initial BWP is any of the following: BWP shared by multiple types of terminal equipment, BWP configured by MIB, BWP configured by SIB, BWP configured by RRC, BWP not configured for MIB, or during initial access BWP configured or used, BWP configured or used after the initial access procedure, or CORESET 0 (resource).

Exemplarily, the difference between the first type of terminal equipment and the second type of terminal equipment may include one or more of the following a to g:

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

b. The maximum number of antennas supported by the first type of terminal equipment is greater than the maximum number of antennas supported by the second type of terminal equipment, and the maximum number of antennas supported by the terminal equipment may be the maximum number of transmitting antennas and/or the maximum number of receiving antennas , but the application is not limited to this.

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

d. The maximum modulation and demodulation mode supported by the first type of terminal equipment is greater 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 (or called the number of data streams) supported by the first type of terminal equipment is greater than the maximum number of MIMO data layers supported by the second type of terminal equipment.

f. The first type of terminal equipment supports a full-duplex communication mode while the second type of terminal equipment only supports a half-duplex communication mode.

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

Exemplarily, the specified type of terminal equipment may include but not limited to REDCAP UE, and the existing terminal equipment may include but not limited to eMBB UE, defined by the third generation partnership project (third generation partnership project, 3GPP) standard release (release) 15 Terminal equipment, terminal equipment defined by 3GPP standard version 16. For example, a REDCAP terminal device defined in Release 18 of the 3GPP standard may be a specified type of terminal device, and for this terminal device, a REDCAP terminal device defined in 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 equipment in specific implementation, or the type of terminal equipment using the non-independent BWP may not be limited in specific implementation. For example, both the terminal device of the first type and the terminal device of the second type may be configured or use a non-independent BWP.

Exemplarily, the configuration information of the BWP may include indication information, and the indication information is used to indicate that the BWP is an independent BWP or a non-independent BWP.

In an 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, it indicates that the BWP is an independent BWP. When the indication field indicates the second state value, it indicates that the BWP is a dependent BWP.

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

In another example, the network device may indicate whether the BWP is an independent or non-independent BWP according to whether the indication information is included in the configuration information of the BWP.

For example, the indication information indicates that the BWP is an independent BWP, and when the configuration information of the BWP includes the indication information, the terminal device may determine that the BWP is an independent BWP. When the configuration information of the BWP does not include the indication information, the terminal device may determine that the BWP is a non-independent BWP. Or the indication information may indicate that the BWP is a non-BWP. This application is not limited to this.

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

Case 1, 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 to say, the first downlink BWP may be an independent initial downlink BWP configured by the network device for the second type of terminal device and used by the terminal device in a non-connected state. The first uplink BWP may be an independent initial uplink BWP configured by the network device for the second type of terminal device and used by the terminal device in a non-connected state. 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, which can avoid readjusting the radio frequency point when the terminal device is in a non-connected state when switching between uplink and downlink, and can Reduce power consumption of terminal equipment.

For example, the first downlink BWP configured by the network device for the UE 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 used as the first initial BWP of the terminal device. After receiving the configuration information and determining the first downlink BWP and the first uplink BWP, the UE can use the first downlink BWP and the first uplink BWP to perform a random access procedure when in the unconnected state, thereby entering the connection state. Specifically, the terminal device uses the first uplink BWP to send uplink information in the random access process to the network device, and uses the first downlink BWP to receive downlink information in the random access process from the network device. Since the first uplink The central frequency of the BWP and the first downlink BWP are the same, and the terminal equipment does not need to re-adjust the frequency when performing mutual switching between the uplink and the downlink during the random access process, which can reduce the power consumption of the terminal equipment.

Exemplarily, 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 (radio resource control, RRC) message.

For example, when the terminal device is in the disconnected state, the UE performs time-frequency synchronization through the SSB sent by the network device, and blindly detects the DCI in CORESET 0, and obtains SIB1 according to the DCI, and the SIB1 is configured with an independent initial downlink BWP (that is, the first downlink BWP) and an independent initial uplink BWP (namely the first uplink BWP). Then the terminal device can use the independent initial downlink BWP (ie, the first downlink BWP) and the independent initial uplink BWP (ie, the first uplink BWP) to perform a random access procedure.

Exemplarily, the CORESET 0 may not belong to the independent initial downlink BWP.

For example, as shown in FIG. 5 , the independent initial downlink BWP (that is, the first downlink BWP) and the independent initial uplink BWP (that is, the first uplink BWP) may be configured at the edge of the carrier bandwidth of the network device. CORESET 0 can be configured near the center frequency of the carrier bandwidth. That is to say, the independent initial downlink BWP frequency domain resources may not include SSB and CORESET0 resources. The resources may be frequency domain resources, bandwidth, carrier bandwidth, BWP bandwidth, time domain resources, or time-frequency domain resources. This enables SSB and CORESET 0 to not be at the edge of the carrier bandwidth along with the independent initial downlink BWP, which can ensure the performance requirements of cell search or time-frequency synchronization of other terminal devices in the network. In addition, the initial BWP of the terminal device can be configured at the edge of the carrier, so that the terminal device can use the initial BWP of the carrier edge for random access without affecting the continuity of frequency domain resources of other large-bandwidth UEs, and avoiding the problem of existing UEs caused by the terminal device entering the network. congestion.

The BWP configured at the edge of the carrier bandwidth may be a BWP configured within a frequency domain range whose frequency domain distance from the edge frequency of the carrier bandwidth is not greater than a preset threshold. The embodiment of the present application provides the following examples. It should be understood that the present application is not limited thereto. In specific implementation, the BWP configured at the edge of the carrier bandwidth may be defined in combination with actual conditions.

For example, if the carrier bandwidth of the network device is 100MHz, then the BWP containing the frequency domain resources belonging to the 0-20MHz frequency band in the carrier bandwidth can be called a BWP configured on the edge of the carrier bandwidth, and/or the frequency domain resources included belong to the carrier bandwidth The BWP in the 80MHz to 100MHz frequency band can be called the BWP configured at the edge of the carrier bandwidth.

For another example, a network device configures a BWP in units of resource blocks (resource blocks, RBs). When the subcarrier space (subcarrier space, SCS) is 15 kHz, and the maximum sequence number of RBs contained in a BWP is less than or equal to 106, it can be called the BWP is the BWP at the edge of the carrier bandwidth; and/or, if the minimum sequence number of the RB included in a BWP is greater than or equal to (N _RBmax -106), then the BWP can be called the BWP at the edge of the carrier bandwidth, where N _RBmax is the carrier bandwidth containing The maximum sequence number of the RB.

For another example, the network device configures BWP in units of RBs. When the SCS is 30kHz, and the maximum sequence number of RBs included in a BWP is less than or equal to 51, the BWP can be called a BWP at the edge of the carrier bandwidth; and/or, a BWP includes If the minimum sequence number of the RB is greater than or equal to (N _RBmax -51), the BWP can be called the BWP at the edge of the carrier bandwidth, where N _RBmax is the maximum sequence number of the RBs included in the carrier bandwidth.

For example, it may be stipulated that if the network device configures the terminal device with an independent initial downlink BWP and an independent initial uplink BWP used when the terminal device is in a non-connected state, then the independent initial downlink BWP and the independent initial uplink BWP have the same center frequency.

The terminal device does not expect that the center frequencies of the independent initial downlink BWP and the independent initial uplink BWP configured by the network device and used when the terminal device is in a non-connected state are different.

Exemplarily, if the network device configures an independent initial downlink BWP and an independent initial uplink BWP for the terminal device, the independent initial downlink BWP and the independent initial uplink BWP have the same center frequency.

The terminal device does not expect that the center frequencies of the independent initial downlink BWP configured by the network device and the independent initial uplink BWP are different.

In the second case, the first downlink BWP is a non-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 or different.

The network device can configure an independent initial uplink BWP for the second type of terminal equipment that is only in the unconnected state, and the second type of terminal equipment can use the non-independent initial downlink BWP and the independent initial uplink BWP to perform random access in the unconnected state. to access the network.

In an example, the center frequencies of the first downlink BWP and the first uplink BWP are different. For example, if the network device configures a non-independent initial downlink BWP in SIB1, and SIB1 also configures an independent initial uplink BWP at the edge of the carrier bandwidth for the UE, the terminal device can use the non-independent initial downlink BWP and the independent initial uplink BWP to execute In a random access process, the downlink information in the random access process is received on the non-independent initial downlink BWP. Specifically, the downlink information during the random access process may be received within the CORESET 0 bandwidth, and the uplink information during the random access process may be sent to the network device on the independent initial uplink BWP at the edge of the carrier bandwidth. Wherein, the BWP ID of the non-independent initial downlink BWP is the same as the BWP ID of the independent initial uplink BWP, for example, both are 0. But the present application is not limited thereto. Configuring the independent initial uplink BWP for the terminal equipment on the network device can realize the configuration of the independent initial uplink BWP of the terminal equipment at the edge of the carrier bandwidth, which can avoid affecting the continuity of uplink frequency domain resources of other large-bandwidth UEs, and can avoid large Uplink data congestion of bandwidth UEs. The flexibility of configuring BWP on the network is increased, so that the network can meet the communication requirements of various application scenarios.

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

In case three, 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.

In an example, the network device may configure the non-independent initial uplink BWP at the edge of the carrier. When the non-independent initial downlink BWP configured by the network device is configured near the center of the carrier, the network device may also configure the independent initial downlink BWP so that the independent initial downlink BWP ( That is, the first downlink BWP) and the non-independent initial uplink BWP (that is, the first uplink BWP) have the same center frequency, so that the second type of terminal equipment can use the independent initial downlink BWP and the The non-independent initial uplink BWP communicates with network devices.

For example, as shown in Figure 6, the network device can configure a non-independent initial downlink BWP near the center frequency point of the carrier through the SIB, and a non-independent initial uplink BWP at the edge of the carrier corresponding to the non-independent initial downlink BWP (that is, the first uplink BWP ), the network device may also configure an independent initial downlink BWP (that is, the first downlink BWP) corresponding to the non-independent initial uplink BWP. After receiving the SIB, the first type of terminal equipment in the non-connected state can use the non-independent initial downlink BWP and non-independent initial uplink BWP configured by the SIB to perform a random access process according to the SIB, so as to establish a communication connection with the network and enter the connection state. After receiving the SIB, the second type of terminal equipment can use the independent initial downlink BWP and non-independent initial uplink BWP configured by the SIB to perform a random access procedure according to the SIB, so as to establish a communication connection with the network and enter the connection state. For example, the network device only configures the non-independent initial uplink BWP to be used by various types of terminal devices in the disconnected state according to resource utilization conditions and the like. However, the present application is not limited thereto, and the network device may also adopt the configuration mode of the third case in other cases.

Situation 4, the first downlink BWP is a non-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.

In an example, the first downlink BWP is the initial downlink BWP configured in the MIB, that is, CORESET 0. The first uplink BWP is the initial uplink BWP configured by the SIB. 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 that 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 a non-independent initial downlink BWP and a non-independent initial uplink BWP, which helps reduce common signaling and common channel overhead when the network load is light.

In the above method, the network device can configure independent initial downlink BWP or non-independent initial downlink BWP, independent initial uplink BWP or non-independent initial The center frequencies of the uplink BWP and the initial downlink BWP can be the same or different, which increases the flexibility of network configuration BWP and enables the network to meet the communication requirements of various application scenarios.

If the initial downlink BWP used by the terminal device in the disconnected state is different from the center frequency point of the initial uplink BWP, the network device can reconfigure one of the BWPs for the terminal device through the configuration information so that the center frequency points of the initial downlink BWP and the initial uplink BWP, Alternatively, the network device may reconfigure two initial downlink BWPs and initial uplink BWPs with the same center frequency for the terminal device through the configuration information.

In an example, if the center frequency of the first downlink BWP used by the terminal device in the disconnected state is different from that of the first uplink BWP, the network device may send configuration information of the second downlink BWP to the terminal device, and the center frequency of the second downlink BWP The frequency 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 the initial downlink BWP, the first uplink BWP is the 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, the configuration information indicating 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 downlink BWP and the first uplink BWP may be initial BWPs used when the terminal device is in a connected state.

The terminal device does not expect that the center frequency of the second downlink BWP is different from that of the first uplink BWP. That is, the terminal device expects that the center frequency of the second downlink BWP is the same as that of the first uplink BWP.

For example, the network device will not send a configuration message to the terminal device to configure the center frequency of the second downlink BWP used by a terminal device in the connected state to be different from the center frequency of the first downlink BWP, and the BWPID of the second downlink BWP is the same as that of the first downlink BWP. The BWP ID of the first uplink BWP is the same.

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

In another example, if the center frequency of the first downlink BWP used by the terminal device in the disconnected state is different from that of the first uplink BWP, the network device may send configuration information of the second uplink BWP to the terminal device, and the second uplink BWP The center frequency 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 the initial downlink BWP, the first uplink BWP is the 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 uplink BWP to the terminal device, the configuration information indicating that 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 0. After receiving the configuration information, the terminal device may determine that the initial uplink BWP is updated from the first uplink BWP to the second uplink BWP. The first downlink BWP and the second uplink BWP may be initial BWPs used when the terminal device is in a connected state.

The terminal device does not expect that the center frequency of the second uplink BWP is different from that of the first downlink BWP. That is, the terminal device expects that the center frequency of the second uplink BWP is the same as that of the first downlink BWP.

In another example, if the center frequency 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 (referred to as the first BWP ID, for example, the first BWPID is 0), the network device can send the configuration information of the second downlink BWP and the configuration information of the second uplink BWP to the terminal device, the BWP ID of the second downlink BWP and the BWP ID of the second uplink BWP Both are 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 whose ID is the first BWP ID with the second downlink BWP, and replaces the first downlink BWP whose ID is the first BWP ID An uplink BWP is replaced by a second uplink BWP, and the second downlink BWP and the second uplink BWP may be initial BWPs used when the terminal device is in a connected state.

As an example without 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 above-mentioned second downlink BWP and second uplink BWP may be BWPs used when the terminal device is in a connected state. However, the present application does not limit the state of the terminal device when it receives the configuration information of the second downlink BWP and the configuration information of the second uplink BWP.

The terminal device may receive configuration information of the second downlink BWP and/or configuration information of the second uplink BWP in a non-connected state. For example, the network device can pass message 4 (message 4, Msg.4), message 5 (message 5, Msg.5), DCI of scheduling message 4, DCI of scheduling message 5, and The DCI or message B (messageB, Msg.B) configures the second downlink BWP and/or the second uplink BWP for the terminal device. After receiving the message 4 or message B, the terminal device can enter the connected state from the unconnected state.

The terminal device may also receive the configuration information of the second downlink BWP and/or the configuration information of the second uplink BWP when it is in the connected state. For example, after entering the connected state, the terminal device continues to use the first downlink BWP used when the terminal device is in the unconnected state to receive downlink information from the network device 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. The terminal device switches from the first downlink BWP to the second downlink BWP at time one according to the received configuration information. For another example, after the terminal device enters the connected state and before receiving the configuration information of the second uplink BWP, it continues to use the first uplink BWP used when the terminal device is in the unconnected state to send uplink information to the network device. 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. The terminal device switches from the first uplink BWP to the second uplink BWP at time 2 according to the received configuration information.

Exemplarily, time one may be predetermined. For example, time one 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. Alternatively, time one is the start time or end time of the Yth time unit after the terminal device receives the configuration information of the second downlink BWP. Among them, Y is a positive integer.

Exemplarily, the second moment may be predetermined. For example, time two 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. Alternatively, time two is the start time or end time of the Nth time unit after the terminal device receives the configuration information of the second downlink BWP, where N is a positive integer.

As an example without limitation, the foregoing time unit may be one or more items of a frame, a radio frame, a subframe, a time slot, or a transmission period.

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

For example, time two can be pre-specified. For example, time two is the X time unit after receiving the configuration information of the second downlink BWP or the Yth time unit after receiving the configuration information of the second downlink BWP. For example, the time unit is frame, radio frame, subframe, time 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 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 stipulated that the central frequency of the uplink BWP and the downlink BWP configured by the network device for the terminal device and used when the terminal device is in the connected state are the same. This enables connected terminal devices to communicate with network devices without readjusting the radio frequency when switching between uplink and downlink, which can reduce the power consumption of terminal devices and avoid the increase in communication delay caused by frequent switching .

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

Mode 1, the first downlink BWP is a separate (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 the center frequency of the first uplink BWP, which can prevent the terminal device from readjusting the radio frequency point when switching between uplink and downlink, and can reduce power consumption of the terminal device.

Exemplarily, for a low-capability terminal device of the second type, the network device can configure the first downlink BWP and the first uplink BWP at the edge of the carrier bandwidth, which can prevent the narrow bandwidth of the low-capability terminal device from affecting other large Frequency Domain Resource Continuity for Bandwidth Terminal Devices.

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

The second type of terminal equipment does not expect the central frequency of a set of initial downlink BWPs configured by the network equipment and used when the terminal equipment is in the connected state to be different from that of the initial uplink BWP.

Mode 2, the first downlink BWP is a non-independent initial downlink BWP, and the first uplink BWP is a non-independent initial uplink BWP.

That is to say, the first downlink BWP can be a non-independent initial downlink BWP configured by the network device and used when multiple types of terminal devices are in the connected state, and the first uplink BWP can be the The non-independent initial uplink BWP used in the 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 configured by the network device for the terminal device and used in the connected state is the same as the center frequency of the initial uplink BWP.

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

That is to say, in this optional implementation, regardless of whether the type of the terminal device is the first type or the second type, the center frequency of the downlink initial BWP configured by the network device for the terminal device and used when the terminal device is in the connected state The center frequency of the uplink initial BWP needs to be consistent, that is, the center frequency is the same.

Manner 3, the first downlink BWP is a non-independent initial downlink BWP, and the first uplink BWP is an independent initial uplink BWP.

Mode 4, the first downlink BWP is an independent initial downlink BWP, and the first uplink BWP is a non-independent initial uplink BWP.

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

Exemplarily, the first downlink BWP is the initial downlink BWP, and the first uplink BWP is the initial uplink BWP.

For example, the network device notifies the terminal device that the first downlink BWP is the initial downlink BWP through the configuration information of the first downlink BWP, and notifies the terminal device that the first uplink BWP is the initial uplink BWP through the configuration information of the second uplink BWP. The terminal device can either The first downlink BWP and the first uplink BWP are used in the connected state, and the first downlink BWP and the first uplink BWP may also be used in the disconnected state.

For example, before S401, the terminal device may report to the network device that the terminal device supports or does not support the difference between the center frequency of the uplink BWP and the center frequency of the downlink BWP.

In an example, the terminal device may send capability information to the network device, where the capability information is used to indicate that the terminal device supports or does not support the difference between the center frequency of the uplink BWP and the center frequency of the downlink BWP.

Correspondingly, the network device receives the capability information from the terminal device, and if the capability information indicates that the center frequency of the terminal device supporting the uplink BWP is different from the center frequency of the downlink BWP, the network device configures the first downlink BWP and the second downlink BWP for the terminal device. The center frequencies of an uplink BWP can be the same or different. If the capability information indicates that the terminal device does not support the center frequency of the uplink BWP and the center frequency of the downlink BWP being different, 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 center frequency of the first downlink BWP supported by the terminal device is different from that of the first uplink BWP, the terminal device reports first information to the network device, and the first information is used to indicate that the terminal device supports the center frequency of the uplink BWP. The frequency 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, the terminal device does not report the first information to the network device.

After the network device obtains the first information from the terminal device, the network device can 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 network device configures the first downlink BWP and the first uplink BWP for the terminal device. The center frequencies of the BWPs can be the same or different. If the network device does not receive the first information from the terminal device, the network device believes that the terminal device does not support the center frequency of the uplink BWP and the center frequency of the downlink BWP are different, and the network device configures the first downlink with the same center frequency for the terminal device BWP and first upstream BWP. If the central frequency point of the uplink BWP is different from that of the downlink BWP, the terminal device needs to be equipped with two phase lock loops (phase lock loop, PLL) for clock synchronization of uplink information and clock synchronization of downlink information respectively. Therefore, whether the terminal device supports the center frequency point of the uplink BWP is different from the center frequency point of the downlink BWP and whether the terminal device is configured with two PLLs. If the terminal device is configured with only one PLL, the terminal device only supports the same central frequency point of the uplink BWP and the downlink BWP, and the clock synchronization of the uplink information and the clock synchronization of the downlink information share the one PLL configured by the terminal device. However, the present application is not limited thereto, and whether the terminal device supports a center frequency point of the uplink BWP being different from that 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 downlink BWP according to the The configuration information determines the first uplink BWP. It should be noted that the embodiment of the present application does not limit the order in which the terminal device determines the first downlink BWP and the first uplink BWP. The terminal device may determine the first downlink BWP and the first uplink BWP after receiving the two pieces of configuration information in the same message. It may also be that the two pieces of configuration information are successively received in different messages, and the corresponding BWP is determined based on the received configuration information.

If the first downlink BWP and the first uplink BWP are the BWPs used by the terminal device in the connected state, then the terminal device can use the first downlink BWP to receive downlink information from the network device when it is in the connected state, and use The first uplink BWP sends uplink information to the network device.

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

According to the solution provided by the embodiment of this application, the network device can configure uplink BWPs with the same or different center frequencies for the terminal device based on the state of the terminal device (including one or more of the connected state, the idle state, and the inactive state) and downlink BWP. It can realize low-capability terminal equipment to access the network, and use the system bandwidth resources of the network equipment to communicate with the network equipment. The flexibility of configuring BWP on the network is increased, so that the network can meet the communication requirements of various application scenarios.

In an implementation manner, the center frequencies of the initial downlink BWP and the initial uplink BWP used when the terminal device is in the unconnected state may be different. The center frequency 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 non-connected 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 when the terminal device is in the unconnected state are different or the same. When the terminal device is in the connected state, the center frequency of the initial downlink BWP and the initial uplink BWP used by the terminal device to communicate with the network device are the same. When the terminal device is in the connected state, the terminal device does not expect that the center frequencies of the initial downlink BWP and the initial uplink BWP are different.

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

For another example, when the terminal device is in a non-connected state, the center frequency (center frequency) 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 frequency of the initial downlink BWP and the initial uplink BWP used by the terminal device to communicate with the network device are the same. After the terminal device leaves the unconnected state or enters the connected state, the terminal device determines the initial BWP used when communicating 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 the initial uplink BWP and/or the initial downlink 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 for the terminal device in the connected state is configured for the SIB. Alternatively, the initial downlink BWP when the terminal device is in the unconnected state is configured by MIB, and the initial downlink BWP when the terminal device is in the connected state is configured by the RRC message. Alternatively, the initial uplink BWP when the terminal device is in the unconnected state is configured by the SIB, and the initial uplink BWP when the terminal device is in the connected state is configured by the RRC message.

In one possible implementation:

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

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 first uplink BWP.

For example, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in the connected state or after initial access, and the center frequency of the first downlink BWP and the first uplink BWP The center frequency of the BWP is the same. And/or, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state or for initial access, and the center frequency of the first downlink BWP and the first The central frequencies of an uplink BWP are the same or different, and the disconnected 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 the center frequency of the first downlink BWP is the same as or different from the center frequency of the first uplink BWP. And/or, 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 .

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 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, and the first uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP, so The center frequency of the first downlink BWP is the same as or different from the center frequency of the first uplink BWP. The first resource includes: CORESET 0 and/or SSB bandwidth.

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

In another possible implementation:

The network device determines configuration information of the first downlink partial bandwidth BWP, and determines configuration information of the first uplink BWP.

The network device sends 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 the terminal device in the connected state or after initial access, and the center frequency of the first downlink BWP and the first uplink BWP The center frequency is the same. And/or, the first downlink BWP and the first uplink BWP are BWPs used by the terminal device in a non-connected state or for initial access, and the center frequency of the first downlink BWP and the first The central frequencies of an uplink BWP are the same or different, and the disconnected 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 the center frequency of the first downlink BWP is the same as or different from the center frequency of the first uplink BWP. And/or, 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 .

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 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, and the first uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP, so The center frequency of the first downlink BWP is the same as or different from the center frequency of the first uplink BWP. The first resource includes: CORESET 0 and/or SSB bandwidth.

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

Another embodiment of the present invention is explained below.

Not only can the center frequency of the first downlink BWP and the center frequency of the first uplink BWP be the same according to the RRC connection state of the terminal device, but also the center frequency of the first downlink BWP can be specified according to whether the terminal device is in the initial access stage Whether the frequency is the same as the center frequency of the first uplink BWP. For example, after the terminal device is in the 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. That is, for a terminal device in a connected state or after initial access, 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. In this way, the terminal device does not need to tune the center frequency during downlink reception and uplink transmission, avoiding the introduction of frequency tuning time, reducing the power consumption of the terminal device and the complexity of information reception/transmission, and improving resource utilization efficiency.

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 include any or all resources in the first resources. The first uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP. The center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP. The first resource includes at least one of CORESET 0 and SSB bandwidth. For example, when the terminal device does not expect that the bandwidth of the first initial downlink BWP does not 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 because at least one resource unit in the independent initial downlink BWP is not included in the first resource. For example, the bandwidth of the independent initial downlink BWP is greater than the bandwidth of the first resource. For example, the independent initial downlink BWP includes the first resource. For example, the resource unit is a resource block (resources block, RB), a resource element (resources element, RE) or a control channel element (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 that receives {one or more of random access response, paging message, and system information} (for example, an independent initial downlink BWP or a non-independent initial downlink BWP or an initial downlink BWP configured by MIB ), and/or the first downlink BWP does not contain any or all of the first resources. The first uplink BWP is an uplink BWP (such as an independent initial uplink BWP or a non-independent initial uplink BWP) that sends {one or more of the PUCCH feedback of the physical random access channel, message 3, and 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 includes at least one of CORESET 0 and SSB bandwidth.

When the terminal device is in a non-connected state or in an initial access process, the center frequency of the first downlink BWP of the terminal device may be the same as or different from the center frequency of the first uplink BWP. That is, for a terminal device in a non-connected state or in an initial access process, 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.

When the terminal device is in the non-connected state or in the process of initial access, its communication with the network device is infrequent. Even if the center frequency of the first downlink BWP is different from the center frequency of the first uplink BWP, the terminal device receives and sends data in the downlink. When the center frequency tuning is not very frequent, it will not have a great impact on the power consumption and information processing (receiving or sending) complexity of the terminal equipment, but it improves the center frequency of the base station to the first downlink BWP and the first The central frequency configuration flexibility of the uplink BWP helps to reuse existing downlink resources (such as CORESET 0 or SSB), maintain the continuity of uplink resources, and reduce the impact on data transmission of UEs of previous versions. Moreover, for a terminal device in a non-connected state or in the initial access process, its downlink reception and uplink transmission are usually serially processed. When the center frequency of the first downlink BWP is different from the center frequency of the first uplink BWP, the terminal device The interval time between downlink reception and uplink transmission is used for frequency tuning, which also avoids the reduction of the utilization efficiency of system resources. Of course, when the terminal device is in the non-connected state or in the initial access process, the network device can 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 communication between the uplink and downlink of the low-complexity terminal device. The frequency tuning is lowered.

Specifically, the terminal device is in a non-connected state or in an initial access process. The first downlink BWP is an independent initial downlink BWP, and the first downlink BWP includes 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 uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP. The center frequency of the first downlink BWP and the center frequency of the first uplink BWP may be the same or different. Therefore, the network device has greater flexibility to configure the center frequency of the first downlink BWP and the center frequency of the first uplink BWP. For example, when the network device allows low-complexity terminal devices to reuse existing downlink resources (such as coreset 0 or SSB), and the network device keeps uplink resources as continuous as possible to reduce the impact on data transmission of UEs of previous versions, The network device may configure that the center frequency of the first downlink BWP is different from the center frequency of the first uplink BWP. For example, in order to reduce the frequency of uplink and downlink frequency tuning of low-complexity terminal devices, 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 in an initial access process. The first downlink BWP is a downlink BWP that receives {one or more of random access response, paging message, and system information} (for example, an independent initial downlink BWP or a non-independent initial downlink BWP or an initial downlink BWP configured by MIB ), and/or the first downlink BWP includes all resources in the first resource. The first uplink BWP is an uplink BWP (such as an independent initial uplink BWP or a non-independent initial uplink BWP) that sends {one or more of the PUCCH feedback of the physical random access channel, message 3, and 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 includes at least one of CORESET 0 and SSB bandwidth.

To sum up, the center frequency of the first downlink BWP and the center frequency of the first uplink BWP of the terminal device meet the requirements of one or more scenarios in 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 meet the requirements of one or more scenarios in the following scenarios.

Provisions for Scenario 1:

After the terminal device is in the connection state or initially accesses, 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 the connected state or initially accessed, 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 downlink BWP is an independent initial downlink BWP. For example, the first uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP.

Provisions for Scenario 2:

The terminal device is in a non-connected state or in the initial access process, the first downlink BWP is an independent initial downlink BWP, and the first downlink BWP does not contain the entire first resource, and the first uplink BWP is an independent initial uplink BWP or a non-independent initial For the uplink BWP, the center frequency of the first downlink BWP of the terminal device 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.

Provisions for Scenario 3:

The terminal device is in the disconnected state or the initial access process, the first downlink BWP is an independent initial downlink BWP, and the first downlink BWP includes the entire first resource, and the first uplink BWP is an independent initial uplink BWP or a non-independent initial uplink BWP , the center frequency of the first downlink BWP of the terminal device is the same as or different from 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 or different from the center frequency of the first uplink BWP.

The first resource includes: bandwidth of CORESET 0 and/or SSB.

Another embodiment of the present invention is explained 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, CORESET 0, 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 the first downlink BWP to include one of cell-defined SSB, non-cell-defined SSB, CORESET 0, and system information block or more.

Because the terminal device does not expect the first downlink BWP to include one or more of the cell-defined SSB, non-cell-defined SSB, CORESET 0, and system information block, the first downlink BWP may not include the cell-defined SSB, One or more of SSB, CORESET 0, and system information block defined by the non-cell, so as to save resources in the first downlink BWP. The terminal device can tune to other resources to receive one or more of the cell-defined SSB, non-cell-defined SSB, CORESET0, and system information block, thereby saving system overhead. It should be noted that the exclusion of the present invention can be interpreted as not supporting transmission. Optionally, in order to reduce restrictions on the network device, the first downlink BWP configured by the network device may not include one or more of cell-defined SSB, non-cell-defined SSB, CORESET 0, system information block, or It may include one or more of cell-defined SSB, non-cell-defined SSB, CORESET 0, and system information block.

The first downlink BWP is the 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 SSB, non-cell-defined SSB, and channel state information reference signal CSI-RS . Alternatively, the first downlink BWP is the downlink BWP (initial or non-initial) after the initial access process, and the terminal device expects the first downlink BWP to include cell-defined SSB, non-cell-defined SSB, channel state information reference signal CSI- One or more of RS.

For the active BWP configured by 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 cell-defined SSB, non-cell-defined SSB, CORESET 0, One or more of the system information blocks, the terminal device does not need to tune to other resources to receive one or more of the cell-defined SSB, non-cell-defined SSB, CORESET 0, and system information blocks, thereby avoiding Frequent frequency tuning of the terminal equipment saves power consumption of the terminal equipment. Optionally, in order to reduce restrictions 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, CORESET 0, system information block, or One or more of cell-defined SSB, non-cell-defined SSB, CORESET 0, and system information block are not included.

Another embodiment of the present invention is explained below.

The first downlink BWP and the first uplink BWP are initial BWPs 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. 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 downlink BWP is an independent initial downlink BWP, and the first uplink BWP is an independent initial uplink BWP.

For example, the first downlink BWP is an independent initial downlink BWP, and the first uplink BWP is a dependent initial uplink BWP.

For example, the first downlink BWP is a non-independent initial downlink BWP, and the first uplink BWP is an independent initial uplink BWP.

For example, the first downlink BWP is a non-independent initial downlink BWP, and the first uplink BWP is a non-independent initial uplink BWP.

In the manner described above, the network device may configure the center frequency of the uplink BWP and downlink BWP for the terminal device to be the same or different based on the use of the BWP of the terminal device (including one or more items of initial BWP and non-initial BWP). It can realize low-capability terminal equipment to access the network, and use the system bandwidth resources of the network equipment to communicate with the network equipment. The flexibility of configuring BWP on network devices is increased, so that the system can meet the communication requirements of various application scenarios.

Herein, the center frequency of the first downlink BWP is the same as or different from the center frequency of the first uplink BWP, 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 network devices. Due to the initial access process or the non-connected state, the transmission delay requirements of the terminal equipment are relatively low, and the frequency tuning caused by the misalignment of the uplink and downlink center frequency points has little impact. The center frequency of the first downlink BWP is the same as the center frequency of the first uplink BWP, because the terminal device does not expect the center frequency of the first downlink BWP to be different from the center frequency of the first uplink BWP, or because the network device cannot set the first downlink The center frequency of the row BWP is configured to be different from the center frequency of the first uplink BWP. This limits the flexibility of network equipment resource allocation, but avoids frequency tuning between uplink and downlink of terminal equipment, avoids interruption of terminal equipment transmission, and shortens transmission delay.

In this way, when the terminal device is in the non-connected state, the network device does not obtain sufficient information about the terminal device, and the center frequency of the initial downlink BWP and the initial uplink BWP used when the terminal device is in the non-connected state are allowed to be different. The device can access the network as much as possible by adopting multiple methods such as the same or different uplink and downlink center frequencies. However, after the terminal device accesses the network and is in the connected state, it is necessary that the center frequency of the initial downlink BWP used when the terminal device is in the connected state is the same as that of the initial uplink BWP. The terminal equipment in the connected state does not need to readjust the radio frequency point when switching between uplink and downlink during the communication process, which can reduce the power consumption of the terminal equipment and avoid the increase of communication delay caused by frequent switching.

In the above embodiments provided in the present application, the methods provided in the embodiments of the present application are introduced from the perspectives of the network device, the terminal device, and the interaction between the network device and the terminal device. In order to realize the various functions in the method provided by the above-mentioned embodiments of the present application, the network device and the terminal device may include a hardware structure and/or a software module, and realize the above-mentioned functions in the form of a hardware structure, a software module, or a hardware structure plus a software module . Whether one of the above-mentioned functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution. Wherein, the steps performed by the network device may also be respectively implemented by different communication devices. For example: the first device is used to determine the configuration information of the first downlink BWP and the configuration information of the first uplink BWP, and the second device is used to send the configuration information of the first downlink BWP and the first uplink BWP to the terminal equipment. The configuration information of the BWP, that is to say, the first device and the second device jointly complete the steps performed by the network device in the embodiment of the present application, and the specific division method is not limited in the present application. When the network architecture includes one or more DUs, one or more CUs, and one or more radio frequency units (RUs), the above steps performed by the network device may be respectively implemented by the DUs, CUs, and RUs. In order to realize the various functions in the method provided by the above-mentioned embodiments of the present application, the terminal device and the network device may include a hardware structure and/or a software module, and realize the above-mentioned functions in the form of a hardware structure, a software module, or a hardware structure plus a software module . Whether one of the above-mentioned functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

FIG. 7 is a schematic structural diagram of a possible communication device provided by an embodiment of the present application. The communication device can realize the functions of the terminal device or the network device in the foregoing method embodiments, and therefore can also realize the beneficial effects of the foregoing method embodiments. In this embodiment of the application, the communication device may be the terminal device 110 as shown in Figure 1, or the access network device 120 as shown in Figure 1, or a Modules (such as chips).

When the communication device 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 the first downlink BWP and configuration information of the first uplink BWP from the network device. The processing module 702 is configured to determine the first downlink BWP according to the configuration information of the first downlink BWP, and determine the first uplink BWP according to the configuration information of the first uplink BWP, and is used to call the transceiver module 701 to send a signal to the network device or Receive signals from network devices.

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

For a more detailed description of the foregoing transceiver module 701 and processing module 702, reference may be made to relevant descriptions in the foregoing method embodiments, and no further description is given here.

FIG. 8 shows a schematic structural diagram of a terminal device provided by an embodiment of the present application.

The terminal device 800 shown in FIG. 8 is applicable to the system shown in FIG. 1 . For ease of description, FIG. 8 only shows main components of a terminal device 800 . As shown in FIG. 8 , a terminal device 800 includes a processor, a memory, a control circuit, an antenna, and an input and output device. The processor is mainly used to process communication protocols and communication data, control the entire terminal device 800, execute software programs, and process data of the software programs. Memory is primarily used to store software programs and data. The control circuit is mainly used for conversion of baseband signal and radio frequency signal and processing of radio frequency signal. Antennas are mainly used to send and receive 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 to receive data input by users and output data to users.

Taking the terminal device 800 as a mobile phone as an example, when the terminal device 800 is turned on, the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the control circuit, and the control circuit performs radio frequency processing on the baseband signal, and sends the radio frequency signal through the antenna in the form of electromagnetic waves. When data is sent to the terminal device 800, the control circuit receives the 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 can understand that, for ease of illustration, FIG. 8 only shows a memory and a processor. In some embodiments, the terminal device 800 may include multiple processors and memories. A storage may also be called a storage medium or a storage device, which is not limited in this embodiment of the present invention.

As an optional implementation, the processor may include a baseband processor and a central processing unit, the baseband processor is mainly used to process communication protocols and communication data, and the central processor is mainly used to control the entire terminal device 800, Executing the software program, processing the data of the software program. The processor in FIG. 8 integrates the functions of the baseband processor and the central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit can also be independent processors, interconnected through technologies such as a bus. The terminal device 800 may include multiple baseband processors to adapt to different network standards, the terminal device 800 may include multiple central processors to enhance its processing capability, and various components of the terminal device 800 may be connected through various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit may also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and communication data can be built in the processor, or can 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 an example, the antenna and the control circuit with the transceiver function may be regarded as the transceiver unit 810 of the terminal device 800 , and the processor with the processing function may be regarded as the processing unit 820 of the terminal device 800 . As shown in FIG. 8 , a terminal device 800 includes a transceiver unit 810 and a processing unit 820 . The transceiver unit may also be referred to as a transceiver, a transceiver, a transceiver device, and the like. Optionally, the device in the transceiver unit 810 for realizing the receiving function may be regarded as a receiving unit, and the device in the transceiver unit 810 for realizing the sending function may be regarded as a sending unit, that is, the transceiver unit 810 includes a receiving unit and a sending unit. Exemplarily, the receiving unit may also be called a receiver, receiver, receiving circuit, etc., and the sending unit may be called a transmitter, transmitter, or transmitting circuit, etc.

The embodiment of the present application also provides a network device, which can be used in the foregoing embodiments. The network device includes means, units and/or circuits for realizing the functions of the network device described in the embodiment shown in FIG. 4 . For example, the network device includes a transceiver module, configured to support the terminal device to implement the transceiver function, and a processing module, configured to support the network device to process signals. It can be understood that the first network device and the second network device are relative to one or some UEs, and relative to some other UEs, the roles of the first network device and the second network device can be mutually Change.

FIG. 9 shows a schematic structural diagram of a network device 20 provided in an embodiment of the present application. As shown in FIG. 9 , the network device 20 may be applicable to 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 have the function of the first network device as the first network device for some or some UEs, or may have the function of the second network device as the second network device for some or some UEs. The function of network equipment. The network device includes: a baseband device 201 , a radio frequency device 202 , and an antenna 203 . In the uplink direction, the radio frequency device 202 receives the information sent by the terminal device through the antenna 203, and sends the information sent by the terminal device to the baseband device 201 for processing. In the downlink direction, the baseband device 201 processes the information of the terminal device and sends it to the radio frequency device 202 , and the radio frequency device 202 processes the information of the terminal device and sends it 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 . The processing unit 2011 is configured to support the network device to execute the functions of the network device in the foregoing method embodiments. The storage unit 2012 is used to store software programs and/or data. The interface 2013 is used for exchanging information with the radio frequency device 202, and the interface includes an interface circuit for input and output of information. In one implementation, the processing unit is an integrated circuit, 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 can be integrated together to form a chip. The storage unit 2012 and the processing unit 2011 may be located in the same chip, that is, an on-chip storage element. Alternatively, the storage unit 2012 and the processing unit 2011 may also be located on different chips from the processing unit 2011, that is, an off-chip storage unit. The storage unit 2012 may be one memory, or a general term for multiple memories or storage elements.

A network device may implement part or all of the steps in the foregoing method embodiments in the form of one or more processing unit schedulers. For example, the corresponding functions of the network device in FIG. 4 are implemented. The one or more processing units may support wireless access technologies of the same standard, or may support wireless access technologies of different standards.

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

The embodiment of the present application also provides a communication system. Specifically, the communication system includes a network device and a terminal device, or may further include more network devices and multiple terminal devices. Exemplarily, the communication system includes a network device and a terminal device for realizing the related functions in FIG. 4 above.

The network devices are respectively used to realize the functions of the relevant network parts in FIG. 4 above. The terminal device is used to implement the functions of the above-mentioned terminal device in FIG. 4 . For details, please refer to relevant descriptions in the foregoing method embodiments, and details are not repeated here.

An embodiment of the present application also provides a computer-readable storage medium, including instructions, which, when running on a computer, cause the computer to execute the method performed by the network device in Figure 4; or when running on the computer, cause the computer to execute The method executed by the terminal device in FIG. 4 .

An embodiment of the present application also provides a computer program product, including instructions, which, when run on a computer, cause the computer to execute the method performed by the network device in Figure 4; or when run on a computer, cause the computer to execute the method shown in Figure 4 The method executed by the terminal device.

An embodiment of the present application provides a chip system, the chip system includes a processor, and may also include a memory, for implementing the functions of the network device or terminal in the foregoing method; or for realizing the functions of the network device and the terminal in the foregoing method. The system-on-a-chip may consist of chips, or may include chips and other discrete devices.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

Those of ordinary skill in the art can appreciate that various illustrative logical blocks (illustrative logical blocks) and steps (steps) described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. accomplish. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Obviously, those skilled in the art can make various changes and modifications to the application without departing from the spirit and scope of the application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims (36)

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,

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.

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,

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 downlink BWP is a dependent initial downlink BWP, and the first uplink BWP is a dependent initial uplink BWP.

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,

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.

12. The method according to claim 10 or 11,

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.

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,

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

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:

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 gas,

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.

20. The apparatus of claim 18 or 19,

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.

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,

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.

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 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 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,

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

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 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 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,

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,

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.

28. The apparatus of claim 26 or 27,

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.

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.

Images