WO2012041131A1

WO2012041131A1 - Method and system for subscriber to participate in establishment of local access connection

Info

Publication number: WO2012041131A1
Application number: PCT/CN2011/078639
Authority: WO
Inventors: 雷小燕; 王静; 周娜
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-09-29
Filing date: 2011-08-19
Publication date: 2012-04-05
Also published as: CN102438328B; CN102438328A

Abstract

Disclosed is a method for a subscriber to participate in establishment of local access connection, comprising: establishing or rejecting a PDN connection by a network side according to a message carrying subscriber willingness and sent by the subscriber, or when a location of the subscriber is changed, establishing or rejecting a PDN connection by a target mobility management entity according to willingness of the subscriber from an original mobility management entity. Further disclosed is a system for a subscriber to participate in establishment of local access connection. SIPTO connections established through the present invention can all be sensed by the subscriber, so even if the service quality of the subscriber cannot be guaranteed due to feeder loss or local control after the establishment of the SIPTO connections, the subscriber also has a mental preparation, thereby improving the service experience of the subscriber.

Description

Method and system for user participation in local access connection establishment

The present invention relates to mobile communication technologies, and in particular, to a method and system for a user to participate in local access connection establishment. Background technique

The 3rd Generation Partnership Project (3GPP) evolved Evolved Packet System (EPS) from 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 (Home Subscriber Server, HSS), 3GPP's Authentication, Authorization and Accounting (AAA) server, Policy and Charging Rules Function (PCRF) entity and other supporting nodes. The mobility management entity is responsible for control planes such as mobility management, non-access stratum signaling processing, and user mobility management context management; the access gateway includes S-GW and P-GW, and the S-GW is The E-UTRAN-connected access gateway device forwards data between the E-UTRAN and the P-GW and is responsible for buffering the paging waiting data. The P-GW is an EPS and Packet Data Network (PDN). Border gateway, responsible for PDN access and forwarding data between EPS and PDN; authentication authorization server includes HSS, 3GPP AAA; PCRF is a policy and charging rule function entity, which receives interface Rx and carrier IP service The network is connected to obtain the service information. In addition, it is connected to the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the establishment of the IP bearer, guaranteeing the quality of service (QoS) of the service data, and performing charging. control. As a new access service mode, the home base station is a small, low-power base station deployed in indoor places such as homes and offices. The main function is to provide users with higher service rates and lower use of high-speed services. The cost required, while making up for the lack of coverage of existing distributed 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.

1, FIG. 2 and FIG. 3 are respectively schematic diagrams of connection of three wireless communication networks in the prior art. It can be seen that the home base station in FIG. 1 is directly connected to the core network, and the home base station in FIG. The main function of the home base station gateway is: verifying the security of the home base station, processing 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 switching the core Network and home base station data.

In addition to supporting access to the mobile core network, mobile communication systems (including home base station systems) can also support selected IP Traffic Offload (SIPTO) functions to enable local access of the terminal to the Internet.

The implementation of SIPTO in the systems shown in Figure 1, Figure 2 and Figure 3 can provide strong support for SIPTO by adding a local gateway. The local gateway acts as a gateway to the external network (such as the Internet) to provide address allocation and accounting. , packet packet filtering, policy control, data offloading function, NAS/S1-AP/RANAP (Radios Access Network Application Part) / General Tunneling Protocol (GTP) I proxy mobile IP protocol ( Proxy Mobile IP, PMIP) / Mobile IP (MIP) Message parsing, Network Address Translation (NAT), IP offloading policy routing and execution. The local gateway can be combined with the wireless side network element or can be arranged separately.

In the case of a home base station gateway, the local gateway can be configured not only with the home base station (as shown in FIG. 2) or separately, but also with the home base station gateway (as shown in FIG. 3) or separately. The wireless side network element is a home base station subsystem including a home base station and/or a home base station gateway, The local gateway may be a local service gateway (Local SGW, L-SGW) and a local packet data gateway (Local PGW, L-PGW), or may be a separate L-PGW or data offloading functional entity. In addition, the home base station gateway can be combined with the home base station.

FIG. 4 and FIG. 5 are respectively two connection diagrams of SIPTO performed by the wireless communication system in the prior art. In the prior art, when a user uses the SIPTO function, the local gateway performs data offloading. Since the local gateway is generally placed in the home or enterprise, the administrator of the home or enterprise can set a corresponding firewall policy on the local gateway. Some users' access to other external IP networks may cause some services to be impossible to perform normally. This kind of operation is beyond the control of the operator. In addition, since the mobile network is uncontrollable for the local gateway local policy, the quality of the user cannot be guaranteed. From the perspective of user satisfaction, the user may prefer to use the core network connection to access the external network. Summary of the invention

In view of this, the main object of the present invention is to provide a method and system for a user to participate in a local access connection establishment, which can establish a SIPTO connection according to the user's wishes, thereby improving the user experience.

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

A method for a user to participate in establishing a local access connection includes: The network side establishes or rejects a PDN connection according to a message sent by the user that carries the user's will.

The message sent by the user is a PDN connection setup request message.

Before the user sends a message carrying the user's will, the method further includes: when the network side determines that the PDN connection type that needs to be established for the user is a SIPTO connection, obtaining the user's will,

The message sent by the user is a PDN connection setup response message.

The network side establishes or rejects the PDN connection according to the PDN connection establishment request message sent by the user carrying the user's will:

The user desires to establish a PDN connection of a specified type, and the network side establishes a corresponding PDN connection for the user according to the user's will, network capability, local policy, and subscription decision. Establishing the specified type of PDN connection;

The user desires to establish a PDN connection of a specified type, and the network side does not establish a corresponding PDN connection for the user according to the user's will, network capability, local policy, and subscription decision, and then establishes a core network PDN connection for the user, or rejects The user's PDN connection establishment request message; the user's intention is not to establish a PDN connection of a specified type, and the network side establishes a core network PDN connection or rejects the user's PDN connection establishment request message for the user.

The network side establishes or rejects the PDN connection according to the PDN connection setup response message sent by the user carrying the user's will:

The user determines whether to allow the SIPTO connection according to the PDN connection type sent by the network side; if the user wishes to accept the SIPTO connection, the network side establishes a SIPTO connection; if the user wishes to reject the SIPTO connection, the network side establishes a core network PDN connection for the user. , or do not establish a PDN connection.

The PDN connection type includes one or more of the following: a core network connection, a SIPTO connection. When the user refuses to establish a SIPTO connection, the method further includes: the user notifying the network side to perform a PDN connection release operation, or the user carrying the parameter to initiate a PDN connection release operation.

A system for a user to participate in the establishment of a local access connection includes a network side and a user side. The network side is configured to establish or reject a PDN connection according to a message sent by the user side that carries the user's will.

The message sent by the user side is a PDN connection setup request message.

The network side is further configured to acquire a user's will when determining that the PDN connection type that needs to be established for the user is a SIPTO connection;

The message sent by the user side is a PDN connection setup response message.

The user's willingness is to allow a PDN connection of a specified type to be established, and the network side according to the use The user's will, the network capability, the local policy, and the subscription decision establish a corresponding PDN connection for the user, and then establish the PDN connection of the specified type;

The user desires to establish a PDN connection of a specified type, and the network side does not establish a corresponding PDN connection for the user according to the user's will, network capability, local policy, and subscription decision, and then establishes a core network PDN connection for the user, or rejects The PDN connection establishment request message of the user; the user's intention is that the PDN connection of the specified type is not allowed to be established, and the network side establishes a PDN connection of the core network for the user, or rejects the PDN connection establishment request message of the user.

The user side is further configured to notify the network side to perform a PDN connection release operation when the user refuses to establish a SIPTO connection, or to carry out a PDN connection release operation by carrying parameters.

A method for a user to participate in establishing a local access connection, including:

In the case where the user has changed the location, the target mobility management entity establishes or denies the PDN connection of the user according to the wishes of the user from the original mobility management entity.

The method specifically includes: in the tracking area update process, the target mobility management entity acquires the user's will of the user from the original mobility management entity on the source network side, and then establishes or according to the user's will from the original mobility management entity. The PDN connection of the user is rejected.

The original mobility management entity carries the user's will through the context response message.

The method specifically includes: in the handover process, the original mobility management entity on the source network side actively sends the user's will of the user to the target mobility management entity, and then the target mobility management entity according to the original mobility management entity User's willingness to establish or reject the user's PDN connection.

The original mobility management entity sends the user's will to the target mobility management entity by relocation request message or relocation forward completion confirmation message.

The target mobility management entity establishes or rejects the PDN connection according to the message sent by the original mobility management entity:

The user desires to establish a PDN connection of a specified type, and the target mobility management entity establishes a corresponding PDN connection for the user according to the user's will, network capability, local policy, and subscription decision, and then establishes the PDN connection of the specified type. ;

The user desires to establish a PDN connection of a specified type, and the target mobility management entity does not establish a corresponding PDN connection for the user according to the user's will, network capability, local policy, and subscription decision, and establishes a core network PDN connection for the user. , or reject the user's PDN connection establishment request message;

The user's intention is that the PDN connection of the specified type is not allowed to be established, and the target mobility management entity establishes a PDN connection establishment message for the user or rejects the PDN connection establishment request message of the user; if the user wishes to accept the SIPTO connection, the network side establishes SIPTO connection; the user's willingness to reject the SIPTO connection, the target mobility management entity establishes a core network PDN connection for the user, or does not establish a PDN connection.

The PDN connection type includes one or more of the following: a core network connection, a SIPTO connection. A system for a user to participate in local access connection establishment, comprising a target mobility management entity and an original mobility management entity, wherein the target mobility management entity is configured to be based on original mobility management when a user changes location The user of the entity wishes to establish or reject the PDN connection of the user.

The target mobility management entity is specifically configured to acquire the user's will of the user from the original mobility management entity on the source network side during the tracking area update process, and then establish or according to the user's will from the original mobility management entity. The PDN connection of the user is rejected. The original mobility management entity is specifically configured to carry the user's will by the context response message.

The original mobility management entity is specifically configured to actively send the user's will of the user to the target mobility management entity during the handover process;

The target mobility management entity establishes or denies the PDN connection of the user according to the user's willingness from the original mobility management entity.

The original mobility management entity sends the user willingness to the target mobility management entity by using a relocation forward request message or a relocation forward completion confirmation message.

The user of the present invention participates in a method and system for establishing a local access connection. The network side establishes or rejects a PDN connection according to the user's willingness to send the user, or the target mobility management entity establishes or rejects a PDN connection according to the wishes of the user from the original mobility management entity. The SIPTO connection established by the present invention can be perceived by the user. Therefore, even if the SIPTO connection is established, the user can be psychologically prepared because the feeder loss or local control cannot guarantee the user's service quality, thereby improving the user's service experience. DRAWINGS

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

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

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

4 is a schematic diagram of a connection of a SIPTO in a wireless communication system in the prior art; FIG. 5 is a schematic diagram of another connection of a SIPTO in a wireless communication system in the prior art; FIG. 6 is a first embodiment of the present invention. A schematic diagram of the process of establishing a connection between a connection and a core network;

7 is a schematic flowchart of a user terminal actively establishing a PDN connection according to Embodiment 2 of the present invention; FIG. 8 is a schematic flowchart of a SIPTO connection initiated by a user after a user SIPTO connection is established, and a SIPTO connection is actively initiated after the user SIPTO connection is established; 9 is a schematic flowchart of a user rejecting a SIPTO connection in a PDN connection establishment process according to Embodiment 4 of the present invention;

FIG. 10 is a schematic diagram of a process for rejecting a SIPTO connection during a process of attaching and establishing a PDN connection according to Embodiment 5 of the present invention; FIG.

11 is a schematic flow chart of the original mobility management entity transmitting the saved user SIPTO willingness to the target mobility management entity in the tracking area update process of the user across the network side according to the embodiment of the present invention;

FIG. 12 is a flow chart showing the intention of the target mobility management entity to actively query the user's SIPTO in the tracking area update process according to the embodiment 7 of the present invention;

FIG. 13 is a flow chart showing the intention of the original mobility management entity in the source network side to transfer the saved user SIPTO to the target mobility management entity in the handover according to Embodiment 8 of the present invention. detailed description

The basic idea of the present invention is that the network side establishes or rejects the PDN connection according to the user's willingness sent by the user, or the target mobility management entity establishes or rejects the PDN connection according to the wishes of the user from the original mobility management entity.

There are four main implementation methods for the user of the present invention to participate in the establishment of a local access connection:

1) The network side establishes a request message according to the PDN connection that is sent by the user, and establishes or rejects the PDN connection. The implementation manner includes the following steps:

When the PDN connection is established, the user sends a PDN connection establishment request message carrying the user's will (such as allowing or not allowing SIPTO to be established) to the network side;

The network side determines whether to establish a corresponding PDN connection for the user according to the user's will, network capability, local policy, subscription, and the like.

Specifically: the user desires to establish a PDN connection of a specified type, and the network side establishes a corresponding PDN connection for the user according to the user's will, network capability, local policy, and subscription decision, and then establishes the PDN connection of the specified type; Willingness to allow the establishment of a specified type of PDN Connecting, and the network side does not establish a corresponding PDN connection for the user according to the user's will, the network capability, the local policy, and the subscription decision, and then establishes a core network PDN connection for the user, or rejects the user's PDN connection establishment request message;

If the user wishes to establish a PDN connection of the specified type, the network side establishes a core network PDN connection for the user, or rejects the user's PDN connection establishment request message.

Taking the SIPTO connection establishment as an example, when the PDN connection establishment request message carries the user's willingness to establish a SIPTO connection, the network side establishes a SIPTO connection for the user; when the PDN connection establishment request message carries a willingness to establish a SIPTO connection, the network side does not establish a SIPTO for the user. Connection, at this time, the network side can establish a core network PDN connection for the user, or can reject the user's PDN connection establishment request message.

2) When the network side determines that a SIPTO connection needs to be established for the user, the user's will is obtained. The implementation specifically includes the following steps:

The network side determines that the user needs to establish a SIPTO connection for the user according to the user's request message (such as a PDN connection establishment request and initialization of the NAS message);

The user returns the user's will (ie accepts the SIPTO connection or rejects the SIPTO connection) to the network side through the PDN connection establishment response message;

The network side establishes or rejects the PDN connection according to the user's wishes.

Specifically, if the user wishes to accept the SIPTO connection, the network side establishes a SIPTO connection; if the user wishes to reject the SIPTO connection, the network side establishes a core network PDN connection for the user, or does not establish a PDN connection.

It should be noted that the foregoing PDN connection type includes one or more of the following: a core network connection, and a SIPTO connection.

It should be noted that the user's wishes include: allowing SIPTO connections to be established, SIPTO connections not allowed, SIPTO connections to be accepted, and SIPTO connections to be rejected.

It should be noted that the user knows that the PDN connection type sent by the network side is SIPTO connection. If the user decides whether to accept or not, the user can notify the network side to perform the PDN connection release operation, or the user carries the parameter to initiate the PDN connection release operation. Here, the parameter carried by the user indicates that the PDN connection is released or rejected.

3) In the case where the user changes the location, specifically in the tracking area update process, the target mobility management entity acquires the user's will of the user from the original mobility management entity on the source network side, and then according to the original mobility management according to the The user of the entity wishes to establish or reject the PDN connection of the user.

Specifically, the original mobility management entity may carry the user's will through the context response message. The target mobility management entity establishes or rejects the PDN connection according to the message sent by the original mobility management entity:

The user desires to establish a PDN connection of a specified type, and the target mobility management entity establishes a corresponding PDN connection for the user according to the user's will, network capability, local policy, and subscription decision, and then establishes the PDN connection of the specified type;

The user desires to establish a PDN connection of a specified type, and the target mobility management entity does not establish a corresponding PDN connection for the user according to the user's will, network capability, local policy, and subscription decision, and then establishes a core network PDN connection for the user, or Rejecting the user's PDN connection establishment request message;

If the user wishes to establish a PDN connection of a specified type, the target mobility management entity establishes a PDN connection for the core network or rejects the PDN connection establishment request message of the user.

If the user wishes to accept the SIPTO connection, the network side establishes a SIPTO connection; if the user wishes to reject the SIPTO connection, the target mobility management entity establishes a core network PDN connection for the user, or does not establish a PDN connection.

It should be noted that the PDN connection type described in this implementation manner may include one or more of the following: a core network connection and a SIPTO connection.

The user's intention described in this implementation manner is the first implementation manner and the second implementation method described above. The user wishes described in the formula have the same meaning, and may include: allowing establishment of a SIPTO connection, not allowing a SIPTO connection to be established, accepting a SIPTO connection, and rejecting a SIPTO connection.

For the establishment or rejection of the PDN connection of the user according to the user's intention, the related descriptions in the first implementation manner and the second implementation manner may be referred to.

4) In the case where the user changes the location, specifically, in the handover process, the original mobility management entity on the source network side actively sends the user's will of the user to the target mobility management entity, and then the target mobility management entity according to the The user from the original mobility management entity wishes to establish or reject the PDN connection of the user.

Specifically, the original mobility management entity may send the user's willingness to the target mobility management entity by using a relocation forward request message or a relocation forward completion confirmation message.

It should be noted that the PDN connection type described in this implementation manner may include the following ones. Or multiple: Core network connection, SIPTO connection.

The user wishes described in this implementation manner have the same meanings as the user wishes described in the foregoing first implementation manner and the second implementation manner, and may include: allowing SIPTO connection to be established, SIPTO connection not allowed, SIPTO connection to be accepted, SIPTO to be rejected connection.

It should be noted that if the user never establishes a PDN connection and does not request to establish a PDN connection before the location change process, that is, the original mobility management entity on the source network side does not have the relevant user's will, the first implementation manner or The second implementation completes the local access connection establishment.

It should be noted that, when the user knows that the PDN connection type sent by the network side is a SIPTO connection, the user decides whether to accept or not according to the will. If the user refuses, the user may notify the network side to perform the PDN connection release operation, or the user carries the parameter to initiate the operation. The PDN connection release operation, where the parameters carried by the user indicate that the PDN connection is released or rejected.

The present invention further provides a system for a user to participate in the establishment of a local access connection, where the system includes a network side and a user side;

The network side is configured to establish or reject a PDN connection according to a message sent by the user side that carries the user's will.

The message sent by the user side is a PDN connection setup request message.

The message sent by the user side is a PDN connection setup response message.

The present invention also correspondingly proposes a system for a user to participate in local access connection establishment, the system comprising a target mobility management entity and an original mobility management entity, wherein the target mobility management entity is set to be in a situation where a user changes location Next, the PDN connection of the user is established or rejected according to the wishes of the user from the original mobility management entity.

The target mobility management entity is specifically configured to acquire the user's will of the user from the original mobility management entity on the source network side in the tracking area update process, and then establish or according to the user's will from the original mobility management entity. The PDN connection of the user is rejected.

The original mobility management entity is specifically configured to carry the user's wishes through the context response message.

The original mobility management entity is specifically configured to actively move to the target mobility in the handover process. The management entity sends the user's willingness to the user;

The embodiments of the present invention are further described in detail below with reference to the specific embodiments, so that those skilled in the art can understand the present invention and can be practiced without departing from the scope of the invention. Example 1

This embodiment describes an application scenario of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) system based on an evolved universal mobile communication system.

FIG. 6 is a schematic flowchart of the initial connection of the SIPTO connection and the core network connection establishment according to the embodiment of the present invention (based on the system shown in FIG. 1 and the data flow shown in FIG. 5). As shown in FIG. 6, the embodiment specifically includes the following. Steps:

Step 601: The user terminal needs to establish a Radio Resource Control (RRC) connection as a bearer of signaling messages or service data before performing communication.

Step 602: The user terminal sends a message that initializes a non-access stratum (NAS) message, carries the user's will, and performs an attach operation. Here the user's wishes are to allow or disallow the establishment of a SIPTO connection.

Step 603: The wireless side network element sends the initial user message to the mobility management entity, and forwards the attach request and the user's will to the mobility management entity. If there is a home base station gateway, it is forwarded to the home base station gateway, and then the home base station gateway sends the message to the mobility management entity. In the LTE system, the mobility management entity is MN.

Step 604: The mobility management entity starts the authentication and security process, and performs verification on the user terminal. Certificate.

Step 605: The mobility management entity requests the HSS to perform location update.

Step 606: The HSS responds to the mobility management entity with a location update response, and sends the user's subscription data to the mobility management entity.

Step 607: The mobility management entity determines whether to establish a SIPTO connection or establish a core network connection according to the user's will, network capability, subscription data, or local policy. If the SIPT0 connection needs to be established, the L-PGW located at the radio side network element/home base station gateway is selected to serve the user; if the core network connection needs to be established, the PGW located in the core network is selected to serve the user.

Step 608: The mobility management entity sends a session establishment request to the S-GW to create a default bearer to the SGW.

Step 609: If, in step 607, the mobility management entity decides to establish a SIPTO connection, the S-GW sends a session establishment request message to the local gateway to create a default bearer to the local gateway.

Step 609a: The local gateway sends a session establishment response to the S-GW, and the process goes to step 611. Step 610: If, in step 607, the mobility management entity decides to establish a core network connection, the S-GW sends a session establishment request message to the core network gateway.

Step 610a: The core network gateway sends a session establishment response to the S-GW, and the process goes to step 611. Step 611: The S-GW sends a session establishment response to the mobility management entity. Step 613: Perform an RRC connection configuration process.

Step 614: The radio side network element replies to the mobility management entity initial context establishment response.

Step 615: The terminal sends a direct transmission message to the wireless side network element, including the attachment completion information.

Step 616: The wireless side network element sends an attach complete message to the mobility management entity.

Step 617: After receiving the initial context response message of step 614 and the attach complete message of step 616, the mobility management entity sends a request to update the bearer message to the S-GW.

Step 618: If in step 607, the mobility management entity decides to establish SIPTO The S-GW sends a bearer update message to the local gateway.

Step 618a: The local gateway responds to the S-GW bearer update response message, and proceeds to step 620. Step 619: If, in step 607, the mobility management entity decides to establish a core network connection, the S-GW sends a bearer update message to the core network gateway.

Step 619a: The core network gateway responds to the S-GW bearer update response message, and proceeds to step 620. Step 620: The S-GW responds to the mobility management entity to carry an update response message. The PDN connection establishment process in the attach process is completed. Example 2

FIG. 7 is a schematic flowchart of a user terminal actively establishing a PDN connection according to Embodiment 2 of the present invention (based on the system architecture shown in FIG. 1 and the data flow shown in FIG. 5). As shown in FIG. 7, the method includes the following steps: Step 701: User terminal When in the connected state, the PDN connection establishment request is initiated to carry the user's will. If the user is in an idle state, the service request process is initiated first, and then a P匪 connection establishment request is initiated. Here the user's intention is to allow or not allow the establishment of the S IPT0 connection.

Step 702: The mobility management entity determines whether to establish a SIPTO connection or establish a core network connection according to the user's intention, the network capability, the subscription data, or the local policy, and sends a session establishment request to the S-GW according to the judgment result.

Step 703: If in step 702, the mobility management entity decides to establish a SIPTO connection, the S-GW sends a session establishment request message to the local gateway.

Step 703a: The local gateway sends a session establishment response to the S-GW.

Step 704: If, in step 702, the mobility management entity decides to establish a core network connection, the S-GW sends a session establishment request message to the core network gateway.

Step 704a: The core network gateway sends a session establishment response to the S-GW.

Step 705: The S-GW sends a session establishment response to the mobility management entity.

Step 706: The mobility management entity initiates a bearer setup request to the radio side network element, including a PDN connection request message. Step 707: Perform an RRC connection configuration process.

Step 708: The radio side network element returns a mobility management entity bearer setup response.

Step 709: The user terminal sends a direct transmission message to the radio side network element, and includes a PDN connection establishment complete message.

Step 710: The radio side network element sends a PDN connection establishment complete message to the mobility management entity. Step 711: The mobility management entity sends a bearer modification request to the S-GW.

Step 712: If, in step 702, the mobility management entity decides to establish a SIPTO connection, the S-GW sends a bearer modification message to the local gateway.

Step 712a: The local gateway responds to the S-GW to change the response message.

Step 713: If, in step 702, the mobility management entity decides to establish a core network connection, the S-GW sends a bearer modification request message to the core network gateway.

Step 713a: The core network gateway responds to the S-GW to change the response message.

Step 714: The S-GW responds to the mobility management entity bearer modification response message, and the entire PDN connection process is completed. Example 3

FIG. 8 is a schematic diagram of a process for a user to reject a SIPTO connection after the user attaches to establish a SIPTO connection, and the network side notifies the user terminal of the SIPTO connection type, and the user rejects the SIPTO connection according to the system architecture shown in FIG. The data flow shown in FIG. 5, as shown in FIG. 8, the method in this embodiment specifically includes the following steps:

Step 801: After the user terminal establishes a SIPTO connection or the user establishes a SIPTO connection in the PDN connection establishment process, the network side notifies the user of the SIPTO connection type, and the user wishes to refuse the SIPTO connection, and initiates a PDN connection release request to carry the user. Willingness. The user's willingness here is to reject the SIPTO connection.

When a user initiates a PDN connection release request, it must be in the connected state. If the user is in the idle state, the service request process must be initiated first. Step 802: The mobility management entity saves the user's will carried in step 801 for a period of time, and is used to establish a core network connection to the user terminal next time. The mobility management entity triggers the release of the PDN connection.

Step 803: The mobility management entity sends a delete session request message to the S-GW, requesting to delete the bearers between the two.

Step 804: The S-GW sends a delete session request message to the local gateway.

Step 805: The local gateway sends a session deletion response to the S-GW.

Step 806: The S-GW sends a session deletion response to the mobility management entity.

Step 807: The mobility management entity deletes the bearer associated with the bearer and initiates a bearer release request to the radio side network element to release the radio side bearer resource.

Step 808: Perform an RRC connection reconfiguration process between the wireless side network element and the user terminal. Step 809: The radio side network element returns a mobility management entity bearer release response.

Step 810: The user terminal sends a direct transmission message to the radio side network element, including a bearer release completion message.

Step 811: The radio side network element sends a bearer release complete message to the mobility management entity, and the PDN release process initiated by the user ends.

If the reason for the user to release the local PDN connection is that the user wishes to reject the SIPTO connection and wants to establish a connection to the core network, after the release process ends, the PDN connection establishment process to the core network needs to be re-initiated. Example 4

9 is a process in which the user in the embodiment of the present invention establishes a SIPTO connection to the user in the PDN connection establishment process, and notifies the user of the PDN connection type. After receiving the PDN connection type, the user decides to refuse or accept according to his or her will. The flow chart of the SIPTO connection is based on the system architecture shown in FIG. 1 and the data flow shown in FIG. 5. As shown in FIG. 9, the method in this embodiment specifically includes the following steps:

Step 901: The user terminal in the connected state initiates a PDN connection request. Step 902: The mobility management entity determines to establish a SIPTO connection according to the network capability, the subscription data, or the local policy, and sends a session establishment request message to the S-GW.

Step 903: The S-GW sends a session establishment request message to the local gateway.

Step 904: The local gateway sends a session establishment response to the S-GW.

Step 905: The S-GW sends a session establishment response to the mobility management entity.

