Logical channel grouping method and communication device

Abstract

This application provides a logical channel grouping method and a communication device, which relate to the field of wireless communication technologies. This application can improve uplink scheduling efficiency and uplink capacity. The method includes: a terminal device determines that buffered data to be reported exists on a first logical channel (LCH); and sends a buffer status report (BSR) to a network device based on the buffered data to be reported on the first LCH according to a preset configuration rule. The BSR indicates a first amount of data and a first logical channel group (LCG), where the first amount of data corresponds to a first LCG, the first amount of data includes a data amount of the first data, the buffered data includes the first data, and the first LCG is one of the LCGs configured for the first LCH. The remaining packet delay budget (PDB) of the first data is within a first remaining PDB range, or the priority level of the first data is within a first priority level range, and the priority level of the first data is determined based on the remaining PDB of the first data and a data type of the first data.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to Chinese Patent Application No. 202211277641.2, entitled "LOGICAL CHANNEL GROUPING METHOD, TERMINAL DEVICE, NETWORK DEVICE, AND APPARATUS," filed with the State Intellectual Property Office of China on October 19, 2022, and Chinese Patent Application No. 202211372394.4, entitled "LOGICAL CHANNEL GROUPING METHOD AND COMMUNICATION APPARATUS," filed with the State Intellectual Property Office of China on November 3, 2022, the entire contents of both of which are incorporated herein by reference.

[0002] [Technical field] This application relates to the field of wireless communications, and in particular to a logical channel grouping method and a communication device. [Background technology]

[0003] In a communication system, when a terminal device needs to transmit uplink data, the terminal device first sends a buffer status report (BSR) to a network device, where the BSR indicates the amount of buffered data to be transmitted by the terminal device, and the network device allocates a corresponding amount of uplink resources to the terminal device based on the amount of buffered data indicated by the BSR. In the BSR reporting mechanism, reporting is performed at the granularity of a logical channel group (LCG).

[0004] However, in extended reality (XR) services, different packets in one data burst correspond to the same packet delay budget (PDB), and packets in different data bursts correspond to different PDBs. The buffered data of an LCG may include packets in different data bursts, and a network device may allocate uplink resources beyond the PDB for a packet (or some packets). As a result, packet scheduling fails, uplink scheduling efficiency is reduced, and uplink capacity is low. Summary of the Invention

[0005] This application provides a logical channel grouping method and a communication device for improving uplink scheduling efficiency and uplink capacity. To achieve the above objectives, this application uses the following technical solutions:

[0006] According to a first aspect, a logical channel grouping method is provided. The method may be executed by a terminal device or a chip used in the terminal device. For the sake of explanation, the following uses an example in which the method is executed by the terminal device. The method includes: the terminal device determines that buffered data to be reported exists on a first logical channel (LCH); then, the terminal device sends a buffer status report (BSR) to a network device based on the buffered data to be reported on the first LCH according to a preset configuration rule; the BSR indicates a first amount of data and a first logical channel group (LCG), where the first amount of data corresponds to the first LCG, the first amount of data includes a data amount of the first data, the buffered data includes the first data, and the first LCG is one of the LCGs configured for the first LCH.

[0007] If possible, the remaining packet delay budget PDB of the first data is within the first remaining PDB range. The configuration rule is configuration rule 1, i.e., includes L LCGs and L remaining PDB ranges, where the L LCGs include the first LCG, the L remaining PDB ranges include the first remaining PDB range, and the first LCG is associated with the first remaining PDB range, where L is a positive integer greater than or equal to 2.

[0008] In other possible cases, the priority level of the first data is within the first priority level range, and the priority level of the first data is determined based on the remaining PDB of the first data and the data type of the first data. The configuration rule includes configuration rule 2, i.e., L LCGs and L priority level ranges, where the L LCGs include the first LCG, the L priority level ranges include the first priority level range, and the first LCG is associated with the first priority level range, and L is a positive integer greater than or equal to 2.

[0009] In other words, when the BSR indicates a first amount of data and a first LCG, and the first LCG is associated with a first remaining PDB range according to preset configuration rule 1, the network device allocates uplink resources to the terminal device based on the first remaining PDB range and the first amount of data. For example, when the remaining PDB corresponding to the first remaining PDB range is small, the network device may preferentially allocate uplink resources to data corresponding to the first amount of data. Alternatively, when the remaining PDB corresponding to the first remaining PDB range is large and transmission resources are insufficient, the network device may later allocate uplink resources to data corresponding to the first amount of data and preferentially allocate uplink resources to other terminal devices. This improves uplink scheduling efficiency and uplink capacity. Alternatively, when the first LCG is associated with a first priority level range according to preset configuration rule 2, the network device allocates uplink resources to the terminal device based on the first priority level range and the first amount of data. For example, when the priority level corresponding to the first priority level range is low, the network device may preferentially allocate uplink resources to data corresponding to the first data amount, or when the priority level corresponding to the first priority level range is high and transmission resources are insufficient, the network device may later allocate uplink resources to data corresponding to the first data amount and preferentially allocate uplink resources to other terminal devices, which improves uplink scheduling efficiency and uplink capacity.

[0010] In a possible design, when the configuration rules include Configuration Rule 1, Configuration Rule 1 further indicates that a second LCG is associated with a second remaining PDB range. The L LCGs include the second LCG, and the L remaining PDB ranges include the second remaining PDB range. For example, the second LCG may be any LCG among the L LCGs other than the first LCG. In other words, in Configuration Rule 1, the L LCGs correspond one-to-one to the L remaining PDB ranges.

[0011] In a possible design, when the buffered data further includes second data and the remaining PDB of the second data is within a second remaining PDB range, the BSR further indicates a second data amount and a second LCG, where the second data amount corresponds to the second LCG and the second data amount includes the data amount of the second data.

[0012] In other words, even if the buffered data on the first LCH includes data of different remaining PDBs, the terminal device determines different LCGs and data amounts indicated by the BSR based on the remaining PDBs. In this way, after receiving the BSR, the network device can know the remaining PDB ranges corresponding to different data amounts based on the LCG indicated by the BSR according to Configuration Rule 1, and can more appropriately allocate uplink resources to improve uplink scheduling efficiency.

[0013] In a possible design, when the remaining PDB of the first data is within the first remaining PDB range, the buffered data including the first data includes: When there is one remaining PDB of the buffered data, the buffered data is the first data.

[0014] In other words, when the buffered data on the first LCH have the same remaining PDB and the remaining PDB is within the first remaining PDB range, the terminal device reports the data amount of the buffered data through one LCG (i.e., the first LCG). In this way, after receiving the BSR, the network device can know the data amount and the remaining PDB range according to Configuration Rule 1 and allocate uplink resources, so that the terminal device uploads the buffered data on the first LCH in a timely manner. This improves uplink scheduling efficiency.

[0015] In a possible design, there are at least two remaining PDBs of the buffered data. The remaining PDB of the first data being within the first remaining PDB range includes the following: When the smallest remaining PDB of the buffered data is used to determine the remaining PDB range corresponding to the buffered data, the smallest remaining PDB of the buffered data is within the first remaining PDB range, and the buffered data is the first data.

[0016] In other words, even if the buffered data on the first LCH includes data of different remaining PDBs, the terminal device determines the remaining PDB range corresponding to the buffered data based on the smallest remaining PDB, and then determines the LCG indicated by the BSR based on the remaining PDB range. In this way, after receiving the BSR, the network device may know the data amount and the remaining PDB range according to Configuration Rule 1 and appropriately allocate uplink resources. For example, when the remaining PDB indicated by the remaining PDB range is small, the network device may preferentially allocate uplink resources based on the data amount corresponding to the remaining PDB range, thereby improving uplink scheduling efficiency.

[0017] In a possible design, when the remaining PDB of the first data is within the first remaining PDB range, before the terminal device determines that the buffered data to be reported is present on the first LCH, the method further includes: the terminal device receives first configuration information from the network device, where the first configuration information indicates configuration rule 1.

[0018] In other words, the network device configures configuration rule 1 for the terminal device, so that the network device properly manages the reporting of the BSR.

[0019] In a possible design, before the terminal device determines that the buffered data to be reported exists on the first LCH, the method further includes: the terminal device receives second configuration information from the network device; the second configuration information is used to configure an LCG range corresponding to the first LCH, the LCG range including all or part of L LCGs, so that the first LCH is dynamically adjusted within the LCG range; in other words, the amount of buffered data on the first LCH can be reported via at least one LCG within the LCG range.

[0020] In a possible design, the second remaining PDB range is [T, Pmax], where T represents the PDB threshold and Pmax represents the maximum transmission latency allowed for the buffered data. In other words, the remaining PDB range is obtained through classification based on the PDB threshold. The terminal device compares the remaining PDB of the buffered data with the PDB threshold to determine the remaining PDB range corresponding to the buffered data. For example, when the remaining PDB of the buffered data is equal to or greater than the PDB threshold, the remaining PDB corresponding to the buffered data is the second remaining PDB range. This simplifies the processing process of the terminal device.

[0021] In a possible design, the first remaining PDB range is [0, T), where T represents a PDB threshold. In other words, the remaining PDB range is obtained through classification based on the PDB threshold. The terminal device compares the remaining PDB of the buffered data with the PDB threshold to determine the remaining PDB range corresponding to the buffered data. For example, when the remaining PDB of the buffered data is less than the PDB threshold, the remaining PDB corresponding to the buffered data is the first remaining PDB range. This simplifies the processing process of the terminal device.

[0022] In a possible design, when the configuration rules include configuration rule 2, configuration rule 2 further indicates that a second LCG is associated with a second priority level range, the L LCGs include the second LCG, and the L priority level ranges include the second priority level range. For example, the second LCG may be any LCG among the L LCGs other than the first LCG. In other words, in configuration rule 2, the L LCGs correspond one-to-one to the L priority level ranges.

[0023] In one possible design, when the first data is data of a first type, the first LCG is an LCG in a first set, the first set including at least one LCG, and each LCG in the first set is used to transmit data of the first type. Alternatively, when the first data is data of a second type, the first LCG is an LCG in a second set, the second set including at least one LCG, and each LCG in the second set is used to transmit data of the second type, and each LCG in the first set is different from each LCG in the second set.

[0024] In other words, the terminal device reports the amount of data of different types via different LCGs.

[0025] In a possible design, when the priority level of the first data is within a first priority level range, the buffered data including the first data includes: When the buffered data are data of the same type and there is one remaining PDB of the buffered data, the buffered data is the first data.

[0026] In other words, when the data type of the buffered data is the same and the remaining PDB of the buffered data is the same, all of the buffered data corresponds to the same priority level and is within the same priority level range.

[0027] In a possible design, when the priority level of the first data is within a first priority level range, the buffered data including the first data includes: the buffered data is the first data when the buffered data is the same type of data, there are at least two remaining PDBs of the buffered data, and the smallest remaining PDB of the buffered data is used to determine the priority level of the buffered data.

[0028] In other words, when the data types of the buffered data are the same and the remaining PDBs of the buffered data are different, the terminal device determines the priority level based on the smallest remaining PDB of the buffered data. In this way, all of the buffered data correspond to the same priority level and are within the same priority level range.

[0029] In a possible design, before the terminal device determines that buffered data to be reported exists on the first LCH, the method further includes: the terminal device receives third configuration information from the network device, where the third configuration information indicates configuration rule 2.

[0030] In other words, the network device configures configuration rule 2 for the terminal device, so that the network device properly manages the reporting of the BSR.

[0031] In a possible design, before the terminal device determines that the buffered data to be reported exists on the first LCH, the method further includes: the terminal device receives fourth configuration information from the network device, the fourth configuration information being used to configure a priority level range corresponding to the first LCH, the priority level range configured by using the fourth configuration information including one or more priority levels within the L priority level range, such that the first LCH is dynamically adjusted within the priority level range configured for the first LCH. In this way, even if the buffered data on the first LCH has different priority levels at different times, the terminal device may report the amount of corresponding buffered data via the corresponding LCG.

[0032] In a possible design, the first priority level range is [0,K) and the second priority level range is [K,Kmax], where K represents the priority level threshold and Kmax represents the lowest priority level that can be present in the buffered data.

[0033] In other words, the priority range is obtained through classification based on the priority threshold. The terminal device compares the priority level of the buffered data with the priority level threshold to determine the corresponding priority level range. For example, when the priority level of the buffered data is less than the priority level threshold, the priority level range of the priority level of the buffered data is the first priority level range, or when the priority level of the buffered data is equal to or greater than the priority level threshold, the priority level range of the priority level of the buffered data is the second priority level range. This simplifies the processing process of the terminal device.

[0034] In a possible design, before the terminal device determines that buffered data to be reported exists on the first LCH, the method further includes: the terminal device receives fifth configuration information from the network device, the fifth configuration information is used to configure a first LCG for the first LCH, so that the terminal device reports the amount of the first data on the first LCH via the first LCG.

[0035] According to a second aspect, a logical channel grouping method is provided. The method may be executed by a network device or a chip used in the network device. For the sake of explanation, the following example uses an example in which the method is executed by the network device. The method includes: receiving a buffer status report (BSR) from a terminal device, where the buffered data to be reported exists on a first logical channel (LCH) of the terminal device; the BSR indicates a first amount of data and a first logical channel group (LCG); the first amount of data corresponds to the first LCG, the first amount of data includes the first amount of data, the buffered data includes the first data, the first LCG is one of the LCGs configured for the first LCH; and the network device allocates uplink resources to the terminal device based on the first amount of data and the first LCG according to a preset configuration rule; and a remaining packet delay budget (PDB) of the first data is within a first remaining PDB range. The configuration rule is Configuration Rule 1, i.e., includes L LCGs and L remaining PDB ranges, where the L LCGs include a first LCG, the L remaining PDB ranges include the first remaining PDB range, and the first LCG is associated with the first remaining PDB range, and L is a positive integer greater than or equal to 2. Alternatively, the priority level of the first data is within a first priority level range, and the priority level of the first data is determined based on the remaining PDB of the first data and the data type of the first data. The configuration rule is Configuration Rule 2, i.e., includes L LCGs and L priority level ranges, where the L LCGs include the first LCG, the L priority level ranges include the first priority level range, and the first LCG is associated with the first priority level range, and L is a positive integer greater than or equal to 2.

[0036] In a possible design, when the configuration rules include Configuration Rule 1, Configuration Rule 1 further indicates that the second LCG is associated with a second remaining PDB range, the L LCG includes the second LCG, and the L remaining PDB ranges include the second remaining PDB range.

[0037] In a possible design, when the buffered data further includes second data and the remaining PDB of the second data is within a second remaining PDB range, the BSR further indicates a second data amount and a second LCG, where the second data amount corresponds to the second LCG and the second data amount includes the data amount of the second data.

[0038] In a possible design, when the remaining PDB of the first data is within the first remaining PDB range, the buffered data including the first data includes: When there is one remaining PDB of the buffered data, the buffered data is the first data.

