WO2013023526A1

WO2013023526A1 - Data transmission method and device

Info

Publication number: WO2013023526A1
Application number: PCT/CN2012/079474
Authority: WO
Inventors: 周燕飞; 张娟
Original assignee: 电信科学技术研究院
Priority date: 2011-08-12
Filing date: 2012-08-01
Publication date: 2013-02-21
Also published as: CN102427599B; CN102427599A

Abstract

Disclosed are a data transmission method and a data transmission device. By applying the technical solutions of the embodiments of the present invention, a core network control node, according to a manner of accessing a local network allowed by a terminal device (LIPA or remote access), sending corresponding indication information to a local gateway, so that the local gateway, when downlink data needs to be sent to the terminal device, sends the downlink data to the terminal device in a different manner. Therefore, the local gateway is capable of performing the transmission of downlink data by adopting a corresponding data plane interface according to a corresponding manner that the terminal device accesses the local network, so as to avoid the case that normal communication fails to be performed on a data connection due to a conflict between a specific transmission data plane interface and a practically applied manner of accessing a local network.

Description

The present invention claims the priority of the Chinese Patent Application entitled "Data Transmission Method and Apparatus" filed on August 12, 2011, the disclosure of which is hereby incorporated by reference. In this application. Technical field

The present invention relates to the field of communications technologies, and in particular, to a data transmission method and device. Background technique

The LIPA (Local IP Access) technology is a technology that allows a terminal to access a local network associated with the home base station through a Home base station (Home (evolved) NodeB, H(e)NB), which enables A terminal with IP (Internet Protocol) capability can access a local IP network, such as a home network or a corporate network, without going through the carrier core network. The terminal accesses the local network through a local gateway (LGW). In the 3GPP (The 3rd Generation Partnership Project) R10P interface, the local gateway and the home base station are implemented on the same physical entity. After R10, the local gateway can be implemented on a different physical entity from the home base station. As shown in FIG. 1, it is a schematic diagram of the R10 LIPA architecture in the prior art, where the LGW is on the same physical entity as the home base station.

When the terminal activates LIPA, a user plane is established between the local gateway and the core network, and a direct user path between the local gateway and the home base station is also established. As shown in FIG. 2, it is a schematic diagram of a logical architecture of a home base station subsystem in an LTE (Long Term Evolution) system, where a user plane between a local gateway and a core network is a local gateway and a SGW (Serving Gateway). ) between the S5 interfaces. In the terminal connection state, LIPA data is transmitted through the direct user path without passing through the S5 interface. After the terminal enters the idle state, the direct user path is released. If the LGW receives the downlink data, the LGW sends the first downlink data packet to the SGW through the S5 interface to trigger the core network. The control entity MME (Mobility Management Entity) paging the terminal, and the LGW buffers the remaining downlink data until the terminal establishes a direct user path in response to the paging, and then sends the downlink data to the terminal through the home base station.

When the LGW receives the downlink data of the idle terminal, the schematic diagram of the triggered service request process is as shown in FIG. 3, and includes the following steps:

Step S301: The LGW receives the downlink data.

Step S302: The LGW determines that there is currently no direct user path, and therefore, sends the first data packet to the SGW and buffers the remaining data.

Step S303: The SGW sends a downlink data notification (DL Data Notification) message to the MME. Step S304: The MME pages the terminal in a certain area.

Step S305: The terminal responds to the paging, and initiates a service request process, which is defined in 3GPP TS 23.401.

In this process, a direct user path between the home base station and the local gateway will be established.

Step S306: The LGW sends downlink data by using a direct user path.

As described above, in the prior art, the LIPA technology provides a method for a terminal to access a local network through a home base station associated with the LGW. Correspondingly, the remote access technology provides a method for enabling a terminal to access a local network through a macro base station or a home base station not associated with the LGW, that is, a method of accessing the local network in a non-LIPA (non-LIPA) manner, And the 3GPP SA1 working group proposes that when the user activates LIPA and leaves the local network coverage, the user can continue to access the local network through remote access. Since the terminal has left the home base station associated with the local gateway at this time, the direct user path is not available, and the data between the local network and the terminal needs to be transmitted through the core network.

In addition to remote access, 3GPP also defines an APN (Access Point Name) of the LIPA-conditional type, so that when the terminal initiates a LIPA request outside the home base station associated with the local gateway, it can be non-LIPA. Access to the local network. According to the prior art, the operation flow chart when the LGW receives the data is as shown in FIG. 4, and includes the following steps.

Step S401: When the LGW receives the downlink data, check whether the direct user path exists.

If yes, step S404 is directly performed;

If not, step S402 is performed.

Step S402: The LGW sends the first data packet to the core network to trigger paging, and buffers the remaining data packets.

