WO2011020418A1

WO2011020418A1 - Connection activation method for changing serving gateway while terminal is converted to connection state and system thereof

Info

Publication number: WO2011020418A1
Application number: PCT/CN2010/075929
Authority: WO
Inventors: 周娜; 霍玉臻
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-08-21
Filing date: 2010-08-12
Publication date: 2011-02-24
Also published as: CN101998567B; CN101998567A

Abstract

A connection activation method for changing the Serving Gateway (S-GW) while a terminal is converted to the connection state is provided. The method includes that: when the terminal is converted to the connection state from the idle state, if a Mobility Management Entity (MME) determines the S-GW needs to be changed, an establishment/activation process of an IP shunt access is initiated, and the S-GW is changed, wherein the MME determines the S-GW needs to be changed if the wireless-side network element of the IP shunt access is changed and the current serving gateway is a Local Serving Gateway (L-SGW), or the wireless-side network element of the IP shunt access is not changed and the current S-GW is a core S-GW. It is also provided a connection activation system for changing an S-GW while a terminal is converted to the connection state. The method and the system resolve the problem that the data is not transmitted smoothly due to no interfaces between the L-SGW and the object wireless-side network element, realize effectively the activation mechanism of the IP shunt access after the wireless side network element is changed, and improve user experience.

Description

Method and system for changing connection of service gateway when terminal is switched to connected state

The present invention relates to mobile communication technologies, and in particular, to a connection activation method and system for changing a service gateway when a terminal is switched to a connected state. Background technique

The 3rd Generation Partnership Project (3GPP) evolved Evolved Packet System (EPS) consists of the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW or PDN GW), Home Subscriber Server (HS S) 3, GPP Authentication, Authorization and Accounting (AAA) server, Policy and Charging Rules Function (PCRF) entity and other supporting nodes. 1 is a schematic diagram of a mobile communication network connection in the prior art. As shown in FIG. 1, the mobility management entity is responsible for control planes such as mobility management, non-access layer signaling processing, and user mobility management context management. Working; both the S-GW and the P-GW belong to the core network gateway, and the S-GW is an access gateway device connected to the E-UTRAN, which forwards data between the E-UTRAN and the P-GW, and is responsible for waiting for paging data. Caching; P-GW is a border gateway between EPS and Packet Data Network (PDN), which is responsible for PDN access and forwarding data between EPS and PDN.

For a Universal Terrestrial Radio Access Network (UTRAN) system, the core network gateway may be a Serving GPRS Support Node (SGSN) or a Gateway GPRS Support Node (Gateway GPRS Support). Node, GGSN).

In addition to supporting access to the mobile core network, the mobile communication system can also support the IP offload function. Under the condition that the wireless side network element has IP offload capability and the user subscribes to allow IP offload, the terminal can implement other IP devices or interconnections of the home network. Local access to the network. The addition of the local gateway in Figure 1 provides strong support for IP offloading technology. The local gateway acts as a gateway for local access to external networks (such as the Internet), providing address allocation, accounting, packet filtering, policy control, and data offloading. , NAS/S1-AP/RANAP (Radios Access Network Application Part) / GTP (General Tunneling Protocol) / PMIP (Proxy Mobile IP) / MIP (Mobile IP) , Mobile IP protocol) Message parsing, NAT (Network Address Translation), IP offload policy routing and execution, etc. The local gateway can be L-SGW (Local SGW, Local SGW) and L-PGW (Local PGW, Local PGW), which can also be a separate L-PGW, can be a local GGSN (L-GGSN, Local GGSN) and a local SGSN (L-SGSN, Local SGSN), can be a separate L-GGSN, and can be a data offload function. entity.

The home base station is a small, low-power base station deployed in indoor places such as homes and offices. The main purpose is to provide users with higher service rates and lower the cost of using high-speed services, while making up for existing distributed Insufficient coverage of cellular wireless communication systems. The advantages of home base stations are affordable, convenient, low power output, plug and play, and more. In the home base station system, the home base station is a wireless side network element. The home base station can be directly connected to the core network (as shown in FIG. 1); FIG. 2 is a schematic diagram of another mobile communication network connection in the prior art. As shown in FIG. 2, the home base station can also use the home base station gateway as the logical network element. Access to the core network, where the main functions of the home base station gateway are: verifying the security of the home base station, handling the registration of the home base station, performing operation and maintenance management on the home base station, configuring and controlling the home base station according to the operator's requirements, and responsible for exchanging the core network And the data of the home base station; FIG. 3 is a schematic diagram of another mobile communication network connection in the prior art, as shown in FIG. 3, when there is a home base station gateway, the local gateway can also be home Set up with the base station gateway. In addition, the home base station gateway can also be combined with the home base station. Taking the Long Term Evolution (LTE) mobile communication network architecture as an example, FIG. 4 is a schematic diagram of the IP offloaded data flow of the mobile communication system in the prior art. As shown in FIG. 4, the data flow connected by the core network is at the terminal and the wireless side network. The meta/local gateway, the S-GW, and the P-GW are transmitted, and the IP offloaded data stream is transmitted between the terminal and the wireless side network element/local gateway.

