CN112953843B - Data transmission method and device - Google Patents

Abstract

The embodiment of the application discloses a data transmission method and a device thereof, wherein the method can be applied to a scene supporting local distribution, and comprises the following steps: receiving an uplink data packet from terminal equipment, and determining session information corresponding to the uplink data packet; and under the condition that the session information corresponding to the uplink data packet meets the edge forwarding condition, sending the uplink data packet to an edge gateway. By implementing the embodiment of the application, the data traffic processed by the edge gateway can be reduced.

Description

A data transmission method and device thereof

technical field

The present application relates to the technical field of the Internet, and in particular to a data transmission method and device thereof.

Background technique

The current network is an aggregated network. Under the current network, terminals access data through a centrally deployed gateway. With the development of virtualization technology and distributed cloud technology, future mobile networks will deploy micro-cloud platforms at the edge of the network (for example, near base stations), that is, multi-access edge computing/multi-access edge computing /cloud, MEC) platform.

Taking the network architecture diagram shown in Figure 1a as an example, when the base station side gateway (cell site gateway, CSG)/access service gateway (access gateway, ASG) receives the data sent by the base station, it will send all the data from the base station are sent to the MEC gateway. The MEC gateway judges whether the data needs to be distributed locally based on the distribution rules. If the data needs to be distributed locally, the data is sent to the local network. If the data does not need to be distributed locally, the MEC gateway sends the data to the CSG/ASG, and the CSG/ASG sends the data to the core network for processing. However, this will result in a large amount of data traffic to be processed by the MEC gateway.

Contents of the invention

Embodiments of the present application provide a data transmission method and device thereof, which are beneficial to reducing data traffic processed by an edge gateway.

In the first aspect, an embodiment of the present application provides a data transmission method, the method comprising: receiving an uplink data packet from a terminal device, determining session information corresponding to the uplink data packet; meeting edge forwarding requirements in the session information corresponding to the uplink data packet If the condition is met, the uplink data packet is sent to the edge gateway.

In this technical solution, by sending the uplink data packet to the edge gateway when the session information corresponding to the uplink data packet satisfies the edge forwarding condition, it is beneficial to reduce the data traffic processed by the edge gateway and reduce the load of the edge gateway.

In one implementation, the session information may include a session type, and the edge forwarding condition may include one or more edge forwarding session types; the session information meeting the edge forwarding condition may include that the session type corresponding to the uplink data packet is the same as the edge forwarding session type .

In this technical solution, it is beneficial to reduce the data traffic processed by the edge gateway and reduce the load of the edge gateway.

In one implementation, the session information may include the identifier and session type of the access network device corresponding to the terminal device; the edge forwarding condition may include one or more edge forwarding device identifiers and one or more edge forwarding session types; the session information Satisfying the edge forwarding condition may include: the identifier of the access network device is the same as the edge forwarding device identifier, and the session type corresponding to the uplink data packet is the same as the edge forwarding session type.

In an implementation manner, before sending the uplink data packet to the edge gateway, the method may further include: obtaining the address information of the edge gateway, modifying the destination address information of the uplink data packet to the address information of the edge gateway; A specific implementation manner of sending to the edge gateway may be: sending the uplink data packet to the edge gateway according to the modified destination address information of the uplink data packet.

In this technical solution, by modifying the destination address information of the uplink data packet to the address information of the edge gateway, the uplink data packet can be sent to the edge gateway according to the modified destination address information of the uplink data packet. Therefore, it is beneficial to reduce the data traffic processed by the edge gateway.

In an implementation manner, the address information of the edge gateway may include an Internet Protocol version 6 IPV6 address.

In an implementation manner, the method may further include: when the session information corresponding to the uplink data packet does not satisfy the edge forwarding condition, sending the uplink data packet to a network element of the core network.

In this technical solution, when the session information corresponding to the uplink data packet does not satisfy the edge forwarding condition, the uplink data packet is sent to the network element of the core network, and the data requested by the uplink data packet can be obtained from the core network, To prevent upstream data packets from being unresponsive.

In the second aspect, the embodiment of the present application provides another data transmission method, the method includes: determining that the current tunnel information is different from the historical tunnel information; the tunnel information is the tunnel information between the core network element and the access network device ; Send the downlink data packet corresponding to the tunnel information to the edge gateway.

In this technical solution, when the tunnel information changes, the downlink data packet corresponding to the changed tunnel information is sent to the edge gateway. The edge gateway can determine the current tunnel information according to the information carried in the downlink data packet, and encapsulate and send the downlink data packet from the local server according to the current tunnel information.

In an implementation manner, the method may further include: generating a downlink data packet.

In this technical solution, by generating downlink data packets by itself, it is possible to avoid the situation that there are no downlink data packets from the Internet, resulting in the edge gateway being unable to determine the current tunnel information, thereby helping to improve the return of downlink data packets from the local server to the terminal device. Success rate.

In an implementation manner, the method may further include: receiving a downlink data packet from a core network element.

In an implementation manner, the downlink data packets may be the first n downlink data packets in the downlink data flow; wherein, n may be a positive integer.

In this technical solution, it is beneficial to ensure that the edge gateway can learn the current tunnel information according to the received n downlink data packets, thereby helping to improve the success rate of returning the downlink data packets from the local server to the terminal device.

In an implementation manner, before sending the downlink data packet corresponding to the tunnel information to the edge gateway, the method may further include: obtaining address information of the edge gateway; modifying the destination address information of the downlink data packet to the edge gateway address information ; The specific implementation manner of sending the downlink data packet corresponding to the tunnel information to the edge gateway may be: according to the modified destination address information of the downlink data packet, send the downlink data packet to the edge gateway.

In this technical solution, by modifying the destination address information of the downlink data packet to the address information of the edge gateway, the downlink data packet can be sent to the edge gateway according to the modified destination address information of the downlink data packet. Therefore, it is beneficial to improve the success rate of returning the downlink data packets from the local server to the terminal device.

In an implementation manner, the address information of the edge gateway may include an Internet Protocol version 6 IPV6 address.

In an implementation manner, the method may further include: determining session information corresponding to the tunnel information; and triggering the step of sending the downlink data packet corresponding to the tunnel information to the edge gateway when the session information satisfies the edge forwarding condition.

In this technical solution, when the session information corresponding to the tunnel information satisfies the edge forwarding condition, the downlink data packet corresponding to the tunnel information is sent to the edge gateway. Return to the terminal device; on the other hand, it can avoid the situation that the downlink data packet corresponding to the tunnel information is sent to the edge gateway when the session information corresponding to the tunnel information does not meet the edge forwarding conditions, which is beneficial to reduce the data processed by the edge gateway flow.

In a third aspect, the embodiment of the present application provides a data transmission device, which is a first network device or a device (such as a chip) having a function of the first network device. The device has the function of realizing the data transmission method provided by the first aspect, and the function is realized by hardware or by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a fourth aspect, the embodiment of the present application provides another data transmission device, which is a second network device or a device (such as a chip) having the function of the second network device. The device has the function of realizing the data transmission method provided by the second aspect, and the function is realized by hardware or by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a fifth aspect, the embodiment of the present application provides yet another data transmission device, which is a first network device or a device (such as a chip) having the function of the first network device. The device includes a processor and a storage medium, and instructions are stored in the storage medium, and when the instructions are executed by the processor, the device implements the data transmission method provided in the first aspect.

