WO2012167460A1 - Procédé et appareil permettant la réalisation de mobilité de connexion d'accès ip local ou de délestage de trafic ip sélectionné - Google Patents

Procédé et appareil permettant la réalisation de mobilité de connexion d'accès ip local ou de délestage de trafic ip sélectionné Download PDF

Info

Publication number
WO2012167460A1
WO2012167460A1 PCT/CN2011/076450 CN2011076450W WO2012167460A1 WO 2012167460 A1 WO2012167460 A1 WO 2012167460A1 CN 2011076450 W CN2011076450 W CN 2011076450W WO 2012167460 A1 WO2012167460 A1 WO 2012167460A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
access network
gateway
user equipment
message
Prior art date
Application number
PCT/CN2011/076450
Other languages
English (en)
Chinese (zh)
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 华为技术有限公司
Priority to CN201180001542.5A priority Critical patent/CN103155683B/zh
Priority to PCT/CN2011/076450 priority patent/WO2012167460A1/fr
Publication of WO2012167460A1 publication Critical patent/WO2012167460A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H04L12/5691—Access to open networks; Ingress point selection, e.g. ISP selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing 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/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents

Definitions

  • Embodiments of the present invention relate to the field of wireless access and, more particularly, to methods and apparatus for implementing mobility of LIPA or SIPTO. Background technique
  • Femtocell is a generic term for low-power wireless access point technology, using licensed spectrum, connecting to standard wireless terminals, using DSL (digital subscriber line) for home occupants, and broadband access to cable The mode is connected to the mobile operator's network.
  • Figure 1 is a schematic diagram of the general model of Femtocell, which is connected to various user equipments and connected to the Internet through a broadband router.
  • a home base station (HNB: Home NodeB) is a home wireless access point operating in a UTRAN (UMTS Territorial Radio Access Network) spectrum
  • a home evolved base station (HeNB: Home evolved NodeB) Is a home wireless access point operating in the E-UTRAN (Evolved UMTS Territorial Radio Access Network) spectrum
  • Home non-3GPP WAP Home non-3GPP Wireless Access Point is a home wireless access point for spectrum running on non-3GPP networks such as CDMA/Wimax/WLAN/HRPD.
  • the home base station gateway (HNB GW), the home evolved base station gateway (HeNB GW), and the home non-3GPP wireless access point gateway (Home non-3GPP WAP GW) respectively pass the universal IP access network and the HNB.
  • a gateway network element of the home wireless access point connected to the access network element and the home non-3GPP wireless access point.
  • the network element in the mobile network includes: a mobility management entity in the E-UTRAN (MME:
  • SGSN Serving GPRS Supporting Node
  • non-3GPP GW non-3GPP GW
  • EDG Evolved Packet Data Gateway
  • ASN GW Access Service Network Gateway
  • AGW Access Gateway
  • AGW Access Gateway
  • HRPD HRPD Serving Gateway
  • the Home Subscriber Server (HSS) is used to store subscription information of the UE (User Equipment).
  • the Authentication Authorization and Accounting Server (AAA Server) is used to perform access authentication, authorization, and accounting functions for the UE.
  • FIG. 2 is only an example of a home access system architecture.
  • a home access point can be directly connected to a network element in a mobile network.
  • H(e)NB home evolved base station
  • the data for the user to access the Internet can be directly sent to the Internet in the vicinity of the access network element or in the vicinity of the access network element.
  • operators provide additional services, that is, users can access other IP devices, such as printers and fax machines, which are also in the home or enterprise network through access network elements.
  • LIPA Local IP Access
  • L-GW Local Gateway
  • the meta is also located in the home gateway of the home or corporate network to access other IP devices in the home or corporate network.
  • SIPTO Select IP traffic offload
  • the UE can be located in the home or enterprise through the local gateway located in the access network element or through the access network element.
  • the local gateway of the network accesses a specific IP network, such as the Internet.
  • FIG. 3 is a general Schematic diagram of a LIPA or SIPTO PDN connection.
  • a method for implementing local IP access LIPA or selecting an IP data stream to steer SIPTO mobility includes: receiving, from an access network element, a tunnel endpoint identifier TEID assigned by the access network element to a user equipment a first IP address, where the first IP address is an IP address used by the access network element to interact with the local gateway; and the serving gateway sends the TEID assigned by the access network element to the user equipment to the local gateway.
  • an apparatus for implementing local IP access LIPA or selecting an IP data stream to steer SIPTO mobility includes: receiving means, configured to receive, by an access network element, the access network element for user equipment allocation
  • the tunnel endpoint identifies the TEID and the first IP address, where the first IP address is an IP address used by the access network element to interact with the local gateway; and the sending device is configured to send the access to the local gateway through the serving gateway.
  • Figure 1 is a schematic diagram of a general model of Femtocell
  • FIG. 2 is a schematic diagram of a home access system architecture
  • Figure 3 is a schematic diagram of a general LIPA or SIPTO PDN connection
  • FIG. 4 is a schematic diagram showing an architecture in which an access network element and a local gateway are integrated;
  • 5 is a schematic diagram showing an architecture in which an access network element and a local gateway are separated; 6 is a flow chart showing a method of implementing mobility of LIPA or SIPTO, in accordance with an embodiment of the present invention;
  • FIG. 7 is a schematic diagram showing a flow of establishing a tunnel connection between an access network element and a local gateway when establishing a LIPA or SIPTO PDN connection;
  • Figure 8 is a diagram showing the flow of connection release between the local gateway and the access network element when the Sl/Iu connection is released;
  • Figure 9 is a diagram showing the flow when the user equipment makes a service request after the S 1/Iu connection is released;
  • FIG. 10 is a schematic diagram showing how to establish a tunnel connection between a new access network element and a local gateway when the access network element changes;
  • Figure 11 is a diagram showing an x2 or RNC enhanced handover procedure when an access network element changes
  • Figure 12 is a block diagram showing a device implementing mobility of LIPA or SIPTO according to an embodiment of the present invention. detailed description
  • FIG. 4 is a diagram showing the architecture of the access network element and the local gateway. Schematic diagram. As shown in Figure 4, the dashed lines show the signaling transfer in the architecture of the existing access network element and local gateway.
  • the UE When the UE needs to send signaling to the local area network, it first sends the signaling to the access network element (HNB in FIG. 4). Thereafter, the access network element transmits the signaling via the mobility management network element (SGSN in FIG. 4).
  • HNB access network element
  • SGSN mobility management network element
  • the service gateway forwards to the local gateway (LGW in Figure 4), which then communicates with other networks and devices.
  • the access network element and the local gateway are unified.
  • the mobility management network element assigns the user name TEID (the tunnel endpoint identity: Tunnel endpoint identifier) It is sent to the access network element, and the access network element performs bearer binding according to the TEID by using the internal interface, and establishes an internal data forwarding tunnel between the local gateway and the local gateway.
  • TEID the tunnel endpoint identity: Tunnel endpoint identifier
  • the access network element receives the uplink data sent by the UE and sends the data to the local gateway through the internal data forwarding tunnel, and then the local gateway sends the data packet to the destination address in the local area network.
  • the local gateway sends the data packet to the access network element through the internal data forwarding tunnel, and then sends the data packet to the UE.
  • the data packet is directly sent by the access network element to the local gateway, which saves the transmission cost of the core network and improves the transmission efficiency. Since there are fewer signaling data packets, they are still delivered according to the existing 3GPP standard procedures, which can avoid major changes to the network element.
  • FIG. 5 is a schematic diagram showing an architecture in which an access network element and a local gateway are separated.
  • HNB access network element
  • S-GW Serving Gateway
  • the access network element is separated from the local gateway, and the internal interface cannot be used for bearer binding. Therefore, the access network element cannot be transmitted between the access network element and the local gateway. data. That is to say, there is a need for a direct data transfer between the access network element and the local gateway by establishing a tunnel connection between the access network element and the local gateway when the LIPA or SIPTO PDN is connected, thereby implementing LIPA. Or SIPTO's mobility method.
  • embodiments of the present invention provide methods and apparatus for implementing local IP access to LIPA or selecting IP data streams to groom the mobility of SIPTO.
  • 6 is a flow chart showing a method of implementing mobility of LIPA or SIPTO, implemented by a mobility management network element, in accordance with an embodiment of the present invention.
  • S1 receiving, by the access network element, a tunnel endpoint identifier TEID and a first IP address that are allocated by the access network element to the user equipment, where the first IP address is an IP address used by the access network element to interact with the local gateway; Sending, by the serving gateway, the TEID and the first IP address allocated by the access network element to the user equipment, where the TEID and the first IP address are received by the serving gateway, and the serving gateway forwards to the local The local gateway.
  • TEID tunnel endpoint identifier
  • the tunnel connection between the access network element and the local gateway may be implemented. Realize the continuity of LIPA or SIPTO, and save the cost of the operator because there is no need to upgrade the service gateway.
  • the method for implementing local IP access LIPA or selecting IP data flow to groom SIPTO mobility may be applied to a tunnel between an access network element and a local gateway when initially establishing a LIPA or SIPTO PDN connection. The establishment of the connection will be specifically described below in conjunction with FIG.
  • the access network element refers to the HNB in the UTRAN or the HeNB in the E-UTRAN system
  • the mobility management network element refers to the SGSN in the UTRAN system or the MME in the E-UTRAN system.
  • the access network element and the mobility management network element can also refer to other corresponding devices, and embodiments of the present invention are not intended to limit the present.
  • Figure 7 is a diagram showing the flow of establishing a tunnel connection between an access network element and a local gateway when establishing a LIPA or SIPTO PDN connection.
  • the user equipment sends a PDN Connectivity Request (PDN Connectivity Request) message to the mobility management network element.
  • PDN Connectivity Request PDN Connectivity Request
  • the mobility management network element is configured according to the information about establishing a LIPA or a SIPTO PDN connection, where the related information is specifically: a connection subscription and/or access network element information, for example, an APN requested by the user equipment (Access Point Name: access) Point Name) Whether to allow 1IPA or SIPTO, access network element to support LIPA or SIPTO, user equipment subscription data or carrier configuration to determine whether LIPA or SIPTO PDN can be activated.
  • the mobility management network element may establish a LIPA or SIPTO PDN connection for the user, and mark the PDN connection. Connect for LIPA or SIPTO PDN.
  • the marking is only an implementation manner for determining whether the PDN is a LIPA or a SIPTO PDN in the subsequent process of the mobility management network element, and the embodiment of the present invention is not intended to impose any limitation on the method of determining.
  • the capability of the access network element to support the LIPA or the SIPTO is reported by the access network element to the mobility management network element through the Iu or S1 interface when the user equipment accesses the core network or when the user equipment is started, and the mobility management network element is saved.
  • the mobility management network element sends a Create Session Request message to the service gateway, where the service gateway allocates user plane and control plane information.
  • the user plane information includes but is not limited to the user plane IP address. / TEID
  • the control plane information includes but is not limited to the control plane IP address / TEID.
  • the serving gateway forwards the create session request message to the local gateway. After receiving the message, the local gateway allocates user plane information and control plane information to the PDN connection.
  • the local gateway sends a Create Session Response message to the serving gateway, where the Create Session Response message includes a user plane and a control plane letter allocated by the local gateway to the user.
  • the service gateway sends a create session response message to the mobility management network element, where the create session response message includes the local gateway and the user plane and control plane information allocated by the service gateway for the user.
  • the mobility management network element sends an ERAB/RAB (Evolved Radio Access Bearer/Radio Access Bearer) assignment request ((E-RAB) RAB Assignment request) to the access network element.
  • ERAB/RAB Evolved Radio Access Bearer/Radio Access Bearer
  • RAB Assignment request (E-RAB) RAB Assignment request)
  • the mobility management network element determines to establish the user LIPA or SIPTO PDN, the message comprises a local gateway and TEID allocated to the user's IP address, and the IP address for the local gateway
  • the IP address used to interact with the access NE usually called LGW@LN.
  • the mobility management network element may obtain the LGW@LN in the following three manners:
  • Method 1 In S13, the user plane or control plane IP address carried in the created session response message sent by the local network includes the L-GW@LN, and is sent to the mobility management network element via the serving gateway;
  • the L-GW@LN can be pre-sent to the access NE through the OAM (Operation and Maintenance System), and the L-GW@LN can pass the Iu interface or the S1 interface by the access NE.
  • the message is sent to the mobility management network element;
  • Method 3 The mobility management network element queries the domain name server (DNS) to obtain L-GW@LN according to the cell accessed by the user.
  • DNS domain name server
  • the access NE saves the TEID and L-GW@LN allocated by the local gateway to the user, and sends an ERAB/RAB Assignment Response (E-RAB) RAB Assignment response message to the mobility management network element, where the message includes The TEID assigned by the access NE to the user and the IP address used for interaction with the local gateway, commonly referred to as H(e)NB@LN.
  • E-RAB ERAB/RAB Assignment Response
  • the mobility management network element accesses the user plane information allocated by the network element, that is, TEID+IP, because the LIPA or SIPTO PDN connection is established.
  • the address is sent to the serving gateway in the change notification request message.
  • the TEID+IP address is encapsulated in a special cell in the message.
  • the cell service network element is not parsed, and is directly forwarded to the local gateway after receiving. , such as the Private Extension (Private Extension) cell.
  • the serving gateway forwards it to the local gateway.
  • the local gateway saves the user plane information allocated by the access network element, that is, the TEID and the IP address, and sends a change notification response (Change Notification Response) message to the serving gateway, and the service gateway forwards the change notification response message to the mobility.
  • Change Notification Response Change Notification Response
  • the local gateway When the local gateway is connected to the local gateway, the local gateway can send the data packet to the access network element according to the TEID and the IP address allocated by the access network element, and when the uplink data is sent from the UE to the access network element, the access network element also The data packet can be sent to the local gateway according to the TEID and IP address assigned by the local gateway, and then sent to the destination address by the local gateway.
  • the mobility management network element sends the user plane information allocated by the access network element by changing the notification request message, because in the existing message definition, the change notification notification message includes certain cells, such as Private Extension may not
  • the service gateway needs to be processed, and the service gateway can directly forward to the packet gateway after receiving the message. Therefore, the change notification request message includes the user plane information allocated by the access network element, and does not require the service gateway to perform special processing, and only needs to be forwarded as before, which avoids the service gateway upgrade. Also, the same is true for the change notification response message sent from the local gateway.
  • the user plane information or thePririvate Extension cell allocated by the access network element is not limited by using the change notification request message, and other service gateways may also be used.
  • the message that needs to be forwarded only needs to include the user plane information allocated by the access network element, and is sent to the local gateway.
  • the method avoids establishing a user plane tunnel between the access network element and the local gateway, establishing a control plane tunnel between the access network element and the local gateway, and performing tunnel management, and implementing the access network element. Therefore, the deployment cost of the access network element is saved.
  • the LIPA or SIPTO PDN connection it is determined at S12 whether the LIPA or SIPTO PDN connection can be activated based on the information related to establishing the LIPA or SIPTO PDN connection, and the identity of the LIPA or SIPTO PDN connection is saved.
  • the TEID and the IP address assigned by the access network element to the user are notified to the local gateway via, for example, a change notification request, the related information of the LIPA or SIPTO PDN connection may be established to determine the home access.
  • the system architecture is a LIPA or SIPTO PDN connection
  • the message that does not need to be processed by the serving gateway but only needs to be forwarded sends the TEID and IP address allocated by the access network element to the user, thereby realizing the connectivity of LIPA or SIPTO.
  • Fig. 7 it is shown how to establish a tunnel connection between an access network element and a local gateway when establishing a LIPA or SIPTO PDN.
  • LIPA or SIPTO PDN connection After the LIPA or SIPTO PDN connection has been established, other conditions may occur depending on the change of the communication environment, for example, the release of the Sl/Iu connection, the service request, and the access network element due to the movement of the user equipment. Switch and so on. In the following, some of these cases will be explained in conjunction with Figs. 8 through 11.
  • FIG. 8 is a diagram showing the flow of connection release between the local gateway and the access network element when the Sl/Iu connection is released.
  • the Sl/Iu connection release usually occurs when the user no longer performs services and transitions from the connected state to the idle state, when the wireless resources are released.
  • S21 when the Sl/Iu connection is released, the access network element or the mobility management network element initiates the Sl/Iu release process to release the radio side resources.
  • S22 performing other processes of Sl/Iu release, thereby completing the release of Sl/Iu.
  • those skilled in the art can understand which processes are required to complete the release of the Sl/Iu in addition to the flow shown in the figure.
  • S23 The radio resource, including the resource allocated by the access NE for the user, has been released. According to the flag when establishing the LIPA or SIPTO PDN connection (refer to S12 in FIG. 7), the mobility management NE determines that the LIPA or SIPTO PDN exists. Connect, send a Change Notification Request message to the local gateway. S23. After receiving the change notification request message, the local gateway sends the downlink data packet to the serving gateway. In the embodiment of the present invention, the local gateway is notified that the sending of the downlink data packet to the service gateway may be specifically as follows:
  • the mobility management network element includes the user plane information allocated by the service gateway for the user in the change notification request message, and sends the information to the local gateway.
  • the allocated user plane information of the serving gateway is sent by the serving gateway to the mobility management network element when establishing the PDN connection (refer to step S13 in FIG. 7).
  • the local gateway locally saves the received user plane information, and after receiving the downlink data packet, sends the downlink data packet to the service gateway according to the received user plane information, specifically Therefore, the destination TEID and the IP address of the downlink data packet are filled in as the TEID and the IP address allocated by the serving gateway, so that the downlink data packet is sent to the serving gateway.
  • the mobility management network element indicates that the local gateway radio resource is unavailable or switches the user plane in the change notification request message.
  • the local gateway After receiving the change notification request message, the local gateway sends the user downlink data to the serving gateway according to the user plane information allocated by the received service gateway.
  • the manner of the local gateway or the serving gateway is specifically referred to S12 of FIG.
  • the purpose of S23 is to instruct the local gateway to send the downlink data packet to the serving gateway by the mobility management network element, and the indication may be a direct indication, such as mode 2, or an indirect indication.
  • the embodiments of the present invention are not intended to be any specific limitation.
  • the local gateway sends the change notification response (Change Notification Response) message to the mobility management network element via the serving gateway, thereby completing the release process between the access network element and the local gateway.
  • Change Notification Response Change Notification Response
  • the connection between the local gateway and the access network element is released, and when the Iu or S1 connection of the user is released, the radio resource is deleted, and the mobility management network element is deleted.
  • the local gateway can be notified in time to send downlink data to the service gateway to prevent the downlink data of the user from being lost.
  • the processing of the service gateway is not required, and the service gateway upgrade is avoided, which not only ensures the service but also saves the upgrade cost of the operator.
  • Fig. 9 is a diagram showing the flow when the user device makes a service request after the Sl/Iu connection is released.
  • S31 the user equipment sends a Service Request message to the access network element.
  • S32 The mobility management network element determines whether the user has a LIPA or SIPTO PDN connection. If it is determined that the user has a LIPA or SIPTO PDN connection, the mobility management network element sends an Initial Context Setup Request message to the access network element.
  • a RAB assignment request message includes a TEID and an IP address assigned by the local gateway to the user, where the IP address is the above LGW@LN.
  • the mobility management network element obtains the TEID and IP address assigned by the local gateway to the user in S13 of FIG. 7 and keeps it in the context of the user.
  • the access NE saves the TEID and L-GW@LN allocated by the local gateway to the user, and sends an Initial Context Setup response message or a RAB assignment response to the mobility management network element.
  • the message includes the TEID assigned by the access NE to the user and the IP address used for interaction with the local gateway, that is, the above H(e)NB@LN.
  • the mobility management network element After receiving the initial context setup response message, because the established radio bearer belongs to the LIPA or SIPTO PDN connection, the mobility management network element accesses the user plane information allocated by the network element, that is, the TEID+IP address is included in the change notification request.
  • the (change notification request) message is sent to the service gateway. After receiving the message, the service gateway forwards the message to the local gateway.
  • the local gateway saves the TEID and the IP address allocated by the access NE, and sends a change notification response message to the serving gateway, and the monthly service gateway forwards the message to the mobility management network element.
  • the local gateway when downlink data is sent to the local gateway, the local gateway directly sends the data packet to the access network element according to the TEID and IP information allocated by the access network element, and when When receiving the uplink data from the user, the access network element sends the uplink data to the local gateway according to the TEID and IP information allocated by the local gateway, and then the local gateway sends the uplink data to the destination address.
  • the user plane information of the access network element can be stored in a cell that is not processed by the monthly service gateway, such as Private Extension.
  • the user equipment After the release of the Sl/Iu connection shown in FIG. 9, the user equipment makes a service request again.
  • the mobility management network element can notify the local gateway in time.
  • the downlink data is directly sent to the access network element, which reduces the data forwarding path bypass and saves transmission costs.
  • the service gateway upgrade is avoided due to the change of the notification request message, which is processed by the service gateway, which saves the upgrade cost of the operator.
  • Figure 10 is a diagram showing the flow of how to establish a tunnel connection between a new access network element and a local gateway when the access network element changes.
  • the user equipment moves, for example, from one cell to another, it may access the target access network element from the source access network element, and when the access network element changes
  • the mobility management network element corresponding to the mobility management network element may also be changed, that is, the source mobility management network element is accessed from the source mobility management network element.
  • Figure 10 depicts the tunnel connection between the new access network element and the local gateway in this case.
  • S41 receiving a UE measurement report to determine a handover, such as a radio parameter level of a target cell, etc., to achieve a handover requirement.
  • the source access NE sends a Handover Required message to the source mobility management network element.
  • the source mobility management network element sends a forward relocation request (Forward Relocation Request) message to the target mobility management network element, where the message includes a TEID and an IP address allocated by the local gateway for the user, where the IP address is L-GW@ LN.
  • Forward Relocation Request Forward Relocation Request
  • the source mobility management network element needs to indicate in the message which of the target side is a LIPA or SIPTO PDN connection, and the indication may be an indication cell displayed, such as
  • the LIPA indication (LIPA indication) may also be an implicit indication cell. For example, if L-GW@LN exists in the context except L-GW@CN, it indicates that the PDN is LIPA or SIPTO PDN. S44. Perform other switching processes from the source access NE to the target access NE. Here, those skilled in the art can understand which processes are required for the switching of the access network element. In order to highlight the key points of the embodiments of the present invention, details are not described herein.
  • the target mobility management network element sends a handover request (Handover Request) message to the target access network element, where the handover request message includes a TEID and an IP address allocated by the local gateway to the user.
  • the access network element saves the received information and sends a Handover Response message to the target mobility management network element.
  • the handover request response message includes the user plane information allocated by the access network element for the LIPA or the SIPTO PDN connection, that is, the TEID and the IP address, where the IP address is a Forward Relocation Response message.
  • the handover request message, the forward handover request message, the handover request message, the handover response message, and the forward handover response message include a change process of the target establishment.
  • those skilled in the art can understand which processes are needed for the handover of the mobility management network element. In order to highlight the key points of the embodiments of the present invention, details are not described herein.
  • the mobility management network element notifies the serving gateway to send an update message to the local gateway to update the downlink user plane information saved by the local gateway.
  • the mobility management network element sends the user plane information allocated by the access network element, that is, the TEID+IP address, in the Change Notification Request message, to the serving gateway, where the TEID
  • the IP address information is encapsulated in a cell that is not processed by the serving gateway.
  • the Private Extension refers to the process of establishing a tunnel connection between the access NE and the local gateway as shown in FIG. 7. After receiving the message, the service gateway forwards the message to the local gateway.
  • the local gateway saves the TEID and IP information allocated by the access network element, and sends a change notification response (Change Notification Response) message to the monthly service gateway, and the service gateway further forwards the response message to the mobility management network element.
  • the local gateway directly sends the data packet to the access network element according to the TEID and IP information allocated by the access network element, and when When receiving the uplink data from the user, the access network element sends the uplink data to the local gateway according to the TEID and IP information allocated by the local gateway, and then the local gateway sends the uplink data to the destination address.
  • the local gateway is notified to send downlink data to the new access network element to prevent the data packet from being dropped and improve the user experience.
  • the change notification request message is processed by the service gateway, for example, the service gateway upgrade is avoided, and the upgrade cost of the operator is saved.
  • the mobility management network element does not change during the handover process in which the access network element changes, the S43, S46, and S47 in FIG. 10 are omitted, and the source mobility management network element and the target are in this case.
  • the mobility management network element is the same network element.
  • FIG. 11 is a diagram showing the x2 or RNC enhanced handover procedure when the access network element changes.
  • the access NEs can complete the handover process and then notify the mobility management NE to reduce the impact on the mobility management NE.
  • S51 first receives a UE measurement report to determine a handover, such as a radio parameter level of a target cell, to reach a handover requirement.
  • S52 other processes for performing the x2 switchover or other processes of the enhanced RNC switch, and those skilled in the art can understand which processes are needed for the above-mentioned handover, and the details of the embodiments of the present invention are not limited herein.
  • S53 is a diagram showing the x2 or RNC enhanced handover procedure when the access network element changes.
  • the target access NE sends a Path Switch Request message to the mobility management network element to request to update the downlink user plane information, where the message includes the access network element being connected to the LIPA or the SIPTO PDN.
  • the assigned user plane information that is, the TEID and IP address, where the IP address is H(e)NB@LN. S54.
  • the mobility management network element notifies the monthly service gateway to update the downlink user plane information by tampering with the Modify Bearer Request/Response.
  • step S55 determining that it is a LIPA or SIPTO PDN connection (refer to step S12 shown in FIG. 7 for the manner of determining the LIPA or SIPTO PDN), and the mobility management network element accesses the user plane information allocated by the network element, that is, the TEID+IP address. This is sent to the service gateway in the Change Notification Request message. After receiving the message, the service gateway forwards the message to the local gateway.
  • the local gateway saves the TEID and the IP address allocated by the access network element, and sends a change notification response (Change Notification Response) message to the serving gateway, where the service gateway sends the message to the mobility management network element.
  • a change notification response (Change Notification Response) message
  • the TEID+IP address can be encapsulated in a special cell in the change notification message, which is not processed by the serving gateway and forwarded directly to the local gateway to avoid service gateway upgrade.
  • the mobility management network element sends a path switch acknowledgement message (Path Switch Acknowledge) to the target access NE to confirm that the path switch is completed.
  • Path Switch Acknowledge a path switch acknowledgement message
  • the local gateway when the downlink data is sent to the local gateway, the local gateway sends the data packet directly to the access network element according to the user plane information allocated by the access network element, and is connected.
  • the incoming network element receives the uplink data from the user, according to the user plane information allocated by the local gateway, The uplink data is sent to the local gateway, and then sent by the local gateway to the destination address.
  • the mobility management network element can notify the local gateway to send the downlink data to the new access network element in time when the access network element of the user equipment is changed. , to avoid packet loss, and improve the user experience.
  • the notification notification request message is processed by the service gateway, the service gateway upgrade is avoided, and the upgrade cost of the operator is saved.
  • FIG. 12 is a block diagram showing an apparatus for implementing mobility of LIPA or SIPTO, which may be included in a mobility management network element, in accordance with an embodiment of the present invention.
  • the device 100 includes: a receiving device 101, which receives, from an access network element, a tunnel endpoint identifier TEID and a first IP address allocated by the access network element to the user equipment, where the first IP address is used by the access network element The IP address of the local gateway is used by the local gateway; the sending device 102 sends the first message to the local gateway by using the forwarding of the serving gateway, where the first message includes the TEID and the first IP address allocated by the access network element for the user equipment, and the first message The TEID and the first IP address do not need to be processed by the serving gateway and only need to be forwarded.
  • the mobility function under the LIPA or SIPTO PDN connection can be implemented without upgrading the service gateway, and therefore, by avoiding the upgrade of the service gateway, It saves operators' deployment and maintenance costs.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
  • Another point that is shown or discussed between each other The coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

Abstract

La présente invention concerne un procédé et un appareil permettant la réalisation de mobilité de connexion d'accès IP local (LIPA) ou de délestage de trafic IP sélectionné (SIPTO). Le procédé comprend les étapes suivantes: l'identifiant de point d'extrémité de tunnel (TEID) et d'une première adresse IP allouée par l'élément de réseau d'accès pour l'équipement utilisateur sont reçus en provenance de l'élément de réseau d'accès, la première adresse IP étant l'adresse IP utilisée par l'élément de réseau d'accès pour une interaction avec la passerelle locale ; l'identifiant TEID et la première adresse IP allouée par l'élément de réseau d'accès pour l'équipement utilisateur sont transmis à la passerelle locale via la passerelle de desserte, l'identifiant TEID et la première adresse IP étant reçus et réacheminés vers la passerelle locale par la passerelle de desserte. Selon le procédé et l'appareil pour la réalisation de mobilité d'accès IP local (LIPA) ou de délestage de trafic IP sélectionné (SIPTO), la fonction de mobilité sous la connexion de réseau public de transmission de données (PDN) de connexion d'accès IP local (LIPA) et de délestage de trafic IP sélectionné (SIPTO) peut être réalisée sans mise à niveau de la passerelle de desserte, permettant donc d'économiser le coût de déploiement et de maintenance d'opérateurs en évitant la mise à niveau de la passerelle de desserte.
PCT/CN2011/076450 2011-06-27 2011-06-27 Procédé et appareil permettant la réalisation de mobilité de connexion d'accès ip local ou de délestage de trafic ip sélectionné WO2012167460A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201180001542.5A CN103155683B (zh) 2011-06-27 2011-06-27 实现lipa或sipto的移动性的方法和设备
PCT/CN2011/076450 WO2012167460A1 (fr) 2011-06-27 2011-06-27 Procédé et appareil permettant la réalisation de mobilité de connexion d'accès ip local ou de délestage de trafic ip sélectionné

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/076450 WO2012167460A1 (fr) 2011-06-27 2011-06-27 Procédé et appareil permettant la réalisation de mobilité de connexion d'accès ip local ou de délestage de trafic ip sélectionné

Publications (1)

Publication Number Publication Date
WO2012167460A1 true WO2012167460A1 (fr) 2012-12-13

Family

ID=47295355

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/076450 WO2012167460A1 (fr) 2011-06-27 2011-06-27 Procédé et appareil permettant la réalisation de mobilité de connexion d'accès ip local ou de délestage de trafic ip sélectionné

Country Status (2)

Country Link
CN (1) CN103155683B (fr)
WO (1) WO2012167460A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110248387A (zh) * 2018-03-08 2019-09-17 海能达通信股份有限公司 移动通信方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3661167B1 (fr) * 2013-06-26 2022-08-10 Huawei Technologies Co., Ltd. Système et procédé d'attribution d'adresses ip

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002000001A2 (fr) * 2000-06-30 2002-01-03 Ingenium Pharmaceuticals Ag Recepteur igpcr20 couple a la proteine g humaine, et utilisations correspondantes
CN101998370A (zh) * 2009-08-21 2011-03-30 中兴通讯股份有限公司 一种本地ip访问连接的释放系统及方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101652442B1 (ko) * 2009-05-05 2016-08-30 엘지전자 주식회사 이동통신 네트워크 내에서 제어 평면（Ｃｏｎｔｒｏｌ Ｐｌａｎｅ）을 담당하는 서버 및 커넥션 설정을 제어하는 방법

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002000001A2 (fr) * 2000-06-30 2002-01-03 Ingenium Pharmaceuticals Ag Recepteur igpcr20 couple a la proteine g humaine, et utilisations correspondantes
CN101998370A (zh) * 2009-08-21 2011-03-30 中兴通讯股份有限公司 一种本地ip访问连接的释放系统及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP TSG SA WG2 MEETING #80 TD, S2-103495, 3 September 2010 (2010-09-03), pages 6 - 9, 12, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_80_Brunstad/Docs/S2-103495.zip> *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110248387A (zh) * 2018-03-08 2019-09-17 海能达通信股份有限公司 移动通信方法
CN110248387B (zh) * 2018-03-08 2021-04-27 海能达通信股份有限公司 移动通信方法

Also Published As

Publication number Publication date
CN103155683B (zh) 2015-11-25
CN103155683A (zh) 2013-06-12

Similar Documents

Publication Publication Date Title
JP6148294B2 (ja) 相異なるワイヤレス通信アーキテクチャ間のモビリティのための資源管理
JP5426025B2 (ja) 移動ネットワークにおいてユーザ・プレーン・データをルーティングする方法、装置、及びシステム
AU2010338889B2 (en) Traffic offload method, traffic offload function entity and traffic offload system
US9167413B2 (en) Local breakout with parameter access service
CN103609150B (zh) 基于apn专有或者非apn专有信息经由本地网络进行流量分流
US10779357B2 (en) Method for avoiding handover failure
US11129054B2 (en) Methods, systems and devices for supporting local breakout in small cell architecture
US8842636B2 (en) Method and device for managing Internet Protocol offload connection
US20110235605A1 (en) Radio resource allocation method and device of henb in evolved packet system
WO2009094916A1 (fr) Procédé, système et dispositif de commande pour redémarrage après défaillance dans le domaine circuit
WO2011020386A1 (fr) Procédé d&#39;indication, système pour un type de porteur et élément de réseau de dérivation de transmission
JP2015053706A (ja) 通信システムと通信制御方法
KR20130014398A (ko) 핸드오버 지원 장치 및 방법
EP1871050B1 (fr) Réseau Wimax, élément de réseau Wimax et un procédé de traitement de la qualité de service
WO2011026392A1 (fr) Procédé et système d&#39;acquisition de stratégies d’itinéraire
WO2011054320A1 (fr) Procédé, dispositif et système permettant de transférer un service de protocole internet du réseau fédérateur
WO2011035732A1 (fr) Procédé, dispositif et système de commande pour un accès ip local ou un déchargement de trafic ip sélectionné
WO2011143997A1 (fr) Procédé et dispositif de routage
WO2013033883A1 (fr) Procédé de traitement de basculement, élément de réseau de gestion de mobilité, et élément et système de réseau d&#39;accès sans fil
WO2011023125A1 (fr) Procédé, dispositif et système pour libération de connexion
WO2011144000A1 (fr) Procédé et appareil de sélection de route
WO2012126319A1 (fr) Procédé et système pour le transfert intercellulaire d&#39;un service d&#39;accès local
WO2011109999A1 (fr) Procédé d&#39;indication de données et élément de réseau de gestion de mobilité
WO2011157100A1 (fr) Procédé et système de mise en cache de données
WO2012167460A1 (fr) Procédé et appareil permettant la réalisation de mobilité de connexion d&#39;accès ip local ou de délestage de trafic ip sélectionné

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180001542.5

Country of ref document: CN

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

Ref document number: 11867380

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

Country of ref document: EP

Kind code of ref document: A1