WO2012126319A1 - 一种本地访问业务的切换方法及系统 - Google Patents

一种本地访问业务的切换方法及系统 Download PDF

Info

Publication number
WO2012126319A1
WO2012126319A1 PCT/CN2012/072067 CN2012072067W WO2012126319A1 WO 2012126319 A1 WO2012126319 A1 WO 2012126319A1 CN 2012072067 W CN2012072067 W CN 2012072067W WO 2012126319 A1 WO2012126319 A1 WO 2012126319A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
handover
local
management unit
user
Prior art date
Application number
PCT/CN2012/072067
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 WO2012126319A1 publication Critical patent/WO2012126319A1/zh

Links

Classifications

    • 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

  • the present invention relates to the field of mobile communications, and in particular, to a method and system for switching local access services.
  • FIG. 1 shows a schematic structural diagram of an evolved packet domain system.
  • the entire EPS system is divided into two parts: a radio access network and a core network.
  • the home subscriber server (HSS) the mobility management entity (MME, Mobility Management Entity), the serving GPRS support node (SGSN), and the policy charging rule function (PCRF) are included.
  • Policy and Charging Rule Function a Policy and Charging Rule Function
  • S-GW Service Gateway
  • Serving Gateway Packet Data Gateway
  • PDN Gateway Packet Data Network
  • PDN Gateway Packet Data Network
  • the Home Subscriber Server which contains all the functions of the Home Location Register (HLR), is the permanent storage location for the subscriber's subscription data and is located in the home network to which the subscriber is contracted.
  • HLR Home Location Register
  • the Mobility Management Entity is the storage location of the user subscription data in the current network, responsible for terminal-to-network non-access stratum signaling management, terminal security verification function, terminal mobility management, and user idle mode tracking. And paging management functions and bearer management.
  • the Serving GPRS Support Node is a service support point for the GSM Radio Access Network (GERAN, GSM EDGE Radio Access Network) and the UMTS Terrestrial Radio Access Network (UTRAN) to access the core network. Similar to the mobility management entity, it is responsible for user location update, paging management, and bearer management.
  • GERAN GSM Radio Access Network
  • UTRAN UMTS Terrestrial Radio Access Network
  • the service gateway is the gateway from the core network to the wireless system, and is responsible for the user of the terminal to the core network.
  • the data cache in the idle mode of the terminal the function of initiating the service request on the network side, the lawful interception and the packet data routing and forwarding function; the service gateway is responsible for counting the situation in which the user terminal uses the wireless network, and generates the CDRs of the terminal using the wireless network, and transmits Give the billing gateway.
  • the packet data gateway is a gateway of the evolved system and the external packet data network of the system. It is connected to the Internet and the packet data network, and is responsible for the Internet Protocol (IP) address allocation, charging function, packet filtering, and policy of the terminal. Control and other functions.
  • IP Internet Protocol
  • the GPRS (General Packet Radio Service) Gateway Support Node supports the edge routing function of the GPRS network. That is, the GGSN is responsible for routing and forwarding data of the GPRS network, and through the firewall and filtering functions. To protect the integrity of GPRS network data.
  • the GGSN also has a charging function.
  • the P-GW contains all the functions of the GGSN, and the GGSN can be considered as a sub-function of the P-GW and embedded in the P-GW. Therefore, the SGSN can be directly connected to the P-GW, using the Gn/Gp interface.
  • the packet data network is the operator's IP service network, which provides IP services to users through the carrier's core network.
  • the policy charging rule function entity is a server in the evolution system responsible for providing rules for charging control, online credit control, threshold control, and quality of service (QoS) policies.
  • the radio access network is composed of an evolved base station (eNB, E-UTRAN NodeB) and a 3G radio network controller (RNC), which is mainly responsible for transmitting and receiving wireless signals, and communicating with the terminal through the air interface to manage the air interface. Radio resources, resource scheduling, access control.
  • eNB evolved base station
  • RNC 3G radio network controller
  • a home base station (HNB, Home NodeB) or an evolved home base station (HeNB, Home eNodeN) is a type of small, low-power base station that is used as a dedicated resource for certain users and deployed in private places such as homes, groups, companies, or schools.
  • the main purpose is to provide users with higher service rates and reduce the cost of using high-rate services, while at the same time making up for the shortage of existing distributed cellular wireless communication systems.
  • the advantages of home base stations are affordability, convenience, low power output, plug and play, broadband access, use of single mode terminals, and more.
  • the home base station can be applied in a third generation mobile communication technology (3G, 3rd Generation) or a Long Term Evolution (LTE) mobile communication network.
  • 3G, 3rd Generation 3rd Generation
  • LTE Long Term Evolution
  • the station manages and introduces a new network element, that is, the home base station gateway, in the network.
  • the main functions performed by the home base station gateway are: verifying the security of the home base station, performing maintenance and management on the operation of the home base station, configuring and controlling the home base station according to the operator's requirements, and exchanging data information of the core network and the home base station.
  • the home base station has different access modes, namely closed mode, mixed mode and open mode.
  • closed mode closed subscriber group
  • mixed mode open mode
  • open mode the user needs to verify the user's closed subscriber group (CSG, closed subscribed group) subscription information from the base station.
  • CSG closed subscriber group
  • the home base station can also support local IP access functions. Under the condition that the home base station has local IP access capability and the user subscribes to allow local IP access, the user can implement the user to the home network. Local access to IP devices or the Internet. Through the local access function, the Internet data service can be diverted, the core network load can be reduced, and the access to the home network device can be forwarded without the core network, and the data transmission is convenient and efficient.
  • the local IP access function can also be used on the macro cell. The main purpose is similar to that of the home base station, and more is applied to the local IP access to the Internet. The purpose is to reduce the core network load.
  • FIG. 2 shows the architecture for implementing the above-mentioned local access function.
  • the local gateway serves as a local access network to an external network (such as the Internet), and provides address allocation, accounting, packet filtering, policy control, and data offloading functions.
  • the radio access network application part (NAS/RANAP, Radios Access Network Application Part) performs message parsing, network address translation (NAT), local IP access policy routing, and execution.
  • the local gateway can also access the internal network to achieve mutual access within the jurisdiction of the local gateway, different terminals directly, and the internal network.
  • the NE can be deployed in conjunction with an existing home base station during actual deployment.
  • the local gateway can also be deployed in conjunction with the base station. It can also be deployed as a separate network element.
  • the local gateway implements the internal network access function
  • the terminal accessing the internal network needs to be authenticated.
  • the mobility management unit including the MME and the SGSN
  • the mobility management unit needs to authenticate the user. .
  • Local service access is only possible if a particular CSG accesses a particular APN.
  • the local gateway is combined with the home base station and does not support mobility. This will cause the UE to disconnect from the home base station that establishes the local connection, and the local service is interrupted, resulting in the user experience. Relatively poor. Therefore, the industry began to study how to ensure that the UE can still guarantee the continuity of local services after the mobile, and the UE performs local services from other base stations as shown in FIG.
  • the technical problem to be solved by the present invention is to provide a method and system for switching local access services to solve the problem of continuity of local services during user handover.
  • the present invention uses the following technical solutions:
  • a method for switching a local access service includes: after a user establishes a local service through a source home base station, when a handover occurs, performing the following steps:
  • the source home base station selects the target base station to be handed over, and sends a handover request to the mobility management unit of the core network;
  • the mobility management unit After receiving the handover request, the mobility management unit returns a handover preparation failure message to the source home base station if it is determined that the local base station is not allowed to establish a local service, and indicates a failure reason in the handover preparation failure message.
  • the switching method further includes:
  • the mobility management unit After receiving the handover request, the mobility management unit, if it is determined that the local service is allowed to be established at the target base station, sends a handover command to the source home base station to perform the handover process of the user.
  • the switching method further includes:
  • the mobile management unit determines whether the local service is the only connection of the user, and if it is the unique connection of the user, Returning the handover preparation failure message to the source home base station, and including a failure cause value 1 in the handover preparation failure message;
  • the failure cause value one indicates that the target side does not support the local service.
  • the switching method further includes:
  • the mobile management unit determines whether the local service is established as the unique connection of the user before returning the handover preparation failure message, if not the unique connection of the user, Returning the handover preparation failure message to the source home base station, and including a failure cause value 2 in the handover preparation failure message;
  • the failure cause value two indicates that the target side does not support the local service, and also indicates that the local connection is not the user unique connection.
  • the switching method further includes:
  • the mobile management unit determines whether the local service is established as the unique connection of the user before returning the handover preparation failure message, if not the unique connection of the user, After the initiating the deletion of the related bearer of the local service, the handover preparation failure message is returned to the source home base station, where the handover preparation failure message includes a failure cause value of two;
  • the failure cause value two indicates that the target side does not support the local service, and also indicates that the local connection is not the user unique connection.
  • the switching method further includes:
  • the source home base station After receiving the handover preparation failure message, the source home base station locally determines whether the local service is established as a unique connection of the user, and if it is the only connection of the user, re-initiates the mobility management unit to New target base station handover request.
  • the switching method further includes: After receiving the handover preparation failure message, the source home base station locally determines whether the local service is established as a unique connection of the user, and if it is not the only connection of the user, initiates deletion of the local service. After the bearer, a handover request to the same target base station is initiated to the mobility management unit.
  • the switching method further includes:
  • the source home base station After receiving the handover preparation failure message, the source home base station determines locally whether the established local service is a unique connection of the user, and if it is not the only connection of the user, confirms the related bearer of the local service. After the deletion, a handover request to the same target base station is initiated to the mobility management unit.
  • the switching method further includes:
  • the source home base station After receiving the handover preparation failure message, the source home base station marks the target base station as a base station that the user cannot handover when re-initiating a handover request to the new target base station to the mobility management unit.
  • the step of the mobile management unit initiating deletion of the related bearer of the local service includes: the mobility management unit sends a delete session request to the local gateway through the core network access gateway, and carries the local connection context identifier;
  • the core network access gateway After the local gateway deletes the related bearer of the local connection, the core network access gateway sends a delete session response to the mobility management unit, and sends a delete bearer request to the source home base station;
  • the source home base station After the source home base station deletes the locally connected bearers, the source home base station returns a delete bearer response to the local gateway.
  • the step of the mobile management unit initiating deletion of the related bearer of the local service includes: the mobility management unit sends a delete session request to the local gateway through the core network access gateway, and carries the local connection context identifier;
  • the local gateway After the local gateway deletes the related bearer of the local connection, sends a delete session response to the mobility management unit by using the core network access gateway;
  • the mobility management unit After receiving the deletion session response, the mobility management unit sends a delete bearer request to the source home base station; After the source home base station deletes the locally connected bearers, the source home base station returns a delete bearer response to the mobility management unit.
  • the step of the source home base station initiating deletion of the related bearer of the local service includes: the source home base station sending a delete bearer request to the local gateway, requesting to delete the related bearer of the local connection;
  • the core network access gateway After the local gateway deletes the related bearers of the local connection, the core network access gateway sends a delete bearer request to the mobility management unit, and carries the context identifier of the local connection;
  • the mobility management unit After the mobility management unit and the core network access gateway delete the related bearer of the local connection, the mobility management unit sends a delete bearer response to the local gateway by using the core network access gateway.
  • a handover system for a local access service includes a service continuity determination module and a handover processing module in a core network mobility management unit, where:
  • the service continuity determining module is configured to: after receiving a handover request sent by the source home base station that the user establishes the local service, determine whether to allow the local base station to establish a local service;
  • the switching processing module is configured to: after determining that the user has established a local service, if it is determined that the local base station is not allowed to establish a local service, return a handover preparation failure message to the source home base station, and indicate in the handover preparation failure message The reason for the failure.
  • the switching processing module is further configured to: after determining that the user has established a local service, if it is determined that the local base station is allowed to establish a local service, send a handover command to the source home base station to perform the handover process of the user.
  • the switching system further includes a handover execution module in the home base station, where:
  • the handover processing module is further configured to determine, after returning the handover preparation failure message, that the established local service is not the only connection of the user, if it is the user The only connection, the handover preparation failure message is returned to the source home base station, and the failure reason value 1 is included in the handover preparation failure message;
  • the handover execution module is configured to: receive the handover preparation failure message, and determine a failure cause indicated therein, and if the failure cause value is one, re-initiate a handover request to the new target base station to the mobility management unit ; The failure cause value one indicates that the target side does not support the local service.
  • the switching system further includes a handover execution module in the home base station, where:
  • the handover processing module is further configured to: after determining that the local service is not allowed to be established in the target base station, before returning the handover preparation failure message, determining whether the local service is established as the unique connection of the user, if not the user The only connection, the handover preparation failure message is returned to the source home base station, and the failure reason value 2 is included in the handover preparation failure message;
  • the handover execution module is configured to: determine a failure cause indicated in the handover preparation failure message, and if the failure cause value is two, initiate deletion of a related bearer of the local service, and confirm deletion of the local service After the relevant bearer, re-initiating a handover request to the same target base station to the mobility management unit;
  • the failure cause value two indicates that the target side does not support the local service, and also indicates that the local connection is not the user unique connection.
  • the switching system further includes a handover execution module in the home base station, where:
  • the handover processing module is further configured to: after determining that the local service is not allowed to be established in the target base station, before returning the handover preparation failure message, determining whether the local service is established as the unique connection of the user, if not the user The unique connection, after the initiation of the deletion of the related bearer of the local service, the handover preparation failure message is returned to the source home base station, where the handover preparation failure message includes a failure cause value of two;
  • the handover execution module is configured to: determine a failure cause indicated in the handover preparation failure message, and if the failure cause value is two, re-send to the mobility management unit after confirming that the related bearer of the local service is deleted Initiating a handover request to the same target base station;
  • the failure cause value two indicates that the target side does not support the local service, and also indicates that the local connection is not the user unique connection.
  • the switching system further includes a handover execution module in the home base station, where:
  • the handover execution module is configured to: after receiving the handover preparation failure message, locally determine whether the established local service is a unique connection of the user, and if it is a unique connection of the user, re-send to the The mobility management unit initiates a handover request to the new target base station.
  • the switching system further includes a handover execution module in the home base station, where: The handover execution module is configured to: after receiving the handover preparation failure message, locally determine whether the established local service is a unique connection of the user, and if not the unique connection of the user, initiate a deletion After the relevant bearer of the local service is described, a handover request to the same target base station is re-initiated to the mobility management unit.
  • the switching system further includes a handover execution module in the home base station, where:
  • the handover execution module is configured to: after receiving the handover preparation failure message, locally determine whether the established local service is a unique connection of the user, and if not the unique connection of the user, confirm the After the relevant bearer of the local service is deleted, a handover request to the same target base station is re-initiated to the mobility management unit.
  • the handover execution module is further configured to: after receiving the handover preparation failure message, mark the target base station as the user when re-initiating a handover request to the new target base station to the mobility management unit. A base station that cannot be switched.
  • the foregoing technical solution provides a handover processing scheme for a local service in a mobile process for a UE that establishes a local service, and clarifies whether a local service continuity determination method can be supported, thereby being able to meet specific conditions.
  • the terminal provides continuity of local services and improves the business experience of these users.
  • 1 is a schematic diagram of an architecture of an evolved packet domain system
  • FIG. 2 is a schematic diagram of a structure of a user accessing a local service
  • FIG. 3 is a schematic diagram of a structure in which a user moves to another base station to access a local service
  • FIG. 4 is a flowchart of main processing steps of a method for switching a local access service according to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of implementing handover according to Embodiment 1 of the present invention
  • 6 is a schematic flowchart of implementing handover according to Embodiment 2 of the present invention
  • FIG. 7 is a schematic flowchart of implementing handover according to Embodiment 3 of the present invention.
  • the embodiment of the present invention provides a method for switching a local access service. After a user establishes a local service through a source home base station, when a handover occurs, the method includes the following steps:
  • Step 1 The source home base station selects the target base station to be handed over, and sends a handover request to the core network mobility management unit.
  • Step 2 After receiving the handover request, the mobility management unit determines that the local base station is not allowed to establish a local service.
  • Step 3 The mobility management unit returns a handover preparation failure message to the source home base station, and indicates a failure reason in the handover preparation failure message.
  • Figure 5 is a local connection suitable for a user to establish from a source home base station, and subsequently moved to another base station or home base station due to a change in location. Network) or GPRS network.
  • the home base station is an HNB
  • the base station is a BSS or a NodeB/RNC
  • the mobility management unit is an SGSN.
  • the home base station is the HeNB
  • the base station is the eNB
  • the mobility management unit is the MME.
  • the SGSN is connected to the local gateway through the Gn/Gp interface, there is no SGW in this process, and all the messages passing through the SGW do not need to pass through the SGW, but the mobile management unit sends the message directly to the local gateway.
  • the home base station there may be a home base station gateway in the network. If there is a home base station gateway, the messages between all the home base stations and the mobility management unit need to pass through the home base station gateway. Further, the message between the home base station and the local gateway may be through the home base station gateway or not through the home base station gateway.
  • the home base station gateway forwards the message, the home base station gateway transparently transmits the passed message, and the transparent transmission process has nothing to do with the present invention, and details are not described herein.
  • This embodiment is applicable to the case where the home base station and the local gateway have control plane signaling. As shown in FIG. 5, the process of this embodiment mainly includes the following steps:
  • Step 501 The location of the UE changes, and the source home base station detects the arrival handover threshold, and acquires the wireless measurement report of the neighboring area from the UE.
  • the source home base station selects the target base station according to the radio measurement report reported by the UE, and sends a handover request to the mobility management unit.
  • Step 502 The mobility management unit determines whether the user has a local service, such as local IP access (LIPA) or remote IP access (RIPA). If there is no local service, the existing technology is applied. Within the scope of the present invention; if the UE has established a local service, it is determined whether the information of the target base station is allowed to establish a local connection at the target base station according to the subscription data, and whether the local service is a unique PDN connection of the user, that is, the user does not have a core network. PDN connection.
  • LIPA local IP access
  • RIPA remote IP access
  • the information of the target base station includes but is not limited to one or any combination of the following: CSG information of the target base station, access mode information of the target base station (closed mode, open mode, or mixed mode), base station identity of the target base station, and cell of the target cell Logo.
  • the user subscription information includes the correspondence between the APN and the CSG, that is, whether the user is allowed to establish a correspondence to a local connection of a specific APN in some CSGs.
  • Step 503 If the local connection is allowed to be established in the target base station according to the determination in step 502, the subsequent process of the handover is performed, and the subsequent process is similar to the prior art, and details are not described herein.
  • Step 503a if it is not allowed to establish a local connection at the target base station according to the determination of step 502, it is further required to determine whether the local connection is a unique PDN connection of the UE, and if yes, perform steps 504a-506a; otherwise, perform step 504b ⁇ 510b;
  • Step 504a The mobility management unit returns a handover preparation failure message to the source home base station, where the failure indication is carried out, indicating that the failure reason is that the target side does not support the local service.
  • This indication can be achieved by extending the value of the existing cause value IE (Information Element) or by adding a new IE.
  • Step 505a The source home base station selects other handover-capable cells for the UE according to the indication information, and re-initiates the handover request to the mobility management unit, and starts execution in step 501. And identifying the cell that failed the handover as a cell that the UE cannot handover.
  • Step 506a if the source home base station finds that there are no other available handoverable cells, the handover attempt is terminated.
  • the release of the radio bearer is initiated after the wireless signal reaches the threshold.
  • Step 503b if it is determined according to the determination in step 502 that the connection to the target cell is not allowed, and further determining that the local connection is not the unique PDN connection of the UE, performing steps 504b ⁇ 51 Ob.
  • Step 504b The mobility management unit returns a handover preparation failure message to the source home base station, where the failure indication is carried out, indicating that the failure reason is that the target side does not support the local service.
  • the failure cause values in the foregoing steps 504a and 504b may be the same value or different values.
  • the source home base station determines whether the local connection is a unique connection according to the locally stored information, and then determines whether to continue the a process (unique connection) or the b process (non-unique connection).
  • the source home base station can judge whether to continue the a process or the b process according to different cause value indications.
  • the value of Element ) can also be achieved by adding a new IE.
  • the cause value can be used in the following manner:
  • the cause value one indicates that the target side does not support the local service; in step 504b, the extended cause value two can be carried, and the cause value is two. Indicates that the target side does not support the local service, and also indicates that the local connection is not the user's unique connection.
  • the original cause value of one may be carried, or the extended cause value of three may be carried, and the cause value of three indicates that the target side is not Support local business, and also indicates that the local connection is the user's only connection, and so on.
  • the meanings that are not supported include but are not limited to:
  • the target side network element does not support establishing a local connection; the subscription or configuration limit target side cannot establish a local connection.
  • the failure cause value in the foregoing step 504a and step 504b is the same value, and the mobility management unit additionally adds an indication of whether the local connection is a user unique connection in the returned handover preparation failure message, so that the source home base station can increase according to the Indicates whether to continue executing the a process or the b process.
  • the local bearer bearer/primary PDP context identifier is carried in the local connection.
  • Step 506b The local gateway deletes the related bearer of the local connection and deletes, and sends a delete session response to the mobility management unit by using the SGW.
  • Step 507b The local gateway sends a delete bearer request to the source home base station. If the local connection has multiple bearers, then the request needs to be able to remove these bearers. At this time, the source home base station may send multiple delete bearer requests, or delete the bearers simultaneously in one message.
  • Step 508b The source home base station returns a delete 7-load response to the local gateway.
  • Step 509b The source home base station does not re-initiate the handover (HO) procedure according to the cause value in step 504b and/or the indication information that is not the unique connection, until the handover procedure to the target base station is initiated after the bearer is deleted in step 507b.
  • HO handover
  • Step 510b performing a subsequent process of the handover, and the subsequent process is similar to the prior art, and details are not described herein.
  • This embodiment is applicable to a local connection established by a user from a source home base station, and subsequently moved to another base station or a home base station due to a change in location. Or GPRS gateway.
  • the home base station is an HNB
  • the base station is a BSS or a NodeB/RNC
  • the mobility management unit is an SGSN.
  • the home base station is the HeNB
  • the base station is the eNB
  • the mobility management unit is the MME.
  • the mobile management unit sends the message directly to the local gateway.
  • the home base station there may be a home base station gateway in the network, if there is a home base station network Off, then all messages between the home base station and the mobility management unit need to go through the home base station gateway. Further, the message between the home base station and the local gateway may be through the home base station gateway or not through the home base station gateway.
  • the home base station gateway transparently transmits the passed message, and the transparent transmission process has nothing to do with the present invention, and details are not described herein.
  • This embodiment is applicable to the case where the home base station and the local gateway have no control plane signaling. As shown in FIG. 6, the process of this embodiment mainly includes the following steps:
  • Step 601 The location of the UE changes, and the source home base station detects the arrival handover threshold, and acquires the wireless measurement report of the neighboring area from the UE.
  • the source home base station selects the target base station according to the radio measurement report reported by the UE, and sends a handover request to the mobility management unit.
  • Step 602 The mobility management unit determines whether the user has a local service. If there is no local service, applying the prior art is not within the scope of the present invention. If the UE establishes a local service, and the local service is the only bearer of the user. Then, it is necessary to judge whether the information of the target base station can establish the local connection according to the subscription data.
  • the information of the target base station includes but is not limited to one of the following: CSG information of the target base station, access mode information of the target base station, base station identity of the target base station, and cell identity of the target cell.
  • the subscription information contains a matching relationship between the APN and the CSG that allows the user to establish a local service.
  • Step 603 If the local connection is allowed to be established in the target cell according to the judgment of the step 602, the subsequent process of the handover is performed, and the subsequent process is similar to the prior art, and details are not described herein.
  • Step 603a if it is not allowed to establish a local connection at the target base station according to the judgment of step 602, it is further required to determine whether the local connection is a unique PDN connection of the UE. If yes, steps 604a-606a are performed.
  • Step 604a The mobility management unit returns a handover preparation failure message to the source home base station, where the failure indication is carried out, indicating that the failure reason is that the target side does not support the local service.
  • This indication can be achieved by extending the value of the existing cause value IE (Information Element) or by adding a new IE.
  • the meanings that are not supported include but are not limited to: The target side network element does not support establishing a local connection; the subscription or configuration limit target side cannot establish a local connection.
  • Step 605a The source home base station selects other handover-capable cells for the UE according to the indication information, and re-initiates the handover request to the mobility management unit, and starts execution in step 601. And identifying the cell that failed the handover as a cell that the UE cannot handover.
  • Step 606a If the source home base station finds that there are no other available handoverable cells, the handover attempt is terminated. The release of the radio bearer is initiated after the wireless signal reaches the threshold.
  • Step 603b if it is not allowed to establish a local connection in the target cell according to the judgment of step 602, it is further required to determine whether the local connection is a unique PDN connection of the UE. If no, steps 604b-610b are performed.
  • Step 604b The mobility management unit returns a handover preparation failure message to the source home base station, where the failure indication is carried out, indicating that the failure reason is that the target side does not support the local service.
  • This indication can be achieved by extending the value of the existing cause value IE (Information Element) or by adding a new IE.
  • the failure cause values in the above steps 604a and 604b may be the same value or different values.
  • the source home base station judges whether to continue the process a or b according to whether the local connection is a unique connection.
  • the source home base station can judge whether to continue the a process or the b process according to different cause value indications.
  • Element The value of Element ) can also be achieved by adding a new IE.
  • the cause value may be used as follows:
  • the cause value one indicates that the target side does not support the local service; in step 604b, the extended cause value two may be carried, and the cause value is two. Indicates that the target side does not support the local service, and also indicates that the local connection is not the user's unique connection.
  • the original cause value of one may be carried, or the extended cause value of three may be carried, and the cause value of three indicates that the target side does not Support local business, and also indicates that the local connection is the user's only connection, and so on.
  • the meanings that are not supported include but are not limited to: The target side network element does not support establishing a local connection; the subscription or configuration limit target side cannot establish a local connection.
  • the failure cause values in the above steps 604a and 604b are the same value, and the movement is
  • the management unit additionally adds an indication of whether the local connection is a user unique connection in the returned handover preparation failure message, so that the source home base station can judge whether to continue the a process or the b process according to the increase indication.
  • the local bearer/primary PDP context identifier is carried in the local connection.
  • Step 606b The local gateway deletes the related bearer of the local connection, and deletes the related session, and sends a delete session response to the mobility management unit by using the SGW.
  • Step 607b The mobility management unit sends a delete bearer request to the source home base station. If there are multiple bearers connected locally, the request needs to be able to remove these bearers. At this time, the source home base station can send multiple delete bearer requests, or delete the bearers simultaneously in one message.
  • Step 608b The source home base station returns a delete bearer response to the mobility management unit.
  • Step 609b The source home base station does not re-initiate the HO process according to the cause value in step 604b and/or the indication information that is not the only connection.
  • the handover procedure to the target base station is initiated until the bearer is deleted in step 607b.
  • Step 610b performing a subsequent process of the handover, and the subsequent process is similar to the prior art, and details are not described herein.
  • This embodiment is applicable to a local connection established by a user from a source home base station, and subsequently moved to another base station or a home base station due to a change in location.
  • This embodiment is applicable to a terminal accessing an EPC network or a GPRS gateway from GERAN/UTRAN/EUTRAN.
  • the home base station is an HNB
  • the base station is a BSS or a NodeB/RNC
  • the mobility management unit is an SGSN.
  • the home base station is the HeNB
  • the base station is the eNB
  • the mobility management unit is the MME.
  • the SGSN is connected to the local gateway through the Gn/Gp interface, there is no SGW in this process. All the messages passing through the SGW do not need to pass through the SGW, but the mobile management unit sends the message directly to the local gateway.
  • the home base station there may be a home base station gateway in the network. If there is a home base station gateway, all the messages between the home base station and the mobility management unit need to pass through the home base station gateway. Enter one The message between the stepped home base station and the local gateway may be through the home base station gateway or not through the home base station gateway.
  • the home base station gateway transparently transmits the passed message, and the transparent transmission process has nothing to do with the present invention, and no comment is made here.
  • This embodiment is applicable to the case where the home base station and the local gateway have control plane signaling. As shown in FIG. 7, the process of this embodiment mainly includes the following steps:
  • Step 701 The location of the UE changes, and the source home base station detects the arrival handover threshold, and acquires the wireless measurement report of the neighboring area from the UE.
  • the source home base station selects the target base station according to the radio measurement report reported by the UE, and sends a handover request to the mobility management unit.
  • Step 702 The mobility management unit determines whether the user has a local service. If there is no local service, applying the prior art is not within the scope of the present invention. If the UE establishes a local service, and the local service is the only bearer of the user. Then, it is necessary to judge whether the information of the target base station can establish the local connection according to the subscription data.
  • the information of the target base station includes but is not limited to one of the following: CSG information of the target base station, access mode information of the target base station, base station identity of the target base station, and cell identity of the target cell.
  • the subscription information contains a matching relationship between the APN and the CSG that allows the user to establish a local service.
  • Step 703 If the local connection is allowed to be established in the target cell according to the determination in step 702, the subsequent process of the handover is performed, and the subsequent process is similar to the prior art, and details are not described herein.
  • Step 703a if it is not allowed to establish a local connection in the target cell according to the judgment of step 702, it is further required to determine whether the local connection is a unique PDN connection of the UE. If yes, steps 704a-706a are performed.
  • Step 704a The mobility management unit returns a handover preparation failure message to the source home base station, where the failure indication is carried out, indicating that the failure reason is that the target side does not support the local service.
  • This indication can be achieved by extending the value of the existing cause value IE (Information Element) or by adding a new IE.
  • the meanings that are not supported include but are not limited to: The target side network element does not support establishing a local connection; the subscription or configuration limit target side cannot establish a local connection.
  • Step 705a The source home base station selects other handover-capable cells for the UE according to the indication information, and re-initiates the handover request to the mobility management unit, and starts execution in step 701. And identifying the cell that failed the handover as the cell that the UE cannot handover.
  • Step 706a if the source home base station finds that there are no other available handoverable cells, then Stop switching attempts. The release of the radio bearer is initiated after the wireless signal reaches the threshold.
  • step 703b if it is not allowed to establish a local connection in the target cell according to the judgment of step 702, it is further required to determine whether the local connection is a unique PDN connection of the UE. If no, steps 704b to 711b are performed.
  • Step 704b The mobility management unit returns a handover preparation failure message to the source home base station, where the failure indication is carried out, indicating that the failure reason is that the target side does not support the local service.
  • This indication can be achieved by extending the value of the existing cause value IE (Information Element) or by adding a new IE.
  • the failure cause values in the above steps 704a and 704b may be the same value or different values.
  • the source home base station judges whether to continue the process a or b according to whether the local connection is a unique connection.
  • the source home base station can judge whether to continue the a process or the b process according to different cause value indications.
  • Element The value of Element ) can also be achieved by adding a new IE.
  • the cause value may be used as follows:
  • the cause value one indicates that the target side does not support the local service; in step 704b, the extended cause value two may be carried, and the cause value is two. Indicates that the target side does not support the local service, and also indicates that the local connection is not the user's unique connection.
  • the original cause value of one may be carried, or the extended cause value of three may be carried, and the cause value of three indicates that the target side does not Support local business, and also indicates that the local connection is the user's only connection, and so on.
  • the meanings that are not supported include but are not limited to: The target side network element does not support establishing a local connection; the subscription or configuration limit target side cannot establish a local connection.
  • the failure cause value in the above steps 704a and 704b is the same value, and the mobility management unit additionally adds whether the local connection is unique to the user in the returned handover preparation failure message.
  • the indication is received, so that the source home base station can judge whether to continue the a process or the b process according to the increase indication.
  • Step 705b The source home base station actively initiates the delete of the local connection bearer request according to the cause value in the handover preparation failure message and/or the indication information that is not the unique connection in step 704b, and releases the local connection of the UE.
  • Step 706b The source home base station sends a delete bearer request to the local gateway. This request is used to request the local gateway to delete the local connection, but the name of this message is not limited to this. If the local connection has multiple bearers, then the request needs to be able to remove these bearers. At this time, the source home base station may send multiple delete bearer requests, or delete the bearers simultaneously in one message. The request carries the local 7?
  • Step 707b The local gateway deletes the related bearer of the local connection according to the request of the source home base station, and sends a delete bearer request to the mobility management unit by using the SGW, where the local connection default bearer/primary PDP context identifier is carried.
  • Step 708b the mobility management unit and the SGW delete related bearers of the local connection.
  • the mobility management unit sends a delete bearer response to the local gateway through the SGW.
  • Step 709b The local gateway sends a delete bearer request to the source home base station. If the local connection has multiple bearers, then the request needs to be able to remove these bearers. At this time, the source home base station may send multiple delete bearer requests, or delete the bearers simultaneously in one message.
  • the source home base station does not re-initiate the HO process according to the cause value in step 704b and/or the indication information that is not the only connection.
  • the handover procedure to the target base station is initiated until the bearer is deleted in step 709b.
  • Step 711b performing a subsequent process of the handover, and the subsequent process is similar to the prior art, and details are not described herein.
  • the mobility management unit further determines whether the local connection is a user unique connection, and notifies the source home base station whether the local connection is a unique connection of the user by using different cause values and/or additional indication information. In other embodiments of the present invention, the mobility management unit may also determine whether the local connection is a unique connection of the user, or only judge but not notify the source home base station, but the source home base station makes the local determination. In addition, in the foregoing embodiment, when the mobile management unit determines that the local connection is not the user's unique connection, the related bearer that deletes the local connection is initiated; or the source home base station according to the cause value and/or the additional indication in the handover preparation failure message.
  • the information determines that the local connection is not the only connection of the user, and initiates the deletion of the relevant bearer of the local connection.
  • the source home base station may initiate the deletion of the related bearer of the local connection when the local base station determines that the local connection is not the user unique connection.
  • the embodiment of the present invention further provides a handover system for local access services, where the system mainly includes a service continuity determination module and a handover processing module in a core network mobility management unit, where:
  • the service continuity determining module is configured to: after receiving a handover request sent by the source home base station that the user establishes the local service, determine whether to allow the local base station to establish a local service;
  • the handover processing module is configured to: if it is determined that the local base station is not allowed to establish a local service, return a handover preparation failure message to the source home base station, and indicate a failure reason in the handover preparation failure message.
  • the handover processing module is further configured to: if it is determined that the local service is allowed to be established in the target base station, send a handover command to the source home base station, and perform the handover process of the user.
  • the system further includes a handover execution module in the home base station,
  • the handover processing module is further configured to: determine, after returning the handover preparation failure message, that the established local service is a unique connection of the user, after determining that the local base service is not allowed to be established, Returning, by the user, the handover preparation failure message to the source home base station, and including a failure cause value 1 in the handover preparation failure message;
  • the handover execution module is configured to: receive the handover preparation failure message, and according to the failure reason indicated therein, if the failure cause value is one, re-initiate the mobility management unit to the new target base station Switch the request.
  • the switching processing module is further configured to: determine, after returning the handover preparation failure message, that the established local service is a unique connection of the user, if not The unique connection of the user returns the handover preparation failure message to the source home base station, and includes a failure cause value in the handover preparation failure message.
  • the handover execution module is configured to: according to the failure reason indicated in the handover preparation failure message, if the failure cause value is two, initiate deletion of the relevant bearer of the local service, and confirm deletion of the local After the relevant bearer of the service, a handover request to the same target base station is re-initiated to the mobility management unit.
  • the switching processing module is further configured to: determine, after returning the handover preparation failure message, that the established local service is a unique connection of the user, if not The unique connection of the user, after initiating the deletion of the related bearer of the local service, returning the handover preparation failure message to the source home base station, where the handover preparation failure message includes a failure cause value of two;
  • the handover execution module is configured to: according to the failure reason indicated in the handover preparation failure message, if the failure cause value is two, after confirming that the related bearer of the local service is deleted, re-moving to the mobile
  • the management unit initiates a handover request to the same target base station.
  • the system further includes a handover execution module in the home base station,
  • the handover execution module is configured to: after receiving the handover preparation failure message, locally determine whether the established local service is a unique connection of the user, and if it is a unique connection of the user, re-send to the The mobility management unit initiates a handover request to the new target base station.
  • the handover execution module is configured to: after receiving the handover preparation failure message, locally determine whether the established local service is a unique connection of the user, and if not the unique connection of the user, initiate After deleting the relevant bearer of the local service, a handover request to the same target base station is re-initiated to the mobility management unit.
  • the handover execution module is configured to: after receiving the handover preparation failure message, locally determine whether the established local service is a unique connection of the user, and if it is not the unique connection of the user, confirm After the related bearer of the local service is deleted, a handover request to the same target base station is re-initiated to the mobility management unit.
  • the handover execution module is further configured to: after receiving the handover preparation failure message, mark the target base station as the user when re-initiating a handover request to the new target base station to the mobility management unit. A base station that cannot be switched.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
  • the invention is not limited to any particular combination of hardware and software.
  • the foregoing technical solution provides a handover processing scheme for a local service in a mobile process for a UE that establishes a local service, and clarifies whether a local service continuity determination method can be supported, thereby providing a local service for a terminal that meets a specific condition. Continuity to improve the business experience of this part of the user. Therefore, the present invention has strong industrial applicability.

