WO2023065965A1 - 通信方法、装置以及存储介质 - Google Patents

通信方法、装置以及存储介质 Download PDF

Info

Publication number
WO2023065965A1
WO2023065965A1 PCT/CN2022/120864 CN2022120864W WO2023065965A1 WO 2023065965 A1 WO2023065965 A1 WO 2023065965A1 CN 2022120864 W CN2022120864 W CN 2022120864W WO 2023065965 A1 WO2023065965 A1 WO 2023065965A1
Authority
WO
WIPO (PCT)
Prior art keywords
format
bsr
value
lcg
identifier
Prior art date
Application number
PCT/CN2022/120864
Other languages
English (en)
French (fr)
Inventor
孙飞
朱元萍
史玉龙
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22882576.6A priority Critical patent/EP4408064A1/en
Publication of WO2023065965A1 publication Critical patent/WO2023065965A1/zh
Priority to US18/641,114 priority patent/US20240276291A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0006—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
    • H04L1/0007—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format by modifying the frame length
    • H04L1/0008—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format by modifying the frame length by supplementing frame payload, e.g. with padding bits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1614—Details of the supervisory signal using bitmaps
    • 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/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • 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
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present application relates to the technical field of communication, and in particular to a communication method, device and storage medium.
  • the communication device when the communication device has buffered data to transmit, it reports the amount of buffered data of the communication device to the base station through a buffer status report (BSR), so that the base station allocates uplink data for the communication device according to the amount of buffered data of the communication device. transfer resources.
  • BSR buffer status report
  • the communication device may establish a large number of radio bearers. If a BSR is reported for each logical channel (logical channel, LCH), a large amount of signaling overhead will be brought. In order to reduce this overhead, LCH combinations are classified to form a logical channel group (logical channel group, LCG), and each LCH corresponds to one LCG. The BSR is reported at the granularity of the LCG.
  • the buffered data amount of each LCG includes the total amount of buffered data of all logical channels included in the LCG.
  • the corresponding relationship between LCG and LCH of the communication device is configured by the base station.
  • LTE long term evolution
  • LCG long term evolution
  • NR new air interface
  • Embodiments of the present application provide a communication method, device, and storage medium, capable of reporting a BSR reasonably.
  • the embodiment of the present application provides a communication method, the communication method includes:
  • the target cache status report BSR format based on the comparison result of the first identifier and the first value, wherein the first identifier is the largest LCG identifier among the LCG identifiers of the logical channel group LCG with cached data; according to the target BSR format Generate BSRs.
  • the communication device can determine an appropriate BSR format to report the BSR according to the comparison result between the first identifier and the first value, and can reasonably use uplink transmission resources to report the BSR, so as to realize fine-grained scheduling of network resources.
  • the determining the target BSR format based on the comparison result between the first identifier and the first value includes: when the first identifier is greater than the first value, setting the A format is determined as the target BSR format, and the BSR in the first format is used to report the buffered data volume of the LCG whose LCG identifier is within a first identifier threshold; when the first identifier is less than or equal to the first value
  • the second format is determined as the target BSR format, and the BSR in the second format is used to report the buffered data volume of the LCG whose LCG identifier is within the second identification threshold; wherein, the first identification threshold is greater than the specified The second identification threshold.
  • the number of bits of the BSR in the first format is greater than that of the BSR in the second format, and the BSR in the second format cannot report LCGs whose LCG identifiers are greater than the first value. If the first identifier is greater than the first numerical value, determine the first format as the target BSR format; if the first identifier is less than or equal to the first numerical value, determine the second format as the target BSR format. While ensuring the integrity of the reported LCG with cached data, the number of bits required for reporting the BSR is saved, and resource utilization efficiency is improved.
  • the first format or the second format when the number of LCGs with cached data is 1, the first format or the second format is a short BSR format; or, when the number of LCGs with cached data When the number of LCGs with cached data is greater than 1 and less than the second value, the first format or the second format is a medium BSR format; or, when the number of LCGs with cached data is greater than or equal to the second value In some cases, the first format or the second format is a long BSR format.
  • the specific format of the first format or the second format is determined according to the number of LCGs with cached data, wherein the above-mentioned short BSR format is used to report the amount of cached data of one LCG, the above-mentioned long BSR format and the above-mentioned medium
  • the BSR format can report the buffered data volume of one or more LCGs, and the number of bits of the short BSR format is smaller than that of the long BSR format and the medium BSR format.
  • the number of bits of the BSR in the medium BSR format is less than the number of bits in the BSR in the long BSR format; the number of LCGs reported in the BSR In the case of greater than or equal to the second value, when reporting the same number of LCGs, the number of bits of the BSR in the medium BSR format is greater than or equal to the number of bits in the BSR in the long BSR format.
  • the first format or the second format is a short BSR format; when the number of LCGs with cached data is greater than 1 and less than the second value, the first format or the second format
  • the second format is a medium BSR format; when the number of LCGs with cached data is greater than or equal to the second value, the first format or the second format is a long BSR format. While ensuring the integrity of the reported LCG, the number of bits required for reporting the BSR is saved, and resource utilization efficiency is improved.
  • the BSR in the long BSR format includes a first bit map, and each bit in the first bit map is used to indicate whether each LCG in at least one LCG exists Buffer data, or used to indicate whether the buffer size BS field corresponding to each LCG in at least one LCG exists.
  • the bitmap is used to indicate whether each LCG in at least one LCG has cached data, or to indicate whether the cache size BS field corresponding to each LCG in at least one LCG exists, without reporting the LCG In the case that the number of reported LCGs is greater than or equal to the second value, the number of bits required for reporting the BSR is saved, and the waste of the number is reduced.
  • the BSR in the medium BSR format includes an LCG identifier of at least one LCG, and indication information for indicating a cached data amount of the at least one LCG.
  • the medium BSR format is used to report the BSR, which saves the number of bits required for reporting the BSR and improves resource utilization efficiency.
  • the BSR in the short BSR format includes an LCG identifier of the first LCG, and indication information for indicating the amount of cached data of the first LCG.
  • the short BSR format is used to report the BSR, which can rationally utilize uplink transmission resources and reduce data waste.
  • the determining the target BSR format based on the comparison result between the first identifier and the first value includes: based on the comparison result between the first identifier and the first value, and filling A comparison result of the number of bits and the third value determines the target BSR format.
  • the target BSR format is determined according to the comparison result between the first identifier and the first value, and the comparison result between the number of padding bits and the third value, so as to select an appropriate BSR format to report the cached
  • the amount of buffered data in the LCG of the data can be reported to the BSR by rational use of uplink resources, and the refined scheduling of network resources can be realized.
  • the target BSR format is determined based on a comparison result between the first identifier and the first value, and a comparison result between the number of padding bits and a third value, Including: when the first identifier is greater than the first value and the number of filling bits is greater than or equal to a third value, determining the first format as the target BSR format; or, when the first identifier is greater than In the case of the first value and the number of filling bits is less than the third value, determine the second format as the target BSR format; the BSR in the second format is used to report the cached data In the LCG, the LCG identifier is less than the first numerical value of the LCG cache data volume; or, in the case that the first identifier is less than or equal to the first numerical value, the second format is determined as the target BSR format .
  • the BSR in the first format and the BSR in the second format can report different LCG identification thresholds and occupy different bits. Determine the appropriate BSR format from the first format and the second format according to the comparison result of the first identifier and the first value and the number of padding bits, and use the BSR format to report the BSR to ensure the integrity of the reported LCG.
  • the first format when the number of filling bits is equal to the third value, the first format is a short BSR format; or, when the number of filling bits is greater than the specified When the third value is less than the fourth value, the first format is a medium BSR format; or, when the number of filling bits is greater than or equal to the fourth value, the first format is Long BSR format.
  • the specific format of the first format is determined according to the number of stuffing bits.
  • the first format is a short BSR format; when the number of stuffing bits is greater than the third value and less than the fourth numerical value, the first format is a medium BSR format; in the case that the number of stuffing bits is greater than or equal to the fourth numerical value, the first format is a long BSR format, ensuring that the number of stuffing bits is greater than or equal to the first
  • the size of the BSR in the format plus the size of the MAC subheader of the BSR in the first format reduces the occurrence of the situation that the BSR cannot be reported because the number of bits in the generated BSR is greater than the number of filling bits.
  • the third value is determined according to a size of the BSR in the first format and a size of a media access control MAC subheader of the BSR in the first format.
  • the third value may specifically be the number of bits occupied by the BSR in the first format when reporting the cached data volume of an LCG plus the number of bits occupied by the MAC subheader in the first format, that is, the third value is the communication The minimum number of bits required by the device to send a BSR in the first format. If the number of stuffing bits is greater than the third value, the first format is determined as the target BSR format, and the stuffing bits are ensured to be sufficient to report the generated BSR in the first format.
  • the determining the target BSR format based on the comparison result between the first identifier and the first value includes: based on the comparison result between the first identifier and the first value, and the The number of LCGs with cached data determines the target BSR format.
  • the target BSR format is determined according to the comparison result between the first identifier and the first value, and the number of LCGs with buffered data, so as to select an appropriate BSR format to report the buffered data volume of the LCG with buffered data , can reasonably use the uplink resources to report to the BSR, and realize fine scheduling of network resources.
  • the determining the target BSR format based on the comparison result of the first identifier and the first value, and the number of LCGs with cached data includes: When the first identifier is greater than the first value and the number of LCGs with cached data is 1, determine the first short BSR format as the target BSR format; or, when the first identifier is greater than the If the first value and the number of LCGs with cached data is greater than 1 and less than a second value, determine the intermediate BSR format as the target BSR format; or, when the first identifier is greater than the first value And when the number of LCGs with cached data is greater than or equal to the second value, determine the first long BSR format as the target BSR format; or, when the first identifier is less than or equal to the second value When a value and the number of LCGs with cached data is 1, determine the second short BSR format as the target BSR format; or, when the first identifier is less than or equal to the first value
  • the first long BSR format, the first short BSR format, the medium BSR format, the second long BSR format and A suitable BSR format is determined in the second short BSR format, and the BSR is reported by using the BSR format. While ensuring the integrity of the reported LCG, the number of bits required for reporting the BSR is saved, and resource utilization efficiency is improved.
  • the determining the target BSR format based on the comparison result between the first identifier and the first value includes: based on the comparison result between the first identifier and the first value, the The number of LCGs with buffered data and the number of padding bits determine the target BSR format.
  • the target BSR format is determined according to the comparison result of the first identifier and the first value, the number of LCGs with cached data, and the comparison result of the number of padding bits and the third value, to Selecting an appropriate BSR format to report the buffered data volume of the LCG with buffered data can make reasonable use of uplink resources to report to the BSR, and realize fine-grained scheduling of network resources.
  • the target BSR format is determined based on the comparison result between the first identifier and the first value, the number of LCGs with cached data, and the number of padding bits , including: when the first identifier is greater than the first value, the number of LCGs with cached data is 1, and the number of padding bits is greater than or equal to a third value, the first short BSR format Determined as the target BSR format; or, when the first identifier is greater than the first value, the number of LCGs with cached data is greater than 1, and the number of filling bits is equal to the third value , determining the first short BSR format as the target BSR format; or, when the first identifier is greater than the first value, the number of LCGs with cached data is greater than 1, and the padding bits
  • the second short BSR format is determined as the target BSR format, and the BSR in the second short BSR format is used to report that the LCG identifier in the L
  • the first long BSR format, the first short BSR format, the middle BSR format the first Determine a suitable BSR format from the second long BSR format and the second short BSR format, and use this BSR format to report the BSR. While ensuring the integrity of the reported LCG, it saves the number of bits required to report the BSR and improves resource utilization efficiency. .
  • the fifth value is determined according to a size of a BSR in the second short BSR format and a size of a MAC subheader corresponding to the second short BSR format.
  • the first numerical value is 7.
  • the embodiment of the present application provides a communication method, including: determining the target cache status report BSR format based on the comparison result of the second identifier and the first value, the second identifier being the LCG identifier of the LCG configured for the communication device The largest LCG identifier; generate a BSR according to the target BSR format.
  • a BSR format of a format is determined as the target BSR format according to the LCG identifier of the configured LCG of the communication device, and the BSR is reported in the target BSR format.
  • the target BSR format is determined according to the configuration of the communication device, so that the format used by the communication device to report the BSR matches the configuration information of the communication device, and the BSR can be reported reasonably.
  • the determining the target cache status report BSR format based on a comparison result between the second identifier and the first value includes: when the second identifier is greater than the first value , determining the first format as the target BSR format, and the BSR in the first format is used to report the buffered data volume of the LCG whose LCG identifier is within the first identifier threshold; when the second identifier is less than or equal to the first identifier threshold In the case of a value, the second format is determined as the target BSR format, and the BSR in the second format is used to report the buffered data volume of the LCG whose LCG identifier is within the second identifier threshold; wherein the first identifier The threshold is greater than the second identification threshold.
  • the number of bits of the BSR in the first format is greater than that of the BSR in the second format, and the BSR in the second format cannot report LCGs whose LCG identifiers are greater than the first value. If the second identifier is greater than the first numerical value, determine the first format as the target BSR format; if the second identifier is less than or equal to the first numerical value, determine the second format as the target BSR format. While ensuring the integrity of the reported LCG with cached data, the number of bits required for reporting the BSR is saved, and resource utilization efficiency is improved.
  • an embodiment of the present application provides a communication method, including: determining a target BSR format based on the number of LCGs configured on a communication device; and generating a BSR according to the target BSR format.
  • a BSR format of one format is determined as the target BSR format according to the number of LCGs configured on the communication device, and the BSR is reported in the target BSR format.
  • the target BSR format is determined according to the configuration of the communication device, so that the format used by the communication device to report the BSR matches the configuration information of the communication device, and the BSR can be reported reasonably.
  • the determining the target BSR format based on the number of LCGs configured on the communication device includes: when the number of LCGs is greater than a first value, determining the first format as The target BSR format, the BSR in the first format is used to report the amount of buffered data of the LCG whose LCG identifier is within the first identifier threshold; when the number of the LCG is less than or equal to the first value, the The second format is determined as the target BSR format, and the BSR in the second format is used to report the cached data volume of the LCG whose LCG identifier is within a second identification threshold; wherein, the first identification threshold is greater than the second identification threshold.
  • the number of bits of the BSR in the first format is greater than that of the BSR in the second format, and the BSR in the second format cannot report LCGs whose LCG identifiers are greater than the first value.
  • determine the first format as the target BSR format determines the first format as the target BSR format; when the number of LCGs configured on the communication device is less than or equal to the first value, determine the second format Determined as the target BSR format.
  • the embodiment of the present application provides a communication device, including:
  • a processing module configured to determine a target cache status report BSR format based on a comparison result between the first identifier and the first value, wherein the first identifier is the largest LCG identifier among the LCG identifiers of the logical channel group LCG with cached data;
  • the processing module is further configured to generate a BSR according to the target BSR format
  • a transceiver module configured to send the BSR to a network device.
  • the processing module is specifically configured to determine the first format as the target BSR format when the first identifier is greater than the first value, and the The BSR in the first format is used to report the cached data volume of the LCG whose LCG identifier is within the first identifier threshold; when the first identifier is less than or equal to the first value, determine the second format as the target BSR format, the BSR in the second format is used to report the buffered data volume of the LCG whose LCG identifier is within a second identification threshold; wherein, the first identification threshold is greater than the second identification threshold.
  • the first format or the second format when the number of LCGs with cached data is 1, the first format or the second format is a short BSR format; or, when the number of LCGs with cached data When the number of LCGs with cached data is greater than 1 and less than the second value, the first format or the second format is a medium BSR format; or, when the number of LCGs with cached data is greater than or equal to the second value In some cases, the first format or the second format is a long BSR format.
  • the BSR in the long BSR format includes a first bit map, and each bit in the first bit map is used to indicate whether each LCG in at least one LCG exists Buffer data, or used to indicate whether the buffer size BS field corresponding to each LCG in at least one LCG exists.
  • the BSR in the medium BSR format includes an LCG identifier of at least one LCG, and indication information for indicating a cached data amount of the at least one LCG.
  • the BSR in the short BSR format includes an LCG identifier of the first LCG, and indication information for indicating the amount of buffered data of the first LCG.
  • the processing module is specifically configured to determine based on a comparison result between the first identifier and the first value, and a comparison result between the number of padding bits and the third value The target BSR format.
  • the processing module is specifically configured to convert the first format to determined as the target BSR format; or,
  • the second format determines the second format as the target BSR format; the BSR in the second format is used for Reporting the amount of buffered data in the LCGs whose LCG identifiers are smaller than the first value among the LCGs with cached data; or, when the first identifier is less than or equal to the first value, the second format Determine the format for the target BSR.
  • the first format when the number of filling bits is equal to the third value, the first format is a short BSR format; or, when the number of filling bits is greater than the specified When the third value is less than the fourth value, the first format is a medium BSR format; or, when the number of filling bits is greater than or equal to the fourth value, the first format is Long BSR format.
  • the third value is determined according to a size of the BSR in the first format and a size of a media access control MAC subheader of the BSR in the first format.
  • the processing module is specifically configured to determine the target based on a comparison result between the first identifier and the first value, and the number of LCGs with cached data BSR format.
  • the processing module is specifically configured to set the first short Determine the BSR format as the target BSR format; or, if the first identifier is greater than the first value and the number of LCGs with cached data is greater than 1 and less than a second value, determine the intermediate BSR format is the target BSR format; or, when the first identifier is greater than the first value and the number of LCGs with cached data is greater than or equal to the second value, determine the first long BSR format is the target BSR format; or, when the first identifier is less than or equal to the first value and the number of LCGs with cached data is 1, determine the second short BSR format as the target BSR format; or, when the first identifier is less than or equal to the first value and the number of LCGs with cached data is greater than 1, determine the second long BSR format as the target BSR format.
  • the processing module is specifically configured to, based on the comparison result between the first identifier and the first value, the number of LCGs with cached data and the number of filling bits Determine the target BSR format.
  • the processing module is specifically configured to: when the first identifier is greater than the first value, the number of LCGs with cached data is 1, and the number of filling bits When the number is greater than or equal to the third value, determine the first short BSR format as the target BSR format; or, when the first identifier is greater than the first value, the number of LCGs with cached data is greater than 1, and when the number of filling bits is equal to the third value, determine the first short BSR format as the target BSR format; or, when the first identifier is greater than the first value, When the number of LCGs with cached data is greater than 1 and the number of filling bits is less than the third value, determine the second short BSR format as the target BSR format, and the second short BSR format The BSR is used to report the amount of buffered data in the LCG with the LCG identifier smaller than the first value in the LCG with buffered data; or, when the first identifier is greater than the first value
  • the fifth value is determined according to the size of the BSR in the second short BSR format and the size of the MAC subheader corresponding to the second short BSR format.
  • the first numerical value is 7.
  • the embodiment of the present application provides a communication device, the communication device includes a processor and a memory; a computer program is stored in the memory; when the processor executes the computer program, the computing device executes any one of the foregoing first aspects, or Any one of the second aspect, or the method described in any one of the third aspect.
  • the embodiment of the present application provides a communication device, the communication device includes a logic circuit and an interface, and the logic circuit is coupled to the interface; the interface is used to input data to be processed, and the logic circuit is configured as follows: Any one of the first aspect, or any one of the second aspect, or the method described in any one of the third aspect processes the data to be processed to obtain the processed data, and the interface is used to output the the processed data.
  • the embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium stores instructions, and when the instructions are run on at least one processor, any one of the aforementioned first aspects is implemented. , or any one of the second aspect, or the method described in any one of the third aspect.
  • the present application provides a computer program product, the computer program product includes a computer program or computer code, and when it is run on a computer, the above first aspect or any possible implementation of the first aspect shows The method is executed, or the method shown in the second aspect or any possible implementation manner of the second aspect is executed, or the method shown in the third aspect or any possible implementation manner of the third aspect is executed.
  • Fig. 1 is a schematic structural diagram of an IAB system provided by an embodiment of the present application.
  • Fig. 2 is a kind of IAB network architecture diagram provided by the embodiment of the present application.
  • Fig. 3 is the structural representation of a kind of MAC PDU that the embodiment of the present application provides;
  • FIG. 4 is a schematic structural diagram of a BSR format provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of another BSR format provided by the embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of another BSR format provided by the embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of another BSR format provided by the embodiment of the present application.
  • FIG. 8a is a schematic structural diagram of another BSR format provided by the embodiment of the present application.
  • FIG. 8b is a schematic structural diagram of another BSR format provided by the embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a BAP topology of an IAB network adopted in the embodiment of the present application.
  • FIG. 13 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 14 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • an embodiment means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application.
  • the occurrences of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is understood explicitly and implicitly by those skilled in the art that the embodiments described herein can be combined with other embodiments.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (long term evolution, LTE) system, universal mobile telecommunications system (universal mobile telecommunications system, UMTS), fifth generation (5th generation, 5G) system, new radio (new radio, NR) and other new systems that appear with the development of technology.
  • LTE long term evolution
  • UMTS universal mobile telecommunications system
  • 5th generation, 5G fifth generation
  • new radio new radio
  • NR new radio
  • the fifth-generation mobile communication puts forward more stringent requirements for various performance indicators of the network. For example, the capacity has been increased by 1000 times, wider coverage requirements, ultra-high reliability and ultra-low latency, etc.
  • the capacity has been increased by 1000 times, wider coverage requirements, ultra-high reliability and ultra-low latency, etc.
  • the use of high-frequency small cell networking is becoming more and more popular.
  • the propagation characteristics of high-frequency carriers are poor, the attenuation is serious due to occlusion, and the coverage area is not wide, so a large number of densely deployed small stations are required.
  • IAB technology provides an idea to solve the above two problems: its access link and backhaul link both adopt wireless transmission solutions, which reduces the deployment of optical fibers.
  • FIG. 1 is an example of an IAB system structure provided by an embodiment of the present application.
  • the relay node RN Relay Node
  • IAB node IAB node
  • UE user equipment
  • the road is connected to the IAB donor (IAB donor) for transmission.
  • the IAB donor may also be called a donor node (donor node) or a donor base station (DgNB, Donor gNodeB).
  • the IAB node is composed of a mobile terminal (mobile termination, MT) part and a distributed unit (distributed unit, DU).
  • the host base station DgNB can be an access network element with complete base station functions, or an access network element in the form of separation of a centralized unit (CU) and a distributed unit (DU).
  • CU centralized unit
  • DU distributed unit
  • Connect to the core network element serving the UE for example, connect to the 5G core network, 5GC) and provide the wireless backhaul function for the IAB node.
  • the centralized unit of the host node is referred to as the donor CU (or directly referred to as the CU), and the distributed unit of the host node is referred to as the donor DU.
  • the donor CU may also be the control plane (control plane, CP) and User plane (user plane, UP) separation form, for example: CU can be composed of one CU-CP and one (or more) CU-UP.
  • FIG. 1 takes 2 UEs and 5 IAB nodes as an example.
  • the two UEs are UE1 and UE2 respectively, and the five IAB nodes are IAB node 1-IAB node 5 respectively.
  • the thick lines in FIG. 1 indicate access links, and the thin lines indicate backhaul links.
  • UE2 may be connected to the donor base station via IAB node 5 , IAB node 2 and IAB node 1 .
  • UE2 may also be connected to the donor base station via IAB node 4 , IAB node 2 and IAB node 1 .
  • UE2 may also be connected to the donor base station via IAB node 4 , IAB node 3 and IAB node 1 .
  • UE1 can be connected to the donor base station via IAB node 4 , IAB node 3 and IAB node 1 .
  • UE1 can be connected to the donor base station via IAB node 4 , IAB node 2 and IAB node 1 .
  • FIG. 1 the communication system shown in FIG. 1 is only an example, and does not limit the applicable application scenarios of this embodiment of the present application. It should be understood that the use of the IAB node in the embodiment of the present application is only for the purpose of description, and it does not mean that the solution in the embodiment of the present application is only used in the NR scenario.
  • one or more IAB nodes may be included on a transmission path between the UE and the IAB host.
  • Each IAB node needs to maintain a wireless backhaul link facing the parent node, and also needs to maintain a wireless link with the child nodes. If the child node of the IAB node is a UE, there is a wireless access link between the IAB node and its child node (that is, the UE). If the child nodes of the IAB node are other IAB nodes, there is a wireless backhaul link between the IAB node and its child nodes (that is, other IAB nodes).
  • UE1 accesses IAB node 4 through a wireless access link, and IAB node 4 connects to The IAB node 3 is connected to the IAB node 1 through a wireless backhaul link, and the IAB node 1 is connected to the IAB host node through a wireless backhaul link.
  • the BSR reporting method provided in the embodiment of the present application can be applied to an IAB network, including a standalone (SA) IAB network and a non-standalone (NSA) IAB network.
  • IAB node includes MT part and DU part, IAB donor can be divided into DU and CU part, CU can be further divided into CU-CP and CU-UP part.
  • FIG. 2 is an example of an IAB network architecture diagram provided by an embodiment of the present application.
  • Figure 2 shows an example of an IAB node connected to an IAB donor through a wireless backhaul link.
  • Figure 2 takes 1 UE, 2 IAB nodes and 2 IAB donors as an example.
  • the two IAB nodes are IAB node 1 and IAB node 2, both of which include MT part and DU part; the two IAB donors are IAB donor 1 and IAB donor 2 respectively.
  • the two IAB donors are IAB donor 1 and IAB donor 2.
  • Each IAB donor can be further divided into DU and CU parts, and CU can also be divided into CU-CP and CU-UP parts.
  • wireless backhaul is used between the MT of IAB node 2 and the DU of IAB node 1, between the MT of IAB node 1 and the DU of IAB donor 1, and between the MT of IAB node 1 and the DU of IAB donor 2 (backhual, BH) link (link) communication;
  • Uu interface is established between UE and IAB2-DU;
  • F1-C interface is established between IAB donor DU and IAB donor CU-CP, IAB donor DU and IAB donor CU-
  • the F1 interface can include two parts: the control plane and the user plane, where the user plane is maintained between IAB-DU and IAB donor CU-UP, and the control plane is maintained between IAB-DU and IAB donor CU-CP of.
  • the F1 interface between IAB-DU and IAB donor CU is not shown in Figure 2.
  • the F1 interface may also be called an F1* interface, and this embodiment of the present application does not limit the name of the interface.
  • the interface is referred to as an F1 interface as an example.
  • the F1 interface can support user plane protocols (F1-U/F1*-U) and control plane protocols (F1-C/F1*-C), and the user plane protocols include one or more of the following protocol layers: general packet radio service (general packet radio service, GPRS) tunneling protocol user plane (GPRS tunneling protocol user plane, GTP-U) protocol layer, user datagram protocol (user datagram protocol, UDP) protocol layer, Internet protocol (internet protocol, IP) protocol layer, etc. ;
  • the control plane protocol includes one or more of the following protocol layers: F1 application protocol (F1 application protocol, F1AP), stream control transport protocol (stream control transport protocol, SCTP), IP protocol layer, etc.
  • the IAB node and the IAB host can perform interface management, manage the IAB-DU, and perform UE context-related configuration, etc.
  • functions such as user plane data transmission and downlink transmission status feedback can be performed between the IAB node and the IAB host.
  • the IAB node When the IAB node works in SA mode, the IAB node can be single-connected to one parent node, or dual-connected to two parent nodes.
  • the two parent nodes can be controlled by the same IAB donor, or controlled by different IAB donors. It is enough to establish an F1 interface between the DU part of the IAB node and an IAB donor.
  • the IAB donor can be connected to the 5G core network, which is the thick line in Figure 2.
  • the IAB-donor-CU-CP is connected to the control plane network elements (such as access and mobility management functions) in the 5GC through the NG control plane interface (NG-C), and the IAB-donor-CU-UP is connected to the NG user plane interface (NG-U) is connected to user plane network elements (eg user plane functions) in 5GC.
  • control plane network elements such as access and mobility management functions
  • NG-C NG control plane interface
  • NG-U NG user plane interface
  • user plane network elements eg user plane functions
  • the IAB-donor-CU-UP can be connected to the EPC (for example, connected to the serving gateway (SGW)) through the S1 user plane interface (S1-U), the MT of the MeNB and the IAB node There is an LTE Uu air interface connection between them, and there is an X2-C interface between MeNB and IAB-donor-CU-CP.
  • MeNB is connected to EPC through S1 interface (including S1 interface user plane and S1 interface control plane), that is, in Figure 2 The dotted line part of .
  • the MeNB in Figure 2 can also be replaced with a 5G base station gNB.
  • the LTE-Uu interface in Figure 2 is replaced by the NR-Uu interface accordingly.
  • the gNB can establish a user plane and/or control plane interface with the 5GC.
  • the gNB and IAB-donor provide dual connection services for the IAB node.
  • the gNB can The role of the primary base station as the IAB node, or the role of the secondary base station.
  • the terminal device may be called user equipment (user equipment, UE), terminal device, terminal, mobile station (mobile station, MS), mobile terminal (mobile terminal, MT) and so on.
  • a terminal device may comprise a handheld device with wireless connectivity, or a communication device connected to a wireless modem.
  • the terminal device can communicate with the core network via a radio access network (radio access network, RAN), and exchange voice and/or data with the RAN.
  • a terminal device can be called an access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless network equipment, user agent, or user device.
  • the terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the communication device reports the BSR through the MAC control element (control element, CE) of the media access control (Media Access Control, MAC) layer.
  • the MAC CE may be included in a MAC protocol data unit (protocol data unit, PDU), for example, a MAC PDU may include one or more MAC sub-PDUs (subPDU).
  • a MAC subPDU may include any of the following:
  • a MAC subheader plus a MAC service data unit (service data unit, SDU);
  • FIG. 3 is a schematic structural diagram of a MAC PDU provided in an embodiment of the present application.
  • the MAC PDU shown in Figure 3 includes at least 5 MAC subPDUs, including two MAC SDUs, a fixed-size MAC CE 1, a variable-size MAC CE 2, and padding.
  • the sub-header of the above-mentioned MAC SDU and variable-sized MAC CE 2 consists of four header fields R/F/LCID/L.
  • the subheader of a fixed-size MAC CE 1 consists of two header fields R/LCID. It can be understood that the description about the MAC PDU shown in FIG. 3 is only an example, and should not be construed as a limitation to this embodiment of the present application.
  • the R field is a reserved bit, set to 0.
  • the L field is in bytes and indicates the length of the corresponding MAC SDU or variable-sized MAC CE.
  • each MAC subheader has an L field.
  • the size of the L field is indicated by the F field.
  • the F field occupies 1 bit and is used to indicate the size of the length field (L field).
  • L field the length field
  • each MAC subheader has an F field. .
  • the F field is 0, it means that the length field occupies 8 bits, and when the F field is 1, it means that the length field occupies 16 bits.
  • the LCID field occupies 6 bits, and each MAC subheader has an LCID field. This field indicates the logical channel instance corresponding to the MAC SDU, and the type or padding corresponding to the MAC CE.
  • the communication device When the communication device meets the trigger condition of the BSR, the communication device triggers a BSR report.
  • the triggering conditions of BSR are as follows, and the communication device will trigger a BSR if one of the following conditions is met:
  • Regular BSR regular BSR
  • the communication device periodically reports to the network equipment: the base station configures a timer (timer) for the communication device through the periodicBSR-Timer field of MAC-MainConfig.
  • timer timer
  • the communication device triggers a BSR to report, and the BSR is called It is periodic BSR (Periodic BSR).
  • Timing retransmission The base station configures a timer (timer) for the communication device through the retxBSR-Timer field of MAC-MainConfig. When the timer expires and any LCH of any LCG in the communication device has cached data, The communication device triggers a BSR, which is called a regular BSR.
  • the communication device When the communication device has uplink resources and the data to be sent is not enough to fill the resources, the extra bits will be used as padding bits.
  • the padding bits are greater than or equal to the size of "BSR MAC CE + corresponding sub-header"
  • the communication device triggers the BSR and uses the padding bits to send the BSR, which is called padding BSR.
  • BSR trigger conditions are only examples, and the BSR trigger conditions in this embodiment of the present application are not limited to the above five examples, and may also include other new BSR trigger conditions that appear with the development of technology.
  • FIG. 4 is a schematic structural diagram of a BSR format provided by an embodiment of the present application.
  • the BSR format shown in FIG. 4 may be called a conventional short BSR format (Short BSR format).
  • the BSR in the regular short BSR format is used to report the amount of buffered data in an LCG.
  • the BSR in the regular short BSR format includes a logical channel group identifier (LCGID) field and a buffer size (Buffer Size, BS) field.
  • LCGID logical channel group identifier
  • Buffer Size, BS buffer size
  • the above-mentioned LCGID field is used to indicate the identity of the LCG reported by the BSR
  • the above-mentioned BS field is used to indicate the amount of buffered data of the LCG reported by the BSR.
  • the BSR format shown in FIG. 4 occupies one byte (octet, Oct), wherein the above-mentioned LCGID field occupies 3 bits, and using 3 bits to represent the LCG identifier can represent an LCG whose identifier is between 0 and 7 Therefore, the BSR in the conventional short BSR format can report the LCG whose identifier is less than or equal to 7.
  • the MAC layer quantifies the actual cache sizes of different LCGs, and the BS field indicates the range of cached data volumes corresponding to the actual cache sizes of the LCGs.
  • the above-mentioned BS field occupies 5 bits, and the value of the BS field indicates the range of the cached data volume of the LCG, and the MAC layer quantizes the actual cache size of the LCG into a range of 32 cached data volumes.
  • the value of the BS field is an index of the buffered data volume range of the LCG. It is used to indirectly indicate the cached data range of the LCG.
  • Table 1 shows the mapping relationship between the index and the cached data volume range of the LCG. As shown in Table 1, the BS value (BS value) indicates the range of the cached data volume in bytes, and the index (Index) is used to indirectly indicate the range of the cached data volume.
  • An index corresponds to a cached data volume range, and the index indicates the corresponding BS The value of the field. For example, assume that the cached data volume of the LCG is 100 bytes, the buffered data volume range is 74 ⁇ BS ⁇ 102, the corresponding index is 8, and the corresponding BS field value is "01000".
  • the foregoing table 1 may be specified by a protocol, or may be configured by a network device.
  • the BSR shown in Figure 4 can also be referred to as the conventional short truncated BSR format (Short Truncated BSR format), the BSR of the conventional short truncated BSR format is used to report the cached data volume of one LCG in the LCG with cached data, and the LCG can be The amount of cached data of the LCG with the highest priority among the LCGs with cached data.
  • the priority of an LCG is determined according to the priorities of the LCHs it contains, and the priority of the LCH with the highest priority among the LCHs contained in each LCG is taken as the priority of its LCG.
  • the communication device uses the BSR in the conventional short truncated BSR format to report the highest priority among the LCGs with the buffered data amount The amount of cached data in the LCG.
  • FIG. 5 is a schematic structural diagram of another BSR format provided by the embodiment of the present application.
  • the BSR format shown in FIG. 5 can be recorded as a conventional long BSR format (Long BSR format).
  • the BSR in the regular long BSR format is used to report the buffered data volume of one or more LCGs.
  • a BSR in conventional long BSR format includes a bitmap and one or more BS fields. Each bit in the above bitmap is used to indicate whether an LCG has cached data, or whether a BS field corresponding to an LCG exists. Each of the above one or more BS fields is used to indicate the amount of buffered data of one LCG of the above one or more LCGs.
  • the number of BS fields included in the BSR of the conventional long BSR format is the number of LCGs reported by the BSR, that is, m in FIG. 5 is the number of LCGs reported by the BSR.
  • each bit in the bitmap is used to indicate whether the BS field corresponding to the LCG exists.
  • the bitmap may include multiple LCGi fields, and the LCGi field is used to indicate whether the BS field corresponding to the i-th LCG exists.
  • the number of BS fields is equal to the number of LCGs with buffered data, and the LCGi field can also indicate whether the i-th LCG has buffered data.
  • the value of the LCGi field is 1, it means that the BS field corresponding to the i-th LCG exists in the BSR, that is, the i-th LCG has cached data; when the value of the LCGi field is 0, it means that the BS field corresponding to the i-th LCG in the BSR exists The BS field does not exist, that is, the i-th LCG has no cached data. It should be understood that the value of the LCGi field in the bitmap is 1 or 0 is just an example, and should not constitute a limitation to this application.
  • the value of the LCGi field can be 2, 3 or 4, etc., as long as there is a cache in the i-th LCG
  • the value of the LCGi field is different, so that the network device can determine whether the corresponding i-th LCG has cached data through the value of the LCGi field in the bitmap.
  • the arrangement order of the above one or more BS fields may be arranged according to the priority of the corresponding LCG, that is, the BS field corresponding to the LCG with higher priority is arranged before the BS field corresponding to the LCG with lower priority.
  • the BSR format shown in FIG. 5 can also be called a conventional long truncated BSR format (Long Truncated BSR format).
  • a BSR in the conventional long truncated BSR format each bit in the bitmap is used to indicate whether the corresponding LCG has cached data.
  • the truncated BSR in the conventional long BSR format is used to report the cached data volume of all LCGs with cached data, and not every LCG with cached data is reported, that is, not every LCG with cached data has a corresponding BS field, so in the BSR of the conventional long truncated BSR format, the LCGi field is used to indicate whether the i-th LCG has cached data.
  • the value of the LCGi field When the value of the LCGi field is 1, it means that the i-th LCG has cached data; when the value of the LCGi field is 0, it means that the i-th LCG has no cached data.
  • the value of the LCGi field in the bitmap is 1 or 0 is just an example, and should not constitute a limitation to this application.
  • the value of the LCGi field can be 2, 3 or 4, etc., as long as there is a cache in the i-th LCG
  • the value of the LCGi field is different, so that the network device can determine whether the corresponding i-th LCG has cached data through the value of the LCGi field in the bitmap.
  • the truncated BSR in the conventional long BSR format reports the amount of buffered data in the LCGs with higher priority among the LCGs with buffered data.
  • the order of the BS fields in the truncated BSR of the conventional long BSR format can be arranged according to the priority of the LCG corresponding to the BS field, that is, the BS field corresponding to the LCG with a higher priority is arranged in the BS field corresponding to the LCG with a lower priority in front of.
  • the above bitmap occupies one byte, including 8 bits, and each bit in the 8 bits is used to indicate whether each LCG in the 8 LCGs has cached data, or to indicate whether each of the 8 LCGs has cached data.
  • the BS field for each LCG exists.
  • Each of the above-mentioned one or more BS fields occupies one byte, and the value of the BS field is an index of the cached data volume range of the LCG, which is used to indirectly indicate the cached data volume range of the LCG.
  • Table 2 shows the mapping relationship between the index and the cached data range of the LCG.
  • the BS value indicates the range of cached data in bytes
  • the index is used to indirectly indicate the range of cached data.
  • An index corresponds to a range of cached data, and the index indicates the corresponding BS The value of the field.
  • the LCID field is extended to 16 bits in R16, and the number of LCGs is extended to 256 in R17.
  • FIG. 6 is a schematic structural diagram of another BSR format provided by the embodiment of the present application.
  • the BSR format shown in Figure 6 can be called the Extended Short BSR format (Extended Short BSR format).
  • the BSR in the extended short BSR format is used to report the buffered data volume of an LCG.
  • the BSR in the extended short BSR format includes an LCGID field and a BS field.
  • the above-mentioned LCGID field is used to indicate the identity of the LCG
  • the above-mentioned BS field is used to indicate the amount of cached data of the LCG.
  • the number of bits occupied by the LCGID field in the BSR in the extended short BSR format is greater than the number of bits occupied by the LCGID field in the BSR in the conventional short BSR format shown in FIG. 4 .
  • the BSR in the extended short BSR format occupies two bytes, and the LCGID field occupies one byte, using 8 bits to indicate the identity of the LCG, which can indicate the identity of the LCG whose identity is between 0 and 255, so the extended The BSR in the short BSR format can report the buffered data volume of the LCG whose identifier is less than 256.
  • the above-mentioned BS field occupies one byte, and the value of the BS field indicates the buffered data volume range of the reported LCG, and the mapping relationship between the buffered data volume range of the LCG and the value of the BS field is shown in Table 2.
  • the BSR shown in Figure 6 can also be called the Extended Short Truncated BSR format (Extended Short Truncated BSR format).
  • the BSR in the extended short truncated BSR format is used to report the cached data volume of one of the LCGs with cached data.
  • the LCG can It is the amount of cached data of the LCG with the highest priority among the LCGs with cached data.
  • the communication device uses the BSR in the extended short truncated BSR format to report the highest priority among the LCGs with the buffered data amount The amount of cached data in the LCG.
  • FIG. 7 is a schematic structural diagram of another BSR format provided by the embodiment of the present application.
  • the BSR format shown in Figure 7 can be called the Extended Long BSR format (Extended Long BSR format).
  • the BSR in the extended long BSR format is used to report the buffered data volume of one or more LCGs.
  • the BSR includes a bitmap and one or more BS field. Each bit in the above bitmap is used to indicate whether an LCG has cached data, or to indicate whether the BA field corresponding to an LCG exists, and each BS field in the above one or more BS fields is used to indicate the above one or the cached data volume of each LCG in multiple LCGs.
  • the number of BS fields included in the BSR of the extended long BSR format is the number of LCGs reported by the BSR, that is, m in Figure 7 is the number of LCGs reported by the BSR.
  • each bit in the bitmap is used to indicate whether the BS field corresponding to the LCG exists.
  • the bitmap may include multiple LCGi fields, and the LCGi is used to indicate whether the BS field corresponding to the i-th LCG exists.
  • the number of BS fields is equal to the number of LCGs with cached data, and the LCGi field can also indicate whether the i-th LCG has cached data.
  • the value of the LCGi field is 1, it means that the BS field corresponding to the i-th LCG exists in the BSR, that is, the i-th LCG has cached data; when the value of the LCGi field is 0, it means that the BS field corresponding to the i-th LCG in the BSR exists The BS field does not exist, that is, the i-th LCG has no cached data. It should be understood that the value of the LCGi field in the bitmap is 1 or 0 is just an example, and should not constitute a limitation to this application.
  • the value of the LCGi field can be 2, 3 or 4, etc., as long as there is a cache in the i-th LCG
  • the value of the LCGi field is different, so that the network device can determine whether the corresponding i-th LCG has cached data through the value of the LCGi field in the bitmap.
  • the arrangement order of the above one or more BS fields may be arranged according to the identification order of the corresponding LCG, or may be arranged according to the priority of the corresponding LCG, that is, the BS field corresponding to the LCG with a higher priority is arranged in the order with a lower priority.
  • the lower LCG corresponds to the front of the BS field.
  • the priority of an LCG is determined according to the priorities of the LCHs it contains, and the priority of the LCH with the highest priority among the LCHs contained in each LCG is taken as the priority of its LCG.
  • the BSR format shown in FIG. 7 can also be called an extended long truncated BSR format (Extended Long Truncated BSR format), and each bit in the bitmap in the BSR of the extended long truncated BSR format is used to indicate whether the corresponding LCG has cached data.
  • the BSR in the extended long truncated BSR format is used to report the cached data volume of all LCGs with cached data, not every LCG with cached data is reported, that is, not every LCG with cached data has a corresponding BS field, so in the truncated BSR of the extended long BSR format, the LCGi field is used to indicate whether the i-th LCG has cached data.
  • the value of the LCGi field When the value of the LCGi field is 1, it means that the i-th LCG has cached data; when the value of the LCGi field is 0, it means that the i-th LCG has no cached data.
  • the value of the LCGi field in the bitmap is 1 or 0 is just an example, and should not constitute a limitation to this application.
  • the value of the LCGi field can be 2, 3 or 4, etc., as long as there is a cache in the i-th LCG
  • the value of the LCGi field is different, so that the network device can determine whether the corresponding i-th LCG has cached data through the value of the LCGi field in the bitmap.
  • the BSR in the extended long-truncated BSR format reports the amount of buffered data in the LCG with higher priority among the LCGs with buffered data.
  • the order of the BS fields in the BSR of the extended long-truncated BSR format can be arranged according to the priority of the LCG corresponding to the BS field, that is, the BS field corresponding to the LCG with a higher priority is arranged in the BS field corresponding to the LCG with a lower priority in front of.
  • the number of bits in the bitmap in the BSR in the BSR format shown in FIG. 7 is greater than the number of bits in the bitmap in the BSR in the BSR format shown in FIG. 5 .
  • the bitmap in the BSR of the extended long BSR format shown in FIG. 7 includes 256 bits, and each bit in the 256 bits is used to indicate whether each LCG in the 256 LCGs has cached data, or It is used to indicate whether the BS field corresponding to each LCG in the 256 LCGs exists.
  • Each of the above one or more BS fields occupies one byte and is used to indicate the cached data volume range of an LCG, where the mapping relationship between the LCG cached data volume range and the value of the BS field is shown in Table 2.
  • bitmap To report a BSR using the BSR format shown in Figure 7, a bitmap (bitmap) needs to be reported each time to indicate whether the corresponding LCG has cached data, or to indicate whether the BS field corresponding to the LCG exists.
  • bitmap When the number of LCGs to be reported is small, if the number of LCGs to be reported is less than the number of bytes occupied by the bitmap, reporting the BSR using the BSR format shown in FIG. 7 will cause waste of data.
  • the embodiment of the present application provides a medium BSR format (Extended Long BSR format*). As shown in Fig.
  • the BSR in the medium BSR format is used to report the buffered data volume of multiple LCGs
  • the BSR in the medium BSR format includes multiple LCGID fields and multiple BS fields.
  • Each of the above multiple LCGID fields is used to indicate an identifier of an LCG
  • each of the above multiple BS fields is used to indicate the amount of buffered data of one LCG.
  • the above multiple LCGID fields are in one-to-one correspondence with the above multiple BS fields. Any LCGID field among the above-mentioned multiple LCG fields uniquely indicates an identifier of an LCG, and its corresponding BS field uniquely indicates the amount of buffered data of the LCG.
  • any LCGID field among the above multiple LCGID fields occupies one byte and is used to indicate an LCG identifier. Therefore, a BSR in the medium BSR format can report the buffered data volume of LCGs whose identifiers are between 0 and 255.
  • Any BS field among the above-mentioned multiple BS fields occupies one byte, and is used to indicate the cached data volume range of an LCG, and the mapping relationship between the LCG cached data volume range and the value of the BS field is shown in Table 2.
  • the above-mentioned BSR format can have multiple LCGID fields and multiple BS fields in turn, wherein, the arrangement order of the above-mentioned multiple LCGID fields can be based on the priority arrangement of the LCG indicated by the LCGID field, that is, LCG ID 1 corresponds to The priority of an LCG is higher than that of other LCGs.
  • the arrangement order of the above-mentioned multiple BS fields corresponds to the arrangement order of the above-mentioned LCGID fields, that is, the i-th BS field indicates the buffered data volume of the LCG indicated by the i-th LCGID field. As shown in FIG.
  • the above BSR format may sequentially include an LCGID1 field, a BS1 field, an LCGID2 field and a BS2 field.
  • the LCGID1 field is used to indicate the identity of the first LCG
  • the BS1 field is used to indicate the buffer data amount of the first LCG
  • the LCGID2 is used to indicate the identity of the second LCG
  • the BS2 field is used to identify the buffer data amount of the second LCG.
  • the arrangement order of the LCGID field and the BS field corresponding to each LCG in FIG. 8b may be arranged according to the priority of the LCG, that is, the priority of the first LCG is higher than the priority of the second LCG.
  • the difference between the BSR format shown in FIG. 8a and the BSR format shown in FIG. 8b lies in the arrangement order of the LCGID field and the BS field.
  • the BSR format shown in FIG. 8a and FIG. 8b may also be called a medium truncated BSR format, and the BSR in the medium truncated BSR format is used to report the cached data volume of a part of the LCG with cached data.
  • the partial LCGs reported by the BSR in the medium-truncated BSR format may be the partial LCGs with higher priority among the LCGs with cached data.
  • the embodiment of the present application provides a method for reporting a BSR, which can effectively use the BSR format shown in FIG. 4 to FIG. 8 b to report a BSR reasonably.
  • the BSR format shown in FIG. 4 to FIG. 8b is only an example, and the BSR format in the embodiment of the present application is not limited to the BSR format shown in FIG. 4 to FIG. 8b.
  • FIG. 9 is a schematic flowchart of a communication method provided by an embodiment of the present application. It should be understood that FIG. 9 shows steps or operations of the communication method, but these steps or operations are only examples, and other operations or variations of the operations in FIG. 9 may also be performed in the embodiment of the present application.
  • the communication method shown in FIG. 9 is applied to the interaction between the communication device and the network equipment, and the communication method shown in FIG. 9 may be executed by the communication device.
  • the communication device When there is cached data to be uploaded in the communication device, perform the steps shown in Figure 9 to generate a BSR, send the BSR to the network device, and report the buffered data volume of the communication device to the network device, so that the network device can use the buffered data volume of the communication device as The communication device allocates uplink transmission resources.
  • the communication device is a device equipped with a processor that can be used to instruct a computer to execute instructions.
  • the communication device may be a terminal device or a network node (such as an IAB node).
  • the communication method shown in FIG. 9 can be used in the IAB network.
  • the terminal device executes the communication method shown in FIG. 9 , it can send a BSR to the network device through the Uu link.
  • the IAB node executes the communication method shown in FIG. 9 , it is executed by the MT part of the IAB node, and sends a BSR to the parent node of the IAB node through the BH link.
  • the communication method may include but not limited to the following steps:
  • the specific numerical value of the foregoing first numerical value may be set by the network device, and the first numerical value may specifically be 7.
  • the communication device may determine the target BSR format used to report the BSR from multiple BSR formats according to a comparison result between the first identifier and the first value.
  • the communication device can use the first identifier and the first value
  • the comparison results determine the target BSR format from the above-mentioned various BSR formats.
  • the number of reported LCGs is the same, the number of bits occupied by the BSR of the above two BSR formats is different.
  • the foregoing first value may be equal to a maximum value of LCG identifiers of LCGs that can be reported by one of the foregoing multiple BSR formats.
  • the communication device determines the above-mentioned one BSR format as the target BSR format.
  • the communication device may execute step 901 when a BSR trigger condition is satisfied, and for the BSR trigger condition, reference may be made to the relevant description of the aforementioned FIG. 3 .
  • the BSR triggering condition includes a buffer area. It can be understood that the triggering condition shown here is only an example.
  • the terminal device may also trigger execution of step 901 according to other triggering conditions.
  • the communication device determines the value of each field in the above-mentioned target BSR format according to the identifier of the LCG with buffered data and the amount of buffered data, and generates the BSR.
  • the target BSR format is the conventional long BSR format as shown in Figure 5
  • the number of LCGs with cached data is 3, respectively LCG0, LCG2, and LCG5 have cached data
  • the generated conventional long BSR format Bit 0, bit 2, and bit 5 in the bitmap in the BSR are 1, and other bits in the bitmap are 0.
  • the above-mentioned BSR includes three BS fields, and the values of the three BS fields correspond to indexes of buffered data volume ranges of LCG0, LCG2, and LCG5, respectively.
  • the BSR in the target BSR format generated by the communication device is included in the MAC PDU.
  • one MAC PDU may include multiple BSRs.
  • the communication device When the communication device generates a MAC PDU, if the first identifier is greater than the first value, it means that there is at least one LCG identifier greater than the first value among the LCG identifiers of the LCGs with cached data, and the communication device can use two BSR formats to report respectively Part of the LCGs with cached data whose LCG identifier is less than or equal to the first value and the part of the LCG with cached data whose LCG identifier is greater than the first value.
  • the communication device may use the BSR in the first format to report the amount of buffered data in the LCG with the LCG identifier greater than the first value in the LCG with buffered data, and use the BSR in the second format to report the amount of buffered data in the LCG with buffered data.
  • the LCG identifier is less than or equal to the first numerical value of the cached data volume of the LCG.
  • the maximum value of LCG identifiers of LCGs that can be reported by the BSR in the first format is greater than the maximum value of the LCG identifiers of LCGs that can be reported by the BSR in the second format.
  • the foregoing first value may be equal to the maximum value of LCG identifiers of LCGs that can be reported by the BSR in the second format.
  • the method shown in Figure 9 further includes:
  • the communication device sends the BSR in the target BSR format to the network device through the MAC PDU, and reports the buffered data amount of the communication device to the network device, so that the network device determines the amount of uplink transmission resources allocated for the communication device according to the buffered data amount of the communication device.
  • the communication device can determine an appropriate BSR format to report the BSR according to the comparison result between the first identifier and the first value, and can reasonably use uplink transmission resources to report the BSR, so as to realize fine-grained scheduling of network resources.
  • step 901 shown in FIG. 9 also provides the following implementation methods:
  • the aforementioned determination of the target BSR format based on the comparison result of the first identifier and the first value includes:
  • the first format is determined as the target BSR format, and the BSR in the first format is used to report the buffered data volume of the LCG whose LCG identifier is within the first identifier threshold;
  • the second format is determined as the target BSR format, and the BSR in the second format is used to report the buffered data volume of the LCG whose LCG identifier is within the second identifier threshold.
  • the above-mentioned first identification threshold is greater than the above-mentioned second identification threshold.
  • the foregoing multiple BSR formats may include a first format and a second format, and the BSR in the first format and the BSR in the second format may report different identification ranges of LCG identifiers of LCGs.
  • the communication device may determine the identity range to which the LCG identity of the LCG that needs to be reported belongs according to the first identity, and determine the target BSR format corresponding to the identity range.
  • the above-mentioned first value may be equal to the maximum value of the LCG identifier of the LCG that the BSR in the second format can report, that is, the above-mentioned first value may be equal to the above-mentioned second identifier threshold, and the BSR in the second format cannot report the LCG identifier greater than LCG of the first value. If the first identifier is less than or equal to the first value, determine the second format as the target BSR format. If the first identifier is greater than the first value, determine the first format as the target BSR format.
  • the number of bits occupied by the BSR in the first format is greater than the number of bits occupied by the BSR in the second format.
  • the BSR in the first format includes the first LCGID field or the first bit map, the first LCG field is used to indicate the identity of the reported LCG, and each bit in the first bit map is used to indicate at least one LCG in each Whether there is buffer data in one LCG, or whether the buffer size BS field corresponding to each LCG in at least one LCG exists.
  • the BSR in the second format includes a second LCGID field or a second bitmap
  • the second LCG field is used to indicate the identity of the reported LCG
  • each bit in the second bitmap is used to indicate that each of the at least one LCG Whether there is buffer data in one LCG, or whether the buffer size BS field corresponding to each LCG in at least one LCG exists.
  • the number of bits in the first LCGID field is greater than that in the second LCGID field
  • the number of bits in the first bitmap is greater than that in the second bitmap.
  • the BSR in the second format cannot report the buffered data volume of the LCG whose LCG identifier is greater than the second identifier threshold, so the second format is used.
  • the BSR in one format reports the amount of cached data of the above-mentioned LCG with cached data.
  • the BSR in the second format can be used to report the cached data volume of the LCGs with cached data.
  • the communication device may also use the BSR in the first format to report the buffered data amount of the LCG with buffered data.
  • the number of bits occupied by the BSR in the first format is greater than the number of bits occupied by the BSR in the second format.
  • the above-mentioned first identification threshold may be 255, and the BSR in the first format may report LCGs whose LCG identifications are between 0 and 255.
  • the above-mentioned second identification threshold may be 7, and the BSR in the second format may report LCGs whose LCG identifications are between 0 and 7.
  • the first format may include the extended short BSR format shown in FIG. 6, the extended long BSR format shown in FIG. 7, and the medium BSR format shown in FIG. 8a or 8b.
  • the second format may include the conventional short BSR format shown in FIG. 4 and the conventional long BSR format shown in FIG. 5 .
  • the number of bits of the BSR in the first format is greater than that of the BSR in the second format, and the BSR in the second format cannot report an LCG whose LCG identifier is greater than the first value. If the first identifier is greater than the first numerical value, determine the first format as the target BSR format; if the first identifier is less than or equal to the first numerical value, determine the second format as the target BSR format. While ensuring the integrity of the reported LCG with cached data, the number of bits required for reporting the BSR is saved, and resource utilization efficiency is improved.
  • the communication device may also determine the specific format of the first format or the second format according to the number of LCGs with cached data.
  • the communication device determines the specific format of the first format according to the number of LCGs with cached data, which may include the following steps:
  • the above-mentioned first format or second format is a short BSR format
  • the above-mentioned first format or second format is a medium BSR format
  • the first format or the long BSR format of the second format In the case that the number of LCGs with cached data is greater than or equal to the second value, the first format or the long BSR format of the second format.
  • the BSR in the short BSR format is used to report the buffered data amount of one LCG
  • the BSR in the short BSR format includes the LCG identifier of the first LCG and indication information for indicating the buffered data amount of the first LCG.
  • the first LCG is an LCG with cached data.
  • the above short BSR format When the second format is the short BSR format, the BSR in the second format is used to report the buffered data volume of an LCG whose LCG identifier is within the second identification threshold.
  • the first format is the short BSR format
  • the BSR in the first format is used to report the buffered data volume of an LCG whose LCG identifier is within the first identifier threshold.
  • the BSR in the first format includes a first LCGID field, and the first LCGID field is used to indicate the identity of the above-mentioned one LCG.
  • the first format when the first format is the short BSR format, the first format may be the extended short BSR format as shown in FIG. 6 .
  • the BSR in the second format includes a second LCGID field, and the second LCGID field is used to indicate the identity of the above-mentioned one LCG.
  • both the first format and the second format are short BSR formats
  • the number of bits of the BSR in the first format is greater than the number of bits in the BSR in the second format.
  • the number of bits of the first LCGID field is greater than the number of bits of the second LCGID.
  • the second format when the second format is the short BSR format, the second format may be the normal short BSR format as shown in FIG. 4 .
  • the above-mentioned BSR in the medium BSR format is used to report the buffered data volume of one or more LCGs.
  • the BSR in the medium BSR format includes an LCG identifier of at least one LCG and indication information for indicating the amount of cached data of the at least one LCG.
  • the above at least one LCG is at least one LCG among the LCGs with cached data.
  • the BSR in the first format is used to report the buffered data volume of the LCG whose LCG identifier is within the first identifier threshold.
  • the BSR in the first format includes at least one LCGID field.
  • the first format may be the medium BSR format as shown in FIG.
  • the BSR in the second format is used to report the buffered data volume of the LCG whose LCG identifier is within the second identification threshold, and the BSR in the second format includes at least one LCGID field.
  • the number of bits of any LCGID field in the at least one LCGID field in the BSR in the second format is smaller than the number of bits in any LCG field in the at least one LCGID field in the BSR in the first format.
  • the BSR in the above long BSR format is used to report the buffered data volume of one or more LCGs.
  • the above-mentioned BSR in the long BSR format includes a first bit map, and each bit in the first bit map is used to indicate whether each LCG in the at least one LCG has cached data, or to indicate each LCG in the at least one LCG Whether the corresponding cache size BS field exists.
  • the at least one LCG includes the LCG with cached data.
  • the BSR in the first format is used to report the amount of buffered data of the LCG whose LCG identifier is within the first identification threshold, and the BSR in the first format includes a first bitmap.
  • the first format when the first format is the long BSR format, the first format may be the extended long BSR format as shown in FIG. 7 .
  • the second format is the long BSR format
  • the BSR in the second format is used to report the buffered data volume of the LCG whose LCG identifier is within the second identifier threshold, and the BSR in the second format includes a second bitmap, and the bits of the second bitmap The number is less than the number of bits in the first bitmap above.
  • the second format when the second format is the long BSR format, the second format may be the conventional long BSR format as shown in FIG. 5 .
  • the second value may be determined according to the number of bytes occupied by the first bitmap in the BSR in the long BSR format.
  • the second value may specifically be the number of bytes occupied by the first bitmap in the BSR in the long BSR format.
  • the BSR in the second format is used to report the cached data volume of the LCG whose LCG identification is between 0 and 7, and the above-mentioned second bitmap may occupy one byte.
  • the value of the second value is 1, so there is no situation that the number of LCGs with cached data is less than the second value. Therefore, when the second identification threshold is 7, the second format may be the short BSR format or the long BSR format.
  • the second format is the short BSR format; when the number of LCGs with buffered data is greater than 1, the second format is the long BSR format.
  • the determination of the target BSR format is introduced.
  • the determination of the target BSR format in different situations is as follows:
  • the extended short BSR format is determined as the target BSR format.
  • the medium BSR format is determined as the target BSR format.
  • the extended long BSR format is determined as the target BSR format.
  • the conventional long BSR format is determined as the target BSR format.
  • the communication device may also determine the specific format of the first format according to the number of padding bits.
  • the communication device may determine the target BSR format used for reporting the BSR according to the comparison result between the first identifier and the first value, the number of LCGs with cached data, and the value of the padding bits.
  • the above-mentioned communication device determines the specific format of the first format according to the number of filling bits, which may include the following situations:
  • Case 1 When the first identifier is greater than the first value and the number of LCGs with cached data is greater than or equal to the second value, the communication device determines the specific format of the first format according to the number of filling bits.
  • the communication device determines the size of the BSR in the long BSR format and the size of the MAC subheader of the BSR in the long BSR format.
  • the size of the BSR in the long BSR format is the number of bits occupied when the BSR in the long BSR format reports all LCGs with buffered data.
  • the number of padding bits is compared with the sixth value, which is the size of the BSR in the long BSR format plus the size of the MAC subheader of the BSR in the long BSR format. In the case that the number of padding bits is greater than or equal to the above sixth value, the first format is the long BSR format.
  • the first format is the long truncated BSR format.
  • the fourth value is the number of bits occupied when the number of LCGs reported by the BSR in the medium BSR format is equal to the second value.
  • the above-mentioned first format is a medium truncated BSR format.
  • the third value is determined according to the size of the BSR in the first format and the size of the MAC subheader of the BSR in the first format.
  • the third value may specifically be the number of bits occupied when the BSR in the first format reports the buffered data volume of an LCG plus the number of bits occupied by the MAC subheader in the first format, that is, the third value is the first The minimum number of bits required for a BSR in the format.
  • the first format is a short truncated BSR format.
  • the communication device can only report the buffered data volume of one LCG, so the first format is the short truncated BSR format to inform the network equipment that the communication device has other LCGs besides the LCG reported by the BSR There is cached data.
  • the BSR in short truncated BSR format is used to report the amount of buffered data of the LCG with higher priority among the LCGs with buffered data.
  • the communication device determines the second format as the target BSR format.
  • the number of LCGs with buffered data is greater than 1
  • the first identifier is greater than the first value
  • the filling bits are not enough to report the BSR in the first format
  • use the BSR in the second format to report the LCG identifiers in the LCGs with buffered data less than The amount of cached data in the LCG of the first value.
  • Case 2 When the first identifier is greater than the first value and the number of LCGs with cached data is less than the second value, the communication device determines the specific format of the first format according to the number of filling bits.
  • the communication device determines a size of a BSR in the medium BSR format, and a size of a MAC subheader of the BSR in the medium BSR format.
  • the number of padding bits is compared with the size of the medium BSR format BSR plus the size of the MAC subheader of the medium BSR format BSR. In the case that the number of padding bits is greater than or equal to the size of the BSR in the medium BSR format plus the size of the MAC subheader of the BSR in the medium BSR format, the above-mentioned first format is the medium BSR format.
  • the first format is the medium truncated BSR format.
  • the first format is a short truncated BSR format.
  • the communication device determines the second format as the target BSR format.
  • the communication device determines the size of the BSR in the short BSR format, and the size of the MAC subheader of the BSR in the short BSR format.
  • the first format is the short BSR format.
  • the second format is determined as the target BSR format.
  • the third value is the size of the BSR in the short BSR format plus the size of the MAC subheader of the BSR in the short BSR format.
  • the communication device may also determine the specific format of the first format according to the number of padding bits, so as to ensure that the communication device can use the padding bits to report the generated BSR in the first format.
  • the communication device may also determine the specific format of the second format according to the number of padding bits.
  • the above-mentioned communication device determines the specific format of the second format according to the number of filling bits, which may include the following situations:
  • Case 1 When the first identifier is less than or equal to the first value and the number of LCGs with cached data is greater than or equal to the second value, the communication device determines the specific format of the second format according to the number of filling bits.
  • the communication device determines the number of bits occupied by the BSR in the long BSR format.
  • the second format is the long BSR format.
  • the second format is the long truncated BSR format .
  • the seventh value is the number of bits occupied when the number of LCGs reported by the BSR in the medium BSR format is equal to the above-mentioned second value.
  • the above-mentioned second format is a medium truncated BSR format.
  • the fifth value is determined according to the BSR in the short BSR format and the size of the MAC subheader of the BSR in the short BSR format.
  • the fifth value may specifically be the size of the BSR in the short BSR format plus the size of the MAC subheader of the BSR in the short BSR format, that is, the fifth value is the number of bits required to report the BSR in the short BSR format.
  • the second format is a short truncated BSR format.
  • the communication device can only report the buffered data volume of one LCG in the short truncated BSR format.
  • the BSR in the short truncated BSR format is used to report the amount of cached data of an LCG with a higher priority among the LCGs with cached data.
  • Case 2 When the first identifier is less than or equal to the first value and the number of LCGs with cached data is less than the second value, the communication device determines the specific format of the second format according to the number of filling bits.
  • the communication device determines a size of a BSR in the medium BSR format, and a size of a MAC subheader of the BSR in the medium BSR format.
  • the number of padding bits is compared with the size of the medium BSR format BSR plus the size of the MAC subheader of the medium BSR format BSR. In the case that the number of padding bits is greater than or equal to the size of the BSR in the medium BSR format plus the size of the MAC subheader of the BSR in the medium BSR format, the above second format is the medium BSR format.
  • the second format is the medium truncated BSR format.
  • the second format is the regular short truncated BSR format.
  • Case three when the first identifier is less than or equal to the first value and the number of LCGs with cached data is 1, the second format is the short BSR format.
  • the communication device may also determine the specific format of the second format according to the number of padding bits, so as to ensure that the communication device can use the padding bits to report the generated BSR in the second format.
  • the above target BSR format is determined.
  • the foregoing third value may be determined according to BSR sizes corresponding to multiple BSR formats usable by the communication device.
  • the third value may specifically be the size of the BSR in one of the above-mentioned multiple BSR formats plus the size of the corresponding MAC subheader, that is, the third value is required for the communication device to report the BSR in the above-mentioned one of the BSR formats minimum number of bits.
  • the communication device may determine the target BSR format used for reporting the BSR from multiple BSR formats according to the comparison result of the first identifier and the first value, and the comparison result of the number of padding bits and the third value.
  • the communication device can determine the target BSR format used for reporting the BSR according to the comparison result of the first identifier and the first value, and the number of padding bits and the bit result of the third value.
  • the above-mentioned comparison result based on the first identifier and the first value, and the comparison result between the number of filling bits and the third value, and determining the above-mentioned target BSR format include the following steps:
  • the second format is determined as the target BSR format; the BSR in the second format is used to report the LCG with buffered data The cached data volume of the LCG whose LCG identifier is less than the above-mentioned first value; or,
  • the aforementioned multiple BSR formats may include a first format and a second format.
  • the foregoing multiple BSR formats may include a first format and a second format, and the BSRs in the first format and the BSRs in the second format may report different LCG identification ranges.
  • the BSR in the first format is used to report the cached data volume of the LCG whose LCG identifier is within the first identifier threshold
  • the BSR in the second format is used to report the buffered data amount of the LCG whose LCG identifier is within the second identifier threshold, wherein The first identification threshold is greater than the second identification threshold.
  • the number of bits occupied by the BSR in the first format is greater than the number of bits occupied by the BSR in the second format.
  • the communication device needs to use padding bits to send BSR, so it needs to determine that the size of the BSR generated according to the target BSR format plus the size of its MAC subheader is less than or equal to the number of padding bits, so as to ensure that the BSR can be sent using padding bits. Therefore, the communication device may determine the target BSR format from the first format and the second format according to the comparison result of the first identifier and the first value, and the comparison result of the number of padding bits and the third value.
  • the above-mentioned first value may be equal to the largest LCG identifier among the LCG identifiers of LCGs that can be reported by the BSR in the above-mentioned second format, that is, the above-mentioned first value may be equal to the above-mentioned second identifier threshold, and the BSR in the second format cannot report the LCG LCGs greater than the first numerical value are identified.
  • the third value is determined according to the size of the BSR in the first format and the size of the MAC subheader of the BSR in the first format.
  • the third value may specifically be the number of bits required when the BSR in the first format reports the buffered data volume of one LCG, that is, the third value is the minimum number of bits required to report the BSR in the first format.
  • the communication device can use the stuffing bits to send the BSR of the first format, so the first format is determined as the target BSR format, using the first format
  • the BSR in one format reports the amount of cached data of some or all of the LCGs with cached data.
  • the communication device determines the second format as the target BSR format, and uses the second format
  • the BSR reports the amount of cached data of LCGs whose identifiers are less than or equal to the first value among the LCGs with cached data.
  • the communication device determines the second format as the target BSR format, and uses the BSR in the second format to report the buffered data volume of some or all of the LCGs with buffered data.
  • the first identifier when the first identifier is greater than the first value and the number of padding bits is greater than or equal to the third value, determine the LCG identifier of the high priority LCG among the LCGs with cached data. In the case that the LCG identifier of the high-priority LCG is less than or equal to the first value, the format that can report a larger number of LCGs among the first format and the second format is determined as the target BSR format.
  • the LCG with cached data when the number of LCGs whose LCG identifier is less than or equal to the first value is greater than the number of LCGs that can be reported by the BSR of the first format, determine the second format as the target format; in the LCG with cached data If the number of LCGs whose LCG identifiers are less than or equal to the first value is less than the number of LCGs that can be reported by the BSR in the first format, determine the first format as the target BSR format.
  • the communication device may determine the specific format of the first format according to the number of padding bits.
  • the above-mentioned first format is a short BSR format; or, when the number of padding bits is greater than the third value and less than the fourth value, the above-mentioned first format is a medium BSR format ; Or, in the case that the number of stuffing bits is greater than the fourth value, the above-mentioned first format is a long BSR format.
  • the BSR in the first format is used to report the buffered data volume of the LCG whose LCG identifier is within the first identifier threshold, and the BSR in the first format includes a first bitmap, and the above-mentioned first bitmap Each bit is used to indicate whether each LCG in the at least one LCG has cached data, or is used to indicate whether the buffer size BS field corresponding to each LCG in the at least one LCG exists.
  • the LCG identification of the at least one LCG is within the first identification threshold.
  • the first format may be the extended long BSR format as shown in FIG. 7 .
  • the above-mentioned long BSR format can also be understood as a long-truncated BSR format.
  • the above-mentioned first format is a long-truncated BSR format.
  • the BSR in the first format is used to report the buffered data volume of an LCG whose LCG identifier is within the first identifier threshold.
  • the BSR in the first format includes a first LCGID field, and the first LCGID field is used to indicate the identity of the above-mentioned one LCG.
  • the first format may be the extended short BSR format as shown in FIG. 6 .
  • the above-mentioned short BSR format can also be understood as a short-truncated BSR format.
  • the padding bits are insufficient to report the buffered data volume of all LCGs with buffered data, the above-mentioned first format is a long-truncated BSR format.
  • the BSR in the first format is used to report the buffered data volume of the LCG whose LCG identifier is within the first identifier threshold.
  • the BSR in the first format includes an LCG identifier of at least one LCG and indication information for indicating the amount of cached data of the at least one LCG.
  • the at least one LCG is at least one LCG among the LCGs with cached data.
  • the first format may be the medium BSR format as shown in FIG. 8a or FIG. 8b.
  • the above-mentioned medium BSR format can also be understood as a medium-truncated BSR format.
  • the above-mentioned first format is a medium-truncated BSR format.
  • the above fourth value may be the number of LCGs reported by the BSR in the long BSR format and the BSR in the medium BSR format and the number of occupied bits, the number of bits occupied by the BSR in the long BSR format or the BSR in the medium BSR format, that is, when the long
  • the BSR in the long BSR format and the BSR in the medium BSR format can report the same number of LCGs.
  • the number of LCGs that can be reported by the BSR in the medium BSR format is greater than the number of LCGs that can be reported in the long BSR format.
  • the number of bits occupied by the BSR in the medium BSR format is the same as the number of bits occupied by the BSR in the long BSR format and both are greater than the fourth value, the number of LCGs that can be reported by the BSR in the medium BSR format is smaller than the number of LCGs that can be reported by the BSR in the long BSR format quantity.
  • the number of padding bits is greater than or equal to the third value and less than the fourth value
  • the number of LCGs that can be reported by the BSR in the medium BSR format is greater than the number of LCGs that can be reported by the BSR in the long BSR format
  • the communication device uses the medium BSR format Determined as the target BSR format.
  • the number of padding bits is greater than or equal to the fourth value
  • the number of LCGs that can be reported by the BSR in the long BSR format is greater than the number of LCGs that can be reported by the BSR in the medium BSR format
  • the communication device determines the long BSR format as the target BSR format .
  • the specific format of the first format is determined according to the number of padding bits, and a reasonable BSR format is selected for reporting, so that more buffered data volume of the LCG can be reported.
  • the communication device may determine the specific format of the first format according to the number of LCGs with cached data.
  • the communication device determines the specific format of the first format according to the number of LCGs with cached data, which may include the following situations:
  • Case 1 When the first identifier is greater than the first value and the number of filling bits is equal to the third value, the communication device may determine the specific format of the first format according to the number of LCGs with cached data.
  • the above-mentioned first format is the short BSR format.
  • the first format is the short truncated BSR format.
  • Case 2 In the case where the first identifier is greater than the first value and the number of filling bits is greater than the third value and less than or equal to the fourth value, the communication device may determine the specific format of the above-mentioned first format according to the number of LCGs with cached data .
  • the above-mentioned first format is a medium BSR format; when the number of LCGs with cached data is less than the eighth value, the above-mentioned first format is medium truncated BSR format.
  • the eighth value above is the number of LCGs that can be reported by the BSR in the medium BSR format on the premise that the number of bits occupied by the BSR in the medium BSR format is less than or equal to the above padding bits.
  • the above-mentioned first format may be a short BSR format.
  • Case 3 When the first identifier is greater than the first value and the number of padding bits is greater than or equal to the fourth value, the communication device may further determine the specific format of the first format according to the number of LCGs with cached data.
  • the above-mentioned first format is the long BSR format; when the number of LCGs with cached data is greater than the ninth value, the above-mentioned first format is long truncated BSR format.
  • the above ninth value is the number of LCGs that can be reported by the BSR in the long BSR format under the premise that the number of bits occupied by the BSR in the long BSR format is less than or equal to the padding bits.
  • the first format when the number of LCGs with cached data is 1, the first format may be a short BSR format. In a case where the number of LCGs with cached data is greater than 1 and less than the second value, the first format is a medium BSR format. In the case where the amount of cached data is greater than the second value, the first format is the long BSR format or the long truncated BSR format. It is in the long truncated BSR format, and the BSR in the long truncated BSR format is used to report the cached data volume of some LCGs in the LCGs with cached data. The part of the LCG reported by the BSR in the long-truncated BSR format is the part of the LCG with higher priority among the above-mentioned LCGs with cached data.
  • the communication device may determine the specific format of the second format according to the number of padding bits.
  • the second format is the short BSR format; when the number of padding bits is greater than the fifth value, the second format is the long BSR format.
  • the BSR in the second format is used to report the buffered data volume of an LCG whose LCG identifier is within the second identification threshold.
  • the BSR in the second format includes a second LCGID field, and the second LCGID field is used to indicate the identity of the above-mentioned one LCG.
  • both the first format and the second format are short BSR formats
  • the number of bits of the BSR in the first format is greater than the number of bits in the BSR in the second format.
  • the number of bits of the first LCGID field is greater than the number of bits of the second LCGID.
  • the second format may be the normal short BSR format as shown in FIG. 4 .
  • the above-mentioned short BSR format can also be understood as a short-truncated BSR format.
  • the above-mentioned second format is a short-truncated BSR format.
  • the BSR in the second format is used to report the buffered data volume of the LCG whose LCG identifier is within the second identifier threshold, and the BSR in the second format includes a second bitmap, and the above-mentioned second bitmap Each bit is used to indicate whether each LCG in the at least one LCG has cached data, or is used to indicate whether the buffer size BS field corresponding to each LCG in the at least one LCG exists.
  • the LCG identification of the at least one LCG is within the second identification threshold.
  • the number of bits of the second bitmap is smaller than the number of bits of the first bitmap.
  • the second format when the second format is the long BSR format, the second format may be the conventional long BSR format as shown in FIG. 5 .
  • the above-mentioned long BSR format can also be understood as a long-truncated BSR format.
  • the above-mentioned second format is a long-truncated BSR format.
  • the communication device may determine the specific format of the second format according to the number of LCGs with cached data.
  • the communication device determines the specific format of the second format according to the number of LCGs with cached data, which may include the following situations:
  • Case 1 When the first identifier is less than or equal to the first value and the number of padding bits is less than the fifth value, the communication device may determine the specific format of the second format according to the amount of buffered data.
  • the second format is the short BSR format; when the number of LCGs with buffered data is greater than 1, the second format is the short truncated BSR format.
  • Case 2 When the first identifier is less than or equal to the first value and the number of padding bits is greater than or equal to the fifth value, the communication device may determine the specific format of the second format according to the number of LCGs with cached data.
  • the above-mentioned second format is the long BSR format.
  • the above-mentioned second format is the long truncated BSR format.
  • the tenth value is the number of LCGs that can be reported by the BSR in the long BSR format under the premise that the number of bits occupied by the BSR in the long BSR format is less than or equal to the padding bits.
  • the second format is the short BSR format.
  • the target BSR format is determined according to the comparison result between the first identifier and the first value, and the comparison result between the number of padding bits and the third value, so as to select an appropriate BSR format to report the cached
  • the amount of buffered data in the LCG of the data can be reported to the BSR by rational use of uplink resources, and the refined scheduling of network resources can be realized.
  • the BSRs of the two BSR formats have different maximum values of LCG identifiers of LCGs that can be reported, and the number of LCGs that can be reported is also different.
  • the communication device may determine the target BSR format according to the comparison result of the first identifier and the first value and the number of padding bits.
  • the above-mentioned multiple BSR formats include the first BSR format, the maximum value of LCG identifiers of LCGs that can be reported in this first BSR format is 7, and the number of LCGs that can be reported is 8. If there is an LCG with cached data The number is 3, and the largest LCG ID among the LCG IDs of the LCGs with cached data is 5, and the communication device determines the above-mentioned first BSR format as the target BSR format.
  • the determination of the target BSR format based on the comparison result of the first identifier and the first value, and the number of LCGs with cached data includes the following steps:
  • the first identifier is greater than the first value and the number of LCGs with cached data is greater than or equal to the second value, determine the first long BSR format as the target BSR format; or,
  • the first identifier is less than or equal to the first value and the number of LCGs with cached data is greater than 1, determine the second long BSR format as the target BSR format.
  • the aforementioned multiple BSR formats may include a first long BSR format, a first short BSR format, a medium BSR format, a second long BSR format, and a second short BSR format.
  • the BSR in the first long BSR format is used to report the buffered data volume of the LCG whose LCG identifier is within the first identification threshold, and the BSR in the first long BSR format includes a first bitmap, and each bit in the first bitmap It is used to indicate whether each LCG of at least one LCG has cached data, or is used to indicate whether the buffer size BS field corresponding to each LCG of at least one LCG exists, and the LCG identification of the at least one LCG is within the first identification threshold Inside.
  • the above-mentioned first long BSR format may be the extended long BSR format as shown in FIG. 7 .
  • the BSR in the second long BSR format is used to report the buffered data volume of the LCG whose LCG identifier is within the second identification threshold
  • the BSR in the second long BSR format includes a second bit map, and each bit in the second bit map above It is used to indicate whether each LCG in at least one LCG has cached data, or is used to indicate whether the buffer size BS field corresponding to each LCG in at least one LCG exists, and the LCG identification of the at least one LCG is within the second identification threshold Inside.
  • the first identification threshold is greater than the second identification threshold, and the number of bits in the first bitmap is greater than the number of bits in the second bitmap.
  • the above-mentioned second long BSR format may be a conventional long BSR format as shown in FIG. 5 .
  • the BSR in the first short BSR format is used to report the buffered data volume of an LCG whose LCG identifier is within the first identifier threshold.
  • the BSR in the first short BSR format includes a first LCGID field, and the first LCGID field is used to indicate the identity of the above-mentioned one LCG.
  • the above-mentioned first short BSR format may be the extended short BSR format as shown in FIG. 6 .
  • the BSR in the second short BSR format is used to report the buffered data volume of an LCG whose LCG identifier is within the second identifier threshold.
  • the BSR in the second short BSR format includes a second LCGID field, and the second LCGID field is used to indicate the identity of the above-mentioned one LCG.
  • the number of bits of the first LCGID field is greater than the number of bits of the second LCGID.
  • the above-mentioned second short BSR format may be a conventional short BSR format as shown in FIG. 4 .
  • the BSR in the medium BSR format is used to report the buffered data volume of the LCG whose LCG identifier is within the first identifier threshold.
  • the BSR in the medium BSR format includes an LCG identifier of at least one LCG and indication information for indicating the amount of cached data of the at least one LCG.
  • the at least one LCG is at least one LCG among the LCGs with cached data.
  • the above medium BSR format may be the medium BSR format as shown in Fig. 8a or Fig. 8b.
  • the above-mentioned first value may be equal to the above-mentioned second identification threshold, and in the case that the first identification is less than or equal to the first value, the communication device may use the BSR in the second long BSR format or the BSR in the second short BSR format to report the cached data.
  • the foregoing second value may be determined according to the number of bytes occupied by the first bitmap in the foregoing first long BSR format.
  • the second value may specifically be the number of bytes occupied by the first bitmap in the long BSR format.
  • the communication device uses the BSR in the above medium BSR format to report the buffered data volume of the LCG with buffered data, which can save resources and make reasonable use of resources.
  • the communication device may also determine the target BSR format according to the number of padding bits.
  • the communication device determines the target BSR format according to the number of filling bits, which may include the following situations:
  • Case 1 When the first identifier is greater than the first value and the number of LCGs with buffered data is 1, the communication device may determine the target BSR format according to the number of padding bits.
  • the first short BSR format is determined as the target BSR format.
  • the third value is determined according to the size of the BSR in the first short BSR format and the size of the MAC subheader of the BSR in the first short BSR format.
  • the third value may specifically be the number of bits occupied by the first short BSR format.
  • Case 2 When the first identifier is greater than the first value and the number of LCGs with cached data is greater than 1 and less than the second value, the communication device may determine the target BSR format according to the number of filling bits.
  • the LCG determines whether the LCG with cached data has an LCG whose LCG identifier is less than or equal to the first value, if any of the LCGs with buffered data has an LCG whose identifier is less than or equal to the first value
  • the LCG determines the second short truncated BSR format as the target BSR format, and the BSR in the second truncated short BSR format is used to report the buffered data volume of an LCG whose LCG identifier is less than or equal to the first value among the LCGs with buffered data.
  • the first short truncated BSR format is determined as the target BSR format, and the BSR of the first short truncated BSR format is used to report an LCG with a higher priority among the LCGs with cached data The amount of cached data.
  • the medium BSR format or the medium truncated BSR format is determined as the target BSR format.
  • the filling bits are sufficient to report the buffered data volume of all LCGs with buffered data
  • determine the medium BSR format as the target BSR format and when the filled bits are insufficient to report the buffered data volume of all LCGs with buffered data , determining the medium truncated BSR format as the target BSR format, and the BSR in the medium truncated BSR format is used to report the cached data volume of the LCG with higher priority among the LCGs with cached data.
  • Case 3 When the first identifier is greater than the first value and the number of LCGs with cached data is greater than or equal to the second value, the communication device may determine the target BSR format according to the number of padding bits.
  • the LCG determines whether the LCG with cached data has an LCG whose LCG identifier is less than or equal to the first value, if any of the LCGs with buffered data has an LCG whose identifier is less than or equal to the first value
  • the LCG determines the second short truncated BSR format as the target BSR format, and the BSR in the second truncated short BSR format is used to report the buffered data volume of an LCG whose LCG identifier is less than or equal to the first value among the LCGs with buffered data.
  • the first short truncated BSR format is determined as the target BSR format, and the BSR of the first short truncated BSR format is used to report an LCG with a higher priority among the LCGs with cached data The amount of cached data.
  • the medium truncated BSR format is determined as the target BSR format.
  • the first long BSR format or the first long truncated BSR format is determined as the target BSR format.
  • the stuffing bits are enough to report the buffered data volume of all LCGs with buffered data
  • determine the first long BSR format as the target BSR format; if the stuffed bits are insufficient to report the buffered data volume of all LCGs with buffered data
  • the first long truncated BSR format is determined as the target BSR format
  • the BSR in the first long truncated BSR format is used to report the buffered data volume of the LCG with higher priority among the LCGs with buffered data.
  • the foregoing fourth value may be the number of bits occupied when the number of LCGs reported by the BSR in the medium BSR format is equal to the second value.
  • the communication device may determine the target BSR format according to the number of padding bits.
  • the second short truncated BSR format is determined as the target BSR format, and the BSR of the second short truncated BSR format is used to report the highest priority LCG among the LCGs with buffered data The amount of cached data.
  • the second long BSR format or the second long truncated BSR format is determined as the target BSR format.
  • the second long BSR format is determined as the target BSR format; if the stuffed bits are insufficient to report the buffered data volume of all LCGs with buffered data
  • the second long truncated BSR format is determined as the target BSR format, and the BSR in the second long truncated BSR format is used to report the cached data volume of the LCG with higher priority among the LCGs with cached data.
  • the foregoing fifth value may be determined according to the size of the BSR in the second short BSR format and the size of the MAC subheader of the BSR in the second short BSR format.
  • the fifth value may be specifically equal to the size of the BSR in the second short BSR format plus the size of the MAC subheader of the BSR in the second short BSR format, that is, the fifth value is the bits required to report the BSR in the second short BSR format number.
  • the target BSR format is determined according to the comparison result between the first identifier and the first value, and the number of LCGs with cached data, so as to select an appropriate BSR format to report the LCG with cached data
  • the amount of buffered data can make reasonable use of uplink resources to report to the BSR, and realize fine-grained scheduling of network resources.
  • the communication device may determine the target BSR format used for reporting the BSR from multiple BSR formats according to the comparison result between the first identifier and the first value, the number of LCGs with cached data, and the number of padding bits.
  • the communication device may determine the target BSR format used for reporting the BSR according to the comparison result between the first identifier and the first value, the number of LCGs with cached data, the number of padding bits, and the third value.
  • the communication device may compare the number of LCGs with cached data with the number of LCGs that can be reported by a BSR in any one of the multiple BSR formats, and compare the first identifier with any of the above multiple BSR formats
  • a BSR in a BSR format can compare the maximum value of the LCG identifier of the LCG that can be reported by the BSR, and compare the padding bits with the number of bits occupied by the BSR in any one of the above-mentioned BSR formats, and determine the number of bits that have cached data.
  • the target BSR format that the LCG matches, so that the BSR in the target BSR format can report the buffered data volume of some or all of the LCGs in the LCGs with buffered data.
  • the above-mentioned multiple BSR formats include the first BSR format, the maximum value of LCG identifiers of LCGs that can be reported by the first BSR format is 7, and the number of LCGs that can be reported is 8, and the first BSR format required to report The minimum number of bits is 2 bytes. If the number of LCGs with cached data is 3, the maximum LCG identifier among the LCG identifiers of LCGs with cached data is 5, and the number of padding bits is 8 bytes, the above-mentioned first BSR format is the same as that of the LCG with cached data match, thus determining the first BSR format as the target BSR format.
  • the determination of the target BSR format based on the comparison result of the first identifier and the first value, the number of LCGs with cached data, and the number of padding bits may include the following steps:
  • the number of LCGs with cached data is 1, and the number of padding bits is greater than or equal to a third value, determine the first short BSR format as the the target BSR format described above; or,
  • the number of LCGs with cached data is greater than 1, and the number of padding bits is equal to the third value, the first short BSR format determined as the target BSR format; or,
  • the second short BSR format determines the second short BSR format as In the target BSR format, the BSR in the second short BSR format is used to report the amount of buffered data in the LCGs whose LCG identifiers are smaller than the first value among the LCGs with buffered data; or,
  • medium BSR The format is determined to be the target BSR format
  • the medium BSR The format is determined to be the target BSR format
  • the number of LCGs with a cached amount is greater than 1, and the padding bit is equal to a fifth value, determine the second short BSR format as the target BSR format; or,
  • the number of LCGs with cached data is greater than 1, and the padding bit is greater than a fifth value, determine the second long BSR format as the Target BSR format.
  • the above multiple BSR formats may include a first long BSR format, a first short BSR format, a medium BSR format, a second long BSR format, and a second short BSR format.
  • the BSR in the first long BSR format is used to report the buffered data volume of the LCG whose LCG identifier is within the first identification threshold, and the BSR in the first long BSR format includes a first bitmap, and each bit in the first bitmap It is used to indicate whether each LCG of at least one LCG has cached data, or is used to indicate whether the buffer size BS field corresponding to each LCG of at least one LCG exists, and the LCG identification of the at least one LCG is within the first identification threshold Inside.
  • the above-mentioned first long BSR format may be the extended long BSR format as shown in FIG. 7 .
  • the BSR in the second long BSR format is used to report the buffered data volume of the LCG whose LCG identifier is within the second identification threshold
  • the BSR in the second long BSR format includes a second bit map, and each bit in the second bit map above It is used to indicate whether each LCG in at least one LCG has cached data, or is used to indicate whether the buffer size BS field corresponding to each LCG in at least one LCG exists, and the LCG identification of the at least one LCG is within the second identification threshold Inside.
  • the first identification threshold is greater than the second identification threshold, and the number of bits in the first bitmap is greater than the number of bits in the second bitmap.
  • the above-mentioned second long BSR format may be a conventional long BSR format as shown in FIG. 5 .
  • the BSR in the first short BSR format is used to report the buffered data volume of an LCG whose LCG identifier is within the first identifier threshold.
  • the BSR in the first short BSR format includes a first LCGID field, and the first LCGID field is used to indicate the identity of the above-mentioned one LCG.
  • the above-mentioned first short BSR format may be the extended short BSR format as shown in FIG. 6 .
  • the BSR in the second short BSR format is used to report the buffered data volume of an LCG whose LCG identifier is within the second identifier threshold.
  • the BSR in the second short BSR format includes a second LCGID field, and the second LCGID field is used to indicate the identity of the above-mentioned one LCG.
  • the number of bits of the first LCGID field is greater than the number of bits of the second LCGID.
  • the above-mentioned second short BSR format may be a conventional short BSR format as shown in FIG. 4 .
  • the BSR in the medium BSR format is used to report the buffered data volume of the LCG whose LCG identifier is within the first identifier threshold.
  • the BSR in the medium BSR format includes an LCG identifier of at least one LCG and indication information for indicating the amount of cached data of the at least one LCG.
  • the at least one LCG is at least one LCG among the LCGs with cached data.
  • the above medium BSR format may be the medium BSR format as shown in Fig. 8a or Fig. 8b.
  • the foregoing first value may be equal to the foregoing second identification threshold.
  • the communication device may use the BSR in the second long BSR format or the BSR in the second short BSR format to report the cached data volume of some or all of the LCGs in the LCGs with cached data;
  • the communication device may use the BSR in the first long BSR format, the BSR in the first short BSR format, or the BSR in the medium BSR format to report some or all of the LCGs with the cached number The amount of cached data.
  • the foregoing second value may be determined according to the number of bytes occupied by the first bitmap in the foregoing first long BSR format.
  • the second value may specifically be the number of bytes occupied by the first bitmap in the long BSR format.
  • the third value is determined according to the size of the BSR in the first short BSR format and the size of the MAC subheader of the BSR in the first short BSR format.
  • the third value may specifically be the number of bits occupied by the first short BSR format.
  • the above fourth value is the number of bits occupied when the number of LCGs reported in the medium BSR format is equal to the second value.
  • the fifth value is determined according to the size of the BSR in the second short BSR format and the size of the MAC subheader corresponding to the second short BSR format.
  • the fifth value may specifically be the number of bits occupied by the BSR in the second short BSR format plus the number of bits occupied by the MAC subheader of the BSR in the second short BSR format, that is, the fifth value is the number of bits reported by the BSR in the second short BSR format the number of bits required.
  • the above first short BSR format can also be understood as the first short truncated BSR format
  • the above first long BSR format can also be understood as the first long truncated BSR format
  • the above medium BSR format can also be understood as the medium truncated BSR format
  • the above second The long BSR format can also be understood as the second long truncated BSR format
  • the second short BSR format can also be understood as the second short truncated BSR format.
  • the number of LCGs with cached data is 1, and the number of padding bits is greater than or equal to the third value, determine the first short BSR format as the target short BSR format.
  • the first short truncated BSR format is used to report the cached data volume of the LCG with the highest priority among the LCGs with cached data.
  • the second short truncated BSR The format is determined to be the target BSR format.
  • the BSR in the second short truncated BSR format is used to report the cached data volume of the LCGs whose LCG identifiers are smaller than the first value among the LCGs with cached data.
  • the number of LCGs with cached data is greater than 1, and the number of filling bits is greater than the third value and less than the fourth value, determine the size of the BSR in the medium BSR format, and the medium BSR format
  • the size of the MAC subheader of the BSR if the number of padding bits is greater than or equal to the size of the BSR of the medium BSR format plus the size of the MAC subheader of the BSR of the medium BSR format, then the medium BSR format is determined as the target BSR format. If the number of padding bits is less than the size of the BSR in the medium BSR format plus the size of the MAC subheader of the BSR in the medium BSR format, the medium truncated BSR format is determined as the target BSR format.
  • the medium BSR format is determined as the target BSR format.
  • the number of LCGs with cached data is greater than or equal to the second value
  • the number of padding bits is greater than or equal to the fourth value
  • determine the size of the BSR in the first long BSR format and The size of the MAC subheader of the BSR in the first long BSR format, if the number of padding bits is greater than or equal to the size of the BSR in the first long BSR format plus the size of the MAC subheader in the BSR in the first long BSR format, then the second A long BSR format is determined as the target BSR format.
  • the number of padding bits is less than the size of the BSR in the first long BSR format plus the size of the MAC subheader of the BSR in the first long BSR format, then determine the first long truncated BSR format as the target BSR format.
  • the number of LCGs with a cached number is greater than 1, and the filling bits are equal to the fifth value, determine the second short truncated BSR format as the target BSR format.
  • the number of LCGs with cached data is greater than 1, and the filling bits are greater than the fifth value, determine the size of the BSR in the second long BSR format, and determine the size of the BSR in the second long BSR format.
  • the size of the MAC subhead of the BSR if the quantity of padding bits is greater than or equal to the size of the BSR of the second long BSR format plus the size of the MAC subhead of the BSR of the second long BSR format, then the second long BSR format is determined as Target BSR format.
  • the second long truncated BSR format is less than the size of the BSR in the second long BSR format plus the size of the MAC subheader of the BSR in the second long BSR format.
  • the first long BSR format is the extended long BSR format
  • the first short BSR format is the extended short BSR format
  • the second long BSR format is the regular long BSR format
  • the second short BSR format is the regular short BSR format.
  • the first value is 7.
  • the first identification threshold is 255
  • the second identification threshold is 7 as an example.
  • the communication device determines the normal short BSR format as the target BSR format.
  • the communication device determines the normal short BSR format as the target BSR format. It should be understood that, when the number of LCGs with cached data is 1, the first identifier is less than or equal to 7, and the number of padding bits is greater than or equal to 2 fields, the communication device may also determine the extended short BSR format as the target BSR format.
  • the communication device determines the extended short BSR format as the target BSR format.
  • the communication device determines the conventional short truncated BSR format as The target BSR format, the BSR in the regular short truncated BSR format is used to report the cached data volume of the LCG with the highest priority among the LCGs with cached data.
  • the communication device determines the conventional long truncated BSR format as the target BSR format.
  • the BSR in the conventional long-truncated BSR format is used to report the cached data volume of the LCG with the highest priority among the above-mentioned LCGs with cached data.
  • the communication device determines the extended short truncated BSR format as the target BSR format, and the extended short truncated BSR format The BSR is used to report the cached data volume of the LCG with the highest priority among the LCGs with cached data.
  • the communication device determines the size of the BSR in the conventional long BSR format and the conventional The size of the MAC subheader of the BSR in the long BSR format.
  • the communication device determines the regular long BSR format as the target BSR format. Otherwise the communications device determines the regular long truncated BSR format as the target BSR format.
  • the communication device determines the size of the BSR in the medium BSR format and the medium BSR The size of the MAC subheader of the formatted BSR. In case the padding bits are greater than or equal to the size of the BSR of the medium BSR format plus the size of the MAC subheader of the BSR of the regular long BSR format, the communication device determines the medium BSR format as the target BSR format. Otherwise the communication device determines the medium truncated BSR format as the target BSR format.
  • the communication The device determines the LCG ID of the high-priority LCG among the LCGs with cached data, and selects the one that can report the largest number of LCGs from the medium truncated BSR format and the regular long BSR format when the LCG ID of the high-priority LCG is less than 7 format to report to BSR.
  • the medium truncated BSR format determines the conventional long BSR format as the target BSR format; identify in the LCG with buffered data If the number of LCGs less than or equal to 7 is less than the number of LCGs that can be reported using the medium truncated BSR format, the medium truncated BSR format is determined as the target BSR format. For example, assuming that the number of padding bits is 10, the BSR in the medium truncated BSR format can report the buffered data volume of 5 LCGs.
  • the BSR can only report the amount of buffered data of LCGs whose identifiers are less than 7. Therefore, the number of LCGs that can be reported by the BSR of the conventional long BSR format is less than 5, and the communication device determines the medium BSR format as the target BSR format; If the number of identified LCGs is greater than 5, the communication device determines the conventional long BSR format as the target BSR format.
  • the communication device determines the conventional long BSR format as the target BSR format.
  • the communication device determines the medium BSR format as the target BSR format.
  • the communication device determines the extended long BSR format or the extended long truncated BSR format as the target BSR format .
  • the target BSR format is determined according to the comparison result of the first identifier and the first value, the number of LCGs with cached data, and the number of padding bits, so as to select an appropriate BSR format to report the cache of LCGs with cached data
  • the amount of data can be reported to the BSR by rational use of uplink resources to achieve fine-grained scheduling of network resources.
  • FIG. 10 is a schematic flowchart of another communication method provided by the embodiment of the present application. As shown in Figure 10, the communication method includes but is not limited to the following steps:
  • the foregoing first numerical value may be set by a network device, and the first numerical value may specifically be 7.
  • the communication device determines a target BSR format from a plurality of BSR formats based on a comparison result between the second identifier and the first value.
  • a target BSR format from a plurality of BSR formats based on a comparison result between the second identifier and the first value.
  • the comparison results determine the target BSR format from the above-mentioned various BSR formats. When the number of reported LCGs is the same, the number of bits occupied by the BSR of the above two BSR formats is different.
  • the foregoing first value may be equal to a maximum value of LCG identifiers of LCGs that can be reported by one of the foregoing multiple BSR formats.
  • the communication device determines the above-mentioned one BSR format as the target BSR format.
  • the LCG of the above-mentioned communication device is configured by a network device, and the network device configures the correspondence between the LCG and the LCH for the communication device through configuration information.
  • the communication device determines the LCG that the communication device can use according to the configuration information sent by the network device.
  • the determination of the target BSR format based on the comparison result between the second identifier and the first value includes:
  • the BSR in the first format is used to report the buffered data volume of LCGs whose LCG identifiers are within the first identification threshold
  • the BSR in the second format is used to report the buffered data volume of LCGs whose LCG identifiers are within the second identification threshold.
  • An identification threshold is greater than the above-mentioned second identification threshold.
  • the foregoing multiple BSR formats may include a first format and a second format, and the BSR in the first format and the BSR in the second format may report different identification ranges of LCG identifiers of LCGs.
  • the communication device may determine the identity range to which the LCG identity of the LCG that needs to be reported belongs according to the first identity, and determine the target BSR format corresponding to the identity range.
  • the above-mentioned first value may be equal to the maximum value of the LCG identifier of the LCG that the BSR in the second format can report, that is, the above-mentioned first value may be equal to the above-mentioned second identifier threshold, and the BSR in the second format cannot report the LCG identifier greater than LCG of the first value. If the second identifier is less than or equal to the first value, determine the second format as the target BSR format. If the second identifier is greater than the first value, determine the first format as the target BSR format.
  • the number of bits occupied by the BSR in the first format is greater than the number of bits occupied by the BSR in the second format.
  • the BSR in the first format includes the first LCGID field or the first bit map, the first LCG field is used to indicate the identity of the reported LCG, and each bit in the first bit map is used to indicate at least one LCG in each Whether there is buffer data in one LCG, or whether the buffer size BS field corresponding to each LCG in at least one LCG exists.
  • the BSR in the second format includes a second LCGID field or a second bitmap
  • the second LCG field is used to indicate the identity of the reported LCG
  • each bit in the second bitmap is used to indicate that each of the at least one LCG Whether there is buffer data in one LCG, or whether the buffer size BS field corresponding to each LCG in at least one LCG exists.
  • the number of bits in the first LCGID field is greater than that in the second LCGID field
  • the number of bits in the first bitmap is greater than that in the second bitmap.
  • the BSR in the second format cannot report the buffered data volume of the LCG whose LCG identifier is greater than the second identifier threshold, so the first value is used.
  • One format of the BSR reports the amount of cached data of the configured LCG of the communication device. In the case where the second identifier is less than or equal to the first value, the LCG identifiers of the LCGs configured on the communication device are all less than or equal to the second identifier threshold, and the BSR in the second format can be used to report the buffered data volume of the LCG configured on the communication device .
  • the communication device may also use the BSR in the first format to report the buffered data volume of the LCG configured on the communication device.
  • the number of bits occupied by the BSR in the first format is greater than the number of bits occupied by the BSR in the second format.
  • the above-mentioned first identification threshold may be 255, and the BSR in the first format may report LCGs whose LCG identifications are between 0 and 255.
  • the above-mentioned second identification threshold may be 7, and the BSR in the second format may report LCGs whose LCG identifications are between 0 and 7.
  • the first format may include the extended short BSR format shown in FIG. 6, the extended long BSR format shown in FIG. 7, and the medium BSR format shown in FIG. 8a or 8b.
  • the second format may include the conventional short BSR format shown in FIG. 4 and the conventional long BSR format shown in FIG. 5 . When the second identifier is greater than 7, the communication device determines the first format as the target BSR format; when the second identifier is less than or equal to 7, the communication device determines the second format as the target BSR format.
  • the communication device may determine the specific format of the first format or the second format according to the number of LCGs with cached data and the number of padding bits.
  • the above-mentioned communication device determines the specific format of the first format or the second format according to the number of LCGs with cached data and the number of padding bits, and reference may be made to the relevant description of the first implementation manner of step 901.
  • the first format when the second identifier is greater than the first value, the first format is determined as the target BSR format; when the second identifier is less than or equal to the first value, the second format is determined as the target BSR format. While ensuring the integrity of the reported LCG with cached data, the number of bits required for reporting the BSR is saved, and resource utilization efficiency is improved.
  • step 1002 and step 1003 reference may be made to the specific description of step 902 and step 903 shown in FIG. 9 , which will not be repeated here.
  • a BSR format of a format is determined as the target BSR format according to the LCG identifier of the configured LCG of the communication device, and the BSR is reported in the target BSR format.
  • the target BSR format is determined according to the configuration of the communication device, so that the format used by the communication device to report the BSR matches the configuration information of the communication device, and the BSR can be reported reasonably.
  • FIG. 11 is a schematic flowchart of another communication method provided by an embodiment of the present application. As shown in Figure 11, the communication method includes but is not limited to the following steps:
  • the above-mentioned first value may be specified by the protocol, or may be configured by the network device, and the first value may specifically be 7.
  • the communication device determines the target BSR format used for reporting the BSR from multiple BSR formats based on a comparison result between the number of LCGs configured on the communication device and the first value.
  • multiple BSR formats there are at least two different BSR formats, and the BSRs of the two BSR formats can report different numbers of LCGs.
  • the above-mentioned first value may be the number of LCGs that can be reported by a BSR in one BSR format among the above-mentioned multiple BSR formats.
  • the communication device determines the aforementioned one BSR format as the target BSR format.
  • the LCG of the above-mentioned communication device is configured by a network device, and the network device configures the correspondence between the LCG and the LCH for the communication device through configuration information.
  • the communication device determines the number of LCGs that the communication device can use according to the configuration information sent by the network device.
  • the determination of the target cache status report BSR format based on the comparison result between the number of LCGs configured by the communication device and the first value includes:
  • the second format is determined as the target BSR format.
  • the multiple BSR formats may include a first format and a second format, and the BSRs in the first format and the BSRs in the second format may report different numbers of LCGs.
  • the number of LCGs that can be reported by the BSR in the first format is the first number threshold
  • the number of LCGs that can be reported by the BSR in the second format is the second number threshold
  • the first number threshold is greater than the second number threshold.
  • using the BSR in the second format to report the buffered data volume of the LCGs may result in failure to report the buffered data volumes of some LCGs.
  • the BSR in the first format is used to report the buffered data amount of the LCG.
  • the above-mentioned first number threshold may be 256, and the above-mentioned second number threshold may be eight.
  • the first format may include the extended short BSR format shown in FIG. 6, the extended long BSR format shown in FIG. 7, and the medium BSR format shown in FIG. 8a or 8b.
  • the second format may include the conventional short BSR format shown in FIG. 4 and the conventional long BSR format shown in FIG. 5 .
  • the communication device determines the first format as the target BSR format; when the number of LCGs configured by the communication device is less than or equal to 8, the communication device determines the second format Determined as the target BSR format.
  • the communication device may determine the specific format of the first format or the second format according to the number of LCGs with cached data and the number of padding bits.
  • the above-mentioned communication device determines the specific format of the first format or the second format according to the number of LCGs with cached data and the number of padding bits, and reference may be made to the relevant description of the first implementation manner of step 901 .
  • the number of bits of the BSR in the first format is greater than that of the BSR in the second format, and the BSR in the second format cannot report an LCG whose LCG identifier is greater than the first value.
  • determine the first format as the target BSR format determines the first format as the target BSR format; when the number of LCGs configured on the communication device is less than or equal to the first value, determine the second format Determined as the target BSR format. While ensuring the integrity of the reported LCG with cached data, the number of bits required for reporting the BSR is saved, and resource utilization efficiency is improved.
  • step 1102 and step 1103 reference may be made to the specific description of step 902 and step 903 shown in FIG. 9 , which will not be repeated here.
  • a BSR format of one format is determined as the target BSR format according to the number of LCGs configured on the communication device, and the BSR is reported in the target BSR format.
  • the target BSR format is determined according to the configuration of the communication device, so that the format used by the communication device to report the BSR matches the configuration information of the communication device, and the BSR can be reported reasonably.
  • FIG. 12 is an example of a BAP topology of an IAB network provided by an embodiment of the present application.
  • the BAP topology refers to the topology of the BAP layer.
  • IAB2-MT and IAB2-DU are two parts included in IAB node 2
  • IAB3-MT and IAB-DU3 are two parts included in IAB node 3 .
  • the topology in the thin line box represents BAP topology 1 controlled by Donor-CU1 , for example, the BAP address of the IAB node located in BAP topology 1 is allocated by Donor-CU1 .
  • the topology in the thick line box represents the BAP topology 2 controlled by Donor-CU2, for example, the BAP address of the IAB node located in BAP topology 2 is allocated by Donor-CU2.
  • BAP topology 1 includes IAB node 1 , IAB node 2 and IAB node 3 ;
  • BAP topology 2 includes IAB node 4 .
  • the MT of IAB node 2, ie, IAB-MT2 is connected to Donor-DU1 and Donor-DU2 respectively through dual connections.
  • the F1 interface of the IAB node 2 is terminated at CU1, that is, CU1 is the F1-termination node of the IAB node 2.
  • the service of an IAB node or the service of a UE connected under the IAB node may be transmitted via several different types of nodes.
  • These different types of nodes may include IAB nodes managed by CU1 (for example, IAB node 4 ), and IAB nodes managed by CU2 (for example, IAB node 3 ).
  • IAB node 2 can receive the data packet sent by CU1 via Donor-DU1 and IAB node 1 (see the path indicated by the solid arrow in Figure 12), and can also receive the data packet sent by CU1 via Donor-DU2 and IAB node 3 delivered data packets (refer to the path indicated by the dotted arrow in FIG. 12 ).
  • the IAB node 2 is a boundary node in the IAB network shown in FIG. 12 . Because the F1 interface of IAB node 2 is terminated in CU1 (the DU of IAB node 2 is terminated in CU1), the DU of one parent node of IAB node 2 (IAB node 3) is terminated in CU2.
  • Uu interface exists between IAB node 2 and donor base station 1 (gNB1, including CU1 and Donor-DU1), and Uu exists between IAB node 2 and donor base station 2 (gNB2, including CU2 and Donor-DU2) interface.
  • An F1 interface exists between the IAB node 2 and the donor base station 1 .
  • the F1 interface communication between IAB node 2 and host base station 1 can pass through either Donor DU1 or Donor DU2, that is to say, host base station 1 can choose to communicate with IAB node 2 through Donor DU1, and/or, Donor DU2 F1 interface communication.
  • the dual connectivity scenario may exist not only in the process of the IAB node 2 performing a handover across the primary base station, but also in the process of the IAB node 2 performing the addition of the secondary base station.
  • IAB node 2 first establishes a connection with the first parent node (that is, IAB 1), and then establishes a connection with the second parent node (that is, IAB 4) by adding a secondary station, wherein the first parent node is connected to CU1, and the second parent node The node is connected to CU2.
  • the DU part of IAB node 2 is connected to CU1, but its MT part is simultaneously connected to the cell served by IAB node 1 (specifically its DU part) and the cell served by IAB node 4 (specifically its DU part).
  • the child nodes and subordinate UEs of IAB node 2 still maintain a connection relationship with CU1 (that is, Donor DU2 and IAB node 4 in the current thick line frame are managed or controlled by the target IAB host, or are controlled by CU 2
  • the network segment, other thin line frame parts are managed or controlled by the source IAB host node, or belong to the network segment controlled by CU 1.
  • IAB2-MT can be regarded as a node controlled or managed by the source IAB host.
  • IAB2-MT communicates with IAB node 1, it can be regarded as a node managed or controlled by the source IAB host, or It belongs to the network segment controlled by CU 1; in addition, IAB2-MT can be regarded as a network segment controlled by the target IAB host. Part of the nodes can also be regarded as managed or controlled by the target IAB host, or belong to the network segment controlled by CU 2.
  • IAB2-MT can be regarded as controlled by the maintenance of its radio resources Layer (Radio Resource Control, RRC) node controlled or managed by the host node connected, or belongs to the network segment controlled by the host node maintaining its RRC connection, for example, the RRC connection of IAB2-MT is maintained with CU 1,
  • RRC Radio Resource Control
  • the management of IAB2-MT can be regarded as a node controlled or managed by the source IAB host). Therefore, the service of UE served by IAB node 2 and the service of IAB node 3 (including the services of subordinate UE2 and UE3) can be transmitted via IAB node 2, IAB node 4 and Donor DU2 (see the dotted double arrow in the figure indicated path).
  • RRC Radio Resource Control
  • FIG. 13 is another communication method provided by the embodiment of this application.
  • the method is applied to the border nodes of the IAB network, and the border nodes in the IAB network are located in the first BAP topology (such as the above-mentioned BAP topology 1) and also in the second BAP topology (such as the above-mentioned BAP topology 2).
  • a border node in the IAB network may have the following characteristics: the IAB-donor-CU where the DU of the border node terminates is different from the IAB-donor-CU where the DU of at least one parent node terminates.
  • Boundary IAB node can be defined as follows: IAB-node, whose IAB-DU is terminated to a different IAB-donor-CU than a parent DU. Assuming that an IAB node in the IAB network has two parent nodes, the DU of the IAB node terminates in the CU of IAB-donor 1, the DU of a parent node of the IAB node terminates in the CU of IAB-donor 1, and the DU of the IAB node terminates in the CU of IAB-donor 1. The DU of another parent node terminates at the CU of IAB-donor 2, then the IAB node is a border node. The method comprises the steps of:
  • the IAB node receives a BAP data packet through a first ingress link.
  • the above-mentioned IAB node is a border node of the IAB network.
  • the receiving end of the BAP entity of the IAB node receives the BAP data packet through the first ingress link.
  • the BAP data packet may specifically be a BAP data PDU.
  • the above-mentioned first ingress link may be an ingress link, or an ingress channel.
  • the first ingress link may correspond to a first ingress backhaul RLC channel (backhaul RLC channel, BH RLC CH).
  • the IAB node determines whether the destination address of the BAP data packet matches the BAP address of the IAB node, where the BAP address of the IAB node is the BAP address corresponding to the first ingress link.
  • the BAP address corresponding to the first ingress link may be understood as the BAP address configured for the IAB node by the base station corresponding to the first ingress link.
  • the above-mentioned IAB node may be configured with multiple BAP addresses, the above-mentioned IAB node may be connected to multiple BAP topologies, and each of the multiple base stations managing the above-mentioned multiple BAP topologies allocates a BAP address for the above-mentioned IAB node.
  • the IAB node receives the BAP data packet sent by the first BAP topology through the first ingress link, and the first BAP topology is managed by the first base station.
  • the IAB node parses out the destination address of the BAP data packet from the received BAP data packet, and compares the destination address with the BAP address configured by the first base station for the above-mentioned IAB node. If the above-mentioned destination address is the same as the BAP address configured by the first base station for the IAB node, then it is determined that the destination address of the above-mentioned BAP data packet matches the BAP address of the above-mentioned IAB node. If not, it is determined that the destination address of the BAP data packet does not match the BAP address of the IAB node.
  • the IAB node may be dual-connected to a first BAP topology and a second BAP topology, the first BAP topology is managed by a first base station (eg gNB1), and the second BAP topology is managed by a second base station (eg gNB2).
  • the first ingress link is used to receive the BAP data packet sent from the first BAP topology
  • the second ingress link is used to receive the data packet from the second BAP topology.
  • the BAP address configured by gNB1 for the IAB node is X
  • the BAP address configured by gNB2 for the IAB node is Y.
  • the BAP address X configured by gNB1 for the IAB node is compared with the destination address in the BAP data packet to determine whether they match.
  • the BAP address Y configured by gNB2 for the IAB node is compared with the destination address in the BAP data packet to determine whether they match.
  • the IAB node can remove the BAP header in the BAP data packet to obtain the BAP SDU. Submit the BAP SDU to the upper layer of the BAP layer of the IAB node.
  • the IAB node receives the BAP data packet through the first ingress link, and matches the destination address of the BAP data packet with the BAP address corresponding to the first ingress link in the IAB node. In the case that the destination address matches the above-mentioned BAP address, the BAP data packet is processed. Prevent wrong processing of BAP packets, resulting in waste of resources.
  • FIG. 14 is another communication method provided by the embodiment of this application. As shown in Figure 14, the communication method includes:
  • the IAB node receives a BAP data packet through a first ingress link.
  • step 1401 for the specific implementation of step 1401, reference may be made to the specific description of step 1301 shown in FIG. 13 , which will not be repeated here.
  • the MT side of the IAB node determines whether the first ingress link is a secondary cell group (secondary cell group, SCG) and IAB link between nodes, and determine if the above IAB node is configured with multiple BAP addresses.
  • secondary cell group secondary cell group
  • the IAB node After receiving the BAP data packet through the first ingress link, the IAB node compares the destination address in the BAP data packet with the BAP address of the IAB node to determine whether they match. In the case that the destination address in the BAP data packet does not match the BAP address of the IAB node, it means that the above-mentioned BAP data packet is not sent to the above-mentioned IAB node, and the IAB node needs to route it to the correct path. Exemplarily, it is determined by the MT side of the IAB node that the BAP header of the above-mentioned BAP data packet may need to be rewritten, so as to route the above-mentioned BAP data packet to a correct path.
  • the MT side of the IAB node determines whether the first ingress link is a link between the SCG and the IAB node, or the MT side of the IAB node determines whether the first ingress link is the direct air interface wireless connection between the IAB node in the SCG and the secondary base station link. In the case where the MT side of the IAB node determines that the first ingress link is a link between the SCG and the IAB node, it means that the above BAP is from the secondary base station. In the case that the first ingress link is a link between the SCG and the IAB node, the MT side of the IAB node determines whether the above-mentioned IAB node is configured with multiple BAP addresses. In the case that the IAB node is configured with multiple BAP addresses, it may be necessary to rewrite the BAP header of the above-mentioned BAP data packet.
  • the above-mentioned IAB node may be dual-connected to the first BAP topology and the second BAP topology, the first BAP topology is managed by the first base station (such as gNB1), and the second BAP topology is managed by the second base station (such as gNB2).
  • the ingress link 1 is used to receive the BAP data packet sent by the first BAP topology
  • the ingress link 2 is used to receive the data packet sent by the second BAP topology.
  • gNB1 may act as the primary base station of the IAB node
  • gNB2 may act as the secondary base station.
  • the MT side of the IAB node determines that the first ingress link is the link between the SCG and the IAB node, and may determine that the above BAP data packet comes from the second BAP topology.
  • the IAB node is configured with two BAP addresses, it means that the IAB node can be connected to two topologies.
  • the destination address of the above-mentioned BAP data packet does not match the BAP address of the above-mentioned IAB node, it means that the above-mentioned BAP data packet is not sent to the IAB node, and the IAB node needs to route it to the correct path.
  • the IAB node When the BAP packet received by the IAB node is sent by the second BAP topology, and not sent to the IAB node, the IAB node needs to rewrite the BAP header of the BAP packet and send it to the child node, so that the IAB node Child nodes are able to identify the BAP packet.
  • the IAB network shown in FIG. 12 may be an example of an IAB network to which the method in FIG. 14 is applicable.
  • the first BAP topology corresponds to BAP topology 1
  • the second BAP topology corresponds to BAP topology 2
  • gNB1 corresponds to CU1 and Donor-DU1
  • gNB2 corresponds to CU2 and Donor-DU2
  • the above IAB node corresponds to IAB node 2.
  • step 1402 may be replaced by: when the destination address of the BAP data packet does not match the BAP address of the IAB node, the DU side of the IAB node determines whether the IAB node is configured with multiple BAPs address. When the DU side of the IAB node determines that the above-mentioned IAB node is configured with multiple BAP addresses, it is determined that the BAP header of the above-mentioned BAP data packet may need to be rewritten.
  • the BAP header of the BAP data packet is removed to obtain the BAP SDU, and the BAP SDU is delivered to the upper layer of the BAP layer.
  • the MT side of the IAB node determines that the above-mentioned first ingress link is a link between the SCG and the IAB node and that the above-mentioned IAB node is configured with multiple BAP addresses, it may be necessary to determine the BAP header of the above-mentioned BAP data packet is overridden.
  • Determining that the BAP header of the above BAP data packet may need to be rewritten can also be understood as determining to execute the BAP header rewriting judging process.
  • the BAP header rewriting judgment process can be: check whether the first BAP routing identifier of the above-mentioned BAP packet matches a rewriting table (rewriting table), that is, judge whether the first BAP routing identifier can be rewriting; , then rewrite the first BAP routing identifier to the second BAP routing identifier based on the rewriting table. If the first BAP routing identifier does not match the rewriting table, the first data packet is delivered to the upper layer of the BAP node of the first IAB node.
  • a rewriting table rewriting table
  • the rewriting table can contain one or more sets of BAP routing identifier mapping relationships, and each set of BAP routing identifier mapping relationships is used to convert a BAP routing identifier that is not recognized by the IAB node (that is, a BAP route recognizable by the IAB node in the second BAP topology) ID) is mapped to the BAP routing ID recognizable by the IAB node (that is, the BAP routing ID recognizable by the IAB nodes in the first BAP topology).
  • Checking whether the first BAP routing identifier of the BAP packet matches the rewriting table may be: querying whether the rewriting table includes the mapping relationship between the first BAP routing identifier and other BAP routing identifiers.
  • Rewriting the first BAP routing identifier into a second BAP routing identifier based on the rewriting table may be: obtaining a second BAP routing identifier that has a BAP routing identifier mapping relationship with the first BAP routing identifier based on the rewriting table.
  • Table 3 is an example of a rewriting table provided by this application.
  • the first column is the original BAP routing identifier
  • the second column is the rewritten BAP routing identifier.
  • each original BAP route identifier in the first column is a BAP route identifier recognizable by the IAB nodes in the second BAP topology.
  • each original BAP routing identifier in the first column corresponds to a BAP routing identifier from a downlink data packet (eg, a BAP data packet) belonging to the second BAP topology.
  • the rewritten BAP routing identifier in the second column is a BAP routing identifier recognizable by the IAB node.
  • the original BAP routing identifier in each row corresponds to the rewritten BAP routing identifier in the row.
  • the first BAP route identifier in the first row corresponds to the second BAP route identifier in the first row.
  • the first BAP routing identifier can query whether the first column of table 1 contains the first BAP routing identifier; if so, the first BAP routing identifier matches the rewriting table; if not, the first BAP routing identifier does not match the rewriting table . In this example, if the first column of Table 1 contains the first BAP routing identifier, the second BAP routing identifier that has a mapping relationship with the first BAP routing identifier is acquired.
  • the above step 1403 may be replaced by: when the DU side of the IAB node determines that the above IAB node is configured with multiple BAP addresses, it is determined that the BAP header of the above BAP data packet may need to be rewritten.
  • the ingress link of the IAB node receiving BAP data and the egress link of the sending BAP node may not be in the same BAP topology, so the BAP header of the above BAP data packet may need to be rewrite. Determining that the BAP header of the above BAP data packet may need to be rewritten can also be understood as determining to execute the BAP header rewriting judging process.
  • the MT side of the IAB node determines that the first ingress link is not an SCG or that the IAB node is configured with only one BAP address, determine not to rewrite the BAP header of the BAP data packet.
  • the MT side of the IAB node determines that the above-mentioned first ingress link is not the SCG, it means that the BAP data packet is from the master base station, and then it is determined that the BAP header of the BAP data packet does not need to be rewritten.
  • the IAB node is configured with only one BAP address, it means that the IAB node is only connected to one BAP topology, and it is determined that the BAP header of the BAP data packet does not need to be rewritten.
  • the MT side of the IAB node or the DU side of the IAB node may determine whether the BAP header of the BAP data packet needs to be rewritten, so that the BAP data packet received by the IAB node is routed to the correct path.
  • the communication device 150 may implement the functions or steps of the foregoing method embodiments.
  • the communications device may include a processing module 1501 and a transceiver module 1502 .
  • a storage unit may also be included, and the storage unit may be used to store instructions (code or program) and/or data.
  • the processing module 1501 and the transceiver module 1502 may be coupled with the storage unit, for example, the processing module 1501 may read instructions (code or program) and/or data in the storage unit to implement a corresponding method.
  • Each of the above units can be set independently, or can be partially or fully integrated.
  • the transceiving module 1502 may include a sending module and a receiving module.
  • the processing module 1501 is configured to support the communication device to execute step 901, step 902, step 1001, step 1002, step 1101 and step 1102, and/or other processes for the technologies described herein.
  • a transceiver module 1502 configured to support communication between the communication device and other communication devices, for example, support access to the communication device to perform step 903, step 1003 and step 1103, and/or other processes for the technologies described herein .
  • FIG. 16 is a schematic structural diagram of another communication device 160 provided in an embodiment of the present application.
  • the communication device 160 can implement the method provided in the embodiment of the present application.
  • the communication device 160 may be a system on a chip.
  • the system-on-a-chip may be composed of chips, or may include chips and other discrete devices.
  • the above-mentioned transceiver module 1502 may be a transceiver, and the transceiver is integrated in the communication device 160 to form the communication interface 1601 .
  • the communication device 160 includes at least one processor 1602, configured to implement or support the communication device 160 to implement the method provided in the embodiment of the present application. For details, refer to the detailed description in the method example, and details are not repeated here.
  • the communication device 160 may also include at least one memory 1603 for storing program instructions and/or data.
  • the memory 1603 is coupled to the processor 1602 .
  • the coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • Processor 1602 may cooperate with memory 1603 .
  • the processor 1602 may execute program instructions and/or data stored in the memory 1603, so that the communication device 160 implements a corresponding method. At least one of the at least one memory may be included in the processor.
  • the communication device 160 may also include a communication interface 1601 for communicating with other devices through a transmission medium, so that devices used in the communication device 160 can communicate with other devices.
  • a communication interface 1601 for communicating with other devices through a transmission medium, so that devices used in the communication device 160 can communicate with other devices.
  • the communication apparatus 160 is an IAB node
  • the other device is another IAB node or a terminal device.
  • the processor 1602 can use the communication interface 1601 to send and receive data.
  • the communication interface 1601 may specifically be a transceiver.
  • the embodiment of the present application does not limit the specific connection medium among the communication interface 1601, the processor 1602, and the memory 1603.
  • the memory 1603, the processor 1602, and the communication interface 1601 are connected through the bus 1604.
  • the bus is represented by a thick line in FIG. 16, and the connection between other components is only for schematic illustration. , is not limited.
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 16 , but it does not mean that there is only one bus or one type of bus.
  • the processor 1602 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement Or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.
  • a general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the memory 1603 may be a non-volatile memory, such as a hard disk (hard disk drive, HDD) or a solid-state drive (solid-state drive, SSD), etc., and may also be a volatile memory (volatile memory), For example random-access memory (random-access memory, RAM).
  • a memory is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the memory in the embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, and is used for storing program instructions and/or data.
  • FIG. 17 shows another form of the communication device 160 .
  • the communication device 170 is an IAB node.
  • the IAB node includes a CU and a DU.
  • the CU may include a communication interface, a processor, and a memory, and a bus connecting the communication interface, the processor, and the memory.
  • the communication interface may be used to communicate with The CU of the IAB host node or the DU of the IAB node communicate.
  • the DU may also include a communication interface, a processor, and a memory, and a bus connecting the communication interface, the processor, and the memory, wherein the communication interface is used to communicate with the MT of the IAB node.
  • FIG. 18 is a schematic structural diagram of another communication device 180 provided by an embodiment of the present application.
  • the communication device 180 shown in FIG. 18 includes a logic circuit 1801 and an interface 1802 .
  • the processing module in FIG. 15 can be realized by a logic circuit 1801
  • the transceiver module in FIG. 15 can be realized by an interface 1802 .
  • the logic circuit 1801 may be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc.
  • the interface 1802 may be a communication interface, an input-output interface, or the like.
  • the logic circuit and the interface may also be coupled to each other. The embodiment of the present application does not limit the specific connection manner of the logic circuit and the interface.
  • the logic circuit and interface may be used to execute the methods shown in FIGS. 9 to 11 above.
  • the embodiment of the present application also provides a chip system, the chip system includes at least one processor, memory and interface circuit, the memory, the transceiver and the at least one processor are interconnected by wires, the at least one memory
  • a computer program is stored in the computer; when the computer program is executed by the processor, the method flow shown in FIG. 9 to FIG. 11 is realized.
  • An embodiment of the present application also provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is run on a communication device, the method flow shown in FIG. 9 to FIG. 11 is realized.
  • An embodiment of the present application further provides a computer program product.
  • the computer program product is run on a communication device, the method flows shown in FIGS. 9 to 11 are implemented.
  • sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the processes can be completed by computer programs or hardware related to the computer programs.
  • the computer programs can be stored in computer-readable storage media.
  • the computer programs During execution, it may include the processes of the foregoing method embodiments.
  • the aforementioned storage medium includes: ROM or random access memory RAM, magnetic disk or optical disk, and other various media that can store computer program codes.

