CN119172775A - Network information management method, network information management device, electronic equipment and medium - Google Patents
Network information management method, network information management device, electronic equipment and medium Download PDFInfo
- Publication number
- CN119172775A CN119172775A CN202411238272.5A CN202411238272A CN119172775A CN 119172775 A CN119172775 A CN 119172775A CN 202411238272 A CN202411238272 A CN 202411238272A CN 119172775 A CN119172775 A CN 119172775A
- Authority
- CN
- China
- Prior art keywords
- network
- node
- configuration information
- network node
- central
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 87
- 230000004044 response Effects 0.000 claims abstract description 74
- 238000000034 method Methods 0.000 claims abstract description 35
- 238000004891 communication Methods 0.000 claims description 42
- 238000012545 processing Methods 0.000 claims description 35
- 238000012508 change request Methods 0.000 claims description 18
- 238000012544 monitoring process Methods 0.000 claims description 10
- 230000005856 abnormality Effects 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 3
- 239000003795 chemical substances by application Substances 0.000 description 105
- 230000006870 function Effects 0.000 description 21
- 230000002159 abnormal effect Effects 0.000 description 16
- 230000008859 change Effects 0.000 description 11
- 230000003993 interaction Effects 0.000 description 9
- 230000007246 mechanism Effects 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 230000002452 interceptive effect Effects 0.000 description 7
- 230000006855 networking Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 4
- 238000012795 verification Methods 0.000 description 4
- 239000000284 extract Substances 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 230000002708 enhancing effect Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000013070 change management Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0846—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on copy from other elements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The disclosure provides a network information management method, a network information management device, electronic equipment and a computer readable storage medium, and belongs to the technical field of computers. The method comprises the steps of responding to a network registration request sent by a first network node received by a central network node, adding first node configuration information into central network configuration information, sending registration request response information to the first network node through the central network node so that the first network node synchronously adds central node configuration information and/or second node configuration information according to the registration request response information, responding to the first network node meeting preset conditions, and sending notification information containing the first node configuration information to the second network node through the central network node so that the second network node adds the first node configuration information into the second network configuration information according to the notification information. The method and the device can synchronously manage the node configuration information of the network node.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a network information management method, a network information management device, an electronic apparatus, and a computer readable storage medium.
Background
With the rapid development of communication technology, information communication between networks is one of the key points of current attention. The existing 5G (5 th Generation Mobile Communication Technology, fifth generation mobile communication technology) network adopts two-stage NRF (NF Repository Function, network storage function) for service management, where the provincial NRF is responsible for service registration and discovery of control plane network elements in the provincial NRF, and the backbone NRF is mainly responsible for forwarding network element discovery query and response messages across provincials. Taking fig. 1 as an example, when a service consumer in province a, such as AMF (ACCESS AND Mobility Management Function ) 110 in province a, needs to provide an initial registration/session establishment service for a user belonging to province B, a UDM (Unified DATA MANAGEMENT, unified data management function) discovery request needs to be initiated to NRF (NF Repository Function, network storage function) 120 in province to query user Subscription data, carrying a user Subscription PERMANENT IDENTITY (Subscription permanent identifier) identifier as a discovery parameter. The NRF 120 of this province finds that the user number segment does not match with the UDM of this province, then forwards the discovery request to the backbone NRF 130, the backbone NRF 130 forwards to the NRF 140 of the B province based on the number segment configuration of different provinces, the NRF 140 of the B province stores the UDM 150 registration information of this province, if including address information, the UDM 150 service configuration information of this province is returned to the backbone NRF 130 through the service discovery response, and then the backbone NRF 130 forwards to vNRF of the a province, finally the AMF of the a province acquires the UDM configuration information of the B province, then caches the discovery result and directly initiates the service request to the UDM of the B province. For UE (User Equipment) or NF (Network Function) in province B, the AMF in province a is vAMF (VISITED AMF, visited access and mobility management Function), the NRF in province a is vNRF (VISITED NRF, visited Network storage Function), the NRF in province B is hNRF (home NRF, home Network storage Function), and the UDM is hUDM (home UDM).
However, the above network information management method is limited to the discovery and request of the cross-network service of the user data network element, and cannot be applied to the application scenario of diversified cross-network cooperative service, and the interaction flow is complex, the timeliness is poor, and it is not possible to efficiently cooperate with each participating network to obtain the service information of the cooperative network more comprehensively, for example, it is not possible to apply to the 6G (6 th Generation Mobile Communication Technology, sixth generation mobile communication technology) network. Therefore, how to effectively manage the network information is a technical problem to be solved in the prior art.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure provides a network information management method, a network information management device, an electronic apparatus, and a computer readable storage medium, so as to overcome, at least to some extent, the problem of low network information management efficiency in the prior art.
Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.
According to one aspect of the disclosure, a network information management method is provided, and is applied to a network information management system, wherein the network information management system at least comprises a first network node, a central network node and a second network node, the method comprises the steps of adding first node configuration information to central network configuration information in response to the central network node receiving a network registration request sent by the first network node, the network registration request at least comprises first node configuration information of the first network node, the central network configuration information at least comprises central node configuration information of the central network node and/or second node configuration information of the second network node, sending registration request response information to the first network node through the central network node so that the first network node can synchronously add the central node configuration information and/or the second node configuration information according to the registration request response information, responding to the first network node and meeting preset conditions, sending notification information containing the first node configuration information to the second network node through the central network node, and enabling the first node to be added to the first node according to the first node configuration information.
According to one aspect of the disclosure, a network information management device is provided, and the network information management device is applied to a network information management system, wherein the network information management system at least comprises a first network node, a central network node and a second network node, the device comprises a first information management module, a third information management module and a first information management module, the first information management module is used for responding to a network registration request sent by the central network node, the first information management module is used for responding to a network registration request sent by the central network node, the first information management module is used for responding to the central network node, the first node configuration information is added to the central network configuration information, the central network registration request at least comprises first node configuration information of the first network node, the central network configuration information at least comprises second node configuration information of the central network node and/or second node configuration information of the second network node, the second information management module is used for sending registration request response information to the first network node through the central network node, so that the first network node can synchronously add the central node configuration information and/or the second node configuration information according to the registration request response information, the first network node can be used for synchronously, the central network node configuration information is added to the central network node configuration information, the first node configuration information is used for sending the first node configuration information.
According to one aspect of the disclosure, there is provided an electronic device comprising a processor and a memory for storing executable instructions of the processor, wherein the processor is configured to perform the method of any one of the above via execution of the executable instructions.
According to one aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of any one of the above.
Exemplary embodiments of the present disclosure have the following advantageous effects:
The method comprises the steps of receiving a network registration request sent by a first network node by a central network node, adding first node configuration information to the central network configuration information, wherein the network registration request at least comprises first node configuration information of the first network node, the central network configuration information at least comprises central node configuration information of the central network node and/or second node configuration information of a second network node, sending registration request response information to the first network node through the central network node so that the first network node synchronously adds the central node configuration information and/or the second node configuration information according to the registration request response information, the registration request response information comprises the central network configuration information, and sending notification information containing the first node configuration information to the second network node through the central network node in response to the first network node meeting preset conditions, so that the second network node adds the first node configuration information to the second network configuration information according to the notification information. On one hand, the present exemplary embodiment proposes a new network information management method, which is different from the prior art in that when network information interaction is performed, information synchronization is required to be implemented between a plurality of network elements or devices through complex and cumbersome interaction operations, and the present exemplary embodiment can implement synchronization of node configuration information of each network node based on a simple and convenient flow, on the other hand, when a first network node meets a preset condition, the present exemplary embodiment can timely synchronize the first node configuration information to second network configuration information, thereby implementing accurate monitoring of the first network node and effective update of node configuration information in each network node.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
Fig. 1 schematically illustrates a network information communication diagram in the related art;
fig. 2 schematically shows an architecture diagram of network information management in the present exemplary embodiment;
fig. 3 schematically shows an architecture diagram of another network information management in the present exemplary embodiment;
fig. 4 schematically shows a flowchart of a network information management method in the present exemplary embodiment;
fig. 5 schematically shows an interactive flowchart of a network information management method according to the present exemplary embodiment;
Fig. 6 schematically shows an interactive sub-flowchart of a network information management method in the present exemplary embodiment;
fig. 7 schematically shows another interactive sub-flowchart of a network information management method in the present exemplary embodiment;
fig. 8 schematically shows an interactive sub-flowchart of another network information management method in the present exemplary embodiment;
fig. 9 schematically shows an interactive sub-flowchart of still another network information management method in the present exemplary embodiment;
Fig. 10 schematically shows a block diagram of a network information management apparatus in the present exemplary embodiment;
fig. 11 schematically shows an electronic device for implementing the above method in the present exemplary embodiment.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein, but rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
The exemplary embodiments of the present disclosure first provide a network information management method applied to a network information management system, where the network service system includes at least a first network node, a central network node, and a second network node. The Network node may include NF (Network Function), service proxy, etc. of the Network node, the first Network node may refer to a Network node to be registered, the second Network node may refer to a registered Network node, and the central Network node refers to a management center serving as Network service configuration information.
Fig. 2 shows a system architecture of a network information management method in this exemplary embodiment, where the system may include a distributed network a 210, i.e. a first network node, a distributed network B220, i.e. a second network node, and a central network 230, i.e. a central network node. Wherein, the distributed network a 210 may include a plurality of NFs 211 and service agents 212 of the distributed network a, the distributed network B220 may include a plurality of NFs 221 and service agents 222 of the distributed network B, and the central network 230 may include a plurality of NFs 231 and service agents 232 of the central network. The service agent can be used as a registration management center of the network internal service to synchronize the node configuration information of each participating networking network. The node configuration information may include network identities such as MCC (mobile device network code) +mnc (mobile network code) +specific number, or a brand new numbering system, network types such as a central network/distributed network, address information of service agents such as IP address or FQDN (Fully qualified domain name, fully defined domain name), location and coverage information, network capability information exposed externally as required, network functions including NF service list and supporting parameters such as number segment, DNN (Data Network Name ) and user authentication mode, etc., but does not include privacy information such as NF instance identities and addresses, network performance including capacity and load, etc.
Specifically, the service agent of the central network serves as a network service configuration information management center, which can manage registration, change and notification of service configuration information of each distributed network, and can monitor the state of each distributed network through a heartbeat mechanism. In the present exemplary embodiment, the distributed network may generate node configuration information of its own network service as needed, register and update the service agent to the central network through the service agent, and receive a notification of change of the node configuration information of the service agent of the central network with respect to other network nodes. The service agent can also be used as an anchor point of cross-network cooperation and is responsible for processing and forwarding request and response messages of the cross-network service, and topology hiding is carried out on message contents related to internal service privacy, so that safety is ensured.
Fig. 3 shows a system architecture of another network information management method in this exemplary embodiment, the service agent may be an enhanced service agent that is co-located by NRF (NF Repository Function, network storage function) and SCP (Service Communication Proxy, service communication agent) after enhancing public service, and as shown in fig. 3, the network information system may include a distributed network a310, i.e. a first network node, a distributed network B320, i.e. a second network node, and a central network 330, i.e. a central network node. Wherein, the distributed network a310 may include a plurality of NFs 311 and an enhanced service agent 312 of the distributed network a, the enhanced service agent 312 may include an NRF 3121 of the distributed network a and an SCP 3122 of the distributed network a, the distributed network B320 may include a plurality of NFs 321 and an enhanced service agent 322 of the distributed network B, the enhanced service agent 322 may include an NRF 3221 of the distributed network B and an SCP 3222 of the distributed network B, the central network 330 may include a plurality of NFs 331 and an enhanced service agent 332 of the central network, and the enhanced service agent 332 may include an NRF 3321 of the central network and an SCP 3322 of the central network.
Besides managing registration and discovery of NF inside a core network, the enhanced NRF may be additionally responsible for synchronization of network configuration information lists of each participating network, where the NRF of the central network may be used as a network configuration information management center, the NRF of the distributed network needs to register and update node configuration information of its own network to the central node NRF, and receive update notification of node configuration information of other network nodes of the central network NRF, and the enhanced SCP may be responsible for indirect communication of NF inside the core network in a D mode (a communication technology), and may also be responsible for forwarding of cross-network service requests and responses and additional processing, such as topology hiding and generation and verification of security tokens, so as to ensure security of cross-network cooperation, and the SCP may obtain configuration information of the target network from the NRF by subscription or discovery, such as carrying service discovery parameters, so as to perform cross-network cooperation processing.
In the present exemplary embodiment, the node configuration information includes the number of the network, mcc+mnc+specific network identifier, network type, central network/distributed network, SCP address, IP or FQDN form (no need of exposing NRF address information because service discovery through NRF is not needed for cross-network service collaboration), location and coverage information, network capability information exposed externally as required, network function including externally exposed NF service list and supporting parameters such as number segment, DNN and user authentication mode, etc., but not including detailed privacy information such as identifier and address of each NF instance, network performance including capacity and load, etc.
The following describes the present exemplary embodiment with reference to fig. 4, and as shown in fig. 4, the network information management method may include the following steps S410 to S430:
In step S410, in response to the central network node receiving the network registration request sent by the first network node, the first node configuration information is added to the central network configuration information, wherein the network registration request at least comprises the first node configuration information of the first network node, and the central network configuration information at least comprises the central node configuration information of the central network node and/or the second node configuration information of the second network node.
The first network node may be any node that needs to perform network registration, and the first network node may be a plurality of nodes, for example, a network node A1 to be registered, a network node A2 to be registered, and the like, and the second network node may be any node that has performed network registration, and the second network node may be a plurality of nodes, for example, a registered network node B1, a registered network node B2, and the like. In this exemplary embodiment, when the first network node is operating normally, for example, after network a is online, a network registration request may be sent to the central network node to join in network management of the central network node. The network registration request refers to a request sent by the first network node for joining the central network node to perform network management, and the network registration request at least can include first node configuration information of the first network node.
In the present exemplary embodiment, the node configuration information may include a network number or identifier, for example, mcc+mnc+specific number, or a brand new numbering system, a network type, for example, a central network/distributed network, address information of a service agent, for example, an IP address or FQDN, location and coverage information, network capability information exposed to the outside as required, for example, network functions including NF service lists and supporting parameters, such as number segments, DNN, and user authentication modes, etc., but does not include privacy information, such as identification of each NF instance and address, network performance including capacity and load, etc.
The first node configuration information refers to service configuration information related to the first network node, for example, when the first network node is an NF of the distributed network, the first node configuration information may include an identification of the NF of the first network node, a service list of the NF, a type of the NF, an IP (Internet Protocol ) address, a support parameter, or the like, and the support parameter may include a database number segment, or a support parameter providing an AI (ARTIFICIAL INTELLIGENCE ) function or other 6G function.
The central network node receives a network registration request sent by the first network node, adds first node configuration information to central network configuration information, where the central network configuration information is information configured by a central network node side and used for maintaining and managing node configuration information of each network node, and may be managed in a list form, for example, may be a network configuration information list maintained by the central network node side. In the present exemplary embodiment, the central network configuration information includes at least central node configuration information of the central network node and/or second node configuration information of the second network node, that is, the central network node may configure a network configuration information list to manage configuration information of itself or other registered network nodes through the network configuration information list.
In an exemplary embodiment, the first network node may include a network function NF of the first distributed network and a service proxy of the first distributed network, and the first network node sending the network registration request to the central network node may include the steps of:
After the network function instance of the first distributed network is online, the configuration information of the service agent of the first distributed network can be registered to the service agent of the first distributed network, for example, the information such as NF identification, NF service list, IP address, supported service parameters and the like is registered to the service agent of the first distributed network, and after the service agent of the first distributed network judges that all planned NF are online, the service agent of the first distributed network can generate the configuration information of the first node and initiate a network registration request to a central network node by utilizing the configuration information of the first node.
It should be noted that, in this exemplary embodiment, the configuration information includes explicit configuration information and implicit configuration information, explicit configuration information may be set up from the configuration information of the configuration information to generate the configuration information of the first node, and the configuration information of the first node is sent to the central network node, for example, after the service agent of the first distributed network determines that all planned NFs are online, the service agent may hide the implicit configuration information such as NF instance identifiers and IP addresses, and only extract explicit configuration information such as NF types and supporting parameters, so as to generate the configuration information of the first node.
Step S420, the registration request response information is sent to the first network node through the central network node, so that the first network node synchronously adds the central node configuration information and/or the second node configuration information according to the registration request response information, wherein the registration request response information comprises the central network configuration information.
After receiving the network registration request containing the first node configuration information, the central network node may add the first node configuration information to the central network configuration information after the verification is successful. Registration request response information may then be returned to the first network node to inform the first network node of its registration request processing results. The registration request processing result may include central node configuration information of the central network node and/or second node configuration information of the second network node, where the central node configuration information is similar to the second node configuration information, and may include configuration information of the network node, for example, related information of NF, or supported service parameters, and the like, similar to the first node configuration information. After receiving the registration request response information, the first network node may add the central node configuration information and the second node configuration information to the node synchronously, for example, may also maintain a first network configuration information list to manage node configuration information of each network node.
Step S430, in response to the first network node meeting the preset condition, the central network node sends notification information containing the first node configuration information to the second network node, so that the second network node adds the first node configuration information to the second network configuration information according to the notification information.
Finally, the central network node may further send notification information including the first node configuration information to the second network node when the first network node meets a preset condition, so as to add the first node configuration information to the second network configuration information, thereby implementing information synchronization of the network configuration information in each network node. The second network configuration information may be a local network configuration information list configured by the second network node, and the notification information may include first node configuration information of the first network node, and when the second network node receives the notification information, the second network node may extract the first node configuration information from the first node configuration information and store the first node configuration information in the local second network configuration information. In addition, the notification information may also include central node configuration information of the central network node, so that the second network node can synchronously update the central node configuration information while saving the first node configuration information.
In this exemplary embodiment, the first network node meeting the preset condition may include that the state of the first network node meets the preset condition, for example, when the state of the first network node is an on-line state, a normal connection state, or the like, notification information including configuration information of the first node is sent to the second network node.
Based on the above description, in the present exemplary embodiment, in response to a network registration request sent by a first network node being received by a central network node, first node configuration information is added to the central network configuration information, the network registration request includes at least first node configuration information of the first network node, the central network configuration information includes at least central node configuration information of the central network node and/or second node configuration information of a second network node, registration request response information is sent to the first network node through the central network node, so that the first network node synchronously adds the central node configuration information and/or the second node configuration information according to the registration request response information, the registration request response information includes the central network configuration information, and in response to the first network node meeting a preset condition, notification information including the first node configuration information is sent to the second network node through the central network node, so that the second network node adds the first node configuration information to the second network configuration information according to the notification information. On one hand, the present exemplary embodiment proposes a new network information management method, which is different from the prior art in that when network information interaction is performed, information synchronization is required to be implemented between a plurality of network elements or devices through complex and cumbersome interaction operations, and the present exemplary embodiment can implement synchronization of node configuration information of each network node based on a simple and convenient flow, on the other hand, when a first network node meets a preset condition, the present exemplary embodiment can timely synchronize the first node configuration information to second network configuration information, thereby implementing accurate monitoring of the first network node and effective update of node configuration information in each network node.
In an exemplary embodiment, in response to the first network node meeting the preset condition, sending, by the central network node, notification information including the first node configuration information to the second network node may include:
The central network node monitors the first network node and sends notification information containing the first node configuration information to the second network node in response to monitoring that the first network node meets a preset condition.
The central network node monitors the first network node, which may be monitoring a state of the first network node, where the state of the first network node may include that the network of the first network node is normally running on line, has a fault, or is off line, and so on. In order to ensure that network configuration information in each network node can be synchronized in time so as to effectively manage node configuration information of the multiparty network nodes, the present exemplary embodiment may monitor the first network node through the central network node, so that the central network node may send notification information including the first node configuration information to the second network node when monitoring that the first network node meets a preset condition, and execute a corresponding instruction.
Wherein the corresponding instructions may include updating the central network configuration information, for example, modifying first node configuration information of the first network node therein, or deleting first node configuration information of the first network node, and the corresponding instructions may further include sending a notification to the second network node to cause the second network node to update or delete the first node configuration information in the second network configuration information, and so on.
In an exemplary embodiment, the central network node monitoring the first network node may include:
and establishing heartbeat communication connection between the central network node and the first network node according to a preset heartbeat cycle interval so that the central network node monitors the first network node through the heartbeat communication connection.
The present exemplary embodiment may establish a heartbeat communication connection between the central network node and the first network node according to a preset heartbeat period, so that the central network node monitors the first network node through the heartbeat communication connection, for example, monitors a state of the first network node, where the first network node meets a preset condition, and may be that the state of the first network node meets the preset condition.
A heartbeat communication connection is a network communication mechanism that may be used to detect and maintain the active state of a communication link. It is achieved by periodically sending and receiving specific data packets, such as heartbeat packets, which can be set to a small size in order to check whether both parties to the communication are still online and able to receive data. In this exemplary embodiment, when the central network node returns the registration request response information to the first network node, the central network node may simultaneously carry a preset heartbeat cycle, and the first network node and the central network node may respectively start a heartbeat timer to establish a heartbeat communication connection between the first network node and the central network node. In this exemplary embodiment, the central network node may send a heartbeat packet to the first network node according to a preset heartbeat cycle, and after receiving the heartbeat packet sent by the central network node, the first network node may return acknowledgement information to the central network node, which indicates that the heartbeat packet sent by the central network node has been received, and all is normal. If the first network node does not receive the heartbeat packet sent by the central network node within the preset time period, or the first network node does not return acknowledgement information to the central network node or the central network node receives response abnormal information sent by the first network node, the communication link can be considered to have a problem. At this point, corresponding measures may be taken, such as re-establishing a connection or informing the network node, to ensure reliable transmission of the data.
Fig. 5 shows an interaction flow chart of network information management in the present exemplary embodiment, where the network information management system includes a first network node, a central network node, and a second network node, where the first network node is taken as a distributed network a, specifically may include NF 510 of the distributed network a and service agent 520 of the distributed network a, the central network node includes central network service agent 530, and the second network node is taken as a distributed network B, specifically may include service agent 540 of the distributed network B for illustration, and specifically may include the following steps:
step S502, after the NF 510 instance of the distributed network A is online, registering the configuration information of the NF 510 instance of the distributed network A to a service agent 520 of the distributed network A, wherein the configuration information of the NF can comprise NF identification, NF service list, IP address, supported service parameters and the like;
Step S504, after the service agent 520 of the distributed network A judges that all planned NF' S are online, generating first node configuration information of the distributed network A, wherein the first node configuration information is explicit configuration information extracted from configuration information of the NF 510 of the distributed network A, that is, when the service agent 520 of the distributed network A generates the first node configuration information, implicit configuration information such as NF instance identification and IP address needs to be hidden, the first node configuration information is generated only according to the NF type and the explicit configuration information such as supporting parameters, and is sent to the central network service agent 530;
step S506, the service agent 520 of the distributed network A initiates a network registration request to the central network service agent 530, wherein the network registration request is used for requesting network configuration registration, and the network registration request can comprise first node configuration information, and can also implicitly subscribe to changes of network state information of other participants, such as subscribing to changes of state information of the distributed network B and the central network, and the state information can comprise network online, offline, failure and the like;
step S508, the central network service agent 530 stores the first node configuration information of the distributed network a into the network configuration information list of the central network;
Step S510, the central network service agent 530 sends a registration request response message to the service agent 520 of the distributed network A, informing the distributed network A that the network configuration registration is successful;
step S512, the service agent 520 of the distributed network A stores node configuration information of other network nodes, wherein the node configuration information of the other network nodes comprises central node configuration information of a central network and second node configuration information of the distributed network B;
Step S514, the service agent 520 and the central network service agent 530 of the distributed network a respectively start a heartbeat timing device, so that the central network can monitor the status of the distributed network a through the heartbeat mechanism, for example, the status of the distributed network a such as on-line, off-line or failure;
Step S516, the central network sends notification information to the service agent 540 of the registered distributed network B through the central network service agent 530 to inform the distributed network B that the distributed network A is on line, wherein the notification information may include first node configuration information of the distributed network A, and in the present exemplary embodiment, the notification information may also be sent to other registered distributed networks;
step S518, the service agent 540 of the distributed network B adds the first node configuration information of the distributed network a to the network configuration information list of the distributed network B;
In step S520, the service agent 540 of the distributed network B replies a notification response to the central network service agent 530, which has informed the central network service agent 530 that the configuration information synchronization is completed.
In an exemplary embodiment, the network information management method may further include:
Deleting first node configuration information of the first network node from the central network configuration information in response to detecting that an abnormal condition occurs in the heartbeat communication connection;
And sending an exception notification to the second network node so that the second network node deletes the first node configuration information of the first network node from the second network configuration information.
The abnormal situation of the heartbeat communication connection may include abnormal situations of the first network node, such as a heartbeat request timeout of the first network node, a first network node offline or other faults of the first network node, etc., and abnormal situations of the central network node, such as a heartbeat response timeout of the central network node or other faults of the central network node, etc.
In this exemplary embodiment, when an abnormal condition of the heartbeat communication connection is detected, for example, when the heartbeat communication connection is abnormal due to the first network node, the first node configuration information of the first network node may be deleted from the central network configuration information, for example, the first node configuration information may be deleted from the network configuration information list configured on the central network node side, and an abnormal notification may be sent to the second network node, so as to inform the second network node that the heartbeat communication connection between the central network node and the first network node is abnormal, so that the second network node deletes the first node configuration information of the first network node in the network configuration information thereof.
Fig. 6 is a flowchart showing an interaction of a network information management method in the case of abnormal heartbeat communication connection in the present exemplary embodiment, where the network information management system may include a service agent 610 of a distributed network a, a central network service agent 620, and a service agent 630 of a distributed network B, and may specifically include the following steps:
Step S610, when the central network service agent 620 detects that the heartbeat request of the service agent 610 of the distributed network a is timed out through the heartbeat communication connection, it is determined that the service agent 610 of the distributed network a may fail, so that the distributed network a cannot be accessed;
Step S620, the central network service agent 620 deletes the first node configuration information of the distributed network a in the central network configuration information list;
Step S630, the central network service agent 620 notifies the service agents of other network nodes, such as the service agent 630 of the distributed network B, of the status information of the distributed network a, such as a downlink message;
In step S640, the service agent 630 of the distributed network B deletes the first node configuration information of the distributed network a from the network configuration information list of the distributed network B.
In an exemplary embodiment, the network information management method may further include:
And in response to detecting abnormal conditions of the heartbeat communication connection, enabling the first network node to delete the added central node configuration information and/or the second node configuration information, and sending a network registration request to the central network node again.
In this exemplary embodiment, when an abnormal condition of the heartbeat communication connection is detected, for example, when the heartbeat communication connection is abnormal due to a central network node, the first network node may be caused to delete the added central node configuration information and/or the second node configuration information, and send a network registration request to the central network node again, for example, the first network node periodically initiates a network registration request of the network configuration to the central network node again until the re-registration is successful. In addition, when the first network node deletes the added configuration information of the central node and/or the configuration information of the second node, the central network node and the second network node can delete the configuration information of the first node on the local side correspondingly according to actual needs, so as to realize management synchronization of the configuration information.
Fig. 7 is an interactive flowchart of a network information management method in the case of abnormal heartbeat communication connection in the present exemplary embodiment, where the network information management system may include a service agent 710 of a distributed network a and a central network service agent 720, and may specifically include the following steps:
Step S710, detecting that the service agent 710 of the distributed network a is working properly through the heartbeat communication connection, but that the heartbeat response of the central network service agent 720 is timeout;
Step S720, the service agent 710 of the distributed network a deletes the node configuration information of the synchronized other network nodes, such as the central node configuration information of the central network and the second node configuration information of the distributed network B;
In step S730, the service agent 710 of the distributed network a initiates again a network registration request for registering network configuration information to the central network service agent 720 according to a preset period until re-registration is successful.
In an exemplary embodiment, the network information management method may further include:
The central network node responds to receiving the configuration information change request sent by the first network node, updates the central network configuration information of the central network node according to the configuration information change request, and sends the configuration information change request to the second network node, so that the second network node updates the second network configuration information of the second network node according to the configuration information change request.
In practical applications, the first network node may have some situations, for example, capacity expansion, offline, or load change, where the configuration information of the first node of the first network node may change, so as to ensure accuracy of synchronization of node configuration information in the network configuration information of each network node, when the configuration information of the first node of the first network node changes, a configuration information change request may be sent to the central network node, where the request may include changed node configuration information, or node configuration information that needs to be changed, and the central network node may update the central network configuration information after receiving the configuration information change request. In addition, the central network node may send a configuration information change request to the second network node, so that the second network node updates the second network configuration information according to the configuration information change request.
Fig. 8 shows another interaction flow chart of network information management in the present exemplary embodiment, where the network information management system includes a first network node, a central network node and a second network node, where the first network node is taken as a distributed network a, and may specifically include NF 810 of the distributed network a and service agent 820 of the distributed network a, the central network node includes central network service agent 830, and the second network node is taken as a distributed network B, and may specifically include service agent 840 of the distributed network B for illustration, and may specifically include the following steps:
Step S810, in response to detecting that the NF 810 of the distributed network a is changed, for example, capacity expansion, offline or load change, the change information of the first node configuration information of the distributed network a is synchronized to the service agent 820 of the distributed network a;
Step S820, the service agent 820 of the distributed network A updates the network configuration information list of the distributed network A according to the change information of the first node configuration information;
Step S830, the service agent 820 of the distributed network A sends a configuration information change request to the central network service agent 830, wherein the configuration information change request comprises change information of the configuration information of the first node;
Step S840, the central network service agent 830 updates the first node configuration information of the distributed node a in the network configuration information list of the central network;
Step S850, the central network service agent 830 replies the service agent 820 of the distributed network a with a response message of successful update;
step S860, transmitting the change information of the first node configuration information of the distributed network a to other network nodes, such as the service agent 840 of the distributed network node B, through the central network service agent 830;
Step S870, the service agent 840 of the distributed network B updates the stored first node configuration information according to the change information of the first node configuration information;
in step S880, the service agent 840 of the distributed network B replies with a notification response to the central network service agent 830.
In an exemplary embodiment, the first network node synchronously adds the central node configuration information and/or the second node configuration information according to the registration request response information, including:
The first network node adds the central node configuration information and/or the second node configuration information to the first network configuration information of the first network node according to the registration request response information;
the network information management method may further include:
the target service network is used for providing corresponding service for the first network node according to the service processing request;
the first network configuration information at least comprises center node configuration information of the center network node and second node configuration information of the second network node.
For convenience in management and application, the first network node may also correspondingly set first network configuration information, for example, a first network configuration information list, so as to effectively manage other node configuration information added synchronously and node configuration information of the first network node, for example, store the received central node configuration information and the second node configuration information into the first network configuration information.
In practical applications, a service processing request may be initiated after the first network node is online to request a network service, where the service processing request may include relevant information for requesting service processing, such as a service discovery parameter, etc.
The present exemplary embodiment may search the node configuration information in the first network configuration information configured by the first network node for performing node configuration information management to determine a target service network for providing network services for the first network node, where the target service network may be a central network node, a second network node, or the like, and the disclosure is not limited in detail.
Specifically, the first network node may send a service processing request to its own service proxy, and when a suitable network node cannot be found according to the service processing request, the first network node may search for node configuration information in the first network configuration information, where the searching may be performed according to a preset priority, and after determining the target service network, the service processing request may be sent to the target service network, so as to implement a responsive network service by analyzing the service processing request by the target service network.
In this exemplary embodiment, the target service network may be a second network node or a central network node, and the second network node is hereinafter illustrated by way of example, fig. 9 shows an interaction flow chart of still another network information management in this exemplary embodiment, where the network information management system includes a first network node and a second network node, where the first network node is a distributed network a, and may specifically include a consumer NF 910 of the distributed network a and a service agent 920 of the distributed network a, and the second network node is a distributed network B, and may specifically include a service agent 930 of the distributed network B and a producer NF 940 of the distributed network B, and may specifically include the following steps:
Step S902, the distributed network A triggers the service requirement according to the interactive behavior of the accessed user equipment or other NF requests;
step S904, the consumer NF 910 of the distributed network a directly initiates a service processing request to the service proxy 920 of the distributed network a, where the service processing request may include service discovery parameters such as a user identifier, an authentication type, DNN (Data Network Name, a data network name), etc.;
Step S906, when the service agent 920 of the distributed network A can not find a suitable network node to provide service according to the discovery parameter, but can find the node configuration information of the network node capable of providing service in the network configuration information list of the distributed network A, the cooperative network, such as the distributed network B, can be determined according to the priority of each network node, wherein the cooperative network is the target service network, and the priority of each network node can be determined according to the information of capacity, load, position and the like;
Step S908, the service agent 920 of the distributed network a performs specified processing on the service processing request that needs cross-network collaboration, for example, replaces the destination address of the callback URI of the consumer NF 910 of the distributed network a with the service agent address of the present network to implement topology hiding, and adds access tokens of the requester network and the network element, etc.;
step S910, the service agent 920 of the distributed network a forwards the service processing request to the service agent 930 of the distributed network B;
step S912, the service agent 930 of the distributed network B parses the service processing request, extracts the access token and other discovery parameters;
step S914, the service agent 930 of the distributed network B verifies the validity of the requester distributed network a and the consumer NF 910 of the distributed network a according to the access token;
Step S916, after determining that the verification is passed, the service agent 930 of the distributed network B determines a proper producer NF of the distributed network B according to the discovery parameters;
Step S918, the service agent 930 of the distributed network B forwards the service processing request to the selected producer NF of the distributed network B;
If it is detected that the service processing request includes a callback URI (Uniform Resource Identifier ), then the consumer NF 910 instance ID (Identity document, unique identification) of the distributed network A needs to be recorded, which instance ID can be carried in the service processing request or discovery parameters for correct routing to the consumer when triggering callback operations;
Step S922, the service agent 930 of the distributed network B replaces the destination address related to the URI of the service producer in the response with the service agent address to implement topology hiding;
Step S924, the service proxy 930 of the distributed network B forwards the response to the service proxy 920 of the distributed network a;
in step S926, the service proxy 920 of the distributed network a finally forwards the service response to the consumer NF 910 of the distributed network a.
It should be noted that, when the service agent processes the request/response of the internal NF, the destination address of the callback URI is replaced with the address of the service agent, so if the subsequent NF in cross-network collaboration has a continuous service requirement, for example, such as secondary authentication or deregistration, the service agent initiates a request to the local service agent with the destination address of the callback URI and the instance ID of the callback NF as discovery parameters. The local service agent can redirect the request to the service agent of the network previously participating in the cooperation directly through the destination address of the callback URI, and the service agent forwards the request to the NF previously participating in the cooperation through the instance ID of the callback NF, so that the callback request is forwarded in a correct route between the two cross-network NFs previously participating in the cooperation.
Based on the above, on the one hand, the present exemplary embodiment designs a network-level configuration information service synchronization mechanism in combination with the future distributed networking scenario, and the service agents of each distributed network may obtain the overall service configuration information of the networks participating in networking through registration, update and notification, so that the cross-network collaboration is not limited to the collaboration of the mobile/session management network element and the user data network element, but can extend to the collaboration of multiple services such as 6G communication, intelligence, calculation, and the like, and improves the flexibility of the cross-network collaboration. The central network can timely detect the abnormality of the working state of the distributed network service agent through a heartbeat mechanism, timely notify the whole network of the downlink state of the distributed network, and improve the networking reliability.
In addition, the present exemplary embodiment configures a notification mechanism and a heartbeat mechanism between the central network service agent and the distributed network service agent, so that the distributed network can synchronize the whole network service configuration change rapidly through the notification of the central network, and make network selection decisions in high efficiency later, and the central network can monitor the running state of the distributed network according to the heartbeat, thereby improving the reliability of the networking.
On the other hand, in the present exemplary embodiment, the cross-network collaboration does not adopt a mechanism of acquiring the NF service discovery result of the target network and then requesting the service, but directly initiates the NF service request to the target network service proxy by the service proxy of the present network according to the synchronized network configuration information, and the target network service proxy selects an appropriate service producer to answer according to the discovery parameter under the condition that token verification passes, thereby improving efficiency, and the service consumer cannot acquire the detailed configuration information of the collaborative network service producer. Compared with the topology hiding scheme in the D mode of the SCP (Service Communications Proxy, service communication proxy), the embodiment can support cross-network NF collaboration, hide parts of callback URI and the like which possibly indirectly expose the network topology information, and improve privacy. Compared with the topology hiding scheme of SEPP (Security Edge Protection Proxies, secure edge protection proxy), the present exemplary embodiment may also be applied to NF collaboration between a distributed private network and a central public network of the same PLMN, and hide NF address information in a manner of not using FQDN for callback URI address, but hide NF address information by replacing it with the present network service proxy address, thus supporting both FQDN format and IP format address hiding.
The exemplary embodiments of the present disclosure also provide a network information management apparatus. Referring to fig. 10, the apparatus 1000 may include a first information management module 1010 configured to add first node configuration information to central network configuration information in response to a central network node receiving a network registration request sent by the first network node, the network registration request including at least first node configuration information of the first network node, the central network configuration information including at least central node configuration information of the central network node and/or second node configuration information of the second network node, a second information management module 1020 configured to send registration request response information to the first network node through the central network node, so that the first network node synchronously adds the central node configuration information and/or the second node configuration information according to the registration request response information, the registration request response information including the central network configuration information, and a third information management module 1030 configured to send notification information including the first node configuration information to the second network node through the central network node in response to the first network node satisfying a preset condition, so that the second network node adds the first node configuration information to the second network configuration information according to the notification information.
In an exemplary embodiment, the third information management module further includes a monitoring module, configured to monitor the first network node by the central network node, and send notification information including configuration information of the first node to the second network node in response to monitoring that the first network node meets a preset condition.
In an exemplary embodiment, the monitoring module comprises a heartbeat communication connection establishing unit, configured to establish a heartbeat communication connection between the central network node and the first network node according to a preset heartbeat cycle interval, so that the central network node monitors the first network node through the heartbeat communication connection.
In an exemplary embodiment, the network information management device further comprises a fourth information management module, configured to delete the first node configuration information of the first network node from the central network configuration information in response to detecting that the heartbeat communication connection is abnormal, and send an abnormality notification to the second network node, so that the second network node deletes the first node configuration information of the first network node from the second network configuration information.
In an exemplary embodiment, the network information management device further includes a fifth information management module, configured to, in response to detecting that an abnormal condition occurs in the heartbeat communication connection, cause the first network node to delete the added configuration information of the central node and/or the configuration information of the second node, and send a network registration request to the central network node again.
In an exemplary embodiment, the network information management device further includes a configuration information change management module, configured to, in response to receiving the configuration information change request sent by the first network node, update the central network configuration information of the central network node according to the configuration information change request, and send the configuration information change request to the second network node, so that the second network node updates the second network configuration information of the second network node according to the configuration information change request.
In an exemplary embodiment, the second information management module comprises a first information management unit, a service processing module and a target service network, wherein the first information management unit is used for adding central node configuration information and/or second node configuration information into first network configuration information of the first network node according to registration request response information, the service processing module is used for responding to a service processing request sent by the first network node and determining the target service network according to the first network configuration information, the target service network is used for providing corresponding service for the first network node according to the service processing request, and the first network configuration information at least comprises central node configuration information of the central network node and second node configuration information of the second network node.
The specific details of each module/unit in the above apparatus are already described in the embodiments of the method section, and the details not disclosed can be found in the embodiments of the method section, so that they will not be described here again.
The exemplary embodiments of the present disclosure also provide an electronic device capable of implementing the above method.
Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, aspects of the present disclosure may be embodied in the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects that may be referred to herein collectively as a "circuit," module, "or" system.
An electronic device 1100 according to such an exemplary embodiment of the present disclosure is described below with reference to fig. 11. The electronic device 1100 shown in fig. 11 is merely an example and should not be construed as limiting the functionality and scope of use of the disclosed embodiments.
As shown in fig. 11, the electronic device 1100 is embodied in the form of a general purpose computing device. The components of the electronic device 1100 may include, but are not limited to, the at least one processing unit 1110 described above, the at least one storage unit 1120 described above, a bus 1130 connecting the various system components (including the storage unit 1120 and the processing unit 1110), and a display unit 1140.
Wherein the storage unit stores program code that is executable by the processing unit 1110 such that the processing unit 1110 performs steps according to various exemplary embodiments of the present disclosure described in the above-described "exemplary methods" section of the present specification. For example, the processing unit 1110 may perform the steps shown in fig. 4, 5, 7, 8, or 9, etc.
The storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as a Random Access Memory (RAM) 1121 and/or a cache memory 1122, and may further include a Read Only Memory (ROM) 1123.
The storage unit 1120 may also include a program/utility 1124 having a set (at least one) of program modules 1125, such program modules 1125 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The bus 1130 may be a local bus representing one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a bus using any of a variety of bus architectures.
The electronic device 1100 may also communicate with one or more external devices 1200 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 1100, and/or any devices (e.g., routers, modems, etc.) that enable the electronic device 1100 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 1150. Also, electronic device 1100 can communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 1160. As shown, network adapter 1160 communicates with other modules of electronic device 1100 via bus 1130. It should be appreciated that although not shown, other hardware and/or software modules may be utilized in connection with the electronic device 1100, including, but not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solutions according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the exemplary embodiments of the present disclosure.
Exemplary embodiments of the present disclosure also provide a computer readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification. In some possible implementations, various aspects of the disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the disclosure as described in the "exemplary methods" section of this specification, when the program product is run on the terminal device.
Exemplary embodiments of the present disclosure also provide a program product for implementing the above method, which may employ a portable compact disc read-only memory (CD-ROM) and comprise program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of a readable storage medium include an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
Furthermore, the above-described figures are only schematic illustrations of processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with exemplary embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202411238272.5A CN119172775A (en) | 2024-09-04 | 2024-09-04 | Network information management method, network information management device, electronic equipment and medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202411238272.5A CN119172775A (en) | 2024-09-04 | 2024-09-04 | Network information management method, network information management device, electronic equipment and medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN119172775A true CN119172775A (en) | 2024-12-20 |
Family
ID=93879605
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202411238272.5A Pending CN119172775A (en) | 2024-09-04 | 2024-09-04 | Network information management method, network information management device, electronic equipment and medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN119172775A (en) |
-
2024
- 2024-09-04 CN CN202411238272.5A patent/CN119172775A/en active Pending
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11418602B2 (en) | Systems and methods for service layer session migration and sharing | |
US7978631B1 (en) | Method and apparatus for encoding and mapping of virtual addresses for clusters | |
US9071656B2 (en) | Router and method for routing service | |
JP5143125B2 (en) | Authentication method, system and apparatus for inter-domain information communication | |
CN112711635B (en) | Method for cross-regional data consistency of distributed Internet of things equipment and service cluster | |
US20130232217A1 (en) | Signalling Gateway, Method, Computer Program And Computer Program Product For Communication Between HTTP And SIP | |
JP2008527907A (en) | Method and apparatus for handling emergency calls | |
ZA200700120B (en) | Method, system and computer program to enable semantic mediation for sip events through support of dynamicall binding to and changing of application semantics of si events | |
US20060004924A1 (en) | Method and system providing support for location and service category service discovery in a SIP environment using a SIP event package, forking and AOR registration | |
WO2021168715A1 (en) | Method, apparatus and system for discovering application | |
US20240048986A1 (en) | Communication method and apparatus | |
US12021922B2 (en) | Methods of operating service control nodes | |
WO2021168714A1 (en) | Application discovery method, apparatus, and system | |
US20130159374A1 (en) | Method And Apparatus For Messaging In The Cloud | |
CN110557336A (en) | Addressing routing method and system | |
CN119172775A (en) | Network information management method, network information management device, electronic equipment and medium | |
CN115190168B (en) | Edge server management system and server cluster | |
CN102821118B (en) | The method and system of service backup in a kind of network for possessing heterogeneous nodes | |
EP3031196B1 (en) | Mirror presence between websites | |
CN102984182B (en) | A kind of P2P network mobility management methods and system | |
US20210211417A1 (en) | Methods and systems to automatically interconnect devices and applications over multi-cloud providers and on-premises networks | |
CN112800289B (en) | Metadata query method and system | |
CN116647707B (en) | Multicast scheduling method, device and system | |
CN115348595B (en) | Mobile network backup method, device, electronic device and computer storage medium | |
CN120568309A (en) | Information sending and service calling method and device, electronic equipment and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |