A method and apparatus for reporting a buffer status report, a communication device, and a storage medium

Abstract

Embodiments of the present disclosure provide a buffer status report reporting method and apparatus, a communication device and a storage medium; a user equipment (UE) reports a buffer status report (BSR) for uplink data with emergency scheduling requirements.

Description

Technical Field

[0001] This disclosure relates to, but is not limited to, the field of communication technology, and in particular to a method, apparatus, communication device, and storage medium for reporting cache status. Background Technology

[0002] In Extended Reality (XR) services, XR service data typically consists of multiple data streams (Qosflow), resulting in a very large data volume. Furthermore, XR service streams need to meet certain latency requirements during transmission, especially since some data streams need to arrive at the server simultaneously for decoding. Delay in any one of these data streams will cause the joint decoding of multiple data streams to fail. Summary of the Invention

[0003] This disclosure presents a method, apparatus, communication device, and storage medium for reporting cache status.

[0004] According to a first aspect of this disclosure, a cache status report reporting method is provided, wherein the method is executed by a user equipment (UE) and includes:

[0005] For uplink data with urgent scheduling needs, a Cache Status Report (BSR) is submitted.

[0006] In one embodiment, reporting a BSR for uplink data with urgent scheduling needs includes:

[0007] The logical channel corresponding to the uplink data with urgent scheduling needs is determined as the highest priority, and the BSR is reported based on the priority of the logical channel.

[0008] In one embodiment, reporting a BSR for uplink data with urgent scheduling needs includes:

[0009] In response to uplink data indicating an urgent scheduling requirement on the logical channel, the BSR of the logical channel is triggered for reporting.

[0010] In one embodiment, reporting a BSR for uplink data with urgent scheduling needs includes:

[0011] In response to uplink data indicating an urgent scheduling requirement on at least one logical channel, a first type of BSR is triggered on the first logical channel, wherein the first type of BSR has a higher priority than the second type of BSR, and the first logical channel is the logical channel with the highest priority among the at least one logical channels.

[0012] In one embodiment, reporting a BSR for uplink data with urgent scheduling needs includes:

[0013] In response to uplink data indicating an urgent scheduling requirement for a logical channel, the logical channel is determined to have a first highest priority, and the BSR is reported based on the first highest priority, wherein the first highest priority is higher than the second highest priority.

[0014] In one embodiment, the uplink data includes: extended reality (XR) service uplink data.

[0015] In one embodiment, the uplink data with urgent scheduling requirements includes: the uplink data with a remaining packet delay budget less than a delay threshold.

[0016] In one embodiment, the granularity of the latency threshold configuration includes one of the following:

[0017] UE granularity;

[0018] Logical channel granularity;

[0019] Logical channel group granularity.

[0020] In one embodiment, the uplink data with urgent scheduling needs is at the data packet granularity.

[0021] or,

[0022] The uplink data with urgent scheduling needs is at the data packet set granularity.

[0023] In one embodiment, the method further includes:

[0024] Based on the first indication information obtained from the non-access layer or the application layer, it is determined that the uplink data has an urgent scheduling requirement.

[0025] In one embodiment, reporting a BSR for uplink data with urgent scheduling needs includes:

[0026] According to the second indication information sent by the base station, the BSR is reported for the uplink data with urgent scheduling needs.

[0027] In one embodiment, the second indication information includes: a latency threshold associated with the remaining packet latency budget of the uplink data.

[0028] In one embodiment, reporting the BSR for uplink data with urgent scheduling needs based on the second indication information sent by the base station includes one of the following:

[0029] According to the instructions of the second instruction information, the BSR is reported for the uplink data of the UE that has an urgent scheduling requirement;

[0030] According to the instructions of the second instruction information, the BSR is reported for the uplink data that has an urgent scheduling requirement for the predetermined logical channel;

[0031] According to the instructions of the second instruction information, the BSR is reported for the uplink data that has an urgent scheduling requirement for the predetermined logical channel group.

[0032] In one embodiment, the method further includes:

[0033] The UE sends auxiliary information to the base station, the auxiliary information being used to indicate that the UE can report the BSR for uplink data with urgent scheduling needs.

[0034] According to a second aspect of this disclosure, a method for reporting cache status is provided, wherein the method is executed by a base station and includes:

[0035] Receive buffer status report (BSR), wherein the BSR is sent by the user equipment (UE) for uplink data with urgent scheduling requirements.

[0036] In one embodiment, the BSR is a report made by the UE based on the priority of the logical channel corresponding to the uplink data with urgent scheduling needs, which is determined as the highest priority.

[0037] In one embodiment, the BSR is triggered by the UE in response to uplink data indicating an urgent scheduling requirement on the logical channel.

[0038] In one embodiment, the reported BSR includes: a first type of BSR, which is associated with a first logical channel;

[0039] The first type of BSR is the uplink data that the UE responds to in at least one logical channel having an urgent scheduling requirement, and the first logical channel is the logical channel with the highest priority among the at least one logical channels, wherein the priority of the first type of BSR is higher than that of the second type of BSR.

[0040] In one embodiment,

[0041] The BSR is a report made by the UE in response to uplink data indicating that the logical channel has an urgent scheduling requirement, determining that the logical channel has a first highest priority, and reporting it based on the first highest priority, wherein the first highest priority is higher than the second highest priority.

[0042] In one embodiment, the uplink data includes: extended reality (XR) service uplink data.

[0043] In one embodiment, the uplink data with urgent scheduling requirements includes: the uplink data with a remaining packet delay budget less than a delay threshold.

[0044] In one embodiment, the granularity of the latency threshold configuration includes one of the following:

[0045] UE granularity;

[0046] Logical channel granularity;

[0047] Logical channel group granularity.

[0048] In one embodiment, the uplink data with urgent scheduling needs is at the data packet granularity.

[0049] or,

[0050] The uplink data with urgent scheduling needs is at the data packet set granularity.

[0051] In one embodiment, the method further includes:

[0052] Send a second indication message to the UE, wherein the second indication message is used to instruct the UE to report the BSR for the uplink data with urgent scheduling requirements.

[0053] In one embodiment, the second indication information includes: a latency threshold associated with the remaining packet latency budget of the uplink data.

[0054] In one embodiment, the second indication information is used to indicate one of the following:

[0055] The BSR is reported for uplink data that the UE has an urgent scheduling requirement;

[0056] The uplink data with urgent scheduling requirements for the predetermined logical channel is reported to the BSR;

[0057] The uplink data with urgent scheduling requirements for a predetermined logical channel group is reported to the BSR.

[0058] In one embodiment, sending the second indication information to the UE includes:

[0059] In response to receiving auxiliary information sent by the UE, the second indication information is sent to the UE, wherein the auxiliary information is used to indicate that the UE can report the BSR for uplink data with urgent scheduling needs.

[0060] According to a third aspect of this disclosure, a cache status report reporting device is provided, wherein it is configured in a user equipment (UE) and includes:

[0061] The transceiver module is configured to report a cache status report (BSR) for uplink data with urgent scheduling needs.

[0062] In one embodiment, the transceiver module is specifically configured as follows:

[0063] The logical channel corresponding to the uplink data with urgent scheduling needs is determined as the highest priority, and the BSR is reported based on the priority of the logical channel.

[0064] In one embodiment, the transceiver module is specifically configured as follows:

[0065] In response to uplink data indicating an urgent scheduling requirement on the logical channel, the BSR of the logical channel is triggered for reporting.

[0066] In one embodiment, the transceiver module is specifically configured as follows:

[0067] In response to uplink data indicating an urgent scheduling requirement on at least one logical channel, a first type of BSR is triggered on the first logical channel, wherein the first type of BSR has a higher priority than the second type of BSR, and the first logical channel is the logical channel with the highest priority among the at least one logical channels.

[0068] In one embodiment, the transceiver module is specifically configured as follows:

[0069] In response to uplink data indicating an urgent scheduling requirement for a logical channel, the logical channel is determined to have a first highest priority, and the BSR is reported based on the first highest priority, wherein the first highest priority is higher than the second highest priority.

[0070] In one embodiment, the uplink data includes: extended reality (XR) service uplink data.

[0071] In one embodiment, the uplink data with urgent scheduling requirements includes: the uplink data with a remaining packet delay budget less than a delay threshold.

[0072] In one embodiment, the granularity of the latency threshold configuration includes one of the following:

[0073] UE granularity;

[0074] Logical channel granularity;

[0075] Logical channel group granularity.

[0076] In one embodiment, the uplink data with urgent scheduling needs is at the data packet granularity.

[0077] or,

[0078] The uplink data with urgent scheduling needs is at the data packet set granularity.

[0079] In one embodiment, the apparatus further includes:

[0080] The processing module is configured to determine, based on first indication information obtained from the non-access layer or the application layer, that the uplink data has an urgent scheduling requirement.

[0081] In one embodiment, the transceiver module is specifically configured as follows:

[0082] According to the second indication information sent by the base station, the BSR is reported for the uplink data with urgent scheduling needs.

[0083] In one embodiment, the second indication information includes: a latency threshold associated with the remaining packet latency budget of the uplink data.

[0084] In one embodiment, the transceiver module is specifically configured as one of the following:

[0085] According to the instructions of the second instruction information, the BSR is reported for the uplink data of the UE that has an urgent scheduling requirement;

[0086] According to the instructions of the second instruction information, the BSR is reported for the uplink data that has an urgent scheduling requirement for the predetermined logical channel;

[0087] According to the instructions of the second instruction information, the BSR is reported for the uplink data that has an urgent scheduling requirement for the predetermined logical channel group.

[0088] In one embodiment, the transceiver module is further configured to:

[0089] The UE sends auxiliary information to the base station, the auxiliary information being used to indicate that the UE can report the BSR for uplink data with urgent scheduling needs.

[0090] According to a fourth aspect of this disclosure, a buffer status report reporting device is provided, wherein it is disposed in a base station and includes:

[0091] The transceiver module is configured to receive a buffer status report (BSR), wherein the BSR is sent by the user equipment (UE) for uplink data with urgent scheduling requirements.

[0092] In one embodiment, the BSR is a report made by the UE based on the priority of the logical channel corresponding to the uplink data with urgent scheduling needs, which is determined as the highest priority.

[0093] In one embodiment, the BSR is triggered by the UE in response to uplink data indicating an urgent scheduling requirement on the logical channel.

[0094] In one embodiment, the reported BSR includes: a first type of BSR, which is associated with a first logical channel;

[0095] The first type of BSR is the uplink data that the UE responds to in at least one logical channel having an urgent scheduling requirement, and the first logical channel is the logical channel with the highest priority among the at least one logical channels, wherein the priority of the first type of BSR is higher than that of the second type of BSR.

[0096] In one embodiment, the BSR is the UE responding to uplink data indicating that the logical channel has an urgent scheduling requirement, determining that the logical channel has a first highest priority, and reporting it based on the first highest priority, wherein the first highest priority is higher than the second highest priority.