Landscapes

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

Abstract

本申请实施例提供一种通信方法、装置以及存储介质。该通信方法包括：基于第一标识和第一数值的比较结果确定目标缓存状态报告BSR格式，其中，所述第一标识为有缓存数据的逻辑信道组LCG的LCG标识中最大的LCG标识；根据所述目标BSR格式生成BSR。能够合理利用上行传输资源上报BSR。

Description

通信方法、装置以及存储介质
本申请要求于2021年10月21日提交中国专利局、申请号为202111229686.8、申请名称为“通信方法、装置以及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法、装置以及存储介质。
背景技术
在通信系统中，通信装置有缓存数据需要传输时，通过缓冲区状态报告(buffer status report，BSR)向基站上报通信装置的缓存数据量，以便基站根据通信装置的缓存数据量为通信装置分配上行传输资源。
根据业务的不同，通信装置可能建立大量的无线承载，如果为每一个逻辑信道(logical channel，LCH)都上报一个BSR，会带来大量的信令开销。为了减少这种开销，将LCH组合分类，形成逻辑信道组(logical channel group，LCG)，每个LCH对应属于一个LCG。BSR是以LCG为粒度进行上报。每个LCG的缓存数据量包括该LCG所包含的所有的逻辑信道的缓存数据的总量。通信装置的LCG和LCH的对应关系是由基站配置的，在长期演进(long term evolution，LTE)通信系统中定义了LCG的数量为4，在新空口(new radio，NR)通信系统中将LCG的数量扩展至8。
随着通信系统的发展，LCG的数量增多，通信装置需要上报的LCG的数量增多。因此，如何合理上报BSR是亟需解决的问题。
发明内容
本申请实施例提供一种通信方法、装置以及存储介质，能够合理上报BSR。
第一方面，本申请实施例提供一种通信方法，该通信方法包括：
基于第一标识和第一数值的比较结果确定目标缓存状态报告BSR格式，其中，所述第一标识为有缓存数据的逻辑信道组LCG的LCG标识中最大的LCG标识；根据所述目标BSR格式生成BSR。
在本申请实施例中，通信装置可以根据第一标识与第一数值的比较结果，确定一个合适的BSR格式上报BSR，可以合理利用上行传输资源上报BSR，实现网络资源的精细化调度。
在第一方面的一种可能实施方式中，所述基于第一标识和第一数值的比较结果确定目标BSR格式，包括：在所述第一标识大于所述第一数值的情况下，将第一格式确定为所述目标BSR格式，所述第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量；在所述第一标识小于或等于所述第一数值的情况下，将第二格式确定为所述目标BSR格式，所述第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量；其中，所述第一标识阈值大于所述第二标识阈值。
在该种实施方式中，上报相同数量的LCG时，第一格式的BSR的比特数大于第二格式的BSR，第二格式的BSR不能上报LCG标识大于第一数值的LCG。在第一标识大于第一数值的情况下，将第一格式确定为目标BSR格式；在第一标识小于或等于第一数值的情况下， 将第二格式确定为目标BSR格式。在保证上报的有缓存数据的LCG的完整性的同时，节省上报BSR所需的比特数，提高资源的利用效率。
在第一方面的一种可能实施方式中，在所述有缓存数据的LCG的数量为1的情况下，所述第一格式或者第二格式为短BSR格式；或者，在所述有缓存数据的LCG的数量大于1且小于第二数值的情况下，所述第一格式或者第二格式为中等BSR格式；或者，在所述有缓存数据的LCG的数量大于或等于所述第二数值的情况下，所述第一格式或者第二格式为长BSR格式。
在该种实施方式中，根据有缓存数据的LCG的数量确定第一格式或第二格式的具体格式，其中，上述短BSR格式用于上报一个LCG的缓存数据量，上述长BSR格式和上述中等BSR格式可以上报一个或多个LCG的缓存数据量，其中，短BSR格式的比特数小于长BSR格式和中等BSR格式。在BSR上报的LCG的数量大于1且小于第二数值的情况下，上报相同数量的LCG时，中等BSR格式的BSR的比特数小于长BSR格式的BSR的比特数；在BSR上报的LCG的数量大于或等于第二数值的情况下，上报相同数量的LCG时，中等BSR格式的BSR的比特数大于或等于长BSR格式的BSR的比特数。在有缓存数据的LCG的数量为1的情况下，第一格式或第二格式为短BSR格式；在有缓存数据的LCG的数量大于1且小于第二数值的情况下，第一格式或者第二格式为中等BSR格式；在有缓存数据的LCG的数量大于或等于第二数值的情况下，所述第一格式或者第二格式为长BSR格式。在保证上报的LCG的完整性的同时，节省上报BSR所需的比特数，提高资源的利用效率。
在第一方面的一种可能实施方式中，所述长BSR格式的BSR包括第一比特图，所述第一比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个LCG中的每一个LCG对应的缓存大小BS字段是否存在。
在该种实施方式中，通过比特图的方式指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个LCG中的每一个LCG对应的缓存大小BS字段是否存在，无需上报LCG的标识，在上报的LCG的数量大于或等于第二数值的情况下，节省上报BSR所需的比特数，减少数量的浪费。
在第一方面的一种可能实施方式中，所述中等BSR格式的BSR包括至少一个LCG的LCG标识，和用于指示所述至少一个LCG的缓存数据量的指示信息。
在该种实施方式中，在上报的LCG的数量小于第二数值的情况下，使用中等BSR格式上报BSR，节省上报BSR所需的比特数，提高资源的利用效率。
在第一方面的一种可能实施方式中，所述短BSR格式的BSR包括第一LCG的LCG标识，和一个用于指示所述第一LCG的缓存数据量的指示信息。
在该种实施方式中，在需上报的LCG的数量为1时，使用短BSR格式上报BSR，能够合理利用上行传输资源，减少数据的浪费。
在第一方面的一种可能实施方式中，所述基于第一标识和第一数值的比较结果确定目标BSR格式，包括：基于所述第一标识和所述第一数值的比较结果，以及填充比特的数量和第三数值的比较结果，确定所述目标BSR格式。
在该种实施方式中，根据第一标识和所述第一数值的比较结果，以及填充比特的数量和第三数值的比较结果，确定所述目标BSR格式，以选择合适的BSR格式上报有缓存数据的LCG的缓存数据量，能够合理利用上行资源上报BSR，实现网络资源的精细化调度。
在第一方面的一种可能实施方式中，所述基于所述第一标识和所述第一数值的比较结果，以及填充比特的数量和第三数值的比较结果，确定所述目标BSR格式，包括：在所述第一标 识大于所述第一数值且填充比特的数量大于或等于第三数值的情况下，将第一格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值且所述填充比特的数量小于所述第三数值的情况下，将第二格式确定为所述目标BSR格式；所述第二格式的BSR用于上报所述有缓存数据的LCG中LCG标识小于所述第一数值的LCG的缓存数据量；或者，在所述第一标识小于或等于所述第一数值的情况下，将所述第二格式确定为所述目标BSR格式。
在该种实施方式中，第一格式的BSR与第二格式的BSR能够上报的LCG的LCG标识阈值不同，占用的比特数不同。根据第一标识和第一数值的比较结果以及填充比特的数量从第一格式和第二格式中确定合适的BSR格式，利用该BSR格式上报BSR，保证上报的LCG的完整性。
在第一方面的一种可能实施方式中，在所述填充比特的数量等于所述第三数值的情况下，所述第一格式为短BSR格式；或者，在所述填充比特的数量大于所述第三数值且小于第四数值的情况下，所述第一格式为中等BSR格式；或者，在所述填充比特的数量大于或等于所述第四数值的情况下，所述第一格式为长BSR格式。
在该种实施方式中，根据填充比特的数量确定第一格式的具体格式，在填充比特的数量等于第三数值的情况下，第一格式为短BSR格式；在填充比特的数量大于第三数值且小于第四数值的情况下，第一格式为中等BSR格式；在填充比特的数量大于或等于第四数值的情况下，第一格式为长BSR格式，保证填充比特的数量大于或等于第一格式的BSR的大小加上第一格式的BSR的MAC子头的大小，减少了因生成的BSR的比特数大于填充比特的数量而无法上报BSR的情况的发生。
在第一方面的一种可能实施方式中，所述第三数值根据所述第一格式的BSR的大小和所述第一格式的BSR的媒体介入控制MAC子头的大小确定。
在该种实施方式中，第三数值具体可以为第一格式的BSR上报一个LCG的缓存数据量时占用的比特数加上第一格式的MAC子头占用的比特数，即第三数值为通信装置要发送第一格式的BSR所需的最小比特数。在填充比特的数量大于第三数值的情况下，将第一格式确定为目标BSR格式，确保填充比特足以上报生成的第一格式的BSR。
在第一方面的一种可能实施方式中，所述基于第一标识和第一数值的比较结果确定目标BSR格式，包括：基于所述第一标识和所述第一数值的比较结果，以及所述有缓存数据的LCG的数量确定所述目标BSR格式。
在该种实施方式中，根据第一标识和所述第一数值的比较结果，以及有缓存数据的LCG的数量确定目标BSR格式，以选择合适的BSR格式上报有缓存数据的LCG的缓存数据量，能够合理利用上行资源上报BSR，实现网络资源的精细化调度。
在第一方面的一种可能实施方式中，所述基于所述第一标识和所述第一数值的比较结果，以及所述有缓存数据的LCG的数量确定所述目标BSR格式，包括：在所述第一标识大于所述第一数值且有缓存数据的LCG的数量为1的情况下，将第一短BSR格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值且所述有缓存数据的LCG的数量大于1且小于第二数值的情况下，将中间BSR格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值且所述有缓存数据的LCG的数量大于或等于所述第二数值的情况下，将第一长BSR格式确定为所述目标BSR格式；或者，在所述第一标识小于或等于所述第一数值且所述有缓存数据的LCG的数量为1的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，在所述第一标识小于或等于所述第一数值且所述有缓存数据的LCG的数量大于1的情况下，将第二长BSR格式确定为所述目标BSR格式。
在该种实施方式中，根据第一标识和第一数值的比较结果，以及有缓存数据的LCG的数量从第一长BSR格式，第一短BSR格式，中等BSR格式，第二长BSR格式以及第二短BSR格式中确定一个合适的BSR格式，利用该BSR格式上报BSR，在保证上报的LCG的完整性的同时，节省上报BSR所需的比特数，提高资源的利用效率。
在第一方面的一种可能实施方式中，所述基于第一标识和第一数值的比较结果确定目标BSR格式，包括：基于所述第一标识和所述第一数值的比较结果，所述有缓存数据的LCG的数量以及填充比特的数量确定所述目标BSR格式。
在该种实施方式中，根据第一标识和所述第一数值的比较结果，有缓存数据的LCG的数量，以及填充比特的数量和第三数值的比较结果，确定所述目标BSR格式，以选择合适的BSR格式上报有缓存数据的LCG的缓存数据量，能够合理利用上行资源上报BSR，实现网络资源的精细化调度。
在第一方面的一种可能实施方式中，所述基于所述第一标识和所述第一数值的比较结果，所述有缓存数据的LCG的数量以及填充比特的数量确定所述目标BSR格式，包括：在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量为1且所述填充比特的数量大于或等于第三数值的情况下，将第一短BSR格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量等于所述第三数值的情况下，将所述第一短BSR格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量小于所述第三数值的情况下，将第二短BSR格式确定为所述目标BSR格式，所述第二短BSR格式的BSR用于上报所述有缓存数据的LCG中LCG标识小于所述第一数值的LCG的缓存数据量；或者，在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量大于所述第三数值且小于第四数值的情况下，将中等BSR格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1且小于第二数值，且填充比特的数量大于所述第四数值的情况下，将所述中等BSR格式确定为目标BSR格式；或者，在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于或等于所述第二数值，且所述填充比特的数量大于所述第四数值的情况下，将第一长BSR格式确定为所述目标BSR格式；或者，在所述第一标识小于或等于所述第一数值，所述有缓存数量的LCG的数量为1的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，在所述第一标识小于或等于所述第一数值，所述有缓存数量的LCG的数量大于1，且所述填充比特等于第五数值的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，在所述第一标识小于或等于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特大于第五数值的情况下，将第二长BSR格式确定为所述目标BSR格式。
在该种实施方式中，根据第一标识和第一数值的比较结果，以及有缓存数据的LCG的数量以及填充比特的数量从第一长BSR格式，第一短BSR格式，中等BSR格式，第二长BSR格式以及第二短BSR格式中确定一个合适的BSR格式，利用该BSR格式上报BSR，在保证上报的LCG的完整性的同时，节省上报BSR所需的比特数，提高资源的利用效率。
在第一方面的一种可能实施方式中，所述第五数值根据所述第二短BSR格式的BSR的大小和所述第二短BSR格式对应的MAC子头的大小确定。
在第一方面的一种可能实施方式中，所述第一数值为7。
第二方面，本申请实施例提供一种通信方法，包括：基于第二标识与第一数值的比较结果确定目标缓存状态报告BSR格式，所述第二标识为通信装置被配置的LCG的LCG标识中 最大的LCG标识；根据所述目标BSR格式生成BSR。
在本申请实施例中，根据通信装置被配置的LCG的LCG标识确定一个格式的BSR格式为目标BSR格式，利用目标BSR格式上报BSR。根据通信装置的配置情况确定目标BSR格式，以使通信装置上报BSR使用的格式与通信装置的配置信息相匹配，可以合理上报BSR。
在第二方面的一种可能实施方式中，所述基于第二标识与第一数值的比较结果确定目标缓存状态报告BSR格式，包括：在所述第二标识大于所述第一数值的情况下，将第一格式确定为所述目标BSR格式，所述第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量；在所述第二标识小于或等于所述第一数值的情况下，将第二格式确定为所述目标BSR格式，所述第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量；其中，所述第一标识阈值大于所述第二标识阈值。
在该种实施方式中，上报相同数量的LCG时，第一格式的BSR的比特数大于第二格式的BSR，第二格式的BSR不能上报LCG标识大于第一数值的LCG。在第二标识大于第一数值的情况下，将第一格式确定为目标BSR格式；在第二标识小于或等于第一数值的情况下，将第二格式确定为目标BSR格式。在保证上报的有缓存数据的LCG的完整性的同时，节省上报BSR所需的比特数，提高资源的利用效率。
第三方面，本申请实施例提供一种通信方法，包括：基于通信装置被配置的LCG的数量确定目标BSR格式；根据所述目标BSR格式生成BSR。
在本申请实施例中，根据通信装置被配置的LCG的数量确定一个格式的BSR格式为目标BSR格式，利用目标BSR格式上报BSR。根据通信装置的配置情况确定目标BSR格式，以使通信装置上报BSR使用的格式与通信装置的配置信息相匹配，可以合理上报BSR。
在第三方面的一种可能实施方式中，所述基于通信装置被配置的LCG的数量确定目标BSR格式，包括：在所述LCG的数量大于第一数值的情况下，将第一格式确定为所述目标BSR格式，所述第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量；在所述LCG的数量小于或等于所述第一数值的情况下，将第二格式确定为所述目标BSR格式，所述第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量；其中，所述第一标识阈值大于所述第二标识阈值。
在该种实施方式中，上报相同数量的LCG时，第一格式的BSR的比特数大于第二格式的BSR，第二格式的BSR不能上报LCG标识大于第一数值的LCG。在通信装置被配置的LCG的数量大于第一数值的情况下，将第一格式确定为目标BSR格式；在通信装置被配置的LCG的数量小于或等于第一数值的情况下，将第二格式确定为目标BSR格式。在保证上报的有缓存数据的LCG的完整性的同时，节省上报BSR所需的比特数，提高资源的利用效率。
第四方面，本申请实施例提供一种通信装置，包括：
处理模块，用于基于第一标识和第一数值的比较结果确定目标缓存状态报告BSR格式，其中，所述第一标识为有缓存数据的逻辑信道组LCG的LCG标识中最大的LCG标识；
所述处理模块，还用于根据所述目标BSR格式生成BSR；
收发模块，用于向网络设备发送所述BSR。
在第四方面的一种可能实施方式中，所述处理模块，具体用于在所述第一标识大于所述第一数值的情况下，将第一格式确定为所述目标BSR格式，所述第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量；在所述第一标识小于或等于所述第一数值的情况下，将第二格式确定为所述目标BSR格式，所述第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量；其中，所述第一标识阈值大于所述第二标识阈值。
在第四方面的一种可能实施方式中，在所述有缓存数据的LCG的数量为1的情况下，所述第一格式或者第二格式为短BSR格式；或者，在所述有缓存数据的LCG的数量大于1且小于第二数值的情况下，所述第一格式或者第二格式为中等BSR格式；或者，在所述有缓存数据的LCG的数量大于或等于所述第二数值的情况下，所述第一格式或者第二格式为长BSR格式。
在第四方面的一种可能实施方式中，所述长BSR格式的BSR包括第一比特图，所述第一比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个LCG中的每一个LCG对应的缓存大小BS字段是否存在。
在第四方面的一种可能实施方式中，所述中等BSR格式的BSR包括至少一个LCG的LCG标识，和用于指示所述至少一个LCG的缓存数据量的指示信息。
在第四方面的一种可能实施方式中，所述短BSR格式的BSR包括第一LCG的LCG标识，和一个用于指示所述第一LCG的缓存数据量的指示信息。
在第四方面的一种可能实施方式中，所述处理模块，具体用于基于所述第一标识和所述第一数值的比较结果，以及填充比特的数量和第三数值的比较结果，确定所述目标BSR格式。
在第四方面的一种可能实施方式中，所述处理模块，具体用于所述第一标识大于所述第一数值且填充比特的数量大于或等于第三数值的情况下，将第一格式确定为所述目标BSR格式；或者，
在所述第一标识大于所述第一数值且所述填充比特的数量小于所述第三数值的情况下，将第二格式确定为所述目标BSR格式；所述第二格式的BSR用于上报所述有缓存数据的LCG中LCG标识小于所述第一数值的LCG的缓存数据量；或者，在所述第一标识小于或等于所述第一数值的情况下，将所述第二格式确定为所述目标BSR格式。
在第四方面的一种可能实施方式中，在所述填充比特的数量等于所述第三数值的情况下，所述第一格式为短BSR格式；或者，在所述填充比特的数量大于所述第三数值且小于第四数值的情况下，所述第一格式为中等BSR格式；或者，在所述填充比特的数量大于或等于所述第四数值的情况下，所述第一格式为长BSR格式。
在第四方面的一种可能实施方式中，所述第三数值根据所述第一格式的BSR的大小和所述第一格式的BSR的媒体介入控制MAC子头的大小确定。
在第四方面的一种可能实施方式中，所述处理模块，具体用于基于所述第一标识和所述第一数值的比较结果，以及所述有缓存数据的LCG的数量确定所述目标BSR格式。
在第四方面的一种可能实施方式中，所述处理模块，具体用于在所述第一标识大于所述第一数值且有缓存数据的LCG的数量为1的情况下，将第一短BSR格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值且所述有缓存数据的LCG的数量大于1且小于第二数值的情况下，将中间BSR格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值且所述有缓存数据的LCG的数量大于或等于所述第二数值的情况下，将第一长BSR格式确定为所述目标BSR格式；或者，在所述第一标识小于或等于所述第一数值且所述有缓存数据的LCG的数量为1的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，在所述第一标识小于或等于所述第一数值且所述有缓存数据的LCG的数量大于1的情况下，将第二长BSR格式确定为所述目标BSR格式。
在第四方面的一种可能实施方式中，所述处理模块，具体用于基于所述第一标识和所述第一数值的比较结果，所述有缓存数据的LCG的数量以及填充比特的数量确定所述目标BSR格式。
在第四方面的一种可能实施方式中，所述处理模块，具体用于在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量为1且所述填充比特的数量大于或等于第三数值的情况下，将第一短BSR格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量等于所述第三数值的情况下，将所述第一短BSR格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量小于所述第三数值的情况下，将第二短BSR格式确定为所述目标BSR格式，所述第二短BSR格式的BSR用于上报所述有缓存数据的LCG中LCG标识小于所述第一数值的LCG的缓存数据量；或者，在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量大于所述第三数值且小于第四数值的情况下，将中等BSR格式确定为所述目标BSR格式；或者，在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1且小于第二数值，且填充比特的数量大于所述第四数值的情况下，将所述中等BSR格式确定为目标BSR格式；或者，在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于或等于所述第二数值，且所述填充比特的数量大于所述第四数值的情况下，将第一长BSR格式确定为所述目标BSR格式；或者，在所述第一标识小于或等于所述第一数值，所述有缓存数量的LCG的数量为1的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，在所述第一标识小于或等于所述第一数值，所述有缓存数量的LCG的数量大于1，且所述填充比特等于第五数值的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，在所述第一标识小于或等于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特大于第五数值的情况下，将第二长BSR格式确定为所述目标BSR格式。
在第四方面的一种可能实施方式中，所述第五数值根据所述第二短BSR格式的BSR的大小和所述第二短BSR格式对应的MAC子头的大小确定。
在第四方面的一种可能实施方式中，所述第一数值为7。
关于第四方面或第四方面的各种可能的实施方式所带来的技术效果，可参考对于第一方面或第一方面的各种可能的实施方式的技术效果的介绍。
第五方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储器；存储器中存储有计算机程序；处理器执行计算机程序时，计算设备执行前述第一方面中任一项，或者第二方面任一项，或者第三方面任一项所描述的方法。
第六方面，本申请实施例提供一种通信装置，该通信装置包括逻辑电路和接口，所述逻辑电路和所述接口耦合；所述接口用于输入待处理的数据，所述逻辑电路按照如第一方面中任一项，或者第二方面任一项，或者第三方面任一项所描述的方法对所述待处理的数据进行处理，获得处理后的数据，所述接口用于输出所述处理后的数据。
第七方面，本申请实施例提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当所述指令在至少一个处理器上运行时，实现前述第一方面任一项、或第二方面任一项、或第三方面任一项所描述的方法。
第八方面，本申请提供一种计算机程序产品，该计算机程序产品包括计算机程序或计算机代码，当其在计算机上运行时，使得上述第一方面或第一方面的任意可能的实现方式所示的方法被执行，或者使得上述第二方面或第二方面的任意可能的实现方式所示的方法被执行，或者使得上述第三方面或第三方面的任意可能的实现方式所示的方法被执行。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的一种IAB系统的结构示意图；
图2是本申请实施例提供的一种IAB网络架构图；
图3是本申请实施例提供的一种MAC PDU的结构示意图；
图4是本申请实施例提供的一种BSR格式的结构示意图；
图5是本申请实施例提供的另一种BSR格式的结构示意图；
图6是本申请实施例提供的另一种BSR格式的结构示意图；
图7是本申请实施例提供的另一种BSR格式的结构示意图；
图8a为本申请实施例提供的另一种BSR格式的结构示意图；
图8b为本申请实施例提供的另一种BSR格式的结构示意图；
图9为本申请实施例提供的一种通信方法的流程示意图；
图10为本申请实施例提供的另一种通信方法的流程示意图；
图11为本申请实施例提供的另一种通信方法的流程示意图；
图12为本申请实施例通过的一种IAB网络的BAP拓扑的结构示意图；
图13为本申请实施例提供的另一种通信方法的流程示意图；
图14为本申请实施例提供的另一种通信方法的流程示意图；
图15为本申请实施例提供的一种通信装置的结构示意图；
图16为本申请实施例提供的另一种通信装置的结构示意图；
图17为本申请实施例提供的另一种通信装置的结构示意图；
图18为本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
本申请的说明书、权利要求书及附图中的术语“第一”和“第二”等仅用于区别不同对象，而不是用于限定多个对象的顺序、时序、优先级或者重要程度。本申请实施例中“多个”是指两个或两个以上。此外，术语“包括”和“具有”以及它们的任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备等，没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元等，或可选地还包括对于这些过程、方法、产品或设备等固有的其它步骤或单元。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。
在本文中提及的“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员可以显式地和隐式地理解的是，本文所描述的实施例可以与其它实施例相结合。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、通用移动通信系统(universal mobile telecommunication system，UMTS)、第五代(5th generation，5G)系统、新无线(new radio，NR)以及随着技术的发展出现的其他新的系统等。下面以NR中的接入回传一体化(integrated access and backhaul，IAB)网络场景 为例对本申请实施例的技术方案的应用场景进行举例介绍。
相较于第四代移动通信系统，第五代移动通信(5G)针对网络各项性能指标，提出了更严苛的要求。例如，容量提升1000倍，更广的覆盖需求、超高可靠超低时延等。一方面，考虑到高频载波频率资源丰富，在热点区域，为满足5G超高容量需求，利用高频小站组网愈发流行。高频载波传播特性较差，受遮挡衰减严重，覆盖范围不广，故而需要大量密集部署小站，相应地，为这些大量密集部署的小站提供光纤回传的代价很高，施工难度大，因此需要经济便捷的回传方案；另一方面，从广覆盖需求的角度出发，在一些偏远地区提供网络覆盖，光纤的部署难度大，成本高，也需要设计灵活便利的接入和回传方案。IAB技术为解决上述两个问题提供了思路：其接入链路(access link)和回传链路(backhaul link)皆采用无线传输方案，减少了光纤部署。
请参见图1，图1为本申请实施例提供的一种IAB系统结构的举例。在IAB网络中，中继节点RN(Relay Node)或者叫IAB节点(IAB node)，可以为用户设备(user equipment，UE)提供无线接入服务，UE的业务数据由IAB节点通过无线回传链路连接到IAB宿主(IAB donor)传输，本申请中IAB donor也可称为宿主节点(donor node)或宿主基站(DgNB，Donor gNodeB)。IAB节点由移动终端(mobile termination，MT)部分和分布式单元(distributed unit，DU)部分组成，其中，当IAB节点面向其父节点时，可以作为终端设备，即MT的角色；当IAB面向其子节点(子节点可能是另一IAB节点，或者普通UE)时，其被视为网络设备，即作为DU的角色。宿主基站DgNB可以是一个具有完整基站功能的接入网网元，还可以是集中式单元(centralized unit，CU)和分布式单元(distributed unit，DU)分离形态的接入网网元，宿主基站连接到为UE服务的核心网(例如连接到5G核心网，5GC)网元，并为IAB节点提供无线回传功能。为便于表述，将宿主节点的集中式单元简称为donor CU(或直接称为CU)，宿主节点的分布式单元简称为donor DU，其中donor CU还有可能是控制面(control plane，CP)和用户面(user plane，UP)分离的形态，例如：CU可由一个CU-CP和一个(或多个)CU-UP组成。
图1以包括2个UE和5个IAB节点为例。其中，这2个UE分别为UE1和UE2，这5个IAB节点分别为IAB节点1～IAB节点5。应理解，图1粗线示意接入链路，细线示意回传链路。其中，UE2可经由IAB节点5、IAB节点2和IAB节点1与宿主基站相连。UE2也可经由IAB节点4、IAB节点2和IAB节点1与宿主基站相连。或者UE2也可经由IAB节点4、IAB节点3和IAB节点1与宿主基站相连。UE1可经由IAB节点4、IAB节点3和IAB节点1与宿主基站相连。UE1可经由IAB节点4、IAB节点2和IAB节点1与宿主基站相连。
需要说明的是，图1所示的通信系统只是一种示例，并不对本申请实施例适用的应用场景构成限定。应理解，本申请实施例中采用IAB节点仅仅出于描述的需要，并不表示本申请实施例的方案仅用于NR的场景。
在IAB网络中，在UE和IAB宿主之间的一条传输路径上，可以包含一个或多个IAB节点。每个IAB节点需要维护面向父节点的无线回传链路，还需要维护与子节点之间的无线链路。若IAB节点的子节点是UE，该IAB节点和其子节点(即UE)之间是无线接入链路。若IAB节点的子节点是其他IAB节点，该IAB节点和其子节点(即其他IAB节点)之间是无线回传链路。参见图1，在路径“UE1→IAB节点4→IAB节点3→IAB节点1→IAB宿主”中，UE1通过无线接入链路接入IAB节点4，IAB节点4通过无线回传链路连接到IAB节点3，IAB节点3通过无线回传链路连接到IAB节点1，IAB节点1通过无线回传链路连接到IAB宿主节点。
本申请实施例提供的BSR上报方法可以应用于IAB网络，包括独立组网(standalone，SA)的IAB网络，以及非独立组网(non-standalone，NSA)的IAB网络。IAB节点包含MT部分和DU部分，IAB donor可以分为DU和CU部分，CU还可进一步分为CU-CP和CU-UP部分。图2为本申请实施例提供的一种IAB网络架构图的示例。图2展示IAB节点通过无线回传链路连接到IAB donor的示例。图2以包括1个UE、2个IAB节点以及2个IAB donor为例。其中，这两个IAB节点为IAB节点1和IAB节点2，这两个IAB节点均包括MT部分和DU部分；这两个IAB donor分别为IAB donor 1和IAB donor 2。这2个IAB donor为IAB donor 1和IAB donor 2，每个IAB donor可以进一步分为DU和CU部分，CU还可分为CU-CP和CU-UP部分。图2中，IAB节点2的MT和IAB节点1的DU之间、IAB节点1的MT与IAB donor 1的DU之间以及IAB节点1的MT与IAB donor 2的DU之间均通过无线回传(backhual，BH)链路(link)通信；UE和IAB2-DU之间建立有Uu接口；IAB donor DU与IAB donor CU-CP之间建立有F1-C接口，IAB donor DU与IAB donor CU-UP之间建立有F1-U接口；IAB donor 2的DU与IAB donor 1的CU之间通过IP network连接。
每个IAB节点的DU和IAB宿主的CU之间有F1接口。该F1接口可包含控制面和用户面两部分，其中用户面的部分是IAB-DU与IAB donor CU-UP之间维护的，而控制面部分是IAB-DU与IAB donor CU-CP之间维护的。IAB-DU和IAB donor CU之间的F1接口，在图2中未示出。当然该F1接口也可以称为F1*接口，本申请实施例对该接口的名称不作限制。且本文中以该接口称为F1接口为例。
F1接口可支持用户面协议(F1-U/F1*-U)和控制面协议(F1-C/F1*-C)，用户面协议包括以下协议层的一个或多个：通用分组无线服务(general packet radio service，GPRS)隧道协议用户面(GPRS tunnelling protocol user plane，GTP-U)协议层，用户数据报协议(user datagram protocol，UDP)协议层、因特网协议(internet protocol，IP)协议层等；控制面协议包括以下协议层中的一个或者多个：F1应用协议(F1 application protocol，F1AP)、流控传输协议(stream control transport protocol，SCTP)、IP协议层等。通过F1/F1*接口的控制面，IAB节点和IAB宿主之间可以进行执行接口管理、对IAB-DU进行管理，以及执行UE上下文相关的配置等。通过F1/F1*接口的用户面，IAB节点和IAB宿主之间可以执行用户面数据的传输，以及下行传输状态反馈等功能。
在IAB节点工作在SA模式时，IAB node可以单连接到一个父节点，或者双连接到两个父节点。其中这两个父节点可以由同一个IAB donor控制，或者分别由不同的IAB donor控制。IAB node的DU部分与一个IAB donor之间建立F1接口即可，该IAB donor可以连接到5G核心网，即图2中的粗线部分。其中IAB-donor-CU-CP通过NG控制面接口(NG-C)连接到5GC中的控制面网元(例如接入和移动性管理功能)，IAB-donor-CU-UP通过NG用户面接口(NG-U)连接到5GC中的用户面网元(例如用户面功能)。
当IAB节点工作在NSA模式时，IAB-donor-CU-UP可以通过S1用户面接口(S1-U)连接到EPC(例如连接到业务网关(serving gateway，SGW))，MeNB与IAB node的MT之间有LTE Uu空口连接，MeNB与IAB-donor-CU-CP之间有X2-C接口，MeNB通过S1接口连接到EPC(包括S1接口用户面，以及S1接口控制面)，即图2中的虚线部分。
另一种可能的情况，图2中的MeNB也可以换成5G的基站gNB。图2中的LTE-Uu接口相应的被替换为NR-Uu接口，gNB可以和5GC之间建立用户面和/或控制面的接口，gNB和IAB-donor为IAB节点提供双连接服务，gNB可以作为IAB节点的主基站的角色，或者辅基站的角色。
前述为本申请实施例的技术方案的一种应用场景的举例，应理解的是，本申请实施例的技术方案不限定只应用于图2所示的网络架构中。
本申请实施例中，终端设备可以称为用户设备(user equipment，UE)、终端设备、终端、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。例如终端设备可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的通信设备。终端设备可以经无线接入网(radio access network，RAN)与核心网进行通信，与RAN交换语音和/或数据。终端设备可称为接入终端、终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线网络设备、用户代理或用户装置。终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless localloop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备或物联网、车辆网中的终端设备以及未来网络中的任意形态的终端设备等。
通信装置上报BSR是通过媒体介入控制(Media Access Control，MAC)层的MAC控制单元(control element，CE)进行上报的。示例性的，MAC CE可以包含于MAC协议数据单元(protocol data unit，PDU)，例如一个MAC PDU可以包括一个或多个MAC子PDU(subPDU)。示例性的，一个MAC subPDU可以包括以下任意一种：
1)一个MAC子头(subheader)；
2)一个MAC子头加一个MAC服务数据单元(service data unit，SDU)；
3)一个MAC子头加一个MAC CE；
4)一个MAC子头加填充(padding)。
请参见图3，图3为本申请实施例提供的一种MAC PDU的结构示意图。图3示出的MAC PDU中包括至少5个MAC subPDU，其中两个MAC SDU，一个固定大小的MAC CE 1，一个可变大小的MAC CE 2，以及填充(padding)。上述MAC SDU和可变大小的MAC CE 2的子头由四个报头字段R/F/LCID/L组成。固定大小的MAC CE 1的子头由两个报头字段R/LCID组成。可理解，关于图3所示的MAC PDU的描述仅为示例，不应将其理解为对本申请实施例的限定。
R字段为保留位，设置为0。
L字段以字节为单位，表示相应MAC SDU或可变大小的MAC CE的长度。除了包含上行公共控制通道(uplink common control channel，UL CCCH)的MAC SDU、填充和固定大小的MAC CE对应的子头之外，每个MAC子头有一个L字段。L字段的大小由F字段表示。
F字段占用1比特，用于表示长度字段(L字段)的大小，除了固定大小的MAC CE、填充和包含UL CCCH的MAC SDU对应的子头之外，每个MAC子头都有一个F字段。F字段为0时，表示长度字段占用8比特大小，F字段为1时，表示长度字段占用16比特大小。
LCID字段占用6比特，每个MAC子头都有一个LCID字段。该字段表示MAC SDU对应的逻辑信道实例，MAC CE对应的类型或者padding。
当通信装置满足BSR的触发条件时，通信装置触发一个BSR上报。BSR的触发条件如下，通信装置满足下列条件之一都会触发一个BSR：
1)缓冲区有新数据到达：当属于任一LCG的LCH中有缓存数据，且当前所有的LCG中的LCH都没有缓存数据时，通信装置触发BSR上报，该BSR称为常规BSR(Regular BSR)。
2)高优先级的数据到达：当属于任一LCG的LCH有缓存数据，且该LCH的优先级高于已经上报的LCG中任何一个LCG的LCH的优先级，通信装置触发BSR上报，该BSR被 称为常规BSR(Regular BSR)。
3)通信装置周期性向网络设备上报：基站通过MAC-MainConfig的periodicBSR-Timer字段为通信装置配置了一个定时器(timer)，在该timer超时的情况下，通信装置触发BSR上报，该BSR被称为周期BSR(Periodic BSR)。
4)定时重传：基站通过MAC-MainConfig的retxBSR-Timer字段为通信装置配置了一个定时器(timer)，当该timer超时且通信装置中任一个LCG的任意一个LCH有缓存数据的情况下，通信装置触发BSR，该BSR被称为常规BSR。
5)当通信装置有上行资源且需要发送的数据不足以填满该资源时，多余的比特会作为填充比特(padding bits)。当padding bits大于或等于“BSR MAC CE+对应的子头”的大小时，通信装置触发BSR，利用padding bits发送该BSR，该BSR被称为填充Padding BSR。
应理解的是，上述BSR触发条件仅为示例，本申请实施例的BSR触发条件不限于上述5种示例，还可以包括随着技术的发展出现的新的其他BSR触发条件。
请参见图4，图4为本申请实施例提供的一种BSR格式的结构示意图。图4所示的BSR格式可以称为常规短BSR格式(Short BSR format)。常规短BSR格式的BSR用于上报一个LCG的缓存数据量，常规短BSR格式的BSR包括一个逻辑信道组标识(LCGID)字段和一个缓存大小(Buffer Size，BS)字段。上述LCGID字段用于指示BSR上报的LCG的标识，上述BS字段用于指示BSR上报的LCG的缓存数据量。示例性的，图4所示的BSR格式占用一个字节(octet，Oct)，其中，上述LCGID字段占用3比特，利用3位比特来表示LCG的标识可以表示标识在0到7之间的LCG的标识，因此常规短BSR格式的BSR可以上报标识小于或等于7的LCG。MAC层对不同LCG的实际缓存大小进行量化，BS字段指示的LCG的实际缓存大小对应的缓存数据量范围。示例性的，上述BS字段占用5比特，BS字段的值指示的是LCG的缓存数据量范围，MAC层将LCG的实际缓存大小量化为32个缓存数据量范围。BS字段的值为LCG的缓存数据量范围的索引。用于间接指示LCG的缓存数据量范围。索引与LCG的缓存数据量范围之间的映射关系如表1所示。如表1所示，BS值(BS value)表示缓存数据量范围，单位为字节，索引(Index)用于间接指示缓存数据量范围，一个索引对应一个缓存数据量范围，索引表示对应的BS字段的值。举例来说，假设LCG的缓存数据量为100字节，所属的缓存数据量范围为74<BS≤102，对应的索引为8，对应的BS字段的值为“01000”。
表1
索引 BS值 索引 BS值 索引 BS值 索引 BS值
0 0 8 ≤102 16 ≤1446 24 ≤20516
1 ≤10 9 ≤142 17 ≤2014 25 ≤28581
2 ≤14 10 ≤198 18 ≤2806 26 ≤39818
3 ≤20 11 ≤276 19 ≤3909 27 ≤55474
4 ≤28 12 ≤384 20 ≤5446 28 ≤77284
5 ≤38 13 ≤535 21 ≤7587 29 ≤107669
6 ≤53 14 ≤745 22 ≤10570 30 ≤150000
7 ≤74 15 ≤1038 23 ≤14726 31 >150000
示例性的，上述表1可以是协议规定的，也可以是网络设备配置的。
图4所示的BSR还可以称为常规短截断BSR格式(Short Truncated BSR format)，常规 短截断BSR格式的BSR用于上报有缓存数据的LCG中的一个LCG的缓存数据量，该LCG可以为有缓存数据的LCG中优先级高的一个LCG的缓存数据量。LCG的优先级根据其包含的LCH的优先级确定，将每个LCG包含的LCH中优先级最高的LCH的优先级作为其LCG的优先级。在通信装置触发padding BSR且填充比特(padding bits)的数量只能够上报一个LCG的缓存数据量的情况下，通信装置使用常规短截断BSR格式的BSR上报有缓存数据量的LCG中优先级最高的LCG的缓存数据量。
请参见图5，图5为本申请实施例提供的另一种BSR格式的结构示意图。图5所示的BSR格式可以记为常规长BSR格式(Long BSR format)。常规长BSR格式的BSR用于上报一个或多个LCG的缓存数据量。常规长BSR格式的BSR包括一个比特图和一个或多个BS字段。上述比特图中的每一位比特用于指示一个LCG是否有缓存数据，或者用于指示一个LCG对应的BS字段是否存在。上述一个或多个BS字段中的每一个BS字段用于指示上述一个或多个LCG中的一个LCG的缓存数据量。常规长BSR格式的BSR中包括的BS字段的数量为BSR上报的LCG的数量，即图5中的m为BSR上报的LCG的数量。
对于常规长BSR格式的BSR，比特图中的每一位比特用于指示LCG对应的BS字段是否存在。比特图可以包括多个LCGi字段，LCGi字段用于指示第i个LCG对应的BS字段是否存在。在常规长BSR格式的BSR中，BS字段的数量等于有缓存数据的LCG的数量，LCGi字段还可以指示第i个LCG是否有缓存数据。当LCGi字段的值为1时，表示BSR中包括第i个LCG对应的BS字段存在，即第i个LCG有缓存数据；当LCGi字段的值为0时，表示BSR中第i个LCG对应的BS字段不存在，即第i个LCG没有缓存数据。应理解的是，比特图中的LCGi字段的值为1或0只是示例，不应对本申请构成限制，如LCGi字段的值可以2、3或4等均可以，只要在第i个LCG有缓存数据和第i个LCG没有缓存数据时，LCGi字段的取值不同，以使网络设备可以通过比特图中的LCGi字段的值确定对应的第i个LCG是否有缓存数据即可。上述一个或多个BS字段的排列顺序可以是按照对应的LCG的优先级排列，即优先级较高的LCG对应的BS字段排在优先级较低的LCG对应的BS字段的前面。
图5所示的BSR格式还可以称为常规长截断BSR格式(Long Truncated BSR format)，对于常规长截断BSR格式的BSR，比特图中的每一位用于指示对应的LCG是否有缓存数据。常规长BSR格式的截断BSR用于上报所有有缓存数据的LCG的部分LCG的缓存数据量，并不是每个有缓存数据的LCG都上报，即并非每个有缓存数据的LCG都有对应的BS字段，因此在常规长截断BSR格式的BSR中，LCGi字段用于指示第i个LCG是否有缓存数据。LCGi字段的值为1时，表示第i个LCG有缓存数据；LCGi字段的值为0时，表示第i个LCG没有缓存数据。应理解的是，比特图中的LCGi字段的值为1或0只是示例，不应对本申请构成限制，如LCGi字段的值可以2、3或4等均可以，只要在第i个LCG有缓存数据和第i个LCG没有缓存数据时，LCGi字段的取值不同，以使网络设备可以通过比特图中的LCGi字段的值确定对应的第i个LCG是否有缓存数据即可。常规长BSR格式的截断BSR上报的是有缓存数据的LCG中优先级高的部分LCG的缓存数据量。常规长BSR格式的截断BSR中的BS字段的排列顺序可以是按照BS字段对应的LCG的优先级排列，即优先级较高的LCG对应的BS字段排在优先级较低的LCG对应的BS字段的前面。
示例性的，上述比特图占用一个字节，包括8位比特，8位比特中的每一位比特用于指示8个LCG中的每一个LCG是否有缓存数据，或者用于指示8个LCG中的每一个LCG对于的BS字段是否存在。上述一个或多个BS字段中的每一个BS字段占用一个字节，BS字段的值为LCG的缓存数据量范围的索引，用于间接指示LCG的缓存数据量范围。索引与LCG 的缓存数据量范围之间的映射关系如表2所示。如表2所示，BS值(BS value)表示缓存数据量范围，单位为字节，索引(Index)用于间接指示缓存数据量范围，一个索引对应一个缓存数据量范围，索引表示对应的BS字段的值。
表2
索引 BS值 索引 BS值 索引 BS值 索引 BS值
0 0 64 ≤560 128 ≤31342 192 ≤1754595
1 ≤10 65 ≤597 129 ≤33376 193 ≤1868488
2 ≤11 66 ≤635 130 ≤35543 194 ≤1989774
3 ≤12 67 ≤677 131 ≤37850 195 ≤2118933
4 ≤13 68 ≤720 132 ≤40307 196 ≤2256475
5 ≤14 69 ≤767 133 ≤42923 197 ≤2402946
6 ≤15 70 ≤817 134 ≤45709 198 ≤2558924
7 ≤16 71 ≤870 135 ≤48676 199 ≤2725027
8 ≤17 72 ≤926 136 ≤51836 200 ≤2901912
9 ≤18 73 ≤987 137 ≤55200 201 ≤3090279
10 ≤19 74 ≤1051 138 ≤58784 202 ≤3290873
11 ≤20 75 ≤1119 139 ≤62599 203 ≤3504487
12 ≤22 76 ≤1191 140 ≤66663 204 ≤3731968
13 ≤23 77 ≤1269 141 ≤70990 205 ≤3974215
14 ≤25 78 ≤1351 142 ≤75598 206 ≤4232186
15 ≤26 79 ≤1439 143 ≤80505 207 ≤4506902
16 ≤28 80 ≤1532 144 ≤85730 208 ≤4799451
17 ≤30 81 ≤1631 145 ≤91295 209 ≤5110989
18 ≤32 82 ≤1737 146 ≤97221 210 ≤5442750
19 ≤34 83 ≤1850 147 ≤103532 211 ≤5796046
20 ≤36 84 ≤1970 148 ≤110252 212 ≤6172275
21 ≤38 85 ≤2098 149 ≤117409 213 ≤6572925
22 ≤40 86 ≤2234 150 ≤125030 214 ≤6999582
23 ≤43 87 ≤2379 151 ≤133146 215 ≤7453933
24 ≤46 88 ≤2533 152 ≤141789 216 ≤7937777
25 ≤49 89 ≤2698 153 ≤150992 217 ≤8453028
26 ≤52 90 ≤2873 154 ≤160793 218 ≤9001725
27 ≤55 91 ≤3059 155 ≤171231 219 ≤9586039
28 ≤59 92 ≤3258 156 ≤182345 220 ≤10208280
29 ≤62 93 ≤3469 157 ≤194182 221 ≤10870913
30 ≤66 94 ≤3694 158 ≤206786 222 ≤11576557
31 ≤71 95 ≤3934 159 ≤220209 223 ≤12328006
32 ≤75 96 ≤4189 160 ≤234503 224 ≤13128233
33 ≤80 97 ≤4461 161 ≤249725 225 ≤13980403
34 ≤85 98 ≤4751 162 ≤265935 226 ≤14887889
35 ≤91 99 ≤5059 163 ≤283197 227 ≤15854280
36 ≤97 100 ≤5387 164 ≤301579 228 ≤16883401
37 ≤103 101 ≤5737 165 ≤321155 229 ≤17979324
38 ≤110 102 ≤6109 166 ≤342002 230 ≤19146385
39 ≤117 103 ≤6506 167 ≤364202 231 ≤20389201
40 ≤124 104 ≤6928 168 ≤387842 232 ≤21712690
41 ≤132 105 ≤7378 169 ≤413018 233 ≤23122088
42 ≤141 106 ≤7857 170 ≤439827 234 ≤24622972
43 ≤150 107 ≤8367 171 ≤468377 235 ≤26221280
44 ≤160 108 ≤8910 172 ≤498780 236 ≤27923336
45 ≤170 109 ≤9488 173 ≤531156 237 ≤29735875
46 ≤181 110 ≤10104 174 ≤565634 238 ≤31666069
47 ≤193 111 ≤10760 175 ≤602350 239 ≤33721553
48 ≤205 112 ≤11458 176 ≤641449 240 ≤35910462
49 ≤218 113 ≤12202 177 ≤683087 241 ≤38241455
50 ≤233 114 ≤12994 178 ≤727427 242 ≤40723756
51 ≤248 115 ≤13838 179 ≤774645 243 ≤43367187
52 ≤264 116 ≤14736 180 ≤824928 244 ≤46182206
53 ≤281 117 ≤15692 181 ≤878475 245 ≤49179951
54 ≤299 118 ≤16711 182 ≤935498 246 ≤52372284
55 ≤318 119 ≤17795 183 ≤996222 247 ≤55771835
56 ≤339 120 ≤18951 184 ≤1060888 248 ≤59392055
57 ≤361 121 ≤20181 185 ≤1129752 249 ≤63247269
58 ≤384 122 ≤21491 186 ≤1203085 250 ≤67352729
59 ≤409 123 ≤22885 187 ≤1281179 251 ≤71724679
60 ≤436 124 ≤24371 188 ≤1364342 252 ≤76380419
61 ≤464 125 ≤25953 189 ≤1452903 253 ≤81338368
62 ≤494 126 ≤27638 190 ≤1547213 254 >81338368
63 ≤526 127 ≤29431 191 ≤1647644 255 Reserved
针对IAB网络场景，在R16中将LCID字段拓展至16比特，在R17中将LCG的数量拓展至256。请参见图6，图6为本申请实施例提供的另一种BSR格式的结构示意图。图6所示的BSR格式可以称为拓展短BSR格式(Extended Short BSR format)，拓展短BSR格式的BSR用于上报一个LCG的缓存数据量，拓展短BSR格式的BSR包括一个LCGID字段和一个BS字段。上述LCGID字段用于指示LCG的标识，上述BS字段用于指示LCG的缓存数据量。拓展短BSR格式的BSR中的LCGID字段占用的比特数大于图4所示的常规短BSR格式的BSR中的LCGID字段所占用的比特数。示例性的，拓展短BSR格式的BSR占用两个字节，其中LCGID字段占用一个字节，使用8个比特来指示LCG的标识，可以指示标识在0到255之间的LCG的标识，因此拓展短BSR格式的BSR可以上报标识小于256的LCG的缓存数据量。上述BS字段占用一个字节，BS字段的值指示上报的LCG的缓存数据量范 围，其中LCG的缓存数据量范围和BS字段的值的映射关系如表2所示。
图6所示的BSR还可以称为拓展短截断BSR格式(Extended Short Truncated BSR format)，拓展短截断BSR格式的BSR用于上报有缓存数据的LCG中的一个LCG的缓存数据量，该LCG可以为有缓存数据的LCG中优先级最高的一个LCG的缓存数据量。在通信装置触发padding BSR且填充比特(padding bits)的数量只能够上报一个LCG的缓存数据量的情况下，通信装置使用拓展短截断BSR格式的BSR上报有缓存数据量的LCG中优先级最高的LCG的缓存数据量。
请参见图7，图7为本申请实施例提供的另一种BSR格式的结构示意图。图7所示的BSR格式可以称为拓展长BSR格式(Extended Long BSR format)，拓展长BSR格式的BSR用于上报一个或多个LCG的缓存数据量，该BSR包括一个比特图和一个或多个BS字段。上述比特图中的每一位比特用于指示一个LCG是否有缓存数据，或者用于指示一个LCG对应的BA字段是否存在，上述一个或多个BS字段中的每一个BS字段用于指示上述一个或多个LCG中的每一个LCG的缓存数据量。拓展长BSR格式的BSR中包含的BS字段的数量为BSR上报的LCG的数量，即图7中m为BSR上报的LCG的数量。
对于拓展长BSR格式的BSR，比特图中的每一位比特用于指示LCG对应的BS字段是否存在。比特图中可以包括多个LCGi字段，LCGi用于指示第i个LCG对应的BS字段是否存在。在拓展长BSR格式的BSR中，BS字段的数量等于有缓存数据的LCG的数量，LCGi字段还可以指示第i个LCG是否有缓存数据。当LCGi字段的值为1时，表示BSR中包括第i个LCG对应的BS字段存在，即第i个LCG有缓存数据；当LCGi字段的值为0时，表示BSR中第i个LCG对应的BS字段不存在，即第i个LCG没有缓存数据。应理解的是，比特图中的LCGi字段的值为1或0只是示例，不应对本申请构成限制，如LCGi字段的值可以2、3或4等均可以，只要在第i个LCG有缓存数据和第i个LCG没有缓存数据时，LCGi字段的取值不同，以使网络设备可以通过比特图中的LCGi字段的值确定对应的第i个LCG是否有缓存数据即可。上述一个或多个BS字段的排列顺序可以是按照对应的LCG的标识顺序排列，也可以是按照对应的LCG的优先级高低排列，即优先级较高的LCG对应的BS字段排在优先级较低的LCG对应的BS字段的前面。LCG的优先级根据其包含的LCH的优先级确定，将每个LCG包含的LCH中优先级最高的LCH的优先级作为其LCG的优先级。
图7所示的BSR格式还可以称为拓展长截断BSR格式(Extended Long Truncated BSR format)，拓展长截断BSR格式的BSR中比特图中的每一位用于指示对应的LCG是否有缓存数据。拓展长截断BSR格式的BSR用于上报所有有缓存数据的LCG的部分LCG的缓存数据量，并不是每个有缓存数据的LCG都上报，即并非每个有缓存数据的LCG都有对应的BS字段，因此在拓展长BSR格式的截断BSR中，LCGi字段用于指示第i个LCG是否有缓存数据。当LCGi字段的值为1时，表示第i个LCG有缓存数据；当LCGi字段的值为0时，表示第i个LCG没有缓存数据。应理解的是，比特图中的LCGi字段的值为1或0只是示例，不应对本申请构成限制，如LCGi字段的值可以2、3或4等均可以，只要在第i个LCG有缓存数据和第i个LCG没有缓存数据时，LCGi字段的取值不同，以使网络设备可以通过比特图中的LCGi字段的值确定对应的第i个LCG是否有缓存数据即可。拓展长截断BSR格式的BSR上报的是有缓存数据的LCG中优先级高的部分LCG的缓存数据量。拓展长截断BSR格式的BSR中的BS字段的排列顺序可以是按照BS字段对应的LCG的优先级排列，即优先级较高的LCG对应的BS字段排在优先级较低的LCG对应的BS字段的前面。
图7所示的BSR格式的BSR中的比特图中的比特数量大于图5所示的BSR格式的BSR 中的比特图中的比特数量。示例性的，图7所示的拓展长BSR格式的BSR中的比特图包括256位比特，256位比特中的每一位比特用于指示256个LCG中的每一个LCG是否有缓存数据，或者用于指示256个LCG中的每一个LCG对应的BS字段是否存在。上述一个或多个BS字段中的每个BS字段占用一个字节，用于指示一个LCG的缓存数据量范围，其中LCG的缓存数据量范围和BS字段的值的映射关系如表2所示。
使用图7所示的BSR格式上报BSR，每一次都需要上报一个比特图(bitmap)，用于指示对应的LCG是否有缓存数据，或者用于指示LCG对应的BS字段是否存在。当需要上报的LCG的数量较少时，如需上报的LCG的数量小于比特图所占用的字节数时，使用图7所示的BSR格式上报BSR会造成数据的浪费。为了提高资源的利用率，本申请实施例提供一种中等BSR格式(Extended Long BSR format*)。如图8a所示，中等BSR格式的BSR用于上报多个LCG的缓存数据量，中等BSR格式的BSR包括多个LCGID字段和多个BS字段。上述多个LCGID字段中的每一个LCGID字段用于指示一个LCG的标识，上述多个BS字段中的每一BS字段用于指示一个LCG的缓存数据量。上述多个LCGID字段与上述多个BS字段一一对应。上述多个LCG字段中的任一LCGID字段唯一指示一个LCG的标识，其对应的BS字段唯一指示该LCG的缓存数据量。示例性的，上述多个LCGID字段中的任一LCGID字段占用一个字节，用于指示一个LCG的标识，因此中等BSR格式的BSR可以上报标识在0至255之间的LCG的缓存数据量。上述多个BS字段中的任一BS字段占用一个字节，用于指示一个LCG的缓存数据量范围，LCG的缓存数据量范围和BS字段的值的映射关系如表2所示。如图8a所示，上述BSR格式可以依次多个LCGID字段和多个BS字段，其中，上述多个LCGID字段的排列顺序可以是基于LCGID字段所指示的LCG的优先级排列，即LCG ID 1对应的LCG的优先级高于其他的LCG的优先级。上述多个BS字段的排列顺序与上述LCGID字段的排列顺序相对应，即第i个BS字段指示的是第i个LCGID字段所指示的LCG的缓存数据量。如图8b所示，上述BSR格式可以依次包括LCGID1字段、BS1字段、LCGID2字段以及BS2字段。其中，LCGID1字段用于指示第一LCG的标识，BS1字段用于指示第一LCG的缓存数据量，LCGID2用于指示第二LCG的标识，BS2字段用于标识第二LCG的缓存数据量。图8b中各个LCG对应的LCGID字段和BS字段的排列顺序可以按照LCG的优先级排列，即上述第一LCG的优先级高于第二LCG的优先级。图8a所示的BSR格式与图8b所示的BSR格式的区别在于LCGID字段和BS字段的排列顺序。
图8a和图8b所示的BSR格式还可以称为中等截断BSR格式，中等截断BSR格式的BSR用于上报有缓存数据的LCG的部分LCG的缓存数据量。中等截断BSR格式的BSR上报的部分LCG可以为有缓存数据的LCG中优先级高的部分LCG。
本申请实施例提供一种BSR上报方法，能够有效利用图4到图8b所示的BSR格式合理上报BSR。图4到图8b所示的BSR格式仅为示例，本申请实施例中的BSR格式不限于图4到图8b所示的BSR格式。
请参见图9，图9为本申请实施例提供的一种通信方法的流程示意图。应理解，图9示出了通信方法的步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其他操作或者图9中的各个操作的变形。图9所示的通信方法应用于通信装置和网络设备之间的交互，图9所示的通信方法可以由通信装置执行。当通信装置中有缓存数据要上传时，执行图9所示的步骤生成BSR，将BSR发送至网络设备，向网络设备上报通信装置的缓存数据量，以便网络设备根据通信装置的缓存数据量为通信装置分配上行传输资源。本申请实施例中通 信装置为搭载了可用于指示计算机执行指令的处理器的设备，通信装置可以是终端设备，也可以是网络节点(例如IAB节点)。图9所示的通信方法可以用于IAB网络，终端设备执行图9所示的通信方法时，可以通过Uu链路向网络设备发送BSR。IAB节点执行图9所示的通信方法时，由IAB节点的MT部分执行，通过BH链路向该IAB节点的父节点发送BSR。如图9所示，该通信方法可以包括但不限于如下步骤：
901，基于第一标识和第一数值的比较结果确定目标缓存状态报告BSR格式，上述第一标识为有缓存数据的LCG的LCG标识中最大的LCG标识。
示例性的，上述第一数值的具体数值可以由网络设备设置，第一数值具体可以为7。通信装置可以根据第一标识和第一数值的比较结果从多种BSR格式中确定上报BSR使用的目标BSR格式。
示例性的，上述多种BSR格式中至少存在两种不同的BSR格式，这两种BSR格式的BSR能够上报的LCG的LCG标识的最大值不同，因此通信装置可以根据第一标识和第一数值比较结果从上述多种BSR格式中确定目标BSR格式。在上报的LCG的数量相同的情况下，上述两种BSR格式的BSR占用的比特数不同。
示例性的，上述第一数值可以等于上述多种BSR格式中的一种BSR格式能够上报的LCG的LCG标识的最大值。在第一标识小于或等于第一数值的情况下，通信装置将上述一种BSR格式确定为目标BSR格式。
示例性的，通信装置可以在满足BSR触发条件时执行步骤901，该BSR触发条件可以参考前述图3的相关描述。例如，该BSR触发条件包括缓存区，可理解，这里所示的触发条件仅为示例，在具体实现时，终端设备还可以根据其他触发条件触发执行步骤901。
902，根据目标BSR格式生成BSR。
示例性的，通信装置根据有缓存数据的LCG的标识和缓存数据量确定上述目标BSR格式中各个字段的取值，生成BSR。举例来说，目标BSR格式为如图5所示的常规长BSR格式的情况下，有缓存数据的LCG的数量为3，分别是LCG0，LCG2，LCG5有缓存数据，则生成的常规长BSR格式的BSR中的比特图中的第0位、第2位以及第五位为1，比特图的其他位为0。上述BSR中包括三个BS字段，这三个BS字段的值分别对应LCG0，LCG2，LCG5的缓存数据量范围的索引。通信装置生成的目标BSR格式的BSR包含在MAC PDU中。
在一种实施方式中，一个MAC PDU可以包括多个BSR。在通信装置生成MAC PDU时，若第一标识大于第一数值，即表明有缓存数据的LCG的LCG标识中存在至少一个LCG标识大于第一数值，通信装置可以使用两种BSR格式的BSR分别上报上述有缓存数据的LCG中LCG标识小于或等于第一数值的部分LCG和有缓存数据的LCG中LCG标识大于第一数值的部分LCG。
示例性的，通信装置可以使用第一格式的BSR上报有缓存数据的LCG中LCG标识大于第一数值的部分LCG的缓存数据量，使用第二格式的BSR格式的BSR上报有缓存数据的LCG中LCG标识小于或等于第一数值的LCG的缓存数据量。上述第一格式的BSR能够上报的LCG的LCG标识的最大值大于第二格式的BSR能够上报的LCG的LCG标识的最大值。上述第一数值可以等于第二格式的BSR能够上报的LCG的LCG标识的最大值。
在一种可能的实现方式中，图9所示的方法还包括：
903，向网络设备发送BSR。
通信装置通过MAC PDU将目标BSR格式的BSR发送至网络设备，向网络设备上报通信装置的缓存数据量，以便网络设备根据通信装置的缓存数据量确定为该通信装置分配的上 行传输资源的多少。
在本申请实施例中，通信装置可以根据第一标识与第一数值的比较结果，确定一个合适的BSR格式上报BSR，可以合理利用上行传输资源上报BSR，实现网络资源的精细化调度。
为更详细地理解图9所示的步骤901，本申请实施例还提供了如下几种实现方式：
实现方式一：
上述基于第一标识和第一数值的比较结果确定目标BSR格式，包括：
在第一标识大于第一数值的情况下，将第一格式确定为目标BSR格式，上述第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量；
在第一标识小于或等于第一数值的情况下，将第二格式确定为目标BSR格式，上述第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量。
上述第一标识阈值大于上述第二标识阈值。上述多个BSR格式可以包括第一格式和第二格式，第一格式的BSR与第二格式的BSR可以上报的LCG的LCG标识的标识范围不同。示例性的，通信装置可以根据第一标识确定需要上报的LCG的LCG标识所属的标识范围，确定该标识范围对应的目标BSR格式。
示例性的，上述第一数值可以等于上述第二格式的BSR能够上报的LCG的LCG标识的最大值，即上述第一数值可以等于上述第二标识阈值，第二格式的BSR无法上报LCG标识大于第一数值的LCG。在第一标识小于或等于第一数值的情况下，将第二格式确定为目标BSR格式。在第一标识大于第一数值的情况下，将第一格式确定为目标BSR格式。
示例性的，在上报相同数量的LCG的缓存数据量时，第一格式的BSR占用的比特数大于第二格式的BSR占用的比特数。第一格式的BSR中包括第一LCGID字段或者第一比特图，第一LCG字段用于指示上报的LCG的标识，上述第一比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个的LCG中的每一个LCG对应的缓存大小BS字段是否存在。第二格式的BSR中包括第二LCGID字段或者第二比特图，第二LCG字段用于指示上报的LCG的标识，上述第二比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个的LCG中的每一个LCG对应的缓存大小BS字段是否存在。其中，第一LCGID字段的比特数大于第二LCGID字段的比特数，第一比特图的比特数大于第二比特图的比特数。
在第一标识大于第一数值的情况下，有缓存数据的LCG的LCG标识大于第二标识阈值，第二格式的BSR无法上报LCG标识大于第二标识阈值的LCG的缓存数据量，因此使用第一格式的BSR上报上述有缓存数据的LCG的缓存数据量。在第一标识小于或等于第一数值的情况下，有缓存数据的LCG的LCG标识都小于或等于第二标识阈值，可以使用第二格式的BSR上报有缓存数据的LCG的缓存数据量。应该理解的是，在第一标识小于或等于第一数值的情况下，通信装置也可以使用第一格式的BSR上报有缓存数据的LCG的缓存数据量。在第一标识小于或等于第一数值，上报相同数量的LCG的缓存数据量的情况下，第一格式的BSR占用的比特数大于第二格式的BSR占用的比特数。
示例性的，上述第一标识阈值可以为255，第一格式的BSR可以上报LCG标识在0到255之间的LCG。上述第二标识阈值可以7，第二格式的BSR可以上报LCG标识在0到7之间的LCG。第一格式可以包括图6所示的拓展短BSR格式，图7所示的拓展长BSR格式，以及图8a或者图8b所示的中等BSR格式。第二格式可以包括图4所示的常规短BSR格式和图5所示的常规长BSR格式。在第一标识大于7的情况下，通信装置将第一格式确定为目 标BSR格式；在第一标识小于或等于7的情况下，通信装置将第二格式确定为目标BSR格式。
在本申请实施例中，上报相同数量的LCG时，第一格式的BSR的比特数大于第二格式的BSR，第二格式的BSR不能上报LCG标识大于第一数值的LCG。在第一标识大于第一数值的情况下，将第一格式确定为目标BSR格式；在第一标识小于或等于第一数值的情况下，将第二格式确定为目标BSR格式。在保证上报的有缓存数据的LCG的完整性的同时，节省上报BSR所需的比特数，提高资源的利用效率。
在一种实施方式中，通信装置还可以根据有缓存数据的LCG的数量确定第一格式或第二格式的具体格式。通信装置根据有缓存数据的LCG的数量确定第一格式的具体格式，可以包括如下步骤：
在有缓存数据的LCG的数量为1的情况下，上述第一格式或者第二格式为短BSR格式；
在有缓存数据的LCG的数量大于1且小于第二数值的情况下，上述第一格式或者第二格式为中等BSR格式；
在有缓存数据的LCG的数量大于或等于第二数值的情况下，上述第一格式或者第二格式的长BSR格式。
示例性的，上述短BSR格式的BSR用于上报一个LCG的缓存数据量，短BSR格式的BSR包括第一LCG的LCG标识和一个用于指示第一LCG的缓存数据量的指示信息。第一LCG为有缓存数据的一个LCG。上述短BSR格式。第二格式为短BSR格式时，第二格式的BSR用于上报LCG标识在第二标识阈值内的一个LCG的缓存数据量。第一格式为短BSR格式时，第一格式的BSR用于上报LCG标识在第一标识阈值内的一个LCG的缓存数据量。第一格式的BSR包括第一LCGID字段，第一LCGID字段用于指示上述一个LCG的标识。示例性的，第一格式为短BSR格式时，第一格式可以是如图6所示的拓展短BSR格式。第二格式的BSR包括第二LCGID字段，第二LCGID字段用于指示上述一个LCG的标识。第一格式和第二格式均为短BSR格式时，第一格式的BSR的比特数大于第二格式的BSR的比特数。上述第一LCGID字段的比特数大于上述第二LCGID的比特数。示例性的，第二格式为短BSR格式时，第二格式可以是如图4所示的常规短BSR格式。
上述中等BSR格式的BSR用于上报一个或多个LCG的缓存数据量。中等BSR格式的BSR包括至少一个LCG的LCG标识和用于指示上述至少一个LCG的缓存数据量的指示信息。上述至少一个LCG为有缓存数据的LCG中的至少一个LCG。第一格式为中等BSR格式时，第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量。第一格式的BSR包括至少一个LCGID字段。示例性的，第一格式为中等BSR格式时，第一格式可以是如图8a或图8b所示的中等BSR格式。第二格式为中等BSR格式时，第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量，第二格式的BSR包括至少一个LCGID字段。示例性的，第二格式的BSR中的至少一个LCGID字段中任一LCGID字段的比特数小于第一格式的BSR中的至少一个LCGID字段中的任一LCG字段的比特数。
上述长BSR格式的BSR用于上报一个或多个LCG的缓存数据量。上述长BSR格式的BSR包括第一比特图，第一比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否有缓存数据，或者用于指示至少一个LCG中的每一个LCG对应的缓存大小BS字段是否存在。上述至少一个LCG包括上述有缓存数据的LCG。示例性的，第一格式为长BSR格式时，第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量，第一格式的BSR包括第一比特图，示例性的，第一格式为长BSR格式时，第一格式可以是如图7 所示的拓展长BSR格式。第二格式为长BSR格式时，第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量，第二格式的BSR包括第二比特图，上述第二比特图的比特数小于上述第一比特图的比特数。示例性的，第二格式为长BSR格式时，第二格式可以是如图5所示的常规长BSR格式。
上述第二数值可以根据上述长BSR格式的BSR中的第一比特图占用的字节数确定。第二数值具体可以为长BSR格式的BSR中第一比特图占用的字节数。通信装置上报长BSR格式的BSR时，都需上报一个比特图，该比特图占用一定的比特数，当需上报的LCG的数量小于比特图占用的字节数时，会造成资源的浪费，因此在需上报的LCG的数量小于比特图占用的字节数时，通信装置上报中等BSR格式的BSR，可以节省上报BSR所需的比特数，提高资源的利用效率。
示例性的，在第二标识阈值为7的情况下，第二格式的BSR用于上报LCG标识在0到7之间的LCG的缓存数据量，上述第二比特图可以占用一个字节，第二数值的取值为1，因此不存在有缓存数据的LCG的数量小于第二数值的情况。因此在第二标识阈值为7的情况下，第二格式可以为短BSR格式或长BSR格式。在有缓存数据的LCG的数量为1的情况下，第二格式为短BSR格式；在有缓存数据的LCG的数量大于1的情况下，第二格式为长BSR格式。
下面以第一数值可以为7，第一标识阈值可以为255，第二标识阈值为7为例，对目标BSR格式的确定进行介绍，在不同情况下目标BSR格式的确定具体如下：
在第一标识大于第一数值，有缓存数据的LCG的数量为1的情况下，将拓展短BSR格式确定为目标BSR格式。
在第一标识大于第一数值，有缓存数据的LCG的数量大于1且小于32的情况下，将中等BSR格式确定为目标BSR格式。
在第一标识大于第一数值，有缓存数据的LCG的数量大于32的情况下，将拓展长BSR格式确定为目标BSR格式。
在第一标识小于或等于第一数值，有缓存数据的LCG的数量为1的情况下，将常规短BSR格式确定为目标BSR格式。
在第一标识小于或等于第一数值，有缓存数据的LCG的数量大于1的情况下，将常规长BSR格式确定为目标BSR格式。
在一种实施方式中，通信装置还可以根据填充比特的数量确定第一格式的具体格式。对于Padding BSR，通信装置可以根据第一标识和第一数值的比较结果，有缓存数据的LCG的数量以及填充比特的数值确定上报BSR使用的目标BSR格式。上述通信装置根据填充比特的数量确定第一格式的具体格式，可以包括如下几种情况：
情况一：在第一标识大于第一数值，有缓存数据的LCG的数量大于或等于第二数值的情况下，通信装置根据填充比特的数量确定第一格式的具体格式。
通信装置确定上述长BSR格式的BSR的大小，以及长BSR格式的BSR的MAC子头的大小。上述长BSR格式的BSR的大小为长BSR格式的BSR上报所有的有缓存数据的LCG时占用的比特数。将填充比特的数量与第六数值进行比较，上述第六数值为长BSR格式的BSR的大小加上长BSR格式的BSR的MAC子头的大小。在填充比特的数量大于或等于上述第六数值的情况下，第一格式为长BSR格式。
在填充比特的数量小于上述第六数值且大于或等于第四数值的情况下，第一格式为长截断BSR格式。示例性的，第四数值为中等BSR格式的BSR上报的LCG的数量等于第二数 值时占用的比特数。
在填充比特的数量小于第四数值且大于第三数值的情况下，上述第一格式为中等截断BSR格式。示例性的，第三数值根据上述第一格式的BSR的大小和所述第一格式的BSR的MAC子头的大小确定。例如，第三数值具体可以为第一格式的BSR上报一个LCG的缓存数据量时占用的比特数加上第一格式的MAC子头占用的比特数，即第三数值为通信装置要发送第一格式的BSR所需的最小比特数。
在填充比特的数量等于第三数值的情况下，第一格式为短截断BSR格式。填充比特的数量等于第三数值时，通信装置只能上报一个LCG的缓存数据量，因此第一格式为短截断BSR格式，以告知网络设备除了BSR上报的LCG外，通信装置还有其他的LCG存在缓存数据。短截断BSR格式的BSR用于上报有缓存数据的LCG中优先级高的LCG的缓存数据量。
在填充比特的数量小于第三数值的情况下，通信装置将第二格式确定为目标BSR格式。在有缓存数据的LCG的数量大于1，第一标识大于第一数值，且填充比特不足以上报第一格式的BSR的情况下，使用第二格式的BSR上报有缓存数据的LCG中LCG标识小于第一数值的LCG的缓存数据量。
情况二：在第一标识大于第一数值，有缓存数据的LCG的数量小于第二数值的情况下，通信装置根据填充比特的数量确定第一格式的具体格式。
通信装置确定中等BSR格式的BSR的大小，以及中等BSR格式的BSR的MAC子头的大小。将填充比特的数量与中等BSR格式的BSR的大小加上中等BSR格式的BSR的MAC子头的大小进行比较。在填充比特的数量大于或等于上述中等BSR格式的BSR的大小加上中等BSR格式的BSR的MAC子头的大小的情况下，上述第一格式为中等BSR格式。在填充比特的数量小于中等BSR格式的BSR的大小加上中等BSR格式的BSR的MAC子头的大小，且大于第三数值的情况下，第一格式为中等截断BSR格式。
在填充比特的数量等于第三数值的情况下，第一格式为短截断BSR格式。
在填充比特的数量小于第三数值的情况下，通信装置将第二格式确定为目标BSR格式。
情况三：在第一标识大于第一数值，有缓存数据的LCG的数量为1的情况下，
通信装置确定短BSR格式的BSR的大小，以及短BSR格式的BSR的MAC子头的大小。在填充比特的数量大于或等于第三数值的情况下，第一格式为短BSR格式。在填充比特的数量小于第三数值的情况下，将第二格式确定为目标BSR格式。第三数值为短BSR格式的BSR的大小加上短BSR格式的BSR的MAC子头的大小。
在本申请实施例中，对于Padding BSR，通信装置还可以根据填充比特的数量确定第一格式的具体格式，以保证通信装置能够利用填充比特上报生成的第一格式的BSR。
在另一种实施方式中，通信装置还可以根据填充比特的数量确定第二格式的具体格式。上述通信装置根据填充比特的数量确定第二格式的具体格式，可以包括如下几种情况：
情况一：在第一标识小于或等于第一数值，有缓存数据的LCG的数量大于或等于第二数值的情况下，通信装置根据填充比特的数量确定第二格式的具体格式。
通信装置确定上述长BSR格式的BSR所占用的比特数。在填充比特的数量大于或等于长BSR格式的BSR的大小加上长BSR格式的BSR的MAC子头的大小的情况下，第二格式为长BSR格式。
在填充比特的数量小于长BSR格式的BSR的大小加上长BSR格式的BSR的MAC子头的大小，且填充比特的数量大于或等于第七数值的情况下，第二格式为长截断BSR格式。示例性的，第七数值为中等BSR格式的BSR上报的LCG的数量等于上述第二数值时占用的比 特数。
在填充比特的数量小于第七数值且大于第五数值的情况下，上述第二格式为中等截断BSR格式。其中，第五数值根据上述短BSR格式的BSR以及短BSR格式的BSR的MAC子头的大小确定。示例性的，第五数值具体可以为短BSR格式的BSR的大小加上短BSR格式的BSR的MAC子头的大小，即第五数值为上报短BSR格式的BSR所需的比特数。
在填充比特的数量等于第五数值的情况下，第二格式为短截断BSR格式。填充比特的数量小于第五数值的情况下，通信装置只能使用短截断BSR格式上报一个LCG的缓存数据量。上述短截断BSR格式的BSR用于上报有缓存数据的LCG中优先级高的一个LCG的缓存数据量。
情况二：在第一标识小于或等于第一数值，有缓存数据的LCG的数量小于第二数值的情况下，通信装置根据填充比特的数量确定第二格式的具体格式。
通信装置确定中等BSR格式的BSR的大小，以及中等BSR格式的BSR的MAC子头的大小。将填充比特的数量与中等BSR格式的BSR的大小加上中等BSR格式的BSR的MAC子头的大小进行比较。在填充比特的数量大于或等于上述中等BSR格式的BSR的大小加上中等BSR格式的BSR的MAC子头的大小的情况下，上述第二格式为中等BSR格式。在填充比特的数量小于中等BSR格式的BSR的大小加上中等BSR格式的BSR的MAC子头的大小，且大于第五数值的情况下，第二格式为中等截断BSR格式。
在填充比特的数量等于第五数值的情况下，第二格式为常规短截断BSR格式。
情况三：在第一标识小于或等于第一数值，有缓存数据的LCG的数量为1的情况下，第二格式为短BSR格式。
在本申请实施例中，对于Padding BSR，通信装置还可以根据填充比特的数量确定第二格式的具体格式，以保证通信装置能够利用填充比特上报生成的第二格式的BSR。
实现方式二：
基于第一标识和第一数值的比较结果，以及填充比特的数量和第三数值的比较结果，确定上述目标BSR格式。
示例性的，上述第三数值可以根据通信装置可使用的多种BSR格式对应的BSR大小确定。例如，第三数值具体可以为上述多种BSR格式中一种BSR格式的BSR的大小加上其对应的MAC子头的大小，即第三数值为通信装置上报上述一种BSR格式的BSR所需的最小比特数。
对于Padding BSR，通信装置可以根据第一标识和第一数值的比较结果，以及填充比特的数量和第三数值的比较结果从多种BSR格式中确定上报BSR使用的目标BSR格式。上述多种BSR格式中至少存在两种不同的BSR格式，这两种BSR格式的BSR能够上报的LCG的LCG标识的最大值不同。在上报相同数量的LCG时，上述两种BSR格式的BSR的大小不同。因此通信装置可以根据第一标识和第一数值的比较结果，以及填充比特的数量与第三数值的比特结果确定上报BSR使用的目标BSR格式。
在一种实施方式中，上述基于第一标识和第一数值的比较结果，以及填充比特的数量和第三数值的比较结果，确定上述目标BSR格式，包括如下步骤：
在上述第一标识大于上述第一数值且填充比特的数量大于或等于第三数值的情况下，将第一格式确定为目标BSR格式；或者，
在上述第一标识大于上述第一数值且上述填充比特的数量小于上述第三数值的情况下， 将第二格式确定为上述目标BSR格式；上述第二格式的BSR用于上报有缓存数据的LCG中LCG标识小于上述第一数值的LCG的缓存数据量；或者，
在上述第一标识小于或等于上述第一数值的情况下，将上述第二格式确定为上述目标BSR格式。
上述多种BSR格式可以包括第一格式和第二格式。上述多个BSR格式可以包括第一格式和第二格式，第一格式的BSR与第二格式的BSR可以上报的LCG的标识范围不同。其中，上述第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量，第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量，其中第一标识阈值大于第二标识阈值。在上报相同数量的LCG的缓存数据量时，第一格式的BSR占用的比特数大于第二格式的BSR占用的比特数。通信装置需要利用填充比特发送BSR，因此需要确定根据目标BSR格式生成的BSR的大小加上其MAC子头的大小小于或等于填充比特的数量，以保证能够利用填充比特发送BSR。因此，通信装置可以根据第一标识和第一数值的比较结果，以及填充比特的数量和第三数值的比较结果从第一格式和第二格式中确定目标BSR格式。
示例性的，上述第一数值可以等于上述第二格式的BSR可以上报的LCG的LCG标识中最大的LCG标识，即上述第一数值可以等于上述第二标识阈值，第二格式的BSR无法上报LCG标识大于第一数值的LCG。
示例性的，上述第三数值根据上述第一格式的BSR的大小和所述第一格式的BSR的MAC子头的大小确定。例如第三数值具体可以为第一格式的BSR上报一个LCG的缓存数据量时所需的比特数，即第三数值为上报第一格式的BSR所需的最小比特数。在第一标识大于第一数值，且填充比特的数量大于或等于第三数值的情况下，通信装置能够利用填充比特发送第一格式的BSR，因此将第一格式确定为目标BSR格式，使用第一格式的BSR上报上述有缓存数据的LCG中的部分或全部LCG的缓存数据量。在第一标识大于第一数值，且填充比特的数量小于第三数值的情况下，填充比特不足以发送第一格式的BSR，因此通信装置将第二格式确定为目标BSR格式，利用第二格式的BSR上报有缓存数据的LCG中标识小于或等于第一数值的LCG的缓存数据量。在第一标识小于或等于第一数值的情况下，通信装置将第二格式确定为目标BSR格式，使用第二格式的BSR上报上述有缓存数据的LCG中的部分或全部LCG的缓存数据量。
在一种实施方式中，在第一标识大于第一数值，填充比特的数量大于或等于第三数值的情况下，确定有缓存数据的LCG中高优先级的LCG的LCG标识。在高优先级的LCG的LCG标识小于或等于第一数值的情况下，将第一格式和第二格式中能够上报LCG的数量多的格式确定为目标BSR格式。在有缓存数据的LCG中LCG标识小于或等于第一数值的LCG的数量大于第一格式的BSR能够上报的LCG的数量的情况下，将第二格式确定为目标格式；在有缓存数据的LCG中LCG标识小于或等于第一数值的LCG的数量小于第一格式的BSR能够上报的LCG的数量的情况下，将第一格式确定为目标BSR格式。
在一种实施方式中，通信装置可以根据填充比特的数量确定上述第一格式的具体格式。在填充比特的数量等于第三数值的情况下，上述第一格式为短BSR格式；或者，在填充比特的数量大于第三数值且小于第四数值的情况下，上述第一格式为中等BSR格式；或者，在填充比特的数量大于第四数值的情况下，上述第一格式为长BSR格式。
第一格式为长BSR格式时，第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量，第一格式的BSR包括第一比特图，上述第一比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个的LCG中的每一 个LCG对应的缓存大小BS字段是否存在。上述至少一个LCG的LCG标识在第一标识阈值内。示例性的，第一格式为长BSR格式时，第一格式可以是如图7所示的拓展长BSR格式。上述长BSR格式还可以理解为长截断BSR格式，在填充比特不足以上报所有的有缓存数据的LCG的缓存数据量的情况下，上述第一格式为长截断BSR格式。
第一格式为短BSR格式时，第一格式的BSR用于上报LCG标识在第一标识阈值内的一个LCG的缓存数据量。第一格式的BSR包括第一LCGID字段，第一LCGID字段用于指示上述一个LCG的标识。示例性的，第一格式为短BSR格式时，第一格式可以是如图6所示的拓展短BSR格式。上述短BSR格式还可以理解为短截断BSR格式，在填充比特不足以上报所有的有缓存数据的LCG的缓存数据量的情况下，上述第一格式为长截断BSR格式。
第一格式为中等BSR格式时，第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量。第一格式的BSR包括至少一个LCG的LCG标识和用于指示上述至少一个LCG的缓存数据量的指示信息。其中，上述至少一个LCG为上述有缓存数据的LCG中的至少一个LCG。示例性的，第一格式为中等BSR格式时，第一格式可以是如图8a或图8b所示的中等BSR格式。上述中等BSR格式还可以理解为中等截断BSR格式，在填充比特不足以上报所有的有缓存数据的LCG的缓存数据量的情况下，上述第一格式为中等截断BSR格式。
上述第四数值可以为长BSR格式的BSR和中等BSR格式的BSR上报的LCG的数量和占用的比特数都相同时，长BSR格式的BSR或者中等BSR格式的BSR占用的比特数，即当长BSR格式的BSR占用的比特数和中等BSR格式的BSR占用的比特数都为第四数值时，长BSR格式的BSR与中等BSR格式的BSR可以上报的LCG的数量相同。在中等BSR格式的BSR占用的比特数和长BSR格式占用的比特数相同且都小于第四数值时，中等BSR格式的BSR能够上报的LCG的数量大于长BSR格式能够上报的LCG的数量。在中等BSR格式的BSR占用的比特数和长BSR格式的BSR占用的比特数相同且都大于第四数值时，中等BSR格式的BSR能够上报的LCG的数量小于长BSR格式的BSR能够上报的LCG的数量。在填充比特的数量大于或等于第三数值且小于第四数值的情况下，中等BSR格式的BSR能够上报的LCG的数量大于长BSR格式的BSR能够上报的LCG的数量，通信装置将中等BSR格式确定为目标BSR格式。在填充比特的数量大于或等于第四数值的情况下，长BSR格式的BSR能够上报的LCG的数量大于中等BSR格式的BSR能够上报的LCG的数量，通信装置将长BSR格式确定为目标BSR格式。
在本申请实施例中，根据填充比特的数量确定第一格式的具体格式，选择合理的BSR格式上报，可以上报更多的LCG的缓存数据量。
在一种实施方式中，通信装置可以根据有缓存数据的LCG的数量确定上述第一格式的具体格式。通信装置根据有缓存数据的LCG的数量确定第一格式的具体格式，可以包括如下几种情况：
情况一：在第一标识大于第一数值，所述填充比特的数量等于上述第三数值的情况下，通信装置可以根据有缓存数据的LCG的数量确定上述第一格式的具体格式。
在有缓存数据的LCG的数量为1的情况下，上述第一格式为短BSR格式。在有缓存数据的LCG的数量大于1的情况下，第一格式为短截断BSR格式。
情况二：在第一标识大于第一数值，填充比特的数量大于第三数值且小于或等于第四数值的情况下，通信装置可以根据有缓存数据的LCG的数量确定上述第一格式的具体格式。
在有缓存数据的LCG的数量小于或等于第八数值的情况下，上述第一格式为中等BSR 格式；在有缓存数据的LCG的数量小于第八数值的情况下，上述第一格式为中等截断BSR格式。上述第八数值为中等BSR格式的BSR占用的比特数小于或等于上述填充比特的前提下，中等BSR格式的BSR能够上报的LCG的数量。
在一种实施方式中，为了节省资源，在有缓存数据的LCG的数量为1的情况下，上述第一格式可以为短BSR格式。
情况三：在第一标识大于第一数值，填充比特的数量大于或等于第四数值的情况下，通信装置可以进一步根据有缓存数据的LCG的数量确定第一格式的具体格式。
在有缓存数据的LCG的数量小于或等于第九数值的情况下，上述第一格式为长BSR格式；在有缓存数据的LCG的数量大于第九数值的情况下，上述第一格式为长截断BSR格式。上述第九数值为长BSR格式的BSR占用的比特数小于或等于填充比特的前提下，长BSR格式的BSR能够上报的LCG的数量。
在一种实施方式中，为了节省资源，在有缓存数据的LCG的数量为1的情况下，第一格式可以为短BSR格式。在有缓存数据的LCG的数量大于1小于第二数值的情况下，第一格式为中等BSR格式。在有缓存数据的数量大于第二数值的情况下，第一格式为长BSR格式或长截断BSR格式，在填充比特不足以上报全部有缓存数据的LCG的缓存数据量的情况下，第一格式为长截断BSR格式，长截断BSR格式的BSR用于上报有缓存数据的LCG中的部分LCG的缓存数据量。长截断BSR格式的BSR上报的部分LCG为上述有缓存数据的LCG中优先级高的部分LCG。
在一种实施方式中，通信装置可以根据填充比特的数量确定上述第二格式的具体格式。在填充比特的数量等于第五数值的情况下，上述第二格式为短BSR格式；在填充比特的数量大于第五数值的情况下，上述第二格式为长BSR格式。
第二格式为短BSR格式时，第二格式的BSR用于上报LCG标识在第二标识阈值内的一个LCG的缓存数据量。第二格式的BSR包括第二LCGID字段，第二LCGID字段用于指示上述一个LCG的标识。第一格式和第二格式均为短BSR格式时，第一格式的BSR的比特数大于第二格式的BSR的比特数。上述第一LCGID字段的比特数大于上述第二LCGID的比特数。示例性的，第二格式为短BSR格式时，第二格式可以是如图4所示的常规短BSR格式。上述短BSR格式还可以理解为短截断BSR格式，在填充比特的数量小于第五数值，填充比特不足以上报所有的有缓存数据的LCG的缓存数据量的情况下，上述第二格式为短截断BSR格式。
第二格式为长BSR格式时，第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量，第二格式的BSR包括第二比特图，上述第二比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个的LCG中的每一个LCG对应的缓存大小BS字段是否存在。上述至少一个LCG的LCG标识在第二标识阈值内。上述第二比特图的比特数小于上述第一比特图的比特数。示例性的，第二格式为长BSR格式时，第二格式可以是如图5所示的常规长BSR格式。上述长BSR格式还可以理解为长截断BSR格式，在填充比特不足以上报所有的有缓存数据的LCG的缓存数据量的情况下，上述第二格式为长截断BSR格式。
在一种实施方式中，通信装置可以根据有缓存数据的LCG的数量确定上述第二格式的具体格式。通信装置根据有缓存数据的LCG的数量确定第二格式的具体格式，可以包括如下几种情况：
情况一：在第一标识小于或等于第一数值，填充比特的数量小于第五数值的情况下，通 信装置可以根据有缓存数据的数量确定第二格式的具体格式。
在有缓存数据的LCG的数量为1的情况下，第二格式为短BSR格式；在有缓存数据的LCG的数量大于1的情况下，第二格式为短截断BSR格式。
情况二：在第一标识小于或等于第一数值，填充比特的数量大于或等于第五数值的情况下，通信装置可以根据有缓存数据的LCG的数量确定第二格式的具体格式。
在有缓存数据的LCG的数量小于或等于第十数值的情况下，上述第二格式为长BSR格式。在有缓存数据的LCG的数量大于第十数值的情况下，上述第二格式为长截断BSR格式。第十数值为长BSR格式的BSR占用的比特数小于或等于填充比特的前提下，长BSR格式的BSR能够上报的LCG的数量。
在一种实施方式中，为了节省资源，在有缓存数据的LCG的数量为1的情况下，第二格式为短BSR格式。
在该种实现方式中，根据第一标识和所述第一数值的比较结果，以及填充比特的数量和第三数值的比较结果，确定所述目标BSR格式，以选择合适的BSR格式上报有缓存数据的LCG的缓存数据量，能够合理利用上行资源上报BSR，实现网络资源的精细化调度。
实现方式三：
基于第一标识和第一数值的比较结果，以及有缓存数据的LCG的数量确定目标BSR格式。
示例性的，上述多种BSR格式中至少存在两种不同的BSR格式，这两种BSR格式的BSR能够上报的LCG的LCG标识的最大值不同，能够上报的LCG的数量也不同。通信装置可以根据第一标识和第一数值的比较结果以及填充比特的数量确定目标BSR格式。
举例来说，上述多种BSR格式中包括第一BSR格式，该第一BSR格式能够上报的LCG的LCG标识的最大值为7，能够上报的LCG的数量为8，若有缓存数据的LCG的数量为3，在有缓存数据的LCG的LCG标识中最大的LCG标识为5，通信装置将上述第一BSR格式确定为目标BSR格式。
在一种实施方式中，上述基于第一标识和第一数值的比较结果，以及有缓存数据的LCG的数量确定目标BSR格式，包括如下步骤：
在所述第一标识大于所述第一数值且有缓存数据的LCG的数量为1的情况下，将第一短BSR格式确定为所述目标BSR格式；或者，
在所述第一标识大于所述第一数值且所述有缓存数据的LCG的数量大于1且小于第二数值的情况下，将中等BSR格式确定为所述目标BSR格式；或者，
在所述第一标识大于所述第一数值且所述有缓存数据的LCG的数量大于或等于所述第二数值的情况下，将第一长BSR格式确定为所述目标BSR格式；或者，
在所述第一标识小于或等于所述第一数值且所述有缓存数据的LCG的数量为1的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，
在所述第一标识小于或等于所述第一数值且所述有缓存数据的LCG的数量大于1的情况下，将第二长BSR格式确定为所述目标BSR格式。
上述多种BSR格式可以包括第一长BSR格式、第一短BSR格式、中等BSR格式、第二长BSR格式以及第二短BSR格式。
上述第一长BSR格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量，第一长BSR格式的BSR包括第一比特图，上述第一比特图中的每一位比特用于指示至 少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个的LCG中的每一个LCG对应的缓存大小BS字段是否存在，上述至少一个LCG的LCG标识在第一标识阈值内。示例性的，上述第一长BSR格式可以是如图7所示的拓展长BSR格式。
上述第二长BSR格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量，第二长BSR格式的BSR包括第二比特图，上述第二比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个的LCG中的每一个LCG对应的缓存大小BS字段是否存在，上述至少一个LCG的LCG标识在第二标识阈值内。上述第一标识阈值大于上述第二标识阈值，上述第一比特图的比特数大于第二比特图的比特数。示例性的，上述第二长BSR格式可以是如图5所示的常规长BSR格式。
上述第一短BSR格式的BSR用于上报LCG标识在第一标识阈值内的一个LCG的缓存数据量。第一短BSR格式的BSR包括第一LCGID字段，第一LCGID字段用于指示上述一个LCG的标识。示例性的，上述第一短BSR格式可以是如图6所示的拓展短BSR格式。
上述第二短BSR格式的BSR用于上报LCG标识在第二标识阈值内的一个LCG的缓存数据量。第二短BSR格式的BSR包括第二LCGID字段，第二LCGID字段用于指示上述一个LCG的标识。上述第一LCGID字段的比特数大于上述第二LCGID的比特数。示例性的，上述第二短BSR格式可以是如图4所示的常规短BSR格式。
上述中等BSR格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量。中等BSR格式的BSR包括至少一个LCG的LCG标识和用于指示上述至少一个LCG的缓存数据量的指示信息。其中，上述至少一个LCG为上述有缓存数据的LCG中的至少一个LCG。示例性的，上述中等BSR格式可以是如图8a或图8b所示的中等BSR格式。
上述第一数值可以等于上述第二标识阈值，在第一标识小于或等于第一数值的情况下，通信装置可以使用第二长BSR格式的BSR或者第二短BSR格式的BSR上报有缓存数据的LCG中的部分或全部LCG的缓存数据量；在第一标识大于第一数值的情况下，通信装置可以使用第一长BSR格式的BSR或者第一短BSR格式的BSR或者中等BSR格式的BSR上报有缓存数量的LCG中的部分或全部LCG的缓存数据量。
上述第二数值可以根据上述第一长BSR格式的第一比特图占用的字节数确定。第二数值具体可以为长BSR格式中第一比特图占用的字节数。通信装置上报第一长BSR格式的BSR时，都需上报一个比特图，该比特图占用一定的比特数，当需上报的LCG的数量小于比特图占用的字节数时，会造成资源的浪费，因此在需上报的LCG的数量小于比特图占用的字节数时，通信装置使用上述中等BSR格式的BSR上报有缓存数据的LCG的缓存数据量，可以节省资源，合理利用资源。
在一种实施方式中，通信装置还可以根据填充比特的数量确定目标BSR格式。通信装置根据填充比特的数量确定目标BSR格式，可以包括如下几种情况：
情况一：在第一标识大于第一数值且有缓存数据的LCG的数量为1的情况下，通信装置可以根据填充比特的数量确定目标BSR格式。
在填充比特的数量大于或等于第三数值的情况下，将第一短BSR格式确定为目标BSR格式。
在填充比特的数量小于第三数值的情况下，说明填充比特不足以上报上述第一短BSR格式的BSR，通信装置不向网络设备上报BSR。示例性的，第三数值根据上述第一短BSR格式的BSR的大小和第一短BSR格式的BSR的MAC子头的大小确定。例如，第三数值具体可以为第一短BSR格式占用的比特数。
情况二：在第一标识大于第一数值且所述有缓存数据的LCG的数量大于1且小于第二数值的情况下，通信装置可以根据填充比特的数量确定目标BSR格式。
在填充比特的数量小于第三数值的情况下，确定上述有缓存数据的LCG是否有LCG标识小于或等于第一数值的LCG，若有缓存数据的LCG中有LCG标识小于或等于第一数值的LCG，则将第二短截断BSR格式确定为目标BSR格式，上述第二截断短BSR格式的BSR用于上报有缓存数据的LCG中LCG标识小于或等于第一数值的一个LCG的缓存数据量。
在填充比特的数量等于第三数值的情况下，将第一短截断BSR格式确定为目标BSR格式，上述第一短截断BSR格式的BSR用于上报有缓存数据的LCG中优先级高的一个LCG的缓存数据量。
在填充比特的数量大于第三数值的情况下，将中等BSR格式或中等截断BSR格式确定为目标BSR格式。在填充比特足以上报所有的有缓存数据的LCG的缓存数据量的情况下，将中等BSR格式确定为目标BSR格式，在填充比特不足以上报所有的有缓存数据的LCG的缓存数据量的情况下，将中等截断BSR格式确定为目标BSR格式，上述中等截断BSR格式的BSR用于上报有缓存数据的LCG中优先级高的LCG的缓存数据量。
情况三：在第一标识大于第一数值且有缓存数据的LCG的数量大于或等于第二数值的情况下，通信装置可以根据填充比特的数量确定目标BSR格式。
在填充比特的数量小于第三数值的情况下，确定上述有缓存数据的LCG是否有LCG标识小于或等于第一数值的LCG，若有缓存数据的LCG中有LCG标识小于或等于第一数值的LCG，则将第二短截断BSR格式确定为目标BSR格式，上述第二截断短BSR格式的BSR用于上报有缓存数据的LCG中LCG标识小于或等于第一数值的一个LCG的缓存数据量。
在填充比特的数量等于第三数值的情况下，将第一短截断BSR格式确定为目标BSR格式，上述第一短截断BSR格式的BSR用于上报有缓存数据的LCG中优先级高的一个LCG的缓存数据量。
在填充比特的数量大于第三数值且小于第四数值的情况下，将中等截断BSR格式确定为目标BSR格式。
在填充比特的数量大于或等于第三数值的情况下，将第一长BSR格式或第一长截断BSR格式确定为目标BSR格式。在填充比特足以上报所有的有缓存数据的LCG的缓存数据量的情况下，将第一长BSR格式确定为目标BSR格式；在填充比特不足以上报所有的有缓存数据的LCG的缓存数据量的情况下，将第一长截断BSR格式确定为目标BSR格式，上述第一长截断BSR格式的BSR用于上报有缓存数据的LCG中优先级高的LCG的缓存数据量。示例性的，上述第四数值可以为中等BSR格式的BSR上报的LCG的数量等于第二数值时占用的比特数。
情况四：在第一标识小于或等于第一数值且有缓存数据的LCG的数量大于1的情况下，通信装置可以根据填充比特的数量确定目标BSR格式。
在填充比特的数量等于第五数值的情况下，将第二短截断BSR格式确定为目标BSR格式，上述第二短截断BSR格式的BSR用于上报有缓存数据的LCG中优先级最高的一个LCG的缓存数据量。
在填充比特的数量大于或等于第五数值的情况下，将第二长BSR格式或第二长截断BSR格式确定为目标BSR格式。在填充比特足以上报所有的有缓存数据的LCG的缓存数据量的情况下，将第二长BSR格式确定为目标BSR格式；在填充比特不足以上报所有的有缓存数据的LCG的缓存数据量的情况下，将第二长截断BSR格式确定为目标BSR格式，上述第二 长截断BSR格式的BSR用于上报有缓存数据的LCG中优先级高的LCG的缓存数据量。示例性的，上述第五数值可以根据第二短BSR格式的BSR的大小和第二短BSR格式的BSR的MAC子头的大小确定。例如，第五数值具体可以等于第二短BSR格式的BSR的大小加上第二短BSR格式的BSR的MAC子头的大小，即第五数值为上报第二短BSR格式的BSR所需的比特数。
在该种实现方式中，根据第一标识和所述第一数值的比较结果，以及有缓存数据的LCG的数量，确定所述目标BSR格式，以选择合适的BSR格式上报有缓存数据的LCG的缓存数据量，能够合理利用上行资源上报BSR，实现网络资源的精细化调度。
实现方式四：
基于第一标识和第一数值的比较结果，有缓存数据的LCG的数量以及填充比特的数量确定目标BSR格式。
示例性的，对于Padding BSR，通信装置可以根据第一标识和第一数值的比较结果，有缓存数据的LCG的数量以及填充比特的数量从多种BSR格式中确定上报BSR使用的目标BSR格式。上述多种BSR格式中至少存在两种不同的BSR格式，这两种BSR格式的BSR能够上报的LCG的LCG标识的最大值不同，能够上报的LCG的数量不同。在上报相同数量的LCG时，上述两种BSR格式的BSR占用的比特数也不同。因此，通信装置可以根据第一标识和第一数值的比较结果，有缓存数据的LCG的数量以及填充比特的数量与第三数值的比特结果确定上报BSR使用的目标BSR格式。
示例性的，通信装置可以将有缓存数据的LCG的数量与多种BSR格式中任一种BSR格式的BSR能够上报的LCG的数量进行比较，将第一标识与上述多种BSR格式中的任一种BSR格式的BSR能够上报的LCG的LCG标识的最大值进行比较，以及将填充比特与上述多种BSR格式中任一种BSR格式的BSR占用的比特数进行比较，确定与有缓存数据的LCG相匹配的目标BSR格式，使得目标BSR格式的BSR能够上报有缓存数据的LCG中的部分或全部LCG的缓存数据量。
举例来说，上述多种BSR格式中包括第一BSR格式，该第一BSR格式能够上报的LCG的LCG标识的最大值为7，能够上报的LCG的数量为8，上报第一BSR格式所需的最小比特数为2字节。若有缓存数据的LCG数量为3，有缓存数据的LCG的LCG标识中的最大LCG标识为5，填充比特的数量为8字节的情况下，上述第一BSR格式与有缓存数据的LCG相匹配，因此，将第一BSR格式确定为目标BSR格式。
在一种实施方式中，上述基于第一标识和第一数值的比较结果，有缓存数据的LCG的数量以及填充比特的数量确定目标BSR格式，可以包括如下步骤：
在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量为1且所述填充比特的数量大于或等于第三数值的情况下，将第一短BSR格式确定为所述目标BSR格式；或者，
在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量等于所述第三数值的情况下，将所述第一短BSR格式确定为所述目标BSR格式；或者，
在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量小于所述第三数值的情况下，将第二短BSR格式确定为所述目标BSR格式，所述第二短BSR格式的BSR用于上报所述有缓存数据的LCG中LCG标识小于所述第一数值的LCG的缓存数据量；或者，
在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量大于所述第三数值且小于第四数值的情况下，将中等BSR格式确定为所述目标BSR格式；或者，
在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1且小于第二数值，且填充比特的数量大于所述第四数值的情况下，将所述中等BSR格式确定为目标BSR格式；或者，
在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于或等于所述第二数值，且所述填充比特的数量大于所述第四数值的情况下，将第一长BSR格式确定为所述目标BSR格式；或者，
在所述第一标识小于或等于所述第一数值，所述有缓存数量的LCG的数量为1的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，
在所述第一标识小于或等于所述第一数值，所述有缓存数量的LCG的数量大于1，且所述填充比特等于第五数值的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，
在所述第一标识小于或等于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特大于第五数值的情况下，将第二长BSR格式确定为所述目标BSR格式。
上述多种BSR格式可以包括第一长BSR格式，第一短BSR格式，中等BSR格式，第二长BSR格式，第二短BSR格式。
上述第一长BSR格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量，第一长BSR格式的BSR包括第一比特图，上述第一比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个的LCG中的每一个LCG对应的缓存大小BS字段是否存在，上述至少一个LCG的LCG标识在第一标识阈值内。示例性的，上述第一长BSR格式可以是如图7所示的拓展长BSR格式。
上述第二长BSR格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量，第二长BSR格式的BSR包括第二比特图，上述第二比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个的LCG中的每一个LCG对应的缓存大小BS字段是否存在，上述至少一个LCG的LCG标识在第二标识阈值内。上述第一标识阈值大于上述第二标识阈值，上述第一比特图的比特数大于第二比特图的比特数。示例性的，上述第二长BSR格式可以是如图5所示的常规长BSR格式。
上述第一短BSR格式的BSR用于上报LCG标识在第一标识阈值内的一个LCG的缓存数据量。第一短BSR格式的BSR包括第一LCGID字段，第一LCGID字段用于指示上述一个LCG的标识。示例性的，上述第一短BSR格式可以是如图6所示的拓展短BSR格式。
上述第二短BSR格式的BSR用于上报LCG标识在第二标识阈值内的一个LCG的缓存数据量。第二短BSR格式的BSR包括第二LCGID字段，第二LCGID字段用于指示上述一个LCG的标识。上述第一LCGID字段的比特数大于上述第二LCGID的比特数。示例性的，上述第二短BSR格式可以是如图4所示的常规短BSR格式。
上述中等BSR格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量。中等BSR格式的BSR包括至少一个LCG的LCG标识和用于指示上述至少一个LCG的缓存数据量的指示信息。其中，上述至少一个LCG为上述有缓存数据的LCG中的至少一个LCG。示例性的，上述中等BSR格式可以是如图8a或图8b所示的中等BSR格式。
示例性的，上述第一数值可以等于上述第二标识阈值。在第一标识小于或等于第一数值的情况下，通信装置可以使用第二长BSR格式的BSR或第二短BSR格式的BSR上报有缓存 数据的LCG中的部分或全部LCG的缓存数据量；在第一标识大于第一数值的情况下，通信装置可以使用第一长BSR格式的BSR，第一短BSR格式的BSR，或中等BSR格式的BSR上报有缓存数量的LCG中的部分或全部LCG的缓存数据量。
示例性的，上述第二数值可以根据上述第一长BSR格式的第一比特图占用的字节数确定。例如第二数值具体可以为长BSR格式中第一比特图占用的字节数。
示例性的，上述第三数值根据上述第一短BSR格式的BSR的大小和第一短BSR格式的BSR的MAC子头的大小确定。例如，第三数值具体可以为第一短BSR格式占用的比特数。
示例性的，上述第四数值为中等BSR格式上报的LCG数量等于第二数值时占用的比特数。
示例性的，上述第五数值根据上述第二短BSR格式的BSR的大小和上述第二短BSR格式对应的MAC子头的大小确定。例如，第五数值具体可以为第二短BSR格式的BSR占用的比特数加上第二短BSR格式的BSR的MAC子头占用的比特数，即第五数值为上报第二短BSR格式的BSR所需的比特数。
上述第一短BSR格式还可以理解为第一短截断BSR格式，上述第一长BSR格式还可以理解为第一长截断BSR格式，上述中等BSR格式还可以理解为中等截断BSR格式，上述第二长BSR格式还可以理解为第二长截断BSR格式，上述第二短BSR格式还可以理解为第二短截断BSR格式。
在第一标识大于第一数值，有缓存数据的LCG的数量为1，且填充比特的数量大于或等于第三数值的情况下，将第一短BSR格式确定为目标短BSR格式。
在第一标识大于第一数值，有缓存数据的LCG的数量大于1，且填充比特的数量等于第三数值的情况下，将第一短截断BSR格式确定为目标BSR格式。上述第一短截断BSR格式的BSR用于上报有缓存数据的LCG中优先级最高的一个LCG的缓存数据量。
在第一标识大于第一数值，有缓存数据的LCG的数量大于1，且填充比特的数量小于第三数值的情况下，填充比特不足以发送第一格式的BSR，因此将第二短截断BSR格式确定为目标BSR格式。上述第二短截断BSR格式的BSR用于上报所述有缓存数据的LCG中LCG标识小于第一数值的LCG的缓存数据量。
在第一标识大于第一数值，有缓存数据的LCG的数量大于1，且填充比特的数量大于第三数值且小于第四数值的情况下，确定中等BSR格式的BSR的大小，以及中等BSR格式的BSR的MAC子头的大小，若填充比特的数量大于或等于中等BSR格式的BSR的大小加上中等BSR格式的BSR的MAC子头的大小，则将中等BSR格式确定为目标BSR格式。若填充比特的数量小于中等BSR格式的BSR的大小加上中等BSR格式的BSR的MAC子头的大小，则将中等截断BSR格式确定为目标BSR格式。
在第一标识大于第一数值，有缓存数据的LCG的数量大于1且小于第二数值，且填充比特的数量大于或等于第四数值的情况下，将中等BSR格式确定为目标BSR格式。
在第一标识大于第一数值，有缓存数据的LCG的数量大于或等于第二数值，且填充比特的数量大于或等于第四数值的情况下，确定第一长BSR格式的BSR的大小，以及第一长BSR格式的BSR的MAC子头的大小，若填充比特的数量大于或等于第一长BSR格式的BSR的大小加上第一长BSR格式的BSR的MAC子头的大小，则将第一长BSR格式确定为目标BSR格式。若填充比特的数量小于第一长BSR格式的BSR的大小加上第一长BSR格式的BSR的MAC子头的大小，则将第一长截断BSR格式确定为目标BSR格式。
在第一标识小于或等于第一数值，有缓存数量的LCG的数量为1的情况下，将第二短 BSR格式确定为目标BSR格式。
在第一标识小于或等于第一数值，有缓存数量的LCG的数量大于1，且填充比特等于第五数值的情况下，将第二短截断BSR格式确定为目标BSR格式。
在第一标识小于或等于第一数值，有缓存数据的LCG的数量大于1，且填充比特大于第五数值的情况下，确定第二长BSR格式的BSR的大小，以及第二长BSR格式的BSR的MAC子头的大小，若填充比特的数量大于或等于第二长BSR格式的BSR的大小加上第二长BSR格式的BSR的MAC子头的大小，则将第二长BSR格式确定为目标BSR格式。若填充比特的数量小于第二长BSR格式的BSR的大小加上第二长BSR格式的BSR的MAC子头的大小，则将第二长截断BSR格式确定为目标BSR格式。
下面以第一长BSR格式为拓展长BSR格式，第一短BSR格式为拓展短BSR格式，第二长BSR格式为常规长BSR格式，第二短BSR格式为常规短BSR格式，第一数值为7，第一标识阈值为255，第二标识阈值为7为例，对上述基于第一标识和第一数值的比较结果，有缓存数据的LCG的数量以及填充比特的数量确定目标BSR格式进行介绍。在比较填充比特的数量与BSR的大小加上BSR的MAC的大小时，都需要考虑BSR的MAC子头的大小，因此，为了方便描述，以下情况中的填充比特可以理解为减去BSR对应的MAC子头的大小后剩余的比特。针对不同情况下下目标BSR格式的确定具体如下：
在有缓存数据的LCG的数量为1，第一标识小于或等于7，且填充比特的数量大于或等于1个字节的情况下，通信装置将常规短BSR格式确定为目标BSR格式。
在有缓存数据的LCG的数量为1，第一标识小于或等于7，且填充比特的数量大于或等于2个字节的情况下，通信装置将常规短BSR格式确定为目标BSR格式。应该理解的是，在有缓存数据的LCG的数量为1，第一标识小于或等于7且填充比特的数量大于或等于2个字段的情况下，通信装置也可以将拓展短BSR格式确定为目标BSR格式。
在有缓存数据的LCG的数量为1，第一标识大于7，且填充比特的数量大于或等于2个字节的情况下，通信装置将拓展短BSR格式确定为目标BSR格式。
在有缓存数据的LCG的数量大于1，第一标识小于或等于7，填充比特的数量大于或等于1个字节且小于2个字节的情况下，通信装置将常规短截断BSR格式确定为目标BSR格式，该常规短截断BSR格式的BSR用于上报有缓存数据的LCG中优先级最高的LCG的缓存数据量。
在有缓存数据的LCG的数量大于1，第一标识小于或等于7，且填充比特的数量等于2个字节的情况下，通信装置将常规长截断BSR格式确定为目标BSR格式。该常规长截断BSR格式的BSR用于上报上述有缓存数据的LCG中优先级最高的一个LCG的缓存数据量。
在有缓存数据的LCG的数量大于1，第一标识大于7，且填充比特的数量等于2字节的情况下，通信装置将拓展短截断BSR格式确定为目标BSR格式，该拓展短截断BSR格式的BSR用于上报有缓存数据的LCG中优先级最高的LCG的缓存数据量。
在有缓存数据的LCG的数量大于1，第一标识小于或等于7，且填充比特的数量大2字节且小于64字节的情况下，通信装置确定常规长BSR格式的BSR的大小以及常规长BSR格式的BSR的MAC子头的大小。在填充比特大于或等于常规长BSR格式的BSR的大小加上常规长BSR格式的BSR的MAC子头的大小的情况下，通信装置将常规长BSR格式确定为目标BSR格式。否则通信装置将常规长截断BSR格式确定为目标BSR格式。
在有缓存数据的LCG的数量大于1，第一标识大于7，且填充比特的数量大于2字节且小于或等于64字节的情况下，通信装置确定中等BSR格式的BSR的大小以及中等BSR格 式的BSR的MAC子头的大小。在填充比特大于或等于中等BSR格式的BSR的大小加上常规长BSR格式的BSR的MAC子头的大小的情况下，通信装置将中等BSR格式确定为目标BSR格式。否则通信装置将中等截断BSR格式确定为目标BSR格式。
在有缓存数据的LCG的数量大于1，且填充比特的数量大于9且小于16的情况下，若中等BSR格式的BSR和常规长BSR格式的BSR都不能上报所有的有缓存数据的LCG，通信装置确定有缓存数据的LCG中高优先级的LCG的LCG标识，在高优先级的LCG的LCG标识小于7的情况下，从中等截断BSR格式和常规长BSR格式中选择能够上报LCG的数量多的格式上报BSR。在有缓存数据的LCG中LCG标识小于7的LCG的数量大于使用中等截断BSR格式能够上报的LCG的数量的情况下，将常规长BSR格式确定为目标BSR格式；在有缓存数据的LCG中标识小于或等于7的LCG的数量小于使用中等截断BSR格式能够上报的LCG的数量的情况下，将中等截断BSR格式确定为目标BSR格式。举例来说，假设填充比特的数量为10，中等截断BSR格式的BSR可以上报5个LCG的缓存数据量，当有缓存数量的LCG中标识小于7的LCG的数量小于5，常规长BSR格式的BSR只能上报标识小于7的LCG的缓存数据量，因此常规长BSR格式的BSR能够上报的LCG的数量小于5，则通信装置将中等BSR格式确定为目标BSR格式；若有缓存数据的LCG中标识的LCG的数量大于5，则通信装置将常规长BSR格式确定为目标BSR格式。
在有缓存数据的LCG的数量大于1，第一标识小于或等于7，且填充比特的数量大于32字节的情况下，通信装置将常规长BSR格式确定为目标BSR格式。
在第一标识大于7，有缓存数据的LCG的数量大于1且小于32，填充比特的数量大于32字节的情况下，通信装置将中等BSR格式确定为目标BSR格式。
在第一标识大于7，有缓存数据的LCG的数量大于或等于32，且填充比特的数量大于32字节的情况下，通信装置将拓展长BSR格式或拓展长截断BSR格式确定为目标BSR格式。
在该种实现方式中，根据第一标识和第一数值的比较结果，有缓存数据的LCG的数量以及填充比特的数量确定目标BSR格式，以选择合适的BSR格式上报有缓存数据的LCG的缓存数据量，能够合理利用上行资源上报BSR，实现网络资源的精细化调度。
请参见图10，图10位本申请实施例提供的另一种通信方法的流程示意图。如图10所示，该通信方法包括但不限于如下步骤：
1001，基于第二标识与第一数值的比较结果确定目标缓存状态报告BSR格式，上述第二标识为通信装置被配置的LCG的LCG标识中最大的LCG标识。
示例性的，上述第一数值可以由网络设备设置，第一数值具体可以为7。
通信装置基于第二标识与第一数值的比较结果从多种BSR格式的确定目标BSR格式。示例性的，上述多种BSR格式中至少存在两种不同的BSR格式，这两种BSR格式的BSR能够上报的LCG的LCG标识的最大值不同，因此通信装置可以根据第一标识和第一数值比较结果从上述多种BSR格式中确定目标BSR格式。在上报的LCG的数量相同的情况下，上述两种BSR格式的BSR占用的比特数不同。
示例性的，上述第一数值可以等于上述多种BSR格式中的一种BSR格式能够上报的LCG的LCG标识的最大值。在第二标识小于或等于第一数值的情况下，通信装置将上述一种BSR格式确定为目标BSR格式。
示例性的，上述通信装置的LCG由网络设备配置，网络设备通过配置信息为通信装置配置LCG和LCH的对应关系。通信装置根据网络设备发送的配置信息确定该通信装置可使用 的LCG。
在一种实施方式中，上述基于第二标识与第一数值的比较结果确定目标BSR格式，包括：
在第二标识大于第一数值的情况下，将第一格式确定为目标BSR格式；
在第二标识小于或等于第一数值的情况下，将第二格式确定为目标BSR格式。
上述第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量，上述第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量，上述第一标识阈值大于上述第二标识阈值。上述多个BSR格式可以包括第一格式和第二格式，第一格式的BSR与第二格式的BSR可以上报的LCG的LCG标识的标识范围不同。示例性的，通信装置可以根据第一标识确定需要上报的LCG的LCG标识所属的标识范围，确定该标识范围对应的目标BSR格式。
示例性的，上述第一数值可以等于上述第二格式的BSR能够上报的LCG的LCG标识的最大值，即上述第一数值可以等于上述第二标识阈值，第二格式的BSR无法上报LCG标识大于第一数值的LCG。在第二标识小于或等于第一数值的情况下，将第二格式确定为目标BSR格式。在第二标识大于第一数值的情况下，将第一格式确定为目标BSR格式。
示例性的，在上报相同数量的LCG的缓存数据量时，第一格式的BSR占用的比特数大于第二格式的BSR占用的比特数。第一格式的BSR中包括第一LCGID字段或者第一比特图，第一LCG字段用于指示上报的LCG的标识，上述第一比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个的LCG中的每一个LCG对应的缓存大小BS字段是否存在。第二格式的BSR中包括第二LCGID字段或者第二比特图，第二LCG字段用于指示上报的LCG的标识，上述第二比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个的LCG中的每一个LCG对应的缓存大小BS字段是否存在。其中，第一LCGID字段的比特数大于第二LCGID字段的比特数，第一比特图的比特数大于第二比特图的比特数。
在第二标识大于第一数值的情况下，有缓存数据的LCG的LCG标识大于第二标识阈值，第二格式的BSR无法上报LCG标识大于第二标识阈值的LCG的缓存数据量，因此使用第一格式的BSR上报通信装置被配置的LCG的缓存数据量。在第二标识小于或等于第一数值的情况下，通信装置被配置的LCG的LCG标识都小于或等于第二标识阈值，可以使用第二格式的BSR上报通信装置被配置的LCG的缓存数据量。应该理解的是，在第二标识小于或等于第一数值的情况下，通信装置也可以使用第一格式的BSR上报通信装置被配置的LCG的缓存数据量。在第二标识小于或等于第一数值，上报相同数量的LCG的缓存数据量的情况下，第一格式的BSR占用的比特数大于第二格式的BSR占用的比特数。
示例性的，上述第一标识阈值可以为255，第一格式的BSR可以上报LCG标识在0到255之间的LCG。上述第二标识阈值可以7，第二格式的BSR可以上报LCG标识在0到7之间的LCG。第一格式可以包括图6所示的拓展短BSR格式，图7所示的拓展长BSR格式，以及图8a或者图8b所示的中等BSR格式。第二格式可以包括图4所示的常规短BSR格式和图5所示的常规长BSR格式。在第二标识大于7的情况下，通信装置将第一格式确定为目标BSR格式；在第二标识小于或等于7的情况下，通信装置将第二格式确定为目标BSR格式。
在一种实施方式中，通信装置可以根据有缓存数据的LCG的数量和填充比特的数量确定第一格式或第二格式的具体格式。
示例性的，上述通信装置根据有缓存数据的LCG的数量和填充比特的数量确定第一格式 或第二格式的具体格式的具体实施方式可以参考步骤901的实现方式一种的相关描述。
在本申请实施例中，在第二标识大于第一数值的情况下，将第一格式确定为目标BSR格式；在第二标识小于或等于第一数值的情况下，将第二格式确定为目标BSR格式。在保证上报的有缓存数据的LCG的完整性的同时，节省上报BSR所需的比特数，提高资源的利用效率。
1002，根据目标BSR格式生成BSR。
1003，向网络设备发送BSR。
其中，步骤1002和步骤1003的具体实施可以参见图9所示的步骤902和步骤903的具体描述，此处不再赘述。
在本申请实施例中，根据通信装置被配置的LCG的LCG标识确定一个格式的BSR格式为目标BSR格式，利用目标BSR格式上报BSR。根据通信装置的配置情况确定目标BSR格式，以使通信装置上报BSR使用的格式与通信装置的配置信息相匹配，可以合理上报BSR。
请参见图11，图11为本申请实施例提供的另一种通信方法的流程示意图。如图11所示，该通信方法包括但不限于如下步骤：
1101，基于通信装置被配置的LCG的数量与第一数值的比较结果确定目标缓存状态报告BSR格式。
示例性的，上述第一数值可以是协议规定的，也可以是网络设备配置的，第一数值具体可以为7。
通信装置基于该通信装置被配置的LCG的数量与第一数值的比较结果从多种BSR格式确定上报BSR使用的目标BSR格式。上述多种BSR格式中至少存在两种不同的BSR格式，这两种BSR格式的BSR能够上报的LCG的数量不同。
示例性的，上述第一数值可以为上述多种BSR格式中一种BSR格式的BSR能够上报的LCG的数量。在通信装置被配置的LCG的数量小于或等于第一数值的情况下，通信装置将上述一种BSR格式确定为目标BSR格式。
示例性的，上述通信装置的LCG由网络设备配置，网络设备通过配置信息为通信装置配置LCG和LCH的对应关系。通信装置根据网络设备发送的配置信息确定该通信装置可使用的LCG的数量。
在一种实施方式中，上述基于通信装置被配置的LCG的数量与第一数值的比较结果确定目标缓存状态报告BSR格式，包括：
在通信装置被配置的LCG的数量大于第一数值的情况下，将第一格式确定为目标BSR格式；
在通信装置被配置的LCG的数量小于或等于第一数值的情况下，将第二格式确定为目标BSR格式。
上述多种BSR格式可以包括第一格式和第二格式，上述第一格式的BSR和上述第二格式的BSR可以上报的LCG的数量不同。第一格式的BSR能够上报的LCG的数量为第一数量阈值，第二格式的BSR能够上报的LCG的数量为第二数量阈值，上述第一数量阈值大于上述第二数量阈值。在通信装置被配置的LCG的数量大于第二数量阈值的情况下，使用第二格式的BSR上报LCG的缓存数据量，会导致部分LCG的缓存数据量无法上报。为了保证每一个LCG的缓存数据量都能上报，在通信装置被配置的LCG的数量大于第二数量阈值的情况下，使用第一格式的BSR上报LCG的缓存数据量。
示例性的，上述第一数量阈值可以为256，上述第二数量阈值可以为8。第一格式可以包括图6所示的拓展短BSR格式，图7所示的拓展长BSR格式，以及图8a或者图8b所示的中等BSR格式。第二格式可以包括图4所示的常规短BSR格式和图5所示的常规长BSR格式。在通信装置被配置的LCG的数量大于8的情况下，通信装置将第一格式确定为目标BSR格式；在通信装置被配置的LCG的数量小于或等于8的情况下，通信装置将第二格式确定为目标BSR格式。
在一种实施方式中，通信装置可以根据有缓存数据的LCG的数量和填充比特的数量确定第一格式或第二格式的具体格式。
示例性的，上述通信装置根据有缓存数据的LCG的数量和填充比特的数量确定第一格式或第二格式的具体格式的具体实施方式可以参考步骤901的实现方式一种的相关描述。
在本申请实施例中，上报相同数量的LCG时，第一格式的BSR的比特数大于第二格式的BSR，第二格式的BSR不能上报LCG标识大于第一数值的LCG。在通信装置被配置的LCG的数量大于第一数值的情况下，将第一格式确定为目标BSR格式；在通信装置被配置的LCG的数量小于或等于第一数值的情况下，将第二格式确定为目标BSR格式。在保证上报的有缓存数据的LCG的完整性的同时，节省上报BSR所需的比特数，提高资源的利用效率。
1102，根据目标BSR格式生成BSR。
1103，向网络设备发送BSR。
其中，步骤1102和步骤1103的具体实施可以参见图9所示的步骤902和步骤903的具体描述，此处不再赘述。
在本申请实施例中，根据通信装置被配置的LCG的数量确定一个格式的BSR格式为目标BSR格式，利用目标BSR格式上报BSR。根据通信装置的配置情况确定目标BSR格式，以使通信装置上报BSR使用的格式与通信装置的配置信息相匹配，可以合理上报BSR。
图12为本申请实施例提供的一种IAB网络的BAP拓扑的示例。本申请中，BAP拓扑是指BAP层的拓扑。图12中，IAB2-MT和IAB2-DU为IAB节点2包括的两部分，IAB3-MT和IAB-DU3为IAB节点3包括的两部分。如图12所示，细线框中的拓扑表示受Donor-CU1控制的BAP拓扑1，例如位于BAP拓扑1中的IAB节点的BAP地址由Donor-CU1分配。粗线框中的拓扑表示受Donor-CU2控制的BAP拓扑2，例如，位于BAP拓扑2中的IAB节点的BAP地址由Donor-CU2分配。其中，BAP拓扑1包括IAB节点1、IAB节点2以及IAB节点3；BAP拓扑2包括IAB节点4。图12中，IAB节点2的MT，即IAB-MT2通过双连接分别连接至Donor-DU1和Donor-DU2。其中，IAB节点2的F1接口终结于CU1，即CU1是IAB节点2的F1-termination节点。针对这种BAP拓扑，可能会出现一个IAB节点的业务或者IAB节点下连接的UE的业务可经由几类不同的节点所传输。这几类不同的节点可能包含CU1所管理的IAB节点(例如IAB节点4)，CU2管理的IAB节点(例如，IAB节点3)。
如图12所示，IAB节点2可接收CU1经Donor-DU1和IAB节点1下发的数据包(参阅图12中的实线箭头表示的路径)，也可接收CU1经Donor-DU2和IAB节点3下发的数据包(参阅图12中的虚线箭头表示的路径)。IAB节点2为图12所示IAB网络中的边界节点。因为IAB节点2的F1接口终结于CU1(IAB节点2的DU终止于CU1)，IAB节点2的一个父节点(IAB节点3)的DU终止于CU2。
在双连接场景下：IAB节点2和宿主基站1(gNB1，包括CU1和Donor-DU1)之间存在Uu接口，IAB节点2和宿主基站2(gNB2，包括CU2和Donor-DU2)之间存在Uu接口。IAB 节点2和宿主基站1之间存在F1接口。IAB节点2和宿主基站1之间的F1接口通信既可以经过Donor DU1，也可以经过Donor DU2，也就是说，宿主基站1可以选择通过Donor DU1，和/或，Donor DU2，与IAB节点2进行F1接口通信。
该双连接场景既可能存在于IAB节点2进行跨宿主基站切换过程中，也可能存在于IAB节点2进行执行辅基站添加过程中。IAB节点2先与第一父节点(即IAB 1)建立连接，然后通过添加辅站的方式，与第二父节点(即IAB 4)建立连接，其中第一父节点连接到CU1，第二父节点连接到CU2。IAB节点2的DU部分连接到CU1，但其MT部分，同时接入到IAB节点1(具体是其DU部分)服务的小区和IAB节点4(具体是其DU部分)所服务的小区。IAB节点2的子节点和下属UE，都仍然与CU1之间保持连接关系(即当前粗线框部分的Donor DU2、IAB节点4由目标IAB宿主进行管理或控制，或者是属于在CU 2控制的网段，其他细线框部分由源IAB宿主节点的管理或控制，或者是属于在CU 1控制的网段。特殊的，由于IAB2-MT部分可以同时维护到两个不同宿主节点控制的父节点的双链接，则IAB2-MT既可以看做是属于源IAB宿主控制或管理的节点，例如IAB2-MT在与IAB节点1通信时可以看做是由源IAB宿主管理或控制的节点，或者说是属于在CU 1控制的网段；此外，IAB2-MT又可以看做是属于目标IAB宿主控制的网段，例如IAB2-MT在虚线双箭头所示的路径上，也可以和其他粗线框部分的节点一样可以看做是由目标IAB宿主的管理或控制，或者是属于在CU 2控制的网段。或者另一种可能的方式中，IAB2-MT可以看做是由维护其无线资源控制层(Radio Resource Control，RRC)连接的宿主节点所控制或管理的节点，或者属于维护其RRC连接的宿主节点所控制的网段，例如IAB2-MT的RRC连接是与CU 1之间维护的，则IAB2-MT所管理，可以看做是属于源IAB宿主控制或管理的节点)。因此，IAB节点2所服务的UE的业务，以及IAB节点3的业务(包括下属UE2和UE3的业务)都可以经由IAB节点2，以及IAB节点4和Donor DU2传输(参见图中的虚线双箭头指示的路径)。
请参见图13，图13为本申请实施例提供的另一种通信方法。所述方法应用于IAB网络的边界节点，IAB网络中的边界节点即位于第一BAP拓扑(例如上述BAP拓扑1)中，也位于第二BAP拓扑(例如上述BAP拓扑2)中。IAB网络中的边界节点可以具备以下特性：边界节点的DU终止于的IAB-donor-CU与其至少一个父节点的DU终止于的IAB-donor-CU不同。边界IAB节点(Boundary IAB node)的定义可以如下：IAB-node,whose IAB-DU is terminated to a different IAB-donor-CU than a parent DU。假定IAB网络中的一个IAB节点有两个父节点，该IAB节点的DU终止于IAB-donor 1的CU，该IAB节点的一个父节点的DU终止于IAB-donor 1的CU，该IAB节点的另一个父节点的DU终止于IAB-donor 2的CU，则该IAB节点为边界节点。所述方法包括如下步骤：
1301，IAB节点通过第一入口链路接收BAP数据包。
示例性的，上述IAB节点为IAB网络的边界节点。IAB节点的BAP实体的接收端通过第一入口链路接收BAP数据包。该BAP数据包具体可以为BAP data PDU。
示例性的，上述第一入口链路可以是ingress link，也可以是入口信道。上述第一入口链路可以对应有第一入口回传RLC信道(backhaul RLC channel，BH RLC CH)。
1302，IAB节点确定上述BAP数据包的目的地址与上述IAB节点的BAP地址是否匹配，上述IAB节点的BAP地址为与所述第一入口链路对应的BAP地址。
示例性的，上述第一入口链路对应的BAP地址可以理解为第一入口链路对应的基站为上述IAB节点配置的BAP地址。示例性的，上述IAB节点可以被配置多个BAP地址，上述IAB 节点可以连接至多个BAP拓扑，管理上述多个BAP拓扑的多个基站中的每一个基站为上述IAB节点分配一个BAP地址。IAB节点通过第一入口链路接收第一BAP拓扑发送的BAP数据包，上述第一BAP拓扑由第一基站管理。IAB节点从接收到的BAP数据包中解析出BAP数据包的目的地址，并将该目的地址与第一基站为上述IAB节点配置的BAP地址进行比较。若上述目的地址与第一基站为IAB节点配置的BAP地址相同，则确定上述BAP数据包的目的地址与上述IAB节点的BAP地址匹配。若不相同，则确定上述BAP数据包的目的地址与上述IAB节点的BAP地址不匹配。
示例性的，IAB节点可以双连接到第一BAP拓扑和第二BAP拓扑，第一BAP拓扑由第一基站(例如gNB1)管理，第二BAP拓扑由第二基站(例如gNB2)管理。第一入口链路用于接收来自上述第一BAP拓扑发送的BAP数据包，第二入口链路用于接收来自第二BAP拓扑的数据包。举例来说，gNB1为IAB节点配置的BAP地址为X，gNB2为IAB节点配置的BAP地址为Y。在IAB节点通过第一入口链路接收到BAP数据包的情况下，将gNB1为IAB节点配置的BAP地址X与BAP数据包中的目的地址进行比较，以判断是否匹配。在IAB节点通过第二入口链路接收到BAP数据包的情况下，将gNB2为IAB节点配置的BAP地址Y与BAP数据包中的目的地址进行比较，以判断是否匹配。
图12展示的IAB网络可以是图13中的方法适用的一种IAB网络的示例。其中，第一BAP拓扑对应于BAP拓扑1，第二BAP拓扑对应于BAP拓扑2，gNB1对应于CU1和Donor-DU1，gNB2对应于CU2和Donor-DU2，上述IAB节点对应于IAB节点2。
1303，在上述BAP数据包的目地址与上述BAP地址匹配的情况下，对所述BAP数据包进行处理。
示例性的，IAB节点可以将BAP数据包中的BAP头去掉，得到BAP SDU。将BAP SDU递交给IAB节点的BAP层的上层。
在本申请实施例中，IAB节点通过第一入口链路接收BAP数据包，并将BAP数据包的目的地址与IAB节点中与第一入口链路对应的BAP地址进行匹配，在上述BAP数据包的目地址与上述BAP地址匹配的情况下，对所述BAP数据包进行处理。防止错误处理BAP数据包，造成资源的浪费。
请参见图14，图14为本申请实施例提供的另一种通信方法。如图14所示，该通信方法包括：
1401，IAB节点通过第一入口链路接收BAP数据包。
其中，步骤1401的具体实施可以参见图13所示的步骤1301的具体描述，此处不再赘述。
1402，在上述BAP数据包的目的地址与上述IAB节点的BAP地址不匹配的情况下，上述IAB节点的MT侧确定上述第一入口链路是否为辅小区组(secondary cell group，SCG)与IAB节点之间的链路，以及确定上述IAB节点是否被配置多个BAP地址。
IAB节点通过第一入口链路接收到BAP数据包后，将BAP数据包中的目的地址与IAB节点的BAP地址进行比较，以判断是否匹配。在BAP数据包中的目的地址与IAB节点的BAP地址不匹配的情况下，说明上述BAP数据包不是发送给上述IAB节点的，需要IAB节点将其路由至正确路径上。示例性的，由IAB节点的MT侧确定上述BAP数据包的BAP头可能需要被重写，以将上述BAP数据包路由至正确路径。IAB节点的MT侧确定第一入口链路是否为SCG与IAB节点之间的链路，或者IAB节点的MT侧确定第一入口链路是否为处于SCG中的IAB节点与辅基站直接的空口无线链路。在IAB节点的MT侧确定第一入口链路为SCG 与IAB节点之间的链路的情况下，说明上述BAP来自辅基站。在第一入口链路为SCG与IAB节点之间的链路的情况下，IAB节点的MT侧确定上述IAB节点是否被配置了多个BAP地址。在IAB节点被配置了多个BAP地址的情况下，确定上述BAP数据包的BAP头可能需要被重写。
示例性的，上述IAB节点可以双连接至第一BAP拓扑和第二BAP拓扑，第一BAP拓扑由第一基站(如gNB1)管理，第二BAP拓扑由第二基站(如gNB2)管理。入口链路1用于接收上述第一BAP拓扑发送的BAP数据包，入口链路2用于接收第二BAP拓扑发送的数据包。其中，gNB1可以作为IAB节点的主基站的角色，gNB2可以作为辅基站的角色。IAB节点的MT侧确定第一入口链路为SCG与IAB节点之间的链路，可以确定上述BAP数据包来自与第二BAP拓扑。在IAB节点被配置两个BAP地址的情况下，说明IAB节点可以连接到两个拓扑。在上述BAP数据包的目的地址与上述IAB节点的BAP地址不匹配的情况下，说明上述BAP数据包不是发给该IAB节点的，需要IAB节点将其路由至正确路径。在IAB节点接收到的BAP数据包由第二BAP拓扑发送，且不是发送给该IAB节点的情况下，IAB节点需要将BAP数据包的BAP头重写后发给子节点，以使IAB节点的子节点能够识别该BAP数据包。
图12展示的IAB网络可以是图14中的方法适用的一种IAB网络的示例。其中，第一BAP拓扑对应于BAP拓扑1，第二BAP拓扑对应于BAP拓扑2，gNB1对应于CU1和Donor-DU1，gNB2对应于CU2和Donor-DU2，上述IAB节点对应于IAB节点2。
在一些实施方式中，步骤1402可替换为：在上述BAP数据包的目地址与上述IAB节点的BAP地址不匹配的情况下，上述IAB节点的DU侧确定上述IAB节点是否被配置了多个BAP地址。在IAB节点的DU侧确定上述IAB节点被配置了多个BAP地址的情况下，确定上述BAP数据包的BAP头可能需要被重写。
示例性的，在BAP数据包中的目的地址与IAB节点的BAP地址匹配的情况下，去掉BAP数据包的BAP头，得到BAP SDU，将BAP SDU递交至BAP层的上层。
1403，在IAB节点的MT侧确定上述第一入口链路为SCG与IAB节点之间的链路以及上述IAB节点被配置了多个BAP地址的情况下，确定上述BAP数据包的BAP头可能需要被重写。
确定上述BAP数据包的BAP头可能需要被重写，也可以理解为确定执行BAP头重写判断流程。
在一种实施方式中，BAP头重写判断流程可以为：检查上述BAP数据包的第一BAP路由标识是否匹配改写表(rewriting table)，即判断第一BAP路由标识是否可以进行rewriting；若匹配，则基于rewriting table将第一BAP路由标识改写为第二BAP路由标识。若第一BAP路由标识不匹配rewriting table，则将第一数据包递交给第一IAB节点的BAP节点的上层。rewriting table可以包含一组或多组BAP路由标识映射关系，每组BAP路由标识映射关系用于将IAB节点不可识别的一种BAP路由标识(即第二BAP拓扑内的IAB节点可识别的BAP路由标识)映射为该IAB节点可识别的BAP路由标识(即第一BAP拓扑内的IAB节点可识别的BAP路由标识)。检查BAP数据包的第一BAP路由标识是否匹配rewriting table可以是：查询rewriting table中是否包含第一BAP路由标识与其他BAP路由标识的映射关系。基于rewriting table将第一BAP路由标识改写为第二BAP路由标识可以是：基于rewriting table获取与第一BAP路由标识存在BAP路由标识映射关系的第二BAP路由标识。
表3为本申请提供的一个rewriting table的示例。参阅表3，第一列为原始BAP路由标识， 第二列为改写后的BAP路由标识。应理解，第一列中的各原始BAP路由标识为第二BAP拓扑内的IAB节点可识别的BAP路由标识。或者说，第一列中的各原始BAP路由标识对应于来自属于第二BAP拓扑的下行数据包(例如BAP数据包)的BAP路由标识。第二列中的改写后的BAP路由标识为IAB节点可识别的BAP路由标识。表1中，每一行的原始BAP路由标识对应于该行中改写后的BAP路由标识。例如，第一行中的第一BAP路由标识对应于第一行中的第二BAP路由标识。举例来说，第一BAP路由标识可查询表1的第一列是否包含第一BAP路由标识；若是，则第一BAP路由标识匹配rewriting table；若否，则第一BAP路由标识不匹配rewriting table。在该举例中，若表1的第一列包含第一BAP路由标识，则获取与第一BAP路由标识存在映射关系的第二BAP路由标识。
表3
原始BAP路由标识 改写后的BAP路由标识
第一BAP路由标识 第二BAP路由标识
第三BAP路由标识 第四BAP路由标识
… …
第(N)BAP路由标识 第(N+1)BAP路由标识
在一些实施方式中，上述步骤1403可替换为：在IAB节点的DU侧确定上述IAB节点被配置了多个BAP地址的情况下，确定上述BAP数据包的BAP头可能需要被重写。在IAB节点被配置了多个BAP地址的情况下，IAB节点接收BAP数据的入口链路和发送该BAP节点的出口链路可能不是同一个BAP拓扑，因此上述BAP数据包的BAP头可能需要被重写。确定上述BAP数据包的BAP头可能需要被重写，也可以理解为确定执行BAP头重写判断流程。
1404，在IAB节点的MT侧确定上述第一入口链路不为SCG或者上述IAB节点只被配置了一个BAP地址的情况下，确定不对上述BAP数据包的BAP头重写。
在IAB节点的MT侧确定上述第一入口链路不为SCG的情况下，说明BAP数据包来自主基站，则确定不需要对BAP数据包的BAP头重写。在IAB节点只被配置了一个BAP地址的情况下，说明IAB节点只与一个BAP拓扑连接，则确定不需要对BAP数据包的BAP头重写。
在本申请实施例中，可以由IAB节点的MT侧或IAB节点的DU侧确定是否需要将BAP数据包的BAP头重写，以使IAB节点接收到的BAP数据包路由至正确路径。
上述详细阐述了本申请实施例的方法，下面提供了本申请实施例的装置。
请参见图15，图15是本申请实施例提供的一种通信装置的结构示意图。该通信装置150可以实现上述各个方法实施例的功能或者步骤。该通信装置可以包括处理模块1501和收发模块1502。可选的，还可以包括存储单元，该存储单元可以用于存储指令(代码或者程序)和/或数据。处理模块1501和收发模块1502可以与该存储单元耦合，例如，处理模块1501可以读取存储单元中的指令(代码或者程序)和/或数据，以实现相应的方法。上述各个单元可以独立设置，也可以部分或者全部集成。例如收发模块1502可包括发送模块和接收模块。
处理模块1501，用于支持该通信装置执行步骤901、步骤902、步骤1001、步骤1002、步骤1101以及步骤1102，和/或用于本文所描述的技术的其它过程。
收发模块1502，用于支持该通信装置与其他通信装置之间的通信，例如，支持接入该通信装置执行步骤903、步骤1003以及步骤1103，和/或用于本文所描述的技术的其它过程。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
请参见图16，图16为本申请实施例提供的另一种通信装置160的结构示意图。其中，通信装置160能够实现本申请实施例提供的方法。其中，该通信装置160可以为芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
在硬件实现上，上述收发模块1502可以为收发器，收发器集成在通信装置160中构成通信接口1601。
通信装置160包括至少一个处理器1602，用于实现或用于支持通信装置160实现本申请实施例提供的方法。具体参见方法示例中的详细描述，此处不做赘述。
通信装置160还可以包括至少一个存储器1603，用于存储程序指令和/或数据。存储器1603和处理器1602耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1602可能和存储器1603协同操作。处理器1602可能执行存储器1603中存储的程序指令和/或数据，以使得通信装置160实现相应的方法。所述至少一个存储器中的至少一个可以包括于处理器中。
通信装置160还可以包括通信接口1601，用于通过传输介质和其它设备进行通信，从而用于通信装置160中的装置可以和其它设备进行通信。示例性地，当通信装置160为IAB节点时，该其它设备为其他IAB节点或终端设备。处理器1602可以利用通信接口1601收发数据。通信接口1601具体可以是收发器。
本申请实施例中不限定上述通信接口1601、处理器1602以及存储器1603之间的具体连接介质。本申请实施例在图16中以存储器1603、处理器1602以及通信接口1601之间通过总线1604连接，总线在图16中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请实施例中，处理器1602可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器1603可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
应理解，通信装置160为IAB节点时，图17示出了通信装置160的另一种形式。图17中，通信装置170是IAB节点，应理解，IAB节点包括CU和DU，CU可包括通信接口、处理器以及存储器，以及连接通信接口、处理器以及存储器的总线，其中通信接口可用于与IAB宿主节点的CU或IAB节点的DU进行通信。DU也可包括通信接口、处理器以及存储器， 以及连接通信接口、处理器以及存储器的总线，其中通信接口用于与IAB节点的MT进行通信。
图18为本申请实施例提供的另一种通信装置180的结构示意图。如图18所示，图18所示的通信装置180包括逻辑电路1801和接口1802。图15中的处理模块可以用逻辑电路1801实现，图15中的收发模块可以用接口1802实现。其中，该逻辑电路1801可以为芯片、处理电路、集成电路或片上系统(system on chip，SoC)芯片等，接口1802可以为通信接口、输入输出接口等。本申请实施例中，逻辑电路和接口还可以相互耦合。对于逻辑电路和接口的具体连接方式，本申请实施例不作限定。
在本申请的一些实施例中，该逻辑电路和接口可用于执行上述图9至图11所示的方法。
本申请实施例还提供一种芯片系统，所述芯片系统包括至少一个处理器，存储器和接口电路，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述至少一个存储器中存储有计算机程序；所述计算机程序被所述处理器执行时，图9至图11所示的方法流程得以实现。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，当其在通信装置上运行时，图9至图11所示的方法流程得以实现。
本申请实施例还提供一种计算机程序产品，当所述计算机程序产品在通信装置上运行时，图9至图11所示的方法流程得以实现。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来计算机程序相关的硬件完成，该计算机程序可存储于计算机可读取存储介质中，该计算机程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储计算机程序代码的介质。

Claims (30)

  1. 一种通信方法，其特征在于，包括：
    基于第一标识和第一数值的比较结果确定目标缓存状态报告BSR格式，其中，所述第一标识为有缓存数据的逻辑信道组LCG的LCG标识中最大的LCG标识；
    根据所述目标BSR格式生成BSR。
  2. 根据权利要求1所述的方法，其特征在于，所述基于第一标识和第一数值的比较结果确定目标BSR格式，包括：
    在所述第一标识大于所述第一数值的情况下，将第一格式确定为所述目标BSR格式，所述第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量；
    在所述第一标识小于或等于所述第一数值的情况下，将第二格式确定为所述目标BSR格式，所述第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量；
    其中，所述第一标识阈值大于所述第二标识阈值。
  3. 根据权利要求2所述的方法，其特征在于，在所述有缓存数据的LCG的数量为1的情况下，所述第一格式或者第二格式为短BSR格式；或者，
    在所述有缓存数据的LCG的数量大于1且小于第二数值的情况下，所述第一格式或者第二格式为中等BSR格式；或者，
    在所述有缓存数据的LCG的数量大于或等于所述第二数值的情况下，所述第一格式或者第二格式为长BSR格式。
  4. 根据权利要求3所述的方法，其特征在于，所述长BSR格式的BSR包括第一比特图，所述第一比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个LCG中的每一个LCG对应的缓存大小BS字段是否存在。
  5. 根据权利要求3所述的方法，其特征在于，所述中等BSR格式的BSR包括至少一个LCG的LCG标识，和用于指示所述至少一个LCG的缓存数据量的指示信息。
  6. 根据权利要求3所述的方法，其特征在于，所述短BSR格式的BSR包括第一LCG的LCG标识，和一个用于指示所述第一LCG的缓存数据量的指示信息。
  7. 根据权利要求1所述的方法，其特征在于，所述基于第一标识和第一数值的比较结果确定目标BSR格式，包括：
    基于所述第一标识和所述第一数值的比较结果，以及填充比特的数量和第三数值的比较结果，确定所述目标BSR格式。
  8. 根据权利要求7所述的方法，其特征在于，所述基于所述第一标识和所述第一数值的比较结果，以及填充比特的数量和第三数值的比较结果，确定所述目标BSR格式，包括：
    在所述第一标识大于所述第一数值且填充比特的数量大于或等于第三数值的情况下，将第一格式确定为所述目标BSR格式；或者，
    在所述第一标识大于所述第一数值且所述填充比特的数量小于所述第三数值的情况下， 将第二格式确定为所述目标BSR格式；所述第二格式的BSR用于上报所述有缓存数据的LCG中LCG标识小于所述第一数值的LCG的缓存数据量；或者，
    在所述第一标识小于或等于所述第一数值的情况下，将所述第二格式确定为所述目标BSR格式。
  9. 根据权利要求8所述的方法，其特征在于，在所述填充比特的数量等于所述第三数值的情况下，所述第一格式为短BSR格式；或者，
    在所述填充比特的数量大于所述第三数值且小于第四数值的情况下，所述第一格式为中等BSR格式；或者，
    在所述填充比特的数量大于或等于所述第四数值的情况下，所述第一格式为长BSR格式。
  10. 根据权利要求7-9任一项所述的方法，其特征在于，所述第三数值根据所述第一格式的BSR的大小和所述第一格式的BSR的媒体介入控制MAC子头的大小确定。
  11. 根据权利要求1所述的方法，其特征在于，所述基于第一标识和第一数值的比较结果确定目标BSR格式，包括：
    基于所述第一标识和所述第一数值的比较结果，以及所述有缓存数据的LCG的数量确定所述目标BSR格式。
  12. 根据权利要求11所述的方法，其特征在于，所述基于所述第一标识和所述第一数值的比较结果，以及所述有缓存数据的LCG的数量确定所述目标BSR格式，包括：
    在所述第一标识大于所述第一数值且有缓存数据的LCG的数量为1的情况下，将第一短BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识大于所述第一数值且所述有缓存数据的LCG的数量大于1且小于第二数值的情况下，将中间BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识大于所述第一数值且所述有缓存数据的LCG的数量大于或等于所述第二数值的情况下，将第一长BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识小于或等于所述第一数值且所述有缓存数据的LCG的数量为1的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识小于或等于所述第一数值且所述有缓存数据的LCG的数量大于1的情况下，将第二长BSR格式确定为所述目标BSR格式。
  13. 根据权利要求1所述的方法，其特征在于，所述基于第一标识和第一数值的比较结果确定目标BSR格式，包括：
    基于所述第一标识和所述第一数值的比较结果，所述有缓存数据的LCG的数量以及填充比特的数量确定所述目标BSR格式。
  14. 根据权利要求13所述的方法，其特征在于，所述基于所述第一标识和所述第一数值的比较结果，所述有缓存数据的LCG的数量以及填充比特的数量确定所述目标BSR格式，包括：
    在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量为1且所述填充比特 的数量大于或等于第三数值的情况下，将第一短BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量等于所述第三数值的情况下，将所述第一短BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量小于所述第三数值的情况下，将第二短BSR格式确定为所述目标BSR格式，所述第二短BSR格式的BSR用于上报所述有缓存数据的LCG中LCG标识小于所述第一数值的LCG的缓存数据量；或者，
    在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特的数量大于所述第三数值且小于第四数值的情况下，将中等BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于1且小于第二数值，且填充比特的数量大于所述第四数值的情况下，将所述中等BSR格式确定为目标BSR格式；或者，
    在所述第一标识大于所述第一数值，所述有缓存数据的LCG的数量大于或等于所述第二数值，且所述填充比特的数量大于所述第四数值的情况下，将第一长BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识小于或等于所述第一数值，所述有缓存数量的LCG的数量为1的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识小于或等于所述第一数值，所述有缓存数量的LCG的数量大于1，且所述填充比特等于第五数值的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识小于或等于所述第一数值，所述有缓存数据的LCG的数量大于1，且所述填充比特大于第五数值的情况下，将第二长BSR格式确定为所述目标BSR格式。
  15. 根据权利要求14所述的方法，其特征在于，所述第五数值根据所述第二短BSR格式的BSR的大小和所述第二短BSR格式对应的MAC子头的大小确定。
  16. 根据权利要求1-15任一项所述的方法，其特征在于，所述第一数值为7。
  17. 一种通信装置，其特征在于，包括：
    处理模块，用于基于第一标识和第一数值的比较结果确定目标缓存状态报告BSR格式，其中，所述第一标识为有缓存数据的逻辑信道组LCG的LCG标识中最大的LCG标识；
    所述处理模块，还用于根据所述目标BSR格式生成BSR；
    收发模块，用于向网络设备发送所述BSR。
  18. 根据权利要求17所述的装置，其特征在于，所述处理模块，具体用于在所述第一标识大于所述第一数值的情况下，将第一格式确定为所述目标BSR格式，所述第一格式的BSR用于上报LCG标识在第一标识阈值内的LCG的缓存数据量；在所述第一标识小于或等于所述第一数值的情况下，将第二格式确定为所述目标BSR格式，所述第二格式的BSR用于上报LCG标识在第二标识阈值内的LCG的缓存数据量；其中，所述第一标识阈值大于所述第二标识阈值。
  19. 根据权利要求18所述的装置，其特征在于，在所述有缓存数据的LCG的数量为1的情况下，所述第一格式或者第二格式为短BSR格式；或者，
    在所述有缓存数据的LCG的数量大于1且小于第二数值的情况下，所述第一格式或者第二格式为中等BSR格式；或者，
    在所述有缓存数据的LCG的数量大于或等于所述第二数值的情况下，所述第一格式或者第二格式为长BSR格式。
  20. 根据权利要求19所述的装置，其特征在于，所述长BSR格式的BSR包括第一比特图，所述第一比特图中的每一位比特用于指示至少一个LCG中的每一个LCG是否存在缓存数据，或者用于指示至少一个LCG中的每一个LCG对应的缓存大小BS字段是否存在。
  21. 根据权利要求19所述的装置，其特征在于，所述中等BSR格式的BSR包括至少一个LCG的LCG标识，和用于指示所述至少一个LCG的缓存数据量的指示信息。
  22. 根据权利要求19所述的装置，其特征在于，所述短BSR格式的BSR包括第一LCG的LCG标识，和一个用于指示所述第一LCG的缓存数据量的指示信息。
  23. 根据权利要求17所述的装置，其特征在于，所述处理模块，具体用于基于所述第一标识和所述第一数值的比较结果，以及填充比特的数量和第三数值的比较结果，确定所述目标BSR格式。
  24. 根据权利要求23所述的装置，其特征在于，所述处理模块，具体用于所述第一标识大于所述第一数值且填充比特的数量大于或等于第三数值的情况下，将第一格式确定为所述目标BSR格式；或者，
    在所述第一标识大于所述第一数值且所述填充比特的数量小于所述第三数值的情况下，将第二格式确定为所述目标BSR格式；所述第二格式的BSR用于上报所述有缓存数据的LCG中LCG标识小于所述第一数值的LCG的缓存数据量；或者，
    在所述第一标识小于或等于所述第一数值的情况下，将所述第二格式确定为所述目标BSR格式。
  25. 根据权利要求24所述的装置，其特征在于，在所述填充比特的数量等于所述第三数值的情况下，所述第一格式为短BSR格式；或者，
    在所述填充比特的数量大于所述第三数值且小于第四数值的情况下，所述第一格式为中等BSR格式；或者，
    在所述填充比特的数量大于或等于所述第四数值的情况下，所述第一格式为长BSR格式。
  26. 根据权利要求23-25任一项所述的装置，其特征在于，所述第三数值根据所述第一格式的BSR的大小和所述第一格式的BSR的媒体介入控制MAC子头的大小确定。
  27. 根据权利要求17所述的装置，其特征在于，所述处理模块，具体用于基于所述第一 标识和所述第一数值的比较结果，以及所述有缓存数据的LCG的数量确定所述目标BSR格式。
  28. 根据权利要求27所述的装置，其特征在于，所述处理模块，具体用于在所述第一标识大于所述第一数值且有缓存数据的LCG的数量为1的情况下，将第一短BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识大于所述第一数值且所述有缓存数据的LCG的数量大于1且小于第二数值的情况下，将中间BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识大于所述第一数值且所述有缓存数据的LCG的数量大于或等于所述第二数值的情况下，将第一长BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识小于或等于所述第一数值且所述有缓存数据的LCG的数量为1的情况下，将第二短BSR格式确定为所述目标BSR格式；或者，
    在所述第一标识小于或等于所述第一数值且所述有缓存数据的LCG的数量大于1的情况下，将第二长BSR格式确定为所述目标BSR格式。
  29. 一种通信装置，其特征在于，所述通信装置包括处理器和存储器；
    所述存储器中存储有计算机程序；
    所述处理器执行所述计算机程序时，所述计算设备执行前述权利要求1-16中任一所述的方法。
  30. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当所述指令在至少一个处理器上运行时，实现如权利要求1-16中任一项所述的方法。
PCT/CN2022/120864 2021-10-21 2022-09-23 通信方法、装置以及存储介质 WO2023065965A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22882576.6A EP4408064A1 (en) 2021-10-21 2022-09-23 Communication method and apparatus, and storage medium
US18/641,114 US20240276291A1 (en) 2021-10-21 2024-04-19 Communication method and apparatus, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111229686.8A CN116017556A (zh) 2021-10-21 2021-10-21 通信方法、装置以及存储介质
CN202111229686.8 2021-10-21

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/641,114 Continuation US20240276291A1 (en) 2021-10-21 2024-04-19 Communication method and apparatus, and storage medium

Publications (1)

Publication Number Publication Date
WO2023065965A1 true WO2023065965A1 (zh) 2023-04-27

Family

ID=86019768

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/120864 WO2023065965A1 (zh) 2021-10-21 2022-09-23 通信方法、装置以及存储介质

Country Status (4)

Country Link
US (1) US20240276291A1 (zh)
EP (1) EP4408064A1 (zh)
CN (1) CN116017556A (zh)
WO (1) WO2023065965A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108702248A (zh) * 2018-05-21 2018-10-23 北京小米移动软件有限公司 缓存状态报告的格式的设置方法和装置
CN109565897A (zh) * 2017-06-16 2019-04-02 Oppo广东移动通信有限公司 传输信息的方法和设备
WO2020116820A1 (en) * 2018-12-05 2020-06-11 Lg Electronics Inc. Method and apparatus for transmitting buffer status report by wireless node in wireless communication system
CN111314957A (zh) * 2017-09-21 2020-06-19 Oppo广东移动通信有限公司 传输信息的方法和设备
CN111757517A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种缓冲区状态报告传输方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109565897A (zh) * 2017-06-16 2019-04-02 Oppo广东移动通信有限公司 传输信息的方法和设备
CN111314957A (zh) * 2017-09-21 2020-06-19 Oppo广东移动通信有限公司 传输信息的方法和设备
CN108702248A (zh) * 2018-05-21 2018-10-23 北京小米移动软件有限公司 缓存状态报告的格式的设置方法和装置
WO2020116820A1 (en) * 2018-12-05 2020-06-11 Lg Electronics Inc. Method and apparatus for transmitting buffer status report by wireless node in wireless communication system
CN111757517A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种缓冲区状态报告传输方法及装置