Based on the system architecture of FIG. 1 and the scenario where the local gateway is the L-SGW and the L-PGW, the process of performing the service request process when the terminal is switched from the idle state to the connected state is introduced. FIG. 5 is a schematic diagram of the terminal in the prior art. The flow chart of the service request process when the switch to the connected state is as shown in FIG. 5. In the prior art, the process of performing the service request process when the terminal is changed from the idle state to the connected state is as follows:

Step 501: The terminal has an IP offload connection after accessing the wireless communication system, and then the terminal enters an idle state.

Step 502: The terminal sends a service request message to the mobility management entity via the radio side network element. Step 503: The mobility management entity performs a Non-Access-Stratum (NAS) authentication process, which is an optional step. interest.

Step 505: The radio side network element performs a radio bearer establishment procedure.

Step 506: The wireless side network element responds to the mobility management entity initial context establishment complete message. Step 507: When the mobility management entity needs to initiate an activation/establishment operation of the IP offload connection, send a modify bearer request message to the L-SGW.

Step 508: Optionally, the L-SGW sends a bearer modification request message to the L-PGW.

Step 509: Optionally, the L-PGW responds to the L-SGW bearer modification request response result.

Step 510: The L-SGW sends a bearer modification response message to the mobility management entity.

It can be seen from the above process that when the IP offload connection supports mobility, the terminal moves to the destination. After the wireless side network element is marked, the service gateway is still the local service gateway (L-SGW). However, since there may be no interface between the L-SGW and the target wireless side network element, the data cannot be smoothly transmitted at this time, thereby affecting the user experience. Summary of the invention

In view of the above, the main object of the present invention is to provide a method and system for changing the connection activation of a service gateway when the terminal is switched to the connected state, which can ensure smooth data transmission and improve user experience when the IP offload connection supports mobility.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A connection activation method for changing a service gateway when the terminal is switched to the connection state, comprising: when the terminal enters the connection state from the idle state, and the mobility management entity determines that the service gateway needs to be changed, initiates an establishment/activation process of the IP offload access, and changes Service gateway.

Before the terminal enters the connected state from the idle state, the method further includes the following steps: when the terminal enters the idle state from the connected state for the first time, the mobility management entity saves the relevant parameters of the IP offload connection.

The relevant parameters of the IP offload connection are: a service gateway type, and a local gateway identifier of the IP offload connection, and/or a local gateway address, and/or a radio side network element identifier, and/or a radio side network element address.

When the terminal enters the connected state from the idle state, the method further includes the following steps: the terminal sends a service request message to the mobility management entity by using the wireless side network element,

The service request message carries parameters: a local gateway identifier of the current connection, and/or a local gateway address, and/or a wireless side network element identifier, and/or a wireless side network element address.

The mobility management entity determines that the service gateway needs to be changed: the radio side network element of the IP offload access changes and the current serving gateway is the local service gateway, or the radio side network element of the IP offload access does not change and the current service The gateway is the core network service gateway.

The mobility management entity determines that the radio side network element of the IP offload access changes to: by comparing the parameter carried in the service request message with the terminal entering the idle state from the connected state for the first time. The stored parameters are determined by: at least one of a local gateway identifier, and/or a local gateway address, and/or a wireless side network element identifier, and/or a wireless side network element address carried by the service request message. When the terminal stores the corresponding parameters when the connection state enters the idle state for the first time, it determines that the wireless side network element of the IP offload access changes.

The establishment/activation process of the mobility management entity to initiate IP offload access is:

When the wireless side network element of the IP offloading is changed and the current serving gateway is the local serving gateway, the mobility management entity initiates an establishment/activation process of the IP offloading access to the core network serving gateway, which is specifically:

The mobility management entity sends a bearer setup request to the core network serving gateway;

The core network monthly service gateway responds with 7 to establish a response message;

The mobility management entity sends an initial context setup request message carrying the tunnel information of the core network serving gateway to the radio side network element;

The wireless side network element performs a radio bearer establishment process;

The wireless side network element responds to the mobility management entity initial context establishment completion message;

The mobility management entity initiates establishment of a forwarding tunnel between the core network service gateway and the local service gateway;

The mobility management entity sends a bearer modification request to the core network serving gateway;

After the core network service gateway performs bearer modification, the bearer modification response is replied to the mobility management entity.

If the wireless side network element of the IP offloaded access does not change and the current serving gateway is the core network service gateway, the mobility management entity initiates an IP split access setup/activation process to the local service gateway as follows:

The mobility management entity sends a bearer setup request to the local service gateway;

The local service gateway responds to the bearer setup response message;

The mobility management entity sends the tunnel information carrying the local service gateway to the wireless side network element. Start context setup request message;

The mobility management entity sends a bearer modification request to the local service gateway;

After the local service gateway performs bearer modification, it replies to the mobility management entity with a bearer modification response. After the core network service gateway sends the bearer modification response to the mobility management entity, the method further includes the following steps:

The mobility management entity initiates a release session request to the local service gateway;

The mobility management entity initiates a release forwarding tunnel request to the local service gateway;

The mobility management entity initiates a release forwarding tunnel request to the core network serving gateway.

After the local service gateway sends the bearer modification response to the mobility management entity, the method further includes:

The mobility management entity initiates a release session request to the core network serving gateway;

The mobility management entity initiates a release forwarding tunnel request to the core network serving gateway;

The mobility management entity initiates a release forwarding tunnel request to the local service gateway.

The wireless side network element is a base station, or a home base station, or a Radio Network Controller (RNC), or a local gateway, or a traffic off function entity;

The mobility management entity is a Mobility Management Entity (MME), or a Mobile Switching Centre (MSC), or a Serving GPRS Support Node (SGSN);

The local access gateway is an L-PGW or an L-GGSN;

The local service gateway is an L-SGW or an L-SGSN;

The local gateway is an L-SGW (local SGW, Local SGW) and L-PGW (local PGW, Local PGW), or a separate L-PGW, or a local GGSN and a local SGSN, or a separate L-GGSN, or a data offloading functional entity, the local gateway including a local access gateway and/or a local monthly service gateway ;

The core network access gateway is a P-GW or a GGSN;

The core network service gateway is an S-GW or an SGSN;

The IP offloading also includes any of the following: a local IP access user local network, a local IP access company local network, a local IP access Internet, a diversion operation of the Internet service, and a specific IP data offload.

A connection activation system for changing a service gateway when the terminal is switched to the connection state, comprising: a mobility management entity, where the mobility management entity includes a change determination unit and a change execution unit; wherein the change determination unit is used in the terminal When entering the connection state from the idle state, determining whether the service gateway needs to be changed, and notifying the change execution unit when determining that the service gateway needs to be changed; the change execution unit is configured to initiate IP offload access according to the notification of the change determination unit Establish/activate the process and change the service gateway.

The mobility management entity further includes an IP offload connection related parameter storage unit, configured to save related parameters of the IP offload connection when the terminal enters the idle state from the connected state for the first time.

The system further includes a wireless side network element, and the mobility management entity further includes a service request message receiving unit,

The wireless side network element is configured to send a service request message to the mobility management entity when the terminal enters the connected state from the idle state;

The service request message receiving unit is configured to receive a service request message sent by the wireless side network element, and notify the change determining unit;

The change judging unit is further configured to determine, according to the parameter related to the IP offload connection stored in the IP shunt connection related parameter storage unit, and the parameter carried in the service request message received by the service request message receiving unit, to determine whether the service needs to be changed. Gateway. The system further includes a core network service gateway and a local service gateway, and sends a bearer setup request;

The core network serving gateway is configured to respond to the bearer setup response message to the change execution unit according to the bearer setup request of the change execution unit;

The change execution unit is further configured to send, to the radio side network element, an initial context setup request message that carries tunnel information of the core network serving gateway;

The radio side network element is further configured to perform a radio bearer setup procedure according to an initial context setup request message of the tunnel information carrying the core network service gateway from the change execution unit, and respond to the change execution unit with an initial context setup complete message;

The change execution unit is further configured to initiate establishment of a forwarding tunnel between the core network service gateway and the local service gateway;

The change execution unit is further configured to send a bearer modification request to the core network service gateway, where the core network service gateway is further configured to: after the bearer modification is performed according to the bearer modification request from the change execution unit, return the bearer to the change execution unit. Modify the response.

The change execution unit is further configured to send a bearer setup request to the local service gateway according to the notification of the change judging unit;

The local service gateway is further configured to: respond to the change execution unit with a bearer setup response message; the change execution unit is further configured to send, to the radio side network element, an initial context setup request message that carries tunnel information of the local service gateway;

The radio side network element is further configured to respond to the change execution unit initial context establishment complete message after performing the radio bearer setup procedure according to the initial context setup request message carrying the tunnel information of the local service gateway;

The change execution unit is further configured to send a bearer modification request to the local service gateway, where the local service gateway is further configured to modify the request according to the bearer from the change execution unit. After the bearer modification, the bearer modification response is replied to the change execution unit.