Step S403: The LGW checks whether the direct user path is established.

If it is established, step S404 is performed;

If not established, continue to wait, and the waiting time and mode are based on the specific implementation.

Step S404: The LGW sends the buffered data through a direct user path.

In the process of implementing the present invention, the inventors have found that at least the following problems exist in the prior art: The 3GPP R1 1 P section allows the terminal to access the local network in a non-LIPA manner and supports between LIPA access and remote access. Conversion. Therefore, the following scenarios may occur:

Scenario 1. After the terminal that activates LIPA enters the idle state, it opens the local network and resides in the macro cell. Then the LGW receives the downlink data and triggers the core network to send the page. The terminal responds to the paging from the macro base station, at which point the network will automatically convert the LIPA connection to a remote access connection so that the terminal can continue to access the local network, ie the direct user path will not be established. However, according to the prior art, the LGW does not know whether the current terminal accesses by using LIPA or non-LIPA mode, and the LGW may wait for the establishment of the direct user tunnel (ie, stay in step S403 as shown in FIG. 4) without using The user plane interface between the core networks makes the remote access local network impossible.

Scenario 2: The terminal requests to establish a PDN (Public Data Network) connection in the macro base station. According to the subscription, the connection can be accessed in both LIPA and remote access modes, and the terminal is connected from the macro base station at this time. Therefore, the core network control node will adopt the remote access method. However, according to the prior art, the LGW does not know whether the current terminal adopts LIPA or remote access mode. Into, the LGW may wait for the establishment of a direct user tunnel without using a user plane interface with the core network, thereby making the remote access local network impossible.

Scenario 3: The terminal activates LIPA in the home base station cell. Since the target base station is a macro base station handover after the terminal moves, the connection should be changed to the remote access mode after the handover. However, there is no information in the existing mechanism to notify the LGW to perform the above conversion. Therefore, after switching, the LGW will not use the user plane interface with the core network, which may result in remote access to the local network.

Scenario 4: The terminal establishes the above PDN connection in the macro base station, and the target base station is a handover of the home base station that allows LIPA to be activated due to the terminal movement. After the switchover, the above connection should be changed to the LIPA mode. However, there is no information in the existing mechanism to notify the LGW to perform the above conversion. Therefore, after the handover, the LGW may still use the user plane interface with the core network, which may result in the failure of LIPA. Summary of the invention

The embodiment of the invention provides a data transmission method and device, which solves the problem that the local gateway cannot perform normal data transmission when the terminal device accesses the local network by using the non-LIPA mode in the prior art solution.

To achieve the above objective, an embodiment of the present invention provides a data transmission method, which at least includes the following steps:

When the local gateway needs to send downlink data to the terminal device, the local gateway determines whether the indication information sent by the core network control node is currently received.

If the determination result is yes, the local gateway identifies the content of the indication information; when the content of the indication information is used to indicate that the local gateway uses the user plane interface with the core network for data transmission, the local gateway passes And the user plane interface of the core network sends downlink data to the terminal device; when the content of the indication information is used to indicate that the local gateway uses a direct user path for data transmission, the local gateway sends the terminal to the terminal through a direct user path. The device sends downlink data. In another aspect, the embodiment of the present invention further provides a local gateway, where the method further includes: a receiving module, configured to receive a message sent to the local gateway;

a determining module, configured to: when the downlink data needs to be sent to the terminal device, determine whether the receiving module currently receives the indication information sent by the core network control node;

An identification module, configured to: when the determination result of the determining module is yes, identify the content of the indication information;

a sending module, configured to: when the content of the indication information is used by the identification module to indicate that the local gateway uses the user plane interface with the core network for data transmission, to the terminal device by using a user plane interface with the core network Sending the downlink data, or sending the downlink data to the terminal device through the direct user path when the content of the indication information is that the local gateway uses the direct user path for data transmission.

On the other hand, an embodiment of the present invention further provides a data transmission method, which includes at least the following steps:

The core network control node determines a manner in which the terminal device is currently allowed to access the local network;

According to the determined result, the core network control node sends a corresponding indication message to the local gateway. The embodiment of the present invention further provides a core network control entity, which at least includes: a determining module, configured to determine the currently allowed terminal How the device accesses the local network;

The sending module is configured to send the corresponding indication information to the local gateway according to the determined result. Compared with the prior art, the technical solution provided by the embodiment of the present invention has the following advantages: by applying the technical solution of the embodiment of the present invention, The core network control node sends corresponding indication information to the local gateway according to the manner in which the terminal device allows access to the local network (LIPA or remote access), so that the local gateway passes different manners when it needs to send downlink data to the terminal device. Sending downlink data to the terminal device, thereby enabling the local gateway to access the local network according to the corresponding terminal device The network mode uses the corresponding data plane interface for downlink data transmission, avoiding the situation that the data connection cannot be normally communicated due to the contradiction between the specific transmission data plane interface and the actual applied access local network mode. DRAWINGS

