CN118075196A

CN118075196A - Message transmission method, device and equipment

Info

Publication number: CN118075196A
Application number: CN202211466057.1A
Authority: CN
Inventors: 杨滨华; 叶浩楠; 张永康; 彭书萍
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-11-22
Filing date: 2022-11-22
Publication date: 2024-05-24

Abstract

The application provides a method, a device and equipment for transmitting a message, which are used for providing a technical scheme for realizing application-aware network (APN) which is commonly used for different equipment. The message transmission method comprises the following steps: determining first application information according to a first application program; and sending a first message, wherein the first message comprises the first application information, the first message is an internet protocol fourth version IPv4 message, and the first message is associated with the first application program.

Description

Message transmission method, device and equipment

Technical Field

The present application relates to the field of communications, and in particular, to a method, an apparatus, and a device for transmitting a message.

Background

With the development of technology, the differentiated demands of different services on the network are more and more obvious. For this reason, application-aware networking (APN) technology has been developed. The APN technology can provide different network services for different services, so that message transmission of different types of services can be ensured.

Specifically, the APN technology is implemented by carrying relevant information of the application program in the message. For example, in the internet protocol version 6 (Internet Protocol Version, IPv 6) network, the information of the application may be carried in the IPv6 header of the message. The network device used for transmitting the message in the network can analyze the relevant information of the application program from the IPv6 message header of the message, so that the message is sent according to the relevant information of the application program and provided for the message.

The above APN technology requires that a device or system generating a message add relevant information of an application program in an IPv6 header. But limited by hardware or software, some devices and systems do not have information about adding an application program in an IPv6 message, and therefore cannot deploy an APN.

Disclosure of Invention

The application provides a message transmission method, a message transmission device and message transmission equipment, which are used for providing a technical scheme for realizing APN (access point name) which is commonly used for different equipment.

In a first aspect, the present application provides a method for transmitting a message. The message transmission method can be applied to equipment or equipment clusters with the requirement of sending APN messages. Specifically, in order to implement the APN technology through the IPv4 message, first application information may be determined according to the first application program, and then the first message including the first application information may be transmitted. The first message is an IPv4 message, the first application information is used for indicating a first application program, and the first application program is associated with the first message. Specifically, the first application may be an application that generates the first message, or may be an application that provides an APN service. The first application information is used for indicating transmission conditions required by the first message. In this way, the first application information related to the first application program is carried in the IPv4 message (i.e., the first message), even if the first device does not support the network protocol with higher programmability such as IPv6 or SRv, by carrying the first application information in the IPv4 message, the information of the application program related to the first message can still be sent to the network device on the transmission path of the first message, so that the network device can select a corresponding transmission policy according to the first application information to transmit the message, and provide a required SLA guarantee for the message. Therefore, the technical scheme for realizing the APN, which can be commonly used for different devices, is provided, and can support the APN to be realized in the original network such as IPv4 and the like.

In some possible embodiments, the first application information may be carried in an IPv4 header of the first message. Specifically, the first application information may be carried in any one or more fields of a flag (Flags) field, a type of service (ToS) field, an Identifier (ID) field, and an internet protocol option (IP option) field of an IPv4 header of the first message. If the first application information is carried in the Flags field, the first application information may be carried through bit 0 of the Flags field (i.e., the first bit of the binary number corresponding to the Flags field). If the first application information is carried in the ToS field, the first application information may be carried through bit 6 or bit 7 of the ToS field.

In some possible embodiments, if the first application information is carried in an ID field or an IP option field of an IPv4 header of the first message, the IPv4 header of the first message may further include the first identification information. The first identification information is used for indicating that the ID field or the IP option field of the IPv4 message header of the first message comprises first application information. Accordingly, the network device transmitting the first message may determine that the ID field or the IP option field of the IPv4 header of the first message includes the first application information based on the first identification information, so as to determine the first application information by analyzing the ID field or the IP option field of the IPv4 header of the first message.

In some possible embodiments, the first identification information may be carried in any one or more of the Flags field, the ToS field, and the IP option field of the IPv4 header of the first message. Specifically, if the first identification information is carried in the Flags field, the first identification information may be carried by bit 0 of the Flags field (i.e., the first bit of the binary number corresponding to the Flags field). If the first identification information is carried in the ToS field, the first identification information may be carried through bit 6 or bit 7 of the ToS field.

In some possible embodiments, the first identification information may also be carried in load (payload) information of the first packet. Accordingly, the network device forwarding the first packet may determine the first identification information by analyzing payload information of the first packet.

In some possible implementations, if the first packet is used to transmit media data, the payload information of the first packet may include a real-time transport protocol (RTP) header. Accordingly, the first application information may be carried in an RTP header extension (RTP HEADER extension) field of the first message. Specifically, the first application information may be carried in a TLV field of RTP HEADER extension field.

In a second aspect, the present application provides a method for transmitting a message. The method can be applied to a first network device transmitting a first message. The first network device may be, for example, a router or a switch or the like. Specifically, the first network device may first obtain a first packet including first application information. The first message is an IPv4 message, and the first application information in the first message is used to indicate a first application program associated with the first message. The first network device may then forward the first message according to the first application information. That is, the first network device that transmits the first packet may forward the first packet according to the information related to the application program carried in the first packet. Forwarding the message according to the information of the application program is equivalent to implementing the APN technology. In this way, the first application information related to the first application program is carried in the IPv4 message (i.e., the first message), even if the first device does not support the network protocol with higher programmability such as IPv6 or SRv, by carrying the first application information in the IPv4 message, the information of the application program related to the first message can still be sent to the network device on the transmission path of the first message, so that the network device can select a corresponding transmission policy according to the first application information to transmit the message, and provide a required SLA guarantee for the message. Therefore, the technical scheme for realizing the APN, which can be commonly used for different devices, is provided, and can support the APN to be realized in the original network such as IPv4 and the like.

In some possible embodiments, the first application information is carried in any one or more of the following fields of an IPv4 header of the first message: flag field, toS field, ID field, and IP option field.

In some possible implementations, the first application information is carried in an ID field and/or an IP option field of an IPv4 header of the first message. Accordingly, after the first network device obtains the first message, the first network device may determine that the first message includes the first application information according to the first identification information. The first identification information is used for indicating that the first application information is carried in an ID field and/or an internet protocol option IP option of an IPv4 header of the first message.

In some possible embodiments, the first identification information is carried in any one or more of the following fields of an IPv4 header of the first message: flag field, toS field, and IP option field.

In some possible implementations, the first application information is carried in payload information of the first message.

In some possible embodiments, the payload information of the first packet includes an RTP header, and the first application information is carried in a RTP HEADER extension field of the RTP header.

In some possible embodiments, the first network device may encapsulate the first packet according to the first application information. For example, the first network device may encapsulate the first packet into an IPv6 packet according to the first application information, and add the first application information to the encapsulated IPv6 packet. Thus, even if other network devices on the forwarding path of the first message do not have the capability of implementing APN forwarding based on the IPv4 message, by encapsulating the first message into the IPv6 message, the other network devices can still forward the first message based on the first application information. Specifically, the first network device may generate the second message in the IPv6 format according to the first message. The load information of the second message is matched with the load information of the first message, and the IPv6 message header of the second message comprises the first application information. Then, the first network device may send a second message to the next hop device corresponding to the first message.

In a third aspect, the present application provides a message transmission apparatus, where the apparatus includes: the processing unit is used for determining first application information according to the first application program; the sending unit is configured to send a first packet, where the first packet includes the first application information, the first packet is an IPv4 packet, and the first packet is associated with the first application program.

In some possible implementations, the first application information is carried in an ID field and/or an IP option field of an IPv4 header of the first message; the IPv4 header of the first message further includes first identification information, where the first identification information is used to indicate that an ID field or an IP option field of the IPv4 header of the first message includes the first application information.

In a fourth aspect, the present application provides a message transmission apparatus, where the apparatus includes:

The device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a first message, the first message comprises first application information, the first application information is used for indicating a first application program associated with the first message, and the first message is an IPv4 message; and the processing unit is used for forwarding the first message according to the first application information.

In some possible implementations, the first application information is carried in an ID field and/or an IP option field of an IPv4 header of the first message; the processing unit is further configured to determine that the first packet includes the first application information according to first identification information, where the first identification information is used to indicate that the first application information is carried in an ID field and/or an IP option field of an IPv4 packet header of the first packet.

In some possible embodiments, the processing unit is specifically configured to generate a second packet according to a first packet, where load information of the second packet is matched with load information of the first packet, the second packet is an IPv6 packet, and an IPv6 packet header of the second packet includes the first application information; and sending the second message.

In a fifth aspect, an embodiment of the present application further provides a terminal device, where the terminal device includes: at least one processor coupled with the at least one memory: the at least one processor is configured to execute the computer program or the instructions stored in the at least one memory, so that the network device executes the packet transmission method according to the first aspect.

In a sixth aspect, an embodiment of the present application further provides a network device, including: at least one processor coupled with the at least one memory: the at least one processor is configured to execute the computer program or the instructions stored in the at least one memory, so that the network device executes the packet transmission method according to the second aspect.

In a sixth aspect, an embodiment of the present application provides a network system, including the terminal device according to the fifth aspect and at least one network device according to the sixth aspect.

In a seventh aspect, an embodiment of the present application provides a chip, including a processor and an interface circuit, where the interface circuit is configured to receive an instruction and transmit the instruction to the processor; the processor is configured to execute the message transmission method described in the second aspect.

In an eighth aspect, an embodiment of the present application provides a computer readable storage medium, including a computer program, which when executed on a computer, causes the computer to perform the method for transmitting a message according to the first aspect or the second aspect.

In a ninth aspect, an embodiment of the present application provides a computer program product comprising a program or code which, when run on a computer, implements the method for transmitting messages according to any one of the first or second aspects.

Drawings

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;

Fig. 2 is an interaction schematic diagram of a message transmission method according to an embodiment of the present application;

Fig. 3 is a schematic diagram of one possible format of an IPv4 header of a first packet according to an embodiment of the present application;

FIG. 4 is a schematic diagram of one possible format of the ID field in the IPv4 header of the first message according to the embodiment of the present application;

FIG. 5 is a schematic diagram of a possible format of an IP option segment in an IPv4 header of a first message according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a message transmission device 600 according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a message transmission device 700 according to an embodiment of the present application;

Fig. 8 is a schematic structural diagram of a network device 800 according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a network device 900 according to an embodiment of the present application.

Detailed Description

APN technology is an important current development direction in the field of communications. The APN technology may forward messages from different applications through different policies, thereby providing different service level agreements (SERVICE LEVEL AGREEMENT, SLA) guarantees for different applications. Thus, more refined network service can be enabled, and the network service quality is improved.

Specifically, the device (e.g., terminal or server) that generates the message may carry information about the application program in the message. The device (such as a router or a switch) for transmitting the message can analyze the related information of the application programs carried in the message, and select a corresponding transmission strategy to transmit the message according to the related information of the application programs, thereby providing the required SLA guarantee for the message. The related information of the application program may include, for example, an identifier of the application program, or may include information such as a service type identifier corresponding to the message.

The following description will take, as an example, that the related information of the application program includes an identification of the application program, with reference to fig. 1.

Referring to fig. 1, the diagram is a schematic view of an application scenario provided in an embodiment of the present application. In the application scenario shown in fig. 1, device 110, network device 121, network device 122, network device 123, network device 124, and device 130 are included. Wherein network device 121, network device 122, network device 123 and network device 124 belong to network 120, network device 121 is connected with device 110, network device 122 and network device 123 respectively, network device 124 is connected with network device 123 and device 130 respectively, and network device 122 is also connected with device 130. Application 1 and application 2 are running in device 110. Application 1 may generate message 1 and application 2 may generate message 2. Message 1 and message 2 are sent to device 130 over network 120. If the device 110 and the network device 121 apply the APN technology, the device 110 may add the application program identifier to the message 1 and the message 2, and the network device 121 may select a corresponding path to forward according to the application program identifier.

For example, assume that the delay of the transmission of the message along the transmission path "network device 121→network device 122→device 130" is smaller than the delay of the transmission of the message along the transmission path "network device 121→network device 123→network device 124→network device 130", the network bandwidth of the transmission path "network device 121→network device 123→network device 124→network device 130" is larger than the network bandwidth of the transmission path "network device 121→network device 122→device 130", and that the application 1 is an application with a higher demand for time delay (for example, a video conference type application), and the application 2 is an application with a lower demand for time delay but a higher demand for network bandwidth (for example, a file transmission type application).

In this way, after receiving the message 1 sent by the device 110, the network device 121 may determine that the message 1 is sensitive to time delay according to the identifier of the application program carried in the message 1, that is, the identifier of the application program 1. Network device 121 may transmit message 1 via the lower latency transmission path network device 121-network device 122-device 130. Similarly, after receiving the message 2 sent by the device 110, the network device 121 may determine that the message 2 is a message insensitive to delay but having a high requirement on network bandwidth according to the identifier of the application program carried in the message 2, that is, the identifier of the application program 2. Network device 121 may transmit message 2 via path transmission path network device 121-network device 123-network device 124-network device 130.

In the above description, the network device 121 may select an appropriate forwarding path based on the identification of the application program, so as to provide delay guarantee for the packet. It will be appreciated that in some other possible implementations, the network device 121 may also guarantee the delay of the packet 1 in other ways. The delay of the message 1 can be ensured by means of tunnel encapsulation, for example. In summary, in a network applying the APN technology, a transmission mode of a message can be selected based on related information of an application program, so that a corresponding SLA guarantee is provided for the message, and network service quality is improved.

As can be seen from the above description, the APN technology depends on the relevant information of the application program carried in the message. Currently, in order to be able to carry information about applications, APN technology is mostly implemented based on IPv6 networks or on IPv 6-based segment routing protocol (Segment Routing over IPv, SRv) networks. That is, the message sent by the terminal device or the server deployed with the APN is an IPv6 message or SRv message. Thus, since the IPv6 message header or SRv message header has a larger programmable space, the method can be used for carrying the related information of the application program, and has the basis of realizing the APN technology. Taking an IPv6 message as an example, relevant information of an application program may be carried in a message header such as a hop-by-hop option header (hop-by-hop options header, HBH), an address option header (destination options header, DOH), or a Routing Header (RH) of the IPv6 message header of the message.

But some of the servers and end devices may not support IPv6 or SRv6 at present, still transmitting messages based on internet protocol version 4 (Internet Protocol Version, IPv 4). Thus, since the IPv4 header of the IPv4 packet does not have enough programmable space, it is difficult to carry information about the application program. Therefore, devices that do not support IPv6 or SRv technologies at present cannot use APN technology, resulting in a great limitation on the deployment and application of APNs.

In order to solve the above problems, an embodiment of the present application provides a method for transmitting a message, which is used to provide a technical solution for implementing an APN that can be used for different devices. The method may be applied to a network system including an IPv4 enabled device. Obviously, devices supporting IPv6 or SRv6 may also be included in the network system.

The method provided by the embodiment of the application can be applied to the network architecture shown in fig. 1.

In the embodiment shown in fig. 1, message 1 and message 2 are generated by device 110 and sent to device 130. The device 110 and/or the device 130 may be a terminal device or a server. A terminal device, which may also be referred to as a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), a terminal, etc., is a device that provides voice and/or data connectivity to a user, or a chip disposed in the device, for example, a handheld device, an in-vehicle device, etc., having a wireless connection function. Currently, examples of some terminal devices are: a mobile phone, a desktop computer, a tablet computer, a notebook computer, a palm computer, a mobile internet device (mobile INTERNET DEVICE, MID), a wearable device, a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (SELF DRIVING), a wireless terminal in teleoperation (remote medical surgery), a wireless terminal in smart grid (SMART GRID), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), a home gateway device supporting 5G access (5G-RESIDENTIAL GATEWAY, 5G-RG), and the like.

Alternatively, if the device 110 is a server, the device 110 may be one server or a server cluster formed by a plurality of servers. Specifically, if device 110 is a server cluster of multiple servers, message 1 may be generated by a software module deployed in the server cluster and sent to device 130. Accordingly, the device 130 may also be a server or a server cluster formed by a plurality of servers. That is, the method for transmitting a message provided in the embodiment of the present application may be applied to a cloud scenario, and the first message mentioned below may be a message generated by the cloud or a message sent to the cloud. That is, the message transmission method provided by the embodiment of the application can be applied to an application scene of sending a message from a terminal device to the terminal device, an application scene of sending a message from the terminal device to a cloud terminal, an application scene of sending a message from a cloud terminal to the terminal device, and an application scene of sending a message from a cloud terminal to a cloud terminal.

The network device 121, the network device 122, the network device 123, and the network device 124 may be entity devices supporting a routing function, such as a router (router), a switch (switch), or may be servers deploying virtual routers or virtual switches, for transmitting messages or other messages between the device 110 and the device 130. Wherein network device 121, network device 122, network device 123, and network device 124 are IPv 4-capable network devices. Alternatively, network device 121, network device 122, network device 123, and network device 124 may be network devices supporting other network protocols such as IPv6 or SRv.

In the following, in connection with fig. 2, a description will be given of a technical solution provided in an embodiment of the present application, taking a case that a message is generated by a first device and sent to a second device through a network. Referring to fig. 2, the signaling interaction diagram of the message transmission method provided by the embodiment of the present application specifically includes the following S201, S202, S203, and S204.

S201: the first device determines first application information according to the first application program.

In the embodiment of the application, the terminal equipment can determine the first application information according to the first application program. The first device may be a terminal device or a server, or may be a software module running in a server cluster. For example, the first device may be device 110 in the embodiment shown in FIG. 1. The first application is an application running on the first device. The first application information is used for indicating the first application program.

The method for transmitting the message provided by the embodiment of the application can be applied to the process that the first equipment transmits the message to the second equipment. Accordingly, the first application is an application associated with a message sent by the first device to the second device. Specifically, there are at least the following two possible implementations.

In a first possible implementation manner, the first application may be an application that generates a message to be sent, that is, a first message described below is generated by the first application. The first application information may include an identification of the first application. Or if the message generated by the first application program relates to multiple services, the first application information may include an identification of the service corresponding to the message to be sent (for example, a first message described below).

For example, assume that the first application is instant messaging software, including both text messaging services and video telephony services. The first application information may include an identifier of the first application program, or may include an identifier of a service corresponding to a message to be sent by the first application program. If the message to be sent is used for transmitting text data, the first application information may include an identification of the text transmission class service. If the message to be sent is used for transmitting image data or audio data corresponding to the video telephony service, the first application information may include an identifier of the video telephony service. Optionally, the first application information may further include an identifier of the first application program and an identifier of a service corresponding to the message to be sent.

In a second possible implementation, the first application is an application on the first device for sending a message based on the APN. For example, a message to be sent may be generated by a second application on a first device and then sent by the first application to the second device. In the process of sending the message, the first application program can determine the network environment required for sending the message to be sent, thereby determining the first application information. Specifically, the first application may acquire the type of the second application and then generate corresponding first application information. Or the first application program can determine the first application information according to the service type corresponding to the message to be sent.

According to the foregoing description, the method for transmitting a message provided in the embodiment of the present application may also be applied to an application scenario including a cloud, and then S201 may also be executed by a cloud platform. Correspondingly, the first application program may be a software module running on the cloud platform and used for generating the message to be sent, or may be a software module running on the cloud platform and providing an APN service for the message to be sent. Alternatively, the first application may run on one or more servers in the cloud.

S202: the first device generates a first message according to the first application information.

After determining the first application information according to the first application program, the first device may generate a first message. The first message is a message for transmitting the second device. The first message includes first application information and data to be sent, namely data which the first device actually needs to send to the second device. In the embodiment shown in fig. 2, the message to be sent mentioned in S201 is the first message. The data to be sent may be carried in payload (payload) information of the first packet.

According to the foregoing description, the technical solution provided by the embodiment of the present application may be applied in various network environments. Alternatively, if the first device is an IPv6 enabled device, the first message may be an IPv6 message, and the first application information may be carried in an IPv6 header of the first message. If the first device is a SRv6 capable device, the first message may be a SRv6 message and the first application information may be carried in a SRv header of the first message. The specific implementation manner in which the first message carries the first application information is not described herein.

If the first device is a message that does not support IPv6 and SRv, the first message generated by the first device may be an IPv4 message. Accordingly, the first application information may be carried in an IPv4 header of the first message. Or the first application information can be carried in payload information of the first message in consideration of the limited length of the IPv4 message header.

These two cases are described separately below.

First, a case that first application information is carried in an IPv4 header is described. Specifically, if the first application information is carried in the IPv4 header of the first message, the first application information may be carried based on at least the following three implementations.

The implementation mode is as follows: the first application information is carried in a flag (flags) field and/or a ToS field of an IPv4 header of the first message.

In a first possible implementation, the first application information may be carried in flags fields and/or ToS fields of an IPv4 header of the first message. For example, referring to the format diagram of the IPv4 header shown in fig. 3, the first application information may be carried in the Tos field and the Flags field of the IPv4 header shown in fig. 3.

Specifically, in the native IPv4 (NATIVE IPV 4), the 0 th bit of the flag field of the IPv4 header of the message (i.e., the first bit of the binary number corresponding to the flag field) is a reserved bit, and may be used to carry the first application information. Thus, if the first application information can be represented by a 1-bit binary number, the first application information can be carried in bit 0 of the flag field of the IPv4 header of the first message. Accordingly, the network device transmitting the first message may determine the first application information according to the value of bit 0 of the flag field of the IPv4 header of the first message.

In addition, in a network using the transmission control protocol (Transmission Control Protocol, TCP), bits 6 and 7 of the ToS field are used to implement TCP flow control techniques. To this end, in some non-TCP scenarios, such as in the user datagram protocol (user datagram protocol, UDP) or the like, bits 6 and 7 of the ToS field of the IPv4 header of the first message may be used to carry the first application information. Thus, if the first application information can be represented by a 2-bit binary number, the first application information can be carried in the 6 th bit and 7 th bit of the ToS field of the IPv4 header of the first message. Accordingly, the network device transmitting the first message may determine the first application information according to the values of the 6 th bit and the 7 th bit of the ToS field of the IPv4 header of the first message.

Optionally, in order to increase the length of the first application information, the flags field and the ToS field of the Pv4 header of the first packet may also be used to carry the first application information together. For example, assuming that the first application information may be represented by a 3-bit binary number, bit 1 of the first application information may be carried in bit 0 of the flag field of the IPv4 header of the first message, and bits 2 and 3 of the first application information may be carried in bits 6 and 7 of the ToS field of the IPv4 header of the first message, respectively. Accordingly, the network device transmitting the first message may determine the first application information according to the value of the 0 th bit of the flag field and the values of the 6 th bit and the 7 th bit of the ToS field of the IPv4 header of the first message.

The implementation mode II is as follows: the first application information is carried in an ID field of an IPv4 header of the first message.

In a second possible implementation, the first application information may be carried in an ID field of an IPv4 header of the first message. The ID field of the IPv4 header includes 16 bits (bits) that can be used to carry a 16-bit binary number. Thus, if the first application information can be represented by a 16-bit binary number, the first application information can be carried in the ID field of the IPv4 header of the first message. Accordingly, the network device transmitting the first message may determine the first application information according to the value of the ID field of the IPv4 header of the first message.

Optionally, the ID field of the IPv4 header of the first message is in the form of a type-value (TV) field. Wherein, the value part of the TV field is used to carry the first application information, and the type part of the TV field is used to indicate the type of the first application information. For example, as can be seen from the foregoing description, the first application information may be an identifier of the first application program, or may be an identifier of a service corresponding to the data to be sent corresponding to the first packet. The Type portion may be specifically used to indicate a Type of the first application information.

In some possible application scenarios, the first application may be any one of an SLA template, an application identifier (APP ID), a User identifier (User ID), or a Flow identifier (Flow ID) corresponding to the first message. Thus, the type portion of the TV field may include 2 or 3 bits. Taking the example that the type part comprises 3 bits, if the first application information is used for indicating the SLA template corresponding to the first message, the value of the type part may be 000; if the first application information is used for indicating the APP ID corresponding to the first message, the value of the type part may be 001; if the first application information is used for indicating a User ID corresponding to the first message, the value of the type part may be 010; if the first application information is used to indicate a Flow ID corresponding to the first message, the value of the type portion may be 011.

Accordingly, in the above implementation, the value portion of the TV field includes 13 bits, and then the first application information may be identified by a 13-bit binary number. That is, if the value of the type portion is 000, the network device transmitting the first message may select one SLA template from 8196 SLA templates to transmit the first message according to the value of the value portion. If the value of the type portion is 001, the value of the value portion may identify one application of 8196 applications. Alternatively, the ID field of the IPv4 header of the first message in the above description may be as shown in FIG. 4

In some possible application scenarios, the ID field of the IPv4 header may be used to carry relevant information generated by the operating system. For example, in some implementations, the ID field of the IPv4 header may be used to assist in the segmentation and reassembly of the data packet. That is, the information carried in the ID field of the IPv4 header of the first message may or may not be the first application information.

For this purpose, in order to enable the network device transmitting the first message to distinguish the type of information carried in the ID field of the IPv4 header of the message, the first message may further include first identification information. The first identification information may also be referred to as control information or control bit information, and an ID field for indicating an IPv4 header of the first message includes first application information. That is, if the first message includes the first identification information, the ID field of the IPv4 header of the first message is used to carry the first application information. Accordingly, the network device transmitting the first packet may determine whether the first packet includes the first identification information. If the first message includes the first identification information, the network device may obtain the first application information from an IPv4 header of the first message.

Optionally, the first identification information may be carried in an IPv4 header of the first packet. The field in the IPv4 header of the first message that is used to carry the first message may be referred to as a control bit field. For example, the first identification information may be carried in the flag field and/or the ToS field of the IPv4 header of the first message.

For example. The 0 th bit of the flag field of the IPv4 header of the first packet may be a control bit. If the value of bit 0 of the Flags field is 1, the ID field of the IPv4 header of the first message includes the first application information. If the value of bit 0 of the Flags field is 0, it is indicated that the ID field of the IPv4 header of the first message does not include the first application information.

In a third possible implementation, the first application information is carried in an internet protocol option (IP option) field of an IPv4 header of the first message.

In a third possible implementation manner, the first application information may be carried in an IP option field of an IPv4 header of the first message. Thus, the capacity of the IP option field is larger, the programmability is higher, and longer first application information can be carried. Obviously, the longer the length of the first application information is, the larger the amount of information that can be carried in the first application information is, and the finer the granularity of the division of the network service provided for the first device is.

At present, the IPv4 has a plurality of different types of IP option fields, the existing IP option can be utilized to automatically carry the first application information, and a new IP option field can be established to carry the first application information. For example, in some possible implementations, the first application information may be carried through a stream ID option (STREAM IDENTIFIER option) field. Alternatively, the first application information may be carried in the stream ID portion of the stream ID option field, for example, the first application information may be carried in the form of a TV field.

Alternatively, the IP option field of the IPv4 header of the first packet may be as shown in fig. 5. Wherein the value of the type portion of the IP option field is 10001000 (136 in decimal), and the Stream ID portion indicating the IP option field includes first application information. The value of the length portion of the IP option field is 00000010 (4 in decimal), which indicates that the first application information included in the Stream ID portion of the IP option field corresponds to a 4-bit decimal number. The method for carrying the first application information in the Stream ID through the TV field may be referred to above, and will not be described herein.

It should be noted that, in some application scenarios, the forwarding plane of the network device transmitting the message may determine whether the IP option field in the IPv4 header of the message is empty. If the IP option field in the IPv4 message header of the message is empty, the transmission of the message is carried out by the forwarding plane of the network equipment. If the IP option field in the IPv4 header of the message is not null, the forwarding plane of the network device may send the message to the control plane of the network device for further processing, for example, by a central processing unit (central processing unit, CPU) of the network device. The uploading of the message to the control plane for processing consumes additional time. For this reason, in some networks with more stringent latency requirements, the first application information may be carried through the first and second implementations described above.

Some implementations are described above in which the first application information is carried in an IPv4 header of the first message. One implementation of carrying the first application information in the payload information of the first message is described below. It will be appreciated that the first application information may be carried in the payload information of the first packet in other manners, which are not shown here.

In some possible implementations, the payload information of the first packet may include a transport layer protocol header. Alternatively, the first application information may be carried in a transport layer protocol header of payload information of the first message. For example, the first application information may be carried in a type-length-value (TLV) field of a transport layer protocol header of payload information of the first message.

In the following, a specific implementation manner in which the first application information is carried in the transport layer protocol header of the payload information of the first packet is described by taking the first packet for carrying audio and video data as an example.

If the first packet is used for carrying audio/video data, the transport layer protocol header of the payload information of the first packet may be an RTP header. Accordingly, the first application information may be carried in RTP HEADER extension field of the RTP header of the first message. Specifically, the first application information may be carried in a TLV field of RTP HEADER extension field.

S203: the first device sends a first message to the first network device.

After generating the first message, the first message may send the first message to the first network device. Wherein the first network device is a network device with an APN function deployed. That is, the first network device has a capability of resolving the first application information carried in the first packet.

Optionally, the first network device may be a network device in the network system that receives the first packet, for example, an Access Point (AP) device or a switch. Or the first network device may be any network device on the path from the first device to the second device. That is, the first device may send the first message directly to the first network device, or may send the first message to the first network device through other network devices.

S203: and the first network equipment sends a first message to the second equipment according to the first application information.

After receiving the first message, the first network device may parse the first message, and then send the first message to the second device according to the first application information carried in the first message. The first network device may be preconfigured according to a method of application information carried in the packet. Thus, after receiving the first message, the first network device may parse the first application information from the field of the first message.

For example, assume that the first application information is carried in bits 6 and 7 of the ToS field of the IPv4 header of the first message. Then after receiving the first message, the first network device may determine that bits 6 and 7 of the ToS field of the IPv4 header of the first message determine the first application information. Or if the first application information is carried in the ID field of the IPv4 header of the first message, and the 0 th bit of the flag field of the IPv4 header of the first message is the control bit, the first network device may first determine whether the 0 th bit of the flag field of the IPv4 header of the first message indicates that the ID field of the IPv4 header of the first message carries the first application information. If yes, the first network device determines the first application information according to the ID field of the IPv4 message header of the first message.

After determining the first application information, the first network device may send a first message to the second device according to the first application information. Specifically, a plurality of message transmission rules may be set in the first network device in advance. Thus, after the first network device determines the first application information, the first network device may select a message transmission rule corresponding to the first application information from a plurality of preset message transmission rules, and send the first message according to the selected message transmission rule. The message transmission rule may include, for example, sending a first message to the second device through a preset transmission path, or may include tunneling encapsulation of the first message, and then sending the first message to the second device through a specific tunnel.

Optionally, if the first packet is an IPv4 packet, the first network device may encapsulate the first packet as the second packet, considering that some network devices in the network system may not support an APN technology based on IPv 4. Specifically, the first network device may generate the second message according to the first message. The second message is an IPv6 message, the second message includes data to be transmitted included in the first message, and an IPv6 message header of the second message includes first application information. The first network device may then send a second message to the second device. In this way, since the first packet is encapsulated by the first network device into the IPv6 packet, and the IPv6 packet header of the encapsulated first packet (i.e., the second packet) includes the first application information, even if the network devices after the first network device on the transmission path do not have the capability of implementing the APN technology based on the IPv4 packet, these network devices can parse the second packet serving as the IPv6 packet, so as to forward the second packet according to the first application information in the IPv6 packet header of the second packet. Thus, by deploying a relatively small number of network devices in the network system that have the ability to implement APN technology based on IPv4 messages, APN services can be provided for devices that do not support IPv 6. It can be appreciated that the first network device may also encapsulate the first packet into SRv packets or other packets, which are not described herein.

In the embodiment of the present application, the first device may carry the first application information related to the first application program in an IPv4 message (i.e., the first message described above), and forward the IPv4 message through the first network device having the function of resolving the first application information. In this way, even if the first device does not support the network protocol with higher programmability such as IPv6 or SRv, by carrying the first application information in the IPv4 message, the information of the application program related to the first message can still be sent to the network device on the transmission path of the first message, so that the network device can select a corresponding transmission policy according to the first application information to transmit the message, and provide the required SLA guarantee for the message. Therefore, the technical scheme for realizing the APN, which can be commonly used for different devices, is provided, and can support the APN to be realized in the original network such as IPv4 and the like.

In the following, in connection with the application scenario shown in fig. 1, the technical solution provided in the embodiment of the present application is described in detail by taking the first device as the device 110, the second device as the device 130, and the first network device as the network device 121 as an example.

If application 1 running on device 110 needs to send data A to device 130, device 110 may determine application information 1 from application 1. The application information 1 may include, for example, an identifier of the application 1, or may include an identifier of a service corresponding to the data a to be sent by the application 1. After determining application information 1, device 110 generates message 3 from application information 1. The message 3 is an IPv4 message, an ID field of an IPv4 header of the message 3 is used to carry application information 1, a value of bit 0 of a flag field of the IPv4 header of the message 3 is 1, an ID field of the IPv4 header of the message 3 is indicated to carry application information 1, and a payload information portion of the message 3 includes data a to be sent by the application program 1. After generating message 3, device 110 sends message 3 to network device 121.

After receiving message 3, network device 121 may parse the IPv4 header of message 3. Because the value of the 0 th bit of the flag field of the IPv4 header of the packet 3 is 1, the network device 121 uses the information carried in the ID field of the IPv4 header of the packet 3 as application information 1, and determines the packet transmission rule corresponding to the packet 3 according to the application information 1.

For example, assuming that application 1 is a video conference type application, the requirement on the transmission delay of the message is high, then network device 121 may transmit message 3 through transmission path "network device 121→network device 122→device 130". That is, network device 121 sends message 3 to network device 122.

Alternatively, network device 121 may encapsulate message 3 as an IPv6 message or SRv message before sending message 3. Alternatively, network device 121 sending message 3 to network device 122 may refer to network device 121 sending message 3 to device 130 through a tunnel through network device 122.

Similarly, if application 2 running on device 110 needs to send data B to device 130, device 110 may determine application information 2 from application 2. The application information 2 may include, for example, an identifier of the application 2, or may include an identifier of a service corresponding to the data B to be sent by the application 2. After determining application information 2, device 110 generates message 4 from application information 2. The message 4 is an IPv4 message, an ID field of an IPv4 header of the message 4 is used to carry application information 2, a value of bit 0 of a flag field of the IPv4 header of the message 4 is 1, an ID field of the IPv4 header of the message 4 is indicated to be used to carry application information 2, and a payload information portion of the message 4 includes data B to be sent by the application program 2. After generating message 4, device 110 sends message 4 to network device 121.

After receiving message 4, network device 121 may parse the IPv4 header of message 4. Because the value of the 0 th bit of the flag field of the IPv4 header of the message 4 is 1, the network device 121 uses the information carried in the ID field of the IPv4 header of the message 4 as application information 2, and determines the message transmission rule corresponding to the message 4 according to the application information 2.

For example, assuming that application 2 is a file transfer type application, the requirements on the transmission delay of the message are high, but the requirements on the network bandwidth are high, then the network device 121 may transmit the message 4 through the transmission path "network device 121→network device 122→device 130". That is, network device 121 sends message 4 to network device 122.

Alternatively, network device 121 may encapsulate message 4 as an IPv6 message or SRv message before sending message 4. Alternatively, network device 121 sending message 4 to network device 122 may refer to network device 121 sending message 4 to device 130 through a tunnel through network device 122.

Referring to fig. 6, the embodiment of the present application further provides a message transmission apparatus 600, where the message transmission apparatus 600 may implement the function of the first device in the embodiment shown in fig. 2. The message transmission apparatus 600 includes a processing unit 610 and a transmitting unit 620. The processing unit 610 is configured to implement S201 and S202 in the embodiment shown in fig. 2, and the transmitting unit 6420 is configured to implement S203 in the embodiment shown in fig. 2.

Specifically, the processing unit 610 is configured to determine the first application information according to the first application program. The processing unit 610 may be further configured to generate a first message according to the first application information.

The sending unit 620 is configured to send a first packet, where the first packet includes the first application information, the first packet is an IPv4 packet of internet protocol version four, and the first packet is associated with the first application program.

Reference is made to the detailed description of the corresponding steps in the embodiment shown in fig. 2, and details are not repeated here.

Referring to fig. 7, the embodiment of the present application further provides a message transmission apparatus 700, where the message transmission apparatus 700 may implement the function of the first network card device in the embodiment shown in fig. 2. The message transmission device 700 includes an acquisition unit 710 and a processing unit 720. The acquiring unit 710 is configured to receive a first packet sent by the first device, and the processing unit 720 is configured to implement S204 in the embodiment shown in fig. 2

Specifically, the obtaining unit 710 is configured to obtain a first packet, where the first packet includes first application information, where the first application information is used to indicate a first application program associated with the first packet, and the first packet is an internet protocol fourth version IPv4 packet.

And a processing unit 720, configured to forward the first message according to the first application information.

It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. The functional units in the embodiment of the application can be integrated in one processing unit, or each unit can exist alone physically, or two or more units are integrated in one unit. For example, in the above embodiment, the acquisition unit, the processing unit, and the transmission unit may be the same unit or different units. The integrated units may be implemented in hardware or in software functional units.

Fig. 8 is a schematic structural diagram of an apparatus 800 according to an embodiment of the present application. The message transmission apparatus 600 and the message transmission apparatus 700 above may be implemented by the devices shown in fig. 8. With reference to fig. 8, the device 800 comprises at least one processor 801, a communication bus 802 and at least one network interface 804, and optionally the device 800 may also comprise a memory 803.

The processor 801 may be a general purpose central processing unit (Central Processing Unit, CPU), application-specific integrated Circuit (ASIC), or one or more integrated circuits (INTEGRATED CIRCUIT, IC) for controlling the execution of the program of the present application. The processor may be configured to process the packet or the period parameter, so as to implement the packet transmission method provided in the embodiment of the present application.

For example, when the first device of fig. 2 is implemented by the device shown in fig. 8, the processor may be configured to: determining first application information according to a first application program; and sending a first message, wherein the first message comprises the first application information, the first message is an internet protocol fourth version IPv4 message, and the first message is associated with the first application program.

For another example, when the first network device of fig. 2 is implemented by the device shown in fig. 8, the processor may be configured to: acquiring a first message, wherein the first message comprises first application information, the first application information is used for indicating a first application program associated with the first message, and the first message is an internet protocol fourth version IPv4 message; and forwarding the first message according to the first application information.

Communication bus 802 is used to transfer information between processor 801, network interface 804, and memory 803.

The Memory 803 may be, but is not limited to, a Read-only Memory (ROM) or other type of static storage device that can store static information and instructions, the Memory 803 may also be a random access Memory (Random Access Memory, RAM) or other type of dynamic storage device that can store information and instructions, or a Read-only optical disk (Compact Disc Read-only Memory, CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 803 may be stand-alone and coupled to the processor 801 via a communication bus 802. Memory 803 may also be integrated with processor 801.

Optionally, the memory 803 is configured to store program codes or instructions for executing the technical solutions provided by the embodiments of the present application, and the processor 801 controls the execution. The processor 801 is configured to execute program code or instructions stored in the memory 803. One or more software modules may be included in the program code. Alternatively, the processor 801 may store program codes or instructions for performing the technical solutions provided by the embodiments of the present application, in which case the processor 801 does not need to read the program codes or instructions into the memory 803.

The network interface 804 may be a device, such as a transceiver, for communicating with other devices or communication networks, which may be an ethernet, a Radio Access Network (RAN), or a wireless local area network (Wireless Local Area Networks, WLAN), etc. In the embodiment of the present application, the network interface 804 may be configured to receive a packet sent by another node in the segment routing network, or may send a packet to another node in the segment routing network. The network interface 804 may be an Ethernet interface, a fast Ethernet (FAST ETHERNET, FE) interface, a Gigabit Ethernet (GE) interface, or the like.

In a particular implementation, device 800 may include multiple processors, such as processor 801 and processor 805 shown in FIG. 8, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

Fig. 9 is a schematic structural diagram of an apparatus 900 according to an embodiment of the present application. The various devices in fig. 2 may be implemented by the devices shown in fig. 9. Referring to the schematic device structure shown in fig. 9, a device 900 includes a main control board and one or more interface boards. The main control board is in communication connection with the interface board. The main control board is also called a main processing unit (Main Processing Unit, MPU) or a routing processing card (Route Processor Card), and comprises a CPU and a memory, and is responsible for controlling and managing each component in the device 900, including routing computation, device management and maintenance functions. The interface board is also called a Line processing unit (Line Processing Unit, LPU) or Line Card (Line Card) for receiving and transmitting messages. In some embodiments, communication is via a bus between the master control board and the interface board or between the interface board and the interface board. In some embodiments, the interface boards communicate via a switch fabric, in which case the device 900 also includes a switch fabric communicatively coupled to the master board and the interface boards, the switch fabric configured to forward data between the interface boards, which may also be referred to as a switch fabric unit (Switch Fabric Unit, SFU). The interface board includes a CPU, memory, a forwarding engine, and an interface card (INTERFACE CARD, IC), which may include one or more network interfaces. The network interface may be an Ethernet interface, an FE interface, a GE interface, or the like. The CPU is in communication connection with the memory, the forwarding engine and the interface card respectively. The memory is used for storing a forwarding table. The forwarding engine is used for forwarding the received message based on a forwarding table stored in the memory, and if the destination address of the received message is the IP address of the equipment 900, the message is sent to the CPU of the main control board or the interface board for processing; if the destination address of the received message is not the IP address of the device 900, the forwarding table is looked up according to the destination, and if the next hop and the egress interface corresponding to the destination address are found from the forwarding table, the message is forwarded to the egress interface corresponding to the destination address. The forwarding engine may be a network processor (Network Processor, NP). The interface card is also called a sub-card, can be installed on the interface board, and is responsible for converting the photoelectric signal into a data frame, and forwarding the data frame to a forwarding engine for processing or an interface board CPU after performing validity check. In some embodiments, the CPU may also perform the functions of a forwarding engine, such as soft forwarding based on a general purpose CPU, so that no forwarding engine is needed in the interface board. In some embodiments, the forwarding engine may be implemented by an ASIC or field programmable gate array (Field Programmable GATE ARRAY, FPGA). In some embodiments, the memory storing the forwarding table may also be integrated into the forwarding engine as part of the forwarding engine.

The embodiment of the application also provides a chip system, which comprises: and the processor is coupled with the memory, and the memory is used for storing a program or instructions, when the program or instructions are executed by the processor, the chip system is enabled to realize the message transmission method executed by the first device in the embodiment shown in fig. 2, or the chip system is enabled to realize the message transmission method executed by the first network device in the embodiment shown in fig. 2.

Alternatively, the processor in the system-on-chip may be one or more. The processor may be implemented in hardware or in software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general purpose processor, implemented by reading software code stored in a memory. Alternatively, the memory in the system-on-chip may be one or more. The memory may be integral with the processor or separate from the processor, and the application is not limited. The memory may be a non-transitory processor, such as a ROM, which may be integrated on the same chip as the processor, or may be separately provided on different chips, and the type of memory and the manner of providing the memory and the processor are not particularly limited in the present application.

The System-on-Chip may be, for example, an FPGA, an ASIC, a System on Chip (SoC), a CPU, an NP, a digital signal processing circuit (DIGITAL SIGNAL Processor, DSP), a microcontroller (Micro Controller Unit, MCU), a programmable controller (Programmable Logic Device, PLD) or other integrated chips.

It should be understood that the steps in the above-described method embodiments may be accomplished by integrated logic circuitry in hardware in a processor or instructions in the form of software. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

The embodiment of the application also provides a computer readable storage medium, which comprises instructions, when running on a computer, causes the computer to execute the message transmission method provided by the method embodiment and executed by the first device, or causes the computer to execute the message transmission method provided by the method embodiment and executed by the first network device.

The embodiment of the application also provides a computer program product containing instructions, which when running on a computer, causes the computer to execute the message transmission method provided by the method embodiment and executed by the first device, or causes the computer to execute the message transmission method provided by the method embodiment and executed by the first network device.

The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, 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.

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

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, and the division of the units, for example, is merely a logic module division, and there may be additional divisions when actually implemented, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 may be acquired according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each module unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units described above may be implemented either in hardware or in software module units.

The integrated units, if implemented in the form of software module units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Those skilled in the art will appreciate that in one or more of the examples described above, the functions described in the present invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, these functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above embodiments are further described in detail for the purpose, technical solution and advantageous effects of the present invention, and it should be understood that the above description is only an embodiment of the present invention.

The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims

1. A method for transmitting a message, the method comprising:

Determining first application information according to a first application program;

And sending a first message, wherein the first message comprises the first application information, the first message is an internet protocol fourth version IPv4 message, and the first message is associated with the first application program.

2. The method of claim 1, wherein the first application information is carried in any one or more of the following fields of an IPv4 header of the first message:

Flag Flags field, type of service ToS field, identification ID field, and internet protocol option IP option field.

3. The method according to claim 2, wherein the first application information is carried in an ID field and/or an IP option field of an IPv4 header of the first message;

The IPv4 header of the first message further includes first identification information, where the first identification information is used to indicate that an ID field or an IP option field of the IPv4 header of the first message includes the first application information.

4. A method according to claim 3, wherein the first identification information is carried in any one or more of the following fields of an IPv4 header of the first message:

Flag field, toS field, and IP option field.

5. The method according to any of claims 1-4, wherein the first application information is carried in payload information of the first message.

6. The method of claim 5, wherein the payload information of the first message comprises a real-time transport protocol RTP Header, and wherein the first application information is carried in an RTP Header extension field of the RTP Header.

7. A method for transmitting a message, the method comprising:

Acquiring a first message, wherein the first message comprises first application information, the first application information is used for indicating a first application program associated with the first message, and the first message is an internet protocol fourth version IPv4 message;

and forwarding the first message according to the first application information.

8. The method of claim 7, wherein the first application information is carried in any one or more of the following fields of an IPv4 header of the first message:

9. The method according to claim 7, wherein the first application information is carried in an ID field and/or an IP option field of an IPv4 header of the first message;

the method further comprises the steps of:

And determining that the first message comprises the first application information according to first identification information, wherein the first identification information is used for indicating that the first application information is carried in an ID field and/or an IP option field of an IPv4 message header of the first message.

10. The method of claim 9, wherein the first identification information is carried in any one or more of the following fields of an IPv4 header of the first message:

Flag field, toS field, and IP option field.

11. The method according to any of claims 7-10, wherein the first application information is carried in payload information of the first message.

12. The method of claim 11, wherein the payload information of the first message comprises a real-time transport protocol RTP Header, and wherein the first application information is carried in an RTP Header extension field of the RTP Header.

13. The method according to any one of claims 7-12, wherein forwarding the first message according to the first application information comprises:

Generating a second message according to the first message, wherein the load information of the second message is matched with the load information of the first message, the second message is an IPv6 message, and the IPv6 message header of the second message comprises the first application information;

And sending the second message.

14. A message transmission apparatus, the apparatus comprising:

the processing unit is used for determining first application information according to the first application program;

The sending unit is configured to send a first packet, where the first packet includes the first application information, the first packet is an internet protocol fourth version IPv4 packet, and the first packet is associated with the first application program.

15. The apparatus of claim 14, wherein the first application information is carried in any one or more of the following fields of an IPv4 header of the first message:

16. The apparatus of claim 15, wherein the first application information is carried in an ID field and/or an IP option field of an IPv4 header of the first message;

17. The apparatus of claim 16, wherein the first identification information is carried in any one or more of the following fields of an IPv4 header of the first message:

Flag field, toS field, and IP option field.

18. The apparatus according to any of claims 14-17, wherein the first application information is carried in payload information of the first message.

19. The apparatus of claim 18, wherein the payload information of the first message comprises a real-time transport protocol RTP Header, and wherein the first application information is carried in an RTP Header extension field of the RTP Header.

20. A terminal device, characterized in that the terminal device comprises a processor and a memory, the memory being arranged to store instructions or program code, the processor being arranged to call and execute the instructions or program code from the memory to perform the message transmission method according to any of claims 1-6.

21. A network device comprising a processor and a memory, the memory storing instructions or program code, the processor operable to invoke and execute the instructions or program code from the memory to perform the method of message transmission of any of claims 7-13.

22. A network system comprising a terminal device according to claim 20 and a network device according to claim 21.