WO2017214991A1

WO2017214991A1 - Data transmission method, gateway apparatus, and network apparatus

Info

Publication number: WO2017214991A1
Application number: PCT/CN2016/086278
Authority: WO
Inventors: 周军平; 叶文林; 夏渊; 孙晓东
Original assignee: 华为技术有限公司
Priority date: 2016-06-17
Filing date: 2016-06-17
Publication date: 2017-12-21

Abstract

The invention provides a data transmission method, gateway apparatus, and network apparatus. The data transmission method comprises: a first gateway apparatus receives a session establishment request transmitted by a first network apparatus and containing information used to instruct the first gateway apparatus to establish user context for a terminal apparatus; the first gateway apparatus establishes, according to the session establishment request, the user context for the terminal apparatus; the first gateway apparatus receives a service message transmitted by the terminal apparatus and containing service data and address information of a target server containing the service data; when determining, according to the address information of the target server, that the target service is a local application server, the first gateway apparatus transmits, locally and by means of the user context, and to the target server, the service data. The data transmission method, gateway apparatus, and network apparatus according to the invention can increase data transmission efficiency when a terminal apparatus accesses a local network.

Description

Data transmission method, gateway device, and network device

Technical field

The present invention relates to the field of communications, and in particular, to a data transmission method and a gateway device and a network device that perform the data transmission method.

Background technique

The Evolved Packet System (EPS) is the 3rd Generation Partnership Project (3GPP). The EPS network includes an Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN) and an Evolved Packet Core Network (EPC). The EPS network can only provide packets. Packet Switched (PS) service.

The current PS network element includes network elements such as a Serving Gate Way (SGW), a Packet Gate Way (PGW), and a Mobility Management Entity (MME).

When a terminal device accesses a local network through the Internet (Internet), such as an intranet, the PS network elements such as E-UTRAN, SGW, and PGW that are required to pass through the data are usually deployed in the provincial trunk transmission network, resulting in the terminal device. The data transmission path is cumbersome, resulting in inefficient transmission and poor user experience.

Summary of the invention

The present invention provides a data transmission method, a gateway device, and a network device, which can improve data transmission efficiency when a terminal device accesses a local network.

In a first aspect, the present invention provides a data transmission method, including: a first gateway device receiving a session creation request message sent by a first network device, where the session creation request message is used to indicate that the first gateway device is a terminal The device creates a user context information; the first gateway device creates a user context for the terminal device according to the session creation request message; the first gateway device receives a service message sent by the terminal device, where the service message carries The service data and the address information of the target server of the service data; the first gateway device determines, according to the address information of the target server, that the target server is a local application server, and locally to the target server by using the user context Send the business data.

In the embodiment of the present invention, after receiving the session creation request message of the first network device, the first gateway device creates a user context for the terminal device, so that the first gateway device determines that the server corresponding to the target address of the service data of the terminal device is the local server. When the first gateway device determines the local network when the terminal device accesses the network, the service data of the terminal device is directly sent to the local server directly at the first gateway device, so that the upstream network device does not need to pass through the first gateway device. Forwarding the data sent by the terminal device to the local network, thereby shortening the data transmission path, thereby improving the data transmission efficiency, and finally improving the user experience.

In a possible implementation, before the first gateway device receives the service message sent by the terminal device, the data transmission method further includes: the first gateway device receiving the domain name system sent by the terminal device (Domain Name System, DNS) request message, the DNS request message carries domain name information of a target address of the service data; the first gateway device determines a target application corresponding to the target address according to domain name information of the target address When the server is a local application server, the server sends a DNS response message to the terminal device, where the DNS response message carries address information of the target server.

In the embodiment of the present invention, the first gateway device may determine, according to the domain name of the target address of the service data of the terminal device, whether the service data can be directly forwarded from the first gateway device to the local application server, and determine that the service data can be When the first gateway device is directly forwarded to the local application server, the address information of the application server is returned to the terminal device, so that the terminal device carries the address information of the application server in the subsequent service data, and then the first gateway device can Transmitting the service data directly to the corresponding local application server according to the address information of the application server carried in the service data.

In a possible implementation, when the first gateway device determines that the target server corresponding to the target address is a local application server, the first gateway device sends a DNS response message to the terminal device, including: When the first gateway device determines that the domain name information of the target address exists in the domain name information of the at least one local application server on the first gateway device, the first gateway device sends a DNS response message to the terminal device.

Optionally, the domain name information of the at least one local server may be pre-configured on the first gateway device.

In a possible implementation, when the first gateway device determines that the target application server is a local application server according to the address information of the target application server, the first gateway device locally sends the local target application server through the user context. The service data includes: the first network When the device determines that the address information of the target server exists in the address information of the at least one local application server on the first gateway device, the service data is locally sent to the local target application server by using the user context.

Optionally, the address information of the at least one local server may be pre-configured on the first gateway device, or may be dynamically obtained by the first gateway device from another network element, such as a service gateway.

In a possible implementation manner, the first network device is a second gateway device, where the data transmission method further includes: the first gateway device receiving a service message sent by the terminal device, where the service The message carries the service data and the identifier information of the terminal device; when the first gateway device determines that the user context of the terminal device corresponding to the identifier information is not available on the first gateway device, sending, to the second gateway device, The first gateway device receives the session creation request message sent by the first network device, and the first gateway device receives the second gateway device to determine, according to the service data offload policy, that the first gateway device needs to be A session creation request message sent when the terminal device creates a user context. The service data offloading policy may be whether the access point name corresponding to the service data needs to be locally offloaded, or whether the service flow corresponding to the service offload data needs local offloading, or other local offloading policies.

In the embodiment of the present invention, when the first gateway device receives the service data of the terminal device, and the first gateway device does not have the user context of the terminal device, the first gateway device may send the service data to the second gateway device, and then receive the first The second gateway device determines the sent session creation request message according to the traffic distribution policy corresponding to the service data, to create a user context for the terminal device according to the session creation request message.

In a possible implementation manner, the session creation response message further carries address information of the at least one local server.

In the embodiment of the present invention, the first gateway device may dynamically obtain the address information of the at least one local server from the session creation response message sent by the second gateway device.

In a possible implementation manner, the first network device is a mobility management network element MME.

In the embodiment of the present invention, the MME sends a session creation request message to the first gateway device to trigger the first gateway device to create a context for the terminal device.

In a possible implementation manner, the first gateway device is deployed in an access network or a metropolitan area network of the terminal device.

In the embodiment of the present invention, the first gateway device deployed in the access network of the terminal device and the metropolitan area network sends the data of the local network directly to the local network, which can save data. Transmission path.

In a second aspect, the present invention provides a data transmission method, including: a first network device sends a session creation request message to a first gateway device, where the session creation request message is used to indicate that the first gateway device is a terminal device Creating information of a user context; the first network device receiving a session creation response message sent by the first gateway device in response to the session creation request message.

In the embodiment of the present invention, the first network device sends a session creation request message to the first gateway device, so that the first gateway device can create a user context for the terminal device, and the first gateway device can implement the data of the terminal device according to the user context. ,

In a possible implementation, the first network device is a second gateway device, where the data transmission method further includes: the second gateway device receiving the first gateway device to determine the first gateway When the device has no user context of the terminal device, the service data of the terminal device is sent; the first network device sends a session creation request message to the first gateway device, where: the second gateway device is configured according to the The access point name corresponding to the service data determines that the first gateway device needs to create a user context for the terminal device, and sends a session creation request message to the first gateway device.

In the embodiment of the present invention, when the first network device receives the service data of the terminal device that is sent by the first gateway device when determining that the user context of the terminal device is not on the first gateway device, and determining, according to the service data, the first gateway device needs to be determined. When a user context is created for the terminal device, a request message is created to the first gateway device session, such that the first gateway device can create a user context for the terminal device according to the session creation request message.

In a possible implementation manner, the session creation request message further carries address information of at least one local application server, where the address information is used by the first gateway device to determine whether a target server of the service data of the terminal device is local. application server.

In a third aspect, the present invention provides a gateway device, the gateway device comprising means for performing the data transmission method of the first aspect.

In a fourth aspect, the present invention provides a network device, the network device comprising means for performing the data transmission method of the second aspect.

In a fifth aspect, the present invention provides a gateway device including a receiver, a transmitter, a processor, and a memory, the memory for storing code, and the processor for executing in the memory Code, the receiver and transmitter are used to communicate with other devices. When the code is executed, the processor invokes the receiver and transmitter to implement the method of the first aspect.

In a sixth aspect, the present invention provides a network device including a receiver, a transmitter, a processor, and a memory, the memory for storing code, the processor for executing code in the memory, the receiver And the sender is used to communicate with other devices. When the code is executed, the processor invokes the receiver and transmitter to implement the method of the second aspect.

In a seventh aspect, the invention provides a computer readable medium storing program code for execution by a gateway device, the program code comprising instructions for performing the method of the first aspect.

In an eighth aspect, the invention provides a computer readable medium storing program code for execution by a network device, the program code comprising instructions for performing the method of the second aspect.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the embodiments of the present invention will be briefly described below. It is obvious that the drawings described below are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

FIG. 1 is a schematic application scenario diagram of an embodiment of the invention.

FIG. 2 is a schematic flowchart of a data transmission method according to an embodiment of the present invention.

3 is a schematic architectural diagram of a communication network to which a data transmission method according to an embodiment of the present invention is applied.

FIG. 4 is a schematic flowchart of a data transmission method according to an embodiment of the present invention.

FIG. 5 is a schematic structural diagram of a communication network to which a data transmission method according to an embodiment of the present invention is applied.

FIG. 6 is a schematic flowchart of a data transmission method according to an embodiment of the present invention.

FIG. 7 is a schematic structural diagram of a gateway device according to an embodiment of the present invention.

FIG. 8 is a schematic flowchart of a network device according to an embodiment of the present invention.

FIG. 9 is a schematic structural diagram of a gateway device according to an embodiment of the present invention.

FIG. 10 is a schematic flowchart of a network device according to an embodiment of the present invention.

detailed description

In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the following will be combined with the present invention. The technical solutions in the embodiments of the present invention are clearly and completely described in the drawings, and the embodiments are described as a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

For ease of understanding, an exemplary diagram of a communication network to which the data transmission method of the embodiment of the present invention can be applied will be described first. It should be understood that the embodiments of the present invention are not limited to the communication network shown in FIG. 1. In addition, the apparatus in FIG. 1 may be hardware, or may be functionally divided software or a structure of the above two.

As shown in FIG. 1, the communication network to which the data transmission method of the embodiment of the present invention can be applied may include the terminal device 110, the base station 120, the gateway device 130, the gateway device 140, the MME 150, and the local application server 160, and the Internet 170 (Internet) ). The terminal device 110 can communicate with the gateway device 130 and the MME 150 through the base station 120, and the gateway device 130 can forward the service data of the terminal device 110 to the local application server 160 or the gateway device 140. The dashed lines of gateway device 130 and gateway device 140 and MME 150 indicate that one of gateway device 130 or gateway device 140 can communicate with gateway device 140. The local application server 160 can communicate with the gateway device. The gateway device 120 can be deployed in an access network or a metropolitan area network of the terminal device 110.

In the embodiment of the present invention, the terminal equipment 110 (User Equipment, UE) may communicate with one or more core networks (Core Network) via a radio access network (RAN), and the UE may be referred to as an access terminal. , user equipment, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The UE may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or a wireless communication function. Handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, and terminal devices in future 5G networks.

