CN114727340A

CN114727340A - Method and device for transmitting message

Info

Publication number: CN114727340A
Application number: CN202110181698.1A
Authority: CN
Inventors: 周艳; 林霖; 叶进洲; 周汉
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-01-06
Filing date: 2021-02-10
Publication date: 2022-07-08
Also published as: WO2022148371A1

Abstract

The application provides a method and a device for transmitting messages, which comprises the following steps: and generating a plurality of messages and sending the messages. Specifically, the five-tuple information of the plurality of messages is the same, each message of the plurality of messages includes source QoS information, the source QoS information included in each message is used for QoS guarantee of the QoS message corresponding to the message, and the source QoS information included in the plurality of messages is different, so that the transmission network can provide QoS guarantee for each message.

Description

Method and device for transmitting message

The present application claims priority of chinese patent application, entitled "method and apparatus for transmitting messages", filed by chinese patent office on 06.01/06/2021 with application number 202110014125.X, the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of communications, and more particularly, to a method and apparatus for transmitting a packet.

Background

With the development of communication technology, the current communication system has a higher transmission rate and a more flexible bandwidth configuration, and an Internet Protocol (IP) and flat network architecture can provide diversified multimedia services, so an end-to-end quality of service (QoS) mechanism is required to ensure the quality of service of different services.

The Internet Engineering Task Force (IETF) defines three QoS service models: best-effort service (best-effort service), integrated service (IntServ), and differentiated service (DiffServ). In the 3rd Generation partnership project (3 GPP) release 16(release 16, R16), a QoS flow (flow) mechanism is proposed, where QoS flow is the minimum QoS control granularity between a fifth Generation (5G) core network and a radio access network, each QoS flow has a corresponding QoS configuration, and parameters in the QoS configuration describe specific QoS requirements.

Both the IETF QoS service model and the QoS flow mechanism are modes in which, when a forwarding node in a transmission network forwards a packet, the packet is matched to a preset QoS policy corresponding to QoS flow according to network layer characteristics of the packet, and differential guarantee processing is performed according to the QoS policy. Under the existing QoS mechanism, the transmission network cannot guarantee and optimize the QoS more accurately.

Disclosure of Invention

The application provides a method for transmitting messages, which enables a transmission network to provide QoS guarantee for the messages by carrying different source QoS information in different messages with the same quintuple information, thereby improving the accuracy of QoS guarantee and optimization of the transmission network.

In a first aspect, a method for transmitting a message is provided, where the method for transmitting a message may be executed by a message generation device, or may also be executed by a chip or a circuit disposed in the message generation device, and this application is not limited thereto.

The method for transmitting the message comprises the following steps:

generating a plurality of messages, wherein five-tuple information of the plurality of messages is the same, each message in the plurality of messages comprises source QoS (quality of service) information, the source QoS information of each message is used for QoS guarantee of the corresponding QoS message, and the source QoS information of the plurality of messages is different; and transmitting the plurality of messages.

Or it can be said that,

the method for transmitting the message comprises the following steps:

generating a plurality of messages, wherein the plurality of messages have the same quintuple information, the plurality of messages have different source QoS information, and the source QoS information is used for performing QoS guarantee on the corresponding message; and transmitting the plurality of messages.

In the method for transmitting a packet provided by the embodiment of the present application, the packet generated by the packet generation device includes the source QoS information for providing QoS guarantee for the packet, and different packets in the same quintuple information may include different source QoS information, so that the transmission network of the packet may provide QoS guarantee for the packet, thereby improving the accuracy of QoS guarantee and optimization performed by the transmission network.

For convenience of description, a plurality of packets having the same five-tuple information will be hereinafter referred to as packets in one connection. With reference to the first aspect, in some implementation manners of the first aspect, the multiple packets belong to the same connection, and source QoS information included in the multiple packets are different, including: the first source QoS information included in the first message in the connection is different from the second source QoS information included in the second message in the connection, wherein the first message and the second message are any two messages in the plurality of messages.

In other words,

the generating of the multiple messages, the multiple messages having the same quintuple information, the multiple messages having different source QoS information, the source QoS information being used for performing QoS guarantee on the corresponding messages, includes: generating a first message and a second message, wherein the quintuple information of the first message is the same as the quintuple information of the second message, the first source QoS information included in the first message is different from the second source QoS information included in the second message, the first source QoS information is used for QoS guarantee of the first message, and the second source QoS information is used for QoS guarantee of the second message.

Further, the plurality of messages belong to the same connection.

Specifically, the source QoS information included in different packets in the connection may be different from the QoS information included in any two packets in the connection.

With reference to the first aspect, in certain implementations of the first aspect, the first source QoS information includes a first QoS characteristic indicating a QoS requirement of the first packet and a first data characteristic indicating a transmission characteristic of the first packet, and the second source QoS information includes a second QoS characteristic indicating a QoS requirement of the second packet and a second data characteristic indicating a transmission characteristic of the second packet.

Specifically, the source QoS information included in a certain packet may further include QoS characteristics and data characteristics, and the application may clearly and exhaustively indicate the data characteristics and QoS requirements of the application layer to the transmission network, so as to further improve the accuracy of QoS guarantee and optimization performed by the transmission network.

With reference to the first aspect, in some implementation manners of the first aspect, the determining that the source QoS information included in the multiple packets is different includes: the plurality of messages may include different data characteristics and/or the plurality of messages may include different QoS characteristics. For example, 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 characteristic and the second data characteristic are different, and/or the first QoS characteristic and the second QoS characteristic are different.

The difference between the source QoS information included in two packets in the connection may be a data characteristic included in the source QoS information, and/or the QoS characteristic included in the source QoS information is different, which increases the flexibility of the scheme.

With reference to the first aspect, in certain implementations of the first aspect, the first data feature includes a connection-level data feature and/or a packet-level data feature, where the connection-level data feature is used to indicate transmission characteristics of a plurality of packets included in the connection, the packet-level data feature represents the transmission characteristics of the first packet, and the QoS feature includes a connection-level QoS feature and/or a packet-level QoS feature, where the connection-level QoS feature is used to indicate QoS requirements of the plurality of packets included in the connection, and the packet-level QoS feature is used to indicate QoS requirements of the first packet.

Specifically, the data characteristic in the source QoS information included in a certain packet may be a connection-level data characteristic indicating the transmission characteristic of a connection including the packet, or a packet-level data characteristic indicating the transmission characteristic of the packet; similarly, the QoS characteristic may be a connection-level QoS characteristic indicating the QoS requirement of the connection containing the packet, or a packet-level QoS characteristic indicating the QoS requirement of the packet. Different possible granularities of source QoS information are provided, thereby increasing the flexibility of the scheme.

With reference to the first aspect, in certain implementations of the first aspect, the data characteristics of the connection level include one or more of: average rate, duration, frequency, size, delay budget, peak frequency, peak size, peak delay budget, peak transmission time, emergency type, expected emergency occurrence time, expected emergency message volume, and emergency message delay budget, wherein the average rate indicates the average transmission rate of messages in the connection, the duration indicates the duration of the connection, the frequency indicates the message transmission frequency, the size indicates the average value of messages transmitted per frequency, the delay budget indicates the time consumption budget for all messages transmitted to the receiving end within a period, the peak generation frequency of the peak frequency indicates the time consumption budget for all message peaks transmitted to the receiving end, the peak transmission time indicates the time for transmitting the message peaks, the type of emergency indicates the category to which the suddenly occurring time belongs, The expected time of occurrence of the emergency indicates the expected arrival time of the emergency message, the expected volume of the emergency message indicates the volume of the emergency transmission message, and the time delay budget of the emergency message indicates the time consumption budget for transmitting all the emergency messages to the receiving end.

With reference to the first aspect, in certain implementations of the first aspect, the packet-level data characteristics include one or more of: the data block sequence number indicates the data block number to which the first message belongs, the data block size indicates the data block size to which the first message belongs, the packet position indicates the position of the data block to which the first message belongs, and the data block delay budget indicates the time consumption budget for transmitting the first message to a receiving end.

The data characteristics included in the source QoS information can have different implementation modes for different messages, and the flexibility of the scheme is improved.

With reference to the first aspect, in some implementations of the first aspect, the QoS characteristic of the connection level includes a connection QoS characteristics indicator (CQI) and/or connection QoS characteristics information, and the QoS characteristic of the packet level includes a packet QoS characteristics indicator (PQI) and/or packet QoS characteristics information.

The QoS characteristics of the connection level and the QoS characteristics of the packet level can be embodied in different forms, and the flexibility of the scheme is increased.

With reference to the first aspect, in certain implementations of the first aspect, the QoS characteristics represented by the connection-level QoS characteristics or packet-level QoS characteristics include one or more of: resource type, priority, delay budget, and error rate.

The QoS features included in the source QoS information may have different implementation manners for different packets, thereby increasing the flexibility of the scheme.

With reference to the first aspect, in some implementation manners of the first aspect, the including, in the first packet, the first source QoS information includes: connecting the first message with the information of the connection level and the information of the packet level; or, the first message includes information of the packet level, and a virtual Internet protocol (dummy IP) packet includes information of the connection level; or, the first packet includes the packet-level information, and the connection-level information is transmitted through the control plane, where the connection-level information includes the connection-level data characteristics and the connection-level QoS characteristics, and the packet-level information includes the packet-level data characteristics and the packet-level QoS characteristics.

According to the method for transmitting the message, the source QoS information carried in the message can have different implementation modes, and the flexibility of the scheme is improved.

With reference to the first aspect, in some implementations of the first aspect, the first source QoS information is used to indicate that the first packet is mapped to a first QoS flow, and the second source QoS information is used to indicate that the second packet is mapped to a second QoS flow, where the first QoS flow and the second QoS flow belong to a QoS flow group.

Alternatively, the first and second electrodes may be,

with reference to the first aspect, in some implementations of the first aspect, the first source QoS information is used to indicate a quality of service identifier (5G quality of service identifier, 5QI) for mapping the first packet to the first 5G network, and the second source QoS information is used to indicate that the second packet is mapped to a second 5QI, where the first 5QI and the second 5QI belong to one QoS flow.

The method for transmitting the packet provided by the embodiment of the application further provides a QoS flow model, where different QoS flows of different packet mappings included in a certain connection belong to the same QoS flow group, or different 5 QIs of different packet mappings included in a certain connection belong to one QoS flow, so that the control strength of the connection can be improved.

With reference to the first aspect, in some implementation manners of the first aspect, the first source QoS information is used to indicate that the first packet is mapped to a first quality of service flow QoS flow, and the QoS configuration of the first QoS flow includes: maximum guaranteed bandwidth (MGFBR); the MGFBR is configured to adjust resources reserved for the first QoS flow, where a guaranteed bandwidth of the first QoS flow is less than or equal to the MGFBR, where the first packet is any one of the multiple packets, and the first source QoS information is source QoS information included in the first packet. Alternatively, the first and second electrodes may be,

with reference to the first aspect, in some implementations of the first aspect, the QoS configuring of the first QoS flow further includes: a minimum guaranteed bandwidth (GFBR) to adjust resources reserved for the first QoS flow, the guaranteed bandwidth of the first QoS flow being greater than or equal to the GFBR and less than or equal to the MGFBR.

The method for transmitting the message provided by the embodiment of the application can be used for micro-adjusting the resources reserved for the QoS flow by adding the parameter MGFBR in the QoS configuration of the QoS flow.

With reference to the first aspect, in some implementations of the first aspect, the first source QoS information is used to indicate that the first packet is mapped to a first quality of service flow QoS flow, and the QoS configuration of the first QoS flow includes: and indicating information, where the indicating information is used to indicate whether to reserve a resource corresponding to the first QoS flow, where the first message is any one of the multiple messages, and the first source QoS information is source QoS information included in the first message.

The method for transmitting the message provided by the embodiment of the application can indicate whether resources corresponding to the QoS flow are reserved or not by adding the indication information in the QoS configuration of the QoS flow, so that the defects of time consumption of QoS strategy change decision and execution chain length change in the current macro control mode are avoided.

With reference to the first aspect, in some implementations of the first aspect, the mapping the first packet to the first quality of service flow QoS flow by the first source QoS information includes: the first source QoS information includes a QoS characteristic corresponding to a QoS characteristic indicated by a 5QI in the first QoS flow.

Specifically, when the method for transmitting a packet provided in the embodiment of the present application is applied to QoS flow mapping, the compatibility of the scheme may be improved by being compatible with a current QoS mechanism through mapping with 5 QI.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: determining the state of a transmission node in a path for transmitting the first message; and when the state of at least one input node meets a preset condition, starting an active guarantee mechanism.

With reference to the first aspect, in certain implementations of the first aspect, when the state of the at least one input node satisfies a preset condition, the initiating an active safeguard mechanism includes one or more of: when packet loss exists in the at least one transmission node, the first message is repeatedly sent; or when the packet loss rate of the at least one transmission node is greater than a preset value, encoding the first packet by using a Forward Error Correction (FEC) redundancy coding mode.

The method for transmitting a packet provided in the embodiment of the present application further provides an active guarantee mechanism, and when it is sensed that a transmission node at the back end meets a preset condition (for example, due to interference, there is periodic sporadic packet loss, and a packet loss rate cannot meet an end-to-end packet error rate target), the active guarantee mechanism is started, so that a performance of packet transmission is improved.

In addition, it should be noted that, in a scenario where a message generated by the message generation device does not include the source QoS information in the embodiment of the present application, a transmission node in the message transmission network may recognize a part of data characteristics, map the data characteristics as the source QoS information, and transmit the source QoS information to another transmission node.

In a second aspect, a method for transmitting a message is provided, where the method for transmitting a message may be performed by a message receiving device, or may also be performed by a chip or a circuit disposed in the message receiving device, and this application is not limited thereto.

The method for transmitting the message comprises the following steps:

receiving a plurality of messages, wherein five-tuple information of the plurality of messages is the same, each message in the plurality of messages comprises source QoS (quality of service) information, the source QoS information contained in each message is used for QoS guarantee of the corresponding QoS message, and the source QoS information contained in the plurality of messages is different; the plurality of packets are processed based on source QoS information included in the plurality of packets.

Or, it can be said that the method for transmitting a packet includes:

receiving a plurality of messages, wherein the plurality of messages have the same quintuple information, the plurality of messages have different source QoS information, and the source QoS information is used for performing QoS guarantee on the corresponding message; the plurality of packets are processed based on source QoS information included in the plurality of packets.

According to the method for transmitting the message, the message received by the message receiving equipment comprises the source QoS information used for providing QoS guarantee for the message, and different connected messages can comprise different source QoS information, so that a transmission network of the message can provide QoS guarantee for the message, and the accuracy of QoS guarantee and optimization of the transmission network is improved.

With reference to the second aspect, in some implementations of the second aspect, the multiple messages belong to the same connection, and the different source QoS information included in the multiple messages includes: the first source QoS information included in the first message in the connection is different from the second source QoS information included in the second message in the connection, wherein the first message and the second message are any two messages in the plurality of messages.

Or receiving a plurality of messages, wherein the plurality of messages have the same quintuple information, the plurality of messages have different source QoS information, and the source QoS information is used for performing QoS guarantee on the corresponding message and comprises the following steps: receiving a first message and a second message, wherein the quintuple information of the first message is the same as the quintuple information of the second message, the first source QoS information included in the first message is different from the second source QoS information included in the second message, the first source QoS information is used for performing QoS guarantee on the first message, and the second source QoS information is used for performing QoS guarantee on the second message.

Further, the plurality of messages belong to the same connection.

With reference to the second aspect, in certain implementations of the second aspect, 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, and the second data characteristic represents a transmission characteristic of the second packet, and the method further includes: determining the QoS requirement of the first message according to the first QoS characteristic; determining the QoS requirement of the second message according to the second QoS characteristic; processing the plurality of packets based on the source QoS information included in the plurality of packets includes: scheduling resources of the first message according to the QoS requirement of the first message and the first data characteristic; and scheduling the resource of the second message according to the QoS requirement of the second message and the second data characteristic.

Further, the device for receiving the message by the method for transmitting the message provided by the embodiment of the application can perform resource scheduling according to the QoS characteristics and the data characteristics included in the source QoS information.

With reference to the second aspect, in some implementations of the second aspect, the source QoS information included in the multiple packets is different, including: the plurality of messages may include different QoS characteristics and/or the plurality of messages may include different data characteristics. For example, 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 characteristic and the second data characteristic are different, and/or the first QoS characteristic and the second QoS characteristic are different.

The difference between the source QoS information included in two packets in the connection may be data characteristics included in the source QoS information, and/or the QoS characteristics included in the source QoS information are different, thereby increasing flexibility of the scheme.

With reference to the second aspect, in some implementation manners of the second aspect, the scheduling resources of the packet according to the QoS requirement and the data characteristic includes: different resources are scheduled for different messages according to different QoS characteristics. For example, the resources scheduling the first packet and the resources scheduling the second packet are different.

The device for receiving the message in the message transmission method provided by the embodiment of the application can schedule different resources for different connected messages, and the scheduling accuracy is improved.

With reference to the second aspect, in some implementations of the second aspect, the first data characteristic includes a connection-level data characteristic and/or a packet-level data characteristic, and the method further includes: determining the transmission characteristics of a plurality of messages included in the connection according to the data characteristics of the connection level; determining the transmission characteristic of the first message according to the data characteristic of the packet level;

with reference to the second aspect, in some implementations of the second aspect, the first QoS characteristic includes a connection-level QoS characteristic and/or a packet-level QoS characteristic, and the method further includes: determining the QoS requirements of other messages in the connection according to the QoS characteristics of the connection level, wherein the other messages can be messages which do not include the QoS characteristics of the packet level; for example, the QoS requirements of a third packet in the connection are determined according to the QoS characteristics of the connection level, the third packet includes third source QoS information, and the third QoS characteristics included in the third source QoS information may not include packet-level QoS characteristics.

And determining the QoS requirement of the first message according to the QoS characteristics of the packet level.

Specifically, the data characteristic in the source QoS information included in the packet may be a connection-level data characteristic indicating the transmission characteristic of a connection including the packet, or a packet-level data characteristic indicating the transmission characteristic of the packet; similarly, the QoS characteristic may be a connection-level QoS characteristic indicating the QoS requirement of the connection containing the packet, or a packet-level QoS characteristic indicating the QoS requirement of the packet. Different possible granularities of source QoS information are provided, thereby increasing the flexibility of the scheme.

With reference to the second aspect, in some implementations of the second aspect, the data characteristics of the connection level include one or more of: average rate, duration, frequency, size, delay budget, peak frequency, peak size, peak delay budget, peak transmission time, emergency type, expected emergency occurrence time, expected emergency message volume, and emergency message delay budget, wherein the average rate indicates the average transmission rate of messages in the connection, the duration indicates the duration of the connection, the frequency indicates the message transmission frequency, the size indicates the average value of messages transmitted per frequency, the delay budget indicates the time consumption budget for all messages transmitted to the receiving end within a period, the peak generation frequency of the peak frequency indicates the time consumption budget for all message peaks transmitted to the receiving end, the peak transmission time indicates the time for transmitting the message peaks, the type of emergency indicates the category to which the suddenly occurring time belongs, The expected time of the occurrence of the emergency indicates the expected arrival time of the emergency message, the expected volume of the emergency message indicates the volume of the emergency message, and the time delay budget of the emergency message indicates the time consumption budget for transmitting all the emergency messages to the receiving end.

With reference to the second aspect, in some implementations of the second aspect, the packet-level data characteristics include one or more of: the data block sequence number indicates the data block number to which the first message belongs, the data block size indicates the data block size to which the first message belongs, the packet position indicates the position of the data block to which the first message belongs, and the data block delay budget indicates the time consumption budget for transmitting the first message to a receiving end.

With reference to the second aspect, in certain implementations of the second aspect, the connection-level QoS characteristics include a connection QoS characteristics indication CQI and/or connection QoS characteristics information, and the packet-level QoS characteristics include a packet QoS indication PQI and/or packet QoS characteristics information.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: receiving a packet filtering rule from a core network device, wherein the packet filtering rule comprises the CQI and/or the PQI; and mapping the first message to a first quality of service flow QoS flow according to the CQI and/or the PQI.

In the method for transmitting a packet provided in the embodiment of the present application, the core network device may send the enhanced packet filtering rule to a packet receiving device (e.g., a user plane network element), so that QoS stream mapping can be performed subsequently based on QoS characteristics of the packet.

It should be noted that the "enhanced packet filtering rule" referred to in this application refers to a packet filtering rule having more configuration parameters than the current packet filtering rule.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: receiving a reflective QoS flow to DRB mapping indication (RDI) and the PQI; recording the PQI according to the RDI, wherein the PQI is used for indicating that a fourth message is mapped to a third QoS flow; the fourth message is a message to be sent, and the QoS characteristic indicated by the 5QI in the third QoS flow corresponds to the PQI.

The method for transmitting the message provided by the embodiment of the application also provides a reflection enhancement method, so that the QoS flow mapping based on the reflection QoS scheme is more accurate.

With reference to the second aspect, in some implementations of the second aspect, the QoS characteristics represented by the connection-level QoS characteristics or packet-level QoS characteristics include one or more of: resource type, priority, delay budget, and error rate.

With reference to the second aspect, in some implementation manners of the second aspect, the including, in the first packet, the first source QoS information includes: the first message comprises information of a connection level and information of a packet level; or, the first message includes information of the packet level, and the virtual internet protocol dummy IP packet includes information of the connection level; or, the first packet includes the packet-level information, and the connection-level information is transmitted through the control plane, where the connection-level information includes the connection-level data characteristics and the connection-level QoS characteristics, and the packet-level information includes the packet-level data characteristics and the packet-level QoS characteristics.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: mapping the first message to a first QoS flow according to the first source QoS information; mapping the second message to a second QoS flow according to the second source QoS information; wherein the first QoS flow and the second QoS flow belong to a QoS flow group.

Alternatively, the method further comprises: mapping the first message to a service quality identifier 5QI of a first 5G network according to the first source QoS information; mapping the second message to a second 5QI according to the second source QoS information; wherein the first 5QI and the second 5QI belong to one QoS flow.

The method for transmitting the message provided by the embodiment of the application further provides a QoS flow model, different QoS flows of different message mappings included in a certain connection belong to the same QoS flow group, or different 5QI of different message mappings included in a certain connection belong to one QoS flow, so that the control strength of the connection can be improved.

With reference to the second aspect, in some implementations of the second aspect, mapping the first packet to a first QoS flow according to the first source QoS information includes: the first source QoS information is transmitted to a plurality of QoS flows, wherein the first source QoS information includes a first QoS characteristic corresponding to a QoS characteristic indicated by 5QI in the first QoS flow.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: resources reserved for the first QoS flow are adjusted.

With reference to the second aspect, in some implementations of the second aspect, the QoS configuration of the first QoS flow includes: the maximum guaranteed bandwidth MGFBR; the adjusting resources reserved for the first QoS flow includes: determining that the guaranteed bandwidth of the first QoS flow is less than or equal to the MGFBR.

With reference to the second aspect, in some implementations of the second aspect, the QoS configuration of the first QoS flow further includes: minimum guaranteed bandwidth GFBR; the adjusting resources reserved for the first QoS flow includes: and determining 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.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: and determining whether to reserve the resources corresponding to the first QoS flow.

With reference to the second aspect, in some implementations of the second aspect, the QoS configuration of the first QoS flow includes: indicating information, wherein the indicating information is used for indicating whether resources corresponding to the first QoS flow are reserved or not; the determining whether to reserve the resource corresponding to the first QoS flow includes: and determining whether to reserve the resources corresponding to the first QoS flow according to the indication information.

The method for transmitting the message provided by the embodiment of the application can indicate whether resources corresponding to the QoS flow are reserved or not by adding the indication information in the QoS configuration of the QoS flow, and avoids the defects of QoS strategy change decision, execution chain length and time consumption in the current macro control mode.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the first source QoS information is received or locally generated; when the first source QoS information is locally generated, the method further includes: and filling the first source QoS information into the first message.

With reference to the second aspect, in some implementations of the second aspect, the generating the first source QoS information includes: the first source QoS information is determined through flow analysis and/or message analysis.

In the scenario that the message generated by the message generation device does not include the source QoS information in the embodiment of the present application, a transmission node in the message transmission network may recognize a part of data characteristics, and map the data characteristics to the source QoS information, so as to transmit the source QoS information to other transmission nodes.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: determining the state of a transmission node in a path for transmitting the first message; and when the state of at least one input node meets the preset condition, starting an active guarantee mechanism.

With reference to the second aspect, in some implementations of the second aspect, when the state of the at least one input node meets a preset condition, the initiating an active safeguard mechanism includes one or more of: when packet loss exists in the at least one transmission node, the first message is repeatedly sent; or when the packet loss rate of the at least one transmission node is greater than a preset value, the first message is encoded by adopting a Forward Error Correction (FEC) redundancy coding mode.

The method for transmitting a packet provided in the embodiment of the present application further provides an active guarantee mechanism, and when it is sensed that a transmission node at the back end meets a preset condition (for example, a periodic occasional packet loss exists due to interference, and a packet loss rate cannot meet an end-to-end packet error rate target), the active guarantee mechanism is started, so as to improve the performance of packet transmission.

In a third aspect, an apparatus for transmitting a packet is provided, including:

a processing unit, configured to generate multiple messages, where five tuple information of the multiple messages is the same, each message in the multiple messages includes source QoS information, the source QoS information included in each message is used to guarantee QoS for the corresponding message, and the source QoS information included in the multiple messages is different;

and the sending unit is used for sending the plurality of messages.

Or, the apparatus for transmitting a packet includes:

the processing unit is used for generating a plurality of messages, the plurality of messages have the same quintuple information, the plurality of messages have different source QoS information, and the source QoS information is used for performing QoS guarantee on the corresponding messages;

a sending unit, configured to send the multiple messages.

With reference to the third aspect, in some implementation manners of the third aspect, the multiple messages belong to the same connection, and source QoS information included in the multiple messages is different, including: the first source QoS information included in the first message in the connection is different from the second source QoS information included in the second message in the connection, wherein the first message and the second message are any two messages in the plurality of messages.

Or it can be understood that, the processing unit generates multiple packets, where the multiple packets have the same five-tuple information, and the multiple packets have different source QoS information, where the source QoS information is used to perform QoS guarantee on its corresponding packet, and includes:

the processing unit generates a first message and a second message, wherein five-tuple information of the first message is the same as five-tuple information of the second message, first source QoS information included in the first message is different from second source QoS information included in the second message, the first source QoS information is used for QoS guarantee of the first message, and the second source QoS information is used for QoS guarantee of the second message.

Further, the plurality of messages belong to the same connection.

With reference to the third aspect, in some implementations of the third aspect, the first source QoS information includes a first QoS characteristic indicating a QoS requirement of the first packet and a first data characteristic indicating a transmission characteristic of the first packet, and the second source QoS information includes a second QoS characteristic indicating a QoS requirement of the second packet and a second data characteristic indicating a transmission characteristic of the second packet.

With reference to the third aspect, in some implementations of the third aspect, the determining that 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 includes: the first data characteristic and the second data characteristic are different, and/or the first QoS characteristic and the second QoS characteristic are different.

With reference to the third aspect, in certain implementations of the third aspect, the first data characteristic includes a connection-level data characteristic and/or a packet-level data characteristic, where the connection-level data characteristic represents transmission characteristics of a plurality of packets included in the connection, the packet-level data characteristic represents transmission characteristics of the first packet, and the first QoS characteristic includes a connection-level QoS characteristic and/or a packet-level QoS characteristic, where the connection-level QoS characteristic is used to indicate QoS requirements of the plurality of packets included in the connection, and the packet-level QoS characteristic is used to indicate QoS requirements of the first packet.

With reference to the third aspect, in certain implementations of the third aspect, the data characteristics of the connection level include one or more of: average rate, duration, frequency, size, delay budget, peak frequency, peak size, peak delay budget, peak transmission time, emergency type, expected emergency occurrence time, expected emergency message volume, and emergency message delay budget, wherein the average rate indicates the average transmission rate of messages in the connection, the duration indicates the duration of the connection, the frequency indicates the message transmission frequency, the size indicates the average value of messages transmitted per frequency, the delay budget indicates the time consumption budget for all messages transmitted to the receiving end within a period, the peak generation frequency of the peak frequency indicates the time consumption budget for all message peaks transmitted to the receiving end, the peak transmission time indicates the time for transmitting the message peaks, the type of emergency indicates the category to which the suddenly occurring time belongs, The expected time of occurrence of the emergency indicates the expected arrival time of the emergency message, the expected volume of the emergency message indicates the volume of the emergency transmission message, and the time delay budget of the emergency message indicates the time consumption budget for transmitting all the emergency messages to the receiving end.

With reference to the third aspect, in certain implementations of the third aspect, the packet-level data characteristics include one or more of: the data block sequence number indicates the data block number to which the first message belongs, the data block size indicates the data block size to which the first message belongs, the packet position indicates the position of the data block to which the first message belongs, and the data block delay budget indicates the time consumption budget for transmitting the first message to a receiving end.

With reference to the third aspect, in certain implementations of the third aspect, the connection-level QoS characteristics include a connection QoS characteristics indication CQI and/or connection QoS characteristics information, and the packet-level QoS characteristics include a packet QoS indication PQI and/or packet QoS characteristics information.

With reference to the third aspect, in some implementations of the third aspect, the QoS characteristics indicated by the connection-level QoS characteristic information or the packet-level QoS characteristic information include one or more of: resource type, priority, delay budget, and error rate.

With reference to the third aspect, in some implementation manners of the third aspect, the including, in the first packet, the first source QoS information includes: the first message comprises information of a connection level and information of a packet level; or, the first message 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 packet-level information, and the connection-level information is transmitted through the control plane, where the connection-level information includes the connection-level data characteristics and the connection-level QoS characteristics, and the packet-level information includes the packet-level data characteristics and the packet-level QoS characteristics.

With reference to the third aspect, in some implementations of the third aspect, the first source QoS information is used to indicate that the first packet is mapped to a first quality of service flow QoS flow, and the second source QoS information is used to indicate that the second packet is mapped to a second QoS flow, where the first QoS flow and the second QoS flow belong to a QoS flow group.

With reference to the third aspect, in some implementations of the third aspect, the first source QoS information is used to indicate that the first packet is mapped to a quality of service identifier 5QI of the first 5G network, and the second source QoS information is used to indicate that the second packet is mapped to a second 5QI, where the first 5QI and the second 5QI belong to one QoS flow.

With reference to the third aspect, in some implementations of the third aspect, the first source QoS information is used to indicate that the first packet is mapped to a first quality of service flow QoS flow, and the QoS configuration of the first QoS flow includes: the maximum guaranteed bandwidth MGFBR; the MGFBR is configured to adjust resources reserved for the first QoS flow, and a guaranteed bandwidth of the first QoS flow is less than or equal to the MGFBR.

With reference to the third aspect, in some implementations of the third aspect, the QoS configuring of the first QoS flow further includes: and a minimum guaranteed bandwidth (GFBR) for adjusting resources reserved for the first QoS flow, wherein the guaranteed bandwidth of the first QoS flow is greater than or equal to the GFBR and less than or equal to the MGFBR.

With reference to the third aspect, in some implementations of the third aspect, the first source QoS information is used to indicate that the first packet is mapped to a first quality of service flow QoS flow, and the QoS configuration of the first QoS flow includes: and indicating information, wherein the indicating information is used for indicating whether resources corresponding to the first QoS flow are reserved or not.

With reference to the third aspect, in some implementations of the third aspect, the mapping the first packet to the first QoS flow includes: the first source QoS information includes a QoS characteristic corresponding to a QoS characteristic indicated by a 5QI in the QoS flow.

With reference to the third aspect, in some implementations of the third aspect, the processing unit is further configured to determine a state of a transmission node in a path through which the first packet is transmitted; when the state of at least one of the input nodes meets a preset condition, the processing unit is further configured to start an active safeguard mechanism.

With reference to the third aspect, in certain implementations of the third aspect, when the state of the at least one input node satisfies a preset condition, the processing unit is further configured to initiate an active safeguard mechanism that includes one or more of: when there is packet loss in the at least one of the input nodes, the processing unit is further configured to determine to repeatedly send the first packet; or when the packet loss rate of the at least one transmission node is greater than the preset value, the processing unit is further configured to determine to encode the first packet by using a forward error correction FEC redundancy coding method.

In a fourth aspect, an apparatus for transmitting a packet is provided, where the apparatus for transmitting a packet includes:

a receiving unit, configured to receive multiple messages, where five-tuple information of the multiple messages is the same, each message in the multiple messages includes source QoS information, and the source QoS information included in each message is used to guarantee QoS for the QoS message corresponding to the message, and the source QoS information included in the multiple messages is different; and the processing unit is used for processing the plurality of messages based on the source QoS information included in the plurality of messages.

Or, the apparatus for transmitting a packet includes:

a receiving unit, configured to receive multiple packets, where 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 a packet corresponding to the source QoS information; and the processing unit is used for processing the plurality of messages based on the source QoS information included in the plurality of messages.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the multiple messages belong to the same connection, and the source QoS information included in the multiple messages is different and includes: the first source QoS information included in the first message in the connection is different from the second source QoS information included in the second message in the connection, wherein the first message and the second message are any two messages in the plurality of messages.

Or it can be understood that, the receiving unit receives multiple packets, where the multiple packets have the same five-tuple information, the multiple packets have different source QoS information, and the source QoS information is used to perform QoS guarantee on the corresponding packet, where the receiving unit includes: the receiving unit receives a first message and a second message, wherein five-tuple information of the first message is the same as five-tuple information of the second message, first source QoS information included in the first message is different from second source QoS information included in the second message, the first source QoS information is used for QoS guarantee of the first message, and the second source QoS information is used for QoS guarantee of the second message.

Further, the messages belong to the same connection.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the first source QoS information includes a first QoS characteristic and a first data characteristic, the first data characteristic represents a transmission characteristic of the first packet, the second source QoS information includes a second QoS characteristic and a second data characteristic, the second data characteristic represents a transmission characteristic of the second packet, and the processing unit is further configured to: determining the QoS requirement of the first message according to the first QoS characteristic; determining the QoS requirement of the second message according to the second QoS characteristic; the processing unit processes the plurality of messages based on the source QoS information included in the plurality of messages, including: scheduling resources of the first message according to the QoS requirement of the first message and the first data characteristic; and scheduling the resource of the second message according to the QoS requirement of the second message and the second data characteristic.

With reference to the fourth aspect, in some implementations of the fourth aspect, the different 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 characteristic and the second data characteristic are different, and/or the first QoS characteristic and the second QoS characteristic are different.

With reference to the fourth aspect, in some implementations of the fourth aspect, the resource for scheduling the first packet is different from the resource for scheduling the second packet.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the first data characteristic includes a connection-level data characteristic and/or a packet-level data characteristic, and the processing unit is further configured to: determining the transmission characteristics of a plurality of messages included in the connection according to the data characteristics of the connection level; and determining the transmission characteristics of the first message according to the data characteristics of the packet level.

With reference to the fourth aspect, in some implementations of the fourth aspect, the first QoS characteristic includes a QoS characteristic of a connection level, and the processing unit is further configured to: and determining the QoS requirement of a third message except the first message and the second message in the plurality of messages in the connection according to the QoS characteristics of the connection level.

With reference to the fourth aspect, in some implementations of the fourth aspect, the data characteristics of the connection level include one or more of: average rate, duration, frequency, size, delay budget, peak frequency, peak size, peak delay budget, peak transmission time, emergency type, expected emergency occurrence time, expected emergency message volume, and emergency message delay budget, wherein the average rate indicates the average transmission rate of messages in the connection, the duration indicates the duration of the connection, the frequency indicates the message transmission frequency, the size indicates the average value of messages transmitted per frequency, the delay budget indicates the time consumption budget for all messages transmitted to the receiving end within a period, the peak generation frequency of the peak frequency indicates the time consumption budget for all message peaks transmitted to the receiving end, the peak transmission time indicates the time for transmitting the message peaks, the type of emergency indicates the category to which the suddenly occurring time belongs, The expected time of occurrence of the emergency indicates the expected arrival time of the emergency message, the expected volume of the emergency message indicates the volume of the emergency transmission message, and the time delay budget of the emergency message indicates the time consumption budget for transmitting all the emergency messages to the receiving end.

With reference to the fourth aspect, in some implementations of the fourth aspect, the packet-level data characteristics include one or more of: the data block sequence number indicates the data block number to which the first message belongs, the data block size indicates the data block size to which the first message belongs, the packet position indicates the position of the data block to which the first message belongs, and the data block delay budget indicates the time consumption budget for transmitting the first message to a receiving end.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the connection-level QoS characteristics include a connection QoS characteristics indication CQI and/or connection QoS characteristics information, and the packet-level QoS characteristics include a packet QoS indication PQI and/or packet QoS characteristics information.

