Patent Description:
In a new radio (new radio, NR) system, a base station may configure one or more bandwidth parts (bandwidth part, BWP) for a terminal. A BWP includes one or more contiguous physical resource blocks (physical resource block, PRB) in frequency domain.

In BWP-based uplink/downlink resource allocation, there are two resource allocation manners: a resource allocation type <NUM> (a type <NUM> for short hereinafter) and a resource allocation type <NUM> (a type <NUM> for short hereinafter). As shown in <FIG>, for the type <NUM>, a BWP is divided into one or more resource block groups (resource block group, RBG). A base station may schedule resources at a per-RBG granularity, and allocate some or all of RBGs in a BWP to a terminal. As shown in <FIG>, for the type <NUM>, a base station may indicate, to a terminal by using a resource indication value (resource indication value, RIV), an identifier of a starting virtual resource block (virtual resource block, VRB) that is allocated to the terminal and that is in a BWP and a quantity of contiguous VRBs. A VRB is logically a virtual resource block (resource block, RB), and needs to be mapped to a PRB finally.

Based on the two resource allocation manners, when BWPs configured by a base station for a narrowband terminal and a wideband terminal overlap, there may be a problem that a resource not scheduled to the narrowband terminal cannot be scheduled to the wideband terminal, resulting in generation of a resource fragment and a waste of resources.

<CIT> describes New Radio frequency-domain resource allocation techniques.

<CIT> describes a frequency domain resource allocation indication information sending method that comprises: determining a corresponding relationship between each first VRB in a first BWP and a secondVRB in a to-be-activated second BWP; determining a resource indication value according to the first BWP; and sending the resource indication value to a user terminal, so as to enable the user terminalto determine an initial first VRB and a first VRB.

<CIT> proposes a BWP (group) design that supports discrete frequency domain resources.

Embodiments of this application provide a resource allocation method, an apparatus, and a system, to reduce a waste of resources and improve resource utilization.

To achieve the foregoing objectives, the invention of this application is defined and limited by the appended set of independent claims. Further embodiments are set out by the appended dependent claims.

For ease of understanding solutions in embodiments of this application, brief descriptions or definitions of relevant technologies are first provided as follows:.

Subcarrier: In an orthogonal frequency division multiplexing (orthogonal frequency division multiplexing, OFDM) system, a frequency domain resource is divided into several sub-resources. Each sub-resource in frequency domain may be referred to as a subcarrier. The subcarrier may also be considered as a minimum granularity of the frequency domain resource.

Subcarrier spacing: A subcarrier spacing is a value of a spacing between center positions or peak positions of two adjacent subcarriers in frequency domain. For example, a subcarrier spacing in a long term evolution (Long Term Evolution, LTE) system is <NUM> kilohertz (kilohertz, kHz), and a subcarrier spacing in an NR system is <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or the like.

The subcarrier spacing in the NR system may be configured by using a network device. For example, a subcarrier spacing configuration µ=<NUM> corresponds to a subcarrier spacing of <NUM>, a subcarrier spacing configuration µ=<NUM> corresponds to a subcarrier spacing of <NUM>, a subcarrier spacing configuration µ=<NUM> corresponds to a subcarrier spacing of <NUM>, a subcarrier spacing configuration µ=<NUM> corresponds to a subcarrier spacing of <NUM>, a subcarrier spacing configuration µ=<NUM> corresponds to a subcarrier spacing of <NUM>, or the like.

Resource block (resource block, RB): N contiguous subcarriers in frequency domain may be referred to as one RB. For example, one RB in an LTE system and an NR system includes <NUM> subcarriers. As a communication system evolves, a quantity of subcarriers included in one RB may alternatively be another value.

Physical resource block (physical resource block, PRB): A PRB may be understood as a concept of physical frequency domain resources used in allocation of frequency domain resources.

Virtual resource block (virtual resource block, VRB): A VRB may be understood as a concept of logical frequency domain resources used in allocation of frequency domain resources.

It should be noted that a VRB is logically a virtual RB, and needs to be mapped to a PRB finally. A VRB is mapped to a PRB in two manners: interleaving and non-interleaving. In the non-interleaving manner, the VRB is the same as the PRB. In the interleaving manner, the VRB is mapped to the PRB according to a specific rule. In this case, contiguous VRBs are not necessarily mapped to contiguous PRBs finally. For mapping from a VRB to a PRB, refer to an existing technology in NR.

Point A: A point A is a common reference point used to indicate a resource block. A location of the point A is configured by a network device.

Common resource block (common resource block, CRB): For a subcarrier spacing configuration µ, CRBs are numbered sequentially in ascending order of frequency from <NUM>. For the subcarrier spacing configuration µ, the point A corresponds to a center position of a subcarrier <NUM> of a CRB <NUM>. Therefore, when the location of the point A is determined, a location of a CRB is determined. For a relationship between a PRB number and a CRB number, refer to an existing technology in NR.

It should be noted that "number", "index", and "identifier" in embodiments of this application may be replaced with each other. They are all described herein, and details are not described again in the following embodiments.

A BWP includes one or more contiguous PRBs in frequency domain. The BWP is a subset of a bandwidth of a terminal, with a minimum granularity of one PRB. In other words, the PRB may represent an RB in the BWP, and an RB at a lowest frequency in the BWP is numbered first. PRBs included in each BWP are numbered from <NUM>. VRBs included in each BWP are also numbered from <NUM>.

In addition, a network device may configure one or more BWPs for a terminal. The plurality of BWPs may overlap (overlap) in frequency domain. For example, as shown in <FIG>, a network device configures four BWPs for a terminal. A BWP1 and a BWP2 overlap.

It should be noted that at a same time, a terminal device is allowed to operate in only one BWP, or to activate only one BWP for transmission.

It should be noted that "bandwidth part" in embodiments of this application may also be referred to as "bandwidth region", and the two may be replaced with each other. In addition, in the following embodiments of this application, the BWP is used to represent a bandwidth part, and a size (size) of a BWP is a quantity of PRBs (or RBs) included in the BWP. They are all described herein, and details are not described again in the following embodiments.

The following uses a downlink resource allocation manner as an example for description.

For the type <NUM>, a BWP is divided into one or more resource block groups (resource block group, RBG). The RBG is a group of contiguous VRBs. A size (size) of each RBG, or a quantity of VRBs included in each RBG, is determined based on a size of the BWP. An index of an RBG starts from a lowest frequency of the BWP, and RBGs are numbered in ascending order of frequency.

It should be noted that in embodiments of this application, a size of an RBG is a quantity of VRBs included in the RBG.

For example, a relationship between a BWP size and a nominal (nominal) RBG size is shown in Table <NUM> below. P is the nominal RBG size. A network device may notify a terminal device to use a configuration <NUM> or a configuration <NUM>.

The nominal RBG size may be understood as sizes of other RBGs other than a first RBG and a last RBG in a BWP. Sizes of the first RBG and the last RBG are less than or equal to the nominal RBG size.

After determining a BWP that is currently in use, the terminal device may determine a size of each RBG in the BWP according to Table <NUM>. An example is provided as follows:
If a size of the BWP is <MAT>, that is, the BWP includes <MAT> PRBs, a total quantity NRBG of RBGs in the BWP meets: <MAT> where P is determined by searching Table <NUM> based on the size of the BWP; <MAT> is a number of a CRB corresponding to a starting PRB in the BWP; mod indicates a modulo operation; and | | indicates rounding-up.

After determining the size of each RBG in the BWP, the terminal device may determine, based on downlink control information (downlink control information, DCI), RBGs in the BWP that are scheduled by the network device.

In the DCI, a bitmap (bitmap) with a size of NRBG is used to indicate the RBGs scheduled by the network device. Each bit in the bitmap corresponds to one RBG. Specifically, in the bitmap, a most significant bit (most significant bit, MSB) corresponds to the RBG0, a least significant bit (least significant bit, LSB) corresponds to the last RBG, and so on. In addition, when the network device schedules an RBG for the terminal device, a bit corresponding to the RBG in the bitmap is set to <NUM>. When an RBG is not scheduled by the network device, a bit corresponding to the RBG in the bitmap is set to <NUM>.