[0097] In one embodiment, the uplink data includes: extended reality (XR) service uplink data.

[0098] In one embodiment, the uplink data with urgent scheduling requirements includes: the uplink data with a remaining packet delay budget less than a delay threshold.

[0099] In one embodiment, the granularity of the latency threshold configuration includes one of the following:

[0100] UE granularity;

[0101] Logical channel granularity;

[0102] Logical channel group granularity.

[0103] In one embodiment, the uplink data with urgent scheduling needs is at the data packet granularity.

[0104] or,

[0105] The uplink data with urgent scheduling needs is at the data packet set granularity.

[0106] In one embodiment, the transceiver module is further configured to:

[0107] Send a second indication message to the UE, wherein the second indication message is used to instruct the UE to report the BSR for the uplink data with urgent scheduling requirements.

[0108] In one embodiment, the second indication information includes: a latency threshold associated with the remaining packet latency budget of the uplink data.

[0109] In one embodiment, the second indication information is used to indicate one of the following:

[0110] The BSR is reported for uplink data that the UE has an urgent scheduling requirement;

[0111] The uplink data with urgent scheduling requirements for the predetermined logical channel is reported to the BSR;

[0112] The uplink data with urgent scheduling requirements for a predetermined logical channel group is reported to the BSR.

[0113] In one embodiment, the transceiver module is specifically configured as follows:

[0114] In response to receiving auxiliary information sent by the UE, the second indication information is sent to the UE, wherein the auxiliary information is used to indicate that the UE can report the BSR for uplink data with urgent scheduling needs.

[0115] According to a fifth aspect of this disclosure, a communication device is provided, wherein the communication device comprises:

[0116] processor;

[0117] Memory used to store the processor's executable instructions;

[0118] The processor is configured to implement the cache status report reporting method described in the first or second aspect when running the executable instructions.

[0119] According to a sixth aspect of this disclosure, a computer storage medium is provided, wherein the computer storage medium stores a computer executable program, which, when executed by a processor, implements the cache status report reporting method described in the first or second aspect.

[0120] In this embodiment of the disclosure, the UE reports a BSR for uplink data with urgent scheduling needs. Thus, reporting a BSR for uplink data with urgent scheduling needs enables timely scheduling of such data, meeting communication service requirements, reducing data transmission errors such as joint decoding failures, and improving communication reliability.

[0121] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the embodiments of this disclosure. Attached Figure Description

[0122] Figure 1 This is a schematic diagram of the structure of a wireless communication system.

[0123] Figure 2 This is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.

[0124] Figure 3 This is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.

[0125] Figure 4 This is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.

[0126] Figure 5 This is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.

[0127] Figure 6 This is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.

[0128] Figure 7 This is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.

[0129] Figure 8 This is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.

[0130] Figure 9 This is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.

[0131] Figure 10 This is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.

[0132] Figure 11 This is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.

[0133] Figure 12 This is a block diagram illustrating a cache status reporting device according to an exemplary embodiment.

[0134] Figure 13 This is a block diagram illustrating a cache status reporting device according to an exemplary embodiment.

[0135] Figure 14 This is a block diagram illustrating a UE according to an exemplary embodiment.

[0136] Figure 15 This is a block diagram illustrating a base station according to an exemplary embodiment. Detailed Implementation

[0137] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of embodiments of this disclosure.

[0138] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of this disclosure. The singular forms “a” and “the” as used in this disclosure are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0139] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of embodiments of this disclosure, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0140] Please refer to Figure 1 This illustration shows a schematic diagram of the structure of a wireless communication system provided in an embodiment of this disclosure. Figure 1 As shown, the wireless communication system is a communication system based on cellular mobile communication technology. The wireless communication system may include: several user equipment 11 and several base stations 12.

[0141] User equipment 11 can be a device that provides voice and / or data connectivity to a user. User equipment 11 can communicate with one or more core networks via a Radio Access Network (RAN). User equipment 11 can be an Internet of Things (IoT) user equipment, such as sensor devices, mobile phones (or "cellular" phones), and computers with IoT user equipment capabilities. For example, it can be a fixed, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted device. Examples include a station (STA), subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, or user equipment. Alternatively, user equipment 11 can also be a device from an unmanned aerial vehicle (UAV). Alternatively, user equipment 11 can also be a vehicle-mounted device, such as a vehicle computer with wireless communication capabilities, or a wireless user equipment connected to an external vehicle computer. Alternatively, user equipment 11 can also be a roadside device, such as a street light, traffic light, or other roadside device with wireless communication capabilities.

[0142] Base station 12 can be a network-side device in a wireless communication system. This wireless communication system can be a 4G system (also known as Long Term Evolution, LTE); or it can be a 5G system (also known as a New Radio, 5G NR, or 5G NR system). Alternatively, it can be the next generation after 5G. In this case, the access network in the 5G system can be called a New Generation-Radio Access Network (NG-RAN).

[0143] In this embodiment, base station 12 can be an evolved NB (eNB) used in a 4G system. Alternatively, base station 12 can also be a gNB (gNB) using a centralized-distributed architecture in a 5G system. When base station 12 adopts a centralized-distributed architecture, it typically includes a central unit (CU) and at least two distributed units (DU). The central unit is equipped with a protocol stack of Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC) layers; the distributed units are equipped with a physical (PHY) layer protocol stack. This disclosure does not limit the specific implementation of base station 12.

[0144] Base station 12 and user equipment 11 can establish a wireless connection via a wireless air interface. In different implementations, the wireless air interface is a wireless air interface based on the fourth-generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth-generation mobile communication network technology (5G) standard, such as a new air interface; or, the wireless air interface can also be a wireless air interface based on a next-generation mobile communication network technology standard based on 5G.

[0145] In some embodiments, user equipment 11 can also establish E2E (End to End) connections. Examples include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, and vehicle-to-pedestrian (V2P) communication in vehicle-to-everything (V2X) communication.

[0146] Here, the user equipment mentioned above can be considered as the terminal equipment in the following embodiments.

[0147] In some embodiments, the wireless communication system described above may further include a network management device 13.

[0148] Several base stations 12 are connected to network management device 13. Network management device 13 can be a core network device in a wireless communication system, such as a Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Alternatively, it can be other core network devices, such as a Serving Gateway (SGW), a Public Data Network Gateway (PGW), a Policy and Charging Rules Function (PCRF), or a Home Subscriber Server (HSS). The implementation of network management device 13 is not limited in this embodiment.

[0149] To facilitate understanding by those skilled in the art, this disclosure provides multiple embodiments to clearly illustrate the technical solutions of the embodiments of this disclosure. Of course, those skilled in the art will understand that the multiple embodiments provided in this disclosure can be executed individually, or in combination with the methods of other embodiments in this disclosure, or individually or in combination with some methods in other related technologies; this disclosure does not limit these aspects.

[0150] Network scheduling of data streams is dynamic. In some cases, even if some data streams belong to low-priority logical channels, if the data packets have not been scheduled for a long time, a Business Request (BSR) needs to be sent to notify the network as soon as possible to meet the demand for multiple data streams in XR services. However, according to the existing mechanism, a BSR can only be sent when data arrives on a high-priority logical channel, which cannot meet the needs of emergency scheduling.

[0151] Therefore, how to schedule data with urgent scheduling needs, meet communication service requirements, and reduce data transmission errors such as joint decoding failures is an urgent problem to be solved.

[0152] like Figure 2 As shown, this embodiment of the disclosure provides a cache status report reporting method, executed by the UE, including:

[0153] Step 201: For uplink data with urgent scheduling needs, report BSR.

[0154] In one possible implementation, uplink data with urgent scheduling needs may include one of the following: uplink data with priority scheduling needs, or uplink data with higher scheduling needs.

[0155] Data with urgent scheduling needs can also be uplink data that requires priority scheduling; it can also be uplink data that the network or terminal determines needs to be sent in a timely manner.

[0156] Data requiring urgent dispatch can also be determined based on the specific business characteristics of the data. For example, the importance of uplink data can be used to determine whether it requires urgent dispatch. If I-frame data is more important than P-frame data, then I-frame data can be determined to have an urgent dispatch requirement.

[0157] In one possible implementation, uplink data with urgent scheduling needs can be uplink data whose time interval from the latest transmission deadline is less than a predetermined duration threshold.

[0158] For example, uplink data with urgent scheduling needs can be one of multiple data streams that are jointly decoded. Since multiple data streams need to be jointly decoded, decoding will fail if one of the data streams does not arrive before the scheduled decoding time.

[0159] In one possible implementation, uplink data with urgent scheduling needs can be determined by at least one of the following:

[0160] Communication protocol specifications;

[0161] The UE and the network side agree that the network side includes: access network equipment such as base stations, and / or core network equipment.

[0162] In related technologies, a BSR can only be sent if data arrives on a logical channel with a high priority level. Therefore, if the logical channel for uplink data with urgent scheduling needs does not have a high priority level, it cannot send a BSR, and thus the needs of uplink data with urgent scheduling needs cannot be met.

[0163] Here, a Buffer Status Report (BSR) can be reported for uplink data with urgent scheduling needs. This includes: when uplink data with urgent scheduling needs arrives on a logical channel, the UE can send a BSR to the base station. Here, the logical channel can have high priority or no priority.

[0164] In one possible implementation, BSR includes: regular BSR, padding BSR, and retransmission BSR.

[0165] In this way, reporting a BSR to uplink data with urgent scheduling needs can enable timely scheduling of uplink data with urgent scheduling needs, meet communication service requirements, reduce data transmission errors such as joint decoding failures, and improve communication reliability.

[0166] In one embodiment, the uplink data includes: extended reality (XR) service launch data.

[0167] XR service data typically consists of multiple data streams (QoS flows), resulting in a very large data volume. XR service streams need to meet certain latency requirements during transmission, especially since some data streams need to arrive at the server for decoding within a predetermined timeframe. Delay in any one of these data streams can cause the joint decoding of multiple data streams to fail. Therefore, the UE can send a BSR (Browser Request Scheduler) for uplink XR service data with urgent scheduling needs. This enables timely scheduling, meets the requirements of XR services, and reduces data transmission errors such as joint decoding failures.

[0168] In one embodiment, the uplink data with urgent scheduling requirements includes: the uplink data with a remaining packet delay budget less than a delay threshold.

[0169] Uplink data can have a packet delay budget, meaning that transmission within the packet delay budget can meet the uplink data transmission time requirements. The remaining packet delay budget can be the time difference between the current time and the end time of the packet delay budget. The remaining packet delay budget is the remaining time for uplink data to be correctly transmitted and / or decoded.

[0170] When the remaining data packet delay budget for uplink data is less than the delay threshold, the UE can send a BSR for the uplink data to achieve timely scheduling and meet the needs of data services.

