WO2023124928A1 - 信息传输方法、设备和存储介质 - Google Patents

信息传输方法、设备和存储介质 Download PDF

Info

Publication number
WO2023124928A1
WO2023124928A1 PCT/CN2022/138293 CN2022138293W WO2023124928A1 WO 2023124928 A1 WO2023124928 A1 WO 2023124928A1 CN 2022138293 W CN2022138293 W CN 2022138293W WO 2023124928 A1 WO2023124928 A1 WO 2023124928A1
Authority
WO
WIPO (PCT)
Prior art keywords
buffered data
data size
bsr
lcg
communication node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/138293
Other languages
English (en)
French (fr)
Inventor
沙秀斌
戴博
陆婷
谈杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CA3244994A priority Critical patent/CA3244994A1/en
Priority to KR1020247025881A priority patent/KR20240137593A/ko
Priority to EP22914183.3A priority patent/EP4460136A4/en
Publication of WO2023124928A1 publication Critical patent/WO2023124928A1/zh
Priority to US18/759,627 priority patent/US20240357419A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • 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/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • 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
    • 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
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • 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 communication field, for example, to an information transmission method, device and storage medium.
  • the traffic volume of the uplink service is reported through the Buffer Status Report (BSR).
  • BSR Buffer Status Report
  • the traffic volume identification part adopts 5 bits or 8 bits.
  • the service cache of NR terminals is relatively large, and the range of service volume values is also relatively large, for example, from 0 to 81338368 Bytes. It is difficult to accurately represent the service volume between 0 and 81338368 Bytes with 5 bits or 8 bits.
  • the traffic volume reported by the BSR is inaccurate, resulting in inaccurate resource scheduling of the base station, resulting in waste of wireless resources.
  • An embodiment of the present application provides an information transmission method, including:
  • a buffer status report (BSR) is reported based on the parameters related to the size report of the buffered data volume.
  • An embodiment of the present application provides an information transmission method applied to a second communication node, including:
  • An embodiment of the present application provides an information transmission device, including: a communication module, a memory, and one or more processors;
  • the communication module is configured to communicate and interact with other communication nodes
  • the memory configured to store one or more programs
  • the one or more processors When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the foregoing embodiments.
  • An embodiment of the present application provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of the foregoing embodiments is implemented.
  • FIG. 1 is a flowchart of an information transmission method provided in an embodiment of the present application
  • Fig. 2 is a flow chart of another information transmission method provided by the embodiment of the present application.
  • Figure 3 is a short buffer included in the same Media Access Control Packet Data Unit (MAC PDU) or the same Transmission Time Interval (Transmission Time Interval, TTI) provided by the embodiment of the present application
  • MAC PDU Media Access Control Packet Data Unit
  • TTI Transmission Time Interval
  • Schematic diagram of the configuration of the status report media access control layer-control unit Short Buffer Status Report Mediu Access Control-Control Element, Short BSR MAC CE
  • Figure 4 is a long buffer status report media access control layer-control element (Long Buffer Status Report Mediau Access Control-Control Element, Long BSR MAC CE contained in the same MAC PDU or the same TTI provided by the embodiment of the present application. ) configuration diagram;
  • FIG. 5 is a schematic configuration diagram of a Long BSR MAC CE provided by an embodiment of the present application.
  • FIG. 6 is a schematic configuration diagram of another Long BSR MAC CE provided by the embodiment of the present application.
  • FIG. 7 is a schematic configuration diagram of another Long BSR MAC CE provided by the embodiment of the present application.
  • FIG. 8 is a structural block diagram of an information transmission device provided by an embodiment of the present application.
  • FIG. 9 is a structural block diagram of another information transmission device provided by an embodiment of the present application.
  • Fig. 10 is a schematic structural diagram of an information transmission device provided by an embodiment of the present application.
  • Table 1 is a schematic table of the values of the buffered data size level table in a BSR provided by the embodiment of the present application
  • Table 2 is a schematic value table of the buffered data size level table in another BSR provided by the embodiment of the application .
  • Table 1 illustrates the value range of the traffic volume using 5 bits for the traffic size identifier
  • Table 2 illustrates the value range of the traffic volume using 8 bits for the traffic size ID.
  • the embodiment of the present application provides an information transmission method, which can selectively configure the used buffer data size level table to indicate or determine the used buffer data size level table according to the information characteristics of the service to be transmitted, or use multiple buffers The value of the data volume, so that the UE can accurately report the traffic volume.
  • FIG. 1 is a flowchart of an information transmission method provided in an embodiment of the present application.
  • This embodiment can be executed by an information transmission device.
  • the information transmission device may be the first communication node.
  • the first communication node is a terminal side (for example, user equipment).
  • this embodiment includes: S110-S120.
  • the parameters related to the buffered data size report include at least one of the following: the buffered data size level table indication used, the BSR reporting type indication, the BSR format indication, and the indication supporting a specific BSR reporting method;
  • the parameters related to the data size report are configured by the second communication node through broadcast signaling or UE-specific signaling.
  • the used buffered data size level table indication is used to indicate the buffered data size level table adopted by the first communication node.
  • the BSR report type indication is used to indicate the type or granularity of the BSR report value;
  • the BSR format indication is used to indicate which buffer status report the BSR uses to report the media access control layer-control element (Buffer Status Report Media Access Control-Control Element, BSR MAC CE) format for reporting; support for an indication of a specific BSR reporting method, used to indicate whether the second communication node supports a predefined BSR reporting method such as the same MAC PDU or the same TTI containing K BSR MAC CEs.
  • K is a positive integer.
  • the second communication node configures the buffered data size level table indication, BSR reporting type indication, BSR format indication, or indication of supporting a specific BSR reporting method adopted by the first communication node through broadcast signaling or UE-specific signaling , in a manner of reporting the size of buffered data used to indicate to the first communication node. If the second communication node does not indicate to the first communication node, the first communication node uses Table 1 to report the BSR by default.
  • the service to be transmitted before receiving or determining the parameters related to the buffered data size report used by the service to be transmitted, it further includes: indicating to the second communication node the characteristics of the traffic volume information corresponding to the service to be transmitted.
  • the service volume information feature is used to characterize the attribute of the service to be transmitted.
  • the service volume information feature includes at least one of the following: service volume value range; application layer service type; desired buffer data size level table; desired BSR report type indication; desired BSR format instruct.
  • the application layer service types may include: interactive low-rate services, video streaming or file download services, and the like.
  • the desired buffered data size level table refers to one or more buffered data size level tables that can be adopted by the first communication node. It can be understood that multiple buffered data size level tables can be configured according to the application layer service type.
  • the buffered data volume size level table expected to be used includes three tables, which are respectively the buffered data volume size level table corresponding to the traffic volume value range of 5 bits shown in Table 1, and the interaction type small rate Table of buffered data volume size level table corresponding to business and buffered data volume size level table corresponding to video stream or file download business.
  • the desired BSR report type indication is used to indicate the type or granularity of the expected BSR report value; the expected BSR format indication is used to indicate which BSR MAC CE format the expected BSR uses for reporting.
  • the service to be transmitted is indicated to the second communication node at the granularity of a logical channel (Logical Channel, LC), a logical channel group (Logical Channel Group, LCG) or a dedicated radio bearer (Dedicated Radio Bearer, DRB) Quantitative information features.
  • a logical channel Logical Channel, LC
  • a logical channel group Logical Channel Group, LCG
  • a dedicated radio bearer Dedicated Radio Bearer, DRB
  • the first communication node reports the BSR at the granularity of LC or DRB; reporting the BSR at the granularity of LC or DRB includes: BSR MAC CE contains a logical channel identifier (Logical Channel identifier, LC ID) or a dedicated radio bearer identifier (Dedicated Radio Bearer identifier, DRB ID).
  • BSR MAC CE contains a logical channel identifier (Logical Channel identifier, LC ID) or a dedicated radio bearer identifier (Dedicated Radio Bearer identifier, DRB ID).
  • the granularity of the BSR reported by the first communication node is the same as the granularity of the buffered data size level table indicated by the second communication node.
  • the first communication node when the second communication node indicates the used data size level table at the granularity of LC, the first communication node reports the BSR at the granularity of LC; for another example, the second communication node indicates the data used at the granularity of LCG If the volume level table is used, the first communication node reports the BSR at the granularity of LCG; for another example, if the second communication node indicates the data volume level table at the granularity of DRB, the first communication node reports the BSR at the granularity of DRB.
  • the parameters related to the buffered data size report include: an indication that multiple BSR MAC CEs are supported in the same MAC PDU or in the same TTI.
  • performing BSR reporting includes: including K BSR MAC CEs in the same MAC PDU or the same TTI.
  • the buffered data size value corresponding to one LCG identifier is the sum of the buffered data size values corresponding to the LCG identifiers described in K BSR MAC CEs.
  • K is a positive integer.
  • multiple BSRs may be connected in series to accurately express the transport block size (Transport Block Size, TBS).
  • TBS Transport Block Size
  • the buffered data size value corresponding to one LCG identifier is equal to the buffered data size value corresponding to the LCG identifier in multiple BSR MAC CEs sum.
  • the same MAC PDU or the same TTI contains three BSR MAC CEs, and each of the three BSR MAC CEs contains an LCG identifier, and the value of the LCG identifier in the three BSR MAC CEs is If they are the same, then the data size value corresponding to the LCG identifier is the sum of the buffered data size values corresponding to the LCG identifier in the three BSR MAC CEs. In this way, it is equivalent to splitting an imprecise buffered data size value into multiple accurate buffered data size values for reporting, thereby saving resource overhead for uplink scheduling.
  • the parameters related to the buffered data size report include: a BSR report format indication.
  • the BSR MAC CE includes: the number of LCG identifiers, at least two LCG identifiers, and the buffer data size value corresponding to each LCG identifier; wherein, the number of LCG identifiers contained in each BSR MAC CE is the same as The number of LCG identifiers is the same; the LCG identifiers correspond to the value of the buffered data volume one by one in sequence.
  • the buffered data size value corresponding to the LCG mark is the sum of the buffered data size values corresponding to the LCG mark.
  • the number of LCG identifiers refers to the number of LCG identifiers used to indicate each BSR MAC CE.
  • the number of LCG identifiers can be recorded as LCG Num, that is, LCG Num is 3, and each The BSR MAC CE contains three LCG identifiers.
  • each LCG identifier corresponds to the value of the buffered data volume in order, that is, the number of LCG identifiers included in each BSR MAC CE is the same as the number of the LCG identifiers (ie, LCG Num), and, The number of buffer data size values is also the same as LCG Num.
  • the LCG identifiers in the same BSR MAC CE can be the same, that is, one LCG identifier can correspond to multiple buffered data size values, and the buffered data size value corresponding to the LCG identifier is equal to the multiple values corresponding to the LCG identifier. The sum of buffered data size values.
  • the number of LCG identifiers and the number of bits occupied by the LCG identifier are not an integer multiple of 8 bits, and the minimum number of bits among the integer multiples of 8 bits is aligned by reserving bits.
  • reserved bits may be used to align an integer multiple of 8 bits, so that the number of LCG identifiers The total number of occupied bits, bits occupied by all LCG identifiers and reserved bits is an integer multiple of 8 bits.
  • the parameters related to the buffered data size report include: a BSR report format indication.
  • BSR reporting includes: the BSR MAC CE includes: the number indication field of the buffered data size value, the LCG identifier, the LC identifier or the DRB identifier, and K buffered data size indication fields; K is determined by the buffered data size The number of values dictates domain decisions. K is a positive integer.
  • the buffered data size value corresponding to the LCG ID, LC ID or DRB ID is the sum of all buffered data size values corresponding to the LCG ID, LC ID or DRB ID.
  • the first communication node reports the BSR according to the LCG identifier, the LC identifier or the DRB identifier.
  • the sum of multiple buffered data size values corresponding to the ID or DRB ID can reduce the resource overhead of the LCG ID, and can support finer-grained BSR reporting, or report according to the LC ID or DRB ID.
  • the parameters related to the size of the buffered data report include: parameters for determining the level table of the size of the buffered data. Before determining the relevant parameters of the target buffered data size report for the service to be transmitted, it also includes: receiving the maximum TBS value configured by the second communication node according to the logical channel, logical channel group or DRB. Determining the report parameters related to the size of the buffered data used by the service to be transmitted includes: determining the level table of the size of the buffered data used by the service to be transmitted according to the maximum TBS value.
  • the cell where the first communication node is located or the second communication node configures the maximum supported TBS value to the first communication node according to LC, LCG or DRB, so that the first communication node determines the buffer used according to the maximum TBS value Data volume size level table.
  • the buffered data size report related parameters include: indicating using a buffered data size level table. Before determining the parameters related to the target buffered data size report used by the service to be transmitted, it also includes: receiving the indication information of the buffered data size level table broadcast by the cell where the first communication node is located, the BSR report type indication, the BSR format indication, and the support specific At least one of the indications of BSR reporting manners. Determining the parameters related to the buffered data size report used by the service to be transmitted, including: determining the buffered data size level table according to at least one of the indication information of the buffered data size level table, the BSR report type indication, the BSR format indication, and the indication supporting a specific BSR reporting method.
  • the indication information of the buffered data size level table is used to indicate the buffered data size level table used by the first communication node. It can be understood that, the cell where the first communication node is located indicates to the first communication node the buffered data size level table used by the first communication node, and the first communication node uses the buffered data size level table. If the cell corresponding to the first communication node does not broadcast the buffered data size level table indication information, the first communication node uses Table 1 by default to report the BSR.
  • the parameters related to the buffered data size report include: the buffered data size value corresponding to the buffered data size level table.
  • the relevant parameters of the target buffered data size report used by the service to be transmitted Before determining the relevant parameters of the target buffered data size report used by the service to be transmitted, it also includes: receiving the TBS minimum value broadcast by the cell where the first communication node is located or sent by the second communication node according to logical channel, logical channel group or DRB configuration, TBS maximum and granularity. Determine the relevant parameters of the buffered data size report used by the service to be transmitted, including: determine the buffered data size value corresponding to the buffered data size level table used by the service to be transmitted according to at least two of the TBS minimum value, TBS maximum value, and granularity .
  • the cell where the first communication node is located broadcasts or the second communication node sends to the first communication node the TBS minimum value, TBS maximum value and granularity configured according to LC, LCG or DRB, and the first communication node according to the TBS minimum value, TBS At least two of the maximum value and the granularity are automatically calculated for each buffered data size level table or buffered data size value corresponding to the buffered data size level.
  • the parameters related to the size of the buffered data report include: an indication of the used buffered data size level table.
  • Each buffered data size level in the buffered data size level table occupies at least two bytes. In an embodiment, more bits are allocated to each buffered data size level table to define a finer-grained BSR value, so that the buffered data size value can be determined more accurately.
  • the parameters related to the buffered data size report include: a buffered data size value.
  • Pre-configure K buffered data size intervals determine the buffered data size value used by the business to be transmitted according to the K buffered data size ranges; where the buffered data size value is equal to the buffered data size in the K buffered data size range
  • K is a positive integer.
  • the size interval of the buffered data volume refers to the value range of the size of the buffered data volume, wherein different buffered data volume level tables correspond to different buffered data volume size ranges, that is, the two are in one-to-one correspondence.
  • the first communication node or the second communication node predefines a plurality of buffered data size ranges, so that the first communication node determines the buffered data size level table used according to its own buffered data size value, and then The buffer data size value used can be determined.
  • FIG. 2 is a flowchart of another information transmission method provided by the embodiment of the present application.
  • This embodiment can be executed by an information transmission device.
  • the information transmission device may be the second communication node.
  • the second communication node is a base station.
  • this embodiment includes: S210-S220.
  • the parameters related to the buffered data size report include at least one of the following: an indication of the used buffered data size level table, an indication of the BSR reporting type, an indication of the BSR format, and an indication of supporting a specific BSR reporting method.
  • the information transmission method applied to the second communication node further comprising: receiving traffic information characteristics of the service to be transmitted indicated by the first communication node or the third communication node; wherein the traffic information characteristics include at least one of the following: Service volume value range; application layer service type; expected buffer data size level table; expected BSR reporting type indication; expected BSR format indication.
  • the third communication node indicates traffic information characteristics to the second communication node according to the packet data unit session, Quality of Service (Quality of Service, QoS) flow or QoS sub-flow.
  • Quality of Service Quality of Service
  • QoS Quality of Service
  • the second communication node indicates the size of buffered data and reports related parameters at the granularity of LC, LCG or DRB.
  • the pre-configured parameters related to buffered data size report before sending the pre-configured parameters related to buffered data size report to the first communication node, it also includes: sending the maximum TBS value configured according to the logical channel, logical channel group or DRB to the first communication node .
  • receiving the BSR reported by the first communication node based on the parameters related to the size of the buffered data report includes: the same MAC PDU or the same TTI contains K BSR MAC CEs.
  • the buffered data size value corresponding to one LCG identifier is the sum of the buffered data size values corresponding to the LCG identifiers described in K BSR MAC CEs; K is a positive integer.
  • it before sending the pre-configured buffered data size report related parameters to the first communication node, it further includes: the TBS minimum value, TBS maximum value and granularity configured according to the logical channel, logical channel group or DRB sent to the first communication node.
  • the parameters related to the buffered data size report include: the used buffered data size level table indication, BSR report type indication, BSR format indication, and indication of support for a specific BSR reporting method; the parameters are represented by LC, LCG or DRB is a granularity indication.
  • Parameters related to reporting the amount of buffered data are configured by the second communication node through broadcast signaling or UE-specific signaling.
  • the service volume information feature includes at least one of the following: service volume value range; application layer service type; desired buffer data size level table; desired BSR report type indication; desired BSR format indication .
  • the second communication node receives traffic information characteristics of the service to be transmitted indicated by the first communication node at a granularity of LC, LCG or DRB.
  • the BSR reported by the first communication node at the granularity of LC or DRB is received; the BSR reported at the granularity of LC or DRB includes: the LC identifier or the DRB identifier contained in the BSR MAC CE.
  • performing BSR reporting includes: including K BSR MAC CEs in the same MAC PDU or the same TTI.
  • the buffered data size value corresponding to one LCG identifier is the sum of the buffered data size values corresponding to the LCG identifiers in K BSR MAC CEs; where K is a positive integer.
  • BSR reporting includes: the BSR MAC CE includes: the number of LCG identities, at least two LCG identities, and the buffered data size value corresponding to each LCG identity; wherein, in each BSR MAC CE The number of LCG identifiers included is the same as the number of LCG identifiers; LCG identifiers and buffered data size values are in one-to-one correspondence in sequence; the same LCG identifier appears K times in the BSR MAC CE, then the buffer data corresponding to the LCG identifier The size value is the sum of K buffered data size values corresponding to the LCG identifier.
  • the number of LCG identifiers and the number of bits occupied by the LCG identifier are not an integer multiple of 8 bits, and the minimum number of bits among the integer multiples of 8 bits is aligned by reserving bits.
  • the BSR MAC CE includes: the number indicating field of the buffered data size value, the LCG identifier, the LC identifier or the DRB identifier, and K buffered data size indicating fields; K consists of the number of buffered data size values Indicates a domain decision.
  • the buffered data size value corresponding to the LCG ID, LC ID or DRB ID is the sum of the corresponding K buffered data size values; wherein, K is a positive integer.
  • the parameters related to the buffered data size report include: a used buffered data size level table.
  • Each buffer size level occupies at least two bytes.
  • the parameters related to the buffered data size report include: a buffered data size value.
  • Pre-configure K buffered data size intervals determine the buffered data size value used by the service to be transmitted according to the K buffered data size ranges; wherein, the buffered data size value is equal to the buffered data in the K buffered data size range
  • K is a positive integer.
  • the buffered data size level is represented as: Buffer size levels table, the buffered data size value is recorded as Buffer size, the first communication node is UE, the second communication node is a base station, and the third communication node is a core Taking the network as an example, the reporting process of traffic information is described. According to typical business characteristics, determine the Buffer Size fluctuation range of the business to be transmitted, and pre-define multiple Buffer size levels tables.
  • a 5-bit service volume value range (Buffer size levels (in bytes) for 5-bit Buffer Size field) is used for the business volume identification, and two buffer size level tables are configured according to the application layer business type.
  • Table 3 is a schematic table of values of buffered data size levels in a BSR provided by an embodiment of the present application;
  • Table 4 is a schematic table of values of buffered data size levels in another BSR provided in an embodiment of this application.
  • Table 3 is set for interactive low-rate services (that is, the value of Buffer size levels is small);
  • Table 4 is set for video streaming or file download services (that is, the value of Buffer size levels is large).
  • the UE or the core network indicates traffic information characteristics to the base station, and the traffic information characteristics may include one of the following: traffic value range, application layer service type (for example, interactive small rate service, video stream or File download business, etc.), and the expected Buffer size levels table indication (Table 1, Table 2, or Table 3).
  • the core network indicates traffic information characteristics to the base station can be indicated by packet data unit session (PDU session), quality of service flow (QoS Flow) or quality of service sub-flow (QoS sub-Flow).
  • the characteristic of the service volume information indicated by the UE to the base station may be indicated at a granularity of LC, LCG, or DRB.
  • the base station indicates to the UE the Buffer size levels table configured and used (indicate using Table 1, Table 2, or Table 3), and the base station can indicate according to the granularity of LC, LCG, or DRB.
  • the UE receives the Buffer size levels table indication configured by the base station to the UE (the indication uses Table 1, Table 2, or Table 3), and then selects the corresponding BSR table to report the BSR according to the instruction; if the instruction is not received, it defaults to the table 1 Report the BSR.
  • the UE reports the BSR according to the granularity of LC (the BSR contains the LC ID); if the base station indicates according to the granularity of the LCG, the UE reports the BSR according to the granularity of the LCG (the BSR contains the LCG ID); If the base station indicates according to the DRB granularity, the UE reports the BSR (the BSR includes the DRB ID) according to the DRB granularity.
  • the base station may not configure the indication of the Buffer size levels table used, but the UE selects the Buffer size levels table.
  • the Buffer size levels table uses different uplink LC IDs (LC ID for Uplink Shared Channel (Uplink Shared Channel, UL-SCH)) to distinguish.
  • the base station judges which Buffer size levels table the UE uses based on the uplink LC ID (LC ID for UL-SCH) in the MAC subheader.
  • the Buffer Size value in the Buffer size levels table and the number of the Buffer size levels table are only examples, and the actual Buffer Size value and the number of the Buffer size levels table may be different from the embodiments.
  • Fig. 3 is a schematic diagram of configuration of Short BSR MAC CE included in the same MAC PDU or the same TTI provided by the embodiment of the present application.
  • the same MAC PDU or the same TTI contains multiple BSR MAC CEs, and the Buffer Size corresponding to one LCG ID is equal to the sum of the Buffer Sizes corresponding to the LCG ID in multiple BSR MAC CEs.
  • the same MAC PDU or the same TTI contains 3 BSR MAC CEs, and the LCG ID values in the 3 BSR MAC CEs are the same, then the Buffer Size corresponding to the LCG ID is the Buffer Size of the 3 BSR MAC CEs The sum of Buffer Size.
  • 2Bytes of overhead is added when the UE reports the BSR, the resource overhead of 231Bytes in subsequent uplink scheduling is saved.
  • FIG. 4 is a schematic configuration diagram of a Long BSR MAC CE included in the same MAC PDU or the same TTI provided by the embodiment of the present application.
  • the expressed BSR reporting meaning is: the sum of the Buffer Sizes corresponding to the LCG IDs in the two Long BSR MAC CEs is the LCG ID The Buffer Size.
  • the base station may take the latest received MAC PDU as the criterion, and increase the BSR transmission delay.
  • Another method of using multiple BSRs in series to express accurate TBS (compared to another method of Long BSR MAC CE series in Embodiment 2, the overhead of LCG ID can be reduced).
  • FIG. 5 is a schematic configuration diagram of a Long BSR MAC CE provided by an embodiment of the present application.
  • the BSR MAC CE contains the number of LCG IDs (denoted as LCG Num), multiple LCG IDs, and the Buffer Size value corresponding to each LCG ID: LCG IDs and Buffer Size values correspond to each other in sequence.
  • LCG Num The number of LCG IDs indicates how many there are, there are several LCG IDs and the corresponding Buffer Size values of several LCG IDs.
  • the LCG IDs in the same BSR MAC CE can be the same, that is, one LCG ID value can correspond to multiple Buffer Sizes. At this time, the Buffer Size corresponding to the LCG ID is equal to the sum of multiple Buffer Sizes corresponding to the LCG ID value.
  • LCG ID Num and LCG ID are not an integer multiple of 8 bits, the minimum number of bits in the integer multiple of 8 bits is aligned through the reserved bit.
  • FIG. 6 is a schematic configuration diagram of another Long BSR MAC CE provided by the embodiment of the present application.
  • LCG ID Num and 2 LCG IDs occupy 12 bits, which are not integer multiples of 8 bits, 4 reserved bits are used to align integer multiples of 8 bits (LCG ID Num, 2 LCG IDs and 4 reserved bits occupy a total of 16 bits , is an integer multiple of 6bit).
  • the LCG ID can also be an LC ID or a DRB ID, and the number of bits occupied by each field is only an example, and the actual value used can be different from the example.
  • the UE can choose one of the structures and distinguish it through the different uplink LC ID (LCID for UL-SCH) in the MAC subheader Two structures; the base station may also instruct the UE to use one of the structures.
  • LCID uplink LC ID for UL-SCH
  • Another method of using multiple BSRs in series to express accurate TBS can reduce the overhead of LCG ID, and can support more fine-grained BSR reporting, It can also be reported by LC ID or DRB ID).
  • FIG. 7 is a schematic configuration diagram of another Long BSR MAC CE provided by the embodiment of the present application.
  • UE in BSR reporting, can report BSR according to LCG ID, LC ID or DRB ID.
  • the bits corresponding to each ID can contain several Buffer Sizes, and the Length field indicates the number of Buffer Sizes included.
  • the Buffer Size corresponding to the LCG ID, LC ID or DRB ID is the sum of multiple Buffer Sizes corresponding to the LCG ID, LC ID or DRB ID.
  • the cell broadcasts or the base station configures the maximum or minimum TBS value that can be supported by the logical channel, logical channel group or DRB to the UE, and then determines the Buffer size level table based on the maximum or minimum TBS value.
  • the cell broadcasts or the base station configures the maximum supportable TBS value to the UE according to the logical channel, logical channel group or DRB, and the UE and the base station determine the Buffer size level table based on the maximum TBS value. For example: for the three Buffer size level tables in Embodiment 1, if the maximum TBS of the cell broadcast is 967, then use Table 3; if the minimum TBS of the cell broadcast is 1000, then use Table 4; if not broadcast, then use Table 1.
  • the Buffer size level table used by the cell broadcast indicates that the UE selects the Buffer size level table according to the instruction.
  • Table 3 is indicated in the cell broadcast, and both the UE and the base station understand the meaning of the value of Buffer size level (Index) according to Table 3. If the base station does not broadcast the instruction, it will report the BSR according to Table 1 by default.
  • Index Buffer size level
  • the cell broadcasts or the base station configures the minimum TBS value, the maximum TBS value, and/or the granularity to the UE according to logical channels, logical channel groups or DRBs.
  • the UE and the base station automatically calculate the Buffer size value corresponding to each Buffer size level (Index).
  • a new Buffer size level is not introduced, but the Buffer size value corresponding to the Buffer size level (Index) is automatically calculated based on the TBS minimum value, the TBS maximum value, and the granularity.
  • the minimum value of TBS configured by the base station to the UE is 2, and the granularity is 2, then the Buffer size value corresponding to the calculated Buffer size level (Index) is: 0, 2, 4, 6, 8, 10...(0 It is used to indicate that the data transmission is completed, or the data buffer is empty, which is not included in the calculation range of the Buffer size value); the minimum value of TBS configured by the base station to the UE is 2, and the maximum value is 1000, then the Buffer size calculated by the base station is step
  • the length is (1000-2)/30, floor((1000-2)/30), the Buffer size corresponding to the first calculated Buffer size level (Index) is: floor(2+(1000-2) /30) or cell(2+(1000-2)/30).
  • the base station configures the minimum value, maximum value, and/or granularity of TBS to the UE, which can be configured according to LCG, LC, or DRB; if configured according to LC or DRB, the UE reports BSR according to LC or DRB.
  • a Buffer Size level table occupies more bits.
  • a Buffer Size level table occupies 2bytes or 3bytes. Compared with Table 1, it can represent a finer-grained BSR value.
  • BSR table to use can be instructed by the base station broadcast, or the base station can indicate to the UE according to logical channel, logical channel group or DRB configuration, or it can be independently selected by the UE, and through the uplink LC ID (LCID for UL- SCH) to distinguish.
  • LCID uplink LC ID
  • the Buffer Size value is the cumulative result of multiple reported interval values.
  • Buffer size levels Table 1 (Buffer Size range 0 to 1000), the value reported by the UE is XX: occupying 8 bits.
  • Buffer Size levels Table 2 (Buffer Size range 1000 ⁇ 10000), the value reported by UE is YY: occupying 4 bits.
  • Buffer Size levels Table 3 (Buffer Size range 10000 ⁇ 100000), the value reported by UE is ZZ: occupying 4 bits.
  • the reported Buffer size value ZZ*10000+YY*1000+XX, 16bits can express a value of 200000.
  • Buffer size levels Table 1 indicates that the Buffer Size range is 0 to 100000000, the value reported by the UE is XX: occupying 8 bits, and the interval T3 is 524288 (power of 2).
  • Buffer size levels Table 2 indicates that the Buffer Size range is 0 to 524288, the value reported by the UE is YY: occupying 4 bits, and the interval T2 is 32768.
  • Buffer size levels Table 3 indicates that the Buffer Size range is 0 to 32768, and the value reported by the UE is ZZ: occupying 4 bits, and the interval T1 is 2048.
  • the Buffer size value reported by the UE ZZ*524288+YY*32768+XX*2048.
  • Buffer size levels Table 1 is an 8-bit table, and the value reported by the UE is XX: occupying 8 bits.
  • Buffer size levels Table 2 indicates that the Buffer Size range is 0 to T2*16, and the value reported by the UE is YY: occupying 4 bits, the interval is T2, and T2 is 4096, 16384, and T1*16, etc.
  • Buffer size levels Table 3 indicates that the Buffer Size range is 0 to T1*16, and the value reported by the UE is ZZ: occupying 4 bits, and the interval T1 is 256, 512, 768, 1024, 1536, and 2048.
  • the Buffer size value reported by the UE ZZ+YY*T2+XX*T1.
  • Buffer size levels Table 1 is an 8-bit table, and the value reported by the UE is XX: occupying 8 bits.
  • Buffer size levels Table 2 indicates the Buffer Size range T to T*256, where T is the interval, T can be 256, 512, 768, 1024, 1536, and 2048, etc., and the value reported by the UE is YY: occupying 8 bits.
  • the Buffer size value reported by the UE ZZ+YY.
  • Buffer size levels Table 1 is an 8-bit table, and the value reported by the UE is XX: occupying 8 bits.
  • Buffer size levels Table 2 indicates that the Buffer Size interval is 16 values extracted from the 8-bit table as the interval interval, which can be equal or unequal intervals.
  • the value reported by the UE is YY: occupying 4 bits.
  • Buffer size levels Table 3 indicates that the Buffer Size interval is 16 values extracted from the 8-bit table as the interval interval, which can be equal or unequal intervals.
  • the value reported by the UE is ZZ: occupying 4 bits.
  • the Buffer size value reported by the UE ZZ+YY+XX.
  • the granularity of the multi-interval intervals in each table is not necessarily the same, for example, the intervals in the tables of the related art are not completely the same within a large value range.
  • only a large table is defined, for example: the interval of the buffser size value is 1024, or, 65536, or, a large table of 32768, and the base station configures a BSR for each logical channel to indicate that the index in the large table starts to end range.
  • the Buffer size value reported by the UE in Table 1 ranges from Z1 to Z2
  • the Buffer size value reported by the UE in Table 2 ranges from Y1 to Y2
  • the Buffer size value reported by the UE in Table 3 The value range of X1 ⁇ X2, then the value range of the Buffer size value reported by the UE is: X1+Y1+Z1 to X2+Y2+Z2.
  • the value range of the Buffer size value reported by the UE in Table 1 is Z1 ⁇ Z2
  • the value range of the Buffer size value reported by the UE in Table 2 is Y1 ⁇ Y2
  • the value range of the Buffer size value reported by the UE is The value range is: Y1+Z1 to Y2+Z2.
  • the granularity of multiple tables may be smaller and smaller, or different tables may be defined for different value ranges; it may also be a combination of a legacy table and other new granularity tables.
  • FIG. 8 is a structural block diagram of an information transmission device provided in an embodiment of the present application.
  • the information transmission device in this embodiment is integrated in the first communication node.
  • this embodiment includes: a first receiver 810 and a reporting module 820 .
  • the first receiver 810 is configured to receive or determine the parameters related to the buffered data size report used by the service to be transmitted; the reporting module 820 is configured to report the buffer status report BSR based on the parameters related to the buffered data size report.
  • the parameters related to the buffered data size report include at least one of the following: the buffered data size level table indication used, the BSR report type indication, the BSR format indication, and the indication supporting a specific BSR reporting method;
  • the parameters related to the data size report are indicated with LC, LCG or DRB as the granularity; the parameters related to the buffered data size report are configured by the second communication node through broadcast signaling or UE-specific signaling.
  • the information transmission device applied to the first communication node further includes: an indication module, configured to indicate to the second communication node before receiving or determining the relevant parameters of the buffered data size report used by the service to be transmitted Traffic information characteristics corresponding to the transmission service.
  • the service volume information feature includes at least one of the following: service volume value range; application layer service type; desired buffer data size level table; desired BSR report type indication; desired BSR format indication .
  • the indicating module is configured to: indicate to the second communication node the characteristics of traffic information of the service to be transmitted at the granularity of logical channel LC, logical channel group LCG or dedicated radio bearer DRB.
  • the first communication node reports the BSR at the granularity of LC or DRB; reporting the BSR at the granularity of LC or DRB includes: including the LC identifier or the DRB identifier in the BSR MAC CE.
  • performing BSR reporting includes: the same medium access control layer protocol data unit MAC PDU or the same transmission time interval TTI contains K BSR MAC CE; the buffer data size value corresponding to one LCG identifier is K BSR The sum of the buffered data size values corresponding to one LCG identifier in the MAC CE; wherein, K is a positive integer.
  • performing BSR reporting includes: including in the BSR MAC CE: the number of LCG identifiers, at least two LCG identifiers, and the buffered data size value corresponding to each LCG identifier; wherein, in each BSR MAC CE The number of LCG identifiers included is the same as the number of LCG identifiers; LCG identifiers and buffered data size values are in one-to-one correspondence in sequence; the same LCG identifier appears K times in the BSR MAC CE, then the buffer data corresponding to the LCG identifier The size value is the sum of K buffered data size values corresponding to the LCG identifier.
  • the number of LCG identifiers and the number of bits occupied by the LCG identifier are not an integer multiple of 8 bits, and the minimum number of bits among the integer multiples of 8 bits is aligned by reserving bits.
  • the BSR MAC CE includes: the number indication field of the buffered data size value, the LCG identifier, the LC identifier or the DRB identifier, and K buffered data size indication fields; K consists of the buffered data amount size value Determined by the quantity indication field; the buffered data size value corresponding to the LCG identifier, LC identifier or DRB identifier is the sum of all corresponding buffered data sizes; where K is a positive integer.
  • the information transmission device applied to the first communication node further includes: a second receiver, configured to receive the information from the second communication node according to The TBS value of the maximum transmission block size configured by a logical channel, logical channel group or DRB; determine the relevant parameters of the buffered data size report used by the service to be transmitted, including: determine the size level table of the buffered data size used by the service to be transmitted according to the maximum TBS value.
  • the buffered data size report related parameters include: buffered data size level table indication; the information transmission device applied to the first communication node also includes: a third receiver configured to determine the service to be transmitted using Receive at least one of the indication information of the buffered data volume level table broadcast by the cell where the first communication node is located, the BSR report type indication, the BSR format indication, and the indication supporting a specific BSR reporting method 1.
  • Determine the parameters related to the buffered data size report used by the service to be transmitted including: at least one of the indication information according to the buffered data size level table, the BSR reporting type indication, the BSR format indication, and the indication supporting a specific BSR reporting method Determine the size level table of the buffered data volume used by the service to be transmitted.
  • the parameters related to the buffered data size report include: the buffered data size value corresponding to the buffered data size level table; the information transmission device applied to the first communication node further includes: a fourth receiver configured to Before determining the relevant parameters of the target buffered data size report for the service to be transmitted, receive the TBS minimum value and TBS maximum value broadcast by the cell where the first communication node is located or sent by the second communication node according to logical channel, logical channel group or DRB configuration and granularity; determine the relevant parameters of the buffered data size report used by the service to be transmitted, including: determine the buffered data corresponding to the size level table of the buffered data size used by the service to be transmitted according to at least two of the TBS minimum value, TBS maximum value and granularity Quantity value.
  • the parameters related to the buffered data size report include: a buffered data size level table; each buffered data size level in the buffered data size level table occupies at least two bytes.
  • the buffered data size report related parameters include: buffered data size value; pre-configured K buffered data size intervals; determine the buffered data size value used by the service to be transmitted according to the K buffered data size intervals ; Wherein, the buffered data size value is equal to the sum of the buffered data size values in K buffered data size intervals; K is a positive integer.
  • the information transmission device provided in this embodiment is set to implement the information transmission method of the embodiment shown in Figure 1 applied to the first communication node.
  • the implementation principle and technical effect of the information transmission device provided in this embodiment are similar, and will not be repeated here. .
  • FIG. 9 is a structural block diagram of another information transmission device provided in an embodiment of the present application.
  • the information transmission device in this embodiment is integrated in the second communication node. As shown in FIG. 9 , this embodiment includes: a first transmitter 910 and a fifth receiver 920 .
  • the first transmitter 910 is configured to send the pre-configured buffered data size report related parameters to the first communication node; the fifth receiver 920 is configured to receive the BSR reported by the first communication node based on the buffered data size report related parameters .
  • the parameters related to the buffered data size report include at least one of the following: an indication of the used buffered data size level table, an indication of a BSR reporting type, an indication of a BSR format, and an indication of supporting a specific BSR reporting method.
  • the information transmission device applied to the second communication node further includes: a sixth receiver configured to receive traffic information characteristics of the service to be transmitted indicated by the first communication node or the third communication node; wherein,
  • the service volume information features include at least one of the following: service volume value range; application layer service type; expected buffer data size level table; expected BSR reporting type indication, expected BSR format indication.
  • the third communication node indicates the traffic information characteristic to the second communication node according to the packet data unit session, the QoS flow or the QoS sub-flow.
  • the second communication node indicates the size of buffered data and reports related parameters at the granularity of LC, LCG or DRB.
  • the information transmission device applied to the second communication node further includes: a second sender configured to send the pre-configured parameters related to the size of the buffered data report to the first communication node, according to the logic The maximum transport block size TBS value configured by the channel, logical channel group or DRB is sent to the first communication node.
  • receiving the BSR reported by the second communication node based on the buffered data volume size report related parameters includes; the same media access control layer protocol data unit MAC PDU or the same transmission time interval TTI contains K BSR MAC CE; the buffered data size value corresponding to one LCG identifier is the sum of the buffered data size values corresponding to one LCG identifier in the K BSR MAC CEs.
  • the information transmission device applied to the second communication node further includes: a third sender configured to send the pre-configured parameters related to the size of the buffered data report to the first communication node, according to the logic
  • the TBS minimum value, TBS maximum value and granularity of channel, logical channel group or DRB configuration are sent to the first communication node.
  • the parameters related to the buffered data size report include at least one of the following: the buffered data size level table indication used, the BSR report type indication, the BSR format indication, and the indication supporting a specific BSR reporting method;
  • the parameters related to the data size report are indicated with LC, LCG or DRB as the granularity; the parameters related to the buffered data size report are configured by the second communication node through broadcast signaling or UE-specific signaling.
  • the service volume information feature includes at least one of the following: service volume value range; application layer service type; desired buffer data size level table; desired BSR report type indication; desired BSR format indication .
  • the second communication node receives the service volume information characteristic corresponding to the service to be transmitted indicated by the first communication node at the granularity of logical channel LC, logical channel group LCG or dedicated radio bearer DRB.
  • receiving the BSR reported by the first communication node at the granularity of LC or DRB; reporting the BSR at the granularity of LC or DRB includes: including the LC identifier or the DRB identifier in the BSR MAC CE.
  • performing BSR reporting includes: the same medium access control layer protocol data unit MAC PDU or the same transmission time interval TTI contains K BSR MAC CE; the buffer data size value corresponding to one LCG identifier is K BSR The sum of the buffered data size values corresponding to one LCG identifier in the MAC CE; wherein, K is a positive integer.
  • performing BSR reporting includes: including in the BSR MAC CE: the number of LCG identifiers, at least two LCG identifiers, and the buffered data size value corresponding to each LCG identifier; wherein, in each BSR MAC CE The number of LCG identifiers included is the same as the number of LCG identifiers; LCG identifiers and buffered data size values are in one-to-one correspondence in sequence; the same LCG identifier appears K times in the BSR MAC CE, then the buffer data corresponding to the LCG identifier The size value is the sum of at least two buffered data size values corresponding to the LCG identifier.
  • the number of LCG identifiers and the number of bits occupied by the LCG identifier are not an integer multiple of 8 bits, and the minimum number of bits among the integer multiples of 8 bits is aligned by reserving bits.
  • the BSR MAC CE includes: the number indication field of the buffered data size value, the LCG identifier, the LC identifier or the DRB identifier, and K buffered data size indication fields; K consists of the buffered data amount size value Determined by the quantity indication field; the buffered data size value corresponding to any one of the LCG ID, LC ID or DRB ID is the sum of the K buffered data size values corresponding to the any ID; where K is a positive integer.
  • the parameters related to the buffered data size report include: a buffered data size level table; each buffered data size level in the buffered data size level table occupies at least two bytes.
  • the buffered data size report related parameters include: buffered data size value; determine the buffered data size report related parameters used by the service to be transmitted, including: pre-configuring K buffered data size intervals; according to K The buffered data size interval determines the buffered data size value used by the service to be transmitted; wherein, the buffered data size value is equal to the sum of the buffered data size values in K buffered data size ranges; K is a positive integer.
  • the information transmission device provided in this embodiment is configured to implement the information transmission method in the embodiment shown in FIG. 2 applied to the second communication node.
  • the implementation principle and technical effect of the information transmission device provided in this embodiment are similar, and will not be repeated here.
  • Fig. 10 is a schematic structural diagram of an information transmission device provided by an embodiment of the present application.
  • the device provided by this application includes: a processor 1010 , a memory 1020 and a communication module 1030 .
  • the number of processors 1010 in the device may be one or more, and one processor 1010 is taken as an example in FIG. 10 .
  • the number of storage 1020 in the device may be one or more, and one storage 1020 is taken as an example in FIG. 10 .
  • the processor 1010, the memory 1020, and the communication module 1030 of the device may be connected through a bus or in other ways. In FIG. 10, connection through a bus is taken as an example.
  • the device may be a terminal side (for example, user equipment).
  • the memory 1020 can be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to devices in any embodiment of the present application (for example, the first receiver in the information transmission device device 810 and reporting module 820).
  • the memory 1020 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to usage of the device, and the like.
  • the memory 1020 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage devices.
  • memory 1020 may include memory located remotely from processor 1010, and such remote memory may be connected to the device through a network.
  • Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination of the Internet, an intranet, a local area network, and a mobile communication network.
  • the communication module 1030 is configured to communicate with other communication nodes.
  • the information transmission device is the first communication node
  • the device provided above may be configured to execute the information transmission method applied to the first communication node provided in any of the above embodiments, and have corresponding functions and effects.
  • the device provided above may be configured to execute the information transmission method applied to the second communication node provided in any of the above embodiments, and have corresponding functions and effects.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions When executed by a computer processor, the computer-executable instructions are used to execute an information transmission method applied to a first communication node.
  • the method includes: receiving or Determine the parameters related to the report of the size of the buffered data used by the service to be transmitted; report the BSR based on the parameters related to the report of the size of the buffered data.
  • the embodiment of the present application also provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions When executed by a computer processor, the computer-executable instructions are used to execute an information transmission method applied to a second communication node.
  • the method includes: The configured buffered data size report related parameters are sent to the first communication node; and the BSR reported by the first communication node based on the buffered data size report related parameters is received.
  • user equipment covers any type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.
  • the various embodiments of the present application can be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages source or object code.
  • ISA Instruction Set Architecture
  • Any logic flow block diagrams in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions.
  • Computer programs can be stored on memory.
  • the memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as but not limited to Read-Only Memory (ROM), Random Access Memory (RAM), Optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc.
  • Computer readable media may include non-transitory storage media.
  • Data processors can be of any type suitable for the local technical environment, such as but not limited to general purpose computers, special purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC ), programmable logic devices (Field-Programmable Gate Array, FPGA), and processors based on multi-core processor architectures.
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • processors based on multi-core processor architectures.

Landscapes

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

Abstract

本申请提出一种信息传输方法、设备和存储介质。应用于第一通信节点的信息传输方法包括：接收或确定待传输业务采用的缓冲数据量大小报告相关参数；基于所述缓冲数据量大小报告相关参数进行缓冲状态报告BSR上报。

Description

信息传输方法、设备和存储介质 技术领域
本申请涉及通信领域，例如涉及一种信息传输方法、设备和存储介质。
背景技术
在新空口(New Radio，NR)网络中，上行业务的业务量通过缓冲状态报告(Buffer Status Report，BSR)上报。而通过BSR上报业务量时考虑到BSR媒体接入控制层-控制单元(Media Access Control-Control Element,MAC CE)的资源开销，业务量大小标识部分采用5bit或8bit。而NR终端的业务缓存比较大，业务量取值范围也比较大，比如从0到81338368Bytes，用5bit或8bit很难精确表示0到81338368Bytes之间的业务量大小。而通过BSR上报的业务量大小不精确，导致基站资源调度不精确，造成无线资源的浪费。
发明内容
本申请实施例提供一种信息传输方法，包括：
接收或确定待传输业务采用的缓冲数据量大小报告相关参数；
基于所述缓冲数据量大小报告相关参数进行缓冲状态报告BSR上报。
本申请实施例提供一种信息传输方法，应用于第二通信节点，包括：
将预先配置的缓冲数据量大小报告相关参数发送至第一通信节点；
接收第一通信节点基于所述缓冲数据量大小报告相关参数上报的BSR。
本申请实施例提供一种信息传输设备，包括：通信模块，存储器，以及一个或多个处理器；
所述通信模块，配置为与其它通信节点进行通信交互；
所述存储器，配置为存储一个或多个程序；
当所述一个或多个程序被所述一个或多个处理器执行时，所述一个或多个处理器实现上述任一实施例所述的方法。
本申请实施例提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现上述任一实施例所述的方法。
附图说明
图1是本申请实施例提供的一种信息传输方法的流程图；
图2是本申请实施例提供的另一种信息传输方法的流程图；
图3是本申请实施例提供的一种在同一媒体接入控制层分组数据单元(Media Access Control Packet Data Unit，MAC PDU)或同一传输时间间隔(Transmission Time Interval，TTI)内所包含的短缓冲状态报告媒体接入控制层-控制单元(Short Buffer Status Report Mediu Access Control-Control Element，Short BSR MAC CE)的配置示意图；
图4是本申请实施例提供的一种在同一MAC PDU或同一TTI内所包含的长缓冲状态报告媒体接入控制层-控制单元(Long Buffer Status Report Mediu Access Control-Control Element，Long BSR MAC CE)的配置示意图；
图5是本申请实施例提供的一种Long BSR MAC CE的配置示意图；
图6是本申请实施例提供的另一种Long BSR MAC CE的配置示意图；
图7是本申请实施例提供的又一种Long BSR MAC CE的配置示意图；
图8是本申请实施例提供的一种信息传输装置的结构框图；
图9是本申请实施例提供的另一种信息传输装置的结构框图；
图10是本申请实施例提供的一种信息传输设备的结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行说明。以下结合实施例附图对本申请进行描述，所举实例仅用于解释本申请，并非用于限定本申请的范围。
表1是本申请实施例提供的一种BSR中缓冲数据量大小级别表的取值示意表；表2是本申请实施例提供的另一种BSR中缓冲数据量大小级别表的取值示意表。其中，表1是对业务量大小标识采用5bit的业务量取值范围进行说明，表2是对业务量大小标识采用8bit的业务量取值范围进行说明。如表2所示，索引(index)＝200和index＝201的缓冲数据量大小(Buffer Size)值相差188367Bytes，这么大的误差导致基站资源调度不精确。
表1
Index BS value Index BS value Index BS value Index BS value
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
表2
Index BS value Index BS value Index BS value Index BS value
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
因此，如何实现用户设备(User Equipment，UE)可以精确地上报业务量是一个亟待解决的问题。本申请实施例提供一种信息传输方法，可以根据待传输业务的信息特征选择性地配置采用的缓冲数据量大小级别表指示或确定采用的缓冲数据量大小级别表，或者，采用的多个缓冲数据量大小值，从而使得UE可以精确地上报业务量。
在一实施例中，图1是本申请实施例提供的一种信息传输方法的流程图。本实施例可以由信息传输设备执行。其中，信息传输设备可以为第一通信节点。示例性地，第一通信节点为终端侧(比如，用户设备)。如图1所示，本实施例包括：S110-S120。
S110、接收或确定待传输业务采用的缓冲数据量大小报告相关参数。
S120、基于缓冲数据量大小报告相关参数进行BSR上报。
在一实施例中，缓冲数据量大小报告相关参数包括如下至少之一：使用的缓冲数据量大小级别表指示，BSR上报类型指示，BSR格式指示，以及支持特定BSR上报方式的指示；所述缓冲数据量大小报告相关参数为第二通信节点通过广播信令或UE专用信令配置。其中，使用的缓冲数据量大小级别表指示，用于指示第一通信节点所采用的缓冲数据量大小级别表。BSR上报类型指示，用 于指示BSR上报值的类型或粒度；BSR格式指示，用于指示BSR采用哪种缓冲状态报告媒体接入控制层-控制单元(Buffer Status Report Media Access Control-Control Element，BSR MAC CE)格式进行上报；支持特定BSR上报方式的指示，用于指示第二通信节点是否支持同一MAC PDU或同一TTI内包含K个BSR MAC CE等预定义的BSR上报方式。K为正整数。在实施例中，第二通信节点通过广播信令或UE专用信令配置第一通信节点采用的缓冲数据量大小级别表指示，BSR上报类型指示，BSR格式指示，或支持特定BSR上报方式的指示，以向第一通信节点指示所使用的缓冲数据量大小报告方式。在第二通信节点未向第一通信节点指示的情况下，第一通信节点默认采用表1进行BSR上报。
在一实施例中，在接收或确定待传输业务采用的缓冲数据量大小报告相关参数之前，还包括：向第二通信节点指示待传输业务对应的业务量信息特征。其中，业务量信息特征用于表征待传输业务的属性。
在一实施例中，业务量信息特征至少包括下述之一：业务量取值范围；应用层业务类型；期望使用的缓冲数据量大小级别表；期望BSR上报的类型指示；期望使用的BSR格式指示。在实施例中，应用层业务类型可以包括：交互类小速率业务以及视频流或文件下载类业务等。在实施例中，期望使用的缓冲数据量大小级别表指的是第一通信节点可以采用的一个或多个缓冲数据量大小级别表。可以理解为，可以根据应用层业务类型配置多个缓冲数据量大小级别表。示例性地，假设期望使用的缓冲数据量大小级别表包括三个，分别为表1所示的业务量大小标识采用5bit的业务量取值范围对应的缓冲数据量大小级别表，交互类小速率业务对应的缓冲数据量大小级别表以及视频流或文件下载类业务对应的缓冲数据量大小级别表。期望BSR上报类型指示，用于指示期望BSR上报值的类型或粒度；期望BSR格式指示，用于指示期望BSR采用哪种BSR MAC CE格式进行上报。
在一实施例中，以逻辑信道(Logical Channel，LC)、逻辑信道组(Logical Channel Group，LCG)或专用无线承载(Dedicated Radio Bearer，DRB)为粒度向第二通信节点指示待传输业务的业务量信息特征。
在一实施例中，第一通信节点以LC或DRB为粒度上报BSR；以LC或DRB为粒度上报BSR包括：BSR MAC CE中包含逻辑信道标识(Logical Channel identifier，LC ID)或专用无线承载标识(Dedicated Radio Bearer identifier，DRB ID)。在实施例中，第一通信节点上报BSR的粒度与第二通信节点指示使用的缓冲数据量大小级别表的粒度是相同的。示例性地，在第二通信节点以LC为粒度指示使用的数据量大小级别表，则第一通信节点以LC为粒度上报BSR；又 如，在第二通信节点以LCG为粒度指示使用的数据量大小级别表，则第一通信节点以LCG为粒度上报BSR；又如，在第二通信节点以DRB为粒度指示使用的数据量大小级别表，则第一通信节点以DRB为粒度上报BSR。
在一实施例中，缓冲数据量大小报告相关参数包括：支持同一MAC PDU或同一TTI内包含多个BSR MAC CE的指示。示例性地，进行BSR上报包括：同一MAC PDU或同一TTI内包含K个BSR MAC CE。
一个LCG标识对应的缓冲数据量大小值为K个BSR MAC CE中所述LCG标识对应的缓冲数据量大小值的总和。K为正整数。
在实施例中，可以通过多个BSR进行串联，以准确地表达传输块大小(Transport Block Size，TBS)。在实施例中，同一MAC PDU或同一TTI中包含多个BSR MAC CE的情况下，一个LCG标识对应的缓冲数据量大小值等于多个BSR MAC CE中该LCG标识对应的缓冲数据量大小值的总和。示例性地，假设同一个MAC PDU或同一TTI内包含了三个BSR MAC CE，且这三个BSR MAC CE中均包含一个LCG标识，并且，这三个BSR MAC CE中的LCG标识的取值相同，则该LCG标识对应的数据量大小值为这三个BSR MAC CE中该LCG标识对应的缓冲数据量大小值的总和。这样，相当于把一个不精确的缓冲数据量大小值拆分为多个精确的缓冲数据量大小值进行上报，从而节省了上行调度的资源开销。
在一实施例中，缓冲数据量大小报告相关参数包括：BSR上报格式指示。示例性地BSR MAC CE中包括：LCG标识的数量，至少两个LCG标识，以及每个LCG标识对应的缓冲数据量大小值；其中，每个BSR MAC CE中所包含的LCG标识的个数与LCG标识的数量相同；LCG标识和缓冲数据量大小值按照顺序一一对应。
同一个LCG标识在BSR MAC CE出现K次，则该一个LCG标识对应的缓冲数据量大小值为所述LCG标识对应的缓冲数据量大小值的总和。在实施例中，LCG标识的数量指的是用于指示每个BSR MAC CE中所包含的LCG标识的数量，比如，LCG标识的数量可以记为LCG Num，即LCG Num为3，则每个BSR MAC CE中包含三个LCG标识。在实施例中，每个LCG标识与缓冲数据量大小值按照顺序一一对应，即每个BSR MAC CE中所包含的LCG标识的数目与该LCG标识的数量(即LCG Num)相同，并且，缓冲数据量大小值的数量也与LCG Num相同。在实施例中，同一个BSR MAC CE中的LCG标识可以相同，即一个LCG标识可以对应多个缓冲数据量大小值，该LCG标识对应的缓冲数据量大小值等于该LCG标识所对应的多个缓冲数据量大小值的总和。
在一实施例中，LCG标识的数量和LCG标识所占用的比特数并非8比特的 整数倍，通过保留比特对齐8比特的整数倍中的最小比特数。在实施例中，在LCG标识的数量所占用比特和所有LCG标识所占用比特的总数不是8比特的整数倍的情况下，可以采用保留比特对齐8比特的整数倍，以使得LCG标识的数量所占用比特、所有LCG标识所占用比特和保留比特的总数为8比特的整数倍。
在一实施例中，缓冲数据量大小报告相关参数包括：BSR上报格式指示。示例性地，进行BSR上报包括：BSR MAC CE中包括：缓冲数据量大小值的数量指示域，LCG标识、LC标识或DRB标识，和K个缓冲数据量大小指示域；K由缓冲数据量大小值的数量指示域决定。K为正整数。LCG标识、LC标识或DRB标识对应的缓冲数据量大小值为所述LCG标识、LC标识或DRB标识对应的所有缓冲数据量大小值的总和。在实施例中，第一通信节点按照LCG标识、LC标识或DRB标识进行BSR上报。在LCG标识、LC标识或DRB标识所占用比特之后的比特位中配置多个缓冲数据量大小值，以使得该LCG标识、LC标识或DRB标识对应的缓冲数据量大小值为该LCG标识、LC标识或DRB标识对应的多个缓冲数据量大小值的总和，从而可以减少LCG标识的资源开销，以及可以支持更细粒度的BSR上报，也可以按照LC标识或DRB标识进行上报。
在一实施例中，缓冲数据量大小报告相关参数包括：确定缓冲数据量大小级别表的参数。在确定待传输业务采用的目标缓冲数据量大小报告相关参数之前，还包括：接收第二通信节点按照逻辑信道、逻辑信道组或DRB配置的最大TBS值。确定待传输业务采用的缓冲数据量大小报告相关参数，包括：根据最大TBS值确定待传输业务采用的缓冲数据量大小级别表。在实施例中，第一通信节点所在小区或第二通信节点向第一通信节点按照LC、LCG或DRB配置可以支持的最大TBS值，以使第一通信节点根据最大TBS值确定所使用的缓冲数据量大小级别表。
在一实施例中，缓冲数据量大小报告相关参数包括：使用缓冲数据量大小级别表指示。在确定待传输业务采用的目标缓冲数据量大小报告相关参数之前，还包括：接收第一通信节点所在小区广播的缓冲数据量大小级别表的指示信息、BSR上报类型指示、BSR格式指示和支持特定BSR上报方式的指示中的至少之一。确定待传输业务采用的缓冲数据量大小报告相关参数，包括：根据缓冲数据量大小级别表的指示信息、BSR上报类型指示、BSR格式指示和支持特定BSR上报方式的指示中的至少之一确定待传输业务采用的缓冲数据量大小级别表。在实施例中，缓冲数据量大小级别表的指示信息用于指示第一通信节点所使用的缓冲数据量大小级别表。可以理解为，第一通信节点所在小区向第一通信节点指示该第一通信节点使用的缓冲数据量大小级别表，则第一通信节点就采用该缓冲数据量大小级别表。若第一通信节点所对应小区未广播缓冲数据量大小级别表指示信息，则第一通信节点默认采用表1进行BSR上报。
在一实施例中，缓冲数据量大小报告相关参数包括：缓冲数据量大小级别表对应的缓冲数据量大小值。
在确定待传输业务采用的目标缓冲数据量大小报告相关参数之前，还包括：接收第一通信节点所在小区广播或第二通信节点发送的按照逻辑信道、逻辑信道组或DRB配置的TBS最小值、TBS最大值和粒度。确定待传输业务采用的缓冲数据量大小报告相关参数，包括：根据TBS最小值、TBS最大值和粒度中的至少两个确定待传输业务采用的缓冲数据量大小级别表对应的缓冲数据量大小值。
在实施例中，第一通信节点所在小区广播或第二通信节点向第一通信节点按照LC、LCG或DRB配置的TBS最小值、TBS最大值和粒度，第一通信节点根据TBS最小值、TBS最大值和粒度中的至少两个自动计算每个缓冲数据量大小级别表或缓冲数据量大小级别对应的缓冲数据量大小值。
在一实施例中，缓冲数据量大小报告相关参数包括：使用的缓冲数据量大小级别表指示。
所述缓冲数据量大小级别表中每个缓冲数据量大小级别至少占用两个字节。在实施例中，对每个缓冲数据量大小级别表分配更多比特，以定义更细粒度的BSR值，从而可以更准确地确定缓冲数据量大小值。
在一实施例中，缓冲数据量大小报告相关参数包括：缓冲数据量大小值。
预配置K个缓冲数据量大小区间；根据K个缓冲数据量大小区间确定待传输业务采用的缓冲数据量大小值；其中，缓冲数据量大小值等于K个缓冲数据量大小区间内缓冲数据量大小取值的总和，K为正整数。
缓冲数据量大小区间指的是缓冲数据量大小值的取值范围，其中，不同的缓冲数据量大小级别表所对应的缓冲数据量大小区间不同，即两者是一一对应的。在实施例中，第一通信节点或第二通信节点预定义多个缓冲数据量大小区间，以使第一通信节点根据自身的缓冲数据量大小值确定所使用的缓冲数据量大小级别表，进而可以确定所使用的缓冲数据量大小值。
在一实施例中，图2是本申请实施例提供的另一种信息传输方法的流程图。本实施例可以由信息传输设备执行。其中，信息传输设备可以为第二通信节点。示例性地，第二通信节点为基站。如图2所示，本实施例包括：S210-S220。
S210、将预先配置的缓冲数据量大小报告相关参数发送至第一通信节点。
S220、接收第一通信节点基于缓冲数据量大小报告相关参数上报的BSR。
在一实施例中，缓冲数据量大小报告相关参数包括如下至少之一：使用的 缓冲数据量大小级别表指示，BSR上报类型指示，BSR格式指示，以及支持特定BSR上报方式的指示。
应用于第二通信节点的信息传输方法，还包括：接收第一通信节点或第三通信节点指示的待传输业务的业务量信息特征；其中，所述业务量信息特征至少包括下述之一：业务量取值范围；应用层业务类型；期望使用的缓冲数据量大小级别表；期望BSR上报类型指示；期望使用的BSR格式指示。
在一实施例中，第三通信节点按照分组数据单元会话、服务质量(Quality of Service，QoS)流或QoS子流向第二通信节点指示业务量信息特征。
在一实施例中，第二通信节点以LC、LCG或DRB为粒度指示缓冲数据量大小报告相关参数。
在一实施例中，在将预先配置的缓冲数据量大小报告相关参数发送至第一通信节点之前，还包括：将按照逻辑信道、逻辑信道组或DRB配置的最大TBS值发送至第一通信节点。
在一实施例中，接收第一通信节点基于所述缓冲数据量大小报告相关参数上报的BSR，包括：同一MAC PDU或同一TTI内包含K个BSR MAC CE。
一个LCG标识对应的缓冲数据量大小值为K个BSR MAC CE中所述LCG标识对应的缓冲数据量大小值的总和；K为正整数。在一实施例中，在将预先配置的缓冲数据量大小报告相关参数发送至第一通信节点之前，还包括：将按照逻辑信道、逻辑信道组或DRB配置的TBS最小值、TBS最大值和粒度发送至第一通信节点。
在一实施例中，缓冲数据量大小报告相关参数包括：使用的缓冲数据量大小级别表指示、BSR上报类型指示、BSR格式指示以及支持特定BSR上报方式的指示；所述参数以LC、LCG或DRB为粒度指示。
缓冲数据量大小报告相关参数为第二通信节点通过广播信令或UE专用信令配置。
在一实施例中，业务量信息特征至少包括下述之一：业务量取值范围；应用层业务类型；期望使用的缓冲数据量大小级别表；期望BSR上报类型指示；期望使用的BSR格式指示。
在一实施例中，第二通信节点以LC、LCG或DRB为粒度接收第一通信节点指示的待传输业务的业务量信息特征。
在一实施例中，接收第一通信节点以LC或DRB为粒度上报的BSR；以LC或DRB为粒度上报的BSR包括：BSR MAC CE中包含的LC标识或DRB标识。
在一实施例中，进行BSR上报，包括：同一MAC PDU或同一TTI内包含K个BSR MAC CE。
一个LCG标识对应的缓冲数据量大小值为K个BSR MAC CE中LCG标识对应的缓冲数据量大小值的总和；其中，K为正整数。
在一实施例中，进行BSR上报，包括：BSR MAC CE中包括：LCG标识的数量，至少两个LCG标识，以及每个LCG标识对应的缓冲数据量大小值；其中，每个BSR MAC CE中所包含的LCG标识的个数，与LCG标识的数量相同；LCG标识和缓冲数据量大小值按照顺序一一对应；同一个LCG标识在BSR MAC CE出现K次，则该LCG标识对应的缓冲数据量大小值为LCG标识对应的K个缓冲数据量大小值的总和。
在一实施例中，LCG标识的数量和LCG标识所占用的比特数并非8比特的整数倍，通过保留比特对齐8比特的整数倍中的最小比特数。
在一实施例中，BSR MAC CE中包括：缓冲数据量大小值的数量指示域，LCG标识、LC标识或DRB标识，和K个缓冲数据量大小指示域；K由缓冲数据量大小值的数量指示域决定。
LCG标识、LC标识或DRB标识对应的缓冲数据量大小值为对应的K个缓冲数据量大小值的总和；其中，K为正整数。
在一实施例中，缓冲数据量大小报告相关参数包括：使用的缓冲数据量大小级别表。
每个缓冲数据量大小级别至少占用两个字节。
在一实施例中，缓冲数据量大小报告相关参数包括：缓冲数据量大小值。
预配置K个缓冲数据量大小区间；根据K个缓冲数据量大小区间确定待传输业务采用的缓冲数据量大小值；其中，所述缓冲数据量大小值等于K个缓冲数据量大小区间内缓冲数据量大小取值的总和；K为正整数。
需要说明的是，应用于第二通信节点的信息传输方法中的多个参数的解释，见上述实施例中应用于第一通信节点的信息传输方法中的描述，在此不再一一赘述。
实施例1
在实施例中，以缓冲数据量大小级别表记为：Buffer size levels表，缓冲数据大小值记为Buffer size，第一通信节点为UE，第二通信节点为基站，以及第三通信节点为核心网为例，对业务量信息的上报过程进行说明。针对典型业务特征，确定待传输业务的Buffer Size波动范围，并预定义多个Buffer size levels 表。
示例性地，针对业务量大小标识采用5bit的业务量取值范围(Buffer size levels(in bytes)for 5-bit Buffer Size field)，按照应用层业务类型配置两个缓冲数据量大小级别表。表3是本申请实施例提供的一种BSR中缓冲数据量大小级别的取值示意表；表4是本申请实施例提供的另一种BSR中缓冲数据量大小级别的取值示意表。其中，为交互类小速率业务设置表3(即Buffer size levels取值较小)；为视频流或者文件下载类业务设置表4(即Buffer size levels取值较大)。
表3
Index BS value Index BS value Index BS value Index BS value
0 0 8 BS<＝31 16 BS<＝107 24 BS<＝376
1 ≤10 9 BS<＝36 17 BS<＝125 25 BS<＝440
2 ≤14 10 BS<＝42 18 BS<＝146 26 BS<＝515
3 ≤20 11 BS<＝49 19 BS<＝171 27 BS<＝603
4 ≤28 12 BS<＝57 20 BS<＝200 28 BS<＝706
5 ≤38 13 BS<＝67 21 BS<＝234 29 BS<＝826
6 ≤53 14 BS<＝78 22 BS<＝274 30 BS<＝967
7 ≤74 15 BS<＝91 23 BS<＝321 31 967<BS
表4
Index BS value Index BS value Index BS value Index BS value
0 BS＝0 8 BS<＝4677 16 BS<＝16507 24 BS<＝58255
1 BS<＝1000 9 BS<＝5476 17 BS<＝19325 25 BS<＝68201
2 BS<＝1817 10 BS<＝6411 18 BS<＝22624 26 BS<＝79846
3 BS<＝2127 11 BS<＝7505 19 BS<＝26487 27 BS<＝93479
4 BS<＝2490 12 BS<＝8787 20 BS<＝31009 28 BS<＝109439
5 BS<＝2915 13 BS<＝10287 21 BS<＝36304 29 BS<＝128125
6 BS<＝3413 14 BS<＝12043 22 BS<＝42502 30 BS<＝150000
7 BS<＝3995 15 BS<＝14099 23 BS<＝49759 31 BS>150000
在实施例中，UE或者核心网向基站指示业务量信息特征，业务量信息特征可以包括下述之一：业务量取值范围、应用层业务类型(比如，交互类小速率业务、视频流或者文件下载类业务等)、以及期望使用的Buffer size levels表指 示(表1，表2，或者表3)。其中，核心网向基站指示业务量信息特征可以按分组数据单元会话(PDU session)，服务质量流(QoS Flow)或服务质量子流(QoS sub-Flow)指示。UE向基站指示业务量信息特征可以按LC，LCG，或DRB为粒度指示。
基站向UE配置使用的Buffer size levels表指示(指示使用表1，表2，或者表3)，基站可以按LC，LCG，或DRB为粒度来指示。
UE接收到基站向UE配置使用的Buffer size levels表指示(指示使用表1，表2，或者表3)，则按照指示选择对应的BSR表进行BSR上报；如果未收到指示，则默认按表1进行BSR上报。
如果基站按LC为粒度来指示，则UE按LC为粒度上报BSR(BSR里包含LC ID)；如果基站按LCG为粒度来指示，则UE按LCG为粒度上报BSR(BSR里包含LCG ID)；如果基站按DRB为粒度来指示，则UE按DRB为粒度上报BSR(BSR里包含DRB ID)。
在实施例中，基站也可以不配置使用的Buffer size levels表指示，而是由UE来选择Buffer size levels表，此时Buffer size levels表通过MAC子头里的不同的上行LC ID(LC ID for上行共享通道(Uplink Shared Channel，UL-SCH))来区分。此时，基站基于MAC子头里的上行LC ID(LC ID for UL-SCH)来判断UE使用的哪个Buffer size levels表。
在实施例中，Buffer size levels表里的Buffer Size取值以及Buffer size levels表的个数仅做示例，实际的Buffer Size取值和Buffer size levels表的个数可以与实施例不同。
实施例2
采用多个BSR串联表达准确的TBS的方法。
图3是本申请实施例提供的一种在同一MAC PDU或同一TTI内所包含Short BSR MAC CE的配置示意图。如图3所示，同一MAC PDU或同一TTI中包含多个BSR MAC CE，一个LCG ID对应的Buffer Size等于多个BSR MAC CE中该LCG ID对应的Buffer Size之和。
示例性地，同一MAC PDU或同一TTI中包含了3个BSR MAC CE，且3个BSR MAC CE中的LCG ID取值都相同，则该LCG ID对应的Buffer Size为3个BSR MAC CE中的Buffer Size之和。
这样，相当于把一个不精确的Buffer Size拆分为多个精确的Buffer Size值 上报。
比如，UE上报Buffer Size＝1783Bytes的BSR，但表1中没有与Buffer Size＝1783Bytes相近的取值；UE如果上报index＝17，则eNB按照Buffer Size＝2014Bytes分配资源，比期望上报的Buffer Size多231Bytes(＝20146Bytes-1783Bytes)，浪费上行UL-SCH的资源。但如果拆分为2个BSR MAC CE上报，比如第一个MAC CE上报值为Index＝15(对应Buffer Size＝1038Bytes)，第二个MAC CE上报值为Index＝14(对应Buffer Size＝745Bytes)，则基站按照1038Bytes+745Bytes＝1783bytes来分配资源，与UE的期望一致。尽管UE上报BSR时增加了2Bytes的开销，但节省了后续上行调度中的231Bytes的资源开销。
此实施例以short BSR MAC CE为例，同样也适用于Long BSR MAC CE场景。示例性地，图4是本申请实施例提供的一种在同一MAC PDU或同一TTI内所包含的Long BSR MAC CE的配置示意图。如图4所示，两个Long BSR MAC CE包含在同一MAC PDU或同一TTI中，则表达的BSR上报含义为：两个Long BSR MAC CE中的LCG ID对应的Buffer Size之和为该LCG ID的Buffer Size。
需要说明的是，在相关技术中，同一MAC PDU或同一TTI里只能包含一个BSR MAC CE，所以无法把一个buffer size拆分成多个。如果把buffer size拆分为多个值放在不同MAC PDU里进行多次传输，基站可能以最新一次收到的MAC PDU为准，而且增加BSR传输延迟。
实施例3
采用多个BSR串联表达准确的TBS的另一方法(相对于实施例2中的Long BSR MAC CE串联的另外一种方法，可以减小LCG ID的开销)。
图5是本申请实施例提供的一种Long BSR MAC CE的配置示意图。如图5所示，BSR MAC CE里包含LCG ID个数(记为LCG Num)，多个LCG ID，以及每个LCG ID对应的Buffer Size值：LCG ID和Buffer Size值按顺序一一对应。
LCG ID个数(LCG Num)指示有几个，就有几个LCG ID和几个LCG ID对应的Buffer Size值。
同一个BSR MAC CE里的LCG ID可以相同，也就是一个LCG ID值可以对应多个Buffer Size。此时，该LCG ID对应的Buffer Size等于该LCG ID值对应的多个Buffer Size之和。
如果LCG ID Num和LCG ID所占用的比特数不是8bit的整数倍，则通过 reserved bit对齐8比特的整数倍中的最小比特数。
示例性地，图6是本申请实施例提供的另一种Long BSR MAC CE的配置示意图。如图6所示，在BSR MAC CE中的LCG ID Num＝2表示有两个LCG ID，对应两个Buffer Size。两个LCG ID的取值都为1，该BSR MAC CE表达的含义是：LCG ID＝1的Buffer Size值＝Buffer Size 1+Buffer Size 2。
由于LCG ID Num和2个LCG ID占用12个比特，不是8比特的整数倍，采用4个reserved bit对齐8比特的整数倍(LCG ID Num，2个LCG ID和4个reserved bit，共占用16bit，是6bit的整数倍)。
此实施例中，LCG ID也可以为LC ID或DRB ID，每个域占用的比特数只做示例，实际使用值可以与示例不同。
由于该BSR MAC CE的结构与相关技术的标准里的BSR MAC CE的结构不同，UE可以选择其中一种结构，并通过MAC子头里的不同的上行LC ID(LCID for UL-SCH)来区分两种结构；也可以由基站指示UE使用其中一种结构。
实施例4
采用多个BSR串联表达准确的TBS的另一方法(相对于实施例2中的Long BSR MAC CE串联的另外一种方法，可以减小LCG ID的开销，且可以支持更细粒度的BSR上报，也可以按LC ID或DRB ID上报)。
图7是本申请实施例提供的又一种Long BSR MAC CE的配置示意图。如图7所示，在BSR上报中，UE可以按照LCG ID,LC ID or DRB ID上报BSR。每个ID所对应比特的后面可包含若干个Buffer Size，并由Length域指示所包含的Buffer Size数量。该LCG ID，LC ID or DRB ID对应的Buffer Size为该LCG ID、LC ID或DRB ID对应的多个Buffer Size之和。
实施例5
小区广播或基站向UE按逻辑信道、逻辑信道组或DRB配置可支持的最大TBS值或最小TBS值，然后基于最大TBS值或最小TBS值确定Buffer size level表。
在实施例中，小区广播或基站向UE按逻辑信道、逻辑信道组或DRB配置可支持的最大TBS值，UE和基站基于最大TBS值确定Buffer size level表。比如：对于实施例1中的三个Buffer size level表，小区广播最大TBS为967，则使用表3；小区广播最小TBS为1000，则使用表4；如果未广播，则使用表1。
实施例6
小区广播所使用的Buffer size level表指示，UE按照指示选择Buffer size level表。
比如：对于实施例1里的三张表，小区广播中指示使用表3，则UE和基站都按表3理解Buffer size level(Index)的值的含义。如果基站没广播指示，则默认按表1进行BSR上报。
实施例7
小区广播或基站向UE按逻辑信道、逻辑信道组或DRB配置TBS最小值，TBS最大值，和/或粒度。UE和基站自动计算每个Buffer size level(Index)对应的Buffer size值。
在实施例中，不引入新的Buffer size level，而是基于TBS最小值，TBS最大值，及粒度自动计算Buffer size level(Index)对应的Buffer size值。比如基站向UE配置TBS的最小值为2，粒度为2，则可计算出的Buffer size level(Index)对应的Buffer size值为：0,2,4,6,8,10...(0用于指示数据传输完成，或者数据缓冲区为空，不包括在Buffer size值的计算范围内)；基站向UE配置TBS的最小值为2，最大值为1000，则基站计算出的Buffer size步长为(1000-2)/30，floor((1000-2)/30)，第一个可计算出的Buffer size level(Index)对应的Buffer size值为：floor(2+(1000-2)/30)或cell(2+(1000-2)/30)。
其中，Floor表示下取整，cell表示上取整。
基站向UE配置TBS的最小值，最大值，和/或粒度，可以按LCG，LC，或者DRB来配置；如果按照LC或DRB来配置，则UE按LC或DRB来上报BSR。
实施例8
定义更细粒度的BSR值，一个Buffer Size level表占用更多比特。
比如：一个Buffer Size level表占用2byte或3byte，与表1相比，可以表征更细粒度的BSR值。
具体使用哪个BSR表，可以由基站广播指示，或者基站向UE按逻辑信道、逻辑信道组或DRB配置指示，也可以由UE自主选择，并通过MAC子头里的上行LC ID(LCID for UL-SCH)来区分。
实施例9
预定义N个Buffer Size区间，且Buffer Size值为上报的多个区间值的累加结果。
比如：Buffer size levels Table 1(Buffer Size区间0～1000)，UE上报值为XX：占用8bit。
Buffer size levels Table 2(Buffer Size区间1000～10000)，UE上报值为YY：占用4bit。
Buffer size levels Table 3(Buffer Size区间10000～100000)，UE上报值为ZZ：占用4bits。
则：上报的Buffer size值＝ZZ*10000+YY*1000+XX，16bits做多能表达200000的值。
方式1：
Buffer size levels Table 1表示Buffer Size区间0～100000000，UE上报值为XX：占用8bit，间隔T3为524288(2的幂次)。
Buffer size levels Table 2表示Buffer Size区间0～524288，UE上报值为YY：占用4bit，间隔T2为32768。
Buffer size levels Table 3表示Buffer Size区间0～32768，UE上报值为ZZ：占用4bits，间隔T1为2048。
则：UE上报的Buffer size值＝ZZ*524288+YY*32768+XX*2048。
方式2：
Buffer size levels Table 1为8比特表格，UE上报值为XX：占用8bit。
Buffer size levels Table 2表示Buffer Size区间0～T2*16，UE上报值为YY：占用4bit，间隔T2，T2为4096、16384、以及T1*16等。
Buffer size levels Table 3表示Buffer Size区间0～T1*16，UE上报值为ZZ：占用4bits，间隔T1为256、512、768、1024、1536、以及2048等。
则：UE上报的Buffer size值＝ZZ+YY*T2+XX*T1。
方式3：
Buffer size levels Table 1为8比特表格，UE上报值为XX：占用8bit。
Buffer size levels Table 2表示Buffer Size区间T～T*256，其中，T为间隔，T可以为256、512、768、1024、1536以及2048等，UE上报值为YY：占用8bit。
则：UE上报的Buffer size值＝ZZ+YY。
方式4：
Buffer size levels Table 1为8比特表格，UE上报值为XX：占用8bit。
Buffer size levels Table 2表示Buffer Size区间为从8比特表格中抽取出来的16取值作为间隔区间，可以等间隔，也可以不等间隔，UE上报值为YY：占用4bit。
Buffer size levels Table 3表示Buffer Size区间为从8比特表格中抽取出来的16取值作为间隔区间，可以等间隔，也可以不等间隔，UE上报值为ZZ：占用4bits。
则：UE上报的Buffer size值＝ZZ+YY+XX。
在一实施例中，每个表格中多区间间隔的颗粒度不一定相同，例如：相关技术的表格中在大值范围内间隔也不是完全相同的。
在一实施例中，只定义大的表格，例如：buffser size值的间隔为1024，或者，65536，或，32768的大表，基站对每个逻辑信道配置BSR指示大表中index起始到结束的范围。
如果是三个表，假设表1中UE上报的Buffer size值的取值范围Z1～Z2，表2中UE上报的Buffer size值的取值范围Y1～Y2，表3中UE上报的Buffer size值的取值范围X1～X2，则UE上报的Buffer size值的取值范围为：X1+Y1+Z1到X2+Y2+Z2。
如果是两个表，假设表1中UE上报的Buffer size值的取值范围Z1～Z2，表2中UE上报的Buffer size值的取值范围Y1～Y2，则UE上报的Buffer size值的取值范围为：Y1+Z1到Y2+Z2。
在一实施例中，多个表格可以颗粒度越来越小，也可以针对不同取值范围定义不同的表；也可以是一个legacy表格和其他新颗粒度的表格的组合。
在一实施例中，图8是本申请实施例提供的一种信息传输装置的结构框图。 本实施例中的信息传输装置集成于第一通信节点。如图8所示，本实施例包括：第一接收器810和上报模块820。
第一接收器810，配置为接收或确定待传输业务采用的缓冲数据量大小报告相关参数；上报模块820，配置为基于缓冲数据量大小报告相关参数进行缓冲状态报告BSR上报。
在一实施例中，缓冲数据量大小报告相关参数包括如下至少之一：使用的缓冲数据量大小级别表指示、BSR上报类型指示、BSR格式指示、以及支持特定BSR上报方式的指示；所述缓冲数据量大小报告相关参数以LC、LCG或DRB为粒度指示；缓冲数据量大小报告相关参数为第二通信节点通过广播信令或UE专用信令配置。
在一实施例中，应用于第一通信节点的信息传输装置，还包括：指示模块，配置为在接收或确定待传输业务采用的缓冲数据量大小报告相关参数之前，向第二通信节点指示待传输业务对应的业务量信息特征。
在一实施例中，业务量信息特征至少包括下述之一：业务量取值范围；应用层业务类型；期望使用的缓冲数据量大小级别表；期望BSR上报类型指示；期望使用的BSR格式指示。
在一实施例中，指示模块，是设置为：以逻辑信道LC、逻辑信道组LCG或专用无线承载DRB为粒度向第二通信节点指示待传输业务的业务量信息特征。
在一实施例中，第一通信节点以LC或DRB为粒度上报BSR；以LC或DRB为粒度上报BSR包括：在BSR MAC CE中包含LC标识或DRB标识。
在一实施例中，进行BSR上报包括：同一媒体接入控制层协议数据单元MAC PDU或同一传输时间间隔TTI内包含K个BSR MAC CE；一个LCG标识对应的缓冲数据量大小值为K个BSR MAC CE中所述一个LCG标识对应的缓冲数据量大小值的总和；其中，K为正整数。
在一实施例中，进行BSR上报包括：在BSR MAC CE中包括：LCG标识的数量，至少两个LCG标识，以及每个LCG标识对应的缓冲数据量大小值；其中，每个BSR MAC CE中所包含的LCG标识的个数，与LCG标识的数量相同；LCG标识和缓冲数据量大小值按照顺序一一对应；同一个LCG标识在BSR MAC CE出现K次，则该LCG标识对应的缓冲数据量大小值为LCG标识对应的K个缓冲数据量大小值的总和。
在一实施例中，LCG标识的数量和LCG标识所占用的比特数并非8比特的整数倍，通过保留比特对齐8比特的整数倍中的最小比特数。
在一实施例中，在BSR MAC CE中包括：缓冲数据量大小值的数量指示域，LCG标识、LC标识或DRB标识，和K个缓冲数据量大小指示域；K由缓冲数据量大小值的数量指示域决定；LCG标识、LC标识或DRB标识对应的缓冲数据量大小值为对应的所有缓冲数据量大小值的总和；其中，K为正整数。
在一实施例中，应用于第一通信节点的信息传输装置，还包括：第二接收器，配置为在确定待传输业务采用的目标缓冲数据量大小报告相关参数之前，接收第二通信节点按照逻辑信道、逻辑信道组或DRB配置的最大传输块大小TBS值；确定待传输业务采用的缓冲数据量大小报告相关参数，包括：根据最大TBS值确定待传输业务采用的缓冲数据量大小级别表。
在一实施例中，缓冲数据量大小报告相关参数包括：缓冲数据量大小级别表指示；应用于第一通信节点的信息传输装置，还包括：第三接收器，配置为在确定待传输业务采用的目标缓冲数据量大小报告相关参数之前，接收第一通信节点所在小区广播的缓冲数据量大小级别表的指示信息、BSR上报类型指示、BSR格式指示和支持特定BSR上报方式的指示中的至少之一；确定待传输业务采用的缓冲数据量大小报告相关参数，包括：根据缓冲数据量大小级别表的指示信息、BSR上报类型指示、BSR格式指示、支持特定BSR上报方式的指示中的至少之一确定待传输业务采用的缓冲数据量大小级别表。
在一实施例中，缓冲数据量大小报告相关参数包括：缓冲数据量大小级别表对应的缓冲数据量大小值；应用于第一通信节点的信息传输装置，还包括：第四接收器，配置为在确定待传输业务采用的目标缓冲数据量大小报告相关参数之前，接收第一通信节点所在小区广播或第二通信节点发送的按照逻辑信道、逻辑信道组或DRB配置的TBS最小值、TBS最大值和粒度；确定待传输业务采用的缓冲数据量大小报告相关参数，包括：根据TBS最小值、TBS最大值和粒度中的至少两个确定待传输业务采用的缓冲数据量大小级别表对应的缓冲数据量大小值。
在一实施例中，缓冲数据量大小报告相关参数包括：缓冲数据量大小级别表；缓冲数据量大小级别表中每个缓冲数据量大小级别至少占用两个字节。
在一实施例中，缓冲数据量大小报告相关参数包括：缓冲数据量大小值；预配置K个缓冲数据量大小区间；根据K个缓冲数据量大小区间确定待传输业务采用的缓冲数据量大小值；其中，所述缓冲数据量大小值等于K个缓冲数据量大小区间内缓冲数据量大小取值的总和；K为正整数。
本实施例提供的信息传输装置设置为实现图1所示应用于第一通通信节点的实施例的信息传输方法，本实施例提供的信息传输装置实现原理和技术效果类似，此处不再赘述。
在一实施例中，图9是本申请实施例提供的另一种信息传输装置的结构框图。本实施例中的信息传输装置集成于第二通信节点。如图9所示，本实施例包括：第一发送器910和第五接收器920。
第一发送器910，配置为将预先配置的缓冲数据量大小报告相关参数发送至第一通信节点；第五接收器920，配置为接收第一通信节点基于缓冲数据量大小报告相关参数上报的BSR。
在一实施例中，缓冲数据量大小报告相关参数包括如下至少之一：使用的缓冲数据量大小级别表指示，BSR上报类型指示，BSR格式指示，以及支持特定BSR上报方式的指示。
在一实施例中，应用于第二通信节点的信息传输装置，还包括：第六接收器，配置为接收第一通信节点或第三通信节点指示的待传输业务的业务量信息特征；其中，所述业务量信息特征至少包括下述之一：业务量取值范围；应用层业务类型；期望使用的缓冲数据量大小级别表；期望BSR上报类型指示，期望使用的BSR格式指示。
在一实施例中，第三通信节点按照分组数据单元会话、服务质量QoS流或服务质量QoS子流向第二通信节点指示业务量信息特征。
在一实施例中，第二通信节点以LC、LCG或DRB为粒度指示缓冲数据量大小报告相关参数。
在一实施例中，应用于第二通信节点的信息传输装置，还包括：第二发送器，配置为在将预先配置的缓冲数据量大小报告相关参数发送至第一通信节点之前，将按照逻辑信道、逻辑信道组或DRB配置的最大传输块大小TBS值发送至第一通信节点。
在一实施例中，接收第二通信节点基于所述缓冲数据量大小报告相关参数上报的BSR，包括；同一媒体接入控制层协议数据单元MAC PDU或同一传输时间间隔TTI内包含K个BSR MAC CE；一个LCG标识对应的缓冲数据量大小值为K个所述BSR MAC CE中所述一个LCG标识对应的缓冲数据量大小值的总和。
在一实施例中，应用于第二通信节点的信息传输装置，还包括：第三发送器，配置为在将预先配置的缓冲数据量大小报告相关参数发送至第一通信节点之前，将按照逻辑信道、逻辑信道组或DRB配置的TBS最小值、TBS最大值和粒度发送至第一通信节点。
在一实施例中，缓冲数据量大小报告相关参数包括如下至少之一：使用的 缓冲数据量大小级别表指示、BSR上报类型指示、BSR格式指示、以及支持特定BSR上报方式的指示；所述缓冲数据量大小报告相关参数以LC、LCG或DRB为粒度指示；缓冲数据量大小报告相关参数为第二通信节点通过广播信令或UE专用信令配置。
在一实施例中，业务量信息特征至少包括下述之一：业务量取值范围；应用层业务类型；期望使用的缓冲数据量大小级别表；期望BSR上报类型指示；期望使用的BSR格式指示。
在一实施例中，第二通信节点以逻辑信道LC、逻辑信道组LCG或专用无线承载DRB为粒度接收第一通信节点指示的待传输业务对应的业务量信息特征。
在一实施例中，接收第一通信节点以LC或DRB为粒度上报的BSR；以LC或DRB为粒度上报BSR包括：在BSR MAC CE中包含LC标识或DRB标识。
在一实施例中，进行BSR上报包括：同一媒体接入控制层协议数据单元MAC PDU或同一传输时间间隔TTI内包含K个BSR MAC CE；一个LCG标识对应的缓冲数据量大小值为K个BSR MAC CE中所述一个LCG标识对应的缓冲数据量大小值的总和；其中，K为正整数。
在一实施例中，进行BSR上报包括：在BSR MAC CE中包括：LCG标识的数量，至少两个LCG标识，以及每个LCG标识对应的缓冲数据量大小值；其中，每个BSR MAC CE中所包含的LCG标识的个数，与LCG标识的数量相同；LCG标识和缓冲数据量大小值按照顺序一一对应；同一个LCG标识在BSR MAC CE出现K次，则该LCG标识对应的缓冲数据量大小值为LCG标识对应的至少两个缓冲数据量大小值的总和。
在一实施例中，LCG标识的数量和LCG标识所占用的比特数并非8比特的整数倍，通过保留比特对齐8比特的整数倍中的最小比特数。
在一实施例中，在BSR MAC CE中包括：缓冲数据量大小值的数量指示域，LCG标识、LC标识或DRB标识，和K个缓冲数据量大小指示域；K由缓冲数据量大小值的数量指示域决定；LCG标识、LC标识或DRB标识中的任一标识对应的缓冲数据量大小值为所述任一标识对应的K个缓冲数据量大小值的总和；其中，K为正整数。
在一实施例中，缓冲数据量大小报告相关参数包括：缓冲数据量大小级别表；缓冲数据量大小级别表中每个缓冲数据量大小级别至少占用两个字节。
在一实施例中，缓冲数据量大小报告相关参数包括：缓冲数据量大小值；确定待传输业务采用的缓冲数据量大小报告相关参数，包括：预配置K个缓冲 数据量大小区间；根据K个缓冲数据量大小区间确定待传输业务采用的缓冲数据量大小值；其中，所述缓冲数据量大小值等于K个缓冲数据量大小区间内缓冲数据量大小取值的总和；K为正整数。
本实施例提供的信息传输装置设置为实现图2所示应用于第二通信节点的实施例的信息传输方法，本实施例提供的信息传输装置实现原理和技术效果类似，此处不再赘述。
图10是本申请实施例提供的一种信息传输设备的结构示意图。如图10所示，本申请提供的设备，包括：处理器1010、存储器1020和通信模块1030。该设备中处理器1010的数量可以是一个或者多个，图10中以一个处理器1010为例。该设备中存储器1020的数量可以是一个或者多个，图10中以一个存储器1020为例。该设备的处理器1010、存储器1020和通信模块1030可以通过总线或者其他方式连接，图10中以通过总线连接为例。在该实施例中，该设备为可以为终端侧(比如，用户设备)。
存储器1020作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请任意实施例的设备对应的程序指令/模块(例如，信息传输装置中的第一接收器810和上报模块820)。存储器1020可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储器1020可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器1020可包括相对于处理器1010远程设置的存储器，这些远程存储器可以通过网络连接至设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及互联网、企业内部网、局域网、移动通信网的组合。
通信模块1030，配置为与其它通信节点进行通信交互。
在信息传输设备为第一通信节点的情况下，上述提供的设备可设置为执行上述任意实施例提供的应用于第一通信节点的信息传输方法，具备相应的功能和效果。
在信息传输设备为第二通信节点的情况下，上述提供的设备可设置为执行上述任意实施例提供的应用于第二通信节点的信息传输方法，具备相应的功能和效果。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执 行指令在由计算机处理器执行时用于执行一种应用于第一通信节点的信息传输方法，该方法包括：接收或确定待传输业务采用的缓冲数据量大小报告相关参数；基于缓冲数据量大小报告相关参数进行BSR上报。
本申请实施例还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种应用于第二通信节点的信息传输方法，该方法包括：将预先配置的缓冲数据量大小报告相关参数发送至第一通信节点；接收第一通信节点基于缓冲数据量大小报告相关参数上报的BSR。
本领域内的技术人员应明白，术语用户设备涵盖任何类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，通过硬件，或者通过软件和硬件的组合来实现。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FPGA)以及基于多核处理器架构的处理器。

Claims (24)

  1. 一种信息传输方法，应用于第一通信节点，包括：
    接收或确定待传输业务采用的缓冲数据量大小报告相关参数；
    基于所述缓冲数据量大小报告相关参数进行缓冲状态报告BSR上报。
  2. 根据权利要求1所述的方法，其中，所述缓冲数据量大小报告相关参数包括如下至少之一：使用的缓冲数据量大小级别表指示、BSR上报类型指示、BSR格式指示、以及支持特定BSR上报方式的指示；所述缓冲数据量大小报告相关参数以逻辑信道LC、逻辑信道组LCG或专用无线承载DRB为粒度指示；
    所述缓冲数据量大小报告相关参数为第二通信节点通过广播信令或用户设备UE专用信令配置。
  3. 根据权利要求2所述的方法，还包括：
    向第二通信节点指示所述待传输业务对应的业务量信息特征。
  4. 根据权利要求3所述的方法，其中，所述业务量信息特征至少包括下述之一：业务量取值范围；应用层业务类型；期望使用的缓冲数据量大小级别表；期望BSR上报类型指示；期望使用的BSR格式指示。
  5. 根据权利要求3所述的方法，其中，向第二通信节点指示所述待传输业务对应的业务量信息特征包括：以LC、LCG或DRB为粒度向第二通信节点指示待传输业务的业务量信息特征。
  6. 根据权利要求2所述的方法，其中，所述第一通信节点以LC或DRB为粒度上报BSR；所述以LC或DRB为粒度上报BSR包括：在缓冲状态报告媒体接入控制层-控制单元BSR MAC CE中包含LC标识或DRB标识。
  7. 根据权利要求1所述的方法，其中，进行BSR上报包括：同一媒体接入控制层协议数据单元MAC PDU或同一传输时间间隔TTI内包含K个BSR MAC CE；
    一个LCG标识对应的缓冲数据量大小值为所述K个BSR MAC CE中所述一个LCG标识对应的缓冲数据量大小值的总和；其中，K为正整数。
  8. 根据权利要求1所述的方法，其中，进行BSR上报包括：在BSR MAC CE中包括：LCG标识的数量，至少两个LCG标识，以及每个LCG标识对应的缓冲数据量大小值；所述LCG标识和所述缓冲数据量大小值按照顺序一一对应；
    同一个LCG标识在BSR MAC CE出现K次，则该LCG标识对应的缓冲数据量大小值为所述LCG标识对应的K个缓冲数据量大小值的总和。
  9. 根据权利要求8所述的方法，其中，所述LCG标识的数量和所述LCG标识所占用的比特数并非8比特的整数倍，通过保留比特对齐8比特的整数倍中的最小比特数。
  10. 根据权利要求1所述的方法，其中，进行BSR上报包括：在BSR MAC CE中包括：缓冲数据量大小值的数量指示域，LCG标识、LC标识或DRB标识中的一个标识，和K个缓冲数据量大小指示域；K由缓冲数据量大小值的数量指示域决定；
    所述LCG标识、LC标识或DRB标识中的一个标识对应的缓冲数据量大小值为所述一个标识对应的K个缓冲数据量大小值的总和；K为正整数。
  11. 根据权利要求1所述的方法，其中，接收第二通信节点按照LC、LCG或DRB配置的最大传输块大小TBS值；
    所述确定待传输业务采用的缓冲数据量大小报告相关参数，包括：
    根据所述最大TBS值确定待传输业务采用的缓冲数据量大小级别表。
  12. 根据权利要求1所述的方法，还包括：
    接收所述第一通信节点所在小区广播的缓冲数据量大小级别表的指示信息、BSR上报类型指示、BSR格式指示和支持特定BSR上报方式的指示中的至 少之一；
    确定待传输业务采用的缓冲数据量大小报告相关参数，包括：
    根据所述缓冲数据量大小级别表的指示信息、BSR上报类型指示、BSR格式指示和支持特定BSR上报方式的指示中的至少之一确定待传输业务采用的缓冲数据量大小级别表。
  13. 根据权利要求1所述的方法，还包括：
    接收第一通信节点所在小区广播或第二通信节点发送的按照LC、LCG或DRB配置的TBS最小值、TBS最大值和粒度；
    确定待传输业务采用的缓冲数据量大小报告相关参数，包括：
    根据所述TBS最小值、所述TBS最大值和所述粒度中的至少两个确定待传输业务采用的缓冲数据量大小级别表对应的缓冲数据量大小值。
  14. 根据权利要求1所述的方法，其中，所述缓冲数据量大小报告相关参数包括：缓冲数据量大小级别表；
    所述缓冲数据量大小级别表中每个缓冲数据量大小级别至少占用两个字节。
  15. 根据权利要求1所述的方法，其中，所述缓冲数据量大小报告相关参数包括：缓冲数据量大小值；
    所述确定待传输业务采用的缓冲数据量大小报告相关参数，包括：
    预配置K个缓冲数据量大小区间；
    根据所述K个缓冲数据量大小区间确定待传输业务采用的缓冲数据量大小值；
    其中，所述缓冲数据量大小值等于K个缓冲数据量大小区间内缓冲数据量大小取值的总和；K为正整数。
  16. 一种信息传输方法，应用于第二通信节点，包括：
    将预先配置的缓冲数据量大小报告相关参数发送至第一通信节点；
    接收第一通信节点基于所述缓冲数据量大小报告相关参数上报的缓冲状态报告BSR。
  17. 根据权利要求16所述的方法，其中，所述缓冲数据量大小报告相关参数包括如下至少之一：使用的缓冲数据量大小级别表指示，BSR上报类型指示，BSR格式指示，以及支持特定BSR上报方式的指示；
    所述方法，还包括：
    接收第一通信节点或第三通信节点指示的待传输业务的业务量信息特征；其中，所述业务量信息特征至少包括下述之一：业务量取值范围；应用层业务类型；期望使用的缓冲数据量大小级别表；期望BSR上报类型指示，期望使用的BSR格式指示。
  18. 根据权利要求17所述的方法，其中，所述第三通信节点按照分组数据单元会话、服务质量QoS流或QoS子流向第二通信节点指示业务量信息特征。
  19. 根据权利要求17所述的方法，其中，所述第二通信节点以逻辑信道LC、逻辑信道组LCG或专用无线承载DRB为粒度指示所述缓冲数据量大小报告相关参数。
  20. 根据权利要求16所述的方法，其中，将按照LC、LCG或DRB配置的最大传输块大小TBS值发送至第一通信节点。
  21. 根据权利要求16所述的方法，其中，所述接收第一通信节点基于所述缓冲数据量大小报告相关参数上报的BSR，包括；
    同一媒体接入控制层协议数据单元MAC PDU或同一传输时间间隔TTI内包含K个缓冲状态报告媒体接入控制层控制单元BSR MAC CE；
    一个LCG标识对应的缓冲数据量大小值为所述K个BSR MAC CE中所述一个LCG标识对应的缓冲数据量大小值的总和；K为正整数。
  22. 根据权利要求16所述的方法，其中，将按照LC、LCG或DRB配置的TBS最小值、TBS最大值和粒度发送至第一通信节点。
  23. 一种信息传输设备，包括：通信模块，存储器，以及至少一个处理器；
    所述通信模块，配置为与其它通信节点进行通信交互；
    所述存储器，配置为存储至少一个程序；
    当所述至少一个程序被所述至少一个处理器执行时，所述至少一个处理器实现如上述权利要求1-15或16-22中任一项所述的方法。
  24. 一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现如上述权利要求1-15或16-22中任一项所述的方法。
PCT/CN2022/138293 2021-12-31 2022-12-12 信息传输方法、设备和存储介质 Ceased WO2023124928A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CA3244994A CA3244994A1 (en) 2021-12-31 2022-12-12 METHOD AND DEVICE FOR TRANSMITTING INFORMATION AND INFORMATION MEDIUM
KR1020247025881A KR20240137593A (ko) 2021-12-31 2022-12-12 정보 전송 방법, 디바이스, 및 저장 매체
EP22914183.3A EP4460136A4 (en) 2021-12-31 2022-12-12 INFORMATION TRANSMISSION METHOD AND DEVICE AND STORAGE MEDIUM
US18/759,627 US20240357419A1 (en) 2021-12-31 2024-06-28 Information transmission method and device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111673790.6A CN115866580A (zh) 2021-12-31 2021-12-31 信息传输方法、设备和存储介质
CN202111673790.6 2021-12-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/759,627 Continuation US20240357419A1 (en) 2021-12-31 2024-06-28 Information transmission method and device, and storage medium

Publications (1)

Publication Number Publication Date
WO2023124928A1 true WO2023124928A1 (zh) 2023-07-06

Family

ID=85652798

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/138293 Ceased WO2023124928A1 (zh) 2021-12-31 2022-12-12 信息传输方法、设备和存储介质

