WO2022148371A1 - 传输报文的方法和装置 - Google Patents

传输报文的方法和装置 Download PDF

Info

Publication number
WO2022148371A1
WO2022148371A1 PCT/CN2022/070294 CN2022070294W WO2022148371A1 WO 2022148371 A1 WO2022148371 A1 WO 2022148371A1 CN 2022070294 W CN2022070294 W CN 2022070294W WO 2022148371 A1 WO2022148371 A1 WO 2022148371A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos
packet
information
connection
source
Prior art date
Application number
PCT/CN2022/070294
Other languages
English (en)
French (fr)
Inventor
周艳
林霖
叶进洲
周汉
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022148371A1 publication Critical patent/WO2022148371A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • the present application relates to the field of communications, and, more particularly, to methods and apparatuses for transmitting messages.
  • IP Internet protocol
  • QoS quality of service
  • QoS flow is the fifth generation (5th generation, 5G) core network and wireless interface.
  • 3GPP 3rd Generation partnership project
  • 5G fifth generation
  • wireless interface The minimum QoS control granularity for network access.
  • Each QoS flow has a corresponding QoS configuration.
  • the parameters in the QoS configuration describe the specific QoS requirements.
  • the forwarding node in the transmission network forwards the packet, it matches the packet to the preset QoS policy corresponding to the QoS flow according to the network layer characteristics of the packet. , and carry out differentiated guarantee processing mode according to QoS policy. Under the existing QoS mechanism, the transmission network cannot guarantee and optimize QoS more accurately.
  • the present application provides a method for transmitting packets.
  • the transmission network can provide QoS guarantee for the packets, thereby improving the QoS guarantee and optimization of the transmission network. accuracy.
  • a method for transmitting a message is provided, and the method for transmitting a message can be executed by a message generating device, or can also be executed by a chip or circuit provided in the message generating device. Not limited.
  • the method of transmitting the message includes:
  • each packet in the multiple packets includes source QoS information, and the source QoS information included in each packet is used for the The corresponding QoS packets are QoS guaranteed, and the source QoS information included in the multiple packets is different; the multiple packets are sent.
  • the method of transmitting the message includes:
  • the multiple packets have the same quintuple information, the multiple packets have different source QoS information, and the source QoS information is used to perform QoS guarantee on the corresponding packets; sending the multiple packets.
  • the packet generated by the packet generating device includes source QoS information for providing QoS guarantee for the packet, and different packets with the same quintuple information may include different
  • the source QoS information of the packet enables the transmission network of the packet to provide QoS guarantee for the packet, thereby improving the accuracy of QoS guarantee and optimization of the transmission network.
  • multiple packets with the same quintuple information are referred to as packets in one connection.
  • the multiple packets belong to the same connection, and the source QoS information included in the multiple packets is different, including: the first packet in the connection includes: The first source QoS information of the connection is different from the second source QoS information included in the second packet in the connection, wherein the first packet and the second packet are any two of the multiple packets. arts.
  • the multiple packets are generated, the multiple packets have the same quintuple information, the multiple packets have different source QoS information, and the source QoS information is used to perform QoS guarantee on the corresponding packets, including: Generating a first packet and a second packet, the quintuple information of the first packet is the same as the quintuple information of the second packet, the first source QoS information included in the first packet and the second packet.
  • the second source QoS information included in the packet is different, the first source QoS information is used for performing QoS guarantee on the first packet, and the second source QoS information is used for performing QoS guarantee on the second packet.
  • the multiple packets belong to the same connection.
  • the source QoS information included in different packets in the connection is different may be that the QoS information respectively included in any two packets in the connection are different.
  • the first source QoS information includes a first QoS feature and a first data feature
  • the first QoS feature is used to indicate the QoS requirement of the first packet
  • the The first data characteristic represents the transmission characteristic of the first packet
  • the second source QoS information includes a second QoS characteristic and a second data characteristic
  • the second QoS characteristic is used to indicate the QoS requirement of the second packet
  • the second The data characteristic represents the transmission characteristic of the second packet.
  • the source QoS information included in a certain packet may also include QoS characteristics and data characteristics.
  • the application can clearly and detailedly indicate the application layer data characteristics and QoS requirements to the transmission network, and further improve the transmission network for QoS guarantee and optimization. accuracy.
  • the source QoS information included in the multiple packets is different includes: the data features included in the multiple packets are different, and/or, the multiple packets
  • the QoS features included are different.
  • the difference between the first source QoS information included in the first packet in the connection and the second source QoS information included in the second packet in the connection includes: the first data feature and the second data feature are different , and/or, the first QoS feature and the second QoS feature are different.
  • the difference in the source QoS information respectively included in the two packets in the connection may be the data features included in the source QoS information, and/or the different QoS features included in the source QoS information, which increases the flexibility of the solution.
  • the first data feature includes a connection-level data feature and/or a packet-level data feature, wherein the connection-level data feature is used to indicate that the connection Transmission characteristics of the included multiple packets, the packet-level data characteristics represent the transmission characteristics of the first packet, and the QoS characteristics include connection-level QoS characteristics and/or packet-level QoS characteristics, wherein the connection-level QoS characteristics
  • the QoS feature is used to indicate the QoS requirements of the multiple packets included in the connection
  • the packet-level QoS feature is used to indicate the QoS requirements of the first packet.
  • the data feature in the source QoS information included in a packet may be a connection-level data feature indicating the transmission feature of the connection containing the message, or a packet-level data feature indicating the message's transmission feature ;
  • the QoS feature may be a connection-level QoS feature indicating the QoS requirement of the connection containing the message, or a packet-level QoS feature indicating the QoS requirement of the message.
  • Different possible granularities of source QoS information are provided, thereby increasing the flexibility of the scheme.
  • the data characteristics at the connection level include one or more of the following: average rate, duration, frequency, size, delay budget, peak frequency, peak size, Peak delay budget, peak transmission time, type of emergency, estimated time of occurrence of emergency, estimated amount of emergency packets, and estimated delay of emergency packets, where the average rate indicates the packets in the connection
  • the average sending rate indicates the duration of the connection
  • the frequency indicates the frequency of packet sending
  • the size indicates the average value of the packets sent each frequency
  • the delay budget indicates the time-consuming budget for all packets to be delivered to the receiver in a cycle
  • the peak frequency indicates the peak generation frequency of the message
  • the peak delay budget indicates the time-consuming budget for all the message peaks to be delivered to the receiving end
  • the peak sending time indicates the time when the message peak is sent
  • the emergency event type indicates sudden
  • the estimated time of occurrence of the emergency indicates the expected arrival time of the emergency message
  • the estimated amount of the emergency message indicates the amount of the message
  • the packet-level data characteristics include one or more of the following: data block sequence number, data block size, packet location, and data block delay budget, wherein the The data block sequence number indicates the data block number to which the first message belongs, the data block size indicates the size of the data block to which the first message belongs, the packet position indicates the location of the first message in the data block to which it belongs, and the data block delay budget Indicates the time-consuming budget for transmitting the first packet to the receiving end.
  • the data features included in the above source QoS information can be implemented in different ways for different packets, thereby increasing the flexibility of the solution.
  • the QoS characteristics of the connection level include connection QoS characteristics indicator (connection QoS characteristics indicator, CQI) and/or connection QoS characteristic information
  • the QoS characteristics of the packet level include Packet QoS indicators (packet QoS characteristics indicator, PQI) and/or packet QoS characteristics information.
  • the QoS features at the connection level and the QoS features at the packet level can have different forms to increase the flexibility of the solution.
  • the QoS characteristics represented by the connection-level QoS characteristics or the packet-level QoS characteristics include one or more of the following: resource type, priority, delay budget and Error rate.
  • the QoS features included in the above source QoS information may be implemented in different ways for different packets, thereby increasing the flexibility of the solution.
  • the first source QoS information included in the first packet includes: the first packet includes connection-level information and packet-level information; or, The first packet includes information at the packet level, and the dummy Internet protocol (dummy IP) packet includes information at the connection level; or, the first packet includes information at the packet level, the connection Level information is transmitted through the control plane, wherein the connection level information includes the connection level data characteristics and the connection level QoS characteristics, the packet level information includes the packet level access data characteristics and the packet level QoS characteristics .
  • dummy IP dummy Internet protocol
  • the source QoS information carried in the message may be implemented in different ways, thereby improving the flexibility of the solution.
  • the first source QoS information is used to indicate that the first packet is mapped to the first quality of service flow QoS flow
  • the second source QoS information is used to indicate The second message is mapped to a second QoS flow, and the first QoS flow and the second QoS flow belong to one QoS flow group.
  • the first source QoS information is used to indicate that the first packet is mapped to a quality of service identifier (5G quality of service identifier, 5QI) of the first 5G network ), the second source QoS information is used to indicate that the second packet is mapped to the second 5QI, and the first 5QI and the second 5QI belong to one QoS flow.
  • 5G quality of service identifier 5QI
  • 5QI quality of service identifier
  • the method for transmitting packets also provides a QoS flow model, where different QoS flows mapped to different packets included in a certain connection belong to the same QoS flow group, or a certain connection includes different QoS flows.
  • the different 5QIs mapped by the packets belong to a QoS flow, which can improve the management and control of the connection.
  • the first source QoS information is used to indicate that the first packet is mapped to the first quality of service flow QoS flow
  • the QoS configuration of the first QoS flow includes: the maximum Guaranteed bandwidth (maximum guaranteed flow bit rate, MGFBR); the MGFBR is used to adjust the resources reserved for the first QoS flow, and the guaranteed bandwidth of the first QoS flow is less than or equal to the MGFBR, where the first packet is In any one of the multiple packets, the first source QoS information is the source QoS information included in the first packet. or,
  • the QoS configuration of the first QoS flow further includes: a minimum guaranteed bandwidth (guaranteed flow bit rate, GFBR), and the GFBR is used to adjust to the first QoS flow
  • GFBR minimum guaranteed bandwidth
  • the guaranteed bandwidth of the first QoS flow is greater than or equal to the GFBR and less than or equal to the MGFBR.
  • the method for transmitting a message provided by the embodiment of the present application can fine-tune the resources reserved for the QoS flow by adding the parameter MGFBR in the QoS configuration of the QoS flow.
  • the first source QoS information is used to indicate that the first packet is mapped to the first quality of service flow QoS flow
  • the QoS configuration of the first QoS flow includes: Indication information, the indication information is used to indicate whether to reserve the resource corresponding to the first QoS flow, wherein the first packet is any one of the multiple packets, and the first source QoS information is the first packet Source QoS information included in the text.
  • the method for transmitting packets provided by the embodiments of the present application can indicate whether to reserve resources corresponding to the QoS flow by adding indication information in the QoS configuration of the QoS flow, so as to avoid the decision of changing the QoS policy and the length of the execution chain in the current macro control mode. , the disadvantage of changing time-consuming.
  • the first source QoS information is used to indicate that the first packet is mapped to the first quality of service flow QoS flow includes: the first source QoS information includes: QoS feature, the QoS feature corresponds to the QoS feature indicated by the 5QI in the first QoS flow.
  • the compatibility of the scheme can be improved by mapping with 5QI to be compatible with the current QoS mechanism.
  • the method further includes: determining a state of a transmission node in a path for transmitting the first packet; when the state of at least one of the transmission nodes satisfies a preset condition, Start the active safeguard mechanism.
  • starting the active guarantee mechanism when the state of at least one of the input nodes satisfies a preset condition, starting the active guarantee mechanism includes one or more of the following: when the at least one of the input nodes exists When the packet is lost, the first packet is sent repeatedly; or when the packet loss rate of the at least one of the input nodes is greater than the preset value, the forward error correction (forward error correction, FEC) redundancy coding method is used to encode the first message.
  • FEC forward error correction
  • the method for transmitting packets provided by the embodiments of the present application also provides an active guarantee mechanism.
  • a preset condition for example, there is periodic and occasional packet loss due to interference, and the packet loss rate cannot be satisfied
  • End-to-end packet error rate target activate the active guarantee mechanism to improve the performance of packet transmission.
  • the transmission node in the packet transmission network may identify some data features and map them as Source QoS information, and transmit the source QoS information to other transmission nodes.
  • a method for transmitting a message is provided, and the method for transmitting a message can be performed by a message receiving device, or can also be performed by a chip or circuit provided in the message receiving device. Not limited.
  • the method of transmitting the message includes:
  • each packet in the multiple packets includes source QoS information, and the source QoS information included in each packet is used for the
  • the corresponding QoS packets are QoS guaranteed, and the source QoS information included in the multiple packets is different; the multiple packets are processed based on the source QoS information included in the multiple packets.
  • the method of transmitting the message includes:
  • Receive multiple packets the multiple packets have the same quintuple information, the multiple packets have different source QoS information, and the source QoS information is used to perform QoS guarantee on the corresponding packets; based on The source QoS information included in the multiple packets processes the multiple packets.
  • the packet received by the packet receiving device includes source QoS information for providing QoS guarantee for the packet, and different packets in the connection may include different source QoS information information, so that the transmission network of the packet can provide QoS guarantee for the packet, thereby improving the accuracy of QoS guarantee and optimization of the transmission network.
  • the multiple packets belong to the same connection, and the source QoS information included in the multiple packets is not the same, including: the first packet in the connection includes: The first source QoS information of the connection is different from the second source QoS information included in the second packet in the connection, wherein the first packet and the second packet are any two of the multiple packets. arts.
  • receiving multiple packets the multiple packets have the same quintuple information, the multiple packets have different source QoS information, and the source QoS information is used to perform QoS on the corresponding packets. Guaranteeing this includes: receiving a first packet and a second packet, the quintuple information of the first packet is the same as the quintuple information of the second packet, and the first source QoS information included in the first packet Different from the second source QoS information included in the second packet, the first source QoS information is used to perform QoS guarantee on the first packet, and the second source QoS information is used to perform QoS guarantee on the second packet.
  • the multiple packets belong to the same connection.
  • different source QoS information included in different packets in the connection may be different in the QoS information respectively included in any two packets in the connection.
  • the first source QoS information includes a first data characteristic and a first QoS characteristic
  • the second source QoS information includes a second QoS characteristic and a second data characteristic
  • the second data characteristic represents the transmission characteristic of the second packet
  • the method further includes: determining the QoS requirement of the first packet according to the first QoS characteristic; determining the QoS requirement of the second packet according to the second QoS characteristic ;
  • Processing the multiple packets based on the source QoS information included in the multiple packets includes: scheduling the resources of the first packet according to the QoS requirements of the first packet and the first data feature; according to the second packet The QoS requirement and the second data feature schedule the resources of the second packet.
  • a device that receives a message can perform resource scheduling according to the QoS feature and data feature included in the source QoS information.
  • the source QoS information included in the multiple packets is different includes: the QoS features included in the multiple packets are different, and/or, the multiple packets
  • the included data characteristics vary.
  • the difference between the first source QoS information included in the first packet in the connection and the second source QoS information included in the second packet in the connection includes: the first data feature and the second data feature are different , and/or, the first QoS feature and the second QoS feature are different.
  • the difference in the source QoS information respectively included in the two packets in the connection may be the data features included in the source QoS information, and/or the different QoS features included in the source QoS information, which increases the flexibility of the solution.
  • scheduling the resources of the message according to the QoS requirement and the data feature includes: scheduling different resources for different messages according to different QoS features.
  • the resource for scheduling the first message is different from the resource for scheduling the second message.
  • the method for transmitting a message provided by the embodiment of the present application
  • the device that receives the message can schedule different resources for different messages in the connection, thereby improving the accuracy of scheduling.
  • the first data feature includes a connection-level data feature and/or a packet-level data feature
  • the method further includes: determining the data feature according to the connection-level data feature. transmission characteristics of multiple packets included in the connection; determine the transmission characteristics of the first packet according to the data characteristics of the packet level;
  • the first QoS feature includes a connection-level QoS feature and/or a packet-level QoS feature
  • the method further includes: determining the connection-level QoS feature according to the connection-level QoS feature.
  • QoS requirements of other packets in the connection the other packets may be packets that do not include packet-level QoS characteristics; for example, determine the QoS requirements of the third packet in the connection according to the QoS characteristics of the connection level, the third packet
  • the message includes third source QoS information, and the third QoS feature included in the third source QoS information may not include packet-level QoS features.
  • the QoS requirement of the first packet is determined according to the QoS feature of the packet level.
  • the data feature in the source QoS information included in the message may be a connection-level data feature indicating the transmission feature of the connection containing the message, or a packet-level data feature indicating the message’s transmission feature; the same
  • the QoS feature may be a connection-level QoS feature indicating the QoS requirement of the connection containing the packet, or a packet-level QoS feature indicating the QoS requirement of the packet.
  • Different possible granularities of source QoS information are provided, thereby increasing the flexibility of the scheme.
  • the data characteristics at the connection level include one or more of the following: average rate, duration, frequency, size, delay budget, peak frequency, peak size, Peak delay budget, peak transmission time, type of emergency, estimated time of occurrence of emergency, estimated amount of emergency packets, and estimated delay of emergency packets, where the average rate indicates the packets in the connection
  • the average sending rate indicates the duration of the connection
  • the frequency indicates the frequency of packet sending
  • the size indicates the average value of the packets sent each frequency
  • the delay budget indicates the time-consuming budget for all packets to be delivered to the receiver in a cycle
  • the peak frequency indicates the peak generation frequency of the message
  • the peak delay budget indicates the time-consuming budget for all the message peaks to be delivered to the receiving end
  • the peak sending time indicates the time when the message peak is sent
  • the emergency event type indicates sudden
  • the category of the occurrence time indicates the estimated time of occurrence of the emergency indicates the expected arrival time of the emergency message
  • the estimated amount of the emergency message indicates the amount of the message
  • the packet-level data features include one or more of the following: a data block sequence number, a data block size, a packet location, and a data block delay budget, wherein the The data block sequence number indicates the data block number to which the first message belongs, the data block size indicates the size of the data block to which the first message belongs, the packet position indicates the location of the first message in the data block to which it belongs, and the data block delay budget Indicates the time-consuming budget for transmitting the first packet to the receiving end.
  • the data features included in the above source QoS information can be implemented in different ways for different packets, thereby increasing the flexibility of the solution.
  • connection-level QoS characteristics include connection QoS characteristic indication CQI and/or connection QoS characteristic information
  • packet-level QoS characteristics include packet QoS indication PQI and/or Packet QoS feature information.
  • the QoS features at the connection level and the QoS features at the packet level can have different forms to increase the flexibility of the solution.
  • the method further includes: receiving a packet filtering rule from a core network device, where the packet filtering rule includes the CQI and/or the PQI; according to the CQI and/or the PQI; Or the PQI maps the first packet to the first quality of service flow QoS flow.
  • the core network device can send the enhanced packet filtering rules to the packet receiving device (for example, the user plane network element), so that the subsequent QoS flow mapping can be performed based on the packet filtering rules.
  • QoS features are performed.
  • the "enhanced packet filtering rule” involved in this application refers to a packet filtering rule with more configuration parameters than the current packet filtering rule.
  • the method further includes: receiving a reflective QoS flow to DRB mapping indication (RDI) and the PQI; recording the PQI according to the RDI, and the PQI using In order to indicate that the fourth message is mapped to the third QoS flow; wherein, the fourth message is the message to be sent, and the QoS feature indicated by the 5QI in the third QoS flow corresponds to the PQI.
  • RDI reflective QoS flow to DRB mapping indication
  • the method for transmitting a packet provided by the embodiment of the present application also provides a reflection enhancement method, so that the QoS flow mapping based on the reflection QoS scheme is more accurate.
  • the QoS characteristics represented by the connection-level QoS characteristics or the packet-level QoS characteristics include one or more of the following: resource type, priority, delay budget and Error rate.
  • the QoS features included in the above source QoS information may be implemented in different ways for different packets, thereby increasing the flexibility of the solution.
  • the first source QoS information included in the first packet includes: the first packet includes connection-level information and packet-level information; or, the The first packet includes the information of the packet level, and the virtual Internet protocol dummy IP packet includes the information of the connection level; or, the first packet includes the information of the packet level, and the information of the connection level is transmitted through the control plane , wherein the information of the connection level includes data characteristics of the connection level and the QoS characteristics of the connection level, and the information of the packet level includes the connection data characteristics of the packet level and the QoS characteristics of the packet level.
  • the source QoS information carried in the message may be implemented in different ways, thereby improving the flexibility of the solution.
  • the method further includes: mapping the first packet to a first quality of service flow QoS flow according to the first source QoS information; according to the second source QoS The information maps the second message to the second QoS flow; wherein, the first QoS flow and the second QoS flow belong to a QoS flow group.
  • the method further includes: mapping the first packet to a quality of service identifier 5QI of the first 5G network according to the first source QoS information; mapping the second packet to a second packet according to the second source QoS information 5QI; wherein, the first 5QI and the second 5QI belong to one QoS flow.
  • the method for transmitting packets also provides a QoS flow model, where different QoS flows mapped to different packets included in a connection belong to the same QoS flow group, or a certain connection includes different QoS flows.
  • the different 5QIs mapped by the packets belong to a QoS flow, which can improve the management and control of the connection.
  • mapping the first packet to the first QoS flow according to the first source QoS information includes: according to the first QoS information included in the first source QoS information The feature determines the first QoS flow from a plurality of QoS flows, wherein the first QoS feature included in the first source QoS information corresponds to the QoS feature indicated by the 5QI in the first QoS flow.
  • the compatibility of the scheme can be improved by mapping with 5QI to be compatible with the current QoS mechanism.
  • the method further includes: adjusting the resources reserved for the first QoS flow.
  • the QoS configuration of the first QoS flow includes: a maximum guaranteed bandwidth MGFBR; the adjusting the resources reserved for the first QoS flow includes: determining the first QoS flow The guaranteed bandwidth of the flow is less than or equal to the MGFBR.
  • the QoS configuration of the first QoS flow further includes: a minimum guaranteed bandwidth GFBR; the adjusting the resources reserved for the first QoS flow includes: determining the first QoS flow The guaranteed bandwidth of the QoS flow is greater than or equal to the GFBR and less than or equal to the MGFBR.
  • the method for transmitting a message provided by the embodiment of the present application can fine-tune the resources reserved for the QoS flow by adding the parameter MGFBR in the QoS configuration of the QoS flow.
  • the method further includes: determining whether to reserve resources corresponding to the first QoS flow.
  • the QoS configuration of the first QoS flow includes: indication information, the indication information is used to indicate whether to reserve resources corresponding to the first QoS flow; whether to determine whether Reserving the resource corresponding to the first QoS flow includes: determining whether to reserve the resource corresponding to the first QoS flow according to the indication information.
  • the method for transmitting packets provided by the embodiments of the present application can indicate whether to reserve resources corresponding to the QoS flow by adding indication information in the QoS configuration of the QoS flow, so as to avoid the decision of changing the QoS policy and the length of the execution chain in the current macro control mode. , the disadvantage of changing time-consuming.
  • the method further includes: the first source QoS information is received, or the first source QoS information is locally generated; when the first source QoS information is received When the QoS information is locally generated, the method further includes: filling the first packet with the first source QoS information.
  • generating the first source QoS information includes: determining the first source QoS information through traffic analysis and/or packet analysis.
  • the transmission node in the packet transmission network may identify some data features and map them to the source QoS information. The information is transmitted to other transmission nodes.
  • the method further includes: determining a state of a transmission node in a path for transmitting the first packet; when the state of at least one of the transmission nodes satisfies a preset condition, Start the active safeguard mechanism.
  • starting the active guarantee mechanism when the state of at least one of the input nodes satisfies a preset condition, starting the active guarantee mechanism includes one or more of the following: when the at least one of the input nodes exists When the packet is lost, the first packet is repeatedly sent; or when the packet loss rate of the at least one input node is greater than a preset value, the first packet is encoded by the forward error correction (FEC) redundancy encoding method.
  • FEC forward error correction
  • the method for transmitting packets provided by the embodiments of the present application also provides an active guarantee mechanism.
  • a preset condition for example, there is periodic and occasional packet loss due to interference, and the packet loss rate cannot be satisfied
  • End-to-end packet error rate target activate the active guarantee mechanism to improve the performance of packet transmission.
  • an apparatus for transmitting a message including:
  • a processing unit configured to generate multiple packets, the quintuple information of the multiple packets is the same, each packet in the multiple packets includes source QoS information, and the source QoS information included in each packet The information is used to ensure QoS for the corresponding packets, and the source QoS information included in the multiple packets is different;
  • a sending unit configured to send the multiple packets.
  • the device for transmitting messages includes:
  • a processing unit configured to generate multiple packets, the multiple packets have the same quintuple information, the multiple packets have different source QoS information, and the source QoS information is used for the corresponding packets QoS guarantee;
  • a sending unit configured to send the multiple packets.
  • the multiple packets belong to the same connection, and the source QoS information included in the multiple packets is not the same, including: the first packet in the connection includes: The first source QoS information of the connection is different from the second source QoS information included in the second packet in the connection, wherein the first packet and the second packet are any two of the multiple packets. arts.
  • the processing unit generates multiple packets, the multiple packets have the same quintuple information, the multiple packets have different source QoS information, and the source QoS information is used to report the corresponding information.
  • QoS guarantee including:
  • the processing unit generates a first packet and a second packet, the quintuple information of the first packet is the same as the quintuple information of the second packet, and the first source QoS information included in the first packet is the same as the quintuple information of the second packet.
  • the second source QoS information included in the second packet is different, the first source QoS information is used for performing QoS guarantee on the first packet, and the second source QoS information is used for performing QoS guarantee on the second packet.
  • the multiple packets belong to the same connection.
  • the first source QoS information includes a first QoS feature and a first data feature, and the first QoS feature is used to indicate the QoS requirement of the first packet,
  • the first data characteristic represents the transmission characteristic of the first packet
  • the second source QoS information includes a second QoS characteristic and a second data characteristic
  • the second QoS characteristic is used to indicate the QoS requirement of the second packet
  • the The second data characteristic represents the transmission characteristic of the second packet.
  • the first source QoS information included in the first packet in the connection and the second source QoS information included in the second packet in the connection are different Including: the first data feature and the second data feature are different, and/or the first QoS feature and the second QoS feature are different.
  • the first data feature includes a connection-level data feature and/or a packet-level data feature, wherein the connection-level data feature represents a data feature included in the connection Transmission characteristics of multiple packets, the packet-level data characteristics represent transmission characteristics of the first packet, and the first QoS characteristics include connection-level QoS characteristics and/or packet-level QoS characteristics, wherein the connection-level QoS characteristics
  • the QoS feature is used to indicate the QoS requirements of the multiple packets included in the connection
  • the packet-level QoS feature is used to indicate the QoS requirements of the first packet.
  • the data characteristics at the connection level include one or more of the following: average rate, duration, frequency, size, delay budget, peak frequency, peak size, Peak delay budget, peak transmission time, type of emergency, estimated time of occurrence of emergency, estimated amount of emergency packets, and estimated delay of emergency packets, where the average rate indicates the packets in the connection
  • the average sending rate indicates the duration of the connection
  • the frequency indicates the frequency of packet sending
  • the size indicates the average value of the packets sent each frequency
  • the delay budget indicates the time-consuming budget for all packets to be delivered to the receiver in a cycle
  • the peak frequency indicates the peak generation frequency of the message
  • the peak delay budget indicates the time-consuming budget for all the message peaks to be delivered to the receiving end
  • the peak sending time indicates the time when the message peak is sent
  • the emergency event type indicates sudden
  • the estimated time of occurrence of the emergency indicates the expected arrival time of the emergency message
  • the estimated amount of the emergency message indicates the amount of the message
  • the packet-level data features include one or more of the following: data block sequence number, data block size, packet location, and data block delay budget, wherein the The data block sequence number indicates the data block number to which the first message belongs, the data block size indicates the size of the data block to which the first message belongs, the packet position indicates the location of the first message in the data block to which it belongs, and the data block delay budget Indicates the time-consuming budget for transmitting the first packet to the receiving end.
  • connection-level QoS characteristic includes connection QoS characteristic indication CQI and/or connection QoS characteristic information
  • packet-level QoS characteristic includes packet QoS indication PQI and/or Packet QoS feature information.
  • the QoS features represented by the connection-level QoS feature information or the packet-level QoS feature information include one or more of the following: resource type, priority, delay Budget and error rate.
  • the first source QoS information included in the first packet includes: the first packet includes connection-level information and packet-level information; or, the The first packet includes the information of the packet level, and the virtual Internet protocol dummy IP packet includes the information of the connection level; or, the first packet includes the information of the packet level, and the information of the connection level is transmitted through the control plane , wherein the information of the connection level includes data characteristics of the connection level and the QoS characteristics of the connection level, and the information of the packet level includes the connection data characteristics of the packet level and the QoS characteristics of the packet level.
  • the first source QoS information is used to indicate that the first packet is mapped to the first quality of service flow QoS flow
  • the second source QoS information is used to indicate The second message is mapped to a second QoS flow, and the first QoS flow and the second QoS flow belong to one QoS flow group.
  • the first source QoS information is used to indicate that the first packet is mapped to the service quality identifier 5QI of the first 5G network
  • the second source QoS information It is used to indicate that the second packet is mapped to the second 5QI, and the first 5QI and the second 5QI belong to one QoS flow.
  • the first source QoS information is used to indicate that the first packet is mapped to the first quality of service flow QoS flow
  • the QoS configuration of the first QoS flow includes: : maximum guaranteed bandwidth MGFBR; the MGFBR is used to adjust the resources reserved for the first QoS flow, and the guaranteed bandwidth of the first QoS flow is less than or equal to the MGFBR.
  • the QoS configuration of the first QoS flow further includes: a minimum guaranteed bandwidth GFBR, the GFBR is used to adjust the resources reserved for the first QoS flow, the first QoS flow
  • the guaranteed bandwidth of a QoS flow is greater than or equal to the GFBR and less than or equal to the MGFBR.
  • the first source QoS information is used to indicate that the first packet is mapped to the first quality of service flow QoS flow
  • the QoS configuration of the first QoS flow includes: : indication information, the indication information is used to indicate whether to reserve the resource corresponding to the first QoS flow.
  • the first source QoS information is used to indicate that the first packet is mapped to the first QoS flow, including: the first source QoS information includes QoS features, The QoS feature corresponds to the QoS feature indicated by the 5QI in the QoS flow.
  • the processing unit is further configured to determine the state of the transmission node in the path for transmitting the first packet; when the state of at least one of the transmission nodes satisfies a preset condition , the processing unit is also used to start the active safeguard mechanism.
  • the processing unit when the state of at least one of the input nodes satisfies a preset condition, the processing unit is further configured to start an active guarantee mechanism including one or more of the following: when the state of the output node satisfies a preset condition When at least one of the input nodes has packet loss, the processing unit is further configured to determine to send the first packet repeatedly; or when the packet loss rate of the at least one of the input nodes is greater than a preset value, the processing unit is further configured to determine to use The first message is encoded in a forward error correction (FEC) redundancy encoding manner.
  • FEC forward error correction
  • a device for transmitting a message includes:
  • a receiving unit configured to receive multiple packets, the quintuple information of the multiple packets is the same, each packet in the multiple packets includes source QoS information, and the source QoS information included in each packet The information is used to perform QoS guarantee on the corresponding QoS packets, and the source QoS information included in the multiple packets is different; the processing unit is configured to process the multiple packets based on the source QoS information included in the multiple packets .
  • the device for transmitting messages includes:
  • a receiving unit configured to receive multiple packets, the multiple packets have the same quintuple information, the multiple packets have different source QoS information, and the source QoS information is used for the corresponding packets performing QoS assurance; and a processing unit, configured to process the multiple packets based on the source QoS information included in the multiple packets.
  • the multiple packets belong to the same connection, and the source QoS information included in the multiple packets is not the same, including: the first packet in the connection includes: The first source QoS information of the connection is different from the second source QoS information included in the second packet in the connection, wherein the first packet and the second packet are any two of the multiple packets. arts.
  • the receiving unit receives multiple packets, the multiple packets have the same quintuple information, the multiple packets have different source QoS information, and the source QoS information is used to correspond to them.
  • the QoS guarantee of the packet includes: the receiving unit receives a first packet and a second packet, the quintuple information of the first packet is the same as the quintuple information of the second packet, and the first packet
  • the included first source QoS information is different from the second source QoS information included in the second packet, the first source QoS information is used to perform QoS guarantee on the first packet, and the second source QoS information is used to Two packets are guaranteed for QoS.
  • the multiple packets belong to the same connection.
  • the first source QoS information includes a first QoS feature and a first data feature
  • the first data feature represents the transmission feature of the first packet
  • the first The two-source QoS information includes a second QoS feature and a second data feature, where the second data feature represents the transmission feature of the second packet
  • the processing unit is further configured to: determine the first packet according to the first QoS feature QoS requirement; determining the QoS requirement of the second packet according to the second QoS feature
  • the processing unit processing the multiple packets based on the source QoS information included in the multiple packets includes: according to the QoS requirement of the first packet and the first data feature to schedule the resource of the first message; according to the QoS requirement of the second message and the second data feature to schedule the resource of the second message.
  • the first source QoS information included in the first packet in the connection and the second source QoS information included in the second packet in the connection are different Including: the first data feature and the second data feature are different, and/or the first QoS feature and the second QoS feature are different.
  • the resources for scheduling the first packet and the resources for scheduling the second packet are different.
  • the first data feature includes a connection-level data feature and/or a packet-level data feature
  • the processing unit is further configured to: according to the connection-level data feature Determine the transmission characteristics of the multiple packets included in the connection; determine the transmission characteristics of the first packet according to the data characteristics of the packet level.
  • the first QoS feature includes a connection-level QoS feature
  • the processing unit is further configured to: determine the multiple reports in the connection according to the connection-level QoS feature.
  • the QoS requirements of the third packet except the first packet and the second packet in the text.
  • the data characteristics at the connection level include one or more of the following: average rate, duration, frequency, size, delay budget, peak frequency, peak size, Peak delay budget, peak transmission time, type of emergency, estimated time of occurrence of emergency, estimated amount of emergency packets, and estimated delay of emergency packets, where the average rate indicates the packets in the connection
  • the average sending rate indicates the duration of the connection
  • the frequency indicates the frequency of packet sending
  • the size indicates the average value of the packets sent each frequency
  • the delay budget indicates the time-consuming budget for all packets to be delivered to the receiver in a cycle
  • the peak frequency indicates the peak generation frequency of the message
  • the peak delay budget indicates the time-consuming budget for all the message peaks to be delivered to the receiving end
  • the peak sending time indicates the time when the message peak is sent
  • the emergency event type indicates sudden
  • the estimated time of occurrence of the emergency indicates the expected arrival time of the emergency message
  • the estimated amount of the emergency message indicates the amount of the message
  • the packet-level data characteristics include one or more of the following: data block sequence number, data block size, packet location, and data block delay budget, wherein the The data block sequence number indicates the data block number to which the first message belongs, the data block size indicates the size of the data block to which the first message belongs, the packet position indicates the location of the first message in the data block to which it belongs, and the data block delay budget Indicates the time-consuming budget for transmitting the first packet to the receiving end.
  • connection-level QoS characteristic includes connection QoS characteristic indication CQI and/or connection QoS characteristic information
  • packet-level QoS characteristic includes packet QoS indication PQI and/or Packet QoS feature information.
  • the receiving unit is further configured to receive a packet filtering rule from the core network device, where the packet filtering rule includes the CQI and/or the PQI; the processing unit is further for mapping the first packet to the first quality of service flow QoS flow according to the CQI and/or the PQI.
  • the receiving unit is further configured to receive the reflection trigger indication RDI and the PQI; the processing unit is further configured to record the PQI according to the RDI, and the PQI is used to indicate that the The fourth message is mapped to the third QoS flow; wherein, the fourth message is a message to be sent, and the QoS feature indicated by the 5QI in the third QoS flow corresponds to the PQI.
  • the QoS characteristics represented by the connection-level QoS characteristics or the packet-level QoS characteristics include one or more of the following: resource type, priority, delay budget and Error rate.
  • the first source QoS information included in the first packet includes: the first packet includes connection-level information and packet-level information; or, the The first packet includes the information of the packet level, and the virtual Internet protocol dummy IP packet includes the information of the connection level; or, the first packet includes the information of the packet level, and the information of the connection level is transmitted through the control plane , wherein the information of the connection level includes data characteristics of the connection level and the QoS characteristics of the connection level, and the information of the packet level includes the connection data characteristics of the packet level and the QoS characteristics of the packet level.
  • the processing unit is further configured to: map the first packet to the first quality of service flow QoS flow according to the first source QoS information;
  • the source QoS information maps the second message to the second QoS flow; wherein, the first QoS flow and the second QoS flow belong to a QoS flow group.
  • the processing unit is further configured to: map the first packet to the quality of service identifier 5QI of the first 5G network according to the first source QoS information;
  • the second source QoS information maps the second message to the second 5QI; wherein, the first 5QI and the second 5QI belong to one QoS flow.
  • the processing unit mapping the first packet to the first QoS flow according to the first source QoS information includes: the processing unit according to the first source QoS information
  • the first QoS feature included in the first QoS flow is determined from a plurality of QoS flows, wherein the first QoS feature included in the first source QoS information corresponds to the QoS feature indicated by the 5QI in the first QoS flow .
  • the QoS configuration of the first QoS flow includes: a maximum guaranteed bandwidth MGFBR; the processing unit is further configured to: determine that the guaranteed bandwidth of the first QoS flow is less than or equal to The MGFBR.
  • the QoS configuration of the first QoS flow further includes: a minimum guaranteed bandwidth GFBR; the processing unit is further configured to: determine that the guaranteed bandwidth of the first QoS flow is greater than or Equal to the GFBR and less than or equal to the MGFBR.
  • the QoS configuration of the first QoS flow includes: indication information, the indication information is used to indicate whether to reserve resources corresponding to the first QoS flow; the processing unit It is also used for: determining whether to reserve the resource corresponding to the first QoS flow according to the indication information.
  • the processing unit is further configured to: fill the first source QoS information into the first packet.
  • the processing unit is further configured to: determine the state of the transmission node in the path for transmitting the first packet; when the state of at least one of the transmission nodes satisfies a preset condition , the processing unit is also used to start the active safeguard mechanism.
  • the processing unit when the state of at least one of the input nodes satisfies a preset condition, the processing unit is configured to start an active guarantee mechanism including one or more of the following: when the at least one output node satisfies a preset condition When there is packet loss at one of the input nodes, the processing unit determines to repeatedly send the first packet; or when the packet loss rate of the at least one input node is greater than a preset value, the processing unit determines to use forward error correction (FEC redundancy) The encoding method encodes the first packet.
  • FEC redundancy forward error correction
  • a fifth aspect provides an apparatus for transmitting a message, where the apparatus for transmitting a message includes a processor for implementing the function of the message generating device in the method described in the first aspect above.
  • the apparatus for transmitting a message may further include a memory coupled to the processor, where the processor is configured to implement the function of the message generating device in the method described in the first aspect above.
  • the memory is used to store program instructions and data.
  • the memory is coupled to the processor, and the processor can call and execute program instructions stored in the memory, so as to implement the function of the message generating device in the method described in the first aspect above.
  • the apparatus for transmitting a message may further include a communication interface, where the communication interface is used for the apparatus for transmitting a message to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, a circuit, or the like.
  • the device for transmitting messages includes: a processor and a communication interface
  • the processor is configured to run a computer program, so that the device for transmitting messages implements any one of the methods described in the first aspect;
  • the processor communicates with the outside using the communication interface.
  • the external may be an object other than the processor, or an object other than the apparatus.
  • the device for transmitting the message is a chip or a chip system.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip or the chip system.
  • the processor may also be embodied as processing circuitry or logic circuitry.
  • a sixth aspect provides an apparatus for transmitting a message, where the apparatus for transmitting a message includes a processor for implementing the function of the message receiving device in the method described in the second aspect above.
  • the apparatus for transmitting a message may further include a memory coupled to the processor, and the processor is configured to implement the function of the message receiving device in the method described in the second aspect above.
  • the memory is used to store program instructions and data.
  • the memory is coupled to the processor, and the processor can call and execute program instructions stored in the memory, so as to implement the function of the message receiving device in the method described in the second aspect above.
  • the apparatus for transmitting a message may further include a communication interface, where the communication interface is used for the apparatus for transmitting a message to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, a circuit, or the like.
  • the device for transmitting messages includes: a processor and a communication interface
  • the processor communicates with the outside using the communication interface
  • the processor is configured to run a computer program, so that the device for transmitting a message implements any one of the methods described in the second aspect above.
  • the external may be an object other than the processor, or an object other than the apparatus.
  • the device for transmitting the message is a chip or a chip system.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip or the chip system.
  • the processor may also be embodied as processing circuitry or logic circuitry.
  • the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, when the computer-readable storage medium runs on a computer, the computer executes the methods of the above aspects.
  • the present application provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods of the above aspects.
  • a communication system including the apparatus for transmitting a message shown in the third aspect and the apparatus for transmitting a message shown in the fourth aspect.
  • a chip device including a processing circuit, which is used to call and run a program from a memory, so that a communication device installed with the chip device can perform any one of the above-mentioned first and second aspects. method in the implementation.
  • FIG. 1 is a schematic diagram of a network architecture to which an embodiment of the present application is applied.
  • FIG. 2 is a schematic flowchart of a method for transmitting a message provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of another method for transmitting a packet provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of the structure of a header of an Internet protocol version 4 (Internet protocol version 4, IPV4) packet.
  • Internet protocol version 4 Internet protocol version 4, IPV4
  • FIG. 4 is a schematic diagram of the structure of the header of an Internet protocol version 6 (Internet protocol version 6, IPV6) packet.
  • Internet protocol version 6 Internet protocol version 6, IPV6
  • FIG. 5 is a schematic diagram of the structure of the header of a real-time transport protocol (RTP) message.
  • RTP real-time transport protocol
  • FIG. 6 is a schematic diagram of the format of the RTP extension header.
  • GTP general packet radio service tunnelling protocol
  • FIG. 8 (a) in Figure 8 is a schematic diagram of a 5G QoS flow model.
  • FIG. 8 is a schematic diagram of a QoS flow model provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of another QoS flow model provided by the embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a reflective QoS mechanism provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of an apparatus 1000 for transmitting a message provided by the present application.
  • FIG. 11 is a schematic structural diagram of a message generating device 1100 suitable for this embodiment of the present application.
  • FIG. 12 is a schematic diagram of another apparatus 1200 for transmitting a message provided by the present application.
  • FIG. 13 is a schematic structural diagram of a message receiving device 1300 suitable for this embodiment of the present application.
  • FIG. 1 is a schematic diagram of a network architecture to which an embodiment of the present application is applied. Each part involved in the network architecture shown in FIG. 1 will be described below.
  • User equipment (UE) 110 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of terminals, Mobile station (mobile station, MS), terminal (terminal) or soft terminal, etc. For example, water meters, electricity meters, sensors, etc.
  • the user equipment in this embodiment of the present application may refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, a user terminal, or a terminal device.
  • terminal equipment wireless communication equipment, user agent or user equipment.
  • the user equipment may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • a wearable device may also be referred to as a wearable smart device, which is a general term for intelligently designing daily wearable devices and developing wearable devices using wearable technology, such as glasses, Gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • the user equipment may also be a user equipment in an Internet of Things (IoT) system.
  • IoT Internet of Things
  • the IOT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, a narrow band (narrow band, NB) technology.
  • NB narrow band
  • the user equipment may also include sensors such as smart printers, train detectors, and gas stations, and the main functions include collecting data (part of user equipment), receiving control information and downlink data of access network equipment, and Send electromagnetic waves to transmit uplink data to access network equipment.
  • sensors such as smart printers, train detectors, and gas stations
  • the main functions include collecting data (part of user equipment), receiving control information and downlink data of access network equipment, and Send electromagnetic waves to transmit uplink data to access network equipment.
  • the device for implementing the function of the user equipment may be the user equipment, or may be a device capable of supporting the user equipment to realize the function, for example, a chip system or a combined device or component that can realize the function of the user equipment.
  • the apparatus may be installed in user equipment.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the technical solutions provided by the embodiments of the present application are described by taking the device for implementing the functions of the user equipment as the user equipment as an example.
  • (wireless) access network equipment (radio access network, (R)AN) 120 used to provide network access functions for authorized user equipment in a specific area, and can use different quality of transport tunnel.
  • (R)AN can manage radio resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and the core network.
  • (R)AN can also be understood as a base station in a traditional network.
  • the access network device in this embodiment of the present application may be any communication device having a wireless transceiver function for communicating with user equipment.
  • the access network equipment includes but is not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved NodeB, HeNB, or home Node B, HNB), baseband unit (baseBand unit, BBU), wireless fidelity (wireless fidelity, WIFI)
  • the access point (AP), wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP) in the system can also be 5G, For example, a new radio (NR), a gNB in the system, or a transmission point (TRP or TP), one or a group (including multiple antenna panels) antenna panels of a base station in
  • a gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • the CU implements some functions of the gNB, and the DU implements some functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implementing functions of radio resource control (RRC) and packet data convergence protocol (PDCP) layers.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer and the physical (PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical layer
  • the higher-layer signaling such as the RRC layer signaling
  • the access network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the CU can be divided into access network equipment in the access network (radio access network, RAN), and the CU can also be divided into the access network equipment in the core network (core network, CN), this application does not Do limit.
  • the device for implementing the function of the access network device may be the access network device, or may be a device capable of supporting the access network device to realize the function, such as a chip system or a device capable of realizing the function of the access network device
  • the combination device and component of the device can be installed in the access network equipment.
  • the technical solutions provided by the embodiments of the present application are described by taking the device for implementing the functions of the access network equipment as an example of the access network equipment.
  • the interface between the access network device and the user equipment may be a Uu interface (or called an air interface).
  • Uu interface or called an air interface.
  • the names of these interfaces may remain unchanged, or may be replaced with other names, which are not limited in this application.
  • the communication between the access network device and the user equipment follows a certain protocol layer structure.
  • the control plane protocol layer structure may include the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the physical layer; the user plane protocol layer structure. It may include a PDCP layer, an RLC layer, a MAC layer, and a physical layer.
  • a service data adaptation (service data adaptation protocol, SDAP) layer may also be included above the PDCP layer.
  • User plane network element 130 used for packet routing and forwarding, and quality of service (quality of service, QoS) processing of user plane data, and the like.
  • the user plane network element may be a user plane function (UPF) network element.
  • the user plane network element may still be the UPF network element, or may have other names, which are not limited in this application.
  • Data network network element 140 used to provide a network for transmitting data.
  • the data network element may be a data network (DN) network element.
  • DN data network
  • the data network element may still be a DN network element, or may have other names, which are not limited in this application.
  • Access management network element 150 mainly used for mobility management and access management, etc., and can be used to implement other functions except session management in mobility management entity (mobility management entity, MME) functions, for example, legal Monitoring and access authorization/authentication functions.
  • mobility management entity mobility management entity, MME
  • the access management network element may be an access and mobility management function (AMF) network element.
  • AMF access and mobility management function
  • the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.
  • Session management network element 160 mainly used for session management, network interconnection protocol (IP) address allocation and management of user equipment, selection and management of user plane functions, policy control and charging function interface termination point and downlink data notification, etc.
  • IP network interconnection protocol
  • the session management network element may be a session management function (session management function, SMF) network element.
  • SMF session management function
  • the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.
  • network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).
  • the access management function network element is the AMF network element
  • the data network element is the DN network element
  • the user plane function network element is the UPF network element
  • the session management function network element is the SMF network element as an example. Be explained.
  • AMF AMF
  • DN the DN network element
  • UPF the UPF network element
  • SMF the SMF network element
  • this application takes the device as an example of an AMF entity, a DN entity, a UPF entity and an SMF entity to describe the method of transmitting a message.
  • the device as a chip in the AMF entity, a chip in the UPF entity, or an SMF entity
  • the implementation method of the chip in the entity reference may be made to the specific description that the devices are the AMF entity, the UPF entity, and the SMF entity, which will not be repeated.
  • the user equipment is connected to the AMF through the N1 interface
  • the RAN is connected to the AMF through the N2 interface
  • the RAN is connected to the UPF through the N3 interface.
  • the UPFs are connected through the N9 interface, and the UPFs are interconnected with the DN through the N6 interface.
  • the SMF controls the UPF through the N4 interface.
  • the AMF interfaces with the SMF through the N11 interface.
  • the network architecture to which the embodiment of the present application can be applied as shown in FIG. 1 is only an example, and the network architecture applicable to the embodiment of the present application is not limited to this, and any network architecture that can realize the functions of the above-mentioned network elements is applicable. in the examples of this application.
  • network function network element entities such as AMF network elements, SMF network elements, and UPF network elements are referred to as network function network elements (NF) network elements; or, in other network architectures , a set of network elements such as AMF network elements, SMF network elements, and UPF network elements can be called control plane function network elements.
  • NF network function network elements
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • 5G new radio
  • NR new radio
  • the communication system may also be a public land mobile network (PLMN) network, a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an object Internet of Things (IoT) communication system or other communication system.
  • PLMN public land mobile network
  • D2D device-to-device
  • M2M machine-to-machine
  • IoT object Internet of Things
  • the user equipment or the access network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • This hardware layer includes hardware such as central processing unit (CPU), memory management unit (MMU), and memory (also called main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of the present application do not specifically limit the specific structure of the execution body of the methods provided by the embodiments of the present application, as long as the program that records the codes of the methods provided by the embodiments of the present application can be executed to provide the methods provided by the embodiments of the present application.
  • the execution subject of the method provided by the embodiment of the present application may be a user equipment or an access network device, or a functional module in the user equipment or access network device that can call and execute a program.
  • various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques.
  • article of manufacture encompasses a computer program accessible from any computer readable device, carrier or medium.
  • computer readable media may include, but are not limited to, magnetic storage devices (eg, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (eg, compact discs (CDs), digital versatile discs (DVDs) etc.), smart cards and flash memory devices (eg, erasable programmable read-only memory (EPROM), card, stick or key drives, etc.).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable storage medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
  • Each forwarding device processes all packets using a first-in-first-out (FIFO) policy, and does its best to process all packets. Sends the message to the destination, but does not provide any guarantee on the reliability of message transmission, transmission delay and other performance.
  • FIFO first-in-first-out
  • the best-effort service service model is the simplest service model. An application can send out any number of messages at any time without prior approval or notification to network devices. For the best-effort service service model, network devices try their best to send packets. However, no guarantee is provided for performance such as delay and reliability.
  • the best-effort service service model is suitable for most network applications, such as FTP, E-Mail, etc., and is implemented through FIFO queues.
  • RSVP Resource Reservation Protocol
  • network resources such as bandwidth, delay, etc.
  • the network device After the network device confirms the allocation of resources for the application, the network device maintains a state for each connection, and performs packet classification, traffic policing, queuing and scheduling based on this state. As long as the packets of the application are controlled within the range described by the traffic parameters, the network device will promise to meet the QoS requirements of the application.
  • the network device maintains the connection state by configuring a quintuple, wherein the quintuple includes a source IP address, a destination IP address, a protocol number, a source port, and a destination port.
  • the DiffServv service model does not need to use RSVP, that is, the application does not need to notify the network device to reserve resources for it before sending a message.
  • the network device does not need to maintain the state for each flow, and the network device differentiates services code point (differentiated services code point, DSCP) according to the differentiated services class (differentiated services tag field in the IP packet header) of each packet. value) to provide a specific service.
  • DSCP differentiated services code point
  • differentiated services class differentiated services tag field in the IP packet header
  • each forwarding device will perform corresponding forwarding behaviors according to the DSCP fields of the packets, mainly including the following three types of forwarding behaviors:
  • Expedited forwarding It is mainly used for services with low delay, jitter and packet loss rate. Such services generally run at a relatively stable rate and require fast forwarding in the forwarding device;
  • AF Assured forwarding
  • the service that adopts the guaranteed forwarding behavior can ensure the forwarding when the maximum allowable bandwidth is not exceeded. Once the maximum allowable bandwidth is exceeded, the forwarding behavior is divided into 4 categories, and each category can be divided into 3 different types. , each of which ensures that a different bandwidth resource can be allocated to the forwarding class.
  • IETF recommends using 4 different queues to transmit AF1x, AF2x, AF3x, AF4x services, and each queue provides 3 different drop priorities, so 12 guaranteed forwarding per-hop behaviors (Per-Hop Behavior, PHB);
  • BE Best-effort delivery
  • the DiffServ service model only includes a limited number of service levels, and the number of status information is small, so it is simple to implement and has good scalability. It is the mainstream IP network QoS solution in the industry.
  • the disadvantage of the DiffServ service model is that it is difficult to provide end-to-end quality assurance based on flows. Because although the IETF defines the recommended DSCP value for each standard PHB, equipment manufacturers can redefine the mapping relationship between DSCP and PHB, so the intercommunication between DiffServ networks of different operators is still difficult. Different DiffServ networks It is necessary to maintain a consistent DSCP and PHB mapping during interworking.
  • the service model involved in the embodiments of this application refers to a set of end-to-end QoS functions.
  • QoS flow is the minimum QoS control granularity, and each QoS flow has a corresponding QoS configuration.
  • the QoS parameters included in the QoS configuration describe the specific QoS requirements.
  • the QoS parameters mainly include:
  • QoS flow index QoS flow index, QFI
  • 5G network quality of service identifier 5QI minimum guaranteed flow rate (guaranteed flow bit rate, GFBR), maximum guaranteed flow rate (maximum flow bit rate, MFBR).
  • the 5QI in the QoS parameter is a group of QoS feature combination indexes, and the QoS features include:
  • Resource type priority level, packet delay budget, packet error rate, averaging window, and maximum data burst volume ).
  • the resource types include: non-guaranteed bit rate (non-GRB), minimum guaranteed rate (guaranteed bit rate, GRB), delay-sensitive GRB (delay-critical GBR); the maximum burst data volume is Delay-sensitive GRB-specific parameters.
  • non-GRB non-guaranteed bit rate
  • GRB minimum guaranteed rate
  • delay-sensitive GRB delay-sensitive GRB-specific parameters.
  • the 3GPP R16 standard defines a part of the QoS characteristic values of 5QI, which can be used directly. 3GPP also allows operators and/or equipment manufacturers to allocate non-conflicting 5QIs and preset corresponding QoS characteristic values for use in the operator's network.
  • the 5G control plane network elements AMF and SMF deliver the QoS flow configuration to the UE, RAN and UPF, and at the same time deliver the packet filters set to the UE and UPF.
  • the UE maps the uplink packets to the corresponding QoS flow according to the packet filtering rules
  • UPF maps the downlink packets received from the N6 port to the corresponding QoS flow according to the packet filtering rules.
  • the data downlink process in the current 5G scenario includes:
  • Step 1 The user data is included in the IP message and sent from the DN to the UPF device of the 5G core network (5G core, 5GC) through the N6 interface;
  • Step 2 UPF maps IP packets to the corresponding QoS flow according to the QoS configuration and packet filters set issued by the 5GC control plane;
  • the packet filters set defined by the 5G R16 standard includes the following parameters:
  • IPV4 The type of service (TOS) of the header field or the communication category in the IPV4 header field, the flow label field in IPv6 (flow label (IPv6)), the security parameter index (security parameter index) and the packet direction (packet filter) direction).
  • TOS The type of service of the header field or the communication category in the IPV4 header field
  • IPv6 flow label (IPv6)
  • security parameter index security parameter index
  • packet direction packet filter
  • Step 3 UPF performs targeted protection and processing according to the QoS requirements of the QoS flow to which the message belongs;
  • Step 4 UPF uses the general packet radio service tunneling protocol user (GTP-U) protocol to encapsulate the user plane IP packet, and fills in the QFI of the QoS flow to which the packet belongs to the GTP-U protocol header external field, and then forwards the packet to the N3 interface.
  • GTP-U general packet radio service tunneling protocol user
  • the SDAP protocol layer is added to the user plane of the 5G air interface to adapt to the 5G QoS mechanism.
  • SDAP can realize the mapping between QoS flow and data radio bearer (DRB) and the reflective QoS mechanism.
  • the upstream process includes:
  • Step 1 The 5GC control plane issues multiple QoS rules to the UE, and each QoS rule contains the packet filters set and the bound QFI;
  • Step 2 After the UE bottom layer (SDAP protocol stack) receives the IP packet to be sent by the application (application, APP), it matches the packet to the corresponding QoS flow according to the packet filters set in the QoS rule, and fills in the corresponding QFI in air interface packet header;
  • SDAP protocol stack Secure Sockets Layer
  • Step 3 According to the QoS requirements of the QoS flow, the UE maps the IP packets to DRBs of different bearer standards and sends them;
  • Step 4 After the RAN side receives the message sent by the UE, it encapsulates the user plane IP message with the GTP-U protocol, and parses the air interface data packet header to obtain the QFI of the QoS flow to which the message belongs and fills in the GTU-U protocol header field. The packet is then forwarded to the N3 interface.
  • the UE can learn the QoS rules through the QoS reflection mechanism, including:
  • the SDAP protocol header of the air interface protocol stack includes QFI and whether it supports reflective QoS indication: reflective QoS flow to DRB mapping indication (RDI);
  • RDI reflective QoS flow to DRB mapping indication
  • the UE After the UE receives the downlink message, if it finds that the RDI indication is 1, it records the message quintuple, QFI information, and DRB information as the QoS rules learned through the reflection QoS mechanism;
  • the UE When the UE sends uplink packets, it can use the QoS rules learned through the reflection QoS mechanism to match, and match the packets to the corresponding QoS flow and DRB to send.
  • the above-mentioned QoS flow mechanism quantifies the QoS requirements, and the transmission equipment in the network can clearly confirm the QoS requirements and process them through the QoS flow indicator (QFI) in the message (for example, obtain the corresponding QoS configuration according to the QFI). QoS features corresponding to 5QI). Therefore, the QoS flow mechanism solves the problem in the IETF Diffserv service model that different equipment vendors and/or different operators have inconsistent implementations of DSCP and PHB mapping.
  • QFI QoS flow indicator
  • the forwarding node in the transmission network matches the packet to the preset QoS policy according to the network layer characteristics of the IP packet, and executes the process according to the QoS policy.
  • a model for differentiated assurance processing
  • the network layer feature of the IP packet may be the above-mentioned quintuple, TOS, DSCP or QFI; the QoS policy is obtained through configuration or control plane delivery.
  • the application cannot clearly and detailedly indicate the QoS requirements to the transmission network, and further, the application cannot indicate the application layer data characteristics to the transmission network.
  • the information that the connection level is not supported and/or the information that the IP packet level is not supported is indicated to the transport network.
  • the information that does not support the connection level includes:
  • Connection-level data features such as group of picture (GOP) features (average bit rate, frame rate, I-frame frequency, etc.), Internet of things (IOT) data reporting features (reporting cycle, data size, etc.) Wait);
  • GOP group of picture
  • IOT Internet of things
  • Connection-level emergency event information drag events during video-on-demand, head-turn events during virtual reality (VR) playback, etc.
  • IP packet level Information that is not supported at the IP packet level includes:
  • the relationship between the IP packet and the data segment such as which frame of the video the current IP packet belongs to, and how much data there is in the video frame after the IP packet;
  • QoS indication at the IP packet level Due to the limitations of packet filtering rules and transmission protocols, it is difficult to map different packets in a connection to different QoS policies in the current QoS mechanism (for example, I-frame data and P-frame data in a video connection may using a different QoS policy).
  • 3GPP R16 defines a packet filters set mechanism to instruct UPF and UE to map packets to QoS flow.
  • the network has high requirements and many restrictions, which is inconvenient to use.
  • the use of TOS or DSCP mapping has the problem of serial modification and information loss by the transport layer, including:
  • DSCP/TOS is a qualitative QoS expectation
  • 5QI is a quantitative QoS indicator, so there may be information loss problems in mutual conversion
  • the DSCP/TOS may be modified by the routing equipment of the transmission network, and the APP cannot reliably transmit the QoS characteristics to the 3GPP network.
  • the QoS flow mechanism is a macro control mode in which the control plane (AMF, SMF) negotiates, issues QoS policy configuration to the user plane (UPF, RAN), and the user plane packets match the corresponding QoS mechanism according to the rules;
  • the IntServ service model uses the resource reservation protocol (RVSP) protocol, and the DiffServ uses the configuration function in the operation and maintenance field to issue QoS policy configuration, which also belongs to the macro control mode.
  • RVSP resource reservation protocol
  • the DiffServ uses the configuration function in the operation and maintenance field to issue QoS policy configuration, which also belongs to the macro control mode.
  • the macro control mode the decision-making and execution chain of QoS policy changes are long, and the change takes time (seconds or even minutes), which cannot meet the business requirements of frequent and rapid adjustment of QoS policies.
  • the application needs to call the QoS policy change interface of different transmission networks, which is difficult to develop and requires high requirements.
  • GFBR and/or maximum data burst volume (MDBV) in 5G QoS flow cannot be dynamically adjusted according to changes in the number of connections;
  • the number of concurrent connections of a user equipment may change dynamically (for example, customer premises equipment (CPE) may be hung with 1, 3 or N devices), and reservations based on the maximum possible number of concurrent connections will be extremely high.
  • CPE customer premises equipment
  • a huge waste of air interface resources; services calling 5GC open interfaces to dynamically adjust GFBR or MDBV will greatly increase the difficulty of application development, and operators may not open this capability for security reasons.
  • the present application provides a method for transmitting a message, which uses the path-by-path method to carry source QoS information in the message, and the transceiver and the transmission network realize end-to-end according to the source QoS information.
  • QoS guarantee is a method for transmitting a message, which uses the path-by-path method to carry source QoS information in the message, and the transceiver and the transmission network realize end-to-end according to the source QoS information.
  • the QoS information involved in the embodiment of the present application can be understood as a QoS parameter, and can also be understood as an identifier indicating a QoS parameter, which is used to provide QoS guarantee for the message.
  • the sender can clearly and detailedly indicate the application data characteristics and QoS requirements to the transmission network; and/or
  • the forwarding device in the transmission network can clearly perceive the connection-level, packet-level data characteristics and QoS requirements through the packets, and ensure and optimize according to the instructions; and/or
  • the transmission device can also trigger the rapid adjustment of the pipeline QoS policy within a reasonable range according to the perceived data characteristics.
  • to indicate may be understood as “enable”, and “enable” may include direct enabling and indirect enabling.
  • Enable When describing a certain information for enabling A, it may include that the information directly enables A or indirectly enables A, but it does not mean that the information must carry A.
  • the information enabled by the information is called the information to be enabled.
  • the information to be enabled can be directly enabled.
  • the information to be enabled may also be indirectly enabled by enabling other information, where there is an associated relationship between the other information and the information to be enabled. It is also possible to enable only a part of the information to be enabled, while other parts of the information to be enabled are known or agreed in advance.
  • the enabling of specific information may also be implemented by means of a pre-agreed (for example, a protocol stipulated) arrangement order of various information, thereby reducing enabling overhead to a certain extent.
  • the common part of each information can also be identified and enabled in a unified manner, so as to reduce the enabling overhead caused by enabling the same information separately.
  • preset may include predefined definitions, eg, protocol definitions.
  • pre-definition can be achieved by pre-saving corresponding codes, forms or other means that can be used to indicate relevant information in the device (for example, including user equipment or network equipment), and this application does not make any specific implementation methods. limited.
  • the "storage” involved in the embodiments of this application may refer to being stored in one or more memories.
  • the one or more memories may be set separately, or may be integrated in an encoder or a decoder, a processor, or a communication device.
  • the one or more memories may also be partially provided separately and partially integrated in a decoder, a processor, or a communication device.
  • the type of memory may be any form of storage medium, which is not limited in this application.
  • the "protocols” involved in the embodiments of this application may refer to standard protocols in the communication field, such as 5G protocols, new radio (NR) protocols, and related protocols applied in future communication systems.
  • the application is not limited.
  • the present application provides a method for transmitting a message.
  • the executive body includes a message generating device and a message receiving device.
  • the message generating device may be a network (for example, a DN network element) used to provide transmission data
  • the message receiving device includes a core network device ( For example, UPF), access network equipment and user equipment.
  • UPF core network device
  • the message generating device may be an application layer in the user equipment, and the message receiving device includes the bottom layer (for example, the SDAP layer) in the user equipment.
  • the bottom layer for example, the SDAP layer
  • core network equipment eg, UPF
  • access network equipment e.g, DN network elements
  • FIG. 2 is a schematic flowchart of a method for transmitting a message provided by an embodiment of the present application.
  • the method for transmitting a message includes at least some of the following steps.
  • the data network generates a first packet #1.
  • the application on the Internet network generates the first packet #1 in the connection according to the QoS requirement of the service.
  • the first packet #1 includes first source QoS information, where the first source QoS information is used to provide QoS guarantee for the first packet #1.
  • the QoS guarantee in the embodiments of the present application includes providing services for packets and solving problems such as network delay and/or network congestion.
  • IP messages may be referred to as IP messages, data messages, service messages, packets or messages, etc., and hereinafter referred to as messages are just examples and do not constitute any protection scope of the present application.
  • the definition can be understood as the data packets transmitted in the transmission network.
  • the above-mentioned first packet #1 may be any one of the multiple packets generated by the data network, and the quintuple information of the multiple packets is the same, which can be understood as the multiple packets.
  • a message belongs to a connection.
  • the quintuple information of a packet in a connection is the same, and the quintuple information is used to indicate the quintuple of the packet, which may be a quintuple parameter (for example, the above-mentioned source IP address, destination IP address, etc.).
  • protocol number, source port, destination port can also be an identifier indicating a quintuple (for example, identifier #1 indicates source IP address #1, identifier #2 indicates destination IP address #1, and identifier #3 indicates protocol number # 1.
  • the identifier #4 indicates the source port #1, the identifier #5 indicates the destination port #1), and so on, which indirectly indicates the information of the quintuple.
  • the method flow shown in (a) in Figure 2 also includes:
  • the data network generates a second packet #1.
  • the second packet #1 may be any packet other than the above-mentioned first packet #1 among the multiple packets generated by the data network.
  • the second packet #1 includes second source QoS information, where the second source QoS information is used to provide QoS guarantee for the second packet #1.
  • the data network can also generate other messages in the connection.
  • the above-mentioned generation of the first message #1 and the second message #1 is only an example, and the protection scope of the present application is not limited in any way.
  • the network can generate multiple packets, and the quintuple information of the multiple packets is the same.
  • each of the multiple packets includes source QoS parameters, and the source QoS information included in each packet is used to ensure QoS for the corresponding packet, and the multiple packets include The source QoS information is not the same.
  • the first source QoS information included in the first packet #1 and the second source QoS information included in the second packet #1 are different.
  • the source QoS information included in a certain packet of the multiple packets is different from the source QoS information included in at least one packet other than the certain packet in the multiple packets.
  • the source QoS information respectively included in at least two of the multiple packets are different.
  • the two pieces of source QoS information respectively included in the two packets refer to that each of the two packets includes one source QoS information.
  • the source QoS information includes a QoS feature and a data feature, where the QoS feature is used to indicate the QoS requirement of the packet, and the data feature is used to indicate the transmission characteristic of the packet.
  • the above-mentioned first source QoS information includes a first QoS feature and a first data feature
  • the first QoS feature is used to indicate the QoS requirement of the first packet
  • the first data feature represents the transmission feature of the first packet.
  • the above-mentioned second source QoS information includes a second QoS feature and a second data feature
  • the second QoS feature is used to indicate the QoS requirement of the second packet
  • the second data feature represents the transmission feature of the second packet.
  • the source QoS information included in the above-mentioned multiple packets is different. It may be that the data features included in the multiple packets are different, and/or the multiple packets include QoS characteristics are different.
  • the first data feature in the first source QoS information included in the first packet #1 and the second data feature in the second source QoS information included in the second packet #1 are different; and/ or,
  • the first QoS feature in the first source QoS information included in the first packet #1 and the second QoS feature in the second source QoS information included in the second packet #1 are different.
  • connection includes the first packet #1 and the second packet #1, and the different QoS features respectively included in the first packet #1 and the second packet #1 are only examples, and the protection of the present application
  • connection may also include other packets, and the QoS characteristics included in different packets may be different.
  • multiple packets in a connection may have different QoS characteristics, and QoS guarantee is performed on different packets according to the QoS characteristics.
  • QoS guarantee can be provided for packets according to the QoS requirements of different packets.
  • the source QoS information proposed in this application is described below by taking a certain packet in the connection including the source QoS information as an example.
  • the source QoS information includes QoS characteristics, and further the source QoS information also includes data characteristics.
  • the data features include connection-level data features and/or packet-level data features.
  • the data feature at the connection level is used to indicate the transmission characteristics of multiple packets included in the connection, that is, the transmission characteristics of the connection;
  • the data characteristics at the packet level are used to indicate the transmission characteristics of a certain packet, that is, the data at the packet level.
  • the characteristics indicate the transmission characteristics of the message including the data characteristics at the packet level.
  • the data features at the connection level include basic connection information, and further the data features at the connection level include at least one of periodic connection information, periodic connection peak information, or connection emergency notification information.
  • the basic connection information includes the average rate or duration.
  • the average rate indicates the average sending rate of connection data, for example, the bit rate of a live video connection is 2 Mbps, and the duration indicates the expected connection duration.
  • Periodic connection information includes frequency, size or delay budget.
  • the frequency indicates the frequency of data transmission, for example, 25Hz (25 frames per second, and one frame is generated every 40ms)
  • the size indicates the average value of the data sent per frequency, for example, the average P frame of a live video connection is 0.3Mbyte
  • the delay indicates the time-consuming budget for all data to be delivered to the receiver in one cycle.
  • Periodic connection peak information includes peak frequency, peak size, peak delay budget, or peak transmission time.
  • the peak frequency indicates the frequency of peak generation, for example, 0.5 Hz (one I frame occurs every two seconds (one GOP for 2 seconds))
  • the size of the peak indicates the average value of data sent by the peak (for example, one I frame is 2MB)
  • the peak delay budget Indicates the time-consuming budget for all the peak data to be delivered to the receiving end, and the peak sending time indication can be expressed in absolute time, relative time (how many milliseconds away from now), and relative position (at which frequency).
  • the connection emergency notification information includes the type of the emergency, the estimated time of the emergency, the estimated data volume of the emergency, or the budget for the delay of the emergency data.
  • the types of emergencies include, for example, VR head turning, video playback and dragging;
  • the estimated time of occurrence of the emergency indicates the expected arrival time of the emergency data, expressed as a relative time;
  • the estimated amount of emergency data indicates the data that needs to be transmitted in the emergency
  • the emergency data delay budget indicates the time-consuming budget for all the emergency events to be transmitted to the receiver.
  • Packet-level data characteristics include packet data integrity information.
  • Packet data integrity information includes block sequence number, block size, packet location, or block delay budget. Specifically, the sequence number of the data block indicates the number of the data block to which the packet belongs, for example, it is serially numbered by frame in the video stream; the size of the data block indicates the size of the data block to which the packet belongs, for example, the size of the P-frame data segment is 0.3Mbytes; The location of the data block; the data block delay budget indicates the time-consuming budget for all packets to be transmitted to the receiving end.
  • the data blocks involved in the embodiments of this application can be understood as data blocks in a connection, and the data blocks can include at least one packet.
  • each I frame and P frame can be called for the data block.
  • the data block may also be referred to as a data segment, a message segment, or a message block.
  • a certain data block includes multiple packets, and the packet-level data features in different packets include information such as the position and sequence number of the packets in the data block.
  • data integrity transmission means that the receiving end completely receives all the packets of a certain data block before using it (such as a frame of a video), and the transmission network can be optimized and guaranteed in a targeted manner. The transmission efficiency can be improved without affecting the overall delay of the application.
  • the QoS features include connection-level QoS features and/or packet-level QoS features, wherein the connection-level QoS features are used to indicate the QoS requirements of multiple packets included in the connection, that is, indicate the QoS requirements of the connection;
  • the QoS characteristic is used to indicate the QoS requirement of a certain packet, that is, the QoS characteristic at the packet level indicates the transmission characteristic of the packet including the QoS characteristic at the packet level.
  • connection-level QoS feature may be a connection-level QoS feature indicator CQI
  • packet-level QoS feature may be a packet-level QoS feature indicator PQI, where CQI is a connection-level QoS feature, and PQI is a packet-level QoS feature.
  • the QoS features that can be described by CQI and PQI include: resource type, priority, delay budget or error rate, where the resource type can be GBR, delay-sensitive GBR, and Non-GBR; the smaller the priority value, the higher the priority. The higher the level; the delay budget indicates the expected E2E delay; the error rate can be the probability of wrong packets and packet loss.
  • CQI and PQI are only examples of QoS features that can be described by CQI and PQI, and do not constitute any limitation to the scope of protection of this application.
  • CQI and PQI can also describe other QoS features, which are not described here. One by one example.
  • CQI and PQI feature values can also be predefined through standards or enterprise specifications and delivered to the transmission network. In this way, as long as the CQI and PQI are carried in the message, the transmission device can know the quantified QoS requirements at the connection level and/or the packet level.
  • connection-level QoS feature may also be connection QoS feature information
  • packet-level QoS feature may also be packet QoS feature information
  • the source QoS information is carried in the packet, including the following possibilities:
  • Possibility 2 The packet information is carried in the message, and the connection information is carried in the virtual dummy IP packet;
  • Possibility 3 The packet information is carried in the packet, and the connection information is transmitted through the control plane.
  • connection information includes the above-mentioned connection-level data characteristics and connection-level QoS characteristics
  • packet information includes connection-level data characteristics and packet-level QoS characteristics
  • the above-mentioned possibility 1 to 3 are only examples to illustrate how to send the source QOS information to other nodes in the transmission network, and do not constitute any limitation to the protection scope of this application, and the source QOS information can also be sent through other possible implementations.
  • the source QOS information can be sent to the transmission node through other information flows, and the corresponding relationship between the source QOS information and the message is indicated.
  • the QoS feature of the connection level is the above-mentioned CQI
  • the QoS feature of the packet level is the above-mentioned PQI as an example to illustrate how to carry the source QoS information.
  • the QoS feature of the connection level is the connection QoS feature information
  • the QoS feature of the packet level is the packet.
  • the filling method is similar and will not be repeated in this application.
  • the message transmission protocol needs to be extended.
  • IPV4 message header structure request for comments (request for comments, RFC) is defined as shown in Figure 3, which is a schematic diagram of the IPV4 message header structure, including:
  • IP protocol (IPv4) version number bit IP protocol (IPv4) version number bit
  • 4-bit header length identifies how many 4 bytes there are in the header, that is, a maximum of 15*4 bytes in total;
  • 8-bit type of service contains a 4-bit priority field: minimum delay, maximum throughput, maximum reliability and minimum cost;
  • 16-bit total length indicates the length of the entire IP datagram
  • 16-bit identification identifies the datagram
  • 13-bit fragment offset the offset of the fragment relative to the beginning of the original IP datagram
  • TTL time to live
  • Protocol used to distinguish upper-layer protocols
  • header checksum Check whether the datagram header is damaged during transmission
  • the options field in the above IP header can be used for extension.
  • Type 1 There is only one option-type
  • Type 2 option-type and option-length (the length of option-data) and option-data;
  • connection information and packet information are all transmitted in the IP header of the data packet.
  • Type 2 (option-type and ption-length (the length of option-data) and option-data) can be used to extend the Option field of the IP header to support application data characteristics and QoS requirement indication.
  • Option-data expansion method A Expand according to the fixed field method.
  • the fixed field is defined in the following table 2:
  • Table 2 is only exemplary, and does not constitute any limitation to the protection scope of the present application.
  • the unit information in Table 3 may not indicate; for example, the length information in Table 3 may not indicate; for example, one or more items of connection information and/or packet information in Table 3 may not be indicated. That is to say, there may be multiple possibilities for the specific embodiment of the connection information and the packet information, which will not be illustrated here one by one.
  • Option-data expansion mode B Expansion by threshold limit value (TLV) or protocol buffer (protocol buffer), and the definitions of each field are similar to those in Table 3 above. After using the TLV or protocol buffer format, each field can be transmitted as needed, and it is not necessary to carry all of them (for example, aperiodic connection may not carry periodic parameters). For the encoding method of TLV or protocol buffer, reference may be made to the relevant provisions in the current protocol, which will not be repeated in this application.
  • TLV threshold limit value
  • protocol buffer protocol buffer
  • IP extension mode 2 Packet information is transmitted in the IP header of the data packet, and connection information is transmitted using dummy IP packets. Carrying connection information and packet information in each IP packet will cause excessive packet transmission overhead.
  • the dummy IP packet does not transmit user data, but only the connection information corresponding to the quintuple.
  • dummy IP packets are sent periodically (e.g. every 2 seconds) and immediately when the connection information changes (e.g. video stream resolution adjustment causes the connection information to change).
  • the packet information can be transmitted in the IP header of the data packet, and the connection information uses the dummy IP packet transmission method to reduce the transmission overhead of the source QOS information.
  • Use type 2 to extend the Option field of the IP header to support application data characteristics and QoS requirement indication.
  • Option-data expansion method A Expand according to the fixed field method.
  • the fixed field definitions are shown in Table 3 below:
  • Table 3 is only exemplary, and does not constitute any limitation to the protection scope of the present application.
  • the unit information in Table 4 may not indicate; also for example, the length information in Table 4 may not indicate; also for example, one or more items of the packet information in Table 4 may not indicate. That is to say, there are many possibilities for the specific embodiment of the packet information, which will not be illustrated one by one here.
  • Option-data expansion mode B It is expanded by TLV or protocol buffer mode, and the definitions of each field are similar to those in Table 4 above. After using the TLV or protocol buffer format, each field can be transmitted as needed, and it is not necessary to carry all of them (for example, aperiodic connection may not carry periodic parameters). For the encoding method of TLV or protocol buffer, reference may be made to the relevant provisions in the current protocol, which will not be repeated in this application.
  • Use type 2 to extend the Option field of the IP header to support application data characteristics and QoS requirement indication.
  • Option-data expansion method A Expand according to the fixed field method.
  • the fixed field definitions are shown in Table 4 below:
  • Table 4 is only exemplary, and does not constitute any limitation to the protection scope of the present application.
  • the unit information in Table 5 may not be indicated; for example, the length information in Table 5 may not be indicated; and, for example, one or more items of the connection information in Table 5 may not be indicated. That is to say, the specific embodiment of the connection information may have multiple possibilities, which will not be illustrated here one by one.
  • Option-data expansion mode B It is expanded by TLV or protocol buffer mode, and the definitions of each field are similar to the above table. After using the TLV or protocol buffer format, each field can be transmitted as needed, and it is not necessary to carry all of them (for example, aperiodic connection may not carry periodic parameters). For the encoding method of TLV or protocol buffer, reference may be made to the relevant provisions in the current protocol, which will not be repeated in this application.
  • option-data can also be placed in the IP packet data area for transmission;
  • the IP packet data area can also be used to transmit other useful information, such as network status.
  • connection information when using dummy IP packets to transmit connection information, it can be combined with the current dummy packet mechanism.
  • the QoS monitoring defined in the 5G standard and the dummy message mechanism in the performance measurement function mechanism can be extended to support the transfer of connection information.
  • FIG 4 is a schematic diagram of the IPV6 packet header structure, including:
  • the version field is used to indicate that the IP datagram uses IPv6 protocol encapsulation, occupying 4 bits;
  • Traffic class The traffic class field is used to identify the traffic flow class corresponding to IPv6, or the priority level, similar to the ToS (Type of Service) field in IPv4;
  • the flow label field is a new field in the IPv6 datagram, which can be used to mark the data flow type of the packet, so as to distinguish different packets at the network layer.
  • the flow label field is allocated by the source node, and a communication flow can be uniquely identified by the triple method of flow label, source address, and destination address, instead of the five-tuple method (source address, destination address, source port, destination port and transport layer protocol number);
  • Payload length The payload length field identifies the total length of the payload part (including all extension header parts) in the IPv6 datagram in bytes, that is, other parts except the IPv6 basic header. total length;
  • next header field is used to identify the next header type of the current header (or extended header);
  • Hop limit is similar to the TTL field in IPv4 packets, which specifies the number of times the packet can be effectively forwarded. Every time the packet passes through a router node, the hop value is reduced by 1. When the value of this field is reduced to 0, the packet is directly discarded;
  • Source address (source IP address): The source IP address field identifies the IPv6 address of the source node sending the IPv6 message;
  • Destination IP address The destination IP address field identifies the IPv6 address of the receiving node of the IPv6 packet.
  • the IPV6 protocol is extended by the next header field mechanism.
  • the value of this field indicates the upper-layer protocol.
  • this field indicates the type of the next extension field. For the protocol number of the defined extension header, reference may be made to the relevant description in the current protocol, which is not repeated in this application.
  • One of the unused extension types can be selected to represent the source QoS information.
  • the currently undefined protocol number 143 can be used to represent the source QoS information.
  • the source QoS information can be carried in the IPV6 packet header.
  • the IPV6 packet header supports carrying source QoS information, which can be carried in two ways:
  • Porting mode 1 The IPV6 packet carries user packet data, and the source QoS extension field in the header contains connection information and packet information.
  • the source QoS information interface definition is similar to the IP extension mode 1, and will not be described again;
  • Porting mode 2 Two of the unused extension types can be selected to represent the source QoS information packet information and connection information respectively, for example, 143: the packet information in the source QoS information; 144: the connection information in the source QoS information.
  • the IPV6 packet carries user packet data
  • the header extension field protocol number is: 143, which only includes the packet information in the source QoS information
  • the IPV6 packet does not carry the user packet data, and the protocol number of the header extension field is: 144, which only contains the connection information in the source QoS information.
  • the source QoS information interface definition is similar to the IP extension mode 2, and details are not repeated here.
  • FIG. 5 is a schematic diagram of the structure of the RTP packet header, including:
  • Contributing source count 4bits, how many contributing source (CSRC) markers exist after the fixed header;
  • Payload type 7bits, marking the type of information carried by the RTP packet;
  • Sequence number 16bits, the sequence number is incremented by 1 after each RTP packet is sent, and the receiver can rearrange the order of the data packets according to the sequence number;
  • Timestamp 32bits, reflecting the sampling time of the first byte in the information packet carried by the RTP packet;
  • SSRC synchronization source
  • Active source list CSRC list 32bits, identifying the contributing data source.
  • the RTP protocol also allows extension by adding an extended header after the RTP fixed header. As long as the X field in the RTP header is set to 1, an extended header with a variable length can be added after the RTP header.
  • the format of the RTP extension header is shown in FIG. 6 , and FIG. 6 is a schematic diagram of the format of the RTP extension header.
  • Extension 2 The packet information is transmitted in the RTP header of the data packet, and the connection information is transmitted using the new RTP payload type.
  • the payload type in FIG. 5 represents the packet type or payload type of the RTP packet.
  • Trusted signature information can be carried by extending a new RTP packet type (PT).
  • the extension mode 2 is similar to the IP extension mode 2.
  • the new RTP payload type is similar to the dummy IP packet, which will not be repeated here.
  • the GTP protocol format is shown in Figure 7, which is a schematic diagram of the GTP protocol format, including:
  • Version number used to identify the version of the GTP protocol
  • Protocol type used to identify whether it is GTP (PT is 1) or GTP' (PT is 0).
  • GTP' is defined in 3GPP TS 32.295, and the meaning of the GTP' header is the same as that of the GTP header. The meaning is different;
  • Extension Header flag Used to indicate whether the Next Extension Header field is meaningful. When this bit is 0, the Next Extension Header either does not exist, or exists but is not used. When this bit is 1, the Next Extension Header field is to be interpreted and used;
  • Sequence number flag used to indicate whether the Sequence number field is meaningful. When this bit is 0, the Sequence number either does not exist, or exists but is not used. When this bit is 1, the Sequence number field is to be interpreted and used.
  • N-protocol data unit (PDU) flag (N-PDU Number flag, PN): used to indicate whether the N-PDU Number field is meaningful. When this bit is 0, the N-PDU Number either does not exist, or exists but is not used. When this bit is 1, the N-PDU Number field is to be interpreted and used.
  • PDU N-protocol data unit
  • Tunnel endpoint identifier When receiving the general packet radio service tunneling protocol-user plane (general packet radio service tunnelling protocol user, GTP-U) or the general packet radio service tunneling protocol-control plane (general packet radio service tunnelling protocol control, GTP-C) protocol entity defines a tunnel endpoint.
  • the receiver of the GTP tunnel defines a TEID locally, and this TEID is used by the sender.
  • Message Type defines the message types of GTP, including GTP-C and GTP-U.
  • the GTP-U protocol of the 3GPP specification clearly defines the extension header field in the GTP protocol.
  • QoS monitoring packet QoS monitoring packet
  • QMP QoS monitoring packet
  • SNP identification sequence number sequence number presence
  • PPP identification paging policy paging policy presence
  • PPI identification paging policy indicator paging policy indicator
  • RQI identification reflection QoS Indication reflective QoS indicator
  • downlink sending time stamp downlink Sending Time Stamp, DL Sending Time Stamp
  • DL QFI Sequence Number identifies the downlink QFI sequence number.
  • Uplink message (sent from RAN to UPF) GTP-U format:
  • DL Delay Ind. identifies downlink delay indicator (downlink delay indicator), uplink delay indicator (uplink delay indicator, UL Delay Ind.), DL Sending Time Stamp Repeated indicates that the downlink sending timestamp is repeated, DL Received Time Stamp indicates downlink Reception timestamp, UL Sending Time Stamp represents uplink reception timestamp, DL Delay Result represents downlink delay result, UL Delay Result represents uplink delay result, and UL QFI Sequence Number identifies the uplink QFI sequence number.
  • the GTP-U protocol can be extended as follows to support carrying source QoS information.
  • Uplink message (sent from RAN to UPF) GTP-U format:
  • the source QoS information can be carried in the header of the GTP-U packet.
  • GTP-U packet header After the GTP-U packet header supports carrying source QoS information, it can be used in two ways:
  • GTP-U packets carry user packet data
  • the source QoS information field in the header contains connection information and packet information.
  • the source QoS information interface definition is similar to the IP extension mode 1.
  • GTP-U packets carry user packet data, and the source QoS information field in the header only contains packet information;
  • GTP-U packets do not carry user packet data, and the source QoS information field in the header only contains connection information.
  • Method 5 The new transmission protocol extension.
  • protocol number 143 can be defined as a new transmission protocol, which supports carrying source QoS information.
  • Source Port The port of the application on the sending computer that transmits the message using the new transport protocol.
  • Destination Port The port of the application on the receiving end computer that uses the new transport protocol to receive data.
  • Header length The header length of the new transport protocol message.
  • Check value This field occupies 16 bits, which can check whether the source QoS information and user data are damaged during transmission.
  • Source QoS Information Fill in the source QoS content. Content-length is "header-length-8"
  • PayloadType which indicates whether it is a data message or a connection indication message
  • the packet information is sent with the data message
  • the connection information is sent with the connection indication message.
  • the application layer After the packet transmission protocol is extended to support carrying source QoS information, the application layer also needs to indicate the source QoS information when sending data. Generally, the transmission protocol processing layer fills in the source QoS information into the IP packet that is finally sent to the transmission network.
  • the application layer uses IP extension to carry source QoS information.
  • the first parameter specifies the sender's socket descriptor
  • the second parameter specifies a buffer that stores the data to be sent by the application
  • the third parameter specifies the number of bytes of data to be sent
  • the fourth parameter is generally set 0.
  • Send_sqos function can be added:
  • the newly added sQoS information is a memory pointer where the source QoS information is stored, and the parameter structure is similar to that of the source QoS information definition in the protocol extension, and will not be repeated here.
  • the application layer can use the send_sqos function to send data and indicate the source QoS information of the data.
  • the source QoS information can be packaged into the extension field of the IP header.
  • the application layer uses the RTP extension to carry the source QoS information.
  • RTP libraries When performing real-time transmission programming on the Linux platform, some open source RTP libraries, such as JLIBRTP, are generally used.
  • the RTP data sending function in JRTPLIB is:
  • Send_sqos function can be added:
  • the newly added sQoS information is a memory pointer where the source QoS information is stored, and the parameter structure is similar to that of the source QoS information definition in the protocol extension, and will not be repeated here.
  • the application layer can use the SendPacketSQoS function to send data and indicate the source QoS information of the data.
  • the source QoS information can be packaged into the extension field of the RTP header.
  • the first source QoS information included in the above-mentioned first packet #1 is used to indicate that the first packet #1 is mapped to the first quality of service flow QoS flow
  • the second packet The second source QoS information included in #1 is used to indicate that the second packet is mapped to the second QoS flow, and the first QoS flow and the second QoS flow belong to one QoS flow group.
  • At least one message in the connection including multiple messages is mapped to at least one QoS flow, wherein at least one QoS flow belongs to a QoS flow group, and the first QoS flow is the same as the first QoS flow in the QoS flow group.
  • the QoS flow corresponding to the message #1, and the second QoS flow is the QoS flow corresponding to the second message #1 in the QoS flow group.
  • packets of one connection can be mapped to different QoS flows.
  • this application can make related extensions to the current 5G QoS flow model.
  • the current 5G QoS flow model is shown in (a) in Figure 8, and (a) in Figure 8 is a schematic diagram of a 5G QoS flow model.
  • QoS flow group QoS flow group, QFG
  • QFG QoS flow group
  • FIG. 8 A schematic diagram of a QoS flow model. Specifically, the model of QoS flow shown in (b) in Figure 8 is described as follows:
  • a QFG can contain multiple QoS flows, and a QoS flow can only belong to one QFG;
  • the QFG supports the aggregate maximum bit rate (AMBR) parameter, which can perform overall flow control on all non-GRB QoS flows in the QFG, improving the ability to manage and control connections.
  • AMBR aggregate maximum bit rate
  • the above-mentioned QFG configuration includes one or more of the following:
  • QFG identifier/index QoS flow group identifier, QFGI: used to identify the QFG;
  • QoS flow (involved QoS flow) included in the QFG: used to indicate which QoS flows are included in the QFG;
  • At least one CQI used to indicate which CQIs the QFG can be mapped with;
  • AMBR used to indicate the maximum bandwidth of QoS flows of all non-GRB types in the QFG.
  • the QFG configuration can be delivered through the control plane.
  • the UPF can map the connection-level QoS characteristics to the QFG, and map the packets to the specific QoS flow under the QFG according to the packet-level QoS characteristics.
  • the first source QoS information included in the first packet #1 is used to indicate that the first packet #1 is mapped to the first 5QI
  • the first source QoS information included in the second packet #1 The two-source QoS information is used to indicate that the second packet is mapped to the second 5QI, and the first 5QI and the second 5QI belong to one QoS flow.
  • At least one message in the connection including multiple messages is respectively mapped to at least one 5QI, wherein at least one 5QI belongs to a QoS flow, and the first 5QI is the same as the first message #1 in the QoS flow.
  • the corresponding 5QI, the second 5QI is the 5QI corresponding to the second packet #1 in the QoS flow.
  • FIG. 8 is a schematic diagram of another QoS flow model provided by the embodiment of the present application. Specifically, the model of QoS flow shown in (c) in FIG. 8 is described as follows:
  • a QoS flow can contain multiple 5QIs
  • a connected packet can only be mapped to different 5QIs within a QoS flow
  • QoS flow supports AMBR parameters, which can perform overall flow control on all packets whose 5QI is non-GRB in QoS flow, improving the ability to manage and control connections.
  • the 5QI field needs to be added to the extension header field of the transmission protocol. It is mapped to the QFI according to the QoS characteristics of the connection level, and further mapped to the specific 5QI under the QFI according to the QoS characteristics of the packet level.
  • the QoS configuration of the QoS flow includes one or more of the following:
  • Allocation and retention priority (allocation and retention Priority, ARP);
  • AMBR 5QI maximum bandwidth of all non-GRB types under QoS flow.
  • the 5G QoS Group is defined as:
  • Reflective QoS attribute (RQA), 5QI-specific parameter of non-GRB type
  • 5G control plane network elements AMF and SMF can send packet filtering rules to UE and UPF.
  • the following parameters can be added to the packet filters set:
  • the packet can be accurately mapped to the corresponding QoS flow based on the source QoS information in the received IP packet.
  • CQI and PQI in the packet filters set is optional. If there is no CQI and/or PQI, use the QoS features corresponding to the CQI and PQI to compare with the QoS features of the 5QI in the QoS flow, and select the most matching 5QI.
  • the first packet #1 is sent to the core network device (for example, UPF) through the N6 interface, and the method flow shown in (a) in FIG. 2 further includes:
  • the data network sends the first packet #1 to the core network device.
  • the following description takes the core network device as the UPF as an example for description.
  • the UPF maps the first packet #1 to the first QoS flow #1, and the method flow shown in (a) in FIG. 2 further includes:
  • the UPF maps the first packet #1 to the first QoS flow #1.
  • the packet information and connection information included in the source QoS information are carried in the first packet #1, and the UPF maps the IP packet to the QoS according to the source QoS information in the first packet #1.
  • the UPF maps the IP packet to the QoS according to the source QoS information in the first packet #1.
  • the packet information included in the source QoS information is carried in the first packet #1, and the connection information included in the source QoS information is carried in the dummy IP packet.
  • the source QoS information in the dummy IP packet maps the IP packet to the first QoS flow#1 with the closest QoS characteristics;
  • the packet information included in the source QoS information is carried in the first packet #1, and the connection information included in the source QoS information is transmitted via the control plane, and the UPF transmits the information according to the first packet #1 and the control plane.
  • the source QoS information of the IP packet is mapped to the first QoS flow #1 with the closest QoS characteristics.
  • UPF maps IP packets to the first QoS flow#1 in any of the following ways:
  • mapping is performed according to CQI; if PQI is used in source QoS information to identify QoS requirements, and the packet filters set received by UPF contains If the PQI parameter is included, the mapping is performed according to the PQI; or
  • CQI is used to identify QoS requirements in the source QoS information, and the packet filters set received by UPF does not contain CQI, the QoS characteristics corresponding to CQI are used to compare with the QoS characteristics of 5QI in each QoS flow, and the most matching one can be selected;
  • the source QoS information uses the PQI to identify the QoS requirements, and the packet filters set received by the UPF does not contain the PQI, then use the QoS characteristics corresponding to the PQI to compare with the QoS characteristics of the 5QIs in each QoS flow, and select the most matching one; or
  • the source QoS information directly carries specific QoS feature information (for example, carries connection QoS feature information and/or packet QoS feature information), then use the carried QoS feature information to compare with the QoS features of 5QI in each QoS flow, and select the best match is sufficient; or
  • the source QoS information does not carry packet-level QoS characteristics (eg, PQI and/or packet QoS characteristics information) but carries connection-level QoS characteristics (eg, CQI and/or connection QoS characteristics information)
  • the connection-level QoS characteristics eg, CQI and/or connection QoS characteristics information
  • the method flow shown in (a) in Figure 2 also includes:
  • the UPF determines the third packet #1.
  • the UPF processes the first packet #1 based on the first QoS flow #1 to obtain the third packet #1.
  • the third packet #1 includes the information that needs to be transmitted in the first packet #1, but the packet format is converted from the packet format of the first packet #1 that satisfies the transmission of the N6 interface to the one that meets the transmission of the N3 interface. message format.
  • UPF reserves internal forwarding resources (buffer queues, scheduling time slices, etc.) based on the average rate, frequency, peak frequency, and peak size in the connection information to improve the QoS achievement rate.
  • the PQI of the I-frame message is high-level QoS (packet loss rate 0.01%), and the PQI of the P-frame message is medium-level QoS (packet loss rate 1%).
  • UPF puts I-frame data in the high-priority forwarding queue and P-frame data in the medium-priority forwarding queue.
  • I-frame data packets are sent preferentially.
  • UPF can calculate that simply forwarding burst data and current concurrent connection data will lead to an instantaneous traffic peak, exceeding the processing and caching capabilities of back-end transmission equipment (such as RAN), resulting in packet loss.
  • UPF can perform peak shift shaping according to the source QoS information in the packets.
  • the UPF uses uniform and complete data segment transmission to send packets with high latency requirements first, and then send packets with low latency requirements. message to reduce the impact on the downstream.
  • the method flow shown in 2(a) further includes:
  • the UPF sends a third packet #1 to the access network device.
  • the UPF encapsulates the first packet #1 and the source QoS information into the GTP-U protocol format and forwards it to the N3 port, including:
  • the UPF fills in the QFI of the first QoS flow#1 into the GTP-U protocol header.
  • the UPF copies the packet information and connection information in the first packet #1 to the extension field of the GTP-U protocol header as described in the previous GTP protocol extension, which will not be repeated here.
  • the dummy IP packet on the N6 port is converted into a dummy IP packet based on the GTP-U protocol on the N3 port and sent.
  • the RAN side needs to process the received third packet #1 to obtain a fourth packet #1 that needs to be sent to the UE.
  • the fourth packet #1 includes the third packet #1
  • the message format is converted from the message format of the third message #1 that satisfies the N3 interface transmission to the message format that satisfies the air interface transmission.
  • the method flow shown in (a) in Figure 2 also includes:
  • the RAN determines the fourth packet #1.
  • the RAN side After receiving the third packet #1 of the N3 port, the RAN side obtains the connection information and/or packet information of the third packet #1 from the GTP extension header field, and combines the QoS flow to which the packet belongs to conduct pertinence. Guarantee and forwarding processing (such as complete data segment scheduling, etc.), send the processed fourth packet #1 to the UE through the air interface.
  • Guarantee and forwarding processing such as complete data segment scheduling, etc.
  • the method flow shown in (a) in Figure 2 also includes:
  • the RAN sends a fourth packet #1 to the UE.
  • steps S230 to S280 illustrate the transmission process of the downlink packet as an example of the downlink transmission of the first packet #1.
  • Other packets in the downlink transmission connection (for example, the above-mentioned second packet #1 ) is similar to the downlink transmission of the first packet #1, and will not be repeated here.
  • the process shown in (a) in FIG. 2 is a schematic flowchart of the method for transmitting a packet provided by the embodiment of the present application in a downlink scenario.
  • FIG. 2 is a schematic flowchart of another method for transmitting a message provided by an embodiment of the present application.
  • the method for transmitting a message includes at least some of the following steps.
  • the UE generates a first packet #2.
  • the application on the UE generates the first packet #2 according to the QoS requirements of the service.
  • the first packet #2 generated by the UE is similar to the first packet #1 generated by the above-mentioned DN, and reference is made to the relevant description in the above-mentioned S210, which will not be repeated here.
  • the above-mentioned first packet #2 may be any one of multiple packets generated by the UE.
  • the quintuple information of the multiple packets is the same, and it can be understood that the multiple packets belong to a connection.
  • Each of the multiple packets includes source QoS parameters, and the source QoS information included in each packet is used to ensure QoS for the corresponding packet, and the source QoS information included in the multiple packets Are not the same.
  • the UE may also generate a second message #2 among the multiple messages in the connection, and the method flow shown in (b) in FIG. 2 further includes:
  • the UE generates a second packet #2.
  • the second packet #2 generated by the UE is similar to the second packet #1 generated by the above-mentioned DN. Reference is made to the relevant description in the above-mentioned S220, and details are not repeated here.
  • the method flow shown in (b) in Figure 2 also includes:
  • the UE maps the first packet #2 to the first QoS flow #2.
  • the packet information and connection information included in the source QoS information are carried in the first packet #2, and the UE maps the IP packet to the QoS feature according to the source QoS information in the first packet #2 On the closest first QoS fow#2;
  • the packet information included in the source QoS information is carried in the first packet #2, and the connection information included in the source QoS information is carried in the dummy IP packet.
  • the source QoS information in the IP packet maps the IP packet to the first QoS flow#2 with the closest QoS characteristics;
  • the packet information included in the source QoS information is carried in the first packet #2, the connection information included in the source QoS information is transmitted via the control plane, and the UE transmits the information according to the first packet #2 and the control plane.
  • the UE maps the first packet #2 to the first QoS flow #2 in any of the following ways:
  • the mapping is performed according to the CQI; if the source QoS information uses the PQI to identify the QoS requirements, and the packet filters set received by the UE contains The PQI parameter is mapped according to the PQI; or
  • CQI CQI is used to identify the QoS requirements in the source QoS information, and the packet filters set received by the UE does not contain CQI, the QoS characteristics corresponding to CQI are used to compare with the QoS characteristics of 5QI in each QoS flow, and the most matching one can be selected;
  • the source QoS information uses PQI to identify the QoS requirements, and the packet filters set received by the UE does not contain PQI, then use the QoS characteristics corresponding to the PQI to compare with the QoS characteristics of the 5QIs in each QoS flow, and select the most matching one; or
  • the source QoS information directly carries specific QoS feature information (for example, carrying connection QoS feature information and/or packet QoS feature information), then use the carried QoS feature information to compare with the QoS features of 5QI in each QoS flow, and select the best match is sufficient; or
  • connection-level QoS feature is used as the packet QoS feature to identify the QoS requirements of the packet, and mapping is performed according to the connection-level QoS feature.
  • the UE After the UE completes the mapping, it performs targeted guarantee and forwarding processing according to the QoS requirements of the first QoS flow #2 matched by the IP message. Send the first packet #2 to the RAN, and the method flow shown in (b) in FIG. 2 further includes:
  • the UE sends a first packet #2 to the RAN.
  • the bottom layer of the UE uses the air interface transmission protocol to encapsulate the user plane IP packet, and fills the QFI of the first QoS flow #2 matching the packet into the air interface packet header.
  • the bottom layer of the UE performs targeted guarantee and forwarding processing (such as complete data segment scheduling, etc.)
  • the first packet #2 is mapped to DRBs of different bearer standards and sent to the RAN.
  • the PQI of the I-frame message is high-level QoS (packet loss rate 0.01%), and the PQI of the P-frame message is medium-level QoS (packet loss rate 1%).
  • the bottom layer of the UE matches the data packet of the I frame to the high-level DRB bearer (such as supporting retransmission and redundancy), and matches the data packet of the P frame to the medium-level DRB bearer (no retransmission, no redundancy) ;
  • the bottom layer of the UE after receiving all the packets of a video frame, sends it to the RAN through the air interface at one time, reducing the overall transmission delay of the data segment and improving the air interface utilization rate;
  • connection information indicates that 3M bytes of data that has an emergency after 10ms needs to be sent, and the bottom layer of the UE negotiates with the base station in advance to allocate air interface transmission resources after 10ms according to the instruction.
  • the bottom layer of the UE receives the emergency data, it can immediately use the pre-applied air interface resources for transmission, which reduces the transmission delay and improves the utilization efficiency of the air interface resources.
  • the RAN side needs to process the received first packet #2 to obtain a third packet #2 that needs to be sent to the UPF.
  • the third packet #2 includes the first packet #2.
  • the message format is converted from the message format of the first message #2 that satisfies the air interface transmission to the message format that satisfies the N3 interface transmission.
  • the method flow shown in (b) in Figure 2 also includes:
  • the RAN determines the third packet #2.
  • the RAN After the RAN receives the message sent by the UE, it encapsulates the user plane IP message with the GTP-U protocol, and parses the air interface packet header to obtain the QFI of the first QoS flow #2 to which the message belongs, and fills in the GTU-U protocol header field. Then the third packet #2 is sent to the UPF through the N3 interface.
  • the method flow shown in (b) in Figure 2 also includes:
  • the RAN sends a third packet #2 to the UPF.
  • the UPF side needs to process the received third packet #2 to obtain a fourth packet #2 that needs to be sent to the data network.
  • the fourth packet #2 includes the third packet # 2, but the message format is converted from the message format of the third message #2 that satisfies the transmission of the N6 interface to the message format that satisfies the transmission of the N6 interface.
  • the method flow shown in (b) in Figure 2 also includes:
  • the UPF determines the fourth packet #2.
  • the UPF side After receiving the third packet #2 of the N3 port, the UPF side obtains the connection information and packet information of the data packet from the extension field of the IP packet on the user plane, and combines the first QoS flow #2 to which the packet belongs to ensure targeted protection.
  • the fourth packet #2 is determined with forwarding processing (such as complete data segment scheduling, etc.), and the fourth packet #2 is sent to the Internet through the N6 interface.
  • the method flow shown in Figure 2(b) also includes:
  • the UPF sends a fourth packet #2 to the data network.
  • steps S231 to S281 illustrate the transmission process of the uplink packet as an example of the downlink transmission of the first packet #2.
  • Other packets in the uplink transmission connection (for example, the above-mentioned second packet #2 ) is similar to the uplink transmission of the first packet #2, and details are not repeated here.
  • the message generating end carries the source QoS information in the message when generating the message.
  • This application provides a possibility The implementation of the method, the packet generation device does not need to carry the source QoS information when generating the packet, and the transmission node identifies some data features and maps them to the source QoS information.
  • the nodes on the transmission path can identify some data features by themselves through technologies such as traffic analysis, packet parsing, or intelligent perception, and map them to the source QoS
  • the information is filled in the message and sent to the back-end device to ensure QoS.
  • RAN or UPF can perceive the period information of I frames and P frames in the video stream based on traffic analysis, map the period information of I frames and P frames to source QoS information, fill in the packets and send them to the back-end device .
  • FIG. 9 is a schematic flowchart of a reflective QoS mechanism provided by an embodiment of the present application.
  • the reflective QoS mechanism includes at least some of the following steps.
  • the core network device sends the connection-level QoS feature and/or the packet-level QoS feature to the access network device.
  • the core network device for example, UPF
  • the GTP-U protocol for example, UPF
  • the extension field of the GTP-U header carries the CQI and/or the packet's CQI and/or PQI information.
  • the core network device may also send the connection-level QoS features and/or the packet-level QoS features to the access network device in other manners, which will not be illustrated here.
  • connection-level QoS feature may also be connection QoS feature information
  • packet-level QoS feature may also be packet QoS feature information
  • the access network device needs to send the received connection-level QoS features and/or packet-level QoS features to the user equipment, and the method flow shown in FIG. 9 further includes:
  • the access network device sends the connection-level QoS feature and/or the packet-level QoS feature to the user equipment.
  • the access network device uses the air interface protocol stack to encapsulate the user plane IP packet, and sends it to the user equipment.
  • the RDI field in the SDAP protocol header of the air interface protocol stack is filled with 1, indicating that the user equipment triggers QoS reflection processing.
  • the QFI field in the SDAP protocol header of the air interface protocol stack is filled with the CQI parsed from the GTP-U protocol.
  • the PQI extension field of the SDAP protocol header of the air interface protocol stack is filled with the PQI parsed from the GTP-U protocol.
  • SDAP protocol header extension mode 1 directly add a byte extension field.
  • SDAP protocol header extension mode 2 To ensure compatibility, an optional field of 2 bytes is added. When the QFI is all 0 or all 1, it means that there is an extension field. Fill in the real QFI in the extension field of the first byte; fill in the PQI in the extension field of the second byte.
  • the access network device may also send the connection-level QoS feature and/or the packet-level QoS feature to the user equipment in other manners, which will not be illustrated here one by one.
  • connection-level QoS characteristics and/or the packet-level QoS characteristics When the user equipment receives the connection-level QoS characteristics and/or the packet-level QoS characteristics, it may record the connection-level QoS characteristics and/or the packet-level QoS characteristics.
  • the method flow shown in Figure 9 also includes:
  • the user equipment records the connection-level QoS characteristics and/or the packet-level QoS characteristics.
  • the user equipment finds that the RDI indication is 1, and records the mapping relationship between the quintuple, CQI, QFI information, PQI and DRB as the QoS rules learned through the reflective QoS mechanism (currently the reflective QoS mechanism only Record the packet quintuple, QFI information, and DRB mapping).
  • the user equipment can send packets through the learned QoS rules, and the method flow shown in FIG. 9 further includes:
  • the user equipment sends a packet to the access network device.
  • the user equipment when it sends an uplink packet, it can use the QoS rules of the PQI information learned through the reflection QoS mechanism to match, and match the packet to the appropriate QoS flow and DRB for sending.
  • the PQI in the QoS feature of the uplink message to be sent by the user equipment can find the corresponding PQI#1 in the PQI recorded by the UE, then the user equipment can find the corresponding PQI#1 in the QoS feature of the uplink message to be sent in the PQI#1. It is sent on the flow and the DRB, wherein the PQI#1 may be the same PQI as the PQI in the QoS feature of the uplink message to be sent, or the closest PQI.
  • the present application also provides a QoS flow policy micro-adjustment control scheme, which can dynamically adjust the resources corresponding to the QoS flow, specifically by enhancing the QoS configuration of the QoS flow.
  • the QoS configuration of the QoS flow in this embodiment includes one or more of the following:
  • Allocation and retention priority (allocation and retention Priority, ARP);
  • MGFBR represents the maximum guaranteed bandwidth in the micro-control mode, that is, through the micro-control mode, the guaranteed bandwidth of the resources reserved for the QoS flow is less than or equal to (or less than) the dynamic change between MGFBRs.
  • the QoS configuration of the QoS flow in this embodiment includes one or more of the following:
  • Allocation and retention priority (allocation and retention Priority, ARP);
  • Maximum guaranteed bandwidth (maximum guaranteed flow bit rate MGFBR, MGFBR);
  • MGFBR represents the maximum guaranteed bandwidth in the micro-control mode, that is, through the micro-control mode, the actual guaranteed bandwidth of the resources reserved for the QoS flow can be dynamically changed between GFBR and MGFBR.
  • the GFBR is used to adjust the resources reserved for the QoS flow, and the guaranteed bandwidth of the QoS flow is greater than or equal to the GFBR and less than or equal to the MGFBR.
  • the sum of the average rate of the connection and the actual rate of the current GFBR is not greater than the MGFBR, sufficient bandwidth resources are reserved for the connection, and the current actual rate of the GFBR is refreshed to be the sum of the average rate of the new connection and the actual rate of the current GFBR;
  • the processing strategy is similar.
  • the UPF and/or the RAN may add the forwarding node identifier, the forwarding interface bandwidth reservation success mark, and the information such as the currently reserved bandwidth of the forwarding node in the source QoS information of the packet or in the Dummy IP packet, sending and receiving both ends at the same time. and other transport nodes in the network.
  • the present application also provides another QoS flow policy fine-tuning control scheme, which can dynamically indicate whether to reserve resources corresponding to QoS flow, specifically by enhancing the QoS configuration of QoS flow.
  • Allocation and retention priority (allocation and retention Priority, ARP);
  • Maximum guaranteed bandwidth (maximum guaranteed flow bit rate MGFBR, MGFBR);
  • the indication information is used to indicate whether to reserve the resource corresponding to the QoS flow.
  • the indication information can be dynamic creation indication (DCI), DCI indicates whether UFP and/or RAN will reserve the resources corresponding to the QoS flow after receiving the configuration of the QoS flow (or whether to create the QoS flow by default). corresponding instance) instance.
  • the default value is true (TRUE), which supports the QoS flow dynamically created by the micro-control mode, and the DCI is set to false (FALSE).
  • the indication information is referred to as DCI only by way of example, and does not constitute any limitation on the protection scope of the present application, and may be referred to as other names.
  • the UPF and/or RAN actively create an instance for the QoS flow indicated by the DCI as True; and do not create an instance for the QoS flow indicated by the DCI as FALSE.
  • UPF and/or RAN When UPF and/or RAN receives an IP packet, it first determines whether the IP packet can be mapped to an existing non-default QoS flow instance; Whether the packet can be mapped to a QoS flow that is not instantiated in the QoS configuration and whose DCI is FALSE, if so, instantiate the QoS flow and use the QoS flow to forward the packet; if not, use the default QoS flow to forward the packet. The message is forwarded.
  • each transmission node or forwarding device is not responsible for the end-to-end QoS achievement, but only tries its best to ensure pertinence during processing and forwarding according to the packet QoS instruction.
  • it can only be solved by the fault-tolerant mechanism at both ends of the transceiver.
  • the transmission node can combine the end-to-end transmission network damage model and the network state prediction technology to improve the end-to-end QoS achievement rate through the active guarantee mechanism:
  • the transit node when a transit node senses that the back-end network has periodic and occasional packet loss due to interference, the transit node actively uses the repeated transmission of packets within the interference period for the packets that are expected to fail to achieve the end-to-end delay target due to interference. , stagger the interference cycle retransmission and other mechanisms to reduce the transmission delay (compared to the confirmation retransmission mechanism at both ends of the transceiver), and improve the end-to-end QoS achievement rate;
  • a transmission node senses that the packet loss rate of the back-end network can no longer meet the end-to-end packet error rate target, and actively uses the FEC redundancy encoding method to improve the data packet loss resistance and improve the end-to-end QoS. Rate.
  • the UPF implements the safeguard mechanism described above.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. . And it may not be necessary to perform all the operations in the above method embodiments.
  • the user equipment and/or network equipment in the above method embodiments may perform some or all of the steps in the embodiments, these steps or operations are only examples, and the embodiments of the present application may also include performing other operations or variations of various operations .
  • the method implemented by the user equipment may also be implemented by a component (such as a chip or circuit, etc.) that can be used in the user equipment, and the method implemented by the network device may also be implemented by the network device. component implementation.
  • FIG. 10 is a schematic diagram of an apparatus 1000 for transmitting a message provided by the present application.
  • the apparatus 1000 includes a processing unit 1010 , a receiving unit 1020 and a sending unit 1030 .
  • the processing unit 1010 is configured to generate multiple packets, the quintuple information of the multiple packets is the same, each packet in the multiple packets includes source quality of service QoS information, and the source The QoS information is used to ensure QoS for the corresponding packets, and the source QoS information included in the multiple packets is different.
  • the sending unit 1030 is configured to send the multiple packets.
  • the apparatus 1000 corresponds to the user equipment or the data network in the method embodiment, and is configured to generate a packet.
  • the apparatus 1000 may be user equipment or a data network in the method embodiment, or a chip or functional module inside the user equipment or data network in the method embodiment.
  • Corresponding units of the apparatus 1000 are configured to perform the corresponding steps performed by the user equipment or the data network in the method embodiment shown in FIG. 2(a) and FIG. 2(b) and FIG. 9 .
  • the processing unit 1010 in the apparatus 1000 is configured to execute the steps related to processing corresponding to the user equipment or the data network in the method embodiment.
  • the receiving unit 1020 in the apparatus 1000 performs the steps of receiving by the user equipment or the data network in the method embodiment.
  • the sending unit 1030 in the apparatus 1000 is configured to perform the step of sending the user equipment or the data network.
  • the receiving unit 1020 and the transmitting unit can form a transceiver unit, and have the functions of receiving and transmitting at the same time.
  • the processing unit 1010 may be at least one processor.
  • the sending unit may be a transmitter or an interface circuit
  • the receiving unit 1020 may be a receiver or an interface circuit.
  • the receiver and transmitter can be integrated together to form a transceiver or interface circuit.
  • the apparatus 1000 may further include a storage unit for storing data and/or signaling.
  • the processing unit 1010, the sending unit and the receiving unit 1020 may interact or couple with the storage unit, such as reading or calling the storage unit.
  • the data and/or signaling in the unit so that the methods of the above-mentioned embodiments are performed.
  • the above units may exist independently, or may be integrated in whole or in part.
  • FIG. 11 is a schematic structural diagram of a message generating device 1100 applicable to an embodiment of the present application, which can be used to implement the function of a data network in the above-mentioned downlink message transmission scenario, or can also be used to implement the above-mentioned uplink message transmission The capabilities of the user device in the scene.
  • the message generating device 1100 includes a processor 1101, a memory 1102 and a transceiver 1103, wherein the memory 1102 stores instructions or programs, and the processor 1102 and the transceiver 1103 are used to execute or call the instructions or programs stored in the memory 1102 to
  • the message generating device 1100 is made to realize the function of the message generating device in the above method for transmitting a message.
  • the transceiver 1103 is used to perform the operations performed by the sending unit 1030 and the receiving unit 1020 in the embodiment shown in FIG. 10
  • the processor 1102 is used to perform the implementation shown in FIG. 10 .
  • the operations performed by the processing unit 1010 in the example.
  • FIG. 11 only shows one memory and a processor. In an actual user equipment, there may be multiple processors and memories.
  • the memory may also be referred to as a storage medium or a storage device, etc., which is not limited in this embodiment of the present application.
  • FIG. 12 is a schematic diagram of another apparatus 1200 for transmitting a message provided by the present application.
  • the apparatus 1200 includes a receiving unit 1210 , a sending unit 1220 and a processing unit 1230 .
  • a receiving unit 1210 configured to receive multiple packets, where the quintuple information of the multiple packets is the same, each packet in the multiple packets includes source quality of service QoS information, and the source The QoS information is used to ensure QoS for the corresponding QoS packets, and the source QoS information included in the multiple packets is different.
  • the processing unit 1230 is configured to process the multiple packets based on the source QoS information included in the multiple packets.
  • the apparatus 1200 corresponds to a core network device (for example, UPF) or an access network device in the method embodiment, and the apparatus 1200 may be the UPF or the access network device in the method embodiment, or the UPF or the access network device in the method embodiment A chip or functional module inside the device.
  • Corresponding units of the apparatus 1200 are configured to perform the corresponding steps performed by the UPF or the access network device in the method embodiment shown in FIG. 2 (a) and FIG. 2 (b) and the method embodiment shown in FIG. 9 .
  • the sending unit 1220 in the apparatus 1200 performs the step of sending the UPF or the access network device in the method embodiment
  • the receiving unit 1210 in the apparatus 1200 is configured to perform the step of receiving the UPF or the access network device
  • the apparatus 1200 may further include a processing unit 1230, which is used to execute corresponding processing-related steps inside the UPF or the access network device.
  • the apparatus 1200 may further include a storage unit for storing data and/or signaling.
  • the processing unit 1230, the obtaining unit 1220, and the receiving unit 1210 may interact or couple with the storage unit, for example, read or call the data in the storage unit. data and/or signaling so that the methods of the above-described embodiments are performed.
  • the above units may exist independently, or may be integrated in whole or in part.
  • FIG. 13 is a schematic structural diagram of a packet receiving device 1300 applicable to the embodiment of the present application, which can be used to implement the functions of the core network device, the access network device, and the user equipment in the above-mentioned downlink packet transmission scenario, or further It can be used to realize the functions of the core network device, the access network device and the data network in the above uplink message transmission scenario.
  • the message receiving device 1300 includes a processor 1301, a memory 1302 and a transceiver 1303, wherein the memory 1302 stores instructions or programs, and the processor 1302 and the transceiver 1303 are used to execute or call the instructions or programs stored in the memory 1302 to
  • the message receiving device 1300 is made to implement the function of the message receiving device in the above method for transmitting a message.
  • the transceiver 1303 is used to perform the operations performed by the sending unit 1220 and the receiving unit 1210 in the embodiment shown in FIG. 12
  • the processor 1302 is used to perform the implementation shown in FIG. 12 .
  • the operations performed by the processing unit 1230 in the example.
  • An embodiment of the present application further provides a communication system, which includes the foregoing message generating device and message receiving device.
  • the present application also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the computer is made to execute the above-mentioned (a) in FIG. 2 and in FIG. 2 . (b) and various steps performed by the user equipment in the method shown in FIG. 9 .
  • the present application also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the computer is made to execute the above-mentioned (a) in FIG. 2 and in FIG. 2 . (b) and each step performed by the access network device in the method shown in FIG. 9 .
  • the present application also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the computer is made to execute the above-mentioned (a) in FIG. 2 and in FIG. 2 . (b) and each step performed by the core network device in the method shown in FIG. 9 .
  • the present application also provides a computer program product containing instructions, when the computer program product is run on a computer, the computer program product causes the computer to execute as shown in FIG. 2(a) and FIG. 2(b) and FIG. 9 . Each step performed by the user equipment in the method.
  • the present application also provides a computer program product containing instructions, when the computer program product is run on a computer, the computer program product causes the computer to execute as shown in FIG. 2(a) and FIG. 2(b) and FIG. 9 . Each step performed by the access network device in the method.
  • the present application also provides a computer program product containing instructions, when the computer program product is run on a computer, the computer program product causes the computer to execute as shown in FIG. 2(a) and FIG. 2(b) and FIG. 9 . Each step performed by the core network device in the method.
  • the present application also provides a chip including a processor.
  • the processor is configured to read and run the computer program stored in the memory, so as to execute the corresponding operations and/or processes performed by the user equipment in the method for transmitting a message provided in this application.
  • the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory.
  • the chip further includes a communication interface, and the processor is connected to the communication interface.
  • the communication interface is used to receive processed data and/or information, and the processor acquires the data and/or information from the communication interface and processes the data and/or information.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, and the like.
  • the processor may also be embodied as processing circuitry or logic circuitry.
  • the present application also provides a chip including a processor.
  • the processor is configured to read and run the computer program stored in the memory, so as to execute the corresponding operations and/or processes performed by the access network device in the method for transmitting a message provided by this application.
  • the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory.
  • the chip further includes a communication interface, and the processor is connected to the communication interface.
  • the communication interface is used to receive processed data and/or information, and the processor acquires the data and/or information from the communication interface and processes the data and/or information.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, and the like.
  • the processor may also be embodied as a processing circuit or a logic circuit.
  • the present application also provides a chip including a processor.
  • the processor is configured to read and run the computer program stored in the memory, so as to execute the corresponding operations and/or processes performed by the core network device in the method for transmitting a message provided by the present application.
  • the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory.
  • the chip further includes a communication interface, and the processor is connected to the communication interface.
  • the communication interface is used to receive processed data and/or information, and the processor acquires the data and/or information from the communication interface and processes the data and/or information.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, and the like.
  • the processor may also be embodied as a processing circuit or a logic circuit.
  • the above-mentioned chip can also be replaced by a chip system, which will not be repeated here.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual conditions to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .
  • the term "and/or” in this application is only an association relationship to describe associated objects, which means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, and A and B exist at the same time. , there are three cases of B alone.
  • the character "/" in this document generally indicates that the contextual object is an "or” relationship; the term “at least one” in this application can mean “one” and "two or more", for example, A At least one of , B, and C can mean: A alone exists, B exists alone, C exists alone, A and B exist simultaneously, A and C exist simultaneously, C and B exist simultaneously, and A and B and C exist simultaneously. seven situations.

Abstract

本申请提供了一种传输报文的方法与装置，包括：生成多个报文，发送该多个报文。具体地，该多个报文的五元组信息相同，该多个报文中的每个报文包括源服务质量QoS信息，该每个报文包括的源QoS信息用于对其所对应的QoS报文进行QoS保障，该多个报文包括的源QoS信息不相同，使得传输网络可以针对每个报文提供QoS保障。

Description

传输报文的方法和装置
本申请要求于2021年01月06日提交中国专利局、申请号为202110014125.X、申请名称为“传输报文的方法和装置”的中国专利申请的优先权和于2021年02月10日提交中国专利局、申请号为202110181698.1、申请名称为“传输报文的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且，更具体地，涉及传输报文的方法和装置。
背景技术
随着通信技术的发展，目前的通信系统具有更高的传输速率、更灵活的带宽配置，全互联网协议(internet protocol，IP)化、扁平化的网络架构，可以提供多样化的多媒体业务，因此需要端到端的服务质量(quality of service，QoS)机制来保证不同业务的服务质量。
国际互联网工程任务组(the internet engineering task force，IETF)定义了三种QoS服务模型：尽力而为服务模型(best-effort service)、综合服务模型(integrated service，IntServ)和区分服务模型(differentiated service，DiffServ)。第三代合作伙伴项目(the 3rd Generation partnership project，3GPP)版本16(release 16，R16)中，提出QoS流(flow)机制，QoS flow是第五代(5th generation，5G)核心网与无线接入网的最小QoS控制粒度，每个QoS flow都有对应的QoS配置，QoS配置里的参数描述了具体的QoS要求。
无论是上述的IETF QoS服务模型，还是QoS flow机制，都是传输网络中的转发节点在转发报文时，根据报文的网络层特征将报文匹配到与QoS flow对应的预置的QoS策略，并按QoS策略进行差异化保障处理的模式。现有QoS机制下，传输网络无法更准确的QoS保障与优化。
发明内容
本申请提供一种传输报文的方法，通过在五元组信息相同的不同报文中携带不同的源QoS信息，使得传输网络可以针对报文提供QoS保障，从而提高传输网络进行QoS保障与优化的准确度。
第一方面，提供了一种传输报文的方法，该传输报文的方法可以由报文生成设备执行，或者，也可以由设置于报文生成设备中的芯片或电路执行，本申请对此不作限定。
该传输报文的方法包括：
生成多个报文，该多个报文的五元组信息相同，该多个报文中的每个报文包括源服务质量QoS信息，该每个报文包括的源QoS信息用于对其所对应的QoS报文进行QoS保障，该多个报文包括的源QoS信息不相同；发送该多个报文。
或者可以说，
该传输报文的方法包括：
生成多个报文，该多个报文具有相同的五元组信息，该多个报文具有不同的源服务质量QoS信息，该源QoS信息用于对其对应的报文进行QoS保障；发送该多个报文。
本申请实施例提供的传输报文的方法，报文生成设备生成的报文中包括用于为该报文提供QoS保障的源QoS信息，并且五元组信息相同中的不同报文可以包括不同的源QoS信息，使得该报文的传输网络可以针对报文提供QoS保障，从而提高传输网络进行QoS保障与优化的准确度。
为了便于描述，下文中将五元组信息相同的多个报文称为一个连接中的报文。结合第一方面，在第一方面的某些实现方式中，该多个报文属于同一个连接，该多个报文包括的源QoS信息不相同包括：该连接中的第一报文中包括的第一源QoS信息和该连接中的第二报文中包括的第二源QoS信息不同，其中，该第一报文和该第二报文为该多个报文中的任意两个报文。
或者说，
该生成多个报文，该多个报文具有相同的五元组信息，该多个报文具有不同的源QoS信息，该源QoS信息用于对其对应的报文进行QoS保障，包括：生成第一报文和第二报文，该第一报文的五元组信息和该第二报文的五元组信息相同，该第一报文包括的第一源QoS信息和该第二报文包括的第二源QoS信息不同，该第一源QoS信息用于对该第一报文进行QoS保障，该第二源QoS信息用于对第二报文进行QoS保障。
进一步地，该多个报文属于同一个连接。
具体地，连接中的不同报文中包括的源QoS信息不同可以是连接中任意两个报文中分别包括的QoS信息不同。
结合第一方面，在第一方面的某些实现方式中，该第一源QoS信息包括第一QoS特征和第一数据特征，该第一QoS特征用于指示第一报文的QoS需求，该第一数据特征表示第一报文的传输特性，该第二源QoS信息包括第二QoS特征和第二数据特征，该第二QoS特征用于指示该第二报文的QoS需求，该第二数据特征表示该第二报文的传输特性。
具体地，某个报文中包括的源QoS信息还可以包括QoS特征和数据特征，应用可以清晰、详尽的将应用层数据特征与QoS要求指示给传输网络，进一步提高传输网络进行QoS保障与优化的准确度。
结合第一方面，在第一方面的某些实现方式中，该多个报文包括的源QoS信息不相同包括：该多个报文包括的数据特征不同，和/或，该多个报文包括的QoS特征不同。例如，该连接中的第一报文中包括的第一源QoS信息和该连接中的第二报文中包括的第二源QoS信息不同包括：该第一数据特征和该第二数据特征不同，和/或，该第一QoS特征和该第二QoS特征不同。
连接中某两个报文中分别包括的源QoS信息不同可以是源QoS信息中包括的数据特征，和/或，源QoS信息中包括的QoS特征不同，增加方案的灵活性。
结合第一方面，在第一方面的某些实现方式中，该第一数据特征包括连接级别的数据特征和/或包级别的数据特征，其中，该连接级别的数据特征用于指示该连接中包括的多个报文的传输特性，该包级别的数据特征表示该第一报文的传输特性，该QoS特征包括 连接级别的QoS特征和/或包级别的QoS特征，其中，该连接级别的QoS特征用于指示该连接中包括的多个报文的QoS需求，该包级别的QoS特征用于指示该第一报文的QoS需求。
具体地，某个报文中包括的源QoS信息中的数据特征可以是连接级别的数据特征指示包含该报文的连接的传输特性，还可以是包级别的数据特征指示该报文的传输特性；同理，QoS特征可以是连接级别的QoS特征指示包含该报文的连接的QoS需求，还可以是包级别的QoS特征指示该报文的QoS需求。提供源QoS信息不同可能的粒度，从而增加方案的灵活性。
结合第一方面，在第一方面的某些实现方式中，该连接级别的数据特征包括以下一项或者多项：平均速率、持续时长、频率、大小、时延预算、波峰频率、波峰大小、波峰时延预算、波峰发送时间、突发事件类型、预计突发事件发生时间、预计突发事件报文量和突发事件报文时延预算，其中，该平均速率指示该连接中的报文平均发送速率、该持续时长指示该连接持续时长，该频率指示报文发送频率、该大小指示每频次发送报文均值、该时延预算指示一个周期内所有报文全部传递到接收端耗时预算、该波峰频率指示报文的波峰产生频率、该波峰时延预算指示报文波峰全部传递到接收端耗时预算、该波峰发送时间指示该报文波峰发送的时间、该突发事件类型指示突然发生的时间所属的类别、该预计突发事件发生时间指示突发事件报文预计到达时间、该预计突发事件报文量指示突然事件传输的报文量、该突发事件报文时延预算指示突发事件报文全部传输到接收端耗时预算。
结合第一方面，在第一方面的某些实现方式中，该包级别的数据特征包括以下一项或者多项：数据块序号、数据块大小、包位置和数据块时延预算，其中，该数据块序号指示该第一报文所属数据块编号、数据块大小指示该第一报文所属数据块大小、该包位置指示该第一报文在所属数据块的位置、该数据块时延预算指示该第一报文传输到接收端耗时预算。
上述源QoS信息中包括的数据特征可以针对不同的报文有不同的实现方式，增加方案的灵活性。
结合第一方面，在第一方面的某些实现方式中，该连接级别的QoS特征包括连接QoS特征指示(connection QoS characteristics indicator，CQI)和/或连接QoS特征信息，该包级别的QoS特征包括包QoS指示(packet QoS characteristics indicator，PQI)和/或包QoS特征信息。
连接级别的QoS特征和包级别的QoS特征可以有不同的体现形式，增加方案的灵活性。
结合第一方面，在第一方面的某些实现方式中，该连接级别的QoS特征或包级别的QoS特征表示的QoS特征包括以下一项或者多项：资源类型、优先级、时延预算和错误率。
上述源QoS信息中包括的QoS特征可以针对不同的报文有不同的实现方式，增加方案的灵活性。
结合第一方面，在第一方面的某些实现方式中，该第一报文中包括第一源QoS信息包括：连该第一报文中包括接级别的信息和包级别的信息；或者，该第一报文中包括该包级别的信息，虚拟互联网协议(dummy Internet protocol，dummy IP)包中包括该连接级别 的信息；或者，该第一报文中包括该包级别的信息，该连接级别的信息通过控制面传输，其中，该连接级别的信息包括该连接级别的数据特征和该连接级别的QoS特征，该包级别的信息包括该包级别的接数据特征和该包级别的QoS特征。
本申请实施例提供的传输报文的方法，报文中携带源QoS信息可以有不同的实现方式，提高方案的灵活性。
结合第一方面，在第一方面的某些实现方式中，该第一源QoS信息用于指示将该第一报文映射到第一服务质量流QoS flow，该第二源QoS信息用于指示将该第二报文映射到第二QoS flow，该第一QoS flow和该第二QoS flow属于一个QoS flow组。
或者，
结合第一方面，在第一方面的某些实现方式中，该第一源QoS信息用于指示将该第一报文映射到第一5G网络的服务质量标识符(5G quality of service identifier，5QI)，该第二源QoS信息用于指示将该第二报文映射到第二5QI，该第一5QI和该第二5QI属于一个QoS flow。
本申请实施例提供的传输报文的方法，还提供一种QoS流模型，某个连接包含的不同的报文映射的不同的QoS flow属于同一个QoS flow组，或者，某个连接包含的不同的报文映射的不同的5QI属于一个QoS flow，可以提升对连接的管控力度。
结合第一方面，在第一方面的某些实现方式中，第一源QoS信息用于指示将第一报文映射到第一服务质量流QoS flow，该第一QoS flow的QoS配置包括：最大保障带宽(maximum guaranteed flow bit rate，MGFBR)；该MGFBR用于调整为该第一QoS flow预留的资源，该第一QoS flow的保障带宽小于或者等于该MGFBR，其中，该第一报文为该多个报文中的任意一个，该第一源QoS信息为该第一报文中包括的源QoS信息。或者，
结合第一方面，在第一方面的某些实现方式中，该第一QoS flow的QoS配置还包括：最小保障带宽(guaranteed flow bit rate，GFBR)，该GFBR用于调整为该第一QoS flow预留的资源，该第一QoS flow的保障带宽大于或者等于该GFBR且小于或者等于该MGFBR。
本申请实施例提供的传输报文的方法，可以通过在QoS flow的QoS配置中增加参数MGFBR，可以微调整为QoS flow预留的资源。
结合第一方面，在第一方面的某些实现方式中，第一源QoS信息用于指示将该第一报文映射到第一服务质量流QoS flow，该第一QoS flow的QoS配置包括：指示信息，该指示信息用于指示是否预留该第一QoS flow对应的资源，其中，该第一报文为该多个报文中的任意一个，该第一源QoS信息为该第一报文中包括的源QoS信息。
本申请实施例提供的传输报文的方法，可以通过在QoS flow的QoS配置中增加指示信息，指示是否预留QoS flow对应的资源，避免目前宏控制模式下，QoS策略变化决策和执行链长，变更耗时的缺点。
结合第一方面，在第一方面的某些实现方式中，该第一源QoS信息用于指示将该第一报文映射到第一服务质量流QoS flow包括：该第一源QoS信息中包括QoS特征，该QoS特征与该第一QoS flow中的5QI指示的QoS特征相对应。
具体地，本申请实施例提供的传输报文的方法应用于QoS flow映射时，可以通过与5QI相映射兼容目前中的QoS机制，提高方案的兼容性。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：确定传输该第一报文的路径中传输节点的状态；当至少一个该输节点的状态满足预设条件时，启动主动保障机制。
结合第一方面，在第一方面的某些实现方式中，该当至少一个该输节点的状态满足预设条件时，启动主动保障机制包括以下一项或者多项：当该至少一个该输节点存在丢包时，重复发送该第一报文；或者当该至少一个该输节点丢包率大于预设值时，采用前向纠错前向纠错(forward error correction，FEC)冗余编码方式编码该第一报文。
本申请实施例提供的传输报文的方法，还提供一种主动保障机制，当感知到后端的传输节点满足预设条件(例如，因干扰存在周期性偶发性丢包、丢包率已经无法满足端到端包错误率目标)，启动主动保障机制，提高报文传输的性能。
另外，需要说明的是，本申请实施例中报文生成设备生成的报文中不包括上述的源QoS信息的场景下，报文传输网络中的传输节点可能识别出部分数据特征，并映射为源QoS信息，将源QoS信息传输给其他的传输节点。
第二方面，提供了一种传输报文的方法，该传输报文的方法可以由报文接收设备执行，或者，也可以由设置于报文接收设备中的芯片或电路执行，本申请对此不作限定。
该传输报文的方法包括：
接收多个报文，该多个报文的五元组信息相同，该多个报文中的每个报文包括源服务质量QoS信息，该每个报文包括的源QoS信息用于对其所对应的QoS报文进行QoS保障，该多个报文包括的源QoS信息不相同；基于该多个报文包括的源QoS信息处理该多个报文。
或者可以说，该传输报文的方法包括：
接收多个报文，该多个报文具有相同的五元组信息，该多个报文具有不同的源服务质量QoS信息，该源QoS信息用于对其对应的报文进行QoS保障；基于该多个报文包括的源QoS信息处理该多个报文。
本申请实施例提供的传输报文的方法，报文接收设备接收到的报文中包括用于为该报文提供QoS保障的源QoS信息，并且连接中的不同报文可以包括不同的源QoS信息，使得该报文的传输网络可以针对报文提供QoS保障，从而提高传输网络进行QoS保障与优化的准确度。
结合第二方面，在第二方面的某些实现方式中，该多个报文属于同一个连接，该多个报文包括的源QoS信息不相同包括：该连接中的第一报文中包括的第一源QoS信息和该连接中的第二报文中包括的第二源QoS信息不同，其中，该第一报文和该第二报文为该多个报文中的任意两个报文。
或者说，接收多个报文，该多个报文具有相同的五元组信息，该多个报文具有不同的源服务质量QoS信息，该源QoS信息用于对其对应的报文进行QoS保障该包括：接收第一报文和第二报文，该第一报文的五元组信息和该第二报文的五元组信息相同，该第一报文包括的第一源QoS信息和该第二报文包括的第二源QoS信息不同，该第一源QoS信息用于对该第一报文进行QoS保障，该第二源QoS信息用于对第二报文进行QoS保障。
进一步地，该多个报文属于同一个连接。
具体地，连接中的不同报文中包括的源QoS信息不同可以是连接中任意两个报文中 分别包括的QoS信息不同。
结合第二方面，在第二方面的某些实现方式中，该第一源QoS信息包括第一数据特征和第一QoS特征，该第二源QoS信息包括第二QoS特征和第二数据特征，该第二数据特征表示该第二报文的传输特性，该方法还包括：根据该第一QoS特征确定第一报文的QoS需求；根据该第二QoS特征确定该第二报文的QoS需求；基于该多个报文包括的源QoS信息处理该多个报文包括：根据该第一报文的QoS需求和该第一数据特征调度该第一报文的资源；根据该第二报文的QoS需求和该第二数据特征调度该第二报文的资源。
进一步地，本申请实施例提供的传输报文的方法接收报文的设备能够根据源QoS信息中包括的QoS特征和数据特征进行资源调度。
结合第二方面，在第二方面的某些实现方式中，该多个报文包括的源QoS信息不相同包括：该多个报文包括的QoS特征不同，和/或，该多个报文包括的数据特征不同。例如，该连接中的第一报文中包括的第一源QoS信息和该连接中的第二报文中包括的第二源QoS信息不同包括：该第一数据特征和该第二数据特征不同，和/或，该第一QoS特征和该第二QoS特征不同。
连接中某两个报文中分别包括的源QoS信息不同可以是源QoS信息中包括的数据特征，和/或，源QoS信息中包括的QoS特征不同，增加方案的灵活性。
结合第二方面，在第二方面的某些实现方式中，根据该QoS需求和该数据特征调度报文的资源包括：根据不同的QoS特征为不同的报文调度不同的资源。例如，该调度该第一报文的资源和该调度该第二报文的资源不同。
本申请实施例提供的传输报文的方法接收报文的设备能够为连接中的不同报文调度不同的资源，提高调度的准确性。
结合第二方面，在第二方面的某些实现方式中，该第一数据特征包括连接级别的数据特征和/或包级别的数据特征，该方法还包括：根据该连接级别的数据特征确定该连接中包括的多个报文的传输特性；根据该包级别的数据特征确定该第一报文的传输特性；
结合第二方面，在第二方面的某些实现方式中，该第一QoS特征包括连接级别的QoS特征和/或包级别的QoS特征，该方法还包括：根据该连接级别的QoS特征确定该连接中其他报文的QoS需求，该其他报文可以是未包括包级别的QoS特征的报文；例如，根据该连接级别的QoS特征确定该连接中第三报文的QoS需求，该第三报文中包括第三源QoS信息，该第三源QoS信息中包括的第三QoS特征可以未包括包级别的QoS特征。
根据该包级别的QoS特征确定该第一报文的QoS需求。
具体地，报文中包括的源QoS信息中的数据特征可以是连接级别的数据特征指示包含该报文的连接的传输特性，还可以是包级别的数据特征指示该报文的传输特性；同理，QoS特征可以是连接级别的QoS特征指示包含该报文的连接的QoS需求，还可以是包级别的QoS特征指示该报文的QoS需求。提供源QoS信息不同可能的粒度，从而增加方案的灵活性。
结合第二方面，在第二方面的某些实现方式中，该连接级别的数据特征包括以下一项或者多项：平均速率、持续时长、频率、大小、时延预算、波峰频率、波峰大小、波峰时延预算、波峰发送时间、突发事件类型、预计突发事件发生时间、预计突发事件报文量和突发事件报文时延预算，其中，该平均速率指示该连接中的报文平均发送速率、该持续时 长指示该连接持续时长，该频率指示报文发送频率、该大小指示每频次发送报文均值、该时延预算指示一个周期内所有报文全部传递到接收端耗时预算、该波峰频率指示报文的波峰产生频率、该波峰时延预算指示报文波峰全部传递到接收端耗时预算、该波峰发送时间指示该报文波峰发送的时间、该突发事件类型指示突然发生的时间所属的类别、该预计突发事件发生时间指示突发事件报文预计到达时间、该预计突发事件报文量指示突然事件传输的报文量、该突发事件报文时延预算指示突发事件报文全部传输到接收端耗时预算。
结合第二方面，在第二方面的某些实现方式中，该包级别的数据特征包括以下一项或者多项：数据块序号、数据块大小、包位置和数据块时延预算，其中，该数据块序号指示该第一报文所属数据块编号、数据块大小指示该第一报文所属数据块大小、该包位置指示该第一报文在所属数据块的位置、该数据块时延预算指示该第一报文传输到接收端耗时预算。
上述源QoS信息中包括的数据特征可以针对不同的报文有不同的实现方式，增加方案的灵活性。
结合第二方面，在第二方面的某些实现方式中，该连接级别的QoS特征包括连接QoS特征指示CQI和/或连接QoS特征信息，该包级别的QoS特征包括包QoS指示PQI和/或包QoS特征信息。
连接级别的QoS特征和包级别的QoS特征可以有不同的体现形式，增加方案的灵活性。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：接收来自核心网设备的包过滤规则，该包过滤规则中包括该CQI和/或该PQI；根据该CQI和/或该PQI将该第一报文映射至第一服务质量流QoS flow。
本申请实施例提供的传输报文的方法，核心网设备可以将增强的包过滤规则发送给报文接收备(例如，用户面网元)，使得后续进行QoS流映射时，能够基于报文的QoS特征进行。
需要说明的是，本申请中涉及的“增强的包过滤规则”指的是相比于目前的包过滤规则而言，具有更多的配置参数的包过滤规则。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：接收反射触发指示(reflective QoS flow to DRB mapping indication，RDI)和该PQI；根据该RDI记录该PQI，该PQI用于指示将第四报文映射至第三QoS flow；其中，该第四报文为待发送的报文，该第三QoS flow中的5QI指示的QoS特征与该PQI相对应。
本申请实施例提供的传输报文的方法，还提供一种反射增强的方法，使得基于反射QoS方案进行QoS流映射时更为精确。
结合第二方面，在第二方面的某些实现方式中，该连接级别的QoS特征或包级别的QoS特征表示的QoS特征包括以下一项或者多项：资源类型、优先级、时延预算和错误率。
上述源QoS信息中包括的QoS特征可以针对不同的报文有不同的实现方式，增加方案的灵活性。
结合第二方面，在第二方面的某些实现方式中，该第一报文中包括第一源QoS信息包括：该第一报文中包括连接级别的信息和包级别的信息；或者，该第一报文中包括该包 级别的信息，虚拟互联网协议dummy IP包中包括该连接级别的信息；或者，该第一报文中包括该包级别的信息，该连接级别的信息通过控制面传输，其中，该连接级别的信息包括该连接级别的数据特征和该连接级别的QoS特征，该包级别的信息包括该包级别的接数据特征和该包级别的QoS特征。
本申请实施例提供的传输报文的方法，报文中携带源QoS信息可以有不同的实现方式，提高方案的灵活性。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：根据该第一源QoS信息将该第一报文映射到第一服务质量流QoS flow；根据该第二源QoS信息将该第二报文映射到第二QoS flow；其中，该第一QoS flow和该第二QoS flow属于一个QoS flow组。
或者，该方法还包括：根据该第一源QoS信息将该第一报文映射到第一5G网络的服务质量标识符5QI；根据该第二源QoS信息将该第二报文映射到第二5QI；其中，该第一5QI和该第二5QI属于一个QoS flow。
本申请实施例提供的传输报文的方法，还提供一种QoS flow模型，某个连接包含的不同的报文映射的不同的QoS flow属于同一个QoS flow组，或者，某个连接包含的不同的报文映射的不同的5QI属于一个QoS flow，可以提升对连接的管控力度。
结合第二方面，在第二方面的某些实现方式中，根据该第一源QoS信息将该第一报文映射到第一QoS flow包括：根据该第一源QoS信息中包括的第一QoS特征从多个QoS flow中确定该第一QoS flow，其中，该第一源QoS信息中包括的第一QoS特征与该第一QoS flow中的5QI指示的QoS特征相对应。
具体地，本申请实施例提供的传输报文的方法应用于QoS flow映射时，可以通过与5QI相映射兼容目前中的QoS机制，提高方案的兼容性。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：调整为该第一QoS flow预留的资源。
结合第二方面，在第二方面的某些实现方式中，该第一QoS flow的QoS配置包括：最大保障带宽MGFBR；该调整为该第一QoS flow预留的资源包括：确定该第一QoS flow的保障带宽小于或者等于该MGFBR。
结合第二方面，在第二方面的某些实现方式中，该第一QoS flow的QoS配置还包括：最小保障带宽GFBR；该调整为该第一QoS flow预留的资源包括：确定该第一QoS flow的保障带宽大于或者等于该GFBR且小于或者等于该MGFBR。
本申请实施例提供的传输报文的方法，可以通过在QoS flow的QoS配置中增加参数MGFBR，可以微调整为QoS flow预留的资源。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：确定是否预留该第一QoS flow对应的资源。
结合第二方面，在第二方面的某些实现方式中，该第一QoS flow的QoS配置包括：指示信息，该指示信息用于指示是否预留该第一QoS flow对应的资源；该确定是否预留该第一QoS flow对应的资源包括：根据该指示信息确定是否预留该第一QoS flow对应的资源。
本申请实施例提供的传输报文的方法，可以通过在QoS flow的QoS配置中增加指示信息，指示是否预留QoS flow对应的资源，避免目前宏控制模式下，QoS策略变化决策 和执行链长，变更耗时的缺点。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该第一源QoS信息为接收到的，或者，该第一源QoS信息为本地生成的；当该第一源QoS信息为本地生成时，该方法还包括：将该第一源QoS信息填入该第一报文中。
结合第二方面，在第二方面的某些实现方式中，生成该第一源QoS信息包括：通过流量分析和/或报文解析确定该第一源QoS信息。
本申请实施例中报文生成设备生成的报文中不包括上述的源QoS信息的场景下，报文传输网络中的传输节点可能识别出部分数据特征，并映射为源QoS信息，将源QoS信息传输给其他的传输节点。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：确定传输该第一报文的路径中传输节点的状态；当至少一个该输节点的状态满足预设条件时，启动主动保障机制。
结合第二方面，在第二方面的某些实现方式中，该当至少一个该输节点的状态满足预设条件时，启动主动保障机制包括以下一项或者多项：当该至少一个该输节点存在丢包时，重复发送该第一报文；或者当该至少一个该输节点丢包率大于预设值时，采用前向纠错FEC冗余编码方式编码该第一报文。
本申请实施例提供的传输报文的方法，还提供一种主动保障机制，当感知到后端的传输节点满足预设条件(例如，因干扰存在周期性偶发性丢包、丢包率已经无法满足端到端包错误率目标)，启动主动保障机制，提高报文传输的性能。
第三方面，提供一种传输报文的装置，包括：
处理单元，用于生成多个报文，该多个报文的五元组信息相同，该多个报文中的每个报文包括源服务质量QoS信息，该每个报文包括的源QoS信息用于对其所对应的报文进行QoS保障，该多个报文包括的源QoS信息不相同；
发送单元，用于发送该多个报文。
或者说，该传输报文的装置，包括：
处理单元，用于生成多个报文，该多个报文具有相同的五元组信息，该多个报文具有不同的源服务质量QoS信息，该源QoS信息用于对其对应的报文进行QoS保障；
发送单元，用于发送该多个报文。
结合第三方面，在第三方面的某些实现方式中，该多个报文属于同一个连接，该多个报文包括的源QoS信息不相同包括：该连接中的第一报文中包括的第一源QoS信息和该连接中的第二报文中包括的第二源QoS信息不同，其中，该第一报文和该第二报文为该多个报文中的任意两个报文。
或者可以理解为，该处理单元生成多个报文，该多个报文具有相同的五元组信息，该多个报文具有不同的源QoS信息，该源QoS信息用于对其对应的报文进行QoS保障，包括：
处理单元生成第一报文和第二报文，该第一报文的五元组信息和该第二报文的五元组信息相同，该第一报文包括的第一源QoS信息和该第二报文包括的第二源QoS信息不同，该第一源QoS信息用于对该第一报文进行QoS保障，该第二源QoS信息用于对第二报文进行QoS保障。
进一步地，该多个报文属于同一个连接。
结合第三方面，在第三方面的某些实现方式中，该第一源QoS信息包括第一QoS特征和第一数据特征，该第一QoS特征用于指示该第一报文的QoS需求，该第一数据特征表示该第一报文的传输特性，该第二源QoS信息包括第二QoS特征和第二数据特征，该第二QoS特征用于指示该第二报文的QoS需求，该第二数据特征表示该第二报文的传输特性。
结合第三方面，在第三方面的某些实现方式中，该连接中的第一报文中包括的第一源QoS信息和该连接中的第二报文中包括的第二源QoS信息不同包括：该第一数据特征和该第二数据特征不同，和/或，该第一QoS特征和该第二QoS特征不同。
结合第三方面，在第三方面的某些实现方式中，该第一数据特征包括连接级别的数据特征和/或包级别的数据特征，其中，该连接级别的数据特征表示该连接中包括的多个报文的传输特性，该包级别的数据特征表示该第一报文的传输特性，该第一QoS特征包括连接级别的QoS特征和/或包级别的QoS特征，其中，该连接级别的QoS特征用于指示该连接中包括的多个报文的QoS需求，该包级别的QoS特征用于指示该第一报文的QoS需求。
结合第三方面，在第三方面的某些实现方式中，该连接级别的数据特征包括以下一项或者多项：平均速率、持续时长、频率、大小、时延预算、波峰频率、波峰大小、波峰时延预算、波峰发送时间、突发事件类型、预计突发事件发生时间、预计突发事件报文量和突发事件报文时延预算，其中，该平均速率指示该连接中的报文平均发送速率、该持续时长指示该连接持续时长，该频率指示报文发送频率、该大小指示每频次发送报文均值、该时延预算指示一个周期内所有报文全部传递到接收端耗时预算、该波峰频率指示报文的波峰产生频率、该波峰时延预算指示报文波峰全部传递到接收端耗时预算、该波峰发送时间指示该报文波峰发送的时间、该突发事件类型指示突然发生的时间所属的类别、该预计突发事件发生时间指示突发事件报文预计到达时间、该预计突发事件报文量指示突然事件传输的报文量、该突发事件报文时延预算指示突发事件报文全部传输到接收端耗时预算。
结合第三方面，在第三方面的某些实现方式中，该包级别的数据特征包括以下一项或者多项：数据块序号、数据块大小、包位置和数据块时延预算，其中，该数据块序号指示该第一报文所属数据块编号、数据块大小指示该第一报文所属数据块大小、该包位置指示该第一报文在所属数据块的位置、该数据块时延预算指示该第一报文传输到接收端耗时预算。
结合第三方面，在第三方面的某些实现方式中，该连接级别的QoS特征包括连接QoS特征指示CQI和/或连接QoS特征信息，该包级别的QoS特征包括包QoS指示PQI和/或包QoS特征信息。
结合第三方面，在第三方面的某些实现方式中，该连接级别的QoS特征信息或包级别的QoS特征信息表示的QoS特征包括以下一项或者多项：资源类型、优先级、时延预算和错误率。
结合第三方面，在第三方面的某些实现方式中，该第一报文中包括第一源QoS信息包括：该第一报文中包括连接级别的信息和包级别的信息；或者，该第一报文中包括该包级别的信息，虚拟互联网协议dummy IP包中包括该连接级别的信息；或者，该第一报文 中包括该包级别的信息，该连接级别的信息通过控制面传输，其中，该连接级别的信息包括该连接级别的数据特征和该连接级别的QoS特征，该包级别的信息包括该包级别的接数据特征和该包级别的QoS特征。
结合第三方面，在第三方面的某些实现方式中，该第一源QoS信息用于指示将该第一报文映射到第一服务质量流QoS flow，该第二源QoS信息用于指示将该第二报文映射到第二QoS flow，该第一QoS flow和该第二QoS flow属于一个QoS flow组。
结合第三方面，在第三方面的某些实现方式中，该第一源QoS信息用于指示将该第一报文映射到第一5G网络的服务质量标识符5QI，该第二源QoS信息用于指示将该第二报文映射到第二5QI，该第一5QI和该第二5QI属于一个QoS flow。
结合第三方面，在第三方面的某些实现方式中，该第一源QoS信息用于指示将该第一报文映射到第一服务质量流QoS flow，该第一QoS flow的QoS配置包括：最大保障带宽MGFBR；该MGFBR用于调整为该第一QoS flow预留的资源，该第一QoS flow的保障带宽小于或者等于该MGFBR。
结合第三方面，在第三方面的某些实现方式中，该第一QoS flow的QoS配置还包括：最小保障带宽GFBR，该GFBR用于调整为该第一QoS flow预留的资源，该第一QoS flow的保障带宽大于或者等于该GFBR且小于或者等于该MGFBR。
结合第三方面，在第三方面的某些实现方式中，该第一源QoS信息用于指示将该第一报文映射到第一服务质量流QoS flow，该第一QoS flow的QoS配置包括：指示信息，该指示信息用于指示是否预留该第一QoS flow对应的资源。
结合第三方面，在第三方面的某些实现方式中，该第一源QoS信息用于指示将该第一报文映射到第一QoS flow包括：该第一源QoS信息中包括QoS特征，该QoS特征与该QoS flow中的5QI指示的QoS特征相对应。
结合第三方面，在第三方面的某些实现方式中，该处理单元还用于确定传输该第一报文的路径中传输节点的状态；当至少一个该输节点的状态满足预设条件时，该处理单元还用于启动主动保障机制。
结合第三方面，在第三方面的某些实现方式中，该当至少一个该输节点的状态满足预设条件时，该处理单元还用于启动主动保障机制包括以下一项或者多项：当该至少一个该输节点存在丢包时，该处理单元还用于确定重复发送该第一报文；或者当该至少一个该输节点丢包率大于预设值时，该处理单元还用于确定采用前向纠错FEC冗余编码方式编码该第一报文。
第四方面，提供一种传输报文的装置，该传输报文的装置包括：
接收单元，用于接收多个报文，该多个报文的五元组信息相同，该多个报文中的每个报文包括源服务质量QoS信息，该每个报文包括的源QoS信息用于对其所对应的QoS报文进行QoS保障，该多个报文包括的源QoS信息不相同；处理单元，用于基于该多个报文包括的源QoS信息处理该多个报文。
或者说，该传输报文的装置，包括：
接收单元，用于接收多个报文，该多个报文具有相同的五元组信息，该多个报文具有不同的源服务质量QoS信息，该源QoS信息用于对其对应的报文进行QoS保障；处理单元，用于基于该多个报文包括的源QoS信息处理该多个报文。
结合第四方面，在第四方面的某些实现方式中，该多个报文属于同一个连接，该多个报文包括的源QoS信息不相同包括：该连接中的第一报文中包括的第一源QoS信息和该连接中的第二报文中包括的第二源QoS信息不同，其中，该第一报文和该第二报文为该多个报文中的任意两个报文。
或者可以理解为，该接收单元接收多个报文，该多个报文具有相同的五元组信息，该多个报文具有不同的源服务质量QoS信息，该源QoS信息用于对其对应的报文进行QoS保障该包括：接收单元接收第一报文和第二报文，该第一报文的五元组信息和该第二报文的五元组信息相同，该第一报文包括的第一源QoS信息和该第二报文包括的第二源QoS信息不同，该第一源QoS信息用于对该第一报文进行QoS保障，该第二源QoS信息用于对第二报文进行QoS保障。
进一步地，该多个报文属于同一个连接。
结合第四方面，在第四方面的某些实现方式中，该第一源QoS信息包括第一QoS特征和第一数据特征，该第一数据特征表示该第一报文的传输特性，该第二源QoS信息包括第二QoS特征和第二数据特征，该第二数据特征表示该第二报文的传输特性，该处理单元还用于：根据该第一QoS特征确定该第一报文的QoS需求；根据该第二QoS特征确定该第二报文的QoS需求；该处理单元基于该多个报文包括的源QoS信息处理该多个报文包括：根据该第一报文的QoS需求和该第一数据特征调度该第一报文的资源；根据该第二报文的QoS需求和该第二数据特征调度该第二报文的资源。
结合第四方面，在第四方面的某些实现方式中，该连接中的第一报文中包括的第一源QoS信息和该连接中的第二报文中包括的第二源QoS信息不同包括：该第一数据特征和该第二数据特征不同，和/或，该第一QoS特征和该第二QoS特征不同。
结合第四方面，在第四方面的某些实现方式中，该调度该第一报文的资源和该调度该第二报文的资源不同。
结合第四方面，在第四方面的某些实现方式中，该第一数据特征包括连接级别的数据特征和/或包级别的数据特征，该处理单元还用于：根据该连接级别的数据特征确定该连接中包括的多个报文的传输特性；根据该包级别的数据特征确定该第一报文的传输特性。
结合第四方面，在第四方面的某些实现方式中，该第一QoS特征包括连接级别的QoS特征，该处理单元还用于：根据该连接级别的QoS特征确定该连接中该多个报文中除该第一报文和该第二报文之外的第三报文的QoS需求。
结合第四方面，在第四方面的某些实现方式中，该连接级别的数据特征包括以下一项或者多项：平均速率、持续时长、频率、大小、时延预算、波峰频率、波峰大小、波峰时延预算、波峰发送时间、突发事件类型、预计突发事件发生时间、预计突发事件报文量和突发事件报文时延预算，其中，该平均速率指示该连接中的报文平均发送速率、该持续时长指示该连接持续时长，该频率指示报文发送频率、该大小指示每频次发送报文均值、该时延预算指示一个周期内所有报文全部传递到接收端耗时预算、该波峰频率指示报文的波峰产生频率、该波峰时延预算指示报文波峰全部传递到接收端耗时预算、该波峰发送时间指示该报文波峰发送的时间、该突发事件类型指示突然发生的时间所属的类别、该预计突发事件发生时间指示突发事件报文预计到达时间、该预计突发事件报文量指示突然事件传输的报文量、该突发事件报文时延预算指示突发事件报文全部传输到接收端耗时预算。
结合第四方面，在第四方面的某些实现方式中，该包级别的数据特征包括以下一项或者多项：数据块序号、数据块大小、包位置和数据块时延预算，其中，该数据块序号指示该第一报文所属数据块编号、数据块大小指示该第一报文所属数据块大小、该包位置指示该第一报文在所属数据块的位置、该数据块时延预算指示该第一报文传输到接收端耗时预算。
结合第四方面，在第四方面的某些实现方式中，该连接级别的QoS特征包括连接QoS特征指示CQI和/或连接QoS特征信息，该包级别的QoS特征包括包QoS指示PQI和/或包QoS特征信息。
结合第四方面，在第四方面的某些实现方式中，该接收单元还用于接收来自核心网设备的包过滤规则，该包过滤规则中包括该CQI和/或该PQI；该处理单元还用于根据该CQI和/或该PQI将该第一报文映射至第一服务质量流QoS flow。
结合第四方面，在第四方面的某些实现方式中，该接收单元还用于接收反射触发指示RDI和该PQI；该处理单元还用于根据该RDI记录该PQI，该PQI用于指示将第四报文映射至第三QoS flow；其中，该第四报文为待发送的报文，该第三QoS flow中的5QI指示的QoS特征与该PQI相对应。
结合第四方面，在第四方面的某些实现方式中，该连接级别的QoS特征或包级别的QoS特征表示的QoS特征包括以下一项或者多项：资源类型、优先级、时延预算和错误率。
结合第四方面，在第四方面的某些实现方式中，该第一报文中包括第一源QoS信息包括：该第一报文中包括连接级别的信息和包级别的信息；或者，该第一报文中包括该包级别的信息，虚拟互联网协议dummy IP包中包括该连接级别的信息；或者，该第一报文中包括该包级别的信息，该连接级别的信息通过控制面传输，其中，该连接级别的信息包括该连接级别的数据特征和该连接级别的QoS特征，该包级别的信息包括该包级别的接数据特征和该包级别的QoS特征。
结合第四方面，在第四方面的某些实现方式中，该处理单元还用于：根据该第一源QoS信息将该第一报文映射到第一服务质量流QoS flow；根据该第二源QoS信息将该第二报文映射到第二QoS flow；其中，该第一QoS flow和该第二QoS flow属于一个QoS flow组。
结合第四方面，在第四方面的某些实现方式中，该处理单元还用于：根据该第一源QoS信息将该第一报文映射到第一5G网络的服务质量标识符5QI；根据该第二源QoS信息将该第二报文映射到第二5QI；其中，该第一5QI和该第二5QI属于一个QoS flow。
结合第四方面，在第四方面的某些实现方式中，该处理单元根据该第一源QoS信息将该第一报文映射到第一QoS flow包括：该处理单元根据该第一源QoS信息中包括的第一QoS特征从多个QoS flow中确定该第一QoS flow，其中，该第一源QoS信息中包括的第一QoS特征与该第一QoS flow中的5QI指示的QoS特征相对应。
结合第四方面，在第四方面的某些实现方式中，该第一QoS flow的QoS配置包括：最大保障带宽MGFBR；该处理单元还用于：确定该第一QoS flow的保障带宽小于或者等于该MGFBR。
结合第四方面，在第四方面的某些实现方式中，该第一QoS flow的QoS配置还包括： 最小保障带宽GFBR；该处理单元还用于：确定该第一QoS flow的保障带宽大于或者等于该GFBR且小于或者等于该MGFBR。
结合第四方面，在第四方面的某些实现方式中，该第一QoS flow的QoS配置包括：指示信息，该指示信息用于指示是否预留该第一QoS flow对应的资源；该处理单元还用于：根据该指示信息确定是否预留该第一QoS flow对应的资源。
结合第四方面，在第四方面的某些实现方式中，该第一源QoS信息为接收到的，或者，该第一源QoS信息为本地生成的；当该第一源QoS信息为本地生成时，该处理单元还用于：将该第一源QoS信息填入该第一报文中。
结合第四方面，在第四方面的某些实现方式中，该处理单元还用于：确定传输该第一报文的路径中传输节点的状态；当至少一个该输节点的状态满足预设条件时，该处理单元还用于启动主动保障机制。
结合第四方面，在第四方面的某些实现方式中，该当至少一个该输节点的状态满足预设条件时，该处理单元用于启动主动保障机制包括以下一项或者多项：当该至少一个该输节点存在丢包时，该处理单元确定重复发送该第一报文；或者当该至少一个该输节点丢包率大于预设值时，该处理单元确定采用前向纠错FEC冗余编码方式编码该第一报文。
第五方面，提供一种传输报文的装置，该传输报文的装置包括处理器，用于实现上述第一方面描述的方法中报文生成设备的功能。
可选地，该传输报文的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第一方面描述的方法中报文生成设备的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第一方面描述的方法中报文生成设备的功能。
可选地，该传输报文的装置还可以包括通信接口，该通信接口用于该传输报文的装置与其它设备进行通信。该通信接口可以为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该传输报文的装置包括：处理器和通信接口，
该处理器用于运行计算机程序，以使得该传输报文的装置实现上述第一方面描述的任一种方法；
该处理器利用该通信接口与外部通信。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该传输报文的装置为芯片或芯片系统。该通信接口可以是该芯片或芯片系统上输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第六方面，提供一种传输报文的装置，该传输报文的装置包括处理器，用于实现上述第二方面描述的方法中报文接收设备的功能。
可选地，该传输报文的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第二方面描述的方法中报文接收设备的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第二方面描述的方法中报文接收设备的功能。
可选地，该传输报文的装置还可以包括通信接口，该通信接口用于该传输报文的装置与其它设备进行通信。该通信接口可以为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该传输报文的装置包括：处理器和通信接口，
该处理器利用该通信接口与外部通信；
该处理器用于运行计算机程序，以使得该传输报文的装置实现上述第二方面描述的任一种方法。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该传输报文的装置为芯片或芯片系统。该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第七方面，本申请提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面该的方法。
第八方面，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面该的方法。
第九方面，提供了一种通信系统，包括第三方面所示的传输报文的装置和第四方面所示的传输报文的装置。
第十方面，提供了一种芯片装置，包括处理电路，该处理电路用于从存储器中调用并运行程序，使得安装有该芯片装置的通信设备执行上述第一和第二方面中任一种可能实现方式中的方法。
附图说明
图1是本申请实施例适用的一种网络架构示意图。
图2中的(a)是本申请实施例提供的一种传输报文的方法的示意性流程图。
图2中的(b)是本申请实施例提供的另一种传输报文的方法的示意性流程图。
图3是网络协议版本4(Internet protocol version 4，IPV4)报文头部结构示意图。
图4是网络协议版本6(Internet protocol version 6，IPV6)报文头部结构示意图。
图5是实时传输协议(real-time transport protocol，RTP)报文头部结构示意图。
图6是RTP扩展头格式示意图。
图7是通用分组无线业务隧道协议(general packet radio service tunnelling protocol，GTP)协议格式示意图。
图8中的(a)是一种5G QoS flow模型示意图。
图8中的(b)是本申请实施例提供的一种QoS flow模型示意图。
图8中的(c)是本申请实施例提供的另一种QoS flow模型示意图。
图9是本申请实施例提供的一种反射QoS机制示意性流程图。
图10是本申请提供的一种传输报文的装置1000的示意图。
图11是适用于本申请实施例的报文生成设备1100的结构示意图。
图12是本申请提供的另一种传输报文的装置1200的示意图。
图13是适用于本申请实施例的报文接收设备1300的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
图1是本申请实施例适用的一种网络架构示意图。下面对该图1所示的网络架构中涉及的各个部分分别进行说明。
1、用户设备(user equipment，UE)110：可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端、移动台(mobile station，MS)、终端(terminal)或软终端等等。例如，水表、电表、传感器等。
示例性地，本申请实施例中的用户设备可以指接入终端、用户单元、用户站、移动站、移动台、中继站、远方站、远程终端、移动设备、用户终端(user terminal)、终端设备(terminal equipment)、无线通信设备、用户代理或用户装置。用户设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的用户设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的用户设备或者未来车联网中的用户设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，用户设备还可以是物联网(internet of Things，IoT)系统中的用户设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。在本申请实施例中，IOT技术可以通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。
此外，在本申请实施例中，用户设备还可以包括智能打印机、火车探测器、加油站等传感器，主要功能包括收集数据(部分用户设备)、接收接入网设备的控制信息与下行数据，并发送电磁波，向接入网设备传输上行数据。
本申请实施例中，用于实现用户设备的功能的装置可以是用户设备，也可以是能够支持用户设备实现该功能的装置，例如，芯片系统或可实现用户设备功能的组合器件、部件，该装置可以被安装在用户设备中。
本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中，以用于实现用户设备的功能的装置是用户设备为例，描述本申请实施例提供的技术方案。
2、(无线)接入网设备(radio access network，(R)AN)120：用于为特定区域的 授权用户设备提供入网功能，并能够根据用户设备的级别，业务的需求等使用不同质量的传输隧道。
(R)AN能够管理无线资源，为用户设备提供接入服务，进而完成控制信号和用户设备数据在用户设备和核心网之间的转发，(R)AN也可以理解为传统网络中的基站。
示例性地，本申请实施例中的接入网设备可以是用于与用户设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved NodeB，HeNB，或home Node B，HNB)、基带单元(baseBand unit，BBU)，无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如，新无线(new radio，NR)，系统中的gNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的接入网设备，也可以将CU划分为核心网(core network，CN)中的接入网设备，本申请对此不做限定。
本申请实施例中，用于实现接入网设备的功能的装置可以是接入网设备，也可以是能够支持接入网设备实现该功能的装置，例如芯片系统或可实现接入网设备功能的组合器件、部件，该装置可以被安装在接入网设备中。在本申请实施例提供的技术方案中，以用于实现接入网设备的功能的装置是接入网设备为例，描述本申请实施例提供的技术方案。
其中，接入网设备与用户设备之间的接口可以为Uu接口(或称为空口)。当然，在未来通信中，这些接口的名称可以不变，或者也可以用其它名称代替，本申请对此不限定。
示例性地，接入网设备和用户设备之间的通信遵循一定的协议层结构，例如控制面协议层结构可以包括RRC层、PDCP层、RLC层、MAC层和物理层；用户面协议层结构可以包括PDCP层、RLC层、MAC层和物理层，在一种可能的实现中，PDCP层之上还可以包括业务数据适配(service data adaptation protocol，SDAP)层。
3、用户面网元130：用于分组路由和转发以及用户面数据的服务质量(quality of service，QoS)处理等。
在5G通信系统中，该用户面网元可以是用户面功能(user plane function，UPF)网元。在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
4、数据网络网元140：用于提供传输数据的网络。
在5G通信系统中，该数据网络网元可以是数据网络(data network，DN)网元。在未来通信系统中，数据网络网元仍可以是DN网元，或者，还可以有其它的名称，本申请不做限定。
5、接入管理网元150：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听以及接入授权/鉴权等功能。
在5G通信系统中，该接入管理网元可以是接入管理功能(access and mobility management function，AMF)网元。在未来通信系统中，接入管理网元仍可以是AMF网元，或者，还可以有其它的名称，本申请不做限定。
6、会话管理网元160：主要用于会话管理、用户设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是会话管理功能(session management function，SMF)网元。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
为方便说明，本申请后续，以接入管理功能网元为AMF网元，数据网络网元为DN网元，用户面功能网元为UPF网元，会话管理功能网元为SMF网元为例进行说明。
进一步地，将AMF网元简称为AMF，DN网元简称为DN，UPF网元简称为UPF，SMF网元简称为SMF。即本申请后续所描述的AMF均可替换为接入管理功能网元，DN均可替换为数据网络网元，UPF均可替换为用户面功能网元，SMF均可替换为会话管理功能网元。
为方便说明，本申请，以装置为AMF实体、DN实体、UPF实体和SMF实体为例，对传输报文的方法进行说明，对于装置为AMF实体内的芯片、UPF实体内的芯片或为SMF实体内的芯片的实现方法，可参考装置分别为AMF实体、UPF实体、SMF实体的具体说明，不再重复介绍。
在图1所示的网络架构中，用户设备通过N1接口与AMF连接，RAN通过N2接口与AMF连接，RAN通过N3接口与UPF连接。
UPF之间通过N9接口连接，UPF通过N6接口与DN互联。
SMF通过N4接口控制UPF。AMF通过N11接口与SMF接口。
需要说明的是，图1中所涉及的各个网元以及网元之间的通信接口的名称是以目前协议中规定的为例进行简单说明的，但并不限定本申请实施例只能够应用于目前已知的通信系统。因此，以目前协议为例描述时出现的标准名称，都是功能性描述，本申请对于网元、接口或信令等的具体名称并不限定，仅表示网元、接口或者信令的功能，可以对应的扩展 到其它系统，比如3G、4G、5G或未来通信系统中。
上述图1所示的本申请实施例能够应用的网络架构仅是一种举例说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
例如，在某些网络架构中，AMF网元、SMF网元、UPF网元等网络功能网元实体都称为网络功能网元(network function，NF)网元；或者，在另一些网络架构中，AMF网元、SMF网元、UPF网元等网元的集合都可以称为控制面功能网元。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、5G、新无线(new radio，NR)或未来网络等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。通信系统还可以是陆上公用移动通信网(public land mobile network，PLMN)网络、设备到设备(device-to-device，D2D)通信系统、机器到机器(machine to machine，M2M)通信系统、物联网(internet of Things，IoT)通信系统或者其他通信系统。
在本申请实施例中，用户设备或接入网设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是用户设备或接入网设备，或者，是用户设备或接入网设备中能够调用程序并执行程序的功能模块。
另外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读存储介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
为便于理解本申请实施例，对本申请实施例中涉及的几个基本概念做简单说明。应理解，下文中所介绍的基本概念是以NR协议中规定的基本概念为例进行简单说明，但并不限定本申请实施例只能够应用于NR系统。
1、IETF QoS服务模型：
在传统的IP网络中，所有的报文都被无区别的等同对待，每个转发设备对所有的报 文均采用先入先出(first in first out，FIFO)的策略进行处理，尽最大的努力将报文送到目的地，但对报文传送的可靠性、传送延迟等性能不提供任何保证。
随着IP网络上新应用的不断出现，对IP网络的服务质量也提出了新的要求，例如，互联网协议电话(voice over Internet protocol，VoIP)等实时业务就对报文的传输延迟提出了较高要求(相对而言，电子邮件(electronic mail，E-Mail)和文件传输协议(file transfer protocol，FTP)业务对时间延迟并不敏感)。为了支持具有不同服务需求的语音、视频以及数据等业务，要求网络能够区分出不同的通信，进而为之提供相应的服务。于是出现了QoS技术，IETF定义了三种QoS服务模型：
1)best-effort service服务模型：
best-effort service服务模型是最简单的服务模型。应用程序可以在任何时候，发出任意数量的报文，而且不需要事先获得批准，也不需要通知网络设备。对best-effort service服务模型，网络设备尽最大的可能性来发送报文。但对时延、可靠性等性能不提供任何保证。
best-effort service服务模型适用于绝大多数网络应用，例如，FTP、E-Mail等，通过FIFO队列来实现。
2)IntServ服务模型：
IntServ服务模型在发送报文前，需要通过资源预留协议(resource reser vation Protocol，RSVP)信令向网络设备申请特定的服务。RSVP是在应用程序开始发送报文之前来为该应用申请网络资源(如带宽、时延等)的，所以是带外信令。一旦网络设备确认为应用程序分配资源，则网络设备将为每个连接维护一个状态，并基于这个状态执行报文的分类、流量监管、排队及其调度。只要应用程序的报文控制在流量参数描述的范围内，网络设备将承诺满足应用程序的QoS需求。
具体地，网络设备通过配置五元组维护连接状态，其中，五元组包括源IP地址、目的IP地址、协议号、源端口、目的端口。
3)DiffServ服务模型：
与上述的IntServ服务模型不同的是DiffServv服务模型不需要使用RSVP，即应用程序在发出报文前，不需要通知网络设备为其预留资源。对DiffServ服务模型，网络设备不需要为每个流维护状态，网络设备根据每个报文的差分服务类(IP报文头中的差分服务标记字段差分服务代码点(differentiated services code point，DSCP)值)，来提供特定的服务。
在实施DiffServ服务模型的网络中，每一个转发设备都会根据报文的DSCP字段执行相应的转发行为，主要包括以下三类转发行为：
加速转发(expedited forwarding，EF)：主要用于低延迟、抖动和丢包率的业务，这类业务一般运行一个相对稳定的速率，需要在转发设备中进行快速转发；
确保转发(assured forwarding，AF)：采用确保转发行为的业务在没有超过最大允许带宽时能够确保转发，一旦超出最大允许带宽，则将转发行为分为4类，每类又可划分为3个不同的丢弃优先级，其中每一个确保转发类都可分配不同的带宽资源。IETF建议使用4个不同的队列分别传输AF1x、AF2x、AF3x、AF4x业务，并且每个队列提供3种不同的丢弃优先级，因此可以构成12个有保证转发的每跳行为(Per-Hop Behavior，PHB)；
尽力转发(best-effort delivery，BE)：主要用于对时延、抖动和丢包不敏感的业务。
DiffServ服务模型只包含有限数量的业务级别，状态信息的数量少，因此实现简单，扩展性较好，是业界主流的IP网的QoS解决方案。
DiffServ服务模型的不足之处是很难提供基于流的端到端的质量保证。因为尽管IETF为每个标准的PHB都定义了推荐的DSCP值，但是设备厂家可以重新定义DSCP与PHB之间的映射关系，因此不同运营商的DiffServ网络之间的互通还存在困难，不同DiffServ网络在互通时需要维护一致的DSCP与PHB映射。
本申请实施例中涉及的服务模型，是指一组端到端的QoS功能。
2、QoS flow机制：
3GPP R16标准中，QoS flow是最小QoS控制粒度，每个QoS flow都有对应的QoS配置。
QoS配置包括的QoS参数描述了具体的QoS要求，QoS参数主要包括：
QoS flow索引(QoS flow index，QFI)、5G网络的服务质量标识符5QI、流最低保障速率(guaranteed flow bit rate，GFBR)、流最高保障速率(maximum flow bit rate，MFBR)。
进一步地，QoS参数中的5QI是一组QoS特征组合索引，QoS特征包括：
资源类型(resource type)、优先级(priority level)、包时延预算(packet delay budget)、包错误率(packet error rate)、统计周期(averaging window)和最大突发数据量(maximum data burst volume)。
其中，资源类型包括：非最低保障速率(non guaranteed bit rate，non-GRB)、最低保障速率(guaranteed bit rate，GRB)、时延敏感型GRB(delay-critical GBR)；最大突发数据量是时延敏感型GRB特有参数。具体地，3GPP R16标准定义了一部分5QI的QoS特征值，可直接使用。3GPP也允许运营商和/或设备制造商分配不冲突的5QI并预设置对应QoS特征值的方式，在运营商网络中使用。
QoS flow配置生成后，5G控制面网元AMF与SMF将QoS flow配置下发给UE、RAN和UPF，同时下发包过滤规则(packet filters set)给UE与UPF。
UE根据包过滤规则将上行报文映射到对应的QoS flow；
UPF根据包过滤规则将从N6口收到的下行报文映射到对应的QoS flow。
目前5G场景中数据下行流程包括：
步骤1：用户数据包含在IP报文中从DN通过N6接口发送给5G核心网(5G core，5GC)的UPF设备；
步骤2：UPF根据5GC控制面下发的QoS配置与packet filters set，将IP报文映射到对应的QoS flow上；
具体地，5G R16标准定义的packet filters set包含如下参数：
源端口号(source port number)、目的端口号(destination port number)、协议类型(例如，IP协议的协议号(protocol ID of the protocol above IP)或下一个报头类型(next header type))、IPV4头域的服务类型(type of service，TOS)或IPV4头域中的通信类别、IPV6中的流标签字段(flow label(IPv6))、安全参数索引(security parameter index)和报文方向(packet filter direction)。
步骤3：UPF按报文所属的QoS flow的QoS要求，进行针对性保障与处理；
步骤4：UPF使用通用分组无线业务隧道协议-用户面(general packet radio service tunnelling protocol user，GTP-U)协议封装用户面IP报文，将报文所属QoS flow的QFI填写到GTP-U协议头部字段，然后将报文转发到N3接口。
目前5G空口用户面新增SDAP协议层，适配5G QoS机制，其中，SDAP能够实现QoS flow与数据无线承载(date radio bear，DRB)之间的映射以及反射式QoS机制，上行流程包括：
步骤1：5GC控制面下发多条QoS规则给UE，每条QoS规则中都包含packet filters set以及绑定的QFI；
步骤2：UE底层(SDAP协议栈)收到应用(application，APP)要发送的IP报文后，根据QoS规则中packet filters set将报文匹配到对应的QoS flow，并将对应的QFI填写到空口数据包头部；
步骤3：UE根据QoS flow的QoS要求，将IP报文映射到不同承载标准的DRB上发送；
步骤4：RAN侧收到UE发送的报文后，用GTP-U协议封装用户面IP报文，将从空口数据包头解析出报文所属QoS flow的QFI填写到GTU-U协议头部字段，然后将报文转发到N3接口。
为简化5GC控制面下发QoS规则处理，UE可通过QoS反射机制学习到QoS规则，具体地包括：
接入网设备在发送给UE的下行数据中，空口协议栈的SDAP协议头中包含QFI和是否支持反射QoS指示：反射QoS流到DRB映射指示(reflective QoS flow to DRB mapping indication，RDI)；
UE收到下行报文后，若发现RDI指示为1时，记录报文五元组、QFI信息、DRB信息，作为通过反射QoS机制学习到的QoS规则；
UE在发送上行报文时，可使用通过反射QoS机制学习到的QoS规则进行匹配，将报文匹配到对应的QoS flow、DRB上发送。
上述的QoS flow机制量化了QoS要求，网络中的传输设备只要通过报文中QoS流指示(QoS flow indicator，QFI)就可以清晰的确认QoS要求并进行处理(例如，根据QFI取得对应的QoS配置与5QI对应的QoS特征)。因此QoS flow机制解决了IETF Diffserv服务模型中的，不同设备商和/或不同运营商对DSCP与PHB映射实现不一致的问题。
应理解，上述对IETF QoS服务模型和QoS flow机制的介绍只是为了更好的理解本申请提供的传输报文的方法提供的简单的描述，对本申请的保护范围不构成任何的限定，有关IETF QoS服务模型和QoS flow机制的详细说明可以参考目前协议中的相关描述，本申请中不进行赘述。
由上述的IETF QoS服务模型和QoS flow机制可知，传输网络中的转发节点在转发IP报文时，根据IP报文的网络层特征将报文匹配到预置的QoS策略，并按QoS策略进行差异化保障处理的模式。
具体地，IP报文的网络层特征可以是上述的五元组、TOS、DSCP或QFI；QoS策略通过配置或控制面下发获得。
但是，在目前的QoS机制(IETF QoS服务模型或QoS flow机制)下，应用无法清 晰、详尽的将QoS要求指示给传输网络，进一步的，应用无法将应用层数据特征指示给传输网络。
例如，不支持连接级别的信息和/或不支持IP包级别的信息指示给传输网络。
其中，不支持连接级别的信息包括：
连接级别的数据特征：如视频图像组(group of picture，GOP)特征(平均码率、帧率、I帧频率等)、物联网(Internet of things，IOT)数据上报特征(上报周期、数据大小等)；
连接级别的突发事件信息：视频点播时拖动事件、虚拟现实(virtual reality，VR)播放时转头事件等。
不支持IP包级别的信息包括：
IP包与数据段关系：如当前IP包属于视频的哪一帧，该IP包后该视频帧还有多少数据；
IP包级别的QoS指示：由于包过滤规则和传输协议限制，当前QoS机制中一条连接中的不同报文难以映射到不同的QoS策略(例如，一条视频连接中的I帧数据和P帧数据可能使用不同的QoS策略)。
另外，3GPP R16定义了packet filters set机制，用于指示UPF、UE将报文映射到QoS flow。但实际使用时，根据五元组、协议类型映射对组网要求高、限制多，使用不方便。使用TOS或DSCP映射存在被传输层串改、信息丢失的问题，具体包括：
DSCP/TOS是定性的QoS期望，5QI是定量的QoS指标，则相互转化可能存在信息丢失为问题；或者
DSCP/TOS可能被传输网络的路由设备修改，APP无法可靠的将QoS特征传递给3GPP网络。
进一步地，QoS flow机制是一种控制面(AMF、SMF)协商、下发QoS策略配置给用户面(UPF、RAN)，用户面报文按规则匹配对应的QoS机制的宏控制模式；IETF的IntServ服务模型使用资源预留协议(resource reser vation protocol，RVSP)协议，DiffServ使用运维领域的配置功能下发QoS策略配置，也属于宏控制模式。宏控制模式下，QoS策略变化决策和执行链长，变更耗时(秒级甚至分钟级)，无法满足QoS策略需要频繁、快速调整的业务诉求。且需要应用调用不同传输网络的QoS策略变更接口，开发难度大，要求高。
例如，5G QoS flow中的GFBR和/或最大突发数据量(maximum data burst volume，MDBV)，无法根据连接数量的变化而动态调整；
还例如，一个用户设备并发连接数可能是动态变化的(例如，用户驻地设备(customer premises equipment，CPE)可能挂1个、3个或N个设备)，按最大可能并发连接数预留会极大浪费空口资源；业务调用5GC开放接口动态调整GFBR或MDBV会导致应用开发难度极大提升，且运营商出于安全考虑，不一定会开放该能力。
为了解决上述的目前QoS机制存在的问题，本申请提供一种传输报文的方法，使用随路方式，在报文中携带源QoS信息，收发端与传输网络根据源QoS信息，实现端到端QoS保障。
需要说明的是，本申请实施例中涉及的QoS信息可以理解为QoS参数，还可以理解 为指示QoS参数的标识，用于为报文提供QoS保障。
具体地，通过源QoS信息，发送端可将应用数据特征与QoS要求清晰、详尽的指示给传输网络；和/或
通过源QoS信息，传输网络中的转发设备通过报文，可清晰的感知连接级、报文级数据特征与QoS要求，并按指示进行保障与优化；和/或
通过源QoS信息，同时传输设备还能根据感知的数据特征，触发管道QoS策略在合理范围内快速调整。
应理解，本申请实施例提供的方法可以应用于5G通信系统，例如，图1中所示的通信系统。
下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是用户设备、接入网设备或核心网设备，或者，是用户设备、接入网设备或核心网设备中能够调用程序并执行程序的功能模块。
为了便于理解本申请实施例，做出以下几点说明。
第一，在本申请中，“用于指示”可以理解为“使能”，“使能”可以包括直接使能和间接使能。当描述某一信息用于使能A时，可以包括该信息直接使能A或间接使能A，而并不代表该信息中一定携带有A。
将信息所使能的信息称为待使能信息，则具体实现过程中，对待使能信息进行使能的方式有很多种，例如但不限于，可以直接使能待使能信息，如待使能信息本身或者该待使能信息的索引等。也可以通过使能其他信息来间接使能待使能信息，其中该其他信息与待使能信息之间存在关联关系。还可以仅仅使能待使能信息的一部分，而待使能信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的使能，从而在一定程度上降低使能开销。同时，还可以识别各个信息的通用部分并统一使能，以降低单独使能同样的信息而带来的使能开销。
第二，在本申请中示出的第一、第二以及各种数字编号(例如，“#1”、“#2”等)仅为描述方便，用于区分的对象，并不用来限制本申请实施例的范围。例如，区分不同消息等。而不是用于描述特定的顺序或先后次序。应该理解这样描述的对象在适当情况下可以互换，以便能够描述本申请的实施例以外的方案。
第三，在本申请中，“预设的”可包括预先定义，例如，协议定义。其中，“预先定义”可以通过在设备(例如，包括用户设备或网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。
第四，本申请实施例中涉及的“保存”，可以是指的保存在一个或者多个存储器中。所述一个或者多个存储器，可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器，也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
第五，本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括5G协议、新空口(new radio，NR)协议以及应用于未来的通信系统中的相关协议，本申请 对此不做限定。
以下，不失一般性，以报文生成设备和报文接收设备之间的交互为例详细说明本申请实施例提供的传输报文的方法。
本申请提供的一种传输报文的方法。执行主体包括报文生成设备和报文接收设备。
一种可能的实现方式，本申请实施例应用于下行报文传输时，该报文生成设备可以是用于提供传输数据的网络(例如，DN网元)，报文接收设备包括核心网设备(例如，UPF)、接入网设备和用户设备。
另有一种可能的实现方式，本申请实施例应用于上行报文传输时，该报文生成设备可以是用户设备中的应用层，报文接收设备包括用户设备中的底层(例如，SDAP层)、核心网设备(例如，UPF)、接入网设备和数据网络(例如，DN网元)。
为了便于理解，下文从下行和上行分别介绍本申请提供的传输报文的方法。下行报文传输场景下，如图2中的(a)所示，图2中的(a)是本申请实施例提供的一种传输报文的方法的示意性流程图。
该传输报文的方法至少包括以下部分步骤。
S210，数据网络生成第一报文#1。
具体地，Internet网上的应用根据业务的QoS需要生成连接中的第一报文#1。
第一报文#1中包括第一源QoS信息，该第一源QoS信息用于为第一报文#1提供QoS保障。本申请实施例中的QoS保障包括为报文提供服务，解决网络延迟和/或网络阻塞等问题。
需要说明的是本申请实施例中涉及的报文可以称为IP报文、数据报文、业务报文、包或报文等，下文中称为报文只是举例对本申请的保护范围不构成任何的限定，可以理解为传输网络中传输的数据包。
另外，需要说明的是，上述的第一报文#1可以是数据网络生成的多个报文中的任意一个报文，该多个报文的五元组信息相同，可以理解为该多个报文属于一个连接。本申请实施例中一个连接中的报文的五元组信息相同，五元组信息用于指示报文的五元组，可以是五元组参数(例如，上述的源IP地址、目的IP地址、协议号、源端口、目的端口)，还可以是指示五元组的标识(例如，标识#1指示源IP地址#1、标识#2指示目IP地址#1、标识#3指示协议号#1、标识#4指示源端口#1、标识#5指示目的端口#1)等间接指示五元组的信息。进一步地图2中的(a)所示的方法流程还包括：
S220，数据网络生成第二报文#1。
该第二报文#1可以数据网络生成的多个报文中的除上述的第一报文#1之外的任意一个报文。第二报文#1中包括第二源QoS信息，该第二源QoS信息用于为第二报文#1提供QoS保障。
应理解，数据网络还可以生成连接中的其他报文，上述生成第一报文#1以及第二报文#1只是举例，对本申请的保护范围不够成任何的限定，本申请实施例中数据网络可以生成多个报文，并且该多个报文的五元组信息相同。
具体地，该多个报文中的每个报文中都包括源QoS参数，且每个报文包括的源QoS信息用于对其所对应的报文进行QoS保障，多个报文包括的源QoS信息不相同。
例如，上述的第一报文#1中包括的第一源QoS信息和第二报文#1中包括的第二源 QoS信息不相同。
还例如，多个报文中的某个报文中包括的源QoS信息和该多个报文中除该某个报文之外的至少一个报文中包括的源QoS信息不相同。
又例如，该多个报文中至少两个报文中分别包括的两个的源QoS信息不相同。其中，两个报文中分别包括的两个的源QoS信息指的是该两个报文中每个报文包括一个源QoS信息。
示例性地，源QoS信息包括QoS特征和数据特征，QoS特征用于指示报文的QoS需求，数据特征用于指示报文的传输特性。
例如，上述的第一源QoS信息包括第一QoS特征和第一数据特征，第一QoS特征用于指示第一报文的QoS需求，第一数据特征表示第一报文的传输特性。
还例如，上述的第二源QoS信息包括第二QoS特征和第二数据特征，第二QoS特征用于指示第二报文的QoS需求，第二数据特征表示第二报文的传输特性。
在源QoS信息包括QoS特征和数据特征的情况下，上述的多个报文包括的源QoS信息不相同可以是多个报文包括的数据特征不同，和/或，所述多个报文包括的QoS特征不同。
例如，上述的第一报文#1中包括的第一源QoS信息中的第一数据特征和第二报文#1中包括的第二源QoS信息中的第二数据特征不相同；和/或，
上述的第一报文#1中包括的第一源QoS信息中的第一QoS特征和第二报文#1中包括的第二源QoS信息中的第二QoS特征不相同。
需要说明的是，上述连接中包括第一报文#1和第二报文#1，且第一报文#1和第二报文#1分别包括的QoS特征不同只是举例，对本申请的保护范围不构成任何的限定，该连接中还可以包括其他的报文，并且不同的报文包括的QoS特征可以不同。可以理解为本申请实施例中，一个连接中的多个报文可以具备不同的QoS特征，根据QoS特征对不同的报文进行QoS保障。可以针对不同的报文的QoS需求为报文提供QoS保障。
为例便于描述，下文中以连接中的某个报文中包括源QoS信息为例说明本申请中提出的源QoS信息。
下面简单说明本申请实施例中涉及的源QoS信息：
源QoS信息包括QoS特征，进一步地源QoS信息还包括数据特征。
数据特征包括连接级别的数据特征和/或包级别的数据特征。其中，连接级别的数据特征用于指示连接中包括的多个报文的传输特性，即指示连接的传输特性；包级别的数据特征用于指示某一个报文的传输特性，即包级别的数据特征指示包括该包级别的数据特征的报文的传输特性。
连接级别的数据特征包括连接基本信息，进一步地连接级别的数据特征还包括周期型连接信息、周期型连接波峰信息或连接突发事件通知信息中的至少一个。
其中，连接基本信息包括平均速率或持续时长。具体地，平均速率指示连接数据平均发送速率，例如，一条视频直播连接码率为2Mbps、持续时长指示预计连接持续时长。
周期型连接信息包括频率、大小或时延预算。具体地，频率指示数据发送频率，例如，25HZ(每秒25帧，每隔40ms产生一帧)、大小指示每频次发送数据均值，例如，如一条视频直播连接的P帧平均0.3Mbyte、时延预算指示一个周期内所有数据全部传递到接收 端耗时预算。
周期型连接波峰信息包括波峰频率、波峰大小、波峰时延预算或波峰发送时间。具体地，波峰频率指示波峰产生频率，例如，0.5HZ(每隔两秒出现一个I帧(2秒一个GOP))、波峰大小指示波峰发送数据均值(如一个I帧2MB)、波峰时延预算指示波峰数据全部传递到接收端耗时预算、波峰发送时间指示可用绝对时间、相对时间(距离现在多少毫秒后)、相对位置(在哪个频次)方式表示。
连接突发事件通知信息包括突发事件类型、预计突发事件发生时间、预计突发事件数据量或突发事件数据时延预算。具体地，突发事件类型包括例如VR转头、视频播放拖动；预计突发事件发生时间指示突发事件数据预计到达时间，相对时间表示；预计突发事件数据量指示突然事件需要传输的数据量；突发事件数据时延预算指示突发事件全部传输到接收端耗时预算。
需要说明的是，如果应用侧无法通过连接级别的数据特征实现突发事件预通知，可以使用包级别的数据特征实时通知。
包级别的数据特征包括包数据完整性信息。包数据完整性信息包括数据块序号、数据块大小、包位置或数据块时延预算。具体地，数据块序号指示包所属数据块编号，例如，视频流中按帧连续编号；数据块大小指示包所属数据块大小，例如，P帧数据段大小为0.3Mbytes；包位置指示包在所属数据块的位置；数据块时延预算指示包全部传输到接收端耗时预算。
需要说明的是，本申请实施例中涉及的数据块可以理解为连接中的数据块，并且数据块中可以包括至少一个报文，例如，视频流中，每个I帧、P帧都可以称为数据块。另外，数据块还可以称为数据段、报文段或报文块等。
还例如，某个数据块中包括多个报文，不同的报文中的包级别的数据特征包括报文在数据块中的位置、序号等信息。
另外，还需要说明的是，数据完整性传输是指接收端完整的收到某数据块的所有报文后再使用场景下(如视频的一帧)，传输网络可针对性进行优化与保障，可以在不影响应用整体时延的前提下，提升传输效率。
QoS特征包括连接级别的QoS特征和/或包级别的QoS特征，其中，连接级别的QoS特征用于指示连接中包括的多个报文的QoS需求，即指示该连接的QoS需求；包级别的QoS特征用于指示某一个报文的QoS需求，即包级别的QoS特征指示包括该包级别的QoS特征的报文的传输特性。
进一步地，连接级别的QoS特征可以是连接QoS特征指示CQI、包级别的QoS特征可以是包QoS特征指示PQI，CQI是连接级别的QoS特征，PQI是包级别的QoS特征。当报文中携带PQI时，报文使用PQI对应的QoS特征，否则报文使用CQI对应的QoS特征。
通过CQI和/或PQI，可以实现一个连接中不同报文具有不同的QoS特征。
具体地，CQI和PQI可描述的QoS特征包括：资源类型、优先级、时延预算或错误率，其中，资源类型可以是GBR、时延敏感GBR、Non-GBR；优先级值越小，优先级越高；时延预算表示期望E2E时延；错误率可以是错包、丢包的概率。
应理解，上述的CQI和PQI可描述的QoS特征只是举例说明CQI和PQI可以描述的 QoS特征，对本申请的保护范围不构成任何的限定，CQI和PQI还可以描述其他的QoS特征，这里不再一一举例说明。
使用QoS特征时也可通过标准或企业规范预定义CQI、PQI特征值并下发给传输网络。这样只要在报文中携带CQI、PQI，传输设备即可知道连接级别的和/或包级别的量化的QoS要求。
需要说明的是，上述的QoS特征以CQI和/或PQI的形式体现，能够节省传输开销。也可以直接将各个QoS特征值像其他连接级别的数据特征、包级别的数据特征一样，填写到报文中。如，连接级别的QoS特征还可以为连接QoS特征信息，包级别的QoS特征还可以为包QoS特征信息。
在报文中携带源QOS信息，包括以下几种可能：
可能一：连接信息和包信息携带在报文中；
可能二：包信息携带在报文中，连接信息携带在虚拟dummy IP包中；
可能三：包信息携带在报文中，连接信息通过控制面传输，
其中，连接信息包括上述的连接级别的数据特征和连接级别的QoS特征，包信息包括连接级别的数据特征和包级别的QoS特征。
应理解，上述的可能一至可能三只是举例说明如何将源QOS信息发送给传输网络中的其他节点，对本申请的保护范围不构成任何的限定，还可以通过其他可能的实现方式将源QOS信息发送给传输网络中的其他节点，例如，在发送报文之前就可以将源QOS信息通过其他信息流发送给传输节点，并指示源QOS信息和报文之间的对应关系。
下文中以连接级别的QoS特征为上述的CQI，包级别的QoS特征为上述的PQI为例说明如何携带源QoS信息，当连接级别的QoS特征为连接QoS特征信息、包级别的QoS特征为包特征信息的情况下，填写方式类似，本申请中不再赘述。
具体地，在报文中携带源QOS信息时需要对报文传输协议进行扩展。
本申请实施例中提供几种可能的扩展方式：
方式一：IPV4扩展。
IPV4报文头部结构请求评论文件(request for comments，RFC)定义如图3所示，图3是IPV4报文头部结构示意图，包括：
4位版本号(version)：IP协议(IPv4)版本号位；
4位头部长度(header length)：标识头部有多少个4字节，即最大共15*4个字节；
8位服务类型(type of service)：包含一个4位优先权字段：最小延时，最大吞吐量，最高可靠性和最小费用；
16位总长度(total length)：表示整个IP数据报的长度；
16位标识(identification)：标识数据报；
3位标识(flags)：为分片存在；
13位分片偏移(fragment ofset)：分片相对原始IP数据报开始处的偏移；
8位生存时间(time to live，TTL)：数据报到达目的地之前允许经过的路由跳跳数；
8位协议(protocol)：用来区分上层协议；
16位头部校验和(header checksum)：检验数据报头部在传输过程中是否损坏；
32位源端口IP地址(source address)；
32位目的端口地址(destination address)；
选项(options)(可变长)：记录路由。
上述的IP包头中的options字段可用来扩展。
RFC定义了options字段有两类扩展：
类型1：只有一个option-type；
类型2：option-type和option-length(option-data的长度)以及option-data；
当前RFC定义的Option扩展如表1所示：
表1
类型(class) 数值(number) 长度(length) 描述(description)
0 0 - 选项列表结束
0 1 -  
0 2 11  
0 3 Var.  
0 9 Var.  
0 7 Var.  
0 8 4  
2 4 Var.  
扩展方式1：连接信息、包信息都在数据包IP头部传输。
可使用类型2(option-type和ption-length(option-data的长度)以及option-data)对IP头部Option字段进行扩展，支持应用数据特征与QoS要求指示，扩展示例：
option-type.Class＝0；
option-type.Number＝10//连接信息和包信息扩展；
option-type.Length＝var.(按实际长度填写)；
option-data扩展方式A：按固定字段方式扩展，固定字段定义如下表2：
表2
Figure PCTCN2022070294-appb-000001
Figure PCTCN2022070294-appb-000002
应理解，表2只是示例性的，对本申请的保护范围不构成任何的限定。例如，表3中的单位信息可以不指示；还例如，表3中的长度信息可以不指示；还例如，表3中的连接信息和/或包信息中的一项或多项可以不指示。也就是说连接信息和包信息具体的体现形式可以有多种可能，这里不一一举例说明。
option-data扩展方式B：按阈限值(threshold limit value，TLV)或协议缓冲区(protocol buffer)方式扩展，各字段定义与上表3类似。使用TLV或protocol buffer格式后，各字段可按需传输，不必全部携带(如非周期型连接可不携带周期型参数)。TLV或protocol buffer编码方式可以参考目前协议中的相关规定，本申请对此不再赘述。
IP扩展方式2：包信息在数据包IP头部传输，连接信息使用虚拟IP(dummy IP)包传递，在每个IP包中都携带连接信息和包信息会导致报文传输开销过大。
具体地，dummy IP包不传递用户数据，只传递五元组对应的连接信息。另外，dummy IP包定期发送(如每2秒发送一次)，且在连接信息变化时立即发送(例如视频流分辨率调整导致连接信息变化)。
可通过包信息在数据包IP头部传输，连接信息使用dummy IP包传递方式降低源QOS信息的传输开销。
包信息扩展示例：
使用类型2对IP头部Option字段进行扩展，支持应用数据特征与QoS要求指示。
option-type.Class＝0；
option-type.Number＝10//包信息扩展；
option-type.Length＝var.(按实际长度填写)；
option-data扩展方式A：按固定字段方式扩展，固定字段定义如下表3所示：
表3
Figure PCTCN2022070294-appb-000003
应理解，表3只是示例性的，对本申请的保护范围不构成任何的限定。例如，表4中的单位信息可以不指示；还例如，表4中的长度信息可以不指示；还例如，表4中的包信息中的一项或多项可以不指示。也就是说包信息具体的体现形式可以有多种可能，这里不一一举例说明。
option-data扩展方式B：按TLV或protocol buffer方式扩展，各字段定义与上表4类似。使用TLV或protocol buffer格式后，各字段可按需传输，不必全部携带(如非周期型 连接可不携带周期型参数)。TLV或protocol buffer编码方式可以参考目前协议中的相关规定，本申请对此不再赘述。
连接信息扩展示例：
使用类型2对IP头部Option字段进行扩展，支持应用数据特征与QoS要求指示。
option-type.Class＝0；
option-type.Number＝11//连接信息扩展；
option-type.Length＝var.(按实际长度填写)；
option-data扩展方式A：按固定字段方式扩展，固定字段定义如下表4所示：
表4
Figure PCTCN2022070294-appb-000004
应理解，表4只是示例性的，对本申请的保护范围不构成任何的限定。例如，表5中的单位信息可以不指示；还例如，表5中的长度信息可以不指示；还例如，表5中的连接信息中的一项或多项可以不指示。也就是说连接信息具体的体现形式可以有多种可能，这里不一一举例说明。
option-data扩展方式B：按TLV或protocol buffer方式扩展，各字段定义与上表类似。使用TLV或protocol buffer格式后，各字段可按需传输，不必全部携带(如非周期型连接可不携带周期型参数)。TLV或protocol buffer编码方式可以参考目前协议中的相关规定，本申请对此不再赘述。
由于dummy IP包不传递用户数据，因此option-data也可放在IP报文数据区传输；或者
由于dummy IP包不传递用户数据，因此IP报文数据区也可用于传输其他有用信息，如网络状态等。
需要说明的是，使用dummy IP报文传递连接信息时，可以与目前dummy报文机制结合。例如，可扩展5G标准中定义的QoS监测、性能度量函数(performance measurement function)机制中的dummy报文机制，支持传递连接信息。
方式二：IPV6扩展。
IPV6报文头部结构RFC定义如图4所示，图4是IPV6报文头部结构示意图，包括：
版本(version)：版本字段用来表示IP数据报使用的是IPv6协议封装，占4位；
通信分类(traffic class)：通信分类字段用来标识对应IPv6的通信流类别，或者说是优先级别，类似于IPv4中的ToS(服务类型)字段；
流标签(flow label)：流标签字段时IPv6数据报中新增的一个字段，可用来标记报文的数据流类型，以便在网络层区分不同的报文。流标签字段有源节点分配，通过流标签、源地址、目的地址三元组方式就可以唯一标识一条通信流，而不用像IPv4那样需要使用五元组方式(源地址、目的地址、源端口、目的端口和传输层协议号)；
有效载荷长度(payload length)：有效载荷长度字段是以字节为单位的标识IPv6数据报中有效载荷部分(包括所有扩展报头部分)的总长度，也就是除了IPv6的基本报头以外的其他部分的总长度；
下一个头部(next header)：下一个头部字段用来标识当前报头(或者扩展报头)的下一个头部类型；
跳数限制(hop limit)：跳数限制于IPv4报文中的TTL字段类似，指定了报文可以有效转发的次数。报文每经过一个路由器结点，跳数值就减1，当此字段值减到0时，则直接丢弃该报文；
源地址(source IP address)：源IP地址字段标识了发送该IPv6报文源节点的IPv6地址；
目的IP地址(destination IP address)：目的IP地址字段标识了IPv6报文的接受节点的IPv6地址。
IPV6协议通过下一个头部字段机制进行扩展。在没有扩展头的IPv6包中，此字段的值表示上一层协议。在有扩展头的IPv6包中，此字段表示下一个扩展字段的类型，已定义的扩展头协议号可以参考目前协议中的相关描述，本申请中不进行赘述。
可在未使用的扩展类型中，选一个表示源QoS信息，例如，目前未定义的协议号143可以用来表示源QoS信息。
143：源QoS信息。
通过上述扩展，可在IPV6报文头部携带源QoS信息。
IPV6报文头部支持携带源QoS信息，可分两种方式携带：
携带方式1：IPV6报文携带用户报文数据，头部源QoS扩展字段包含连接信息和包信息，该携带方式1下，源QoS信息接口定义与IP扩展方式1类似，不再赘述；
携带方式2：可在未使用的扩展类型中，选两个分别表示源QoS信息包信息和连接信息，例如，143：源QoS信息中的包信息；144：源QoS信息中的连接信息。
具体地，IPV6报文携带用户报文数据，头部扩展字段协议号为：143，只包含源QoS信息中的包信息；
IPV6报文不携带用户报文数据，头部扩展字段协议号为：144，只包含源QoS信息中的连接信息。
该携带方式2下，源QoS信息接口定义与IP扩展方式2类似，不再赘述。
方式三：RTP扩展。
RTP报文头部结构如图5所示，图5是RTP报文头部结构示意图，包括：
版本(version，V):2bits，标明RTP版本号；
填充标识(padding，P):1bit，如果该位被设置，则在该packet末尾包含了额外的附加信息，附加信息的最后一个字节表示额外附加信息的长度(包含该字节本身)。该字段之所以存在是因为一些加密机制需要固定长度的数据块，或者为了在一个底层协议数据单元中传输多个RTP packets；
扩展(extension，X):1bit，如果该位被设置，则在固定的头部后存在一个扩展头部；
起作用的源计数(contributing source count，CC):4bits，在固定头部后存在多少个起作用的源(contributing source，CSRC)标记；
标记(marker，M):1bit，位的功能依赖于配置文件(profile)的定义，profile可以改变该位的长度，但是要保持marker和payload type总长度不变(一共是8bit)；
载荷类型(payload type，PT):7bits，标记RTP packet所携带信息的类型；
序列号(sequence number):16bits，每个RTP packet发送后该序列号加1，接收方可以根据该序列号重新排列数据包顺序；
时间戳(timestamp):32bits，反映RTP packet所携带信息包中第一个字节的采样时间；
标识数据源(synchronization source，SSRC)标识(identifier):32bits，在一个RTP Session其间每个数据流都应该有一个不同的SSRC；
起作用的源列表CSRC list:32bits，标识贡献的数据源。
RTP协议也允许在RTP固定头部后增加扩展头部的方式进行扩展，只要将RTP头部中的X字段设置为1,即可在RTP头部后面增加一个长度可变的扩展头。RTP扩展头格式如图6所示，图6是RTP扩展头格式示意图。
使用该方式1扩展后的携带可信签名的RTP报文格式与IP扩展方式1类似，这里不再赘述。
扩展方式2：包信息在数据包RTP头部传输，连接信息使用新RTP负载类型传递。
图5中的负载类型代表RTP包的包类型或负载类型。可通过扩展新的RTP包类型(PT)来承载可信签名信息。
当前PT定义可以参考目前协议中的相关描述，本申请实施例中不进行赘述。可在未使用PT值中，选一个表示RTP连接信息，例如，选择PT值35。
35：RTP Connect Information。
应理解，还可以选择其他未使用PT值，用于标识RTP连接信息，本申请中不一一举例说明。
该扩展方式2与IP扩展方式2类似，新的RTP payload type类似dummy IP报文，这里不再赘述。
方式四：GTP-U扩展。
GTP协议格式如图7所示，图7是GTP协议格式示意图，包括：
版本号(version)：用来标识GTP协议的版本；
协议类型(protocol type，PT)：用来标识是GTP(PT为1)还是GTP'(PT为0)，GTP'在3GPP TS 32.295中定义，并且GTP'的头部的含义和GTP头部的含义是不一样的；
扩展头标志(Extension Header flag)：用来说明Next Extension Header域是否有意义。当这一位为0的时候，Next Extension Header要么不存在，要么存在但是也不被使用。当 这一位为1的时候，Next Extension Header域要被解释和使用；
序列号标志(Sequence number flag)：用来说明Sequence number域是否有意义。当这一位为0的时候，Sequence number要么不存在，要么存在但是也不被使用。当这一位为1的时候，Sequence number域要被解释和使用。
N-协议数据单元(protocol data unit，PDU)标志(N-PDU Number flag，PN)：用来说明N-PDU Number域是否有意义。当这一位为0的时候，N-PDU Number要么不存在，要么存在但是也不被使用。当这一位为1的时候，N-PDU Number域要被解释和使用。
隧道端点标识(tunnel endpoint identifier，TEID)：在接收通用分组无线业务隧道协议-用户面(general packet radio service tunnelling protocol user，GTP-U)或通用分组无线业务隧道协议-控制面(general packet radio service tunnelling protocol control，GTP-C)协议的实体上定义了一个隧道端点。GTP隧道接收方在本地定义了一个TEID，这个TEID供发送端使用。
消息类型(Message Type)：定义了GTP的消息类型，包括GTP-C和GTP-U。
当GTP协议使用在5G网络是，3GPP规范的GTP-U协议对GTP协议中的扩展头字段进行了明确定义。
下行报文(UPF发给RAN)GTP-U格式：
Figure PCTCN2022070294-appb-000005
其中，QoS监控包(QoS monitoring packet，QMP)、SNP标识序列号(sequence number presence)、PPP标识寻呼政策(paging policy presence)、PPI标识寻呼政策指示(paging policy indicator)、RQI标识反射QoS指示(reflective QoS indicator)、下行发送时间戳(downlink Sending Time Stamp，DL Sending Time Stamp)表示、DL QFI Sequence Number标识下行QFI序列号。
上行报文(RAN发给UPF)GTP-U格式：
Figure PCTCN2022070294-appb-000006
Figure PCTCN2022070294-appb-000007
其中，DL Delay Ind.标识下行延时指示(downlink delay indicator)、上行延时指示(uplink delay indicator，UL Delay Ind.)、DL Sending Time Stamp Repeated表示下行发送时间戳重复、DL Received Time Stamp表示下行接收时间戳、UL Sending Time Stamp表示上行接收时间戳、DL Delay Result表示下行延时结果、UL Delay Result表示上行延时结果、UL QFI Sequence Number标识上行QFI序列号。
本申请实施例中，GTP-U协议可做如下扩展，支持携带源QoS信息。
下行报文(UPF发给RAN)GTP-U格式：
Figure PCTCN2022070294-appb-000008
上行报文(RAN发给UPF)GTP-U格式：
Figure PCTCN2022070294-appb-000009
Figure PCTCN2022070294-appb-000010
通过上述扩展，可在GTP-U报文头部携带源QoS信息。
GTP-U报文头部支持携带源QoS信息后，可分两种方式使用：
方式1：
GTP-U报文携带用户报文数据，头部源QoS信息字段包含连接信息和包信息。该方式1下，源QoS信息接口定义与IP扩展方式1类似。
方式2：
GTP-U报文携带用户报文数据，头部源QoS信息字段只包含包信息；或者
GTP-U报文不携带用户报文数据，头部源QoS信息字段只包含连接信息。
该方式2下，源QoS信息接口定义与IP扩展方式2类似，这里不再赘述。
方式五：新的传输协议扩展。
本申请实施例提供的方案还包括定义新的传输协议：
当前协议号143-252是未分配的。因此可定义协议号143为新传输协议，支持携带源QoS信息。
新传输协议格式定义：
Figure PCTCN2022070294-appb-000011
源端口：发送端计算机上使用新传输协议传输报文的应用程序的端口。
目的端口：接收端计算机上使用新传输协议接收数据的应用程序的端口。
头部长度：新传输协议报文头部长度。
校验值：该字段占据16位，可以检验源QoS信息与用户数据在传输过程中是否被损坏。
源QoS信息：填写源QoS内容。内容长度为“头部长度-8”
申请新的传输协议号，类似用户数据报协议(user datagram protocol，UDP)、TCP在IP层的协议号。
新传输协议中，有PayloadType，指示是数据报文还是连接指示报文，包信息随数据报文发送，连接信息随连接指示报文发送。
报文传输协议扩展支持携带源QoS信息后，还需要应用层在发送数据时指示源QoS信息，一般传输协议处理层将源QoS信息填写到最终发送到传输网络上的IP报文中。
应用层使用IP扩展方式携带源QoS信息。
Linux Socket编程中，发送IP(UDP/TCP)报文的函数为：
Ssize t send(int sockfd,const void*buff,size t nbytes,int flags)
第一个参数指定发送端套接字描述符、第二个参数指明一个存放应用程序要发送数据的缓冲区、第三个参数指明实际要发送的数据的字节数、第四个参数一般置0。
为支持源应用层指示源QoS信息，可新增Send_sqos函数：
ssize_t send_sqos(int sockfd,const void*buff,size_t nbytes,int flags,const void*sqos)
新增sQoS信息为源QoS信息存放处的内存指针，参数结构与协议扩展中源QoS信息定义类似，不再赘述。应用层可使用send_sqos函数发送数据，并指示数据的源QoS信息。IP层处理时，将源QoS信息打包到IP头部扩展字段即可。
应用层使用RTP扩展方式携带源QoS信息。
在Linux平台上进行实时传送编程时，一般会使用一些开放源代码的RTP库，如JLIBRTP。
JRTPLIB中RTP数据发送函数为：
int SendPacket(void*data,int len)；
为支持源应用层指示源QoS信息，可新增Send_sqos函数：
int SendPacketSQoS(void*data,int len，void*sqos)；
新增sQoS信息为源QoS信息存放处的内存指针，参数结构与协议扩展中源QoS信息定义类似，不再赘述。应用层可使用SendPacketSQoS函数发送数据，并指示数据的源QoS信息。RTP协议层处理时，将源QoS信息打包到RTP头部扩展字段即可。
进一步地，作为一种可能的实现方式：上述第一报文#1中包括的第一源QoS信息用于指示将第一报文#1映射到第一服务质量流QoS flow，第二报文#1中包括的第二源QoS信息用于指示将所述第二报文映射到第二QoS flow，第一QoS flow和第二QoS flow属于一个QoS flow组。
可以理解为，包括多个报文的连接中的至少一个报文分别映射到至少一个QoS flow，其中，至少一个QoS flow属于一个QoS flow组，第一QoS flow为该QoS flow组中与第一报文#1相对应的QoS flow，第二QoS flow为该QoS flow组中与第二报文#1相对应的QoS flow。
应理解，本申请实施例中，一个连接的报文能被映射到不同的QoS flow。为了提升对连接的管控力度，本申请对目前的5G QoS flow的模型可做相关扩展。
当前5G QoS flow模型如图8中的(a)所示，图8中的(a)是一种5G QoS flow模型示意图。
本申请实施例中，增加QoS flow组(QoS flow group，QFG)定义，扩展后QoS flow的模型的如图8中的(b)所示，图8中的(b)是本申请实施例提供的一种QoS flow模型示意图。具体地，对于图8中的(b)所示的QoS flow的模型作如下说明：
1)一个QFG内可包含多个QoS flow，一个QoS flow只能属于一个QFG；
2)一个连接的不同的报文只能映射到一个QFG内的不同的QoS flow；
3)QFG中可同时包含non-GRB、GRB、DC-GRB类型的Qos flow；
4)QFG支持总最大带宽(aggregate maximum bit rate，AMBR)参数，可对QFG中 所有non-GRB类型的Qos flow进行整体流控，提升对连接的管控能力。
进一步地，上述的QFG配置包括以下一个或多个：
QFG标识/索引(QoS flow group identifier，QFGI)：用于标识该QFG；
QFG包含的QoS flow(involved QoS flow)：用于指示该QFG包含哪些QoS flow；
至少一个CQI：用于指示该QFG与可以和哪些CQI实现映射；
AMBR：用于指示该QFG中所有non-GRB类型的Qos flow的最大带宽。
示例性地，该QFG配置可以通过控制面下发。
例如，5GC控制面将QFG配置下发给UPF后，UPF即可按连接级别的QoS特征映射到QFG，按包级别的QoS特征将报文映射到该QFG下的具体QoS flow。
作为另一种可能的实现方式：上述第一报文#1中包括的第一源QoS信息用于指示将第一报文#1映射到第一5QI，第二报文#1中包括的第二源QoS信息用于指示将所述第二报文映射到第二5QI，第一5QI和第二5QI属于一个QoS flow。
可以理解为，包括多个报文的连接中的至少一个报文分别映射到至少一个5QI，其中，至少一个5QI属于一个QoS flow，第一5QI为该QoS flow中与第一报文#1相对应的5QI，第二5QI为该QoS flow中与第二报文#1相对应的5QI。
本申请实施例中，提供另一种扩展的QoS flow的模型的如图8中的(c)所示，图8中的(c)是本申请实施例提供的另一种QoS flow模型示意图。具体地，对于图8中的(c)所示的QoS flow的模型作如下说明：
1)一个QoS flow内可包含多个5QI；
2)一个连接的报文只能映射到一个QoS flow内不同的5QI；
3)QoS flow中可同时包含non-GRB、GRB、DC-GRB类型的5QI；
4)QoS flow支持AMBR参数，可对QoS flow中所有5QI为non-GRB的报文进行整体流控，提升对连接的管控能力。
在图8中的(c)所示的扩展方式下，传输协议的扩展头域中需要增加5QI字段。根据连接级别的QoS特征映射到QFI，进一步根据包级别的QoS特征映射到该QFI下的具体5QI。
QoS flow定义增强，支持多5QI配置示例：
在图8中的(c)所示的扩展方式下，QoS flow的QoS配置包括以下一个或多个：
公共参数：对于每个QoS流，QoS配置文件应包括的QoS信息；
分配和保留优先级(allocation and retention Priority，ARP)；
AMBR：QoS flow下所有non-GRB类型的5QI最大带宽。
5G QoS Gurop[n]。
其中，5G QoS Group定义为：
5G QoS Identifier(5QI)；
反射QoS属性(reflective QoS attribute，RQA)，non-GRB类型的5QI特有参数；
GFBR，GRB类型的5QI特有参数；
MFBR，GRB类型的5QI特有参数。
应理解，图8中的(b)和图8中的(c)只是举例说明本申请实施例中适用的QoS flow的模型，对本申请实施例的保护范围不构成任何的限定，本申请实施例中一个连接的多个 不同的报文可以有不同的QoS要求，基于其他的QoS flow的模型映射到不同的QoS flow或5QI上，这里不再一一举例说明。
作为一种可能的实现方式，5G控制面网元AMF与SMF可以将包过滤规则发送给UE和UPF。
本申请实施例中为了实现源QOS驱动网络到5G QoS flow的精准映射，packet filters set可增加如下参数：
CQI和/或PQI。
当packet filters set中包括CQI和/或PQI时，可以基于接收到的IP报文中的源QoS信息，精准的将报文映射到对应的QoS flow。
需要说明的是，packet filters set中扩展CQI、PQI是可选的。如果没有CQI和/或PQI，则使用CQI、PQI对应的QoS特征与QoS flow中5QI的QoS特征比对，挑选5QI中最匹配的即可。
进一步地，数据网络生成第一报文#1之后，通过N6接口将第一报文#1发送给核心网设备(例如，UPF)，图2中的(a)所示的方法流程还包括：
S230，数据网络向核心网设备发送第一报文#1。
本申请实施例中对于各网元之间传输报文的方式不做限制，可以参考目前报文传输的规定，这里不进行赘述。
下文中以核心网设备为UPF为例进行说明。
进一步地，UPF接收到第一报文#1之后，将该第一报文#1映射到第一QoS flow#1，图2中的(a)所示的方法流程还包括：
S240，UPF将第一报文#1映射到第一QoS flow#1。
一种可能的实现方式，源QoS信息包括的包信息和连接信息都携带在第一报文#1中，则UPF根据第一报文#1中的源QoS信息，将IP报文映射到QoS特征最接近的第一QoS flow#1上；
另一种可能的实现方式，源QoS信息包括的包信息携带在第一报文#1中，源QoS信息包括的连接信息携带在dummy IP报文中，则UPF根据第一报文#1和dummy IP报文中的源QoS信息，将IP报文映射到QoS特征最接近的第一QoS flow#1上；
又一种可能的实现方式，源QoS信息包括的包信息携带在第一报文#1中，源QoS信息包括的连接信息经由控制面传输，则UPF根据第一报文#1和控制面传输的源QoS信息，将IP报文映射到QoS特征最接近的第一QoS flow#1上。
UPF将IP报文映射到第一QoS flow#1包括以下任意一种方式：
如果源QoS信息中使用CQI标识QoS要求，且UPF收到的packet filters set中包含CQI参数，则根据CQI进行映射；如果源QoS信息中使用PQI标识QoS要求，且UPF收到的packet filters set中包含PQI参数，则根据PQI进行映射；或者
如果源QoS信息中使用CQI标识QoS要求，UPF收到的packet filters set中不包含CQI，则使用CQI对应的QoS特征与各QoS flow中5QI的QoS特征比对，挑选最匹配的即可；如果源QoS信息中使用PQI标识QoS要求，UPF收到的packet filters set中不包含PQI，则使用PQI对应的QoS特征与各QoS flow中5QI的QoS特征比对，挑选最匹配的即可；或者
如果源QoS信息中直接携带具体QoS特征信息(例如，携带连接QoS特征信息和/或包QoS特征信息)，则用携带的QoS特征信息与各QoS flow中5QI的QoS特征比对，挑选最匹配的即可；或者
如果源QoS信息未携带包级别的QoS特征(例如，PQI和/或包QoS特征信息)但携带连接级别的QoS特征(例如，CQI和/或连接QoS特征信息)，则将连接级别的QoS特征作为报文的QoS特征标识报文的QoS要求，根据连接级别的QoS特征进行映射。
进一步地，UPF完成映射之后根据IP报文匹配的QoS flow的QoS要求，进行针对性保障与转发处理。图2中的(a)所示的方法流程还包括：
S250，UPF确定第三报文#1。
具体地，UPF基于第一QoS flow#1处理第一报文#1得到第三报文#1。可以理解为第三报文#1包括第一报文#1中需要传输的信息，但报文格式由满足N6接口传输的第一报文#1具备的报文格式转换为满足N3接口传输的报文格式。
例如，UPF根据连接信息中平均速率、频率、波峰频率、波峰大小等信息，预留内部转发资源(缓存队列、调度时间片等)，提升QoS达成率。
还例如，DN应用发送的视频流中，I帧报文的PQI为高等级QoS(丢包率0.01％)，P帧报文的PQI为中等级QoS(丢包率1％)。UPF将I帧数据放到高优先级转发队列，将P帧的数据放到中优先级转发队列。当系统或下一跳出口拥塞时，优先发送I帧数据报文。
又例如，UPF根据突发数据指示，可计算出简单转发突发数据和当前并发连接数据会导致瞬间流量峰值，超出后端传输设备(如RAN)处理和缓存能力，产生丢包。UPF可根据报文中源QoS信息进行错峰整形，在保障QoS总体达成率前提下，使用匀速与完整数据段传输的方式，优先发送时延要求高的报文，再发送时延要求低的报文，减少对下游的冲击。
进一步地，UPF需要将IP报文发送给接入网设备，则2(a)所示的方法流程还包括：
S260，UPF向接入网设备发送第三报文#1。
具体地，UPF将第一报文#1、源QoS信息封装为GTP-U协议格式，转发到N3口上，包括：
UPF将第一QoS flow#1的QFI填写到GTP-U协议头部。
需要说明的是，如何将QFI填写到GTP-U协议头部可以参考目前协议中的相关描述，这里不再赘述。
另外，UPF将第一报文#1中的包信息、连接信息拷贝到GTP-U协议头部扩展字段前文GTP协议扩展中有介绍，这里不再赘述。
示例性地，如果连接信息使用dummy IP报文方式传递，则将N6口上的dummy IP报文转换为N3口上基于GTP-U协议的dummy IP报文发送。
进一步地，RAN侧需要对接收到的第三报文#1进行处理得到需要发送给UE的第四报文#1，具体地，可以理解为第四报文#1包括第三报文#1中需要传输的信息，但报文格式由满足N3接口传输的第三报文#1具备的报文格式转换为满足空口传输的报文格式。
图2中的(a)所示的方法流程还包括：
S270，RAN确定第四报文#1。
具体地，RAN侧收到N3口第三报文#1后，从GTP扩展头域获得第三报文#1的连接信息和/或包信息，并结合报文所属的QoS flow，进行针对性保障与转发处理(如完整数据段调度等)，通过空口将处理得到的第四报文#1发送给UE。
图2中的(a)所示的方法流程还包括：
S280，RAN向UE发送第四报文#1。
需要说明的是，上述的步骤S230～S280以下行传输第一报文#1为例说明了下行报文的传输流程，下行传输连接中的其他报文(例如，上述的第二报文#1)与下行传输该第一报文#1类似，这里不再赘述。
图2中的(a)所示的流程为下行场景下，本申请实施例提供的传输报文的方法的示意性流程图。
上行报文传输场景下，如图2中的(b)所示，图2中的(b)是本申请实施例提供的另一种传输报文的方法的示意性流程图。
该传输报文的方法至少包括以下部分步骤。
S211，UE生成第一报文#2。
具体地，UE上的应用根据业务的QoS需要生成第一报文#2。
UE生成的第一报文#2与上述DN生成的第一报文#1类似，参考上述的S210中的相关描述，这里不再赘述。
需要说明的是，上述的第一报文#2可以是UE生成的多个报文中的任意一个报文，该多个报文的五元组信息相同，可以理解为该多个报文属于一个连接。该多个报文中的每个报文中都包括源QoS参数，且每个报文包括的源QoS信息用于对其所对应的报文进行QoS保障，多个报文包括的源QoS信息不相同。
为例便于区分，本申请实施例中上行报文传输流程中的报文增加“#2”，下行报文传输流程中的报文增加“#1”标识进行区分，应理解这种区分标识对本申请的保护范围不构成任何的限定。
进一步地，UE还可以生成连接中多个报文中的第二报文#2，图2中的(b)所示的方法流程还包括：
S221，UE生成第二报文#2。
UE生成的第二报文#2与上述DN生成的第二报文#1类似，参考上述的S220中的相关描述，这里不再赘述。
进一步地，UE生成报文之后，通发送给UE底层，UE底层接收到第一报文#2之后将该第一报文#2映射到第一QoS flow#2。图2中的(b)所示的方法流程还包括：
S231，UE将第一报文#2映射到第一QoS flow#2。
一种可能的实现方式，源QoS信息包括的包信息和连接信息都携带在第一报文#2中，UE根据第一报文#2中的源QoS信息，将IP报文映射到QoS特征最接近的第一QoS fow#2上；
另一种可能的实现方式，源QoS信息包括的包信息携带在第一报文#2中，源QoS信息包括的连接信息携带在dummy IP报文中，UE根据第一报文#2和dummy IP报文中的源QoS信息，将IP报文映射到QoS特征最接近的第一QoS flow#2上；
又一种可能的实现方式，源QoS信息包括的包信息携带在第一报文#2中，源QoS信 息包括的连接信息经由控制面传输，UE根据第一报文#2和控制面传输的源QoS信息，将IP报文映射到QoS特征最接近的第一QoS flow#2上。
UE将第一报文#2映射到第一QoS flow#2包括以下任意一种方式：
如果源QOS信息中使用CQI标识QoS要求，且UE收到的packet filters set中包含CQI，则根据CQI进行映射；如果源QoS信息中使用PQI标识QoS要求，且UE收到的packet filters set中包含PQI参数，则根据PQI进行映射；或者
如果源QOS信息中使用CQI标识QoS要求，UE收到的packet filters set中不包含CQI，则使用CQI对应的QoS特征与各QoS flow中5QI的QoS特征比对，挑选最匹配的即可；如果源QOS信息中使用PQI标识QoS要求，UE收到的packet filters set中不包含PQI，则使用PQI对应的QoS特征与各QoS flow中5QI的QoS特征比对，挑选最匹配的即可；或者
如果源QOS信息中直接携带具体QoS特征信息(例如，携带连接QoS特征信息和/或包QoS特征信息)，则用携带的QoS特征信息与各QoS flow中5QI的QoS特征比对，挑选最匹配的即可；或者
如果源QoS信息未携带PQI或包QoS特征信息但携带CQI或连接QoS特征信息，则将连接级别的QoS特征作为报文QoS特征标识报文的QoS要求，根据连接级别的QoS特征进行映射。
进一步地，UE完成映射之后根据IP报文匹配的第一QoS flow#2的QoS要求，进行针对性保障与转发处理。向RAN发送第一报文#2，图2中的(b)所示的方法流程还包括：
S241，UE向RAN发送第一报文#2。
UE底层使用空口传输协议封装用户面IP报文，并将该报文匹配的第一QoS flow#2的QFI填写到空口数据包头部。
进一步地，UE底层根据用户面报文中的连接信息与包信息，并结合报文所属第一QoS flow#2的QoS要求，进行针对性保障与转发处理(如完整数据段调度等)，将第一报文#2映射到不同承载标准的DRB上发送给RAN。
例如，UE发送的视频流中，I帧报文的PQI为高等级QoS(丢包率0.01％)，P帧报文的PQI为中等级QoS(丢包率1％)。UE底层将I帧的数据报文匹配到高等级DRB承载上(如支持重传、支持冗余)，将P帧的数据报文匹配到中等级DRB承载上(无重传、无冗余)；
还例如，UE底层根据包信息中的数据完整性信息，在收到视频一帧所有报文后，再一次性通过空口发送给RAN，降低数据段整体传输时延，提升空口利用率；
又例如，连接信息中指示10ms后有突发事件的3M byte数据需要发送，UE底层根据指示提前与基站协商分配10ms后空口传输资源。当UE底层收到突发事件数据后，可立即使用预申请好的空口资源传输，降低传输时延，提升空口资源利用效率。
进一步地，RAN侧需要对接收到的第一报文#2进行处理得到需要发送给UPF的第三报文#2，具体地，可以理解为第三报文#2包括第一报文#2中需要传输的信息，但报文格式由满足空口传输的第一报文#2具备的报文格式转换为满足N3接口传输的报文格式。
图2中的(b)所示的方法流程还包括：
S251，RAN确定第三报文#2。
RAN收到UE发送的报文后，用GTP-U协议封装用户面IP报文，将从空口数据包头解析出报文所属第一QoS flow#2的QFI填写到GTU-U协议头部字段，然后将报文通过N3接口将第三报文#2发送给UPF。
图2中的(b)所示的方法流程还包括：
S261，RAN向UPF发送第三报文#2。
进一步地，UPF侧需要对接收到的第三报文#2进行处理得到需要发送给数据网络的第四报文#2，具体地，可以理解为第四报文#2包括第三报文#2中需要传输的信息，但报文格式由满足N6接口传输的第三报文#2具备的报文格式转换为满足N6接口传输的报文格式。
图2中的(b)所示的方法流程还包括：
S271，UPF确定第四报文#2。
UPF侧收到N3口第三报文#2后，从用户面IP报文扩展字段获得数据报文的连接信息与包信息，并结合报文所属的第一QoS flow#2，进行针对性保障与转发处理(如完整数据段调度等)确定第四报文#2，通过N6接口将第四报文#2发送给Internet。图2(b)所示的方法流程还包括：
S281，UPF向数据网络发送第四报文#2。
需要说明的是，上述的步骤S231～S281以下行传输第一报文#2为例说明了上行报文的传输流程，上行传输连接中的其他报文(例如，上述的第二报文#2)与上行传输该第一报文#2类似，这里不再赘述。
应理解，图2中的(a)和图2中的(b)所示的方法中，报文生成端在生成报文的时候即在报文中携带源QoS信息，本申请提供一种可能的实现方式，报文生成设备在生成报文的时候可以无需携带源QoS信息，传输节点识别出部分数据特征，并映射为源QoS信息。
具体地，在发送端未携带源QoS信息时，传输路径上的节点(报文接收设备)可通过流量分析、报文解析或智能感知等技术，自行识别出部分数据特征，并映射为源QoS信息填写到报文中发送给后端设备，实现QoS保障。
例如，RAN或者UPF根据流量分析，可感知出视频流中的I帧、P帧的周期信息，并将I帧、P帧的周期信息映射为源QoS信息填写到报文中发送给后端设备。
可选地，只需在传输路径上的关键节点实施主动数据特征感知即可，无需所有节点都实施。例如，UPF实施上述的主动数据特征感知。
本申请还提供一种反射QoS机制。如图9所示，图9是本申请实施例提供的一种反射QoS机制示意性流程图。
该反射QoS机制至少包括以下部分步骤。
S910，核心网设备向接入网设备发送连接级别的QoS特征和/或包级别的QoS特征。
示例性地，核心网设备(例如，UPF)在N3接口使用GTP-U协议发送用户面IP报文给接入网设备时，在GTP-U头部扩展字段携带了报文的CQI和/或PQI信息。
应理解，核心网设备还可以通过其他方式向接入网设备发送连接级别的QoS特征和/或包级别的QoS特征，这里不一一举例说明。
另外，连接级别的QoS特征还可以是连接QoS特征信息、包级别的QoS特征还可以 是包QoS特征信息。
进一步地，接入网设备需要将接收到的连接级别的QoS特征和/或包级别的QoS特征发送给用户设备，图9所示的方法流程还包括：
S920，接入网设备向用户设备发送连接级别的QoS特征和/或包级别的QoS特征。
示例性地，接入网设备使用空口协议栈封装用户面IP报文，并发送给用户设备。空口协议栈的SDAP协议头中的RDI字段填写为1，指示用户设备触发QoS反射处理。
可选地，空口协议栈的SDAP协议头中的QFI字段填写为从GTP-U协议中解析出的CQI。
可选地，空口协议栈的SDAP协议头的PQI扩展字段填写为从GTP-U协议中解析出的PQI。
SDAP协议头扩展方式1：直接增加一个字节扩展字段。
Bit7 Bit6 Bit0-5
RDI RQI QFI
保留 保留 PQI
SDAP协议头扩展方式2：为保障兼容性，添加2个字节的可选字段，当QFI全0或者全1时表示有扩展字段。在第一个字节的扩展字段中填写真实的QFI；第二个字节的扩展字段中填写PQI。
Bit7 Bit6 Bit0-5
RDI RQI QFI
保留 保留 Real-QFI
保留 保留 PQI
应理解，接入网设备还可以通过其他方式向用户设备发送连接级别的QoS特征和/或包级别的QoS特征，这里不一一举例说明。
用户设备接收到连接级别的QoS特征和/或包级别的QoS特征可以记录该连接级别的QoS特征和/或包级别的QoS特征。图9所示的方法流程还包括：
S930，用户设备记录连接级别的QoS特征和/或包级别的QoS特征。
例如，用户设备收到报文后，发现RDI指示为1时，记录五元组、CQI、QFI信息、PQI和DRB的映射关系，作为通过反射QoS机制学习到的QoS规则(目前反射QoS机制只记录报文五元组、QFI信息、DRB映射关系)。
具体地，用户设备可以通过学习到的QoS规则进行报文发送，图9所示的方法流程还包括：
S940，用户设备向接入网设备发送报文。
例如，用户设备在发送上行报文时，可使用通过反射QoS机制学习到的PQI信息的QoS规则进行匹配，将报文匹配到合适的QoS flow、DRB上发送。
还例如，用户设备待发送的上行报文的QoS特征中的PQI在UE记录的PQI中能够找到对应的PQI#1，则用户设备可以将该待发送的上行报文在PQI#1对应的QoS flow、DRB上发送，其中，PQI#1可以是与待发送的上行报文的QoS特征中的PQI相同的PQI，或最接近的PQI。
本申请还提供一种QoS flow策略微调整控制方案，可以动态调整QoS flow对应的资 源，具体地通过增强QoS flow的QoS配置实现。
一种可能的实现方式，该实施例中QoS flow的QoS配置包括以下一个或多个：
公共参数：对于每个QoS流，QoS配置文件应包括的QoS信息；
5QI；
分配和保留优先级(allocation and retention Priority，ARP)；
反射QoS属性,non-GRB类型的5QI特有参数；
最大保障带宽MGFBR；
MFBR，GRB类型的5QI特有参数。
其中，MGFBR表示微控制模式下最大保障带宽，即通过微控制模式，为该QoS flow预留的资源的保障带宽小于或者等于(或者小于)MGFBR间动态变化。当UPF和/或RAN在该QoS flow上收到连接中的报文时：
从报文和/或GTP-U扩展头域中获得源QoS信息，从中获得连接的平均速率。
另一种可能的实现方式，该实施例中QoS flow的QoS配置包括以下一个或多个：
公共参数：对于每个QoS流，QoS配置文件应包括的QoS信息；
5QI；
分配和保留优先级(allocation and retention Priority，ARP)；
反射QoS属性,non-GRB类型的5QI特有参数；
GFBR，GRB类型的5QI特有参数；
最大保障带宽(maximum guaranteed flow bit rate MGFBR，MGFBR)；
MFBR，GRB类型的5QI特有参数。
其中，MGFBR表示微控制模式下最大保障带宽，即通过微控制模式，为该QoS flow预留的资源的实际保障带宽可在GFBR与MGFBR间动态变化。GFBR用于调整为QoS flow预留的资源，该QoS flow的保障带宽大于或者等于该GFBR且小于或者等于该MGFBR。当UPF和/或RAN在该QoS flow上收到连接中的报文时：
从报文和/或GTP-U扩展头域中获得源QoS信息，从中获得连接的平均速率。
例如，连接平均速率和当前GFBR实际速率之和不大于MGFBR，则为连接预留足够带宽资源，刷新当前GFBR实际速率为新连接平均速率和当前GFBR实际速率之和；
还例如，当UPF和/或RAN检测到该QoS flow上某条已有连接已经失效(断连)、连接平均速率变化时，处理策略类似。
可选地，UPF和/或RAN可在报文的源QoS信息中或Dummy IP报文中，添加转发节点标识、转发接口带宽预留成功标记，转发节点当前预留带宽等信息同时收发两端以及网络中其他传输节点。
本申请还提供另一种QoS flow策略微调整控制方案，可以动态指示是否预留QoS flow对应的资源，具体地通过增强QoS flow的QoS配置实现。
该实施例中QoS flow的QoS配置包括以下一个或多个：
公共参数：对于每个QoS流，QoS配置文件应包括的QoS信息；
5QI；
分配和保留优先级(allocation and retention Priority，ARP)；
指示信息；
反射QoS属性,non-GRB类型的5QI特有参数；
GFBR，GRB类型的5QI特有参数；
最大保障带宽(maximum guaranteed flow bit rate MGFBR，MGFBR)；
MFBR，GRB类型的5QI特有参数。
其中，指示信息用于指示是否预留QoS flow对应的资源。指示信息可以是动态创建指示(dynamic creation indication，DCI)，DCI表示UFP和/或RAN收到该QoS flow的配置后，是否预留该QoS flow对应的资源(或者说是否缺省创建该QoS flow对应的实例)实例。缺省值为真(TRUE)，支持微控制模式动态创建的QoS flow，DCI设为假(FALSE)。
需要说明的是，本申请实施例中将指示信息称为DCI只是举例，对本申请的保护范围不构成任何的限定，称为其他名称也可以。
具体地，UPF和/或RAN收到5G控制面下发的QoS配置后，对DCI指示为True的QoS flow主动创建实例；对DCI指示为FALSE的QoS flow不创建实例。
当UPF和/或RAN收到IP报文时，首先确定该IP报文能否映射到已有的非缺省QoS flow实例上；若能，则按现有流程处理；若否，判断该IP报文能否映射到QoS配置中未实例化且DCI为FALSE的QoS flow，若能，实例化该QoS flow，并使用该QoS flow将报文转发出去；若否，使用缺省QoS flow将该报文转发出去。
另外，目前传输网络中，各传输节点或转发设备不对端到端QoS达成负责，只是根据报文QoS指示，在本节点处理、转发时尽力进行针对性保障。当传输路径中有某些节点无法达成QoS要求时，只能依靠收发两端的容错机制解决。
本申请提供一种保障机制，传输节点可结合端到端传输网络损伤模型与网络状态预测技术，通过主动保障机制，提升端到端QoS达成率：
例如，某个传输节点感知到后端网络因干扰存在周期性偶发性丢包时，该传输节点对因干扰预计无法达成端到端时延目标的报文，主动采用干扰周期内报文重复发送、错开干扰周期重发等机制，降低传输时延(相比收发两端通过确认重发机制)，提升端到端QoS达成率；
还例如，某个传输节点感知到后端网络的丢包率已经无法满足端到端包错误率目标的报文，主动采用FEC冗余编码方式提升数据抗丢包能力，提升端到端QoS达成率。
可选地，只需在传输路径上的关键传输节点实施上述的保障机制即可，无需所有传输节点都实施。例如，UPF实施上述的保障机制。
上述方法实施例中，上述各过程的序列号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。并且有可能并非要执行上述方法实施例中的全部操作。
应理解，上述方法实施例中用户设备和/或网络设备可以执行施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例还可以包括执行其它操作或者各种操作的变形。
可以理解的是，上述方法实施例中，由用户设备实现的方法，也可以由可用于用户设备的部件(例如芯片或者电路等)实现，由网络设备实现的方法，也可以由可用于网络设备的部件实现。
还应理解，在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施 例之间的术语和/或描述可以具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
上面结合图2中的(a)和图2中的(b)的详细介绍了本申请实施例中的传输报文的方法，下面结合图10-图13详细介绍本申请实施例提供的传输报文的装置。
参见图10，图10是本申请提供的传输报文的装置1000的示意图。如图10所示，装置1000包括处理单元1010、接收单元1020和发送单元1030。
处理单元1010，用于生成多个报文，该多个报文的五元组信息相同，该多个报文中的每个报文包括源服务质量QoS信息，该每个报文包括的源QoS信息用于对其所对应的报文进行QoS保障，该多个报文包括的源QoS信息不相同。
发送单元1030，用于发送该多个报文。
装置1000和方法实施例中的用户设备或数据网络对应，用于生成报文。装置1000可以是方法实施例中的用户设备或数据网络，或者方法实施例中的用户设备或数据网络内部的芯片或功能模块。装置1000的相应单元用于执行图2中的(a)和图2中的(b)以及图9所示的方法实施例中由用户设备或数据网络执行的相应步骤。
其中，装置1000中的处理单元1010用于执行方法实施例中用户设备或数据网络对应与处理相关的步骤。装置1000中的接收单元1020执行方法实施例中用户设备或数据网络接收的步骤。装置1000中的发送单元1030，用于执行用户设备或数据网络发送的步骤。
接收单元1020和发送单元可以组成收发单元，同时具有接收和发送的功能。其中，处理单元1010可以是至少一个处理器。发送单元可以是发射器或者接口电路，接收单元1020可以是接收器或者接口电路。接收器和发射器可以集成在一起组成收发器或者接口电路。
可选的，装置1000还可以包括除存储单元，该存储单元用于存储数据和/或信令，处理单元1010、发送单元和接收单元1020可以与存储单元交互或者耦合，例如读取或者调用存储单元中的数据和/或信令，以使得上述实施例的方法被执行。
以上各个单元可以独立存在，也可以全部或者部分集成。
参见图11，图11是适用于本申请实施例的报文生成设备1100的结构示意图，可以用于实现上述下行报文传输场景中数据网络的功能，或者还可以用于实现上述上行报文传输场景中用户设备的功能。
该报文生成设备1100包括处理器1101，存储器1102与收发器1103，其中，存储器1102中存储指令或程序，处理器1102和收发器1103用于执行或调用存储器1102中存储的指令或程序，以使得报文生成设备1100实现上述传输报文的方法中的报文生成设备的功能。存储器1102中存储的指令或程序被执行时，收发器1103用于执行图10所示的实施例中的发送单元1030和接收单元1020执行的操作，处理器1102用于执行图10所示的实施例中的处理单元1010执行的操作。
本领域技术人员可以理解，为了便于说明，图11仅示出了一个存储器和处理器。在实际的用户设备中，可以存在多个处理器和存储器。存储器也可以称为存储介质或者存储设备等，本申请实施例对此不做限制。
参见图12，图12是本申请提供的另一种传输报文的装置1200的示意图。如图12所示，装置1200包括接收单元1210、发送单元1220和处理单元1230。
接收单元1210，用于接收多个报文，该多个报文的五元组信息相同，该多个报文中的每个报文包括源服务质量QoS信息，该每个报文包括的源QoS信息用于对其所对应的QoS报文进行QoS保障，该多个报文包括的源QoS信息不相同。
处理单元1230，用于基于该多个报文包括的源QoS信息处理该多个报文。
装置1200和方法实施例中的核心网设备(例如，UPF)或接入网设备对应，装置1200可以是方法实施例中的UPF或接入网设备，或者方法实施例中的UPF或接入网设备内部的芯片或功能模块。装置1200的相应单元用于执行图2中的(a)和图2中的(b)以及图9所示的方法实施例中由UPF或接入网设备执行的相应步骤。
装置1200中的发送单元1220执行方法实施例中UPF或接入网设备发送的步骤，装置1200中的接收单元1210，用于执行UPF或接入网设备接收的步骤，装置1200还可以包括处理单元1230，用于执行UPF或接入网设备内部对应与处理相关的步骤。
可选的，装置1200还可以包括存储单元，用于存储数据和/或信令，处理单元1230、获取单元1220和接收单元1210可以与存储单元交互或者耦合，例如读取或者调用存储单元中的数据和/或信令，以使得上述实施例的方法被执行。
以上各个单元可以独立存在，也可以全部或者部分集成。
参见图13，图13是适用于本申请实施例的报文接收设备1300的结构示意图，可以用于实现上述下行报文传输场景中核心网设备、接入网设备以及用户设备的功能，或者还可以用于实现上述上行报文传输场景中核心网设备、接入网设备以及数据网络的功能。
该报文接收设备1300包括处理器1301，存储器1302与收发器1303，其中，存储器1302中存储指令或程序，处理器1302和收发器1303用于执行或调用存储器1302中存储的指令或程序，以使得报文接收设备1300实现上述传输报文的方法中的报文接收设备的功能。存储器1302中存储的指令或程序被执行时，收发器1303用于执行图12所示的实施例中的发送单元1220和接收单元1210执行的操作，处理器1302用于执行图12所示的实施例中的处理单元1230执行的操作。
本申请实施例还提供一种通信系统，其包括前述的报文生成设备和报文接收设备。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行上述如图2中的(a)和图2中的(b)以及图9所示的方法中用户设备执行的各个步骤。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行上述如图2中的(a)和图2中的(b)以及图9所示的方法中接入网设备执行的各个步骤。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行上述如图2中的(a)和图2中的(b)以及图9所示的方法中核心网设备执行的各个步骤。
本申请还提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行如图2中的(a)和图2中的(b)以及图9所示的方法中用户设备执行的各个步骤。
本申请还提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行如图2中的(a)和图2中的(b)以及图9所示的方法中接入网设 备执行的各个步骤。
本申请还提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行如图2中的(a)和图2中的(b)以及图9所示的方法中核心网设备执行的各个步骤。
本申请还提供一种芯片，包括处理器。该处理器用于读取并运行存储器中存储的计算机程序，以执行本申请提供的传输报文的方法中由用户设备执行的相应操作和/或流程。可选地，该芯片还包括存储器，该存储器与该处理器通过电路或电线与存储器连接，处理器用于读取并执行该存储器中的计算机程序。进一步可选地，该芯片还包括通信接口，处理器与该通信接口连接。通信接口用于接收处理的数据和/或信息，处理器从该通信接口获取该数据和/或信息，并对该数据和/或信息进行处理。该通信接口可以是该芯片上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
本申请还提供一种芯片，包括处理器。该处理器用于读取并运行存储器中存储的计算机程序，以执行本申请提供的传输报文的方法中由接入网设备执行的相应操作和/或流程。可选地，该芯片还包括存储器，该存储器与该处理器通过电路或电线与存储器连接，处理器用于读取并执行该存储器中的计算机程序。进一步可选地，该芯片还包括通信接口，处理器与该通信接口连接。通信接口用于接收处理的数据和/或信息，处理器从该通信接口获取该数据和/或信息，并对该数据和/或信息进行处理。该通信接口可以是该芯片上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。所述处理器也可以体现为处理电路或逻辑电路。
本申请还提供一种芯片，包括处理器。该处理器用于读取并运行存储器中存储的计算机程序，以执行本申请提供的传输报文的方法中由核心网设备执行的相应操作和/或流程。可选地，该芯片还包括存储器，该存储器与该处理器通过电路或电线与存储器连接，处理器用于读取并执行该存储器中的计算机程序。进一步可选地，该芯片还包括通信接口，处理器与该通信接口连接。通信接口用于接收处理的数据和/或信息，处理器从该通信接口获取该数据和/或信息，并对该数据和/或信息进行处理。该通信接口可以是该芯片上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。所述处理器也可以体现为处理电路或逻辑电路。
上述的芯片也可以替换为芯片系统，这里不再赘述。
本申请中的术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装 置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
另外，本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系；本申请中术语“至少一个”，可以表示“一个”和“两个或两个以上”，例如，A、B和C中至少一个，可以表示：单独存在A，单独存在B，单独存在C、同时存在A和B，同时存在A和C，同时存在C和B，同时存在A和B和C，这七种情况。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (46)

  1. 一种传输报文的方法，其特征在于，包括：
    生成多个报文，所述多个报文的五元组信息相同，所述多个报文中的每个报文包括源服务质量QoS信息，所述每个报文包括的源QoS信息用于对其所对应的报文进行QoS保障，所述多个报文包括的源QoS信息不相同；
    发送所述多个报文。
  2. 如权利要求1所述的方法，其特征在于，所述多个报文属于同一个连接，所述多个报文包括的源QoS信息不相同包括：
    所述连接中的第一报文中包括的第一源QoS信息和所述连接中的第二报文中包括的第二源QoS信息不同，
    其中，所述第一报文和所述第二报文为所述多个报文中的任意两个报文。
  3. 如权利要求2所述的方法，其特征在于，所述第一源QoS信息包括第一QoS特征和第一数据特征，所述第一QoS特征用于指示所述第一报文的QoS需求，所述第一数据特征表示所述第一报文的传输特性，
    所述第二源QoS信息包括第二QoS特征和第二数据特征，所述第二QoS特征用于指示所述第二报文的QoS需求，所述第二数据特征表示所述第二报文的传输特性。
  4. 如权利要求3所述的方法，其特征在于，所述连接中的第一报文中包括的第一源QoS信息和所述连接中的第二报文中包括的第二源QoS信息不同包括：
    所述第一数据特征和所述第二数据特征不同，和/或，所述第一QoS特征和所述第二QoS特征不同。
  5. 如权利要求3或4所述的方法，其特征在于，所述第一数据特征包括连接级别的数据特征和/或包级别的数据特征，
    其中，所述连接级别的数据特征表示所述连接中包括的多个报文的传输特性，所述包级别的数据特征表示所述第一报文的传输特性，
    所述第一QoS特征包括连接级别的QoS特征和/或包级别的QoS特征，
    其中，所述连接级别的QoS特征用于指示所述连接中包括的多个报文的QoS需求，所述包级别的QoS特征用于指示所述第一报文的QoS需求。
  6. 如权利要求5所述的方法，其特征在于，所述连接级别的数据特征包括以下一项或者多项：
    平均速率、持续时长、频率、大小、时延预算、波峰频率、波峰大小、波峰时延预算、波峰发送时间、突发事件类型、预计突发事件发生时间、预计突发事件报文量和突发事件报文时延预算，
    其中，所述平均速率指示所述连接中的报文平均发送速率、所述持续时长指示所述连接持续时长，所述频率指示报文发送频率、所述大小指示每频次发送报文均值、所述时延预算指示一个周期内所有报文全部传递到接收端耗时预算、所述波峰频率指示报文的波峰产生频率、所述波峰时延预算指示报文波峰全部传递到接收端耗时预算、所述波峰发送时间指示所述报文波峰发送的时间、所述突发事件类型指示突然发生的时间所属的类别、所 述预计突发事件发生时间指示突发事件报文预计到达时间、所述预计突发事件报文量指示突然事件传输的报文量、所述突发事件报文时延预算指示突发事件报文传输到接收端耗时预算。
  7. 如权利要求5或6所述的方法，其特征在于，所述包级别的数据特征包括以下一项或者多项：
    数据块序号、数据块大小、包位置和数据块时延预算，
    其中，所述数据块序号指示所述第一报文所属数据块编号、数据块大小指示所述第一报文所属数据块大小、所述包位置指示所述第一报文在所属数据块的位置、所述数据块时延预算指示所述第一报文传输到接收端耗时预算。
  8. 如权利要求5至7中任一项所述的方法，其特征在于，所述连接级别的QoS特征包括连接QoS特征指示CQI和/或连接QoS特征信息，所述包级别的QoS特征包括包QoS指示PQI和/或包QoS特征信息。
  9. 如权利要求5至8中任一项所述的方法，其特征在于，所述连接级别的QoS特征信息或包级别的QoS特征信息表示的QoS特征包括以下一项或者多项：
    资源类型、优先级、时延预算和错误率。
  10. 如权利要求5至9中任一项所述的方法，其特征在于，所述第一报文中包括第一源QoS信息包括：
    所述第一报文中包括连接级别的信息和包级别的信息；或者，
    所述第一报文中包括所述包级别的信息，虚拟互联网协议dummy IP包中包括所述连接级别的信息；或者，
    所述第一报文中包括所述包级别的信息，所述连接级别的信息通过控制面传输，
    其中，所述连接级别的信息包括所述连接级别的数据特征和所述连接级别的QoS特征，所述包级别的信息包括所述包级别的接数据特征和所述包级别的QoS特征。
  11. 如权利要求2至10中任一项所述的方法，其特征在于，所述第一源QoS信息用于指示将所述第一报文映射到第一服务质量流QoS flow，所述第二源QoS信息用于指示将所述第二报文映射到第二QoS flow，所述第一QoS flow和所述第二QoS flow属于一个QoS flow组。
  12. 如权利要求2至10中任一项所述的方法，其特征在于，所述第一源QoS信息用于指示将所述第一报文映射到第一5G网络的服务质量标识符5QI，所述第二源QoS信息用于指示将所述第二报文映射到第二5QI，所述第一5QI和所述第二5QI属于一个QoS flow。
  13. 如权利要求2至12中任一项所述的方法，其特征在于，所述第一源QoS信息用于指示将所述第一报文映射到第一服务质量流QoS flow，所述第一QoS flow的QoS配置包括：
    最大保障带宽MGFBR；
    所述MGFBR用于调整为所述第一QoS flow预留的资源，所述第一QoS flow的保障带宽小于或者等于所述MGFBR。
  14. 如权利要求13所述的方法，其特征在于，所述第一QoS flow的QoS配置还包括：
    最小保障带宽GFBR，所述GFBR用于调整为所述第一QoS flow预留的资源，所述第一QoS flow的保障带宽大于或者等于所述GFBR且小于或者等于所述MGFBR。
  15. 如权利要求2至14中任一项所述的方法，其特征在于，所述第一源QoS信息用于指示将所述第一报文映射到第一服务质量流QoS flow，所述第一QoS flow的QoS配置包括：
    指示信息，所述指示信息用于指示是否预留所述第一QoS flow对应的资源。
  16. 如权利要求13至15中任一项所述的方法，其特征在于，所述第一源QoS信息用于指示将所述第一报文映射到第一QoS flow包括：
    所述第一源QoS信息中包括QoS特征，所述QoS特征与所述QoS flow中的5QI指示的QoS特征相对应。
  17. 如权利要求1至16中任一项所述的方法，其特征在于，所述方法还包括：
    确定传输所述第一报文的路径中传输节点的状态；
    当至少一个所述输节点的状态满足预设条件时，启动主动保障机制。
  18. 如权利要求17所述的方法，其特征在于，所述当至少一个所述输节点的状态满足预设条件时，启动主动保障机制包括以下一项或者多项：
    当所述至少一个所述输节点存在丢包时，重复发送所述第一报文；或者
    当所述至少一个所述输节点丢包率大于预设值时，采用前向纠错FEC冗余编码方式编码所述第一报文。
  19. 一种传输报文的方法，其特征在于，包括：
    接收多个报文，所述多个报文的五元组信息相同，所述多个报文中的每个报文包括源服务质量QoS信息，所述每个报文包括的源QoS信息用于对其所对应的QoS报文进行QoS保障，所述多个报文包括的源QoS信息不相同；
    基于所述多个报文包括的源QoS信息处理所述多个报文。
  20. 如权利要求19所述的方法，其特征在于，所述多个报文属于同一个连接，所述多个报文包括的源QoS信息不相同包括：
    所述连接中的第一报文中包括的第一源QoS信息和所述连接中的第二报文中包括的第二源QoS信息不同，
    其中，所述第一报文和所述第二报文为所述多个报文中的任意两个报文。
  21. 如权利要求20所述的方法，其特征在于，
    所述第一源QoS信息包括第一QoS特征和第一数据特征，所述第一数据特征表示所述第一报文的传输特性，所述第二源QoS信息包括第二QoS特征和第二数据特征，所述第二数据特征表示所述第二报文的传输特性，所述方法还包括：
    根据所述第一QoS特征确定所述第一报文的QoS需求；
    根据所述第二QoS特征确定所述第二报文的QoS需求；
    基于所述多个报文包括的源QoS信息处理所述多个报文包括：
    根据所述第一报文的QoS需求和所述第一数据特征调度所述第一报文的资源；
    根据所述第二报文的QoS需求和所述第二数据特征调度所述第二报文的资源。
  22. 如权利要求21所述的方法，其特征在于，所述连接中的第一报文中包括的第一源QoS信息和所述连接中的第二报文中包括的第二源QoS信息不同包括：
    所述第一数据特征和所述第二数据特征不同，和/或，所述第一QoS特征和所述第二QoS特征不同。
  23. 如权利要求22所述的方法，其特征在于，所述调度所述第一报文的资源和所述调度所述第二报文的资源不同。
  24. 如权利要求21至23中任一项所述的方法，其特征在于，所述第一数据特征包括连接级别的数据特征和/或包级别的数据特征，所述方法还包括：
    根据所述连接级别的数据特征确定所述连接中包括的多个报文的传输特性；
    根据所述包级别的数据特征确定所述第一报文的传输特性。
  25. 如权利要求21至24中任一项所述的方法，其特征在于，所述第一QoS特征包括连接级别的QoS特征，
    所述方法还包括：
    根据所述连接级别的QoS特征确定所述多个报文中除所述第一报文和所述第二报文之外的第三报文的QoS需求。
  26. 如权利要求24或25所述的方法，其特征在于，所述连接级别的数据特征包括以下一项或者多项：
    平均速率、持续时长、频率、大小、时延预算、波峰频率、波峰大小、波峰时延预算、波峰发送时间、突发事件类型、预计突发事件发生时间、预计突发事件报文量和突发事件报文时延预算，
    其中，所述平均速率指示所述连接中的报文平均发送速率、所述持续时长指示所述连接持续时长，所述频率指示报文发送频率、所述大小指示每频次发送报文均值、所述时延预算指示一个周期内所有报文全部传递到接收端耗时预算、所述波峰频率指示报文的波峰产生频率、所述波峰时延预算指示报文波峰全部传递到接收端耗时预算、所述波峰发送时间指示所述报文波峰发送的时间、所述突发事件类型指示突然发生的时间所属的类别、所述预计突发事件发生时间指示突发事件报文预计到达时间、所述预计突发事件报文量指示突然事件传输的报文量、所述突发事件报文时延预算指示突发事件报文全部传输到接收端耗时预算。
  27. 如权利要求24至26中任一项所述的方法，其特征在于，所述包级别的数据特征包括以下一项或者多项：
    数据块序号、数据块大小、包位置和数据块时延预算，
    其中，所述数据块序号指示所述第一报文所属数据块编号、数据块大小指示所述第一报文所属数据块大小、所述包位置指示所述第一报文在所属数据块的位置、所述数据块时延预算指示所述第一报文传输到接收端耗时预算。
  28. 如权利要求25至27中任一项所述的方法，其特征在于，所述连接级别的QoS特征包括连接QoS特征指示CQI和/或连接QoS特征信息，所述包级别的QoS特征包括包QoS指示PQI和/或包QoS特征信息。
  29. 如权利要求25至28中任一项所述的方法，其特征在于，所述连接级别的QoS特征或包级别的QoS特征表示的QoS特征包括以下一项或者多项：
    资源类型、优先级、时延预算和错误率。
  30. 如权利要求29所述的方法，其特征在于，所述方法还包括：
    接收来自核心网设备的包过滤规则，所述包过滤规则中包括所述CQI和/或所述PQI；
    根据所述CQI和/或所述PQI将所述第一报文映射至第一服务质量流QoS flow。
  31. 如权利要求29或30所述的方法，其特征在于，所述方法还包括：
    接收反射触发指示RDI和所述PQI；
    根据所述RDI记录所述PQI，所述PQI用于指示将第四报文映射至第三QoS flow；
    其中，所述第四报文为待发送的报文，所述第三QoS flow中的5QI指示的QoS特征与所述PQI相对应。
  32. 如权利要求25至31中任一项所述的方法，其特征在于，所述第一报文中包括第一源QoS信息包括：
    所述第一报文中包括连接级别的信息和包级别的信息；或者，
    所述第一报文中包括所述包级别的信息，虚拟互联网协议dummy IP包中包括所述连接级别的信息；或者，
    所述第一报文中包括所述包级别的信息，所述连接级别的信息通过控制面传输，
    其中，所述连接级别的信息包括所述连接级别的数据特征和所述连接级别的QoS特征，所述包级别的信息包括所述包级别的接数据特征和所述包级别的QoS特征。
  33. 如权利要求20至32中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述第一源QoS信息将所述第一报文映射到第一服务质量流QoS flow；
    根据所述第二源QoS信息将所述第二报文映射到第二QoS flow；
    其中，所述第一QoS flow和所述第二QoS flow属于一个QoS flow组。
  34. 如权利要求20至32中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述第一源QoS信息将所述第一报文映射到第一5G网络的服务质量标识符5QI；
    根据所述第二源QoS信息将所述第二报文映射到第二5QI；
    其中，所述第一5QI和所述第二5QI属于一个QoS flow。
  35. 如权利要求33所述的方法，其特征在于，所述根据所述第一源QoS信息将所述第一报文映射到第一QoS flow包括：
    根据所述第一源QoS信息中包括的第一QoS特征从多个QoS flow中确定所述第一QoS flow，其中，所述第一源QoS信息中包括的第一QoS特征与所述第一QoS flow中的5QI指示的QoS特征相对应。
  36. 如权利要求33或35所述的方法，其特征在于，
    所述第一QoS flow的QoS配置包括：
    最大保障带宽MGFBR；
    所述方法还包括：
    确定所述第一QoS flow的保障带宽小于或者等于所述MGFBR。
  37. 如权利要求36所述的方法，其特征在于，所述第一QoS flow的QoS配置还包括：
    最小保障带宽GFBR；
    所述方法还包括：确定所述第一QoS flow的保障带宽大于或者等于所述GFBR且小于或者等于所述MGFBR。
  38. 如权利要求33或35至37中任一项所述的方法，其特征在于，所述第一QoS flow的QoS配置包括：
    指示信息，所述指示信息用于指示是否预留所述第一QoS flow对应的资源；
    根据所述指示信息确定是否预留所述第一QoS flow对应的资源。
  39. 如权利要求20至38中任一项所述的方法，其特征在于，所述第一源QoS信息为接收到的，或者，所述第一源QoS信息为本地生成的；
    当所述第一源QoS信息为本地生成时，所述方法还包括：
    将所述第一源QoS信息填入所述第一报文中。
  40. 如权利要求19至39中任一项所述的方法，其特征在于，所述方法还包括：
    确定传输所述第一报文的路径中传输节点的状态；
    当至少一个所述输节点的状态满足预设条件时，启动主动保障机制。
  41. 如权利要求40所述的方法，其特征在于，所述当至少一个所述输节点的状态满足预设条件时，启动主动保障机制包括以下一项或者多项：
    当所述至少一个所述输节点存在丢包时，重复发送所述第一报文；或者
    当所述至少一个所述输节点丢包率大于预设值时，采用前向纠错FEC冗余编码方式编码所述第一报文。
  42. 一种传输报文的装置，其特征在于，用于执行权利要求1至18中任一项所述的方法。
  43. 一种传输报文的装置，其特征在于，用于执行权利要求19至41中任一项所述的方法。
  44. 一种计算机可读存储介质，其特征在于，包括计算机指令，当所述计算机指令在被处理器运行时，使得所述计算机执行如权利要求1至18中任一项所述的方法，或者使得所述计算机执行如权利要求19至41中任一项所述的方法。
  45. 一种芯片装置，其特征在于，包括处理电路，所述处理电路用于从存储器中调用并运行程序，使得安装有该芯片装置的通信设备执行如权利要求1至18中任一项所述的方法，或者使得所述安装有该芯片装置的通信设备执行如权利要求19至41中任一项所述的方法。
  46. 一种通信系统，其特征在于，包括如权利要求42所述的装置和如权利要求43所述的装置。
PCT/CN2022/070294 2021-01-06 2022-01-05 传输报文的方法和装置 WO2022148371A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110014125 2021-01-06
CN202110014125.X 2021-01-06
CN202110181698.1A CN114727340A (zh) 2021-01-06 2021-02-10 传输报文的方法和装置
CN202110181698.1 2021-02-10

Publications (1)

Publication Number Publication Date
WO2022148371A1 true WO2022148371A1 (zh) 2022-07-14

Family

ID=82233979

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/070294 WO2022148371A1 (zh) 2021-01-06 2022-01-05 传输报文的方法和装置

Country Status (2)

Country Link
CN (1) CN114727340A (zh)
WO (1) WO2022148371A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115314409A (zh) * 2022-07-20 2022-11-08 北京邮电大学 网络状态信息获取方法及系统
CN115623087A (zh) * 2022-11-21 2023-01-17 飞天诚信科技股份有限公司 一种解析pb格式流通数据的方法及系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024055334A1 (zh) * 2022-09-16 2024-03-21 北京小米移动软件有限公司 丢包处理方法、装置、通信设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1335038A (zh) * 1998-12-10 2002-02-06 诺基亚网络有限公司 用于在一个网络服务级别中向多播数据包授以优先权的系统与方法
CN103078869A (zh) * 2013-01-16 2013-05-01 华为技术有限公司 一种加速会话转发的系统及其方法
WO2014101164A1 (zh) * 2012-12-31 2014-07-03 华为技术有限公司 一种承载创建方法、装置和系统
CN106487713A (zh) * 2015-08-26 2017-03-08 深圳市中兴微电子技术有限公司 一种服务质量复用方法及装置
CN109691039A (zh) * 2018-01-16 2019-04-26 华为技术有限公司 一种报文传输的方法及装置
CN112333113A (zh) * 2020-05-18 2021-02-05 中兴通讯股份有限公司 信息处理方法、终端及计算机可读存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1335038A (zh) * 1998-12-10 2002-02-06 诺基亚网络有限公司 用于在一个网络服务级别中向多播数据包授以优先权的系统与方法
WO2014101164A1 (zh) * 2012-12-31 2014-07-03 华为技术有限公司 一种承载创建方法、装置和系统
CN103078869A (zh) * 2013-01-16 2013-05-01 华为技术有限公司 一种加速会话转发的系统及其方法
CN106487713A (zh) * 2015-08-26 2017-03-08 深圳市中兴微电子技术有限公司 一种服务质量复用方法及装置
CN109691039A (zh) * 2018-01-16 2019-04-26 华为技术有限公司 一种报文传输的方法及装置
CN112333113A (zh) * 2020-05-18 2021-02-05 中兴通讯股份有限公司 信息处理方法、终端及计算机可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Clarification of Maximum Packet Loss Rate authorization", 3GPP DRAFT; C3-187444 WAS 7215 WAS 6304 CLARIFICATION OF MAXIMUM PACKET LOSS RATE AUTHORIZATION, vol. CT WG3, 3 December 2018 (2018-12-03), West Palm Beach, Florida(US), pages 1 - 4, XP051490846 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115314409A (zh) * 2022-07-20 2022-11-08 北京邮电大学 网络状态信息获取方法及系统
CN115314409B (zh) * 2022-07-20 2024-02-06 北京邮电大学 网络状态信息获取方法及系统
CN115623087A (zh) * 2022-11-21 2023-01-17 飞天诚信科技股份有限公司 一种解析pb格式流通数据的方法及系统

Also Published As

Publication number Publication date
CN114727340A (zh) 2022-07-08

Similar Documents

Publication Publication Date Title
WO2022148371A1 (zh) 传输报文的方法和装置
US10721754B2 (en) Data transmission method and apparatus
US7782872B2 (en) Method, apparatus, and computer-readable medium for providing an applicable QoS for data that has actually experienced a QoS degraded from that requested
CN112423340B (zh) 一种用户面信息上报方法及装置
WO2008053552A1 (en) Wireless communication apparatus and wireless communication method
US20230116578A1 (en) Data transmission method and apparatus
KR20080086778A (ko) 이동통신시스템의 스케쥴링 요청 방법 및 장치
WO2021114107A1 (zh) 一种数据传输方法及装置
WO2019101054A1 (zh) 聚合速率控制方法、设备以及系统
CN111294860A (zh) 缓存区状态报告的生成、接收方法及装置、终端、基站
WO2023126857A1 (en) Design of delay-aware bsr for xr applications
WO2023160116A1 (zh) 通信方法和装置
WO2018058391A1 (zh) 建立承载的方法、无线接入网设备和客户终端设备
CA3153205A1 (en) Method for reporting buffer status report and communications apparatus
WO2023070392A1 (zh) 数据传输方法、设备及存储介质
WO2022151107A1 (zh) 信号的发送和接收方法、装置和通信系统
WO2023185769A1 (zh) 通信方法、通信装置和通信系统
WO2023185608A1 (zh) 一种数据传输的方法及通信装置
CN114788243B (zh) 调度报文的方法和装置
WO2023184537A1 (zh) 一种数据传输方法及装置、通信设备
WO2023024684A1 (zh) 数据传输的方法和装置
WO2023184552A1 (zh) 一种数据传输方法及装置、通信设备
WO2022021021A1 (zh) 无线通信方法、终端设备和网络设备
WO2023019450A1 (zh) 一种QoS的控制方法及装置、通信设备
WO2023185402A1 (zh) 通信方法及装置

Legal Events

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

Ref document number: 22736533

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22736533

Country of ref document: EP

Kind code of ref document: A1