Also Published As

Publication number Publication date
CN116017556A (zh) 2023-04-25
US20240276291A1 (en) 2024-08-15
EP4408064A1 (en) 2024-07-31

Similar Documents

Publication Publication Date Title
WO2020038172A1 (zh) 一种流量控制的方法及装置
US11265755B2 (en) Communication methods, apparatuses, and systems for managing quality of service flows
WO2020164615A1 (zh) 一种通信方法及相关设备
US11496923B2 (en) Data transmission method and apparatus used in wireless backhaul network
WO2020088253A1 (zh) 用于无线回传网络的数据传输方法和装置
WO2019029643A1 (zh) 通信方法、基站、终端设备和系统
EP2445250A1 (en) Data packet sending, receiving and transmission method and device
CN110121867A (zh) 一种传输数据包的方法、发送设备及接收设备
WO2020200024A1 (zh) 通信方法和通信装置
JP2009284479A (ja) バッファ状態報告を実行する方法及び通信装置
CN110365609B (zh) 一种数据包分段方法、及装置
WO2020221296A1 (zh) 数据传输的方法和装置
WO2021056589A1 (zh) 一种数据传输方法及装置
WO2020147056A1 (zh) 用于复制数据传输的方法和设备
CN107786464B (zh) 一种实现节点间通信的方法及装置
WO2021168632A1 (zh) 中继方法、路由表的生成方法、装置、设备及存储介质
WO2020082948A1 (zh) 一种数据传输方法及装置
WO2023065965A1 (zh) 通信方法、装置以及存储介质
WO2020199034A1 (zh) 用于中继通信的方法和装置
WO2022151021A1 (zh) 缓存状态上报的方法、缓存状态上报的配置方法及装置
WO2021062717A1 (zh) 一种缓冲区状态报告传输方法及装置
WO2023011111A1 (zh) 路由方法和通信装置
WO2014000611A1 (zh) 传输数据的方法和装置
US20240080710A1 (en) Communication control method
WO2024207313A1 (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: 22882576

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022882576

Country of ref document: EP

Effective date: 20240426

NENP Non-entry into the national phase

Ref country code: DE