WO2024060191A1 - 一种缓存状态报告上报方法、装置、通信设备及存储介质 - Google Patents

一种缓存状态报告上报方法、装置、通信设备及存储介质 Download PDF

Info

Publication number
WO2024060191A1
WO2024060191A1 PCT/CN2022/120818 CN2022120818W WO2024060191A1 WO 2024060191 A1 WO2024060191 A1 WO 2024060191A1 CN 2022120818 W CN2022120818 W CN 2022120818W WO 2024060191 A1 WO2024060191 A1 WO 2024060191A1
Authority
WO
WIPO (PCT)
Prior art keywords
bsr
uplink data
logical channel
scheduling requirements
data
Prior art date
Application number
PCT/CN2022/120818
Other languages
English (en)
French (fr)
Inventor
李艳华
江小威
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202280003696.6A priority Critical patent/CN116097728A/zh
Priority to PCT/CN2022/120818 priority patent/WO2024060191A1/zh
Publication of WO2024060191A1 publication Critical patent/WO2024060191A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]

Definitions

  • the present disclosure relates to but is not limited to the field of communication technology, and in particular, to a cache status report reporting method, device, communication equipment and storage medium.
  • XR business data usually consists of multiple data flows (Qos flows), and the amount of business data is very large.
  • the XR business stream needs to meet certain delay requirements during the transmission process, especially some data streams need to arrive at the server at the same time for decoding. Delay in any one of the data streams will cause joint decoding of multiple data streams to fail.
  • Embodiments of the present disclosure disclose a cache status report reporting method, device, communication equipment and storage medium.
  • a cache status report reporting method which is executed by user equipment UE and includes:
  • the cache status report BSR is reported.
  • reporting BSR for uplink data with emergency scheduling requirements includes:
  • the logical channel corresponding to the uplink data with urgent scheduling requirements is determined as the highest priority, and the BSR is reported based on the priority of the logical channel.
  • reporting BSR for uplink data with emergency scheduling requirements includes:
  • reporting of the BSR of the logical channel is triggered.
  • reporting BSR for uplink data with emergency scheduling requirements includes:
  • a first type BSR of the first logical channel is triggered, wherein the first type BSR has a higher priority than the second type BSR, and the first type BSR
  • the logical channel is the logical channel with the highest priority among the at least one logical channel.
  • reporting the BSR for uplink data with urgent scheduling requirements includes:
  • the BSR is reported based on the first highest priority, wherein the first highest priority is higher than Second highest priority.
  • the uplink data includes: extended reality XR service uplink data.
  • the uplink data with emergency scheduling requirements includes: the uplink data whose remaining packet delay budget is less than a delay threshold.
  • the configuration granularity of the delay threshold includes one of the following:
  • the uplink data with urgent scheduling requirements is at the granularity of data packets
  • the uplink data with emergency scheduling requirements is at the granularity of a data packet set.
  • the method further includes:
  • the uplink data has emergency scheduling requirements.
  • reporting BSR for uplink data with emergency scheduling requirements includes:
  • the BSR is reported for the uplink data with urgent scheduling requirements.
  • the second indication information includes: a delay threshold associated with the remaining packet delay budget of the uplink data.
  • reporting the BSR for the uplink data with emergency scheduling requirements according to the instructions of the second instruction information sent by the base station includes one of the following:
  • the BSR is reported for the uplink data with emergency scheduling requirements for the predetermined logical channel group.
  • the method further includes:
  • auxiliary information is used to indicate that the UE can report the BSR for the uplink data with emergency scheduling requirements.
  • a cache status report reporting method which is executed by a base station and includes:
  • the BSR is determined by the UE as having the highest priority as the logical channel corresponding to the uplink data with emergency scheduling requirements, and is reported based on the priority of the logical channel.
  • the BSR is triggered by the UE in response to the uplink data having emergency scheduling requirements on the logical channel.
  • the reported BSR includes: a first type BSR, the first type BSR is associated with the first logical channel;
  • the first type of BSR is the uplink data that the UE has emergency scheduling requirements in response to at least one logical channel, and the first logical channel triggers reporting for the logical channel with the highest priority among the at least one logical channel, wherein , the first type BSR has a higher priority than the second type BSR.
  • the BSR is when the UE responds to the uplink data that the logical channel has emergency scheduling requirements, determines that the logical channel has the first highest priority, and reports it based on the first highest priority, wherein the third One highest priority is higher than the second highest priority.
  • the uplink data includes: extended reality XR service uplink data.
  • the uplink data with emergency scheduling requirements includes: the uplink data whose remaining packet delay budget is less than a delay threshold.
  • the configuration granularity of the delay threshold includes one of the following:
  • the uplink data with emergency scheduling requirements is at packet granularity
  • the uplink data with emergency scheduling requirements is at the granularity of a data packet set.
  • the method further includes:
  • the second indication information includes: a delay threshold associated with the remaining packet delay budget of the uplink data.
  • the second indication information is used to indicate one of the following:
  • sending the second indication information to the UE includes:
  • auxiliary information In response to receiving the auxiliary information sent by the UE, sending the second indication information to the UE, wherein the auxiliary information is used to indicate that the UE can report all the uplink data with emergency scheduling requirements. Describe BSR.
  • a buffer status report reporting device which is configured in a user equipment UE and includes:
  • the transceiver module is configured to report buffer status report BSR for uplink data with emergency scheduling requirements.
  • the transceiver module is specifically configured as:
  • the logical channel corresponding to the uplink data with urgent scheduling requirements is determined as the highest priority, and the BSR is reported based on the priority of the logical channel.
  • the transceiver module is specifically configured as follows:
  • reporting of the BSR of the logical channel is triggered.
  • the transceiver module is specifically configured as:
  • a first type BSR of the first logical channel is triggered, wherein the first type BSR has a higher priority than the second type BSR, and the first type BSR
  • the logical channel is the logical channel with the highest priority among the at least one logical channel.
  • the transceiver module is specifically configured as:
  • the BSR is reported based on the first highest priority, wherein the first highest priority is higher than Second highest priority.
  • the uplink data includes: extended reality XR service uplink data.
  • the uplink data with emergency scheduling requirements includes: the uplink data whose remaining packet delay budget is less than a delay threshold.
  • the configuration granularity of the delay threshold includes one of the following:
  • the uplink data with emergency scheduling requirements is at packet granularity
  • the uplink data with emergency scheduling requirements is at the granularity of a data packet set.
  • the device further includes:
  • the processing module is configured to determine that the uplink data has emergency scheduling requirements based on the first indication information obtained from the non-access layer or the application layer.
  • the transceiver module is specifically configured as:
  • the BSR is reported for the uplink data with emergency scheduling requirements.
  • the second indication information includes: a delay threshold associated with the remaining packet delay budget of the uplink data.
  • the transceiver module is specifically configured as one of the following:
  • the BSR is reported for the uplink data with urgent scheduling requirements in the predetermined logical channel group.
  • the transceiver module is further configured to:
  • auxiliary information is used to indicate that the UE can report the BSR for the uplink data with emergency scheduling requirements.
  • a cache status report reporting device is provided, wherein the device is provided in a base station and includes:
  • the transceiver module is configured to: receive a buffer status report BSR, where the BSR is sent by the user equipment UE for uplink data with emergency scheduling requirements.
  • the BSR is determined by the UE as having the highest priority as the logical channel corresponding to the uplink data with emergency scheduling requirements, and is reported based on the priority of the logical channel.
  • the BSR is triggered by the UE in response to the uplink data having emergency scheduling requirements on the logical channel.
  • the reported BSR includes: a first type BSR, the first type BSR is associated with the first logical channel;
  • the first type of BSR is the uplink data that the UE has emergency scheduling requirements in response to at least one logical channel, and the first logical channel triggers reporting for the logical channel with the highest priority among the at least one logical channel, wherein , the first type BSR has a higher priority than the second type BSR.
  • the BSR is the result of the UE responding to the uplink data that the logical channel has emergency scheduling requirements, determining that the logical channel has the first highest priority, and reporting based on the first highest priority. , wherein the first highest priority is higher than the second highest priority.
  • the uplink data includes: extended reality XR service uplink data.
  • the uplink data with emergency scheduling requirements includes: the uplink data whose remaining packet delay budget is less than a delay threshold.
  • the configuration granularity of the delay threshold includes one of the following:
  • the uplink data with emergency scheduling requirements is at packet granularity
  • the uplink data with emergency scheduling requirements is at the granularity of a data packet set.
  • the transceiver module is further configured as:
  • the second indication information includes: a delay threshold associated with the remaining packet delay budget of the uplink data.
  • the second indication information is used to indicate one of the following:
  • the transceiver module is specifically configured as:
  • auxiliary information In response to receiving the auxiliary information sent by the UE, sending the second indication information to the UE, wherein the auxiliary information is used to indicate that the UE can report all the uplink data with emergency scheduling requirements. Describe BSR.
  • a communication device wherein the communication device includes:
  • a memory for storing instructions executable by the processor
  • the processor is configured to implement the cache status report reporting method described in the first aspect or the second aspect when running the executable instructions.
  • a computer storage medium stores a computer executable program, and when executed by a processor, the executable program implements the first aspect or the second aspect. Cache status report reporting method.
  • the UE reports BSR for uplink data with emergency scheduling requirements.
  • reporting BSR for uplink data with emergency scheduling requirements can realize timely scheduling of uplink data with emergency scheduling requirements, meet communication service requirements, reduce data transmission errors such as joint decoding failure, and improve communication reliability.
  • Figure 1 is a schematic structural diagram of a wireless communication system.
  • Figure 2 is a flowchart of a cache status report reporting method according to an exemplary embodiment.
  • Figure 3 is a flowchart of a cache status report reporting method according to an exemplary embodiment.
  • Figure 4 is a flowchart of a cache status report reporting method according to an exemplary embodiment.
  • Figure 5 is a flowchart of a cache status report reporting method according to an exemplary embodiment.
  • Figure 6 is a flowchart of a cache status report reporting method according to an exemplary embodiment.
  • Figure 7 is a flowchart of a cache status report reporting method according to an exemplary embodiment.
  • Figure 8 is a flowchart illustrating a cache status report reporting method according to an exemplary embodiment.
  • Figure 9 is a flowchart of a cache status report reporting method according to an exemplary embodiment.
  • Figure 10 is a flowchart of a cache status report reporting method according to an exemplary embodiment.
  • Figure 11 is a flowchart of a cache status report reporting method according to an exemplary embodiment.
  • Figure 12 is a block diagram of a buffer status report reporting device according to an exemplary embodiment.
  • Figure 13 is a block diagram of a buffer status report reporting device according to an exemplary embodiment.
  • Figure 14 is a block diagram of a UE according to an exemplary embodiment.
  • Figure 15 is a block diagram of a base station according to an exemplary embodiment.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • word “if” as used herein may be interpreted as "when” or "when” or "in response to determining.”
  • FIG. 1 shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
  • the wireless communication system is a communication system based on cellular mobile communication technology.
  • the wireless communication system may include several user equipments 110 and several base stations 120.
  • user equipment 110 may be a device that provides voice and/or data connectivity to a user.
  • the user equipment 110 may communicate with one or more core networks via a Radio Access Network (RAN).
  • RAN Radio Access Network
  • the user equipment 110 may be an Internet of Things user equipment, such as a sensor device, a mobile phone (or a "cellular" phone) ) and computers with IoT user equipment, which may be, for example, fixed, portable, pocket-sized, handheld, computer-built-in, or vehicle-mounted devices.
  • the user equipment 110 may also be equipment of an unmanned aerial vehicle.
  • the user equipment 110 may also be a vehicle-mounted device, for example, it may be an on-board computer with a wireless communication function, or a wireless user equipment connected to an external on-board computer.
  • the user equipment 110 may also be a roadside device, for example, it may be a streetlight, a signal light or other roadside device with a wireless communication function.
  • the base station 120 may be a network-side device in a wireless communication system.
  • the wireless communication system can be the 4th generation mobile communication technology (the 4th generation mobile communication, 4G) system, also known as the Long Term Evolution (LTE) system; or the wireless communication system can also be a 5G system, Also called new air interface system or 5G NR system.
  • the wireless communication system may also be a next-generation system of the 5G system.
  • the access network in the 5G system can be called the New Generation-Radio Access Network (NG-RAN).
  • NG-RAN New Generation-Radio Access Network
  • the base station 120 may be an evolved base station (eNB) used in the 4G system.
  • the base station 120 may also be a base station (gNB) that adopts a centralized distributed architecture in the 5G system.
  • eNB evolved base station
  • gNB base station
  • the base station 120 adopts a centralized distributed architecture it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed units, DU).
  • the centralized unit is equipped with a protocol stack including the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control protocol (Radio Link Control, RLC) layer, and the Media Access Control (Medium Access Control, MAC) layer;
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • the distribution unit is provided with a physical (Physical, PHY) layer protocol stack, and the embodiment of the present disclosure does not limit the specific implementation of the base station 120.
  • a wireless connection may be established between the base station 120 and the user equipment 110 through a wireless air interface.
  • the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, such as
  • the wireless air interface is a new air interface; alternatively, the wireless air interface may also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.
  • an E2E (End to End, end-to-end) connection can also be established between user equipments 110 .
  • vehicle-to-vehicle (V2V) communication vehicle-to-roadside equipment (vehicle to Infrastructure, V2I) communication and vehicle-to-person (vehicle to pedestrian, V2P) communication in vehicle networking communication (vehicle to everything, V2X) Wait for the scene.
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-roadside equipment
  • V2P vehicle-to-person communication in vehicle networking communication
  • V2X vehicle networking communication
  • the above user equipment can be considered as the terminal equipment of the following embodiments.
  • the above-mentioned wireless communication system may also include a network management device 130.
  • the network management device 130 may be a core network device in a wireless communication system.
  • the network management device 130 may be a mobility management entity (Mobility Management Entity) in an evolved packet core network (Evolved Packet Core, EPC). MME).
  • the network management device can also be other core network devices, such as serving gateway (Serving GateWay, SGW), public data network gateway (Public Data Network GateWay, PGW), policy and charging rules functional unit (Policy and Charging Rules) Function, PCRF) or Home Subscriber Server (HSS), etc.
  • serving gateway Serving GateWay, SGW
  • public data network gateway Public Data Network GateWay, PGW
  • Policy and Charging Rules Policy and Charging Rules
  • PCRF Policy and Charging Rules
  • HSS Home Subscriber Server
  • the embodiments of the present disclosure enumerate multiple implementations to clearly describe the technical solutions of the embodiments of the present disclosure.
  • the multiple embodiments provided in the embodiments of the present disclosure can be executed alone or in combination with the methods of other embodiments in the embodiments of the present disclosure. They can also be executed alone or in combination. It is then executed together with some methods in other related technologies; the embodiments of the present disclosure do not limit this.
  • the network's scheduling of data flows is dynamic. In some cases, even if some data flows belong to low-priority logical channels, if the data packet has not been scheduled for a long time, a BSR needs to be sent to notify the network as soon as possible to meet the requirements. XR business requires multiple data streams. However, according to the existing mechanism, BSR can be sent only when data arrives on a high-priority logical channel. At this time, the need for emergency scheduling cannot be met.
  • an embodiment of the present disclosure provides a cache status report reporting method, which is executed by the UE and includes:
  • Step 201 Reporting a BSR for uplink data with urgent scheduling requirements.
  • the uplink data with urgent scheduling requirements may include one of the following: uplink data with priority scheduling requirements, and uplink data with higher scheduling requirements.
  • Data with urgent scheduling requirements may also be uplink data that requires priority scheduling; it may also be uplink data that is determined by the network or the terminal and needs to be sent in a timely manner.
  • Data with emergency dispatch requirements can also be determined based on the business characteristics of specific data. For example, it may be determined whether the uplink data has emergency scheduling requirements based on the importance of the uplink data. For example, I frame data is more important than P frame data, and it can be determined that I frame data has emergency scheduling requirements.
  • the uplink data with emergency scheduling requirements may be uplink data whose time interval from the latest sending time limit is less than a predetermined duration threshold.
  • the uplink data with emergency scheduling requirements may be one of multiple data streams that are jointly decoded. Since multiple data streams need to be jointly decoded, if one of the data streams does not arrive before the scheduled decoding time, the decoding will fail.
  • uplink data with emergency scheduling requirements can be determined by at least one of the following:
  • the UE negotiates with the network side, where the network side includes: access network equipment such as base stations, and/or core network equipment.
  • BSR can be sent only when data arrives on a logical channel with high priority. Therefore, if the logical channel of uplink data with emergency scheduling requirements does not have high priority, BSR cannot be sent. At this time, emergency scheduling requirements cannot be met. upstream data requirements.
  • the buffer status report BSR can be reported for uplink data with emergency scheduling requirements, including: when uplink data with emergency scheduling requirements arrives on the logical channel, the UE can send the BSR to the base station.
  • the logical channel may have high priority or not.
  • the BSR includes: regular BSR, padding BSR, and retransmitted BSR.
  • reporting BSR for uplink data with emergency scheduling requirements can realize timely scheduling of uplink data with emergency scheduling requirements, meet communication service requirements, reduce data transmission errors such as joint decoding failure, and improve communication reliability.
  • the uplink data includes: extended reality XR service online data.
  • XR business data consists of multiple data flows (Qos flows), and the amount of business data is very large.
  • the XR business flow needs to meet certain delay requirements during the transmission process, especially some data flows need to reach the server for decoding within a predetermined time range. Delay in any one of the data streams will cause joint decoding of multiple data streams to fail. Therefore, the UE can send BSR for the uplink data of the XR service with emergency scheduling requirements, which can achieve timely scheduling, meet the needs of the XR service, and reduce data transmission errors such as joint decoding failure.
  • the uplink data with emergency scheduling requirements includes: the uplink data whose remaining packet delay budget is less than a delay threshold.
  • the uplink data may have a packet delay budget, i.e., transmission within the packet delay budget can meet the uplink data transmission time requirement.
  • the remaining packet delay budget may be the time difference between the current moment and the end moment of the packet delay budget.
  • the remaining packet delay budget is the remaining time for the uplink data to be correctly transmitted and/or decoded.
  • the UE can send BSR for the uplink data to achieve timely scheduling and meet the needs of data services.
  • the remaining packet delay budget (the time left until exceeding the PDB) is less than a certain delay threshold (for example, it is determined that the remaining packet delay budget of the data packet is less than 10ms; the delay threshold can be agreed upon by agreement or obtained from network notification.
  • a certain delay threshold for example, it is determined that the remaining packet delay budget of the data packet is less than 10ms; the delay threshold can be agreed upon by agreement or obtained from network notification.
  • PDB The configuration granularity of (packet delay di, packet delay budget) can be for a single packet or for a collection of packets).
  • the terminal can estimate which data packets have almost been used up in the PDB and have not yet been scheduled, so priority scheduling is required. Data with higher scheduling emergency needs can be collected based on packet statistics or based on packet set statistics.
  • the configuration granularity of the delay threshold includes one of the following:
  • the delay threshold may be stipulated in the communication protocol, or may be indicated to the UE by a network side device such as a base station.
  • the delay threshold at the UE granularity can refer to all uplink data of the UE, and the delay threshold can be used to determine whether it is uplink data with emergency scheduling requirements.
  • the delay threshold at the logical channel granularity may refer to the uplink data transmitted within the logical channel, and the delay threshold may be used to determine whether the uplink data has emergency scheduling requirements.
  • the delay threshold at the logical channel group granularity may refer to the uplink data transmitted within the logical channel group, and the delay threshold may be used to determine whether it is uplink data with emergency scheduling requirements.
  • the uplink data with emergency scheduling requirements is at packet granularity
  • the uplink data with emergency scheduling requirements is at the granularity of a data packet set.
  • Uplink data can be counted based on data packets or based on packet sets (Packet set), and it can be determined whether it is uplink data with emergency scheduling requirements.
  • Statistics based on data packets or data packet sets can improve the flexibility of statistics and meet the needs of different forms of upstream data transmission.
  • an embodiment of the present disclosure provides a cache status report reporting method, which is executed by the UE and includes:
  • Step 301 Determine that the uplink data has emergency scheduling requirements based on the first indication information obtained from the non-access layer or application layer.
  • the uplink data with emergency scheduling requirements is indicated by the first indication information.
  • the first indication information may be sent to the UE by network equipment such as the core network through the non-access layer or application layer.
  • the uplink data with urgent scheduling requirements indicated by the first indication information is in the granularity of a data packet or a data packet set.
  • an embodiment of the present disclosure provides a cache status report reporting method, which is executed by the UE and includes:
  • Step 401 According to the instructions of the second instruction information sent by the base station, report the BSR for the uplink data with emergency scheduling requirements.
  • the base station notifies the UE through the second instruction information to enable reporting of the BSR for the uplink data with emergency scheduling requirements.
  • the second indication information may be carried in dedicated signaling such as RRC and/or DCI, and sent to the UE.
  • reporting the BSR for the uplink data with emergency scheduling requirements according to the instructions of the second instruction information sent by the base station includes one of the following:
  • the indication of the second indication information report the BSR for the uplink data for which the UE has emergency scheduling requirements
  • the BSR is reported for the uplink data with emergency scheduling requirements for the predetermined logical channel group.
  • the uplink data with emergency scheduling requirements that may be indicated by the second indication information may be sent to the UE at a UE granularity, a logical channel granularity, or a logical channel group granularity.
  • the UE reports the BSR for the uplink data of the UE that has emergency scheduling requirements.
  • the second indication information corresponds to the UE granularity
  • the UE reports the BSR for the uplink data with emergency scheduling requirements of the specified logical channel group.
  • the base station knows that the UE is a UE that performs XR services, it notifies it that it will enable reporting of BSR for uplink data with emergency scheduling requirements for a specific LCG;
  • the UE reports the BSR for the uplink data with emergency scheduling requirements of the specified logical channel.
  • the second indication information may also indicate at least one of the following that enables reporting of the BSR for the uplink data with an urgent scheduling requirement: UE; logical channel; logical channel group.
  • the second indication information notifies it to enable reporting of a BSR for uplink data with an emergency scheduling requirement for a specific logical channel
  • the second indication information includes: a delay threshold associated with a remaining data packet delay budget of the uplink data.
  • the second indication information may explicitly instruct the UE to report the BSR for the uplink data of the specified logical channel group that has emergency scheduling requirements.
  • the second indication information may implicitly instruct the UE to report the BSR for the uplink data of the specified logical channel group that has emergency scheduling requirements.
  • the second indication information indicates a delay threshold associated with a remaining data packet delay budget for uplink data, so as to implicitly instruct the UE to report the BSR for the uplink data with an urgent scheduling requirement for a specified logical channel group.
  • the granularity of the delay threshold indicated by the second indication information may include one of the following: UE granularity; logical channel granularity; logical channel group granularity.
  • the network notifies the delay threshold for a certain logical channel, it means that the function of reporting BSR for uplink data with emergency scheduling requirements is enabled.
  • an embodiment of the present disclosure provides a cache status report reporting method, which is executed by the UE and includes:
  • Step 501 Send auxiliary information to the base station, where the auxiliary information is used to indicate that the UE can report the BSR for the uplink data with emergency scheduling requirements.
  • the UE's assistance information includes whether the UE supports the ability to report the BSR for the uplink data with emergency scheduling requirements.
  • the UE's assistance information includes whether the UE desires to use the function of reporting the BSR for the uplink data with emergency scheduling requirements.
  • an embodiment of the present disclosure provides a cache status report reporting method, which is executed by the UE and includes:
  • Step 601 Determine the logical channel corresponding to the uplink data with emergency scheduling requirements as the highest priority, and report the BSR based on the priority of the logical channel.
  • the channel can be set to the highest priority.
  • the UE can prioritize triggering the UE to report the BSR of the logical channel based on the priority of the logical channel, and perform scheduling in a timely manner to meet the needs of communication services and reduce data transmission errors such as joint decoding failure.
  • the highest priority of a logical channel may be "1". If the logical channel contains the uplink data with emergency scheduling requirements, then the priority of the logical channel may be determined as "1". This logical channel can have the same transmission priority as other channels with priority "1".
  • the priority level of this type of logical channel is the highest priority level; (for example, LCH1 has data sent and LCH2 has new data arriving, even if the logical channel priority level of LCH2 is lower, but Because emergency scheduling data arrives at LCH2, the priority level of the LCH2 logical channel is higher than that of LCH1, and regular BSR can also be triggered for LCH2). In this way, logical channels with data that require emergency scheduling can trigger BSR in time.
  • the priority level of this type of logical channel is the highest logical channel priority level; (for example, LCH1 has data to send, LCH2 has data Send, even though the logical channel priority of LCH2 is lower, but because emergency scheduling data arrives, its priority is higher than LCH1, so the short truncated BSR (Short Truncated BSR) can only carry one LCG, so it will carry the trigger LCH2’s LCG ID)
  • the logical channel where the data with higher scheduling emergency needs is located is set to the highest priority level; (for example, LCH1 triggers the BSR report, then when the retransmission timer times out, LCH1 will It is considered to be the highest logical channel. Even if the logical channel priority of LCH2 is lower, because emergency scheduling data arrives, LCH2 is also regarded as the highest priority.)
  • an embodiment of the present disclosure provides a cache status report reporting method, which is executed by the UE and includes:
  • Step 701 In response to the uplink data that the logical channel has emergency scheduling requirements, trigger reporting of the BSR of the logical channel.
  • the BSR of the logical channel can be triggered by uplink data with urgent scheduling requirements.
  • the UE when the uplink data with urgent scheduling requirements arrives on the logical channel, the UE triggers the BSR associated with the logical channel to schedule the uplink data with urgent scheduling requirements.
  • BSR should be triggered:
  • the uplink data belongs to a logical channel whose priority is higher than the priority of the logical channel with uplink data in any logical channel group; or
  • the available data arriving on the logical channel belonging to the logical channel group has urgent scheduling requirements, that is, it needs to be scheduled as soon as possible or has a strict delay budget (stringent delay multipli)
  • the BSR may be a regular BSR.
  • the conventional BSR triggering condition in the related art is modified, and a triggering condition is added: there is an emergency scheduling data requirement in the logical channel, that is, the triggering condition. That is, data that requires emergency dispatch data can be triggered.
  • the conventional BSR triggering condition in the related art is modified, and a triggering condition is added: the data that requires emergency scheduling data in the logical channel is triggered from scratch. Compared with the previous embodiment, this method can avoid frequent triggering of this type of BSR.
  • an embodiment of the present disclosure provides a cache status report reporting method, which is executed by the UE and includes:
  • Step 801 In response to the uplink data of at least one logical channel having emergency scheduling requirements, trigger the first type BSR of the first logical channel, wherein the first type BSR has a higher priority than the second type BSR, and the first type BSR has a higher priority than the second type BSR.
  • the first logical channel is the logical channel with the highest priority among the at least one logical channel.
  • Type 1 BSR is different from Type 2 BSR.
  • the second type of BSR may be the BSR used in the related technology.
  • the BSR in the related technology may be divided into several different priorities, and the first type of BSR in the embodiment of the present disclosure is higher than any of the BSR used in the related technology.
  • Priority BSR For example, the second type BSR may be the BSR adopted when the logical channel has the highest priority, while the first type BSR in the embodiment of the present disclosure has a priority higher than the highest priority.
  • the first type of BSR may be a BSR for a logical channel with uplink data having emergency scheduling requirements.
  • logical channels or logical channel groups with uplink data that require emergency scheduling can be prioritized, and the first type of BSR is reported for logical channels or logical channel groups with high priority.
  • the priority of the first type BSR is higher than that of the second type BSR.
  • the first type of BSR can be XR-BSR or called priority BSR.
  • This BSR is used for priority transmission of logical channels or logical channel groups with data that has higher scheduling emergency requirements;
  • the UE determines that if there is data with higher scheduling emergency requirements, the logical channels/logical channel groups to which this type of logical channel belongs will be prioritized to form a priority BSR. If the authorization is limited, that is, it is not enough to transmit all the sorted LCGs, the priority BSR can transmit as many sorted LCGs as possible.
  • the XR-BSR which contains the buffer status of as many priority LCGs as possible that have valid transmission data, taking into account the number of bits in the uplink (UL) grant (i.e. the new BSR carries the priority LCG ).
  • the priority BSR performs logical channel priority processing:
  • the priority level can be defined before the MAC CE for (Extended) BSR.
  • logical channels should be prioritized in the following order (highest priority first):
  • MAC CE for (enhanced) BFR, or MAC CE for authorization confirmation of configuration, or MAC CE for authorization confirmation of multi-entry configuration
  • MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR;
  • MAC CE for IAB-MT recommended beam indication or MAC CE for required IAB-MT PSD range, or MAC CE for required DL Tx power adjustment
  • an embodiment of the present disclosure provides a cache status report reporting method, which is executed by the UE and includes:
  • Step 901 In response to the uplink data that the logical channel has emergency scheduling requirements, determine that the logical channel has the first highest priority, and report the BSR based on the first highest priority, where the first highest priority higher than the second highest priority.
  • the second highest priority may be the highest priority of the logical channel in the related technology.
  • the logical channel in the related technology may be divided into different priorities.
  • the second highest priority may be the highest priority among all priorities in the related technology.
  • the first highest priority in the embodiment of the present disclosure is higher than the highest priority in the related technology (ie, the second highest priority).
  • the logical channel of the uplink data with emergency scheduling requirements may be determined to have the first highest priority.
  • the UE can perform BSR based on the priority level.
  • the logical channel of the uplink data with emergency scheduling needs has a higher priority to report to the BSR, thereby achieving timely scheduling of the uplink data with emergency scheduling needs. Meet data transmission needs.
  • a higher priority (super priority) i.e., the second highest priority
  • the highest priority i.e., the second highest priority
  • the UE determines that the logical channel of the uplink data with emergency scheduling requirements is at a higher level than the priority level of the high-level logical channel;
  • a regular BSR when a regular BSR is triggered, if for a certain logical channel, if data with a high scheduling emergency requirement arrives, the priority level of the logical channel for this type of data is higher than that of any logical channel of any other LCG; Then the regular BSR will be triggered for the LCG corresponding to the logical channel. In this way, for a certain logical channel, if data with high scheduling emergency requirements arrives, the regular BSR can be triggered.
  • the UE determines that if there is data with a higher scheduling emergency demand, the Short Truncated BSR carries the LCG ID for the logical channel for reporting (because the logical channel is of super high priority at this time); if it is a truncated Long BSR, because it can carry multiple LCG information, the LCG ID of the logical channel with data with a higher scheduling emergency demand can be placed at the front. In this way, for a certain logical channel, if data with a higher scheduling emergency demand arrives, and the authorization is insufficient to report the truncated BSR, the priority reporting of the LCG corresponding to the logical channel can be triggered.
  • the UE when the retransmission BSR timer expires, the UE will prioritize transmission in the retransmission BSR scenario triggered by data with higher scheduling emergency needs; (because the logical channel is a super high priority at this time); for example: both LCH1 and LCG2
  • the BSR retransmission report is triggered.
  • LCH1 and LCG2 will be considered as the highest logical channels.
  • the BSR carrying the LCG transmitting LCH2 will also be reported first at this time. In this way, for a certain logical channel, if there is a BSR retransmission of data with higher scheduling emergency requirements, the LCG corresponding to the logical channel will be reported first.
  • an embodiment of the present disclosure provides a cache status report reporting method, which is executed by a base station and includes:
  • Step 1001 Receive a BSR, where the BSR is sent by the user equipment UE for uplink data with emergency scheduling requirements.
  • the uplink data with urgent scheduling requirements may include the following: uplink data with priority scheduling requirements, and uplink data with higher scheduling requirements.
  • the data with urgent scheduling requirements may also be uplink data that requires priority scheduling; or may be uplink data that is determined by the network or the terminal to be sent in a timely manner.
  • Data with emergency dispatch requirements can also be determined based on the business characteristics of specific data. For example, it may be determined whether the uplink data has emergency scheduling requirements based on the importance of the uplink data. For example, I frame data is more important than P frame data, and it can be determined that I frame data has emergency scheduling requirements.
  • the uplink data with emergency scheduling requirements may be uplink data whose time interval from the latest sending time limit is less than a predetermined duration threshold.
  • the uplink data with emergency scheduling requirements may be one of multiple data streams that are jointly decoded. Since multiple data streams need to be jointly decoded, if one of the data streams does not arrive before the scheduled decoding time, the decoding will fail.
  • uplink data with emergency scheduling requirements can be determined by at least one of the following:
  • the UE negotiates with the network side, where the network side includes: access network equipment such as base stations, and/or core network equipment.
  • a BSR can be sent only when data arrives on a logical channel with a high priority level. Therefore, if a logical channel for uplink data with urgent scheduling requirements does not have a high priority level, a BSR cannot be sent, and the requirements of the uplink data with urgent scheduling requirements cannot be met.
  • the buffer status report BSR can be reported for uplink data with emergency scheduling requirements, including: when uplink data with emergency scheduling requirements arrives on the logical channel, the UE can send the BSR to the base station.
  • the logical channel may have high priority or not.
  • the BSR includes: regular BSR, padding BSR, and retransmitted BSR.
  • reporting BSR for uplink data with emergency scheduling requirements can realize timely scheduling of uplink data with emergency scheduling requirements, meet communication service requirements, reduce data transmission errors such as joint decoding failure, and improve communication reliability.
  • the uplink data includes: extended reality XR service online data.
  • XR business data consists of multiple data flows (Qos flows), and the amount of business data is very large.
  • the XR business flow needs to meet certain delay requirements during the transmission process, especially some data flows need to reach the server for decoding within a predetermined time range. Delay in any one of the data streams will cause joint decoding of multiple data streams to fail. Therefore, the UE can send BSR for the uplink data of the XR service with emergency scheduling requirements, which can achieve timely scheduling, meet the needs of the XR service, and reduce data transmission errors such as joint decoding failure.
  • the uplink data with emergency scheduling requirements includes: the uplink data whose remaining packet delay budget is less than a delay threshold.
  • Uplink data can have a packet delay budget, that is, transmission within the packet delay budget can meet uplink data transmission time requirements.
  • the remaining packet delay budget may be the time difference between the current time and the end time of the packet delay budget.
  • the remaining packet delay budget is the remaining time for uplink data to be transmitted and/or decoded correctly.
  • the UE can send a BSR for the uplink data to achieve timely scheduling and meet the needs of the data service.
  • the remaining packet delay budget (the time left until exceeding the PDB) is less than a certain delay threshold (for example, it is determined that the remaining packet delay budget of the data packet is less than 10ms; the delay threshold can be agreed upon by agreement or obtained from network notification.
  • a certain delay threshold for example, it is determined that the remaining packet delay budget of the data packet is less than 10ms; the delay threshold can be agreed upon by agreement or obtained from network notification.
  • PDB The configuration granularity of (packet delay di, packet delay budget) can be for a single packet or for a collection of packets).
  • the terminal can estimate which data packets have almost been used up in the PDB and have not yet been scheduled, so priority scheduling is required. Data with higher scheduling emergency needs can be collected based on packet statistics or based on packet set statistics.
  • the configuration granularity of the delay threshold includes one of the following:
  • the delay threshold may be stipulated in the communication protocol, or may be indicated to the UE by a network side device such as a base station.
  • the delay threshold at the UE granularity can refer to all uplink data of the UE, and the delay threshold can be used to determine whether it is uplink data with emergency scheduling requirements.
  • the delay threshold at the logical channel granularity may refer to the uplink data transmitted within the logical channel, and the delay threshold may be used to determine whether the uplink data has emergency scheduling requirements.
  • the delay threshold at the logical channel group granularity may refer to the uplink data transmitted within the logical channel group, and the delay threshold may be used to determine whether it is uplink data with emergency scheduling requirements.
  • the uplink data with emergency scheduling requirements is at packet granularity
  • the uplink data with emergency scheduling requirements is at the granularity of a data packet set.
  • Uplink data can be counted based on data packets or based on packet sets (Packet set), and it can be determined whether it is uplink data with emergency scheduling requirements.
  • Statistics based on data packets or data packet sets can improve the flexibility of statistics and meet the needs of different forms of upstream data transmission.
  • an embodiment of the present disclosure provides a cache status report reporting method, which is executed by a base station and includes:
  • Step 1101 Send second indication information to the UE, where the second indication information is used to instruct the UE to report the BSR for the uplink data with emergency scheduling requirements.
  • the base station notifies the UE through the second instruction information to enable reporting of the BSR for the uplink data with emergency scheduling requirements.
  • the second indication information may be carried in dedicated signaling such as RRC and/or DCI, and sent to the UE.
  • the second indication information is used to indicate one of the following:
  • the uplink data with emergency scheduling requirements that may be indicated by the second indication information may be sent to the UE at a UE granularity, a logical channel granularity, or a logical channel group granularity.
  • the UE reports the BSR for the uplink data of the UE that has emergency scheduling requirements.
  • the second indication information corresponds to the UE granularity
  • the UE reports the BSR for the uplink data with emergency scheduling requirements of the specified logical channel group.
  • the base station knows that the UE is a UE performing an XR service, it notifies the UE that it will enable reporting of a BSR for uplink data with an urgent scheduling requirement for a specific LCG;
  • the UE reports the BSR for the uplink data with emergency scheduling requirements of the specified logical channel.
  • the second indication information may also indicate at least one of the following to enable reporting of the BSR for the uplink data with emergency scheduling requirements: UE; logical channel; logical channel group.
  • the second indication information notifies it to enable reporting of a BSR for uplink data with an emergency scheduling requirement for a specific logical channel
  • the second indication information includes: a delay threshold associated with a remaining data packet delay budget of the uplink data.
  • the second indication information may explicitly instruct the UE to report the BSR for the uplink data of the specified logical channel group that has emergency scheduling requirements.
  • the second indication information may implicitly instruct the UE to report the BSR for the uplink data of the specified logical channel group that has emergency scheduling requirements.
  • the second indication information indicates a delay threshold associated with a remaining data packet delay budget of the uplink data, so as to implicitly instruct the UE to report the BSR for the uplink data with an urgent scheduling requirement of a specified logical channel group.
  • the granularity of the delay threshold indicated by the second indication information may include one of the following: UE granularity; logical channel granularity; logical channel group granularity.
  • the network if it notifies a delay threshold for a certain logical channel, it means enabling a function of reporting a BSR for uplink data with urgent scheduling requirements.
  • sending the second indication information to the UE includes:
  • auxiliary information In response to receiving the auxiliary information sent by the UE, sending the second indication information to the UE, wherein the auxiliary information is used to indicate that the UE can report all the uplink data with emergency scheduling requirements. Describe BSR.
  • the UE's assistance information includes whether the UE supports the ability to report the BSR for the uplink data with emergency scheduling requirements.
  • the UE's assistance information includes whether the UE desires to use the function of reporting the BSR for the uplink data with emergency scheduling requirements.
  • the base station may send a second indication to the UE. information.
  • the BSR is determined by the UE as having the highest priority as the logical channel corresponding to the uplink data with emergency scheduling requirements, and is reported based on the priority of the logical channel.
  • the channel can be set to the highest priority.
  • the UE can prioritize triggering the UE to report the BSR of the logical channel based on the priority of the logical channel, and perform scheduling in a timely manner to meet the needs of communication services and reduce data transmission errors such as joint decoding failure.
  • the highest priority of a logical channel may be "1". If the logical channel contains the uplink data with emergency scheduling requirements, then the priority of the logical channel may be determined as "1". This logical channel can have the same transmission priority as other channels with priority "1".
  • the priority level of this type of logical channel is the highest priority level; (for example, LCH1 has data sent and LCH2 has new data arriving, even if the logical channel priority level of LCH2 is lower, but Because emergency scheduling data arrives at LCH2, the priority level of the LCH2 logical channel is higher than that of LCH1, and regular BSR can also be triggered for LCH2). In this way, logical channels with data that require emergency scheduling can trigger BSR in time.
  • the priority of this type of logical channel is the highest logical channel priority; (for example, LCH1 has data to send, and LCH2 has data to send. Even if the logical channel priority of LCH2 is lower, because emergency scheduling data arrives, its priority is higher than LCH1. In this case, since the truncated BSR can only carry one LCG, it will carry the LCG ID that triggers LCH2.)
  • the logical channel where the data with higher scheduling emergency needs is located is set to the highest priority level; (for example, LCH1 triggers the BSR report, then when the retransmission timer times out, LCH1 will It is considered to be the highest logical channel. Even if the logical channel priority of LCH2 is lower, because emergency scheduling data arrives, LCH2 is also regarded as the highest priority.)
  • the BSR is triggered to be reported by the UE in response to the uplink data having an urgent scheduling requirement on a logical channel.
  • the BSR of the logical channel can be triggered by uplink data with urgent scheduling requirements.
  • the UE when the uplink data with urgent scheduling requirements arrives on the logical channel, the UE triggers the BSR associated with the logical channel to schedule the arrived uplink data with urgent scheduling requirements.
  • BSR should be triggered:
  • the uplink data belongs to a logical channel whose priority is higher than the priority of the logical channel with uplink data in any logical channel group; or
  • the available data arriving on the logical channel belonging to the logical channel group has urgent scheduling requirements, that is, it needs to be scheduled as soon as possible or has a strict delay budget (stringent delay multipli)
  • the BSR may be a regular BSR.
  • the conventional BSR triggering condition in the related art is modified, and a triggering condition is added: there is an emergency scheduling data requirement in the logical channel, that is, the triggering condition. That is, data that requires emergency dispatch data can be triggered.
  • the conventional BSR triggering condition in the related art is modified, and a triggering condition is added: the data that requires emergency scheduling data in the logical channel is triggered from scratch. Compared with the previous embodiment, this method can avoid frequent triggering of this type of BSR.
  • the reported BSR includes: a first type BSR, the first type BSR is associated with the first logical channel;
  • the first type of BSR is the uplink data that the UE has emergency scheduling requirements in response to at least one logical channel, and the first logical channel triggers reporting for the logical channel with the highest priority among the at least one logical channel, wherein , the first type BSR has a higher priority than the second type BSR.
  • Type 1 BSR is different from Type 2 BSR.
  • the second type of BSR may be the BSR used in the related technology.
  • the BSR in the related technology may be divided into several different priorities, and the first type of BSR in the embodiment of the present disclosure is higher than any of the BSR used in the related technology.
  • Priority BSR For example, the second type BSR may be the BSR adopted when the logical channel has the highest priority, while the first type BSR in the embodiment of the present disclosure has a priority higher than the highest priority.
  • the first type of BSR may be a BSR for a logical channel with uplink data having emergency scheduling requirements.
  • logical channels or logical channel groups of uplink data with urgent scheduling requirements may be prioritized, and a first-type BSR may be reported for logical channels or logical channel groups with high priorities.
  • the priority of the first type BSR is higher than that of the second type BSR.
  • the first type of BSR can be XR-BSR or called priority BSR.
  • This BSR is used for priority transmission of logical channels or logical channel groups with data that has higher scheduling emergency requirements;
  • the UE determines that if there is data with higher scheduling emergency requirements, the logical channels/logical channel groups to which this type of logical channel belongs will be prioritized to form a priority BSR. If the authorization is limited, that is, it is not enough to transmit all the sorted LCGs, the priority BSR can transmit as many sorted LCGs as possible.
  • the XR-BSR which contains the buffer status of as many priority LCGs as possible that have valid transmission data, taking into account the number of bits in the uplink (UL) grant (i.e. the new BSR carries the priority LCG ).
  • the priority BSR performs logical channel priority processing:
  • the priority level can be defined before the MAC CE for (Extended) BSR.
  • logical channels should be prioritized in the following order (highest priority first):
  • MAC CE for (enhanced) BFR, or MAC CE for authorization confirmation of configuration, or MAC CE for authorization confirmation of multi-entry configuration
  • MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR;
  • MAC CE for SL-BSRs, except for SL-BSRs that are prioritized according to Section 5.22.1.6 and SL-BSRs used for padding;
  • MAC CE for IAB-MT recommended beam indication or MAC CE for required IAB-MT PSD range, or MAC CE for required DL Tx power adjustment
  • the BSR is when the UE responds to the uplink data that the logical channel has emergency scheduling requirements, determines that the logical channel has the first highest priority, and reports it based on the first highest priority, wherein the third One highest priority is higher than the second highest priority.
  • the second highest priority may be the highest priority of the logical channel in the related technology.
  • the logical channel in the related technology may be divided into different priorities.
  • the second highest priority may be the highest priority among all priorities in the related technology.
  • the first highest priority in the embodiment of the present disclosure is higher than the highest priority in the related technology (ie, the second highest priority).
  • the logical channel of the uplink data with emergency scheduling requirements may be determined to have the first highest priority.
  • the UE can perform BSR based on the priority level.
  • the logical channel of the uplink data with urgent scheduling requirements has a higher priority level to report the BSR, thereby achieving timely scheduling of the uplink data with urgent scheduling requirements and meeting data transmission requirements.
  • a super priority (super priority) higher than the highest priority (the highest priority) level can be introduced for a logical channel of uplink data with emergency scheduling requirements.
  • the UE determines that the logical channel of the uplink data with emergency scheduling requirements is at a higher level than the priority level of the high-level logical channel;
  • a regular BSR when a regular BSR is triggered, if for a certain logical channel, if data with a high scheduling emergency requirement arrives, the priority level of the logical channel for this type of data is higher than that of any logical channel of any other LCG; Then the regular BSR will be triggered for the LCG corresponding to the logical channel. In this way, for a certain logical channel, if data with high scheduling emergency requirements arrives, the regular BSR can be triggered.
  • the UE determines that if there is data with high scheduling emergency requirements, the Short Truncated BSR carries the LCG for the logical channel. ID reporting (because the logical channel is a super high priority at this time); if it is a truncated long BSR (Long Truncated BSR), because it can carry multiple LCG information, the logical channel with data with higher scheduling emergency needs can be The LCG ID is placed first. In this way, for a certain logical channel, if data with a high scheduling emergency requirement arrives and the authorization is insufficient and a truncated BSR needs to be reported, the priority reporting of the LCG corresponding to the logical channel can be triggered.
  • the UE when the retransmission BSR timer expires, the UE will prioritize transmission in the retransmission BSR scenario triggered by data with higher scheduling emergency needs; (because the logical channel is a super high priority at this time); for example: both LCH1 and LCG2
  • the BSR retransmission report is triggered.
  • LCH1 and LCG2 will be considered as the highest logical channels.
  • the BSR carrying the LCG transmitting LCH2 will also be reported first at this time. In this way, for a certain logical channel, if there is a BSR retransmission of data with higher scheduling emergency requirements, the LCG corresponding to the logical channel will be reported first.
  • Specific data is data (uplink data) with high emergency scheduling requirements (that is, emergency scheduling requirements) in XR services.
  • Data with urgent scheduling requirements may also be data that requires priority scheduling; it may also be data that the network or terminal deems to be sent in a timely manner.
  • Data with emergency dispatch requirements can also be extended to other business characteristics of specific data: such as importance. For example, I frame data is more important than P frame and needs to be sent in time.
  • the UE determines the data with higher scheduling emergency requirements based on the following mechanism:
  • the access layer obtains specific data from the non-access layer or the application layer, which is data with a higher scheduling urgency demand in the XR service.
  • the access layer obtains specific data from the non-access layer or from the application layer, which is more important data in the XR service and needs to be transmitted with priority.
  • the access layer obtains specific data from the non-access layer or from the application layer.
  • Data with higher scheduling emergency requirements in the XR service can be based on implicit instructions from the non-access layer or from the application layer, For example, it is I frame data.
  • the remaining packet delay budget (the time left until exceeding the PDB) is less than a certain threshold (for example, it is judged that the remaining packet delay budget of the data packet is less than 10ms; the threshold can be agreed upon in the agreement or obtained from the network notification .
  • the configuration granularity of PDB (packet delay di, packet delay budget) can be for a single packet or for a collection of packets).
  • the terminal can estimate which data packets have almost been used up in the PDB and have not yet been scheduled, so priority scheduling is required.
  • Data with higher scheduling emergency needs can be collected based on packet statistics or statistics on packet sets.
  • Mode 1 The UE first identifies specific data (such as data with urgent scheduling requirements) and temporarily sets the logical channel where the specific data is located to the highest priority level.
  • a regular BSR When a regular BSR is triggered, it is necessary to consider that the priority level of this type of logical channel is the highest logical channel priority level; (for example, LCH1 has uplink data sent and LCH2 has new data arriving, even if the logical channel of LCH2 The priority level is lower, but because LCH2 has emergency scheduling data arriving, the LCH2 logical channel priority level is higher than LCH1. Regular BSR will also be triggered for LCH2).
  • the advantage of this is that the logical channel with data with urgent scheduling requirements will trigger the BSR in time.
  • the logical channel where the data with higher scheduling emergency needs is located is set to the highest priority level; (for example, LCH1 triggers the BSR report, then when the retransmission timer times out , LCH1 will be considered as the highest logical channel, even if the logical channel priority of LCH2 is lower, but because emergency scheduling data arrives, LCH2 will also be regarded as the highest priority).
  • Method 2 The UE triggers regular BSR when data with higher scheduling emergency requirements arrives.
  • BSR should be triggered:
  • the uplink data belongs to a logical channel whose priority is higher than the priority of the logical channel with uplink data in any logical channel group;
  • the BSR may be a regular BSR.
  • a BSR shall be triggered if any of the following events occur for activated cell group:
  • this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belongs to any LCG;
  • the conventional BSR triggering conditions in related technologies are modified, and a triggering condition is added: the trigger is triggered when there is an emergency scheduling data requirement in the logical channel. That is, data that requires emergency dispatch data can be triggered.
  • the conventional BSR triggering condition in the related art is modified, and a triggering condition is added: data that requires emergency scheduling data in the logical channel is triggered from scratch. Compared with the previous embodiment, this method can avoid frequent triggering of this type of BSR.
  • Method 3 Define a new BSR, such as XR-BSR or priority BSR. This BSR is used for priority transmission of logical channels or logical channel groups with data with high scheduling emergency requirements.
  • the UE determines that if there is data with higher scheduling emergency requirements, the logical channels/logical channel groups to which this type of logical channel belongs will be prioritized to form a priority BSR. If the authorization is limited, that is, it is not enough to transmit all the sorted LCGs, the priority BSR can transmit as many sorted LCGs as possible.
  • the remaining packet delay budget threshold (delay threshold) is configured, and the remaining packet delay budget of the uplink data contained in any logical channel in the LCG is less than the remaining packet delay budget threshold (that is, the packet delay budget will be exhausted), then,
  • the XR-BSR contains the buffer status of as many priority LCGs as possible that have available transmission data, taking into account the number of bits in the uplink (UL) grant (i.e., the new BSR carries the priority LCGs).
  • Example 2 Priority BSR when performing logical channel priority processing: For XR-BSR type BRS or priority BSR, the priority level can be defined before MAC CE for (Extended) BSR. An example is given below.
  • Logical channels should be prioritized in the following order (with the highest priority first):
  • MAC CE for (enhanced) BFR, or MAC CE for authorization confirmation of configuration, or MAC CE for authorization confirmation of multi-entry configuration
  • MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR;
  • MAC CE for IAB-MT recommended beam indication or MAC CE for required IAB-MT PSD range, or MAC CE for required DL Tx power adjustment
  • Method 4 Introduce a level higher than the highest priority (i.e., the second highest priority), that is, super priority (i.e., the first highest priority); at this time The UE determines that the logical channel for data with higher scheduling emergency requirements is at a higher level than the priority level of the high-level logical channel;
  • the above embodiment can ensure that for a certain logical channel, if data with high scheduling emergency requirements arrives, the regular BSR can be triggered.
  • the UE determines that if there is data with higher scheduling emergency requirements, the LCG for the logical channel carried in the Short Truncated BSR will be truncated. ID reporting (because the logical channel is a super high priority at this time); if it is a truncated long BSR (Long Truncated BSR), because it can carry multiple LCG information, the logical channel with data with higher scheduling emergency needs can be The LCG ID is placed first.
  • the above embodiment can ensure that for a certain logical channel, if data with a high scheduling emergency requirement arrives and the authorization is insufficient and a truncated BSR needs to be reported, priority reporting of the LCG corresponding to the logical channel can be triggered.
  • the UE when the retransmission BSR timer expires, the UE will prioritize transmission in the retransmission BSR scenario triggered by data with higher scheduling emergency requirements; (because the logical channel is a super high priority at this time); for example: LCH1 Both LCH1 and LCG2 trigger BSR retransmission reporting. At this time, LCH1 and LCG2 will be considered as the highest logical channels. However, because LCH2 has BSR retransmission triggered by emergency scheduling data, the BSR carrying the LCG that transmits LCH2 will also be reported first at this time. .
  • the above embodiment can ensure that for a certain logical channel, if there is a BSR retransmission of data with higher scheduling emergency requirements, the LCG corresponding to the logical channel will be reported first.
  • the base station notifies the UE to enable this feature through dedicated signaling (second indication information);
  • Method A The notification granularity can be per UE granularity
  • the base station knows that the UE is a UE performing XR services, it will enable this function;
  • Method B The notification granularity can be perLCG granularity
  • the base station knows that the UE is a UE that performs XR services, it notifies it that it will enable this function for a specific LCG;
  • Method C The notification granularity can be per logical channel granularity
  • the base station if the base station knows that the UE is a UE that performs XR services, it notifies it to enable this function for a specific logical channel;
  • the notification method for enabling this function is display or implicit notification
  • the network if the network notifies the delay budget threshold for a certain logical channel, it means that this function is enabled;
  • the base station notifies the UE through dedicated signaling that the use of this function can be based on the UE's auxiliary information
  • the UE's auxiliary information includes whether the UE supports the ability to use this function
  • the UE's assistance information includes whether the UE expects to use this function (for example, if the UE estimates that the data has a high scheduling emergency demand, it will report the assistance information to indicate the expected use);
  • an embodiment of the present disclosure provides a cache status report reporting device 100, which is provided in a UE and includes:
  • the transceiver module 110 is configured to report a buffer status report BSR for uplink data with emergency scheduling requirements.
  • the transceiver module 110 is specifically configured as:
  • the logical channel corresponding to the uplink data with emergency scheduling requirements is determined as the highest priority, and the BSR is reported based on the priority of the logical channel.
  • the transceiver module 110 is specifically configured as:
  • reporting of the BSR of the logical channel is triggered.
  • the transceiver module 110 is specifically configured as:
  • a first type BSR of the first logical channel is triggered, wherein the first type BSR has a higher priority than the second type BSR, and the first type BSR
  • the logical channel is the logical channel with the highest priority among the at least one logical channel.
  • the transceiver module 110 is specifically configured as:
  • the BSR is reported based on the first highest priority, wherein the first highest priority is higher than Second highest priority.
  • the uplink data includes: extended reality XR service online data.
  • the uplink data with emergency scheduling requirements includes: the uplink data whose remaining packet delay budget is less than a delay threshold.
  • the configuration granularity of the delay threshold includes one of the following:
  • the uplink data with emergency scheduling requirements is at packet granularity
  • the uplink data with emergency scheduling requirements is at the granularity of a data packet set.
  • the device further includes:
  • the processing module 120 is configured to determine that the uplink data has emergency scheduling requirements based on the first indication information obtained from the non-access layer or the application layer.
  • the transceiver module is specifically configured as:
  • the BSR is reported for the uplink data with urgent scheduling requirements.
  • the second indication information includes: a delay threshold associated with the remaining packet delay budget of the uplink data.
  • the transceiver module 110 is specifically configured as one of the following:
  • the indication of the second indication information report the BSR for the uplink data for which the UE has emergency scheduling requirements
  • the BSR is reported for the uplink data with emergency scheduling requirements for the predetermined logical channel group.
  • the transceiver module 110 is further configured to:
  • auxiliary information is used to indicate that the UE can report the BSR for the uplink data with emergency scheduling requirements.
  • an embodiment of the present disclosure provides a cache status report reporting device 200, which is provided in a base station and includes:
  • the transceiver module 210 is configured to: receive a buffer status report BSR, where the BSR is sent by the user equipment UE for uplink data with emergency scheduling requirements.
  • the BSR is determined by the UE as having the highest priority as the logical channel corresponding to the uplink data with emergency scheduling requirements, and is reported based on the priority of the logical channel.
  • the BSR is triggered to be reported by the UE in response to the uplink data having an urgent scheduling requirement on a logical channel.
  • the reported BSR includes: a first type BSR, the first type BSR is associated with the first logical channel;
  • the first type of BSR is the uplink data that the UE has emergency scheduling requirements in response to at least one logical channel, and the first logical channel triggers reporting for the logical channel with the highest priority among the at least one logical channel, wherein , the first type BSR has a higher priority than the second type BSR.
  • the BSR is the result of the UE responding to the uplink data that the logical channel has emergency scheduling requirements, determining that the logical channel has the first highest priority, and reporting based on the first highest priority. , wherein the first highest priority is higher than the second highest priority.
  • the uplink data includes: extended reality XR service online data.
  • the uplink data with emergency scheduling requirements includes: the uplink data whose remaining packet delay budget is less than a delay threshold.
  • the configuration granularity of the delay threshold includes one of the following:
  • the uplink data with emergency scheduling requirements is at packet granularity
  • the uplink data with emergency scheduling requirements is at the granularity of a data packet set.
  • the transceiver module 210 is further configured to:
  • the second indication information includes: a delay threshold associated with the remaining packet delay budget of the uplink data.
  • the second indication information is used to indicate one of the following:
  • the transceiver module 210 is specifically configured as:
  • auxiliary information In response to receiving the auxiliary information sent by the UE, sending the second indication information to the UE, wherein the auxiliary information is used to indicate that the UE can report all the uplink data with emergency scheduling requirements. Describe BSR.
  • An embodiment of the present disclosure provides a communication device, including:
  • Memory used to store instructions executable by the processor
  • the processor is configured to implement the cache status report reporting method of any embodiment of the present disclosure when running executable instructions.
  • the communication device may include but is not limited to at least one of: a UE and a network device.
  • the network equipment here may include core network or access network equipment, etc.
  • the access network equipment may include a base station; the core network may include AMF and SMF.
  • the processor may include various types of storage media, which are non-transitory computer storage media that can continue to memorize the information stored thereon after the user equipment is powered off.
  • the processor may be connected to the memory through a bus or the like, and be used to read the executable program stored on the memory, for example, at least one of the methods shown in FIGS. 2 to 11 .
  • An embodiment of the present disclosure also provides a computer storage medium.
  • the computer storage medium stores a computer executable program.
  • the executable program is executed by a processor, the cache status report reporting method of any embodiment of the present disclosure is implemented. For example, at least one of the methods shown in Figures 2 to 11.
  • Figure 14 is a block diagram of a user equipment 3000 according to an exemplary embodiment.
  • the user device 3000 may be a mobile phone, a computer, a digital broadcast user device, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, or the like.
  • user equipment 3000 may include one or more of the following components: processing component 3002, memory 3004, power supply component 3006, multimedia component 3008, audio component 3010, input/output (I/O) interface 3012, sensor component 3014 , and communication component 3016.
  • Processing component 3002 generally controls the overall operations of user device 3000, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 3002 may include one or more processors 3020 to execute instructions to complete all or part of the steps of the above method.
  • processing component 3002 may include one or more modules that facilitate interaction between processing component 3002 and other components.
  • processing component 3002 may include a multimedia module to facilitate interaction between multimedia component 3008 and processing component 3002.
  • Memory 3004 is configured to store various types of data to support operations at user device 3000. Examples of such data include instructions for any application or method operating on user device 3000, contact data, phonebook data, messages, pictures, videos, etc.
  • Memory 3004 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EEPROM erasable programmable read-only memory
  • EPROM Programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory, magnetic or optical disk.
  • Power supply component 3006 provides power to various components of user equipment 3000.
  • Power supply components 3006 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to user device 3000.
  • Multimedia component 3008 includes a screen that provides an output interface between the user device 3000 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide action.
  • multimedia component 3008 includes a front-facing camera and/or a rear-facing camera.
  • the front camera and/or the rear camera may receive external multimedia data.
  • Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.
  • Audio component 3010 is configured to output and/or input audio signals.
  • audio component 3010 includes a microphone (MIC) configured to receive external audio signals when user device 3000 is in operating modes, such as call mode, recording mode, and speech recognition mode. The received audio signals may be further stored in memory 3004 or sent via communications component 3016 .
  • audio component 3010 also includes a speaker for outputting audio signals.
  • the I/O interface 812 provides an interface between the processing component 3002 and a peripheral interface module.
  • the peripheral interface module may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
  • Sensor component 3014 includes one or more sensors that provide various aspects of status assessment for user device 3000 .
  • the sensor component 3014 can detect the open/closed state of the device 3000 and the relative positioning of components, such as the display and keypad of the user device 3000.
  • the sensor component 3014 can also detect the user device 3000 or a component of the user device 3000. position changes, the presence or absence of user contact with user device 3000, user device 3000 orientation or acceleration/deceleration and temperature changes of user device 3000.
  • Sensor assembly 3014 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 3014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 3014 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 3016 is configured to facilitate wired or wireless communication between the user device 3000 and other devices.
  • the user equipment 3000 can access a wireless network based on a communication standard, such as WiFi, 4G or 5G, or a combination thereof.
  • the communication component 3016 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communications component 816 also includes a near field communications (NFC) module to facilitate short-range communications.
  • NFC near field communications
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • user equipment 3000 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation is used to perform the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A programmable gate array
  • controller microcontroller, microprocessor or other electronic component implementation is used to perform the above method.
  • a non-transitory computer-readable storage medium including instructions such as a memory 3004 including instructions, which can be executed by the processor 3020 of the user device 3000 to complete the above method is also provided.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
  • an embodiment of the present disclosure shows the structure of a base station.
  • the base station 900 may be provided as a network side device.
  • base station 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by memory 932 for storing instructions, such as application programs, executable by processing component 922.
  • the application program stored in memory 932 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 922 is configured to execute instructions to perform any of the foregoing methods applied to the base station.
  • Base station 900 may also include a power supply component 926 configured to perform power management of base station 900, a wired or wireless network interface 950 configured to connect base station 900 to a network, and an input/output (I/O) interface 958.
  • Base station 900 may operate based on an operating system stored in memory 932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种缓存状态报告上报方法、装置、退信设备及存储介质；用户设备(UE)针对具有紧急调度需求的上行数据，上报缓存状态报告(BSR)。

Description

一种缓存状态报告上报方法、装置、通信设备及存储介质 技术领域
本公开涉及但不限于通信技术领域，尤其涉及一种缓存状态报告上报方法、装置、通信设备及存储介质。
背景技术
扩展现实(Extended Reality，XR)业务中，通常XR业务数据有多个数据流(Qos flow)构成，其业务数据量非常大。而XR的业务流在传输过程中是需要满足一定的时延需求的，尤其是有些数据流需要同时到达服务器进行解码。其中任何一个数据流的延迟将会导致多个数据流的联合解码失败。
发明内容
本公开实施例公开一种缓存状态报告上报方法、装置、通信设备及存储介质。
根据本公开的第一方面，提供一种缓存状态报告上报方法，其中，被用户设备UE执行，包括：
针对具有紧急调度需求的上行数据，上报缓存状态报告BSR。
在一个实施例中，所述针对具有紧急调度需求的上行数据，上报BSR包括：
将具有紧急调度需求的所述上行数据对应的逻辑信道确定为最高优先级，并基于所述逻辑信道的优先级上报所述BSR。
在一个实施例中，所述针对具有紧急调度需求的上行数据，上报BSR包括：
响应于逻辑信道具有紧急调度需求的所述上行数据，触发上报所述逻辑信道的所述BSR。
在一个实施例中，所述针对具有紧急调度需求的上行数据，上报BSR包括：
响应于至少一个逻辑信道具有紧急调度需求的所述上行数据，触发第一逻辑信道的第一类BSR，其中，所述第一类BSR的优先级高于第二类BSR，并且所述第一逻辑信道为所述至少一个逻辑信道中优先级最高的逻辑信道。
在一个实施例中，所述针对具有紧急调度需求的上行数据，上报BSR包括：
响应于逻辑信道具有紧急调度需求的所述上行数据，确定所述逻辑信道具有第一最高优先级，基于所述第一最高优先级上报所述BSR，其中，所述第一最高优先级高于第二最高优先级。
在一个实施例中，所述上行数据，包括：扩展现实XR业务上行数据。
在一个实施例中，所述具有紧急调度需求的上行数据，包括：剩余数据包延迟预算小于的延迟阈值的所述上行数据。
在一个实施例中，所述延迟阈值的配置粒度包括以下一项：
UE粒度；
逻辑信道粒度；
逻辑信道组粒度。
在一个实施例中，所述具有紧急调度需求的所述上行数据，是数据包粒度的；
或者，
所述具有紧急调度需求的所述上行数据，是数据包集合粒度的。
在一个实施例中，所述方法还包括：
根据从非接入层或者应用层获取的第一指示信息，确定所述上行数据具有紧急调度需求。
在一个实施例中，所述针对具有紧急调度需求的上行数据，上报BSR，包括：
根据基站发送的第二指示信息的指示，针对具有紧急调度需求的所述上行数据，上报所述BSR。
在一个实施例中，所述第二指示信息包括：所述上行数据的剩余数据包延迟预算所关联的延迟阈值。
在一个实施例中，所述根据基站发送的第二指示信息的指示，针对具有紧急调度需求的所述上行数据，上报所述BSR，包括以下一项：
根据所述第二指示信息的指示，针对所述UE具有紧急调度需求的所述上行数据，上报所述BSR；
根据所述第二指示信息的指示，针对预定逻辑信道具有紧急调度需求的所述上行数据，上报所述BSR；
根据所述第二指示信息的指示，针对预定逻辑信道组具有紧急调度需求的所述上行数据，上报所述BSR。
在一个实施例中，所述方法还包括：
向基站发送辅助信息，所述辅助信息用于指示：所述UE能够针对具有紧急调度需求的所述上行数据上报所述BSR。
根据本公开的第二方面，提供一种缓存状态报告上报方法，其中，被基站执行，包括：
接收缓存状态报告BSR，其中，所述BSR是用户设备UE针对具有紧急调度需求的上行数据发送的。
在一个实施例中，所述BSR是所述UE将具有紧急调度需求的所述上行数据对应的逻辑信道确定为最高优先级，并基于所述逻辑信道的优先级上报的。
在一个实施例中，所述BSR是所述UE响应于逻辑信道具有紧急调度需求的所述上行数据，触发上报的。
在一个实施例中，上报的所述BSR包括：第一类BSR，所述第一类BSR关联于第一逻辑信道；
所述第一类BSR是所述UE响应于至少一个逻辑信道具有紧急调度需求的所述上行数据，并且第一逻辑信道为所述至少一个逻辑信道中优先级最高的逻辑信道触发上报的，其中，所述第一类BSR的优先级高于第二类BSR。
在一个实施例中，
所述BSR是所述UE响应于逻辑信道具有紧急调度需求的所述上行数据，确定所述逻辑信道具有第一最高优先级，并基于所述第一最高优先级上报的，其中，所述第一最高优先级高于第二最高优先级。
在一个实施例中，所述上行数据，包括：扩展现实XR业务上行数据。
在一个实施例中，所述具有紧急调度需求的上行数据，包括：剩余数据包延迟预算小于的延迟阈值的所述上行数据。
在一个实施例中，所述延迟阈值的配置粒度包括以下一项：
UE粒度；
逻辑信道粒度；
逻辑信道组粒度。
在一个实施例中，所述具有紧急调度需求的所述上行数据，是数据包粒度的；
或者，
所述具有紧急调度需求的所述上行数据，是数据包集合粒度的。
在一个实施例中，所述方法还包括：
向所述UE发送第二指示信息，其中，所述第二指示信息用于指示所述UE针对具有紧急调度需求的所述上行数据，上报所述BSR。
在一个实施例中，所述第二指示信息包括：所述上行数据的剩余数据包延迟预算所关联的延迟阈值。
在一个实施例中，所述第二指示信息，用于指示以下一项：
针对所述UE具有紧急调度需求的所述上行数据上报所述BSR；
针对预定逻辑信道具有紧急调度需求的所述上行数据上报所述BSR；
针对预定逻辑信道组具有紧急调度需求的所述上行数据上报所述BSR。
在一个实施例中，所述向所述UE发送第二指示信息，包括：
响应于接收到所述UE发送的辅助信息，向所述UE发送所述第二指示信息，其中，所述辅助信息用于指示：所述UE能够针对具有紧急调度需求的所述上行数据上报所述BSR。
根据本公开的第三方面，提供一种缓存状态报告上报装置，其中，设置于用户设备UE中，包括：
收发模块，配置为针对具有紧急调度需求的上行数据，上报缓存状态报告BSR。
在一个实施例中，所述收发模块，具体配置为：
将具有紧急调度需求的所述上行数据对应的逻辑信道确定为最高优先级，并基于所述逻辑信道的优先级上报所述BSR。
在一个实施例中，所述收发模块，具体配置为：
响应于逻辑信道具有紧急调度需求的所述上行数据，触发上报所述逻辑信道的所述BSR。
在一个实施例中，所述收发模块，具体配置为：
响应于至少一个逻辑信道具有紧急调度需求的所述上行数据，触发第一逻辑信道的第一类BSR，其中，所述第一类BSR的优先级高于第二类BSR，并且所述第一逻辑信道为所述至少一个逻辑信道中优先级最高的逻辑信道。
在一个实施例中，所述收发模块，具体配置为：
响应于逻辑信道具有紧急调度需求的所述上行数据，确定所述逻辑信道具有第一最高优先级，基于所述第一最高优先级上报所述BSR，其中，所述第一最高优先级高于第二最高优先级。
在一个实施例中，所述上行数据，包括：扩展现实XR业务上行数据。
在一个实施例中，所述具有紧急调度需求的上行数据，包括：剩余数据包延迟预算小于的延迟阈值的所述上行数据。
在一个实施例中，所述延迟阈值的配置粒度包括以下一项：
UE粒度；
逻辑信道粒度；
逻辑信道组粒度。
在一个实施例中，所述具有紧急调度需求的所述上行数据，是数据包粒度的；
或者，
所述具有紧急调度需求的所述上行数据，是数据包集合粒度的。
在一个实施例中，所述装置还包括：
处理模块，配置为根据从非接入层或者应用层获取的第一指示信息，确定所述上行数据具有紧急调度需求。
在一个实施例中，所述收发模块，具体配置为：
根据基站发送的第二指示信息的指示，针对具有紧急调度需求的所述上行数据，上报所述BSR。
在一个实施例中，所述第二指示信息包括：所述上行数据的剩余数据包延迟预算所关联的延迟阈值。
在一个实施例中，所述收发模块，具体配置为以下一项：
根据所述第二指示信息的指示，针对所述UE具有紧急调度需求的所述上行数据，上报所述BSR；
根据所述第二指示信息的指示，针对预定逻辑信道具有紧急调度需求的所述上行数据，上报所述BSR；
根据所述第二指示信息的指示，针对预定逻辑信道组具有紧急调度需求的所述上行数据，上报所述BSR。
在一个实施例中，所述收发模块，还配置为：
向基站发送辅助信息，所述辅助信息用于指示：所述UE能够针对具有紧急调度需求的所述上行数据上报所述BSR。
根据本公开的第四方面，提供一种缓存状态报告上报装置，其中，设置于基站中，包括：
收发模块，配置为：接收缓存状态报告BSR，其中，所述BSR是用户设备UE针对具有紧急调度需求的上行数据发送的。
在一个实施例中，所述BSR是所述UE将具有紧急调度需求的所述上行数据对应的逻辑信道确定为最高优先级，并基于所述逻辑信道的优先级上报的。
在一个实施例中，所述BSR是所述UE响应于逻辑信道具有紧急调度需求的所述上行数据，触发上报的。
在一个实施例中，上报的所述BSR包括：第一类BSR，所述第一类BSR关联于第一逻辑信道；
所述第一类BSR是所述UE响应于至少一个逻辑信道具有紧急调度需求的所述上行数据，并且第一逻辑信道为所述至少一个逻辑信道中优先级最高的逻辑信道触发上报的，其中，所述第一类BSR的优先级高于第二类BSR。
在一个实施例中，所述BSR是所述UE响应于逻辑信道具有紧急调度需求的所述上行数据，确定所述逻辑信道具有第一最高优先级，并基于所述第一最高优先级上报的，其中，所述第一最高优先级高于第二最高优先级。
在一个实施例中，所述上行数据，包括：扩展现实XR业务上行数据。
在一个实施例中，所述具有紧急调度需求的上行数据，包括：剩余数据包延迟预算小于的延迟阈值的所述上行数据。
在一个实施例中，所述延迟阈值的配置粒度包括以下一项：
UE粒度；
逻辑信道粒度；
逻辑信道组粒度。
在一个实施例中，所述具有紧急调度需求的所述上行数据，是数据包粒度的；
或者，
所述具有紧急调度需求的所述上行数据，是数据包集合粒度的。
在一个实施例中，所述收发模块还配置为：
向所述UE发送第二指示信息，其中，所述第二指示信息用于指示所述UE针对具有紧急调度需求的所述上行数据，上报所述BSR。
在一个实施例中，所述第二指示信息包括：所述上行数据的剩余数据包延迟预算所关联的延迟阈值。
在一个实施例中，所述第二指示信息，用于指示以下一项：
针对所述UE具有紧急调度需求的所述上行数据上报所述BSR；
针对预定逻辑信道具有紧急调度需求的所述上行数据上报所述BSR；
针对预定逻辑信道组具有紧急调度需求的所述上行数据上报所述BSR。
在一个实施例中，所述收发模块，具体配置为：
响应于接收到所述UE发送的辅助信息，向所述UE发送所述第二指示信息，其中，所述辅助信 息用于指示：所述UE能够针对具有紧急调度需求的所述上行数据上报所述BSR。
根据本公开的第五方面，提供一种通信设备，其中，所述通信设备，包括：
处理器；
用于存储所述处理器可执行指令的存储器；
其中，所述处理器被配置为：用于运行所述可执行指令时，实现第一方面或第二方面所述的缓存状态报告上报方法。
根据本公开的第六方面，提供一种计算机存储介质，其中，所述计算机存储介质存储有计算机可执行程序，所述可执行程序被处理器执行时实现第一方面或第二方面所述的缓存状态报告上报方法。
在本公开实施例中，UE针对具有紧急调度需求的上行数据，上报BSR。如此，针对具有紧急调度需求的上行数据，上报BSR，可以实现及时调度具有紧急调度需求的上行数据，满足通信业务需求，减小联合解码失败等数据传输错误的情况，提高通信可靠性。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开实施例。
附图说明
图1是一种无线通信系统的结构示意图。
图2是根据一示例性实施例示出的一种缓存状态报告上报方法的流程图。
图3是根据一示例性实施例示出的一种缓存状态报告上报方法的流程图。
图4是根据一示例性实施例示出的一种缓存状态报告上报方法的流程图。
图5是根据一示例性实施例示出的一种缓存状态报告上报方法的流程图。
图6是根据一示例性实施例示出的一种缓存状态报告上报方法的流程图。
图7是根据一示例性实施例示出的一种缓存状态报告上报方法的流程图。
图8是根据一示例性实施例示出的一种缓存状态报告上报方法的流程图。
图9是根据一示例性实施例示出的一种缓存状态报告上报方法的流程图。
图10是根据一示例性实施例示出的一种缓存状态报告上报方法的流程图。
图11是根据一示例性实施例示出的一种缓存状态报告上报方法的流程图。
图12是根据一示例性实施例示出的一种缓存状态报告上报装置的框图。
图13是根据一示例性实施例示出的一种缓存状态报告上报装置的框图。
图14是根据一示例性实施例示出的一种UE的框图。
图15是根据一示例性实施例示出的一种基站的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
请参考图1，其示出了本公开实施例提供的一种无线通信系统的结构示意图。如图1所示，无线通信系统是基于蜂窝移动通信技术的通信系统，该无线通信系统可以包括：若干个用户设备110以及若干个基站120。
其中，用户设备110可以是指向用户提供语音和/或数据连通性的设备。用户设备110可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，用户设备110可以是物联网用户设备，如传感器设备、移动电话(或称为“蜂窝”电话)和具有物联网用户设备的计算机，例如，可以是固定式、便携式、袖珍式、手持式、计算机内置的或者车载的装置。例如，站(Station，STA)、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点、远程用户设备(remote terminal)、接入用户设备(access terminal)、用户装置(user terminal)、用户代理(user agent)、用户设备(user device)、或用户设备(user equipment)。或者，用户设备110也可以是无人飞行器的设备。或者，用户设备110也可以是车载设备，比如，可以是具有无线通信功能的行车电脑，或者是外接行车电脑的无线用户设备。或者，用户设备110也可以是路边设备，比如，可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
基站120可以是无线通信系统中的网络侧设备。其中，该无线通信系统可以是第四代移动通信技术(the 4th generation mobile communication，4G)系统，又称长期演进(Long Term Evolution，LTE)系统；或者，该无线通信系统也可以是5G系统，又称新空口系统或5G NR系统。或者，该无线通信系统也可以是5G系统的再下一代系统。其中，5G系统中的接入网可以称为新一代无线接入网(New Generation-Radio Access Network，NG-RAN)。
其中，基站120可以是4G系统中采用的演进型基站(eNB)。或者，基站120也可以是5G系统中采用集中分布式架构的基站(gNB)。当基站120采用集中分布式架构时，通常包括集中单元(central unit，CU)和至少两个分布单元(distributed unit，DU)。集中单元中设置有分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、媒体接入控制(Medium Access Control，MAC)层的协议栈；分布单元中设置有物理(Physical，PHY)层协议栈，本公开实施例对基站120的具体实现方式不加以限定。
基站120和用户设备110之间可以通过无线空口建立无线连接。在不同的实施方式中，该无线空口是基于第四代移动通信网络技术(4G)标准的无线空口；或者，该无线空口是基于第五代移动通信网络技术(5G)标准的无线空口，比如该无线空口是新空口；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
在一些实施例中，用户设备110之间还可以建立E2E(End to End，端到端)连接。比如车联网通信(vehicle to everything，V2X)中的车对车(vehicle to vehicle，V2V)通信、车对路边设备(vehicle to Infrastructure，V2I)通信和车对人(vehicle to pedestrian，V2P)通信等场景。
这里，上述用户设备可认为是下面实施例的终端设备。
在一些实施例中，上述无线通信系统还可以包含网络管理设备130。
若干个基站120分别与网络管理设备130相连。其中，网络管理设备130可以是无线通信系统中的核心网设备，比如，该网络管理设备130可以是演进的数据分组核心网(Evolved Packet Core，EPC)中的移动性管理实体(Mobility Management Entity，MME)。或者，该网络管理设备也可以是其它的核心网设备，比如服务网关(Serving GateWay，SGW)、公用数据网网关(Public Data Network GateWay，PGW)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)或者归属签约用户服务器(Home Subscriber Server，HSS)等。对于网络管理设备130的实现形态，本公开实施例不做限定。
为了便于本领域内技术人员理解，本公开实施例列举了多个实施方式以对本公开实施例的技术方案进行清晰地说明。当然，本领域内技术人员可以理解，本公开实施例提供的多个实施例，可以被单独执行，也可以与本公开实施例中其他实施例的方法结合后一起被执行，还可以单独或结合后与其他相关技术中的一些方法一起被执行；本公开实施例并不对此作出限定。
网络针对数据流的调度是动态的，在有些情况下，即便有些数据流属于低优先级别的逻辑信道，但是若该数据包已经很长时间没有得到调度，则需要发送BSR尽快通知网络，以满足XR业务对于多数据流的需求。但是，根据现有机制，只有具有高优先级别逻辑信道有数据到达才能发送BSR，此时就无法满足紧急调度的需求。
因此，如何调度具有紧急调度需求的数据，满足通信业务需求，减小联合解码失败等数据传输错误的情况，是亟待解决的问题。
如图2所示，本公开实施例提供一种缓存状态报告上报方法，由UE执行，包括：
步骤201：针对具有紧急调度需求的上行数据，上报BSR。
在一个可能的实现方式中，具有紧急调度需求的上行数据可以包括以下一项：具有优先调度需求的上行数据，具有较高调度需求的上行数据。
具有紧急调度需求的数据也可以为需要进行优先调度需求的上行数据；还可以是网络或者终端确定的需要及时发送的上行数据。
具有紧急调度需求的数据还可以基于特定数据的业务特性确定的。例如，可以基于上行数据的重要性确定上行数据是否为具有紧急调度需求。比如I帧数据比P帧数据更加重要，可以确定I帧数据具有紧急调度需求。
在一个可能的实现方式中，具有紧急调度需求的上行数据可以是可以距离最晚发送时限的时间间隔小于预定时长阈值的上行数据。
示例性的，具有紧急调度需求的上行数据可以是多个进行联合解码的数据流中的一个。由于多个数据流需要联合解码，因此，如果其中一个数据流没有在预定的解码时刻之前到达，那么会使得解码失败。
在一个可能的实现方式中，具有紧急调度需求的上行数据可以由以下至少一项确定：
通信协议规定；
UE与网络侧商定，其中，网络侧包括：基站等接入网设备，和/或核心网设备。
相关技术中，只有具有高优先级别逻辑信道有数据到达才能发送BSR，因此，具有紧急调度需求的上行数据的逻辑信道如果不具有高优先级别，则无法发送BSR此时就无法满足具有紧急调度需求的上行数据的需求。
这里，可以针对具有紧急调度需求的上行数据，上报缓存状态报告BSR，包括：当逻辑信道有具有紧急调度需求的上行数据到达，UE可以向基站发送BSR。这里，逻辑信道可以具有高优先级或不具有高优先级。
在一个可能的实现方式中，BSR包括：常规BSR，填充(Padding)BSR，重传的BSR。
如此，针对具有紧急调度需求的上行数据，上报BSR，可以实现及时调度具有紧急调度需求的上行数据，满足通信业务需求，减小联合解码失败等数据传输错误的情况，提高通信可靠性。
在一个实施例中，所述上行数据，包括：扩展现实XR业务上线数据。
通常XR业务数据有多个数据流(Qos flow)构成，其业务数据量非常大。而XR的业务流在传输过程中是需要满足一定的时延需求的，尤其是有些数据流需要在预定时间范围内到达服务器进行解码。其中任何一个数据流的延迟将会导致多个数据流的联合解码失败。因此，UE可以针对具有紧急调度需求的XR业务上行数据，发送BSR，可以实现及时调度，满足XR业务的需求，减小联合解码失败等数据传输错误的情况。
在一个实施例中，所述具有紧急调度需求的上行数据，包括：剩余数据包延迟预算小于的延迟阈值的所述上行数据。
上行数据可以具有数据包延迟预算，即在数据包延迟预算范围内进行传输可以满足上行数据传输时间需求。剩余数据包延迟预算可以是当前时刻与数据包延迟预算的结束时刻的时间差。剩余数 据包延迟预算即为上行数据能够被正确传输和/或解码的剩余时长。
当上行数据的剩余数据包延迟预算小于的延迟阈值，UE可以针对该上行数据，发送BSR，实现及时调度，满足数据业务的需求。
示例性的，剩余数据包延迟预算(the time left until exceeding the PDB)小于某个延迟阈值(比如判决该数据包的剩余数据包延迟预算小于10ms；延迟阈值可以协议约定或者从网络通知获得。PDB(packet delay buget，数据包延迟预算)的配置粒度可以是针对单个数据包，也可以是针对数据包集合)。
终端可以预估哪些数据包的PDB已经接近用完，还没有调度出去，因此需要进行优先调度。较高调度紧急需求的数据可以基于数据包(Packet)统计或者针对数据包集合(Packet set)进行统计。
在一个实施例中，所述延迟阈值的配置粒度包括以下一项：
UE粒度；
逻辑信道粒度；
逻辑信道组粒度。
在一个可能的实现方式中，延迟阈值可以是通信协议约定的，也可以是基站等网络侧设备向UE指示的。
UE粒度的延迟阈值，可以是指UE的所有上行数据，均可以采用该延迟阈值判断是否为具有紧急调度需求的上行数据。
逻辑信道粒度的延迟阈值，可以是指在该逻辑信道内传输的上行数据，均可以采用该延迟阈值判断是否为具有紧急调度需求的上行数据。
逻辑信道组粒度的延迟阈值，可以是指在该逻辑信道组内传输的上行数据，均可以采用该延迟阈值判断是否为具有紧急调度需求的上行数据。
在一个实施例中，所述具有紧急调度需求的所述上行数据，是数据包粒度的；
或者，
所述具有紧急调度需求的所述上行数据，是数据包集合粒度的。
上行数据可以基于数据包或者基于数据包集合(Packet set)进行统计，并确定是否为具有紧急调度需求的上行数据。基于基于数据包或者基于数据包集合进行统计可以提高统计的灵活性，满足不同形式上行数据传输的需求。
如图3所示，本公开实施例提供一种缓存状态报告上报方法，由UE执行，包括：
步骤301：根据从非接入层或者应用层获取的第一指示信息，确定所述上行数据具有紧急调度需求。
在一个可能的实施方式中，具有紧急调度需求的上行数据是第一指示信息指示的。第一指示信息可以由核心网等网络设备通过非接入层或者应用层发送给UE。
示例性的，第一指示信息指示的具有紧急调度需求的上行数据是数据包粒度的或者是数据包集合粒度的。
如图4所示，本公开实施例提供一种缓存状态报告上报方法，由UE执行，包括：
步骤401：根据基站发送的第二指示信息的指示，针对具有紧急调度需求的所述上行数据，上报所述BSR。
基站通过第二指示信息通知UE使能针对具有紧急调度需求的所述上行数据，上报所述BSR。
在一个可能的实现方式中，第二指示信息可以携带于RRC和/或DCI等专用信令中，发送给UE。
在一个实施例中，所述根据基站发送的第二指示信息的指示，针对具有紧急调度需求的所述上行数据，上报所述BSR，包括以下一项：
根据所述第二指示信息的指示，针对所述UE具有紧急调度需求的所述上行数据，上报所述BSR；
根据所述第二指示信息的指示，针对预定逻辑信道具有紧急调度需求的所述上行数据，上报所述BSR；
根据所述第二指示信息的指示，针对预定逻辑信道组具有紧急调度需求的所述上行数据，上报所述BSR。
第二指示信息可以指示的针对具有紧急调度需求的所述上行数据发送给UE可以是UE粒度的，也可以是逻辑信道粒度的，还可以是逻辑信道组粒度的。
具体的，第二指示信息对应于UE粒度时，UE针对UE的具有紧急调度需求的所述上行数据，上报所述BSR。
示例性的，若基站知晓UE为进行XR业务的UE，第二指示信息对应于UE粒度；
具体的，第二指示信息对应于逻辑信道组粒度时，UE针对指定逻辑信道组的具有紧急调度需求的所述上行数据，上报所述BSR。
示例性的，若基站知晓UE为进行XR业务的UE，则通知其对于特定的LCG其将使能针对具有紧急调度需求的上行数据，上报BSR；
具体的，第二指示信息对应于逻辑信道粒度时，UE针对指定逻辑信道的具有紧急调度需求的所述上行数据，上报所述BSR。
在一个可能的实现方式中，第二指示信息同时可以指示使能针对具有紧急调度需求的所述上行数据上报所述BSR的以下至少之一项：UE；逻辑信道；逻辑信道组。
示例性的，若基站知晓UE为进行XR业务的UE，则第二指示信息通知其对于特定的逻辑信道使能针对具有紧急调度需求的上行数据，上报BSR；
在一个实施例中，所述第二指示信息包括：所述上行数据的剩余数据包延迟预算所关联的延迟阈值。
在一个可能的实现方式中，第二指示信息可以显式指示UE针对指定逻辑信道组的具有紧急调度需求的所述上行数据，上报所述BSR。
在一个可能的实现方式中，第二指示信息可以隐含指示UE针对指定逻辑信道组的具有紧急调度需求的所述上行数据，上报所述BSR。
在一个可能的实现方式中，第二指示信息指示上行数据的剩余数据包延迟预算所关联的延迟阈 值，以隐含指示UE针对指定逻辑信道组的具有紧急调度需求的所述上行数据，上报所述BSR。
第二指示信息指示的延迟阈值的粒度可以包括以下之一：UE粒度；逻辑信道粒度；逻辑信道组粒度。
示例性的，若网络通知了针对某个逻辑信道的延迟阈值，则意味着使能针对具有紧急调度需求的上行数据，上报BSR的功能。
如图5所示，本公开实施例提供一种缓存状态报告上报方法，由UE执行，包括：
步骤501：向基站发送辅助信息，所述辅助信息用于指示：所述UE能够针对具有紧急调度需求的所述上行数据上报所述BSR。
在一个可能的实现方式中，UE的辅助信息包括UE是否支持针对具有紧急调度需求的所述上行数据上报所述BSR的能力。
在一个可能的实现方式中，UE的辅助信息包括UE是否期望使用针对具有紧急调度需求的所述上行数据上报所述BSR的功能。
如图6所示，本公开实施例提供一种缓存状态报告上报方法，由UE执行，包括：
步骤601：将具有紧急调度需求的所述上行数据对应的逻辑信道确定为最高优先级，并基于所述逻辑信道的优先级上报所述BSR。
这里，针对具有紧急调度需求的所述上行数据对应的逻辑信道，可以将该信道设置为最高优先级。如此，可以由UE基于逻辑信道的优先级，优先触发中UE上报该逻辑信道的BSR，及时进行调度，满足通信业务的需求，减小联合解码失败等数据传输错误的情况。
示例性的，逻辑信道的最高优先级可以为“1”，如果逻辑信道中具有具有紧急调度需求的所述上行数据，那么可以将该逻辑信道的优先级确定为“1”。该逻辑信道可以和其他具有优先级“1”的信道具有相同的传输优先级。
示例性的，在常规BSR触发时，需要考虑到该类型的逻辑信道的优先级别为最高优先级别；(比如LCH1有数据发送，LCH2有新数据到达，即便LCH2的逻辑信道优先级别更低，但是因为LCH2有紧急调度数据到达，则LCH2逻辑信道优先级别高于LCH1，也将针对LCH2可以触发常规BSR)。如此具有紧急调度需求的数据的逻辑信道能够及时触发BSR。
示例性的，在填充(Padding)BSR上报时，若需要进行截短BSR上报，则需要考虑到该类型的逻辑信道的优先级别为最高逻辑信道优先级别；(比如LCH1有数据发送，LCH2有数据发送，即便LCH2的逻辑信道优先级别更低，但是因为有紧急调度数据到达，则其优先级别高于LCH1，则截短端BSR(Short Truncated BSR)中因为仅能携带一个LCG，则将携带触发LCH2的LCG ID)
示例性的，在BSR重传定时器超时，需要考虑较高调度紧急需求的数据的所在的逻辑信道置为最高优先级别；(比如LCH1触发了BSR上报，则重传定时器超时时候，LCH1将被认为是最高逻辑信道，即便LCH2的逻辑信道优先级别更低，但是因为有紧急调度数据到达，则也视为LCH2为最高优先级别)
如图7所示，本公开实施例提供一种缓存状态报告上报方法，由UE执行，包括：
步骤701：响应于逻辑信道具有紧急调度需求的所述上行数据，触发上报所述逻辑信道的所述BSR。
这里，逻辑信道的BSR可以由具有紧急调度需求的上行数据触发。
示例性的，当逻辑信道到达具有紧急调度需求的所述上行数据，那么UE触发逻辑信道关联的BSR，对到达的具有紧急调度需求的所述上行数据进行调度。
示例性的，如果激活的小区组发生以下任一事件，则应触发BSR：
-属于逻辑信道组(LCG)的逻辑信道的上行数据对MAC实体可用；并且：
1.该上行数据属于一个逻辑信道，该逻辑信道的优先级高于任何逻辑信道组中具有上行数据的逻辑信道的优先级；或者
2.属于逻辑信道组的逻辑信道都不包含任何可用的UL数据；或者
3.对于属于逻辑信道组的逻辑信道到达的可用数据成为具有紧急调度需求即需要尽快调度或者具有严格延迟预算(stringent delay buget)
这里，BSR可以是常规BSR。
示例性的，修改了相关技术中的常规BSR触发的条件，增加了一个触发条件：该逻辑信道中存在紧急调度数据需求即触发。即存在紧急调度数据需求的数据则可以触发。
示例性的，修改了相关技术中的常规BSR触发的条件，增加了一个触发条件：该逻辑信道中存在紧急调度数据需求的数据从无到有即触发。相比于前一个实施例，该方式可以避免该类BSR的频繁触发。
如图8所示，本公开实施例提供一种缓存状态报告上报方法，由UE执行，包括：
步骤801：响应于至少一个逻辑信道具有紧急调度需求的所述上行数据，触发第一逻辑信道的第一类BSR，其中，所述第一类BSR的优先级高于第二类BSR，并且所述第一逻辑信道为所述至少一个逻辑信道中优先级最高的逻辑信道。
第一类BSR不同于第二类BSR。
这里，第二类BSR可以是相关技术中采用的BSR，相关技术中的BSR可以分为若干不同优先级，而本公开实施例中的第一类BSR高于相关技术中采用的BSR中的任何优先级的BSR。例如，第二类BSR可以是在逻辑信道具有最高优先级时采用的BSR，而本公开实施例中的第一类BSR优先级高于该最高优先级。第一类BSR可以是针对具有紧急调度需求的上行数据的逻辑信道的BSR。
在一个可能的实现方式中，可以对具有紧急调度需求的上行数据的逻辑信道或逻辑信道组进行优先级排序，针对具有高优先级的逻辑信道或逻辑信道组上报第一类BSR。
在一个可能的实现方式中，第一类BSR的优先级高于第二类BSR。
第一类BSR可以是XR-BSR或者称之为优先权BSR，该BSR用于具有存在较高调度紧急需求的数据的逻辑信道或者逻辑信道组的优先传输；
在一个可能的实现方式中，若UE判决，若存在较高调度紧急需求的数据，则将该类逻辑信道属于的逻辑信道/逻辑信道组进行优先排序，组成优先权BSR。若授权有限即不足以传输排序后的所 有的LCG，则优先权BSR可以传输尽量多的排序后的LCG。
示例性的，
1>如果配置了剩余数据包延迟预算的延迟阈值(PdbThres)，并且任意LCG中逻辑信道包含的上行数据的剩余数据包延迟预算小于PdbThres，那么，
2>提高该LCG的优先级，即将存在快接近调度预算门限的LCG进行优先；
2>如果UL授权不能容纳仅包含所有优先LCG的缓冲区状态的SL-BSR MAC CE；
上报XR-BSR，XR-BSR中包含尽可能多的优先级LCG的缓冲区状态，这些LCG具有生效传输数据，同时考虑到上行(UL)授权中的比特数(即该新的BSR携带优先LCG)。
优先的BSR在进行逻辑信道优先级处理时：对于XR-BSR类型BRS或者优先权BSR的优先级别可以定义MAC CE for(Extended)BSR之前。示例性的，逻辑通道应按照以下顺序进行优先级排序(具有最高优先级的在前)：
·用于C-RNTI的MAC CE，或来自UL-CCCH的数据；
·用于(增强型)BFR的MAC CE，或用于配置的授权确认的MAC CE，或用于多条目配置的授权确认的MAC CE；
·用于Sidelink配置授权确认的MAC CE；
·用于LBT失败的MAC CE；
·用于定时提前报告的MAC CE；
·XR-BSR的MAC CE；
·根据第5.22.1.6节优先考虑的SL-BSR的MAC CE；
·用于(扩展)BSR的MAC CE，不包括用于填充(padding)的BSR；
·用于(增强的)单条目PHR的MAC CE，或用于(增强的)多条目PHR的MAC CE；
·用于定位测量间隙激活/停用请求的MAC CE；
·用于所需保护符号的数量de MAC CE；
·案例6定时请求的MAC CE；
·用于(扩展)抢先BSR的MAC CE；
·用于SL-BSR的MAC CE，但根据第5.22.1.6节优先考虑的SL-BSR和用于填充的SL-BSR除外；
·用于IAB-MT推荐波束指示的MAC CE，或用于所需IAB-MT PSD范围的MAC CE，或用于所需DL Tx功率调整的MAC CE；
·来自任何逻辑信道的数据，来自UL-CCCH的数据除外；
·用于推荐比特率查询的MAC CE；
·包括用于填充(padding)的BSR的MAC CE；
·包括用于填充(padding)的SL-BSR的MAC CE。
如图9所示，本公开实施例提供一种缓存状态报告上报方法，由UE执行，包括：
步骤901：响应于逻辑信道具有紧急调度需求的所述上行数据，确定所述逻辑信道具有第一最高优先级，基于所述第一最高优先级上报所述BSR，其中，所述第一最高优先级高于第二最高优先级。
这里，第二最高优先级可以是相关技术中逻辑信道的最高优先级，相关技术中逻辑信道可以分为不同优先级，第二最高优先级可以为相关技术中所有优先级中的最高优先级，同时，本公开实施例中的第一最高优先级高于该相关技术中的最高优先级(也即第二最高优先级)。这里，可以将具有紧急调度需求的所述上行数据的逻辑信道确定为具有第一最高优先级。UE可以基于优先级的级别进行BSR。
由于第一最高优先级高于第二最高优先级，因此，具有紧急调度需求的所述上行数据的逻辑信道具有更高的优先级别上报BSR，从而实现具有紧急调度需求的上行数据的及时调度，满足数据传输需求。
示例性的，可以针对具有紧急调度需求的上行数据的逻辑信道，引入一个比最高优先级(the highest priority)(即，第二最高优先级)级别更高的超级优先级(super priority)(即，第一最高优先级)。UE将具有紧急调度需求的所述上行数据的逻辑信道判定为处于比高级别逻辑信道优先级别更高的级别；
示例性的，在常规BSR触发时，若对于某个逻辑信道，若存在较高调度紧急需求的数据到达，则该类型数据的逻辑信道的优先级别高于其他任何一个LCG的任何一个逻辑信道；则会针对该逻辑信道对应的LCG触发常规BSR。如此，对于某个逻辑信道，若存在较高调度紧急需求的数据到达，可以触发常规BSR。
示例性的，对于填充(Padding)BSR需要进行截短上报的情况，则UE判决，若存在较高调度紧急需求的数据，则截短短BSR(Short Truncated BSR)中携带针对该逻辑信道的LCG ID上报(因为此时该逻辑信道为超级高优先级别)；若对于截短长BSR(Long Truncated BSR)，因为可以携带多个LCG信息，则可以将存在较高调度紧急需求的数据的逻辑信道的LCG ID放在最前头。如此，对于某个逻辑信道，若存在较高调度紧急需求的数据到达，则授权不够需要上报截断BSR时，可以触发该逻辑信道对应的LCG的优先上报。
示例性的，重传BSR定时器超时，UE将较高调度紧急需求的数据触发的重传BSR场景下优先传输；(因为此时该逻辑信道为超级高优先级别)；比如：LCH1和LCG2都触发了BSR重传上报，此时，LCH1，LCG2将被认为是最高逻辑信道，但是因为LCH2有紧急调度数据触发的BSR重传，此时也将优先上报携带传输LCH2的LCG的BSR。如此，对于某个逻辑信道，若存在较高调度紧急需求的数据的BSR重传时，该逻辑信道对应的LCG的优先上报。
如图10所示，本公开实施例提供一种缓存状态报告上报方法，由基站执行，包括：
步骤1001：接收BSR，其中，所述BSR是用户设备UE针对具有紧急调度需求的上行数据发送的。
在一个可能的实现方式中，具有紧急调度需求的上行数据可以包括以下一项：具有优先调度需 求的上行数据，具有较高调度需求的上行数据。
具有紧急调度需求的数据也可以为需要进行优先调度需求的上行数据；还可以是网络或者终端确定的需要及时发送的上行数据。
具有紧急调度需求的数据还可以基于特定数据的业务特性确定的。例如，可以基于上行数据的重要性确定上行数据是否为具有紧急调度需求。比如I帧数据比P帧数据更加重要，可以确定I帧数据具有紧急调度需求。
在一个可能的实现方式中，具有紧急调度需求的上行数据可以是可以距离最晚发送时限的时间间隔小于预定时长阈值的上行数据。
示例性的，具有紧急调度需求的上行数据可以是多个进行联合解码的数据流中的一个。由于多个数据流需要联合解码，因此，如果其中一个数据流没有在预定的解码时刻之前到达，那么会使得解码失败。
在一个可能的实现方式中，具有紧急调度需求的上行数据可以由以下至少一项确定：
通信协议规定；
UE与网络侧商定，其中，网络侧包括：基站等接入网设备，和/或核心网设备。
相关技术中，只有具有高优先级别逻辑信道有数据到达才能发送BSR，因此，具有紧急调度需求的上行数据的逻辑信道如果不具有高优先级别，则无法发送BSR此时就无法满足具有紧急调度需求的上行数据的需求。
这里，可以针对具有紧急调度需求的上行数据，上报缓存状态报告BSR，包括：当逻辑信道有具有紧急调度需求的上行数据到达，UE可以向基站发送BSR。这里，逻辑信道可以具有高优先级或不具有高优先级。
在一个可能的实现方式中，BSR包括：常规BSR，填充(Padding)BSR，重传的BSR。
如此，针对具有紧急调度需求的上行数据，上报BSR，可以实现及时调度具有紧急调度需求的上行数据，满足通信业务需求，减小联合解码失败等数据传输错误的情况，提高通信可靠性。
在一个实施例中，所述上行数据，包括：扩展现实XR业务上线数据。
通常XR业务数据有多个数据流(Qos flow)构成，其业务数据量非常大。而XR的业务流在传输过程中是需要满足一定的时延需求的，尤其是有些数据流需要在预定时间范围内到达服务器进行解码。其中任何一个数据流的延迟将会导致多个数据流的联合解码失败。因此，UE可以针对具有紧急调度需求的XR业务上行数据，发送BSR，可以实现及时调度，满足XR业务的需求，减小联合解码失败等数据传输错误的情况。
在一个实施例中，所述具有紧急调度需求的上行数据，包括：剩余数据包延迟预算小于的延迟阈值的所述上行数据。
上行数据可以具有数据包延迟预算，即在数据包延迟预算范围内进行传输可以满足上行数据传输时间需求。剩余数据包延迟预算可以是当前时刻与数据包延迟预算的结束时刻的时间差。剩余数据包延迟预算即为上行数据能够被正确传输和/或解码的剩余时长。
当上行数据的剩余数据包延迟预算小于的延迟阈值，UE可以针对该上行数据，发送BSR，实现及时调度，满足数据业务的需求。
示例性的，剩余数据包延迟预算(the time left until exceeding the PDB)小于某个延迟阈值(比如判决该数据包的剩余数据包延迟预算小于10ms；延迟阈值可以协议约定或者从网络通知获得。PDB(packet delay buget，数据包延迟预算)的配置粒度可以是针对单个数据包，也可以是针对数据包集合)。
终端可以预估哪些数据包的PDB已经接近用完，还没有调度出去，因此需要进行优先调度。较高调度紧急需求的数据可以基于数据包(Packet)统计或者针对数据包集合(Packet set)进行统计。
在一个实施例中，所述延迟阈值的配置粒度包括以下一项：
UE粒度；
逻辑信道粒度；
逻辑信道组粒度。
在一个可能的实现方式中，延迟阈值可以是通信协议约定的，也可以是基站等网络侧设备向UE指示的。
UE粒度的延迟阈值，可以是指UE的所有上行数据，均可以采用该延迟阈值判断是否为具有紧急调度需求的上行数据。
逻辑信道粒度的延迟阈值，可以是指在该逻辑信道内传输的上行数据，均可以采用该延迟阈值判断是否为具有紧急调度需求的上行数据。
逻辑信道组粒度的延迟阈值，可以是指在该逻辑信道组内传输的上行数据，均可以采用该延迟阈值判断是否为具有紧急调度需求的上行数据。
在一个实施例中，所述具有紧急调度需求的所述上行数据，是数据包粒度的；
或者，
所述具有紧急调度需求的所述上行数据，是数据包集合粒度的。
上行数据可以基于数据包或者基于数据包集合(Packet set)进行统计，并确定是否为具有紧急调度需求的上行数据。基于基于数据包或者基于数据包集合进行统计可以提高统计的灵活性，满足不同形式上行数据传输的需求。
如图11所示，本公开实施例提供一种缓存状态报告上报方法，由基站执行，包括：
步骤1101：向所述UE发送第二指示信息，其中，所述第二指示信息用于指示所述UE针对具有紧急调度需求的所述上行数据，上报所述BSR。
基站通过第二指示信息通知UE使能针对具有紧急调度需求的所述上行数据，上报所述BSR。
在一个可能的实现方式中，第二指示信息可以携带于RRC和/或DCI等专用信令中，发送给UE。
在一个实施例中，所述第二指示信息，用于指示以下一项：
针对所述UE具有紧急调度需求的所述上行数据上报所述BSR；
针对预定逻辑信道具有紧急调度需求的所述上行数据上报所述BSR；
针对预定逻辑信道组具有紧急调度需求的所述上行数据上报所述BSR。
第二指示信息可以指示的针对具有紧急调度需求的所述上行数据发送给UE可以是UE粒度的，也可以是逻辑信道粒度的，还可以是逻辑信道组粒度的。
具体的，第二指示信息对应于UE粒度时，UE针对UE的具有紧急调度需求的所述上行数据，上报所述BSR。
示例性的，若基站知晓UE为进行XR业务的UE，第二指示信息对应于UE粒度；
具体的，第二指示信息对应于逻辑信道组粒度时，UE针对指定逻辑信道组的具有紧急调度需求的所述上行数据，上报所述BSR。
示例性的，若基站知晓UE为进行XR业务的UE，则通知其对于特定的LCG其将使能针对具有紧急调度需求的上行数据，上报BSR；
具体的，第二指示信息对应于逻辑信道粒度时，UE针对指定逻辑信道的具有紧急调度需求的所述上行数据，上报所述BSR。
在一个可能的实现方式中，第二指示信息同时可以指示使能针对具有紧急调度需求的所述上行数据上报所述BSR的以下至少之一项：UE；逻辑信道；逻辑信道组。
示例性的，若基站知晓UE为进行XR业务的UE，则第二指示信息通知其对于特定的逻辑信道使能针对具有紧急调度需求的上行数据，上报BSR；
在一个实施例中，所述第二指示信息包括：所述上行数据的剩余数据包延迟预算所关联的延迟阈值。
在一个可能的实现方式中，第二指示信息可以显式指示UE针对指定逻辑信道组的具有紧急调度需求的所述上行数据，上报所述BSR。
在一个可能的实现方式中，第二指示信息可以隐含指示UE针对指定逻辑信道组的具有紧急调度需求的所述上行数据，上报所述BSR。
在一个可能的实现方式中，第二指示信息指示上行数据的剩余数据包延迟预算所关联的延迟阈值，以隐含指示UE针对指定逻辑信道组的具有紧急调度需求的所述上行数据，上报所述BSR。
第二指示信息指示的延迟阈值的粒度可以包括以下之一：UE粒度；逻辑信道粒度；逻辑信道组粒度。
示例性的，若网络通知了针对某个逻辑信道的延迟阈值，则意味着使能针对具有紧急调度需求的上行数据，上报BSR的功能。
在一个实施例中，所述向所述UE发送第二指示信息，包括：
响应于接收到所述UE发送的辅助信息，向所述UE发送所述第二指示信息，其中，所述辅助信息用于指示：所述UE能够针对具有紧急调度需求的所述上行数据上报所述BSR。
在一个可能的实现方式中，UE的辅助信息包括UE是否支持针对具有紧急调度需求的所述上行数据上报所述BSR的能力。
在一个可能的实现方式中，UE的辅助信息包括UE是否期望使用针对具有紧急调度需求的所述 上行数据上报所述BSR的功能。
基站确定UE针对具有紧急调度需求的所述上行数据上报所述BSR的能力和/或UE期望使用针对具有紧急调度需求的所述上行数据上报所述BSR的功能后，可以向UE发送第二指示信息。
在一个实施例中，所述BSR是所述UE将具有紧急调度需求的所述上行数据对应的逻辑信道确定为最高优先级，并基于所述逻辑信道的优先级上报的。
这里，针对具有紧急调度需求的所述上行数据对应的逻辑信道，可以将该信道设置为最高优先级。如此，可以由UE基于逻辑信道的优先级，优先触发中UE上报该逻辑信道的BSR，及时进行调度，满足通信业务的需求，减小联合解码失败等数据传输错误的情况。
示例性的，逻辑信道的最高优先级可以为“1”，如果逻辑信道中具有具有紧急调度需求的所述上行数据，那么可以将该逻辑信道的优先级确定为“1”。该逻辑信道可以和其他具有优先级“1”的信道具有相同的传输优先级。
示例性的，在常规BSR触发时，需要考虑到该类型的逻辑信道的优先级别为最高优先级别；(比如LCH1有数据发送，LCH2有新数据到达，即便LCH2的逻辑信道优先级别更低，但是因为LCH2有紧急调度数据到达，则LCH2逻辑信道优先级别高于LCH1，也将针对LCH2可以触发常规BSR)。如此具有紧急调度需求的数据的逻辑信道能够及时触发BSR。
示例性的，在填充(Padding)BSR上报时，若需要进行截短BSR上报，则需要考虑到该类型的逻辑信道的优先级别为最高逻辑信道优先级别；(比如LCH1有数据发送，LCH2有数据发送，即便LCH2的逻辑信道优先级别更低，但是因为有紧急调度数据到达，则其优先级别高于LCH1，则截短端BSR(Short Truncated BSR)中因为仅能携带一个LCG，则将携带触发LCH2的LCG ID)
示例性的，在BSR重传定时器超时，需要考虑较高调度紧急需求的数据的所在的逻辑信道置为最高优先级别；(比如LCH1触发了BSR上报，则重传定时器超时时候，LCH1将被认为是最高逻辑信道，即便LCH2的逻辑信道优先级别更低，但是因为有紧急调度数据到达，则也视为LCH2为最高优先级别)
在一个实施例中，所述BSR是所述UE响应于逻辑信道具有紧急调度需求的所述上行数据，触发上报的。
这里，逻辑信道的BSR可以由具有紧急调度需求的上行数据触发。
示例性的，当逻辑信道到达具有紧急调度需求的所述上行数据，那么UE触发逻辑信道关联的BSR，对到达的具有紧急调度需求的所述上行数据进行调度。
示例性的，如果激活的小区组发生以下任一事件，则应触发BSR：
-属于逻辑信道组(LCG)的逻辑信道的上行数据对MAC实体可用；并且：
1.该上行数据属于一个逻辑信道，该逻辑信道的优先级高于任何逻辑信道组中具有上行数据的逻辑信道的优先级；或者
2.属于逻辑信道组的逻辑信道都不包含任何可用的UL数据；或者
3.对于属于逻辑信道组的逻辑信道到达的可用数据成为具有紧急调度需求即需要尽快调 度或者具有严格延迟预算(stringent delay buget)
这里，BSR可以是常规BSR。
示例性的，修改了相关技术中的常规BSR触发的条件，增加了一个触发条件：该逻辑信道中存在紧急调度数据需求即触发。即存在紧急调度数据需求的数据则可以触发。
示例性的，修改了相关技术中的常规BSR触发的条件，增加了一个触发条件：该逻辑信道中存在紧急调度数据需求的数据从无到有即触发。相比于前一个实施例，该方式可以避免该类BSR的频繁触发。
在一个实施例中，上报的所述BSR包括：第一类BSR，所述第一类BSR关联于第一逻辑信道；
所述第一类BSR是所述UE响应于至少一个逻辑信道具有紧急调度需求的所述上行数据，并且第一逻辑信道为所述至少一个逻辑信道中优先级最高的逻辑信道触发上报的，其中，所述第一类BSR的优先级高于第二类BSR。
第一类BSR不同于第二类BSR。
这里，第二类BSR可以是相关技术中采用的BSR，相关技术中的BSR可以分为若干不同优先级，而本公开实施例中的第一类BSR高于相关技术中采用的BSR中的任何优先级的BSR。例如，第二类BSR可以是在逻辑信道具有最高优先级时采用的BSR，而本公开实施例中的第一类BSR优先级高于该最高优先级。第一类BSR可以是针对具有紧急调度需求的上行数据的逻辑信道的BSR。
在一个可能的实现方式中，可以对具有紧急调度需求的上行数据的逻辑信道或逻辑信道组进行优先级排序，针对具有高优先级的逻辑信道或逻辑信道组上报第一类BSR。
在一个可能的实现方式中，第一类BSR的优先级高于第二类BSR。
第一类BSR可以是XR-BSR或者称之为优先权BSR，该BSR用于具有存在较高调度紧急需求的数据的逻辑信道或者逻辑信道组的优先传输；
在一个可能的实现方式中，若UE判决，若存在较高调度紧急需求的数据，则将该类逻辑信道属于的逻辑信道/逻辑信道组进行优先排序，组成优先权BSR。若授权有限即不足以传输排序后的所有的LCG，则优先权BSR可以传输尽量多的排序后的LCG。
示例性的，
1>如果配置了剩余数据包延迟预算的延迟阈值(PdbThres)，并且任意LCG中逻辑信道包含的上行数据的剩余数据包延迟预算小于PdbThres，那么，
2>提高该LCG的优先级，即将存在快接近调度预算门限的LCG进行优先；
2>如果UL授权不能容纳仅包含所有优先LCG的缓冲区状态的SL-BSR MAC CE；
上报XR-BSR，XR-BSR中包含尽可能多的优先级LCG的缓冲区状态，这些LCG具有生效传输数据，同时考虑到上行(UL)授权中的比特数(即该新的BSR携带优先LCG)。
优先的BSR在进行逻辑信道优先级处理时：对于XR-BSR类型BRS或者优先权BSR的优先级别可以定义MAC CE for(Extended)BSR之前。示例性的，逻辑通道应按照以下顺序进行优先级排序(具有最高优先级的在前)：
·用于C-RNTI的MAC CE，或来自UL-CCCH的数据；
·用于(增强型)BFR的MAC CE，或用于配置的授权确认的MAC CE，或用于多条目配置的授权确认的MAC CE；
·用于Sidelink配置授权确认的MAC CE；
·用于LBT失败的MAC CE；
·用于定时提前报告的MAC CE；
·XR-BSR的MAC CE；
·根据第5.22.1.6节优先考虑的SL-BSR的MAC CE；
·用于(扩展)BSR的MAC CE，不包括用于填充(padding)的BSR；
·用于(增强的)单条目PHR的MAC CE，或用于(增强的)多条目PHR的MAC CE；
·用于定位测量间隙激活/停用请求的MAC CE；
·用于所需保护符号的数量de MAC CE；
·案例6定时请求的MAC CE；
·用于(扩展)抢先BSR的MAC CE；
·用于SL-BSR的MAC CE，但根据第5.22.1.6节优先考虑的SL-BSR和用于填充的SL-BSR除外；
·用于IAB-MT推荐波束指示的MAC CE，或用于所需IAB-MT PSD范围的MAC CE，或用于所需DL Tx功率调整的MAC CE；
·来自任何逻辑信道的数据，来自UL-CCCH的数据除外；
·用于推荐比特率查询的MAC CE；
·包括用于填充(padding)的BSR的MAC CE；
·包括用于填充(padding)的SL-BSR的MAC CE。
在一个实施例中，
所述BSR是所述UE响应于逻辑信道具有紧急调度需求的所述上行数据，确定所述逻辑信道具有第一最高优先级，并基于所述第一最高优先级上报的，其中，所述第一最高优先级高于第二最高优先级。
这里，第二最高优先级可以是相关技术中逻辑信道的最高优先级，相关技术中逻辑信道可以分为不同优先级，第二最高优先级可以为相关技术中所有优先级中的最高优先级，同时，本公开实施例中的第一最高优先级高于该相关技术中的最高优先级(也即第二最高优先级)。这里，可以将具有紧急调度需求的所述上行数据的逻辑信道确定为具有第一最高优先级。UE可以基于优先级的级别进行BSR。
由于第一最高优先级高于第二最高优先级，因此，具有紧急调度需求的所述上行数据的逻辑信道具有更高的优先级别上报BSR，从而实现具有紧急调度需求的上行数据的及时调度，满足数据传输需求。
示例性的，可以针对具有紧急调度需求的上行数据的逻辑信道，引入一个比最高优先级(the highest priority)级别更高的超级优先级(super priority)。UE将具有紧急调度需求的所述上行数据的逻辑信道判定为处于比高级别逻辑信道优先级别更高的级别；
示例性的，在常规BSR触发时，若对于某个逻辑信道，若存在较高调度紧急需求的数据到达，则该类型数据的逻辑信道的优先级别高于其他任何一个LCG的任何一个逻辑信道；则会针对该逻辑信道对应的LCG触发常规BSR。如此，对于某个逻辑信道，若存在较高调度紧急需求的数据到达，可以触发常规BSR。
示例性的，对于填充(Padding)BSR需要进行截短上报的情况，则UE判决，若存在较高调度紧急需求的数据，则截短短BSR(Short Truncated BSR)中携带针对该逻辑信道的LCG ID上报(因为此时该逻辑信道为超级高优先级别)；若对于截短长BSR(Long Truncated BSR)，因为可以携带多个LCG信息，则可以将存在较高调度紧急需求的数据的逻辑信道的LCG ID放在最前头。如此，对于某个逻辑信道，若存在较高调度紧急需求的数据到达，则授权不够需要上报截断BSR时，可以触发该逻辑信道对应的LCG的优先上报。
示例性的，重传BSR定时器超时，UE将较高调度紧急需求的数据触发的重传BSR场景下优先传输；(因为此时该逻辑信道为超级高优先级别)；比如：LCH1和LCG2都触发了BSR重传上报，此时，LCH1，LCG2将被认为是最高逻辑信道，但是因为LCH2有紧急调度数据触发的BSR重传，此时也将优先上报携带传输LCH2的LCG的BSR。如此，对于某个逻辑信道，若存在较高调度紧急需求的数据的BSR重传时，该逻辑信道对应的LCG的优先上报。
为了进一步解释本公开任意实施例，以下提供一个具体实施例。
1、一种针对特定数据上报BSR的方案。
a)特定数据为XR业务中具有较高调度紧急需求(即具有紧急调度需求)的数据(上行数据)。
具有紧急调度需求的数据也可以为需要进行优先调度需求的数据；还可以是网络或者终端认为需要及时发送的数据。
具有紧急调度需求的数据还可以扩展到特定数据的其他的业务特性：比如重要性。比如I帧数据比P帧更加重要，需要及时发送。
2、UE(如终端)判决较高调度紧急需求的数据可以基于如下机制：
a)作为一个实施例：接入层从非接入层或者从应用层获取到特定数据为XR业务中具有较高调度紧急需求的数据。
b)作为一个实施例：接入层从非接入层或者从应用层获取到特定数据为XR业务中较为重要需要进行优先传送的数据。
c)作为一个实施例：接入层从非接入层或者从应用层获取到特定数据为XR业务中具有较高调度紧急需求的数据可以基于非接入层或者从应用层的隐含指示，比如为I帧数据。
d)作为一个实施例：剩余数据包延迟预算(the time left until exceeding the PDB)小于某个阈值(比如判决该数据包的剩余数据包延迟预算小于10ms；该阈值可以协议约定或者从网络通知获得。PDB(packet delay buget，数据包延迟预算)的配置粒度可以是针对单个数据包，也可以是针对数据包集合)。
即终端可以预估哪些数据包的PDB已经接近用完，还没有调度出去，因此需要进行优先调度。
e)较高调度紧急需求的数据可以基于数据包(Packet)统计或者针对数据包集合(Packet set)进行统计。
3、方式1：UE先识别出特定数据(比如具有紧急调度需求的数据)，并将特定数据的所在的逻辑信道临时置为最高优先级别。
a)作为一个实施例：在常规BSR触发时，需要考虑到该类型的逻辑信道的优先级别为最高逻辑信道优先级别；(比如LCH1有上行数据发送，LCH2有新数据到达，即便LCH2的逻辑信道优先级别更低，但是因为LCH2有紧急调度数据到达，则LCH2逻辑信道优先级别高于LCH1。也将针对LCH2触发常规BSR)。
这样做的好处是将具有紧急调度需求的数据的逻辑信道及时触发BSR。
b)作为一个实施例：在填充(Padding)BSR上报时，若需要进行截短BSR上报，则需要考虑到该类型的逻辑信道的优先级别为最高逻辑信道优先级别；(比如LCH1有数据发送，LCH2有数据发送，即便LCH2的逻辑信道优先级别更低，但是因为有紧急调度数据到达，则其优先级别高于LCH2，则截短短BSR(Short Truncated BSR)中因为仅能携带一个LCG，则将携带LCH2的LCG)。
c)作为一个实施例：在BSR重传定时器超时，需要考虑较高调度紧急需求的数据的所在的逻辑信道置为最高优先级别；(比如LCH1触发了BSR上报，则重传定时器超时时候，LCH1将被认为是最高逻辑信道，即便LCH2的逻辑信道优先级别更低，但是因为有紧急调度数据到达，则也视为LCH2为最高优先级别)。
4、方式2：UE将较高调度紧急需求的数据到达触发常规BSR
a)作为一个实施例：即修改了现有的常规BSR触发的条件，增加了一个触发条件：该逻辑信道中存在紧急调度数据需求。
示例性的，如果激活的小区组发生以下任一事件，则应触发BSR：
-属于逻辑信道组(LCG)的逻辑信道的上行数据对MAC实体可用；并且：
1)该上行数据属于一个逻辑信道，该逻辑信道的优先级高于任何逻辑信道组中具有上行数据的逻辑信道的优先级；或者
2)属于逻辑信道组的逻辑信道都不包含任何可用的UL数据；或者
3)对于属于逻辑信道组的逻辑信道到达的可用数据成为具有紧急调度需求(即需要尽快调度或者具有严格延迟预算(stringent delay buget)；
这里，BSR可以是常规BSR。
也即(A BSR shall be triggered if any of the following events occur for activated cell group:
-UL data,for a logical channel which belongs to an LCG,becomes available to the MAC entity；and either
-this UL data belongs to a logical channel with higher priority than the priority of any logical channel containing available UL data which belong to any LCG；or
-none of the logical channels which belong to an LCG contains any available UL data；or
-UL data,for a logical channel which belongs to an LCG,becomes available data which has to be scheduled as soon as possible or has stringent delay buget；
in which case the BSR is referred below to as'Regular BSR'；)
作为一个实施例：即修改了相关技术中的常规BSR触发的条件，增加了一个触发条件：该逻辑信道中存在紧急调度数据需求即触发。即存在紧急调度数据需求的数据则可以触发。
作为一个实施例：即修改了相关技术中的常规BSR触发的条件，增加了一个触发条件：该逻辑信道中存在紧急调度数据需求的数据从无到有即触发。相比于前一个实施例，该方式可以避免该类BSR的频繁触发。
5、方式3：定义一种新的BSR，比如XR-BSR或者称之为优先权BSR，该BSR用于具有存在较高调度紧急需求的数据的逻辑信道或者逻辑信道组的优先传输。
作为一个实施例：若UE判决，若存在较高调度紧急需求的数据，则将该类逻辑信道属于的逻辑信道/逻辑信道组进行优先排序，组成优先权BSR。若授权有限即不足以传输排序后的所有的LCG，则优先权BSR可以传输尽量多的排序后的LCG。
示例1：
对于方式3中优先传输XR的一个实施例如下：
1>如果配置了剩余数据包延迟预算门限(延迟阈值)，并且任意LCG中逻辑信道包含的上行数据的剩余数据包延迟预算小于剩余数据包延迟预算门限(即数据包延迟预算将耗尽)，那么，
2>提高该LCG的优先级，即将存在快接近调度预算门限的LCG进行优先；
2>如果UL授权不能容纳仅包含所有优先LCG的缓冲区状态的SL-BSR MAC CE；
上报XR-BSR或者优先的BSR，XR-BSR中包含尽可能多的优先的LCG的缓冲区状态，这些LCG具有可用传输数据，同时考虑到上行(UL)授权中的比特数(即该新的BSR携带优先LCG)。也即(
1>if PdbThres is configured and the value of the logical channels that belong to any LCG and contain UL data whose remaining delay budget is less than PdbThres according to clause 5.4.5:
2>prioritize the LCG(s)
2>if the UL grant cannot accommodate an SL-BSR MAC CE containing buffer status only for all prioritized LCG:
report XR-BSR containing buffer status for as many prioritized LCGs having data available for transmission as possible,taking the number of bits in the UL grant into consideration.)
示例2：优先的BSR在进行逻辑信道优先级处理时：对于XR-BSR类型BRS或者优先权BSR的优先级别可以定义MAC CE for(Extended)BSR之前。下面给出一个实施例。
比如：逻辑通道应按照以下顺序进行优先级排序(具有最高优先级的在前)：
·用于C-RNTI的MAC CE，或来自UL-CCCH的数据；
·用于(增强型)BFR的MAC CE，或用于配置的授权确认的MAC CE，或用于多条目配置的授权确认的MAC CE；
·用于Sidelink配置授权确认的MAC CE；
·用于LBT失败的MAC CE；
·用于定时提前报告的MAC CE；
·XR-BSR或者优先权BSR的MAC CE；
·根据第5.22.1.6节优先考虑的SL-BSR的MAC CE；
·用于(扩展)BSR的MAC CE，不包括用于填充(padding)的BSR；
·用于(增强的)单条目PHR的MAC CE，或用于(增强的)多条目PHR的MAC CE；
·用于定位测量间隙激活/停用请求的MAC CE；
·用于所需保护符号的数量de MAC CE；
·案例6定时请求的MAC CE；
·用于(扩展)抢先BSR的MAC CE；
·用于SL-BSR的MAC CE，但根据第5.22.1.6节优先考虑的SL-BSR和用于填充的SL-BSR除外；
·用于IAB-MT推荐波束指示的MAC CE，或用于所需IAB-MT PSD范围的MAC CE，或用于所需DL Tx功率调整的MAC CE；
·来自任何逻辑信道的数据，来自UL-CCCH的数据除外；
·用于推荐比特率查询的MAC CE；
·包括用于填充(padding)的BSR的MAC CE；
·包括用于填充(padding)的SL-BSR的MAC CE。
6、方式4：引入一个比最高优先级(the highest priority)(即，第二最高优先级)级别更高的级别即超级优先级(super priority)(即，第一最高优先级)；此时UE将较高调度紧急需求的数据的逻辑信道判定为处于比高级别逻辑信道优先级别更高的级别；
a)作为一个实施例：在常规BSR触发时，若对于某个逻辑信道，若存在较高调度紧急需求的数据到达，则该类型数据的逻辑信道的优先级别高于其他任何一个LCG的任何一个逻辑信道；则会针对该逻辑信道对应的LCG触发常规BSR；
以上实施例，即可以保证对于某个逻辑信道，若存在较高调度紧急需求的数据到达，可以触发常规BSR。
b)作为一个实施例：对于Padding BSR需要进行截短上报的情况，则UE判决，若存在较高调度紧急需求的数据，则截短短BSR(Short Truncated BSR)中携带针对该逻辑信道的LCG ID上报(因为此时该逻辑信道为超级高优先级别)；若对于截短长BSR(Long Truncated BSR)，因为可以携带多个LCG信息，则可以将存在较高调度紧急需求的数据的逻辑信道的LCG ID放在最前头。
以上实施例，即可以保证对于某个逻辑信道，若存在较高调度紧急需求的数据到达，则授权不够需要上报截断BSR时，可以触发该逻辑信道对应的LCG的优先上报。
c)作为一个实施例：重传BSR定时器超时，UE将较高调度紧急需求的数据触发的重传BSR场景下优先传输；(因为此时该逻辑信道为超级高优先级别)；比如：LCH1和LCG2都触发了BSR重传上报，此时，LCH1，LCG2将被认为是最高逻辑信道，但是因为LCH2有紧急调度数据触发的BSR重传，此时也将优先上报携带传输LCH2的LCG的BSR。
以上实施例，即可以保证对于某个逻辑信道，若存在较高调度紧急需求的数据的BSR重传时，该逻辑信道对应的LCG的优先上报。
7、基站通过专用信令(第二指示信息)通知UE使用使能该特性；
a)方式A：其通知粒度可以是per UE粒度；
作为一种实施例，若基站知晓UE为进行XR业务的UE，将使能该功能；
b)方式B：其通知粒度可以是perLCG粒度；
作为一种实施例，若基站知晓UE为进行XR业务的UE，则通知其对于特定的LCG其将使能该功能；
c)方式C：其通知粒度可以是per逻辑信道粒度；
作为一种实施例，若基站知晓UE为进行XR业务的UE，则通知其对于特定的逻辑信道使能该功能；
d)其使能该功能的通知方式为显示或者隐含通知
作为一种实施例：若网络通知了针对某个逻辑信道的延迟预算门限，则意味着使能该功能；
8、基站通过专用信令通知UE使用该功能可以基于UE的辅助信息；
UE的辅助信息包括UE是否支持使用该功能的能力；
UE的辅助信息包括UE是否期望使用该功能(例如，若UE预估数据具有较高调度紧急需求，将上报辅助信息，标识期望使用)；
如图12所示，本公开实施例提供一种一种缓存状态报告上报装置100，其中，设置于UE中，包括：
收发模块110，配置为针对具有紧急调度需求的上行数据，上报缓存状态报告BSR。
在一个实施例中，所述收发模块110，具体配置为：
将具有紧急调度需求的所述上行数据对应的逻辑信道确定为最高优先级，并基于所述逻辑信道的优先级上报所述BSR。
在一个实施例中，所述收发模块110，具体配置为：
响应于逻辑信道具有紧急调度需求的所述上行数据，触发上报所述逻辑信道的所述BSR。
在一个实施例中，所述收发模块110，具体配置为：
响应于至少一个逻辑信道具有紧急调度需求的所述上行数据，触发第一逻辑信道的第一类BSR，其中，所述第一类BSR的优先级高于第二类BSR，并且所述第一逻辑信道为所述至少一个逻辑信道中优先级最高的逻辑信道。
在一个实施例中，所述收发模块110，具体配置为：
响应于逻辑信道具有紧急调度需求的所述上行数据，确定所述逻辑信道具有第一最高优先级，基于所述第一最高优先级上报所述BSR，其中，所述第一最高优先级高于第二最高优先级。
在一个实施例中，所述上行数据，包括：扩展现实XR业务上线数据。
在一个实施例中，所述具有紧急调度需求的上行数据，包括：剩余数据包延迟预算小于的延迟阈值的所述上行数据。
在一个实施例中，所述延迟阈值的配置粒度包括以下一项：
UE粒度；
逻辑信道粒度；
逻辑信道组粒度。
在一个实施例中，所述具有紧急调度需求的所述上行数据，是数据包粒度的；
或者，
所述具有紧急调度需求的所述上行数据，是数据包集合粒度的。
在一个实施例中，所述装置还包括：
处理模块120，配置为根据从非接入层或者应用层获取的第一指示信息，确定所述上行数据具有紧急调度需求。
在一个实施例中，所述收发模块，具体配置为：
根据基站发送的第二指示信息的指示，针对具有紧急调度需求的所述上行数据，上报所述BSR。
在一个实施例中，所述第二指示信息包括：所述上行数据的剩余数据包延迟预算所关联的延迟阈值。
在一个实施例中，所述收发模块110，具体配置为以下一项：
根据所述第二指示信息的指示，针对所述UE具有紧急调度需求的所述上行数据，上报所述BSR；
根据所述第二指示信息的指示，针对预定逻辑信道具有紧急调度需求的所述上行数据，上报所述BSR；
根据所述第二指示信息的指示，针对预定逻辑信道组具有紧急调度需求的所述上行数据，上报所述BSR。
在一个实施例中，所述收发模块110，还配置为：
向基站发送辅助信息，所述辅助信息用于指示：所述UE能够针对具有紧急调度需求的所述上行数据上报所述BSR。
如图13所示，本公开实施例提供一种缓存状态报告上报装置200，其中，设置于基站中，包括：
收发模块210，配置为：接收缓存状态报告BSR，其中，所述BSR是用户设备UE针对具有紧急调度需求的上行数据发送的。
在一个实施例中，所述BSR是所述UE将具有紧急调度需求的所述上行数据对应的逻辑信道确定为最高优先级，并基于所述逻辑信道的优先级上报的。
在一个实施例中，所述BSR是所述UE响应于逻辑信道具有紧急调度需求的所述上行数据，触发上报的。
在一个实施例中，上报的所述BSR包括：第一类BSR，所述第一类BSR关联于第一逻辑信道；
所述第一类BSR是所述UE响应于至少一个逻辑信道具有紧急调度需求的所述上行数据，并且第一逻辑信道为所述至少一个逻辑信道中优先级最高的逻辑信道触发上报的，其中，所述第一类BSR的优先级高于第二类BSR。
在一个实施例中，所述BSR是所述UE响应于逻辑信道具有紧急调度需求的所述上行数据，确定所述逻辑信道具有第一最高优先级，并基于所述第一最高优先级上报的，其中，所述第一最高优先级高于第二最高优先级。
在一个实施例中，所述上行数据，包括：扩展现实XR业务上线数据。
在一个实施例中，所述具有紧急调度需求的上行数据，包括：剩余数据包延迟预算小于的延迟阈值的所述上行数据。
在一个实施例中，所述延迟阈值的配置粒度包括以下一项：
UE粒度；
逻辑信道粒度；
逻辑信道组粒度。
在一个实施例中，所述具有紧急调度需求的所述上行数据，是数据包粒度的；
或者，
所述具有紧急调度需求的所述上行数据，是数据包集合粒度的。
在一个实施例中，所述收发模块210还配置为：
向所述UE发送第二指示信息，其中，所述第二指示信息用于指示所述UE针对具有紧急调度需 求的所述上行数据，上报所述BSR。
在一个实施例中，所述第二指示信息包括：所述上行数据的剩余数据包延迟预算所关联的延迟阈值。
在一个实施例中，所述第二指示信息，用于指示以下一项：
针对所述UE具有紧急调度需求的所述上行数据上报所述BSR；
针对预定逻辑信道具有紧急调度需求的所述上行数据上报所述BSR；
针对预定逻辑信道组具有紧急调度需求的所述上行数据上报所述BSR。
在一个实施例中，所述收发模块210，具体配置为：
响应于接收到所述UE发送的辅助信息，向所述UE发送所述第二指示信息，其中，所述辅助信息用于指示：所述UE能够针对具有紧急调度需求的所述上行数据上报所述BSR。
本公开实施例提供一种通信设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，处理器被配置为：用于运行可执行指令时，实现本公开任意实施例的缓存状态报告上报方法。
在一个实施例中，通信设备可以包括但不限于至少之一：UE及网络设备。这里网络设备可包括核心网或者接入网设备等。这里，接入网设备可包括基站；核心网可包括AMF、SMF。
其中，处理器可包括各种类型的存储介质，该存储介质为非临时性计算机存储介质，在用户设备掉电之后能够继续记忆存储其上的信息。
处理器可以通过总线等与存储器连接，用于读取存储器上存储的可执行程序，例如，如图2至11所示的方法的至少其中之一。
本公开实施例还提供一种计算机存储介质，计算机存储介质存储有计算机可执行程序，可执行程序被处理器执行时实现本公开任意实施例的缓存状态报告上报方法。例如，如图2至11所示的方法的至少其中之一。
关于上述实施例中的装置或者存储介质，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
图14是根据一示例性实施例示出的一种用户设备3000的框图。例如，用户设备3000可以是移动电话，计算机，数字广播用户设备，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图14，用户设备3000可以包括以下一个或多个组件：处理组件3002，存储器3004，电源组件3006，多媒体组件3008，音频组件3010，输入/输出(I/O)的接口3012，传感器组件3014，以及通信组件3016。
处理组件3002通常控制用户设备3000的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件3002可以包括一个或多个处理器3020来执行指令，以完 成上述的方法的全部或部分步骤。此外，处理组件3002可以包括一个或多个模块，便于处理组件3002和其他组件之间的交互。例如，处理组件3002可以包括多媒体模块，以方便多媒体组件3008和处理组件3002之间的交互。
存储器3004被配置为存储各种类型的数据以支持在用户设备3000的操作。这些数据的示例包括用于在用户设备3000上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器3004可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件3006为用户设备3000的各种组件提供电力。电源组件3006可以包括电源管理系统，一个或多个电源，及其他与为用户设备3000生成、管理和分配电力相关联的组件。
多媒体组件3008包括在所述用户设备3000和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件3008包括一个前置摄像头和/或后置摄像头。当用户设备3000处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件3010被配置为输出和/或输入音频信号。例如，音频组件3010包括一个麦克风(MIC)，当用户设备3000处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器3004或经由通信组件3016发送。在一些实施例中，音频组件3010还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件3002和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件3014包括一个或多个传感器，用于为用户设备3000提供各个方面的状态评估。例如，传感器组件3014可以检测到设备3000的打开/关闭状态，组件的相对定位，例如所述组件为用户设备3000的显示器和小键盘，传感器组件3014还可以检测用户设备3000或用户设备3000一个组件的位置改变，用户与用户设备3000接触的存在或不存在，用户设备3000方位或加速/减速和用户设备3000的温度变化。传感器组件3014可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件3014还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件3014还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件3016被配置为便于用户设备3000和其他设备之间有线或无线方式的通信。用户设备 3000可以接入基于通信标准的无线网络，如WiFi，4G或5G，或它们的组合。在一个示例性实施例中，通信组件3016经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，用户设备3000可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器3004，上述指令可由用户设备3000的处理器3020执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
图15所示，本公开一实施例示出一种基站的结构。例如，基站900可以被提供为一网络侧设备。参照图15，基站900包括处理组件922，其进一步包括一个或多个处理器，以及由存储器932所代表的存储器资源，用于存储可由处理组件922的执行的指令，例如应用程序。存储器932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件922被配置为执行指令，以执行上述方法前述应用在所述基站的任意方法。
基站900还可以包括一个电源组件926被配置为执行基站900的电源管理，一个有线或无线网络接口950被配置为将基站900连接到网络，和一个输入输出(I/O)接口958。基站900可以操作基于存储在存储器932的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (31)

  1. 一种缓存状态报告上报方法，其中，被用户设备UE执行，包括：
    针对具有紧急调度需求的上行数据，上报缓存状态报告BSR。
  2. 根据权利要求1所述的方法，其中，所述针对具有紧急调度需求的上行数据，上报BSR包括：
    将具有紧急调度需求的所述上行数据对应的逻辑信道确定为最高优先级，并基于所述逻辑信道的优先级上报所述BSR。
  3. 根据权利要求1所述的方法，其中，所述针对具有紧急调度需求的上行数据，上报BSR包括：
    响应于逻辑信道具有紧急调度需求的所述上行数据，触发上报所述逻辑信道的所述BSR。
  4. 根据权利要求1所述的方法，其中，所述针对具有紧急调度需求的上行数据，上报BSR包括：
    响应于至少一个逻辑信道具有紧急调度需求的所述上行数据，触发第一逻辑信道的第一类BSR，其中，所述第一类BSR的优先级高于第二类BSR，并且所述第一逻辑信道为所述至少一个逻辑信道中优先级最高的逻辑信道。
  5. 根据权利要求1所述的方法，其中，所述针对具有紧急调度需求的上行数据，上报BSR包括：
    响应于逻辑信道具有紧急调度需求的所述上行数据，确定所述逻辑信道具有第一最高优先级，基于所述第一最高优先级上报所述BSR，其中，所述第一最高优先级高于第二最高优先级。
  6. 根据权利要求1至5任一项所述的方法，其中，所述上行数据，包括：扩展现实XR业务上行数据。
  7. 根据权利要求6所述的方法，其中，
    所述具有紧急调度需求的上行数据，包括：剩余数据包延迟预算小于的延迟阈值的所述上行数据。
  8. 根据权利要求7所述的方法，其中，所述延迟阈值的配置粒度包括以下一项：
    UE粒度；
    逻辑信道粒度；
    逻辑信道组粒度。
  9. 根据权利要求6所述的方法，其中，
    所述具有紧急调度需求的所述上行数据，是数据包粒度的；
    或者，
    所述具有紧急调度需求的所述上行数据，是数据包集合粒度的。
  10. 根据权利要求6所述的方法，其中，所述方法还包括：
    根据从非接入层或者应用层获取的第一指示信息，确定所述上行数据具有紧急调度需求。
  11. 根据权利要求1至5任一项所述的方法，其中，所述针对具有紧急调度需求的上行数据，上报BSR，包括：
    根据基站发送的第二指示信息的指示，针对具有紧急调度需求的所述上行数据，上报所述BSR。
  12. 根据权利要求11所述的方法，其中，所述第二指示信息包括：所述上行数据的剩余数据包 延迟预算所关联的延迟阈值。
  13. 根据权利要求11所述的方法，其中，所述根据基站发送的第二指示信息的指示，针对具有紧急调度需求的所述上行数据，上报所述BSR，包括以下一项：
    根据所述第二指示信息的指示，针对所述UE具有紧急调度需求的所述上行数据，上报所述BSR；
    根据所述第二指示信息的指示，针对预定逻辑信道具有紧急调度需求的所述上行数据，上报所述BSR；
    根据所述第二指示信息的指示，针对预定逻辑信道组具有紧急调度需求的所述上行数据，上报所述BSR。
  14. 根据权利要求1至5任一项所述的方法，其中，所述方法还包括：
    向基站发送辅助信息，所述辅助信息用于指示：所述UE能够针对具有紧急调度需求的所述上行数据上报所述BSR。
  15. 一种缓存状态报告上报方法，其中，被基站执行，包括：
    接收缓存状态报告BSR，其中，所述BSR是用户设备UE针对具有紧急调度需求的上行数据发送的。
  16. 根据权利要求15所述的方法，其中，
    所述BSR是所述UE将具有紧急调度需求的所述上行数据对应的逻辑信道确定为最高优先级，并基于所述逻辑信道的优先级上报的。
  17. 根据权利要求15所述的方法，其中，
    所述BSR是所述UE响应于逻辑信道具有紧急调度需求的所述上行数据，触发上报的。
  18. 根据权利要求15所述的方法，其中，上报的所述BSR包括：第一类BSR，所述第一类BSR关联于第一逻辑信道；
    所述第一类BSR是所述UE响应于至少一个逻辑信道具有紧急调度需求的所述上行数据，并且第一逻辑信道为所述至少一个逻辑信道中优先级最高的逻辑信道触发上报的，其中，所述第一类BSR的优先级高于第二类BSR。
  19. 根据权利要求15所述的方法，其中，
    所述BSR是所述UE响应于逻辑信道具有紧急调度需求的所述上行数据，确定所述逻辑信道具有第一最高优先级，并基于所述第一最高优先级上报的，其中，所述第一最高优先级高于第二最高优先级。
  20. 根据权利要求15至19任一项所述的方法，其中，所述上行数据，包括：扩展现实XR业务上行数据。
  21. 根据权利要求20所述的方法，其中，
    所述具有紧急调度需求的上行数据，包括：剩余数据包延迟预算小于的延迟阈值的所述上行数据。
  22. 根据权利要求21所述的方法，其中，所述延迟阈值的配置粒度包括以下一项：
    UE粒度；
    逻辑信道粒度；
    逻辑信道组粒度。
  23. 根据权利要求20所述的方法，其中，
    所述具有紧急调度需求的所述上行数据，是数据包粒度的；
    或者，
    所述具有紧急调度需求的所述上行数据，是数据包集合粒度的。
  24. 根据权利要求15至19任一项所述的方法，其中，所述方法还包括：
    向所述UE发送第二指示信息，其中，所述第二指示信息用于指示所述UE针对具有紧急调度需求的所述上行数据，上报所述BSR。
  25. 根据权利要求24所述的方法，其中，所述第二指示信息包括：所述上行数据的剩余数据包延迟预算所关联的延迟阈值。
  26. 根据权利要求24所述的方法，其中，所述第二指示信息，用于指示以下一项：
    针对所述UE具有紧急调度需求的所述上行数据上报所述BSR；
    针对预定逻辑信道具有紧急调度需求的所述上行数据上报所述BSR；
    针对预定逻辑信道组具有紧急调度需求的所述上行数据上报所述BSR。
  27. 根据权利要求24所述的方法，其中，所述向所述UE发送第二指示信息，包括：
    响应于接收到所述UE发送的辅助信息，向所述UE发送所述第二指示信息，其中，所述辅助信息用于指示：所述UE能够针对具有紧急调度需求的所述上行数据上报所述BSR。
  28. 一种缓存状态报告上报装置，其中，设置于用户设备UE中，包括：
    收发模块，配置为针对具有紧急调度需求的上行数据，上报缓存状态报告BSR。
  29. 一种缓存状态报告上报装置，其中，设置于基站中，包括：
    收发模块，配置为：接收缓存状态报告BSR，其中，所述BSR是用户设备UE针对具有紧急调度需求的上行数据发送的。
  30. 一种通信设备，其中，所述通信设备，包括：
    处理器；
    用于存储所述处理器可执行指令的存储器；
    其中，所述处理器被配置为：用于运行所述可执行指令时，实现权利要求1至14、15至27任一项所述的缓存状态报告上报方法。
  31. 一种计算机存储介质，其中，所述计算机存储介质存储有计算机可执行程序，所述可执行程序被处理器执行时实现权利要求1至14、15至27任一项所述的缓存状态报告上报方法。