1 is a schematic diagram of an R10 LIPA architecture in the prior art;

The schematic diagram of the logical architecture of the home base station subsystem in the LTE system in the prior art; FIG. 3 is a schematic flowchart of the service request process triggered by the LGW receiving the downlink data of the idle state terminal in the prior art;

4 is a flow chart of operations in the prior art when the LGW receives data;

FIG. 5 is a schematic flowchart of a data transmission method according to an embodiment of the present invention; FIG. 6 is a schematic flowchart of a data transmission method in a specific scenario according to an embodiment of the present invention;

FIG. 7 is a schematic flowchart of a data transmission method in a specific scenario according to Embodiment 1 of the present invention;

8 is a schematic flowchart of a data transmission method in a specific scenario according to Embodiment 2 of the present invention;

FIG. 9 is a schematic flowchart of a data transmission method in a specific scenario according to Embodiment 3 of the present invention;

10 is a schematic flowchart of a data transmission method in a specific scenario according to Embodiment 4 of the present invention;

11 is a schematic flowchart of a data transmission method in a specific scenario according to Embodiment 5 of the present invention;

FIG. 12 is a schematic structural diagram of a local gateway according to an embodiment of the present disclosure;

FIG. 13 is a schematic structural diagram of a core network control entity according to an embodiment of the present invention. detailed description

According to the prior art, according to the existing LIPA technology, after the terminal device activated by the LIPA mode enters the idle state, if downlink data occurs on the LIPA connection, the local gateway sends the first data packet to the core network to trigger the search. The local data packet is sent to the terminal device through the direct user path after the terminal device enters the connected state to establish a direct user path.

However, the 3GPP Release 11 P section allows the terminal device to access the local network in a non-LIPA mode. At this time, if the local gateway receives the downlink data of the terminal that is already in the idle state, the local gateway cannot determine which way the terminal device adopts. In the local network, the downlink data can only be buffered according to the existing process, and the direct user path is established. In this case, if the terminal device actually adopts the non-LIPA mode, it will cause The downlink data connection cannot continue normal communication because there is no direct user path establishment.

In order to overcome such a defect, the embodiment of the present invention provides a data transmission method. In a system scenario compatible with the LIPA mode and the non-LIPA mode, the local gateway can adopt a corresponding manner according to the manner in which the terminal device accesses the local network. The transmission data plane interface realizes the normal transmission of downlink data.

As shown in FIG. 5, it is a schematic flowchart of a data transmission method according to an embodiment of the present invention, where the method specifically includes the following steps:

Step S501: When the local gateway needs to send downlink data to the terminal device, the local gateway determines whether the indication information sent by the core network control node is currently received.

If the result of the determination is yes, step S502 is performed;

If the result of the determination is no, step S505 is performed.

In a specific application scenario, the judgment process in this step can be classified into the following two cases according to the difference in the specific message transmission mode:

Case 1: The local gateway determines that the currently received core network control node is directly sent to the local Whether the message of the local gateway carries the indication information.

Case 2: The local gateway determines whether the currently received message sent by the core network control node to the local gateway through the intermediate network node carries the indication information.

In a specific implementation scenario, the specific type of the core network control node may also change correspondingly according to the specific system type difference. When the current system is a UMTS (Universal Mobile Telecommunications System) system, The core network control node may be an SGSN (Serving GPRS Support Node, GPRS, General Packet Radio Service, General Packet Radio Service), and when the current system is an LTE system, the foregoing core network The control node may specifically be ΜΜΕ, and the type change of the specific core network control entity does not affect the protection scope of the present invention.

Further, it can be seen from the above description that in both cases, the core network control entity determines the manner in which the current terminal device accesses the local network, but in the process of sending subsequent messages, the specific message sending manner is different. In the first case, the corresponding message is sent directly to the local gateway, and in the second case, the message is forwarded through the intermediate network node, and the specific case is determined according to the network architecture of the terminal device currently accessing the network, and can be adopted. The existing information in the existing protocol carries the corresponding indication information. In the actual application scenario, the specific message type may include at least a Modify Bearer Request message and a PDP (Packet Data Protocol). Context request message, change notification request (Change Notification Request) message, create session request (Create Session Request) message, create PDP context request (Create PDP Context Request) message, etc., of course, can also be other types of messages, as long as The transmission of the corresponding indication information may be satisfied, and the change of the specific message type does not affect the protection scope of the present invention.

