CN115941143A

CN115941143A - Resource allocation method and device

Info

Publication number: CN115941143A
Application number: CN202111164810.7A
Authority: CN
Inventors: 侯海龙; 金哲; 余政; 温容慧; 孙欢
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-09-30
Filing date: 2021-09-30
Publication date: 2023-04-07
Also published as: WO2023051397A1

Abstract

A resource allocation method and device are provided, in order to increase the continuous frequency domain resource which can be used for allocating PUSCH resource in the carrier bandwidth. The method comprises the following steps: the terminal device receives a first random access message from the network device, wherein the first random access message includes configuration information of a first PUCCH resource and a first BWP, the first PUCCH resource is located in the first BWP, the first BWP is located in a carrier bandwidth, and is located at a position shifted by N resource blocks from a carrier bandwidth boundary to a high frequency direction or a low frequency direction, N is a non-negative integer, the terminal device transmits the PUCCH to the network device by using the first PUCCH resource, and the problem of PUSCH resource fragmentation is solved by designing the first BWP and the first PUCCH resource of the terminal device to be located at an edge position of the carrier bandwidth, so that the uplink rate of the broadband terminal device which does not support discontinuous resource allocation is ensured.

Description

Resource allocation method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a resource allocation method and device.

Background

The bandwidth capabilities of the terminal devices in the new air interface (NR) of the fifth generation (5 th generation,5 g) communication system are different. Some terminal devices can support the whole carrier bandwidth, and can be called as common terminal devices; some terminal devices support a bandwidth capability smaller than the carrier bandwidth, and may be referred to as narrowband terminal devices. For example, the mobile communication standardization organization 3GPP (3 rd Generation Partnership Project) proposes a reduced capability (reduce capability) NR terminal device. One implementation of a terminal device of a RedCap is to reduce the channel bandwidth of the terminal device, which can also be understood as reducing the bandwidth capability of the terminal device. Rel-16 specifies that the bandwidth capability of the NR terminal device of RedCap in the frequency range 1 (frequency range 1, fr1) band is 20MHz, which is much lower than the bandwidth capability of 100MHz of the NR enhanced mobile broadband (eMBB) terminal device.

An eMBB terminal device with a common terminal having a bandwidth capability of 100MHz and a RedCap terminal device with a narrow-band terminal having a bandwidth capability of 20MHz are taken as examples. As shown in fig. 1, the eMBB terminal supports 100MHz bandwidth capability, and the RedCap terminal supports 20MHz fractional bandwidth. The network configures uplink resources for the terminal device in a carrier bandwidth, where the uplink resources include a Physical Uplink Control Channel (PUCCH) and a Physical Uplink Shared Channel (PUSCH), and other resources except the PUCCH resources may allocate the PUSCH. The PUCCH resource is generally configured at an edge position of a partial Bandwidth (BWP) supported by the terminal device. The PUCCH resource of the normal terminal device may be at an edge position of the carrier bandwidth, such as an edge position of the carrier bandwidth of 100MHz in fig. 1, which is indicated by a dotted shaded portion. Since the bandwidth capability supported by a narrowband terminal device is less than the carrier bandwidth, the PUCCH resources of the narrowband terminal device may be distributed at non-edge locations of the carrier bandwidth, as shown in the white-bottom portion of fig. 1. This results in discontinuous, i.e. fragmented, available PUSCH resources, as indicated by the diagonal line shading in fig. 1.

For a terminal device which does not support discontinuous resource allocation, only fragmented PUSCH resources can be allocated, which may cause the uplink rate, especially the peak rate, of the terminal device to be severely reduced.

Disclosure of Invention

The embodiment of the application provides a resource allocation method and a resource allocation device, which are used for solving the problem of improving the uplink rate of common terminal equipment.

In a first aspect, a resource allocation method is provided, where an execution subject of the method may be a terminal device, and may also be a chip applied in the terminal device. The following description will be made taking as an example that the execution subject is a terminal device. The method can be realized by the following steps: the terminal equipment receives a first random access message from the network equipment. The first random access message includes a first fractional bandwidth BWP and configuration information of a first physical uplink control channel PUCCH resource, where the first PUCCH resource is located in the first BWP. The first BWP is located in the carrier bandwidth, and is shifted from the boundary of the carrier bandwidth to the high-frequency direction or the low-frequency direction by N resource blocks, wherein N is a nonnegative integer; and the terminal equipment transmits PUCCH to the network equipment by using the first PUCCH resource. Illustratively, the first BWP may be a portion of the carrier bandwidth that may be located at an edge of the carrier bandwidth, e.g., the edge of the first BWP may coincide with an edge of the carrier bandwidth, or may be located adjacent to the edge of the carrier bandwidth, e.g., the edge of the first BWP may be spaced from the edge of the carrier bandwidth by N resource blocks. By designing the first BWP of the terminal device to be located at the edge of the carrier bandwidth, the continuously available PUSCH resources may be increased. As the number of continuously available PUSCH resources increases, for wideband terminal devices that do not support discontinuous resource allocation, larger continuous PUSCH resources may be used, thereby helping to ensure the uplink rate of these wideband terminal devices.

