[go: up one dir, main page]

WO2016101616A1 - 园区业务访问的方法、装置及系统 - Google Patents

园区业务访问的方法、装置及系统 Download PDF

Info

Publication number
WO2016101616A1
WO2016101616A1 PCT/CN2015/085355 CN2015085355W WO2016101616A1 WO 2016101616 A1 WO2016101616 A1 WO 2016101616A1 CN 2015085355 W CN2015085355 W CN 2015085355W WO 2016101616 A1 WO2016101616 A1 WO 2016101616A1
Authority
WO
WIPO (PCT)
Prior art keywords
campus
henb
user terminal
mme
information
Prior art date
Application number
PCT/CN2015/085355
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 WO2016101616A1 publication Critical patent/WO2016101616A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, device, and system for accessing a campus service.
  • the Local IP Access (LIPA) connection is mainly used for a single residential or enterprise network.
  • the LIPA technology proposed by the 3GPP protocol can separate the user's local service data directly from the base station of the campus (home/enterprise). On the one hand, it avoids the pressure on the core network after the rapid increase of IP data traffic, and on the other hand, the IP is improved. The routing efficiency of the packet. This not only reduces the burden on the core network, reduces the core network throughput and transmission cost of the operator, but also reduces the data transmission delay of the user's local data access.
  • the LIPA technology is an enhancement to the function of the Home Node B (HeNB), which allows the terminal to directly access the IP resources inside the campus through the HeNB. It is usually used by the operator to build campus services based on HeNB.
  • HeNB Home Node B
  • the 23.401 protocol of 3GPP explicitly states that the connection enabling LIPA does not support Handover (referred to as HO):
  • the Mobile Management Entity receives the Path Switch Request message. If the MME determines that the LIPA connection is not released, the MME replies with the path switch request failure message. Switch Request Failure message) to the target HeNB;
  • the MME When the S1 interface H0, the MME receives the handover request message (Handover Request message). If the MME determines that the LIPA connection is not released, the MME returns a Handover Failure (Cause) message to the target HeNB.
  • Handover Request message the handover request message
  • the MME determines that the LIPA connection is not released, the MME returns a Handover Failure (Cause) message to the target HeNB.
  • LGW Local Gateway Way
  • the LGW is initially powered on. After obtaining the IP address from the Serving Gateway (S-GW), the LGW registers with the DNS server.
  • the registration includes: Local Network ID (Local) H(e)NB Network identifier is abbreviated as LHN ID), local network
  • L-GW@Local network address is abbreviated as L-GW@LN) or the Fully Qualified Domain Name (L-GW local FQDN) of the local network, and the L-GW@CN address assigned by the S-GW.
  • the MME initiates a DNS request to the DNS server when receiving the Public Data Network (PDN) connection request of the LIPA of the user UE, and the DNS server returns one or more LGW IP addresses that meet the conditions to the MME;
  • PDN Public Data Network
  • Each HeNB itself configures all L-GW@LN addresses or FQDNs that are connected to the LGW.
  • the HeNB obtains the L-GW@CN address through the Sxx port.
  • the HeNB reports the L-GW@CN address or FQDNs to the MME through the S1 message.
  • the L-GW table (List) provided by the core network MME in the HeNB based on the Access Point Name (APN) and the Local H(e)NB Network ID (LHN ID) choose an L-GW.
  • the 23.859 protocol of 3GPP proposes how to ensure the continuity of the IP data session when the LIPA connection moves between the eNB/HeNB supporting LIPA when the UE moves within the campus (home/enterprise).
  • the campus home/enterprise
  • the present invention provides a method, apparatus and system for accessing a campus service, with at least one of the above problems.
  • a method for accessing a campus service including: a mobility management entity MME acquiring an access point name APN information and a campus information of a user terminal; and the MME obtaining a valid subscription from a home location register HSS Obtaining, by the MME, whether the APN that the user terminal requests to access supports the local IP access LIPA; the MME receives whether the acquisition of the user terminal supports the LIPA bearer information; and the MME is established according to the user terminal.
  • the APN bearer information, the HeNB capability, and the attributes of the HSS number are judged; the MME establishes a relationship between the link base station and the local gateway L-GW according to the base station capability of the user terminal, and allows the user to Accessing the local service of the campus, or the MME modifies the relevant bearer information of the server gateway S-GW and the L-GW, establishes a link channel of the SGW and the LGW, and completes the switching of the data channel.
  • the acquiring, by the mobility management entity MME, the access point name APN information and the campus information of the user terminal includes: in the case of the public data network coverage of the user terminal, initiating a local connection to the MME APN information and park information.
  • the MME performs a determination process according to the APN bearer information, the HeNB capability, and the attributes of the HSS number set that the user terminal has established; the MME selects an appropriate link to pass.
  • the access of the local gateway L-GW to the local service of the campus includes: when the APN requested by the user terminal supports the LIPA, and the HeNB in the campus does not support the LIPA, or the APN requested by the user terminal supports the LIPA, The HeNB in the campus also supports the LIPA, and the MME requests the access to the campus to be inconsistent with the campus to which the user terminal belongs; the MME queries the domain name system DNS server for the user terminal according to the APN information and the campus information carried by the user terminal.
  • the MME creates a L-GW session, and the MME sends a bearer installation message to the HeNB, where The user plane data channel of the HeNB communicates with the L-GW through the S-GW; the MME uses the S-GW@LN address of the S-GW and the TEID of the S-GW tunnel endpoint as the parameters of the internal channel of the L-GW. Brought to the L-GW for the end of the user The terminal accesses the data service in the park through the data channel of the S-GW and the L-GW outside the campus.
  • the MME performs a judgment process according to the APN bearer information, the HeNB capability, and the attributes of the HSS number set that the user terminal has established, and the MME modifies the server gateway S-GW.
  • the L-GW related bearer information, and the data channel switching includes: when the user terminal does not support the LIPA connection park to support the HO handover in the LIPA connection campus, the target HeNB supports the LIPA function in the campus.
  • the MME obtains the local base station network LHN ID or the L-GW@CN List/FQDNs and the HeNB@LN address; the APN currently established by the user terminal and the L-GW of the campus have a bearer establishment, and the target HeNB supports Establishing a LIPA connection with the L-GW accessed by the user terminal, the MME establishing a LIPA channel for the HeNB and the L-GW for the user terminal; the MME modifying the bearer information of the S-GW, and modifying the S-GW@LN address
  • the tunnel endpoint of the /S-GW identifies the TEID of the HeNB@LN/HeNB and modifies the associated bearer information of the L-GW; the MME sends the associated identity Correlation-ID to the target HeNB, and the Correlation-ID includes the L- GW@LN address/TEID of the internal tunnel of the L-GW, used for Standard HeNB user plane data through the channel connected to the target HeNB L-GW.
  • the MME performs a judgment process according to the APN bearer information, the HeNB capability, and the attributes of the HSS number set that the user terminal has established, and the MME modifies the server gateway S-GW.
  • the related bearer information of the L-GW, and the switching between the inbound and outbound data channels includes: the APN established by the user terminal UE when the user terminal supports the handover from the LIPA connection campus to the outside of the LIPA campus.
  • the MME modifies the bearer information of the S-GW, and modifies The TEID of the HeNB@LN/HeNB is the TEID of the S-GW@LN address/S-GW, and the related bearer information of the L-GW is modified; the MME establishes a channel with the L-GW through the S-GW, and the user of the HeNB The surface data channel is connected to the L-GW through the S-GW.
  • the HO handover includes: HO handover of the X2 interface; the S1 interface HO handover procedure and the Sxx interface, that is, the signaling transmission of the support control plane, and the message transmission HO handover of the user plane.
  • the campus information includes at least one of the following: an LHN ID, an LGW@CN List, an IP address of an internal channel of the HeNB, a HeNB@LN IP Addr, and a TEID of an internal channel of the HeNB.
  • an apparatus for accessing a campus service comprising: an obtaining module, configured to acquire, by the mobility management entity MME, an access point name APN information and a campus information of the user terminal; and a support module,
  • the MME is configured to obtain valid subscription information from the home location register HSS, and learn whether the APN requested by the user terminal supports local IP access LIPA; and the base station module is configured to receive, by the MME, the user terminal to attach Whether the acquisition supports the LIPA bearer information;
  • the determining module is configured to determine, according to the APN bearer information that the user terminal has established, the HeNB capability, and the attributes of the HSS numbering;
  • the access module sets The MME establishes a relationship between the link base station and the local gateway L-GW according to the base station capability of the user terminal, and allows the user to access the local service of the campus, or the MME modifies the server gateway S-GW and L- The bearer channel of the GW is established, and the link channel of the SGW
  • the obtaining module is further configured to initiate locally connected APN information and campus information to the MME in case the public data network coverage of the user terminal.
  • the APN that the user terminal requests to access supports the LIPA
  • the HeNB in the campus does not support the LIPA
  • the APN requested by the user terminal supports the LIPA
  • the HeNB in the campus The LIPA is also supported.
  • the determining module is configured to query the domain name system DNS server according to the APN information and the campus information carried by the user terminal.
  • the access module is configured to create the MME and the L-GW session, and the MME delivers the bearer.
  • the installation message is sent to the HeNB, where the user plane data channel of the HeNB communicates with the L-GW through the S-GW; the access module is configured to set the S-GW@LN address and S of the S-GW by the MME.
  • the GW tunnel endpoint identification TEID is carried to the L-GW as a parameter of the internal channel of the L-GW, and is used for the user terminal to perform intra-satellite data service access through the data channels of the S-GW and the L-GW in and out of the garden.
  • the determining module obtains the local base station network LHN ID or the L-GW@CN List/FQDNs and the HeNB@LN address; the access module is configured to be carried by the APN currently established by the user terminal and the L-GW of the campus.
  • the target HeNB supports establishment of an L-GW connected to the user terminal
  • the LIPA is connected, and the MME establishes a LIPA channel of the HeNB and the L-GW to the user terminal;
  • the access module is configured to modify the bearer information of the S-GW by the MME, and modify the tunnel of the S-GW@LN address/S-GW
  • the endpoint identifies the TEID as the TEID of the HeNB@LN/HeNB, and modifies the related bearer information of the L-GW.
  • the access module is configured to send the associated identity Correlation-ID to the target HeNB, and the Correlation-ID includes the L- The TEID of the internal tunnel of the GW@LN address/L-GW, and the user plane data channel for the target HeNB is connected to the target HeNB through the L-GW.
  • the user terminal supports the establishment of the LIPA connection of the L-GW of the campus by the APN established by the user terminal UE in the case that the user terminal supports the handover from the LIPA connection campus to the outside of the LIPA campus. If the target HeNB outside the campus does not support the establishment of the LIPA connection with the L-GW accessed by the mobile terminal, the access module is configured to modify the bearer information of the S-GW by the MME, and modify the HeNB@LN/HeNB.
  • the TEID is the TEID of the S-GW@LN address/S-GW, and modifies the relevant bearer information of the L-GW; the access module is configured to set up, by the S-GW, the channel of the L-GW through the S-GW, and the HeNB The user plane data channel is connected to the L-GW through the S-GW.
  • the HO handover includes: HO handover of the X2 interface; the S1 interface HO handover procedure and the Sxx interface, that is, the signaling transmission of the support control plane, and the message transmission HO handover of the user plane.
  • the campus information includes at least one of the following: an LHN ID, an LGW@CN List, an IP address of an internal channel of the HeNB, a HeNB@LN IP Addr, and a TEID of an internal channel of the HeNB.
  • a system for accessing a campus service comprising: the apparatus of any of the above.
  • the MME obtains the access point name APN information and the campus information of the user terminal by using the mobility management entity MME.
  • the MME obtains the valid subscription information from the home location register HSS, and learns whether the APN requested by the user terminal supports the local IP address. Accessing the LIPA; the MME receives whether the acquisition of the user terminal supports the LIPA bearer information; the MME determines according to the APN bearer information, the HeNB capability, and the attributes of the HSS number that have been established by the user terminal.
  • the MME establishes a relationship between the link base station and the local gateway L-GW, so that the user accesses the local service of the campus, or the MME modifies the server gateways S-GW and L according to the base station capability of the user terminal.
  • the relevant bearer information of the GW establish a link channel of the SGW and the LGW, and complete the switching of the data channel.
  • FIG. 1 is a flowchart of a method for accessing a campus service according to an embodiment of the present invention
  • FIG. 2 is a structural block diagram of an apparatus for accessing a campus service according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a comparative description of accessing a campus network inside and outside a campus according to a preferred embodiment of the present invention
  • FIG. 4 is a schematic diagram of a process for a UE to perform an access request for a campus APN outside a campus according to a preferred embodiment of the present invention
  • FIG. 5 is a schematic diagram of an X2 HO process in a campus outbound campus in accordance with a preferred embodiment of the present invention
  • FIG. 6 is a schematic diagram of an X2 HO process outside a campus in a campus in accordance with a preferred embodiment of the present invention.
  • FIG. 1 is a flowchart of a method for accessing a campus service according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:
  • Step S102 The mobility management entity MME acquires the access point name APN information and the campus information of the user terminal.
  • Step S104 The MME obtains valid subscription information from the home location register HSS, and learns whether the APN requested by the user terminal supports local IP access to the LIPA.
  • Step S106 The MME receives whether the acquisition of the user terminal attachment supports LIPA bearer information.
  • Step S108 The MME performs a determination process according to the APN bearer information that the user terminal has established, the HeNB capability, and the attribute of the HSS number.
  • Step S110 The MME establishes a relationship between the link base station and the local gateway L-GW according to the base station capability of the user terminal, and allows the user to access the local service of the campus, or the MME modifies the server network.
  • the related bearer information of the S-GW and the L-GW is set, the link channel of the SGW and the LGW is established, and the switching of the data channel is completed.
  • the mobility management entity MME is used to obtain the access point name APN information and the campus information of the user terminal; the MME obtains valid subscription information from the home location register HSS, and learns whether the APN requested by the user terminal supports the local IP address. Accessing the LIPA; the MME receives whether the acquisition of the user terminal supports the LIPA bearer information; the MME performs the judgment processing according to the APN bearer information that the user terminal has established, the HeNB capability, and the attributes of the HSS number; The MME establishes a relationship between the link base station and the local gateway L-GW, and allows the user to access the local service of the campus, or the MME modifies the relevant bearer information of the server gateway S-GW and the L-GW.
  • the mobile management entity MME acquiring the access point name APN information and the campus information of the user terminal may include: initiating the locally connected APN information to the MME in the case that the user terminal is over the public data network coverage Park information.
  • the MME performs a determination process according to the APN bearer information that the user terminal has established, the HeNB capability, and the attributes of the HSS number; the MME selects an appropriate link to the campus through the local gateway L-GW.
  • the service access includes: the APN requested to be accessed by the user terminal supports LIPA, and the HeNB in the campus does not support LIPA, or the APN requested by the user terminal supports LIPA, and the HeNB in the campus also supports LIPA, requesting access. If the campus is inconsistent with the campus to which the user terminal belongs;
  • the MME queries the domain name system DNS server for the L-GW@LN, L-GW@CN List/full qualified domain name FQDNs information of the campus APN applied by the user terminal according to the APN information and the campus information carried by the user terminal;
  • the MME creates an L-GW session, and the MME sends a bearer installation message to the HeNB, where the user plane data channel of the HeNB communicates with the L-GW through the S-GW;
  • the MME brings the S-GW@LN address of the S-GW and the S-GW tunnel endpoint identification TEID to the L-GW as parameters of the internal channel of the L-GW, and the user terminal passes the S-GW and the L outside the campus.
  • the MME acquires the local base station network LHN ID. Or L-GW@CN List/FQDNs, HeNB@LN address;
  • the APN currently established by the user terminal and the L-GW of the campus have a bearer establishment, and the target HeNB supports establishing an LIPA connection with the L-GW accessed by the user terminal, and the MME establishes the HeNB and the L-GW for the user terminal.
  • LIPA channel ;
  • the MME modifies the bearer information of the S-GW, and modifies the TEID of the tunnel endpoint identification TEID of the S-GW@LN address/S-GW to be the HeNB@LN/HeNB, and modifies the relevant bearer information of the L-GW;
  • the MME sends an association identity Correlation-ID to the target HeNB, where the Correlation-ID includes the TEID of the L-GW@LN address/L-GW internal tunnel, and the user plane data channel of the target HeNB passes through the L-GW and the target HeNB. Connected.
  • the APN established by the user terminal UE supports the establishment of the LIPA connection of the L-GW of the campus, but outside the campus.
  • the target HeNB does not support the establishment of a LIPA connection with the L-GW accessed by the mobile terminal;
  • the MME modifies the bearer information of the S-GW, and modifies the TEID of the HeNB@LN/HeNB to the TE-ID of the S-GW@LN address/S-GW, and modifies the relevant bearer information of the L-GW;
  • the MME establishes a channel with the L-GW through the S-GW, and the user plane data channel of the HeNB is connected to the L-GW through the S-GW.
  • the HO handover includes: HO handover of the X2 interface; the S1 interface HO handover procedure and the Sxx interface, that is, the signaling transmission of the support control plane, and the message transmission HO handover of the user plane.
  • the campus information includes at least one of the following: an LHN ID, an LGW@CN List, an IP address of an internal channel of the HeNB, HeNB@LN IP Addr, and a TEID of an internal channel of the HeNB.
  • a device for accessing the campus service is provided, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 2 is a structural block diagram of an apparatus for accessing a campus service according to an embodiment of the present invention. As shown in FIG. 2, the apparatus includes:
  • the obtaining module 202 is configured to acquire, by the mobility management entity MME, an access point name APN information and a campus information of the user terminal;
  • the support module 204 is configured to: the MME obtains valid subscription information from the home location register HSS, and learns whether the APN requested by the user terminal supports local IP access LIPA;
  • the base station module 206 is configured to receive, by the MME, whether the acquisition of the user terminal attachment supports LIPA bearer information;
  • the determining module 208 is configured to determine, according to the APN bearer information that the user terminal has established, the HeNB capability, and the attribute of the HSS number.
  • the access module 210 is configured to establish, according to the base station capability of the user terminal, the relationship between the link base station and the local gateway L-GW, so that the user accesses the local service of the campus, or the MME modifies the server gateway S-GW.
  • the bearer channel of the SGW and the LGW is established, and the data channel is switched.
  • the MME obtains the access point name APN information and the campus information of the user terminal by using the MME.
  • the MME obtains the valid subscription information from the home location register HSS, and learns whether the APN requested by the user terminal supports the local IP address. Accessing the LIPA; the MME receives whether the acquisition of the user terminal supports the LIPA bearer information; the MME performs a judgment process according to the APN bearer information that the user terminal has established, the HeNB capability, and the attribute of the HSS number;
  • the base station capability of the user terminal, the MME establishes a relationship between the link base station and the local gateway L-GW, and allows the user to access the local service of the campus, or the MME modifies the related bearers of the server gateway S-GW and the L-GW.
  • the obtaining module 202 is further configured to initiate locally connected APN information and campus information to the MME in case the public data network coverage of the user terminal.
  • the HeNB in the campus does not support LIPA, or the APN requested by the user terminal supports LIPA, and the HeNB in the campus also supports LIPA, requesting to connect. If the entered campus is inconsistent with the campus to which the user terminal belongs;
  • the determining module 208 is configured to query the domain name system DNS server for the L-GW@LN of the campus APN requested by the user terminal according to the APN information and the campus information carried by the user terminal, and the L-GW@CN List/full qualified domain name FQDNs information;
  • the access module 210 is configured to create an L-GW session with the L-GW, and the MME sends a bearer installation message to the HeNB, where the user plane data channel of the HeNB communicates with the L-GW through the S-GW.
  • the access module 210 is configured to bring the S-GW@LN address of the S-GW and the S-GW tunnel endpoint identification TEID to the L-GW as parameters of the internal channel of the L-GW, and the user terminal is used in the park. In-garage data service access is performed through the data channels of the S-GW and the L-GW.
  • the determining module 208 is configured to obtain the MME.
  • the access module 210 is configured to establish a bearer between the APN currently established by the user terminal and the L-GW of the campus, and the target HeNB supports establishing an LIPA connection with the L-GW accessed by the user terminal, and the MME establishes a LIPA connection to the user terminal.
  • the access module 210 is configured to modify the bearer information of the S-GW, modify the tunnel endpoint identification TEID of the S-GW@LN address/S-GW to be the TEID of the HeNB@LN/HeNB, and modify the related bearer information of the L-GW. ;
  • the access module 210 is configured to send the association identity Correlation-ID to the target HeNB, where the Correlation-ID includes the TEID of the internal tunnel of the L-GW@LN address/L-GW, and the user plane data channel of the target HeNB is passed.
  • the L-GW is connected to the target HeNB.
  • the APN established by the user terminal UE supports the establishment of the LIPA connection of the L-GW of the campus, but the target outside the campus.
  • the HeNB does not support the establishment of a LIPA connection with the L-GW accessed by the mobile terminal;
  • the access module 210 is configured to modify the bearer information of the S-GW, modify the TEID of the HeNB@LN/HeNB to be the TEID of the S-GW@LN address/S-GW, and modify the related bearer information of the L-GW;
  • the access module 210 is configured to establish a channel with the L-GW through the S-GW, and the user plane data channel of the HeNB is connected to the L-GW through the S-GW.
  • the HO handover includes: HO handover of the X2 interface; the S1 interface HO handover procedure and the Sxx interface, that is, the signaling transmission of the support control plane, and the message transmission HO handover of the user plane.
  • the campus information includes at least one of the following: an LHN ID, an LGW@CN List, an IP address of an internal channel of the HeNB, HeNB@LN IP Addr, and a TEID of an internal channel of the HeNB.
  • a system for accessing a campus service including: the device of any of the above.
  • the above device can implement the above method.
  • the purpose of the preferred embodiment is to provide a method for accessing campus services outside the campus and to provide a method for supporting continuity of IP data when users (UEs) move between campus intranets.
  • the principle is that the MME selects the LGW accessed by the UE according to the APN/LHN ID information reported by the UE, and selects whether to support according to the L-GW@CN address or the LHN ID (Local H(e)NB Network ID) information reported by the HeNB.
  • LIPA function When the UE accesses outside the campus, the MME chooses to use a non-LIPA channel for local LGW access. When the UE accesses in the campus, the MME chooses to use the LIPA channel to access the local LGW.
  • the MME performs a data channel switching operation.
  • the method includes the following steps:
  • the first step After the LGW is powered on, the registration of the DNS server is completed.
  • the second step the UE initiates an access request of the campus APN. If the UE needs to connect to the campus during the initial access, the Ciphered Options Transfer Flag is set in the Attach request message, and the MME sends the message to the UE. The Ciphered Options are obtained, and the UE brings the Ciphered Options to the MME through a Ciphered Options Response (such as APN and campus information (such as LHN ID)). If the PDN is requested by the UE, the UE carries the APN and the related campus information (such as the LHN ID) through the PDN CONNECTIVITY REQUEST message.
  • APN APN
  • campus information such as LHN ID
  • the third step is: the HeNB attached to the UE determines, according to its own configuration capability, the MME to carry the LHN ID or the L-GW@CN List/FQDNs and the HeNB@LN address.
  • the fourth step the MME performs a judgment according to the HSS numbering information, the capability of the HeNB, and the request initiated by the UE, and determines whether the campus can be accessed and how to access the campus.
  • the fifth step is: when the UE moves from the campus to the outside of the campus, or moves from outside the campus to the campus, the MME performs data channel switching according to the capability of the base station and the connection currently established by the UE.
  • the preferred embodiment provides a method for accessing the campus service outside the campus, and provides a method for supporting the continuity of the IP data when the UE moves between the intranets.
  • the MME can select an appropriate one according to the specific scenario of the UE accessing.
  • the link accesses the local service through the LGW, and can solve the mobility of the eNB/HeNB (inside and outside the campus) where the LIPA capability is inconsistent, and realizes seamless handover inside and outside the campus.
  • FIG. 3 is a schematic diagram of a comparative description of accessing a campus network inside and outside a campus according to a preferred embodiment of the present invention, as shown in FIG.
  • the UE is in the campus, and the data packet is directly offloaded from the HeNB to the LGW through the local offloading technology.
  • the local data does not need to pass through the SGW, and the authentication is guaranteed by the core network numbering authority and the company authentication server;
  • the UE is outside the campus.
  • the data packet is sent to the LGW through the SGW.
  • the authentication mode and the authentication mode of the UE in the campus are unified, and are all guaranteed by the core network numbering authority and the company authentication server; and the ordinary VPN scheme: the data passes through the SGW/PGW, bypassing the company's external network VPN gateway.
  • the UE needs to install the VPN client, and the authentication authority is guaranteed by the external network VPN.
  • FIG. 4 is a schematic diagram of a process for a UE to perform an access request for a campus APN outside a campus according to a preferred embodiment of the present invention, as shown in FIG. 4 .
  • Step 1-3 The L-GW in the campus completes the registration process of power-on;
  • Step 4 The UE performs an access request for the campus APN outside the campus, and the UE passes the non-access stratum (NAS) message PDN Connectivity Request (where the APN and the campus information (eg, LHN ID) are carried. Related information) The PDN connection process that initiated the request.
  • NAS non-access stratum
  • PDN Connectivity Request where the APN and the campus information (eg, LHN ID) are carried.
  • LHN ID campus information
  • the PDN connection process that initiated the request.
  • the message is sent to the MME through the H1 S1 message Uplink NAS Transports, because the UE accesses outside the campus, the HeNB outside the campus does not support LIPA, so the Uplink NAS Transports does not carry the LHN ID or L-GW@CN List/FQDNs.
  • Information related to the campus LIPA bearer such as the HeNB@LN address.
  • Step 5 The MME obtains valid subscription information from the HSS, and learns whether the APN requested by the UE supports LIPA.
  • the MME determines the attributes of the UE request, the HeNB capability, and the HSS number. If the APN requested by the UE supports LIPA, but the HeNB does not support LIPA (or the APN requested by the UE supports LIPA, the HeNB in the park also supports LIPA, but is inconsistent with the campus to which the UE belongs), and the MME is carried according to the UE.
  • APN information and campus information eg, LHN ID
  • Step 7 the MME and the L-GW complete the session creation process
  • Step 8 The MME sends a Bearer Setup Request message to the HeNB, and does not carry a Correlation-ID.
  • the user plane data channel of the HeNB communicates with the L-GW through the S-GW.
  • Step 10 The MME uses the S-GW@LN address/S-GW TEID of the S-GW as a parameter of the "internal channel" of the L-GW through a Change Notification (Change Notification Request/Response message or a Modify Bearer Request/Response message) process. Brought to L-GW.
  • Change Notification Change Notification Request/Response message or a Modify Bearer Request/Response message
  • FIG. 5 is a schematic diagram of an X2 HO process in a campus outbound campus according to a preferred embodiment of the present invention, as shown in FIG. 5.
  • Step 1-2 Outside the campus (does not support LIPA connection), perform X2 HO to the campus (supporting LIPA connection), source HeNB-G and normal X2 HO flow, and control all radio resources (Radio Resource Control, RRC for short).
  • the information such as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) is sent to the target HeNB-YQ through the HO Request of X2.
  • the target HeNB-YQ completes the admission control, returns an ACK (Acknowledgement) to the source HeNB-G, and sends a SN (Serial Number) STATUS TRANSFER message to the source, and starts data back-transmission of the user plane.
  • the data channel of the L-GW is still sent by the L-GW to the HeNB-G through the S-GW.
  • Step 3 The HeNB-YQ in the campus supports the LIPA function, and brings the LHN ID or the L-GW@CN List/FQDNs and the HeNB@LN address to the MME through the S1 message Path Swtich Request.
  • the MME integrates the established APN bearer information, the HeNB capability, and the attributes of the HSS number to determine the UE. If the APN currently established by the UE has established a bearer in the L-GW of the supporting campus, and the target HeNB supports establishing an LIPA connection with the L-GW accessed by the UE, the MME establishes a LIPA channel of the HeNB and the L-GW to the UE;
  • Step 4-5 the MME first modifies the bearer information of the S-GW, and modifies the related bearer information of the L-GW (modifies the Tunnel Endpoint Identifier (TEID) of the S-GW@LN address/S-GW to TEID of HeNB@LN/HeNB);
  • TEID Tunnel Endpoint Identifier
  • Step 6 After the S-GW switches the data channel, after transmitting the user plane data, the end character EndMark is sent to the HeNB.
  • Step 7 The MME sends a Path Swtich Request ACK message to the HeNB, and carries the Correlation-ID (including the TEID of the L-GW@LN address/L-GW internal tunnel).
  • the user plane data channel of the HeNB is connected to the HeNB through the L-GW.
  • the source HeNB-G After receiving the Endmark sent by the S-GW, the source HeNB-G forwards the target to the target HeNB-YQ.
  • step 8-9 the target HeNB initiates release to the source HeNB, and performs a Tracking Area Update (TAU) process.
  • TAU Tracking Area Update
  • FIG. 6 is a schematic diagram of an X2 HO process outside a campus in a campus, as shown in FIG. 6, in accordance with a preferred embodiment of the present invention.
  • the X2 HO process outside the campus (which does not support LIPA connection) (for example, the Sxx port only supports user plane packet transmission) is as follows:
  • Step 1-2 In the campus (supporting LIPA connection), the X2 HO outside the campus (which does not support LIPA connection), the source HeNB-YQ and the normal X2 HO process, and all the RRC/E-RAB information are passed through the X2 HO request.
  • the target HeNB-G completes the admission control, returns an ACK to the source HeNB-YQ, and the source sends a SN STATUS TRANSFER message, and starts data back-transmission of the user plane.
  • the data channel of the L-GW is still sent to the HeNB-YQ through the LIPA connection.
  • Step 3 The HeNB-YQ in the campus does not support the LIPA function.
  • the Path Swtich Request message does not carry the LIPA-related information such as the LHN ID or the L-GW@CN List/FQDNs or the HeNB@LN address to the MME.
  • the MME integrates the established APN bearer information, the HeNB capability, and the attributes of the HSS number to determine the UE. If the APN currently established by the UE already has a bearer setup (LIPA connection) on the L-GW supporting the campus, but the target HeNB does not support establishing an LIPA connection with the L-GW accessed by the UE, and the MME establishes and L through the S-GW.
  • -GW channel LIPA connection
  • Step 4-5 the MME first modifies the bearer information of the S-GW (Serving Gateway), and modifies the related bearer information of the L-GW (modifies the TEID of the HeNB@LN/HeNB to be the S-GW@LN address/the TEID of the S-GW) );
  • Step 6 After the L-GW switches the data channel, the EndMark is sent to the source HeNB-YQ.
  • step 7 the MME sends a Path Swtich Request ACK message to the HeNB, and does not carry the related information of the LIPA.
  • the user plane data channel of the HeNB is connected to the L-GW through the S-GW.
  • step 8-9 the target HeNB initiates release to the source HeNB and performs a TAU procedure.
  • Protocol configuration options (PCO) information elements :
  • the campus information elements are shown in Table 1 and Table 2:
  • the related messages include:
  • E-RAB SETUP RESPONSE radio access bearer setup request
  • Correlation ID information element extension (referred to in the 23.859 protocol), the Correlation ID defined in R10 is a 32-byte string, which is used for the TEID of the L-GW user plane or the Generic Routing Encapsulation (GRE) Keys.
  • GRE Generic Routing Encapsulation
  • the Correlation ID also needs to include the necessary information for the internal tunnel establishment of the L-GW and the HeNB: L-GW@LN address/FQDN.
  • the Correlation ID is the information necessary for the MME to notify the HeNB to establish an internal tunnel. Need to be included in the following messages (all optional fields):
  • E-RAB SETUP REQUEST radio access bearer setup request
  • the S1 HO process in the campus (supporting LIPA connection) and the S1 HO process and Sxx port in the campus (supporting LIPA connection) to the outside of the campus (without LIPA connection) can be consistent with the implementation method and the idea of the above example X2 HO.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network 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 and, in some cases, may be different from The steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • the mobility management entity MME is used to obtain the access point name APN information and the campus information of the user terminal; the MME obtains valid subscription information from the home location register HSS, and learns that the user terminal applies for access.
  • the MME receives whether the acquisition of the user terminal attachment supports the LIPA bearer information; the MME according to the APN bearer information that the user terminal has established, the HeNB capability, and the The MME performs the judging process on the attribute of the HSS number; the MME establishes a relationship between the link base station and the local gateway L-GW according to the base station capability of the user terminal, and allows the user to access the local service of the campus, or the MME modifies
  • the related bearer information of the server gateway S-GW and the L-GW establishes a link channel of the SGW and the LGW, and completes switching of the data channel.

Landscapes

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

Abstract

本发明公开了园区业务访问的方法、装置及系统，其中，园区业务访问的方法通过本发明，采用通过本发明，采用移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；该MME根据该用户终端已建立的该APN承载信息、该HeNB能力以及该HSS放号的属性进行判断处理；该MME建立链路通过本地网关L-GW对园区本地业务进行访问，或者，该MME修改服务器网关S-GW和L-GW的相关承载信息，进行数据通道的切换。解决了用户终端在园区之间移动时，IP数据的连续性，移动性不好的问题，提高了IP数据的连续性和移动性，实现了园区内外的无缝切换。

Description

园区业务访问的方法、装置及系统 技术领域
本发明涉及通信领域，具体而言，涉及一种园区业务访问的方法、装置及系统。
背景技术
本地IP接入(Local IP Access,简称为LIPA)连接主要用于独立的住宅或者企业网络(a single residential or Enterprise network)。3GPP的协议提出的LIPA技术可以使用户的本地业务数据直接从园区(家庭/企业)的基站分流出去，一方面避免了IP数据流量迅速增加后对核心网的压力，另一方面还提高了IP数据包的路由效率。这样既减轻核心网络的负担，降低了运营商的核心网吞吐量和传输成本，还减少用户本地数据访问的数据传输时延。LIPA技术是对家庭基站(Home Node B，简称为HeNB)功能的增强，它允许终端通过HeNB直接访问园区内部的IP资源。通常用于运营商基于HeNB组建的园区服务。
3GPP的23.401协议明确提出了，使能LIPA的连接不支持切换(Hand Over，简称为HO)：
在X2接口HO时移动管理实体(Mobile Managenment Entity，简称为MME)收到路径切换请求消息(Path Switch Request message)，如果MME判断有LIPA连接没有被释放，MME会回复路径切换请求失败消息(Path Switch Request Failure message)给目标HeNB；
在S1接口H0时MME收到切换请求信息(Handover Request message)，如果MME判断有LIPA连接没有被释放，MME会回复切换请求失败(Handover Failure(Cause)message)给目标HeNB；
3GPP的23.859协议给出了LIPA的移动性提案，并给出了本地网关(Local Gate Way,简称为LGW)的选择和寻址方法。提案指出，MME选择LGW可通过如下2种方法：
基于域名系统(Domain Name System简称为DNS)：LGW初始上电，向服务网关(ServingGateway，简称为S-GW)获取到IP地址后，向DNS服务器进行注册，注册内容包括：本地网络ID(Local H(e)NB Network identifier简称为LHN ID),本地网络 地址(L-GW@Local network address简称为L-GW@LN)或者本地网络的全称域名(Fully Qualified Domain Name简称为L-GW local FQDN),S-GW分配的L-GW@CN地址。MME在收到用户UE的LIPA的公共数据网(Public Data Network，简称为PDN)连接请求时，向DNS服务器发起DNS请求，DNS服务器返回符合条件的一个或多个LGW IP地址给MME；
基于无线接入网(Radio Access Network，简称为RAN)：每个HeNB自身配置了所有连接LGW的L-GW@LN地址或者FQDN。HeNB通过Sxx口获取到L-GW@CN地址。HeNB通过S1消息给MME上报L-GW@CN地址或者FQDNs。基于接入点名称(Access Point Name，简称为APN)和本地家庭基站网络ID(Local H(e)NB Network ID,简称为LHN ID)，核心网MME在HeNB提供的L-GW表(List)里选择一个L-GW。
3GPP的23.859协议提出给出了UE在园区(家庭/企业)内移动时，如何保证LIPA连接在支持LIPA的eNB/HeNB之间移动时的IP数据会话的连续性。但并未有如何处理在园区外如何访问园区业务，或如何处理LIPA能力不一致的eNB/HeNB(园区内外)的移动性。
针对相关技术中，用户终端在园区之间移动时，IP数据的连续性，移动性不好的问题，还未提出有效的解决方案。
发明内容
本发明提供了一种园区业务访问的方法、装置及系统，以至少上述问题之一。
根据本发明的一个实施例，提供了一种园区业务访问的方法，包括：移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；所述MME向归属位置寄存器HSS获取有效的订阅信息，获知所述用户终端申请接入的所述APN是否支持本地IP接入LIPA；所述MME接收所述用户终端附着的获取是否支持LIPA承载信息；所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理；根据用户终端附着的基站能力，所述MME建立链路基站与本地网关L-GW的之间关系，让用户对园区本地业务进行访问，或者，所述MME修改服务器网关S-GW和L-GW的相关承载信息，建立SGW和LGW的链路通道，完成数据通道的切换。
在本发明的实施例中，移动管理实体MME获取用户终端的接入点名称APN信息和园区信息包括：在所述用户终端的在公共数据网络覆盖的情况下，向所述MME发起本地连接的APN信息及园区信息。
在本发明的实施例中，所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理；所述MME选择合适的链路通过本地网关L-GW对园区本地业务进行访问包括：在所述用户终端请求接入的APN支持LIPA，园区内HeNB不支持LIPA的情况下，或者，所述用户终端请求接入的APN支持LIPA，园区内HeNB也支持LIPA，请求接入的园区和所述用户终端所属的园区不一致的情况下；所述MME根据所述用户终端携带的APN信息和园区信息向域名系统DNS服务器查询所述用户终端申请的园区APN的L-GW@LN,L-GW@CN List/完全合格域名全称FQDNs信息；所述MME创建和L-GW会话，所述MME下发承载安装消息给所述给HeNB，其中，所述HeNB的用户面数据通道通过S-GW与L-GW相通；所述MME将S-GW的S-GW@LN地址和S-GW隧道端点识别TEID作为L-GW的内部通道的参数带给L-GW，用于所述用户终端在园区外通过S-GW与L-GW的数据通道进行园内数据业务访问。
在本发明的实施例中，所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理，所述MME修改服务器网关S-GW和L-GW的相关承载信息，进行数据通道的切换包括：在所述用户终端从不支持LIPA连接园区外向支持LIPA连接园区内的HO切换的情况下，在园区内目标HeNB支持LIPA功能的情况下，所述MME获取本地基站网络LHN ID或者L-GW@CN List/FQDNs、HeNB@LN地址；在所述用户终端当前建立的APN与园区的L-GW有承载的建立，且目标HeNB支持与所述用户终端接入的L-GW建立LIPA连接，所述MME则给用户终端建立HeNB和L-GW的LIPA通道；所述MME修改S-GW的承载信息，修改S-GW@LN地址/S-GW的隧道端点识别TEID为HeNB@LN/HeNB的TEID，并修改L-GW的相关承载信息；所述MME下发关联身份Correlation-ID给目标HeNB，所述Correlation-ID包括L-GW@LN地址/L-GW的内部隧道的TEID，用于目标HeNB的用户面数据通道通过L-GW与目标HeNB相连。
在本发明的实施例中，所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理，所述MME修改服务器网关S-GW和L-GW的相关承载信息，进行园内与园外数据通道的切换包括：所述用户终端从支持LIPA连接园区内向不支持LIPA园区外的切换的情况下，所述用户终端UE建立的APN支持园区的L-GW承载的建立LIPA连接，但园区外的目标HeNB不支持与所述移动终端接入的L-GW建立LIPA连接的情况下；所述MME修改S-GW的承载信息，修改HeNB@LN/HeNB的TEID为S-GW@LN地址/S-GW的TEID，并修改L-GW的相关承载信息；所述MME则通过S-GW建立和L-GW的通道，HeNB的用户面数据通道通过S-GW与L-GW相连。
在本发明的实施例中，所述HO切换包括：X2接口的HO切换；S1接口HO切换流程及Sxx口即支持控制面的信令传输又支持用户面的报文传输HO切换。
在本发明的实施例中，所述园区信息包括以下至少之一：LHN ID，LGW@CN List，HeNB的内部通道的IP地址HeNB@LN IP Addr，HeNB的内部通道的TEID。
根据本发明的另一个实施例，还提供了一种园区业务访问的装置，其中，包括：获取模块，设置为移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；支持模块，设置为所述MME向归属位置寄存器HSS获取有效的订阅信息，获知所述用户终端申请接入的所述APN是否支持本地IP接入LIPA；基站模块，设置为所述MME接收所述用户终端附着的获取是否支持LIPA承载信息；判断模块，设置为所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理；访问模块，设置为根据用户终端附着的基站能力，所述MME建立链路基站与本地网关L-GW的之间关系，让用户对园区本地业务进行访问，或者，所述MME修改服务器网关S-GW和L-GW的相关承载信息，建立SGW和LGW的链路通道，完成进行数据通道的切换。
在本发明的实施例中，所述获取模块还设置为在所述用户终端的在公共数据网络覆盖的情况下，向所述MME发起本地连接的APN信息及园区信息。
在本发明的实施例中，包括：在所述用户终端请求接入的APN支持LIPA，园区内HeNB不支持LIPA的情况下，或者，所述用户终端请求接入的APN支持LIPA，园区内HeNB也支持LIPA，请求接入的园区和所述用户终端所属的园区不一致的情况下；所述判断模块设置为所述MME根据所述用户终端携带的APN信息和园区信息向域名系统DNS服务器查询所述用户终端申请的园区APN的L-GW@LN,L-GW@CN List/完全合格域名全称FQDNs信息；所述访问模块设置为所述MME创建和L-GW会话，所述MME下发承载安装消息给所述给HeNB，其中，所述HeNB的用户面数据通道通过S-GW与L-GW相通；所述访问模块设置为所述MME将S-GW的S-GW@LN地址和S-GW隧道端点识别TEID作为L-GW的内部通道的参数带给L-GW，用于所述用户终端在园内外通过S-GW与L-GW的数据通道进行园内数据业务访问。
在本发明的实施例中，包括：在所述用户终端从不支持LIPA连接园区外向支持LIPA连接园区内的HO切换的情况下，在园区内目标HeNB支持LIPA功能的情况下，所述判断模块设置为所述MME获取本地基站网络LHN ID或者L-GW@CN List/FQDNs、HeNB@LN地址；所述访问模块设置为在所述用户终端当前建立的APN与园区的L-GW有承载的建立，且目标HeNB支持与所述用户终端接入的L-GW建立 LIPA连接，所述MME则给用户终端建立HeNB和L-GW的LIPA通道；所述访问模块设置为所述MME修改S-GW的承载信息，修改S-GW@LN地址/S-GW的隧道端点识别TEID为HeNB@LN/HeNB的TEID，并修改L-GW的相关承载信息；所述访问模块设置为所述MME下发关联身份Correlation-ID给目标HeNB，所述Correlation-ID包括L-GW@LN地址/L-GW的内部隧道的TEID，用于目标HeNB的用户面数据通道通过L-GW与目标HeNB相连。
在本发明的实施例中，包括：所述用户终端从支持LIPA连接园区内向不支持LIPA园区外的切换的情况下，所述用户终端UE建立的APN支持园区的L-GW承载的建立LIPA连接，但园区外的目标HeNB不支持与所述移动终端接入的L-GW建立LIPA连接的情况下；所述访问模块设置为所述MME修改S-GW的承载信息，修改HeNB@LN/HeNB的TEID为S-GW@LN地址/S-GW的TEID，并修改L-GW的相关承载信息；所述访问模块设置为所述MME则通过S-GW建立和L-GW的通道，HeNB的用户面数据通道通过S-GW与L-GW相连。
在本发明的实施例中，所述HO切换包括：X2接口的HO切换；S1接口HO切换流程及Sxx口即支持控制面的信令传输又支持用户面的报文传输HO切换。
在本发明的实施例中，所述园区信息包括以下至少之一：LHN ID，LGW@CN List，HeNB的内部通道的IP地址HeNB@LN IP Addr，HeNB的内部通道的TEID。
根据本发明的还一个实施例，还提供了一种园区业务访问的系统，包括：上述任一项所述的装置。
通过本发明，采用移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；该MME向归属位置寄存器HSS获取有效的订阅信息，获知该用户终端申请接入的该APN是否支持本地IP接入LIPA；该MME接收该用户终端附着的获取是否支持LIPA承载信息；所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理；根据用户终端附着的基站能力，所述MME建立链路基站与本地网关L-GW的之间关系，让用户对园区本地业务进行访问，或者，所述MME修改服务器网关S-GW和L-GW的相关承载信息，建立SGW和LGW的链路通道，完成数据通道的切换。解决了用户终端在园区之间移动时，IP数据的连续性，移动性不好的问题，提高了IP数据的连续性和移动性，实现了园区内外的无缝切换。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的一种园区业务访问的方法的流程图；
图2是根据本发明实施例的一种园区业务访问的装置的结构框图；
图3是根据本发明优选实施例的园区内外访问园区网的比较说明的示意图；
图4是根据本发明优选实施例的UE在园区外进行园区APN的接入请求流程的示意图；
图5是根据本发明优选实施例的园区外向园区内的X2 HO流程的示意图；
图6是根据本发明优选实施例的园区内向园区外的X2 HO流程的示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
在本实施例中提供了一种园区业务访问的方法，图1是根据本发明实施例的一种园区业务访问的方法的流程图，如图1所示，该流程包括如下步骤：
步骤S102，移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；
步骤S104，MME向归属位置寄存器HSS获取有效的订阅信息，获知该用户终端申请接入的该APN是否支持本地IP接入LIPA；
步骤S106，MME接收该用户终端附着的获取是否支持LIPA承载信息；
步骤S108，MME根据该用户终端已建立的该APN承载信息、该HeNB能力以及该HSS放号的属性进行判断处理；
步骤S110，根据用户终端附着的基站能力，该MME建立链路基站与本地网关L-GW的之间关系，让用户对园区本地业务进行访问，或者，该MME修改服务器网 关S-GW和L-GW的相关承载信息，建立SGW和LGW的链路通道，完成数据通道的切换。
通过上述步骤，采用移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；该MME向归属位置寄存器HSS获取有效的订阅信息，获知该用户终端申请接入的该APN是否支持本地IP接入LIPA；该MME接收该用户终端附着的获取是否支持LIPA承载信息；该MME根据该用户终端已建立的该APN承载信息、该HeNB能力以及该HSS放号的属性进行判断处理；根据用户终端附着的基站能力，该MME建立链路基站与本地网关L-GW的之间关系，让用户对园区本地业务进行访问，或者，该MME修改服务器网关S-GW和L-GW的相关承载信息，建立SGW和LGW的链路通道，完成数据通道的切换。解决了用户终端在园区之间移动时，IP数据的连续性，移动性不好的问题，提高了IP数据的连续性和移动性，实现了园区内外的无缝切换。
在本实施例中，移动管理实体MME获取用户终端的接入点名称APN信息和园区信息可以包括：在该用户终端的在公共数据网络覆盖的情况下，向该MME发起本地连接的APN信息及园区信息。
在本实施例中，该MME根据该用户终端已建立的该APN承载信息、该HeNB能力以及该HSS放号的属性进行判断处理；该MME选择合适的链路通过本地网关L-GW对园区本地业务进行访问包括：在该用户终端请求接入的APN支持LIPA，园区内HeNB不支持LIPA的情况下，或者，该用户终端请求接入的APN支持LIPA，园区内HeNB也支持LIPA，请求接入的园区和该用户终端所属的园区不一致的情况下；
该MME根据该用户终端携带的APN信息和园区信息向域名系统DNS服务器查询该用户终端申请的园区APN的L-GW@LN,L-GW@CN List/完全合格域名全称FQDNs信息；
该MME创建和L-GW会话，该MME下发承载安装消息给该给HeNB，其中，该HeNB的用户面数据通道通过S-GW与L-GW相通；
该MME将S-GW的S-GW@LN地址和S-GW隧道端点识别TEID作为L-GW的内部通道的参数带给L-GW，用于该用户终端在园区外通过S-GW与L-GW的数据通道进行园内数据业务访问。
在另一个实施例中，在该用户终端从不支持LIPA连接园区外向支持LIPA连接园区内的HO切换的情况下，在园区内目标HeNB支持LIPA功能的情况下，该MME获取本地基站网络LHN ID或者L-GW@CN List/FQDNs、HeNB@LN地址；
在该用户终端当前建立的APN与园区的L-GW有承载的建立，且目标HeNB支持与该用户终端接入的L-GW建立LIPA连接，该MME则给用户终端建立HeNB和L-GW的LIPA通道；
该MME修改S-GW的承载信息，修改S-GW@LN地址/S-GW的隧道端点识别TEID为HeNB@LN/HeNB的TEID，并修改L-GW的相关承载信息；
该MME下发关联身份Correlation-ID给目标HeNB，该Correlation-ID包括L-GW@LN地址/L-GW的内部隧道的TEID，用于目标HeNB的用户面数据通道通过L-GW与目标HeNB相连。
在另一个实施例中，该用户终端从支持LIPA连接园区内向不支持LIPA园区外的切换的情况下，该用户终端UE建立的APN支持园区的L-GW承载的建立LIPA连接，但园区外的目标HeNB不支持与该移动终端接入的L-GW建立LIPA连接的情况下；
该MME修改S-GW的承载信息，修改HeNB@LN/HeNB的TEID为S-GW@LN地址/S-GW的TEID，并修改L-GW的相关承载信息；
该MME则通过S-GW建立和L-GW的通道，HeNB的用户面数据通道通过S-GW与L-GW相连。
上述实施例中，该HO切换包括：X2接口的HO切换；S1接口HO切换流程及Sxx口即支持控制面的信令传输又支持用户面的报文传输HO切换。
上述实施例中，该园区信息包括以下至少之一：LHN ID，LGW@CN List，HeNB的内部通道的IP地址HeNB@LN IP Addr，HeNB的内部通道的TEID。
在本实施例中还提供了一种园区业务访问的装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图2是根据本发明实施例的一种园区业务访问的装置的结构框图，如图2所示，该装置包括：
获取模块202，设置为移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；
支持模块204，设置为该MME向归属位置寄存器HSS获取有效的订阅信息，获知该用户终端申请接入的该APN是否支持本地IP接入LIPA；
基站模块206，设置为该MME接收该用户终端附着的获取是否支持LIPA承载信息；
判断模块208，设置为该MME根据该用户终端已建立的该APN承载信息、该HeNB能力以及该HSS放号的属性进行判断处理；
访问模块210，设置为根据用户终端附着的基站能力，该MME建立链路基站与本地网关L-GW的之间关系，让用户对园区本地业务进行访问，或者，该MME修改服务器网关S-GW和L-GW的相关承载信息，建立SGW和LGW的链路通道，完成进行数据通道的切换。
通过上述装置，采用移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；该MME向归属位置寄存器HSS获取有效的订阅信息，获知该用户终端申请接入的该APN是否支持本地IP接入LIPA；该MME接收该用户终端附着的获取是否支持LIPA承载信息；该MME根据该用户终端已建立的该APN承载信息、该HeNB能力以及该HSS放号的属性进行判断处理；用于根据用户终端附着的基站能力，该MME建立链路基站与本地网关L-GW的之间关系，让用户对园区本地业务进行访问，或者，该MME修改服务器网关S-GW和L-GW的相关承载信息，建立SGW和LGW的链路通道，完成进行数据通道的切换。解决了用户终端在园区之间移动时，IP数据的连续性，移动性不好的问题，提高了IP数据的连续性和移动性，实现了园区内外的无缝切换。
在本实施例中，该获取模块202还设置为在该用户终端的在公共数据网络覆盖的情况下，向该MME发起本地连接的APN信息及园区信息。
在本实施例中，在该用户终端请求接入的APN支持LIPA，园区内HeNB不支持LIPA的情况下，或者，该用户终端请求接入的APN支持LIPA，园区内HeNB也支持LIPA，请求接入的园区和该用户终端所属的园区不一致的情况下；
该判断模块208设置为该MME根据该用户终端携带的APN信息和园区信息向域名系统DNS服务器查询该用户终端申请的园区APN的L-GW@LN,L-GW@CN List/完全合格域名全称FQDNs信息；
该访问模块210设置为该MME创建和L-GW会话，该MME下发承载安装消息给该给HeNB，其中，该HeNB的用户面数据通道通过S-GW与L-GW相通；
该访问模块210设置为该MME将S-GW的S-GW@LN地址和S-GW隧道端点识别TEID作为L-GW的内部通道的参数带给L-GW，用于该用户终端在园内外通过S-GW与L-GW的数据通道进行园内数据业务访问。
在本实施例中，在该用户终端从不支持LIPA连接园区外向支持LIPA连接园区内的HO切换的情况下，在园区内目标HeNB支持LIPA功能的情况下，该判断模块208设置为该MME获取本地基站网络LHN ID或者L-GW@CN List/FQDNs、HeNB@LN地址；
该访问模块210设置为在该用户终端当前建立的APN与园区的L-GW有承载的建立，且目标HeNB支持与该用户终端接入的L-GW建立LIPA连接，该MME则给用户终端建立HeNB和L-GW的LIPA通道；
该访问模块210设置为该MME修改S-GW的承载信息，修改S-GW@LN地址/S-GW的隧道端点识别TEID为HeNB@LN/HeNB的TEID，并修改L-GW的相关承载信息；
该访问模块210设置为该MME下发关联身份Correlation-ID给目标HeNB，该Correlation-ID包括L-GW@LN地址/L-GW的内部隧道的TEID，用于目标HeNB的用户面数据通道通过L-GW与目标HeNB相连。
在本实施例中，该用户终端从支持LIPA连接园区内向不支持LIPA园区外的切换的情况下，该用户终端UE建立的APN支持园区的L-GW承载的建立LIPA连接，但园区外的目标HeNB不支持与该移动终端接入的L-GW建立LIPA连接的情况下；
该访问模块210设置为该MME修改S-GW的承载信息，修改HeNB@LN/HeNB的TEID为S-GW@LN地址/S-GW的TEID，并修改L-GW的相关承载信息；
该访问模块210设置为该MME则通过S-GW建立和L-GW的通道，HeNB的用户面数据通道通过S-GW与L-GW相连。
上述实施例中，该HO切换包括：X2接口的HO切换；S1接口HO切换流程及Sxx口即支持控制面的信令传输又支持用户面的报文传输HO切换。
上述实施例中，该园区信息包括以下至少之一：LHN ID，LGW@CN List，HeNB的内部通道的IP地址HeNB@LN IP Addr，HeNB的内部通道的TEID。
在本实施例中，还提供了一种园区业务访问的系统，包括:上述任一项该的装置。上述装置可以实现上述方法。
下面结合优选实施例和实施场景进行详细说明。
本优选实施例的目的在于针对上述问题，提供一种园区外访问园区业务的方法，并提供支持用户(UE)在园区内网之间移动时，IP数据的连续性的方法。其原理是MME根据UE上报的APN/LHN ID信息来选择UE接入的LGW，并根据HeNB上报的L-GW@CN地址或LHN ID(Local H(e)NB Network ID)信息来选择是否支持LIPA功能。当UE在园区外接入时，MME选择使用非LIPA通道进行本地LGW的访问。当UE在园区内接入时，MME选择使用LIPA通道进行本地LGW的访问。当UE在LIPA能力不一致的eNB/HeNB(园区内外)进行移动时，MME进行数据通道的切换工作。
该方法包括以下步骤：
第一步骤：LGW上电后，完成DNS服务器注册工作。
第二步骤：UE发起园区APN的接入请求，如果初始接入时，UE需要连接园区，则在连接(Attach)请求消息里设置了加密选项传递帧(Ciphered Options Transfer Flag)，MME就向UE获取Ciphered Options，UE将Ciphered Options通过Ciphered Options Response(APN及园区信息(如：LHN ID)等相关信息)带给MME。如果为UE请求的PDN连接时，UE通过PDN CONNECTIVITY REQUEST消息携带APN,及相关园区信息(如：LHN ID)等信息。
第三步骤：UE附着的HeNB根据自身的配置能力判断，给MME携带LHN ID或者L-GW@CN List/FQDNs、HeNB@LN地址。
第四步骤：MME根据HSS放号信息，HeNB的能力和UE发起的请求进行判决，判断是否能访问园区，如何访问园区。
第五步骤：当UE从园区内移动到园区外，或者从园区外移动至园区内时，MME根据基站的能力，及UE目前建立的连接，进行数据通道的切换。
本优选实施例提供了一种园区外访问园区业务的方法，并提供支持UE在园区内网之间移动时，IP数据的连续性的方法，MME可以根据UE接入的具体场景，选择合适的链路通过LGW对本地业务进行访问，并能解决LIPA能力不一致的eNB/HeNB(园区内外)的移动性，实现了园区内外的无缝切换。
图3是根据本发明优选实施例的园区内外访问园区网的比较说明的示意图，如图3所示。
UE在园区内，数据报文通过本地分流技术，从HeNB直接分流到LGW上。本地数据不需要经过SGW，认证由核心网放号权限和公司认证服务器统一保证；
UE在园区外，本发明的实施例中，数据报文经过SGW，发送到LGW。认证方式和UE在园区内认证方式统一，都由核心网放号权限和公司认证服务器统一保证；而普通的VPN方案：数据经过SGW/PGW，绕道公司的外网VPN网关。需要UE安装VPN客户端，认证权限由外网VPN保证；
图4是根据本发明优选实施例的UE在园区外进行园区APN的接入请求流程的示意图，如图4所示。
UE在园区外进行园区APN的接入请求流程具体过程如下：
步骤1-3,园区内的L-GW完成上电的注册流程；
步骤4，UE在园区外进行园区APN的接入请求，UE通过非接入层(Non-access stratum，简称为NAS)消息PDN Connectivity Request(其中，携带APN及园区信息(如：LHN ID)等相关信息)发起请求的PDN连接过程。该消息通过HeNB的S1消息Uplink NAS Transports发送到MME时，因为UE在园区外接入，园区外HeNB不支持LIPA，所以在Uplink NAS Transports并未携带LHN ID或者L-GW@CN List/FQDNs、HeNB@LN地址等园区LIPA承载相关的信息。
步骤5，MME向HSS获取有效的订阅信息，获知UE申请接入的APN是否支持LIPA；
步骤6，MME综合UE请求、HeNB能力以及HSS放号的属性进行判断。如果，UE请求接入的APN支持LIPA，但园内HeNB不支持LIPA(或UE请求接入的APN支持LIPA，园内HeNB也支持LIPA，但和UE所属的园区不一致)，MME根据UE携带的APN信息和园区信息(如：LHN ID)向DNS服务器查询UE申请的园区APN的 L-GW@LN,L-GW@CN List/FQDNs(Fully Qualified Domain Nam，完全合格域名/全称域名)信息；
步骤7，MME和L-GW完成创建会话过程；
步骤8，MME下发Bearer Setup Request(承载安装要求)消息给HeNB,不携带Correlation-ID。HeNB的用户面数据通道通过S-GW与L-GW相通。
步骤9，其他流程；
步骤10，MME通过Change Notification(Change Notification Request/Response消息或者Modify Bearer Request/Response消息)过程将S-GW的S-GW@LN地址/S-GW TEID作为L-GW的“内部通道”的参数带给L-GW。
图5是根据本发明优选实施例的园区外向园区内的X2 HO流程的示意图，如图5所示。
园区外(不支持LIPA连接)向园区内(支持LIPA连接)的X2 HO流程(以Sxx口只支持用户面的报文传输为例)具体过程如下：
步骤1-2,园区外(不支持LIPA连接)向园区内(支持LIPA连接)进行X2 HO，源HeNB-G同正常X2 HO流程，将所有的无线资源控制(Radio Resource Control，简称为RRC)/进化型的统一陆地无线接入网络(Evolved Universal Terrestrial Radio Access Network，简称为E-UTRAN)等信息通过X2的HO Request发给目标HeNB-YQ。目标HeNB-YQ完成接纳控制，回复ACK(Acknowledgement)给源HeNB-G，源测发送SN(Serial Number)STATUS TRANSFER(序列号状态转发)消息，并开始用户面的数据反传。此时，L-GW的数据通道依然是L-GW通过S-GW发送给HeNB-G。
步骤3，园区内HeNB-YQ支持LIPA功能，将LHN ID或者L-GW@CN List/FQDNs、HeNB@LN地址通过S1消息Path Swtich Request(路径转换请求)带给MME。MME综合UE已建立的APN承载信息、HeNB能力以及HSS放号的属性进行判断。如果，UE当前建立的APN已经于支持园区的L-GW有承载的建立，且目标HeNB支持与UE接入的L-GW建立LIPA连接，MME则给UE建立HeNB和L-GW的LIPA通道；
步骤4-5，MME首先修改S-GW的承载信息，并修改L-GW的相关承载信息(修改S-GW@LN地址/S-GW的隧道端点识别(Tunnel Endpoint Identifier，简称为TEID)为HeNB@LN/HeNB的TEID)；
步骤6，S-GW切换数据通道后，将用户面数据发送完毕后，发送结束符EndMark给HeNB。
步骤7，MME下发Path Swtich Request ACK消息给HeNB,携带Correlation-ID(包括L-GW@LN地址/L-GW的内部隧道的TEID)。HeNB的用户面数据通道通过L-GW与HeNB相连。源HeNB-G收到S-GW发送的Endmark后，转发给目标HeNB-YQ。
步骤8-9，目标HeNB对源HeNB发起释放，并进行跟踪区更新(Tracking Area Update，简称为TAU)过程。
图6是根据本发明优选实施例的园区内向园区外的X2 HO流程的示意图，如图6所示。
园区内(支持LIPA连接)向园区外(不支持LIPA连接)的X2 HO流程(以Sxx口只支持用户面的报文传输为例)具体过程如下：
步骤1-2,园区内(支持LIPA连接)向园区外(不支持LIPA连接)的X2 HO，源HeNB-YQ同正常X2 HO流程，将所有的RRC/E-RAB等信息通过X2的HO Request发给目标HeNB-G。目标HeNB-G完成接纳控制，回复ACK给源HeNB-YQ，源测发送SN STATUS TRANSFER消息，并开始用户面的数据反传。此时，L-GW的数据通道依然是通过LIPA连接发送给HeNB-YQ。
步骤3，园区内HeNB-YQ不支持LIPA功能，Path Swtich Request消息中不携带LHN ID或者L-GW@CN List/FQDNs、HeNB@LN地址等LIPA相关信息给MME。MME综合UE已建立的APN承载信息、HeNB能力以及HSS放号的属性进行判断。如果，UE当前建立的APN已经于支持园区的L-GW有承载的建立(LIPA连接)，但目标HeNB不支持与UE接入的L-GW建立LIPA连接，MME则通过S-GW建立和L-GW的通道；
步骤4-5，MME首先修改S-GW(服务网关)的承载信息，并修改L-GW的相关承载信息(修改HeNB@LN/HeNB的TEID为S-GW@LN地址/S-GW的TEID)；
步骤6，L-GW切换数据通道后，发送EndMark给源HeNB-YQ。
步骤7，MME下发Path Swtich Request ACK消息给HeNB,不携带LIPA的相关信息。HeNB的用户面数据通道通过S-GW与L-GW相连。
步骤8-9，目标HeNB对源HeNB发起释放，并进行TAU过程。
本实施例的附录：
协议增加字段示例：
协议配置选项(Protocol configuration options，简称为PCO)信息元素：
Figure PCTCN2015085355-appb-000001
园区信息元素如表1和表2所示：
表1
Figure PCTCN2015085355-appb-000002
表2
Figure PCTCN2015085355-appb-000003
HeNB发往MME的相关消息，都需要增加LHN Info字段(均为可选字段)，相关消息包括：
INITIAL UE MESSAGE(初始UE消息)；
UPLINK NAS TRANSPORT(上行网络附加存储(Network Attached Storage)传输)；
E-RAB SETUP RESPONSE(无线接入承载设置请求)；
INITIAL CONTEXT SETUP RESPONSE(初始上下文建立请求)；
PATH SWITCH REQUEST(路径转换请求应答)；
HANDOVER REQUEST ACKNOWLEDGE(切换请求应答)；
Correlation ID信息元素扩展(23.859协议有涉及)，R10中定义的Correlation ID为32字节的字符串，用于L-GW用户面的TEID或者通用路由封装(Generic Routing Encapsulation，简称为GRE)Keys。为了支持独立部署的L-GW的结构，Correlation ID还需要包括L-GW和HeNB的内部隧道建立的必要信息：L-GW@LN address/FQDN。
Correlation ID(相关性标识ID)是MME通知HeNB建立内部隧道的必要信息。需要在以下消息中包括(均为可选字段)：
INITIAL CONTEXT SETUP REQUEST(初始上下文建立请求)；
E-RAB SETUP REQUEST(无线接入承载设置请求)；
PATH SWITCH REQUEST ACKNOWLEDGE(路径转换请求应答)；
HANDOVER REQUEST(切换请求)。
上述实施例中的园区外(不支持LIPA连接)向园区内(支持LIPA连接)的S1 HO流程和园区内(支持LIPA连接)向园区外(不持LIPA连接)的S1 HO流程及Sxx口即支持控制面的信令传输又支持用户面的报文传输HO场景的应用实施例可以同上述例子X2 HO的实现方法和思路一致。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处 的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上该仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
基于本发明实施例提供的上述技术方案，采用移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；该MME向归属位置寄存器HSS获取有效的订阅信息，获知该用户终端申请接入的该APN是否支持本地IP接入LIPA；该MME接收该用户终端附着的获取是否支持LIPA承载信息；所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理；根据用户终端附着的基站能力，所述MME建立链路基站与本地网关L-GW的之间关系，让用户对园区本地业务进行访问，或者，所述MME修改服务器网关S-GW和L-GW的相关承载信息，建立SGW和LGW的链路通道，完成数据通道的切换。解决了用户终端在园区之间移动时，IP数据的连续性，移动性不好的问题，提高了IP数据的连续性和移动性，实现了园区内外的无缝切换。

