Network management method, electronic device and computer-readable storage medium

Abstract

The present application provides a network management method, an electronic device and a computer-readable storage medium. The method comprises: a digital twin system receiving a network service request sent by a request end, determining target network entity data required for executing the network service request, and acquiring a target service model corresponding to the network service request; and inputting the target network entity data into the target service model so as to obtain a service result corresponding to the network service request.

Description

Network management method, electronic device, and computer-readable storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on the Chinese patent application with application number 202311094287.4 and application date August 25, 2023, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this application as a reference. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a network management method, an electronic device, and a computer-readable storage medium. Background Art

[0004] The bearer network is the infrastructure of communications networks and the network foundation supporting the digital transformation of countless industries. Users have higher expectations for bearer network performance and reliability. As bearer network applications continue to expand, the full lifecycle operation and maintenance of the bearer network is becoming increasingly complex. Traditional O&M methods are no longer able to adapt to the scale of business growth and cannot support efficient management and control. Therefore, the bearer network needs to develop towards a self-intelligent network throughout its lifecycle. A self-intelligent bearer network should possess precise perception, automated reasoning, decision-making, and verification capabilities. However, the high trial-and-error costs of network entities make it difficult to support these capabilities.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a network management method, an electronic device, and a computer-readable storage medium, which aim to simulate the behavior and performance of network entities through a digital twin system and provide service support for a self-intelligent bearer network.

[0007] In a first aspect, an embodiment of the present application provides a network management method applied to a digital twin system, wherein the digital twin system includes at least one network service model, and the method includes:

[0008] receiving a network service request sent by a requesting end, determining target network entity data required to execute the network service request, and obtaining a target service model corresponding to the network service request, wherein the target service model is a model in the at least one network service model;

[0009] The target network entity data is input into the target service model to obtain a service result corresponding to the network service request.

[0010] In a second aspect, an embodiment of the present application provides a network management method, applied to a controller, the method comprising:

[0011] Send network service requests to the digital twin system;

[0012] Receiving a service result returned by the digital twin system according to the network service request;

[0013] Execute corresponding network operations according to the service result.

[0014] In a third aspect, an embodiment of the present application provides a digital twin system, including a network service unit, a network simulation unit, and a network mirror unit, wherein:

[0015] The network mirroring unit is used to collect network entity data;

[0016] The network simulation unit includes at least one network service model;

[0017] The network service unit is configured to receive a network service request sent by a requesting end, determine target network entity data required to execute the network service request from the network mirroring unit, and determine a target service model corresponding to the network service request from the network simulation unit, wherein the target service model is a model among the at least one network service model;

[0018] The network simulation unit is used to input the target network entity data into the target service model to obtain the service result corresponding to the network service request.

[0019] In a fourth aspect, an embodiment of the present application provides an electronic device, including:

[0020] one or more processors;

[0021] A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the network management method as described in the first aspect above or the network management method as described in the second aspect above.

[0022] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the network management method as described in the first aspect or the network management method as described in the second aspect.

[0023] In an embodiment of the present application, at least one network service model is deployed in the digital twin system to construct a digital twin corresponding to the network entity. In response to the network service request, the digital twin system obtains the target network entity data required to execute the network service request, and obtains the target service model corresponding to the network service request, and then inputs the target network entity data into the target service model to obtain the service result corresponding to the network service request, and then returns the service result to the requesting end that sent the network service request. The solution of the embodiment of the present application predicts or monitors the status of the network entity based on the service result of the target network entity data by the target service model in the digital twin system, simulates the behavior and performance of the network entity, and provides service support for the self-intelligent bearer network. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 is a schematic diagram of the self-intelligent network target framework;

[0025] FIG2 is a schematic diagram of an exemplary architecture of a management and control system;

[0026] FIG3 is a schematic diagram of an exemplary architecture of an SDN controller;

[0027] FIG4 is a schematic diagram of the architecture of a network management system provided in an embodiment of the present application;

[0028] FIG5a is a schematic diagram of a specific architecture of a network management system provided in an embodiment of the present application;

[0029] FIG5 b is a schematic diagram of a specific architecture of another network management system provided in an embodiment of the present application;

[0030] FIG6 is a flow chart of a network management method provided in an embodiment of the present application;

[0031] FIG7 is a schematic diagram of a service model deployment of a digital twin system provided in an embodiment of the present application;

[0032] FIG8 is a flow chart of a network management method provided in an embodiment of the present application;

[0033] FIG9 is a schematic diagram of the interaction of the network management system provided in Example 1 of the present application;

[0034] FIG10 is a schematic diagram of the interaction of the network management system provided in Example 2 of the present application;

[0035] FIG11 is a schematic diagram of the interaction of the network management system provided in Example 3 of the present application;

[0036] FIG12 is a schematic diagram of the interaction of the network management system provided in Example 4 of the present application;

[0037] FIG13 is a schematic diagram of the interaction of the network management system provided in Example 5 of the present application;

[0038] FIG14 is a schematic diagram of the architecture of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the technical solution of the present application, the network management method, electronic device and computer-readable storage medium provided by the present application are described in detail below with reference to the accompanying drawings.

[0040] Hereinafter, example embodiments will be described more fully in conjunction with the accompanying drawings, but the described example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these examples are provided so that this application will be thorough and complete and will fully enable those skilled in the art to understand the scope of this application.

[0041] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0042] The terms used herein are used only to describe specific embodiments and are not intended to limit this application. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and / or "made of" are used in this specification, they specify the presence of features, wholes, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or groups thereof.

[0043] In the description of the embodiments of the present application, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it can be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.

[0044] In the description of the embodiments of this application, any embodiment or design scheme using "exemplary," "for example," or "for example" should not be understood as being more preferred or advantageous than other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete manner.

[0045] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly identifying the technical features being referred to. Thus, features specified as "first" or "second" may explicitly or implicitly include one or more of such features. The terms "include," "comprising," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0046] In order to facilitate understanding of the solutions of the embodiments of the present application and to provide a clear and concise description of the following embodiments, an introduction to the relevant terms involved in the present application is first given.

[0047] Bearer network:

[0048] The bearer network is the basic network that provides network connectivity for the wireless access network and the core network. It includes the access layer, aggregation layer, and core layer, and provides connectivity services for the network.

[0049] Self-Intelligent Network:

[0050] The self-intelligent network focuses on the planning, construction, maintenance, optimization, and operation management of the bearer network. Figure 1 shows a schematic diagram of the self-intelligent network's target framework. Within the self-intelligent network's target framework, a four-layer, three-closed-loop network architecture is constructed, evolving towards informatization, automation, and intelligence.

[0051] The four management levels include:

[0052] Network element management: Provides built-in intelligent operation and maintenance capabilities for network elements.

[0053] Network management: Provides network-oriented, single-professional, self-intelligent operation and maintenance capabilities.

[0054] Business Management: Provides cross-disciplinary, self-intelligent O&M capabilities for networks and businesses.

[0055] Business Management: Provides customer-oriented self-service management capabilities and unified customer touchpoints.

[0056] The three types of closed loops include:

[0057] Resource closed loop: Single-professional resource management enables single-domain autonomy.

[0058] Business closed loop: Business-oriented, cross-disciplinary end-to-end management to achieve cross-domain collaboration.

[0059] User closed loop: user and business management, including user information, operations, billing, customer service, etc.

[0060] The closed loop seeks to achieve and maintain explicitly set intention goals or automatically execute determined rules / policy instructions through four activities: perception, analysis, decision-making, and execution.

[0061] Digital Twin:

[0062] Digital twin refers to the technology of virtually simulating and modeling an entity (such as a product, system, process, or entire organization) through digital models and physical data. It combines information such as the entity's physical characteristics, behavior, and performance with the digital model to create a digital copy or mirror image of the entity.

[0063] Management and control system:

[0064] Management Control Continuum (MCC) integrates essentially identical management and control functions to achieve unified management and control of transport resources, providing integrated management and control services to upper-layer users. Software-defined network (SDN) controllers, element management systems (EMS), network management systems (NMS), and control planes are all examples of a management and control system. Functional modules within a management and control system provide functional services through interfaces.

[0065] Connection scheduling is a fundamental function of a control system. Figure 2 shows an exemplary architecture diagram of a control system. Figure 2 illustrates the components of the control system and the interaction sequence for establishing a connection. These components include: a network call controller (NCC), a connection controller (CC), a routing controller (RC), a link resource manager (LRM), a termination and adaptation performer (TAP), and forwarding plane network elements.

[0066] The link topology and resource usage information in the controller are stored in the Resource Database (RDB).

[0067] The resources of the forwarding plane (such as time slots and bandwidth) need to be converted into resources that can be controlled in the management and control system. The resources of the forwarding plane are represented by forwarding points (FP) or forwarding end points (FwEP), and the resources used by the management and control system are represented by subnetwork points (SNP). The relationship between FP / FwEP and SNP is managed by the TAP module. One SNP can be bound to one FP / FwEP; multiple SNPs can also be bound to one FP / FwEP to indicate that multiple SNPs share the use of the FP / FwEP resources. In other words, the connection maintained by the management and control system uses a series of SNPs (including the first and last SNPs) from the perspective of management; from the perspective of the forwarding plane, it uses the FP / FwEP resources in the forwarding plane network element.

[0068] A group of SNPs is represented as a SNPP (Subnetwork Point Pool). The association between different SNPPs is represented as an SNPP Link. An SNP identifier represents an instance of an SNP, and an SNPP identifier represents an instance of an SNPP. A Boundary Resource Identifier (BRI) is used at domain boundaries to identify transmission resources at that boundary and to control interfaces between components.

[0069] The component interaction process for the controller to directly control the transmission resources may include:

[0070] As shown in Figure 2, in the controller, when the NCC receives a connection request (1), the boundary resource identifier BRI in the request is converted by DS (2) into two SNP identifiers within the controller. The connection request may also carry part or all of the connection routing information. The NCC sends the first and last SNP identifiers to the CC (3). The CC requests the RC to query the connection route between the first and last SNPs (4). The RC calculates the path that meets the CC request based on the topology and local connection status information provided by the LRM (5). If the CC request carries the connection routing information, the connection routing information can also participate in the RC's routing query. The RC returns the routing information to the CC, and the CC requests the LRM (6) to select an appropriate link connection from the links passed by the route; the LRM configures the forwarding resource usage status to the forwarding plane through the TAP component (7, 8). After the forwarding plane updates the link resource usage status and establishes the subnet cross connection, the connection established by the controller is successfully established. After the establishment is successful, the NCC responds to the client that the connection is successfully established.

[0071] Taking the SDN controller as an example of a management and control system, Figure 3 shows an exemplary architecture diagram of an SDN controller. As shown in Figure 3, in the SDN controller hierarchical architecture, a client layer and service layer relationship is formed between the upper and lower layer controllers; the client layer controller and the service layer controller interact through an interaction context, where the interaction context includes at least one of a service context (ServerContext) and a client context (ClientContext). Each controller can create multiple client contexts, at least one service context, and an administrative context (Administrative Context). The administrative context provides support information for administrators to manage and control the controller and exercise administrator roles within the controller, including maintaining the lifecycle of client contexts and service contexts.

[0072] For resource management and control within the SDN controller, the resources of the service context can be forwarding plane resources directly controlled by the local controller or resources provided by the service layer controller. These resources are mapped to the local resource pool (Local Resource Pool) in the management context. The management context then allocates subsets of the local resource pool to different customer contexts. For each customer context, resources are provided to the customer layer controller through the virtual network. The resources of the above controllers and contexts are SNP / SNPP / SNPP Link, and the resources within the forwarding plane are FP / FwEP. A group of SNPs is represented as SNPP (Subnetwork Point Pool), and the association between different SNPPs is represented as SNPP Link. The SNP identifier represents an instance of the SNP, and the SNPP identifier represents an instance of the SNPP. The Boundary Resource Identifier (BRI) is used at the domain boundary to identify the transmission resources at that boundary and the interface between control components.

[0073] Understandably, the bearer network is the infrastructure of the communications network and the network foundation supporting the digital transformation of numerous industries. Users have higher requirements for bearer network performance and reliability. Furthermore, as bearer network applications continue to expand, the full lifecycle operation and maintenance of the bearer network is becoming increasingly complex. Traditional O&M methods are no longer able to adapt to the scale of business growth and cannot support efficient management and control. Therefore, the bearer network needs to develop towards a self-intelligent network throughout its lifecycle. However, it is difficult to implement historical data backtracking, low-cost trial and error, and prediction functions in physical networks to support the self-intelligent bearer network's accurate perception, automated reasoning, decision-making, and verification. Therefore, it is necessary to build a digital twin system to achieve virtual-physical interaction with the physical network. At the same time, it is necessary to clarify the interaction between the digital twin network and the existing management and control system to address these issues.

[0074] Please refer to Figure 4, which is a schematic diagram of the architecture of a network management system provided in an embodiment of the present application. As shown in Figure 4, the network management system includes an upper-layer application, a controller, a digital twin system, and a network entity, wherein the upper-layer application is respectively communicated with the controller and the digital twin system, the network entity is respectively communicated with the controller and the digital twin system, and the controller and the digital twin system are communicated with each other.

[0075] The digital twin system can interact with the controller and upper-level applications. The digital twin system can include at least one of network mirroring, network simulation and network services. The controller can include at least one of customer context, service context and management context.

[0076] Please refer to Figure 5a, which is a schematic diagram of a specific architecture of a network management system provided by an embodiment of the present application. In the network management system shown in Figure 5a, the network entity includes a physical network entity and / or a virtual network entity, the controller includes a customer context and a service context, and the digital twin system includes three units: network mirroring, network simulation, and network service, wherein:

[0077] The network mirror collects various types of data from network entities and controllers, which can form real-time data and historical data of network entities in time series, including status data, configuration data and relationships between entities.

[0078] Network simulation involves establishing analysis and behavioral models of network entities based on various data from network mirrors, which can include device-level, network element-level, and network-level models.

[0079] Network services are based on various data in the network image and models in the network simulation. They select appropriate models for model orchestration / calling and instantiation according to externally requested services to complete the requested services, which may include simulation, prediction, traceability, backtracking, and optimization services.

[0080] The controller and / or upper-layer applications negotiate or configure contracts / parameters with the digital twin system, and the content may include at least one of the following: communication protocols / parameters, authentication / authorization, and namespace. Therefore, the controller and the digital twin system can exchange each other's capabilities, and / or, the upper-layer applications and the digital twin system can exchange each other's capabilities. The content of the capability interaction may include at least one of the following: the controller's customer context identifier and service context identifier, the information provided by the controller (performance alarms and configuration, etc.) and network resources, etc., the digital twin system's function or service identifier, the digital twin system's network resources, etc.

[0081] It should be noted that the number of physical network entities and virtual network entities in the network entity can be one or more.

[0082] Please refer to Figure 5b, which is a schematic diagram of another specific architecture of the network management system provided in an embodiment of the present application. The network management system shown in Figure 5b differs from the network management system shown in Figure 5a in that the controller also includes a management context. Capability negotiation or configuration of the control system and the digital twin system can be completed through the management context.

[0083] It should be noted that the network management system embodiments described above are merely illustrative. For example, the division of units or components represents only a logical functional division. Actual implementations may employ alternative divisions, such as combining or integrating multiple units or components into another device, or omitting or disabling certain features. Furthermore, any coupling, direct coupling, or communication connection shown or discussed may be implemented via interfaces.

[0084] It should be noted that, in addition to obtaining capability information through capability interaction, digital twin system capabilities can also be directly configured through upper-layer applications. After capability configuration, the digital twin system acquires network service capabilities. Upon receiving a network service request from a controller or upper-layer application, the digital twin system can select the appropriate model based on its own network service capabilities to execute the requested service, such as simulation, prediction, traceability, backtracking, and optimization.

[0085] It should be noted that when the upper-level application or controller makes a service request to the digital twin system, it can determine the identifier of the specific service requested and can carry corresponding parameters, such as strategies, constraints, time series and other information, as well as the context identifier of the controller. The digital twin system can return the processing results of the service based on the corresponding network resources of the context identifier, information provided by the components, and other information.

[0086] It should be noted that when an upper-layer application or digital twin system makes a connection configuration request to the controller, the requested context is determined, which can carry corresponding boundary resource identifiers, relevant policies, constraints, time series, and other information. The controller then returns the corresponding connection configuration result. For example, the connection configuration request can be a create connection request, a delete connection request, or a modify connection configuration request.

[0087] The network management method provided in the embodiment of the present application is described below in conjunction with the architecture of the network management system shown in Figure 4, Figure 5a or Figure 5b.

[0088] Please refer to Figure 6, which is a flowchart of a network management method provided in an embodiment of the present application. The network management method is applied to a digital twin system, which includes at least one network service model. As shown in Figure 6, the network management method includes the following steps:

[0089] Step S110: receiving a network service request sent by a requesting end.

[0090] Exemplarily, the requesting end may be any interactive context in the controller, that is, the requesting end may be any one of a client context and a service context.

[0091] Exemplarily, the requesting end may also be an upper-layer application.

[0092] Exemplarily, the network service request includes at least one of the following: a simulation service request, a prediction service request, a tracing service request, an optimization service request, or a backtracking service request.

[0093] Step S120: determining target network entity data required to execute the network service request.

[0094] Exemplarily, before receiving the network service request sent by the requesting end, the network management method further includes: collecting network entity data from the controller and / or network entity, and forming real-time network entity data and historical network entity data based on the collected network entity data.

[0095] Correspondingly, in step S120 , determining the target network entity data required for executing the network service request specifically includes: acquiring the target network entity data required for executing the network service request from the real-time network entity data and / or the historical network entity data.

[0096] It should be noted that the network entity may include a physical network entity and / or a virtual network entity. Therefore, the above-mentioned network entity data may include physical network entity data and / or virtual network entity data.

[0097] In a specific embodiment, physical network entity data is organized into real-time physical network entity data and historical physical network entity data according to time series. Similarly, virtual network entity data can also be organized into real-time virtual network entity data and historical virtual network entity data according to time series.

[0098] Exemplarily, the network entity data includes at least one of the following: resource data, configuration data, alarm data, or performance data. Please refer to Table 1, which provides data contents included in various data categories.

[0099] Table 1

[0100] Step S130: Obtain a target service model corresponding to the network service request, wherein the target service model is a model among the at least one network service model mentioned above.

[0101] Exemplarily, the at least one network service model includes at least one of the following: a network-level model, a network element-level model, or a device-level model. As shown in Table 2, Table 2 lists the models included in the network-level model, the network element-level model, and the device-level model, respectively.

[0102] Table 2

[0103] In a specific embodiment, the network-level model, the network-element-level model, and the device-level model each include multiple models corresponding to different network service types.

[0104] For example, the network service type may include at least one of the following: simulation service type, prediction service type, traceability service type, optimization service type, or backtracking service type. As shown in Table 3, Table 3 provides the service content corresponding to each network service type.

[0105] Table 3

[0106] Please refer to Figure 7, which is a schematic diagram of the service model deployment of the digital twin system provided in an embodiment of the present application. As shown in Figure 7, the digital twin system is deployed with network-level models, network element-level models, and device-level models. In addition, the network-level model, network element-level model, and device-level model respectively include models of simulation service type, prediction service type, traceability service type, optimization service type, and backtracking service type.

[0107] As shown in Figure 7, the network-level model can include a constant bit rate (CBR) service model, an optical transform unit (OTU) model, and an optical layer model. The CBR service model, OTU model, and optical layer model are further deployed with simulation service type models, prediction service type models, traceability service type models, optimization service type models, and backtracking service type models according to the service type. For each service type, multiple sub-service models can be further subdivided according to the multiple sub-service types included in the service type. For example, the optical layer simulation model includes an optical layer protocol simulation model, an optical layer energy consumption simulation model, and an optical layer fault simulation model.

[0108] As shown in Figure 7, the network element-level model can include a network element model, a board model, and a port model. The network element model, board model, and port model are further deployed based on service type, including simulation service models, prediction service models, traceability service models, optimization service models, and backtracking service models. Each service type can be further subdivided into multiple sub-service models based on the various sub-service types included in that service type. For example, the port simulation model includes a port protocol simulation model, a port energy consumption simulation model, and a port fault simulation model.

[0109] As shown in Figure 7, the device-level model can include a service chip model, an optical device model, and a fiber model. These models are further divided into simulation service models, prediction service models, traceability service models, optimization service models, and backtracking service models, respectively, based on the service type. Each service type can be further subdivided into multiple sub-service models based on the various sub-service types it encompasses. For example, the optical device simulation model includes an optical device protocol simulation model, an optical device traffic simulation model, an optical device energy consumption simulation model, and an optical device fault simulation model.