Landscapes

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

Abstract

一种本地访问业务的切换方法和系统，所述切换方法包括：用户通过源家用基站建立本地业务后，发生切换时，执行以下步骤：所述源家用基站选择切换的目标基站，向核心网的移动管理单元发送切换请求；所述移动管理单元收到所述切换请求后，如果判定不允许在目标基站建立本地业务，则向所述源家用基站返回切换准备失败消息，并在所述切换准备失败消息中指示失败原因。上述技术方案明确了能否支持本地业务连续性的判定方法，从而可以为符合特定条件的终端提供本地业务的连续性，提高这部分用户的业务体验。

Description

一种本地访问业务的切换方法及系统
技术领域
本发明涉及移动通信领域， 具体涉及一种本地访问业务的切换方法及系 统。
背景技术
为了保持第三代移动通信系统在通信领域的竟争力， 为用户提供速率更 快、时延更低、更加个性化的移动通信服务， 同时， 降低运营商的运营成本， 第三代合作伙伴计划（3GPP, 3rd Generation Partnership Project )标准工作组 正致力于演进分组系统（EPS, Evolved Packet System ) 的研究。
图 1示出了演进分组域系统的结构示意图， 如图 1所示， 整个 EPS系统 分为无线接入网和核心网两部分。在核心网中，包含了归属用户服务器（ HSS, Home Subscriber Server ) 、 移动性管理实体 ( MME, Mobility Management Entity ) 、 服务 GPRS支持节点 （SGSN, Serving GPRS Support Node ) 、 策 略计费规则功能（ PCRF, Policy and Charging Rule Function )、服务网关（ S-GW, Serving Gateway ) 、 分组数据网关（ P-GW, PDN Gateway )和分组数据网络 ( PDN, Packet Data Network ) 。 下面将介绍各网元 /节点的主要功能：
归属用户服务器（HSS ) , 包含了归属位置寄存器（HLR )的所有功能， 是用户签约数据的永久存放地点， 位于用户签约的归属网。
移动性管理实体（MME ) , 是用户签约数据在当前网络的存放地点， 负 责终端到网络的非接入层信令管理、 终端的安全验证功能、 终端的移动性管 理、 用户空闲模式下的跟踪和寻呼管理功能和承载管理。
服务 GPRS支持节点（ SGSN ) , 是 GSM无线接入网络（ GERAN, GSM EDGE Radio Access Network )和 UMTS陆地无线接入网 （UTRAN, UMTS Terrestrial Radio Access Network )用户接入核心网络的业务支持点， 功能上 与移动性管理实体类似，负责用户的位置更新、寻呼管理和承载管理等功能。
服务网关， 是核心网到无线系统的网关， 负责终端到核心网的用户面承 载、 终端空闲模式下的数据緩存、 网络侧发起业务请求的功能、 合法监听和 分组数据路由和转发功能； 服务网关负责统计用户终端使用无线网的情况， 并产生终端使用无线网的话单， 传送给计费网关。
分组数据网关， 是演进系统和该系统外部分组数据网络的网关， 它连接 到因特网和分组数据网络上， 负责终端的互联网协议（ IP , Internet Protocol ) 地址分配、 计费功能、 分组包过滤、 策略控制等功能。
通用无线分组业务（ GPRS, General Packet Radio Service )网关支持节点 ( GGSN, Gateway GPRS Support Node ) ,支持 GPRS网络的边缘路由功能， 即 GGSN负责将 GPRS网络的数据进行路由转发，并通过防火墙和过滤功能 来保护 GPRS网络数据的完整性。 GGSN还具有计费功能。
P-GW包含了 GGSN的全部功能，即可认为 GGSN作为 P-GW的一个子 功能， 内嵌在 P-GW内。 因此 SGSN可以直接和 P-GW连接， 使用 Gn/Gp 接口。
分组数据网络，是运营商的 IP业务网络， 该网络通过运营商的核心网为 用户提供 IP服务。
策略计费规则功能实体， 是演进系统中负责提供计费控制、 在线信用控 制、 门限控制、服务质量（QoS, Quality of Service )策略方面规则的服务器。
无线接入网 , 是由演进基站（ eNB , E-UTRAN NodeB )和 3G无线网络 控制器（RNC, Radio Network Control )组成， 它主要负责无线信号的收发， 通过空中接口和终端联系，管理空中接口的无线资源、资源调度、接入控制。
家用基站（HNB, Home NodeB )或者演进的家用基站 （HeNB, Home eNodeN )是一类小型、 低功率的基站， 作为某些用户的专属资源， 部署在家 庭、 团体、 公司或者学校等私人场所使用， 主要是为了给用户提供更高的业 务速率并降低使用高速率服务所需要的费用， 同时弥补已有分布式蜂窝无线 通信系统覆盖的不足。 家用基站的优点是实惠、 便捷、 低功率输出、 即插即 用、 宽带接入、 使用单模终端等。
家用基站可以应用在第三代移动通信技术（3G, 3rd Generation )或者长 期演进（LTE, Long Term Evolution )移动通信网络中。 为了便于对家用基 站进行管理， 在网络中引入了一个新网元， 即家用基站网关。 家用基站网关 主要执行的功能为： 验证家用基站的安全性， 对家用基站的运行进行维护管 理， 根据运营商要求配置和控制家用基站， 负责交换核心网和家用基站的数 据信息。
为了提供不同的私密性，家用基站有不同的接入模式，分别为闭合模式， 混合模式以及开放模式。 对于前两种模式， 用户从基站的时候需要验证用户 的闭合用户组（ CSG, closed subscribed group )签约信息。
家用基站除了支持通过移动核心网络的接入之外，还可以支持本地 IP接 入功能， 在家用基站具备本地 IP接入能力并且用户签约允许本地 IP访问的 条件下，可以实现用户对家庭网络其他 IP设备或者互联网络的本地接入。通 过本地接入功能， 可以实现 Internet数据业务的分流， 降低核心网负荷， 并 且对于家庭网络设备的访问可以不通过核心网来进行转发， 数据传输便捷高 效。 本地 IP接入功能在宏蜂窝上也可以使用， 主要用途和家用基站类似， 更 多的是应用在本地 IP接入 Internet这种场景， 目的是降低核心网负荷。
图 2给出了实现上述本地接入功能的架构， 其中， 本地网关作为本地接 入到外部网络（例如 Internet ) 的网络， 提供地址分配、 计费、 分组包过滤、 策略控制、数据分流功能、无线接入网应用部分（NAS/RANAP, Radios Access Network Application Part )消息解析、 网络地址转换（NAT, Network Address Translation ) 、 本地 IP访问策略路由和执行等功能。 此外， 本地网关还可以 实现内部网络的访问， 实现本地网关所辖范围内， 不同的终端直接， 以及内 部网络的互访。 该网元作为一个独立逻辑单元， 在实际部署的时候可以将其 和现有的家用基站联合部署。 对于宏蜂窝实现本地接入架构， 本地网关可以 也可以和基站联合部署。 也可以作为独立的网元单独部署。
本地网关在实现内部网络访问的功能时， 为了保证内部网络的私密性， 需要对接入内部网络的终端进行验证， 根据用户的签约信息， 移动管理单元 (包括 MME和 SGSN )要对用户进行验证。 只有在特定的 CSG接入特定的 APN才能够进行本地业务的访问。
现有技术中， 本地网关与家用基站合设， 并且不支持移动性。 这样会导 致 UE从建立本地连接的家用基站离开后， 本地业务中断， 导致用户的体验 比较差。 因此业界开始研究如何保证 UE从移动后依然能够保证本地业务连 续， UE从其他基站进行本地业务如图 3所示。
但是由于本地业务的特殊性， 可能涉及本地网络的私密性问题。 因此在 保证 UE移动过程中本地业务的连续性的同时， 还需要考虑如何保护本地业 务以及本地网络中网元和信息的私密性。 而目前还没有相应的解决方案。
发明内容
本发明解决的技术问题是提供一种本地访问业务的切换方法及系统， 以 解决用户切换过程中本地业务的连续性问题。
为解决上述技术问题， 本发明釆用如下技术方案：
一种本地访问业务的切换方法， 所述切换方法包括： 用户通过源家用基 站建立本地业务后， 发生切换时， 执行以下步骤：
所述源家用基站选择切换的目标基站， 向核心网的移动管理单元发送切 换请求；
所述移动管理单元收到所述切换请求后， 如果判定不允许在目标基站建 立本地业务， 则向所述源家用基站返回切换准备失败消息， 并在所述切换准 备失败消息中指示失败原因。
所述切换方法还包括：
所述移动管理单元收到所述切换请求后， 如果判定允许在目标基站建立 本地业务， 则向所述源家用基站发送切换命令， 执行所述用户的切换过程。
所述切换方法还包括：
所述移动管理单元在判定不允许在目标基站建立本地业务后， 返回所述 切换准备失败消息之前， 判断已建立本地业务是否为所述用户的唯一连接， 如果是所述用户的唯一连接， 则向所述源家用基站返回所述切换准备失败消 息， 并在所述切换准备失败消息中包含失败原因值一；
所述源家用基站判断所述切换准备失败消息中指示的失败原因， 如果是 所述失败原因值一， 则重新向所述移动管理单元发起到新的目标基站的切换 请求； 其中， 所述失败原因值一表示目标侧不支持本地业务。
所述切换方法还包括：
所述移动管理单元在判定不允许在目标基站建立本地业务后， 返回所述 切换准备失败消息之前， 判断已建立本地业务是否为所述用户的唯一连接， 如果不是所述用户的唯一连接， 则向所述源家用基站返回所述切换准备失败 消息， 并在所述切换准备失败消息中包含失败原因值二；
所述源家用基站判断所述切换准备失败消息中指示的失败原因， 如果是 所述失败原因值二， 则发起删除所述本地业务的相关承载， 并在确认删除所 述本地业务的相关承载之后， 重新向所述移动管理单元发起到同一目标基站 的切换请求；
其中， 所述失败原因值二表示目标侧不支持本地业务， 同时还表示本地 连接不是用户唯一连接。
所述切换方法还包括：
所述移动管理单元在判定不允许在目标基站建立本地业务后， 返回所述 切换准备失败消息之前， 判断已建立本地业务是否为所述用户的唯一连接， 如果不是所述用户的唯一连接， 则在发起删除所述本地业务的相关承载后， 向所述源家用基站返回所述切换准备失败消息， 所述切换准备失败消息中包 含失败原因值二；
所述源家用基站判断所述切换准备失败消息中指示的失败原因， 如果是 所述失败原因值二， 则在确认所述本地业务的相关承载删除后， 重新向所述 移动管理单元发起到同一目标基站的切换请求；
其中， 所述失败原因值二表示目标侧不支持本地业务， 同时还表示本地 连接不是用户唯一连接。
所述切换方法还包括：
所述源家用基站收到所述切换准备失败消息后， 在本地判断已建立本地 业务是否为所述用户的唯一连接， 如果是所述用户的唯一连接， 则重新向所 述移动管理单元发起到新的目标基站的切换请求。
所述切换方法还包括： 所述源家用基站收到所述切换准备失败消息后， 在本地判断已建立本地 业务是否为所述用户的唯一连接， 如果不是所述用户的唯一连接， 则在发起 删除所述本地业务的相关承载之后， 重新向所述移动管理单元发起到同一目 标基站的切换请求。
所述切换方法还包括：
所述源家用基站收到所述切换准备失败消息后， 在本地判断已建立本地 业务是否为所述用户的唯一连接， 如果不是所述用户的唯一连接， 则在确认 所述本地业务的相关承载删除之后， 重新向所述移动管理单元发起到同一目 标基站的切换请求。
所述切换方法还包括：
所述源家用基站收到所述切换准备失败消息后， 在重新向所述移动管理 单元发起到新的目标基站的切换请求时， 将所述目标基站标记为所述用户不 能切换的基站。
其中，所述移动管理单元发起删除所述本地业务的相关承载的步骤包括： 所述移动管理单元通过核心网接入网关向本地网关发送删除会话请求， 携带本地连接上下文标识；
所述本地网关将所述本地连接的相关承载删除后， 通过所述核心网接入 网关向所述移动管理单元发送删除会话响应， 同时向所述源家用基站发送删 除承载请求；
所述源家用基站将所述本地连接的承载都删除后， 向所述本地网关返回 删除承载响应。
其中，所述移动管理单元发起删除所述本地业务的相关承载的步骤包括： 所述移动管理单元通过核心网接入网关向本地网关发送删除会话请求， 携带本地连接上下文标识；
所述本地网关将所述本地连接的相关承载删除后， 通过所述核心网接入 网关向所述移动管理单元发送删除会话响应；
所述移动管理单元收到所述删除会话响应后， 向所述源家用基站发送删 除承载请求； 所述源家用基站将所述本地连接的承载都删除后， 向所述移动管理单元 返回删除承载响应。
其中， 所述源家用基站发起删除所述本地业务的相关承载的步骤包括： 所述源家用基站向本地网关发送删除承载请求， 请求删除本地连接的相 关承载；
所述本地网关将本地连接的相关承载都删除后， 通过核心网接入网关向 所述移动管理单元发送删除承载请求， 携带本地连接的上下文标识；
所述移动管理单元及所述核心网接入网关删除本地连接的相关承载后， 所述移动管理单元通过所述核心网接入网关向本地网关发送删除承载响应。
一种本地访问业务的切换系统， 所述切换系统包括核心网移动管理单元 中的业务连续性判定模块和切换处理模块， 其中：
所述业务连续性判定模块设置成： 收到用户建立本地业务的源家用基站 发送的切换请求后， 判定是否允许在目标基站建立本地业务；
所述切换处理模块设置成： 确定用户已建立本地业务后， 如果判定不允 许在目标基站建立本地业务， 则向所述源家用基站返回切换准备失败消息， 并在所述切换准备失败消息中指示失败原因。
其中， 所述切换处理模块还设置成： 确定用户已建立本地业务后， 如果 判定允许在目标基站建立本地业务， 则向所述源家用基站发送切换命令， 执 行所述用户的切换过程。
所述切换系统还包括家用基站中的切换执行模块， 其中：
所述切换处理模块还设置成：在判定不允许在目标基站建立本地业务后， 返回所述切换准备失败消息之前， 判断已建立本地业务是否为所述用户的唯 一连接， 如果是所述用户的唯一连接， 则向所述源家用基站返回所述切换准 备失败消息， 并在所述切换准备失败消息中包含失败原因值一；
所述切换执行模块设置成： 接收所述切换准备失败消息， 并判断其中指 示的失败原因， 如果是所述失败原因值一， 则重新向所述移动管理单元发起 到新的目标基站的切换请求； 其中， 所述失败原因值一表示目标侧不支持本地业务。
所述切换系统还包括家用基站中的切换执行模块， 其中：
所述切换处理模块还设置成：在判定不允许在目标基站建立本地业务后， 返回所述切换准备失败消息之前， 还判断已建立本地业务是否为所述用户的 唯一连接， 如果不是所述用户的唯一连接， 则向所述源家用基站返回所述切 换准备失败消息， 并在所述切换准备失败消息中包含失败原因值二；
所述切换执行模块设置成： 判断所述切换准备失败消息中指示的失败原 因， 如果是所述失败原因值二， 则发起删除所述本地业务的相关承载， 并在 确认删除所述本地业务的相关承载之后， 重新向所述移动管理单元发起到同 一目标基站的切换请求；
其中， 所述失败原因值二表示目标侧不支持本地业务， 同时还表示本地 连接不是用户唯一连接。
所述切换系统还包括家用基站中的切换执行模块， 其中：
所述切换处理模块还设置成：在判定不允许在目标基站建立本地业务后， 返回所述切换准备失败消息之前， 还判断已建立本地业务是否为所述用户的 唯一连接， 如果不是所述用户的唯一连接， 则在发起删除所述本地业务的相 关承载后， 向所述源家用基站返回所述切换准备失败消息， 所述切换准备失 败消息中包含失败原因值二；
所述切换执行模块设置成： 判断所述切换准备失败消息中指示的失败原 因， 如果是所述失败原因值二， 则在确认所述本地业务的相关承载删除后， 重新向所述移动管理单元发起到同一目标基站的切换请求；
其中， 所述失败原因值二表示目标侧不支持本地业务， 同时还表示本地 连接不是用户唯一连接。
所述切换系统还包括家用基站中的切换执行模块， 其中：
所述切换执行模块设置成： 收到所述切换准备失败消息后， 在本地判断 所述已建立本地业务是否为所述用户的唯一连接， 如果是所述用户的唯一连 接， 则重新向所述移动管理单元发起到新的目标基站的切换请求。
所述切换系统还包括家用基站中的切换执行模块， 其中： 所述切换执行模块设置成： 收到所述切换准备失败消息后， 在本地判断 所述已建立本地业务是否为所述用户的唯一连接， 如果不是所述用户的唯一 连接， 则在发起删除所述本地业务的相关承载之后， 重新向所述移动管理单 元发起到同一目标基站的切换请求。
所述切换系统还包括家用基站中的切换执行模块， 其中：
所述切换执行模块设置成： 收到所述切换准备失败消息后， 在本地判断 所述已建立本地业务是否为所述用户的唯一连接， 如果不是所述用户的唯一 连接， 则在确认所述本地业务的相关承载删除之后， 重新向所述移动管理单 元发起到同一目标基站的切换请求。
其中， 所述切换执行模块还设置成： 收到所述切换准备失败消息后， 在 重新向所述移动管理单元发起到新的目标基站的切换请求时， 将所述目标基 站标记为所述用户不能切换的基站。
由上所述， 上述技术方案提供了一种对于建立了本地业务的 UE在移动 过程中， 本地业务的切换处理方案， 明确了能否支持本地业务连续性的判定 方法， 从而可以为符合特定条件的终端提供本地业务的连续性， 提高这部分 用户的业务体验。
附图概述
此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中：
图 1是演进分组域系统的架构示意图；
图 2是用户访问本地业务的架构示意图；
图 3是用户移动到其他基站访问本地业务的架构示意图；
图 4是本发明实施例的本地访问业务的切换方法的主要处理步骤流程图; 图 5是本发明实施例一的实现切换的流程示意图； 图 6是本发明实施例二的实现切换的流程示意图；
图 7是本发明实施例三的实现切换的流程示意图。
本发明的较佳实施方式
如图 4所示， 本发明实施例提供了一种本地访问业务的切换方法， 用户 通过源家用基站建立本地业务后， 发生切换时， 主要包括以下步骤：
步骤 1 , 源家用基站选择切换的目标基站， 向核心网移动管理单元发送 切换请求；
步骤 2, 移动管理单元收到所述切换请求后， 判定不允许在目标基站建 立本地业务；
步骤 3 , 移动管理单元向源家用基站返回切换准备失败消息， 切换准备 失败消息中指示失败原因。
为了便于阐述本发明， 以下将结合附图及具体实施例对本发明技术方案 的实施作进一步详细描述。 需要说明的是， 在不冲突的情况下， 本申请中的 实施例及实施例中的特征可以相互任意组合。 这些组合均在本发明的保护范 围内。
实施例一
图 5是适用于用户从源家用基站建立的本地连接， 后续由于位置发生了 变化， 移动到了其他的基站或者家用基站。 网 )或者 GPRS网络。如果 UE从 GERAN/UTRAN接入，家用基站为 HNB, 基站为 BSS或者 NodeB/RNC,移动管理单元为 SGSN。如果 UE从 EUTRAN 接入， 家用基站为 HeNB, 基站为 eNB, 移动管理单元为 MME。 如果对于 SGSN通过 Gn/Gp接口连接本地网关的架构，则本流程中没有 SGW,所有经 过 SGW的消息都不需要经过 SGW,而是移动管理单元直接发送给本地网关。 对于家用基站的场景， 网络中可能存在家用基站网关， 如果存在家用基站网 关，那么所有家用基站和移动管理单元之间的消息都需要经过家用基站网关。 进一步的家用基站和本地网关之间的消息， 可以通过家用基站网关也可以不 通过家用基站网关。 对于通过家用基站网关转发消息的场景， 家用基站网关 对经过的消息进行透传， 透传的过程与本发明无关， 这里不做赘述。
本实施例适用于家用基站与本地网关有控制面信令的情况。如图 5所示， 本实施例流程主要包括如下步骤：
步骤 501 , UE位置发生变化， 源家用基站检测到达切换门限， 则向 UE 获取临近区域的无线测量报告。 源家用基站根据 UE上报的无线测量报告选 择目标基站， 并向移动管理单元发送切换请求。
步骤 502,移动管理单元判断用户是否有本地业务，如本地 IP接入（ LIPA, Local IP access )或远程 IP接入（ RIPA, Remote IP access ) , 如果没有本地 业务， 则应用现有技术， 不在本发明的考虑范围内； 如果 UE已建立本地业 务， 则需要根据签约数据判断目标基站的信息是否允许在目标基站建立本地 连接，并判断本地业务是否用户的唯一 PDN连接，即该用户没有核心网 PDN 连接。 目标基站的信息包含但不限于以下之一或其任意组合： 目标基站的 CSG信息， 目标基站接入模式信息 (闭合模式，开放模式，或者混合模式）， 目标基站的基站标识，目标小区的小区标识。其中，用户签约信息中包含 APN 和 CSG的对应关系，即是否允许用户在某些 CSG建立到特定 APN的本地连 接的对应关系。
步骤 503 , 如果根据步骤 502的判断， 允许在目标基站建立本地连接， 则执行切换的后续过程， 后续过程与现有技术类似， 这里不做赘述。
步骤 503a,如果根据步骤 502的判断，不允许在目标基站建立本地连接， 则还需要进一步判断本地连接是否为 UE的唯一 PDN连接， 如果是， 则执行 步骤 504a~506a; 否则， 执行步骤 504b~510b;
步骤 504a, 移动管理单元向源家用基站返回切换准备失败消息， 其中携 带失败指示， 指示失败原因为目标侧不支持本地业务。 该指示可以通过扩展 现有的原因值 IE ( Information Element ) 的取值 , 或者增加新的 IE来实现。
不支持的含义包括但不限于： 目标侧网元不支持建立本地连接； 签约或 者配置限定目标侧不能够建立本地连接。 步骤 505a,源家用基站根据指示信息，为 UE选择其他可以切换的小区， 并且重新发起切换请求给移动管理单元， 从步骤 501开始执行。 并且将切换 失败的小区标识为该 UE不能切换的小区。
步骤 506a, 如果源家用基站发现没有其他可用的可以切换的小区， 则终 止切换尝试。 在无线信号到达门限值之后发起无线承载的释放。
步骤 503b, 如果根据步骤 502的判断， 判断不允许在目标小区建立地连 接，且进一步判断本地连接不是 UE的唯一 PDN连接，则执行步骤 504b~51 Ob。
步骤 504b, 移动管理单元向源家用基站返回切换准备失败消息， 其中携 带失败指示， 指示失败原因为目标侧不支持本地业务。
其中， 上述步骤 504a和步骤 504b中的失败原因值可以是相同取值， 或 者是不同取值。
其中， 如果源家用基站在建立本地连接的时候， 已经获知哪些承载是本 地连接相关的承载， 那么失败的原因值是可以相同的。 源家用基站在收到上 述原因值之后， 根据本地存储的信息来判断本地连接是否是唯一连接， 进而 来判断继续执行 a过程 (唯一连接 )还是 b过程 (非唯一连接 ) 。
如果源家用基站无法获知哪些承载是本地连接相关的承载， 则上述失败 的原因值需要是不同的取值。 这样， 源家用基站能够根据不同的原因值指示 来判断继续执行 a过程还是 b过程。 Element ) 的取值， 也可以通过增加新的 IE来实现。
对于移动管理单元判断是唯一连接的情况， 原因值可以釆用如下方式： 原因值一（ causel )表示目标侧不支持本地业务； 在步骤 504b中， 可以 携带扩展的原因值二， 该原因值二表示目标侧不支持本地业务， 同时还表示 本地连接不是用户唯一连接； 而在步骤 504a中， 可以携带原有的原因值一， 也可以携带扩展的原因值三， 该原因值三表示目标侧不支持本地业务， 同时 还表示本地连接是用户唯一连接， 等。
不支持的含义包括但不限于： 目标侧网元不支持建立本地连接； 签约或 者配置限定目标侧不能够建立本地连接。 或者， 上述步骤 504a和步骤 504b中的失败原因值为相同取值， 而移动 管理单元在返回的切换准备失败消息中另外增加本地连接是否为用户唯一连 接的指示， 从而源家用基站可以根据该增加指示判断继续执行 a过程还是 b 过程。 中携带本地连接默认承载 /主 PDP上下文标识。
步骤 506b, 本地网关删除本地连接的相关承载都删除， 并通过 SGW向 移动管理单元发送删除会话响应。
步骤 507b, 本地网关向源家用基站发送删除承载请求。 如果本地连接有 多个承载， 那么该请求需要能够将这些承载都删除。 此时源家用基站可以发 送多个删除承载请求， 或者在一条消息中同时删除这些承载。
步骤 508b , 源家用基站向本地网关返回删除 7 载响应。
步骤 509b, 源家用基站根据步骤 504b中的原因值和 /或不是唯一连接的 指示信息， 暂不重新发起切换（HO ) 流程， 直到在步骤 507b删除承载之后 再发起到目标基站的切换流程。
步骤 510b, 执行切换的后续过程， 后续过程与现有技术类似， 这里不做 赘述。
实施例二
本实施例适用于用户从源家用基站建立的本地连接， 后续由于位置发生 了变化， 移动到了其他的基站或者家用基站。 或者 GPRS网关。 如果 UE从 GERAN/UTRAN接入， 家用基站为 HNB, 基 站为 BSS或者 NodeB/RNC, 移动管理单元为 SGSN。 如果 UE从 EUTRAN 接入， 家用基站为 HeNB, 基站为 eNB, 移动管理单元为 MME。 如果对于 SGSN通过 Gn/Gp接口连接本地网关的架构，则本流程中没有 SGW,所有经 过 SGW的消息都不需要经过 SGW,而是移动管理单元直接发送给本地网关。 对于家用基站的场景， 网络中可能存在家用基站网关， 如果存在家用基站网 关，那么所有家用基站和移动管理单元之间的消息都需要经过家用基站网关。 进一步的家用基站和本地网关之间的消息， 可以通过家用基站网关也可以不 通过家用基站网关。 对于通过家用基站网关转发消息的场景， 家用基站网关 对经过的消息进行透传， 透传的过程与本发明无关， 这里不做赘述。
本实施例适用于家用基站与本地网关没有控制面信令的情况。 如图 6所 示， 本实施例流程主要包括如下步骤：
步骤 601 , UE位置发生变化， 源家用基站检测到达切换门限， 则向 UE 获取临近区域的无线测量报告。 源家用基站根据 UE上报的无线测量报告选 择目标基站， 并向移动管理单元发送切换请求。
步骤 602,移动管理单元判断用户是否有本地业务。如果没有本地业务， 则应用现有技术， 不在本发明的考虑范围内。 如果 UE建立本地业务， 并且 本地业务是用户的唯一承载。 则需要根据签约数据判断目标基站的信息是否 可以建立该本地连接。 目标基站的信息包含但不限于以下之一： 目标基站的 CSG信息， 目标基站接入模式信息， 目标基站的基站标识， 目标小区的小区 标识。 签约信息包含允许用户建了本地业务的 APN和 CSG的匹配关系。
步骤 603 , 如果根据步骤 602的判断， 允许在目标小区建立本地连接， 则执行切换的后续过程， 后续过程与现有技术类似， 这里不做赘述。
步骤 603a,如果根据步骤 602的判断，不允许在目标基站建立本地连接， 则还需要进一步判断本地连接是否为 UE的唯一 PDN连接。 如果是， 则执行 步骤 604a~606a。
步骤 604a, 移动管理单元向源家用基站返回切换准备失败消息， 其中携 带失败指示， 指示失败原因为目标侧不支持本地业务。 该指示可以通过扩展 现有的原因值 IE ( Information Element ) 的取值 , 或者增加新的 IE来实现。
不支持的含义包括但不限于： 目标侧网元不支持建立本地连接； 签约或 者配置限定目标侧不能够建立本地连接。
步骤 605a,源家用基站根据指示信息，为 UE选择其他可以切换的小区， 并且重新发起切换请求给移动管理单元， 从步骤 601开始执行。 并且将切换 失败的小区标识为该 UE不能切换的小区。 步骤 606a, 如果源家用基站发现没有其他可用的可以切换的小区， 则终 止切换尝试。 在无线信号到达门限值之后发起无线承载的释放。
步骤 603b,如果根据步骤 602的判断，不允许在目标小区建立本地连接， 则还需要进一步判断本地连接是否为 UE的唯一 PDN连接。 如果否， 则执行 步骤 604b~610b。
步骤 604b, 移动管理单元向源家用基站返回切换准备失败消息， 其中携 带失败指示， 指示失败原因为目标侧不支持本地业务。 该指示可以通过扩展 现有的原因值 IE ( Information Element ) 的取值 , 或者增加新的 IE来实现。
其中， 上述步骤 604a和步骤 604b中的失败原因值可以是相同取值， 或 者是不同取值。
其中， 如果源家用基站在建立本地连接的时候， 已经获知哪些承载是本 地连接相关的承载， 那么失败的原因值是可以相同的。 源家用基站在收到上 述原因值之后， 根据本地判断本地连接是否是唯一连接来判断继续执行 a过 程还是 b过程。
如果源家用基站无法获知哪些承载是本地连接相关的承载， 则上述失败 的原因值需要是不同的取值。 这样， 源家用基站能够根据不同的原因值指示 来判断继续执行 a过程还是 b过程。
Element ) 的取值， 也可以通过增加新的 IE来实现。
对于移动管理单元判断是唯一连接的情况， 原因值可以釆用如下方式： 原因值一（ causel )表示目标侧不支持本地业务； 在步骤 604b中， 可以携带 扩展的原因值二， 该原因值二表示目标侧不支持本地业务， 同时还表示本地 连接不是用户唯一连接； 而在步骤 604a中， 可以携带原有的原因值一， 也可 以携带扩展的原因值三， 该原因值三表示目标侧不支持本地业务， 同时还表 示本地连接是用户唯一连接， 等。
不支持的含义包括但不限于： 目标侧网元不支持建立本地连接； 签约或 者配置限定目标侧不能够建立本地连接。
或者， 上述步骤 604a和步骤 604b中的失败原因值为相同取值， 而移动 管理单元在返回的切换准备失败消息中另外增加本地连接是否为用户唯一连 接的指示， 从而源家用基站可以根据该增加指示判断继续执行 a过程还是 b 过程。
中携带本地连接默认承载 /主 PDP上下文标识。
步骤 606b, 本地网关删除本地连接的相关承载都删除， 并通过 SGW向 移动管理单元发送删除会话响应。
步骤 607b, 移动管理单元向源家用基站发送删除承载请求。 如果本地连 接有多个承载， 那么该请求需要能够将这些承载都删除。 此时源家用基站可 以发送多个删除承载请求， 或者在一条消息中同时删除这些承载。
步骤 608b, 源家用基站向移动管理单元返回删除承载响应。
步骤 609b, 源家用基站根据步骤 604b中的原因值和 /或不是唯一连接的 指示信息，暂不重新发起 HO流程。直到在步骤 607b删除承载之后再发起到 目标基站的切换流程。
步骤 610b, 执行切换的后续过程， 后续过程与现有技术类似， 这里不做 赘述。
实施例三
本实施例适用于用户从源家用基站建立的本地连接， 后续由于位置发生 了变化， 移动到了其他的基站或者家用基站。
本实施例适用于终端从 GERAN/UTRAN/EUTRAN接入 EPC 网络或者 GPRS网关。 如果 UE从 GERAN/UTRAN接入， 家用基站为 HNB, 基站为 BSS或者 NodeB/RNC,移动管理单元为 SGSN。如果 UE从 EUTRAN接入， 家用基站为 HeNB, 基站为 eNB, 移动管理单元为 MME。 如果对于 SGSN 通过 Gn/Gp接口连接本地网关的架构 ,则本流程中没有 SGW,所有经过 SGW 的消息都不需要经过 SGW, 而是移动管理单元直接发送给本地网关。对于家 用基站的场景， 网络中可能存在家用基站网关， 如果存在家用基站网关， 那 么所有家用基站和移动管理单元之间的消息都需要经过家用基站网关。 进一 步的家用基站和本地网关之间的消息， 可以通过家用基站网关也可以不通过 家用基站网关。 对于通过家用基站网关转发消息的场景， 家用基站网关对经 过的消息进行透传， 透传的过程与本发明无关， 这里不做赞述。
本实施例适用于家用基站与本地网关有控制面信令的情况。如图 7所示， 本实施例流程主要包括如下步骤：
步骤 701 , UE位置发生变化， 源家用基站检测到达切换门限， 则向 UE 获取临近区域的无线测量报告。 源家用基站根据 UE上报的无线测量报告选 择目标基站， 并向移动管理单元发送切换请求。
步骤 702,移动管理单元判断用户是否有本地业务。如果没有本地业务， 则应用现有技术， 不在本发明的考虑范围内。 如果 UE建立本地业务， 并且 本地业务是用户的唯一承载。 则需要根据签约数据判断目标基站的信息是否 可以建立该本地连接。 目标基站的信息包含但不限于以下之一： 目标基站的 CSG信息， 目标基站接入模式信息， 目标基站的基站标识， 目标小区的小区 标识。 签约信息包含允许用户建了本地业务的 APN和 CSG的匹配关系。
步骤 703 , 如果根据步骤 702的判断， 允许在目标小区建立本地连接， 则执行切换的后续过程， 后续过程与现有技术类似， 这里不做赘述。
步骤 703a,如果根据步骤 702的判断，不允许在目标小区建立本地连接， 则还需要进一步判断本地连接是否为 UE的唯一 PDN连接。 如果是， 则执行 步骤 704a~706a。
步骤 704a, 移动管理单元向源家用基站返回切换准备失败消息， 其中携 带失败指示， 指示失败原因为目标侧不支持本地业务。 该指示可以通过扩展 现有的原因值 IE ( Information Element ) 的取值 , 或者增加新的 IE来实现。
不支持的含义包括但不限于： 目标侧网元不支持建立本地连接； 签约或 者配置限定目标侧不能够建立本地连接。
步骤 705a,源家用基站根据指示信息，为 UE选择其他可以切换的小区， 并且重新发起切换请求给移动管理单元， 从步骤 701开始执行。 并且将切换 失败的小区标识为该 UE不能切换的小区。
步骤 706a, 如果源家用基站发现没有其他可用的可以切换的小区， 则终 止切换尝试。 在无线信号到达门限值之后发起无线承载的释放。 步骤 703b,如果根据步骤 702的判断，不允许在目标小区建立本地连接， 则还需要进一步判断本地连接是否为 UE的唯一 PDN连接。 如果否， 则执行 步骤 704b~711b。
步骤 704b, 移动管理单元向源家用基站返回切换准备失败消息， 其中携 带失败指示， 指示失败原因为目标侧不支持本地业务。 该指示可以通过扩展 现有的原因值 IE ( Information Element ) 的取值 , 或者增加新的 IE来实现。
其中， 上述步骤 704a和步骤 704b中的失败原因值可以是相同取值， 或 者是不同取值。
其中， 如果源家用基站在建立本地连接的时候， 已经获知哪些承载是本 地连接相关的承载， 那么失败的原因值是可以相同的。 源家用基站在收到上 述原因值之后， 根据本地判断本地连接是否是唯一连接来判断继续执行 a过 程还是 b过程。
如果源家用基站无法获知哪些承载是本地连接相关的承载， 则上述失败 的原因值需要是不同的取值。 这样， 源家用基站能够根据不同的原因值指示 来判断继续执行 a过程还是 b过程。
Element ) 的取值， 也可以通过增加新的 IE来实现。
对于移动管理单元判断是唯一连接的情况， 原因值可以釆用如下方式： 原因值一（ causel )表示目标侧不支持本地业务； 在步骤 704b中， 可以携带 扩展的原因值二， 该原因值二表示目标侧不支持本地业务， 同时还表示本地 连接不是用户唯一连接； 而在步骤 704a中， 可以携带原有的原因值一， 也可 以携带扩展的原因值三， 该原因值三表示目标侧不支持本地业务， 同时还表 示本地连接是用户唯一连接， 等。
不支持的含义包括但不限于： 目标侧网元不支持建立本地连接； 签约或 者配置限定目标侧不能够建立本地连接。
或者， 上述步骤 704a和步骤 704b中的失败原因值为相同取值， 而移动 管理单元在返回的切换准备失败消息中另外增加本地连接是否为用户唯一连 接的指示， 从而源家用基站可以根据该增加指示判断继续执行 a过程还是 b 过程。
步骤 705b , 源家用基站根据切换准备失败消息中的原因值和 /或步骤 704b中的不是唯一连接的指示信息， 主动发起删除本地连接的承载请求， 将 UE的本地连接释放。
步骤 706b, 源家用基站向本地网关发送删除承载请求。 该请求用于请求 本地网关删除本地连接， 但是本消息的名称不限定于此。 如果本地连接有多 个承载， 那么该请求需要能够将这些承载都删除。 此时源家用基站可以发送 多个删除承载请求， 或者在一条消息中同时删除这些承载。 该请求中携带本 地 7?ι载标识。
步骤 707b, 本地网关根据源家用基站的请求删除本地连接的相关承载， 并通过 SGW向移动管理单元发送删除承载请求， 其中携带本地连接默认承 载 /主 PDP上下文标识。
步骤 708b, 移动管理单元和 SGW删除本地连接的相关承载。 移动管理 单元通过 SGW向本地网关发送删除承载响应。
步骤 709b, 本地网关向源家用基站发送删除承载请求。 如果本地连接有 多个承载， 那么该请求需要能够将这些承载都删除。 此时源家用基站可以发 送多个删除承载请求， 或者在一条消息中同时删除这些承载。
710b, 源家用基站根据步骤 704b中的原因值和 /或不是唯一连接的指示 信息， 暂不重新发起 HO流程。直到在步骤 709b删除承载之后再发起到目标 基站的切换流程。
步骤 711b, 执行切换的后续过程， 后续过程与现有技术类似， 这里不做 赘述。
此外， 上述实施例中， 移动管理单元进一步判断本地连接是否为用户唯 一连接，并通过不同的原因值和 /或额外的指示信息通知源家用基站本地连接 是否为用户的唯一连接。 在本发明其他实施例中， 移动管理单元也可以不做 本地连接是否为用户唯一连接的判断， 或者， 仅判断但不会通知给源家用基 站， 而是由源家用基站自己在本地进行判断。 此外， 上述实施例中， 是由移动管理单元在判断本地连接不是用户唯一 连接时， 发起删除本地连接的相关承载； 或者， 源家用基站根据切换准备失 败消息中的原因值和 /或额外的指示信息判断本地连接不是用户唯一连接时， 发起删除本地连接的相关承载。 在本发明其他实施例中， 也可以是源家用基 站在本地判断本地连接不是用户唯一连接时，发起删除本地连接的相关承载。
此外， 本发明实施例中还提供了一种本地访问业务的切换系统， 该系统 主要包括核心网移动管理单元中的业务连续性判定模块和切换处理模块， 其 中：
所述业务连续性判定模块设置成： 收到用户建立本地业务的源家用基站 发送的切换请求后， 判定是否允许在目标基站建立本地业务；
所述切换处理模块设置成： 如果判定不允许在目标基站建立本地业务， 则向所述源家用基站返回切换准备失败消息， 并在所述切换准备失败消息中 指示失败原因。
其中， 所述切换处理模块还设置成： 如果判定允许在目标基站建立本地 业务， 则向所述源家用基站发送切换命令， 执行所述用户的切换过程。
其中， 所述系统还包括家用基站中的切换执行模块，
所述切换处理模块还设置成：在判定不允许在目标基站建立本地业务后， 返回所述切换准备失败消息之前， 判断所述已建立本地业务是否为所述用户 的唯一连接， 如果是所述用户的唯一连接， 则向所述源家用基站返回所述切 换准备失败消息， 并在所述切换准备失败消息中包含失败原因值一；
所述切换执行模块设置成： 接收所述切换准备失败消息， 并根据其中指 示的所述失败原因， 如果是所述失败原因值一， 则重新向所述移动管理单元 发起到新的目标基站的切换请求。
其中， 所述切换处理模块还设置成： 在判定不允许在目标基站建立本地 业务后， 返回所述切换准备失败消息之前， 判断所述已建立本地业务是否为 所述用户的唯一连接， 如果不是所述用户的唯一连接， 则向所述源家用基站 返回所述切换准备失败消息， 并在所述切换准备失败消息中包含失败原因值 所述切换执行模块设置成： 根据所述切换准备失败消息中指示的所述失 败原因， 如果是所述失败原因值二， 则发起删除所述本地业务的相关承载， 并在确认删除所述本地业务的相关承载之后， 重新向所述移动管理单元发起 到同一目标基站的切换请求。
其中， 所述切换处理模块还设置成： 在判定不允许在目标基站建立本地 业务后， 返回所述切换准备失败消息之前， 判断所述已建立本地业务是否为 所述用户的唯一连接， 如果不是所述用户的唯一连接， 则在发起删除所述本 地业务的相关承载后， 向所述源家用基站返回所述切换准备失败消息， 所述 切换准备失败消息中包含失败原因值二；
所述切换执行模块设置成： 根据所述切换准备失败消息中指示的所述失 败原因， 如果是所述失败原因值二， 则在确认所述本地业务的相关承载删除 后， 重新向所述移动管理单元发起到同一目标基站的切换请求。
其中， 所述系统还包括家用基站中的切换执行模块，
所述切换执行模块设置成： 收到所述切换准备失败消息后， 在本地判断 所述已建立本地业务是否为所述用户的唯一连接， 如果是所述用户的唯一连 接， 则重新向所述移动管理单元发起到新的目标基站的切换请求。
其中， 所述切换执行模块设置成： 收到所述切换准备失败消息后， 在本 地判断所述已建立本地业务是否为所述用户的唯一连接， 如果不是所述用户 的唯一连接， 则在发起删除所述本地业务的相关承载之后， 重新向所述移动 管理单元发起到同一目标基站的切换请求。
其中， 所述切换执行模块设置成： 收到所述切换准备失败消息后， 在本 地判断所述已建立本地业务是否为所述用户的唯一连接， 如果不是所述用户 的唯一连接， 则在确认所述本地业务的相关承载删除之后， 重新向所述移动 管理单元发起到同一目标基站的切换请求。
其中， 所述切换执行模块还设置成： 收到所述切换准备失败消息后， 在 重新向所述移动管理单元发起到新的目标基站的切换请求时， 将所述目标基 站标记为所述用户不能切换的基站。 以上仅为本发明的优选实施案例而已， 并不用于限制本发明， 本发明还 可有其他多种实施例， 在不背离本发明精神及其实质的情况下， 熟悉本领域 的技术人员可根据本发明做出各种相应的改变和变形， 但这些相应的改变和 变形都应属于本发明所附的权利要求的保护范围。
显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 并 且在某些情况下， 可以以不同于此处的顺序执行所示出或描述的步骤， 或者 将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软件 结合。
工业实用 4生
上述技术方案提供了一种对于建立了本地业务的 UE在移动过程中， 本 地业务的切换处理方案， 明确了能否支持本地业务连续性的判定方法， 从而 可以为符合特定条件的终端提供本地业务的连续性， 提高这部分用户的业务 体验。 因此本发明具有很强的工业实用性。

Claims

权 利 要 求 书
1、一种本地访问业务的切换方法， 所述切换方法包括： 用户通过源家用 基站建立本地业务后， 发生切换时， 执行以下步骤：
所述源家用基站选择切换的目标基站， 向核心网的移动管理单元发送切 换请求；
所述移动管理单元收到所述切换请求后， 如果判定不允许在目标基站建 立本地业务， 则向所述源家用基站返回切换准备失败消息， 并在所述切换准 备失败消息中指示失败原因。
2、 如权利要求 1所述的切换方法， 所述切换方法还包括：
所述移动管理单元收到所述切换请求后， 如果判定允许在目标基站建立 本地业务， 则向所述源家用基站发送切换命令， 执行所述用户的切换过程。
3、 如权利要求 1所述的切换方法， 所述切换方法还包括：
所述移动管理单元在判定不允许在目标基站建立本地业务后， 返回所述 切换准备失败消息之前， 判断已建立本地业务是否为所述用户的唯一连接， 如果是所述用户的唯一连接， 则向所述源家用基站返回所述切换准备失败消 息， 并在所述切换准备失败消息中包含失败原因值一；
所述源家用基站判断所述切换准备失败消息中指示的失败原因， 如果是 所述失败原因值一， 则重新向所述移动管理单元发起到新的目标基站的切换 请求；
其中， 所述失败原因值一表示目标侧不支持本地业务。
4、 如权利要求 1所述的切换方法， 所述切换方法还包括：
所述移动管理单元在判定不允许在目标基站建立本地业务后， 返回所述 切换准备失败消息之前， 判断已建立本地业务是否为所述用户的唯一连接， 如果不是所述用户的唯一连接， 则向所述源家用基站返回所述切换准备失败 消息， 并在所述切换准备失败消息中包含失败原因值二；
所述源家用基站判断所述切换准备失败消息中指示的失败原因， 如果是 所述失败原因值二， 则发起删除所述本地业务的相关承载， 并在确认删除所 述本地业务的相关承载之后， 重新向所述移动管理单元发起到同一目标基站 的切换请求；
其中， 所述失败原因值二表示目标侧不支持本地业务， 同时还表示本地 连接不是用户唯一连接。
5、 如权利要求 1所述的切换方法， 所述切换方法还包括：
所述移动管理单元在判定不允许在目标基站建立本地业务后， 返回所述 切换准备失败消息之前， 判断已建立本地业务是否为所述用户的唯一连接， 如果不是所述用户的唯一连接， 则在发起删除所述本地业务的相关承载后， 向所述源家用基站返回所述切换准备失败消息， 所述切换准备失败消息中包 含失败原因值二；
所述源家用基站判断所述切换准备失败消息中指示的失败原因， 如果是 所述失败原因值二， 则在确认所述本地业务的相关承载删除后， 重新向所述 移动管理单元发起到同一目标基站的切换请求；
其中， 所述失败原因值二表示目标侧不支持本地业务， 同时还表示本地 连接不是用户唯一连接。
6、 如权利要求 1所述的切换方法， 所述切换方法还包括：
所述源家用基站收到所述切换准备失败消息后， 在本地判断已建立本地 业务是否为所述用户的唯一连接， 如果是所述用户的唯一连接， 则重新向所 述移动管理单元发起到新的目标基站的切换请求。
7、 如权利要求 1所述的切换方法， 所述切换方法还包括：
所述源家用基站收到所述切换准备失败消息后， 在本地判断已建立本地 业务是否为所述用户的唯一连接， 如果不是所述用户的唯一连接， 则在发起 删除所述本地业务的相关承载之后， 重新向所述移动管理单元发起到同一目 标基站的切换请求。
8、 如权利要求 1或 5所述的切换方法， 所述切换方法还包括： 所述源家用基站收到所述切换准备失败消息后， 在本地判断已建立本地 业务是否为所述用户的唯一连接， 如果不是所述用户的唯一连接， 则在确认 所述本地业务的相关承载删除之后， 重新向所述移动管理单元发起到同一目 标基站的切换请求。
9、 如权利要求 3或 6所述的切换方法， 所述切换方法还包括： 所述源家用基站收到所述切换准备失败消息后， 在重新向所述移动管理 单元发起到新的目标基站的切换请求时， 将所述目标基站标记为所述用户不 能切换的基站。
10、 如权利要求 5所述的切换方法， 其中， 所述移动管理单元发起删除 所述本地业务的相关承载的步骤包括：
所述移动管理单元通过核心网接入网关向本地网关发送删除会话请求， 携带本地连接上下文标识；
所述本地网关将所述本地连接的相关承载删除后， 通过所述核心网接入 网关向所述移动管理单元发送删除会话响应， 同时向所述源家用基站发送删 除承载请求；
所述源家用基站将所述本地连接的承载都删除后， 向所述本地网关返回 删除承载响应。
11、 如权利要求 5所述的切换方法， 其中， 所述移动管理单元发起删除 所述本地业务的相关承载的步骤包括：
所述移动管理单元通过核心网接入网关向本地网关发送删除会话请求， 携带本地连接上下文标识；
所述本地网关将所述本地连接的相关承载删除后， 通过所述核心网接入 网关向所述移动管理单元发送删除会话响应；
所述移动管理单元收到所述删除会话响应后， 向所述源家用基站发送删 除承载请求；
所述源家用基站将所述本地连接的承载都删除后， 向所述移动管理单元 返回删除承载响应。
12、 如权利要求 4或 7所述的切换方法， 其中， 所述源家用基站发起删 除所述本地业务的相关承载的步骤包括：
所述源家用基站向本地网关发送删除承载请求， 请求删除本地连接的相 关承载；
所述本地网关将本地连接的相关承载都删除后， 通过核心网接入网关向 所述移动管理单元发送删除承载请求， 携带本地连接的上下文标识；
所述移动管理单元及所述核心网接入网关删除本地连接的相关承载后， 所述移动管理单元通过所述核心网接入网关向本地网关发送删除承载响应。
13、 一种本地访问业务的切换系统， 所述切换系统包括核心网移动管理 单元中的业务连续性判定模块和切换处理模块， 其中：
所述业务连续性判定模块设置成： 收到用户建立本地业务的源家用基站 发送的切换请求后， 判定是否允许在目标基站建立本地业务；
所述切换处理模块设置成： 确定用户已建立本地业务后， 如果判定不允 许在目标基站建立本地业务， 则向所述源家用基站返回切换准备失败消息， 并在所述切换准备失败消息中指示失败原因。
14、 如权利要求 13所述的切换系统， 其中，
所述切换处理模块还设置成： 确定用户已建立本地业务后， 如果判定允 许在目标基站建立本地业务， 则向所述源家用基站发送切换命令， 执行所述 用户的切换过程。
15、如权利要求 13所述的切换系统，所述切换系统还包括家用基站中的 切换执行模块， 其中：
所述切换处理模块还设置成：在判定不允许在目标基站建立本地业务后， 返回所述切换准备失败消息之前， 判断已建立本地业务是否为所述用户的唯 一连接， 如果是所述用户的唯一连接， 则向所述源家用基站返回所述切换准 备失败消息， 并在所述切换准备失败消息中包含失败原因值一；
所述切换执行模块设置成： 接收所述切换准备失败消息， 并判断其中指 示的失败原因， 如果是所述失败原因值一， 则重新向所述移动管理单元发起 到新的目标基站的切换请求；
其中， 所述失败原因值一表示目标侧不支持本地业务。
16、如权利要求 13所述的切换系统，所述切换系统还包括家用基站中的 切换执行模块， 其中： 所述切换处理模块还设置成：在判定不允许在目标基站建立本地业务后， 返回所述切换准备失败消息之前， 还判断已建立本地业务是否为所述用户的 唯一连接， 如果不是所述用户的唯一连接， 则向所述源家用基站返回所述切 换准备失败消息， 并在所述切换准备失败消息中包含失败原因值二；
所述切换执行模块设置成： 判断所述切换准备失败消息中指示的失败原 因， 如果是所述失败原因值二， 则发起删除所述本地业务的相关承载， 并在 确认删除所述本地业务的相关承载之后， 重新向所述移动管理单元发起到同 一目标基站的切换请求；
其中， 所述失败原因值二表示目标侧不支持本地业务， 同时还表示本地 连接不是用户唯一连接。
17、如权利要求 13所述的切换系统，所述切换系统还包括家用基站中的 切换执行模块， 其中：
所述切换处理模块还设置成：在判定不允许在目标基站建立本地业务后， 返回所述切换准备失败消息之前， 还判断已建立本地业务是否为所述用户的 唯一连接， 如果不是所述用户的唯一连接， 则在发起删除所述本地业务的相 关承载后， 向所述源家用基站返回所述切换准备失败消息， 所述切换准备失 败消息中包含失败原因值二；
所述切换执行模块设置成： 判断所述切换准备失败消息中指示的失败原 因， 如果是所述失败原因值二， 则在确认所述本地业务的相关承载删除后， 重新向所述移动管理单元发起到同一目标基站的切换请求；
其中， 所述失败原因值二表示目标侧不支持本地业务， 同时还表示本地 连接不是用户唯一连接。
18、如权利要求 13所述的切换系统，所述切换系统还包括家用基站中的 切换执行模块， 其中：
所述切换执行模块设置成： 收到所述切换准备失败消息后， 在本地判断 所述已建立本地业务是否为所述用户的唯一连接， 如果是所述用户的唯一连 接， 则重新向所述移动管理单元发起到新的目标基站的切换请求。
19、如权利要求 13所述的切换系统，所述切换系统还包括家用基站中的 切换执行模块， 其中：
所述切换执行模块设置成： 收到所述切换准备失败消息后， 在本地判断 所述已建立本地业务是否为所述用户的唯一连接， 如果不是所述用户的唯一 连接， 则在发起删除所述本地业务的相关承载之后， 重新向所述移动管理单 元发起到同一目标基站的切换请求。
20、 如权利要求 13或 17或所述的切换系统， 所述切换系统还包括家用 基站中的切换执行模块， 其中：
所述切换执行模块设置成： 收到所述切换准备失败消息后， 在本地判断 所述已建立本地业务是否为所述用户的唯一连接， 如果不是所述用户的唯一 连接， 则在确认所述本地业务的相关承载删除之后， 重新向所述移动管理单 元发起到同一目标基站的切换请求。
21、 如权利要求 15或 18所述的切换系统， 其中，
所述切换执行模块还设置成： 收到所述切换准备失败消息后， 在重新向 所述移动管理单元发起到新的目标基站的切换请求时， 将所述目标基站标记 为所述用户不能切换的基站。
PCT/CN2012/072067 2011-03-24 2012-03-07 一种本地访问业务的切换方法及系统 WO2012126319A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110072290.7 2011-03-24
CN201110072290.7A CN102695222B (zh) 2011-03-24 2011-03-24 一种本地访问业务的切换方法及系统

Publications (1)

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

Family

ID=46860470

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/072067 WO2012126319A1 (zh) 2011-03-24 2012-03-07 一种本地访问业务的切换方法及系统

Country Status (2)

Country Link
CN (1) CN102695222B (zh)
WO (1) WO2012126319A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108924893B (zh) * 2017-04-26 2020-12-25 中国移动通信有限公司研究院 一种承载释放方法、装置、mme及sae-gw
CN108430081A (zh) * 2018-02-28 2018-08-21 北京科技大学 一种网络虚拟化雾无线接入网络中的切换方法
CA3134505A1 (en) * 2019-03-22 2020-10-01 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Wireless communication method, terminal device and network device
CN112770410B (zh) * 2019-11-06 2023-07-25 维沃移动通信有限公司 一种连接失败处理方法、终端和网络设备
CN114401507B (zh) * 2022-01-17 2023-06-16 中国联合网络通信集团有限公司 一种数据传输方法、装置及存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101784086A (zh) * 2009-01-19 2010-07-21 华为技术有限公司 切换控制的实现方法、相关设备及通信系统
CN101801054A (zh) * 2009-02-05 2010-08-11 中兴通讯股份有限公司 向家庭基站小区切换的接入控制方法
CN101883347A (zh) * 2009-05-08 2010-11-10 大唐移动通信设备有限公司 一种家庭网络中的切换控制方法及装置
CN101888596A (zh) * 2009-05-15 2010-11-17 华为技术有限公司 一种接入控制方法及系统
CN101932074A (zh) * 2009-06-25 2010-12-29 华为技术有限公司 一种家庭基站本地ip接入的控制方法及装置
CN102076038A (zh) * 2011-01-17 2011-05-25 大唐移动通信设备有限公司 一种lipa连接切换准备过程的执行方法及装置
CN102076036A (zh) * 2011-01-14 2011-05-25 大唐移动通信设备有限公司 核心网设备和家庭基站及其处理lipa连接的方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101990192A (zh) * 2009-07-30 2011-03-23 中兴通讯股份有限公司 本地ip访问连接属性的通知方法与装置

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101784086A (zh) * 2009-01-19 2010-07-21 华为技术有限公司 切换控制的实现方法、相关设备及通信系统
CN101801054A (zh) * 2009-02-05 2010-08-11 中兴通讯股份有限公司 向家庭基站小区切换的接入控制方法
CN101883347A (zh) * 2009-05-08 2010-11-10 大唐移动通信设备有限公司 一种家庭网络中的切换控制方法及装置
CN101888596A (zh) * 2009-05-15 2010-11-17 华为技术有限公司 一种接入控制方法及系统
CN101932074A (zh) * 2009-06-25 2010-12-29 华为技术有限公司 一种家庭基站本地ip接入的控制方法及装置
CN102076036A (zh) * 2011-01-14 2011-05-25 大唐移动通信设备有限公司 核心网设备和家庭基站及其处理lipa连接的方法
CN102076038A (zh) * 2011-01-17 2011-05-25 大唐移动通信设备有限公司 一种lipa连接切换准备过程的执行方法及装置

Also Published As

Publication number Publication date
CN102695222A (zh) 2012-09-26
CN102695222B (zh) 2017-03-15

Similar Documents

Publication Publication Date Title
US9320075B2 (en) Method, system and transmission distribution network element for indicating data-distribution
US10779357B2 (en) Method for avoiding handover failure
US11129054B2 (en) Methods, systems and devices for supporting local breakout in small cell architecture
US8730831B2 (en) Method and system for acquiring route strategies
WO2010121558A1 (zh) 切换控制方法、装置和系统
US8743752B2 (en) Method and apparatus for status transition
WO2010045854A1 (zh) 接入控制方法、装置和通信系统
WO2011026407A1 (zh) 一种本地网际协议访问连接移动性支持的方法及系统
WO2012041073A1 (zh) 一种实现流迁移的方法及系统
WO2011015124A1 (zh) 实现本地ip访问控制的方法、通知方法及系统
WO2012171451A1 (zh) 信息获取方法、装置及系统
WO2012062183A1 (zh) 一种实现数据流服务质量和计费策略控制的方法及系统
WO2011006404A1 (zh) 本地ip访问连接建立的实现方法及系统
WO2011143997A1 (zh) 一种实现路由选择的方法和装置
US9629179B2 (en) Method and device for processing local access connection
WO2012126319A1 (zh) 一种本地访问业务的切换方法及系统
WO2011076063A1 (zh) Lipa或sipto管理方法、装置和系统
WO2011097989A1 (zh) 一种本地访问寻呼优化方法及装置
WO2011144000A1 (zh) 一种实现路由选择的方法和装置
WO2011157100A1 (zh) 一种数据缓存的方法和系统
WO2012146093A1 (zh) 一种实现业务处理的方法和系统
WO2011003310A1 (zh) 一种核心网进行接入控制判断的方法、装置及系统
WO2011085623A1 (zh) 本地接入网关获取终端的寻呼信息的方法和系统
WO2011035719A1 (zh) 一种释放本地连接的方法及系统
WO2011032522A1 (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: 12760853

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

Country of ref document: EP

Kind code of ref document: A1