WO2024092667A1 - 缓冲状态报告上传方法、装置、设备、存储介质与芯片 - Google Patents

缓冲状态报告上传方法、装置、设备、存储介质与芯片 Download PDF

Info

Publication number
WO2024092667A1
WO2024092667A1 PCT/CN2022/129675 CN2022129675W WO2024092667A1 WO 2024092667 A1 WO2024092667 A1 WO 2024092667A1 CN 2022129675 W CN2022129675 W CN 2022129675W WO 2024092667 A1 WO2024092667 A1 WO 2024092667A1
Authority
WO
WIPO (PCT)
Prior art keywords
buffer status
status report
data
transmitted
user equipment
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/129675
Other languages
English (en)
French (fr)
Inventor
李艳华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
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 Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to PCT/CN2022/129675 priority Critical patent/WO2024092667A1/zh
Priority to EP22963977.8A priority patent/EP4614896A4/en
Priority to CN202280004510.9A priority patent/CN115997408A/zh
Publication of WO2024092667A1 publication Critical patent/WO2024092667A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • 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/0278—Traffic management, e.g. flow control or congestion control using buffer status reports

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a buffer status report uploading method, device, equipment, storage medium and chip.
  • the UE terminal
  • BSR Buffer Status reporting
  • the BSR provides the amount of data in the UE's buffer waiting to be sent to the network.
  • the network allocates transmission resources for the UE to transmit data based on the BSR reported by the UE.
  • a PDU set (Protocol Data Unit set) contains multiple PDUs (Protocol Data Unit); in the discard mechanism of the PDCP (Packet Data Convergence Protocol) layer, the PDCP layer uses PDU set as the minimum discard unit to discard PDU set.
  • PDCP Packet Data Convergence Protocol
  • the present disclosure provides a buffer status report uploading method, device, equipment, storage medium and chip.
  • a buffer status report reporting method is provided, the method being executed by a user equipment, the method comprising:
  • an update report of a buffer status report is performed.
  • a buffer status report reporting method is provided, the method being executed by a network device, the method comprising:
  • a buffer status report reporting device is provided, the device is configured in a user equipment, and the device includes:
  • the buffer status report sending module is configured to update and report the buffer status report in response to a change in at least one of the amount of data to be transmitted of the user equipment and the remaining delay budget of the amount of data to be transmitted.
  • a buffer status report reporting device configured in a network device, the device comprising:
  • the buffer status report receiving module is configured to receive a buffer status report updated and reported by a user equipment.
  • a user equipment including:
  • a memory for storing processor-executable instructions
  • the processor is configured to implement the steps of the buffer status report reporting method provided in the first aspect of the embodiment of the present disclosure when executing the executable instructions.
  • a network device including:
  • a memory for storing processor-executable instructions
  • the processor is configured to implement the steps of the buffer status report reporting method provided in the second aspect of the embodiment of the present disclosure when executing the executable instructions.
  • a computer-readable storage medium on which computer program instructions are stored.
  • the program instructions are executed by a processor, the steps of the buffer status report reporting method provided by the first aspect of the embodiment of the present disclosure, or the steps of the buffer status report reporting method provided by the second aspect of the embodiment of the present disclosure are implemented.
  • a chip comprising a processor and an interface; the processor is used to read instructions to execute the steps of the buffer status report reporting method provided by the first aspect of the embodiment of the present disclosure, or to execute the steps of the buffer status report reporting method provided by the second aspect of the embodiment of the present disclosure.
  • the PDCP layer may discard the PDU in the PDU set, resulting in a change in the amount of data to be transmitted and/or the remaining delay budget of the data to be transmitted.
  • the BSR can be re-reported, and the re-reported BSR carries the changed amount of data to be transmitted and/or the remaining delay budget of the data to be transmitted. In this way, the network can allocate transmission resources matching the amount of data to be transmitted to the UE based on the changed amount of data to be transmitted and/or the remaining delay budget of the data to be transmitted, without allocating excessive transmission resources, thereby avoiding waste of transmission resources.
  • Fig. 1 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 2 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 3 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 4 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 5 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 6 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 7 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 8 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 9 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 10 is a flow chart showing a method for determining a switching delay according to an exemplary embodiment.
  • Fig. 11 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 12 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 13 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 14 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 15 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 16 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 17 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 18 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 19 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 20 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 21 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 22 is a flow chart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 23 is a flowchart showing a method for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 24 is a block diagram showing a device for reporting a buffer status report according to an exemplary embodiment.
  • Fig. 25 is a block diagram showing a buffer status report reporting device according to an exemplary embodiment.
  • Fig. 26 is a block diagram showing a user equipment according to an exemplary embodiment.
  • Fig. 27 is a block diagram of a network device according to an exemplary embodiment.
  • BSR Buffer Status reporting: Before transmitting data to the network, the UE needs to report BSR to the network. BSR provides the amount of data in the UE's buffer waiting to be sent to the network. The network allocates transmission resources for the UE to transmit data based on the BSR reported by the UE.
  • BSRs triggered under different mechanisms are called different BSRs.
  • the first type of regular BSR (Regular BSR): the UL (Uplink) data transmitted by the UE to the network belongs to a logical channel, and the priority of this logical channel is higher than the priority of any logical channel transmitting UL data. It can also be understood that the highest priority logical channel among the multiple logical channels of the UE has UL data, and this highest priority logical channel will trigger BSR reporting.
  • Regular BSR regular BSR
  • the second type of regular BSR one of the multiple logical channels of the UE has transmittable UL data, and the other logical channels have no transmittable UL data.
  • the logical channel with UL data will trigger BSR reporting.
  • Padding BSR If the UE has been allocated UL resources and the number of padding bits is greater than or equal to the size of the BSR's MAC CE (MAC layer control unit CE) and the MAC CE subheader, the UE will be triggered to report the BSR.
  • MAC CE MAC layer control unit CE
  • the control plane protocol layer structure in the network system can include the functions of the RRC (Radio Resource Control) layer, PDCP (Packet Data Convergence Protocol) layer, RLC (Radio Link Control) layer, MAC (Media Access Control) layer and physical layer.
  • the MAC layer proposed in this paragraph and the PDCP layer to be described below are both one of the control plane protocol layer structures.
  • the MAC layer is responsible for HARQ (Hybrid Automatic Repeat reQuest) and scheduling functions
  • the PDCP layer is responsible for segmenting and linking the data of the RLC layer, header compression and encryption, etc.
  • Periodic BSR When the periodicBSR-Timer (periodic reporting time) expires, the UE will be triggered to report the BSR.
  • LC Logical Channel
  • LCG Logical Channel Group
  • UE generally divides LC into LCGs of different priorities, and each LCG of different priorities is used to send BSRs of different levels.
  • the standardized QCI (1-9) specified in 3GPP (TS23.203) QCIs (1-3) are mapped to LCG1; QCIs (4-6) are mapped to LCG2; QCIs (7-9) are mapped to LCG3, and non-standardized QCIs (10-256) are mapped to LCG3; LCG0 is used to send SRB (signalling radio bearers), and BSR0-3 are sent on LCG0-3 respectively.
  • PDU Protocol Data Unit
  • PDU set Protocol Data Unit set
  • PDU is the data unit transmitted between peer layers.
  • the PDU of the physical layer is the data bit
  • the PDU of the data link layer is the data frame
  • the PDU of the network layer is the data packet
  • the PDU of the transport layer is the data segment
  • the PDU of other higher layers is the message.
  • the names of PDUs at different levels can be uniformly referred to as data packets.
  • PDCP Packet Data Convergence Protocol
  • SDU Service Data Unit
  • PDCP will discard all PDUs related to PDU set.
  • UDP User Datagram Protocol
  • GTP-U GTP-U layer.
  • UDP determines the boundary of a PDU set according to the sequence number (PDU Set SN) of the PDU set, the start PDU of the PDU set (the start PDU is the first PDU in the PDU set) and the end PDU (the end PDU is the last PDU in the PDU set), the sequence number of each PDU in the PDU set, and the number of PDUs in the PDUset.
  • PDU Set SN sequence number of the PDU set
  • the start PDU is the first PDU in the PDU set
  • the end PDU the last PDU in the PDU set
  • the sequence number of each PDU in the PDU set the sequence number of each PDU in the PDU set
  • the number of PDUs in the PDUset When a PDU in a PDU set is lost, all PDUs in the entire PDU set are discarded according to the boundary of the PDU set.
  • XR Extended Reality
  • data frames are divided into I frames (key frames) and P frames (predicted frames).
  • I frames key frames
  • P frames predicted frames
  • UE decodes P frames it cannot decode P frames alone and needs to use I frames to decode P frames. Therefore, all PDU sets contained in data frames such as I frames and P frames need to reach the application layer to correctly decode these data.
  • XR services include: AR (Augmented Reality), VR (Virtual Reality) and MR (Mixed Reality).
  • the PDCP layer will delete all the PDUs in the entire PDU set at the PDCP layer based on the discard mechanism. The deleted PDUs do not need to be transmitted further, which will waste the transmission resources authorized by the network to the deleted PDU.
  • the network authorizes and schedules the transmission resources of 3 PDUs out of the 20 PDUs, but during the period of network authorization scheduling, if the first PDU of the 3 PDUs (assuming that the first PDU is a relatively important I frame) is lost, based on the discard mechanism of the PDCP layer, all PDUs in the entire PDU set will be deleted at the PDCP layer, and these deleted PDUs do not need to continue to be transmitted, and the UE no longer needs the transmission resources of these deleted PDUs. In this case, the network still authorizes the UE to have 3 PDUs of transmission resources according to the amount of data to be transmitted reported by the BSR, which will lead to a waste of transmission resources.
  • the PDCP layer when a UE uses transmission resources for data transmission, if a PDU in a PDU set in the PDCP layer is lost, the PDCP layer will delete the entire PDU set based on a discard mechanism, so that there is no need to continue to transmit the PDUs in the entire PDU set. At this time, if the network still allocates transmission resources for the deleted PDU according to the amount of data to be transmitted in the BSR previously reported by the UE, it will lead to a waste of transmission resources.
  • the present invention re-reports the BSR when at least one of the amount of data to be transmitted and the remaining delay budget of the data to be transmitted changes, so that the network can reasonably authorize transmission resources for the UE based on the re-reported BSR, thereby avoiding the network allocating excess transmission resources to the UE.
  • FIG. 1 shows a buffer status report reporting method according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG. 1 , the buffer status report reporting method includes the following steps.
  • step S101 in response to a change in at least one of the amount of data to be transmitted of the user device and the remaining delay budget of the data to be transmitted, an update report of the buffer status report is performed.
  • the user equipment proposed in any embodiment of the present disclosure may be a mobile phone, a tablet, a portable computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.
  • the present disclosure does not limit the application scenario, and the user equipment may sometimes also be referred to as a terminal device, a terminal, an access terminal, UE, a UE unit, a UE station, a mobile device, a mobile station, a mobile station, a mobile client, etc.
  • the amount of data to be transmitted of the user equipment may be the amount of data to be transmitted in the buffer of the user equipment
  • the remaining delay budget of the amount of data to be transmitted may be the remaining time for the data to be transmitted corresponding to the amount of data to be transmitted to be transmitted from the buffer.
  • the UE allocates a delay budget of 10 ms to the data to be transmitted in the buffer. After 8 ms, the data to be transmitted in the buffer has 2 ms left to be transmitted from the buffer, and 2 ms is the remaining delay budget.
  • the change in the amount of data to be transmitted includes an increase and a decrease in the amount of data to be transmitted.
  • the amount of data to be transmitted increases, it means that new data has arrived at the buffer; when the amount of data to be transmitted decreases, the PDCP layer may discard the PDU set, and the PDCP layer discarding the PDU set may be a batch discard of data packets at the PDCP layer.
  • the network authorizes transmission resources for the UE according to the amount of data to be transmitted in the previous BSR, fewer transmission resources will be allocated to the UE, making it impossible for some of the current data to be transmitted to be transmitted in time.
  • a conventional BSR usually triggers a BSR report only when the data in the buffer increases from zero to full.
  • the conventional BSR cannot trigger a BSR re-report when the data in the buffer increases.
  • the BSR in order to ensure that the UE's data to be transmitted can be sent out in a timely manner when the amount of data to be transmitted increases, the BSR can be updated and reported.
  • the updated reported amount of data to be transmitted is greater than the amount of data to be transmitted in the previously reported BSR.
  • the network can authorize more transmission resources to the UE based on the updated BSR, and the UE can transmit the increased data to be transmitted in a timely manner based on the more transmission resources.
  • the amount of data to be transmitted by the UE decreases, when the PDCP layer discards data packets in batches, the amount of data to be transmitted in the UE's buffer will decrease. At this time, if the network authorizes transmission resources for the UE according to the amount of data to be transmitted in the previous BSR, more transmission resources will be allocated to the UE, resulting in a waste of transmission resources.
  • the BSR in order to reduce the waste of transmission resources when the amount of data to be transmitted decreases, the BSR can be updated and reported when the amount of data to be transmitted of the UE decreases.
  • the updated reported amount of data to be transmitted is less than the amount of data to be transmitted in the previously reported BSR.
  • the network will not authorize more transmission resources to the UE based on the updated BSR, thereby reducing the waste of transmission resources.
  • the BSR update report is performed for the change of the remaining delay budget, including the remaining delay budget increases or decreases compared with the remaining delay budget in the last reported BSR, then the BSR update report is performed; or the remaining delay budget is less than or equal to a certain threshold, then the BSR update report is performed.
  • the change of the remaining delay budget of the amount of data to be transmitted includes the increase and decrease of the remaining delay budget.
  • the PDCP layer may discard PDU sets in batches; when the remaining delay budget decreases, the data to be transmitted may be urgently scheduled.
  • the BSR may be updated and reported when at least one of the amount of data to be transmitted of the user equipment and the remaining delay budget of the amount of data to be transmitted changes, by means of network configuration of the UE or by means of protocol agreement of the UE.
  • the network configuration UE is an indication sent by the network UE, instructing the UE to update and report the BSR when the amount of data to be transmitted in the buffer and/or the remaining delay budget of the data to be transmitted changes.
  • the protocol stipulates that the UE is specified on the logical channel and/or logical channel group between the network and the UE, and updates and reports the BSR when the amount of data to be transmitted in the buffer of the logical channel and/or logical channel group changes. For example, some types of logical channels and/or logical channel groups are used to transmit data of XR services, so the protocol can stipulate that these types of logical channels and/or logical channel groups will update and report the BSR when the amount of data to be transmitted in their respective buffers changes.
  • the UE will send a BSR to the network, and the network will allocate transmission resources to the UE based on the BSR.
  • the network will allocate transmission resources to the UE based on the BSR.
  • batch packet loss occurs at the PDCP layer.
  • the UE will update and report the BSR, and re-upload the BSR carrying the changed amount of data to be transmitted and/or the changed remaining delay budget.
  • the update and reporting of the BSR proposed in any embodiment of the present disclosure can be understood as re-updating the previously reported BSR and reporting it.
  • the last reported BSR carries the remaining delay budget information and/or the amount of data to be transmitted; and the fields related to the remaining delay budget information and/or the amount of data to be transmitted in the subsequently reported BSR are empty, which may mean that the last reported BSR is no longer valid, or that the remaining delay budget information carried in the last reported BSR is no longer valid.
  • the BSR can be re-reported, and the re-reported BSR carries the changed amount of data to be transmitted and/or the remaining delay budget of the data to be transmitted.
  • the network can allocate transmission resources matching the amount of data to be transmitted to the UE based on the changed amount of data to be transmitted and/or the remaining delay budget of the data to be transmitted, without allocating excess transmission resources, thereby avoiding waste of transmission resources.
  • FIG. 2 shows a buffer status report reporting method according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG. 2 , the buffer status report reporting method includes the following steps.
  • step S201 in response to the change value of the amount of data to be transmitted being greater than the change threshold of the amount of data to be transmitted, an update report of the buffer status report is performed.
  • the UE may be configured by the network or agreed upon by the protocol to update and report the BSR when the change value of the amount of data to be transmitted of the UE is greater than the change threshold of the amount of data to be transmitted.
  • the change value of the amount of data to be transmitted may be the amount of packet loss data due to batch packet loss at the PDCP layer, or the amount of data increased in the buffer after new data arrives at the buffer.
  • the network configures the UE or the protocol stipulates that the UE updates and reports the BSR when a batch packet loss operation is performed at the PDCP layer and the amount of packet loss data is greater than the threshold value for the change in the amount of data to be transmitted.
  • the network configures the UE or the protocol stipulates that the UE updates and reports the BSR when the amount of data increased in the buffer is greater than the threshold value for the change in the amount of data to be transmitted.
  • the change value of the amount of data to be transmitted may be any one of the number of lost packets, the number of bytes of lost packets, and the number of bits of lost packets; the number of lost packets may be the number of data packets (Packet) or the number of data packet sets (Packet Set).
  • the amount of data to be transmitted may be determined by the UE based on the amount of data at the PDCP layer and/or RLC (Radio Link Control, radio link layer control protocol).
  • the threshold value for the change in the amount of data to be transmitted may be obtained by the base station from the core network and sent to the UE, or the threshold value for the change in the amount of data to be transmitted may be agreed upon between the UE and the network based on a protocol.
  • the present disclosure proposes to update and report the BSR only when the change value of the amount of data to be transmitted is greater than the change threshold of the amount of data to be transmitted. In this way, after improving the reporting conditions of the BSR, the number of BSR reports can be reduced, reducing the waste of network resources.
  • the BSR in response to the change value of the amount of data to be transmitted being greater than the change threshold of the amount of data to be transmitted, the BSR is updated and reported, which can improve the BSR reporting conditions, reduce the number of BSR reports, and reduce the waste of network resources.
  • FIG. 3 shows a buffer status report reporting method according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG. 3 , the buffer status report reporting method includes the following steps.
  • step S301 when the remaining delay budget decreases, the buffer status report is updated and reported.
  • the remaining delay budget of the data to be transmitted will be controlled to be reduced so that the data to be transmitted can be transmitted from the buffer in a shorter time, thereby realizing emergency scheduling of this part of the data to be transmitted.
  • the remaining delay budget of data packet A is 5ms.
  • the remaining delay budget of data packet A is controlled to change from 5ms to 2ms, so as to control data packet A to be transmitted from the buffer within the remaining 2ms, thereby completing the emergency scheduling of data packet A.
  • the re-reported BSR carries the information that the remaining delay budget of the data to be transmitted is reduced, so that the network can authorize the UE to transmit the transmission resources of this part of the data to be transmitted as soon as possible according to the re-reported BSR, and complete the emergency scheduling of the data to be transmitted in the buffer.
  • a BSR report may be performed when the remaining delay budget of the amount of data to be transmitted is less than or equal to a certain threshold.
  • the predetermined threshold may be obtained from the core network and notified to the UE through the gNB (the next Generation Node B, 5G base station); or it may be based on network agreement.
  • the remaining delay budget of the amount of data to be transmitted is less than or equal to a certain threshold, it indicates that the data to be transmitted in the buffer needs to be transmitted out of the buffer urgently.
  • BSR reporting can be performed so that the network can authorize transmission resources for this part of the data to be transmitted in a timely manner based on the updated reported BSR message.
  • FIG. 4 shows a buffer status report reporting method according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG. 4 , the buffer status report reporting method includes the following steps.
  • step S401 when the amount of data to be transmitted decreases, resulting in an increase in the remaining delay budget, an update report of the buffer status report is performed.
  • the PDCP layer performs a batch packet loss operation, which causes the amount of data to be transmitted in the buffer to decrease.
  • the remaining delay budget will increase.
  • the BSR can be updated and reported.
  • the remaining delay budget of the amount of data to be transmitted is 2ms, but within these 2ms, a batch packet loss operation is performed at the PDCP layer, resulting in the loss of all data in the buffer, and after new data enters the buffer, the remaining delay budget can reach 10ms.
  • the remaining delay budget is larger than the remaining delay budget before the batch packet loss operation is performed, and an update report of the BSR is required.
  • the BSR re-reported by the UE indicates the amount of data to be transmitted and/or the remaining delay budget of the data to be transmitted of the newly arrived buffer.
  • the network can authorize the UE to have transmission resources that match the amount of data to be transmitted in the buffer.
  • the network can know that the data in the buffer does not need to be urgently scheduled out, and the network does not need to quickly allocate transmission resources for the data to be transmitted in the UE buffer, and can allocate transmission resources to the remaining UEs.
  • the remaining delay budget allocated by the UE for the 1000-bit data in the buffer at the beginning is 10ms.
  • the remaining delay budget for the 1000-bit data to be transmitted in the buffer is 2ms, that is, the 1000-bit data to be transmitted has 2ms to expire before it can be transmitted from the buffer.
  • the network actively deletes the 1000-bit data to be transmitted, and 1000 bits of data arrive in the buffer within 2ms, the remaining delay budget for the newly arrived 1000 bits of data to be transmitted is 10ms.
  • the remaining delay budget increases, the amount of data to be transmitted in the buffer does not change. Based on the same amount of data, there is no need to update and report the BSR.
  • the network can authorize transmission resources for the UE based on the 1000-bit data.
  • the BSR is updated and reported, and a smaller remaining delay budget can be sent to the network, so that the network can allocate transmission resources to the UE as soon as possible based on the updated reported remaining delay budget, so as to realize the emergency scheduling of the UE for the data to be transmitted;
  • the BSR is updated and reported, and the amount of data to be transmitted and/or the remaining budget delay of the amount of data to be transmitted in the new buffer to be transmitted can be sent to the network
  • the network can allocate transmission resources matching the data to the new buffer to the UE based on the updated reported remaining delay budget, and on the other hand, the network knows that the data to be transmitted in the UE buffer does not need to be urgently scheduled based on the updated reported remaining delay budget, and can allocate transmission resources to other UEs.
  • FIG3 and FIG4 can be a separate embodiment, or the two can be combined to form a new embodiment.
  • the network will authorize transmission resources for the UE faster based on the updated reported BSR;
  • the PDCP layer packet loss causes the amount of new data to be transmitted in the buffer to increase, which will cause the network to authorize the UE with transmission resources that match the amount of new data to be transmitted in the buffer based on the updated reported BSR.
  • FIG. 5 shows a buffer status report reporting method according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG. 5 , the buffer status report reporting method includes the following steps.
  • step S501 in response to a change in the amount of data to be transmitted of at least one logical channel or at least one logical channel group of the user equipment, an update report of a buffer status report is performed.
  • the user equipment and the network equipment communicate through at least one logical channel or at least one logical channel group.
  • Each logical channel or logical channel group corresponds to its own buffer.
  • the BSR is updated and reported.
  • the amount of data to be transmitted of the UE can be counted from the amount of data to be transmitted in the buffer of at least one logical channel or at least one logical channel group or all logical channels.
  • BSR re-reporting when the amount of data to be transmitted of at least one logical channel changes, BSR re-reporting can be triggered; when the total amount of data to be transmitted of all logical channels in at least one logical channel group changes, BSR re-reporting can be triggered; when the total amount of data to be transmitted of all logical channels changes, BSR re-reporting can be triggered.
  • the BSR can be re-reported so that the network can allocate transmission resources matching the changed amount of data to be transmitted to the UE based on the changed amount of data to be transmitted indicated in the re-reported BSR.
  • FIG. 6 shows a buffer status report reporting method according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG. 6 , the buffer status report reporting method includes the following steps.
  • step S601 in response to a change in at least one of the amount of data to be transmitted of the user equipment and the remaining delay budget of the amount of data to be transmitted, the buffer status report reported to the network device is updated to any one of the regular buffer status reports or to the second type of buffer status report.
  • the BSR after the update report can be any type of regular BSR, such as the first type of regular BSR or the second type of regular BSR mentioned above, or it can be named as another new type of BSR, such as an updated BSR.
  • the network configures the UE or the protocol stipulates that when at least one of the following conditions exists: the amount of data to be transmitted changes, the remaining delay budget of the amount of data to be transmitted changes, and the remaining delay budget of the amount of data to be transmitted is less than or equal to a predetermined threshold, when reporting a BSR update, the BSR may be associated with a specified logical channel ID or a new logical channel ID; after receiving the BSR, the base station may identify the type of BSR through the logical channel ID.
  • the association with the specified logical channel ID or the new logical channel ID may be identified by using a reserved LCH (Logical Channel) ID.
  • a new logical channel ID may be configured separately for a long BSR (Long BSR) and a short BSR (Short BSR).
  • FIG. 7 shows a buffer status report reporting method according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG. 7 , the buffer status report reporting method includes the following steps.
  • step S701 when at least one of the amount of data to be transmitted of the user equipment and the remaining delay budget of the data to be transmitted changes and the user equipment is configured with a buffer status report update function, a buffer status report is updated and reported.
  • the buffer status report update function is a function of re-reporting the BSR when at least one of the amount of data to be transmitted of the user equipment and the remaining delay budget of the amount of data to be transmitted changes.
  • the BSR report may be performed for the first time.
  • the BSR can be reported for the first time; if the remaining delay budget for the amount of data to be transmitted in the UE increases from zero to a certain amount, the first BSR can also be reported. In this way, the network can authorize transmission resources for the UE based on the amount of data to be transmitted and/or the remaining delay budget indicated in the first reported BSR.
  • FIG8 shows a buffer status report reporting method according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG8 , the buffer status report reporting method includes the following steps.
  • step S801 when at least one of the amount of data to be transmitted of the user equipment and the remaining delay budget of the amount of data to be transmitted changes and the reporting value of the buffer status report changes, the buffer status report is updated and reported.
  • the BSR is updated and reported, which causes the UE to frequently report the BSR, resulting in a waste of network resources.
  • the BSR is updated and reported, which reduces the number of BSR reports and reduces the waste of network resources.
  • the reported values of BSR are 1 and 2
  • the range of the amount of data to be transmitted corresponding to 1 is [0, 1000]
  • the range of the amount of data to be transmitted corresponding to 2 is [1001, 2000].
  • the reported value of BSR will not change, and the UE will not update the BSR report.
  • the amount of data to be transmitted changes to 1500, which is within the range of [1001, 2000]
  • the reported value of BSR will change from 1 to 2, and the UE will update the BSR report at this time.
  • the present invention will only update and report the BSR message when the amount of data to be transmitted and/or the remaining delay budget changes, and the reporting value of the BSR changes, so as to make the conditions for updating and reporting the BSR message more stringent, reduce the number of BSR update reports, and reduce the waste of network resources.
  • the BSR is updated and reported. This can make the BSR update reporting conditions more stringent, reduce the number of BSR message reports, and avoid the waste of network resources caused by frequent reporting of BSR messages.
  • FIG. 9 shows a buffer status report reporting method according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG. 9 , the buffer status report reporting method includes the following steps.
  • step S901 when at least one of the amount of data to be transmitted of the user equipment and the remaining delay budget of the amount of data to be transmitted changes and a prohibition timer configured for the user equipment is not running, an update report of a buffer status report is performed.
  • the prohibit timer is a timer used to prohibit BSR message reporting. During the period when the prohibit timer is running, the UE cannot update and report the BSR message; during the period when the prohibit timer is not running, the UE can update and report the BSR message.
  • the running time of the prohibition timer is 3ms. Within 3ms of the prohibition timer running, even if the amount of data to be transmitted and/or the remaining delay budget of the UE changes, the UE will not update the BSR message; after the prohibition timer runs for 3ms, if the amount of data to be transmitted and/or the remaining delay budget of the UE changes, the UE can update the BSR message.
  • the UE can be prohibited from updating and reporting the BSR message during the operation of the prohibition timer, thereby reducing the number of reports of the BSR message and reducing the waste of network resources.
  • the UE can report the BSR during the period when the prohibition timer is not running, and the last number of BSR messages is reduced, thereby avoiding the waste of network resources caused by frequent reporting of BSR messages.
  • FIG. 7 , FIG. 8 , and FIG. 9 can be separate embodiments, or can be combined in pairs or in groups of three to form new embodiments.
  • the BSR message is updated and reported.
  • the UE updates and reports the BSR message only when the prohibition timer is not running and the reported value of the BSR message changes, so that the update reporting of the BSR message is more stringent than the separate steps S602 or S603, further avoiding the waste of network resources caused by frequent reporting of BSR messages.
  • FIG. 10 shows a method for reporting a buffer status report according to an exemplary embodiment.
  • the method is executed by a user equipment. As shown in FIG. 10 , the method includes the following steps.
  • step S1001 a signaling for instructing the user equipment to enable the buffer status report update function is received.
  • the user equipment may receive a signaling to enable a buffer status report update function, that is, the UE may receive a signaling of a BSR update function, and after receiving the signaling, the UE may enable the BSR update function.
  • the BSR update function may be effective on all logical channels and/or logical channel groups of the UE.
  • the UE may implicitly determine that it can use the BSR update function.
  • the UE when the UE receives a threshold value of a change in the amount of data to be transmitted sent by the network, it can determine that the UE can enable the BSR update function.
  • the UE determines that the BSR update function can be used only when the periodic BSR is not triggered, it determines that it can enable the BSR update function. If the UE is configured with a periodic BSR, the BSR can be reported periodically, and there is no need to use the BSR update function proposed in the present disclosure. Therefore, when using the BSR update function proposed in the present disclosure, the use of the periodic BSR can be prohibited. Moreover, compared with the periodic BSR, the conditions for reporting the BSR are more stringent when enabling the BSR update function, so that the overhead of the UE reporting the BSR is relatively small.
  • step S1002 the buffer status report update function is enabled to update and report the buffer status report.
  • the BSR is updated and reported.
  • the BSR update function can be effective at each UE granularity, so that when at least one of the amount of data to be transmitted and the remaining delay budget of the amount of data to be transmitted changes on all configured logical channels or logical channel groups facing the UE, the BSR is updated and reported.
  • FIG. 11 shows a method for reporting a buffer status report according to an exemplary embodiment.
  • the method is executed by a user equipment. As shown in FIG. 11 , the method includes the following steps.
  • step S1101 a signaling for instructing a radio bearer of the user equipment to enable the buffer status report update function is received.
  • Radio Bearer is the service provided by L2 to the upper layer between UE and UTRAN (UMTS Terrestrial Radio Access Network).
  • UE can receive signaling for indicating that the UE's radio bearer enables the BSR update function, so that all logical channels or logical channel groups associated with the UE's radio bearer can enable the BSR update function.
  • the wireless bearer is used to carry XR services
  • the XR services have multiple types of data packets
  • the first type of data packets are transmitted using the first logical channel
  • the second type of data packets are transmitted using the second logical channel
  • these two logical channels are the logical channels associated with the wireless bearer.
  • the association between the logical channel group and the wireless bearer can also be determined in this way, which will not be repeated here.
  • the network may configure in advance which logical channels and logical channel groups are associated with the UE's radio bearer.
  • the UE may implicitly determine that the radio bearer can enable the BSR update function.
  • the UE when the UE receives a threshold value of a change in the amount of data to be transmitted from the network for a certain radio bearer, it can be implicitly determined that the radio bearer can enable the BSR update function.
  • step S1102 the buffer status report update function is enabled to update and report the buffer status report.
  • the BSR update function if the UE determines that the amount of data to be transmitted in the buffer of the logical channel and/or logical channel group associated with the radio bearer has changed, or the remaining delay budget has changed, the BSR is updated and reported.
  • the BSR update function can be effective at each wireless bearer granularity, so that the UE can update and report the BSR when at least one of the amount of data to be transmitted on the wireless bearer and the remaining delay budget of the data to be transmitted changes.
  • FIG. 12 shows a method for reporting a buffer status report according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG. 12 , the method includes the following steps.
  • step S1201 a signaling for indicating that a logical channel or a logical channel group of the user equipment enables the buffer status report updating function is received.
  • the UE may receive signaling for indicating that a logical channel enables a BSR update function, or may receive signaling for indicating that a logical channel group enables a BSR update function.
  • the UE may receive signaling for indicating a first logical channel or a first logical channel group of the user equipment to enable the buffer status report update function.
  • the protocol stipulates that the terminal enables the BSR update function for the first logical channel or the first logical channel group.
  • the first logical channel is a specific logical channel
  • the first logical channel group is a specific logical channel group.
  • the specific logical channel is a logical channel configured to use a specific type of BSR table, such as the second BSRtable (second BSR table), for BSR reporting
  • the specific logical channel group is a logical channel group configured to use a specific type of BSR table, such as the second BSRtable, for BSR reporting.
  • the second BSRtable is a table that maps the newly introduced Buffersize (buffer amount) for the XR service to different quantization levels.
  • the second BSRtable has a mapping relationship between the buffer amount and the buffer amount quantization level.
  • the UE may implicitly determine that a logical channel or a logical channel group can enable the BSR update function.
  • the UE when the UE receives the network's threshold for the change in the amount of data to be transmitted for a logical channel, it can be determined that the logical channel can enable the BSR update function; when the UE receives the network's threshold for the change in the amount of data to be transmitted for a logical channel group, it can be determined that the logical channel group can enable the BSR update function.
  • step S1202 the buffer status report update function is enabled to update and report the buffer status report.
  • the BSR update report is performed.
  • the logical channel group enables the BSR update function, if the UE determines that the amount of data to be transmitted in the logical channel group buffer changes or the remaining delay budget changes, the BSR update report is performed.
  • the BSR update function can be effective at the granularity of each logical channel or each logical channel group, so that the UE can update and report the BSR when at least one of the amount of data to be transmitted of the logical channel or logical channel group and the remaining delay budget of the amount of data to be transmitted changes.
  • FIG. 10 the embodiment shown in FIG. 11 , and the embodiment shown in FIG. 12 may be separate embodiments, or may be combined in pairs to form a new embodiment, or the three embodiments may form a new embodiment.
  • FIG. 13 shows a buffer status report reporting method according to an exemplary embodiment. The method is executed by a user equipment. As shown in FIG. 13 , the method includes the following steps.
  • step S1301 the auxiliary information of the user equipment is reported to a network device.
  • the auxiliary information includes at least one of the following: whether the user equipment supports the capability of using a buffer status report update function, and whether the user equipment expects to use the buffer status report update function.
  • the UE may have a first type BSR reporting capability and a second type BSR reporting capability.
  • the first type BSR reporting capability is the ability to update and report the BSR when at least one of the amount of data to be transmitted and the remaining delay budget of the amount of data to be transmitted changes;
  • the second type BSR reporting capability is the reporting capability of the above-mentioned regular BSR, periodic BSR, retransmission BSR and padding BSR.
  • the UE When the UE receives authorization for excess data to be transmitted, it indicates that the UE desires to enable the BSR update function. At this time, the network will configure the BSR update function for the UE.
  • the network may allocate more authorizations to the UE according to the original data volume, but the terminal does not need so many authorizations.
  • the UE receives the authorization for the excess data to be transmitted, and the UE realizes that the amount of data to be transmitted reported in the BSR message obtained by the network is large. Therefore, the UE can report auxiliary information in the hope of enabling the BSR update function to avoid the network allocating authorizations for the excess data to be transmitted to the UE.
  • the transmission resources can be understood as uplink transmission resources.
  • the UE needs to use the uplink transmission resources to transmit the pending data in the buffer to the network.
  • step S1302 in response to a change in at least one of the amount of data to be transmitted of the user equipment and the remaining delay budget of the amount of data to be transmitted, an update report of a buffer status report is performed.
  • the network will configure the BSR update function for the UE.
  • the network and the UE can also agree on the BSR update function through a protocol.
  • the UE can respond to changes in at least one of the amount of data to be transmitted and the remaining delay budget of the amount of data to be transmitted, and report the BSR update.
  • the UE can report the UE's auxiliary information to the network device to indicate that the UE itself has the ability to enable the BSR update function and/or expects to use the BSR update function, so that the network can configure the BSR update function for the UE based on the auxiliary information.
  • FIG. 14 shows a method for reporting a buffer status report according to an exemplary embodiment.
  • the method is executed by a network device. As shown in FIG. 14 , the method includes the following steps.
  • step S1401 a buffer status report updated and reported by a user equipment is received.
  • the network device proposed in any embodiment of the present disclosure can be a device for communicating with a user device.
  • the network device can also be called an access network device or a wireless access network device. It can be a transmission reception point (TRP), an evolved base station (evolved NodeB, eNB or eNodeB) in an LTE system, a home base station (for example, home evolved NodeB, or home Node B, HNB), a baseband unit (base band unit, BBU), or a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario, or the network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a 5G network, or a network device in a future evolved PLMN network, etc. It can be an access point (access point, AP) in a WLAN, or a gNB of NR, and the embodiments of the present application are not limited.
  • TRP transmission reception point
  • eNB
  • This step may refer to the above step S101 and will not be described in detail here.
  • the network device can allocate transmission resources that match the changed amount of data to be transmitted and/or the remaining delay budget of the data to be transmitted to the UE based on the changed amount of data to be transmitted and/or the remaining delay budget of the data to be transmitted, thereby avoiding the situation where the transmission resources allocated by the network device exceed the transmission resources required by the UE, thereby reducing the waste of transmission resources.
  • FIG. 15 is a buffer status report reporting method according to an exemplary embodiment. The method is executed by a network device. As shown in FIG. 15 , the method includes the following steps.
  • step S1501 a buffer status report updated and reported by a user equipment is received.
  • This step may refer to the above step S101 and will not be described in detail here.
  • step S1502 a change in at least one of an amount of data to be transmitted of the user equipment and a remaining delay budget of the amount of data to be transmitted is determined according to the buffer status report.
  • This step may refer to the above step S101 and will not be described in detail here.
  • FIG. 16 shows a method for reporting a buffer status report according to an exemplary embodiment. The method is executed by a network device. As shown in FIG. 16 , the method includes the following steps.
  • step S1601 a buffer status report updated and reported by a user equipment is received.
  • This step may refer to the above step S101 and will not be described in detail here.
  • step S1602 it is determined, based on the buffer status report, that the change value of the amount of data to be transmitted is greater than a change threshold of the amount of data to be transmitted.
  • This step may refer to the above step S201 and will not be described again here.
  • the network device will receive the BSR updated and reported by the UE only when the change value of the amount of data to be transmitted of the UE is greater than the change threshold of the amount of data to be transmitted.
  • the number of times the network device receives BSR reports is reduced, thereby reducing the waste of network resources.
  • FIG. 17 shows a method for reporting a buffer status report according to an exemplary embodiment.
  • the method is executed by a network device. As shown in FIG. 17 , the method includes the following steps.
  • step S1701 a buffer status report updated and reported by a user equipment is received.
  • This step may refer to the above step S101 and will not be described in detail here.
  • step S1702 it is determined, based on the buffer status report, that a decrease in the remaining delay budget and/or a decrease in the amount of data to be transmitted leads to an increase in the remaining delay budget.
  • This step may refer to the above-mentioned step S301 and step S401, which will not be described in detail here.
  • the BSR is updated and reported, and a smaller remaining delay budget can be sent to the network, so that the network can allocate transmission resources to the UE as soon as possible based on the updated reported remaining delay budget to achieve emergency scheduling of the data to be transmitted;
  • the BSR is updated and reported, and the amount of data to be transmitted and/or the remaining budget delay of the amount of data to be transmitted that has newly arrived in the buffer zone can be sent to the network, and the network can allocate transmission resources to the UE that match the data to be transmitted that has newly arrived in the buffer zone based on the updated reported remaining delay budget.
  • FIG. 18 is a buffer status report reporting method according to an exemplary embodiment. The method is executed by a network device. As shown in FIG. 18 , the method includes the following steps.
  • step S1801 a buffer status report updated and reported by a user equipment is received.
  • This step may refer to the above step S101 and will not be described in detail here.
  • step S1802 a change in the amount of data to be transmitted of at least one logical channel or at least one logical channel group of the user equipment is determined according to the buffer status report.
  • This step may refer to the above step S501 and will not be described in detail here.
  • an updated reported BSR can be received and re-reported, and the network allocates matching transmission resources to the UE based on the changed amount of data to be transmitted indicated in the re-reported BSR.
  • FIG. 19 is a buffer status report reporting method according to an exemplary embodiment. The method is executed by a network device. As shown in FIG. 19 , the method includes the following steps.
  • step S1901 the buffer status report updated by the user equipment is received as any one of the regular buffer status reports, or the buffer status report updated by the user equipment is received as the second type.
  • This step may refer to the above step S601 and will not be described in detail here.
  • FIG. 20 is a buffer status report reporting method according to an exemplary embodiment. The method is executed by a network device. As shown in FIG. 20 , the buffer status report reporting method includes the following steps.
  • step S2001 a signaling for instructing the user equipment to enable a buffer status report update function is sent to the user equipment.
  • the network device if the network device knows that the UE is a UE performing XR services, it will send a signaling for instructing the UE to enable the BSR update function to the UE, notifying the UE to enable the BSR update function.
  • the BSR update function takes effect on all logical channels or logical channel groups of the UE.
  • the network device may implicitly notify the UE to enable the BSR update function.
  • the network device may notify the UE of a threshold value of a change in the amount of data to be transmitted for a certain logical channel or a certain logical channel group.
  • the network device may also notify the UE to use the BSR update function when the periodic BSR is not configured, thereby implicitly notifying the UE to enable the BSR update function.
  • step S2002 a buffer status report updated and reported by a user equipment is received.
  • This step may refer to the above step S101 and will not be described in detail here.
  • the network can configure the BSR update function for the UE to take effect at each UE granularity, so that the UE updates and reports the BSR when at least one of the amount of data to be transmitted by the UE and the remaining delay budget of the amount of data to be transmitted changes.
  • FIG. 21 is a buffer status report reporting method according to an exemplary embodiment. The method is executed by a network device. As shown in FIG. 21 , the buffer status report reporting method includes the following steps.
  • step S2101 a signaling for instructing the radio bearer of the user equipment to enable a buffer status report update function is sent to the user equipment.
  • the network device if the network device knows that the UE is a UE performing XR services, it will send a signaling for instructing the radio bearer to enable the BSR update function to the UE, notifying the radio bearer that the BSR update function can be enabled.
  • the BSR update function takes effect on all logical channels or logical channel groups associated with the radio bearer.
  • the network device may implicitly notify the radio bearer to enable the BSR update function.
  • the network device may notify the UE of a threshold of a change in the amount of data to be transmitted of at least one logical channel or at least one logical channel group associated with the radio bearer, thereby implicitly notifying the radio bearer to enable a BSR update function.
  • step S2102 a buffer status report updated and reported by the user equipment is received.
  • This step may refer to the above step S101 and will not be described in detail here.
  • the network can configure the BSR update function for the UE to take effect at each wireless bearer granularity, so that the UE updates and reports the BSR when at least one of the amount of data to be transmitted on the wireless bearer and the remaining delay budget of the data to be transmitted changes.
  • FIG. 22 is a buffer status report reporting method according to an exemplary embodiment. The method is executed by a network device. As shown in FIG. 22 , the buffer status report reporting method includes the following steps.
  • step S2201 a signaling is sent to the user equipment for indicating that a logical channel or a logical channel group of the user equipment enables the buffer status report update function.
  • the network device if it knows that the UE is a UE performing XR services, it will send a signaling to the UE to indicate that the logical channel enables the BSR update function, notifying the logical channel to enable the BSR update function; it may also send a signaling to the UE to indicate that the logical channel group enables the BSR update function, notifying the logical channel group to enable the BSR update function.
  • the network device may implicitly notify the UE that the logical channel or logical channel group may enable the BSR update function.
  • the network device may notify the UE of a threshold value of a change in the amount of data to be transmitted of at least one logical channel or at least one logical channel group, thereby implicitly notifying the logical channel or logical channel group to enable a BSR update function.
  • step S2202 a buffer status report updated and reported by the user equipment is received.
  • This step may refer to the above step S101 and will not be described in detail here.
  • the network configures the BSR update function for the UE to take effect at the granularity of each logical channel or each logical channel group, so that the UE updates and reports the BSR when at least one of the amount of data to be transmitted of the logical channel or logical channel group and the remaining delay budget of the amount of data to be transmitted changes.
  • FIG. 23 is a buffer status report reporting method according to an exemplary embodiment. The method is executed by a network device. As shown in FIG. 20 , the buffer status report reporting method includes the following steps.
  • step S2301 auxiliary information sent by the user equipment is received.
  • the auxiliary information includes at least one of the following: whether the user equipment supports the capability of using a buffer status report update function, and whether the user equipment expects to use the buffer status report update function.
  • This step may refer to the above-mentioned step S1301 and will not be described in detail here.
  • the network device can receive the auxiliary information reported by the UE to determine whether the UE itself has the ability to enable the BSR update function and/or expects to use the BSR update function, thereby configuring the BSR update function for the UE based on the auxiliary information.
  • FIG. 24 is a buffer status report reporting device according to an exemplary embodiment, and the device is executed by a user equipment. As shown in FIG. 24 , the buffer status report reporting device 240 includes a buffer status report sending module 241 .
  • the buffer status report sending module 241 is configured to update and report the buffer status report in response to a change in at least one of the amount of data to be transmitted of the user equipment and the remaining delay budget of the amount of data to be transmitted.
  • the buffer status report sending module 241 includes:
  • the first buffer status report sending submodule is configured to update and report the buffer status report in response to the change value of the amount of data to be transmitted being greater than a change threshold of the amount of data to be transmitted.
  • the buffer status report sending module 241 includes:
  • a second buffer status report sending submodule is configured to update and report the buffer status report when the remaining delay budget decreases, and/or;
  • the third buffer status report sending submodule is configured to update and report the buffer status report when the amount of data to be transmitted decreases, resulting in an increase in the remaining delay budget.
  • the buffer status report sending module 241 includes:
  • the fourth buffer status report sending submodule is configured to update and report the buffer status report in response to a change in the amount of data to be transmitted of at least one logical channel or at least one logical channel group of the user equipment.
  • the buffer status report sending module 241 includes:
  • the fifth buffer status report sending submodule is configured to update the buffer status report reported to the network device to any one of the conventional buffer status reports or to the second type of buffer status report.
  • the buffer status report sending module 241 includes:
  • the sixth buffer status report sending submodule is configured to update and report the buffer status report when at least one of the amount of data to be transmitted of the user equipment and the remaining delay budget of the amount of data to be transmitted changes and at least one of the following conditions exists:
  • the user equipment is configured with a buffer status report update function, the reporting value of the buffer status report changes, and a prohibition timer configured for the user equipment is not running.
  • the buffer status report sending module 241 includes:
  • a sixth buffer status report sending submodule configured to enable a buffer status report update function and perform update reporting of the buffer status report
  • the enabling of the buffer status report update function is determined by at least one of the following conditions:
  • a signaling is received for indicating that a logical channel or a logical channel group of the user equipment enables the buffer status report update function.
  • the buffer status report reporting device 240 includes:
  • the auxiliary information reporting submodule is configured to report the auxiliary information of the user equipment to the network device, wherein the auxiliary information includes at least one of the following:
  • FIG. 25 is a buffer status report reporting device according to an exemplary embodiment, and the device is executed by a user equipment. As shown in FIG. 25 , the buffer status report reporting device 250 includes a buffer status report receiving module 251 .
  • the buffer status report receiving module 251 is configured to receive a buffer status report updated and reported by a user equipment.
  • the buffer status report receiving module 251 includes:
  • a first buffer status report receiving submodule configured to receive a buffer status report updated and reported by a user equipment
  • the first report determination submodule is configured to determine, based on the buffer status report, a change in at least one of an amount of data to be transmitted of the user equipment and a remaining delay budget of the amount of data to be transmitted.
  • the first report determination submodule includes:
  • the second report determination submodule is configured to determine, based on the buffer status report, that the change value of the amount of data to be transmitted is greater than a threshold value of the change of the amount of data to be transmitted.
  • the first report determination submodule includes:
  • the third report determination submodule is configured to determine, based on the buffer status report, that a decrease in the remaining delay budget and/or a decrease in the amount of data to be transmitted causes an increase in the remaining delay budget.
  • the first report determination submodule includes:
  • the fourth report determination submodule is configured to determine a change in the amount of data to be transmitted of at least one logical channel or at least one logical channel group of the user equipment according to the buffer status report.
  • the buffer status report receiving module 251 includes:
  • the second buffer status report receiving submodule is configured to receive any buffer status report in the conventional buffer status report updated by the user equipment, or to receive a buffer status report of the second type updated by the user equipment.
  • the buffer status report reporting device 250 includes:
  • a first indication submodule is configured to send a signaling to the user equipment for instructing the user equipment to enable a buffer status report update function, and/or;
  • a second indication submodule is configured to send a signaling for indicating that a radio bearer of the user equipment enables a buffer status report update function to the user equipment, and/or;
  • the third indication submodule is configured to send a signaling to the user equipment for indicating that a logical channel or a logical channel group of the user equipment enables the buffer status report update function.
  • the first indication submodule includes:
  • the first data sending submodule is configured to send a threshold value of a change in the amount of data to be transmitted of the user equipment to the user equipment, and to instruct the user equipment to use a buffer status report update function when a periodic buffer status report is not configured.
  • the second indication submodule includes:
  • the second data sending submodule is configured to send a threshold value of a change in the amount of data to be transmitted of the radio bearer to the radio bearer.
  • the third indication submodule includes:
  • the third data sending submodule is configured to send a threshold value of a change in the amount of data to be transmitted of the logical channel or the logical channel group to the logical channel or the logical channel group.
  • the buffer status report reporting device 250 includes:
  • the auxiliary information receiving module is configured to receive the auxiliary information sent by the user equipment, wherein the auxiliary information includes at least one of the following:
  • Fig. 26 is a block diagram of a user equipment device 800 according to an exemplary embodiment.
  • the device 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
  • the apparatus 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input/output interface 812 , a sensor component 814 , and a communication component 816 .
  • the processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method.
  • the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components.
  • the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.
  • the memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc.
  • the memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • the power supply component 806 provides power to the various components of the device 800.
  • the power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 800.
  • the multimedia component 808 includes a screen that provides an output interface between the device 800 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 touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
  • the multimedia component 808 includes a front camera and/or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
  • the audio component 810 is configured to output and/or input audio signals.
  • the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal can be further stored in the memory 804 or sent via the communication component 816.
  • the audio component 810 also includes a speaker for outputting audio signals.
  • the input/output interface 812 provides an interface between the processing component 802 and the peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.
  • the sensor assembly 814 includes one or more sensors for providing various aspects of the status assessment of the device 800.
  • the sensor assembly 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800, and the sensor assembly 814 can also detect the position change of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration/deceleration of the device 800, and the temperature change of the device 800.
  • the sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact.
  • the sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices.
  • the device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.
  • the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication.
  • 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
  • the apparatus 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • controllers microcontrollers, microprocessors or other electronic components to perform the above method.
  • a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the device 800 to perform the above method.
  • the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
  • the above-mentioned device can also be a part of an independent electronic device.
  • the device can be an integrated circuit (IC) or a chip, wherein the integrated circuit can be an IC or a collection of multiple ICs; the chip can include but is not limited to the following types: GPU (Graphics Processing Unit), CPU (Central Processing Unit), FPGA (Field Programmable Gate Array), DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), SOC (System on Chip, SoC), etc.
  • the above-mentioned integrated circuit or chip can be used to execute executable instructions (or codes) to implement the above-mentioned resource selection method.
  • the executable instructions can be stored in the integrated circuit or chip, or can be obtained from other devices or equipment, for example, the integrated circuit or chip includes a processor, a memory, and an interface for communicating with other devices.
  • the executable instruction may be stored in the memory, and when the executable instruction is executed by the processor, the above-mentioned resource selection method is implemented; alternatively, the integrated circuit or chip may receive the executable instruction through the interface and transmit it to the processor for execution, so as to implement the above-mentioned resource selection method.
  • a computer program product is further provided.
  • the computer program product includes a computer program executable by a programmable device.
  • the computer program has a code portion for executing the above resource selection method when executed by the programmable device.
  • FIG. 27 is a block diagram of a network device 1900 according to an exemplary embodiment.
  • the network device 1900 may be provided as a base station.
  • the network device includes a processing component 1922, which further includes one or more processors, and a memory resource represented by a memory 1932 for storing instructions that can be executed by the processing component 1922, such as an application.
  • the application stored in the memory 1932 may include one or more modules each corresponding to a set of instructions.
  • the processing component 1922 is configured to execute instructions to perform the above-mentioned resource selection method.
  • the network device 1900 may also include a power component 1926 configured to perform power management of the device 1900 , a wired or wireless network interface 1950 configured to connect the network device 1900 to a network, and an input/output interface 1958 .
  • the network configures the terminal or the protocol stipulates the operating mechanism for the terminal to report the latest BSR.
  • the network configures the terminal or the protocol stipulates a mechanism for reporting the latest BSR when the amount of terminal data increases or decreases.
  • an increase in the amount of data to be transmitted means the arrival of new data.
  • or the amount of data to be transmitted is reduced, such as discarding PDCP.
  • the change in the amount of data to be transmitted can be based on data packet statistics or data packet sets.
  • the amount of packet loss can be measured by the number of lost packets or the number of lost bits/bytes; the number of lost packets can be based on the number of Packets or the number of Packet Sets.
  • the amount of data to be transmitted can be determined by the terminal based on the data amount of the PDCP layer and/or RLC (Radio Link Control, wireless link layer control protocol).
  • RLC Radio Link Control, wireless link layer control protocol
  • a BSR report is made.
  • a BSR report is performed.
  • the threshold value can be obtained from the core network and notified to the UE through the gNB (the next Generation Node B, 5G base station); or it can be based on network agreement.
  • the gNB the next Generation Node B, 5G base station
  • a BSR report is performed.
  • the application scenario BSR reporting is to update the previously reported BSR (update its validity information).
  • the previously reported BSR carries the remaining delay budget information
  • the related fields in the next reported BSR are empty, which may mean that the previously reported BSR is no longer valid, or that the previously reported BSR carries the remaining delay budget information, which is no longer valid.
  • the network configures the terminal or the protocol stipulates that the terminal updates and reports the BSR after the amount of data to be transmitted changes.
  • the network configures the terminal or the protocol stipulates that the terminal reports a BSR when the amount of data to be transmitted changes.
  • the PDCP layer reports the BSR after performing a batch packet loss operation; (updated as long as there is this batch packet loss operation) wherein the batch packet loss operation will cause a change in the amount of data to be transmitted by the terminal, then the BSR is reported.
  • the network configures the terminal or the protocol stipulates that the terminal reports a BSR after the amount of data to be transmitted changes and exceeds a predetermined threshold.
  • the network configures the terminal or the protocol stipulates that the terminal performs a batch packet loss operation at the PDCP layer and the amount of packet loss data exceeds a predetermined threshold to report a BSR;
  • the change in the amount of data to be transmitted can be based on data packet statistics or data packet set statistics.
  • the amount of packet loss can be measured by the number of lost packets or the number of lost bits/bytes; the number of lost packets can be based on the number of Packets or Packet Sets.
  • the predetermined threshold value may be obtained from the core network and notified to the UE via the gNB (the next Generation Node B, 5G base station). Or it may be based on network agreement.
  • a BSR report is made.
  • the network can give transmission resources to the scheduling with higher scheduling urgency.
  • the statistics of changes in the amount of data to be transmitted can be based on the statistics of the amount of data to be transmitted of one logical channel or one or more logical channels of a logical channel group or all logical channels.
  • the BSR triggered by a change in the amount of data to be transmitted may be triggered based on a logical channel, that is, a change in the amount of data to be transmitted on a logical channel triggers the BSR.
  • the BSR triggered by a change in the amount of data to be transmitted can be triggered based on a logical channel group, that is, the BSR is triggered when the total amount of data to be transmitted of all logical channels in a logical channel group changes.
  • the network configuration terminal or the protocol stipulates that the terminal has at least one of the following conditions: the amount of data to be transmitted has changed, the remaining delay budget of the data to be transmitted has changed, or the remaining delay budget of the data to be transmitted is less than or equal to a threshold, and a BSR is reported, the reported BSR may be a regular BSR or a new type of BSR; for example, an updated BSR.
  • the network configures the terminal or the protocol stipulates that when the amount of data to be transmitted changes, or the remaining delay budget of the data to be transmitted changes, or the remaining delay budget of the data to be transmitted is less than or equal to the threshold, when the terminal reports a BSR, the BSR can be associated with a specified logical channel ID or a new logical channel ID; after receiving the base station, it can identify this type of BSR by the logical channel ID.
  • a new logical channel ID may be configured separately for a long BSR (Long BSR) and a short BSR (Short BSR).
  • the network configures the terminal or the protocol stipulates additional restrictive conditions for the terminal to update and report the BSR after a batch packet loss operation is performed at the PDCP layer.
  • the first report may be performed when conditions are met.
  • the terminal report can be configured or agreed upon by the protocol that the terminal report needs to comply with the prohibition timer restriction, that is, the terminal needs to report when the BSR reporting value changes and the prohibition timer is not running; the prohibition timer is started after reporting; the prohibition timer is configured by the network.
  • the base station Based on 1, the base station notifies the terminal to enable this feature through dedicated signaling or agreement.
  • Method 1 The enabling granularity can be per UE (each terminal) or the feature can be configured for a single UE to determine whether it is effective.
  • the function will be enabled; this means that it will take effect on all logical channels or logical channel groups of the UE.
  • Method 2 The enabling granularity can be per RB (per radio bearer) granularity or configuring each radio bearer to take effect.
  • the base station if the terminal is a terminal performing XR service, it notifies the terminal that it will enable the function for a specific RB; this means that the function is effective on all logical channels or logical channel groups associated with the RB.
  • Mode 3 The enabling granularity may be per logical channel (each logical channel) or logical channel group granularity.
  • the base station notifies the terminal that it enables the function for a specific logical channel or a logical channel group.
  • the notification method for enabling this function is explicit or implicit notification.
  • the network if the network notifies the packet loss threshold for a certain logical channel, it means that the function is enabled.
  • this function is only used when the periodic BSR trigger is not configured (if the periodic BSR report is configured, it can be updated in time, but the periodic BSR requires a large overhead.
  • the advantage of this method over the periodic BSR is that it is triggered based on threshold events and has a small reporting overhead).
  • the protocol stipulates that the terminal enables this function for a specific logical channel or logical channel group.
  • the specific logical channel or logical channel group is a logical channel or logical channel group configured to use a specific type of BSR table (second BSRtable) for BSR reporting.
  • the second BSR table is a table that maps the newly introduced Buffersize (buffer amount) for XR type services to different quantization levels.
  • the base station notifies the terminal through dedicated signaling that the function can be used based on the auxiliary information of the terminal;
  • the auxiliary information of the terminal includes whether the terminal supports the capability of using the function.
  • the terminal's auxiliary information includes whether the terminal expects to use the function (if the terminal finds that the base station often allocates authorizations that exceed actual data, it realizes that the BSR obtained by the network may be too large and will report auxiliary information to indicate expected use).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种缓冲状态报告上传方法、装置、设备、存储介质与芯片，涉及通信技术领域。包括：响应于用户设备的待传数据量与待传数据量的剩余时延预算中至少一者变化，进行缓冲状态报告的更新上报。通过该缓冲状态报告上传方法、装置、设备、存储介质与芯片，可以在批量丢包导致待传数据量变化与待传数据量的剩余时延预算中的至少一者变化的情况下，进行缓冲状态报告的更新上报，以使得网络依据更新的缓冲状态报告来为用户设备分配与待传数据匹配的传输资源，减少传输资源的浪费。