Step 906: The mobility management entity initiates a bearer setup request to the radio side network element, and includes a PDN connection request message, and carries a PDN connection type, where the PDN connection type indication is a SIPTO connection.

Step 907: Perform an RRC connection configuration process.

Step 908: The radio side network element returns a mobility management entity bearer setup response.

Step 909: The user terminal decides to accept the SIPTO connection according to its own will, and sends a direct transmission message to the wireless side network element, where the SIPTO connection is established, where the user wishes to accept the SIPTO connection; the user terminal rejects the SIPTO connection according to his or her will. Then, the direct transmission message is sent to the wireless side network element, and the direct transmission message includes the user's will. The user's willingness here is to reject the SIPTO connection.

Step 910: The wireless side network element sends a PDN connection establishment complete message to the mobility management entity. If the user wishes to reject the SIPTO connection, the completion message includes the user's will.

Step 911: After receiving the PDN connection establishment complete message sent by the wireless side, if the mobility management entity finds that the user's intention is to reject the SIPTO connection, the local marking user does not allow SIPTO, and saves the user's will for a period of time for the user terminal. When a PDN connection is established, the SIPTO connection is no longer established but a connection to the core network is established.

Step 912: The mobility management entity releases the previously established local connection, and in order to ensure the connectivity of the user service, request to re-establish the PDN connection to the core network. Example 5

10 is a user in the embodiment 5 of the present invention, the network side establishes a SIPTO connection to the user, and notifies the user of the PDN connection type, and the user rejects or accepts according to his or her will. The flow chart of the SIPTO connection is based on the system architecture shown in FIG. 1 and the data flow shown in FIG. 5. As shown in FIG. 10, the method in this embodiment specifically includes the following steps:

Step 1001: The user terminal needs to establish an RRC connection as a bearer of signaling messages or service data before performing communication.

Step 1002: The user terminal sends an initial NAS message to start the attach process.

Step 1003: The wireless side network element sends the initial user message to the mobility management entity, and forwards the NAS message to the mobility management entity. If there is a home base station gateway, it is forwarded to the home base station gateway, and then the home base station gateway sends the message to the mobility management entity. In the LTE system, the mobility management entity is the MME.

Step 1004: The mobility management entity starts the authentication and security process, and performs verification on the user terminal.

Step 1005: The mobility management entity requests the HSS to perform location update.

Step 1006: The HSS responds to the mobility management entity with a location update response.

Step 1007: The mobility management entity determines to establish according to network capabilities or local policies, and the like.

The SIPTO connection selects the L-PGW located at the radio side network element/home base station gateway to serve the user, and sends a session establishment request to the S-GW.

Step 1008: The S-GW sends a session establishment request message to the local gateway.

Step 1009: The local gateway sends a session establishment response to the S-GW.

Step 1010: The S-GW sends a session establishment response to the mobility management entity. The request message contains an attach accept message and carries a PDN connection type indicating the SIPTO connection.

Step 1012: Perform an RRC connection configuration process.

Step 1013: The radio side network element replies to the mobility management entity initial context establishment response. Step 1014: After the user terminal receives the PDN connection type, it is a SIPTO connection, according to itself. The willingness to decide to reject the SIPTO connection, send a direct transmission message to the wireless side network element, including the attachment completion message, the user wishes, where the user wishes to reject the SIPTO connection; the user terminal receives the PDN connection type after the SIPTO connection, according to their own wishes After accepting the SIPTO connection, the device sends a direct transmission message to the wireless side network element, including an attach completion message, and the user wishes, where the user wishes to accept the SIPTO connection;

Step 1015: The wireless side network element sends an attach complete message to the mobility management entity, carrying the user's will.

Step 1016: After receiving the context establishment response of step 1013 and the attach completion message of step 1015, the mobility management entity records the user's will if the user wishes to reject the SIPTO connection, and saves the user's will (rejects the SIPTO connection) for a period of time, The next time the core network connection is established to the user terminal, the mobility management entity releases the previously established local connection and requests the user terminal to re-attach, establishing a PDN connection to the core network at the next attachment. Example 6

If the user establishes a SIPTO connection on the source network side before the location change process or has requested to establish a SIPTO connection, the original mobility management entity on the source network side saves the user SIPTO wish. Subsequently, when the user performs tracking area update across the network side, the original mobility management entity may transfer the saved user SIPTO willingness to the target mobility management entity.

FIG. 11 is a schematic flow chart of the original mobility management entity transmitting the saved user SIPTO willingness to the target mobility management entity in the tracking area update process of the user across the network in the embodiment 6 of the present invention. As shown in FIG. 11, the process specifically includes the following steps:

Step 1101: The terminal sends a tracking area update request message to the target mobility management entity by using the target radio side network element, where the message may carry the activation identifier.

Step 1102: The target mobility management entity sends a context request message to the original mobility management entity.

Step 1103: The original mobility management entity sends a context response to the target mobility management entity. The message carries the user SIPTO willingness, and after the target mobility management entity receives the user's SIPTO will, it saves it for use in the subsequent gateway relocation process, referring to the user SIPTO. Step 1104: Optionally, the terminal, the target The mobility management entity and the authentication authorization server perform an authentication process;

Step 1105: The target mobility management entity sends a context confirmation message to the original mobility management entity.

Step 1106: The target mobility management entity sends a modify bearer request to the serving gateway to request a bearer modification operation.

Step 1107: The serving gateway may send a modify bearer request to the local gateway.

Step 1108: The local gateway may respond to the service gateway to modify the bearer response.

Step 1109: The service gateway returns a modify bearer response to the target mobility management entity. Step 1110: Perform a location update process between the target mobility management entity and the authentication authorization server.

Step 1111: Perform a location cancellation process between the authentication authorization server and the original mobility management entity.

Step 1112: The target mobility management entity sends a tracking area update accept message to the user via the target wireless side network element.

It should be noted that after step 1110, the target mobility management entity may perform gateway relocation, and the target mobility management entity refers to the user SIPTO willingness when performing gateway relocation.

In this embodiment, the user can decide whether to accept or reject the SIPTO connection based on his/her own will, and the user SIPTO will also be different depending on the APN, location information or other information. Example 7

In this embodiment, the user never establishes a SIPTO connection or requests to establish a SIPTO connection before the location change process, that is, the original mobility management entity on the source network side has no user SIPTO. In the will, the user in the tracking area update process that needs to establish a radio bearer, the target network side actively asks the user for the SIPTO willingness. FIG. 12 is a schematic diagram of a flow of a target mobility management entity actively inquiring a user's SIPTO intention during a tracking area update process according to Embodiment 7 of the present invention. As shown in FIG. 12, the process specifically includes the following steps:

Step 1201: The terminal sends a tracking area update request message to the target mobility management entity via the target radio side network element, where the message carries the activation identifier.

Step 1202: The target mobility management entity sends a context request message to the original mobility management entity.

Step 1203: The original mobility management entity sends a context response message to the target mobility management entity. In this embodiment, the message does not carry the user SIPTO willingness;

Step 1204: Optionally, the terminal, the target mobility management entity, and the authentication authorization server perform an authentication process.

Step 1205: The target mobility management entity sends a context confirmation message to the original mobility management entity.

Step 1206: The target mobility management entity requests a bearer modification operation from the serving gateway. Step 1207: The serving gateway may send a modify bearer request to the local gateway.

Step 1208: The local gateway can respond to the monthly service gateway tampering response;

Step 1209: The serving gateway responds to the target mobility management entity to modify the bearer response. Step 1210: Perform a location update process between the target mobility management entity and the authentication authorization server.

It should be noted that after step 1210, the target mobility management entity may perform gateway relocation selection.

Step 1211: Perform a location cancellation process between the authentication authorization server and the original mobility management entity.

Step 1212, target mobility tube a request message and a tracking area update accept message, carrying a PDN connection type;

It should be noted that, if the target mobility management entity performs gateway relocation after step 1210, and finds that the current gateway is suitable for the SIPTO connection, the target mobility management entity carries the PDN connection type in the tracking area accept message, and the PDN connection type Indicates SIPTO.

Step 1213: The target radio side network element performs a radio bearer setup process; the radio bearer setup complete message carries the user SIPTO willingness;

It should be noted that after receiving the SIPTO PDN connection type, the user decides whether to reject or accept the SIPTO PDN connection according to his or her will and bring his SIPTO willingness to the target network side.

After receiving the SIPTO of the user, the target network side decides whether to maintain or release the established core network connection according to the user's SIPTO intention.

If the tracking area update process does not need to establish a radio bearer, the original mobility management entity and the target mobility management entity do not know the user's SIPTO intention at the same time, and the target network side finds that the current gateway is suitable for the SIPTO connection when doing the gateway relocation. The target network side may carry the SIPTO PDN connection type to the user by adding a message or using a message similar to the previous embodiment after the tracking area update process ends, and the user decides whether to accept or reject the PDN connection according to his or her own will. The target network side may also not immediately query the user's SIPTO willingness after the tracking area update process ends, but wait for the next time the user enters the connected state, and the target network side determines that a SIPTO connection needs to be established, and then actively uses a message similar to the above or Ask the user SIPTO willingness by adding a message. Example 8

In this embodiment, the user has established a SIPTO connection before the handover procedure or has requested to establish a SIPTO connection, and the original mobility management entity in the source network side transmits the saved user SIPTO will transfer to the target mobility management entity in the handover process. . Figure 13 is an eighth embodiment of the present invention The process diagram of the original mobility management entity in the source network side to transfer the saved user SIPTO will be transferred to the target mobility management entity in the handover. As shown in FIG. 13, the process specifically includes the following steps:

Step 1301: The original radio side network element determines that an S1 handover needs to be initiated.

Step 1302: The original radio side network element sends a handover request to the original mobility management entity. Step 1303: The original mobility management entity sends a relocation forward request message to the target mobility management entity, where the message carries the user SIPTO willingness;

If the original mobility management entity has the SIPTO willingness of the user, the original mobility management entity may bring the user SIPTO willingness to the target mobile in the relocation forward request message of this step or in the subsequent relocation forward completion confirmation message. Sexual management entity. The target mobility management entity saves the user SIPTO willingness to refer to the user SIPTO willingness in the subsequent gateway relocation process.

Step 1304: The target mobility management entity may initiate a session establishment process of the local IP connection to the serving gateway.

Step 1305: The target mobility management entity requests the target radio side network element to perform handover. Step 1306: The target radio side network element responds to the target mobility management entity with a handover request acknowledgement message.

Step 1307: The target mobility management entity sends a relocation forward response message to the original mobility management entity.

Step 1308: The original mobility management entity sends a handover command to the original radio side network element. Step 1309: The original radio side network element sends a handover command to the terminal.

Step 1310: The terminal initiates a handover confirmation message to the target radio side network element.

Step 1311: The target radio side network element notifies the target mobility management entity to perform the handover. Step 1312: The target radio side network element sends a relocation forward completion notification message to the original mobility management entity.

Step 1313: The original wireless side network element returns the relocation forward to the target mobility management entity. Confirmation message