[0171] For example, the remaining packet delay budget (the time left until exceeding the PDB) is less than a certain delay threshold (e.g., determining that the remaining packet delay budget for the packet is less than 10ms; the delay threshold can be agreed upon by the protocol or obtained from network notification. The configuration granularity of PDB (packet delay budget) can be for a single packet or for a set of packets).

[0172] The terminal can predict which data packets have nearly exhausted their PDB and have not yet been scheduled out, thus requiring priority scheduling. Data with higher scheduling urgency can be scheduled based on packet statistics or packet set statistics.

[0173] In one embodiment, the granularity of the latency threshold configuration includes one of the following:

[0174] UE granularity;

[0175] Logical channel granularity;

[0176] Logical channel group granularity.

[0177] In one possible implementation, the delay threshold can be agreed upon by the communication protocol or indicated to the UE by network-side equipment such as the base station.

[0178] The UE-level latency threshold can refer to all uplink data of the UE, and this latency threshold can be used to determine whether uplink data has an urgent scheduling requirement.

[0179] The delay threshold at the logical channel granularity can refer to the uplink data transmitted within that logical channel. This delay threshold can be used to determine whether the uplink data has an urgent scheduling requirement.

[0180] The delay threshold at the logical channel group level can be used to determine whether uplink data transmitted within that logical channel group is uplink data with urgent scheduling requirements.

[0181] In one embodiment, the uplink data with urgent scheduling needs is at the data packet granularity.

[0182] or,

[0183] The uplink data with urgent scheduling needs is at the data packet set granularity.

[0184] Uplink data can be statistically analyzed based on individual packets or packet sets to determine whether it is uplink data with urgent scheduling needs. Statistical analysis based on individual packets or packet sets improves the flexibility of the analysis and meets the needs of different forms of uplink data transmission.

[0185] like Figure 3 As shown, this embodiment of the disclosure provides a cache status report reporting method, executed by the UE, including:

[0186] Step 301: Based on the first indication information obtained from the non-access layer or application layer, determine that the uplink data has an urgent scheduling requirement.

[0187] In one possible implementation, the uplink data with urgent scheduling needs is indicated by the first indication information. The first indication information can be sent to the UE by network devices such as the core network through the non-access stratum or the application layer.

[0188] For example, the first indication information indicates uplink data with urgent scheduling needs at the packet granularity or packet set granularity.

[0189] like Figure 4 As shown, this embodiment of the disclosure provides a cache status report reporting method, executed by the UE, including:

[0190] Step 401: According to the second indication information sent by the base station, report the BSR for the uplink data with urgent scheduling needs.

[0191] The base station notifies the UE to enable the reporting of the BSR for uplink data with urgent scheduling needs through the second indication information.

[0192] In one possible implementation, the second indication information can be carried in dedicated signaling such as RRC and / or DCI and sent to the UE.

[0193] In one embodiment, reporting the BSR for uplink data with urgent scheduling needs based on the second indication information sent by the base station includes one of the following:

[0194] According to the instructions of the second instruction information, the BSR is reported for the uplink data of the UE that has an urgent scheduling requirement;

[0195] According to the instructions of the second instruction information, the BSR is reported for the uplink data that has an urgent scheduling requirement for the predetermined logical channel;

[0196] According to the instructions of the second instruction information, the BSR is reported for the uplink data that has an urgent scheduling requirement for the predetermined logical channel group.

[0197] The second instruction information can be sent to the UE for uplink data with urgent scheduling needs. This instruction can be at the UE level, the logical channel level, or the logical channel group level.

[0198] Specifically, when the second indication information corresponds to the UE granularity, the UE reports the BSR for the uplink data of the UE that has an urgent scheduling requirement.

[0199] For example, if the base station knows that the UE is a UE performing XR services, the second indication information corresponds to the UE granularity;

[0200] Specifically, when the second indication information corresponds to the logical channel group granularity, the UE reports the BSR for the uplink data with urgent scheduling requirements for the specified logical channel group.

[0201] For example, if the base station knows that the UE is a UE performing XR services, it will notify the UE that it will enable uplink data with urgent scheduling needs to report BSR for a specific LCG.

[0202] Specifically, when the second indication information corresponds to the logical channel granularity, the UE reports the BSR for the uplink data with urgent scheduling requirements for the specified logical channel.

[0203] In one possible implementation, the second indication information may simultaneously indicate enabling at least one of the following to report the BSR for uplink data with urgent scheduling needs: UE; logical channel; logical channel group.

[0204] For example, if the base station knows that the UE is a UE performing XR services, the second indication information notifies it to enable uplink data with urgent scheduling needs for a specific logical channel and report BSR.

[0205] In one embodiment, the second indication information includes: a latency threshold associated with the remaining packet latency budget of the uplink data.

[0206] In one possible implementation, the second indication information may explicitly instruct the UE to report the BSR for uplink data with urgent scheduling requirements for a specified logical channel group.

[0207] In one possible implementation, the second indication information may implicitly instruct the UE to report the BSR for uplink data with urgent scheduling requirements for a specified logical channel group.

[0208] In one possible implementation, the second indication information indicates a delay threshold associated with the remaining packet delay budget of the uplink data, implicitly instructing the UE to report the BSR for the uplink data with urgent scheduling requirements for a specified logical channel group.

[0209] The granularity of the delay threshold indicated by the second indication information may include one of the following: UE granularity; logical channel granularity; logical channel group granularity.

[0210] For example, if the network notifies a delay threshold for a logical channel, it means that the function of reporting BSRs for uplink data with urgent scheduling needs is enabled.

[0211] like Figure 5 As shown, this embodiment of the disclosure provides a cache status report reporting method, executed by the UE, including:

[0212] Step 501: Send auxiliary information to the base station, the auxiliary information being used to indicate that the UE can report the BSR for uplink data with urgent scheduling requirements.

[0213] In one possible implementation, the UE's auxiliary information includes whether the UE supports the ability to report the BSR for uplink data with urgent scheduling needs.

[0214] In one possible implementation, the UE's auxiliary information includes whether the UE expects to use the uplink data to report the BSR for urgent scheduling needs.

[0215] like Figure 6 As shown, this embodiment of the disclosure provides a cache status report reporting method, executed by the UE, including:

[0216] Step 601: Determine the logical channel corresponding to the uplink data with urgent scheduling needs as the highest priority, and report the BSR based on the priority of the logical channel.

[0217] Here, for the logical channel corresponding to the uplink data with urgent scheduling needs, this channel can be set to the highest priority. In this way, the UE can prioritize reporting the BSR (Browser Response Scheduler) for that logical channel based on its priority, enabling timely scheduling to meet communication service requirements and reduce data transmission errors such as joint decoding failures.

[0218] For example, the highest priority of a logical channel can be "1". If there is uplink data in the logical channel with urgent scheduling requirements, then the priority of the logical channel can be set to "1". This logical channel can have the same transmission priority as other channels with priority "1".

[0219] For example, when a regular BSR is triggered, the priority level of the logical channel of that type needs to be considered as the highest priority. (For instance, if LCH1 sends data and LCH2 receives new data, even if LCH2 has a lower logical channel priority, its priority is higher than LCH1 because of the arrival of urgent scheduling data. Therefore, a regular BSR can be triggered for LCH2). This ensures that logical channels with data requiring urgent scheduling can trigger BSR in a timely manner.

[0220] For example, when padding a BSR report, if a truncated BSR report is required, the priority level of the logical channel of this type must be considered as the highest logical channel priority. (For example, if LCH1 and LCH2 are sending data, even if LCH2 has a lower logical channel priority, its priority is higher than LCH1 because of the arrival of urgent scheduling data. Therefore, the truncated BSR will carry the LCG ID that triggered LCH2 because it can only carry one LCG.)

[0221] For example, when the BSR retransmission timer expires, the logical channel containing data with higher scheduling urgency needs should be set to the highest priority level; (for example, if LCH1 triggers BSR reporting, then when the retransmission timer expires, LCH1 will be considered the highest logical channel, even if LCH2 has a lower logical channel priority level, because urgent scheduling data has arrived, LCH2 will also be considered the highest priority level).

[0222] like Figure 7 As shown, this embodiment of the disclosure provides a cache status report reporting method, executed by the UE, including:

[0223] Step 701: In response to the uplink data indicating an urgent scheduling requirement for the logical channel, trigger the reporting of the BSR for the logical channel.

[0224] Here, the BSR of the logical channel can be triggered by uplink data with urgent scheduling requirements.

[0225] For example, when the logical channel arrives with uplink data that has an urgent scheduling requirement, the UE triggers the logical channel associated BSR to schedule the arriving uplink data with the urgent scheduling requirement.

[0226] For example, a BSR should be triggered if any of the following events occur in an active cell group:

[0227] - Uplink data belonging to a logical channel group (LCG) is available to the MAC entity; and:

[0228] 1. The uplink data belongs to a logical channel, and this logical channel has a higher priority than any logical channel in any logical channel group that has uplink data; or

[0229] 2. None of the logical channels belonging to the logical channel group contain any usable UL data; or

[0230] 3. Available data arriving on logical channels belonging to a logical channel group is considered to have an urgent scheduling requirement, i.e., it needs to be scheduled as soon as possible, or it has a stringent delay budget.

[0231] Here, BSR can be a regular BSR.

[0232] For example, the conventional BSR triggering conditions in related technologies have been modified by adding a triggering condition: the existence of an urgent scheduling data requirement in the logical channel triggers the event. In other words, the presence of data requiring urgent scheduling can trigger the event.

[0233] For example, the conventional BSR triggering conditions in related technologies have been modified by adding a triggering condition: the trigger is activated as soon as data with urgent scheduling data requirements appears in the logical channel. Compared to the previous embodiment, this method can avoid the frequent triggering of this type of BSR.

[0234] like Figure 8 As shown, this embodiment of the disclosure provides a cache status report reporting method, executed by the UE, including:

[0235] Step 801: In response to the uplink data that has an urgent scheduling requirement on at least one logical channel, trigger a first type BSR on the first logical channel, wherein the first type BSR has a higher priority than the second type BSR, and the first logical channel is the logical channel with the highest priority among the at least one logical channels.

[0236] The first type of BSR is different from the second type of BSR.

[0237] Here, the second type of BSR can be a BSR used in related technologies, which can be divided into several different priorities. The first type of BSR in this embodiment of the present disclosure has a higher priority than any BSR used in related technologies. For example, the second type of BSR can be a BSR used when the logical channel has the highest priority, while the first type of BSR in this embodiment of the present disclosure has a higher priority than that highest priority. The first type of BSR can be a BSR for logical channels of uplink data with urgent scheduling needs.

[0238] In one possible implementation, logical channels or logical channel groups with urgent scheduling needs can be prioritized, and a first-class BSR can be reported for logical channels or logical channel groups with high priority.

[0239] In one possible implementation, the first type of BSR has a higher priority than the second type of BSR.