Description

缓冲状态报告上传方法、装置、设备、存储介质与芯片 技术领域
本公开涉及通信技术领域，尤其涉及一种缓冲状态报告上传方法、装置、设备、存储介质与芯片。
背景技术
在网络系统中，UE(终端)会在上行链路向网络上报BSR(Buffer Status reporting，缓冲状态报告)，BSR提供了UE的缓冲区中等待发送给网络的数据量，网络根据UE上报的BSR，为UE分配传输数据的传输资源。
其中，一个PDU set(Protocol Data Unit set，协议数据单元集合)中具有多个PDU(Protocol Data Unit，协议数据单元)；PDCP(Packet Data Convergence Protocol)，分组数据汇聚协议)层的discard(丢弃)机制中，PDCP层会以PDU set为最小丢弃单元，来进行PDU set的丢弃。
发明内容
本公开提供一种缓冲状态报告上传方法、装置、设备、存储介质与芯片。
根据本公开实施例的第一方面提供一种缓冲状态报告上报方法，所述方法被用户设备执行，所述方法包括：
响应于所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行缓冲状态报告的更新上报。
根据本公开实施例的第二方面提供一种缓冲状态报告上报方法，所述方法被网络设备执行，所述方法包括：
接收用户设备更新上报的缓冲状态报告。
根据本公开实施例的第三方面提供一种缓冲状态报告上报装置，所述装置被配置在用户设备，所述装置包括：
缓冲状态报告发送模块，被配置为响应于所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行缓冲状态报告的更新上报。
根据本公开实施例的第四方面提供一种缓冲状态报告上报装置，所述装置被配置在网络设备，所述装置包括：
缓冲状态报告接收模块，被配置为接收用户设备更新上报的缓冲状态报告。
根据本公开实施例的第五方面提供一种用户设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为在执行所述可执行指令时，实现本公开实施例的第一方面提供的缓冲状态报告上报方法的步骤。
根据本公开实施例的第六方面提供一种网络设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为在执行所述可执行指令时，实现本公开实施例的第二方面提供的缓冲状态报告上报方法的步骤。
根据本公开实施例的第七方面提供一种计算机可读存储介质，其上存储有计算机程序指令，该程序指令被处理器执行时实现本公开实施例的第一方面提供的缓冲状态报告上报方法的步骤，或本公开实施例的第二方面提供的缓冲状态报告上报方法的步骤。
根据本公开实施例的第八方面提供一种芯片，包括处理器和接口；所述处理器用于读取指令以执行本公开实施例的第一方面提供的缓冲状态报告上报方法的步骤，或执行本公开实施例的第二方面提供的缓冲状态报告上报方法的步骤。
通过上述技术方案，在UE的待传数据量与待传数据量的剩余时延预算中的至少一者变化的情况下，代表PDCP层可能丢弃了PDU set中的PDU，导致待传数据量和/或待传数据量的剩 余时延预算发生了变化，此时为了避免网络授权UE多余的传输资源，可以重新上报BSR，重新上报的BSR中携带了变化后的待传数据量和/或待传数据量的剩余时延预算，如此网络可以依据变化后的待传数据量和/或待传数据量的剩余时延预算，来为UE分配与待传数据量相匹配的传输资源，而不会分配过多的传输资源，避免了传输资源的浪费。
附图说明
图1是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图2是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图3是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图4是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图5是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图6是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图7是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图8是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图9是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图10是根据一示例性实施例示出的一种切换时延确定方法的流程图。
图11是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图12是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图13是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图14是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图15是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图16是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图17是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图18是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图19是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图20是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图21是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图22是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图23是根据一示例性实施例示出的一种缓冲状态报告上报方法的流程图。
图24是根据一示例性实施例示出的一种缓冲状态报告上报装置的框图。
图25是根据一示例性实施例示出的一种缓冲状态报告上报装置的框图。
图26是根据一示例性实施例示出的一种用户设备的框图。
图27是根据一示例性实施例示出的一种网络设备的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
需要说明的是，本申请中所有获取信号、信息或数据的动作都是在遵照所在地国家相应的数据保护法规政策的前提下，并获得由相应装置所有者给予授权的情况下进行的。
为了便于理解，先介绍下本公开涉及的术语。
1、BSR(Buffer Status reporting，缓冲状态报告)，UE在向网络传输数据之前，需要向网络上报BSR，BSR提供了UE的缓冲区中等待发送给网络的数据量，网络根据UE上报的BSR，为UE分配传输数据的传输资源。
2、相关技术中存在以下多种触发BSR的机制，在不同机制下被触发的BSR被称为不同的BSR。
1)、第一类常规BSR(Regular BSR)，UE传输给网络的UL(Uplink，上行链路)数据属于一个逻辑信道，且该逻辑信道的优先级高于任何传输有UL数据的逻辑信道的优先级，也可以理解为UE的多个逻辑信道中的最高优先级的逻辑信道中具有UL数据，该最高优先级的逻辑信道会触发BSR上报。
2)、第二类常规BSR，UE的多个逻辑信道中的其中一个逻辑信道具有可传输的UL数据， 其余逻辑信道均没有可传输的UL数据，具有UL数据的逻辑信道会触发BSR上报。
3)、填充BSR(Padding BSR)，UE已分配了UL资源，且填充位的数量大于或等于BSR的MAC CE(MAC层的控制单元CE)与MAC CE子报头的大小，会触发UE上报BSR。
当UE的待传数据量超过缓冲区尺寸时，会将填充的比特空间用于发送BSR。其中，网络系统中的控制面协议层结构可以包括RRC(Radio Resource Control，无线资源控制)层、PDCP(Packet Data Convergence Protocol，分组数据汇聚层协议)层、RLC(Radio Link Control，无线链路控制)层、MAC(Media Access Control，媒体接入控制)层与物理层等协议层的功能，本段所提出的MAC层与下面即将阐述的PDCP层均属于控制面协议层结构中的一种，MAC层负责HARQ(Hybrid Automatic Repeat reQuest，混合自动重传请求)和调度功能，PDCP层负责将RLC层的数据进行分段链接，头压缩和加密等。
4)、重传BSR，至少有一个属于逻辑信道组的逻辑信道包含UL数据，retxBSR-Timer(BSR重发时间)到期的情况下，会触发UE进行BSR上报。
5)、周期BSR，periodicBSR-Timer(周期报告时间)过期的情况下，会触发UE进行BSR上报。
3、LC(Logical Channel，逻辑信道)、LCG(Logical Channel Group，逻辑信道组)，UE一般会将LC划分为不同优先级的LCG，每个不同优先级的LCG用于发送不同等级的BSR。例如，3GPP(TS23.203)中规定的标准化的QCI(1-9)，QCIs(1-3)映射到LCG1；QCIs(4-6)映射到LCG2；QCIs(7-9)映射到LCG3，非标准化的QCIs(10-256)映射到LCG3；LCG0用于发送SRB(signalling radio bearers，信令无线承载)，而BSR0-3分别在LCG0-3上发送。
4、PDU(Protocol Data Unit，协议数据单元)、PDU set(Protocol Data Unit set，协议数据单元集合)，PDU是对等层次之间传输的数据单位，例如物理层的PDU是数据位(bit)，数据链路层的PDU是数据帧(frame)，网络层的PDU是数据包(packet)，传输层的PDU是数据段(segment)，其他更高层次的PDU是报文(message)，实际使用时，可以将PDU在各个层次之间的名称统一地称为数据包。
5、PDCP(Packet Data Convergence Protocol)，分组数据汇聚协议)层，对于UE而言，在UE的PDCP层中以PDU set为最小丢弃单元来进行数据的丢弃；PDCP的丢弃是由每个SDU(Service Data Unit，业务数据单元)对PDU set集进行管理的，PDCP会丢弃与PDU set相关的所有PDU。示例地，UDP(User Datagram Protocol，用户数据报协议)标记PDU设置在GTP-U层，通过GTP-U头扩展DL PDU，UDP会标识属于一个PDU set中的多个PDU，例如，UDP根据PDU set的序列号(PDU Set SN)、PDU set的开始PDU(开始PDU是PDU set中的第一个PDU)与结束PDU(结束PDU是PDU set中的最后一个PDU)、PDU set中每个PDU的序列号以及PDUset中PDU的个数，从而确定一个PDU set的边界，进而在一个PDU set中的某个PDU丢失时，依据PDU set的边界，丢弃整个PDU set中的所有PDU。
对于部分业务而言，对数据并不按照重要性进行区分，PDU set中大部分的PDU到达应用层，剩余的PDU即使未到达应用层，也可以通过应用层的纠错机制来进行对这些数据进行正确解码；而对于其余业务，例如XR(eXtended Reality，扩展现实)业务而言，会对数据按照重要性进行区分，例如将数据帧划分为I帧(关键帧)和P帧(预测帧)，由于UE在对P帧进行解码时，UE无法单独对P帧解码，需要利用I帧才能对P帧进行解码，所以需要I帧与P帧等数据帧包含的所有PDU set均到达应用层，才能对这些数据进行正确解码。XR业务包括：AR(Augmented Reality，增强现实)、VR(Virtual Reality，虚拟现实)和MR(Mixed reality，混合现实)等。
对于需要PDU set到达应用层才能正确解码的情况下，若PDU set中的某个PDU丢失，PDCP层基于丢弃机制，会将整个PDU set中的PDU都在PDCP层进行删除，被删除的PDU都无需继续进行传输，此时会浪费网络授权给被删除的PDU的传输资源。
示例地，假设一个PDU set中有20个PDU，UE在BSR中上报了20个PDU的待传数据量，若网络授权调度了20个PDU中3个PDU的传输资源。但在网络授权调度的期间内，若3个PDU中的第一个PDU(假设第一个PDU是比较重要的I帧)丢失时，基于PDCP层的丢弃机制，会将整个PDU set中的PDU都在PDCP层被进行删除，而这些被删除的PDU则没有必要继续进行传输，UE也不再需要这些被删除的PDU的传输资源。在此情况下，网络却仍然按照BSR上报的待传数据量为UE授权了3个PDU的传输资源，则会导致传输资源的浪费。
相关技术中，在UE使用传输资源进行数据传输的过程中，若PDCP层中的某个PDU set中的某个PDU丢失，PDCP层会基于丢弃机制，将整个PDU set进行删除，使得整个PDU set中的PDU都没有必要继续进行传输。此时若网络仍然按照UE之前上报的BSR中的待传数据量来为被删除的PDU分配传输资源，则会导致传输资源的浪费。
为了避免网络授权给UE多余的传输资源，本公开在待传数据量与待传数据量的剩余时延预算中的至少一者变化的情况下，重新上报BSR，以使得网络依据重新上报的BSR，来合理为UE授权传输资源，避免网络为UE分配多余的传输资源。
图1是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图1所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S101中，响应于所述用户设备的待传数据量与所述待传数据量的剩余时延预算(delay budget)中至少一者变化，进行缓冲状态报告的更新上报。
其中，本公开任意实施例提出的用户设备可以是手机、平板、便携电脑、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等，本公开对应用场景不做限定，用户设备有时也可以称为终端设备、终端、接入终端、UE、UE单元、UE站、移动设备、移动站、移动台(mobile station)、移动客户端等。
其中，用户设备的待传数据量可以是用户设备的缓冲区中的待传数据量、待传数据量的剩余时延预算可以是待传数据量对应的待传数据从缓冲区传输出去的剩余时长，例如，UE给缓冲区中的待传数据分配了10ms的时延预算，过去8ms之后，缓冲区的待传数据还剩2ms的时长从缓冲区中传输出去，而2ms则是剩余时延预算。
其中，待传数据量变化包括待传数据量的增多与减少。在待传数据量增多时，代表新数据到达了缓冲区；在待传数据量减少时，可能出现PDCP层丢弃PDU set的情况，PDCP层丢弃PDU set可以是PDCP层出现批量丢弃数据包。
在UE的待传数据量增多的情况下，由于当前的待传数据量相较于之前UE上报给网络的待传数据量更多，若网络按照之前的BSR中的待传数据量为UE授权传输资源，会导致分配给UE的传输资源较少，使得当前的待传数据中的部分待传数据无法及时地传输出去。
相关技术中，常规BSR通常在缓冲区中的数据从无到有的情况下，才会触发BSR的上报，常规BSR无法在缓冲区的数据增多的情况下，触发BSR重新上报。
本公开中，为了在待传数据量增多的情况下，UE的待传数据能够被及时地发送出去，在UE的待传数据量增多的情况下，可以进行BSR的更新上报，更新上报的待传数据量相较于之前上报的BSR中的待传数据量更多，网络依据更新后的BSR，才能授权更多的传输资源给UE，UE依据更多的传输资源才能及时地将增多的待传数据传输出去。
在UE的待传数据量减少的情况下，当PDCP层批量丢弃数据包时，会导致UE的缓冲区的待传数据量减少，此时若网络按照之前的BSR中的待传数据量为UE授权传输资源，会导致分配给UE的传输资源较多，导致传输资源的浪费。
本公开中，为了在待传数据量减少的情况下，减少传输资源的浪费，可以在UE的待传数据量减少的情况下，进行BSR的更新上报，更新上报的待传数据量相较于之前上报的BSR中的待传数据量更少，网络依据更新后的BSR，则不会授权较多的传输资源给UE，从而减少了传输资源的浪费。
其中，剩余时延预算变化进行BSR更新上报，包括剩余时延预算相较于上次上报的BSR中的剩余时延预算增大或变小，则进行BSR更新上报；或者剩余时延预算小于或等于某个阈值，则进行BSR更新上报。待传数据量的剩余时延预算变化包括剩余时延预算的增大与减小。在剩余时延预算增大时，可能出现PDCP层批量丢弃PDU set的情况；在剩余时延预算减小时，可能出现紧急调度待传数据的情况。
其中，可以通过网络配置UE或协议约定UE的方式，在用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化的情况下，进行BSR的更新上报。
网络配置UE是网络UE下发指示，指示UE在面临缓冲区中的待传数据量和/或待传数据量的剩余时延预算发生变化的情况下，进行BSR的更新上报。协议约定UE是在网络与UE之间的逻辑信道和/或逻辑信道组上规定，在辑信道和/或逻辑信道组的缓冲区的待传数据量发生变 化的情况下，进行BSR的更新上报，例如一些类型的辑信道和/或逻辑信道组用于传输XR业务的数据，那么协议可以约定这些类型的辑信道和/或逻辑信道组，在各自的缓冲区的待传数据量发生变化时，进行BSR的更新上报。
其中，UE会向网络发送BSR，网络依据BSR为UE分配传输资源，UE使用传输资源进行数据传输的过程中，在PDCP层出现批量丢包现象，此时UE会进行BSR的更新上报，重新上传携带有变化后的待传数据量和/或变化后的剩余时延预算的BSR，那么本公开任意实施例中提出的进行BSR的更新上报可以理解为将之前上报的BSR进行重新更新后上报。
示例地，上次上报的BSR中携带剩余时延预算信息和/或待传数据量；而后一次上报的BSR中与剩余时延预算信息和/或待传数据量相关的字段为空，可以意味着上次上报的BSR不再生效，或者意味着上次上报的BSR中携带剩余时延预算信息不再生效。
通过上述技术方案，在UE的待传数据量与待传数据量的剩余时延预算中的至少一者变化的情况下，为了避免网络授权UE多余的传输资源，可以重新上报BSR，重新上报的BSR中携带了变化后的待传数据量和/或待传数据量的剩余时延预算，如此网络可以依据变化后的待传数据量和/或待传数据量的剩余时延预算，来为UE分配与待传数据量相匹配的传输资源，而不会分配多余的传输资源，避免了传输资源的浪费。
图2是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图2所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S201中，响应于所述待传数据量的变化值大于待传数据量变化阈值，进行缓冲状态报告的更新上报。
其中，可以通过网络配置UE或协议约定UE，在UE的待传数据量的变化值大于待传数据量变化阈值，进行BSR的更新上报。
其中，待传数据量的变化值可以是在PDCP层批量丢包的丢包数据量，也可以是新数据到达缓冲区之后，缓冲区中增多的数据量。示例地，网络配置UE或协议约定UE，在PDCP层进行了批量丢包操作且丢包数据量大于待传数据量变化阈值的情况下，进行BSR的更新上报。示例地，网络配置UE或协议约定UE，在缓冲区增加的数据量大于待传数据量变化阈值的情况下，进行BSR的更新上报。
待传数据量的变化值可以是丢包的个数、丢包的字节数、丢包的比特数中的任意一者；丢包的个数可以是数据包(Packet)的数量或者数据包集合(Packet Set)的个数。作为一个实施例，待传数据量可以是UE基于PDCP层和/或者RLC(Radio Link Control，无线链路层控制协议)的数据量进行确定。
待传数据量变化阈值可以是基站从核心网获取并发送给UE的，待传数据量变化阈值也可以是UE与网络基于协议约定的。
其中，若在待传数据量发生变化的情况下，就进行BSR的更新上报，会导致BSR更新上报过于频繁，会浪费网络资源。
为了减少网络资源的浪费，本公开提出在待传数据量的变化值大于待传数据量变化阈值的情况下，才进行BSR的更新上报。如此，在提高了BSR的上报条件之后，可以减少BSR的上报次数，减少网络资源的浪费。
通过上述技术方案，响应于待传数据量的变化值大于待传数据量变化阈值，进行BSR的更新上报，可以提高BSR上报条件，减少BSR上报次数，减少网络资源的浪费。
图3是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图3所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S301中，在所述剩余时延预算减小的情况下，进行缓冲状态报告的更新上报。
其中，在UE对部分待传数据进行紧急调度，需要将这部分待传数据从缓冲区中传输出去的情况下，会控制待传数据量的剩余时延预算减少，以使得待传数据能够在较短的时间内从缓冲区传输出去，实现这部分待传数据的紧急调度。
示例地，数据包A的剩余时延预算是5ms，在对缓冲区中的数据包A进行紧急调度时，会控制数据包A的剩余时延预算从5ms变为2ms，以控制数据包A在剩余2ms的时间内从缓冲区传输出去，以此来完成数据包A的紧急调度。
其中，在剩余时延预算减小的情况下，可能表明缓冲区中的待传数据需要进行紧急调度，需要UE及时地将这部分待传数据从缓冲区发送出去，因此需要进行BSR的重新上报，重新上 报的BSR中携带有待传数据量的剩余时延预算减小的信息，以使得网络依据重新上报的BSR，给UE尽快授权这部分待传数据的传输资源，完成缓冲区中待传数据的紧急调度。
作为一个示例，也可以在待传数据量其剩余时延预算小于或者等于某个阈值的情况下，则进行BSR上报。作为一个实施例：预定阈值可以从核心网获取，通过gNB(the next Generation Node B，5G基站)通知给UE；或者可以基于网络约定。
通过上述技术方案，在待传数据量的剩余时延预算小于或等于某个阈值的情况下，表明缓冲区中的待传数据需要紧急地从缓冲区传输出去，此时可以进行BSR上报，以使得网络依据更新上报的BSR报文，来及时地为这部分待传数据授权传输资源。
图4是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图4所示，该缓冲状态报告上报方法包括以下步骤中。
在步骤S401中，在所述待传数据量减小导致所述剩余时延预算增大的情况下，进行缓冲状态报告的更新上报。
其中，PDCP层进行了批量丢包操作，导致缓冲区的待传数据量减小，且缓冲区到达新的待传数据的情况下，会导致剩余时延预算增大，此时可以进行BSR的更新上报。
示例地，若待传数据量的剩余时延预算为2ms，但是在这2ms内，在PDCP层进行了批量丢包操作，导致缓冲区中的所有数据丢失，并且缓冲区中进入了新数据之后，剩余时延预算可以达到10ms，此时剩余时延预算相较于未进行批量丢包操作之前的剩余时延预算更大，此时则需要进行BSR的更新上报。在此情况下，UE重新上报的BSR中所指示的则是新到达缓冲区中的待传数据的待传数据量和/或待传数据量的剩余时延预算。
可见，在待传数据量减少导致剩余时延预算增大的情况下，可能是PDCP层进行了批量丢包操作，UE删除了缓冲区中的部分数据包，此时也需要进行BSR的重新上报，将新到达缓冲区中的待传数据量的剩余时延预算上报至网络，一方面可以使得网络给UE授权与缓冲区中的待传数据量匹配的传输资源，另一方面可以使得网络能够知晓缓冲区内的数据并不需要被紧急调度出去，网络并不需要较快地为该UE缓冲区内的待传数据分配传输资源，可以将传输资源分配给其余UE。
当然，在一种实施例中，在PDCP层丢包导致网络删除缓冲区中的部分待传数据，导致剩余时延预算变大的情况下，也可以无需进行BSR的更新上报。
示例地，假设UE最开始为缓冲区中的1000bit的数据量分配的剩余时延预算为10ms，在经过8ms之后，缓冲区中的1000bit的待传数据量的剩余时延预算为2ms，即，1000bit的待传数据还有2ms的时间到期可以从缓冲区传输出去。此时若网络主动删除了这1000bit的待传数据，并且在2ms内缓冲区中新到来1000bit的数据，新到来的1000bit待传数据的剩余时延预算为10ms，在剩余时延预算增大的情况下，缓冲区中的待传数据量却并未发生变化，基于同样的数据量，则无需进行BSR的更新上报，网络依据1000bit的数据量为UE授权传输资源即可。
通过上述技术方案，在剩余时延预算减小的情况下，进行BSR的更新上报，可以将更小的剩余时延预算发送至网络，使得网络依据更新上报的剩余时延预算来尽快地为UE分配传输资源，以实现UE对待传数据的紧急调度；在待传数据量减小导致剩余时延预算增大的情况下，进行BSR的更新上报，可以将新到达缓冲区的待传数据的待传数据量和/或待传数据量的剩余预算时延发送至网络，一方面使得网络依据更新上报的剩余时延预算来为UE分配与新到达缓冲区的数据相匹配的传输资源，另一方面网络依据更新上报的剩余时延预算，知晓该UE缓冲区内的待传数据并不需要紧急调度出去，可以将传输资源分配给其余UE。
可以理解的是，上述图3与图4所示出的示例可以分别单独为一个实施例，也可以两者组合形成新的实施例。当图3示出的实施例为单独的一个实施例的情况下，会使得网络依据更新上报的BSR来为UE更快授权传输资源；当图4示出的实施例为单独的一个实施例的情况下，PDCP层丢包导致缓冲区新到达待传数据量增多，会使得网络依据更新上报的BSR，来为UE授权与缓冲区中新到达的待传数据量匹配的传输资源。
图5是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图5所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S501中，响应于所述用户设备的至少一个逻辑信道或至少一个逻辑信道组的待传数据量变化，进行缓冲状态报告的更新上报。
其中，用户设备与网络设备之间通过至少一个逻辑信道或至少一个逻辑信道组进行通信， 每个逻辑信道或逻辑信道组对应有各自的缓冲区，逻辑信道或逻辑信道组对应有各自的缓冲区中的待传数据量变化的情况下，进行BSR的更新上报。
因此，UE的待传数据量可以从至少一个逻辑信道或至少一个逻辑信道组或全部逻辑信道的缓冲区的待传数据量中统计。
示例地，在至少一个逻辑信道的待传数据量发生变化的情况下，可以触发BSR重新上报；在至少一个逻辑信道组内的所有逻辑信道的待传数据量总和发生变化的情况下，可以触发BSR重新上报；在所有逻辑信道的待传数据量总和发生变化的情况下，可以触发BSR重新上报。
通过上述技术方案，在至少一个逻辑信道或至少一个逻辑信道组的待传数据量变化的情况下，可以进行BSR重新上报，以使得网络依据重新上报的BSR中指示的变化后的待传数据量，来为UE分配与变化后的待传数据量相匹配的传输资源。
图6是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图6所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S601中，响应于所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，将上报至网络设备的缓冲状态报告，更新为常规缓冲状态报告中的任意一种或更新为第二类型的缓冲状态报告。
其中，在进行BSR的更新上报时，更新上报后的BSR可以为常规BSR中的任意一种，例如为上述的第一类常规BSR或者为第二类常规BSR，也可以命名为另一种新类型的BSR，例如为更新BSR(updated BSR)。
在一种实施例中，网络配置UE或者协议约定UE，在待传数据量有变化、在待传数据量其剩余delay budget(剩余时延预算)有变化、在待传数据量其剩余delay budget(剩余时延预算)小于或者等于预定阈值中的至少一者存在的情况下，进行BSR更新上报时，该BSR可以关联到指定的逻辑信道ID或者新的逻辑信道ID；这样基站收到之后，则可以通过该逻辑信道ID识别该类型的BSR。关联到指定的逻辑信道ID或者新的逻辑信道ID可以是使用预留的一个LCH(Logical Channel，逻辑信道)ID来标识。
作为一种实施例，新的逻辑信道ID可以针对长BSR(Long BSR)和短BSR(Short BSR)分别配置。
图7是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图7所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S701中，在所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，且所述用户设备配置了缓冲状态报告更新功能的情况下，进行缓冲状态报告的更新上报。
其中，缓冲状态报告更新功能为在所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行BSR重新上报的功能。
在UE配置了缓冲状态报告更新功能，且UE确定出待传数据量与待传数据量的剩余时延预算中的至少一者变化的情况下，即可首次进行BSR上报。
示例地，在UE配置了缓冲状态报告更新功能之后，若UE缓冲区中的待传数据从无到有时，即可首次上报BSR；若UE中待传数据量的剩余时延预算从无到有时，也可以进行首次BSR的上报。如此，网络可以依据首次上报的BSR中指示的待传数据量和/或剩余时延预算，来为UE授权传输资源。
图8是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图8所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S801中，在所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，且所述缓冲状态报告的上报值变化的情况下，进行缓冲状态报告的更新上报。
其中，若用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，就进行BSR的更新上报，会导致UE频繁上报BSR，造成网络资源的浪费。
本公开中，在所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，且所述缓冲状态报告的上报值变化的情况下，采进行BSR的更新上报，减少了BSR上报次数，减少了网络资源的浪费。
示例地，假设BSR上报的上报值有1与2，1对应的待传数据量的范围为[0，1000]，2对应的待传数据量的范围为[1001，2000]，若之前的待传数据量是500，现在是800，仍然在[0， 1000]的范围之内，所以BSR的上报值不会发生变化，UE不会进行BSR的更新上报。当待传数据量变化为1500，在[1001，2000]范围之内时，BSR的上报值才会从1变化为2，此时UE才会进行BSR的更新上报。
可见，本公开在待传数据量和/或剩余时延预算发生变化，且BSR的上报值变化的情况下，才会进行BSR报文的更新上报，以使得BSR报文更新上报的条件更加严苛，减少BSR更新上报的次数，减少网络资源的浪费。
通过上述技术方案，在所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，且所述缓冲状态报告的上报值变化的情况下，进行BSR的更新上报，可以使得BSR的更新上报条件更加严苛，减少BSR报文的上报次数，避免频繁上报BSR报文所带来的网络资源的浪费。
图9是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图9所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S901中，在所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，且所述用户设备配备的禁止定时器未运行的情况下，进行缓冲状态报告的更新上报。
其中，禁止定时器是用于禁止BSR报文上报的定时器，在禁止定时器运行期间，UE无法进行BSR报文的更新上报；在禁止定时器未运行期间，UE可以进行BSR报文的更新上报。
示例地，禁止定时器的运行时间为3ms，在禁止定时器运行的3ms之内，即使UE的待传数据量和/或剩余时延预算发生变化，UE也不会进行BSR报文的更新上报；在禁止定时器运行3ms结束之后，若UE的待传数据量和/或剩余时延预算发生变化，UE则可以进行BSR报文的更新上报。
可见，通过UE配置禁止定时器，可以在禁止定时器运行期间，禁止UE更新上报BSR报文，从而减少BSR报文的上报次数，减少网络资源的浪费。
通过上述技术方案，在所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，且所述用户设备配备的禁止定时器未运行的情况下，可以使得UE在禁止定时器没有运行的期间内上报BSR，也减少了BSR报文的上次次数，进而避免频繁上报BSR报文所带来的网络资源的浪费。
可以理解的是，上述图7、图8与图9所示出的示例可以分别为单独的实施例，也可以两两组合，或者三个组合分别形成新的实施例。
示例地，在图8与图9所示出的示例进行组合后，可以得到在所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，且所述缓冲状态报告的上报值变化，且所述用户设备配备的禁止定时器未运行的情况下，进行BSR报文的更新上报。在此情况下，UE是在禁止定时器未运行，且BSR报文的上报值有变化的情况下，才进行BSR报文的更新上报，使得BSR报文的更新上报相较于单独的步骤S602或S603而言更加严苛，进一步避免频繁上报BSR报文所带来的网络资源的浪费。
图10是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图10所示，该方法包括以下步骤。
在步骤S1001中，接收用于指示所述用户设备使能所述缓冲状态报告更新功能的信令。
其中，用户设备可以接收使能缓冲状态报告更新功能的信令，即UE可以接收BSR更新功能的信令，在接收到该信令之后，UE可以使能BSR更新功能。BSR更新功能可以在UE所有的逻辑信道和/或逻辑信道组上生效。
其中，UE可以隐含地确定自身可以使用BSR更新功能。
示例地，当UE接收到网络发送的待传数据量变化阈值的情况下，即可确定自身可以使能BSR更新功能。
示例地，当UE确定仅在周期BSR没有触发时可以使用BSR更新功能的情况下，确定自身可以使能BSR更新功能。若UE配置了周期BSR，则可以周期性地将BSR进行上报，没必要使用本公开提出的BSR更新功能。因此，在使用本公开提出的BSR更新功能时，可以禁止使用周期BSR。并且，使能BSR更新功能相较于周期BSR而言，上报BSR的条件更加苛刻，使得UE上报BSR的开销相对较小。
在步骤S1002中，使能所述缓冲状态报告更新功能，进行缓冲状态报告的更新上报。
其中，在UE能够使能BSR更新功能之后，若UE确定出用户设备的待传数据量与所述待 传数据量的剩余时延预算中至少一者变化，则进行BSR的更新上报。
通过上述技术方案，可以使得BSR更新功能在每个UE粒度上生效，使得UE在面对UE的所有配置的逻辑信道或者逻辑信道组上，其待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行BSR的更新上报。
图11是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图11所示，该方法包括以下步骤。
在步骤S1101中，接收用于指示所述用户设备的无线承载使能所述缓冲状态报告更新功能的信令。
其中，无线承载(Radio Bearer，RB)是UE与UTRAN(UMTS Terrestrial Radio Access Network，UTMS陆地无线接入网)之间L2向上层提供的业务。UE可以接收用于指示UE的无线承载使能BSR更新功能的信令，如此与UE的无线承载关联的所有逻辑信道或逻辑信道组都可以使能BSR更新功能。
示例地，若无线承载用于承载XR业务，XR业务有多种类型的数据包，第一种类型的数据包用第一个逻辑信道传输，第二种类型的数据包用第二个逻辑信道传输，那么这两个逻辑信道则是与无线承载关联的逻辑信道.同理，逻辑信道组与无线承载的关联也可以通过这种方式进行判断，在此不再赘述。
其中，网络可以事先配置UE的无线承载与哪些逻辑信道、逻辑信道组进行关联。
其中，UE可以隐含地确定无线承载能够使能BSR更新功能。
示例地，当UE接收到网络针对某个无线承载的待传数据量变化阈值的情况下，可以隐含地确定该无线承载可以使能BSR更新功能。
在步骤S1102中，使能所述缓冲状态报告更新功能，进行缓冲状态报告的更新上报。
其中，UE的无线承载使能BSR更新功能之后，若UE确定出与无线承载关联的逻辑信道和/或逻辑信道组的缓冲区中的待传数据量变化，或者剩余时延预算变化，则进行BSR的更新上报。
通过上述技术方案，可以使得BSR更新功能在每个无线承载粒度上生效，使得UE在面对无线承载的待传数据量与所述待传数据量的剩余时延预算中至少一者变化时，进行BSR的更新上报。
图12是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图12所示，该方法包括以下步骤。
在步骤S1201中，接收用于指示所述用户设备的逻辑信道或逻辑信道组使能所述缓冲状态报告更新功能的信令。
其中，UE可以接收用于指示逻辑信道使能BSR更新功能的信令，也可以接收用于指示逻辑信道组使能BSR更新功能的信令。
作为一种实施例，UE可以接收用于指示用户设备的第一逻辑信道或第一逻辑信道组，使能所述缓冲状态报告更新功能的信令。
示例地，协议约定终端其对于第一逻辑信道或第一逻辑信道组，使能BSR更新功能。第一逻辑信道为特定的逻辑信道，第一逻辑信道组为特定的逻辑信道组。其中，特定的逻辑信道为配置了使用特定类型BSR表格，例如第二BSRtable(第二BSR表格)，进行BSR上报的逻辑信道；特定的逻辑信道组为配置了使用特定类型BSR表格，例如第二BSRtable，进行BSR上报的逻辑信道组。
作为一种实施例，第二BSRtable是为XR业务新引入的Buffersize(缓冲量)映射到不同量化等级的表格，第二BSRtable中具有缓冲量与缓冲量量化等级之间的映射关系。
其中，UE可以隐含地确定逻辑信道或逻辑信道组能够使能BSR更新功能。
示例地，UE接收到网络针对逻辑信道的待传数据量变化阈值的情况下，则可以确定该逻辑信道可以使能BSR更新功能；UE接收到网络针对逻辑信道组的待传数据量变化阈值的情况下，则可以确定该逻辑信道组可以使能BSR更新功能。
在步骤S1202中，使能所述缓冲状态报告更新功能，进行缓冲状态报告的更新上报。
其中，UE的逻辑信道可以使能BSR更新功能之后，若UE确定出逻辑信道缓冲区中的待传数据量变化或者剩余时延预算变化，则进行BSR的更新上报。逻辑信道组可以使能BSR更新功能之后，若UE确定出逻辑信道组缓冲区中的待传数据量变化或者剩余时延预算变化，则进行 BSR的更新上报。
通过上述技术方案，可以使得BSR更新功能在每个逻辑信道粒度或每个逻辑信道组粒度上生效，使得UE在面对逻辑信道或逻辑信道组的待传数据量与所述待传数据量的剩余时延预算中至少一者变化时，进行BSR的更新上报。
可以理解的是，图10示出的实施例、图11示出的实施例与图12示出的实施例这三个实施例之间可以为单独的实施例，也可以两两之间相互组合形成一个新的实施例，也可以三个实施例形成一个新的实施例。
图13是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被用户设备执行，如图13所示，该方法包括以下步骤。
在步骤S1301中，将所述用户设备的辅助信息上报至网络设备。
其中，所述辅助信息包括以下至少一者：所述用户设备是否支持使用缓冲状态报告更新功能的能力、所述用户设备是否期望使用所述缓冲状态报告更新功能。
其中，UE可以具有第一类BSR上报能力与第二类BSR上报能力。第一类BSR上报能力为在待传数据量与所述待传数据量的剩余时延预算中至少一者变化的情况下，进行BSR更新上报的能力；第二类BSR上报能力为上述常规BSR、周期BSR、重传BSR与填充BSR的上报能力。当UE上报第一类BSR上报能力时，表明UE支持使能BSR更新功能，此时网络会为UE配置BSR更新功能。
其中，在UE接收到多余待传数据的授权时，表明UE期望使能BSR更新功能，此时网络会为UE配置BSR更新功能。
示例地，当UE缓冲区的待传数据丢包之后，网络可能会按照原来的数据量来为UE分配较多的授权，而终端并不需要那么多的授权，此时UE接收到多余待传数据的授权，UE则意识到网络获取到的BSR报文中上报的待传数据量较多。因此UE可以上报辅助信息，以期望使能BSR更新功能，避免网络为UE分配多余待传数据量的授权。
授权指的是网络为UE的待传数据授权的传输资源，传输资源可以理解为上行传输资源，UE需要利用上行传输资源将缓冲区中的待传数据传输至网络。
在步骤S1302中，响应于所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行缓冲状态报告的更新上报。
其中，当UE将辅助信息上传至网络之后，网络会为UE配置BSR更新功能，当然网络与UE之间也可以通过协议约定BSR更新功能，此时UE可以响应于待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行BSR的更新上报。
通过上述技术方案，UE可以向网络设备上报UE的辅助信息，以表明UE自身具有使能BSR更新功能的能力和/或期望使用BSR更新功能，使得网络能够依据辅助信息来为UE配置BSR更新功能。
图14是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被网络设备执行，如图14所示，该方法包括以下步骤。
在步骤S1401中，接收用户设备更新上报的缓冲状态报告。
其中，本公开任意实施例提出的网络设备可以是用于与用户设备通信的设备，该网络设备也可以称为接入网设备或无线接入网设备，可以是传输接收点(transmission reception point，TRP)，还可以是LTE系统中的演进型基站(evolved NodeB，eNB或eNodeB)，还可以是家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等，可以是WLAN中的接入点(access point，AP)，可以是NR的gNB，本申请实施例并不限定。
该步骤可以参照上述步骤S101，在此不再赘述。
通过上述技术方案，网络设备在接收到用户设备更新上报的BSR之后，由于BSR中指示有变化后的待传数据量和/或待传数据量的剩余时延预算，所以网络设备可以依据变化后的待传数据量和/或待传数据量的剩余时延预算，来为UE分配与变化后的待传数据量和/或待传数据量的剩余时延预算匹配的传输资源，避免网络设备分配的传输资源多余UE所需的传输资源的情况，减少了传输资源的浪费。
图15是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被网络设备执行，如图15所示，该方法包括以下步骤。
在步骤S1501中，接收用户设备更新上报的缓冲状态报告。
该步骤可以参考上述步骤S101，在此不再赘述。
在步骤S1502中，根据所述缓冲状态报告，确定所述用户设备的待传数据量与所述待传数据量的剩余时延预算中的至少一者变化。
该步骤可以参考上述步骤S101，在此不再赘述。
通过上述技术方案，在接收到UE更新上报的BSR的情况下，可以根据BSR中指示的待传数据量或剩余时延预算，来为UE分配与待传数据量或剩余时延预算匹配的传输资源。
图16是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被网络设备执行，如图16所示，该方法包括以下步骤。
在步骤S1601中，接收用户设备更新上报的缓冲状态报告。
该步骤可以参考上述步骤S101，在此不再赘述。
在步骤S1602中，根据所述缓冲状态报告，确定所述待传数据量的变化值大于待传数据量变化阈值。
该步骤可以参考上述步骤S201，在此不再赘述。
通过上述技术方案，网络设备会在UE的待传数据量的变化值大于待传数据量变化阈值的情况下，才会接收到UE更新上报的BSR，网络设备接收到BSR的上报次数减少，减少了网络资源的浪费。
图17是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被网络设备执行，如图17所示，该方法包括以下步骤。
在步骤S1701中，接收用户设备更新上报的缓冲状态报告。
该步骤可以参考上述步骤S101，在此不再赘述。
在步骤S1702中，根据所述缓冲状态报告，确定所述剩余时延预算减小和/或所述待传数据量减小导致所述剩余时延预算增大。
该步骤可以参考上述步骤S301与步骤S401，在此不再赘述。
通过上述技术方案，在剩余时延预算减小的情况下，进行BSR的更新上报，可以将更小的剩余时延预算发送至网络，使得网络依据更新上报的剩余时延预算来尽快地为UE分配传输资源，以实现对待传数据的紧急调度；在待传数据量减小导致剩余时延预算增大的情况下，进行BSR的更新上报，可以将新到达缓冲区的待传数据的待传数据量和/或待传数据量的剩余预算时延发送至网络，网络依据更新上报的剩余时延预算来为UE分配与新到达缓冲区的待传数据相匹配的传输资源。
图18是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被网络设备执行，如图18所示，该方法包括以下步骤。
在步骤S1801中，接收用户设备更新上报的缓冲状态报告。
该步骤可以参考上述步骤S101，在此不再赘述。
在步骤S1802中，根据所述缓冲状态报告，确定所述用户设备的至少一个逻辑信道或至少一个逻辑信道组的待传数据量变化。
该步骤可以参考上述步骤S501，在此不再赘述。
通过上述技术方案，在至少一个逻辑信道或至少一个逻辑信道组的待传数据量变化的情况下，可以接收更新上报的BSR重新，网络依据重新上报的BSR中指示的变化后的待传数据量，来为UE分配匹配的传输资源。
图19是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被网络设备执行，如图19所示，该方法包括以下步骤。
在步骤S1901中，接收所述用户设备更新上报为常规缓冲状态报告中的任意一种缓冲状态报告，或接收用户设备更新上报为第二类型的缓冲状态报告。
该步骤可以参考上述步骤S601，在此不再赘述。
图20是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被网络设备执行，如图20所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S2001中，向所述用户设备发送用于指示所述用户设备使能缓冲状态报告更新功能 的信令。
其中，若网络设备知晓UE为进行XR业务的UE，则会向UE发送用于指示UE使能BSR更新功能的信令，通知UE使能BSR更新功能。
在网络设备通知UE使能该BSR更新功能之后，UE所有的逻辑信道或逻辑信道组上都生效该BSR更新功能。
其中，网络设备可以隐含地通知UE使能BSR更新功能。
示例地，网络设备可以通知UE针对某个逻辑信道或某个逻辑信道组的待传数据量变化阈值，网络设备也可以通知UE在周期BSR没有配置时使用BSR更新功能，从而隐含地通知UE使能BSR更新功能。
在步骤S2002中，接收用户设备更新上报的缓冲状态报告。
该步骤可以参考上述步骤S101，在此不再赘述。
通过上述技术方案，网络可以为UE配置BSR更新功能在每个UE粒度上生效，使得UE在面对UE的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行BSR的更新上报。
图21是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被网络设备执行，如图21所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S2101中，向所述用户设备发送用于指示所述用户设备的无线承载使能缓冲状态报告更新功能的信令。
其中，若网络设备知晓UE为进行XR业务的UE，则会向UE发送用于指示无线承载使能BSR更新功能的信令，通知无线承载能够使能BSR更新功能。
在网络设备通知UE使能该BSR更新功能之后，与无线承载关联的所有的逻辑信道或逻辑信道组上都生效该BSR更新功能。
其中，网络设备可以隐含地通知无线承载使能BSR更新功能。
示例地，网络设备可以通知UE与无线承载关联的至少一个逻辑信道或至少一个逻辑信道组的待传数据量变化阈值，从而隐含地通知无线承载使能BSR更新功能。
在步骤S2102中，接收用户设备更新上报的缓冲状态报告。
该步骤可以参考上述步骤S101，在此不再赘述。
通过上述技术方案，网络可以为UE配置BSR更新功能在每个无线承载粒度上生效，使得UE在面对无线承载的待传数据量与所述待传数据量的剩余时延预算中至少一者变化时，进行BSR的更新上报。
图22是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被网络设备执行，如图22所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S2201中，向所述用户设备发送用于指示所述用户设备的逻辑信道或逻辑信道组使能所述缓冲状态报告更新功能的信令。
其中，若网络设备知晓UE为进行XR业务的UE，则会向UE发送用于指示逻辑信道使能BSR更新功能的信令，通知逻辑信道使能BSR更新功能；也可以向UE发送用于指示逻辑信道组使能BSR更新功能的信令，通知逻辑信道组使能BSR更新功能。
其中，网络设备可以隐含地通知UE逻辑信道或逻辑信道组可以使能BSR更新功能。
示例地，网络设备可以通知UE至少一个逻辑信道或至少一个逻辑信道组各自的待传数据量变化阈值，从而隐含地通知逻辑信道或逻辑信道组使能BSR更新功能。
在步骤S2202中，接收用户设备更新上报的缓冲状态报告。
该步骤可以参照上述步骤S101，在此不再赘述。
通过上述技术方案，网络为UE配置BSR更新功能在每个逻辑信道粒度或每个逻辑信道组粒度上生效，使得UE在面对逻辑信道或逻辑信道组的待传数据量与所述待传数据量的剩余时延预算中至少一者变化时，进行BSR的更新上报。
图23是根据一示例性实施例示出的一种缓冲状态报告上报方法，该方法被网络设备执行，如图20所示，该缓冲状态报告上报方法包括以下步骤。
在步骤S2301中，接收所述用户设备发送的辅助信息。
其中，所述辅助信息包括以下至少一者：所述用户设备是否支持使用缓冲状态报告更新功能的能力、所述用户设备是否期望使用所述缓冲状态报告更新功能。
该步骤可以参照上述步骤S1301，在此不再赘述。
通过上述技术方案，网络设备可以接收UE上报的辅助信息，以确定UE自身具有使能BSR更新功能的能力和/或期望使用BSR更新功能，从而依据辅助信息来为UE配置BSR更新功能。
图24是根据一示例性实施例实处的一种缓冲状态报告上报装置，该装置被用户设备执行，如图24所示，该缓冲状态报告上报装置240包括缓冲状态报告发送模块241。
缓冲状态报告发送模块241，被配置为响应于所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行缓冲状态报告的更新上报。
可选地，缓冲状态报告发送模块241包括：
第一缓冲状态报告发送子模块，被配置为响应于所述待传数据量的变化值大于待传数据量变化阈值，进行缓冲状态报告的更新上报。
可选地，缓冲状态报告发送模块241包括：
第二缓冲状态报告发送子模块，被配置为在所述剩余时延预算减小的情况下，进行缓冲状态报告的更新上报，和/或；
第三缓冲状态报告发送子模块，被配置为在所述待传数据量减小导致所述剩余时延预算增大的情况下，进行缓冲状态报告的更新上报。
可选地，缓冲状态报告发送模块241包括：
第四缓冲状态报告发送子模块，被配置为响应于所述用户设备的至少一个逻辑信道或至少一个逻辑信道组的待传数据量变化，进行缓冲状态报告的更新上报。
可选地，缓冲状态报告发送模块241包括：
第五缓冲状态报告发送子模块，被配置为将上报至网络设备的缓冲状态报告，更新为常规缓冲状态报告中的任意一种或更新为第二类型的缓冲状态报告。
可选地，缓冲状态报告发送模块241包括：
第六缓冲状态报告发送子模块，被配置为在所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，且存在以下至少一种条件的情况下，进行缓冲状态报告的更新上报：
所述用户设备配置了缓冲状态报告更新功能、所述缓冲状态报告的上报值变化、所述用户设备配备的禁止定时器未运行。
可选地，缓冲状态报告发送模块241包括：
第六缓冲状态报告发送子模块，被配置为使能缓冲状态报告更新功能，进行所述缓冲状态报告的更新上报；
其中，通过以下至少一种条件，确定使能所述缓冲状态报告更新功能：
接收用于指示所述用户设备使能所述缓冲状态报告更新功能的信令；
接收用于指示所述用户设备的无线承载使能所述缓冲状态报告更新功能的信令；
接收用于指示所述用户设备的逻辑信道或逻辑信道组使能所述缓冲状态报告更新功能的信令。
可选地，缓冲状态报告上报装置240包括：
辅助信息上报子模块，被配置为将所述用户设备的辅助信息上报至网络设备，所述辅助信息包括以下至少一者：
所述用户设备是否支持使用缓冲状态报告更新功能的能力、所述用户设备是否期望使用所述缓冲状态报告更新功能。
图25是根据一示例性实施例实处的一种缓冲状态报告上报装置，该装置被用户设备执行，如图25所示，该缓冲状态报告上报装置250包括缓冲状态报告接收模块251。
缓冲状态报告接收模块251，被配置为接收用户设备更新上报的缓冲状态报告。
可选地，缓冲状态报告接收模块251包括：
第一缓冲状态报告接收子模块，被配置为接收用户设备更新上报的缓冲状态报告；
第一报告确定子模块，被配置为根据所述缓冲状态报告，确定所述用户设备的待传数据量与所述待传数据量的剩余时延预算中的至少一者变化。
可选地，第一报告确定子模块包括：
第二报告确定子模块，被配置为根据所述缓冲状态报告，确定所述待传数据量的变化值大于待传数据量变化阈值。
可选地，第一报告确定子模块包括：
第三报告确定子模块，被配置为根据所述缓冲状态报告，确定所述剩余时延预算减小和/或所述待传数据量减小导致所述剩余时延预算增大。
可选地，第一报告确定子模块包括：
第四报告确定子模块，被配置为根据所述缓冲状态报告，确定所述用户设备的至少一个逻辑信道或至少一个逻辑信道组的待传数据量变化。
可选地，缓冲状态报告接收模块251包括：
第二缓冲状态报告接收子模块，被配置为接收所述用户设备更新上报为常规缓冲状态报告中的任意一种缓冲状态报告，或接收用户设备更新上报为第二类型的缓冲状态报告。
可选地，缓冲状态报告上报装置250包括：
第一指示子模块，被配置为向所述用户设备发送用于指示所述用户设备使能缓冲状态报告更新功能的信令，和/或；
第二指示子模块，被配置为向所述用户设备发送用于指示所述用户设备的无线承载使能缓冲状态报告更新功能的信令，和/或；
第三指示子模块，被配置为向所述用户设备发送用于指示所述用户设备的逻辑信道或逻辑信道组使能所述缓冲状态报告更新功能的信令。
可选地，第一指示子模块包括：
第一数据发送子模块，被配置为向所述用户设备发送所述用户设备的待传数据量变化阈值、指示所述用户设备在未配置周期缓冲状态报告的状态下使用缓冲状态报告更新功能。
可选地，第二指示子模块包括：
第二数据发送子模块，被配置为向所述无线承载发送所述无线承载的待传数据量变化阈值。
可选地，第三指示子模块包括：
第三数据发送子模块，被配置为向所述逻辑信道或所述逻辑信道组，发送所述逻辑信道或所述逻辑信道组的待传数据量变化阈值。
可选地，缓冲状态报告上报装置250包括：
辅助信息接收模块，被配置为接收所述用户设备发送的辅助信息，所述辅助信息包括以下至少一者：
所述用户设备是否支持使用缓冲状态报告更新功能的能力、所述用户设备是否期望使用所述缓冲状态报告更新功能。
图26是根据一示例性实施例示出的一种用户设备的装置800的框图。例如，装置800可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图26，装置800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出接口812，传感器组件814，以及通信组件816。
处理组件802通常控制装置800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器820来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在装置800的操作。这些数据的示例包括用于在装置800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为装置800的各种组件提供电力。电源组件806可以包括电源管理系统，一个或多个电源，及其他与为装置800生成、管理和分配电力相关联的组件。
多媒体组件808包括在所述装置800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以 被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当装置800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当装置800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
输入/输出接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为装置800提供各个方面的状态评估。例如，传感器组件814可以检测到装置800的打开/关闭状态，组件的相对定位，例如所述组件为装置800的显示器和小键盘，传感器组件814还可以检测装置800或装置800一个组件的位置改变，用户与装置800接触的存在或不存在，装置800方位或加速/减速和装置800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于装置800和其他设备之间有线或无线方式的通信。装置800可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由装置800的处理器820执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
上述装置除了可以是独立的电子设备外，也可是独立电子设备的一部分，例如在一种实施例中，该装置可以是集成电路(Integrated Circuit，IC)或芯片，其中该集成电路可以是一个IC，也可以是多个IC的集合；该芯片可以包括但不限于以下种类：GPU(Graphics Processing Unit，图形处理器)、CPU(Central Processing Unit，中央处理器)、FPGA(Field Programmable Gate Array，可编程逻辑阵列)、DSP(Digital Signal Processor，数字信号处理器)、ASIC(Application Specific Integrated Circuit，专用集成电路)、SOC(System on Chip，SoC，片上系统或系统级芯片)等。上述的集成电路或芯片中可以用于执行可执行指令(或代码)，以实现上述的资源选择方法。其中该可执行指令可以存储在该集成电路或芯片中，也可以从其他的装置或设备获取，例如该集成电路或芯片中包括处理器、存储器，以及用于与其他的装置通信的接口。该可执行指令可以存储于该存储器中，当该可执行指令被处理器执行时实现上述的资源选择方法；或者，该集成电路或芯片可以通过该接口接收可执行指令并传输给该处理器执行，以实现上述的资源选择方法。
在另一示例性实施例中，还提供一种计算机程序产品，该计算机程序产品包含能够由可编程的装置执行的计算机程序，该计算机程序具有当由该可编程的装置执行时用于执行上述的资源选择方法的代码部分。
图27是根据一示例性实施例示出的一种网络设备1900的框图。例如，网络设备1900可 以被提供为一基站。参照图27，网络设备包括处理组件1922，其进一步包括一个或多个处理器，以及由存储器1932所代表的存储器资源，用于存储可由处理组件1922的执行的指令，例如应用程序。存储器1932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件1922被配置为执行指令，以执行上述资源选择方法。
网络设备1900还可以包括一个电源组件1926被配置为执行装置1900的电源管理，一个有线或无线网络接口1950被配置为将网络设备1900连接到网络，和一个输入/输出接口1958。
本领域技术人员在考虑说明书及实践本公开后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
可以理解的是，下文示例提出的方案是本公开中的缓冲状态报告上报方法、装置、设备、计算机可读存储介质与芯片等实施例的示例。
1、网络配置终端或者协议约定终端上报最新的BSR的操作机制。
a)、作为一个实施例：网络配置终端或者协议约定终端数据量增多或者变少场景下上报最新的BSR的机制。
作为一个实施例：待传数据量增多，则意味着新数据的到达。
作为一个实施例：或者待传数据量减少，比如丢弃PDCP的丢弃发生。
作为一个实施例：待传数据量的变化可以基于数据包统计或者针对数据包集合进行统计。比如：丢包量可以用丢包个数或者丢包bit数/字节数衡量；其中丢包个数可以基于Packet(数据包)个数或者Packet Set(数据包集合)个数。
作为一个实施例，待传数据量可以是终端基于PDCP层和/或者RLC(Radio Link Control，无线链路层控制协议)的数据量进行确定。
b)、作为一个实施例：网络配置终端或者协议约定终端在待传数据量其剩余delay budget(剩余时延预算)有变化，则进行BSR上报。
作为一个实施例：待传数据量其剩余delay budget小于或者等于某个阈值，则进行BSR上报。
作为一个实施例：阈值可以从核心网获取，通过gNB(the next Generation Node B，5G基站)通知给UE；或者可以基于网络约定。
作为一个实施例：待传数据量其剩余delay budget(剩余时延预算)相比于前次上报，剩余时延预算增大或者变小，则进行BSR上报。
c)、作为一种实施例：应用场景BSR上报为对之前上报的BSR进行update(更新其有效性信息)。
作为一种实施例：之前上报的BSR中携带剩余时延预算信息；而后一次上报的BSR中相关字段为空。可以意味着之前上报的BSR不再生效；或者意味着之前上报的BSR中携带剩余时延预算信息不再生效。
2、网络配置终端或者协议约定终端在待传数据量有变化后进行BSR更新上报。
a)、作为一个实施例：网络配置终端或者协议约定终端在待传数据量有变化，则进行BSR上报。
作为一个实施例：PDCP层进行了批量丢包操作后进行BSR上报；(只要有这个批量丢包操作即更新)其中批量丢包操作将导致终端的待传数据量有变化，则进行BSR上报。
b)、作为一个实施例：网络配置终端或者协议约定终端在待传数据量有变化超过预定门限后进行BSR上报。
作为一个实施例：网络配置终端或者协议约定终端在PDCP层进行了批量丢包操作且丢包数据量超过预定阈值后进行BSR上报；
作为一个实施例：待传数据量的变化可以基于数据包统计或者针对数据包集合进行统计。比如：丢包量可以用丢包个数或者丢包bit数/字节数衡量；其中丢包个数可以基于Packet或者Packet Set个数。
作为一个实施例：预定阈值可以从核心网获取，通过gNB(the next Generation Node B， 5G基站)通知给UE。或者可以基于网络约定。
c)、作为一个实施例：网络配置终端或者协议约定终端在待传数据量其剩余delay budget(剩余时延预算)有变化，则进行BSR上报。
或者增加条件：仅仅在剩余delay budget(剩余时延预算)变小才进行上报。
作为一个实施例，仅仅需要在调度紧急度提升时候进行BSR上报。比如同样的1000bit，若网络进行了主动删除，则若新到来1000bit，则同样的数据量，其剩余delay budget变大了，此时就无需update BSR)。这样做的好处是可以让网络将传输资源给调度紧急度更高的调度。
d)、作为一个实施例：待传数据量有变化的统计可以基于一个逻辑信道或者一个逻辑信道组的一个或者多个逻辑信道或者全部逻辑信道的待传数据量统计。
e)、作为一个实施例：待传数据量有变化的触发的BSR可以基于一个逻辑信道触发，即一个逻辑信道上待传数据量有变化则触发BSR。
f)、作为一个实施例：待传数据量有变化的触发的BSR可以基于一个逻辑信道组触发，即一个逻辑信道组内所有的逻辑信道加起来待传数据量有变化则触发BSR。
3、网络配置终端或者协议约定终端在待传数据量有变化、在待传数据量其剩余delay budget(剩余时延预算)有变化、在待传数据量其剩余delay budget(剩余时延预算)小于或者等于阈值中存在至少一者，进行BSR上报时，该上报的BSR可以为常规BSR的一种或者另外命名为一种新类型的BSR；比如为updated BSR，即更新BSR。
4、网络配置终端或者协议约定终端在待传数据量有变化后或者在待传数据量其剩余delay budget(剩余时延预算)有变化后或者在待传数据量其剩余delay budget(剩余时延预算)小于或者等于阈值进行BSR上报时，该BSR可以关联到指定的逻辑信道ID或者新的逻辑信道ID；这样基站收到之后，则可以通过该逻辑信道ID识别该类型的BSR。
作为一种实施例，新的逻辑信道ID可以针对长BSR(Long BSR)和短BSR(Short BSR)分别配置。
5、网络配置终端或者协议约定终端在PDCP层进行了批量丢包操作后进行BSR更新上报的附加限定条件。
a)、作为一个实施例：可以在配置了该BSR更新上报功能之后满足条件即进行首次上报。
b)、作为一个实施例：可以配置或者约定终端需要在BSR上报值有变化之后才能上报。
c)、作为一种实施例：可以配置或者协议约定终端上报需要遵循禁止定时器限制，即终端需要在BSR上报值有变化且禁止定时器没有在运行才能上报；上报之后启动禁止定时器；禁止定时器为网络配置。
6、基于1，基站通过专用信令通知或协议约定终端使用使能该特性。
a)、方式1：其使能粒度可以是per UE(每个终端)粒度或者针对单个UE配置是否生效该特性。
作为一种实施例，若基站知晓终端为进行XR业务的终端，将使能该功能；则意味着该UE的所有的逻辑信道或者逻辑信道组上都生效。
b)、方式2：其使能粒度可以是per RB(每个无线承载)粒度或者配置每个无线承载生效该特性。
作为一种实施例，若基站知晓终端为进行XR业务的终端，则通知其对于特定的RB其将使能该功能；则意味着该RB关联的所有的逻辑信道或者逻辑信道组上都生效。
c)、方式3：其使能粒度可以是per逻辑信道(每个逻辑信道)或者逻辑信道组粒度。
作为一种实施例，即基站通知终端其对于特定的逻辑信道或者逻辑信道组使能该功能。
d)、其使能该功能的通知方式为显示或者隐含通知。
作为一种实施例：若网络通知了针对某个逻辑信道的丢包阈值门限，则意味着使能该功能。
e)、作为一种实施例：该功能仅在周期BSR触发没有配置时使用(若配置了周期BSR上报，则可以及时更新，但是周期性BSR需要开销较大，该方式比周期BSR更好的地方在于基于门限事件触发，其上报开销较小)。
f)、作为一种实施例，协议约定终端其对于特定的逻辑信道或者逻辑信道组使能该功能。其中，特定的逻辑信道或者逻辑信道组为配置了使用特定类型BSR表格(第二BSRtable)进行BSR上报的逻辑信道或者逻辑信道组。作为一种实施例，第二BSR表格是为XR类型业务新引入的Buffersize(缓冲量)映射到不同量化等级的表格。
7、基于1，基站通过专用信令通知终端使用该功能可以基于终端的辅助信息；
a)、终端的辅助信息包括终端是否支持使用该功能的能力。
b)、终端的辅助信息包括终端是否期望使用该功能(终端发现基站经常分配多余实际数据的授权，则意识到网络获取到的BSR可能过大，将上报辅助信息，标识期望使用)。