The following uses a specific example to describe the resource allocation manner.

For example, a bandwidth of the BWP is <NUM> PRBs, that is, <MAT>, and the configuration <NUM> is used.

(<NUM>) It is determined according to Table <NUM> that P=<NUM>. (<NUM>) A total quantity of RBGs: <MAT>.

That is, a correspondence between an RBG and VRBs is shown in Table <NUM> below.

(<NUM>) A length of the bitmap in the DCI is equal to the total quantity of RBGs and is <NUM>. (<NUM>) It is assumed that the bitmap is <NUM>. That is, the network device allocates an RBG0, an RBG2, an RBG4, an RBG5, an RBG6, and an RBG12 to the terminal device. For example, as shown in <FIG>, boxes filled with vertical lines are the RBGs scheduled by the network device.

In conclusion, for the type <NUM>, resources are scheduled at a per-RBG granularity, and allocation of non-contiguous VRBs in frequency domain is supported. It should be noted that the type <NUM> can also support allocation of contiguous VRBs in frequency domain. For example, a plurality of consecutive bits in the bitmap are set to <NUM>.

In the type <NUM>, a base station may allocate one VRB or a plurality of contiguous VRBs in a BWP to a terminal device. Specifically, a network device adds a resource indication value (resource indication value, RIV) to a resource allocation field in DCI. Based on the RIV, the following can be derived: an identifier (RBstart) of a starting VRB allocated to the terminal device and a quantity (LRBs) of contiguous VRBs.

In the DCI, a quantity of bits occupied by the RIV is: <MAT>, where <MAT> is a size of a downlink activated BWP, that is, a quantity of PRBs included in the BWP. It may be understood that <MAT> and <MAT> are equal.

For example, a bandwidth of the BWP is <NUM> PRBs, an index RBstart of the starting VRB is <NUM>, and the quantity LRBs of contiguous VRBs is <NUM>.

A quantity of bits occupied by an RIV field in the DCI for downlink scheduling is: <MAT>.

After the terminal device receives the RIV, a possible implementation in which the terminal device determines RBstart and LRBs based on the RIV is as follows:
<IMG>.

Based on the foregoing example, after receiving the RIV, the terminal device can determine based on the implementation that the index RBstart of the starting VRB is <NUM> and the quantity LRBs of contiguous VRBs is <NUM>, as shown in <FIG>.

In conclusion, the type <NUM> supports allocation of contiguous VRBs in frequency domain. Different from the type <NUM> that has a scheduling granularity of an RBG, the type <NUM> may have a scheduling granularity of a VRB (or an RB).

In addition, an uplink type <NUM> and an uplink type <NUM> are similar to the downlink type <NUM> and the downlink type <NUM>, respectively. Only replacing a downlink parameter with an uplink parameter is required. Therefore, details are not described herein again.

Currently, a terminal device in an NR system has a large operating bandwidth, and may be referred to as a wideband terminal or a wideband terminal device. For a frequency band <NUM> (FR1), a maximum operating bandwidth of the terminal device may reach <NUM> megahertz (megahertz, MHz). For a frequency band <NUM> (FR2), the maximum operating bandwidth of the terminal device may reach <NUM>.

However, the wideband terminal has high costs and is not suitable to be used in an internet of things application with relatively low costs. Therefore, a narrowband terminal is introduced in NR. That is, the terminal device has a small operating bandwidth. However, when the narrowband terminal and the wideband terminal coexist and BWPs configured by a network device for the narrowband terminal and the wideband terminal overlap, if in a scheduling, RBGs or VRBs scheduled by the network device to the narrowband terminal are the same as some VRBs in an RBG configured for the wideband terminal, the some VRBs in the RBG configured for the wideband terminal are scheduled to the narrowband terminal. Because scheduling is performed on a per-RBG granularity in the type <NUM>, the network device cannot schedule the RBG configured for the wideband terminal to the wideband terminal. As a result, other RBGs not scheduled to the narrowband terminal in the RBG configured for the wideband terminal cannot be scheduled to the wideband terminal. In other words, it may result in a problem that a resource not scheduled to the narrowband terminal cannot be scheduled to the wideband terminal, causing a waste of resources.

For example, it is assumed that a terminal <NUM> is a narrowband terminal, a size of a BWP1 allocated by the network device to the terminal <NUM> is <NUM> PRBs, a terminal <NUM> is a wideband terminal, a size of a BWP2 allocated by the network device to the terminal <NUM> is <NUM> PRBs, and the BWP1 and BWP2 have a same starting frequency. The following scenarios are considered.

Scenario <NUM>: The type <NUM> is used for resource allocation of both the terminal <NUM> and the terminal <NUM>.

It is assumed that the network device performs configuration according to the configuration <NUM> for both the terminal <NUM> and the terminal <NUM>. According to Table <NUM> described above, a nominal RBG size corresponding to the BWP1 is <NUM>, and a nominal RBG size corresponding to the BWP2 is <NUM>. In this case, division of RBGs corresponding to the BWP1 and division of RBGs corresponding to the BWP2 may be shown in <FIG>. It may be understood that <FIG> shows only some RBGs in the BWP2.

Based on <FIG>, if the network device schedules an RBG0, an RBG1, an RBG3, an RBG4, an RBG5, an RBG6, an RBG7, and an RBG8 in the BWP1 to the terminal <NUM>, in this case, an RBG2 in the BWP1 is not scheduled to the terminal <NUM>. However, because the RBG0, the RBG1, the RBG3, the RBG4, the RBG5, the RBG6, and the RBG7 in the BWP1 are scheduled to the terminal <NUM>, these RBGs are the same as some VRBs in an RBG0 in the BWP2, and the network device cannot schedule a same VRB to different terminals at a same time, the RBG0 in the BWP2 cannot be scheduled to the terminal <NUM>. As a result, the RBG2 in the BWP1 is neither scheduled to the terminal <NUM> nor can be scheduled to the terminal <NUM>, and becomes a resource fragment. Likewise, a VRB not scheduled to the terminal <NUM> in an RBG1 in the BWP2 is also a resource fragment. These resource fragments are not used, causing a waste of resources.

Scenario <NUM>: The terminal <NUM> uses the type <NUM> for allocation of downlink resources, and the terminal <NUM> uses the type <NUM> for allocation of downlink resources.

For the terminal <NUM>, it is assumed that the network device performs configuration according to the configuration <NUM>. According to Table <NUM> described above, a nominal RBG size corresponding to the BWP2 is <NUM>.

It is assumed that a starting VRB that is in the BWP1 and that is scheduled by the network device to the terminal <NUM> is the same as a VRB in an RBG0 in the BWP2, and a last VRB that is in the BWP1 and that is scheduled by the network device to the terminal <NUM> is the same as a VRB in an RBG1 in the BWP2, as shown in <FIG>. Some VRBs in the RBG0 in the BWP2 are scheduled to the terminal <NUM>. Therefore, the RBG0 cannot be scheduled to the terminal <NUM>. As a result, VRBs not scheduled to the terminal <NUM> in the RBG0 also cannot be scheduled to the terminal <NUM>. Likewise, a VRB not scheduled to the terminal <NUM> in the RBG1 in the BWP2 also cannot be scheduled to the terminal <NUM>, causing a waste of resources.

It may be understood that <FIG> shows only some RBGs in the BWP2.

Based on this, embodiments of this application provide resource allocation methods to reduce generation of a resource fragment, thereby improving resource utilization.

The following describes technical solutions in embodiments of this application with reference to the accompanying drawings in embodiments of this application. In a description of this application, unless otherwise specified, "/" indicates that associated objects are in an "or" relationship. For example, A/B may represent A or B. In this application, "and/or" is merely an association relationship describing associated objects, and indicates that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists, where A and B may be singular or plural. In addition, in the descriptions of this application, "a plurality of" means two or more than two. "At least one of the following items (pieces)" or a similar expression thereof refers to any combination of these items, including any combination of singular items (pieces) or plural items (pieces). For example, at least one of a, b, or c may indicate: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.