Step 1314: The subsequent process of the handover process is performed, and the subsequent process is similar to the prior art, and no comment is made here.

If the original mobility management entity and the target mobility management entity do not know the user SIPTO willingness when the user initiates the handover, the tracking area update process described in the previous embodiment may be used in the tracking area update process after the cross-network side handover. The way to obtain the user SIPTO will be obtained in order to obtain the user SIPTO willingness.

It should be noted that the message used to carry the user's SIPTO intention is not limited to the message given in the embodiment of the present invention, and the user SIPTO intention may also be carried by the message having the similar function as the message in this embodiment, or extended. New message to achieve.

It should be noted that the local gateway in the present invention may be an L-SGW and an L-PGW, or may be a separate L-PGW, or may be a data offload function entity; a SIPTO wireless side network element may be connected to a local gateway. The addresses are the same; SIPTO connections can be local IP access to the user's local network, local IP access to the company's local network, local IP access to the Internet, Internet traffic shunting, or specific IP data offloading.

It should be noted that, in order to simplify the description, the above embodiment only uses the case of FIG. 1 as an example to describe the management manner of the SIPTO connection. In the case of the local gateway and the wireless side network element division, FIG. 2, and FIG. 3 system in FIG. 1, regardless of the SIPTO connection mode shown in FIG. 4 or FIG. 5, the UTRAN or E-UTRAN system, the flow of the user perceives the SIPTO connection and the above The embodiments are similar and will not affect the description of the present invention, and therefore will not be described again.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, 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 separately fabricated into individual integrated circuit modules, or they may be Multiple modes Blocks or steps are made in 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 a user to participate in a local access connection establishment, wherein the method includes: the network side establishes or rejects a PDN connection according to a message sent by the user that carries the user's will.

2. The method according to claim 1, wherein the message sent by the user is a PDN connection establishment request message.

The method according to claim 1, wherein, before the user sends the message carrying the user's will, the method further includes: when the network side determines that the PDN connection type that needs to be established for the user is a SIPTO connection, obtaining the user's will,

The message sent by the user is a PDN connection setup response message.

The method according to claim 2, wherein the network side establishes or rejects the PDN connection according to the PDN connection establishment request message sent by the user to carry the user:

The user desires to establish a PDN connection of a specified type, and the network side establishes a corresponding PDN connection for the user according to the user's will, network capability, local policy, and subscription decision, and then establishes the PDN connection of the specified type;

5. The method according to claim 3, wherein the network side establishes or rejects the PDN connection according to the PDN connection establishment response message sent by the user to carry the user:

The user determines whether to allow the SIPTO connection according to the PDN connection type sent by the network side; if the user wishes to accept the SIPTO connection, the network side establishes a SIPTO connection; if the user wishes to reject the SIPTO connection, the network side establishes a core network PDN connection for the user. , or not established

PDN connection.

The method according to any one of claims 1 to 5, wherein the PDN connection type comprises one or more of the following: a core network connection, a SIPTO connection.

The method according to claim 3 or 5, wherein, when the user refuses to establish a SIPTO connection, the method further includes: the user notifying the network side to perform a PDN connection release operation, or the user carrying the parameter to initiate a PDN connection release operation .

A system in which a user participates in a local access connection establishment, where the system includes a network side and a user side;

9. The system according to claim 8, wherein the message sent by the user side is a PDN connection setup request message.

10. The system according to claim 8, wherein

The message sent by the user side is a PDN connection setup response message.

The system according to claim 9, wherein the network side establishes or rejects the PDN connection according to the PDN connection establishment request message sent by the user to carry the user:

12. The system according to claim 10, wherein the network side establishes or rejects the PDN connection according to a PDN connection setup response message sent by the user to carry the user:

PDN connection.

13. The system according to claim 10 or 12, wherein

A method for a user to participate in a local access connection establishment, wherein the method includes: in a case where a user changes a location, the target mobility management entity establishes or rejects the PDN of the user according to a user's willingness from the original mobility management entity. connection.

The method according to claim 14, wherein the method specifically includes: in the tracking area update process, the target mobility management entity acquires the user's will of the user from the original mobility management entity on the source network side, and then according to The user from the original mobility management entity wishes to establish or reject the PDN connection of the user.

The method according to claim 15, wherein the original mobility management entity carries the user's will through the context response message.

The method according to claim 14, wherein the method specifically includes: in the handover process, the original mobility management entity on the source network side actively sends the user's will of the user to the target mobility management entity, and then the target The mobility management entity establishes or denies the PDN connection of the user according to the user's wishes from the original mobility management entity.

18. The method according to claim 17, wherein the original mobility management entity sends the user's will to the target mobility management entity by using a relocation forward request message or a relocation forward completion confirmation message.

The method according to claim 16 or 18, wherein the target mobility management entity establishes or rejects the PDN connection according to a message sent by the original mobility management entity:

The method according to any one of claims 14 to 18, wherein the PDN connection type comprises one or more of the following: a core network connection, a SIPTO connection.

A system in which a user participates in a local access connection establishment, where the system includes a target mobility management entity and an original mobility management entity, where the target mobility management entity is set to be in a case where a user changes location, The PDN connection of the user is established or rejected according to the wishes of the user from the original mobility management entity.

22. The system of claim 21, wherein

The target mobility management entity is specifically configured to acquire the user's will of the user from the original mobility management entity on the source network side during the tracking area update process, and then establish or according to the user's will from the original mobility management entity. The PDN connection of the user is rejected.

23. The system of claim 22, wherein The original mobility management entity is specifically configured to carry the user's will by the context response message.

24. The system of claim 21, wherein

25. The system of claim 24, wherein