Buffer status report method and communication device

Abstract

The present invention relates to a method, apparatus, communication device and storage medium for buffer status report, in which a UE (user equipment) reports a BSR (buffer status report) for uplink data with an urgent scheduling request.

Description

Cross-Citation of Related Applications

[0001] This application is the Japanese national stage of International Application No. PCT / CN2022 / 120818, filed on September 23, 2022, the entire contents of which are incorporated herein by reference for all purposes. [Technical Field]

[0002] The present disclosure relates to, but is not limited to, the field of communications technology, and more particularly to a reporting method, apparatus, communications device, and storage medium for buffer status reporting. [Background technology]

[0003] In Extended Reality (XR) services, XR service data typically consists of multiple data flows (Qosflows), and the amount of service data is very large. During transmission, XR service flows must meet certain latency requirements, especially when several data flows arrive at the server simultaneously for decoding. If even one data flow is delayed, the joint decoding of multiple data flows may fail. Summary of the Invention [Means for solving the problem]

[0004] An embodiment of the present disclosure provides a method for reporting a buffer status report, and Communication Device Su Disclose.

[0005] According to a first aspect of the present disclosure, there is provided a method for reporting a buffer status report, the method being performed by a UE (user equipment), comprising: This includes reporting a buffer status report (BSR) for uplink data with urgent scheduling requests.

[0006] In one embodiment, reporting a BSR for uplink data with an urgent scheduling request comprises: determining that a logical channel corresponding to the uplink data having an urgent scheduling request has the highest priority, and reporting the BSR based on the priority of the logical channel;

[0007] In one embodiment, reporting a BSR for uplink data with an urgent scheduling request comprises: Triggering and reporting the BSR of the logical channel in response to the logical channel having uplink data with the urgent scheduling request.

[0008] In one embodiment, reporting a BSR for uplink data with an urgent scheduling request comprises: Triggering a first type BSR of a first logical channel in response to at least one logical channel having uplink data with an urgent scheduling request, wherein a priority of the first type BSR is higher than a priority of a second type BSR, and the first logical channel is a highest priority logical channel among the at least one logical channel.

[0009] In one embodiment, reporting a BSR for uplink data with an urgent scheduling request comprises: In response to a logical channel having uplink data with an urgent scheduling request, determining that the logical channel has a first highest priority and reporting the BSR based on the first highest priority, the first highest priority being higher than a second highest priority.

[0010] In one embodiment, the uplink data includes uplink data of an extended reality (XR) service.

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

[0012] In one embodiment, the setting granularity of the delay threshold is: UE grain size, Logical channel granularity, or Contains one of the logical channel group granularities.

[0013] In one embodiment, the uplink data with the urgent scheduling request is at data packet granularity; or The uplink data with the urgent scheduling request is at a data packet set granularity.

[0014] In one embodiment, the method comprises: The method further includes determining, according to first indication information obtained from the non-access stratum or the application layer, that the uplink data has the urgent scheduling request.

[0015] In one embodiment, reporting a BSR for uplink data with an urgent scheduling request comprises: and reporting a BSR for uplink data having an emergency scheduling request according to an indication of the second indication information transmitted from the base station.

[0016] In one embodiment, the second indication comprises a delay threshold associated with a remaining data packet delay budget of the uplink data.

[0017] In one embodiment, reporting the BSR for the uplink data having an emergency scheduling request according to the indication of the second indication information sent by the base station includes: Reporting the BSR for uplink data having an emergency scheduling request of the UE according to an indication of the second indication information; reporting the BSR for uplink data having an urgent scheduling request of a predetermined logical channel according to an indication of the second indication information; and reporting the BSR for uplink data having an urgent scheduling request of a predetermined logical channel group according to an indication of the second indication information.

[0018] In one embodiment, the method comprises: The method further includes transmitting assistance information to a base station, the assistance information configured to indicate that the UE is capable of reporting a BSR for the uplink data with an emergency scheduling request.

[0019] According to a second aspect of the present disclosure, there is provided a method for reporting a buffer status report performed by a base station, comprising: The method includes receiving a buffer status report (BSR), the BSR being transmitted by a user equipment (UE) for uplink data with an urgent scheduling request.

[0020] In one embodiment, the BSR is reported based on the priority of the logical channels, with the UE determining that the logical channel corresponding to the uplink data with urgent scheduling request has the highest priority.

[0021] In one embodiment, the BSR is triggered and reported by the UE in response to a logical channel having the uplink data with an urgent scheduling request.

[0022] In one embodiment, the reported BSR comprises a first type BSR associated with a first logical channel; The first type BSR is triggered and reported by the UE in response to at least one logical channel having uplink data with an urgent scheduling request, the first logical channel being the highest priority logical channel among the at least one logical channel, and the priority of the first type BSR is higher than the priority of the second type BSR.

[0023] In one embodiment, the BSR determines that a logical channel has a first highest priority in response to the UE having uplink data with an urgent scheduling request on the logical channel, and is reported based on the first highest priority, the first highest priority being higher than the second highest priority.

[0024] In one embodiment, the uplink data includes uplink data of an extended reality (XR) service.

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

[0026] In one embodiment, the setting granularity of the delay threshold is: UE grain size, Logical channel granularity, or Contains one of the logical channel group granularities.

[0027] In one embodiment, the uplink data with the urgent scheduling request is at data packet granularity; or The uplink data with the urgent scheduling request is at a data packet set granularity.

[0028] In one embodiment, the method comprises: The method further includes sending second indication information to the UE, wherein the second indication information is configured to indicate that the UE should report a BSR for the uplink data with the emergency scheduling request.

[0029] In one embodiment, the second indication comprises a delay threshold associated with a remaining data packet delay budget of the uplink data.

[0030] In one embodiment, the second instruction information comprises: reporting the BSR for the uplink data with an emergency scheduling request of the UE; reporting the BSR for the uplink data having an urgent scheduling request for a predetermined logical channel; and reporting the BSR for uplink data having an urgent scheduling request for a predetermined logical channel group.

[0031] In one embodiment, transmitting the second indication information to the UE comprises: and transmitting the second indication information to the UE in response to receiving auxiliary information transmitted by the UE, the auxiliary information being configured to indicate that the UE is capable of reporting the BSR for the uplink data having the emergency scheduling request.

[0032] According to a third aspect of the present disclosure, there is provided a reporting device for a buffer status report, the reporting device being installed in a UE (user equipment), comprising: The system includes a transceiver module configured to report a buffer status report (BSR) for uplink data having an urgent scheduling request.

[0033] In one embodiment, the transceiver module comprises: determining that a logical channel corresponding to the uplink data having an urgent scheduling request has the highest priority, and reporting the BSR based on the priority of the logical channel;

[0034] In one embodiment, the transceiver module comprises: The BSR of a logical channel is configured to be triggered to be reported in response to the logical channel having uplink data with the urgent scheduling request.

[0035] In one embodiment, the transceiver module comprises: and configured to trigger a first type BSR of a first logical channel in response to at least one logical channel having uplink data with an urgent scheduling request, wherein a priority of the first type BSR is higher than a priority of a second type BSR, and the first logical channel is a logical channel with a highest priority among the at least one logical channel.

[0036] In one embodiment, the transceiver module comprises: and configured to determine, in response to a logical channel having uplink data with an urgent scheduling request, that the logical channel has a first highest priority and report the BSR based on the first highest priority, the first highest priority being higher than a second highest priority.

[0037] In one embodiment, the uplink data includes uplink data of an extended reality (XR) service.

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

[0039] In one embodiment, the setting granularity of the delay threshold is: UE grain size, Logical channel granularity, or Contains one of the logical channel group granularities.

[0040] In one embodiment, the uplink data with the urgent scheduling request is at data packet granularity; or The uplink data with the urgent scheduling request is at a data packet set granularity.

[0041] In one embodiment, the device comprises: The method further includes a processing module configured to determine, according to first indication information obtained from the non-access stratum or the application layer, that the uplink data has the urgent scheduling request.

[0042] In one embodiment, the transceiver module comprises: The base station is configured to report a BSR for uplink data having an emergency scheduling request according to the instruction of the second instruction information sent from the base station.

[0043] In one embodiment, the second indication comprises a delay threshold associated with a remaining data packet delay budget of the uplink data.

[0044] In one embodiment, the transceiver module comprises: Reporting the BSR for uplink data having an emergency scheduling request of the UE according to an indication of the second indication information; reporting the BSR for uplink data having an urgent scheduling request of a predetermined logical channel according to an indication of the second indication information; and reporting the BSR for uplink data having an urgent scheduling request of a predetermined logical channel group according to an indication of the second indication information.

[0045] In one embodiment, the transceiver module comprises: The UE is further configured to send assistance information to a base station, the assistance information being configured to indicate that the UE is capable of reporting a BSR for the uplink data with an urgent scheduling request.

[0046] According to a fourth aspect of the present disclosure, there is provided a reporting device for a buffer status report, which is executed by a base station, comprising: The system includes a transceiver module configured to receive a buffer status report (BSR), the BSR being transmitted by a user equipment (UE) for uplink data having an urgent scheduling request.

[0047] In one embodiment, the BSR is reported based on the priority of the logical channels, with the UE determining that the logical channel corresponding to the uplink data with urgent scheduling request has the highest priority.

[0048] In one embodiment, the BSR is triggered and reported by the UE in response to a logical channel having the uplink data with an urgent scheduling request.

[0049] In one embodiment, the reported BSR comprises a BSR of a first type associated with a first logical channel; The first type BSR is triggered and reported by the UE in response to at least one logical channel having uplink data with an urgent scheduling request, the first logical channel being the highest priority logical channel among the at least one logical channel, and the priority of the first type BSR is higher than the priority of the second type BSR.

[0050] In one embodiment, the BSR determines that a logical channel has a first highest priority in response to the UE having uplink data with an urgent scheduling request on the logical channel, and is reported based on the first highest priority, the first highest priority being higher than the second highest priority.

[0051] In one embodiment, the uplink data includes uplink data of an extended reality (XR) service.

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

[0053] In one embodiment, the setting granularity of the delay threshold is: UE grain size, Logical channel granularity, or Contains one of the logical channel group granularities.

[0054] In one embodiment, the uplink data with the urgent scheduling request is at data packet granularity; or The uplink data with the urgent scheduling request is at a data packet set granularity.

[0055] In one embodiment, the transceiver module comprises: The method is further configured to send second indication information to the UE, the second indication information being configured to indicate that the UE should report a BSR for the uplink data with the emergency scheduling request.

[0056] In one embodiment, the second indication comprises a delay threshold associated with a remaining data packet delay budget of the uplink data.