In addition, to clearly describe the technical solutions in embodiments of this application, words such as "first" and "second" are used in embodiments of this application to distinguish between same items or similar items that have basically the same functions or purposes. A person skilled in the art may understand that the terms such as "first" and "second" do not limit a quantity or an execution sequence, and the terms such as "first" and "second" do not indicate a definite difference. In embodiments of this application, the word "example", "for example", or the like is used to represent giving an example, an illustration, or a description. Any embodiment or design scheme described as an "example" or "for example" in embodiments of this application should not be explained as being more preferred or having more advantages than another embodiment or design scheme. Exactly, use of the word "example", "for example", or the like is intended to present a related concept in a specific manner.

Embodiments of this application may be applicable to an LTE system and an NR system, and may also be applicable to other wireless communication systems such as a global system for mobile communication (global system for mobile communication, GSM), a mobile communication system (universal mobile telecommunications system, UMTS), a code division multiple access (code division multiple access, CDMA) system, a wideband code division multiple access (wideband code division multiple access, WCDMA) system, a <NUM> network, and a future-oriented new network system. This is not specifically limited in embodiments of this application. The foregoing communication systems to which this application is applicable are merely used as examples for description. A communication system to which this application is applicable is not limited thereto. They are all described herein, and details are not described again below. The terms "system" and "network" can be interchanged with each other.

<FIG> shows a communication system <NUM> according to an embodiment of this application. The communication system <NUM> includes a network device <NUM>, and one or more terminal devices <NUM> connected to the network device <NUM>. Optionally, different terminal devices <NUM> may communicate with each other.

For example, the network device <NUM> shown in <FIG> interacts with any terminal device <NUM>. In this embodiment of this application, the network device and the terminal device determine a bandwidth part allocated to the terminal device. The bandwidth part includes a first bandwidth part. The network device determines a first value and sends first indication information to the terminal device, so that the terminal device receives the first indication information. The first indication information is used to indicate the first value. The first value may be used to indicate an RBG size corresponding to the first bandwidth part. Correspondingly, after receiving the first indication information, the terminal device determines, based on the first value, the RBG size corresponding to the first bandwidth part. Alternatively, the first value may be used to determine an RIV set corresponding to the first bandwidth part. Correspondingly, after receiving the first indication information, the terminal device determines, based on the first value, the RIV set corresponding to the first bandwidth part.

Based on the solution, compared with that the RBG size corresponding to the first BWP is determined by searching a table in the conventional technology, in this embodiment of this application, the RBG size corresponding to the first BWP may be controlled by the network device by using the first value. Therefore, the network device may adjust the RBG size corresponding to the first BWP, so that some RBGs in the first BWP are aligned with some RBGs in a second BWP, reducing occurrence of a case in which an RBG in the second BWP includes an RBG in the first BWP, further reducing generation of a resource fragment, and improving resource utilization.

Alternatively, compared with the conventional technology, in this embodiment of this application, the network device may control, by using the first value, an RIV in the RIV set corresponding to the first BWP, so that a starting VRB in a VRB set determined based on the RIV in the RIV set is aligned with a starting or ending VRB in an RBG in a second BWP, and/or an ending VRB in the VRB set is aligned with a starting or ending VRB in an RBG in the second BWP. Subsequently, the network device may indicate the RIV in the RIV set to the terminal device, so that the starting VRB and/or ending VRB in the VRB set allocated to the terminal device in the first BWP meet/meets the foregoing alignment requirements/requirement, reducing occurrence of a case in which an RBG in the second BWP includes the VRB set in the first BWP, further reducing generation of a resource fragment, and improving resource utilization.

Optionally, the network device <NUM> in this embodiment of this application is a device that enables the terminal device <NUM> to access a radio network, and may be an evolved NodeB (evolved Node B, eNB or eNodeB) in long term evolution (long term evolution, LTE), a base station in a 5th generation (5th generation, <NUM>) network or a future evolved public land mobile network (public land mobile network, PLMN), a broadband network service gateway (broadband network gateway, BNG), a convergence switch, or a non-3rd generation partnership project (3rd generation partnership project, 3GPP) access device. Alternatively, the network device <NUM> in this embodiment of this application may be a radio controller in a cloud radio access network (cloud radio access network, CRAN), a transmission and reception point (transmission and reception point, TRP), a device including a TRP, or the like. This is not specifically limited in this embodiment of this application. Optionally, the base station in this embodiment of this application may include various forms of base stations, such as a macro base station, a micro base station (also referred to as a small cell), a relay station, and an access point. This is not specifically limited in this embodiment of this application.

In a possible manner, the network device <NUM> in this embodiment of this application may alternatively be a central unit (central unit, CU) or a distributed unit (distributed unit, DU), or the network device may include a CU and a DU. A plurality of DUs may share one CU. One DU may be alternatively connected to a plurality of CUs. It may be understood that the base station is divided into the CU and the DU from the perspective of a logical function. The CU and the DU may be physically separate from each other, or may be deployed together. This is not specifically limited in this embodiment of this application. The CU and the DU may be connected through an interface, for example, an F1 interface. The CU and the DU may be determined based on protocol layers of a radio network. For example, functions of an RRC protocol layer, a service data adaptation protocol stack (service data adaptation protocol, SDAP) protocol layer, and a packet data convergence protocol (packet data convergence protocol, PDCP) protocol layer are set in the CU, while functions of a radio link control (radio link control, RLC) protocol layer, a media access control (media access control, MAC) protocol layer, a physical (physical, PHY) protocol layer, and the like are set in the DU.

It may be understood that processing functions of the CU and the DU being determined based on protocol layers is merely an example, and the processing functions of the CU and the DU may be alternatively determined in another manner.

For example, the CU or the DU may be determined to have more protocol layer functions. For example, the CU or the DU may alternatively have some processing functions of the protocol layers through division. In a design, some functions of the RLC layer and functions of protocol layers above the RLC layer are set in the CU, and remaining functions of the RLC layer and functions of protocol layers below the RLC layer are set in the DU. In another design, functions of the CU or the DU may be alternatively determined based on a service type or another system requirement. For example, division is performed based on a latency, a function whose processing time needs to satisfy a latency requirement is disposed on the DU, and a function whose processing time does not need to satisfy the latency requirement is disposed on the CU. In another design, the CU may alternatively have one or more functions of the core network. One or more CUs may be disposed together or separately. For example, the CUs may be disposed on a network side for ease of centralized management. The DU may have a plurality of radio frequency functions. Alternatively, the radio frequency functions may be disposed remotely.

Optionally, the CU may include a CU control plane (CU control plane, CU-CP) and a CU user plane (CU user plane, CU-UP). The CU-CP and the CU-UP may be understood as being obtained after the CU is divided from a perspective of a logical function. The CU-CP and the CU-UP may be determined based on the protocol layers of the radio network. For example, functions of the RRC protocol layer and the PDCP protocol layer that corresponds to a signaling radio bearer (signal radio bearer, SRB) are set in the CU-CP, while functions of the PDCP protocol layer corresponding to a data radio bearer (data radio bearer, DRB) are set in the CU-UP. In addition, the functions of the SDAP protocol layer may be alternatively set in the CU-UP.

Optionally, the terminal device <NUM> in this embodiment of this application may be a device configured to implement a wireless communication function, for example, a terminal or a chip that may be used in a terminal. The terminal may be user equipment (user equipment, UE), an access terminal, a terminal unit, a terminal station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a terminal agent, a terminal apparatus, or the like in an internet of things (Internet of Things, IoT), a <NUM> network, or a future evolved PLMN. The access terminal may be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device or computing device with a wireless communication function or another processing device, vehicle-mounted device, or wearable device connected to a wireless modem, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in telemedicine (remote medical), a wireless terminal in a smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), or the like. The terminal may be mobile or fixed.

Optionally, the network device <NUM> and the terminal device <NUM> in this embodiment of this application may also be referred to as communication apparatuses, which may be general-purpose devices or dedicated devices. This is not specifically limited in this embodiment of this application.

Optionally, <FIG> is a schematic diagram of structures of a network device <NUM> and a terminal device <NUM> according to an embodiment of this application.

The terminal device <NUM> includes at least one processor (in <FIG>, an example in which one processor <NUM> is included is used for description) and at least one transceiver (in <FIG>, an example in which one transceiver <NUM> is included is used for description). Optionally, the terminal device <NUM> may further include at least one memory (in <FIG>, an example in which one memory <NUM> is included is used for description), at least one output device (in <FIG>, an example in which one output device <NUM> is included is used for description), and at least one input device (in <FIG>, an example in which one input device <NUM> is included is used for description).

The processor <NUM>, the memory <NUM>, and the transceiver <NUM> are connected to each other by a communication line. The communication line may include a path, which transports information between the components.

The processor <NUM> may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (application-specific integrated circuit, ASIC), or one or more integrated circuits configured to control program execution of the solutions in this application. In specific implementation, in an embodiment, the processor <NUM> may alternatively include a plurality of CPUs. The processor <NUM> may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor herein may refer to one or more devices, circuits, and/or processing cores configured to process data (for example, computer program instructions).

The memory <NUM> may be an apparatus with a storage function. For example, the memory <NUM> may be a read-only memory (read-only memory, ROM) or another type of static storage device that can store static information and instructions, or a random access memory (random access memory, RAM) or another type of dynamic storage device that can store information and instructions, or may be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory, CD-ROM) or another optical disk storage, an optical disc storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, or the like), a disk storage medium or another magnetic storage device, or any other medium that can be used to carry or store expected program code in a form of instructions or a data structure and that can be accessed by a computer. However, the memory <NUM> is not limited thereto. The memory <NUM> may exist independently and is connected to the processor <NUM> by using the communication line. Alternatively, the memory <NUM> may be integrated with the processor <NUM>.

The memory <NUM> is configured to store computer-executable instructions for performing the solutions in this application, and the processor <NUM> controls execution. Specifically, the processor <NUM> is configured to execute the computer-executable instructions stored in the memory <NUM>, to implement the communication methods in embodiments of this application.

Alternatively, optionally, in this embodiment of this application, it may be that the processor <NUM> performs processing-related functions in the communication methods provided in the following embodiments of this application, and the transceiver <NUM> is responsible for communicating with another device or a communication network. This is not specifically limited in this embodiment of this application.

Optionally, the computer-executable instructions in this embodiment of this application may also be referred to as application program code or computer program code. This is not specifically limited in this embodiment of this application.

The transceiver <NUM> may use any apparatus such as a transceiver, and is configured to communicate with another device or a communication network such as an Ethernet, a radio access network (radio access network, RAN), or a wireless local area network (wireless local area networks, WLAN). The transceiver <NUM> includes a transmitter (transmitter, Tx) and a receiver (receiver, Rx).

The output device <NUM> communicates with the processor <NUM>, and may display information in a plurality of manners. For example, the output device <NUM> may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a cathode ray tube (cathode ray tube, CRT) display device, or a projector (projector).

The input device <NUM> communicates with the processor <NUM>, and may receive a user input in a plurality of manners. For example, the input device <NUM> may be a mouse, a keyboard, a touchscreen device, or a sensor device.

The network device <NUM> includes at least one processor (in <FIG>, an example in which one processor <NUM> is included is used for description), at least one transceiver (in <FIG>, an example in which one transceiver <NUM> is included is used for description), and at least one network interface (in <FIG>, an example in which one network interface <NUM> is included is used for description). Optionally, the network device <NUM> may further include at least one memory (in <FIG>, an example in which one memory <NUM> is included is used for description). The processor <NUM>, the memory <NUM>, the transceiver <NUM>, and the network interface <NUM> are connected to each other by a communication line. The network interface <NUM> is configured to be connected to a core network device by using a link (for example, an S1 interface), or to be connected to a network interface of another network device by using a wired or wireless link (for example, an X2 interface) (not shown in <FIG>). This is not specifically limited in this embodiment of this application. In addition, for relevant descriptions of the processor <NUM>, the memory <NUM>, and the transceiver <NUM>, refer to the descriptions of the processor <NUM>, the memory <NUM>, and the transceiver <NUM> in the terminal device <NUM>.

With reference to <FIG> and using an example in which the network device <NUM> shown in <FIG> interacts with any terminal device <NUM>, the following describes in detail the resource allocation methods provided in embodiments of this application.

It may be understood that in embodiments of this application, the terminal device and/or the network device may perform some or all of steps in embodiments of this application. These steps or operations are merely examples. In embodiments of this application, other operations or variations of various operations may also be performed. In addition, the steps may be performed in different orders presented in embodiments of this application, and it may not be necessary to perform all operations in embodiments of this application.

It may be understood that in embodiments of this application, interaction between the network device and the terminal device may also be applicable to interaction between a CU and a terminal device or interaction between a DU and a terminal device. It may be understood that in embodiments of this application, a mechanism of interaction between the network device and the terminal device may be appropriately modified to be applicable to interaction between a CU or DU and a terminal device.

It should be noted that names of messages between network elements, names of parameters in the messages, or the like in the following embodiments of this application are merely examples, and there may be other names during specific implementation. This is not specifically limited in embodiments of this application.

It should be noted that a BWP in the following embodiments of this application, including a first BWP, a second BWP, and a third BWP, may be a downlink BWP, and correspondingly, the resource allocation methods in this application are used for allocation of downlink resources; or the BWP may be an uplink BWP, and correspondingly, the resource allocation methods in this application are used for allocation of uplink resources.

In this embodiment of this application, an example is used for description in which a first BWP of the terminal device is currently activated and the network device allocates a resource in the first BWP to the terminal device.

The following is first described: a resource allocation method provided in an embodiment of this application for a case in which a network device uses a type <NUM> for allocation of resources in a first BWP to a terminal device. As shown in <FIG>, the resource allocation method includes the following steps.

S801: A network device determines a BWP allocated to a terminal device.

It may be understood that the network device may allocate one or more BWPs to the terminal device, and the one or more BWPs include a first BWP.

S802: The network device determines a first value.

The first value is used to indicate an RBG size corresponding to the first BWP. It may be understood that the RBG size corresponding to the first BWP is a nominal RBG size.

Optionally, the network device may determine the first value based on a nominal RBG size of a second BWP. Alternatively, the network device determines the nominal RBG size of the first BWP based on the nominal RBG size of the second BWP. The second BWP may be a currently activated BWP of another terminal device, and the network device currently also uses the type <NUM> for allocation of resources in the second BWP to the another terminal device. Alternatively, the second BWP may be an initial BWP of another terminal device. A type of the second BWP is not specifically limited in this embodiment of this application.

Optionally, there may be the following relationships between sizes of the first BWP and the second BWP.

In a possible implementation, the size of the second BWP is greater than the size of the first BWP, and the second BWP includes at least one part of the first BWP. For example, the second BWP includes all PRBs in the first BWP, that is, the first BWP is included in the second BWP. Alternatively, the second BWP includes some PRBs in the first BWP but does not include other PRBs in the first BWP, that is, the first BWP and the second BWP overlap. In this case, the terminal device with the first BWP currently activated may be understood as a narrowband terminal, and another terminal device with the second BWP currently activated may be understood as a wideband terminal. Optionally, the first value may be equal to the nominal RBG size corresponding to the second BWP. Alternatively, the first value may be equal to N times the nominal RBG size corresponding to the second BWP, where N is a positive integer greater than <NUM>.

For example, the size of the second BWP is <NUM> PRBs, the size of the first BWP is <NUM> PRBs, and the first value is equal to the RBG size corresponding to the second BWP. It is assumed that a configuration <NUM> is used. The network device may determine according to Table <NUM> that the nominal RBG size corresponding to the second BWP is <NUM>. In this case, the network device may determine the first value as <NUM>, that is, the network device determines that the nominal RBG size corresponding to the first BWP is also <NUM>.

In another possible implementation, the size of the second BWP is less than the size of the first BWP, and the first BWP includes at least one part of the second BWP. For example, the first BWP includes all PRBs in the second BWP, that is, the second BWP is included in the first BWP. Alternatively, the first BWP includes some PRBs in the second BWP but does not include other PRBs in the second BWP, that is, the first BWP and the second BWP overlap. In this case, the terminal device with the first BWP currently activated may be understood as a wideband terminal, and another terminal device with the second BWP currently activated may be understood as a narrowband terminal.

Optionally, the first value may be equal to the nominal RBG size corresponding to the second BWP. Alternatively, the first value may be equal to <NUM>/N times the nominal RBG size corresponding to the second BWP, where N is a positive integer greater than <NUM>.

In the following embodiment of this application, an example is used for description in which the size of the second BWP is greater than the size of the first BWP. It may be understood that the method in the following embodiment is also applicable when the size of the second BWP is less than the size of the first BWP.

Optionally, in step S801 described above, the BWP that the network device determines to allocate to the terminal device may further include a third BWP. That is, the network device may allocate a plurality of BWPs to the terminal device.

In an implementation scenario of this case, the network device may determine an RBG size corresponding to the third BWP to be the same as the RBG size corresponding to the first BWP. In this case, the first value may be further used to indicate the RBG size corresponding to the third BWP. That is, a plurality of BWPs (or a group of BWPs) of the terminal device correspond to one first value, or RBG sizes corresponding to a plurality of BWPs are configured by using the first value.

For example, it is assumed that the network device allocates four BWPs to the terminal device, namely, a BWP0, a BWP1, a BWP2, and a BWP3. If the first BWP is the BWP0 and the third BWP is the BWP1, the BWP2, and the BWP3, the first value may indicate RBG sizes corresponding to the BWP0 to the BWP3. Alternatively, if the first BWP is the BWP0 and the third BWP is the BWP1, the first value may indicate RBG sizes corresponding to the BWP0 and the BWP1. For RBG sizes corresponding to the BWP2 and the BWP3, the network device may indicate the RBG sizes by using a second value.

In other words, for a plurality of BWPs of the terminal device, the network device can indicate, by using one value, RBG sizes corresponding to the plurality of BWPs, reducing signaling overheads used for indicating, to the terminal device, the RBG sizes corresponding to the plurality of BWPs.

In another implementation scenario of this case, the network device may determine an RBG size corresponding to the third BWP to be different from the RBG size corresponding to the first BWP. In other words, the network device may configure a separate RBG size for each BWP.

For example, it is assumed that the network device allocates four BWPs to the terminal device, namely, a BWP0, a BWP1, a BWP2, and a BWP3. If the first BWP is the BWP0, the network device may configure an RBG size corresponding to the BWP0 to be the first value, configure an RBG size corresponding to the BWP1 to be a second value, configure an RBG size corresponding to the BWP2 to be a third value, and configure an RBG size corresponding to the BWP3 to be a fourth value.

In other words, for a plurality of BWPs of the terminal device, the network device may indicate, by using a plurality of values, RBG sizes corresponding to the plurality of BWPs, improving flexibility of configuration.

S803: The network device sends first indication information to the terminal device. Correspondingly, the terminal device receives the first indication information from the network device.

The first indication information is used to indicate the first value.

Optionally, the network device may send the first indication information to the terminal device in different manners.

In a possible implementation, the network device may send the first indication information to the terminal device by using higher layer signaling. For example, the network device may send a system message to the terminal device, where the system message includes the first indication information; or the network device may send radio resource control (radio resource control, RRC) signaling to the terminal device, where the RRC signaling includes the first indication information; or the network device may send a media access control control element (media access control control element, MAC CE) to the terminal device, where the MAC CE includes the first indication information.

In another possible implementation, the network device may send the first indication information to the terminal device by using physical layer signaling. For example, the network device may send downlink control information (downlink control information, DCI) to the terminal device, where the DCI includes the first indication information.

S804: The terminal device determines the BWP allocated by the network device to the terminal device.

It may be understood that the BWP allocated by the network device to the terminal device may include one or more BWPs, and the one or more BWPs include the first BWP.

It should be noted that step S804 and steps S802 and S803 are not necessarily performed in a particular order. Step S804 may be performed first, and then steps S802 and S803 are performed; or steps S802 and S803 may be performed first, and then step S804 is performed; or step S804 and steps S802 and S803 may be performed simultaneously.

S805: The terminal device determines, based on the first value, the RBG size corresponding to the first BWP.

Optionally, the terminal device may determine the first value as the RBG size corresponding to the first BWP.

Optionally, after determining the RBG size corresponding to the first BWP, the terminal device may determine RBGs in the first BWP by using the method described in the type <NUM> above.

For example, the size of the first BWP is <NUM> PRBs, the first value is <NUM>, and a number <MAT> of a CRB corresponding to a starting PRB in the first BWP is <NUM>. The terminal device may determine the RBG size of the first BWP as <NUM>. Then, the terminal device determines a quantity of RBGs in the first BWP, a size of a first RBG, and a size of a last RBG. For example,
the total quantity of RBGs in the first BWP: <MAT>.

For example, if the size of the second BWP is <NUM> PRBs and the configuration <NUM> is used, it can be obtained according to Table <NUM> that the RBG size corresponding to the second BWP is <NUM>. Assuming that a number <MAT> of a CRB corresponding to a starting PRB in the second BWP is <NUM>, RBGs in the second BWP that are determined by using the method described in the type <NUM> above may be as follows:
a total quantity of RBGs: <MAT>.

Based on the foregoing examples, the first BWP and the second BWP may be shown in <FIG>. It may be understood that <FIG> shows only some RBGs in the second BWP. It can be learned from <FIG> that a head and a tail of the RBG#<NUM> in the first BWP are aligned with a head and a tail of an RBG#<NUM> in the second BWP, respectively. Therefore, when the network device schedules the RBG#<NUM> in the first BWP to the terminal device, there is no resource fragment in the RBG#<NUM> in the second BWP.

It may be understood that if the configuration <NUM> is used, the RBG size that corresponds to the first BWP and that is determined based on Table <NUM> described above is <NUM>. When RBGs in the first BWP are determined based on the size, the RBG#<NUM> in the second BWP include a plurality of RBGs in the first BWP. As a result, when the network device allocates any one or more RBGs of the plurality of RBGs to the terminal device, there is a resource fragment in the RBG#<NUM> in the second BWP, causing a waste of resources.

Optionally, when the network device indicates, by using one value, RBG sizes corresponding to a plurality of BWPs, the terminal device may determine the RBG sizes corresponding to the plurality of BWPs after receiving the first indication information. For example, when the first value is further used to indicate the RBG size corresponding to the third BWP, the terminal device further determines, based on the first value, the RBG size corresponding to the third BWP. For details, refer to the relevant description of the first BWP. When the network device indicates, by using a plurality of values, RBG sizes corresponding to a plurality of BWPs, the network device may further send, to the terminal device, RBG sizes corresponding to other BWPs other than the first BWP.

According to the foregoing solution, compared with that the RBG size corresponding to the first BWP is determined by searching a table in the conventional technology, in this embodiment of this application, the RBG size corresponding to the first BWP may be controlled by the network device. The network device may flexibly adjust the RBG size corresponding to the first BWP, so that some RBGs in the first BWP are aligned with some RBGs in the second BWP, reducing occurrence of a case in which an RBG in the second BWP includes an RBG in the first BWP, further reducing generation of a resource fragment, and improving resource utilization.

Optionally, as shown in <FIG>, the resource allocation method may further include the following step.

S806: The network device sends second indication information to the terminal device. Correspondingly, the terminal device receives the second indication information from the network device.

The second indication information is used to indicate a first RBG. The first RBG is an RBG allocated to the terminal device in the first BWP.

Optionally, the second indication information is carried by a first field, and a bit quantity of the first field is determined based on the first value. For example, the bit quantity of the first field is the same as the total quantity that is of the RBGs in the first BWP and that is determined based on the first value.

Based on the example shown in <FIG>, the bit quantity of the first field may be <NUM>. If the network device allocates the RBG#<NUM> in the first BWP to the terminal device, that is, the first RBG is the RBG#<NUM> in the first BWP, the second indication information may be "<NUM>".

Based on the solution, compared with the conventional technology, because the RBG size corresponding to the first BWP increases, the total RBG quantity of the first BWP decreases, and therefore, the bit quantity of the first field decreases accordingly, reducing signaling overheads.

Optionally, the network device may send the second indication information to the terminal device by using the DCI. In other words, the network device sends the DCI to the terminal device, where the DCI includes the second indication information.

It should be noted that step S805 and step S806 are not necessarily performed in a particular order. Step S805 may be performed first, and then step S806 is performed; or step S806 may be performed first, and then step S805 is performed; or step S805 and step S806 may be performed simultaneously.

S807: The terminal device determines, based on the second indication information, the RBG allocated to the terminal device.

Optionally, the terminal device determines the first RBG indicated by the second indication information as the RBG allocated to the terminal device in the first BWP.

For example, based on the example shown in <FIG>, if the second indication information is "<NUM>", the first RBG is the RBG#<NUM> in the first BWP. In this case, the terminal device determines the RBG#<NUM> in the first BWP as the RBG allocated by the network device to the terminal device.

At this point, the terminal device can determine, according to the method provided in this embodiment of this application, a resource allocated by the network device to the terminal device, and therefore, can use the resource for transmission.

In the foregoing embodiment, the method is provided that the network device indicates, to the terminal device, the RBG size corresponding to the first BWP. In another implementation scenario of this application, the network device may not indicate, to the terminal device, the RBG size corresponding to the first BWP. In this case, the RBG size corresponding to the first BWP may be a preset value or a value agreed on in a protocol. For example, when the size of the second BWP is greater than the size of the first BWP, the preset value or agreed value is equal to a maximum value of P in Table <NUM>, that is, the RBG size corresponding to the first BWP is <NUM>. Alternatively, when the size of the second BWP is less than the size of the first BWP, the preset value or agreed value is equal to a minimum value of P in Table <NUM>, that is, the RBG size corresponding to the first BWP is <NUM>.

The following describes a resource allocation method provided in an embodiment of this application for a case in which a network device uses a type <NUM> for allocation of resources in a first BWP to a terminal device. As shown in <FIG>, the resource allocation method includes the following steps.

S1001: A network device determines a BWP allocated to a terminal device.

Step S1001 is the same as step S801 in the embodiment shown in <FIG> described above. For details, refer to the relevant description in S801 described above.

S1002: The network device determines a first value.

The first value is used to determine an RIV set corresponding to the first BWP.

Optionally, when a size of a second BWP is greater than a size of the first BWP, and the second BWP includes at least one part of the first BWP, the first value may be equal to a nominal RBG size corresponding to the second BWP. Alternatively, the first value may be equal to N times the nominal RBG size corresponding to the second BWP. When a size of a second BWP is less than a size of the first BWP, and the first BWP includes at least one part of the second BWP, the first value may be equal to a nominal RBG size corresponding to the second BWP. Alternatively, the first value may be equal to <NUM>/N times the nominal RBG size corresponding to the second BWP, where N is a positive integer greater than <NUM>. For a relevant description, refer to step S802 described above.

Optionally, a VRB set determined based on an RIV in the RIV set meets one or more of the following: <MAT> where K is the first value, RBstart is an index value of a starting VRB in the VRB set, LRBs is a quantity of VRBs included in the VRB set, and <MAT> is a number of a CRB corresponding to a starting PRB in the first BWP.

It should be noted that the VRB set may include one or more VRBs. When the VRB set includes a plurality of VRBs, the plurality of VRBs are contiguous.

It may be understood that when the first value is equal to the nominal RBG size corresponding to the second BWP or is equal to N times the nominal RBG size, the starting VRB included in the VRB set in the first BWP can be controlled, by using <MAT>, to be aligned with a starting or ending VRB in an RBG in the second BWP, and an ending VRB included in the VRB set can be controlled, by using <MAT>, to be aligned with a starting or ending VRB in an RBG in the second BWP.

For example, the size of the second BWP is <NUM> PRBs, a number <MAT> of a CRB corresponding to a starting PRB in the second BWP is <NUM>, the size of the first BWP is <NUM> PRBs, the number <MAT> of the CRB corresponding to the starting PRB in the first BWP is <NUM>, and the first value is equal to an RBG size corresponding to the second BWP. It is assumed that a configuration <NUM> is used. The network device may determine according to Table <NUM> that the nominal RBG size corresponding to the second BWP is <NUM>. In this case, the network device may determine the first value as <NUM>. Correspondingly, an index of the starting VRB in the VRB set meets (<NUM> + RBstart) mod <NUM> = <NUM>. For example, the index of the starting VRB is <NUM> or <NUM>. Alternatively, the index of the starting VRB and the quantity of VRBs in the VRB set meet (<NUM> + RBstart + LRBs) mod <NUM> = <NUM>. For example, the index of the starting VRB is <NUM>, and the quantity of VRBs is <NUM>, or the index of the starting VRB is <NUM>, and the quantity of VRBs is <NUM>.

For example, the index of the starting VRB in the VRB set meets (<NUM> + RBstart)mod16 = <NUM>, the index of the starting VRB is <NUM>, and the quantity of VRBs is, for example, <NUM>. As shown in <FIG>, the starting VRB included in the VRB set that is allocated to the terminal device and that is in the first BWP is aligned with a starting VRB in an RBG#<NUM> in the second BWP. Alternatively, for example, the index of the starting VRB and the quantity of VRBs in the VRB set meet (<NUM> + RBstart + LRBs) mod <NUM> = <NUM> , the index of the starting VRB is <NUM>, and the quantity of VRBs is <NUM>. As shown in <FIG>, the ending VRB included in the VRB set that is allocated to the terminal device and that is in the first BWP is aligned with an ending VRB in an RBG#<NUM> in the second BWP. Alternatively, for example, the index of the starting VRB in the VRB set meets (<NUM> + RBstart) mod <NUM> = <NUM> , and the index of the starting VRB and the quantity of VRBs meet (<NUM> + RBstart + LRBs) mod <NUM> = <NUM>. For example, the index of the starting VRB is <NUM>, and the quantity of VRBs is <NUM>. As shown in <FIG>, the starting VRB included in the VRB set that is allocated to the terminal device and that is in the first BWP is aligned with a starting VRB in an RBG#<NUM> in the second BWP, and the ending VRB in the VRB set is aligned with an ending VRB in an RBG#<NUM> in the second BWP.

Optionally, after determining the first value, because the network device can determine a quantity of PRBs included in the first BWP and an index of the CRB corresponding to the starting PRB in the first BWP, the network device may traverse various possible starting VRBs and quantities of contiguous VRBs in the first BWP, to determine RBstart and LRBs that meet the foregoing formulas, and then determine the RIV set based on RBstart and LRBs.

Optionally, it is assumed that the RIV set includes M RIVs. The network device may number the RIVs in order of RIV value. For example, the RIVs are numbered <NUM>, <NUM>, <NUM>,. , and M-<NUM> sequentially in ascending order.

Optionally, in step S1001 described above, the BWP that the network device determines to allocate to the terminal device may further include a third BWP. That is, the network device may allocate a plurality of BWPs to the terminal device.

In an implementation scenario of this case, the network device may determine that an RIV set corresponding to the third BWP is also determined based on the first value. In this case, the first value may be further used to determine the RIV set corresponding to the third BWP.

In other words, for a plurality of BWPs of the terminal device, the network device may indicate, by using one value, RIV sets corresponding to the plurality of BWPs, with no need to separately send, to the terminal device, values used for determining the RIV sets corresponding to the BWPs, further reducing signaling overheads.

In another implementation scenario of this case, the network device may determine that an RIV set corresponding to the third BWP is determined based on a second value.

In other words, the network device may configure different values for different BWPs to determine RIV sets corresponding to different BWPs, improving flexibility of configuration.

It should be noted that a method for determining the RIV set corresponding to the third BWP is similar to the method for determining the RIV set corresponding to the first BWP, and a difference lies in that when the RIV set corresponding to the third BWP is determined, the number of the CRB corresponding to the starting PRB in the first BWP in the foregoing formulas needs to be replaced with a number of a CRB corresponding to a starting PRB in the third BWP.

S1003: The network device sends first indication information to the terminal device. Correspondingly, the terminal device receives the first indication information from the network device.

Step S1003 is the same as step S803 in the embodiment shown in <FIG> described above. For details, refer to the relevant description in S803 described above.

S1004: The terminal device determines the BWP allocated by the network device to the terminal device.

Step S1004 is the same as step S804 in the embodiment shown in <FIG> described above. For details, refer to the relevant description in S804 described above.

S1005: The terminal device determines, based on the first value, the RIV set corresponding to the first BWP.

It may be understood that a method that the terminal device determines the RIV set corresponding to the first BWP is the same as the method that the network device determines the RIV set corresponding to the first BWP. For details, refer to the relevant description in step S1002 described above.

Optionally, after determining the RIVs included in the RIV set, the terminal device may number the RIVs by using a same rule as that used by the network device. For example, the RIVs are numbered <NUM>, <NUM>, <NUM>,. , and M-<NUM> sequentially in ascending order.

Optionally, when the first value is further used to determine the RIV set corresponding to the third BWP, the terminal device further determines, based on the first value, the RIV set corresponding to the third BWP.

According to the foregoing solution, compared with the conventional technology, in this embodiment of this application, the network device may control, by using the first value, an RIV in the RIV set corresponding to the first BWP, so that a starting VRB in a VRB set determined based on the RIV in the RIV set is aligned with a starting or ending VRB in an RBG in the second BWP, and/or an ending VRB in the VRB set is aligned with a starting or ending VRB in an RBG in the second BWP. Subsequently, the network device may indicate the RIV in the RIV set to the terminal device, so that the starting VRB and/or ending VRB in the VRB set allocated to the terminal device in the first BWP meet/meets the foregoing alignment requirements/requirement, reducing occurrence of a case in which an RBG in the second BWP includes the VRB set in the first BWP, further reducing generation of a resource fragment, and improving resource utilization.

S1006: The network device sends second indication information to the terminal device. Correspondingly, the terminal device receives the second indication information from the network device.

The second indication information is used to indicate a first RIV. The first RIV is used to determine a virtual resource block VRB set that is allocated to the terminal device and that is in the first BWP.

Optionally, the second indication information may be a number or index of the first RIV.

Optionally, the second indication information is carried by a first field, and a bit quantity of the first field is determined based on the first value. For example, the bit quantity of the first field meets <MAT>, where M is a total quantity of RIVs included in the RIV set corresponding to the first BWP, and M is determined based on the first value.

Based on the solution, because the RIVs included in the RIV set meet a condition in step S1002, compared with the conventional technology, a quantity of possible RIV values decreases, and therefore, a quantity of bits required to carry RIVs decreases accordingly, reducing signaling overheads.

Optionally, the network device may send the second indication information to the terminal device by using DCI. In other words, the network device sends the DCI to the terminal device, where the DCI includes the second indication information.

It should be noted that step S1005 and step S1006 are not necessarily performed in a particular order. Step S1005 may be performed first, and then step S1006 is performed; or step S1006 may be performed first, and then step S1005 is performed; or step S1005 and step S1006 may be performed simultaneously.

S1007: The terminal device determines, based on the second indication information, the VRB set allocated to the terminal device.

Optionally, the terminal device may determine, based on the RIV set corresponding to the first BWP and the second indication information, the VRB set corresponding to the first RIV indicated by the second indication information, as the VRB set that is allocated to the terminal device and that is in the first BWP.

For example, if the second indication information indicates the index of the first RIV, the terminal device may search, based on the index, the RIV set corresponding to the first BWP for a value of the first RIV. Then, the terminal device determines, based on the first RIV, a VRB set corresponding to the first RIV, and determines the VRB set as the VRB set that is allocated to the terminal device and that is in the first BWP. For a method that the terminal device determines, based on the first RIV, a VRB set corresponding to the first RIV, refer to the manner in a type <NUM> described above.

It may be understood that the foregoing methods may be applicable to a scenario in which the first BWP and the second BWP overlap, but the scenario shall not constitute any limitation on this application. This application may also be applicable to other scenarios, for example, may also be applicable to a scenario in which the first BWP and the second BWP do not overlap and/or a scenario in which a relationship between sizes of the first BWP and the second BWP is not limited, and is used to improve flexibility of resource allocation in the scenarios.

In the embodiment shown in <FIG> or <FIG> described above, actions of the network device may be performed by the network device <NUM> shown in <FIG>, where the processor <NUM> in the network device <NUM> invokes the application program code stored in the memory <NUM> to instruct the network device to perform the actions. In the embodiment shown in <FIG> or <FIG> described above, actions of the terminal device may be performed by the terminal device <NUM> shown in <FIG>, where the processor <NUM> in the terminal device <NUM> invokes the application program code stored in the memory <NUM> to instruct the terminal device to perform the actions. This is not limited in this embodiment.

In embodiments of this application, if there is no special description or a logical conflict, terms and/or descriptions in different embodiments are consistent and may be referenced to each other. Technical features in different embodiments may be combined to form a new embodiment based on an intrinsic logical relationship between the technical features.

It may be understood that in the foregoing embodiments, the methods and/or steps implemented by the terminal device may be alternatively implemented by a component (for example, a chip or a circuit) that may be used in the terminal device, and the methods and/or steps implemented by the network device may be alternatively implemented by a component that may be used in the network device.

The foregoing mainly describes the solutions provided in embodiments of this application from the perspective of interaction between network elements. Correspondingly, an embodiment of this application further provides a communication apparatus. The communication apparatus is configured to implement the foregoing methods. The communication apparatus may be the terminal device in the foregoing method embodiments, or an apparatus including the terminal device, or a component that may be used in the terminal device. Alternatively, the communication apparatus may be the network device in the foregoing method embodiments, or an apparatus including the network device, or a component that may be used in the network device. It may be understood that, to implement the foregoing functions, the communication apparatus includes a corresponding hardware structure and/or software module for performing the functions. A person skilled in the art should be easily aware that units, algorithms, and steps in the examples described with reference to the embodiments disclosed in this specification can be implemented in a form of hardware or a combination of hardware and computer software in this application. Whether a function is performed by hardware or hardware driven by computer software depends on a particular application and a design constraint of the technical solutions.

In this embodiment of this application, the communication apparatus may be divided into functional modules based on the foregoing method embodiments. For example, each functional module may be obtained through division based on each corresponding function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software functional module. It should be noted that, in embodiments of this application, division into the modules is an example and is merely logical function division, and may be other division in an actual implementation.

For example, the communication apparatus is the network device in the foregoing method embodiments. <FIG> is a schematic diagram of a structure of a network device <NUM>. The network device <NUM> includes a processing module <NUM> and a transceiver module <NUM>. The transceiver module <NUM> may also be referred to as a transceiver unit, is configured to implement a transmission function and/or a reception function, and may be, for example, a transceiver circuit, a transceiver, or a communication interface.

The processing module <NUM> is configured to determine a bandwidth part allocated to a terminal device, where the bandwidth part includes a first bandwidth part. The processing module <NUM> is further configured to determine a first value, where the first value is used to indicate a resource block group RBG size corresponding to the first bandwidth part, or the first value is used to determine a resource indication value RIV set corresponding to the first bandwidth part. The transceiver module <NUM> is configured to send first indication information to the terminal device, where the first indication information is used to indicate the first value.

Optionally, the transceiver module <NUM> is further configured to send second indication information to the terminal device. When the first value is used to indicate the RBG size corresponding to the first bandwidth part, the second indication information is used to indicate a first RBG, where the first RBG is an RBG that is allocated to the terminal device and that is in the first bandwidth part. When the first value is used to determine the RIV set corresponding to the first bandwidth part, the second indication information is used to indicate a first RIV in the RIV set, where the first RIV is used to determine a virtual resource block VRB set that is allocated to the terminal device and that is in the first bandwidth part.

Optionally, that the transceiver module <NUM> is configured to send first indication information to the terminal device may include: The transceiver module <NUM> is configured to send a system message to the terminal device, where the system message includes the first indication information; or.

All related content of the steps in the method embodiments may be cited in function descriptions of corresponding functional modules.

In this embodiment, the network device <NUM> is presented in a form of obtaining each functional module through division in an integrated manner. The "module" herein may be a specific ASIC, a circuit, a processor and a memory that execute one or more software or firmware programs, an integrated logic circuit, and/or another component that can provide the foregoing functions. In a simple embodiment, a person skilled in the art may figure out that the network device <NUM> may be in a form of the network device <NUM> shown in <FIG>.

For example, the processor <NUM> in the network device <NUM> shown in <FIG> may invoke the computer-executable instructions stored in the memory <NUM>, so that the network device <NUM> performs the resource allocation methods in the foregoing method embodiments.

Specifically, functions/implementation processes of the processing module <NUM> and the transceiver module <NUM> in <FIG> may be implemented by the processor <NUM> in the network device <NUM> shown in <FIG> invoking the computer-executable instructions stored in the memory <NUM>. Alternatively, a function/implementation process of the processing module <NUM> in <FIG> may be implemented by the processor <NUM> in the network device <NUM> shown in <FIG> invoking the computer-executable instructions stored in the memory <NUM>, and a function/implementation process of the transceiver module <NUM> in <FIG> may be implemented by the transceiver <NUM> in the network device <NUM> shown in <FIG>.

Because the network device <NUM> provided in this embodiment may perform the foregoing resource allocation methods, for technical effects that can be obtained by the network device <NUM>, refer to the foregoing method embodiments.

Alternatively, for example, the communication apparatus is the terminal device in the foregoing method embodiments. <FIG> is a schematic diagram of a structure of a terminal device <NUM>. The terminal device <NUM> includes a processing module <NUM> and a transceiver module <NUM>. The transceiver module <NUM> may also be referred to as a transceiver unit, is configured to implement a transmission function and/or a reception function, and may be, for example, a transceiver circuit, a transceiver, a transceiver, or a communication interface.

The processing module <NUM> is configured to determine a bandwidth part allocated by a network device to the terminal device, where the bandwidth part includes a first bandwidth part. The transceiver module <NUM> is configured to receive first indication information from the network device, where the first indication information is used to indicate a first value. The processing module <NUM> is further configured to determine, based on the first value, a resource block group RBG size corresponding to the first bandwidth part. Alternatively, the processing module <NUM> is further configured to determine, based on the first value, a resource indication value RIV set corresponding to the first bandwidth part.

Optionally, the transceiver module <NUM> is further configured to receive second indication information from the network device. The processing module <NUM> is further configured to determine, based on the RBG size corresponding to the first bandwidth part and the second indication information, a first RBG indicated by the second indication information as an RBG that is allocated to the terminal device and that is in the first bandwidth part. Alternatively, the processing module <NUM> is further configured to determine, based on the RIV set corresponding to the first bandwidth part and the second indication information, a VRB set corresponding to a first RIV that is indicated by the second indication information, as a VRB set that is allocated to the terminal device and that is in the first bandwidth part.

Optionally, the processing module <NUM> is further configured to determine, based on the first value, an RBG size corresponding to a third bandwidth part. Alternatively, the processing module <NUM> is further configured to determine, based on the first value, an RIV set corresponding to a third bandwidth part.

Optionally, that the transceiver module <NUM> is configured to receive first indication information from the network device may include: The transceiver module <NUM> is configured to receive a system message from the network device, where the system message includes the first indication information; or.

In this embodiment, the terminal device <NUM> is presented in a form of obtaining each functional module through division in an integrated manner. The "module" herein may be a specific ASIC, a circuit, a processor and a memory that execute one or more software or firmware programs, an integrated logic circuit, and/or another component that can provide the foregoing functions. In a simple embodiment, a person skilled in the art may figure out that the terminal device <NUM> may be in a form of the terminal device <NUM> shown in <FIG>.

For example, the processor <NUM> in the terminal device <NUM> shown in <FIG> may invoke the computer-executable instructions stored in the memory <NUM>, so that the terminal device <NUM> performs the resource allocation methods in the foregoing method embodiments.

Specifically, functions/implementation processes of the processing module <NUM> and the transceiver module <NUM> in <FIG> may be implemented by the processor <NUM> in the terminal device <NUM> shown in <FIG> invoking the computer-executable instructions stored in the memory <NUM>. Alternatively, a function/implementation process of the processing module <NUM> in <FIG> may be implemented by the processor <NUM> in the terminal device <NUM> shown in <FIG> invoking the computer-executable instructions stored in the memory <NUM>, and a function/implementation process of the transceiver module <NUM> in <FIG> may be implemented by the transceiver <NUM> in the terminal device <NUM> shown in <FIG>.

Because the terminal device <NUM> provided in this embodiment may perform the foregoing resource allocation methods, for technical effects that can be obtained by the terminal device <NUM>, refer to the foregoing method embodiments.

Optionally, an embodiment of this application further provides a communication apparatus (for example, the communication apparatus may be a chip or a chip system). The communication apparatus includes a processor, configured to implement the method in any one of the foregoing method embodiments. In a possible design, the communication apparatus further includes a memory. The memory is configured to store necessary program instructions and necessary data. The processor may invoke program code stored in the memory, to indicate the communication apparatus to perform the method in any one of the foregoing method embodiments. Certainly, the communication apparatus may not include a memory. In another possible design, the communication apparatus further includes an interface circuit. The interface circuit is a code/data read-write interface circuit. The interface circuit is configured to receive computer-executable instructions (the computer-executable instructions are stored in a memory, and may be read directly from the memory or by using another device) and transmit the computer-executable instructions to the processor. When the communication apparatus is a chip system, the communication apparatus may include a chip, or may include a chip and another discrete component. This is not specifically limited in this embodiment of this application.

Claim 1:
A resource allocation method, wherein the method comprises:
determining (S801, S1001), by a network device (<NUM>), a bandwidth part allocated to a terminal device (<NUM>), wherein the bandwidth part comprises a first bandwidth part;
determining (S802, S1002), by the network device, a first value, wherein the first value is used to indicate a resource block group, RBG, size corresponding to the first bandwidth part, or the first value is used to determine a resource indication value, RIV, set corresponding to the first bandwidth part; and
sending (S803, S1003), by the network device, first indication information to the terminal device, wherein the first indication information is used to indicate the first value;
characterized in that:
when the first value is used to indicate a RBG size, the network device determines the first value based on a nominal RBG size of a second bandwidth part so that some RBGs in the first bandwidth part are aligned with some RBGs in the second bandwidth part; or
when the first value is used to determine a RIV set, the network device determines the first value so that a starting VRB in a VRB set determined based on a RIV in the RIV set is aligned with a starting or ending VRB in an RBG in the second BWP and/or an ending VRB in the VRB set is aligned with a starting or ending VRB in an RBG in the second BWP.