CN102438328A

CN102438328A - Method and system for establishing user-involved and local access connection

Info

Publication number: CN102438328A
Application number: CN2011101644873A
Authority: CN
Inventors: 雷小燕; 王静; 周娜
Original assignee: ZTE Corp
Current assignee: Greely (Jiangsu) Intelligent Technology Co.,Ltd.
Priority date: 2010-09-29
Filing date: 2011-06-17
Publication date: 2012-05-02
Anticipated expiration: 2031-06-17
Also published as: CN102438328B; WO2012041131A1

Abstract

The invention discloses a method for establishing a user-involved and local access connection. The method comprises the following step that: a network side establishes or rejects a PDN (public data network) connection according to a message which carries user intention and is sent by a user, or a target MME (mobility management entity) establishes or rejects the PDN connection of the user according to the user intention from an original mobility management entity under the condition that the position of the user is changed. The invention also correspondingly discloses a system for establishing a user-involved and local access connection. SIPTO (selected internet protocol traffic offload) connections established according to the invention can be perceived by the user, therefore even the QoS (quality of service) of the user can not be ensured due to feeder loss or local control and the like after the SIPTO connections are established, the user also has psychological preparation, thus improving the service experience of the user.

Description

A kind of user participates in this accessing and connects the method and system of setting up

Technical field

The present invention relates to mobile communication technology, relate in particular to a kind of user and participate in the method and system that this accessing connects foundation.

Background technology

Third generation partner program (3rd Generation Partnership Project; 3GPP) the grouping system of evolution (Evolved Packet System; EPS) by UMTS land radio access web (the Evolved Universal Terrestrial Radio Access Network of evolution; E-UTRAN), Mobility Management Entity (Mobility Management Entity; MME), gateway (Serving Gateway, S-GW), grouped data network gateway (Packet Data Network Gateway, P-GW or PDNGW), home subscriber server (Home Subscriber Server; HSS), the authentication and authorization charging of 3GPP (Authentication, Authorization and Accounting; AAA) server, "Policy and Charging Rules Function (Policy and Charging Rules Function, PCRF) form by entity and other support nodes.Wherein, Mobility Management Entity is responsible for the related work of the chain of command such as processing and the contextual management of user's mobile management of mobile management, Non-Access Stratum signaling; IAD comprises S-GW and P-GW, and S-GW is the accessing gateway equipment that links to each other with E-UTRAN, between E-UTRAN and P-GW, transmits data, and is responsible for pending datas such as paging are carried out buffer memory; P-GW then is that (PacketData Network, borde gateway PDN) are responsible for the access of PDN and between EPS and PDN, are transmitted function such as data for EPS and packet data network; The Authentication Authorization server comprises HSS, 3GPP AAA; PCRF is the "Policy and Charging Rules Function entity, and it links to each other with operator IP operation network through receiving interface Rx, obtains business information; In addition; It links to each other with gateway device in the network through the Gx/Gxa/Gxc interface, is responsible for initiating the foundation that IP carries, service quality (the Quality of Service of assurance business datum; And the control of chargeing QoS).

A kind of as new access service mode; Base station from home is a kind of small-sized, lower powered base station; Be deployed in indoor places such as family and office; Main effect is in order higher service rate to be provided to the user and to reduce and use the needed expense of high rate services, remedying the deficiency that existing distributed cellular radio communication system covers simultaneously.The advantage of base station from home is economical, convenient, low-power output, plug and play etc.In the family expenses base station system, base station from home is the wireless side network element.

Fig. 1, Fig. 2, Fig. 3 are respectively the connection sketch map of three kinds of cordless communication networks in the prior art; Can find out that base station from home is directly connected to core network among Fig. 1, base station from home is linked into core network through this logical ne of home base-station gateway among Fig. 2; Wherein, The home base-station gateway major function is: the fail safe of checking base station from home, handle the registration of base station from home, and base station from home is carried out operation maintenance management; According to Carrier Requirements configuration and control base station from home, be responsible for the data of exchcange core net and base station from home.

Except the access of supporting mobile core network, GSM (comprising the base station from home system) can support that also (Selected IP Traffic Offload, SIPTO) function realize this locality access of terminal to the internet to specific IP data distribution.

The realization of SIPTO can provide providing powerful support for SIPTO through setting up local gateway in Fig. 1, Fig. 2 and the system shown in Figure 3; Local gateway is linked into the gateway of external network (for example Internet) as this locality; Address assignment, charging, packet package filtration, policy control, data distribution function, NAS/S1-AP/RANAP (Radios Access Network Application Part are provided; The wireless access network applying portion)/general tunnel protocol (General Tunneling Protocol; GTP)/proxy mobile IP protocol (ProxyMobile IP; PMIP)/mobile IP protocol (Mobile IP, MIP) message parse, network address translation (Network Address Translation, NAT), function such as IP distributing strategy route and execution.Local gateway can close with the wireless side network element and establish, and also can arrange separately.

Exist under the situation of home base-station gateway, local gateway not only can close with base station from home to be established (as shown in Figure 2) or sets up separately, also can close with home base-station gateway to establish (as shown in Figure 3) or set up separately.Wherein, The wireless side network element is that the base station from home subsystem comprises base station from home and/or home base-station gateway, and local gateway can be that (Local SGW is L-SGW) with local packet data gateway (Local PGW for the local service gateway; L-PGW), also can be independent L-PGW or data distribution functional entity.In addition, home base-station gateway can close with base station from home and establish.

Fig. 4, Fig. 5 are respectively wireless communication system in the prior art to carry out two kinds of SIPTO and connects sketch mapes.In the prior art; When the user uses the SIPTO function; Carry out data distribution by local gateway and since local gateway generally be placed on family, enterprises or near, the manager of family or enterprise can be provided with corresponding firewall policy and limit the visit of certain user to other external IP network on local gateway; Cause some professional can not normally execution, this operation is that operator is uncontrollable.Because the mobile network is uncontrollable to the local gateway local policy, can't guarantee user's quality of service in addition, say that from user satisfaction this moment, the user possibly more expect to use core net connected reference external network.

