WO2017181353A1 - 专用核心网迁移处理方法、设备和*** - Google Patents

专用核心网迁移处理方法、设备和*** Download PDF

Info

Publication number
WO2017181353A1
WO2017181353A1 PCT/CN2016/079712 CN2016079712W WO2017181353A1 WO 2017181353 A1 WO2017181353 A1 WO 2017181353A1 CN 2016079712 W CN2016079712 W CN 2016079712W WO 2017181353 A1 WO2017181353 A1 WO 2017181353A1
Authority
WO
WIPO (PCT)
Prior art keywords
core network
dedicated core
auxiliary information
mobility management
request message
Prior art date
Application number
PCT/CN2016/079712
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 CN201680083437.3A priority Critical patent/CN108781402A/zh
Priority to KR1020187032544A priority patent/KR20180132851A/ko
Priority to BR112018071476A priority patent/BR112018071476A2/pt
Priority to EP16898941.6A priority patent/EP3448089A4/en
Priority to PCT/CN2016/079712 priority patent/WO2017181353A1/zh
Publication of WO2017181353A1 publication Critical patent/WO2017181353A1/zh
Priority to US16/164,875 priority patent/US20190053037A1/en

Links

Images

Classifications

    • 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
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • 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
    • 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
    • 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
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • 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
    • 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
    • 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/08—Access point devices
    • 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/14—Backbone network devices