In a specific implementation scenario, the foregoing indication information may be included in an existing message, for example, an IE (Information Element) is added to the existing message, and the value of the IE is different according to the value of the IE. Indication, if 0 is used, it means that the direct user path is adopted, and the time table is taken. The interface between the core network and the core network is defined, or two IEs are defined to correspond to two different indications. Alternatively, the existing IE may be extended to implement, for example, an idle bit in the existing IE may be extended to indicate different indication information.

Step S502: The local gateway identifies the content of the indication information.

When the content of the indication information indicates that the local gateway uses the user plane interface with the core network for data transmission, step S503 is performed;

When the content of the indication information indicates that the local gateway uses the direct user path for data transmission, step S504 is performed.

Step S503: The local gateway sends downlink data to the terminal device by using a user plane interface with the core network.

In a specific application scenario, the local gateway and the terminal device establish a corresponding data transmission path through a user plane interface with the core network, and the local gateway and the terminal device can perform corresponding data through the data transmission path. Data transmission includes not only the transmission of downlink data but also the reception of uplink data sent by the terminal device.

Step S504: The local gateway sends downlink data to the terminal device by using the direct user path.

If there is currently no direct user path, the implementation of this step needs to be implemented after the direct user is established.

Of course, in this case, the uplink data transmitted by the terminal device through the direct user path is also included.

Step S505: The local gateway continues to wait for the indication information sent by the core network control node or sends the downlink data by using a currently used data interface.

If the local gateway has a data interface in use at this time, the downlink data is sent by using the data interface in use, otherwise the indication information is continued.

Correspondingly, on the core network control node side, connection establishment, service request, and handover are required. The process of determining the manner in which the current terminal device accesses the local network, including the LIPA mode and the remote access mode.

When the core network control node determines that the terminal device is currently allowed to access the local network in LIPA mode, the core network control node sends an indication to the local gateway that the local gateway uses the direct user path for data transmission. a message indicating that the local gateway performs corresponding data transmission with the terminal device through the direct user path;

When the core network control node determines that the terminal device is currently allowed to access the local network in a remote manner, the core network control node sends a user plane interface that indicates that the local gateway uses the core network to the local gateway. The message indicating the information of the data transmission indicates that the local gateway adopts a user plane interface with the core network to perform corresponding data transmission with the terminal device.

For details on how to send the specified information, refer to the above description. Similar to this, it will not be repeated here.

Compared with the prior art, the technical solution proposed by the embodiment of the present invention has the following advantages: By applying the technical solution of the embodiment of the present invention, the core network control node is based on the manner in which the terminal device allows access to the local network (LIPA or remote connection). And sending the corresponding indication information to the local gateway, so that the local gateway sends the downlink data to the terminal device in different manners when the downlink data needs to be sent to the terminal device, so that the local gateway can be connected according to the corresponding terminal device. The method of entering the local network uses the corresponding data plane interface to transmit downlink data, so as to avoid the situation that the data connection cannot be normally communicated due to the contradiction between the specific transmission data plane interface and the actual applied access local network mode.

The technical solutions proposed by the embodiments of the present invention are described below in conjunction with specific application scenarios.

The embodiment of the invention provides a method for notifying the LGW to perform data transmission with the terminal device in different manners in different situations:

When the core network control node decides to allow the terminal device to access the local network in a non-LIPA mode, The corresponding indication information is sent to the local gateway through the intermediate network node, indicating to the user that the user plane interface with the core network should be used instead of the direct user path for downlink data transmission, and further uplink data reception.

When the core network control node decides to allow the terminal device to access the local network in LIPA mode, the corresponding indication information is sent to the local gateway directly or through the intermediate network node, indicating to the user that the direct user path should be used for downlink data transmission, and further Receive of upstream data.

Corresponding to the foregoing description, the technical solution proposed by the embodiment of the present invention is modified to the core network control node side: when the core network control node determines that the terminal device needs to access the local network in a non-LIPA manner, it needs to send to the local gateway. The indication information of the user plane interface with the core network may be used, and the indication information may be included in an existing message. When the core network control node determines that the terminal device needs to access the local network in the LIPA mode, the local gateway needs to send the indication information of using the direct user path, and the indication information may be included in the existing message.

The above two indications can be implemented by adding IE to the existing message, or by extending the existing IE. In the method implemented by adding a new IE, one IE may be added, and different indication values may be used to indicate different indication information, or two IEs may be newly defined to represent different indication information respectively; In the method, the idle bits in the existing IE can be extended to represent different indication information.

The change to the local gateway side is: When the local gateway needs to send downlink data to the terminal device, it needs to continue to determine whether the local gateway receives the corresponding indication information; if the indication information is received, the corresponding interface is used according to the content of the indication information. The terminal device transmits data.