For example, the difference between the frequency domain end position of the first BWP and the frequency domain start position of the first BWP is the bandwidth occupied by the first BWP, for example, the frequency domain start position of the first BWP is located at a position shifted by N resource blocks from the boundary of the carrier bandwidth to the high frequency direction or to the low frequency direction, which may mean that the frequency domain start position of the first BWP is located at a position shifted by N resource blocks from the lower boundary of the carrier bandwidth to the high frequency direction, or the frequency domain end position of the first BWP is located at a position shifted by N resource blocks from the upper boundary of the carrier bandwidth to the low frequency direction.

For example, N =0, the frequency domain start position of the first BWP is aligned with the lower boundary of the carrier bandwidth, or the frequency domain end position of the first BWP is aligned with the upper boundary of the carrier bandwidth.

In one possible design, the first random access message is any one of the following messages: a conflict resolution message, a radio resource control, RRC, connection setup message, an RRC connection reestablishment message, or an RRC connection recovery message.

In one possible design, the terminal device sends a second random access message to the network device via a second BWP before receiving the first random access message from the network device. For example, the second BWP may be configured in SIB1. And sending a second random access message by using the second BWP configured in SIB1, where the second BWP may not be limited to the edge position of the carrier bandwidth, so as to ensure flexible configuration of parameters required in the random access process.

In one possible design, PUCCH resources are not configured on the second BWP. Since the first PUCCH resource for transmission of the PUCCH is configured in the first BWP. In this way, the PUCCH resource may not be configured on the second BWP, which may achieve the purpose of reducing the configuration complexity of the second BWP.

In one possible design, a second PUCCH resource is configured on the second BWP. By adopting the mode, when the second BWP is configured by the SIB1, the design of the existing SIB1 signaling can not be changed, thereby reducing the complexity of the design and achieving the purpose of saving power consumption.

In one possible design, the terminal device performs resource switching based on a predefined manner, where the resource switching includes: switching to the first BWP by the second BWP, and/or switching to the first PUCCH resource by the second PUCCH resource. Through the protocol pre-defined mode, extra configuration information is not required to be introduced to indicate switching, and network resources are saved.

In one possible design, the terminal device performs resource switching based on the indication information, where the resource switching includes: switching to the first BWP by the second BWP, and/or switching to the first PUCCH resource by the second PUCCH resource. The switching action of the BWP and PUCCH resources may be explicitly indicated. In one possible design, when the terminal device transmits a PUCCH to the network device using the first PUCCH resource, the following may be implemented: after a first duration (for example, the first duration is not less than 10 milliseconds) elapses after the terminal device receives the first random access message, the terminal device sends a PUCCH to the network device using the first PUCCH resource, and the first duration is determined according to a time for the terminal device to process the first random access message. By introducing the first time length, the signaling analysis of the first message can be ensured to be completed, and the network robustness is increased. In a second aspect, a resource configuration method is provided, where an execution subject of the method may be a network device, and may also be a chip applied in the network device. The following description will be given taking as an example that the execution subject is a network device. The method can be realized by the following steps: the network equipment sends a first random access message to the terminal equipment. Wherein the first random access message includes a first fractional bandwidth BWP and configuration information of a first physical uplink control channel PUCCH resource, and the first PUCCH resource is located within the first BWP. The first BWP is located in a carrier bandwidth, and is shifted from the boundary of the carrier bandwidth to the high-frequency direction or the low-frequency direction by N resource blocks, wherein N is a non-negative integer. The network device receives a PUCCH from the terminal device using the first PUCCH resource. Illustratively, the first BWP may be a portion of the carrier bandwidth, which may be located at an edge of the carrier bandwidth, e.g., the edge of the first BWP may coincide with the edge of the carrier bandwidth, or may be located adjacent to the edge of the carrier bandwidth, e.g., the edge of the first BWP may be spaced from the edge of the carrier bandwidth by N resource blocks. By designing the first BWP of the terminal device to be located at the edge of the carrier bandwidth, the continuously available PUSCH resources may be increased. As the number of continuously available PUSCH resources increases, for wideband terminal devices that do not support discontinuous resource allocation, larger continuous PUSCH resources may be used, thereby helping to ensure the uplink rate of these wideband terminal devices.

In one possible design, the network device receives a second random access message from the terminal device via a second BWP before the network device sends the first random access message to the terminal device.

In one possible design, PUCCH resources are not configured on the second BWP.