[0240] The first type of BSR can be an XR-BSR or a priority BSR, which is used for priority transmission of logical channels or logical channel groups with data that have a high scheduling urgency requirement.

[0241] In one possible implementation, if the UE determines that there is data with a high scheduling urgency, it prioritizes the logical channels / groups to which this type of logical channel belongs, forming a priority BSR. If the authorization is limited, i.e., insufficient to transmit all the ordered LCGs, the priority BSR can transmit as many ordered LCGs as possible.

[0242] For example,

[0243] 1> If a delay threshold (PdbThres) for the remaining packet delay budget is configured, and the remaining packet delay budget for uplink data contained in any logical channel of an LCG is less than PdbThres, then,

[0244] 2> Increase the priority of the LCG, that is, give priority to LCGs that are close to the scheduling budget threshold;

[0245] 2> If the UL authorization cannot accommodate an SL-BSR MAC CE containing only the buffer states of all priority LCGs;

[0246] Report the XR-BSR, which contains the buffer status of as many priority LCGs as possible, which have active transmission data, while taking into account the number of bits in the uplink (UL) grant (i.e., the new BSR carries priority LCGs).

[0247] When prioritizing logical channels, the priority level of a BSR (Border Streaming Service) can be defined before the (Extended) BSR (Extended MAC CE) for XR-BSR type BSRs. For example, logical channels should be prioritized in the following order (highest priority first):

[0248] • MAC CE for C-RNTI, or data from UL-CCCH;

[0249] • MAC CE for (enhanced) BFR, or MAC CE for authorization verification of configuration, or MAC CE for authorization verification of multi-entry configuration;

[0250] • MAC CE used for Sidelink configuration authorization verification;

[0251] • MAC CE for LBT failure;

[0252] • MAC CE for scheduled advance reporting;

[0253] • MAC CE of XR-BSR;

[0254] • MAC CE of SL-BSR as preferred under Section 5.22.1.6;

[0255] • MAC CE for (extended) BSR, excluding BSR for padding;

[0256] • MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR;

[0257] • MAC CE used for locating and measuring gap activation / deactivation requests;

[0258] • The number of symbols required for protection, de MAC CE;

[0259] Case 6: MAC CE for Timed Requests;

[0260] • MAC CE for (extended) preemptive BSR;

[0261] • MAC CE for SL-BSR, except for SL-BSRs preferred under Section 5.22.1.6 and SL-BSRs for filling;

[0262] • MAC CE for IAB-MT recommended beam indication, or MAC CE for required IAB-MT PSD range, or MAC CE for required DL Tx power adjustment;

[0263] • Data from any logical channel, except data from UL-CCCH;

[0264] • MAC CE used for recommending bitrate queries;

[0265] • Includes MAC CE for BSR used for padding;

[0266] • Includes MAC CE for SL-BSR used for padding.

[0267] like Figure 9 As shown, this embodiment of the disclosure provides a cache status report reporting method, executed by the UE, including:

[0268] Step 901: In response to the uplink data indicating that the logical channel has an urgent scheduling requirement, determine that the logical channel has a first highest priority, and report the BSR based on the first highest priority, wherein the first highest priority is higher than the second highest priority.

[0269] Here, the second highest priority can be the highest priority of a logical channel in related technologies. Logical channels in related technologies can be divided into different priorities, and the second highest priority can be the highest priority among all priorities in related technologies. Meanwhile, in this embodiment, the first highest priority is higher than the highest priority in the related technologies (i.e., the second highest priority). Here, the logical channel of the uplink data with urgent scheduling needs can be determined to have the first highest priority. The UE can perform BSR based on the priority level.

[0270] Since the first highest priority is higher than the second highest priority, the logical channel of the uplink data with urgent scheduling needs has a higher priority to report the BSR, thereby realizing the timely scheduling of uplink data with urgent scheduling needs and meeting the data transmission requirements.

[0271] For example, a superpriority (i.e., first highest priority) can be introduced for logical channels of uplink data with urgent scheduling needs, which is higher than the highest priority (i.e., the second highest priority). The UE determines the logical channel of the uplink data with urgent scheduling needs to be at a higher priority level than the higher-level logical channel priority.

[0272] For example, during a regular BSR trigger, if data with a high scheduling urgency arrives on a certain logical channel, the logical channel carrying this type of data has a higher priority than any logical channel in any other LCG; therefore, a regular BSR will be triggered for the LCG corresponding to that logical channel. Thus, if data with a high scheduling urgency arrives on a certain logical channel, a regular BSR can be triggered.

[0273] For example, when a Padding BSR needs to be truncated before reporting, the UE determines that if there is data with high scheduling urgency, the Short Truncated BSR should carry the LCG ID for that logical channel (because that logical channel has super high priority at this time). For a Long Truncated BSR, since it can carry multiple LCG information, the LCG ID of the logical channel with high scheduling urgency can be placed at the beginning. Thus, for a certain logical channel, if data with high scheduling urgency arrives but the authorization is insufficient to report a truncated BSR, priority reporting of the LCG corresponding to that logical channel can be triggered.

[0274] For example, when the BSR retransmission timer expires, the UE will prioritize transmitting BSR retransmissions triggered by data with higher scheduling urgency (because this logical channel has a super high priority level). For instance, if both LCH1 and LCG2 trigger BSR retransmission reports, LCH1 and LCG2 will be considered the highest logical channels. However, because LCH2 has a BSR retransmission triggered by urgent scheduling data, it will also prioritize reporting the BSR of the LCG carrying LCH2. Thus, for a certain logical channel, if there is a BSR retransmission of data with higher scheduling urgency, the LCG corresponding to that logical channel will be reported first.

[0275] like Figure 10 As shown, this embodiment of the disclosure provides a cache status report reporting method, executed by a base station, including:

[0276] Step 1001: Receive BSR, wherein the BSR is sent by the user equipment (UE) for uplink data with urgent scheduling requirements.

[0277] In one possible implementation, uplink data with urgent scheduling needs may include one of the following: uplink data with priority scheduling needs, or uplink data with higher scheduling needs.

[0278] Data with urgent scheduling needs can also be uplink data that requires priority scheduling; it can also be uplink data that the network or terminal determines needs to be sent in a timely manner.

[0279] Data requiring urgent dispatch can also be determined based on the specific business characteristics of the data. For example, the importance of uplink data can be used to determine whether it requires urgent dispatch. If I-frame data is more important than P-frame data, then I-frame data can be determined to have an urgent dispatch requirement.

[0280] In one possible implementation, uplink data with urgent scheduling needs can be uplink data whose time interval from the latest transmission deadline is less than a predetermined duration threshold.

[0281] For example, uplink data with urgent scheduling needs can be one of multiple data streams that are jointly decoded. Since multiple data streams need to be jointly decoded, decoding will fail if one of the data streams does not arrive before the scheduled decoding time.

[0282] In one possible implementation, uplink data with urgent scheduling needs can be determined by at least one of the following:

[0283] Communication protocol specifications;

[0284] The UE and the network side agree that the network side includes: access network equipment such as base stations, and / or core network equipment.

[0285] In related technologies, a BSR can only be sent if data arrives on a logical channel with a high priority level. Therefore, if the logical channel for uplink data with urgent scheduling needs does not have a high priority level, it cannot send a BSR, and thus the needs of uplink data with urgent scheduling needs cannot be met.

[0286] Here, a Buffer Status Report (BSR) can be reported for uplink data with urgent scheduling needs. This includes: when uplink data with urgent scheduling needs arrives on a logical channel, the UE can send a BSR to the base station. Here, the logical channel can have high priority or no priority.

[0287] In one possible implementation, BSR includes: regular BSR, padding BSR, and retransmission BSR.

[0288] In this way, reporting a BSR to uplink data with urgent scheduling needs can enable timely scheduling of uplink data with urgent scheduling needs, meet communication service requirements, reduce data transmission errors such as joint decoding failures, and improve communication reliability.

[0289] In one embodiment, the uplink data includes: extended reality (XR) service launch data.

[0290] XR service data typically consists of multiple data streams (QoS flows), resulting in a very large data volume. XR service streams need to meet certain latency requirements during transmission, especially since some data streams need to arrive at the server for decoding within a predetermined timeframe. Delay in any one of these data streams can cause the joint decoding of multiple data streams to fail. Therefore, the UE can send a BSR (Browser Request Scheduler) for uplink XR service data with urgent scheduling needs. This enables timely scheduling, meets the requirements of XR services, and reduces data transmission errors such as joint decoding failures.

[0291] In one embodiment, the uplink data with urgent scheduling requirements includes: the uplink data with a remaining packet delay budget less than a delay threshold.

[0292] Uplink data can have a packet delay budget, meaning that transmission within the packet delay budget can meet the uplink data transmission time requirements. The remaining packet delay budget can be the time difference between the current time and the end time of the packet delay budget. The remaining packet delay budget is the remaining time for uplink data to be correctly transmitted and / or decoded.

[0293] When the remaining data packet delay budget for uplink data is less than the delay threshold, the UE can send a BSR for the uplink data to achieve timely scheduling and meet the needs of data services.

[0294] For example, the remaining packet delay budget (the time left until exceeding the PDB) is less than a certain delay threshold (e.g., determining that the remaining packet delay budget for the packet is less than 10ms; the delay threshold can be agreed upon by the protocol or obtained from network notification. The configuration granularity of PDB (packet delay budget) can be for a single packet or for a set of packets).

[0295] The terminal can predict which data packets have nearly exhausted their PDB and have not yet been scheduled out, thus requiring priority scheduling. Data with higher scheduling urgency can be scheduled based on packet statistics or packet set statistics.

[0296] In one embodiment, the granularity of the latency threshold configuration includes one of the following:

[0297] UE granularity;

[0298] Logical channel granularity;

[0299] Logical channel group granularity.

[0300] In one possible implementation, the delay threshold can be agreed upon by the communication protocol or indicated to the UE by network-side equipment such as the base station.

[0301] The UE-level latency threshold can refer to all uplink data of the UE, and this latency threshold can be used to determine whether uplink data has an urgent scheduling requirement.

[0302] The delay threshold at the logical channel granularity can refer to the uplink data transmitted within that logical channel. This delay threshold can be used to determine whether the uplink data has an urgent scheduling requirement.

[0303] The delay threshold at the logical channel group level can be used to determine whether uplink data transmitted within that logical channel group is uplink data with urgent scheduling requirements.

[0304] In one embodiment, the uplink data with urgent scheduling needs is at the data packet granularity.

[0305] or,

[0306] The uplink data with urgent scheduling needs is at the data packet set granularity.

[0307] Uplink data can be statistically analyzed based on individual packets or packet sets to determine whether it is uplink data with urgent scheduling needs. Statistical analysis based on individual packets or packet sets improves the flexibility of the analysis and meets the needs of different forms of uplink data transmission.

[0308] like Figure 11 As shown, this embodiment of the disclosure provides a cache status report reporting method, executed by a base station, including:

[0309] Step 1101: Send a second indication information to the UE, wherein the second indication information is used to instruct the UE to report the BSR for the uplink data with urgent scheduling requirements.

[0310] The base station notifies the UE to enable the reporting of the BSR for uplink data with urgent scheduling needs through the second indication information.

[0311] In one possible implementation, the second indication information can be carried in dedicated signaling such as RRC and / or DCI and sent to the UE.

[0312] In one embodiment, the second indication information is used to indicate one of the following:

[0313] The BSR is reported for uplink data that the UE has an urgent scheduling requirement;

[0314] The uplink data with urgent scheduling requirements for the predetermined logical channel is reported to the BSR;

[0315] The uplink data with urgent scheduling requirements for a predetermined logical channel group is reported to the BSR.

[0316] The second instruction information can be sent to the UE for uplink data with urgent scheduling needs. This instruction can be at the UE level, the logical channel level, or the logical channel group level.

[0317] Specifically, when the second indication information corresponds to the UE granularity, the UE reports the BSR for the uplink data of the UE that has an urgent scheduling requirement.

[0318] For example, if the base station knows that the UE is a UE performing XR services, the second indication information corresponds to the UE granularity;

[0319] Specifically, when the second indication information corresponds to the logical channel group granularity, the UE reports the BSR for the uplink data with urgent scheduling requirements for the specified logical channel group.

[0320] For example, if the base station knows that the UE is a UE performing XR services, it will notify the UE that it will enable uplink data with urgent scheduling needs to report BSR for a specific LCG.

[0321] Specifically, when the second indication information corresponds to the logical channel granularity, the UE reports the BSR for the uplink data with urgent scheduling requirements for the specified logical channel.

[0322] In one possible implementation, the second indication information may simultaneously indicate enabling at least one of the following to report the BSR for uplink data with urgent scheduling needs: UE; logical channel; logical channel group.

[0323] For example, if the base station knows that the UE is a UE performing XR services, the second indication information notifies it to enable uplink data with urgent scheduling needs for a specific logical channel and report BSR.

[0324] In one embodiment, the second indication information includes: a latency threshold associated with the remaining packet latency budget of the uplink data.

[0325] In one possible implementation, the second indication information may explicitly instruct the UE to report the BSR for uplink data with urgent scheduling requirements for a specified logical channel group.

[0326] In one possible implementation, the second indication information may implicitly instruct the UE to report the BSR for uplink data with urgent scheduling requirements for a specified logical channel group.

[0327] In one possible implementation, the second indication information indicates a delay threshold associated with the remaining packet delay budget of the uplink data, implicitly instructing the UE to report the BSR for the uplink data with urgent scheduling requirements for a specified logical channel group.

[0328] The granularity of the delay threshold indicated by the second indication information may include one of the following: UE granularity; logical channel granularity; logical channel group granularity.

[0329] For example, if the network notifies a delay threshold for a logical channel, it means that the function of reporting BSRs for uplink data with urgent scheduling needs is enabled.

[0330] In one embodiment, sending the second indication information to the UE includes:

[0331] In response to receiving auxiliary information sent by the UE, the second indication information is sent to the UE, wherein the auxiliary information is used to indicate that the UE can report the BSR for uplink data with urgent scheduling needs.

[0332] In one possible implementation, the UE's auxiliary information includes whether the UE supports the ability to report the BSR for uplink data with urgent scheduling needs.

[0333] In one possible implementation, the UE's auxiliary information includes whether the UE expects to use the uplink data to report the BSR for urgent scheduling needs.

[0334] After the base station determines that the UE has the ability to report the BSR for uplink data with urgent scheduling needs and / or the UE expects to use the function of reporting the BSR for uplink data with urgent scheduling needs, it may send a second indication message to the UE.

[0335] In one embodiment, the BSR is a report made by the UE based on the priority of the logical channel corresponding to the uplink data with urgent scheduling needs, which is determined as the highest priority.

[0336] Here, for the logical channel corresponding to the uplink data with urgent scheduling needs, this channel can be set to the highest priority. In this way, the UE can prioritize reporting the BSR (Browser Response Scheduler) for that logical channel based on its priority, enabling timely scheduling to meet communication service requirements and reduce data transmission errors such as joint decoding failures.

[0337] For example, the highest priority of a logical channel can be "1". If there is uplink data in the logical channel with urgent scheduling requirements, then the priority of the logical channel can be set to "1". This logical channel can have the same transmission priority as other channels with priority "1".

[0338] For example, when a regular BSR is triggered, the priority level of the logical channel of that type needs to be considered as the highest priority. (For instance, if LCH1 sends data and LCH2 receives new data, even if LCH2 has a lower logical channel priority, its priority is higher than LCH1 because of the arrival of urgent scheduling data. Therefore, a regular BSR can be triggered for LCH2). This ensures that logical channels with data requiring urgent scheduling can trigger BSR in a timely manner.

[0339] For example, when padding a BSR report, if a truncated BSR report is required, the priority level of the logical channel of this type must be considered as the highest logical channel priority. (For example, if LCH1 and LCH2 are sending data, even if LCH2 has a lower logical channel priority, its priority is higher than LCH1 because of the arrival of urgent scheduling data. Therefore, the truncated BSR will carry the LCG ID that triggered LCH2 because it can only carry one LCG.)

[0340] For example, when the BSR retransmission timer expires, the logical channel containing data with higher scheduling urgency needs should be set to the highest priority level; (for example, if LCH1 triggers BSR reporting, then when the retransmission timer expires, LCH1 will be considered the highest logical channel, even if LCH2 has a lower logical channel priority level, because urgent scheduling data has arrived, LCH2 will also be considered the highest priority level).

[0341] In one embodiment, the BSR is triggered by the UE in response to uplink data indicating an urgent scheduling requirement on the logical channel.

[0342] Here, the BSR of the logical channel can be triggered by uplink data with urgent scheduling requirements.

[0343] For example, when the logical channel arrives with uplink data that has an urgent scheduling requirement, the UE triggers the logical channel associated BSR to schedule the arriving uplink data with the urgent scheduling requirement.

[0344] For example, a BSR should be triggered if any of the following events occur in an active cell group:

[0345] - Uplink data belonging to a logical channel group (LCG) is available to the MAC entity; and:

[0346] 1. The uplink data belongs to a logical channel, and this logical channel has a higher priority than any logical channel in any logical channel group that has uplink data; or

[0347] 2. None of the logical channels belonging to the logical channel group contain any usable UL data; or

[0348] 3. Available data arriving on logical channels belonging to a logical channel group is considered to have an urgent scheduling requirement, i.e., it needs to be scheduled as soon as possible, or it has a stringent delay budget.

[0349] Here, BSR can be a regular BSR.

[0350] For example, the conventional BSR triggering conditions in related technologies have been modified by adding a triggering condition: the existence of an urgent scheduling data requirement in the logical channel triggers the event. In other words, the presence of data requiring urgent scheduling can trigger the event.

[0351] For example, the conventional BSR triggering conditions in related technologies have been modified by adding a triggering condition: the trigger is activated as soon as data with urgent scheduling data requirements appears in the logical channel. Compared to the previous embodiment, this method can avoid the frequent triggering of this type of BSR.

[0352] In one embodiment, the reported BSR includes: a first type of BSR, which is associated with a first logical channel;

[0353] The first type of BSR is the uplink data that the UE responds to in at least one logical channel having an urgent scheduling requirement, and the first logical channel is the logical channel with the highest priority among the at least one logical channels, wherein the priority of the first type of BSR is higher than that of the second type of BSR.

[0354] The first type of BSR is different from the second type of BSR.

[0355] Here, the second type of BSR can be a BSR used in related technologies, which can be divided into several different priorities. The first type of BSR in this embodiment of the present disclosure has a higher priority than any BSR used in related technologies. For example, the second type of BSR can be a BSR used when the logical channel has the highest priority, while the first type of BSR in this embodiment of the present disclosure has a higher priority than that highest priority. The first type of BSR can be a BSR for logical channels of uplink data with urgent scheduling needs.

[0356] In one possible implementation, logical channels or logical channel groups with urgent scheduling needs can be prioritized, and a first-class BSR can be reported for logical channels or logical channel groups with high priority.

[0357] In one possible implementation, the first type of BSR has a higher priority than the second type of BSR.

[0358] The first type of BSR can be an XR-BSR or a priority BSR, which is used for priority transmission of logical channels or logical channel groups with data that have a high scheduling urgency requirement.

[0359] In one possible implementation, if the UE determines that there is data with a high scheduling urgency, it prioritizes the logical channels / groups to which this type of logical channel belongs, forming a priority BSR. If the authorization is limited, i.e., insufficient to transmit all the ordered LCGs, the priority BSR can transmit as many ordered LCGs as possible.

[0360] For example,

[0361] 1> If a delay threshold (PdbThres) for the remaining packet delay budget is configured, and the remaining packet delay budget for uplink data contained in any logical channel of an LCG is less than PdbThres, then,

[0362] 2> Increase the priority of the LCG, that is, give priority to LCGs that are close to the scheduling budget threshold;

[0363] 2> If the UL authorization cannot accommodate an SL-BSR MAC CE containing only the buffer states of all priority LCGs;

[0364] Report the XR-BSR, which contains the buffer status of as many priority LCGs as possible, which have active transmission data, while taking into account the number of bits in the uplink (UL) grant (i.e., the new BSR carries priority LCGs).

[0365] When prioritizing logical channels, the priority level of a BSR (Border Streaming Service) can be defined before the (Extended) BSR (Extended MAC CE) for XR-BSR type BSRs. For example, logical channels should be prioritized in the following order (highest priority first):

[0366] • MAC CE for C-RNTI, or data from UL-CCCH;

[0367] • MAC CE for (enhanced) BFR, or MAC CE for authorization verification of configuration, or MAC CE for authorization verification of multi-entry configuration;

[0368] • MAC CE used for Sidelink configuration authorization verification;

[0369] • MAC CE for LBT failure;

[0370] • MAC CE for scheduled advance reporting;

[0371] • MAC CE of XR-BSR;

[0372] • MAC CE of SL-BSR as preferred under Section 5.22.1.6;

[0373] • MAC CE for (extended) BSR, excluding BSR for padding;

[0374] • MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR;

[0375] • MAC CE used for locating and measuring gap activation / deactivation requests;

[0376] • The number of symbols required for protection, de MAC CE;

[0377] Case 6: MAC CE for Timed Requests;

[0378] • MAC CE for (extended) preemptive BSR;

[0379] • MAC CE for SL-BSR, except for SL-BSRs preferred under Section 5.22.1.6 and SL-BSRs for filling;

[0380] • MAC CE for IAB-MT recommended beam indication, or MAC CE for required IAB-MT PSD range, or MAC CE for required DL Tx power adjustment;

[0381] • Data from any logical channel, except data from UL-CCCH;

[0382] • MAC CE used for recommending bitrate queries;

[0383] • Includes MAC CE for BSR used for padding;

[0384] • Includes MAC CE for SL-BSR used for padding.

[0385] In one embodiment, the BSR is the UE responding to uplink data indicating that the logical channel has an urgent scheduling requirement, determining that the logical channel has a first highest priority, and reporting it based on the first highest priority, wherein the first highest priority is higher than the second highest priority.

[0386] Here, the second highest priority can be the highest priority of a logical channel in related technologies. Logical channels in related technologies can be divided into different priorities, and the second highest priority can be the highest priority among all priorities in related technologies. Meanwhile, in this embodiment, the first highest priority is higher than the highest priority in the related technologies (i.e., the second highest priority). Here, the logical channel of the uplink data with urgent scheduling needs can be determined to have the first highest priority. The UE can perform BSR based on the priority level.

[0387] Since the first highest priority is higher than the second highest priority, the logical channel of the uplink data with urgent scheduling needs has a higher priority to report the BSR, thereby realizing the timely scheduling of uplink data with urgent scheduling needs and meeting the data transmission requirements.

[0388] For example, a super priority, higher than the highest priority level, can be introduced for logical channels of uplink data with urgent scheduling needs. The UE will determine the logical channel of the uplink data with urgent scheduling needs to be at a higher priority level than the higher-level logical channel priority level;

[0389] For example, during a regular BSR trigger, if data with a high scheduling urgency arrives on a certain logical channel, the logical channel carrying this type of data has a higher priority than any logical channel in any other LCG; therefore, a regular BSR will be triggered for the LCG corresponding to that logical channel. Thus, if data with a high scheduling urgency arrives on a certain logical channel, a regular BSR can be triggered.

[0390] For example, when a Padding BSR needs to be truncated before reporting, the UE determines that if there is data with high scheduling urgency, the Short Truncated BSR should carry the LCG ID for that logical channel (because that logical channel has super high priority at this time). For a Long Truncated BSR, since it can carry multiple LCG information, the LCG ID of the logical channel with high scheduling urgency can be placed at the beginning. Thus, for a certain logical channel, if data with high scheduling urgency arrives but the authorization is insufficient to report a truncated BSR, priority reporting of the LCG corresponding to that logical channel can be triggered.

[0391] For example, when the BSR retransmission timer expires, the UE will prioritize transmitting BSR retransmissions triggered by data with higher scheduling urgency (because this logical channel has a super high priority level). For instance, if both LCH1 and LCG2 trigger BSR retransmission reports, LCH1 and LCG2 will be considered the highest logical channels. However, because LCH2 has a BSR retransmission triggered by urgent scheduling data, it will also prioritize reporting the BSR of the LCG carrying LCH2. Thus, for a certain logical channel, if there is a BSR retransmission of data with higher scheduling urgency, the LCG corresponding to that logical channel will be reported first.

[0392] To further explain any embodiment of this disclosure, a specific embodiment is provided below.

[0393] 1. A scheme for reporting BSR for specific data.

[0394] a) Specific data refers to data (uplink data) in XR services that have a high urgent scheduling need (i.e., have an urgent scheduling need).

[0395] Data with urgent scheduling needs can also be data that needs to be prioritized for scheduling; it can also be data that the network or terminal deems necessary to send in a timely manner.

[0396] Data requiring urgent dispatch can also be extended to other business characteristics of specific data, such as importance. For example, I-frame data is more important than P-frame data and needs to be sent promptly.

[0397] 2. Data that the UE (e.g., the terminal) determines has a high scheduling urgency requirement can be based on the following mechanism:

[0398] a) As an example: The access layer obtains specific data from the non-access layer or from the application layer that is data with high scheduling urgency in XR services.

[0399] b) As an example: The access layer obtains specific data from the non-access layer or from the application layer that is important data in the XR service and needs to be transmitted with priority.

[0400] c) As an example: The access layer obtains specific data from the non-access layer or from the application layer. For data with high scheduling urgency in XR services, it can be based on implicit indications from the non-access layer or from the application layer, such as I-frame data.

[0401] d) As an example: The remaining packet delay budget (the time left until exceeding the PDB) is less than a certain threshold (e.g., determining that the remaining packet delay budget of the packet is less than 10ms; this threshold can be agreed upon by the protocol or obtained from network notification. The configuration granularity of PDB (packet delay budget) can be for a single packet or for a set of packets).

[0402] That is, the terminal can predict which data packets have nearly exhausted their PDB and have not yet been scheduled out, and therefore need to be prioritized for scheduling.

[0403] e) Data with high scheduling urgency can be statistically analyzed based on packets or packets sets.

[0404] 3. Method 1: The UE first identifies specific data (such as data with urgent scheduling needs) and temporarily sets the logical channel containing the specific data to the highest priority level.

[0405] a) As an example: When triggering a regular BSR, the priority level of the logical channel of this type needs to be considered as the highest logical channel priority level; (for example, if LCH1 has uplink data transmission and LCH2 has new data arrival, even if LCH2 has a lower logical channel priority level, because LCH2 has emergency scheduling data arrival, LCH2's logical channel priority level is higher than LCH1. A regular BSR will also be triggered for LCH2).

[0406] The advantage of doing this is that logical channels with urgent scheduling needs will trigger BSR in a timely manner.

[0407] b) As an example: When padding a BSR, if a truncated BSR needs to be reported, the priority level of the logical channel of this type should be taken into account as the highest logical channel priority level; (for example, if LCH1 has data transmission and LCH2 has data transmission, even if the logical channel priority level of LCH2 is lower, its priority level is higher than that of LCH2 because urgent scheduling data has arrived. Therefore, since the truncated BSR can only carry one LCG, it will carry the LCG of LCH2).

[0408] c) As an example: When the BSR retransmission timer expires, the logical channel containing data with higher scheduling urgency needs should be set to the highest priority level; (for example, if LCH1 triggers BSR reporting, then when the retransmission timer expires, LCH1 will be considered the highest logical channel, even if the logical channel priority of LCH2 is lower, because urgent scheduling data has arrived, LCH2 will also be considered the highest priority level).

[0409] 4. Method 2: The UE sends data with high scheduling urgency to trigger a regular BSR.

[0410] a) As an example: the existing conventional BSR triggering conditions were modified, and an additional triggering condition was added: there is an urgent scheduling data requirement in the logical channel.

[0411] For example, a BSR should be triggered if any of the following events occur in an active cell group:

[0412] - Uplink data belonging to a logical channel group (LCG) is available to the MAC entity; and:

[0413] 1) The uplink data belongs to a logical channel, and this logical channel has a higher priority than any logical channel in any logical channel group that has uplink data; or

[0414] 2) None of the logical channels belonging to the logical channel group contain any usable UL data; or

[0415] 3) Available data arriving on logical channels belonging to logical channel groups becomes data with urgent scheduling needs (i.e., data needs to be scheduled as soon as possible or has a stringent delay budget).

[0416] Here, BSR can be a regular BSR.

[0417] That is (A BSR shall be triggered if any of the following events occur for activated cell group:

[0418] -UL data,for a logical channel which belongs to an LCG,becomesavailable to the MAC entity;and either

[0419] -this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG; or

[0420] -none of the logical channels which belong to an LCG contains anyavailable UL data; or

[0421] -UL data,for a logical channel which belongs to an LCG,becomes available data which has to be scheduled as soon as possible or has stringentdelay buget;

[0422] in which case the BSR is referred below to as'Regular BSR';)

[0423] As an example, the conventional BSR triggering conditions in related technologies were modified by adding a triggering condition: the existence of an urgent scheduling data requirement in the logical channel triggers the event. In other words, the presence of data requiring urgent scheduling triggers the event.

[0424] As an example, the conventional BSR triggering conditions in related technologies are modified by adding a triggering condition: the system triggers when data with urgent scheduling data requirements appears in the logical channel from none. Compared to the previous example, this method can avoid the frequent triggering of this type of BSR.

[0425] 5. Method 3: Define a new BSR, such as XR-BSR or priority BSR, which is used for priority transmission of logical channels or logical channel groups with data that have high scheduling urgency requirements.

[0426] As an example: If the UE determines that there is data with a high scheduling urgency, it will prioritize the logical channels / logical channel groups to which this type of logical channel belongs, forming a priority BSR. If the authorization is limited, i.e., insufficient to transmit all the prioritized LCGs, the priority BSR can transmit as many prioritized LCGs as possible.

[0427] Example 1:

[0428] An example of prioritizing XR transmission in method 3 is as follows:

[0429] 1> If a remaining packet delay budget threshold (delay threshold) is configured, and the remaining packet delay budget for uplink data contained in any logical channel of an LCG is less than the remaining packet delay budget threshold (i.e., the packet delay budget will be exhausted), then,

[0430] 2> Increase the priority of the LCG, that is, give priority to LCGs that are close to the scheduling budget threshold;

[0431] 2> If the UL authorization cannot accommodate an SL-BSR MAC CE containing only the buffer states of all priority LCGs;

[0432] Report the XR-BSR or a preferred BSR. The XR-BSR contains the buffer status of as many preferred LCGs as possible, which have available data for transmission, while also taking into account the number of bits in the uplink (UL) grant (i.e., the new BSR carries preferred LCGs). That is (

[0433] 1>if PdbThres is configured and the value of the logical channels that belong to any LCG and contain UL data whose remaining delay budget is less than PdbThres according to clause 5.4.5:

[0434] 2> Prioritize the LCG(s)

[0435] 2>if the UL grant cannot accommodate an SL-BSR MAC CE containingbuffer status only for all prioritized LCG:

[0436] report XR-BSR containing buffer status for as many prioritized LCGshaving data available for transmission as possible,taking the number of bitsin the UL grant into consideration.)

[0437] Example 2: When performing logical channel priority processing for a priority BSR: For XR-BSR type BSRs or priority BSRs, the priority level can be defined by MAC CE before (Extended) BSRs. An example is given below.

[0438] For example, logical channels should be prioritized in the following order (highest priority first):

[0439] • MAC CE for C-RNTI, or data from UL-CCCH;

[0440] • MAC CE for (enhanced) BFR, or MAC CE for authorization verification of configuration, or MAC CE for authorization verification of multi-entry configuration;

[0441] • MAC CE used for Sidelink configuration authorization verification;

[0442] • MAC CE for LBT failure;

[0443] • MAC CE for scheduled advance reporting;

[0444] • MAC CE of XR-BSR or priority BSR;

[0445] • MAC CE of SL-BSR as preferred under Section 5.22.1.6;

[0446] • MAC CE for (extended) BSR, excluding BSR for padding;

[0447] • MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR;

[0448] • MAC CE used for locating and measuring gap activation / deactivation requests;

[0449] • The number of symbols required for protection, de MAC CE;

[0450] Case 6: MAC CE for Timed Requests;

[0451] • MAC CE for (extended) preemptive BSR;