Claims (15)

  1. 一种园区业务访问的方法，包括：
    移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；
    所述MME向归属位置寄存器HSS获取有效的订阅信息，获知所述用户终端申请接入的所述APN是否支持本地IP接入LIPA；
    所述MME接收所述用户终端附着的基站获取是否支持LIPA承载信息；
    所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理；
    根据用户终端附着的基站能力，所述MME建立链路基站与本地网关L-GW的之间关系，让用户对园区本地业务进行访问，或者，所述MME修改服务器网关S-GW和L-GW的相关承载信息，建立SGW和LGW的链路通道，完成数据通道的切换。
  2. 根据权利要求1所述的方法，其中，移动管理实体MME获取用户终端的接入点名称APN信息和园区信息包括：
    在所述用户终端的在公共数据网络覆盖的情况下，向所述MME发起本地连接的APN信息及园区信息。
  3. 根据权利要求1所述的方法，其中，所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理；所述MME选择合适的链路通过本地网关L-GW对园区本地业务进行访问包括：
    在所述用户终端请求接入的APN支持LIPA，园区内HeNB不支持LIPA的情况下，或者，所述用户终端请求接入的APN支持LIPA，园区内HeNB也支持LIPA，请求接入的园区和所述用户终端所属的园区不一致的情况下；
    所述MME根据所述用户终端携带的APN信息和园区信息向域名系统DNS服务器查询所述用户终端申请的园区APN的L-GW@LN,L-GW@CN List/完全合格域名全称FQDNs信息；
    所述MME创建和L-GW会话，所述MME下发承载安装消息给所述给HeNB，其中，所述HeNB的用户面数据通道通过S-GW与L-GW相通；
    所述MME将S-GW的S-GW@LN地址和S-GW隧道端点识别TEID作为L-GW的内部通道的参数带给L-GW，用于所述用户终端在园区外通过S-GW与L-GW的数据通道进行园内数据业务访问。
  4. 根据权利要求1所述的方法，其中，所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理，所述MME修改服务器网关S-GW和L-GW的相关承载信息，进行数据通道的切换包括：
    在所述用户终端从不支持LIPA连接园区外向支持LIPA连接园区内的HO切换的情况下，在园区内目标HeNB支持LIPA功能的情况下，所述MME获取本地基站网络LHN ID或者L-GW@CN List/FQDNs、HeNB@LN地址；
    在所述用户终端当前建立的APN与园区的L-GW有承载的建立，且目标HeNB支持与所述用户终端接入的L-GW建立LIPA连接，所述MME则给用户终端建立HeNB和L-GW的LIPA通道；
    所述MME修改S-GW的承载信息，修改S-GW@LN地址/S-GW的隧道端点识别TEID为HeNB@LN/HeNB的TEID，并修改L-GW的相关承载信息；
    所述MME下发关联身份Correlation-ID给目标HeNB，所述Correlation-ID包括L-GW@LN地址/L-GW的内部隧道的TEID，用于目标HeNB的用户面数据通道通过L-GW与目标HeNB相连。
  5. 根据权利要求1所述的方法，其中，所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理，所述MME修改服务器网关S-GW和L-GW的相关承载信息，进行园内与园外数据通道的切换包括：
    所述用户终端从支持LIPA连接园区内向不支持LIPA园区外的切换的情况下，所述用户终端UE建立的APN支持园区的L-GW承载的建立LIPA连接，但园区外的目标HeNB不支持与所述移动终端接入的L-GW建立LIPA连接的情况下；
    所述MME修改S-GW的承载信息，修改HeNB@LN/HeNB的TEID为S-GW@LN地址/S-GW的TEID，并修改L-GW的相关承载信息；
    所述MME则通过S-GW建立和L-GW的通道，HeNB的用户面数据通道通过S-GW与L-GW相连。
  6. 根据权利要求4或5所述的方法，其中，所述HO切换包括：
    X2接口的HO切换；
    S1接口HO切换流程及Sxx口即支持控制面的信令传输又支持用户面的报文传输HO切换。
  7. 根据权利要求1至6任一项所述的方法，其中，所述园区信息包括以下至少之一：
    LHN ID，LGW@CN List，HeNB的内部通道的IP地址HeNB@LN IP Addr，HeNB的内部通道的TEID。
  8. 一种园区业务访问的装置，包括：
    获取模块，设置为移动管理实体MME获取用户终端的接入点名称APN信息和园区信息；
    支持模块，设置为所述MME向归属位置寄存器HSS获取有效的订阅信息，获知所述用户终端申请接入的所述APN是否支持本地IP接入LIPA；
    基站模块，设置为所述MME接收所述用户终端附着的基站获取是否支持LIPA承载信息；
    判断模块，设置为所述MME根据所述用户终端已建立的所述APN承载信息、所述HeNB能力以及所述HSS放号的属性进行判断处理；
    访问模块，设置为根据用户终端附着的基站能力，所述MME建立链路基站与本地网关L-GW的之间关系，让用户对园区本地业务进行访问，或者，所述MME修改服务器网关S-GW和L-GW的相关承载信息，建立SGW和LGW的链路通道，完成进行数据通道的切换。
  9. 根据权利要求8所述的装置，其中，所述获取模块还设置为在所述用户终端的在公共数据网络覆盖的情况下，向所述MME发起本地连接的APN信息及园区信息。
  10. 根据权利要求8所述的装置，其中，包括：
    在所述用户终端请求接入的APN支持LIPA，园区内HeNB不支持LIPA的情况下，或者，所述用户终端请求接入的APN支持LIPA，园区内HeNB也支持LIPA，请求接入的园区和所述用户终端所属的园区不一致的情况下；
    所述判断模块设置为所述MME根据所述用户终端携带的APN信息和园区信息向域名系统DNS服务器查询所述用户终端申请的园区APN的L-GW@LN,L-GW@CN List/完全合格域名全称FQDNs信息；
    所述访问模块设置为所述MME创建和L-GW会话，所述MME下发承载安装消息给所述给HeNB，其中，所述HeNB的用户面数据通道通过S-GW与L-GW相通；
    所述访问模块设置为所述MME将S-GW的S-GW@LN地址和S-GW隧道端点识别TEID作为L-GW的内部通道的参数带给L-GW，用于所述用户终端在园内外通过S-GW与L-GW的数据通道进行园内数据业务访问。
  11. 根据权利要求8所述的装置，其中，包括：
    在所述用户终端从不支持LIPA连接园区外向支持LIPA连接园区内的HO切换的情况下，在园区内目标HeNB支持LIPA功能的情况下，所述判断模块设置为所述MME获取本地基站网络LHN ID或者L-GW@CN List/FQDNs、HeNB@LN地址；
    所述访问模块设置为在所述用户终端当前建立的APN与园区的L-GW有承载的建立，且目标HeNB支持与所述用户终端接入的L-GW建立LIPA连接，所述MME则给用户终端建立HeNB和L-GW的LIPA通道；
    所述访问模块设置为所述MME修改S-GW的承载信息，修改S-GW@LN地址/S-GW的隧道端点识别TEID为HeNB@LN/HeNB的TEID，并修改L-GW的相关承载信息；
    所述访问模块设置为所述MME下发关联身份Correlation-ID给目标HeNB，所述Correlation-ID包括L-GW@LN地址/L-GW的内部隧道的TEID，用于目标HeNB的用户面数据通道通过L-GW与目标HeNB相连。
  12. 根据权利要求8所述的装置，其中，包括：
    所述用户终端从支持LIPA连接园区内向不支持LIPA园区外的切换的情况下，所述用户终端UE建立的APN支持园区的L-GW承载的建立LIPA连接，但园区外的目标HeNB不支持与所述移动终端接入的L-GW建立LIPA连接的情况下；
    所述访问模块设置为所述MME修改S-GW的承载信息，修改HeNB@LN/HeNB的TEID为S-GW@LN地址/S-GW的TEID，并修改L-GW的相关承载信息；
    所述访问模块设置为所述MME则通过S-GW建立和L-GW的通道，HeNB的用户面数据通道通过S-GW与L-GW相连。
  13. 根据权利要求11或12所述的装置，其中，所述HO切换包括：
    X2接口的HO切换；
    S1接口HO切换流程及Sxx口即支持控制面的信令传输又支持用户面的报文传输HO切换。
  14. 根据权利要求8至13任一项所述的装置，其中，所述园区信息包括以下至少之一：
    LHN ID，LGW@CN List，HeNB的内部通道的IP地址HeNB@LN IP Addr，HeNB的内部通道的TEID。
  15. 一种园区业务访问的系统，包括：
    权利要求8至权利要求14任一项所述的装置。
PCT/CN2015/085355 2014-12-26 2015-07-28 园区业务访问的方法、装置及系统 WO2016101616A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410829594.7 2014-12-26
CN201410829594.7A CN105792199A (zh) 2014-12-26 2014-12-26 园区业务访问的方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2016101616A1 true WO2016101616A1 (zh) 2016-06-30

Family

ID=56149160

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/085355 WO2016101616A1 (zh) 2014-12-26 2015-07-28 园区业务访问的方法、装置及系统

Country Status (2)

Country Link
CN (1) CN105792199A (zh)
WO (1) WO2016101616A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111781905A (zh) * 2020-07-24 2020-10-16 广州市悦冠智能科技有限公司 一种eba物业管理系统
CN112702744A (zh) * 2019-10-22 2021-04-23 上海华为技术有限公司 基于蜂窝网络的专有小区建立方法、业务运行方法及装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106230715A (zh) * 2016-09-20 2016-12-14 中节能六合天融环保科技有限公司 一种应用于节能减排监控的网关

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102868994A (zh) * 2011-07-08 2013-01-09 北京三星通信技术研究有限公司 一种支持用户设备ue移动性的方法
CN103428670A (zh) * 2012-05-23 2013-12-04 中兴通讯股份有限公司 一种访问控制方法及移动管理实体
CN103517362A (zh) * 2012-06-29 2014-01-15 北京三星通信技术研究有限公司 一种接入控制判断方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107750050B (zh) * 2011-01-06 2022-03-04 北京三星通信技术研究有限公司 一种支持用户设备ue移动性的方法和设备
US9924413B2 (en) * 2011-07-01 2018-03-20 Interdigital Patent Holdings, Inc. Method and apparatus for supporting local IP access and selected IP traffic offload
CN102868999A (zh) * 2011-07-04 2013-01-09 中兴通讯股份有限公司 分组数据网络连接的建立方法及系统
CN103813397B (zh) * 2012-11-12 2019-02-15 中兴通讯股份有限公司 管理分流连接的方法、无线侧网元及移动性管理实体
CN103841657B (zh) * 2012-11-21 2018-08-14 中兴通讯股份有限公司 一种本地ip访问连接的释放方法和mrn
CN104080133B (zh) * 2013-03-29 2019-07-02 中兴通讯股份有限公司 一种移动性优化方法、用户设备和接入网设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102868994A (zh) * 2011-07-08 2013-01-09 北京三星通信技术研究有限公司 一种支持用户设备ue移动性的方法
CN103428670A (zh) * 2012-05-23 2013-12-04 中兴通讯股份有限公司 一种访问控制方法及移动管理实体
CN103517362A (zh) * 2012-06-29 2014-01-15 北京三星通信技术研究有限公司 一种接入控制判断方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112702744A (zh) * 2019-10-22 2021-04-23 上海华为技术有限公司 基于蜂窝网络的专有小区建立方法、业务运行方法及装置
CN111781905A (zh) * 2020-07-24 2020-10-16 广州市悦冠智能科技有限公司 一种eba物业管理系统

