Method for managing network digital twin, computer readable storage medium, electronic device and computer program product

Abstract

Embodiments of the present application provide a network digital twin management method, a computer readable storage medium, an electronic device and a computer program product, wherein the method comprises: querying NDT support information of a second network element; and sending an NDT management request to the second network element, wherein the NDT management request is used to request the second network element to manage the NDT. The method can at least solve the problem of how to effectively manage and control the full life cycle of the network digital twin (NDT) to meet different capabilities and needs in a complex network management system in the related art, realizes comprehensive life cycle management of the NDT, and improves the flexibility and configurability of the NDT system.

Description

Technical Field

[0001] This application relates to the field of text retrieval technology, and more specifically, to a method for managing a network digital twin, a computer-readable storage medium, an electronic device, and a computer program product. Background Technology

[0002] Digital twins are an increasingly popular technology related to system automation. A digital twin is a virtual copy of a real-world system—a "physical" system—on which configuration and other related operations can be performed. Network Digital Twin (NDT) technology can build a real-time mirror of a physical network, reflecting its configuration, topology, status, and other information. Full lifecycle management of digital twins, from creation and configuration to operation, is essential for supporting standardized digital twin applications. Based on the different capabilities supported at different stages, the lifecycle of a digital twin can be divided into three phases: creation, configuration, and operation. Each phase supports different capabilities. However, in complex network management systems, a solution for effectively managing and controlling the entire lifecycle of a Network Digital Twin (NDT) to meet diverse capabilities and requirements remains to be found. Summary of the Invention

[0003] This application provides a method for managing network digital twins, a computer-readable storage medium, an electronic device, and a computer program product, to at least address the problem in related technologies of how to effectively manage and control the entire lifecycle of a network digital twin (NDT) in a complex network management system to meet different capabilities and needs.

[0004] According to one embodiment of this application, a method for managing a network digital twin is provided, applied to a first network element, comprising: querying NDT support information of a second network element; and sending an NDT management request to the second network element, wherein the NDT management request is used to request the second network element to manage NDT.

[0005] According to another embodiment of this application, a method for managing a network digital twin is also provided, applied to a second network element, comprising: providing NDT support information to a first network element; and managing NDT based on an NDT management request from the first network element.

[0006] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0007] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0008] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0009] Through the above embodiments of this application, the NDT support information of the second network element is queried; an NDT management request is sent to the second network element, wherein the NDT management request is used to request the second network element to manage the NDT. This can solve the problem in related technologies of how to effectively manage and control the entire life cycle of the network digital twin (NDT) in a complex network management system to meet different capabilities and needs, realize comprehensive life cycle management of the NDT, and improve the flexibility and configurability of the NDT system. Attached Figure Description

[0010] Figure 1 This is an architecture diagram of a digital twin network according to an embodiment of this application;

[0011] Figure 2 This is a flowchart of a network digital twin management method according to an embodiment of this application. Figure 1 ;

[0012] Figure 3 This is a flowchart of a network digital twin management method according to an embodiment of this application. Figure 2 ;

[0013] Figure 4 This is a schematic diagram of the lifecycle management of a Network Digital Twin (NDT) according to an embodiment of this application;

[0014] Figure 5 This is a flowchart illustrating the NDT MnS capability exposure according to an embodiment of this application;

[0015] Figure 6 This is a flowchart illustrating the generation of an NDT instance based on an existing NDT, according to an embodiment of this application.

[0016] Figure 7 This is a flowchart of updating an existing NDT instance according to an embodiment of this application. Detailed Implementation

[0017] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0018] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0019] A digital twin network is a network system that creates a virtual twin of a physical network entity in a digital way, and can interact and map with the physical network entity in real time. Figure 1 This is an architecture diagram of a digital twin network according to an embodiment of this application, such as... Figure 1 As shown, the architecture is a "three-layer, three-domain, dual-closed-loop" structure. The three layers refer to the physical network layer, the twin network layer, and the network application layer that constitute the digital twin network system. The three domains refer to the data domain, model domain, and management domain of the twin network layer, which correspond to the three subsystems of data sharing warehouse, service mapping model, and network twin management, respectively. The "dual-closed-loop" refers to the "inner closed-loop" simulation and optimization based on the service mapping model within the twin network layer, and the "outer closed-loop" control, feedback, and optimization of network applications based on the three-layer architecture.

[0020] Building a DTN system requires the use of the following three types of interfaces:

[0021] (1) Twin Southbound Interface: This includes the data acquisition interface and the control delivery interface between the twin network layer and the physical network layer. The data acquisition interface is responsible for acquiring data from the twin network layer's data sharing repository, while the control delivery interface is responsible for sending control commands, verified by the service mapping model simulation, to the network elements of the physical network layer.

[0022] (2) Twin Northbound Interface: This includes the intent translation interface and capability invocation interface between the network application layer and the twin network layer. The network application layer can use the intent translation interface to pass application layer intents to the twin network layer, providing abstract requirement inputs for the functional model.

[0023] (3) Twin internal interfaces: including a set of interfaces such as the interface between the internal data warehouse and functional model of the twin network layer, the interface between the functional model and the digital twin management, and the interface between functional models.

[0024] This embodiment provides a management method for a network digital twin running on the above-described network architecture. Figure 2 This is a flowchart of a network digital twin management method according to an embodiment of this application. Figure 1 ,like Figure 2 As shown, this process, applied to the first network element, includes the following steps:

[0025] Step S202: Query the NDT support information of the second network element;

[0026] Step S204: Send an NDT management request to the second network element, wherein the NDT management request is used to request the second network element to manage the NDT.

[0027] Through the above steps S202 to S204, the problem of how to effectively manage and control the entire lifecycle of a network digital twin (NDT) in a complex network management system to meet different capabilities and needs can be solved. This achieves comprehensive lifecycle management of the NDT and improves the flexibility and configurability of the NDT system.

[0028] In this embodiment, the first network element is an NDT MnS Consumer, and the second network element is an NDT MnS Producer. This enables network operators to quickly understand the NDT capabilities of each network element, thereby managing and scheduling network resources more effectively and improving network operation and maintenance efficiency. Application scenarios include network fault prediction, resource optimization and configuration, and network performance monitoring. Through digital twin technology, real-time simulation and prediction of network status can be achieved, providing a basis for network decision-making.

[0029] In this embodiment, the NDT management request may specifically include at least one of the following: an NDT operation request, an NDT configuration request, and an NDT run request. Correspondingly, step S204 above may include at least one of the following: sending an NDT operation request to the second network element, wherein the NDT operation request is used to request the second network element to perform an operation on the NDT instance, and the operation may specifically include at least one of the following: NDT creation, NDT deletion, NDT orchestration, NDT update, and NDT query. For creating an NDT instance, there is no NDT instance before creation; sending an NDT configuration request to the second network element, wherein the NDT configuration request is used to request the second network element to configure the NDT instance; and sending an NDT run request to the second network element, wherein the NDT run request is used to request the second network element to provide NDT run results. The NDT run results include simulation results, prediction results, analysis results, etc., that is, the NDT run request includes requesting the second network element to perform NDT simulation, NDT prediction, or NDT analysis. This refined request method makes network management more precise, enabling operations to be performed according to specific needs, and improving the flexibility and response speed of network management. Application scenarios include network simulation, network planning, and network optimization. Through precise requests, specific parts of the network can be analyzed and optimized in depth.

[0030] In one embodiment of this application, after sending an NDT operation request to the second network element, the method further includes: receiving an NDT operation response sent by the second network element after performing at least one of the following operations on the NDT instance: NDT creation, NDT deletion, NDT orchestration, NDT update, or NDT query. This bidirectional communication mechanism ensures the transparency and controllability of network operations, allowing network administrators to monitor operation results in real time and adjust management strategies accordingly. Application scenarios include dynamic adjustment of network resources and fault recovery. Real-time feedback enables rapid response to network changes, improving network stability and reliability.

[0031] In this embodiment of the application, the NDT operation request may include at least one of the following: NDT type, NDT operation type, NDT operation information; and / or the NDT operation response may include at least one of the following: NDT status, NDT description file.

[0032] The NDT type varies depending on the differentiation method. Based on NDT data synchronization, it can include at least one of the following: real-time NDT, non-real-time NDT, and semi-real-time NDT. Based on NDT assembly method, it can include at least one of the following: single NDT, nested NDT, and combined NDT. Based on NDT capabilities, it can include at least one of the following: NDT and NDT components. NDT operation types include at least one of the following: NDT creation, NDT deletion, NDT orchestration, NDT update, and NDT query. NDT operation information depends on the NDT operation type and includes at least one of the following: NDT component list, NDT capability information, and NDT component capability information. And / or NDT status includes at least one of the following: in progress or completed. And / or NDT description file includes at least one of the following: NDT identifier, NDT capability information, NDT component information, and NDT creation context. When the NDT operation type is NDT update, the NDT operation information is the NDT update information, including at least one of the following: the updated NDT identifier, the updated NDT component identifier, and the NDT component update history. When an NDT is a nested NDT, the NDT component is the NDT itself. In other words, an NDT component can be part of an NDT or a standalone NDT.

[0033] In one embodiment of this application, after sending an NDT configuration request to the second network element, the method further includes: receiving an NDT configuration response sent by the second network element, wherein the NDT configuration response is sent after the second network element performs at least one of the following actions according to the NDT configuration request: NDT configuration, NDT data acquisition, NDT data synchronization, and updating the NDT status. If the NDT operation request requests operation on a non-real-time NDT instance, the second network element performs NDT configuration according to the NDT configuration request; if the NDT operation request requests operation on a real-time NDT instance, the second network element performs NDT data acquisition and / or NDT data synchronization according to the NDT configuration request. This configuration request and response mechanism makes the configuration process of the network digital twin instance more transparent and controllable, allowing network administrators to monitor the configuration progress and status in real time and adjust configuration strategies accordingly. Application scenarios include network resource configuration and optimization. Through real-time configuration responses, dynamic adjustments to network resources can be achieved, improving the utilization efficiency of network resources.

[0034] In this embodiment of the application, the NDT configuration request includes at least one of the following: NDT identifier, NDT configuration type, NDT configuration information, NDT data acquisition information, NDT data synchronization information; and / or the NDT configuration response includes at least one of the following: NDT status, NDT configuration history.

[0035] NDT configuration types include at least one of the following: configuration, data collection, data synchronization; and / or NDT configuration information includes at least one of the following: NDT configuration scope, NDT configuration parameters, NDT performance parameters; and / or NDT data acquisition information includes at least one of the following: NDT data acquisition object, NDT data collection content, NDT data collection conditions; and / or NDT data synchronization information includes at least one of the following: NDT data synchronization object, NDT data synchronization content, NDT data synchronization filtering conditions, NDT data synchronization conditions; and / or NDT status includes at least one of the following: configuring, configuration completed, data acquisition in progress, data synchronization pending, data synchronization in progress, simulation pending.

[0036] In one embodiment of this application, after sending an NDT operation request to the second network element, the method further includes: receiving an NDT operation response sent by the second network element, wherein the NDT operation response is sent by the second network element after performing one of the following based on the NDT operation request: NDT activation, NDT deactivation, or NDT operation, and updating the NDT status. This operation request and response mechanism makes the operation process of the network digital twin instance more transparent and controllable, allowing network administrators to monitor the operation status in real time and adjust operation strategies accordingly. Application scenarios include network simulation testing, network resource optimization, and network fault prediction. Through real-time operation responses, real-time simulation and prediction of network status can be achieved, improving the efficiency and accuracy of network management.

[0037] In this embodiment, the NDT operation request includes at least one of the following: NDT operation type, NDT operation information; and / or the NDT operation response includes: NDT status. The NDT operation type includes at least one of the following: activation, deactivation, running, paused, terminated; the NDT operation information includes at least one of the following: NDT identifier, NDT component identifier, NDT operation condition. These parameters can be used in combination. For example, if some NDT components need to be activated when PM is greater than a threshold, the NDT operation type is activation, the NDT operation information includes the identifier of the activated NDT component, and the NDT operation condition is that PM is greater than a threshold; the NDT status can include at least one of the following: active state, deactivation state, running, paused, completed, terminated.

[0038] In this embodiment, step S202 may specifically include: sending an NDT query request to a first network element; and receiving an NDT query response from a second network element, wherein the NDT query response carries the NDT support information, which is obtained by the second network element based on the NDT query request. This query mechanism makes the management of network digital twin instances more transparent and controllable. Network administrators can understand the NDT capabilities of each network element in real time and adjust management strategies accordingly. Application scenarios include dynamic configuration of network resources, real-time monitoring of network performance, and prediction and recovery of network faults. Through real-time NDT support information query, real-time adjustment and optimization of network status can be achieved, improving the quality of network services.

[0039] In this embodiment of the application, NDT support information includes at least one of the following: existing NDT and NDT capability information; existing NDT components and NDT component capability information; supported NDT capability information; supported NDT component capability information.

[0040] NDT capability information, supported NDT capability information includes one of the following: NDT type, general capability information, scenario-based capability information; and / or NDT component capability information, supported NDT component capability information includes one of the following: NDT component type, general capability information, scenario-based capability information.

[0041] Through the embodiments of this application, the network digital twin management method achieves efficient management and operation of network digital twin (NDT) instances, improving the utilization efficiency of network resources and the quality of network services. Specifically, by querying the NDT support information of the second network element, the first network element can understand the available NDT resources and capabilities in the network, thereby sending NDT management requests more accurately. Furthermore, through NDT operation requests, configuration requests, and run requests, the first network element can perform operations such as creation, deletion, orchestration, update, query, configuration, data collection, data synchronization, activation, deactivation, and operation on NDT instances. This not only enhances the flexibility and scalability of the network but also enables the network to quickly adjust and optimize according to actual needs. Simultaneously, through feedback of NDT status and configuration history information, the first network element can monitor the operation of NDT instances in real time, adjust management strategies promptly, and ensure the stability and reliability of network services. The application of the embodiments of this application will significantly improve the intelligence level of network management, providing strong support for network operation and maintenance, fault prediction, resource optimization, and other scenarios. In practical applications, this method helps network operators respond quickly to various needs in complex and ever-changing network environments, achieving optimal allocation of network resources and improving network operating efficiency and user experience. For example, during the network planning phase, the creation and configuration of NDTs can simulate different network architectures and traffic models, predict network performance, and thus make more reasonable planning decisions. During the network operation and maintenance phase, the operation and monitoring of NDTs can analyze network status in real time, predict potential faults, take proactive measures, reduce network outages and fault recovery time, and improve network stability and reliability. Furthermore, this method also supports dynamic network optimization. Through real-time data collection and analysis, the allocation of network resources can be dynamically adjusted, improving network resource utilization efficiency and reducing network operating costs. In conclusion, the application of the implementation method described in this application will bring revolutionary changes to network management, making it more intelligent and automated, and better adaptable to the future development needs of networks.

[0042] This embodiment also provides a method for managing network digital twins running on the aforementioned mobile terminal or network architecture. Figure 3 This is a flowchart of a network digital twin management method according to an embodiment of this application. Figure 2 ,like Figure 3 As shown, this process, applied to the second network element, includes the following steps:

[0043] Step S302: Provide NDT support information to the first network element;

[0044] In this embodiment of the application, step S302 may specifically include: receiving an NDT query request sent by a first network element; obtaining NDT support information based on the NDT query request; and sending an NDT query response to the first network element, wherein the NDT query response carries NDT support information.

[0045] Step S304: Manage NDT based on NDT management request of the first network element.

[0046] Through the above steps S302 to S304, the problem of how to effectively manage and control the entire lifecycle of a network digital twin (NDT) in a complex network management system to meet different capabilities and needs can be solved. This achieves comprehensive lifecycle management of the NDT and improves the flexibility and configurability of the NDT system.

[0047] The embodiments of this application can effectively improve the efficiency and accuracy of network management. Especially in large-scale network environments, digital twin technology can be used to achieve real-time monitoring and prediction of network status, providing an important basis for network optimization and troubleshooting.

[0048] In this embodiment of the application, step S304 may include:

[0049] S3041, Based on the NDT operation request of the first network element, execute the operation of the NDT instance;

[0050] S3042, NDT configuration request based on the first network element to configure the NDT instance;

[0051] S3043 provides NDT operation results based on the NDT operation request of the first network element.

[0052] The above steps S3041-S3043, through a hierarchical management mechanism, can meet the network management needs at different levels, such as creation, deletion, orchestration, updating and querying at the operation level, parameter adjustment and data synchronization at the configuration level, and activation, deactivation and simulation at the runtime level, making network management more refined and intelligent.

[0053] Furthermore, S3041 may include: receiving an NDT operation request sent by the first network element; performing at least one of the following operations based on the NDT operation request: NDT creation, NDT deletion, NDT orchestration, NDT update, NDT query; and sending an NDT operation response to the first network element. This operation mechanism is particularly important in 5G networks and IoT environments, enabling rapid response to network changes and dynamic allocation and optimization of network resources.

[0054] In this embodiment of the application, the NDT operation request includes at least one of the following: NDT type, NDT operation type, NDT operation information, NDT update information; and / or the NDT operation response includes at least one of the following: NDT status, NDT description file.

