Network registration updating method and apparatus, and device

By using the registration and update method between core network nodes under the 6G distributed architecture, the problem that 5G system cannot support registration and update between different network nodes is solved, and the terminal is successfully updated when network requirements change. It is suitable for 6G system. Distributed architecture.

WO2024234854A1PCT designated stage expired Publication Date: 2024-11-21DATANG MOBILE COMM EQUIP CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/085442
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-04-02
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Existing 5G systems cannot support network registration and updates between different network nodes, especially in the 6G distributed architecture, when user equipment changes its network requirements or network load changes, it cannot achieve effective registration and updates.

Method used

Provide a network registration and update method, perform registration and update operations to the second core network node through the first core network node, including receiving terminal context requests, sending registration messages, determining target network nodes and core network nodes, ensuring that the terminal can get from the old core Network node registration and update to the new core network node.

Benefits of technology

The interaction between new and old core network nodes between different network nodes is realized, and the problem of registration and update under the 6G distributed architecture is solved, ensuring that the terminal can smoothly update from old nodes to new nodes, meeting changes in network needs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024085442_21112024_PF_FP_ABST
    Figure CN2024085442_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to the technical field of communications. Provided are a network registration updating method and apparatus, and device. The network registration updating method comprises: executing a first operation for updating terminal registration to a second core network node, wherein a network node to which a first core network node belongs is different from a network node to which the second core network node belongs, and the first operation comprises 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; and sending a registration message to a terminal, wherein the registration message carries a registration updating reason, and the registration message comprises: a registration request, a registration instruction, a registration updating request or a registration updating instruction.
Need to check novelty before this filing date? Find Prior Art

Description

Network registration update method, device and equipment

[0001] This disclosure claims priority to a Chinese patent application filed with the Patent Office of China on May 12, 2023, with application number 202310534531.8 and application name “A Network Registration Update Method, Apparatus and Device,” the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0002] The present disclosure relates to the field of communication technologies, and in particular to a network registration update method, apparatus, and device. Background Art

[0003] The current fifth-generation mobile communication technology (5G) system is originally designed for centralized control. With the development of the network, the trend of the sixth-generation mobile communication technology (6G) system 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.

[0004] For the 6G distributed architecture, when the network demand of the user equipment (UE) 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 5G system (5G System, 5GS) domain registration update method is not applicable.

[0005] Specifically, the centralized 5GS mobility registration update mainly targets changes in the access and mobility management function (AMF) caused by changes in the tracking area (TA) due to UE mobility, or changes in the AMF when the original AMF cannot meet its needs due to UE updated capabilities or protocol parameters, triggering interactions between the old and new AMFs within a network node. However, the existing solutions are not applicable to the interactions between the old and new AMFs in different network nodes involved in the 6G distributed architecture.

[0006] As described above, the related technologies have problems such as being unable to support network registration updates between different network nodes.

[0007] Summary of the Invention

[0008] The purpose of the present disclosure is to provide a network registration update method, apparatus and device to solve the problem in related technologies that network registration update between different network nodes cannot be supported.

[0009] In order to solve the above technical problems, an embodiment of the present disclosure provides a network registration update method, which is applied to a first core network node, including:

[0010] Performing a first operation for terminal registration update to the second core network node;

[0011] The first core network node and the second core network node belong to different network nodes;

[0012] The first operation includes at least one of the following:

[0013] receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node;

[0014] 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.

[0015] In some embodiments, before receiving the terminal context request sent by the second core network node, the method further includes:

[0016] receiving a first request sent by an access network node;

[0017] Determining a target network node according to the first request, and determining a second core network node under the target network node;

[0018] Sending a second request to the second core network node;

[0019] The method further comprises:

[0020] receiving a request acceptance response fed back by the second core network node;

[0021] The first request is used to request registration or request registration update; the second request is used to request registration or request registration update.

[0022] In some embodiments, determining the target network node according to the first request includes:

[0023] Obtaining a first parameter according to the first request;

[0024] Determining a target network node according to the first parameter;

[0025] The first parameter includes at least one of the following:

[0026] Alternative network node information;

[0027] Device information of the terminal;

[0028] The local node determination policy or the acquired node determination policy.

[0029] In some embodiments, determining the second core network node under the target network node includes:

[0030] Determining a second core network node under the target network node according to a default configuration or the first information;

[0031] The first information includes at least one of the following:

[0032] Information of candidate core network nodes;

[0033] The load of core network nodes;

[0034] Device information of the terminal;

[0035] Information about access network nodes.

[0036] In some embodiments, determining a target network node according to the first request, and determining a second core network node under the target network node, includes:

[0037] determining a target network node according to the first request;

[0038] A second core network node is determined according to the target network node.

[0039] In some embodiments, determining a target network node according to the first request, and determining a second core network node under the target network node, includes:

[0040] 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;

[0041] Receive information about the target network node and the second core network node fed back by the centralization node or the access network node.

[0042] The present disclosure also provides a network registration update method, which is applied to a second core network node and includes:

[0043] Sending a terminal context request to the first core network node according to the second request;

[0044] receiving a terminal context response fed back by the first core network node;

[0045] Sending a first response or a first notification to the terminal according to the terminal context response;

[0046] The second request is used to request registration or request registration update;

[0047] The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.

[0048] In some embodiments, before sending the terminal context request to the first core network node according to the second request, the method further includes:

[0049] Receive the second request sent by the first core network node or the access network node.

[0050] In some embodiments, further comprising:

[0051] Send a request acceptance response to the second request to the first core network node.

[0052] The present disclosure also provides a network registration update method, which is applied to an access network node and includes:

[0053] Performing a second operation for the terminal to update registration from the first core network node to the second core network node;

[0054] The first core network node and the second core network node belong to different network nodes;

[0055] The second operation includes:

[0056] 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.

[0057] In some embodiments, before sending the second request to the second core network node, the method further includes:

[0058] A target network node is determined according to the first request, and a second core network node under the target network node is determined.

[0059] In some embodiments, determining the target network node according to the first request includes:

[0060] According to the first request, obtaining a second parameter;

[0061] determining a target network node according to the second parameter;

[0062] The second parameter includes at least one of the following:

[0063] Updated network requirement parameters;

[0064] a connection relationship with the access network node;

[0065] Maintained node information;

[0066] Device information of the terminal;

[0067] The local node determination policy or the acquired node determination policy.

