Network management method, electronic equipment and computer readable storage medium

Abstract

The invention provides a network management method, electronic equipment and a computer readable storage medium, and the method comprises the steps that a digital twin system receives a network service request sent by a request end, determines target network entity data required for executing the network service request, and obtains a target service model corresponding to the network service request; and inputting the target network entity data into the target service model to obtain a service result corresponding to the network service request. According to the embodiment of the invention, at least one network service model is deployed in the digital twin system to construct the digital twin corresponding to the network entity, and the state of the network entity is predicted or monitored according to the service result of the target service model in the digital twin system for the target network entity data, so that the behavior and performance of the network entity are simulated. And service support is provided for the self-intelligent bearer network.

Description

Technical Field

[0001] 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

[0002] The bearer network is the infrastructure of the communication network and the network foundation that supports the digital transformation of thousands of industries. Users have higher requirements for the performance and reliability of the bearer network. As the application scale of the bearer network continues to grow, the operation and maintenance of the bearer network throughout its life cycle is becoming increasingly complex. Traditional operation and maintenance methods can no longer adapt to the scale growth of business and are difficult to support efficient management and control. Therefore, the bearer network needs to develop in the direction of a self-intelligent network throughout its life cycle. The self-intelligent bearer network should have accurate perception, automatic reasoning, decision-making and verification functions, but the trial and error cost of network entities is too high to support the above functions of the self-intelligent bearer network. Summary of the invention

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

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

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

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

[0007] In a second aspect, an embodiment of the present application provides a network management method, which is applied to a controller, and the method includes:

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

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

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

[0011] 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 mirroring unit, wherein:

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

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

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

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

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

[0017] one or more processors;

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

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

[0020] 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 request end that sent the network service request. The scheme of the embodiment of the present application predicts or monitors the status of the network entity according to 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

[0021] Figure 1 It is a schematic diagram of the target framework of the self-intelligence network;

[0022] Figure 2 It is an exemplary architecture diagram of a control system;

[0023] Figure 3 is a schematic diagram of an exemplary architecture of an SDN controller;

[0024] Figure 4 It is a schematic diagram of the architecture of a network management system provided in an embodiment of the present application;

[0025] Figure 5a It is a schematic diagram of a specific architecture of a network management system provided by an embodiment of the present application;

[0026] Figure 5b It is a schematic diagram of a specific architecture of another network management system provided in an embodiment of the present application;

[0027] Figure 6 It is a flowchart of a network management method provided by an embodiment of the present application;

[0028] Figure 7 It is a schematic diagram of the service model deployment of the digital twin system provided in the embodiment of the present application;

[0029] Figure 8 It is a flowchart of a network management method provided by an embodiment of the present application;

[0030] Fig. 9 is an interactive schematic diagram of a network management system provided in Example 1 of the present application;

[0031] Fig.10 is an interactive schematic diagram of a network management system provided in Example 2 of the present application;

[0032] Fig.11 is an interactive schematic diagram of a network management system provided in Example 3 of the present application;

[0033] Fig.12 is an interactive schematic diagram of a network management system provided in Example 4 of the present application;

[0034] Fig.13 is an interactive schematic diagram of a network management system provided in Example 5 of the present application;

[0035] Fig.14 It is a schematic diagram of the architecture of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] 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 in conjunction with the accompanying drawings.

[0037] 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 being limited to the embodiments set forth herein. On the contrary, the purpose of providing these embodiments is to make this application thorough and complete, and will enable those skilled in the art to fully understand the scope of this application.

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

[0039] The terms used herein are only used to describe specific embodiments and are not intended to limit the present application. As used herein, the singular forms "a", "an" and "the" are also 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, the presence of features, wholes, steps, operations, elements and / or components is specified, but the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof is not excluded.

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

[0041] In the description of the embodiments of the present application, any embodiment or design scheme of "exemplary", "for example" or "for example" should not be understood as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0042] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. The terms "include", "comprises", "has" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

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

[0044] Bearer network:

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

[0046] Self-Intelligence Network:

[0047] The self-intelligent network is responsible for the planning, construction, maintenance, optimization, operation and other operational management aspects of the bearer network, such as Figure 1 As shown in the figure, it is a schematic diagram of the target framework of the self-intelligent network. In the target framework of the self-intelligent network, a four-layer three-closed-loop network architecture is constructed, which evolves in the direction of informatization, automation and intelligence.

[0048] The four management levels include:

[0049] Network element management: Provides self-intelligent operation and maintenance capabilities built into network elements.

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

[0051] Business management: Provides cross-disciplinary self-intelligent operation and maintenance capabilities for networks and businesses.

[0052] Business management: Provide customer-oriented self-intelligent service management capabilities and provide unified customer touchpoints.

[0053] The three types of closed loops include:

[0054] Resource closed loop: Single-professional resource management to achieve single-domain autonomy.

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

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

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

[0058] Digital Twin:

[0059] Digital twin refers to the technology of virtual simulation and modeling of entities (such as products, systems, processes or entire organizations) through digital models and entity data. It combines information such as the physical characteristics, behavior and performance of the entity with the digital model to create a digital copy or mirror of the entity.

[0060] Control system:

[0061] Management Control Continuum (MCC) integrates essentially the same management functions and control functions to achieve unified management and control of transmission resources and provide comprehensive management and control services for upper-level users. Software Defined Network (SDN) controllers, element management systems (EMS), network management systems (NMS) and control planes are all examples of management and control systems. Functional modules in the management and control system provide functional services through interfaces.

[0062] Connection scheduling is a basic function of the control system. Figure 2 The figure shows an exemplary architecture diagram of a management and control system. Figure 2 The components in the management and control system and the interaction sequence for connection establishment are shown. The components include: Network call controller NCC (Network call controller), connection controller CC (Connection controller), routing controller RC (Routing controller), link resource manager LRM (Link Resources Manager), termination and adaptation performer (TAP) components, etc., as well as forwarding plane network elements.

[0063] The link topology and resource usage information in the controller are stored in the resource database (RDB).

[0064] 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 and control; from the perspective of the forwarding plane, the FP / FwEP resources in the forwarding plane network element are used.

[0065] A group of SNPs is represented as a SNPP (Subnetwork Point Pool), the association between different SNPPs is represented as a 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 the boundary and the interface between control components.

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

[0067] like Figure 2 As shown, 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 in the controller. The connection request may also carry part or all of the routing information of the connection. 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 satisfies the CC request based on the topology and local connection status information provided by the LRM (5). If the CC request carries the routing information of the connection, the routing information of the connection can also participate in the routing query of the RC. The RC returns the routing information to the CC. 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 customer that the connection is successfully established.

[0068] Take the SDN controller as an example of the control system. Figure 3 FIG. 1 shows an exemplary architecture diagram of an SDN controller. Figure 3 As shown, in the SDN controller hierarchy, the upper and lower controllers form a client layer and service layer relationship; the client layer controller and the service layer controller interact through an interaction context, wherein 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 the administrator to manage and control the controller, and exercises the administrator role within the controller, including maintaining the life cycle of the client context and service context.

[0069] For resource management control within the SDN controller, the resources of the service context can be the resources of the forwarding plane directly controlled by the local controller, or the 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 controller and context refer to SNP / SNPP / SNPP Link, and the resources in the forwarding plane refer to FP / FwEP. A group of SNPs combined together are represented as SNPP (Subnetwork Point Pool), the association between different SNPPs is represented as SNPP Link, the SNP identifier represents an instance of SNP, and the SNPP identifier represents an instance of SNPP. The boundary resource identifier (Boundary Resource Identifier, BRI) is used at the domain boundary to identify the transmission resources at the boundary and the interface between the control components.

[0070] It is understandable that the bearer network is the infrastructure of the communication network and the network foundation that supports the digital transformation of thousands of industries. Users have higher requirements for the performance and reliability of the bearer network. As the application scale of the bearer network continues to grow, the full life cycle operation and maintenance of the bearer network is becoming increasingly complex. The traditional operation and maintenance methods can no longer adapt to the scale growth of the business and are difficult to support efficient management and control. Therefore, the bearer network needs to develop in the direction of self-intelligent network throughout its life cycle. However, it is difficult to implement historical data backtracking, low-cost trial and error, and prediction functions in physical network entities to support the accurate perception, automatic reasoning, decision-making, verification, etc. of the self-intelligent bearer network. Therefore, it is necessary to build a digital twin system to achieve virtual-real interaction with the physical network. At the same time, it is necessary to clarify the interactive relationship between the digital twin network and the existing management and control system to solve the above problems.

[0071] See also Figure 4 , Figure 4 Schematic diagram of the architecture of a network management system provided by an embodiment of the present application. Figure 4 As shown, 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 communicatively connected with the controller and the digital twin system respectively, the network entity is communicatively connected with the controller and the digital twin system respectively, and the controller and the digital twin system are communicatively connected with each other.

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

[0073] See also Figure 5a , Figure 5a This is a schematic diagram of a specific architecture of the network management system provided by the embodiment of the present application. Figure 5a In the network management system shown, 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:

[0074] 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 the relationship between entities.

[0075] Network simulation includes establishing analysis and behavior models for network entities based on various data of network mirroring, which can include device-level, network element-level and network-level models.

[0076] Based on various data in the network image and models in the network simulation, network services select appropriate models for model orchestration / calling and instantiation according to externally requested services to complete the requested services, which may include simulation, prediction, tracing, backtracking and optimization services.

[0077] The controller and / or upper-layer application 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 application 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 customer context identifier and service context identifier of the controller, the information (performance alarms and configuration, etc.) and network resources provided by the controller, the function or service identifier of the digital twin system, the network resources of the digital twin system, etc.

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

[0079] See also Figure 5b , Figure 5b It is another specific architecture diagram of the network management system provided in an embodiment of the present application. Figure 5b The network management system shown is compared Figure 5a The network management system shown in the figure is different in that the controller also includes a management context. The capability negotiation or configuration of the control system and the digital twin system can be completed through the management context.

[0080] It should be noted that the network management system embodiments described above are only illustrative. For example, the division of units or components is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be realized through some interfaces.

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

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

[0083] It should be noted that 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 the corresponding boundary resource identifier, relevant policies, constraints, time series and other information, and the controller returns the corresponding connection configuration result. Exemplarily, the connection configuration request can be a create connection request, a delete connection request or a modify connection configuration request.

[0084] Combine the following Figure 4 , Figure 5a or Figure 5b The architecture of the network management system shown illustrates the network management method provided in the embodiment of the present application.

[0085] See also Figure 6 , Figure 6 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, the digital twin system includes at least one network service model, such as Figure 6 As shown, the network management method includes the following steps:

[0086] Step S110, receiving a network service request sent by a requesting end.

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

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

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

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

[0091] 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 the network entity, and forming real-time network entity data and historical network entity data based on the collected network entity data.

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

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

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

[0095] 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 respectively included in various data categories.

[0096] Table 1

[0097]

[0098]

[0099] Step S130, 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 mentioned above.

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

[0101] Table 2

[0102]

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

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

[0105] Table 3

[0106]

[0107]

[0108] See also Figure 7 , Figure 7 A schematic diagram of the service model deployment of the digital twin system provided in the embodiment of the present application. Figure 7 As shown in the figure, network-level models, network element-level models and device-level models are deployed in the digital twin system. In addition, the network-level models, network element-level models and device-level models include simulation service type models, prediction service type models, traceability service type models, optimization service type models and backtracking service type models respectively.

[0109] like Figure 7 As shown, the network-level model may include a constant bit rate (CBR) service model, an optical transform unit (OTU) model, and an optical layer model. The CBR service model, the OTU model, and the optical layer model are respectively deployed with a simulation service type model, a prediction service type model, a traceability service type model, an optimization service type model, and a backtracking service type model 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.

[0110] like Figure 7As shown, the network element level model may include a network element model, a single board model, and a port model. The network element model, the single board model, and the port model are respectively deployed with a simulation service type model, a prediction service type model, a traceability service type model, an optimization service type model, and a backtracking service type model 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 port simulation model includes a port protocol simulation model, a port energy consumption simulation model, and a port fault simulation model.

[0111] like Figure 7 As shown, the device-level model may include a service chip model, an optical device model, and an optical fiber model. The service chip model, the optical device model, and the optical fiber model are respectively deployed with a simulation service type model, a prediction service type model, a traceability service type model, an optimization service type model, and a backtracking service type model 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 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.

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

[0113] 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, tracing service, optimization service or backtracking service.

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

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

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

[0117] In a specific embodiment, the service parameter includes a constraint parameter, and the constraint parameter includes an object constraint parameter. The object constraint parameter is used to indicate the object executed by the network service request. 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 single board (network element level); for another example, the execution object of the current network service request is the first optical device (device level).

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

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

[0120] When the execution level is the device level, determine the target device corresponding to the object constraint parameter, use the network entity data corresponding to the target device as the target network entity data, and select the corresponding device level model as the target service model according to the target device;

[0121] 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. According to the target device associated with the target network element, a corresponding device-level model can be selected to form a network element-level model, and the network element-level model is used as the target service model;

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

[0123] Exemplarily, 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, it is possible to combine the virtual network / virtual network element according to its abstraction level, and directly use the data of the edge access point of the virtual network / virtual network element 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.

[0124] 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, a 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.

[0125] In another specific embodiment, according to 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, according to 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.

[0126] In another specific embodiment, according to 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, according to 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.

[0127] It is understandable that each network simulation model of the digital twin system has the ability to simulate independently. Combined with the needs of the application scenario, the relationship between network simulation models is analyzed according to the data flow direction to complete the data transfer between the simulation models; by setting the online simulation timing of the simulation model, various simulation tasks are serialized to achieve the arrangement of the digital twin model. The results of the twin model arrangement can be saved in a file for later reading. The digital twin system will allocate memory and computing resources for the arranged model and create a digital twin model instance.

[0128] Exemplarily, there are multiple target service models. After obtaining the target service model corresponding to the network service request, the network management method of the 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.

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

[0130] 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 topological 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 one or more services requested externally, such as closed-loop operations such as prediction, optimization, and simulation, or it can make a vertical call based on the services requested externally, such as selecting part of the network element-level energy consumption model according to the strategy 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 externally, different levels of energy consumption models such as network level, network element level, and device level can be selected to provide services.

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

[0132] For example, the digital twin system receives a network service request, determines the service type requested by the network service request as performance backtracking service and performance optimization service according to the service identifier, and determines the execution object scope as the optical layer network according to the constraint condition parameters. Therefore, the optical layer performance backtracking service model and the optical layer performance optimization service model are selected as the target network model, and the optical layer performance backtracking service model and the optical layer performance optimization service model are orchestrated according to the service strategy parameters, and the optical layer performance backtracking service model is orchestrated before the optical layer performance optimization service model. The network entity data required for executing the optical layer performance backtracking service and the optical layer performance optimization service within a week is obtained according to the time series parameters. When executing the network service request, the network entity data required for executing the optical layer performance backtracking service is first input into the optical layer performance backtracking service model, and the optical layer performance backtracking task is executed through the optical layer performance backtracking service model to obtain the optical layer performance backtracking result; then the optical layer performance optimization service model outputs the optical layer performance optimization result based on the optical layer performance backtracking result and the network entity data related to the optical layer performance optimization.

[0133] 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 a physical network and at least one of a lower-layer controller.

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

[0135] The digital twin system performs 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;

[0136] 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 client 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.

[0137] 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, exchanging each other's namespaces, etc. 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, the context identifier of the controller, and 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.

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

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

[0140] Exemplarily, the controller is configured to: receive a connection configuration request initiated by an upper layer application through a client context, and determine a connection path according to the connection configuration request. For example, the connection configuration request carries a boundary resource identifier BRI, and then the BRI is converted into two SNP identifiers in the controller, the connection route between the first and last SNPs is queried, and the path that satisfies the connection configuration request is calculated according to the network topology and local connection status information.

[0141] 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 satisfies the network routing protocol.

[0142] In a specific embodiment, the controller is further configured to: when 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 understandable 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.

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

[0144] 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. It can be understood that after the controller calculates the path of the network connection, 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.

[0145] In a specific embodiment, the controller is further configured to: when the service result corresponding to the connection configuration simulation service is a successful result, perform network connection configuration on the network entity through the service context. It is understandable 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 through the service context based on the path to complete the network connection.

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

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

[0148] 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 customer context of the controller. 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 optimizes the connection configuration of the optical layer service entity according to the connection configuration request, and reports 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.

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

[0150] See also Figure 8 , Figure 8 A flow chart of a network management method provided in an embodiment of the present application is provided. The network management method is applied to a controller, such as Figure 8 As shown, the network management method includes the following steps S210-S230:

[0151] Step S210, sending a network service request to the digital twin system.

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

[0153] Exemplarily, the controller includes one or more interaction contexts. Among them, the interaction context can be at least one of the customer context and the service context, and the network service request is sent by at least one of the customer context and the service context. In other words, both the customer context and the service context can send network service requests to the digital twin system, and the customer context and the service context can send network service requests to the digital twin system at the same time.

[0154] Step S220, receiving the service result returned by the digital twin system based on the network service request.

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

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

[0157] Exemplarily, the network management method of the 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 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. Wherein, the network entity includes a physical network entity and / or a virtual network entity.

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

[0159] The controller performs 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;

[0160] 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 client 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.

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

[0162] Receive a connection configuration request initiated by an upper-layer application through a client context;

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

[0164] A service request is generated according to the connection path through the customer context as a routing protocol simulation service request, 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.

[0165] Exemplarily, performing corresponding network operations 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.

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

[0167] Receive a connection configuration request initiated by an upper-layer application through a client context;

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

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

[0170] 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 success result, performing network connection configuration on the network entity through the service context.

[0171] 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 a customer context; performing connection configuration according to the connection configuration request through a 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.

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

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

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

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

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

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

[0178] The scheme of the embodiment of the present application is explained below through specific embodiments.

[0179] Example 1

[0180] See also Fig. 9 , Fig. 9Schematic diagram of the interaction of the network management system provided in Example 1 of the present application. Fig. 9 As shown in the figure, the interaction process of the network management system includes:

[0181] The controller and the digital twin system negotiate or are configured with the interaction-related contract / parameter and other capability information (11), such as authentication and authorization of service context and data processing, communication protocol and namespace. The capability negotiation or configuration of the controller and the digital twin system can be completed through the management role; the service context of the controller collects data of various entities / objects from the network entity (12) and transmits it to the network mirror unit (12) of the digital twin system. The data may include alarm, performance, network topology and configuration data. The network mirror unit also collects data of various entities / objects from the network entity (12). The above 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 and backed up to real-time data and historical data with timestamp identification. 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 an optical module backtracking model, and arranges or calls the model (16). The network service unit triggers the network simulation unit to instantiate 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.

[0182] Example 2

[0183] See also Fig.10 , Fig.10 Schematic diagram of the interaction of the network management system provided in Example 2 of the present application. Fig.10 As shown in the figure, the interaction process of the network management system includes:

[0184] 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 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 can complete the configuration simulation of the forwarding plane. The upper-layer application sends a connection configuration request (22) to the client context of the controller. The controller calculates the connection path according to the connection configuration request (22) (23), 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 port, switching or cross-type, time slot and time series of the network element. The network service unit selects a suitable model to complete the model arrangement or call (25), such as the network element-level connection simulation model, and triggers the network simulation unit to instantiate the connection model according to the data of the relevant entity reported by the network mirror unit (26), thereby completing the connection configuration simulation of the network element (27) and returning the simulation result (28). If the simulation result (28) is a failure result, the service context of the controller responds to the client context with a failure, otherwise, the configuration of the physical network is completed and the connection configuration result is responded to the client context (29).

[0185] Example 3

[0186] See also Fig.11 , Fig.11 Schematic diagram of the interaction of the network management system provided in Example 3 of the present application. Fig.11 As shown in the figure, the interaction process of the network management system includes:

[0187] 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 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 routing protocol simulations on the forwarding plane. The capability negotiation or configuration of the controller and the digital twin system can be completed through management roles. The controller receives a connection configuration request from an upper-layer application, such as receiving a connection configuration request to the controller's customer context (32). The controller performs connection path calculation (33). The customer The context requests the 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 orchestration or call of the simulation model (35), and triggers the network simulation unit to instantiate the routing simulation model according to 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 to configure the connection, completes the configuration of the physical network and responds to the configuration result (39).

[0188] Example 4

[0189] See also Fig.12 , Fig.12 Schematic diagram of the interaction of the network management system provided in Example 4 of the present application. Fig.12 As shown in the figure, the interaction process of the network management system includes:

[0190] 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 namespace, 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 the network service unit for service optimization (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.

[0191] Example 5

[0192] See also Fig.13 , Fig.13 Schematic diagram of the interaction of the network management system provided in Example 5 of the present application. Fig.13 As shown in the figure, the interaction process of the network management system includes:

[0193] The digital twin system and the controller negotiate or are configured with the contract / parameters and other capabilities related to interaction. They can also be negotiated or 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, such as network-level optical layer energy consumption prediction / optimization / simulation services. The upper-layer application requests the required services from the network service unit, and the network service selects a suitable model for model orchestration or call, such as selecting the energy consumption prediction model of the optical device in the network simulation for orchestration or call to build a network element-level and network-level optical layer energy consumption prediction model, and trigger the network simulation unit to obtain energy consumption-related data from the mirror network unit, instantiate the above model, and complete the prediction of network-level optical layer energy consumption. According to the prediction results, if hidden dangers are identified, it is necessary to optimize the optical layer resources, such as concentrating the channel resources of the optical layer service 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, instantiate the optical layer service optimization model and the optical layer service simulation model to complete the optimization of the optical layer service, and then perform optical layer service simulation based on the optimization results. The network service unit further simulates the optical layer energy consumption model based on 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.

[0194] See also Fig.14 , is an electronic device provided in an embodiment of the present application, and the electronic device 900 includes but is not limited to:

[0195] at least one processor 910;

[0196] At least one memory 920, used to store at least one program;

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

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

[0199] It should be understood that the processor 910 may be a central processing unit (CPU). The processor may 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 gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. Alternatively, the processor 910 may be one or more integrated circuits for executing related programs to implement the technical solutions provided in the embodiments of the present application.

[0200] The memory 920 is a non-transitory computer-readable storage medium that 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 the present application. The processor 910 implements the above-mentioned network management method by running the non-transitory software programs and instructions stored in the memory 920.

[0201] 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 an application 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 arranged 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.

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

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

[0204] 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 devices, or any combination of the above. More specific examples (non-exhaustive lists) 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-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. 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.

[0205] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0206] The program code embodied on the 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.

[0207] Computer program code for performing the operations of the present application may 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 may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may 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 may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0208] The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the above-mentioned implementation mode. Technical personnel familiar with the field can also make various equivalent modifications or substitutions without violating the spirit 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that: 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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 according to claim 22, characterized in that The method further comprises: 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 according to claim 22, characterized in that The method further comprises: 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 according to claim 23, characterized in that 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, characterized in that 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 according to claim 23, characterized in that 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, characterized in that 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 according to claim 23, characterized in that The method further comprises: 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