[0452] • MAC CE for SL-BSR, except for SL-BSRs preferred under Section 5.22.1.6 and SL-BSRs for filling;

[0453] • MAC CE for IAB-MT recommended beam indication, or MAC CE for required IAB-MT PSD range, or MAC CE for required DL Tx power adjustment;

[0454] • Data from any logical channel, except data from UL-CCCH;

[0455] • MAC CE used for recommending bitrate queries;

[0456] • Includes MAC CE for BSR used for padding;

[0457] • Includes MAC CE for SL-BSR used for padding.

[0458] 6. Method 4: Introduce a higher priority level than the highest priority (i.e., the second highest priority), namely super priority (i.e., the first highest priority); in this case, the UE will determine the logical channel of data with higher scheduling urgent needs to be at a higher priority level than the higher-level logical channel.

[0459] a) As an example: When a regular BSR is triggered, if data with a high scheduling urgency requirement arrives for a certain logical channel, the logical channel of this type of data has a higher priority than any logical channel of any other LCG; then a regular BSR will be triggered for the LCG corresponding to that logical channel.

[0460] The above embodiments can ensure that for a certain logical channel, if data with a high scheduling urgency arrives, a regular BSR can be triggered.

[0461] b) As an example: When Padding BSR needs to be truncated, the UE decides that if there is data with high scheduling urgency, the Short Truncated BSR should carry the LCG ID for that logical channel (because the logical channel is super high priority at this time); if it is a Long Truncated BSR, since it can carry multiple LCG information, the LCG ID of the logical channel with high scheduling urgency can be placed at the beginning.

[0462] The above embodiments can ensure that for a certain logical channel, if data with high scheduling urgency arrives but the authorization is insufficient and a BSR needs to be reported, priority reporting of the corresponding LCG can be triggered.

[0463] c) As an example: When the BSR retransmission timer expires, the UE will prioritize the transmission of BSR retransmissions triggered by data with higher scheduling urgent needs (because the logical channel is at super high priority level at this time); for example: both LCH1 and LCG2 have triggered BSR retransmission reports. At this time, LCH1 and LCG2 will be considered the highest logical channels, but because LCH2 has BSR retransmissions triggered by urgent scheduling data, the BSR carrying LCGs transmitting LCH2 will also be reported first.

[0464] The above embodiments can ensure that for a certain logical channel, if there is a BSR retransmission of data with high scheduling urgency, the LCG corresponding to that logical channel will be reported first.

[0465] 7. The base station notifies the UE to enable this feature via dedicated signaling (second indication information);

[0466] a) Method A: Its notification granularity can be per UE granularity;

[0467] As one example, if the base station knows that the UE is a UE performing XR services, it will enable this function;

[0468] b) Method B: Its notification granularity can be perLCG granularity;

[0469] As one example, if the base station knows that the UE is a UE performing XR services, it notifies the UE that it will enable the function for a specific LCG.

[0470] c) Method C: Its notification granularity can be per logical channel granularity;

[0471] As one example, if the base station knows that the UE is a UE performing XR services, it notifies the UE to enable the function for a specific logical channel;

[0472] d) The notification method that enables this function is either a visible or implicit notification.

[0473] As one example: if the network notifies a delay budget threshold for a logical channel, it means that the function is enabled;

[0474] 8. The base station can notify the UE to use this function based on the UE's auxiliary information via dedicated signaling;

[0475] The UE's auxiliary information includes whether the UE supports the ability to use this function;

[0476] The UE's auxiliary information includes whether the UE expects to use the function (for example, if the UE estimates that the data has a high scheduling urgency, it will report auxiliary information to indicate that it expects to use it).

[0477] like Figure 12 As shown, this embodiment of the present disclosure provides a cache status report reporting device 100, which is configured in the UE and includes:

[0478] The transceiver module 110 is configured to report a buffer status report (BSR) for uplink data with urgent scheduling needs.

[0479] In one embodiment, the transceiver module 110 is specifically configured as follows:

[0480] The logical channel corresponding to the uplink data with urgent scheduling needs is determined as the highest priority, and the BSR is reported based on the priority of the logical channel.

[0481] In one embodiment, the transceiver module 110 is specifically configured as follows:

[0482] In response to uplink data indicating an urgent scheduling requirement on the logical channel, the BSR of the logical channel is triggered for reporting.

[0483] In one embodiment, the transceiver module 110 is specifically configured as follows:

[0484] In response to uplink data indicating an urgent scheduling requirement on at least one logical channel, a first type of BSR is triggered on the first logical channel, wherein the first type of BSR has a higher priority than the second type of BSR, and the first logical channel is the logical channel with the highest priority among the at least one logical channels.

[0485] In one embodiment, the transceiver module 110 is specifically configured as follows:

[0486] In response to uplink data indicating an urgent scheduling requirement for a logical channel, the logical channel is determined to have a first highest priority, and the BSR is reported based on the first highest priority, wherein the first highest priority is higher than the second highest priority.

[0487] In one embodiment, the uplink data includes: extended reality (XR) service launch data.

[0488] In one embodiment, the uplink data with urgent scheduling requirements includes: the uplink data with a remaining packet delay budget less than a delay threshold.

[0489] In one embodiment, the granularity of the latency threshold configuration includes one of the following:

[0490] UE granularity;

[0491] Logical channel granularity;

[0492] Logical channel group granularity.

[0493] In one embodiment, the uplink data with urgent scheduling needs is at the data packet granularity.

[0494] or,

[0495] The uplink data with urgent scheduling needs is at the data packet set granularity.

[0496] In one embodiment, the apparatus further includes:

[0497] The processing module 120 is configured to determine, based on first indication information obtained from the non-access layer or the application layer, that the uplink data has an urgent scheduling requirement.

[0498] In one embodiment, the transceiver module is specifically configured as follows:

[0499] According to the second indication information sent by the base station, the BSR is reported for the uplink data with urgent scheduling needs.

[0500] In one embodiment, the second indication information includes: a latency threshold associated with the remaining packet latency budget of the uplink data.

[0501] In one embodiment, the transceiver module 110 is specifically configured as follows:

[0502] According to the instructions of the second instruction information, the BSR is reported for the uplink data of the UE that has an urgent scheduling requirement;

[0503] According to the instructions of the second instruction information, the BSR is reported for the uplink data that has an urgent scheduling requirement for the predetermined logical channel;

[0504] According to the instructions of the second instruction information, the BSR is reported for the uplink data that has an urgent scheduling requirement for the predetermined logical channel group.

[0505] In one embodiment, the transceiver module 110 is further configured to:

[0506] The UE sends auxiliary information to the base station, the auxiliary information being used to indicate that the UE can report the BSR for uplink data with urgent scheduling needs.

[0507] like Figure 13 As shown, this embodiment of the disclosure provides a cache status report reporting device 200, which is disposed in a base station and includes:

[0508] The transceiver module 210 is configured to receive a buffer status report (BSR), wherein the BSR is sent by the user equipment (UE) for uplink data with urgent scheduling requirements.

[0509] In one embodiment, the BSR is a report made by the UE based on the priority of the logical channel corresponding to the uplink data with urgent scheduling needs, which is determined as the highest priority.

[0510] In one embodiment, the BSR is triggered by the UE in response to uplink data indicating an urgent scheduling requirement on the logical channel.

[0511] In one embodiment, the reported BSR includes: a first type of BSR, which is associated with a first logical channel;

[0512] The first type of BSR is the uplink data that the UE responds to in at least one logical channel having an urgent scheduling requirement, and the first logical channel is the logical channel with the highest priority among the at least one logical channels, wherein the priority of the first type of BSR is higher than that of the second type of BSR.

[0513] In one embodiment, the BSR is the UE responding to uplink data indicating that the logical channel has an urgent scheduling requirement, determining that the logical channel has a first highest priority, and reporting it based on the first highest priority, wherein the first highest priority is higher than the second highest priority.

[0514] In one embodiment, the uplink data includes: extended reality (XR) service launch data.

[0515] In one embodiment, the uplink data with urgent scheduling requirements includes: the uplink data with a remaining packet delay budget less than a delay threshold.

[0516] In one embodiment, the granularity of the latency threshold configuration includes one of the following:

[0517] UE granularity;

[0518] Logical channel granularity;

[0519] Logical channel group granularity.

[0520] In one embodiment, the uplink data with urgent scheduling needs is at the data packet granularity.

[0521] or,

[0522] The uplink data with urgent scheduling needs is at the data packet set granularity.

[0523] In one embodiment, the transceiver module 210 is further configured to:

[0524] Send a second indication message to the UE, wherein the second indication message is used to instruct the UE to report the BSR for the uplink data with urgent scheduling requirements.

[0525] In one embodiment, the second indication information includes: a latency threshold associated with the remaining packet latency budget of the uplink data.

[0526] In one embodiment, the second indication information is used to indicate one of the following:

[0527] The BSR is reported for uplink data that the UE has an urgent scheduling requirement;

[0528] The uplink data with urgent scheduling requirements for the predetermined logical channel is reported to the BSR;

[0529] The uplink data with urgent scheduling requirements for a predetermined logical channel group is reported to the BSR.

[0530] In one embodiment, the transceiver module 210 is specifically configured as follows:

[0531] In response to receiving auxiliary information sent by the UE, the second indication information is sent to the UE, wherein the auxiliary information is used to indicate that the UE can report the BSR for uplink data with urgent scheduling needs.

[0532] This disclosure provides a communication device, including:

[0533] processor;

[0534] Memory used to store processor-executable instructions;

[0535] The processor is configured to implement the cache status reporting method of any embodiment of this disclosure when running executable instructions.

[0536] In one embodiment, the communication equipment may include, but is not limited to, at least one of: a UE and a network device. The network device may include core network or access network equipment, etc. The access network equipment may include a base station; the core network may include an AMF (Active Network Filter) and an SMF (Small and Medium Network Filter).

[0537] The processor may include various types of storage media, which are non-transitory computer storage media that can continue to store information after the user equipment loses power.

[0538] The processor can connect to memory via a bus or similar means to read executable programs stored in memory, for example... Figures 2 to 11 At least one of the methods shown.

[0539] This disclosure also provides a computer storage medium storing a computer-executable program. When the executable program is executed by a processor, it implements the cache status report reporting method of any embodiment of this disclosure. For example, such as... Figures 2 to 11 At least one of the methods shown.

[0540] Regarding the apparatus or storage medium in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0541] Figure 14 This is a block diagram illustrating a user equipment 3000 according to an exemplary embodiment. For example, the user equipment 3000 may be a mobile phone, computer, digital broadcast user equipment, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0542] Reference Figure 14 User equipment 3000 may include one or more of the following components: processing component 3002, memory 3004, power supply component 3006, multimedia component 3008, audio component 3010, input / output (I / O) interface 3012, sensor component 3014, and communication component 3016.