[0068] In some embodiments, determining the second core network node under the target network node includes:

[0069] Determining a second core network node under the target network node according to a default configuration or the first information;

[0070] The first information includes at least one of the following:

[0071] Information of candidate core network nodes;

[0072] The load of core network nodes;

[0073] Device information of the terminal;

[0074] Information about access network nodes.

[0075] In some embodiments, determining a target network node according to the first request, and determining a second core network node under the target network node, includes:

[0076] determining a target network node according to the first request;

[0077] A second core network node is determined according to the target network node.

[0078] In some embodiments, determining a target network node according to the first request, and determining a second core network node under the target network node, includes:

[0079] 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;

[0080] Receive the information of the target network node and the second core network node fed back by the central node.

[0081] The present disclosure also provides a network registration update method, which is applied to a terminal and includes:

[0082] Performing a third operation of registering and updating the terminal from the first core network node to the second core network node;

[0083] The first core network node and the second core network node belong to different network nodes;

[0084] The third operation includes at least one of the following:

[0085] Receive 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;

[0086] Receive a first response or a first notification sent by the second core network node; the first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.

[0087] In some embodiments, the method further comprises:

[0088] 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,

[0089] Sending a first request to an access network node according to the registration message;

[0090] The first request is used to request registration or request registration update.

[0091] The embodiment of the present disclosure further provides a network registration update device, which is a first core network node and includes a memory, a transceiver, and a processor:

[0092] 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:

[0093] Performing a first operation for terminal registration update to the second core network node;

[0094] The first core network node and the second core network node belong to different network nodes;

[0095] The first operation includes at least one of the following:

[0096] 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;

[0097] A registration message is sent to the terminal via 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.

[0098] The embodiment of the present disclosure further provides a network registration update device, which is a second core network node and includes a memory, a transceiver, and a processor:

[0099] 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:

[0100] Sending a terminal context request to the first core network node through the transceiver according to the second request;

[0101] receiving, through the transceiver, a terminal context response fed back by the first core network node;

[0102] Sending a first response or a first notification to the terminal through the transceiver according to the terminal context response;

[0103] The second request is used to request registration or request registration update;

[0104] The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.

[0105] The embodiment of the present disclosure further provides a network registration update device, which is an access network node and includes a memory, a transceiver, and a processor:

[0106] 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:

[0107] Performing a second operation for the terminal to update registration from the first core network node to the second core network node;

[0108] The first core network node and the second core network node belong to different network nodes;

[0109] The second operation includes:

[0110] 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.

[0111] The embodiment of the present disclosure further provides a network registration and updating device, which is a terminal and includes a memory, a transceiver, and a processor:

[0112] 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:

[0113] Performing a third operation of registering and updating the terminal from the first core network node to the second core network node;

[0114] The first core network node and the second core network node belong to different network nodes;

[0115] The third operation includes at least one of the following:

[0116] 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;

[0117] A first response or a first notification sent by the 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.

[0118] The embodiment of the present disclosure further provides a network registration update device, applied to a first core network node, including:

[0119] A first execution unit, configured to execute a first operation for registering and updating the terminal to the second core network node;

[0120] The first core network node and the second core network node belong to different network nodes;

[0121] The first operation includes at least one of the following:

[0122] receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node;

[0123] 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.

[0124] The embodiment of the present disclosure further provides a network registration update device, applied to a second core network node, including:

[0125] A second sending unit, configured to send a terminal context request to the first core network node according to the second request;

[0126] A third receiving unit, configured to receive a terminal context response fed back by the first core network node;

[0127] A third sending unit, configured to send a first response or a first notification to the terminal according to the terminal context response;

[0128] The second request is used to request registration or request registration update;

[0129] The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.

[0130] The embodiment of the present disclosure further provides a network registration update device, which is applied to an access network node, including:

[0131] A second execution unit, configured to execute a second operation for the terminal to update registration from the first core network node to the second core network node;

[0132] The first core network node and the second core network node belong to different network nodes;

[0133] The second operation includes:

[0134] 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.

[0135] The present disclosure also provides a network registration update device, which is applied to a terminal and includes:

[0136] 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;

[0137] The first core network node and the second core network node belong to different network nodes;

[0138] The third operation includes at least one of the following:

[0139] Receive 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;

[0140] Receive a first response or a first notification sent by the second core network node; the first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.

[0141] An embodiment of the present disclosure also provides a readable storage medium, which stores a computer program, and the computer program is used to enable a 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.

[0142] The beneficial effects of the above technical solution disclosed in the present invention are as follows:

[0143] 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 and the network node to which the second core network node belongs are different; 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; 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 related technology cannot support the network registration update between different network nodes. BRIEF DESCRIPTION OF THE DRAWINGS

[0144] FIG1 is a schematic diagram of a wireless communication system architecture according to an embodiment of the present disclosure;

[0145] FIG2 is a schematic diagram of a 6G distributed network architecture according to an embodiment of the present disclosure;

[0146] FIG3 is a flowchart of a network registration update method according to an embodiment of the present disclosure;

[0147] FIG4 is a second flow chart of a network registration update method according to an embodiment of the present disclosure;

[0148] FIG5 is a third flowchart of a network registration update method according to an embodiment of the present disclosure;

[0149] FIG6 is a fourth flowchart of a network registration update method according to an embodiment of the present disclosure;

[0150] FIG7 is a schematic diagram of a specific implementation flow of the network registration update method according to an embodiment of the present disclosure;

[0151] FIG8 is a second schematic diagram of a specific implementation flow of the network registration update method according to an embodiment of the present disclosure;

[0152] FIG9 is a third schematic diagram of a specific implementation flow of the network registration update method according to an embodiment of the present disclosure;

[0153] FIG10 is a fourth flowchart of a specific implementation method of the network registration update method according to an embodiment of the present disclosure;

[0154] FIG11 is a schematic diagram of the structure of a network registration and updating device according to an embodiment of the present disclosure;

[0155] FIG12 is a second structural diagram of a network registration and updating device according to an embodiment of the present disclosure;

[0156] FIG13 is a third structural diagram of a network registration and updating device according to an embodiment of the present disclosure;

[0157] FIG14 is a fourth structural diagram of a network registration and updating device according to an embodiment of the present disclosure;

[0158] FIG15 is a first structural diagram of a network registration and updating device according to an embodiment of the present disclosure;