[0057] In one embodiment, the second instruction information comprises: reporting the BSR for the uplink data with an emergency scheduling request of the UE; reporting the BSR for the uplink data having an urgent scheduling request for a predetermined logical channel; and reporting the BSR for uplink data having an urgent scheduling request for a predetermined logical channel group.

[0058] In one embodiment, the transceiver module: and configured to transmit the second indication information to the UE in response to receiving auxiliary information transmitted by the UE, the auxiliary information being configured to indicate that the UE is capable of reporting the BSR for the uplink data having the emergency scheduling request.

[0059] According to a fifth aspect of the present disclosure, there is provided a communications device, comprising: a processor; a memory for storing executable instructions for said processor; The processor is configured to implement a first manner or a second manner buffer status reporting method when executing the executable instructions.

[0060] According to a fifth aspect of the present disclosure, there is provided a computer storage medium, comprising: The computer storage medium stores a computer executable program that, when executed by a processor, implements the buffer status reporting method of the first aspect or the second aspect.

[0061] In an embodiment of the present disclosure, the UE reports a BSR for uplink data with an emergency scheduling request, thereby achieving timely scheduling of the uplink data with an emergency scheduling request, meeting the demand for communication services, reducing data transmission errors such as joint decoding failures, and improving communication reliability.

[0062] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not to be construed as limiting the embodiments of the present disclosure. [Brief explanation of the drawings]

[0063] [Figure 1] 1 is a schematic diagram of the structure of a wireless communication system; [Figure 2] 1 is a flowchart of a method for reporting a buffer status report according to an example embodiment. [Figure 3] 1 is a flowchart of a method for reporting a buffer status report according to an example embodiment. [Figure 4] 1 is a flowchart of a method for reporting a buffer status report according to an example embodiment. [Figure 5] 1 is a flowchart of a method for reporting a buffer status report according to an example embodiment. [Figure 6] 1 is a flowchart of a method for reporting a buffer status report according to an example embodiment. [Figure 7] 1 is a flowchart of a method for reporting a buffer status report according to an example embodiment. [Figure 8] 1 is a flowchart of a method for reporting a buffer status report according to an example embodiment. [Figure 9] 1 is a flowchart of a method for reporting a buffer status report according to an example embodiment. [Figure 10] 1 is a flowchart of a method for reporting a buffer status report according to an example embodiment. [Figure 11] 1 is a flowchart of a method for reporting a buffer status report according to an example embodiment. [Figure 12] 1 is a block diagram of a reporting device for buffer status reporting according to an exemplary embodiment; [Figure 13] 1 is a block diagram of a reporting device for buffer status reporting according to an exemplary embodiment; [Figure 14] FIG. 2 is a block diagram of a UE according to an example embodiment. [Figure 15] FIG. 2 is a block diagram of a base station in accordance with an exemplary embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0064] Reference will now be made in detail to exemplary embodiments, which are illustrated in the accompanying drawings. When referring to the drawings in the following description, the same numerals in different drawings represent the same or similar elements unless otherwise noted. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with embodiments of the present disclosure. Instead, they are merely examples of apparatus and methods consistent with some aspects of embodiments of the present disclosure, as detailed in the appended claims.

[0065] The terms used in the embodiments of the present disclosure are for the purpose of describing particular embodiments only and are not intended to limit the embodiments of the present disclosure. As used in the embodiments of the present disclosure and in the appended claims, the singular forms "a kind of," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise. Also, as used herein, the term "and / or" should be understood to refer to and include any or all possible combinations of one or more associated items as listed.

[0066] In the embodiments of the present disclosure, terms such as "first," "second," and "third" can be used to describe various pieces of information, but it should be understood that these pieces of information should not be limited to these terms. These terms are merely used to distinguish between the same types of information. For example, the first piece of information can also be referred to as "second information," and similarly, the second piece of information can also be referred to as "first information" without departing from the scope of the embodiments of the present disclosure. Depending on the context, the word "if" used herein may be interpreted as "at," "when," or "in response to a determination."

[0067]

[0023] Reference may be made to Figure 1, which illustrates a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure. As shown in Figure 1, the wireless communication system is a communication system based on cellular mobile communication technology, and may include a plurality of user equipments 110 and a plurality of base stations 120.

[0068] The user equipment 110 may be a device that provides a user with voice and / or data connectivity. The user equipment 110 may communicate with one or more core networks via a Radio Access Network (RAN). The user equipment 110 may be a sensor device, an Internet of Things user device such as a mobile phone (also referred to as a "cellular" phone), or a computer, such as a fixed, portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted device. For example, the user equipment 110 may be a station (STA), subscriber unit, subscriber station, mobile station, mobile, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, or user equipment. Alternatively, the user equipment 110 may be an unmanned aerial vehicle device, an in-vehicle device such as a driving computer with wireless communication capabilities or wireless user equipment connected to an external driving computer, or a roadside device with wireless communication capabilities such as a street lamp, traffic light, or other roadside device.

[0069] The base station 120 may be a network-side device in a wireless communication system. The wireless communication system may be a 4th generation mobile communication (4G) system, also known as a Long Term Evolution (LTE) system. Alternatively, the wireless communication system may be a 5G system, also known as a New Air Interface System or a 5GNR system. Alternatively, the wireless communication system may be a next-generation system of a 5G system. An access network in a 5G system may be called a New Generation-Radio Access Network (NG-RAN).

[0070] The base station 120 may be an evolved base station (eNB) used in a 4G system. Alternatively, the base station 120 may also be a base station (gNB) using a centralized-distributed architecture in a 5G system. When the base station 120 uses a centralized-distributed architecture, it generally includes a centralized unit (CU) and at least two distributed units (DUs). The centralized unit includes a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The distributed units are provided with a physical (PHY) layer protocol stack. The specific implementation of the base station 120 is not limited to the embodiments of the present disclosure.

[0071] A wireless connection may be established between the base station 120 and the user equipment 110 via a wireless air interface. In different embodiments, the wireless air interface may be a wireless air interface based on a fourth generation mobile communication network technology (4G) standard. Alternatively, the wireless air interface may be a wireless air interface based on a fifth generation mobile communication network technology (5G) standard. For example, the wireless air interface may be a new air interface. Alternatively, the wireless air interface may be a wireless air interface based on a 5G next-generation mobile communication network technology standard.

[0072] In some embodiments, E2E (End to End) connections may also be established between user equipment 110 in V2X (vehicle to everything) communications, such as vehicle to everything (V2V) communications, vehicle to infrastructure (V2I) communications, and vehicle to pedestrian (V2P) communications.

[0073] Here, the user equipment can be regarded as a terminal device in the following embodiments.

[0074] In some embodiments, the wireless communication system may also include a network management device 130 .

[0075] The multiple base stations 120 are each connected to a network management device 130. The network management device 130 may be a core network device of a wireless communication system. For example, the network management device 130 may be a Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Alternatively, the network management device may be another core network device, 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 embodiments of the present disclosure are not limited in the implementation manner of the network management device 130.

[0076] In order to facilitate the understanding of persons skilled in the art, the embodiments of the present disclosure will list several embodiments to clearly explain the technical solutions in the embodiments of the present disclosure. Obviously, those skilled in the art can understand that the several embodiments provided by the embodiments of the present disclosure can be implemented separately, can be implemented together with the methods of other embodiments in the embodiments of the present disclosure, or can be implemented separately or in combination with some embodiments in other related technologies. The embodiments of the present disclosure are not limited in this respect.

[0077] The network scheduling of data flows is dynamic. In some cases, even if a data flow belongs to a low-priority logical channel, if no data packets have been scheduled for a long time, it is necessary to send a BSR to promptly notify the network in order to meet the demands of XR services for multiple data flows. However, with the existing mechanism, a BSR may only be sent when data arrives on a high-priority logical channel, which makes it impossible to meet urgent scheduling requests.

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

[0079] As shown in FIG. 2 , an embodiment of the present disclosure provides a reporting method for a buffer status report performed by a UE (user equipment), including: In step 201: Report BSR for uplink data with urgent scheduling request.

[0080] In a possible embodiment, the uplink data with urgent scheduling requirements may include at least one of uplink data with priority scheduling requirements and uplink data with relatively high scheduling requirements.

[0081] The uplink data with an urgent scheduling request may be uplink data that needs to be scheduled with priority, or may be uplink data that the network or the terminal determines needs to be transmitted in a timely manner.

[0082] The uplink data having an urgent scheduling requirement may be determined based on the service characteristics of the specific data. For example, whether the uplink data has an urgent scheduling requirement may be determined based on the importance of the uplink data. For example, since the I-frame data is more important than the P-frame data, the I-frame data may be determined to have an urgent scheduling requirement.

[0083] In a possible embodiment, uplink data with an urgent scheduling request may be uplink data whose time interval from the most recent transmission deadline is less than a predetermined duration threshold.

[0084] For example, uplink data with an emergency scheduling request may be one of multiple data flows involved in joint decoding. Because multiple data flows need to be jointly decoded, decoding may fail if one of the data flows does not arrive before the predetermined decoding time.

[0085] In a possible embodiment, the uplink data with urgent scheduling request may be determined based on at least one of the following: communication protocol specifications, An agreement between the UE and the network side, where the network side includes access network devices and / or core network devices such as base stations.

[0086] In the related art, a BSR can be transmitted only when data arrives on a logical channel with a high priority level. Therefore, if a logical channel carrying uplink data with an urgent scheduling request does not have a high priority level, a BSR cannot be transmitted, and therefore the request for the uplink data with an urgent scheduling request cannot be satisfied.

[0087] In this case, for the uplink data with the emergency scheduling request, reporting the BSR may include the UE sending a BSR to the base station when the uplink data with the emergency scheduling request arrives on a logical channel, where the logical channel may or may not have a high priority level.

[0088] In a possible embodiment, the BSRs include a normal BSR, a padding BSR, and a retransmission BSR.

[0089] Therefore, by reporting a BSR for uplink data with urgent scheduling requests, timely scheduling of uplink data with urgent scheduling requests can be achieved, thereby meeting communication service requirements, reducing data transmission errors such as joint decoding failures, and improving communication reliability.

[0090] In one embodiment, the uplink data includes uplink data for an extended reality (XR) service.

[0091] Typically, XR service data consists of multiple data flows (Qosflows), and the amount of service data is very large. In particular, because some data flows must arrive at the server within a certain time range for decoding, XR service flows must meet specific delay requirements during transmission. Delay in any of the data flows can result in joint decoding failure for multiple data flows. Therefore, the UE can send a BSR for XR service uplink data with an urgent scheduling request, enabling timely scheduling, satisfying the requirements of the XR service, and reducing data transmission errors such as joint decoding failure.

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

[0093] The uplink data may have a data packet delay budget, i.e., transmission within the data packet delay budget may meet the transmission time requirement of the uplink data. The remaining data packet delay budget may be the time difference between the current time and the end time of the data packet delay budget. The remaining data packet delay budget is the remaining duration for which the uplink data is transmitted and / or decoded correctly.

[0094] If the remaining data packet delay budget of the uplink data is less than the delay threshold, the UE may send a BSR for the uplink data to enable timely scheduling and satisfy the data service request.

[0095] For example, if the remaining data packet delay budget (the time left until exceeding the PDB) is less than a specific delay threshold (e.g., if the remaining data packet delay budget for the data packet is determined to be less than 10 ms, the delay threshold may be determined by the protocol or obtained from a network notification. The setting granularity of the PDB (packet delay budget) may be for a single data packet or for a set of data packets).

[0096] The terminal may estimate which data packets' PDBs are about to be exhausted, have not yet been scheduled, and therefore need to be scheduled preferentially. Uplink data with relatively high urgent scheduling requirements may be counted based on data packets (Packets) or data packet sets (Packetsets).

[0097] In one embodiment, the delay threshold setting granularity includes one of the following: UE grain size, logical channel granularity, Logical channel group granularity.

[0098] In possible embodiments, the delay threshold may be agreed upon by a communication protocol or may be indicated to the UE by a network side device such as a base station.

[0099] The UE granularity delay threshold may refer to the delay threshold being applied to all uplink data of the UE to determine whether the uplink data has an urgent scheduling request.

[0100] A logical channel granularity delay threshold may refer to the delay threshold being applied to uplink data transmitted within a logical channel to determine whether the uplink data has an urgent scheduling request.

[0101] A logical channel group granularity delay threshold may refer to the delay threshold being applied to uplink data transmitted within the logical channel group to determine whether the uplink data has an urgent scheduling request.

[0102] In one embodiment, the uplink data having the urgent scheduling request is at data packet granularity. or The uplink data with the urgent scheduling request is at a data packet set granularity.

[0103] The uplink data may be counted based on a data packet or a data packet set to determine whether the uplink data has an urgent scheduling request. The counting is performed based on a data packet or a data packet set, which can improve the flexibility of the counting and meet the requirements of different types of uplink data transmission.

[0104] As shown in FIG. 3 , an embodiment of the present disclosure provides a reporting method for a buffer status report performed by a UE (user equipment), including: In step 301, it is determined that the uplink data has an urgent scheduling request according to first indication information obtained from a non-access stratum or an application layer.

[0105] In a possible embodiment, the uplink data with the urgent scheduling request is indicated by first indication information, which may be transmitted to the UE by a network device, such as a core network, via a non-access stratum or an application layer.

[0106] For example, the uplink data having an urgent scheduling request indicated by the first indication information may be at a data packet granularity or a data packet set granularity.

[0107] As shown in FIG. 4 , an embodiment of the present disclosure provides a reporting method for a buffer status report performed by a UE, including: In step 401, the BSR is reported for the uplink data having an emergency scheduling request according to the instruction of the second instruction information sent by the base station.

[0108] The base station notifies the UE through the second indication information to enable the UE to report the BSR for the uplink data with an emergency scheduling request.

[0109] In a possible embodiment, the second indication information may be carried in dedicated signaling, such as RRC and / or DCI, and transmitted to the UE.

[0110] In one embodiment, reporting a BSR for the uplink data having an emergency scheduling request according to an indication of second indication information transmitted from the base station includes: Reporting the BSR for uplink data having an emergency scheduling request of the UE according to an indication of the second indication information; reporting the BSR for the uplink data having an urgent scheduling request of a predetermined logical channel according to an indication of the second indication information; and reporting the BSR for the uplink data having an urgent scheduling request of a predetermined logical channel group according to an indication of the second indication information.

[0111] The second indication information may indicate that the uplink data having an emergency scheduling request sent to the UE may be at UE granularity, logical channel granularity, or logical channel group granularity.

[0112] Specifically, if the second indication information corresponds to UE granularity, the UE reports the BSR for the uplink data having an urgent scheduling request of the UE.

[0113] For example, if the base station knows that the UE is a UE that runs an XR service, the second indication information corresponds to UE granularity.

[0114] Specifically, if the second indication information corresponds to a logical channel group granularity, the UE reports the BSR for the uplink data having an urgent scheduling request of the designated logical channel group.

[0115] For example, if the base station knows that the UE is a UE that runs an XR service, it can notify the UE to enable reporting of a BSR for uplink data with an urgent scheduling request for a specific logical channel group.

[0116] Specifically, if the second indication information corresponds to a logical channel granularity, the UE reports the BSR for the uplink data having an urgent scheduling request of the designated logical channel.

[0117] In a possible embodiment, the second indication information may simultaneously indicate that reporting of the BSR is enabled for the uplink data with an emergency scheduling request in at least one of the UE, logical channel, or logical channel group.

[0118] For example, if the base station knows that the UE is a UE that runs an XR service, the second indication information can notify the UE to enable BSR reporting for uplink data having an urgent scheduling request for a specific logical channel.

[0119] In one embodiment, the second indication comprises a delay threshold associated with a remaining data packet delay budget of the uplink data.

[0120] In a possible embodiment, the second indication information may explicitly indicate that the UE reports a BSR for said uplink data having an urgent scheduling request for a specified logical channel group.

[0121] In a possible embodiment, the second indication information may implicitly indicate that the UE reports a BSR for said uplink data with an urgent scheduling request of a specified logical channel group.

[0122] In a possible embodiment, the second indication information indicates a delay threshold related to the remaining data packet delay budget of the uplink data and implicitly indicates that the UE reports a BSR for said uplink data with an urgent scheduling request of the specified logical channel group.

[0123] The granularity of the delay threshold indicated by the second indication information may include one of UE granularity, logical channel granularity, or logical channel group granularity.

[0124] For example, if the network signals a delay threshold for a particular logical channel, it means that it enables the ability to report a BSR for uplink data with urgent scheduling requests.

[0125] As shown in FIG. 5 , an embodiment of the present disclosure provides a reporting method for a buffer status report performed by a UE, including: In step 501, assistance information is sent to a base station, and the assistance information is used to indicate that the UE can report the BSR for the uplink data with an emergency scheduling request.

[0126] In a possible embodiment, the UE's assistance information includes whether the UE supports the capability to report the BSR for the uplink data with an emergency scheduling request.

[0127] In a possible embodiment, the UE's assistance information includes whether the UE wishes to use the BSR reporting function for the uplink data with an urgent scheduling request.

[0128] As shown in FIG. 6 , an embodiment of the present disclosure provides a reporting method for a buffer status report performed by a UE, including: In step 601, determine that the logical channel corresponding to the uplink data with urgent scheduling request has the highest priority, and report the BSR based on the priority of the logical channel.

[0129] Here, the logical channel corresponding to the uplink data having an urgent scheduling request may be set to the highest priority, so that the UE can prioritize the triggering of BSR reports for the logical channels based on the priority of the logical channels, thereby achieving timely scheduling, meeting communication service requirements, and reducing data transmission errors such as joint decoding failures.

[0130] For example, the highest priority of a logical channel may be "1", and if a logical channel includes the uplink data with an urgent scheduling request, the priority of the logical channel may be determined to be "1", and the logical channel may have the same transmission priority as other logical channels with priority "1".

[0131] For example, when a normal BSR is triggered, the priority level of this type of logical channel should be considered as the highest priority level. (For example, if there is data to be transmitted on LCH1 and newly arrived data on LCH2, even if the logical channel priority level of LCH2 is low, data for emergency scheduling arrives on LCH2, so the priority level of the logical channel of LCH2 is higher than LCH1 and a normal BSR may be triggered for LCH2.) This allows the logical channel of data with an emergency scheduling request to trigger a BSR in a timely manner.

[0132] For example, when a padding BSR is reported, if a truncated BSR needs to be reported, the priority level of this type of logical channel should be considered as the highest priority level of the logical channel. (For example, if there is data to be sent to LCH1 and data to be sent to LCH2, even if the priority level of the logical channel of LCH2 is lower, because data requiring urgent scheduling has arrived, the priority level is higher than LCH1. Since a short truncated BSR can only carry one LCG, LCH2 of Carrying LCGID).

[0133] For example, when the BSR retransmission timer times out, the logical channel with data of a relatively urgent scheduling request must be set as the highest priority level (e.g., if LCH1 triggers a BSR report, when the retransmission timer times out, LCH1 is considered the logical channel with the highest priority level, and even though the logical channel of LCH2 has a lower priority level, LCH2 is considered the logical channel with the highest priority level because data with an urgent scheduling request has arrived).

[0134] As shown in FIG. 7 , an embodiment of the present disclosure provides a reporting method for a buffer status report performed by a UE, including: In step 701, in response to a logical channel having the uplink data with an urgent scheduling request, the BSR of the logical channel is triggered and reported.

[0135] Here, the BSR of a logical channel can be triggered by uplink data with an urgent scheduling request.

[0136] For example, when the uplink data with an emergency scheduling request arrives on a logical channel, the UE triggers a BSR associated with the logical channel to schedule the uplink data with the arrived emergency scheduling request.

[0137] For example, a BSR should be triggered if any of the following events occur in an activated cell group: Uplink data for logical channels belonging to a logical channel group (LCG) is available to the MAC entity, and 1. The uplink data belongs to a logical channel with a higher priority level than any logical channel with uplink data in the logical channel group; or 2. All logical channels belonging to a logical channel group do not contain available uplink data (UL), or 3. The available data arriving on a logical channel belonging to a logical channel group is data with urgent scheduling requirements, ie data that needs to be scheduled as soon as possible or has a stringent delay budget.

[0138] Here, the BSR may be a normal BSR.

[0139] For example, the trigger condition of the normal BSR in the related art is changed, and one trigger condition is added: it is triggered when there is an urgent scheduling data request on the logical channel, that is, the existence of data with an urgent scheduling request triggers the BSR.

[0140] For example, the trigger condition of a normal BSR in the related art is changed, and one trigger condition is added: the BSR is triggered when data having an urgent scheduling request in the logical channel changes from absent to present. Compared with the previous embodiment, this embodiment can avoid frequent triggering of this type of BSR.

[0141] As shown in FIG. 8 , an embodiment of the present disclosure provides a reporting method for a buffer status report performed by a UE, including: In step 801, in response to at least one logical channel having the uplink data with an urgent scheduling request, a first type BSR of a first logical channel is triggered, where the priority of the first type BSR is higher than the priority of a second type BSR, and the first logical channel is the highest priority logical channel among the at least one logical channel.

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

[0143] Here, the second type BSR may be a BSR used in the related art, where BSRs can be divided into several different priorities, and the first type BSR in the embodiment of the present disclosure has a higher priority than any of the priorities of the BSRs used in the related art. For example, the second type BSR may be a BSR used when a logical channel has the highest priority, and the first type BSR in the embodiment of the present disclosure has a higher priority than such a highest priority. The first type BSR may be a BSR for a logical channel of uplink data with an urgent scheduling request.

[0144] In a possible embodiment, uplink data logical channels or logical channel groups with urgent scheduling requirements may be prioritized, reporting a first type of BSR for higher level logical channels or logical channel groups.

[0145] In a possible implementation, the priority of the first type of BSR is higher than the priority of the second type of BSR.

[0146] The first type of BSR may be an XR-BSR, also called a priority BSR, which is used for priority transmission of logical channels or groups of logical channels carrying data with relatively high urgent scheduling requirements.

[0147] In a possible embodiment, if the UE determines that there is data with a relatively high urgency of scheduling requirements, it may data The priority BSR prioritizes the logical channels or logical channel groups to which the LCGs belong, forming a priority BSR. If the grant is limited, i.e., insufficient to transmit all ranked LCGs, the priority BSR can transmit as many ranked LCGs as possible.

[0148] for example 1> If a delay threshold (PdbThres) for the remaining data packet delay budget is set and the remaining data packet delay budget of the uplink data contained in any logical channel of the LCG is less than PdbThres, 2> Increase the priority of the LCG, i.e., the LCG that is about to approach the scheduling budget threshold is given priority; 2>If the UL grant cannot accommodate the SL-BSRMAC CE containing the buffer status for all priority LCGs only, An XR-BSR is reported, which contains the buffer status of as many priority LCGs as possible that have data available for transmission, taking into account the number of bits in the UL grant (i.e., the new BSR carries the priority LCGs).

[0149] The preferred BSR is the case when logical channels are prioritized: the priority level of the XR-BSR type BRS or preferred BSR may be defined before the MAC CE for (Extended) BSR. For example, logical channels should be prioritized according to the following order (highest priority listed first): Data from MAC CE or UL-CCCH for C-RNTI, MAC CE for (enhanced) BFR, or MAC CE for grant confirmation for configuration, or MAC CE for grant confirmation for multiple entry configuration, MACCE for confirming Sidelink setting grant, MAC CE for LBT failure, MACCE for timing advance reporting, MAC CE of XR-BSR, MACCE of the SL-BSR, which is prioritized in accordance with paragraph 5.22.1.6; MACCE for (extended) BSR, excluding BSR included for padding, MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR, MACCE for positioning measurement gap activation / deactivation request, MACCE for the number of guard symbols required, MACCE for timing requirements in case 6, MACCE for (extended) preemption of BSR, MACCE for SL-BSR, excluding SL-BSRs that are prioritized according to clause 5.22.1.6 and SL-BSRs for padding MAC CE for IAB-MT recommended beam pointing, or MAC CE for required IAB-MT PSD range, or MAC CE for required DL Tx power adjustment, Data from any logical channel except data from UL-CCCH, MACCE for recommended bitrate queries, MACCE, including BSR for padding, MACCE with SL-BSR for padding.

[0150] As shown in FIG. 9 , an embodiment of the present disclosure provides a reporting method for a buffer status report performed by a UE (user equipment), including: In step 901, in response to a logical channel having the uplink data with an urgent scheduling request, determine that the logical channel has a first highest priority and report the BSR based on the first highest priority, where the first highest priority is higher than a second highest priority.

[0151] Here, the second highest priority may be the highest priority of a logical channel in the related art, where logical channels may be classified into different priorities, and the second highest priority may be the highest priority among all priorities in the related art. Meanwhile, the first highest priority in the embodiment of the present disclosure is higher than the highest priority (i.e., the second highest priority) in the related art. In this case, the logical channel having the uplink data with an emergency scheduling request may be determined to have the first highest priority. The UE can report a BSR based on the priority level.

[0152] Since the first highest priority is higher than the second highest priority, the logical channel having the uplink data with urgent scheduling request has a higher priority level for reporting BSR, thereby enabling timely scheduling of the uplink data with urgent scheduling request and satisfying the data transmission request.

[0153] For example, a super priority (i.e., the first highest priority) higher than the highest priority (i.e., the second highest priority) may be introduced for a logical channel having uplink data with an urgent scheduling request, and the UE determines that the logical channel having the uplink data with the urgent scheduling request is at a higher priority level than a logical channel at a higher level.

[0154] For example, when a normal BSR is triggered, if data with a relatively high urgent scheduling requirement arrives on a specific logical channel, and the priority level of the logical channel for this type of data is higher than any other logical channel in any LCG, then a normal BSR is triggered for the LCG corresponding to that logical channel. In this way, a normal BSR can be triggered when data with a relatively high urgent scheduling requirement arrives on a specific logical channel.

[0155] For example, when a padded BSR is truncated and reported, if there is data with a relatively high urgent scheduling request, the UE determines that the LCG ID of the logical channel is carried in a short truncated BSR for reporting (because the logical channel is at a super-high priority level), and in the case of a long truncated BSR, since multiple LCG information may be carried, the LCG ID of the logical channel with data with a relatively high urgent scheduling request is placed first. Therefore, when data with a relatively high urgent scheduling request arrives for a certain logical channel and the grant is insufficient, and a truncated BSR needs to be reported, a priority report of the LCG corresponding to the logical channel can be triggered.

[0156] For example, when the BSR retransmission timer times out, the UE prioritizes transmission of a BSR retransmission scenario triggered by data with a relatively high urgent scheduling request (because the logical channel is at a super-high priority level). For example, if both LCH1 and LCG2 trigger a BSR retransmission report, both LCH1 and LCG2 are considered as the highest priority logical channels, but because LCH2 has data with an urgent scheduling request that triggers a BSR retransmission, the BSR carrying the LCG of LCH2 is also prioritized for reporting. Therefore, for a certain logical channel, when data with a relatively high urgent scheduling request triggers a BSR retransmission, a prioritized report of the LCG corresponding to the logical channel can be triggered.

[0157] As shown in FIG. 10 , an embodiment of the present disclosure provides a reporting method for a buffer status report performed by a base station, including: In step 1001, a BSR is received, where the BSR is transmitted by a UE (user equipment) for uplink data with an urgent scheduling request.

[0158] In a possible embodiment, the uplink data with urgent scheduling requirements may include one of uplink data with priority scheduling requirements and uplink data with relatively high scheduling requirements.

[0159] The data with an urgent scheduling request may be uplink data that needs to be scheduled with priority, or may be uplink data that the network or the terminal determines needs to be transmitted in a timely manner. Data having an urgent scheduling requirement may be determined based on the service characteristics of the specific data. For example, whether uplink data has an urgent scheduling requirement may be determined based on the importance of the uplink data. For example, I-frame data is more important than P-frame data, so the I-frame data may be determined to have an urgent scheduling requirement.

[0160] In a possible embodiment, uplink data with an urgent scheduling request may be uplink data whose time interval from the most recent transmission deadline is less than a predetermined duration threshold.

[0161] For example, uplink data with an emergency scheduling request may be one of multiple data flows involved in joint decoding. Since multiple data flows need to be jointly decoded, decoding may fail if one of the data flows does not arrive before the predetermined decoding time.

[0162] In a possible embodiment, the uplink data with urgent scheduling request may be determined based on at least one of the following: Provision of communication protocols; An agreement between the UE and the network side (wherein the network side includes an access network device such as a base station and / or a core network device).

[0163] In the related art, a BSR can be transmitted only when data arrives on a logical channel with a high priority level. Therefore, if a logical channel having uplink data with an urgent scheduling request does not have a high priority level, a BSR is not transmitted, and the request for the uplink data with an urgent scheduling request cannot be satisfied.

[0164] In this case, for uplink data with an emergency scheduling request, reporting a BSR may include the UE sending a BSR to the base station when the uplink data with the emergency scheduling request arrives on a logical channel, where the logical channel may or may not have high priority.

[0165] In a possible embodiment, the BSRs include a normal BSR, a padding BSR, and a retransmission BSR.

[0166] In this way, by reporting a BSR for uplink data with an emergency scheduling request, timely scheduling of the uplink data with an emergency scheduling request can be achieved, thereby meeting communication service requirements, reducing data transmission errors such as joint decoding failures, and improving communication reliability.

[0167] In one embodiment, the uplink data includes uplink data for an extended reality (XR) service.

[0168] Typically, XR service data consists of multiple data flows (Qosflows), and the amount of service data is very large. In particular, because some data flows must arrive at the server within a certain time range for decoding, XR service flows must meet specific delay requirements during the transmission process. If a delay occurs in any of the data flows, joint decoding for multiple data flows may fail. Therefore, the UE can send a BSR for uplink data of an XR service with an urgent scheduling request, enabling timely scheduling, satisfying the requirements of the XR service, and reducing data transmission errors such as joint decoding failures.

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

[0170] The uplink data may have a data packet delay budget, i.e., transmission within the data packet delay budget may meet the transmission time requirement of the uplink data. The remaining data packet delay budget may be the time difference between the current time and the end time of the data packet delay budget. The remaining data packet delay budget is the remaining duration in which the uplink data can be transmitted and / or decoded correctly.

[0171] If the remaining data packet delay budget of the uplink data is less than the delay threshold, the UE may transmit a BSR for the uplink data to enable timely scheduling and meet service requirements.

[0172] For example, if the remaining data packet delay budget (the time left until exceeding the PDB) is less than a specific delay threshold (e.g., if the remaining data packet delay budget for the data packet is determined to be less than 10 ms, the delay threshold may be specified by a protocol agreement or obtained from a network notification. The setting granularity of the data packet delay budget (PDB) may be for a single data packet or for a set of data packets).

[0173] The UE may estimate which data packets are close to being exhausted, have not yet been scheduled, and therefore need to be scheduled preferentially. Uplink data with relatively high urgent scheduling requirements may be counted based on data packets or data packet sets.

[0174] In one embodiment, the delay threshold setting granularity includes one of the following: UE grain size, logical channel granularity, Logical channel group granularity.

[0175] In possible embodiments, the delay threshold may be agreed upon by a communication protocol or may be indicated to the UE by a network side device such as a base station.

[0176] The UE granular delay threshold may refer to the delay threshold being applied to all uplink data of the UE to determine whether the uplink data has an urgent scheduling request.

[0177] A logical channel granularity delay threshold may refer to the delay threshold being applied to uplink data transmitted within a logical channel to determine whether the uplink data has an urgent scheduling request.

[0178] A logical channel group granularity delay threshold may refer to the delay threshold being applied to uplink data transmitted within the logical channel group to determine whether the uplink data has an urgent scheduling request.

[0179] In one embodiment, the uplink data having the urgent scheduling request is at data packet granularity. or The uplink data with the urgent scheduling request is at the granularity of a set of data packets.

[0180] The uplink data may be counted based on a data packet or a data packet set to determine whether the uplink data has an urgent scheduling request. The counting is performed based on a data packet or a data packet set, which can improve the flexibility of the counting and meet the requirements of different types of uplink data transmission.

[0181] As shown in FIG. 11 , an embodiment of the present disclosure provides a reporting method for a buffer status report performed by a base station, including: In step 1101: second indication information is sent to the UE, where the second indication information is used to indicate that the UE reports a BSR for uplink data having an emergency scheduling request.

[0182] The base station notifies the UE via the second indication information to enable the UE to report a BSR for uplink data having an emergency scheduling request.

[0183] In a possible embodiment, the second indication information may be carried in dedicated signaling, such as RRC and / or DCI, and transmitted to the UE.

[0184] In one embodiment, the second indication is configured to indicate one of the following: reporting a BSR for the uplink data with an urgent scheduling request of the UE; reporting a BSR for said uplink data having an urgent scheduling request for a given logical channel; or Reporting the BSR for uplink data with urgent scheduling requests for a given logical channel group.

[0185] The second indication information may indicate that the uplink data having an emergency scheduling request sent to the UE may be at UE granularity, logical channel granularity, or logical channel group granularity.

[0186] Specifically, if the second indication information corresponds to UE granularity, the UE reports a BSR for uplink data having an urgent scheduling request of the UE.

[0187] For example, if the base station knows that the UE is an XR service UE, the second indication information corresponds to UE granularity.

[0188] Specifically, if the second indication information corresponds to a logical channel group granularity, the UE reports a BSR for the uplink data having an urgent scheduling request of the designated logical channel group.

[0189] For example, if the base station knows that the UE is an XR service UE, it can notify the UE to enable reporting of a BSR for uplink data with an urgent scheduling request for a specific logical channel group (LCG).

[0190] Specifically, if the second indication information corresponds to the granularity of a logical channel, the UE reports the BSR for the uplink data having an urgent scheduling request of a specific logical channel.

[0191] In a possible embodiment, the second indication information may indicate that reporting of the BSR is enabled for the uplink data having an emergency scheduling request in at least one of a UE, a logical channel, or a logical channel group.

[0192] For example, if the base station knows that the UE is an XR service UE, the second indication information can notify the UE to enable BSR reporting for uplink data with an urgent scheduling request for a specific logical channel.

[0193] In one embodiment, the second indication comprises a delay threshold associated with a remaining data packet delay budget of the uplink data.

[0194] In a possible embodiment, the second indication information may explicitly indicate that the UE reports the BSR for the uplink data with an urgent scheduling request for a specific logical channel group.

[0195] In a possible embodiment, the second indication information may implicitly indicate that the UE reports the BSR for the uplink data with an urgent scheduling request for a specific logical channel group.

[0196] In a possible embodiment, the second indication information indicates a delay threshold related to the remaining data packet delay budget of the uplink data to implicitly indicate that the UE reports the BSR for the uplink data having an urgent scheduling request of a specific logical channel group.

[0197] The granularity of the delay threshold indicated by the second indication information may include one of UE granularity, logical channel granularity, or logical channel group granularity.

[0198] For example, if the network signals a delay threshold for a particular logical channel, it means that it enables the ability to report a BSR for uplink data with urgent scheduling requests.

[0199] In one embodiment, sending the second indication information to the UE comprises: and transmitting the second indication information to the UE in response to receiving auxiliary information transmitted by the UE, the auxiliary information being configured to indicate that the UE is capable of reporting a BSR for the uplink data having an emergency scheduling request.

[0200] In a possible embodiment, the UE's assistance information includes whether the UE supports the capability to report a BSR for said uplink data with an emergency scheduling request.

[0201] In a possible embodiment, the UE's assistance information includes whether the UE wishes to use the BSR reporting function for the uplink data with an urgent scheduling request.

[0202] The base station may send second indication information to the UE after determining the UE's capability to report the BSR for the uplink data with an emergency scheduling request and / or after determining that the UE wants to use the function of reporting the BSR for the uplink data with an emergency scheduling request.

[0203] In one embodiment, the BSR determines that the logical channel corresponding to the uplink data with urgent scheduling request by the UE has the highest priority, and is reported based on the priority of the logical channel.

[0204] Here, the logical channel corresponding to the uplink data having an urgent scheduling request may be set to the highest priority, so that the UE can prioritize the triggering of BSR reports for the logical channels based on the priorities of the logical channels, thereby performing timely scheduling, meeting communication service requirements, and reducing data transmission errors such as joint decoding failures.

[0205] For example, the highest priority of a logical channel may be "1", and if a logical channel includes the uplink data with an urgent scheduling request, the priority of the logical channel may be determined to be "1", and the logical channel may have the same transmission priority as other logical channels with priority "1".

[0206] For example, when a normal BSR is triggered, the priority level of this type of logical channel should be considered as the highest priority level. (For example, if there is data to be transmitted on LCH1 and newly arrived data on LCH2, even if the logical channel priority level of LCH2 is low, data for emergency scheduling arrives on LCH2, so the priority of the logical channel of LCH2 is higher than the priority level of LCH1, and a normal BSR may be triggered for LCH2.) This allows the logical channel of data with an emergency scheduling request to trigger a BSR in a timely manner.

[0207] For example, when a padding BSR is reported, if a truncated BSR needs to be reported, the priority level of this type of logical channel should be considered as the highest priority level of the logical channel. (For example, if there is data to be sent to LCH1 and data to be sent to LCH2, even if the priority level of the logical channel of LCH2 is lower, because data requiring urgent scheduling has arrived, the priority level is higher than LCH1. Since a short truncated BSR can only carry one LCG, LCH2 of Carrying LCGID).

[0208] For example, when the BSR retransmission timer times out, the logical channel with data of a relatively urgent scheduling request must be set as the highest priority level (e.g., if LCH1 triggers a BSR report, when the retransmission timer times out, LCH1 is considered the logical channel with the highest priority level, and even though the logical channel of LCH2 has a lower priority level, LCH2 is considered the logical channel with the highest priority level because data with an urgent scheduling request has arrived).

[0209] In one embodiment, the BSR is triggered and reported by the UE in response to a logical channel having the uplink data with an urgent scheduling request.

[0210] Here, the BSR of a logical channel can be triggered by uplink data with an urgent scheduling request.

[0211] For example, when uplink data with an emergency scheduling request arrives on a logical channel, the UE triggers a BSR associated with the logical channel to schedule the uplink data with the arrived emergency scheduling request.

[0212] For example, a BSR should be triggered if any of the following events occur in an activated cell group: Uplink data for logical channels belonging to a logical channel group (LCG) is available to the MAC entity, and 1. The uplink data belongs to a logical channel whose priority is higher than the priority of any logical channel having uplink data in the logical channel group; or 2. All logical channels belonging to a logical channel group do not contain available uplink (UL) data, or 3. Available data arriving on a logical channel belonging to a logical channel group has urgent scheduling requirements, ie, data that needs to be scheduled as soon as possible or has a stringent delay budget.

[0213] Here, the BSR may be a normal BSR.

[0214] For example, the trigger condition of the normal BSR in the related art is modified, and one trigger condition is added: it is triggered when the logical channel has an urgent scheduling data request, that is, it is triggered by the existence of data with an urgent scheduling request.

[0215] For example, the trigger condition of a normal BSR in the related art is changed, and one trigger condition is added: when data having an urgent scheduling request in the logical channel changes from absent to present, which can avoid frequent triggering of this type of BSR compared with the previous embodiment.

[0216] In one embodiment, the reported BSR includes a first type BSR associated with a first logical channel; The first type BSR is triggered and reported by the UE in response to at least one logical channel having the uplink data with an emergency scheduling request, the first logical channel being a logical channel with a highest priority among the at least one logical channel, and the priority of the first type BSR is higher than the priority of a second type BSR.

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

[0218] Here, the second type BSR may be a BSR used in related art, where BSRs in related art may have different priorities. The first type BSR in the embodiment of the present disclosure has a higher priority than any of the BSRs used in related art. For example, the second type BSR may be a BSR used when a logical channel has the highest priority, and the first type BSR in the embodiment of the present disclosure has a higher priority than such a highest priority. The first type BSR may be a BSR for a logical channel of uplink data with an urgent scheduling request.

[0219] In a possible embodiment, logical channels or logical channel groups of uplink data with urgent scheduling requirements may be prioritized, reporting a first type of BSR for higher level logical channels or logical channel groups. In a possible implementation, the priority of the first type of BSR is higher than the priority of the second type of BSR.

[0220] The first type of BSR may be an XR-BSR, also called a priority BSR, which is used for priority transmission of logical channels or groups of logical channels carrying data with relatively high urgent scheduling requirements.

[0221] In a possible embodiment, if the UE determines that there is data with a relatively high urgent scheduling requirement, the logical channels or logical channel groups to which the logical channels of this type belong are prioritized to form a priority BSR. If there is a grant limitation, i.e., insufficient to transmit all ranked LCGs, the priority BSR can transmit as many ranked LCGs as possible.

[0222] for example 1> If a delay threshold (PdbThres) for the remaining data packet delay budget is set and the remaining data packet delay budget of the uplink data contained in any logical channel of the LCG is less than PdbThres, 2> Increase the priority of the LCG, i.e., the LCG that is about to approach the scheduling budget threshold is given priority; 2>If the UL grant cannot accommodate the SL-BSRMAC CE containing the buffer status for all priority LCGs only, An XR-BSR is reported, which contains the buffer status of as many priority LCGs as possible that have data available for transmission, taking into account the number of bits in the UL grant (i.e., the new BSR carries the priority LCGs).

[0223] A preferred BSR is when logical channels are prioritized: the priority level of a BSR of type XR-BSR or a priority BSR may be defined before MAC CE for (Extended) BSR. For example, logical channels should be prioritized according to the following order (highest priority listed first): Data from MAC CE or UL-CCCH for C-RNTI, MAC CE for (enhanced) BFR, or MAC CE for grant confirmation for configuration, or MAC CE for grant confirmation for multiple entry configuration, MACCE for confirming Sidelink setting grant, MAC CE for LBT failure, MACCE for timing advance reporting, MAC CE of XR-BSR, MACCE of the SL-BSR, which is prioritized in accordance with paragraph 5.22.1.6; MACCE for (extended) BSR, excluding BSR included for padding, MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR, MACCE for positioning measurement gap activation / deactivation request, MACCE for the number of guard symbols required, MACCE for timing requirements in case 6, MACCE for (extended) preemption of BSR, MACCE for SL-BSR, excluding SL-BSRs that are prioritized according to clause 5.22.1.6 and SL-BSRs for padding MAC CE for IAB-MT recommended beam pointing, or MAC CE for required IAB-MT PSD range, or MAC CE for required DL Tx power adjustment, Data from any logical channel except data from UL-CCCH, MACCE for recommended bitrate queries, MACCE, including BSR for padding, MACCE with SL-BSR for padding.

[0224] In one embodiment, The BSR determines that the logical channel has a first highest priority in response to the UE having the uplink data with an urgent scheduling request for the logical channel, and reports based on the first highest priority, the first highest priority being higher than the second highest priority.

[0225] Here, the second highest priority may be the highest priority of a logical channel in the related art. In the related art, logical channels may be classified into different priorities, and the second highest priority may be the highest priority among all priorities in the related art. Meanwhile, the first highest priority in the embodiment of the present disclosure is higher than the highest priority (i.e., the second highest priority) in the related art. In this case, the logical channel having the uplink data with an urgent scheduling request may be determined to have the first highest priority. The UE can report a BSR based on the priority level.

[0226] Since the first highest priority is higher than the second highest priority, the logical channel having the uplink data with urgent scheduling request has a higher priority level for reporting BSR, thereby enabling timely scheduling of the uplink data with urgent scheduling request and satisfying the data transmission request.

[0227] For example, a super priority higher than the highest priority may be introduced for a logical channel having uplink data with an urgent scheduling request, and the UE determines that the logical channel having the uplink data with the urgent scheduling request has a higher priority than the priority of a higher-level logical channel.

[0228] For example, when a normal BSR is triggered, if data with a relatively high urgent scheduling requirement arrives on a specific logical channel, and the priority level of the logical channel for this type of data is higher than any other logical channel in any LCG, then a normal BSR is triggered for the LCG corresponding to that logical channel. In this way, a normal BSR can be triggered when data with a relatively high urgent scheduling requirement arrives on a specific logical channel.

[0229] For example, when a padded BSR is truncated and reported, if there is data with a relatively high urgent scheduling request, the UE determines that the LCG ID of the logical channel is carried in a short truncated BSR for reporting (because the logical channel is at a super-high priority level), and in the case of a long truncated BSR, since multiple LCG information may be carried, the LCG ID of the logical channel with data with a relatively high urgent scheduling request is placed first. Therefore, when data with a relatively high urgent scheduling request arrives for a certain logical channel and the grant is insufficient, and a truncated BSR needs to be reported, a priority report of the LCG corresponding to the logical channel can be triggered.

[0230] For example, when the BSR retransmission timer times out, the UE prioritizes transmission of a BSR retransmission scenario triggered by data with a relatively high urgent scheduling request (because the logical channel is at a super-high priority level). For example, if both LCH1 and LCG2 trigger a BSR retransmission report, both LCH1 and LCG2 are considered as the highest priority logical channels, but because LCH2 has data with an urgent scheduling request that triggers a BSR retransmission, the BSR carrying the LCG of LCH2 is also prioritized for reporting. Therefore, for a certain logical channel, when data with a relatively high urgent scheduling request triggers a BSR retransmission, a prioritized report of the LCG corresponding to the logical channel can be triggered.

[0231] To further illustrate any embodiment of the present disclosure, specific embodiments are provided below.

[0232] 1. Solutions for reporting BSR for specific data. a) Specific data refers to data (uplink data) that has a relatively high urgent scheduling requirement (i.e., has an urgent scheduling requirement) in the XR service.

[0233] The data with urgent scheduling requirements may be data that needs to be prioritized for scheduling, or may be data that the network or terminal deems needs to be transmitted in a timely manner.

[0234] The data having urgent scheduling requirements may also be extended to other service characteristics of the particular data, such as importance, for example, I-frame data is more important than P-frame data and needs to be transmitted in a timely manner.

[0235] 2. The UE (e.g., terminal) determines data with relatively high urgent scheduling requirements based on the following mechanism: a) As an embodiment: The access layer obtains specific data from the non-access layer or the application layer, which is data that has a relatively high urgent scheduling requirement in the XR service. b) As an embodiment: The access layer obtains from the non-access layer or the application layer specific data that is relatively important in the XR service and needs to be prioritized for transmission. c) As an embodiment, the access stratum obtains specific data from the non-access stratum or application stratum, which data has a relatively high urgent scheduling requirement in the XR service, and which may be based on an implicit instruction from the non-access stratum or application stratum, such as I-frame data. d) In one embodiment, the remaining data packet delay budget (the time left until exceeding the PDB) is less than a certain threshold (e.g., the remaining data packet delay budget of the data packet is less than 10 ms, and the threshold may be promised by a protocol agreement or obtained from a network notification). The granularity of the setting of the data packet delay budget (PDB) may be for a single data packet or for a set of data packets.

[0236] That is, the terminal may estimate which data packets' PDBs are close to being exhausted, have not yet been scheduled, and therefore need to be scheduled preferentially.

[0237] e) Data with relatively high urgency scheduling requirements may be counted based on data packets or data packet sets.

[0238] 3. Form 1: The UE first identifies specific data (such as data having an urgent scheduling request) and temporarily sets the logical channel in which the specific data is located to the highest priority level. a) As an embodiment: When a normal BSR is triggered, the priority level of this type of logical channel should be considered as the highest priority level of the logical channel. (For example, if there is uplink data to be transmitted on LCH1 and there is newly arrived data on LCH2, even though the logical channel priority level of LCH2 is lower, the priority level of LCH2 is higher than that of LCH1 because data with an urgent scheduling request has arrived. A normal BSR may also be triggered for LCH2.)

[0239] The advantage of doing so is that logical channels of data with urgent scheduling requirements can trigger a BSR in a timely manner. b) In one embodiment, when a padding BSR is reported, if a truncated BSR needs to be reported, the priority level of this type of logical channel should be considered as the highest priority level of the logical channel. (For example, if there is data to be transmitted to LCH1 and data to be transmitted to LCH2, even if the priority level of the logical channel of LCH2 is low, the priority level is set to LCH1 because data requiring urgent scheduling has arrived.) 1The LCG of LCH2 is higher, in this case because the Short Truncated BSR can only carry one LCG.

[0240] c) As an embodiment: When the BSR retransmission timer times out, the logical channel in which data with a relatively high urgent scheduling request is located should be considered as the highest priority level (for example, if LCH1 triggers a BSR report, when the retransmission timer times out, LCH1 is considered as the logical channel with the highest priority, and even though the logical channel priority level of LCH2 is lower, LCH2 is considered as the highest priority level because data with an urgent scheduling request has arrived).

[0241] 4. Mode 2: The UE triggers a normal BSR when data with a relatively high urgency scheduling request arrives. a) As an embodiment: the conventional triggering conditions of a normal BSR are modified and one triggering condition is added: there is data with an urgent scheduling request on the logical channel. For example, a BSR should be triggered if any of the following events occur in an activated cell group: Uplink data for logical channels belonging to a logical channel group (LCG) is available to the MAC entity, and 1) the uplink data belongs to a logical channel with a higher priority than the priority of any logical channel with uplink data in the logical channel group; or 2) All logical channels belonging to a logical channel group do not contain available uplink data (UL), or 3) The available data arriving on a logical channel belonging to a logical channel group is data with urgent scheduling requirements, i.e., data that needs to be scheduled as soon as possible or has a stringent delay budget.

[0242] where: A BSR shall be triggered if any of the following events occur for an activated cell group: ‐UL data, for a logical channel which belongs to an LCG, becomes available to the MACentity; AND either -this UL data belongsto a logical channel with higherpriority than the priorityof any logicalchannel containing availableUL data whichbelong to any LCG; or -none of the logicalchannels which belong toan LCG containsany available ULdata; or ‐UL data, for a logical channel which belongs to an LCG, becomes available data which hasto be scheduled as soon as possible or has strictdelay buget; in which case theBSR is referred below to as 'Regular BSR';).

[0243] In one embodiment, the triggering condition of a normal BSR in the related art is modified and one triggering condition is added: it is triggered when the logical channel has an urgent scheduling data request, i.e., the existence of data with an urgent scheduling request triggers the BSR.

[0244] In one embodiment, the trigger condition of a normal BSR in the related art is changed, and one trigger condition is added: when data with an urgent scheduling request in the logical channel changes from absent to present, this embodiment can avoid frequent triggering of this type of BSR compared with the previous embodiment.

[0245] 5. Form 3: A new type of BSR, such as XR-BSR, also called priority BSR, is defined, which is used for priority transmission of logical channels or logical channel groups having data with relatively high urgent scheduling requirements.

[0246] In one embodiment, when the UE determines that there is data with a relatively high urgent scheduling requirement, data The logical channels or logical channel groups to which they belong are prioritized to form a Priority BSR. If the grant is limited, i.e., insufficient to transmit all ranked LCGs, the Priority BSR can transmit as many ranked LCGs as possible.

[0247] Example 1: The embodiment of the priority transmission XR in form 3 is as follows: 1> If a remaining data packet delay budget threshold (delay threshold) is set and the remaining data packet delay budget of uplink data included in any logical channel of the LCG is less than the remaining data packet delay budget threshold (i.e., the data packet delay budget is exhausted), 2> Increase the priority of the LCG, i.e., the LCG that is about to approach the scheduling budget threshold is given priority; 2>If the UL grant cannot accommodate the SL-BSRMAC CE containing the buffer status for all priority LCGs only, An XR-BSR or a preferred BSR is reported, and the XR-BSR contains the buffer status of as many preferred LCGs as possible that have data available for transmission, taking into account the number of bits in the UL grant (i.e., the new BSR carries the preferred LCGs). 1>if PdbThres is configured and the value of the logical channelsthat belong toany LCG andcontain UL data whose remaining delaybudget is less than PdbThres according to clause 5.4.5: 2> prioritize the LCG(s) 2>if the UL grant cannot accommodate anSL-BSR MAC CEcontaining buffer status onlyfor all prioritized LCG: report XR-BSR containing bufferstatus for asmany prioritized LCGshaving data availablefor transmission aspossible, taking the numberof bits inthe UL grant intoconsideration.)

[0248] Example 2: When the logical channel is prioritized, the priority level of the XR-BSR type BSR or priority BSR may be defined before the MAC CE for (Extended) BSR. The following provides one embodiment.

[0249] For example, logical channels should be prioritized according to the following order (highest priority listed first): Data from MAC CE or UL-CCCH for C-RNTI, MAC CE for (enhanced) BFR, or MAC CE for grant confirmation for configuration, or MAC CE for grant confirmation for multiple entry configuration, MACCE for confirming Sidelink setting grant, MAC CE for LBT failure, MACCE for timing advance reporting, MACCE of XR-BSR or Priority-BSR, MACCE of the SL-BSR, which is prioritized in accordance with paragraph 5.22.1.6; MACCE for (extended) BSR, excluding BSR included for padding, MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR, MACCE for positioning measurement gap activation / deactivation request, MACCE for the number of guard symbols required, MACCE for timing requirements in case 6, MACCE for (extended) preemption of BSR, MACCE for SL-BSR, excluding SL-BSRs that are prioritized according to clause 5.22.1.6 and SL-BSRs for padding MAC CE for IAB-MT recommended beam pointing, or MAC CE for required IAB-MT PSD range, or MAC CE for required DL Tx power adjustment, Data from any logical channel except data from UL-CCCH, MACCE for recommended bitrate queries, MACCE, including BSR for padding, MACCE with SL-BSR for padding.

[0250] 6. Form 4: A super priority (i.e., the first highest priority) at a level higher than the highest priority (i.e., the second highest priority) may be introduced. The UE determines that a logical channel having data with an urgent scheduling request is at a higher level of priority than the priority of the higher-level logical channel.

[0251] a) In one embodiment, when a normal BSR is triggered, if data with a relatively high urgency scheduling requirement arrives on a certain logical channel, the priority level of the logical channel for this type of data is higher than any other logical channel in any LCG, in which case a normal BSR is triggered for the LCG corresponding to that logical channel.

[0252] In the above embodiment, it can be ensured that when uplink data with relatively high urgent scheduling requirements arrive on a specific logical channel, a normal BSR is triggered.

[0253] In one embodiment, when the padding BSR is truncated and reported, if the UE has data of a relatively high urgent scheduling request, the LCG ID of the logical channel is carried in the short truncated BSR for reporting (because the logical channel is at a very high priority level), and in the case of a long truncated BSR, since multiple LCG information may be carried, the LCG ID of the logical channel with uplink data of a relatively high urgent scheduling request is placed at the beginning.

[0254] In the above embodiment, when uplink data arrives for a certain logical channel with a relatively high urgency scheduling requirement, and the grant is insufficient and a truncated BSR report is required, it can be ensured that a priority report of the LCG corresponding to the logical channel is triggered.

[0255] c) In one embodiment, when the BSR retransmission timer times out, the UE prioritizes the transmission of retransmission BSR scenarios triggered by data with a relatively high urgent scheduling request (because the logical channel is at a very high priority level). For example, if both LCH1 and LCG2 trigger a BSR retransmission report, both LCH1 and LCG2 are considered as the highest priority logical channels, but since LCH2 has data with an urgent scheduling request that triggers a BSR retransmission, the BSR carrying the LCG of LCH2 is also prioritized for reporting.

[0256] In the above embodiment, for a particular logical channel, when a BSR retransmission of data with a relatively high urgent scheduling requirement is performed, priority reporting of the LCG corresponding to the logical channel may be guaranteed.

[0257] 7. The base station enables this feature by informing the UE via dedicated signaling (second indication information).

[0258] a) Form A: Notification granularity may be per UE granularity.

[0259] In one embodiment: the base station enables this function if it knows that the UE is a UE that runs the XR service.

[0260] b) Form B: The notification granularity may be perLCG granularity.

[0261] As an embodiment: if the base station knows that the UE is a UE that runs the XR service, it notifies the UE that this function is available for a specific LCG.

[0262] c) Form C: The notification granularity may be per logical channel granularity.

[0263] As an embodiment: if the base station knows that the UE is a UE that runs the XR service, it notifies the UE that this function is available for a specific logical channel.

[0264] d) The notification method for enabling this feature may be explicit or implicit.

[0265] As an embodiment: if the network advertises a delay budget threshold for a particular logical channel, it means that this feature is enabled.

[0266] 8. The base station informs the UE that this function can be used based on the aiding information via dedicated signaling.

[0267] The UE assistance information includes whether the UE supports the ability to use this function.

[0268] The UE's auxiliary information includes whether the UE wants to use this feature (e.g., if the UE estimates that the data has a relatively high urgent scheduling requirement, it reports auxiliary information indicating that it wants to use it).

[0269] As shown in FIG. 12 , the present disclosure provides a reporting apparatus 100 for buffer status reporting, which is installed in a UE, and includes: Transmitting and receiving module 110 0 is configured to report a buffer status report (BSR) for uplink data with an urgent scheduling request.

[0270] In one embodiment, the transceiver module 110 0 Specifically, it is structured as follows: Determine that the logical channel corresponding to the uplink data with an urgent scheduling request has the highest priority, and report the BSR based on the priority of the logical channel.

[0271] In one embodiment, the transceiver module 110 0 Specifically, it is structured as follows: In response to a logical channel having the uplink data with an urgent scheduling request, triggering and reporting the BSR of the logical channel.

[0272] In one embodiment, the transceiver module 110 0 Specifically, it is structured as follows: In response to at least one logical channel having the uplink data with an urgent scheduling request, trigger a first type BSR of a first logical channel, where a priority of the first type BSR is higher than a priority of a second type BSR, and the first logical channel is a logical channel with a highest priority among the at least one logical channel.

[0273] In one embodiment, the transceiver module 110 0 Specifically, it is structured as follows: In response to a logical channel having the uplink data with an urgent scheduling request, determine that the logical channel has a first highest priority and report the BSR based on the first highest priority, where the first highest priority is higher than a second highest priority.

[0274] In one embodiment, the uplink data includes uplink data of an extended reality (XR) service.

[0275] In one embodiment, the uplink data with the urgent scheduling request includes the uplink data whose remaining data packet delay budget is less than a delay threshold.

[0276] In one embodiment, the delay threshold setting granularity includes one of the following: UE grain size, Logical channel granularity, or Logical channel group granularity.

[0277] In one embodiment, the uplink data having the urgent scheduling request is at data packet granularity. or The uplink data with the urgent scheduling request is at a data packet set granularity.

[0278] In one embodiment, the device further comprises: Processing Module 120 0 is configured to determine, according to first indication information obtained from a non-access stratum or an application layer, that the uplink data has an urgent scheduling request.

[0279] In one embodiment, the transceiver module is specifically configured as follows: According to the instruction of the second instruction information sent by the base station, report the BSR for the uplink data having an emergency scheduling request.

[0280] In one embodiment, the second indication comprises a delay threshold associated with a remaining data packet delay budget of the uplink data.

[0281] In one embodiment, the transceiver module 110 0 is specifically configured to do one of the following: reporting the BSR for the uplink data having an emergency scheduling request of the UE according to the indication of the second indication information;

[0282] reporting the BSR for the uplink data having an urgent scheduling request of a predetermined logical channel according to the indication of the second indication information; or The BSR is reported for the uplink data having an urgent scheduling request of a predetermined logical channel group according to the instruction of the second instruction information.

[0283] In one embodiment, the transceiver module 110 0 is further constructed as follows: Sending assistance information to a base station, the assistance information configured to indicate that the UE is capable of reporting the BSR for the uplink data with an urgent scheduling request.

[0284] As shown in FIG. 13 , the present disclosure provides a reporting device 200 for buffer status reporting, which is installed in a base station, and includes: The transceiver module 210 is configured to receive a buffer status report BSR, which is sent by a UE (user equipment) for uplink data with an urgent scheduling request.

[0285] In one embodiment, the BSR determines that the logical channel corresponding to the uplink data with urgent scheduling request by the UE has the highest priority, and is reported based on the priority of the logical channel.

[0286] In one embodiment, the BSR is triggered and reported by the UE in response to a logical channel having the uplink data with an urgent scheduling request.

[0287] In one embodiment, the reported BSR comprises a first type BSR associated with a first logical channel; The first type BSR is triggered and reported by the UE in response to at least one logical channel having the uplink data with an urgent scheduling request, the first logical channel being the logical channel with the highest priority among the at least one logical channel, and the priority of the first type BSR is higher than the priority of the second type BSR.

[0288] In one embodiment, the BSR determines that a logical channel has a first highest priority in response to the UE having the uplink data with an urgent scheduling request on the logical channel, and reports based on the first highest priority, the first highest priority being higher than the second highest priority.

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

[0290] In one embodiment, the uplink data with the urgent scheduling request includes the uplink data whose remaining data packet delay budget is less than a delay threshold.

[0291] In one embodiment, the delay threshold setting granularity includes one of the following: UE grain size, Logical channel granularity, or Logical channel group granularity.

[0292] In one embodiment, the uplink data having the urgent scheduling request is at data packet granularity. or The uplink data with the urgent scheduling request is at a data packet set granularity.

[0293] In one embodiment, the transceiver module 210 is further configured as follows: Send second indication information to the UE, where the second indication information is configured to indicate that the UE reports the BSR for the uplink data with an urgent scheduling request.

[0294] In one embodiment, the second indication comprises a delay threshold associated with a remaining data packet delay budget of the uplink data.

[0295] In one embodiment, the second indication is configured to indicate one of the following: reporting the BSR for the uplink data with an emergency scheduling request of the UE; reporting the BSR for the uplink data with an urgent scheduling request for a given logical channel; or The BSR is reported for the uplink data having an urgent scheduling request for a predetermined logical channel group.

[0296] In one embodiment, the transceiver module 210 is specifically configured as follows: In response to receiving the auxiliary information transmitted by the UE, transmit second indication information to the UE, the auxiliary information being configured to indicate that the UE is capable of reporting a BSR for the uplink data having an emergency scheduling request.

[0297] An embodiment of the present disclosure provides a communication device including: processor, a memory for storing processor executable instructions; Here, the processor is configured, when executing the executable instructions, to implement a method for reporting a buffer status report according to any of the embodiments of the present disclosure.

[0298] In one embodiment, the communication device may include, but is not limited to, at least one of a UE and a network device, where the network device may include a core network device or an access network device, etc., where the access network device may include a base station, and the core network device may include an AMF, an SMF, etc.

[0299] The processor may include various types of storage media that are non-transitory computer storage media and may continue to retain information stored therein even after the user equipment is powered off.

[0300] The processor may be connected to the memory via a bus or the like to read executable programs stored on the memory, such as, for example, at least one of the methods shown in Figures 2 to 11.

[0301] The present disclosure also provides a computer storage medium storing a computer-executable program, which, when executed by a processor, performs a buffer status report method according to any embodiment of the present disclosure, such as at least one of the methods illustrated in FIGS.

[0302] Regarding the devices or storage media in the above embodiments, the specific embodiments in which each module performs the operations have been described in detail in the method embodiments, and will not be described in detail here.

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

[0304] Referring to FIG. 14, the user equipment 3000 may include one or more components: a processing component 3002, a memory 3004, a power component 3006, a multimedia component 3008, an audio component 3010, an input / output (I / O) interface 3012, a sensor component 3014, and a communication component 3016.

[0305] The processing component 3002 typically controls the overall operation of the user equipment 3000, including but not limited to, display, telephone calls, data communications, camera operation, recording operations, etc. The processing component 3002 may include one or more processors 3020 that execute instructions to complete all or some of the steps of the methods described above. Additionally, the processing component 3002 may include one or more modules that facilitate interaction between the processing component 3002 and other components. For example, the processing component 3002 may include a multimedia module for facilitating interaction between the multimedia component 3008 and the processing component 3002.

[0306] The memory 3004 is configured to store various types of data to support operation on the user equipment 3000. Examples of this data include instructions for any applications or methods to operate on the user equipment 3000, contact data, phone book data, messages, images, videos, etc. The memory 3004 can be implemented by any type of volatile or non-volatile storage device, 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 memory, flash memory, magnetic disk, optical disk, or a combination thereof.

[0307] The power supply component 3006 provides power to the various components of the user equipment 3000. The power supply component 3006 may include a power management system, one or more power sources, and other components associated with the generation, management, and distribution of power for the user equipment 3000.

[0308] The multimedia component 3008 includes a screen that provides an output interface between the user equipment 3000 and a user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). When the screen includes a touch panel, the screen is implemented as a touch screen and can receive input signals from a user. The touch panel includes one or more touch sensors for detecting touches, slides, and gestures on the touch panel. The touch sensors can detect not only the boundaries of a touch or slide operation but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 3008 includes a front camera and / or a rear camera. When the user equipment 3000 is in an operating mode, such as a photo mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera may have a fixed optical lens system or may have a focal length and optical zoom capability.

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

[0310] The I / O interface 3012 provides an interface between the processing component 3002 and a peripheral interface module, which may be a keyboard, click wheel, buttons, etc. These buttons include, but are not limited to, a home page button, volume buttons, start button, and lock button.

[0311] The sensor component 3014 includes one or more sensors for providing various aspects of the user equipment 3000 with status assessment. For example, the sensor component 3014 can detect the on / off status of the user equipment 3000, the relative position of a component, such as the display and keypad of the user equipment 3000, a change in the position of the user equipment 3000 or one of its components, the presence or absence of a user's contact with the device 3000, the orientation or acceleration / deceleration of the device 3000, and a change in temperature of the device 3000. The sensor component 3014 can include a proximity sensor configured to detect the presence of a nearby object in the absence of any physical contact. The sensor component 3014 can also include an optical sensor, such as a CMOS or CCD image sensor for use in imaging applications. In some embodiments, the sensor component 3014 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0312] The communication component 3016 is configured to facilitate wired or wireless communication between the user equipment 3000 and other devices. The user equipment 3000 may access a wireless network based on a communication standard such as WiFi, 4G, or 5G, or a combination thereof. In an exemplary embodiment, the communication component 3016 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 3016 further includes a near-field communication (NFC) module for facilitating short-range communication. For example, the NFC module may be implemented based on wireless frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0313] 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 processors (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

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

[0315] As shown in Figure 15, one embodiment of the present disclosure illustrates the structure of a base station. For example, base station 900 may be provided as a network-side device. Referring to Figure 15, base station 900 includes a processing component 922 further including one or more processors, and memory resources represented by memory 932 for storing instructions, such as applications, that may be executed by processing component 922. The application program stored in memory 932 may include one or more modules, each corresponding to a set of instructions. Furthermore, processing component 922 is configured to execute instructions to perform any of the aforementioned methods applied to the base station.

[0316] The base station 900 may also include a power supply component 926 configured to perform power management for the base station 900, a wired or wireless network interface 950 configured to connect the base station 900 to a network, and an input / output (I / O) interface 958. The base station 900 may be operated by an operating system stored in memory 932, such as, for example, Windows Server™, Mac OS X™, Unix™, Linux™, or FreeBSD™.

[0317] Other embodiments of the present disclosure will be readily apparent to those skilled in the art after studying the specification and practicing the teachings disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure in accordance with the general principles of the present disclosure, including techniques known or customary in the art but not disclosed herein. The specification and embodiments are considered exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0318] It should be understood that the present disclosure is not limited to the exact construction described above and illustrated in the accompanying drawings, and that various modifications and changes may be made thereto without departing from the scope thereof, which is limited only by the appended claims.

Claims

1. A method for reporting a buffer status report (BSR) performed by a user equipment (UE), comprising: A method for reporting a buffer status report, including reporting a BSR for uplink data with an urgent scheduling request.

2. reporting a BSR for uplink data having the urgent scheduling request, 2. The method of claim 1, further comprising: determining that a logical channel corresponding to the uplink data with an urgent scheduling request has the highest priority; and reporting the BSR based on the priority of the logical channel.

3. reporting a BSR for uplink data having the urgent scheduling request, 2. The method of claim 1, comprising triggering and reporting the BSR of a logical channel in response to the logical channel having the uplink data with an urgent scheduling request.

4. reporting a BSR for uplink data having the urgent scheduling request, 2. The method of claim 1, further comprising: triggering a first type BSR of a first logical channel in response to at least one logical channel having the uplink data with an urgent scheduling request, wherein a priority of the first type BSR is higher than a priority of a second type BSR, and the first logical channel is a highest priority logical channel among the at least one logical channel.

5. reporting a BSR for uplink data having the urgent scheduling request, 2. The method of claim 1, further comprising: in response to a logical channel having the uplink data with an urgent scheduling request, determining that the logical channel has a first highest priority; and reporting the BSR based on the first highest priority, the first highest priority being higher than a second highest priority.

6. The method according to any one of claims 1 to 5, wherein the uplink data includes uplink data of an XR (Extended Reality) service.

7. The method of claim 6 , wherein the uplink data with the urgent scheduling request comprises the uplink data whose remaining data packet delay budget is less than a delay threshold.

8. The setting granularity of the delay threshold is: UE granularity, Logical channel granularity, or The method of claim 7 , wherein the channel group granularity is one of: logical channel group granularity;

9. the uplink data with the urgent scheduling request is at data packet granularity; or The method of claim 6 , wherein the uplink data with the urgent scheduling request is at a data packet set granularity.

10. The method comprises: The method of claim 6 , further comprising: determining, according to first indication information obtained from the non-access stratum or the application layer, that the uplink data has an urgent scheduling request.

11. reporting a BSR for uplink data having the urgent scheduling request, The method according to any one of claims 1 to 5, comprising reporting the BSR for the uplink data having an emergency scheduling request according to an indication of second indication information transmitted from a base station.

12. The method of claim 11 , wherein the second indication comprises a delay threshold associated with a remaining data packet delay budget for the uplink data.

13. reporting the BSR for the uplink data having an emergency scheduling request according to the indication of the second indication information transmitted by the base station, reporting the BSR for the uplink data having an emergency scheduling request of the UE according to an indication of the second indication information; reporting the BSR for the uplink data having an urgent scheduling request of a predetermined logical channel according to the indication of the second indication information; and reporting the BSR for the uplink data having an urgent scheduling request of a predetermined logical channel group according to an indication of the second indication information.

14. The method comprises:

6. The method according to claim 1, further comprising: transmitting auxiliary information to a base station, the auxiliary information being configured to indicate that the UE is capable of reporting a BSR for the uplink data with an emergency scheduling request.

15. A reporting method for (buffer status report) performed by a base station, comprising: A method for reporting a buffer status report, comprising: receiving a BSR, the BSR being transmitted by a UE (user equipment) for uplink data having an urgent scheduling request.

16. 16. The method of claim 15, wherein the BSR is reported based on the priority of the logical channel corresponding to the uplink data having an urgent scheduling request determined by the UE to have the highest priority.

17. The method of claim 15, wherein the BSR is triggered and reported by the UE in response to a logical channel having the uplink data with an urgent scheduling request.

18. the reported BSR includes a first type BSR associated with a first logical channel; 16. The method of claim 15, wherein the first type BSR is triggered and reported by a UE in response to at least one logical channel having the uplink data with an urgent scheduling request, the first logical channel being a logical channel with a highest priority among the at least one logical channel, and a priority of the first type BSR is higher than a priority of the second type BSR.

19. 16. The method of claim 15, wherein the BSR is reported based on the first highest priority determined by the UE in response to the logical channel having the uplink data with an urgent scheduling request, the first highest priority being higher than the second highest priority.

20. The method according to any one of claims 15 to 19, wherein the uplink data includes uplink data of an XR (Extended Reality) service.

21. 21. The method of claim 20, wherein the uplink data with the urgent scheduling request comprises uplink data with a remaining data packet delay budget less than a delay threshold.

22. The setting granularity of the delay threshold is: UE granularity, Logical channel granularity, or 22. The method of claim 21, including one of logical channel group granularity.

23. the uplink data with the urgent scheduling request is at data packet granularity; or The method of claim 20, wherein the uplink data with the urgent scheduling request is at a data packet set granularity.

24. The method comprises:

20. The method according to claim 15, further comprising: transmitting second indication information to the UE, wherein the second indication information is configured to indicate that the UE reports the BSR for the uplink data with the emergency scheduling request.

25. 25. The method of claim 24, wherein the second indication comprises a delay threshold associated with a remaining data packet delay budget for the uplink data.

26. The second instruction information is reporting the BSR for the uplink data with an emergency scheduling request of the UE; reporting the BSR for the uplink data having an urgent scheduling request for a predetermined logical channel; and reporting the BSR for the uplink data having an urgent scheduling request for a predetermined logical channel group.

27. transmitting the second indication information to the UE, 25. The method of claim 24, comprising transmitting the second indication information to the UE in response to receiving auxiliary information transmitted by the UE, the auxiliary information configured to indicate that the UE is capable of reporting the BSR for the uplink data with the emergency scheduling request.

28. A reporting device for a buffer status report installed in a UE (user equipment), comprising: A buffer status report reporting device includes a transceiver module configured to report a buffer status report (BSR) for uplink data having an urgent scheduling request.

29. A buffer status report device installed in a base station, comprising:

1. A buffer status report reporting device, comprising: a transceiver module configured to receive a buffer status report (BSR), the BSR being transmitted by a user equipment (UE) for uplink data having an urgent scheduling request.

30. 1. A communication device, comprising: a processor; a memory for storing executable instructions for said processor; A communications device, wherein the processor, when executing the executable instructions, is configured to implement the method for reporting a buffer status report of any one of claims 1 to 14 or 15 to 27.

31. 1. A computer storage medium, comprising: The computer storage medium stores a computer-executable program, which, when executed by a processor, implements the method for reporting a buffer status report according to any one of claims 1 to 14 or 15 to 27.

Images