WO2020151700A1 - 副链路缓存状态报告发送、接收方法和设备 - Google Patents

副链路缓存状态报告发送、接收方法和设备 Download PDF

Info

Publication number
WO2020151700A1
WO2020151700A1 PCT/CN2020/073482 CN2020073482W WO2020151700A1 WO 2020151700 A1 WO2020151700 A1 WO 2020151700A1 CN 2020073482 W CN2020073482 W CN 2020073482W WO 2020151700 A1 WO2020151700 A1 WO 2020151700A1
Authority
WO
WIPO (PCT)
Prior art keywords
bsr
data
preset information
preset
format
Prior art date
Application number
PCT/CN2020/073482
Other languages
English (en)
French (fr)
Inventor
郑倩
杨晓东
马玥
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to KR1020217026549A priority Critical patent/KR20210114524A/ko
Priority to EP20745946.2A priority patent/EP3917254A4/en
Publication of WO2020151700A1 publication Critical patent/WO2020151700A1/zh
Priority to US17/383,792 priority patent/US12108278B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • 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/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • 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
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1215—Wireless traffic scheduling for collaboration of different radio technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present disclosure relates to the field of communication technology, and more specifically to a method and device for sending and receiving a secondary link buffer status report.
  • a side link (Sidelink, SL), also called a side link or a side link, is used for direct data transmission between terminal equipment (User Equipment, UE) without using network equipment.
  • the secondary link buffer status report (Sidelink Buffer Status Report, SL BSR) is used by the secondary link terminal equipment (User Equipment, UE) to inform the network equipment of a logical channel group (Logical channel group, based on the destination address (Destination) of the short distance service). The amount of data (in bytes) to be sent for all logical channels in the LCG).
  • the truncated SLBSR is used for reporting.
  • the truncation measure is to report the size of the buffered data contained in the LCG as much as possible.
  • the secondary link in addition to broadcast services, can also support unicast services and multicast services, and can also support LTE Sidelink and NR Sidelink at the same time, which makes uplink resources insufficient to report all
  • the original SL BSR transmission method used for the data size of the secondary link logical channel buffer is no longer applicable.
  • the embodiments of the present disclosure provide a method and device for sending and receiving a secondary link buffer status report, so as to provide a more applicable SL BSR sending solution.
  • a method for sending a secondary link buffer status report is provided, which is applied to a terminal device, and the method includes:
  • a truncated secondary link buffer status report SL BSR is sent, at least one of the SL BSRs
  • the domain is associated with the preset information
  • At least one SL BSR format of SL BSR is sent based on the preset priority, the SL BSR format is based on the preset of the buffer data The information is ok.
  • a method for receiving a secondary link buffer status report is provided, which is applied to a network device, and the method includes:
  • SL BSR Receive a truncated secondary link buffer status report SL BSR, where the truncated SL BSR is a pre-determination based on the buffer data when the terminal device reports the total amount of buffer data of all secondary link logical channels when the uplink resources are insufficient. It is assumed that the information is sent, and at least one field of the SL BSR is associated with the preset information; or,
  • the at least one SL BSR format SL BSR is the terminal equipment when the uplink resources are insufficient to report the total amount of data buffered data of all secondary link logical channels, according to the preset priority And the SL BSR format is determined based on preset information of the buffered data.
  • a terminal device in a third aspect, includes:
  • the sending module is configured to send a truncated secondary link buffer status report SL BSR based on the preset information of the buffer data when the uplink resources are insufficient to report the total amount of buffer data of all secondary link logical channels, the SL At least one field of the BSR is associated with the preset information; or, when the uplink resources are insufficient to report the total amount of buffered data of all secondary link logical channels, at least one SL BSR format SL is sent based on the preset priority BSR, the SL BSR format is determined based on preset information of the buffered data.
  • a network device in a fourth aspect, includes:
  • the receiving module is configured to receive a truncated secondary link buffer status report SL BSR, where the truncated SL BSR is based on the total amount of data that the terminal device reports the buffer data of all secondary link logical channels when the uplink resources are insufficient
  • the preset information of the buffered data is sent, and at least one field of the SL BSR is associated with the preset information; or, used to receive at least one SL BSR format of the SL BSR, the at least one SL BSR format
  • the SL BSR is sent by the terminal device according to the preset priority when the uplink resources are insufficient to report the total amount of buffered data of all secondary link logical channels, and the SL BSR format is based on the preset information of the buffered data definite.
  • a terminal device in a fifth aspect, includes a memory, a processor, and a wireless communication program that is stored on the memory and can run on the processor, and the wireless communication program is executed by the processor.
  • the steps of the method described in the first aspect are realized when executed.
  • a network device in a sixth aspect, includes a memory, a processor, and a wireless communication program that is stored on the memory and can run on the processor, and the wireless communication program is executed by the processor.
  • the steps of the method described in the second aspect are realized when executed.
  • a computer-readable medium is provided, and a wireless communication program is stored on the computer-readable medium.
  • the wireless communication program is executed by a processor, the method according to the first aspect or the second aspect is implemented. step.
  • the terminal device can provide a better applicable buffer status reporting scheme when the uplink resources are insufficient to report the total amount of buffer data of all secondary link logical channels; and, when the buffer data is reported At the same time as the amount of data, it can also directly or indirectly carry the preset information of the buffered data in the SL BSR, so that the network equipment can learn more comprehensive terminal equipment buffer status information, so as to better allocate resources to the terminal equipment and improve Communication effectiveness.
  • FIG. 1 is a schematic flowchart of a method for sending a secondary link buffer status report according to an embodiment of the present disclosure.
  • FIG. 2 is one of the schematic diagrams of the format of the SLBSR provided by an embodiment of the present disclosure.
  • FIG. 3 is a second schematic diagram of the format of the SLBSR provided by an embodiment of the present disclosure.
  • Fig. 4 is a schematic flowchart of a method for receiving a secondary link buffer status report provided by an embodiment of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a terminal device 500 provided by an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a network device 600 provided by an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a terminal device 700 provided by an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a network device 800 provided by an embodiment of the present disclosure.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • Terminal equipment can communicate with at least one core network via a radio access network (Radio Access Network, RAN), and terminal equipment can It is a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal.
  • UE User Equipment
  • RAN Radio Access Network
  • terminal equipment can It is a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal.
  • a mobile terminal such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal.
  • it can be a portable, pocket-sized, handheld, built-in computer or vehicle-mounted mobile device, which is connected to a wireless access network.
  • Exchange language and/or data Exchange language and/or data.
  • a network device is a device deployed in a wireless access network device to receive feedback information for a secondary link.
  • the network device may be a base station, and the base station may be a base station (Base Transceiver Station, in GSM or CDMA).
  • BTS Base Transceiver Station
  • it can also be a base station (NodeB) in WCDMA, an evolved base station (evolutional Node B, eNB, or e-NodeB) and a 5G base station (gNodeB, gNB) in LTE, and a subsequent evolutionary communication system Network-side equipment, however, the words used do not constitute a limitation on the protection scope of the present disclosure.
  • the size of the sequence number of each process does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not be implemented in the embodiments of the present disclosure.
  • the process constitutes any limitation.
  • the following first describes a method for sending a secondary link buffer status report provided by an embodiment of the present disclosure.
  • the method for sending a secondary link buffer status report may include:
  • Step 101 When the uplink resources are insufficient to report the total amount of data buffered for all secondary link logical channels, based on the preset information of the buffered data, send a truncated secondary link buffer status report SL BSR, the SLBSR At least one field of is associated with the preset information; or, when the uplink resources are not enough to report the total amount of data buffered for all secondary link logical channels, at least one SLBSR in the SL BSR format is sent based on the preset priority The SL BSR format is determined based on preset information of the buffered data.
  • the uplink resources are not enough to report the total amount of buffered data of all secondary link logical channels
  • the data amount of buffered data of the secondary link logical channel can be realized through two specific implementations. (Or the size of the data) report, the following are separately explained.
  • a truncated secondary link buffer status report (Sidelink Buffer Status Report, SL BSR) is sent, and the truncated At least one domain of the SL BSR is associated with the preset information.
  • SL BSR Segment Buffer Status Report
  • at least one field of the truncated SL BSR can be associated with the preset information in two ways, implicitly or explicitly, which will be described with examples below.
  • the preset information includes, but is not limited to, at least one of a radio access technology (Radio Access Technology, RAT) type, an SL service transmission mode, and a quality of service (Quality of Service, QoS) parameter.
  • a radio access technology Radio Access Technology, RAT
  • SL service transmission mode an SL service transmission mode
  • QoS Quality of Service
  • the RAT type may include at least one of a Long Term Evolution (LTE) type, a New Radio (NR) type, and a RAT type that may appear subsequently.
  • LTE Long Term Evolution
  • NR New Radio
  • the SL service transmission mode may include at least one of unicast, multicast, and broadcast.
  • QoS parameters may include, but are not limited to, at least one of the following: priority of a data packet or data flow (Priority), latency of a data packet or data flow (Latency, in ms), reliability of a data packet or data flow (Reliability) , Expressed as a percentage (%)), the communication range of the data packet or data stream (Communication range, the unit is meter), the size of the data packet or data stream (payload, the unit is byte (Byte)), the data packet Or the transmission rate of the data stream (Transmission rate, expressed in message/sec) and the data rate of the data packet or data stream (Data rate, in Mbps), etc.
  • the format of the SL BSR includes the destination address index (destination index) field, the logical channel group index (Logical Channel Group Index, LCG ID) field, and the to-be-transmitted A data volume (Buffer size level) field, wherein at least one of the destination address index field and the logical channel group index field is associated with the preset information.
  • the original SL BSR may be the SL BSR shown in Table 1 below, and the corresponding code point is 10111.
  • the truncated SL BSR refers to the SL BSR that is truncated on the basis of the original SL BSR.
  • the destination address index field and/or the logical channel group index field are implicitly associated with the RAT type, and specifically may be implicitly associated with the LTE type and/or NR type.
  • the destination address index field and/or the logical channel group index field are implicitly associated with the SL transmission mode, and specifically may be implicitly associated with at least one of unicast, groupcast, and broadcast .
  • the destination address index field and/or the logical channel group index field are implicitly associated with the QoS parameter, and specifically may be implicitly associated with the combination of one or more of the above QoS parameters.
  • the so-called implicit association can be understood as establishing in advance the mapping relationship between the destination address index field and/or the logical channel group index field in the SL BSR format and the preset information, so that when the terminal device sends the SL to the network device After the BSR, the network device can know the preset information carried in the SLBSR based on the mapping relationship, without directly carrying the preset information in the SLBSR.
  • the format of the SL BSR includes: the destination address index (destination index) field, the logical channel group index (Logical Channel Group Index, LCG ID) field, and the to-be-transmitted A data volume (Buffer size level) field and at least one additional field, wherein the at least one additional field is used to carry the preset information, so as to realize the association between the at least one additional field and the preset information.
  • the additional field can be considered as a field added to the format of the SL BSR specifically for carrying the preset information.
  • the format of the SL BSR may include the following fields: destination address index field, logical channel group index field, data volume to be transmitted field, and RAT type field, where the RAT type field is an additional field, so
  • the RAT type field is used to carry RAT type information, such as carrying LTE PC5 interface information, or carrying NR PC5 interface information.
  • the PC5 interface is an interface for direct communication between terminal devices without network equipment.
  • the SL BSR format can include the following fields: destination address index field, logical channel group index field, data volume to be transmitted field, and SL transmission mode field, where the SL transmission mode field is an additional Domain, the SL transmission mode domain is used to carry SL transmission mode information, such as unicast, multicast, or broadcast information.
  • the format of the SL BSR may include the following fields: destination address index field, logical channel group index field, data volume to be transmitted field, RAT type field, and SL transmission mode field, where RAT type field and SL transmission
  • the mode field is two additional fields.
  • the RAT type field is used to carry RAT type information, such as LTE PC5 interface information, or NR PC5 interface information;
  • the SL transmission mode field is used to carry SL transmission mode information, such as Carry unicast, multicast or broadcast information.
  • the network device can learn more comprehensive information about the buffer status of the terminal device, so as to better allocate resources to the terminal device and improve communication effectiveness.
  • the above-mentioned sending a truncated SL BSR based on the preset information of the buffered data may specifically include: preset based on the buffered data of all secondary link logical channels Information to determine the reporting order of the data volume of different types of buffered data; based on the reporting sequence, a truncated SL BSR is sent to report the total amount of buffered data of all secondary link logical channels when the uplink resources are insufficient Reporting of the data volume of cached data.
  • the target cache data that is ranked first based on the reporting order it is possible to determine the target cache data that is ranked first based on the reporting order; then send the SL BSR that firstly carries the data volume of the target cache data in order, that is, send as much as possible the prior cache data quantity.
  • the amount of data of different types of buffered data is determined based on the preset information
  • the reporting sequence includes: determining the reporting sequence of the data amount of the buffered data of the different RAT types in the buffered data based on the preset priorities of the different RAT types.
  • the preset priorities of different RAT types can be specified by protocols, configured by network equipment, or pre-configured by terminal equipment.
  • the priority of LTE type> the priority of NR type can be pre-configured
  • the corresponding reporting order can be LTE type buffered data data volume> NR type buffered data data volume
  • pre-configured NR type priority>LTE type priority the corresponding reporting order may be NR type buffered data data volume>LTE type buffered data data volume.
  • the different types of buffer data are determined based on the preset information
  • the order of reporting the amount of data includes: determining the order of reporting the amount of data of the buffered data corresponding to the different SL service transmission modes in the buffered data based on the preset priorities of different SL service transmission modes.
  • the preset priorities of different SL transmission modes can be specified by the protocol, configured by the network device, or pre-configured by the terminal device. For example, if the SL transmission mode includes unicast, multicast, and broadcast, you can pre-configure the priority of the unicast transmission mode>the priority of the multicast transmission mode>the priority of the broadcast transmission mode, and the corresponding reporting order can be unicast transmission Data volume of the buffered data corresponding to the mode>Data volume of the buffered data corresponding to the multicast transmission mode>Data volume of the buffered data corresponding to the broadcast transmission mode; Or, the priority of the broadcast transmission mode can be pre-configured>The priority of the multicast transmission mode Level>Priority of unicast transmission mode, the corresponding reporting order can be the data volume of buffered data corresponding to broadcast transmission mode>data volume of buffered data corresponding to multicast transmission mode>data volume of buffered data corresponding to unicast transmission mode .
  • the data of different types of buffered data are determined based on the preset information
  • the order of reporting the amount of data includes: determining the order of reporting the amount of data of the buffered data corresponding to the different QoS parameters in the buffered data based on the preset priorities of different QoS parameters.
  • the preset priorities of different QoS parameters can be stipulated by protocols, configured by network equipment or pre-configured by terminal equipment. For example, if the QoS parameters include multiple priority data packets or data streams, you can pre-configure the priority of the higher priority data packet or data stream> the priority of the lower priority data packet or data stream.
  • the corresponding reporting order can be the data volume of high-priority data packets or data streams> the data volume of low-priority data packets or data streams; or, if the parameters include data packets or data streams with multiple delays, pre- Configure the priority of the data packet or data stream with lower delay> the priority of the data packet or data stream with higher delay, the corresponding reporting order can be the data volume of the data packet or data stream with low delay> high time The amount of delayed data packets or data streams, etc.
  • the truncated SL BSR first carries as much data volume of the buffered data corresponding to the NR PC5 interface as possible, and then carries as much data volume of the buffered data corresponding to the LTE PC5 interface as possible until it is used for sending The uplink resources of the SL BSR are used up; or, if the reporting order is the data volume of the LTE-type buffered data> the data volume of the NR-type buffered data, the truncated SL BSR carries as much buffer data corresponding to the LTE PC5 interface as possible Secondly, as much data as possible to carry the buffered data corresponding to the NR PC5 interface until the uplink resources used to send the SL BSR are used up
  • SL transmission mode for buffered data of all secondary link logical channels, for example, it specifically includes three transmission modes: unicast, multicast and broadcast, and the reporting order is the buffer corresponding to the unicast transmission mode.
  • the truncated SL BSR will first carry as many high-priority data packets or data flows as possible, and then carry as many low-priority data packets as possible. Level of data packets or data flow until the uplink resources used to send SL BSR are used up.
  • the truncated SL BSR first carries as many low-latency data packets or data streams as possible, and then as much as possible to carry high-latency data packets Or the data volume of the data stream until the uplink resources for sending SL BSR are used up.
  • the truncated SL BSR sent by the terminal device carries the preset information, so that the network device can Get more comprehensive information about the buffer status of the terminal device, so as to better allocate resources to the terminal device and improve the effectiveness of communication.
  • At least one SL BSR format of SL BSR is sent based on a preset priority, and the SL BSR format is determined based on preset information of the buffered data.
  • the preset information includes but is not limited to at least one of a radio access technology (Radio Access Technology, RAT) type and an SL service transmission mode.
  • RAT Radio Access Technology
  • the RAT type may include at least one of a Long Term Evolution (LTE) type and a New Radio (NR) type.
  • the SL service transmission mode may include at least one of unicast, multicast, and broadcast.
  • the sending of the SL BSR of at least one SL BSR format based on the preset priority may include: based on the preset information, determining multiple SL BSR formats for sending the data amount of the buffered data; For the preset priorities of the multiple SL BSR formats, at least one SL BSR format SL BSR is sent.
  • multiple SL BSR formats can be predefined based on the preset information, and the priority of these multiple SL BSR formats can be defined, so that the total amount of data buffered for all secondary link logical channels is reported when the uplink resources are insufficient.
  • at least one SL BSR format is selected to send the SL BSR.
  • SL BSR formats can be understood as dedicated SL BSR formats, and since these various SL BSR formats are defined based on the preset information, sending the SL BSR format of the SL BSR to the network device means At the same time, the preset information is carried.
  • an SL BSR format for sending one or more data volume combinations of buffered data.
  • the SL BSR format used to send the data volume of LTE-type buffered data and/or the data volume of NR-type buffered data can be defined, and the corresponding SL BSR format can be expressed as NR Sidelink BSR format, LTE Sidelink BSR format , NR/LTE Sidelink BSR format, etc.; or, you can define the SL BSR format that is used to send the data volume of the buffered data corresponding to at least one of unicast, multicast, and broadcast, and the corresponding SL BSR format It can be expressed as unicast Sidelink BSR format, groupcast Sidelink BSR format, broadcast Sidelink BSR format, etc.
  • these various SL BSR formats include the following fields: a destination address index field, a logical channel group index field, and a data volume to be transmitted field.
  • the SL BSR format generally includes a destination address index field, a logical channel group index field, and a data volume to be transmitted field.
  • logical channel groups are often divided into 4 groups.
  • the logical channel group index occupies 2 bits in the SL BSR, which is used to describe the LCG ID corresponding to the buffer area of the terminal device; the length of the destination address index can be configured, and the common 16 groups , Occupies 4 bits; the amount of data to be transmitted is arranged in the descending order of the priority of the SL logical channels contained in the LCG, and occupies 6 bits, which is used to specify the transmission timing interval (Transmission Timing Interval, TTI After all MAC protocol data units (Protocol Data Unit, PDU) in) are generated, the radio link control (Radio Link Control, RLC) layer and packet data convergence protocol (Packet) of all logical channels in the LCG corresponding to the short-distance service destination address The sum of the remaining valid data to be transmitted in the Data Convergence Protocol
  • Figures 2 and 3 respectively show schematic diagrams of two formats of SL BSR in the related art.
  • Figure 2 is a schematic diagram of BSR format with an even number of index (index)
  • Figure 3 is a schematic diagram of the value of index (index).
  • one row represents one octet (1 Oct)
  • N represents the maximum value of the index.
  • the MAC layer uses the MAC control element (CE) to report the BSR, and the SL BSR and the truncated SL BSR use the same MAC control element (CE).
  • CE MAC control element
  • Each MAC CE adopts a logical channel ID (Logical Channel ID, LCID).
  • Table 1 below lists the LCID values and codepoints in the uplink shared channel (UpLink-Shared Channel, UL-SCH). relationship.
  • the code point "10111" corresponds to the SL BSR format of related technologies.
  • the display association in the first specific embodiment mentioned above is equivalent to introducing at least one additional field on the basis of the SL BSR format of the related technology.
  • it is equivalent to introducing and NR on the basis of Table 1.
  • SL BSR a new format of SL BSR based on the related technology's SL BSR format.
  • Table 3 it is equivalent to introducing NR Sidelink on the basis of Table 1.
  • BSR and LTE Sidelink BSR are two new SL BSR formats, and the code points of these two new SL BSR formats are to be determined.
  • the method shown in FIG. 1 may further include: determining preset priorities of the multiple SL BSR formats based on the preset information.
  • the preset information of the buffered data of all secondary link logical channels includes the RAT type, and there is more than one RAT type
  • the preset information of the multiple SL BSR formats is determined based on the preset information.
  • Setting the priority includes: determining the preset priority of the multiple SL BSR formats based on different RAT types.
  • the priority of the NR sidelink BSR format >the priority of the LTE sidelink BSR format.
  • the SL BSR in the NR sidelink BSR format can be sent first.
  • the priority of the LTE sidelink BSR format >the priority of the NR sidelink BSR format.
  • the SL BSR in the LTE sidelink BSR format can be sent first.
  • the multiple SL BSRs are determined based on the preset information
  • the preset priority of the format includes: determining the preset priority of the multiple SL BSR formats based on different SL service transmission modes.
  • the unicast sidelink BSR format SL BSR can be sent first, followed by the groupcast sidelink BSR format SL BSR, and finally the broadcast sidelink BSR format.
  • the priority of the broadcast sidelink BSR format may be defined> the priority of the groupcast sidelink BSR format> the priority of the unicast sidelink BSR format.
  • the SL BSR in broadcast sidelink BSR format can be sent first, the SL BSR in groupcast sidelink BSR format is sent second, and the unicast sidelink BSR format is sent last. SL BSR.
  • the preset priority of the multiple SL BSR formats is determined based on the preset information The level includes: determining the preset priority of the multiple SL BSR formats based on the SL service transmission mode and the RAT type.
  • the priority of NR groupcast sidelink BSR format can be defined> Priority of LTE broadcast sidelink BSR format.
  • the SL BSR in the NR groupcast sidelink BSR format can be sent first, and the SL BSR in the LTE broadcast sidelink BSR format can be sent second.
  • the priority of LTE broadcast sidelink BSR format may be defined> NR The priority of the broadcast sidelink BSR format.
  • the SL BSR in the LTE broadcast sidelink BSR format can be sent first, and the SL BSR in the NR broadcast sidelink BSR format can be sent second.
  • the method for sending a secondary link buffer status report provided by the embodiment of this specification, on the one hand, can provide a better applicability when the uplink resources are insufficient to report the total amount of buffer data of all secondary link logical channels.
  • it while reporting the data volume of the cached data, it can also directly or indirectly carry the preset information of the cached data in the SL BSR, so that the network device can learn more comprehensive terminal device information Cache status information, so as to better allocate resources to terminal devices and improve communication effectiveness.
  • the foregoing description corresponds to the method for sending a secondary link buffer status report for a terminal device, and the following describes a method for receiving a secondary link buffer status report provided by an embodiment of the present disclosure with reference to FIG. 4.
  • a secondary link buffer status report receiving method provided by an embodiment of the present disclosure is applied to a network device, and the method may include:
  • Step 401 Receive a truncated secondary link buffer status report SL BSR, where the truncated SL BSR is based on the buffer when the terminal equipment reports the total amount of buffer data of all secondary link logical channels when the uplink resources are insufficient.
  • the preset information of the data is sent, and at least one field of the SL BSR is associated with the preset information; or, at least one SL BSR in the SL BSR format is received, and the at least one SL BSR in the SL BSR format is received
  • the terminal device sends the total amount of buffered data of all secondary link logical channels and sends it according to the preset priority, and the SL BSR format is determined based on the preset information of the buffered data.
  • the data amount of buffered data of the secondary link logical channel can be realized through two specific implementations. The reception of (or data size) will be described separately below.
  • the network device receives the truncated secondary link buffer status report SL BSR.
  • the truncated SL BSR received by the network device is sent by the terminal device based on the reporting sequence of the data volume of different types of buffered data, the reporting sequence is determined based on the preset information, and the received truncated At least one field of the short SL BSR is associated with the preset information.
  • At least one field of the truncated SL BSR can be associated with the preset information in two ways, implicitly or explicitly, which are described below with examples.
  • the preset information includes but is not limited to at least one of the radio access technology RAT type, SL service transmission mode and QoS parameters.
  • the RAT type may include at least one of LTE type, NR type, and new RAT types appearing subsequently.
  • the SL service transmission mode may include at least one of unicast, multicast, and broadcast.
  • QoS parameters may include but are not limited to at least one of the following: priority of a data packet or data flow (Priority), latency of a data packet or data flow (Latency, in ms), reliability of a data packet or data flow (Reliability , Expressed as a percentage (%)), the communication range of the data packet or data stream (Communication range, the unit is meter), the size of the data packet or data stream (payload, the unit is byte (Byte)), the data packet Or the transmission rate of the data stream (Transmission rate, expressed in message/sec) and the data rate of the data packet or data stream (Data rate, in Mbps), etc.
  • the format of the SL BSR includes the destination address index (destination index) field, the logical channel group index (Logical Channel Group Index, LCG ID) field and the to-be-transmitted A data volume (Buffer size level) field, wherein at least one of the destination address index field and the logical channel group index field is associated with the preset information.
  • the method shown in FIG. 4 may further include: determining the preset information based on at least one of the destination address index field and the logical channel group index field.
  • the so-called implicit association can be understood as the establishment of the mapping relationship between the destination address index field and/or the logical channel group index field in the SL BSR format and the preset information in advance, so that when the network device receives the SL BSR Therefore, the preset information carried by the SL BSR can be known based on the mapping relationship, without directly carrying the preset information in the SL BSR.
  • the format of the SL BSR includes: a destination address index field, a logical channel group index field, a data volume field to be transmitted, and at least one additional field, where the At least one additional domain is used to carry the preset information, so as to realize the association between the at least one additional domain and the preset information. That is, the additional field can be considered as a field specially used to carry the preset information added to the format of the SL BSR.
  • the method shown in FIG. 4 may further include: determining the preset information based on the at least one additional domain.
  • the network device can learn more comprehensive information about the buffer status of the terminal device, so as to better allocate resources to the terminal device and improve communication effectiveness.
  • the terminal device determines the reporting sequence of different types of buffered data, and how to send the truncated SL BSR based on the reporting sequence of different types of buffered data, please refer to the corresponding secondary link buffer for the terminal device above.
  • the description of the embodiment of the status report sending method will not be repeated here.
  • the network device receives at least one SL BSR format of SL BSR, and as an example, the receiving at least one SL BSR format of SL BSR includes: preset based on multiple SL BSR formats Priority, receiving at least one SL BSR format SL BSR; wherein, the multiple SL BSR formats are determined by the terminal device based on the preset information.
  • the preset information includes but is not limited to at least one of RAT type and SL service transmission mode.
  • the RAT type may include at least one of LTE type, NR type, and new RAT types appearing subsequently.
  • the SL service transmission mode may include at least one of unicast, multicast, and broadcast.
  • These various SL BSR formats can be understood as dedicated SL BSR formats, and because these various SL BSR formats are defined based on the preset information, the network device receives the SL BSR in the SL BSR format, which means At the same time, the preset information is received.
  • these various SL BSR formats include the following fields: a destination address index field, a logical channel group index field, and a data volume to be transmitted field.
  • the display association in the first specific embodiment mentioned above is equivalent to introducing at least one additional field on the basis of the SL BSR format of the related technology. For example, as shown in Table 2 above, it is equivalent to introducing and Sidelink BSR associated with NR and LTE.
  • the terminal device determines the preset priorities of the multiple SL BSR formats based on preset information, and how to send at least one SL BSR format of SL BSR based on the preset priorities of the multiple SL BSR formats .
  • the terminal device determines the preset priorities of the multiple SL BSR formats based on preset information, and how to send at least one SL BSR format of SL BSR based on the preset priorities of the multiple SL BSR formats .
  • the embodiment of this specification provides a method for receiving a secondary link buffer status report.
  • a buffer with better applicability can be provided.
  • Status reporting scheme while receiving the data volume of the cached data, it can also directly or indirectly receive the preset information of the cached data, so that the network equipment can learn more comprehensive terminal equipment cache status information, and thus more Good allocation of resources to terminal equipment to improve communication effectiveness.
  • the foregoing description corresponds to the receiving method of the secondary link buffer status report for the network device.
  • the terminal device and the network device according to the embodiments of the present disclosure will be described in detail below with reference to FIGS. 5 to 6.
  • FIG. 5 shows a schematic structural diagram of a terminal device provided by an embodiment of the present disclosure.
  • the terminal device 500 may include a sending module 501.
  • the sending module 501 is configured to send a truncated secondary link buffer status report SL BSR based on the preset information of the buffer data when the uplink resources are insufficient to report the total amount of buffer data of all secondary link logical channels, the At least one field of the SL BSR is associated with the preset information; or, when the uplink resources are insufficient to report the total amount of data buffered for all secondary link logical channels, at least one SL BSR format is sent based on the preset priority SL BSR, the SL BSR format is determined based on preset information of the cache data.
  • the sending module 501 can implement the buffered data for the secondary link logical channels through two specific implementations.
  • the report of the amount of data (or data size) is described below.
  • the sending module 501 may send the truncated SL BSR based on the preset information of the buffered data of all secondary link logical channels, and at least one field of the sent truncated SL BSR is the same as the The preset information is associated.
  • at least one field of the truncated SL BSR can be associated with the preset information in two ways, implicitly or explicitly, which will be described with examples below.
  • the preset information includes but is not limited to at least one of RAT type, SL service transmission mode and QoS parameter.
  • the RAT type may include at least one of an LTE type, an NR type, and a new RAT type that subsequently appears.
  • the SL service transmission mode may include at least one of unicast, multicast, and broadcast.
  • QoS parameters may include but are not limited to at least one of the following: priority of a data packet or data flow (Priority), latency of a data packet or data flow (Latency, in ms), reliability of a data packet or data flow (Reliability , Expressed as a percentage (%)), the communication range of the data packet or data stream (Communication range, the unit is meter), the size of the data packet or data stream (payload, the unit is byte (Byte)), the data packet Or the transmission rate of the data stream (Transmission rate, expressed in message/sec) and the data rate of the data packet or data stream (Data rate, in Mbps), etc.
  • the format of the SL BSR includes the destination address index (destination index) field, the logical channel group index (Logical Channel Group Index, LCG ID) field, and the to-be-transmitted A data volume (Buffer size level) field, wherein at least one of the destination address index field and the logical channel group index field is associated with the preset information.
  • the so-called implicit association can be understood as establishing in advance the mapping relationship between the destination address index field and/or the logical channel group index field in the SL BSR format and the preset information, so that when the terminal device sends the SL to the network device After the BSR, the network device can know the preset information carried in the SLBSR based on the mapping relationship, without directly carrying the preset information in the SLBSR.
  • the format of the SL BSR includes: the destination address index (destination index) field, the logical channel group index (Logical Channel Group Index, LCG ID) field, and the to-be-transmitted A data volume (Buffer size level) field and at least one additional field, wherein the at least one additional field is used to carry the preset information, so as to realize the association between the at least one additional field and the preset information. That is, the additional field can be considered as a field added to the format of the SL BSR specifically for carrying the preset information.
  • the network device can learn more comprehensive information about the buffer status of the terminal device, so as to better allocate resources to the terminal device and improve communication effectiveness.
  • the sending module 501 can be used to: based on the preset information of the buffered data of all secondary link logical channels, determine the reporting order of the data amount of different types of buffered data; In the reporting sequence, a truncated SL BSR is sent to report the data amount of the buffered data when the uplink resources are insufficient to report the total amount of buffered data of all secondary link logical channels.
  • the sending module 501 can be used to determine the target buffer data that is ranked first based on the reporting order; and then send the SL BSR that firstly carries the data volume of the target buffer data in order, that is, send as many as possible in the order of the target buffer data. The number of cached data before.
  • the sending module 501 can be used to determine the preset priority of different RAT types The order in which the data amount of the cached data of different RAT types in the cached data is reported.
  • the preset priorities of different RAT types may be specified by protocols, configured by network equipment, or pre-configured by terminal equipment.
  • the sending module 501 can be used to: preset based on different SL service transmission modes The priority determines the reporting order of the data volume of the buffered data corresponding to different SL service transmission modes in the buffered data.
  • the preset priorities of different SL transmission modes can be specified by the protocol, configured by the network device, or pre-configured by the terminal device.
  • the sending module 501 can be used to: determine based on the preset priorities of different QoS parameters The reporting sequence of the data amount of the buffer data corresponding to different QoS parameters in the buffer data.
  • the preset priorities of different QoS parameters can be stipulated by protocols, configured by network equipment or pre-configured by terminal equipment.
  • the sending module 501 sends the truncated SL BSR based on the reporting sequence of different types of buffer data sizes, please refer to the description of the method embodiment shown in FIG. 1 above, and the description will not be repeated here.
  • the sending module 501 is configured to send at least one SL BSR format of SL BSR based on a preset priority, and the SL BSR format is determined based on preset information of the buffered data.
  • the preset information includes but is not limited to at least one of RAT type and SL service transmission mode.
  • the RAT type may include at least one of LTE type, NR type, and new RAT types appearing subsequently.
  • the SL service transmission mode may include at least one of unicast, multicast, and broadcast.
  • the sending module 501 may be configured to: based on the preset information, determine multiple SL BSR formats for sending the data volume of the buffered data; based on the preset priorities of the multiple SL BSR formats, send at least An SL BSR in the SL BSR format.
  • the sending module 501 can predefine multiple SL BSR formats based on the preset information, and define the priority of these multiple SL BSR formats, so that when the uplink resources are insufficient, the buffer data of all secondary link logical channels is reported. For the total amount of data, at least one SL BSR format is selected to send the SL BSR according to the preset priorities of these multiple SL BSR formats.
  • SL BSR formats can be understood as dedicated SL BSR formats, and since these various SL BSR formats are defined based on the preset information, sending the SL BSR format of the SL BSR to the network device means At the same time, the preset information is carried.
  • these various SL BSR formats include the following fields: a destination address index field, a logical channel group index field, and a data volume to be transmitted field.
  • the display association in the first specific implementation above is equivalent to introducing at least one additional field on the basis of the SL BSR format of the related technology. For example, as shown in Table 2 above, it is equivalent to introducing and Sidelink BSR associated with NR and LTE.
  • the terminal device 500 shown in FIG. 5 may further include: a priority determining module, configured to determine the multiple SL BSR formats based on the preset information Preset priority.
  • the priority determining module may be used to determine the multiple RAT based on different RAT types.
  • the preset priority of the SL BSR format may be used to determine the multiple RAT based on different RAT types.
  • the priority determination module can be used to: based on different SL service transmission modes To determine the preset priorities of the multiple SL BSR formats.
  • the priority determination module may be used to: based on the SL service transmission mode and the RAT type To determine the preset priorities of the multiple SL BSR formats.
  • the terminal device 500 provided by the embodiment of the present specification, on the one hand, can provide a more applicable buffer status reporting solution when the uplink resources are insufficient to report the total amount of data buffered for all secondary link logical channels.
  • the terminal device 500 while reporting the data volume of the cached data, it can also directly or indirectly carry the preset information of the cached data in the SL BSR, so that the network equipment can learn more comprehensive terminal equipment cache status information, thereby Better allocate resources to terminal equipment and improve communication effectiveness.
  • the terminal device 500 shown in FIG. 5 may be used to implement the above-described embodiments of the method for sending a secondary link buffer status report shown in FIG. 1.
  • the terminal device 500 shown in FIG. 5 may be used to implement the above-described embodiments of the method for sending a secondary link buffer status report shown in FIG. 1.
  • the terminal device 500 has been described above, and the network device 600 provided by the embodiment of the present disclosure will be described below with reference to FIG. 6.
  • FIG. 6 shows a schematic structural diagram of a network device provided by an embodiment of the present disclosure.
  • the network device 600 may include: a receiving module 601.
  • the receiving module 601 is configured to receive a truncated secondary link buffer status report SL BSR, where the truncated SL BSR is the total amount of data that the terminal device reports the buffered data of all secondary link logical channels when the uplink resources are insufficient.
  • the preset information of the buffered data is sent, and at least one field of the SL BSR is associated with the preset information; or, it is used to receive at least one SLBSR format of the SL BSR, the at least one SL BSR format
  • the SL BSR is sent by the terminal device according to the preset priority when the uplink resources are insufficient to report the total amount of buffered data of all secondary link logical channels, and the SL BSR format is based on the preset information of the buffered data definite.
  • the data amount of buffered data of the secondary link logical channel can be realized through two specific implementations. The reception of (or data size) will be described separately below.
  • the receiving module 601 is configured to receive the truncated secondary link buffer status report SL BSR.
  • the truncated SL BSR received by the receiving module 601 is sent by the terminal device based on the reporting sequence of the data volume of different types of buffered data, and the reporting sequence is determined based on the preset information, and At least one field of the received truncated SL BSR is associated with the preset information.
  • At least one field of the truncated SL BSR can be associated with the preset information in two ways, implicitly or explicitly, which will be described with examples below.
  • the preset information includes but is not limited to at least one of a radio access technology RAT type, an SL service transmission mode, and QoS parameters.
  • the RAT type may include at least one of LTE type, NR type, and new RAT types appearing subsequently.
  • SL service transmission methods can include at least one of unicast, multicast, and broadcast;
  • QoS parameters can include, but are not limited to, at least one of the following: priority of data packets or data streams, and timing of data packets or data streams.
  • Latency (unit: ms), reliability of a data packet or data stream (Reliability, expressed as a percentage (%)), communication range of a data packet or data stream (Communication range, unit of meter), data packet Or the size of the data stream (payload, in bytes), the transmission rate of the data packet or data stream (Transmission rate, expressed in message/sec), and the data rate of the data packet or data stream (Data rate, the unit is Mbps), etc.
  • the format of the SL BSR includes the destination address index (destination index) field, the logical channel group index (Logical Channel Group Index, LCG ID) field, and the to-be-transmitted A data volume (Buffer size level) field, wherein at least one of the destination address index field and the logical channel group index field is associated with the preset information.
  • the network device shown in FIG. 6 may further include: a first determining module, configured to determine the destination address index field and the logical channel group index field based on at least one of the Preset information.
  • the so-called implicit association can be understood as the establishment of the mapping relationship between the destination address index field and/or the logical channel group index field in the SL BSR format and the preset information in advance, so that when the network device receives the SL BSR Therefore, the preset information carried by the SL BSR can be known based on the mapping relationship, without directly carrying the preset information in the SL BSR.
  • the format of the SL BSR includes: a destination address index field, a logical channel group index field, a data volume field to be transmitted, and at least one additional field, where the At least one additional domain is used to carry the preset information, so as to realize the association between the at least one additional domain and the preset information.
  • the additional field can be considered as a field added to the format of the SL BSR specifically for carrying the preset information.
  • the network device shown in FIG. 6 may further include: a first determining module, for determining the preset information based on the at least one additional domain.
  • the network device can learn more comprehensive information about the buffer status of the terminal device, so as to better allocate resources to the terminal device and improve communication effectiveness.
  • the terminal device determines the reporting sequence of different types of buffered data, and how to send the truncated SL BSR based on the reporting sequence of different types of buffered data, please refer to the corresponding secondary link buffer for the terminal device above.
  • the description of the embodiment of the status report sending method will not be repeated here.
  • the receiving module 601 is configured to receive at least one SL BSR format of SL BSR, and as an example, the receiving module 601 can be specifically used to: based on preset priorities of multiple SL BSR formats, Receive an SL BSR in at least one SL BSR format; wherein, the multiple SL BSR formats are determined by the terminal device based on the preset information.
  • the preset information includes but is not limited to at least one of RAT type and SL service transmission mode.
  • the RAT type may include at least one of LTE type, NR type, and new RAT types appearing subsequently.
  • the SL service transmission mode may include at least one of unicast, multicast, and broadcast.
  • These various SL BSR formats can be understood as dedicated SL BSR formats, and because these various SL BSR formats are defined based on the preset information, the network device receives the SL BSR in the SL BSR format, which means At the same time, the preset information is received.
  • these various SL BSR formats include the following fields: a destination address index field, a logical channel group index field, and a data volume to be transmitted field.
  • the display association in the first specific implementation above is equivalent to introducing at least one additional field on the basis of the SL BSR format of the related technology. For example, as shown in Table 2 above, it is equivalent to introducing and Sidelink BSR associated with NR and LTE.
  • the terminal device determines the preset priorities of the multiple SL BSR formats based on preset information, and how to send at least one SL BSR format of SL BSR based on the preset priorities of the multiple SL BSR formats .
  • the terminal device determines the preset priorities of the multiple SL BSR formats based on preset information, and how to send at least one SL BSR format of SL BSR based on the preset priorities of the multiple SL BSR formats .
  • the network device 600 provided by the embodiment of this specification, on the one hand, can provide a better applicable buffer status reporting solution when the uplink resources are insufficient to report the total amount of data buffered for all secondary link logical channels; On the one hand, while receiving the data volume of the buffered data, it can also directly or indirectly receive the preset information of the buffered data, so that the network device can learn more comprehensive information about the buffer status of the terminal device, so as to better provide the terminal device Allocate resources to improve communication effectiveness.
  • the above-mentioned network device 600 shown in FIG. 6 may be used to implement various embodiments of the above-mentioned method for receiving a secondary link buffer status report shown in FIG. 4, and please refer to the above-mentioned method embodiment for related details.
  • Fig. 7 is a schematic structural diagram of a terminal device according to another embodiment of the present disclosure.
  • the terminal device 700 shown in FIG. 7 includes: at least one processor 701, a memory 702, at least one network interface 704, and a user interface 703.
  • the various components in the terminal device 700 are coupled together through the bus system 705.
  • the bus system 705 is used to implement connection and communication between these components.
  • the bus system 705 also includes a power bus, a control bus, and a status signal bus.
  • various buses are marked as the bus system 705 in FIG. 7.
  • the user interface 703 may include a display, a keyboard, a pointing device (for example, a mouse, a trackball), a touch panel or a touch screen, etc.
  • the memory 702 in the embodiment of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be Read-Only Memory (ROM), Programmable Read-Only Memory (Programmable ROM, PROM), Erasable Programmable Read-Only Memory (Erasable PROM, EPROM), and Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Link Dynamic Random Access Memory
  • DRRAM Direct Rambus RAM
  • the memory 702 stores the following elements, executable modules or data structures, or a subset of them, or an extended set of them: the operating system 7021 and the application 7022.
  • the operating system 7021 includes various system programs, such as a framework layer, a core library layer, and a driver layer, which are used to implement various basic services and process hardware-based tasks.
  • the application program 7022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services.
  • a program for implementing the method of the embodiments of the present disclosure may be included in the application program 7022.
  • the terminal device 700 further includes: a computer program stored in the memory 702 and capable of running on the processor 701, and when the computer program is executed by the processor 701, each of the foregoing methods for sending a secondary link buffer status report is implemented. Process, and can achieve the same technical effect, in order to avoid repetition, I will not repeat it here.
  • the methods disclosed in the foregoing embodiments of the present disclosure may be applied to the processor 701 or implemented by the processor 701.
  • the processor 701 may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method can be completed by an integrated logic circuit of hardware in the processor 701 or instructions in the form of software.
  • the aforementioned processor 701 may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present disclosure can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present disclosure may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a computer-readable storage medium that is mature in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the computer-readable storage medium is located in the memory 702, and the processor 701 reads information in the memory 702, and completes the steps of the foregoing method in combination with its hardware.
  • a computer program is stored on the computer-readable storage medium, and when the computer program is executed by the processor 701, the steps of the foregoing method for sending a secondary link buffer status report are implemented.
  • FIG. 8 is a structural diagram of a network device applied in an embodiment of the present disclosure, which can realize the details of the above-mentioned secondary link buffer status report receiving method and achieve the same effect.
  • the network device 800 includes: a processor 801, a transceiver 802, a memory 803, a user interface 804, and a bus interface, where:
  • the network device 800 further includes: a computer program stored in the memory 803 and capable of running on the processor 801.
  • the computer program When the computer program is executed by the processor 801, it implements the above-mentioned secondary link buffer status report receiving method.
  • Each process can achieve the same technical effect. In order to avoid repetition, it will not be repeated here.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, at least one processor represented by the processor 801 and various circuits of the memory represented by the memory 803 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further description will be given herein.
  • the bus interface provides the interface.
  • the transceiver 802 may be a plurality of elements, that is, include a transmitter and a receiver, and provide a unit for communicating with various other devices on a transmission medium.
  • the user interface 804 may also be an interface that can externally and internally connect the required device.
  • the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 801 is responsible for managing the bus architecture and general processing, and the memory 803 can store data used by the processor 801 when performing operations.
  • the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in at least one application specific integrated circuit (ASIC), digital signal processor (Digital Signal Processor, DSP), digital signal processing device (DSP Device, DSPD), programmable logic device (Programmable Logic Device, PLD), Field-Programmable Gate Array (FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, and other electronic units used to perform the functions described in this disclosure Or a combination thereof.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • DSP Device digital signal processing device
  • DSPD digital signal processing device
  • PLD programmable logic device
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present disclosure can be implemented by modules (for example, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • the software codes can be stored in the memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • the embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored.
  • the computer program is executed by a processor, each process of the above-mentioned method for sending feedback information of the secondary link is realized, and can To achieve the same technical effect, in order to avoid repetition, I will not repeat them here.
  • the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk, etc.
  • the embodiments of the present disclosure also provide a computer program product including instructions.
  • the computer runs the instructions of the computer program product, the computer executes the above-mentioned secondary link feedback information sending method or the above-mentioned secondary link feedback information sending method .
  • the computer program product can be run on the aforementioned network device.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present disclosure essentially or the part that contributes to the related technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including several
  • the instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present disclosure.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .
  • the program can be stored in a computer readable storage medium. When executed, it may include the procedures of the above-mentioned method embodiments.
  • the storage medium may be a magnetic disk, an optical disc, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM), etc.

Landscapes

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

Abstract

本公开提供一种副链路缓存状态报告发送、接收方法和设备，所述发送方法包括：在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息，发送截短的副链路缓存状态报告SL BSR，所述SL BSR的至少一个域与所述预设信息相关联；或者，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于预设优先级发送至少一种SL BSR格式的SL BSR，所述SL BSR格式是基于所述缓存数据的预设信息确定的。

Description

副链路缓存状态报告发送、接收方法和设备
相关申请的交叉引用
本申请主张在2019年1月23日在中国提交的中国专利申请号No.201910065287.9的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，更具体地涉及一种副链路缓存状态报告发送、接收方法和设备。
背景技术
副链路(Sidelink，SL)，也称侧链路或边链路，用于终端设备(User Equipment，UE)之间不通过网络设备而直接进行数据传输。副链路缓存状态报告(Sidelink Buffer Status Report，SL BSR)用于副链路终端设备(User Equipment，UE)告诉网络设备基于近距离服务目的地址(Destination)的一个逻辑信道组(Logical channel group,LCG)内所有逻辑信道待发的数据量(以字节为单位)。在长期演进(Long Term Evolution，LTE)系统中，由于副链路仅支持广播业务，因此当上行资源不够上报所有副链路逻辑信道缓存的数据大小时，采用截短的SL BSR进行上报，具体的截短措施为尽可能多的上报LCG所包含的缓存数据大小。
然而，在新空口(New Radio，NR)系统中，除了广播业务，副链路还可以支持单播业务和组播业务，并且还可以同时支持LTE Sidelink和NR Sidelink，这使得上行资源不够上报所有副链路逻辑信道缓存的数据大小时所采用的原有SL BSR发送方法不再适用。
发明内容
本公开实施例提供一种副链路缓存状态报告发送、接收方法和设备，以提供一种适用性更好的SL BSR发送方案。
第一方面，提供了一种副链路缓存状态报告发送方法，应用于终端设备， 所述方法包括：
在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息，发送截短的副链路缓存状态报告SL BSR，所述SL BSR的至少一个域与所述预设信息相关联；或者，
在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于预设优先级发送至少一种SL BSR格式的SL BSR，所述SL BSR格式是基于所述缓存数据的预设信息确定的。
第二方面，提供了一种副链路缓存状态报告接收方法，应用于网络设备，所述方法包括：
接收截短的副链路缓存状态报告SL BSR，所述截短的SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息发送的，且所述SL BSR的至少一个域与所述预设信息相关联；或者，
接收至少一种SL BSR格式的SL BSR，所述至少一种SL BSR格式的SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，按预设优先级发送的，且所述SL BSR格式是基于所述缓存数据的预设信息确定的。
第三方面，提供了一种终端设备，该终端设备包括：
发送模块，用于在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息，发送截短副链路缓存状态报告SL BSR，所述SL BSR的至少一个域与所述预设信息相关联；或者，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于预设优先级发送至少一种SL BSR格式的SL BSR，所述SL BSR格式是基于所述缓存数据的预设信息确定的。
第四方面，提供了一种网络设备，该网络设备包括：
接收模块，用于接收截短副链路缓存状态报告SL BSR，所述截短的SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息发送的，且所述SL BSR的至少一个域与所述预设信息相关联；或者，用于接收至少一种SL BSR格式的SL BSR， 所述至少一种SL BSR格式的SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，按预设优先级发送的，且所述SL BSR格式是基于所述缓存数据的预设信息确定的。
第五方面，提供了一种终端设备，该网络设备包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的无线通信程序，所述无线通信程序被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种网络设备，该终端设备包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的无线通信程序，所述无线通信程序被所述处理器执行时实现如第二方面所述的方法的步骤。
第七方面，提供了一种计算机可读介质，所述计算机可读介质上存储有无线通信程序，所述无线通信程序被处理器执行时实现如第一方面或第二方面所述的方法的步骤。
在本公开实施例中，终端设备可以在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，提供一种适用性更好的缓存状态上报方案；并且，在上报缓存数据的数据量的同时，还能直接或间接的在SL BSR中携带缓存数据的预设信息，因此可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
附图说明
为了更清楚地说明本公开实施例或相关技术中的技术方案，下面将对实施例或相关技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本公开实施例提供的一种副链路缓存状态报告发送方法的流程示意图。
图2是本公开实施例提供的SL BSR的格式示意图之一。
图3是本公开实施例提供的SL BSR的格式示意图之二。
图4是本公开实施例提供的一种副链路缓存状态报告接收方法的流程示 意图。
图5是本公开实施例提供的终端设备500的一种结构示意图。
图6是本公开实施例提供的网络设备600的一种结构示意图。
图7是本公开实施例提供的终端设备700的一种结构示意图。
图8是本公开实施例提供的网络设备800的一种结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本公开中的技术方案，下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都应当属于本公开保护的范围。
应理解，本公开实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)或全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、第5代(5 th generation，5G)系统，或者说NR系统。
终端设备(User Equipment，UE)，也可称之为移动终端(Mobile Terminal)、移动终端设备等，可以经无线接入网(Radio Access Network，RAN)与至少一个核心网进行通信，终端设备可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。
网络设备是一种部署在无线接入网设中用于接收针对副链路的反馈信息的装置，所述网络设备可以为基站，所述基站可以是GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB)，还可以是LTE中的演进型基站(evolutional Node B，eNB或e-NodeB)及5G基站(gNodeB，gNB)，以及后续演进通信系统中的网络侧设备，然而用词并不构成对本公开保护范围的限制。
需要说明的是，在描述具体实施例时，各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本公开实施例的实施过程构成任何限定。
下面先对本公开实施例提供的一种副链路缓存状态报告发送方法进行说明。
如图1所示，本公开实施例提供的一种副链路缓存状态报告发送方法，可以包括：
步骤101、在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息，发送截短的副链路缓存状态报告SL BSR，所述SL BSR的至少一个域与所述预设信息相关联；或者，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于预设优先级发送至少一种SL BSR格式的SL BSR，所述SL BSR格式是基于所述缓存数据的预设信息确定的。
也就是说，在本公开实施例中，当上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，可以通过两种具体实施方式实现副链路逻辑信道的缓存数据的数据量(或者说数据大小)的上报，下面分别进行说明。
在第一种具体实施方式中，基于所有副链路逻辑信道的缓存数据的预设信息，发送截短的副链路缓存状态报告(Sidelink Buffer Status Report，SL BSR)，且发送的截短的SL BSR的至少一个域与所述预设信息相关联。其中，截短的SL BSR的至少一个域可通过隐式或显式两种方式与所述预设信息相关联， 下面会分别举例说明。
其中，所述预设信息包括但不限于无线接入技术(Radio Access Technology，RAT)类型、SL业务传输方式和服务质量(Quality of Service，QoS)参数中的至少一种。
RAT类型可以包括长期演进(Long Term Evolution，LTE)类型、新空口(New Radio，NR)类型和后续可能出现的RAT类型中的至少一种。
SL业务传输方式可以包括单播、组播和广播中的至少一种。
QoS参数可以包括但不限于如下至少一种：数据包或数据流的优先级(Priority)、数据包或数据流的时延(Latency，单位为ms)、数据包或数据流的可靠性(Reliability，用百分数(％)表示)、数据包或数据流的通信距离(Communication range，单位为米(meter))、数据包或数据流的大小(payload，单位为字节(Byte))、数据包或数据流的发送速率(Transmission rate，用message/sec表示)和数据包或数据流的数据速率(Data rate，单位为Mbps)，等等。
在第一个例子中，截短的SL BSR的至少一个域通过隐式的方式与所述预设信息相关联。具体的，所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中包括：目的地址索引(destination index)域、逻辑信道组索引(Logical Channel Group Index，LCG ID)域和待传输数据量(Buffer size level)域，其中，所述目的地址索引域和所述逻辑信道组索引域中的至少一个与所述预设信息相关联。
需要说明的是，在本公开实施例中，原SL BSR可以是下表1中所示的SL BSR，对应的码点为10111。并且，截短的SL BSR，指的是在原SL BSR基础上截短得到的SL BSR。
例如，目的地址索引域和/或逻辑信道组索引域与RAT类型隐式关联，具体可以与LTE类型和/或NR类型隐式关联。
再如，目的地址索引域和/或逻辑信道组索引域与SL传输方式隐式关联， 具体可以与单播(unicast)、组播(groupcast)和广播(broadcast)中的至少一种隐式关联。
又如，目的地址索引域和/或逻辑信道组索引域与QoS参数隐式关联，具体可以与上文中的一种或多种QoS参数的组合隐式关联。
所谓隐式关联，可以理解为是，事先建立SL BSR的格式中的目的地址索引域和/或逻辑信道组索引域与所述预设信息的映射关系，这样当终端设备向网络设备发送该SL BSR之后，网络设备就可以基于该映射关系知道该SLBSR携带的所述预设信息，而不需要在该SL BSR中直接携带所述预设信息。
在第二个例子中，截短的SL BSR的至少一个域通过显式的方式与所述预设信息相关联。具体的，所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中包括：目的地址索引(destination index)域、逻辑信道组索引(Logical Channel Group Index，LCG ID)域、待传输数据量(Buffer size level)域和至少一个附加域，其中，所述至少一个附加域用于承载所述预设信息，以实现所述至少一个附加域与所述预设信息的关联。
也即，附加域可以认为是在所述SL BSR的格式中增加的专门用于承载所述预设信息的域。
例如，可以使所述SL BSR的格式中包含如下域：目的地址索引域、逻辑信道组索引域、待传输数据量域和RAT类型域，其中，所述RAT类型域即为一个附加域，所述RAT类型域用于承载RAT类型信息，如承载LTE PC5接口信息，或承载NR PC5接口信息，PC5接口是终端设备之间不通过网络设备直接通信的接口。
再如，可以使所述SL BSR的格式中包含如下域：目的地址索引域、逻辑信道组索引域、待传输数据量域和SL传输方式域，其中，所述SL传输方式域即为一个附加域，所述SL传输方式域用于承载SL传输方式信息，如承载单播、组播或广播信息。
又如，可以使所述SL BSR的格式中包含如下域：目的地址索引域、逻 辑信道组索引域、待传输数据量域、RAT类型域和SL传输方式域，其中，RAT类型域和SL传输方式域即为两个附加域，所述RAT类型域用于承载RAT类型信息，如承载LTE PC5接口信息，或承载NR PC5接口信息；所述SL传输方式域用于承载SL传输方式信息，如承载单播、组播或广播信息。
当然，还可以在所述SL BSR的格式中增加专用于承载QoS参数的域，此处不再一一列举。
可以理解，无论所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中的至少一个域与所述预设信息隐式关联还是显式关联，都使得终端设备发送的截短的SL BSR中携带有所述预设信息，因此，可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
在上述第一个例子和第二个例子的前提下，上述基于所述缓存数据的预设信息，发送截短的SL BSR，具体可以包括：基于所有副链路逻辑信道的缓存数据的预设信息，确定不同类型的缓存数据的数据量的上报顺序；基于所述上报顺序，发送截短的SL BSR，以在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，实现缓存数据的数据量的上报。
具体的，可以基于所述上报顺序，确定排序在前的目标缓存数据；然后发送按顺序优先承载所述目标缓存数据的数据量的SL BSR，也即尽可能多的发送排序在前的缓存数据的数量。
下面先通过几个例子对如何确定不同类型的缓存数据的数据量的上报顺序进行说明。
在一个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括RAT类型，且RAT类型超过一种，则所述基于所述预设信息，确定不同类型的缓存数据的数据量的上报顺序，包括：基于不同RAT类型的预设优先级，确定所述缓存数据中不同RAT类型的缓存数据的数据量的上报顺序。
其中，不同RAT类型的预设优先级可以由协议规定、由网络设备配置或 由终端设备预配置。例如，假如RAT类型包括LTE类型和NR类型，可以预配置LTE类型的优先级＞NR类型的优先级，相应的上报顺序可以为LTE类型的缓存数据的数据量＞NR类型的缓存数据的数据量；或者，可以预配置NR类型的优先级＞LTE类型的优先级，相应的上报顺序可以为NR类型的缓存数据的数据量＞LTE类型的缓存数据的数据量。
在第二个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括SL传输方式，且SL传输方式超过一种，则所述基于所述预设信息，确定不同类型的缓存数据的数据量的上报顺序，包括：基于不同SL业务传输方式的预设优先级，确定所述缓存数据中不同SL业务传输方式对应的缓存数据的数据量的上报顺序。
其中，不同SL传输方式的预设优先级可以由协议规定、由网络设备配置或由终端设备预配置。例如，假如SL传输方式包括单播、组播和广播，可以预配置单播传输方式的优先级＞组播传输方式的优先级＞广播传输方式的优先级，相应的上报顺序可以为单播传输方式对应的缓存数据的数据量＞组播传输方式对应的缓存数据的数据量＞广播传输方式对应的缓存数据的数据量；或者，可以预配置广播传输方式的优先级＞组播传输方式的优先级＞单播传输方式的优先级，相应的上报顺序可以为广播传输方式对应的缓存数据的数据量＞组播传输方式对应的缓存数据的数据量＞单播传输方式对应的缓存数据的数据量。
在第三个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括QoS参数，且QoS参数超过一种，则所述基于所述预设信息，确定不同类型的缓存数据的数据量的上报顺序，包括：基于不同QoS参数的预设优先级，确定所述缓存数据中不同QoS参数对应的缓存数据的数据量的上报顺序。
其中，不同QoS参数的预设优先级可以由协议规定、由网络设备配置或由终端设备预配置。例如，假如QoS参数包括多种优先级的数据包或数据流，可以预配置本身优先级较高的数据包或数据流的优先级＞本身优先级较低的 数据包或数据流的优先级，相应的上报顺序可以为高优先级的数据包或数据流的数据量＞低优先级的数据包或数据流的数据量；或者，假如参数包括多种时延的数据包或数据流，可以预配置时延较低的数据包或数据流的优先级＞时延较高的数据包或数据流的优先级，相应的上报顺序可以为低时延的数据包或数据流的数据量＞高时延的数据包或数据流的数据量，等等。
下面再通过几个例子对如何基于不同类型的缓存数据大小的上报顺序发送截短的SL BSR进行说明。
在一个例子中，假如所有副链路逻辑信道的缓存数据的RAT类型超过一种，例如包括LTE类型和NR类型的两种类型，且上报顺序为NR类型的缓存数据的数据量＞LTE类型的缓存数据的数据量，则截短的SL BSR先尽可能多的承载NR PC5接口对应的缓存数据的数据量，其次尽可能多的承载LTE PC5接口对应的缓存数据的数据量，直到用于发送SL BSR的上行资源被利用完；或者，上报顺序为LTE类型的缓存数据的数据量＞NR类型的缓存数据的数据量，则截短的SL BSR尽可能多的承载LTE PC5接口对应的缓存数据的数据量，其次尽可能多的承载NR PC5接口对应的缓存数据的数据量，直到用于发送SL BSR的上行资源被利用完。
在另一个例子中，假如所有副链路逻辑信道的缓存数据的SL传输方式超过一种，例如具体包括单播、组播和广播三种传输方式，且上报顺序为单播传输方式对应的缓存数据的数据量＞组播传输方式对应的缓存数据的数据量＞广播传输方式对应的缓存数据的数据量，则截短的SL BSR先尽可能多的承载单播传输方式对应的缓存数据的数据量，其次尽可能多的承载组播传输方式对应的缓存数据的数据量，最后承载广播传输方式对应的缓存数据的数据量，直到用于发送SL BSR的上行资源被利用完；或者，上报顺序为广播传输方式对应的缓存数据的数据量＞组播传输方式对应的缓存数据的数据量＞单播传输方式对应的缓存数据的数据量，则截短的SL BSR先尽可能多的承载广播传输方式对应的缓存数据的数据量，其次尽可能多的承载组播传输 方式对应的缓存数据的数据量，最后承载单播传输方式对应的缓存数据的数据量，直到用于发送SL BSR的上行资源被利用完。
在又一个例子中，假如所有副链路逻辑信道的缓存数据的QoS参数超过一种，例如具体包括多种优先级的数据包或数据流，且上报顺序为高优先级的数据包或数据流的数据量＞低优先级的数据包或数据流的数据量，则截短的SL BSR先尽可能多的承载高优先级的数据包或数据流的数据量，其次尽可能多的承载低优先级的数据包或数据流的数据量，直到用于发送SL BSR的上行资源被利用完。或者，假如所有副链路逻辑信道的缓存数据的QoS参数超过一种，例如具体包括多种时延的数据包或数据流，且上报顺序为低时延的数据包或数据流的数据量＞高时延的数据包或数据流的数据量，则截短的SL BSR先尽可能多的承载低时延的数据包或数据流的数据量，其次尽可能多的承载高时延的数据包或数据流的数据量，直到用于发送SL BSR的上行资源被利用完。
不难理解，在上述第一种具体实施方式中，一方面，相比于相关技术中尽可能多的上报LCG所包含的缓存数据大小，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，由于本实施方式可以基于所有副链路逻辑信道的缓存数据的预设信息，发送按不同方式截短的SL BSR，因此可以提供一种适用性更好的缓存状态上报方案。另一方面，由于发送的SL BSR的格式中的至少一个域与所述预设信息相关联，使得终端设备发送的截短的SL BSR中携带有所述预设信息，因此，可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
在第二种具体实施方式中，基于预设优先级发送至少一种SL BSR格式的SL BSR，所述SL BSR格式是基于所述缓存数据的预设信息确定的。
所述预设信息包括但不限于无线接入技术(Radio Access Technology，RAT)类型和SL业务传输方式中的至少一种。其中，RAT类型可以包括长期演进(Long Term Evolution，LTE)类型和新空口(New Radio，NR)类型中 的至少一种。SL业务传输方式可以包括单播、组播和广播中的至少一种。
具体的，所述基于预设优先级发送至少一种SL BSR格式的SL BSR，可以包括：基于所述预设信息，确定用于发送所述缓存数据的数据量的多种SL BSR格式；基于所述多种SL BSR格式的预设优先级，发送至少一种SL BSR格式的SL BSR。
也就是说，可以基于所述预设信息预先定义多种SL BSR格式，并定义这多种SL BSR格式的优先级，这样在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，按照这多种SL BSR格式的预设优先级，从中选择至少一种SL BSR格式进行SL BSR的发送。
这多种SL BSR格式可以理解为是专用的SL BSR格式，并且，由于这多种SL BSR格式是基于所述预设信息定义的，因此，向网络设备发送该SL BSR格式的SL BSR，意味着同时携带了所述预设信息。
例如，可以定义用于发送一种或多种缓存数据的数据量组合的SL BSR格式。具体的，可以定义用于发送LTE类型的缓存数据的数据量和/或NR类型的缓存数据的数据量的SL BSR格式，相应的该SL BSR格式可以表示为NR Sidelink BSR格式、LTE Sidelink BSR格式、NR/LTE Sidelink BSR格式，等等；或者，可以定义用于发送单播、组播和广播中的至少一种传输方式对应的缓存数据的数据量的SL BSR格式,相应的该SL BSR格式可以表示为unicast Sidelink BSR格式、groupcast Sidelink BSR格式、broadcast Sidelink BSR格式等。
可选地，与相关技术类似，这多种SL BSR格式包括如下域：目的地址索引域、逻辑信道组索引域和待传输数据量域。
在相关技术中，SL BSR的格式中一般包含目的地址索引域、逻辑信道组索引域、待传输数据量域。其中，逻辑信道组常被分为4组，逻辑信道组索引在SL BSR中占2比特，用于说明终端设备的缓存区域对应的LCG ID；目的地址索引的长度可配置，常见的为16组，占4比特；待传输数据量，以 LCG包含的SL逻辑信道的优先级递减的顺序排列，占6比特，用于指定SL终端设备在发送该SL BSR的传输时序间隔(Transmission Timing Interval，TTI)内的所有MAC协议数据单位(Protocol Data Unit，PDU)生成后，对应近距离服务目的地址的LCG内所有逻辑信道的无线链路控制(Radio Link Control，RLC)层和分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层中剩余的待传输的有效数据总和。
图2和图3分别示出了相关技术中的SL BSR的两种格式的示意图，其中图2是索引(index)的取值为偶数的BSR格式示意图，图3是索引(index)的取值为奇数的BSR格式示意图。在图2和图3中，一行表示一个八位字节(1个Oct)，N表示索引的最大取值。
在相关技术中，MAC层采用MAC控制单元(MAC Control Element，CE)上报BSR，且SL BSR和截短SL BSR使用相同的MAC控制单元(MAC Control Element，CE)。每种MAC CE对应采用一个逻辑信道标识(Logical Channel ID，LCID)标识，下表1列出了上行共享信道(UpLink-Shared Channel,UL-SCH)中LCID取值与码点(codepoint)的对应关系。
在表1中，码点“10111”对应相关技术的SL BSR格式。上述第一种具体实施方式中的显示关联，相当于在相关技术的SL BSR格式的基础上引入至少一个附加域，例如，如表2所示，相当于在表1的基础上，引入与NR和LTE相关联的Sidelink BSR。
而在第二种具体实施方式中，相当于在相关技术的SL BSR格式的基础上引入新的格式的SL BSR，例如，如表3所示，相当于在表1的基础上，引入NR Sidelink BSR和LTE Sidelink BSR这两种新的SL BSR格式，这两种新的SL BSR格式的码点待定。
表1
Figure PCTCN2020073482-appb-000001
Figure PCTCN2020073482-appb-000002
表2
10111 Sidelink BSR
XXXXXX 与NR和LTE相关联的Sidelink BSR(Sidelink BSR for NR and LTE)
表3
10111 Sidelink BSR
XXXXX NR Sidelink BSR
XXXXX LTE Sidelink BSR
在基于预设信息，定义出多种SL BSR格式之后，图1所示的方法还可以包括：基于所述预设信息，确定所述多种SL BSR格式的预设优先级。
在一个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括RAT类型，且RAT类型超过一种，则所述基于所述预设信息，确定所述多种SL BSR格式的预设优先级，包括：基于不同的RAT类型，确定所述多种SL BSR格式的预设优先级。
例如，可以定义NR sidelink BSR格式的优先级＞LTE sidelink BSR格式的优先级。相应的，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，可以优先发送NR sidelink BSR格式的SL BSR。
或者，可以定义LTE sidelink BSR格式的优先级＞NR sidelink BSR格式的优先级。相应的，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，可以优先发送LTE sidelink BSR格式的SL BSR。
在另一个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括SL传输方式，且SL传输方式超过一种，则所述基于所述预设信息，确定所述多种SL BSR格式的预设优先级，包括：基于不同的SL业务传输方式，确定所述多种SL BSR格式的预设优先级。
例如，可以定义unicast sidelink BSR格式的优先级＞groupcast sidelink BSR格式的优先级＞broadcast sidelink BSR格式的优先级。相应的，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，可以优先发送unicast sidelink BSR格式的SL BSR，其次发送groupcast sidelink BSR格式的SL BSR，最后发送broadcast sidelink BSR格式的SL BSR。
或者，可以定义broadcast sidelink BSR格式的优先级＞groupcast sidelink BSR格式的优先级＞unicast sidelink BSR格式的优先级。相应的，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，可以优先发送broadcast sidelink BSR格式的SL BSR，其次发送groupcast sidelink BSR格式的SL BSR，最后发送unicast sidelink BSR格式的SL BSR。
除了上述两个例子中的发送顺序，还可以基于所述预设信息包含的SL传输方式进行穷举，此处不一一列举。
在又一个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括SL传输方式和RAT类型，则所述基于所述预设信息，确定所述多种SL BSR格式的预设优先级，包括：基于所述SL业务传输方式和所述RAT类型，确 定所述多种SL BSR格式的预设优先级。
例如，假如所述预设信息包括LTE类型和NR类型两种RAT类型，且所述预设信息包括LTE广播和NR组播两种SL传输方式，则可以定义NR groupcast sidelink BSR格式的优先级＞LTE broadcast sidelink BSR格式的优先级。相应的，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，可以优先发送NR groupcast sidelink BSR格式的SL BSR，其次发送LTE broadcast sidelink BSR格式的SL BSR。
或者，假如所述预设信息包括LTE类型和NR类型两种RAT类型，且所述预设信息包括LTE广播和NR广播两种SL传输方式，则可以定义LTE broadcast sidelink BSR格式的优先级＞NR broadcast sidelink BSR格式的优先级。相应的，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，可以优先发送LTE broadcast sidelink BSR格式的SL BSR，其次发送NR broadcast sidelink BSR格式的SL BSR。
以上仅仅是通过一些例子，对基于预设信息定义多种SL BSR格式，以及基于预设信息定义多种SL BSR格式的优先级的过程进行说明，应理解，上述例子并非穷举，也不构成对本公开实施例提供的技术方案的限定。
不难理解，在上述第二种具体实施方式中，一方面，相比于相关技术中尽可能多的上报LCG所包含的缓存数据大小，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，由于本实施方式可以基于预设优先级发送至少一种SL BSR格式的SL BSR，因此可以提供一种适用性更好的缓存状态上报方案。另一方面，由于发送的SL BSR的格式基于所述预设信息确定的，使得发送的SL BSR中间接携带所述预设信息，因此，可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
总之，本说明书实施例提供的一种副链路缓存状态报告发送方法，一方面，可以在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时， 提供一种适用性更好的缓存状态上报方案；另一方面，在上报缓存数据的数据量的同时，还能直接或间接的在SL BSR中携带缓存数据的预设信息，因此可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
以上对应用于终端设备的副链路缓存状态报告发送方法进行了说明，下面结合图4对本公开实施例提供的一种副链路缓存状态报告接收方法进行说明。
如图4所示，本公开实施例提供的一种副链路缓存状态报告接收方法，应用于网络设备，该方法可以包括：
步骤401、接收截短的副链路缓存状态报告SL BSR，所述截短的SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息发送的，且所述SL BSR的至少一个域与所述预设信息相关联；或者，接收至少一种SL BSR格式的SL BSR，所述至少一种SL BSR格式的SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，按预设优先级发送的，且所述SL BSR格式是基于所述缓存数据的预设信息确定的。
也就是说，在本公开实施例中，当上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，可以通过两种具体实施方式实现副链路逻辑信道的缓存数据的数据量(或者说数据大小)的接收，下面分别进行说明。
第一种具体实施方式，网络设备接收截短的副链路缓存状态报告SL BSR。
具体的，网络设备接收的截短的SL BSR是所述终端设备基于不同类型的缓存数据的数据量的上报顺序发送的，所述上报顺序是基于所述预设信息确定的，且接收的截短的SL BSR的至少一个域与所述预设信息相关联。
其中，截短的SL BSR的至少一个域可通过隐式或显式两种方式与所述预设信息相关联，下面分别举例说明。
所述预设信息包括但不限于无线接入技术RAT类型、SL业务传输方式 和QoS参数中的至少一种。其中，RAT类型可以包括LTE类型、NR类型和后续出现的新的RAT类型中的至少一种。SL业务传输方式可以包括单播、组播和广播中的至少一种。QoS参数可以包括但不限于如下至少一种：数据包或数据流的优先级(Priority)、数据包或数据流的时延(Latency，单位为ms)、数据包或数据流的可靠性(Reliability，用百分数(％)表示)、数据包或数据流的通信距离(Communication range，单位为米(meter))、数据包或数据流的大小(payload，单位为字节(Byte))、数据包或数据流的发送速率(Transmission rate，用message/sec表示)和数据包或数据流的数据速率(Data rate，单位为Mbps)，等等。
在第一个例子中，截短的SL BSR的至少一个域通过隐式的方式与所述预设信息相关联。具体的，所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中包括：目的地址索引(destination index)域、逻辑信道组索引(Logical Channel Group Index，LCG ID)域和待传输数据量(Buffer size level)域，其中，所述目的地址索引域和所述逻辑信道组索引域中的至少一个与所述预设信息相关联。
在此基础上，可选地，图4所示的方法还可以包括：基于所述目的地址索引域和所述逻辑信道组索引域中的至少一个，确定所述预设信息。
所谓隐式关联，可以理解为是，事先建立SL BSR的格式中的目的地址索引域和/或逻辑信道组索引域与所述预设信息的映射关系，这样当网络设备接收到该SL BSR之后，就可以基于该映射关系知道该SL BSR携带的所述预设信息，而不需要在该SL BSR中直接携带所述预设信息。
在第二个例子中，截短的SL BSR的至少一个域通过显式的方式与所述预设信息相关联。具体的，所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中包括：目的地址索引域、逻辑信道组索引域、待传输数据量域和至少一个附加域，其中，所述至少一个附加域用于承载所述预设信息，以实现所述至少一个附加域与所述预设信息的关联。也即，附加域可以认为是在所 述SL BSR的格式中增加的专门用于承载所述预设信息的域。
在此基础上，可选地，图4所示的方法还可以包括：基于所述至少一个附加域，确定所述预设信息。
可以理解，无论所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中的至少一个域与所述预设信息隐式关联还是显式关联，都使得网络设备接收的截短的SL BSR中携带有所述预设信息，因此，可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
其中，关于终端设备如何确定不同类型的缓存数据的上报顺序，以及如何及基于不同类型的缓存数据的上报顺序，发送截短的SL BSR，请参照上文中对应用于终端设备的副链路缓存状态报告发送方法的实施例的说明，此处不做重复描述。
在第二种具体实施方式中，网络设备接收至少一种SL BSR格式的SLBSR，且作为一个例子，所述接收至少一种SL BSR格式的SL BSR，包括：基于多种SL BSR格式的预设优先级，接收至少一种SL BSR格式的SL BSR；其中，所述多种SL BSR格式是所述终端设备基于所述预设信息确定的。
所述预设信息包括但不限于RAT类型和SL业务传输方式中的至少一种。其中，RAT类型可以包括LTE类型、NR类型和后续出现的新的RAT类型中的至少一种。SL业务传输方式可以包括单播、组播和广播中的至少一种。
这多种SL BSR格式可以理解为是专用的SL BSR格式，并且，由于这多种SL BSR格式是基于所述预设信息定义的，因此，网络设备接收该SL BSR格式的SL BSR，意味着同时接收了所述预设信息。
可选地，与相关技术类似，这多种SL BSR格式包括如下域：目的地址索引域、逻辑信道组索引域和待传输数据量域。
上述第一种具体实施方式中的显示关联，相当于在相关技术的SL BSR格式的基础上引入至少一个附加域，例如，如上表2所示，相当于在上表1 的基础上，引入与NR和LTE相关联的Sidelink BSR。
而在第二种具体实施方式中，相当于在相关技术的SL BSR格式的基础上引入新的格式的SL BSR，例如，如上表3所示，相当于在上表1的基础上，引入NR Sidelink BSR和LTE Sidelink BSR这两种新的SL BSR格式，这两种新的SL BSR格式的码点待定。
其中，关于终端设备如何基于预设信息确定所述多种SL BSR格式的预设优先级，以及如何基于所述多种SL BSR格式的预设优先级，发送至少一种SL BSR格式的SL BSR，请参照上文中对应用于终端设备的副链路缓存状态报告发送方法的实施例的说明，此处不做重复描述。
本说明书实施例提供的一种副链路缓存状态报告接收方法，一方面，可以在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，提供一种适用性更好的缓存状态上报方案；另一方面，在接收缓存数据的数据量的同时，还能直接或间接的接收缓存数据的预设信息，因此可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
以上对应用于网络设备的副链路缓存状态报告接收方法进行了说明，下面将结合图5至图6详细描述根据本公开实施例的终端设备和网络设备。
图5示出了本公开实施例提供的一种终端设备的结构示意图，如图5所示，终端设备500可以包括：发送模块501。
发送模块501，用于在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息，发送截短副链路缓存状态报告SL BSR，所述SL BSR的至少一个域与所述预设信息相关联；或者，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于预设优先级发送至少一种SL BSR格式的SL BSR，所述SL BSR格式是基于所述缓存数据的预设信息确定的。
也就是说，在本公开实施例中，当上行资源不够上报所有副链路逻辑信 道的缓存数据的数据总量时，发送模块501可以通过两种具体实施方式实现副链路逻辑信道的缓存数据的数据量(或者说数据大小)的上报，下面分别进行说明。
在第一种具体实施方式中，发送模块501可以基于所有副链路逻辑信道的缓存数据的预设信息，发送截短的SL BSR，且发送的截短的SL BSR的至少一个域与所述预设信息相关联。其中，截短的SL BSR的至少一个域可通过隐式或显式两种方式与所述预设信息相关联，下面会分别举例说明。
其中，所述预设信息包括但不限于RAT类型、SL业务传输方式和QoS参数中的至少一种。
RAT类型可以包括LTE类型、NR类型和后续出现的新的RAT类型中的至少一种。
SL业务传输方式可以包括单播、组播和广播中的至少一种。
QoS参数可以包括但不限于如下至少一种：数据包或数据流的优先级(Priority)、数据包或数据流的时延(Latency，单位为ms)、数据包或数据流的可靠性(Reliability，用百分数(％)表示)、数据包或数据流的通信距离(Communication range，单位为米(meter))、数据包或数据流的大小(payload，单位为字节(Byte))、数据包或数据流的发送速率(Transmission rate，用message/sec表示)和数据包或数据流的数据速率(Data rate，单位为Mbps)，等等。
在第一个例子中，截短的SL BSR的至少一个域通过隐式的方式与所述预设信息相关联。具体的，所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中包括：目的地址索引(destination index)域、逻辑信道组索引(Logical Channel Group Index，LCG ID)域和待传输数据量(Buffer size level)域，其中，所述目的地址索引域和所述逻辑信道组索引域中的至少一个与所述预设信息相关联。
所谓隐式关联，可以理解为是，事先建立SL BSR的格式中的目的地址 索引域和/或逻辑信道组索引域与所述预设信息的映射关系，这样当终端设备向网络设备发送该SL BSR之后，网络设备就可以基于该映射关系知道该SLBSR携带的所述预设信息，而不需要在该SL BSR中直接携带所述预设信息。
在第二个例子中，截短的SL BSR的至少一个域通过显式的方式与所述预设信息相关联。具体的，所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中包括：目的地址索引(destination index)域、逻辑信道组索引(Logical Channel Group Index，LCG ID)域、待传输数据量(Buffer size level)域和至少一个附加域，其中，所述至少一个附加域用于承载所述预设信息，以实现所述至少一个附加域与所述预设信息的关联。也即，附加域可以认为是在所述SL BSR的格式中增加的专门用于承载所述预设信息的域。
可以理解，无论所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中的至少一个域与所述预设信息隐式关联还是显式关联，都使得终端设备发送的截短的SL BSR中携带有所述预设信息，因此，可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
在上述第一个例子和第二个例子的前提下，发送模块501可用于：基于所有副链路逻辑信道的缓存数据的预设信息，确定不同类型的缓存数据的数据量的上报顺序；基于所述上报顺序，发送截短的SL BSR，以在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，实现缓存数据的数据量的上报。
具体的，发送模块501可用于基于所述上报顺序，确定排序在前的目标缓存数据；然后发送按顺序优先承载所述目标缓存数据的数据量的SL BSR，也即尽可能多的发送排序在前的缓存数据的数量。
下面先通过几个例子对如何确定不同类型的缓存数据的数据量的上报顺序进行说明。
在一个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括 RAT类型，且RAT类型超过一种，则发送模块501可用于：基于不同RAT类型的预设优先级，确定所述缓存数据中不同RAT类型的缓存数据的数据量的上报顺序。
其中，不同RAT类型的预设优先级可以由协议规定、由网络设备配置或由终端设备预配置。
在第二个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括SL传输方式，且SL传输方式超过一种，则发送模块501可用于：基于不同SL业务传输方式的预设优先级，确定所述缓存数据中不同SL业务传输方式对应的缓存数据的数据量的上报顺序。
其中，不同SL传输方式的预设优先级可以由协议规定、由网络设备配置或由终端设备预配置。
在第三个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括QoS参数，且QoS参数超过一种，则发送模块501可用于：基于不同QoS参数的预设优先级，确定所述缓存数据中不同QoS参数对应的缓存数据的数据量的上报顺序。
其中，不同QoS参数的预设优先级可以由协议规定、由网络设备配置或由终端设备预配置。
关于发送模块501如何基于不同类型的缓存数据大小的上报顺序发送截短的SL BSR，请参照上文中对图1所示的方法实施例的说明，此处不再重复描述。
在第二种具体实施方式中，发送模块501，用于基于预设优先级发送至少一种SL BSR格式的SL BSR，所述SL BSR格式是基于所述缓存数据的预设信息确定的。
所述预设信息包括但不限于RAT类型和SL业务传输方式中的至少一种。其中，RAT类型可以包括LTE类型、NR类型和后续出现的新的RAT类型中的至少一种。SL业务传输方式可以包括单播、组播和广播中的至少一种。
具体的，发送模块501可用于：基于所述预设信息，确定用于发送所述缓存数据的数据量的多种SL BSR格式；基于所述多种SL BSR格式的预设优先级，发送至少一种SL BSR格式的SL BSR。
也就是说，发送模块501可以基于所述预设信息预先定义多种SL BSR格式，并定义这多种SL BSR格式的优先级，这样在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，按照这多种SL BSR格式的预设优先级，从中选择至少一种SL BSR格式进行SL BSR的发送。
这多种SL BSR格式可以理解为是专用的SL BSR格式，并且，由于这多种SL BSR格式是基于所述预设信息定义的，因此，向网络设备发送该SL BSR格式的SL BSR，意味着同时携带了所述预设信息。
可选地，与相关技术类似，这多种SL BSR格式包括如下域：目的地址索引域、逻辑信道组索引域和待传输数据量域。
上述第一种具体实施方式中的显示关联，相当于在相关技术的SL BSR格式的基础上引入至少一个附加域，例如，如上表2所示，相当于在上表1的基础上，引入与NR和LTE相关联的Sidelink BSR。
而在第二种具体实施方式中，相当于在相关技术的SL BSR格式的基础上引入新的格式的SL BSR，例如，如上表3所示，相当于在上表1的基础上，引入NR Sidelink BSR和LTE Sidelink BSR这两种新的SL BSR格式，这两种新的SL BSR格式的码点待定。
在基于预设信息，定义出多种SL BSR格式之后，图5所示的终端设备500还可以包括：优先级确定模块，用于基于所述预设信息，确定所述多种SL BSR格式的预设优先级。
在一个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括RAT类型，且RAT类型超过一种，则所述优先级确定模块可用于：基于不同的RAT类型，确定所述多种SL BSR格式的预设优先级。
在另一个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括 SL传输方式，且SL传输方式超过一种，则所述优先级确定模块可用于：基于不同的SL业务传输方式，确定所述多种SL BSR格式的预设优先级。
在又一个例子中，如果所有副链路逻辑信道的缓存数据的预设信息包括SL传输方式和RAT类型，则所述优先级确定模块可用于：基于所述SL业务传输方式和所述RAT类型，确定所述多种SL BSR格式的预设优先级。
不难理解，在上述第二种具体实施方式中，一方面，相比于相关技术中尽可能多的上报LCG所包含的缓存数据大小，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，由于本实施方式可以基于预设优先级发送至少一种SL BSR格式的SL BSR，因此可以提供一种适用性更好的缓存状态上报方案。另一方面，由于发送的SL BSR的格式基于所述预设信息确定的，使得发送的SL BSR中间接携带所述预设信息，因此，可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
总之，本说明书实施例提供的一种终端设备500，一方面，可以在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，提供一种适用性更好的缓存状态上报方案；另一方面，在上报缓存数据的数据量的同时，还能直接或间接的在SL BSR中携带缓存数据的预设信息，因此可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
上述图5所示的终端设备500，可以用于实现上述图1所示的副链路缓存状态报告发送方法的各个实施例，相关之处请参考上述方法实施例。
以上对终端设备500进行了说明，下面结合图6对本公开实施例提供的网络设备600进行说明。
图6示出了本公开实施例提供的一种网络设备的结构示意图，如图6所示，网络设备600可以包括：接收模块601。
接收模块601，用于接收截短副链路缓存状态报告SL BSR，所述截短的 SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息发送的，且所述SL BSR的至少一个域与所述预设信息相关联；或者，用于接收至少一种SL BSR格式的SLBSR，所述至少一种SL BSR格式的SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，按预设优先级发送的，且所述SL BSR格式是基于所述缓存数据的预设信息确定的。
也就是说，在本公开实施例中，当上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，可以通过两种具体实施方式实现副链路逻辑信道的缓存数据的数据量(或者说数据大小)的接收，下面分别进行说明。
在第一种具体实施方式中，接收模块601，用于接收截短的副链路缓存状态报告SL BSR。
具体的，接收模块601接收的所述截短的SL BSR是所述终端设备基于不同类型的缓存数据的数据量的上报顺序发送的，所述上报顺序是基于所述预设信息确定的，且接收的截短的SL BSR的至少一个域与所述预设信息相关联。
其中，截短的SL BSR的至少一个域可通过隐式或显式两种方式与所述预设信息相关联，下面会分别举例说明。
所述预设信息包括但不限于无线接入技术RAT类型、SL业务传输方式和QoS参数中的至少一种。其中，RAT类型可以包括LTE类型、NR类型和后续出现的新的RAT类型中的至少一种。SL业务传输方式可以包括单播、组播和广播中的至少一种；QoS参数可以包括但不限于如下至少一种：数据包或数据流的优先级(Priority)、数据包或数据流的时延(Latency，单位为ms)、数据包或数据流的可靠性(Reliability，用百分数(％)表示)、数据包或数据流的通信距离(Communication range，单位为米(meter))、数据包或数据流的大小(payload，单位为字节(Byte))、数据包或数据流的发送速率(Transmission rate，用message/sec表示)和数据包或数据流的数据速率(Data  rate，单位为Mbps)，等等。
在第一个例子中，截短的SL BSR的至少一个域通过隐式的方式与所述预设信息相关联。具体的，所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中包括：目的地址索引(destination index)域、逻辑信道组索引(Logical Channel Group Index，LCG ID)域和待传输数据量(Buffer size level)域，其中，所述目的地址索引域和所述逻辑信道组索引域中的至少一个与所述预设信息相关联。
在此基础上，可选地，图6所示的网络设备还可以包括：第一确定模块，用于基于所述目的地址索引域和所述逻辑信道组索引域中的至少一个，确定所述预设信息。
所谓隐式关联，可以理解为是，事先建立SL BSR的格式中的目的地址索引域和/或逻辑信道组索引域与所述预设信息的映射关系，这样当网络设备接收到该SL BSR之后，就可以基于该映射关系知道该SL BSR携带的所述预设信息，而不需要在该SL BSR中直接携带所述预设信息。
在第二个例子中，截短的SL BSR的至少一个域通过显式的方式与所述预设信息相关联。具体的，所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中包括：目的地址索引域、逻辑信道组索引域、待传输数据量域和至少一个附加域，其中，所述至少一个附加域用于承载所述预设信息，以实现所述至少一个附加域与所述预设信息的关联。
也即，附加域可以认为是在所述SL BSR的格式中增加的专门用于承载所述预设信息的域。
在此基础上，可选地，图6所示的网络设备还可以包括：第一确定模块，关于基于所述至少一个附加域，确定所述预设信息。
可以理解，无论所述SL BSR(包括截短的SL BSR和原SL BSR)的格式中的至少一个域与所述预设信息隐式关联还是显式关联，都使得网络设备接收的截短的SL BSR中携带有所述预设信息，因此，可以使网络设备获知 更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
其中，关于终端设备如何确定不同类型的缓存数据的上报顺序，以及如何及基于不同类型的缓存数据的上报顺序，发送截短的SL BSR，请参照上文中对应用于终端设备的副链路缓存状态报告发送方法的实施例的说明，此处不做重复描述。
在第二种具体实施方式中，接收模块601，用于接收至少一种SL BSR格式的SL BSR，且作为一个例子，接收模块601具体可用于：基于多种SL BSR格式的预设优先级，接收至少一种SL BSR格式的SL BSR；其中，所述多种SL BSR格式是所述终端设备基于所述预设信息确定的。
所述预设信息包括但不限于RAT类型和SL业务传输方式中的至少一种。其中，RAT类型可以包括LTE类型、NR类型和后续出现的新的RAT类型中的至少一种。SL业务传输方式可以包括单播、组播和广播中的至少一种。
这多种SL BSR格式可以理解为是专用的SL BSR格式，并且，由于这多种SL BSR格式是基于所述预设信息定义的，因此，网络设备接收该SL BSR格式的SL BSR，意味着同时接收了所述预设信息。
可选地，与相关技术类似，这多种SL BSR格式包括如下域：目的地址索引域、逻辑信道组索引域和待传输数据量域。
上述第一种具体实施方式中的显示关联，相当于在相关技术的SL BSR格式的基础上引入至少一个附加域，例如，如上表2所示，相当于在上表1的基础上，引入与NR和LTE相关联的Sidelink BSR。
而在第二种具体实施方式中，相当于在相关技术的SL BSR格式的基础上引入新的格式的SL BSR，例如，如上表3所示，相当于在上表1的基础上，引入NR Sidelink BSR和LTE Sidelink BSR这两种新的SL BSR格式，这两种新的SL BSR格式的码点待定。
其中，关于终端设备如何基于预设信息确定所述多种SL BSR格式的预 设优先级，以及如何基于所述多种SL BSR格式的预设优先级，发送至少一种SL BSR格式的SL BSR，请参照上文中对应用于终端设备的副链路缓存状态报告发送方法的实施例的说明，此处不做重复描述。
本说明书实施例提供的一种网络设备600，一方面，可以在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，提供一种适用性更好的缓存状态上报方案；另一方面，在接收缓存数据的数据量的同时，还能直接或间接的接收缓存数据的预设信息，因此可以使网络设备获知更加全面的终端设备的缓存状态信息，从而更好的给终端设备分配资源，提高通信有效性。
上述图6所示的网络设备600，可以用于实现上述图4所示的副链路缓存状态报告接收方法的各个实施例，相关之处请参考上述方法实施例。
图7是本公开另一个实施例的终端设备的结构示意图。图7所示的终端设备700包括：至少一个处理器701、存储器702、至少一个网络接口704和用户接口703。终端设备700中的各个组件通过总线系统705耦合在一起。可理解，总线系统705用于实现这些组件之间的连接通信。总线系统705除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图7中将各种总线都标为总线系统705。
其中，用户接口703可以包括显示器、键盘、点击设备(例如，鼠标，轨迹球(trackball))、触感板或者触摸屏等。
可以理解，本公开实施例中的存储器702可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可 用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch Link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本公开实施例描述的系统和方法的存储器702旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器702存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统7021和应用程序7022。
其中，操作系统7021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序7022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用于实现各种应用业务。实现本公开实施例方法的程序可以包含在应用程序7022中。
在本公开实施例中，终端设备700还包括：存储在存储器702上并可在处理器701上运行的计算机程序，计算机程序被处理器701执行时实现上述副链路缓存状态报告发送方法的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
上述本公开实施例揭示的方法可以应用于处理器701中，或者由处理器701实现。处理器701可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器701中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器701可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array， FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的计算机可读存储介质中。该计算机可读存储介质位于存储器702，处理器701读取存储器702中的信息，结合其硬件完成上述方法的步骤。具体地，该计算机可读存储介质上存储有计算机程序，计算机程序被处理器701执行时实现如上述副链路缓存状态报告发送方法实施例的各步骤。
请参阅图8，图8是本公开实施例应用的网络设备的结构图，能够实现上述副链路缓存状态报告接收方法的细节，并达到相同的效果。如图8所示，网络设备800包括：处理器801、收发机802、存储器803、用户接口804和总线接口，其中：
在本公开实施例中，网络设备800还包括：存储在存储器上803并可在处理器801上运行的计算机程序，计算机程序被处理器801、执行时实现上述副链路缓存状态报告接收方法的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
在图8中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器801代表的至少一个处理器和存储器803代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机802可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的终端设备，用户接口804还可以是能够外接内接需要设备的接口，连接 的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器801负责管理总线架构和通常的处理，存储器803可以存储处理器801在执行操作时所使用的数据。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在至少一个专用集成电路(Application Specific Integrated Circuit，ASIC)、数字信号处理器(Digital Signal Processor，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述副链路反馈信息发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本公开实施例还提供一种包括指令的计算机程序产品，当计算机运行所述计算机程序产品的所述指令时，所述计算机执行上述副链路反馈信息发送方法或者上述副链路反馈信息发送方法。具体地，该计算机程序产品可以运行于上述网络设备上。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特 定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本公开所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、 随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来控制相关的硬件来完成，所述的程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储器(Read-Only Memory，ROM)或随机存取存储器(Random Access Memory，RAM)等。以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应所述以权利要求的保护范围为准。

Claims (29)

  1. 一种副链路缓存状态报告发送方法，应用于终端设备，包括：
    在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息，发送截短的副链路缓存状态报告SL BSR，所述SL BSR的至少一个域与所述预设信息相关联；或者，
    在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于预设优先级发送至少一种SL BSR格式的SL BSR，所述SL BSR格式是基于所述缓存数据的预设信息确定的。
  2. 根据权利要求1所述的方法，其中，
    所述基于所述缓存数据的预设信息，发送截短的SL BSR，包括：
    基于所述预设信息，确定不同类型的缓存数据的数据量的上报顺序；
    基于所述上报顺序，发送截短的SL BSR。
  3. 根据权利要求2所述的方法，其中，
    所述基于所述上报顺序，发送截短的SL BSR，包括：
    基于所述上报顺序，确定排序在前的目标缓存数据；
    发送按顺序优先承载所述目标缓存数据的数据量的SL BSR。
  4. 根据权利要求2或3所述的方法，其中，
    所述SL BSR的格式包括目的地址索引域，逻辑信道组索引域和待传输数据量域，且所述目的地址索引域和所述逻辑信道组索引域中的至少一个与所述预设信息相关联。
  5. 根据权利要求2或3所述的方法，其中，
    所述SL BSR的格式包括目的地址索引域、逻辑信道组索引域、待传输数据量域和至少一个附加域；
    其中，所述至少一个附加域用于承载所述预设信息。
  6. 根据权利要求2-5任一项所述的方法，其中，
    所述预设信息包括无线接入技术RAT类型、SL业务传输方式和服务质量QoS参数中的至少一种。
  7. 根据权利要求6所述的方法，其中，所述预设信息包括RAT类型， 其中，所述基于所述预设信息，确定不同类型的缓存数据的数据量的上报顺序，包括：
    基于不同RAT类型的预设优先级，确定所述缓存数据中不同RAT类型的缓存数据的数据量的上报顺序。
  8. 根据权利要求6所述的方法，其中，所述预设信息包括SL业务传输方式，其中，所述基于所述预设信息，确定不同类型的缓存数据的数据量的上报顺序，包括：
    基于不同SL业务传输方式的预设优先级，确定所述缓存数据中不同SL业务传输方式对应的缓存数据的数据量的上报顺序。
  9. 根据权利要求6所述的方法，其中，所述预设信息包括QoS参数，其中，所述基于所述预设信息，确定不同类型的缓存数据的数据量的上报顺序，包括：
    基于不同QoS参数的预设优先级，确定所述缓存数据中不同QoS参数对应的缓存数据的数据量的上报顺序。
  10. 根据权利要求6所述的方法，其中，
    所述RAT类型包括长期演进LTE类型、新空口NR类型和后续出现的新RAT类型中的至少一种。
  11. 根据权利要求6所述的方法，其中，
    所述SL业务传输方式包括单播、组播和广播中的至少一种。
  12. 根据权利要求6所述的方法，其中，
    所述QoS参数包括数据包或数据流的优先级、数据包或数据流的时延、数据包或数据流的可靠性、数据包或数据流的通信距离、数据包或数据流的大小、数据包或数据流的发送速率和数据包或数据流的数据速率中的至少一种。
  13. 根据权利要求1所述的方法，其中，
    所述基于预设优先级发送至少一种SL BSR格式的SL BSR，包括：
    基于所述预设信息，确定用于发送所述缓存数据的数据量的多种SL BSR格式；
    基于所述多种SL BSR格式的预设优先级，发送至少一种SL BSR格式的 SL BSR。
  14. 根据权利要求13所述的方法，还包括：
    基于所述预设信息，确定所述多种SL BSR格式的预设优先级。
  15. 根据权利要求14所述的方法，其中，
    所述预设信息包括无线接入技术RAT类型和SL业务传输方式中的至少一种。
  16. 根据权利要求15所述的方法，其中，所述预设信息包括RAT类型，所述基于所述预设信息，确定所述多种SL BSR格式的预设优先级，包括：
    基于不同的RAT类型，确定所述多种SL BSR格式的预设优先级。
  17. 根据权利要求15所述的方法，其中，所述预设信息包括SL业务传输方式，所述基于所述预设信息，确定所述多种SL BSR格式的预设优先级，包括：
    基于不同的SL业务传输方式，确定所述多种SL BSR格式的预设优先级。
  18. 根据权利要求15所述的方法，其中，所述预设信息包括SL业务传输方式和RAT类型，所述基于所述预设信息，确定所述多种SL BSR格式的预设优先级，包括：
    基于所述SL业务传输方式和所述RAT类型，确定所述多种SL BSR格式的预设优先级。
  19. 一种副链路缓存状态报告接收方法，应用于网络设备，包括：
    接收截短的副链路缓存状态报告SL BSR，所述截短的SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息发送的，且所述SL BSR的至少一个域与所述预设信息相关联；或者，
    接收至少一种SL BSR格式的SL BSR，所述至少一种SL BSR格式的SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，按预设优先级发送的，且所述SL BSR格式是基于所述缓存数据的预设信息确定的。
  20. 根据权利要求19所述的方法，其中，
    所述截短的SL BSR的格式包括目的地址索引域，逻辑信道组索引域和 待传输数据量域，且所述目的地址索引域和所述逻辑信道组索引域中的至少一个与所述预设信息相关联，所述方法还包括：
    基于所述目的地址索引域和所述逻辑信道组索引域中的至少一个，确定所述预设信息。
  21. 根据权利要求19所述的方法，其中，
    所述截短的SL BSR的格式包括目的地址索引域、逻辑信道组索引域、待传输数据量域和至少一个附加域，所述至少一个附加域用于承载所述预设信息，所述方法还包括：
    基于所述至少一个附加域，确定所述预设信息。
  22. 根据权利要求20或21所述的方法，其中，
    所述预设信息包括无线接入技术RAT类型、SL业务传输方式和服务质量QoS参数中的至少一种。
  23. 根据权利要求19所述的方法，其中，
    所述接收至少一种SL BSR格式的SL BSR，包括：
    基于多种SL BSR格式的预设优先级，接收至少一种SL BSR格式的SL BSR；
    其中，所述多种SL BSR格式是所述终端设备基于所述预设信息确定的。
  24. 根据权利要求23所述的方法，其中，
    所述预设信息包括无线接入技术RAT类型和SL业务传输方式中的至少一种。
  25. 一种终端设备，包括：
    发送模块，用于在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息，发送截短副链路缓存状态报告SL BSR，所述SL BSR的至少一个域与所述预设信息相关联；或者，在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于预设优先级发送至少一种SL BSR格式的SL BSR，所述SL BSR格式是基于所述缓存数据的预设信息确定的。
  26. 一种网络设备，包括：
    接收模块，用于接收截短副链路缓存状态报告SL BSR，所述截短的SL  BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，基于所述缓存数据的预设信息发送的，且所述SL BSR的至少一个域与所述预设信息相关联；或者，用于接收至少一种SL BSR格式的SL BSR，所述至少一种SL BSR格式的SL BSR是终端设备在上行资源不够上报所有副链路逻辑信道的缓存数据的数据总量时，按预设优先级发送的，且所述SL BSR格式是基于所述缓存数据的预设信息确定的。
  27. 一种终端设备，包括存储器、处理器及存储在所述存储器上并在所述处理器上运行的无线通信程序，所述无线通信程序被所述处理器执行时实现如权利要求1-18任一项所述的方法的步骤。
  28. 一种网络设备，包括存储器、处理器及存储在所述存储器上并在所述处理器上运行的无线通信程序，所述无线通信程序被所述处理器执行时实现如权利要求19-24任一项所述的方法的步骤。
  29. 一种计算机可读介质，所述计算机可读介质上存储有无线通信程序，所述无线通信程序被处理器执行时实现如权利要求1-24任一项所述的方法的步骤。
PCT/CN2020/073482 2019-01-23 2020-01-21 副链路缓存状态报告发送、接收方法和设备 WO2020151700A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR1020217026549A KR20210114524A (ko) 2019-01-23 2020-01-21 사이드링크 버퍼 상태 보고 송신, 수신 방법 및 장치
EP20745946.2A EP3917254A4 (en) 2019-01-23 2020-01-21 SIDE LINK BUFFER STATUS REPORT SENDING METHOD, SIDE LINK BUFFER STATUS REPORT RECEIVING METHOD AND DEVICE
US17/383,792 US12108278B2 (en) 2019-01-23 2021-07-23 Sidelink buffer status report sending method, sidelink buffer status report receiving method, and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910065287.9 2019-01-23
CN201910065287.9A CN111263457B (zh) 2019-01-23 2019-01-23 一种副链路缓存状态报告发送、接收方法和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/383,792 Continuation US12108278B2 (en) 2019-01-23 2021-07-23 Sidelink buffer status report sending method, sidelink buffer status report receiving method, and device

Publications (1)

Publication Number Publication Date
WO2020151700A1 true WO2020151700A1 (zh) 2020-07-30

Family

ID=70952045

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/073482 WO2020151700A1 (zh) 2019-01-23 2020-01-21 副链路缓存状态报告发送、接收方法和设备

Country Status (5)

Country Link
US (1) US12108278B2 (zh)
EP (1) EP3917254A4 (zh)
KR (1) KR20210114524A (zh)
CN (1) CN111263457B (zh)
WO (1) WO2020151700A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102018129809A1 (de) * 2018-11-26 2020-05-28 Beckhoff Automation Gmbh Verteilerknoten, Automatisierungsnetzwerk und Verfahren zum Übertragen von Telegrammen
DE102018129813A1 (de) * 2018-11-26 2020-05-28 Beckhoff Automation Gmbh Datenübertragungsverfahren und Automatisierungskommunikationsnetzwerk
CN111263451B (zh) * 2019-01-23 2022-10-11 维沃移动通信有限公司 副链路传输方法和设备
US11665583B2 (en) * 2021-03-01 2023-05-30 Qualcomm Incorporated Subchannel selection and channel state information (CSI) indication via buffer status report (BSR) for sidelink
US20230224903A1 (en) * 2022-01-13 2023-07-13 Qualcomm Incorporated Sidelink buffer status report for multiple destination devices
CN114422799B (zh) * 2022-01-24 2024-04-19 北京百度网讯科技有限公司 视频文件的解码方法、装置、电子设备、程序产品
CN117998454A (zh) * 2022-11-03 2024-05-07 维沃移动通信有限公司 格式确定方法、用户设备ue及可读存储介质
CN116261875A (zh) * 2022-12-28 2023-06-13 北京小米移动软件有限公司 信息传输方法、装置、通信设备和存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170245245A1 (en) * 2016-02-18 2017-08-24 Lg Electronics Inc. METHOD OF TRANSMITTING AND RECEIVING MESSAGE FOR COMMUNICATION BETWEEN UEs IN WIRELESS COMMUNICATION SYSTEM AND APPARATUS USING METHOD
CN107872885A (zh) * 2016-09-27 2018-04-03 华为技术有限公司 一种缓存状态报告的上报方法及装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10057918B2 (en) * 2014-08-08 2018-08-21 Telefonaktiebolaget Lm Ericsson (Publ) Coordination between prose BSR and cellular BSR
KR102248331B1 (ko) * 2015-01-29 2021-05-06 주식회사 아이티엘 단말간 통신을 지원하는 무선 통신 시스템에서 절단된 버퍼상태보고 운용 방법 및 장치
CN112788573B (zh) * 2015-08-12 2023-06-06 Lg电子株式会社 用于在无线通信系统中操作的方法及无线装置
US10548047B2 (en) * 2015-09-24 2020-01-28 Lg Electronics Inc. Method for transmitting a buffer status report in a D2D communication system and device therefor
CN105163346B (zh) * 2015-09-25 2018-04-10 宇龙计算机通信科技(深圳)有限公司 副链路缓冲状态报告的生成方法及装置
EP3148283A1 (en) * 2015-09-25 2017-03-29 ASUSTek Computer Inc. Method and apparatus for reducing signaling overhead in a wireless communication system
JP6545906B2 (ja) * 2015-10-27 2019-07-17 エルジー エレクトロニクス インコーポレイティド Ｄ２ｄ通信システムにおいてバッファ状態報告をトリガーする方法及びその装置
US10200991B2 (en) * 2016-04-25 2019-02-05 Ofinno Technologies, Llc Scheduling request process in a wireless device and wireless network
US11026116B2 (en) * 2017-05-04 2021-06-01 Lg Electronics Inc. Apparatus and method for generating a buffer status report
WO2019191961A1 (en) * 2018-04-04 2019-10-10 Lenovo (Beijing) Limited Buffer status report for packet duplication
WO2020132284A1 (en) * 2018-12-21 2020-06-25 Idac Holdings, Inc. Procedures for enabling simultaneous transmission of different types

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170245245A1 (en) * 2016-02-18 2017-08-24 Lg Electronics Inc. METHOD OF TRANSMITTING AND RECEIVING MESSAGE FOR COMMUNICATION BETWEEN UEs IN WIRELESS COMMUNICATION SYSTEM AND APPARATUS USING METHOD
CN107872885A (zh) * 2016-09-27 2018-04-03 华为技术有限公司 一种缓存状态报告的上报方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Management of Sidelink logical channel groups", 3GPP TSG-RAN WG2 #91BIS TDOC R2-154154, 9 October 2015 (2015-10-09), XP051004747, DOI: 20200408093002X *
INTEL CORPORATION: "Open aspects of priority handling for ProSe communication", 3GPP TSG RAN WG2 MEETING #91 R2-154385, 9 October 2015 (2015-10-09), XP051004961, DOI: 20200408093254X *
See also references of EP3917254A4 *

Also Published As

Publication number Publication date
EP3917254A1 (en) 2021-12-01
US12108278B2 (en) 2024-10-01
CN111263457A (zh) 2020-06-09
US20210352682A1 (en) 2021-11-11
CN111263457B (zh) 2022-03-01
EP3917254A4 (en) 2022-03-23
KR20210114524A (ko) 2021-09-23

Similar Documents

Publication Publication Date Title
WO2020151700A1 (zh) 副链路缓存状态报告发送、接收方法和设备
WO2019192596A1 (zh) 传输数据的方法及其装置和系统
WO2021233400A1 (zh) 数据传输方法、终端设备和网络设备
WO2018120160A1 (zh) 数据传输的方法和装置
WO2021088922A1 (zh) 测量上报的方法、终端设备和网络设备
EP3606158A1 (en) Buffer status reporting method, ue, buffer status report processing method, and network-side device
EP3503644A1 (en) Method and device for processing buffer status report
WO2021013102A1 (zh) 参数确定、信息配置方法和设备
WO2018227814A1 (zh) 数据指示方法、装置、通信系统
WO2019192471A1 (zh) Csi报告的传输方法、终端设备和网络设备
WO2021016774A1 (zh) 无线通信方法和设备
WO2021013088A1 (zh) 传输方式确定、信息配置方法和设备
EP3937565A1 (en) Communication method and apparatus
WO2021233401A1 (zh) 数据传输方法和设备
CN108809510B (zh) 一种数据传输的处理方法和装置
WO2021004374A1 (zh) 数据发送的方法、数据接收的方法和设备
WO2020088520A1 (zh) 上行传输方法和终端设备
WO2018201459A1 (zh) 逻辑信道资源分配的方法和终端设备
WO2020221070A1 (zh) 拥塞控制方法及设备
CN111107635B (zh) 一种副链路信息发送、接收方法和设备
WO2018202186A1 (zh) 一种数据传输的处理方法和装置
WO2020088329A1 (zh) 一种数据传输方法、网络设备、终端和存储介质
WO2020087289A1 (zh) 一种资源配置方法、网络设备及终端设备
WO2019126962A1 (zh) 上行授权的方法和终端设备
CN110167065B (zh) 一种取消上行调度请求的方法、终端设备和网络侧设备

Legal Events

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

Ref document number: 20745946

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217026549

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020745946

Country of ref document: EP

Effective date: 20210823