In one possible design, a second PUCCH resource is configured on the second BWP.

In one possible design, the first random access message further includes indication information indicating that the terminal device performs resource handover, where the resource handover includes handover from the second BWP to the first BWP, and the resource handover may further include handover from the second PUCCH resource to the first PUCCH resource.

The beneficial effects of the same design of the second aspect as the first aspect can be referred to the description of the first aspect, and are not repeated herein.

In a third aspect, a communication apparatus is provided, which may be a terminal device or a component (e.g., a chip or a system of chips or a circuit) located in the terminal device. The apparatus has the function of carrying out the method of the first aspect described above and of any one of the possible designs of the first aspect. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. In one design, the apparatus may include a processing module and a transceiver module. Exemplarily, the following steps are carried out: the processing module is used for calling the transceiver module to send signals to the network equipment or receive signals from the network equipment. The transceiver module is configured to receive a first random access message from a network device, where the first random access message includes a first partial bandwidth BWP and configuration information of a first physical uplink control channel PUCCH resource, the first PUCCH resource is located in the first BWP, the first BWP is located in a carrier bandwidth and is offset by N resource blocks from a carrier bandwidth boundary to a high frequency direction or a low frequency direction, and N is a non-negative integer; the transceiver module is further configured to transmit a PUCCH to the network device using the first PUCCH resource. A more detailed description of the processing module and the transceiver module described above may be taken directly with reference to the related description in the first aspect described above. The third aspect and the advantages of each possible design may be referred to the description of the corresponding parts of the first aspect.

In a fourth aspect, a communication apparatus is provided, which may be a network device or a component (e.g., a chip or a system of chips or a circuit) located in the network device. The apparatus has the functionality to implement the method in any of the possible designs of the second aspect and the second aspect described above. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions. In one design, the apparatus may include a processing module and a transceiver module. By way of example: the processing module is used for calling the transceiver module to send signals to the terminal equipment or receive signals from the terminal equipment. The transceiver module is configured to send a first random access message to a terminal device, where the first random access message includes a first partial bandwidth BWP and configuration information of a first physical uplink control channel PUCCH resource, the first PUCCH resource is located in the first BWP, the first BWP is located in a carrier bandwidth and is offset from a boundary of the carrier bandwidth to a high frequency direction or a low frequency direction by N resource blocks, and N is a non-negative integer; the transceiver module is further configured to receive a PUCCH from the terminal device using the first PUCCH resource. A more detailed description of the processing module and the transceiver module described above can be directly obtained with reference to the related description in the second aspect described above. The fourth aspect and various possible design advantages may refer to the description of the corresponding parts of the second aspect.

In a fifth aspect, an embodiment of the present application provides a communication apparatus, which includes an interface circuit and a processor, where the processor and the interface circuit are coupled to each other. The processor is configured to implement the method described in the first aspect, each possible design of the first aspect, by logic circuits or executing code instructions. The interface circuit is used for receiving signals from other communication devices except the communication device and transmitting the signals to the processor or sending the signals from the processor to other communication devices except the communication device. It will be appreciated that the interface circuit may be a transceiver or an input-output interface.

Optionally, the communication device may further include a memory for storing instructions to be executed by the processor or for storing input data required by the processor to execute the instructions or for storing data generated by the processor after executing the instructions. The memory may be a physically separate unit or may be coupled to the processor, or the processor may comprise the memory.

In a sixth aspect, an embodiment of the present application provides a communication device, which includes an interface circuit and a processor, where the processor and the interface circuit are coupled to each other. The processor is configured to implement the method described in the second aspect, and each possible design of the second aspect, by logic circuits or executing code instructions. The interface circuit is used for receiving signals from other communication devices except the communication device and transmitting the signals to the processor or sending the signals from the processor to other communication devices except the communication device. It will be appreciated that the interface circuit may be a transceiver or an input-output interface.

Optionally, the communication device may further include a memory for storing instructions to be executed by the processor or storing input data required by the processor to execute the instructions or storing data generated after the processor executes the instructions. The memory may be a physically separate unit or may be coupled to the processor, or the processor may comprise the memory.

In a seventh aspect, embodiments of the present application provide a computer-readable storage medium, in which a computer program or readable instructions are stored, and when the computer program or readable instructions are executed by a communication device, the computer program or readable instructions cause the method described in each possible design of the above aspects or aspects to be performed.

In an eighth aspect, an embodiment of the present application provides a chip system, where the chip system includes a processor and may further include a memory. The memory is used for storing programs, instructions or codes; the processor is used to execute the memory-stored programs, instructions or code to implement the methods described in the above-described aspects or various possible designs of aspects. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

In a ninth aspect, there is provided a computer program product containing instructions which, when executed by a communication apparatus, cause a method as described in the third aspect or various possible designs of aspects to be performed.

Drawings

FIG. 1 is a diagram illustrating resource allocation in the prior art;

FIG. 2 is a diagram of a communication system architecture in an embodiment of the present application;

FIG. 3 is a flowchart illustrating a resource allocation method according to an embodiment of the present application;

FIG. 4a is a schematic view of a first BWP in the embodiment of the present application;

FIG. 4b is a second schematic view illustrating the position of the first BWP in the present embodiment;

FIG. 4c is a third exemplary view illustrating a position of the first BWP in accordance with the present invention;

FIG. 4d is a fourth exemplary view illustrating the position of the first BWP in the present embodiment;

fig. 5a is one of schematic diagrams of a first BWP and a second BWP received by a terminal device in this embodiment of the application;

fig. 5b is a second schematic diagram of the first BWP and the second BWP received by the terminal device in the embodiment of the present application;

FIG. 6 is a flowchart illustrating a method for resource allocation according to an embodiment of the present application;

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

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

fig. 9 is a schematic structural diagram of a network device in the embodiment of the present application.

Detailed Description

The embodiment of the application provides a resource allocation method and device, which aim to improve the continuous range of the configurable PUSCH resources in the carrier bandwidth and avoid the problem of PUSCH resource fragmentation. The method and the device are based on the same or similar technical conception, and because the principle of solving the problem of the method and the device is similar, the implementation of the device and the method can be mutually referred, and repeated parts are not described again.

The communication method provided by the embodiment of the application can be applied to a fourth generation (4G) communication system, such as Long Term Evolution (LTE), and can also be applied to a 5G communication system, such as NR, and can also be applied to various communication systems of future evolution, such as a sixth generation (6G) communication system, or an air-space-sea-ground integrated communication system. It can be understood that the system architecture and the application scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided in the embodiment of the present application.

The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

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

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

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

Optionally, in the network architecture shown in fig. 2, a core network device may also be included, and the core network device is not illustrated in fig. 2. The terminal device 110 may be connected to the network device 120 in a wireless manner, and the network device 120 may be connected to the core network device in a wired or wireless manner. The core network device and the network device 120 may be separate and distinct physical devices, or the core network device and the network device 120 may be the same physical device on which all/part of the logical functions of the core network device and the network device 120 are integrated.

In the network architecture shown in fig. 2, the terminal device 110 may be fixed or mobile, and is not limited. The network architecture shown in fig. 2 may further include other network devices, such as a wireless relay device and a wireless backhaul device, without limitation. In the architecture shown in fig. 2, the number of terminal devices, network devices, and core network devices is not limited.

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

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

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

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

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

In the embodiment of the present application, the terminal devices involved may include a narrowband terminal device and a wideband terminal device. The narrowband terminal device may refer to a terminal device that supports a bandwidth smaller than a carrier bandwidth, for example, a red beacon terminal device in NR or a terminal device in a narrowband band internet of things (NB-IoT). The wideband terminal device may also be referred to as a normal terminal device, and refers to a terminal device supporting bandwidth capability as a carrier bandwidth, for example, an eMBB device in NR, or an Ultra Reliable Low Latency Communication (URLLC) device in NR. It is to be understood that the present application may also be applied in any of the following scenarios: the wideband terminal equipment supports a bandwidth larger than that supported by the narrowband terminal equipment.

The RedCap terminal equipment is NR equipment with reduced capacity, and is mainly applied to industrial wireless sensing, video monitoring or wearable equipment and other scenes. The RedCap terminal equipment can have the following characteristics: equipment cost and complexity are reduced; the equipment size is low; the system supports all FR1 and FR2 frequency bands for Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

Based on the problem of PUSCH resource fragmentation caused by resource allocation of a narrowband terminal, embodiments of the present application provide a resource allocation method, which aims to solve the above problem.

Before introducing the resource configuration method provided in the embodiment of the present application, first, how to configure PUCCH resources of a narrowband terminal device in an embodiment a is described. In the following, a narrowband terminal device may be briefly described as a terminal device. In embodiment a, before accessing the network, the terminal device receives a synchronization broadcast signal block (SS/PBCH block, SSB) from the network device, where the SSB carries configuration information of some system information, for example, system information block 1 (sibb 1). The terminal equipment receives the SIB1 according to the SSB. The SIB1 includes basic configuration parameters of the terminal device camping and the access cell, and is used for uplink synchronization. For example, SIB1 includes an initial uplink partial Bandwidth (BWP), a Physical Random Access Channel (PRACH) resource, or a Physical Uplink Control Channel (PUCCH) resource. And the terminal equipment carries out random access according to the configuration parameters in the SIB1 and sends the PUCCH to the network equipment according to the PUCCH resource configuration in the SIB1 after the random access. Based on fig. 1, it can be seen that, since the operating bandwidth of the terminal is a narrow band and is located at a non-edge position of the carrier bandwidth, the PUCCH resource configuration of the terminal device may cause a problem of PUSCH resource fragmentation.

Based on this, the embodiment of the present application provides a resource configuration method, so as to solve the problem of PUSCH resource fragmentation. As shown in fig. 3, a flow of the resource allocation method provided in the embodiment of the present application is as follows. The method can be executed by the terminal device and the network device, or can also be executed by a chip in the terminal device and a chip in the network device. The network device in fig. 3 may be the network device 120 in fig. 2 and the terminal device may be the terminal device 110 in fig. 2.

S301, the network device sends a first random access message to the terminal device, and correspondingly, the terminal device receives the first random access message from the network device.

The first random access message includes configuration information of a first BWP and a first PUCCH resource, and the first PUCCH resource is located within the first BWP. The first BWP is located within the carrier bandwidth, and the first BWP is located at an edge position of the carrier bandwidth, that is, the first BWP is located at a position shifted by N resource blocks from a boundary of the carrier bandwidth to a high frequency direction or a low frequency direction, where N is a non-negative integer, that is, N is 0 or an integer greater than 0.

It should be noted that the configured first BWP may be an initial upstream BWP or a proprietary upstream BWP.

S302, the terminal equipment sends PUCCH to the network equipment by using the first PUCCH resource, and the network equipment receives PUCCH from the terminal equipment by using the first PUCCH resource.

Because part of the terminal devices are broadband terminal devices which do not support discontinuous resource allocation, the first BWP of the terminal devices is designed to be positioned at the edge position of the carrier bandwidth, and the continuously available PUSCH resources are increased, thereby being beneficial to ensuring the uplink rate of the broadband terminal devices which do not support discontinuous resource allocation.

Some alternative implementations of the embodiment of fig. 3 are described below.

Illustratively, the first BWP is located at a position shifted by N resource blocks from the boundary of the carrier bandwidth in the high frequency direction or in the low frequency direction. The difference between the frequency domain end position of the first BWP and the frequency domain start position of the first BWP is the bandwidth occupied by the first BWP.

For example, N is 0, and the frequency domain start position of the first BWP is aligned with the lowest frequency domain position of the carrier bandwidth. For another example, N is 0, and the frequency domain end position of the first BWP is aligned with the highest frequency domain position of the carrier bandwidth.

For example, N is greater than 0, meaning that the first BWP is offset from the boundary of the carrier bandwidth by N resource blocks.

The frequency domain start position of the first BWP may be located at a position shifted upward by a first offset value from the lowest frequency domain position of the carrier bandwidth. Alternatively, the frequency domain end position of the first BWP is located at the highest frequency domain position of the carrier bandwidth shifted downward by the second offset value. The first offset value may refer to one or more frequency domain units, which may be RBs or time units or other units of measure. Similarly, the second offset value may refer to one or more frequency domain units, which may be RBs or time units or other units of measure.

The position of the first BWP is illustrated below with reference to the example of fig. 1. For example, the carrier bandwidth is 100MHz and the first BWP is 20MHz. As shown in fig. 4a, the first BWP is located at the lower edge of the carrier bandwidth, and the frequency domain start position of the first BWP is aligned with the lowest frequency domain position of the carrier bandwidth. As shown in fig. 4b, the first BWP is located at the upper edge of the carrier bandwidth, and the frequency domain end position of the first BWP is aligned with the highest frequency domain position of the carrier bandwidth. As shown in fig. 4c, the first BWP is close to the lower edge of the carrier bandwidth, and the first BWP is located at N resource blocks shifted from the boundary of the carrier bandwidth to the high frequency direction, where N is greater than 0. As shown in fig. 4d, the first BWP is close to the upper edge of the carrier bandwidth, and the first BWP is located at N resource blocks shifted from the boundary of the carrier bandwidth to the low frequency direction, where N is greater than 0. In fig. 4c or fig. 4d, PUCCH of the wideband terminal device may also be configured on N resource blocks of the first BWP offset.

In fig. 4a to 4d, the PUSCH resources are shown by hatching with oblique lines, and as can be seen from fig. 4a to 4d, the continuous available range of the PUSCH resources is enlarged, which is beneficial to configure a larger continuous PUSCH resource for the broadband terminal device, and ensure the uplink rate of the broadband terminal device.

As described in the foregoing embodiment a of resource configuration, parameters such as initial uplink BWP, PRACH resource, and PUCCH resource of the terminal device may be configured in SIB1. In contrast, the embodiment of fig. 3 configures a first BWP and a first PUCCH resource in a first random access message. In this way, the terminal device's transmission of upstream data is based on the first BWP, rather than the initial upstream BWP indicated in SIB1.

The first random access message is a message in the random access process. Illustratively, the first random access message may be a last message in a random access procedure. That is, in the process of random access by the terminal device, the first random access message is the last step message sent by the network device to the terminal device, and after the terminal device receives the first random access message, the process of random access is completed. The random access process may be four-step random access, including the following processes: the terminal equipment sends a message 1 (bearing a random access preamble) to the network equipment, the network equipment sends a message 2 (bearing a random access response) to the terminal equipment, the terminal equipment sends a message 3 (bearing control information) to the network equipment, the control information comprises a unique identifier of the terminal equipment, and the network equipment sends a message 4 (bearing competition resolving information) to the terminal equipment. The first random access message may be message 4. The random access process may also be a two-step random access process, including the following processes: the terminal device sends a message a (bearer random access request) to the network device, and the network device sends a message B (bearer random access response) to the terminal device, and the first random access message may be message B.

Optionally, the first random access message may be a collision resolution message, a Radio Resource Control (RRC) connection setup message, an RRC connection reestablishment message, or an RRC connection recovery message.

The random access procedure may include a multi-step message, and the terminal device may also send a second random access message to the network device before receiving the first random access message from the network device. The terminal device may transmit a second random access message to the network device through the second BWP. For two-step random access, the second random access message may be, for example, message a. For four-step random access, the second random access message may be message 1 or message 3.

The BWP used by the terminal device in the random access process and the BWP for transmitting the PUCCH are configured respectively. The first BWP is configured through the first random access message and the second BWP needs to be configured before the random access, e.g., the second BWP may be configured through SIB1.

Before the random access procedure, the network device sends SIB1 to the terminal device, and the terminal device receives SIB1 from the network device. SIB1 includes uplink synchronization related configuration parameters, for example, SIB1 may include an initial uplink BWP (i.e., a second BWP) and PRACH resources, and may further include a resource of message 3. The PRACH resources and the resources of message 3 may be indicated on a second BWP basis. And after receiving the SIB1, the terminal equipment sends a preamble to the network equipment according to the PRACH resource indicated by the SIB1. And the terminal equipment sends the message 3 to the network equipment according to the resource of the message 3 indicated by the SIB1.

On the basis that the first random access message configures the first BWP and the first PUCCH resource, whether the second BWP needs to configure the PUCCH resource is provided.

The method I comprises the following steps: the PUCCH resource is not configured on the second BWP.

For example, the configuration parameters of SIB1 do not include PUCCH resources, and the terminal device may perform random access according to SIB1, and transmit PUCCH to the network device using the first PUCCH resource after the first random access message indicates the first BWP and the first PUCCH resource. After the terminal device accesses the network, when performing data transmission with the network device, the second BWP is already released, or the configuration of the second BWP is already invalid, and the terminal device may use the configuration of the first BWP, and because the first BWP is configured at the edge of the carrier bandwidth, the PUSCH resource is not fragmented.

On the basis of the first method, a schematic diagram of the first BWP and the second BWP received by the terminal device is shown in fig. 5 a. The terminal equipment receives configuration information of a second BWP from the network equipment at the time t1, and PUCCH resources are not configured in the second BWP; the terminal device receives a first random access message from the network device at a time t2, where the first random access message includes configuration information of a first BWP, and a first PUCCH resource is configured in the first BWP.

The second method comprises the following steps: and a second PUCCH resource is configured on the second BWP.

For example, when the second BWP is configured through SIB1, the SIB1 further includes configuration information of the second PUCCH resource. In this case, the signaling of the existing SIB1 may not be changed. If the terminal device is expected to transmit the PUCCH according to the first PUCCH resource in the first random access message, resource switching can be carried out according to the following mode. The resource switching includes switching from the second BWP to the first BWP and also includes switching from the second PUCCH resource to the first PUCCH resource. On the basis that the SIB1 message is received and includes the second PUCCH resource, the terminal equipment does not use the second PUCCH resource to transmit the PUCCH, but uses the first PUCCH resource in the first random access message to transmit the PUCCH after receiving the first random access message. The terminal equipment can perform resource switching based on a predefined mode, namely, the protocol is well specified, and the terminal equipment performs resource switching after receiving the first random access message. Or, the terminal device performs resource switching based on the indication information, and the indication information may be carried in the first random access message. For example, the first random access message is a message 4, the message 4 includes a PDCCH and a PDSCH, the configuration information of the first BWP and the first PUCCH resource is carried in the PDSCH of the message 4, and the indication information is carried in the PDCCH of the message 4.

Based on the second method, the schematic diagram of the first BWP and the second BWP received by the terminal device is shown in fig. 5 b. The terminal device receives configuration information of a second BWP from the network device at the time t1, wherein a second PUCCH resource is configured in the second BWP; the terminal device receives a first random access message from the network device at a time t2, where the first random access message includes configuration information of a first BWP, and a first PUCCH resource is configured in the first BWP. And after receiving the first random access message, the terminal equipment performs resource switching and transmits the PUCCH by using the first PUCCH resource.

By adopting the second mode, the terminal device needs a certain time length for processing the first random access message, and based on this, the terminal device can use the first PUCCH resource to send the PUCCH to the network device after the first time length elapses from the time when the first random access message is received. The first duration is determined according to the time for processing the first random access message by the terminal equipment. For example, the first random access message may carry RRC signaling, generally, a duration for the terminal device to process the RRC signaling is not less than 10ms, the first duration may be set to be greater than or equal to 10ms, and an upper limit of the first duration may also be set, for example, the first duration is not greater than 20ms.

The resource allocation method according to the embodiment of the present application is described in detail below with reference to specific application scenarios.

Taking four-step random access as an example, as shown in fig. 6, the resource allocation method is as follows.

S601, the network device sends SIB1 to the terminal device, and correspondingly, the terminal device receives SIB1 from the network device.

Illustratively, the SIB1 includes an initial uplink BWP resource (corresponding to the second BWP in the foregoing), and the initial uplink BWP resource is configured with parameters such as PRACH time-frequency resource and configuration information of the message 3 (Msg 3). In one approach, the initial uplink BWP is configured with the resource of the second PUCCH, and in another approach, the initial uplink BWP is not configured with the resource of the PUCCH.

And S602, the terminal equipment uses PRACH time frequency resources to send a preamble, namely a message 1, to the network equipment according to the configuration parameters in the SIB1. Correspondingly, the network device receives the preamble from the terminal device.

S603, the network device sends a message 2, namely a random access response, to the terminal device, and correspondingly, the terminal device receives the random access response from the network device.

S604, the terminal device sends the Msg3 to the network device based on the configuration information of the Msg3 in the SIB1, and the network device receives the Msg3 from the terminal device.

S605, the network device sends a message 4 to the terminal device, wherein the message 4 is a conflict resolution message, and correspondingly, the terminal device receives the message 4 from the network device.

The message 4 includes configuration information of the first BWP and the first PUCCH resource, and the message 4 corresponds to the first random access message in the foregoing.

And S606, the terminal equipment sends the PUCCH to the network equipment by using the first PUCCH resource. The network device receives the PUCCH from the terminal device using the first PUCCH resource.

If the second PUCCH resource is configured on the initial uplink BWP in S601, the terminal device needs to perform resource switching, that is, switching from the second PUCCH resource to the first PUCCH resource, and switching from the second BWP to the first BWP.

In the embodiments provided in the present application, the method provided in the embodiments of the present application is introduced from the perspective of a network device, a terminal device, and interaction between the network device and the terminal device. In order to implement the functions in the method provided by the embodiments of the present application, the network device and the terminal device may include a hardware structure and/or a software module, and the functions are implemented in the form of a hardware structure, a software module, or a hardware structure and a software module. Whether any of the above-described functions is implemented as a hardware structure, a software module, or a hardware structure plus a software module depends upon the particular application and design constraints imposed on the technical solution.

In the embodiments provided in the present application, the method provided in the embodiments of the present application is introduced from the perspective of interaction between the terminal device and the network device. The steps executed by the network device may also be implemented by different communication apparatuses. For example: the first apparatus is configured to send a first random access message, and the second apparatus is configured to receive a PUCCH from the terminal device using the first PUCCH resource, that is, the first apparatus and the second apparatus together complete the steps performed by the network device in the embodiment of the present application, and the present application does not limit a specific partitioning manner. When one or more DUs, one or more CUs, and one or more radio frequency units (RUs) are included in the network architecture, the steps performed by the network device described above can be implemented by a DU, a CU, and a RU, respectively. In order to implement the functions in the method provided by the embodiments of the present application, the terminal device and the network device may include a hardware structure and/or a software module, and the functions are implemented in the form of a hardware structure, a software module, or a hardware structure and a software module. Whether any of the above-described functions is implemented as a hardware structure, a software module, or a hardware structure plus a software module depends upon the particular application and design constraints imposed on the technical solution.

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

As shown in fig. 7, the communication apparatus 700 includes a transceiver module 701 and a processing module 702. The communication apparatus 700 may be used to implement the functions of the terminal device or the network device in the above method embodiments.

When the communication apparatus 700 is used to implement the functions of the terminal device in the method embodiment: a transceiver module 701, configured to receive a first random access message from a network device; and means for transmitting the PUCCH to the network device using the first PUCCH resource. The processing module 702 is configured to invoke the transceiver module 701 to transmit a signal to a network device or receive a signal from the network device.