In the sixth aspect, the embodiment of the present application provides yet another data transmission device, the device is a second network device or a device (such as a chip) having the function of the second network device, the device includes a processor and a storage medium, and the storage medium stores There are instructions, and when the instructions are executed by the processor, the device realizes the data transmission method provided by the second aspect.

In the seventh aspect, the embodiment of the present application provides a data transmission system, the data transmission system includes the data transmission device described in the third aspect and the data transmission device described in the fourth aspect, or, the data transmission system includes the fifth aspect The data transmission device described in the sixth aspect and the data transmission device described in the sixth aspect.

In the eighth aspect, the embodiment of the present application provides a computer-readable storage medium, which is used to store the computer program instructions used by the data transmission device described in the third aspect above, which includes instructions for performing the method involved in the first aspect above. program.

In the ninth aspect, the embodiment of the present application provides a computer-readable storage medium, which is used to store the computer program instructions used by the data transmission device described in the fourth aspect above, which includes instructions for performing the method involved in the second aspect above program.

In a tenth aspect, an embodiment of the present application provides a computer program product, the program product includes a program, and when the program is executed by a data transmission device, the device implements the method described in the first aspect above.

In an eleventh aspect, an embodiment of the present application provides a computer program product, the program product includes a program, and when the program is executed by a data transmission device, the device implements the method described in the second aspect above.

Description of drawings

Figure 1a is an existing network architecture diagram;

Fig. 1b is a schematic structural diagram of a communication system disclosed in an embodiment of the present application;

FIG. 2 is a schematic flowchart of a data transmission method disclosed in an embodiment of the present application;

Fig. 3a is a schematic flowchart of another data transmission method disclosed in the embodiment of the present application;

Fig. 3b is a schematic diagram of an SRH extension header in an IPv6 data packet header disclosed in an embodiment of the present application;

FIG. 4 is a schematic flowchart of another data transmission method disclosed in the embodiment of the present application;

FIG. 5 is a schematic flowchart of another data transmission method disclosed in the embodiment of the present application;

Fig. 6a is a schematic diagram of a network architecture in which the control plane and the forwarding plane are separated according to the embodiment of the present application;

Fig. 6b is a schematic diagram of a network architecture in which the control plane and the forwarding plane are integrated disclosed in the embodiment of the present application;

FIG. 6c is a schematic diagram of a network architecture of a 5G independent networking disclosed in the embodiment of the present application;

FIG. 7 is a schematic structural diagram of a data transmission device disclosed in an embodiment of the present application;

Fig. 8 is a schematic structural diagram of another data transmission device disclosed in the embodiment of the present application;

FIG. 9 is a schematic structural diagram of another data transmission device disclosed in the embodiment of the present application;

Fig. 10 is a schematic structural diagram of another data transmission device disclosed in the embodiment of the present application.

detailed description

In order to better understand a data transmission method disclosed in the embodiment of the present application, the communication system to which the embodiment of the present application applies is firstly described below.

Please refer to FIG. 1b. FIG. 1b is a schematic structural diagram of a communication system disclosed in an embodiment of the present application. As shown in Fig. 1b, the communication system includes: a first network device and an edge gateway.

The first network device may receive the uplink data packet from the terminal device, determine the session information corresponding to the uplink data packet, and send the uplink data packet to the edge gateway when the session information satisfies the edge forwarding condition. In this way, it is beneficial to reduce the data traffic processed by the edge gateway and reduce the load of the edge gateway. In the embodiment of the present application, the session information corresponding to the uplink data packet satisfying the edge forwarding condition may indicate that the uplink data packet is used to access local services. The edge gateway can receive the uplink data packet and send the uplink data packet to the local network. Relevant data of local services may be stored in the local network. Sending uplink data packets for accessing local services to the local network is beneficial to improving the success rate of users accessing local services.

Wherein, the first network device may be an entity on the network side for transmitting or receiving signals, for example, the first network device may be an access network device (such as a base station). In an implementation manner, the first network device may also be a device located behind the base station (not shown in FIG. 1b ) in the uplink direction. For example, the first network device may be located between the base station and the edge gateway, and the first network device has the following functions: receiving an uplink data packet sent by the base station (the uplink data packet comes from a terminal device), and determining the session corresponding to the uplink data packet information, and when the session information satisfies the edge forwarding condition, send the uplink data packet to the edge gateway.

The edge gateway can send the received uplink data packet to the local network. Specifically, the edge gateway may be a multi-access edge computing/multi-access edge computing/cloud (multi-access edge computing/cloud, MEC) gateway, or other network elements that have the above-mentioned functions of the edge gateway.

It can be understood that the communication system described in the embodiment of the present application is to illustrate the technical solutions of the embodiments of the present application more clearly, and does not constitute a limitation to the technical solutions provided in the embodiments of the present application. Those skilled in the art know that with the system For the evolution of architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

The data transmission method and data transmission device provided by the present application will be described in detail below with reference to the accompanying drawings.

Please refer to FIG. 2 . FIG. 2 is a schematic flowchart of a data transmission method provided by an embodiment of the present application. The method details how to reduce the data traffic handled by the edge gateway in the upstream direction. Wherein, the execution subject of steps S201 to S203 is the first network device, or a chip in the first network device, and the execution subject of step S204 is the edge gateway, or a chip in the edge gateway. Hereinafter, the first network device, The edge gateway is used as an execution body of the data transmission method as an example for illustration. As shown in Figure 2, the method may include but not limited to the following steps:

Step S201: the first network device receives an uplink data packet from a terminal device.

Specifically, when the first network device is a base station, after the terminal device generates the uplink data packet, it may send the uplink data packet to the first network device. When the first network device is a device located behind the base station in the uplink direction, the terminal device can send the uplink data packet to the base station where the terminal device is currently camping, and then the base station where the terminal device is currently camping sends the uplink data packet The packet is sent to the first network device.

The terminal device may be an entity on the user side for receiving or transmitting signals. Specifically, the terminal device may be a user equipment (user equipment, UE), a remote terminal, a mobile terminal, a wireless communication device, a user device, and the like. Wherein, the user equipment may be a mobile phone, a desktop computer, a notebook computer, or other wearable devices.

Step S202: the first network device determines session information corresponding to the uplink data packet.

Specifically, the first network device may determine the session information corresponding to the uplink data packet according to the first information carried in the uplink data packet. Then judge whether the session information satisfies the edge forwarding condition, and if the session information satisfies the edge forwarding condition, send the uplink data packet to the edge gateway.

In an implementation manner, the first information may be a source internet protocol (internet protocol, IP) address carried in the uplink data packet. The session to which the uplink data packet belongs can be determined through the source IP address. The first network device may determine the session identifier corresponding to the source IP address carried in the uplink data packet as the session identifier corresponding to the uplink data packet according to the pre-stored correspondence between the source IP address and the session identifier. The session indicated by the session identifier corresponding to the uplink data packet is the session to which the uplink data packet belongs. Further, the first network device may determine session information of the session to which the uplink data packet belongs.

In an implementation manner, when the first network device is a base station, the first network device may store session information corresponding to terminals residing under the first network device (that is, the base station). When the first network device is a device located behind the first base station in the uplink direction, the first network device may store session information corresponding to terminals residing under the first base station. Or, the session information corresponding to the terminals camped on the first base station is stored in the first base station. After the first base station determines the session information corresponding to the foregoing uplink data packet, it may send the uplink data packet and the corresponding session information to the first network device. So that the first network device sends the uplink data packet to the edge gateway when the session information satisfies the edge forwarding condition. Wherein, the number of the first base station may be one or more.

It should be noted that each terminal can correspond to one or more sessions, and each terminal can correspond to one or more source IP addresses. The source IP addresses of data packets belonging to different sessions are different, and the source IP addresses of data packets belonging to the same session The address is the same. Specifically, the session mentioned in the embodiment of the present application may be a protocol data unit (packet data unit, PDU) session in the fifth-generation mobile communication technology (fifth-generation, 5G), or a session in the next-generation network, This embodiment of the present application does not limit it.

Step S203: the first network device sends the uplink data packet to the edge gateway when the session information satisfies the edge forwarding condition.

In an implementation manner, the session information may include a session type, sessions of different session types may be used to transmit different types of data, and sessions of the same session type may be used to transmit the same type of data. For example, when a terminal requests to obtain video application data and instant messaging application data, the network may allocate session resources for transmitting video application data and session resources for transmitting instant messaging application data to the terminal respectively. In other words, the type of service requested by the uplink data packet can be determined according to the session type corresponding to the uplink data packet.

In an implementation manner, the edge forwarding condition may include one or more edge forwarding session types. If the session type corresponding to the aforementioned uplink data packet is the same as any one of the one or more edge forwarding session types, then it is determined that the session information corresponding to the uplink data packet satisfies the edge forwarding condition, and the uplink data packet is sent to edge gateway. In this way, it is beneficial to reduce the data traffic processed by the edge gateway and reduce the load of the edge gateway.

In an implementation manner, for the signaling plane data packets that do not require local distribution, the session type is not the edge forwarding session type. For data packets of long-term evolution voice bearer (voice over long-termevolution, VoLTE) services or other instant communication services that do not require local offloading, the session type is not the edge forwarding session type. In this manner, it is possible to avoid sending service flows that do not require local distribution to the edge gateway for processing, thereby helping to reduce data traffic processed by the edge gateway.

In the embodiment of the present application, if the session type corresponding to the uplink data packet is an edge forwarding session type, it may indicate that the service data requested by the uplink data packet is stored in the local network. Compared with sending the uplink data packet to the core network to obtain the data requested by the uplink data packet, by sending the uplink data packet to the local network to obtain the data requested by the uplink data packet, the transmission of the uplink data packet in the latter The path is shorter. Therefore, compared with the core network, by sending the uplink data packet to the local network to obtain the data requested by the uplink data packet, it is beneficial to improve the efficiency of obtaining the data requested by the uplink data packet, and it is also beneficial to reduce the data flow through the core network. data traffic.

In an implementation manner, the session information may include a session type and an identifier of an access network device (such as a base station) corresponding to the aforementioned terminal device. The edge forwarding condition may include one or more edge forwarding device identifiers and one or more edge forwarding session types. If the identifier of the access network device is the same as any one of the one or more edge forwarding device identifiers, and the session type corresponding to the aforementioned uplink data packet is the same as any one of the above one or more edge forwarding session types, Then the first network device may determine that the session information corresponding to the uplink data packet satisfies the edge forwarding condition. Wherein, the access network device corresponding to the terminal device may be the base station where the terminal device currently resides.

In actual situations, operators can determine whether to deploy a local network based on the location of the base station, the number of users connected to the base station, and other reasons. And the number of base stations that can be served by a local network is limited. In other words, not any base station can send the uplink data packet to the edge gateway after receiving the uplink data packet, and then obtain the data requested by the uplink data packet from the local network corresponding to the edge gateway.

In one implementation, the user can configure the service area of the edge gateway on the first network device, or the user can configure the service area of the edge gateway on the preset network device, and then the preset network device sends the first network The device sends an indication message to indicate the service area of the edge gateway. In an implementation manner, the service area of the edge gateway may be indicated by an edge forwarding device identifier, and the edge forwarding device identifier may be an access network device identifier (such as a base station identifier). The coverage area of the base station indicated by the edge forwarding device identifier may represent the service area of the edge gateway. Only when the base station identifier is the edge forwarding device identifier, can the uplink data packet received by the base station be sent to the edge gateway, and the data requested by the uplink data packet can be obtained from the local network corresponding to the edge gateway.

When the first network device receives the uplink data packet from the terminal device, and the identifier of the access network device corresponding to the terminal device is an edge forwarding device identifier, it may indicate that the access network device is located in the service area of the edge gateway. Correspondingly, the first network device may determine whether the session type corresponding to the uplink data packet is an edge forwarding session type, and if the session type is an edge forwarding session type, send the uplink data packet to the edge gateway. When the first network device receives the uplink data packet from the terminal device, and the identifier of the access network device corresponding to the terminal device is not an edge forwarding device identifier, it may indicate that the access network device is located outside the service area of the edge gateway. Correspondingly, the first network device may send the uplink data packet to a core network element.

In this way, when the identification of the access network device corresponding to the terminal device is not the identification of the edge forwarding device, that is, when the access network device is located outside the service area of the edge gateway, the uplink data packet from the terminal device can be avoided sent to the edge gateway. Since the access network device is located outside the service area of the edge gateway, even if the uplink data packet from the terminal device is sent to the edge gateway, the data requested by the uplink data packet cannot be obtained from the local network corresponding to the edge gateway . This is beneficial to avoid that the uplink data packet from the terminal device cannot be responded.

In an implementation manner, the first network device may set the edge forwarding condition by default, or set and change the edge forwarding condition according to a user operation.

In an implementation manner, when the session information corresponding to the uplink data packet does not satisfy the edge forwarding condition, the first network device may send the uplink data packet to a network element of the core network. In this way, the data requested by the uplink data packet can be obtained from the core network, preventing the uplink data packet from being unresponsive.

Step S204: the edge gateway sends the uplink data packet to the local server.

Specifically, after the edge gateway receives the uplink data packet, it can strip the general packet radio service tunneling protocol-user plane (GTPU) header of the general packet radio service (GPRS) tunneling protocol-user plane, and then send the stripped uplink data packet to to the local server. In order to obtain the data requested by the uplink data packet from the local server (that is, the local network).

In the embodiment of the present application, by sending the uplink data packet to the edge gateway when the session information corresponding to the uplink data packet satisfies the edge forwarding condition, it is beneficial to reduce the data traffic processed by the edge gateway and reduce the load of the edge gateway.

Please refer to Fig. 3a, Fig. 3a is a schematic flowchart of another data transmission method provided by the embodiment of the present application, which describes in detail how the first network device modifies the address information of the uplink data packet so that the uplink data packet can pass through the edge gateway. Wherein, the execution subject of steps S301 to S305 is the first network device, or the chip in the first network device, and the execution subject of step S306 is the edge gateway, or the chip in the edge gateway. Hereinafter, the first network device, The edge gateway is used as an execution body of the data transmission method as an example for illustration. The method may include, but is not limited to, the following steps:

Step S301: the first network device receives an uplink data packet from a terminal device.

Step S302: the first network device determines session information corresponding to the uplink data packet.

It should be noted that, for the execution process of step S301 to step S302, refer to the specific description of step S201 to step S202 in FIG. 2 respectively, which will not be repeated here.

Step S303: the first network device obtains the address information of the edge gateway when the session information satisfies the edge forwarding condition.

Specifically, when the session information corresponding to the uplink data packet satisfies the edge forwarding condition, the first network device can obtain the address information of the edge gateway and the address information of the uplink data packet, and then forward the uplink data according to the address information of the edge gateway. The address information of the packet is modified so that the uplink data packet can pass through the edge gateway.

Step S304: the first network device modifies the destination address information of the uplink data packet to the address information of the edge gateway.

In an implementation manner, the address information of the uplink data packet may include destination address information. If the destination address information of the uplink data packet is the same as the address information of the edge gateway, it indicates that the uplink data packet originally passes through the edge gateway. At this time, the first network device may not change the address information of the uplink data packet. If the destination address information of the uplink data packet is different from the address information of the edge gateway, the first network device may modify the destination address information of the uplink data packet to the address information of the edge gateway.

Wherein, the uplink data packet may be an Internet protocol version 4 (internet protocol version 4, IPv4) data packet or an Internet protocol version 6 (internet protocol version 6, IPv6) data packet. Correspondingly, the address information in this embodiment of the present application may include an IPv4 address or an IPv6 address.

In an implementation manner, when the uplink data packet is an IPv6 data packet, the header of the uplink data packet may include an IPv6 standard header and a segment routing header (segment routing header, SRH). When the IPv6 data packet is sent to the destination address, the SRH extension header can be used to specify the address of the intermediate node that must pass through.

Take the schematic diagram of the SRH extension header in the IPv6 data packet header shown in FIG. 3 b as an example. In Fig. 3b, the meanings of each field in the SRH extension header are as follows: Next Header: used to identify the type of the header immediately following the SRH. Hdr ExtLen: The length of the SRH extension header. Hdr Ext Len mainly refers to the length occupied from Segment List[0] to Segment List[n]. Routing Type: identifies the routing header type. Segments Left: The number of intermediate nodes that should still be visited before reaching the destination node. Last Entry: Contains the index of the last element of the segment list in the segment list. Flags: Some identifiers of the data packet. Tag: identifies the same group of data packets. Segment List[n]: Label segment list, the segment list starts encoding from the last segment of the path. The Segment List is in the form of an IPv6 address. Segment List[n] can be expressed as SL[n].

The process of specifying the address of the intermediate node that must pass through the SRH extension header is as follows: For example, when an IPv6 data packet sent from the source address E1::1 to the destination address A3::1 must pass through the address A2::1 on the way, if the When the data packet is sent from the source address, the destination address of the data packet is A2::1, and the data packet carries the extension header. If SL[0]=A3::1, SL[1]=A2::1, and Segments Left=1 in the extension header, after the data packet reaches A2::1, the intermediate routing device can update the destination address to A3::1, and update the Segments Left in the extension header to 0. Then continue to query the route and send it to the destination address A3::1.

In this embodiment of the present application, when the uplink data packet is an IPv6 data packet, and the header of the uplink data packet includes an SRH extension header, the first network device may modify the destination address of the uplink data packet to the IPv6 address of the edge gateway. Optionally, the Segments Left in the SRH extension header may also be updated to 0.

Step S305: the first network device sends the uplink data packet to the edge gateway according to the modified destination address information of the uplink data packet.

Specifically, the first network device may query a routing table according to the modified destination address information of the uplink data packet, so as to send the uplink data packet to the edge gateway.

Step S306: the edge gateway sends the uplink data packet to the local server.

It should be noted that, for the execution process of step S306, reference may be made to the specific description of step S204 in FIG. 2 , which will not be repeated here.

In the embodiment of the present application, by modifying the destination address information of the uplink data packet to the address information of the edge gateway, the uplink data packet can be sent to the edge gateway according to the modified destination address information of the uplink data packet. Therefore, it is beneficial to reduce the data traffic processed by the edge gateway.

Please refer to FIG. 4 . FIG. 4 is a schematic flowchart of another data transmission method provided by an embodiment of the present application. The method describes in detail how to reduce the data traffic processed by the edge gateway in the downlink direction. Wherein, steps S401 to S402 are executed by the second network device, or a chip in the second network device, and the following takes the second network device as the execution body of the data transmission method as an example for illustration. The method may include, but is not limited to, the following steps:

Step S401: the second network device determines that current tunnel information is different from historical tunnel information; the tunnel information is tunnel information between a core network element and an access network device.

Wherein, the second network device may be a network element of the core network, a gateway of the core network, or a device before the edge gateway in the downlink direction. The downlink data packet can be returned to the terminal device smoothly through the tunnel information. The tunnel in this embodiment of the present application may refer to a GTPU tunnel or other network tunnels. The tunnel information of the GTPU tunnel may include but not limited to: an identifier of an access network device and a tunnel endpoint identifier (tunnel endpoint identifier, TEID). Therefore, when the access network device accessed by the terminal device changes, and/or the TEID changes, the tunnel information will change. The TEID may include the TEID of the user plane (TEIDU for short) and the TEID of the control plane (TEIDC for short). The tunnel corresponding to the TEIDU can be used to transmit user plane data, and the tunnel corresponding to the TEIDC can be used to transmit control plane data.

In one implementation, tunnel information of all GTPU tunnels may be stored in the core network, and when any tunnel information changes, the core network may send a first message to the second network device, and the first message may indicate The current tunnel information is different from the historical tunnel information. In one implementation, both the core network and the second network device can store tunnel information of all GTPU tunnels, and when any tunnel information changes, the core network can send a second message to the second network device, the The second message may carry current tunnel information. After receiving the second message, the second network device may determine that the tunnel information has changed by comparing historical tunnel information with current tunnel information.

Step S402: the second network device sends the downlink data packet corresponding to the tunnel information to the edge gateway.

In the embodiment of this application, when the tunnel information changes, the edge gateway cannot know the tunnel information after the change (that is, the current tunnel information), so when the edge gateway receives the downlink data packet from the local server, it still follows the historical The downlink data packet is sent with the tunnel information, which will cause the downlink data packet to fail to return to the correct terminal device.

Specifically, when the tunnel information changes, the second network device may send the downlink data packet corresponding to the changed tunnel information to the edge gateway. After receiving the downlink data packet, the edge gateway can determine the current tunnel information according to the information carried in the downlink data packet, then encapsulate the downlink data packet from the local server according to the current tunnel information, and send the encapsulated downlink data packet. In this way, it is beneficial to improve the success rate of returning the downlink data packets from the local server to the terminal device.

In the embodiment of the present application, when the tunnel information changes, the downlink data packet corresponding to the tunnel information is sent to the edge gateway, which can avoid sending the downlink data packet from the core network to the edge gateway when the tunnel information has not changed. edge gateway. In this way, it is beneficial to reduce the data traffic processed by the edge gateway and reduce the load of the edge gateway.

In one implementation, when the tunnel information changes, the second network device sends the downlink data packet corresponding to the tunnel information to the edge gateway, which may come from a network element of the core network, or the downlink data packet may be sent by the second network device Generated by yourself.

Since the edge gateway cannot know the changed tunnel information (that is, the current tunnel information) when the tunnel information changes, if the downlink data packet corresponding to the changed tunnel information does not come from the core network (or the Internet), then the first The second network device cannot send downlink data packets from the core network (or the Internet) to the edge gateway. Correspondingly, the edge gateway cannot learn the current tunnel information, which will cause the downlink data packets from the local server (that is, the local network) to fail to return to the terminal device correctly. At this time, the second network device can avoid the situation that there is no downlink data packet from the Internet by creating the downlink data packet by itself, resulting in the edge gateway being unable to determine the current tunnel information, which is beneficial to improve the return of the downlink data packet from the local server to the terminal device. success rate.

In the embodiment of the present application, after determining that the tunnel information has changed, the second network device generates a downlink data packet corresponding to the tunnel information, and sends the downlink data packet to the edge gateway. The edge gateway can determine the current tunnel information according to the information carried in the downlink data packet. In this way, when the edge gateway receives the downlink data packet from the local server, it can encapsulate and send the downlink data packet from the local server more timely according to the current tunnel information.

In an implementation manner, after the second network device determines that the tunnel information has changed, if the downlink data packet corresponding to the tunnel information is not received, the second network device may obtain the current tunnel information, and create a tunnel according to the current tunnel information. The downlink data packet corresponding to the tunnel information. The downlink data packet created in this way carries address information that can be correctly returned to the terminal.

In an implementation manner, before the second network device sends the downlink data packet corresponding to the tunnel information to the edge gateway, it may also determine the session information corresponding to the tunnel information; when the session information satisfies the edge forwarding condition, trigger Execute the step of sending the downlink data packet corresponding to the tunnel information to the edge gateway.

Specifically, when the session information corresponding to the tunnel information satisfies the edge forwarding condition, there is a high probability that the downlink data packet corresponding to the changed tunnel information will be returned from the local network, or the edge gateway will receive the changed The downlink data packet (from the local network) corresponding to the tunnel information. In this case, sending the downlink data packet (from the core network or the Internet) corresponding to the changed tunnel information to the edge gateway is beneficial for the edge gateway to determine the current tunnel information, so that the downlink data packet returned from the local network can correctly returns the terminal device. It should be noted that, for the session information and the edge forwarding conditions, refer to the descriptions in the embodiments of FIG. 2 to FIG. 3 a , and details are not repeated here.

In an implementation manner, if all the uplink data packets from the first terminal device are sent to the core network, but not to the local network. Then there will be no downlink data packet corresponding to the uplink data packet returned from the local network. Since the data packet returned from the core network can be correctly returned to the first terminal device without being forwarded to the edge gateway, in this case, the downlink data packet may not be sent to the edge gateway.

When the session information corresponding to the tunnel information satisfies the edge forwarding condition, the downlink data packet corresponding to the tunnel information is sent to the edge gateway. On the one hand, it is beneficial for the downlink data packet returned from the local network to return to the terminal device correctly; on the other hand On the one hand, it can avoid the situation that the downlink data packet corresponding to the tunnel information is sent to the edge gateway when the session information corresponding to the tunnel information does not meet the edge forwarding condition, which is beneficial to reduce the data flow processed by the edge gateway.

By implementing the embodiments of the present application, it is beneficial to improve the success rate of returning the downlink data packets from the local server to the terminal device.

Please refer to FIG. 5. FIG. 5 is a schematic flowchart of another data transmission method provided by the embodiment of the present application. This method describes in detail how the second network device modifies the address information of the downlink data packet so that the downlink data packet can pass through the edge gateway. Wherein, the executing subject of steps S501 to S505 is the second network device, or a chip in the second network device, and the following takes the second network device as the executing subject of the data transmission method as an example for illustration. The method may include, but is not limited to, the following steps:

Step S501: the second network device receives a downlink data packet from a core network element.

Step S502: the second network device determines that the current tunnel information is different from the historical tunnel information; the tunnel information is the tunnel information between the core network element and the access network device.

It should be noted that, for the execution process of step S501 to step S502, refer to the specific description of step S401 to step S402 in FIG. 4 , which will not be repeated here.

Step S503: the second network device obtains the address information of the edge gateway.

Step S504: the second network device modifies the destination address information of the downlink data packet to the address information of the edge gateway.

In an implementation manner, the address information of the edge gateway may be an IPV4 address or an IPV6 address.

Step S505: the second network device sends the downlink data packet to the edge gateway according to the modified destination address information of the downlink data packet.

In an implementation manner, the downlink data packets corresponding to the changed tunnel information may be the first n downlink data packets in the downlink data flow. In other words, when the second network device determines that the tunnel information corresponding to the received downlink data packets changes, it may send the first n downlink data packets received to the edge gateway. This is beneficial to ensure that the edge gateway can learn the current tunnel information according to the received n downlink data packets, thereby helping to improve the success rate of returning the downlink data packets from the local server to the terminal device. Wherein, n may be greater than or equal to 1. In an implementation manner, the larger n is, the better it can be ensured that the edge gateway can learn the current tunnel information according to the received n downlink data packets. In an implementation manner, the second network device may send the first n downlink data packets received first to the edge gateway according to the order of receipt. Alternatively, the second network device may send the first n downlink data packets with smaller transmission control protocol (transmission control protocol, TCP) sequence numbers in the downlink data stream to the edge gateway. Wherein, the TCP sequence number is the sequence number in the TCP header, and the sequence number is used to identify the position of the downlink data packet in the downstream data flow to which it belongs.

In an implementation manner, when the second network device determines that the tunnel information corresponding to the received downlink data packets has changed, after sending the first n downlink data packets to the edge gateway, for the subsequent received downlink data packets , can be returned to the terminal device according to the address information carried in the downlink data packet itself. This can prevent the edge gateway from continuing to send downlink data packets to the edge gateway under the condition that the edge gateway has successfully learned the current tunnel information. It can also reduce the data traffic processed by the edge gateway. On the other hand, the downlink data packet is returned to the terminal device according to the address information carried by itself, which can avoid prolonging the path that the downlink data packet passes before returning to the terminal device.

It should be noted that the execution process of the second network device modifying the destination address information of the downlink data packet according to the address information of the edge gateway is the same as the execution process of the first network device modifying the destination address information of the uplink data packet according to the address information of the edge gateway . That is, the execution process of step S503 to step S505 may refer to the specific description of step S303 to step S305 in FIG. 3 a , which will not be repeated here.

In the embodiment of the present application, by modifying the destination address information of the downlink data packet to the address information of the edge gateway, the downlink data packet can be sent to the edge gateway according to the modified destination address information of the downlink data packet, thereby effectively It is beneficial to improve the success rate of returning the downlink data packets from the local server to the terminal device.

The data transmission method described in the foregoing embodiments in FIGS. 2-5 can be applied to different network architectures, for example, the 4th generation mobile communication technology (the 4th generation mobile communication technology, 4G) long term evolution (long term evolution, LTE) Core network, 5G core network (5G core network, 5GC) or network architecture of other networks. The core network of LTE is an evolved packet core network (evolved packet core network, EPC) or EPC+. The EPC+ network can support both 4G and 5G non-stand alone (NSA). Wherein, the EPC network (or EPC+ network) may be a network architecture in which the control plane and a forwarding plane (control plane and user plane, CU) are separated or a network architecture in which the CU is integrated.

The EPC network (or EPC+ network) may include but not limited to the following network elements: mobility management entity (mobility management entity, MME), serving gateway (serving gateway, SGW) and packet data network gateway (packetdata network gateway, PGW). The 5GC network may include but not limited to the following network elements: user plane function (userplane function, UPF), service management function (service management function, SMF) and access management function (access management function, AMF). Under the network architecture where CU is separated, SGW can be divided into serving gateway for user plane (SGW-U) and serving gateway for control plane (SGW-C), and PGW can be divided into user plane grouping A data network gateway (packet data network gateway for user plane, PGW-U) and a control plane packet data network gateway (packet data network gateway for control plane, PGW-C).

In the following, description will be made exemplarily by taking the foregoing data transmission methods respectively applied to the network architectures shown in FIG. 6a , FIG. 6b , and FIG. 6c .

In the network architecture in which CUs are separated as shown in FIG. 6a , base station a and base station b are configured to perform corresponding functions of the first network device in the methods described in FIGS. 2-3a. The SGW-U is configured to execute the corresponding functions of the second network device in the methods described in FIGS. 4-5 . Both base station a and base station b are located in the service area of the edge gateway, that is, the edge forwarding device identifier includes at least the identifier of base station a and the identifier of base station b. Data packet 1 is an uplink data packet, and data packet 2 and data packet 3 are both downlink data packets.

1) In the uplink direction: As can be seen from Figure 6a, terminal a can send data packet 1 to base station a, and after receiving data packet 1, the base station can determine the session information corresponding to data packet 1 (such as the session type corresponding to terminal a base station (ie, the identity of base station a)). Since the edge forwarding device identifier includes the identifier of base station a, if the session type of the data packet 1 is the edge forwarding session type, it can be determined that the session information corresponding to the data packet 1 satisfies the edge forwarding condition. Further, base station a may send the data packet 1 to the edge gateway. After receiving the data packet 1, the edge gateway can strip the GTPU header of the data packet 1, and send the data packet 1 with the GTPU header stripped to the local network.

Specifically, base station a may send the data packet 1 to the edge gateway by modifying the destination address of the data packet 1 to the IPv6 address of the edge gateway. In the network architecture shown in Fig. 6a, the IPv6 address of the edge gateway may be sent by the MME to the base station a. In one implementation, when terminal a is activated in base station a (for example, powered on), or terminal a moves from outside the coverage area of base station a to within the coverage area of base station a, SGW-C can use extended information elements to Send the information carrying the IPv6 address of the edge gateway to the MME. In other words, when terminal a is activated in the service area of the edge gateway, or when terminal a moves from outside the service area of the edge gateway to the service area of the edge gateway, SGW-C can send information carrying the IPv6 address of the edge gateway to MME .

2) In the downlink direction: As can be seen from Figure 6a, when terminal a moves from the coverage area of base station a to the coverage area of base station b, SGW-C can send the current tunnel information to SGW-U. When the SGW-U receives the current tunnel information, it may determine that the tunnel information changes. Then, SGW-U can generate data packet 2 according to the current tunnel information, and send data packet 2 to the edge gateway. After the edge gateway receives the data packet 2, it can extract the address information carried in the data packet 2 and learn the current tunnel information. Wherein, the tunnel corresponding to the tunnel information may be used to transmit the downlink data packet corresponding to the data packet 1 (that is, the data packet 3 in FIG. 6a ). When the edge gateway receives the data packet 3 from the local network, it can correctly send the data packet 3 to the base station b according to the learned current tunnel information, so that the terminal a can successfully obtain the downlink data packet corresponding to the data packet 1 ( That is packet 3).

It should be noted that the SGW-U can generate n data packets 3 and send all n data packets 3 to the edge gateway, so as to ensure that the edge gateway can successfully learn the current tunnel information. It should also be noted that FIG. 6a is illustrated by taking no data packets from the Internet as an example, which does not constitute a limitation to the embodiment of the present application. If there are data packets from the Internet, the SGW-U may send the first n data packets from the Internet to the edge gateway. It should be noted that the data packets from the Internet can reach the SGW-U via the PGW-U. Wherein, PGW is a border gateway of the EPC network, PGW-U can be used to process user plane data, and PGW-C can be used to process control plane data.

In the CU-in-one network architecture shown in Figure 6b, except that the IPv6 address of the edge gateway is sent to the MME by the SGW, the current tunnel information is determined by the SGW itself, and the SGW is configured to perform the second Except for the corresponding functions of the network equipment, the functions of other network elements are consistent with those in FIG. 6a. I won't repeat them here.

In the 5G standalone (SA) network architecture shown in FIG. 6c, the functions of each network element in FIG. 6c are basically the same as those in FIG. 6a. The differences are as follows: first, the UPF or the SGW-U is configured to execute the corresponding functions of the second network device in the methods shown in FIGS. 4-5 . Second, the SMF sends the IPv6 address of the edge gateway to the AMF, and the AMF sends the IPv6 address of the edge gateway to the base station a. Alternatively, the IPv6 address of the edge gateway may be sent to base station a by the MME. Third, the current tunnel information is notified to the UPF by the SMF, or the current tunnel information is sent to the SGW-U by the SGW-C.

The method disclosed in the embodiment of the present application has been described in detail above, and the device in the embodiment of the present application will be provided below.

Please refer to FIG. 7. FIG. 7 is a schematic structural diagram of a data transmission device provided by an embodiment of the present application. The device may be a first network device or a device (such as a chip) having the function of a first network device. In executing the steps performed by the first network device in the method embodiment corresponding to FIG. 2-FIG. 3a, the data transmission device 70 includes:

A communication module 701, configured to receive an uplink data packet from a terminal device;

A processing module 702, configured to determine session information corresponding to the uplink data packet;

The communication module 701 is further configured to send the uplink data packet to the edge gateway when the session information corresponding to the uplink data packet satisfies the edge forwarding condition.

In one implementation, the session information may include a session type, and the edge forwarding condition may include one or more edge forwarding session types; the session information meeting the edge forwarding condition may include that the session type corresponding to the uplink data packet is the same as the edge forwarding session type .

In one implementation, the session information may include the identifier and session type of the access network device corresponding to the terminal device; the edge forwarding condition may include one or more edge forwarding device identifiers and one or more edge forwarding session types; the session information Satisfying the edge forwarding condition may include: the identifier of the access network device is the same as the edge forwarding device identifier, and the session type corresponding to the uplink data packet is the same as the edge forwarding session type.

In one implementation, the communication module 701 can also be used to obtain the address information of the edge gateway; the processing module 702 can also be used to modify the destination address information of the uplink data packet to the address information of the edge gateway; When the uplink data packet is sent to the edge gateway, it may specifically be used to send the uplink data packet to the edge gateway according to the modified destination address information of the uplink data packet.

In an implementation manner, the address information of the edge gateway may include an Internet Protocol version 6 IPV6 address.

In an implementation manner, the communication module 701 may also be configured to send the uplink data packet to a network element of the core network when the session information corresponding to the uplink data packet does not satisfy the edge forwarding condition.

It should be noted that for the content not mentioned in the embodiment corresponding to FIG. 7 and the specific implementation manners of the execution steps of each module, refer to the embodiment shown in FIGS. 2-3a and the foregoing content, and details are not repeated here.

In an implementation manner, related functions implemented by each module in FIG. 7 may be implemented in combination with a processor and a communication interface. Referring to FIG. 8, FIG. 8 is a schematic structural diagram of another data transmission device provided by an embodiment of the present application. The device may be a first network device or a device (such as a chip) having the function of a first network device. The data transmission device 80 It may include a communication interface 801, a processor 802, and a memory 803, and the communication interface 801, the processor 802, and the memory 803 may be connected to each other through one or more communication buses, or may be connected in other ways. Related functions implemented by the communication module 701 and the processing module 702 shown in FIG. 7 may be implemented by the same processor 802 , or may be implemented by multiple different processors 802 .

The communication interface 801 may be used to send data and/or signaling, and to receive data and/or signaling. Applied in the embodiment of the present application, the communication interface 801 may be used to receive an uplink data packet from a terminal device, and the communication interface 801 may be a transceiver.

The processor 802 is configured to execute corresponding functions of the first network device in the methods described in FIG. 2-FIG. 3a. The processor 802 may include one or more processors, for example, the processor 802 may be one or more central processing units (central processing unit, CPU), network processor (network processor, NP), hardware chip or any other combination. In the case that the processor 802 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

The memory 803 is used to store program codes and the like. The memory 803 may include a volatile memory (volatile memory), such as a random access memory (random access memory, RAM); the memory 803 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (read-only memory, ROM), flash memory (flash memory), hard disk (hard disk drive, HDD) or solid-state drive (solid-state drive, SSD); the memory 803 may also include a combination of the above types of memory. It should be noted that the memory 803 included in the data transmission device 80 is only used as an example, and does not constitute a limitation to the embodiment of the present application. In an implementation manner, the memory 803 may be replaced by other storage media with a storage function.

The processor 802 can call the program code stored in the memory 803 to make the data transmission device 80 perform the following operations:

receiving an uplink data packet from a terminal device, and determining session information corresponding to the uplink data packet;

When the session information corresponding to the uplink data packet satisfies the edge forwarding condition, the uplink data packet is sent to the edge gateway.

In one implementation, the session information may include a session type, and the edge forwarding condition may include one or more edge forwarding session types; the session information meeting the edge forwarding condition may include that the session type corresponding to the uplink data packet is the same as the edge forwarding session type .

In one implementation, the session information may include the identifier and session type of the access network device corresponding to the terminal device; the edge forwarding condition may include one or more edge forwarding device identifiers and one or more edge forwarding session types; the session information Satisfying the edge forwarding condition may include: the identifier of the access network device is the same as the edge forwarding device identifier, and the session type corresponding to the uplink data packet is the same as the edge forwarding session type.

In one implementation, before sending the uplink data packet to the edge gateway, the processor 802 can also call the program code stored in the memory 803 to make the data transmission device 80 perform the following operations: obtain the address information of the edge gateway, and send the uplink data packet to the edge gateway. The destination address information of the packet is modified to the address information of the edge gateway; the processor 802 calls the program code stored in the memory 803 to enable the data transmission device 80 to perform the sending of the uplink data packet to the edge gateway, specifically, the data transmission device 80 can perform the following Action: Send the uplink data packet to the edge gateway according to the destination address information of the modified uplink data packet.

In an implementation manner, the address information of the edge gateway may include an Internet Protocol version 6 IPV6 address.

In one implementation, the processor 802 may also call the program code stored in the memory 803 to enable the data transmission device 80 to perform the following operations: when the session information corresponding to the uplink data packet does not meet the edge forwarding condition, the uplink The data packet is sent to the network element of the core network.

Further, the processor 802 can also call the program code stored in the memory 803 to enable the data transmission device 80 to perform the operation corresponding to the first network device in the embodiment shown in FIG. 2-FIG. 3a. For details, please refer to the description in the method embodiment , which will not be repeated here.

Please refer to FIG. 9. FIG. 9 is a schematic structural diagram of another data transmission device provided by an embodiment of the present application. The device may be a second network device or a device (such as a chip) having the function of a second network device. The data transmission device 90 For performing the steps performed by the second network device in the method embodiments corresponding to FIGS. 4-5 , the data transmission device 90 may include:

The processing module 901 is configured to determine that the current tunnel information is different from the historical tunnel information; the tunnel information is the tunnel information between the core network element and the access network device;

The communication module 902 is configured to send the downlink data packet corresponding to the tunnel information to the edge gateway.

In an implementation manner, the processing module 901 may also be configured to generate a downlink data packet.

In an implementation manner, the communication module 902 may also be configured to receive downlink data packets from network elements of the core network.

In an implementation manner, the downlink data packets may be the first n downlink data packets in the downlink data flow; wherein, n may be a positive integer.

In one implementation, the communication module 902 can also be used to obtain the address information of the edge gateway; the processing module 901 can also be used to modify the destination address information of the downlink data packet to the address information of the edge gateway; the communication module 902 is used to When sending the downlink data packet corresponding to the tunnel information to the edge gateway, it may specifically be used to send the downlink data packet to the edge gateway according to the modified destination address information of the downlink data packet.

In an implementation manner, the address information of the edge gateway may include an Internet Protocol version 6 IPV6 address.

In one implementation, the processing module 901 can also be used to determine the session information corresponding to the tunnel information; when the session information satisfies the edge forwarding condition, trigger the execution of the step of sending the downlink data packet corresponding to the tunnel information to the edge gateway .

It should be noted that for the content not mentioned in the embodiment corresponding to FIG. 9 and the specific implementation manners of the execution steps of each module, refer to the embodiments shown in FIGS. 4-5 and the foregoing content, and details are not repeated here.

In an implementation manner, related functions implemented by each module in FIG. 9 may be implemented in combination with a processor and a communication interface. Referring to FIG. 10, FIG. 10 is a schematic structural diagram of another data transmission device provided by an embodiment of the present application. The device may be a second network device or a device (such as a chip) having the function of a second network device. The data transmission device 100 It may include a communication interface 1001, a processor 1002, and a memory 1003, and the communication interface 1001, the processor 1002, and the memory 1003 may be connected to each other through one or more communication buses, or may be connected in other ways. The relevant functions implemented by the processing module 901 and the communication module 902 shown in FIG. 9 may be implemented by the same processor 1002 , or may be implemented by multiple different processors 1002 .

The communication interface 1001 can be used to send data and/or signaling, and receive data and/or signaling. Applied in the embodiment of the present application, the communication interface 1001 may be used to send the downlink data packet corresponding to the tunnel information to the edge gateway. Communication interface 1001 may be a transceiver.

The processor 1002 is configured to execute corresponding functions of the second network device in the methods described in FIGS. 4-5 . The processor 1002 may include one or more processors, for example, the processor 1002 may be one or more central processing units (central processing unit, CPU), network processor (network processor, NP), hardware chip or any other combination. In the case that the processor 1002 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

The memory 1003 is used to store program codes and the like. The memory 1003 may include a volatile memory (volatile memory), such as a random access memory (random access memory, RAM); the memory 1003 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (read-only memory, ROM), flash memory (flash memory), hard disk (hard disk drive, HDD) or solid-state drive (solid-state drive, SSD); the memory 1003 may also include a combination of the above types of memory. It should be noted that the memory 1003 included in the data transmission device 100 is only used as an example, and does not constitute a limitation to the embodiment of the present application. In an implementation manner, the memory 1003 may be replaced by other storage media with a storage function.

The processor 1002 can call the program code stored in the memory 1003 to make the data transmission device 100 perform the following operations:

Determine that the current tunnel information is different from the historical tunnel information; the tunnel information is the tunnel information between the core network element and the access network device;

Send the downlink data packet corresponding to the tunnel information to the edge gateway.

In an implementation manner, the processor 1002 may also invoke program codes stored in the memory 1003 to enable the data transmission device 100 to perform the following operations: generate a downlink data packet.

In an implementation manner, the processor 1002 may also invoke program codes stored in the memory 1003 to enable the data transmission device 100 to perform the following operations: receive a downlink data packet from a core network element.

In an implementation manner, the downlink data packets may be the first n downlink data packets in the downlink data flow; wherein, n may be a positive integer.

In an implementation manner, before sending the downlink data packet corresponding to the tunnel information to the edge gateway, the processor 1002 may also call the program code stored in the memory 1003 to enable the data transmission device 100 to perform the following operations: obtain the address information of the edge gateway ; modify the destination address information of the downlink data packet to the address information of the edge gateway; the processor 1002 calls the program code stored in the memory 1003 so that the data transmission device 100 executes when the downlink data packet corresponding to the tunnel information is sent to the edge gateway, Specifically, the data transmission device 100 may be made to perform the following operations: according to the modified destination address information of the downlink data packet, send the downlink data packet to the edge gateway.

In an implementation manner, the address information of the edge gateway may include an Internet Protocol version 6 IPV6 address.

In one implementation, the processor 1002 may also call the program code stored in the memory 1003 to enable the data transmission device 100 to perform the following operations: determine the session information corresponding to the tunnel information; when the session information satisfies the edge forwarding condition, The step of sending the downlink data packet corresponding to the tunnel information to the edge gateway is triggered.

Further, the processor 1002 can also call the program code stored in the memory 1003 to enable the data transmission device 100 to perform the operation corresponding to the second network device in the embodiment shown in FIG. 4-FIG. 5. For details, please refer to the description in the method embodiment. , which will not be repeated here.

The embodiment of the present application also provides a data transmission system, the data transmission system includes the aforementioned data transmission device as shown in Figure 7, the aforementioned data transmission device and the edge gateway as shown in Figure 8, or, the data transmission system includes the aforementioned The data transmission device shown in FIG. 9 , the aforementioned data transmission device and the edge gateway shown in FIG. 10 .

The embodiment of the present application also provides a computer-readable storage medium, which can be used to store the computer software instructions used by the data transmission device in the embodiment shown in FIG. program of.

The embodiment of the present application also provides a computer-readable storage medium, which can be used to store the computer software instructions used by the data transmission device in the embodiment shown in FIG. program of.

The above-mentioned computer-readable storage medium includes, but is not limited to, flash memory, hard disk, and solid-state hard disk.

The embodiment of the present application also provides a computer program product, which can execute the method designed for the first network device in the embodiment of FIG. 2-FIG. 3a above when the computer product is run by the computing device.

The embodiment of the present application also provides a computer program product, which can execute the method designed for the second network device in the above-mentioned embodiments of FIG. 4-FIG. 5 when the computer product is run by a computing device.

In an embodiment of the present application, a chip is also provided, including a processor and a memory. The memory includes a processor and a memory. The memory is used to store a computer program. The processor is used to call and run the computer program from the memory. The computer program is used to implement the methods in the above method embodiments.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed in this application can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

The above-mentioned embodiments may be fully or partially implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, all or part of the processes or functions according to the embodiments of the present application will be generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The above computer instructions may be stored in or transmitted through a computer-readable storage medium. The above computer instructions may be sent from one website site, computer, server or data center to another website site, via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) computer, server or data center for transmission. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server, a data center, etc. integrated with one or more available media. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (solid state disk, SSD)), etc.

The above is only a specific embodiment of the application, but the scope of protection of the application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. All should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (18)

1. A data transmission method, characterized in that the method comprises: receiving an uplink data packet from a terminal device, and determining session information corresponding to the uplink data packet; When the session information satisfies the edge forwarding condition, the uplink data packet is an IPv6 data packet, and the header of the uplink data packet includes a segment routing extension header SRH, modify the destination address of the uplink data packet to be an edge The IPv6 address of the gateway, and updating the Segments Left field in the SRH extension header to 0; Send the uplink data packet to the edge gateway according to the modified destination address of the uplink data packet. 2. The method according to claim 1, wherein the session information includes a session type, and the edge forwarding condition includes one or more edge forwarding session types; the session information satisfies the edge forwarding condition including the session The type is the same as the edge forwarding session type. 3. The method according to claim 1, wherein the session information includes the identifier and session type of the access network device corresponding to the terminal device; the edge forwarding condition includes one or more edge forwarding device identifiers and one or more edge forwarding session types; the session information meeting the edge forwarding condition includes that the identifier of the access network device is the same as the edge forwarding device identifier and the session type is the same as the edge forwarding session type. 4. The method according to claim 1, wherein the address information of the edge gateway comprises an Internet Protocol version 6 IPV6 address. 5. The method according to any one of claims 1 to 4, characterized in that the method further comprises: When the session information does not satisfy the edge forwarding condition, the uplink data packet is sent to a core network element. 6. A data transmission method, characterized in that the method comprises: Determining that the current tunnel information is different from the historical tunnel information; the tunnel information is the tunnel information between the core network element and the access network device; When the session information corresponding to the tunnel information satisfies the edge forwarding condition, send the downlink data packet corresponding to the tunnel information to the edge gateway, and the current tunnel information is used to encapsulate the downlink data packet from the local server; The uplink data packet corresponding to the session information includes the uplink data packet sent to the local server. 7. The method according to claim 6, further comprising: Generate the downlink data packet. 8. The method according to claim 6, further comprising: receiving the downlink data packet from the network element of the core network. 9. The method according to claim 8, wherein the downlink data packets are the first n downlink data packets in the downlink data flow; wherein, n is a positive integer. 10. The method according to any one of claims 6-9, wherein before sending the downlink data packet corresponding to the tunnel information to the edge gateway, the method further comprises: Obtain the address information of the edge gateway; modifying the destination address information of the downlink data packet to the address information of the edge gateway; The sending the downlink data packet corresponding to the tunnel information to the edge gateway includes: Send the downlink data packet to the edge gateway according to the modified destination address information of the downlink data packet. 11. The method according to claim 10, wherein the address information of the edge gateway includes an Internet Protocol Version 6 IPV6 address. 12. A data transmission device, comprising a unit for executing the method according to any one of claims 1-5. 13. A data transmission device, comprising a unit for executing the method according to any one of claims 6-11. 14. A data transmission device, characterized in that it includes a processor and a memory, wherein program instructions are stored in the memory, and the processor invokes the program instructions stored in the memory to make the data transmission device execute The method described in any one of 1 to 5 is required. 15. A data transmission device, characterized in that it includes a processor and a memory, wherein program instructions are stored in the memory, and the processor invokes the program instructions stored in the memory to make the data transmission device execute The method described in any one of 6 to 11 is required. 16. A data transmission system, characterized in that it comprises the data transmission device as claimed in claim 12 and the data transmission device as claimed in claim 13, or comprises the data transmission device as claimed in claim 14 and the data transmission device as claimed in claim 14 The data transmission device of claim 15. 17. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes the following: The method according to any one of claims 1-5. 18. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes the following: The method according to any one of claims 6-11.

Images