Based on the technical idea of the foregoing, as shown in FIG. 6, the schematic diagram of the data transmission method proposed by the embodiment of the present invention in the service request process initiated by the network includes the following steps:

Step S601: The local gateway receives downlink data that needs to be sent to the terminal device.

Step S602: The local gateway sends the first data packet of the downlink data to the core network, and caches other data packets. Specifically, the first data packet may be sent to an intermediate network entity (for example, an SGW) on the core network side, and then further notified to the core network control entity (for example, the MME) to page the terminal device, or directly sent to the terminal device. The core network control entity (for example, SGSN) triggers the core network control entity to page the terminal device.

After paging to the terminal device, the core network control entity determines the manner in which the terminal device is currently allowed to access the local network, and sends corresponding indication information to the local gateway according to the determined result, and notifies the local gateway to notify the local gateway in a corresponding manner. The terminal device sends the downlink data, and the corresponding indication information may be carried in an existing message and sent to the local gateway.

Step S603: The local gateway determines whether the indication information sent by the core network control entity is received. If yes, step S604 is performed;

If not received, continue to wait until the corresponding indication is received.

Step S604: The local gateway identifies the content of the indication information.

When the content of the indication information is used to indicate that the local gateway uses the user plane interface with the core network for data transmission, step S605 is performed;

When the content of the indication information indicates that the local gateway uses the direct user path for data transmission, step S606 is performed.

Step S605: The local gateway sends the downlink data through a user plane interface with the core network. Of course, in the subsequent processing, the local gateway can also receive the uplink data returned by the terminal device through the user plane interface.

Step S606: The local gateway determines whether a direct user path between the home base station and the home base station has been established. If it has been established, step S607 is performed;

If not established, it waits for the establishment of the direct user path, and returns to step S606. Step S607: The local gateway sends the downlink data to the corresponding terminal device through the direct user path.

In subsequent processing, the local gateway may also receive the terminal device through the direct user path. Upward data back.

Based on the above technical idea, the technical solution proposed by the embodiment of the present invention will be further described below in combination with different specific application scenarios.

Embodiment 1

In the LTE system, the core network control node is the MME. The MME is connected to the LGW through the SGW, and the interface between the SGW and the LGW, that is, the user plane interface between the LGW and the core network is the S5 interface.

The terminal device activates LIPA in the home base station cell, and then the target cell is switched to the macro cell due to the terminal movement.

FIG. 7 is a schematic flowchart of a data transmission method in a specific scenario according to Embodiment 1 of the present invention, which specifically includes the following steps:

Step S701: The source home base station initiates an S1 handover process, and performs corresponding processing according to the process specified in TS 23.401 (specifically, steps 1 to 15).

Step S702: The MME sends a Change Notification Request message to the SGW, where the indication information indicating that the LGW uses the user plane interface with the core network is carried, and the indication information may be represented by using a newly defined IE, and when the IE value is 0, Use the user plane interface with the core network.

Step S703: The SGW sends a Change Notification Request message to the LGW.

Steps S704 and S705: The LGW returns a response message Change Notification Response message to the MME through the SGW.

The subsequent operations are switched according to the prior art.

It should be noted that the switching subsequent operations and the steps S702 to S705 can be performed in parallel without a sequence. After step S705 is completed, the data path to the local network is:

LGW<->SGW<-> macro base station.

Embodiment 2 In the UMTS system, the core network control node is the SGSN, and the user plane interface between the SGSN and the LGW is the Gn interface.

The terminal activates LIPA in the home base station cell, then enters the idle state and camps on the macro cell, after which the LGW receives the downlink data.

As shown in FIG. 8 , it is a schematic flowchart of a data transmission method in a specific scenario proposed in Embodiment 2 of the present invention, which specifically includes the following steps:

Step S801: The LGW receives downlink data that needs to be sent to the UE.

Step S802: The LGW sends the first data packet of the downlink data to the SGSN, and caches other data packets.

Step S803: The SGSN pages the UE in a certain area.

Step S804: The UE responds to the paging of the SGSN, and accesses the network through a macro base station (RNC).

The SGSN determines that the UE accesses the RNC at this time. Therefore, the remote access mode is used to allow the terminal device to access the local network, that is, the UE is allowed to access the local network by using the non-LIPA mode.

Step S805: The SGSN carries the foregoing indication information in the update PDP context request message and sends the indication information to the LGW to notify the user to use the data plane interface with the core network. The indication information may be added to the IE implementation in the updated PDP context request message.

After completing the above notification, after updating the corresponding context information, the LGW returns a corresponding update PDP context response message to the SGSN.

Step S806: The LGW sends the corresponding downlink data to the UE directly through the user plane interface with the core network.