Country Status (6)

Country Link
US (1) US20240357419A1 (zh)
EP (1) EP4460136A4 (zh)
KR (1) KR20240137593A (zh)
CN (2) CN119031405A (zh)
CA (1) CA3244994A1 (zh)
WO (1) WO2023124928A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117714475A (zh) * 2023-12-08 2024-03-15 江苏云工场信息技术有限公司 用于边缘云存储的智能管理方法及系统

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240373284A1 (en) * 2023-05-01 2024-11-07 Qualcomm Incorporated Bsr enhancements for xr applications
EP4712639A1 (en) * 2023-05-11 2026-03-18 Beijing Xiaomi Mobile Software Co., Ltd. Information processing method and apparatus, and storage medium
CN119835681A (zh) * 2023-10-12 2025-04-15 华为技术有限公司 一种缓存状态报告的上报方法及相关设备
WO2026064891A1 (en) * 2024-09-24 2026-04-02 Nokia Shanghai Bell Co., Ltd. Buffer status reporting

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102291771A (zh) * 2010-06-21 2011-12-21 中兴通讯股份有限公司 一种实现缓冲区状态上报的方法及系统
CN102547669A (zh) * 2012-02-10 2012-07-04 大唐移动通信设备有限公司 数据缓存状态上报及上行资源调度方法和设备
CN103889066A (zh) * 2014-03-12 2014-06-25 中国科学技术大学 一种智能电网通信中精细上行资源调度方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8625415B2 (en) * 2010-04-02 2014-01-07 Nokia Siemens Networks Oy Dynamic buffer status report selection for carrier aggregation
KR20240089487A (ko) * 2022-01-28 2024-06-20 지티이 코포레이션 버퍼 상태 보고(bsr) 기술

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102291771A (zh) * 2010-06-21 2011-12-21 中兴通讯股份有限公司 一种实现缓冲区状态上报的方法及系统
CN102547669A (zh) * 2012-02-10 2012-07-04 大唐移动通信设备有限公司 数据缓存状态上报及上行资源调度方法和设备
CN103889066A (zh) * 2014-03-12 2014-06-25 中国科学技术大学 一种智能电网通信中精细上行资源调度方法

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117714475A (zh) * 2023-12-08 2024-03-15 江苏云工场信息技术有限公司 用于边缘云存储的智能管理方法及系统
CN117714475B (zh) * 2023-12-08 2024-05-14 江苏云工场信息技术有限公司 用于边缘云存储的智能管理方法及系统

Also Published As

Publication number Publication date
CN119031405A (zh) 2024-11-26
CA3244994A1 (en) 2025-06-13
EP4460136A1 (en) 2024-11-06
EP4460136A4 (en) 2025-04-23
KR20240137593A (ko) 2024-09-20
US20240357419A1 (en) 2024-10-24
CN115866580A (zh) 2023-03-28

Similar Documents

Publication Publication Date Title
US8488527B2 (en) Apparatus and method for facilitating radio resource dimensioning for communication services
WO2023124928A1 (zh) 信息传输方法、设备和存储介质
CN109644486B (zh) 终端在无线通信系统中发送侧链路控制信息的方法和使用该方法的终端
CN102685895B (zh) 一种上行数据的调度方法、系统及装置
US9713030B2 (en) Transmission data processing method and devices
CN102291771B (zh) 一种实现缓冲区状态上报的方法及系统
CN107925995B (zh) 一种用户设备、网络设备及数据传输方法
US11974317B2 (en) Data transmission method and apparatus, computer device, and system
US20230095067A1 (en) Communication method and communication device
CN111263469A (zh) 确定参数值的方法和设备
CN103636242A (zh) eMBMS管理方法、多媒体广播组播业务协调实体和基站
US20240259867A1 (en) Method, device, and system for buffer status report
CN103999526A (zh) 上行资源分配方法及装置
CN110463119A (zh) 用于增强调度信息指示的扩展调度请求(sr)
CN111417198B (zh) 一种资源配置方法、网络侧设备及终端
CN111148225B (zh) 资源调度方法、装置及设备
US9084163B2 (en) Apparatus and method for performing carrier switching operation for E-MBS service in multicarrier system
CN110139388B (zh) 缓冲区状态的上报、数据调度方法、终端及网络侧设备
KR101211515B1 (ko) 사용자 기기, 리소스를 결정하기 위한 방법, 리소스를 보고하기 위한 방법, 및 리소스를 분배하기 위한 시스템
CN101741707A (zh) 一种上行数据传输方法、装置及通信系统
CN115604777A (zh) 资源分配方法、终端和计算机可读存储介质
CN114339617A (zh) Nr小区中mbs资源的配置使用方法及装置
CN102083127B (zh) 基于多载波hsupa的调度信息上报方法、装置及系统
JP7392844B2 (ja) 車両通信サービスの通信方法、装置及び通信システム
CN101272609B (zh) 一种无线通信系统中ip电话调度组的管理方法

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: 22914183

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202417057656

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 20247025881

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022914183

Country of ref document: EP

Effective date: 20240731