[0055] NDT types include at least one of the following: real-time NDT, non-real-time NDT, and semi-real-time NDT; and / or NDT operation types include at least one of the following: NDT creation, NDT deletion, NDT orchestration, NDT update, and NDT query; and / or NDT operation information includes at least one of the following: NDT component list, NDT capability information, and NDT component capability information; and / or NDT status includes at least one of the following: in progress or completed; and / or NDT description files include at least one of the following: NDT identifier, NDT capability information, NDT component information, and NDT creation context; and / or NDT update information includes at least one of the following: updated NDT identifier, updated NDT component identifier, and NDT component update history.

[0056] Furthermore, step S3042 may include: receiving an NDT configuration request sent by the first network element; performing at least one of the following based on the NDT configuration request: NDT configuration, NDT data acquisition, NDT data synchronization, and updating the NDT status; and sending an NDT configuration response to the first network element. This configuration mechanism, in cloud computing and edge computing scenarios, enables efficient utilization of network resources and real-time data synchronization, ensuring consistency between the digital twin network and the physical network.

[0057] In this embodiment of the application, the NDT configuration request includes at least one of the following: NDT identifier, NDT configuration type, NDT configuration information, NDT data acquisition information, NDT data synchronization information; and / or the NDT configuration response includes at least one of the following: NDT status, NDT configuration history.

[0058] NDT configuration types include at least one of the following: configuration, data collection, data synchronization; and / or NDT configuration information includes at least one of the following: NDT configuration scope, NDT configuration parameters, NDT performance parameters; and / or NDT data acquisition information includes at least one of the following: NDT data acquisition object, NDT data collection content, NDT data collection conditions; and / or NDT data synchronization information includes at least one of the following: NDT data synchronization object, NDT data synchronization content, NDT data synchronization filtering conditions, NDT data synchronization conditions; and / or NDT status includes at least one of the following: configuring, configuration completed, data acquisition in progress, data synchronization pending, data synchronization in progress, simulation pending.

[0059] Furthermore, step S3043 may include: receiving an NDT operation request sent by the first network element; performing one of the following based on the NDT operation request: NDT activation, NDT deactivation, NDT operation, and updating the NDT status; and sending an NDT operation response to the first network element. This operation mechanism can provide high-precision network status prediction and simulation in demanding scenarios such as autonomous driving and telemedicine, ensuring the safe operation of these applications.

[0060] In this embodiment of the application, the NDT run request includes at least one of the following: NDT run operation type, NDT run operation information; and / or the NDT run response includes: NDT status.

[0061] NDT operation types include at least one of the following: Activate, Deactivate, Run, Pause, Terminate; NDT operation information includes at least one of the following: NDT identifier, NDT component identifier, NDT operation conditions; NDT status includes at least one of the following: Activated, Deactivated, Running, Paused, Completed, Terminated.

[0062] In this embodiment, the NDT support information includes at least one of the following: existing NDT and NDT capability information; existing NDT components and NDT component capability information; supported NDT capability information; and supported NDT component capability information. Providing this support information enables network administrators to fully understand the current status and potential of network digital twins, providing data support for future network planning and development, especially in network architecture design and the introduction of new technologies, enabling more scientific and rational decision-making.

[0063] This application not only enables real-time monitoring and prediction of network status but also allows for dynamic adjustment and optimization based on network needs, ensuring efficient utilization of network resources and high-quality network services. Furthermore, the method supports efficient interaction between network devices, achieving refined management and intelligent operation of network digital twins through explicit operation requests, configuration requests, and runtime requests, along with detailed response information. In specific application scenarios, such as 5G networks, the Internet of Things, cloud computing, edge computing, autonomous driving, and telemedicine, this method provides high-precision network status prediction and simulation, offering strong support for the secure operation and performance optimization of these applications. It significantly enhances network adaptability and user experience, while also providing network operators with more intuitive and controllable network management tools, greatly improving the intelligence level and operational efficiency of network operations. In the future, with the continuous development of network technology and the expansion of application scenarios, the application of network digital twin management methods will become more widespread, becoming an important means of network management and optimization.

[0064] Figure 4This is a schematic diagram of the lifecycle management of a network digital twin (NDT) according to an embodiment of this application, as shown below. Figure 4 As shown, the lifecycle management of a network digital twin (NDT) is divided into three phases: creation, configuration, and operation. NDTs at different lifecycle phases need to support different functionalities.

[0065] The capabilities of NDT at different lifecycle stages, derived from the Consumer's requirements for different stages of NDT, are contained in OperationInfo.

[0066] Creation phase: Supports the creation / deletion, orchestration, and updating of NDT instances.

[0067] Configuration phase: Supports configuring NDT instances, including collecting data from the physical network according to the Consumer's needs and synchronizing data with the NDT.

[0068] Operation phase: Supports activating, deactivating, running, and terminating configured NDT instances.

[0069] NDT Operations at Different Stages of NDT:

[0070] The lifecycle management operations during the creation phase include: NDT creation, NDT deletion, NDT orchestration, NDT update, and NDT query.

[0071] The lifecycle management operations during the configuration phase include: data acquisition, data synchronization, and data control.

[0072] The lifecycle management operations during the runtime phase include: NDT activation, NDT deactivation, and NDT business requests. NDT business requests include common business request operations such as NDT running, NDT pausing, and NDT termination, which will not be elaborated here.

[0073] NDT State at Different NDT Stages:

[0074] During the creation phase, the NDT status includes: in progress and / or completed; here, "completed" can be understood as "pending configuration", that is, the NDT instance has been created or updated and can enter the configuration phase.

[0075] During the configuration phase, the NDT status includes at least one of the following: configuring, configuration completed, data acquisition in progress, data synchronization pending (i.e., data acquisition completed), data synchronization in progress, and simulation pending. Here, "simulation pending" can be understood as configuration completed, i.e., configuration completed directly, or data acquisition and data synchronization completed.

[0076] During the runtime phase, the NDT state includes at least one of the following: active, deactivated, running, paused, completed, or terminated.

[0077] The NDT configuration state (NDT_Configuring_State) includes "Data Collecting", "Ready for Synchronization (which can be understood as data collection completed)", "Data Synchronizing", and "Ready for Simulation (which can be understood as synchronization completed)".

[0078] Figure 5 This is a flowchart illustrating the NDT MnS capability exposure according to an embodiment of this application, such as... Figure 5 As shown, it includes:

[0079] S501, the NDT MnS consumer sends an NDT query request to the NDT MnS producer to query the NDT support information of the NDT MnS producer.

[0080] S502, after receiving an NDT Query request, the NDT MnS Producer queries and retrieves NDT support information. The NDT support information must contain at least one of the following parameters:

[0081] Existing NDT and NDT capability information consists of a list of existing NDT identifiers and their capability information. Existing NDT identifiers can be DNs. NDT capability information includes one of the following parameters:

[0082] The NDT type can be an NDT type indicator to distinguish between NDT components and NDTs; or it can indicate the composition type of the NDT, such as single NDT, nested NDT, combined NDT, etc., to distinguish the NDT composition method. Among them, the components of nested NDTs are NDTs, which have complete NDT capabilities and can support NDT MnS independently, but the components of combined NDTs do not have complete NDT capabilities; or real-time NDT, non-real-time NDT, semi-real-time NDT, to distinguish whether the NDT supports real-time synchronization with physical entities.

[0083] General capability information, such as modeling, simulation, verification, and prediction;

[0084] Contextualized capability information, such as base station energy saving, signaling storm, NTN, etc.;

[0085] Existing NDT components and their capabilities are listed as a list of existing NDT component identifiers and their capability information. Existing NDT component identifiers can be DNs, and their corresponding capability information includes one of the following parameters:

[0086] NDT component types can be NDT component type identifiers to distinguish NDT; or specific NDT component types, such as NDT network element components, NDT base stations, NDT behavior components, NDT environment components, etc.; or real-time NDT components, non-real-time NDT components, and semi-real-time NDT components to distinguish whether NDT components support real-time synchronization with physical entities.

[0087] General capability information, such as modeling, simulation, verification, and prediction;

[0088] Contextualized capability information, such as base station energy saving, signaling storm, NTN, etc.;

[0089] Supported NDT capability information;

[0090] Supported NDT component capability information;

[0091] S503, the NDT MnS Producer sends an NDT query response to the NDT MnS Consumer, which contains NDT support information.

[0092] After the NDT MnS Consumer retrieves the NDT support information for the NDT MnS Producer, it can perform relevant operations on the NDT instance. Figure 6 This is a flowchart illustrating the generation of NDT instances based on existing NDT rearrangement according to embodiments of this application, such as... Figure 6 As shown, it includes:

[0093] NDT creation phase:

[0094] S601a, the NDT MnS Consumer sends an NDT orchestration request (one of the NDT operation requests mentioned above) to the NDT MnS Producer, requesting the creation of an NDT instance through orchestration. The NDT orchestration request includes one of the following parameters:

[0095] The NDT operation type (NDTOp) can specifically be "NDT_Create", "NDT_Delete", "NDT_Orchestrate", or "NDT_Update". In this embodiment, the NDT operation type is "NDT_Orchestrate".

[0096] NDT operation information (NDTOpInfo) contains the corresponding NDT operation information for different NDT operations. When the NDT operation is "NDT orchestration", the NDT operation information is the NDT orchestration information (NDTOrchestrationInfo), which includes at least one of the following parameters:

[0097] The NDT component list consists of a list of existing NDT identifiers and a list of existing NDT component identifiers. Both NDT identifiers and NDT component identifiers can be DNs. When this parameter is present, the NDT MnS Consumer request reconstructs a new NDT based on the Producer's existing NDTs or NDT components. That is, the new NDT instance will have a new DN to distinguish it from existing NDTs in the Producer.

[0098] NDT capability information;

[0099] NDT component capability information;

[0100] S601b, the NDT MnS Producer creates an NDT instance according to the NDT orchestration request. It then updates NDTstage = Creation.

[0101] S601c, the NDT MnS Producer sends an NDT orchestration response to the NDT MnS Consumer, wherein the NDT orchestration response contains at least one of the following parameters:

[0102] During the creation phase, NDTState can be in progress or completed.

[0103] An NDT profile (NDTProfile) must include at least one of the following parameters:

[0104] The NDT identifier identifies the newly created NDT instance;

[0105] NDT capability information;

[0106] NDT component list, specific parameters and definitions are shown in S601a;

[0107] The NDT creation context, in this embodiment, includes the NDT creation time, the reason for NDT creation, and NDT component change information.

[0108] NDT configuration phase:

[0109] Case 1: In S601a, during the creation phase, a request is made to generate a non-real-time NDT (i.e., NDTType is "non-real-time NDT").

[0110] S602a, the NDT MnS Consumer sends an NDT configuration request (corresponding to one of the NDT operation requests described above) to the NDT MnS Producer, requesting configuration of the NDT instance. The NDT configuration request includes one of the following parameters:

[0111] NDT identifier (NDTID);

[0112] The NDT configuration type (NDTConfigurationType) can be either Direct Configuration (Configuration), Data Collection (Data_Collection), or Data Synchronization (Data_Synchronization). In this embodiment, Step 1a has an NDTType, which is "Non-real-time NDT," and the NDT configuration type is "Direct Configuration (Configuration)."

[0113] NDT configuration information (NDTConfigInfo) includes the following parameters:

[0114] The NDT configuration scope refers to the range of objects to be configured, such as the list of base stations in the NDT, the range of parameters that need to be manually configured (configuration parameters and performance parameters), and the NDT components that need to be configured. This can be understood as the portion not within the NDT configuration scope, whose status is automatically generated by the Producer.

[0115] NDT configuration parameters refer to the configuration parameters and values ​​of each configurable object in the NDT instance, such as the switching on and off of the base station in the NDT, the frequency of the radio frequency, the UE's movement trajectory, and the energy consumption of the base station.

[0116] NDT performance parameters, the performance parameters and values ​​that NDT must meet at this time, PM / KPI.

[0117] S602b, NDT MnS Producer executes NDT configuration and updates NDTstage=Configuration.

[0118] S602c, the NDT MnS Producer sends an NDT configuration response (corresponding to one of the NDT operation responses mentioned above) to the NDT MnS Consumer. The NDT configuration response includes one of the following parameters.

[0119] During the configuration phase, the NDT state can be "Configuring" or "Configured".

[0120] The NDT configuration history records the configuration stages of NDT, such as the NDT configuration information for this configuration.

[0121] Case 2: In S601a, during the creation phase, a request is made to generate a real-time NDT or a semi-real-time NDT (i.e., NDTType is not "non-real-time NDT").

[0122] S603a: The NDT MnS Consumer sends an NDT configuration request to the NDT MnS Producer, requesting the execution of data acquisition. The NDT operation request includes one of the following parameters:

[0123] NDT identifier (NDTID);

[0124] The NDT configuration type exists in S601a, but it is not "Non-real-time NDT". The NDT configuration type is "Data Collection".

[0125] NDT data acquisition information includes the following parameters:

[0126] The NDT data collection object is the identifier of the object whose data needs to be collected, such as base stations or network elements in the physical network; or it can be identified in the form of a range, such as the area location or the type of the entity being collected.

[0127] The NDT data collection content includes the PM / KPIs (Performance Measurement / Key Performance Indicator) that need to be collected.

[0128] NDT data collection conditions include two parts: general conditions and specific conditions. General conditions include the time, frequency, and amount of data collection; specific conditions are the specific conditions that data collection must meet, such as data collection when a certain performance indicator is below a certain threshold.

[0129] S603b, the NDT MnS Producer performs data acquisition and updates the NDTState.

[0130] S603c, the NDT MnS Producer sends an NDT configuration response to the NDT MnS Consumer, and the NDT configuration response includes one of the following parameters.

[0131] During the configuration phase - data collection, NDTState can be "DataCollecting" or "Ready_for_Synchronization," which also means that data collection is complete.

[0132] The NDT configuration history records the configuration phases of the NDT, such as the information collected in this data collection.

[0133] In S603d, the NDT MnS Consumer sends an NDT configuration request to the NDT MnS Producer, requesting data synchronization. The NDT configuration request includes one of the following parameters:

[0134] NDT identifier (NDTID);

[0135] The NDT configuration operation type (NDTConfigurationOp) can be either direct configuration (Configuration), data collection (Data_Collection), or data synchronization (Data_Synchronization). In this embodiment, NDTType exists in S601a, but it is not "non-real-time NDT", and the NDT configuration type is "data synchronization (DataSynchronization)".

[0136] NDT data synchronization information (NDTDataSynchronizationInfo) includes the following parameters:

[0137] The NDT data synchronization object is identified by the object to be synchronized, such as base stations or network elements in NDT; or it can be identified in the form of a range, such as the type of object to be synchronized.

[0138] NDT data synchronization content, including PMs / KPIs that need to be synchronized.

[0139] NDT data synchronization filtering conditions: This parameter is used to filter information from NDT data collection. Examples include filtering based on the synchronization object (based on object identifier), filtering based on performance metrics (PM / KPI), or filtering based on a combination of specific conditions (e.g., the PM of base stations in a certain area is less than a specific condition).

[0140] NDT data synchronization conditions include two parts: general conditions and specific conditions. General conditions include the time, frequency, and amount of data to be synchronized; specific conditions are the specific conditions that data synchronization must meet, such as data synchronization occurring when a certain performance indicator is below a specific threshold.

[0141] S603e, NDT MnS Producer performs NDT data synchronization.

[0142] S603f, the NDT MnS Producer sends an NDT configuration response to the NDT MnS Consumer, which includes one of the following parameters.

[0143] During the configuration phase - data synchronization, NDTState can be either "Data Synchronizing" or "Ready for Simulation," which also indicates that data synchronization is complete.

[0144] The NDT configuration history records the NDT data synchronization status, such as the current NDT data synchronization information.

[0145] NDT simulation phase:

[0146] S604a, the NDT MnS Consumer sends an NDT run request to the NDT MnS Producer. In this embodiment, it is an NDT simulation request, requesting to run NDT and report the simulation results.

[0147] S604b, the NDT MnS Producer performs NDT simulation and updates NDTStage to Simulation.

[0148] S604c, the NDT MnS Producer sends an NDT simulation response to the NDT MnS Consumer, and the NDT simulation response is configured to include one of the following parameters:

[0149] During the configuration phase – data synchronization, NDTState can be "Running" or "Finished," which also signifies the end of the simulation.

[0150] The NDT simulation report records the simulation results of NDT.

[0151] The NDT simulation history records the NDT data synchronization status, such as the data synchronization information for this NDT.

[0152] Figure 7 This is a flowchart illustrating the updating of an existing NDT instance according to an embodiment of this application, such as... Figure 7 As shown, it includes:

[0153] Case 1: The required NDT instance exists, but its capabilities do not meet the consumer's needs and it needs to be updated.

[0154] S701a, the NDT MnS Consumer sends an NDT update request to the NDT MnS Producer, requesting an update to the NDT instance. The NDT update request includes one of the following parameters:

[0155] NDT operation type (NDTOp). In this embodiment, the NDT operation type is NDT update (NDT_Update).

[0156] NDT operation information (NDTOpInfo) contains the corresponding NDT operation information for different NDT operations. When the NDT operation is "NDT Update", the NDT operation information (NDTOpInfo) is the same as the NDT update information (NDTUpdateInfo).

[0157] NDT update information (NDTUpdateInfo) includes at least one of the following parameters:

[0158] The updated NDT identifiers are the existing list of NDT identifiers;

[0159] Update the NDT component identifier to add / enhance / nest NDT identifiers or / and NDT component identifiers based on the updated NDT;