Summary of the invention

In view of this, main purpose of the present invention is to provide a kind of user to participate in the method and system that this accessing connects foundation, can set up SIPTO according to user intention and connect, thereby improve user experience.

For achieving the above object, technical scheme of the present invention is achieved in that

A kind of user participates in this accessing and connects the method for setting up, and comprising: the message of carrying user intention that network side sends according to the user is set up or refusal PDN connects.

Said messages sent by users is that request message is set up in the PDN connection.

The user sends and carries before the message of user intention, and this method also comprises: when network side is confirmed for the PDN connection type that the user sets up to be the SIPTO connection, obtain user intention,

Said messages sent by users is a PDN connection establishment response message.

Request message foundation is set up in the PDN connection of carrying user intention that said network side sends according to the user or refusal PDN is connected to:

Said user intention is that the PDN connection and the network side that allow to set up specified type connect for the user sets up corresponding PDN according to said user intention, network capabilities, local policy, the signatory decision, and the PDN that then sets up said specified type connects;

Said user intention is that the PDN connection and the network side that allow to set up specified type do not connect for the user sets up corresponding PDN according to said user intention, network capabilities, local policy, signatory decision; Then connect, or request message is set up in the PDN of refusing user's connection for the user sets up the core network PDN;

Said user intention connects for not allowing the PDN that sets up specified type, and then the core network PDN connects network side or request message is set up in the PDN connection of refusing user's for the user sets up.

The PDN connection establishment response message of carrying user intention that said network side sends according to the user is set up or refusal PDN is connected to:

The PDN connection type that said user sends according to network side judges whether to allow SIPTO to connect;

Said user intention connects for accepting SIPTO, and then network side is set up the SIPTO connection; User intention connects for refusal SIPTO, and then network side connects for the user sets up the core network PDN, or does not set up the PDN connection.

Said PDN connection type comprise following one or more: core net connects, SIPTO connects.

When said user's refusal was set up the SIPTO connection, this method also comprised: the user notification network side carries out PDN and connects releasing operation, and perhaps, the user carries parameter and initiatively initiates PDN connection releasing operation.

A kind of user participates in this accessing and connects the system that sets up, and comprises network side and user side; Wherein,

Said network side is used for setting up or refusal PDN connection according to the message of carrying user intention that user side sends.

The message that said user side sends is that request message is set up in the PDN connection.

Said network side also is used for when confirming for the PDN connection type that the user sets up to be the SIPTO connection, obtaining user intention;

The message that said user side sends is PDN connection establishment response message.

Said user intention connects for not allowing the PDN that sets up specified type, and then network side connects for the user sets up the core network PDN, or request message is set up in the PDN of refusing user's connection.

Said user side also is used for when user's refusal is set up the SIPTO connection, and the informing network side is carried out PDN and connected releasing operation, perhaps, carries parameter and initiatively initiates PDN connection releasing operation.

A kind of user participates in this accessing and connects the method for setting up, and comprising:

Under the situation that user's occurrence positions changes, target mobility management entity is according to the PDN connection of setting up or refuse said user from the user intention of former Mobility Management Entity.

This method specifically comprises: in the tracing section updating process; Target mobility management entity is obtained said user's user intention to the former Mobility Management Entity of source network side, sets up according to said user intention from former Mobility Management Entity afterwards or the PDN that refuses said user connects.

Said former Mobility Management Entity carries user intention through context response information.

This method specifically comprises: in handoff procedure; The former Mobility Management Entity of source network side initiatively sends said user's user intention to target mobility management entity; Afterwards, target mobility management entity sets up or refuses said user's PDN connection according to said user intention from former Mobility Management Entity.

Said former Mobility Management Entity changes before through reorientation to change before request message or the reorientation to be accomplished acknowledge message and sends user intention to target mobility management entity.

The message that said target mobility management entity is sent according to former Mobility Management Entity is set up or refusal PDN is connected to:

Said user intention is that the PDN connection and the target mobility management entity that allow to set up specified type connect for the user sets up corresponding PDN according to said user intention, network capabilities, local policy, the signatory decision, and the PDN that then sets up said specified type connects;

Said user intention is that the PDN connection and the target mobility management entity that allow to set up specified type do not connect for the user sets up corresponding PDN according to said user intention, network capabilities, local policy, signatory decision; Then connect, or request message is set up in the PDN of refusing user's connection for the user sets up the core network PDN;

Said user intention connects for not allowing the PDN that sets up specified type, and then the core network PDN connects target mobility management entity or request message is set up in the PDN connection of refusing user's for the user sets up;

Said user intention connects for accepting SIPTO, and then network side is set up the SIPTO connection; User intention connects for refusal SIPTO, and then target mobility management entity connects for the user sets up the core network PDN, or does not set up the PDN connection.

A kind of user participates in this accessing and connects the system that sets up; Comprise target mobility management entity and former Mobility Management Entity; Wherein, Said target mobility management entity is used under the situation that user's occurrence positions changes, according to the PDN connection of setting up or refuse said user from the user intention of former Mobility Management Entity.

Said target mobility management entity; Specifically be used for obtaining said user's user intention to the former Mobility Management Entity of source network side, set up according to said user intention afterwards or the PDN that refuses said user connects from former Mobility Management Entity in the tracing section updating process.

Said former Mobility Management Entity specifically is used for carrying user intention through context response information.

Said former Mobility Management Entity specifically is used for initiatively sending said user's user intention to target mobility management entity at handoff procedure;

Said user's PDN connection is specifically set up or refuse to said target mobility management entity according to said user intention from former Mobility Management Entity.

Said former Mobility Management Entity specifically sends user intention through commentaries on classics completion acknowledge message before changeing request message or reorientation before the reorientation to target mobility management entity.

User of the present invention participates in this accessing and connects the method and system of setting up; The user intention that network side sends according to the user is set up or refusal PDN connects; Perhaps, target mobility management entity is according to setting up from the user intention of former Mobility Management Entity or refusal PDN connection.SIPTO connection through the present invention sets up all can be by user's perception; So; Set up the back because feeder loss or local control wait the quality of service that can't guarantee the user even SIPTO connects, the user also has psychological preparation, thereby can improve user's business experience sense.

Description of drawings

Fig. 1 is the connection sketch map of a kind of cordless communication network in the prior art;

Fig. 2 is the connection sketch map of another kind of cordless communication network in the prior art;

Fig. 3 is the connection sketch map of another cordless communication network in the prior art;

Fig. 4 carries out a kind of connection sketch map of SIPTO for wireless communication system in the prior art;

Fig. 5 connects sketch map for the another kind that wireless communication system in the prior art carries out SIPTO;

Fig. 6 is that the embodiment of the invention 1 user initially adheres to and carries out SIPTO and connect the schematic flow sheet that is connected foundation with core net;

Fig. 7 initiatively sets up the schematic flow sheet that PDN connects for the embodiment of the invention 2 user terminals;

Fig. 8 is that user SIPTO wish changed after the embodiment of the invention 3 user SIPTO connected the foundation completion, initiatively initiates to discharge the schematic flow sheet of SIPTO connection;

Fig. 9 is that the embodiment of the invention 4 users connect the schematic flow sheet of setting up refusal SIPTO connection in the process at PDN;

Figure 10 is that the embodiment of the invention 5 users are adhering to the schematic flow sheet of setting up refusal SIPTO connection in the PDN connection procedure;

Figure 11 is the schematic flow sheet that the tracing section updating flow process Central Plains Mobility Management Entity of the embodiment of the invention 6 user's across a network sides sends the user SIPTO wish of preserving to target mobility management entity;

Figure 12 be the embodiment of the invention 7 users in the tracing section updating process, target mobility management entity is initiatively inquired the schematic flow sheet of user SIPTO wish;

Figure 13 is the embodiment of the invention 8 is sent to the user SIPTO wish of preserving target mobility management entity in switching by the former Mobility Management Entity in the source network side a schematic flow sheet.

Embodiment

Basic thought of the present invention is: the user intention that network side sends according to the user is set up or refusal PDN connects, and perhaps, the target mobility management entity basis sets up from the user intention of former Mobility Management Entity or refusal PDN connects.

The method that user of the present invention participates in this accessing connection foundation mainly contains four kinds of implementations:

1) network side is set up request message according to the PDN connection of carrying user intention that the user initiatively sends, and sets up or refusal PDN connection, and this implementation specifically may further comprise the steps:

When the PDN connection was set up, the user sent the PDN connection of carrying user intention (as allowing or do not allow to set up SIPTO) to network side and sets up request message;

Whether network side is that the user sets up corresponding PDN connection according to said user intention, network capabilities, local policy, decision such as signatory.

Concrete: user intention is that the PDN connection and the network side that allow to set up specified type connect for the user sets up corresponding PDN according to said user intention, network capabilities, local policy, the signatory decision, and the PDN that then sets up said specified type connects; User intention is that the PDN connection and the network side that allow to set up specified type do not connect for the user sets up corresponding PDN according to said user intention, network capabilities, local policy, signatory decision; Then connect, or request message is set up in the PDN of refusing user's connection for the user sets up the core network PDN;

User intention connects for not allowing the PDN that sets up specified type, and then network side connects for the user sets up the core network PDN, or request message is set up in the PDN of refusing user's connection.

Connect with SIPTO and to be established as example, PDN connects and sets up request message and carry the user when allowing to set up SIPTO and connecting wish, and network side connects for the user sets up SIPTO; PDN connects and to set up request message and carry when not allowing to set up SIPTO and connecting wish, and network side does not connect for the user sets up SIPTO, and at this moment, network side can connect for the user set up the core network PDN, and PDN that also can refusing user's connects and sets up request message.

When 2) network side is confirmed to set up the SIPTO connection for the user, obtain user intention.This implementation specifically may further comprise the steps:

Network side is confirmed and need be connected for the user sets up SIPTO according to user's request message (connecting the request of foundation, initialization NAS message like PDN), then obtains user intention;

The user is back to network side through PDN connection establishment response message with user intention (promptly accepting SIPTO connection or refusal SIPTO connection);

Network side is set up according to user intention or refusal PDN connects.

Concrete, said user intention connects for accepting SIPTO, and then network side is set up the SIPTO connection; User intention connects for refusal SIPTO, and then network side connects for the user sets up the core network PDN, or does not set up the PDN connection.

Need to prove, above-mentioned PDN connection type comprise following one or more: core net connects, SIPTO connects.

Need to prove that user intention comprises: allow to set up the SIPTO connection, do not allow to set up the SIPTO connection, accept the SIPTO connection, refuse the SIPTO connection.

Need to prove, learn the user PDN connection type that network side issues is SIPTO when connecting, and judges whether accept according to wish; If refusal; The user can the informing network side carry out PDN connection releasing operation so, and perhaps, the user carries parameter and initiatively initiates PDN connection releasing operation; Here, the parameter indication PDN that carries of user connects and discharges or refusal.

3) under the situation that user's occurrence positions changes; Specifically in the tracing section updating flow process; Target mobility management entity is obtained said user's user intention to the former Mobility Management Entity of source network side, sets up according to said user intention from former Mobility Management Entity afterwards or the PDN that refuses said user connects.

Concrete, former Mobility Management Entity can carry user intention through context response information.

The message that target mobility management entity is sent according to former Mobility Management Entity is set up or refusal PDN is connected to:

User intention is that the PDN connection and the target mobility management entity that allow to set up specified type connect for the user sets up corresponding PDN according to said user intention, network capabilities, local policy, the signatory decision, and the PDN that then sets up said specified type connects;

User intention is that the PDN connection and the target mobility management entity that allow to set up specified type do not connect for the user sets up corresponding PDN according to said user intention, network capabilities, local policy, signatory decision; Then connect, or request message is set up in the PDN of refusing user's connection for the user sets up the core network PDN;

User intention connects for not allowing the PDN that sets up specified type, and then the core network PDN connects target mobility management entity or request message is set up in the PDN connection of refusing user's for the user sets up;

User intention connects for accepting SIPTO, and then network side is set up the SIPTO connection; User intention connects for refusal SIPTO, and then target mobility management entity connects for the user sets up the core network PDN, or does not set up the PDN connection.

Need to prove, the PDN connection type described in this implementation can comprise following one or more: core net connects, SIPTO connects.

The user intention implication of describing in user intention described in this implementation and aforementioned first kind of implementation and the second kind of implementation is identical, can comprise: allow to set up SIPTO and connect, do not allow to set up SIPTO and connect, accept that SIPTO connects, refusal SIPTO connects.

Described in this implementation according to user intention set up or the PDN that refuses said user connect also can be with reference to the associated description in aforementioned first kind of implementation and the second kind of implementation.

4) under the situation that user's occurrence positions changes; Specifically in switching flow; The former Mobility Management Entity of source network side initiatively sends said user's user intention to target mobility management entity; Afterwards, target mobility management entity sets up or refuses said user's PDN connection according to said user intention from former Mobility Management Entity.

Concrete, former Mobility Management Entity can send user intention to target mobility management entity through commentaries on classics completion acknowledge message before changeing request message or reorientation before the reorientation.

Need to prove; If the user never set up the PDN connection and also asked to set up the PDN connection before the position change flow process; The former Mobility Management Entity that is the source network side does not have associated user's wish, then can accomplish this accessing according to first kind of implementation or second kind of implementation and connect foundation.

The also corresponding a kind of user of proposition of the present invention participates in this accessing and connects the system that sets up, and this system comprises network side and user side; Wherein,

The also corresponding a kind of user of proposition of the present invention participates in this accessing and connects the system that sets up; This system comprises target mobility management entity and former Mobility Management Entity; Wherein, Said target mobility management entity is used under the situation that user's occurrence positions changes, according to the PDN connection of setting up or refuse said user from the user intention of former Mobility Management Entity.

Said target mobility management entity; Specifically be used for obtaining said user's user intention to the former Mobility Management Entity of source network side, set up according to said user intention afterwards or the PDN that refuses said user connects from former Mobility Management Entity in the tracing section updating flow process.

Said former Mobility Management Entity specifically is used for initiatively sending said user's user intention to target mobility management entity at switching flow;

Below in conjunction with specific embodiment the enforcement of technical scheme of the present invention is done further to describe in detail so that those skilled in the art can better understand the present invention and can implement, but the embodiment that lifts not conduct to qualification of the present invention.

Embodiment 1

Present embodiment has been described UMTS land radio access web (EvolvedUniversal Terrestrial Radio Access Network, the E-UTRAN) application scenarios of system based on evolution.

Fig. 6 is that the embodiment of the invention 1 user initially adheres to and carries out SIPTO and connect the schematic flow sheet (based on system shown in Figure 1, data flow shown in Figure 5) that is connected foundation with core net, and as shown in Figure 6, present embodiment specifically may further comprise the steps:

Step 601: user terminal need be set up Radio Resource control before communicating (Radio ResourceControl, RRC) connection is as the carrying of signaling message or business datum.

Step 602: user terminal sends the initialization Non-Access Stratum, and (Non-Access-Stratum, NAS) message is carried user intention, carries out attach operation.User intention is to allow or do not allow to set up SIPTO to connect here.

Step 603: the wireless side network element is issued Mobility Management Entity with initial user message, and transmits attach request and user intention to Mobility Management Entity.If there is femto gateway, then is transmitted to femto gateway earlier, and then message issued Mobility Management Entity by femto gateway.Mobility Management Entity is MME in the LTE system.

Step 604: Mobility Management Entity is opened authentication and safe procedures, and user terminal is verified.

Step 605: Mobility Management Entity request HSS carries out the position to be upgraded.

Step 606:HSS responds the position to Mobility Management Entity and upgrades response, and user's subscription data is issued Mobility Management Entity.

Step 607: it still is to set up core net to connect that Mobility Management Entity confirms to set up the SIPTO connection according to user intention, network capabilities, subscription data or local policy etc.Setting up SIPTO if desired connects and then to select the L-PGW that is positioned at wireless side network element/femto gateway to serve for the user; Setting up core net if desired connects and then to select the PGW that is positioned at core net to serve for the user.

Step 608: Mobility Management Entity sends session to S-GW and sets up request, is created to the default bearing of SGW.

Step 609: if in step 607, the Mobility Management Entity decision is set up SIPTO and is connected, and S-GW sends session to local gateway and sets up request message, is created to the default bearing of local gateway.

Step 609a: local gateway sends session to S-GW and sets up response, forwards step 611 to.

Step 610: if in step 607, the Mobility Management Entity decision is set up core net and is connected, and S-GW sends session to the core net gateway and sets up request message.

Step 610a: the core net gateway sends session to S-GW and sets up response, forwards step 611 to.

Step 611:S-GW sends session to Mobility Management Entity and sets up response.

Step 612: Mobility Management Entity is initiated initial context to the wireless side network element and is set up request.

Step 613: carry out RRC and connect layoutprocedure.

Step 614: the wireless side network element is replied the Mobility Management Entity initial context and is set up response.

Step 615: direct-sending message is sent to the wireless side network element in the terminal, comprises and adheres to completion information.

Step 616: the wireless side network element sends to Mobility Management Entity and adheres to completion message.

Step 617: Mobility Management Entity receive step 614 initial context response message and step 616 adhere to accomplish message after, upgrade bearer messages to the S-GW request of sending.

Step 618: if in step 607, what the Mobility Management Entity decision was set up is that SIPTO connects, and S-GW sends bearer update message to local gateway.

Step 618a: local gateway is responded S-GW bearer update response message, forwards step 620 to.

Step 619: if in step 607, what the Mobility Management Entity decision was set up is that core net connects, and S-GW sends bearer update message to the core net gateway.

Step 619a: the core net gateway is responded S-GW bearer update response message, forwards step 620 to.

Step 620:S-GW responds Mobility Management Entity bearer update response message.PDN in the attaching process connects the process of setting up to be accomplished.

Embodiment 2

Fig. 7 initiatively sets up the schematic flow sheet (based on system shown in Figure 1 framework, data flow shown in Figure 5) that PDN connects for the embodiment of the invention 2 user terminals, and as shown in Figure 7, the method comprising the steps of:

Step 701: initiatively initiate PDN when user terminal is in connected state and connect the request of foundation, carry user intention.If the user is in Idle state, then at first initiate the service request flow process, initiate PDN again and connect the request of foundation.User intention is to allow or do not allow to set up SIPTO to connect here.

Step 702: it still is to set up core net to connect that Mobility Management Entity confirms to set up the SIPTO connection according to user intention, network capabilities, subscription data or local policy etc., and sends session according to judged result to S-GW and set up request.

Step 703: if in step 702, the Mobility Management Entity decision is set up SIPTO and is connected, and S-GW sends session to local gateway and sets up request message.

Step 703a: local gateway sends session to S-GW and sets up response.

Step 704: if in step 702, the Mobility Management Entity decision is set up core net and is connected, and S-GW sends session to the core net gateway and sets up request message.

Step 704a: the core net gateway sends session to S-GW and sets up response.

Step 705:S-GW sends session to Mobility Management Entity and sets up response.

Step 706: Mobility Management Entity initiates to carry the request of foundation to the wireless side network element, comprises PDN connection request message.

Step 707: carry out RRC and connect layoutprocedure.

Step 708: the wireless side network element is replied Mobility Management Entity and is carried the foundation response.

Step 709; User terminal sends direct-sending message to the wireless side network element, comprises the PDN connection setup complete message.

Step 710: the wireless side network element sends the PDN connection setup complete message to Mobility Management Entity.

Step 711: Mobility Management Entity sends the bearing modification request to S-GW.

Step 712: if in step 702, what the Mobility Management Entity decision was set up is that SIPTO connects, and S-GW sends bearing modification message to local gateway.

Step 712a: local gateway is responded S-GW bearing modification response message.

Step 713: if in step 702, what the Mobility Management Entity decision was set up is that core net connects, and S-GW sends the bearing modification request message to the core net gateway.

Step 713a: the core net gateway is responded S-GW bearing modification response message.

Step 714:S-GW responds Mobility Management Entity bearing modification response message, and whole PDN connection procedure is accomplished.

Embodiment 3

After Fig. 8 accomplishes for the embodiment of the invention 3 users adhere to and sets up the SIPTO connection; Network side is with this SIPTO connection type informing user terminal; User intention connects for refusal SIPTO; Then the user refuses the schematic flow sheet (based on system shown in Figure 1 framework, data flow shown in Figure 5) that SIPTO connects, and as shown in Figure 8, the present embodiment method specifically may further comprise the steps:

Step 801: user terminal adhere to accomplish set up that SIPTO connects or the user PDN connect set up set up SIPTO in the process and connect after; Network side is notified the user with this SIPTO connection type; User intention connects for refusal SIPTO, initiatively initiates PDN and connects the request of release, carries user intention.User intention is that refusal SIPTO connects here.

The user initiatively initiates PDN and connects when discharging request, must be in connected state, if the user is in Idle state, then must at first initiate the service request flow process.

Step 802: Mobility Management Entity is preserved user intention a period of time that step 801 is carried, and is used for setting up core net to user terminal next time and connects.Mobility Management Entity also triggers PDN connection release.

Step 803: Mobility Management Entity is sent out the deletion conversation request message to S-GW, request deletion carrying each other.

Step 804:S-GW sends out the deletion conversation request message to local gateway.

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

Step 806:S-GW sends session deletion response to Mobility Management Entity.

Step 807: initiate to carry the request of release to the wireless side network element after the carrying that the Mobility Management Entity deletion is correlated with it, release wireless side bearing resource.

Step 808: the wireless side network element connects reconfiguration course with carrying out RRC between the user terminal.

Step 809: the wireless side network element is replied Mobility Management Entity and is carried the release response.

Step 810: user terminal sends direct-sending message to the wireless side network element, comprises the carrying Release complete.

Step 811: the wireless side network element sends to Mobility Management Entity and carries Release complete, and the PDN release flow that the user initiatively initiates finishes.

If it is that user intention is that refusal SIPTO connects that the user discharges the cause value of local PDN connection, and wants to be established to the connection of core net, after then this release flow finishes, need be initiated to the PDN connection building process of core net again.

Embodiment 4

Fig. 9 is that the embodiment of the invention 4 users set up in the process in the PDN connection; Network side is set up SIPTO to the user and is connected; And this PDN connection type notified to the user, after the user receives the PDN connection type, according to oneself wish decision refusal or accept the schematic flow sheet (based on system shown in Figure 1 framework, data flow shown in Figure 5) that SIPTO connects; As shown in Figure 9, the present embodiment method specifically may further comprise the steps:

Step 901: the user terminal that is in connected state is initiated the PDN connection request.

Step 902: Mobility Management Entity is confirmed to set up SIPTO according to network capabilities, subscription data or local policy etc. and is connected, and sends session to S-GW and set up request message.

Step 903:S-GW sends session to local gateway and sets up request message.

Step 904: local gateway sends session to S-GW and sets up response.

Step 905:S-GW sends session to Mobility Management Entity and sets up response.

Step 906: Mobility Management Entity initiates to carry the request of foundation to the wireless side network element, comprises PDN connection request message, and carries the PDN connection type, and this PDN connection type is designated as SIPTO and connects.

Step 907: carry out RRC and connect layoutprocedure.

Step 908: the wireless side network element is replied Mobility Management Entity and is carried the foundation response.

Step 909: user terminal is accepted this SIPTO according to the wish decision of oneself and is connected, and then sends direct-sending message to the wireless side network element, and this SIPTO connection is set up, and user intention is to accept SIPTO to connect here; User terminal connects according to this SIPTO of wish refusal of oneself, then sends direct-sending message to the wireless side network element, and direct-sending message comprises user intention.User intention is that refusal SIPTO connects here.

Step 910: the wireless side network element sends the PDN connection setup complete message to Mobility Management Entity, and SIPTO connects if user intention is refusal, and then this completion message comprises user intention.

Step 911: after Mobility Management Entity is received the PDN connection setup complete message of wireless side transmission; If finding user intention is that refusal SIPTO connects; Then do not allow SIPTO this ground mark user; And preserve user intention a period of time when being used for setting up PDN next time and connecting to user terminal, no longer set up SIPTO and connect but be established to core net and connect.

Step 912: Mobility Management Entity discharges previous this locality of setting up and connects, and in order to guarantee the connectivity of customer service, the PDN that request rebulids core net connects.

Embodiment 5

Figure 10 is that the embodiment of the invention 5 users are in attaching process; Network side is set up SIPTO to the user and is connected; And this PDN connection type notified to the user; The user refuses according to the wish of oneself or accepts the schematic flow sheet (based on system shown in Figure 1 framework, data flow shown in Figure 5) that SIPTO connects, and shown in figure 10, the present embodiment method specifically may further comprise the steps:

Step 1001: user terminal need be set up RRC and connect the carrying as signaling message or business datum before communicating.

Step 1002: user terminal sends initialization NAS message, the beginning attachment flow.

Step 1003: the wireless side network element is issued Mobility Management Entity with initial user message, and transmits NAS message to Mobility Management Entity.If there is femto gateway, then is transmitted to femto gateway earlier, and then message issued Mobility Management Entity by femto gateway.Mobility Management Entity is MME in the LTE system.

Step 1004: Mobility Management Entity is opened authentication and safe procedures, and user terminal is verified.

Step 1005: Mobility Management Entity request HSS carries out the position to be upgraded.

Step 1006:HSS responds the position to Mobility Management Entity and upgrades response.

Step 1007: Mobility Management Entity is confirmed to set up SIPTO according to network capabilities or local policy etc. and is connected, and selects the L-PGW that is positioned at wireless side network element/femto gateway to be user's service, and sends session to S-GW and set up request.

Step 1008:S-GW sends session to local gateway and sets up request message.

Step 1009: local gateway sends session to S-GW and sets up response.

Step 1010:S-GW sends session to Mobility Management Entity and sets up response.

Step 1011: Mobility Management Entity is initiated initial context to the wireless side network element and is set up request.This request message comprises to adhere to accepts message, and carries the PDN connection type, and this PDN connection type indication SIPTO connects.

Step 1012: carry out RRC and connect layoutprocedure.

Step 1013: the wireless side network element is replied the Mobility Management Entity initial context and is set up response.

Step 1014: user terminal receives that the PDN connection type is after SIPTO connects, and according to the wish decision refusal SIPTO connection of oneself, sends direct-sending message to the wireless side network element, comprise and adhere to completion message, and user intention, user intention is that refusal SIPTO connects here; User terminal receives that the PDN connection type is after SIPTO connects, and accepts SIPTO according to the wish decision of oneself and connects, and then sends direct-sending message to the wireless side network element, comprise and adhere to completion message, and user intention, user intention is to accept SIPTO to connect here;

Step 1015: the wireless side network element sends to Mobility Management Entity and adheres to completion message, carries user intention.

Step 1016: after Mobility Management Entity receives that the context foundation response of step 1013 is accomplished message with adhering to of step 1015; SIPTO connects then the recording user wish if user intention is refusal; And preserve user intention (refusal SIPTO connects) a period of time, being used for setting up core net to user terminal next time and connecting, Mobility Management Entity discharges previous this locality of setting up and connects; And asking user terminal to adhere to again, the PDN that when adhering to next time, is established to core net connects.

Embodiment 6

SIPTO connected or once-requested was set up the SIPTO connection if user's source network side before the position change flow process was set up, and then the former Mobility Management Entity of source network side can be preserved user SIPTO wish.Follow-up when the tracing section updating of across a network side takes place the user, can send the user SIPTO wish of preserving to target mobility management entity by former Mobility Management Entity.

Figure 11 is the schematic flow sheet that the tracing section updating flow process Central Plains Mobility Management Entity of the embodiment of the invention 6 user's across a network sides sends the user SIPTO wish of preserving to target mobility management entity.Shown in figure 11, this flow process specifically may further comprise the steps:

Step 1101: the terminal is sent the tracing section updating request message through Target Wireless side network element to target mobility management entity, and this message can be carried and activated sign;

Step 1102: target mobility management entity is sent context request message to former Mobility Management Entity;

Step 1103: former Mobility Management Entity sends context response information to target mobility management entity; This message is carried user SIPTO wish; After target mobility management entity is received user SIPTO wish; It is preserved, be used in follow-up gateway reorientation flow process, with reference to user SIPTO wish.

Step 1104: alternatively, terminal, target mobility management entity, Authentication Authorization server are carried out authorizing procedure;

Step 1105: target mobility management entity is sent context acknowledgement message to former Mobility Management Entity;

