WO2015184722A1 - 专用网络选择方法及装置 - Google Patents

专用网络选择方法及装置 Download PDF

Info

Publication number
WO2015184722A1
WO2015184722A1 PCT/CN2014/089035 CN2014089035W WO2015184722A1 WO 2015184722 A1 WO2015184722 A1 WO 2015184722A1 CN 2014089035 W CN2014089035 W CN 2014089035W WO 2015184722 A1 WO2015184722 A1 WO 2015184722A1
Authority
WO
WIPO (PCT)
Prior art keywords
sgw
pgw
terminal
private network
management entity
Prior art date
Application number
PCT/CN2014/089035
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 中兴通讯股份有限公司
Priority to US15/316,148 priority Critical patent/US20170127324A1/en
Priority to EP14894150.3A priority patent/EP3154294A4/en
Publication of WO2015184722A1 publication Critical patent/WO2015184722A1/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/0085—Hand-off measurements
    • H04W36/0094—Definition of hand-off measurement parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • 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 private network selection method and apparatus.
  • the 3GPP (3rd Generation Partnership Project) standard working group is working on the research of EPS (Evolved Packet System).
  • the entire EPS system mainly includes an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and an EPC (Evolved Packet Core).
  • the system's EPC can support users' access from GERAN (GSM EDGE radio access network) and UTRAN (Universal Terrestrial Radio Access Network).
  • the EPC packet core network includes an HSS (Home Subscriber Server), an MME (Mobility Management Entity), an S-GW (Serving Gateway), and a P-GW (PDN Gateway). , Packet Data Network Gateway, SGSN (Serving GPRS Support Node), and PCRF (Policy and Charging Enforcement Function).
  • HSS Home Subscriber Server
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • SGSN Serving GPRS Support Node
  • PCRF Policy and Charging Enforcement Function
  • the HSS is a permanent storage location for user subscription data, and is located in the home network to which the user subscribes.
  • the MME is the storage location of the user subscription data in the current network, and is responsible for the terminal-to-network NAS layer (Non-Access Stratum) signaling management, the user idle mode tracking and paging management function, and bearer management.
  • the S-GW is a gateway from the core network to the wireless system, and is responsible for the user plane bearer of the terminal to the core network, the data buffer in the terminal idle mode, the function of initiating a service request by the network side, the lawful eavesdropping, and the packet data routing and forwarding function.
  • the P-GW is an evolved packet domain system (EPS) and a gateway of the external network of the system, and is responsible for functions such as IP address allocation, charging function, packet filtering, and policy application of the terminal.
  • EPS evolved packet domain system
  • the SGSN is a service support point for GERAN and UTRAN users to access the EPC network. It functions similarly to the MME and is responsible for user location update, paging management, and bearer management.
  • the PCRF is responsible for providing policy control and charging rules to the PCEF.
  • 3GPP networks begin to support devices with special features, such as sensor devices, data cards, etc. Due to their different characteristics, these different types of devices and users may use the network when they use the network. The situation is different. Therefore, operators need to provide different networks for these different characteristics of devices and users from the perspective of operation, and these networks may have characteristics different from ordinary user access. Call it a private network. Considering compatibility issues, some devices may not be able to notify their device type, so the network may only be able to select a private network for the terminal based on the user's subscription information. However, the user's subscription data can only obtain the user's subscription data after the user has accessed the network. Therefore, when the user accesses the non-dedicated network, the non-dedicated network is required to provide a method for reselecting the user to the private network.
  • the method mainly includes the following steps 201-213.
  • Steps 201 to 202 The terminal initiates an attach request, where the terminal carries the real identifier or the temporary identifier.
  • the base station may route the request to the MME of a non-dedicated network.
  • Steps 203-204 after completing the authorization and authentication process for the terminal, the MME initiates a location update request to the HSS. After receiving the HSS, the user data is inserted into the MME, where the user subscription type information is carried.
  • Step 205 The MME determines, according to the subscription data and the local configuration, that the private network needs to be re-selected for the user, and therefore allocates a fake temporary identifier and a non-broadcast tracking area identifier to the terminal.
  • the temporary identifier includes two parts: a GUMMEI (Globally Unique MME Identifier) and an M-TMSI (M-Temporary Mobile Station Identifier MME assigned temporary terminal identifier), where the GUMMEI points to the private network instead of assigning the identifier. MME.
  • GUMMEI Globally Unique MME Identifier
  • M-TMSI M-Temporary Mobile Station Identifier MME assigned temporary terminal identifier
  • Step 206 The MME sends a create session request to the SGW/PGW, and the SGW/PGW returns a create session response to the MME after the session is successfully established.
  • Step 207 The MME sends the allocated temporary identifier and the non-broadcast tracking area identifier to the terminal by using an attach accept message. After receiving the terminal and completing the radio bearer setup process, the terminal sends an attach complete message to the network.
  • Step 208 The terminal sends a tracking area update request to carry the GUTI according to the received non-broadcast tracking area identifier, and the message sent to the base station carries the GUMMEI information in the fake GUTI.
  • Steps 209-210 the base station selects the MME of the private network for the terminal according to the GUMMEI information.
  • the tracking area update request is forwarded to the MME of the private network.
  • Steps 211 to 212 The MME of the private network receives the request, and according to the GUTI included therein, determines that the user has previously registered to the non-dedicated network, and therefore rejects the current access, and includes the reason for the rejection as implicit separation.
  • Step 213 The terminal re-initiates an attach request, where the fake GUTI is carried out to re-execute the attach procedure in the prior art.
  • the base station can select a private network according to the GUMMEI information therein. in this process, After the MME in the private network is selected, the MME of the private network selects the SGW and the PGW of the private network for the terminal according to the local configuration.
  • the present invention provides a method and apparatus for selecting a dedicated network to solve at least the above problems in view of the problem that the related art may not be able to select a dedicated network after the terminal location changes.
  • a private network selection method including: a mobility management entity acquires user subscription data of a terminal when receiving a location update request; and the mobility management entity subscribes data according to the user Determining that a dedicated network needs to be selected for the terminal; the mobility management entity determines whether the serving gateway SGW and the packet data network gateway PGW that the terminal is using belong to a private network; if the SGW and/or PGW in use are not Depending on the private network, the mobility management entity selects the SGW and/or PGW of the private network for the terminal and switches the SGW and/or PGW used by the terminal to the selected SGW and/or PGW.
  • the mobility management entity determines whether the serving gateway SGW and the packet data network gateway PGW that the terminal is using belong to a private network, and includes: the mobility management entity according to a locally configured private network SGW and PGW Address information, determining whether the SGW and the PGW that the terminal is using belong to the private network; or the mobility management entity acquires the full name domain name FQDN of the SGW and the PGW that the terminal is using by using the context or the domain name system DNS. It is judged whether the SGW and the PGW that the terminal is using belong to the private network according to the attributes of the FGW of the SGW and the PGW of the private network set in advance.
  • the mobility management entity selects, for the terminal, the SGW and/or the PGW of the private network, where the mobility management entity selects the terminal used by the SGW and the PGW of the locally configured private network.
  • SGW and/or PGW; or, the mobility management entity queries the DNS for the FQDN of the SGW and/or the PGW, and selects one from the list returned by the DNS according to the attributes of the SGW of the private network and/or the FQDN of the PGW set in advance.
  • SGW/ or PGW of the private network is mapped to the mobility management entity.
  • the mobility management entity switches the SGW and/or PGW used by the terminal to the selected SGW and/or PGW, including: if the SGW being used does not belong to a private network, the The used PGW belongs to a private network, and the mobility management entity switches the SGW used by the terminal to the selected SGW; if the SGW being used belongs to a private network, the used PGW does not belong to a private network.
  • the mobility management entity switches the PGW used by the terminal to the selected PGW; if the SGW being used does not belong to a private network, and the PGW being used does not belong to a private network, the mobile The sex management entity switches the SGW used by the terminal to the selected SGW, and then switches the PGW used by the terminal to the selected PGW.
  • the mobility management entity switches the SGW used by the terminal to the selected SGW, where the mobility management entity sends a create session request to the selected SGW, requesting the selected SGW.
  • Creating a session for the terminal sending, by the selected SGW, a modify bearer request to the used PGW; the mobility management entity sending a delete session request to the used SGW, requesting to delete the used The session of the terminal on the SGW.
  • the mobility management entity switches the PGW used by the terminal to the selected PGW, including: Step A, the mobility management entity determines whether all the PGWs connected to the terminal do not belong to the private network. If yes, proceed to step B, otherwise, perform step C; step B, the mobility management entity sends a message to the terminal, instructing the terminal to re-initiate the attach request, and through the SGW being used by the terminal Determining that the PGW being used sends a delete session request, requesting to delete the session of the terminal on the PGW being used; Step C, the mobility management entity sends a delete session request to the PGW being used by the SGW of the private network Requesting to delete the session of the terminal on the PGW being used, and then sending a deactivation bearer request to the terminal, instructing the terminal to delete the PDN connection with the related data packet network, and initiating the PDN connection reactivation.
  • the mobility management entity allocates the selected PGW to the terminal during reactivation.
  • a private network selecting apparatus located in a mobility management entity, comprising: an obtaining module, configured to acquire user subscription data of a terminal when receiving a location update request; determining a module, setting Determining, according to the user subscription data, that a dedicated network needs to be selected for the terminal; the determining module is configured to determine whether the serving gateway SGW and the packet data network gateway PGW that the terminal is using belong to a private network, if the used The SGW and/or the PGW do not belong to the private network, and the execution module is triggered; the execution module is configured to select the SGW and/or PGW of the private network for the terminal, and switch the SGW and/or PGW used by the terminal to the selected one.
  • the SGW and/or PGW located in a mobility management entity, comprising: an obtaining module, configured to acquire user subscription data of a terminal when receiving a location update request; determining a module, setting Determining, according to the user subscription data, that a dedicated network needs to be selected for the terminal; the determining
  • the determining module determines, according to one of the following manners, whether the SGW and the PGW that the terminal is using belong to the private network according to the address information of the SGW and the PGW of the locally configured private network. And obtaining the full-name domain name FQDN of the SGW and the PGW that the terminal is using by using the context, or determining the SGW and the PGW that the terminal is using according to the attributes of the SGW of the private network and the FQDN of the PGW. Whether it is a private network.
  • the executing module selects an SGW and/or a PGW of the private network for the terminal by selecting one of the SGW and the PGW of the locally configured private network, and selecting the SGW and/or the PGW used by the terminal. Or, query the DNS for the FQDN of the SGW and/or the PGW, and select an SGW/PGW of a private network from the list returned by the DNS according to the attributes of the SGW of the private network and/or the FQDN of the PGW set in advance.
  • the execution module includes: a first switching module, configured to switch the SGW used by the terminal if the used SGW does not belong to a private network, and the used PGW belongs to a private network. Go to the selected SGW; the second switching module is configured to switch the PGW used by the terminal to the selected one if the SGW being used belongs to a private network, and the PGW being used does not belong to the private network The PGW; the third switching module is configured to switch the SGW used by the terminal to the selected one, if the used SGW does not belong to a private network, and the used PGW does not belong to a private network. The SGW then switches the PGW used by the terminal to the selected PGW.
  • a first switching module configured to switch the SGW used by the terminal if the used SGW does not belong to a private network, and the used PGW belongs to a private network. Go to the selected SGW
  • the second switching module is configured to switch the PGW used by the terminal to the selected one if the SGW being used belongs to a
  • the first switching module includes: a first requesting unit, configured to send a create session request to the selected SGW, requesting the selected SGW to create a session for the terminal, by the selected SGW
  • the PGW in use sends a modify bearer request
  • the second request unit is configured to send a delete session request to the SGW in use, requesting to delete the session of the terminal on the SGW being used.
  • the second switching module includes: a first determining unit, configured to determine whether all the PGWs connected to the terminal do not belong to the private network, and if yes, trigger the first switching unit, otherwise, trigger the second switching a first switching unit, configured to send a message to the terminal, instructing the terminal to re-initiate an attach request, and sending a delete session request to the used PGW by using the SGW being used, requesting to delete the a session of the terminal on the used PGW; the second switching unit is configured to send a delete session request to the PGW being used by the SGW of the private network, requesting to delete the session of the terminal on the PGW being used, and Sending a deactivation bearer request to the terminal, instructing the terminal to delete the PDN connection with the associated data packet network and initiating the PDN connection reactivation, and assigning the selection to the terminal during the reactivation of the terminal PGW.
  • a first determining unit configured to determine whether all the PGWs connected to the terminal do not belong to the private
  • a mobility management entity including the dedicated network selection device described above.
  • the mobility management entity selects the SGW and the PGW of the private network for the terminal when receiving the tracking area update request or the routing area update request of the terminal, and solves the related problem in the related art after the terminal location changes.
  • the problem of the private network may not be selected, and the operation of the terminal may be maintained or re-selected to a dedicated network after the terminal location changes, thereby improving the success rate of the terminal access.
  • FIG. 1 is a schematic diagram of a network architecture of an EPS system
  • FIG. 2 is a flowchart of a method for reselecting a user of an initial access non-dedicated network to a private network according to the related art
  • FIG. 3 is a flow chart of a private network selection method in accordance with an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for an MME to perform a dedicated network selection according to an alternative embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of a dedicated network selection apparatus according to an embodiment of the present invention.
  • FIG. 8 is a signaling flow chart according to Embodiment 3 of the present invention.
  • a private network selection method is provided.
  • FIG. 3 is a flowchart of a method for selecting a private network according to an embodiment of the present invention. As shown in FIG. 3, the method mainly includes the following steps S302 to S308.
  • Step S302 The mobility management entity acquires user subscription data of the terminal when receiving the location update request.
  • the location update request is a Tracking Area Update (TAU) request
  • the mobility management entity is the SGSN
  • the location update request is a routing area update (Route Area) Update, RAU) request.
  • the mobility management entity of the embodiment of the present invention is a mobility management entity of a private network.
  • the terminal may initiate a TAU procedure to the target MME by using the base station, where the terminal may initiate the TAU process in the idle state or after the handover. If the terminal initiates the TAU in the idle state, the MME may receive the TAU request. The context is further retrieved from the source MME and the bearer is updated. If the TAU is initiated after the handover, the delivery of the context has been completed during the handover process, as well as the bearer update.
  • the MME may obtain the user subscription information of the terminal from the location update response returned by the HHE by initiating a location update request to the HSS.
  • Step S304 the mobility management entity determines, according to the user subscription data and the local configuration, that a dedicated network needs to be selected for the terminal.
  • the subscription may indicate that some terminals should be routed to the private network, for example, by adding attribute tags.
  • the mobile management entity receives the subscription data of such users, it may be based on a specific label. Route to a private network.
  • the selection may be assisted according to the local configuration of the mobility management entity.
  • the attribute indicating that the terminal A in the subscription data is 1 may be routed to the private network 1, but the mobility management entity The local configuration does not allow roaming users to use their own private network 1, so that they can select a normal network for the terminal regardless of the subscription settings.
  • Step S306 the mobility management entity determines whether the serving gateway SGW and the packet data network gateway PGW that the terminal is using belong to a private network.
  • the address information of the SGW and the PGW of the private network may be configured in the mobility management entity, and the mobility management entity may determine, according to the address information of the SGW and the PGW of the locally configured private network, that the terminal is in use. Whether the SGW and the PGW belong to the private network; or the mobility management entity may obtain the full-name domain name FQDN of the SGW and the PGW that the terminal is using by using the domain name system DNS, according to the preset SGW of the dedicated network. The attribute of the FQDN of the PGW determines whether the SGW and the PGW that the terminal is using belong to a private network.
  • Step S308 if the SGW and/or PGW in use does not belong to a private network, the mobility management entity selects an SGW and/or a PGW of the private network for the terminal, and uses the SGW and/or used by the terminal. Or the PGW switches to the selected SGW and/or PGW.
  • the SGW and/or the PGW used by the terminal may be selected from the SGW and the PGW of the locally configured private network.
  • query the DNS for the FQDN of the SGW and/or the PGW and select an SGW/PGW of a private network from the list returned by the DNS according to the attributes of the SGW of the private network and/or the FQDN of the PGW set in advance.
  • the mobility management entity switching the SGW and/or PGW used by the terminal to the selected SGW and/or PGW may include: if the being used The SGW does not belong to a private network, and the PGW being used belongs to a private network, and the mobility management entity switches the SGW used by the terminal to the selected SGW; if the SGW being used belongs to a dedicated network, If the PGW being used does not belong to a private network, the mobility management entity switches the PGW used by the terminal to the selected PGW; if the SGW being used does not belong to a private network, the PGW being used Not belonging to the private network, the mobility management entity switches the SGW used by the terminal to the selected SGW, and then switches the PGW used by the terminal to the selected PGW.
  • the mobility management entity when the mobility management entity switches the SGW used by the terminal, the mobility management entity may send a create session request to the selected SGW, and request the selected SGW to create the terminal. a session, the selected SGW sends a modify bearer request to the used PGW; and sends a delete session request to the used SGW to request to delete the session of the terminal on the SGW being used. Thereby, the SGW used by the terminal is switched to the SGW of the private network.
  • the mobility management entity when the PGW used by the terminal is switched to the selected PGW, may include the following steps: Step A, the mobility management entity determines whether the All the PGWs connected to the terminal do not belong to the private network. If yes, step B is performed. Otherwise, step C is performed. In step B, the mobility management entity sends a message to the terminal, instructing the terminal to re-initiate the attach request.
  • step C the mobility management entity passes through a SGW of a private network Sending a delete session request to the PGW in use, requesting to delete the session of the terminal on the PGW being used, and then sending a deactivation bearer request to the terminal, instructing the terminal to delete the associated data packet network PDN Connecting and initiating the PDN connection reactivation, the mobility management entity assigning the terminal to the terminal during the reactivation process Select the PGW.
  • the MME may be all MMEs in the network
  • FIG. 4 is a flowchart executed by the MME in an optional implementation manner of the embodiment of the present invention.
  • the MME after receiving the location update request and the subscription data of the terminal, the MME first determines whether it is necessary to select a dedicated network for the terminal, and if not, performs a normal location update procedure. Otherwise, the MME further determines whether it is itself.
  • the network element of the private network If the MME is not a network element of the private network, the process is performed according to the process shown in FIG. 2, that is, the process after step 205 is performed.
  • the MME determines whether the PGW being used by the terminal is a PGW of the private network. . If the PGW being used is the PGW of the private network, the MME further determines whether the SGW currently used by the terminal belongs to the private network, and if the SGW currently used by the terminal does not belong to the private network, the SGW reselection process is performed; otherwise, the normal location is performed. Update process. If the PGW being used is not the PGW of the private network, the MME further determines that all the PGWs connected by the terminal do not belong to the private network, that is, are not dedicated network nodes.
  • the logout process is initiated, or the location update request is rejected, and the terminal is required to re-register to the network. If the part of the PGW to which the terminal is connected belongs to the private network, it is further determined whether the SGW currently used by the terminal belongs to the private network, and if the SGW currently used by the terminal does not belong to the private network, the SGW reselection process is performed, and then the PGW does not belong to the private network.
  • the related PDN connection initiates bearer deactivation, and the terminal is required to reactivate the relevant PDN connection. If the SGW currently used by the terminal belongs to the private network, the bearer is deactivated directly for the PDN connection that the PGW does not belong to the private network, and the terminal is required to be reactivated.
  • Related PDN connections are provided.
  • the MME of the private network determines whether to select a dedicated SGW/PGW for the terminal according to the user subscription data. If the PGW that the terminal is using is not the PGW of the private network, it is further determined whether all the PGWs are not the private network. PGW. If none of them are, the logout process is initiated, or the location update request is rejected, requiring the terminal to re-register to the network. If not all of the nodes are non-dedicated nodes, it is further determined whether the SGW is a dedicated node.
  • the SGW reselection process is performed first, and then the bearer deactivation is initiated, and the terminal is required to reactivate the related PDN connection. If the SGW being used by the terminal is not the SGW of the private network, the MME performs a process of SGW reselection. With the technical solution provided by the embodiment of the present invention, a private network can be maintained or reselected after the terminal location changes.
  • a dedicated network selection apparatus is further provided, which is located in a mobility management entity, and is used to implement the foregoing dedicated network selection method provided by the implementation of the present invention.
  • FIG. 5 is a schematic structural diagram of a dedicated network selection apparatus according to an embodiment of the present invention.
  • the apparatus mainly includes: an obtaining module 510, configured to acquire user subscription data of a terminal; and a determining module 520, configured to The user subscription data and the local configuration determine that a dedicated network needs to be selected for the terminal; the determining module 530 is configured to determine whether the serving gateway SGW and the packet data network gateway PGW that the terminal is using belong to a private network, if the The SGW and/or the PGW are not part of the private network, and the execution module is triggered;
  • the executing module 540 is configured to select an SGW and/or a PGW of the private network for the terminal, and switch the SGW and/or PGW used by the terminal to the selected SGW and/or PGW.
  • the determining module 530 may determine, according to one of the following manners, whether the SGW and the PGW that the terminal is using belong to the private network according to the address information of the SGW and the PGW of the locally configured private network; Or obtaining the full-name domain name FQDN of the SGW and the PGW that the terminal is using by using the domain name system DNS, and determining whether the SGW and the PGW that the terminal is using belong to the private network according to the attributes of the SGW of the private network and the FQDN of the PGW.
  • the executing module 540 may select, for the terminal, the SGW and/or the PGW of the private network by using one of the following manners: selecting the SGW and/or used by the terminal from the SGW and the PGW of the locally configured private network. Or PGW; or, query the DNS for the FQDN of the SGW and/or the PGW, and select a SGW/PGW of the private network from the list returned by the DNS according to the attributes of the SGW of the private network and/or the FQDN of the PGW.
  • the executing module 540 may include: a first switching module, configured to use the terminal when the used SGW does not belong to a private network, where the used PGW belongs to a private network.
  • the SGW switches to the selected SGW;
  • the second switching module is configured to switch the PGW used by the terminal to the case where the SGW being used belongs to a private network, and the PGW being used does not belong to the private network.
  • the third switching module is configured to switch the SGW used by the terminal to the selected one if the used SGW does not belong to the private network, and the used PGW does not belong to the private network.
  • the SGW then switches the PGW used by the terminal to the selected PGW.
  • the first switching module may include: a first requesting unit, configured to send a create session request to the selected SGW, requesting the selected SGW to create a session for the terminal, by the selected SGW Transmitting a modify bearer request to the PGW being used; the second requesting unit is configured to send a delete session request to the SGW in use, requesting to delete a session of the terminal on the SGW being used.
  • the second switching module may include: a first determining unit, configured to determine whether all the PGWs connected to the terminal do not belong to the private network, and if yes, trigger the first switching unit, otherwise, trigger the second a switching unit, configured to send a message to the terminal, instructing the terminal to re-initiate an attach request, and sending a delete session request to the used PGW by using the SGW being used, requesting to delete the The session of the terminal on the PGW being used; the second switching unit is configured to send a delete session request to the PGW being used by the SGW of the private network, requesting to delete the session of the terminal on the PGW being used, And sending a deactivation bearer request to the terminal, instructing the terminal to delete the phase
  • the closed data packet network PDN connects and initiates the PDN connection reactivation, and assigns the selected PGW to the terminal during the terminal reactivation.
  • a mobility management entity including the above-mentioned dedicated network selection device.
  • the source network does not support a dedicated network
  • the MME/SGSN in the target network is a network element in the private network
  • the SGW is not a network element in the private network.
  • the terminal may initiate the TAU/RAU process in an idle state, or may be a TAU/RAU process that occurs after the handover (HO).
  • TAU is taken as an example, and RAU is similar.
  • FIG. 6 is a signaling flowchart of performing dedicated network selection in a TAU process according to the embodiment. As shown in FIG. 6, the method mainly includes the following steps:
  • the target MME initiates a location update request to the HSS.
  • the location cancellation request is sent to the source MME/SGSN, and the source MME/SGSN returns a location cancellation response to the HSS.
  • the HSS inserts user data into the target MME through the location update response, which carries the user subscription type information.
  • the MME does not belong to the dedicated network node, the MME does not need to perform the subsequent steps, and directly executes the related procedure after step 205 in the prior art.
  • the target MME obtains the SGW address information of the private network according to the local configuration information and/or the DNS query.
  • All dedicated MMEs configure the SGW and PGW address information of the private network. Therefore, the MME can determine whether the SGW/PGW is a dedicated node according to the local configuration, or select a dedicated SGW/PGW.
  • the SGW/PGW uses different FQDNs, such as special tags.
  • the MME obtains the corresponding FQDN through the context or DNS query to determine whether the SGW/PGW is a dedicated node or selects from the list returned by the DNS.
  • a dedicated SGW/PGW is a dedicated node or selects from the list returned by the DNS.
  • Step 606 to step 609 the target MME sends a create session request to the SGW, and the SGW sends a modify bearer request to the PGW.
  • the PGW sends a modify bearer response to the SGW, and the SGW returns a create session response to the MME.
  • Step 610 The target MME sends a delete session request to the SGW of the non-dedicated node, and deletes the corresponding resource. After the deletion succeeds, the SGW sends a delete session response to the MME.
  • Step 611 If the TAU is initiated after the handover, or the radio bearer is established after the TAU, the eNB needs to be notified after the reselection, that is, the step is performed.
  • the target MME sends the re-selected dedicated SGW-assigned address and tunnel end identifier to the eNB.
  • Steps 612-613 the target MME sends a TAU accept message to the terminal, and the terminal saves the temporary identifier and other related information allocated by the network, and sends a TAU complete message to the MME.
  • the source network does not support a dedicated network
  • the MME/SGSN in the target network is a network element in the private network
  • the PGW is not a network element in the private network.
  • the process can be either an idle state initiated TAU/RAU process or a TAU/RAU process occurring after the HO.
  • the TAU is taken as an example, and the RAU is similar.
  • FIG. 7 is a signaling flowchart of a private network selection in the embodiment. As shown in FIG. 7, the method mainly includes the following steps:
  • the target MME initiates a location update request to the HSS.
  • the location cancellation request is sent to the source MME/SGSN, and the source MME/SGSN returns a location cancellation response to the HSS.
  • the HSS inserts user data into the target MME through the location update response, which carries the user subscription type information.
  • Step 705 The target MME determines, according to the subscription data and the local configuration, that the private network needs to be re-selected for the user, and is a dedicated network node.
  • the target MME determines, according to the local configuration, that the SGW connected to the terminal is a dedicated network node, and the PGW does not belong to the dedicated network node.
  • the steps 606-613 in the embodiment FIG. 6 are performed first. After the execution, the SGW belongs to the dedicated network node, and the relevant steps in the embodiment are performed.
  • the target MME obtains PGW address information of the private network according to local configuration information and/or DNS query.
  • the manner in which the MME selects or configures a dedicated SGW/PGW may be:
  • All dedicated MMEs configure the SGW and PGW address information of the private network. Therefore, the MME can determine whether the SGW/PGW is a dedicated node according to the local configuration, or select a dedicated SGW/PGW.
  • the SGW/PGW uses different FQDNs, such as special tags.
  • the MME obtains the corresponding FQDN through the context or DNS query to determine whether the SGW/PGW is a dedicated node or selects from the list returned by the DNS.
  • a dedicated SGW/PGW is a dedicated node or selects from the list returned by the DNS.
  • Steps 706-707 The target MME sends a TAU accept message to the terminal. After receiving the temporary identifier and other related information allocated by the network, the terminal sends a TAU complete message to the MME.
  • the target MME initiates steps 708-710 after the UE enters the idle state. If the radio bearer is not established in the previous process, steps 708-710 can be performed immediately.
  • Step 708 The target MME sends a delete session request to the PGW through the SGW. After deleting the session, the PGW returns a delete session response to the MME through the SGW.
  • Steps 709-710 The target MME initiates a deactivation bearer request to the terminal, where the default bearer identifier of the relevant PDN connection is carried, and the reason for the deactivation is "reactivation".
  • the terminal deletes the relevant PDN connection and returns a deactivated bearer response to the MME.
  • the target MME selects the PGW of the private network for the terminal, and the selection scheme is as described in step 705.
  • the source network does not support a dedicated network
  • the MME/SGSN in the target network is a network element in the private network
  • the PGW is not a network element in the private network.
  • it is assumed that all PGWs connected by the terminal are not dedicated network nodes.
  • the MME supports private network selection, but is not a dedicated network node. In this case, steps 506a-510a are recommended.
  • the process can be either an idle state initiated TAU/RAU process or a TAU/RAU process occurring after the HO.
  • TAU is taken as an example, and RAU is similar.
  • FIG. 8 is a signaling flowchart of a private network selection in the embodiment. As shown in FIG. 8 , the method mainly includes the following steps:
  • Steps 801 to 805 are similar to steps 701 to 705, and are not described herein.
  • Steps 806a-810a and steps 806b-807b only need to perform one of them.
  • steps 806a-810a or steps 806b-807b may be performed immediately.
  • Step 806a to step 807a the target MME sends a TAU accept message to the terminal, and the terminal saves the temporary identifier and other related information allocated by the network, and sends a TAU complete message to the MME.
  • Step 808a The target MME sends a logout request to the terminal, where the carrying indication requires the terminal to re-initiate the attach procedure.
  • step 809a the target MME sends a delete session request to the PGW through the SGW. After deleting the session, the PGW returns a delete session response to the MME through the SGW.
  • step 810a the terminal returns a logout completion message to the target MME, and re-initiates the attach request, where the temporary identifier obtained by the network is obtained in step 806a.
  • the base station can select the target MME according to the GUMMEI information therein.
  • step 807b the target MME sends a delete session request to the PGW through the SGW. After deleting the session, the PGW returns a delete session response to the MME through the SGW.
  • the present invention achieves the following technical effects: when receiving the tracking area update request or the routing area update request of the terminal, the mobility management entity selects the SGW and the PGW of the private network for the terminal, and solves the problem.
  • the problem of the private network may not be selected, thereby ensuring that the terminal location is changed, and then maintaining or reselecting to a dedicated network, thereby improving the success rate of the terminal access.
  • 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 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 thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the mobility management entity when receiving the tracking area update request or the routing area update request of the terminal, selects the SGW and the PGW of the dedicated network for the terminal, and solves the related information in the terminal location. After the change, the problem of the private network may not be selected, thereby ensuring that the terminal location is changed, and then maintaining or reselecting to a dedicated network, thereby improving the success rate of the terminal access.