Definitions

  • the present invention relates to communication technologies, and in particular, to a dedicated core network migration processing method, device, and system.
  • the operator subscribes to a user equipment (User Equipment, UE) usage type for the terminal type with the same communication feature, and deploys a dedicated DCN network element for the terminal having the same usage type. It is specially deployed on the DCN network element, so that operators can carry out targeted management and maintenance on different types of terminals, and realize dedicated network, thereby improving the efficiency of massive terminal access mobility management and session management, and reducing network efficiency. Maintenance costs.
  • UE User Equipment
  • the change of the type of the subscription of the UE to the network side causes the DCN network element of the currently serving UE to continue to serve the UE, and the UE needs to be migrated to the DCN network element that can provide the service type for the UE after the update.
  • the migration of the private network is implemented by redirecting the UE on the network side.
  • the DCN network element requests the UE to initiate a re-access procedure, and initiates a Non-Access Stratum (NAS) in the access procedure initiated by the UE.
  • NAS Non-Access Stratum
  • the directed procedure redirects the UE to a DCN network element that can support the UE usage type.
  • the DCN network element needs to initiate a NAS redirection process to redirect the UE from one DCN network element to another type that can support the UE after the update.
  • the DCN network element wastes unnecessary signaling overhead.
  • redirecting the UE between different DCNs also affects the isolation between different DCNs deployed by the operator, which is not conducive to the evolution of the 5G network slicing technology.
  • the present invention provides a dedicated core network migration processing method, device, and system for saving unnecessary redirection signaling overhead and ensuring isolation between different DCNs.
  • an embodiment of the present invention provides a dedicated core network migration processing method, including:
  • the mobility management network element acquires a usage type of the user equipment UE subscription
  • the mobility management network element determines the auxiliary core network auxiliary information of the UE according to the usage type of the UE subscription;
  • the mobility management network element sends a request message to the UE, where the request message is used to indicate that the UE re-initiates the access request, and the request message carries the UE.
  • Dedicated core network auxiliary information is used to indicate that the UE re-initiates the access request, and the request message carries the UE.
  • the mobility management network element acquires the usage type of the UE subscription, and determines the UE's dedicated core network auxiliary information according to the usage type, after requesting When the UE re-initiates the access procedure, the dedicated core network auxiliary information is sent to the UE, so that the UE may send the dedicated core network auxiliary information to the base station in the RRC connection setup request message that is triggered when the access procedure is initiated.
  • the base station can select a dedicated core network corresponding to the dedicated core network auxiliary information for the UE according to the dedicated core network auxiliary information, and directly migrate the UE to the mobility management network element that can serve the UE, thereby preventing the mobile management network element from initiating NAS redirection.
  • the process saves unnecessary redirection signaling overhead and also ensures isolation between different DCNs.
  • determining the dedicated core network auxiliary information of the UE according to the type of the UE subscription including:
  • the mobility management network element determines the dedicated core network auxiliary information of the UE according to the usage type of the UE subscription and the following information: the mapping relationship between the usage type of the UE configured by the operator and the dedicated core network, and the locally configured carrier Policy, context information of the UE.
  • the method further includes:
  • the mobility management network element sends a paging message to the UE to make the UE into a connected state.
  • the mobile management network element sends a request message to the UE, specifically:
  • the mobility management network element sends a temporary identity re-allocation request message to the UE, where the temporary identity re-allocation request message carries the non-broadcast location area identifier and the dedicated core network auxiliary information of the UE, where the non-broadcast location area identifier is used to indicate that the UE re-initiates the connection.
  • the temporary identity re-allocation request message carries the non-broadcast location area identifier and the dedicated core network auxiliary information of the UE, where the non-broadcast location area identifier is used to indicate that the UE re-initiates the connection.
  • the mobile management network element sends a request message to the UE, specifically:
  • the mobility management network element sends a connection release command message to the serving base station of the UE, and the connection release command message carries the cause value and the dedicated core network auxiliary information of the UE; the connection release command message is used to indicate that the base station uses the cause value and the dedicated core network of the UE.
  • the information carried in the RRC connection release message is sent to the UE, and the reason value is used to indicate that the UE re-initiates the access request.
  • the mobile management network element sends a request message to the UE, specifically:
  • the mobility management network element sends a detach request message to the UE, where the detach request message carries the re-attachment separation type and the dedicated core network auxiliary information of the UE, and the re-attachment separation type is used to instruct the UE to re-initiate the access request.
  • the UE re-initiates the access request, including: an attach request or a location update request.
  • the dedicated core network auxiliary information of the UE includes: a dedicated core network type of the mobility management network element and/or a usage type of the UE subscription.
  • the embodiment of the present invention provides a dedicated core network migration processing method, including:
  • the user equipment UE receives the request message sent by the mobility management network element, where the request message is used to indicate that the UE re-initiates the access request, and the request message carries the dedicated core network auxiliary information determined by the mobility management network element for the UE;
  • the UE sends an access request message according to the request message, and the private core network auxiliary information is carried in the radio resource control RRC connection setup request message triggered by the access request message, and is sent to the serving base station of the UE, and the dedicated core network auxiliary information is used by the base station.
  • the UE selects to correspond to the dedicated core network auxiliary information.
  • Dedicated core network Dedicated core network.
  • the foregoing method further includes: the UE saves the dedicated core network auxiliary information, and associates the dedicated core network auxiliary information with the service network of the UE.
  • the dedicated core network auxiliary information is determined by the mobility management network element according to the usage type of the UE subscription and at least one of the following information: the usage type and the dedicated mode of the UE configured by the operator The mapping relationship between the core networks, the locally configured carrier policy, and the context information of the UE.
  • the method further includes:
  • the UE receives the paging message sent by the mobility management network element, and sends a paging response message to establish a connection with the mobility management network element.
  • the UE receives the request message sent by the mobility management network element, specifically:
  • the UE receives the temporary identity re-allocation request message sent by the mobility management network element, where the temporary identity re-allocation request message carries the non-broadcast location area identifier and the dedicated core network auxiliary information of the UE, where the non-broadcast location area identifier is used to indicate that the UE re-initiates Access request.
  • the UE receives the request message sent by the mobility management network element, specifically:
  • the UE receives the radio resource control RRC connection release message sent by the base station, where the RRC connection release message carries the cause value and the dedicated core network auxiliary information of the UE; the RRC connection release message is sent by the base station after receiving the connection release command message sent by the mobility management network element.
  • the connection release command message carries the cause value and the dedicated core network auxiliary information of the UE, and the cause value is used to instruct the UE to re-initiate the access request.
  • the UE receives the request message sent by the mobility management network element, specifically:
  • the UE receives the detach request message sent by the mobility management network element, where the detach request message carries the re-attachment separation type and the dedicated core network auxiliary information of the UE, and the re-attachment separation type is used to instruct the UE to re-initiate the access request.
  • the access request message includes: an attach request or a location update request.
  • the dedicated core network auxiliary information of the UE is a dedicated core network type of the mobility management network element or a usage type subscribed by the UE.
  • an embodiment of the present invention provides a mobility management network element, including:
  • An obtaining module configured to acquire a usage type of the user equipment UE subscription
  • a determining module configured to determine, according to the type of use signed by the UE, the dedicated core network auxiliary information of the UE;
  • a sending module configured to send a request message to the UE, if the dedicated core network auxiliary information of the UE does not match the dedicated core network served by the mobility management network element, the request message is used to indicate that the UE re-initiates the access request, and the request message carries The dedicated core network auxiliary information of the UE.
  • the determining module is specifically configured to:
  • the sending module is further configured to: if the UE is in an idle state, send a paging message to the UE to change the UE into a connected state before sending the request message to the UE.
  • the sending module is specifically configured to:
  • the sending module is specifically configured to:
  • connection release command message carries the cause value and the dedicated core network auxiliary information of the UE; the connection release command message is used to instruct the base station to carry the cause value and the UE's dedicated core network auxiliary information in the wireless
  • the resource control RRC connection release message is sent to the UE, and the cause value is used to instruct the UE to re-initiate the access request.
  • the sending module is specifically configured to:
  • the detach request message is sent to the UE, and the detach request message carries the re-attachment separation type and the dedicated core network auxiliary information of the UE, and the re-attachment separation type is used to instruct the UE to re-initiate the access request.
  • the UE re-initiates the access request, including: an attach request or a location update request.
  • the dedicated core network auxiliary information of the UE includes: a dedicated core network type of the mobility management network element and/or a usage type of the UE subscription.
  • the embodiment of the present invention provides a user equipment UE, including:
  • a receiving module configured to receive a request message sent by the mobility management network element, where the request message is used to instruct the UE to re-initiate the access request, where the request message carries the dedicated core network auxiliary information determined by the mobility management network element for the UE;
  • a sending module configured to send an access request message according to the request message, and send the dedicated core network auxiliary information to the serving base station sent by the UE in the RRC connection setup request message triggered by the access request message, and the dedicated core network auxiliary information
  • the base station selects a dedicated core network corresponding to the dedicated core network auxiliary information for the UE.
  • the UE further includes:
  • the storage module is configured to save the dedicated core network auxiliary information, and associate the dedicated core network auxiliary information with the UE service network.
  • the dedicated core network auxiliary information is determined by the mobility management network element according to the usage type of the UE subscription and at least one of the following information: the usage type and the dedicated mode of the UE configured by the operator The mapping relationship between the core networks, the locally configured carrier policy, and the context information of the UE.
  • the receiving module is further configured to:
  • the receiving module is specifically configured to:
  • the temporary identity re-allocation request message carries the non-broadcast location area identifier and the dedicated core network auxiliary information of the UE, where the non-broadcast location area identifier is used to indicate that the UE re-initiates the connection Into the request.
  • the receiving module is specifically configured to:
  • the RRC connection release message is sent by the base station after receiving the connection release command message sent by the mobility management network element, and the connection release command message carries the cause value and the dedicated core network of the UE.
  • the information, the cause value is used to instruct the UE to re-initiate the access request.
  • the receiving module is specifically configured to:
  • the detach request message carries the re-attachment separation type and the dedicated core network auxiliary information of the UE, where the re-attach separation type is used to instruct the UE to re-initiate the access request.
  • the access request message includes: an attach request or a location update request.
  • the dedicated core network auxiliary information of the UE is a dedicated core network type of the mobility management network element or a usage type subscribed by the UE.
  • an embodiment of the present invention provides a mobility management network element, including:
  • a processor configured to acquire a usage type of the user equipment UE subscription; and determine, according to the usage type of the UE subscription, the UE core network auxiliary information;
  • a transmitter configured to send a request message to the UE, if the dedicated core network auxiliary information of the UE does not match the dedicated core network served by the mobility management network element, the request message is used to indicate that the UE re-initiates the access request, and the request message carries The dedicated core network auxiliary information of the UE.
  • the processor is specifically configured to:
  • the transmitter is further configured to: if the UE is in an idle state, send a paging message to the UE to change the UE into a connected state before sending the request message to the UE.
  • the transmitter is specifically configured to:
  • the temporary identity re-allocation request message is sent to the UE, where the non-broadcast location area identifier and the dedicated core network auxiliary information of the UE are carried in the non-broadcast location area identifier, and the non-broadcast location area identifier is used to instruct the UE to re-initiate the access request.
  • the transmitter is specifically configured to:
  • connection release command message Sending a connection release command message to the serving base station of the UE, where the connection release command message carries the cause value and the dedicated core network auxiliary information of the UE; the connection release command message is used to instruct the base station to carry the cause value and the UE's dedicated core network auxiliary information in the wireless
  • the resource control RRC connection release message is sent to the UE, and the cause value is used to instruct the UE to re-initiate the access request.
  • the transmitter is specifically configured to:
  • the detach request message carries the re-attachment separation type and the dedicated core network auxiliary information of the UE, and the re-attachment separation type is used to instruct the UE to re-initiate the access request.
  • the UE re-initiates the access request, including: an attach request or a location update request.
  • the dedicated core network auxiliary information of the UE includes: a dedicated core network type of the mobility management network element and/or a usage type of the UE subscription.
  • an embodiment of the present invention provides a user equipment UE, including:
  • a receiver configured to receive a request message sent by the mobility management network element, where the request message is used to indicate that the UE re-initiates the access request, where the request message carries the dedicated core network auxiliary information determined by the mobility management network element for the UE;
  • a transmitter configured to send an access request message according to the request message, and carry the dedicated core network auxiliary information in a radio resource control RRC connection setup request message triggered by the access request message, and send the message to the serving base station of the UE, and the dedicated core network auxiliary information
  • the base station selects a dedicated core network corresponding to the dedicated core network auxiliary information for the UE.
  • the UE further includes: a memory and a processor, where the memory is used to save the dedicated core network auxiliary information; and the processor is configured to associate the dedicated core network auxiliary information with the service network of the UE.
  • the dedicated core network auxiliary information is determined by the mobility management network element according to the usage type of the UE subscription and at least one of the following information: the usage type and the dedicated mode of the UE configured by the operator The mapping relationship between the core networks, the locally configured carrier policy, and the context information of the UE.
  • the receiver is further configured to:
  • the receiver is specifically configured to:
  • the temporary identity re-allocation request message carries the non-broadcast location area identifier and the dedicated core network auxiliary information of the UE, where the non-broadcast location area identifier is used to indicate that the UE re-initiates the connection Into the request.
  • the receiver is specifically configured to:
  • the RRC connection release message is sent by the base station after receiving the connection release command message sent by the mobility management network element.
  • the connection release command message carries the cause value and the dedicated core network auxiliary information of the UE, and the cause value is used to indicate that the UE re-initiates the access request.
  • the receiver is specifically configured to:
  • the detach request message carries the re-attachment separation type and the dedicated core network auxiliary information of the UE, where the re-attach separation type is used to instruct the UE to re-initiate the access request.
  • the access request message includes: an attach request or a location update request.
  • the dedicated core network auxiliary information of the UE is a dedicated core network type of the mobility management network element or a usage type subscribed by the UE.
  • the seventh aspect of the present invention provides a dedicated core network migration processing system, including: the mobility management network element provided by the foregoing third aspect, and the user equipment UE provided by the foregoing fourth aspect.
  • the eighth aspect of the present invention provides a dedicated core network migration processing system, including: the mobility management network element provided in the foregoing fifth aspect, and the user equipment UE provided in the foregoing sixth aspect.
  • the mobility management network element acquires the usage type of the UE subscription, and according to the usage class
  • the dedicated core network auxiliary information is sent to the UE, so that the UE may be in the RRC connection setup request message triggered when the access procedure is initiated.
  • FIG. 1 is a schematic diagram of a system architecture provided by the present invention.
  • Embodiment 1 is a schematic flowchart of Embodiment 1 of a method for processing a dedicated core network migration according to the present invention
  • Embodiment 3 is a schematic flowchart of Embodiment 2 of a method for processing a dedicated core network migration according to the present invention
  • Embodiment 4 is a schematic flowchart of Embodiment 3 of a method for processing a dedicated core network migration according to the present invention
  • FIG. 5 is a schematic flowchart diagram of Embodiment 4 of a method for processing a dedicated core network migration according to the present invention
  • FIG. 6 is a schematic structural diagram of Embodiment 1 of a mobility management network element according to the present invention.
  • FIG. 7 is a schematic structural diagram of Embodiment 1 of a UE according to the present invention.
  • FIG. 8 is a schematic structural diagram of Embodiment 2 of a mobility management network element provided by the present invention.
  • FIG. 9 is a schematic structural diagram of Embodiment 2 of a UE according to the present invention.
  • the dedicated core network migration processing method provided by the embodiment of the present invention can be applied to 2G, 3G, 4G.
  • 1 is a schematic diagram of a system architecture provided by the present invention. As shown in FIG. 1, the system includes: a user equipment UE, a base station, and a mobility management network element (a mobility management network element is a type of a CN network element), and the UE can pass through a base station and a Or multiple mobile management network elements to communicate.
  • a mobility management network element is a type of a CN network element
  • each mobility management network element has its DCN type (DCN type), and the DCN type mobility management network element also A DCN network element;
  • DCN type DCN type
  • a DCN-type mobility management network element can provide services for one or more types of UEs, and a UE usage type can be simultaneously served by multiple DCN network elements supporting different DCN types. Therefore, there may be the following four correspondences between the DCN type of the DCN network element and the usage type of the UE:
  • DCN network elements with DCN type for machine type communication can only serve UEs using type smart meter communication;
  • DCN network elements with DCN type for machine type communication can simultaneously provide services for UEs using type of smart meter communication and smart water meter communication;
  • a DCN network element has two DCN types: machine type communication and smart car communication, and machine type communication can simultaneously provide services for UEs using type of smart meter communication and smart water meter communication; Both class communication and smart car communication require simultaneous service for UEs that use a type of autonomous vehicle communication.
  • the DCN type of the mobility management network element and the UE usage type that can be served are mutually equivalent, that is, the DCN type of the mobility management network element is the served UE.
  • the usage type for example, the mobility management network element can simultaneously provide services for the UE using the type 1, the usage type 2, and the usage type 3.
  • the three DCN types of the mobility management network element are usage type 1, usage type 2, and usage.
  • Type 3 wherein the type 1 can be specifically for machine type communication, the type 2 can be specifically for smart car communication, and the type 3 can be for smart home communication.
  • a UE is a device that provides voice, short message, and/or data connectivity to a user, and may include, for example, a handheld device having a wireless connection function or a processing device connected to a wireless modem.
  • the user equipment can pass through a radio access network (Radio Access Network, Referred to as RAN), it communicates with the core network and exchanges voice and/or data with the RAN.
  • the user equipment may include a wireless terminal device, a mobile terminal device, a Subscriber Unit, a Subscriber Station, a Mobile Station, a Mobile, a Remote Station, and an access point. (Access Point, AP), Remote Terminal, Access Terminal, User Terminal, User Agent, User Device, etc.
  • the user equipment may also include a mobile telephone (or "cellular" telephone), a computer with a mobile terminal device, a portable, pocket, handheld, computer built-in or vehicle-mounted mobile device, for example, personal communication service (Personal Communication) Service, referred to as PCS) telephone, cordless telephone, Session Initiation Protocol (SIP) telephone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), Subscriber Unit , Personal Computer, Laptop Computer, Tablet Computer, Netbook, Handheld, Data Card, USB Insert Device, Mobile Wireless Fidelity Devices such as Wi-Fi devices such as WiFi devices, smart watches/smart glasses, and Wearable Devices.
  • PCS Personal communication service
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • Wi-Fi devices such as WiFi devices, smart watches/smart glasses, and Wearable Devices.
  • the base station may be a base station controller (BSC) in a 2G network, a radio network controller (Radio Network Controller, RNC for short) or a base station (NodeB) in a 3G network. It may be an evolved base station (eNodeB, e-volved Node B, E-UTRAN Node B) or the like in a 4G network, and is not limited in this application.
  • BSC base station controller
  • RNC Radio Network Controller
  • the mobile management network element in the embodiment of the present invention may be a Mobile Switching Centre (MSC)/Visitors Location Register (VLR) in a 2G/3G network, and the MSC and the VLR are usually combined.
  • MSC/VLR Mobility Management Entity
  • VLR Mobility Management Entity
  • the same network element, called MSC/VLR, or simply VLR may also be a Serving General Packet Radio Service Support Node (SGSN) in a 2G/3G network, or may be 4G.
  • the mobility management entity (Mobility Management Entity, MME for short) in the network may also include other device types and the like, which is not specifically limited in this application.
  • the dedicated core network migration processing method in the embodiment of the present invention is to solve the problem that the DCN network element needs to initiate a NAS redirection process to redirect the UE from one DCN network element to another DCN network capable of supporting the UE usage type.
  • a technical problem that wastes unnecessary signaling overhead and affects the isolation between DCNs.
  • Embodiment 1 is a schematic flowchart of Embodiment 1 of a method for processing a dedicated core network migration according to the present invention. As shown in FIG. 2, the method provided in this embodiment includes the following steps:
  • the mobility management network element acquires a usage type of the UE subscription.
  • an operator subscribes to a usage type for a UE having the same communication feature, for example, a handheld device, a smart home, a car, and the like.
  • the UE's Home Subscriber Server (HSS) or Home Location Register (HLR) stores the UE subscription type.
  • HSS Home Subscriber Server
  • HLR Home Location Register
  • the mobility management NE can The HSS/HLR obtains the usage type of the updated UE.
  • the HSS/HLR actively informs the service mobility management network element of the UE of the updated UE usage type.
  • the mobility management network element determines the dedicated core network auxiliary information of the UE according to the usage type of the UE subscription.
  • the DCN Assistance Information also known as the DCN Selection Assistance Parameter, is assigned by the operator to a dedicated core network (including mobility management network elements) deployed in its network.
  • a mobility management network element represented by a dedicated core network auxiliary information may provide services for one or more types of UEs, and the dedicated core network auxiliary information of the UE is a dedicated core corresponding to the mobility management network element that can serve the same. Network auxiliary information.
  • the dedicated core network auxiliary information may be: a DCN type of the mobility management network element and/or a UE subscription type, or other types of DCN types and/or UE subscription types that may indicate the mobility management network element.
  • the information as for the specific information name, is not specifically limited in the present invention.
  • each mobility management network element has its DCN type, and a DCN type mobility management network element can provide services for one or more usage types of UEs. If a mobility management network element only provides services for a UE of one type of use, the DCN type may also be a usage type of the UE.
  • the dedicated core network auxiliary information may be a DCN type or a usage type of the UE; if a mobility management
  • the network element provides services for multiple types of UEs, and the dedicated core network auxiliary information is of the DCN type.
  • DCN type can be machine type communication MTC, cellular internet of things (Cellular Internet of Things, referred to as CIoT) communication, mobile broadband (MBB) communication, car networking communication and other types, wherein the car network communication DCN can serve a variety of brands (use type) of car services.
  • the mobility management network element may determine the dedicated core network auxiliary information of the UE according to the usage type of the UE subscription and the following information: the usage type of the UE configured by the operator and the dedicated core network. The mapping relationship between the two, the locally configured carrier policy, and the context information of the UE.
  • the mobility management network element may have a mapping relationship between the usage type of the UE configured by the operator and the dedicated core network, and according to the mapping relationship, the mobility management network element may directly obtain the dedicated core corresponding to the usage type of the UE.
  • Network auxiliary information may be used to directly obtain the dedicated core corresponding to the usage type of the UE.
  • the mobility management network element may also obtain the dedicated core network auxiliary information corresponding to the usage type of the UE according to the locally configured carrier policy. For example, for a roaming UE, the operator can configure a corresponding access policy, and determine, according to the signed roaming protocol, a dedicated core network that the UE of the usage type can access, and the mobility management network element obtains corresponding to the usage type of the UE.
  • Dedicated core network auxiliary information For example, for a roaming UE, the operator can configure a corresponding access policy, and determine, according to the signed roaming protocol, a dedicated core network that the UE of the usage type can access, and the mobility management network element obtains corresponding to the usage type of the UE.
  • the mobility management network element may further determine the dedicated core network auxiliary information corresponding to the usage type of the UE according to the context information of the available UE. For example, for the UE using the type of CIoT, the mobility management network element may be supported according to the saved UE. Context information such as CIoT control plane optimization capability or user plane optimization capability is used to determine the dedicated core network assistance information of the UE.
  • the mobility management network element sends a request message to the UE.
  • the request message is used to indicate that the UE re-initiates the access request, and the request message carries the dedicated core network auxiliary information of the UE.
  • the dedicated core network auxiliary information of the UE does not match the dedicated core network served by the mobile management network element currently served by the UE, that is, the mobile currently serving the UE.
  • the management network element cannot continue to serve the UE corresponding to the dedicated core network auxiliary information; at this time, the mobility management network element may carry the dedicated core network auxiliary information in the request message and send the message to the UE, and notify the mobile management network that the UE can serve.
  • the dedicated core network auxiliary information corresponding to the element; and the UE is requested to re-initiate the access request, so that the base station directly migrates the UE to the mobility management network element that can serve the UE.
  • the mobile management network element will determine the brand B smart car corresponding to the dedicated core network auxiliary information brand B car networking Sent to the UE.
  • the UE receives a request message sent by the mobility management network element.
  • the UE can obtain the dedicated core network auxiliary information corresponding to the mobility management network element that can be served by the UE, and then report the dedicated core network auxiliary information to the base station.
  • the UE sends an access request message according to the request message, and sends the dedicated core network auxiliary information to the serving base station of the UE in the RRC connection setup request message triggered by the access request message.
  • the dedicated core network auxiliary information is used by the base station to select a dedicated core network DCN corresponding to the dedicated core network auxiliary information for the UE.
  • the UE after receiving the request message sent by the mobility management network element, the UE re-initiates the access procedure.
  • the UE needs to establish a connection with the serving base station first, that is, the UE first sends an access request message.
  • a Radio Resource Control (RRC) connection establishment request message is triggered.
  • the UE may send the dedicated core network auxiliary information in the RRC connection setup request message to the base station, so that the base station selects the dedicated core network corresponding to the dedicated core network auxiliary information according to the dedicated core network auxiliary information.
  • RRC Radio Resource Control
  • the access request re-initiated by the UE may be an attach request or a location update request, which may be determined according to the indication information in the request message sent by the mobility management network element.
  • the location update request may be Including a Location Area Updating (LAU) request, a Routing Area Updating (RAU) request, or a Tracking Area Updating (TAU) request.
  • LAU Location Area Updating
  • RAU Routing Area Updating
  • TAU Tracking Area Updating
  • the base station selects, for the UE, a dedicated core network corresponding to the dedicated core network auxiliary information.
  • the base station receives the RRC connection setup request message sent by the UE, and after establishing a connection with the UE, may select a dedicated core network corresponding to the dedicated core network auxiliary information according to the dedicated core network auxiliary information, to send the request message sent by the UE. Forwarding to the mobility management network element that can serve the UE corresponding to the dedicated core network auxiliary information, the UE is migrated to the mobility management network element that can serve the UE.
  • the base station has already stored the configuration relationship between the dedicated core network auxiliary information and the corresponding DCN network element, for example, if the dedicated core network auxiliary information is of the DCN type, the base station saves The DCN type 1 corresponds to the DCN network element A, and the DCN type 2 corresponds to the DCN network element B. If the dedicated core network auxiliary information is the UE usage type, the base station stores the usage type 1 corresponding to the DCN network element A, and the usage type 2 Corresponds to DCN network element B and so on.
  • the dedicated core network migration processing method when the usage type of the UE subscription is changed, the mobility management network element acquires the usage type of the UE subscription, and after determining the dedicated core network auxiliary information of the UE according to the usage type, requesting the UE When the access process is re-initiated, the dedicated core network auxiliary information is sent to the UE, so that the UE may send the dedicated core network auxiliary information to the serving base station in the RRC connection setup request message that is triggered when the access process is re-initiated.
  • the base station can select a dedicated core network corresponding to the dedicated core network auxiliary information for the UE according to the dedicated core network auxiliary information, and directly migrate the UE to the mobile management network element capable of serving the updated usage type of the UE, thereby avoiding the mobility management network.
  • the element initiates the NAS redirection process, which saves unnecessary redirection signaling overhead and ensures isolation between different DCNs.
  • Embodiment 3 is a schematic flowchart of Embodiment 2 of a method for processing a dedicated core network migration according to the present invention.
  • This embodiment is a detailed description of a specific implementation manner of step S103 in the foregoing embodiment shown in FIG. 2, as shown in FIG.
  • the method provided in this embodiment includes the following steps:
  • the mobility management network element acquires a usage type of the UE subscription.
  • the mobility management network element determines the dedicated core network auxiliary information of the UE according to the usage type of the UE subscription. If the dedicated core network auxiliary information of the UE does not match the dedicated core network served by the mobility management network element, and the UE is in an idle state, Steps S203 and S204 are performed; if the UE is in the connected state, steps S203 and S204 are skipped and step S205 is directly executed.
  • the mobility management network element sends a paging message to the UE.
  • the UE receives the paging message, and sends a paging response message to establish a connection with the mobility management network element, and becomes a connected state.
  • the mobility management network element sends a temporary identity re-allocation request message to the UE.
  • the temporary identity re-allocation request message carries the non-broadcast location area identifier and the UE.
  • the dedicated core network auxiliary information, the non-broadcast location area identifier is used to instruct the UE to re-initiate the access request.
  • the temporary identity re-allocation request message may be a globally unique Temporary Identity (GUTI) re-allocation command (GUTI REALLOCATION COMMAND) message of the UE, in the 2G/3G network, temporary The identity re-allocation request message may be a Temporary Mobile Subscriber Identity (TMSI) re-allocation command (TMSI REALLOCATION COMMAND) message, or a Packet Temporary Mobile Subscriber Identity (P-TMSI) Assign a command (P-TMSI REALLOCATION COMMAND) message, etc.
  • TMSI Temporary Mobile Subscriber Identity
  • P-TMSI Packet Temporary Mobile Subscriber Identity
  • P-TMSI REALLOCATION COMMAND Packet Temporary Mobile Subscriber Identity
  • the non-broadcast location area identifier (non-broadcast tracking area identifier, non-broadcast TAI) carried in the temporary identity re-allocation request message is in the 2G/3G network.
  • the non-broadcast location area identifier (non-broadcast location area identifier (non-broadcast location area identifier) or the non-broadcast routing area identifier (non-broadcast routing area identifier) is not included in the non-broadcast location area identifier (non-broadcast location area identifier).
  • the identity referred to as the non-broadcast RAI, is used to indicate that the UE re-initiates the access request. At this time, the access request re-initiated by the UE is specifically a location update request.
  • the UE receives a temporary identity re-allocation request message sent by the mobility management network element.
  • the UE saves the dedicated core network auxiliary information, and associates the dedicated core network auxiliary information with the UE service network.
  • the UE learns the dedicated core network auxiliary information corresponding to the mobility management network element that can be served by the UE; at this time, the UE may save the dedicated core network auxiliary information, and
  • the associated private network auxiliary information and the UE currently serving the Public Land Mobile Network (PLMN), that is, the mobile management network element serving the UE in the current serving PLMN is the DCN network element corresponding to the auxiliary information of the dedicated core network.
  • the update of the dedicated core network auxiliary information is implemented, so that the UE subsequently reports the updated dedicated core network auxiliary information when the serving PLMN initiates the access request.
  • the UE sends an access request message, and sends the dedicated core network auxiliary information to the serving base station of the UE in the RRC connection setup request message triggered by the access request message.
  • the UE A location update procedure is initiated, in which the UE carries the dedicated core network auxiliary information in the RRC connection setup request message and sends it to the serving base station.
  • the base station selects, for the UE, a dedicated core network DCN corresponding to the dedicated core network auxiliary information.
  • FIG. 4 is a schematic flowchart of a third embodiment of a dedicated core network migration processing method according to the present invention.
  • This embodiment is a detailed description of another specific implementation manner of step S103 in the foregoing embodiment shown in FIG. 2, as shown in FIG.
  • the method provided in this embodiment includes the following steps:
  • the mobility management network element acquires a usage type of the UE subscription.
  • the mobility management network element determines the dedicated core network auxiliary information of the UE according to the usage type of the UE subscription. If the dedicated core network auxiliary information of the UE does not match the dedicated core network served by the mobility management network element, and the UE is in an idle state, Steps S303 and S304 are performed; if the UE is in the connected state, steps S303 and S304 are skipped and step S305 is directly executed.
  • the mobility management network element sends a paging message to the UE.
  • the UE receives the paging message, and sends a paging response message to establish a connection with the mobility management network element, and becomes a connected state.
  • the mobility management network element sends a connection release command message to the serving base station of the UE.
  • connection release command message carries the cause value and the dedicated core network auxiliary information of the UE, and the connection release command message is used to instruct the base station to carry the cause value and the dedicated core network auxiliary information of the UE in the RRC connection release message.
  • the UE, the cause value is used to instruct the UE to re-initiate the access request.
  • connection release command message may be a UE context connection release command message (UE Context Release Command), or may be an Iu Release Release Command message (Iu Release Command).
  • the message When the mobile management network element sends the connection release command message, the message carries the cause value.
  • the cause value may be, for example, DCN reselection, to indicate that the UE re-initiates the access request.
  • the reselection of the DCN may also be a cause value indicating that the UE needs to initiate re-access because it needs to perform DCN reselection.
  • the base station sends the cause value and the dedicated core network auxiliary information of the UE to the UE in an RRC connection release message.
  • the base station after receiving the connection release command message, the base station sends an RRC connection release message to the UE, and the RRC connection release message is sent, the base station may forward the reason value to the UE, and instruct the UE to re-initiate the access request. .
  • the access request re-initiated by the UE is specifically a location update request.
  • the UE receives an RRC connection release message sent by the base station.
  • the UE saves the dedicated core network auxiliary information, and associates the dedicated core network auxiliary information with the UE service network.
  • the UE sends an access request message, and sends the dedicated core network auxiliary information to the serving base station of the UE in the RRC connection setup request message triggered by the access request message.
  • the UE after receiving the RRC connection release message sent by the mobility management network element, the UE initiates a location update process according to the cause value.
  • the UE carries the dedicated core network auxiliary information in the RRC connection setup request message and sends the message to the base station.
  • the base station selects, for the UE, a dedicated core network corresponding to the dedicated core network auxiliary information.
  • FIG. 5 is a schematic flowchart of Embodiment 4 of a method for processing a dedicated core network migration according to the present invention.
  • This embodiment is a detailed description of another specific implementation manner of step S103 in the foregoing embodiment shown in FIG. 2, as shown in FIG. 5.
  • the method provided in this embodiment includes the following steps:
  • the mobility management network element acquires a usage type of the UE subscription.
  • the mobility management network element determines the dedicated core network auxiliary information of the UE according to the usage type of the UE subscription, if the UE's dedicated core network auxiliary information does not match the dedicated core network served by the mobility management network element, and the UE is in an idle state, Steps S403 and S404 are performed; if the UE is in the connected state, steps S403 and S404 are skipped and step S405 is directly executed.
  • the mobility management network element sends a paging message to the UE.
  • the UE receives the paging message, and sends a paging response message to establish a connection with the mobility management network element.
  • the mobility management network element sends a separation request message to the UE.
  • the detach request message carries the re-attachment separation type and the dedicated core network auxiliary information of the UE, and the re-attachment separation type is used to instruct the UE to re-initiate the access request (specifically, an attach request).
  • the UE receives the separation request message sent by the mobility management network element.
  • the UE saves the dedicated core network auxiliary information, and associates the dedicated core network auxiliary information with the UE's service network.
  • the UE sends an access request message, and sends the dedicated core network auxiliary information to the serving base station of the UE in the RRC connection setup request message triggered by the access request message.
  • the UE after receiving the detach request message sent by the mobility management network element, the UE initiates an attach procedure. In the process, the UE sends the dedicated core network auxiliary information in the RRC connection setup request message to the base station.
  • the base station selects, for the UE, a dedicated core network corresponding to the dedicated core network auxiliary information.
  • FIG. 6 is a schematic structural diagram of Embodiment 1 of a mobility management network element according to the present invention. As shown in FIG. 6, the mobility management network element 100 in this embodiment includes:
  • the obtaining module 110 is configured to acquire a usage type of the user equipment UE subscription
  • the determining module 120 is configured to determine, according to the usage type of the UE subscription, the dedicated core network auxiliary information of the UE;
  • the sending module 130 is configured to: if the dedicated core network auxiliary information of the UE does not match the dedicated core network served by the mobility management network element, send a request message to the UE, where the request message is used to instruct the UE to re-initiate the access request, in the request message. Carrying the dedicated core network auxiliary information of the UE.
  • the determining module 120 is specifically configured to: Dedicated core network auxiliary information of the UE is determined by the type of usage of the UE subscription and the following information: the mapping relationship between the usage type of the UE configured by the operator and the dedicated core network, the locally configured operator policy, and the context of the UE. information.
  • the sending module 130 is further configured to: if the UE is in an idle state, send a paging message to the UE to send the UE into a connected state before sending the request message to the UE.
  • the sending module 130 is specifically configured to: send a temporary identity re-allocation request message to the UE, where the temporary identity re-allocation request message carries the non-broadcast location area identifier and the dedicated core of the UE.
  • the network auxiliary information, the non-broadcast location area identifier is used to instruct the UE to re-initiate the access request.
  • the sending module 130 is specifically configured to: send a connection release command message to the serving base station of the UE, where the connection release command message carries the cause value and the dedicated core network auxiliary information of the UE;
  • the command message is used to indicate that the base station sends the cause value and the dedicated core network auxiliary information of the UE to the UE in the RRC connection release message, and the reason value is used to indicate that the UE re-initiates the access request.
  • the sending module 130 is specifically configured to: send a detach request message to the UE, where the detach request message carries the re-attachment separation type and the dedicated core network auxiliary information of the UE, and the re-attach separation type is used.
  • the UE is instructed to re-initiate the access request.
  • the access request re-initiated by the UE includes: an attach request or a location update request.
  • the dedicated core network auxiliary information of the UE includes: a dedicated core network type of the mobility management network element and/or a usage type of the UE subscription.
  • the mobility management network element provided in this embodiment may perform the foregoing method embodiments, and the implementation principles and technical effects thereof are similar, and details are not described herein again.
  • FIG. 7 is a schematic structural diagram of Embodiment 1 of a UE according to the present invention. As shown in FIG. 7, the UE 200 in this embodiment includes:
  • the receiving module 210 is configured to receive a request message sent by the mobility management network element, where the request message is used to instruct the UE to re-initiate the access request, where the request message carries the dedicated core network auxiliary information determined by the mobility management network element for the UE;
  • the sending module 220 is configured to send an access request message according to the request message, and send the dedicated core network
  • the auxiliary information is sent to the serving base station of the UE in the RRC connection setup request message triggered by the access request message, and the dedicated core network auxiliary information is used by the base station to select a dedicated core network corresponding to the dedicated core network auxiliary information for the UE.
  • the UE 200 further includes: a storage module 230, configured to save the dedicated core network auxiliary information, and associate the dedicated core network auxiliary information with the service network of the UE.
  • a storage module 230 configured to save the dedicated core network auxiliary information, and associate the dedicated core network auxiliary information with the service network of the UE.
  • the dedicated core network auxiliary information is determined by the mobility management network element according to the usage type of the UE subscription and at least one of the following information: the usage type and the dedicated core of the UE configured by the operator.
  • the receiving module 210 is further configured to: receive a paging message sent by the mobility management network element, and send a paging response message to the mobile management network element by using the sending module 220.
  • the receiving module 210 is specifically configured to: receive a temporary identity re-allocation request message sent by the mobility management network element, where the temporary identity re-allocation request message carries the non-broadcast location area identifier and The dedicated core network auxiliary information of the UE, the non-broadcast location area identifier is used to instruct the UE to re-initiate the access request.
  • the receiving module 210 is specifically configured to: receive a radio resource control RRC connection release message sent by the base station, where the RRC connection release message carries the cause value and the dedicated core network auxiliary information of the UE;
  • the connection release message is sent by the base station after receiving the connection release command message sent by the mobility management network element.
  • the connection release command message carries the cause value and the dedicated core network auxiliary information of the UE, and the cause value is used to indicate that the UE re-initiates the access request.
  • the receiving module 210 is specifically configured to: receive a detach request message sent by the mobility management network element, where the detach request message carries the re-attach separation type and the dedicated core network auxiliary information of the UE, and The attach separation type is used to instruct the UE to re-initiate the access request.
  • the access request message includes: an attach request or a location update request.
  • the dedicated core network auxiliary information of the UE may be a dedicated core network type of the mobility management network element or a usage type subscribed by the UE.
  • the UE provided by the embodiment of the present invention may perform the foregoing method embodiments, and the implementation principles and technical effects thereof are similar, and details are not described herein again.
  • FIG. 8 is a schematic structural diagram of Embodiment 2 of a mobility management network element according to the present invention.
  • the mobility management network element 300 in this embodiment includes: a processor 310, a memory 320, and a transmitter 330.
  • Memory 320 can include read only memory and random access memory and provides instructions and data to processor 310.
  • the processor 310 is configured to acquire a type of use that the user equipment UE subscribes to; and determine, according to the type of use signed by the UE, the dedicated core network auxiliary information of the UE;
  • the transmitter 330 is configured to send a request message to the UE, if the dedicated core network auxiliary information of the UE does not match the dedicated core network served by the mobility management network element, where the request message is used to instruct the UE to re-initiate the access request, in the request message. Carrying the dedicated core network auxiliary information of the UE.
  • the processor 310 is specifically configured to: determine the dedicated core network auxiliary information of the UE according to the usage type of the UE subscription and the following information: the usage type of the UE configured by the operator The mapping relationship with the dedicated core network, the locally configured carrier policy, and the context information of the UE.
  • the sender 330 is further configured to: if the UE is in an idle state, send a paging message to the UE to send the UE into a connected state before sending the request message to the UE.
  • the transmitter 330 is specifically configured to: send a temporary identity re-allocation request message to the UE, where the temporary identity re-allocation request message carries the non-broadcast location area identifier and the dedicated core of the UE.
  • the network auxiliary information, the non-broadcast location area identifier is used to instruct the UE to re-initiate the access request.
  • the transmitter 330 is specifically configured to: send a connection release command message to the serving base station of the UE, where the connection release command message carries the cause value and the dedicated core network auxiliary information of the UE;
  • the command message is used to indicate that the base station sends the cause value and the dedicated core network auxiliary information of the UE to the UE in the RRC connection release message, and the reason value is used to indicate that the UE re-initiates the access request.
  • the transmitter 330 is specifically configured to: send a detach request message to the UE, where the detach request message carries the re-attach separation type and the dedicated core network auxiliary information of the UE, and the re-attach separation type is used.
  • the UE is instructed to re-initiate the access request.
  • the access request re-initiated by the UE includes: an attach request or a location update request.
  • the dedicated core network auxiliary information of the UE includes: a dedicated core network type of the mobility management network element and/or a usage type of the UE subscription.
  • the mobility management network element provided in this embodiment may perform the foregoing method embodiments, and the implementation principles and technical effects thereof are similar, and details are not described herein again.
  • FIG. 9 is a schematic structural diagram of Embodiment 2 of a UE according to the present invention.
  • the UE 400 in this embodiment includes: a processor 410, a memory 420, a receiver 430, and a transmitter 440.
  • Memory 420 can include read only memory and random access memory and provides instructions and data to processor 410.
  • the receiver 430 is configured to receive a request message sent by the mobility management network element, where the request message is used to instruct the UE to re-initiate the access request, where the request message carries the dedicated core network auxiliary information determined by the mobility management network element for the UE. ;
  • the transmitter 440 is configured to send an access request message according to the request message, and send the dedicated core network auxiliary information to the serving base station sent by the UE in the RRC connection setup request message triggered by the access request message, and the dedicated core network assists The information is used by the base station to select a dedicated core network corresponding to the dedicated core network auxiliary information for the UE.
  • the UE 400 further includes: a memory 420, configured to save the dedicated core network auxiliary information; the processor 410 is configured to associate the dedicated core network auxiliary information with the UE service by calling a program or an instruction stored in the memory 420.
  • the internet is a standard for storing program code.
  • the dedicated core network auxiliary information is determined by the mobility management network element according to the usage type of the UE subscription and at least one of the following information: the usage type and the dedicated core of the UE configured by the operator.
  • the receiver 430 is further configured to: receive a paging message sent by the mobility management network element, and send a paging response message by using the transmitter 440 to establish a connection with the mobility management network element.
  • the receiver 430 is specifically configured to: receive a temporary identity re-allocation request message sent by the mobility management network element, where the temporary identity re-allocation request message carries the non-broadcast location area identifier and The dedicated core network auxiliary information of the UE, the non-broadcast location area identifier is used to instruct the UE to re-initiate the access request.
  • the receiver 430 is specifically configured to: receive The RRC connection release message is sent by the RRC connection release message, and the RRC connection release message carries the cause value and the dedicated core network auxiliary information of the UE.
  • the RRC connection release message is sent by the base station after receiving the connection release command message sent by the mobility management network element.
  • the connection release command message carries the cause value and the dedicated core network auxiliary information of the UE, and the cause value is used to instruct the UE to re-initiate the access request.
  • the receiver 430 is specifically configured to: receive a detach request message sent by the mobility management network element, where the detach request message carries the re-attach separation type and the dedicated core network auxiliary information of the UE, and The attach separation type is used to instruct the UE to re-initiate the access request.
  • the access request message includes: an attach request or a location update request.
  • the dedicated core network auxiliary information of the UE may be a dedicated core network type of the mobility management network element or a usage type subscribed by the UE.
  • the UE provided by the embodiment of the present invention may perform the foregoing method embodiments, and the implementation principles and technical effects thereof are similar, and details are not described herein again.
  • An embodiment of the present invention provides a dedicated core network migration processing system, which includes: the mobility management network element in the foregoing embodiment shown in FIG. 6 and the user equipment UE in the foregoing embodiment shown in FIG.
  • An embodiment of the present invention further provides a dedicated core network migration processing system, which includes: the mobility management network element in the foregoing embodiment shown in FIG. 8 and the user equipment UE in the foregoing embodiment shown in FIG.
  • the mobile management network element and the UE are at least one, and the system can perform the foregoing method embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.

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

本发明提供一种专用核心网迁移处理方法、设备和***，其中，该方法包括：当UE签约的使用类型改变时，移动管理网元获取UE签约的使用类型，若UE的专用核心网辅助信息与移动管理网元所服务的专用核心网不匹配，移动管理网元向UE发送请求消息，UE根据请求消息发送接入请求消息，并将专用核心网辅助信息携带在接入请求消息触发的RRC连接建立请求消息中发送给UE的服务基站，使基站为UE选择与专用核心网辅助信息对应的专用核心网。本发明提供的技术方案能够避免移动管理网元发起NAS重定向流程，从而节省不必要的重定向信令开销，同时保证不同DCN之间的隔离性。

Description

专用核心网迁移处理方法、设备和*** 技术领域
本发明涉及通信技术，尤其涉及一种专用核心网迁移处理方法、设备和***。
背景技术
随着移动通信网络的演进与大量新应用的不断出现，不同的用户在不同的应用领域中逐渐形成了不同的通信特征，从而产生了不同的移动通信类型与对应的终端类型，比如：机器类通信(Machine Type Communication，简称MTC)、移动虚拟网络通信、公共安全通信等。这些不同的终端类型从核心网(Core Network，简称CN)侧来看具有不同的通信需求：不同的可选特征支持、不同的业务特征需求、不同的可用性需求、不同的拥塞管理机制等。随着不同终端类型数量的急剧增加，运营商提出了为不同的终端类型部署不同专用核心网(Dedicated Core Networks，简称DCN)的需求。具体的，运营商为具有相同通信特征的终端类型签约一个用户设备(User Equipment，UE)使用类型(usage type)，并为其部署专门的DCN网元，让具有相同使用类型的终端注册在为其专门部署的DCN网元上，以便于运营商对不同类型的终端进行有针对性的管理与维护，实现专网专用，从而提升对海量终端接入移动管理与会话管理的效率，降低网络的维护成本。
对于UE在网络侧签约的使用类型改变，导致当前服务UE的DCN网元不能继续服务该UE，需要将该UE迁移到能为该UE更新后的使用类型提供服务的DCN网元上，以满足运营商对不同使用类型终端进行专用网络管理的需求。
现有技术中通过在网络侧对UE进行重定向来实现专用网络的迁移。具体的，当UE在网络侧签约的使用类型改变时，DCN网元会请求UE发起重新接入流程，在UE发起的接入流程中发起非接入层(Non-Access Stratum，简称NAS)重定向流程，将UE重定向到能支持该UE使用类型的DCN网元上。
在研究过程中，发明人发现现有的这种专用核心网迁移处理方法，DCN网元需要发起NAS重定向流程将UE从一个DCN网元重定向到另一个能支持UE更新后的使用类型的DCN网元，从而浪费了不必要的信令开销；并且，在不同DCN之间重定向UE，也影响了运营商部署的不同DCN之间的隔离性，从而不利于向5G网络切片技术演进。
发明内容
针对现有技术的上述缺陷，本发明提供一种专用核心网迁移处理方法、设备和***，用于节省不必要的重定向信令开销，保证不同DCN之间的隔离性。
第一方面，本发明实施例提供一种专用核心网迁移处理方法，包括：
移动管理网元获取用户设备UE签约的使用类型；
移动管理网元根据UE签约的使用类型，确定UE的专用核心网辅助信息；
若UE的专用核心网辅助信息与移动管理网元所服务的专用核心网不匹配，移动管理网元向UE发送请求消息，请求消息用于指示UE重新发起接入请求，请求消息中携带UE的专用核心网辅助信息。
通过第一方面提供的专用核心网迁移处理方法，当UE签约的使用类型改变时，移动管理网元获取UE签约的使用类型，并根据该使用类型确定UE的专用核心网辅助信息后，在请求UE重新发起接入流程时，就将该专用核心网辅助信息发送给UE，从而UE可以在发起接入流程时触发的RRC连接建立请求消息中，将该专用核心网辅助信息发送给基站，使得基站能够根据该专用核心网辅助信息为UE选择与专用核心网辅助信息对应的专用核心网，直接将UE迁移到能服务该UE的移动管理网元，因而避免了移动管理网元发起NAS重定向流程，节省了不必要的重定向信令开销，同时也保证了不同DCN之间的隔离性。
在第一方面的一种可能的实施方式中，根据UE签约的使用类型，确定UE的专用核心网辅助信息，包括：
移动管理网元根据UE签约的使用类型和如下信息中的至少一种确定UE的专用核心网辅助信息：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
在第一方面的一种可能的实施方式中，若UE处于空闲态，在移动管理网元向UE发送请求消息之前，上述方法还包括：
移动管理网元向UE发送寻呼消息，以使UE变为连接态。
在第一方面的一种可能的实施方式中，移动管理网元向UE发送请求消息，具体包括：
移动管理网元发送临时身份标识重分配请求消息给UE，临时身份标识重分配请求消息中携带非广播位置区域标识和UE的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
在第一方面的一种可能的实施方式中，移动管理网元向UE发送请求消息，具体包括：
移动管理网元发送连接释放命令消息给UE的服务基站，连接释放命令消息中携带原因值和UE的专用核心网辅助信息；连接释放命令消息用于指示基站将原因值和UE的专用核心网辅助信息携带在无线资源控制RRC连接释放消息中发送给UE，原因值用于指示UE重新发起接入请求。
在第一方面的一种可能的实施方式中，移动管理网元向UE发送请求消息，具体包括：
移动管理网元发送分离请求消息给UE，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求。
在第一方面的一种可能的实施方式中，UE重新发起的接入请求，包括：附着请求或者位置更新请求。
在第一方面的一种可能的实施方式中，UE的专用核心网辅助信息包括：移动管理网元的专用核心网类型和/或UE签约的使用类型。
第二方面，本发明实施例提供一种专用核心网迁移处理方法，包括：
用户设备UE接收移动管理网元发送的请求消息，请求消息用于指示UE重新发起接入请求，请求消息中携带移动管理网元为UE确定的专用核心网辅助信息；
UE根据请求消息发送接入请求消息，并将专用核心网辅助信息携带在接入请求消息触发的无线资源控制RRC连接建立请求消息中发送给UE的服务基站，专用核心网辅助信息用于基站为UE选择与专用核心网辅助信息对应 的专用核心网。
在第二方面的一种可能的实施方式中，上述方法还包括：UE保存专用核心网辅助信息，并关联专用核心网辅助信息与UE的服务网络。
在第二方面的一种可能的实施方式中，专用核心网辅助信息是移动管理网元根据UE签约的使用类型和如下信息中的至少一种确定的：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
在第二方面的一种可能的实施方式中，若UE处于空闲态，在UE接收移动管理网元发送的请求消息之前，上述方法还包括：
UE接收移动管理网元发送的寻呼消息，并发送寻呼响应消息与移动管理网元建立连接。
在第二方面的一种可能的实施方式中，UE接收移动管理网元发送的请求消息，具体包括：
UE接收移动管理网元发送的临时身份标识重分配请求消息，临时身份标识重分配请求消息中携带非广播位置区域标识和UE的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
在第二方面的一种可能的实施方式中，UE接收移动管理网元发送的请求消息，具体包括：
UE接收基站发送的无线资源控制RRC连接释放消息，RRC连接释放消息中携带原因值和UE的专用核心网辅助信息；RRC连接释放消息是基站接收到移动管理网元发送的连接释放命令消息后发送的，连接释放命令消息中携带原因值和UE的专用核心网辅助信息，原因值用于指示UE重新发起接入请求。
在第二方面的一种可能的实施方式中，UE接收移动管理网元发送的请求消息，具体包括：
UE接收移动管理网元发送的分离请求消息，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求。
在第二方面的一种可能的实施方式中，接入请求消息包括：附着请求或者位置更新请求。
在第二方面的一种可能的实施方式中，UE的专用核心网辅助信息为移动管理网元的专用核心网类型或者UE签约的使用类型。
上述第二方面所提供的通信方法，其有益效果可以参见上述第一方面所带来的有益效果，在此不再赘述。
第三方面，本发明实施例提供一种移动管理网元，包括：
获取模块，用于获取用户设备UE签约的使用类型；
确定模块，用于根据UE签约的使用类型，确定UE的专用核心网辅助信息；
发送模块，用于若UE的专用核心网辅助信息与移动管理网元所服务的专用核心网不匹配，则向UE发送请求消息，请求消息用于指示UE重新发起接入请求，请求消息中携带UE的专用核心网辅助信息。
在第三方面的一种可能的实施方式中，确定模块具体用于：
根据UE签约的使用类型和如下信息中的至少一种确定UE的专用核心网辅助信息：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
在第三方面的一种可能的实施方式中，发送模块还用于：若UE处于空闲态，在向UE发送请求消息之前，向UE发送寻呼消息，以使UE变为连接态。
在第三方面的一种可能的实施方式中，发送模块具体用于：
发送临时身份标识重分配请求消息给UE，临时身份标识重分配请求消息中携带非广播位置区域标识和UE的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
在第三方面的一种可能的实施方式中，发送模块具体用于：
发送连接释放命令消息给UE的服务基站，连接释放命令消息中携带原因值和UE的专用核心网辅助信息；连接释放命令消息用于指示基站将原因值和UE的专用核心网辅助信息携带在无线资源控制RRC连接释放消息中发送给UE，原因值用于指示UE重新发起接入请求。
在第三方面的一种可能的实施方式中，发送模块具体用于：
发送分离请求消息给UE，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求。
在第三方面的一种可能的实施方式中，UE重新发起的接入请求，包括：附着请求或者位置更新请求。
在第三方面的一种可能的实施方式中，UE的专用核心网辅助信息包括：移动管理网元的专用核心网类型和/或UE签约的使用类型。
上述第三方面所提供的移动管理网元，其有益效果可以参见上述第一方面所带来的有益效果，在此不再赘述。
第四方面，本发明实施例提供一种用户设备UE，包括：
接收模块，用于接收移动管理网元发送的请求消息，请求消息用于指示UE重新发起接入请求，请求消息中携带移动管理网元为UE确定的专用核心网辅助信息；
发送模块，用于根据请求消息发送接入请求消息，并将专用核心网辅助信息携带在接入请求消息触发的无线资源控制RRC连接建立请求消息中发送给UE的服务基站，专用核心网辅助信息用于基站为UE选择与专用核心网辅助信息对应的专用核心网。
在第四方面的一种可能的实施方式中，UE还包括：
存储模块，用于保存专用核心网辅助信息，并关联专用核心网辅助信息与UE的服务网络。
在第四方面的一种可能的实施方式中，专用核心网辅助信息是移动管理网元根据UE签约的使用类型和如下信息中的至少一种确定的：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
在第四方面的一种可能的实施方式中，接收模块还用于：
接收移动管理网元发送的寻呼消息，并通过发送模块发送寻呼响应消息与移动管理网元建立连接。
在第四方面的一种可能的实施方式中，接收模块具体用于：
接收移动管理网元发送的临时身份标识重分配请求消息，临时身份标识重分配请求消息中携带非广播位置区域标识和UE的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
在第四方面的一种可能的实施方式中，接收模块具体用于：
接收基站发送的无线资源控制RRC连接释放消息，RRC连接释放消息 中携带原因值和UE的专用核心网辅助信息；RRC连接释放消息是基站接收到移动管理网元发送的连接释放命令消息后发送的，连接释放命令消息中携带原因值和UE的专用核心网辅助信息，原因值用于指示UE重新发起接入请求。
在第四方面的一种可能的实施方式中，接收模块具体用于：
接收移动管理网元发送的分离请求消息，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求。
在第四方面的一种可能的实施方式中，接入请求消息包括：附着请求或者位置更新请求。
在第四方面的一种可能的实施方式中，UE的专用核心网辅助信息为移动管理网元的专用核心网类型或者UE签约的使用类型。
上述第四方面所提供的UE，其有益效果可以参见上述第一方面所带来的有益效果，在此不再赘述。
第五方面，本发明实施例提供一种移动管理网元，包括：
处理器，用于获取用户设备UE签约的使用类型；并根据UE签约的使用类型，确定UE的专用核心网辅助信息；
发送器，用于若UE的专用核心网辅助信息与移动管理网元所服务的专用核心网不匹配，则向UE发送请求消息，请求消息用于指示UE重新发起接入请求，请求消息中携带UE的专用核心网辅助信息。
在第五方面的一种可能的实施方式中，处理器具体用于：
根据UE签约的使用类型和如下信息中的至少一种确定UE的专用核心网辅助信息：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
在第五方面的一种可能的实施方式中，发送器还用于：若UE处于空闲态，在向UE发送请求消息之前，向UE发送寻呼消息，以使UE变为连接态。
在第五方面的一种可能的实施方式中，发送器具体用于：
向UE发送临时身份标识重分配请求消息，临时身份标识重分配请求消息中携带非广播位置区域标识和UE的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
在第五方面的一种可能的实施方式中，发送器具体用于：
向UE的服务基站发送连接释放命令消息，连接释放命令消息中携带原因值和UE的专用核心网辅助信息；连接释放命令消息用于指示基站将原因值和UE的专用核心网辅助信息携带在无线资源控制RRC连接释放消息中发送给UE，原因值用于指示UE重新发起接入请求。
在第五方面的一种可能的实施方式中，发送器具体用于：
向UE发送分离请求消息，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求。
在第五方面的一种可能的实施方式中，UE重新发起的接入请求，包括：附着请求或者位置更新请求。
在第五方面的一种可能的实施方式中，UE的专用核心网辅助信息包括：移动管理网元的专用核心网类型和/或UE签约的使用类型。
上述第五方面所提供的移动管理网元，其有益效果可以参见上述第一方面所带来的有益效果，在此不再赘述。
第六方面，本发明实施例提供一种用户设备UE，包括：
接收器，用于接收移动管理网元发送的请求消息，请求消息用于指示UE重新发起接入请求，请求消息中携带移动管理网元为UE确定的专用核心网辅助信息；
发送器，用于根据请求消息发送接入请求消息，并将专用核心网辅助信息携带在接入请求消息触发的无线资源控制RRC连接建立请求消息中发送给UE的服务基站，专用核心网辅助信息用于基站为UE选择与专用核心网辅助信息对应的专用核心网。
在第六方面的一种可能的实施方式中，UE还包括：存储器和处理器，存储器用于保存专用核心网辅助信息；处理器用于关联专用核心网辅助信息与UE的服务网络。
在第六方面的一种可能的实施方式中，专用核心网辅助信息是移动管理网元根据UE签约的使用类型和如下信息中的至少一种确定的：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
在第六方面的一种可能的实施方式中，接收器还用于：
接收移动管理网元发送的寻呼消息，并通过发送器发送寻呼响应消息与移动管理网元建立连接。
在第六方面的一种可能的实施方式中，接收器具体用于：
接收移动管理网元发送的临时身份标识重分配请求消息，临时身份标识重分配请求消息中携带非广播位置区域标识和UE的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
在第六方面的一种可能的实施方式中，接收器具体用于：
接收基站发送的无线资源控制RRC连接释放消息，RRC连接释放消息中携带原因值和UE的专用核心网辅助信息；RRC连接释放消息是基站接收到移动管理网元发送的连接释放命令消息后发送的，连接释放命令消息中携带原因值和UE的专用核心网辅助信息，原因值用于指示UE重新发起接入请求。
在第六方面的一种可能的实施方式中，接收器具体用于：
接收移动管理网元发送的分离请求消息，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求。
在第六方面的一种可能的实施方式中，接入请求消息包括：附着请求或者位置更新请求。
在第六方面的一种可能的实施方式中，UE的专用核心网辅助信息为移动管理网元的专用核心网类型或者UE签约的使用类型。
上述第六方面所提供的UE，其有益效果可以参见上述第一方面所带来的有益效果，在此不再赘述。
第七方面，本发明实施例提供一种专用核心网迁移处理***，包括：上述第三方面提供的移动管理网元和上述第四方面提供的用户设备UE。
第八方面，本发明实施例提供一种专用核心网迁移处理***，包括：上述第五方面提供的移动管理网元和上述第六方面提供的用户设备UE。
上述第七方面和第八方面所提供的***，其有益效果可以参见上述第一方面所带来的有益效果，在此不再赘述。
本实施例提供的专用核心网迁移处理方法、设备和***，当UE签约的使用类型改变时，移动管理网元获取UE签约的使用类型，并根据该使用类 型确定UE的专用核心网辅助信息后，在请求UE重新发起接入流程时，就将该专用核心网辅助信息发送给UE，从而UE可以在发起接入流程时触发的RRC连接建立请求消息中，将该专用核心网辅助信息发送给基站，使得基站能够根据该专用核心网辅助信息为UE选择与专用核心网辅助信息对应的专用核心网，直接将UE迁移到能服务该UE的移动管理网元，因而避免了移动管理网元发起NAS重定向流程，节省了不必要的重定向信令开销，同时也保证了不同DCN之间的隔离性。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本发明提供的***架构示意图；
图2为本发明提供的专用核心网迁移处理方法实施例一的流程示意图；
图3为本发明提供的专用核心网迁移处理方法实施例二的流程示意图；
图4为本发明提供的专用核心网迁移处理方法实施例三的流程示意图；
图5为本发明提供的专用核心网迁移处理方法实施例四的流程示意图；
图6为本发明提供的移动管理网元实施例一的结构示意图；
图7为本发明提供的UE实施例一的结构示意图；
图8为本发明提供的移动管理网元实施例二的结构示意图；
图9为本发明提供的UE实施例二的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明实施例提供的专用核心网迁移处理方法，可以适用于2G、3G、4G 等核心网下的UE的迁移。图1为本发明提供的***架构示意图，如图1所示，***包括：用户设备UE、基站和移动管理网元(移动管理网元是CN网元的一种)，UE可以通过基站与一个或多个移动管理网元进行通信。在部署了专用核心网DCN的网络中，运营商为每个UE签约一个使用类型(usage type)，每个移动管理网元有其DCN类型(DCN type)，具有DCN类型的移动管理网元也称为DCN网元；一种DCN类型的移动管理网元可以为一种或多种使用类型的UE提供服务，同时一个UE的使用类型可以同时被多个支持不同DCN类型的DCN网元提供服务，从而DCN网元的DCN类型与UE的使用类型之间可以存在如下四种对应关系：
(1)一对一，例如：DCN类型为机器类通信的DCN网元只能为使用类型为智能电表通信的UE提供服务；或者
(2)一对多，例如：DCN类型为机器类通信的DCN网元可以同时为使用类型为智能电表通信和智能水表通信的UE提供服务；或者
(3)多对一，例如：使用类型为自动驾驶汽车通信的UE需要同时被DCN类型为机器类通信的DCN网元和DCN类型为智能汽车通信的DCN网元提供服务；
(4)多对多；例如：一个DCN网元有两种DCN类型：机器类通信和智能汽车通信，机器类通信可以同时为使用类型为智能电表通信和智能水表通信的UE提供服务；而机器类通信和智能汽车通信二者需要同时为使用类型为自动驾驶汽车通信的UE提供服务。
需要说明的是，目前具有一种较为合理的DCN部署方式：移动管理网元的DCN类型与其能服务的UE使用类型之间相互等价，即该移动管理网元的DCN类型就是所服务的UE使用类型，例如：移动管理网元可以同时为使用类型1、使用类型2和使用类型3的UE提供服务，则该移动管理网元的三种DCN类型分别为使用类型1、使用类型2和使用类型3，其中使用类型1具体可以为机器类通信，使用类型2具体可以为智能汽车通信，使用类型3具体可以为智能家居通信。
本发明实施例涉及的UE，是指向用户提供语音、短信和/或数据连通性的设备，例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该用户设备可以经无线接入网(Radio Access Network， 简称RAN)与核心网进行通信，与RAN交换语音和/或数据。该用户设备可以包括无线终端设备、移动终端设备、订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、接入点(Access Point，AP)、远程终端设备(Remote Terminal)、接入终端设备(Access Terminal)、用户终端设备(User Terminal)、用户代理(User Agent)、或用户装备(User Device)等。该用户设备还可以包括移动电话(或称为“蜂窝”电话)，具有移动终端设备的计算机，便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，例如，个人通信业务(Personal Communication Service，简称PCS)电话、无绳电话、会话发起协议(SIP)话机、无线本地环路(Wireless Local Loop，简称WLL)站、个人数字助理(Personal Digital Assistant，简称PDA)、用户单元(Subscriber Unit)、个人电脑(Personal Computer)、膝上型电脑(Laptop Computer)、平板电脑(Tablet Computer)、上网本(Netbook)、手持设备(Handheld)、数据卡(Data Card)、USB***设备、移动无线保真热点设备(WiFi Devices)、智能手表/智能眼镜等可穿戴设备(Wearable Devices)等设备。
本发明实施例所涉及的基站，可以是2G网络中的基站控制器(Base Station Controller，简称BSC)，3G网络中的无线网络控制器(Radio Network Controller，简称RNC)或基站(NodeB)，还可以是4G网络中的演进型基站(eNodeB，evolved Node B，E-UTRAN Node B)等，本申请不做特别限定。
本发明实施例所涉及的移动管理网元，可以是2G/3G网络中的移动交换中心(Mobile Switching Centre，简称MSC)/拜访位置寄存器(Visitors Location Register，简称VLR)，MSC与VLR通常合设为同一网元，称为MSC/VLR，或简称为VLR，也可以是2G/3G网络中的服务通用分组无线服务技术支持节点(Serving General Packet Radio Service Support Node，简称SGSN)，还可以是4G网络中的移动管理实体(Mobility Management Entity，简称MME)，移动管理网元还可以包括其他设备类型等，本申请不做特别限定。
本发明实施例所涉及的专用核心网迁移处理方法，旨在解决现有技术中DCN网元需要发起NAS重定向流程将UE从一个DCN网元重定向到另一个能支持UE使用类型的DCN网元，而浪费不必要的信令开销，并且影响DCN之间的隔离性的技术问题。
下面以具体地实施例对本发明的技术方案以及本发明的技术方案如何解决上述技术问题进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例中不再赘述。
图2为本发明提供的专用核心网迁移处理方法实施例一的流程示意图，如图2所示，本实施例提供的方法包括如下步骤：
S101、移动管理网元获取UE签约的使用类型。
具体的，在部署有专用核心网的网络中，运营商为具有相同通信特征的UE签约一个使用类型，例如：手持设备、智能家居、汽车等使用类型。UE的归属签约用户服务器(Home Subscriber Server，简称HSS)或归属位置寄存器(Home Location Register，简称HLR)中保存有UE签约的使用类型，当UE的使用类型发生变化时，移动管理网元可以从HSS/HLR获取更新的UE的使用类型，具体地，当HSS/HLR中签约的UE使用类型发生改变时，HSS/HLR会主动将更新后的UE使用类型通知给该UE的服务移动管理网元。
S102、移动管理网元根据UE签约的使用类型，确定UE的专用核心网辅助信息。
专用核心网辅助信息(DCN Assistance Information)，也称为专用核心网选择辅助参数(DCN Selection Assistance Parameter)，是运营商为其网络中部署的专用核心网(包括移动管理网元)分配的。一种专用核心网辅助信息所代表的移动管理网元可以为一种或多种使用类型的UE提供服务，UE的专用核心网辅助信息即为可以为其服务的移动管理网元对应的专用核心网辅助信息。
本实施例中，专用核心网辅助信息可以为：移动管理网元的DCN类型和/或UE签约的使用类型，或者其它可以表明该移动管理网元的DCN类型和/或UE签约的使用类型的信息，至于具体信息名称，本发明不做具体限定。具体的，每个移动管理网元有其DCN类型，一种DCN类型的移动管理网元可以为一种或多种使用类型的UE提供服务。如果一个移动管理网元只为一种使用类型的UE提供服务，则DCN类型也可以为UE的使用类型，此时，专用核心网辅助信息可以为DCN类型或UE的使用类型；如果一个移动管理网元为多种使用类型的UE提供服务，专用核心网辅助信息则为DCN类型。例如：DCN类型可以是机器类通信MTC，蜂窝物联网(Cellular Internet of  Things，简称CIoT)通信、移动宽带(Mobile Broadband，简称MBB)通信、车联网通信等类型，其中，车联网通信DCN可以为多种品牌(使用类型)的汽车服务。
可选的，本实施例中，移动管理网元可以根据UE签约的使用类型和如下信息中的至少一种确定UE的专用核心网辅助信息：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
具体的，移动管理网元中可以保存有运营商配置的UE的使用类型与专用核心网之间的映射关系，根据该映射关系，移动管理网元可以直接获取与UE的使用类型对应的专用核心网辅助信息。
移动管理网元也可以根据本地配置的运营商策略，获取与UE的使用类型对应的专用核心网辅助信息。例如：对于漫游的UE，运营商可以配置对应的接入策略，并根据签署的漫游协议确定该使用类型的UE可以接入的专用核心网，移动管理网元据此获取与UE的使用类型对应的专用核心网辅助信息。
移动管理网元还可以根据可用的UE的上下文信息来确定与UE的使用类型对应的专用核心网辅助信息，例如：对于使用类型为CIoT的UE，移动管理网元可以根据保存的该UE支持的CIoT控制面优化能力或用户面优化能力等上下文信息来确定该UE的专用核心网辅助信息。
S103、若UE的专用核心网辅助信息与移动管理网元所服务的专用核心网不匹配，移动管理网元向UE发送请求消息。
其中，请求消息用于指示UE重新发起接入请求，请求消息中携带UE的专用核心网辅助信息。
具体的，当UE的使用类型发生变化时，UE的专用核心网辅助信息与当前为其服务的移动管理网元所服务的专用核心网则会不匹配，也就是说，当前为UE服务的移动管理网元不能继续为该专用核心网辅助信息对应的UE服务；此时，移动管理网元可以将专用核心网辅助信息携带在请求消息中发送给UE，告知UE可以为其服务的移动管理网元所对应的专用核心网辅助信息；并请求UE重新发起接入请求，以使基站直接将UE迁移到可以为该UE服务的移动管理网元。例如：UE的使用类型从之前的品牌A智能汽车变为 品牌B智能汽车，而当前UE的服务移动管理网元的DCN类型只能为品牌A智能汽车提供服务，则移动管理网元将确定的品牌B智能汽车对应的专用核心网辅助信息品牌B车联网发送给该UE。
S104、UE接收移动管理网元发送的请求消息。
具体的，UE接收移动管理网元发送的请求消息后，则能够获知可以为其服务的移动管理网元所对应的专用核心网辅助信息，然后将该专用核心网辅助信息上报给基站。
S105、UE根据请求消息发送接入请求消息，并将专用核心网辅助信息携带在接入请求消息触发的RRC连接建立请求消息中发送给UE的服务基站。
其中，专用核心网辅助信息用于基站为UE选择与专用核心网辅助信息对应的专用核心网DCN。
具体的，UE接收到移动管理网元发送的请求消息后则会重新发起接入流程，在该接入流程中，UE需要先与服务基站建立连接，即UE在发送接入请求消息时会先触发无线资源控制(Radio Resource Control，简称RRC)连接建立请求消息。此时，UE可以将专用核心网辅助信息携带在RRC连接建立请求消息中发送给基站，以使基站根据专用核心网辅助信息选择与专用核心网辅助信息对应的专用核心网。
本实施例中，UE重新发起的接入请求可以是附着请求(Attach Request)或者位置更新请求，具体可根据移动管理网元发送的请求消息中的指示信息来决定，具体地，位置更新请求可以包括位置域更新(Location Area Updating，简称LAU)请求，路由域更新(Routing Area Updating，简称RAU)请求，或者跟踪域更新(Tracking Area Updating，简称TAU)请求。
S106、基站为UE选择与专用核心网辅助信息对应的专用核心网。
具体的，基站接收到UE发送的RRC连接建立请求消息，在与UE建立连接后，则可以根据专用核心网辅助信息选择与专用核心网辅助信息对应的专用核心网，以将UE发送的请求消息转发给可以为该专用核心网辅助信息对应的UE服务的移动管理网元，实现将UE迁移到可以为其服务的移动管理网元。
需要说明的是，基站已经保存有专用核心网辅助信息与对应的DCN网元之间的配置关系，例如：若专用核心网辅助信息为DCN类型，则基站上保存 有DCN类型1对应于DCN网元A，DCN类型2对应于DCN网元B；若专用核心网辅助信息为UE使用类型，则基站上保存有使用类型1对应于DCN网元A，使用类型2对应于DCN网元B等。
本实施例提供的专用核心网迁移处理方法，当UE签约的使用类型改变时，移动管理网元获取UE签约的使用类型，并根据该使用类型确定UE的专用核心网辅助信息后，在请求UE重新发起接入流程时，将该专用核心网辅助信息发送给UE，从而UE可以在重新发起接入流程时触发的RRC连接建立请求消息中，将该专用核心网辅助信息发送给服务基站，使得基站能够根据该专用核心网辅助信息为UE选择与专用核心网辅助信息对应的专用核心网，直接将UE迁移到能服务该UE更新后的使用类型的移动管理网元，从而避免了移动管理网元发起NAS重定向流程，节省了不必要的重定向信令开销，同时也保证了不同DCN之间的隔离性。
图3为本发明提供的专用核心网迁移处理方法实施例二的流程示意图，本实施例是对上述图2所示实施例中步骤S103的一种具体的实现方式的详细说明，如图3所示，本实施例提供的方法包括如下步骤：
S201、移动管理网元获取UE签约的使用类型。
该步骤可参考上述图2所示实施例对应步骤的描述，在此不在赘述。
S202、移动管理网元根据UE签约的使用类型，确定UE的专用核心网辅助信息，若UE的专用核心网辅助信息与移动管理网元所服务的专用核心网不匹配，且UE处于空闲态，则执行步骤S203与S204；若UE处于连接态，则跳过步骤S203与S204而直接执行步骤S205。
该步骤可参考上述图2所示实施例对应步骤的描述，在此不在赘述。
S203、移动管理网元向UE发送寻呼消息。
该步骤为现有技术，在此不在赘述。
S204、UE接收寻呼消息，并发送寻呼响应消息与移动管理网元建立连接，变为连接态。
该步骤为现有技术，在此不在赘述。
S205、移动管理网元向UE发送临时身份标识重分配请求消息。
其中，临时身份标识重分配请求消息中携带非广播位置区域标识和UE 的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
具体的，在4G网络中，临时身份标识重分配请求消息可以是UE的全球唯一临时标识(Globally Unique Temporary Identity，简称GUTI)重分配命令(GUTI REALLOCATION COMMAND)消息，在2G/3G网络中，临时身份标识重分配请求消息可以是临时移动用户标识(Temporary Mobile Subscriber Identity，简称TMSI)重分配命令(TMSI REALLOCATION COMMAND)消息，或者分组临时移动用户标识(Packet Temporary Mobile Subscriber Identity，简称P-TMSI)重分配命令(P-TMSI REALLOCATION COMMAND)消息等。
对应地，在4G网络中，临时身份标识重分配请求消息中携带的非广播位置区域标识具体为非广播跟踪域标识(non-broadcast Tracking Area Identity，简称non-broadcast TAI)，在2G/3G网络中，临时身份标识重分配请求消息中携带的非广播位置区域标识具体为非广播位置域标识(non-broadcast Location Area Identity，简称non-broadcast LAI)或非广播路由域标识(non-broadcast Routing Area Identity，简称non-broadcast RAI)，该标识用于指示UE重新发起接入请求，此时，UE重新发起的接入请求具体为位置更新请求。
S206、UE接收移动管理网元发送的临时身份标识重分配请求消息。
S207、UE保存专用核心网辅助信息，并关联专用核心网辅助信息与UE的服务网络。
具体的，UE接收移动管理网元发送的请求消息后，则会获知可以为其服务的移动管理网元所对应的专用核心网辅助信息；此时，UE可以保存该专用核心网辅助信息，并关联专用核心网辅助信息与UE当前服务公共陆地移动网络(Public Land Mobile Network，简称PLMN)，即当前服务PLMN中为UE提供服务的移动管理网元为该专用核心网辅助信息对应的DCN网元，实现专用核心网辅助信息的更新，以便UE后续在该服务PLMN发起接入请求时上报更新后的专用核心网辅助信息。
S208、UE发送接入请求消息，并将专用核心网辅助信息携带在接入请求消息触发的RRC连接建立请求消息中发送给UE的服务基站。
具体的，UE接收到移动管理网元发送的临时身份标识重分配请求消息后 则会发起位置更新流程，在该流程中，UE将专用核心网辅助信息携带在RRC连接建立请求消息中发送给服务基站。
S209、基站为UE选择与专用核心网辅助信息对应的专用核心网DCN。
该步骤可参考上述图2所示实施例对应步骤的描述，在此不在赘述。
图4为本发明提供的专用核心网迁移处理方法实施例三的流程示意图，本实施例是对上述图2所示实施例中步骤S103的另一种具体的实现方式的详细说明，如图4所示，本实施例提供的方法包括如下步骤：
S301、移动管理网元获取UE签约的使用类型。
该步骤可参考上述图2所示实施例对应步骤的描述，在此不在赘述。
S302、移动管理网元根据UE签约的使用类型，确定UE的专用核心网辅助信息，若UE的专用核心网辅助信息与移动管理网元所服务的专用核心网不匹配，且UE处于空闲态，则执行步骤S303与S304；若UE处于连接态，则跳过步骤S303与S304而直接执行步骤S305。
该步骤可参考上述图2所示实施例对应步骤的描述，在此不在赘述。
S303、移动管理网元向UE发送寻呼消息。
该步骤为现有技术，在此不在赘述。
S304、UE接收寻呼消息，并发送寻呼响应消息与移动管理网元建立连接，变为连接态。
该步骤为现有技术，在此不在赘述。
S305、移动管理网元向UE的服务基站发送连接释放命令消息。
其中，连接释放命令消息中携带原因值和UE的专用核心网辅助信息，连接释放命令消息用于指示基站将原因值和UE的专用核心网辅助信息携带在无线资源控制RRC连接释放消息中发送给UE，原因值用于指示UE重新发起接入请求。
具体的，连接释放命令消息(Release Command)可以是UE上下文连接释放命令消息(UE Context Release Command)，也可以是Iu连接释放命令消息(Iu Release Command)。
移动管理网元发送连接释放命令消息时，会在消息中携带原因值；本实施例中，该原因值例如可以是DCN重选，以指示UE重新发起接入请求实现 DCN的重选，也可以是其它用来指示UE因为需要进行DCN重选而需要发起重新接入的原因值。
S306、基站将原因值和UE的专用核心网辅助信息携带在RRC连接释放消息中发送给UE。
具体的，基站接收到连接释放命令消息后，就会向UE发送RRC连接释放消息(RRC connection release)，通过RRC连接释放消息，基站可以将上述原因值转发给UE，指示UE重新发起接入请求。此时，UE重新发起的接入请求具体为位置更新请求。
S307、UE接收基站发送的RRC连接释放消息。
该步骤为现有技术，在此不在赘述。
S308、UE保存专用核心网辅助信息，并关联专用核心网辅助信息与UE的服务网络。
该步骤可参考上述图3所示实施例对应步骤的描述，在此不在赘述。
S309、UE发送接入请求消息，并将专用核心网辅助信息携带在接入请求消息触发的RRC连接建立请求消息中发送给UE的服务基站。
具体的，UE接收到移动管理网元发送的RRC连接释放消息后会根据原因值发起位置更新流程，在该流程中，UE将专用核心网辅助信息携带在RRC连接建立请求消息中发送给基站。
S310、基站为UE选择与专用核心网辅助信息对应的专用核心网。
该步骤可参考上述图2所示实施例对应步骤的描述，在此不在赘述。
图5为本发明提供的专用核心网迁移处理方法实施例四的流程示意图，本实施例是对上述图2所示实施例中步骤S103的又一种具体的实现方式的详细说明，如图5所示，本实施例提供的方法包括如下步骤：
S401、移动管理网元获取UE签约的使用类型。
该步骤可参考上述图2所示实施例对应步骤的描述，在此不在赘述。
S402、移动管理网元根据UE签约的使用类型，确定UE的专用核心网辅助信息，若UE的专用核心网辅助信息与移动管理网元所服务的专用核心网不匹配，且UE处于空闲态，则执行步骤S403与S404；若UE处于连接态，则跳过步骤S403与S404而直接执行步骤S405。
该步骤可参考上述图2所示实施例对应步骤的描述，在此不在赘述。
S403、移动管理网元向UE发送寻呼消息。
该步骤为现有技术，在此不在赘述。
S404、UE接收寻呼消息，并发送寻呼响应消息与移动管理网元建立连接。
该步骤为现有技术，在此不在赘述。
S405、移动管理网元向UE发送分离请求消息。
其中，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求(具体为附着请求)。
S406、UE接收移动管理网元发送的分离请求消息。
该步骤为现有技术，在此不在赘述。
S407、UE保存专用核心网辅助信息，并关联专用核心网辅助信息与UE的服务网络。
该步骤可参考上述图3所示实施例对应步骤的描述，在此不在赘述。
S408、UE发送接入请求消息，并将专用核心网辅助信息携带在接入请求消息触发的RRC连接建立请求消息中发送给UE的服务基站。
具体的，UE接收到移动管理网元发送的分离请求消息后则会发起附着流程，在该流程中，UE将专用核心网辅助信息携带在RRC连接建立请求消息中发送给基站。
S409、基站为UE选择与专用核心网辅助信息对应的专用核心网。
该步骤可参考上述图2所示实施例对应步骤的描述，在此不在赘述。
图6为本发明提供的移动管理网元实施例一的结构示意图，如图6所示，本实施例中的移动管理网元100包括：
获取模块110，用于获取用户设备UE签约的使用类型；
确定模块120，用于根据UE签约的使用类型，确定UE的专用核心网辅助信息；
发送模块130，用于若UE的专用核心网辅助信息与移动管理网元所服务的专用核心网不匹配，则向UE发送请求消息，请求消息用于指示UE重新发起接入请求，请求消息中携带UE的专用核心网辅助信息。
作为本发明实施例一种具体的实施方式，确定模块120具体用于：根据 UE签约的使用类型和如下信息中的至少一种确定UE的专用核心网辅助信息：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
可选的，发送模块130还用于：若UE处于空闲态，在向UE发送请求消息之前，向UE发送寻呼消息，以使UE变为连接态。
作为本发明实施例第一种可能的实施方式，发送模块130具体用于：向UE发送临时身份标识重分配请求消息，临时身份标识重分配请求消息中携带非广播位置区域标识和UE的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
作为本发明实施例第二种可能的实施方式，发送模块130具体用于：向UE的服务基站发送连接释放命令消息，连接释放命令消息中携带原因值和UE的专用核心网辅助信息；连接释放命令消息用于指示基站将原因值和UE的专用核心网辅助信息携带在无线资源控制RRC连接释放消息中发送给UE，原因值用于指示UE重新发起接入请求。
作为本发明实施例第三种可能的实施方式，发送模块130具体用于：向UE发送分离请求消息，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求。
本实施例中，可选的，UE重新发起的接入请求，包括：附着请求或者位置更新请求。
UE的专用核心网辅助信息包括：移动管理网元的专用核心网类型和/或UE签约的使用类型。
本实施例提供的移动管理网元，可以执行上述方法实施例，其实现原理和技术效果类似，此处不再赘述。
图7为本发明提供的UE实施例一的结构示意图，如图7所示，本实施例中的UE200包括：
接收模块210，用于接收移动管理网元发送的请求消息，请求消息用于指示UE重新发起接入请求，请求消息中携带移动管理网元为UE确定的专用核心网辅助信息；
发送模块220，用于根据请求消息发送接入请求消息，并将专用核心网 辅助信息携带在接入请求消息触发的无线资源控制RRC连接建立请求消息中发送给UE的服务基站，专用核心网辅助信息用于基站为UE选择与专用核心网辅助信息对应的专用核心网。
可选的，本实施例中，UE200还包括：存储模块230，用于保存专用核心网辅助信息，并关联专用核心网辅助信息与UE的服务网络。
作为本发明实施例一种具体的实施方式，专用核心网辅助信息是移动管理网元根据UE签约的使用类型和如下信息中的至少一种确定的：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
可选的，接收模块210还用于：接收移动管理网元发送的寻呼消息，并通过发送模块220发送寻呼响应消息与移动管理网元建立连接。
作为本发明实施例第一种可能的实施方式，接收模块210具体用于：接收移动管理网元发送的临时身份标识重分配请求消息，临时身份标识重分配请求消息中携带非广播位置区域标识和UE的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
作为本发明实施例第二种可能的实施方式，接收模块210具体用于：接收基站发送的无线资源控制RRC连接释放消息，RRC连接释放消息中携带原因值和UE的专用核心网辅助信息；RRC连接释放消息是基站接收到移动管理网元发送的连接释放命令消息后发送的，连接释放命令消息中携带原因值和UE的专用核心网辅助信息，原因值用于指示UE重新发起接入请求。
作为本发明实施例第三种可能的实施方式，接收模块210具体用于：接收移动管理网元发送的分离请求消息，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求。
本实施例中，可选的，接入请求消息包括：附着请求或者位置更新请求。
UE的专用核心网辅助信息可以为移动管理网元的专用核心网类型或者UE签约的使用类型。
本发明实施例提供的UE，可以执行上述方法实施例，其实现原理和技术效果类似，此处不再赘述。
图8为本发明提供的移动管理网元实施例二的结构示意图，如图8所示，本实施例中的移动管理网元300包括：处理器310、存储器320和发送器330。
存储器320可以包括只读存储器和随机存取存储器，并向处理器310提供指令和数据。
本实施例中，通过调用存储器320存储的程序或指令，处理器310用于获取用户设备UE签约的使用类型；并根据UE签约的使用类型，确定UE的专用核心网辅助信息；
发送器330，用于若UE的专用核心网辅助信息与移动管理网元所服务的专用核心网不匹配，则向UE发送请求消息，请求消息用于指示UE重新发起接入请求，请求消息中携带UE的专用核心网辅助信息。
作为本发明实施例一种具体的实施方式，处理器310具体用于：根据UE签约的使用类型和如下信息中的至少一种确定UE的专用核心网辅助信息：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
可选的，发送器330还用于：若UE处于空闲态，在向UE发送请求消息之前，向UE发送寻呼消息，以使UE变为连接态。
作为本发明实施例第一种可能的实施方式，发送器330具体用于：向UE发送临时身份标识重分配请求消息，临时身份标识重分配请求消息中携带非广播位置区域标识和UE的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
作为本发明实施例第二种可能的实施方式，发送器330具体用于：向UE的服务基站发送连接释放命令消息，连接释放命令消息中携带原因值和UE的专用核心网辅助信息；连接释放命令消息用于指示基站将原因值和UE的专用核心网辅助信息携带在无线资源控制RRC连接释放消息中发送给UE，原因值用于指示UE重新发起接入请求。
作为本发明实施例第三种可能的实施方式，发送器330具体用于：向UE发送分离请求消息，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求。
本实施例中，可选的，UE重新发起的接入请求，包括：附着请求或者位置更新请求。
UE的专用核心网辅助信息包括：移动管理网元的专用核心网类型和/或UE签约的使用类型。
本实施例提供的移动管理网元，可以执行上述方法实施例，其实现原理和技术效果类似，此处不再赘述。
图9为本发明提供的UE实施例二的结构示意图，如图9所示，本实施例中的UE400包括：处理器410、存储器420、接收器430和发送器440。
存储器420可以包括只读存储器和随机存取存储器，并向处理器410提供指令和数据。
本实施例中，接收器430，用于接收移动管理网元发送的请求消息，请求消息用于指示UE重新发起接入请求，请求消息中携带移动管理网元为UE确定的专用核心网辅助信息；
发送器440，用于根据请求消息发送接入请求消息，并将专用核心网辅助信息携带在接入请求消息触发的无线资源控制RRC连接建立请求消息中发送给UE的服务基站，专用核心网辅助信息用于基站为UE选择与专用核心网辅助信息对应的专用核心网。
可选的，本实施例中，UE400还包括：存储器420，用于保存专用核心网辅助信息；通过调用存储器420存储的程序或指令，处理器410用于关联专用核心网辅助信息与UE的服务网络。
作为本发明实施例一种具体的实施方式，专用核心网辅助信息是移动管理网元根据UE签约的使用类型和如下信息中的至少一种确定的：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、UE的上下文信息。
可选的，接收器430还用于：接收移动管理网元发送的寻呼消息，并通过发送器440发送寻呼响应消息与移动管理网元建立连接。
作为本发明实施例第一种可能的实施方式，接收器430具体用于：接收移动管理网元发送的临时身份标识重分配请求消息，临时身份标识重分配请求消息中携带非广播位置区域标识和UE的专用核心网辅助信息，非广播位置区域标识用于指示UE重新发起接入请求。
作为本发明实施例第二种可能的实施方式，接收器430具体用于：接收 基站发送的无线资源控制RRC连接释放消息，RRC连接释放消息中携带原因值和UE的专用核心网辅助信息；RRC连接释放消息是基站接收到移动管理网元发送的连接释放命令消息后发送的，连接释放命令消息中携带原因值和UE的专用核心网辅助信息，原因值用于指示UE重新发起接入请求。
作为本发明实施例第三种可能的实施方式，接收器430具体用于：接收移动管理网元发送的分离请求消息，分离请求消息中携带重新附着分离类型和UE的专用核心网辅助信息，重新附着分离类型用于指示UE重新发起接入请求。
本实施例中，可选的，接入请求消息包括：附着请求或者位置更新请求。
UE的专用核心网辅助信息可以为移动管理网元的专用核心网类型或者UE签约的使用类型。
本发明实施例提供的UE，可以执行上述方法实施例，其实现原理和技术效果类似，此处不再赘述。
本发明一实施例提供一种专用核心网迁移处理***，该***包括：上述图6所示实施例中的移动管理网元和上述图7所示实施例中的用户设备UE。
本发明一实施例还提供一种专用核心网迁移处理***，该***包括：上述图8所示实施例中的移动管理网元和上述图9所示实施例中的用户设备UE。
具体的，移动管理网元和UE为至少一个，该***可以执行上述方法实施例，其实现原理和技术效果类似，此处不再赘述。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (53)

  1. 一种专用核心网迁移处理方法，其特征在于，包括：
    移动管理网元获取用户设备UE签约的使用类型；
    所述移动管理网元根据所述UE签约的使用类型，确定所述UE的专用核心网辅助信息；
    若所述UE的专用核心网辅助信息与所述移动管理网元所服务的专用核心网不匹配，所述移动管理网元向所述UE发送请求消息，所述请求消息用于指示所述UE重新发起接入请求，所述请求消息中携带所述UE的专用核心网辅助信息。
  2. 根据权利要求1所述的方法，其特征在于，所述根据所述UE签约的使用类型，确定所述UE的专用核心网辅助信息，包括：
    所述移动管理网元根据所述UE签约的使用类型和如下信息中的至少一种确定所述UE的专用核心网辅助信息：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、所述UE的上下文信息。
  3. 根据权利要求1或2所述的方法，其特征在于，若所述UE处于空闲态，在所述移动管理网元向所述UE发送请求消息之前，所述方法还包括：
    所述移动管理网元向所述UE发送寻呼消息，以使所述UE变为连接态。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述移动管理网元向所述UE发送请求消息，具体包括：
    所述移动管理网元向所述UE发送临时身份标识重分配请求消息，所述临时身份标识重分配请求消息中携带非广播位置区域标识和所述UE的专用核心网辅助信息，所述非广播位置区域标识用于指示所述UE重新发起接入请求。
  5. 根据权利要求1-3任一项所述的方法，其特征在于，所述移动管理网元向所述UE发送请求消息，具体包括：
    所述移动管理网元向所述UE的服务基站发送连接释放命令消息，所述连接释放命令消息中携带原因值和所述UE的专用核心网辅助信息；所述连接释放命令消息用于指示所述基站将所述原因值和所述UE的专用核心网辅助信息携带在无线资源控制RRC连接释放消息中发送给所述UE，所述原因值用于指示所述UE重新发起接入请求。
  6. 根据权利要求1-3任一项所述的方法，其特征在于，所述移动管理网元向所述UE发送请求消息，具体包括：
    所述移动管理网元向所述UE发送分离请求消息，所述分离请求消息中携带重新附着分离类型和所述UE的专用核心网辅助信息，所述重新附着分离类型用于指示所述UE重新发起接入请求。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述UE重新发起的接入请求，包括：附着请求或者位置更新请求。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述UE的专用核心网辅助信息包括：所述移动管理网元的专用核心网类型和/或所述UE签约的使用类型。
  9. 一种专用核心网迁移处理方法，其特征在于，包括：
    用户设备UE接收移动管理网元发送的请求消息，所述请求消息用于指示所述UE重新发起接入请求，所述请求消息中携带所述移动管理网元为所述UE确定的专用核心网辅助信息；
    所述UE根据所述请求消息发送接入请求消息，并将所述专用核心网辅助信息携带在所述接入请求消息触发的无线资源控制RRC连接建立请求消息中发送给所述UE的服务基站，所述专用核心网辅助信息用于所述基站为所述UE选择与所述专用核心网辅助信息对应的专用核心网。
  10. 根据权利要求9所述的方法，其特征在于，还包括：所述UE保存所述专用核心网辅助信息，并关联所述专用核心网辅助信息与所述UE的服务网络。
  11. 根据权利要求9或10所述的方法，其特征在于，所述专用核心网辅助信息是所述移动管理网元根据所述UE签约的使用类型和如下信息中的至少一种确定的：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、所述UE的上下文信息。
  12. 根据权利要求9-11任一项所述的方法，其特征在于，若所述UE处于空闲态，在所述UE接收移动管理网元发送的请求消息之前，所述方法还包括：
    所述UE接收所述移动管理网元发送的寻呼消息，并发送寻呼响应消息与所述移动管理网元建立连接。
  13. 根据权利要求9-12任一项所述的方法，其特征在于，所述UE接收移动管理网元发送的请求消息，具体包括：
    所述UE接收所述移动管理网元发送的临时身份标识重分配请求消息，所述临时身份标识重分配请求消息中携带非广播位置区域标识和所述UE的专用核心网辅助信息，所述非广播位置区域标识用于指示所述UE重新发起接入请求。
  14. 根据权利要求9-12任一项所述的方法，其特征在于，所述UE接收移动管理网元发送的请求消息，具体包括：
    所述UE接收所述基站发送的无线资源控制RRC连接释放消息，所述RRC连接释放消息中携带原因值和所述UE的专用核心网辅助信息；所述RRC连接释放消息是所述基站接收到所述移动管理网元发送的连接释放命令消息后发送的，所述连接释放命令消息中携带所述原因值和所述UE的专用核心网辅助信息，所述原因值用于指示所述UE重新发起接入请求。
  15. 根据权利要求9-12任一项所述的方法，其特征在于，所述UE接收移动管理网元发送的请求消息，具体包括：
    所述UE接收所述移动管理网元发送的分离请求消息，所述分离请求消息中携带重新附着分离类型和所述UE的专用核心网辅助信息，所述重新附着分离类型用于指示所述UE重新发起接入请求。
  16. 根据权利要求9-15任一项所述的方法，其特征在于，所述接入请求消息包括：附着请求或者位置更新请求。
  17. 根据权利要求9-16任一项所述的方法，其特征在于，所述UE的专用核心网辅助信息为所述移动管理网元的专用核心网类型或者所述UE签约的使用类型。
  18. 一种移动管理网元，其特征在于，包括：
    获取模块，用于获取用户设备UE签约的使用类型；
    确定模块，用于根据所述UE签约的使用类型，确定所述UE的专用核心网辅助信息；
    发送模块，用于若所述UE的专用核心网辅助信息与所述移动管理网元所服务的专用核心网不匹配，则向所述UE发送请求消息，所述请求消息用于指示所述UE重新发起接入请求，所述请求消息中携带所述UE的专用核心 网辅助信息。
  19. 根据权利要求18所述的移动管理网元，其特征在于，所述确定模块具体用于：
    根据所述UE签约的使用类型和如下信息中的至少一种确定所述UE的专用核心网辅助信息：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、所述UE的上下文信息。
  20. 根据权利要求18或19所述的移动管理网元，其特征在于，所述发送模块还用于：若所述UE处于空闲态，在向所述UE发送请求消息之前，向所述UE发送寻呼消息，以使所述UE变为连接态。
  21. 根据权利要求18-20任一项所述的移动管理网元，其特征在于，所述发送模块具体用于：
    向所述UE发送临时身份标识重分配请求消息，所述临时身份标识重分配请求消息中携带非广播位置区域标识和所述UE的专用核心网辅助信息，所述非广播位置区域标识用于指示所述UE重新发起接入请求。
  22. 根据权利要求18-20任一项所述的移动管理网元，其特征在于，所述发送模块具体用于：
    向所述UE的服务基站发送连接释放命令消息，所述连接释放命令消息中携带原因值和所述UE的专用核心网辅助信息；所述连接释放命令消息用于指示所述基站将所述原因值和所述UE的专用核心网辅助信息携带在无线资源控制RRC连接释放消息中发送给所述UE，所述原因值用于指示所述UE重新发起接入请求。
  23. 根据权利要求18-20任一项所述的移动管理网元，其特征在于，所述发送模块具体用于：
    向所述UE发送分离请求消息，所述分离请求消息中携带重新附着分离类型和所述UE的专用核心网辅助信息，所述重新附着分离类型用于指示所述UE重新发起接入请求。
  24. 根据权利要求18-23任一项所述的移动管理网元，其特征在于，所述UE重新发起的接入请求，包括：附着请求或者位置更新请求。
  25. 根据权利要求18-24任一项所述的移动管理网元，其特征在于，所述UE的专用核心网辅助信息包括：所述移动管理网元的专用核心网类型和/ 或所述UE签约的使用类型。
  26. 一种用户设备UE，其特征在于，包括：
    接收模块，用于接收移动管理网元发送的请求消息，所述请求消息用于指示所述UE重新发起接入请求，所述请求消息中携带所述移动管理网元为所述UE确定的专用核心网辅助信息；
    发送模块，用于根据所述请求消息发送接入请求消息，并将所述专用核心网辅助信息携带在所述接入请求消息触发的无线资源控制RRC连接建立请求消息中发送给所述UE的服务基站，所述专用核心网辅助信息用于所述基站为所述UE选择与所述专用核心网辅助信息对应的专用核心网。
  27. 根据权利要求26所述的UE，其特征在于，还包括：
    存储模块，用于保存所述专用核心网辅助信息，并关联所述专用核心网辅助信息与所述UE的服务网络。
  28. 根据权利要求26或27所述的UE，其特征在于，所述专用核心网辅助信息是所述移动管理网元根据所述UE签约的使用类型和如下信息中的至少一种确定的：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、所述UE的上下文信息。
  29. 根据权利要求26-28任一项所述的UE，其特征在于，所述接收模块还用于：
    接收所述移动管理网元发送的寻呼消息，并通过所述发送模块发送寻呼响应消息与所述移动管理网元建立连接。
  30. 根据权利要求26-29任一项所述的UE，其特征在于，所述接收模块具体用于：
    接收所述移动管理网元发送的临时身份标识重分配请求消息，所述临时身份标识重分配请求消息中携带非广播位置区域标识和所述UE的专用核心网辅助信息，所述非广播位置区域标识用于指示所述UE重新发起接入请求。
  31. 根据权利要求26-29任一项所述的UE，其特征在于，所述接收模块具体用于：
    接收所述基站发送的无线资源控制RRC连接释放消息，所述RRC连接释放消息中携带原因值和所述UE的专用核心网辅助信息；所述RRC连接释放消息是所述基站接收到所述移动管理网元发送的连接释放命令消息后发送 的，所述连接释放命令消息中携带所述原因值和所述UE的专用核心网辅助信息，所述原因值用于指示所述UE重新发起接入请求。
  32. 根据权利要求26-29任一项所述的UE，其特征在于，所述接收模块具体用于：
    接收所述移动管理网元发送的分离请求消息，所述分离请求消息中携带重新附着分离类型和所述UE的专用核心网辅助信息，所述重新附着分离类型用于指示所述UE重新发起接入请求。
  33. 根据权利要求26-32任一项所述的UE，其特征在于，所述接入请求消息包括：附着请求或者位置更新请求。
  34. 根据权利要求26-33任一项所述的UE，其特征在于，所述UE的专用核心网辅助信息为所述移动管理网元的专用核心网类型或者所述UE签约的使用类型。
  35. 一种移动管理网元，其特征在于，包括：
    处理器，用于获取用户设备UE签约的使用类型；并根据所述UE签约的使用类型，确定所述UE的专用核心网辅助信息；
    发送器，用于若所述UE的专用核心网辅助信息与所述移动管理网元所服务的专用核心网不匹配，则向所述UE发送请求消息，所述请求消息用于指示所述UE重新发起接入请求，所述请求消息中携带所述UE的专用核心网辅助信息。
  36. 根据权利要求35所述的移动管理网元，其特征在于，所述处理器具体用于：
    根据所述UE签约的使用类型和如下信息中的至少一种确定所述UE的专用核心网辅助信息：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、所述UE的上下文信息。
  37. 根据权利要求35或36所述的移动管理网元，其特征在于，所述发送器还用于：若所述UE处于空闲态，在向所述UE发送请求消息之前，向所述UE发送寻呼消息，以使所述UE变为连接态。
  38. 根据权利要求35-37任一项所述的移动管理网元，其特征在于，所述发送器具体用于：
    向所述UE发送临时身份标识重分配请求消息，所述临时身份标识重分 配请求消息中携带非广播位置区域标识和所述UE的专用核心网辅助信息，所述非广播位置区域标识用于指示所述UE重新发起接入请求。
  39. 根据权利要求35-37任一项所述的移动管理网元，其特征在于，所述发送器具体用于：
    向所述UE的服务基站发送连接释放命令消息，所述连接释放命令消息中携带原因值和所述UE的专用核心网辅助信息；所述连接释放命令消息用于指示所述基站将所述原因值和所述UE的专用核心网辅助信息携带在无线资源控制RRC连接释放消息中发送给所述UE，所述原因值用于指示所述UE重新发起接入请求。
  40. 根据权利要求35-37任一项所述的移动管理网元，其特征在于，所述发送器具体用于：
    向所述UE发送分离请求消息，所述分离请求消息中携带重新附着分离类型和所述UE的专用核心网辅助信息，所述重新附着分离类型用于指示所述UE重新发起接入请求。
  41. 根据权利要求35-40任一项所述的移动管理网元，其特征在于，所述UE重新发起的接入请求，包括：附着请求或者位置更新请求。
  42. 根据权利要求35-41任一项所述的移动管理网元，其特征在于，所述UE的专用核心网辅助信息包括：所述移动管理网元的专用核心网类型和/或所述UE签约的使用类型。
  43. 一种用户设备UE，其特征在于，包括：
    接收器，用于接收移动管理网元发送的请求消息，所述请求消息用于指示所述UE重新发起接入请求，所述请求消息中携带所述移动管理网元为所述UE确定的专用核心网辅助信息；
    发送器，用于根据所述请求消息发送接入请求消息，并将所述专用核心网辅助信息携带在所述接入请求消息触发的无线资源控制RRC连接建立请求消息中发送给所述UE的服务基站，所述专用核心网辅助信息用于所述基站为所述UE选择与所述专用核心网辅助信息对应的专用核心网。
  44. 根据权利要求43所述的UE，其特征在于，还包括：存储器和处理器，所述存储器用于保存所述专用核心网辅助信息；所述处理器用于关联所述专用核心网辅助信息与所述UE的服务网络。
  45. 根据权利要求43或44所述的UE，其特征在于，所述专用核心网辅助信息是所述移动管理网元根据所述UE签约的使用类型和如下信息中的至少一种确定的：运营商配置的UE的使用类型与专用核心网之间的映射关系、本地配置的运营商策略、所述UE的上下文信息。
  46. 根据权利要求43-45任一项所述的UE，其特征在于，所述接收器还用于：
    接收所述移动管理网元发送的寻呼消息，并通过所述发送器发送寻呼响应消息与所述移动管理网元建立连接。
  47. 根据权利要求43-46任一项所述的UE，其特征在于，所述接收器具体用于：
    接收所述移动管理网元发送的临时身份标识重分配请求消息，所述临时身份标识重分配请求消息中携带非广播位置区域标识和所述UE的专用核心网辅助信息，所述非广播位置区域标识用于指示所述UE重新发起接入请求。
  48. 根据权利要求43-46任一项所述的UE，其特征在于，所述接收器具体用于：
    接收所述基站发送的无线资源控制RRC连接释放消息，所述RRC连接释放消息中携带原因值和所述UE的专用核心网辅助信息；所述RRC连接释放消息是所述基站接收到所述移动管理网元发送的连接释放命令消息后发送的，所述连接释放命令消息中携带所述原因值和所述UE的专用核心网辅助信息，所述原因值用于指示所述UE重新发起接入请求。
  49. 根据权利要求43-46任一项所述的UE，其特征在于，所述接收器具体用于：
    接收所述移动管理网元发送的分离请求消息，所述分离请求消息中携带重新附着分离类型和所述UE的专用核心网辅助信息，所述重新附着分离类型用于指示所述UE重新发起接入请求。
  50. 根据权利要求43-49任一项所述的UE，其特征在于，所述接入请求消息包括：附着请求或者位置更新请求。
  51. 根据权利要求43-50任一项所述的UE，其特征在于，所述UE的专用核心网辅助信息为所述移动管理网元的专用核心网类型或者所述UE签约的使用类型。
  52. 一种专用核心网迁移处理***，其特征在于，包括：如权利要求18-25任一项所述的移动管理网元和如权利要求26-34任一项所述的用户设备UE。
  53. 一种专用核心网迁移处理***，其特征在于，包括：如权利要求35-42任一项所述的移动管理网元和如权利要求43-51任一项所述的用户设备UE。
PCT/CN2016/079712 2016-04-20 2016-04-20 专用核心网迁移处理方法、设备和*** WO2017181353A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CN201680083437.3A CN108781402A (zh) 2016-04-20 2016-04-20 专用核心网迁移处理方法、设备和***
KR1020187032544A KR20180132851A (ko) 2016-04-20 2016-04-20 전용 코어 네트워크 천이를 처리하는 방법, 장비, 및 시스템
BR112018071476A BR112018071476A2 (pt) 2016-04-20 2016-04-20 método, dispositivo e sistema para processar migração entre redes principais dedicadas
EP16898941.6A EP3448089A4 (en) 2016-04-20 2016-04-20 METHOD FOR PROCESSING THE MIGRATION OF A DEDICATED CORE NETWORK, EQUIPMENT AND SYSTEM
PCT/CN2016/079712 WO2017181353A1 (zh) 2016-04-20 2016-04-20 专用核心网迁移处理方法、设备和***
US16/164,875 US20190053037A1 (en) 2016-04-20 2018-10-19 Method, Device, And System For Processing Migration Between Dedicated Core Networks

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/079712 WO2017181353A1 (zh) 2016-04-20 2016-04-20 专用核心网迁移处理方法、设备和***

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/164,875 Continuation US20190053037A1 (en) 2016-04-20 2018-10-19 Method, Device, And System For Processing Migration Between Dedicated Core Networks

Publications (1)

Publication Number Publication Date
WO2017181353A1 true WO2017181353A1 (zh) 2017-10-26

Family

ID=60115516

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/079712 WO2017181353A1 (zh) 2016-04-20 2016-04-20 专用核心网迁移处理方法、设备和***

Country Status (6)

Country Link
US (1) US20190053037A1 (zh)
EP (1) EP3448089A4 (zh)
KR (1) KR20180132851A (zh)
CN (1) CN108781402A (zh)
BR (1) BR112018071476A2 (zh)
WO (1) WO2017181353A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107295498A (zh) * 2016-04-01 2017-10-24 电信科学技术研究院 确定提供终端所需的移动性管理支持及处理的方法、装置
JP6804922B2 (ja) * 2016-10-07 2020-12-23 日本電気株式会社 制御装置、方法及びプログラム
WO2019105552A1 (en) * 2017-11-30 2019-06-06 Telefonaktiebolaget Lm Ericsson (Publ) Core network allocation handling
US20220104225A1 (en) * 2019-01-25 2022-03-31 Lenovo (Beijing) Limited Resource configuration
GB2592095A (en) * 2020-02-14 2021-08-18 Samsung Electronics Co Ltd User confidentiality in network
CN115398976A (zh) * 2020-04-08 2022-11-25 苹果公司 使用ue辅助信息的nr中的ue功率节省
US11991525B2 (en) 2021-12-02 2024-05-21 T-Mobile Usa, Inc. Wireless device access and subsidy control

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102316523A (zh) * 2010-06-29 2012-01-11 ***通信集团公司 负载重分配、迁移的方法和设备、***
CN102843741A (zh) * 2012-08-29 2012-12-26 中兴通讯股份有限公司 源侧、目标侧切换通信装置、通信***和呼叫切换方法
WO2016056966A1 (en) * 2014-10-10 2016-04-14 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for standalone lte ran using unlicensed frequency band

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100584093C (zh) * 2006-08-15 2010-01-20 华为技术有限公司 一种在移动通信***中转移用户设备的方法及***
BR122016000399B1 (pt) * 2011-09-30 2019-05-07 Nec Corporation Terminal em um sistema de comunicação móvel compreendendo pelo menos uma estação de base e método de comunicação para o terminal
US10231176B2 (en) * 2014-10-06 2019-03-12 Sharp Kabushiki Kaisha Base station device, terminal device, location management device, and control method
KR102135394B1 (ko) * 2016-01-18 2020-07-17 엘지전자 주식회사 무선 통신 시스템에서 혼잡 제어 방법 및 이를 위한 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102316523A (zh) * 2010-06-29 2012-01-11 ***通信集团公司 负载重分配、迁移的方法和设备、***
CN102843741A (zh) * 2012-08-29 2012-12-26 中兴通讯股份有限公司 源侧、目标侧切换通信装置、通信***和呼叫切换方法
WO2016056966A1 (en) * 2014-10-10 2016-04-14 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatus for standalone lte ran using unlicensed frequency band

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
BR112018071476A2 (pt) 2019-02-19
CN108781402A (zh) 2018-11-09
EP3448089A1 (en) 2019-02-27
EP3448089A4 (en) 2019-02-27
US20190053037A1 (en) 2019-02-14
KR20180132851A (ko) 2018-12-12

Similar Documents

Publication Publication Date Title
US11026127B2 (en) Method and apparatus for inter-system change in wireless communication
CN109673174B (zh) 以逐个会话为基础支持会话连续性的方法
WO2017181353A1 (zh) 专用核心网迁移处理方法、设备和***
JP6031529B2 (ja) モバイル通信システム、モバイル通信ネットワーク、インフラストラクチャ機器、モビリティマネージャ、方法およびコンピュータプログラム
KR101201731B1 (ko) 사용자 정보 통지 방법, 시스템 및 장치
JP2020129826A (ja) 無線通信方法及びデバイス
US20140348081A1 (en) Method for handling proximity-based service discovery and communication in a wireless communications system
CN102111748B (zh) 本地ip连接建立方法及***
WO2018059401A1 (zh) 网络切换方法、装置及***，网络接入方法及装置
WO2011098040A1 (zh) 回退到2g/3g网络的方法和相关设备及通信***
WO2017063484A1 (zh) 一种将终端设备切换到目标小区的方法、装置及基站
EP2296418B1 (en) Processing method, system and apparatus for mobility management
WO2016180018A1 (zh) 一种接入方法及相应的接入节点、终端和通信网络
WO2018000325A1 (zh) 一种基于位置区域的服务控制方法及设备
KR20130035143A (ko) 로컬 네트워크에서 로컬 엑세스와 음성 통화를 지원하기 위한 방법 및 장치
WO2018010583A1 (zh) 网络***
WO2016095113A1 (zh) 一种寻呼方法、移动性管理实体及基站
KR20120022022A (ko) 무선 통신 시스템에서 단말의 접속 제어 정보 설정 방법 및 장치
CN113439458A (zh) 用于连接建立的方法和装置
WO2015043244A1 (zh) 用户设备、请求消息接收方法、装置及其***
WO2013113240A1 (zh) 一种传输rn信息、寻呼ue的方法及装置
WO2017185199A1 (zh) 附着方法、寻呼方法、装置和设备
JP2020096389A (ja) 通信方法、通信システム、及び移動管理装置
WO2013152715A1 (zh) 一种csg签约信息的传输方法和设备
WO2018191952A1 (zh) 网络切换方法、装置与***

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112018071476

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20187032544

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2016898941

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016898941

Country of ref document: EP

Effective date: 20181120

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

Ref document number: 16898941

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 112018071476

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20181018