[0159] FIG16 is a second structural diagram of a network registration and updating device according to an embodiment of the present disclosure;

[0160] FIG17 is a third structural diagram of a network registration and updating device according to an embodiment of the present disclosure;

[0161] FIG18 is a fourth structural diagram of the network registration and updating device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0162] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure and not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0163] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0164] In the embodiments of the present disclosure, the term "plurality" refers to two or more than two, and other quantifiers are similar thereto.

[0165] It is explained here that the technical solutions provided by the embodiments of the present disclosure can be applicable to a variety of systems, especially 5G systems. For example, applicable systems can be global system of mobile communication (GSM) systems, code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, long term evolution advanced (LTE-A) systems, universal mobile telecommunication systems (UMTS), worldwide interoperability for microwave access (WiMAX) systems, 5G new air interface (NR) systems, etc. These various systems include terminal devices and network devices. The system can also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0166] Figure 1 shows a block diagram of a wireless communication system to which embodiments of the present disclosure may be applied. The wireless communication system includes a terminal device (also referred to as a terminal) and a network device.

[0167] The terminal device involved in the embodiments of the present disclosure may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing device 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 User Equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges voice and / or data with a radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), 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, or a user device, but is not limited in the embodiments of the present disclosure.

[0168] The network device involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or may be called another name. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, acting 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 disclosure may be a base transceiver station (BTS) in the Global System for Mobile communications (GSM) or code division multiple access (CDMA), a network device (NodeB) in wide-band code division multiple access (WCDMA), an evolutionary Node B (eNB or e-NodeB) in the long term evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), a home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of the present disclosure. 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 geographically separated.

[0169] 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 configuration and number of antenna combinations, MIMO transmission can be two-dimensional MIMO (2D-MIMO), three-dimensional MIMO (3D-MIMO), full-dimensional MIMO (FD-MIMO), or massive MIMO. It can also use diversity transmission, precoding, or beamforming.

[0170] The following first introduces the contents involved in the solution provided by the embodiment of the present disclosure.

[0171] 1. 6G distributed architecture trends;

[0172] A key trend in the development of 6G networks is the shift towards centralized and distributed network architectures. 5G and previous generations of network architecture were originally designed for centralized control. However, as networks evolve, driven by both business and technological advancements, 6G network design must consider a distributed architecture, with control gradually evolving towards distributed control.

[0173] Specifically, 6G networks will address diverse scenarios and network performance requirements across air, space, land, and sea. A centralized network architecture cannot uniformly meet all requirements. To address this challenge, as shown in Figure 2, 6G network architecture must evolve beyond centralized control and gradually towards a distributed architecture. This will extend more network functions to the network edge and build distributed, homogeneous network nodes with varying functional levels, each with complete control and data forwarding capabilities. Multiple network nodes across domains can form autonomous micro-networks based on business needs, providing targeted network services tailored to specific business scenarios, user scale, geographic environment, and other requirements.

[0174] 2. Regarding the update of mobile registration within the 5GS (5G system) domain;

[0175] 5G is a centrally controlled system architecture, and the 5G registration update method is intra-domain registration update.

[0176] Currently, UE (terminal) registration includes initial registration, mobility registration update, periodic registration update, emergency registration, disaster roaming registration and other registrations.

[0177] Among them, the mobility registration update occurs when the UE is in the Registration Management (RM

[0178] ) - One of the following situations when in the REGISTERED state:

[0179] 1) When the UE moves to a new TA outside the UE registration area (connected or idle state);

[0180] 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 behavior may cause incompatibility with the supported network behavior provided by the serving AMF;

[0181] 3) When the UE intends to obtain local area data network (LADN) information;

[0182] 4) When the NR satellite access changes to a suitable cell, it indicates that the registered public land mobile network (RPLMN) has multiple TAs, and these TAs are outside the UE's registration area in both the connection management-connected (CM-CONNECTED) and connection management-idle (CM-IDLE) states;

[0183] 5) When the UE in Multi-Universal Subscriber Identity Module (MUSIM) mode requires a new 5G Globally Unique Temporary Identifier (5G-GUTI) to be allocated.

[0184] Specifically, the 5GS mobility registration update process mainly targets changes in the serving AMF caused by changes in the TA due to UE mobility, or changes in the serving AMF caused by changes in UE capabilities or protocol parameters, which make the original AMF unable to meet the UE's needs. In short, the 5GS mobility registration update process triggers interactions between AMFs within a network node.

[0185] Based on the foregoing, embodiments of the present disclosure provide a network registration update method, apparatus, and device to address the problem in related technologies of being unable to support network registration updates between different network nodes. The method, apparatus, and device are based on the same patent application concept. Since the principles for solving the problems solved by the method, apparatus, and device are similar, their implementation can refer to each other, and any repetitions will not be repeated.

[0186] The network registration update method provided in the embodiment of the present disclosure is applied to a first core network node, as shown in FIG3 , and includes:

[0187] 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.

[0188] 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 this.

[0189] The network registration update method provided by the embodiment of the present disclosure 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; 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 related technology cannot support the network registration update between different network nodes.

[0190] 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 the access network node; determining the target network node based on 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; 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).

[0191] This can support the first core network node selecting 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 (a newly added registration type), or a newly defined registration update request (a new message, distinct from a registration request), but is not limited thereto.

[0192] 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.

[0193] This allows the target network node to be accurately determined. Acquiring the first parameter may include, but is not limited to, obtaining the first parameter from a Node Auto Register (NAR) or a centralized node. The terminal device information may include, but is not limited to, device location, device resources, and device type.

[0194] In an embodiment of the present disclosure, the determining of the second core network node under the target network node includes: determining the second core network node under the target network node based on a default configuration or first information; wherein the first information includes at least one of the following: information of the candidate core network node; load of the core network node; device information of the terminal; information of the access network node.

[0195] In this way, the second core network node can be accurately determined.

[0196] 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.

[0197] In this way, the target network node and the second core network node can be selected separately; in this solution, 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.

[0198] In an embodiment of the present disclosure, 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.

[0199] In this way, the target network node and the second core network node can be accurately determined as much as possible.

[0200] The present disclosure also provides a network registration update method, which is applied to a second core network node, as shown in FIG4 , and includes:

[0201] Step 41: Sending a terminal context request to the first core network node according to the second request;

[0202] Step 42: Receive a terminal context response fed back by the first core network node;

[0203] 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 receive response or a registration update accept response, and the first notification is a registration update notification.

[0204] 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 this.

[0205] The network registration update method provided by the embodiment of the present disclosure 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; and 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 effectively solves the problem that related technologies cannot support network registration updates between different network nodes.

[0206] Furthermore, before sending the terminal context request to the first core network node according to the second request, the method further includes: receiving the second request sent by the first core network node or the access network node.

[0207] This will get the second request exactly.

[0208] In the embodiment of the present disclosure, the network registration update method further includes: sending a request acceptance response to the second request to the first core network node.

[0209] This ensures that a response to the second request is achieved.

[0210] The present disclosure also provides a network registration update method, which is applied to an access network node, as shown in FIG5 , and includes:

[0211] 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 network node to which the second core network node belongs are different; 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).

[0212] 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 this.

[0213] The network registration update method provided by the embodiment of the present disclosure 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 network node to which the second core network node belongs are different; 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 related technology cannot support the network registration update between different network nodes.

[0214] Furthermore, before sending the second request to the second core network node, the method further includes: determining a target network node according to the first request, and determining a second core network node under the target network node.

[0215] This can support the access network node 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, or a registration request with a registration type of network demand change (this registration type is newly added), or a newly defined registration update request (a new message, different from a registration request), but is not limited to this. In addition, the present solution can 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. This can ensure that the first core network node accurately determines the target network node and the second core network node as much as possible.

[0216] 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: updated network requirement parameters; connection relationship with the access network node; maintained node information; device information of the terminal; local node determination strategy or acquired node determination strategy.

[0217] 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.

[0218] In an embodiment of the present disclosure, the determining of the second core network node under the target network node includes: determining the second core network node under the target network node based on a default configuration or first information; wherein the first information includes at least one of the following: information of the candidate core network node; load of the core network node; device information of the terminal; information of the access network node.

[0219] In this way, the second core network node can be accurately determined.

[0220] 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.

[0221] In this way, the target network node and the second core network node can be selected separately; in this solution, 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.

[0222] In an embodiment of the present disclosure, 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.

[0223] In this way, the target network node and the second core network node can be accurately determined as much as possible.

[0224] The present disclosure also provides a network registration update method, which is applied to a terminal, as shown in FIG6 , and includes:

[0225] 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 receive response or a registration update accept response, and the first notification is a registration update notification.

[0226] 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 this.

[0227] The network registration update method provided by the embodiment of the present disclosure 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 network node to which the second core network node belongs are different; 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 related technology cannot support the network registration update between different network nodes.

[0228] Among them, the network registration update method also includes: 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, 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.

[0229] This allows the terminal to proactively initiate registration updates.

[0230] It is noted here that the relevant contents of the above methods can be referenced to each other, and the repeated parts will not be repeated.

[0231] The following is an example of the network registration update method provided in the embodiment of the present disclosure, taking AMF as an example of the core network node.

[0232] In response to the above technical problems, the embodiments of the present disclosure provide a network registration update method, which can be specifically implemented as a distributed network registration update method. The method is aimed at: when the current serving network node cannot meet the UE's needs due to changes in the UE's network needs or changes in network load, the centralized 5GS mobility registration update only supports mobility registration updates within one network node, which 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 UEs or networks triggering network nodes in the distributed network architecture, and solves the problems of distributed network node selection, new AMF selection, information interaction, etc. in this scenario. This solution mainly involves: UE initiating registration update due to changes in needs, or the network instructing the UE to register and update to a new network node due to status changes, or the network notifying the UE after updating the UE's registration to a new network node due to status changes.

[0233] The following is a specific example to illustrate this solution.

[0234] Example 1: UE initiates registration update due to demand changes;

[0235] Example 1.1: The old network node selects the new network node;

[0236] Specifically, the distributed network registration update process 1 may be shown in FIG7 , and includes the following steps:

[0237] 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 type is a registration process for mobility registration update) is triggered, carrying the registered UE identifier (e.g., 5G-GUTI (Globally Unique Temporary UE Identifier)) and new demand parameters, etc. (corresponding to the above-mentioned first request sent to the access network node).

[0238] The message sending the registration request may be an access network (AN) message (carrying AN parameters and a registration request);

[0239] Specifically, the registration request may carry at least one of the following parameters: registration type, Subscription Concealed Identifier (SUCI) or Globally Unique Temporary UE Identity (5G-GUTI) or Permanent Equipment Identifier (PEI), Tracking Area Identity (TAI) last visited by the terminal (if available), security parameters, Network Slice Selection Assistance Information (NSSAI) requested by the terminal, mapping of NSSAI requested by the terminal, Protocol Data Unit (PDU) session state, active time requested by the terminal, LADN data network name (DNN) or indicator for requesting LADN information, non-access stratum (NAS) message container, preferred network behavior, UE paging probability information, UE policy container and UE radio capability ID, release request indication, and PEI.

[0240] AN parameters include: 5G-S (system) - Temporary Mobile Subscriber Identity (TMSI) or GUAMI (globally unique AMF identifier), the selected Public Land Mobile Network (PLMN) identity (Identity document, ID), and Network Slice Selection Assistance Information (NSSAI); it may also include an establishment cause (Establishment cause) or a registration cause to provide the reason for requesting to establish a Radio Resource Control (RRC) connection between the UE and the AN.

[0241] The Registration type is a mobile registration update, and the Preferred Network Behavior is a new requirement for the network.

[0242] 2. The radio access network (RAN) forwards the registration request according to the UE identifier (such as 5G-S-TMSI or GUAMI) and the N2 (interface) connection (corresponding to the above-mentioned sending of the first request to the first core network node according to the first request).

[0243] 3. When the 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 the node auto registration (Node Auto Register, NAR) to obtain a list of network nodes that can meet the UE requirements (ie, send a node discovery request to the NAR, corresponding to the above-mentioned first request, obtain the first parameter). 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 plug-and-play functions of nodes.

[0244] 4. NAR responds with a list of candidate network nodes and the node information of the candidate nodes (corresponding to the above-mentioned candidate network node information), i.e., NAR feedback node discovery response;

[0245] 5. The Old AMF performs network node selection (corresponding to determining the target network node according to the first parameter) based on the responded network node list, the responded node information, the UE information (corresponding to the device information of the above-mentioned terminal), the local policy (which may also be a policy obtained through the Policy Control Function (PCF), etc.; corresponding to the above-mentioned local node determination policy or the obtained node determination policy);

[0246] 6. The Old AMF performs AMF selection in the selected network node, which may be the default configuration AMF, or retrieves the optional AMF (corresponding to the information of the candidate core network node) through the Network Repository Function (NRF) and completes the AMF selection 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. (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);

[0247] 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 via the RAN); corresponding to the sending of the second request to the second core network node;

[0248] 8. If the New AMF determines that the registration request can be accepted based on the local information, it replies with a registration acceptance message (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);

[0249] 9. The Old AMF replies with the UE context to the New AMF (corresponding to sending the terminal context response to the second core network node), including the AN access information. After replying to the message, the locally maintained UE context may be deleted after receiving the response or after a timer expires.

[0250] 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 at the same time as sending the registration request, but is not limited to this.

[0251] 10. The New AMF maintains the UE context and assigns a new identifier (e.g., 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 based on the terminal context, a first response is sent to the terminal.

[0252] 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 can be deleted; it may also include AMF handover 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.

[0253] After the AMF changes, it may be necessary to update the access management policy (AM Policy) and / or UE policy association (UE Policy Association) with the PCF (Policy Control Function). The PCF policy update-related process can be found in the target-related solution, which will not be repeated here. The same applies to the following examples.

[0254] After a new network node is selected, whether other network elements remain in the old network node or migrate to the new network node as needed is not limited in this solution.

[0255] Example 1.2: RAN performs new network node selection (network node selection and AMF selection in Example 1.1 may also be performed by RAN, but is not limited to this);

[0256] Specifically, the distributed network registration update process 2 may be shown in FIG8 , and includes the following steps:

[0257] 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 type is a registration process for 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).

[0258] The message sending the registration request may be an AN message (carrying AN parameters and a registration request);

[0259] Specifically, the registration request may carry at least one of the following parameters: registration type, SUCI or 5G-GUTI or permanent equipment identifier PEI, tracking area identifier TAI last visited by the terminal (if available), security parameters, NSSAI 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 requesting LADN information, NAS (non-access stratum) message container, preferred network behavior, UE paging probability information, UE policy container and UE radio capability ID, release request indication, and PEI.

[0260] 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.

[0261] Among them, Registration type is mobile registration update, and Preferred Network Behaviour is the new requirement for the network.

[0262] 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 may identify the old network node and 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 determination of 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, such as 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), maintained node information, UE information (corresponding to the above-mentioned terminal device information, including UE device type, such as XR (Internet Data Center) device, Internet of Things IoT device, drone device, etc.), local policy (corresponding to the above-mentioned local node determination policy), etc. The above-mentioned information covers the user's direct and potential needs for the network. The UE device implicitly has requirements for network bandwidth, mobility, service range, etc. For example, a 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 capabilities and lower latency, etc.

[0263] 3. The RAN performs AMF selection in the selected network node (corresponding to the above-mentioned determination of the target network node according to the first request; determining the second core network node according to the target network node). It can be the default configuration AMF, or it can be retrieved through the NRF. The optional AMF (corresponding to the information of the above-mentioned candidate core network node) and based on the 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 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).

[0264] 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 information together for simultaneous selection) to avoid selecting the node first and then selecting AMF, which may not be the optimal selection result.

[0265] 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.

[0266] 5. If the New AMF determines that the registration request can be accepted based on the local information, it replies with a registration acceptance message (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);

[0267] 6. The Old AMF replies with the UE context to the New AMF (corresponding to sending the terminal context response to the second core network node), including the AN access information. After replying to the message, the locally maintained UE context may be deleted after receiving the response or after a timer expires.

[0268] 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 at the same time as sending the registration request, but is not limited to this.

[0269] 7. The New AMF maintains the UE context and assigns a new identifier (e.g., 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.

[0270] 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 can be deleted; it may also include AMF handover 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.

[0271] After a new network node is selected, whether other network elements remain in the old network node or migrate to the new network node as needed is not limited in this solution.

[0272] 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.

[0273] Among them, in the above Examples 1.1 and 1.2, when the performance of the base station (i.e., RAN) is limited or there is less distributed node information expected to be maintained for the base station in the core network, 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, permissions, 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.

[0274] Example 2: The network instructs the UE to register and update to a new network node due to a state change;

[0275] The UE initiating the registration update procedure in Example 1 may also be due to changes in network load that may not meet the UE's needs, or when operator policies expect the UE to register and update to a new network node, and the network instructs the UE to initiate the registration update procedure 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.

[0276] Specifically, the scheme for the network to indicate registration update to the UE may be as shown in FIG9 , including the following steps:

[0277] 1. The Unified Data Management (UDM) entity sends a registration update notification Nudm_UECM_REgistrationUpdateNotification to the AMF (corresponding to the first core network node mentioned above);

[0278] Among them, it may be due to the operator policy, etc. that the UDM updates the registration management context, 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 (execute step 2 below).

[0279] 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 an application function (AF), PCF, etc., that is, the registration update demand is triggered due to changes in application requirements or network policies.

[0280] 2. The AMF sends a RegistrationUpdate Request (or indication) to the UE, corresponding to the above-mentioned sending of a registration message to the terminal;

[0281] 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.

[0282] It is noted here that the above-mentioned registration update request (or indication) is only a message containing the meaning of the registration update request or indication, which can be a newly defined message, or the registration update meaning can be carried in a related message, which is not limited here.

[0283] 3. AMF sends a registration update notification response Nudm_UECM_REgistrationUpdateNotificationAck to UDM.

[0284] Example 3: The network notifies the UE after updating the UE registration to a new network node due to a state change;

[0285] Specifically, the distributed network registration update process 3 may be shown in FIG10 , and includes the following steps:

[0286] 1. Due to changes in network load, the UE's needs 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;

[0287] 2. Old AMF (corresponding to the above-mentioned first core network node) requests NAR to obtain a list of network nodes that can meet the UE requirements (ie, sends 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, used to maintain node granularity information and implement plug-and-play functions of nodes.

[0288] 3. NAR responds with a list of candidate network nodes and the node information of the candidate nodes (corresponding to the above-mentioned candidate network node information), i.e., NAR feedback node discovery response;

[0289] 4. The Old AMF performs network node selection (corresponding to determining the target network node according to the first parameter) based on the responded network node list, the responded node information, the UE information (corresponding to the device information of the above-mentioned terminal), the local policy (which may also be a policy obtained through the PCF, etc.; corresponding to the above-mentioned local node determination policy or the obtained node determination policy);

[0290] 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 an 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);

[0291] 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 via the RAN); corresponding to the sending of the second request to the second core network node;

[0292] 7. If the New AMF determines that the registration request can be accepted based on the local information, it replies with a registration acceptance message (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);

[0293] 8. The Old AMF replies with the UE context to the New AMF (corresponding to sending the terminal context response to the second core network node), including the AN access information. After replying to the message, the locally maintained UE context may be deleted after receiving the response or after a timer expires.

[0294] 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 at the same time as sending the registration request, but is not limited to this.

[0295] 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.

[0296] In this step, the New AMF may include interacting with the RAN to update the UE context information but is not limited thereto.

[0297] It is noted that: (1) in the above example, when the RAN or old network node performs network node selection, it can also obtain a list of candidate New network nodes through a centralized node in the distributed network (compared to Example 1, where the list is obtained through the 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 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.

[0298] (2) In the above examples 1 and 3, when the Old AMF determines that the current network node cannot meet the new requirements of the UE, it can also feed back the result to the RAN, and the RAN will perform 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-mentioned 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.

[0299] In addition, the diagrams in the above examples only illustrate the key processes. The authentication and contracting functions involved, such as the Authentication Server Function (AUSF) and UDM, are not described, but can be implemented by referring to the current relevant solutions. Furthermore, when there is an established PDU session, communication with the SMF (session management function) is involved, which can also be referred to the current relevant solutions and will not be repeated in the above examples.

[0300] Based on the above, the embodiments of the present disclosure provide a distributed network registration update method to implement a UE-initiated or network-initiated registration update process solution, wherein:

[0301] 1. The UE-initiated registration update procedure is initiated when the UE's network demand changes. The registration type may be mobility registration update, and the AN parameter may carry the registration reason. The registration message may carry future demand preferences. Based on this, the access network or core network selects the network node and AMF and completes the registration update procedure.

[0302] 2. The network-initiated registration update process is when changes such as network load may not be able to meet UE requirements, or when operator policies require 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;

[0303] 3. The above registration update process is for the core network or access network to execute the selection of new network nodes and new AMF.

[0304] 3.1 For the UE-initiated registration update process, the core network may select the network node based on the network node candidate list, network node information, UE information, local policies (possibly policies obtained through the PCF), etc., or the access network may select the network node based on network requirement parameters, connection relationship with the RAN, maintained node information, UE information, local policies, etc.

[0305] 3.2 The above UE-initiated registration update process can be the default configuration AMF, or it can be retrieved by NRF and the AMF selection is completed based on the AMF load, UE information, RAN information, etc.

[0306] 3.3 The above network node selection and AMF selection can be performed by first performing network node selection and then selecting AMF at the network node; or the network node and AMF information can be integrated to jointly complete the selection of network node and AMF.

[0307] In summary, this solution provides a distributed network registration update method to address the registration update issues for the 6G distributed architecture. Specifically, for the centralized 5GS mobility registration update, it expands the new scenario of registration updates between UEs or network-triggered network nodes in the distributed network architecture, solving the problems of distributed network node selection, new AMF selection, and information exchange in this scenario.

[0308] 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.

[0309] The embodiment of the present disclosure further provides a network registration update device, which is a first core network node, as shown in FIG11 , including a memory 111 , a transceiver 112 , and a processor 113 :

[0310] 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:

[0311] Performing a first operation for terminal registration update to the second core network node;

[0312] The first core network node and the second core network node belong to different network nodes;

[0313] The first operation includes at least one of the following:

[0314] receiving, through 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;

[0315] A registration message is sent to the terminal via the transceiver 112 , 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.

[0316] The network registration update device provided by the embodiment of the present disclosure 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, 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; 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, so as 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 related technology cannot support the network registration update between different network nodes.

[0317] Specifically, the transceiver 112 is configured to receive and send data under the control of the processor 113 .

[0318] In FIG11 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 113 and various circuits of memory represented by memory 111. 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 112 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or 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.

[0319] 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.

[0320] 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 based on 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.

[0321] 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.

[0322] In an embodiment of the present disclosure, the determining of the second core network node under the target network node includes: determining the second core network node under the target network node based on a default configuration or first information; wherein the first information includes at least one of the following: information of the candidate core network node; load of the core network node; device information of the terminal; information of the access network node.

[0323] 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.

[0324] In an embodiment of the present disclosure, 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 the centralized node or the 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.

[0325] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure 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 of this embodiment that are the same as the method embodiment will not be described in detail here.

[0326] The embodiment of the present disclosure further provides a network registration update device, which is a second core network node, as shown in FIG12 , including a memory 121, a transceiver 122, and a processor 123:

[0327] 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:

[0328] According to the second request, sending a terminal context request to the first core network node through the transceiver 122;

[0329] Receiving, through the transceiver 122, a terminal context response fed back by the first core network node;

[0330] Sending a first response or a first notification to the terminal through the transceiver 122 according to the terminal context response;

[0331] The second request is used to request registration or request registration update;

[0332] The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.

[0333] The network registration update device provided in the embodiment of the present disclosure 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; and 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 effectively solves the problem that related technologies cannot support network registration updates between different network nodes.

[0334] Specifically, the transceiver 122 is configured to receive and send data under the control of the processor 123 .

[0335] In FIG12 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linking together one or more processors represented by processor 123 and memory represented by memory 121. 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, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or the like. 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.

[0336] 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.

[0337] 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.

[0338] In the embodiment of the present disclosure, the operation further includes: sending a request acceptance response to the second request to the first core network node through the transceiver.

[0339] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure 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 of this embodiment that are the same as the method embodiment will not be described in detail here.

[0340] The embodiment of the present disclosure further provides a network registration update device, which is an access network node, as shown in FIG13 , including a memory 131 , a transceiver 132 , and a processor 133 :

[0341] 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:

[0342] Performing a second operation for the terminal to update registration from the first core network node to the second core network node;

[0343] The first core network node and the second core network node belong to different network nodes;

[0344] The second operation includes:

[0345] A first request sent by the 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.

[0346] The network registration update device provided by the embodiment of the present disclosure performs 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 network node to which the second core network node belongs are different; 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 related technology cannot support the network registration update between different network nodes.

[0347] Specifically, the transceiver 132 is configured to receive and send data under the control of the processor 133 .

[0348] In FIG13 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits linking together 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 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 132 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or 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.

[0349] 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.

[0350] Furthermore, the operation further 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.

[0351] 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: updated network requirement parameters; connection relationship with the access network node; maintained node information; device information of the terminal; local node determination strategy or acquired node determination strategy.

[0352] In an embodiment of the present disclosure, the determining of the second core network node under the target network node includes: determining the second core network node under the target network node based on a default configuration or first information; wherein the first information includes at least one of the following: information of the candidate core network node; load of the core network node; device information of the terminal; information of the access network node.

[0353] 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.

[0354] In an embodiment of the present disclosure, 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 the 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.

[0355] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure 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 of this embodiment that are the same as the method embodiment will not be described in detail here.

[0356] The embodiment of the present disclosure further provides a network registration update device, which is a terminal, as shown in FIG14 , including a memory 141 , a transceiver 142 , and a processor 143 :

[0357] 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:

[0358] Performing a third operation of registering and updating the terminal from the first core network node to the second core network node;

[0359] The first core network node and the second core network node belong to different network nodes;

[0360] The third operation includes at least one of the following:

[0361] Receiving, through the transceiver 142, 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;

[0362] 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.

[0363] The network registration update device provided by the embodiment of the present disclosure performs a third 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 network node to which the second core network node belongs are different; 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 related technology cannot support the network registration update between different network nodes.

[0364] Specifically, the transceiver 142 is configured to receive and send data under the control of the processor 143 .

[0365] In FIG14 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits connected together by one or more processors represented by processor 143 and memory represented by memory 141. The bus architecture may also connect 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 144 may be a plurality of components, including 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. For different user devices, the user interface 144 may also be an interface capable of connecting external or internal devices as required, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0366] 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.