Step 1106: target mobility management entity is sent the request of carrying of revising to gateway, the operation of request bearing modification;

Step 1107: gateway can send the request of carrying of revising to local gateway;

Step 1108: local gateway can be responded gateway and revise the carrying response;

Step 1109: gateway returns to revise to target mobility management entity and carries response;

Step 1110: executing location new technological process more between target mobility management entity and the Authentication Authorization server;

Step 1111: executing location cancellation flow process between Authentication Authorization server and the former Mobility Management Entity;

Step 1112: target mobility management entity is sent tracing section updating through Target Wireless side network element to the user and is accepted message.

Need to prove that after step 1110, target mobility management entity can be done the gateway reorientation, target mobility management entity is when doing the gateway reorientation, with reference to user SIPTO wish.

In the present embodiment, the user can decide based on the wish of oneself and accept or refusal SIPTO connection, and user SIPTO wish also can be different and different with APN, positional information or other information.

Embodiment 7

In the present embodiment; The user never set up the SIPTO connection and also asked to set up the SIPTO connection before the position change flow process; The former Mobility Management Entity that is the source network side does not have user SIPTO wish; The user sets up in the tracing section updating process of radio bearer at needs, and the objective network side is initiatively inquired user SIPTO wish.Figure 12 be the embodiment of the invention 7 users in the tracing section updating process, target mobility management entity is initiatively inquired the schematic flow sheet of user SIPTO wish, and is shown in figure 12, this flow process specifically may further comprise the steps:

Step 1201: the terminal is sent the tracing section updating request message through Target Wireless side network element to target mobility management entity, and this message is carried and activated sign;

Step 1202: target mobility management entity is sent context request message to former Mobility Management Entity;

Step 1203: former Mobility Management Entity sends context response information to target mobility management entity, and in the present embodiment, this message is not carried user SIPTO wish;

Step 1204: alternatively, terminal, target mobility management entity, Authentication Authorization server are carried out verification process;

Step 1205: target mobility management entity is sent context acknowledgement message to former Mobility Management Entity;

Step 1206: target mobility management entity is operated to gateway request bearing modification;

Step 1207: gateway can send the request of carrying of revising to local gateway;

Step 1208: local gateway can be responded gateway and revise the carrying response;

Step 1209: gateway is responded target mobility management entity and is revised the carrying response;

Step 1210: executing location new technological process more between target mobility management entity and the Authentication Authorization server;

Need to prove that after the step 1210, target mobility management entity can be done the gateway reorientation and select.

Step 1211: executing location cancellation flow process between Authentication Authorization server and the former Mobility Management Entity;

Step 1212, target mobility management entity send to Target Wireless side network element that initial context is set up request message and tracing section updating is accepted message, carry the PDN connection type;

Need to prove; When if step 1210 back target mobility management entity is done the gateway reorientation; Find that current gateway is suitable for SIPTO and connects, then target mobility management entity is accepted to carry the PDN connection type in the message at tracking area, and PDN connection type indication SIPTO.

Step 1213: Target Wireless side network element is carried out radio bearer and is set up process;

Step 1214: Target Wireless side network element is responded the Mobility Management Entity initial context and is set up completion/radio bearer foundation completion message, carries user SIPTO wish;

Need to prove, after the user receives SIPTO PDN connection type, be refusal or accepting this SIPTO PDN connects according to oneself wish decision, and bring the objective network side with oneself SIPTO wish.

After the objective network side was received user SIPTO wish, the core net connection of foundation was kept or is discharged in decision according to user SIPTO wish.

If the tracing section updating process need not set up radio bearer; Former Mobility Management Entity and target mobility management entity are not known user SIPTO wish simultaneously; And the objective network side is when doing the gateway reorientation; Find that current gateway is suitable for SIPTO and connects; Then the objective network side can be after the tracing section updating flow process finishes, and through newly-increased message or adopt and carry SIPTO PDN connection type with the similar message of embodiment before and give the user, the user still refuses this PDN connection according to own wish decision acceptance again.The objective network side can not inquired user SIPTO wish immediately yet after the tracing section updating flow process finishes; But when waiting user to get into connected state next time, the objective network side initiatively adopts to catch up with when confirming to set up SIPTO and connecting again and states similar message or inquire user SIPTO wish through newly-increased message.

Embodiment 8

In the present embodiment; The user before switching flow, once set up the SIPTO connection or once-requested was set up the SIPTO connection, and the former Mobility Management Entity in the source network side sends the user SIPTO wish of preserving to target mobility management entity in handoff procedure.Figure 13 sends the user SIPTO wish of preserving the schematic flow sheet of target mobility management entity to for the embodiment of the invention 8 by the former Mobility Management Entity in the source network side in switching, shown in figure 13, this flow process specifically may further comprise the steps:

Step 1301: former wireless side network element judgement needs to initiate S1 and switches;

Step 1302: former wireless side network element sends handoff request to former Mobility Management Entity;

Step 1303: former Mobility Management Entity changes request message before target mobility management entity is sent reorientation, this message is carried user SIPTO wish;

If former Mobility Management Entity has user's SIPTO wish, then former Mobility Management Entity can change in the request message before the reorientation in this step or before the reorientation of back, bring target mobility management entity with user SIPTO wish in the commentaries on classics completion acknowledge message.Target mobility management entity is preserved user SIPTO wish, is used at follow-up gateway repositioning process with reference to user SIPTO wish.

Step 1304: target mobility management entity can be initiated the session that local IP connects to gateway and set up flow process;

Step 1305: target mobility management entity request target wireless side network element is carried out and is switched;

Step 1306: Target Wireless side network element is responded switching request acknowledgement message to target mobility management entity;

Step 1307: target mobility management entity is changeed response message before former Mobility Management Entity sends reorientation.

Step 1308: former Mobility Management Entity sends switching command to former wireless side network element;

Step 1309: former wireless side network element sends switching command to the terminal;