Specifically, the LGW sends the downlink data to the SGSN through the Gn interface with the SGSN, and then the SGSN sends the downlink data to the RNC, and the RNC sends the downlink data to the UE through the bearer with the UE, and The user plane interface receives uplink data sent by the UE.

Embodiment 3

The application scenario of this embodiment is in an LTE system, and the core network control node is an MME. The terminal activates LIPA in the home base station cell, then enters the idle state and camps on the macro cell, after which the LGW receives the downlink data.

As shown in FIG. 9, a schematic flowchart of a data transmission method in a specific scenario proposed in Embodiment 3 of the present invention includes the following steps:

Step S901: The LGW receives downlink data that needs to be sent to the UE.

Step S902: The LGW sends the first data packet of the downlink data to the SGW, and caches other data packets.

Step S903: The SGW sends a downlink data notification to the MME.

Step S904: The MME pages the UE in a certain area.

Step S905: The UE responds to the paging of the MME, and accesses the network through the macro base station (eNB).

The MME determines that the UE accesses the eNB through the eNB. Therefore, the remote device is used to allow the terminal device to access the local network, that is, the UE is allowed to access the local network by using the non-LIPA mode.

Step S906: The MME carries the foregoing indication information in a Modify Bearer Request message and sends the indication information to the SGW.

The indication information can be implemented by extending the Indication Flags IE in the Modify Bearer Request message. The coding format of the Indication Flags IE is shown in Table 1.

Table 1 Indication Flags The encoding format of the IE can be extended to the 3rd and 4th bits of the 7th byte. For example, when the 3rd bit is set to 1, the direct user path is used, and when the 4th bit is set to 1, the use and core network are used. User interface interface between.

Step S907: The SGW forwards the foregoing message to the LGW, and the LGW uses the data plane interface with the core network by using the indication information in the message.

After completing the foregoing notification, after completing the corresponding bearer modification, the local gateway returns a corresponding 7-load tampering response (Modify Bearer Response) message to the SGW, and the SGW further feeds back the response to the MME. Step S908: The LGW sends the corresponding downlink data to the UE directly through the user plane interface with the core network.

Specifically, the LGW sends the downlink data to the SGW through the S5 interface between the SGW and the SGW, and then the SGW sends the downlink data to the eNB, and the eNB sends the downlink data to the UE by using the bearer between the UE and the UE. The user plane interface receives uplink data sent by the UE.

Embodiment 4:

The application scenario of this embodiment is that in the LTE system, the core network control node is the MME.

The UE requests to establish a PDN connection in the LTE system macro cell, and the PDN allows access in LIPA mode and non-LIPA mode according to the subscription data. Since the UE currently accessing the cell is a macro cell, the MME will instruct the local gateway to use the data plane interface with the core network.

As shown in FIG. 10, it is a schematic flowchart of a data transmission method in a specific scenario proposed in Embodiment 4 of the present invention, which specifically includes the following steps:

Step S1001: The UE initiates a PDN connection establishment request in the macro cell.

Step S1002: According to the subscription data, the MME can know that the requested PDN can be accessed through the remote access mode. Therefore, an indication is added in the Create Session Request Create Session Request message to indicate that the LGW uses the interface with the core network.

This indication can be reflected in the way of adding IE.

Step S1003: The SGW sends a Create Session Request message carrying the indication to step S1004, and the LGW returns a Create Session Response message.

Step S1005: After completing the PDN connection establishment process, after the PDN connection is established, according to the indication from the MME, the LGW will use the interface with the core network to send downlink data.

Embodiment 5:

In the LTE system, the UE requests a PDN connection in the macro cell, and the PDN connection can be The LIPA mode or the non-LIPA mode access, and then the target cell is the handover of the home base station cell due to the UE mobility. According to the subscription data, the MME can know that the LIPA can be activated after the terminal is switched, and therefore an indication will be sent to the LGW.

As shown in FIG. 11, a schematic flowchart of a data transmission method in a specific scenario proposed in Embodiment 5 of the present invention includes the following steps:

Step S1101: The source macro base station initiates an S1 handover due to the terminal moving, and is performed according to the handover procedure specified in TS23.401 (specifically, steps l-14b).

Step S1102: Since the target base station is a home base station that allows LIPA to be activated, the MME notifies the LGW to use the direct user path, and specifically adds an indication to the Modify Bearer Request message, instructing the LGW to use the direct user path to transmit data.

The indication information can be implemented by adding an IE. The IE content can be related to the direct user path, such as the TEID (Tunnel Endpoint Identity) and the IP address of the direct user path.

Step S1103: The SGW sends the foregoing message to the LGW.

Step S1104: After receiving the indication, the LGW prepares to convert the data plane interface to the direct user path, and returns a Modify Bearer Response message.

Continue to perform subsequent operations. Note that since the terminal will allow the LIPA to be activated after the handover, the MME will establish a direct user path between the home base station and the LGW during the handover process, and the order of execution of the operation and its indication is not within the scope of the method. Inside.

Compared with the prior art, the technical solution proposed by the embodiment of the present invention has the following advantages: By applying the technical solution of the embodiment of the present invention, the core network control node is based on the manner in which the terminal device allows access to the local network (LIPA or remote connection). And sending the corresponding indication information to the local gateway, so that the local gateway sends the downlink data to the terminal device in different manners when the downlink data needs to be sent to the terminal device, so that the local gateway can be connected according to the corresponding terminal device. The method of entering the local network uses the corresponding data plane interface to transmit downlink data, avoiding the specific transmission The contradiction between the data plane interface and the actual applied access to the local network mode causes the data connection to fail to communicate normally.

In order to implement the technical solution of the embodiment of the present invention, the embodiment of the present invention further provides a gateway device, which is shown in FIG. 12, and is applied to the system as a local gateway, and at least includes: a receiving module 1201, configured to receive and send a message to the local gateway;

The determining module 1202 is configured to determine, when the downlink data needs to be sent to the terminal device, whether the receiving module 1201 currently receives the indication information sent by the core network control node;

The identifying module 1203 is configured to: when the determining result of the determining module 1202 is YES, identify the content of the indication information;

The sending module 1204 is configured to: when the identifying module 1203 identifies that the content of the indication information is to indicate that the local gateway uses the user plane interface with the core network for data transmission, by using a user interface with the core network The terminal device sends the downlink data, or when the identifier module 1203 identifies that the content of the indication information is that the local gateway uses the direct user path for data transmission, sending the downlink data to the terminal device by using the direct user path. . .

The determining module 1202 is specifically configured to:

Determining whether the message sent by the core network control node currently received by the receiving module 1201 to the local gateway carries the indication information; or

And determining whether the indication information is carried in the message that the core network control node currently received by the receiving module 1201 sends to the local gateway through the intermediate network node.

In a specific implementation scenario,

The identifying module 1203 is further configured to: when the determining result of the determining module 1202 is negative, instructing the determining module 1202 to continue waiting for the indication information sent by the core network control node, or sending by using a data interface currently in use. The downlink data.

If the local gateway has a data interface in use at this time, the downlink data is sent by using the data interface in use, otherwise, the indication information is continued. Further, the embodiment of the present invention further provides a core network control entity, and a schematic structural diagram thereof is shown in FIG. 13, which at least includes:

The determining module 1301 is configured to determine a manner in which the terminal device is currently allowed to access the local network. The sending module 1302 is configured to send, according to the determined result, a corresponding indication message to the local gateway, where the sending module 1302 is specifically configured to:

Sending a message carrying the corresponding indication information directly to the local gateway; or

A message carrying the corresponding indication information is sent to the local gateway through the intermediate network node. Further, when the current system is a UMTS system, the core network control node is specifically

SGSN; When the current system is an LTE system, the core network control node is specifically an MME.

In a specific implementation scenario, the manner in which the determining module 1301 determines that the terminal device is currently allowed to access the local network includes the LIPA mode and the remote access mode.

The sending module 1302 is specifically configured to:

When the determining module 1301 determines that the terminal device is currently allowed to access the local network in LIPA mode, sending a message carrying the indication information indicating that the local gateway uses the direct user path for data transmission to the local gateway;

When the determining module 1301 determines that the terminal device is currently allowed to access the local network in a remote manner, sending, to the local gateway, a message carrying indication information indicating that the local gateway uses the user plane interface with the core network for data transmission. .

Through the description of the above embodiments, those skilled in the art can clearly understand that the embodiments of the present invention can be implemented by hardware, or can be implemented by means of software plus necessary general hardware platform. Based on the understanding, the technical solution of the embodiment of the present invention may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc.). A number of instructions are included to cause a computer device (which may be a personal computer, a server, or a network side device, etc.) to perform the methods described in various implementation scenarios of embodiments of the present invention.

A person skilled in the art can understand that the drawings are only a schematic diagram of a preferred implementation scenario, and the modules or processes in the drawings are not necessarily required to implement the embodiments of the present invention.

Those skilled in the art can understand that the modules in the apparatus in the implementation scenario may be distributed in the apparatus for implementing the scenario according to the implementation scenario description, or may be correspondingly changed in one or more devices different from the implementation scenario. The modules of the above implementation scenarios may be combined into one module, or may be further split into multiple sub-modules.