With reference to the fourth aspect, in some implementations of the fourth aspect, the receiving unit is further configured to receive a packet filtering rule from a core network device, where the packet filtering rule includes the CQI and/or the PQI; the processing unit is further configured to map the first packet to a first quality of service flow QoS flow according to the CQI and/or the PQI.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the receiving unit is further configured to receive a reflection trigger indication RDI and the PQI; the processing unit is further configured to record the PQI according to the RDI, where the PQI is used to indicate that a fourth packet is mapped to a third QoS flow; the fourth message is a message to be sent, and the QoS characteristic indicated by the 5QI in the third QoS flow corresponds to the PQI.

With reference to the fourth aspect, in some implementations of the fourth aspect, the QoS characteristics represented by the connection-level QoS characteristics or packet-level QoS characteristics include one or more of: resource type, priority, delay budget, and error rate.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the including, in the first packet, the first source QoS information includes: the first message comprises information of a connection level and information of a packet level; or, the first message 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 packet-level information, and the connection-level information is transmitted through the control plane, where the connection-level information includes the connection-level data characteristics and the connection-level QoS characteristics, and the packet-level information includes the packet-level data characteristics and the packet-level QoS characteristics.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the processing unit is further configured to: mapping the first message to a first QoS flow according to the first source QoS information; mapping the second message to a second QoS flow according to the second source QoS information; wherein the first QoS flow and the second QoS flow belong to a QoS flow group.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the processing unit is further configured to: mapping the first message to a service quality identifier 5QI of the first 5G network according to the first source QoS information; mapping the second message to a second 5QI according to the second source QoS information; wherein the first 5QI and the second 5QI belong to one QoS flow.

With reference to the fourth aspect, in some implementations of the fourth aspect, the mapping, by the processing unit, the first packet to the first QoS flow according to the first source QoS information includes: the processing unit determines the first QoS flow from a plurality of QoS flows according to a first QoS characteristic included in the first source QoS information, wherein the first QoS characteristic included in the first source QoS information corresponds to a QoS characteristic indicated by 5QI in the first QoS flow.

With reference to the fourth aspect, in some implementations of the fourth aspect, the QoS configuration of the first QoS flow includes: the maximum guaranteed bandwidth MGFBR; the processing unit is further configured to: determining that the guaranteed bandwidth of the first QoS flow is less than or equal to the MGFBR.

With reference to the fourth aspect, in some implementations of the fourth aspect, the QoS configuration of the first QoS flow further includes: minimum guaranteed bandwidth GFBR; the processing unit is further configured to: and determining 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.

With reference to the fourth aspect, in some implementations of the fourth aspect, the QoS configuration of the first QoS flow includes: indicating information, wherein the indicating information is used for indicating whether resources corresponding to the first QoS flow are reserved or not; the processing unit is further configured to: and determining whether to reserve the resources corresponding to the first QoS flow according to the indication information.

With reference to the fourth aspect, in some implementations of the fourth aspect, the first source QoS information is received, or the first source QoS information is locally generated; when the first source QoS information is locally generated, the processing unit is further configured to: and filling the first source QoS information into the first message.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the processing unit is further configured to: determining the state of a transmission node in a path for transmitting the first message; when the state of at least one of the input nodes meets a preset condition, the processing unit is further configured to start an active safeguard mechanism.

With reference to the fourth aspect, in some implementations of the fourth aspect, when the state of the at least one input node meets a preset condition, the processing unit is configured to initiate an active safeguard mechanism that includes one or more of: when the packet loss exists in the at least one input node, the processing unit determines to repeatedly send the first message; or when the packet loss rate of the at least one transmission node is greater than a preset value, the processing unit determines to encode the first message by using a Forward Error Correction (FEC) redundancy coding mode.

In a fifth aspect, a device for transmitting a message is provided, where the device for transmitting a message includes a processor, and is configured to implement the function of the message generating apparatus in the method described in the first aspect.

Optionally, the apparatus for transmitting a message may further include a memory, the memory is coupled to the processor, and the processor is configured to implement the function of the message generating device in the method described in the first aspect.

In one possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, and the processor can call and execute the 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.

Optionally, 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, or a circuit, etc.

In one possible design, the means for transmitting the message includes: a processor and a communication interface, wherein the processor is connected with the communication interface,

the processor is configured to run a computer program to enable the apparatus for transmitting a message to implement any one of the methods described in the first aspect;

the processor communicates with the outside using the communication interface.

It will be appreciated that the external may be an object other than a processor, or an object other than the apparatus.

In another possible embodiment, the device for transmitting messages is a chip or a chip system. The communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or system of chips, etc. The processor may also be embodied as a processing circuit or a logic circuit.

A sixth aspect provides a device for transmitting a message, where the device for transmitting a message includes a processor, and is configured to implement the function of the message receiving apparatus in the method described in the second aspect.

Optionally, the apparatus for transmitting a message may further include a memory, the memory being coupled to the processor, and the processor being configured to implement the function of the message receiving device in the method described in the second aspect.

In one possible implementation, the memory is used to store program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory, so as to implement the functions of the message receiving apparatus in the method described in the second aspect.

the processor communicates with the outside by using the communication interface;

the processor is configured to run the computer program to enable the apparatus for transmitting a message to implement any one of the methods described in the second aspect.

It will be appreciated that the external portion may be an object other than a processor, or an object other than the apparatus.

In another possible embodiment, the device for transmitting messages is a chip or a system of chips. The communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit, etc. on the chip or system of chips. The processor may also be embodied as a processing circuit or a logic circuit.

In a seventh aspect, the present application provides a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the method of the above aspects.

In an eighth aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

In a ninth aspect, a communication system is provided, which includes the apparatus for transmitting a message shown in the third aspect and the apparatus for transmitting a message shown in the fourth aspect.

In a tenth aspect, a chip apparatus is provided, which includes a processing circuit, and the processing circuit is configured to call and run a program from a memory, so that a communication device in which the chip apparatus is installed executes the method in any one of the possible implementation manners of the first and second aspects.

Drawings

Fig. 1 is a schematic diagram of a network architecture to which the embodiment of the present application is applicable.

Fig. 2(a) is a schematic flowchart of a method for transmitting a packet according to an embodiment of the present application.

Fig. 2(b) is a schematic flow chart of another method for transmitting a packet according to an embodiment of the present application.

Fig. 3 is a schematic diagram of a header structure of a network protocol version 4 (IPV4) message.

Fig. 4 is a schematic diagram of a header structure of a network protocol version 6 (IPV6) message.

Fig. 5 is a schematic diagram of a header structure of a real-time transport protocol (RTP) packet.

Fig. 6 is a schematic diagram of an RTP extension header format.

Fig. 7 is a schematic diagram of a general packet radio service tunneling protocol (GTP) protocol format.

Fig. 8 (a) is a schematic diagram of a 5G QoS flow model.

Fig. 8 (b) is a schematic diagram of a QoS flow model provided in an embodiment of the present application.

Fig. 8 (c) is a schematic diagram of another QoS flow model provided in the embodiment of the present application.

Fig. 9 is a schematic flow chart of a reflective QoS mechanism provided in an embodiment of the present application.

Fig. 10 is a schematic diagram of an apparatus 1000 for transmitting a message according to the present application.

Fig. 11 is a schematic structural diagram of a message generation apparatus 1100 applicable to the embodiment of the present application.

Fig. 12 is a schematic diagram of another apparatus 1200 for transmitting a message according to the present application.

Fig. 13 is a schematic structural diagram of a message receiving apparatus 1300 applicable to the embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a network architecture to which the embodiment of the present application is applicable. The following describes each part involved in the network architecture shown in fig. 1.

1. User Equipment (UE) 110: may include a variety of handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication capabilities, as well as various forms of terminals, Mobile Stations (MSs), terminals (terminals), or soft terminals, etc. Such as water meters, electricity meters, sensors, etc.

Illustratively, the user equipment in the embodiments of the present application may refer to an access terminal, a subscriber unit, a subscriber station, a mobile station, a relay station, a remote terminal, a mobile device, a user terminal (user terminal), a terminal device (terminal equipment), a wireless communication device, a user agent, or a 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 handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a user equipment in a 5G network or a user equipment in a Public Land Mobile Network (PLMN) for future evolution, or a user equipment in a vehicle networking for future evolution, and the like, which is not limited in this embodiment.

By way of example and not limitation, in the embodiments of the present application, a wearable device may also be referred to as a wearable smart device, which is a generic term for intelligently designing daily wearing and developing wearable devices, such as glasses, gloves, watches, clothing, shoes, and the like, by applying wearable technology. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

In addition, in the embodiment of the present application, the user equipment may also be user equipment in an internet of Things (IoT) system, where IoT is an important component of future information technology development, and a main technical feature of the present application is to connect an article with a network through a communication technology, so as to implement an intelligent network with interconnected human-computer and interconnected objects. In the embodiment of the present application, the IOT technology may achieve massive connection, deep coverage, and power saving for the terminal through a Narrowband (NB) technology, for example.

In addition, in this embodiment of the application, the user equipment may further include sensors such as an intelligent printer, a train detector, and a gas station, and the main functions include collecting data (part of the user equipment), receiving control information and downlink data of the access network equipment, and sending electromagnetic waves to transmit uplink data to the access network equipment.

In this embodiment, the apparatus for implementing the function of the user equipment may be the user equipment, or may be an apparatus capable of supporting the user equipment to implement the function, for example, a chip system or a combined device and a component capable of implementing the function of the user equipment, and the apparatus may be installed in the user equipment.

In the embodiment of the present application, the chip system may be formed by a chip, and may also include a chip and other discrete devices. In the technical solution provided in the embodiment of the present application, a device for implementing a function of a user equipment is taken as an example of the user equipment, and the technical solution provided in the embodiment of the present application is described.

2. (radio access network, (R) AN) 120: the method and the device are used for providing a network access function for authorized user equipment in a specific area, and can use transmission tunnels with different qualities according to the level of the user equipment, the service requirement and the like.

The (R) AN can manage radio resources and provide access services for the ue, thereby completing forwarding of control signals and ue data between the ue and the core network, and the (R) AN can also be understood as a base station in a conventional network.

The access network device in the embodiment of the present application may be any communication device with a wireless transceiving function for communicating with the user equipment. The access network devices include, but are not limited to: evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), home base station (home enodeb, HeNB, or home Node B, HNB), baseBand unit (BBU), Access Point (AP), wireless relay Node, wireless backhaul Node, Transmission Point (TP), or Transmission and Reception Point (TRP) in a wireless fidelity (WIFI) system, and the like, and may also be 5G, such as New Radio (NR), NB in a system, or a transmission point (TRP or TP), and one or more antennas in a base station (NB) or a group of NB, and may also be a panel of a network or a panel of a base station (NB), such as a baseband unit (BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and a DU. The gNB may also include an Active Antenna Unit (AAU). The CU implements part of the function of the gNB and the DU implements part of the function of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing functions of a Radio Resource Control (RRC) layer and a Packet Data Convergence Protocol (PDCP) layer. The DU is responsible for processing a physical layer protocol and a real-time service, and implements functions of a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. The AAU implements part of the physical layer processing functions, radio frequency processing and active antenna related functions. Since the information of the RRC layer eventually becomes or is converted from the information of the PHY layer, the higher layer signaling, such as the RRC layer signaling, may also be considered to be transmitted by the DU or by the DU + AAU under this architecture. It is to be understood that the access network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into access network devices in an access network (RAN), or may be divided into access network devices in a Core Network (CN), which is not limited in this application.

In this embodiment of the present application, the apparatus for implementing the function of the access network device may be an access network device, or may be an apparatus capable of supporting the access network device to implement the function, for example, a chip system or a composite device or a component capable of implementing the function of the access network device, and the apparatus may be installed in the access network device. In the technical solution provided in the embodiment of the present application, taking an example that a device for implementing a function of an access network device is an access network device, the technical solution provided in the embodiment of the present application is described.

The interface between the access network device and the user equipment may be a Uu interface (or referred to as an air interface). Of course, in future communications, the names of these interfaces may be unchanged or replaced by other names, which are not limited in this application.

Illustratively, communication between the access network device and the user equipment follows a certain protocol layer structure, e.g., the control plane protocol layer structure may include an RRC layer, a PDCP layer, an RLC layer, a MAC layer, and a physical layer; the user plane protocol layer structure may include a PDCP layer, an RLC layer, an MAC layer, and a physical layer, and in a possible implementation, the PDCP layer may further include a Service Data Adaptation Protocol (SDAP) layer.

3. The user plane network element 130: for packet routing and forwarding, quality of service (QoS) handling of user plane data, etc.

In the 5G communication system, the user plane network element may be a User Plane Function (UPF) network element. In a future communication system, the user plane network element may still be a UPF network element, or may also have another name, which is not limited in this application.

4. Data network element 140: for providing a network for transmitting data.

In the 5G communication system, the data network element may be a Data Network (DN) element. In future communication systems, the data network element may still be a DN element, or may also have another name, which is not limited in this application.

5. The access management network element 150: the method is mainly used for mobility management, access management and the like, and can be used for realizing other functions except session management in Mobility Management Entity (MME) functions, such as functions of lawful interception, access authorization/authentication and the like.

In the 5G communication system, the access management network element may be an access and mobility management function (AMF) network element. In the future communication system, the access management network element may still be an AMF network element, or may also have another name, which is not limited in this application.

6. Session management network element 160: the method is mainly used for session management, Internet Protocol (IP) address allocation and management of the user equipment, selection of a termination point capable of managing a user plane function, a policy control and charging function interface, downlink data notification and the like.

In the 5G communication system, the session management network element may be a Session Management Function (SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or may also have another name, which is not limited in this application.

It is to be understood that the above network elements or functions may be network elements in a hardware device, or may be software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).

For convenience of description, in the following description, an access management function network element is an AMF network element, a data network element is a DN network element, a user plane function network element is a UPF network element, and a session management function network element is an SMF network element.

Further, the AMF network element is abbreviated as AMF, the DN network element is abbreviated as DN, the UPF network element is abbreviated as UPF, and the SMF network element is abbreviated as SMF. That is, AMFs described later in the present application may be replaced with access management function network elements, DNs may be replaced with data network elements, UPFs may be replaced with user plane function network elements, and SMFs may be replaced with session management function network elements.

For convenience of description, in the present application, a method for transmitting a packet is described by taking devices as an AMF entity, a DN entity, an UPF entity, and an SMF entity as examples, and for an implementation method in which a device is a chip in an AMF entity, a chip in an UPF entity, or a chip in an SMF entity, reference may be made to specific descriptions of the devices as an AMF entity, an UPF entity, and an SMF entity, and no repeated description is given.

In the network architecture shown in fig. 1, the user equipment is connected to the AMF through an N1 interface, the RAN is connected to the AMF through an N2 interface, and the RAN is connected to the UPF through an N3 interface.

The UPFs are connected through an N9 interface, and are interconnected with the DN through an N6 interface.

The SMF controls the UPF via the N4 interface. The AMF interfaces with the SMF through an N11 interface.

It should be noted that the names of the network elements and the communication interfaces between the network elements referred to in fig. 1 are simply described by taking the examples defined in the current protocol as examples, but the embodiments of the present application are not limited to be applicable only to currently known communication systems. Therefore, the standard names appearing when the current protocol is described as an example are all functional descriptions, and the specific names of the network elements, interfaces, signaling and the like in the present application are not limited, and only indicate the functions of the network elements, interfaces or signaling, and can be correspondingly extended to other systems, such as 3G, 4G, 5G or future communication systems.

The network architecture applicable to the embodiment of the present application shown in fig. 1 is only an example, and the network architecture applicable to the embodiment of the present application is not limited thereto, and any network architecture capable of implementing the functions of the network elements described above is applicable to the embodiment of the present application.

For example, in some network architectures, network function network element entities such as an AMF network element, an SMF network element, and an UPF network element are all called Network Function (NF) network elements; alternatively, in other network architectures, a set of network elements such as an AMF network element, an SMF network element, and a UPF network element may be referred to as a control plane function network element.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a 5G, a New Radio (NR), a future network, or the like. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system. 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 internet of Things (IoT) communication system, or other communication systems.

In an embodiment of the present application, a user equipment or an access network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a Central Processing Unit (CPU), a Memory Management Unit (MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processing through processes (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 comprises applications such as a browser, an address list, word processing software, instant messaging software and the like. Furthermore, the embodiment of the present application does not particularly limit the specific structure of the execution main body of the method provided in the embodiment of the present application, as long as the program recorded with the code of the method provided in the embodiment of the present application can be executed to perform communication according to the method provided in the embodiment of the present application, for example, the execution main body of the method provided in the embodiment of the present application may be a user equipment or an access network device, or a functional module capable of calling the program and executing the program in the user equipment or the access network device.

In addition, 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. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disk, floppy disk, or magnetic tape), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), card, stick, or key drive, etc.). In addition, 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" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.

In order to facilitate understanding of the embodiments of the present application, a brief description is given of several basic concepts involved in the embodiments of the present application. It should be understood that the basic concept described below is simply illustrated by taking the basic concept specified in the NR protocol as an example, but does not limit the application of the embodiments to the NR system.

1. IETF QoS service model:

in a conventional IP network, all messages are treated identically and indiscriminately, each forwarding device processes all messages by using a First In First Out (FIFO) policy, and sends the messages to a destination as much as possible, but does not provide any guarantee for the reliability of message transmission, transmission delay, and other performances.

With the continuous emergence of new applications on IP networks, new requirements are also imposed on the service quality of the IP networks, for example, real-time services such as voice over Internet protocol (VoIP) and the like impose high requirements on the transmission delay of messages (relatively speaking, electronic Mail (E-Mail) and File Transfer Protocol (FTP) services are not sensitive to time delay). In order to support services such as voice, video and data with different service requirements, a network is required to be able to distinguish different communications and provide corresponding services for the different communications. QoS technologies have thus emerged, and the IETF defines three QoS service models:

1) best-effort service model:

the best-effort service model is the simplest service model. The application can send out any number of messages at any time, and does not need to be approved in advance, nor does it need to notify the network device. For the best-effort service model, the network device sends the message as much as possible. But does not provide any guarantees on performance such as time delay, reliability, etc.

The best-effort service model is suitable for most network applications, such as FTP, E-Mail, etc., and is implemented by FIFO queues.

2) IntServ service model:

before sending a message, the IntServ service model needs to apply for a specific service to a network device through resource reservation Protocol (RSVP) signaling. RSVP applies for network resources (e.g., bandwidth, latency, etc.) for an application before the application begins sending messages, and is therefore out-of-band signaling. Once the network device confirms that resources are allocated for the application, the network device maintains a state for each connection and performs classification, traffic policing, queuing, and scheduling of packets based on this state. As long as the messaging control of the application is within the scope of the flow parameter description, the network device will promise to meet the QoS requirements of the application.

Specifically, the network device maintains the connection state by configuring a five-tuple, where the five-tuple includes a source IP address, a destination IP address, a protocol number, a source port, and a destination port.

3) DiffServ service model:

unlike the IntServ service model described above, the diffserv service model does not require the use of RSVP, i.e., the application does not need to notify the network device to reserve resources for it before sending out a message. For the DiffServ service model, the network device does not need to maintain a state for each flow, and the network device provides a specific service according to a differentiated services class (differentiated services code point (DSCP) value of a differentiated services flag field in an IP packet header) of each packet.

In a network implementing a DiffServ service model, each forwarding device executes a corresponding forwarding behavior according to a DSCP field of a packet, and the forwarding behavior mainly includes the following three types of forwarding behaviors:

expedited Forwarding (EF): the method is mainly used for services with low delay, jitter and packet loss rate, wherein the services generally run at a relatively stable speed and need to be quickly forwarded in forwarding equipment;

assured Forwarding (AF): the method adopts the technical scheme that the forwarding can be ensured when the maximum allowed bandwidth is not exceeded by adopting the service ensuring forwarding behavior, once the maximum allowed bandwidth is exceeded, the forwarding behavior is divided into 4 classes, each class can be divided into 3 different drop priorities, and each class is ensured to be capable of allocating different bandwidth resources. The IETF suggests to use 4 different queues to transmit AF1x, AF2x, AF3x, AF4x traffic, respectively, and each queue provides 3 different drop priorities, so that 12 Per-Hop behaviors with guaranteed forwarding (Per-Hop Behavior, PHB) can be constructed;

best-effort delivery (BE): the method is mainly used for services insensitive to time delay, jitter and packet loss.

The DiffServ service model only contains a limited number of service levels and a small number of state information, so the DiffServ service model is simple to realize and has better expansibility and is a mainstream QoS solution of an IP network in the industry.

A disadvantage of the DiffServ service model is that it is difficult to provide flow-based end-to-end quality assurance. Because the IETF defines the recommended DSCP values for each standard PHB, the equipment vendors can redefine the mapping between the DSCP and PHB, there is a difficulty in interworking between DiffServ networks of different operators, which need to maintain consistent DSCP and PHB mappings when interworking.

The service model referred to in the embodiments of the present application refers to a set of end-to-end QoS functions.

2. The QoS flow mechanism:

in the 3GPP R16 standard, QoS flows are minimum QoS control granularity, and each QoS flow has a corresponding QoS configuration.

The QoS parameters included in the QoS configuration describe specific QoS requirements, and the QoS parameters mainly include:

QoS Flow Index (QFI), quality of service identifier 5QI of the 5G network, guaranteed flow rate (GFBR), maximum flow rate (MFBR).

Further, 5QI of the QoS parameters is a set of QoS feature combination indices, the QoS features including:

resource type (resource type), priority level (priority level), packet delay budget (packet delay budget), packet error rate (packet error rate), statistical period (averaging window), and maximum burst size (maximum data burst volume).

Wherein, the resource types include: non-guaranteed bit rate (non-GRB), guaranteed bit rate (GRB), delay-sensitive GRB (delay-critical GBR); the maximum burst data size is a specific parameter of the delay sensitive GRB. Specifically, the 3GPP R16 standard defines a part of 5QI QoS characteristic values, which can be directly used. The 3GPP also allows operators and/or device manufacturers to assign non-conflicting 5QI and preset corresponding QoS tag values for use in the operator's network.

After the QoS flow configuration is generated, the 5G control plane network elements AMF and SMF issue the QoS flow configuration to the UE, RAN and UPF, and issue packet filtering rules (packet filters set) to the UE and UPF at the same time.

The UE maps the uplink message to a corresponding QoS flow according to a packet filtering rule;

and the UPF maps the downlink message received from the port N6 to the corresponding QoS flow according to the packet filtering rule.

The data downlink process in the current 5G scene comprises the following steps:

step 1: the user data is contained in an IP message and is sent to UPF equipment of a 5G core (5G core, 5GC) from DN through an N6 interface;

step 2: the UPF maps the IP message to a corresponding QoS flow according to QoS configuration and packet filters set issued by a 5GC control plane;

specifically, packet filters set defined by the 5G R16 standard contains the following parameters:

source port number (source port number), destination port number (destination port number), protocol type (e.g., protocol ID of the IP protocol or next header type), service type of IPV4 header field (TOS) or traffic class in IPV4 header, flow label field in IPV6 (flow label (IPV6)), security parameter index (security parameter index) and packet direction (packet filter direction).

And step 3: the UPF performs targeted guarantee and processing according to the QoS requirement of the QoS flow to which the message belongs;

and 4, step 4: the UPF uses a general packet radio service tunneling protocol-user plane (GTP-U) protocol to encapsulate a user plane IP message, fills QFI of QoS flow to which the message belongs in a header field of the GTP-U protocol, and then forwards the message to an N3 interface.

At present, an SDAP protocol layer is newly added to a 5G air interface user plane, and a 5G QoS mechanism is adapted, wherein the SDAP can realize mapping between QoS flow and Data Radio Bearer (DRB) and a reflective QoS mechanism, and an uplink flow includes:

step 1: the control surface of the 5GC issues a plurality of QoS rules to the UE, wherein each QoS rule comprises a packet filters set and a bound QFI;

step 2: after receiving an IP message to be sent by an Application (APP), a UE bottom layer (SDAP protocol stack) matches the message to a corresponding QoS flow according to a packet filters set in a QoS rule, and fills a corresponding QFI in the head of an air interface data packet;

and step 3: the UE maps the IP message to DRBs with different bearing standards according to the QoS requirement of QoS flow and sends the IP message;

and 4, step 4: and after receiving the message sent by the UE, the RAN side encapsulates the user plane IP message by using a GTP-U protocol, fills QFI (quad Flat interface) of QoS (quality of service) flow which is analyzed from an air interface data packet header into a GTU-U protocol header field, and then forwards the message to an N3 interface.

In order to simplify the process of issuing the QoS rules by the 5GC control plane, the UE may learn the QoS rules through the QoS reflection mechanism, which specifically includes:

in downlink data sent to the UE by the access network device, an SDAP protocol header of an air interface protocol stack includes QFI and whether a reflection QoS indication is supported: reflecting QoS flow to DRB mapping indication (RDI);

after receiving the downlink message, if the RDI is found to be 1, the UE records the five-tuple of the message, QFI information and DRB information as a QoS rule learned through a reflection QoS mechanism;

when the UE sends the uplink message, the UE can use the QoS rule learned by the reflection QoS mechanism to carry out matching, and the message is matched to the corresponding QoS flow and DRB to be sent.

The QoS flow mechanism quantifies QoS requirements, and a transmission device in the network can clearly confirm and process the QoS requirements only through a QoS Flow Indicator (QFI) in a message (for example, obtain a QoS feature corresponding to a QoS configuration corresponding to 5QI according to QFI). Therefore, the QoS flow mechanism solves the problem that different equipment vendors and/or different operators realize inconsistent mapping between the DSCP and the PHB in the IETF Diffserv service model.

It should be understood that the above descriptions of the IETF QoS service model and the QoS flow mechanism are only provided for better understanding of the simple description provided by the method for transmitting a packet provided by the present application, and the scope of protection of the present application is not limited at all.

As can be seen from the IETF QoS service model and the QoS flow mechanism, when a forwarding node in a transmission network forwards an IP packet, the packet is matched to a preset QoS policy according to network layer characteristics of the IP packet, and a differentiated assurance processing mode is performed according to the QoS policy.

Specifically, the network layer characteristics of the IP packet may be the above five tuple, TOS, DSCP, or QFI; the QoS policy is obtained through configuration or control plane delivery.

However, under the current QoS mechanism (IETF QoS service model or QoS flow mechanism), the application cannot clearly and exhaustively indicate the QoS requirement to the transport network, and further, the application cannot indicate the application layer data feature to the transport network.

For example, information that the connection level is not supported and/or information that the IP packet level is not supported is indicated to the transport network.

Wherein the information that the connection level is not supported includes:

data characteristics of connection level: such as video group of picture (GOP) features (average code rate, frame rate, I-frame frequency, etc.), Internet of things (IOT) data reporting features (reporting period, data size, etc.);

connection level incident information: a drag event when video on demand, a turn-around event when Virtual Reality (VR) is played, etc.

The information that the IP packet level is not supported includes:

IP packet to data segment relationship: if the current IP packet belongs to which frame of the video, the video frame has more data after the IP packet;

QoS indication at IP packet level: due to packet filtering rules and transport protocol limitations, different packets in a connection in current QoS mechanisms are difficult to map to different QoS policies (e.g., I frame data and P frame data in a video connection may use different QoS policies).

In addition, 3GPP R16 defines a packet filters set mechanism for instructing UPF, UE to map the packet to QoS flow. However, in practical use, the requirement on networking is high, the limitation is large and the use is inconvenient according to the mapping of five tuples and protocol types. The problems of transmission layer crosstalk and information loss exist by using TOS or DSCP mapping, and the problems specifically include that:

DSCP/TOS is qualitative QoS expectation, 5QI is quantitative QoS index, and mutual conversion may cause information loss; or alternatively

The DSCP/TOS may be modified by the routing equipment of the transport network and the APP cannot reliably deliver QoS features to the 3GPP network.

Furthermore, the QoS flow mechanism is a macro control mode in which a control plane (AMF, SMF) negotiates and issues QoS strategy configuration to a user plane (UPF, RAN), and a user plane message is matched with a corresponding QoS mechanism according to rules; the IntServ service model of IETF uses a resource reservation protocol (RVSP) protocol, DiffServ uses a configuration function in the operation and maintenance field to issue QoS policy configuration, and also belongs to a macro control mode. In the macro control mode, the QoS policy changes the decision and executes the chain length, and the change takes time (second level or even minute level), so that the service requirement that the QoS policy needs frequent and rapid adjustment cannot be met. And the QoS strategy change interfaces of different transmission networks need to be applied and called, so that the development difficulty is high and the requirement is high.

For example, GFBR and/or maximum burst volume (MDBV) in a 5G QoS flow cannot be dynamically adjusted according to the change in the number of connections;

for example, the number of concurrent connections of one ue may be dynamically changed (for example, a Customer Premises Equipment (CPE) may hang 1, 3, or N devices), and reserving a number of concurrent connections according to the maximum possible number may greatly waste air interface resources; the service calls a 5GC open interface to dynamically adjust GFBR or MDBV, which results in great difficulty in application development, and operators do not necessarily open the capability for safety reasons.

In order to solve the problems of the current QoS mechanism, the present application provides a method for transmitting a packet, which uses a channel following manner to carry source QoS information in the packet, and a transceiving end and a transmission network implement end-to-end QoS guarantee according to the source QoS information.

It should be noted that the QoS information related in the embodiment of the present application may be understood as a QoS parameter, and may also be understood as an identifier indicating the QoS parameter, so as to provide QoS guarantee for the packet.

Specifically, through the source QoS information, the sending end can clearly and exhaustively indicate the application data characteristics and the QoS requirements to the transmission network; and/or

Through the source QoS information, forwarding equipment in a transmission network can clearly sense connection level, message level data characteristics and QoS requirements through messages, and guarantee and optimize according to instructions; and/or

Through the source QoS information, the transmission equipment can trigger the pipeline QoS strategy to be rapidly adjusted within a reasonable range according to the sensed data characteristics.

It should be understood that the method provided by the embodiment of the present application can be applied to a 5G communication system, for example, the communication system shown in fig. 1.

The following embodiments are not limited to specific structures of execution subjects of the methods provided by the embodiments of the present application, as long as the execution subjects can perform communication according to the methods provided by the embodiments of the present application by running a program recorded with codes of the methods provided by the embodiments of the present application, for example, the execution subjects of the methods provided by the embodiments of the present application may be user equipment, access network equipment, or core network equipment, or functional modules capable of invoking the programs and executing the programs in the user equipment, the access network equipment, or the core network equipment.

To facilitate understanding of the embodiments of the present application, the following description is made.

First, in the present application, "for indicating" may be understood as "enabling" which may include direct enabling and indirect enabling. When a piece of information is described as enabling a, the information may be included to directly enable a or indirectly enable a, and does not necessarily represent that a is carried in the information.

If the information enabled by the information is referred to as information to be enabled, in a specific implementation process, there are many ways for enabling the information to be enabled, for example, but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or an index of the information to be enabled. The information to be enabled can also be indirectly enabled by enabling other information, wherein an association relationship exists between the other information and the information to be enabled. It is also possible to enable only a portion of the information to be enabled, while other portions of the information to be enabled are known or predetermined in advance. For example, enabling specific information may also be implemented by means of a pre-agreed (e.g., protocol-specified) arrangement order of respective information, thereby reducing the enabling overhead to some extent. Meanwhile, the universal parts of all information can be identified and enabled uniformly, so that the enabling cost caused by independently enabling the same information is reduced.

Second, first, second, and various numerical numbers (e.g., "# 1", "# 2", etc.) shown in the present application are merely for convenience of description, and are not intended to limit the scope of the embodiments of the present application. E.g. to distinguish between different messages, etc. Rather than to describe a particular order or sequence. It should be understood that the objects so described are interchangeable under appropriate circumstances to enable description of aspects other than those of the embodiments of the application.

Third, in the present application, "preset" may include a predefined definition, for example, a protocol definition. The "predefined" may be implemented by saving a corresponding code, table, or other means that can be used to indicate the relevant information in advance in a device (for example, including a user device or a network device), and the present application is not limited to a specific implementation manner thereof.

Fourth, the term "store" referred to in the embodiments of the present application may refer to a store in one or more memories. The one or more memories may be provided separately or integrated in the encoder or decoder, the processor, or the communication device. The one or more memories may also be provided separately, with a portion of the one or more memories being integrated into the decoder, the processor, or the communication device. The type of memory may be any form of storage medium and is not intended to be limiting of the present application.

Fifth, the "protocol" referred to in the embodiments of the present application may refer to a standard protocol in the communication field, and may include, for example, a 5G protocol, a New Radio (NR) protocol, and related protocols applied in future communication systems, which is not limited in the present application.

Hereinafter, the method for transmitting a packet provided in the embodiment of the present application is described in detail by taking an interaction between a packet generating device and a packet receiving device as an example without loss of generality.

The application provides a method for transmitting a message. The execution body comprises a message generation device and a message receiving device.

When the embodiment of the present application is applied to downlink packet transmission, the packet generating device may be a network (e.g., a DN network element) for providing transmission data, and the packet receiving device includes a core network device (e.g., a UPF), an access network device, and a user equipment.

In another possible implementation manner, when the embodiment of the present application is applied to uplink packet transmission, the packet generating device may be an application layer in a user equipment, and the packet receiving device includes a bottom layer (e.g., an SDAP layer) in the user equipment, a core network device (e.g., a UPF), an access network device, and a data network (e.g., a DN network element).

For ease of understanding, the method for transmitting a packet provided by the present application is described below separately from the downlink and the uplink. In a downlink packet transmission scenario, as shown in fig. 2(a), fig. 2(a) is a schematic flowchart of a method for transmitting a packet according to an embodiment of the present application.

The method for transmitting the message at least comprises the following steps.

S210, the data network generates a first packet # 1.

Specifically, an application on the Internet generates a first packet #1 in a connection according to the QoS requirements of the service.

The first packet #1 includes first source QoS information, which is used to provide QoS guarantee for the first packet # 1. The QoS guarantee in the embodiment of the application comprises the steps of providing service for the message and solving the problems of network delay and/or network blockage and the like.

It should be noted that the messages referred to in this embodiment may be referred to as IP messages, data messages, service messages, packets, or messages, and the like, and the messages referred to hereinafter are only examples and do not limit the scope of the present application at all, and may be understood as data packets transmitted in a transmission network.

In addition, the first packet #1 may be any one of a plurality of packets generated by the data network, and the five-tuple information of the plurality of packets is the same, which may be understood that the plurality of packets belong to one connection. In this embodiment of the present application, the quintuple information of the packets in one connection is the same, and the quintuple information is used to indicate a quintuple of the packet, and may be a quintuple parameter (e.g., the source IP address, the destination IP address, the protocol number, the source port, and the destination port described above), or may be information indicating an indirect indication of the quintuple, such as an identifier #1 indicating the source IP address #1, an identifier #2 indicating the destination IP address #1, an identifier #3 indicating the protocol number #1, an identifier #4 indicating the source port #1, and an identifier #5 indicating the destination port # 1. Further, the method flow shown in (a) in fig. 2 further includes:

s220, the data network generates a second packet # 1.

The second packet #1 may be any one of the plurality of packets generated by the data network except for the first packet # 1. The second packet #1 includes second source QoS information, which is used to provide QoS guarantee for the second packet # 1.

It should be understood that the data network may also generate other packets in the connection, the above-mentioned generation of the first packet #1 and the second packet #1 is only an example, and the protection scope of the present application is not limited in any way, and in the embodiment of the present application, the data network may generate a plurality of packets, and the five-tuple information of the plurality of packets is the same.

Specifically, each of the multiple messages includes a source QoS parameter, and source QoS information included in each message is used to guarantee QoS for the corresponding message, and the source QoS information included in the multiple messages is different.

For example, the first source QoS information included in the first packet #1 and the second source QoS information included in the second packet #1 described above are not the same.

For example, the source QoS information included in a certain one of the plurality of messages is different from the source QoS information included in at least one of the plurality of messages other than the certain one of the plurality of messages.

For another example, the source QoS information of two of at least two messages included in the plurality of messages is different. The two source QoS information respectively included in the two messages means that each of the two messages includes one source QoS information.

Illustratively, the source QoS information includes QoS characteristics for indicating QoS requirements of the message and data characteristics for indicating transmission characteristics of the message.

For example, the first source QoS information includes a first QoS characteristic indicating a QoS requirement of the first packet and a first data characteristic indicating a transmission characteristic of the first packet.

For another example, the second source QoS information includes a second QoS characteristic indicating a QoS requirement of the second packet and a second data characteristic indicating a transmission characteristic of the second packet.

In the case that the source QoS information includes QoS characteristics and data characteristics, the source QoS information included in the plurality of packets may be different in that the data characteristics included in the plurality of packets are different, and/or the QoS characteristics included in the plurality of packets are different.

For example, a first data characteristic in the first source QoS information included in the first packet #1 and a second data characteristic in the second source QoS information included in the second packet #1 are different; and/or the presence of a gas in the atmosphere,

the first QoS characteristics in the first source QoS information included in the first packet #1 and the second QoS characteristics in the second source QoS information included in the second packet #1 are different.

It should be noted that, the connection includes the first packet #1 and the second packet #1, and the QoS characteristics included in the first packet #1 and the second packet #1 are different, which is only an example, and the protection scope of the present application is not limited in any way, and the connection may also include other packets, and the QoS characteristics included in different packets may be different. It can be understood that in the embodiment of the present application, multiple packets in one 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 the messages according to the QoS requirements of different messages.

For convenience of description, the source QoS information provided in the present application is described below by taking an example in which a certain message in a connection includes the source QoS information.

The source QoS information referred to in the embodiments of the present application is briefly described below:

the source QoS information includes QoS characteristics and further the source QoS information includes data characteristics.

The data characteristics include connection-level data characteristics and/or packet-level data characteristics. The data characteristics of the connection level are used for indicating the transmission characteristics of a plurality of messages included in the connection, namely indicating the transmission characteristics of the connection; the packet-level data characteristic is used to indicate the transmission characteristic of a certain packet, i.e. the packet-level data characteristic indicates the transmission characteristic of a packet including the packet-level data characteristic.

The data characteristic of the connection level includes connection basic information, and further the data characteristic of the connection level further includes at least one of periodic connection information, periodic connection peak information, or connection emergency notification information.

Wherein the connection basic information includes an average rate or duration. Specifically, the average rate indicates the average sending rate of the connection data, for example, the bitrate of a live video connection is 2Mbps, and the duration indicates the expected duration of the connection.

The periodic connection information includes a frequency, size, or delay budget. Specifically, the frequency indicates the data transmission frequency, for example, 25HZ (25 frames per second, one frame is generated every 40 ms), the size indicates the average value of data transmitted every frequency, for example, the average of P frames of a video live connection is 0.3Mbyte, and the delay budget indicates the time consumption budget for all data to be transferred to the receiving end in one period.

The periodic connection peak information includes peak frequency, peak size, peak delay budget or peak transmission time. Specifically, the peak frequency indicates the peak generation frequency, for example, 0.5HZ (one I frame occurs every two seconds (one GOP every 2 seconds)), the peak size indicates the peak transmission data mean (e.g., one I frame by 2MB), the peak delay budget indicates the time consumption budget for the peak data to be completely transferred to the receiving end, the peak transmission time indicates the available absolute time, relative time (after how many milliseconds now), and relative position (at which frequency).

The connection emergency notification information includes the type of the emergency, the expected time of the emergency, the expected data volume of the emergency or the delay budget of the data of the emergency. Specifically, the emergency type includes, for example, VR head turning, video playing dragging; the expected emergency occurrence time indicates the expected arrival time of the emergency data, and the relative time represents; the expected data volume of the emergency indicates the data volume which needs to be transmitted by the emergency; the incident data delay budget indicates the time consumption budget for the entire transmission of the incident to the receiving end.

It should be noted that, if the application side cannot implement the emergency pre-notification through the data feature at the connection level, the application side may use the data feature at the packet level to perform the real-time notification.

The packet-level data characteristics include packet data integrity information. The packet data integrity information includes a data block sequence number, a data block size, a packet location, or a data block delay budget. Specifically, the data block sequence number indicates the data block number to which the packet belongs, for example, a serial number by frame in a video stream; the block size indicates the block size to which the packet belongs, e.g., the P frame data segment size is 0.3 Mbytes; the packet position indicates the position of the packet in the data block; the data block delay budget indicates the time consumption budget for the entire transmission of the packet to the receiving end.

It should be noted that the data block referred to in the embodiments of the present application may be understood as a data block in a connection, and the data block may include at least one packet, for example, in a video stream, each I frame and P frame may be referred to as a data block. In addition, a data block may also be referred to as a data segment, a message block, or the like.

For example, a certain data block includes multiple packets, and the packet-level data characteristics in different packets include the location and sequence number of the packet in the data block.

In addition, it should be noted that data integrity transmission refers to that a receiving end receives all messages of a certain data block completely and then uses the messages in a scene (for example, a frame of a video), and a transmission network can be optimized and guaranteed in a targeted manner, so that transmission efficiency can be improved on the premise of not affecting the whole application delay.

The QoS characteristics comprise QoS characteristics of a connection level and/or QoS characteristics of a packet level, wherein the QoS characteristics of the connection level are used for indicating the QoS requirements of a plurality of messages included in the connection, namely the QoS requirements of the connection are indicated; the packet-level QoS characteristic is used to indicate the QoS requirement of a certain packet, i.e., the packet-level QoS characteristic indicates the transmission characteristic of a packet including the packet-level QoS characteristic.

Further, the connection level QoS feature may be a connection QoS feature indication CQI, the packet level QoS feature may be a packet QoS feature indication PQI, the CQI is a connection level QoS feature, and the PQI is a packet level QoS feature. When the message carries PQI, the message uses the QoS characteristic corresponding to PQI, otherwise, the message uses the QoS characteristic corresponding to CQI.

By means of the CQI and/or PQI, different packets in a connection may have different QoS characteristics.

Specifically, CQI and PQI describable QoS features include: resource type, priority, delay budget or error rate, wherein the resource type can be GBR, delay sensitive GBR, Non-GBR; the smaller the priority value is, the higher the priority is; the delay budget represents the expected E2E delay; the error rate may be the probability of packet errors or packet losses.

It should be understood that the above described QoS features that the CQI and PQI can describe are only examples, and do not limit the scope of the present application in any way, and the CQI and PQI can also describe other QoS features, which are not illustrated here.

When the QoS characteristics are used, the CQI and PQI characteristic values can be predefined through standards or enterprise specifications and are issued to a transmission network. Thus, as long as the CQI and PQI are carried in the packet, the transmission device can know the quantized QoS requirements at the connection level and/or the packet level.

It should be noted that the QoS feature is embodied in the form of CQI and/or PQI, which can save transmission overhead. Each QoS characteristic value can also be directly filled in the message as the data characteristics of other connection levels and the data characteristics of packet levels. For example, the connection-level QoS characteristics may also be connection QoS characteristics information, and the packet-level QoS characteristics may also be packet QoS characteristics information.

The source QOS information is carried in the message, which includes the following possibilities:

the following steps are possible: the connection information and the packet information are carried in the message;

and the possibility of two: the packet information is carried in the message, and the connection information is carried in the virtual dummy IP packet;

the possibility is three: the packet information is carried in a message, the connection information is transmitted through the control plane,

the connection information includes the data characteristics of the connection level and the QoS characteristics of the connection level, and the packet information includes the data characteristics of the connection level and the QoS characteristics of the packet level.

It should be understood that the above-mentioned one to three possibilities are only examples of how to send the source QOS information to other nodes in the transport network, and the scope of the present application is not limited in any way, and the source QOS information may also be sent to other nodes in the transport network through other possible implementations, for example, the source QOS information may be sent to the transport node through other information streams before sending the packet, and the corresponding relationship between the source QOS information and the packet is indicated.

Hereinafter, the QoS characteristics of the connection level are the above CQI, the QoS characteristics of the packet level are the above PQI, and how to carry the source QoS information is described as an example, and when the QoS characteristics of the connection level are the connection QoS characteristics information and the QoS characteristics of the packet level are the packet characteristics information, the filling manner is similar, and details are not described in this application.

Specifically, when source QOS information is carried in a message, a message transmission protocol needs to be extended.

In the embodiment of the application, several possible extension modes are provided:

the first method is as follows: the IPV4 expands.

The IPV4 message header structure request for comments (RFC) definition is shown in fig. 3, where fig. 3 is a schematic diagram of the structure of the IPV4 message header, and includes:

4-bit version number (version): IP protocol (IPv4) version number bit;

4-bit header length (header length): identifying how many 4 bytes of the header are, i.e., a maximum of 15 x 4 bytes;

8-bit service type (type of service): contains a 4-bit priority field: minimum latency, maximum throughput, highest reliability and minimum cost;

total length of 16bits (total length): indicates the length of the entire IP datagram;

16-bit identification (identification): identifying the datagram;

3-bit flag (flags): the fragment exists;

13-bit slice offset (fragment offset): fragmentation offset from the beginning of the original IP datagram;

time To Live (TTL): the number of routing hops a datagram is allowed to traverse before reaching its destination;

8-bit protocol (protocol): to distinguish upper layer protocols;

16-bit header checksum (header checksum): checking whether the datagram header is damaged during transmission;

a 32-bit source port IP address (source address);

a 32-bit destination port address (destination address);

options (options) (variable length): and recording the route.

The options field in the IP header described above may be used for extension.

RFC defines two types of extensions for the options field:

type 1: there is only one option-type;

type 2: option-type and option-length (length of option-data) and option-data;

the Option extensions of the current RFC definition are shown in table 1:

TABLE 1

Type (class)	Numerical value (number)	Length (length)	Description (description)
				0	0	-	Ending the list of options
0	1	-
				0	2	11
0	3	Var.
				0	9	Var.
0	7	Var.
				0	8	4
2	4	Var.

The expansion mode 1: the connection information and the packet information are transmitted in the data packet IP header.

The IP header Option field can be extended with type 2 (length of Option-data) and Option-data), supporting application data characteristics and QoS requirement indication, extension example:

option-type.Class＝0；

number 10// connection information and packet information extension;

option-type length var "(filled in actual length);

option-data extension mode a: extended by fixed field, the fixed field is defined as the following table 2:

TABLE 2

It should be understood that table 2 is exemplary only and should not be construed as limiting the scope of the present application in any way. For example, the unit information in table 3 may not indicate; also for example, the length information in table 3 may not indicate; also for example, one or more of the connection information and/or the packet information in table 3 may not be indicated. That is, specific embodiments of the connection information and the packet information may be various, which are not illustrated here.

option-data extension mode B: extended by Threshold Limit (TLV) or protocol buffer (protocol buffer), each field is defined similarly to table 3 above. After using TLV or protocol buffer format, the fields can be transmitted as needed and do not need to be carried all together (e.g., non-periodic connections may not carry periodic parameters). The TLV or protocol buffer encoding manner may refer to relevant provisions in the current protocol, which is not described herein again.

IP extension mode 2: packet information is transmitted at the IP header of a data packet, connection information is transmitted using virtual IP (dummy IP) packets, and each IP packet carries connection information and packet information, which results in excessive overhead in packet transmission.

Specifically, the dummy IP packet does not transfer user data, but only transfers connection information corresponding to the quintuple. In addition, dummy IP packets are sent periodically (e.g., once every 2 seconds) and immediately when connection information changes (e.g., video stream resolution adjustments cause connection information to change).

The packet information can be transmitted at the IP head of the data packet, and the connection information reduces the transmission overhead of the source QOS information by using a dummy IP packet transmission mode.

Example packet information extension:

the IP header Option field is extended with type 2 to support application data characteristics and QoS requirement indication.

option-type.Class＝0；

Number 10// packet information extension;

length var (filled in by actual length);

option-data extension mode a: extended by fixed field, the fixed field definition is as shown in table 3 below:

TABLE 3

It should be understood that table 3 is exemplary only and should not be construed as limiting the scope of the present application in any way. For example, 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 of the packet information in table 4 may not be indicated. That is, the specific embodiment of the packet information may be various, which is not illustrated here.

option-data extension mode B: extended in TLV or protocol buffer manner, and the definition of each field is similar to that in the above table 4. After using TLV or protocol buffer format, the fields can be transmitted as needed and do not need to be carried all together (e.g., non-periodic connections may not carry periodic parameters). The TLV or protocol buffer encoding manner may refer to relevant provisions in the current protocol, which is not described herein again.

Connection information extension example:

option-type.Class＝0；

Number 11// connection information extension;

option-type length var "(filled in actual length);

option-data extension mode A: extended by fixed field, the fixed field definition is shown in table 4 below:

TABLE 4

It should be understood that table 4 is exemplary only, and should not be construed as limiting the scope of the present application in any way. For example, the unit information in table 5 may not indicate; also for example, the length information in table 5 may not indicate; also for example, one or more of the connection information in table 5 may not be indicated. That is, the specific embodiment of the connection information may be various, which is not illustrated here.

option-data extension mode B: extending in TLV or protocol buffer mode, the definition of each field is similar to the above table. After using TLV or protocol buffer format, the fields can be transmitted as needed and do not need to be carried all together (e.g., non-periodic connections may not carry periodic parameters). The TLV or protocol buffer encoding manner may refer to relevant provisions in the current protocol, which is not described herein again.

Because the dummy IP packet does not transmit user data, the option-data can also be transmitted in the IP message data area; or

Because the dummy IP packet does not transmit user data, the IP packet data area can also be used to transmit other useful information, such as network status, etc.

It should be noted that, when the dummy IP packet is used to transmit the connection information, the connection information may be combined with the current dummy packet mechanism. For example, a dummy message mechanism in a QoS monitoring and performance measurement function (performance measurement function) mechanism defined in the extensible 5G standard supports transfer of connection information.

The second method comprises the following steps: the IPV6 expands.

The RFC definition of the IPV6 message header structure is shown in fig. 4, where fig. 4 is a schematic diagram of the IPV6 message header structure, and the schematic diagram includes:

version (version): the version field is used for indicating that the IP datagram uses IPv6 protocol encapsulation, and the version field occupies 4 bits;

traffic class (traffic class): the traffic classification field is used to identify the traffic class, or priority level, corresponding to IPv6, similar to the ToS (type of service) field in IPv 4;

flow label (flow label): when the flow label field is a field added in the IPv6 datagram, the field 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 distributed by the active node, and a communication flow can be uniquely identified by a flow label, source address and destination address triple mode without using a quintuple mode (source address, destination address, source port, destination port and transport layer protocol number) as IPv 4;

payload length (payload length): the payload length field is a length field that identifies the total length of the payload part (including all extension header parts) in the IPv6 datagram in bytes, i.e., the total length of the other parts except the basic header of IPv 6;

next header: the next header field is used to identify the next header type of the current header (or extension header);

hop limit (hop limit): the hop count is limited to be similar to the TTL field in the IPv4 message, and the number of times that the message can be effectively forwarded is specified. When the message passes through a router node, the hop value is reduced by 1, and when the field value is reduced to 0, the message 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 (destination IP address): the destination IP address field identifies the IPv6 address of the recipient node of the IPv6 message.

The IPV6 protocol is extended by a next header field mechanism. In an IPv6 packet without an extension header, the value of this field indicates the upper layer protocol. In the IPv6 packet with an extension header, this field indicates the type of the next extension field, and the defined protocol number of the extension header may refer to the description related to the current protocol, which is not described in detail in this application.

One of the unused extension types may be selected to represent the source QoS information, for example, a currently undefined protocol number 143 may be used to represent the source QoS information.

143: source QoS information.

Through the extension, the source QoS information can be carried in the IPV6 message header.

The IPV6 message header supports carrying source QoS information, and can be carried in two ways:

carrying mode 1: the IPV6 message carries user message data, the header source QoS extension field includes connection information and packet information, and in this carrying mode 1, the source QoS information interface definition is similar to the IP extension mode 1 and is not described again;

carrying mode 2: two types of unused extension can be selected to represent the source QoS packet information and connection information, respectively, for example, 143: packet information in source QoS information; 144: connection information in source QoS information.

Specifically, the IPV6 message carries user message data, and the header extension field protocol number is: 143, including only packet information in the source QoS information;

the IPV6 message does not carry user message data, and the header extension field protocol number is: 144 containing only connection information in the source QoS information.

In the carrying mode 2, the definition of the source QoS information interface is similar to that of the IP extension mode 2, and is not described again.

The third method comprises the following steps: and (5) RTP extension.

The RTP packet header structure is shown in fig. 5, and fig. 5 is a schematic diagram of the RTP packet header structure, which includes:

version (V) 2bits, designating the RTP version number;

1bit, if set, additional information is included at the end of the packet, the last byte of the additional information indicating the length of the additional information (including the byte itself). This field exists because some encryption mechanisms require fixed-length data blocks, or to transport multiple RTP packets in one underlying protocol data unit;

extension (X) 1bit, if set, an extension header exists after the fixed header;

functional source count (CC) 4bits, how many functional source (CSRC) tags are present behind the anchor header;

mark (marker, M):1bit, the function of the bit depends on the definition of the profile (profile) which can change the length of the bit, but keep the total length of the marker and payload type constant (a total of 8 bits);

7bits, marking the type of information carried by the RTP packet;

16bits, adding 1 to the sequence number after each RTP packet is sent, and the receiver can rearrange the sequence of the data packets according to the sequence number;

the time stamp (timestamp) is 32bits and reflects the sampling time of the first byte in the information packet carried by the RTP packet;

an identification data source (SSRC) identifier (identifier) of 32bits, each data stream should have a different SSRC during an RTP Session;

the active source list CSRC list:32bits identifies the contributing data sources.

The RTP protocol also allows extension by adding an extension header after the RTP fixed header, and by setting the X field in the RTP header to 1, an extension 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.

The format of the RTP packet carrying the trusted signature after being extended by the method 1 is similar to that of the IP extension method 1, and is not described herein again.

Expansion mode 2: the packet information is transmitted in the data packet RTP header and the connection information is delivered using the new RTP payload type.

The payload type in fig. 5 represents a packet type or a payload type of an RTP packet. Trusted signature information may be carried by extending a new RTP Packet Type (PT).

The current PT definition may refer to the related description in the current protocol, and is not described in detail in this embodiment. One of the unused PT values may be selected to represent RTP connection information, e.g., the PT value 35 is selected.

35：RTP Connect Information。

It should be understood that other unused PT values may be selected for identifying RTP connection information, which is not illustrated herein.

The extension mode 2 is similar to the IP extension mode 2, and the new RTP payload type is similar to a dummy IP packet, which is not described herein again.

The method is as follows: and expanding GTP-U.

GTP protocol format as shown in fig. 7, fig. 7 is a schematic diagram of GTP protocol format, which includes:

version number (version): to identify the version of the GTP protocol;

protocol Type (PT): to identify whether GTP (PT is 1) or GTP ' (PT is 0), GTP ' is defined in 3GPP TS 32.295, and the meaning of the header of GTP ' is not the same as the meaning of the header of GTP;

extension Header flag (Extension Header flag): it is used to show whether the Next Extension Header field makes sense. When this bit is 0, the Next Extension Header is either not present or present but not used. When this bit is 1, the Next Extension Header field is to be interpreted and used;

sequence number flag (Sequence number flag): to illustrate whether the Sequence number field makes sense. When this bit is 0, the Sequence number is either not present or present but 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): to indicate whether the N-PDU Number field is meaningful. When this bit is 0, the N-PDU Number is either not present or present but not used. When this bit is 1, the N-PDU Number field is to be interpreted and used.

Tunnel Endpoint Identifier (TEID): a tunnel endpoint is defined on an entity receiving a general packet radio service tunneling protocol user (GTP-U) or general packet radio service tunneling protocol control (GTP-C) protocol. The receiving party of GTP tunnel defines a TEID locally, and the TEID is used by the sending party.

Message Type (Message Type): the message types of GTP are defined, including GTP-C and GTP-U.

When the GTP protocol is used in a 5G network, the GTP-U protocol of the 3GPP specification defines the extension header field in the GTP protocol.

Downlink message (UPF to RAN) GTP-U format:

the QoS Monitoring Packet (QMP), the SNP identifier Sequence Number (Sequence Number presence), the PPP identifier paging policy (paging policy presence), the PPI identifier paging policy indicator (paging policy indicator), the RQI identifier reflection QoS indicator (reflective QoS indicator), the downlink transmission timestamp (DL transmitting timestamp) indicator, and the DL QFI Sequence qf Number (QoS monitoring packet, QMP) identify the downlink QoS Sequence Number.

Uplink message (RAN sends to UPF) GTP-U format:

the DL Delay index identifies a downlink Delay indication (downlink Delay indicator), an uplink Delay indication (UL Delay index), a DL Sending Time Stamp repeat indicates a downlink Sending Time Stamp repeat, a DL receiving Time Stamp indicates a downlink receiving Time Stamp, a UL Sending Time Stamp indicates an uplink receiving Time Stamp, a DL Delay Result indicates a downlink Delay Result, a UL Delay Result indicates an uplink Delay Result, and a UL Sequence Number identifies an uplink QFI serial Number.

In the embodiment of the application, the GTP-U protocol may be extended as follows to support carrying source QoS information.

Downlink message (UPF to RAN) GTP-U format:

uplink message (RAN to UPF) GTP-U format:

through the extension, the GTP-U message head can carry the source QoS information.

After the GTP-U message header supports carrying source QoS information, the method can be used in two ways:

mode 1:

the GTP-U message carries user message data, and the header source QoS information field comprises connection information and packet information. In this manner 1, the source QoS information interface definition is similar to the IP extension manner 1.

Mode 2:

GTP-U message carries user message data, and the header source QoS information field only contains packet information; or

The GTP-U message does not carry user message data, and the header source QoS information field only contains connection information.

In this mode 2, the source QoS information interface definition is similar to the IP extension mode 2, and is not described here again.

The fifth mode is as follows: new transport protocol extensions.

The scheme provided by the embodiment of the application further comprises defining a new transmission protocol:

the current protocol number 143- > 252 is unassigned. The protocol number 143 can be defined as the new transport protocol that supports carrying source QoS information.

The new transport protocol format defines:

source port: and the port of the application program which uses the new transmission protocol to transmit the message on the sending end computer.

Destination port: the port of the application on the receiving computer that receives the data using the new transport protocol.

Head length: new transport protocol message header length.

And (3) checking the value: this field occupies 16bits and can check whether the source QoS information and user data are damaged during transmission.

Source QoS information: source QoS content is filled in. The content length is "head length-8"

Apply for new transmission protocol numbers, like the protocol numbers of User Datagram Protocol (UDP), TCP at the IP layer.

In the new transmission protocol, a PayloadType is provided to indicate whether the transmission protocol is a data message or a connection indication message, packet information is sent along with the data message, and connection information is sent along with the connection indication message.

After the message transmission protocol extension supports carrying source QoS information, an application layer is required to indicate the source QoS information when sending data, and a general transmission protocol processing layer fills the source QoS information into an IP message which is finally sent to a transmission network.

The application layer uses an IP extension mode to carry the source QoS information.

In Linux Socket programming, the function of sending an IP (UDP/TCP) message is:

Ssize t send(int sockfd,const void*buff,size t nbytes,int flags)

the first parameter specifies the sending end socket descriptor, the second parameter specifies a buffer for storing data to be sent by the application program, the third parameter specifies the number of bytes of data to be actually sent, and the fourth parameter is normally set to 0.

To support the source application layer to indicate the source QoS information, a Send _ sql function may be added:

ssize_t send_sqos(int sockfd,const void*buff,size_t nbytes,int flags,const void*sqos)

the new sQoS information is a memory pointer of the storage position of the source QoS information, and the parameter structure is similar to the definition of the source QoS information in the protocol extension and is not repeated. The application layer may transmit data using the send _ sqos function and indicate source QoS information of the data. When the IP layer processes, the source QoS information is packed into the IP head extension field.

The application layer uses RTP extension mode to carry the source QoS information.

When real-time transfer programming is performed on the Linux platform, some RTP libraries of open source code, such as jlbrtp, are generally used.

The RTP data transmission function in the JRTPLIB is:

int SendPacket(void*data,int len)；

int SendPacketSQoS(void*data,int len，void*sqos)；

the new sQoS information is a memory pointer of the storage position of the source QoS information, and the parameter structure is similar to the definition of the source QoS information in the protocol extension and is not repeated. The application layer may send data using a sendpacketsoos function and indicate source QoS information of the data. When the RTP protocol layer is processed, the source QoS information is packed into the RTP header extension field.

Further, as a possible implementation: the first source QoS information included in the first packet #1 is used to indicate that the first packet #1 is mapped to a first QoS flow, the second source QoS information included in the second packet #1 is used to indicate that the second packet is mapped to a second QoS flow, and the first QoS flow and the second QoS flow belong to a QoS flow group.

It is understood that at least one packet in a connection comprising a plurality of packets is mapped to at least one QoS flow, respectively, wherein at least one QoS flow belongs to a QoS flow group, the first QoS flow is a QoS flow corresponding to the first packet #1 in the QoS flow group, and the second QoS flow is a QoS flow corresponding to the second packet #1 in the QoS flow group.

It should be understood that in the embodiment of the present application, the packets of one connection can be mapped to different QoS flows. In order to improve the control strength of the connection, the method can be used for performing relevant expansion on the current 5G QoS flow model.

The current 5G QoS flow model is shown in fig. 8 (a), which is a schematic diagram of a 5G QoS flow model in fig. 8.

In the embodiment of the present application, a QoS Flow Group (QFG) definition is added, and a model of the QoS flow after being extended is as shown in fig. 8 (b), where fig. 8 (b) is a schematic diagram of a QoS flow model provided in the embodiment of the present application. Specifically, the model of QoS flow shown in fig. 8 (b) is explained as follows:

1) one QFG can contain a plurality of QoS flows, and one QoS flow only belongs to one QFG;

2) different messages of one connection can only be mapped to different QoS flows in one QFG;

3) QFG can simultaneously contain non-GRB, GRB and DC-GRB type Qos flow;

4) the QFG supports the parameter of the maximum bandwidth (AMBR), can perform integral flow control on Qos flow of all non-GRB types in the QFG, and improves the control capability of connection.

Further, the QFG configuration described above includes one or more of:

QFG identification/index (QoS flow group identifier, QFGI): for identifying the QFG;

QFG contains QoS flow (involved QoS flow): for indicating which QoS flows the QFG contains;

at least one CQI: indicating the QFG to be mapped with which CQI can be mapped;

AMBR: indicating the maximum bandwidth of Qos flow for all non-GRB types in the QFG.

Illustratively, the QFG configuration may be issued through the control plane.

For example, after the 5GC control plane issues the QFG configuration to the UPF, the UPF may map to the QFG according to the QoS characteristics of the connection level, and map the packet to the specific QoS flow under the QFG according to the QoS characteristics of the packet level.

As another possible implementation: the first source QoS information included in the first packet #1 is used to indicate that the first packet #1 is mapped to a first 5QI, the second source QoS information included in the second packet #1 is used to indicate that the second packet is mapped to a second 5QI, and the first 5QI and the second 5QI belong to one QoS flow.

It is understood that at least one packet in a connection including a plurality of packets is mapped to at least one 5QI, respectively, wherein at least one 5QI belongs to one QoS flow, the first 5QI is a 5QI corresponding to the first packet #1 in the QoS flow, and the second 5QI is a 5QI corresponding to the second packet #1 in the QoS flow.

In the embodiment of the present application, another model of extended QoS flow is provided as shown in fig. 8 (c), and fig. 8 (c) is a schematic diagram of another QoS flow model provided in the embodiment of the present application. Specifically, the model of QoS flow shown in (c) in fig. 8 is explained as follows:

1) one QoS flow may contain multiple 5 QI;

2) one connected message can only be mapped to different 5 QIs in one QoS flow;

3) QoS flow can simultaneously contain non-GRB, DC-GRB type 5 QI;

4) the QoS flow supports AMBR parameters, and can perform overall flow control on all messages with 5QI being non-GRB in the QoS flow, so that the control capability of connection is improved.

In the extension mode shown in (c) of fig. 8, a 5QI field needs to be added in the extension header field of the transmission protocol. Mapping to QFI according to QoS characteristics at the connection level, further mapping to a specific 5QI under QFI according to QoS characteristics at the packet level.

QoS flow definition enhancements support multiple 5QI configuration examples:

in the extended manner shown in (c) in fig. 8, the QoS configuration of QoS flow includes one or more of the following:

common parameters: for each QoS flow, the QoS information that the QoS profile should include;

allocation and Retention Priority (ARP);

AMBR: 5QI maximum bandwidth for all non-GRB types under QoS flow.

5G QoS Gurop[n]。

Wherein, the 5G QoS Group is defined as:

5G QoS Identifier(5QI)；

reflective QoS Attribute (RQA), 5QI specific parameter of non-GRB type;

GFBR, 5QI specific parameters of GRB type;

MFBR, 5QI specific parameters of GRB type.

It should be understood that (b) in fig. 8 and (c) in fig. 8 are only examples of the QoS flow model applicable in the embodiment of the present application, and the scope of the embodiment of the present application is not limited in any way, and a plurality of different messages connected in the embodiment of the present application may have different QoS requirements, and are mapped to different QoS flows or 5QI based on other QoS flow models, which are not illustrated here.

As a possible implementation, the 5G control plane network elements AMF and SMF may send the packet filtering rules to the UE and the UPF.

In the embodiment of the application, in order to realize the accurate mapping from the source QOS driving network to the 5G QoS flow, the packet filters set can be added with the following parameters:

CQI and/or PQI.

When the packet filters set includes CQI and/or PQI, the packet can be accurately mapped to the corresponding QoS flow based on the source QoS information in the received IP packet.

It should be noted that the extension CQI and PQI in the packet filters set are optional. And if the CQI and/or PQI does not exist, comparing the QoS characteristics corresponding to the CQI and the PQI with the QoS characteristics of 5QI in the QoS flow, and selecting the best matching QoS characteristics of the 5 QI.

Further, after the data network generates the first packet #1, the first packet #1 is sent to a core network device (e.g., UPF) through an N6 interface, and the method flow shown in fig. 2(a) further includes:

s230, the data network sends the first packet #1 to the core network device.

In the embodiment of the present application, a method for transmitting a packet between network elements is not limited, and reference may be made to a current packet transmission rule, which is not described herein again.

The core network device is hereinafter described as an example UPF.

Further, after receiving the first packet #1, 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:

s240, the UPF maps the first packet #1 to the first QoS flow # 1.

According to a possible implementation mode, packet information and connection information included in source QoS information are carried in a first message #1, and a UPF maps an IP message to a first QoS flow #1 with the closest QoS characteristic according to the source QoS information in the first message # 1;

in another possible implementation manner, packet information included in the source QoS information is carried in the first message #1, and connection information included in the source QoS information is carried in the dummy IP message, so that the UPF maps the IP message to the first QoS flow #1 with the closest QoS characteristic according to the source QoS information in the first message #1 and the dummy IP message;

in another possible implementation manner, 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, so that the UPF maps the IP packet to the first QoS flow #1 with the closest QoS characteristic according to the first packet #1 and the source QoS information transmitted by the control plane.

The UPF maps the IP message to the first QoS flow #1 in any mode of:

if the source QoS information uses the CQI to identify the QoS requirement and the packet filters set received by the UPF contains the CQI parameter, mapping according to the CQI; if the QoS requirement is identified by using PQI in the source QoS information and the packet filters set received by the UPF contains PQI parameters, mapping is carried out according to the PQI; or

If the source QoS information uses the CQI to identify the QoS requirement and the packet filters set received by the UPF does not contain the CQI, comparing the QoS characteristic corresponding to the CQI with the QoS characteristic of 5QI in each QoS flow, and selecting the best matching QoS; if the QoS requirement is identified by using PQI in the source QoS information and the packet filters set received by the UPF does not contain PQI, comparing the QoS characteristics corresponding to the PQI with the QoS characteristics of 5QI in each QoS flow, and selecting the best matching QoS; or

If the source QoS information directly carries specific QoS characteristic information (for example, carries connection QoS characteristic information and/or packet QoS characteristic information), comparing the carried QoS characteristic information with the QoS characteristics of 5QI in each QoS flow, and selecting the best matching QoS; or

If the source QoS information does not carry packet-level QoS characteristics (e.g., PQI and/or packet QoS characteristic information) but does carry connection-level QoS characteristics (e.g., CQI and/or connection QoS characteristic information), the connection-level QoS characteristics are used as the QoS characteristics of the packet to identify the QoS requirements of the packet, and mapping is performed according to the connection-level QoS characteristics.

Further, after the mapping is completed, the UPF performs the targeted guarantee and forwarding processing according to the QoS requirement of the QoS flow matched with the IP message. The method flow shown in fig. 2(a) further includes:

s250, the UPF determines the third packet # 1.

Specifically, the UPF processes the first packet #1 based on the first QoS flow #1 to obtain the third packet # 1. It can be understood that the third packet #1 includes the information to be transmitted in the first packet #1, but the packet format is converted from the packet format of the first packet #1 satisfying the N6 interface transmission to the packet format satisfying the N3 interface transmission.

For example, the UPF reserves internal forwarding resources (buffer queues, scheduling time slices, etc.) according to information such as average rate, frequency, peak size, etc. in the connection information, and improves the QoS achievement rate.

For example, in the video stream transmitted by the DN application, the PQI of the I frame message is high-level QoS (packet loss rate is 0.01%), and the PQI of the P frame message is medium-level QoS (packet loss rate is 1%). And the UPF puts the I frame data into a high priority forwarding queue and puts the P frame data into a medium priority forwarding queue. And when the system or the next hop outlet is congested, the I frame data message is preferentially sent.

For another example, according to the burst data indication, the UPF may calculate that the instantaneous traffic peak value caused by simply forwarding the burst data and the current concurrent connection data exceeds the processing and buffering capability of the back-end transmission device (e.g., RAN), and thus a packet loss occurs. The UPF can carry out peak staggering shaping according to the source QoS information in the message, and preferentially sends the message with high delay requirement and then sends the message with low delay requirement by using a uniform speed and complete data segment transmission mode on the premise of ensuring the total achievement rate of the QoS, thereby reducing the impact on the downstream.

Further, if the UPF needs to send the IP packet to the access network device, the method flow shown in fig. 2(a) further includes:

s260, the UPF sends the third packet #1 to the access network device.

Specifically, the UPF encapsulates the first packet #1 and the source QoS information into a GTP-U protocol format, and forwards the GTP-U protocol format to the N3 port, including:

the UPF populates the QFI of the first QoS flow #1 to the GTP-U protocol header.

It should be noted that, how to fill the QFI in the GTP-U protocol header may refer to the related description in the current protocol, and details are not described here.

In addition, the UPF copies the packet information and the connection information in the first packet #1 to the GTP-U protocol header extension field, and the introduction is introduced in the GTP protocol extension, which is not described herein again.

Exemplarily, if the connection information is transmitted by using a dummy IP messaging mode, the dummy IP messaging on the N6 port is converted into a dummy IP messaging on the N3 port based on the GTP-U protocol.

Further, 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, and specifically, it can be understood that the fourth packet #1 includes information that needs to be transmitted in the third packet #1, but a packet format of the third packet #1 that meets the interface transmission of N3 is converted into a packet format that meets the transmission over the air interface.

The method flow shown in fig. 2(a) further includes:

s270, the RAN determines the fourth packet # 1.

Specifically, after receiving the N3 port third packet #1, the RAN side obtains connection information and/or packet information of the third packet #1 from the GTP extended header field, performs targeted security and forwarding processing (such as complete data segment scheduling) in combination with the QoS flow to which the packet belongs, and sends the processed fourth packet #1 to the UE through the air interface.

The method flow shown in fig. 2(a) further includes:

s280, the RAN sends a fourth packet #1 to the UE.

It should be noted that, in the above steps S230 to S280, the transmission flow of the downlink message is described by taking the first message #1 for downlink transmission as an example, and other messages (for example, the second message #1) in the downlink transmission connection are similar to the first message #1 for downlink transmission, and are not described again here.

The flow shown in fig. 2(a) is a schematic flow chart of the method for transmitting a packet provided in the embodiment of the present application in a downlink scenario.

In an uplink packet transmission scenario, as shown in fig. 2(b), fig. 2(b) is a schematic flowchart of another method for transmitting a packet according to an embodiment of the present application.

The method for transmitting the message at least comprises the following steps.

S211, the UE generates a first packet # 2.

Specifically, the application on the UE generates a 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 DN, and reference is made to the related description in S210, which is not repeated here.

It should be noted that the first packet #2 may be any one of a plurality of packets generated by the UE, and the five-tuple information of the plurality of packets is the same, which may be understood that the plurality of packets belong to one connection. Each message of the plurality of messages comprises a source QoS parameter, source QoS information included in each message is used for QoS guarantee of the corresponding message, and the source QoS information included in the plurality of messages is different.

For example, to facilitate the distinction, in the embodiment of the present application, "# 2" is added to the packet in the uplink packet transmission flow, and a "# 1" identifier is added to the packet in the downlink packet transmission flow for distinction, it should be understood that such a distinction identifier does not constitute any limitation to the protection scope of the present application.

Further, the UE may further generate a second packet #2 in the multiple packets in the connection, and the method flow shown in (b) in fig. 2 further includes:

s221, 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 DN, and reference is made to the related description in S220, which is not repeated herein.

Further, after generating the packet, the UE sends the packet to the UE bottom layer, and after receiving the first packet #2, the UE bottom layer maps the first packet #2 to the first QoS flow # 2. The method flow shown in fig. 2(b) further includes:

s231, the UE maps the first packet #2 to the first QoS flow # 2.

According to a possible implementation mode, packet information and connection information included in source QoS information are carried in a first message #2, and according to the source QoS information in the first message #2, UE maps an IP message to a first QoS tow #2 with the closest QoS characteristic;

in another possible implementation manner, packet information included in the source QoS information is carried in a first message #2, connection information included in the source QoS information is carried in a dummy IP message, and the UE maps the IP message to a first QoS flow #2 with the closest QoS characteristic according to the source QoS information in the first message #2 and the dummy IP message;

in another possible implementation manner, packet information included in the source QoS information is carried in the first packet #2, connection information included in the source QoS information is transmitted via the control plane, and the UE maps the IP packet to the first QoS flow #2 with the closest QoS characteristic according to the first packet #2 and the source QoS information transmitted by the control plane.

The UE mapping the first packet #2 to the first QoS flow #2 includes any one of the following manners:

if the source QOS information uses CQI to identify the QoS requirement and the packet filters set received by the UE contains CQI, mapping is carried out according to the CQI; if the QoS requirement is identified by using PQI in the source QoS information and the packet filters set received by the UE contains PQI parameters, mapping is carried out according to the PQI; or

If the source QOS information uses the CQI to identify the QoS requirement and the packet filters set received by the UE does not contain the CQI, comparing the QoS characteristic corresponding to the CQI with the QoS characteristic of 5QI in each QoS flow, and selecting the best matched QoS; if the source QOS information uses PQI to identify the QoS requirement and the packet filters set received by the UE does not contain PQI, comparing the QoS characteristics corresponding to the PQI with the QoS characteristics of 5QI in each QoS flow and selecting the best matching QoS; or

If the source QOS information directly carries specific QoS characteristic information (for example, carrying connection QoS characteristic information and/or packet QoS characteristic information), the carried QoS characteristic information is compared with the QoS characteristics of 5QI in each QoS flow, and the best matching is selected; or

If the source QoS information does not carry the PQI or the packet QoS characteristic information but carries the CQI or the connection QoS characteristic information, the QoS characteristic of the connection level is used as the QoS requirement of the message QoS characteristic identification message, and mapping is carried out according to the QoS characteristic of the connection level.

Further, after the mapping is completed, the UE performs the targeted guarantee and forwarding processing according to the QoS requirement of the first QoS flow #2 matched with the IP packet. Sending a first message #2 to the RAN, the method flow shown in fig. 2(b) further includes:

s241, the UE sends the first packet #2 to the RAN.

And the UE bottom layer encapsulates the user plane IP message by using an air interface transmission protocol, and fills the QFI of the first QoS flow #2 matched with the message into the head of an air interface data packet.

Further, the UE bottom layer performs targeted security and forwarding processing (such as complete data segment scheduling) according to the connection information and packet information in the user plane packet and in combination with the QoS requirement of the first QoS flow #2 to which the packet belongs, and maps the first packet #2 to DRBs of different bearer standards and sends the DRBs to the RAN.

For example, in a video stream transmitted by the UE, the PQI of the I frame packet is a high-level QoS (packet loss rate 0.01%), and the PQI of the P frame packet is a medium-level QoS (packet loss rate 1%). The UE bottom layer matches the data message of the I frame to a high-level DRB bearer (such as retransmission support and redundancy support), and matches the data message of the P frame to a medium-level DRB bearer (no retransmission and no redundancy);

for example, the UE bottom layer receives all the messages of a frame of video according to the data integrity information in the packet information, and then sends the messages to the RAN through the air interface once again, so as to reduce the overall transmission delay of the data segment and improve the utilization rate of the air interface;

for another example, the connection information indicates that there is 3M byte data of an emergency after 10ms that needs to be sent, and the UE bottom layer negotiates with the base station to allocate an air interface transmission resource after 10ms according to the indication. After the UE bottom layer receives the emergency data, the pre-applied air interface resources can be used for transmission immediately, so that the transmission delay is reduced, and the utilization efficiency of the air interface resources is improved.

Further, 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, and specifically, it can be understood that the third packet #2 includes information that needs to be transmitted in the first packet #2, but the packet format is converted from the packet format of the first packet #2 that meets air interface transmission to the packet format that meets N3 interface transmission.

The method flow shown in fig. 2(b) further includes:

s251, the RAN determines the third packet # 2.

After receiving the message sent by the UE, the RAN encapsulates the user plane IP message by using a GTP-U protocol, fills the QFI (quad flat interface) of the first QoS flow #2 which the message belongs to into a head field of the GTU-U protocol, which is analyzed from an air interface data packet header, and then sends the third message #2 to the UPF through an N3 interface.

The method flow shown in fig. 2(b) further includes:

s261, the RAN sends the third packet #2 to the UPF.

Further, 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, and specifically, it can be understood that the fourth packet #2 includes information that needs to be transmitted in the third packet #2, but the packet format is converted from the packet format of the third packet #2 that meets the transmission of the N6 interface to the packet format that meets the transmission of the N6 interface.

The method flow shown in fig. 2(b) further includes:

s271, the UPF determines the fourth packet # 2.

After receiving the third message #2 with the N3 port, the UPF side obtains the connection information and packet information of the data message from the user plane IP message extension field, performs targeted guarantee and forwarding processing (such as complete data segment scheduling) by combining the first QoS flow #2 to which the message belongs to determine the fourth message #2, and sends the fourth message #2 to the Internet through the N6 interface. The method flow shown in fig. 2(b) further includes:

s281, the UPF sends the fourth packet #2 to the data network.

It should be noted that, in the above steps S231 to S281, the transmission flow of the uplink packet is described by taking the first packet #2 for downlink transmission as an example, and other packets (for example, the second packet #2) in the uplink transmission connection are similar to the first packet #2 for uplink transmission, which is not described herein again.

It should be understood that, in the methods shown in fig. 2(a) and fig. 2(b), when the message generating end generates the message, the message carries the source QoS information, and the present application provides a possible implementation manner, when the message generating device generates the message, the transmission node may identify a part of the data features and map the data features as the source QoS information without carrying the source QoS information.

Specifically, when the sending end does not carry the source QoS information, a node (message receiving device) on the transmission path may identify part of the data characteristics by itself through technologies such as traffic analysis, message parsing, or intelligent sensing, and map the data characteristics into the source QoS information, fill the source QoS information in a message, and send the message to the back-end device, thereby implementing QoS guarantee.

For example, the RAN or the UPF may, according to traffic analysis, sense the period information of the I frame and the P frame in the video stream, map the period information of the I frame and the P frame into source QoS information, fill the source QoS information in a message, and send the source QoS information to the backend device.

Optionally, active data feature sensing is only required to be implemented on key nodes on a transmission path, and all nodes are not required to be implemented. For example, UPF implements the active data feature awareness described above.

The present application also provides a reflective QoS mechanism. As shown in fig. 9, fig. 9 is a schematic flow chart of a reflection QoS mechanism provided in an embodiment of the present application.

The reflective QoS mechanism includes at least the following partial steps.

S910, the core network device sends the QoS characteristics of the connection level and/or the QoS characteristics of the packet level to the access network device.

Illustratively, when a core network device (e.g., UPF) sends a user plane IP packet to an access network device using a GTP-U protocol at an N3 interface, CQI and/or PQI information of the packet is carried in a GTP-U header extension field.

It should be understood that the core network device may also send the QoS characteristics at the connection level and/or the QoS characteristics at the packet level to the access network device by other means, which are not illustrated here.

In addition, the QoS characteristics of the connection level may be connection QoS characteristic information, and the QoS characteristics of the packet level may be packet QoS characteristic information.

Further, the access network device needs to send the received QoS characteristics of the connection level and/or the QoS characteristics of the packet level to the user equipment, and the method flow shown in fig. 9 further includes:

s920, the access network equipment sends QoS characteristics of connection level and/or QoS characteristics of packet level to the user equipment.

Illustratively, the access network device encapsulates the user plane IP packet using an air interface protocol stack and sends the user plane IP packet to the user equipment. Filling an RDI field in an SDAP protocol head of an air interface protocol stack as 1, and indicating the user equipment to trigger QoS reflection processing.

Optionally, a QFI field in an SDAP protocol header of the air interface protocol stack is filled in as a CQI parsed from the GTP-U protocol.

Optionally, a PQI extension field of an SDAP protocol header of the air interface protocol stack is filled in as a PQI parsed from the GTP-U protocol.

SDAP protocol header extension mode 1: a one byte extension field is added directly.

Bit7	Bit6	Bit0-5
			RDI	RQI	QFI
Retention	Retention	PQI

SDAP protocol header extension mode 2: to ensure compatibility, an optional field of 2 bytes is added, and when QFIs are all 0 or all 1, an extension field is indicated. Filling in a real QFI in an extension field of a first byte; the extension field of the second byte fills in the PQI.

Bit7	Bit6	Bit0-5
			RDI	RQI	QFI
Retention	Retention	Real-QFI
			Retention	Retention	PQI

It should be understood that the access network device may also send the connection-level QoS features and/or the packet-level QoS features to the user equipment in other manners, which are not illustrated here.

The user equipment receiving the connection level QoS characteristics and/or the packet level QoS characteristics may record the connection level QoS characteristics and/or the packet level QoS characteristics. The method flow shown in fig. 9 further includes:

s930, the user equipment records the QoS characteristics of the connection level and/or the QoS characteristics of the packet level.

For example, after receiving a packet, when finding that the RDI indication is 1, the user equipment records a mapping relationship between a quintuple, CQI, QFI information, PQI, and DRB as a QoS rule learned by the reflective QoS mechanism (currently, the reflective QoS mechanism only records a mapping relationship between a quintuple, QFI information, and DRB of the packet).

Specifically, the user equipment may perform message sending according to the learned QoS rule, and the method flow shown in fig. 9 further includes:

s940, the user equipment sends the message to the access network equipment.

For example, when the user equipment sends an uplink message, the user equipment may perform matching by using the QoS rule of the PQI information learned by the reflected QoS mechanism, and match the message to an appropriate QoS flow or DRB for sending.

For example, the PQI in the QoS characteristics of the uplink message to be sent by the user equipment can find the corresponding PQI #1 in the PQI recorded by the UE, and the user equipment can send the uplink message to be sent on the QoS flow and DRB corresponding to the PQI #1, where the PQI #1 may be the same PQI as the PQI in the QoS characteristics of the uplink message to be sent, or the closest PQI.

The application also provides a QoS flow strategy fine adjustment control scheme, which can dynamically adjust resources corresponding to the QoS flow, and is specifically realized by enhancing the QoS configuration of the QoS flow.

One possible implementation manner, in this embodiment, the QoS configuration of the QoS flow includes one or more of the following:

5QI；

allocation and Retention Priority (ARP);

reflecting QoS attributes, 5QI specific parameters of non-GRB type;

the maximum guaranteed bandwidth MGFBR;

MFBR, 5QI specific parameters of GRB type.

Wherein, MGFBR represents the maximum guaranteed bandwidth in the micro control mode, that is, 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 in the micro control mode. When the UPF and/or RAN receives a message in a connection on the QoS flow:

and obtaining source QoS information from the message and/or GTP-U extension header domain, and obtaining the average speed of the connection.

In another possible implementation manner, the QoS configuration of the QoS flow in this embodiment includes one or more of the following:

5QI；

allocation and Retention Priority (ARP);

reflecting QoS attributes, 5QI specific parameters of non-GRB type;

GFBR, 5QI specific parameters of GRB type;

maximum guaranteed bandwidth (maximum guaranteed flow rate MGFBR, MGFBR);

MFBR, 5QI specific parameters of GRB type.

The MGFBR indicates the maximum guaranteed bandwidth in the micro control mode, that is, the actual guaranteed bandwidth of the resources reserved for the QoS flow may dynamically change between the GFBR and the MGFBR in the micro control mode. The GFBR is used for adjusting resources reserved for 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. When the UPF and/or RAN receives a message in a connection on the QoS flow:

For example, if the sum of the connection average rate and the current GFBR actual rate is not greater than the MGFBR, reserving enough bandwidth resources for connection, and refreshing the current GFBR actual rate to be the sum of the new connection average rate and the current GFBR actual rate;

also for example, the processing strategy is similar when the UPF and/or RAN detect that an existing connection on the QoS flow has failed (disconnected), and the average rate of the connection changes.

Optionally, the UPF and/or the RAN may add a forwarding node identifier, a forwarding interface bandwidth reservation success flag, and information such as a current reserved bandwidth of the forwarding node to the source QoS information of the packet or the Dummy IP packet, and simultaneously transmit and receive information such as two ends and other transmission nodes in the network.

The present application further provides another QoS flow policy fine adjustment control scheme, which may dynamically indicate whether resources corresponding to the QoS flow are reserved, and specifically, is implemented by enhancing QoS configuration of the QoS flow.

The QoS configuration of the QoS flow in this embodiment includes one or more of:

5QI；

allocation and Retention Priority (ARP);

indication information;

reflecting QoS attributes, 5QI specific parameters of non-GRB type;

GFBR, 5QI specific parameters of GRB type;

maximum guaranteed bandwidth (maximum guaranteed flow rate MGFBR, MGFBR);

MFBR, 5QI specific parameters of GRB type.

The indication information is used for indicating whether resources corresponding to the QoS flow are reserved or not. The indication information may be Dynamic Creation Indication (DCI), where the DCI indicates whether the UFP and/or the RAN reserves a resource corresponding to the QoS flow (or whether to create an instance corresponding to the QoS flow by default) after receiving the configuration of the QoS flow. The default value is TRUE (TRUE), dynamically created QoS flow in micro control mode is supported, DCI is set to FALSE (FALSE).

In the embodiments of the present application, the indication information is referred to as DCI by way of example only, and the scope of protection of the present application is not limited at all, and may be referred to by other names.

Specifically, after receiving the QoS configuration issued by the 5G control plane, the UPF and/or the RAN actively creates an instance for the QoS flow indicated as True by the DCI; no instance is created for QoS flow indicated as FALSE to DCI.

When UPF and/or RAN receives IP message, firstly determining whether the IP message can be mapped to the existing non-default QoS flow example; if yes, processing according to the existing flow; if not, judging whether the IP message can be mapped to a QoS flow which is not instantiated in the QoS configuration and DCI is FALSE, if so, instantiating the QoS flow, and forwarding the message by using the QoS flow; if not, forwarding the message by using default QoS flow.

In addition, in the current transmission network, each transmission node or forwarding device does not take charge of the end-to-end QoS, and only tries to make targeted guarantee when the node processes and forwards according to the message QoS indication. When some nodes in the transmission path can not meet the QoS requirement, only the fault tolerance mechanism at the transmitting and receiving ends can be used for solving the problem.

The application provides a guarantee mechanism, a transmission node can combine an end-to-end transmission network damage model and a network state prediction technology, and an end-to-end QoS achievement rate is improved through an active guarantee mechanism:

for example, when a certain transmission node senses that a back-end network has periodic occasional packet loss due to interference, the transmission node actively adopts mechanisms such as repeated transmission of messages in an interference period, retransmission of the interference period staggered and the like to the messages which cannot achieve the end-to-end delay target due to interference, so that the transmission delay is reduced (compared with a retransmission confirming mechanism at the receiving and transmitting ends), and the end-to-end QoS achievement rate is improved;

for example, when a certain transmission node senses that the packet loss rate of the back-end network cannot meet the packet error rate target of the end-to-end network, an FEC redundancy coding mode is actively adopted to improve the packet loss resistance of data, and the end-to-end QoS achievement rate is improved.

Optionally, the above guarantee mechanism only needs to be implemented on the key transmission node on the transmission path, and all transmission nodes are not required to be implemented. For example, UPF implements the safeguard mechanism described above.

In the method embodiment, the sequence number of each process does not mean the execution sequence, and the execution sequence of each process should be determined by the function and the internal logic of the process, and should not limit the implementation process of the embodiment of the present application. And possibly not all operations in the above method embodiments.

It should be understood that the user equipment and/or the network equipment in the above method embodiments may perform some or all of the steps in the embodiments, and these steps or operations are merely examples, and the embodiments of the present application may also include performing other operations or variations of various operations.

It is to be understood that, in the above method embodiments, the method implemented by the user equipment may also be implemented by a component (e.g., a chip or a circuit, etc.) available to the user equipment, and the method implemented by the network equipment may also be implemented by a component available to the network equipment.

It is also to be understood that the terminology and/or descriptions herein may be consistent between different embodiments and may be mutually inconsistent, if not expressly stated or logically conflicting, and that features of different embodiments may be combined to form new embodiments based on their inherent logical relationships.

The method for transmitting a message in the embodiment of the present application is described in detail above with reference to (a) in fig. 2 and (b) in fig. 2, and the apparatus for transmitting a message provided in the embodiment of the present application is described in detail below with reference to fig. 10 to fig. 13.

Referring to fig. 10, fig. 10 is a schematic diagram of an apparatus 1000 for transmitting a message according to the present application. As shown in fig. 10, the apparatus 1000 includes a processing unit 1010, a receiving unit 1020, and a transmitting unit 1030.

The processing unit 1010 is configured to generate multiple packets, where five tuple information of the multiple packets is the same, each packet in the multiple packets includes source QoS information, the source QoS information included in each packet is used to guarantee QoS for the corresponding packet, and the source QoS information included in the multiple packets is different.

A sending unit 1030, configured to send the multiple messages.

The apparatus 1000 corresponds to a user equipment or a data network in the method embodiment, and is configured to generate a packet. The apparatus 1000 may be a user equipment or a data network in the method embodiment, or a chip or a functional module inside the user equipment or the data network in the method embodiment. The corresponding units of the apparatus 1000 are adapted to perform the corresponding steps performed by the user equipment or the data network in the method embodiments shown in fig. 2(a) and 2(b) and fig. 9.

The processing unit 1010 in the apparatus 1000 is configured to execute the steps related to the 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 the user equipment or data network reception in the method embodiment. A sending unit 1030 in the apparatus 1000, configured to perform the step of user equipment or data network sending.

The receiving unit 1020 and the transmitting unit may constitute a transceiving unit, and have both receiving and transmitting functions. Wherein the processing unit 1010 may be at least one processor. The transmitting unit may be a transmitter or an interface circuit, and the receiving unit 1020 may be a receiver or an interface circuit. The receiver and transmitter may be integrated together to form a transceiver or interface circuit.

Optionally, the apparatus 1000 may further include a storage unit, which is used for storing data and/or signaling, and the processing unit 1010, the sending unit, and the receiving unit 1020 may interact with or be coupled to the storage unit, for example, read or call the data and/or signaling in the storage unit, so as to enable the method of the above-described embodiment to be performed.

The above units may exist independently, or may be integrated wholly or partially.

Referring to fig. 11, fig. 11 is a schematic structural diagram of a message generating device 1100 applicable to the embodiment of the present application, and may be used to implement a function of a data network in the downlink message transmission scenario or may also be used to implement a function of a user equipment in the uplink message transmission scenario.

The message generating device 1100 includes a processor 1101, a memory 1102 and a transceiver 1103, where the memory 1102 stores instructions or programs, and the processor 1102 and the transceiver 1103 are configured to execute or call the instructions or programs stored in the memory 1102, so that the message generating device 1100 implements functions of the message generating device in the above-described method for transmitting a message. When the instructions or programs stored in the memory 1102 are executed, the transceiver 1103 is configured to perform the operations performed by the transmitting unit 1030 and the receiving unit 1020 in the embodiment shown in fig. 10, and the processor 1102 is configured to perform the operations performed by the processing unit 1010 in the embodiment shown in fig. 10.

Those skilled in the art will appreciate that fig. 11 shows only one memory and processor for ease of illustration. 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, and the like, which is not limited in this application.

Referring to fig. 12, fig. 12 is a schematic diagram of another apparatus 1200 for transmitting a message according to the present application. As shown in fig. 12, the apparatus 1200 includes a receiving unit 1210, a transmitting unit 1220, and a processing unit 1230.

A receiving unit 1210, configured to receive multiple packets, where five tuple information of the multiple packets are the same, each packet in the multiple packets includes source QoS information, and the source QoS information included in each packet is used to perform QoS guarantee on a QoS packet corresponding to the packet, and source QoS information included in the multiple packets are different.

A processing unit 1230, configured to process the multiple packets based on source QoS information included in the multiple packets.

The apparatus 1200 corresponds to a core network device (e.g., UPF) or an access network device in the method embodiment, and the apparatus 1200 may be a UPF or an access network device in the method embodiment, or a chip or a functional module inside the UPF or the access network device in the method embodiment. The corresponding elements of the apparatus 1200 are used to perform the corresponding steps performed by the UPF or access network device in the method embodiments shown in fig. 2(a) and 2(b) and fig. 9.

A sending unit 1220 in the apparatus 1200 executes the step of sending by the UPF or the access network device in the method embodiment, a receiving unit 1210 in the apparatus 1200 is configured to execute the step of receiving by the UPF or the access network device, and the apparatus 1200 may further include a processing unit 1230 configured to execute the step corresponding to the processing related to the inside of the UPF or the access network device.

Optionally, the apparatus 1200 may further include a storage unit for storing data and/or signaling, and the processing unit 1230, the obtaining unit 1220, and the receiving unit 1210 may interact with or be coupled to the storage unit, for example, read or call the data and/or signaling in the storage unit, so as to enable the method of the foregoing embodiment to be performed.

The above units may exist independently, or may be wholly or partially integrated.

Referring to fig. 13, fig. 13 is a schematic structural diagram of a message receiving device 1300 applicable to the embodiment of the present application, and may be used to implement functions of a core network device, an access network device, and a user equipment in the downlink message transmission scenario, or may also be used to implement functions of a core network device, an access network device, and a data network in the uplink message transmission scenario.

The message receiving device 1300 includes a processor 1301, a memory 1302, and a transceiver 1303, where the memory 1302 stores instructions or programs, and the processor 1302 and the transceiver 1303 are configured to execute or call the instructions or programs stored in the memory 1302, so that the message receiving device 1300 implements the functions of the message receiving device in the above message transmission method. When the instructions or programs stored in the memory 1302 are executed, the transceiver 1303 is configured to perform the operations performed by the sending unit 1220 and the receiving unit 1210 in the embodiment shown in fig. 12, and the processor 1302 is configured to perform the operations performed by the processing unit 1230 in the embodiment shown in fig. 12.

The 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 having stored therein instructions which, when executed on a computer, cause the computer to perform the steps performed by the user equipment in the methods as shown in fig. 2(a) and 2(b) and fig. 9.

The present application also provides a computer-readable storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the various steps performed by the access network device in the methods described above as shown in fig. 2(a) and 2(b), and fig. 9.

The present application also provides a computer-readable storage medium, which stores instructions that, when executed on a computer, cause the computer to perform the steps performed by the core network device in the methods shown in fig. 2(a) and fig. 2(b) and fig. 9.

The present application also provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the steps performed by the user equipment in the method as shown in fig. 2(a) and 2(b) and fig. 9.

The present application also provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the steps performed by the access network device in the method as shown in fig. 2(a) and 2(b) and fig. 9.

The present application also provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the steps performed by the core network device in the methods as shown in fig. 2(a) and 2(b) and fig. 9.

The application also provides a chip comprising a processor. The processor is configured to read and execute the computer program stored in the memory to perform corresponding operations and/or processes performed by the user equipment in the method for transmitting a message provided by the present application. Optionally, the chip further comprises a memory, the memory is connected with the processor through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory. Further optionally, the chip further comprises a communication interface, and the processor is connected to the communication interface. The communication interface is used for receiving the 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, interface circuit, output circuit, input circuit, pin or related circuit on the chip, etc. The processor may also be embodied as a processing circuit or a logic circuit.

The application also provides a chip comprising a processor. The processor is configured to read and execute the computer program stored in the memory, so as to perform corresponding operations and/or procedures executed by the access network device in the method for transmitting a message provided by the present application. Optionally, the chip further comprises a memory, the memory is connected with the processor through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory. Further optionally, the chip further comprises a communication interface, and the processor is connected to the communication interface. The communication interface is used for receiving the 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, interface circuit, output circuit, input circuit, pin or related circuit on the chip, etc. The processor may also be embodied as a processing circuit or a logic circuit.

The application also provides a chip comprising a processor. The processor is configured to read and execute the computer program stored in the memory to perform corresponding operations and/or processes executed by the core network device in the method for transmitting a packet provided by the present application. Optionally, the chip further comprises a memory, the memory is connected with the processor through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory. Further optionally, the chip further comprises a communication interface, and the processor is connected to the communication interface. The communication interface is used for receiving the 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, interface circuit, output circuit, input circuit, pin or related circuit on the chip, etc. The processor may also be embodied as a processing circuit or a logic circuit.

The chip can be replaced by a chip system, which is not described herein again.

The terms "comprises," "comprising," and "having," and any variations thereof, in this application are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual conditions to achieve the purpose of the scheme of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

In addition, the term "and/or" in the present application is only one kind of association relationship describing the associated object, and means that three kinds of relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship; the term "at least one" in this application may mean "one" and "two or more", for example, at least one of A, B and C, may mean: a exists alone, B exists alone, C exists alone, A and B exist together, A and C exist together, C and B exist together, A and B exist together, and A, B and C exist together, which are seven cases.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for transmitting a message, comprising:

generating a plurality of messages, wherein five-tuple information of the plurality of messages is the same, each message in the plurality of messages comprises source QoS information, the source QoS information of each message is used for QoS guarantee of the corresponding message, and the source QoS information of the plurality of messages is different;

and sending the plurality of messages.

2. The method of claim 1, wherein the plurality of packets belong to a same connection, and wherein the plurality of packets include source QoS information that is different comprises:

the first source QoS information included in a first packet in the connection and the second source QoS information included in a second packet in the connection are different,

wherein the first packet and the second packet are any two packets of the plurality of packets.

3. The method of claim 2, wherein the first source QoS information comprises a first QoS characteristic indicating a QoS requirement for the first packet and a first data characteristic representing a transmission characteristic of the first packet,

the second source QoS information includes a second QoS characteristic indicating a QoS requirement of the second packet and a second data characteristic indicating a transmission characteristic of the second packet.

4. The method of claim 3, wherein 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 being different comprises:

the first data characteristic and the second data characteristic are different, and/or the first QoS characteristic and the second QoS characteristic are different.

5. The method according to claim 3 or 4, wherein the first data characteristic comprises a connection-level data characteristic and/or a packet-level data characteristic,

wherein the connection-level data characteristics represent transmission characteristics of a plurality of packets included in the connection, the packet-level data characteristics represent transmission characteristics of the first packet,

the first QoS characteristics include connection-level QoS characteristics and/or packet-level QoS characteristics,

wherein the connection-level QoS characteristics are used to indicate QoS requirements of a plurality of packets included in the connection, and the packet-level QoS characteristics are used to indicate QoS requirements of the first packet.

6. The method of claim 5, wherein the data characteristics of the connectivity level comprise one or more of:

average rate, duration, frequency, magnitude, delay budget, peak frequency, peak magnitude, peak delay budget, peak transmission time, incident type, expected incident time, expected incident message volume, and expected incident message delay budget,

wherein the average rate indicates an average sending rate of messages in the connection, the duration indicates the duration of the connection, the frequency indicates a message sending frequency, the size indicates a message average value sent every frequency, the delay budget indicates a time consumption budget for all messages to be transmitted to a receiving end in a period, the peak frequency indicates a peak generating frequency of the message, the peak delay budget indicates a time consumption budget for all messages to be transmitted to the receiving end, the peak sending time indicates a message peak sending time, the type of the sudden event type indicates a category of the sudden event, the predicted time of the sudden event indicates a predicted arrival time of the sudden event message, the predicted sudden event message amount indicates a message amount transmitted by the sudden event, and the sudden event message delay budget indicates a time consumption budget for transmitting the sudden event message to the receiving end.

7. The method of claim 5 or 6, wherein the packet-level data characteristics include one or more of:

data block sequence number, data block size, packet location, and data block delay budget,

wherein the data block sequence number indicates a data block number to which the first packet belongs, the data block size indicates a data block size to which the first packet belongs, the packet position indicates a position of the data block to which the first packet belongs, and the data block delay budget indicates a time consumption budget for transmitting the first packet to a receiving end.

8. The method according to any of claims 5 to 7, wherein the connection level QoS characteristics comprise a connection QoS characteristics indication CQI and/or connection QoS characteristics information, and the packet level QoS characteristics comprise a packet QoS indication PQI and/or packet QoS characteristics information.

9. The method of any of claims 5 to 8, wherein the QoS characteristics represented by the connection-level QoS characteristic information or packet-level QoS characteristic information comprise one or more of:

resource type, priority, delay budget, and error rate.

10. The method of any of claims 5 to 9, wherein including first source QoS information in the first packet comprises:

the first message comprises connection level information and packet level information; alternatively, the first and second electrodes may be,

the first message comprises the information of the packet level, and a virtual internet protocol dummy IP packet comprises the information of the connection level; alternatively, the first and second electrodes may be,

the first packet includes the packet-level information, the connection-level information is transmitted through a control plane,

wherein the connection level information includes the connection level data characteristics and the connection level QoS characteristics, and the packet level information includes the packet level data characteristics and the packet level QoS characteristics.

11. The method according to any of claims 2 to 10, wherein said first source QoS information is used to indicate mapping of said first packets to a first quality of service flow QoS flow, said second source QoS information is used to indicate mapping of said second packets to a second QoS flow, said first QoS flow and said second QoS flow belonging to one QoS flow group.

12. The method according to any of claims 2 to 10, wherein said first source QoS information is used to indicate a quality of service identifier 5QI mapping said first packet to a first 5G network, said second source QoS information is used to indicate a mapping of said second packet to a second 5QI, said first 5QI and said second 5QI belonging to one QoS flow.

13. The method according to any of claims 2 to 12, wherein the first source QoS information is used to indicate mapping of the first packet to a first quality of service flow QoS flow, the QoS configuration of the first QoS flow comprising:

the maximum guaranteed bandwidth MGFBR;

and the MGFBR is used for adjusting resources reserved for the first QoS flow, and the guaranteed bandwidth of the first QoS flow is less than or equal to the MGFBR.

14. The method of claim 13, wherein the QoS configuration of the first QoS flow further comprises:

and the minimum guaranteed bandwidth GFBR is used for adjusting resources reserved for the first QoS flow, and the guaranteed bandwidth of the first QoS flow is greater than or equal to the GFBR and less than or equal to the MGFBR.

15. The method according to any of claims 2 to 14, wherein the first source QoS information is used to indicate mapping of the first packet to a first quality of service flow QoS flow, the QoS configuration of the first QoS flow comprising:

and indicating information, wherein the indicating information is used for indicating whether resources corresponding to the first QoS flow are reserved or not.

16. The method of any of claims 13-15, wherein the first source QoS information indicating that the first packet is mapped to a first QoS flow comprises:

the first source QoS information comprises QoS characteristics corresponding to QoS characteristics indicated by 5QI in the QoS flow.

17. The method of any one of claims 1 to 16, further comprising:

determining the state of a transmission node in a path for transmitting the first message;

and when the state of at least one input node meets a preset condition, starting an active guarantee mechanism.

18. The method of claim 17, wherein initiating an active safeguard mechanism when the state of at least one of the input nodes meets a preset condition comprises one or more of:

when packet loss exists in the at least one input node, the first message is repeatedly sent; or

And when the packet loss rate of the at least one transmission node is greater than a preset value, coding the first message by adopting a Forward Error Correction (FEC) redundancy coding mode.

19. A method for transmitting a message, comprising:

receiving a plurality of messages, wherein five-tuple information of the plurality of messages is the same, each message in the plurality of messages comprises source QoS (quality of service) information, the source QoS information of each message is used for QoS guarantee of the corresponding QoS message, and the source QoS information of the plurality of messages is different;

processing the plurality of packets based on source QoS information included in the plurality of packets.

20. The method of claim 19, wherein the plurality of packets belong to a same connection, and wherein the plurality of packets include source QoS information that is different comprises:

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,

21. The method of claim 20,

the first source QoS information includes a first QoS characteristic and a first data characteristic, the first data characteristic representing a transmission characteristic of the first packet, the second source QoS information includes a second QoS characteristic and a second data characteristic, the second data characteristic representing a transmission characteristic of the second packet, the method further comprising:

determining the QoS requirement of the first message according to the first QoS characteristic;

determining the QoS requirement of the second message according to the second QoS characteristic;

processing the plurality of packets based on source QoS information included in the plurality of packets includes:

scheduling resources of the first message according to the QoS requirement of the first message and the first data characteristic;

and scheduling the resource of the second message according to the QoS requirement of the second message and the second data characteristic.

22. The method of claim 21, wherein 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 being different comprises:

23. The method of claim 22, wherein the resources scheduling the first packet are different from the resources scheduling the second packet.

24. The method of any of claims 21 to 23, wherein the first data characteristics comprise connection-level data characteristics and/or packet-level data characteristics, the method further comprising:

determining the transmission characteristics of a plurality of messages included in the connection according to the data characteristics of the connection level;

and determining the transmission characteristic of the first message according to the data characteristics of the packet level.

25. The method of any of claims 21 to 24, wherein the first QoS characteristics comprise QoS characteristics of a connection level,

the method further comprises the following steps:

and determining the QoS requirement of a third message except the first message and the second message in the plurality of messages according to the QoS characteristics of the connection level.

26. A method as claimed in claim 24 or 25, wherein the data characteristics of the connectivity level include one or more of:

wherein the average rate indicates an average sending rate of messages in the connection, the duration indicates the duration of the connection, the frequency indicates a message sending frequency, the size indicates a message average value sent every frequency, the delay budget indicates a time consumption budget for all messages to be transmitted to a receiving end in a period, the peak frequency indicates a peak generating frequency of the message, the peak delay budget indicates a time consumption budget for all messages to be transmitted to the receiving end, the peak sending time indicates a message peak sending time, the type of an emergency event indicates a category of a time of sudden occurrence, the predicted time of the sudden event indicates a predicted arrival time of the message of the emergency event, the predicted message amount of the sudden event indicates a message amount transmitted by the sudden event, and the burst event message delay budget indicates a time consumption budget for all messages to be transmitted to the receiving end.

27. A method according to any one of claims 24 to 26, wherein the packet-level data characteristics include one or more of:

28. The method according to any of claims 25 to 27, wherein the connection level QoS characteristics comprise a connection QoS characteristics indication, CQI, and/or connection QoS characteristics information, and the packet level QoS characteristics comprise a packet QoS indication, PQI, and/or packet QoS characteristics information.

29. The method of any of claims 25 to 28, wherein the QoS characteristics represented by the connection-level QoS characteristics or packet-level QoS characteristics comprise one or more of:

resource type, priority, delay budget, and error rate.

30. The method of claim 29, wherein the method further comprises:

receiving a packet filtering rule from a core network device, wherein the packet filtering rule comprises the CQI and/or the PQI;

and mapping the first message to a first quality of service flow (QoS) flow according to the CQI and/or the PQI.

31. The method of claim 29 or 30, further comprising:

receiving a reflection trigger indication (RDI) and the PQI;

recording the PQI according to the RDI, wherein the PQI is used for indicating that a fourth message is mapped to a third QoS flow;

and the fourth message is a message to be sent, and the QoS characteristic indicated by the 5QI in the third QoS flow corresponds to the PQI.

32. The method of any of claims 25 to 31, wherein including first source QoS information in the first packet comprises:

33. The method of any of claims 20 to 32, further comprising:

mapping the first message to a first quality of service flow QoS flow according to the first source QoS information;

mapping the second message to a second QoS flow according to the second source QoS information;

wherein the first QoS flow and the second QoS flow belong to one QoS flow group.

34. The method of any of claims 20 to 32, further comprising:

mapping the first message to a service quality identifier (5 QI) of a first 5G network according to the first source QoS information;

mapping the second message to a second 5QI according to the second source QoS information;

wherein the first 5QI and the second 5QI belong to one QoS flow.

35. The method of claim 33, wherein the mapping the first packet to a first QoS flow based on the first source QoS information comprises:

determining the first QoS flow from a plurality of QoS flows according to a first QoS characteristic included in the first source QoS information, wherein the first QoS characteristic included in the first source QoS information corresponds to a QoS characteristic indicated by 5QI in the first QoS flow.

36. The method of claim 33 or 35,

the QoS configuration of the first QoS flow comprises:

the maximum guaranteed bandwidth MGFBR;

the method further comprises the following steps:

and determining that the guaranteed bandwidth of the first QoS flow is less than or equal to the MGFBR.

37. The method of claim 36, wherein the QoS configuration of the first QoS flow further comprises:

minimum guaranteed bandwidth GFBR;

the method further comprises the following steps: and determining 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.

38. The method of any of claims 33 or 35 to 37, wherein the QoS configuration of the first QoS flow comprises:

indicating information, wherein the indicating information is used for indicating whether resources corresponding to the first QoS flow are reserved or not;

and determining whether to reserve the resources corresponding to the first QoS flow or not according to the indication information.

39. The method of any of claims 20 to 38, wherein the first source QoS information is received or the first source QoS information is locally generated;

when the first source QoS information is locally generated, the method further comprises:

and filling the first source QoS information into the first message.

40. The method of any one of claims 19 to 39, further comprising:

41. The method of claim 40, wherein initiating an active safeguard mechanism when the state of at least one of the input nodes meets a preset condition comprises one or more of:

42. An apparatus for transmitting messages, characterized by being configured to perform the method of any one of claims 1 to 18.

43. An apparatus for transmitting messages, characterized by being configured to perform the method of any of claims 19 to 41.

44. A computer readable storage medium comprising computer instructions which, when executed by a processor, cause the computer to perform the method of any of claims 1 to 18 or cause the computer to perform the method of any of claims 19 to 41.

45. A chip arrangement, characterized in that it comprises processing circuitry for calling up and running a program from a memory, causing a communication device on which the chip arrangement is installed to perform a method according to any one of claims 1 to 18, or causing the communication device on which the chip arrangement is installed to perform a method according to any one of claims 19 to 41.