[0160] The NDT component update history records the component information or nesting information of NDT before and after each update operation.

[0161] S701b, NDT MnS Producer performs NDT update.

[0162] S701c, the NDT MnS Producer sends an NDT update response to the NDT MnS Consumer, and the response contains at least one of the following parameters:

[0163] During the update phase, the NDT state can be either "Updating" or "Updating_Completed".

[0164] An NDT profile (NDTProfile) must include at least one of the following parameters:

[0165] The NDT identifier identifies the newly created NDT instance;

[0166] NDT capability information;

[0167] NDT ingredient list;

[0168] The NDT creation context includes the NDT update time, NDT update components (NDT component change information), and NDT update reason.

[0169] S702, NDT MnS Producer performs NDT configuration, the same as S602a-2c above.

[0170] S703, NDT MnS Producer performs NDT simulation, as described in S604a-4c above.

[0171] S704a, the NDT MnS Consumer sends an NDT deactivation request to the NDT MnS Producer. The request message must contain at least one of the following parameters:

[0172] The NDT operation type (NDTRunOp) is defined in this embodiment as NDTRunOp = Deactivate, which can be further subdivided into activation, deactivation, running, pausing, and termination.

[0173] The NDT operation information (NDTRunOplnfo) includes the following parameters: NDT identifier, NDT component identifier, and NDT operation conditions.

[0174] S704b, the NDT MnS Producer performs NDT deactivation and updates NDTState to Deactivated;

[0175] In S704c, the NDT MnS Producer sends an NDT deactivation response to the NDT MnS Consumer, which includes the following parameters:

[0176] During the runtime phase, the NDT state can be "Activated", "Deactivated", "Running", "Suspended", "Finished", or "Terminated". In this embodiment, it is "Deactivated".

[0177] Case 2: The required NDT instance exists and its capabilities meet the requirements, so no update is needed.

[0178] S705a-5c is the same as S704a-4c, but the NDT run operation type (NDTRun0p) is Activate and the NDTState is Activated.

[0179] Repeat S702-3;

[0180] S705d-5f is the same as S704a-4c, but the NDT run operation type (NDTRunOp) is Terminate, and the NDTState is Terminated. Terminated means that the Producer clears the configuration information on the NDT, but does not delete the NDT instance.

[0181] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to 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 device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0182] This embodiment also provides a network digital twin management device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated. Applied to a first network element, the device includes:

[0183] The query module is used to query the NDT support information of the second network element;

[0184] The sending module is used to send an NDT management request to the second network element, wherein the NDT management request is used to request the second network element to manage the NDT.

[0185] This embodiment also provides a network digital twin management device, applied to a second network element, the device comprising:

[0186] The module provides NDT support information to the first network element.

[0187] The management module is used to manage NDT based on the NDT management request of the first network element.

[0188] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0189] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0190] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0191] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0192] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0193] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0194] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0195] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for managing a network digital twin, characterized in that, Applied to the first network element, including: Query the NDT support information of the second network element; Send an NDT management request to the second network element, wherein the NDT management request is used to request the second network element to manage NDT.

2. The method according to claim 1, characterized in that, Sending an NDT management request to the second network element includes at least one of the following: Send an NDT operation request to the second network element, wherein the NDT operation request is used to request the second network element to perform the operation of the NDT instance; Send an NDT configuration request to the second network element, wherein the NDT configuration request is used to request the second network element to configure the NDT instance; Send an NDT operation request to the second network element, wherein the NDT operation request is used to request the second network element to provide NDT operation results.

3. The method according to claim 2, characterized in that, After sending an NDT operation request to the second network element, the method further includes: Receive the NDT operation response sent by the second network element after performing at least one of the following operations: NDT creation, NDT deletion, NDT orchestration, NDT update, or NDT query.

4. The method according to claim 3, characterized in that, The NDT operation request includes at least one of the following: NDT type, NDT operation type, NDT operation information; and / or The NDT operation response includes at least one of the following: NDT status, NDT description file.

5. The method according to claim 4, characterized in that, The NDT type includes at least one of the following: real-time NDT, non-real-time NDT, and semi-real-time NDT; The NDT operation types include at least one of the following: NDT creation, NDT deletion, NDT orchestration, NDT update, and NDT query; The NDT operation information includes at least one of the following: NDT component list, NDT capability information, NDT component capability information; The NDT status includes at least one of the following: in progress, completed; The NDT description file includes at least one of the following: NDT identifier, NDT capability information, NDT component information, and NDT creation context.

6. The method according to claim 2, characterized in that, After sending an NDT configuration request to the second network element, the method further includes: The network element receives an NDT configuration response sent by the second network element, wherein the NDT configuration response is sent by the second network element after performing at least one of the following actions according to the NDT configuration request: NDT configuration, NDT data acquisition, NDT data synchronization, and updating the NDT status.

7. The method according to claim 6, characterized in that, The NDT configuration request includes at least one of the following: NDT identifier, NDT configuration type, NDT configuration information, NDT data acquisition information, NDT data synchronization information; and / or The NDT configuration response includes at least one of the following: NDT status, NDT configuration history.

8. The method according to claim 7, characterized in that, The NDT configuration type includes at least one of the following: configuration, data collection, data synchronization; and / or The NDT configuration information includes at least one of the following: NDT configuration range, NDT configuration parameters, NDT performance parameters; and / or The NDT data acquisition information includes at least one of the following: NDT data acquisition object, NDT data collection content, NDT data collection conditions; and / or The NDT data synchronization information includes at least one of the following: NDT data synchronization object, NDT data synchronization content, NDT data synchronization filtering conditions, NDT data synchronization conditions; and / or The NDT status includes at least one of the following: configuring, configuration completed, data acquisition in progress, data synchronization pending, data synchronization in progress, and simulation pending.