Claims (26)

  1. 一种缓冲状态报告上报方法，其特征在于，所述方法被用户设备执行，所述方法包括：
    响应于所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行缓冲状态报告的更新上报。
  2. 根据权利要求1所述的方法，其特征在于，所述响应于所述用户设备的待传数据量变化，进行缓冲状态报告的更新上报，包括：
    响应于所述待传数据量的变化值大于待传数据量变化阈值，进行缓冲状态报告的更新上报。
  3. 根据权利要求1所述的方法，其特征在于，所述响应于所述待传数据量的剩余时延预算变化，进行缓冲状态报告的更新上报，包括：
    在所述剩余时延预算减小的情况下，进行缓冲状态报告的更新上报，和/或；
    在所述待传数据量减小导致所述剩余时延预算增大的情况下，进行缓冲状态报告的更新上报。
  4. 根据权利要求1所述的方法，其特征在于，所述响应于所述用户设备的待传数据量变化，进行缓冲状态报告的更新上报，包括：
    响应于所述用户设备的至少一个逻辑信道或至少一个逻辑信道组的待传数据量变化，进行缓冲状态报告的更新上报。
  5. 根据权利要求1所述的方法，其特征在于，所述进行缓冲状态报告的更新上报，包括：
    将上报至网络设备的缓冲状态报告，更新为常规缓冲状态报告中的任意一种或更新为第二类型的缓冲状态报告。
  6. 根据权利要求1所述的方法，其特征在于，所述响应于所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行缓冲状态报告的更新上报，包括：
    在所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，且存在以下至少一种条件的情况下，进行缓冲状态报告的更新上报：
    所述用户设备配置了缓冲状态报告更新功能、所述缓冲状态报告的上报值变化、所述用户设备配备的禁止定时器未运行。
  7. 根据权利要求1所述的方法，其特征在于，所述进行缓冲状态报告的更新上报包括：
    使能缓冲状态报告更新功能，进行所述缓冲状态报告的更新上报；
    其中，通过以下至少一种条件，确定使能所述缓冲状态报告更新功能：
    接收用于指示所述用户设备使能所述缓冲状态报告更新功能的信令；
    接收用于指示所述用户设备的无线承载使能所述缓冲状态报告更新功能的信令；
    接收用于指示所述用户设备的逻辑信道或逻辑信道组使能所述缓冲状态报告更新功能的信令。
  8. 根据权利要求7所述的方法，其特征在于，所述接收用于指示所述用户设备的逻辑信道或逻辑信道组使能所述缓冲状态报告更新功能的信令，包括：
    接收用于指示所述用户设备的第一逻辑信道或第一逻辑信道组，使能所述缓冲状态报告更新功能的信令。
  9. 根据权利要求1所述的方法，其特征在于，所述进行缓冲状态报告的更新上报之前，所述方法还包括：
    将所述用户设备的辅助信息上报至网络设备，所述辅助信息包括以下至少一者：
    所述用户设备是否支持使用缓冲状态报告更新功能的能力、所述用户设备是否期望使用所述缓冲状态报告更新功能。
  10. 一种缓冲状态报告上报方法，其特征在于，所述方法被网络设备执行，所述方法包括：
    接收用户设备更新上报的缓冲状态报告。
  11. 根据权利要求10所述的方法，其特征在于，所述接收用户设备更新上报的缓冲状态报告，包括：
    接收用户设备更新上报的缓冲状态报告；
    根据所述缓冲状态报告，确定所述用户设备的待传数据量与所述待传数据量的剩余时延预算中的至少一者变化。
  12. 根据权利要求11所述的方法，其特征在于，所述根据所述缓冲状态报告，确定所述用户设备的待传数据量变化，包括：
    根据所述缓冲状态报告，确定所述待传数据量的变化值大于待传数据量变化阈值。
  13. 根据权利要求11所述的方法，其特征在于，所述根据所述缓冲状态报告，确定所述待传数 据量的剩余时延预算中变化，包括：
    根据所述缓冲状态报告，确定所述剩余时延预算减小和/或所述待传数据量减小导致所述剩余时延预算增大。
  14. 根据权利要求11所述的方法，其特征在于，所述根据所述缓冲状态报告，确定所述用户设备的待传数据量变化，包括：
    根据所述缓冲状态报告，确定所述用户设备的至少一个逻辑信道或至少一个逻辑信道组的待传数据量变化。
  15. 根据权利要求10所述的方法，其特征在于，所述接收所述用户设备更新上报的缓冲状态报告，包括：
    接收所述用户设备更新上报为常规缓冲状态报告中的任意一种缓冲状态报告，或接收用户设备更新上报为第二类型的缓冲状态报告。
  16. 根据权利要求10所述的方法，其特征在于，所述接收所述用户设备更新上报的缓冲状态报告之前，所述方法还包括：
    向所述用户设备发送用于指示所述用户设备使能缓冲状态报告更新功能的信令，和/或；
    向所述用户设备发送用于指示所述用户设备的无线承载使能缓冲状态报告更新功能的信令，和/或；
    向所述用户设备发送用于指示所述用户设备的逻辑信道或逻辑信道组使能所述缓冲状态报告更新功能的信令。
  17. 根据权利要求16的方法，其特征在于，通过以下至少一种隐含通知信令的方式，向所述用户设备发送用于指示所述用户设备使能缓冲状态报告更新功能的信令：
    向所述用户设备发送所述用户设备的待传数据量变化阈值、指示所述用户设备在未配置周期缓冲状态报告的状态下使用缓冲状态报告更新功能。
  18. 根据权利要求16的方法，其特征在于，所述向所述用户设备的无线承载发送用于指示所述无线承载使能缓冲状态报告更新功能的信令，包括：
    向所述用户设备发送所述无线承载的待传数据量变化阈值。
  19. 根据权利要求16所述的方法，其特征在于，所述向所述用户设备的逻辑信道或逻辑信道组发送用于指示逻辑信道或逻辑信道组使能所述缓冲状态报告更新功能的信令，包括：
    向所述用户设备发送所述逻辑信道或所述逻辑信道组的待传数据量变化阈值。
  20. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    接收所述用户设备发送的辅助信息，所述辅助信息包括以下至少一者：
    所述用户设备是否支持使用缓冲状态报告更新功能的能力、所述用户设备是否期望使用所述缓冲状态报告更新功能。
  21. 一种缓冲状态报告上报装置，其特征在于，所述装置被配置在用户设备，所述装置包括：
    缓冲状态报告发送模块，被配置为响应于所述用户设备的待传数据量与所述待传数据量的剩余时延预算中至少一者变化，进行缓冲状态报告的更新上报。
  22. 一种缓冲状态报告上报装置，其特征在于，所述装置被配置在网络设备，所述装置包括：
    缓冲状态报告接收模块，被配置为接收用户设备更新上报的缓冲状态报告。
  23. 一种用户设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为在执行所述可执行指令时，实现权利要求1～9任一项所述方法的步骤。
  24. 一种网络设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为在执行所述可执行指令时，实现权利要求10～20任一项所述方法的步骤。
  25. 一种计算机可读存储介质，其上存储有计算机程序指令，其特征在于，该程序指令被处理器执行时实现权利要求1～9中任一项所述方法的步骤，或实现权利要求10～20中任一项所述方法的步骤。
  26. 一种芯片，其特征在于，包括处理器和接口；所述处理器用于读取指令以执行权利要求1～9中任一项所述方法的步骤，或执行权利要求10～20中任一项所述方法的步骤。
PCT/CN2022/129675 2022-11-03 2022-11-03 缓冲状态报告上传方法、装置、设备、存储介质与芯片 Ceased WO2024092667A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2022/129675 WO2024092667A1 (zh) 2022-11-03 2022-11-03 缓冲状态报告上传方法、装置、设备、存储介质与芯片
EP22963977.8A EP4614896A4 (en) 2022-11-03 2022-11-03 METHOD AND APPARATUS FOR DOWNLOADING BUFFER STATUS REPORTS, DEVICE, STORAGE MEDIA AND CHIP
CN202280004510.9A CN115997408A (zh) 2022-11-03 2022-11-03 缓冲状态报告上传方法、装置、设备、存储介质与芯片

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/129675 WO2024092667A1 (zh) 2022-11-03 2022-11-03 缓冲状态报告上传方法、装置、设备、存储介质与芯片

Publications (1)

Publication Number Publication Date
WO2024092667A1 true WO2024092667A1 (zh) 2024-05-10

Family

ID=85993911

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/129675 Ceased WO2024092667A1 (zh) 2022-11-03 2022-11-03 缓冲状态报告上传方法、装置、设备、存储介质与芯片

Country Status (3)

Country Link
EP (1) EP4614896A4 (zh)
CN (1) CN115997408A (zh)
WO (1) WO2024092667A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118660341A (zh) * 2024-06-25 2024-09-17 新华三技术有限公司 一种数据传输方法、装置、电子设备及存储介质
WO2026021427A1 (zh) * 2024-07-26 2026-01-29 夏普株式会社 由用户设备执行的方法以及用户设备

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118741593A (zh) * 2023-03-31 2024-10-01 荣耀终端有限公司 信息处理方法及装置
CN118945717A (zh) * 2023-05-09 2024-11-12 华为技术有限公司 信息上报方法、装置及系统
WO2024229786A1 (en) * 2023-05-11 2024-11-14 Apple Inc. Technologies for logical channel group specific buffer status reporting
CN117615411B (zh) * 2024-01-23 2024-05-24 荣耀终端有限公司 通信方法、设备及存储介质
WO2026030988A1 (en) * 2024-08-07 2026-02-12 Apple Inc. Delay status reporting

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132619A (zh) * 2006-08-22 2008-02-27 大唐移动通信设备有限公司 终端缓冲区数据量信息上报方法
US20100135166A1 (en) * 2007-06-19 2010-06-03 Nec Corporation Buffer status reproting
US20100271990A1 (en) * 2009-04-24 2010-10-28 Motorola, Inc. Method and apparatus for triggering buffer status reports with packet discarding
CN107277856A (zh) * 2017-05-05 2017-10-20 电信科学技术研究院 一种配置、触发缓冲区状态上报的方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101541099B (zh) * 2008-03-21 2011-12-07 中兴通讯股份有限公司 缓冲区状态报告方法及装置、数据量设置方法
CN106941729B (zh) * 2016-01-04 2020-06-16 中国移动通信集团公司 一种上传和接收缓冲区状态的方法、装置
CN109429568B (zh) * 2017-06-19 2022-07-29 北京小米移动软件有限公司 一种上报缓存状态报告的方法及装置
EP4017196B1 (en) * 2020-03-18 2025-08-13 LG Electronics Inc. Method and device for determining priority of harq feedback in nr v2x
CN116114298A (zh) * 2020-08-06 2023-05-12 苹果公司 高传播延迟网络中用于减少延迟的用户装备（ue）补充bsr

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132619A (zh) * 2006-08-22 2008-02-27 大唐移动通信设备有限公司 终端缓冲区数据量信息上报方法
US20100135166A1 (en) * 2007-06-19 2010-06-03 Nec Corporation Buffer status reproting
US20100271990A1 (en) * 2009-04-24 2010-10-28 Motorola, Inc. Method and apparatus for triggering buffer status reports with packet discarding
CN107277856A (zh) * 2017-05-05 2017-10-20 电信科学技术研究院 一种配置、触发缓冲区状态上报的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4614896A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118660341A (zh) * 2024-06-25 2024-09-17 新华三技术有限公司 一种数据传输方法、装置、电子设备及存储介质
WO2026021427A1 (zh) * 2024-07-26 2026-01-29 夏普株式会社 由用户设备执行的方法以及用户设备

Also Published As

Publication number Publication date
EP4614896A4 (en) 2025-11-26
EP4614896A1 (en) 2025-09-10
CN115997408A (zh) 2023-04-21

Similar Documents

Publication Publication Date Title
WO2024092667A1 (zh) 缓冲状态报告上传方法、装置、设备、存储介质与芯片
CN119318174A (zh) 用于pdu集延迟状态报告的方法及设备
CN113615295B (zh) 用于sl sr/bsr处理的方法
CN118042518A (zh) 一种通信方法和装置
CN120692593A (zh) 传输bsr的方法及装置
EP4510529A1 (en) Communication method and apparatus
CN109246753B (zh) 一种传输数据的方法、网络设备和终端设备
WO2021022508A1 (zh) 边链路调度请求的触发方法、装置和系统
WO2018202037A1 (zh) 传输数据的方法、终端设备和网络设备
WO2024065109A1 (zh) 信息传输控制方法、装置、通信设备及存储介质
WO2024152330A1 (zh) 调度请求传输方法及装置、通信设备及存储介质
EP4593457A1 (en) Buffer status report reporting method and apparatus, and communication device and storage medium
EP4654698A1 (en) Delay reporting method and apparatus, and user equipment and network-side device
EP4583573A1 (en) Data packet discarding method and related device
CN118542046A (zh) 无线通信的方法、终端设备和网络设备
CN118104287A (zh) 数据传输方法、设备及存储介质
CN121866806A (zh) 一种信息发送、接收和处理方法、装置、通信系统
CN114175744A (zh) 一种传输数据的方法和装置
CN111918328A (zh) 一种用户设备资源调度方法及装置
WO2024067106A1 (zh) 通信方法、装置及计算机可读存储介质
EP4645944A1 (en) Information transmission method and apparatus, communication device, and storage medium
RU2858557C2 (ru) Способ сообщения отчета о состоянии буфера и устройство связи
CN113709887A (zh) 数据发送方法和设备
CN110546914A (zh) 资源配置的方法及装置、通信设备及存储介质
CN119562337A (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: 22963977

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202527047436

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2022963977

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022963977

Country of ref document: EP

Effective date: 20250603

WWP Wipo information: published in national office

Ref document number: 202527047436

Country of ref document: IN

WWP Wipo information: published in national office

Ref document number: 2022963977

Country of ref document: EP