The serial numbers of the foregoing embodiments of the present invention are merely for description, and do not represent the advantages and disadvantages of the implementation scenarios. The examples are not limited thereto, and any changes that can be made by those skilled in the art should fall within the scope of the business restrictions of the embodiments of the present invention.

Claims

Rights request

A data transmission method, characterized in that it comprises at least the following steps:

If the determination result is yes, the local gateway identifies the content of the indication information; when the content of the indication information is used to indicate that the local gateway uses the user plane interface with the core network for data transmission, the local gateway passes And the user plane interface of the core network sends downlink data to the terminal device; when the content of the indication information is used to indicate that the local gateway uses a direct user path for data transmission, the local gateway sends the terminal to the terminal through a direct user path. The device sends downlink data.

2. The method according to claim 1, wherein the local gateway determines whether the indication information sent by the control node of the core network is currently received, specifically:

The local gateway determines whether the currently received message sent by the core network control node directly to the local gateway carries the indication information; or

The local gateway determines whether the currently received message sent by the core network control node to the local gateway through the intermediate network node carries the indication information.

3. The method of claim 1 or 2, wherein

When the current system is a UMTS system, the core network control node is specifically an SGSN;

When the current system is an LTE system, the core network control node is specifically an MME.

The method according to claim 2, wherein the message is specifically: carrying a modification request message; or

Update the PDP context request message; or,

Change the notification request message; or,

Create a session request message; or, Create a PDP context request message.

The method of claim 1, wherein, after the local gateway determines whether the indication information sent by the core network control node is received, the method further includes:

If the judgment result is no, the local gateway continues to wait for the indication information sent by the core network control node or sends the downlink data by using the currently used data interface.

6. A local gateway, comprising: at least:

a receiving module, configured to receive a message sent to the local gateway;

The local gateway according to claim 6, wherein the determining module is specifically configured to:

Determining whether the indication message directly carried by the core network control node currently received by the receiving module to the local gateway carries the indication information; or

And determining, by the core network control node currently received by the receiving module, whether the information is sent by the intermediate network node to the local gateway.

8. The local gateway of claim 6 wherein:

The identifying module is further configured to: when the determining result of the determining module is negative, instructing the determining module to continue to wait for the indication information sent by the core network control node or to instruct the sending module to adopt The downlink data is transmitted using a data interface currently in use.

9. A data transmission method, characterized in that it comprises at least the following steps:

According to the determined result, the core network control node sends a corresponding indication letter to the local gateway.

The method according to claim 9, wherein the core network control node sends corresponding indication information to the local gateway, specifically:

The core network control node directly sends a message carrying the corresponding indication information to the local gateway; or

The core network control node sends a message carrying the corresponding indication information to the local gateway through the SGW.

11. The method of claim 9 or 10, wherein

The method according to claim 10, wherein the message is specifically: carrying a modification request message; or

Update the PDP context request message; or,

Change the notification request message; or,

Create a session request message; or,

Create a PDP context request message.

The method according to claim 9, wherein the manner in which the core network control node determines that the terminal device is currently allowed to access the local network includes the LIPA mode and the remote access mode.

When the core network control node determines that the terminal device is currently allowed to access the local network in LIPA mode, the core network control node sends a carrying indication to the local gateway to enable the local gateway to enable a message for indicating information of data transmission using a direct user path;

When the core network control node determines that the terminal device is currently allowed to access the local network in a remote manner, the core network control node sends a user plane interface that indicates that the local gateway uses the core network to the local gateway. A message indicating the information of the data transmission.

The method according to claim 13, wherein the indication information is specifically carried in the message by:

Carrying the indication information by adding an IE to the message; or

The carrying of the indication information is implemented by extending an existing IE.

15. A core network control entity, characterized in that it comprises at least:

a determining module, configured to determine a manner in which the terminal device is currently allowed to access the local network;

a sending module, configured to send, according to the determined result, corresponding indication information to the local gateway, where

The core network control entity according to claim 15, wherein the sending module is specifically configured to:

A message carrying the corresponding indication information is sent to the local gateway through the intermediate network node.

The core network control entity according to claim 15 or 16, wherein when the current system is a UMTS system, the core network control node is specifically an SGSN;

The core network control entity according to claim 15, wherein the determining, by the determining module, the manner in which the terminal device is allowed to access the local network, specifically includes a LIPA mode and a remote access mode; :

When the determining module determines that the terminal device is currently allowed to access the local network in LIPA mode, sending, to the local gateway, a message carrying indication information indicating that the local gateway uses a direct user path for data transmission; When the determining module determines that the terminal device is currently allowed to access the local network in a remote manner, sending a message to the local gateway carrying indication information indicating that the local gateway uses the user plane interface with the core network for data transmission.