Step 1310: switch acknowledgment message is initiated to Target Wireless side network element in the terminal;

Step 1311: Target Wireless side network element notification target Mobility Management Entity switches;

Step 1312: Target Wireless side network element changes before former Mobility Management Entity sends reorientation accomplishes notification message;

Step 1313: former wireless side network element changes before target mobility management entity is replied reorientation accomplishes acknowledge message;

Step 1314: carry out the subsequent process of switching flow, subsequent process and prior art are similar, do not do here and give unnecessary details.

If former Mobility Management Entity and target mobility management entity were not all known user SIPTO wish when the user initiated to switch; Then can be in the tracing section updating process after the across a network side is switched, the mode of in the tracing section updating process, obtaining user SIPTO wish that embodiment describes before adopting is obtained user SIPTO wish.

Need to prove; The message that is used for carrying user SIPTO wish is not limited to the message that provides in the embodiment of the invention; User SIPTO wish also can through with present embodiment in message have the message of similar function to carry, perhaps through the expansion new information realize.

Need to prove that the local gateway described in the present invention can be L-SGW and L-PGW, also can be independent L-PGW, also can be the data distribution functional entity; The wireless side network element of SIPTO can be identical with the local gateway address; It can be the triage operator or the specific IP data distribution of local IP access subscriber's local network, local IP access company local network, local IP access the Internet, Internet service that SIPTO connects.

Need to prove that in order to simplify description, above embodiment is that example is explained the way to manage that SIPTO connects with the situation of Fig. 1 only.Set up separately at Fig. 1 local gateway and wireless side network element, under the situation of Fig. 2, Fig. 3 system; No matter Fig. 4 or SIPTO connected mode shown in Figure 5, no matter UTRAN or E-UTRAN system; The flow process that user's perception SIPTO connects is similar to the aforementioned embodiment; Can not impact, so repeat no more setting forth the present invention.

Obviously, it is apparent to those skilled in the art that above-mentioned each module of the present invention or each step can realize with the general calculation device; They can concentrate on the single calculation element; Perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element; Thereby; Can they be stored in the storage device and carry out, perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize by calculation element.Like this, the present invention is not restricted to any specific hardware and software combination.

The above is merely preferred embodiment of the present invention, is not to be used to limit protection scope of the present invention.

Claims

1. a user participates in the method that this accessing connects foundation, it is characterized in that this method comprises: the message of carrying user intention that network side sends according to the user is set up or refusal PDN connects.

2. method according to claim 1 is characterized in that, said messages sent by users is that request message is set up in the PDN connection.

3. method according to claim 1 is characterized in that, the user sends and carries before the message of user intention, and this method also comprises: when network side is confirmed for the PDN connection type that the user sets up to be the SIPTO connection, obtain user intention,

Said messages sent by users is a PDN connection establishment response message.

4. method according to claim 2 is characterized in that, request message foundation is set up in the PDN connection of carrying user intention that said network side sends according to the user or refusal PDN is connected to:

5. method according to claim 3 is characterized in that, the PDN connection establishment response message of carrying user intention that said network side sends according to the user is set up or refusal PDN is connected to:

6. according to each described method of claim 1 to 5, it is characterized in that, said PDN connection type comprise following one or more: core net connects, SIPTO connects.

7. according to claim 3 or 5 described methods, it is characterized in that when said user's refusal was set up the SIPTO connection, this method also comprised: the user notification network side carries out PDN and connects releasing operation, perhaps, the user carries parameter and initiatively initiates PDN connection releasing operation.

8. a user participates in the system that this accessing connects foundation, it is characterized in that this system comprises network side and user side; Wherein,

9. system according to claim 8 is characterized in that, the message that said user side sends is that request message is set up in the PDN connection.

10. system according to claim 8 is characterized in that,

11. system according to claim 9 is characterized in that, request message foundation is set up in the PDN connection of carrying user intention that said network side sends according to the user or refusal PDN is connected to:

12. system according to claim 10 is characterized in that, the PDN connection establishment response message of carrying user intention that said network side sends according to the user is set up or refusal PDN is connected to:

13. according to claim 10 or 12 described systems, it is characterized in that,

14. a user participates in this accessing and connects the method for setting up, and it is characterized in that this method comprises:

15. method according to claim 14; It is characterized in that; This method specifically comprises: in the tracing section updating process; Target mobility management entity is obtained said user's user intention to the former Mobility Management Entity of source network side, sets up according to said user intention from former Mobility Management Entity afterwards or the PDN that refuses said user connects.

16. method according to claim 15 is characterized in that, said former Mobility Management Entity carries user intention through context response information.

17. method according to claim 14; It is characterized in that; This method specifically comprises: in handoff procedure; The former Mobility Management Entity of source network side initiatively sends said user's user intention to target mobility management entity, and afterwards, target mobility management entity sets up or refuse said user's PDN connection according to said user intention from former Mobility Management Entity.

18. method according to claim 17 is characterized in that, said former Mobility Management Entity changes before through reorientation to change before request message or the reorientation to be accomplished acknowledge message and sends user intention to target mobility management entity.

19., it is characterized in that the message that said target mobility management entity is sent according to former Mobility Management Entity is set up or refusal PDN is connected to according to claim 16 or 18 described methods:

20. according to each described method of claim 14 to 18, it is characterized in that, said PDN connection type comprise following one or more: core net connects, SIPTO connects.

21. a user participates in this accessing and connects the system that sets up; It is characterized in that; This system comprises target mobility management entity and former Mobility Management Entity; Wherein, said target mobility management entity is used under the situation that user's occurrence positions changes, according to the PDN connection of setting up or refuse said user from the user intention of former Mobility Management Entity.

22. system according to claim 21 is characterized in that,

23. system according to claim 22 is characterized in that,

24. system according to claim 21 is characterized in that,

25. system according to claim 24 is characterized in that,