Landscapes

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

Abstract

一种专用网络选择方法及装置。其中，该方法包括：专用网络的移动性管理实体在接收到位置更新请求时，获取终端的用户签约数据；所述移动性管理实体根据所述用户签约数据确定需要为所述终端选择专用网络；所述移动性管理实体判断所述终端正在使用的SGW和PGW是否属于专用网络；如果所述正在使用的SGW和/或PGW不属于专用网络，则所述移动性管理实体为所述终端选择专用网络的SGW和/或PGW，并将所述终端使用的SGW和/或PGW切换到选择的所述SGW和/或PGW。

Description

专用网络选择方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种专用网络选择方法及装置。
背景技术
为了保持第三代移动通信***在通信领域的竞争力，3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)标准工作组正致力于EPS(Evolved Packet System，演进分组域***)的研究。整个EPS***如图1所示主要包括E-UTRAN(Evolved Universal Terrestrial Radio Access Network，演进的通用陆地无线接入网络)和EPC(Evolved Packet Core，演进的分组核心网)两部分。该***的EPC能够支持用户从GERAN(GSM EDGE radio access network，GSM EDGE无线接入网)和UTRAN(Universal Terrestrial Radio Access Network，通用陆地无线接入网)的接入。
在EPC分组核心网中，包含了HSS(Home Subscriber Server，归属用户数据服务器)、MME(Mobility Management Entity，移动性管理单元)、S-GW(Serving Gateway，服务网关)、P-GW(PDN Gateway，分组数据网络网关)、SGSN(Serving GPRS Support Node，服务GPRS支持节点)和PCRF(Policy and Charging Enforcement Function，策略与计费规则功能实体)。
在EPC分组核心网中，HSS为用户签约数据的永久存放地点，位于用户签约的归属网。MME是用户签约数据在当前网络的存放地点，负责终端到网络的NAS层(Non-Access Stratum,非接入层)信令管理、用户空闲模式下的跟踪和寻呼管理功能和承载管理。S-GW是核心网到无线***的网关，负责终端到核心网的用户面承载、终端空闲模式下的数据缓存、网络侧发起业务请求的功能、合法窃听和分组数据路由和转发功能。P-GW是演进的分组域***(EPS)和该***外部网络的网关，负责终端的IP地址分配、计费功能、分组包过滤、策略应用等功能。SGSN是GERAN和UTRAN用户接入EPC网络的业务支持点，功能上与MME类似，负责用户的位置更新、寻呼管理和承载管理等功能。PCRF负责向PCEF提供策略控制与计费规则。
随着移动互联的发展，3GPP网络开始支持具有特殊特性的设备，例如传感器设备、数据卡等，由于各自不同的特性，这些不同类型的设备和用户在使用网络时，可能对网络的要求和使用情况都有所不同。因此，由运营商从运营的角度考虑为这些不同特性的设备和用户提供不同的网络，而这些网络可能具有区别于普通用户接入的特性， 称之为专用网络。考虑到兼容性的问题，有些设备可能无法通知自己的设备类型，因此网络可能只能够根据用户的签约信息为终端选择专用网络。但是用户的签约数据只能够在用户已经接入网络之后获取用户的签约数据，因此当用户接入非专用网络之后，需要非专用网络提供一种能够将用户重选到专用网络的方法。
图2为相关技术中的一种对于初始接入非专用网络的用户重选到专用网络的方法。如图2所示，该方法主要包括以下步骤201-步骤213。
步骤201～202，终端发起附着请求，其中携带终端的真实标识或者临时标识。基站可能将该请求路由到一个非专用网络的MME。
步骤203～204，在完成对终端的授权和鉴权过程后，MME向HSS发起位置更新请求。HSS收到后，向MME***用户数据，其中携带用户签约类型信息。
步骤205，MME根据签约数据和本地配置判断需要为用户重新选择专用网络，因此为终端分配一个虚假的临时标识，和一个非广播的跟踪区标识。其中临时标识包括两个部分：GUMMEI(Globally Unique MME Identifier，全球唯一MME标识)和M-TMSI(M-Temporary Mobile Station Identifier MME分配的临时终端标识)，其中GUMMEI指向专用网络而不是分配该标识的MME。
步骤206，MME向SGW/PGW发送创建会话请求，SGW/PGW建立会话成功后向MME返回创建会话响应。
步骤207，MME将分配的临时标识和非广播跟踪区标识通过附着接受消息发送给终端。终端收到后，并且完成无线承载建立流程后向网络发送附着完成消息
步骤208，终端根据收到的非广播跟踪区标识，与广播的不一致发起跟踪区更新请求携带GUTI，其中发送给基站的消息中携带虚假GUTI中的GUMMEI信息。
步骤209～210，基站根据GUMMEI信息为终端选择专用网络的MME。并将跟踪区更新请求转交给专用网络的MME。
步骤211～212，专用网络的MME收到该请求，根据其中包含的GUTI判断该用户之前注册到了非专用网络，因此拒绝本次接入，并在其中包含拒绝原因为隐式分离。
步骤213，终端重新发起附着请求，其中携带虚假的GUTI重新执行现有技术中的附着过程。基站即可根据其中的GUMMEI信息选择到专用网络。在这一过程中， 选定了专用网络中的MME后，专用网络的MME根据本地配置为终端选择专用网络的SGW和PGW。
然而上述方案中，没有考虑到当终端位置发生变化之后，如何保持或者重新选择到一个专用网络，从而使得在终端位置发生变化后可能无法选择到专用网络。
针对相关技术中在终端位置发生变化后可能无法选择到专用网络的问题，目前尚未提出有效的解决方案。
发明内容
针对相关技术中在终端位置发生变化后可能无法选择到专用网络的问题，本发明提供了一种专用网络选择方法及装置，以至少解决上述问题。
根据本发明的一个实施例，提供了一种专用网络选择方法，包括：移动性管理实体在接收到位置更新请求时，获取终端的用户签约数据；所述移动性管理实体根据所述用户签约数据确定需要为所述终端选择专用网络；所述移动性管理实体判断所述终端正在使用的服务网关SGW和分组数据网络网关PGW是否为属于专用网络；如果所述正在使用的SGW和/或PGW不属于专用网络，则所述移动性管理实体为所述终端选择专用网络的SGW和/或PGW，并将所述终端使用的SGW和/或PGW切换到选择的所述SGW和/或PGW。
可选地，所述移动性管理实体判断所述终端正在使用的服务网关SGW和分组数据网络网关PGW是否为属于专用网络，包括：所述移动性管理实体根据本地配置的专用网络的SGW和PGW的地址信息，判断所述终端正在使用的SGW和PGW是否属于专用网络；或者，所述移动性管理实体通过上下文获取或者通过域名***DNS获取所述终端正在使用的SGW和PGW的全称域名FQDN，根据预先设置的专用网络的SGW和PGW的FQDN的属性，判断所述终端正在使用的SGW和PGW是否属于专用网络。
可选地，所述移动性管理实体为所述终端选择专用网络的SGW和/或PGW，包括：所述移动性管理实体从本地配置的专用网络的SGW和PGW中，选择所述终端使用的SGW和/或PGW；或，所述移动性管理实体向DNS查询SGW和/或PGW的FQDN，根据预先设置的专用网络的SGW和/或PGW的FQDN的属性，从DNS返回的列表中选择一个专用网络的SGW/或PGW。
可选地，所述移动性管理实体将所述终端使用的SGW和/或PGW切换到选择的所述SGW和/或PGW，包括：如果所述正在使用的SGW不属于专用网络，所述正在使用的PGW属于专用网络，则所述移动性管理实体将所述终端使用的SGW切换到选择的所述SGW；如果所述正在使用的SGW属于专用网络，所述正在使用的PGW不属于专用网络，则所述移动性管理实体将所述终端使用的PGW切换到选择的所述PGW；如果所述正在使用的SGW不属于专用网络，所述正在使用的PGW不属于专用网络，则所述移动性管理实体将所述终端使用的SGW切换到选择的所述SGW，然后将所述终端使用的PGW切换到选择的所述PGW。
可选地，所述移动性管理实体将所述终端使用的SGW切换到选择的所述SGW，包括：所述移动性管理实体向选择的所述SGW发送创建会话请求，请求选择的所述SGW为所述终端创建会话，由选择的所述SGW向所述正在使用的PGW发送修改承载请求；所述移动性管理实体向所述正在使用的SGW发送删除会话请求，请求删除所述正在使用的SGW上的所述终端的会话。
可选地，所述移动性管理实体将所述终端使用的PGW切换到选择的所述PGW，包括：步骤A，所述移动性管理实体判断是否所述终端连接的所有PGW都不属于专用网络，如果是，则执行步骤B，否则，执行步骤C；步骤B，所述移动性管理实体向所述终端发送消息，指示所述终端重新发起附着请求，以及通过所述正在使用的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话；步骤C，所述移动性管理实体通过专用网络的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话，然后向所述终端发送去活承载请求，指示所述终端删除与相关的数据分组网络PDN连接，并发起该PDN连接重新激活，所述移动性管理实体在重新激活的过程中，为所述终端分配所述选择的PGW。
根据本发明的另一个实施例，提供了一种专用网络选择装置，位于移动性管理实体，包括：获取模块，设置为在接收到位置更新请求时，获取终端的用户签约数据；确定模块，设置为根据所述用户签约数据确定需要为所述终端选择专用网络；判断模块，设置为判断所述终端正在使用的服务网关SGW和分组数据网络网关PGW是否为属于专用网络，如果所述正在使用的SGW和/或PGW不属于专用网络，则触发执行模块；执行模块，设置为为所述终端选择专用网络的SGW和/或PGW，并将所述终端使用的SGW和/或PGW切换到选择的所述SGW和/或PGW。
可选地，所述判断模块通过以下方式之一进行判断：根据本地配置的专用网络的SGW和PGW的地址信息，判断所述终端正在使用的SGW和PGW是否属于专用网 络；通过上下文获取或者通过域名***DNS获取所述终端正在使用的SGW和PGW的全称域名FQDN，根据预先设置的专用网络的SGW和PGW的FQDN的属性，判断所述终端正在使用的SGW和PGW是否属于专用网络。
可选地，所述执行模块通过以下方式之一为所述终端选择专用网络的SGW和/或PGW：从本地配置的专用网络的SGW和PGW中，选择所述终端使用的SGW和/或PGW；或，向DNS查询SGW和/或PGW的FQDN，根据预先设置的专用网络的SGW和/或PGW的FQDN的属性，从DNS返回的列表中选择一个专用网络的SGW/或PGW。
可选地，所述执行模块包括：第一切换模块，设置为在所述正在使用的SGW不属于专用网络，所述正在使用的PGW属于专用网络的情况下，将所述终端使用的SGW切换到选择的所述SGW；第二切换模块，设置为在所述正在使用的SGW属于专用网络，所述正在使用的PGW不属于专用网络的情况下，将所述终端使用的PGW切换到选择的所述PGW；第三切换模块，设置为在所述正在使用的SGW不属于专用网络，所述正在使用的PGW不属于专用网络的情况下，将所述终端使用的SGW切换到选择的所述SGW，然后将所述终端使用的PGW切换到选择的所述PGW。
可选地，所述第一切换模块包括：第一请求单元，设置为向选择的所述SGW发送创建会话请求，请求选择的所述SGW为所述终端创建会话，由选择的所述SGW向所述正在使用的PGW发送修改承载请求；第二请求单元，设置为向所述正在使用的SGW发送删除会话请求，请求删除所述正在使用的SGW上的所述终端的会话。
可选地，所述第二切换模块包括：第一判断单元，设置为判断是否所述终端连接的所有PGW都不属于专用网络，如果是，则触发第一切换单元，否则，触发第二切换单元；第一切换单元，设置为向所述终端发送消息，指示所述终端重新发起附着请求，以及通过所述正在使用的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话；第二切换单元，设置为通过专用网络的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话，以及向所述终端发送去活承载请求，指示所述终端删除与相关的数据分组网络PDN连接并发起该PDN连接重新激活，并在所述终端重新激活的过程中，为所述终端分配所述选择的PGW。
根据本发明的又一个实施例，提供了一种移动性管理实体，包括上述的专用网络选择装置。
通过本发明，移动性管理实体在接收到终端的跟踪区更新请求或路由区更新请求时，为终端选择专用网络的SGW和PGW，解决了相关技术中在终端位置发生变化后 可能无法选择到专用网络的问题，进而可以保证当终端位置发生变化之后，也保持或者重新选择到一个专用网络，提高了终端接入的成功率。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是EPS***的网络架构示意图；
图2是根据相关技术的初始接入非专用网络的用户重选到专用网络的方法流程图；
图3是根据本发明实施例的专用网络选择方法的流程图；
图4是根据本发明可选实施例的MME执行专用网络选择方法的流程示意图；
图5是根据本发明实施例的专用网络选择装置的结构示意图；
图6是根据本发明实施例一的信令流程图；
图7是根据本发明实施例二的信令流程图；
图8是根据本发明实施例三的信令流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
根据本发明实施例，提供了一种专用网络选择方法。
图3为根据本发明实施例的专用网络选择方法的流程图，如图3所示，主要包括以下步骤S302至步骤S308。
步骤S302，移动性管理实体在接收到位置更新请求时，获取终端的用户签约数据。
在具体实施过程中，当移动性管理实体为MME时，位置更新请求为跟踪区更新(Tracking Area Update，TAU)请求，当移动性管理实体为SGSN时，位置更新请求为路由区更新(Route Area Update，RAU)请求。
优选地，本发明实施例的移动性管理实体为专用网络的移动性管理实体。
例如，终端可以通过基站向目标MME发起TAU流程，其中，终端可以在空闲态发起也可以在是切换之后发起TAU流程，如果终端是在空闲态发起TAU，则MME在接收到TAU请求时，可以进一步到源MME中获取上下文，并更新承载。如果是在切换之后发起TAU，则在切换过程中已经完成了上下文的传递，以及承载更新。
MME可以通过向HSS发起位置更新请求，从HHE返回的位置更新响应中获取终端的用户签约信息。
步骤S304，所述移动性管理实体根据所述用户签约数据和本地配置确定需要为所述终端选择专用网络。
为了便于网络为终端选择专用网络，签约中可能会指明某些终端应该被路由到专用网络，例如增加属性标签的方式，当移动管理实体收到这样用户的签约数据，可以根据特定的标签将其路由到专用网络。特别的是，可能对于不同的属性有不同的专用的网络，即网络中存在多种专用网络，移动管理实体可以根据不同的属性为其选择。考虑到漫游场景，除了依据签约数据，还可以根据移动管理实体的本地配置来协助这种选择，例如签约数据中的指示终端A的属性为1，可以路由到专用网络1，但是移动管理实体的本地配置不允许漫游用户使用自己的专用网络1，就可以不管签约的设置，为终端选择普通的网络。
步骤S306，所述移动性管理实体判断所述终端正在使用的服务网关SGW和分组数据网络网关PGW是否为属于专用网络。
可选地，可以在移动性管理实体中配置专用网络的SGW和PGW的地址信息，所述移动性管理实体可以根据本地配置的专用网络的SGW和PGW的地址信息，判断所述终端正在使用的SGW和PGW是否属于专用网络；或者，所述移动性管理实体也可以通过上下文获取或者通过域名***DNS获取所述终端正在使用的SGW和PGW的全称域名FQDN，根据预先设置的专用网络的SGW和PGW的FQDN的属性，判断所述终端正在使用的SGW和PGW是否属于专用网络。
步骤S308，如果所述正在使用的SGW和/或PGW不属于专用网络，则所述移动性管理实体为所述终端选择专用网络的SGW和/或PGW，并将所述终端使用的SGW和/或PGW切换到选择的所述SGW和/或PGW。
可选地，所述移动性管理实体在为所述终端选择专用网络的SGW和/或PGW时，可以从本地配置的专用网络的SGW和PGW中，选择所述终端使用的SGW和/或PGW；或，向DNS查询SGW和/或PGW的FQDN，根据预先设置的专用网络的SGW和/或PGW的FQDN的属性，从DNS返回的列表中选择一个专用网络的SGW/或PGW。
在本发明实施例的可选实施方式中，所述移动性管理实体将所述终端使用的SGW和/或PGW切换到选择的所述SGW和/或PGW，可以包括：如果所述正在使用的SGW不属于专用网络，所述正在使用的PGW属于专用网络，则所述移动性管理实体将所述终端使用的SGW切换到选择的所述SGW；如果所述正在使用的SGW属于专用网络，所述正在使用的PGW不属于专用网络，则所述移动性管理实体将所述终端使用的PGW切换到选择的所述PGW；如果所述正在使用的SGW不属于专用网络，所述正在使用的PGW不属于专用网络，则所述移动性管理实体将所述终端使用的SGW切换到选择的所述SGW，然后将所述终端使用的PGW切换到选择的所述PGW。
在本发明实施例的一个可选实施方式中，所述移动性管理实体在切换终端使用的SGW时，可以向选择的所述SGW发送创建会话请求，请求选择的所述SGW为所述终端创建会话，由选择的所述SGW向所述正在使用的PGW发送修改承载请求；以及向所述正在使用的SGW发送删除会话请求，请求删除所述正在使用的SGW上的所述终端的会话。从而将终端使用的SGW切换到专用网络的SGW上。
在本发明实施例的一个可选实施方式中，所述移动性管理实体将所述终端使用的PGW切换到选择的所述PGW可以包括以下步骤：步骤A，所述移动性管理实体判断是否所述终端连接的所有PGW都不属于专用网络，如果是，则执行步骤B，否则，执行步骤C；步骤B，所述移动性管理实体向所述终端发送消息，指示所述终端重新发起附着请求，以及通过所述正在使用的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话；步骤C，所述移动性管理实体通过专用网络的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话，然后向所述终端发送去活承载请求，指示所述终端删除与相关的数据分组网络PDN连接，并发起该PDN连接重新激活，所述移动性管理实体在重新激活的过程中，为所述终端分配所述选择的PGW。
可选地，上述MME可以为网络中的所有MME，图4为本发明实施例的可选实施方式中MME执行的流程图。如图4所示，MME在收到位置更新请求以及终端的签约数据后，首先判断是否需要为终端选择专用网络，如果不需要，则执行正常的位置更新流程，否则，MME进一步判断其本身是否为专用网络的网元。如果MME不是专用网络的网元，则按照图2所示的流程执行，即执行步骤205之后的流程，如果MME是专用网络的网元，则MME判断终端正在使用的PGW是否为专用网络的PGW。如果正在使用的PGW是专用网络的PGW，则MME进一步判断是否终端当前使用的SGW是否属于专用网络，如果终端当前使用的SGW不属于专用网络，则执行SGW重选过程，否则，执行正常的位置更新流程。如果正在使用的PGW不是专用网络的PGW，则MME进一步判断终端连接的全部PGW都不属于专用网络，即都不是专用网络节点。如果终端连接的全部PGW都不属于专用网络，则发起注销过程，或者拒绝位置更新请求，要求终端重新注册到网络。如果终端连接的部分PGW属于专用网络，则进一步判断是否终端当前使用的SGW是否属于专用网络，如果终端当前使用的SGW不属于专用网络，则执行SGW重选过程，然后对于PGW不属于专用网络的相关的PDN连接发起承载去活，要求终端重新激活相关的PDN连接，如果终端当前使用的SGW属于专用网络，则直接对于PGW不属于专用网络的相关的PDN连接发起承载去活，要求终端重新激活相关的PDN连接。
在本发明实施例中，专用网络的MME根据用户签约数据判断是否为终端选择专用的SGW/PGW，如果终端正在使用的PGW不是专用网络的PGW，则进一步判断是否全部的PGW都不是专用网络的PGW。如果全部都不是，则发起注销过程，或者拒绝位置更新请求，要求终端重新注册到网络。如果不是全部都是非专用节点，则进一步判断SGW是否为专用节点，如果SGW不是专用节点，则先执行SGW重选的过程，然后再发起承载去活，要求终端重新激活相关的PDN连接。如果终端正在使用的SGW不是专用网络的SGW，则MME执行SGW重选的过程。通过本发明实施例提供的技术方案，可以在终端位置发生变化后，保持或者重新选择到一个专用网络。
根据本发明实施例，还提供一种专用网络选择装置，位于移动性管理实体，用于实现本发明实施提供的上述专用网络选择方法。
图5为根据本发明实施例的专用网络选择装置的结构示意图，如图5所示，该装置主要包括：获取模块510，设置为获取终端的用户签约数据；确定模块520，设置为根据所述用户签约数据和本地配置确定需要为所述终端选择专用网络；判断模块530，设置为判断所述终端正在使用的服务网关SGW和分组数据网络网关PGW是否为属于专用网络，如果所述正在使用的SGW和/或PGW不属于专用网络，则触发执行模块； 执行模块540，设置为为所述终端选择专用网络的SGW和/或PGW，并将所述终端使用的SGW和/或PGW切换到选择的所述SGW和/或PGW。
可选地，所述判断模块530可以通过以下方式之一进行判断：根据本地配置的专用网络的SGW和PGW的地址信息，判断所述终端正在使用的SGW和PGW是否属于专用网络；通过上下文获取或者通过域名***DNS获取所述终端正在使用的SGW和PGW的全称域名FQDN，根据预先设置的专用网络的SGW和PGW的FQDN的属性，判断所述终端正在使用的SGW和PGW是否属于专用网络。
可选地，所述执行模块540可以通过以下方式之一为所述终端选择专用网络的SGW和/或PGW：从本地配置的专用网络的SGW和PGW中，选择所述终端使用的SGW和/或PGW；或，向DNS查询SGW和/或PGW的FQDN，根据预先设置的专用网络的SGW和/或PGW的FQDN的属性，从DNS返回的列表中选择一个专用网络的SGW/或PGW。
可选地，所述执行模块540可以包括：第一切换模块，设置为在所述正在使用的SGW不属于专用网络，所述正在使用的PGW属于专用网络的情况下，将所述终端使用的SGW切换到选择的所述SGW；第二切换模块，设置为在所述正在使用的SGW属于专用网络，所述正在使用的PGW不属于专用网络的情况下，将所述终端使用的PGW切换到选择的所述PGW；第三切换模块，设置为在所述正在使用的SGW不属于专用网络，所述正在使用的PGW不属于专用网络的情况下，将所述终端使用的SGW切换到选择的所述SGW，然后将所述终端使用的PGW切换到选择的所述PGW。
可选地，所述第一切换模块可以包括：第一请求单元，设置为向选择的所述SGW发送创建会话请求，请求选择的所述SGW为所述终端创建会话，由选择的所述SGW向所述正在使用的PGW发送修改承载请求；第二请求单元，设置为向所述正在使用的SGW发送删除会话请求，请求删除所述正在使用的SGW上的所述终端的会话。
可选地，所述第二切换模块可以包括：第一判断单元，设置为判断是否所述终端连接的所有PGW都不属于专用网络，如果是，则触发第一切换单元，否则，触发第二切换单元；第一切换单元，设置为向所述终端发送消息，指示所述终端重新发起附着请求，以及通过所述正在使用的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话；第二切换单元，设置为通过专用网络的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话，以及向所述终端发送去活承载请求，指示所述终端删除与相 关的数据分组网络PDN连接并发起该PDN连接重新激活，并在所述终端重新激活的过程中，为所述终端分配所述选择的PGW。
根据本发明实施例，还提供了一种移动性管理实体，包括上述的专用网络选择装置。
下面通过具体实施例对本发明实施例提供的技术方案进行说明。
实施例一
本实施例中对在TAU/RAU过程中实现专用网络选择进行说明。
在该本实施例中，源网络不支持专用网络，目标网络中的MME/SGSN是专用网络中的网元，而SGW不是专用网络中的网元。本实施例中，终端可以是空闲态发起TAU/RAU过程，也可以是在切换(HO)之后发生的TAU/RAU流程。下面描述中以TAU为例，RAU类似。
图6为本实施例中，在TAU过程中进行专用网络选择的信令流程图，如图6所示，主要包括以下步骤：
步骤601，UE通过基站向目标MME发起TAU流程。如果该过程是空闲态发起的，则目标MME在执行步骤602之前还需要从源MME获取上下文，并且更新承载。如果是在切换之后TAU，则在切换过程中已经完成了上下文的传递，以及承载更新，可以直接执行步骤602。
步骤602～304，目标MME向HSS发起位置更新请求。HSS收到后，向源MME/SGSN发送位置取消请求，源MME/SGSN向HSS返回位置取消响应。HSS通过位置更新响应向目标MME***用户数据，其中携带用户签约类型信息。
步骤605，目标MME根据签约数据和本地配置判断需要为用户重新选择专用网络，并且自己为专用网络节点。目标MME根据本地配置判断，终端所连接的PGW为专用网络节点，而SGW不属于专用网络节点。PGW不属于专用网络节点的情况在实施例二或三中讨论。
如果MME不属于专用网络节点，则MME不需要执行后续步骤，直接执行现有技术中的步骤205之后的相关流程。
目标MME根据本地配置信息，和/或DNS查询，获取专用网络的SGW地址信息。
MME选择或者配置专用SGW/PGW的方式可以为：
1.所有专用的MME都配置专用网络的SGW和PGW地址信息。因此MME就可以根据本地配置来判断SGW/PGW是否为专用节点，或者选择一个专用的SGW/PGW。
2.SGW/PGW使用不同的FQDN，例如特殊标记等方式，MME通过上下文获取，或者DNS查询获取到相应的FQDN，就能够判断该SGW/PGW是否为专用节点，或者从DNS返回的列表中选择一个专用的SGW/PGW.
步骤606～步骤609，目标MME向SGW发送创建会话请求，SGW向PGW发送修改承载请求。承载更新成功后，PGW向SGW发送修改承载响应，SGW向MME返回创建会话响应。
步骤610，目标MME向非专用节点的SGW发送删除会话请求，删除相应的资源，删除成功后，SGW向MME发送删除会话响应。
步骤611，如果TAU是切换之后发起的，或者在TAU之后建立了无线承载，则重选之后需要通知eNB，即执行该步骤。目标MME将重新选择的专用的SGW分配的地址和隧道端标识发送给eNB。
之前的过程中，如果没有建立无线承载，则不需要执行该步骤。
步骤612～613，目标MME向终端发送TAU接受消息，终端收到后保存网络分配的临时标识以及其他相关信息，向MME发送TAU完成消息。
实施例二
本实施例中，源网络不支持专用网络，目标网络中的MME/SGSN是专用网络中的网元，而PGW不是专用网络中的网元。当终端有多个PGW时，并且其中一个或者多个(不是全部)不为专用网络节点。该过程既可以是空闲态发起的TAU/RAU过程，也可以是在HO之后发生的TAU/RAU流程。本实施例中以TAU为例，RAU类似。
图7为本实施例中专用网络选择的信令流程图，如图7所示，主要包括以下步骤：
步骤701，UE通过基站向目标MME发起TAU流程。如果该过程是空闲态发起的，则目标MME在执行步骤702之前还需要去源MME获取上下文，并且更新承载。如果是在切换之后TAU，则在切换过程中已经完成了上下文的传递，以及承载更新，可以直接执行步骤702。
步骤702～704，目标MME向HSS发起位置更新请求。HSS收到后，向源MME/SGSN发送位置取消请求，源MME/SGSN向HSS返回位置取消响应。HSS通过位置更新响应向目标MME***用户数据，其中携带用户签约类型信息。
步骤705，目标MME根据签约数据和本地配置判断需要为用户重新选择专用网络，并且自己为专用网络节点。目标MME根据本地配置判断，终端所连接的SGW为专用网络节点，而PGW不属于专用网络节点。对于SGW和PGW都不属于专用网络节点的情况，需要先执行实施例图6中的步骤606～613，执行后，SGW属于专用网络节点，在执行该实施例中的相关步骤。
如果MME不属于专用网络节点，则MME不需要执行后续步骤，直接执行现有技术中的步骤205之后的相关流程。
目标MME根据本地配置信息，和/或DNS查询，获取专用网络的PGW地址信息。
MME选择或者配置专用SGW/PGW的方式可以为：
1.所有专用的MME都配置专用网络的SGW和PGW地址信息。因此MME就可以根据本地配置来判断SGW/PGW是否为专用节点，或者选择一个专用的SGW/PGW。
2.SGW/PGW使用不同的FQDN，例如特殊标记等方式，MME通过上下文获取，或者DNS查询获取到相应的FQDN，就能够判断该SGW/PGW是否为专用节点，或者从DNS返回的列表中选择一个专用的SGW/PGW.
步骤706～707，目标MME向终端发送TAU接受消息，终端收到后保存网络分配的临时标识以及其他相关信息，向MME发送TAU完成消息。
如果该过程是HO之后发起的TAU，或者已经有无线承载建立了，则目标MME在UE进入空闲态之后发起步骤708～710。如果在之前的过程中没有建立无线承载，则可以立即执行步骤708～710。
步骤708，目标MME通过SGW向PGW发送删除会话请求。PGW删除会话后通过SGW向MME返回删除会话响应。
步骤709～710，目标MME向终端发起去活承载请求，其中携带相关PDN连接的默认承载标识，并携带去活原因为“重新激活”。终端删除相关PDN连接，并向MME返回去活承载响应。并在后续发起该PDN连接的重新激活，在重新激活的过程中，目标MME为终端选择专用网络的PGW，选择方案如步骤705中描述。
实施例三
本实施例，
本实施例中，源网络不支持专用网络，目标网络中的MME/SGSN是专用网络中的网元，而PGW不是专用网络中的网元。该实施例中，假设终端连接的全部PGW都不是专用网络节点。或者MME支持专用网络选择，但是本身不是专用网络节点，此时推荐执行步骤506a～510a。
该过程既可以是空闲态发起的TAU/RAU过程，也可以是在HO之后发生的TAU/RAU流程。下面描述中以TAU为例，RAU类似。
图8为本实施例中专用网络选择的信令流程图，如图8所示，主要包括以下步骤：
步骤801～805与步骤701～705类似，不做赘述。
步骤806a～810a和步骤806b～807b，只需要执行其中一种。
与图7类似的是，如果该过程是HO之后发起的TAU，或者已经有无线承载建立了，则目标MME在UE进入空闲态之后发起步骤806a～810a或者步骤806b～807b。如果在之前的过程中没有建立无线承载，则可以立即执行步骤806a～810a或者步骤806b～807b。
步骤806a～步骤807a，目标MME向终端发送TAU接受消息，终端收到后保存网络分配的临时标识以及其他相关信息，向MME发送TAU完成消息。
步骤808a，目标MME向终端发送注销请求，其中携带指示要求终端重新发起attach过程。
步骤809a，目标MME通过SGW向PGW发送删除会话请求。PGW删除会话后通过SGW向MME返回删除会话响应。
步骤810a，终端向目标MME返回注销完成消息，并重新发起附着请求，其中携带在步骤806a中获得网络分配的临时标识。基站即可根据其中的GUMMEI信息选择到目标MME。
步骤806b，目标MME向终端返回TAU拒绝消息，其中携带拒绝原因为隐式分离。终端收到后重新发起附着请求。
步骤807b，目标MME通过SGW向PGW发送删除会话请求。PGW删除会话后通过SGW向MME返回删除会话响应。
从以上的描述中，可以看出，本发明实现了如下技术效果：移动性管理实体在接收到终端的跟踪区更新请求或路由区更新请求时，为终端选择专用网络的SGW和PGW，解决了相关技术中在终端位置发生变化后可能无法选择到专用网络的问题，进而可以保证当终端位置发生变化之后，也保持或者重新选择到一个专用网络，提高了终端接入的成功率。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
基于本发明实施例提供的上述技术方案，移动性管理实体在接收到终端的跟踪区更新请求或路由区更新请求时，为终端选择专用网络的SGW和PGW，解决了相关技术中在终端位置发生变化后可能无法选择到专用网络的问题，进而可以保证当终端位置发生变化之后，也保持或者重新选择到一个专用网络，提高了终端接入的成功率。

