CN117998469A - Service characteristic reporting method, device and storage medium - Google Patents

Service characteristic reporting method, device and storage medium Download PDF

Info

Publication number
CN117998469A
CN117998469A CN202211380076.2A CN202211380076A CN117998469A CN 117998469 A CN117998469 A CN 117998469A CN 202211380076 A CN202211380076 A CN 202211380076A CN 117998469 A CN117998469 A CN 117998469A
Authority
CN
China
Prior art keywords
data set
data
packet loss
reporting
terminal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211380076.2A
Other languages
Chinese (zh)
Inventor
傅婧
谌丽
皮埃尔·伯特兰
熊春山
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Datang Mobile Communications Equipment Co Ltd
Original Assignee
Datang Mobile Communications Equipment Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Datang Mobile Communications Equipment Co Ltd filed Critical Datang Mobile Communications Equipment Co Ltd
Priority to CN202211380076.2A priority Critical patent/CN117998469A/en
Publication of CN117998469A publication Critical patent/CN117998469A/en
Pending legal-status Critical Current

Links

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

A service characteristic reporting method, a device and a storage medium relate to the technical field of wireless communication. In the method, a terminal acquires service characteristics of a data set, wherein the service characteristics comprise packet loss characteristics and/or characteristics of whether disorder delivery is supported; and the terminal reports the service characteristics of the data to network equipment. The method can realize that the terminal reports the service characteristics of the data set to the network equipment.

Description

Service characteristic reporting method, device and storage medium
Technical Field
The present application relates to the field of wireless communications technologies, and in particular, to a service characteristic reporting method, a device, and a storage medium.
Background
The fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G) system supports video services such as augmented reality (eXtended Reality, XR) and cloud gaming. Aiming at the transmission characteristics of video services such as XR service, the concept of a packet data Unit (PACKET DATA Unit, PDU) set (also called PDU set) is introduced by a higher layer, certain association relation exists between PDUs in the PDU set, and different PDU sets may have different packet loss characteristics. In addition, the application layer may support out-of-order delivery of traffic. The packet loss characteristic of a PDU set and whether the PDU set supports out-of-order delivery may be referred to as the traffic characteristic of the PDU set.
For this situation, how to obtain the service characteristics of PDU set on the New Generation radio access network (NG-RAN) side, so as to improve the transmission efficiency is a problem that needs to be solved at present.
Disclosure of Invention
The embodiment of the application provides a service characteristic reporting method, a device and a storage medium, which are used for realizing that a terminal reports service characteristics of a data set to network equipment.
In a first aspect, a service characteristic reporting method is provided, where the method may be applied to a terminal device, and the method includes: acquiring service characteristics of a data set, wherein the service characteristics comprise packet loss characteristics and/or characteristics of whether disorder delivery is supported; and reporting the service characteristics of the data set to network equipment.
Optionally, the data set includes one or more of:
a data set carried by a first quality of service flow (QoS flow);
a data set carried by a first quality of service sub-flow (QoS sub-flow);
a data set of a first Data Radio Bearer (DRB) bearer;
The first logical channel carries a set of data.
Optionally, the service characteristic of the data set is a service characteristic corresponding to a type of the data set.
Optionally, the acquiring the service characteristic of the data set includes: acquiring service characteristics of the data set according to configuration information sent by the network equipment; the configuration information is used for indicating whether the packet loss characteristic of the data set is needed or allowed to be reported by the terminal, and/or the configuration information is used for indicating whether the packet loss characteristic of the data set is needed or allowed to be reported by the terminal, and whether the out-of-order delivery characteristic is supported.
Optionally, the configuration information includes indication information of a packet loss characteristic type; the acquiring the service characteristics of the data set includes: and acquiring the packet loss characteristics of the data set according to the indication information of the packet loss characteristic type.
Optionally, the acquiring the service characteristic of the data set includes: and acquiring the service characteristics of the data set based on the request for reporting the service characteristics sent by the network equipment.
Optionally, the request for reporting the service characteristic is used for requesting to report the service characteristic of the data set carried by one or more of the first QoS flow, the first QoS sub-flow, the first DRB and the first logical channel.
Optionally, the request for reporting the service characteristic is used for requesting to report the service characteristic corresponding to the type of the data set.
Optionally, the acquiring the service characteristics of the data set and reporting the service characteristics of the data set to the network device includes at least one of the following:
Under the condition of establishing or modifying a first QoS flow, acquiring and reporting the packet loss characteristic of a data set borne by the first QoS flow to the network equipment;
Under the condition of establishing or modifying a first Qos-flow, acquiring and reporting the packet loss characteristic of a data set carried by the first Qos-flow to the network equipment;
Under the condition of adding or modifying a first DRB, acquiring and reporting the packet loss characteristic of a data set borne by the first DRB to the network equipment;
Under the condition of establishing or modifying a first logic channel, acquiring and reporting the packet loss characteristic of a data set borne by the first logic channel to the network equipment;
when the packet loss characteristics of the data set change, acquiring and reporting the packet loss characteristics of the data set after the change to the network equipment;
When the time interval from the last report of the packet loss characteristic of the data set is greater than a set threshold value, acquiring and reporting the packet loss characteristic of the data set to the network equipment;
And if the data set has the packet loss characteristic, acquiring and reporting the packet loss characteristic of the data set to the network equipment.
Optionally, the acquiring the service characteristics of the data set and reporting the service characteristics of the data set to the network device includes at least one of the following:
Under the condition of establishing or modifying a first QoS flow, acquiring and reporting whether a data set carried by the first QoS flow supports the out-of-order delivery or not to the network equipment;
Under the condition of establishing or modifying a first Qos-flow, acquiring and reporting whether a data set carried by the first Qos-flow supports out-of-order delivery or not to the network equipment;
Under the condition of adding or modifying a first DRB, acquiring and reporting whether a data set borne by the first DRB supports out-of-order delivery or not to the network equipment;
under the condition of establishing or modifying a first logic channel, acquiring and reporting whether a data set borne by the first logic channel supports the out-of-order delivery or not to the network equipment;
when the characteristic of whether the data set supports out-of-order delivery changes, acquiring and reporting the changed characteristic of whether the data set supports out-of-order delivery to the network equipment;
when the time interval from the last time of reporting whether the data set supports out-of-order delivery is larger than a set threshold value, acquiring and reporting whether the data set supports out-of-order delivery to the network equipment;
and if the data set has the characteristic of whether the out-of-order delivery is supported, acquiring and reporting the characteristic of whether the out-of-order delivery is supported to the network equipment.
Optionally, the type of the packet loss characteristic includes one or more of the following:
first packet loss characteristic type: in the data set, if any one or a section of data is lost, the rest data in the data set are discarded;
The second packet loss characteristic type: in a data set, if a certain proportion of data is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain proportion of data is correctly transmitted, the rest one or more sections of data in the data set are lost, and the data set is still available to the receiving end;
Third packet loss characteristic type: in a data set, if a certain proportion of data sequenced in front is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain proportion of the data sequenced in the front is correctly transmitted, the rest one or more sections of data in the data set are lost, and the data set is still available to the receiving end;
Fourth packet loss characteristic type: in a data set, if a certain amount of data is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain amount of data is correctly transmitted, one or more pieces of data in the rest of the data set are lost, and the data set is still available to the receiving end;
Fifth packet loss characteristic type: in the data set, if at least two data which are sequenced in the front and are continuous in all data are correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available for a receiving end; wherein the number of the at least two data is associated with a total number of data in the data set; or in the data set, if at least two segments of data which are sequenced in the front and continuous in all the data are correctly transmitted, one or more segments of the rest segments of data in the data set are lost, and the data set is still available for a receiving end; wherein the number of the at least two pieces of data is associated with a total number of pieces of data in the data set;
Sixth packet loss characteristic type: in the data set, if at least one data which is sequenced in the front and continuous is transmitted correctly, the rest one or more data in the data set are lost, and the data set is still available to the receiving end; or in the data set, if at least one segment of data which is sequenced in the front and continuous is transmitted correctly, the rest segment or segments of data in the data set are lost, and the data set is still available to the receiving end.
Optionally, the data set is a PDU set.
In a second aspect, a service characteristic reporting method is provided, where the method may be applied to a network device, and the method includes: and receiving service characteristics of the data set reported by the terminal, wherein the service characteristics comprise packet loss characteristics and/or characteristics of supporting out-of-order delivery.
Optionally, before the service characteristics of the data set reported by the receiving terminal, the method further includes: and sending configuration information to the terminal, wherein the configuration information is used for indicating whether the packet loss characteristic of the data set is required or allowed to be reported by the terminal, and/or the configuration information is used for indicating whether the packet loss characteristic of the data set is required or allowed to be reported by the terminal, and whether the out-of-order delivery characteristic is supported or not.
Optionally, the configuration information includes indication information of a packet loss characteristic type, where the indication information is used to indicate the terminal to report the packet loss characteristic of the corresponding type.
Optionally, before the service characteristics of the data set reported by the receiving terminal, the method further includes: and sending a request for reporting the service characteristics to the terminal.
Optionally, the request for reporting the service characteristic is used for requesting to report the service characteristic of the data set carried by one or more of the first QoS flow, the first QoS sub-flow, the first DRB, and the first logical channel.
Optionally, the request for reporting a service characteristic is used for requesting to report the service characteristic corresponding to the type of the data set.
Optionally, the type of the packet loss characteristic includes one or more of the following:
first packet loss characteristic type: in the data set, if any one or a section of data is lost, the rest data in the data set are discarded;
The second packet loss characteristic type: in a data set, if a certain proportion of data is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain proportion of data is correctly transmitted, the rest one or more sections of data in the data set are lost, and the data set is still available to the receiving end;
Third packet loss characteristic type: in a data set, if a certain proportion of data sequenced in front is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain proportion of the data sequenced in the front is correctly transmitted, the rest one or more sections of data in the data set are lost, and the data set is still available to the receiving end;
Fourth packet loss characteristic type: in a data set, if a certain amount of data is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain amount of data is correctly transmitted, one or more pieces of data in the rest of the data set are lost, and the data set is still available to the receiving end;
Fifth packet loss characteristic type: in the data set, if at least two data which are sequenced in the front and are continuous in all data are correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available for a receiving end; wherein the number of the at least two data is associated with a total number of data in the data set; or in the data set, if at least two segments of data which are sequenced in the front and continuous in all the data are correctly transmitted, one or more segments of the rest segments of data in the data set are lost, and the data set is still available for a receiving end; wherein the number of the at least two pieces of data is associated with a total number of pieces of data in the data set;
Sixth packet loss characteristic type: in the data set, if at least one data which is sequenced in the front and continuous is transmitted correctly, the rest one or more data in the data set are lost, and the data set is still available to the receiving end; or in the data set, if at least one segment of data which is sequenced in the front and continuous is transmitted correctly, the rest segment or segments of data in the data set are lost, and the data set is still available to the receiving end.
Optionally, after receiving the service characteristics of the data set reported by the terminal, the method further includes: and carrying out resource allocation and/or scheduling on data transmission of the data set according to the service characteristics of the data set.
Optionally, the data set is a PDU set.
In a third aspect, a terminal is provided, including a processing unit and a transceiver unit; the processing unit is used for acquiring service characteristics of a data set of the packet data unit, wherein the service characteristics comprise packet loss characteristics and/or characteristics of whether disorder delivery is supported; and the receiving and transmitting unit is used for reporting the service characteristics corresponding to the data set to network equipment.
In a fourth aspect, a network device is provided, including a processing unit and a transceiver unit; the processing unit is used for configuring a terminal to report service characteristics of a data set of a packet data unit, wherein the service characteristics comprise packet loss characteristics and/or characteristics of supporting disorder delivery; the receiving and transmitting unit is used for receiving the service characteristics of the data set reported by the terminal.
In a fifth aspect, there is provided a communication apparatus comprising: a processor, a memory, and a transceiver; the transceiver is used for receiving and transmitting data under the control of the processor; the memory stores computer instructions; the processor being configured to read the computer instructions and perform the method according to any of the first aspects.
In a sixth aspect, there is provided a communication apparatus comprising: a processor, a memory, and a transceiver; the transceiver is used for receiving and transmitting data under the control of the processor; the memory stores computer instructions; the processor being configured to read the computer instructions and perform the method according to any of the second aspects.
In a seventh aspect, there is provided a computer readable storage medium storing computer executable instructions for causing the computer to perform the method according to any one of the first aspects or to perform the method according to any one of the second aspects.
In an eighth aspect, there is provided a computer program product which, when invoked by a computer, causes the computer to perform the method of any one of the first aspects or the second aspects.
In the above embodiment of the present application, since the terminal may report the service characteristics of the data set to the network side, the network side may perform resource allocation and/or scheduling on data transmission of the data set based on the service characteristics of the data set, so as to improve the transmission efficiency of the service.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a diagram illustrating related art PDU set partitioning;
Fig. 2 is a schematic diagram of a communication system according to an embodiment of the present application;
Fig. 3 is a schematic diagram of a service characteristic reporting procedure at a terminal side according to an embodiment of the present application;
Fig. 4 is a schematic diagram of a service characteristic reporting procedure at a network side according to an embodiment of the present application;
Fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present application;
Fig. 6 is a schematic structural diagram of a network device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail below with reference to the accompanying drawings, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In the present embodiment, the terms "network" and "system" are often used interchangeably, but those skilled in the art will understand the meaning.
The term "plurality" in embodiments of the present application means two or more, and other adjectives are similar.
In the embodiment of the application, "and/or", the description of the association relationship of the association object indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
The third generation partnership project (3rd Generation Partnership Project,3GPP) 5G system introduces XR (extended-range) services, which can be divided into the following categories:
-augmented reality (Augmented Reality, AR): seamlessly integrating the real world and the virtual world;
Virtual Reality (VR): generating a virtual world by using equipment simulation;
Mixed Reality (MR): and contains real physical entity and virtual information.
Based on the standard of efficient Video Coding (HEVC), an XR service coded Video stream is formed by a series of groups of pictures (GoP) arranged in sequence. The first frame of a GoP is an I frame (INTRA FRAME, intra frame, also called key frame), followed by a P frame and possibly a B frame (bi-directional frame ). I frames are intra-coded pictures, P frames are forward predicted frames (also referred to as forward reference frames), and B frames are bi-directionally interpolated frames (also referred to as bi-directional reference frames). I-frames can be considered as a complete picture, P-frames and B-frames record changes relative to I-frames, which cannot be decoded without I-frames. I frames in GoP can also be used as instant decoding refresh (Instantaneous Decoding Refresh, IDR) frames, wherein the IDR frames are forced refresh frames, and when the decoder receives the IDR frames, the decoder discards all reference frame queues and resumes decoding, so that errors cannot propagate.
The video coded bit stream of XR traffic is divided into several network abstraction layer (Network Abstract Layer, NAL) units. Priority (nal_ REFERRENCE _idc, NRI) may be included in the NAL unit: for identifying the importance of the NAL unit. Also included in the NAL unit may be a NAL unit type (nal_type): for identifying the type of NAL unit.
A frame image may be divided into slices (slices) or slices (tiles). The Slice may not depend on the data structure of other slices independently encoded in the same picture. The coded data corresponding to one Slice can comprise signal prediction, residual signal reconstruction and entropy coding. The main purpose of using Slice is to guarantee decoding synchronization again after data loss. Each Slice is encapsulated for one NAL unit transmission.
The Slice can be classified into:
I Slice: the coding process of all Coding Units (CUs) in the Slice uses intra prediction;
P Slice: on the basis of the I Slice, the CUs in the Slice can also use inter prediction, and each Prediction Block (PB) uses at most one piece of motion compensation prediction information;
B Slice: on a P Slice basis, a CU in B Slice may also use inter prediction, but each PB may use at most two motion compensated prediction information.
The image frame is divided into rectangular areas with several boundaries, horizontal and vertical, each rectangular area being a slice (Tile) and also being an independent coding unit. The main purpose of slice division is to enhance the ability to process in parallel, and not primarily to provide error robustness. Different tiles of a picture can be divided into a ROI portion and a non-ROI (non-ROI) portion, and the tiles of the ROI portion and the non-ROI portion of the frame can be encapsulated into different NAL units respectively.
NAL units can be divided into two categories depending on the kind of data carried: one type is a video coding layer NAL (VCL NAL) unit containing coded data, such as coded Slice NAL units or Tile NAL units, and the other type is a non-video coding layer NAL (non-VCL NAL) unit containing control data, etc., typically belonging to a plurality of coded pictures, such as parameter set NAL units including the following:
video parameter set (video PARAMETER SET, VPS): the method is mainly used for transmitting video grading information, and is beneficial to the expansion of compatibility standards in scalable video coding or multi-view video.
Sequence parameter set (Sequence PARAMETER SET, SPS): a set of global parameters of the encoded video sequence (Coded video sequence) is stored in the SPS.
Picture PARAMETER SET (PPS): contains common parameters for a picture, i.e. all slices (SLICE SEGMENT, SS) in a picture refer to the same PPS. The NAL units of SPS and PPS are typically located at the start of the entire stream.
XR traffic is modeled in terms of data frames (frames), the same data frame (e.g., I-frame, B-frame, or P-frame) may be partitioned into multiple PDUs, and one or more PDUs may correspond to one NAL unit, that is, one NAL unit may be encapsulated into one or more PDUs. Multiple PDUs may form one PDU set. The PDU set is defined as follows: one or more PDUs corresponding to the same NAL unit constitute one PDU set. The PDUs within PDU set have a certain correlation. For example, as shown in fig. 1, one video frame (i.e., I-frame) may be divided into 3 slices, each Slice is encapsulated into one NAL unit, each NAL unit is encapsulated into multiple PDUs, and all PDUs corresponding to one NAL unit (or Slice) form one PDU set.
The packet loss characteristics of the PDU are different depending on the encoding protocol used, etc. For example, in some embodiments, it is necessary that all PDUs in the PDU set be used by the receiving end only after all PDUs in the PDU set are correctly received (or successfully received) by the receiving end; in other embodiments, when some PDUs in the PDU set are lost, the receiving end may recover, and the receiving end may still use the information contained in the PDU set. In addition, the application layer may support out-of-order delivery of XR traffic.
There is no relevant scheme how the NG-RAN side obtains XR service characteristics currently. Some service characteristics, such as packet loss characteristics of the PDU in PDU set, or whether the application layer supports out-of-order delivery characteristics, do not change frequently, and the terminal side can obtain relevant characteristics according to the application layer of the XR service. Therefore, the embodiment of the application provides a service characteristic reporting method, which can enable the NG-RAN side to acquire service characteristics in time with smaller air interface expenditure, thereby improving the transmission efficiency of the service.
Embodiments of the present application will be described in detail below with reference to the accompanying drawings.
Referring to fig. 2, a schematic diagram of a system architecture used in an embodiment of the present application is shown.
The communication system shown in fig. 2 includes a network device 101 and a terminal 102.
The network device 101 is a device that provides a wireless communication function for a terminal, and is configured to receive an uplink signal from the terminal 102 or transmit a downlink signal to the terminal 102. Network device 101 includes, but is not limited to: a gNB in 5G, a radio network controller (radio network controller, RNC), a Node B (NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (e.g., home evolved nodeB, or home node B, HNB), a BaseBand Unit (BBU), a transmission point (TRANSMITTING AND RECEIVING point, TRP), a transmission point (TRANSMITTING POINT, TP), a mobile switching center, and the like. The base station in the present application may also be a device for providing a wireless communication function for a terminal in other communication systems that may occur in the future.
The terminal 102 is an entity on the user side for receiving or transmitting signals, and is used for sending uplink signals to a network device or receiving downlink signals from the network device. The terminal may also be referred to as UE (user equipment). The terminal 102 may provide voice and/or data connectivity to a user. For example, the terminal may include a handheld device, an in-vehicle device, etc. having a wireless connection function. Currently, the terminal may be: a mobile phone, a tablet, a notebook, a palm, a mobile internet device (mobile INTERNET DEVICE, MID), a wearable device, a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned driving (self-driving), a wireless terminal in smart grid (SMART GRID), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), or the like.
Fig. 2 is merely an example, and is not limited to the type of communication system and the number, type, etc. of devices included in the communication system. The network architecture and the service scenario described in the embodiments of the present application are for illustrating the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided by the embodiments of the present application, and as a person of ordinary skill in the art can know, with evolution of the network architecture and occurrence of a new service scenario, the technical solution provided by the embodiments of the present application is applicable to similar technical problems.
Based on the system architecture shown in fig. 2, in the embodiment of the present application, the terminal may report the packet loss characteristic and/or the characteristic of whether to support out-of-order delivery of the data set to a network device (e.g., NG-RAN node), so as to assist the network device in configuring and/or scheduling resources for the transmission of the data set.
The data set may also be referred to as a data packet set, a data unit set, etc., and the data packet may be a service data packet. The manner of encapsulation and naming of the data or data packets may also vary depending on the communication protocol. One example of such a data set is a set of PDUs (or PDU sets). Taking the PDU set as an example, one data in the data set may be one PDU in the PUD set, and the PDU may be a PDU of the XR service. It will be appreciated that, depending on the protocol, the naming of the data may be different, and the naming of the corresponding data set may be different, which is not a limitation of the embodiments of the present application.
Referring to fig. 3, a flow chart of a service characteristic reporting method implemented by a terminal side according to an embodiment of the present application is shown, where the flow chart may include the following steps:
S301: the terminal acquires service characteristics of the data set, wherein the service characteristics comprise packet loss characteristics and/or characteristics of whether out-of-order delivery is supported.
Alternatively, the data set may be a PDU set of the first service. Optionally, the first service may include an XR service, a cloud game service, and other video services.
Alternatively, the terminal acts as a sender of service data (such as a PDU), which can obtain the service characteristics of the data set directly from the service application layer.
It will be appreciated that taking a PDU data set as an example, the packet loss characteristics may indicate, for one PDU set, the tolerance of the PDU set to PDU packet loss, e.g., that for some PDU sets only one PDU is lost, the PDU set is not available to the receiving end, while for other PDU sets, the PDU set is available to the receiving end as long as some of them can be transmitted correctly. Each packet loss characteristic may correspond to a transmission resource configuration and/or scheduling policy of the network side, so that the network side performs transmission resource configuration and/or scheduling on the PDUs in the PDU set according to the packet loss characteristic of the PDU set. The feature of whether a set of PDUs supports out-of-order delivery refers to whether the PDUs in the set of PDUs can be transmitted out-of-order. The PDU set supports out-of-order transmission and does not support out-of-order transmission, and corresponds to different transmission resource configuration and/or scheduling strategies, so that the network side can carry out transmission resource configuration and/or scheduling on the PDU in the PDU set according to whether the PDU set supports out-of-order delivery.
In one possible implementation, the packet loss characteristics of the data set may include one or more types, each of which may be distinguished using a type identifier. The following exemplary shows several possible packet loss characteristic types:
first packet loss characteristic type: in a data set, if any one or a segment of data is lost, the rest of the data in the data set is discarded. It will be appreciated that if any one or a segment of data in the data set is lost, the remaining data in the data set is allowed or may be discarded. That is, all data in the data set is equally important, and only after all data in the data set is correctly transmitted, the data set is available to the receiving end.
It will be appreciated that a data set is available to the receiving end, meaning that the data set is useful to the receiving end, that is, the receiving end can use the data set (or information contained in the data set).
Taking XR service as an example, if the NAL unit corresponding to the PDU set contains video encoded data of an I frame, since the I frame is used as a key frame, and the subsequent P frame needs to be recovered by inter-frame prediction based on the I frame, the packet loss characteristic of the PDU set corresponding to the I frame belongs to the first packet loss characteristic type. For example, if part of the data in the I frame is lost, the receiving end discards other data already received in the I frame, or the receiving end may notify the transmitting end that the non-transmitting part of the I frame does not need to be transmitted, thereby saving transmission resources.
The second packet loss characteristic type: in the data set, if a certain proportion of data is correctly transmitted, one or more other data in the data set is lost, and the data set is still available to the receiving end. Or in the data set, if a certain proportion of data is correctly transmitted, the rest one or more sections of data in the data set are lost, and the data set is still available to the receiving end.
Taking XR service as an example, if only a certain proportion of the NAL units corresponding to the PDU set can be correctly transmitted, even if some other PDUs are lost, the recovery can be performed based on the received PDUs, and at this time, the packet loss characteristics of the PDU set may belong to the second packet loss characteristic type.
Alternatively, the receiving end may be an NG-RAN, or a core network node, or an application layer server. Taking an application layer server as an example, the application layer server may perform processes such as parsing received data or data sets.
In one possible implementation, the specific value of the "certain proportion" is not a fixed value, but indicates that the data set has such a packet loss characteristic. The specific value of the "certain proportion" may be reported to the network device by the terminal.
In another possible implementation manner, the specific value of the "certain proportion" may be a preset value range, for example, the value range may be described as a number of x% which is the lowest, and x is greater than 0 and less than 100, for example, the value range of x is any number between 0 and 100. That is, if the lowest x% of the data in the data set is correctly received, the data set is still available to the receiving end, and the data set belongs to the second packet loss characteristic type.
One example of the second packet loss characteristic type is: taking the PDU set as an example, if the terminal device has correctly transmitted 80% of the PDUs in a certain PDU set to the NG-RAN, the PDU set is useful for the receiving end, the network side can correctly parse the PDU set, and other PDUs in the PDU set can be allowed to be discarded or lost. It should be noted that, although the terminal first transmits the PDU to the NG-RAN, the NR-RAN may be delivered to the relevant node, and may be finally delivered to the application layer for parsing, so the network side may be the NG-RAN, or may be a core network node or an application layer server, which is not limited in this embodiment of the present application.
Third packet loss characteristic type: in a data set, if a certain proportion of the data in the first order is correctly transmitted, the rest one or more data in the data set is lost, and the data set is still available to a receiving end. Or in the data set, if a certain proportion of the data sequenced in the front is correctly transmitted, the rest one or more pieces of data in the data set are lost, and the data set is still available to the receiving end.
Taking XR service as an example, if some PDUs in the NAL units corresponding to the PDU sets contain important information, the packet loss characteristics of the corresponding PDU sets may belong to the third packet loss characteristic type.
In one possible implementation, the data in the data set may be ordered by sequence number. The data that is sorted first herein means data that is sorted first by sequence number.
In another possible implementation, the data in the data set may be ordered by priority or importance. The data which is ranked before here means data which is ranked before from high to low in priority or importance.
Similar to the second packet loss characteristic type, in one possible implementation manner, the specific value of the "certain proportion" is not a fixed value, and the specific value of the "certain proportion" may be reported to the network device by the terminal. In another possible implementation manner, the specific value of the "certain proportion" may be a preset value range, for example, the value range may be described as the lowest y%, where y is greater than 0 and less than 100, for example, the value range of y is any number between 1 and 100.
One example of the third packet loss characteristic type is: taking the PDU set as an example, when the terminal has correctly transmitted the first 60% of PDUs in a certain PDU set to the NG-RAN, the PDU set is useful for the receiving end, the network side can correctly parse the PDU set, and other PDUs remaining in the PDU set can be allowed to be discarded or lost. The meaning of the network side is the same as that of the network side in the second packet loss characteristic type.
Fourth packet loss characteristic type: in a data set, if a certain amount of data is transmitted correctly, the rest of one or more data in the data set is lost, and the data set is still available to the receiving end. Or in the data set, if a certain amount of data is correctly transmitted, one or more pieces of data in the rest data set are lost, and the data set is still available to the receiving end.
In one possible implementation, the specific value of the "certain number" is not a fixed value, but indicates that the data set has such a packet loss characteristic. The specific numerical value of the "certain number" may be reported to the network device by the terminal.
In another possible implementation manner, the specific value of the "certain number" may be a preset value range, for example, the value range may be described as a minimum of k, where k is an integer greater than 1, and k is less than the total number of data contained in the data set. That is, if k or more data are correctly received in the data set, which is still available to the receiving end, the data set belongs to the fourth packet loss characteristic type.
One example of the fourth packet loss characteristic type is: taking a PDU set as an example, a certain PDU set of the terminal includes 20 (n=20) PDUs in total, if any 15 (k=15) or more than 15 PDUs in the 20 PDUs are correctly transmitted to the NG-RAN, the PDU set is useful to the receiving end, the network side can correctly analyze the PDU set, and other PDUs in the PDU set can be allowed to be discarded or lost.
Fifth packet loss characteristic type: in the data set, if at least two data which are sequenced in the front and continuous in all the data are correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to the receiving end, wherein the number of the at least two data is related to the total number of the data in the data set. Or in the data set, if at least two segments of data which are sequenced in the front and continuous in all the data are correctly transmitted, the rest one segment or more segments of data in the data set are lost, and the data set is still available for the receiving end; wherein the number of the at least two pieces of data is associated with the total number of pieces of data in the data set.
In one possible implementation, the data in the data set may be ordered by sequence number. The data that is sorted first herein means data that is sorted first by sequence number. In another possible implementation, the data in the data set may be ordered by priority or importance. The data which is ranked before here means data which is ranked before from high to low in priority or importance.
In one possible implementation, the specific values of "at least two" are not fixed values, but rather indicate that the data set has such a packet loss characteristic. The specific values of the 'at least two' can be reported to the network device by the terminal.
In another possible implementation manner, the specific value of "at least two" may be a preset value range, for example, the value range may be described as a minimum of n, where n is an integer greater than 1, and n is less than the total number of data contained in the data set. That is, as long as the first n data in the data set is correctly received, the data set is still available to the receiving end, and the data set belongs to the fifth packet loss characteristic type.
In the fifth packet loss characteristic type, the number of the "at least two data" is associated with the total number of data in the data set. For example, taking the value of the "at least two data" as an example, if the total number of data in the data set n=100, n=50; if the total number of data in the data set n=200, then n=80. The correlation manner between N and N (or the rule between N and N values) is not limited in this embodiment of the present application.
One example of the fifth packet loss characteristic type is: taking a PDU set as an example, a certain PDU set of the terminal includes 20 (n=20) PDUs, when the first 15 PDUs in the 20 PDUs are correctly transmitted to the NG-RAN, the PDU set is useful for the receiving end, the network side can correctly parse the PDU set, and other PDUs in the PDU set can be allowed to be discarded or lost.
Sixth packet loss characteristic type: in the data set, if the first one or more data are correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to the receiving end. Or in the data set, if at least one segment of data which is sequenced in the front and continuous is transmitted correctly, the rest segment or segments of data in the data set are lost, and the data set is still available to the receiving end.
In one possible implementation, the data in the data set may be ordered by sequence number. The data that is sorted first herein means data that is sorted first by sequence number. In another possible implementation, the data in the data set may be ordered by priority or importance. The data which is ranked before here means data which is ranked before from high to low in priority or importance.
In one possible implementation, the specific value of "one or more" is not a fixed value, and the specific value of "one or more" may be reported to the network device by the terminal. In another possible implementation manner, the specific value of the "one or more" may be a preset value range, for example, the value range may be described as a minimum of n, where n is an integer greater than or equal to 1. That is, as long as the first n data in the data set is correctly received, the data set is still available to the receiving end, and the data set belongs to the sixth packet loss characteristic type.
Taking the PDU set as an example, in some cases, some PDUs in the PDU set may have higher importance, for example, when n=1, it is important to indicate that the first PDU in the PDU set is important, when the first PDU is lost, other PDUs are not useful (cannot be parsed), when the first PDU is correctly received, the PDU set is useful to the receiving end, the network side can correctly parse the PDU set, and other PDUs in the PDU set may be allowed to be discarded or lost. For another example, when n=n-1, it indicates that the last PDU in the PDU set may be available, and even if the last PDU is lost, the network side may parse the PDU set according to other PDUs in the PDU set, so that when all other PDUs except the last PDU in the PDU set are correctly transmitted to the NG-RAN, the PDU set is useful to the receiving end, and the last PDU in the PDU set may be allowed to be discarded or lost.
It should be noted that the above six types of packet loss characteristics are merely examples, and the embodiments of the present application are not limited thereto. In addition, the examples in each packet loss type are only some possible cases, and the embodiment of the present application is not limited thereto.
In one possible implementation, there may be multiple types of data sets, for example, PDU sets, such as NAL units corresponding to PDU set 1 containing I-frame video encoded data and NAL units corresponding to PDU set 2 containing B-frame video encoded data, the two PDU sets belonging to different types. Different types of PDU sets correspond to different importance (importance), and their traffic characteristics may also be different. Taking the two PDU sets as an example, PDU set 1 is more important than PDU set 2, and the packet loss characteristic of PDU set 1 belongs to the first packet loss characteristic type, and the packet loss characteristic of PDU set 2 belongs to the second packet loss characteristic type.
In the above case, when the terminal acquires the service characteristics of the data set, the terminal may acquire the service characteristics corresponding to the type of the data set. For example, taking the two PDU sets as an example, the terminal may acquire the packet loss characteristics of the first packet loss characteristic type for the PDU set 1, and acquire the packet loss characteristics of the second packet loss characteristic type for the PDU set 2.
In a possible implementation manner, the terminal may obtain the service characteristics of the following data sets:
-traffic characteristics of a data set carried by a first quality of service flow (QoS flow). Optionally, taking PDU sets as an example, the network side may map the PDU sets corresponding to NAL units of the same type onto the same QoS flow for transmission according to the type or priority of the NAL units corresponding to the PDU sets, or map the PDU sets corresponding to NAL units of the same priority onto the same QoS flow for transmission. The network side can allocate one or more QoS flows for PDU uplink transmission of the terminal, and the terminal can report service characteristics of PDU sets carried by one or more QoS flows.
-Traffic characteristics corresponding to the first quality of service sub-flow (QoS sub-flow). Optionally, one QoS flow may include multiple QoS sub-flows. Taking PDU sets as an example, the network side may map the PDU sets corresponding to NAL units of the same subtype onto the same QoS sub-flow for transmission according to the finer granularity type (called subtype) of the NAL units corresponding to the PDU sets. The network side can allocate one or more QoS sub-flows for PDU uplink transmission of the terminal, and the terminal can report service characteristics of PDU sets borne by one or more QoS sub-flows.
-A traffic characteristic corresponding to the first data radio bearer (Data Radio Bearer, DRB). Optionally, taking PDU sets as an example, the network side may map the PDU sets corresponding to NAL units of the same type onto the same DRB for transmission, or map the PDU sets corresponding to NAL units of the same priority onto the same DRB for transmission, according to the type or priority of the NAL units corresponding to the PDU sets. The network side can allocate one or more DRB for PDU uplink transmission of the terminal, and the terminal can report the service characteristics of the PDU set carried by one or more DRB.
-Traffic characteristics corresponding to the first logical channel. Optionally, taking PDU sets as an example, the network side may map the PDU sets corresponding to NAL units of the same type to the same logical channel for transmission according to the type or priority of the NAL units corresponding to the PDU sets, or map the PDU sets corresponding to NAL units of the same priority to the same logical channel for transmission. The network side can allocate one or more logic channels for PDU uplink transmission of the terminal, and the terminal can report the service characteristics of the PDU set carried by one or more logic channels.
In one possible implementation, the terminal may automatically obtain the service characteristics of the data set, so as to report the service characteristics to the network device.
Optionally, for the packet loss characteristic, the terminal may automatically acquire and report the characteristic under one or more of the following conditions:
-in case of setting up (setup) or modifying the first QoS flow, the terminal obtains the packet loss characteristics of the data set of the QoS flow bearer for reporting to the network device in a subsequent step.
-In case of establishing or modifying the first QoS sub-flow, the terminal obtains the packet loss characteristics of the data set of the QoS sub-flow bearer for reporting to the network device in a subsequent step.
-In case of adding or modifying the first DRB, the terminal obtains the packet loss characteristics of the data set carried by the DRB for reporting to the network device in a subsequent step.
In case the first logical channel is established or modified, the terminal acquires the packet loss characteristics of the data set carried by this logical channel for reporting to the network device in a subsequent step.
In case of a change in the packet loss characteristics of a data set, such as the first data set, the terminal obtains the packet loss characteristics of the data set after the change for reporting to the network device in a subsequent step.
-The terminal obtaining the packet loss characteristics of the data set for reporting to the network device in a subsequent step when the time interval from the last reporting of the packet loss characteristics of the data set by the terminal is greater than a set threshold. Alternatively, the set threshold may be set according to factors such as service requirements or transmission performance requirements, for example, the set threshold may be in seconds, or may be in a smaller or larger time granularity level, which is not limited by the embodiment of the present application.
-If the data set has packet loss characteristics, acquiring the packet loss characteristics of the data set for reporting to the network device in a subsequent step.
Some data sets, such as PDU sets containing I-frame video encoded data, have a certain requirement on packet loss rate, and thus have packet loss characteristics. For other data sets, even if the data contained in the data sets are lost, the data sets have no great influence on the service, and the data sets have no packet loss characteristic.
Optionally, regarding the feature of whether out-of-order delivery is supported, the terminal may automatically acquire and report the feature under one or more of the following conditions:
-in case the first QoS flow is established or modified, the terminal obtains whether the data set of the QoS flow bearer supports out-of-order delivery characteristics for reporting to the network device in a subsequent step.
-In case the first QoS sub-flow is established or modified, the terminal obtains whether the data set of the QoS sub-flow bearer supports out-of-order delivery characteristics for reporting to the network device in a subsequent step.
-In case of adding or modifying the first DRB, the terminal obtains whether the data set carried by the DRB supports out-of-order delivery characteristics for reporting to the network device in a subsequent step.
In the case of setting up or modifying the first logical channel, the terminal obtains whether the data set carried by this logical channel supports the feature of out-of-order delivery, in order to be reported to the network device in a subsequent step.
In case of a change in the characteristics of whether the data set (e.g. the first data set) supports out-of-order delivery, the terminal obtains the changed characteristics of whether the data set supports out-of-order delivery for reporting to the network device in a subsequent step.
-The terminal obtaining the characteristic of whether the data set supports out-of-order delivery when the time interval from the last time the terminal reported the characteristic of whether the data set supports out-of-order delivery is greater than a set threshold. Alternatively, the set threshold may be set according to factors such as service requirements or transmission performance requirements, for example, the set threshold may be in seconds, or may be in a smaller or larger time granularity level, which is not limited by the embodiment of the present application.
-If the data set has the property of whether out-of-order delivery is supported, obtaining the property of whether out-of-order delivery is supported for reporting to the network device in a subsequent step.
In one possible implementation, the network device may send a request for reporting the service characteristics to the terminal, and the terminal may obtain the service characteristics of the data set of the first service based on the request, so as to report to the network device in a subsequent step.
In a possible implementation manner, the request for reporting the service characteristic may be used for requesting the terminal to report the service characteristic of the data set of the first QoS flow bearer, or request to report the service characteristic of the data set of the first QoS sub-flow bearer, or request to report the service characteristic of the data set of the first DRB bearer, or request to report the service characteristic of the data set of the first logical channel bearer, or a combination of the above, for example, request to report the service characteristic of the data set of the first QoS flow bearer and the service characteristic of the data set of the first QoS sub-flow bearer. The terminal may obtain, according to a request from the network side, service characteristics of the data set, so as to report, in a subsequent step, the one or more service characteristics to the network device.
In another possible implementation manner, the request for reporting a service characteristic is used for requesting to report a service characteristic corresponding to a type of the data set. The terminal can acquire the service characteristics corresponding to the types of the data sets according to the request of the network side so as to report the service characteristics to the network equipment in the subsequent step.
In one possible implementation manner, when the network side requests the terminal to report the packet loss characteristics of the data set, the network side may further request the type of the packet loss characteristics to be reported. For example, the network side may carry the indication information of the packet loss characteristic type in the request, so as to request the terminal to report the packet loss characteristic of the corresponding type. The type of the packet loss characteristics may be referred to in the foregoing description, and will not be described in detail herein.
In one possible implementation manner, the network side may send configuration information to the terminal, so as to indicate whether the terminal needs (or allows) to report the packet loss characteristic of the data set, and/or indicate whether the terminal needs (or allows) to report whether the data set supports out-of-order delivery. Correspondingly, the terminal can acquire the special characteristics of the data set according to the configuration information sent by the network equipment. For example, if the configuration information sent by the network device indicates that "the terminal needs (or allows) to report the packet loss characteristics of the PDU set", the terminal acquires the packet loss characteristics of the PDU set so as to report to the network device in a subsequent step; if the configuration information sent by the network device indicates that the terminal needs (or allows) to report whether the characteristics of out-of-order delivery are supported, the terminal acquires whether the PDU set supports the characteristics of out-of-order delivery or not so as to report to the network device in a subsequent step; if the configuration information sent by the network device indicates to report the two characteristics, the terminal acquires the two characteristics of the PDU set to report to the network device in a subsequent step.
Optionally, the configuration information includes indication information of a packet loss characteristic type, for example, the configuration information includes an identifier of the packet loss characteristic type, and in this case, the terminal may obtain, according to the indication information of the packet loss characteristic type, a packet loss characteristic of a corresponding type of the data set, so as to report to the network device in a subsequent step.
S302: and the terminal reports the service characteristics of the acquired data set to the network equipment.
In a possible implementation manner, when the terminal reports the service characteristics based on the type of the packet loss characteristics requested by the network side, the terminal may also report the supporting situation of the type of the requested packet loss characteristics.
For example, taking a PDU set as an example, in a case where a network device (e.g., an NG-RAN side node) requests a terminal to report a packet loss characteristic of a second packet loss type, if a service of the terminal supports the packet loss characteristic of the second packet loss type, the terminal may further report a percentage value, such as x%, for indicating a PDU duty cycle, where, as long as no less than x% of PDUs in the PDU set are correctly transmitted, remaining PDUs in the PDU set may be discarded, and the PDU set is available to a receiving end; if the service of the terminal does not support the packet loss characteristic of the type, the terminal can report a null value (used for indicating that the terminal does not indicate the characteristic) or report indication information that the characteristic is not supported, or the terminal does not report the packet loss characteristic of the type.
For another example, taking a PDU set as an example, in a case where a network device (e.g., an NG-RAN side node) requests a terminal to report a packet loss characteristic of a fourth packet loss type, if a service of the terminal supports the packet loss characteristic, the terminal may further report a value for indicating the number of PDUs, for example, k, which indicates that as long as not less than k PDUs in the PDU set are correctly transmitted, remaining PDUs in the PDU set may be discarded, where the PDU set is available to a receiving end, and optionally, the terminal may further increase the total number of PDUs in the PDU set; if the service of the terminal does not support the packet loss feature, the terminal may report a null value (to indicate that the terminal does not indicate the feature) or report indication information that the feature is not supported, or the terminal does not report the type of packet loss feature.
In a possible implementation manner, when reporting the packet loss characteristics of the data set, the terminal may report indication information (such as a type identifier) of the packet loss characteristic type supported by the data set, and further may report relevant parameters of the packet loss characteristic type.
For example, taking a PDU set as an example, if the PDU set supports the second packet loss characteristic type, the terminal may report a type identifier of the second packet loss characteristic type for the PDU set, and may further report a percentage value for indicating a PDU duty cycle, such as x%, which indicates that, as long as no less than x% of PDUs in the PDU set are correctly transmitted, the remaining PDUs in the PDU set may be discarded, and the PDU set is available to the receiving end. For different values of x%, the network side may employ different resource configurations and/or scheduling policies.
For example, taking a PDU set as an example, if the PDU set supports the third packet loss characteristic type, the terminal may report a type identifier of the third packet loss characteristic type for the PDU set, and may further report a percentage value, such as y%, for indicating a PDU duty cycle, which indicates that, as long as not less than y% of the PDUs in the PDU set that are ordered in the front are correctly transmitted, the remaining PDUs in the PDU set may be discarded, where the PDU set is available to the receiving end. For different values of y%, the network side may employ different resource configurations and/or scheduling policies. Further, the terminal may also report the total number of PDUs in the PDU set.
For example, taking a PDU set as an example, if the PDU set supports the fourth packet loss characteristic type, the terminal may report a type identifier of the corresponding packet loss characteristic type for the PDU set, and may further report a value for indicating the number of PDUs, for example, k, which indicates that, if no less than k PDUs in the PDU set are correctly transmitted, the remaining PDUs in the PDU set may be discarded, where the PDU set is available to the receiving end. For different values of k, the network side may employ different resource configurations and/or scheduling policies. Further, the terminal may also report the total number of PDUs in the PDU set.
For example, taking a PDU set as an example, if the PDU set supports the fifth packet loss characteristic type, the terminal may report a type identifier of the corresponding packet loss characteristic type for the PDU set, and may further report a value indicating the number of PDUs, for example, n, which indicates that, in the PDU set, as long as the first n PDUs are correctly transmitted, the remaining PDUs of the PDU set may be discarded, and the PDU set is available to the receiving end. For different values of n, the network side may employ different resource configurations and/or scheduling policies. Further, the terminal may also report the total number of PDUs in the PDU set.
In one possible implementation manner, after the terminal reports the packet loss characteristic of the data set, if the terminal finds that the packet loss characteristic of the data set reported before changes, the terminal may report the packet loss characteristic of the changed data set to the network device (such as NG-RAN). Optionally, after acquiring the packet loss characteristic of the changed data set, the terminal reports the packet loss characteristic of the changed data set to the network device when the packet loss characteristic of the data set reported last time is greater than a set threshold.
In one possible implementation manner, after the terminal reports the characteristic of whether the data set supports out-of-order delivery, if the terminal finds that the characteristic of whether the data set previously reported supports out-of-order delivery changes, the terminal may report the changed characteristic of whether the data set supports out-of-order delivery to a network device (such as NG-RAN). Optionally, after obtaining the characteristic of whether the changed data set supports out-of-order delivery, the terminal reports the characteristic of whether the changed data set supports out-of-order delivery to the network device when the characteristic of whether the data set supports out-of-order delivery from the last time is greater than a set threshold.
In the flow shown in fig. 3, since the terminal may report the service characteristics of the data set to the network side, the network side may perform resource allocation and/or scheduling on data transmission of the data set based on the service characteristics of the data set, so as to improve the transmission efficiency of the service.
Referring to fig. 4, a flow chart of a service characteristic reporting method implemented by a network side according to an embodiment of the present application is shown, where the flow chart may include the following steps:
S401: the network equipment receives service characteristics of a data set reported by the terminal, wherein the service characteristics comprise packet loss characteristics and/or characteristics of whether disorder delivery is supported.
The service characteristics of the data set, and the reporting method, may refer to the relevant content of the flow shown in fig. 3, and are not repeated here.
S402: and the network equipment performs resource allocation or scheduling on the data transmission of the data set according to the service characteristics of the data set reported by the terminal. This step is an optional step.
For example, if the terminal reports that the data set supports the first packet loss characteristic type, the network device (e.g., NG-RAN) may configure a link with good signal quality and low error rate for a link transmitting the data set.
For example, taking a PDU set as an example, if the terminal reports that the PDU set carried by the first QoS flow supports the second packet loss characteristic type and reports a value x% for indicating the number of PDUs, when the network device (e.g., NG-RAN) schedules uplink data carried by the QoS flow (PDUs in the PDU set), if it finds that x% of PDUs are correctly transmitted to the NG-RAN, the priority of scheduling the uplink data carried by the QoS flow may be reduced.
For example, taking a PDU set as an example, if the terminal reports that the PDU set carried by the first Qos sub-flow supports the third packet loss characteristic type and reports a value y "for representing the number of PDUs in the PDU set, when the network device (e.g., NG-RAN) schedules the data carried by the Qos sub-flow, the network device preferentially schedules the first y% of PDUs in the PDU set.
For example, taking a PDU set as an example, if the terminal reports that the PDU set carried by the first DRB supports the fourth packet loss characteristic type, the network device (e.g., NG-RAN) may configure to start the early discard function for the DRB; specifically, the early discard function may be configured to be turned on under certain conditions preset.
Taking PDU sets as an example, if the terminal reports that the PDU set carried by the first DRB supports the fifth packet loss characteristic type and reports a value n for representing the number of PDUs, the network device (e.g., NG-RAN) may configure a related early discard function, and further, may configure a discard condition; or to schedule preferentially the first n PDUs in the PDU set.
For example, taking a PDU set as an example, if the terminal reports that the PDU set carried by the first logical channel supports the sixth packet loss characteristic type and reports a value n for indicating the number of PDUs, when the network device (e.g., NG-RAN) schedules the logical channel, if the first n PDUs in a certain PDU set carried by the logical channel have been correctly received, the NG-RAN may notify the terminal that the remaining PDUs except the first n PDUs in the PDU set may not be transmitted.
For example, taking a PDU set as an example, if the terminal reports that the PDU set of the first QoS flow bearer supports out-of-order delivery, the network device (e.g., NG-RAN) may start out-of-order delivery for the air interface configuration of the QoS flow bearer, thereby improving the air interface transmission efficiency.
In the flow shown in fig. 4, since the terminal may report the service characteristics of the data set to the network side, the network side may perform resource allocation and/or scheduling on transmission of data in the data set based on the service characteristics of the data set, so as to improve the transmission efficiency of the service.
Based on the same technical conception, the embodiment of the application also provides a terminal. The terminal can realize the functions of the terminal side in the above embodiments.
Fig. 5 illustrates a terminal provided by an embodiment of the present application, where the terminal may include: a processing unit 501 and a transceiver unit 502.
A processing unit 501, configured to obtain service characteristics of a data set, where the service characteristics include packet loss characteristics and/or characteristics that support out-of-order delivery; and the transceiver unit 502 is configured to report the service characteristics corresponding to the data set to a network device.
Optionally, the data set includes one or more of the following: the data transmission method comprises the steps of a data set borne by a first QoS flow, a data set borne by a first QoS sub-flow, a data set borne by a first DRB and a data set borne by a first logic channel.
Optionally, the service characteristic of the data set is a service characteristic corresponding to a type of the data set.
Optionally, the processing unit 501 is specifically configured to: acquiring service characteristics of the data set according to configuration information sent by the network equipment; the configuration information is used for indicating whether the packet loss characteristic of the data set is required or allowed to be reported by the terminal, and/or the configuration information is used for indicating whether the packet loss characteristic of the data set is required or allowed to be reported by the terminal and whether the out-of-order delivery is supported or not.
Optionally, the configuration information includes indication information of a packet loss characteristic type; the processing unit 501 is specifically configured to: and acquiring the packet loss characteristics of the corresponding types of the data set according to the indication information of the packet loss characteristic types.
Optionally, the processing unit 501 is specifically configured to: and acquiring the service characteristics of the data set based on the request for reporting the service characteristics sent by the network equipment.
Optionally, the request for reporting the service characteristic is used for requesting to report the service characteristic of the data set carried by one or more of the first QoS flow, the first QoS sub-flow, the first DRB and the first logical channel.
Optionally, the request for reporting a service characteristic is used for requesting to report the service characteristic corresponding to the type of the data set.
Optionally, the processing unit 501 is specifically configured to perform one or more of the following operations:
Under the condition of establishing or modifying the first QoS flow, acquiring and reporting the packet loss characteristic of the data set borne by the first QoS flow to the network equipment through a receiving and transmitting unit 502;
Under the condition of establishing or modifying a first Qos-flow, acquiring and reporting the packet loss characteristic of a data set carried by the first Qos-flow to the network equipment;
Under the condition of adding or modifying the first DRB, acquiring and reporting the packet loss characteristic of the data set borne by the first DRB to the network equipment through a transceiver unit 502;
under the condition of establishing or modifying a first logic channel, acquiring and reporting the packet loss characteristic of a data set borne by the first logic channel to the network equipment through a transceiver unit 502;
when the packet loss characteristics of the data set change, acquiring and reporting the packet loss characteristics of the data set after the change to the network equipment through a receiving and transmitting unit 502;
When the time interval from the last report of the packet loss characteristics of the data set by the terminal is greater than a set threshold value, acquiring and reporting the packet loss characteristics of the data set to the network equipment through the transceiver unit 502;
If the data set has the packet loss characteristic, the packet loss characteristic of the data set is obtained and reported to the network device through the transceiver unit 502.
Optionally, the processing unit 501 is specifically configured to perform one or more of the following operations:
Under the condition of establishing or modifying the first QoS flow, acquiring and reporting whether the data set carried by the first QoS flow supports the out-of-order delivery or not to the network equipment through a receiving and transmitting unit 502;
under the condition of establishing or modifying a first Qos sub-flow, acquiring and reporting whether a data set carried by the first Qos sub-flow supports out-of-order delivery or not to the network equipment through a receiving and transmitting unit 502;
Under the condition of adding or modifying the first DRB, acquiring and reporting whether the data set carried by the first DRB supports out-of-order delivery or not to the network equipment carrier through a receiving and transmitting unit 502;
under the condition of establishing or modifying a first logic channel, acquiring and reporting whether a data set borne by the first logic channel supports out-of-order delivery or not to the network equipment through a receiving and transmitting unit 502;
When the characteristics of whether the data set supports out-of-order delivery change, acquiring and reporting the characteristics of whether the data set changes and supports out-of-order delivery to the network equipment through a receiving and transmitting unit 502;
When the time interval from the last time of reporting whether the data set supports out-of-order delivery is greater than a set threshold value, acquiring and reporting whether the data set supports out-of-order delivery to the network equipment through the transceiver unit 502;
if the data set has the characteristic of whether to support out-of-order delivery, the characteristic of whether to support out-of-order delivery of the data set is obtained and reported to the network device through the transceiver unit 502.
It should be noted that, the above terminal provided by the embodiment of the present application can implement all the method steps implemented by the terminal in the embodiment of the method, and can achieve the same technical effects, and the same parts and beneficial effects as those of the embodiment of the method in the embodiment are not described in detail herein.
Based on the same technical conception, the embodiment of the application also provides network equipment. The network device may implement the functions of the network side in the above embodiments.
Fig. 6 illustrates a network device according to an embodiment of the present application, where the network device may include: processing unit 601, receiving and transmitting unit 602.
The processing unit 601 is configured to configure service characteristics of a data set reported by a terminal, where the service characteristics include packet loss characteristics and/or characteristics of whether out-of-order delivery is supported; and the transceiver 602 is configured to receive the service characteristics of the data set reported by the terminal.
Optionally, the processing unit 601 is further configured to: before receiving, by the transceiver 602, the service characteristics of the data set reported by the terminal, the transceiver 602 sends configuration information to the terminal, where the configuration information is used to indicate whether packet loss characteristics of the data set are needed or allowed to be reported by the terminal, and/or the configuration information is used to indicate whether characteristics of whether out-of-order delivery is needed or allowed to be supported by the terminal to report the data set.
Optionally, the configuration information includes indication information of a packet loss characteristic type, where the indication information is used to indicate the terminal to report the packet loss characteristic of the corresponding type.
Optionally, the processing unit 601 is further configured to: before receiving, by the transceiver 602, the service characteristics of the data set reported by the terminal, a request for reporting the service characteristics is sent to the terminal by the transceiver 602.
Optionally, the request for reporting the service characteristic is used for requesting to report the service characteristic of the data set of at least one of the first QoS flow, the first QoS sub-flow, the first DRB and the first logical channel.
Optionally, the request for reporting a service characteristic is used for requesting to report the service characteristic corresponding to the type of the data set.
Optionally, the processing unit 602 is further configured to: after receiving the service characteristics of the data set reported by the terminal through the transceiver unit 602, resource allocation and/or scheduling are performed on the transmission of the data in the data set according to the service characteristics of the data set.
It should be noted that, the network device provided in the embodiment of the present application can implement all the method steps implemented by the network device in the embodiment of the method, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those of the embodiment of the method in the embodiment are omitted.
Based on the same technical concept, the embodiment of the application also provides a communication device, which can realize the functions of the corresponding equipment in the previous embodiment.
Fig. 7 schematically illustrates a configuration of a communication apparatus in an embodiment of the present application. As shown, the communication device may include: a processor 701, a memory 702, a transceiver 703 and a bus interface 704.
The processor 701 is responsible for managing the bus architecture and general processing, and the memory 702 may store data used by the processor 701 in performing operations. The transceiver 703 is used to receive and transmit data under the control of the processor 701.
A bus architecture may comprise any number of interconnecting buses and bridges, and in particular one or more processors represented by the processor 701 and various circuits of memory represented by the memory 702. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The processor 701 is responsible for managing the bus architecture and general processing, and the memory 702 may store data used by the processor 701 in performing operations.
The flow disclosed in the embodiments of the present application may be applied to the processor 701 or implemented by the processor 701. In implementation, the steps of the signal processing flow may be performed by integrated logic circuits of hardware in the processor 701 or instructions in the form of software. The processor 701 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and may implement or perform the methods, steps and logic blocks disclosed in embodiments of the application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in the memory 702, and the processor 701 reads the information in the memory 702, and completes the steps of the signal processing flow in combination with its hardware.
Specifically, the processor 701 is configured to read the computer instructions in the memory 702 and execute the functions implemented by the corresponding devices in the flow shown in the foregoing embodiment of the present application.
It should be noted that, the communication device provided in the embodiment of the present application can implement all the method steps implemented in the method embodiment and achieve the same technical effects, and the same parts and beneficial effects as those of the method embodiment in the embodiment are not described in detail herein.
The embodiment of the application also provides a computer readable storage medium, which stores computer executable instructions for causing a computer to execute the method executed by the corresponding device in the above embodiment.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims (27)

1. The service characteristic reporting method is characterized by comprising the following steps:
acquiring service characteristics of a data set, wherein the service characteristics comprise packet loss characteristics and/or characteristics of whether disorder delivery is supported;
And reporting the service characteristics of the data set to network equipment.
2. The method of claim 1, wherein the data set comprises one or more of:
a data set carried by a first quality of service (QoS) flow;
a data set carried by the QoS sub-flow of the first service quality sub-flow;
A data set carried by a first data radio bearer, DRB;
The first logical channel carries a set of data.
3. The method according to any of claims 1-2, wherein the traffic characteristics of the data set are traffic characteristics corresponding to the type of the data set.
4. A method according to any of claims 1-3, wherein said obtaining traffic characteristics of the data set comprises:
Acquiring service characteristics of the data set according to configuration information sent by the network equipment; the configuration information is used for indicating whether the packet loss characteristic of the data set is needed or allowed to be reported by the terminal, and/or the configuration information is used for indicating whether the packet loss characteristic of the data set is needed or allowed to be reported by the terminal, and whether the out-of-order delivery characteristic is supported.
5. The method of claim 4, wherein the configuration information comprises indication of a type of packet loss characteristics;
the acquiring the service characteristics of the data set includes:
and acquiring the packet loss characteristics of the data set according to the indication information of the packet loss characteristic type.
6. The method according to any of claims 1-5, wherein the obtaining the traffic characteristics of the data set comprises:
And acquiring the service characteristics of the data set based on the request for reporting the service characteristics sent by the network equipment.
7. The method of claim 6, wherein the request for reporting traffic characteristics is for requesting reporting traffic characteristics of a data set carried by one or more of a first QoS flow, a first QoS sub-flow, a first DRB, a first logical channel.
8. The method according to any of claims 6-7, wherein the request to report traffic characteristics is for requesting reporting of traffic characteristics corresponding to the type of the data set.
9. The method according to any of claims 1-5, wherein the obtaining the traffic characteristics of the data set and reporting the traffic characteristics of the data set to the network device comprises at least one of:
Under the condition of establishing or modifying a first QoS flow, acquiring and reporting the packet loss characteristic of a data set borne by the first QoS flow to the network equipment;
Under the condition of establishing or modifying a first Qos-flow, acquiring and reporting the packet loss characteristic of a data set carried by the first Qos-flow to the network equipment;
Under the condition of adding or modifying a first DRB, acquiring and reporting the packet loss characteristic of a data set borne by the first DRB to the network equipment;
Under the condition of establishing or modifying a first logic channel, acquiring and reporting the packet loss characteristic of a data set borne by the first logic channel to the network equipment;
when the packet loss characteristics of the data set change, acquiring and reporting the packet loss characteristics of the data set after the change to the network equipment;
When the time interval from the last report of the packet loss characteristic of the data set is greater than a set threshold value, acquiring and reporting the packet loss characteristic of the data set to the network equipment;
And if the data set has the packet loss characteristic, acquiring and reporting the packet loss characteristic of the data set to the network equipment.
10. The method according to any of claims 1-5, wherein the obtaining the traffic characteristics of the data set and reporting the traffic characteristics of the data set to the network device comprises at least one of:
Under the condition of establishing or modifying a first QoS flow, acquiring and reporting whether a data set carried by the first QoS flow supports the out-of-order delivery or not to the network equipment;
Under the condition of establishing or modifying a first Qos-flow, acquiring and reporting whether a data set carried by the first Qos-flow supports out-of-order delivery or not to the network equipment;
Under the condition of adding or modifying a first DRB, acquiring and reporting whether a data set borne by the first DRB supports out-of-order delivery or not to the network equipment;
under the condition of establishing or modifying a first logic channel, acquiring and reporting whether a data set borne by the first logic channel supports the out-of-order delivery or not to the network equipment;
when the characteristic of whether the data set supports out-of-order delivery changes, acquiring and reporting the changed characteristic of whether the data set supports out-of-order delivery to the network equipment;
when the time interval from the last time of reporting whether the data set supports out-of-order delivery is larger than a set threshold value, acquiring and reporting whether the data set supports out-of-order delivery to the network equipment;
and if the data set has the characteristic of whether the out-of-order delivery is supported, acquiring and reporting the characteristic of whether the out-of-order delivery is supported to the network equipment.
11. The method of any of claims 1-9, wherein the type of packet loss characteristics comprises one or more of:
first packet loss characteristic type: in the data set, if any one or a section of data is lost, the rest data in the data set are discarded;
The second packet loss characteristic type: in a data set, if a certain proportion of data is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain proportion of data is correctly transmitted, the rest one or more sections of data in the data set are lost, and the data set is still available to the receiving end;
Third packet loss characteristic type: in a data set, if a certain proportion of data sequenced in front is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain proportion of the data sequenced in the front is correctly transmitted, the rest one or more sections of data in the data set are lost, and the data set is still available to the receiving end;
Fourth packet loss characteristic type: in a data set, if a certain amount of data is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain amount of data is correctly transmitted, one or more pieces of data in the rest of the data set are lost, and the data set is still available to the receiving end;
Fifth packet loss characteristic type: in the data set, if at least two data which are sequenced in the front and are continuous in all data are correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available for a receiving end; wherein the number of the at least two data is associated with a total number of data in the data set; or in the data set, if at least two segments of data which are sequenced in the front and continuous in all the data are correctly transmitted, one or more segments of the rest segments of data in the data set are lost, and the data set is still available for a receiving end; wherein the number of the at least two pieces of data is associated with a total number of pieces of data in the data set;
Sixth packet loss characteristic type: in the data set, if at least one data which is sequenced in the front and continuous is transmitted correctly, the rest one or more data in the data set are lost, and the data set is still available to the receiving end; or in the data set, if at least one segment of data which is sequenced in the front and continuous is transmitted correctly, the rest segment or segments of data in the data set are lost, and the data set is still available to the receiving end.
12. The method according to any of claims 1-11, wherein the set of data is a set of PDUs.
13. The service characteristic reporting method is characterized by comprising the following steps:
and receiving service characteristics of the data set reported by the terminal, wherein the service characteristics comprise packet loss characteristics and/or characteristics of supporting out-of-order delivery.
14. The method of claim 13, wherein prior to the service characteristics of the data set reported by the receiving terminal, further comprising:
and sending configuration information to the terminal, wherein the configuration information is used for indicating whether the packet loss characteristic of the data set is required or allowed to be reported by the terminal, and/or the configuration information is used for indicating whether the packet loss characteristic of the data set is required or allowed to be reported by the terminal, and whether the out-of-order delivery characteristic is supported or not.
15. The method of claim 14, wherein the configuration information includes indication information of a type of packet loss characteristics, the indication information being used to indicate the terminal to report the corresponding type of packet loss characteristics.
16. The method according to any one of claims 13-15, wherein before the receiving the service characteristics of the data set reported by the terminal, further comprises:
and sending a request for reporting the service characteristics to the terminal.
17. The method of claim 16, wherein the request to report traffic characteristics is for requesting reporting traffic characteristics of a data set carried by one or more of a first QoS flow, a first QoS sub-flow, a first DRB, a first logical channel.
18. The method according to any of claims 16-17, wherein the request for reporting a traffic characteristic is for requesting reporting a traffic characteristic corresponding to a type of the data set.
19. The method of any of claims 13-18, wherein the type of packet loss characteristics comprises one or more of:
first packet loss characteristic type: in the data set, if any one or a section of data is lost, the rest data in the data set are discarded;
The second packet loss characteristic type: in a data set, if a certain proportion of data is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain proportion of data is correctly transmitted, the rest one or more sections of data in the data set are lost, and the data set is still available to the receiving end;
Third packet loss characteristic type: in a data set, if a certain proportion of data sequenced in front is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain proportion of the data sequenced in the front is correctly transmitted, the rest one or more sections of data in the data set are lost, and the data set is still available to the receiving end;
Fourth packet loss characteristic type: in a data set, if a certain amount of data is correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available to a receiving end; or in the data set, if a certain amount of data is correctly transmitted, one or more pieces of data in the rest of the data set are lost, and the data set is still available to the receiving end;
Fifth packet loss characteristic type: in the data set, if at least two data which are sequenced in the front and are continuous in all data are correctly transmitted, the rest one or more data in the data set are lost, and the data set is still available for a receiving end; wherein the number of the at least two data is associated with a total number of data in the data set; or in the data set, if at least two segments of data which are sequenced in the front and continuous in all the data are correctly transmitted, one or more segments of the rest segments of data in the data set are lost, and the data set is still available for a receiving end; wherein the number of the at least two pieces of data is associated with a total number of pieces of data in the data set;
Sixth packet loss characteristic type: in the data set, if at least one data which is sequenced in the front and continuous is transmitted correctly, the rest one or more data in the data set are lost, and the data set is still available to the receiving end; or in the data set, if at least one segment of data which is sequenced in the front and continuous is transmitted correctly, the rest segment or segments of data in the data set are lost, and the data set is still available to the receiving end.
20. The method according to any one of claims 13-19, wherein after receiving the service characteristics of the data set reported by the terminal, further comprises:
And carrying out resource allocation and/or scheduling on data transmission of the data set according to the service characteristics of the data set.
21. The method according to any of claims 13-20, wherein the set of data is a set of PDUs.
22. A terminal, characterized by comprising a processing unit and a receiving and transmitting unit;
the processing unit is used for acquiring service characteristics of a data set of the packet data unit, wherein the service characteristics comprise packet loss characteristics and/or characteristics of whether disorder delivery is supported;
And the receiving and transmitting unit is used for reporting the service characteristics corresponding to the data set to network equipment.
23. A network device, comprising a processing unit and a transceiver unit;
The processing unit is used for configuring a terminal to report service characteristics of a data set of a packet data unit, wherein the service characteristics comprise packet loss characteristics and/or characteristics of supporting disorder delivery;
The receiving and transmitting unit is used for receiving the service characteristics of the data set reported by the terminal.
24. A communication device, comprising: a processor, a memory, and a transceiver;
The transceiver is used for receiving and transmitting data under the control of the processor;
the memory stores computer instructions;
the processor configured to read the computer instructions and perform the method of any one of claims 1-12.
25. A communication device, comprising: a processor, a memory, and a transceiver;
The transceiver is used for receiving and transmitting data under the control of the processor;
the memory stores computer instructions;
The processor configured to read the computer instructions and perform the method of any of claims 13-21.
26. A computer readable storage medium storing computer executable instructions for causing the computer to perform the method of any one of claims 1-12 or to perform the method of any one of claims 13-21.
27. A computer program product, characterized in that the computer program product, when called by a computer, causes the computer to perform the method according to any of claims 1-12 or to perform the method according to any of claims 13-21.
CN202211380076.2A 2022-11-04 2022-11-04 Service characteristic reporting method, device and storage medium Pending CN117998469A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211380076.2A CN117998469A (en) 2022-11-04 2022-11-04 Service characteristic reporting method, device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211380076.2A CN117998469A (en) 2022-11-04 2022-11-04 Service characteristic reporting method, device and storage medium

Publications (1)

Publication Number Publication Date
CN117998469A true CN117998469A (en) 2024-05-07

Family

ID=90897992

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211380076.2A Pending CN117998469A (en) 2022-11-04 2022-11-04 Service characteristic reporting method, device and storage medium

Country Status (1)

Country Link
CN (1) CN117998469A (en)

Similar Documents

Publication Publication Date Title
US10939127B2 (en) Method and apparatus for transmission of substreams of video data of different importance using different bearers
TW201415893A (en) Frame prioritization based on prediction information
WO2014046610A1 (en) A circuit arrangement and method of determining a priority of packet scheduling
CN113766567A (en) Communication method and device
CN106330713B (en) Message transmission method and device
US20110067072A1 (en) Method and apparatus for performing MPEG video streaming over bandwidth constrained networks
WO2022052102A1 (en) Communication method and apparatus
WO2021252178A1 (en) Video throughput improvement using long term referencing, deep learning, and load balancing
CN117998469A (en) Service characteristic reporting method, device and storage medium
WO2022151492A1 (en) Scheduling transmission method and apparatus
WO2023155633A1 (en) Data transmission method and apparatus
Baik et al. Efficient MAC for real-time video streaming over wireless LAN
WO2024060991A1 (en) Data stream guide method and apparatus for multiple paths
CN114928554A (en) Video transmission method, device and storage medium
WO2023108413A1 (en) Method and apparatus of reporting buffer status
CN116938904A (en) Information transmission method, device, related equipment and storage medium
WO2022126437A1 (en) Communication method and apparatus
WO2015074253A1 (en) Video service scheduling method and apparatus
CN117063463A (en) Data transmission method, related equipment and communication system
WO2024028380A1 (en) Adaptive quality of service
WO2023078537A1 (en) Method, apparatus and computer program
CN115484506A (en) Video streaming transmission method and related communication device
CN116866983A (en) Media unit transmission method and device
WO2023143729A1 (en) Device and method for correlated qos treatment cross multiple flows
CN117858154A (en) Data processing method, device, communication equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination