WO2020103773A1

WO2020103773A1 - User route updating method and device

Info

Publication number: WO2020103773A1
Application number: PCT/CN2019/118918
Authority: WO
Inventors: 唐廷芳; 艾明; 王胡成
Original assignee: 电信科学技术研究院有限公司
Priority date: 2018-11-19
Filing date: 2019-11-15
Publication date: 2020-05-28
Also published as: CN111200857B; CN116669140A; CN111200857A

Abstract

The present application relates to the technical field of wireless communications, and in particular, to a user route updating method and device, for use in solving the problem in the prior art of no solution to automatically update user routes. In embodiments of the present application, a user equipment receives first information which is sent by a unified data management function entity by means of an access and mobility management function entity and used for notifying the user equipment of a route update; initiates a deregistration process after receiving the first information, and initiates a registration process after the deregistration process is completed. After the route of a user equipment is updated, the user equipment initiates a deregistration process, and a core network internally releases the connection to the unified data management function entity before the update; and the user equipment initiates a registration process to update the user route inside the core network; thus, the system performance is further improved.

Description

User routing update method and equipment

This application requires the priority of the Chinese patent application filed on November 19, 2018 in the Chinese Patent Office with the application number 201811378541.2 and the application name "a user route update method and device", the entire contents of which are incorporated by reference in this application in.

Technical field

This application relates to the field of wireless communication technology, and in particular, to a user route update method and device.

Background technique

At present, SUPI (Subscription, Permanent Identifier, User Permanent Identifier) in the fifth-generation mobile communication technology (5th-Generation, 5G) system is not transmitted on the air interface, and the initial registration request message for the interaction between UE (User Equipment) and the network uses SUCI Subscription Concealed Identifier (user hidden identifier), where SUCI is encrypted SUPI, both SUCI and SUPI are used to identify the user. During the authentication process, the AUSF (Authentication, Unit, Selection, Function, AMMF) entity returns the SUPI to the Access and Mobility Management Function (Access and Mobility Management Function) entity. In the subsequent process, 5G The core network uses SUPI to identify the UE. For example, the access and mobility management function entity selects a unified data management function (Unified Data Management (UDM) entity according to SUPI, and the session management function (Session Management Function, SMF) entity selects a unified entity according to SUPI. 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.

At present, according to the needs of operators, there are scenarios in which the user database of some users needs to be relocated from the unified data management functional entity to another unified data management functional entity. The existing method is to change the configuration data in the background. This method requires a lot of manpower and resources to be wasted, and the user routing update period is long. Therefore, at present, how to implement automatic update of user routes has become an urgent problem to be solved.

Summary of the invention

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.

Based on the above problem, in a first aspect, 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.

Optionally, 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.

Optionally, 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.

In a second aspect, 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 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.

In a third aspect, an embodiment of the present application provides user equipment, including: a processor, a memory, and a transceiver;

Wherein, the processor is used to read the program in the memory and execute:

Receiving 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 de-registration process is initiated, and after the de-registration process is completed, a registration process is initiated.

Optionally, the processor is specifically used to:

According 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.

According to a fourth aspect, an embodiment of the present application provides a unified data management functional entity, including: a processor, a memory, and a transceiver;

Wherein, the processor is used to read the program in the memory and execute:

Sending, through the access and mobility management function entity, first information for notifying the user equipment to trigger route update to the user equipment, so that the user equipment initiates a deregistration process after receiving the first information, And initiate the registration process after the de-registration process is completed.

According to a fifth aspect, 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.

Optionally, the processing module is specifically used for:

Determine the SUCI containing the updated routing information according to the updated routing information;

The initial registration process is initiated according to the SUCI containing the updated routing information.

According to a sixth aspect, 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.

According to a seventh aspect, 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.

In the embodiment of the present application, after receiving the first information sent by the access and mobility management function entity, the user equipment 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. After 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.

According to an eighth aspect, 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;

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.

Optionally, the first route update indication is used to indicate that the registration update request is used for route update.

Optionally, the first route update instruction further includes updated route information.

In a ninth aspect, 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.

Optionally, after the access and mobility management function entity performs unified data management function 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.

Optionally, 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.

Optionally, after the access and mobility management function entity performs unified data management function entity selection according to the first route update instruction, 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.

Optionally, 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.

Optionally, 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.

Optionally, 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.

According to a tenth aspect, an embodiment of the present application provides user equipment, including: a processor, a memory, and a transceiver;

Wherein, the processor is used to read the program in the memory and execute:

Receiving 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;

After receiving the second information, send a registration update request including a first route update instruction to the access and mobility management function entity, so that the access and mobility management function entity receives the first After a routing update instruction, the entity selection of the unified data management function is performed.

According to an eleventh aspect, an embodiment of the present application provides an access and mobility management functional entity, including: a processor, a memory, and a transceiver;

Wherein, the processor is used to read the program in the memory and execute:

Receiving a registration update request sent by the user equipment and containing the first route update instruction;

Perform entity selection for unified data management functions.

Optionally, the processor is also used to:

After the unified data management function entity selection is performed, the association with the unified data management function entity accessed before the update is disassociated.

Optionally, the processor is specifically used to:

Disassociate with the unified data management function entity accessed before the update through a specific de-registration process or de-subscription process.

Optionally, the processor is also used to:

After the unified data management function entity selection is performed according to the first route update instruction, 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.

Optionally, the processor is specifically used to:

The target unified data management function is associated with a specific registration process or subscription process.

Optionally, the processor is also used to:

Sending a second route update instruction to the session management function entity, so that the session management function entity determines the target unified data management function entity that the user equipment accesses after the update after receiving the second route update instruction.

According to a twelfth aspect, 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.

In a thirteenth aspect, an embodiment of the present application provides 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.

Optionally, the selection module is also used to:

Optionally, the selection module is specifically used for:

Optionally, the selection module is also used to:

Optionally, the selection module is specifically used for:

Optionally, the selection module is also used to:

According to a fourteenth aspect, 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.

In this embodiment of the present application, 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.

BRIEF DESCRIPTION

1 is a schematic diagram of a system architecture of an embodiment of this application;

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;

6 is a schematic structural diagram of a first unified data management function entity according to an embodiment of this application;

7 is a schematic structural diagram of a second user equipment according to an embodiment of this application;

8 is a schematic structural diagram of a second unified data management function entity according to an embodiment of this application;

9 is a flowchart of a first user route update method according to an embodiment of this application;

10 is a flowchart of a second user route update method according to an embodiment of this application;

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;

17 is a schematic structural diagram of a fourth user equipment according to an embodiment of this application;

18 is a schematic structural diagram of a second entity of access and mobility management functions according to an embodiment of the present application;

19 is a third user route update method according to an embodiment of this application;

FIG. 20 is a fourth user route update method according to an embodiment of this application.

detailed description

Hereinafter, some terms in the embodiments of the present application will be explained to facilitate understanding by those skilled in the art.

(1) In the embodiments of the present application, the terms "network" and "system" are often used interchangeably, but those skilled in the art can understand the meaning.

(2) In the embodiments of the present application, the term "plurality" refers to two or more, and other quantifiers are similar.

(3) "and / or", describing the relationship of related objects, indicating that there can be three types of relationships, for example, A and / or B, which can indicate: there are A alone, A and B, and B alone Happening. The character "/" generally indicates that the related object is a "or" relationship.

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.

In order to make the purpose, technical solutions and advantages of the present application more clear, the present application will be described in further detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in this application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of this application.

The present application will be described in further detail below with reference to the drawings.

FIG. 1 exemplarily shows a schematic diagram of a system architecture applicable to an embodiment of the present application. As shown in FIG. 1, in a future 5G system architecture, 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. 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. 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) The base station (Base Transceiver Station, BTS) in the system can also be the base station (NodeB, NB) in the wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, or the long term evolution (LTE) Evolutionary base station (Evolutional Node B, eNB or eNodeB) in the system, etc.

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.

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. For example, some DNs may provide an Internet access function for terminal 101, and some DNs may provide MMS function for terminal 101.

It should be noted that the above 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.

In the embodiment 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.

As shown in FIG. 2, the first user route update system according to an embodiment of the present application 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.

In the embodiment of the present application, 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.

It should be noted here that in the embodiment of the present application, 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.

In the embodiment of the present application, after receiving the first information sent by the access and mobility management function entity, the user equipment initiates a de-registration and registration process;

Specifically, 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.

When the method provided by the embodiment of the present application is adopted, the unified data management function entity needs to send the updated routing information to the user equipment through the first information.

It should be noted here that during the initial registration process, 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.

1. User routing update during user device registration.

With reference to FIG. 3, a flow of user route update during a user equipment registration process according to an embodiment of the present application is described.

It is assumed that 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, and 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.

Step 303: The network side authenticates the user. During the authentication and authorization process, the authentication server functional entity selects a suitable unified data management functional entity based on the PLMN and routing information in SUCI. 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;

It should be noted here that after the first unified data management functional entity sends the first information to the access and mobility management functional entity, 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;

Wherein, 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;

Specifically, 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;

It should be noted that, when the user equipment needs to establish a session, a corresponding session is established for the user equipment and associated with the second unified data management function entity.

2. The user routing update is performed after the user device registration is completed.

With reference to FIG. 4, the process of updating the user route after the user equipment registration is completed in the embodiment of the present application is described.

It is assumed that the unified data management functional entity accessed by the user equipment before the route update is the first unified data management functional entity, and 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 When the relocation is performed, 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;

Specifically, 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;

Wherein, 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;

When 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;

Specifically, 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;

As shown in FIG. 5, the first user equipment according to an embodiment of the present application 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. In the implementation process, 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.

Specifically, the processor 500 is configured to read the program in the memory 501 and execute:

Optionally, the processor 500 is specifically used to:

As shown in FIG. 6, 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. In the implementation process, 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. 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 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.

Specifically, the processor 600 is configured to read the program in the memory 601 and execute:

Sending, through the access and mobility management function entity, first information for notifying the user equipment to trigger route update to the user equipment, so that the user equipment initiates a de-registration process after receiving the first information, And initiate the registration process after the de-registration process is completed.

As shown in FIG. 7, the second user equipment according to an embodiment of the present application 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.

Optionally, the first processing module 702 is specifically used to:

As shown in FIG. 8, 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.

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 .

Based on the same inventive concept, 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.

As shown in FIG. 9, the first user route update method according to an embodiment of the present application 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.

Optionally, the user equipment initiates a registration process, including:

As shown in FIG. 10, a second user route update method according to an embodiment of the present application 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.

As shown in FIG. 11, a second user route update system according to an embodiment of the present application 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.

It should be noted here that in the embodiment of the present application, 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.

Specifically, when initiating the registration update operation, the user equipment in the embodiment of the present application 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.

Optionally, 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.

In implementation, the manifestation form of the first route update indication information in the registration update request may be:

1. Represented by the extended registration type.

Add a registration type on the basis of the existing registration type, which can specifically be the registration type of "update parameter registration update"; when the registration type in the registration request message is the update parameter type, there are multiple types that can be updated Parameters; therefore, when adopting this representation form, it is also necessary to carry the updated parameter as an indication of routing in the registration update request.

For example, 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.

When the bit indicating the type of registration is 111, it means that the current registration update request is used to update the parameters; when the registration update request carries the updated parameter as an indication of routing, the access and mobility management function entity can determine the registration Update requests are used for routing updates.

2. The first routing update indication information is indicated by specific parameters;

Specifically, 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.

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.

Specifically, the access and mobility management functional entity selects the unified data management functional entity according to the SUPI corresponding to the user equipment.

In the embodiment of the present application, 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.

It should be noted here that after the unified data management functional entity determines that the user equipment needs to be triggered to update the route, the configuration parameters of the user equipment can be modified through the background. After it is determined that the routing update of the user equipment needs to be triggered, 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 After the request, 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.

Optionally, after determining that the unified data management functional entity has changed, the access and mobility management functional entity disassociates from the unified data management functional entity accessed before the update.

During implementation, 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.

Optionally, 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;

In implementation, 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.

It should be noted that after the access and mobility management functional entity is associated with the target unified data management functional entity, the access and mobility management functional entity changes the recorded unified data management functional entity to the target unified data management functional entity.

When the routing update occurs after the user equipment has established a session, 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;

Optionally, 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.

In implementation, 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;

Correspondingly, after receiving the second routing update instruction, 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. When 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. When the recorded unified data management functional entity is different from the target unified data management functional entity, it is determined that the unified data management functional entity changes; 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.

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. During implementation, 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. 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.

It should be noted that after the session management functional entity is associated with the target unified data management functional entity, the session management functional entity changes the recorded unified data management functional entity to the target unified data management functional entity.

1. User routing update during user device registration.

With reference to FIG. 13, the process of updating the user route during the registration of the user equipment according to the embodiment of the present application is described.

It is assumed that 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, and 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.

Step 1303: The network side authenticates the user. During the authentication and authorization process, the authentication server functional entity selects a suitable unified data management functional entity based on the PLMN and routing information in SUCI. 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;

It should be noted here that after the first unified data management functional entity sends the second information to the access and mobility management functional entity, 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;

Wherein, 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. For example, 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;

Specifically, 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.

If 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.

With reference to FIG. 14, the process of updating the user route after the user equipment registration is completed in the embodiment of the present application is described.

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 When the relocation is performed, 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;

Specifically, the access and mobility management function entity forwards the second information to the user equipment by means of NAS transport messages;

Alternatively, the access and mobility management functions can also forward the second information to the user equipment by way of over-the-air technology (OTA).

Step 1403: The user equipment records the updated routing information and returns a response message to the access and mobility management function entity;

When 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;

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;

If 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;

Wherein, 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;

Among them, 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.

Among them, 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.

As shown in FIG. 15, 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. In the implementation process, 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.

Specifically, the processor 1500 is configured to read the program in the memory 1501 and execute:

As shown in FIG. 16, 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. In the implementation process, 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.

Specifically, the processor 1600 is used to read the program in the memory 1601 and execute:

Perform entity selection for unified data management functions.

Optionally, the processor 1600 is also used to:

Optionally, the processor 1600 is specifically used to:

Optionally, the processor 1600 is also used to:

Optionally, the processor 1600 is specifically used to:

Optionally, the processor 1600 is also used to:

As shown in FIG. 17, a user equipment according to an embodiment of the present application 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.

As shown in FIG. 18, an access and mobility management functional entity according to an embodiment of the present application 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.

Optionally, the selection module 1802 is also used to:

Optionally, the selection module 1802 is specifically used to:

Optionally, the selection module 1802 is also used to:

Optionally, the selection module 1802 is specifically used to:

Optionally, 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.

As shown in FIG. 19, 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.

Based on the same inventive concept, 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.

As shown in FIG. 20, 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.

Optionally, 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 goal of unified data management functional entities.

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.

The present application is described above with reference to block diagrams and / or flowcharts showing methods, apparatuses (systems) and / or computer program products according to embodiments of the present application. It should be understood that a block of the block diagram and / or flowchart illustration and a combination of blocks of the block diagram and / or flowchart illustration can be implemented by computer program instructions. These computer program instructions may be provided to a general-purpose computer, a dedicated computer processor, and / or other programmable data processing devices to produce a machine, such that instructions executed via the computer processor and / or other programmable data processing devices are created for A method to implement the functions / actions specified in the block diagram and / or flowchart block.

Correspondingly, the application can also be implemented in hardware and / or software (including firmware, resident software, microcode, etc.). Further, 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. In the context of this application, 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.

Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Those skilled in the art should understand that 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.

This application is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the application. It should be understood that each flow and / or block in the flowchart and / or block diagram and a combination of the flow and / or block in the flowchart and / or block diagram may be implemented by computer program instructions. 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 An apparatus for realizing the functions specified in one block or multiple blocks of one flow or multiple flows of a flowchart and / or one block or multiple blocks of a block diagram.

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.

Although the preferred embodiments of the present application have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic inventive concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

Obviously, those skilled in the art can make various modifications and variations to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. In this way, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims

A user route update method, characterized in that the method includes:

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 method of claim 1, wherein 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 method of claim 2, wherein the user equipment initiating the registration process includes:

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 user route update method, characterized in that the method includes:

The unified data management function entity sends 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 initiates The registration process, and the registration process is initiated after the de-registration process is completed.
The method according to claim 4, wherein 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 user equipment is characterized by comprising: a processor, a memory and a transceiver;

Wherein, the processor is used to read the program in the memory and execute:

Receiving 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 de-registration process is initiated, and after the de-registration process is completed, a registration process is initiated.
The user equipment according to claim 6, wherein 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 according to claim 7, wherein the processor is specifically configured to:

According 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.
A unified data management functional entity, which is characterized by comprising: a processor, a memory and a transceiver;

Wherein, the processor is used to read the program in the memory and execute:

Sending, through the access and mobility management function entity, first information for notifying the user equipment to trigger route update to the user equipment, so that the user equipment initiates a deregistration process after receiving the first information, After the registration process is completed, the registration process is initiated.
The unified data management functional entity according to claim 9, wherein 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 user equipment is characterized by comprising:

A first receiving module, configured to receive first 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;

The first 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.
A unified data management functional entity, which is characterized by including:

A first sending module, configured to send first information for informing the user equipment to trigger 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 completed;

The second processing module is used to control the sending module to send the first information.
A computer-storable medium on which a computer program is stored, characterized in that when the program is executed by a processor, the steps of the method according to any one of claims 1 to 3 or the method according to claim 4 or 5 are realized A step of.
A user route update method, characterized in that 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;

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 method of claim 14, wherein the first route update indication is used to indicate that the registration update request is used for route update.
The method of claim 14, wherein the first route update instruction further includes updated route information.
A user route update method, characterized in that 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 according to claim 17, wherein after the access and mobility management function entity performs unified data management function entity selection, the method further comprises:

The access and mobility management functional entity is disassociated from the unified data management functional entity accessed before the update.
The method of claim 18, wherein the disassociating the access and mobility management function entity from the unified data management function 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 according to claim 17, wherein after the access and mobility management function entity performs unified data management function entity selection according to the first route update instruction, the method further comprises:

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 method of claim 20, wherein 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 of claim 17, wherein the method further comprises:

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 method according to claim 22, wherein after the session management function entity determines the target unified data management function entity that the user equipment accesses after the route update after receiving the second route update instruction, include:

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.
A user equipment is characterized by comprising: a processor, a memory and a transceiver;

Wherein, the processor is used to read the program in the memory and execute:

Receiving 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;

After receiving the second information, send a registration update request including a first route update instruction to the access and mobility management function entity, so that the access and mobility management function entity receives the first After a routing update instruction, the entity selection of the unified data management function is performed.
The user equipment according to claim 24, wherein the first route update indication is used to indicate that the registration update request is used for route update.
The user equipment according to claim 24, wherein the first route update instruction further includes updated route information.
An access and mobility management functional entity, which is characterized by comprising: a processor, a memory and a transceiver;

Wherein, the processor is used to read the program in the memory and execute:

Receiving a registration update request sent by the user equipment and containing the first route update instruction;

Perform entity selection for unified data management functions.
The access and mobility management functional entity of claim 27, wherein the processor is further configured to:

After the unified data management function entity selection is performed, the association with the unified data management function entity accessed before the update is disassociated.
The access and mobility management functional entity of claim 28, wherein the processor is specifically configured to:

Disassociate with the unified data management function entity accessed before the update through a specific de-registration process or de-subscription process.
The access and mobility management functional entity of claim 27, wherein the processor is further configured to:

After the unified data management function entity selection is performed according to the first route update instruction, 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 access and mobility management functional entity according to claim 30, wherein the processor is specifically configured to:

The target unified data management function is associated with a specific registration process or subscription process.
The access and mobility management functional entity of claim 27, wherein the processor is further configured to:

Sending a second route update instruction to the session management function entity, so that the session management function entity determines the target unified data management function entity that the user equipment accesses after the route update after receiving the second route update instruction.
A user equipment is characterized by comprising:

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.
An access and mobility management functional entity, which is characterized by:

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.
A computer-storable medium on which a computer program is stored, characterized in that when the program is executed by a processor, the steps of the method according to any one of claims 14 to 16 or the method according to any of claims 17 to 23 Describe the steps of the method.