[0110] Exemplarily, the network service request carries service parameters that instruct the digital twin system to determine the target network entity data required to execute the network service request and to obtain the target service model corresponding to the network service request. The service parameters may include at least one of the following: a service identifier, a service policy parameter, a constraint parameter, or a time series parameter.

[0111] Exemplarily, the service identifier is used to indicate the type of service requested by the network service request, for example, any one or more of simulation service, prediction service, traceability service, optimization service, or backtracking service.

[0112] Exemplarily, the service policy parameter is used to instruct the digital twin system on the strategy for executing network service requests.

[0113] Exemplarily, the constraint parameter is used to indicate the constraints of the digital twin system executing the network service request, for example, executing object constraints.

[0114] Exemplarily, the time series parameter is used to indicate the scope of the digital twin system to obtain target network entity data.

[0115] In a specific embodiment, the service parameters include constraint parameters, and the constraint parameters include object constraint parameters. The object constraint parameters are used to indicate the object on which the network service request is to be executed. For example, the execution object of the current network service request is the first OTU (network level); for another example, the execution object of the current network service request is the first board (network element level); and for another example, the execution object of the current network service request is the first optical device (device level).

[0116] In the case where the network service request carries an object constraint parameter, the above-mentioned determination of the target network entity data required to execute the network service request and acquisition of the target service model corresponding to the network service request may specifically include the following steps:

[0117] Determining an execution level corresponding to the network service request according to the object constraint parameters, wherein the execution level includes a device level, a network element level, and a network level;

[0118] When the execution level is the device level, a target device corresponding to the object constraint parameter is determined, network entity data corresponding to the target device is used as target network entity data, and a corresponding device-level model is selected as a target service model according to the target device;

[0119] When the execution level is the network element level, the target network element and / or the target device associated with the target network element corresponding to the object constraint parameter is determined, and the network entity data corresponding to the target network element and / or the target device associated with the target network element is used as the target network entity data. A corresponding device-level model can be selected according to the target device associated with the target network element to form a network element-level model, and the network element-level model is used as the target service model;

[0120] When the execution level is the network level, determine the target network and / or network elements associated with the target network corresponding to the object constraint parameters, and use the network entity data corresponding to the target network and / or network elements associated with the target network as the target network entity data. According to the network elements associated with the target network, the corresponding network element level model can be selected to form a network level model, and the network level model can be used as the target service model.

[0121] For example, since virtual networks / virtual network elements are generally abstract, when the object executed by the network service request is a virtual network / virtual network element, the virtual network / virtual network element can be combined according to its degree of abstraction, and the data of the edge access point of the virtual network / virtual network element can be directly used as the abstract data of the virtual network / virtual network element. When the object executed by the network service request is a physical network, the entity data of the physical network can be constructed based on the data of the physical network elements and physical devices associated with the physical network. When the object executed by the network service request is a physical network element, the entity data of the physical network element can be constructed based on the data of the physical devices associated with the physical network element.

[0122] In a specific embodiment, based on the object constraint parameters carried by the current network service request, it is determined that the execution level corresponding to the current network service request is the device level, and the specific execution object (i.e., the target device) is the first business chip; then, the network entity data related to the first business chip is searched from the network image to obtain the target network entity data; and based on the target device being the first business chip, the business chip model is selected as the target service model. For example, if the current network service request is a business chip energy consumption prediction request, the business chip energy consumption prediction model is selected as the target service model.

[0123] In another specific embodiment, based on the object constraint parameters carried by the current network service request, it is determined that the execution level corresponding to the current network service request is the network element level, and the specific execution object (i.e., the target network element) is the first line board; then, based on the devices (service chips, optical devices, optical fibers, etc.) contained on the first line board, the devices associated with the first line board are determined, and the network entity data of the first line board and its associated devices are searched from the network image to obtain the target network entity data; based on the first line board and its associated devices, the relevant device-level model is selected to construct a network element-level model, and the constructed network element-level model is used as the target service model.

[0124] In another specific embodiment, based on the object constraint parameters carried by the current network service request, it is determined that the execution level corresponding to the current network service request is the network level, and the specific execution object (i.e., the target network) is the first optical layer network; then, based on the network elements contained in the first optical layer network, the network elements associated with the first optical layer network are determined, and the network entity data of the first optical layer network and its associated network elements are searched from the network image to obtain the target network entity data; based on the first optical layer network and its associated network elements, relevant network element-level models are selected to construct a network-level model, and the constructed network-level model is used as the target service model.

[0125] It's understandable that each network simulation model in a digital twin system possesses independent simulation capabilities. Based on the needs of the application scenario, the relationships between network simulation models are analyzed according to data flow, enabling data transfer between them. By setting the online simulation sequence for each simulation model, various simulation tasks are serialized, enabling the orchestration of the digital twin model. The results of the twin model orchestration can be saved to a file for later access. The digital twin system allocates memory and computing resources to the orchestrated model and creates a digital twin model instance.

[0126] Exemplarily, there are multiple target service models. After obtaining the target service model corresponding to the network service request, the network management method of an embodiment of the present application also includes: arranging the multiple target service models according to a preset association relationship to determine the data transfer relationship between the multiple target service models.

[0127] Among them, arranging multiple target service models according to preset association relationships includes: hierarchically arranging multiple target service models according to network structure or network topology; and / or hierarchically arranging multiple target service models according to the life cycle of network services.

[0128] It is understandable that the arrangement or calling relationship between the network service and network simulation models can be a horizontal call or a vertical call, that is, it can be a vertical model arrangement based on the application scenario, that is, a hierarchical arrangement of a group of simulation models, such as serialization through network structure or topology relationship, or it can be a horizontal model arrangement based on the life cycle of the service. For example, when there is an external request, the network service unit can make a horizontal call to one or more services according to the external request, such as closed-loop operations such as prediction, optimization, and simulation, or it can make a vertical call according to the external request service. For example, according to the strategy, some network element-level energy consumption models are selected to build a network-level energy consumption model to provide services. Similarly, the network element-level energy consumption model can also be built based on the device-level energy consumption model. At the same time, according to the granularity of the energy consumption service requested by the external, different levels of energy consumption models such as network level, network element level, and device level can be selected to provide services.

[0129] Step S140: input the target network entity data into the target service model to obtain a service result corresponding to the network service request.

[0130] For example, the digital twin system receives a network service request and determines, based on the service identifier, that the requested service type is a performance backtracking service or a performance optimization service. Based on the constraint parameters, the execution scope is determined to be the optical layer network. Therefore, the optical layer performance backtracking service model and the optical layer performance optimization service model are selected as the target network models. These models are orchestrated based on the service policy parameters, with the optical layer performance backtracking service model orchestrated before the optical layer performance optimization service model. Based on the time series parameters, the network entity data required to execute the optical layer performance backtracking service and the optical layer performance optimization service are obtained within a week. When executing the network service request, the network entity data required to execute the optical layer performance backtracking service is first input into the optical layer performance backtracking service model. The optical layer performance backtracking service model then executes the optical layer performance backtracking task and obtains the optical layer performance backtracking results. The optical layer performance optimization service model then outputs the optical layer performance optimization results based on the optical layer performance backtracking results and the network entity data related to optical layer performance optimization.

[0131] Exemplarily, the digital twin system may be connected to a controller, and the controller may include a customer context and a service context, wherein the customer context is connected to an upper-layer application, and the service context is connected to at least one of a physical network and a lower-layer controller.

[0132] Before receiving the network service request sent by the requesting end, the network management method further includes:

[0133] The digital twin system exchanges basic information with the controller to establish a communication connection with the controller, wherein the content of the basic information exchange includes at least one of the following: communication protocol, communication parameters, authentication information, authorization information, and namespace;

[0134] The digital twin system performs capability interaction with the controller to obtain network service capabilities, wherein the content of the capability interaction includes at least one of the following: the customer context identifier of the controller, the service context identifier of the controller, the information provided by the controller, the network resources of the controller, the service identifier of the digital twin system, or the network resources of the digital twin system.

[0135] It is understandable that the digital twin system first exchanges basic information with the controller to establish a communication connection between the two, including exchanging each other's communication protocols / parameters, mutual authentication and authorization, and exchanging each other's namespaces. After establishing the communication connection, the digital twin system exchanges capabilities with the controller to provide support for the subsequent execution of network service requests by the digital twin system. After the capability interaction, when the upper-level application or controller makes a network service request to the digital twin system, the request can carry a specific service identifier, as well as corresponding parameters, such as policies, constraints, time series and other information, and the context identifier of the controller. The digital twin system can return the processing results of the network service based on the context identifier and its corresponding network resources, information provided by components, and other information.

[0136] After capability interaction, when the upper-layer application or digital twin system makes a connection configuration request to the controller, the requested context is determined, which can carry corresponding boundary resource identifiers, related policies, constraints, time series and other information, and the controller returns the connection configuration result.

[0137] Exemplarily, the controller is configured to: collect network entity data from the network entity through the service context, and send the collected network entity data to the digital twin system.

[0138] Exemplarily, the controller is configured to receive a connection configuration request from an upper-layer application via a client context, and determine a connection path based on the connection configuration request. For example, the connection configuration request may include a boundary resource identifier (BRI). The controller then converts the BRI into two SNP identifiers within the controller, queries the connection route between the first and last SNPs, and calculates a path that satisfies the connection configuration request based on the network topology and local connection status information.

[0139] Exemplarily, the service request includes a routing protocol simulation service request, and the controller is further configured to: generate a service request as a routing protocol simulation service request according to the connection path through the customer context, and send the routing protocol simulation service request to the digital twin system so that the digital twin system determines the service result corresponding to the routing protocol simulation service request. It can be understood that the controller can select an appropriate link (i.e., path) connection from the links passed by the route based on the routing information of the connection. The controller sends a routing protocol simulation service request to the digital twin system so that the digital twin system performs a routing protocol simulation on the selected link to verify whether the link meets the network routing protocol.

[0140] In one specific embodiment, the controller is further configured to: if the service result corresponding to the routing protocol simulation service request is a successful result, configure the network connection of the network entity through the service context. It is understood that if the routing protocol simulation result returned by the digital twin system indicates that the currently selected path satisfies the network routing protocol, then the relevant network connection configuration can be performed on the network entity through the service context based on the path to complete the network connection.

[0141] Exemplarily, the service request includes a connection configuration simulation service request, and the controller is further configured to:

[0142] A connection configuration simulation service request is generated based on the connection path through the service context, and the connection configuration simulation service is sent to the digital twin system so that the digital twin system can determine the service result corresponding to the connection configuration simulation service. It can be understood that after the controller calculates the network connection path, it simulates the connection configuration of the path through the digital twin system to determine whether the connection configuration of the path can be successfully configured in the network entity.

[0143] In a specific embodiment, the controller is further configured to: if the service result corresponding to the connection configuration simulation service is a success result, perform network connection configuration on the network entity using the service context. It is understood that if the connection configuration simulation result returned by the digital twin system indicates that the connection configuration of the path can be successfully configured in the network entity, then the relevant network connection configuration can be performed on the network entity based on the path using the service context to complete the network connection.

[0144] It should be noted that the client context sends a routing protocol simulation service request to the digital twin system, and the service context sends a connection configuration simulation service request to the digital twin system, which can be carried out at the same time.

[0145] Exemplarily, after obtaining the service result corresponding to the network service request, the network management method of an embodiment of the present application also includes: when the service result is a successful result, sending a connection configuration request to the customer context of the controller, so that the customer context conveys the connection configuration request to the service context, and then performing connection configuration according to the connection configuration request through the service context, and returning the connection configuration result to the customer context; the digital twin system receives the connection configuration result corresponding to the connection configuration request from the customer context of the controller.

[0146] For example, after the digital twin system completes the optimization and simulation tasks of the optical layer service, it sends a connection configuration request to the controller's customer context. The connection configuration request carries the configuration data of the optimized optical layer service. After receiving the connection configuration request, the customer context forwards the connection configuration request to the service context, so that the service context can optimize the connection configuration of the optical layer service entity according to the connection configuration request, and report the connection configuration result to the customer context after completing the connection configuration optimization. The customer context returns the connection configuration result to the digital twin system.

[0147] The embodiments of the present application propose a method for constructing and interacting with a digital twin system of a bearer network, that is, the digital twin system can interact with the controller and upper-layer applications of the management and control system, and respond to network service requests from the controller or upper-layer applications. The digital twin system simulates the performance or behavior of entities at the network level, network element level, or device level, and completes simulation, prediction, tracing, optimization, or backtracking at the network level, network element level, or device level. The processing results of the digital twin system can provide support for the self-intelligence of the bearer network.

[0148] Please refer to FIG8 , which is a flow chart of a network management method provided in an embodiment of the present application. The network management method is applied to a controller. As shown in FIG8 , the network management method includes the following steps S210 - S230:

[0149] Step S210: Send a network service request to the digital twin system.

[0150] Exemplarily, the network service request includes at least one of the following: a simulation service request, a prediction service request, a tracing service request, an optimization service request, or a backtracking service request.

[0151] Exemplarily, the controller includes one or more interaction contexts. The interaction context can be at least one of a customer context and a service context, and network service requests are sent by at least one of the customer context and the service context. That is, both the customer context and the service context can send network service requests to the digital twin system, and both the customer context and the service context can send network service requests to the digital twin system simultaneously.

[0152] Step S220: Receive the service result returned by the digital twin system based on the network service request.

[0153] The digital twin system completes the service requested by the network service request sent by the controller through the locally deployed model and network entity data.

[0154] Step S230: Execute corresponding network operations according to the service result.

[0155] Exemplarily, the network management method of an embodiment of the present application may further include: collecting network entity data from the network entity through the service context, and sending the collected network entity data to the digital twin system, so that the digital twin system generates real-time network entity data and historical network entity data based on the network entity data, and determines the target network entity data required to execute the network service request from the real-time network entity data and / or historical network entity data. The network entity includes a physical network entity and / or a virtual network entity.