[0543] Processing component 3002 typically controls the overall operation of user equipment 3000, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 3002 may include one or more processors 3020 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 3002 may include one or more modules to facilitate interaction between processing component 3002 and other components. For example, processing component 3002 may include a multimedia module to facilitate interaction between multimedia component 3008 and processing component 3002.

[0544] Memory 3004 is configured to store various types of data to support the operation of user equipment 3000. Examples of this data include instructions for any application or method operating on user equipment 3000, contact data, phonebook data, messages, pictures, videos, etc. Memory 3004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0545] Power supply component 3006 provides power to various components of user equipment 3000. Power supply component 3006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to user equipment 3000.

[0546] Multimedia component 3008 includes a screen that provides an output interface between the user equipment 3000 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 3008 includes a front-facing camera and / or a rear-facing camera. When the user equipment 3000 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0547] Audio component 3010 is configured to output and / or input audio signals. For example, audio component 3010 includes a microphone (MIC) configured to receive external audio signals when user equipment 3000 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 3004 or transmitted via communication component 3016. In some embodiments, audio component 3010 also includes a speaker for outputting audio signals.

[0548] I / O interface 3012 provides an interface between processing component 3002 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0549] Sensor assembly 3014 includes one or more sensors for providing status assessments of various aspects of user equipment 3000. For example, sensor assembly 3014 can detect the on / off state of user equipment 3000, the relative positioning of components, such as the display and keypad of user equipment 3000, changes in position of user equipment 3000 or a component of user equipment 3000, the presence or absence of contact between the user and user equipment 3000, the orientation or acceleration / deceleration of user equipment 3000, and temperature changes of user equipment 3000. Sensor assembly 3014 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 3014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 3014 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0550] Communication component 3016 is configured to facilitate wired or wireless communication between user equipment 3000 and other devices. User equipment 3000 can access wireless networks based on communication standards, such as WiFi, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 3016 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 3016 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0551] In an exemplary embodiment, the user equipment 3000 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0552] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 3004 including instructions, which can be executed by a processor 3020 of a user equipment 3000 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0553] Figure 15 As shown, one embodiment of this disclosure illustrates the structure of a base station. For example, base station 900 can be provided as a network-side device. (Refer to...) Figure 15 The base station 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by a memory 932 for storing instructions executable by the processing component 922, such as application programs. The application programs stored in the memory 932 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 922 is configured to execute instructions to perform any of the methods described above applied to the base station.

[0554] Base station 900 may also include a power supply component 926 configured to perform power management of base station 900, a wired or wireless network interface 950 configured to connect base station 900 to a network, and an input / output (I / O) interface 958. Base station 900 can operate on an operating system stored in memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.

[0555] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.

[0556] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for reporting a buffer status report, wherein, Executed by the user equipment (UE), including: For uplink data with urgent scheduling needs, a Category I Cache Status Report (BSR) is submitted. In the logical channel priority processing, the priority level of the first type of BSR is after the priority level of the Media Access Control Layer Control Element (MAC CE) used for advance timing reporting, and before the priority side link SL-BSR MAC CE.

2. The method of claim 1, wherein, The first type of BSR reported for uplink data with urgent scheduling needs includes: The logical channel corresponding to the uplink data with urgent scheduling needs is determined as the highest priority, and the first type of BSR is reported based on the priority of the logical channel.

3. The method according to claim 1, wherein, The first type of BSR reported for uplink data with urgent scheduling needs includes: In response to the uplink data indicating an urgent scheduling requirement on the logical channel, the first type of BSR is triggered to be reported on the logical channel.

4. The method according to claim 1, wherein, The first type of BSR reported for uplink data with urgent scheduling needs includes: In response to uplink data indicating an urgent scheduling requirement on at least one logical channel, a first type of BSR is triggered on the first logical channel, wherein the first type of BSR has a higher priority than the second type of BSR, and the first logical channel is the logical channel with the highest priority among the at least one logical channels.

5. The method according to claim 1, wherein, The first type of BSR reported for uplink data with urgent scheduling needs includes: In response to the uplink data indicating an urgent scheduling requirement for the logical channel, the logical channel is determined to have a first highest priority, and the first type of BSR is reported based on the first highest priority, wherein the first highest priority is higher than the second highest priority.

6. The method according to any one of claims 1 to 5, wherein, The uplink data includes: extended reality (XR) service uplink data.

7. The method according to claim 6, wherein, The uplink data with urgent scheduling requirements includes: uplink data with a remaining data packet delay budget less than a delay threshold; wherein, the remaining data packet delay budget is the time difference between the current time and the end time of the data packet delay budget.

8. The method according to claim 7, wherein, The configuration granularity of the latency threshold includes one of the following: UE granularity; Logical channel granularity; Logical channel group granularity.

9. The method according to claim 6, wherein, The uplink data with urgent scheduling needs is at the data packet granularity. or, The uplink data with urgent scheduling needs is at the data packet set granularity.

10. The method according to claim 7, wherein, The latency threshold is specified by the protocol or notified by the network device.

11. The method according to claim 6, wherein, The method further includes: Based on the first indication information obtained from the non-access layer or the application layer, it is determined that the uplink data has an urgent scheduling requirement.

12. The method according to any one of claims 1 to 5, wherein, The first type of BSR reported for uplink data with urgent scheduling needs includes: According to the second indication information sent by the base station, the first type of BSR is reported for the uplink data with urgent scheduling needs.

13. The method according to claim 12, wherein, The second indication information includes: the latency threshold associated with the remaining packet latency budget of the uplink data.

14. The method according to claim 12, wherein, The step of reporting the first type of BSR for uplink data with urgent scheduling needs based on the second indication information sent by the base station includes one of the following: According to the instructions of the second instruction information, for the uplink data of the UE that has an urgent scheduling requirement, the first type of BSR is reported; According to the instructions of the second instruction information, the first type of BSR is reported for the uplink data with urgent scheduling requirements for the predetermined logical channel; According to the instructions of the second instruction information, the first type of BSR is reported for the uplink data that has an urgent scheduling requirement for the predetermined logical channel group.

15. The method according to claim 12, wherein, The second indication information is carried in the Radio Resource Control (RRC) message or the Downlink Control Information (DCI).

16. The method according to any one of claims 1 to 5, wherein, The method further includes: Sending auxiliary information to the base station, the auxiliary information indicating one of the following: Does the UE support reporting the first type of BSR for uplink data with urgent scheduling needs? Does the UE expect to report the first type of BSR for uplink data with urgent scheduling needs? 17. A method for reporting cache status, wherein, Executed by the base station, including: Receive a first type of buffer status report (BSR), wherein the first type of BSR is sent by the user equipment (UE) for uplink data with urgent scheduling requirements; When the UE performs logical channel priority processing, the priority level of the first type of BSR is after the priority level of the Media Access Control Layer Control Element (MAC CE) used for advance timing reporting, and before the priority side link SL-BSR MACCE.

18. The method according to claim 17, wherein, The first type of BSR is generated when the UE determines the logical channel corresponding to the uplink data with urgent scheduling needs as the highest priority and reports it based on the priority of the logical channel.

19. The method of claim 17, wherein, The first type of BSR is triggered by the UE in response to uplink data that has an urgent scheduling requirement on the logical channel.

20. The method of claim 17, wherein, The first type of BSR is associated with the first logical channel; The first type of BSR is the uplink data that the UE responds to in at least one logical channel having an urgent scheduling requirement, and the first logical channel is the logical channel with the highest priority among the at least one logical channels, wherein the priority of the first type of BSR is higher than that of the second type of BSR.

21. The method according to claim 17, wherein, The first type of BSR is reported by the UE in response to uplink data that has an urgent scheduling requirement for the logical channel, determining that the logical channel has a first highest priority, and reporting it based on the first highest priority, wherein the first highest priority is higher than the second highest priority.

22. The method according to any one of claims 17 to 21, wherein, The uplink data includes: extended reality (XR) service uplink data.

23. The method according to claim 17, wherein, The uplink data with urgent scheduling requirements includes: uplink data with a remaining data packet delay budget less than a delay threshold; wherein, the remaining data packet delay budget is the time difference between the current time and the end time of the data packet delay budget.

24. The method according to claim 23, wherein, The configuration granularity of the latency threshold includes one of the following: UE granularity; Logical channel granularity; Logical channel group granularity.

25. The method according to claim 23, wherein, The uplink data with urgent scheduling needs is at the data packet granularity. or, The uplink data with urgent scheduling needs is at the data packet set granularity.

26. The method according to claim 23, wherein, The latency threshold is specified by the protocol or notified by the network device.

27. The method according to any one of claims 17 to 21, wherein, The method further includes: Send a second indication message to the UE, wherein the second indication message is used to instruct the UE to report the first type of BSR for the uplink data with urgent scheduling needs.

28. The method according to claim 27, wherein, The second indication information includes: the latency threshold associated with the remaining packet latency budget of the uplink data.

29. The method according to claim 27, wherein, The second indication information is used to indicate one of the following: For uplink data with urgent scheduling requirements of the UE, the first type of BSR is reported; The uplink data with urgent scheduling requirements for the predetermined logical channel is reported to the first type of BSR; The uplink data with urgent scheduling requirements for the predetermined logical channel group is reported to the first type of BSR.

30. The method of claim 27, wherein, The second indication information is carried in the Radio Resource Control (RRC) message or the Downlink Control Information (DCI).

31. The method according to claim 27, wherein, Sending the second indication information to the UE includes: In response to receiving the auxiliary information sent by the UE, the second indication information is sent to the UE. The auxiliary information is used to indicate one of the following: Does the UE support reporting the first type of BSR for uplink data with urgent scheduling needs? Does the UE expect to report the first type of BSR for uplink data with urgent scheduling needs? 32. A cache status report reporting device, wherein, Configured in the User Equipment (UE), including: The transceiver module is configured to report a Type I Buffer Status Report (BSR) for uplink data with urgent scheduling needs. In the logical channel priority processing, the priority level of the first type of BSR is after the priority level of the Media Access Control Layer Control Element (MAC CE) used for advance timing reporting, and before the priority side link SL-BSR MAC CE.

33. A cache status report reporting device, wherein, Configured in the base station, including: The transceiver module is configured to receive a first type of buffer status report (BSR), wherein the BSR is sent by the user equipment (UE) for uplink data with urgent scheduling requirements; When the UE performs logical channel priority processing, the priority level of the first type of BSR is after the priority level of the Media Access Control Layer Control Element (MAC CE) used for advance timing reporting, and before the priority side link SL-BSR MACCE.

34. A communication device, wherein, The communication device includes: processor; Memory used to store the processor's executable instructions; The processor is configured to implement the cache status reporting method according to any one of claims 1 to 16 and 17 to 31 when running the executable instructions.

35. A computer storage medium, wherein, The computer storage medium stores a computer-executable program, which, when executed by a processor, implements the cache status report reporting method according to any one of claims 1 to 16, 17 to 31.

Images