The change execution unit is further configured to initiate a release session request to the local service gateway; and initiate a release forwarding tunnel request to the local service gateway; and initiate a release forwarding tunnel request to the core network serving gateway.

The change execution unit is further configured to initiate a release session request to the core network serving gateway; and initiate a release forwarding tunnel request to the core network serving gateway; and initiate a release forwarding tunnel request to the local service gateway.

The wireless side network element is a base station, or a home base station, or a radio network controller, or a local gateway, or a offloading functional entity;

The mobility management entity is a mobility management unit, or a mobile switching center, or a serving GPRS support node;

The local access gateway is an L-PGW or an L-GGSN;

The local service gateway is an L-SGW or an L-SGSN;

The local gateway is an L-SGW and an L-PGW, or a separate L-PGW, or a local GGSN and a local SGSN, or a separate L-GGSN, or a data offloading functional entity, the local gateway including a local access gateway and / or local service gateway;

The core network access gateway is a P-GW or a GGSN;

The core network service gateway is an S-GW or an SGSN;

When the terminal of the present invention is switched to the connected state, the connection activation method and system of the service gateway are changed. When the IP offload connection supports mobility, and the terminal moves to the target radio side network element, the mobility management entity determines to connect the IP offload by determining The service gateway migrates to activate the IP offload connection, thereby solving the problem that the data cannot be obtained because there is no interface between the L-SGW and the target radio side network element. The problem of smooth transmission effectively realizes the IP shunt connection activation mechanism after the terminal changes the radio side network element, thereby improving the user experience. DRAWINGS

1 is a schematic diagram of a mobile communication network connection in the prior art;

2 is a schematic diagram of another mobile communication network connection in the prior art;

3 is a schematic diagram of another connection of a mobile communication network in the prior art;

4 is a schematic diagram of an IP split access data flow of a mobile communication system in the prior art; FIG. 5 is a schematic diagram of a process of performing a service request process when a terminal transitions from an idle state to a connected state in the prior art;

6 is a schematic diagram showing a flow of a method for changing a connection activation of a service gateway when the terminal is switched to a connected state;

7 is a schematic diagram showing the structure of a connection activation system for changing a service gateway when the terminal is switched to a connected state;

8 is a schematic flowchart of a method for changing a connection activation manner of a service gateway when a terminal is switched to a connected state according to Embodiment 1 of the present invention;

FIG. 9 is a schematic flowchart of a method for changing a connection activation manner of a service gateway when a terminal is switched to a connected state according to Embodiment 2 of the present invention. detailed description

The basic idea of the present invention is: When the IP offload connection supports mobility, and the terminal moves to the target radio side network element, the mobility management entity determines to migrate the service gateway connected by the IP offload to activate the IP offload connection. .

The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings.

FIG. 6 is a schematic flowchart of a method for changing a connection activation of a service gateway when the terminal is turned into a connected state according to the present invention. As shown in FIG. 6, when the terminal of the present invention is switched to a connected state, the connection activation party of the service gateway is changed. The method generally includes the following steps:

Step 61: When the terminal enters the idle state from the connected state for the first time, the mobility management entity saves the relevant parameters of the IP offload connection.

The parameters related to the IP offload connection generally include: a service gateway type, and a local gateway identifier of the IP offload connection, and/or a local gateway address, and/or a radio side network element identifier, and/or a radio side network element address.

Here, the service gateway type is generally a local type or a core network type.

Step 62: When the terminal enters the connected state from the idle state, the service request message is sent to the mobility management entity by the wireless side network element.

The service request message generally carries: a local gateway identifier of the connection, and/or a local gateway address, and/or a radio side network element identifier, and/or a radio side network element address.

It should be noted that, in actual applications, the parameters carried in the service request message should correspond to the relevant parameters of the IP offload connection saved by the mobility management entity when the terminal enters the idle state for the first time from the connected state. It should be possible to ensure that the judgment of the subsequent steps is met.

Step 63: The mobility management entity determines whether the service gateway needs to be changed according to the parameter stored in step 61 and the parameter carried in the service request message in step 62. If yes, go to step 64; otherwise, go to step 65.

The mobility management entity determines that there are two situations in which the service gateway needs to be changed:

1. The wireless side network element of the IP split access changes and the current serving gateway is the local service gateway.

2. The wireless side network element of the IP offload access does not change and the current serving gateway is the core network service gateway.

Specifically, by comparing the parameters carried in the service request message in step 62 with the parameters stored in step 61, the local gateway identifier carried in the service request message in step 62, and/or local If at least one of the gateway address, and/or the wireless side network element identifier, and/or the wireless side network element address is different from the corresponding parameter stored in step 61, it is determined that the wireless side network element of the IP offload access changes.

In other words, the method for determining whether the terminal accesses from the wireless side network element of the IP offloading may be a comparison.

Whether the wireless side network element identifier/address is the same as the locally stored wireless side network element identifier/address, or the wireless side network element is compared to the mobility management when the wireless side network element and the local gateway identifier/address are the same. Whether the wireless side network element identifier/address transmitted by the entity is the same as the locally saved local gateway identifier/address.

Step 64: The mobility management entity initiates an establishment/activation process of the IP offload access, changes the service gateway, and the process ends.

Here, if the radio side network element of the IP offload access changes and the current serving gateway is the local serving gateway, the mobility management entity initiates an IP split access setup/activation procedure to the core network serving gateway; If the wireless side network element does not change and the current serving gateway is the core network serving gateway, the mobility management entity initiates an IP split access setup/activation process to the local serving gateway. Moreover, after the radio bearer is established, a data forwarding tunnel needs to be established between the core network serving gateway and the local service gateway.

If the mobility management entity needs to switch the local serving gateway to the core network serving gateway, the initial context setup request message sent by the mobility management entity to the wireless side network element carries the tunnel information of the core network serving gateway. If the mobility management entity needs to switch the core network service gateway to the tunnel information carrying the local service gateway in the message. The tunnel information includes an address and a tunnel identifier. The tunnel identifier may be a Tunnel End Point Identifier (TEID) or a GRE Key.

In addition, after the IP offload connection is established/activated, the mobility management entity can initiate data forwarding. The release of the tunnel.

Step 65: Perform the prior art process.

It should be noted that, in the present invention, the radio side network element may be a base station, a home base station, a radio network controller (RNC), a local gateway, a offload function entity, etc.; the mobility management entity may be a mobility management unit (Mobility) Management Entity, MME), Mobile Switching Centre (MSC), Serving GPRS Support Node (SGSN), etc.; local access gateways may be L-PGW, L-GGSN, etc.; It is an L-SGW, an L-SGSN, etc.; the local gateway may be an L-SGW (Local SGW, Local SGW) and an L-PGW (Local PGW, Local PGW), or may be a separate L-PGW, or may be a local GGSN ( L-GGSN, Local GGSN, and Local SGSN (L-SGSN, Local SGSN), may be separate L-GGSNs, may be data offloading functional entities; local gateways may include local access gateways and/or local serving gateways. The core network access gateway may be a P-GW, a GGSN, or the like; the core network serving gateway may be an S-GW, an SGSN, or the like. In addition, the wireless side network element of the IP offload can be the same as the local gateway address.

IP offloading can also include one of the following: local IP access to the user's local network, local IP access to the company's local network, local IP access to the Internet, offloading of Internet traffic, and specific IP data offload.

FIG. 7 is a schematic structural diagram of a connection activation system for changing a service gateway when the terminal is turned into a connected state according to the present invention. As shown in FIG. 7, the connection activation system for changing the service gateway when the terminal is switched to the connected state includes: a mobility management entity 71, The mobility management entity 71 includes a change determination unit 711 and a change execution unit 712;

The change determining unit 711 is configured to: when the terminal enters the connected state from the idle state, determine whether the service gateway needs to be changed, and when it is determined that the service gateway needs to be changed, notify the change execution unit 712; and the change executing unit 712 is configured to determine the unit according to the change The notification of 711 initiates the establishment/activation process of IP offload access and changes the service gateway. The mobility management entity 71 further includes an IP offload connection related parameter storage unit 713, configured to save related parameters of the IP offload connection when the terminal enters the idle state from the connected state for the first time.

The system also includes a wireless side network element 72, and the mobility management entity 71 further includes a service request message receiving unit 714.

The wireless side network element 72 is configured to send a service request message to the mobility management entity 71 when the terminal enters the connected state from the idle state;

The service request message receiving unit 714 is configured to receive a service request message sent by the wireless side network element 72, and notify the change determining unit 711;

The change judging unit 711 is further configured to determine, according to the parameter related to the IP offload connection stored in the IP offload connection related parameter storage unit 713, and the parameter carried in the service request message received by the service request message receiving unit 714, to determine whether the change is required. Service gateway.

The system also includes a core network service gateway 73 and a local service gateway 74.

The change execution unit 712 is further configured to send a bearer setup request to the core network service gateway 73 according to the notification of the change judging unit 711;

The core network service gateway 73 is configured to respond to the bearer setup response message to the change execution unit 712 according to the bearer setup request of the change execution unit 712.

The change execution unit 712 is further configured to send an initial context setup request message carrying the tunnel information of the core network serving gateway 73 to the wireless side network element 72;

The radio side network element 72 is further configured to perform a radio bearer setup procedure according to the initial context setup request message of the tunnel information carrying the core network serving gateway 73 from the change execution unit 712, and respond to the change execution unit 712 with an initial context setup complete message;

The change execution unit 712 is further configured to initiate establishment of a forwarding tunnel between the core network serving gateway 73 and the local serving gateway 74;

The change execution unit 712 is further configured to send a bearer modification request to the core network serving gateway 73; the core network serving gateway 73 is further configured to modify according to the bearer from the change executing unit 712. After requesting the bearer modification, the change execution unit 712 is replied to the bearer modification response. The change execution unit 712 is further configured to send a bearer setup request to the local serving gateway 74 according to the notification of the change determining unit 711;

The local service gateway 74 is further configured to respond to the change execution unit 712 with a bearer setup response message; the change execution unit 712 is further configured to send an initial context setup request message carrying the tunnel information of the local service gateway 74 to the radio side network element 72;

The wireless side network element 72 is further configured to respond to the change execution unit 712 initial context establishment complete message after performing the radio bearer setup procedure according to the initial context setup request message carrying the tunnel information of the local service gateway 74.

The change execution unit 712 is further configured to send a bearer modification request to the local service gateway 74. The local service gateway 74 is further configured to: reply to the change execution unit 712 with the bearer modification after the bearer modification is performed according to the bearer modification request from the change execution unit 712. response.

The change execution unit 712 is further configured to initiate a release session request to the local service gateway 74; and initiate a release forwarding tunnel request to the local service gateway 74; and initiate a release forwarding tunnel request to the core network serving gateway 73.

The change execution unit 712 is further configured to initiate a release session request to the core network serving gateway 73; and initiate a release forwarding tunnel request to the core network serving gateway 73; and initiate a release forwarding tunnel request to the local serving gateway 74.

The technical solution of the present invention will be further described in detail below through specific embodiments.

Example 1

In this embodiment, based on the system architecture shown in FIG. 1 and the local gateway is an L-SGW and an L-PGW scenario, a flow chart of performing a service request process when the terminal transitions from an idle state to a connected state is provided. In this embodiment, the serving gateway of the IP offload connection is an L-SGW. FIG. 8 is a schematic flowchart of a method for changing a connection activation of a service gateway when a terminal is switched to a connected state according to Embodiment 1 of the present invention. As shown in FIG. 8, the connection activation method for changing a service gateway when the terminal is switched to a connected state according to Embodiment 1 of the present invention includes: Step 801: The terminal has an IP offload connection after accessing the wireless communication system, and then the terminal enters an idle state.

When the terminal is idle, the mobility management entity needs to save the service gateway type (local type or core network type), and the local gateway (L-PGW) identifier of the IP offload connection, and/or the local gateway address, and/or the wireless side network element. Parameters such as identification, and/or wireless side network element address.

Step 802: The terminal sends a service request message to the mobility management entity via the radio side network element. Here, the message sent by the wireless side network element to the mobility management entity may carry the local gateway identifier of the current connection, and/or the local gateway address, and/or the wireless side network element identifier, and/or the wireless side network element address.

Step 803: The mobility management entity performs a NAS authentication process.

This step is an optional step.

Step 804: The mobility management entity determines whether the service gateway needs to be changed.

If the mobility management entity finds that the terminal accesses the wireless side network element of the non-IP offload, that is, the radio side network element of the IP offload access changes, the core network service gateway (S-GW) is selected to establish an IP offload connection. If the serving gateway of the IP offloading is the L-SGW, the L-SGW is switched to the S-GW and an IP offload connection is established.

If the mobility management entity finds that the terminal accesses from the wireless side network element of the IP offload, that is, the radio side network element of the IP offload access does not change, the local service gateway (L-SGW) is selected to establish an IP offload connection. If the serving gateway of the IP offloading is the S-GW, the S-GW is switched to the L-SGW and an IP offload connection is established.

The method for determining whether the terminal accesses from the wireless side network element of the IP offloading may be to compare whether the local gateway (L-PGW) identifier/address carried in step 802 is the same as the locally saved local gateway (L-PGW) identifier/address, The comparison may be performed by comparing the radio side network element identifier/address carried in the step 802 with the locally stored radio side network element identifier/address, or in the case that the radio side network element and the local gateway identifier/address are the same, The wireless side network element carried in step 802 Whether the identity/address is the same as the locally saved local gateway ID/address.

Step 805: The mobility management entity determines that the L-SGW needs to be switched to the S-GW and establishes a connection, and then sends a bearer setup request to the S-GW.

Step 806: The S-GW responds with a setup response message. interest.

The initial context setup request message carries the tunnel information of the S-GW.

Step 808: The radio side network element performs a radio bearer establishment process.

Step 809: The wireless side network element responds to the mobility management entity initial context establishment complete message. Step 810: The mobility management entity initiates establishment of a forwarding tunnel.

Here, the forwarding tunnel refers to a forwarding tunnel between the L-SGW and the S-GW.

Step 811: The mobility management entity sends a bearer modification request to the S-GW.

Step 812: Perform bearer modification between the S-GW and the L-PGW.

Step 813: The S-GW replies to the mobility management entity with a bearer modification response.

Step 814: The timer management device sends a session release request to the L-SGW.

Step 815: The L-SGW returns a session release response message to the mobility management entity.

Step 816: The timer is triggered by the mobility management entity to request the L-SGW to release the forwarding tunnel.

Step 817: The L-SGW returns a forwarding tunnel release response message to the mobility management entity. Step 818: The timer is triggered by the mobility management entity to request the S-GW to release the forwarding tunnel. It should be noted that the above-mentioned action triggered by the timer is not limited to the timing trigger, and may be triggered by other means such as an instruction.

Step 819: The S-GW returns a forwarding tunnel release response message to the mobility management entity.

Example 2 In the scenario of the system architecture of FIG. 1 and the local gateway being the L-SGW and the L-PGW, another process for performing a service request process when the terminal is switched from the idle state to the connected state is provided, where the IP offloaded connection service is provided. The gateway is an S-GW. FIG. 9 is a schematic flowchart of a method for changing a connection activation of a service gateway when the terminal is switched to a connected state according to Embodiment 2 of the present invention. As shown in FIG. 9, the second embodiment of the present invention changes the service gateway when the terminal is switched to the connected state. The connection activation methods include:

Step 901: The terminal has an IP offload connection after accessing the wireless communication system, and then the terminal enters an idle state.

Step 902: The terminal sends a service request message to the mobility management entity via the radio side network element. The message sent by the wireless side network element to the mobility management entity may carry the local gateway identifier of the current connection, and/or the local gateway address, and/or the wireless side network element identifier, and/or the wireless side network element address.

Step 903: The mobility management entity performs a NAS authentication process.

This step is an optional step.

Step 904: The mobility management entity determines whether the service gateway needs to be changed.

If the mobility management entity finds that the terminal accesses the wireless side network element of the IP offload, that is, the wireless side network element of the IP offload access does not change, the local service gateway (L-SGW) is selected to establish an IP offload connection. If the serving gateway of the IP offloading is the S-GW at this time, the S-GW is switched to the L-SGW and an IP offload connection is established. A method for determining whether the terminal accesses from the IP side offloaded wireless side network element: whether the local gateway (L-PGW) identifier/address carried in the comparison step 902 is the same as the locally saved local gateway (L-PGW) identifier/address The wireless side network element identifier/address carried in the comparison step 902 may be the same as the locally stored wireless side network element identifier/address, or may be the same when the wireless side network element and the local gateway identifier/address are the same. The radio side network element identifier/address carried in the comparison step 902 is the same as the locally saved local gateway identifier/address.

Step 905: The mobility management entity determines that the S-GW needs to be handed over to the L-SGW and establishes a connection, and the mobility management entity sends a bearer setup request to the L-SGW.

Step 906: The L-SGW responds with a set of response messages. interest.

The initial context setup request message carries the tunnel information of the L-SGW.

Step 908: The radio side network element performs a radio bearer establishment procedure.

Step 909: The wireless side network element responds to the mobility management entity initial context establishment complete message. Step 910: The mobility management entity initiates establishment of a forwarding tunnel.

Here, the forwarding tunnel that needs to be established is a forwarding tunnel between the L-SGW and the S-GW.

Step 911: The mobility management entity sends a bearer modification request to the L-SGW.

Step 912: Perform bearer modification between the L-SGW and the L-PGW.

Step 913: The L-SGW replies to the mobility management entity with a bearer modification response.

Step 914: The timer management triggers the mobility management entity to send a session release request to the S-GW.

Step 915: The S-GW replies to the mobility management entity with a session release response message.

Step 916: The timer is triggered by the mobility management entity to request the S-GW to release the forwarding tunnel. Step 917: The S-GW returns a forwarding tunnel release response message to the mobility management entity.

Step 918: The timer is triggered, and the mobility management entity requests the L-SGW to release the forwarding tunnel. Road.

It should be noted that the above-mentioned action triggered by the timer is not limited to the timing trigger, and may be triggered by other means such as an instruction.

Step 919: The L-SGW returns a forwarding tunnel release response message to the mobility management entity. In order to simplify the description, the above embodiment only illustrates the manner in which the serving gateway is changed after the terminal transitions to the connected state by taking the case where the E-UTRAN system does not have the home base station gateway. When there is a home base station gateway, the manner in which the service gateway changes in the IP offload connection after the terminal is switched to the connected state is similar to the above embodiment, and will not be described in detail herein.

When the radio side network element that the terminal is currently accessing is the same as the radio side network element corresponding to the IP offloading access, the radio side network element of the IP offloading access is not changed.

When the radio side network element that the terminal is currently accessing is different from the radio side network element corresponding to the IP offloading access, the radio side network element of the IP offloading access is changed.

It should be noted that the foregoing modules or steps of the present invention may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices, optionally They may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be fabricated into individual integrated circuit modules, or multiple modules thereof or The steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for changing a connection activation of a service gateway when the terminal is switched to a connection state, the method comprising:

When the terminal enters the connected state from the idle state, the mobility management entity determines that the service gateway needs to be changed, initiates an establishment/activation process of the IP offload access, and changes the serving gateway.

The method according to claim 1, wherein before the terminal enters the connected state from the idle state, the method further includes: when the terminal enters the idle state from the connected state for the first time, the mobility management entity saves the relevant parameters of the IP offload connection. ,

The method according to claim 2, wherein, when the terminal enters the connected state from the idle state, the method further includes: the terminal sending a service request message to the mobility management entity by using the wireless side network element,

The method according to claim 3, wherein the mobility management entity determines that the service gateway needs to be changed: the radio side network element of the IP offload access changes and the current serving gateway is a local service gateway, or The wireless side network element of the IP offloaded access does not change and the current serving gateway is the core network monthly service gateway.

The method according to claim 4, wherein the mobility management entity determines whether the wireless side network element accessed by the IP offloading is changed to: by comparing parameters carried by the service request message with the terminal Determining, for the first time, the parameters stored when the connected state enters the idle state; specifically: the local gateway identifier carried by the service request message, and/or the local gateway address, and/or the wireless side network element identifier, and/or the wireless side network In the meta address, at least one of the first time with the terminal When the corresponding parameters stored when the connected state enters the idle state are different, it is determined that the wireless side network element accessed by the IP offloading changes.

6. The method of claim 4, wherein

When the wireless side network element of the IP split accessing is changed and the current serving gateway is the local serving gateway, the establishment/activation process of the IP-based splitting access initiated by the mobility management entity is:

When the wireless side network element of the IP offloading access does not change and the current serving gateway is the core network service gateway, the establishment/activation process of the IP management network to initiate IP offload access is:

The local service gateway responds to the bearer setup response message;

The mobility management entity sends an initial context setup request message carrying the tunnel information of the local serving gateway to the radio side network element;

The mobility management entity initiates a forwarding tunnel between the core network service gateway and the local service gateway Establishment

After the local service gateway performs bearer modification, it replies to the mobility management entity with a bearer modification response.

7. The method of claim 6 wherein:

After the core network serving gateway sends the bearer modification response to the mobility management entity, the method further includes the following steps:

8. A method according to any one of claims 1 to 7, characterized in that

The local access gateway is an L-PGW or an L-GGSN;

The local service gateway is an L-SGW or an L-SGSN;

The core network access gateway is a P-GW or a GGSN; The core network service gateway is an S-GW or an SGSN;

A connection activation system for changing a service gateway when the terminal is switched to the connection state, wherein the system includes a mobility management entity, and the mobility management entity includes: a change determination unit and a change execution unit;

The change judging unit is configured to: when the terminal enters the connected state from the idle state, determine whether the service gateway needs to be changed, and notify the change execution unit when it is determined that the service gateway needs to be changed; the change execution unit is configured to determine according to the change The unit's notification initiates the establishment/activation process of IP offload access and changes the service gateway.

The system according to claim 9, wherein the mobility management entity further comprises an IP offload connection related parameter storage unit, configured to save the IP offload connection when the terminal enters the idle state from the connected state for the first time. parameter.

The system according to claim 10, wherein the system further comprises a wireless side network element, wherein the mobility management entity further comprises a service request message receiving unit,

The change judging unit is further configured to determine, according to the parameter related to the IP offload connection stored in the IP shunt connection related parameter storage unit, and the parameter carried in the service request message received by the service request message receiving unit, to determine whether the service needs to be changed. Gateway.

12. The system according to claim 10, wherein the system further comprises a core network service gateway and a local monthly service gateway. Knowing that the bearer establishment request is sent to the core network monthly service gateway;

13. The system of claim 12, wherein

14. The system of claim 12, wherein:

15. The system of claim 13 wherein:

The system according to any one of claims 12 to 15, wherein the wireless side network element is a base station, or a home base station, or a radio network controller, or a local gateway, or a offloading functional entity;

The local access gateway is an L-PGW or an L-GGSN;

The local service gateway is an L-SGW or an L-SGSN;

The core network access gateway is a P-GW or a GGSN;

The core network service gateway is an S-GW or an SGSN;