In the embodiment of the present invention, the base station 120 may be a Global System for Mobile communication (GSM) system or a Base Transceiver Station (BTS) in a Code Division Multiple Access (CDMA) system. It may be a base station (NodeB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or in a future 5G network. Base station equipment, small base station equipment, etc., this issue This is not limited to this. Moreover, in the embodiment of the present invention, the base station may represent the access network.

In the embodiment of the present invention, the MME 150 is a control plane network element, and is mainly responsible for control plane functions such as mobility management and session management of user equipment.

In an embodiment of the invention, the Local Application Server (LAPP) 160 is essentially an application server. When the application server and the terminal device are in a local geographical scope (such as a school, a factory, and an organization), the application server may be referred to as a local application server of the terminal device. The terminal device 110 only needs to access the local application server 160 through the base station 120 and the gateway device 130 to access the local network without accessing the local network 160 through the gateway device 140 and the Internet 170. The local application server 160 is usually deployed by an application service provider near a terminal device (such as an access network location). Therefore, the traffic of the terminal device 110 can be directly routed from the gateway device 130 to the local application server 160. The direct routing mode can be called local transmission.

It should be noted that the explanation of the terms in the embodiments of the present invention is merely illustrative and should not be construed as limiting the embodiments of the present invention.

FIG. 2 is a schematic flowchart of a data transmission method according to an embodiment of the present invention. It should be understood that FIG. 2 illustrates steps or operations of the data transmission method, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the operations of FIG. 2. Moreover, the various steps in FIG. 2 may be performed in a different order than that presented in FIG. 2, and it is possible that not all operations in FIG. 2 are to be performed.

S210, the gateway device 204 receives the session creation request message sent by the network device 206, where the session creation request message carries information indicating that the gateway device 204 creates a user context for the terminal device 202. The gateway device 204 may be the gateway device 130 in FIG. 1 , the network device 206 may be the gateway device 140 or the MME 150 in FIG. 1 , the terminal device 202 may be the terminal device 110 in FIG. 1 , and the local application server 208 may be The local application server 160 in FIG.

Generally, when the terminal device 202 is powered on, it initiates an attach registration process to the network to request network service rights. The network completes the authentication and authorization of the terminal device, and establishes a default bearer for the terminal device to provide services for the UE.

After the terminal device 202 is attached to the network, the network device 206 in the network sends a session creation request message to the gateway device 204, instructing the gateway device 204 to create a user context for the terminal device 202, so that when the terminal device 202 sends the service data, the gateway device The service data of the terminal device 202 can be transmitted using the user context of the terminal device 202.

Network device 206 may be a control device (such as MME 150) in the network, or a gateway device 140, or other network device.

When the network device 206 is a control device (such as the MME 150) in the network, when the terminal device 202 is attached to the network, the MME 150 selects a suitable gateway device 204 to serve the terminal device based on the location or service information of the terminal device 202. And a session creation request message is sent to the gateway device 204.

When the network device 206 is the gateway device 140, one possible implementation of the network device 206 transmitting a session creation request message to the gateway device 204 is as follows. After the terminal device 202 is attached to the network, the gateway device 204 receives the service data transmitted by the terminal device 202. The gateway device 204 determines if there is a user context of the terminal device 202 thereon. When the gateway device 204 determines that there is no user context of the terminal device 202, the service data of the terminal device 202 is sent to the network device 206, and the network device 206 determines whether the gateway device 204 needs to be created according to the access point name corresponding to the service data. User context of terminal device 202. When the network device 206 determines that the gateway device 204 needs to create a user context for the terminal device 202, the network device 206 sends a session creation request message to the gateway device 204.

If the gateway device 204 determines that there is a user context of the terminal device 202 thereon, the service data of the terminal device 202 is directly transmitted to the local application server 208 or other gateway using the user context.

S220. The gateway device 204 creates a user context for the terminal device 202 according to the session creation request message.

After receiving the session creation request message sent by the network device 206, the gateway device 204 creates a user context for the terminal device 202. After the gateway device 204 creates a user context for the terminal device 202, a session creation response message can be sent to the network device 206 to respond to the network device 206 with a session creation request message. The session creation response message sent by the gateway device 204 may also carry information such as its tunnel identifier or address.

S230. The gateway device 204 receives the service message sent by the terminal device 202, where the service message carries the service data and the address information of the target server of the service data.

S240. The gateway device 204, when determining that the target server is the local application server 208 according to the address information of the target server, locally sends the service data to the target server 208 through the user context.

After receiving the service message sent by the terminal device 202, the gateway device 204 can determine whether the target server is a local application service according to the address information of the target server carried in the service message. Device. When the gateway device 204 determines that the target server is the local application server, the service data of the terminal device 202 is locally sent to the local application server 208 corresponding to the address information by using the previously created user context. If the gateway device 204 determines that the target server is not the local application server, the service data of the terminal device 202 is sent to other network devices (such as the network device 206) through the previously created user context, so that the other network devices can use the service data of the terminal device 202. Sent to the target server.

Here, the gateway device 204 locally transmits the service data of the terminal device to the local application server 208, that is, the gateway device 204 directly sends the service data of the terminal device to the local application server 208 without going through the terminal device 202 more than the gateway device 204. Far from other network devices to send the service data of the terminal device to the target server of the service data. Taking the network architecture shown in FIG. 1 as an example, the service data of the terminal device 110 accessing the local network may be forwarded to the local application server 160 via the gateway device 120, and then accessed by the local application server 160. That is to say, the service data of the terminal device 110 accessing the local network does not pass through the gateway device 140 and the Internet, and then accesses the local network.

Because the local application server and the terminal device are in a geographical range together, and the gateway device 204 is deployed closer to the terminal device 202 (eg,), the gateway device 204 directly sends the service data of the terminal device 202 to the local application server. 208, the transmission path of the service data can be shortened, and the transmission message of the service data is improved.

In the embodiment of the present invention, when the gateway device 204 determines whether the target server is the local application server according to the address information of the target server, the specific implementation manner may be: the gateway device 204 determines that the target server exists in the address information of the at least one local application server. When determining the address information, determine the target server as the local application server. That is, when the gateway device 204 determines that the address information of the target server exists in the address information of the at least one local application server, the service data is directly transmitted to the target server through the user context of the terminal device 202.

The address information of the at least one local application server on the gateway device 204 for determining whether the target server is the local application server may be pre-configured on the gateway device 204, or may be carried in the session creation request message sent by the network device 206 to the gateway device 204. Of course, it can also be obtained by other means, and the present invention does not limit this.

In the embodiment of the present invention, before the gateway device 204 receives the service message sent by the terminal device 202, the data transmission method may further include: the gateway device 204 receives the DNS request message sent by the terminal device 202, and the DNS request message carries the service of the terminal device 202. Destination address of the data The domain name information is used by the gateway device 204 to determine whether the target server of the service data is a local application server according to the domain name information. When the gateway device 204 determines that the target server corresponding to the service data is a local application server according to the domain name information, the gateway device 204 sends the domain name information to the terminal device 202. The DNS response message, the DNS response message carries the address information of the target server.

Correspondingly, the data transmission method may further include: when the gateway device 204 determines, according to the domain name information, that the target server corresponding to the target address is not a local application server, to another gateway device (for convenience of subsequent description, the gateway device is referred to as The second gateway device forwards the DNS response message, and the second gateway device sends a DNS request message to the DNS server, so that the DNS server determines the address information of the server corresponding to the domain name information. And returning the address information of the application server to the second gateway device by using a DNS response message, and sending the second gateway device to the gateway device 204. The gateway device 204 then receives the address information of the server transmitted by the second gateway device and transmits the address information of the server to the terminal device 202. The second gateway device may be the gateway device 140 in FIG.

In the embodiment of the present invention, when the gateway device 204 determines, according to the domain name information, whether the target server corresponding to the service data is a local application server, the specific implementation manner may be: the gateway device 204 determines at least one local application on the gateway device 204. When the domain name information exists in the domain name information of the server, the target server corresponding to the service data is determined to be a local application server. That is, the gateway device 204 determines that the domain name information exists in the domain name information of the at least one local application server on the gateway device 204, and sends a DNS response message to the terminal device 202.

3 is a more detailed schematic architectural diagram of the communication network shown in FIG. 1. The apparatus in FIG. 3 may be hardware, or may be functionally divided software or a structure of both.

In the communication network shown in FIG. 3, the gateway device 130 can be transparently connected to the S1-U interface, and all the user plane traffic must pass through the gateway device 130. The gateway device 130 is invisible to the surrounding network element (such as the MME), and the gateway device 140 The gateway device 130 can be controlled and managed through the control interface Sx interface. The gateway device 140 may have the functions of a Serving Gate Way (SGW) and a Packet Data Network Gateway (PGW).

In the embodiment of the present invention, the SGW and the PGW have both control plane and user plane functions, and mainly participate in mobility management and session management, such as access control, data forwarding, and charging. The SGW and the PGW can be separately set, and the interface between them can be a standard S5 interface; the SGW and the PGW network element can also be combined.

In the communication network shown in FIG. 3, since the gateway device 130 is separated from the gateway device 140 by the terminal The device 110 is relatively close, that is, the gateway device 130 is located in a remote location in the entire network. Therefore, the gateway device 130 can be referred to as a remote gateway (RGW), and the gateway device 140 can be referred to as a centralized gateway. , CGW).

When the network device 206 in the data transmission method shown in FIG. 2 is the gateway device 140, a schematic flowchart of the data transmission method shown in FIG. 2 specifically applied to the communication network shown in FIG. 3 is shown in FIG. 4.

It should be understood that FIG. 4 illustrates steps or operations of the data transmission method, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the respective operations in FIG. Moreover, the various steps in FIG. 4 may be performed in a different order than that presented in FIG. 4, and it is possible that not all operations in FIG. 4 are to be performed.

S402. The UE initiates an attach registration process to the network, requesting service rights of the network. The network completes the authentication and authorization of the UE, and establishes a default bearer for the UE to provide services for the user. The UE can initiate an attach procedure at boot time.

The attach registration process can be performed according to the process in the 3GPP standard, and detailed steps are not described here. Since the attachment process is the interaction of control signaling, the RGW may not actually participate in the attachment process of the UE.

S404. The UE sends a DNS request message to the eNB, where the eNB receives the DNS request message sent by the UE.

Before this step, the RGW can configure the DNS hijacking policy locally, that is, configure the address of the local network, such as the mapping between the Internet Protocol (IP) address and the domain name of the server belonging to the local network (LAPP). The IP address of the LAPP can be the same as or different from the IP address of the Public Data Network (PDN).

After the UE's attach registration process is completed, the UE may send data to the RGW through the eNB by using the bearer established in the attach procedure. Before the UE sends data to the RGW, it needs to initiate a DNS request message to query the address of the domain name of the network that the UE will access. Therefore, the DNS request message may carry the domain name of the network that the UE will access.

S406. The eNB sends a DNS request message of the UE to the RGW, and the RGW receives the DNS request message of the UE sent by the eNB.

S408. After receiving the DNS request message of the UE, the RGW determines, according to the locally configured DNS hijacking policy, whether the DNS request message needs to be directly acknowledged, or whether the DNS request message needs to be sent to the CGW, and the CGW responds to the DNS request message.

For example, when the RGW determines that the domain name corresponding to the locally configured LAPP address contains the domain name carried in the DNS request message, the address of the LAPP corresponding to the domain name is determined, that is, the RGW responds to the DNS request message. Otherwise, the RGW sends the DNS request message to the CGW.

S410. After the RGW determines the LAPP address corresponding to the domain name of the network to be accessed by the UE, the RGW sends a DNS response message to the eNB, where the DNS response message carries the address of the LAPP.

If the RGW sends a DNS request message to the CGW, the CGW sends a DNS request message to the DNS server, so that the DNS server determines the address of the application server corresponding to the domain name of the network that the UE is to access, and returns the address information of the application server to the address server. The CGW further sends the address information of the application server to the RGW through a DNS response message, and the RGW receives the address of the server sent by the CGW.

S412. The eNB sends the address of the LAPP to the UE. If the eNB receives the address of the server returned by the CGW from the RGW, the eNB here transmits the address of the server returned by the CGW to the UE.

According to the above steps, the RGW may determine, according to the DNS request message of the UE, that the server corresponding to the network to be accessed by the UE is the LAPP, and then directly respond to the DNS request message, instead of sending the DNS request message of the sending UE to the DNS server through the CGW. That is, the RGW can directly determine the address information corresponding to the domain name of the network to be accessed for the UE.

S414. The UE sends an uplink service message to the eNB, where the uplink service message carries the service data sent by the UE to the network to be accessed and the address of the server corresponding to the network.

The address of the server carried in the uplink service message may be the address of the LAPP determined by the RGW, or may be the address of the server returned by the CGW.

S416. The eNB sends an uplink service message of the UE to the RGW.

S418: The RGW receives the uplink service message sent by the UE, parses the service data in the uplink service message, obtains the address of the UE in the data packet, and queries the RGW for the user context information of the UE according to the address.

S420: The RGW determines that the user context of the UE is not locally, and the RGW determines that the UE is a new user, that is, the local offload function of the UE is not activated on the RGW. Therefore, the RGW sends the service data of the UE to the CGW.

When the RGW sends the service data information to the CGW, an implementation manner is as follows: the RGW inserts the service data into the extension header of the General Packet Radio Service (GPRS) Tunneling Protocol (GTPU) at the user level. The Sx interface address and the tunnel identification information of the S1-U, and then the service data is sent to the CGW.

S422. After receiving the service data information sent by the RGW, the CGW parses the service data packet, obtains the address of the UE in the data packet, and after querying the local user context of the UE according to the address of the UE, the CGW can be connected according to the target address of the service data. Whether the ingress point supports the local offload function to determine whether the context should be created for the UE on the RGW.

When the CGW determines that a context should be created for the UE on the RGW, the CGW sends a session creation request message to the RGW. The session request response message may carry information such as address information, tunnel identification information, quality of service (QoS) parameters, and charging policy information of the CGW.

S424. After receiving the session creation request message sent by the CGW, the RGW creates a context for the UE according to the session creation request message. In this way, the RGW can send the UE service data according to the context of the created UE.

S425. After the RGW creates a context for the UE, the RGW replies to the CGW with a session creation response message.

It can be seen from the above steps that the RGW can create a context for the UE, so that the RGW can forward the service data of the UE according to the context.

S426. After the RGW creates a context for the UE, the UE may send an uplink service message to the eNB, where the uplink service message carries address information of the target server of the service data and the service data.

S428. The eNB sends an uplink service message of the UE to the RGW.

S430: After receiving the uplink service message of the UE, the RGW compares the address information of the target server with the local offload policy, and determines whether the target server is an LAPP.

When the local offloading policy is the address information of the at least one LAPP, if the address information of the at least one LAPP includes the address information of the target server, the target server may be determined to be the LAPP.

S432. When the RGW determines that the target server is the LAPP, the RGW sends the service data to the target server. Otherwise, the RGW can send the service data to the CGW.

Certainly, the RGW may receive downlink service data of the UE sent by the CGW and the LAPP, and then send the downlink service data to the UE by using the eNB. Optionally, the RGW may process the downlink service data received from the LAPP (such as encapsulation) and then send the data to the UE. The RGW may directly transmit the downlink data packet received from the CGW to the UE.

It can be seen that, when the target server that determines the service data of the UE is the LAPP, the RGW can directly send the service data to the LAPP, instead of being forwarded by the network element deployed farther from the UE, thereby saving the data transmission path and improving. Data transfer efficiency ultimately improves user experience.

FIG. 5 is a more specific schematic architecture diagram of the communication network shown in FIG. 1. The apparatus in FIG. 5 may be hardware, or may be functionally divided software or a structure of both.

The gateway device 130 can be deployed with an access network (such as base station 120) or can be deployed on a local area network. At this time, the gateway device 130 can be seen by the neighboring network element (such as the MME and the eNB). The S11 interface can exist between the gateway device 130 and the MME, so that the MME can select the gateway device served by the terminal device 110. The gateway device 130 may have the function of an SGW, and the gateway device 140 may have the function of a PGW.

In the communication network shown in FIG. 5, since the gateway device 130 is closer to the terminal device 110 than the gateway device 140, that is, the gateway device 130 is located in a relatively remote location in the entire network, the gateway device 130 may be referred to as an RGW. Gateway device 140 is referred to as a CGW.

When the network device 206 in the data transmission method shown in FIG. 2 is the MME 150, a schematic flowchart of the data transmission method shown in FIG. 2 specifically applied to the communication network shown in FIG. 5 is shown in FIG. 6.

It should be understood that FIG. 6 illustrates the steps or operations of the data transmission method, but these steps or operations are merely examples, and embodiments of the present invention may perform other operations or variations of the various operations in FIG. 6. Moreover, the various steps in FIG. 6 may be performed in a different order than that presented in FIG. 6, and it is possible that not all operations in FIG. 6 are to be performed.

S602. The UE initiates an attach registration process to the network, requesting service rights of the network. The network completes the authentication and authorization of the UE, and establishes a default bearer for the UE to provide services for the user. The UE can initiate an attach procedure at boot time.

The attach process follows the 3GPP standard (the Attach process of Section 5.3.2 of TS 23.401). For details, refer to steps 1 to 11 in the Attach procedure in section 5.3.2 of the 3GPP standard TS 23.401. The RGW in the present invention corresponds to the SGW in the standard flow, and the CGW in the present invention corresponds to the PGW in the standard flow.

S604: After the UE is attached to the network, the MME selects an appropriate RGW and CGW for the UE based on the location and service information of the UE, and initiates a session creation process.

The MME sends a session creation request message to the selected RGW, and instructs the RGW to create a context for the UE. The message may include information such as a tunnel identifier of the MME and an address of the CGW.

S606. After receiving the session creation request message sent by the MME, the RGW may send a session creation request message to the CGW, where the message may include information such as an address of the RGW and a tunnel identifier.

S608, after receiving the session creation request message sent by the RGW, the CGW creates an upper and lower Text.

It should be noted that, at this time, the CGW may initiate an IP-Connectivity Access Network (IP-CAN) session establishment process to the Policy and Charging Rules Function (PCRF) unit, and then the PCRF to the CGW. Issue policies such as Policy and Charging Control (PCC).

The PCRF can also send a local offloading policy (such as service identification information, or LAPP address information) to the CGW in the IP-CAN session establishment process.

S610, the CGW sends a session creation response message to the RGW, where the message may include information such as an address of the CGW and a tunnel identifier.

If the PCRF sends a local offload policy to the CGW, the CGW can forward the local offload policy to the RGW.

S612. After receiving the session creation request message sent by the MME, the RGW creates a context for the UE. It should be noted that the present invention does not limit the order of execution of S412 and S406.

S614. After the RGW creates a context for the UE, and receives a response message sent by the CGW to create a context for the UE, the RGW replies to the MME with a session creation response message. The session creation response message may include information such as an address and tunnel identification information of the RGW, and an address and a tunnel identifier of the CGW.

S616. The UE sends a DNS request message to the eNB, so that the eNB sends a DNS request message to the RGW, so that the RGW determines the address of the domain name of the network that the UE is to access. Therefore, the DNS request message may carry the domain name of the network that the UE will access.

S618: The eNB sends a DNS request message of the UE to the RGW, and the RGW receives the DNS request message of the UE sent by the eNB.

S620: After receiving the DNS request message of the UE, the RGW determines, according to the locally configured DNS hijacking policy, whether the DNS request message needs to be directly acknowledged, or whether the DNS request message needs to be sent to the DNS server through the CGW, and the DNS server answers the DNS request. Request message.

For example, when the RGW determines that the domain name corresponding to the address of the LAPP configured on the domain name includes the domain name carried in the DNS request message, the address of the LAPP corresponding to the domain name is determined, that is, the RGW responds to the DNS request message. Otherwise, the RGW sends the DNS request message to the CGW.

S622, after the RGW determines the LAPP address corresponding to the domain name of the network to be accessed by the UE, sends a DNS response message to the eNB, where the DNS response message carries the address of the LAPP.

If the RGW sends a DNS request message to the CGW, the CGW sends a DNS request message. Giving the DNS server, so that the DNS server determines the address of the application server corresponding to the domain name of the network that the UE is to access, and returns the address information of the application server to the CGW, and the CGW further sends the address information of the application server through the DNS response message. Give RGW. The RGW receives the address of the server sent by the CGW and sends the address to the eNB.

S624. The eNB sends the address of the LAPP to the UE. If the eNB receives the address of the server determined by the CGW from the RGW, the eNB here transmits the address of the server determined by the CGW to the UE.

According to the above steps, the RGW may determine, according to the DNS request message of the UE, that the server corresponding to the network to be accessed by the UE is LAPP, and then directly respond to the DNS request message without sending a DNS request message of the UE to the CGW, that is, the RGW may directly The address information corresponding to the domain name of the network to be accessed is determined for the UE.

S626. The UE sends an uplink service message to the eNB, where the uplink service message carries the service data sent by the UE to the network to be accessed and the address of the server corresponding to the network.

The address of the server carried in the uplink service message may be the address of the LAPP determined by the RGW, or may be the address of the server determined by the CGW.

S628. The eNB sends an uplink service message of the UE to the RGW.

S630: After receiving the uplink service message of the UE, the RGW compares the address information of the target server with the local offload policy, and determines whether the target server is an LAPP.

S632. When the RGW determines that the target server is the LAPP, the RGW sends the service data to the target server. Otherwise, the RGW can send the service data to the CGW.

The data transmission method of the embodiment of the present invention is described above with reference to FIG. 1 to FIG. 6 . 7 to FIG. 10 show a gateway device and a network device according to an embodiment of the present invention.

As shown in FIG. 7, the gateway device 700 of the embodiment of the present invention includes a receiving module 710, a creating module 720, and a sending module 730. It should be understood that the gateway device shown in FIG. 7 is only an example, and the gateway device of the embodiment of the present invention may further include other modules or units, or include modules similar to those of the respective modules in FIG. 7, or not including FIG. 7. All modules in .

The receiving module 710 is configured to receive a session creation request message sent by the first network device, where the session creation request message carries information used to instruct the first gateway device to create a user context for the terminal device.

The creating module 720 is configured to create a user context for the terminal device according to the session creation request message.

The receiving module 710 is further configured to receive a service message sent by the terminal device, where the service message carries service data and address information of a target server of the service data.

The sending module 730 is configured to locally send the service data to the target server by using the user context when the gateway device determines that the target server is a local application server according to the address information of the target server.

In the embodiment of the present invention, after receiving the session creation request message of the first network device, the gateway device creates a user context for the terminal device, so that the gateway device determines that the server corresponding to the target address of the service data of the terminal device is the local server, that is, the gateway. When the device determines the network that is accessed by the terminal device, the service data of the terminal device is sent locally to the local server directly at the gateway device, so that the data sent by the terminal device to the local network is not forwarded by the upstream network device of the gateway device. Thereby, the data transmission path can be shortened, thereby improving the data transmission efficiency, and finally the user experience can be improved.

Optionally, as an embodiment, the receiving module 710 is further configured to receive a DNS request message sent by the terminal device, where the DNS request message carries domain name information of a target address of the service data. The sending module 730 is further configured to: when the gateway device determines, according to the domain name information of the target address, that the target server corresponding to the target address is a local application server, send a DNS response message to the terminal device, where the DNS response is The message carries address information of the target server.

Optionally, as an embodiment, the sending module 730 is specifically configured to: when the gateway device determines that the domain name information of the target address exists in the domain name information of the at least one local application server on the gateway device, The terminal device sends a DNS response message.

Optionally, as an embodiment, the sending module 730 is specifically configured to: when the gateway device determines that the address information of the target server exists in the address information of the at least one local application server on the gateway device, The user context locally sends the service data to the target server.

Optionally, as an embodiment, the first network device is a second gateway device. Correspondingly, the receiving module 710 is further configured to receive a service message sent by the terminal device, where the service message carries service data and identifier information of the terminal device, and the sending module 730 is further configured to be used in the gateway device. Determining, when the gateway device does not have a user context of the terminal device corresponding to the identifier information, sending the service data to the second gateway device; the receiving module 710 is specifically configured to receive the second gateway device according to the The access point name corresponding to the service data determines a session creation request message that is sent when the gateway device needs to create a user context for the terminal device.

Optionally, as an embodiment, the session creation request message further carries address information of at least one local application server.

Optionally, as an embodiment, the first network device is an MME.

Optionally, as an embodiment, the gateway device is deployed in an access network or a metropolitan area network of the terminal device.

The foregoing and other operations and/or functions of the gateway device in the embodiment of the present invention are respectively omitted in order to implement the corresponding processes performed by the gateway device 204 in the data transmission method shown in FIG. 2, and are not described herein again for brevity.

As shown in FIG. 8, the network device 800 of the embodiment of the present invention includes a sending module 810 and a receiving module 820. It should be understood that the gateway device shown in FIG. 8 is only an example, and the gateway device of the embodiment of the present invention may further include other modules or units, or include modules similar to those of the respective modules in FIG. 8, or not including FIG. 8. All modules in .

The sending module 810 is configured to send a session creation request message to the first gateway device, where the session creation request message carries information used to instruct the first gateway device to create a user context for the terminal device.

The receiving module 820 is configured to receive a session creation response message sent by the first gateway device to respond to the session creation request message.

In the embodiment of the present invention, the network device sends a session creation request message to the first gateway device, so that the first gateway device can create a user context for the terminal device, and the first gateway device can implement the data of the terminal device according to the user context.

Optionally, as an embodiment, the network device is a second gateway device. Correspondingly, the receiving module 820 is specifically configured to receive the service data of the terminal device that is sent when the first gateway device determines that the user context of the terminal device is not on the first gateway device. The sending module 810 is specifically configured to: when the second gateway device determines, according to the access point name corresponding to the service data, that the first gateway device needs to create a user context for the terminal device, to the first gateway. The device sends a session creation request message.

Optionally, as an embodiment, the session creation request message further carries address information of at least one local application server, where the address information is used by the first gateway device to determine whether a target server of the service data of the terminal device is local. application server.

Optionally, as an embodiment, the network device is an MME.

The above-mentioned and other operations and/or functions of the network device in the embodiment of the present invention are respectively omitted in order to implement the corresponding processes performed by the network device 206 in the data transmission method shown in FIG. 2 for brevity.

As shown in FIG. 9, the gateway device 900 of the embodiment of the present invention includes a memory 910, a processor 920, a receiver 930, and a transmitter 940.

The memory 910 is used to store programs.

The processor 920 is configured to execute programs stored in the memory 910.

The receiver 930 is configured to receive, when the processor 920 executes the program in the memory 910, a session creation request message sent by the first network device, where the session creation request message is used to instruct the first gateway device to create a user for the terminal device. Contextual information.

The processor 920 is specifically configured to create a user context for the terminal device according to the session creation request message received by the receiver 930.

The receiver 930 is further configured to receive a service message sent by the terminal device, where the service message carries service data and address information of a target server of the service data.

The transmitter 940 is configured to locally send the service data to the target server by using the user context when the gateway device determines that the target server is a local application server according to the address information of the target server.

In the embodiment of the present invention, after receiving the session creation request message of the first network device, the gateway device creates a user context for the terminal device, so that the gateway device determines that the server corresponding to the target address of the service data of the terminal device is the local server, that is, the gateway. When the device determines the local network when the terminal accesses the network, directly sends the service of the terminal device to the local server directly at the gateway device. The data is such that the data sent by the terminal device to the local network is not forwarded by the upstream network device of the gateway device, thereby shortening the data transmission path, thereby improving the data transmission efficiency, and finally improving the user experience.

Optionally, as an embodiment, the receiver 930 is further configured to receive a DNS request message sent by the terminal device, where the DNS request message carries domain name information of a target address of the service data. The transmitter 940 is further configured to: when the gateway device determines, according to the domain name information of the target address, that the target server corresponding to the target address is a local application server, send a DNS response message to the terminal device, where the DNS response is The message carries address information of the target server.

Optionally, as an embodiment, the transmitter 940 is specifically configured to: when the gateway device determines that the domain name information of the target address exists in the domain name information of the at least one local application server on the gateway device, The terminal device sends a DNS response message.

Optionally, as an embodiment, the transmitter 940 is specifically configured to: when the gateway device determines that the address information of the target server exists in the address information of the at least one local application server on the gateway device, The user context locally sends the service data to the target server.

Optionally, as an embodiment, the first network device is a second gateway device. Correspondingly, the receiver 930 is further configured to receive a service message sent by the terminal device, where the service message carries service data and identifier information of the terminal device. The transmitter 940 is further configured to: when the gateway device determines that the user context of the terminal device corresponding to the identifier information is not on the gateway device, send the service data to the second gateway device. The receiver 930 is specifically configured to receive, by the second gateway device, a session creation request message that is sent when the gateway device needs to create a user context for the terminal device according to the access point name corresponding to the service data.

Optionally, as an embodiment, the first network device is an MME.

As shown in FIG. 10, the network device 1000 of the embodiment of the present invention includes a memory 1010 and a processor. 1020. Receiver 1030 and transmitter 1040.

The memory 1010 is for storing programs.

The processor 1020 is configured to execute a program stored in the memory 1010.

The transmitter 1040 is configured to send a session creation request message to the first gateway device when the processor 1020 executes the program in the memory 1010, where the session creation request message is used to instruct the first gateway device to create a user context for the terminal device. Information.

The receiver 1030 is configured to receive, when the processor 1020 executes a program in the memory 1010, a session creation response message sent by the first gateway device to respond to the session creation request message.

Optionally, as an embodiment, the network device is a second gateway device. Correspondingly, the receiver 1030 is specifically configured to receive service data of the terminal device that is sent when the first gateway device determines that the user context of the terminal device is not on the first gateway device. The transmitter 1040 is specifically configured to: when the second gateway device determines, according to the access point name corresponding to the service data, that the first gateway device needs to create a user context for the terminal device, to the first gateway. The device sends a session creation request message.

Optionally, as an embodiment, the network device is an MME.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

It will be apparent to those skilled in the art that the above description is convenient and concise for the description. For the specific working process of the system, the device and the unit, reference may be made to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

A data transmission method, comprising:

Receiving, by the first gateway device, a session creation request message sent by the first network device, where the session creation request message carries information used to instruct the first gateway device to create a user context for the terminal device;

The first gateway device creates a user context for the terminal device according to the session creation request message;

Receiving, by the first gateway device, a service message sent by the terminal device, where the service message carries service data and address information of a target server of the service data;

When the first gateway device determines that the target server is a local application server according to the address information of the target server, the service data is locally sent to the target server by using the user context.
The data transmission method according to claim 1, wherein before the first gateway device receives the service message sent by the terminal device, the data transmission method further includes:

Receiving, by the first gateway device, a domain name system DNS request message sent by the terminal device, where the DNS request message carries domain name information of a target address of the service data;

When the first gateway device determines that the target server corresponding to the service data is the local application server, the first gateway device sends a DNS response message to the terminal device, where the DNS response message carries the address information of the target server.
The data transmission method according to claim 2, wherein the first gateway device sends, according to the domain name information of the target address, that the target server corresponding to the target address is a local application server, and sends the data to the terminal device. DNS response messages, including:

When the first gateway device determines that the domain name information of the target address exists in the domain name information of the at least one local application server on the first gateway device, the first gateway device sends a DNS response message to the terminal device.
The data transmission method according to any one of claims 1 to 3, wherein the first gateway device determines that the target server is a local application server according to address information of the target server, and passes the user The context sends the service data locally to the target server, including:

When the first gateway device determines that the address information of the target server exists in the address information of the at least one local application server on the first gateway device, the user context is used to The target server locally sends the service data.
The data transmission method according to any one of claims 1 to 4, wherein the first network device is a second gateway device;

The data transmission method further includes:

Receiving, by the first gateway device, a service message sent by the terminal device, where the service message carries service data and identifier information of the terminal device;

When the first gateway device determines that the user context of the terminal device corresponding to the identifier information is not on the first gateway device, the first gateway device sends the service data to the second gateway device;

The first gateway device receives the session creation request message sent by the first network device, and includes:

The first gateway device receives, by the second gateway device, a session creation request message that is sent when the first gateway device needs to create a user context for the terminal device according to the access point name corresponding to the service data.
The data transmission method according to claim 5, wherein the session creation request message further carries address information of at least one local application server.
The data transmission method according to any one of claims 1 to 4, wherein the first network device is a mobility management network element MME.
The data transmission method according to any one of claims 1 to 7, wherein the first gateway device is deployed in an access network or a metropolitan area network of the terminal device.
A data transmission method, comprising:

The first network device sends a session creation request message to the first gateway device, where the session creation request message carries information used to instruct the first gateway device to create a user context for the terminal device;

The first network device receives a session creation response message sent by the first gateway device to respond to the session creation request message.
The data transmission method according to claim 9, wherein the first network device is a second gateway device;

The data transmission method further includes:

Receiving, by the second gateway device, the service data of the terminal device that is sent when the first gateway device determines that the user context of the terminal device is not on the first gateway device;

The sending, by the first network device, the session creation request message to the first gateway device includes:

Determining, by the second gateway device, that the first gateway device needs to create a user context for the terminal device according to the access point name corresponding to the service data, sending, by the second gateway device, the first gateway device to the first gateway device Session creation request message.
The data transmission method according to claim 10, wherein the session creation request message further carries address information of at least one local application server, and the address information is used by the first gateway device to determine service data of the terminal device. Whether the target server is a local application server.
The data transmission method according to claim 9, wherein the first network device is a mobility management network element MME.
A gateway device, comprising:

a receiving module, configured to receive a session creation request message sent by the first network device, where the session creation request message carries information used to instruct the first gateway device to create a user context for the terminal device;

a creating module, configured to create a user context for the terminal device according to the session creation request message;

The receiving module is further configured to receive a service message sent by the terminal device, where the service message carries service data and address information of a target server of the service data;

And a sending module, configured to send the service data locally to the target server by using the user context when the gateway device determines that the target server is a local application server according to the address information of the target server.
The gateway device according to claim 13, wherein the receiving module is further configured to receive a domain name system DNS request message sent by the terminal device, where the DNS request message carries domain name information of a target address of the service data. ;

The sending module is further configured to: when the gateway device determines, according to the domain name information of the target address, that the target server corresponding to the target address is a local application server, send a DNS response message to the terminal device, where the DNS response message is sent. Carrying the address information of the target server.
The gateway device according to claim 14, wherein the sending module is specifically configured to: when the gateway device determines that domain name information of the target address exists in domain name information of at least one local application server on the gateway device At the time, a DNS response message is sent to the terminal device.
The gateway device according to any one of claims 13 to 15, wherein the sending module is configured to: determine, in the address information of the at least one local application server on the gateway device, that the gateway device exists When the address information of the target server is described, the user is The context sends the service data locally to the target server.
The gateway device according to any one of claims 13 to 16, wherein the first network device is a second gateway device;

The receiving module is further configured to receive a service message sent by the terminal device, where the service message carries service data and identifier information of the terminal device;

The sending module is further configured to: when the gateway device determines that the user context of the terminal device corresponding to the identifier information is not on the gateway device, send the service data to the second gateway device;

The receiving module is specifically configured to receive, by the second gateway device, a session creation request message that is sent when the gateway device needs to create a user context for the terminal device according to the access point name corresponding to the service data.
The gateway device according to claim 17, wherein the session creation request message further carries address information of at least one local application server.
The gateway device according to any one of claims 13 to 16, wherein the first network device is a mobility management network element MME.
The gateway device according to any one of claims 13 to 19, wherein the gateway device is deployed in an access network or a metropolitan area network of the terminal device.
A network device, comprising:

a sending module, configured to send a session creation request message to the first gateway device, where the session creation request message carries information used to instruct the first gateway device to create a user context for the terminal device;

And a receiving module, configured to receive a session creation response message sent by the first gateway device to respond to the session creation request message.
The network device according to claim 21, wherein the network device is a second gateway device;

The receiving module is specifically configured to receive, when the first gateway device determines that the user context of the terminal device is not on the first gateway device, the service data of the terminal device that is sent;

The sending module is specifically configured to: when the second gateway device determines, according to the access point name corresponding to the service data, that the first gateway device needs to create a user context for the terminal device, to the first gateway device Send a session creation request message.
The network device according to claim 22, wherein said session creation is requested The request message further carries address information of at least one local application server, where the address information is used by the first gateway device to determine whether the target server of the service data of the terminal device is a local application server.
The network device according to claim 21, wherein the network device is a mobility management network element MME.