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, titled "LOGICAL CHANNEL GROUPING METHOD, TERMINAL DEVICE, NETWORK DEVICE, AND APPARATUS", filed with the China National Intellectual Property Administration on October 19, 2022, and Chinese Patent Application No. 202211372394.4, titled "LOGICAL CHANNEL GROUPING METHOD AND COMMUNICATION APPARATUS", filed with the China National Intellectual Property Administration on November 3, 2022, and the entire contents of both are incorporated herein by reference.

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

Background Art

[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 the network device. The BSR indicates the amount of buffered data to be transmitted by the terminal device, and the network device allocates an amount of uplink resources corresponding to the terminal device based on the amount of buffered data indicated by the BSR. In the BSR reporting mechanism, the reporting is performed at the granularity of a logical channel group (LCG).

[0004] However, in extended reality (XR) services, different packets within a single data burst correspond to the same packet delay budget (PDB), while packets within different data bursts correspond to different PDBs. Buffered data in an LCG may include packets from different data bursts, and network devices may allocate uplink resources beyond the PDBs of packets (or some packets). As a result, packet scheduling can fail, uplink scheduling efficiency is reduced, and uplink capacity is lowered. [Overview of the Initiative]

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

[0006] According to a first embodiment, a method for logical channel grouping is provided. This method may be performed by a terminal device or by a chip used in the terminal device. For illustrative purposes, an example in which the method is performed by a terminal device is used below. The method includes the following: The terminal device determines that the buffered data to be reported is located on a first logical channel LCH. The terminal device then 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 pre-configured configuration rule. The BSR indicates a first data amount and a first logical channel group LCG, where the first data amount corresponds to the first LCG, the first data amount includes the 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] Where possible, the remaining packet delay budget PDB of the first data is within the range of the first remaining PDB. The configuration rule is configuration rule 1, i.e., it includes L LCGs and L remaining PDB ranges, where L LCGs include the first LCG, L remaining PDB ranges include the first remaining PDB range, the first LCG is associated with the first remaining PDB range, and L is a positive integer greater than or equal to 2.

[0008] Otherwise possible, 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 PDBs of the first data and the data type of the first data. The configuration rule is configuration rule 2, namely, including L LCGs and L priority level ranges, where L LCGs include the first LCG, 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.

[0009] In other words, when the BSR indicates a first data volume and a first LCG, and the first LCG is associated with a first remaining PDB range according to a pre-configured configuration rule 1, the network device allocates uplink resources to terminal devices based on the first remaining PDB range and the first data volume. For example, when the remaining PDBs corresponding to the first remaining PDB range are small, the network device may preferentially allocate uplink resources to the data corresponding to the first data volume, or when the remaining PDBs corresponding to the first remaining PDB range are large and transmission resources are insufficient, the network device may allocate uplink resources later to the data corresponding to the first data volume 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 a pre-configured configuration rule 2, the network device allocates uplink resources to terminal devices based on the first priority level range and the first data volume. 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 volume, 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 volume and preferentially allocate uplink resources to other terminal devices. This improves uplink scheduling efficiency and uplink capacity.

[0010] In a possible design, when the configuration rule includes configuration rule 1, configuration rule 1 further indicates that the second LCG is associated with the second remaining PDB range. L LCGs include the second LCG, and L remaining PDB ranges include the second remaining PDB range. For example, the second LCG may be any LCG other than the first LCG among the L LCGs. In other words, configuration rule 1 has a one-to-one correspondence between L LCGs and L remaining PDB ranges.

[0011] In a possible design, when the buffered data further includes the second data, and the remaining PDB of the second data is within the range of the second remaining PDB, the BSR further indicates the second data amount and the 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 from different remaining PDBs, the terminal device determines the different LCGs and data amounts indicated by the BSR based on the remaining PDBs. Thus, after receiving the BSR, the network device may, in accordance with configuration rule 1, know the remaining PDB ranges corresponding to the different data amounts based on the LCGs indicated by the BSR, and allocate uplink resources more appropriately to improve uplink scheduling efficiency.

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

[0014] In other words, when buffered data on the first LCH has the same remaining PDB and the remaining PDB is within the range of the first remaining PDB, the terminal device reports the amount of buffered data via one LCG (i.e., the first LCG). Thus, after receiving the BSR, the network device may know the amount of data and the remaining PDB range according to configuration rule 1 and allocate uplink resources, resulting in the terminal device uploading 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 for the buffered data. The fact that the remaining PDB of the first data lies within the range of the first remaining PDB 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 lies within the range of the first remaining PDB, and the buffered data is the first data.

[0016] In other words, even if the buffered data on the first LCH includes data from 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. Thus, after receiving the BSR, the network device may know the amount of data and the remaining PDB range according to configuration rule 1 and allocate uplink resources appropriately. For example, when the remaining PDBs indicated by the remaining PDB range are small, the network device can improve uplink scheduling efficiency by preferentially allocating uplink resources based on the amount of data corresponding to the remaining PDB range.

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

[0018] In other words, the network device configures configuration rule 1 for the terminal device, and as a result, the network device properly manages BSR reporting.

[0019] In a possible design, before the terminal device determines that the buffered data to be reported resides 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 includes all or part of L LCGs, and as a result 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 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 to 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 greater than or equal to the PDB threshold, the remaining PDB corresponding to the buffered data is the second remaining PDB range. This simplifies the processing process for the terminal device.

[0021] In a possible design, the first remaining PDB range is [0, T), where T represents the 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 to 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 rule includes configuration rule 2, configuration rule 2 further indicates that the second LCG is associated with the second priority level range, L LCGs include the second LCG, and L priority level ranges include the second priority level range. For example, the second LCG may be any LCG other than the first LCG among the L LCGs. In other words, configuration rule 2 has a one-to-one correspondence between L LCGs and L priority level ranges.

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

[0024] In other words, terminal devices report the amount of data for different types of data via different LCGs.

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

[0026] In other words, when the buffered data has the same data type and the remaining PDBs of the buffered data are 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 the first priority level range, the buffered data including the first data includes the following. The buffered data is of the same type of data, there are at least two remaining PDBs of the buffered data, and when the minimum remaining PDB of the buffered data is used to determine the priority level of the buffered data, the buffered data is the first 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 minimum remaining PDB of the buffered data. Thus, all of the buffered data corresponds to the same priority level and is within the same priority level range.

[0029] 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 following. The terminal device receives third configuration information from the network device, and 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 resides on the first LCH, the method further includes: the terminal device receives fourth configuration information from the network device, which is used to configure a priority level range corresponding to the first LCH, and the priority level range configured using the fourth configuration information includes one or more priority levels within L priority level ranges, so that the first LCH is dynamically adjusted within the priority level range configured for the first LCH. Thus, even if the buffered data on the first LCH has different priority levels at different times, the terminal device may report the amount of data of the 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 possible priority level that may exist 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 buffered data's priority level 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 buffered data's priority level 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 the buffered data to be reported resides 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 data of the first data on the first LCH via the first LCG.

[0035] According to a second embodiment, a logical channel grouping method is provided. This method may be performed by a network device or by a chip used in the network device. For illustrative purposes, an example in which the method is performed by a network device is used below. The method includes: The network device receives a buffer state report BSR from a terminal device, the buffered data to be reported resides on a first logical channel LCH of the terminal device, the BSR indicates a first data volume and a first logical channel group LCG, the first data volume corresponds to the first LCG, the first data volume includes the data volume of the first 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 data volume and the first LCG according to a pre-configured configuration rule. The remaining packet delay budget PDB for the first data is within the range of the first remaining PDB. The configuration rule is configuration rule 1, i.e., it includes L LCGs and L remaining PDB ranges, where L LCGs include a first LCG, L remaining PDB ranges include a first remaining PDB range, the first LCG is associated with a 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 the first priority level range, and the priority level of the first data is determined based on the remaining PDBs of the first data and the data type of the first data. The configuration rule is configuration rule 2, i.e., it includes L LCGs and L priority level ranges, where L LCGs include a first LCG, L priority level ranges include a first priority level range, the first LCG is associated with a first priority level range, and L is a positive integer greater than or equal to 2.

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

[0037] In a possible design, when the buffered data further includes the second data, and the remaining PDB of the second data is within the range of the second remaining PDB, the BSR further indicates the second data amount and the 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 PDBs of the first data are within the range of the first remaining PDBs, the buffered data containing the first data includes the following: When there is one remaining PDB of buffered data, the buffered data is the first data.

[0039] In a possible design, there are at least two remaining PDBs for the buffered data. The fact that the remaining PDB of the first data lies within the range of the first remaining PDB 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 lies within the range of the first remaining PDB, and the buffered data is the first data.

