WO2012126298A1 - 本地ip访问连接的处理方法及装置 - Google Patents

本地ip访问连接的处理方法及装置 Download PDF

Info

Publication number
WO2012126298A1
WO2012126298A1 PCT/CN2012/071176 CN2012071176W WO2012126298A1 WO 2012126298 A1 WO2012126298 A1 WO 2012126298A1 CN 2012071176 W CN2012071176 W CN 2012071176W WO 2012126298 A1 WO2012126298 A1 WO 2012126298A1
Authority
WO
WIPO (PCT)
Prior art keywords
local
management entity
mobility management
gateway
mobility
Prior art date
Application number
PCT/CN2012/071176
Other languages
English (en)
French (fr)
Inventor
周娜
王静
霍玉臻
梁爽
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012126298A1 publication Critical patent/WO2012126298A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • H04W8/082Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents

Definitions

  • the present invention relates to the field of communications, and in particular to a method and apparatus for processing a local IP access connection.
  • 3GPP 3rd Generation Partnership Project
  • EPS evolved Evolved Packet System
  • E-UTRAN Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • AAA 3GPP Authenticated Authorization and Accounting
  • Policy and Charging Rules Function Policy and Charging Rules Function
  • PCRF Policy and Charging Rules Function
  • FIG. 1 is a schematic diagram of an EPS system architecture according to the related art
  • FIG. 1a is another schematic diagram of an EPS system architecture according to the related art
  • FIG. 1b is still another schematic diagram of an EPS system architecture according to the related art, mobility management.
  • the entity is responsible for the control planes such as mobility management, non-access stratum signaling processing and user mobility management context management
  • S-GW is the access gateway device connected to E-UTRAN, in E-UTRAN and P- The GW forwards data and is responsible for buffering the paging waiting data.
  • the P-GW is the border gateway of the EPS and Packet Data Network (PDN) network, which is responsible for PDN access and EPS and PDN.
  • PDN Packet Data Network
  • S-GW and P-GW are both core network gateways.
  • mobile communication systems including home base station systems
  • local IP access functions can be achieved under the condition that the wireless side network element has local IP access capability and the user subscribes to allow local IP access.
  • the local access of the terminal to other IP devices or the Internet of the home network.
  • the implementation of the local IP access can adopt multiple connection establishment modes: the core network access and the local IP access function can be realized at the same time by establishing a connection. In this case, it is not necessary to add a local gateway function on the wireless side network element or the home base station gateway ( As shown in Figure lb); local gateways can also be provided to provide strong support for local IP access technologies.
  • Local gateways serve as gateways for local access to external networks (such as the Internet), providing address allocation, accounting, packet filtering, and policy. Control, data offloading function, Radio Access Network Application Part (NAS/S1-AP/RANAP for short) / General Tunneling (General Tunneling) Protocol (GTP) / Proxy Mobile IP (PMIP) / Mobile IP (Mobile IP, MIP for short) Message Parsing, Network Address Translation (NAT), Local IP Access Policy Routing and execution functions.
  • the local gateway can be combined/distributed with the wireless side network element (as shown in Figure 1).
  • 2 is a schematic diagram of a local IP access data flow according to the related art
  • FIG. 2a is another schematic diagram of a local IP access data flow according to the related art
  • Step S301 A user needs to establish a wireless before performing communication.
  • a Resource Control (Radio Resource Control, abbreviated as RRC) connection is used as a bearer for signaling messages or service data.
  • RRC Radio Resource Control
  • Step S302 the user sends an initial non-access stratum (Non-Access-Stratum, NAS for short) message to perform an attach operation.
  • Step S303 the radio side network element sends the initial user message to the mobility management entity, and forwards the NAS message to the mobility management entity.
  • Step S304 the mobility management entity starts the authentication and the security process, and performs verification on the user.
  • Step S305 the mobility management entity requests the HSS to perform location update.
  • Step S306 the HSS responds to the mobility management entity with a location update response.
  • Step S307 the mobility management entity sends a session establishment request to the S-GW.
  • the P-GW replies to the S-GW with a session establishment response.
  • Step S309 the S-GW sends a session establishment response to the mobility management entity.
  • Step S310 the mobility management entity initiates an initial context setup request to the radio side network element.
  • Step S311 performing an RRC connection configuration process.
  • Step S312 the radio side network element replies to the mobility management entity initial context establishment response.
  • Step S313 The terminal sends a direct transmission message to the radio side network element, including attach completion information.
  • Step S314 the radio side network element sends an attach complete message to the mobility management entity.
  • Step S315 the mobility management entity requests the S-GW to update the bearer.
  • Step S316 the S-GW sends a bearer update request to the P-GW.
  • FIG. 4 is a flow chart of the interaction of the service request when the terminal is changed from the idle state to the connected state according to the related art according to the related art. As shown in FIG. 4, the following steps S401 to S412 are included. Step S401, the terminal has a local IP access connection after accessing the wireless communication system, and then the terminal enters an idle state.
  • Step S402 The terminal sends a service request message to the mobility management entity via the radio side network element.
  • a NAS (Non-Access-Stratum) authentication process is performed, and the step is optional.
  • Step S404 the mobility management entity sends an initial context setup request message to the radio side network element.
  • Step S405 The radio side network element performs a radio bearer setup process.
  • Step S406 the radio side network element responds to the mobility management entity initial context setup complete message.
  • Step S407 the mobility management entity requests the serving gateway to perform bearer modification.
  • the serving gateway sends a bearer modification request message to the local gateway.
  • Step S409 the local gateway responds to the bearer modification response message to the serving gateway.
  • Step S410 The serving gateway sends a modify bearer response message to the mobility management entity.
  • Step S411 a tunnel is established between the wireless side network element and the local gateway.
  • the wireless side network element requests tunnel establishment from the local gateway.
  • Step S412, the local gateway responds to the radio side network element tunnel establishment response.
  • 4a is an interaction flowchart of a terminal performing a location update process on the basis of the system of FIG. 1 according to the related art. As shown in FIG. 4a, the following steps S4a01 to S4al8 are included.
  • Step S4a01 The terminal sends a tracking area update request message to the mobility management entity via the target radio side network element, and carries the activation identifier.
  • Step S4a02 the target mobility management entity sends a context request message to the original mobility management entity.
  • Step S4a03 a context response message sent by the original mobility management entity to the target mobility management entity.
  • Step S4a04 optionally, the terminal, the mobility management entity, and the authentication authorization server perform an authentication process.
  • Step S4a05 the target mobility management entity sends a context confirmation message to the original mobility management entity.
  • Step S4a06 the target mobility management entity initiates a create session request operation to the target service gateway.
  • the target serving gateway requests the bearer modification from the local gateway.
  • step S4a08 the local gateway returns the target service gateway bearer modification response.
  • step S4a09 the target service gateway replies to the target mobility management entity to create a session response.
  • step S4al0 a location update process is performed between the target mobility management entity and the authentication authorization server.
  • step S4all the location cancellation process is performed between the authentication authorization server and the original mobility management entity.
  • the target mobility management entity sends an initial context setup request message to the target radio side network element.
  • step S4al3 the target radio side network element performs a radio bearer setup process.
  • Step S4al4 the target radio side network element responds to the mobility management entity initial context setup complete/radio bearer setup complete message.
  • step S4al5 the mobility management entity requests the target serving gateway to perform bearer modification to activate/establish the core network connection of the terminal.
  • step S4al6 the target serving gateway sends a bearer modification response message to the target mobility management entity.
  • the target service gateway performs bearer modification with the local gateway.
  • step S4al7 a tunnel is established between the wireless side network element and the local gateway.
  • the wireless side network element requests tunnel establishment from the local gateway.
  • step S4al8 the local gateway responds to the radio side network element tunnel establishment response.
  • FIG. 4b is an interaction flowchart of the handover process performed by the terminal on the basis of the system of FIG. 1 according to the related art. As shown in FIG. 4b, the following steps S4b01 to S4b20 are included.
  • step S4b01 the radio side network element determines that the S1 handover needs to be initiated.
  • Step S4b02 the original radio side network element sends a handover request to the original mobility management entity.
  • Step S4b03 the relocation forward request message sent by the original mobility management entity to the target mobility management entity.
  • the target mobility management entity may initiate a session establishment procedure of the local IP access connection to the target serving gateway.
  • Step S4b05 the target mobility management entity requests the target radio side network element to perform handover.
  • Step S4b06 the target radio side network element responds to the target mobility management entity with a handover request acknowledgement message.
  • Step S4b07 the target mobility management entity sends a relocation forward response message to the original mobility management entity.
  • step S4b08 the original mobility management entity sends a handover command to the original radio side network element.
  • step S4b09 the original radio side network element terminal sends handover execution.
  • step S4M0 the terminal notifies the target wireless side network element of the handover confirmation.
  • step S4b11 the target radio side network element notifies the target mobility management entity to perform handover.
  • step S4M2 the target mobility management entity sends a relocation forward completion notification message to the original mobility management entity.
  • step S4M3 the original mobility management entity replies with a confirmation response.
  • step S4M4 the target mobility management entity requests the bearer modification from the target service gateway.
  • step S4M5 and step S4bl6, a bearer modification operation is performed between the target serving gateway and the local gateway.
  • Step S4M7 The target serving gateway replies to the target mobility management entity with a bearer modification response message.
  • step S4al8 a tunnel is established between the wireless side network element and the local gateway.
  • the wireless side network element requests tunnel establishment from the local gateway.
  • step S4al9 the local gateway responds to the radio side network element tunnel establishment response.
  • step S4b20 the normal switching process is continued.
  • IP offloading the terminal service continuity is allowed to be maintained within a certain range. After the terminal moves, the mobility management entity will judge whether the IP offload connection needs to be maintained or released by moving decision information (for example, information such as a closed user group).
  • a processing method of a local IP access connection includes: in a process of establishing a local IP access connection, the mobility management entity receives the mobile decision information; and the mobility management entity determines according to the mobile decision information.
  • the mobility management entity receives the mobile decision information, including: the mobility management entity receives the mobile decision information sent by the radio side network element, where the radio side network element includes one of the following: a base station, a home base station, a home base station gateway, and a radio network controller. , data offloading functional entities.
  • the mobility management entity receives the mobility decision information, including: the mobility management entity receives the mobile decision information sent by the local gateway, where the local gateway is a local access gateway and/or a local service gateway, and the local access gateway includes one of the following: -PGW, L-GGSN L-GW, local service gateway is one of the following: L-SGW L-SGSN L-GWo
  • the mobility management entity receives the mobility decision information sent by the local gateway, and the following: The mobility management entity receives the mobile decision information sent by the local gateway via the wireless side network element, where the wireless side network element includes one of the following: a base station, a home a base station, a home base station gateway, a radio network controller, and a data offloading function entity; the mobility management entity receives the mobile decision information sent by the local gateway via the serving gateway, where the serving gateway is a local service gateway and/or a core network service gateway, and is locally
  • the serving gateway is one of the following: L-SGW, L-SGSN L-GW, and the
  • the receiving, by the mobility management entity, the mobile decision information includes: the mobility management entity receives the mobile decision information sent by the DNS server or the network management system.
  • the receiving, by the mobility management entity, the mobile decision information includes: the mobility management entity receives the mobile decision information sent by the authentication authorization server.
  • the local IP access connection includes one of the following: local IP access to the user's local network, local IP access to the company's local network, local IP access to the Internet, Internet traffic shunting, and specific IP data offloading.
  • the mobility management entity includes one of the following: a mobility management unit, a mobile switching center, a serving general packet radio service support node, and a home base station gateway.
  • the mobile decision information includes at least one of the following: a CSG list, a CSG group, and a CSG name.
  • the mobile decision information also includes at least one of the following: an LHN name, an LHN identifier.
  • a processing apparatus for a local IP access connection is provided.
  • the processing device of the local IP access connection according to the present invention may be applied to a mobility management entity, including a receiving module, configured to receive mobile decision information in the process of establishing a local IP access connection; and a determining module configured to be based on the mobile decision information , to determine whether the local IP access connection supports mobility.
  • the mobile decision information is externally configured and received by the mobility management entity, thereby implementing flexible processing performance of the IP offload system and improving system operability.
  • BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  • FIG. 1b is still another schematic diagram of an EPS system architecture according to the related art;
  • FIG. 2a is another schematic diagram of a local IP access data stream according to the related art;
  • FIG. 2b is another local IP access data stream according to the related art.
  • FIG. 3 is an interaction flowchart of a user performing PDN connection establishment on the basis of the system of FIG. 1 according to the related art;
  • FIG. 4 is a diagram of a terminal provided by the idle state according to the system of FIG. 1 according to the related art.
  • FIG. 4a is an interaction flowchart of a location update process provided by a terminal according to the related art according to the related art;
  • FIG. 4b is a system in FIG. 1 according to the related art;
  • FIG. 5 is a flowchart of a method for processing a local IP access connection according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a method for processing a local IP access connection according to an embodiment of the present invention
  • FIG. 6a is an interaction flowchart of a terminal performing a handover process on the basis of the system of FIG. 1 according to an embodiment of the present invention.
  • FIG. 7 is an interaction flowchart 2 of a user initial access for connection establishment based on the system of FIG. 1 according to an embodiment of the present invention
  • FIG. 8 is a schematic diagram of a user initializing on the basis of the system of FIG. 1 according to an embodiment of the present invention; Accessing the interaction flow chart 3 for establishing the connection;
  • FIG. 8 is an interaction flowchart 2 of a user initial access for connection establishment based on the system of FIG. 1 according to an embodiment of the present invention
  • FIG. 9 is an interaction flowchart 4 of the user initial access for establishing the connection on the basis of the system of FIG. 1 according to an embodiment of the present invention
  • 10 is an interaction flowchart 5 of a user initial access for connection establishment based on the system of FIG. 1 according to an embodiment of the present invention
  • FIG. 11 is a diagram of a terminal switching according to the system of FIG. 1 according to an embodiment of the present invention
  • FIG. 11a is an interaction flow chart 2 of a terminal performing a handover process on the basis of the system of FIG. 1 according to an embodiment of the present invention
  • FIG. 12 is a system diagram of FIG. 1 according to an embodiment of the present invention
  • the interaction flow chart of the terminal performing the handover process is shown in FIG. 13 .
  • FIG. 13 The interaction flow chart of the terminal performing the handover process is shown in FIG. 13 .
  • FIG. 13 is a flowchart showing a service request process when the terminal is changed from the idle state to the connected state, and the mobility management entity moves according to the system of FIG. 1 according to an embodiment of the present invention.
  • FIG. 14 is an interaction flowchart 1 of a terminal performing location update process on the basis of the system of FIG. 1 according to an embodiment of the present invention;
  • FIG. 15 is a system in FIG. 1 according to an embodiment of the present invention.
  • FIG. 16 is a structural block of a processing device for a local IP access connection according to an embodiment of the present invention. .
  • FIG. 5 is a flowchart of a method for processing a local IP access connection according to an embodiment of the present invention. As shown in FIG. 5, the following steps S502 to S504 are included. Step S502, in the process of establishing a local IP access connection, the mobility management entity receives the mobile decision information. Step S504, the mobility management entity determines, according to the mobility decision information, whether the local IP access connection supports mobility.
  • the mobile decision information is configured on the mobility management entity, which is not flexible enough and the network management operation is complicated.
  • the mobile decision information is externally configured and received by the mobility management entity, thereby implementing flexible processing performance of the IP offload system and improving system operability.
  • the mobility management entity receives the mobility decision information, including: the mobility management entity receives the mobile decision information sent by the wireless side network element, where the wireless side network element includes one of the following: a base station, a home base station, a home base station gateway, and a wireless Network controller, data offloading function entity.
  • the mobility management entity receives the mobility decision information, including: the mobility management entity receives the mobile decision information sent by the local gateway, where the local gateway is a local access gateway and/or a local service gateway, and the local access gateway includes the following One: Local PDN Gateway (L-PGW for short), Local Gateway General Packet Radio Service Supporting Node (L-GGSN for short), Local Gateway (Local Gateway,
  • the local service gateway is one of the following: L-SGW, Local Serving General packet radio service support node (L-SGSN for short) L-GW.
  • the mobility management entity receives the mobility decision information sent by the local gateway, where the mobility management entity receives the mobile decision information sent by the local gateway via the wireless side network element, where the wireless side network element includes one of the following: a base station, a home base station, a home base station gateway, a radio network controller, and a data offloading function entity; the mobility management entity receives mobile decision information sent by the local gateway via the serving gateway, where the serving gateway is a local serving gateway and/or a core network serving gateway
  • the local service gateway is one of the following: L-SGW, L-SGSN, L-GW, and the core network service gateway includes one of the following: S-GW, SGSN.
  • the receiving, by the mobility management entity, the mobile decision information comprises: the mobility management entity receiving the mobile decision information sent by the DNS server or the network management system.
  • the receiving, by the mobility management entity, the mobile decision information comprises: the mobility management entity receiving the mobile decision information sent by the authentication authorization server.
  • the local IP access connection comprises one of the following: local IP access to the user's local network, local IP access to the company's local network, local IP access to the Internet, offloading of Internet services, and specific IP data offloading.
  • the mobility management entity comprises one of the following: a mobility management unit, a mobile switching center, a serving general packet radio service support node, and a home base station gateway.
  • the mobile decision information includes at least one of the following: a closed subscriber group (CSG) list, a CSG group, a CSG name, and a local home base station network (Local H(e)NB Network, referred to as LHN) name, LHN logo.
  • CSG closed subscriber group
  • LHN local home base station network
  • the present invention has been made in view of the problem of how to obtain mobile decision information for a local IP access connection in the related art.
  • the main object of the present invention is to provide a method for a mobility management entity to acquire mobile decision information, so as to solve at least the above problems.
  • the implementation process of the embodiment of the present invention will be described in detail below with reference to examples.
  • the following embodiment diagram describes an application scenario of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) system based on an evolved universal mobile communication system.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • 6 to 6a are embodiments in which decision information is transmitted by the radio side network element to the mobility management entity.
  • 7 is an embodiment of a decision by a local gateway to transmit decision information to a mobility management entity via a wireless side network element.
  • 8 is an embodiment of a decision by a local gateway to transmit decision information to a mobility management entity via a serving gateway.
  • 9 is an embodiment of an authentication authorization server transmitting decision information to a mobility management entity.
  • FIG. 10 is an embodiment of transmitting decision information to a mobility management entity by a DNS server or a network management system. 11 to FIG.
  • FIG. 15 are diagrams showing an embodiment in which the mobility management entity performs mobility determination during the movement after obtaining the decision information based on the various methods described above.
  • FIG. 6 is a flow chart 1 of an interaction of a user initial access for connection establishment based on the system of FIG. 1 according to an embodiment of the present invention.
  • the decision information is sent by the wireless side network element to the mobility management entity.
  • Step S601 The user needs to establish an RRC (Radio Resource Control) connection as a signaling message or a bearer of service data before performing communication.
  • Step S602 the user sends an initial NAS (Non-Access-Stratum) message to perform an attach operation.
  • RRC Radio Resource Control
  • Step S603 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 with the decision information.
  • Step S604 the mobility management entity starts the authentication and the security process, and performs verification on the user.
  • Step S605 the mobility management entity requests the HSS to perform location update.
  • Step S606 the HSS responds to the mobility management entity with a location update response.
  • Step S607 the mobility management entity sends a session establishment request to the S-GW.
  • Step S608 receiving a message sent by the mobility management entity, and the S-GW sends a session establishment request message to the P-GW.
  • the P-GW replies to the S-GW with a session establishment response.
  • Step S609 the S-GW sends a session establishment response to the mobility management entity.
  • Step S610 The mobility management entity initiates an initial context setup request to the radio side network element.
  • Step S613 The terminal sends a direct transmission message to the radio side network element, including attach completion information.
  • Step S614, the radio side network element sends an attach complete message to the mobility management entity.
  • Step S615 the mobility management entity requests the S-GW to update the bearer.
  • the P-GW responds to the S-GW with a bearer update response.
  • Step S617 the S-GW responds to the mobility management entity to carry an update response message.
  • Step S618, a tunnel is established between the wireless side network element and the local gateway.
  • the establishment manner may be: Method (1), the radio side network element requests a tunnel establishment from the local gateway, and the local gateway responds to the radio side network element tunnel establishment response.
  • Method (2) the message in the above method (1) is transmitted through the security gateway.
  • the method (3) the wireless side network element requests a tunnel establishment from the network element that is set up with the local gateway, and the network element notifies the local gateway to establish a tunnel between the wireless side network element and the local gateway, and further, the network element moves to the wireless side network element. Respond to the tunnel establishment response.
  • the above embodiment only illustrates the manner in which the mobile decision information is acquired by taking the case where the user initially accesses the connection establishment.
  • the radio side network element needs to notify the mobility management entity of the decision information by the PDN connection establishment request message (step S302), facilitating mobility management of the local IP access. Other processes are consistent with the prior art and will not be described here.
  • the radio side network element needs to notify the mobility management entity decision information through the service request message (step S402), which facilitates mobility management of the local IP access. Other processes are consistent with the prior art and will not be described here.
  • the radio side network element needs to notify the mobility management entity of the decision information through the tracking area update request message (step S4a01), which facilitates the mobility management of the local IP access.
  • step S4a01 the radio side network element needs to notify the mobility management entity of the decision information through the tracking area update request message (step S4a01), which facilitates the mobility management of the local IP access.
  • FIG. 6a is an interaction flowchart of the handover process performed by the terminal on the basis of the system of FIG. 1 according to the embodiment of the present invention.
  • the target wireless side network element sends the decision information to the target mobile.
  • the specific steps are as follows: Step S6a01: The radio side network element determines that the SI handover needs to be initiated.
  • Step S6a02 the original radio side network element sends a handover request to the original mobility management entity.
  • Step S6a03 the relocation forward request message sent by the original mobility management entity to the target mobility management entity.
  • the target mobility management entity may initiate a session establishment process of the core network and the local IP access connection to the core network gateway.
  • step S6a05 the target mobility management entity requests the target radio side network element to perform handover.
  • step S6a06 The target radio side network element responds to the target mobility management entity with a handover request acknowledgement message, and carries the decision information.
  • step S6a07 the target mobility management entity determines whether to support mobility according to the decision information. The method for judging whether mobility is supported is: if the initial or original CSG or LHN belongs to the decision information supporting mobility, or the initial or original CSG or LHN and the target CSG or LHN belong to the CSG or LHN list supporting mobility, the target mobile The sex management entity believes that mobility is supported.
  • the target mobility management entity considers support for mobility. If mobility is supported, the core network connection and the local IP access connection are activated/established/updated; otherwise, only the core network connection is activated/established/updated, and the local IP access connection is released. Step S6a08, the target mobility management entity sends a relocation forward response message to the original mobility management entity. If mobility is not supported, the message carries an indication that the local IP access connection is invalid. In step S6a09, the original mobility management entity sends a handover command to the original radio side network element. If mobility is not supported, the bearer information to be released in the handover command includes bearer information of the local IP access connection.
  • step S6al0 the normal switching process is continued.
  • step S6all if the mobility is not supported, the original mobility management entity initiates a deletion process of the local IP access connection to the original local gateway. This step can be performed after step S6a08.
  • step S6al2 if the mobility is not supported, the target mobility management entity initiates a deletion procedure of the local IP access connection bearer to the target radio side network element. This step can be performed in step S6a07.
  • FIG. 7 is an interaction flow diagram 2 of a user initial access for connection establishment on the basis of the system of FIG. 1 according to an embodiment of the present invention.
  • the local gateway transmits the decision information to the mobility management entity via the wireless side network element. .
  • Step S701 A user needs to establish an RRC (Radio Resource Control) connection as a signaling message or a bearer of service data before performing communication.
  • Step S702 the user sends an initial NAS (Non-Access-Stratum) message to perform an attach operation.
  • Step S703 the radio side network element sends the initial user message to the mobility management entity, and forwards the NAS message to the mobility management entity.
  • Step S704 the mobility management entity starts the authentication and the security process, and performs verification on the user.
  • Step S705 the mobility management entity requests the HSS to perform location update.
  • Step S706, the HSS responds to the mobility management entity with a location update response.
  • Step S707 the mobility management entity sends a session establishment request to the S-GW.
  • Step S708 Receive a message sent by the mobility management entity, and the S-GW sends a session establishment request message to the P-GW. The P-GW replies to the S-GW with a session establishment response.
  • Step S709 the S-GW sends a session establishment response to the mobility management entity.
  • Step S710 the mobility management entity initiates an initial context setup request to the radio side network element.
  • Step S711 performing an RRC connection configuration process.
  • Step S712 the radio side network element replies to the mobility management entity initial context establishment response.
  • Step S713 The terminal sends a direct transmission message to the radio side network element, including attach completion information.
  • Step S714 the radio side network element sends an attach complete message to the mobility management entity.
  • Step S715 the mobility management entity requests the S-GW to update the bearer.
  • Step S716, the S-GW sends a bearer update request to the P-GW.
  • the P-GW responds to the S-GW with a bearer update response.
  • Step S717 The S-GW returns a mobility management entity bearer update response message.
  • Step S718 to step S719 a tunnel is established between the radio side network element and the local gateway.
  • the establishment manner may be: Method (1), the radio side network element requests a tunnel establishment from the local gateway, the local gateway responds to the radio side network element tunnel establishment response, and the response message carries the decision information.
  • Method (2) the message in the above method (1) is transmitted through the security gateway.
  • the wireless side network element requests a tunnel establishment from the network element that is set up with the local gateway, and the network element notifies the local gateway to establish a tunnel between the wireless side network element and the local gateway, and further, the network element moves to the wireless side network element.
  • the response message carries the decision information.
  • the radio side network element sends an update message to the mobility management entity, and carries the decision information.
  • the above embodiment only illustrates the manner in which the mobile decision information is acquired by taking the case where the user initially accesses the connection establishment.
  • step S720 for mobility management of local IP access.
  • Other processes are consistent with the prior art and will not be described here.
  • the process of transmitting the decision information by the local gateway to the mobility management entity is similar to the above steps S718 to S720 (ie, steps S412 to S413 require similar steps S718 to S720) to facilitate local IP. Mobility management for access. Other processes are consistent with the prior art and will not be described here.
  • the process of transmitting the decision information by the local gateway to the mobility management entity is similar to the above steps S718 to S720 (ie, steps S4al8 to S4al9 require similar steps S718 to S720), which facilitates localization. Mobility management for IP access. Other processes are consistent with the prior art and will not be described here.
  • FIG. 8 is an interaction flowchart 3 of the user initial access for connection establishment based on the system of FIG. 1 according to an embodiment of the present invention.
  • the decision information is transmitted by the local gateway to the mobility management entity via the service gateway.
  • the specific steps in this embodiment are described as follows: Step S801: A user needs to establish an RRC (Radio Resource Control) connection as a signaling message or a bearer of service data before performing communication.
  • RRC Radio Resource Control
  • Step S802 the user sends an initial NAS (Non-Access-Stratum) message to perform an attach operation.
  • Step S803 the radio side network element sends the initial user message to the mobility management entity, and forwards the NAS message to the mobility management entity.
  • Step S804 the mobility management entity starts the authentication and the security process, and performs verification on the user.
  • Step S805 the mobility management entity requests the HSS to perform location update.
  • Step S806 the HSS responds to the mobility management entity with a location update response.
  • Step S808a Receive a message sent by the mobility management entity, and the S-GW sends a session establishment request message to the P-GW.
  • Step S808b the P-GW returns a session establishment response to the S-GW, and carries the decision information.
  • Step S809 the S-GW sends a session establishment response to the mobility management entity, and carries the decision information.
  • Step S810 the mobility management entity initiates an initial context setup request to the radio side network element.
  • Step S811 performing an RRC connection configuration process.
  • Step S812 the radio side network element replies to the mobility management entity initial context establishment response.
  • Step S814, the radio side network element sends an attach complete message to the mobility management entity.
  • Step S815 the mobility management entity requests the S-GW to update the bearer.
  • the P-GW responds to the S-GW with a bearer update response.
  • the establishment manner may be: Method (1), the radio side network element requests a tunnel establishment from the local gateway, and the local gateway responds to the radio side network element tunnel establishment response.
  • Method (2), the message in the above method (1) is transmitted through the security gateway.
  • the wireless side network element requests a tunnel establishment from the network element that is set up with the local gateway, and the network element notifies the local gateway to establish a tunnel between the wireless side network element and the local gateway, and further, the network element moves to the wireless side network element. Respond to the tunnel establishment response.
  • the above embodiment only illustrates the manner in which the mobile decision information is acquired by taking the case where the user initially accesses the connection establishment.
  • the local gateway sends a session establishment response to the serving gateway (step S308), and the service gateway sends a session establishment response message (step S309) to the mobility management entity to carry the decision information, so that Mobility management for local IP access.
  • the service gateway sends a session establishment response message (step S309) to the mobility management entity to carry the decision information, so that Mobility management for local IP access.
  • the local gateway sends a modify bearer response to the serving gateway (step S410), and the service gateway sends the modify bearer response message (step S411) to the mobility management entity to carry the decision information, which facilitates local IP access. Mobility management. Other processes are consistent with the prior art and will not be described here.
  • the local gateway sends a modify bearer response to the serving gateway (step S4a09), and the serving gateway sends the modify bearer response message (step S4al0) to the mobility management entity to carry the decision information, which facilitates local IP. Mobility management for access. Other processes are consistent with the prior art and will not be described here.
  • FIG. 9 is an interaction flowchart 4 of the user initial access for connection establishment based on the system of FIG. 1 according to an embodiment of the present invention.
  • the decision information is transmitted by the authentication authority server to the mobility management entity.
  • Step S901 A user needs to establish an RRC (Radio Resource Control) connection as a signaling message or a bearer of service data before performing communication.
  • RRC Radio Resource Control
  • Step S902 the user sends an initial NAS (Non-Access-Stratum) message to perform an attach operation.
  • Step S903 the radio side network element sends the initial user message to the mobility management entity, and forwards the NAS message to the mobility management entity.
  • Step S904 the mobility management entity starts the authentication and the security process, and performs verification on the user.
  • Step S905 the mobility management entity requests the HSS to perform location update.
  • Step S906 the HSS responds to the mobility management entity with a location update response, and carries the decision information.
  • Step S907 the mobility management entity sends a session establishment request to the S-GW.
  • Step S908 Receive a message sent by the mobility management entity, and the S-GW sends a session establishment request message to the P-GW.
  • the P-GW replies to the S-GW with a session establishment response.
  • Step S909 the S-GW sends a session establishment response to the mobility management entity.
  • Step S910 the mobility management entity initiates an initial context setup request to the radio side network element.
  • Step S911 performing an RRC connection configuration process.
  • Step S912 the radio side network element replies to the mobility management entity initial context establishment response.
  • Step S913, the terminal sends a direct transmission message to the radio side network element, including attach completion information.
  • the radio side network element sends an attach complete message to the mobility management entity.
  • Step S915 the mobility management entity requests the S-GW to update the bearer.
  • the P-GW responds to the S-GW with a bearer update response.
  • Step S917 the S-GW returns a mobility management entity bearer update response message.
  • Step S918 to step S919 a tunnel is established between the radio side network element and the local gateway.
  • the establishment manner may be: Method (1), the radio side network element requests a tunnel establishment from the local gateway, and the local gateway responds to the radio side network element tunnel establishment response.
  • Method (2) the message in the above method (1) is transmitted through the security gateway.
  • the method (3) the wireless side network element requests a tunnel establishment from the network element that is set up with the local gateway, and the network element notifies the local gateway to establish a tunnel between the wireless side network element and the local gateway, and further, the network element moves to the wireless side network element.
  • FIG. 10 is an interaction flowchart 5 of the user initial access for connection establishment based on the system of FIG. 1 according to an embodiment of the present invention.
  • the decision information is transmitted to the mobility management entity by the DNS server or the network management system.
  • Step S1001 Before the communication is performed, the user needs to establish an RRC (Radio Resource Control) connection as a signaling message or a bearer of service data.
  • step S1002 the user sends an initial NAS (Non-Access-Stratum) message to perform an attach operation.
  • Step S1003 The radio side network element sends the initial user message to the mobility management entity, and forwards the NAS message to the mobility management entity.
  • step S1004 the mobility management entity starts the authentication and the security process, and performs verification on the user.
  • Step S1005 The mobility management entity queries the DNS server or the network management system for the decision information, with the APN and/or the radio side network element information and/or the local gateway information.
  • Step S1006 The DNS server or the network management system responds to the mobility management entity with a response message and carries the decision information.
  • Step S1007 The mobility management entity sends a session establishment request to the S-GW.
  • Step S1008 Receive a message sent by the mobility management entity, and the S-GW sends a session establishment request message to the P-GW.
  • the P-GW replies to the S-GW with a session establishment response.
  • Step S1009 The S-GW sends a session establishment response to the mobility management entity.
  • Step S1010 The mobility management entity initiates an initial context setup request to the radio side network element.
  • an RRC connection configuration process is performed.
  • Step S1012 The radio side network element replies to the mobility management entity initial context establishment response.
  • Step S1013 The terminal sends a direct transmission message to the radio side network element, including attach completion information.
  • Step S1014 The radio side network element sends an attach complete message to the mobility management entity.
  • Step S1015 The mobility management entity requests the S-GW to update the bearer.
  • Step S1016 The S-GW sends a bearer update request to the P-GW.
  • the P-GW responds to the S-GW with a bearer update response.
  • Step S1017 The S-GW responds to the mobility management entity to carry an update response message.
  • Step S1018 to step S1019 a tunnel is established between the radio side network element and the local gateway.
  • the establishment manner may be: Method (1), the radio side network element requests a tunnel establishment from the local gateway, and the local gateway responds to the radio side network element tunnel establishment response.
  • Method (2) the message in the above method (1) is transmitted through the security gateway.
  • the method (3) the wireless side network element requests a tunnel establishment from the network element that is set up with the local gateway, and the network element notifies the local gateway to establish a tunnel between the wireless side network element and the local gateway, and further, the network element moves to the wireless side network element. Respond to the tunnel establishment response.
  • the above embodiment only illustrates the manner in which the mobile decision information is acquired by taking the case where the user initially accesses the connection establishment.
  • the mobility management entity adds a message to the DNS server or the network management system to acquire the decision information after step S302 (similar to steps S1005 and S1006), the step is performed after step S302, There is no sequence with the subsequent steps of step S302, which facilitates mobility management of local IP access. Other processes are consistent with the prior art and will not be described here.
  • the mobility management entity adds a message to the DNS server or the network management system to acquire the decision information after step S402 (similar to steps S1005 and S1006), the step is performed after step S402, and is followed by step S402. The steps are not in order, facilitating mobility management for local IP access. Other processes are consistent with the prior art and will not be described here.
  • the target mobility management entity adds a message to the DNS server or the network management system to acquire the decision information after step S4a01 (similar to step S1005 and step S1006), the step is performed after step S4a01, and steps The subsequent steps of S4a01 are not in order, which facilitates mobility management of local IP access. Other processes are consistent with the prior art and will not be described here.
  • FIG. 11 is a flow chart 1 of the interaction process performed by the terminal on the basis of the system of FIG. 1 according to the embodiment of the present invention.
  • the target mobility management entity determines whether mobility is supported. The specific steps are as follows: S1101: The wireless side network element determines that an S1 handover needs to be initiated.
  • Step S1102 The original radio side network element sends a handover request to the original mobility management entity, and carries the target CSG or LHN identifier.
  • Step S1103 The original mobility management entity sends a relocation forward request message to the target mobility management entity, and may carry the decision information.
  • the target mobility management entity determines whether mobility is supported. The method for judging whether mobility is supported is: if the initial or original CSG or LHN belongs to the decision information supporting mobility, or the initial or original CSG or LHN and the target CSG or LHN belong to the CSG or LHN list supporting mobility, the target mobile The sex management entity believes that mobility is supported.
  • the target mobility management entity If the initial or original CSG or LHN and the target CSG or LHN identity are the same, the target mobility management entity considers support for mobility. If mobility is supported, the core network connection and the local IP access connection are activated/established/updated; otherwise, only the core network connection is activated/established/updated, releasing the local IP access connection. Step S1105: If the mobility is not supported, the target mobility management entity initiates a session establishment and a forwarding tunnel establishment process of the core network connection to the core network gateway, and does not need to establish local IP access connection information. Step S1106: The target mobility management entity requests the target radio side network element to perform handover, and carries the bearer information of the core network connection without the local IP access connection information.
  • Step S1107 The target radio side network element responds to the target mobility management entity with a handover request acknowledgement message.
  • step S1108 the normal switching process is continued.
  • the relocation forward completion message sent by the target mobility management entity to the original mobility management entity carries the indication information that the local IP access is invalid.
  • Step S1109 Optionally, if the indication information of the local IP access failure is obtained in step 1108, the original mobility management entity initiates a deletion procedure of the local IP access connection to the original local access gateway.
  • FIG. 11a is an interaction flowchart 2 of a handover process performed by a terminal on the basis of the system of FIG.
  • the target mobility management entity determines whether mobility is supported.
  • the specific steps are as follows: SllaOl, the wireless side network element determines that an S1 switch needs to be initiated.
  • Step Slla02 the original radio side network element sends a handover request to the original mobility management entity.
  • Step Slla03 the relocation forward request message sent by the original mobility management entity to the target mobility management entity may optionally carry the decision information.
  • Step Slla04 the target mobility management entity may initiate a session establishment process of the core network and the local IP access connection to the core network gateway.
  • Step Slla05 the target mobility management entity requests the target radio side network element to perform handover.
  • Step Slla06 the target radio side network element responds to the target mobility management entity with a handover request acknowledgement message.
  • the target mobility management entity determines whether to support mobility based on the decision information. The method for judging whether mobility is supported is: if the initial or original CSG or LHN belongs to the decision information supporting mobility, or the initial or original CSG or LHN and the target CSG or LHN belong to the CSG or LHN list supporting mobility, the target mobile The sex management entity believes that mobility is supported. If the initial or original CSG or LHN and the target CSG or LHN identity are the same, the target mobility management entity considers support for mobility.
  • Step Slla08 the target mobility management entity sends a relocation forward response message to the original mobility management entity. If mobility is not supported, the message carries an indication that the local IP access connection is invalid.
  • step S11a09 the original mobility management entity sends a handover command to the original radio side network element. If mobility is not supported, the bearer information to be released in the handover command includes bearer information of the local IP access connection. Step SllalO, continue the normal switching process. Step Sllal l.
  • FIG. 12 is a flow chart 3 of the interaction process performed by the terminal on the basis of the system of FIG. 1 according to the embodiment of the present invention.
  • the original mobility management entity determines whether mobility is supported. The specific steps are as follows: Step S1201 The wireless side network element determines that an S1 handover needs to be initiated.
  • Step S1202 The original radio side network element sends a handover request to the original mobility management entity.
  • the original mobility management entity determines whether mobility is supported.
  • the method for judging whether mobility is supported is: If the initial or original CSG or LHN belongs to the decision information supporting mobility, or the original or original CSG or LHN and the target CSG or LHN belong to the CSG or LHN list supporting mobility, the original mobile Sexual management The body believes in supporting mobility. If the initial or original CSG or LHN and the target CSG or LHN identity are the same, the original mobility management entity considers support for mobility.
  • Step S1204 The relocation forward request message sent by the original mobility management entity to the target mobility management entity. If mobility is not supported, the message does not carry bearer information of the local IP access connection. Step S1205, the target mobility management entity may initiate a session establishment of the core network connection to the core network gateway.
  • Step S1206 The target mobility management entity requests the target radio side network element to perform handover.
  • Step S1207 The target radio side network element responds to the target mobility management entity with a handover request acknowledgement message.
  • step S1208 the normal switching process is continued.
  • Step S1209 If the mobility is not supported, the original mobility management entity initiates a deletion process of the local IP access connection to the original local gateway. This step can be performed after step S1203.
  • FIG. 13 is an interaction flowchart of the service request process and the mobility management entity performing mobility determination when the terminal is changed from the idle state to the connected state, and the mobility management entity performs the mobility determination according to the system of FIG. 1 according to the embodiment of the present invention.
  • Step S1301 After the terminal accesses the wireless communication system, the terminal has a local IP access connection and a core network connection, and then the terminal enters an idle state.
  • Step S1302 The terminal sends a service request message to the mobility management entity via the radio side network element.
  • step S1303 a NAS (Non-Access-Stratum) authentication process is performed, and the step is optional.
  • Step S1304 the mobility management entity determines whether mobility is supported.
  • the method for judging whether mobility is supported is: If the initial or original CSG or LHN belongs to the decision information supporting mobility, or the initial or original CSG or LHN and the target CSG or LHN belong to the CSG or LHN list supporting mobility, the mobility The management entity believes that mobility is supported. If the initial or original CSG or LHN and the target CSG or LHN identity are the same, the mobility management entity considers support for mobility. If mobility is supported, the core network connection and the local IP access connection are activated/established/updated; otherwise, only the core network connection is activated/established/updated, and the local IP access connection is released. Step S1305: The mobility management entity sends an initial context setup request message to the radio side network element.
  • Step S1306 The radio side network element performs a radio bearer setup process.
  • Step S1307 The radio side network element responds to the mobility management entity initial context establishment complete message.
  • Step S1308 If mobility is not supported, the mobility management entity performs a bearer release procedure of the local IP access connection with the local gateway. If mobility is supported, the mobility management entity performs a bearer modification operation with the local gateway for the local IP access connection.
  • Step S1401 The terminal sends a tracking area update request message to the mobility management entity via the target radio side network element, and carries the activation identifier.
  • Step S1402 The target mobility management entity sends a context request message to the original mobility management entity.
  • Step S1403 The context response message sent by the original mobility management entity to the target mobility management entity optionally carries the decision information.
  • Step S1404, optionally, the terminal, the mobility management entity, and the authentication authorization server perform an authentication process.
  • the target mobility management entity determines whether mobility is supported.
  • the method for judging whether mobility is supported is: if the initial or original CSG or LHN belongs to the decision information supporting mobility, or the initial or original CSG or LHN and the target CSG or LHN belong to the CSG or LHN list supporting mobility, the target mobile The sex management entity believes that mobility is supported. If the initial or original CSG or LHN and the target CSG or LHN identity are the same, the target mobility management entity considers support for mobility. If mobility is supported, the core network connection and the local IP access connection are activated/established/updated; otherwise, only the core network connection is activated/established/updated, releasing the local IP access connection.
  • Step S1406 If the mobility is not supported, the Context Confirmation message sent by the target mobility management entity to the original mobility management entity may carry the local IP access failure indication information.
  • Step S1407 The target mobility management entity initiates a bearer modification operation to the core network S-GW, and does not need to modify the information of the local IP access connection.
  • Step S1408, a location update process is performed between the target mobility management entity and the authentication authorization server.
  • Step S1409, the location cancellation process is performed between the authentication authorization server and the original mobility management entity.
  • Step S1410 The target mobility management entity sends an initial context setup request message to the target radio side network element, carrying the core network connection information without the local IP access connection information.
  • Step S1411 The target radio side network element performs a radio bearer setup process.
  • Step S1412 The target radio side network element responds to the mobility management entity initial context setup complete/radio bearer setup complete message.
  • Step S1413 The mobility management entity requests the core network S-GW to perform bearer modification, so as to activate/establish the core network connection of the terminal; and the core network S-GW sends a bearer modification response message to the mobility management entity.
  • the core network S-GW sends a bearer modification request message to the core network P-GW.
  • Step S1414 optionally, the target mobility management entity initiates a release process of the local IP access connection.
  • Step S1415 or, optionally, the original mobility management entity initiates a release procedure of the local IP access connection after acquiring the local IP access failure indication information in step S1406.
  • step S1414 can be performed after step S1405.
  • FIG. 15 is an interaction flowchart 2 of the terminal performing location update process on the basis of the system of FIG. 1 according to an embodiment of the present invention.
  • the original mobility management entity determines whether mobility is supported.
  • the specific steps are as follows: Step S1501: The terminal sends a tracking area update request message to the mobility management entity via the target radio side network element, and carries the activation identifier.
  • Step S1502 The target mobility management entity sends a context request message to the original mobility management entity.
  • step S1503 the original mobility management entity determines whether mobility is supported.
  • the method for judging whether mobility is supported is: If the initial or original CSG or LHN belongs to the decision information supporting mobility, or the original or original CSG or LHN and the target CSG or LHN belong to the CSG or LHN list supporting mobility, the original mobile The sex management entity believes that mobility is supported. If the initial or original CSG or LHN and the target CSG or LHN identity are the same, the original mobility management entity considers support for mobility. If mobility is supported, the core network connection and the local IP access connection are activated/established/updated; otherwise, only the core network connection is activated/established/updated, releasing the local IP access connection.
  • Step S1504 If the mobility is not supported, the context response message sent by the original mobility management entity to the target mobility management entity carries the core network connection information without the local IP access connection information. S1505.
  • the terminal, the mobility management entity, and the authentication authorization server perform an authentication process.
  • S1506 The target mobility management entity sends a context confirmation message to the original mobility management entity.
  • S1507. The target mobility management entity initiates a bearer modification operation to the core network S-GW.
  • S1508 Perform a location update process between the target mobility management entity and the authentication authorization server.
  • Step S1509 The location cancellation process is performed between the authentication authorization server and the original mobility management entity.
  • the target mobility management entity sends an initial context setup request to the target radio side network element.
  • Step S1511 The target radio side network element performs a radio bearer setup process.
  • Step S1512 The target radio side network element responds to the mobility management entity initial context establishment completion/radio bearer setup completion message.
  • Step S1513 The mobility management entity requests the core network S-GW to perform bearer modification, so as to activate/establish the core network connection of the terminal; and the core network S-GW sends a bearer modification response message to the mobility management entity.
  • the core network S-GW sends a bearer modification request message to the core network P-GW.
  • Step S1514 the original mobility management entity initiates a release process of the local IP access connection. Step S1514 may be performed after step S1503.
  • the wireless side network element or the local gateway may also send the decision information to the mobility management entity at the time of power-on, so as to facilitate mobility determination during the mobile process.
  • Decision information refers to CSG or LHN information, such as CSG list or CSG group or CSG name or LHN name or
  • the LHN identifier can be used to determine whether to maintain mobility or business continuity.
  • the information of the radio side network element includes: a radio side network element identifier, a radio side network element address, and a radio side network element ID.
  • the local gateway information includes: a local gateway identifier, a local gateway address, and a local gateway ID.
  • the decision information can be obtained through various processes shown in FIGS. 6 to 10. If the local IP access and the core network connection use the same service gateway, the service gateway is both a local service gateway and a core network service gateway. In order to simplify the description, the above embodiment only illustrates the management manner of the local IP access connection by taking the case of FIG.
  • the wireless side network element may be a base station, a home base station, a home base station gateway, and an RNC (Radio Network Controller) data offload function entity.
  • RNC Radio Network Controller
  • the mobility management entity may be an MME (Mobility Management Entity) MSC (Mobile Switching Centre), an SGSN (Serving GPRS Support Node), a home base station gateway.
  • the local gateway may be an L-SGW and an L-PGW, may be a separate L-PGW, may be an L-GGSN and an L-SGSN, may be a separate L-GGSN, and may be a data offloading functional entity.
  • the core network access gateway may be an S-GW, a P-GW, an SGSN, or a GGSN.
  • the service gateway includes a local service gateway or/and a core network service gateway, and the access gateway includes a local access gateway or
  • the local service gateway can be an L-SGW or an L-SGSN or an L-GW.
  • the core network service gateway can be an S-GW or an SGSN.
  • the local gateway can be a local access gateway and/or a local service gateway.
  • the local access gateway may be an L-PGW or an L-GGSN or an L-GW.
  • the core network access gateway may be an S-GW, a P-GW, an SGSN, or a GGSN.
  • the core network gateway may be a core network access gateway and/or a core network service gateway.
  • the service gateway can be a local service gateway or a core network service gateway.
  • the wireless side network element accessed by the local IP address can be the same as the local gateway address.
  • the authentication authorization server can be a user subscription database.
  • the location update can be a tracking area update, a routing area update.
  • Local IP access 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, and specific IP data offloading.
  • the initial CSG or LHN identity of the user refers to the CSG or LHN identity when the user initially establishes a local IP access connection.
  • FIG. 16 is a structural block diagram of a processing apparatus for a local IP access connection according to an embodiment of the present invention. As shown in FIG. 16, a receiving module 162 and a determining module 164 are included.
  • the receiving module 162 is configured to receive the mobile decision information during the establishment of the local IP access connection.
  • the determining module 164 is coupled to the receiving module 162, and configured to determine whether the local IP access connection is supported according to the mobile decision information received by the receiving module 162. Mobility. It should be noted that the processing device of the local IP access connection described in the device embodiment corresponds to the foregoing method embodiment, and the specific implementation process has been described in detail in the method embodiment, and details are not described herein again. In summary, according to the above embodiments of the present invention, a method and apparatus for processing a local IP access connection are provided.
  • the mobile decision information is externally configured and received by the mobility management entity, thereby implementing flexible processing performance of the IP offload system and improving system operability.
  • 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.
  • 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 modules or steps are made into a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种本地IP访问连接的处理方法及装置,该方法包括:在建立本地IP访问连接的过程中,移动性管理实体接收到移动决策信息;移动性管理实体根据移动决策信息,判断本地IP访问连接是否支持移动性。通过本发明,移动决策信息通过外部配置,并由移动性管理实体接收,从而可实现IP分流系统的灵活处理性能,提升系统可操作性。

Description

本地 IP访问连接的处理方法及装置 技术领域 本发明涉及通信领域, 具体而言, 涉及一种本地 IP访问连接的处理方法及装置。 背景技术 第三代合作伙伴计划(3rd Generation Partnership Project, 简称为 3GPP)演进的分 组系统(Evolved Packet System, 简称为 EPS) 由演进的通用移动通信系统陆地无线接 入网 (Evolved Universal Terrestrial Radio Access Network, 简称为 E-UTRAN)、 移动管 理单元 (Mobility Management Entity, 简称为 MME)、 服务网关 (Serving Gateway, 简称为 S-GW)、 分组数据网络网关 (Packet Data Network Gateway, 简称为 P-GW或 者 PDN GW) 归属用户服务器(Home Subscriber Server, 简称为 HSS)、 3 GPP的认证 授权计费 (Authentication Authorization and Accounting, 简称为 AAA)服务器, 策略 和计费规则功能 (Policy and Charging Rules Function, 简称为 PCRF) 实体及其他支撑 节点组成。 图 1是根据相关技术的 EPS系统架构的一种示意图,图 la是根据相关技术的 EPS 系统架构的另一种示意图, 图 lb是根据相关技术的 EPS系统架构的又一种示意图, 移动性管理实体负责移动性管理、 非接入层信令的处理和用户移动管理上下文的管理 等控制面的相关工作; S-GW是与 E-UTRAN相连的接入网关设备, 在 E-UTRAN和 P-GW之间转发数据, 并且负责对寻呼等待数据进行缓存; P-GW则是 EPS与分组数 据网络 (Packet Data Network, 简称为 PDN) 网络的边界网关, 负责 PDN的接入及在 EPS与 PDN间转发数据等功能; S-GW和 P-GW都属于核心网网关。 除了支持移动核心网络的接入以外, 移动通信系统 (包括家用基站系统) 还可支 持本地 IP访问功能, 在无线侧网元具备本地 IP访问能力以及用户签约允许本地 IP访 问的条件下, 可实现终端对家用网络其他 IP设备或者互联网络的本地接入。 本地 IP访问的实现可以采用多种连接建立方式:可通过建立一个连接来同时实现 核心网访问以及本地 IP的访问功能,此时无需在无线侧网元或家用基站网关上增设本 地网关的功能 (如图 lb); 也可通过增设本地网关来提供对本地 IP访问技术的有力支 持, 本地网关作为本地接入到外部网络(例如 Internet)的网关, 提供地址分配、计费、 分组包过滤、策略控制、数据分流功能、无线接入网应用部分(Radios Access Network Application Part, 简称为 NAS/S1-AP/RANAP ) /通用隧道协议 (General Tunneling Protocol, 简称为 GTP) /代理移动 IP协议 (Proxy Mobile IP, 简称为 PMIP) /移动 IP 协议 (Mobile IP, 简称为 MIP) 消息解析、 NAT (Network Address Translation, 网络 地址转换)、 本地 IP访问策略路由和执行等功能。 本地网关可与无线侧网元进行合设 / 分设 (如图 1所示)。 图 2是根据相关技术的本地 IP接入数据流的一种示意图, 图 2a是根据相关技术 的本地 IP接入数据流的另一种示意图, 图 2b是根据相关技术的本地 IP接入数据流的 又一种示意图, 如图 2、 图 2a和图 2b所示, 基于长期演进 (Long Term Evolution, 简 称为 LTE)移动通信网络架构下, 在图 1中所示的无线通信系统中本地 IP访问和核心 网连接的数据流。 图 3是根据相关技术的在图 1系统的基础上,用户进行 PDN连接建立的交互流程 图, 如图 3所示, 本实施例具体步骤描述如下: 步骤 S301 , 用户在进行通信前需要建立无线资源控制 (Radio Resource Control, 简称为 RRC) 连接作为信令消息或者业务数据的承载。 步骤 S302, 用户发送初始化非接入层 (Non-Access-Stratum, 简称为 NAS) 消息 进行附着操作。 步骤 S303 , 无线侧网元将初始的用户消息发给移动性管理实体, 并转发 NAS消 息至移动性管理实体。 步骤 S304, 移动性管理实体开启鉴权以及安全流程, 对用户进行验证。 步骤 S305, 移动性管理实体请求 HSS进行位置更新。 步骤 S306, HSS向移动性管理实体回应位置更新响应。 步骤 S307, 移动性管理实体向 S-GW发送会话建立请求。 步骤 S308, 接收到移动性管理实体发送的消息, S-GW将会话建立请求消息发送 给 P-GW。 P-GW向 S-GW回复会话建立响应。 步骤 S309, S-GW向移动性管理实体发送会话建立响应。 步骤 S310, 移动性管理实体向无线侧网元发起初始上下文建立请求。 步骤 S311, 执行 RRC连接配置过程。 步骤 S312, 无线侧网元回复移动性管理实体初始上下文建立响应。 步骤 S313 , 终端向无线侧网元发送直传消息, 包括附着完成信息。 步骤 S314, 无线侧网元向移动性管理实体发送附着完成消息。 步骤 S315 , 移动性管理实体向 S-GW请求更新承载。 步骤 S316, S-GW向 P-GW发送承载更新请求。 P-GW向 S-GW回应承载更新响 应。 步骤 S317, S-GW回应移动性管理实体承载更新响应消息。 步骤 S318, 无线侧网元与本地网关之间进行隧道建立。 无线侧网元向本地网关请 求隧道建立。 步骤 S319, 本地网关回应无线侧网元隧道建立响应。 图 4是根据相关技术的在图 1系统的基础上, 提供的终端由空闲态转为连接态时 进行服务请求的交互流程图, 如图 4所示, 包括如下的步骤 S401至步骤 S412。 步骤 S401, 终端接入无线通信系统后具有本地 IP访问连接, 此后终端进入空闲 态。 步骤 S402, 终端经无线侧网元向移动性管理实体发送服务请求消息。 步骤 S403 , 执行 NAS (Non-Access-Stratum, 非接入层)认证过程, 该步骤可选。 步骤 S404, 移动性管理实体向无线侧网元发送初始上下文建立请求消息。 步骤 S405 , 无线侧网元执行无线承载建立过程。 步骤 S406, 无线侧网元回应移动性管理实体初始上下文建立完成消息。 步骤 S407, 移动性管理实体请求服务网关进行承载修改。 步骤 S408, 服务网关向本地网关发送承载修改请求消息。 步骤 S409, 本地网关回应承载修改响应消息给服务网关。 步骤 S410, 服务网关向移动性管理实体发送修改承载响应消息。 步骤 S411, 无线侧网元与本地网关之间进行隧道建立。 无线侧网元向本地网关请 求隧道建立。 步骤 S412, 本地网关回应无线侧网元隧道建立响应。 图 4a是根据相关技术的在图 1系统的基础上,提供的终端进行位置更新过程的交 互流程图, 如图 4a所示, 包括如下的步骤 S4a01至步骤 S4al8。 步骤 S4a01, 终端经目标无线侧网元向移动性管理实体发送跟踪区更新请求消息, 携带激活标识。 步骤 S4a02, 目标移动性管理实体向原移动性管理实体发送上下文请求消息。 步骤 S4a03, 原移动性管理实体向目标移动性管理实体发送的上下文应答消息。 步骤 S4a04, 可选地, 终端、 移动性管理实体、 鉴权授权服务器执行认证过程。 步骤 S4a05, 目标移动性管理实体向原移动性管理实体发送上下文确认消息。 步骤 S4a06, 目标移动性管理实体向目标服务网关发起创建会话请求操作。 步骤 S4a07, 目标服务网关向本地网关请求承载修改。 步骤 S4a08, 本地网关回复目标服务网关承载修改响应。 步骤 S4a09, 目标服务网关向目标移动性管理实体回复创建会话响应。 步骤 S4al0, 目标移动性管理实体与鉴权授权服务器之间执行位置更新流程。 步骤 S4all, 鉴权授权服务器与原移动性管理实体之间执行位置取消过程。 步骤 S4al2, 目标移动性管理实体向目标无线侧网元发送初始上下文建立请求消 息。 步骤 S4al3, 目标无线侧网元执行无线承载建立过程。 步骤 S4al4, 目标无线侧网元回应移动性管理实体初始上下文建立完成 /无线承载 建立完成消息。 步骤 S4al5, 移动性管理实体请求目标服务网关进行承载修改, 以便激活 /建立终 端的核心网连接。 步骤 S4al6, 目标服务网关向目标移动性管理实体发送承载修改响应消息。 可选 地, 目标服务网关与本地网关进行承载修改。 步骤 S4al7, 无线侧网元与本地网关之间进行隧道建立。 无线侧网元向本地网关 请求隧道建立。 步骤 S4al8, 本地网关回应无线侧网元隧道建立响应。 图 4b是根据相关技术的在图 1系统的基础上, 终端进行切换过程的交互流程图, 如图 4b所示, 包括如下的步骤 S4b01至步骤 S4b20。 步骤 S4b01, 无线侧网元判断需要发起 S1切换。 步骤 S4b02, 原无线侧网元向原移动性管理实体发送切换请求。 步骤 S4b03, 原移动性管理实体在向目标移动性管理实体发送的重定位前转请求 消息。 步骤 S4b04和步骤 S4b04a, 目标移动性管理实体可以向目标服务网关发起本地 IP 访问连接的会话建立流程。 步骤 S4b05, 目标移动性管理实体请求目标无线侧网元执行切换。 步骤 S4b06, 目标无线侧网元向目标移动性管理实体回应切换请求确认消息。 步骤 S4b07, 目标移动性管理实体向原移动性管理实体发送重定位前转响应消息。 步骤 S4b08, 原移动性管理实体向原无线侧网元发送切换命令。 步骤 S4b09, 原无线侧网元终端发送切换执行。 步骤 S4M0, 终端向目标无线侧网元通知切换确认。 步骤 S4bll, 目标无线侧网元通知目标移动性管理实体进行切换。 步骤 S4M2, 目标移动性管理实体向原移动性管理实体发送重定位前转完成通知 消息。 步骤 S4M3 , 原移动性管理实体回复确认响应。 步骤 S4M4, 目标移动性管理实体向目标服务网关请求承载修改。 步骤 S4M5和步骤 S4bl6, 目标服务网关与本地网关之间进行承载修改操作。 步骤 S4M7, 目标服务网关向目标移动性管理实体回复承载修改响应消息。 步骤 S4al8, 无线侧网元与本地网关之间进行隧道建立。 无线侧网元向本地网关 请求隧道建立。 步骤 S4al9, 本地网关回应无线侧网元隧道建立响应。 步骤 S4b20, 继续执行正常的切换流程。 存在 IP分流的情况下, 允许在一定范围内保持终端业务连续性, 当终端发生移动 后移动性管理实体将通过移动决策信息(例如闭合用户组等信息)判断 IP分流连接是 否需要保持或释放。 相关技术中, 上述移动决策信息在移动性管理实体上进行配置, 该方式不够灵活 且网管操作复杂。 发明内容 本发明提供了一种本地 IP访问连接的处理方法及装置, 以至少解决相关技术中, 移动决策信息在移动性管理实体上进行配置, 不够灵活且网管操作复杂的问题。 为了实现上述目的, 根据本发明的一个方面, 提供了一种本地 IP访问连接的处理 方法。 根据本发明的一个方面, 提供了一种本地 IP访问连接的处理方法包括: 在建立本 地 IP访问连接的过程中, 移动性管理实体接收到移动决策信息; 移动性管理实体根据 移动决策信息, 判断本地 IP访问连接是否支持移动性。 移动性管理实体接收到移动决策信息包括: 移动性管理实体接收到无线侧网元发 送的移动决策信息, 其中无线侧网元包括以下之一: 基站、 家用基站、 家用基站网关、 无线网络控制器、 数据分流功能实体。 移动性管理实体接收到移动决策信息包括: 移动性管理实体接收到本地网关发送 的移动决策信息, 其中本地网关是本地接入网关和 /或本地服务网关, 本地接入网关包 括以下之一: L-PGW、 L-GGSN L-GW,本地服务网关是以下之一: L-SGW L-SGSN L-GWo 移动性管理实体接收到本地网关发送的移动决策信息包括以下之一: 移动性管理 实体接收到本地网关经由无线侧网元发送的移动决策信息, 其中无线侧网元包括以下 之一: 基站、 家用基站、 家用基站网关、 无线网络控制器、 数据分流功能实体; 移动 性管理实体接收到本地网关经由服务网关发送的移动决策信息, 其中服务网关是本地 服务网关禾 P/或核心网服务网关,本地服务网关是以下之一: L-SGW、 L-SGSN L-GW, 核心网服务网关包括以下之一: S-GW、 SGSN。 移动性管理实体接收到移动决策信息包括:移动性管理实体接收到 DNS服务器或 网管系统发送的移动决策信息。 移动性管理实体接收到移动决策信息包括: 移动性管理实体接收到鉴权授权服务 器发送的移动决策信息。 本地 IP访问连接包括以下之一: 本地 IP访问用户本地网络、 本地 IP访问公司本 地网络、 本地 IP访问互联网、 互联网业务的分流操作、 特定 IP数据分流。 移动性管理实体包括以下之一: 移动管理单元、 移动交换中心、 服务通用分组无 线业务支持节点、 家用基站网关。 移动决策信息包括以下至少之一: CSG列表、 CSG组、 CSG名。 移动决策信息还包括以下至少之一: LHN名、 LHN标识。 为了实现上述目的, 根据本发明的另一个方面, 提供了一种本地 IP访问连接的处 理装置。 根据本发明的本地 IP访问连接的处理装置, 可以应用于移动性管理实体, 包括接 收模块, 设置为在建立本地 IP访问连接的过程中, 接收移动决策信息; 判断模块, 设 置为根据移动决策信息, 判断本地 IP访问连接是否支持移动性。 通过本发明, 移动决策信息通过外部配置, 并由移动性管理实体接收, 从而可实 现 IP分流系统的灵活处理性能, 提升系统可操作性。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中: 图 1是根据相关技术的 EPS系统架构的一种示意图; 图 la是根据相关技术的 EPS系统架构的另一种示意图; 图 lb是根据相关技术的 EPS系统架构的又一种示意图; 图 2是根据相关技术的本地 IP接入数据流的一种示意图; 图 2a是根据相关技术的本地 IP接入数据流的另一种示意图; 图 2b是根据相关技术的本地 IP接入数据流的又一种示意图; 图 3是根据相关技术的在图 1系统的基础上,用户进行 PDN连接建立的交互流程 图; 图 4是根据相关技术的在图 1系统的基础上, 提供的终端由空闲态转为连接态时 进行服务请求的交互流程图; 图 4a是根据相关技术的在图 1系统的基础上,提供的终端进行位置更新过程的交 互流程图; 图 4b是根据相关技术的在图 1系统的基础上, 终端进行切换过程的交互流程图; 图 5是根据本发明实施例的本地 IP访问连接的处理方法的流程图; 图 6是根据本发明实施例的在图 1系统的基础上, 用户初始接入进行连接建立的 交互流程图一; 图 6a是根据本发明实施例的在图 1系统的基础上,终端进行切换过程的交互流程 图; 图 7是根据本发明实施例的在图 1系统的基础上, 用户初始接入进行连接建立的 交互流程图二; 图 8是根据本发明实施例的在图 1系统的基础上, 用户初始接入进行连接建立的 交互流程图三; 图 9是根据本发明实施例的在图 1系统的基础上, 用户初始接入进行连接建立的 交互流程图四; 图 10是根据本发明实施例的在图 1系统的基础上,用户初始接入进行连接建立的 交互流程图五; 图 11是根据本发明实施例的在图 1系统的基础上,终端进行切换过程的交互流程 图一; 图 11a是根据本发明实施例的在图 1系统的基础上, 终端进行切换过程的交互流 程图二; 图 12是根据本发明实施例的在图 1系统的基础上,终端进行切换过程的交互流程 图三; 图 13是根据本发明实施例的在图 1系统的基础上,提供的终端由空闲态转为连接 态时进行服务请求过程、 移动性管理实体进行移动性判断的交互流程图; 图 14是根据本发明实施例的在图 1系统的基础上,提供的终端进行位置更新过程 的交互流程图一; 图 15是根据本发明实施例的在图 1系统的基础上,提供的终端进行位置更新过程 的交互流程图二; 图 16是根据本发明实施例的本地 IP访问连接的处理装置的结构框图。 具体实施方式 需要说明的是, 在不冲突的情况下, 本申请中的实施例及实施例中的特征可以相 互组合。 下面将参考附图并结合实施例来详细说明本发明。 本发明提供了一种本地 IP访问连接的处理方法。图 5是根据本发明实施例的本地 IP访问连接的处理方法的流程图, 如图 5所示, 包括如下的步骤 S502至步骤 S504。 步骤 S502, 在建立本地 IP访问连接的过程中, 移动性管理实体接收到移动决策 信息。 步骤 S504, 移动性管理实体根据移动决策信息, 判断本地 IP访问连接是否支持 移动性。 相关技术中, 移动决策信息在移动性管理实体上进行配置, 该方式不够灵活且网 管操作复杂。 本发明实施例中, 移动决策信息通过外部配置, 并由移动性管理实体接 收, 从而可实现 IP分流系统的灵活处理性能, 提升系统可操作性。 优选地, 移动性管理实体接收到移动决策信息包括: 移动性管理实体接收到无线 侧网元发送的移动决策信息, 其中无线侧网元包括以下之一: 基站、 家用基站、 家用 基站网关、 无线网络控制器、 数据分流功能实体。 优选地, 移动性管理实体接收到移动决策信息包括: 移动性管理实体接收到本地 网关发送的移动决策信息, 其中本地网关是本地接入网关和 /或本地服务网关, 本地接 入网关包括以下之一:本地分组数据网络网关(Local PDN Gateway,简称为 L-PGW)、 本地网关通用分组无线业务支持节点 (Local Gateway General Packet Radio Service Supporting Node, 简称为 L-GGSN)、 本地网关 (Local Gateway, 简称为 L-GW), 本 地服务网关是以下之一: L-SGW、本地服务通用分组无线业务支撑节点(Local Serving General packet radio service Support Node, 简称为 L-SGSN) L-GW。 优选地, 移动性管理实体接收到本地网关发送的移动决策信息包括以下之一: 移 动性管理实体接收到本地网关经由无线侧网元发送的移动决策信息, 其中无线侧网元 包括以下之一: 基站、 家用基站、 家用基站网关、 无线网络控制器、 数据分流功能实 体; 移动性管理实体接收到本地网关经由服务网关发送的移动决策信息, 其中服务网 关是本地服务网关和 /或核心网服务网关,本地服务网关是以下之一: L-SGW、L-SGSN、 L-GW, 核心网服务网关包括以下之一: S-GW、 SGSN。 优选地, 移动性管理实体接收到移动决策信息包括: 移动性管理实体接收到 DNS 服务器或网管系统发送的移动决策信息。 优选地, 移动性管理实体接收到移动决策信息包括: 移动性管理实体接收到鉴权 授权服务器发送的移动决策信息。 优选地, 本地 IP访问连接包括以下之一: 本地 IP访问用户本地网络、 本地 IP访 问公司本地网络、 本地 IP访问互联网、 互联网业务的分流操作、 特定 IP数据分流。 优选地, 移动性管理实体包括以下之一: 移动管理单元、 移动交换中心、 服务通 用分组无线业务支持节点、 家用基站网关。 优选地, 移动决策信息包括以下至少之一: 闭合用户组(Closed Subscriber Group, 简称 CSG) 列表、 CSG组、 CSG名、 本地家用基站网络 (Local H(e)NB Network, 简 称为 LHN) 名、 LHN标识。 针对相关技术中如何对本地 IP访问连接获取移动决策信息的问题而提出本发明, 为此, 本发明的主要目的在于提供一种移动性管理实体获取移动决策信息的方法, 以 解决上述问题至少之一。 下面将结合实例对本发明实施例的实现过程进行详细描述。 以下实施例图描述了基于演进的通用移动通信系统陆地无线接入网 (Evolved Universal Terrestrial Radio Access Network,简称为 E-UTRAN)系统的应用场景。其中, 图 6至图 6a为由无线侧网元将决策信息传送给移动性管理实体的实施例。图 7为由本 地网关经无线侧网元将决策信息传送给移动性管理实体的实施例。 图 8为由本地网关 经服务网关将决策信息传送给移动性管理实体的实施例。 图 9为由鉴权授权服务器将 决策信息传送给移动性管理实体的实施例。 图 10为由 DNS服务器或网管系统将决策 信息传送给移动性管理实体的实施例。 图 11至图 15为移动性管理实体基于上述各种 方法获得决策信息后, 在移动过程中进行移动性判断的实施例。 图 6是根据本发明实施例的在图 1系统的基础上, 用户初始接入进行连接建立的 交互流程图一。 此时, 由无线侧网元将决策信息发给移动性管理实体。 本实施例具体 步骤描述如下: 步骤 S601 , 用户在进行通信前需要建立 RRC (Radio Resource Control, 无线资源 控制) 连接作为信令消息或者业务数据的承载。 步骤 S602, 用户发送初始化 NAS (Non-Access-Stratum, 非接入层) 消息进行附 着操作。 步骤 S603 , 无线侧网元将初始的用户消息发给移动性管理实体, 并转发 NAS消 息至移动性管理实体, 带决策信息。 步骤 S604, 移动性管理实体开启鉴权以及安全流程, 对用户进行验证。 步骤 S605, 移动性管理实体请求 HSS进行位置更新。 步骤 S606, HSS向移动性管理实体回应位置更新响应。 步骤 S607, 移动性管理实体向 S-GW发送会话建立请求。 步骤 S608, 接收到移动性管理实体发送的消息, S-GW将会话建立请求消息发送 给 P-GW。 P-GW向 S-GW回复会话建立响应。 步骤 S609, S-GW向移动性管理实体发送会话建立响应。 步骤 S610, 移动性管理实体向无线侧网元发起初始上下文建立请求。 步骤 S611 , 执行 RRC连接配置过程。 步骤 S612, 无线侧网元回复移动性管理实体初始上下文建立响应。 步骤 S613 , 终端向无线侧网元发送直传消息, 包括附着完成信息。 步骤 S614, 无线侧网元向移动性管理实体发送附着完成消息。 步骤 S615, 移动性管理实体向 S-GW请求更新承载。 步骤 S616, S-GW向 P-GW发送承载更新请求。 P-GW向 S-GW回应承载更新响 应。 步骤 S617, S-GW回应移动性管理实体承载更新响应消息。 步骤 S618, 无线侧网元与本地网关之间进行隧道建立。 其中建立方式可以为: 方法 (1 ), 无线侧网元向本地网关请求隧道建立, 本地网关回应无线侧网元隧道 建立响应。 方法 (2), 上述方法 (1 ) 中的消息经过安全网关传递。 方法 (3 ), 无线侧网元向与本地网关合设的网元请求隧道建立, 由该网元通知本 地网关建立无线侧网元与本地网关的隧道, 此外, 该网元向无线侧网元回应隧道建立 响应。 为了简化描述, 以上实施例仅以用户初始接入进行连接建立的情况为例来说明移 动决策信息的获取方式。
( 1 )对于多 PDN连接建立的情况下, 需要由无线侧网元通过 PDN连接建立请求 消息 (步骤 S302) 通知移动性管理实体决策信息, 便于进行本地 IP访问的移动性管 理。 其他流程与现有技术一致, 在此不再赘述。 (2) 对于服务请求过程, 需要由无线侧网元通过服务请求消息 (步骤 S402) 通 知移动性管理实体决策信息, 便于进行本地 IP访问的移动性管理。其他流程与现有技 术一致, 在此不再赘述。
( 3 ) 对于跟踪区更新过程, 需要由无线侧网元通过跟踪区更新请求消息 (步骤 S4a01 ) 通知移动性管理实体决策信息, 便于进行本地 IP访问的移动性管理。 其他流 程与现有技术一致, 在此不再赘述。
(4) 对于切换过程, 图 6a是根据本发明实施例的在图 1系统的基础上, 终端进 行切换过程的交互流程图, 该实施例中由目标无线侧网元将决策信息发送给目标移动 性管理实体, 具体步骤描述如下: 步骤 S6a01, 无线侧网元判断需要发起 SI切换。 步骤 S6a02, 原无线侧网元向原移动性管理实体发送切换请求。 步骤 S6a03, 原移动性管理实体在向目标移动性管理实体发送的重定位前转请求 消息。 步骤 S6a04, 目标移动性管理实体可以向核心网网关发起核心网和本地 IP访问连 接的会话建立流程。 步骤 S6a05, 目标移动性管理实体请求目标无线侧网元执行切换。 步骤 S6a06, 目标无线侧网元向目标移动性管理实体回应切换请求确认消息, 携 带决策信息。 步骤 S6a07, 目标移动性管理实体根据决策信息判断是否支持移动性。 判断是否 支持移动性的方法为: 如果初始或原 CSG或 LHN属于支持移动性的决策信息中, 或 者初始或原 CSG或 LHN和目标 CSG或 LHN属于支持移动性的 CSG或 LHN列表, 则目标移动性管理实体认为支持移动性。 如果初始或原 CSG或 LHN和目标 CSG或 LHN标识相同, 则目标移动性管理实体认为支持移动性。 如果支持移动性, 则激活 / 建立 /更新核心网连接和本地 IP访问连接; 否则, 则仅仅激活 /建立 /更新核心网连接, 释放本地 IP访问连接。 步骤 S6a08, 目标移动性管理实体向原移动性管理实体发送重定位前转响应消息。 若不支持移动性, 则在消息中携带本地 IP访问连接无效的指示。 步骤 S6a09, 原移动性管理实体向原无线侧网元发送切换命令。 如果不支持移动 性, 则该切换命令中携带需释放的承载信息包括本地 IP访问连接的承载信息。 步骤 S6al0, 继续正常的切换流程。 步骤 S6all, 如果不支持移动性, 原移动性管理实体向原本地网关发起本地 IP访 问连接的删除流程。 该步骤可以在步骤 S6a08后执行。 步骤 S6al2, 如果不支持移动性, 则目标移动性管理实体向目标无线侧网元发起 本地 IP访问连接承载的删除流程。 该步骤可以在步骤 S6a07执行。 图 7是根据本发明实施例的在图 1系统的基础上, 用户初始接入进行连接建立的 交互流程图二, 此时, 由本地网关将决策信息经无线侧网元传送给移动性管理实体。 本实施例具体步骤描述如下: 步骤 S701 , 用户在进行通信前需要建立 RRC (Radio Resource Control, 无线资源 控制) 连接作为信令消息或者业务数据的承载。 步骤 S702, 用户发送初始化 NAS (Non-Access-Stratum, 非接入层) 消息进行附 着操作。 步骤 S703 , 无线侧网元将初始的用户消息发给移动性管理实体, 并转发 NAS消 息至移动性管理实体。 步骤 S704, 移动性管理实体开启鉴权以及安全流程, 对用户进行验证。 步骤 S705, 移动性管理实体请求 HSS进行位置更新。 步骤 S706, HSS向移动性管理实体回应位置更新响应。 步骤 S707, 移动性管理实体向 S-GW发送会话建立请求。 步骤 S708, 接收到移动性管理实体发送的消息, S-GW将会话建立请求消息发送 给 P-GW。 P-GW向 S-GW回复会话建立响应。 步骤 S709, S-GW向移动性管理实体发送会话建立响应。 步骤 S710, 移动性管理实体向无线侧网元发起初始上下文建立请求。 步骤 S711 , 执行 RRC连接配置过程。 步骤 S712, 无线侧网元回复移动性管理实体初始上下文建立响应。 步骤 S713 , 终端向无线侧网元发送直传消息, 包括附着完成信息。 步骤 S714, 无线侧网元向移动性管理实体发送附着完成消息。 步骤 S715, 移动性管理实体向 S-GW请求更新承载。 步骤 S716, S-GW向 P-GW发送承载更新请求。 P-GW向 S-GW回应承载更新响 应。 步骤 S717, S-GW回应移动性管理实体承载更新响应消息。 步骤 S718至步骤 S719, 无线侧网元与本地网关之间进行隧道建立。 其中建立方 式可以为: 方法 (1 ), 无线侧网元向本地网关请求隧道建立, 本地网关回应无线侧网元隧道 建立响应, 响应消息中携带决策信息。 方法 (2), 上述方法 (1 ) 中的消息经过安全网关传递。 方法 (3 ), 无线侧网元向与本地网关合设的网元请求隧道建立, 由该网元通知本 地网关建立无线侧网元与本地网关的隧道, 此外, 该网元向无线侧网元回应隧道建立 响应, 响应消息中携带决策信息。 步骤 S720, 无线侧网元向移动性管理实体发送更新消息, 携带决策信息。 为了简化描述, 以上实施例仅以用户初始接入进行连接建立的情况为例来说明移 动决策信息的获取方式。
( 1 ) 对于多 PDN连接建立的情况下, 由本地网关向移动性管理实体传送决策信 息的过程与上述步骤 S718至步骤 S720类似(即步骤 S318至步骤 S319需要类似步骤
S718至步骤 S720处理), 以便进行本地 IP访问的移动性管理。 其他流程与现有技术 一致, 在此不再赘述。
(2)对于服务请求过程, 由本地网关向移动性管理实体传送决策信息的过程与上 述步骤 S718至步骤 S720类似 (即步骤 S412至步骤 S413需要类似步骤 S718至步骤 S720处理), 便于进行本地 IP访问的移动性管理。 其他流程与现有技术一致, 在此不 再赘述。 (3 )对于跟踪区更新过程, 由本地网关向移动性管理实体传送决策信息的过程与 上述步骤 S718至步骤 S720类似 (即步骤 S4al8至步骤 S4al9需要类似步骤 S718至 步骤 S720处理), 便于进行本地 IP访问的移动性管理。其他流程与现有技术一致, 在 此不再赘述。 (4)对于切换过程, 由本地网关向移动性管理实体传送决策信息的过程与上述步 骤 S718至步骤 S720类似(即步骤 S4M9至步骤 S4b20需要类似步骤 S718至步骤 S720 处理), 便于进行本地 IP访问的移动性管理。 其他流程与现有技术一致, 在此不再赘 述。 图 8是根据本发明实施例的在图 1系统的基础上, 用户初始接入进行连接建立的 交互流程图三。 此时, 由本地网关将决策信息经服务网关传送给移动性管理实体。 本 实施例具体步骤描述如下: 步骤 S801 , 用户在进行通信前需要建立 RRC (Radio Resource Control, 无线资源 控制) 连接作为信令消息或者业务数据的承载。 步骤 S802, 用户发送初始化 NAS (Non-Access-Stratum, 非接入层) 消息进行附 着操作。 步骤 S803 , 无线侧网元将初始的用户消息发给移动性管理实体, 并转发 NAS消 息至移动性管理实体。 步骤 S804, 移动性管理实体开启鉴权以及安全流程, 对用户进行验证。 步骤 S805, 移动性管理实体请求 HSS进行位置更新。 步骤 S806, HSS向移动性管理实体回应位置更新响应。 步骤 S807, 移动性管理实体向 S-GW发送会话建立请求。 步骤 S808a,接收到移动性管理实体发送的消息, S-GW将会话建立请求消息发送 给 P-GW。 步骤 S808b, P-GW向 S-GW回复会话建立响应, 携带决策信息。 步骤 S809, S-GW向移动性管理实体发送会话建立响应, 携带决策信息。 步骤 S810, 移动性管理实体向无线侧网元发起初始上下文建立请求。 步骤 S811 , 执行 RRC连接配置过程。 步骤 S812, 无线侧网元回复移动性管理实体初始上下文建立响应。 步骤 S813 , 终端向无线侧网元发送直传消息, 包括附着完成信息。 步骤 S814, 无线侧网元向移动性管理实体发送附着完成消息。 步骤 S815, 移动性管理实体向 S-GW请求更新承载。 步骤 S816, S-GW向 P-GW发送承载更新请求。 P-GW向 S-GW回应承载更新响 应。 步骤 S817, S-GW回应移动性管理实体承载更新响应消息。 步骤 S818至步骤 S819, 无线侧网元与本地网关之间进行隧道建立。 其中建立方 式可以为: 方法 (1 ), 无线侧网元向本地网关请求隧道建立, 本地网关回应无线侧网元隧道 建立响应。 方法 (2), 上述方法 (1 ) 中的消息经过安全网关传递。 方法 (3 ), 无线侧网元向与本地网关合设的网元请求隧道建立, 由该网元通知本 地网关建立无线侧网元与本地网关的隧道, 此外, 该网元向无线侧网元回应隧道建立 响应。 为了简化描述, 以上实施例仅以用户初始接入进行连接建立的情况为例来说明移 动决策信息的获取方式。
( 1 ) 对于多 PDN连接建立的情况下, 由本地网关向服务网关发送会话建立响应 (步骤 S308)、 以及服务网关向移动性管理实体发送会话建立响应消息 (步骤 S309) 中携带决策信息, 以便进行本地 IP访问的移动性管理。 其他流程与现有技术一致, 在 此不再赘述。
(2)对于服务请求过程, 由本地网关向服务网关发送修改承载响应(步骤 S410)、 以及服务网关向移动性管理实体发送修改承载响应消息(步骤 S411 )中携带决策信息, 便于进行本地 IP访问的移动性管理。 其他流程与现有技术一致, 在此不再赘述。 ( 3 ) 对于跟踪区更新过程, 由本地网关向服务网关发送修改承载响应 (步骤 S4a09)、 以及服务网关向移动性管理实体发送修改承载响应消息 (步骤 S4al0) 中携 带决策信息, 便于进行本地 IP访问的移动性管理。 其他流程与现有技术一致, 在此不 再赘述。 (4) 对于切换过程, 由本地网关向服务网关发送修改承载响应 (步骤 S4bl7)、 以及服务网关向移动性管理实体发送修改承载响应消息 (步骤 S4M8) 中携带决策信 息, 便于进行本地 IP访问的移动性管理。 其他流程与现有技术一致, 在此不再赘述。 图 9是根据本发明实施例的在图 1系统的基础上, 用户初始接入进行连接建立的 交互流程图四。 此时, 由鉴权授权服务器将决策信息传送给移动性管理实体。 本实施 例具体步骤描述如下: 步骤 S901 , 用户在进行通信前需要建立 RRC (Radio Resource Control, 无线资源 控制) 连接作为信令消息或者业务数据的承载。 步骤 S902, 用户发送初始化 NAS (Non-Access-Stratum, 非接入层) 消息进行附 着操作。 步骤 S903 , 无线侧网元将初始的用户消息发给移动性管理实体, 并转发 NAS消 息至移动性管理实体。 步骤 S904, 移动性管理实体开启鉴权以及安全流程, 对用户进行验证。 步骤 S905, 移动性管理实体请求 HSS进行位置更新。 步骤 S906, HSS向移动性管理实体回应位置更新响应, 携带决策信息。 步骤 S907, 移动性管理实体向 S-GW发送会话建立请求。 步骤 S908, 接收到移动性管理实体发送的消息, S-GW将会话建立请求消息发送 给 P-GW。 P-GW向 S-GW回复会话建立响应。 步骤 S909, S-GW向移动性管理实体发送会话建立响应。 步骤 S910, 移动性管理实体向无线侧网元发起初始上下文建立请求。 步骤 S911 , 执行 RRC连接配置过程。 步骤 S912, 无线侧网元回复移动性管理实体初始上下文建立响应。 步骤 S913, 终端向无线侧网元发送直传消息, 包括附着完成信息。 步骤 S914, 无线侧网元向移动性管理实体发送附着完成消息。 步骤 S915, 移动性管理实体向 S-GW请求更新承载。 步骤 S916, S-GW向 P-GW发送承载更新请求。 P-GW向 S-GW回应承载更新响 应。 步骤 S917, S-GW回应移动性管理实体承载更新响应消息。 步骤 S918至步骤 S919, 无线侧网元与本地网关之间进行隧道建立。 其中建立方 式可以为: 方法 (1 ), 无线侧网元向本地网关请求隧道建立, 本地网关回应无线侧网元隧道 建立响应。 方法 (2), 上述方法 (1 ) 中的消息经过安全网关传递。 方法 (3 ), 无线侧网元向与本地网关合设的网元请求隧道建立, 由该网元通知本 地网关建立无线侧网元与本地网关的隧道, 此外, 该网元向无线侧网元回应隧道建立 响应。 为了简化描述, 以上实施例仅以用户初始接入进行连接建立的情况为例来说明移 动决策信息的获取方式。 对于跟踪区更新过程, 在鉴权授权服务器向移动性管理实体 发送的位置更新响应 (步骤 S4all ) 中携带决策信息, 便于进行本地 IP访问的移动性 管理。 其他流程与现有技术一致, 在此不再赘述。 图 10是根据本发明实施例的在图 1系统的基础上,用户初始接入进行连接建立的 交互流程图五。 此时, 由 DNS服务器或网管系统将决策信息传送给移动性管理实体。 本实施例具体步骤描述如下: 步骤 S1001 , 用户在进行通信前需要建立 RRC (Radio Resource Control, 无线资 源控制) 连接作为信令消息或者业务数据的承载。 步骤 S1002, 用户发送初始化 NAS (Non-Access-Stratum, 非接入层)消息进行附 着操作。 步骤 S1003 , 无线侧网元将初始的用户消息发给移动性管理实体, 并转发 NAS消 息至移动性管理实体。 步骤 S1004, 移动性管理实体开启鉴权以及安全流程, 对用户进行验证。 步骤 S1005 , 移动性管理实体向 DNS服务器或网管系统查询决策信息, 带 APN 和 /或无线侧网元信息和 /或本地网关信息; 该步骤 S在步骤 S1003之后执行, 与步骤 S1003后续的步骤 S (即步骤 S1004、 步骤 S1007至步骤 S1019) 没有先后顺序。 步骤 S1006, DNS服务器或网管系统向移动性管理实体回应响应消息, 携带决策 信息。 步骤 S1007, 移动性管理实体向 S-GW发送会话建立请求。 步骤 S1008, 接收到移动性管理实体发送的消息, S-GW将会话建立请求消息发 送给 P-GW。 P-GW向 S-GW回复会话建立响应。 步骤 S1009, S-GW向移动性管理实体发送会话建立响应。 步骤 S1010, 移动性管理实体向无线侧网元发起初始上下文建立请求。 步骤 S 1011, 执行 RRC连接配置过程。 步骤 S1012, 无线侧网元回复移动性管理实体初始上下文建立响应。 步骤 S1013 , 终端向无线侧网元发送直传消息, 包括附着完成信息。 步骤 S1014, 无线侧网元向移动性管理实体发送附着完成消息。 步骤 S1015 , 移动性管理实体向 S-GW请求更新承载。 步骤 S1016, S-GW向 P-GW发送承载更新请求。 P-GW向 S-GW回应承载更新响 应。 步骤 S1017, S-GW回应移动性管理实体承载更新响应消息。 步骤 S1018至步骤 S1019, 无线侧网元与本地网关之间进行隧道建立。 其中建立 方式可以为: 方法 (1 ), 无线侧网元向本地网关请求隧道建立, 本地网关回应无线侧网元隧道 建立响应。 方法 (2), 上述方法 (1 ) 中的消息经过安全网关传递。 方法 (3 ), 无线侧网元向与本地网关合设的网元请求隧道建立, 由该网元通知本 地网关建立无线侧网元与本地网关的隧道, 此外, 该网元向无线侧网元回应隧道建立 响应。 为了简化描述, 以上实施例仅以用户初始接入进行连接建立的情况为例来说明移 动决策信息的获取方式。
( 1 )对于多 PDN连接建立的情况下,在移动性管理实体在步骤 S302之后增加与 DNS服务器或网管系统获取决策信息的消息 (类似步骤 S1005和步骤 S1006), 该步 骤在步骤 S302之后执行, 与步骤 S302后续的步骤没有先后顺序, 便于进行本地 IP 访问的移动性管理。 其他流程与现有技术一致, 在此不再赘述。
(2)对于服务请求过程,在移动性管理实体在步骤 S402之后增加与 DNS服务器 或网管系统获取决策信息的消息(类似步骤 S1005和步骤 S1006),该步骤在步骤 S402 之后执行, 与步骤 S402后续的步骤没有先后顺序, 便于进行本地 IP访问的移动性管 理。 其他流程与现有技术一致, 在此不再赘述。 (3 )对于跟踪区更新过程,在目标移动性管理实体在步骤 S4a01之后增加与 DNS 服务器或网管系统获取决策信息的消息(类似步骤 S1005和步骤 S1006), 该步骤在步 骤 S4a01之后执行, 与步骤 S4a01后续的步骤没有先后顺序, 便于进行本地 IP访问的 移动性管理。 其他流程与现有技术一致, 在此不再赘述。
(4) 对于切换过程, 在目标移动性管理实体重定位前转请求消息 (步骤 S4b03 ) 之后增加与 DNS 服务器或网管系统获取决策信息的消息 (类似步骤 S1005 和步骤 S1006), 该消息与切换过程步骤 S4b03后其他消息的执行没有先后顺序, 便于进行本 地 IP访问的移动性管理。 其他流程与现有技术一致, 在此不再赘述。 图 11是根据本发明实施例的在图 1系统的基础上,终端进行切换过程的交互流程 图一, 该实施例中由目标移动性管理实体进行判断是否支持移动性, 具体步骤描述如 下: 步骤 S1101 , 无线侧网元判断需要发起 S1切换。 步骤 S1102, 原无线侧网元向原移动性管理实体发送切换请求, 携带目标 CSG或 LHN标识。 步骤 S1103 , 原移动性管理实体向目标移动性管理实体发送重定位前转请求消息, 可以携带决策信息。 步骤 S1104, 目标移动性管理实体判断是否支持移动性。 判断是否支持移动性的 方法为:如果初始或原 CSG或 LHN属于支持移动性的决策信息中,或者初始或原 CSG 或 LHN和目标 CSG或 LHN属于支持移动性的 CSG或 LHN列表,则目标移动性管理 实体认为支持移动性。 如果初始或原 CSG或 LHN和目标 CSG或 LHN标识相同, 则 目标移动性管理实体认为支持移动性。如果支持移动性,则激活 /建立 /更新核心网连接 和本地 IP访问连接;否则,则仅仅激活 /建立 /更新核心网连接,释放本地 IP访问连接。 步骤 S1105, 如果不支持移动性, 则目标移动性管理实体向核心网网关发起核心 网连接的会话建立、 转发隧道建立流程, 无需建立本地 IP访问连接信息。 步骤 S1106, 目标移动性管理实体请求目标无线侧网元执行切换, 携带核心网连 接的承载信息, 而不带本地 IP访问连接信息。 步骤 S1107, 目标无线侧网元向目标移动性管理实体回应切换请求确认消息。 步骤 S1108, 继续正常的切换流程。 其中目标移动性管理实体向原移动性管理实 体发送的重定位前转完成消息中携带本地 IP访问失效的指示信息。 步骤 S1109, 可选地, 如果在步骤 1108中获取了本地 IP访问失效的指示信息, 则原移动性管理实体向原本地接入网关发起本地 IP访问连接的删除流程。 步骤 S1110, 或者, 可选地, 目标移动性管理实体发起本地 IP访问连接的释放流 程, 该步骤可以在步骤 S1104后执行。 图 11a是根据本发明实施例的在图 1系统的基础上, 终端进行切换过程的交互流 程图二, 该实施例中由目标移动性管理实体进行判断是否支持移动性, 具体步骤描述 如下: 步骤 SllaOl , 无线侧网元判断需要发起 S1切换。 步骤 Slla02, 原无线侧网元向原移动性管理实体发送切换请求。 步骤 Slla03, 原移动性管理实体在向目标移动性管理实体发送的重定位前转请求 消息, 可选携带决策信息。 步骤 Slla04, 目标移动性管理实体可以向核心网网关发起核心网和本地 IP访问 连接的会话建立流程。 步骤 Slla05, 目标移动性管理实体请求目标无线侧网元执行切换。 步骤 Slla06, 目标无线侧网元向目标移动性管理实体回应切换请求确认消息。 步骤 Slla07, 目标移动性管理实体根据决策信息判断是否支持移动性。 判断是否 支持移动性的方法为: 如果初始或原 CSG或 LHN属于支持移动性的决策信息中, 或 者初始或原 CSG或 LHN和目标 CSG或 LHN属于支持移动性的 CSG或 LHN列表, 则目标移动性管理实体认为支持移动性。 如果初始或原 CSG或 LHN和目标 CSG或 LHN标识相同, 则目标移动性管理实体认为支持移动性。 如果支持移动性, 则激活 / 建立 /更新核心网连接和本地 IP访问连接; 否则, 则仅仅激活 /建立 /更新核心网连接, 释放本地 IP访问连接。 步骤 Slla08, 目标移动性管理实体向原移动性管理实体发送重定位前转响应消 息。 若不支持移动性, 则在消息中携带本地 IP访问连接无效的指示。 步骤 Slla09, 原移动性管理实体向原无线侧网元发送切换命令。 如果不支持移动 性, 则该切换命令中携带需释放的承载信息包括本地 IP访问连接的承载信息。 步骤 SllalO, 继续正常的切换流程。 步骤 Sllal l , 如果不支持移动性, 原移动性管理实体向原本地网关发起本地 IP 访问连接的删除流程。 该步骤可以在步骤 Slla08后执行。 步骤 Sllal2, 如果不支持移动性, 则目标移动性管理实体向目标无线侧网元发起 本地 IP访问连接承载的删除流程。 该步骤可以在步骤 Slla07执行。 图 12是根据本发明实施例的在图 1系统的基础上,终端进行切换过程的交互流程 图三, 该实施例中由原移动性管理实体判断是否支持移动性, 具体步骤描述如下: 步骤 S1201 , 无线侧网元判断需要发起 S1切换。 步骤 S1202, 原无线侧网元向原移动性管理实体发送切换请求。 步骤 S1203 , 原移动性管理实体判断是否支持移动性。 判断是否支持移动性的方 法为: 如果初始或原 CSG或 LHN属于支持移动性的决策信息中, 或者初始或原 CSG 或 LHN和目标 CSG或 LHN属于支持移动性的 CSG或 LHN列表,则原移动性管理实 体认为支持移动性。 如果初始或原 CSG或 LHN和目标 CSG或 LHN标识相同, 则原 移动性管理实体认为支持移动性。如果支持移动性,则激活 /建立 /更新核心网连接和本 地 IP访问连接; 否则, 则仅仅激活 /建立 /更新核心网连接, 释放本地 IP访问连接。 步骤 S1204, 原移动性管理实体在向目标移动性管理实体发送的重定位前转请求 消息。 如果不支持移动性, 则该消息中不携带本地 IP访问连接的承载信息。 步骤 S1205, 目标移动性管理实体可以向核心网网关发起核心网连接的会话建立
步骤 S1206, 目标移动性管理实体请求目标无线侧网元执行切换。 步骤 S1207, 目标无线侧网元向目标移动性管理实体回应切换请求确认消息。 步骤 S1208, 继续正常的切换流程。 步骤 S1209, 如果不支持移动性, 原移动性管理实体向原本地网关发起本地 IP访 问连接的删除流程。 该步骤可以在步骤 S1203后执行。 图 13是根据本发明实施例的在图 1系统的基础上,提供的终端由空闲态转为连接 态时进行服务请求过程、移动性管理实体进行移动性判断的交互流程图,如图 13所示, 具体步骤描述如下: 步骤 S1301 , 终端接入无线通信系统后具有本地 IP访问连接和核心网连接, 此后 终端进入空闲态。 步骤 S1302, 终端经无线侧网元向移动性管理实体发送服务请求消息。 步骤 S1303 , 执行 NAS (Non-Access-Stratum, 非接入层)认证过程, 该步骤可选。 步骤 S1304, 移动性管理实体判断是否支持移动性。 判断是否支持移动性的方法 为: 如果初始或原 CSG或 LHN属于支持移动性的决策信息中, 或者初始或原 CSG或 LHN和目标 CSG或 LHN属于支持移动性的 CSG或 LHN列表,则移动性管理实体认 为支持移动性。 如果初始或原 CSG或 LHN和目标 CSG或 LHN标识相同, 则移动性 管理实体认为支持移动性。 如果支持移动性, 则激活 /建立 /更新核心网连接和本地 IP 访问连接; 否则, 则仅仅激活 /建立 /更新核心网连接, 释放本地 IP访问连接。 步骤 S1305, 移动性管理实体向无线侧网元发送初始上下文建立请求消息。 如果不支持移动性, 则该消息携带核心网连接的承载信息, 而不携带本地 IP访问 连接的承载信息。 如果支持移动性, 则该消息携带核心网连接以及本地 IP访问连接的承载信息。 步骤 S1306, 无线侧网元执行无线承载建立过程。 步骤 S1307, 无线侧网元回应移动性管理实体初始上下文建立完成消息。 步骤 S1308, 如果不支持移动性, 则移动性管理实体与本地网关执行本地 IP访问 连接的承载释放过程。如果支持移动性, 则移动性管理实体与本地网关执行本地 IP访 问连接的承载修改操作。 图 14是根据本发明实施例的在图 1系统的基础上,提供的终端进行位置更新过程 的交互流程图一。 该实施例中由目标移动性管理实体进行判断是否支持移动性。 具体 步骤描述如下: 步骤 S1401 ,终端经目标无线侧网元向移动性管理实体发送跟踪区更新请求消息, 携带激活标识。 步骤 S1402, 目标移动性管理实体向原移动性管理实体发送上下文请求消息。 步骤 S1403 ,原移动性管理实体向目标移动性管理实体发送的上下文应答消息中, 可选携带决策信息。 步骤 S1404, 可选地, 终端、 移动性管理实体、 鉴权授权服务器执行认证过程。 步骤 S1405, 目标移动性管理实体判断是否支持移动性。 判断是否支持移动性的 方法为:如果初始或原 CSG或 LHN属于支持移动性的决策信息中,或者初始或原 CSG 或 LHN和目标 CSG或 LHN属于支持移动性的 CSG或 LHN列表,则目标移动性管理 实体认为支持移动性。 如果初始或原 CSG或 LHN和目标 CSG或 LHN标识相同, 则 目标移动性管理实体认为支持移动性。如果支持移动性,则激活 /建立 /更新核心网连接 和本地 IP访问连接;否则,则仅仅激活 /建立 /更新核心网连接,释放本地 IP访问连接。 步骤 S1406, 如果不支持移动性, 目标移动性管理实体向原移动性管理实体发送 的上下文确认消息中可以携带本地 IP访问失效指示信息。 步骤 S1407, 目标移动性管理实体向核心网 S-GW发起承载修改操作, 不需要修 改本地 IP访问连接的信息。 步骤 S1408, 目标移动性管理实体与鉴权授权服务器之间执行位置更新流程。 步骤 S1409, 鉴权授权服务器与原移动性管理实体之间执行位置取消过程。 步骤 S1410, 目标移动性管理实体向目标无线侧网元发送初始上下文建立请求消 息, 携带核心网连接信息, 而不带本地 IP访问连接信息。 步骤 S1411 , 目标无线侧网元执行无线承载建立过程。 步骤 S1412, 目标无线侧网元回应移动性管理实体初始上下文建立完成 /无线承载 建立完成消息。 步骤 S1413 , 移动性管理实体请求核心网 S-GW进行承载修改, 以便激活 /建立终 端的核心网连接; 核心网 S-GW向移动性管理实体发送承载修改响应消息。 可选地, 核心网 S-GW向核心网 P-GW发送承载修改请求消息。 步骤 S1414, 可选地, 目标移动性管理实体发起本地 IP访问连接的释放流程。 步骤 S1415, 或者, 可选地, 原移动性管理实体在获取步骤 S1406中本地 IP访问 失效指示信息后, 发起本地 IP访问连接的释放流程。 其中步骤 S1414可以在步骤 S1405之后执行。 图 15是根据本发明实施例的在图 1系统的基础上,提供的终端进行位置更新过程 的交互流程图二。 该实施例中由原移动性管理实体进行判断是否支持移动性。 具体步 骤描述如下: 步骤 S1501 ,终端经目标无线侧网元向移动性管理实体发送跟踪区更新请求消息, 携带激活标识。 步骤 S1502, 目标移动性管理实体向原移动性管理实体发送上下文请求消息。 步骤 S1503 , 原移动性管理实体判断是否支持移动性。 判断是否支持移动性的方 法为: 如果初始或原 CSG或 LHN属于支持移动性的决策信息中, 或者初始或原 CSG 或 LHN和目标 CSG或 LHN属于支持移动性的 CSG或 LHN列表,则原移动性管理实 体认为支持移动性。 如果初始或原 CSG或 LHN和目标 CSG或 LHN标识相同, 则原 移动性管理实体认为支持移动性。如果支持移动性,则激活 /建立 /更新核心网连接和本 地 IP访问连接; 否则, 则仅仅激活 /建立 /更新核心网连接, 释放本地 IP访问连接。 步骤 S1504, 如果不支持移动性, 则原移动性管理实体向目标移动性管理实体发 送的上下文应答消息中携带核心网连接信息, 不带本地 IP访问连接信息。 S1505, 可选地, 终端、 移动性管理实体、 鉴权授权服务器执行认证过程。 S1506, 目标移动性管理实体向原移动性管理实体发送上下文确认消息。 S1507, 目标移动性管理实体向核心网 S-GW发起承载修改操作。
Figure imgf000029_0001
S1508, 目标移动性管理实体与鉴权授权服务器之间执行位置更新流程。 步骤 S1509, 鉴权授权服务器与原移动性管理实体之间执行位置取消过程。 步骤 S1510, 目标移动性管理实体向目标无线侧网元发送初始上下文建立请求消
步骤 S1511 , 目标无线侧网元执行无线承载建立过程。 步骤 S1512, 目标无线侧网元回应移动性管理实体初始上下文建立完成 /无线承载 建立完成消息。 步骤 S1513 , 移动性管理实体请求核心网 S-GW进行承载修改, 以便激活 /建立终 端的核心网连接; 核心网 S-GW向移动性管理实体发送承载修改响应消息。 可选地, 核心网 S-GW向核心网 P-GW发送承载修改请求消息。 步骤 S1514, 原移动性管理实体发起本地 IP访问连接的释放流程。 其中步骤 S1514可以在步骤 S1503之后执行。 以上所有实施例中, 除了以上决策信息获取方式以外, 无线侧网元或本地网关还 可以在上电时将决策信息发送给移动性管理实体,便于在移动过程中进行移动性判断。 决策信息是指 CSG或 LHN信息, 如 CSG列表或 CSG组或 CSG名或 LHN名或
LHN标识, 可以用于判断是否保持移动性或业务连续性。 无线侧网元信息包括: 无线 侧网元标识、 无线侧网元地址、 无线侧网元 ID。 本地网关信息包括: 本地网关标识、 本地网关地址、 本地网关 ID。 上述图 11至图 15所示移动性管理流程中, 在移动性管理实体执行移动性判断之 前, 可以通过图 6至图 10所示的各种流程获取决策信息。 如果本地 IP访问和核心网连接采用同一个服务网关,则该服务网关既是本地服务 网关, 又是核心网服务网关。 为了简化描述, 以上实施例仅以图 1的情况为例来说明本地 IP访问连接的管理方 式。 在其他情况下 (例如, UTRAN系统、 存在家用基站网关的情况下), 仍然需要移 动性管理实体如上述多种方式获取决策信息并据此判断是否支持移动性, 便于进行本 地 IP访问的连接管理。在这些情况下,对决策信息的获取方式与上述实施例极为相似, 不会对阐述本发明造成影响, 故在此不再重复描述。 无线侧网元可以是基站、家用基站、家用基站网关、 RNC (无线网络控制器, Radio Network Controller ) 数据分流功能实体。 移动性管理实体可以为 MME (移动管理单 元, Mobility Management Entity ) MSC (移动交换中心, Mobile Switching Centre )、 SGSN (服务 GPRS支持节点, Serving GPRS Support Node)、 家用基站网关。 本地网 关可以是 L-SGW和 L-PGW, 可以是单独的 L-PGW, 可以是 L-GGSN和 L-SGSN, 可 以是单独的 L-GGSN,可以是数据分流功能实体。核心网接入网关可以是 S-GW、P-GW、 SGSN、 GGSN。 服务网关包括本地服务网关或 /和核心网服务网关,接入网关包括本地接入网关或
/和核心网接入网关。 本地服务网关可以是 L-SGW或 L-SGSN或 L-GW。 核心网服务 网关可以是 S-GW或 SGSN。 本地网关可以是本地接入网关和 /或本地服务网关。 本地 接入网关可以是 L-PGW或 L-GGSN或 L-GW。核心网接入网关可以是 S-GW、 P-GW、 SGSN、 GGSN。核心网网关可以是核心网接入网关和 /或核心网服务网关。服务网关可 以是本地服务网关, 也可以是核心网服务网关。 本地 IP访问的无线侧网元可以与本地网关地址相同。 鉴权授权服务器可以是用户签约数据库。 位置更新可以是跟踪区更新、 路由区更新。 本地 IP访问可以是本地 IP访问用户本地网络、 本地 IP访问公司本地网络、 本地 IP访问互联网、 互联网业务的分流操作、 特定 IP数据分流。 用户的初始 CSG或 LHN标识指该用户初始建立本地 IP访问连接时的 CSG或 LHN 标识。 需要说明的是, 在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的 计算机系统中执行, 并且, 虽然在流程图中示出了逻辑顺序, 但是在某些情况下, 可 以以不同于此处的顺序执行所示出或描述的步骤。 需要说明的是, 在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的 计算机系统中执行, 并且, 虽然在流程图中示出了逻辑顺序, 但是在某些情况下, 可 以以不同于此处的顺序执行所示出或描述的步骤。 本发明实施例提供了一种本地 IP访问连接的处理装置, 该本地 IP访问连接的处 理装置可以应用于移动性管理实体,该本地 IP访问连接的处理装置可以用于实现上述 本地 IP访问连接的处理方法。 图 16是根据本发明实施例的本地 IP访问连接的处理装 置的结构框图, 如图 16所示, 包括接收模块 162和判断模块 164。 下面对其结构进行 详细描述。 接收模块 162, 设置为在建立本地 IP访问连接的过程中, 接收移动决策信息; 判 断模块 164, 连接至接收模块 162, 设置为根据接收模块 162接收的移动决策信息, 判 断本地 IP访问连接是否支持移动性。 需要说明的是,装置实施例中描述的本地 IP访问连接的处理装置对应于上述的方 法实施例, 其具体的实现过程在方法实施例中已经进行过详细说明, 在此不再赘述。 综上所述, 根据本发明的上述实施例, 提供了一种本地 IP访问连接的处理方法及 装置。 通过本发明, 移动决策信息通过外部配置, 并由移动性管理实体接收, 从而可 实现 IP分流系统的灵活处理性能, 提升系统可操作性。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 或者将它们分别制作成各个集成电路模 块, 或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明 不限制于任何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技 术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的 任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。

Claims

权 利 要 求 书
1. 一种本地 IP访问连接的处理方法, 包括:
在建立本地 IP访问连接的过程中, 移动性管理实体接收到移动决策信息; 所述移动性管理实体根据所述移动决策信息,判断所述本地 IP访问连接是 否支持移动性。
2. 根据权利要求 1所述的方法,其中,移动性管理实体接收到移动决策信息包括: 所述移动性管理实体接收到无线侧网元发送的所述移动决策信息, 其中所述无 线侧网元包括以下之一: 基站、 家用基站、 家用基站网关、 无线网络控制器、 数据分流功能实体。
3. 根据权利要求 1所述的方法,其中,移动性管理实体接收到移动决策信息包括: 所述移动性管理实体接收到本地网关发送的所述移动决策信息, 其中所述本地 网关是本地接入网关和 /或本地服务网关, 所述本地接入网关包括以下之一: 本 地分组数据网络网关 L-PGW、 本地网关通用分组无线业务支持节点 L-GGSN、 本地网关 L-GW, 所述本地服务网关是以下之一: L-SGW、 本地服务通用分组 无线业务支撑节点 L-SGSN、 L-GW。
4. 根据权利要求 3所述的方法, 其中, 所述移动性管理实体接收到本地网关发送 的所述移动决策信息包括以下之一:
所述移动性管理实体接收到本地网关经由无线侧网元发送的所述移动决策 信息, 其中所述无线侧网元包括以下之一: 基站、 家用基站、 家用基站网关、 无线网络控制器、 数据分流功能实体;
所述移动性管理实体接收到本地网关经由服务网关发送的所述移动决策信 息, 其中所述服务网关是本地服务网关和 /或核心网服务网关, 所述本地服务网 关是以下之一: L-SGW L-SGSN L-GW, 所述核心网服务网关包括以下之一: S-GW、 SGSN。
5. 根据权利要求 1所述的方法,其中,移动性管理实体接收到移动决策信息包括: 所述移动性管理实体接收到 DNS服务器或网管系统发送的所述移动决策信息。
6. 根据权利要求 1所述的方法,其中,移动性管理实体接收到移动决策信息包括: 所述移动性管理实体接收到鉴权授权服务器发送的所述移动决策信息。
7. 根据权利要求 1至 6中任一项所述的方法, 其中, 所述本地 IP访问连接包括以 下之一: 本地 IP访问用户本地网络、 本地 IP访问公司本地网络、 本地 IP访问 互联网、 互联网业务的分流操作、 特定 IP数据分流。
8. 根据权利要求 1至 6中任一项所述的方法, 其中, 所述移动性管理实体包括以 下之一: 移动管理单元、 移动交换中心、 服务通用分组无线业务支持节点、 家 用基站网关。
9. 根据权利要求 1至 6中任一项所述的方法, 其中, 所述移动决策信息包括以下 至少之一: 闭合用户组 CSG列表、 CSG组、 CSG名。
10. 根据权利要求 9所述的方法, 其中, 所述移动决策信息还包括以下至少之一: 本地家用基站网络 LHN名、 LHN标识。
11. 一种本地 IP访问连接的处理装置, 应用于移动性管理实体, 包括:
接收模块, 设置为在建立本地 IP访问连接的过程中, 接收移动决策信息; 判断模块, 设置为根据所述移动决策信息, 判断所述本地 IP访问连接是否 支持移动性。
PCT/CN2012/071176 2011-03-24 2012-02-15 本地ip访问连接的处理方法及装置 WO2012126298A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110072609.6 2011-03-24
CN2011100726096A CN102695159A (zh) 2011-03-24 2011-03-24 本地ip访问连接的处理方法及装置

Publications (1)

Publication Number Publication Date
WO2012126298A1 true WO2012126298A1 (zh) 2012-09-27

Family

ID=46860410

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/071176 WO2012126298A1 (zh) 2011-03-24 2012-02-15 本地ip访问连接的处理方法及装置

Country Status (2)

Country Link
CN (1) CN102695159A (zh)
WO (1) WO2012126298A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103813397B (zh) * 2012-11-12 2019-02-15 中兴通讯股份有限公司 管理分流连接的方法、无线侧网元及移动性管理实体

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101803329A (zh) * 2007-07-10 2010-08-11 松下电器产业株式会社 移动节点中实施的移动性功能的检测
CN101990192A (zh) * 2009-07-30 2011-03-23 中兴通讯股份有限公司 本地ip访问连接属性的通知方法与装置
CN101990321A (zh) * 2009-08-03 2011-03-23 中兴通讯股份有限公司 一种本地ip访问接入控制的方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101803329A (zh) * 2007-07-10 2010-08-11 松下电器产业株式会社 移动节点中实施的移动性功能的检测
CN101990192A (zh) * 2009-07-30 2011-03-23 中兴通讯股份有限公司 本地ip访问连接属性的通知方法与装置
CN101990321A (zh) * 2009-08-03 2011-03-23 中兴通讯股份有限公司 一种本地ip访问接入控制的方法及系统

Also Published As

Publication number Publication date
CN102695159A (zh) 2012-09-26

Similar Documents

Publication Publication Date Title
EP3694254B1 (en) Handover method in wireless communication system and apparatus therefor
JP7074759B2 (ja) ネットワーク・ハンドオーバー方法および関係した装置
JP7330200B2 (ja) ハンドオーバ方法および装置
US10015718B2 (en) Method, apparatus, and system for routing user plane data in mobile network
EP2391067B1 (en) Methods and apparatuses for forwarding data in case of a handover between GERAN/UTRAN systems using the Direct Tunnel solution
EP3310100A1 (en) Wireless communications access method, communications device, wireless terminal and system
US8842636B2 (en) Method and device for managing Internet Protocol offload connection
EP2498468A1 (en) Method for managing local internet protocol (ip) access connections
EP2582175A1 (en) Method, device and system for setting maximum bandwidth
WO2012034468A1 (zh) 重启移动性管理单元的处理方法及移动性管理单元
WO2011054294A1 (zh) 连接建立方法和装置
EP4192106A1 (en) Communication method and apparatus
WO2014194457A1 (zh) 一种无默认承载的切换方法和设备
WO2010133107A1 (zh) 家用基站网关转发消息至家用基站的方法及系统
WO2013029245A1 (zh) 一种承载的处理方法、系统及装置
WO2013004121A1 (zh) 本地网关信息处理方法及装置
EP2571302A1 (en) Method, apparatus and system for processing local address in shunt connection
WO2012075907A1 (zh) 数据分流方法及本地网关
WO2012174976A1 (zh) Ip分流连接处理方法、装置及系统
WO2012126298A1 (zh) 本地ip访问连接的处理方法及装置
WO2012068935A1 (zh) 网关重定位方法和源分流网关
WO2023246620A1 (zh) 通信方法、装置和系统
WO2023226647A1 (zh) 数据传输方法、网络设备及计算机可读存储介质
WO2013000352A1 (zh) Ip数据计费方法及装置
WO2010012241A1 (zh) 进行信息交互的方法及存储用户签约数据的节点

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12760737

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12760737

Country of ref document: EP

Kind code of ref document: A1