WO2011006404A1 - 本地ip访问连接建立的实现方法及*** - Google Patents

本地ip访问连接建立的实现方法及*** Download PDF

Info

Publication number
WO2011006404A1
WO2011006404A1 PCT/CN2010/073776 CN2010073776W WO2011006404A1 WO 2011006404 A1 WO2011006404 A1 WO 2011006404A1 CN 2010073776 W CN2010073776 W CN 2010073776W WO 2011006404 A1 WO2011006404 A1 WO 2011006404A1
Authority
WO
WIPO (PCT)
Prior art keywords
connection
bearer
local
gateway
access gateway
Prior art date
Application number
PCT/CN2010/073776
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 WO2011006404A1 publication Critical patent/WO2011006404A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a method and system for implementing local IP access connection establishment.
  • the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) Evolved Packet System is an Evolved Universal Mobile Telecommunications System Terrestrial Radio (Evolved Universal Mobile Telecommunications System Terrestrial Radio) Access Network (referred to as E-UTRAN), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P) -GW or PDN GW), Home Subscriber Server (HSS), 3GPP Authenticated Authorization and Accounting (AAA) server, Policy and Charging Rules (Policy and Charging)
  • PCRF Policy and Charging Rules
  • PCRF Policy and Charging Rules Function
  • the MME is responsible for control planes such as mobility management, non-access stratum signaling processing, and user mobility management context management
  • the S-GW is an access gateway device connected to the E-UTRAN. Forwarding data between E-UTRAN and P-GW, and responsible for buffering paging waiting data
  • P-GW is the border gateway between EPS and Packet Data Network (PDN), responsible for PDN access and forwarding of data between the EPS and the PDN
  • the PCRF is a policy and charging rule function entity, which is connected to the service network protocol (Internet Protocol, IP for short) service network through the receiving interface Rx to obtain service information.
  • the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the establishment of the IP bearer, ensuring the Quality of Service (QoS) of the service data, and performing charging control.
  • QoS Quality of Service
  • the home base station is a small, low-power base station deployed in indoor places such as homes and offices. Its main role is to provide users with higher service rates and reduce the cost of using high-rate services, while making up for the lack of coverage of existing distributed cellular wireless communication systems.
  • the advantages of home base stations are affordable, convenient, low power output, plug and play, and more.
  • the home base station can be directly connected to the core network, or can be accessed to the core network through the logical base unit of the home base station gateway, as shown in FIG.
  • the main functions of the home base station gateway are: verifying the security of the home base station, handling the registration of the home base station, performing operation and maintenance management on the home base station, configuring and controlling the home base station according to the operator's requirements, and exchanging data of the core network and the home base station.
  • the access gateway may be an S-GW (Serving Gateway), a P-GW (Packet Data Network Gateway), an SGSN (Serving GPRS Support Node), and a Serving GPRS Support Node.
  • GGSN Gateway GPRS Support Node
  • L-SGW Local SGW
  • L-PGW Local PGW
  • V-SGW Virtual SGW
  • V-PGW Virtual PGW
  • L-GGSN Local GGSN, Local GGSN
  • the local access gateway can be combined with the wireless side entity or the home base station gateway. It can also be set near the wireless side entity or the home base station gateway.
  • mobile communication systems can also support local IP access functions to enable local access to other IP devices or the Internet in the home network.
  • FIG. 2 is a flow chart of a process for establishing a local IP access connection when a user initially accesses on the basis of the home base station system of FIG. 1, and the specific steps are as follows:
  • Step 201 The user establishes an RRC (Radio Resource Control) connection as a bearer of signaling messages or service data before performing communication;
  • RRC Radio Resource Control
  • Step 202 The user sends an Initialization NAS (Non-Access-Stratume, Non-Access Layer) message to perform an attach operation.
  • Initialization NAS Non-Access-Stratume, Non-Access Layer
  • Step 203 The wireless side entity sends an initial user message to the mobility management entity, and forwards the message.
  • Step 204 The mobility management entity starts an authentication and a security process to authenticate the user.
  • Step 205 The mobility management entity according to an APN (Access Point Name) Or a local access identifier (which may be carried in the message in step 203), after discovering that a local IP access connection needs to be established, sending a session establishment request to the L-SGW;
  • APN Access Point Name
  • a local access identifier which may be carried in the message in step 203
  • Step 206 Receive a request message sent by the mobility management entity, and the L-SGW sends a session establishment request message to the L-PGW.
  • Step 207 The L-PGW returns a session establishment response to the L-SGW.
  • Step 208 The L-SGW sends a session establishment response to the mobility management entity.
  • Step 209 The mobility management entity initiates an initial context setup request to the home base station.
  • Step 210 Perform an RRC connection configuration process.
  • Step 211 The home base station returns an initial context establishment response to the mobility management entity.
  • Step 214 The mobility management entity sends a bearer update request to the L-SGW, and carries the address of the wireless side entity and the tunnel identifier of the wireless side entity.
  • Step 215 this step is optional. If the handover indication is carried in step 214, the L-SGW sends a bearer update request to the L-PGW.
  • Step 216 this step is optional.
  • the L-PGW returns a bearer update response to the L-SGW.
  • Step 217 The L-SGW returns a bearer update response to the mobility management entity.
  • the technical problem to be solved by the present invention is to provide a method and system for implementing local IP access connection establishment, which effectively implements a mechanism for creating two data tunnels.
  • the present invention provides a method for implementing local IP access connection establishment, which includes the following steps:
  • the mobility management device initiates a primary connection establishment and notifies the local access gateway of the primary connection information; the path of the primary connection is from the terminal to the wireless side entity to the local access gateway;
  • the mobility management device initiates a secondary connection establishment in association, and notifies the secondary access gateway of the secondary connection information; the secondary connection path is from the core network access gateway to the local access gateway.
  • the primary connection and the secondary connection information include a bearer identifier and a bearer status, where the primary connection and the secondary connection are associated by using the same bearer identifier or by using a dedicated association identifier, where the bearer status is active or idle. Or use a primary or secondary connection.
  • the step of initiating a primary connection establishment and notifying the local access gateway of the primary connection information, and the step of initiating the secondary connection establishment and notifying the local access gateway of the secondary connection information are performed in parallel, and Before the step of initiating the establishment of the primary connection, the method further includes: determining, by the mobility management device, that a local IP access connection needs to be established according to the access point name (APN) or the local access identifier.
  • APN access point name
  • the method further includes: the local access gateway selecting a correct bearer for the downlink data according to the primary connection and the secondary connection information, and forwarding; and the local access gateway modifying or releasing the primary connection and the secondary connection in association with each other.
  • the wireless side entity is a base station or a home base station;
  • the mobility management device is a mobility management entity (MME);
  • the local access gateway comprises a local service gateway (L-SGW) and a local packet data network gateway. (L-PGW);
  • the core network access gateway is a serving gateway (S-GW);
  • the step of the MME initiating a primary connection establishment and notifying the local access gateway of the primary connection information includes:
  • the L-SGW After receiving the message sent by the MME, the L-SGW sends the session establishment request message to the L-PGW together with the indication of the bearer as the primary connection, where the L-SGW saves the indication that the bearer is the primary connection;
  • the L-PGW After receiving the request message, the L-PGW returns a session establishment response to the L-SGW, and identifies the bearer as the primary connection according to the indication in the request message;
  • the step of the MME initiating a secondary connection establishment and notifying the local access gateway of the secondary connection information includes:
  • the MME Sending, by the MME, a session establishment request message to the S-GW, and indicating in the message that the bearer corresponding to the session is a secondary connection and the bearer identifier allocated by the MME for the bearer;
  • the bearer identifier assigned to the MME is the same as the bearer identifier, or the bearer identifier allocated by the MME for the secondary connection is different from the bearer identifier allocated by the MME as the primary connection, but the direction is directed to the L-SGW or S.
  • the session establishment request message sent by the GW carries the dedicated association identifier of the ⁇ allocation;
  • the S-GW After receiving the message sent by the UI, the S-GW sends the session establishment request message to the L-PGW together with the indication that the bearer is a secondary connection, and the S-GW saves the bearer as a secondary connection indication;
  • the L-PGW After receiving the request message, the L-PGW returns a session establishment response to the S-GW, and identifies the bearer as a secondary connection according to an indication in the request message;
  • the S-GW sends a session establishment response to the UI.
  • the wireless side entity is a base station, a home base station or a radio network controller (RNC); the mobility management device and the core network access gateway are serving a general packet radio service (GPRS) support node (SGSN);
  • GPRS general packet radio service
  • the local access gateway is a local gateway GPRS support node (L-GGSN);
  • the step of the SGSN initiating a primary connection establishment and notifying the L-GGSN of the primary connection information includes: the SGSN sending a PDP to the L-GGSN Context establishing a request message, and indicating in the message that the bearer corresponding to the PDP context is a primary connection and a corresponding bearer identifier;
  • the L-GGSN After receiving the request message sent by the SGSN, the L-GGSN returns to the SGSN.
  • the PDP context establishes a response, and identifies the bearer as the primary connection according to the indication in the request message; performs a radio access bearer establishment process;
  • the SGSN returns a PDP context activation accept message to the terminal;
  • the step of the SGSN initiating the secondary connection establishment and notifying the L-GGSN of the secondary connection information includes:
  • the SGSN sends a PDP context setup request message to the L-GGSN, and indicates in the message that the bearer corresponding to the PDP context is a secondary connection and a corresponding bearer identifier; the bearer identifier corresponding to the secondary connection corresponds to the primary connection
  • the bearer identifier is the same, or the bearer identifier corresponding to the secondary connection is different from the bearer identifier corresponding to the primary connection, but at least one of the PDP context setup request messages sent by the SGSN to the L-GGSN is carried.
  • the L-GGSN After receiving the request message, the L-GGSN returns a PDP context setup response to the SGSN, and identifies the bearer as a secondary connection according to the indication in the request message.
  • the present invention also provides an implementation system for establishing a local IP access connection, including a mobility management device and a local access gateway, where:
  • the mobility management apparatus is configured to initiate a primary connection and a secondary connection establishment and notify the local access gateway of the primary connection and the secondary connection information in association with each other; the path of the primary connection is from the terminal to the wireless side entity to the office.
  • the local access gateway, the path of the secondary connection is from a core network access gateway to the local access gateway;
  • the local access gateway is configured to create a primary connection and a secondary connection and save the primary connection and the secondary connection information.
  • the primary connection and the secondary connection information include a bearer identifier and a bearer status, where the primary connection and the secondary connection are associated by using the same bearer identifier or by using a dedicated association identifier, where the bearer status is active or idle. Or use a primary or secondary connection.
  • the local access gateway is further configured to select a correct bearer and forward the downlink data according to the primary connection and the secondary connection information, and modify or release the primary connection and the secondary connection in association.
  • the system further includes the core network access gateway, configured to create a secondary connection and ensure Save the connection information.
  • the core network access gateway configured to create a secondary connection and ensure Save the connection information.
  • the wireless side entity is a base station, a home base station, and a radio network controller (RNC);
  • the mobility management apparatus is a mobility management entity (MME), a mobile switching center (MSC), or a serving general packet radio service (GPRS) Support Node (SGSN);
  • the local access gateway includes a Local Serving Gateway (L-SGW) and a Local Packet Data Network Gateway (L-PGW), or a Local Gateway GPRS Support Node (L-GGSN);
  • the access gateway is the Serving Gateway (S-GW) or SGSN 0
  • the present invention provides a technical solution for simultaneously establishing two data tunnels for local IP access, wherein the core network mobility management device (eg, MME, SGSN) identifies the tunnel as the primary connection when creating the first data tunnel. And at the same time, the second data tunnel is established, and the identifier is a secondary connection, so that the local access gateway can simultaneously save two data tunnel information, and can accurately select the tunnel used by the data flow, thereby solving the problem of local IP access at the same time.
  • the problem of establishing multiple connections effectively implements the creation mechanism of two data tunnels.
  • FIG. 1 is a schematic diagram of a connection of a mobile communication network in the prior art
  • FIG. 2 is a flow chart of establishing a local IP connection when a user initially accesses in the prior art
  • FIG. 3a is a schematic diagram of local IP access data flow in an LTE mobile communication system according to the present invention
  • FIG. 3b is a schematic diagram of local IP access data flow in a UTRAN mobile communication system according to the present invention
  • FIG. 4 is a method for implementing local IP access connection establishment according to the present invention
  • FIG. 5 is a flowchart of establishing a local IP connection when a user initially accesses in the LTE system according to the present invention
  • FIG. 6 is a flowchart of establishing a local IP connection in a multi-PDN connection establishment process in the LTE system of the present invention
  • FIG. 7 is a flowchart of a modification of a local IP connection bearer in an LTE system according to the present invention.
  • 9 is a flowchart of establishing a local IP connection when a user performs PDP context activation in a UTRAN system provided by the present invention
  • 10 is a flowchart of a PDP context modification performed by a user on a local IP connection in a UTRAN system provided by the present invention
  • FIG. 11 is a flow chart of a user performing PDP context deletion on a local IP connection in the UTRAN system provided by the present invention.
  • the main idea of the method and system of the present invention is to simultaneously establish a local IP access path through the core network and a local IP access path through the core network for the user supporting the local IP access, wherein the local IP does not pass through the core network.
  • the access path as the primary connection, implements fast data transfer, and through the local IP access path of the core network, as a secondary connection, the downlink data of the idle state terminal can be cached.
  • the local IP access may be a local IP access user local network, a local IP access company local network, a local IP access Internet, a diversion operation of the Internet service, and a specific IP data offload.
  • Figure 3a shows the schematic data flow of local IP access in the LTE (Long Term Evolution) mobile communication network architecture:
  • S-GW core network access gateway
  • L-PGW local access gateway
  • FIG. 3b shows a schematic data flow for local IP access in a UTRAN (Universal Mobile Telecommunications System Terrestrial Radio Access Network) mobile communication network architecture.
  • UTRAN Universal Mobile Telecommunications System Terrestrial Radio Access Network
  • two local IP access data paths can be established in the UTRAN network architecture.
  • the first local IP access data path from the terminal to the wireless side entity to the local access gateway (L-GGSN)
  • L-GGSN local access gateway
  • a local IP access data path from the core network SGSN to a local access gateway (L-GGSN), wherein the core network SGSN can buffer downlink data of the idle state terminal.
  • L-GGSN local access gateway
  • the addition of the local access gateway can provide strong support for the local IP access technology.
  • the gateway can be combined with the wireless side entity, or can be set up with the home base station gateway, or can be set on the wireless side entity or Near the home base station gateway.
  • the method for establishing a local IP access connection of the present invention includes the following steps in the session and bearer establishment process:
  • Step 401 A primary connection establishment step, the mobility management device initiates a primary connection establishment and notifies the local access gateway of the primary connection information, and the path of the primary connection is from the terminal to the wireless side entity to the local access gateway;
  • Step 402 A secondary connection establishment step, the mobility management device initiates a secondary connection establishment in association, and notifies the local access gateway of the secondary connection information, where the path of the secondary connection is from the core network access gateway to the local Access gateway.
  • the primary connection and the secondary connection information include a bearer identifier and a bearer status (the bearer status is activated or idle, or represented by a primary connection or a secondary connection), and the primary connection and the secondary connection are associated or used by using the same bearer identifier. Association identifiers are associated.
  • the primary connection establishing step and the secondary connection establishing step may be performed in parallel, and before the primary connection establishing step and the secondary connection establishing step, the mobility management device is based on an access point name (APN) or local
  • the access identifier determines that a local IP access connection needs to be established.
  • the method further includes a downlink data forwarding step and a bearer maintenance step, where the downlink data forwarding step includes: the local access gateway is downlink data according to the primary connection and the secondary connection information. Selecting the correct bearer and forwarding; the bearer maintenance step includes: modifying, by the local access gateway, the primary connection and the secondary connection in association with each other.
  • the mobility management device, the wireless side entity, the local access gateway and the core network access gateway described in the present invention are logical functional entities.
  • FIG. 5 to FIG. 8 illustrate an application scenario of the LTE architecture, where the wireless side entity may be a base station or a home base station, and the mobility management apparatus is an MME (Mobility Management Entity), local access.
  • the gateway includes an L-SGW (Local SGW, Local SGW) and a local L-PGW (Local PGW), and the core network access gateway is an S-GW.
  • L-SGW Local SGW
  • L-PGW Local PGW
  • FIG. 5 is a flowchart of establishing a local IP connection when a user initially accesses in an LTE system according to the system of FIG. 1. The embodiment includes the following steps:
  • Step 501 The user establishes an RRC (Radio Resource Control) connection as a signaling message or a bearer of service data before performing communication;
  • RRC Radio Resource Control
  • Step 502 The user sends an Initialization NAS (Non-Access-Stratume, Non-Access Layer) message to perform an attach operation.
  • Initialization NAS Non-Access-Stratume, Non-Access Layer
  • Step 503 The wireless side entity sends an initial user message to the mobility management device (MME), and forwards the NAS message to the mobility management device.
  • MME mobility management device
  • Step 504 The mobility management device starts the authentication and the security process to verify the user.
  • Step 505a The mobility management device is configured according to an APN (Access Point Name) or a local access identifier (the identifiers may be in the message in step 503). It is found that a local IP connection needs to be established, and the L-SGW located on the wireless side entity/home base station gateway is selected; the MME sends a session establishment request message to the L-SGW, and indicates in the message that the bearer is the primary connection or activation.
  • the connection and the bearer identifier allocated by the MME for the bearer, and the message may also carry the local IP access identifier;
  • the MME may also assign a dedicated association identifier to the connection for associating the primary connection with the secondary connection. If the MME allocates a dedicated association identifier, it needs to be carried in the message and sent to the L-SGW.
  • Step 506a After receiving the message sent by the MME, the L-SGW sends the session establishment request message to the L-PGW along with the indication that the bearer is the primary connection or the activated connection, where the local IP access identifier may be carried, and the L-SGW saves An indication of the connection that is the primary connection or activation;
  • Step 507a After receiving the request message, the L-PGW returns a session establishment response to the L-SGW, and identifies the connection that the bearer is the primary connection or the activation according to the indication in the request message.
  • Step 508a The L-SGW sends a session establishment response to the MME.
  • Step 505b when the mobility management device (MME) establishes a primary connection of the local IP connection, it also needs to establish a secondary connection. At this time, the MME selects to use the S-GW located in the core network, and the MME sends a session establishment request message to the S-GW.
  • MME mobility management device
  • the secondary connection uses the bearer identifier allocated by the MME as the associated primary connection in step 505a, and the message The local IP access identifier may also be carried; if the MME allocates a dedicated association identifier in step 505a, the secondary connection may use the association identifier as the bearer identifier;
  • Step 506b After receiving the message sent by the MME, the S-GW sends the session establishment request message to the L-PGW along with the indication that the bearer is a secondary connection or an idle connection, where the local IP access identifier may be carried, and the S-GW saves the An indication that the bearer is a secondary or idle connection;
  • Step 507b After receiving the request message, the L-PGW returns a session establishment response to the S-GW, and identifies the bearer as a secondary connection or an idle connection according to the indication in the request message.
  • Step 508b The S-GW sends a session establishment response to the MME.
  • the MME does not initiate the establishment process of the wireless side connection to the wireless side entity; the above steps 505a-508a and 505b-508b may be parallel steps, after the MME decides to establish a local IP connection in step 505a, step 505b - 508b can be executed in parallel with steps 505a-508a. When the execution of step 508a is completed, step 509 can be performed without waiting for step 508b to complete;
  • Step 509 The MME initiates an initial context establishment request to the wireless side entity.
  • Step 510 Perform an RRC connection configuration process.
  • Step 511 The wireless side entity returns an initial context setup response to the MME.
  • Step 512 The terminal sends a direct transmission message to the wireless side entity, where the connection completion information is included.
  • Step 514 The MME sends a bearer update request to the L-SGW.
  • Step 515 The L-SGW may send a bearer update request to the L-PGW.
  • step 516 the L-PGW returns a 7-load update response to the L-SGW.
  • step 517 The L-SGW returns a bearer update response to the MME.
  • FIG. 6 is a flow chart of the present invention for establishing a local IP connection after initial user access based on the system of FIG. 1. This embodiment includes the following steps:
  • Step 601 The terminal is attached to the network, and has a PDN connection of the core network.
  • Step 602 The terminal initiates a PDN connection request message to the MME via the wireless side entity.
  • Step 603a The mobility management device (MME) is based on an APN (Access Point Name) or a local access identifier (the identifiers may be in the message at step 602). It is found that a local IP connection needs to be established, and the L-SGW located on the wireless side entity/home base station gateway is selected.
  • the MME sends a session establishment request message to the L-SGW, and indicates in the message that the bearer is the primary connection or the activated connection and the bearer identifier allocated by the MME for the bearer, and the message may also carry the local IP access identifier;
  • the MME may also assign a dedicated association identifier to the connection for associating the primary connection with the secondary connection. If the MME allocates a dedicated association identifier, it needs to be carried in the message and sent to the L-SGW.
  • Step 604a After receiving the message sent by the MME, the L-SGW sends the session establishment request message to the L-PGW along with the indication that the bearer is the primary connection or the activated connection, where the local IP access identifier may be carried, and the L-SGW saves An indication of the connection that is the primary connection or activation;
  • Step 605a after receiving the request message, the L-PGW returns a session establishment response to the L-SGW, and identifies the connection that the bearer is the primary connection or the activation according to the indication in the request message;
  • Step 606a the L-SGW sends a session establishment response to the MME.
  • Step 603b When the mobility management device establishes a primary connection of the local IP connection, the secondary connection needs to be established.
  • the MME selects to use the S-GW located in the core network, and the MME sends a session establishment request message to the S-GW, and The message indicates that the bearer is a secondary or idle connection, and the MME does not allocate a separate bearer identifier for the secondary connection.
  • the secondary connection uses the bearer identifier allocated by the MME as the primary connection in step 603a, and the message may also carry the local IP address. Accessing the identifier; if the MME assigns a dedicated association identifier in step 603a, the secondary connection may use the association identifier as the bearer identifier;
  • Step 604b After receiving the message sent by the MME, the S-GW sends the session establishment request message to the L-PGW together with the indication that the bearer is a secondary connection or an idle connection, where the local IP access identifier. The S-GW saves the indication that the bearer is a secondary connection or an idle connection.
  • Step 605b After receiving the request message, the L-PGW returns a session establishment response to the S-GW, and identifies the bearer as a secondary connection or idle according to the indication in the request message. connection;
  • Step 606b the S-GW sends a session establishment response to the MME.
  • steps 603a-606a and 603b-606b may be parallel steps, in step 603a
  • steps 603b-606b can be performed in parallel with steps 603a-606a.
  • step 607 can be performed without waiting for the completion of step 606b.
  • Steps 607-615 are the same as steps 509-517.
  • the L-PGW saves the two bearers with the same bearer ID and the status of the two bearers (primary connection/activation or secondary connection/idle).
  • the L-PGW selects the correct data for the downlink data based on this information. Hosted.
  • FIG. 7 is a flow chart of the local IP connection bearer modification after the user initially accesses the system according to the system of FIG. 1.
  • the terminal initiates the bearer modification as an example, including the following steps: Step 701: When the terminal has been attached to the network and has a local IP connection, the terminal initiates a local IP connection bearer to the mobility management device (MME) via the wireless side entity. Modifying the request, the terminal sends a bearer resource modification request message to the MME, where the message carries the identifier of the bearer to be modified; Step 702: The MME sends a bearer resource command message to the L-SGW;
  • MME mobility management device
  • Step 703 After receiving the message sent by the MME, the L-SGW sends a bearer resource command message to the L-PGW.
  • Step 704 After receiving the message, the L-PGW triggers the bearer modification of the primary IP connection primary connection, and the L-PGW sends a bearer update request message to the L-SGW, where the message carries the identifier of the bearer to be updated; Step 705, L-SGW The MME forwards the bearer update request message;
  • Step 706 The MME initiates a session management request and a bearer modification request to the wireless side entity.
  • Step 707 Perform an RRC connection configuration process.
  • Step 708 The wireless side entity returns a bearer change response to the MME.
  • Step 709 The terminal initiates a direct transmission message.
  • Step 710 The wireless side entity sends a session management response message to the UI.
  • Step 711 Send a bearer update response to the L-SGW.
  • Step 712 The L-SGW sends a bearer update response to the L-PGW.
  • Step 713 After receiving the bearer update response, the L-PGW determines that the bearer of the local IP connection modified by the host has the same bearer identifier, and triggers the bearer modification of the secondary connection, and the L-PGW sends the bearer to the S-GW.
  • the bearer update request message carries the identifier of the bearer to be modified.
  • Step 714 The S-GW determines that the secondary connection bearer needs to be modified, and then returns the bearer update response directly to the L-PGW after updating the local bearer information.
  • This process uses the terminal to initiate bearer modification as an example.
  • the process of initiating the modification of other NEs in the LTE system is similar to this process and will not be detailed here.
  • FIG. 8 is a flowchart of the local IP connection bearer deletion after the user initially accesses the system according to the system of FIG. 1.
  • the MME initiates the bearer deletion as an example, including the following steps: Step 801: When the terminal has been attached to the network and has a local IP connection, the radio resource needs to be released due to local reasons (such as an abnormality); Carrying the information, the wireless side entity sends a radio resource release indication message to the mobility management device (MME), where the message carries the identifier that needs to be released;
  • MME mobility management device
  • Step 802 Send a bearer deletion command message to the L-SGW.
  • Step 803 After receiving the message sent by the UI, the L-SGW sends a bearer deletion command message to the L-PGW.
  • Step 804a After receiving the message, the L-PGW triggers the release of the bearer of the primary IP connection primary connection, and the L-PGW sends a bearer deletion request message to the L-SGW, where the message carries the identifier of the bearer to be deleted.
  • Step 805a The L-SGW forwards a bearer deletion request message to the MME.
  • Step 806 The MME initiates a bearer deactivation request to the wireless side entity.
  • Step 807 performing an RRC connection configuration process.
  • Step 808 The radio side entity returns a bearer deactivation response to the MME.
  • Step 809 The terminal initiates a direct transmission message.
  • Step 810 The radio side entity sends an EPS bearer deactivation accept message to the MME.
  • Step 811a The MME sends a bearer deletion response to the L-SGW.
  • Step 812a the L-SGW sends a bearer deletion response to the L-PGW.
  • Step 804b after the L-PGW triggers the release of the bearer of the local IP connection main connection in step 804a, and determines that the bearer of the local IP connection released here still has the secondary connection bearer with the same bearer identifier, the auxiliary connection may be triggered at the same time.
  • the bearer is deleted, and the L-PGW sends a bearer deletion request message to the S-GW, where the message carries the identifier of the bearer to be deleted.
  • Step 805b the S-GW determines that the secondary connection bearer needs to be deleted, and then returns the bearer deletion response directly to the L-PGW after deleting the local bearer information;
  • Steps 804b, 805b and steps 804a, 805a may be steps in parallel.
  • This process is described by taking the MME as the bearer deletion.
  • the process of initiating bearer deletion by other NEs in the LTE system is similar to this process and will not be described in detail here.
  • the local access gateways are L-PGWs and L-SGWs, and the L-SGWs are located at the radio side network element/home base station gateway.
  • the PDN connection establishment process is similar to this process when the L-SGW does not exist.
  • the MME needs to directly interact with the L-PGW.
  • the L-SGW does not participate in the process.
  • the PDN connection establishment process is the same as this process, except that the MME needs to exchange messages with the SGW of the core network, which will not be described in detail here.
  • a wireless side entity can be a station, a home base station, an RNC (Radio Network Controller), a mobility management device, and a core network access gateway.
  • RNC Radio Network Controller
  • the local access gateway is the L-GGSN (Local GGSN, Local GGSN).
  • FIG. 9 is a flow chart of establishing a local IP connection when PDP (Packet Data Protocol) context activation is performed after the initial access of the user is completed on the basis of the UTRAN system. This embodiment includes the following steps:
  • Step 901 The terminal successfully attaches to the network by performing an attach procedure.
  • Step 902 The terminal sends a PDP context activation request message to the mobility by using the wireless side entity.
  • a management device SGSN
  • the message carrying the identifier (NSAPI) of the bearer to be established (Network Layer Service Access Point Identifier);
  • Step 903 The SGSN finds that a local IP connection needs to be established according to an APN (Access Point Name) or a local access identifier (the identifier can be carried in the message in step 902), and selects to use the wireless side entity/home base station gateway.
  • the L-GGSN the SGSN sends a PDP context setup request message to the L-GGSN, and indicates in the message that the bearer is the primary connection or the activated connection NSAPI (this identifier is sent by the terminal), and the message may also carry the local IP.
  • the SGSN can also assign a dedicated association identifier to the connection to associate the primary and secondary connections. If the SGSN is assigned a dedicated association identifier, it needs to be carried in the message and sent to L-GGSN 0.
  • Step 904 After receiving the request message sent by the SGSN, the L-GGSN returns a PDP context establishment response to the SGSN, and identifies the connection that the bearer is the primary connection or the activation according to the indication in the request message.
  • Step 905 Perform a radio access bearer establishment process.
  • Step 906 The SGSN may send a PDP context update request to the L-GGSN to notify the L-GGSN of the modified QoS parameter.
  • Step 907 The L-GGSN returns a PDP context update response to the SGSN.
  • Step 908 The SGSN sends a PDP context activation accept message to the terminal.
  • Step 909 when the SGSN establishes a primary connection of the local IP connection, it also needs to establish a secondary connection.
  • the SGSN sends a PDP context setup request message to the L-GGSN, and indicates that the bearer is a secondary connection or an idle connection in the message, and the identifier used to identify the bearer in the message is still the NSAPI used to identify the primary connection in the foregoing step.
  • the message may also carry the local IP access identifier; if the SGSN allocates a dedicated association identifier in step 903, the secondary connection may use the association identifier as the identifier;
  • Step 910 After receiving the request message, the L-GGSN returns a PDP context setup response to the SGSN, and identifies the bearer as a secondary connection or an idle connection according to the indication in the request message.
  • the SGSN does not initiate the establishment process of the wireless side bearer to the wireless side entity.
  • the foregoing steps 909 and 910 may be directly performed after the step 905. Otherwise, the steps 909 and 910 need to be performed after the step 907.
  • FIG. 10 is a flow chart of the PDP context modification of a local IP connection after the initial access of the user is completed on the basis of the UTRAN system according to the present invention.
  • the terminal initiates a PDP context modification and changes to an example, including the following steps:
  • Step 1001 The terminal successfully attaches to the network by performing an attach procedure.
  • Step 1002 The terminal sends a PDP context modification request message to the mobility management device (SGSN) through the wireless side entity, where the message carries the identifier NSAPI of the bearer to be modified.
  • SGSN mobility management device
  • Step 1003 The SGSN sends a PDP context update request message to the L-GGSN.
  • Step 1004 After receiving the message sent by the SGSN, the L-GGSN triggers the bearer modification of the local IP connection primary connection, and returns a PDP context update response message to the SGSN. Carrying the logo that needs to be tampered with;
  • Step 1005 Perform a radio access bearer modification process.
  • Step 1006 The SGSN may send a PDP context update request to the L-GGSN, and notify the L-GGSN of the modified QoS parameter.
  • Step 1007 The L-GGSN returns a PDP context update response to the SGSN.
  • Step 1008 The SGSN sends a PDP context modification accept message to the terminal.
  • Step 1009 After the L-GGSN triggers the modification of the primary connection bearer of the local IP connection in step 1004, it is determined that the bearer of the local IP connection modified by the eNB has the same bearer identifier NSAPI, and the bearer of the secondary connection is triggered. Modifying, the L-GGSN sends a PDP context update request message to the SGSN, and carries the identifier of the bearer to be modified in the message;
  • Step 1010 The SGSN determines that the secondary connection bearer needs to be modified, and returns the PDP context update response to the L-GGSN after updating the local bearer information.
  • step 1009 the L-GGSN starts the timer after step 1004 instead of directly executing step 1009.
  • the timer expires before receiving Go to the message in step 1006, the timer is cleared, and step 1009 is performed; if the message in step 1006 is not received after the timer expires, step 1009 is directly executed.
  • the PDP context modification initiated by the terminal is taken as an example.
  • the process of modifying the PDP context initiated by other network elements in the UTRAN system is similar to this process, and is not detailed here.
  • Figure 11 is a diagram showing the present invention on the basis of the UTRAN system, after the initial access of the user is completed.
  • This example takes the terminal-initiated PDP context deletion as an example, and includes the following steps:
  • Step 1101 The terminal successfully attaches to the network by performing an attach procedure.
  • Step 1102 The terminal sends a PDP context deactivation request message to the mobility management device (SGSN) through the wireless side entity, where the message carries the identifier NSAPI of the bearer to be modified.
  • SGSN mobility management device
  • Step 1103a the SGSN sends a PDP Context Delete Request message to the L-GGSN.
  • Step 1104a After receiving the message sent by the SGSN, the L-GGSN triggers the release of the bearer of the primary IP connection primary connection. The L-GGSN returns a PDP context deletion response message to the SGSN, where the message carries the identifier of the bearer to be deleted.
  • Step 1105 The SGSN sends a PDP context deactivation accept message to the terminal.
  • Step 1106 Perform a radio access bearer release process.
  • Step 1103b After the L-GGSN triggers the release of the primary connection bearer of the local IP connection in step 1104a, it is determined that the bearer of the local IP connection released by the L-GGSN still has the same bearer identifier NSAPI, and the bearer of the secondary connection is triggered. Release, the L-GGSN sends a PDP context delete request message to the SGSN, and carries the identifier of the bearer to be deleted in the message;
  • Step 1104b the SGSN determines that the secondary connection bearer needs to be deleted, and then returns the PDP context deletion response directly to the L-GGSN after deleting the local bearer information.
  • the process of deleting the PDP context by the terminal is taken as an example.
  • the process of deleting the PDP context by other network elements in the UTRAN system is similar to this process, and is not detailed here.
  • the above embodiment illustrates a method of establishing two data tunnels for local IP access only by taking the case where there is no home base station gateway and the local access gateway is located at or near the wireless side entity.
  • the case where there is a home base station gateway is similar.
  • the local access gateway is located at or near the wireless side entity, between the mobility management device and the wireless side entity Messages between the message and mobility management device and the local access gateway will be communicated via the home base station gateway.
  • the message between the mobility management device and the wireless side entity will be transmitted through the home base station gateway, and the mobility management device and the local access gateway The message between the two does not require home base station gateway forwarding.
  • the method of establishing two data tunnels for local IP access is very similar to the method of the above embodiment, and thus the description will not be repeated here.
  • the radio side entity can be a station, a home base station, and a radio network controller (RNC).
  • RNC radio network controller
  • the wireless side entity of the local IP access may have the same address as the local access gateway.
  • the present invention further provides a local IP access connection establishment implementation system, where the system includes a mobility management device and a local access gateway, where:
  • the mobility management apparatus is configured to initiate primary and secondary connection establishment and notify the local access gateway of the primary connection and the secondary connection information in association; the path of the primary connection is from the terminal to the wireless side entity to the local An access gateway, where the path of the secondary connection is from a core network access gateway to a local access gateway;
  • the primary connection and the secondary connection information include a bearer identifier and a bearer state, where the primary connection and the secondary connection are associated by using the same bearer identifier or by using a dedicated association identifier; the bearer state is activated or idle, or is used by the master. Connection or secondary connection representation.
  • the local access gateway is configured to: create a primary connection and a secondary connection, and save the primary connection and the secondary connection information, select the correct bearer and forward the downlink data according to the primary connection and the secondary connection information, and modify or release the associated link.
  • the main connection and the auxiliary connection are configured to: create a primary connection and a secondary connection, and save the primary connection and the secondary connection information, select the correct bearer and forward the downlink data according to the primary connection and the secondary connection information, and modify or release the associated link.
  • the wireless side entity is a base station, a home base station, a radio network controller (RNC); the mobility management device is a mobility management entity (MME), a mobile switching center (MSC) or a serving GPRS support node (SGSN); local access
  • the gateway may be an L-SGW, an L-PGW, a V-SGW, a V-PGW, an L-GGSN, or a data offloading functional entity.
  • the local access gateway may be combined with the wireless side entity, or may be set up with the home base station gateway, or may be disposed near the wireless side entity or the home base station gateway; the core network access gateway is the S-GW and the SGSN.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.
  • the present invention provides a method for establishing two data tunnels for local IP access, and the core network mobility management device (for example, MME, SGSN) identifies the tunnel as the primary connection when creating the first data tunnel, and At the same time, the establishment of the second data tunnel is initiated, and the identifier is a secondary connection, so that the local access gateway can simultaneously save the information of the two data tunnels, and can accurately select the tunnel used by the data flow, thereby solving the problem of establishing the local IP access at the same time.
  • the problem of multiple connections effectively implements the creation mechanism of two data tunnels.

Landscapes

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

Description

本地 IP访问连接建立的实现方法及***
技术领域
本发明涉及移动通信领域， 具体涉及本地 IP访问连接建立的实现方法及 ***。
背景技术
第三代合作伙伴计划 （ 3rd Generation Partnership Project, 筒称为 3GPP ) 演进的分组*** （ Evolved Packet System , 简称为 EPS ) 由演进的通用移动 通信***陆地无线接入网 ( Evolved Universal Mobile Telecommunications System 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的***架构的示意图。 如图 1所示， MME 负责移动性管理、 非接入层信令的处理和用户移动性管理上下文的管理等控 制面的相关工作； S-GW是与 E-UTRAN相连的接入网关设备， 在 E-UTRAN 和 P-GW之间转发数据，并且负责对寻呼等待数据进行緩存； P-GW则是 EPS 与分组数据网络（ Packet Data Network , 筒称为 PDN )之间的边界网关， 负 责 PDN的接入及在 EPS与 PDN间转发数据等功能； PCRF是策略和计费规 则功能实体， 它通过接收接口 Rx和运营商网络协议（Internet Protocol, 简称 为 IP )业务网络相连 , 获取业务信息 , 此外， 它通过 Gx/Gxa/Gxc接口与网络 中的网关设备相连， 负责发起 IP 承载的建立， 保证业务数据的服务质量 ( Quality of Service, 简称为 QoS ) ， 并进行计费控制。
家用基站是一种小型、低功率的基站， 部署在家庭及办公室等室内场所， 其主要作用是向用户提供更高的业务速率并降低使用高速率服务所需要的费 用， 同时弥补已有分布式蜂窝无线通信***覆盖的不足。 家用基站的优点是 实惠、 便捷、 低功率输出、 即插即用等。
家用基站可以直接连接到核心网络， 也可以通过家用基站网关这个逻辑 网元接入到核心网络， 如图 1所示。 其中， 家用基站网关主要功能为： 验证 家用基站的安全性， 处理家用基站的注册， 对家用基站进行运行维护管理， 根据运营商要求配置和控制家用基站， 负责交换核心网和家用基站的数据。 接入网关可以是 S-GW (服务网关， Serving Gateway ) 、 P-GW (分组数据网 网关， Packet Data Network Gateway )、 SGSN(服务通用分组无线业务（ GPRS ) 支持节点， Serving GPRS Support Node )、 GGSN(网关 GPRS支持节点， Gateway GPRS Support Node )„本地接入网关可以是 L-SGW(本地 SGW, Local SGW )、 L-PGW (本地 PGW, Local PGW ) 、 V-SGW (虚拟 SGW, Virtual SGW ) 、 V-PGW (虚拟 PGW, Virtual PGW ) 、 L-GGSN (本地 GGSN, Local GGSN ) , 还可以是数据分流功能实体。 本地接入网关可以和无线侧实体合设， 也可以 和家用基站网关合设， 还可以设置在无线侧实体或家用基站网关附近。
除了支持移动核心网络的接入以外， 移动通信***（包括家用基站***） 还可支持本地 IP访问功能， 实现终端对家用网络中其他 IP设备或者互联网 络的本地接入。
图 2是现有技术在图 1家用基站***的基础上， 用户初始接入时建立本 地 IP访问连接的过程的流程图， 其具体步骤描述如下：
步骤 201 , 用户在进行通信前建立 RRC ( Radio Resource Control, 无线资 源控制） 连接作为信令消息或者业务数据的承载；
步骤 202, 用户发送初始化 NAS ( Non-Access-Stratum, 非接入层） 消息 进行附着操作；
步骤 203， 无线侧实体将初始的用户消息发给移动性管理实体， 并转发
NAS消息至移动性管理实体；
步骤 204 , 移动性管理实体开启鉴权以及安全流程， 对用户进行验证； 步骤 205， 移动性管理实体根据 APN ( Access Point Name， 接入点名称） 或本地访问标识 （这些标识可以在步骤 203消息中携带）发现需建立本地 IP 访问连接后， 向 L-SGW发送会话建立请求；
步骤 206, 接收到移动性管理实体发送的请求消息， L-SGW将会话建立 请求消息发送给 L-PGW;
步骤 207, L-PGW向 L-SGW返回会话建立响应；
步骤 208, L-SGW向移动性管理实体发送会话建立响应；
步骤 209, 移动性管理实体向家用基站发起初始上下文建立请求； 步骤 210， 执行 RRC连接配置过程；
步骤 211 , 家用基站向移动性管理实体返回初始上下文建立响应； 步骤 212, 终端向无线侧实体发送直传消息， 包含附着完成消息； 步骤 213 , 无线侧实体向移动性管理实体发送附着完成消息；
步骤 214， 移动性管理实体向 L-SGW发送承载更新请求， 携带无线侧实 体的地址和无线侧实体的隧道标识；
步骤 215, 该步可选。 如果在 214步中携带了切换指示， 则 L-SGW向 L-PGW发送承载更新请求。
步骤 216， 该步可选。 L-PGW向 L-SGW返回承载更新响应。
步骤 217, L-SGW向移动性管理实体返回承载更新响应。
在上述本地 IP访问连接建立过程中， 只存在一个数据隧道（L-PGW至 L-SGW 至无线侧实体） ， 若每当用户空闲时就将 L-SGW切换到核心网的 S-GW， 则会导致 L-SGW与 S-GW之间的频繁切换， 增加***负荷， 延长用 户接入时间； 当用户空闲时， 若 L-SGW保持不变， 则需要在无线侧实体中緩 存下行数据， 增加了无线侧实体的成本和负荷， 尤其是对家用基站***； 若 为避免上述问题而在建立本地 IP访问连接时选择核心网的 S-GW为用户服 务， 则该本地 IP访问连接需要经过核心网， 因此数据的传递速度受到一定的 制约。 创建两个数据隧道虽然可以解决上述问题， 但现有技术中还未提供明 确的解决方案。 发明内容
本发明要解决的技术问题是提供一种本地 IP访问连接建立的实现方法和 ***， 有效地实现两条数据隧道的创建机制。
为解决上述技术问题，本发明提供一种本地 IP访问连接建立的实现方法， 包括以下步骤：
移动性管理装置发起主连接建立并将主连接信息通知本地接入网关； 所 述主连接的路径是从终端至无线侧实体至本地接入网关； 以及
所述移动性管理装置相关联地发起辅连接建立， 并将辅连接信息通知所 述本地接入网关； 所述辅连接的路径是从核心网接入网关至本地接入网关。
优选地， 所述主连接及辅连接信息包括承载标识及承载状态， 所述主连 接与辅连接通过使用相同的承载标识或通过使用专用的关联标识相关联， 所 述承载状态为激活或空闲， 或者用主连接或辅连接表示。
优选地， 所述发起主连接建立并将主连接信息通知所述本地接入网关的 步骤， 以及所述发起辅连接建立并将辅连接信息通知所述本地接入网关的步 骤并行执行， 且在所述发起主连接建立的步骤之前， 所述方法还包括： 移动 性管理装置根据接入点名称（ APN )或本地访问标识确定需要建立本地 IP访 问连接。
优选地， 在所述发起主连接建立并将主连接信息通知所述本地接入网关 的步骤， 以及所述发起辅连接建立并将辅连接信息通知所述本地接入网关的 步骤之后， 所述方法还包括： 所述本地接入网关根据所述主连接及辅连接信 息为下行数据选择正确的承载并转发； 以及所述本地接入网关相关联地修改 或释放所述主连接及辅连接。
优选地， 所述无线侧实体是基站或家用基站； 所述移动性管理装置为移 动性管理实体（ MME )； 所述本地接入网关包括本地服务网关（ L-SGW )和 本地分组数据网络网关（ L-PGW )；所述核心网接入网关为服务网关 ( S-GW )； 所述 MME发起主连接建立并将主连接信息通知所述本地接入网关的步骤包 括：
所述 MME向所述 L-SGW发送会话建立请求消息，并在消息中指示该会 话对应的 7 载为主连接以及所述 MME为该 7|载分配的 7 载标识；
接收到 MME发送的消息后，所述 L-SGW将会话建立请求消息连同该承 载为主连接的指示一起发送给所述 L-PGW, 所述 L-SGW保存该承载为主连 接的指示；
所述 L-PGW收到请求消息后向所述 L-SGW返回会话建立响应， 并根据 请求消息中的指示标识该承载为主连接； 以及
所述 L-SGW向所述 MME发送会话建立响应；
所述 MME发起辅连接建立， 并将辅连接信息通知所述本地接入网关的 步骤包括：
所述 MME向所述 S-GW发送会话建立请求消息， 并在消息中指示该会 话对应的承载为辅连接以及所述 MME为该承载分配的承载标识；所述 MME 为辅连接分配的承载标识与所述 MME为主连接分配的承载标识相同， 或者， 所述 MME为辅连接分配的 载标识与所述 MME为主连接分配的 载标识 不同，但所述 ΜΜΕ向所述 L-SGW或 S-GW发送的会话建立请求消息中携带 所述 ΜΜΕ分配的专用的关联标识；
接收到所述 ΜΜΕ发送的消息后， 所述 S-GW将会话建立请求消息连同 该承载为辅连接的指示一起发送给所述 L-PGW, 所述 S-GW保存该承载为辅 连接指示；
所述 L-PGW收到请求消息后向所述 S-GW返回会话建立响应，并根据请 求消息中的指示标识该承载为辅连接； 以及
所述 S-GW向所述 ΜΜΕ发送会话建立响应。
优选地， 所述无线侧实体是基站、 家用基站或无线网络控制器（RNC )； 所述移动性管理装置及核心网接入网关是服务通用分组无线业务（ GPRS )支 持节点（ SGSN )；所述本地接入网关是本地网关 GPRS支持节点（ L-GGSN )； 所述 SGSN发起主连接建立并将主连接信息通知所述 L-GGSN的步骤包括： 所述 SGSN向所述 L-GGSN发送 PDP上下文建立请求消息，并在消息中 指示该 PDP上下文对应的承载为主连接及对应的承载标识；
接收到所述 SGSN发送的请求消息后， 所述 L-GGSN向所述 SGSN返回 PDP上下文建立响应， 并根据请求消息中的指示标识该承载为主连接； 执行无线接入承载建立流程； 以及
所述 SGSN返回 PDP上下文激活接受消息给终端；
所述 SGSN发起辅连接建立并将辅连接信息通知所述 L-GGSN的步骤包 括：
所述 SGSN向所述 L-GGSN发送 PDP上下文建立请求消息 ,并在消息中 指示该 PDP上下文对应的承载为辅连接以及对应的承载标识； 所述辅连接对 应的承载标识与所述主连接对应的承载标识相同， 或者， 所述辅连接对应的 承载标识与所述主连接对应的承载标识不同， 但所述 SGSN向所述 L-GGSN 发送的所述 PDP上下文建立请求消息中的至少一个携带所述 SGSN分配的专 用的关联标识； 以及
所述 L-GGSN收到请求消息后向所述 SGSN返回 PDP上下文建立响应， 并根据请求消息中的指示标识该承载为辅连接。
为解决上述技术问题， 本发明还提供一种本地 IP访问连接建立的实现系 统， 包括移动性管理装置及本地接入网关， 其中：
所述移动性管理装置， 设置为相关联地发起主连接和辅连接建立以及将 主连接及辅连接信息通知所述本地接入网关； 所述主连接的路径是从终端至 无线侧实体至所述本地接入网关， 所述辅连接的路径是从核心网接入网关至 所述本地接入网关；
所述本地接入网关， 设置为创建主连接及辅连接并保存主连接及辅连接 信息。
优选地， 所述主连接及辅连接信息包括承载标识及承载状态， 所述主连 接与辅连接通过使用相同的承载标识或通过使用专用的关联标识相关联， 所 述承载状态为激活或空闲， 或者用主连接或辅连接表示。
优选地， 所述本地接入网关还设置为根据所述主连接及辅连接信息为下 行数据选择正确的承载并转发， 以及相关联地修改或释放所述主连接及辅连 接。
优选地， 所述***还包括所述核心网接入网关， 设置为创建辅连接并保 存辅连接信息。
优选地， 所述无线侧实体是基站、 家用基站、 无线网络控制器（RNC )； 所述移动性管理装置是移动性管理实体（MME ) 、 移动交换中心（MSC )或 服务通用分组无线业务（GPRS ) 支持节点 （SGSN ) ； 所述本地接入网关包 括本地服务网关 （ L-SGW )和本地分组数据网络网关 （ L-PGW ) ， 或者是本 地网关 GPRS支持节点 （ L-GGSN ) ； 核心网接入网关是服务网关 （ S-GW ) 或 SGSN0
本发明提供了一种为本地 IP访问同时建立两条数据隧道的技术方案， 其 中， 核心网移动性管理装置（如， MME、 SGSN )在创建第一条数据隧道时， 标识该隧道为主连接， 并同时发起第二条数据隧道的建立， 且标识为辅连接， 以便本地接入网关可以同时保存两条数据隧道信息， 并可以准确选择数据流 使用的隧道， 从而解决了为本地 IP访问同时建立多连接的问题， 有效地实现 了两条数据隧道的创建机制。
附图概述
图 1为现有技术中移动通信网络连接示意图；
图 2为现有技术中用户初始接入时建立本地 IP连接的流程图；
图 3a为本发明 LTE移动通信***中本地 IP接入数据流示意图； 图 3b为本发明 UTRAN移动通信***中本地 IP接入数据流示意图； 图 4为本发明本地 IP访问连接建立的实现方法的示意图；
图 5是本发明 LTE***中用户初始接入时建立本地 IP连接的流程图； 图 6是本发明 LTE***中多 PDN连接建立过程中进行本地 IP连接建立 的流程图；
图 7是本发明 LTE***中本地 IP连接承载修改的流程图；
图 8是本发明 LTE***中本地 IP连接承载释放的流程图；
图 9是本发明提供的 UTRAN***中用户进行 PDP上下文激活时建立本 地 IP连接的流程图； 图 10是本发明提供的 UTRAN***中用户对本地 IP连接进行 PDP上下 文修改的流程图；
图 11是本发明提供的 UTRAN***中用户对本地 IP连接进行 PDP上下 文删除的流程图。
本发明的较佳实施方式
本发明方法和***的主要思想是， 为支持本地 IP访问的用户同时建立经 过核心网的本地 IP访问路径和不经过核心网的本地 IP访问路径两条路径， 其中， 不经过核心网的本地 IP访问路径，作为主连接， 实现数据的快速传递， 经过核心网的本地 IP访问路径， 作为辅连接， 可实现空闲状态终端的下行数 据的緩存。
本发明中， 本地 IP访问可以是本地 IP访问用户本地网络、 本地 IP访问 公司本地网络、 本地 IP访问互联网、 互联网业务的分流操作、 特定 IP数据 分流。
图 3a显示了 LTE ( Long Term Evolution, 长期演进）移动通信网络架构 中， 本地 IP访问的示意数据流： 第一条本地 IP访问数据路径从终端至无线 侧实体至本地接入网关 （L-SGW, L-PGW ) , 数据传输不经过核心网， 效率 较高， 且不需要无线侧实体进行数据緩存； 另一条本地 IP访问数据路径从核 心网接入网关 （S-GW ) 至本地接入网关 （L-PGW ) ， 其中核心网 S-GW可 緩存空闲态终端的下行数据。 终端处于连接态时可从第一条本地 IP访问数据 路径传送数据， 而终端进入空闲态后， 数据可从第二条本地 IP访问数据路径 进行传输。
图 3b显示了在 UTRAN ( Universal Mobile Telecommunications System Terrestrial Radio Access Network,通用移动通信***陆地无线接入网络 )移动 通信网络架构中， 本地 IP访问的示意数据流。 如同 LTE网络中的本地 IP访 问连接， 在 UTRAN网络架构中同样可以建立两条本地 IP访问数据路径， 第 一条本地 IP访问数据路径从终端至无线侧实体至本地接入网关（ L-GGSN ) , 数据传输不经过核心网， 效率较高， 且不需要无线侧实体进行数据緩存； 另 一条本地 IP访问数据路径， 从核心网 SGSN至本地接入网关 （ L-GGSN ) , 其中核心网 SGSN可緩存空闲态终端的下行数据。 终端位于连接态时可从第 一条本地 IP访问数据路径传送数据， 而终端进入空闲态后， 数据可从第二条 本地 IP访问数据路径进行传输。
如图 3a及 3b， 本地接入网关的增设可提供对本地 IP访问技术的有力支 持， 该网关可以和无线侧实体合设， 也可以和家用基站网关合设， 还可以设 置在无线侧实体或家用基站网关附近。
如图 4所示， 本发明的本地 IP访问连接建立的方法， 在会话和承载建立 过程中包括以下步驟：
步骤 401 : 主连接建立步骤， 移动性管理装置发起主连接建立并将主连 接信息通知本地接入网关， 所述主连接的路径是从终端至无线侧实体至本地 接入网关；
步骤 402: 辅连接建立步骤， 所述移动性管理装置相关联地发起辅连接 建立， 并将辅连接信息通知所述本地接入网关， 所述辅连接的路径是从核心 网接入网关至本地接入网关。
所述主连接及辅连接信息包括承载标识及承载状态 （承载状态为激活或 空闲， 或者用主连接或辅连接表示） ， 所述主连接及辅连接通过使用相同的 承载标识关联或使用专用的关联标识进行关联。
所述主连接建立步骤和所述辅连接建立步骤可以并行执行， 且在所述主 连接建立步骤和所述辅连接建立步骤之前， 所述移动性管理装置根据接入点 名称 （ APN )或本地访问标识确定需要建立本地 IP访问连接。
所述方法在主连接建立及辅连接步骤之后， 还包括下行数据转发步骤及 承载维护步骤， 所述下行数据转发步骤包括： 所述本地接入网关根据所述主 连接及辅连接信息为下行数据选择正确的承载并转发； 所述承载维护步骤包 括： 所述本地接入网关相关联地修改或释放所述主连接及辅连接。
本发明所描述的移动性管理装置、 无线侧实体、 本地接入网关及核心网 接入网关均为逻辑功能实体。
下面结合附图和具体实施例对本发明所述技术方案作进一步的详细描 述， 以使本领域的技术人员可以更好的理解本发明并能予以实施， 但所举实 施例不作为对本发明的限定。
以下实施例中， 图 5至图 8描述了 LTE架构的应用场景， 其中， 无线侧 实体可以是基站或家用基站， 移动性管理装置为 MME (移动性管理实体， Mobility Management Entity )， 本地接入网关包括 L-SGW (本地 SGW， Local SGW )及本地 L-PGW (本地 PGW, Local PGW ) , 核心网接入网关是 S-GW。
图 5是本发明在图 1 ***的基础上， LTE***中在用户初始接入时建立 本地 IP连接的流程图， 本实施例包括如下步骤：
步骤 501， 用户在进行通信前建立 RRC ( Radio Resource Control, 无线资 源控制 ) 连接作为信令消息或者业务数据的承载；
步骤 502, 用户发送初始化 NAS ( Non-Access-Stratum, 非接入层） 消息 进行附着操作；
步骤 503， 无线侧实体将初始的用户消息发给移动性管理装置（ MME )， 并转发 NAS消息至移动性管理装置；
步骤 504, 移动性管理装置开启鉴权以及安全流程， 对用户进行验证； 步骤 505a, 移动性管理装置根据 APN ( Access Point Name,接入点名称） 或本地访问标识 （这些标识可以在步骤 503消息中携带 )发现需建立本地 IP 连接， 并选择使用位于无线侧实体 /家用基站网关上的 L-SGW; MME 向 L-SGW发送会话建立请求消息， 并在消息中指示该承载为主连接或激活的连 接以及 MME为该承载分配的承载标识， 同时该消息还可以携带本地 IP访问 标识；
MME也可以为该连接分配一个专用的关联标识，用来关联主连接和辅连 接。若 MME分配了专用的关联标识，则需要携带在该消息中发送给 L-SGW。
步骤 506a, 接收到 MME发送的消息后， L-SGW将会话建立请求消息连 同该承载为主连接或激活的连接的指示一起发送给 L-PGW, 其中可以携带本 地 IP访问标识， L-SGW保存该承载为主连接或激活的连接的指示；
步骤 507a， L-PGW收到请求消息后向 L-SGW返回会话建立响应， 并根 据请求消息中的指示标识该承载为主连接或激活的连接； 步骤 508a, L-SGW向 MME发送会话建立响应；
步骤 505b, 当移动性管理装置（ MME )在建立本地 IP连接的主连接时， 还需要建立辅连接，此时 MME选择使用位于核心网的 S-GW, MME向 S-GW 发送会话建立请求消息， 并在消息中指示该承载为辅连接或空闲连接， MME 不再为此辅连接分配单独的承载标识， 此辅连接使用 MME为关联的主连接 在步骤 505a中分配的承载标识， 同时该消息还可以携带本地 IP访问标识； 若 MME在步骤 505a中分配了专用的关联标识， 则此辅连接可以使用该 关联标识作为承载标识；
步骤 506b， 接收到 MME发送的消息后， S-GW将会话建立请求消息连 同该承载为辅连接或空闲连接的指示一起发送给 L-PGW, 其中可以携带本地 IP访问标识， S-GW保存该承载为辅连接或空闲连接的指示；
步骤 507b, L-PGW收到请求消息后向 S-GW返回会话建立响应， 并根据 请求消息中的指示标识该承载为辅连接或空闲连接；
步骤 508b， S-GW向 MME发送会话建立响应；
对于辅连接， MME不会再向无线侧实体发起无线侧连接的建立过程； 上述步骤 505a-508a和 505b-508b可以是并行的步骤， 当在步骤 505a中 MME决定建立本地 IP连接后，步骤 505b-508b即可以和步骤 505a-508a并行 执行。 当步骤 508a执行结束后即可执行步骤 509， 不需要等待步骤 508b执行 完成；
步骤 509, MME向无线侧实体发起初始上下文建立请求；
步骤 510, 执行 RRC连接配置过程；
步骤 511， 无线侧实体向 MME返回初始上下文建立响应；
步骤 512, 终端向无线侧实体发送直传消息， 其中包含附着完成信息; 步骤 513 , 无线侧实体向 MME发送附着完成消息；
步骤 514, MME向 L-SGW发送承载更新请求；
步骤 515, L-SGW可能向 L-PGW发送承载更新请求；
步骤 516, L-PGW向 L-SGW返回 7 载更新响应。 步骤 517, L-SGW向 MME返回承载更新响应。
图 6是本发明在图 1***的基础上， 在用户初始接入后进行本地 IP连接 建立的流程图。 本实施例包括如下步骤：
步骤 601， 终端已经附着到网络， 具有核心网的 PDN连接；
步骤 602， 终端经无线侧实体向 MME发起 PDN连接请求消息； 步骤 603a, 移动性管理装置（ MME )根据 APN ( Access Point Name, 接 入点名称） 或本地访问标识 （这些标识可以在步骤 602消息中携带）发现需 建立本地 IP连接， 并选择使用位于无线侧实体 /家用基站网关上的 L-SGW。 MME向 L-SGW发送会话建立请求消息， 并在消息中指示该承载为主连接或 激活的连接以及 MME为该承载分配的承载标识， 同时该消息还可以携带本 地 IP访问标识；
MME也可以为该连接分配一个专用的关联标识，用来关联主连接和辅连 接。若 MME分配了专用的关联标识，则需要携带在该消息中发送给 L-SGW。
步骤 604a, 接收到 MME发送的消息后， L-SGW将会话建立请求消息连 同该承载为主连接或激活的连接的指示一起发送给 L-PGW, 其中可以携带本 地 IP访问标识， L-SGW保存该承载为主连接或激活的连接的指示；
步骤 605a, L-PGW收到请求消息后向 L-SGW返回会话建立响应， 并根 据请求消息中的指示标识该承载为主连接或激活的连接；
步骤 606a, L-SGW向 MME发送会话建立响应；
步骤 603b, 当移动性管理装置在建立本地 IP连接的主连接时，还需要建 立辅连接， 此时 MME选择使用位于核心网的 S-GW, MME向 S-GW发送会 话建立请求消息， 并在消息中指示该承载为辅连接或空闲连接， MME不再为 此辅连接分配单独的承载标识， 此辅连接使用 MME为主连接在步骤 603a中 分配的承载标识， 同时该消息还可以携带本地 IP访问标识； 若 MME在步骤 603a中分配了专用的关联标识， 则此辅连接可以使用该关联标识作为承载标 识；
步骤 604b， 接收到 MME发送的消息后， S-GW将会话建立请求消息连 同该承载为辅连接或空闲连接的指示一起发送给 L-PGW, 其中可以携带本地 IP访问标识。 S-GW保存该承载为辅连接或空闲连接的指示； 步骤 605b, L-PGW收到请求消息后向 S-GW返回会话建立响应， 并根据 请求消息中的指示标识该承载为辅连接或空闲连接；
步骤 606b， S-GW向 MME发送会话建立响应；
上述步骤 603a-606a和 603b-606b可以是并行的步骤， 当在步骤 603a中
MME决定建立本地 IP访问连接后， 步骤 603b-606b即可以和步骤 603a-606a 并行执行。 当步骤 606a执行结束后即可执行步骤 607, 不需要等待步骤 606b 执行完成。
步骤 607-615与步骤 509-517相同。
应用图 5和图 6所示的流程，为用户的本地 IP访问同时建立了两条隧道。 为同一个用户， L-PGW保存了具有相同承载标识的两条承载， 及这两条承载 的状态 （主连接 /激活或辅连接 /空闲） ， L-PGW根据这些信息为下行数据选 择正确的承载。
图 7是本发明在图 1***的基础上， 在用户初始接入后进行本地 IP连接 承载修改的流程图。 本实施例以终端发起承载修改为例， 包括如下步骤： 步骤 701 , 当终端已经附着到网络， 且具有本地 IP连接时， 终端经无线 侧实体向移动性管理装置 （MME )发起本地 IP连接承载修改请求， 终端发 送承载资源修改请求消息给 MME， 消息中携带需要修改的承载的标识； 步骤 702 , MME向 L-SGW发送承载资源命令消息；
步骤 703 ,接收到 MME发送的消息后， L-SGW向 L-PGW发送承载资源 命令消息；
步骤 704， L-PGW收到消息后触发本地 IP连接主连接的承载修改， L-PGW 向 L-SGW发送承载更新请求消息， 消息中携带需要更新的承载的标识； 步骤 705 , L-SGW向 MME转发承载更新请求消息；
步骤 706 , MME向无线侧实体发起会话管理请求和承载修改请求； 步骤 707， 执行 RRC连接配置过程；
步骤 708, 无线侧实体向 MME返回承载^ ί 改响应； 步骤 709 , 终端发起直传消息；
步骤 710, 无线侧实体向 ΜΜΕ发送会话管理响应消息；
步骤 711 , ΜΜΕ向 L-SGW发送承载更新响应；
步骤 712， L-SGW向 L-PGW发送承载更新响应；
步骤 713 , L-PGW收到承载更新响应后 , 判断此处修改的本地 IP连接的 承载还存在具有相同承载标识的辅连接承载， 则触发辅连接的承载修改， L-PGW向 S-GW发送承载更新请求消息，消息中携带需要修改的承载的标识； 步骤 714， S-GW判断出此处需要修改的是辅连接承载， 则更新本地承载 信息后直接向 L-PGW返回承载更新响应。
本流程以终端发起承载修改为例进行说明。 LTE ***中其他网元发起承 载修改的流程与该流程相似， 此处不再详述。
图 8是本发明在图 1***的基础上， 在用户初始接入后进行本地 IP连接 承载删除的流程图。 本实施例以 MME发起承载删除为例， 包括如下步骤： 步骤 801 , 当终端已经附着到网络， 且具有本地 IP连接时， 由于本地原 因 （如异常等） ， 需要释放无线资源； 终端删除相应的承载信息， 无线侧实 体向移动性管理装置（MME )发送无线资源释放指示消息， 消息中携带需要 释放的 ? 载的标识；
步骤 802， ΜΜΕ向 L-SGW发送承载删除命令消息；
步骤 803 ,接收到 ΜΜΕ发送的消息后， L-SGW向 L-PGW发送承载删除 命令消息；
步骤 804a， L-PGW 收到消息后触发本地 IP 连接主连接的承载释放， L-PGW向 L-SGW发送承载删除请求消息， 消息中携带需要删除的承载的标 识；
步骤 805a, L-SGW向 MME转发承载删除请求消息；
步骤 806, MME向无线侧实体发起承载去激活请求；
步骤 807 , 执行 RRC连接配置过程；
步骤 808, 无线侧实体向 MME返回承载去激活响应； 步骤 809 , 终端发起直传消息；
步骤 810, 无线侧实体向 ΜΜΕ发送 EPS承载去激活接受消息； 步骤 811a, MME向 L-SGW发送承载删除响应；
步骤 812a， L-SGW向 L-PGW发送承载删除响应；
步骤 804b ,当 L-PGW在步骤 804a中触发本地 IP连接主连接的承载释放 后 , 判断此处释放的本地 IP连接的承载还存在具有相同承载标识的辅连接承 载， 则可以同时触发辅连接的承载删除， L-PGW向 S-GW发送承载删除请求 消息， 消息中携带需要删除的承载的标识；
步骤 805b, S-GW判断出此处需要删除的是辅连接承载， 则删除本地承 载信息后直接向 L-PGW返回承载删除响应；
步骤 804b、 805b与步骤 804a、 805a可以是并行的步骤。
本流程以 MME发起承载删除为例进行说明。 LTE***中其他网元发起 承载删除的流程与该流程相似， 此处不再详述。
在图 5至图 8的示例中 , 本地接入网关为 L-PGW和 L-SGW, 且 L-SGW 位于无线侧网元 /家庭基站网关处。对于 L-SGW不存在时 PDN连接建立流程 与本流程相似， 只是 MME需要直接和 L-PGW进行消息交互， 流程中不再有 L-SGW的参与， 此处不再详述。 对于 L-SGW位于核心网时 PDN连接建立流 程与本流程相同， 只是 MME需要和核心网的 SGW进行消息交互， 此处不再 详述。
图 9至图 11描述了基于 UTRAN***的应用场景， 其中， 无线侧实体可 以 ^^站、 家用基站、 RNC (无线网络控制器， Radio Network Controller ) , 移动性管理装置及核心网接入网关均为 SGSN (服务 GPRS支持节点， Serving GPRS Support Node )，本地接入网关是 L-GGSN(本地 GGSN， Local GGSN )。
图 9是本发明在 UTRAN***的基础上，在用户初始接入完成后进行 PDP ( Packet Data Protocol , 分组数据协议） 上下文激活时建立本地 IP连接的流 程图。 本实施例包括如下步骤：
步骤 901， 终端通过执行附着流程， 成功附着到网絡；
步骤 902, 终端通过无线侧实体发送 PDP上下文激活请求消息给移动性 管理装置（ SGSN ) ,消息中携带需要建立的承载的标识 NSAPI ( Network layer Service Access Point Identifier , 网絡层业务接入点标识） ；
步骤 903 , SGSN根据 APN ( Access Point Name, 接入点名称）或本地访 问标识（这些标识可以在步骤 902消息中携带）发现需建立本地 IP连接， 选 择使用位于无线侧实体 /家用基站网关上的 L-GGSN, SGSN向 L-GGSN发送 PDP 上下文建立请求消息， 并在消息中指示该承载为主连接或激活的连接 NSAPI (这个标识是由终端发送的） ， 同时该消息中还可以携带本地 IP访问 标识；
SGSN也可以为该连接分配一个专用的关联标识， 用来关联主连接和辅 连接。 若 SGSN 分配了专用的关联标识， 则需要携带在该消息中发送给 L-GGSN0
步骤 904,接收到 SGSN发送的请求消息后， L-GGSN向 SGSN返回 PDP 上下文建立响应， 并根据请求消息中的指示标识该承载为主连接或激活的连 接；
步骤 905, 执行无线接入承载建立流程；
步骤 906 , SGSN可能向 L-GGSN发送 PDP上下文更新请求，通知 L-GGSN 修改后的 QoS参数；
步骤 907， L-GGSN向 SGSN返回 PDP上下文更新响应；
步骤 908, SGSN向终端发送 PDP上下文激活接受消息；
步骤 909, 当 SGSN在建立本地 IP连接的主连接时，还需要建立辅连接，
SGSN向 L-GGSN发送 PDP上下文建立请求消息， 并在消息中指示该承载为 辅连接或空闲连接， 在该消息中用来标识该承载的标识仍然为上述步骤中用 来标识主连接的 NSAPI, 同时该消息还可以携带本地 IP访问标识； 若 SGSN 在步骤 903 中分配了专用的关联标识， 则此辅连接可以使用该关联标识作为 载标识；
步骤 910, L-GGSN收到请求消息后向 SGSN返回 PDP上下文建立响应， 并根据请求消息中的指示标识该承载为辅连接或空闲连接；
对于辅连接， SGSN不会再向无线侧实体发起无线侧承载的建立过程。 当 SGSN在步骤 905后不需要更新 L-GGSN时， 上述步骤 909、 910, 可 以在步骤 905后直接执行， 否则步骤 909、 910需要在步骤 907后执行。
图 10是本发明在 UTRAN***的基础上，在用户初始接入完成后对本地 IP连接进行 PDP上下文修改的流程图。 本实施例以终端发起 PDP上下文修 改为例， 包括如下步骤：
步骤 1001 , 终端通过执行附着流程， 成功附着到网络；
步骤 1002,终端通过无线侧实体发送 PDP上下文修改请求消息给移动性 管理装置 （ SGSN ) , 消息中携带需要修改的承载的标识 NSAPI;
步骤 1003， SGSN向 L-GGSN发送 PDP上下文更新请求消息； 步骤 1004 ,接收到 SGSN发送的消息后， L-GGSN触发本地 IP连接主连 接的承载修改， 并向 SGSN返回 PDP上下文更新响应消息， 消息中携带需要 爹改的 ? 载的标识；
步骤 1005， 执行无线接入承载修改流程；
步骤 1006, SGSN 可能向 L-GGSN发送 PDP 上下文更新请求， 通知 L-GGSN修改后的 QoS参数；
步骤 1007, L-GGSN向 SGSN返回 PDP上下文更新响应；
步骤 1008， SGSN向终端发送 PDP上下文修改接受消息；
步骤 1009, 当 L-GGSN在步骤 1004中触发本地 IP连接的主连接承载修 改后， 判断此处修改的本地 IP连接的承载还存在具有相同承载标识 NSAPI 的辅连接承载， 则触发辅连接的承载修改， L-GGSN向 SGSN发送 PDP上下 文更新请求消息， 并在消息中携带需要修改的承载的标识；
步骤 1010, SGSN判断出此处需要修改的是辅连接承载， 则更新本地承 载信息后直接向 L-GGSN返回 PDP上下文更新响应；
当 SGSN在步骤 1005后需要更新 L-GGSN时， 上述步骤 1009、 1010, 需要在步骤 1006后再次执行；
为避免重复执行步骤 1009和 1010，还可以釆用另一种方法， 即 L-GGSN 在步骤 1004后启动定时器， 而不是直接执行步骤 1009。 当定时器超时前收 到步骤 1006 中的消息， 则清除定时器， 并执行步骤 1009; 当定时器超时后 仍未收到步骤 1006中的消息， 则直接执行步骤 1009。
本实施例以终端发起 PDP上下文修改为例， UTRAN***中其他网元发 起的 PDP上下文修改的流程与此流程类似 , 此处不再详述。
图 11是本发明在 UTRAN***的基础上，在用户初始接入完成后对本地
IP连接进行 PDP上下文删除的流程图。 本实施例以终端发起 PDP上下文删 除为例， 包括如下步骤：
步骤 1101 , 终端通过执行附着流程， 成功附着到网络；
步骤 1102，终端通过无线侧实体发送 PDP上下文去激活请求消息给移动 性管理装置 （SGSN ) ， 消息中携带需要修改的承载的标识 NSAPI;
步骤 1103a, SGSN向 L-GGSN发送 PDP上下文删除请求消息； 步骤 1104a, L-GGSN接收到 SGSN发送的消息后， 触发本地 IP连接主 连接的承载释放。 L-GGSN向 SGSN返回 PDP上下文删除响应消息， 消息中 携带需要删除的承载的标识；
步骤 1105, SGSN向终端发送 PDP上下文去激活接受消息；
步骤 1106, 执行无线接入承载释放流程；
步骤 1103b， 当 L-GGSN在步骤 1104a中触发本地 IP连接的主连接承载 释放后，判断此处释放的本地 IP连接的承载还存在具有相同承载标识 NSAPI 的辅连接承载， 则触发辅连接的承载释放， L-GGSN向 SGSN发送 PDP上下 文删除请求消息， 并在消息中携带需要删除的承载的标识；
步骤 1104b , SGSN判断出此处需要删除的是辅连接承载， 则删除本地承 载信息后直接向 L-GGSN返回 PDP上下文删除响应；
本实施例以终端发起 PDP上下文删除为例， UTRAN***中其他网元发 起 PDP上下文删除的流程与此流程类似， 此处不再详述。
为了简化描述， 以上实施例仅以不存在家用基站网关且本地接入网关位 于无线侧实体或其附近的情况为例来说明为本地 IP访问建立两条数据隧道的 方法。 存在家用基站网关的情况与之类似。 当然， 存在家用基站网关， 且本 地接入网关位于无线侧实体或其附近时， 移动性管理装置与无线侧实体之间 的消息和移动性管理装置与本地接入网关之间的消息将经由家用基站网关传 递。 当存在家用基站网关， 且本地接入网关位于家用基站网关或其附近时， 移动性管理装置与无线侧实体之间的消息将经由家用基站网关传递， 而移动 性管理装置与本地接入网关之间的消息不需要家用基站网关转发。 在这些情 况下，为本地 IP访问建立两条数据隧道的方法与上述实施例的方法极为相似， 故在此不再重复描述。
以上实施例不仅可以应用于家用基站***， 而且适用于宏基站***。 在 上述实施例中无线侧实体可以^ &站、 家用基站和无线网络控制器（RNC ) 。 本地 IP访问的无线侧实体可以与本地接入网关具有相同的地址。
为了实现以上方法， 本发明还提供一种本地 IP访问连接建立实现***， 该***包括移动性管理装置及本地接入网关， 其中：
所述移动性管理装置， 设置为相关联地发起主连接和辅连接建立以及将 主连接及辅连接信息通知所述本地接入网关； 所述主连接的路径是从终端至 无线侧实体至本地接入网关， 所述辅连接的路径是从核心网接入网关至本地 接入网关；
所述主连接及辅连接信息包括承载标识及承载状态， 所述主连接与辅连 接通过使用相同的承载标识或通过使用专用的关联标识相关联； 所述承载状 态为激活或空闲， 或者用主连接或辅连接表示。
本地接入网关， 设置为： 创建主连接及辅连接并保存主连接及辅连接信 息， 根据所述主连接及辅连接信息为下行数据选择正确的承载并转发， 以及 相关联地修改或释放所述主连接及辅连接。
所述无线侧实体是基站、 家用基站、 无线网络控制器 （RNC ) ； 移动性 管理装置为移动性管理实体（MME ) 、 移动交换中心 （MSC ) 或服务 GPRS 支持节点（ SGSN );本地接入网关可以是 L-SGW、 L-PGW、 V-SGW、 V-PGW、 L-GGSN,还可以是数据分流功能实体。本地接入网关可以和无线侧实体合设， 也可以和家用基站网关合设，还可以设置在无线侧实体或家用基站网关附近； 核心网接入网关是 S-GW、 SGSN。
当然， 为了完整地实现本地 IP访问连接的建立， 还应包括其他网元， 如 核心网接入网关及无线侧实体等， 其中核心网接入网关用于创建辅连接并保 存辅连接信息。
显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 或 者将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软 件结合。
以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。
工业实用性
本发明提供了一种为本地 IP访问同时建立两条数据隧道的方法， 由核心 网移动性管理装置 （如， MME、 SGSN )在创建第一条数据隧道时， 标识该 隧道为主连接， 并同时发起第二条数据隧道的建立， 且标识为辅连接， 以便 本地接入网关可以同时保存两条数据隧道的信息， 并可以准确选择数据流使 用的隧道， 从而解决了为本地 IP访问同时建立多连接的问题， 有效地实现了 两条数据隧道的创建机制。

Claims

权 利 要 求 书
1、 一种本地 IP访问连接建立的实现方法， 包括以下步骤：
移动性管理装置发起主连接建立并将主连接信息通知本地接入网关； 所 述主连接的路径是从终端至无线侧实体至本地接入网关； 以及
所述移动性管理装置相关联地发起辅连接建立， 并将辅连接信息通知所 述本地接入网关； 所述辅连接的路径是从核心网接入网关至本地接入网关。
2、 如权利要求 1所述的方法， 其中， 所述主连接及辅连接信息包括承载 标识及承载状态， 所述主连接与辅连接通过使用相同的承载标识或通过使用 专用的关联标识相关联， 所述承载状态为激活或空闲， 或者用主连接或辅连 接表示。
3、 如权利要求 1所述的方法， 其中， 所述发起主连接建立并将主连接信 息通知所述本地接入网关的步骤， 以及所述发起辅连接建立并将辅连接信息 通知所述本地接入网关的步骤并行执行， 且在所述发起主连接建立的步骤之 前， 所述方法还包括： 移动性管理装置根据接入点名称 （APN ) 或本地访问 标识确定需要建立本地 IP访问连接。
4、 如权利要求 1所述的方法， 其中， 在所述发起主连接建立并将主连接 信息通知所述本地接入网关的步骤， 以及所述发起辅连接建立并将辅连接信 息通知所述本地接入网关的步骤之后， 所述方法还包括： 所述本地接入网关 根据所述主连接及辅连接信息为下行数据选择正确的承载并转发； 以及所述 本地接入网关相关联地修改或释放所述主连接及辅连接。
5、 如权利要求 1至 4中任一项所述的方法， 其中， 所述无线侧实体是基 站或家用基站； 所述移动性管理装置为移动性管理实体（MME )； 所述本地 接入网关包括本地服务网关（ L-SGW )和本地分组数据网絡网关（ L-PGW )； 所述核心网接入网关为服务网关（S-GW )； 所述 MME发起主连接建立并将 主连接信息通知所述本地接入网关的步骤包括：
所述 MME向所述 L-SGW发送会话建立请求消息，并在消息中指示该会 话对应的 载为主连接以及所述 MME为该 ? 载分配的 7 载标识；
接收到 ΜΜΕ发送的消息后，所述 L-SGW将会话建立请求消息连同该承 载为主连接的指示一起发送给所述 L-PGW, 所述 L-SGW保存该承载为主连 接的指示；
所述 L-PGW收到请求消息后向所述 L-SGW返回会话建立响应， 并根据 请求消息中的指示标识该承载为主连接； 以及
所述 L-SGW向所述 MME发送会话建立响应；
所述 MME发起辅连接建立， 并将辅连接信息通知所述本地接入网关的 步骤包括：
所述 MME向所述 S-GW发送会话建立请求消息， 并在消息中指示该会 话对应的 ^载为辅连接以及所述 MME为该 ? 载分配的 7 载标识；所述 ΜΜΕ 为辅连接分配的承载标识与所述 ΜΜΕ为主连接分配的承载标识相同； 或者， 所述 ΜΜΕ为辅连接分配的 ? 载标识与所述 ΜΜΕ为主连接分配的 载标识 不同，但所述 ΜΜΕ向所述 L-SGW或 S-GW发送的会话建立请求消息中携带 所述 ΜΜΕ分配的专用的关联标识；
接收到所述 ΜΜΕ发送的消息后， 所述 S-GW将会话建立请求消息连同 该承载为辅连接的指示一起发送给所述 L-PGW, 所述 S-GW保存该承载为辅 连接指示；
所述 L-PGW收到请求消息后向所述 S-GW返回会话建立响应，并根据请 求消息中的指示标识该承载为辅连接； 以及
所述 S-GW向所述 ΜΜΕ发送会话建立响应。
6、 如权利要求 1至 4中任一项所述的方法， 其中， 所述无线侧实体是基 站、 家用基站或无线网络控制器 （RNC ) ； 所述移动性管理装置及核心网接 入网关是服务通用分组无线业务（GPRS ) 支持节点 （SGSN ) ； 所述本地接 入网关是本地网关 GPRS支持节点（ L-GGSN )； 所述 SGSN发起主连接建立 并将主连接信息通知所述 L-GGSN的步骤包括：
所述 SGSN向所述 L-GGSN发送 PDP上下文建立请求消息 ,并在消息中 指示该 PDP上下文对应的承载为主连接及对应的承载标识；
接收到所述 SGSN发送的请求消息后， 所述 L-GGSN向所述 SGSN返回 PDP上下文建立响应， 并根据请求消息中的指示标识该承载为主连接； 执行无线接入承载建立流程； 以及
所述 SGSN返回 PDP上下文激活接受消息给终端；
所述 SGSN发起辅连接建立并将辅连接信息通知所述 L-GGSN的步骤包 括：
所述 SGSN向所述 L-GGSN发送 PDP上下文建立请求消息，并在消息中 指示该 PDP上下文对应的承载为辅连接以及对应的承载标识； 所述辅连接对 应的承载标识与所述主连接对应的承载标识相同； 或者， 所述辅连接对应的 承载标识与所述主连接对应的承载标识不同， 但所述 SGSN向所述 L-GGSN 发送的所述 PDP上下文建立请求消息中的至少一个携带所述 SGSN分配的专 用的关联标识； 以及
所述 L-GGSN收到请求消息后向所述 SGSN返回 PDP上下文建立响应 , 并根据请求消息中的指示标识该承载为辅连接。
7、 一种本地 IP访问连接建立的实现***， 包括移动性管理装置及本地 接入网关， 其中：
所述移动性管理装置， 设置为相关联地发起主连接和辅连接建立以及将 主连接及辅连接信息通知所述本地接入网关； 所述主连接的路径是从终端至 无线侧实体至所述本地接入网关， 所述辅连接的路径是从核心网接入网关至 所述本地接入网关；
所述本地接入网关， 设置为创建主连接及辅连接并保存主连接及辅连接 信息。
8、 如权利要求 7所述的***， 其中， 所述主连接及辅连接信息包括承载 标识及承载状态， 所述主连接与辅连接通过使用相同的承载标识或通过使用 专用的关联标识相关联， 所述承载状态为激活或空闲， 或者用主连接或辅连 接表示。
9、 如权利要求 7所述的***， 其中， 所述本地接入网关还设置为根据所 述主连接及辅连接信息为下行数据选择正确的承载并转发， 以及相关联地修 改或释放所述主连接及辅连接。
10、 如权利要求 7所述的***， 其中， 所述***还包括所述核心网接入 网关， 设置为创建辅连接并保存辅连接信息。
11、 如权利要求 7至 10中任一项所述的***， 其中， 所述无线侧实体是 基站、 家用基站、 无线网络控制器 （RNC ) ； 所述移动性管理装置是移动性 管理实体（ MME )、移动交换中心（ MSC )或服务通用分组无线业务（ GPRS ) 支持节点（ SGSN )； 所述本地接入网关包括本地服务网关（ L-SGW )和本地 分组数据网络网关（ L-PGW )， 或者是本地网关 GPRS支持节点（ L-GGSN )； 核心网接入网关是服务网关 （S-GW )或 SGSN。
PCT/CN2010/073776 2009-07-17 2010-06-10 本地ip访问连接建立的实现方法及*** WO2011006404A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910159170.3 2009-07-17
CN200910159170.3A CN101959175B (zh) 2009-07-17 2009-07-17 本地ip访问连接建立的实现方法及***

Publications (1)

Publication Number Publication Date
WO2011006404A1 true WO2011006404A1 (zh) 2011-01-20

Family

ID=43448927

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/073776 WO2011006404A1 (zh) 2009-07-17 2010-06-10 本地ip访问连接建立的实现方法及***

Country Status (2)

Country Link
CN (1) CN101959175B (zh)
WO (1) WO2011006404A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9882803B2 (en) 2012-02-22 2018-01-30 Zte Corporation Method and system for implementing local IP service
EP3720203A4 (en) * 2017-12-29 2021-01-06 Huawei Technologies Co., Ltd. MEETING SETUP METHOD, DEVICE AND SYSTEM
EP3720235A4 (en) * 2017-12-29 2021-01-27 Huawei Technologies Co., Ltd. SESSION PREPARATION METHOD, DEVICE AND SYSTEM

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130089076A1 (en) * 2011-04-01 2013-04-11 Interdigital Patent Holdings, Inc. Local / remote ip traffic access and selective ip traffic offload service continuity
CN102869116B (zh) * 2011-07-05 2015-07-08 华为终端有限公司 一种本地网络和实现本地网关和家庭基站建立连接的方法
CN102427599B (zh) * 2011-08-12 2015-04-08 电信科学技术研究院 数据传输方法和设备
EP2999267B1 (en) 2013-06-27 2020-04-22 Huawei Technologies Co., Ltd. Method for controlling handover of user equipment, base station, user equipment, and system
WO2014205825A1 (zh) * 2013-06-28 2014-12-31 富士通株式会社 资源配置方法、装置和***
CN107333338B (zh) * 2016-04-29 2020-02-21 中国电信股份有限公司 基于lipa的动态承载策略控制方法、装置和通信网络

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006114628A2 (en) * 2005-04-26 2006-11-02 Vodafone Group Plc Sae/lte telecommunications networks
CN101094520A (zh) * 2006-06-20 2007-12-26 阿尔卡特朗讯 Wimax网络、Wimax网元及其中处理QoS需求的方法
US20080004030A1 (en) * 2006-06-30 2008-01-03 Nokia Corporation Multi-level control for measurement reports

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060416B (zh) * 2006-04-21 2010-05-12 北京三星通信技术研究有限公司 建立和更新隧道传输的方法
EP1883195A1 (en) * 2006-07-28 2008-01-30 Nokia Siemens Networks Gmbh & Co. Kg Tunnel switching mechanism inside a SGSN for OTA (one tunnel approach) - TTA (Two tunnel approach) switching used for legal interception
CN100486381C (zh) * 2006-08-18 2009-05-06 中兴通讯股份有限公司 分组域中ggsn获知sgsn启用单隧道信息的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006114628A2 (en) * 2005-04-26 2006-11-02 Vodafone Group Plc Sae/lte telecommunications networks
CN101094520A (zh) * 2006-06-20 2007-12-26 阿尔卡特朗讯 Wimax网络、Wimax网元及其中处理QoS需求的方法
US20080004030A1 (en) * 2006-06-30 2008-01-03 Nokia Corporation Multi-level control for measurement reports

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9882803B2 (en) 2012-02-22 2018-01-30 Zte Corporation Method and system for implementing local IP service
EP3720203A4 (en) * 2017-12-29 2021-01-06 Huawei Technologies Co., Ltd. MEETING SETUP METHOD, DEVICE AND SYSTEM
EP3720235A4 (en) * 2017-12-29 2021-01-27 Huawei Technologies Co., Ltd. SESSION PREPARATION METHOD, DEVICE AND SYSTEM
US11483878B2 (en) 2017-12-29 2022-10-25 Huawei Technologies Co., Ltd. Session establishment method and system, and device

Also Published As

Publication number Publication date
CN101959175A (zh) 2011-01-26
CN101959175B (zh) 2014-03-19

Similar Documents

Publication Publication Date Title
RU2749750C1 (ru) Управление разрывом услуги для беспроводного устройства
US10015718B2 (en) Method, apparatus, and system for routing user plane data in mobile network
US9320075B2 (en) Method, system and transmission distribution network element for indicating data-distribution
US8855045B2 (en) Method and system for controlling establishment of local IP access
JP2019526970A (ja) 無線通信システムにおける登録解除方法及びこのための装置
WO2011006404A1 (zh) 本地ip访问连接建立的实现方法及***
US8842636B2 (en) Method and device for managing Internet Protocol offload connection
WO2011026392A1 (zh) 一种路由策略的获取方法及***
WO2012041073A1 (zh) 一种实现流迁移的方法及***
WO2011026407A1 (zh) 一种本地网际协议访问连接移动性支持的方法及***
US9629179B2 (en) Method and device for processing local access connection
WO2011015092A1 (zh) 实现本地ip访问控制的方法、通知方法及***
WO2011054264A1 (zh) 一种建立本地ip访问下行数据通道的方法及***
WO2011017979A1 (zh) 支持ip分流的通信***中资源管理方法与装置
WO2011020408A1 (zh) 一种本地ip访问连接的释放***及方法
CN102014452B (zh) 一种本地ip访问连接实现移动性的方法和***
WO2012126319A1 (zh) 一种本地访问业务的切换方法及***
WO2012103773A1 (zh) 中继***的过载控制方法及***
WO2011144000A1 (zh) 一种实现路由选择的方法和装置
WO2011050663A1 (zh) 支持本地ip访问的通信***中隧道更新方法与***
WO2011020418A1 (zh) 终端转为连接态时更改服务网关的连接激活方法及***
WO2011009353A1 (zh) 建立ip分流连接的实现方法和***
WO2012041131A1 (zh) 一种用户参与本地访问连接建立的方法及***
WO2011035671A1 (zh) 一种释放本地ip访问连接的***及方法
WO2011153889A1 (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: 10799402

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: 10799402

Country of ref document: EP

Kind code of ref document: A1