[0156] Exemplarily, the network management method of the embodiment of the present application may further include:

[0157] The controller exchanges basic information with the digital twin system to establish a communication connection with the digital twin system, wherein the content of the basic information exchange includes at least one of the following: communication protocol, communication parameters, authentication information, authorization information, and namespace;

[0158] The controller interacts with the digital twin system to enable the digital twin system to obtain network service capabilities, wherein the content of the capability interaction includes at least one of the following: the customer context identifier of the controller, the service context identifier of the controller, the information provided by the controller, the network resources of the controller, the service identifier of the digital twin system, or the network resources of the digital twin system.

[0159] Exemplarily, the service request includes a routing protocol simulation service request, and sending a network service request to the digital twin system includes:

[0160] Receive connection configuration request initiated by upper layer application through client context;

[0161] Determine a connection path according to the connection configuration request;

[0162] A service request is generated as a routing protocol simulation service request according to the connection path through the customer context, and the routing protocol simulation service request is sent to the digital twin system so that the digital twin system determines the service result corresponding to the routing protocol simulation service request.

[0163] Exemplarily, executing a corresponding network operation according to the service result may include: when the service result corresponding to the routing protocol simulation service request is a success result, configuring a network connection for the network entity through the service context.

[0164] Exemplarily, the service request includes a connection configuration simulation service request, and sending a network service request to the digital twin system includes:

[0165] Receive connection configuration request initiated by upper layer application through client context;

[0166] Determine a connection path according to the connection configuration request;

[0167] A connection configuration simulation service request is generated according to the connection path through the service context, and the connection configuration simulation service is sent to the digital twin system so that the digital twin system determines the service result corresponding to the connection configuration simulation service.

[0168] Exemplarily, the network management method of the embodiment of the present application may further include: when the service result corresponding to the connection configuration simulation service is a successful result, performing network connection configuration on the network entity through the service context.

[0169] Exemplarily, the network management method of an embodiment of the present application may also include: receiving a connection configuration request sent by the digital twin system through the customer context; performing connection configuration according to the connection configuration request through the service context, and returning the connection configuration result to the customer context; and sending the connection configuration result to the digital twin system through the customer context.

[0170] The embodiment of the present application further provides a digital twin system, which includes a network service unit, a network simulation unit and a network mirror unit, wherein:

[0171] The network mirroring unit is used to collect network entity data;

[0172] The network simulation unit includes at least one network service model;

[0173] The network service unit is used to receive a network service request sent by a requesting end, determine target network entity data required to execute the network service request from the network mirroring unit, and determine a target service model corresponding to the network service request from the network simulation unit, wherein the target service model is a model in at least one network service model;

[0174] The network simulation unit is further used to input the target network entity data into the target service model to obtain the service result corresponding to the network service request.

[0175] It should be noted that the information interaction, execution process, etc. between the above-mentioned units are based on the same concept as the method embodiment of this application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0176] The following describes the solutions of the embodiments of the present application through specific examples.

[0177] Example 1

[0178] Please refer to Figure 9, which is a schematic diagram of the interaction of the network management system provided in Example 1 of this application. As shown in Figure 9, the interaction process of the network management system includes:

[0179] The controller and the digital twin system negotiate or are configured with interaction-related contract / parameter information (11), such as authentication and authorization of service context and data processing, communication protocol and namespace. The negotiation or configuration of the capabilities of the controller and the digital twin system can be completed through management roles. The service context of the controller collects data of various entities / objects from network entities (12) and transmits it to the network mirror unit (12) of the digital twin system. This data may include alarms, performance, network topology and configuration data. The network mirror unit also collects data of various entities / objects from network entities (12). The two ways of obtaining data (12) of the network mirror unit may differ in data category, granularity and real-time performance. The network mirror unit processes the data (13) and can be automatically or manually triggered to back up the data to real-time data or historical data with time stamps. The upper-layer application and the digital twin system negotiate the required services (14), such as the backtracking of the performance of the optical module in a certain historical time period. The upper-layer application sends a backtracking service request to the network service unit of the digital twin system. The network service unit selects a suitable model, such as the optical module backtracking model, and arranges or calls the model (16). The network service unit triggers the network simulation unit to complete the instantiation of the optical module backtracking model according to the data reported by the network mirror unit (17), and realizes the backtracking of the required historical performance data (19). The data reported by the network mirror unit (17) is the data required for the instantiation of the model according to the service (14), which can be part or all of the real-time data and historical data of the requesting entity / object.

[0180] Example 2

[0181] Please refer to Figure 10, which is a schematic diagram of the interaction of the network management system provided in Example 2 of this application. As shown in Figure 10, the interaction process of the network management system includes:

[0182] The controller and the digital twin system negotiate or are configured with interaction-related contracts / parameters and other capabilities (21), such as communication protocols, authentication and authorization, namespaces, and network element-level simulation services of the digital twin system required by the controller, service context identifiers required by the digital twin system and their related network resource information. The negotiation or configuration of the capabilities of the controller and the digital twin system can be completed through the management role; services such as network element-level connection simulation complete the configuration simulation of the forwarding surface. The upper-layer application sends a connection configuration request (22) to the controller's client context. The controller calculates the connection path (23) based on the connection configuration request (22), and then requests the connection configuration from the service context. The service context sends a network element-level configuration simulation request (24) to the network service unit of the digital twin system. The request contains information such as the network element's port, switching or cross type, time slot and time series. The network service unit selects a suitable model to complete the model orchestration or call (25), such as the network element-level connection simulation model, and triggers the network simulation unit to instantiate the connection model based on the data of the relevant entities reported by the network mirror unit (26), thereby completing the network element connection configuration simulation (27) and returning the simulation result (28). If the simulation result (28) is a failure result, the controller's service context responds to the client context with a failure response. Otherwise, the configuration of the physical network is completed and the connection configuration result (29) is responded to the client context.

[0183] Example 3

[0184] Please refer to Figure 11, which is a schematic diagram of the interaction of the network management system provided in Example 3 of this application. As shown in Figure 11, the interaction process of the network management system includes:

[0185] The controller and the digital twin system negotiate or are configured with interaction-related contracts / parameters and other capabilities (31), such as communication protocols, authentication and authorization, namespaces, and network-level simulation services of the digital twin system required by the controller, customer context identifiers required by the digital twin system and their related resources and topology information. The controller and the digital twin system negotiate or are configured with network-level simulations required to complete the routing protocol simulation of the forwarding plane. The capability negotiation or configuration of the controller and the digital twin system can be completed through the management role. The controller receives a connection configuration request from the upper-layer application, such as receiving a connection configuration request (32) from the controller's customer context. The controller performs connection path calculation (33), and the customer The following text requests network-level routing protocol simulation from the network service unit (34) to verify the degree to which the routing protocol satisfies the constraints, such as the reliability of path protection / recovery in the event of a failure. The network service unit selects a suitable model to complete the arrangement or call of the simulation model (35), and triggers the network simulation unit to instantiate the routing simulation model based on the data of the relevant objects reported by the network mirror unit (36), thereby completing the simulation of the routing protocol (37) and returning the simulation result (38). If the result is a failure, the controller's client context directly responds to the failure or re-triggers the routing calculation. Otherwise, it requests the service context for connection configuration, completes the configuration of the physical network and responds to the configuration result (39).

[0186] Example 4

[0187] Please refer to Figure 12, which is a schematic diagram of the interaction of the network management system provided in Example 4 of this application. As shown in Figure 12, the interaction process of the network management system includes:

[0188] The controller negotiates or is configured with interaction-related contracts / parameters and other capabilities (41) with the digital twin system. It can also negotiate or be configured through management roles: such as communication protocols, authentication authorization and namespaces, as well as the controller's customer context identifier and network resources. At the same time, the upper-layer application and the digital twin system negotiate the required services (41'), such as business optimization services for a certain domain. The upper-layer application requests service optimization from the network service unit (42). The network service selects a suitable model to complete the orchestration or call of the optimization model (43), such as selecting the network-level service optimization model and service simulation model in the network simulation unit, and triggering the network simulation unit to instantiate the service optimization model and service simulation model according to the entity data of the domain object reported by the network mirror unit (44), determine the optimization plan for service configuration change, and simulate the optimized service configuration plan. After the service completes the closed loop from optimization to simulation (45), the network service unit sends a connection configuration request (46) to the controller's customer context based on the optimization and simulation results, such as a connection creation request, a connection deletion request, or a connection configuration modification request carrying a boundary resource identifier, related policies, constraints, and time series. After the controller completes the connection configuration of the network entity (47), the network service unit reports the configuration result (48) returned by the customer context to the upper-layer application.

[0189] Example 5

[0190] Please refer to Figure 13, which is a schematic diagram of the interaction of the network management system provided in Example 5 of this application. As shown in Figure 13, the interaction process of the network management system includes:

[0191] The digital twin system and the controller negotiate or are configured with interaction-related contracts / parameters and other capabilities. Management roles can also be used to negotiate or configure capabilities such as communication protocols, authentication authorization, and namespaces, as well as the controller's customer context identifier and network resources. Upper-layer applications and the digital twin system negotiate required services, such as network-level optical layer energy consumption prediction / optimization / simulation services. Upper-layer applications request the required services from the network service unit, which selects an appropriate model for orchestration or invocation. For example, it selects an energy consumption prediction model for optical devices in network simulation for orchestration or invocation to construct network element- and network-level optical layer energy consumption prediction models. This triggers the network simulation unit to obtain energy consumption-related data from the mirrored network unit, instantiate the aforementioned model, and complete network-level optical layer energy consumption prediction. Based on the prediction results, if potential risks are identified, optical layer resources may need to be optimized, such as concentrating the channel resources of optical layer services to save energy. That is: select the network-level optical layer service optimization model and optical layer service simulation model in the network simulation, and trigger the network simulation unit to obtain optical layer service-related data from the network mirror unit, and instantiate the optical layer service optimization model and the optical layer service simulation model to complete the optimization of the optical layer service. According to the optimization results, the optical layer service simulation is performed again. The network service unit further simulates the optical layer energy consumption model according to the optimization and simulation results (the process is the same as the optical layer prediction model). If the simulation is valid, a connection configuration request is sent to the customer context of the controller, such as a create / delete connection request carrying a time series. After the controller completes the connection configuration, the network service unit reports the configuration result returned by the customer context to the upper-layer application.

[0192] Please refer to FIG14 , which shows an electronic device provided in an embodiment of the present application. The electronic device 900 includes but is not limited to:

[0193] at least one processor 910;

[0194] at least one memory 920, for storing at least one program;

[0195] When at least one program is executed by at least one processor 910 , the network management method described in any of the above embodiments is performed.

[0196] It should be understood that the processor 910 and the memory 920 may be connected via a bus or other means.

[0197] It should be understood that the processor 910 can be a central processing unit (CPU). The processor can also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. Alternatively, the processor 910 uses one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0198] Memory 920, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs, such as the network management method described in any embodiment of this application. Processor 910 implements the aforementioned network management method by executing the non-transitory software programs and instructions stored in memory 920.

[0199] The memory 920 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store and execute the above-mentioned network management method. In addition, the memory 920 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 920 may optionally include a memory remotely located relative to the processor 910, and these remote memories may be connected to the processor 910 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0200] The non-transient software programs and instructions required to implement the above-mentioned network management method are stored in the memory 920. When executed by one or more processors 910, the network management method provided by any embodiment of the present application is executed.

[0201] An embodiment of the present application further provides a computer-readable storage medium, which stores a program executable by a processor. When the program executable by the processor is executed by the processor, it is used to implement the network management method described in any of the above embodiments.

[0202] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media.Computer-readable media can be computer-readable signal media or computer-readable storage media.Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or components, or any combination thereof.More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination thereof.In this document, computer-readable storage media can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0203] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0204] Program code embodied on a computer 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.

[0205] Computer program code for performing the operations of the present application can be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (such as through the Internet using an Internet service provider).

[0206] The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the above implementation mode. Technical personnel familiar with the field can also make various equivalent modifications or substitutions without violating the essence of the present application. These equivalent modifications or substitutions are all included in the scope defined by the present application.

Claims

1. A network management method, applied to a digital twin system, wherein the digital twin system includes at least one network service model, and the method includes: Receive a network service request sent by a requesting end, determine target network entity data required to execute the network service request, and obtain a target service model corresponding to the network service request, wherein the target service model is a model in the at least one network service model; The target network entity data is input into the target service model to obtain a service result corresponding to the network service request.

2. The method according to claim 1, wherein: The network service request includes at least one of the following: a simulation service request, a prediction service request, a tracing service request, an optimization service request or a backtracking service request.

3. The method according to claim 1, wherein: Before the receiving of the network service request sent by the requesting end, the method further comprises: collecting network entity data from the controller and / or the network entity, and forming real-time network entity data and historical network entity data according to the collected network entity data, wherein the network entity comprises a physical network entity and / or a virtual network entity; The determining of the target network entity data required to execute the network service request includes: The target network entity data required for executing the network service request is acquired from the real-time network entity data and / or the historical network entity data.

4. The method according to claim 3, wherein: The network entity data includes at least one of the following: resource data, configuration data, alarm data or performance data.

5. The method according to claim 2, wherein: The digital twin system is connected to at least one of a controller and an upper-layer application; the controller includes one or more interaction contexts; the requesting end is any one of the interaction contexts, or the requesting end is an upper-layer application.

6. The method according to claim 5, wherein: The interaction context includes a client context and a service context, wherein the client context is connected to the upper layer application, and the service context is connected to at least one of a physical network and a lower layer controller.

7. The method according to claim 6, wherein: Before receiving the network service request sent by the requesting end, the method further includes: Performing basic information interaction with the controller to establish a communication connection with the controller, wherein the content of the basic information interaction includes at least one of the following: communication protocol, communication parameters, authentication information, authorization information, and namespace; Perform capability interaction with the controller to obtain network service capabilities, wherein the content of the capability interaction includes at least one of the following: a customer context identifier of the controller, a service context identifier of the controller, information provided by the controller, network resources of the controller, a service identifier of the digital twin system, or network resources of the digital twin system.

8. The method according to claim 6, wherein: The controller is configured to collect network entity data from the network entity through the service context, and send the collected network entity data to the digital twin system.

9. The method according to claim 6, wherein: The controller is configured to: Receiving a connection request initiated by the upper layer application through the client context; A connection path is determined according to the connection request.

10. The method according to claim 9, wherein: The service request includes a routing protocol simulation service request, and the controller is further configured to: The service request is generated as a routing protocol simulation service request according to the connection path through the customer context, and the routing protocol simulation service request is sent to the digital twin system so that the digital twin system determines the service result corresponding to the routing protocol simulation service request.

11. The method according to claim 10, wherein: The controller is further configured to: when the service result corresponding to the routing protocol simulation service request is a success result, perform network connection configuration on the network entity through the service context.

12. The method according to claim 9, wherein: The service request includes a connection configuration simulation service request, and the controller is further configured to: The connection configuration simulation service request is generated according to the connection path through the service context, and the connection configuration simulation service is sent to the digital twin system so that the digital twin system determines the service result corresponding to the connection configuration simulation service.

13. The method according to claim 12, wherein: The controller is further configured to: when the service result corresponding to the connection configuration simulation service is a success result, perform network connection configuration on the network entity through the service context.

14. The method according to claim 6, wherein: After obtaining the service result corresponding to the network service request, the method further includes: If the service result is a success result, sending a connection configuration request to the client context of the controller, so that the service context of the controller performs network connection configuration on the network entity and returns a connection configuration result; The connection configuration result corresponding to the connection configuration request is received from the client context of the controller.

15. The method according to claim 1, wherein: The at least one network service model includes at least one of the following: a network-level model, a network element-level model, or a device-level model.

16. The method according to claim 15, wherein: The network-level model, the network-element-level model and the device-level model respectively include a plurality of models corresponding to different network service types.

17. The method according to claim 16, wherein: The network service type includes at least one of the following: a simulation service type, a prediction service type, a tracing service type, an optimization service type or a backtracking service type.

18. The method according to claim 1, wherein: The network service request carries service parameters, and the service parameters are used to instruct the digital twin system to determine the target network entity data required to execute the network service request, and to obtain the target service model corresponding to the network service request; The service parameter includes at least one of the following parameters: a service identifier, a service policy parameter, a constraint condition parameter or a time series parameter.

19. The method according to claim 1, wherein: The number of the target service models is multiple. After obtaining the target service model corresponding to the network service request, the method further includes: Arranging the plurality of target service models according to a preset association relationship to determine a sequence relationship between the plurality of target service models; The arranging of the plurality of target service models according to the preset association relationship includes at least one of the following: hierarchically arranging the plurality of target service models according to the network structure or network topology; The plurality of target service models are hierarchically orchestrated according to the life cycle of the network service.

20. A network management method, applied to a controller, the method comprising: Send network service requests to the digital twin system; Receiving a service result returned by the digital twin system according to the network service request; Execute corresponding network operations according to the service result.

21. The method according to claim 20, wherein: The network service request includes at least one of the following: a simulation service request, a prediction service request, a tracing service request, an optimization service request or a backtracking service request.

22. The method according to claim 20, wherein: The controller includes one or more interaction contexts, and the network service request is sent by at least one of the interaction contexts.

23. The method according to claim 22, wherein: The interaction context includes a client context and a service context, wherein the client context is connected to an upper layer application, and the service context is connected to at least one of a physical network and a lower layer controller.

24. The method of claim 22, further comprising: Collecting network entity data from the network entity through the service context, and sending the collected network entity data to the digital twin system, so that the digital twin system forms real-time network entity data and historical network entity data according to the network entity data, and determines the target network entity data required to execute the network service request from the real-time network entity data and / or the historical network entity data; The network entity includes a physical network entity and / or a virtual network entity.

25. The method of claim 22, further comprising: Performing basic information interaction with the digital twin system to establish a communication connection with the digital twin system, wherein the content of the basic information interaction includes at least one of the following: communication protocol, communication parameters, authentication information, authorization information, and namespace; Perform capability interaction with the digital twin system so that the digital twin system obtains network service capabilities, wherein the content of the capability interaction includes at least one of the following: a customer context identifier of the controller, a service context identifier of the controller, information provided by the controller, the network resources of the controller, the service identifier of the digital twin system, or the network resources of the digital twin system.

26. The method of claim 23, wherein: The service request includes a routing protocol simulation service request, and sending a network service request to the digital twin system includes: Receiving a connection configuration request initiated by an upper layer application through the client context; Determine a connection path according to the connection configuration request; The service request is generated as a routing protocol simulation service request according to the connection path through the customer context, and the routing protocol simulation service request is sent to the digital twin system so that the digital twin system determines the service result corresponding to the routing protocol simulation service request.

27. The method according to claim 26, wherein: The performing corresponding network operations according to the service result includes: When the service result corresponding to the routing protocol simulation service request is a success result, a network connection configuration is performed on the network entity through the service context.

28. The method of claim 23, wherein: The service request includes a connection configuration simulation service request, and sending a network service request to the digital twin system includes: Receiving a connection configuration request initiated by an upper layer application through the client context; Determine a connection path according to the connection configuration request; The connection configuration simulation service request is generated according to the connection path through the service context, and the connection configuration simulation service is sent to the digital twin system so that the digital twin system determines the service result corresponding to the connection configuration simulation service.

29. The method according to claim 28, wherein: The performing corresponding network operations according to the service result includes: When the service result corresponding to the connection configuration simulation service is a success result, the network connection configuration is performed on the network entity through the service context.

30. The method of claim 23, further comprising: receiving, through the client context, a connection configuration request sent by the digital twin system; Performing network connection configuration on the network entity according to the connection configuration request through the service context, and returning a connection configuration result to the client context; The connection configuration result is sent to the digital twin system through the customer context.

31. A digital twin system, comprising a network service unit, a network simulation unit and a network mirror unit, wherein: The network mirroring unit is used to collect network entity data; The network simulation unit includes at least one network service model; The network service unit is used to receive a network service request sent by a requesting end, determine target network entity data required to execute the network service request from the network mirroring unit, and determine a target service model corresponding to the network service request from the network simulation unit, wherein the target service model is a model in the at least one network service model; The network simulation unit is used to input the target network entity data into the target service model to obtain the service result corresponding to the network service request.

32. An electronic device comprising: one or more processors; A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the network management method as described in any one of claims 1-19, or implement the network management method as described in any one of claims 20-30.

33. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the program implements the network management method according to any one of claims 1 to 30, or implements the network management method according to any one of claims 20 to 29.

Images