Claims (13)

  1. 一种专用网络选择方法，包括：
    移动性管理实体在接收到位置更新请求时，获取终端的用户签约数据；
    所述移动性管理实体根据所述用户签约数据确定需要为所述终端选择专用网络；
    所述移动性管理实体判断所述终端正在使用的服务网关SGW和分组数据网络网关PGW是否属于专用网络；
    如果所述正在使用的SGW和/或PGW不属于专用网络，则所述移动性管理实体为所述终端选择专用网络的SGW和/或PGW，并将所述终端使用的SGW和/或PGW切换到选择的所述SGW和/或PGW。
  2. 根据权利要求1所述的方法，其中，所述移动性管理实体判断所述终端正在使用的服务网关SGW和分组数据网络网关PGW是否属于专用网络，包括：
    所述移动性管理实体根据本地配置的专用网络的SGW和PGW的地址信息，判断所述终端正在使用的SGW和PGW是否属于专用网络；或者，
    所述移动性管理实体通过上下文获取或者通过域名***DNS获取所述终端正在使用的SGW和PGW的全称域名FQDN，根据预先设置的专用网络的SGW和PGW的FQDN的属性，判断所述终端正在使用的SGW和PGW是否属于专用网络。
  3. 根据权利要求1所述的方法，其中，所述移动性管理实体为所述终端选择专用网络的SGW和/或PGW，包括：
    所述移动性管理实体从本地配置的专用网络的SGW和PGW中，选择所述终端使用的SGW和/或PGW；或，
    所述移动性管理实体向DNS查询SGW和/或PGW的FQDN，根据预先设置的专用网络的SGW和/或PGW的FQDN的属性，从DNS返回的列表中选择一个专用网络的SGW/或PGW。
  4. 根据权利要求1至3中任一项所述的方法，其中，所述移动性管理实体将所述终端使用的SGW和/或PGW切换到选择的所述SGW和/或PGW，包括：
    如果所述正在使用的SGW不属于专用网络，所述正在使用的PGW属于专用网络，则所述移动性管理实体将所述终端使用的SGW切换到选择的所述SGW；
    如果所述正在使用的SGW属于专用网络，所述正在使用的PGW不属于专用网络，则所述移动性管理实体将所述终端使用的PGW切换到选择的所述PGW；
    如果所述正在使用的SGW不属于专用网络，所述正在使用的PGW不属于专用网络，则所述移动性管理实体将所述终端使用的SGW切换到选择的所述SGW，然后将所述终端使用的PGW切换到选择的所述PGW。
  5. 根据权利要求4所述的方法，其中，所述移动性管理实体将所述终端使用的SGW切换到选择的所述SGW，包括：
    所述移动性管理实体向选择的所述SGW发送创建会话请求，请求选择的所述SGW为所述终端创建会话，由选择的所述SGW向所述正在使用的PGW发送修改承载请求；
    所述移动性管理实体向所述正在使用的SGW发送删除会话请求，请求删除所述正在使用的SGW上的所述终端的会话。
  6. 根据权利要求4所述的方法，其中，所述移动性管理实体将所述终端使用的PGW切换到选择的所述PGW，包括：
    步骤A，所述移动性管理实体判断是否所述终端连接的所有PGW都不属于专用网络，如果是，则执行步骤B，否则，执行步骤C；
    步骤B，所述移动性管理实体向所述终端发送消息，指示所述终端重新发起附着请求，以及通过所述正在使用的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话；
    步骤C，所述移动性管理实体通过专用网络的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话，然后向所述终端发送去活承载请求，指示所述终端删除与相关的数据分组网络PDN连接，并发起该PDN连接重新激活，所述移动性管理实体在重新激活的过程中，为所述终端分配所述选择的PGW。
  7. 一种专用网络选择装置，位于移动性管理实体，包括：
    获取模块，设置为在接收到位置更新请求时，获取终端的用户签约数据；
    确定模块，设置为根据所述用户签约数据确定需要为所述终端选择专用网络；
    判断模块，设置为判断所述终端正在使用的服务网关SGW和分组数据网络网关PGW是否属于专用网络，如果所述正在使用的SGW和/或PGW不属于专用网络，则触发执行模块；
    执行模块，设置为为所述终端选择专用网络的SGW和/或PGW，并将所述终端使用的SGW和/或PGW切换到选择的所述SGW和/或PGW。
  8. 根据权利要求7所述的装置，其中，所述判断模块通过以下方式之一进行判断：
    根据本地配置的专用网络的SGW和PGW的地址信息，判断所述终端正在使用的SGW和PGW是否属于专用网络；
    通过上下文获取或者通过域名***DNS获取所述终端正在使用的SGW和PGW的全称域名FQDN，根据预先设置的专用网络的SGW和PGW的FQDN的属性，判断所述终端正在使用的SGW和PGW是否属于专用网络。
  9. 根据权利要求7所述的装置，其中，所述执行模块通过以下方式之一为所述终端选择专用网络的SGW和/或PGW：
    从本地配置的专用网络的SGW和PGW中，选择所述终端使用的SGW和/或PGW；或，
    向DNS查询SGW和/或PGW的FQDN，根据预先设置的专用网络的SGW和/或PGW的FQDN的属性，从DNS返回的列表中选择一个专用网络的SGW/或PGW。
  10. 根据权利要求7至9中任一项所述的装置，其中，所述执行模块包括：
    第一切换模块，设置为在所述正在使用的SGW不属于专用网络，所述正在使用的PGW属于专用网络的情况下，将所述终端使用的SGW切换到选择的所述SGW；
    第二切换模块，设置为在所述正在使用的SGW属于专用网络，所述正在使用的PGW不属于专用网络的情况下，将所述终端使用的PGW切换到选择的所述PGW；
    第三切换模块，设置为在所述正在使用的SGW不属于专用网络，所述正在使用的PGW不属于专用网络的情况下，将所述终端使用的SGW切换到选择的所述SGW，然后将所述终端使用的PGW切换到选择的所述PGW。
  11. 根据权利要求10所述的装置，其中，所述第一切换模块包括：
    第一请求单元，设置为向选择的所述SGW发送创建会话请求，请求选择的所述SGW为所述终端创建会话，由选择的所述SGW向所述正在使用的PGW发送修改承载请求；
    第二请求单元，设置为向所述正在使用的SGW发送删除会话请求，请求删除所述正在使用的SGW上的所述终端的会话。
  12. 根据权利要求10所述的装置，其中，所述第二切换模块包括：
    第一判断单元，设置为判断是否所述终端连接的所有PGW都不属于专用网络，如果是，则触发第一切换单元，否则，触发第二切换单元；
    第一切换单元，设置为向所述终端发送消息，指示所述终端重新发起附着请求，以及通过所述正在使用的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话；
    第二切换单元，设置为通过专用网络的SGW向所述正在使用的PGW发送删除会话请求，请求删除所述正在使用的PGW上所述终端的会话，以及向所述终端发送去活承载请求，指示所述终端删除与相关的数据分组网络PDN连接并发起该PDN连接重新激活，并在所述终端重新激活的过程中，为所述终端分配所述选择的PGW。
  13. 一种移动性管理实体，包括权利要求7至12中任一项所述的装置。
