Node cooperation method and apparatus, network device, storage medium, and program product
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA MOBILE COMM LTD RES INST
- Filing Date
- 2024-12-06
- Publication Date
- 2026-06-09
Smart Images
Figure CN122179845A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of mobile communication technology, specifically to a node collaboration method, apparatus, network device, storage medium, and program product. Background Technology
[0002] In the context of a 6G distributed autonomous network architecture, user data is still activated on the local subnet, and terminal registration and data storage also occur locally. However, because some subnets will be simplified to networks with only basic functions, they cannot independently complete complex tasks, necessitating the introduction of collaborative mechanisms such as capability negotiation to support complete 6G information services. In a distributed autonomous network, since some subnets, after simplification, only possess basic functions, authentication, data analysis, and capability opening become optional, leading to difficulties in the smooth operation of collaborative mechanisms. Summary of the Invention
[0003] At least one embodiment of this application provides a node collaboration method, apparatus, network device, storage medium, and program product to solve the problem of subnet collaboration mechanism not operating smoothly in existing distributed autonomous networks.
[0004] To solve the above-mentioned technical problems, this application is implemented as follows:
[0005] In a first aspect, embodiments of this application provide a node collaboration method, applied to a first node, comprising:
[0006] Receive the first request sent by the Network Function (NF) service consumer;
[0007] If no target data corresponding to the first request can be found, a second request is sent to the second node; the second request is used to obtain the target data.
[0008] Receive feedback information sent by the second node in accordance with the second request;
[0009] The first request is processed based on the feedback information.
[0010] Furthermore, sending the second request to the second node includes:
[0011] If the first node cannot determine the node information of the second node, a third request is sent to the third node, the third request being used to obtain the node information of the second node;
[0012] Receive node information fed back by the third node;
[0013] The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key;
[0014] The second node is determined based on the node information, and the second request is sent to the second node;
[0015] The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0016] Further, processing the first request based on the feedback information includes:
[0017] Send the processing result to the NF service consumer;
[0018] The processing result includes one of the following: the target data, error information, and default information.
[0019] Furthermore, the method also includes:
[0020] Upon receiving the fourth request from the NF service consumer, a first notification is generated; the first notification is used to instruct the NF service consumer to perform a registration or deregistration operation on the first node.
[0021] If a communication session is established with a third node, the first notification is sent to the third node.
[0022] Furthermore, the method also includes:
[0023] Upon receiving the notification message from the NF service consumer, a fifth request is generated;
[0024] When a communication session is established with a third node, the fifth request is sent to the third node; the fifth request is used to request the third node to update the data based on the changes in the user data of the first node.
[0025] The fifth request carries user data change information and at least one of the following target information: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0026] Secondly, embodiments of this application provide a node collaboration method applied to a second node, comprising:
[0027] Receive a second request sent by the first node, the second request being used to request the acquisition of target data;
[0028] Based on the second request, send feedback information to the first node;
[0029] The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0030] Thirdly, embodiments of this application provide a node collaboration method applied to a third node, including:
[0031] Receive a third request sent by the first node, the third request being used to obtain node information of the second node;
[0032] According to the third request, send the node information of the second node to the first node;
[0033] The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key.
[0034] Furthermore, the method also includes:
[0035] The system receives a fifth request sent by the first node, the fifth request carrying user data change information and at least one of the following target information: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, the causal consistency sequence number being used to characterize the correspondence between the generation order and arrival order of messages for the same event.
[0036] Based on the target information, determine whether to execute the fifth request.
[0037] Further, determining whether to execute the fifth request based on the target information includes:
[0038] If the target information is verified, the user data is updated, and the target node information of the target subscription node corresponding to the fifth request is obtained;
[0039] A sixth request is generated and sent to the fourth node when a communication session is established with the fourth node;
[0040] The sixth request includes the target information and the change information of the user data.
[0041] The target node information includes at least one of the following: the location area of the target subscription node, the local node ID, the last heartbeat time, and the key.
[0042] Fourthly, embodiments of this application provide a node collaboration method applied to a fourth node, including:
[0043] Receive a sixth request sent by a third node, the sixth request carrying change information of user data on the first node, and target information of the first node;
[0044] If the target information passes verification, the user data is updated based on the change information, and an update confirmation message is generated.
[0045] If the target information fails verification, a rejection message is generated;
[0046] When establishing a communication session with the third node, the update confirmation information or the rejection information is sent to the third node;
[0047] The target information includes at least one of the following: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0048] Fifthly, embodiments of this application provide a node collaboration device applied to a first node, comprising:
[0049] The first receiving module is used to receive the first request sent by the Network Function (NF) service consumer;
[0050] The first sending module is used to send a second request to the second node when the target data corresponding to the first request cannot be found; the second request is used to obtain the target data.
[0051] The second receiving module is used to receive feedback information sent by the second node according to the second request;
[0052] The processing module is used to process the first request based on the feedback information.
[0053] Sixthly, embodiments of this application provide a node collaboration device applied to a second node, comprising:
[0054] The third receiving module is used to receive a second request sent by the first node, the second request being used to request the acquisition of target data;
[0055] The second sending module is used to send feedback information to the first node according to the second request;
[0056] The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0057] In a seventh aspect, embodiments of this application provide a node collaboration device applied to a third node, comprising:
[0058] The fourth receiving module is used to receive a third request sent by the first node, the third request being used to obtain node information of the second node;
[0059] The third sending module is used to send the node information of the second node to the first node according to the third request;
[0060] The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key.
[0061] Eighthly, embodiments of this application provide a node collaboration device applied to a fourth node, comprising:
[0062] The fifth receiving module is used to receive a sixth request sent by the third node, wherein the sixth request carries change information of user data on the first node and target information of the first node;
[0063] The modification module is used to update user data according to the modification information when the target information passes verification, and generate update confirmation information.
[0064] The generation module is used to generate a rejection message if the target information fails verification.
[0065] The fourth sending module is used to send the update confirmation information or the rejection information to the third node when establishing a communication session with the third node;
[0066] The target information includes at least one of the following: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0067] Ninthly, embodiments of this application provide a network device, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described above.
[0068] In a tenth aspect, embodiments of this application provide a computer-readable storage medium storing a program that, when executed by a processor, implements the steps of the method described above.
[0069] Eleventhly, a computer program product is provided, including computer instructions that, when executed by a processor, implement the steps of the method described above.
[0070] Compared with existing technologies, the node collaboration method, apparatus, network device, storage medium, and program product provided in this application embodiment, when the first node cannot find the target data corresponding to the first request sent by the NF service consumer locally, obtains the target data from the second node by sending a second request to the second node. Through cooperation between nodes, the NF service consumer can obtain target data from the local node; and when the target data cannot be found on the local node, it can obtain the target data from the second node (registration node). Through cooperation between nodes, various functions of the distributed autonomous network are completed. Attached Figure Description
[0071] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:
[0072] Figure 1 This is a flowchart illustrating the application of the node collaboration method of this application to the first node.
[0073] Figure 2 This is one of the logical flow diagrams of the node collaboration method in an embodiment of this application;
[0074] Figure 3 This is a second schematic diagram of the logical flow of the node collaboration method in an embodiment of this application;
[0075] Figure 4 This is a flowchart illustrating the application of the node collaboration method of this application to a second node.
[0076] Figure 5 This is a flowchart illustrating the node collaboration method applied to a third node according to an embodiment of this application.
[0077] Figure 6 This is the third logical flow diagram of the node collaboration method in this application embodiment;
[0078] Figure 7This is a flowchart illustrating the application of the node collaboration method of this application to the fourth node.
[0079] Figure 8 This is one of the module schematic diagrams of the node collaboration device according to an embodiment of this application;
[0080] Figure 9 This is a second schematic diagram of the node collaboration device according to an embodiment of this application;
[0081] Figure 10 This is the third schematic diagram of the node collaboration device according to an embodiment of this application;
[0082] Figure 11 This is the fourth schematic diagram of the node collaboration device according to an embodiment of this application;
[0083] Figure 12 This is one of the structural schematic diagrams of a network device according to an embodiment of this application;
[0084] Figure 13 This is a second schematic diagram of the network device according to an embodiment of this application;
[0085] Figure 14 This is the third schematic diagram of the network device according to an embodiment of this application;
[0086] Figure 15 This is the fourth schematic diagram of the network device according to an embodiment of this application;
[0087] Figure 16 This is a schematic diagram of the structure of a network device according to an embodiment of this application. Detailed Implementation
[0088] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.
[0089] The terms “first,” “second,” etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. The terms “and / or” in the specification and claims indicate at least one of the connected objects.
[0090] The technologies described in this document are not limited to NR systems and Long Time Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in various wireless communication systems such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably. CDMA systems can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. TDMA systems can implement radio technologies such as the Global System for Mobile Communication (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.21 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE and more advanced LTE (such as LTE-A) are newer versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2).The techniques described herein can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. However, the following description describes NR systems for illustrative purposes, and NR terminology is used in most of the following description, although these techniques can also be applied to applications beyond NR systems.
[0091] The following description provides examples and is not intended to limit the scope, applicability, or configuration set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the spirit and scope of this disclosure. Various procedures or components may be appropriately omitted, substituted, or added to the examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with reference to certain examples may be combined in other examples.
[0092] Mobile communication has now reached the 5G stage and is moving towards 6G. A key characteristic of the 5G network architecture is its service-based network functions and processes. In 5G networks, during processes such as User Equipment (UE) registration, authentication, and N2 handover, network functions (NFs) such as Access and Mobility Management Functions (AMF) and User Data Management (UDM) may interact with other NFs within the same network to obtain data and perform their functions.
[0093] In the context of 6G distributed autonomous network architecture, user data is still deployed on the local subnet, and UE registration and data storage also occur locally. However, since some subnets will be simplified to networks with only basic functions and cannot independently complete complex tasks, collaborative mechanisms such as capability negotiation are needed to support complete 6G information services. The capability negotiation mechanism allows NFs of a subnet to request network services or data that are not available locally from the core node and adjacent subnets.
[0094] When facing the future 6G distributed autonomous simplified network architecture, the existing technical solutions for synchronizing UDM data across subnets in distributed networks have the following shortcomings:
[0095] 1. Current methods, primarily based on centralized deployment and subscription-based synchronization of NF state information, struggle to maintain effective inter-network isolation under the new 6G distributed autonomous architecture. Each subnet node and core node possesses autonomy, with its own Network Repository Function (NRF) or Service Communication Proxy (SCP) framework and independent NF discovery and selection strategies. Furthermore, sensitive and / or volatile NF information within a subnet (such as load and capacity) should not be exposed to other subnets, even if subscribed to. Existing methods can only subscribe to the full state notification of an NF, leading to unnecessary information exposure.
[0096] 2. Distributed systems are primarily used for UDM load balancing and lack efficient cross-subnet capability negotiation and data synchronization mechanisms. In distributed autonomous networks, some subnets, after simplification, will only have basic functions, with authentication, data analysis, and capability exposure becoming optional. Some processes may require cross-subnet communication using the NRF / SCP service framework as a bridge. However, without exposing relevant information, external SCPs lack unified control over the exchange and synchronization of relevant information (such as UE context, NF status, etc.), leading to signaling waste due to the establishment of too many channels.
[0097] The solution proposed in this application aims to address the two aforementioned deficiencies and resolve the corresponding technical problems in UDM data synchronization.
[0098] Please refer to Figure 1 The node collaboration method provided in this application embodiment, applied to a first node, includes the following steps:
[0099] Step 101: Receive the first request sent by the Network Function (NF) service consumer;
[0100] Step 102: If no target data corresponding to the first request can be found, a second request is sent to the second node; the second request is used to obtain the target data.
[0101] Step 103: Receive feedback information sent by the second node according to the second request;
[0102] Step 104: Process the first request based on the feedback information.
[0103] In this embodiment of the application, when the NF service consumer accesses the first node (the user's local node), it determines whether the service is provided by the local UDM, or by requesting the UDM of other nodes to provide services through the NRF / SCP service framework, or by both the local node and other nodes simultaneously, based on the requested service type (including subscription data management, UE context management, UE authentication, etc.) and the type of service operation to be performed (including registration / unregistration / notification service operations, acquisition service operations, update / change service operations).
[0104] Optionally, the first request is a request for an operation to obtain a service.
[0105] It should be noted that retrieval-type service operations refer to retrieving or obtaining data from the local node or other node UDMs, but do not involve modifying the data in the UDM. Examples include services such as subscription data management, UE context management, and UE authentication.
[0106] In this embodiment of the application, the NF consumer first accesses the local node UDM to attempt to obtain the target data;
[0107] If the target data is retrieved at the local node UDM, the target data is returned to the NF consumer. This process is closed-loop within the subnet and does not require interaction with other nodes.
[0108] If the target data cannot be retrieved on the local node, a data retrieval request (the first request) is generated through the NRF / SCP service framework. The first request should include: the location area where the local node is located, the local node ID, the network element type that initiated the request, the key, and other additional information.
[0109] The node collaboration method provided in this application embodiment allows a first node to obtain the target data from a second node by sending a second request to a second node when the first node cannot find the target data corresponding to the first request sent by the NF service consumer locally. Through node collaboration, the NF service consumer can obtain the target data from its local node; and when the target data cannot be found on the local node, it can obtain the target data from the second node (registered node). This node collaboration enables the completion of various functions of the distributed autonomous network.
[0110] Optionally, sending the second request to the second node includes:
[0111] If the first node cannot determine the node information of the second node, a third request is sent to the third node, the third request being used to obtain the node information of the second node;
[0112] Receive node information fed back by the third node;
[0113] The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key;
[0114] The second node is determined based on the node information, and the second request is sent to the second node;
[0115] The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0116] It should be noted that the causal consistency mentioned refers to the fact that for the same event, the message generated earlier arrives first.
[0117] Optionally, the first node is the user's local node, the second node is the user's registration node, the third node is the core node of the distributed autonomous network, and the fourth node is a distributed node of the distributed autonomous network.
[0118] In this embodiment of the application, the second request is sent to the NRF / SCP service framework of the registration node (second node) to obtain the target data from the registration node;
[0119] If the registered node is unknown or does not respond, a third request is generated and sent to the core node (third node) to obtain the node list of the registered node (second node) through the NRF / SCP service framework of the core node; then, according to the node list of the registered node, the second request is sent to the registered node.
[0120] It should be noted that the core node (third node) stores a list of all users' registered nodes; after receiving the third request, the third node will not directly process such query requests to ensure the network isolation and autonomy of each node.
[0121] The node collaboration method in this application embodiment, when the first node cannot determine the node information of the second node, first obtains the node information of the second node from a third node, and then obtains the target data through the second node. This method enables data acquisition to be achieved through collaboration between nodes.
[0122] Optionally, processing the first request based on the feedback information includes:
[0123] Send the processing result to the NF service consumer;
[0124] The processing result includes one of the following: the target data, error information, and default information.
[0125] It should be noted that after receiving the second request, the second node determines whether to accept or respond to the second request based on the node ID, permission level, key, timestamp, or causal consistency sequence number of the first node carried in the second request. If it responds, it sends the target data to the first node; if it does not respond, it sends error information or default information to the first node.
[0126] Optionally, the method further includes:
[0127] The processing result is sent to the NF service consumer.
[0128] In the embodiments of this application, such as Figure 2 As shown, for retrieval-type service operations: these refer to service operations that retrieve or obtain data from the local node or other node UDMs, but do not involve modifying the data in the UDM. Such operations are involved in service processes such as subscription data management, UE context management, and UE authentication.
[0129] The workflow framework for retrieving operations is as follows:
[0130] 1. The NF consumer first accesses the local node UDM to attempt to obtain the target data;
[0131] 2. If the required data is retrieved at the local node UDM, it is returned to the NF consumer; the process is closed-loop within the subnet and does not require interaction with other nodes;
[0132] 3. If the required data cannot be retrieved at the local node, a data retrieval request will be generated through the NRF / SCP service framework, which should include the location area where the local node is located, the local node ID, the network element type that initiated the request, the key (optional), and other additional information.
[0133] 4. If the registered node of the corresponding user is unknown or does not respond, the data retrieval request is sent to the NRF / SCP service framework of the core node to request the user's list of registered nodes. The core node stores a record of the registered node list for each user, but does not directly process such query requests to ensure the network isolation and autonomy of each node;
[0134] 5. The NRF / SCP service framework of the core node returns a list of registered nodes for this user to the requesting node. The list should include the location region, node ID, last heartbeat time, key (optional), and other additional information of the registered nodes;
[0135] 6. If the user's registration node for the relevant data is known, then the data retrieval request is directly sent to the NRF / SCP service framework of the relevant node;
[0136] 7. The NRF / SCP service framework of this distributed node (the user's registration node) requests the corresponding data from the UDM of this node based on the received data acquisition request;
[0137] 8. The core distributed node UDM determines whether to accept the request based on the source node ID (and its permission level), key, timestamp, and causal consistency sequence number. If accepted, the corresponding data is returned to the NRF / SCP service framework; if rejected, a rejection message and reason are returned.
[0138] 9. Send the requested information or error information to the NRF / SCP service framework of the node that initiated the data acquisition request (some possible reasons for rejection include request timeout, the receiving node not allowing the node to access this information, or the information not being found in the UDM of the receiving node, etc. Depending on the configuration of each node, if a rejection is made, an error message or default information can be returned);
[0139] 10. The NRF / SCP service framework of the initiating node returns the acquired data or processing results to the NF service consumer.
[0140] Optionally, the method further includes:
[0141] Upon receiving the fourth request from the NF service consumer, a first notification is generated; the first notification is used to instruct the NF service consumer to perform a registration or deregistration operation on the first node.
[0142] If a communication session is established with a third node, the first notification is sent to the third node.
[0143] Optionally, the fourth request is a registration, deregistration, or notification request.
[0144] This type of service operation is typically involved in services such as UE context management; after the operation is completed, the local node's UDM only notifies the core node, without involving querying or changing the UDM data of the core node or other nodes.
[0145] like Figure 3 As shown:
[0146] 1. NF consumers first access the local node UDM to perform registration / to register;
[0147] 2. After that, the local node's UDM generates a non-real-time notification to be sent to the core node, which should include the location area where the local node is located, the local node ID, the network element type that initiated the request, the key (optional), and other additional information.
[0148] 3. Store the notification in the message queue to be pushed, but do not actively establish a session with the core node. Instead, push it together when the next communication session with the core node is established. Decouple the data changes generated by local node UDM registration / deregistration from the announcements to other nodes, thus achieving sub-network autonomy.
[0149] The node collaboration method in this application embodiment includes a message queue to be pushed to the first node.
[0150] In this embodiment, the synchronization of local data with other nodes follows the principle of causal consistency. After the operation is completed, other nodes are not immediately notified; instead, the data is stored in the message queue to be pushed within the NRF / SCP service framework. The data is pushed together with the target node during the next communication established within the service framework, achieving non-real-time synchronization. It does not require strong consistency but only causal consistency (i.e., for the same event, the message generated first arrives first). Furthermore, it does not require waiting for other nodes to confirm the local node's logs, reducing the time and communication resources wasted on repeatedly establishing sessions and ensuring the autonomy of the local node.
[0151] Optionally, the method further includes:
[0152] Upon receiving the notification message from the NF service consumer, a fifth request is generated;
[0153] When a communication session is established with a third node, the fifth request is sent to the third node; the fifth request is used to request the third node to update the data based on the changes in the user data of the first node.
[0154] The fifth request carries user data change information and at least one of the following target information: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0155] Optionally, the fifth request is a request for an update / change type service operation.
[0156] In this embodiment of the application, when user data changes, the NF service consumer modifies the UDM data of the local node and informs the registration node, core node and distribution node through the local node.
[0157] It should be noted that the registered node can be either the core node or a distributed node.
[0158] In this embodiment of the application, when user data transmission changes, the NF service consumer modifies the UDM data of the local node; and informs the local node of the data change of the NRF / SCP service framework; the local node generates the fifth request and sends the fifth request to the core node.
[0159] like Figure 4 As shown in the figure, this application embodiment also provides a node collaboration method applied to a second node, including the following steps:
[0160] Step 401: Receive a second request sent by the first node, the second request being used to request the acquisition of target data;
[0161] Step 402: Send feedback information to the first node according to the second request;
[0162] The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0163] Optionally, according to the second request, feedback information is sent to the first node, including:
[0164] Based on the second request, determine the legitimacy of the first node;
[0165] If the first node is valid, the feedback information is sent to the first node.
[0166] like Figure 5 As shown in the embodiments of this application, a node collaboration method is also provided, applied to a third node, including the following steps:
[0167] Step 501: Receive a third request sent by the first node, the third request being used to obtain node information of the second node;
[0168] Step 502: Based on the third request, send the node information of the second node to the first node;
[0169] The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key.
[0170] Optionally, the third request is sent when the first node cannot determine the node information of the second node, and is used to obtain relevant information about the second node from the third node.
[0171] In the node collaboration method of this application embodiment, the first node can obtain the node information of the second node through the third node, thereby successfully obtaining the target data from the second node.
[0172] Optionally, the method further includes:
[0173] The system receives a fifth request sent by the first node, the fifth request carrying user data change information and at least one of the following target information: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, the causal consistency sequence number being used to characterize the correspondence between the generation order and arrival order of messages for the same event.
[0174] Based on the target information, determine whether to execute the fifth request.
[0175] It should be noted that the fifth request is a request generated for synchronizing changes in user data.
[0176] When user data changes, after modifying the UDM data of the local node, the fifth request is generated through the local NRF / SCP service framework, but it does not need to be sent to the third node immediately. The fifth request is sent to the third node when the next communication session is established.
[0177] Optionally, determining whether to execute the fifth request based on the target information includes:
[0178] If the target information is verified, the user data is updated, and the target node information of the target subscription node corresponding to the fifth request is obtained;
[0179] A sixth request is generated and sent to the fourth node when a communication session is established with the fourth node;
[0180] The sixth request includes the target information and the change information of the user data.
[0181] The target node information includes at least one of the following: the location area of the target subscription node, the local node ID, the last heartbeat time, and the key.
[0182] In this embodiment of the application, for update or change type service operations, such as Figure 6 As shown:
[0183] 1. When user data changes, the NF service consumer modifies the local UDM data;
[0184] 2. Subsequently, the NF service consumer notifies the local node's NRF / SCP service framework of the data changes;
[0185] 3. The local node's NRF / SCP service framework generates a data change request and sends the specific change content to the core node's NRF / SCP service framework; this should include the location area where the local node is located, the local node ID, the network element type that initiated the request, the key (optional), and other additional information;
[0186] 4. Store the request in the message queue to be pushed, without having to actively establish a session with the core node, and push it together when the next communication session with the core node is established;
[0187] 5. After receiving a data change request from a distributed node (local node), the NRF / SCP service framework of the core node sends the update content to its own UDM and obtains a list of legitimate subscribers for the update. The list should include the location region of the registered nodes, the local node ID, the last heartbeat time, the key (optional), and other additional information.
[0188] 6. The core node's UDM determines whether to accept the request based on the source node ID (and its permission level), key, timestamp, and causal consistency sequence number. If accepted, the UDM data is updated, and a list of legitimate subscribers is returned to the NRF / SCP service framework; the list should include the node IDs of those registered nodes. If rejected, a rejection message and reason for rejection are returned.
[0189] 7. The NRF / SCP service framework of the core node determines which nodes in the list are legitimate subscribers based on their ID, location region, last heartbeat time, key (optional), and other additional information. Then, it generates data change requests for those legitimate subscribers.
[0190] 8. Store the request in the message queue to be pushed, without having to actively establish a session with the legitimate subscriber nodes, and push it together when the next communication session is established with them;
[0191] 9. After receiving a data change request from the core node, the NRF / SCP framework of the distributed node (i.e., the legitimate subscriber node) sends the updated content to its own UDM.
[0192] 10. The distributed node's UDM determines whether to accept the update based on the source node ID (and its permission level), key, timestamp, and causal consistency sequence number, and returns the execution result or rejection information to the node's NRF / SCP framework.
[0193] 11. Store the result in the message queue to be pushed. Instead of actively establishing a session with the core node, push it together when the next communication session with the core node is established.
[0194] like Figure 7 As shown in the figure, this application embodiment also provides a node collaboration method applied to a fourth node, including the following steps:
[0195] Step 701: Receive a sixth request sent by the third node, the sixth request carrying change information of user data on the first node, and target information of the first node;
[0196] Step 702: If the target information passes verification, update the user data according to the change information and generate update confirmation information;
[0197] Step 703: If the target information fails verification, generate a rejection message;
[0198] Step 704: When establishing a communication session with the third node, send the update confirmation information or the rejection information to the third node;
[0199] The target information includes at least one of the following: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0200] The node collaboration method in this application embodiment enables the user's local node to synchronize the user's changed data to the core node and distributed nodes through the NRF / SCP framework; and it has a pending message queue mechanism, which reduces the time and communication resources wasted by repeatedly establishing sessions.
[0201] The various methods of the embodiments of this application have been described above. Apparatus for implementing the above methods will now be provided.
[0202] like Figure 8 As shown in the illustration, this application also provides a node collaboration device 800, applied to a first node, comprising:
[0203] The first receiving module 801 is used to receive a first request sent by a network function (NF) service consumer;
[0204] The first sending module 802 is used to send a second request to the second node when the target data corresponding to the first request cannot be found; the second request is used to obtain the target data.
[0205] The second receiving module is used to receive feedback information sent by the second node according to the second request;
[0206] The processing module 803 is used to process the first request based on the feedback information.
[0207] The node collaboration device provided in this application embodiment enables network function (NF) service consumers to obtain target data from local nodes through collaboration between nodes; and if the target data cannot be found on the local node, the target data can be obtained from a second node (registration node). Through collaboration between nodes, various functions of the distributed autonomous network can be completed.
[0208] like Figure 9 As shown in the illustration, this application also provides a node collaboration device 900, applied to a second node, comprising:
[0209] The third receiving module 901 is used to receive a second request sent by the first node, the second request being used to request the acquisition of target data;
[0210] The second sending module 902 is used to send feedback information to the first node according to the second request;
[0211] The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0212] like Figure 10 As shown in the illustration, this application also provides a node collaboration device 1000, applied to a third node, comprising:
[0213] The fourth receiving module 1001 is used to receive a third request sent by the first node, the third request being used to obtain node information of the second node;
[0214] The third sending module 1002 is used to send the node information of the second node to the first node according to the third request;
[0215] The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key.
[0216] In the node collaboration device of this application embodiment, the first node can obtain the node information of the second node through the third node, thereby successfully obtaining the target data from the second node.
[0217] like Figure 11 As shown, this application embodiment also provides a node collaboration device 1100, applied to a fourth node, including:
[0218] The fifth receiving module 1101 is used to receive a sixth request sent by the third node, wherein the sixth request carries change information of user data on the first node and target information of the first node;
[0219] The modification module 1102 is used to update user data according to the modification information when the target information passes verification, and generate update confirmation information.
[0220] The generation module 1103 is used to generate a rejection message if the target information fails verification.
[0221] The fourth sending module 1104 is used to send the update confirmation information or the rejection information to the third node when establishing a communication session with the third node;
[0222] The target information includes at least one of the following: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0223] The node collaboration device in this application embodiment enables the user's local node to synchronize the user's changed data to the core node and distributed nodes through the NRF / SCP framework; and it has a pending message queue mechanism, which reduces the time and communication resources wasted by repeatedly establishing sessions.
[0224] Please refer to Figure 12 This application also provides a network device 1200, including: a transceiver 1201 and a processor 1202;
[0225] The transceiver 1201 is used to receive a first request sent by a Network Function (NF) service consumer.
[0226] If no target data corresponding to the first request can be found, a second request is sent to the second node; the second request is used to obtain the target data.
[0227] Receive feedback information sent by the second node in accordance with the second request;
[0228] The processor 1202 is used to process the first request based on the feedback information.
[0229] Please refer to Figure 13 This application also provides a network device 1300, including: a transceiver 1301;
[0230] The transceiver 1301 is used to receive a second request sent by the first node, the second request being used to request the acquisition of target data;
[0231] Based on the second request, send feedback information to the first node;
[0232] The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0233] Please refer to Figure 14 This application also provides a network device 1400, including: a transceiver 1401;
[0234] The transceiver 1401 is used to receive a third request sent by the first node, the third request being used to obtain node information of the second node;
[0235] According to the third request, send the node information of the second node to the first node;
[0236] The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key.
[0237] Please refer to Figure 15 This application also provides a network device 1500, including: a transceiver 1501 and a processor 1502;
[0238] The transceiver 1501 is used to receive a sixth request sent by a third node, the sixth request carrying change information of user data on the first node and target information of the first node.
[0239] The processor 1502 is configured to update user data based on the change information and generate update confirmation information when the target information passes verification.
[0240] If the target information fails verification, a rejection message is generated;
[0241] The transceiver 1501 is also used to send the update confirmation information or the rejection information to the third node when establishing a communication session with the third node;
[0242] The target information includes at least one of the following: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
[0243] Please refer to Figure 16This application also provides a network device 1600, including a processor 1601, a memory 1602, and a computer program stored in the memory 1602 and executable on the processor 1601. When the computer program is executed by the processor 1601, it implements the various processes of the above-described node cooperation method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0244] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the above-described node collaboration method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
[0245] This application also provides a computer program product, including computer instructions. When executed by a processor, the computer instructions implement the various processes of the above-described node collaboration method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.
[0246] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0247] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0248] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.
Claims
1. A node collaboration method, applied to a first node, characterized in that, include: Receive the first request sent by the Network Function (NF) service consumer; If no target data corresponding to the first request can be found, a second request is sent to the second node. The second request is used to obtain the target data; Receive feedback information sent by the second node in accordance with the second request; The first request is processed based on the feedback information.
2. The node collaboration method according to claim 1, characterized in that, Sending the second request to the second node includes: If the first node cannot determine the node information of the second node, a third request is sent to the third node, the third request being used to obtain the node information of the second node; Receive node information fed back by the third node; The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key; The second node is determined based on the node information, and the second request is sent to the second node; The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
3. The node collaboration method according to claim 1, characterized in that, The step of processing the first request based on the feedback information includes: Send the processing result to the NF service consumer; The processing result includes one of the following: the target data, error information, and default information.
4. The node collaboration method according to claim 1, characterized in that, The method further includes: Upon receiving the fourth request from the NF service consumer, a first notification is generated; the first notification is used to instruct the NF service consumer to perform a registration or deregistration operation on the first node. If a communication session is established with a third node, the first notification is sent to the third node.
5. The node collaboration method according to claim 1, characterized in that, The method further includes: Upon receiving the notification message from the NF service consumer, a fifth request is generated; When a communication session is established with a third node, the fifth request is sent to the third node; the fifth request is used to request the third node to update the data based on the changes in the user data of the first node. The fifth request carries user data change information and at least one of the following target information: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
6. A node collaboration method, applied to a second node, characterized in that, include: Receive a second request sent by the first node, the second request being used to request the acquisition of target data; Based on the second request, send feedback information to the first node; The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
7. A node collaboration method applied to a third node, characterized in that, include: Receive a third request sent by the first node, the third request being used to obtain node information of the second node; According to the third request, send the node information of the second node to the first node; The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key.
8. The method according to claim 7, characterized in that, The method further includes: The system receives a fifth request sent by the first node, the fifth request carrying user data change information and at least one of the following target information: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, the causal consistency sequence number being used to characterize the correspondence between the generation order and arrival order of messages for the same event. Based on the target information, determine whether to execute the fifth request.
9. The method according to claim 8, characterized in that, The step of determining whether to execute the fifth request based on the target information includes: If the target information is verified, the user data is updated, and the target node information of the target subscription node corresponding to the fifth request is obtained; A sixth request is generated and sent to the fourth node when a communication session is established with the fourth node; The sixth request includes the target information and the change information of the user data. The target node information includes at least one of the following: the location area of the target subscription node, the local node ID, the last heartbeat time, and the key.
10. A node collaboration method applied to a fourth node, characterized in that, include: Receive a sixth request sent by a third node, the sixth request carrying change information of user data on the first node, and target information of the first node; If the target information passes verification, the user data is updated based on the change information, and an update confirmation message is generated. If the target information fails verification, a rejection message is generated; When establishing a communication session with the third node, the update confirmation information or the rejection information is sent to the third node; The target information includes at least one of the following: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
11. A node collaboration device, applied to a first node, characterized in that, include: The first receiving module is used to receive the first request sent by the Network Function (NF) service consumer; The first sending module is used to send a second request to the second node if the target data corresponding to the first request cannot be found. The second request is used to obtain the target data; The second receiving module is used to receive feedback information sent by the second node according to the second request; The processing module is used to process the first request based on the feedback information.
12. A node collaboration device, applied to a second node, characterized in that, include: The third receiving module is used to receive a second request sent by the first node, the second request being used to request the acquisition of target data; The second sending module is used to send feedback information to the first node according to the second request; The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
13. A node collaboration device applied to a third node, characterized in that, include: The fourth receiving module is used to receive a third request sent by the first node, the third request being used to obtain node information of the second node; The third sending module is used to send the node information of the second node to the first node according to the third request; The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key.
14. A node collaboration device applied to a fourth node, characterized in that, include: The fifth receiving module is used to receive a sixth request sent by the third node, wherein the sixth request carries change information of user data on the first node and target information of the first node; The modification module is used to update user data according to the modification information when the target information passes verification, and generate update confirmation information. The generation module is used to generate a rejection message if the target information fails verification. The fourth sending module is used to send the update confirmation information or the rejection information to the third node when establishing a communication session with the third node; The target information includes at least one of the following: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
15. A network device, characterized in that, Includes transceivers and processors, among which, The transceiver is used to receive a first request sent by a Network Function (NF) service consumer. If no target data corresponding to the first request can be found, a second request is sent to the second node; the second request is used to obtain the target data. Receive feedback information sent by the second node in accordance with the second request; The processor is configured to process the first request based on the feedback information.
16. A network device, characterized in that, Including transceivers, among which, The transceiver is used to receive a second request sent by the first node, the second request being used to request the acquisition of target data; Based on the second request, send feedback information to the first node; The second request carries at least one of the following: the node ID, permission level, key, timestamp, and causal consistency sequence number of the first node. The causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
17. A network device, characterized in that, Including transceivers, among which, The transceiver is used to receive a third request sent by the first node, the third request being used to obtain node information of the second node; According to the third request, send the node information of the second node to the first node; The node information includes at least one of the following: the location area of the second node, the node ID, the last heartbeat time, and the key.
18. A network device, characterized in that, Includes transceivers and processors, among which, The transceiver is used to receive a sixth request sent by a third node, the sixth request carrying change information of user data on the first node, and target information of the first node; The processor is configured to update user data based on the change information and generate update confirmation information when the target information passes verification. If the target information fails verification, a rejection message is generated; The transceiver is also used to send the update confirmation information or the rejection information to the third node when establishing a communication session with the third node; The target information includes at least one of the following: the ID, permission level, key, timestamp, and causal consistency sequence number of the first node, wherein the causal consistency sequence number is used to characterize the correspondence between the generation order and the arrival order of messages for the same event.
19. A network device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, the program, when executed by the processor, implementing the steps of the method as described in any one of claims 1 to 10.
20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 10.
21. A computer program product, characterized in that, Includes computer instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 10.