[0367] In some embodiments, the processor 143 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.

[0368] The processor calls the computer program stored in the memory to execute any of the methods provided by the embodiments of the present disclosure according to the obtained executable instructions. The processor and the memory can also be arranged physically separately.

[0369] Furthermore, the operation also includes: 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 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.

[0370] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure 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.

[0371] The present disclosure also provides a network registration update device, which is applied to a first core network node, as shown in FIG15 , and includes:

[0372] The first execution unit 151 is configured to execute a first operation for registering and updating the terminal to the second core network node;

[0373] The first core network node and the second core network node belong to different network nodes;

[0374] The first operation includes at least one of the following:

[0375] receiving a terminal context request sent by the second core network node, and sending a terminal context response to the second core network node;

[0376] 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.

[0377] The network registration update device provided by the embodiment of the present disclosure 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, 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; 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, so as 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 related technology cannot support the network registration update between different network nodes.

[0378] 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.

[0379] 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.

[0380] In an embodiment of the present disclosure, the determining of the second core network node under the target network node includes: determining the second core network node under the target network node based on a default configuration or first information; wherein the first information includes at least one of the following: information of the candidate core network node; load of the core network node; device information of the terminal; information of the access network node.

[0381] 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.

[0382] In an embodiment of the present disclosure, 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.

[0383] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure 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 of this embodiment that are the same as the method embodiment will not be described in detail here.

[0384] The embodiment of the present disclosure further provides a network registration update device, which is applied to a second core network node, as shown in FIG16 , and includes:

[0385] The second sending unit 161 is configured to send a terminal context request to the first core network node according to the second request;

[0386] The third receiving unit 162 is configured to receive a terminal context response fed back by the first core network node;

[0387] The third sending unit 163 is configured to send a first response or a first notification to the terminal according to the terminal context response;

[0388] The second request is used to request registration or request registration update;

[0389] The first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.

[0390] The network registration update device provided in the embodiment of the present disclosure 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; and 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 effectively solves the problem that related technologies cannot support network registration updates between different network nodes.

[0391] Furthermore, the network registration update device also includes: a fourth receiving unit, configured 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.

[0392] In the embodiment of the present disclosure, 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.

[0393] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure 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 of this embodiment that are the same as the method embodiment will not be described in detail here.

[0394] The present disclosure also provides a network registration update device, which is applied to an access network node, as shown in FIG17 , and includes:

[0395] The second execution unit 171 is configured to execute a second operation for the terminal to update registration from the first core network node to the second core network node;

[0396] The first core network node and the second core network node belong to different network nodes;

[0397] The second operation includes:

[0398] 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.

[0399] The network registration update device provided by the embodiment of the present disclosure 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 network node to which the second core network node belongs are different; 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 related technology cannot support the network registration update between different network nodes.

[0400] 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.

[0401] 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: updated network requirement parameters; connection relationship with the access network node; maintained node information; device information of the terminal; local node determination strategy or acquired node determination strategy.

[0402] In an embodiment of the present disclosure, the determining of the second core network node under the target network node includes: determining the second core network node under the target network node based on a default configuration or first information; wherein the first information includes at least one of the following: information of the candidate core network node; load of the core network node; device information of the terminal; information of the access network node.

[0403] 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.

[0404] In an embodiment of the present disclosure, 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.

[0405] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure 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 of this embodiment that are the same as the method embodiment will not be described in detail here.

[0406] The present disclosure also provides a network registration update device, which is applied to a terminal, as shown in FIG18 , and includes:

[0407] The third execution unit 181 is 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;

[0408] The first core network node and the second core network node belong to different network nodes;

[0409] The third operation includes at least one of the following:

[0410] Receive 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;

[0411] Receive a first response or a first notification sent by the second core network node; the first response is a registration receive response or a registration update accept response, and the first notification is a registration update notification.

[0412] The network registration update device provided by the embodiment of the present disclosure 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 network node to which the second core network node belongs are different; 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 related technology cannot support the network registration update between different network nodes.

[0413] 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 the 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 based on the registration message; wherein the first request is used to request registration or request registration update.

[0414] It should be noted here that the above-mentioned device provided by the embodiment of the present disclosure can implement all the method steps implemented by 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.

[0415] It should be noted that the division of units in the embodiments of the present disclosure is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0416] 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 disclosure is essentially or the part that contributes to the relevant technology 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 for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0417] An embodiment of the present disclosure 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.

[0418] 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 (MO)), etc.), optical storage (such as compact disks (CD), digital video discs (DVD), Blu-ray discs (BD), high-definition versatile discs (HVD), etc.), and semiconductor memory (such as read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), non-volatile memory (NAND FLASH), solid-state disk (SSD)), etc.

[0419] 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 also achieve the same technical effects.

[0420] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0421] The present disclosure 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 disclosure. 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 produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0422] 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 a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0423] 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, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0424] It should be noted that it should be understood that the division of the above modules is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. Moreover, these modules can all be implemented in the form of software called by a processing element; or they can all be implemented in the form of hardware; or some modules can be implemented in the form of software called by a processing element, and some modules can be implemented in the form of hardware. For example, the determination module can be a separately established processing element, or it can be integrated into a chip of the above-mentioned device. In addition, it can also be stored in the memory of the above-mentioned device in the form of program code, and called by a processing element of the above-mentioned device to perform the functions of the above-mentioned determination module. The implementation of other modules is similar. In addition, these modules can all or partly be integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed by the hardware integrated logic circuit in the processor element or by instructions in the form of software.

[0425] For example, each module, unit, sub-unit or sub-module may be one or more integrated circuits configured to implement the above method, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs). For another example, when a module is implemented by scheduling program code through a processing element, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0426] The terms "first," "second," and the like in the specification and claims of the present disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of the present disclosure described herein may be implemented in a sequence other than that illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units need not be limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or devices. In addition, the use of "and / or" in the specification and claims to indicate at least one of the connected objects, for example, A and / or B and / or C, means that seven situations are included: A alone, B alone, C alone, both A and B present, both B and C present, both A and C present, and all A, B, and C present. Similarly, the use of "at least one of A and B" in the specification and claims should be understood to mean "A alone, B alone, or both A and B present."

[0427] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is intended to include these modifications and variations.

Claims

1. A network registration update method, applied to a first core network node, comprising: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, comprising: 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, wherein: 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, further comprising: 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, comprising: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, comprising: 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, 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; 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, further comprising: 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, comprising a memory, a transceiver, and a processor: Memory for storing computer programs; 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 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. The network registration update device according to claim 18, wherein: The operations also include: Before receiving the terminal context request sent by the second core network node, receiving, by the transceiver, 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 through the transceiver; The operations also include: Receiving, by the transceiver, 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.

20. The network registration update device according to claim 19, wherein: 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.

21. The network registration update device according to claim 19, wherein: 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.

22. The network registration update device according to claim 19, wherein: 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.

23. The network registration update device according to claim 19, wherein: The determining a target network node according to the first request, and determining a second core network node under the target network node, includes: According to the first request, sending 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 through the transceiver; The 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 through the transceiver.

24. A network registration update device, the network registration update device being a second core network node, comprising a memory, a transceiver, and a processor: Memory for storing computer programs; 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: 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 receiving response or a registration updating accepting response, and the first notification is a registration Update notifications.

25. The network registration update device according to claim 24, wherein: The operations also include: Before sending the terminal context request to the first core network node through the transceiver according to the second request, the second request sent by the first core network node or the access network node is received through the transceiver.

26. The network registration update device according to claim 24, wherein: The operations also include: A request acceptance response for the second request is sent to the first core network node via the transceiver.

27. A network registration update device, the network registration update device is an access network node, comprising a memory, a transceiver, and a processor: Memory for storing computer programs; 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.

28. The network registration update device according to claim 27, wherein: The operations also include: Before sending the second request to the second core network node, a target network node is determined according to the first request, and a second core network node under the target network node is determined.

29. The network registration update device according to claim 28, wherein: 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.

30. The network registration update device according to claim 28, wherein: 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.

31. The network registration update device according to claim 28, wherein: 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.

32. The network registration update device according to claim 28, wherein: The determining a target network node according to the first request, and determining a second core network node under the target network node, includes: According to the first request, sending a second determination request for determining a target network node and a second core network node to a centralized node through the transceiver; The information of the target network node and the second core network node fed back by the centralized node is received through the transceiver.

33. A network registration update device, the network registration update device is a terminal, comprising a memory, a transceiver, and a processor: Memory for storing computer programs; 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: 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.

34. The network registration update device according to claim 33, wherein: The operation further 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 an access network node through the transceiver; The first request is used to request registration or request registration update.

35. A network registration update device, applied to a first core network node, comprising: 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.

36. The network registration updating device according to claim 35, further comprising: A first receiving unit, configured to receive a first request sent by an access network node before receiving a terminal context request sent by the second core network node; A first determining unit, configured to determine a target network node according to the first request, and determine a second core network node under the target network node; A first sending unit, configured to send a second request to the second core network node; The device further comprises: A second receiving unit, configured 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.

37. The network registration update device according to claim 36, wherein: 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.

38. The network registration updating device according to claim 36, wherein: 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.

39. The network registration update device according to claim 36, wherein: 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.

40. The network registration update device according to claim 36, wherein: 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.

41. A network registration update device, applied to a second core network node, comprising: 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.

42. The network registration updating device according to claim 41, further comprising: The fourth receiving unit is 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.

43. The network registration updating device according to claim 41, further comprising: The fourth sending unit is used to send a request acceptance response to the second request to the first core network node.

44. A network registration update device, applied to an access network node, comprising: 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.

45. The network registration updating device according to claim 44, further comprising: The second determining unit is configured to determine a target network node according to the first request and determine a second core network node under the target network node before sending a second request to the second core network node.

46. ​​The network registration update device according to claim 45, wherein: 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.

47. The network registration updating device according to claim 45, wherein: 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.

48. The network registration updating device according to claim 45, wherein: 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.

49. The network registration update device according to claim 45, wherein: 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.

50. A network registration update device, applied to a terminal, comprising: The third execution unit is used to execute the registration update from the first core network node to the second core network node for the terminal. The third operation of the 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.

51. The network registration updating device according to claim 50, further comprising: A fifth sending unit, configured 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, According to the registration message, a first request is sent to the access network node; wherein the first request is used to request registration or request registration update.

52. A readable storage medium storing a computer program, wherein the computer program is configured to cause a processor to execute the method according to any one of claims 1 to 17.

Citation Information

Patent Citations

  • Method and apparatus for updating multicast and broadcast service system information in a wireless access system

    US20130028165A1

  • Communication method and apparatus

    WO2022056796A1

  • Communication control method

    WO2022085757A1

  • Method and apparatur for multicast session signaling in wireless communication system

    WO2022231303A1

  • Group notification and confirmation for multicast broadcast services

    WO2022261272A1