PCT/CN2014/089035 2014-06-05 2014-10-21 专用网络选择方法及装置 WO2015184722A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/316,148 US20170127324A1 (en) 2014-06-05 2014-10-21 Dedicate Network Selection Method and Device
EP14894150.3A EP3154294A4 (en) 2014-06-05 2014-10-21 Private network selection method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410248239.0A CN105142128B (zh) 2014-06-05 2014-06-05 专用网络选择方法及装置
CN201410248239.0 2014-06-05

Publications (1)

Publication Number Publication Date
WO2015184722A1 true WO2015184722A1 (zh) 2015-12-10

Family

ID=54727308

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/089035 WO2015184722A1 (zh) 2014-06-05 2014-10-21 专用网络选择方法及装置

Country Status (4)

Country Link
US (1) US20170127324A1 (zh)
EP (1) EP3154294A4 (zh)
CN (1) CN105142128B (zh)
WO (1) WO2015184722A1 (zh)

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6630675B2 (ja) 2014-10-06 2020-01-15 シャープ株式会社 Ｕｅ、基地局装置、ｕｅの通信制御方法及び基地局の通信制御方法
US10855645B2 (en) * 2015-01-09 2020-12-01 Microsoft Technology Licensing, Llc EPC node selection using custom service types
US9749908B2 (en) * 2015-07-29 2017-08-29 Verizon Patent And Licensing Inc. Local breakout service
CN107205251B (zh) * 2016-03-18 2020-03-06 北京佰才邦技术有限公司 一种终端接入网络的方法、装置及终端
CN107231703A (zh) * 2016-03-24 2017-10-03 中兴通讯股份有限公司 一种连接激活方法、设备和***
CN107548050B (zh) * 2016-06-24 2020-07-03 大唐移动通信设备有限公司 一种选择网元设备的方法和装置
CN107645722B (zh) * 2016-07-20 2021-01-26 中国电信股份有限公司 专用网络选择接入方法和***、公网mme、hss和基站
CN107872785B (zh) * 2016-09-23 2021-07-23 中国电信股份有限公司 终端附着方法和***、及移动性管理实体
CN108282827B (zh) * 2017-01-06 2022-07-12 北京三星通信技术研究有限公司 用于网络间互操作的方法、节点及设备
US10548140B2 (en) 2017-05-02 2020-01-28 Affirmed Networks, Inc. Flexible load distribution and management in an MME pool
EP4178242A1 (en) 2017-05-05 2023-05-10 Microsoft Technology Licensing, LLC Methods of and systems of service capabilities exposure function (scef) based internet-of-things (iot) communications
US11032378B2 (en) 2017-05-31 2021-06-08 Microsoft Technology Licensing, Llc Decoupled control and data plane synchronization for IPSEC geographic redundancy
CN109219099B (zh) * 2017-07-06 2021-07-20 北京佰才邦技术股份有限公司 一种网络切换方法、网络控制器、相关服务器及pgw
US10856134B2 (en) 2017-09-19 2020-12-01 Microsoft Technolgy Licensing, LLC SMS messaging using a service capability exposure function
CN110049578B (zh) * 2018-01-17 2021-08-03 华为技术有限公司 无线连接修改方法、设备及***
US11051201B2 (en) 2018-02-20 2021-06-29 Microsoft Technology Licensing, Llc Dynamic selection of network elements
EP3769476A1 (en) 2018-03-20 2021-01-27 Microsoft Technology Licensing, LLC Systems and methods for network slicing
US10924913B2 (en) * 2018-04-18 2021-02-16 T-Mobile Usa, Inc. Fault handling for location services requests
EP3827577B1 (en) 2018-07-23 2023-09-13 Microsoft Technology Licensing, LLC System and method for intelligently managing sessions in a mobile network
CN110881014B (zh) * 2018-09-05 2021-09-28 普天信息技术有限公司 一种对无线专网的业务进行物理隔离的方法及装置
CN112437456B (zh) * 2020-12-07 2023-05-26 中国联合网络通信集团有限公司 一种非公共网络中的通信方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012068837A1 (zh) * 2010-11-24 2012-05-31 中兴通讯股份有限公司 接入网关选择方法和装置
CN103313329A (zh) * 2012-03-07 2013-09-18 ***通信集团公司 服务网关选择方法及移动性管理实体
US20130308604A1 (en) * 2011-01-28 2013-11-21 Huawei Technologies Co., Ltd. Method and apparatus for selecting serving gateway
CN103609150A (zh) * 2011-06-18 2014-02-26 Lg电子株式会社 基于apn专有或者非apn专有信息经由本地网络进行流量分流

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056321B (zh) * 2009-10-30 2014-07-02 中兴通讯股份有限公司 一种实现本地接入的方法及***
CN102056143A (zh) * 2009-11-03 2011-05-11 中兴通讯股份有限公司 本地ip访问连接的管理方法
CN102056138B (zh) * 2009-11-05 2016-08-03 中兴通讯股份有限公司 本地ip访问连接的管理方法及装置
CN102056265A (zh) * 2009-11-10 2011-05-11 中兴通讯股份有限公司 限制mtc设备接入和通信的方法、移动管理单元及网关单元
CN102238676B (zh) * 2010-04-30 2014-02-19 华为技术有限公司 电路交换域到分组交换域的切换方法和设备及通信***
CN102244859B (zh) * 2010-05-10 2016-03-30 中兴通讯股份有限公司 分流连接中本地地址的处理方法、装置及***
CN102232311B (zh) * 2010-10-26 2013-10-02 华为技术有限公司 实现家庭基站服务质量控制的方法和设备及***
CN102801822B (zh) * 2012-08-15 2018-05-15 中兴通讯股份有限公司 一种本地网关地址更新方法及装置
CN103716850B (zh) * 2012-09-29 2018-10-26 中兴通讯股份有限公司 通信路径的切换方法、***及装置
CN103731811B (zh) * 2012-10-11 2018-08-31 中兴通讯股份有限公司 一种演进的分组核心网络实现移动性管理的方法和***
CN104735638B (zh) * 2013-12-18 2020-10-23 中兴通讯股份有限公司 一种小基站环境下交互信息的方法、基站和移动管理实体
CN111510980B (zh) * 2014-05-08 2022-06-03 交互数字专利控股公司 Ue到专用核心网络节点的重定向方法及无线发射接收单元

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012068837A1 (zh) * 2010-11-24 2012-05-31 中兴通讯股份有限公司 接入网关选择方法和装置
US20130308604A1 (en) * 2011-01-28 2013-11-21 Huawei Technologies Co., Ltd. Method and apparatus for selecting serving gateway
CN103609150A (zh) * 2011-06-18 2014-02-26 Lg电子株式会社 基于apn专有或者非apn专有信息经由本地网络进行流量分流
CN103313329A (zh) * 2012-03-07 2013-09-18 ***通信集团公司 服务网关选择方法及移动性管理实体

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3154294A4 *

Also Published As

Publication number Publication date
CN105142128A (zh) 2015-12-09
US20170127324A1 (en) 2017-05-04
EP3154294A4 (en) 2017-12-27
CN105142128B (zh) 2020-01-14
EP3154294A1 (en) 2017-04-12

Similar Documents

Publication Publication Date Title
WO2015184722A1 (zh) 专用网络选择方法及装置
US11272440B2 (en) Network slice selection method and apparatus
US10412647B2 (en) Mobility management apparatus reselection method and mobility management apparatus
JP7291245B2 (ja) Ｒａｎページング処理
KR20210142725A (ko) 코어 페이징 처리
US20150280927A1 (en) Method, system, and controller for routing forwarding
US8582503B2 (en) Method for indicating the bearer management of a serving gateway
US11202332B2 (en) Terminal apparatus, AMF, SMF, core network apparatus, and communication control method
JP2010539758A (ja) Ｌｔｅシステムにおいて、ユーザ静的ｉｐアドレスのアドレッシングをサポートする方法、システムおよび装置
WO2011050678A1 (zh) 一种基于控制面与媒体面分离的网络架构实现的通信网络
US10448433B2 (en) Data processing method, apparatus, terminal, mobility management entity, and system
WO2014166294A1 (zh) 临近业务服务器的选择方法及装置、用户注册方法及装置
WO2014206251A1 (zh) ***间切换方法、装置及网络***
WO2013004121A1 (zh) 本地网关信息处理方法及装置
WO2016000189A1 (zh) 网元选择实体及用户设备注册的方法
EP3484234B1 (en) User equipment context management method, device, and apparatus
WO2015154426A1 (zh) ProSe临时标识的通知与更新方法和装置
KR20190116358A (ko) 단말 장치, 코어 네트워크 장치, 및 통신 제어 방법
WO2016019559A1 (zh) 共享网络的用户设备识别装置、***及方法
JP7507144B2 (ja) インジケーション情報送信方法、装置およびシステム、および記憶媒体
WO2009097780A1 (zh) 一种静态ip地址的处理方法和设备
WO2013174188A1 (zh) 路由优化方法及***、无线侧网元
WO2016112774A1 (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: 14894150

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2014894150

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15316148

Country of ref document: US

Ref document number: 2014894150

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE