Network registration updating method, device and equipment
By introducing a network registration and update method in the 5G system, the terminal registration and update from the first core network node to the second core network node is realized, solving the challenge of registration and update between network nodes in the 6G distributed architecture, ensuring that the terminal is on the network Stable registration under demand and load changes.
Patent Information
- Application Number
- CN202310534531.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-12
AI Technical Summary
The existing 5G system cannot support network registration and updates between different network nodes, and cannot adapt to the registration and update requirements caused by changes in terminal network requirements and network load in 6G distributed architecture.
Provide a network registration and update method, perform terminal registration and update operations to the second core network node through the first core network node, including receiving terminal context requests, sending terminal context responses, sending registration messages to the terminal, carrying the registration and update reasons, and If necessary, determine the target network node and core network node to realize the interaction between new and old core network nodes.
It effectively supports terminal registration and updates from the first core network node to the second core network node, solving the problem of network registration and updates between different network nodes, ensuring that terminals can adapt to changes in network demand and load changes.
Smart Images

Figure CN118945807A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a network registration update method, device and equipment. Background Art
[0002] The current 5G mobile communication network system is natively designed for centralized control. With the development of the network, the trend of 6G network is a network architecture that combines centralized and distributed control. 6G will extend more network functions to the edge of the network and build distributed homogeneous units with different functional levels. Each distributed unit has complete control and data forwarding functions.
[0003] For the 6G distributed architecture, when the UE (terminal) network demand changes or the network load changes, and the network node where the UE is registered needs to be changed without changing the base station, the UE registration update process (involving network node changes) is triggered, and the existing 5GS (5G system) domain registration update method is not applicable.
[0004] Specifically, the mobility registration update of centralized 5GS mainly targets the changes in AMF (access and mobility management function) caused by changes in TA (tracking area) due to UE mobility, or changes in AMF when the original AMF cannot meet its needs due to UE update capabilities or protocol parameters, triggering the interaction between the old and new AMFs in a network node. However, the existing solutions are not applicable to the interaction between the old and new AMFs in different network nodes involved in the 6G distributed architecture.
[0005] As described above, the existing technology has problems such as being unable to support network registration updates between different network nodes. Summary of the invention
[0006] The purpose of the present application is to provide a network registration update method, device and equipment to solve the problem that the prior art cannot support the implementation of network registration update between different network nodes.
[0007] In order to solve the above technical problems, an embodiment of the present application provides a network registration update method, which is applied to a first core network node, including:
[0008] Execute a first operation for updating terminal registration to a second core network node;
[0009] The first core network node and the second core network node belong to different network nodes;
[0010] The first operation includes at least one of the following:
[0011] receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node;
[0012] A registration message is sent to the terminal, where the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication.
[0013] Optionally, before receiving the terminal context request sent by the second core network node, the method further includes:
[0014] Receiving a first request sent by an access network node;
[0015] Determine a target network node according to the first request, and determine a second core network node under the target network node;
[0016] Sending a second request to the second core network node;
[0017] The method further comprises:
[0018] receiving a request acceptance response fed back by the second core network node;
[0019] The first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
[0020] Optionally, determining the target network node according to the first request includes:
[0021] According to the first request, obtaining a first parameter;
[0022] Determine a target network node according to the first parameter;
[0023] The first parameter includes at least one of the following:
[0024] Alternative network node information;
[0025] Device information of the terminal;
[0026] The local node determines the strategy or the acquired node determines the strategy.
[0027] Optionally, the determining a second core network node under the target network node includes:
[0028] Determine, according to the default configuration or the first information, a second core network node under the target network node;
[0029] The first information includes at least one of the following:
[0030] Information of candidate core network nodes;
[0031] The load of the core network nodes;
[0032] Device information of the terminal;
[0033] Information about access network nodes.
[0034] Optionally, determining a target network node according to the first request, and determining a second core network node under the target network node includes:
[0035] Determining a target network node according to the first request;
[0036] A second core network node is determined according to the target network node.
[0037] Optionally, determining a target network node according to the first request, and determining a second core network node under the target network node includes:
[0038] Sending, according to the first request, a first determination request for determining a target network node and a second core network node to a centralized node or an access network node;
[0039] Receive information about the target network node and the second core network node fed back by the centralized node or the access network node.
[0040] The embodiment of the present application further provides a network registration update method, which is applied to a second core network node, including:
[0041] Sending a terminal context request to the first core network node according to the second request;
[0042] Receiving a terminal context response fed back by the first core network node;
[0043] Sending a first response or a first notification to the terminal according to the terminal context response;
[0044] Wherein, the second request is used to request registration or request registration update;
[0045] The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.
[0046] Optionally, before sending the terminal context request to the first core network node according to the second request, the method further includes:
[0047] Receive the second request sent by the first core network node or the access network node.
[0048] Optionally, also include:
[0049] Send a request acceptance response to the second request to the first core network node.
[0050] The embodiment of the present application also provides a network registration update method, which is applied to an access network node, including:
[0051] Execute a second operation for the terminal to register and update from the first core network node to the second core network node;
[0052] The first core network node and the second core network node belong to different network nodes;
[0053] The second operation includes:
[0054] Receive a first request sent by a terminal; based on the first request, send a first request to the first core network node or send a second request to the second core network node; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
[0055] Optionally, before sending the second request to the second core network node, the method further includes:
[0056] A target network node is determined according to the first request, and a second core network node under the target network node is determined.
[0057] Optionally, determining the target network node according to the first request includes:
[0058] According to the first request, obtaining a second parameter;
[0059] Determining a target network node according to the second parameter;
[0060] The second parameter includes at least one of the following:
[0061] Updated network requirement parameters;
[0062] A connection relationship with the access network node;
[0063] Maintained node information;
[0064] Device information of the terminal;
[0065] The local node determines the strategy or the acquired node determines the strategy.
[0066] Optionally, the determining a second core network node under the target network node includes:
[0067] Determine, according to the default configuration or the first information, a second core network node under the target network node;
[0068] The first information includes at least one of the following:
[0069] Information of candidate core network nodes;
[0070] The load of the core network nodes;
[0071] Device information of the terminal;
[0072] Information about access network nodes.
[0073] Optionally, determining a target network node according to the first request, and determining a second core network node under the target network node includes:
[0074] Determining a target network node according to the first request;
[0075] A second core network node is determined according to the target network node.
[0076] Optionally, determining a target network node according to the first request, and determining a second core network node under the target network node includes:
[0077] Sending, according to the first request, a second determination request for determining a target network node and a second core network node to a centralized node;
[0078] Receive the information of the target network node and the second core network node fed back by the centralized node.
[0079] The embodiment of the present application also provides a network registration update method, which is applied to a terminal, including:
[0080] Performing a third operation of registering and updating the terminal from the first core network node to the second core network node;
[0081] The first core network node and the second core network node belong to different network nodes;
[0082] The third operation includes at least one of the following:
[0083] Receiving a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication;
[0084] Receive a first response or a first notification sent by the second core network node; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification.
[0085] Optionally, also include:
[0086] Before performing the third operation of registering and updating the terminal from the first core network node to the second core network node, sending a first request to the access network node; or,
[0087] Sending a first request to an access network node according to the registration message;
[0088] The first request is used to request registration or request registration update.
[0089] The embodiment of the present application further provides a network registration update device, which is a first core network node and includes a memory, a transceiver, and a processor:
[0090] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0091] Execute a first operation for updating terminal registration to a second core network node;
[0092] The first core network node and the second core network node belong to different network nodes;
[0093] The first operation includes at least one of the following:
[0094] Receiving, by the transceiver, a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node;
[0095] A registration message is sent to the terminal through the transceiver, where the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication.
[0096] The embodiment of the present application further provides a network registration update device, which is a second core network node and includes a memory, a transceiver, and a processor:
[0097] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0098] According to the second request, sending a terminal context request to the first core network node through the transceiver;
[0099] Receiving, by the transceiver, a terminal context response fed back by the first core network node;
[0100] Sending a first response or a first notification to the terminal through the transceiver according to the terminal context response;
[0101] Wherein, the second request is used to request registration or request registration update;
[0102] The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.
[0103] The embodiment of the present application further provides a network registration update device, which is an access network node and includes a memory, a transceiver, and a processor:
[0104] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0105] Execute a second operation for the terminal to register and update from the first core network node to the second core network node;
[0106] The first core network node and the second core network node belong to different network nodes;
[0107] The second operation includes:
[0108] A first request sent by a terminal is received through the transceiver; based on the first request, a first request is sent to the first core network node or a second request is sent to the second core network node through the transceiver; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
[0109] The embodiment of the present application further provides a network registration update device, which is a terminal and includes a memory, a transceiver, and a processor:
[0110] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0111] Performing a third operation of registering and updating the terminal from the first core network node to the second core network node;
[0112] The first core network node and the second core network node belong to different network nodes;
[0113] The third operation includes at least one of the following:
[0114] Receiving, by the transceiver, a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message including: a registration request, a registration indication, a registration update request or a registration update indication;
[0115] A first response or a first notification sent by a second core network node is received through the transceiver; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification.
[0116] The embodiment of the present application further provides a network registration update device, which is applied to a first core network node, including:
[0117] A first execution unit, configured to execute a first operation for updating terminal registration to a second core network node;
[0118] The first core network node and the second core network node belong to different network nodes;
[0119] The first operation includes at least one of the following:
[0120] receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node;
[0121] A registration message is sent to the terminal, where the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication.
[0122] The embodiment of the present application further provides a network registration update device, which is applied to a second core network node, including:
[0123] A second sending unit, configured to send a terminal context request to the first core network node according to the second request;
[0124] A third receiving unit, configured to receive a terminal context response fed back by the first core network node;
[0125] A third sending unit, configured to send a first response or a first notification to the terminal according to the terminal context response;
[0126] The second request is used to request registration or request registration update;
[0127] The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.
[0128] The embodiment of the present application further provides a network registration update device, which is applied to an access network node, including:
[0129] A second execution unit, configured to execute a second operation for the terminal to register and update from the first core network node to the second core network node;
[0130] The first core network node and the second core network node belong to different network nodes;
[0131] The second operation includes:
[0132] Receive a first request sent by a terminal; based on the first request, send a first request to the first core network node or send a second request to the second core network node; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
[0133] The embodiment of the present application further provides a network registration update device, applied to a terminal, comprising:
[0134] A third execution unit, configured to execute a third operation for the terminal to register and update from the first core network node to the second core network node;
[0135] The first core network node and the second core network node belong to different network nodes;
[0136] The third operation includes at least one of the following:
[0137] Receiving a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication;
[0138] Receive a first response or a first notification sent by the second core network node; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification.
[0139] An embodiment of the present application also provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable the processor to execute the above-mentioned method on the first core network node side, the second core network node side, the access network node side or the terminal side.
[0140] The beneficial effects of the above technical solution of the present application are as follows:
[0141] In the above scheme, the network registration update method performs a first operation for terminal registration update to a second core network node; wherein the first core network node is different from the network node to which the second core network node belongs; the first operation includes at least one of the following: (1) receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node; (2) sending a registration message to the terminal, wherein the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication; and can support the interaction between the old and new core network nodes (the first core network node and the second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support the implementation of network registration update between different network nodes. BRIEF DESCRIPTION OF THE DRAWINGS
[0142] Figure 1 A schematic diagram of the wireless communication system architecture of an embodiment of the present application;
[0143] Figure 2A schematic diagram of a 6G distributed network architecture according to an embodiment of the present application;
[0144] Figure 3 The network registration update method process of the embodiment of the present application is shown as follows: Figure 1 ;
[0145] Figure 4 The network registration update method process of the embodiment of the present application is shown as follows: Figure 2 ;
[0146] Figure 5 The network registration update method process of the embodiment of the present application is shown as follows: Figure 3 ;
[0147] Figure 6 The network registration update method process of the embodiment of the present application is shown as follows: Figure 4 ;
[0148] Figure 7 The specific implementation process of the network registration update method of the embodiment of the present application is shown as follows: Figure 1 ;
[0149] Figure 8 The specific implementation process of the network registration update method of the embodiment of the present application is shown as follows: Figure 2 ;
[0150] Fig. 9 The specific implementation process of the network registration update method of the embodiment of the present application is shown as follows: Figure 3 ;
[0151] Fig.10 The specific implementation process of the network registration update method of the embodiment of the present application is shown as follows: Figure 4 ;
[0152] Fig.11 The network registration and updating device structure of the embodiment of the present application is shown as follows: Figure 1 ;
[0153] Fig.12 The network registration and updating device structure of the embodiment of the present application is shown as follows: Figure 2 ;
[0154] Fig.13 The network registration and updating device structure of the embodiment of the present application is shown as follows: Figure 3 ;
[0155] Fig.14 The network registration and updating device structure of the embodiment of the present application is shown as follows: Figure 4 ;
[0156] Fig.15 The network registration update device structure of the embodiment of the present application is shown as follows: Figure 1 ;
[0157] Fig.16 The network registration update device structure of the embodiment of the present application is shown as follows: Figure 2 ;
[0158] Fig.17 The network registration update device structure of the embodiment of the present application is shown as follows: Figure 3 ;
[0159] Fig.18 The network registration update device structure of the embodiment of the present application is shown as follows: Figure 4 . DETAILED DESCRIPTION
[0160] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0161] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.
[0162] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.
[0163] It is explained here that the technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.
[0164] Figure 1 A block diagram of a wireless communication system applicable to the embodiments of the present application is shown. The wireless communication system includes a terminal device (also referred to as a terminal) and a network device.
[0165] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). The wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it can be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDA) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.
[0166] The network device involved in the embodiment of the present application may be a base station, which may include multiple cells providing services for the terminal. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.
[0167] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.
[0168] The following first introduces the contents involved in the solution provided in the embodiment of the present application.
[0169] 1. Trends in 6G distributed architecture;
[0170] The important trend of 6G network development is centralized and distributed network architecture. The original design of 5G and previous generations of network architecture is centralized control. With the development of the network, facing the dual driving forces of business development and technological development, the design of 6G network needs to consider the distributed architecture, and its control gradually evolves towards distributed control.
[0171] Specifically, 6G networks will be oriented towards diverse scenarios and network performance requirements in the air, space, land, and sea, and centralized network architecture cannot uniformly meet all scenarios. To meet this challenge, Figure 2 As shown in the figure, the 6G network architecture needs to go beyond centralized control and gradually evolve to a distributed architecture, extending more network functions to the edge of the network, and building distributed homogeneous network nodes with different functional levels. Each network node has all the functions of complete control and data forwarding. Multiple network nodes across domains can form autonomous micro-networks according to business needs, and provide targeted network services according to specific business scenarios, user scale, geographical environment and other requirements.
[0172] 2. About the update of mobile registration in the 5GS (5G system) domain;
[0173] 5G is a centrally controlled system architecture, and the 5G registration update method is intra-domain registration update.
[0174] Currently, UE (terminal) registration includes initial registration, mobility registration update, periodic registration update, emergency registration, disaster roaming registration and other registrations.
[0175] The mobility registration update occurs in one of the following situations when the UE is in the RM (Registration Management)-REGISTERED (Registered) state:
[0176] 1) When the UE moves to a new TA (tracking area) outside the UE registration area (connected or idle state);
[0177] 2) Regardless of whether the new TA is changed, the UE needs to update the capabilities or protocol parameters it negotiated during the registration process. For example, a change in the UE's Preferred Network Behaviour will cause incompatibility with the Supported Network Behaviour provided by the serving AMF (Access and Mobility Management Function);
[0178] 3) When the UE intends to obtain LADN (local data network) information;
[0179] 4) When the NR (New Radio) satellite access changes to a suitable cell, it indicates that the RPLMN (Registered PLMN) has multiple TAs, and these TAs are outside the UE's registration area in both CM-CONNECTED (Connection Management - Connected) and CM-IDLE (Connection Management - Idle) states;
[0180] 5) When the UE in MUSIM (Multi-Universal Subscriber Identity Module) mode requires a new 5G-GUTI (Globally Unique Temporary Identity) allocation.
[0181] Specifically, the mobility registration update of 5GS is mainly aimed at the change of the service AMF caused by the change of TA due to UE mobility, or the change of the service AMF caused by the original AMF being unable to meet the needs of the UE due to the update of UE capabilities or protocol parameters. In short, the mobility registration update process of 5GS triggers the interaction between AMFs within a network node.
[0182] Based on the above, the embodiments of the present application provide a network registration update method, device and equipment to solve the problem that the prior art cannot support the network registration update between different network nodes. Among them, the method, device and equipment are based on the same application concept. Since the principles of solving the problems by the method, device and equipment are similar, the implementation of the method, device and equipment can refer to each other, and the repeated parts will not be repeated.
[0183] The network registration update method provided in the embodiment of the present application is applied to the first core network node, such as Figure 3 As shown, including:
[0184] Step 31: Execute a first operation for terminal registration update to a second core network node; wherein the first core network node is different from the network node to which the second core network node belongs; the first operation includes at least one of the following: (1) receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node; (2) sending a registration message to the terminal, the registration message carrying a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication.
[0185] Among them, the first core network node can be the core network node where the terminal is originally registered (for example, the old core network node), and the second core network node can be the core network node where the terminal is targeted to be registered (for example, the new core network node), but this is not limited to.
[0186] The network registration update method provided in the embodiment of the present application performs a first operation for terminal registration update to a second core network node; wherein the first core network node is different from the network node to which the second core network node belongs; the first operation includes at least one of the following: (1) receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node; (2) sending a registration message to the terminal, wherein the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication; and can support interaction between new and old core network nodes (first core network node and second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, thereby effectively solving the problem that the prior art cannot support network registration update between different network nodes.
[0187] Furthermore, before receiving the terminal context request sent by the second core network node, it also includes: receiving a first request (which may carry a registration reason) sent by an access network node; determining a target network node based on the first request, and determining a second core network node under the target network node; sending a second request to the second core network node; the method also includes: receiving a request acceptance response fed back by the second core network node; wherein the first request is used to request registration or request registration update; the second request is used to request registration or request registration update (the content carried by the second request is the same as or different from the content carried by the first request).
[0188] In this way, the first core network node can be supported to select the target network node and the second core network node. The first request can be a registration request with a registration type of mobile registration update, a registration request with a registration type of network demand change (adding this registration type), or a newly defined registration update request (new message, different from a registration request), but is not limited thereto.
[0189] Among them, determining the target network node according to the first request includes: obtaining a first parameter according to the first request; determining the target network node according to the first parameter; wherein the first parameter includes at least one of the following: alternative network node information; device information of the terminal; local node determination strategy or acquired node determination strategy.
[0190] In this way, the target network node can be accurately determined. Wherein, obtaining the first parameter may include: obtaining the first parameter from NAR (Node Auto Register, node automatic registration) or a centralized node, but is not limited thereto. The device information of the terminal may include: device location, device resources, device type, etc., which are not limited here.
[0191] In an embodiment of the present application, determining the second core network node under the target network node includes: determining the second core network node under the target network node according to a default configuration or first information; wherein the first information includes at least one of the following: information of candidate core network nodes; load of the core network node; device information of the terminal; information of the access network node.
[0192] In this way, the second core network node can be accurately determined.
[0193] The determining of the target network node according to the first request and the determining of the second core network node under the target network node include: determining the target network node according to the first request; and determining the second core network node according to the target network node.
[0194] In this way, the target network node and the second core network node can be selected separately; in this scheme, the target network node and the second core network node can also be selected together, for example: according to the first request, the target network node and the second core network node under the target network node are determined at the same time, but it is not limited to this.
[0195] In an embodiment of the present application, determining the target network node according to the first request, and determining the second core network node under the target network node include: sending a first determination request for determining the target network node and the second core network node to a centralized node or an access network node according to the first request; and receiving information about the target network node and the second core network node fed back by the centralized node or the access network node.
[0196] In this way, the target network node and the second core network node can be accurately determined as much as possible.
[0197] The embodiment of the present application also provides a network registration update method, which is applied to a second core network node, such as Figure 4 As shown, including:
[0198] Step 41: Send a terminal context request to the first core network node according to the second request;
[0199] Step 42: receiving a terminal context response fed back by the first core network node;
[0200] Step 43: Send a first response or a first notification to the terminal according to the terminal context response; wherein the second request is used to request registration or request registration update; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification.
[0201] Among them, the first core network node can be the core network node where the terminal is originally registered (for example, the old core network node), and the second core network node can be the core network node where the terminal is targeted to be registered (for example, the new core network node), but this is not limited to.
[0202] The network registration update method provided in the embodiment of the present application sends a terminal context request to the first core network node according to a second request; receives a terminal context response fed back by the first core network node; sends a first response or a first notification to the terminal according to the terminal context response; wherein the second request is used to request registration or request registration update; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification; and can support interaction between new and old core network nodes (first core network node and second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support network registration updates between different network nodes.
[0203] Furthermore, before sending the terminal context request to the first core network node according to the second request, it also includes: receiving the second request sent by the first core network node or the access network node.
[0204] This way the second request can be obtained accurately.
[0205] In the embodiment of the present application, the network registration update method further includes: sending a request acceptance response to the second request to the first core network node.
[0206] This ensures that a response to the second request is achieved.
[0207] The present application also provides a network registration update method, which is applied to an access network node, such as Figure 5 As shown, including:
[0208] Step 51: Execute a second operation for the terminal to register and update from the first core network node to the second core network node; wherein, the first core network node and the second core network node belong to different network nodes; the second operation includes: receiving a first request sent by the terminal; according to the first request, sending a first request to the first core network node or sending a second request to the second core network node; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update (the content carried by the second request is the same as or different from the content carried by the first request).
[0209] Among them, the first core network node can be the core network node where the terminal is originally registered (for example, the old core network node), and the second core network node can be the core network node where the terminal is targeted to be registered (for example, the new core network node), but this is not limited to.
[0210] The network registration update method provided in the embodiment of the present application performs a second operation for the terminal to register and update from a first core network node to a second core network node; wherein the first core network node and the second core network node belong to different network nodes; the second operation includes: receiving a first request sent by the terminal; according to the first request, sending a first request to the first core network node or sending a second request to the second core network node; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update; it can support the interaction between the old and new core network nodes (the first core network node and the second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support the implementation of network registration updates between different network nodes.
[0211] Furthermore, before sending the second request to the second core network node, it also includes: determining a target network node according to the first request, and determining a second core network node under the target network node.
[0212] This can support the access network node to select the target network node and the second core network node. Among them, the first request can be a registration request with a registration type of mobile registration update, or a registration request with a registration type of network demand change (adding this registration type), or a newly defined registration update request (new message, different from the registration request), but is not limited to this. In addition, the present scheme may also include: receiving a first determination request sent by the first core network node for determining the target network node and the second core network node; and feeding back information about the target network node and the second core network node to the first core network node. In this way, the first core network node can be guaranteed to accurately determine the target network node and the second core network node as much as possible.
[0213] Among them, determining the target network node according to the first request includes: obtaining a second parameter according to the first request; determining the target network node according to the second parameter; wherein the second parameter includes at least one of the following: an updated network requirement parameter; a connection relationship with the access network node; maintained node information; device information of the terminal; a local node determination strategy or an acquired node determination strategy.
[0214] In this way, the target network node can be accurately determined. The device information of the terminal may include: device location, device resources, device type, etc., which are not limited here.
[0215] In an embodiment of the present application, determining the second core network node under the target network node includes: determining the second core network node under the target network node according to a default configuration or first information; wherein the first information includes at least one of the following: information of candidate core network nodes; load of the core network node; device information of the terminal; information of the access network node.
[0216] In this way, the second core network node can be accurately determined.
[0217] The determining of the target network node according to the first request and the determining of the second core network node under the target network node include: determining the target network node according to the first request; and determining the second core network node according to the target network node.
[0218] In this way, the target network node and the second core network node can be selected separately; in this scheme, the target network node and the second core network node can also be selected together, for example: according to the first request, the target network node and the second core network node under the target network node are determined at the same time, but it is not limited to this.
[0219] In an embodiment of the present application, determining the target network node according to the first request and determining the second core network node under the target network node include: sending a second determination request for determining the target network node and the second core network node to a centralized node according to the first request; and receiving information about the target network node and the second core network node fed back by the centralized node.
[0220] In this way, the target network node and the second core network node can be accurately determined as much as possible.
[0221] The present application also provides a network registration update method, which is applied to a terminal, such as Figure 6 As shown, including:
[0222] Step 61: Execute a third operation for the terminal to update registration from the first core network node to the second core network node; wherein the first core network node is different from the network node to which the second core network node belongs; the third operation includes at least one of the following: (1) receiving a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication; (2) receiving a first response or a first notification sent by the second core network node; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification.
[0223] Among them, the first core network node can be the core network node where the terminal is originally registered (for example, the old core network node), and the second core network node can be the core network node where the terminal is targeted to be registered (for example, the new core network node), but this is not limited to.
[0224] The network registration update method provided in the embodiment of the present application performs a third operation for the terminal to register and update from a first core network node to a second core network node; wherein the first core network node and the second core network node belong to different network nodes; the third operation includes at least one of the following: (1) receiving a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication; (2) receiving a first response or a first notification sent by the second core network node; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification; it can support the interaction between the new and old core network nodes (the first core network node and the second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support the implementation of network registration updates between different network nodes.
[0225] Among them, the network registration update method also includes: before executing the third operation of registering and updating the terminal from the first core network node to the second core network node, sending a first request to the access network node; or, according to the registration message, sending a first request to the access network node; wherein the first request is used to request registration or request registration update.
[0226] This can support the terminal to actively initiate registration updates.
[0227] It is to be noted that the relevant contents of the above methods can refer to each other, and the repeated contents will not be repeated here.
[0228] The network registration update method provided in the embodiment of the present application is illustrated below, with AMF being taken as an example of the core network node.
[0229] In response to the above technical problems, the embodiment of the present application provides a network registration update method, which can be specifically implemented as a distributed network registration update method, for: when the network node currently serving cannot meet the UE demand due to changes in the UE's network demand or changes in network load, the centralized 5GS mobility registration update only supports mobility registration updates within one network node, and cannot meet the new scenario of mobile registration updates in distributed networks; facing the 6G distributed architecture, this solution expands the new scenario of registration updates between UE or network triggered network nodes in the distributed network architecture, and solves the problems of distributed network node selection and new AMF selection, information interaction, etc. in this scenario. This solution mainly involves: UE initiates registration update due to changes in demand, or the network instructs the UE to register and update to a new network node due to a state change, or the network notifies the UE after updating the UE registration to a new network node due to a state change.
[0230] The following is a specific example to illustrate this solution.
[0231] Example 1: UE initiates registration update due to demand changes;
[0232] Example 1.1: The old network node selects the new network node;
[0233] Specifically, the distributed network registration update process 1 can be as follows: Figure 7 As shown, the following steps are included:
[0234] 1. When the UE's demand for the network changes due to changes in the access service type, device type, etc., the registration update process (i.e., the registration process with the registration type of mobility registration update) is triggered, carrying the registered UE identifier (such as 5G-GUTI (globally unique temporary UE identifier)) and new demand parameters, etc. (corresponding to the above-mentioned sending of the first request to the access network node).
[0235] The message for sending the registration request may be an AN (access network) message (carrying AN parameters and a registration request);
[0236] Specifically, the registration request may carry at least one of the following parameters: registration type, SUCI (user hidden identifier) or 5G-GUTI (globally unique temporary UE identifier) or permanent equipment identifier PEI, tracking area identifier TAI last visited by the terminal (if available), security parameters, NSSAI (network slice selection assistance information) requested by the terminal, mapping of NSSAI requested by the terminal, PDU session state, active time requested by the terminal, LADN (local data network) DNN (data network name) or indicator for requesting LADN information, NAS (non-access layer) message container, preferred network behavior, UE paging probability information, UE policy container and UE radio capability ID, release request indication, and PEI.
[0237] AN parameters include: 5G-S (system)-TMSI (temporary mobile subscription identity) or GUAMI (globally unique AMF identifier), selected PLMN (public land mobile network) ID, and NSSAI information; it may also include Establishment cause, or registration cause, to provide the reason for requesting to establish an RRC (radio resource control) connection between the UE and AN.
[0238] Among them, Registration type is mobile registration update, and Preferred NetworkBehaviour is the new requirement for the network.
[0239] 2. The RAN (radio access network) forwards the registration request according to the UE identifier (such as 5G-S-TMSI or GUAMI) and the N2 (interface) connection (corresponding to sending the first request to the first core network node according to the first request).
[0240] 3. When Old AMF (corresponding to the above-mentioned first core network node) receives the registration request and parses the new requirement parameters, if it is determined that the current network node cannot meet the new requirements of the UE, it requests NAR (Node Auto Register) to obtain a list of network nodes that can meet the UE requirements (i.e., sending a node discovery request to NAR, corresponding to the above-mentioned acquisition of the first parameter according to the first request), and the request information includes the UE's locally stored parameters and newly carried parameters for network requirements; NAR can be a new network function at a network node granularity, which is used to maintain node granularity information and realize plug-and-play functions of nodes.
[0241] 4. NAR responds with a list of candidate network nodes and node information of the candidate nodes (corresponding to the above candidate network node information), that is, NAR feedback node discovery response;
[0242] 5. Old AMF performs network node selection (corresponding to determining the target network node according to the first parameter above) based on the responded network node list, the responded node information, the UE information (corresponding to the device information of the above terminal), the local policy (which may also be a policy obtained through the PCF, etc.; corresponding to the above local node determination policy or the obtained node determination policy), etc.;
[0243] 6. The Old AMF performs AMF selection in the selected network node, which may be the default configuration AMF, or may be retrieved through the NRF as the optional AMF (corresponding to the information of the candidate core network node) and based on the AMF load (corresponding to the load of the core network node), UE information (corresponding to the device information of the terminal), RAN information (corresponding to the information of the access network node), etc. to complete the AMF selection (corresponding to the above-mentioned determination of the second core network node under the target network node according to the default configuration or the first information);
[0244] 7. The Old AMF forwards the registration request to the New AMF (corresponding to the second core network node) (the message may also be forwarded through the RAN); corresponding to the sending of the second request to the second core network node;
[0245] 8. If the New AMF determines that the registration request can be accepted according to the local information, it replies with a registration acceptance (corresponding to sending a request acceptance response to the second request to the first core network node) and requests to obtain the UE context (corresponding to sending a terminal context request to the first core network node according to the second request);
[0246] 9. The Old AMF replies the UE context to the New AMF (corresponding to the above-mentioned sending of the terminal context response to the second core network node), including the AN access information; after replying the message, the locally maintained UE context may be deleted after receiving the response or after a timer time;
[0247] Among them: the above steps 7-9 can also be combined into one, and the Old AMF sends the UE context to the New AMF while sending the registration request, but it is not limited to this.
[0248] 10. The New AMF maintains the UE context and assigns a new identifier (for example, 5G-GUTI) to the UE, and replies to the UE with a registration acceptance response (the message may also be forwarded by the Old AMF); corresponding to the above response according to the terminal context, a first response is sent to the terminal.
[0249] The message in step 10 may also include a response from the New AMF to the Old AMF to inform the Old AMF that the locally maintained UE context may be deleted; and may also include AMF switching information sent by the New AMF to the RAN to notify the RAN to update the information of the Old AMF in the locally maintained UE context.
[0250] After the AMF changes, it may be necessary to update the AM Policy (Access Management Policy) and / or UE Policy Association (UE Policy Association) with the PCF (Policy Control Function). The relevant process of PCF policy update can be found in the target-related solution, which will not be repeated here. The same applies to the following examples.
[0251] After the new network node is selected, whether other network elements are still located in the Old network node or migrated to the New network node according to demand is not limited in this solution.
[0252] Example 1.2: RAN performs new network node selection (the network node selection and AMF selection in Example 1.1 may also be performed by RAN, but is not limited thereto);
[0253] Specifically, the distributed network registration update process 2 can be as follows: Figure 8 As shown, the following steps are included:
[0254] 1. When the UE's demand for the network changes due to changes in the access service type, device type, etc., the registration update process (i.e., the registration process with the registration type of mobility registration update) is triggered, carrying the registered UE identifier (e.g., 5G-GUTI) and new demand parameters, etc.; (corresponding to the above-mentioned sending of the first request to the access network node).
[0255] The message for sending the registration request may be an AN (access network) message (carrying AN parameters and a registration request);
[0256] Specifically, the registration request may carry at least one of the following parameters: registration type, SUCI (user hidden identifier) or 5G-GUTI (globally unique temporary UE identifier) or permanent equipment identifier PEI, tracking area identifier TAI last visited by the terminal (if available), security parameters, NSSAI (network slice selection assistance information) requested by the terminal, mapping of NSSAI requested by the terminal, PDU session state, active time requested by the terminal, LADN (local data network) DNN (data network name) or indicator for requesting LADN information, NAS (non-access layer) message container, preferred network behavior, UE paging probability information, UE policy container and UE radio capability ID, release request indication, and PEI.
[0257] AN parameters include: 5G-S-TMSI or GUAMI, selected PLMN ID, NSSAI information; it may also include Establishment cause, or registration reason, to provide the reason for requesting to establish an RRC connection between the UE and AN, and the reason for initiating a registration update: changes in distributed network requirements.
[0258] Among them, Registration type is mobile registration update, and Preferred Network Behaviour is the new requirement for the network.
[0259] 2. If the RAN determines based on the AN parameters that the current network node cannot meet the new requirements of the UE, the RAN can identify the old network node and the old AMF accessed by the UE based on the AN parameters, and perform network node selection (corresponding to the above-mentioned determination of the target network node according to the first request, and determining the second core network node under the target network node) based on the new network requirement parameters (corresponding to the above-mentioned updated network requirement parameters, for example, the UE's service objectives have changed significantly-the main service accessed is updated to a new service type, or the user is upgraded from a low priority and / or low-paying user), the connection relationship with the RAN (corresponding to the above-mentioned connection relationship with the access network node), the maintained node information, the UE information (corresponding to the device information of the above-mentioned terminal, including the UE device type, such as XR (Internet Data Center) device, Internet of Things IoT device, drone device, etc.), the local policy (corresponding to the above-mentioned local node determination policy), etc. The above information covers the user's direct and potential needs for the network. The UE device implicitly has requirements for the network's bandwidth, mobility, service range, etc. For example, the drone has a large range of movement and needs to select a network node with a larger service range to avoid frequent switching; the XR device requires the network to select a network node with greater computing power and bandwidth capacity and smaller latency, etc.
[0260] 3. RAN performs AMF selection in the selected network node (corresponding to determining the target network node according to the first request; determining the second core network node according to the target network node), which may be the default configuration AMF, or may be retrieved through NRF. Optional AMF (corresponding to the information of the above-mentioned candidate core network node) and based on AMF load (corresponding to the load of the above-mentioned core network node), UE information (corresponding to the device information of the above-mentioned terminal), RAN information (corresponding to the information of the above-mentioned access network node), etc. Complete AMF selection (corresponding to the above-mentioned determination of the second core network node under the target network node according to the default configuration or the first information).
[0261] Among them: steps 2 and 3 can also be considered jointly to complete the selection of network nodes and AMF at the same time (which can be understood as: considering the information of network nodes and AMF together for simultaneous selection) to avoid selecting nodes first and then AMF, which may not be the optimal selection result.
[0262] 4. The RAN sends a registration request to the selected New AMF (corresponding to sending a second request to the second core network node according to the first request), carrying the Old AMF information.
[0263] 5. If the New AMF determines that the registration request can be accepted according to the local information, it replies with a registration acceptance (corresponding to sending a request acceptance response to the second request to the first core network node) and requests to obtain the UE context (corresponding to sending a terminal context request to the first core network node according to the second request);
[0264] 6. The Old AMF replies the UE context to the New AMF (corresponding to the above-mentioned sending of the terminal context response to the second core network node), including the AN access information; after replying the message, the locally maintained UE context may be deleted after receiving the response or after a timer time;
[0265] Among them: the above steps 4-6 can also be combined into one, and the Old AMF sends the UE context to the New AMF while sending the registration request, but it is not limited to this.
[0266] 7. The New AMF maintains the UE context and assigns a new identifier (for example, 5G-GUTI) to the UE, and replies to the UE with a registration acceptance response (the message may also be forwarded by the Old AMF); corresponding to the above response according to the terminal context, a first response is sent to the terminal.
[0267] The message in step 7 may also include a response from the New AMF to the Old AMF to inform the Old AMF that the locally maintained UE context may be deleted; and may also include AMF switching information sent by the New AMF to the RAN to notify the RAN to update the information of the Old AMF in the locally maintained UE context.
[0268] After the new network node is selected, whether other network elements are still located in the Old network node or migrated to the New network node according to demand is not limited in this solution.
[0269] In addition, in step 7, the New AMF may notify the Old AMF to release the locally maintained UE context, but is not limited thereto.
[0270] Among them, in the above Examples 1.1 and 1.2, when the performance of the base station (i.e., RAN) is limited or less distributed node information of the core network is expected to be maintained for the base station, it is recommended to use the method of the old network node performing network node selection in Example 1.1; when different distributed network nodes cannot interact directly due to operations, authority, etc., it is recommended to use the method of RAN performing network node selection in Example 1.2, but it is not limited to this.
[0271] Example 2: The network instructs the UE to register and update to a new network node due to a state change;
[0272] The UE initiating the registration update process in Example 1 may also be due to changes in network load, etc. that may not meet the UE's needs, or when the operator's policy expects the UE to register and update to a new network node, the network instructs the UE to initiate the registration update process to register and update to the new network node. Before the UE initiates the registration update request in Example 1, the network first initiates a registration update request or instruction to the UE.
[0273] Specifically, the scheme for the network to indicate registration update to the UE may be as follows: Fig. 9 As shown, the following steps are included:
[0274] 1. UDM sends a registration update notification Nudm_UECM_REgistrationUpdateNotification to AMF (corresponding to the above-mentioned first core network node);
[0275] Among them, it may be that the UDM updates the registration management context due to the operator policy, triggering the UE registration update (sending a notification to the AMF); it may also be that the AMF monitors the network status change, etc., triggering the UE registration update (executing step 2 below).
[0276] It is noted here that the network function that sends the registration update notification to AMF is not limited to UDM, but can also be AF, PCF, etc., that is, the registration update demand is triggered by changes in application requirements or network policies.
[0277] 2. AMF sends a registration update request RegistrationUpdate Request (or indication) to the UE; corresponding to the above-mentioned sending of a registration message to the terminal;
[0278] Among them, the registration update request or indication sent to the UE carries Cause, which indicates the reason for the registration update (corresponding to the registration update reason carried in the above-mentioned registration message), such as network load changes, operator policy reasons, etc., and may also optionally carry indication information such as the target RAN, target network node, or target AMF where the UE is expected to initiate the registration update, which is not limited here.
[0279] It is explained here that the above-mentioned registration update request (or indication) is just a message containing the meaning of the registration update request or indication, which can be a newly defined message or can carry the registration update meaning in an existing message, and is not limited here.
[0280] 3. AMF sends a registration update notification response Nudm_UECM_REgistrationUpdateNotificationAck to UDM.
[0281] Example 3: The network notifies the UE after updating the UE registration to a new network node due to a state change;
[0282] Specifically, the distributed network registration update process 3 can be as follows: Fig.10 As shown, the following steps are included:
[0283] 1. Due to changes in network load, the UE requirements may not be met, or the operator's policy expects the UE to register and update to a new network node, triggering the update of the network node serving the UE;
[0284] 2. Old AMF (corresponding to the above-mentioned first core network node) requests NAR (Node Auto Register) to obtain a list of network nodes that can meet the UE's needs (i.e., sending a node discovery request to NAR, corresponding to the above-mentioned acquisition of the first parameter according to the first request). The request information includes the UE's locally stored parameters and newly carried parameters for network requirements; NAR can be a new network function at a network node granularity, which is used to maintain node granularity information and implement node plug-and-play and other functions.
[0285] 3. NAR responds with a list of candidate network nodes and node information of the candidate nodes (corresponding to the above candidate network node information), that is, NAR feedback node discovery response;
[0286] 4. Old AMF performs network node selection (corresponding to determining the target network node according to the first parameter above) based on the responded network node list, the responded node information, the UE information (corresponding to the device information of the above terminal), the local policy (which may also be a policy obtained through the PCF, etc.; corresponding to the above local node determination policy or the obtained node determination policy), etc.;
[0287] 5. The Old AMF performs AMF selection in the selected network node, which may be the default configuration AMF, or may be retrieved through the NRF as the optional AMF (corresponding to the information of the candidate core network node) and based on the AMF load (corresponding to the load of the core network node), UE information (corresponding to the device information of the terminal), RAN information (corresponding to the information of the access network node), etc. to complete the AMF selection (corresponding to the above-mentioned determination of the second core network node under the target network node according to the default configuration or the first information);
[0288] 6. The Old AMF forwards the registration request to the New AMF (corresponding to the second core network node) (the message may also be forwarded through the RAN); corresponding to the sending of the second request to the second core network node;
[0289] 7. If the New AMF determines that the registration request can be accepted according to the local information, it replies with a registration acceptance (corresponding to sending a request acceptance response to the second request to the first core network node) and requests to obtain the UE context (corresponding to sending a terminal context request to the first core network node according to the second request);
[0290] 8. The Old AMF replies the UE context to the New AMF (corresponding to the above-mentioned sending of the terminal context response to the second core network node), including the AN access information; after replying the message, the locally maintained UE context may be deleted after receiving the response or after a timer time;
[0291] Among them: the above steps 6-8 can also be combined into one, and the Old AMF sends the UE context to the New AMF while sending the registration request, but it is not limited to this.
[0292] 9. The New AMF sends a registration update notification message to the UE (corresponding to the first notification sent to the terminal above), carrying the reason for the network registration update (such as network load reason, operator policy reason, etc.) and the new UE identifier allocated by the New AMF.
[0293] In this step, the New AMF may include interacting with the RAN to update the UE context information but is not limited thereto.
[0294] Here is an explanation: (1) In the above example, when the RAN or old network node performs network node selection, it can also obtain the list of alternative New network nodes through the centralized node in the distributed network (compared to Example 1, it is obtained through NAR); further, the New AMF located at the New network node can be selected by the RAN or old network node, or by the centralized node. Corresponding to the above, according to the first request, a first determination request (or a second determination request) for determining the target network node and the second core network node is sent to the centralized node; and information about the target network node and the second core network node fed back by the centralized node is received.
[0295] (2) In the above example 1 and example 3, when the Old AMF determines that the current network node cannot meet the new requirements of the UE, the result can also be fed back to the RAN, and the RAN performs the selection of the new network node (in contrast, the original method is to directly select the Old network node or the RAN, and here the Old network node determines that it cannot provide service and feeds back the result to the RAN, and the RAN makes the network node selection); corresponding to the above, according to the first request, a first determination request for determining the target network node and the second core network node is sent to the access network node; and information of the target network node and the second core network node fed back by the centralized node or the access network node is received.
[0296] In addition: The schematic diagrams of the above examples only illustrate the key processes, and the authentication and contract functions such as AUSF (Authentication Service Function) and UDM (Uniform Data Management Function) involved are not described, but can be implemented by referring to the current relevant solutions. In addition, when there is an established PDU (Protocol Data Unit) session, it involves communication with SMF (Session Management Function), which can also be referred to the current relevant solutions, and will not be repeated in the above examples.
[0297] From the above, the embodiment of the present application provides a distributed network registration update method to implement a registration update process scheme initiated by a UE or initiated by a network, wherein:
[0298] 1. The registration update process initiated by the UE is a registration update process initiated actively when the UE's network demand tendency changes. The registration type may be mobility registration update, and the AN parameter may carry the registration reason. Among them, the registration message may carry the future tendency demand. Based on this, the access network or core network executes the network node and AMF selection and completes the registration update process.
[0299] 2. The registration update process initiated by the network is when changes such as network load may not be able to meet the UE's needs, or when the operator's policy expects the UE to register and update to a new network node, the network instructs the UE to initiate a registration update process to register and update to a new network node;
[0300] 3. The above registration update process is the core network or access network executing the selection of new network nodes and new AMF.
[0301] 3.1 The registration update process initiated by the UE may be that the core network performs network node selection based on the network node candidate list, network node information, UE information, local policy (or policy obtained through PCF, etc.), or the access network performs network node selection based on network requirement parameters, connection relationship with RAN, maintained node information, UE information, local policy, etc.;
[0302] 3.2 The above UE-initiated registration update process can be the default configuration AMF, or it can be retrieved through NRF and the optional AMF is selected based on AMF load, UE information, RAN information, etc.;
[0303] 3.3 The above network node selection and AMF selection can be performed by first performing the network node selection and then selecting the AMF in the network node; or the network node and AMF information can be integrated to jointly complete the selection of the network node and AMF.
[0304] In summary, this solution provides a distributed network registration update method to solve the registration update problem for 6G distributed architecture. Among them, for the mobility registration update of centralized 5GS, a new scenario of registration update between UE or network triggered network nodes in distributed network architecture is expanded, solving the problems of distributed network node selection and new AMF selection, information interaction, etc. in this scenario.
[0305] It is noted here that the above AMF is based on the 5G system as an example. For 6G, the first core network node here can be a new network function that performs the access management function, and / or the second core network node can be a new network function that performs the access management function, which is not limited here.
[0306] The embodiment of the present application also provides a network registration update device, wherein the network registration update device is a first core network node, such as Fig.11 As shown, it includes a memory 111, a transceiver 112, and a processor 113:
[0307] The memory 111 is used to store computer programs; the transceiver 112 is used to send and receive data under the control of the processor 113; the processor 113 is used to read the computer program in the memory 111 and perform the following operations:
[0308] Execute a first operation for updating terminal registration to a second core network node;
[0309] The first core network node and the second core network node belong to different network nodes;
[0310] The first operation includes at least one of the following:
[0311] Receiving, by the transceiver 112, a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node;
[0312] A registration message is sent to the terminal via the transceiver 112, wherein the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication.
[0313] The network registration update device provided in the embodiment of the present application performs a first operation for terminal registration update to a second core network node; wherein the first core network node is different from the network node to which the second core network node belongs; the first operation includes at least one of the following: (1) receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node; (2) sending a registration message to the terminal, wherein the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication; and can support interaction between new and old core network nodes (a first core network node and a second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, thereby effectively solving the problem that the prior art cannot support network registration updates between different network nodes.
[0314] Specifically, the transceiver 112 is used to receive and send data under the control of the processor 113 .
[0315] Among them, Fig.11 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 113 and memory represented by memory 111. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 112 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 113 is responsible for managing the bus architecture and general processing, and the memory 111 may store data used by the processor 113 when performing operations.
[0316] The processor 113 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0317] Furthermore, the operation also includes: before receiving the terminal context request sent by the second core network node, receiving a first request sent by the access network node through the transceiver; determining the target network node according to the first request, and determining the second core network node under the target network node; sending a second request to the second core network node through the transceiver; the operation also includes: receiving a request acceptance response fed back by the second core network node through the transceiver; wherein the first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
[0318] Among them, determining the target network node according to the first request includes: obtaining a first parameter according to the first request; determining the target network node according to the first parameter; wherein the first parameter includes at least one of the following: alternative network node information; device information of the terminal; local node determination strategy or acquired node determination strategy.
[0319] In an embodiment of the present application, determining the second core network node under the target network node includes: determining the second core network node under the target network node according to a default configuration or first information; wherein the first information includes at least one of the following: information of candidate core network nodes; load of the core network node; device information of the terminal; information of the access network node.
[0320] The determining of the target network node according to the first request and the determining of the second core network node under the target network node include: determining the target network node according to the first request; and determining the second core network node according to the target network node.
[0321] In an embodiment of the present application, determining the target network node according to the first request, and determining the second core network node under the target network node include: sending a first determination request for determining the target network node and the second core network node to a centralized node or an access network node through the transceiver according to the first request; and receiving information about the target network node and the second core network node fed back by the centralized node or the access network node through the transceiver.
[0322] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned first core network node side method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.
[0323] The embodiment of the present application also provides a network registration update device, wherein the network registration update device is a second core network node, such as Fig.12 As shown, it includes a memory 121, a transceiver 122, and a processor 123:
[0324] The memory 121 is used to store computer programs; the transceiver 122 is used to send and receive data under the control of the processor 123; the processor 123 is used to read the computer program in the memory 121 and perform the following operations:
[0325] According to the second request, sending a terminal context request to the first core network node through the transceiver 122;
[0326] Receiving, through the transceiver 122, a terminal context response fed back by the first core network node;
[0327] Sending a first response or a first notification to the terminal through the transceiver 122 according to the terminal context response;
[0328] The second request is used to request registration or request registration update;
[0329] The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.
[0330] The network registration update device provided in the embodiment of the present application sends a terminal context request to the first core network node according to a second request; receives a terminal context response fed back by the first core network node; sends a first response or a first notification to the terminal according to the terminal context response; wherein the second request is used to request registration or request registration update; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification; it can support the interaction between the old and new core network nodes (the first core network node and the second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support the implementation of network registration updates between different network nodes.
[0331] Specifically, the transceiver 122 is used to receive and send data under the control of the processor 123.
[0332] Among them, Fig.12 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 123 and various circuits of memory represented by memory 121 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 122 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which transmission medium may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 123 is responsible for managing the bus architecture and general processing, and the memory 121 may store data used by the processor 123 when performing operations.
[0333] The processor 123 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0334] Furthermore, the operation also includes: before sending the terminal context request to the first core network node through the transceiver according to the second request, receiving the second request sent by the first core network node or the access network node through the transceiver.
[0335] In the embodiment of the present application, the operation also includes: sending a request acceptance response to the second request to the first core network node through the transceiver.
[0336] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned second core network node side method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.
[0337] The embodiment of the present application also provides a network registration update device, the network registration update device is an access network node, such as Fig.13 As shown, it includes a memory 131, a transceiver 132, and a processor 133:
[0338] The memory 131 is used to store computer programs; the transceiver 132 is used to send and receive data under the control of the processor 133; the processor 133 is used to read the computer program in the memory 131 and perform the following operations:
[0339] Execute a second operation for the terminal to register and update from the first core network node to the second core network node;
[0340] The first core network node and the second core network node belong to different network nodes;
[0341] The second operation includes:
[0342] A first request sent by a terminal is received through the transceiver 132; based on the first request, a first request is sent to the first core network node or a second request is sent to the second core network node through the transceiver 132; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
[0343] The network registration update device provided in the embodiment of the present application performs a second operation for the terminal to register and update from a first core network node to a second core network node; wherein the first core network node and the second core network node belong to different network nodes; the second operation includes: receiving a first request sent by the terminal; according to the first request, sending a first request to the first core network node or sending a second request to the second core network node; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update; it can support the interaction between the old and new core network nodes (the first core network node and the second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support the implementation of network registration updates between different network nodes.
[0344] Specifically, the transceiver 132 is used to receive and send data under the control of the processor 133.
[0345] Among them, Fig.13In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 133 and memory represented by memory 131. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 132 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 133 is responsible for managing the bus architecture and general processing, and the memory 131 may store data used by the processor 133 when performing operations.
[0346] The processor 133 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0347] Furthermore, the operation also includes: before sending the second request to the second core network node, determining a target network node according to the first request, and determining a second core network node under the target network node.
[0348] Among them, determining the target network node according to the first request includes: obtaining a second parameter according to the first request; determining the target network node according to the second parameter; wherein the second parameter includes at least one of the following: an updated network requirement parameter; a connection relationship with the access network node; maintained node information; device information of the terminal; a local node determination strategy or an acquired node determination strategy.
[0349] In an embodiment of the present application, determining the second core network node under the target network node includes: determining the second core network node under the target network node according to a default configuration or first information; wherein the first information includes at least one of the following: information of candidate core network nodes; load of the core network node; device information of the terminal; information of the access network node.
[0350] The determining of the target network node according to the first request and the determining of the second core network node under the target network node include: determining the target network node according to the first request; and determining the second core network node according to the target network node.
[0351] In an embodiment of the present application, determining the target network node according to the first request, and determining the second core network node under the target network node include: sending a second determination request for determining the target network node and the second core network node to a centralized node through the transceiver according to the first request; and receiving information about the target network node and the second core network node fed back by the centralized node through the transceiver.
[0352] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned access network node side method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.
[0353] The embodiment of the present application also provides a network registration update device, wherein the network registration update device is a terminal, such as Fig.14 As shown, it includes a memory 141, a transceiver 142, and a processor 143:
[0354] The memory 141 is used to store computer programs; the transceiver 142 is used to send and receive data under the control of the processor 143; the processor 143 is used to read the computer program in the memory 141 and perform the following operations:
[0355] Performing a third operation of registering and updating the terminal from the first core network node to the second core network node;
[0356] The first core network node and the second core network node belong to different network nodes;
[0357] The third operation includes at least one of the following:
[0358] Receiving, by the transceiver 142, a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication;
[0359] A first response or a first notification sent by the second core network node is received through the transceiver 142; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification.
[0360] The network registration update device provided in the embodiment of the present application performs a third operation for the terminal to register and update from a first core network node to a second core network node; wherein the first core network node and the second core network node belong to different network nodes; the third operation includes at least one of the following: (1) receiving a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication; (2) receiving a first response or a first notification sent by the second core network node; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification; it can support the interaction between the old and new core network nodes (the first core network node and the second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support the implementation of network registration updates between different network nodes.
[0361] Specifically, the transceiver 142 is used to receive and send data under the control of the processor 143.
[0362] Among them, Fig.14 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 143 and various circuits of memory represented by memory 141 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 144 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, including wireless channels, wired channels, optical cables, and other transmission media. For different user devices, the user interface 144 may also be an interface capable of externally and internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
[0363] The processor 143 is responsible for managing the bus architecture and general processing, and the memory 141 can store data used by the processor 143 when performing operations.
[0364] Optionally, the processor 143 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.
[0365] The processor calls the computer program stored in the memory to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.
[0366] Furthermore, the operation also includes: before executing the third operation of registering and updating the terminal from the first core network node to the second core network node, sending a first request to the access network node through the transceiver; or, according to the registration message, sending a first request to the access network node through the transceiver; wherein the first request is used to request registration or request registration update.
[0367] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned terminal side method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.
[0368] The embodiment of the present application also provides a network registration update device, which is applied to a first core network node, such as Fig.15 As shown, including:
[0369] The first execution unit 151 is used to execute a first operation for updating the terminal registration to the second core network node;
[0370] The first core network node and the second core network node belong to different network nodes;
[0371] The first operation includes at least one of the following:
[0372] receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node;
[0373] A registration message is sent to the terminal, where the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication.
[0374] The network registration update device provided in the embodiment of the present application performs a first operation for terminal registration update to a second core network node; wherein the first core network node is different from the network node to which the second core network node belongs; the first operation includes at least one of the following: (1) receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node; (2) sending a registration message to the terminal, wherein the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication; and can support the interaction between the old and new core network nodes (the first core network node and the second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support the implementation of network registration update between different network nodes.
[0375] Furthermore, the network registration update device also includes: a first receiving unit, used to receive a first request sent by the access network node before receiving the terminal context request sent by the second core network node; a first determination unit, used to determine the target network node according to the first request, and determine the second core network node under the target network node; a first sending unit, used to send a second request to the second core network node; the device also includes: a second receiving unit, used to receive a request acceptance response fed back by the second core network node; wherein the first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
[0376] Among them, determining the target network node according to the first request includes: obtaining a first parameter according to the first request; determining the target network node according to the first parameter; wherein the first parameter includes at least one of the following: alternative network node information; device information of the terminal; local node determination strategy or acquired node determination strategy.
[0377] In an embodiment of the present application, determining the second core network node under the target network node includes: determining the second core network node under the target network node according to a default configuration or first information; wherein the first information includes at least one of the following: information of candidate core network nodes; load of the core network node; device information of the terminal; information of the access network node.
[0378] The determining of the target network node according to the first request and the determining of the second core network node under the target network node include: determining the target network node according to the first request; and determining the second core network node according to the target network node.
[0379] In an embodiment of the present application, determining the target network node according to the first request, and determining the second core network node under the target network node include: sending a first determination request for determining the target network node and the second core network node to a centralized node or an access network node according to the first request; and receiving information about the target network node and the second core network node fed back by the centralized node or the access network node.
[0380] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned first core network node side method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.
[0381] The embodiment of the present application also provides a network registration update device, which is applied to a second core network node, such as Fig.16 As shown, including:
[0382] The second sending unit 161 is used to send a terminal context request to the first core network node according to the second request;
[0383] The third receiving unit 162 is configured to receive a terminal context response fed back by the first core network node;
[0384] The third sending unit 163 is used to send a first response or a first notification to the terminal according to the terminal context response;
[0385] The second request is used to request registration or request registration update;
[0386] The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.
[0387] The network registration update device provided in the embodiment of the present application sends a terminal context request to the first core network node according to a second request; receives a terminal context response fed back by the first core network node; sends a first response or a first notification to the terminal according to the terminal context response; wherein the second request is used to request registration or request registration update; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification; it can support the interaction between the old and new core network nodes (the first core network node and the second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support the implementation of network registration updates between different network nodes.
[0388] Furthermore, the network registration update device also includes: a fourth receiving unit, used to receive the second request sent by the first core network node or the access network node before sending the terminal context request to the first core network node according to the second request.
[0389] In the embodiment of the present application, the network registration update device further includes: a fourth sending unit, configured to send a request acceptance response to the second request to the first core network node.
[0390] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned second core network node side method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.
[0391] The embodiment of the present application also provides a network registration update device, which is applied to an access network node, such as Fig.17 As shown, including:
[0392] The second execution unit 171 is used to execute a second operation for the terminal to register and update from the first core network node to the second core network node;
[0393] The first core network node and the second core network node belong to different network nodes;
[0394] The second operation includes:
[0395] Receive a first request sent by a terminal; based on the first request, send a first request to the first core network node or send a second request to the second core network node; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
[0396] The network registration update device provided in the embodiment of the present application performs a second operation for the terminal to register and update from a first core network node to a second core network node; wherein the first core network node and the second core network node belong to different network nodes; the second operation includes: receiving a first request sent by the terminal; according to the first request, sending a first request to the first core network node or sending a second request to the second core network node; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update; it can support the interaction between the old and new core network nodes (the first core network node and the second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support the implementation of network registration updates between different network nodes.
[0397] Furthermore, the network registration update device also includes: a second determination unit, used to determine the target network node according to the first request and determine the second core network node under the target network node before sending the second request to the second core network node.
[0398] Among them, determining the target network node according to the first request includes: obtaining a second parameter according to the first request; determining the target network node according to the second parameter; wherein the second parameter includes at least one of the following: an updated network requirement parameter; a connection relationship with the access network node; maintained node information; device information of the terminal; a local node determination strategy or an acquired node determination strategy.
[0399] In an embodiment of the present application, determining the second core network node under the target network node includes: determining the second core network node under the target network node according to a default configuration or first information; wherein the first information includes at least one of the following: information of candidate core network nodes; load of the core network node; device information of the terminal; information of the access network node.
[0400] The determining of the target network node according to the first request and the determining of the second core network node under the target network node include: determining the target network node according to the first request; and determining the second core network node according to the target network node.
[0401] In an embodiment of the present application, determining the target network node according to the first request and determining the second core network node under the target network node include: sending a second determination request for determining the target network node and the second core network node to a centralized node according to the first request; and receiving information about the target network node and the second core network node fed back by the centralized node.
[0402] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned access network node side method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.
[0403] The present application also provides a network registration update device, which is applied to a terminal, such as Fig.18 As shown, including:
[0404] The third execution unit 181 is used to execute a third operation for the terminal to register and update from the first core network node to the second core network node;
[0405] The first core network node and the second core network node belong to different network nodes;
[0406] The third operation includes at least one of the following:
[0407] Receiving a registration message sent by the first core network node, where the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request, or a registration update indication;
[0408] Receive a first response or a first notification sent by the second core network node; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification.
[0409] The network registration update device provided in the embodiment of the present application performs a third operation for the terminal to register and update from a first core network node to a second core network node; wherein the first core network node and the second core network node belong to different network nodes; the third operation includes at least one of the following: (1) receiving a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication; (2) receiving a first response or a first notification sent by the second core network node; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification; it can support the interaction between the new and old core network nodes (the first core network node and the second core network node) for different network nodes to ensure that the terminal can register and update from the first core network node to the second core network node, which well solves the problem that the prior art cannot support the implementation of network registration updates between different network nodes.
[0410] Furthermore, the network registration update device also includes: a fifth sending unit, used to send a first request to the access network node before performing a third operation of registering and updating the terminal from the first core network node to the second core network node; or, sending a first request to the access network node according to the registration message; wherein the first request is used to request registration or request registration update.
[0411] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned terminal side method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.
[0412] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0413] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.
[0414] An embodiment of the present application also provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable the processor to execute the above-mentioned method on the first core network node side, the second core network node side, the access network node side or the terminal side.
[0415] The non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.
[0416] Among them, the implementation embodiments of the methods on the first core network node side, the second core network node side, the access network node side or the terminal side are all applicable to the embodiments of the non-transitory readable storage medium, and can achieve the same technical effect.
[0417] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.
[0418] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0419] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0420] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0421] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.
Claims
1. A network registration update method, applied to a first core network node, characterized in that: include: Execute a first operation for updating terminal registration to a second core network node; The first core network node and the second core network node belong to different network nodes; The first operation includes at least one of the following: receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node; A registration message is sent to the terminal, where the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication.
2. The network registration update method according to claim 1, characterized in that: Before receiving the terminal context request sent by the second core network node, the method further includes: Receiving a first request sent by an access network node; Determine a target network node according to the first request, and determine a second core network node under the target network node; Sending a second request to the second core network node; The method further comprises: receiving a request acceptance response fed back by the second core network node; The first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
3. The network registration update method according to claim 2, characterized in that: The determining the target network node according to the first request includes: According to the first request, obtaining a first parameter; Determine a target network node according to the first parameter; The first parameter includes at least one of the following: Alternative network node information; Device information of the terminal; The local node determines the strategy or the acquired node determines the strategy.
4. The network registration update method according to claim 2, characterized in that: The determining a second core network node under the target network node includes: Determine, according to the default configuration or the first information, a second core network node under the target network node; The first information includes at least one of the following: Information of candidate core network nodes; The load of the core network nodes; Device information of the terminal; Information about access network nodes.
5. The network registration update method according to claim 2, characterized in that: The determining a target network node according to the first request, and determining a second core network node under the target network node, includes: Determining a target network node according to the first request; A second core network node is determined according to the target network node.
6. The network registration update method according to claim 2, characterized in that: The determining a target network node according to the first request, and determining a second core network node under the target network node, includes: Sending, according to the first request, a first determination request for determining a target network node and a second core network node to a centralized node or an access network node; Receive information about the target network node and the second core network node fed back by the centralized node or the access network node.
7. A network registration update method, applied to a second core network node, characterized in that: include: Sending a terminal context request to the first core network node according to the second request; Receiving a terminal context response fed back by the first core network node; Sending a first response or a first notification to the terminal according to the terminal context response; The second request is used to request registration or request registration update; The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.
8. The network registration update method according to claim 7, characterized in that: Before sending the terminal context request to the first core network node according to the second request, the method further includes: Receive the second request sent by the first core network node or the access network node.
9. The network registration update method according to claim 7, characterized in that: Also includes: Send a request acceptance response to the second request to the first core network node.
10. A network registration update method, applied to an access network node, characterized in that: include: Execute a second operation for the terminal to register and update from the first core network node to the second core network node; The first core network node and the second core network node belong to different network nodes; The second operation includes: Receive a first request sent by a terminal; based on the first request, send a first request to the first core network node or send a second request to the second core network node; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
11. The network registration update method according to claim 10, characterized in that: Before sending the second request to the second core network node, the method further includes: A target network node is determined according to the first request, and a second core network node under the target network node is determined.
12. The network registration update method according to claim 11, characterized in that: The determining the target network node according to the first request includes: According to the first request, obtaining a second parameter; Determining a target network node according to the second parameter; The second parameter includes at least one of the following: Updated network requirement parameters; A connection relationship with the access network node; Maintained node information; Device information of the terminal; The local node determines the strategy or the acquired node determines the strategy.
13. The network registration update method according to claim 11, characterized in that: The determining a second core network node under the target network node includes: Determine, according to the default configuration or the first information, a second core network node under the target network node; The first information includes at least one of the following: Information of candidate core network nodes; The load of the core network nodes; Device information of the terminal; Information about access network nodes.
14. The network registration update method according to claim 11, characterized in that: The determining a target network node according to the first request, and determining a second core network node under the target network node, includes: Determining a target network node according to the first request; A second core network node is determined according to the target network node.
15. The network registration update method according to claim 11, characterized in that: The determining a target network node according to the first request, and determining a second core network node under the target network node, includes: Sending, according to the first request, a second determination request for determining a target network node and a second core network node to a centralized node; Receive the information of the target network node and the second core network node fed back by the centralized node.
16. A network registration update method, applied to a terminal, characterized in that: include: Performing a third operation of registering and updating the terminal from the first core network node to the second core network node; The first core network node and the second core network node belong to different network nodes; The third operation includes at least one of the following: Receiving a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication; Receive a first response or a first notification sent by the second core network node; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification.
17. The network registration update method according to claim 16, characterized in that: Also includes: Before performing a third operation of registering and updating the terminal from the first core network node to the second core network node, sending a first request to the access network node; or, Sending a first request to an access network node according to the registration message; The first request is used to request registration or request registration update.
18. A network registration update device, the network registration update device being a first core network node, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Execute a first operation for updating terminal registration to a second core network node; The first core network node and the second core network node belong to different network nodes; The first operation includes at least one of the following: Receiving, by the transceiver, a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node; A registration message is sent to the terminal through the transceiver, where the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication.
19. A network registration update device, the network registration update device being a second core network node, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: According to the second request, sending a terminal context request to the first core network node through the transceiver; Receiving, by the transceiver, a terminal context response fed back by the first core network node; Sending a first response or a first notification to the terminal through the transceiver according to the terminal context response; The second request is used to request registration or request registration update; The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.
20. A network registration update device, the network registration update device being an access network node, characterized in that: Including memory, transceiver, processor: a memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Execute a second operation for the terminal to register and update from the first core network node to the second core network node; The first core network node and the second core network node belong to different network nodes; The second operation includes: A first request sent by a terminal is received through the transceiver; based on the first request, a first request is sent to the first core network node or a second request is sent to the second core network node through the transceiver; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
21. A network registration update device, the network registration update device being a terminal, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Performing a third operation of registering and updating the terminal from the first core network node to the second core network node; The first core network node and the second core network node belong to different network nodes; The third operation includes at least one of the following: Receiving, by the transceiver, a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message including: a registration request, a registration indication, a registration update request or a registration update indication; A first response or a first notification sent by a second core network node is received through the transceiver; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification.
22. A network registration update device, applied to a first core network node, characterized in that: include: A first execution unit, configured to execute a first operation for updating terminal registration to a second core network node; The first core network node and the second core network node belong to different network nodes; The first operation includes at least one of the following: receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node; A registration message is sent to the terminal, where the registration message carries a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication.
23. A network registration update device, applied to a second core network node, characterized in that: include: A second sending unit, configured to send a terminal context request to the first core network node according to the second request; A third receiving unit, configured to receive a terminal context response fed back by the first core network node; A third sending unit, configured to send a first response or a first notification to the terminal according to the terminal context response; The second request is used to request registration or request registration update; The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.
24. A network registration update device, applied to an access network node, characterized in that: include: A second execution unit, configured to execute a second operation for the terminal to register and update from the first core network node to the second core network node; The first core network node and the second core network node belong to different network nodes; The second operation includes: Receive a first request sent by a terminal; based on the first request, send a first request to the first core network node or send a second request to the second core network node; the first request is used to request registration or request registration update; the second request is used to request registration or request registration update.
25. A network registration update device, applied to a terminal, characterized in that: include: A third execution unit, configured to execute a third operation for the terminal to register and update from the first core network node to the second core network node; The first core network node and the second core network node belong to different network nodes; The third operation includes at least one of the following: Receiving a registration message sent by the first core network node, the registration message carrying a registration update reason; the registration message includes: a registration request, a registration indication, a registration update request or a registration update indication; Receive a first response or a first notification sent by the second core network node; the first response is a registration reception response or a registration update acceptance response, and the first notification is a registration update notification.
26. A non-transitory readable storage medium, characterized in that The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method according to any one of claims 1 to 17.
