WO2020103773A1 - 一种用户路由更新方法及设备 - Google Patents

一种用户路由更新方法及设备

Info

Publication number
WO2020103773A1
WO2020103773A1 PCT/CN2019/118918 CN2019118918W WO2020103773A1 WO 2020103773 A1 WO2020103773 A1 WO 2020103773A1 CN 2019118918 W CN2019118918 W CN 2019118918W WO 2020103773 A1 WO2020103773 A1 WO 2020103773A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
management function
unified data
data management
access
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/118918
Other languages
English (en)
French (fr)
Inventor
唐廷芳
艾明
王胡成
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Academy of Telecommunications Technology CATT
Original Assignee
China Academy of Telecommunications Technology CATT
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 China Academy of Telecommunications Technology CATT filed Critical China Academy of Telecommunications Technology CATT
Publication of WO2020103773A1 publication Critical patent/WO2020103773A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • This application relates to the field of wireless communication technology, and in particular, to a user route update method and device.
  • SUPI Subscriber Identity, Permanent Identifier, User Permanent Identifier
  • 5G fifth-generation mobile communication technology
  • UE User Equipment
  • SUCI Subscription Concealed Identifier user hidden identifier
  • the AUSF Authentication, Unit, Selection, Function, AMMF
  • the Access and Mobility Management Function Access and Mobility Management Function
  • 5G The core network uses SUPI to identify the UE.
  • the access and mobility management function entity selects a unified data management function (Unified Data Management (UDM) entity according to SUPI
  • UDM Unified Data Management
  • SMF Session Management Function
  • Data management functional entity, and temporary identifiers (5G-GUTI (5G Globally Unique Temporary Unique Identifier), or 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier, 5G temporary mobile user identifier )) Identify the user.
  • the SUCI includes a routing field for routing the UE to the corresponding unified data management functional entity. Especially for large operators with multiple sub-unified data management functional entities, routing assistance is often needed to determine the unified data management functional entity.
  • the present application provides a user route update method and device to solve the problem that there is no solution for automatically updating user routes in the prior art.
  • an embodiment of the present application provides a user route update method, including:
  • the user equipment receives the first information sent by the unified data management function entity through the access and mobility management function entity to notify the user equipment of the route update;
  • the user equipment initiates a de-registration process after receiving the first information, and initiates a registration process after the de-registration process is completed.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs a response, an instruction indicating that the user equipment needs to initiate a de-registration process and a registration process.
  • the user equipment initiates a registration process, including:
  • the user equipment determines the SUCI containing the updated routing information according to the updated routing information
  • the user equipment initiates an initial registration process according to the SUCI containing the updated routing information.
  • an embodiment of the present application provides a user route update method.
  • the method includes:
  • the unified data management function entity sends the first information for informing the user equipment to trigger the route update to the user equipment through the access and mobility management function entity, so that the user equipment receives the first information Initiate the de-registration process, and initiate the registration process after the de-registration process is complete.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs to respond, and an instruction indicating that the user equipment needs to initiate a de-registration and registration process.
  • an embodiment of the present application provides user equipment, including: a processor, a memory, and a transceiver;
  • the processor is used to read the program in the memory and execute:
  • a de-registration process is initiated, and after the de-registration process is completed, a registration process is initiated.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs a response, an instruction indicating that the user equipment needs to initiate a de-registration process and a registration process.
  • the processor is specifically used to:
  • the updated routing information determine the SUCI containing the updated routing information; and initiate the initial registration process according to the SUCI containing the updated routing information.
  • an embodiment of the present application provides a unified data management functional entity, including: a processor, a memory, and a transceiver;
  • the processor is used to read the program in the memory and execute:
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs to respond, and an instruction indicating that the user equipment needs to initiate a de-registration and registration process.
  • an embodiment of the present application provides user equipment, including:
  • a receiving module configured to receive the first information sent by the unified data management function entity through the access and mobility management function entity to notify the user equipment of route update;
  • the processing module is configured to initiate a de-registration process after receiving the first information, and initiate a registration process after the de-registration process is completed.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs a response, an instruction indicating that the user equipment needs to initiate a de-registration process and a registration process.
  • processing module is specifically used for:
  • the initial registration process is initiated according to the SUCI containing the updated routing information.
  • an embodiment of the present application provides a unified data management functional entity, including:
  • a sending module configured to send first information for informing the user equipment to trigger a route update to the user equipment through an access and mobility management function entity, so that the user equipment receives the first information Initiate the de-registration process, and initiate the registration process after the de-registration process is complete.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs to respond, and an instruction indicating that the user equipment needs to initiate a de-registration and registration process.
  • an embodiment of the present application provides a computer storable medium on which a computer program is stored, which when executed by a processor implements the steps of the method described in the first aspect above, or the method described in the second aspect above step.
  • the user equipment after receiving the first information sent by the access and mobility management function entity, determines the routing update of the user equipment; the user equipment initiates the de-registration process, and initiates the registration process after the de-registration process is completed.
  • the user equipment route is updated, the user equipment initiates the de-registration process, the core network internally releases the connection with the unified data management function entity before the update, and the user equipment initiates the registration process to implement the core network internal user route update To further improve system performance.
  • an embodiment of the present application provides a user route update method.
  • the method includes:
  • the user equipment receives second information sent by the unified data management function entity through the access and mobility management function entity to notify the user equipment of route update;
  • the user equipment After receiving the second information, the user equipment sends a registration update request including the first route update indication to the access and mobility management function entity, so that the access and mobility management function entity is receiving After the first route update instruction is performed, a unified data management function entity selection is performed.
  • the first route update indication is used to indicate that the registration update request is used for route update.
  • the first route update instruction further includes updated route information.
  • an embodiment of the present application provides a user route update method.
  • the method includes:
  • the access and mobility management function entity receives the registration update request sent by the user equipment and containing the first route update indication
  • the access and mobility management functional entity performs unified data management functional entity selection.
  • the method further includes:
  • the access and mobility management functional entity is disassociated from the unified data management functional entity accessed before the update.
  • disassociating the access and mobility management functional entity from the unified data management functional entity accessed before the update includes:
  • the access and mobility management functional entity disassociates with the unified data management functional entity accessed before the update through a specific de-registration process or de-subscription process.
  • the method further includes:
  • the access and mobility management functional entity determines a target unified data management functional entity that the user equipment accesses after the update, and associates with the target unified data management functional entity.
  • the access and mobility management function entity associated with the target unified data management function includes:
  • the access and mobility management function entity is associated with the target unified data management function through a specific registration process or subscription process.
  • the method further includes:
  • the access and mobility management function entity sends a second route update instruction to the session management function entity, so that the session management function entity determines that the user equipment receives the route update after receiving the second route update instruction
  • the target unified data management functional entity The target unified data management functional entity.
  • the session management function entity determines the target unified data management function entity that the user equipment accesses after the route update, and further includes:
  • the session management functional entity disassociates from the unified data management functional entity accessed before the update and associates with the selected target unified data management functional entity.
  • an embodiment of the present application provides user equipment, including: a processor, a memory, and a transceiver;
  • the processor is used to read the program in the memory and execute:
  • the first route update indication is used to indicate that the registration update request is used for route update.
  • the first route update instruction further includes updated route information.
  • an embodiment of the present application provides an access and mobility management functional entity, including: a processor, a memory, and a transceiver;
  • the processor is used to read the program in the memory and execute:
  • the processor is also used to:
  • the association with the unified data management function entity accessed before the update is disassociated.
  • the processor is specifically used to:
  • the processor is also used to:
  • a target unified data management function entity accessed by the user equipment after the update is determined, and associated with the target unified data management function entity.
  • the processor is specifically used to:
  • the target unified data management function is associated with a specific registration process or subscription process.
  • the processor is also used to:
  • an embodiment of the present application provides user equipment, including:
  • a second receiving module configured to receive second information sent by the unified data management functional entity through the access and mobility management functional entity to notify the user equipment of route update;
  • a second sending module configured to send a registration update request containing a first route update instruction to the access and mobility management function entity after receiving the second information, so that the access and mobility management function After receiving the first route update indication, the entity performs entity selection of the unified data management function.
  • the first route update indication is used to indicate that the registration update request is used for route update.
  • the first route update instruction further includes updated route information.
  • an access and mobility management functional entity including:
  • a third receiving module configured to receive a registration update request sent by the user equipment and containing the first route update instruction
  • Selection module for entity selection of unified data management functions.
  • the selection module is also used to:
  • the association with the unified data management function entity accessed before the update is disassociated.
  • the selection module is specifically used for:
  • the selection module is also used to:
  • a target unified data management function entity accessed by the user equipment after the update is determined, and associated with the target unified data management function entity.
  • the selection module is specifically used for:
  • the target unified data management function is associated with a specific registration process or subscription process.
  • the selection module is also used to:
  • an embodiment of the present application provides a computer storable medium on which a computer program is stored, which when executed by a processor implements the steps of the method described in the eighth aspect, or as described in the ninth aspect Method steps.
  • the user equipment after receiving the second information sent by the access and mobility management function entity, the user equipment determines that the user equipment has a route update; the user equipment initiates a registration update request. After the routing update of the user equipment, the user equipment initiates a registration update request, and the core network internally reselects the unified data management function entity to implement the update of the core network internal user route and further improve system performance.
  • FIG. 1 is a schematic diagram of a system architecture of an embodiment of this application.
  • FIG. 2 is a schematic structural diagram of a first user route update system according to an embodiment of this application.
  • FIG. 3 is a first flowchart of user route update according to an embodiment of this application.
  • FIG. 4 is a second flowchart of performing user route update according to an embodiment of this application.
  • FIG. 5 is a schematic structural diagram of a first user equipment according to an embodiment of this application.
  • FIG. 6 is a schematic structural diagram of a first unified data management function entity according to an embodiment of this application.
  • FIG. 7 is a schematic structural diagram of a second user equipment according to an embodiment of this application.
  • FIG. 8 is a schematic structural diagram of a second unified data management function entity according to an embodiment of this application.
  • FIG. 9 is a flowchart of a first user route update method according to an embodiment of this application.
  • FIG. 10 is a flowchart of a second user route update method according to an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of a second user route update system according to an embodiment of this application.
  • FIG. 12 is a schematic diagram of registration types according to an embodiment of the application.
  • FIG. 13 is a third flowchart of performing user route update according to an embodiment of this application.
  • FIG. 14 is a flowchart of performing user routing update according to the fourth embodiment of the present application.
  • 15 is a schematic structural diagram of a third user equipment according to an embodiment of this application.
  • 16 is a schematic structural diagram of a first entity of access and mobility management functions according to an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of a fourth user equipment according to an embodiment of this application.
  • FIG. 18 is a schematic structural diagram of a second entity of access and mobility management functions according to an embodiment of the present application.
  • FIG. 20 is a fourth user route update method according to an embodiment of this application.
  • the term “plurality” refers to two or more, and other quantifiers are similar.
  • the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly explain the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. With the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • FIG. 1 exemplarily shows a schematic diagram of a system architecture applicable to an embodiment of the present application.
  • a terminal 101 may communicate with a core network via an access network entity 102.
  • the terminal May refer to UE, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.
  • Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital processing (Personal Digital Assistant (PDA), wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in future 5G networks, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • wireless communication Functional handheld devices computing devices or other processing devices connected to wireless modems
  • in-vehicle devices wearable devices
  • terminals in future 5G networks etc.
  • FIG. 1 For convenience of description in FIG. 1, only one terminal is exemplified. In an actual network, there may be multiple terminals coexisting, which will not be repeated here.
  • An access network (Access) (AN) entity 102 An access network (Access) (AN) entity 102.
  • the access network entity may also be referred to as a radio access network ((Radio) Access Network ((R) AN) entity, hereinafter collectively referred to as an access network entity or (R)
  • the AN entity is mainly responsible for providing a wireless connection for the terminal 101 and ensuring reliable transmission of uplink and downlink data of the terminal 101.
  • the access network entity 102 may be a next-generation base station (generation Node B, gNB) in a 5G system, and may be a Global System of Mobile (GSM) system or Code Division Multiple Access (CDMA)
  • GSM Global System of Mobile
  • CDMA Code Division Multiple Access
  • BTS Base Transceiver Station
  • NodeB, NB the base station in the wideband code division multiple access
  • WCDMA Wideband Code Division Multiple Access
  • LTE long term evolution
  • Evolutionary base station Evolutional Node B, eNB or eNodeB
  • a session management function (Session Management Function, SMF) entity 103 which can be used to perform some functions of a mobility management entity (Mobility Management Entity, MME) in the LTE system, is mainly responsible for establishing a session and managing a session for the terminal 101.
  • An appropriate user plane function (User Plane Function, UPF) entity may be selected for the terminal 101 according to the location information of the terminal 101.
  • the user plane functional entity 104 is a functional network element of the user plane of the terminal 101.
  • the main functions include packet routing and forwarding, and quality of service (QoS) processing of user plane data.
  • QoS quality of service
  • the access and mobility management functional entity 105 whose main functions include the termination point of the wireless access network control plane, the termination point of non-access signaling, mobility management, legal interception, access authorization or authentication, and so on.
  • the Policy Control Function (PCF) entity 106 is mainly responsible for functions such as the establishment, release, and modification of user plane transmission paths.
  • An authentication server function (Authentication Server Function, AUSF) entity 107, whose main functions include user authentication and the like.
  • the unified data management function (Unified Data Management Function, UDMF) entity 108 is mainly responsible for managing user's contract data and so on.
  • Data network (DN) 109 may refer to a network that provides services for terminal 101.
  • some DNs may provide an Internet access function for terminal 101, and some DNs may provide MMS function for terminal 101.
  • system architecture is only an illustration of the system architecture applicable to the embodiment of the present application.
  • the system architecture applicable to the embodiment of the present application can add other entities or reduce some entities compared to the system architecture shown in FIG. 1.
  • the embodiments of the present application when updating user routes, network element selection is performed within the core network, for example, the access and mobility management function entity selects a unified data management function entity, and the session management function entity selects a unified data management function entity; After the unified data management function for device access needs to be changed, the embodiments of the present application provide an automatic user route update method.
  • the first user route update system includes: user equipment 10 and a unified data management function entity 11.
  • the user equipment 10 is configured to receive first information sent by the unified data management function entity through the access and mobility management function entity to notify the user equipment of route update; after receiving the first information, a deregistration process is initiated , And initiate the re-registration process after the de-registration process is completed;
  • the unified data management function entity 11 is configured to send the first information used to notify the user equipment to trigger the route update to the user equipment through the access and mobility management function entity, so that the user equipment receives the After the first information, the de-registration process is initiated, and after the de-registration process is completed, the registration process is initiated.
  • the unified data management functional entity after determining that the routing update of the user equipment needs to be performed, the unified data management functional entity sends the first information to the access and mobility management functional entity. After receiving the first information, the access and mobility management functional entity Forward the first information to the user equipment.
  • the routing update of the user equipment may also be called a routing ID (Routing ID) routing update on the UE side, and may be called a routing ID routing update inside the core network, or may be called unified data.
  • the management function entity changes, both of which can indicate that the unified data management function entity accessed by the user equipment has changed.
  • the routing information in the embodiment of the present application may also be referred to as Routing ID information on the user equipment side, and may be referred to as Routing ID information within the core network; or the routing information may also be other entities representing the unified data management function entity accessed by the user equipment information.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs a response, an instruction indicating that the user equipment needs to initiate a de-registration process and a registration process.
  • the user equipment after receiving the first information sent by the access and mobility management function entity, the user equipment initiates a de-registration and registration process
  • the user equipment initiates the de-registration process according to the following methods:
  • the user equipment initiates a deregistration process through the 5G-GUTI obtained by initiating the route update, triggering the core network side to update the 5G mobility management (5G Mobility Management, 5GMM) and 5G session management (5G Session Management (5GSM) of the UE established before the route update
  • the context and its associated information include deletion of information associated with the first unified data management function entity, that is, the core network side deletes the context information and relevant associated information related to the SUPI corresponding to the pre-update route.
  • the user equipment initiates the registration process according to the following methods:
  • the user equipment determines the SUCI containing the updated routing information according to the updated routing information; the user equipment initiates an initial registration process through the SUCI containing the updated routing information.
  • the unified data management function entity needs to send the updated routing information to the user equipment through the first information.
  • the user equipment of the embodiment of the present application uses the SUCI containing the updated routing information; in addition, the user equipment uses the SUCI containing the updated routing information for the initial registration process and the prior art The user equipment initiates the same initial registration process, which will not be described in detail here.
  • the user route update method provided in the embodiment of the present application is applicable to user route update during user equipment registration, and also applicable to user route update after user equipment registration is completed. The following will be described in conjunction with different processes.
  • the unified data management functional entity selected by the authentication server functional entity before the route update is the first unified data management functional entity
  • the unified data management functional entity accessed by the user equipment after the route update is the second unified data management functional entity.
  • Step 301 The user equipment initiates an initial registration request; wherein, the user identifier carried in the initial registration request is SUCI.
  • Step 302 The access and mobility management functional entity selects an authentication node selection functional entity according to the PLMN (Public Land Mobile Network) and routing information in SUCI.
  • PLMN Public Land Mobile Network
  • Step 303 The network side authenticates the user.
  • the authentication server functional entity selects a suitable unified data management functional entity based on the PLMN and routing information in SUCI.
  • the authentication server functional entity After completing the authentication process, the authentication server functional entity returns the user
  • the SUPI information is given to access and mobility management functional entities.
  • the access and mobility management functions establish a 5GMM context for user equipment with SUPI as the index.
  • Step 304 The access and mobility management functional entity completes user registration with the first unified data management functional entity according to the SUPI information, obtains subscription data, performs user subscription and other operations, and updates the 5GMM context of the UE.
  • Step 305 The first unified data management function entity determines that the route of the user equipment needs to be updated, and the first unified data management function entity sends first information to the access and mobility management function entity to notify the user equipment to trigger route update;
  • the access and mobility management functional entity needs to forward the first information to the user equipment.
  • Step 306 The access and mobility management function entity allocates 5G-GUTI to the user equipment and saves the relevant information in the 5GMM context of the UE, sends a registration acceptance message containing the 5G-GUTI and the first information to the UE, and completes the registration process;
  • the first information includes updated routing information, an instruction indicating whether the user equipment needs a response, and an instruction indicating that the user equipment initiates the de-registration and registration process.
  • Step 307 The user equipment initiates a de-registration process after receiving the registration acceptance message containing the first information
  • the information associated with the first unified data management function entity in the core network of the user equipment before the update is deleted; for example, the 5GMM context and 5GSM context of the user equipment.
  • Step 308 The user equipment initiates an initial registration process using SUCI containing the updated routing information, and establishes a 5GMM context associated with the second unified data management function entity;
  • the user routing update is performed after the user device registration is completed.
  • the unified data management functional entity accessed by the user equipment before the route update is the first unified data management functional entity
  • the unified data management functional entity accessed by the user equipment after the route update is the second unified data management functional entity.
  • Step 401 The first unified data management function entity sends the first information used to notify the user equipment to trigger the route update to the access and mobility management function entity;
  • the first unified data management functional entity determines that it needs to update the unified data management functional entity accessed by the user equipment, and then sends the first information to the access and mobility management functional entity; for example, the operator needs to update the user database of the user equipment
  • the first unified data management function entity sends the first information used to notify the user equipment to trigger the route update to the access and mobility management function entity.
  • Step 402 The access and mobility management function entity forwards the first information to the user equipment
  • the access and mobility management functional entity forwards the first information to the user equipment by means of a non-access layer (Non Access Stratum, NAS) transport (transport) message;
  • NAS Non Access Stratum
  • transport transport
  • the first information includes updated routing information, an indication indicating whether the user equipment needs a response, and an indication indicating that the user equipment needs to initiate a de-registration and registration process.
  • Step 403 The user equipment records the updated routing information and returns a response message to the access and mobility management function entity;
  • the access and mobility management function entity forwards the first information to the user equipment by means of a downlink NAS transmission (DL NAS transport) message
  • the user equipment uses UL NAS transmission (UL NAS transport) to access and mobility management
  • the functional entity returns a response.
  • Step 404 The access and mobility management functional entity forwards the response message returned by the user equipment to the first unified data management functional entity.
  • Step 405 The user equipment initiates a de-registration process
  • the user equipment initiates a de-registration process, which carries 5G-GUTI, and the access and mobility management function entity finds the context and related information of the user equipment through 5G-GUTI. Further, the access and mobility management function entity Delete the information associated with the user equipment and the first unified data management function entity before the update. If the user equipment has established a session, the access and mobility management function entity will trigger the associated session management function entity recorded above to delete the User device related information. That is, deleting the relevant information of the user equipment in the core network includes, for example, the 5GMM context and 5GSM context of the user equipment.
  • Step 406 The user equipment initiates an initial registration process using SUCI containing updated routing information, and establishes a 5GMM context associated with the second unified data management function entity;
  • the first user equipment includes: a processor 500, a memory 501, a transceiver 502, and a bus interface.
  • the processor 500 is responsible for managing the bus architecture and general processing, and the memory 501 may store data used by the processor 500 when performing operations.
  • the transceiver 502 is used to receive and transmit data under the control of the processor 500.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 500 and various circuits of the memory represented by the memory 501 are linked together.
  • the bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, etc., which are well known in the art, and therefore, they will not be further described in this article.
  • the bus interface provides an interface.
  • the processor 500 is responsible for managing the bus architecture and general processing, and the memory 501 may store data used by the processor 500 when performing operations.
  • the process disclosed in the embodiments of the present application may be applied to the processor 500 or implemented by the processor 500.
  • each step of the signal processing flow may be completed by an integrated logic circuit of hardware in the processor 500 or instructions in the form of software.
  • the processor 500 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the embodiments of the present application The disclosed methods, steps and logic block diagrams.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware processor, or may be executed and completed by a combination of hardware and software modules in the processor.
  • the software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers.
  • the storage medium is located in the memory 501, and the processor 500 reads the information in the memory 501 and completes the steps of the signal processing flow in combination with its hardware.
  • the processor 500 is configured to read the program in the memory 501 and execute:
  • a de-registration process is initiated, and after the de-registration process is completed, a registration process is initiated.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs a response, an instruction indicating that the user equipment needs to initiate a de-registration process and a registration process.
  • processor 500 is specifically used to:
  • the updated routing information determine the SUCI containing the updated routing information; and initiate the initial registration process according to the SUCI containing the updated routing information.
  • the first unified data management functional entity of the embodiment of the present application includes: a processor 600, a memory 601, a transceiver 602, and a bus interface.
  • the processor 600 is responsible for managing the bus architecture and general processing, and the memory 601 may store data used by the processor 600 when performing operations.
  • the transceiver 602 is used to receive and transmit data under the control of the processor 600.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 600 and various circuits of the memory represented by the memory 601 are linked together.
  • the bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, etc., which are well known in the art, and therefore, they will not be further described in this article.
  • the bus interface provides an interface.
  • the processor 600 is responsible for managing the bus architecture and general processing, and the memory 601 may store data used by the processor 600 when performing operations.
  • the process disclosed in the embodiments of the present application may be applied to the processor 600 or implemented by the processor 600.
  • each step of the signal processing flow may be completed by an integrated logic circuit of hardware in the processor 600 or instructions in the form of software.
  • the processor 600 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which can implement or execute the embodiments of the present application
  • the disclosed methods, steps and logic block diagrams may be a microprocessor or any conventional processor.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware processor, or may be executed and completed by a combination of hardware and software modules in the processor.
  • the software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers.
  • the storage medium is located in the memory 601, and the processor 600 reads the information in the memory 601 and completes the steps of the signal processing flow in combination with its hardware.
  • the processor 600 is configured to read the program in the memory 601 and execute:
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs to respond, and an instruction indicating that the user equipment needs to initiate a de-registration and registration process.
  • the second user equipment includes:
  • the first receiving module 701 is configured to receive first information sent by the unified data management function entity through the access and mobility management function entity to notify the user equipment of route update;
  • the first processing module 702 is configured to initiate a de-registration process after receiving the first information, and initiate a registration process after the de-registration process is completed.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs a response, an instruction indicating that the user equipment needs to initiate a de-registration process and a registration process.
  • the first processing module 702 is specifically used to:
  • the initial registration process is initiated according to the SUCI containing the updated routing information.
  • the second unified data management functional entity of the embodiment of the present application includes:
  • the first sending module 801 is configured to send the first information used to notify the user equipment to trigger the route update to the user equipment through the access and mobility management function entity, so that the user equipment receives the first Initiate the de-registration process after a message, and initiate the registration process after the de-registration process is completed;
  • the second processing module 802 is configured to control the sending module to send the first information.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs to respond, and an instruction indicating that the user equipment needs to initiate a de-registration and registration process.
  • An embodiment of the present application provides a computer storable medium on which a computer program is stored, which when executed by a processor implements the steps of the method described above on the user equipment side, or the steps of the method described above by the unified data management function entity .
  • a user route update method is provided in an embodiment of the present application, because this method corresponds to the method on the user equipment side in the user route update system of the embodiment of the present application, and the principle of the method to solve the problem is similar to the system Therefore, the implementation of this method can be referred to the implementation of the system, and the repetition is not repeated here.
  • the first user route update method includes:
  • Step 901 The user equipment receives first information sent by the unified data management function entity through the access and mobility management function entity to notify the user equipment of route update;
  • Step 902 The user equipment initiates a de-registration process after receiving the first information, and initiates a registration process after the de-registration process is completed.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs a response, an instruction indicating that the user equipment needs to initiate a de-registration process and a registration process.
  • the user equipment initiates a registration process, including:
  • the user equipment determines the SUCI containing the updated routing information according to the updated routing information
  • the user equipment initiates an initial registration process according to the SUCI containing the updated routing information.
  • a second user route update method includes:
  • Step 1001 The unified data management functional entity determines the routing update of the user equipment
  • Step 1002 The unified data management function entity sends the first information for notifying the user equipment to trigger the route update to the user equipment through the access and mobility management function entity, so that the user equipment receives the first After a message, the de-registration process is initiated, and after the de-registration process is completed, the registration process is initiated.
  • the first information includes some or all of the following information:
  • the updated routing information an instruction indicating whether the user equipment needs to respond, and an instruction indicating that the user equipment needs to initiate a de-registration and registration process.
  • a second user route update system includes: user equipment 110, an access and mobility management function entity 111, and a unified data management function entity 112.
  • the unified data management function entity 112 is configured to send the first information used to notify the user equipment to trigger a route update to the user equipment through the access and mobility management function entity, so that the user equipment receives the The registration update process is initiated after the first information;
  • the user equipment 110 is configured to receive the first information sent by the unified data management function entity through the access and mobility management function entity to notify the user equipment of the route update;
  • the entry and mobility management functional entity sends a registration update request containing the first route update instruction, so that the access and mobility management functional entity performs unified data management function entity selection after receiving the first route update instruction;
  • the access and mobility management function entity 111 is configured to receive a registration update request sent by the user equipment and containing the first route update indication, and perform unified data management function entity selection.
  • the unified data management functional entity after determining that the routing update of the user equipment needs to be performed, the unified data management functional entity sends the first information to the access and mobility management functional entity. After receiving the first information, the access and mobility management functional entity Forward the first information to the user equipment.
  • the routing update of the user equipment may also be called routing update on the UE side, may be called routing update inside the core network, or may be called a unified data management function entity change, both of which are It can indicate that the unified data management function entity accessed by the user equipment changes.
  • the user equipment in the embodiment of the present application when initiating the registration update operation, sends a registration update request including the first route update indication to the access and mobility management function entity; wherein the first route update indication is used to trigger access Uniform data management function entity selection with mobility management function entity.
  • the first route update instruction is used to trigger the access and mobility management function entity to perform unified data management function entity selection and then perform route update when receiving the registration update request.
  • the manifestation form of the first route update indication information in the registration update request may be:
  • the existing registration types include initial registration type, mobile registration update type, periodic registration update type, and emergency registration type; the registration type of "update parameter registration update" is extended on the basis of the existing registration type; as shown in FIG. 12 , Three bits are used to indicate the registration type, where 000 indicates the initial registration type, 010 indicates the mobile registration update type, 011 indicates the periodic registration update type, 100 indicates the emergency registration type, and 111 indicates the update parameter registration update type.
  • the access and mobility management function entity can determine the registration Update requests are used for routing updates.
  • the first routing update indication information is indicated by specific parameters
  • a specific parameter is carried in the registration update request, and when the registration request contains the specific parameter, it indicates that the registration update request is used for routing update.
  • the access and mobility management function entity After receiving the registration update request sent by the user equipment and including the first route update instruction, the access and mobility management function entity performs unified data management function entity selection.
  • the access and mobility management functional entity selects the unified data management functional entity according to the SUPI corresponding to the user equipment.
  • the access and mobility management functional entity records the unified data management functional entity that the user equipment accesses before updating the route. After selecting the unified data management functional entity according to the SUPI, the access and mobility management functional entity compares the records The unified data management functional entity and the selected target unified data management functional entity, if the recorded unified data management functional entity and the target unified data management functional entity are different, the access and mobility management functions determine the access unified data management function The entity changes.
  • the configuration parameters of the user equipment can be modified through the background.
  • the unified data management functional entity accessed by the user equipment is modified to the second unified data management functional entity; then, the access and mobility management functional entity receives the registration update sent by the user equipment
  • the unified data management functional entity selected according to the SUPI of the user equipment is the second unified data management functional entity, and the access and mobility management functional entity determines that the unified data management functional entity accessed by the user equipment changes.
  • the access and mobility management functional entity disassociates from the unified data management functional entity accessed before the update.
  • the access and mobility management functional entity disassociates from the unified data management functional entity accessed before the update through a specific de-registration process or de-subscription process.
  • the access and mobility management functional entity determines the target unified data management functional entity accessed by the updated user equipment according to the SUPI of the user equipment, and associates with the target unified data management function;
  • the access and mobility management function entity is associated with the target unified data management function through a specific registration process or subscription process. Since the access and mobility management function already has context information related to the user equipment, it is related to the target The association of the unified data management function may not need to retrieve the contracted data of the user device from the unified data management function, but only needs to update the access and mobility management functions to bind with the target unified data management function to complete the subscription to the target unified data management function That's it.
  • the access and mobility management functions can also reacquire the subscription data of the user equipment from the target unified data management function according to the registration process and complete the relevant subscription.
  • the access and mobility management functional entity changes the recorded unified data management functional entity to the target unified data management functional entity.
  • the access and mobility management functional entity is disassociated from the unified data management functional entity accessed before the update and associated with the target unified data management functional entity.
  • the functional entity also needs to notify the session management functional entity that the user equipment has a routing update;
  • the access and mobility management function entity sends a second route update instruction to the session management function entity, so that the session management function entity determines the user after the route update after receiving the second route update instruction
  • the target unified data management functional entity accessed by the device, and the association with the unified data management functional entity accessed before the update and the association with the selected target unified data management functional entity are disassociated.
  • the access and mobility management functional entity determines the associated session management functional entity based on the 5GMM context information of the user equipment, and sends a second route update indication to the session management functional entity; wherein the second route update indication is used to represent the user Device routing update;
  • the session management functional entity selects the target unified data management functional entity according to the SUPI of the user equipment; and compares the recorded unified data management functional entity with the target unified data management functional entity.
  • the unified data management functional entity is different from the target unified data management functional entity, it is determined that the unified data management function has changed;
  • the second route update instruction received by the session management function entity may further include information related to the target unified data management function, and the session management function entity may directly determine the target unified access of the user equipment after the update according to the second route update instruction Data management functional entity; and compare the recorded unified data management functional entity with the target unified data management functional entity.
  • the relevant information of the target unified data management functional entity may be the IP address or identification information of the target unified data management functional entity selected by the access and mobility management functional entity.
  • the session management functional entity After determining that the unified data management function has changed, the session management functional entity disassociates with the unified data management functional entity accessed before the update and associates with the selected target unified data management functional entity.
  • the session management functional entity is disassociated from the unified data management functional entity accessed before the update through a specific de-registration or subscription process, and the session management functional entity is associated with the target unity through a specific registration or subscription process Data management functional entity.
  • the session management functional entity Since the session management functional entity already has context information related to the user equipment, the association with the target unified data management functional entity may not need to re-acquire the user equipment contract data from the unified data management functional entity, only update the access It is only necessary to bind with the mobility management functional entity and the target unified data management functional entity to complete the subscription to the target unified data management functional entity.
  • the session management functional entity may also be processed according to the registration process, specifically including re-acquiring the subscription data of the user equipment from the target unified data management functional entity and completing the relevant subscription.
  • the session management functional entity changes the recorded unified data management functional entity to the target unified data management functional entity.
  • the user route update method provided in the embodiment of the present application is applicable to user route update during user equipment registration, and also applicable to user route update after user equipment registration is completed. The following will be described in conjunction with different processes.
  • the unified data management functional entity selected by the authentication server functional entity before the route update is the first unified data management functional entity
  • the target unified data management functional entity accessed by the user equipment after the route update is the second unified data management functional entity.
  • Step 1301 The user equipment initiates an initial registration request; wherein, the user identifier carried in the initial registration request is SUCI.
  • Step 1302 The access and mobility management functional entity selects an appropriate authentication server functional entity according to the PLMN (Public Land Mobile Network) and routing information in SUCI.
  • PLMN Public Land Mobile Network
  • Step 1303 The network side authenticates the user.
  • the authentication server functional entity selects a suitable unified data management functional entity based on the PLMN and routing information in SUCI.
  • the authentication server functional entity After completing the authentication process, the authentication server functional entity returns to the user
  • the SUPI information is given to access and mobility management functional entities.
  • the access and mobility management functions establish a 5GMM context for the UE with the SUPI as the index.
  • Step 1304 The access and mobility management functional entity completes user registration with the first unified data management functional entity according to the SUPI information, obtains subscription data, performs user subscription and other operations, and updates the 5GMM context of the UE.
  • Step 1305 the first unified data management function entity determines that the route of the user equipment needs to be updated, and the first unified data management function entity sends second information to the access and mobility management function entity to notify the user equipment to trigger route update;
  • the access and mobility management functional entity needs to forward the second information to the user equipment.
  • Step 1306 The access and mobility management function entity allocates 5G-GUTI to the user equipment and saves the relevant information in the 5GMM context of the UE, sends a registration acceptance message containing the 5G-GUTI and the second information to the UE, and completes the registration process.
  • Step 1307 After receiving the registration acceptance message containing the second information, the user equipment sends a registration update request containing the first route update indication to the access and mobility management function entity;
  • the first route update indication may be through independent parameters or included in other parameters, the purpose of which is to trigger the access and mobility management function entity to trigger the unified data management function entity selection after receiving the registration request.
  • the registration update type of the parameter update can be added by extending the registration type, and carry the indication that the update parameter is the route; it can also directly carry a parameter to indicate that the registration update is used for route update, etc.
  • the updated route can also be carried in the indication information.
  • Step 1308, the access and mobility management functional entity performs unified data management functional entity selection, and determines that the unified data management function has changed;
  • the access and mobility management functional entity selects according to the SUPI of the user equipment and selects the second unified data management functional entity; the access and mobility management functional entity determines the recorded first unified data management functional entity and selects If the second unified data management functional entity is different, the access and mobility management functional entity determines that the unified data management functional entity has changed.
  • the unified data management functional entity does not change after the access and mobility management functional entity judges, the subsequent steps are ignored, that is, there is no need to contact the association with the first unified data management functional entity and the second unified data management functional entity Treatment.
  • Step 1309 The access and mobility management functional entity disassociates from the first unified data management functional entity according to the recorded first unified data management functional entity.
  • Step 1310 The access and mobility management functional entity is associated with the second unified data management functional entity, and the recorded unified data management functional entity is changed to the second unified data management functional entity.
  • the user routing update is performed after the user device registration is completed.
  • the unified data management functional entity selected by the authentication server functional entity before the route update is the first unified data management functional entity
  • the target unified data management functional entity accessed by the user equipment after the route update is the second unified data management functional entity.
  • Step 1401 The first unified data management function entity sends the second information used to notify the user equipment to trigger the route update to the access and mobility management function entity;
  • the first unified data management functional entity determines that the unified data management functional entity that needs to be updated by the user equipment needs to be updated, and sends the second information to the access and mobility management functional entity; for example, the operator needs to update the user database of the user equipment
  • the first unified data management function entity sends the second information used to notify the user equipment to trigger the route update to the access and mobility management function entity.
  • Step 1402 The access and mobility management function entity forwards the second information to the user equipment
  • the access and mobility management function entity forwards the second information to the user equipment by means of NAS transport messages;
  • the access and mobility management functions can also forward the second information to the user equipment by way of over-the-air technology (OTA).
  • OTA over-the-air technology
  • Step 1403 The user equipment records the updated routing information and returns a response message to the access and mobility management function entity;
  • the access and mobility management function entity forwards the second information to the user equipment by means of a NAS transport message
  • the user equipment returns a response to the access and mobility management function entity through the NAS transport.
  • Step 1404 The access and mobility management functional entity forwards the response message returned by the user equipment to the first unified data management functional entity.
  • Step 1405 the user equipment sends a registration update request containing the first route update indication to the access and mobility management function entity;
  • the first route update indication may be through independent parameters or included in other parameters, the purpose of which is to trigger the access and mobility management function entity to trigger the unified data management function entity selection after receiving the registration request.
  • the registration update type of the parameter update can be added by extending the registration type, and carry the indication that the update parameter is the route; it can also directly carry a parameter to indicate that the registration update is used for route update, etc.
  • the updated route can also be carried in the indication information.
  • Step 1406 the access and mobility management functional entity performs unified data management functional entity selection, and determines that the unified data management functional entity changes;
  • the access and mobility management functional entity selects according to the SUPI of the user equipment and selects the second unified data management functional entity; the access and mobility management functional entity determines the recorded first unified data management functional entity and selects If the second unified data management functional entity is different, the access and mobility management functional entity determines that the unified data management functional entity has changed.
  • the unified data management functional entity does not change after the access and mobility management functional entity judges, the subsequent steps are ignored, that is, there is no need to contact the association with the first unified data management functional entity and the second unified data management functional entity Process, there is no need to initiate routing update processing to the session management function entity.
  • Step 1407 The access and mobility management functional entity disassociates from the first unified data management functional entity according to the recorded first unified data management functional entity.
  • Step 1408 The access and mobility management functional entity is associated with the second unified data management functional entity, and the recorded unified data management functional entity is changed to the second unified data management functional entity.
  • Step 1409 The access and mobility management functional entity determines the associated session management functional entity according to the 5GMM context information of the user equipment, and sends a second route update instruction to the session management functional entity;
  • the second route update indication is used to indicate the route update of the user equipment.
  • Step 1410 After receiving the second route update instruction, the session management functional entity determines the target unified data management functional entity of the user equipment;
  • the determination of the target unified data management functional entity may be that the session management functional entity receives the second route update instruction and triggers selection according to SUPI, or the access and mobility management functional entity notifies the session management functional entity.
  • Step 1411 The session management function entity determines that the unified data management function has changed, and the session management function entity disassociates from the first unified data management function entity;
  • the session management function entity determines the target unified data management function, that is, the second unified data management function entity, and the session management function entity compares the recorded first unified data management function entity with the selected second unified data management function entity to determine Changes in unified data management functions;
  • the session management functional entity disassociates from the unified data management functional entity accessed before the update through a specific de-registration process or de-subscription process.
  • Step 1412 The session management functional entity is associated with the second unified data management functional entity, and the recorded unified data management functional entity is changed to the second unified data management functional entity.
  • the session management function entity is associated with the target unified data management function through a specific registration process or subscription process. Since the session management function entity already has context information related to the user equipment, the association with the target unified data management function entity may not be
  • the subscription data of the user equipment needs to be re-acquired from the source unified data management functional entity, and only the access and mobility management functional entity is bound to the target unified data management functional entity to complete the subscription to the target unified data management functional entity.
  • the session management functional entity may also be processed in accordance with the registration process, including re-acquiring the subscription data of the user equipment from the target unified data management functional entity and completing the relevant subscription.
  • the third user equipment in the embodiment of the present application includes: a processor 1500, a memory 1501, a transceiver 1502, and a bus interface.
  • the processor 1500 is responsible for managing the bus architecture and general processing, and the memory 1501 may store data used by the processor 1500 in performing operations.
  • the transceiver 1502 is used to receive and transmit data under the control of the processor 1500.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1500 and various circuits of the memory represented by the memory 1501 are linked together.
  • the bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, etc., which are well known in the art, and therefore, they will not be further described in this article.
  • the bus interface provides an interface.
  • the processor 1500 is responsible for managing the bus architecture and general processing, and the memory 1501 may store data used by the processor 1500 in performing operations.
  • the process disclosed in the embodiments of the present application may be applied to the processor 1500 or implemented by the processor 1500.
  • each step of the signal processing flow may be completed by an integrated logic circuit of hardware in the processor 1500 or an instruction in the form of software.
  • the processor 1500 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the embodiments of the present application The disclosed methods, steps and logic block diagrams.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware processor, or may be executed and completed by a combination of hardware and software modules in the processor.
  • the software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers.
  • the storage medium is located in the memory 1501.
  • the processor 1500 reads the information in the memory 1501 and completes the steps of the signal processing flow in combination with its hardware.
  • the processor 1500 is configured to read the program in the memory 1501 and execute:
  • the first route update indication is used to indicate that the registration update request is used for route update.
  • the first route update instruction further includes updated route information.
  • an embodiment of the present application provides an access and mobility management functional entity, including: a processor 1600, a memory 1601, a transceiver 1602, and a bus interface.
  • the processor 1600 is responsible for managing the bus architecture and general processing, and the memory 1601 may store data used by the processor 1600 in performing operations.
  • the transceiver 1602 is used to receive and transmit data under the control of the processor 1600.
  • the bus architecture may include any number of interconnected buses and bridges, specifically, one or more processors represented by the processor 1600 and various circuits of the memory represented by the memory 1601 are linked together.
  • the bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, etc., which are well known in the art, and therefore, they will not be further described in this article.
  • the bus interface provides an interface.
  • the processor 1600 is responsible for managing the bus architecture and general processing, and the memory 1601 may store data used by the processor 1600 in performing operations.
  • the process disclosed in the embodiments of the present application may be applied to the processor 1600 or implemented by the processor 1600.
  • each step of the signal processing flow may be completed by an integrated logic circuit of hardware in the processor 1600 or instructions in the form of software.
  • the processor 1600 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the embodiments of the present application The disclosed methods, steps and logic block diagrams.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware processor, or may be executed and completed by a combination of hardware and software modules in the processor.
  • the software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers.
  • the storage medium is located in the memory 1601.
  • the processor 1600 reads the information in the memory 1601 and completes the steps of the signal processing flow in combination with its hardware.
  • the processor 1600 is used to read the program in the memory 1601 and execute:
  • processor 1600 is also used to:
  • the association with the unified data management function entity accessed before the update is disassociated.
  • processor 1600 is specifically used to:
  • processor 1600 is also used to:
  • a target unified data management function entity accessed by the user equipment after the update is determined, and associated with the target unified data management function entity.
  • processor 1600 is specifically used to:
  • the target unified data management function is associated with a specific registration process or subscription process.
  • processor 1600 is also used to:
  • a user equipment includes:
  • the second receiving module 1701 is configured to receive second information sent by the unified data management function entity through the access and mobility management function entity to notify the user equipment of route update;
  • the second sending module 1702 is configured to send a registration update request including a first route update indication to the access and mobility management function entity after receiving the second information, so that the access and mobility management The functional entity selects the unified data management functional entity after receiving the first route update instruction.
  • the first route update indication is used to indicate that the registration update request is used for route update.
  • the first route update instruction further includes updated route information.
  • an access and mobility management functional entity includes:
  • the third receiving module 1801 is configured to receive a registration update request sent by the user equipment and containing the first route update indication
  • the selection module 1802 is used for entity selection of unified data management functions.
  • the selection module 1802 is also used to:
  • the association with the unified data management function entity accessed before the update is disassociated.
  • the selection module 1802 is specifically used to:
  • the selection module 1802 is also used to:
  • a target unified data management function entity accessed by the user equipment after the update is determined, and associated with the target unified data management function entity.
  • the selection module 1802 is specifically used to:
  • the target unified data management function is associated with a specific registration process or subscription process.
  • the selection module 1802 is also used to:
  • An embodiment of the present application provides a computer storable medium on which a computer program is stored, which when executed by a processor implements the steps of the method described above on the user equipment side, or the side described on the entity side of the access and mobility management function Method steps.
  • a user route update method is provided in an embodiment of the present application, because this method corresponds to the method on the user equipment side in the user route update system of the embodiment of the present application, and the principle of the method to solve the problem is similar to the system Therefore, the implementation of this method can be referred to the implementation of the system, and the repetition is not repeated here.
  • an embodiment of the present application provides a user route update method.
  • the method includes:
  • Step 1901 The user equipment receives second information sent by the unified data management function entity through the access and mobility management function entity to notify the user equipment of route update;
  • Step 1902 After receiving the second information, the user equipment sends a registration update request including a first route update indication to the access and mobility management function entity to enable the access and mobility management function After receiving the first route update indication, the entity performs entity selection of the unified data management function.
  • the first route update indication is used to indicate that the registration update request is used for route update.
  • the first route update instruction further includes updated route information.
  • an embodiment of the present application provides a user route update method, because this method corresponds to the method of the access and mobility management function entity side in the user route update system of the embodiment of the present application, and this method solves the problem
  • the principle of is similar to that of this system, so the implementation of this method can refer to the implementation of the system, and the repetition is not repeated here.
  • an embodiment of the present application provides a user route update method.
  • the method includes:
  • Step 2001 The access and mobility management function entity receives a registration update request sent by the user equipment and containing the first route update indication;
  • Step 2002 the access and mobility management functional entity performs unified data management functional entity selection.
  • the method further includes:
  • the access and mobility management functional entity is disassociated from the unified data management functional entity accessed before the update.
  • disassociating the access and mobility management functional entity from the unified data management functional entity accessed before the update includes:
  • the access and mobility management functional entity disassociates with the unified data management functional entity accessed before the update through a specific de-registration process or de-subscription process.
  • the method further includes:
  • the access and mobility management functional entity determines a target unified data management functional entity that the user equipment accesses after the update, and associates with the target unified data management functional entity.
  • the access and mobility management function entity associated with the target unified data management function includes:
  • the access and mobility management function entity is associated with the target unified data management function through a specific registration process or subscription process.
  • the method further includes:
  • the access and mobility management function entity sends a second route update instruction to the session management function entity, so that the session management function entity determines that the user equipment accesses after the update after receiving the second route update instruction.
  • the session management function entity determines the target unified data management function entity that the user equipment accesses after the route update, and further includes:
  • the session management functional entity disassociates from the unified data management functional entity accessed before the update and associates with the selected target unified data management functional entity.
  • the computer storage medium may be any available medium or data storage device that can be accessed by the computer, including but not limited to magnetic memory (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical memory (such as CD, DVD, BD, HVD, etc.), and semiconductor memory (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state hard disk (SSD)), etc.
  • magnetic memory such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.
  • optical memory such as CD, DVD, BD, HVD, etc.
  • semiconductor memory such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state hard disk (SSD)
  • the application can also be implemented in hardware and / or software (including firmware, resident software, microcode, etc.).
  • the present application may take the form of a computer-usable or computer-readable storage medium on a computer-readable storage medium with computer-usable or computer-readable program code implemented in the medium to be used by an instruction execution system or Used in conjunction with an instruction execution system.
  • a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, transmit, or transmit a program for use by an instruction execution system, apparatus, or device, or in conjunction with an instruction execution system, Use of device or equipment.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, the present application may take the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.
  • computer usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can be provided to the processor of a general-purpose computer, special-purpose computer, embedded processing machine, or other programmable data processing device to produce a machine that enables the generation of instructions executed by the processor of the computer or other programmable data processing device
  • These computer program instructions may also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, the instructions The device implements the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and / or block diagrams.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operating steps are performed on the computer or other programmable device to produce computer-implemented processing, which is executed on the computer or other programmable device
  • the instructions provide steps for implementing the functions specified in one block or multiple blocks of the flowchart one flow or multiple flows and / or block diagrams.

Landscapes

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

Abstract

本申请涉及无线通信技术领域，特别涉及一种用户路由更新方法及设备，用以解决现有技术中还没有一种实现用户路由自动更新的方案的问题。本申请实施例用户设备接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。在用户设备路由更新后，通过用户设备发起去注册流程的方式，核心网内部解除与更新前统一数据管理功能实体的连接，并通过用户设备发起注册流程的方式，实现核心网内部用户路由的更新，进一步提高系统性能。

Description

一种用户路由更新方法及设备
本申请要求在2018年11月19日提交中国专利局、申请号为201811378541.2、申请名称为“一种用户路由更新方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，特别涉及一种用户路由更新方法及设备。
背景技术
目前第五代移动通信技术(5th-Generation,5G)系统中SUPI(Subscription Permanent Identifier，用户永久标识)都不在空口传递，UE(User Equipment，用户设备)与网络交互的初始注册请求消息采用SUCI(Subscription Concealed Identifier，用户隐藏标识)，其中SUCI为加密后的SUPI，SUCI与SUPI均用来标识用户。在鉴权认证过程中，AUSF(Authentication Unit Selection Function,AMMF)实体给接入和移动性管理功能(Access and Mobility Management Function，接入和移动性管理功能)实体返回SUPI，在后续流程中在5G核心网内部均采用SUPI来标识UE，例如接入和移动性管理功能实体根据SUPI选择统一数据管理功能(Unified Data Management,UDM)实体，会话管理功能(Session Management Function,SMF)实体根据SUPI选择统一数据管理功能实体，而在空口则采用临时标识(5G-GUTI(5G Globally Unique Temporary Identifier，5G用户全球唯一临时标识)或者5G-S-TMSI(5G S-Temporary Mobile Subscription Identifier，5G临时移动用户标识))标识用户。SUCI中包含了路由字段，用于路由UE到相应的统一数据管理功能实体，尤其针对大运营商存在多个子统一数据管理功能实体的情况下，往往需要通过路由协助确定统一数据管理功能实体。
目前，根据运营商需求，存在需要将部分用户的用户数据库从接入的统一数据管理功能实体搬迁到另一统一数据管理功能实体的场景，现有的做法是通过后台更改配置数据的方式实现，该方式需要浪费大量的人力物力，并且用户路由更新周期较长。因此，目前如何实现用户路由的自动更新成为亟待解决的问题。
发明内容
本申请提供一种用户路由更新方法及设备，用以解决现有技术中还没有一种实现用户路由自动更新的方案的问题。
基于上述问题，第一方面，本申请实施例提供一种用户路由更新方法，包括：
用户设备接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；
所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册流程和注册流程的指示。
可选的，所述用户设备发起注册流程，包括：
所述用户设备根据所述更新后的路由信息，确定包含所述更新后的路由信息的SUCI；
所述用户设备根据包含所述更新后的路由信息的SUCI发起初始注册过程。
第二方面，本申请实施例提供一种用户路由更新方法，该方法包括：
统一数据管理功能实体通过接入和移动性管理功能实体向所述用户设备发送用于通知所述用户设备触发路由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册和注册流程的指示。
第三方面，本申请实施例提供一种用户设备，包括：处理器、存储器和收发机；
其中，所述处理器，用于读取存储器中的程序并执行：
接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；
在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册流程和注册流程的指示。
可选的，所述处理器具体用于：
根据所述更新后的路由信息，确定包含所述更新后的路由信息的SUCI；根据包含所述更新后的路由信息的SUCI发起初始注册过程。
第四方面，本申请实施例提供一种统一数据管理功能实体，包括：处理器、存储器和收发机；
其中，所述处理器，用于读取存储器中的程序并执行：
通过接入和移动性管理功能实体向所述用户设备发送用于通知所述用户设备触发路 由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册和注册流程的指示。
第五方面，本申请实施例提供一种用户设备，包括：
接收模块，用于接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；
处理模块，用于在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册流程和注册流程的指示。
可选的，处理模块具体用于：
根据所述更新后的路由信息，确定包含所述更新后的路由信息的SUCI；
根据包含所述更新后的路由信息的SUCI发起初始注册过程。
第六方面，本申请实施例提供一种统一数据管理功能实体，包括：
发送模块，用于通过接入和移动性管理功能实体向所述用户设备发送用于通知所述用户设备触发路由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册和注册流程的指示。
第七方面，本申请实施例提供一种计算机可存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述第一方面所述方法的步骤，或上述第二方面所述方法的步骤。
由于本申请实施例用户设备在接收到接入和移动性管理功能实体发送的第一信息后，确定用户设备路由更新；用户设备发起去注册流程，且在去注册流程完成后发起注册流程。在用户设备路由更新后，通过用户设备发起去注册流程的方式，核心网内部解除与更新前统一数据管理功能实体的连接，并通过用户设备发起注册流程的方式，实现核心网内部用户路由的更新，进一步提高系统性能。
第八方面，本申请实施例提供一种用户路由更新方法，该方法包括：
用户设备接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第二信息；
所述用户设备在接收到所述第二信息后向所述接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求，以使所述接入和移动性管理功能实体在接收到所述第一路由更新指示后进行统一数据管理功能实体选择。
可选的，所述第一路由更新指示用于指示所述注册更新请求用于路由更新。
可选的，所述第一路由更新指示中还包含更新后的路由信息。
第九方面，本申请实施例提供一种用户路由更新方法，该方法包括：
接入和移动性管理功能实体接收用户设备发送的包含第一路由更新指示的注册更新请求；
所述接入和移动性管理功能实体进行统一数据管理功能实体选择。
可选的，在所述接入和移动性管理功能实体进行统一数据管理功能实体选择之后，还包括：
所述接入和移动性管理功能实体解除与更新之前接入的统一数据管理功能实体的关联。
可选的，所述接入和移动性管理功能实体解除与更新之前接入的统一数据管理功能实体的关联，包括：
所述接入和移动性管理功能实体通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联。
可选的，在所述接入和移动性管理功能实体根据所述第一路由更新指示进行统一数据管理功能实体选择之后，还包括：
所述接入和移动性管理功能实体确定更新后所述用户设备接入的目标统一数据管理功能实体，并关联到所述目标统一数据管理功能实体。
可选的，所述接入和移动性管理功能实体关联到所述目标统一数据管理功能，包括：
所述接入和移动性管理功能实体通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能。
可选的，该方法还包括：
所述接入和移动性管理功能实体向会话管理功能实体发送第二路由更新指示，以使所述会话管理功能实体在接收到所述第二路由更新指示后确定路由更新后所述用户设备接入的目标统一数据管理功能实体。
可选的，所述会话管理功能实体在接收到所述第二路由更新指示后确定路由更新后所述用户设备接入的目标统一数据管理功能实体之后，还包括：
所述会话管理功能实体解除与更新之前接入的统一数据管理功能实体的关联以及关联到选择出的目标统一数据管理功能实体。
第十方面，本申请实施例提供一种用户设备，包括：处理器、存储器和收发机；
其中，所述处理器，用于读取存储器中的程序并执行：
接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第二信息；
在接收到所述第二信息后向所述接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求，以使所述接入和移动性管理功能实体在接收到所述第一路由更新指示后进行统一数据管理功能实体选择。
可选的，所述第一路由更新指示用于指示所述注册更新请求用于路由更新。
可选的，所述第一路由更新指示中还包含更新后的路由信息。
第十一方面，本申请实施例提供一种接入和移动性管理功能实体，包括：处理器、存储器和收发机；
其中，所述处理器，用于读取存储器中的程序并执行：
接收用户设备发送的包含第一路由更新指示的注册更新请求；
进行统一数据管理功能实体选择。
可选的，所述处理器还用于：
在进行统一数据管理功能实体选择之后，解除与更新之前接入的统一数据管理功能实体的关联。
可选的，所述处理器具体用于：
通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联。
可选的，所述处理器还用于：
在根据所述第一路由更新指示进行统一数据管理功能实体选择之后，确定更新后所述用户设备接入的目标统一数据管理功能实体，并关联到所述目标统一数据管理功能实体。
可选的，所述处理器具体用于：
通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能。
可选的，所述处理器还用于：
向会话管理功能实体发送第二路由更新指示，以使所述会话管理功能实体在接收到所述第二路由更新指示后确定更新后所述用户设备接入的目标统一数据管理功能实体。
第十二方面，本申请实施例提供一种用户设备，包括：
第二接收模块，用于接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第二信息；
第二发送模块，用于在接收到所述第二信息后向所述接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求，以使所述接入和移动性管理功能实体在接收到所述第一路由更新指示后进行统一数据管理功能实体选择。
可选的，所述第一路由更新指示用于指示所述注册更新请求用于路由更新。
可选的，所述第一路由更新指示中还包含更新后的路由信息。
第十三方面，本申请实施例提供一种接入和移动性管理功能实体，包括：
第三接收模块，用于接收用户设备发送的包含第一路由更新指示的注册更新请求；
选择模块，用于进行统一数据管理功能实体选择。
可选的，所述选择模块还用于：
在进行统一数据管理功能实体选择之后，解除与更新之前接入的统一数据管理功能实体的关联。
可选的，所述选择模块具体用于：
通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联。
可选的，所述选择模块还用于：
在根据所述第一路由更新指示进行统一数据管理功能实体选择之后，确定更新后所述用户设备接入的目标统一数据管理功能实体，并关联到所述目标统一数据管理功能实体。
可选的，所述选择模块具体用于：
通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能。
可选的，所述选择模块还用于：
向会话管理功能实体发送第二路由更新指示，以使所述会话管理功能实体在接收到所述第二路由更新指示后确定更新后所述用户设备接入的目标统一数据管理功能实体。
第十四方面，本申请实施例提供一种计算机可存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述第八方面所述方法的步骤，或如上述第九方面所述方法的步骤。
由于本申请实施例用户设备在接收到接入和移动性管理功能实体发送的第二信息后，确定用户设备路由更新；用户设备发起注册更新请求。在用户设备路由更新后，通过用户设备发起注册更新请求的方式，核心网内部重新选择统一数据管理功能实体，实现核心网内部用户路由的更新，进一步提高系统性能。
附图说明
图1为本申请实施例系统架构示意图；
图2为本申请实施例第一种用户路由更新系统结构示意图；
图3为本申请实施例第一种进行用户路由更新的流程图；
图4为本申请实施例第二种进行用户路由更新的流程图；
图5为本申请实施例第一种用户设备结构示意图；
图6为本申请实施例第一种统一数据管理功能实体结构示意图；
图7为本申请实施例第二种用户设备结构示意图；
图8为本申请实施例第二种统一数据管理功能实体结构示意图；
图9为本申请实施例第一种用户路由更新方法流程图；
图10为本申请实施例第二种用户路由更新方法流程图；
图11为本申请实施例第二种用户路由更新系统结构示意图；
图12为本申请实施例注册类型示意图；
图13为本申请实施例第三种进行用户路由更新的流程图；
图14为本申请实施例第四种进行用户路由更新的流程图；
图15为本申请实施例第三种用户设备结构示意图；
图16为本申请实施例第一种接入和移动性管理功能实体结构示意图；
图17为本申请实施例第四种用户设备结构示意图；
图18为本申请实施例第二种接入和移动性管理功能实体结构示意图；
图19为本申请实施例第三种用户路由更新方法；
图20为本申请实施例第四种用户路由更新方法。
具体实施方式
以下，对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
(1)本申请实施例中，名词“网络”和“系统”经常交替使用，但本领域的技术人员可以理解其含义。
(2)本申请实施例中术语“多个”是指两个或两个以上，其它量词与之类似。
(3)“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本申请保护的范围。
下面将结合附图对本申请作进一步地详细描述。
图1示例性示出了适用于本申请实施例的一种系统架构示意图，如图1所示，在未来的5G系统架构中，终端101可以经接入网实体102与核心网进行通信，终端可以指UE、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端等。图1中为方便描述，只示例出1个终端，实际网络中，可能存在多个终端共存，在此不再赘述。
接入网(Access Network，AN)实体102，接入网实体也可以称之为无线接入网((Radio)Access Network，(R)AN)实体，以下统称为接入网实体或(R)AN实体，主要负责为终端101提供无线连接，保证终端101的上下行数据的可靠传输等。接入网实体102可为5G系统中的下一代基站(generation Node B，gNB)，可以是全球移动通讯(Global System of Mobile communication，GSM)系统或码分多址(Code Division Multiple Access，CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统中的基站(NodeB，NB)，还可以是长期演进(Long Term Evolution，LTE)系统中的演进型基站(Evolutional Node B，eNB或eNodeB)等。
会话管理功能(Session Management Function,SMF)实体103，该实体可以用于执行LTE系统中移动性管理实体(Mobility Management Entity，MME)的部分功能，主要负责为终端101建立会话、管理会话等。可以根据终端101的位置信息为终端101选择合适的用户面功能(User Plane Function，UPF)实体。
用户面功能实体104，是终端101用户面的功能网元，主要功能包括分组路由和转发，用户面数据的服务质量(Quality of Service，QoS)处理等。
接入和移动性管理功能实体105，主要功能包括无线接入网络控制平面的终结点，非接入信令的终结点，移动性管理，合法监听，接入授权或鉴权等等。
策略控制功能(Policy Control Funtion，PCF)实体106，主要负责用户面传输路径的建立、释放和更改等功能。
鉴权服务器功能(Authentication Server Function,AUSF)实体107，其主要功能包括用户鉴权等。
统一数据管理功能(Unified Data Management Function,UDMF)实体108，主要负责管理用户的签约数据等。
数据网络(Data Network，DN)109可以是指为终端101提供服务的网络，比如有些DN可以为终端101提供上网功能，有些DN可以为终端101提供彩信功能。
需要说明的是，上述系统架构仅是对本申请实施例适用系统架构的举例说明，本申请实施例适用的系统架构相比图1所示的系统架构还可以增加其它实体，或减少部分实体。
本申请实施例在更新用户路由时，在核心网内部进行网元选择，例如，接入和移动性管理功能实体选择统一数据管理功能实体，会话管理功能实体选择统一数据管理功能实体；在确定用户设备接入的统一数据管理功能需要变化后，本申请实施例提供了自动用户路由更新的方法。
如图2所示，本申请实施例第一种用户路由更新系统，包括：用户设备10、统一数据管理功能实体11。
用户设备10，用于接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起重新注册流程；
统一数据管理功能实体11，用于通过接入和移动性管理功能实体向所述用户设备发送用于通知所述用户设备触发路由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
本申请实施例统一数据管理功能实体在确定需要进行用户设备路由更新后，向接入和移动性管理功能实体发送第一信息，接入和移动性管理功能实体在接收到该第一信息后，将该第一信息转发给用户设备。
这里需要说明的是，本申请实施例中用户设备路由更新，在UE侧也可以称为路由标识(Routing ID)路由更新，在核心网内部可以称为Routing ID路由更新，也可以称为统一数据管理功能实体变化，二者均可以表示用户设备接入的统一数据管理功能实体发生变化。
本申请实施例中路由信息，在用户设备侧也可以称为Routing ID信息，在核心网内部可以称为Routing ID信息；或者路由信息还可以是表示用户设备接入的统一数据管理功能实体的其他信息。
可选的，第一信息包含下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册流程和注册流程的指示。
本申请实施例用户设备在接收接入和移动性管理功能实体发送的第一信息后，发起去注册和注册流程；
具体的，用户设备根据下列方式发起去注册流程：
用户设备通过发起路由更新获得的5G-GUTI发起去注册流程，触发核心网侧将更新路由前建立的UE的5G移动性管理(5G Mobility Management,5GMM)和5G会话管理(5G Session Management,5GSM)上下文及其关联信息包括跟第一统一数据管理功能实体关联 的信息等删除，即核心网侧删除与更新前路由对应的SUPI相关的上下文信息和相关关联信息。
用户设备根据下列方式发起注册流程：
用户设备根据所述更新后的路由信息，确定包含所述更新后的路由信息的SUCI；用户设备通过包含所述更新后的路由信息的SUCI发起初始注册过程。
在采用本申请实施例提供的方法时，统一数据管理功能实体需要将更新后的路由信息通过该第一信息发送给用户设备。
这里需要说明的是，本申请实施例用户设备在发起初始注册过程中，采用包含更新后的路由信息的SUCI；另外，用户设备采用包含更新后的路由信息的SUCI进行初始注册过程与现有技术中用户设备发起初始注册过程相同，在此不再详细赘述。
本申请实施例提供的用户路由更新方法适用于用户设备注册过程中进行用户路由更新，也适用于用户设备注册完成后进行用户路由更新，下面结合不同的过程分别进行说明。
一、用户设备注册过程中进行用户路由更新。
结合附图3，说明本申请实施例在用户设备注册过程中进行用户路由更新的流程。
假设更新路由之前鉴权服务器功能实体选择出的统一数据管理功能实体为第一统一数据管理功能实体，更新路由之后用户设备接入的统一数据管理功能实体为第二统一数据管理功能实体。
步骤301、用户设备发起初始注册请求；其中，该初始注册请求中携带的用户标识为SUCI。
步骤302、接入和移动性管理功能实体根据SUCI中的PLMN(Public Land Mobile Network，公共陆地移动网络)和路由信息选择认证节点选择功能实体。
步骤303、网络侧对用户进行认证，在认证授权过程中鉴权服务器功能实体根据SUCI中的PLMN和路由信息选择合适的统一数据管理功能实体，在完成认证过程之后，鉴权服务器功能实体返回用户的SUPI信息给接入和移动性管理功能实体。接入和移动性管理功能为用户设备以SUPI为索引建立5GMM上下文。
步骤304、接入和移动性管理功能实体根据SUPI信息，与第一统一数据管理功能实体完成用户注册、获取签约数据进行用户订阅等操作，并更新UE的5GMM上下文。
步骤305、第一统一数据管理功能实体确定需要更新用户设备的路由，第一统一数据管理功能实体向接入和移动性管理功能实体发送用于通知所述用户设备触发路由更新的第一信息；
这里需要说明的是，第一统一数据管理功能实体发送给接入和移动性管理功能实体第一信息后，接入和移动性管理功能实体需要将该第一信息转发给用户设备。
步骤306、接入和移动性管理功能实体为用户设备分配5G-GUTI并将相关信息保存在 UE的5GMM上下文中，发送包含5G-GUTI和第一信息的注册接受消息给UE，完成注册流程；
其中，该第一信息中包含更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册和注册流程的指示。
步骤307、用户设备在接收到包含第一信息的注册接受消息后发起去注册流程；
具体的，将用户设备在核心网与更新前第一统一数据管理功能实体相关联的信息删除；例如用户设备的5GMM上下文、5GSM上下文。
步骤308、用户设备采用包含更新后的路由信息的SUCI发起初始注册过程，建立与第二统一数据管理功能实体关联的5GMM上下文；
需要说明的是，在用户设备需要建立会话时，为用户设备建立相应的会话并与第二统一数据管理功能实体关联。
二、用户设备注册完成后进行用户路由更新。
结合附图4，说明本申请实施例在用户设备注册完成后进行用户路由更新的流程。
假设更新路由前用户设备接入的统一数据管理功能实体为第一统一数据管理功能实体，更新路由之后用户设备接入的统一数据管理功能实体为第二统一数据管理功能实体。
步骤401、第一统一数据管理功能实体向接入和移动性管理功能实体发送用于通知用户设备触发路由更新的第一信息；
其中，第一统一数据管理功能实体确定需要更新用户设备接入的统一数据管理功能实体后，向接入和移动性管理功能实体发送该第一信息；例如，运营商需要对用户设备的用户数据库进行搬迁，则第一统一数据管理功能实体向接入和移动性管理功能实体发送该用于通知用户设备触发路由更新的第一信息。
步骤402、接入和移动性管理功能实体将该第一信息转发给用户设备；
具体的，接入和移动性管理功能实体通过非接入层(Non Access Stratum,NAS)传输(transport)消息的方式将该第一信息转发给用户设备；
其中，第一信息中包含更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册和注册流程的指示。
步骤403、用户设备记录更新后的路由信息，并向接入和移动性管理功能实体返回响应消息；
在接入和移动性管理功能实体通过下行NAS传输(DL NAS transport)消息的方式将该第一信息转发给用户设备时，用户设备通过上行NAS传输(UL NAS transport)向接入和移动性管理功能实体返回响应。
步骤404、接入和移动性管理功能实体将用户设备返回的响应消息转发给第一统一数据管理功能实体。
步骤405、用户设备发起去注册流程；
具体的，用户设备发起去注册流程，其中携带5G-GUTI，接入和移动性管理功能实体通过5G-GUTI找到用户设备相关的上下文及其相关信息，进一步的，接入和移动性管理功能实体将用户设备与更新前第一统一数据管理功能实体相关联的信息删除，如果用户设备已经建立会话，则接入和移动性管理功能实体会触发其上文中记录的关联的会话管理功能实体删除该用户设备相关的信息。即删除用户设备在核心网中的相关信息包括例如用户设备的5GMM上下文、5GSM上下文。
步骤406、用户设备采用包含更新后的路由信息的SUCI发起初始注册过程，建立与第二统一数据管理功能实体关联的5GMM上下文；
需要说明的是，在用户设备需要建立会话时，为用户设备建立相应的会话并与第二统一数据管理功能实体关联。
如图5所示，本申请实施例第一种用户设备，包括：处理器500、存储器501、收发机502以及总线接口。
处理器500负责管理总线架构和通常的处理，存储器501可以存储处理器500在执行操作时所使用的数据。收发机502用于在处理器500的控制下接收和发送数据。
总线架构可以包括任意数量的互联的总线和桥，具体由处理器500代表的一个或多个处理器和存储器501代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。处理器500负责管理总线架构和通常的处理，存储器501可以存储处理器500在执行操作时所使用的数据。
本申请实施例揭示的流程，可以应用于处理器500中，或者由处理器500实现。在实现过程中，信号处理流程的各步骤可以通过处理器500中的硬件的集成逻辑电路或者软件形式的指令完成。处理器500可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器501，处理器500读取存储器501中的信息，结合其硬件完成信号处理流程的步骤。
具体地，处理器500，用于读取存储器501中的程序并执行：
接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；
在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册流程和注册流程的指示。
可选的，所述处理器500具体用于：
根据所述更新后的路由信息，确定包含所述更新后的路由信息的SUCI；根据包含所述更新后的路由信息的SUCI发起初始注册过程。
如图6所示，本申请实施例第一种统一数据管理功能实体，包括：处理器600、存储器601、收发机602以及总线接口。
处理器600负责管理总线架构和通常的处理，存储器601可以存储处理器600在执行操作时所使用的数据。收发机602用于在处理器600的控制下接收和发送数据。
总线架构可以包括任意数量的互联的总线和桥，具体由处理器600代表的一个或多个处理器和存储器601代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。处理器600负责管理总线架构和通常的处理，存储器601可以存储处理器600在执行操作时所使用的数据。
本申请实施例揭示的流程，可以应用于处理器600中，或者由处理器600实现。在实现过程中，信号处理流程的各步骤可以通过处理器600中的硬件的集成逻辑电路或者软件形式的指令完成。处理器600可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器601，处理器600读取存储器601中的信息，结合其硬件完成信号处理流程的步骤。
具体地，处理器600，用于读取存储器601中的程序并执行：
通过接入和移动性管理功能实体向所述用户设备发送用于通知所述用户设备触发路由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册和注册流程的指示。
如图7所示，本申请实施例第二种用户设备，包括：
第一接收模块701，用于接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；
第一处理模块702，用于在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册流程和注册流程的指示。
可选的，第一处理模块702具体用于：
根据所述更新后的路由信息，确定包含所述更新后的路由信息的SUCI；
根据包含所述更新后的路由信息的SUCI发起初始注册过程。
如图8所示，本申请实施例第二种统一数据管理功能实体，包括：
第一发送模块801，用于通过接入和移动性管理功能实体向所述用户设备发送用于通知所述用户设备触发路由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程；
第二处理模块802，用于控制所述发送模块发送所述第一信息。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册和注册流程的指示。
本申请实施例提供一种计算机可存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述用户设备侧所述方法的步骤，或上述统一数据管理功能实体测所述方法的步骤。
基于同一发明构思，本申请实施例中提供一种用户路由更新方法，由于该方法对应的是本申请实施例用户路由更新系统中用户设备侧的方法，并且该方法解决问题的原理与该系统相似，因此该方法的实施可以参见系统的实施，重复之处不再赘述。
如图9所示，本申请实施例第一种用户路由更新方法，该方法包括：
步骤901、用户设备接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；
步骤902、所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册流程和注册流程的指示。
可选的，所述用户设备发起注册流程，包括：
所述用户设备根据所述更新后的路由信息，确定包含所述更新后的路由信息的SUCI；
所述用户设备根据包含所述更新后的路由信息的SUCI发起初始注册过程。
如图10所示，本申请实施例第二种用户路由更新方法，该方法包括：
步骤1001、统一数据管理功能实体确定用户设备路由更新；
步骤1002、统一数据管理功能实体通过接入和移动性管理功能实体向所述用户设备发送用于通知所述用户设备触发路由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
可选的，所述第一信息中包括下列信息中的部分或全部：
更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册和注册流程的指示。
如图11所示，本申请实施例第二种用户路由更新系统，包括：用户设备110、接入和移动性管理功能实体111和统一数据管理功能实体112。
统一数据管理功能实体112，用于通过接入和移动性管理功能实体向所述用户设备发送用于通知所述用户设备触发路由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起注册更新流程；
用户设备110，用于接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；在接收到所述第一信息后向所述接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求，以使所述接入和移动性管理功能实体在接收到所述第一路由更新指示后进行统一数据管理功能实体选择；
接入和移动性管理功能实体111，用于接收用户设备发送的包含第一路由更新指示的注册更新请求，并进行统一数据管理功能实体选择。
本申请实施例统一数据管理功能实体在确定需要进行用户设备路由更新后，向接入和移动性管理功能实体发送第一信息，接入和移动性管理功能实体在接收到该第一信息后，将该第一信息转发给用户设备。
这里需要说明的是，本申请实施例中用户设备路由更新，在UE侧也可以称为路由更新，在核心网内部可以称为路由更新，也可以称为统一数据管理功能实体变化，二者均可以表示用户设备接入的统一数据管理功能实体发生变化。
具体的，本申请实施例用户设备在发起注册更新操作时，向接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求；其中，该第一路由更新指示用于触发接入和移动性管理功能实体进行统一数据管理功能实体选择。
可选的，第一路由更新指示用于触发接入和移动性管理功能实体在接收到所述注册更新请求时进行统一数据管理功能实体选择进而进行路由更新。
实施中，第一路由更新指示信息在注册更新请求中的表现形式可以为：
1、通过扩展的注册类型进行表示。
在现有的注册类型的基础上增加一个注册类型，具体可以是增加“更新参数注册更新”的注册类型；在注册请求消息中的注册类型为更新参数类型时，由于存在多种能够进行更新的参数；因此，在采用该表现形式时，还需要在注册更新请求中携带更新的参数为路由的指示。
例如，现有的注册类型包括初始注册类型、移动注册更新类型、周期性注册更新类型、紧急注册类型；在现有注册类型基础上扩展“更新参数注册更新”的注册类型；如图12所示，采用三个比特位表示注册类型，其中，000表示初始注册类型，010表示移动注册更新类型，011表示周期性注册更新类型、100表示紧急注册类型，111表示更新参数注册更新类型。
在表示注册类型的比特位上为111时，表示当前注册更新请求用于更新参数；在该注册更新请求中携带更新的参数为路由的指示时，接入和移动性管理功能实体能够确定该注册更新请求用于路由更新。
2、第一路由更新指示信息通过特定参数表示；
具体的，在注册更新请求中携带一个特定参数，在该注册请求中包含该特定参数时，表示该注册更新请求用于路由更新。
接入和移动性管理功能实体在接收到用户设备发送的包含第一路由更新指示的注册更新请求后，进行统一数据管理功能实体选择。
具体的，接入和移动性管理功能实体根据用户设备对应的SUPI进行统一数据管理功能实体选择。
本申请实施例接入和移动性管理功能实体记录有用户设备在更新路由之前接入的统一数据管理功能实体，接入和移动性管理功能实体在根据SUPI选择统一数据管理功能实体之后，比较记录的统一数据管理功能实体和选择到的目标统一数据管理功能实体，若记录的统一数据管理功能实体和目标统一数据管理功能实体不同，则接入和移动性管理功能确定接入的统一数据管理功能实体发生变化。
这里需要说明的是，由于在统一数据管理功能实体确定需要触发用户设备路由更新后，可以通过后台修改用户设备的配置参数，假设用户设备在路由更新之前接入第一统一数据管理功能实体，在确定需要触发用户设备路由更新后，会将用户设备接入的统一数据管理功能实体修改为第二统一数据管理功能实体；那么，接入和移动性管理功能实体在接收到用户设备发送的注册更新请求后，根据用户设备的SUPI选择到的统一数据管理功能实体为第二统一数据管理功能实体，接入和移动性管理功能实体确定用户设备接入的统一数据管理功能实体发生变化。
可选的，接入和移动性管理功能实体在确定统一数据管理功能实体发生变化后，解除与更新之前接入的统一数据管理功能实体的关联。
实施中，接入和移动性管理功能实体通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联。
可选的，接入和移动性管理功能实体根据用户设备的SUPI确定出更新后用户设备接入的目标统一数据管理功能实体，并关联到所述目标统一数据管理功能；
实施中，所述接入和移动性管理功能实体通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能，由于接入和移动性管理功能已经用户设备相关的上下文信息，因此与目标统一数据管理功能的关联可以不需要从统一数据管理功能重新获取用户设备的签约数据，只需要更新接入和移动性管理功能与目标统一数据管理功能进行绑定完成到目标统一数据管理功能的订阅即可。接入和移动性管理功能也可以照注册流程包括从目标统一数据管理功能重新获取用户设备的签约数据并完成相关的订阅。
需要说明的是，在接入和移动性管理功能实体关联到目标统一数据管理功能实体之后，该接入和移动性管理功能实体将记录的统一数据管理功能实体变更为目标统一数据管理功能实体。
在用户设备已建立会话后发生路由更新时，接入和移动性管理功能实体与更新前接入的统一数据管理功能实体解除关联并关联到目标统一数据管理功能实体之后，接入和移动性管理功能实体还需要通知会话管理功能实体该用户设备路由更新；
可选的，接入和移动性管理功能实体向会话管理功能实体发送第二路由更新指示，以使所述会话管理功能实体在接收到所述第二路由更新指示后确定路由更新后所述用户设备接入的目标统一数据管理功能实体，并解除与更新之前接入的统一数据管理功能实体的关联以及关联到选择出的目标统一数据管理功能实体。
实施中，接入和移动性管理功能实体根据用户设备的5GMM上下文信息，确定关联的会话管理功能实体，向该会话管理功能实体发送第二路由更新指示；其中第二路由更新指示用于表示用户设备的路由更新；
相应的，会话管理功能实体在接收到该第二路由更新指示后，根据用户设备的SUPI选择目标统一数据管理功能实体；并比较记录的统一数据管理功能实体与目标统一数据管理功能实体，在记录的统一数据管理功能实体与目标统一数据管理功能实体不同时，确定统一数据管理功能发生变化；
会话管理功能实体接收到的第二路由更新指示中还可以包含目标统一数据管理功能相关信息，则会话管理功能实体则可以根据第二路由更新指示直接确定更新后所述用户设备接入的目标统一数据管理功能实体；并比较记录的统一数据管理功能实体与目标统一数据管理功能实体，在记录的统一数据管理功能实体与目标统一数据管理功能实体不同时， 确定统一数据管理功能实体发生变化；所述目标统一数据管理功能实体相关信息可以是接入和移动性管理功能实体选择的目标统一数据管理功能实体的IP地址或者标识信息。
会话管理功能实体在确定统一数据管理功能发生变化后，解除与更新之前接入的统一数据管理功能实体的关联并关联到选择出的目标统一数据管理功能实体。实施中，会话管理功能实体通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联，会话管理功能实体通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能实体，由于会话管理功能实体已经有用户设备相关的上下文信息，因此与目标统一数据管理功能实体的关联可以不需要从统一数据管理功能实体重新获取用户设备的签约数据，仅更新接入和移动性管理功能实体与目标统一数据管理功能实体进行绑定完成到目标统一数据管理功能实体的订阅即可。会话管理功能实体也可以按照注册流程处理，具体的包括从目标统一数据管理功能实体重新获取用户设备的签约数据并完成相关的订阅。
需要说明的是，在会话管理功能实体关联到目标统一数据管理功能实体之后，该会话管理功能实体将记录的统一数据管理功能实体变更为目标统一数据管理功能实体。
本申请实施例提供的用户路由更新方法适用于用户设备注册过程中进行用户路由更新，也适用于用户设备注册完成后进行用户路由更新，下面结合不同的过程分别进行说明。
一、用户设备注册过程中进行用户路由更新。
结合附图13，说明本申请实施例在用户设备注册过程中进行用户路由更新的流程。
假设更新路由之前鉴权服务器功能实体选择出的统一数据管理功能实体为第一统一数据管理功能实体，更新路由之后用户设备接入的目标统一数据管理功能实体为第二统一数据管理功能实体。
步骤1301、用户设备发起初始注册请求；其中，该初始注册请求中携带的用户标识为SUCI。
步骤1302、接入和移动性管理功能实体根据SUCI中的PLMN(Public Land Mobile Network，公共陆地移动网络)和路由信息选择合适的鉴权服务器功能实体。
步骤1303、网络侧对用户进行认证，在认证授权过程中鉴权服务器功能实体根据SUCI中的PLMN和路由信息选择合适的统一数据管理功能实体，在完成认证过程之后，鉴权服务器功能实体返回用户的SUPI信息给接入和移动性管理功能实体。接入和移动性管理功能为UE以SUPI为索引建立5GMM上下文。
步骤1304、接入和移动性管理功能实体根据SUPI信息，与第一统一数据管理功能实体完成用户注册、获取签约数据进行用户订阅等操作，并更新UE的5GMM上下文。
步骤1305、第一统一数据管理功能实体确定需要更新用户设备的路由，第一统一数据管理功能实体向接入和移动性管理功能实体发送用于通知所述用户设备触发路由更新的 第二信息；
这里需要说明的是，第一统一数据管理功能实体发送给接入和移动性管理功能实体第二信息后，接入和移动性管理功能实体需要将该第二信息转发给用户设备。
步骤1306、接入和移动性管理功能实体为用户设备分配5G-GUTI并将相关信息保存在UE的5GMM上下文中，发送包含5G-GUTI和第二信息的注册接受消息给UE，完成注册流程。
步骤1307、用户设备在接收到包含第二信息的注册接受消息后，向接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求；
其中，第一路由更新指示可以是通过独立参数或者包含在别的参数中，其目的就是触发接入和移动性管理功能实体在接收到注册请求之后触发统一数据管理功能实体选择。例如可以通过扩展注册类型增加参数更新的注册更新类型，并携带更新参数为路由的指示；也可以直接携带一个参数指示该注册更新用于路由更新等。更新后的路由也可以在指示信息中携带。
步骤1308、接入和移动性管理功能实体进行统一数据管理功能实体选择，并确定统一数据管理功能发生变化；
具体的，接入和移动性管理功能实体根据用户设备的SUPI进行选择，选择出第二统一数据管理功能实体；接入和移动性管理功能实体确定记录的第一统一数据管理功能实体和选择出的第二统一数据管理功能实体不同，则接入和移动性管理功能实体确定统一数据管理功能实体发生变化。
如果接入和移动性管理功能实体进行判断之后统一数据管理功能实体没有发生变化则忽略后续步骤，即不需要接触与第一统一数据管理功能实体的关联，和关联到第二统一数据管理功能实体的处理。
步骤1309、接入和移动性管理功能实体根据记录的第一统一数据管理功能实体，解除与第一统一数据管理功能实体的关联。
步骤1310、接入和移动性管理功能实体关联到第二统一数据管理功能实体，并将记录的统一数据管理功能实体变更为第二统一数据管理功能实体。
需要说明的是，在用户设备需要建立会话时，为用户设备建立相应的会话并与第二统一数据管理功能实体关联。
二、用户设备注册完成后进行用户路由更新。
结合附图14，说明本申请实施例在用户设备注册完成后进行用户路由更新的流程。
假设更新路由之前鉴权服务器功能实体选择出的统一数据管理功能实体为第一统一数据管理功能实体，更新路由之后用户设备接入的目标统一数据管理功能实体为第二统一数据管理功能实体。
步骤1401、第一统一数据管理功能实体向接入和移动性管理功能实体发送用于通知用户设备触发路由更新的第二信息；
其中，第一统一数据管理功能实体确定需要更新用户设备接入的统一数据管理功能实体后，向接入和移动性管理功能实体发送该第二信息；例如，运营商需要对用户设备的用户数据库进行搬迁，则第一统一数据管理功能实体向接入和移动性管理功能实体发送该用于通知用户设备触发路由更新的第二信息。
步骤1402、接入和移动性管理功能实体将该第二信息转发给用户设备；
具体的，接入和移动性管理功能实体通过NAS transport消息的方式将该第二信息转发给用户设备；
或者，接入和移动性管理功能是还可以通过空间下载技术(Over-the-Air Technology,OTA)的方式将第二信息转发给用户设备。
步骤1403、用户设备记录更新后的路由信息，并向接入和移动性管理功能实体返回响应消息；
在接入和移动性管理功能实体通过NAS transport消息的方式将该第二信息转发给用户设备时，用户设备通过NAS transport向接入和移动性管理功能实体返回响应。
步骤1404、接入和移动性管理功能实体将用户设备返回的响应消息转发给第一统一数据管理功能实体。
步骤1405、用户设备向接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求；
其中，第一路由更新指示可以是通过独立参数或者包含在别的参数中，其目的就是触发接入和移动性管理功能实体在接收到注册请求之后触发统一数据管理功能实体选择。例如可以通过扩展注册类型增加参数更新的注册更新类型，并携带更新参数为路由的指示；也可以直接携带一个参数指示该注册更新用于路由更新等。更新后的路由也可以在指示信息中携带。
步骤1406、接入和移动性管理功能实体进行统一数据管理功能实体选择，并确定统一数据管理功能实体发生变化；
具体的，接入和移动性管理功能实体根据用户设备的SUPI进行选择，选择出第二统一数据管理功能实体；接入和移动性管理功能实体确定记录的第一统一数据管理功能实体和选择出的第二统一数据管理功能实体不同，则接入和移动性管理功能实体确定统一数据管理功能实体发生变化。
如果接入和移动性管理功能实体进行判断之后统一数据管理功能实体没有发生变化则忽略后续步骤，即不需要接触与第一统一数据管理功能实体的关联，和关联到第二统一数据管理功能实体的处理，也不需要发起到会话管理功能实体的路由更新处理。
步骤1407、接入和移动性管理功能实体根据记录的第一统一数据管理功能实体，解除与第一统一数据管理功能实体的关联。
步骤1408、接入和移动性管理功能实体关联到第二统一数据管理功能实体，并将记录的统一数据管理功能实体变更为第二统一数据管理功能实体。
步骤1409、接入和移动性管理功能实体根据用户设备的5GMM上下文信息，确定关联的会话管理功能实体，向该会话管理功能实体发送第二路由更新指示；
其中第二路由更新指示用于表示用户设备的路由更新。
步骤1410、会话管理功能实体在接收到该第二路由更新指示后，确定用户设备的目标统一数据管理功能实体；
其中，目标统一数据管理功能实体的确定可以是会话管理功能实体接收到第二路由更新指示后触发根据SUPI选择的，也可以是接入和移动性管理功能实体告知会话管理功能实体的。
步骤1411、会话管理功能实体确定统一数据管理功能发生变化，会话管理功能实体解除与第一统一数据管理功能实体的关联；
其中，会话管理功能实体根据确定的目标统一数据管理功能即第二统一数据管理功能实体，会话管理功能实体比较记录的第一统一数据管理功能实体与选择出的第二统一数据管理功能实体，确定统一数据管理功能发生变化；
会话管理功能实体通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联。
步骤1412、会话管理功能实体关联到第二统一数据管理功能实体，并将记录的统一数据管理功能实体变更为第二统一数据管理功能实体。
其中，会话管理功能实体通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能，由于会话管理功能实体已经有用户设备相关的上下文信息，因此与目标统一数据管理功能实体的关联可以不需要从源统一数据管理功能实体重新获取用户设备的签约数据，仅更新接入和移动性管理功能实体与目标统一数据管理功能实体进行绑定完成到目标统一数据管理功能实体的订阅即可。会话管理功能实体也可以按照注册流程处理，包括从目标统一数据管理功能实体重新获取用户设备的签约数据并完成相关的订阅。
如图15所示，本申请实施例第三种用户设备，包括：处理器1500、存储器1501、收发机1502以及总线接口。
处理器1500负责管理总线架构和通常的处理，存储器1501可以存储处理器1500在执行操作时所使用的数据。收发机1502用于在处理器1500的控制下接收和发送数据。
总线架构可以包括任意数量的互联的总线和桥，具体由处理器1500代表的一个或多个处理器和存储器1501代表的存储器的各种电路链接在一起。总线架构还可以将诸如外 围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。处理器1500负责管理总线架构和通常的处理，存储器1501可以存储处理器1500在执行操作时所使用的数据。
本申请实施例揭示的流程，可以应用于处理器1500中，或者由处理器1500实现。在实现过程中，信号处理流程的各步骤可以通过处理器1500中的硬件的集成逻辑电路或者软件形式的指令完成。处理器1500可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1501，处理器1500读取存储器1501中的信息，结合其硬件完成信号处理流程的步骤。
具体地，处理器1500，用于读取存储器1501中的程序并执行：
接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第二信息；
在接收到所述第二信息后向所述接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求，以使所述接入和移动性管理功能实体在接收到所述第一路由更新指示后进行统一数据管理功能实体选择。
可选的，所述第一路由更新指示用于指示所述注册更新请求用于路由更新。
可选的，所述第一路由更新指示中还包含更新后的路由信息。
如图16所示，本申请实施例提供一种接入和移动性管理功能实体，包括：处理器1600、存储器1601、收发机1602以及总线接口。
处理器1600负责管理总线架构和通常的处理，存储器1601可以存储处理器1600在执行操作时所使用的数据。收发机1602用于在处理器1600的控制下接收和发送数据。
总线架构可以包括任意数量的互联的总线和桥，具体由处理器1600代表的一个或多个处理器和存储器1601代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。处理器1600负责管理总线架构和通常的处理，存储器1601可以存储处理器1600在执行操作时所使用的数据。
本申请实施例揭示的流程，可以应用于处理器1600中，或者由处理器1600实现。在实现过程中，信号处理流程的各步骤可以通过处理器1600中的硬件的集成逻辑电路或者软件形式的指令完成。处理器1600可以是通用处理器、数字信号处理器、专用集成电路、 现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1601，处理器1600读取存储器1601中的信息，结合其硬件完成信号处理流程的步骤。
具体地，处理器1600，用于读取存储器1601中的程序并执行：
接收用户设备发送的包含第一路由更新指示的注册更新请求；
进行统一数据管理功能实体选择。
可选的，所述处理器1600还用于：
在进行统一数据管理功能实体选择之后，解除与更新之前接入的统一数据管理功能实体的关联。
可选的，所述处理器1600具体用于：
通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联。
可选的，所述处理器1600还用于：
在根据所述第一路由更新指示进行统一数据管理功能实体选择之后，确定更新后所述用户设备接入的目标统一数据管理功能实体，并关联到所述目标统一数据管理功能实体。
可选的，所述处理器1600具体用于：
通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能。
可选的，所述处理器1600还用于：
向会话管理功能实体发送第二路由更新指示，以使所述会话管理功能实体在接收到所述第二路由更新指示后确定更新后所述用户设备接入的目标统一数据管理功能实体。
如图17所示，本申请实施例一种用户设备，包括：
第二接收模块1701，用于接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第二信息；
第二发送模块1702，用于在接收到所述第二信息后向所述接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求，以使所述接入和移动性管理功能实体在接收到所述第一路由更新指示后进行统一数据管理功能实体选择。
可选的，所述第一路由更新指示用于指示所述注册更新请求用于路由更新。
可选的，所述第一路由更新指示中还包含更新后的路由信息。
如图18所示，本申请实施例一种接入和移动性管理功能实体，包括：
第三接收模块1801，用于接收用户设备发送的包含第一路由更新指示的注册更新请求；
选择模块1802，用于进行统一数据管理功能实体选择。
可选的，所述选择模块1802还用于：
在进行统一数据管理功能实体选择之后，解除与更新之前接入的统一数据管理功能实体的关联。
可选的，所述选择模块1802具体用于：
通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联。
可选的，所述选择模块1802还用于：
在根据所述第一路由更新指示进行统一数据管理功能实体选择之后，确定更新后所述用户设备接入的目标统一数据管理功能实体，并关联到所述目标统一数据管理功能实体。
可选的，所述选择模块1802具体用于：
通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能。
可选的，所述选择模块1802还用于：
向会话管理功能实体发送第二路由更新指示，以使所述会话管理功能实体在接收到所述第二路由更新指示后确定更新后所述用户设备接入的目标统一数据管理功能实体。
本申请实施例提供一种计算机可存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述用户设备侧所述方法的步骤，或上述接入和移动性管理功能实体侧所述方法的步骤。
基于同一发明构思，本申请实施例中提供一种用户路由更新方法，由于该方法对应的是本申请实施例用户路由更新系统中用户设备侧的方法，并且该方法解决问题的原理与该系统相似，因此该方法的实施可以参见系统的实施，重复之处不再赘述。
如图19所示，本申请实施例提供一种用户路由更新方法，该方法包括：
步骤1901、用户设备接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第二信息；
步骤1902、所述用户设备在接收到所述第二信息后向所述接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求，以使所述接入和移动性管理功能实体在接收到所述第一路由更新指示后进行统一数据管理功能实体选择。
可选的，所述第一路由更新指示用于指示所述注册更新请求用于路由更新。
可选的，所述第一路由更新指示中还包含更新后的路由信息。
基于同一发明构思，本申请实施例中提供一种用户路由更新方法，由于该方法对应的是本申请实施例用户路由更新系统中接入和移动性管理功能实体侧的方法，并且该方法解决问题的原理与该系统相似，因此该方法的实施可以参见系统的实施，重复之处不再赘述。
如图20所示，本申请实施例提供一种用户路由更新方法，该方法包括：
步骤2001、接入和移动性管理功能实体接收用户设备发送的包含第一路由更新指示的注册更新请求；
步骤2002、所述接入和移动性管理功能实体进行统一数据管理功能实体选择。
可选的，在所述接入和移动性管理功能实体进行统一数据管理功能实体选择之后，还包括：
所述接入和移动性管理功能实体解除与更新之前接入的统一数据管理功能实体的关联。
可选的，所述接入和移动性管理功能实体解除与更新之前接入的统一数据管理功能实体的关联，包括：
所述接入和移动性管理功能实体通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联。
可选的，在所述接入和移动性管理功能实体根据所述第一路由更新指示进行统一数据管理功能实体选择之后，还包括：
所述接入和移动性管理功能实体确定更新后所述用户设备接入的目标统一数据管理功能实体，并关联到所述目标统一数据管理功能实体。
可选的，所述接入和移动性管理功能实体关联到所述目标统一数据管理功能，包括：
所述接入和移动性管理功能实体通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能。
可选的，该方法还包括：
所述接入和移动性管理功能实体向会话管理功能实体发送第二路由更新指示，以使所述会话管理功能实体在接收到所述第二路由更新指示后确定更新后所述用户设备接入的目标统一数据管理功能实体。
可选的，所述会话管理功能实体在接收到所述第二路由更新指示后确定路由更新后所述用户设备接入的目标统一数据管理功能实体之后，还包括：
所述会话管理功能实体解除与更新之前接入的统一数据管理功能实体的关联以及关联到选择出的目标统一数据管理功能实体。
所述计算机存储介质可以是计算机能够存取的任何可用介质或数据存储设备，包括但不限于磁性存储器(例如软盘、硬盘、磁带、磁光盘(MO)等)、光学存储器(例如CD、DVD、BD、HVD等)、以及半导体存储器(例如ROM、EPROM、EEPROM、非易失性存储器(NAND FLASH)、固态硬盘(SSD))等。
以上参照示出根据本申请实施例的方法、装置(系统)和/或计算机程序产品的框图和/或流程图描述本申请。应理解，可以通过计算机程序指令来实现框图和/或流程图示图的 一个块以及框图和/或流程图示图的块的组合。可以将这些计算机程序指令提供给通用计算机、专用计算机的处理器和/或其它可编程数据处理装置，以产生机器，使得经由计算机处理器和/或其它可编程数据处理装置执行的指令创建用于实现框图和/或流程图块中所指定的功能/动作的方法。
相应地，还可以用硬件和/或软件(包括固件、驻留软件、微码等)来实施本申请。更进一步地，本申请可以采取计算机可使用或计算机可读存储介质上的计算机程序产品的形式，其具有在介质中实现的计算机可使用或计算机可读程序代码，以由指令执行系统来使用或结合指令执行系统而使用。在本申请上下文中，计算机可使用或计算机可读介质可以是任意介质，其可以包含、存储、通信、传输、或传送程序，以由指令执行系统、装置或设备使用，或结合指令执行系统、装置或设备使用。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (35)

  1. 一种用户路由更新方法，其特征在于，该方法包括：
    用户设备接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；
    所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
  2. 如权利要求1所述的方法，其特征在于，所述第一信息中包括下列信息中的部分或全部：
    更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册流程和注册流程的指示。
  3. 如权利要求2所述的方法，其特征在于，所述用户设备发起注册流程，包括：
    所述用户设备根据所述更新后的路由信息，确定包含所述更新后的路由信息的SUCI；
    所述用户设备根据包含所述更新后的路由信息的SUCI发起初始注册过程。
  4. 一种用户路由更新方法，其特征在于，该方法包括：
    统一数据管理功能实体通过接入和移动性管理功能实体向用户设备发送用于通知所述用户设备触发路由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
  5. 如权利要求4所述的方法，其特征在于，所述第一信息中包括下列信息中的部分或全部：
    更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册和注册流程的指示。
  6. 一种用户设备，其特征在于，包括：处理器、存储器和收发机；
    其中，所述处理器，用于读取存储器中的程序并执行：
    接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；
    在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
  7. 如权利要求6所述的用户设备，其特征在于，所述第一信息中包括下列信息中的部分或全部：
    更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册流程和注册流程的指示。
  8. 如权利要求7所述的用户设备，其特征在于，所述处理器具体用于：
    根据所述更新后的路由信息，确定包含所述更新后的路由信息的SUCI；根据包含所述更新后的路由信息的SUCI发起初始注册过程。
  9. 一种统一数据管理功能实体，其特征在于，包括：处理器、存储器和收发机；
    其中，所述处理器，用于读取存储器中的程序并执行：
    通过接入和移动性管理功能实体向所述用户设备发送用于通知用户设备触发路由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
  10. 如权利要求9所述的统一数据管理功能实体，其特征在于，所述第一信息中包括下列信息中的部分或全部：
    更新后的路由信息、表示是否需要用户设备响应的指示、表示需要用户设备发起去注册和注册流程的指示。
  11. 一种用户设备，其特征在于，包括：
    第一接收模块，用于接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第一信息；
    第一处理模块，用于在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程。
  12. 一种统一数据管理功能实体，其特征在于，包括：
    第一发送模块，用于通过接入和移动性管理功能实体向用户设备发送用于通知所述用户设备触发路由更新的第一信息，以使所述用户设备在接收到所述第一信息后发起去注册流程，并在去注册流程完成后发起注册流程；
    第二处理模块，用于控制所述发送模块发送所述第一信息。
  13. 一种计算机可存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现如权利要求1～3任一所述方法的步骤，或如权利要求4或5所述方法的步骤。
  14. 一种用户路由更新方法，其特征在于，该方法包括：
    用户设备接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第二信息；
    所述用户设备在接收到所述第二信息后向所述接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求，以使所述接入和移动性管理功能实体在接收到所述第一路由更新指示后进行统一数据管理功能实体选择。
  15. 如权利要求14所述的方法，其特征在于，所述第一路由更新指示用于指示所述注册更新请求用于路由更新。
  16. 如权利要求14所述的方法，其特征在于，所述第一路由更新指示中还包含更新后的路由信息。
  17. 一种用户路由更新方法，其特征在于，该方法包括：
    接入和移动性管理功能实体接收用户设备发送的包含第一路由更新指示的注册更新 请求；
    所述接入和移动性管理功能实体进行统一数据管理功能实体选择。
  18. 如权利要求17所述的方法，其特征在于，在所述接入和移动性管理功能实体进行统一数据管理功能实体选择之后，还包括：
    所述接入和移动性管理功能实体解除与更新之前接入的统一数据管理功能实体的关联。
  19. 如权利要求18所述的方法，其特征在于，所述接入和移动性管理功能实体解除与更新之前接入的统一数据管理功能实体的关联，包括：
    所述接入和移动性管理功能实体通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联。
  20. 如权利要求17所述的方法，其特征在于，在所述接入和移动性管理功能实体根据所述第一路由更新指示进行统一数据管理功能实体选择之后，还包括：
    所述接入和移动性管理功能实体确定更新后所述用户设备接入的目标统一数据管理功能实体，并关联到所述目标统一数据管理功能实体。
  21. 如权利要求20所述的方法，其特征在于，所述接入和移动性管理功能实体关联到所述目标统一数据管理功能，包括：
    所述接入和移动性管理功能实体通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能。
  22. 如权利要求17所述的方法，其特征在于，该方法还包括：
    所述接入和移动性管理功能实体向会话管理功能实体发送第二路由更新指示，以使所述会话管理功能实体在接收到所述第二路由更新指示后确定路由更新后所述用户设备接入的目标统一数据管理功能实体。
  23. 如权利要求22所述的方法，其特征在于，所述会话管理功能实体在接收到所述第二路由更新指示后确定路由更新后所述用户设备接入的目标统一数据管理功能实体之后，还包括：
    所述会话管理功能实体解除与更新之前接入的统一数据管理功能实体的关联以及关联到选择出的目标统一数据管理功能实体。
  24. 一种用户设备，其特征在于，包括：处理器、存储器和收发机；
    其中，所述处理器，用于读取存储器中的程序并执行：
    接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第二信息；
    在接收到所述第二信息后向所述接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求，以使所述接入和移动性管理功能实体在接收到所述第一路由更新指 示后进行统一数据管理功能实体选择。
  25. 如权利要求24所述的用户设备，其特征在于，所述第一路由更新指示用于指示所述注册更新请求用于路由更新。
  26. 如权利要求24所述的用户设备，其特征在于，所述第一路由更新指示中还包含更新后的路由信息。
  27. 一种接入和移动性管理功能实体，其特征在于，包括：处理器、存储器和收发机；
    其中，所述处理器，用于读取存储器中的程序并执行：
    接收用户设备发送的包含第一路由更新指示的注册更新请求；
    进行统一数据管理功能实体选择。
  28. 如权利要求27所述的接入和移动性管理功能实体，其特征在于，所述处理器还用于：
    在进行统一数据管理功能实体选择之后，解除与更新之前接入的统一数据管理功能实体的关联。
  29. 如权利要求28所述的接入和移动性管理功能实体，其特征在于，所述处理器具体用于：
    通过特定的去注册流程或者去订阅流程解除与更新之前接入的统一数据管理功能实体的关联。
  30. 如权利要求27所述的接入和移动性管理功能实体，其特征在于，所述处理器还用于：
    在根据所述第一路由更新指示进行统一数据管理功能实体选择之后，确定更新后所述用户设备接入的目标统一数据管理功能实体，并关联到所述目标统一数据管理功能实体。
  31. 如权利要求30所述的接入和移动性管理功能实体，其特征在于，所述处理器具体用于：
    通过特定的注册流程或者订阅流程关联到所述目标统一数据管理功能。
  32. 如权利要求27所述的接入和移动性管理功能实体，其特征在于，所述处理器还用于：
    向会话管理功能实体发送第二路由更新指示，以使所述会话管理功能实体在接收到所述第二路由更新指示后确定路由更新后所述用户设备接入的目标统一数据管理功能实体。
  33. 一种用户设备，其特征在于，包括：
    第二接收模块，用于接收统一数据管理功能实体通过接入和移动性管理功能实体发送的用于通知所述用户设备路由更新的第二信息；
    第二发送模块，用于在接收到所述第二信息后向所述接入和移动性管理功能实体发送包含第一路由更新指示的注册更新请求，以使所述接入和移动性管理功能实体在接收到所 述第一路由更新指示后进行统一数据管理功能实体选择。
  34. 一种接入和移动性管理功能实体，其特征在于，包括：
    第三接收模块，用于接收用户设备发送的包含第一路由更新指示的注册更新请求；
    选择模块，用于进行统一数据管理功能实体选择。
  35. 一种计算机可存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现如权利要求14～16任一所述方法的步骤，或如权利要求17～23任一所述方法的步骤。
PCT/CN2019/118918 2018-11-19 2019-11-15 一种用户路由更新方法及设备 Ceased WO2020103773A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811378541.2A CN111200857B (zh) 2018-11-19 2018-11-19 一种用户路由更新方法及设备
CN201811378541.2 2018-11-19

Publications (1)

Publication Number Publication Date
WO2020103773A1 true WO2020103773A1 (zh) 2020-05-28

Family

ID=70747307

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/118918 Ceased WO2020103773A1 (zh) 2018-11-19 2019-11-15 一种用户路由更新方法及设备

Country Status (2)

Country Link
CN (2) CN116669140A (zh)
WO (1) WO2020103773A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111638997A (zh) * 2020-05-28 2020-09-08 中国联合网络通信集团有限公司 数据恢复方法、装置及网络设备
CN112291752B (zh) * 2020-11-16 2022-08-12 中国联合网络通信集团有限公司 一种网络注册方法及装置
CN114867098B (zh) * 2021-02-03 2024-09-13 中国电信股份有限公司 用于5g网络中的用户设备的去注册的方法、udm网元、以及存储介质
CN120835286A (zh) * 2024-04-19 2025-10-24 中兴通讯股份有限公司 通信方法、装置、存储介质及计算机程序产品

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018097601A1 (ko) * 2016-11-27 2018-05-31 엘지전자(주) 무선 통신 시스템에서의 등록 해제 방법 및 이를 위한 장치

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101437219B (zh) * 2007-11-12 2011-04-20 华为技术有限公司 一种终端的移动性管理方法及设备
CN102100114B (zh) * 2009-09-30 2013-12-04 华为技术有限公司 一种移动性管理的方法和终端设备
US10397892B2 (en) * 2017-02-06 2019-08-27 Huawei Technologies Co., Ltd. Network registration and network slice selection system and method
CN108574969B (zh) * 2017-03-08 2021-04-09 华为技术有限公司 多接入场景中的连接处理方法和装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018097601A1 (ko) * 2016-11-27 2018-05-31 엘지전자(주) 무선 통신 시스템에서의 등록 해제 방법 및 이를 위한 장치

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
CATT: "Discussion on Routing ID Update", SA WG2 MEETING #S2-129BIS, S2-1812140, 20 November 2018 (2018-11-20), XP051498869 *
CATT: "Update to UDM Discovery", 3GPP TSG-SA WG2 MEETING #127BIS, S2-185251, 27 May 2018 (2018-05-27), XP051448750 *
NOKIA ET AL.: "23.501: AUSF, UDM, UDR Discovery", SA WG2 MEETING #128BIS, S2-188094, 14 August 2018 (2018-08-14), XP051537033 *
NOKIA ET AL.: "Comments to LS on Routing ID CP-182238", 3GPP TSG SA3 MEETING #92BIS, S3-183050, 19 September 2018 (2018-09-19), XP051541100 *
QUALCOMM INCORPORATED ET AL.: "Update of Default Configured NSSAI and Other UE Parameters via Control Plane Solution from UDM to AMF with Direct NAS Transport to UE", SA WG2 MEETING #S2-129, S2-1811267, 17 October 2018 (2018-10-17), XP051540111 *
QUALCOMM INCORPORATED: "Update of Routing ID in the UE", SA WG2 MEETING #129, S2-1810060, 9 October 2018 (2018-10-09), XP051539057 *

Also Published As

Publication number Publication date
CN111200857A (zh) 2020-05-26
CN111200857B (zh) 2023-06-30
CN116669140A (zh) 2023-08-29

Similar Documents

Publication Publication Date Title
US11737045B2 (en) Connection processing method and apparatus in multi-access scenario
US10873889B2 (en) Handover apparatus and method
EP3745746B1 (en) Communication method and apparatus
CN109219111B (zh) 切片选择方法和装置
CN109699072B (zh) 通信方法、装置和系统
CN112312539B (zh) 策略控制功能网元的选择方法、装置、系统及存储介质
CN110366216B (zh) 通信的方法和通信装置
CN110366241A (zh) 通信方法、装置和系统
CN112655244B (zh) 一种业务处理方法、设备及存储介质
WO2018161796A1 (zh) 多接入场景中的连接处理方法和装置
US11317274B2 (en) Access and mobility management policy association termination method and apparatus
CN109309904B (zh) 组播数据传输方法、相关设备及通信系统
CN111200857B (zh) 一种用户路由更新方法及设备
WO2020001226A1 (zh) 重定向的方法、通信系统和通信装置
CN103229525B (zh) 一种处理封闭用户组签约数据请求的方法、设备和系统
WO2023051430A1 (zh) 通信的方法和装置
CN109788511A (zh) 终端的网络变更方法及核心网设备
TW202015440A (zh) 無線通訊的方法和設備
CN115776487A (zh) 数据分流方法、装置、设备及存储介质
WO2024017069A1 (zh) 定位方法、装置及存储介质
WO2021088007A1 (zh) 无线通信的方法、终端设备和网络设备
JP6473171B2 (ja) Ｍｓｃ間ハンドオーバのためのｍａｐを介したｉｍｅｉｓｖの指示
WO2023040958A1 (zh) 一种联邦学习组处理方法、装置及功能实体
CN115314958A (zh) QoE测量的配置方法、设备、装置及存储介质
WO2020103086A1 (zh) 无线通信方法、网络节点和终端设备

Legal Events

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

Ref document number: 19886705

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19886705

Country of ref document: EP

Kind code of ref document: A1