PCT/CN2022/120818 2022-09-23 2022-09-23 一种缓存状态报告上报方法、装置、通信设备及存储介质 WO2024060191A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280003696.6A CN116097728A (zh) 2022-09-23 2022-09-23 一种缓存状态报告上报方法、装置、通信设备及存储介质
PCT/CN2022/120818 WO2024060191A1 (zh) 2022-09-23 2022-09-23 一种缓存状态报告上报方法、装置、通信设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/120818 WO2024060191A1 (zh) 2022-09-23 2022-09-23 一种缓存状态报告上报方法、装置、通信设备及存储介质

Publications (1)

Publication Number Publication Date
WO2024060191A1 true WO2024060191A1 (zh) 2024-03-28

Family

ID=86208727

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/120818 WO2024060191A1 (zh) 2022-09-23 2022-09-23 一种缓存状态报告上报方法、装置、通信设备及存储介质

Country Status (2)

Country Link
CN (1) CN116097728A (zh)
WO (1) WO2024060191A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024092678A1 (zh) * 2022-11-03 2024-05-10 北京小米移动软件有限公司 信息传输控制方法及装置、通信设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101925128A (zh) * 2009-06-17 2010-12-22 大唐移动通信设备有限公司 一种上报缓存状态报告的方法及装置
CN102905305A (zh) * 2011-07-25 2013-01-30 联芯科技有限公司 缓存状态报告的上报方法及用户终端
CN107404732A (zh) * 2016-05-18 2017-11-28 普天信息技术有限公司 缓存报告的上报方法和装置
CN108540994A (zh) * 2017-03-01 2018-09-14 展讯通信（上海）有限公司 缓存状态报告的触发方法、装置及用户设备
CN109429568A (zh) * 2017-06-19 2019-03-05 北京小米移动软件有限公司 一种上报缓存状态报告的方法及装置
WO2019222884A1 (zh) * 2018-05-21 2019-11-28 北京小米移动软件有限公司 缓存状态报告的格式的设置方法和装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101925128A (zh) * 2009-06-17 2010-12-22 大唐移动通信设备有限公司 一种上报缓存状态报告的方法及装置
CN102905305A (zh) * 2011-07-25 2013-01-30 联芯科技有限公司 缓存状态报告的上报方法及用户终端
CN107404732A (zh) * 2016-05-18 2017-11-28 普天信息技术有限公司 缓存报告的上报方法和装置
CN108540994A (zh) * 2017-03-01 2018-09-14 展讯通信（上海）有限公司 缓存状态报告的触发方法、装置及用户设备
CN109429568A (zh) * 2017-06-19 2019-03-05 北京小米移动软件有限公司 一种上报缓存状态报告的方法及装置
WO2019222884A1 (zh) * 2018-05-21 2019-11-28 北京小米移动软件有限公司 缓存状态报告的格式的设置方法和装置

Also Published As

Publication number Publication date
CN116097728A (zh) 2023-05-09

Similar Documents

Publication Publication Date Title
WO2021109043A1 (zh) 数据处理方法及装置、通信设备
CN111869274B (zh) 数据传输处理方法、装置、用户设备及存储介质
CN113115591B (zh) Harq-ack传输方法及装置、通信设备及存储介质
WO2021087829A1 (zh) Harq-ack处理方法及装置、通信设备及存储介质
WO2023184187A1 (zh) 确定传输方向的方法、装置、通信设备及存储介质
WO2024060191A1 (zh) 一种缓存状态报告上报方法、装置、通信设备及存储介质
WO2021030979A1 (zh) 数据处理方法及装置、通信设备及存储介质
WO2022261877A1 (zh) Drx定时器的启动方法、装置、通信设备及存储介质
WO2024065109A1 (zh) 信息传输控制方法、装置、通信设备及存储介质
US20220386357A1 (en) Data transmission method and apparatus, and communication device
WO2023184186A1 (zh) 确定传输方向的方法、装置、通信设备及存储介质
WO2022032581A1 (zh) 上行传输的发送、接收方法及装置、通信设备及介质
CN115053582B (zh) 信息处理方法及装置、通信设备及存储介质
WO2022236498A1 (zh) 连接失败检测方法及装置、通信设备及存储介质
WO2021258371A1 (zh) 直连通信控制方法、装置及用户设备
WO2021163969A1 (zh) 数据传输方法、装置和通信设备
WO2022016450A1 (zh) 逻辑信道复用方法及装置、通信设备及存储介质
WO2021087766A1 (zh) 混合自动重传请求应答传输方法及装置、设备及介质
WO2024092678A1 (zh) 信息传输控制方法及装置、通信设备及存储介质
WO2023122916A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2024130505A1 (zh) 调度处理方法以及装置、通信设备及存储介质
WO2024044916A1 (zh) 上报bsr的方法、装置、通信设备及存储介质
WO2024055313A1 (zh) 一种目标终端确定方法、装置、通信设备及存储介质
CN116325891A (zh) 调度请求传输方法及装置、通信设备及存储介质
WO2023221025A1 (zh) 波束确定方法、装置、通信设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22959198

Country of ref document: EP

Kind code of ref document: A1