9. The method according to claim 2, characterized in that, After sending the NDT operation request to the second network element, the method further includes: The network receives an NDT operation response sent by the second network element, wherein the NDT operation response is sent by the second network element after performing one of the following actions based on the NDT operation request: NDT activation, NDT deactivation, NDT operation, and updating the NDT status.

10. The method according to claim 9, characterized in that, The NDT run request includes at least one of the following: NDT run operation type, NDT run operation information; and / or The NDT operation response includes: NDT status.

11. The method according to claim 10, characterized in that, The NDT operation type includes at least one of the following: activation, deactivation, running, pause, and termination; The NDT operation information includes at least one of the following: NDT identifier, NDT component identifier, and NDT operation conditions; The NDT state includes at least one of the following: active state, deactivated state, running, paused, completed, and terminated.

12. The method according to claim 1, characterized in that, The NDT support information for the second network element includes: Send an NDT query request to the first network element; The network element receives an NDT query response sent by the second network element, wherein the NDT query response carries the NDT support information, which is obtained by the second network element based on the NDT query request.

13. The method according to claim 12, characterized in that, The NDT support information includes at least one of the following: Existing NDT and NDT capability information; Existing NDT component and NDT component capability information; Supported NDT capability information; Supported NDT component capability information.

14. The method according to claim 13, characterized in that, The NDT capability information and the supported NDT capability information include one of the following: NDT type, general capability information, and scenario-based capability information; and / or The NDT component capability information and the supported NDT component capability information include one of the following: NDT component type, general capability information, and scenario-specific capability information.

15. A method for managing a network digital twin, characterized in that, Applied to the second network element, including: Provide NDT support information to the first network element; NDT management is based on the NDT management request of the first network element.

16. The method according to claim 15, characterized in that, NDT request management based on the first network element includes: The NDT operation request based on the first network element is used to execute the operation of the NDT instance; Configure the NDT instance based on the NDT configuration request of the first network element; Provide NDT operation results based on the NDT operation request of the first network element.

17. The method according to claim 16, characterized in that, The operations performed on the NDT instance based on the NDT operation request of the first network element include: Receive the NDT operation request sent by the first network element; Based on the NDT operation request, perform at least one of the following operations: NDT creation, NDT deletion, NDT orchestration, NDT update, or NDT query; Send an NDT operation response to the first network element.

18. The method according to claim 17, characterized in that, The NDT operation request includes at least one of the following: NDT type, NDT operation type, NDT operation information; and / or The NDT operation response includes at least one of the following: NDT status, NDT description file.

19. The method according to claim 18, characterized in that, The NDT type includes at least one of the following: real-time NDT, non-real-time NDT, semi-real-time NDT; and / or The NDT operation types include at least one of the following: NDT creation, NDT deletion, NDT orchestration, NDT update, and NDT query; and / or The NDT operation information includes at least one of the following: an NDT component list, NDT capability information, NDT component capability information; and / or The NDT status includes at least one of the following: in progress, completed; and / or The NDT description file includes at least one of the following: NDT identifier, NDT capability information, NDT component information, and NDT creation context.

20. The method according to claim 16, characterized in that, Configuring the NDT instance based on the NDT configuration request of the first network element includes: Receive the NDT configuration request sent by the first network element; Perform at least one of the following actions based on the NDT configuration request: NDT configuration, NDT data acquisition, NDT data synchronization, and update the NDT status; Send an NDT configuration response to the first network element.

21. The method according to claim 20, characterized in that, The NDT configuration request includes at least one of the following: NDT identifier, NDT configuration type, NDT configuration information, NDT data acquisition information, NDT data synchronization information; and / or The NDT configuration response includes at least one of the following: NDT status, NDT configuration history.

22. The method according to claim 21, characterized in that, The NDT configuration type includes at least one of the following: configuration, data collection, data synchronization; and / or The NDT configuration information includes at least one of the following: NDT configuration range, NDT configuration parameters, NDT performance parameters; and / or The NDT data acquisition information includes at least one of the following: NDT data acquisition object, NDT data collection content, NDT data collection conditions; and / or The NDT data synchronization information includes at least one of the following: NDT data synchronization object, NDT data synchronization content, NDT data synchronization filtering conditions, NDT data synchronization conditions; and / or The NDT status includes at least one of the following: configuring, configuration completed, data acquisition in progress, data synchronization pending, data synchronization in progress, and simulation pending.

23. The method according to claim 16, characterized in that, The NDT operation results provided based on the NDT operation request of the first network element include: Receive the NDT operation request sent by the first network element; Based on the NDT run request, perform one of the following: NDT activation, NDT deactivation, NDT run, and update the NDT status; Send an NDT operation response to the first network element.

24. The method according to claim 23, characterized in that, The NDT run request includes at least one of the following: NDT run operation type, NDT run operation information; and / or The NDT operation response includes: NDT status.

25. The method according to claim 24, characterized in that, The NDT operation type includes at least one of the following: activation, deactivation, running, pause, and termination; The NDT operation information includes at least one of the following: NDT identifier, NDT component identifier, and NDT operation conditions; The NDT state includes at least one of the following: active state, deactivated state, running, paused, completed, and terminated.

26. The method according to claim 15, characterized in that, Providing NDT support information to the first network element includes: Receive the NDT query request sent by the first network element; Obtain the NDT support information based on the NDT query request; Send an NDT query response to the first network element, wherein the NDT query response carries the NDT support information.

27. The method according to claim 26, characterized in that, The NDT support information includes at least one of the following: Existing NDT and NDT capability information; Existing NDT component and NDT component capability information; Supported NDT capability information; Supported NDT component capability information.

28. The method according to claim 27, characterized in that, The NDT capability information and the supported NDT capability information include one of the following: NDT type, general capability information, and scenario-based capability information; and / or The NDT component capability information includes one of the following: NDT component type, general capability information, and scenario-specific capability information.

29. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 14, 15 to 18.

30. A computer program product, characterized in that, Includes a computer program, which, when executed by a processor, implements the steps of the method described in any one of claims 1 to 14, 15 to 18.

Images