[0039] In a possible design, there are at least two remaining PDBs of the buffered data. The remaining PDB of the first data being within the first remaining PDB range includes the following: When the smallest remaining PDB of the buffered data is used to determine the remaining PDB range corresponding to the buffered data, the smallest remaining PDB of the buffered data is within the first remaining PDB range, and the buffered data is the first data.

[0040] In a possible design, when the remaining PDB of the first data is within the first remaining PDB range, before the network device receives a BSR from the terminal device, the method further includes: the network device sends first configuration information to the terminal device, where the first configuration information indicates configuration rule 1.

[0041] In a possible design, before the network device receives the BSR from the terminal device, the method further includes: the network device sends second configuration information to the terminal device, where the second configuration information is used to configure an LCG range corresponding to the first LCH, and the LCG range includes all or part of the L LCGs.

[0042] In a possible design, the second remaining PDB range is [T, Pmax], where T represents the PDB threshold and Pmax represents the maximum transmission latency allowed for the buffered data.

[0043] In a possible design, the first remaining PDB range is [0,T), where T represents the PDB threshold.

[0044] In a possible design, when the configuration rules include configuration rule 2, configuration rule 2 further indicates that a second LCG is associated with a second priority level range, L LCGs include the second LCG, and L priority level ranges include the second priority level range.

[0045] In one possible design, when the first data is data of a first type, the first LCG is an LCG in a first set, the first set including at least one LCG, and each LCG in the first set is used to transmit data of the first type. Alternatively, when the first data is data of a second type, the first LCG is an LCG in a second set, the second set including at least one LCG, and each LCG in the second set is used to transmit data of the second type, and each LCG in the first set is different from each LCG in the second set.

[0046] In a possible design, when the priority level of the first data is within a first priority level range, the buffered data including the first data includes: When the buffered data are data of the same type and there is one remaining PDB of the buffered data, the buffered data is the first data.

[0047] In a possible design, when the priority level of the first data is within a first priority level range, the buffered data including the first data includes: the buffered data is the first data when the buffered data is the same type of data, there are at least two remaining PDBs of the buffered data, and the smallest remaining PDB of the buffered data is used to determine the priority level of the buffered data.

[0048] In a possible design, before the network device receives the BSR from the terminal device, the method further includes: the network device sends third configuration information to the terminal device, where the third configuration information indicates configuration rule 2;

[0049] In a possible design, before the network device receives the BSR from the terminal device, the method further includes: the network device sending fourth configuration information to the terminal device, the fourth configuration information being used to configure a priority level range corresponding to the first LCH, and the priority level range configured by using the fourth configuration information including one or more priority levels within the L priority level ranges.

[0050] In a possible design, the first priority level range is [0,K) and the second priority level range is [K,Kmax], where K represents the priority level threshold and Kmax represents the lowest priority level that can be present in the buffered data.

[0051] In a possible design, before the network device receives the BSR from the terminal device, the method further includes: the network device sends fifth configuration information to the terminal device, where the fifth configuration information is used to configure a first LCG for the first LCH.

[0052] According to a third aspect, there is provided a communications device. The communications device includes a processor. The processor is coupled to a memory and configured to read and execute instructions in the memory, such that the communications device performs a method performed by a terminal device in any one of the above aspects or any possible design of any one of the above aspects. The communications device may be the terminal device in the first aspect or any one of the possible designs of the first aspect, or a chip implementing functionality of the terminal device.

[0053] According to a fourth aspect, there is provided a chip. The chip includes a processing circuit and an input / output interface. The input / output interface is configured to communicate with a module external to the chip. For example, the chip may be a chip that implements the functionality of the terminal device of the first aspect or any one of the possible designs of the first aspect. The processing circuit is configured to execute a computer program or instructions to implement the method of the first aspect or any one of the possible designs of the first aspect.

[0054] According to a fifth aspect, there is provided a communications apparatus. The communications apparatus includes a processor. The processor is coupled to a memory and configured to read and execute instructions in the memory, such that the communications apparatus performs a method performed by a network device in any one of the above aspects or any possible design of any one of the above aspects. The communications apparatus may be the network device in the second aspect or any one of the possible designs of the second aspect, or a chip implementing functionality of the network device.

[0055] According to a sixth aspect, there is provided a chip. The chip includes a processing circuit and an input / output interface. The input / output interface is configured to communicate with a module external to the chip. For example, the chip may be a chip that implements the functionality of the network device of the second aspect or any one of the possible designs of the second aspect. The processing circuit is configured to execute a computer program or instructions to implement the method of the second aspect or any one of the possible designs of the second aspect.

[0056] According to a seventh aspect, there is provided a computer-readable storage medium having instructions stored thereon that, when executed on a computer, enable the computer to perform the method of any one of the above aspects.

[0057] According to an eighth aspect, there is provided a computer program product comprising instructions which, when executed on a computer, enable the computer to carry out the method of any one of the above aspects.

[0058] According to a ninth aspect, there is provided a circuit system including a processing circuit configured to perform the method of any one of the above aspects.

[0059] According to a tenth aspect, there is provided a communication system including a terminal device and a network device, wherein the terminal device is configured to perform the method of the first aspect and any one of possible designs thereof, and the network device is configured to perform the method of the second aspect and any one of possible designs thereof.

[0060] The technical effects brought about by any of the designs in the second to tenth aspects refer to the beneficial effects of the corresponding methods provided above, and the details will not be described again in this specification. [Brief explanation of the drawings]

[0061] [Figure 1] 1 is a diagram of the architecture of a communication system according to an embodiment of the present application; [Figure 2] FIG. 1 is a diagram of a scheduling scenario according to an embodiment of the present application. [Figure 3] FIG. 2 is a diagram of a structure of a data frame according to an embodiment of the present application. [Figure 4]FIG. 2 is a diagram of a communication protocol stack according to an embodiment of the present application. [Figure 5] FIG. 1 is a diagram of a BSR format according to an embodiment of the present application. [Figure 6] FIG. 10 is a diagram of another BSR format according to an embodiment of the present application. [Figure 7] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 8] 1 is a schematic flowchart of a logical channel grouping method according to an embodiment of the present application; [Figure 9] FIG. 1 is a diagram of a logical channel group configuration according to an embodiment of the present application. [Figure 10] FIG. 10 is a diagram of another logical channel group configuration according to an embodiment of the present application. [Figure 11] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 12] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 13] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 14] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 15] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 16] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 17] FIG. 2 is a diagram of data frame mapping according to an embodiment of the present application. [Figure 18] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 19] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 20] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 21]FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 22] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 23] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 24] FIG. 10 is a diagram of another scheduling scenario according to an embodiment of the present application. [Figure 25] 4 is a schematic flowchart of another logical channel grouping method according to an embodiment of the present application; [Figure 26] 4 is a schematic flowchart of another logical channel grouping method according to an embodiment of the present application; [Figure 27] 4 is a schematic flowchart of another logical channel grouping method according to an embodiment of the present application; [Figure 28] 1 is a diagram of the structure of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0062] The technical solutions of this application are described below with reference to the accompanying drawings.

[0063] 1 is an architecture diagram of a communication system 1000 to which an embodiment of this application is applied. As shown in FIG. 1, the communication system 1000 includes at least one network device (e.g., 110a and 110b in FIG. 1) and at least one terminal device (e.g., 120a to 120j in FIG. 1). The terminal device is connected to the network device in a wireless manner. FIG. 1 is just a diagram. The communication system may further include other network devices, for example, wireless relay devices and wireless backhaul devices (not shown in FIG. 1).

[0064] The network device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation (5G) mobile communication system, a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, an access node in a wireless fidelity (Wi-Fi) system, or the like, or may be a module or unit that completes part of the functions of a base station. For example, the network device may be a central unit (CU) or a distributed unit (DU). The CU in this specification completes the functions of a radio resource control (RRC) protocol and a packet data convergence protocol (PDCP) of a base station and may further complete the function of a service data adaptation protocol (SDAP). The DU completes the functions of the radio link control (RLC) layer and medium access control (MAC) layer of the base station, and may further complete some or all of the functions of the physical (PHY) layer. For a specific description of the above protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). The network device may be a macro base station (e.g., 110a in FIG. 1), a micro base station, or an indoor base station (e.g., 110b in FIG. 1), or may be a relay node, a donor node, etc. The specific technology and the specific device type used by the network device are not limited in the embodiments of this application.For ease of explanation, the following uses a network device as an illustrative example.

[0065] A terminal device may also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. The terminal device may be widely applied to various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, and smart city. The terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver functionality, a wearable device, a vehicle, an unmanned aerial vehicle, a helicopter, an airplane, a ship, a robot, a robotic arm, a smart home device, etc. The specific technology and the specific device type used by the terminal device are not limited in the embodiments of this application.

[0066] The network device and the terminal device may be in a fixed position or may be mobile. The network device and the terminal device may be located on land, including an indoor or outdoor device, a handheld device, or an in-vehicle device, or may be located on water, or may be located on an airplane, a balloon, or a satellite in the air. The application scenario of the network device and the terminal device is not limited in the embodiments of this application.

[0067] The roles of a network device and a terminal device may be relative. For example, helicopter or unmanned aerial vehicle 120i in FIG. 1 may be configured as a mobile base station. For terminal device 120j accessing a wireless access network through 120i, terminal device 120i is a network device. However, for network device 110a, 120i is a terminal device. In other words, 110a and 120i communicate with each other by using a wireless air interface protocol. Obviously, 110a and 120i may alternatively communicate with each other by using an interface protocol between base stations. In this case, for 110a, 120i is also a network device. Therefore, both network devices and terminal devices may be collectively referred to as communication devices. 110a and 110b in FIG. 1 may be referred to as communication devices having the functionality of network devices, and 120a to 120j in FIG. 1 may be referred to as communication devices having the functionality of terminal devices.

[0068] Communications between network devices and terminal devices, communications between network devices, and communications between terminal devices may be performed over licensed spectrum, or over unlicensed spectrum, or over both licensed and unlicensed spectrum. Communications may be performed over spectrum below 6 gigahertz (GHz), or over spectrum above 6 GHz, or over both spectrum below 6 GHz and above 6 GHz. Spectral resources used for wireless communications are not limited in the embodiments of this application.

[0069] In the embodiments of this application, the functions of the network device may alternatively be performed by a module (e.g., a chip) within the network device, or may be performed by a control subsystem including the functions of the network device. The control subsystem including the functions of the network device in this specification may be a control center in the above application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal device may alternatively be performed by a module (e.g., a chip or a modem) within the terminal device, or may be performed by a device including the functions of the terminal device.

[0070] In this application, a network device transmits a downlink signal or downlink information to a terminal device, where the downlink information is carried on a downlink channel, and the terminal device transmits an uplink signal or uplink information to the network device, where the uplink information is carried on an uplink channel. To communicate with the network device, the terminal device needs to establish a wireless connection to a cell controlled by the network device. The cell that establishes a wireless connection to the terminal device is called the serving cell of the terminal device. When communicating with the serving cell, the terminal device is further interfered with by signals from neighboring cells.

[0071] In order to facilitate understanding of the embodiments of this application, the following will first briefly explain the terms used in the embodiments of this application, which should be understood to be merely for the purpose of facilitating understanding of the embodiments of this application and not to constitute any limitations on this application.

[0072] 1. Cross reality (extended reality, XR) XR refers to a human-machine interaction environment that combines reality and virtuality, created using computer technology and wearable devices. XR is proposed based on augmented reality (AR), virtual reality (VR), and mixed reality (MR). In other words, to avoid conceptual confusion, XR is actually a general term that includes AR, VR, and MR. XR services aim to use technologies such as high-speed networks and 360-degree imaging to achieve an interactive immersive experience. XR services have the following characteristics: large service volume, high transmission latency requirements (i.e., transmission latency needs to be reduced as much as possible), short data frame arrival intervals, and clear service cycles.

[0073] In a scenario where a network device transmits data frames of an XR or XR-like service to a terminal device, when the data frame rate is 60 frames per second (fps), the average inter-arrival time between service data corresponding to two adjacent data frames is 16.6666... ​​ms (approximately equal to 16.67 ms). It should be understood that a data frame is defined from the perspective of the application layer, and one data frame may be replaced with one video frame. A protocol data unit set (PDU set) contains service data within one data frame. A PDU set is defined from the perspective of the MAC layer, and one data frame may also be replaced with one PDU set.

[0074] For example, one PDU set contains the service data of one video frame of an XR service. The data volume of one PDU set is large, and one PDU set is usually divided into tens to hundreds of packets for transmission. The packets of the PDU set are generated in the form of a data burst. Specifically, there are no packets for a certain period of time. When packets exist, a large number of packets appear in a very short period of time. Furthermore, video frames have a specific periodicity. For example, for a 60 fps XR video stream, a PDU set appears every 16.6666... ​​ms (approximately equal to 16.67 ms). In other words, as shown in Figure 2, a data burst occurs every 16.6666... ​​ms (approximately equal to 16.67 ms).

[0075] For example, a video frame is used as an example, and data burst types include I type and P type. I type indicates that the video frame corresponding to the data burst is an I frame, and P type indicates that the video frame corresponding to the data burst is a P frame. It can be easily understood that a video sequence of an XR service may be segmented into multiple groups of pictures (GOPs). For example, each GOP may include the same number of video frames. In each GOP, the terminal device may perform intra-frame coding or inter-frame coding on each frame of an image. As shown in FIG. 3, the first frame of an image in each GOP may be referred to as an intra-frame coding frame. An intra-frame coding frame is abbreviated as an I frame and may be independently encoded and decoded. Subsequent frames of an image may be referred to as inter-frame coding frames, including predictive frames (abbreviated as P frames) and bidirectional predictive frames (abbreviated as B frames). Inter-coding frames need to be coded and decoded based on previously coded images, improving coding and decoding compression performance.

[0076] 2. Packet Delay Budget (PDB) The PDB is a latency upper limit for transmitting packets between a terminal device and a user plane network element, and represents the maximum transmission latency allowed for the packet. The user plane network element may be a user plane function (UPF) network element that terminates the N6 interface in a 5G system.

[0077] The PDB may be divided into two parts: the access network (AN) PDB (denoted as AN PDB) and the core network (CN) PDB (denoted as CN PDB). The AN PDB is the latency upper bound for transmitting packets between terminal devices and access network devices. The CN PDB is the latency upper bound for transmitting packets between access network devices and user plane network elements. The PDB is equal to the sum of the AN PDB and the CN PDB.

[0078] The PDB of a data burst can be understood as the delay from when a packet arrives at a terminal device to when the packet is successfully transmitted to a network device. Packets that do not cross the PDB and are not successfully transmitted to a network device can be considered unwanted packets.

[0079] The video service in the XR service is used as an example. A typical value of the PDB of an uplink video frame is 30 milliseconds (ms), and optional values ​​are 60ms, 15ms, 45ms, etc.

[0080] It can be easily understood that in the embodiment of this application, the unit of the PDB may be milliseconds, for example, tens of milliseconds or tens of milliseconds. Obviously, the PDB may alternatively have other time units. This is not limited in the embodiment of this application. Furthermore, in the embodiment of this application, delay and latency are equivalent and may be substituted for each other. For example, the latency upper limit may also be described as the delay upper limit.

[0081] 3. Protocol stack on the radio access network side The protocol stack on the radio access network side may be classified into a user plane protocol stack and a control plane protocol stack. The user plane protocol stack may include an SDAP layer, a PDCP layer, an RLC layer, a MAC layer, a PHY layer, etc. The PHY layer belongs to the first layer (also called layer 1 (L1)), and the MAC layer, the RLC layer, the PDCP layer, and the SDAP layer belong to the second layer (also called layer 2 (L2)). Furthermore, the RRC layer and the NAS layer of the control plane belong to the third layer (also called layer 3 (L3)).

[0082] As shown in FIG. 4, in the user plane protocol stack, the SDAP layer is located above the PDCP layer, which is located above the RLC layer, which is located above the MAC layer, and which is located above the PHY layer. For an XR service, after service data arrives at the terminal device, the terminal device sequentially processes packets at the protocol layers in the top-to-bottom order shown in FIG. 4 and finally transmits the processed packets to the network device over the air interface. After receiving the packets over the air interface, the network device sequentially performs corresponding processing on the packets in the reverse order to that of the terminal device. Packet processing at each protocol layer is realized by a multi-function entity corresponding to the protocol layer. For details, please refer to the relevant technical specifications of 3GPP. The details will not be described again in this specification. It can be easily understood that the user plane protocol stack shown in FIG. 4 does not constitute any limitation on the solution of this application. In actual applications, the user plane protocol stack may include more or fewer protocol layers than those shown in the drawing.

[0083] Each layer of the protocol stack may have multiple protocol entities and multiple defined channel resources. The MAC layer is used as an example.

[0084] A logical channel (LCH) is used by the MAC layer to provide data transmission services. The logical channel is used to indicate the content to be carried. A network device configures a transmission parameter set of the LCH for a terminal device. The transmission parameter set may include parameters that can be transmitted or mapped by the LCH, such as subcarrier spacing, cyclic prefix length, and the serving cell of the terminal device corresponding to uplink resources.

[0085] A logical channel group (LCG) is a set containing multiple LCHs, typically configured by a network device for an end device.

[0086] The uplink resource is used to transmit uplink data of a terminal device, for example, a physical uplink shared channel (PUSCH) resource.

[0087] 4.BSR In a communication system, a terminal device may request uplink scheduling from a network device via a BSR. For example, the terminal device transmits a BSR to the network device. In response, the network device receives a BSR from the terminal device. The BSR indicates the amount of buffered data to be reported by the terminal device. The network device allocates a corresponding number of uplink resources to the terminal device based on the amount of buffered data indicated by the BSR.

[0088] The BSR types are described as follows: In a communication system, there may be multiple types of BSR, such as regular BSR, periodic BSR, or padding BSR. In this application, regular BSR is used as an example for illustration.

[0089] The trigger for regular BSR is described as follows: The trigger for regular BSR satisfies the following conditions: When one of the following cases is met, uplink data needs to be transmitted on a logical channel (LCH) belonging to an LCG:

[0090] Case 1: An LCH has uplink data to be uploaded and has a higher priority level than other LCHs belonging to the same LCG. For example, LCG1 is used as an example. LCG1 includes four LCHs, which are denoted as LCH5 to LCH8, respectively. Uplink data needs to be uploaded on one or more of LCH5, LCH6, and LCH7, but the priority levels of LCH5, LCH6, and LCH7 are lower than the priority level of LCH8. When uplink data needs to be uploaded on LCH8, if the trigger condition in Case 1 is met, the terminal device triggers a regular BSR.

[0091] Case 2: There is no uplink data that needs to be uploaded on other LCHs belonging to the LCG. For example, LCG1 is used as an example. LCG1 includes four LCHs, which are denoted as LCH5 to LCH8, respectively. There is no uplink data that needs to be uploaded on LCH5, LCH6, and LCH7, but there is uplink data that needs to be uploaded on LCH8. In this case, if the trigger condition of case 2 is met, the terminal device triggers a regular BSR.

[0092] The BSR format is described as follows: The BSR format includes a short BSR format and a long BSR format.

[0093] As shown in Figure 5, the length of the short BSR format is fixed and is one octet (which can also be called a byte). In the short BSR format, three bits are used to indicate a logical channel group identity, i.e., LCG ID, and five bits are used to indicate the interval in which the amount of buffered data (buffer size) is located. The buffer size field indicates the total amount of buffered data for the logical channel group corresponding to the LCG ID field.

[0094] As shown in FIG. 6, the length of the long BSR format is not fixed, and the long BSR format may have multiple bytes. In the long BSR format, the first byte is a bitmap, and each bit in the bitmap is used to indicate whether to report the buffer size of the LCG corresponding to the bit. The second byte or the byte after the second byte is used to indicate the interval in which the amount of buffered data is located. For example, when the value of LCG_i is set to 1, this indicates that there is uplink data to be reported in LCG_i, or when the value of LCG_i is set to 0, this indicates that there is no uplink data to be reported in LCG_i. The interval in which the amount of buffered data in each LCG_i, for which data needs to be reported, is located is indicated by using one byte.

[0095] In other words, in the BSR reporting mechanism, reporting is performed at the granularity of an LCG. One BSR may be used to report the amount of uplink data corresponding to one or more LCGs.

[0096] However, the uplink data in the buffer corresponding to the LCG may include packets in one data burst or may include packets in multiple data bursts. Therefore, at a certain time, different data bursts correspond to different remaining PDBs. In this case, problems of low uplink scheduling efficiency and a reduction in uplink capacity may occur. For details, see the following descriptions in Cases A and B.

[0097] Case A: After receiving the BSR, the network device allocates uplink resources to the terminal device at intervals of a certain period, so that a packet (or some packets) in a data burst cannot be transmitted within the PDB time range, resulting in low uplink scheduling efficiency and low uplink capacity.

[0098] 7, on the side of terminal device 1, terminal device 1 obtains a packet in data burst 1 at 0 ms and obtains a packet in data burst 2 at 16.67 ms. In this case, the uplink data in the buffer corresponding to LCG1 includes a packet in data burst 1 and a packet in data burst 2. K1 represents the amount of data of data burst 1 in the buffer corresponding to LCG1, and K2 represents the amount of data of data burst 2 in the buffer corresponding to LCG1.

[0099] On the network device side, after receiving the BSR, the network device does not immediately allocate uplink resources to terminal device 1. For example, the network device allocates uplink resources to terminal device 1 only at 32 ms. Furthermore, the uplink resources allocated by the network device to terminal device 1 at 32 ms are uplink resources determined based on the amount of data K indicated by the BSR. At 32 ms, the network device allocates uplink resources beyond the PDB range corresponding to packets in data burst 1. In this case, the packets (some packets) are considered invalid packets. As a result, the uplink capacity is low. Furthermore, the network device still allocates uplink resources to packets in data burst 1, which affects uplink scheduling efficiency.

[0100] Case B: When the network device receives the BSRs of at least two terminal devices and has insufficient uplink resources, the network device may allocate excessive uplink resources to some terminal devices and insufficient uplink resources to other terminal devices, resulting in poor uplink scheduling efficiency and poor uplink capacity.

[0101] For example, as shown in Figure 7, on the side of terminal device 1, for terminal device 1, please refer to the description in case A. Details will not be described again in this specification. The BSR sent by terminal device 1 is denoted as BSR1, and the amount of data indicated by BSR1 is denoted as K.

[0102] At the terminal device 2 side, a packet in data burst 3 is obtained at 1 ms. In this case, the uplink data in the buffer corresponding to LCG1 of the terminal device 2 includes the packet in data burst 3. K3 represents the amount of data of data burst 3 in the buffer corresponding to LCG1 of the terminal device 2. Correspondingly, the BSR sent by the terminal device 2 is denoted as BSR2, and the amount of data indicated by BSR2 is denoted as K3.

[0103] On the network device side, after receiving BSR1 and BSR2, the network device allocates uplink resources to terminal device 1 and terminal device 2 only at 12 ms. Furthermore, at 28 ms, the uplink resources are insufficient. The network device allocates uplink resources to terminal device 1. The uplink resources allocated to terminal device 1 are determined based on the amount of data K indicated by BSR1 and can be used by terminal device 1 to upload packets in data burst 1 and packets in data burst 2. However, the uplink resources allocated to terminal device 2 by the network device are insufficient, or there are no uplink resources available for terminal device 2 to report packets in data burst 3.

[0104] However, at 28 ms, the remaining PDB corresponding to packets in data burst 1 is 2 ms, the remaining PDB corresponding to packets in data burst 2 is approximately 18.67 (i.e., 30-(28-16-0.67)) ms, and the remaining PDB corresponding to packets in data burst 3 is 3 ms. Thus, uplink resources are not allocated to packets in data burst 3 of terminal device 2 in a timely manner, and uplink resources are easily allocated beyond the PDB range corresponding to the packets. As a result, the uplink capacity is low and the uplink scheduling efficiency is reduced.

[0105] In conclusion, the BSR can indicate the interval in which the amount of uplink data to be reported is located, but the BSR cannot indicate the remaining PDB. Therefore, when a network device allocates uplink resources based on the interval in which the amount of data indicated by the BSR is located, problems of low uplink scheduling efficiency and low uplink capacity may occur.

[0106] In consideration of this, an embodiment of this application provides a logical channel grouping method, which may be applied to the communication system in FIG. 1. In the logical channel grouping method provided in this embodiment of this application, a terminal device determines that buffered data to be reported exists on a first logical channel (LCH). Then, the terminal device sends a buffer status report (BSR) to a network device based on the buffered data to be reported on the first LCH according to a preset configuration rule. The BSR indicates a first amount of data and a first logical channel group (LCG), where the first amount of data corresponds to the first LCG, the first amount of data includes the first amount of data, the buffered data includes the first data, and the first LCG is one of at least one LCG configured for the first LCH.

[0107] If possible, the remaining packet delay budget PDB of the first data is within the first remaining PDB range. It includes L LCGs and L remaining PDB ranges, where the L LCGs include a first LCG, the L remaining PDB ranges include the first remaining PDB range, and the first LCG is associated with the first remaining PDB range, and L is a positive integer greater than or equal to 2.

[0108] Alternatively, in other possible cases, the priority level of the first data is within the first priority level range, and the priority level of the first data is determined based on the remaining PDB of the first data and the data type of the first data. The LCGs include L LCGs and L priority level ranges, where the L LCGs include a first LCG, the L priority level ranges include a first priority level range, and the first LCG is associated with the first priority level range, and L is a positive integer greater than or equal to 2.

[0109] In other words, when the BSR indicates a first amount of data and a first LCG, and the first LCG is associated with a first remaining PDB range according to preset configuration rule 1, the network device allocates uplink resources to the terminal device based on the first remaining PDB range and the first amount of data. For example, when the remaining PDB corresponding to the first remaining PDB range is small, the network device may preferentially allocate uplink resources to the data corresponding to the first amount of data. Alternatively, when the remaining PDB corresponding to the first remaining PDB range is large, the network device may later allocate uplink resources to the data corresponding to the first amount of data and preferentially allocate uplink resources to other terminal devices. This improves uplink scheduling efficiency and uplink capacity. Alternatively, when the first LCG is associated with a first priority level range according to preset configuration rule 2, the network device allocates uplink resources to the terminal device based on the first priority level range and the first amount of data. For example, when the priority level corresponding to the first priority level range is low, the network device may preferentially allocate uplink resources to data corresponding to the first data amount, or when the priority level corresponding to the first priority level range is high, the network device may later allocate uplink resources to data corresponding to the first data amount and preferentially allocate uplink resources to other terminal devices, which improves uplink scheduling efficiency and uplink capacity.

[0110] It should be understood that the names of messages between devices, names of parameters in messages, etc. in the following embodiments of this application are merely examples, and other names may be used in a specific implementation, which is not particularly limited in the embodiments of this application.

[0111] The logical channel grouping method provided in the embodiment of this application will be described in detail below with reference to Figures 8 to 27. The logical channel grouping method 800 provided in the embodiment of this application includes the following steps:

[0112] S801: A terminal device determines that buffered data to be reported exists on a first LCH.

[0113] For example, the first LCH is any logical channel for transmitting XR service data, for example, the first LCH is denoted as LCH1.

[0114] For example, in terms of data type, the buffered data on the first LCH includes data of an I frame in an XR service, or the buffered data on the first LCH includes data of a P frame in an XR service.

[0115] In another example, for a data burst, the buffered data on the first LCH includes packets within the same data burst. In this case, the buffered data on the first LCH has the same remaining PDB, or in other words, there is one remaining PDB for the buffered data on the first LCH. Alternatively, the buffered data on the first LCH includes packets within different data bursts. In this case, the buffered data on the first LCH has different remaining PDBs, or in other words, there are at least two remaining PDBs for the buffered data on the first LCH.

[0116] S802: The terminal device sends a BSR to the network device based on buffered data to be reported on the first LCH according to a preset configuration rule. In response, the network device receives a BSR from the terminal device.

[0117] The preset configuration rules include configuration rule 1 and / or configuration rule 2. For example, configuration rule 1 and configuration rule 2 are written as follows:

[0118] Configuration rule 1 indicates L LCGs and L remaining PDB ranges, where the L LCGs include a first LCG, the L remaining PDB ranges include the first remaining PDB range, and the first LCG is associated with the first remaining PDB range, and L is a positive integer greater than or equal to 2.

[0119] For example, there is a one-to-one correspondence between the L LCGs and the L remaining PDB ranges. For example, the i-th LCG among the L LCGs is associated with the i-th remaining PDB range among the L remaining PDB ranges, where i is any positive integer less than or equal to L. For example, when L is a positive integer greater than or equal to 2, Configuration Rule 1 further indicates that a second LCG is associated with the second remaining PDB range. The L LCGs include the second LCG, and the L remaining PDB ranges include the second remaining PDB range. It can be easily understood that the second LCG may be any LCG other than the first LCG among the L LCGs.

[0120] Table 1 is used as an example. Table 1 shows the correspondence between LCG and the rest of the PDB coverage. [Table 1]

[0121] As shown in Table 1, when LCG ID=0, the remaining PDB range corresponding to LCG0 is 0 ms to 2 ms. When LCG ID=1, the remaining PDB range corresponding to LCG1 is 2 ms to 4 ms. If the LCG ID has other values, the same rule may be followed. Details will not be described again. It should be understood that in Table 1, the correspondence between the LCG and the remaining PDB range is described by using an example where the value of the LCG ID ranges from 0 to 7, i.e., L=8. Obviously, L may alternatively have other values, for example, L=4. This is not limited in the embodiments of this application.

[0122] It can be easily understood that the first LCG and the second LCG may be different LCGs in Table 1. The first remaining PDB range and the second remaining PDB range may be different remaining PDB ranges in Table 1.

[0123] In some embodiments, the first remaining PDB range may be determined based on a PDB threshold. For example, the first remaining PDB range is [0,T], and the second remaining PDB range is [T,Pmax], where T represents the PDB threshold and Pmax represents the maximum transmission latency allowed for buffered data. For example, T=2 ms and Pmax=30 ms. Table 2 is used as an example. Table 2 shows other correspondences between LCGs and remaining PDB ranges. [Table 2]

[0124] As shown in Table 2, when LCG ID=0, the remaining PDB range corresponding to LCG0 is 0ms to Tms. When LCG ID is any value from 1 to 7, the remaining PDB range corresponding to LCG is T to Pmax. It can be easily understood that Table 2 may be replaced with Table 3. [Table 3]

[0125] As shown in Table 3, when LCG ID=0, the remaining PDB range corresponding to LCG0 is 0ms to Tms. For a terminal device, the terminal device determines based on Table 3 that the remaining PDB range corresponding to other LCGs (e.g., LCG1 to LCG7) is T to Pmax.

[0126] It can be easily understood that the first LCG may be LCG0 in Table 2 (or Table 3), and the second LCG may be any one of LCG1 to LCG7 in Table 2.

[0127] It can be easily understood that the configuration rule 1 may be pre-configured information or may be configured by the network device for the terminal device. Specifically, as shown in Figure 25, the logical channel grouping method in this embodiment of the present application further includes S803.

[0128] S803: The network device sends first configuration information to the terminal device. Correspondingly, the terminal device receives the first configuration information from the network device.

[0129] The first configuration information indicates configuration rule 1. For example, the first configuration information may be information in LogicalChannelConfig.

[0130] For example, when configuration rule 1 is as shown in Table 1, it can be understood that the first configuration information is used to configure L LCGs and L remaining PDB ranges, and the correspondence between the L LCGs and the L remaining PDB ranges.

[0131] In another example, when configuration rule 1 is as shown in Table 2 (or Table 3), it can be understood that the first configuration information is used to configure the first LCG.

[0132] It should be understood that S803 is executed before S801, and as a result, the terminal device transmits a BSR (at S802) based on the configuration at S803. In other words, the L LCGs in configuration rule 1 include the first LCG at S802, and the L remaining PDB ranges in configuration rule 1 include the first remaining PDB range at S802.

[0133] Configuration rule 2 indicates L LCGs and L priority level ranges, where the L LCGs include a first LCG, the L priority level ranges include a first priority level range, the first LCG is associated with the first priority level range, and L is a positive integer greater than or equal to 2.

[0134] For example, there is a one-to-one correspondence between the L LCGs and the L priority level ranges. For example, the i-th LCG among the L LCGs is associated with the i-th priority level range among the L priority level ranges, where i is a positive integer less than or equal to L. For example, when L is a positive integer greater than or equal to 2, Configuration Rule 2 further indicates that a second LCG is associated with the second priority level range. The L LCGs include the second LCG, and the L priority level ranges include the second priority level range. In this embodiment of the present application, the priority level is determined based on the data type of the buffered data on any LCH and the remaining PDB of the buffered data on the LCH. It can be easily understood that the second LCG may be any LCG other than the first LCG among the L LCGs.

[0135] Table 4 is used as an example. Table 4 shows the correspondence between LCGs and priority level ranges. [Table 4]

[0136] As shown in Table 4, when LCG ID=0, the priority level range corresponding to LCG0 is 0 to 2. When LCG ID=1, the priority level range corresponding to LCG1 is 3 to 4. If the LCG ID has other values, the same rule may be followed. Details will not be described again. It should be understood that in Table 4, the correspondence between LCGs and priority level ranges is described by using an example where the value of the LCG ID ranges from 0 to 7, i.e., L=8. Obviously, L may alternatively have other values, for example, L=4. This is not limited in the embodiments of this application.

[0137] It can be easily understood that the first LCG and the second LCG may be different LCGs in Table 4. The first priority level range and the second priority level range may be different priority level ranges in Table 4.

[0138] In some embodiments, the first priority level range may be determined based on a priority level threshold. For example, the first priority level range is [0, K], and the second priority level range is [K, Kmax], where K represents the priority level threshold and Kmax represents the lowest priority level that may exist in the buffered data. For example, K=2 and Kmax=16. Table 5 is used as an example. Table 5 shows other correspondences between LCGs and priority level ranges. [Table 5]

[0139] As shown in Table 5, when LCG ID=0, the priority level range corresponding to LCG0 is 0 to K. When LCG ID is any value between 1 and 7, the priority level range corresponding to LCG is K to Kmax. It can be easily understood that Table 5 may be replaced with Table 6. [Table 6]

[0140] As shown in Table 6, when LCG ID=0, the priority level range corresponding to LCG0 is 0 to K. For a terminal device, the terminal device determines based on Table 6 that the priority level range corresponding to other LCGs (e.g., LCG1 to LCG7) is K to Kmax.

[0141] It can be easily understood that the first LCG may be LCG0 in Table 5 (or Table 6), and the second LCG may be any one of LCG1 to LCG7 in Table 5.

[0142] It can be easily understood that the configuration rule 2 may be pre-configured information or may be configured by the network device for the terminal device. Specifically, as shown in FIG. 25 , the logical channel grouping method in this embodiment of the present application further includes S804.

[0143] S804: The network device sends the third configuration information to the terminal device. In response, the terminal device receives the third configuration information from the network device.

[0144] The third configuration information indicates configuration rule 2. For example, the third configuration information may be information in LogicalChannelConfig.

[0145] For example, when configuration rule 2 is as shown in Table 4, it can be understood that the third configuration information is used to configure L LCGs and L priority level ranges, and the correspondence between the L LCGs and the L priority level ranges.

[0146] In another example, when configuration rule 2 is as shown in Table 5 (or Table 6), it can be understood that the third configuration information is used to configure the first LCG.

[0147] It should be understood that S804 is executed before S801, and as a result, the terminal device transmits a BSR (in S802) based on the configuration in S804. In other words, the L LCGs in configuration rule 2 include the first LCG in S802, and the L priority level ranges in configuration rule 2 include the first priority level range in S802.

[0148] The BSR in S802 is explained as follows.

[0149] The BSR indicates a first amount of data and a first LCG. For example, when the BSR is as shown in Figure 5, the LCG ID field indicates the first LCG, and the buffer size field indicates the first amount of data. In another example, when the BSR is as shown in Figure 6, one bit in byte 1 indicates the first LCG, and one byte in bytes 2 to m+1 indicates the first amount of data.

[0150] The first amount of data indicated by the BSR corresponds to the first LCG, for example, the first amount of data is the amount of data in the buffer corresponding to the first LCG.

[0151] The first data amount indicated by the BSR includes the data amount of the first data, and the buffered data on the first LCH includes the first data (this may be understood as the first data being all or part of the buffered data on the first LCH). For example, the first LCH is indicated as LCH1. When the first LCG includes LCH1 but does not include other LCHs, the data in the buffer corresponding to the first LCG is the first data in the buffered data on LCH1. Correspondingly, the first data amount is the data amount of the first data. When the first LCG includes both LCH1 and other LCHs, the data in the buffer corresponding to the first LCG includes both the first data in the buffered data on LCH1 and the buffered data on the other LCHs. Correspondingly, the first data amount is larger than the data amount of the first data. The first data may be all or part of the buffered data on the first LCH. For details, see the descriptions of Implementations 1 to 10 below. Details will not be described in this specification.

[0152] The first LCG is one of at least one LCG configured for the first LCH. For example, the LCG configured for the first LCH is described in detail using two configuration cases (Configuration Case 1 and Configuration Case 2 below).

[0153] Configuration Case 1: The network device configures multiple LCGs for each LCH of the terminal device. The first LCH is used as an example. As shown in FIG. 26, the logical channel grouping method in this embodiment of the present application further includes S805.

[0154] S805: The network device sends the second configuration information to the terminal device. In response, the terminal device receives the second configuration information from the network device.

[0155] The second configuration information is used to configure an LCG range corresponding to the first LCH. For example, the LCG range configured by using the second configuration information includes all or part of L LCGs. The first LCH may be dynamically adjusted within the LCG range corresponding to the first LCH. For example, at time point 1, the LCG to which the first LCH belongs is LCG1, and at time point 2, the LCG to which the first LCH belongs is LCG2. For details, see the descriptions of implementation methods 1 to 3 below. Details will not be described in this specification.

[0156] For example, the second configuration information may be information in LogicalChannelConfig, such as logicalChannelGroupRange:SEQUENCE(SIZE(1...8)) OF INTEGER(0...maxLCG-ID).

[0157] Table 1 (or Table 4) is used as an example. The LCG range configured for the first LCH by using the second configuration information is shown as (0,7). In other words, the first LCH may be dynamically adjusted among eight LCGs (i.e., LCG0 to LCG7).

[0158] 9 is used as an example. The LCG range configured for the first LCH (denoted as LCH1) by using the second configuration information is denoted as (1, n). In other words, the first LCH may be dynamically adjusted among n LCGs (i.e., LCG1 to LCGn).

[0159] It can be easily understood that S805 may be executed before S801, and S803 (or S804) and S805 may be executed simultaneously. For example, the first configuration information and the second configuration information are transmitted via the same message. Alternatively, the network device first executes S803 (or S804) and then executes S805. This is not limited to the embodiments of this application. In S805, the first LCH is used as an example for explanation. When the terminal device has another LCH, for example, a second LCH that is also used to transmit XR service data, the network device also configures an LCG range for the second LCH.

[0160] Configuration Case 2: In addition to configuring a normal LCG, the network device further configures an additional LCG for each LCH of the terminal device. In Configuration Case 2, the additionally configured LCG for each LCH is denoted as the first LCG, and the normally configured LCG for each LCH is denoted as the second LCG. The first LCH is used as an example. As shown in Figure 26, the logical channel grouping method in this embodiment of the present application further includes S806.

[0161] S806: The network device sends the fifth configuration information to the terminal device. In response, the terminal device receives the fifth configuration information from the network device.

[0162] The fifth configuration information is used to configure a first LCG for a first LCH. For example, Table 2 (or Table 3) is used as an example. The first LCG configured by using the fifth configuration information is LCG0, so that the terminal device reports, via LCG0, the amount of data in the buffered data (on the first LCH) whose remaining PDB is less than the PDB threshold. In another example, Table 5 (or Table 6) is used as an example. The first LCG configured by using the fifth configuration information is LCG0, so that the terminal device reports, via LCG0, the amount of data in the buffered data (on the first LCH) whose priority level is less than the priority level threshold.

[0163] For example, the fifth configuration information may be information in LogicalChannelConfig.

[0164] Table 2 (or Table 3, Table 5 or Table 6) is used as an example. The first LCG configured for the first LCH by using the fifth configuration information is denoted as LCG0.

[0165] Figure 10 is used as an example. The first LCG configured for the first LCH (denoted as LCH1) by using the fifth configuration information is denoted as LCG0. Furthermore, in Figure 10, the second LCG configured normally for the first LCH (denoted as LCH1) is denoted as LCG1.

[0166] It can be easily understood that S806 may be executed before S801, and S803 (or S804) and S806 may be executed simultaneously. For example, the first configuration information and the fifth configuration information are transmitted via the same message. Alternatively, the network device first executes S803 (or S804) and then executes S806. This is not limited to the embodiments of this application. In S806, the first LCH is used as an example for explanation. When the terminal device has another LCH, for example, a second LCH that is also used to transmit XR service data, the network device also configures an LCG for the second LCH. The LCG further configured for the first LCH is different from the LCG further configured for the second LCH. Figure 17 is used as an example. When the first LCH is LCH1 and the second LCH is LCH2, the normal LCG configured for the first LCH includes LCG2, LCG4, and LCG6, the LCG further configured for the first LCH (i.e., the first LCG) is LCG0, the normal LCG configured for the second LCH includes LCG3, LCG5, and LCG7, and the LCG further configured for the second LCH is LCG1.

[0167] It should be understood that the combination relationship between the two configuration rules (Configuration Rule 1 and Configuration Rule 2) and the two configuration cases (Configuration Case 1 and Configuration Case 2) is described as follows: When the configuration case of each LCH is Configuration Case 1, the configuration rule used is either the one shown in Table 1 in Configuration Rule 1, or the one shown in Table 4 in Configuration Rule 2. When the configuration case of each LCH is Configuration Case 2, the configuration rule used is either the one shown in Table 2 (or Table 3) in Configuration Rule 1, or the one shown in Table 5 (or Table 6) in Configuration Rule 2.

[0168] The first data will be described below with reference to the above two configuration rules (for example, configuration rule 1 and configuration rule 2).

[0169] In a first possible implementation, the configuration rule in S802 includes configuration rule 1. In this case, the remaining PDB of the first data is within the first remaining PDB range. For details, see the descriptions of Examples 1 and 2.

[0170] Example 1 In Example 1, the configuration case of the first LCH is Configuration Case 1. Correspondingly, the configuration rule used is that shown in Table 1 in Configuration Rule 1. Below, an explanation is provided by using three realization methods (i.e., Realization Method 1 to Realization Method 3 below).

[0171] In implementation scheme 1 in configuration case 1, there are at least two remaining PDBs of buffered data on the first LCH, and the buffered data on the first LCH is reported via different LCGs.

[0172] Specifically, when a first LCG is associated with a first remaining PDB range and the buffered data on the first LCH further includes second data, the BSR indicates not only the first amount of data and the first LCG, but also the second amount of data and the second LCG. The first amount of data corresponds to the first LCG, the first amount of data includes the amount of the first data, and the remaining PDB of the first data is within the first remaining PDB range. The second amount of data corresponds to the second LCG, the second amount of data includes the amount of the second data, and the remaining PDB of the second data is within the second remaining PDB range.

[0173] For example, when the buffered data on the first LCH includes packets in different data bursts, the buffered data on the first LCH will have different remaining PDBs at a given time.

[0174] For example, referring to Table 1 and FIG. 22, still based on the example where the first LCH is LCH1, in the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., indicated as Data 0) is 1 ms, and the remaining PDB range of the remaining PDB is indicated as Remaining PDB Range 1, e.g., 0 ms to 2 ms, and the remaining PDB of another portion of the data (e.g., indicated as Data 1) is 3 ms, and the remaining PDB range of the remaining PDB is indicated as Remaining PDB Range 2, e.g., 2 ms to 4 ms. In this case, the BSR indicates the following four items: LCG0, Data Amount 0, LCG1, and Data Amount 1. In other words, the data amount of Data 0 on LCH1 is reported via LCG0, e.g., Data Amount 0 corresponding to LCG0 includes the data amount of Data 1, and the data amount of Data 1 on LCH1 is reported via LCG1, e.g., Data Amount 1 corresponding to LCG1 includes the data amount of Data 2.

[0175] 11, still based on the example where the first LCH is LCH1, for the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., shown as Data 1) is 1 ms, and the remaining PDB range of the remaining PDB is shown as Remaining PDB Range 1, e.g., 0 ms to 2 ms; the remaining PDB of another portion of the data (e.g., shown as Data 2) is 3 ms, and the remaining PDB range of the remaining PDB is shown as Remaining PDB Range 2, e.g., 2 ms to 4 ms; and the remaining PDB of yet another portion of the data (e.g., shown as Data n) is 2n-1 ms, and the remaining PDB range of the remaining PDB is shown as Remaining PDB Range n, e.g., 2(n-1) ms to 2n ms. In this case, the BSR indicates the following 2n items: LCG1 and data amount 1; LCG2 and data amount 2, ...; and LCGn and data amount n. In other words, the amount of data 1 on LCH1 is reported via LCG1, e.g., data amount 1 corresponding to LCG1 includes the amount of data 1, the amount of data 2 on LCH1 is reported via LCG2, e.g., data amount 2 corresponding to LCG2 includes the amount of data 2, ..., the amount of data n on LCH1 is reported via LCGn, e.g., data amount n corresponding to LCGn includes the amount of data n.

[0176] It can be easily understood that Remaining PDB Range 1 may be considered as the first remaining PDB range, and each of Remaining PDB Range 2 to Remaining PDB Range n may be considered as the second remaining PDB range. For the indication state of the BSR, refer to the description of the first data amount, the first LCG, the second data amount, and the second LCG in Implementation Method 1. Details will not be described again in this specification.

[0177] It can be easily understood that the buffered data on the first LCH may be allocated to a smaller remaining PDB range based on the remaining PDB. For example, the buffered data on the first LCH may be allocated to one remaining PDB range indicated as remaining PDB range 1. In this case, remaining PDB range 1 may be regarded as the first remaining PDB range. For the indication state of the BSR, refer to the description of the first data amount and the first LCG in implementation method 1. Details will not be described again in this specification.

[0178] In other words, even if the buffered data on the first LCH includes data of different remaining PDBs, the terminal device determines at least one LCG indicated by the BSR based on the remaining PDB. In this way, after receiving the BSR, the network device knows at least one data amount, at least one remaining PDB range, and the correspondence between the data amount and the remaining PDB range, and may appropriately allocate uplink resources. For example, when the remaining PDB indicated by the remaining PDB range is small, the network device may preferentially allocate uplink resources based on the data amount corresponding to the remaining PDB range. In another example, when the remaining PDB indicated by the remaining PDB range is large and transmission resources are insufficient, the network device may later allocate uplink resources based on the data amount corresponding to the remaining PDB range, and may preferentially allocate uplink resources to data amounts corresponding to small remaining PDBs, thereby improving uplink scheduling efficiency.

[0179] In implementation 2 of configuration case 1, there is one remaining PDB of buffered data on the first LCH, and the buffered data on the first LCH is reported via one LCG.

[0180] Specifically, when a first LCG is associated with a first remaining PDB range and the buffered data on the first LCH includes packets in a data burst, there is one remaining PDB of buffered data on the first LCH at a certain point in time. When the remaining PDB of the buffered data on the first LCH is within the first remaining PDB range, the buffered data on the first LCH is the first data, or in other words, the buffered data on the first LCH is equivalent to the first data. The first data can be understood to be all of the buffered data on the first LCH. Correspondingly, the BSR indicates a first amount of data and a first LCG, where the first amount of data corresponds to the first LCG, the first amount of data includes the data amount of the first data, and the remaining PDB of the first data is within the first remaining PDB range.

[0181] For example, referring to FIG. 12 , still based on the example where the first LCH is LCH1, at time point 1, the remaining PDB of all buffered data (e.g., shown as Data 1) on LCH1 is 1 ms, and the remaining PDB range of the remaining PDB is shown as Remaining PDB Range 1, e.g., 0 ms to 2 ms. In this case, the BSR indicates the following two items: LCG1 and Data Amount 1. In other words, the data amount of the buffered data (i.e., Data 1) on LCH1 is reported via LCG1, and for example, Data Amount 1 corresponding to LCG1 includes the total data amount of the buffered data on LCH1. At time point 2, the remaining PDB of all buffered data (e.g., shown as Data 1) on LCH1 is 3 ms, and the remaining PDB range of the remaining PDB is shown as Remaining PDB Range 2, e.g., 2 ms to 4 ms, which is not shown in FIG. 12. In this case, the BSR indicates the following two items: LCG2 and Data Amount 2. In other words, the amount of buffered data (i.e., data 1) on LCH1 is reported via LCG2, and for example, data amount 2 corresponding to LCG2 includes all the amounts of buffered data on LCH1.

[0182] In other words, when the buffered data on the first LCH has the same remaining PDB, the terminal device reports the amount of buffered data through one LCG (i.e., the first LCG). In this way, after receiving the BSR, the network device knows the amount of data and the remaining PDB range and can allocate uplink resources so that the terminal device uploads the buffered data on the first LCH in a timely manner. This improves uplink scheduling efficiency.

[0183] In implementation method 3 in configuration case 1, when there are at least two remaining PDBs of buffered data on the first LCH and the smallest remaining PDB of the at least two remaining PDBs is used to determine the remaining PDB range corresponding to the buffered data, the buffered data on the first LCH is reported via the same LCG.

[0184] Specifically, when a first LCG is associated with a first remaining PDB range and the buffered data on the first LCH includes packets in different data bursts, there are at least two remaining PDBs for the buffered data on the first LCH at a given time. When the smallest remaining PDB for the buffered data on the first LCH is used to determine the remaining PDB range corresponding to the buffered data, the remaining PDB for the first data being within the first remaining PDB range can be understood as the smallest remaining PDB for the buffered data on the first LCH being within the first remaining PDB range. The buffered data on the first LCH is the first data. Correspondingly, the BSR indicates a first amount of data and a first LCG, where the first amount of data corresponds to the first LCG, the first amount of data includes the amount of data for the first data, and the remaining PDB for the first data being within the first remaining PDB range.

[0185] For example, referring to Table 1, still based on the example where the first LCH is LCH1, for the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., indicated as Data 0) is 1 ms, and the remaining PDB of another portion of the data (e.g., indicated as Data 1) is 3 ms. When the minimum remaining PDB of the buffered data on LCH1 is used to determine the remaining PDB range of the buffered data, the minimum remaining PDB is 1 ms, and the remaining PDB range of the remaining PDB is indicated as Remaining PDB Range 1, e.g., 0 ms to 2 ms. In this case, the BSR indicates the following two items: LCG0 and Data Amount 0. In other words, all data amounts of the buffered data (i.e., Data 0 and Data 1) on LCH1 are reported via LCG0, and for example, Data Amount 0 corresponding to LCG0 includes all data amounts of the buffered data on LCH1.

[0186] For example, referring to FIG. 13 , still based on the example where the first LCH is LCH1, for the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., designated as Data 1) is 1 ms, the remaining PDB of another portion of the data (e.g., designated as Data 2) is 3 ms, and the remaining PDB of yet another portion of the data (e.g., designated as Data n) is 2n−1 ms. When the minimum remaining PDB of the buffered data on LCH1 is used to determine the remaining PDB range of the buffered data, the minimum remaining PDB is 1 ms, and the remaining PDB range of the remaining PDB is designated as Remaining PDB Range 1, e.g., 0 ms to 2 ms. In this case, the BSR indicates the following two items: LCG1 and Data Amount 1. In other words, all data amounts of the buffered data (i.e., Data 1 to Data n) on LCH1 are reported via LCG1. Correspondingly, Data Amount 1 corresponding to LCG1 includes all data amounts of the buffered data on LCH1.

[0187] In other words, even if the buffered data on the first LCH includes data of different remaining PDBs, the terminal device determines the LCG indicated by the BSR based on the smallest remaining PDB. In this way, after receiving the BSR, the network device may know the amount of data and the remaining PDB range and appropriately allocate uplink resources. For example, when the remaining PDB indicated by the remaining PDB range is small, the network device may preferentially allocate uplink resources based on the amount of data corresponding to the remaining PDB range, thereby improving uplink scheduling efficiency.

[0188] Example 2 In Example 2, the configuration case of the first LCH is Configuration Case 2. Correspondingly, the configuration rules used are those shown in Table 2 (or Table 3) in Configuration Rule 1. Below, an explanation is provided by using three implementation methods (i.e., Implementation Methods 4 to 6 below).

[0189] In implementation scheme 4 in configuration case 2, there are at least two remaining PDBs of buffered data on the first LCH, and the buffered data on the first LCH is reported via different LCGs.

[0190] Specifically, when a first LCG is associated with a first remaining PDB range and the buffered data on the first LCH further includes second data, the BSR indicates not only the first amount of data and the first LCG, but also the second amount of data and the second LCG. The first amount of data corresponds to the first LCG, the first amount of data includes the amount of the first data, and the remaining PDB of the first data is within the first remaining PDB range. The second amount of data corresponds to the second LCG, the second amount of data includes the amount of the second data, and the remaining PDB of the second data is within the second remaining PDB range.

[0191] For example, referring to Table 2 (or Table 3), still based on the example where the first LCH is LCH1, the PDB threshold is set to 2 ms, i.e., T=2 ms. In the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., shown as Data 0) is 1 ms, the remaining PDB is less than the PDB threshold, and the remaining PDB range of the remaining PDB is shown as Remaining PDB Range 1, e.g., 0 ms to 2 ms, and the remaining PDB of another portion of the data (e.g., shown as Data 1) is 3 ms, the remaining PDB is greater than the PDB threshold, and the remaining PDB range of the remaining PDB is shown as Remaining PDB Range 2, e.g., 2 ms to 4 ms. In this case, the BSR indicates the following four items: LCG0, Data Amount 0, LCG1, and Data Amount 1. In other words, the amount of data for data 0 on LCH1 is reported via LCG0, e.g., data amount 0 corresponding to LCG0 includes the amount of data for data 1, and the amount of data for data 1 on LCH1 is reported via LCG1, e.g., data amount 1 corresponding to LCG1 includes the amount of data for data 2.

[0192] For example, referring to FIG. 14 , still based on the example where the first LCH is LCH1, in the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., shown as Data 1) is 1 ms, and the remaining PDB range of the remaining PDB is shown as Remaining PDB Range 1, e.g., 0 ms to 2 ms, and the remaining PDB of another portion of the data (e.g., shown as Data 2) is 3 ms, and the remaining PDB range of the remaining PDB is shown as Remaining PDB Range 2, e.g., 2 ms to 30 ms. In this case, the BSR indicates the following four items: LCG0, Data Amount 0, LCG1, and Data Amount 1. In other words, the data amount of Data 1 on LCH1 is reported via LCG0, e.g., Data Amount 0 corresponding to LCG0 includes the data amount of Data 1, and the data amount of Data 2 on LCH1 is reported via LCG1, e.g., Data Amount 1 corresponding to LCG1 includes the data amount of Data 2.

[0193] It can be easily understood that the buffered data on the first LCH may be allocated to a smaller remaining PDB range based on the remaining PDB. For example, if all the remaining PDBs of the buffered data on the first LCH are less than the PDB threshold, the buffered data on the first LCH is allocated to one remaining PDB range indicated as remaining PDB range 1. Remaining PDB range 1 may be considered as the first remaining PDB range. For the indication state of the BSR, refer to the description of the first data amount and the first LCG in implementation method 4. Details will not be described again in this specification. For example, referring to FIG. 23, based on an example in which the first LCH is any one of LCH1 to LCHn, for the buffered data on the first LCH, when the remaining PDB of the buffered data is less than the PDB threshold (θ), the data amount of the buffered data (i.e., the first data amount) is reported via the first LCG.

[0194] Alternatively, if all remaining PDBs of buffered data on the first LCH are greater than the PDB threshold, the buffered data on the first LCH are allocated to one remaining PDB range, designated as remaining PDB range 2. Remaining PDB range 2 may be considered as the second remaining PDB range. For the indication state of the BSR, refer to the description of the second data amount and the second LCG in implementation method 4. Details will not be described again in this specification.

[0195] In other words, even if the buffered data on the first LCH includes data of a different remaining PDB, the terminal device determines at least one LCG indicated by the BSR based on the remaining PDB. For example, when the remaining PDB is less than the PDB threshold, the terminal device reports the amount of a portion of the data via the first LCG, or when the remaining PDB is equal to or greater than the PDB threshold, the terminal device reports the amount of a portion of the data via the second LCG. In this way, after receiving the BSR, the network device knows at least one data amount, at least one remaining PDB range, and the correspondence between the data amount and the remaining PDB range, and may appropriately allocate uplink resources. For example, when the remaining PDB indicated by the remaining PDB range is small, the network device preferentially allocates uplink resources based on the data amount corresponding to the remaining PDB range. In another example, when the remaining PDB indicated by the remaining PDB range is large and transmission resources are insufficient, the network device may later allocate uplink resources based on the amount of data corresponding to the remaining PDB range, and may preferentially allocate uplink resources to the amount of data corresponding to a small remaining PDB to improve uplink scheduling efficiency.

[0196] In implementation scheme 5 for configuration case 2, there is one remaining PDB of buffered data on the first LCH, and the buffered data on the first LCH is reported via one LCG.

[0197] Specifically, when a first LCG is associated with a first remaining PDB range and the buffered data on the first LCH includes packets in a data burst, there is one remaining PDB of buffered data on the first LCH at a certain point in time. When the remaining PDB of the buffered data on the first LCH is within the first remaining PDB range, the buffered data on the first LCH is the first data, or in other words, the buffered data on the first LCH is equivalent to the first data. The first data can be understood to be all of the buffered data on the first LCH. Correspondingly, the BSR indicates a first amount of data and a first LCG, where the first amount of data corresponds to the first LCG, the first amount of data includes the data amount of the first data, and the remaining PDB of the first data is within the first remaining PDB range.

[0198] For example, referring to FIG. 15 , still based on the example where the first LCH is LCH1, the PDB threshold is set to 2 ms, i.e., T=2 ms. At time point 1, the remaining PDB of all buffered data (e.g., shown as Data 1) on LCH1 is 1 ms, the remaining PDB is less than the PDB threshold, and the remaining PDB range of the remaining PDB is shown as Remaining PDB Range 1, e.g., 0 ms to 2 ms. In this case, the BSR indicates the following two items: LCG0 and Data Amount 0. In other words, all data amounts of buffered data (i.e., Data 1) on LCH1 are reported via LCG1, e.g., Data Amount 0 corresponding to LCG0 includes all data amounts of buffered data on LCH1. At time point 2, the total remaining PDB of all buffered data on LCH1 is 3 ms, the remaining PDB is greater than the PDB threshold, and the remaining PDB range of the remaining PDB is shown as remaining PDB range 2, e.g., 2 ms to 30 ms, which is not shown in FIG. 15. In this case, the BSR indicates the following two items: LCG1 and data amount 1. In other words, all data amounts of buffered data on LCH1 are reported via LCG1, for example, data amount 1 corresponding to LCG1 includes all data amounts of buffered data on LCH1.

[0199] In other words, when the buffered data on the first LCH has the same remaining PDB, for example, when the remaining PDB is less than the PDB threshold, or when the remaining PDB is equal to or greater than the PDB threshold, the terminal device reports the amount of buffered data through one LCG (i.e., the first LCG). In this way, after receiving the BSR, the network device knows the data amount and remaining PDB range and can allocate uplink resources so that the terminal device uploads the buffered data on the first LCH in a timely manner. This improves uplink scheduling efficiency.

[0200] In implementation method 6 in configuration case 2, when there are at least two remaining PDBs of buffered data on the first LCH and the smallest remaining PDB of the at least two remaining PDBs is used to determine the remaining PDB range corresponding to the buffered data, the buffered data on the first LCH is reported via the same LCG.

[0201] Specifically, when a first LCG is associated with a first remaining PDB range and the buffered data on the first LCH includes packets in different data bursts, there are at least two remaining PDBs for the buffered data on the first LCH at a given time. When the smallest remaining PDB for the buffered data on the first LCH is used to determine the remaining PDB range corresponding to the buffered data, the remaining PDB for the first data being within the first remaining PDB range can be understood as the smallest remaining PDB for the buffered data on the first LCH being within the first remaining PDB range, e.g., the smallest remaining PDB for the buffered data on the first LCH being less than the PDB threshold. The buffered data on the first LCH is the first data. Correspondingly, the BSR indicates a first amount of data and a first LCG, where the first amount of data corresponds to the first LCG, the first amount of data includes the amount of data for the first data, and the remaining PDB for the first data being within the first remaining PDB range.

[0202] For example, referring to Table 2 (or Table 3), still based on the example where the first LCH is LCH1, for the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., indicated as Data 0) is 1 ms, and the remaining PDB of another portion of the data (e.g., indicated as Data 1) is 3 ms. When the minimum remaining PDB of the buffered data on LCH1 is used to determine the remaining PDB range of the buffered data, the minimum remaining PDB is 1 ms, and the remaining PDB range of the remaining PDB is indicated as Remaining PDB Range 1, e.g., 0 ms to 2 ms. In this case, the BSR indicates the following two items: LCG0 and Data Amount 0. In other words, all data amounts of the buffered data (i.e., Data 0 and Data 1) on LCH1 are reported via LCG0, and for example, Data Amount 0 corresponding to LCG0 includes all data amounts of the buffered data on LCH1.

[0203] For example, referring to FIG. 16 , still based on the example where the first LCH is LCH1, the PDB threshold is set to 2 ms, i.e., T=2 ms. For the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., denoted as Data 1) is 1 ms, and the remaining PDB of another portion of the data (e.g., denoted as Data 2) is 3 ms. When the minimum remaining PDB of the buffered data on LCH1 is used to determine the remaining PDB range of the buffered data, the minimum remaining PDB is 1 ms, the remaining PDB is less than the PDB threshold, and the remaining PDB range of the remaining PDB is denoted as Remaining PDB Range 1, e.g., 0 ms to 2 ms. In this case, the BSR indicates the following two items: LCG0 and Data Amount 0. In other words, all data amounts of the buffered data (i.e., Data 1 and Data 2) on LCH1 are reported via LCG0. Correspondingly, Data Amount 0 corresponding to LCG0 includes all data amounts of the buffered data on LCH1.

[0204] In other words, even if the buffered data on the first LCH includes data of different remaining PDBs, the terminal device determines the LCG indicated by the BSR based on the smallest remaining PDB. In this way, after receiving the BSR, the network device may know the amount of data and the remaining PDB range and appropriately allocate uplink resources. For example, when the remaining PDB indicated by the remaining PDB range is less than the PDB threshold, the network device may preferentially allocate uplink resources based on the amount of data corresponding to the remaining PDB range, thereby improving uplink scheduling efficiency.

[0205] In another possible implementation, the configuration rule in S802 includes configuration rule 2. In this case, the priority level of the first data is within a first priority level range, and the priority level of the first data is determined based on the remaining PDB of the first data and the data type of the first data. For details, see the descriptions of Examples 3 and 4.

[0206] Example 3 In Example 3, the configuration case of the first LCH is Configuration Case 1. Correspondingly, the configuration rule used is that shown in Table 4 in Configuration Rule 2. Below, we provide an explanation by using two implementation methods (Implementation Method 7 and Implementation Method 8 below).

[0207] In Example 3, the priority level is determined based on the remaining PDB of buffered data and the data type of the buffered data.

[0208] First, the function of data type in the priority level determination process will be described. First data is used as an example. When the first data is data of a first type, the first LCG is an LCG in a first set. The first set includes at least one LCG, and each LCG in the first set is used to transmit data of the first type. Alternatively, when the first data is data of a second type, the first LCG is an LCG in a second set. The second set includes at least one LCG, and each LCG in the second set is used to transmit data of the second type. Each LCG in the first set is different from each LCG in the second set.

[0209] As shown in FIG. 17, the first type of data may be I type, i.e., data of an I frame, and the second type of data may be P type, i.e., data of a P frame, and the first set includes LCG0, LCG2, LCG4, and LCG6, and the second set includes LCG1, LCG3, LCG5, and LCG7.

[0210] 17, when the first data is data of an I-frame, the first LCH may be LCH1, and the first LCG is one of LCG0, LCG2, LCG4, and LCG6. The specific LCG to which the first data is mapped is determined based on the remaining PDB of the first data. For details, see the following descriptions of Implementations 7 and 8.

[0211] 17, when the first data is data of a P frame, the first LCH may be LCH2, and the first LCG is one of LCG1, LCG3, LCG5, and LCG7. The specific LCG to which the first data is mapped is determined based on the remaining PDB of the first data. For details, see the following descriptions of Implementations 7 and 8.

[0212] Next, the function of the remaining PDB in the priority level determination process will be described. The first data is used as an example. When the buffered data on the first LCH are the same type of data and there is one remaining PDB for the buffered data on the first LCH, the first data is all of the buffered data on the first LCH. For details, please refer to the description of Implementation Scheme 7 in Configuration Case 1.

[0213] When the buffered data on the first LCH are the same type of data and there are at least two remaining PDBs of the buffered data on the first LCH, the priority level of the buffered data is determined based on the smallest remaining PDB of the buffered data on the first LCH, and the first data is all of the buffered data on the first LCH. For details, see the description of Implementation Scheme 8 in Configuration Case 1.

[0214] For example, implementation method 7 in configuration case 1 and implementation method 8 in configuration case 1 are described as follows:

[0215] In implementation scheme 7 in configuration case 1, there is one remaining PDB of buffered data on the first LCH, and the buffered data on the first LCH is reported via one LCG.

[0216] Specifically, when a first LCG is associated with a first priority level range and the buffered data on the first LCH includes packets in a data burst, there is one remaining PDB of buffered data on the first LCH at a certain point in time. When the priority level of the buffered data on the first LCH is within the first priority level range, the buffered data on the first LCH is the first data, or in other words, the buffered data on the first LCH is equivalent to the first data. The first data can be understood to be all of the buffered data on the first LCH. Correspondingly, the BSR indicates a first amount of data and a first LCG, where the first amount of data corresponds to the first LCG, the first amount of data includes the data amount of the first data, and the remaining PDB of the first data is within the first remaining PDB range.

[0217] For example, referring to FIG. 18 or FIG. 24, still based on the example where the first LCH is LCH1, at time point 1, the total remaining PDB of the buffered data (e.g., shown as Data 1) on LCH1 is 1 ms, and the priority level determined based on the remaining PDB is within priority level range 1, e.g., 1 to 2. In this case, the BSR indicates the following two items: LCG1 and data amount 1. In other words, the total data amount of the buffered data (e.g., Data 1) on LCH1 is reported via LCG1, and for example, data amount 1 corresponding to LCG1 includes the total data amount of the buffered data on LCH1. At time point 2, the total remaining PDB of the buffered data (e.g., shown as Data 2) on LCH1 is 3 ms, and the priority level determined based on the remaining PDB is within priority level range 2, e.g., 3 to 4. Priority level range 2 is not shown in FIG. 18. In this case, the BSR indicates the following two items: LCG2 and data amount 2. In other words, the total amount of buffered data (e.g., data 2) on LCH1 is reported via LCG2, and for example, data amount 2 corresponding to LCG2 includes the total amount of buffered data on LCH1.

[0218] In other words, when the buffered data on the first LCH are the same type of data and have the same remaining PDB, the terminal device reports the amount of buffered data through one LCG (i.e., the first LCG). In this way, after receiving the BSR, the network device knows the data amount and priority level range and can allocate uplink resources so that the terminal device uploads the buffered data on the first LCH in a timely manner. This improves uplink scheduling efficiency.

[0219] In implementation method 8 in configuration case 1, when there are at least two remaining PDBs of buffered data on the first LCH and the smallest remaining PDB of the at least two remaining PDBs is used to determine the priority level range corresponding to the buffered data, the buffered data on the first LCH is reported via the same LCG.

[0220] Specifically, when a first LCG is associated with a first priority level range and the buffered data on the first LCH includes packets in different data bursts, there are at least two remaining PDBs of the buffered data on the first LCH at a certain time. When the smallest remaining PDB of the buffered data on the first LCH is used to determine the priority level range corresponding to the buffered data, the remaining PDB of the first data being within the first priority level range can be understood as the smallest remaining PDB of the buffered data on the first LCH being within the first priority level range. The buffered data on the first LCH is the first data. Correspondingly, the BSR indicates a first amount of data and a first LCG, where the first amount of data corresponds to the first LCG, the first amount of data includes the amount of data of the first data, and the remaining PDB of the first data being within the first remaining PDB range.

[0221] For example, referring to Table 2 (or Table 3), still based on the example where the first LCH is LCH1, for the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., indicated as Data 0) is 1 ms, and the remaining PDB of another portion of the data (e.g., indicated as Data 1) is 3 ms. When the priority level of the buffered data is determined based on the minimum remaining PDB of the buffered data on LCH1, the minimum remaining PDB is 1 ms, and the priority level range determined based on the remaining PDB is indicated as priority level range 1, e.g., 1 to 2. In this case, the BSR indicates the following two items, i.e., LCG0 and data amount 0. In other words, all data amounts of the buffered data (i.e., Data 0 and Data 1) on LCH1 are reported via LCG0, and for example, data amount 0 corresponding to LCG0 includes all data amounts of the buffered data on LCH1.

[0222] For example, referring to FIG. 19 , still based on the example where the first LCH is LCH1, for the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., designated as Data 1) is 1 ms, the remaining PDB of another portion of the data (e.g., designated as Data 2) is 3 ms, and the remaining PDB of yet another portion of the data (e.g., designated as Data n) is 2n−1 ms. When the priority level range of the buffered data is determined based on the minimum remaining PDB of the buffered data on LCH1, the minimum remaining PDB is 1 ms, and the priority level range determined based on the remaining PDB is indicated as priority level range 1, e.g., 1 to 2. In this case, the BSR indicates the following two items: LCG1 and data amount 1. In other words, all data amounts of the buffered data (i.e., Data 1 to Data n) on LCH1 are reported via LCG1, and for example, data amount 1 corresponding to LCG1 includes all data amounts of the buffered data on LCH1.

[0223] In other words, even if the buffered data on the first LCH includes data of different remaining PDBs, the terminal device determines the priority level of the buffered data based on the smallest remaining PDB and determines the LCG indicated by the BSR based on the priority level of the buffered data. In this way, after receiving the BSR, the network device may know the data amount and the priority level range and appropriately allocate uplink resources. For example, when the priority level indicated by the priority level range is low, the network device may preferentially allocate uplink resources based on the data amount corresponding to the priority level range, thereby improving uplink scheduling efficiency.

[0224] In Example 3, it can be easily understood that the network device configures one priority level range for each LCH. The first LCH is used as an example. As shown in Figure 27, the logical channel grouping method in this embodiment of the present application further includes S807.

[0225] S807: The network device sends the fourth configuration information to the terminal device. In response, the terminal device receives the fourth configuration information from the network device.

[0226] The fourth configuration information is used to configure a priority level range corresponding to the first LCH. For example, the priority level range configured by using the fourth configuration information includes all or part of the L priority level ranges. The first LCH may be dynamically adjusted within the priority level range corresponding to the first LCH. For example, the priority level range corresponding to the first LCH is 1 to 16. At time point 1, the priority level of the first LCH is priority level 1. At time point 2, the priority level of the first LCH is priority level 2. For details, refer to the descriptions of implementation method 7 in configuration case 1 and implementation method 8 in configuration case 1. The details will not be described again in this specification.

[0227] For example, the fourth configuration information may be information in LogicalChannelConfig, such as priorityRange:SEQUENCE(SIZE(1...8)) OF INTEGER(0...16).

[0228] It should be understood that in this embodiment of the present application, an example is used in which the first data is all of the buffered data on the first LCH, and the priority level of the first data is equal to the priority level of the first LCH, and the two may be interchangeable.

[0229] Table 2 (or Table 3) is used as an example. The priority level range configured for the first LCH by using the fourth configuration information is shown as (1, 16). In other words, the priority level of the first LCH may be dynamically adjusted among 16 priorities (i.e., priority level 1 to priority level 16).

[0230] 18 (or 19) is used as an example. The LCG range configured for the first LCH (denoted as LCH1) by using the second configuration information is denoted as (1, 2n). In other words, the priority level of the first LCH may be dynamically adjusted among 2n priority levels (i.e., priority level 1 to priority level n).

[0231] It can be easily understood that S807 may be executed before S801, and S806 and S807 may be executed simultaneously. For example, the fourth configuration information and the fifth configuration information are transmitted via the same message. Alternatively, the network device may first execute S806 and then execute S807. This is not limited in the embodiments of this application. In S807, the first LCH is used as an example for explanation. When the terminal device has another LCH, for example, a second LCH that is also used to transmit XR service data, the network device also configures a priority level range for the second LCH. The priority level range configured for the first LCH may be the same as or different from the priority level range configured for the second LCH. This is not limited in the embodiments of this application.

[0232] Example 4 In Example 4, the configuration case of the first LCH is Configuration Case 2. Correspondingly, the configuration rule used is that shown in Table 5 (or Table 6) in Configuration Rule 2. Below, we provide an explanation by using two implementation methods (Implementation Method 9 and Implementation Method 10 below).

[0233] In Example 4, the priority level is still determined based on the remaining PDB of buffered data and the data type of the buffered data.

[0234] For the function of data types in the priority level determination process, please refer to the explanation in Example 3. The details will not be described again here.

[0235] Next, the function of the remaining PDB in the priority level determination process will be described. The first data is used as an example. When the buffered data on the first LCH are the same type of data and there is one remaining PDB for the buffered data on the first LCH, the first data is all of the buffered data on the first LCH. For details, please refer to the description of Implementation Scheme 9 in Configuration Case 2.

[0236] When the buffered data on the first LCH are the same type of data and there are at least two remaining PDBs of the buffered data on the first LCH, the priority level of the buffered data is determined based on the smallest remaining PDB of the buffered data on the first LCH, and the first data is all of the buffered data on the first LCH. For details, see the description of the implementation method 10 in configuration case 2.

[0237] For example, implementation method 9 in configuration case 2 and implementation method 10 in configuration case 2 are described as follows:

[0238] In implementation 9 in configuration case 2, there is one remaining PDB of buffered data on the first LCH, and the buffered data on the first LCH is reported via one LCG.

[0239] Specifically, when a first LCG is associated with a first priority level range and the buffered data on the first LCH includes packets in a data burst, there is one remaining PDB of buffered data on the first LCH at a certain point in time. When the priority level of the buffered data on the first LCH is within the first priority level range, e.g., less than a priority level threshold, the buffered data on the first LCH is the first data; in other words, the buffered data on the first LCH is equivalent to the first data. The first data can be understood to be all of the buffered data on the first LCH. Correspondingly, the BSR indicates a first amount of data and a first LCG, where the first amount of data corresponds to the first LCG, the first amount of data includes the data amount of the first data, and the remaining PDB of the first data is within the first remaining PDB range.

[0240] For example, referring to FIG. 20 , still based on the example where the first LCH is LCH1, the priority level threshold is set to 2 ms, i.e., K=2. Normal LCGs configured for the first LCH include LCG2, LCG4, and LCG6. For details, see the related art. An LCG further configured for the first LCH is LCG0. At time point 1, the total remaining PDB of buffered data (e.g., indicated as Data0) on LCH1 is 1 ms, the priority level (e.g., priority level is 1) determined based on the remaining PDB is less than the priority level threshold, and the priority level range determined based on the remaining PDB is indicated as priority level range 1, e.g., 1 to K. In this case, the BSR indicates the following two items: LCG0 and data amount 0. In other words, all data amounts of buffered data (i.e., Data0) on LCH1 are reported via LCG0, and for example, data amount 0 corresponding to LCG0 includes all data amounts of buffered data on LCH1. At time point 2, the total remaining PDB of the buffered data on LCH1 is 3 ms, the priority level determined based on the remaining PDB (e.g., the priority level is 3) is greater than the priority level threshold, and the priority level range determined based on the remaining PDB is indicated as priority level range 2, e.g., K to Kmax, which is not shown in FIG. 20. In this case, the BSR indicates the following two items: LCG1 and data amount 1. In other words, the total data amount of the buffered data on LCH1 is reported via LCG1, for example, data amount 1 corresponding to LCG1 includes the total data amount of the buffered data on LCH1.

[0241] An example is used in which the first LCH is LCH2. The priority level threshold is set to 2 ms, i.e., K=2. Normal LCGs configured for the first LCH include LCG3, LCG5, and LCG7. For details, see the related art. An LCG further configured for the first LCH is LCG1. At time 1, the remaining PDB of all buffered data on LCH2 is 1 ms, the priority level determined based on the remaining PDB (e.g., the priority level is 1) is less than the priority level threshold, and the priority level range determined based on the remaining PDB is indicated as priority level range 1, e.g., 1 to K. In this case, the BSR indicates the following two items: LCG1 and data amount 1. In other words, the data amount of all buffered data on LCH2 is reported via LCG1, and for example, data amount 1 corresponding to LCG1 includes all data amounts of buffered data on LCH2.

[0242] In other words, when the buffered data on the first LCH are of the same type and have the same remaining PDB, for example, when the priority level determined based on the remaining PDB is less than the priority level threshold, or when the priority level determined based on the remaining PDB is equal to or greater than the priority level threshold, the terminal device reports the amount of buffered data via one LCG (i.e., the first LCG). In this way, after receiving the BSR, the network device knows the data amount and priority level range and can allocate uplink resources so that the terminal device uploads the buffered data on the first LCH in a timely manner. This improves uplink scheduling efficiency.

[0243] In the implementation method 10 in configuration case 2, when there are at least two remaining PDBs of buffered data on the first LCH and the smallest PDB of the at least two remaining PDBs is used to determine the priority level range corresponding to the buffered data, the buffered data on the first LCH is reported via the same LCG.

[0244] Specifically, when a first LCG is associated with a first priority level range and the buffered data on the first LCH includes packets in different data bursts, there are at least two remaining PDBs of the buffered data on the first LCH at a certain time. When the smallest remaining PDB of the buffered data on the first LCH is used to determine the priority level range corresponding to the buffered data, the priority level of the first data being within the first priority level range can be understood as the lowest priority level of the buffered data on the first LCH being within the first priority level range. The lowest priority level is determined based on the smallest remaining PDB of the at least two remaining PDBs. The buffered data on the first LCH is the first data. Correspondingly, the BSR indicates a first amount of data and a first LCG, where the first amount of data corresponds to the first LCG, the first amount of data includes the first amount of data, and the remaining PDB of the first data is within the first remaining PDB range.

[0245] For example, referring to Table 5 (or Table 6), still based on the example where the first LCH is LCH1, for the buffered data on LCH1, the remaining PDB of a portion of the data (e.g., indicated as Data 0) is 1 ms, and the remaining PDB of another portion of the data (e.g., indicated as Data 1) is 3 ms. When the priority level of the buffered data is determined based on the minimum remaining PDB of the buffered data on LCH1, the minimum remaining PDB is 1 ms, and the priority level range determined based on the remaining PDB is indicated as priority level range 1, e.g., 1 to 2. In this case, the BSR indicates the following two items, i.e., LCG0 and data amount 0. In other words, all data amounts of the buffered data (i.e., Data 0 and Data 1) on LCH1 are reported via LCG0, and for example, data amount 0 corresponding to LCG0 includes all data amounts of the buffered data on LCH1.

[0246] For example, referring to FIG. 21 , still based on the example where the first LCH is LCH1, the priority level threshold is set to 2, i.e., K=2. Normal LCGs configured for the first LCH include LCG2, LCG4, and LCG6. For details, see the related art. An additional LCG configured for the first LCH is LCG0. For buffered data on LCH1, the remaining PDB of a portion of the data (e.g., indicated as Data0) is 1 ms, and the remaining PDB of another portion of the data (e.g., indicated as Data1) is 3 ms. When the priority level range of the buffered data is determined based on the minimum remaining PDB of the buffered data on LCH1, the minimum remaining PDB is 1 ms, the priority level determined based on the remaining PDB (e.g., the priority level is 1) is less than the priority level threshold, and the priority level range determined based on the remaining PDB is indicated as a priority level range 1, e.g., 1 to K. In this case, the BSR indicates the following two items, i.e., LCG0 and data amount 0. In other words, all data amounts of buffered data (i.e., Data 0 and Data 1) on LCH1 are reported via LCG0. Correspondingly, Data Amount 0 corresponding to LCG0 includes all data amounts of buffered data on LCH1.

[0247] For example, assume that the first LCH is LCH2. The priority level threshold is set to 2, i.e., K=2. Normal LCGs configured for the first LCH include LCG3, LCG5, and LCG7. For details, see the related art. An additional LCG configured for the first LCH is LCG1. For buffered data on LCH2, the remaining PDB of a portion of the data is 1 ms, and the remaining PDB of another portion of the data is 3 ms. When the priority level range of the buffered data is determined based on the minimum remaining PDB of the buffered data on LCH2, the minimum remaining PDB is 1 ms, and the priority level determined based on the remaining PDB (e.g., priority level 1) is less than the priority level threshold, and the priority level range determined based on the remaining PDB is indicated as priority level range 1, e.g., 1 to K. In this case, the BSR indicates the following two items: LCG1 and data amount 1. In other words, the data amount of all buffered data on LCH2 is reported via LCG1. Correspondingly, the data amount 1 corresponding to LCG1 includes all the data amounts buffered on LCH2.

[0248] In other words, even if the buffered data on the first LCH includes data of different remaining PDBs, the terminal device determines the priority level of the buffered data based on the smallest remaining PDB, and then determines the LCG indicated by the BSR based on the priority level of the buffered data. In this way, after receiving the BSR, the network device may know the data amount and the priority level range and appropriately allocate uplink resources. For example, when the priority level indicated by the priority level range is less than the priority level threshold, the network device preferentially allocates uplink resources based on the data amount corresponding to the priority level range, thereby improving uplink scheduling efficiency.

[0249] After receiving the BSR, the network device executes S808.

[0250] S808: The network device allocates uplink resources to the terminal device based on the first amount of data and the first LCG according to a preset configuration rule.

[0251] The configuration rules in S808 are the same as those in S802, and the details will not be described again in this specification.

[0252] For example, when the BSR indicates a first amount of data and a first LCG, and the first LCG is associated with a first remaining PDB range, the network device allocates uplink resources to the terminal device based on the first remaining PDB range and the first amount of data.

[0253] For example, when the first remaining PDB range is 29 ms to 30 ms, the network device may allocate uplink resources to the terminal device later (e.g., 5 ms or 10 ms after the BSR is received). During this period (e.g., after the network device receives the BSR in S802 and before the network device allocates uplink resources based on the BSR), the network device may preferentially allocate uplink resources to other terminal devices.

[0254] In another example, when the first remaining PDB range is 0 ms to 2 ms, the network device preferentially allocates uplink resources to the terminal device (eg, 1 ms after the BSR is received).

[0255] When the first LCG is associated with the first priority level range, the network device allocates uplink resources to the terminal device based on the first priority level range and the first amount of data.

[0256] For example, when the first priority level range is 15 to 16, the network device may allocate uplink resources to the terminal device later (e.g., 5 ms or 10 ms after the BSR is received). During this period (e.g., after the network device receives the BSR in S802 and before the network device allocates uplink resources based on the BSR), the network device may preferentially allocate uplink resources to other terminal devices.

[0257] In another example, when the first priority level range is 1 to 2, the network device preferentially allocates uplink resources to the terminal device (eg, 1 ms after the BSR is received).

[0258] In some embodiments, when the BSR further indicates a second amount of data and a second LCG, and when the second LCG is associated with a second remaining PDB range, the network device allocates uplink resources to the terminal device based on the first remaining PDB range, the first amount of data, the second remaining PDB range, and the second amount of data.

[0259] When the second LCG is associated with the second priority level range, the network device allocates uplink resources to the terminal device based on the first priority level range, the first amount of data, the second priority level range, and the second amount of data.

[0260] For a terminal device, after uplink resources are allocated to the terminal device, the terminal device preferentially transmits buffered data corresponding to a first amount of data on the uplink resources. Optionally, when sufficient uplink resources are allocated to the terminal device, the terminal device further transmits buffered data corresponding to a second amount of data on the uplink resources. For details, please refer to the related art. The details will not be described again in this specification.

[0261] In this embodiment of the present application, it can be easily understood that two or more of the five pieces of configuration information (the first to fifth pieces of configuration information) may be transmitted via the same message, but this is not limited to this embodiment of the present application.

[0262] The above describes the solutions provided in the embodiments of this application mainly from the perspective of interactions between network elements. Correspondingly, the embodiments of this application also provide a communication device. The communication device may be a network element in the above method embodiment, a device including the above network element, or a component that can be used in a network element. To realize the above functions, it can be understood that the communication device includes corresponding hardware structures and / or software modules for performing each function. In combination with the examples described in the embodiments disclosed in this specification, those skilled in the art should easily recognize that the units and algorithm steps in this application can be realized by hardware or a combination of hardware and computer software. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to realize the described functions for each specific application, but the implementation method should not be considered to go beyond the scope of this application.

[0263] For example, Figure 28 is a diagram of the structure of a communication device according to an embodiment of this application. The communication device may be a terminal device, or a chip (system) or other part or component that may be disposed in a terminal device. Alternatively, the communication device may be a network device, or a chip (system) or other part or component that may be disposed in a network device.

[0264] 28, the communications device 2800 may include a processor 2801. Optionally, the communications device 2800 may further include a memory 2802 and / or a transceiver 2803. The processor 2801 is coupled to the memory 2802 and the transceiver 2803. For example, the processor 2801, the memory 2802, and the transceiver 2803 may be connected via a communications bus.

[0265] Each component of the communication device 2800 will be described in detail below with reference to FIG.

[0266] Processor 2801 is the control center of communication device 2800 and may be a single processor or a collective term for multiple processing elements. For example, processor 2801 may be one or more central processing units (CPUs), or application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement embodiments of this application, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0267] Optionally, the processor 2801 may execute software programs stored in the memory 2802 and access data stored in the memory 2802 to perform various functions of the communication device 2800.

[0268] In a specific implementation, in an embodiment, the processor 2801 may include one or more CPUs, for example, CPU0 and CPU1 shown in FIG.

[0269] In a specific implementation, in an embodiment, communications device 2800 may alternatively include multiple processors, such as processor 2801 and processor 2804 shown in FIG. 28. Each processor may be a single-core processor (single CPU) or a multi-core processor (multiple CPUs). A processor herein may refer to one or more devices, circuits, and / or processing cores configured to process data (e.g., computer program instructions).

[0270] The memory 2802 is configured to store a software program for implementing the solution of this application, and the processor 2801 controls the execution of the software program. For specific implementation manners, please refer to the above method embodiments. Details will not be described again in this specification.

[0271] Optionally, memory 2802 may be read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, or random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or may be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium usable to carry or store expected program code in the form of instructions or data structures and accessible by a computer. However, this is not limited thereto. Memory 2802 may be integrated with processor 2801 or may exist separately and be coupled to processor 2801 through an interface circuit (not shown in FIG. 28 ) of communication device 2800. This is not particularly limited in the embodiments of this application.

[0272] The transceiver 2803 is configured to communicate with other communication devices. For example, the communication device 2800 may be a terminal device and the transceiver 2803 may be configured to communicate with a network device. In another example, the communication device 2800 may be a network device and the transceiver 2803 may be configured to communicate with a terminal device.

[0273] Optionally, the transceiver 2803 may include a receiver and a transmitter (not shown separately in FIG. 28), where the receiver is configured to implement a receiving function and the transmitter is configured to implement a transmitting function.

[0274] Optionally, the transceiver 2803 may be integrated with the processor 2801 or may exist independently and be coupled to the processor 2801 through an interface circuit (not shown in FIG. 28) of the communication device 2800. This is not particularly limited in the embodiments of this application.

[0275] It can be readily understood that the structure of the communications device 2800 shown in Figure 28 does not constitute a limitation on the communications device. An actual communications device may include more or fewer components than those shown in the drawings, may combine some components, or may have a different arrangement of components.

[0276] Furthermore, the technical effects of the communication device 2800 refer to the technical effects of the method in the above method embodiments, and the details will not be described again in this specification.

[0277] It should be understood that the processor in the embodiments of this application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc.

[0278] It should be further understood that the memory in the embodiments of this application may be volatile memory, non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) may be used, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM).

[0279] Optionally, the embodiments of this application further provide a computer program product carrying computer instructions, which, when executed on a computer, enable the computer to perform the methods described in the above embodiments.

[0280] Optionally, the embodiments of this application further provide a computer-readable storage medium, which stores computer instructions, which, when executed on a computer, enable the computer to perform the methods described in the above embodiments.

[0281] Optionally, an embodiment of the present application further provides a chip including a processing circuit and a transceiver circuit, the processing circuit and the transceiver circuit being configured to realize the methods described in the above embodiments, the processing circuit being configured to perform processing operations in the corresponding methods, and the transceiver circuit being configured to perform receiving / transmitting operations in the corresponding methods.

[0282] All or part of the above embodiments may be realized by using software, hardware (e.g., circuits), firmware, or any combination thereof. When software is used to realize the embodiments, the above embodiments may be fully or partially realized in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the procedures or functions according to the embodiments of this application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., infrared, radio, or microwave) method. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device integrating one or more available media, such as a server or data center. The usable media may be magnetic media (e.g., floppy disk, hard disk, or magnetic tape), optical media (e.g., DVD), or semiconductor media, which may be a solid-state drive.

[0283] It should be understood that the term "and / or" in this specification only describes an association relationship for describing related objects and represents 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, and A and B may be singular or plural. Furthermore, the character " / " in this specification usually indicates an "or" relationship between related objects, but may also indicate an "and / or" relationship. For more details, please refer to the context for understanding.

[0284] In this application, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions means any combination of these items, including a singular item or any combination of multiple items. For example, at least one of a, b, or c may refer to a, b, c, ab, ac, bc, or abc, where a, b, and c may be singular or plural.

[0285] It should be understood that the sequence numbers of the above processes do not mean the execution order in various embodiments of this application. The execution order of the processes should be determined based on the functions and internal logic of the processes, and should not be construed as any limitation on the implementation process of the embodiments of this application.

[0286] Those skilled in the art may recognize that, in combination with the examples described in the embodiments disclosed in this specification, the units and algorithm steps may be realized by electronic hardware or a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to realize the described functions for each specific application, but the implementation method should not be considered to go beyond the scope of this application.

[0287] For the purpose of convenient and concise description, those skilled in the art can clearly understand that the detailed operation processes of the above systems, devices and units may refer to the corresponding processes in the above method embodiments, and the details will not be described again in this specification.

[0288] In some embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be realized in other ways. For example, the above-described device embodiments are merely examples. For example, the division into units is merely a logical division of function, and other divisions may be used in actual implementations. For example, multiple units or components may be combined or integrated into other systems, or some features may be omitted or not implemented. Furthermore, the shown or discussed mutual couplings or direct couplings or communication connections may be realized through some interfaces. Indirect couplings or communication connections between devices or units may be realized in electronic, mechanical, or other forms.

[0289] The units described as separate parts may or may not be physically separate. The parts shown as units may or may not be physical units, and may be located in one place or distributed across multiple network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.

[0290] Furthermore, the functional units in the embodiments of this application may be integrated into one processing unit, each of the units may exist physically alone, or two or more units may be integrated into one unit.

[0291] When a function is realized in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application may essentially, or a portion of the technical solution or a portion of the technical solution may be realized in the form of a software product. A computer software product is stored in a storage medium and includes some instructions for instructing a computer device (which may be a personal computer, a server, or a communication device) to perform all or part of the steps of the method described in the embodiments of this application. The above storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0292] The above description is merely a specific implementation of this application and is not intended to limit the scope of protection of this application. Any variations or replacements that can be easily conceived by those skilled in the art within the technical scope disclosed in this application shall fall within the scope of protection of this application. Therefore, the scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. 1. A logical channel grouping method, comprising: determining, by the terminal device, that buffered data to be reported exists on a first logical channel (LCH); sending, by the terminal device, a buffer status report (BSR) to a network device based on the buffered data to be reported on the first LCH according to a preset configuration rule; Including, the BSR indicates a first amount of data and a first logical channel group (LCG), the first amount of data corresponds to the first LCG, the first amount of data includes a first amount of data, the buffered data includes the first data, and the first LCG is one of the LCGs configured for the first LCH; The remaining packet delay budget (PDB) of the first data is within a first remaining PDB range, and the configuration rule is configuration rule 1, i.e., includes L LCGs and L remaining PDB ranges, the L LCGs include the first LCG, the L remaining PDB ranges include the first remaining PDB range, and the first LCG is associated with the first remaining PDB range, and L is a positive integer greater than or equal to 2; or A method in which the priority level of the first data is within a first priority level range, the priority level of the first data is determined based on a remaining PDB of the first data and a data type of the first data, and the configuration rule is configuration rule 2, i.e., L LCGs and L priority level ranges, the L LCGs include the first LCG, the L priority level ranges include the first priority level range, the first LCG is associated with the first priority level range, and L is a positive integer greater than or equal to 2.

2. When the configuration rules include the configuration rule 1, the configuration rule 1 further indicates that a second LCG is associated with a second remaining PDB range; The method of claim 1 , wherein the L LCGs include the second LCG and the L remaining PDB ranges include the second remaining PDB range.

3. 3. The method of claim 2, wherein when the buffered data further includes second data and a remaining PDB of the second data is within the second remaining PDB range, the BSR further indicates a second amount of data and the second LCG, the second amount of data corresponds to the second LCG, and the second amount of data includes an amount of data of the second data.

4. When the remaining PDB of the first data is within the first remaining PDB range, the buffered data includes the first data, The method of claim 1 or 2, wherein the buffered data is the first data when there is one remaining PDB of the buffered data.

5. There are at least two remaining PDBs of the buffered data, and the remaining PDB of the first data is within the first remaining PDB range; When the smallest remaining PDB of the buffered data is used to determine a remaining PDB range corresponding to the buffered data, the smallest remaining PDB of the buffered data is within the first remaining PDB range; The method of claim 1 or 2, wherein the buffered data is the first data.

6. When the remaining PDB of the first data is within the first remaining PDB range, before determining by the terminal device that the buffered data to be reported is present on the first LCH, the method includes: The method according to claim 1 , further comprising the step of receiving, by the terminal device, first configuration information from the network device, the first configuration information indicating the configuration rule 1.

7. Before determining by the terminal device that buffered data to be reported exists on the first LCH, the method includes:

7. The method of claim 6, further comprising: receiving, by the terminal device, second configuration information from the network device, the second configuration information being used to configure an LCG range corresponding to the first LCH, the LCG range including all or part of the L LCGs.

8. 4. The method of claim 2 or 3, wherein the second remaining PDB range is [T, Pmax], where T represents a PDB threshold and Pmax represents a maximum transmission latency allowed for the buffered data.

9. 9. The method of claim 1, wherein the first remaining PDB range is [0, T), where T represents a PDB threshold.

10. 2. The method of claim 1, wherein when the configuration rules include the configuration rule 2, the configuration rule 2 further indicates that a second LCG is associated with a second priority level range, the L LCGs include the second LCG, and the L priority level ranges include the second priority level range.

11. When the first data is data of a first type, the first LCG is an LCG in a first set, the first set including at least one LCG, and each LCG in the first set is used to transmit data of the first type; or 11. The method of claim 10, wherein when the first data is data of a second type, the first LCG is an LCG in a second set, the second set including at least one LCG, each LCG in the second set is used to transmit the data of the second type, and each LCG in the first set is different from each LCG in the second set.

12. When the priority level of the first data is within the first priority level range, the buffered data includes the first data, The buffered data is the first data when the buffered data is of the same type and there is one remaining PDB of the buffered data; or When the buffered data is the same type of data, there are at least two remaining PDBs of the buffered data, and the smallest remaining PDB of the buffered data is used to determine the priority level of the buffered data, the buffered data is the first data. The method of claim 11 , comprising:

13. Before determining by the terminal device that buffered data to be reported exists on the first LCH, the method includes: The method of claim 10 , further comprising the step of receiving, by the terminal device, third configuration information from the network device, the third configuration information indicating the configuration rule 2.

14. Before determining by the terminal device that buffered data to be reported exists on the first LCH, the method includes:

14. The method of claim 13, further comprising: receiving, by the terminal device, fourth configuration information from the network device, the fourth configuration information being used to configure a priority level range corresponding to the first LCH, the priority level range configured by using the fourth configuration information including one or more priority levels within the L priority level ranges.

15. the first priority level range is [0, K] and the second priority level range is [K, Kmax]; 13. The method of any one of claims 10 to 12, wherein K represents a priority level threshold and Kmax represents the lowest priority level that can be present in the buffered data.

16. Before determining by the terminal device that buffered data to be reported exists on the first LCH, the method includes:

16. The method of claim 1, further comprising: receiving, by the terminal device, fifth configuration information from the network device, the fifth configuration information being used to configure the first Line Channel Group (LCG) for the first Layer 2 Channel (LCH).

17. 1. A logical channel grouping method, comprising: receiving, by a network device, a buffer status report (BSR) from a terminal device, where buffered data to be reported exists on a first logical channel (LCH) of the terminal device, the BSR indicating a first amount of data and a first logical channel group (LCG), where the first amount of data corresponds to the first LCG, the first amount of data includes a first amount of data, the buffered data includes the first data, and the first LCG is one of the LCGs configured for the first LCH; allocating, by the network device, uplink resources to the terminal device based on the first amount of data and the first LCG according to a preset configuration rule; Including, The remaining packet delay budget (PDB) of the first data is within a first remaining PDB range, and the configuration rule is configuration rule 1, i.e., includes L LCGs and L remaining PDB ranges, the L LCGs include the first LCG, the L remaining PDB ranges include the first remaining PDB range, and the first LCG is associated with the first remaining PDB range, and L is a positive integer greater than or equal to 2; or A method in which the priority level of the first data is within a first priority level range, the priority level of the first data is determined based on a remaining PDB of the first data and a data type of the first data, and the configuration rule is configuration rule 2, i.e., L LCGs and L priority level ranges, the L LCGs include the first LCG, the L priority level ranges include the first priority level range, the first LCG is associated with the first priority level range, and L is a positive integer greater than or equal to 2.

18. When the configuration rules include the configuration rule 1, the configuration rule 1 further indicates that a second LCG is associated with a second remaining PDB range; 18. The method of claim 17, wherein the L LCGs include the second LCG and the L remaining PDB ranges include the second remaining PDB range.

19. 20. The method of claim 18, wherein when the buffered data further includes second data and a remaining PDB of the second data is within the second remaining PDB range, the BSR further indicates a second amount of data and the second LCG, the second amount of data corresponds to the second LCG, and the second amount of data includes an amount of data of the second data.

20. When the remaining PDB of the first data is within the first remaining PDB range, the buffered data includes the first data, 19. The method of claim 17 or 18, wherein the buffered data is the first data when there is one remaining PDB of the buffered data.

21. There are at least two remaining PDBs of the buffered data, and the remaining PDB of the first data is within the first remaining PDB range; When the smallest remaining PDB of the buffered data is used to determine a remaining PDB range corresponding to the buffered data, the smallest remaining PDB of the buffered data is within the first remaining PDB range; 19. The method of claim 17 or 18, wherein the buffered data is the first data.

22. When the remaining PDB of the first data is within the first remaining PDB range, before receiving a BSR from a terminal device, by a network device, the method includes:

22. The method of claim 17, further comprising the step of: transmitting, by the network device, first configuration information to a terminal device, the first configuration information indicating the configuration rule 1.

23. Before receiving a BSR from the terminal device by the network device, the method includes:

23. The method of claim 22, further comprising: transmitting, by the network device, second configuration information to the terminal device, the second configuration information being used to configure an LCG range corresponding to the first LCH, the LCG range including all or part of the L LCGs.

24. 20. The method of claim 18 or 19, wherein the second remaining PDB range is [T, Pmax], where T represents a PDB threshold and Pmax represents a maximum transmission latency allowed for the buffered data.

25. 25. The method of any one of claims 17 to 21 or 24, wherein the first remaining PDB range is [0,T), where T represents a PDB threshold.

26. 18. The method of claim 17, wherein when the configuration rules include the configuration rule 2, the configuration rule 2 further indicates that a second LCG is associated with a second priority level range, the L LCGs include the second LCG, and the L priority level ranges include the second priority level range.

27. When the first data is data of a first type, the first LCG is an LCG in a first set, the first set including at least one LCG, and each LCG in the first set is used to transmit data of the first type; or 27. The method of claim 26, wherein when the first data is data of a second type, the first LCG is an LCG in a second set, the second set including at least one LCG, each LCG in the second set is used to transmit data of the second type, and each LCG in the first set is different from each LCG in the second set.

28. When the priority level of the first data is within the first priority level range, the buffered data includes the first data, The buffered data is the first data when the buffered data is of the same type and there is one remaining PDB of the buffered data; or When the buffered data is the same type of data, there are at least two remaining PDBs of the buffered data, and the smallest remaining PDB of the buffered data is used to determine the priority level of the buffered data, the buffered data is the first data.

28. The method of claim 27, comprising:

29. Before receiving a BSR from the terminal device by the network device, the method includes:

29. The method of claim 26, further comprising the step of transmitting, by the network device, third configuration information to the terminal device, the third configuration information indicating the configuration rule 2.

30. Before receiving a BSR from the terminal device by the network device, the method includes:

30. The method of claim 29, further comprising: transmitting, by the network device, fourth configuration information to the terminal device, the fourth configuration information being used to configure a priority level range corresponding to the first LCH, the priority level range configured by using the fourth configuration information including one or more priority levels within the L priority level ranges.

31. 29. The method of claim 26, wherein the first priority level range is [0, K] and the second priority level range is [K, Kmax], where K represents a priority level threshold and Kmax represents the lowest priority level that may be present in the buffered data.

32. Before receiving a BSR from the terminal device by the network device, the method includes:

32. The method of claim 17, further comprising the step of: transmitting, by the network device, fifth configuration information to the terminal device, the fifth configuration information being used to configure the first Line Channel Group (LCG) for the first Layer Channel Handover (LCH).

33. A terminal device including a processor and a memory, 17. A terminal device, wherein the processor is coupled to the memory, the memory storing program instructions, and wherein the program instructions stored in the memory, when executed by the processor, implement the method of any one of claims 1 to 16.

34. A network device including a processor and a memory, 33. A network device, wherein the processor is coupled to the memory, the memory storing program instructions, the program instructions stored in the memory, when executed by the processor, implementing the method of any one of claims 17 to 32.

35. A chip including a processor and an input / output interface, A chip, wherein the input / output interface is configured to receive signals from a device other than the chip and to send the signals to the processor, or to send signals from the processor to a device other than the chip, and wherein the processor is configured to implement the method of any one of claims 1 to 32 through logic circuits or by executing code instructions.

36. 1. A computer-readable storage medium, comprising:

33. A computer-readable storage medium storing a computer program or instructions, the computer program or instructions being executed to implement the method of any one of claims 1 to 32.

37. A communication system including a terminal device and a network device, The terminal device is configured to perform the method according to any one of claims 1 to 16, A communication system, wherein the network devices are configured to perform the method of any one of claims 17 to 32.

Images