When the communication apparatus 700 is used to implement the functions of the network device in the method embodiment: a transceiver module 701, configured to send a first random access message to a terminal device, and to receive a PUCCH from the terminal device using a first PUCCH resource; the processing module 702 is configured to invoke the transceiver module 701 to send a signal to the terminal device or receive a signal from the terminal device.

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

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

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

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

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

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

In one example, the antenna and the control circuit with transceiving functions can be regarded as a transceiving module of the terminal device 800, and the processor with processing function can be regarded as a processing module of the terminal device 800, so that the terminal device 800 can be regarded as the communication apparatus 700. The transceiver module of the terminal device 800 can be regarded as the transceiver module 701 of the communication apparatus 700, and the processing module of the terminal device 800 can be regarded as the processing module 702 of the communication apparatus 700. A transceiver module may also be referred to as a transceiver, a transceiving device, etc. Optionally, a device in the transceiver module 701 for implementing the receiving function may be regarded as a receiving unit, and a device in the transceiver module 701 for implementing the transmitting function may be regarded as a transmitting unit, that is, the transceiver module 701 includes a receiving unit and a transmitting unit. For example, the receiving unit may also be referred to as a receiver, a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitting circuit, etc.

The embodiment of the present application further provides a network device, which may be used in the foregoing embodiments. The network device comprises means (means), units and/or circuits to implement the functionality of the network device described in the embodiment shown in fig. 3. For example, the network device includes a transceiver module for supporting the terminal device to implement a transceiver function, and a processing module for supporting the network device to process the signal.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method for resource allocation, comprising:

receiving a first random access message from a network device; wherein the first random access message includes configuration information of a first partial bandwidth BWP and a first physical uplink control channel PUCCH resource, and the first PUCCH resource is located within the first BWP; the first BWP is located in a carrier bandwidth, and is shifted by N resource blocks from the boundary of the carrier bandwidth to the high-frequency direction or the low-frequency direction, wherein N is a non-negative integer;

and transmitting the PUCCH to the network equipment by using the first PUCCH resource.

2. The method of claim 1, wherein the first random access message is any one of: a conflict resolution message, a radio resource control, RRC, connection setup message, an RRC connection reestablishment message, or an RRC connection recovery message.

3. The method of claim 1 or 2, wherein prior to receiving the first random access message from the network device, the method further comprises:

transmitting a second random access message to the network device through a second BWP.

4. The method of claim 3, wherein a second PUCCH resource is configured on the second BWP.

5. The method of claim 4, wherein the method further comprises:

performing resource switching based on a predefined manner, wherein the resource switching comprises: switching to the first BWP by the second BWP, and/or switching to the first PUCCH resource by the second PUCCH resource.

6. The method of claim 4, wherein the method further comprises:

performing resource switching based on the indication information, wherein the resource switching comprises: switching to the first BWP by the second BWP, and/or switching to the first PUCCH resource by the second PUCCH resource.

7. The method of any of claims 1-6, wherein transmitting the PUCCH to the network device using the first PUCCH resource comprises:

after a first duration from the reception of the first random access message, transmitting a PUCCH to the network equipment by using the first PUCCH resource; the first duration is determined according to a time at which the first random access message is processed.

8. A method for resource allocation, comprising:

sending a first random access message to terminal equipment; wherein the first random access message includes configuration information of a first partial bandwidth BWP and a first physical uplink control channel PUCCH resource, and the first PUCCH resource is located within the first BWP; the first BWP is located in a carrier bandwidth, and is shifted by N resource blocks from the boundary of the carrier bandwidth to the high-frequency direction or the low-frequency direction, wherein N is a non-negative integer;

and receiving the PUCCH from the terminal equipment by using the first PUCCH resource.

9. The method of claim 8, wherein the first random access message is any one of: a conflict resolution message, a radio resource control, RRC, connection setup message, an RRC connection reestablishment message, or an RRC connection recovery message.

10. The method of claim 8 or 9, wherein prior to sending the first random access message to the terminal device, the method further comprises:

receiving a second random access message from the terminal device through a second BWP.

11. The method of claim 10, wherein a second PUCCH resource is configured on the second BWP.

12. The method of claim 11, wherein the first random access message further comprises indication information for indicating the terminal device to perform resource handover, the resource handover comprising: switching to the first BWP by the second BWP, and/or switching to the first PUCCH resource by the second PUCCH resource.

13. A communications device comprising means for performing the method of any one of claims 1 to 7 or the method of any one of claims 8 to 12.

14. 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 one of claims 1 to 7 or the method of any one of claims 8 to 12.

15. 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 7 or the method of any of claims 8 to 12.

16. A computer program product, the computer program product comprising: computer program code for implementing the method of any of claims 1 to 7 or the method of any of claims 8 to 12 when said computer program code is run.