[0040] In a possible design, when the remaining PDBs of the first data are within the range of the first remaining PDBs, before the network device receives the BSR from the terminal device, the method further includes: The network device sends first configuration information to the terminal device, which 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 transmits second configuration information to the terminal device, which is used to configure an LCG range corresponding to a first LCH, the LCG range including all or some of 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 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 rule includes configuration rule 2, configuration rule 2 further indicates that the second LCG is associated with the second priority level range, L LCGs include the second LCG, and L priority level ranges include the second priority level range.

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

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

[0047] In a possible design, buffered data containing first data includes the following when the priority level of first data is within the first priority level range: buffered data is first data when buffered data is of the same type, there are at least two remaining PDBs of buffered data, and the smallest remaining PDB of buffered data is used to determine the priority level of 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, which 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 transmits a fourth configuration information to the terminal device, which is used to configure a priority level range corresponding to the first LCH, and the priority level range configured using the fourth configuration information includes one or more priority levels within 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 possible priority level that may exist 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 transmits a fifth configuration to the terminal device, which is used to configure a first LCG for a first LCH.

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

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

[0054] According to a fifth aspect, a communication device is provided. The communication device includes a processor. The processor is coupled to memory and configured to read and execute instructions in memory, so that the communication device performs a method performed by a network device in any one of the above aspects or in any possible design of any one of the above aspects. The communication device may also be a network device in any one of the second aspect or a possible design of the second aspect, or a chip that implements the functions of a network device.

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

[0056] According to the seventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions. When the instructions are executed on a computer, the computer becomes capable of performing the method in any one of the above aspects.

[0057] According to the eighth aspect, a computer program product including instructions is provided. When the computer program product is executed on a computer, the computer becomes capable of performing the method in any one of the above aspects.

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

[0059] According to a tenth aspect, a communication system is provided which includes a terminal device and a network device. The terminal device is configured to perform a method in any one of the first aspect and a possible design of the first aspect, and the network device is configured to perform a method in any one of the second aspect and a possible design of the second aspect.

[0060] For the technical effects resulting from any of the designs in the second to tenth aspects, refer to the beneficial effects of the corresponding methods provided above. Further details are not described herein. [Brief explanation of the drawing]

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

[0062] The technical solution of this application will be described below with reference to the attached drawings.

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

[0064] Network devices may include base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5th generation (5G) mobile communication systems, next-generation base stations in 6th generation (6G) mobile communication systems, base stations in future mobile communication systems, access nodes in wireless fidelity (Wi-Fi) systems, etc., or they may be modules or units that complete some of the functions of a base station. For example, a network device may be a central unit (CU) or a distributed unit (DU). The CU in this specification completes the functions of the base station's radio resource control (RRC) protocol and packet data convergence protocol (PDCP), and may further complete the functions of the service data adaptation protocol (SDAP). The DU may complete the functions of the base station's radio link control (RLC) and medium access control (MAC) layers, and may further complete some or all of the functions of the physical (PHY) layer. For a specific description of the protocol layers described above, 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 Figure 1), or a micro base station or indoor base station (e.g., 110b in Figure 1), or a relay node, donor node, etc. Specific technologies and device forms used by the network device are not limited to the embodiments of this application.To simplify the explanation, we will use network devices as examples below.

[0065] Terminal devices may also be called terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminal devices may be broadly 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 grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminal devices may also be mobile phones, tablet computers, computers with wireless receiver functionality, wearable devices, vehicles, unmanned aerial vehicles, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. Specific technologies and specific device forms used by terminal devices are not limited to the embodiments of this application.

[0066] Network devices and terminal devices may be in a fixed location or they may be mobile. Network devices and terminal devices may be located on land, on water, or in the air, including indoor or outdoor devices, handheld devices, or vehicle-mounted devices. Application scenarios for network devices and terminal devices are not limited to the embodiments of this application.

[0067] The roles of network devices and terminal devices may be relative. For example, the helicopter or unmanned aerial vehicle 120i in Figure 1 may be configured as a mobile base station. For terminal device 120j that accesses the radio 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 the radio air interface protocol. Obviously, 110a and 120i may also communicate with each other by using the 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 Figure 1 may be called communication devices with network device functionality, and 120a to 120j in Figure 1 may be called communication devices with terminal device functionality.

[0068] Communication between network devices and terminal devices, communication between network devices, and communication between terminal devices may be performed over a licensed spectrum, over an unlicensed spectrum, or over both a licensed and unlicensed spectrum. Communication may be performed over a spectrum below 6 gigahertz (GHz), over a spectrum above 6 GHz, or over both a spectrum below 6 GHz and a spectrum above 6 GHz. The spectral resources used for wireless communication are not limited to the embodiments of this application.

[0069] In 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 by a control subsystem that includes the functions of the network device. The control subsystem that includes the functions of the network device as described herein may also be a control center in the above application scenarios such as smart grids, industrial control, smart transportation, and smart cities. The functions of the terminal device may, alternatively, be performed by a module (e.g., a chip or modem) within the terminal device, or by a device that includes the functions of the terminal device.

[0070] In this application, a network device transmits downlink signals or downlink information to a terminal device, with the downlink information carried over the downlink channel. The terminal device transmits uplink signals or uplink information to a network device, with the uplink information carried over the 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 to which the terminal device has a wireless connection is called the terminal device's serving cell. When communicating with the serving cell, the terminal device is further subjected to interference from signals from neighboring cells.

[0071] To facilitate understanding of the embodiments of this application, a brief explanation of the terminology used in these embodiments is provided below. It should be understood that these explanations are solely for the purpose of facilitating understanding of the embodiments of this application and do not constitute any limitation to this application.

[0072] 1. Cross-reality (extended reality, XR) XR refers to a human-machine interaction environment that combines reality and virtuality, generated by 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° imaging to achieve interactive, immersive experience effects. XR services have the following characteristics: large service volume, high transmission latency requirements (i.e., transmission latency must be reduced as much as possible), short data frame arrival intervals, and a clear service cycle.

[0073] In a scenario where a network device transmits data frames of XR or an XR-like service to a terminal device, when the data frame rate is 60 frames per second (fps), the average arrival time interval between service data corresponding to two adjacent data frames is 16.6666...ms (approximately equal to 16.67ms). It should be understood that a data frame is defined from the perspective of the application layer, and one data frame may be replaced by 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 by one PDU set.

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

[0075] For example, video frames are 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 contain the same number of video frames. In each GOP, a terminal device may perform intra-frame coding or inter-frame coding for each frame of the image. As shown in Figure 3, the first frame of the image in each GOP may be called an intra-frame coding frame. An intra-frame coding frame is abbreviated as an I-frame and may be coded and decoded independently. Subsequent frames of the image may be called inter-frame coding frames, including predictive frames (abbreviated as P-frames) and bidirectional predictive frames (abbreviated as B-frames). Inter-frame 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) PDB is the latency limit for transmitting packets between a terminal device and a user plane network element, representing the maximum transmission latency allowed for a packet. The user plane network element may also be a user plane function (UPF) network element terminating the N6 interface in a 5G system.

[0077] The PDB may be divided into two parts: the access network (AN) PDB (referred to as AN PDB) and the core network (CN) PDB (referred to as CN PDB). The AN PDB is the latency limit for transmitting packets between terminal devices and access network devices. The CN PDB is the latency limit 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 between the time a packet arrives at a terminal device and the time the packet is successfully transmitted to a network device. Packets that are not successfully transmitted to a network device beyond the PDB may be considered unwanted packets.

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

[0080] In embodiments of this application, it can be readily understood that the unit of PDB may be milliseconds, for example, tens of milliseconds or tens of milliseconds. Obviously, PDB may have other units of time as an alternative. This is not limited to embodiments of this application. Furthermore, in embodiments of this application, delay and latency are equivalent and may be interchangeable. For example, latency limit may also be described as delay limit.

[0081] 3. Protocol stack on the wireless access network side The protocol stack on the wireless 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 the SDAP layer, PDCP layer, RLC layer, MAC layer, PHY layer, etc. The PHY layer belongs to the first layer (also called layer 1 (L1)), and the MAC layer, RLC layer, PDCP layer, and SDAP layer belong to the second layer (also called layer 2 (L2)). Furthermore, the RRC layer and NAS layer of the control plane belong to the third layer (also called layer 3 (L3)).

[0082] As shown in Figure 4, in the user-plane protocol stack, the SDAP layer is located above the PDCP layer, the PDCP layer above the RLC layer, the RLC layer above the MAC layer, and the MAC layer above the PHY layer. For XR services, after service data arrives at the terminal device, the terminal device sequentially processes the packets in the protocol layers in the order shown from top to bottom in Figure 4, and finally transmits the processed packets to the network device via the air interface. After receiving the packets via the air interface, the network device sequentially performs the corresponding processing on the packets in the reverse order of the terminal device. Packet processing at each protocol layer is implemented by the multifunction entity corresponding to the protocol layer. For details, refer to the relevant 3GPP technical specifications. Details are not described again herein. It can be easily understood that the user-plane protocol stack shown in Figure 4 does not constitute any limitation to the solution of this application. In practical applications, the user-plane protocol stack may include more or fewer protocol layers than those shown in the drawings.

[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 being carried. Network devices configure a transmission parameter set for the LCH for terminal devices. This transmission parameter set may include parameters that can be transmitted or mapped by the LCH, such as subcarrier spacing, cyclic prefix length, and serving cells of terminal devices corresponding to uplink resources.

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

[0086] Uplink resources are used to transmit uplink data from terminal devices and are, for example, resources for a physical uplink shared channel (PUSCH).

[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 sends 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 reported by the terminal device. Based on the amount of buffered data indicated by the BSR, the network device allocates a corresponding number of uplink resources to the terminal device.

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

[0089] The trigger for a regular BSR is described as follows: The trigger for a regular BSR satisfies the following conditions: When one of the following conditions is met, the uplink data must be transmitted over a logical channel (LCH) belonging to the 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 shown as LCH5 to LCH8, respectively. The 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 the 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 shown 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 will trigger a regular BSR.

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

[0093] As shown in Figure 5, the length of the short BSR format is fixed at 1 octet (also called a byte). In the short BSR format, 3 bits are used to indicate the logical channel group identity, i.e., the LCG ID, and 5 bits are used to indicate the interval in which the buffered data amount (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 Figure 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 or not to report the buffer size of the LCG corresponding to the bit. The second byte, or the byte following the second byte, is used to indicate the interval in which the amount of buffered data is located. For example, if the value of LCG_i is set to 1, this indicates that there is uplink data to be reported in LCG_i, or if 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 in which data needs to be reported is indicated by using one byte.

[0095] In other words, in the BSR reporting mechanism, reporting is performed at the LCG granularity. 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 contain packets from one data burst or packets from multiple data bursts. Therefore, at some point, different data bursts may correspond to different remaining PDBs. In this case, problems of low uplink scheduling efficiency and reduced uplink capacity may occur. For details, see the following explanations for Case A and Case B.

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

[0098] For example, as shown in Figure 7, on the terminal device 1 side, terminal device 1 acquires packets in data burst 1 at 0 ms and packets in data burst 2 at 16.67 ms. In this case, the uplink data in the buffer corresponding to LCG1 includes packets in data burst 1 and packets in data burst 2. K1 represents the amount of data in data burst 1 in the buffer corresponding to LCG1, and K2 represents the amount of data in 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 32ms. Furthermore, the uplink resources allocated to terminal device 1 by the network device at 32ms are the uplink resources determined based on the amount of data K indicated by the BSR. At 32ms, the network device allocates uplink resources beyond the PDB range corresponding to packets in data burst 1. In this case, packets (some packets) are considered invalid packets. As a result, the uplink capacity is low. Moreover, the network device still allocates uplink resources to packets in data burst 1, affecting uplink scheduling efficiency.

[0100] Scenario B: If uplink resources are insufficient after a network device has received BSRs from at least two terminal devices, the network device may allocate excessive uplink resources to one terminal device and insufficient uplink resources to another terminal device. This results in problems of low uplink scheduling efficiency and low uplink capacity.

[0101] For example, as shown in Figure 7, on the terminal device 1 side, refer to the explanation in Case A for terminal device 1. Details will not be explained again in this specification. The BSR transmitted by terminal device 1 is shown as BSR1, and the amount of data shown by BSR1 is shown as K.

[0102] On terminal device 2, packets within data burst 3 are captured in 1 ms. In this case, the uplink data in the buffer corresponding to terminal device 2's LCG1 includes packets within data burst 3. K3 represents the amount of data in data burst 3 in the buffer corresponding to terminal device 2's LCG1. Correspondingly, the BSR transmitted by terminal device 2 is shown as BSR2, and the amount of data shown by BSR2 is shown as K3.

[0103] On the network device side, after receiving BSR1 and BSR2, the network device allocates uplink resources to terminal devices 1 and 2 only at 12ms. Furthermore, at 28ms, 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 data amount 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 28ms, the remaining PDB for packets in data burst 1 is 2ms, the remaining PDB for packets in data burst 2 is approximately 18.67ms (i.e., 30-(28-16-0.67)), and the remaining PDB for packets in data burst 3 is 3ms. Thus, uplink resources are not allocated in a timely manner to packets in data burst 3 of terminal device 2, and uplink resources are easily allocated beyond the PDB range corresponding to packets. As a result, uplink capacity is low and uplink scheduling efficiency is reduced.

[0105] In conclusion, while the BSR can indicate the intervals in which the reported uplink data volume is located, it cannot indicate the remaining PDBs. Therefore, when network devices allocate uplink resources based on the intervals in which the data volume is located as indicated by the BSR, problems of low uplink scheduling efficiency and low uplink capacity may occur.

[0106] With this in mind, embodiments of this application provide a logical channel grouping method, which may be applied to the communication system shown in Figure 1. In the logical channel grouping method provided in this embodiment of this application, a terminal device determines that buffered data to be reported resides on a first logical channel LCH. The terminal device then transmits a buffer status report BSR to a network device based on the buffered data to be reported on the first LCH, according to a pre-configured configuration rule. The BSR indicates a first data amount and a first logical channel group LCG, where the first data amount corresponds to the first LCG, the first data amount includes the data amount of the first 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] Where possible, the remaining packet delay budget PDB for the first data is within the range of the first remaining PDB. The configuration rule is configuration rule 1, i.e., It includes L LCGs and L remaining PDB ranges, where L LCGs include the first LCG, L remaining PDB ranges include the first remaining PDB range, 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, where otherwise possible, 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 PDBs of the first data and the data type of the first data. The configuration rule is configuration rule 2, i.e., It includes L LCGs and L priority level ranges, where L LCGs include a first LCG, L priority level ranges include a first priority level range, the first LCG is associated with a 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 data volume and a first LCG, and the first LCG is associated with a first remaining PDB range according to a pre-configured configuration rule 1, the network device allocates uplink resources to terminal devices based on the first remaining PDB range and the first data volume. For example, when the remaining PDBs corresponding to the first remaining PDB range are small, the network device may preferentially allocate uplink resources to the data corresponding to the first data volume, or when the remaining PDBs corresponding to the first remaining PDB range are large, the network device may allocate uplink resources later to the data corresponding to the first data volume 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 a pre-configured configuration rule 2, the network device allocates uplink resources to terminal devices based on the first priority level range and the first data volume. 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 volume, 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 volume and preferentially allocate uplink resources to other terminal devices. This improves uplink scheduling efficiency and uplink capacity.

[0110] The names of messages between devices, the names of parameters within messages, etc., in the following embodiments of this application are merely examples, and it should be understood that other names may be used in a particular implementation. This is not particularly limited to the embodiments of this application.

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

[0112] S801: The terminal device determines that the buffered data to be reported resides on the first LCH.

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

[0114] For example, with respect to data types, the buffered data on the first LCH may include I-frame data in the XR service, or the buffered data on the first LCH may include P-frame data in the XR service.

[0115] In another example, with respect to a data burst, the buffered data on the first LCH contains 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 contains 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 the buffered data to be reported on the first LCH, according to pre-configured configuration rules. The network device receives the BSR from the terminal device.

[0117] The pre-configured 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 represents L LCGs and L remaining PDB ranges, where L LCGs include the first LCG, L remaining PDB ranges include the first remaining PDB range, 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 L LCGs and 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, construction rule 1 further shows that the 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 is easily understood that the second LCG can be any LCG among the L LCGs other than the first LCG.

[0120] Table 1 is used as an example. Table 1 shows the correspondence between the LCG and the remaining PDB range. [Table 1]

[0121] As shown in Table 1, when LCG ID=0, the remaining PDB range corresponding to LCG0 is 0ms to 2ms. When LCG ID=1, the remaining PDB range corresponding to LCG1 is 2ms to 4ms. The same rule may be followed when LCG ID is a different value. Further details will not be explained again. It should be understood that in Table 1, the correspondence between LCG and the remaining PDB range is described by using the example where the LCG ID value is in the range of 0 to 7, i.e., L=8. Obviously, L may have other values ​​as an alternative, for example, L=4. This is not limited to 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 LCG 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 terminal devices, 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 is easy to understand 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 configuration rule 1 may be pre-configured information or may be configured by a network device for a terminal device. Specifically, as shown in Figure 25, the logical channel grouping method in this embodiment of the application further includes S803.

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

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

[0130] For example, if 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 L LCGs and L remaining PDB ranges.

[0131] In other examples, 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 construct the first LCG.

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

[0133] Configuration rule 2 indicates L LCGs and L priority level ranges, where L LCGs include a first LCG, L priority level ranges include a first priority level range, the first LCG is associated with a 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 L LCGs and 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 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 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. In this embodiment of the 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 among the L LCGs other than the first LCG.

[0135] Table 4 is used as an example. Table 4 shows the correspondence between LCG 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-2. When LCG ID=1, the priority level range corresponding to LCG1 is 3-4. The same rules may apply when LCG ID is a different value. Further details will not be provided. It should be understood that in Table 4, the correspondence between LCG and priority level range is described by using the example where the LCG ID value is in the range of 0 to 7, i.e., L=8. Obviously, L may have other values ​​as an alternative, for example, L=4. This is not limited to 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 LCG 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 from 1 to 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 terminal devices, 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 is easy to understand 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 configuration rule 2 may be pre-configured information or may be configured by a network device for a terminal device. Specifically, as shown in Figure 25, the logical channel grouping method in this embodiment of the application further includes S804.

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

[0144] The third configuration information refers to configuration rule 2. For example, the third configuration information may be information within LogicalChannelConfig.

[0145] For example, if 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 L LCGs and L priority level ranges.

[0146] In other examples, when configuration rule 2 is as shown in Table 5 (or Table 6), it may be understood that the third configuration information is used to constitute 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, L LCGs in configuration rule 2 include the first LCG in S802, and 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 the first data amount and the 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 data amount. 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 through m+1 indicates the first data amount.

[0150] The first data amount indicated by the BSR corresponds to the first LCG. For example, the first data amount is the data amount of the 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 can 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 not 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 other LCHs. Correspondingly, the first data amount is greater 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 are not described herein.

[0152] The first LCG is one of at least one LCG configured for the first LCH. For example, an 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. A first LCH is used as an example. As shown in Figure 26, the logical channel grouping method in this embodiment of the 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 the LCG range corresponding to the first LCH. For example, the LCG range configured using the second configuration information includes all or some 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. Further details are not described herein.

[0156] For example, the second configuration information could be information within 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 using the second configuration information is shown as (0,7). In other words, the first LCH may be dynamically adjusted between eight LCGs (i.e., LCG0 to LCG7).

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

[0159] It can be easily understood that S805 is executed before S801, and that 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 may execute S803 (or S804) first, and then S805. This is not limited to the embodiments of this application. In S805, the first LCH is used as an example for illustrative purposes. When the terminal device has another LCH, for example, a second LCH which is also used to transmit XR service data, the network device also constitutes an LCG range for the second LCH.

[0160] Configuration Case 2: In addition to configuring a normal LCG, the network device further configures additional LCGs for each LCH of the terminal device. In Configuration Case 2, the additional LCG configured for each LCH is shown as the first LCG, and the LCG configured normally for each LCH is shown 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 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 the first LCG for the first LCH. For example, Table 2 (or Table 3) is used as an example. The first LCG configured using the fifth configuration information is LCG0, and as a result, the terminal device reports via LCG0 the amount of data in the buffered data (on the first LCH) where the remaining PDB is below the PDB threshold. In another example, Table 5 (or Table 6) is used as an example. The first LCG configured using the fifth configuration information is LCG0, and as a result, the terminal device reports via LCG0 the amount of data in the buffered data (on the first LCH) where the priority level is below the priority level threshold.

[0163] For example, the fifth configuration information could be information within 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 using the fifth configuration information is shown as LCG0.

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

[0166] It can be easily understood that S806 is executed before S801, and that 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 may execute S803 (or S804) first, and then S806. This is not limited to the embodiments of this application. In S806, the first LCH is used as an example for illustrative purposes. When the terminal device has another LCH, for example, a second LCH which is also used to transmit XR service data, the network device also further 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 two configuration rules mentioned above (for example, Configuration Rule 1 and Configuration Rule 2).

[0169] In the first possible implementation, the configuration rule in S802 includes configuration rule 1. In this case, the remaining PDBs of the first data are within the range of the first remaining PDBs. See the explanations in Examples 1 and 2 for details.

[0170] Example 1 In Example 1, the configuration case for the first LCH is Configuration Case 1. Correspondingly, the configuration rule used is shown in Table 1 for Configuration Rule 1. The following explanation is provided using three implementation methods (i.e., Implementation Methods 1 to 3 below).

[0171] In implementation method 1 of 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 the first LCG is associated with the first remaining PDB range, and the buffered data on the first LCH further includes the second data, the BSR indicates not only the first data amount and the first LCG, but also the second data amount and the second LCG. The first data amount corresponds to the first LCG, the first data amount includes the data amount of the first data, and the remaining PDB of the first data is within the range of the first remaining PDB. The second data amount corresponds to the second LCG, the second data amount includes the data amount of the second data, and the remaining PDB of the second data is within the range of the second remaining PDB.

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

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

[0175] For example, referring to Figure 11, still based on the example where the first LCH is LCH1, in the buffered data on LCH1, the remaining PDB for 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 for 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 for yet another portion of the data (e.g., shown as data n) is 2n-1 milliseconds, and the remaining PDB range of the remaining PDB is shown as remaining PDB range n, e.g., 2(n-1) milliseconds to 2n milliseconds. In this case, the BSR represents the following 2n items, namely LCG1 and data quantity 1, LCG2 and data quantity 2, ..., and LCGn and data quantity n. In other words, the data volume of data 1 on LCH1 is reported via LCG1, for example, data volume 1 corresponding to LCG1 includes the data volume of data 1; the data volume of data 2 on LCH1 is reported via LCG2, for example, data volume 2 corresponding to LCG2 includes the data volume of data 2; ..., the data volume of data n on LCH1 is reported via LCGn, for example, data volume n corresponding to LCGn includes the data volume of data n.

[0176] Remaining PDB range 1 may be considered a first remaining PDB range, and each of remaining PDB ranges 2 to n can be considered a second remaining PDB range. For the indication state of the BSR, refer to the description of the first data amount, first LCG, second data amount, and second LCG in implementation method 1. Further details are not described herein.

[0177] It is readily apparent that, based on the remaining PDBs, the buffered data on the first LCH may be allocated to a smaller remaining PDB range. 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 considered 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. Further details are not described herein.

[0178] In other words, even if the buffered data on the first LCH contains data from different remaining PDBs, the terminal device determines at least one LCG indicated by the BSR based on the remaining PDBs. Thus, after receiving the BSR, the network device may know at least one data volume, at least one remaining PDB range, and the correspondence between the data volume and the remaining PDB range, and allocate uplink resources appropriately. 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 volume 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 volume corresponding to the remaining PDB range, or it may improve uplink scheduling efficiency by preferentially allocating uplink resources to the data volume corresponding to the smaller remaining PDB.

[0179] In implementation method 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 the first LCG is associated with the first remaining PDB range, and the buffered data on the first LCH includes packets in a data burst, there exists at some point one remaining PDB of the buffered data on the first LCH. When the remaining PDB of the buffered data on the first LCH is within the range of the first remaining PDB, 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. It can be understood that the first data is all of the buffered data on the first LCH. Correspondingly, the BSR indicates the first data amount and the first LCG, the first data amount corresponds to the first LCG, the first data amount includes the data amount of the first data, and the remaining PDB of the first data is within the range of the first remaining PDB.

[0181] For example, referring to Figure 12, still based on the example where the first LCH is LCH1, at time 1, the remaining PDB for all buffered data on LCH1 (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. In this case, the BSR shows the following two items, namely LCG1 and Data Quantity 1. In other words, the data quantity of buffered data on LCH1 (i.e., Data 1) is reported via LCG1, and for example, Data Quantity 1 corresponding to LCG1 includes the total data quantity of buffered data on LCH1. At time 2, the remaining PDB for all buffered data on LCH1 (e.g., shown as Data 1) 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 Figure 12. In this case, the BSR shows the following two items, namely LCG2 and Data Quantity 2. In other words, the amount of buffered data on LCH1 (i.e., data 1) is reported via LCG2, and for example, data amount 2 corresponding to LCG2 includes the total amount of buffered data on LCH1.

[0182] In other words, when buffered data on the first LCH has the same remaining PDBs, the terminal device reports the amount of data buffered via one LCG (i.e., the first LCG). Thus, after receiving the BSR, the network device knows the amount of data and the remaining PDB range and may allocate uplink resources, resulting in the terminal device uploading the buffered data on the first LCH in a timely manner. This improves uplink scheduling efficiency.

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

[0184] Specifically, when a first LCG is associated with a first remaining PDB range, and the buffered data on a first LCH contains packets in different data bursts, there are at least two remaining PDBs for the buffered data on the first LCH at some point in 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 fact that the remaining PDBs for the first data are 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 the first data amount and the first LCG, where the first data amount corresponds to the first LCG, the first data amount includes the data amount of the first data, and the remaining PDBs for the first data are within the first remaining PDB range.

[0185] For example, referring to Table 1, still based on the example where the first LCH is LCH1, in the buffered data on LCH1, the remaining PDB for a portion of the data (e.g., shown as data 0) is 1 ms, and the remaining PDB for the other portion of the data (e.g., shown 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 shown as remaining PDB range 1, e.g., 0 ms to 2 ms. In this case, the BSR shows the following two items, namely LCG0 and data amount 0. In other words, the total data amount of the buffered data on LCH1 (i.e., data 0 and data 1) is reported via LCG0, and for example, data amount 0 corresponding to LCG0 includes the total data amount of the buffered data on LCH1.

[0186] For example, referring to Figure 13, still based on the example where the first LCH is LCH1, in the buffered data on LCH1, the remaining PDB for a portion of the data (e.g., shown as data 1) is 1 ms, the remaining PDB for another portion of the data (e.g., shown as data 2) is 3 ms, and the remaining PDB for yet another portion of the data (e.g., shown as data n) is 2n-1 milliseconds. 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 shown as remaining PDB range 1, e.g., 0 ms to 2 ms. In this case, the BSR shows the following two items, namely LCG1 and data amount 1. In other words, the total data amount of the buffered data on LCH1 (i.e., data 1 to data n) is reported via LCG1. Correspondingly, data amount 1 corresponding to LCG1 includes the total data amount of the buffered data on LCH1.

[0187] In other words, even if the buffered data on the first LCH contains data from different remaining PDBs, the terminal device determines the LCG indicated by the BSR based on the smallest remaining PDB. Thus, after receiving the BSR, the network device may know the amount of data and the remaining PDB range and allocate uplink resources appropriately. For example, when the remaining PDBs indicated by the remaining PDB range are small, the network device can improve uplink scheduling efficiency by preferentially allocating uplink resources based on the amount of data corresponding to the remaining PDB range.

[0188] Example 2 In Example 2, the configuration case for the first LCH is configuration case 2. Correspondingly, the configuration rule used is shown in Table 2 (or Table 3) in configuration rule 1. The following explanation is provided by using three implementation methods (i.e., implementation methods 4 to 6 below).

[0189] In implementation method 4 of 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 the first LCG is associated with the first remaining PDB range, and the buffered data on the first LCH further includes the second data, the BSR indicates not only the first data amount and the first LCG, but also the second data amount and the second LCG. The first data amount corresponds to the first LCG, the first data amount includes the data amount of the first data, and the remaining PDB of the first data is within the range of the first remaining PDB. The second data amount corresponds to the second LCG, the second data amount includes the data amount of the second data, and the remaining PDB of the second data is within the range of the second remaining PDB.

[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 2ms, i.e., T=2ms. In the buffered data on LCH1, the remaining PDB for a portion of the data (e.g., shown as data 0) is 1ms, the remaining PDB is less than the PDB threshold, and the remaining PDB range for the remaining PDB is shown as remaining PDB range 1, e.g., 0ms to 2ms; the remaining PDB for the other portion of the data (e.g., shown as data 1) is 3ms, the remaining PDB is greater than the PDB threshold, and the remaining PDB range for the remaining PDB is shown as remaining PDB range 2, e.g., 2ms to 4ms. In this case, the BSR shows the following four items: LCG0, data amount 0, LCG1, and data amount 1. In other words, the data amount for data 0 on LCH1 is reported via LCG0, for example, data amount 0 corresponding to LCG0 includes the data amount for data 1, and the data amount for data 1 on LCH1 is reported via LCG1, for example, data amount 1 corresponding to LCG1 includes the data amount for data 2.

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

[0193] It can be easily understood that, based on the remaining PDBs, the buffered data on the first LCH may be assigned to a smaller remaining PDB range. For example, all remaining PDBs of the buffered data on the first LCH are below the PDB threshold. In this case, the buffered data on the first LCH is assigned to one remaining PDB range, indicated as remaining PDB range 1. Remaining PDB range 1 may be considered the first remaining PDB range. For the indication state of the BSR, see the description of the first data amount and the first LCG in implementation 4. Further details are not described herein. For example, referring to Figure 23, based on the example where the first LCH is one of LCH1 to LCHn, in the buffered data on the first LCH, when the remaining PDBs of the buffered data are below the PDB threshold (θ), the data amount of the buffered data (i.e., the first data amount) is reported via the first LCG.

[0194] Alternatively, all remaining PDBs of the buffered data on the first LCH are greater than the PDB threshold. In this case, the buffered data on the first LCH is allocated to one remaining PDB range, indicated as remaining PDB range 2. Remaining PDB range 2 may be considered a second remaining PDB range. For the indication state of the BSR, see the description of the second data amount and the second LCG in implementation method 4. Further details are not described herein.

[0195] In other words, even if the buffered data on the first LCH includes data from different remaining PDBs, the terminal device determines at least one LCG indicated by the BSR based on the remaining PDBs. For example, if the remaining PDBs are less than the PDB threshold, the terminal device reports a portion of the data amount via the first LCG, or if the remaining PDBs are greater than or equal to the PDB threshold, the terminal device reports a portion of the data amount via the second LCG. Thus, after receiving the BSR, the network device may know at least one data amount, at least one remaining PDB range, and the correspondence between the data amount and the remaining PDB range, and allocate uplink resources appropriately. For example, if the remaining PDBs indicated by the remaining PDB range are 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 PDBs indicated by the remaining PDB range are large and transmission resources are insufficient, the network device may allocate uplink resources later based on the amount of data corresponding to the remaining PDB range, or it may improve uplink scheduling efficiency by prioritizing the allocation of uplink resources to the amount of data corresponding to smaller remaining PDBs.

[0196] In implementation method 5 of 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 the first LCG is associated with the first remaining PDB range, and the buffered data on the first LCH includes packets in a data burst, there exists at some point one remaining PDB of the buffered data on the first LCH. When the remaining PDB of the buffered data on the first LCH is within the range of the first remaining PDB, 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. It can be understood that the first data is all of the buffered data on the first LCH. Correspondingly, the BSR indicates the first data amount and the first LCG, the first data amount corresponds to the first LCG, the first data amount includes the data amount of the first data, and the remaining PDB of the first data is within the range of the first remaining PDB.

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

[0199] In other words, when the buffered data on the first LCH has the same remaining PDBs, for example, when the remaining PDBs are less than or equal to the PDB threshold, the terminal device reports the amount of data buffered via one LCG (i.e., the first LCG). Thus, after receiving the BSR, the network device knows the amount of data and the remaining PDB range and may allocate uplink resources, resulting in the terminal device uploading 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, the buffered data on the first LCH is reported via the same LCG when there are at least two remaining PDBs for the buffered data on the first LCH, and the smallest of the two remaining PDBs is used to determine the remaining PDB range corresponding to the buffered data.

[0201] Specifically, when a first LCG is associated with a first remaining PDB range, and the buffered data on a first LCH contains packets in different data bursts, there are at least two remaining PDBs for the buffered data on the first LCH at some point in 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 fact that the remaining PDB for the first data is 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, for example, 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 the first data amount and the first LCG, where the first data amount corresponds to the first LCG, the first data amount includes the data amount of the first data, and the remaining PDB for the first data is 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, in the buffered data on LCH1, the remaining PDB for a portion of the data (e.g., shown as data 0) is 1 ms, and the remaining PDB for the other portion of the data (e.g., shown 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 shown as remaining PDB range 1, e.g., 0 ms to 2 ms. In this case, the BSR shows the following two items, namely LCG0 and data amount 0. In other words, the total data amount of the buffered data on LCH1 (i.e., data 0 and data 1) is reported via LCG0, and for example, data amount 0 corresponding to LCG0 includes the total data amount of the buffered data on LCH1.

[0203] For example, referring to Figure 16, still based on the example where the first LCH is LCH1, the PDB threshold is set to 2ms, i.e., T=2ms. In the buffered data on LCH1, the remaining PDB for a portion of the data (e.g., shown as Data 1) is 1ms, and the remaining PDB for the other portion of the data (e.g., shown as Data 2) is 3ms. 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 1ms, 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., 0ms to 2ms. In this case, the BSR shows the following two items, namely LCG0 and data amount 0. In other words, the total data amount of the buffered data on LCH1 (i.e., Data 1 and Data 2) is reported via LCG0. Correspondingly, data amount 0 corresponding to LCG0 includes the total data amount of the buffered data on LCH1.

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

[0205] In other possible implementations, the configuration rule in S802 includes configuration rule 2. In this case, 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 PDBs of the first data and the data type of the first data. See the explanations in Examples 3 and 4 for details.

[0206] Example 3 In Example 3, the configuration case for the first LCH is configuration case 1. Correspondingly, the configuration rule used is shown in Table 4 under Configuration Rule 2. The following explanation is provided using two implementation methods (implementation methods 7 and 8 below).

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

[0208] First, let's explain the function of data types in the priority level determination process. A 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 contains 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 contains 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 Figure 17, the first type of data may be I-type, i.e., I-frame data, and the second type of data may be P-type, i.e., P-frame data, with the first set including LCG0, LCG2, LCG4, and LCG6, and the second set including LCG1, LCG3, LCG5, and LCG7.

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

[0211] As shown in Figure 17, when the first data is P-frame data, 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 PDBs of the first data. For details, see the following descriptions of implementation methods 7 and 8.

[0212] Next, we will describe the function of remaining PDBs in the priority level determination process. The first data is used as an example. When the buffered data on the first LCH is of the same type, 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, see the description of implementation method 7 in configuration case 1.

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

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

[0215] In implementation method 7 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.

[0216] Specifically, when the first LCG is associated with the first priority level range, and the buffered data on the first LCH includes packets in a data burst, there exists at some point one remaining PDB of the buffered data on the first LCH. 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 as all of the buffered data on the first LCH. Correspondingly, the BSR indicates the first data amount and the first LCG, the first data amount corresponds to the first LCG, the first data amount includes the data amount of the first data, and the remaining PDB of the first data is within the range of the first remaining PDB.

[0217] For example, referring to Figure 18 or Figure 24, still based on the example where the first LCH is LCH1, at time 1, all remaining PDBs for the buffered data on LCH1 (e.g., shown as Data 1) are 1 ms, and the priority level determined based on the remaining PDBs is within priority level range 1, e.g., 1-2. In this case, the BSR shows the following two items: LCG1 and Data Quantity 1. In other words, all data quantities for the buffered data on LCH1 (e.g., Data 1) are reported via LCG1, and for example, Data Quantity 1 corresponding to LCG1 includes all data quantities for the buffered data on LCH1. At time 2, all remaining PDBs for the buffered data on LCH1 (e.g., shown as Data 2) are 3 ms, and the priority level determined based on the remaining PDBs is within priority level range 2, e.g., 3-4. Priority level range 2 is not shown in Figure 18. In this case, the BSR shows the following two items: LCG2 and Data Quantity 2. In other words, the total amount of buffered data on LCH1 (e.g., data 2) 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 is of the same type and has the same remaining PDB, the terminal device reports the amount of data buffered through one LCG (i.e., the first LCG). Thus, after receiving the BSR, the network device knows the amount of data and the priority level range and may allocate uplink resources, resulting in the terminal device uploading 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, the buffered data on the first LCH is reported via the same LCG when there are at least two remaining PDBs for the buffered data on the first LCH, and the smallest of the two remaining PDBs is used to determine the priority level range corresponding to the buffered data.

[0220] Specifically, when a first LCG is associated with a first priority level range, and the buffered data on a first LCH contains packets in different data bursts, at some point there are at least two remaining PDBs for the buffered data on the first LCH. When the smallest remaining PDB for the buffered data on the first LCH is used to determine the priority level range corresponding to the buffered data, the fact that the remaining PDBs for the first data are within the first priority level range can be understood as the smallest remaining PDB for 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 the first data amount and the first LCG, where the first data amount corresponds to the first LCG, the first data amount includes the data amount of the first data, and the remaining PDBs for the first data are 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, in the buffered data on LCH1, the remaining PDB for a portion of the data (e.g., shown as data 0) is 1 ms, and the remaining PDB for the other portion of the data (e.g., shown 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 shown as priority level range 1, e.g., 1-2. In this case, the BSR shows the following two items: LCG0 and data amount 0. In other words, the total data amount of the buffered data on LCH1 (i.e., data 0 and data 1) is reported via LCG0, and for example, data amount 0 corresponding to LCG0 includes the total data amount of the buffered data on LCH1.

[0222] For example, referring to Figure 19, still based on the example where the first LCH is LCH1, in the buffered data on LCH1, the remaining PDB for a portion of the data (e.g., shown as data 1) is 1 ms, the remaining PDB for another portion of the data (e.g., shown as data 2) is 3 ms, and the remaining PDB for yet another portion of the data (e.g., shown as data n) is 2n-1 milliseconds. 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 shown as priority level range 1, e.g., 1-2. In this case, the BSR shows the following two items, namely LCG1 and data quantity 1. In other words, the total data quantity of the buffered data on LCH1 (i.e., data 1-data n) is reported via LCG1, and for example, data quantity 1 corresponding to LCG1 includes the total data quantity of the buffered data on LCH1.

[0223] In other words, even if the buffered data on the first LCH includes data from 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. Thus, after receiving the BSR, the network device may know the amount of data and the priority level range and allocate uplink resources appropriately. For example, when the priority level indicated by the priority level range is low, the network device can improve uplink scheduling efficiency by preferentially allocating uplink resources based on the amount of data corresponding to the priority level range.

[0224] In Example 3, it can be easily understood that the network device constitutes one priority level range for each LCH. A first LCH is used as an example. As shown in Figure 27, the logical channel grouping method in this embodiment of the 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 the priority level range corresponding to the first LCH. For example, the priority level range configured using the fourth configuration information includes all or part of 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 1, the priority level of the first LCH is priority level 1. At time 2, the priority level of the first LCH is priority level 2. For further details, see the descriptions of implementation methods 7 and 8 in configuration case 1. Further details will not be described again herein.

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

[0228] It should be understood that in this embodiment of the application, an example is used in which the first data is all of the buffered data on the first LCH. The priority level of the first data is equivalent 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 using the fourth configuration information is shown as (1,16). In other words, the priority levels of the first LCH may be dynamically adjusted among 16 priorities (i.e., priority levels 1 to 16).

[0230] Figure 18 (or Figure 19) is used as an example. The LCG range configured for the first LCH (indicated as LCH1) using the second configuration information is shown 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 is executed before S801, and that S806 and S807 may be executed simultaneously. For example, the fourth and fifth configuration information are transmitted via the same message. Alternatively, the network device executes S806 first, and then S807. This is not limited to the embodiments of this application. In S807, the first LCH is used as an example for illustrative purposes. When the terminal device has another LCH, for example, a second LCH which 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 to the embodiments of this application.

[0232] Example 4 In Example 4, the configuration case for the first LCH is configuration case 2. Correspondingly, the configuration rules used are those shown in Table 5 (or Table 6) in configuration rule 2. The following explanation is provided using two implementation methods (implementation methods 9 and 10 below).

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

[0234] For details on the function of data types in the priority level determination process, please refer to the explanation in Example 3. Further details will not be provided again in this specification.

[0235] Next, we will describe the function of remaining PDBs in the priority level determination process. The first data is used as an example. When the buffered data on the first LCH is of the same type, 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, see the description of implementation method 9 in configuration case 2.

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

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

[0238] In implementation method 9 of 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 the first LCG is associated with the first priority level range, and the buffered data on the first LCH includes packets in a data burst, there exists at some point one remaining PDB of the buffered data on the first LCH. When the priority level of the buffered data on the first LCH is within the first priority level range, for example, below the priority level threshold, 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. It can be understood that the first data is all of the buffered data on the first LCH. Correspondingly, the BSR indicates the first data amount and the first LCG, the first data amount corresponds to the first LCG, the first data amount 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 Figure 20, still based on the example where the first LCH is LCH1, the priority level threshold is set to 2ms, i.e., K=2. The normal LCGs configured for the first LCH include LCG2, LCG4, and LCG6. See Related Techniques for details. An LCG further configured for the first LCH is LCG0. At time 1, all remaining PDBs of the buffered data on LCH1 (e.g., shown as data 0) are 1ms, the priority level determined based on the remaining PDBs (e.g., priority level is 1) is less than the priority level threshold, and the priority level range determined based on the remaining PDBs is shown as priority level range 1, e.g., 1~K. In this case, the BSR shows the following two items, namely LCG0 and data amount 0. In other words, all data amounts of the buffered data on LCH1 (i.e., data 0) are reported via LCG0, and for example, data amount 0 corresponding to LCG0 includes all data amounts of the buffered data on LCH1. At time point 2, the total remaining PDB for all buffered data on LCH1 is 3ms, the priority level determined based on the remaining PDB (e.g., priority level is 3) is greater than the priority level threshold, and the priority level range determined based on the remaining PDB is shown as priority level range 2, e.g., K~Kmax, which is not shown in Figure 20. In this case, the BSR shows the following two items: LCG1 and data quantity 1. In other words, the total data quantity for all buffered data on LCH1 is reported via LCG1, and for example, data quantity 1 corresponding to LCG1 includes the total data quantity for all buffered data on LCH1.

[0241] An example is used where the first LCH is LCH2. The priority level threshold is set to 2ms, i.e., K=2. The normal LCGs configured for the first LCH include LCG3, LCG5, and LCG7. See related techniques for details. An LCG further configured for the first LCH is LCG1. At time 1, all remaining PDBs of buffered data on LCH2 are 1ms, the priority level determined based on the remaining PDBs (e.g., priority level is 1) is less than the priority level threshold, and the priority level range determined based on the remaining PDBs is shown as priority level range 1, e.g., 1~K. In this case, the BSR shows the following two items, namely 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 the data amount of all buffered data on LCH2.

[0242] In other words, when the buffered data on the first LCH is of the same type and has the same remaining PDB, for example, when the priority level determined based on the remaining PDB is below 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 data buffered through one LCG (i.e., the first LCG). Thus, after receiving the BSR, the network device knows the amount of data and the priority level range and may allocate uplink resources, resulting in the terminal device uploading the buffered data on the first LCH in a timely manner. This improves uplink scheduling efficiency.

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

[0244] Specifically, when a first LCG is associated with a first priority level range, and the buffered data on a first LCH contains packets in different data bursts, at some point there are at least two remaining PDBs for the buffered data on the first LCH. When the smallest remaining PDB for the buffered data on the first LCH is used to determine the priority level range corresponding to the buffered data, the first data's priority level being within the first priority level range can be understood as the lowest priority level for 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 among at least two remaining PDBs. The buffered data on the first LCH is the first data. Correspondingly, the BSR indicates the first data amount and the first LCG, where the first data amount corresponds to the first LCG, the first data amount includes the data amount of the first data, and the remaining PDBs for the first data are 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, in the buffered data on LCH1, the remaining PDB for a portion of the data (e.g., shown as data 0) is 1 ms, and the remaining PDB for the other portion of the data (e.g., shown 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 shown as priority level range 1, e.g., 1-2. In this case, the BSR shows the following two items: LCG0 and data amount 0. In other words, the total data amount of the buffered data on LCH1 (i.e., data 0 and data 1) is reported via LCG0, and for example, data amount 0 corresponding to LCG0 includes the total data amount of the buffered data on LCH1.

[0246] For example, referring to Figure 21, still based on the example where the first LCH is LCH1, the priority level threshold is set to 2, i.e., K=2. The normal LCGs configured for the first LCH include LCG2, LCG4, and LCG6. See Related Techniques for details. An LCG further configured for the first LCH is LCG0. In the buffered data on LCH1, the remaining PDB for a portion of the data (e.g., shown as data 0) is 1 ms, and the remaining PDB for the other portion of the data (e.g., shown as data 1) 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., priority level is 1) is less than the priority level threshold, and the priority level range determined based on the remaining PDB is shown as priority level range 1, e.g., 1~K. In this case, the BSR shows the following two items, namely LCG0 and data amount 0. In other words, the total amount of buffered data on LCH1 (i.e., data 0 and data 1) is reported via LCG0. Correspondingly, data amount 0 corresponding to LCG0 includes the total amount of buffered data on LCH1.

[0247] For example, consider an example where the first LCH is LCH2. The priority level threshold is set to 2, i.e., K=2. The standard LCGs configured for the first LCH include LCG3, LCG5, and LCG7. See Related Techniques for details. Another LCG further configured for the first LCH is LCG1. In the buffered data on LCH2, the remaining PDB for some of the data is 1ms, and the remaining PDB for other parts of the data is 3ms. 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 1ms, the priority level determined based on the remaining PDB (e.g., priority level is 1) is less than the priority level threshold, and the priority level range determined based on the remaining PDB is shown as priority level range 1, e.g., 1~K. In this case, the BSR shows the following two items, namely LCG1 and data amount 1. In other words, the data amount of all buffered data on LCH2 is reported via LCG1. Accordingly, the data amount 1 corresponding to LCG1 includes the total amount of buffered data on LCH2.

[0248] In other words, even if the buffered data on the first LCH includes data from 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. Thus, after receiving the BSR, the network device may know the amount of data and the priority level range and allocate uplink resources appropriately. For example, when the priority level indicated by the priority level range is below the priority level threshold, the network device can improve uplink scheduling efficiency by preferentially allocating uplink resources based on the amount of data corresponding to the priority level range.

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

[0250] S808: The network device allocates uplink resources to terminal devices based on a first data volume and a first LCG, according to pre-configured configuration rules.

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

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

[0253] For example, if the remaining PDB range for the first time is 29ms to 30ms, the network device may later allocate uplink resources to a terminal device (for example, in the 5th or 10th ms after the BSR is received). During this period (for example, 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 0ms to 2ms, the network device preferentially allocates uplink resources to the terminal device (for example, in the first 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 terminal devices based on the first priority level range and the first data volume.

[0256] For example, when the first priority level range is 15-16, the network device may later allocate uplink resources to a terminal device (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-2, the network device preferentially allocates uplink resources to the terminal device (for example, within 1ms after the BSR is received).

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

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

[0260] For terminal devices, after uplink resources are allocated to the terminal device, the terminal device preferentially transmits buffered data corresponding to a first data volume over 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 data volume over the uplink resources. For further details, refer to related technologies. Details are not described again in this specification.

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

[0262] The above describes, primarily, the solutions provided in embodiments of this application from the perspective of the interaction between network elements. Correspondingly, embodiments of this application further provide communication devices. The communication device may be a network element in an embodiment of the above method, a device including the above network element, or a component that may 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. Those skilled in the art should readily recognize, in combination with the examples described in the embodiments disclosed in this specification, that the units and algorithmic steps can be realized in this application by hardware or by 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 should not be considered to exceed the scope of this application.

[0263] For example, Figure 28 shows 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 placed 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 placed in a network device.

[0264] As shown in FIG. 28, the communication device 2800 may include a processor 2801. Optionally, the communication 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 through a communication bus.

[0265] Hereinafter, referring to FIG. 28, each component of the communication device 2800 will be described in detail.

[0266] The processor 2801 is the control center of the communication device 2800, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 2801 may be one or more central processing units (CPUs), or may be an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the 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 a software program stored in the memory 2802, call data stored in the memory 2802, and execute various functions of the communication device 2800.

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

[0269] In a specific implementation, the communication device 2800 may, in an embodiment, include, alternatively, multiple processors, for example, processors 2801 and 2804 shown in Figure 28. Each processor may be a single-core processor (single CPU) or a multi-core processor (multi-CPU). In this specification, a processor may refer to one or more devices, circuits and / or processing cores configured to process data (e.g., computer program instructions).

[0270] Memory 2802 is configured to store a software program for executing the solution of this application, and processor 2801 controls the execution of the software program. For specific implementations, refer to embodiments of the method described above. Further details are not described herein again.

[0271] Optionally, memory 2802 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, or a random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital multipurpose discs, Blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store expected program code in the form of instructions or data structures and is accessible by a computer. However, this is not limited to these. Memory 2802 may be integrated with processor 2801 or may exist independently, and is coupled to processor 2801 through an interface circuit of communication device 2800 (not shown in Figure 28). This is not particularly limited to 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 Figure 28). The receiver is configured to perform receiving functions, and the transmitter is configured to perform transmitting functions.

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

[0275] It can be easily understood that the structure of the communication device 2800 shown in Figure 28 does not constitute a limitation on communication devices. Actual communication devices may include more or fewer components than those shown in the drawing, or they may be combinations of several components, or they may have different component arrangements.

[0276] Furthermore, for the technical effects of the communication device 2800, refer to the technical effects of the method in the embodiment of the method described above. 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 it may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, 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 or 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. Many forms of random access memory (RAM), such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (DR RAM), may be used, but not as an example.

[0279] Optionally, embodiments of this application further provide a computer program product for carrying computer instructions. When computer instructions are executed on a computer, the computer becomes capable of performing the methods described in the above embodiments.

[0280] Optionally, embodiments of this application further provide a computer-readable storage medium for storing computer instructions. When the computer instructions are executed on a computer, the computer becomes capable of performing the methods described in the above embodiments.

[0281] Optionally, embodiments of this application further provide a chip comprising a processing circuit and a transceiver circuit. The processing circuit and the transceiver circuit are configured to implement the methods described in the embodiments described above. The processing circuit is configured to perform processing operations in the corresponding methods, and the transceiver circuit is configured to perform receiving / transmitting operations in the corresponding methods.

[0282] All or part of the embodiments described above may be implemented using software, hardware (e.g., circuitry), firmware, or a combination thereof. When software is used to implement the embodiments, the embodiments may be implemented all or partly in the form of a computer program product. A 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, all or part of the procedures or functions according to the embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted by wired means (e.g., infrared, wireless, or microwave) from one website, computer, server, or data center to another website, computer, server, or data center. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device that integrates one or more available media, such as a server or data center. The usable media may be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., DVDs), or semiconductor media. The semiconductor media may also be solid-state drives.

[0283] The term "and / or" in this specification should be understood to describe only the association relationship for describing the related objects, and that three relationships may exist. For example, A and / or B may represent the following three cases: that only A exists, that both A and B exist, and that only B exists, and A and B may be singular or plural. Furthermore, the letter " / " in this specification usually indicates an "or" relationship between related objects, but may also indicate an "and / or" relationship. Refer to the context for further details.

[0284] In this application, "at least one" means one or more, and "a plurality" means two or more. "At least one of the following items (parts)" or a similar expression means any combination of these items, including a combination of a single item (part) or a plurality of items (parts). For example, at least one of a, b, or c may indicate a, b, c, a-b, a-c, b-c, or a-b-c, and 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 process should be determined based on the functions and internal logics of the process, and should not be construed as any limitation to 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 implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the function is executed by hardware or by software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but the implementation manner should not be considered to exceed the scope of this application.

[0287] For the purpose of convenience and concise description, those skilled in the art can clearly understand by referring to the corresponding processes in the embodiments of the above method for the detailed operation processes of the above system, device, and unit. 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, apparatus and methods may be implemented in other ways. For example, the embodiments of the apparatus described above are merely examples. For example, the division into units is merely a logical functional division, 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 ignored or not performed. Furthermore, the mutual coupling, direct coupling or communication connection indicated or discussed may be implemented through some interfaces. Indirect coupling or communication connection between apparatus or units may be implemented electronically, mechanically or in other forms.

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

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

[0291] When a function is implemented in the form of a software function unit and sold or used as an independent product, the function may be stored on a computer-readable storage medium. Based on this understanding, the technical solution of this application, or a portion of the technical solution that contributes to the prior art, may be implemented in the form of a software product. The computer software product is stored on a storage medium and includes several 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 embodiments of this application. The storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0292] The above description is merely a specific way of realizing this application and is not intended to limit the scope of protection of this application. Any modification or substitution that is readily conceivable by a person skilled in the art within the scope of the art disclosed in this application shall fall within the scope of protection of this application. Accordingly, the scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. A method performed by a terminal device or a chip within a terminal device, The steps include determining that the buffered data to be reported resides on the first logical channel (LCH), The steps include sending a buffer status report (BSR) to a network device based on the buffered data to be reported on the first LCH, according to a pre-configured configuration rule, and Includes, The BSR indicates a first data volume and a first logical channel group (LCG), the first data volume corresponds to the first LCG, the first data volume includes the data volume 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 the first remaining PDB range, the configuration rule is configuration rule 1, i.e., 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, the first LCG is associated with the first remaining PDB range, and L is a positive integer greater than or equal to 2, or The priority level of the first data is within the first priority level range, the priority level of the first data is determined based on the remaining PDBs 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, 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, method.

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

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

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

5. There are at least two remaining PDBs for the buffered data, and the remaining PDB for the first data is within the range of the first remaining PDB. 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 lies within the first remaining PDB range, The method according to claim 1, wherein the buffered data is the first data.

6. When the remaining PDB of the first data is within the range of the first remaining PDB, the method determines that the buffered data to be reported is present on the first LCH, The method according to claim 1, further comprising the step of receiving first configuration information from the network device, wherein the first configuration information indicates the configuration rule 1.

7. Before determining that the buffered data to be reported is present on the first LCH, the method: The method according to claim 6, further comprising the step of receiving 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. The method according to claim 2, wherein the second remaining PDB range is [T, Pmax], where T is the PDB threshold and Pmax is the maximum transmission latency allowed for the buffered data.

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

10. The method according to claim 1, wherein when the configuration rule includes 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 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 the first type of data, or The method according to claim 10, wherein when the first data is of a second type, the first LCG is an LCG in a second set, the second set comprises at least one LCG, each LCG in the second set is used to transmit the second type of data, 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 range of the first priority level, the buffered data includes the first data. When the buffered data is of the same type, and there is one remaining PDB of the buffered data, the buffered data is the first data, or The buffered data is the first data when the buffered data is of the same type, there are at least two remaining PDBs for the buffered data, and the smallest remaining PDB for the buffered data is used to determine the priority level of the buffered data. The method according to claim 11, including the method described in claim 11.

13. Before determining that the buffered data to be reported is present on the first LCH, the method: The method according to claim 10, further comprising the step of receiving a third configuration information from the network device, wherein the third configuration information indicates the configuration rule 2.

14. Before determining that the buffered data to be reported is present on the first LCH, the method: The method according to claim 13, further comprising the step of receiving a fourth configuration information from the network device, the fourth configuration information being used to configure a priority level range corresponding to the first LCH, and the priority level range configured using the fourth configuration information comprising 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]. The method according to claim 10, wherein K represents a priority level threshold and Kmax represents the lowest priority level that may exist in the buffered data.

16. Before determining that the buffered data to be reported is present on the first LCH, the method: The method according to claim 1, further comprising the step of receiving a fifth configuration information from the network device, wherein the fifth configuration information is used to configure the first LCG for the first LCH.

17. A method performed by a network device or a chip within a network device, The steps include receiving a Buffer Status Report (BSR) from a terminal device, wherein the buffered data to be reported resides on a first logical channel (LCH) of the terminal device, the BSR indicates a first data volume and a first logical channel group (LCG), the first data volume corresponds to the first LCG, the first data volume includes the data volume 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, and The steps include allocating uplink resources to the terminal device based on the first data volume and the first LCG, according to a pre-configured configuration rule, and Includes, 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., 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, the first LCG is associated with the first remaining PDB range, and L is a positive integer greater than or equal to 2, or The priority level of the first data is within the first priority level range, the priority level of the first data is determined based on the remaining PDBs 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, 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, method.

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

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

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

21. There are at least two remaining PDBs for the buffered data, and the remaining PDB for the first data is within the range of the first remaining PDB. 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 lies within the first remaining PDB range, The method according to claim 17, wherein the buffered data is the first data.

22. When the remaining PDB of the first data is within the range of the first remaining PDB, before receiving the BSR from the terminal device, the method The method according to claim 17, further comprising the step of transmitting first configuration information to a terminal device, wherein the first configuration information indicates the configuration rule 1.

23. Before receiving a BSR from a terminal device, the method The method according to claim 22, further comprising the step of transmitting a second configuration information to the terminal device, wherein 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.

24. The method according to claim 18, wherein the second remaining PDB range is [T, Pmax], where T is the PDB threshold and Pmax is the maximum transmission latency allowed for the buffered data.

25. The method according to claim 17, wherein the first remaining PDB range is [0, T), where T represents the PDB threshold.

26. The method according to claim 17, wherein when the configuration rule includes 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 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 the first type of data, or The method according to claim 26, wherein when the first data is of a second type, the first LCG is an LCG in a second set, the second set comprises at least one LCG, each LCG in the second set is used to transmit the second type of data, 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 range of the first priority level, the buffered data includes the first data. When the buffered data is of the same type, and there is one remaining PDB of the buffered data, the buffered data is the first data, or The buffered data is the first data when the buffered data is of the same type, there are at least two remaining PDBs for the buffered data, and the smallest remaining PDB for the buffered data is used to determine the priority level of the buffered data. The method according to claim 27, including the method described in claim 27.

29. Before receiving a BSR from a terminal device, the method The method according to claim 26, further comprising the step of transmitting a third configuration information to the terminal device, wherein the third configuration information indicates the configuration rule 2.

30. Before receiving a BSR from a terminal device, the method The method according to claim 29, further comprising the step of transmitting a fourth configuration information to the terminal device, wherein the fourth configuration information is used to configure a priority level range corresponding to the first LCH, and the priority level range configured by using the fourth configuration information includes one or more priority levels within the L priority level ranges.

31. The method according to 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 exist in the buffered data.

32. Before receiving a BSR from a terminal device, the method The method according to claim 17, further comprising the step of transmitting a fifth configuration information to the terminal device, wherein the fifth configuration information is used to configure the first LCG for the first LCH.

33. A communication device including a processor and memory, A communication device wherein the processor is coupled to the memory, the memory stores program instructions, and when executed by the processor, the method according to any one of claims 1 to 16 is realized.

34. A communication device including a processor and memory, A communication device wherein the processor is coupled to the memory, the memory stores program instructions, and when executed by the processor, the method according to any one of claims 17 to 32 is realized.

35. A computer program, A computer program that, when executed on a communication device, realizes the method described in any one of claims 1 to 16.

36. A computer program, A computer program that, when executed on a communication device, realizes the method described in any one of claims 17 to 32.

Images