Also Published As

Publication number Publication date
CN105792199A (zh) 2016-07-20

Similar Documents

Publication Publication Date Title
JP6536850B2 (ja) 通信システム
US8804682B2 (en) Apparatus for management of local IP access in a segmented mobile communication system
EP3691356B1 (en) Switching 3gpp access from eps to 5gs
KR101002810B1 (ko) 패킷 스위칭 도메인에서 단말의 위치 등록 방법 및 장치
US9769852B2 (en) Maintaining current cell location information in a cellular access network
KR101877734B1 (ko) 무선 통신 시스템에서 단말의 이동성을 지원하기 위한 방법 및 장치
US8724509B2 (en) Mobile communication method, mobile communication system, and corresponding apparatus
US9432960B2 (en) Method of handling proximity service in wireless communication system
US11228560B2 (en) Mobility functionality for a cloud-based access system
BR112020002580A2 (pt) dipositivo sem fio e entidade ou função de rede núcleo para prover controle de gap de serviço e métodos de operação relacionados
CN108702810A (zh) 无线通信系统中执行用于基于网络切片的nr的小区特定过程或者移动性过程的方法和装置
US20170244705A1 (en) Method of using converged core network service, universal control entity, and converged core network system
WO2011026392A1 (zh) 一种路由策略的获取方法及系统
CN106470465B (zh) Wifi语音业务发起方法、lte通信设备、终端及通信系统
CN106332222A (zh) 一种网络选择的方法和基站
WO2012130133A1 (zh) 一种接入点及终端接入方法
WO2010133107A1 (zh) 家用基站网关转发消息至家用基站的方法及系统
JP2024123131A (ja) インジケーション情報送信方法、装置およびシステム、および記憶媒体
WO2013004121A1 (zh) 本地网关信息处理方法及装置
US20130058312A1 (en) Method, apparatus and system for processing local address in shunt connection
WO2016101616A1 (zh) 园区业务访问的方法、装置及系统
CN102448185B (zh) 远程接入方法及设备
WO2010102571A1 (zh) S101隧道重定向的方法和装置
WO2011157117A2 (zh) 接入控制方法和装置
WO2012034474A1 (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: 15871690

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

Country of ref document: EP

Kind code of ref document: A1