WO2025076687A1

WO2025076687A1 - Systems and methods for orchestrating a network digital twin map

Info

Publication number: WO2025076687A1
Application number: PCT/CN2023/123747
Authority: WO
Inventors: Baoguo Xie
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2023-10-10
Filing date: 2023-10-10
Publication date: 2025-04-17
Anticipated expiration: 2026-04-10

Abstract

Presented are systems and methods for orchestrating a network digital twin map. A network digital twin map orchestration (NDTMO) may receive from a digital twin verification control (DTVC), a request to orchestrate a digital twin (DT) map. The NDTMO may determine whether to acquire a model of the DT map corresponding to the request, from a knowledge graph system (KGS). The NDTMO may orchestrate the DT map.

Description

SYSTEMS AND METHODS FOR ORCHESTRATING A NETWORK DIGITAL TWIN MAP

TECHNICAL FIELD

The disclosure relates generally to wireless communications, including but not limited to systems and methods for orchestrating a network digital twin map.

BACKGROUND

In the conventional telecommunications field, there is no mechanism or system for constructing a network map composed of available components, topology, capability, and function, that serves as a flexible virtual representation of the physical network.

SUMMARY

The example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.

At least one aspect is directed to a system, method, apparatus, or a computer-readable medium. A network digital twin map orchestration (NDTMO) may receive from a digital twin verification control (DTVC) , a request to orchestrate (e.g., establish, create, update, assemble) a digital twin (DT) map. The NDTMO may determine whether to acquire a model of the DT map corresponding to the request, from a knowledge graph system (KGS) . The NDTMO may orchestrate the DT map.

In some embodiments, orchestrating the DT map includes the NDTMO determining an arrangement or rearrangement of at least one component of the DT map, using the model of the DT map or an existing instance of the DT map. At least one component of the DT map may comprise at least one of: at least one network element of the model, at least one network function of the model, a network topology of the model, performance of the model, or at least one resource allocation for the at least one network element or the DT map.

In certain embodiments, the NDTMO may determine the model of the DT map to acquire, according to a type of scenario indicated by the request. The NDTMO may determine the model of the DT map to acquire, according to a type of task indicated by the request. In certain embodiments, the NDTMO may determine the model of the DT map to acquire according to a type of service indicated by the request. In certain embodiments, the NDTMO may determine the model of the DT map to acquire, according to a type of intent indicated by the request. A DT application may send a request to the DTVC. The request may indicate a request type. In certain embodiments, the DTVC may determine, according to the request, at least one requirement for the DT map and the request type.

In some implementations, the request to orchestrate the DT map may comprise an indication of a type of scenario. The request to orchestrate the DT map may comprise an indication of a type of task. The request to orchestrate the DT map may comprise an indication of a type of service. The request to orchestrate the DT map may comprise an indication of a type of intent. The request to orchestrate the DT map may comprise an indication of at least one requirement for the DT map.

In some embodiments, the NDTMO determines whether to acquire the model of the DT map, which can include at least one of the following. The NDTMO can determine, according to a request type of the request, whether an instance of the DT map exists. The NDTMO can determine to acquire the model of the DT map from the KGS, when the instance does not exist. The NDTMO can determine to reuse or update the instance of the DT map, when the instance exists.

In certain embodiments, the digital twin management (DTM) acquires a network element (NE) model, a function model, and/or a topology model from the KGS according to the arrangement or rearrangement of the at least one component of the DT map. The DTM establishes an instance of the DT map according to the NE model, the function model, and/or the topology model. The DTM allocates at least one resource for the instance. The DTM configures or modifies at least one service parameter of the instance. The digital twin management (DTM) can update the existing instance of the DT map according to the arrangement or rearrangement of the at least one component of the DT map. The DTM can allocate at least one resource for the instance. The DTM can configure or modify at least one service parameter of the instance.

In some implementations, the DTVC sends a request message to the DTM to perform digital twin simulation and/or verification on the instance. The DTM may perform the digital twin simulation and/or verification on the instance, according to at least one requirement. The DTM can send to the DTVC a report on the simulation and/or verification. In certain implementations, the NDTMO can operate with the DTVC and/or the DTM to iteratively update the instance and/or perform the simulation and/or verification, until requirements of the DT application are satisfied. The DTVC can send to the DT application a final result of the simulation and/or verification.

At least one aspect is directed to a system, method, apparatus, or a computer-readable medium. In some embodiments, a digital twin verification control (DTVC) may send to a network digital twin map orchestration (NDTMO) a request to orchestrate a digital twin (DT) map. The NDTMO may determine whether to acquire a model of the DT map corresponding to the request. The NDTMO may orchestrate the DT map.

BRIEF DESCRIPTION OF THE DRAWINGS

Various example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for purposes of illustration only and merely depict example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered limiting of the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure;

FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure;

FIG. 3 illustrates an example DTN architecture/system, in accordance with some embodiments of the present disclosure;

FIG. 4 illustrates an example enhanced DTN architecture/system, in accordance with some embodiments of the present disclosure;

FIG. 5 illustrates an example KGS, in accordance with some embodiments of the present disclosure;

FIG. 6 illustrates an example process for onboarding models of a DT map, in accordance with some embodiments of the present disclosure;

FIG. 7 illustrates an example process of establishing a DT map according to scenario or task type, in accordance with some embodiments of the present disclosure;

FIG. 8 illustrates an example process of establishing a DT map according to service type, in accordance with an embodiment of the present disclosure;

FIG. 9 illustrates an example process of establishing a DT map according to intent (e.g., intent type) , in accordance with an embodiment of the present disclosure;

FIG. 10 illustrates an example for updating a digital twin map instance, in accordance with an embodiment of the present disclosure; and

FIG. 11 illustrates a flow diagram of an example method for establishing or updating a DT map, in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

1. Mobile Communication Technology and Environment

FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100. ” Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101. In FIG. 1, the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126. Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.

For example, the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively. Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128. In the present disclosure, the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.

FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of FIG. 1, as described above.

System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) . The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.

As would be understood by persons of ordinary skill in the art, system 200 may further include any number of modules other than the modules shown in FIG. 2. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

In accordance with some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion. Similarly, in accordance with some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion. The operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.

The UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.

In accordance with various embodiments, the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example. In some embodiments, the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc. The processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this manner, a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.

The network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communication with the base station 202. For example, network communication module 218 may be configured to support internet or WiMAX traffic. In a typical deployment, without limitation, network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network. In this manner, the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC)) . The terms “configured for, ” “configured to” and conjugations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted and/or arranged to perform the specified operation or function.

The Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems. The model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it. The OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols. The OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model. In some embodiments, a first layer may be a physical layer. In some embodiments, a second layer may be a Medium Access Control (MAC) layer. In some embodiments, a third layer may be a Radio Link Control (RLC) layer. In some embodiments, a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer. In some embodiments, a fifth layer may be a Radio Resource Control (RRC) layer. In some embodiments, a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.

Various example embodiments of the present solution are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present solution. As would be apparent to those of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the example embodiments and applications described and illustrated herein. Additionally, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present solution. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless expressly stated otherwise.

2. Systems and Methods for Orchestrating a Network Digital Twin Map

Digital Twins (DTs) can be part of technology relevant to system automation. A digital twin object can be a virtual replica of a real-world system -a “physical” system -on which operations can be performed.

In the telecommunications field, a digital twin network reference architecture and related requirements which can be used for simulation of physical networks can be defined. This disclosure provides solutions on how to build a network digital twin map which can be formed by various components or models (e.g., topology, capability, function) as a flexible virtual mirror for physical networks.

As applied to the communication industry and communication systems (e.g., systems discussed in connection with FIGS. 1 and 2) , digital twin based technology can be used for data collection, element model creation, etc. A fixed network digital twin platform may be designed and used for satisfying digital twin applications (e.g., for simulation) . However, a fixed network digital twin platform that has fixed network elements, topology, and functions, cannot be orchestrated/configured flexibly based on an application’s specific requirements (or updated requirements) . Therefore, such a fixed network digital twin platform may incur unnecessary network resources as such a fixed network digital twin platform cannot be customized/configured accordingly to particular requirements.

Based on the above problem, this disclosure provides systems, methods and solutions to flexibly orchestrate and/or manage a network digital twin map which can be dynamically and efficiently created and/or updated based on specific/changing requirements, and can be used for corresponding network digital twin applications.

Introduction

A digital twin network (DTN) can be an expansion platform for network simulations (e.g., simulations of networks such as communications networks/systems described in connection with FIGS. 1 and 2) . Through real-time data interactions between the physical network and its twin network, the digital twin network can help network designers to perform/achieve more simple, automatic, resilient, and full life-cycle operation and maintenance.

FIG. 3 illustrates an example architecture of a DTN. Referring to a digital twin architecture for industrial domains and combining it with the characteristics of communication networks, the digital twin network can be designed using an architecture with multiple layers (e.g., three layers) . The t layers can include a physical network layer, a network digital twin layer, and/or a network application layer, of a digital twin network system.

The bottom layer of a digital twin network can be a physical network layer. Network elements present in the physical networks can exchange massive network data and/or control information with a network digital twin entity, via southbound interfaces for instance. The physical network can be a telecommunication operator network, data center network, campus network, industrial internet of things network, or a network of another network type. The physical network can be for a single network domain (e.g., access network, transportation network, core network, IP carrier network, etc. ) , or for an end-to-end cross-domain network. In addition, the physical network can either contain all infrastructures in the network or may contain specific infrastructure (e.g., radio spectrum resources, user plane function elements in the core network, etc. ) .

The middle layer of a digital twin network can be a network digital twin layer, which can form the core of the DTN system. This layer can include but is not limited to subsystems: unified data repository, unified data models, and digital twin entity management.

A) Data handling system: by collecting and updating real-time operational data of various network entities through the southbound interface, a single source of truth for the network twin network can be formed, which can provide accurate and/or complete information for various network applications. One or more of the following are responsibilities of a unified data repository.

– Data collection: To complete the extraction, transformation, loading, cleaning, and/or processing of network data. To facilitate large-scale data to achieve efficient distributed storage.

– Data storage: To store the data efficiently with one or more database techniques, according to diversified characteristics of network data, which can include but is not limited to user and/or service data, operational and/or status data and/or log data, network environment and/or configuration data, etc.

– Data service: To provide a variety of data services for the unified data model sub-system, which can include but is not limited to fast retrieval, concurrent conflict, batch service, unified interface, etc.

– Data management: This can include but is not limited to data asset management, data safety management, data quality management, metadata management, etc.

The more complete and accurate the data in the unified data repository is, a more complete and accurate unified data model subsystem can be achieved.

b) Unified data models: For some application scenarios, the unified data model's subsystem can be used to complete data-based modeling, provide model instances for various network applications, and/or maximize the agility and programmability of the network services. To ensure the effectiveness and reliability of change controls to the data models before the change controls are distributed to the physical network, the corresponding model instance can be used to complete the full emulation and verification of one or more of the following objectives in the virtual twin network: the prediction, scheduling, configuration, optimization, etc. The data models can include types such as but not limited to basic models, functional models, etc.

– Basic models of a network digital twin entity can refer to the network element model and/or network topology model. Basic models can be based on but not limited to the basic configuration, environment information, operational state, link topology, and/or other information of the network element, and can be used to complete the real-time accurate description of the physical network. Basic models can be used to help verify and/or emulate control changes and/or optimization solutions to ensure the effectiveness and reliability of the change controls before the change controls are sent to the entity network.

– A functional model can refer to various data models such as but not limited to network analysis, emulation, diagnosis, prediction, assurance, etc. Functional models can be established by making full use of the network data in a unified data repository for application scenarios. The functional models can be constructed and/or expanded by multiple dimensions such as but not limited to:

Network type (e.g., functional models can be models serving for single network domain or multiple network domains) ;

Function type (e.g., functional models can be divided into models that include but is not limited to state monitoring, traffic analysis, security drills, fault diagnosis, quality assurance, etc. ) ;

Generality, (e.g., functional models can be divided into a general model, special-purpose model, etc. ) .

Multiple dimensions can be combined to create a data model for more application scenarios. For example, the traffic balance optimization model can be created on the core switch of one campus network, and the model instance can be used to serve the corresponding network applications.

The more types of data models there are, the more powerful is the ability of DTN to meet the requests and/or requirements of network applications.

c) A digital twin management can be used to complete the management function of the digital twin network, record the life-cycle of the entity, visualize and/or control various elements of the network digital twin (e.g., topology management, model management, security management, etc. ) .

A top layer can be the digital twin application layer. DT applications can input the requirements to the network digital twin layer through the northbound interfaces and can deploy services through modeling instances. After verification, the twin network layer can send the control updates to the physical entity network through the southbound interfaces. Applications can be deployed rapidly with lower cost, higher efficiency, and can have a lower impact on the running of a network business and can include but are not limited to network operation, network maintenance, network optimization, self-driving network, network innovation technology, etc.

Solutions for the identified problem

Example Implementation 1: DTN reference architecture enhancement

FIG. 4 depicts an example of an enhanced DTN system. The DTN architecture (e.g., discussed in connection with FIG. 3) can be enhanced to raise/provide some new functions and capabilities which are integrated in new function blocks or enhanced on existing function blocks. The enhancements can be used to support the orchestration and/or management of the network digital twin map and digital twin application that can be running on the digital twin map instance. In an enhanced DTN system, one or more additional/enhanced function blocks, capabilities, and/or functions can include:

Digital Twin Verification Control: The Digital Twin Verification Control is a device/system that can be used to analyze/parse/interpret the requirements of digital twin applications, which can include but are not limited to configuration requirements of the created digital map and/or application requirements on the digital map. The Digital Twin Verification Control may be responsible for the control of various digital twin capabilities (e.g., scenario-based/type operation, business or service type operation, intent simulation, policy verification, fault prediction, network search, etc. ) .

Network Digital Twin Map Orchestration: The Network Digital Twin Map Orchestration is a device/system that can be responsible for the orchestration and/or life cycle management of network digital twin map instance based on scenarios and requirements which can include but are not limited to the creation, modification, query, and/or deletion of network digital twin map instances.

Digital Twin management: The Digital Twin management is a device/system that can be enhanced to be responsible for building and/or running differentiated network digital map instances (such as, e.g., creating digital twin instances according to arranged/orchestrated basic model and/or functional model, allocating resources to each network digital twin map instance, etc. ) .

FIG. 5 depicts an example Knowledge Graph System (KGS) . The KGS is a device/system that can include data handling functions, various functional model (s) , and/or basic model (s) , and can be enhanced by being responsible for storing/maintaining and/or providing/provisioning various network digital twin digital map models which can be evaluated/assessed and/or used to create digital twin map instances by the network digital twin map orchestration and management.

Implementation Example 2: DT map model on-boarding

In case that the model provider (e.g., Operations and/or Business Support Systems (OSS/BSS) , Vendor) has built the network digital twin map models which can include different models identified as different object types in terms of scenarios and customer’s requirements, the model provider can onboard the network digital twin map model to the KGS. A network digital twin map model can be associated and/or identified with one or more object types (e.g., service type) .

FIG. 6 illustrates an example process for onboarding models of a DT map.

Step 601. After the model provider (e.g., OSS/BSS) has designed/built/established the network digital twin map models in terms of specified scenarios and customer requirements, the model provider can initiate the on-boarding process of the network digital twin map models.

The model provider may request to onboard a DT map model to DTM. The request can include DT map model information, which can have a unique identifier to indicate certain scenarios and/or requirements.

The model provider may onboard the digital twin map model to the KGS directly if there is an interface between the model provider and the KGS.

Step 602. The DTM can check/test/verify the integrity and consistency of the digital twin map model information, and can request to onboard the digital twin map model information to KGS.

Step 603. The KGS can receive and/or can store the digital twin map model information, and may be responsible for the management operations of the digital twin map model, including for instance query, update, deletion, etc. The KGS can send a response to the DTM to indicate that the digital twin map model information is on-boarded successfully, and the DTM can inform the model provider that the digital twin map model information is on-boarded successfully.

Implementation Example 3: Establishing a DT map according to scenario or task type

Digital Twin applications serving communication service customers can have digital twin simulation requirements based on specific scenarios or specific tasks (e.g., antenna optimization for specific base stations, performance improvement for specific network element, fault prediction, network optimization, innovative service deployment verification, etc. ) .

The digital twin verification control function (DTVC) can have the capability to analyze the request (e.g., which may include simulation operation request information) of the digital twin application based on the specific scenarios or specific tasks and/or can decompose the request into one or more specific scenario or specific task types of a network digital twin map to be created, network digital twin map requirements, digital twin application requirements and/or at least one policy for digital twin simulation and/or verification, etc. The digital twin verification control function (DTVC) can request the network digital map management and orchestration function (NDTMO) to perform orchestration and/or perform one or more life cycle management operations for the network digital twin map.

The network digital map management and orchestration function (NDTMO) can be a device/system that can check whether there is an existing digital twin map instance corresponding to a specific scenario or task type. If there is no such existing digital twin map instance, the NDTMO can obtain the network digital twin map model corresponding to specific scenario or task type from the KGS and can configure the corresponding network digital twin map description file based on the network digital twin map requirements.

The digital twin management (DTM) can be a system/device that can instantiate/establish the network digital twin map instance based on the network digital twin map description file. After the digital twin map instance is successfully created, the digital twin verification control function (DTVC) can request the DTM to perform the digital twin application simulation and/or verification operations on the network digital twin map instance in terms of the digital twin application requirements, and can iteratively update and/or iterate the digital twin map instance according to the simulation and/or verification results until the simulation and/or verification results meet the digital twin application requirements.

It should be understood that one or more features from the above/following implementation examples are not exclusive to the specific implementation examples, but can be combined in any manner (e.g., in any priority and/or order, concurrently or otherwise) .

An example procedure of the simulation operation of scenario or task based DT application, as depicted in FIG. 5, is described as follows, FIG. 7 illustrates an example process of establishing a DT map according to scenario or task type.

Step 701. A scenario or task based digital twin application (DT APP) can be to simulate/emulate/perform the task/scenario of network maintenance and/or operation (e.g., network optimization, fault prediction, network fault root cause analysis, location, network visualization, etc. ) . Examples of specific tasks or scenarios can include but are not limited to simulating a certain 5G base station, resource optimization for a network element, verification of a network strategy, innovation industry deployment, etc.

The DT APP can send a request for digital twin simulation and verification operation (which can include information of the digital twin application requirements based on a specific scenario or specific task) to the digital twin verification control function (DTVC) . The DT APP can carry a scenario or task description information in the message.

Step 702. After the request is received, the DTVC can parse and/or translate the request into at least one of digital twin application simulation and/or verification requirements, network digital twin map requirements, the digital twin simulation and/or verification policy, and/or specific scenarios/task type. The specific scenarios/task type can be obtained from the scenario or task description information.

Step 703. The DTVC can initiate orchestration and management of a network digital twin map, at the NDTMO by sending a message to the NDTMO comprising an orchestration and management request. The DTVC can carry the network digital twin map requirements and/or corresponding scenarios/task type in the message.

Step 704. The NDTMO can receive the orchestration and management request of the network digital twin map. The NDTMO can judge whether there is an existing digital twin map instance associated with the corresponding scenario or task type. If there is none, the NDTMO can acquire/obtain the corresponding digital twin map model in terms of the specific scenarios/task type from the KGS. In the case that the KGS does not find a digital twin map model associated with this specific scenario or task type, the KGS can return a universal digital twin map model to the NDTMO with an indication of cause/reason (e.g., that no suitable model is available. The NDTMO can generate digital twin map configuration parameters based on the requirements of the network digital twin map.

Step 705. The NDTMO can define a new network digital twin map object description profile based on obtained digital twin map model and/or one or more digital twin map configuration parameters, in which network elements, network functions, and/or a network topology defined in digital twin map model can be modified and/or tailored based on the orchestration requirements/procedure.

The orchestration for the digital twin map can involve (re) arranging, (re) organizing, (re) programming and/or (re) configuring the components of the digital twin map based on the corresponding digital twin model, and can include at least one of, but not limited to, needed digital twin network elements, network topology, resource allocation for network elements and/or the digital twin map, network function (s) and/or performance of the digital twin map, etc.

The new network digital twin map object description profile can contain at least one of, but not limited to, the needed digital twin network elements, network topology, resource allocation for network elements and/or digital twin map, the network function (s) and/or performance of the digital twin map, etc.

Step 706. The NDTMO can send a request message to request the DTM to instantiate the network digital twin map. The NDTMO can carry/include/convey the relevant network digital twin map object description profile in the request message.

Step 707. The DTM, based on the received network digital twin map object description profile, can acquire/access/receive the NE model, function model, and/or topology model from the KGS, and/or can create the network digital twin map instance. To satisfy the functional and performance requirements of the digital twin map, the DTM can allocate compute/storage/network resources for the instance, and can configure necessary service parameters on the instance. After the network digital twin map instance is created successfully, the DTM can inform the NDTMO that the network digital twin map instance is created successfully.

Step 708. The NDTMO can inform the DTVC that the network digital twin map instance associated with specific scenario or task type is created successfully. The NDTMO can inform the DTVC via a notification message or a response.

Step 709. The DTVC can request the DTM to perform an operation of digital twin simulation and/or verification on the created network digital twin map instance. The DTVC can carry/convey/communicate the digital twin simulation and/or verification requirements and operation policy in the message.

Step 710. The DTM can perform the operation of digital twin simulation and/or verification on the created network digital twin map instance based on the digital twin simulation and/or verification requirements and operation policy. The DTM can report/send the result of digital twin simulation and/or verification (e.g., fault cause, network optimization strategy, possible future fault, etc. ) to the DTVC.

Step 711. If the simulation and/or verification operation (s) does not satisfy/meet the requirements /specification of the digital twin application, the DTVC, the NDTMO and/or the DTM can collaborate/interoperate together to update iteratively the network digital twin instance and the simulation operation policy, and can perform the simulation and verification operation until the result satisfies the needs/requirements/specification of the digital twin application.

The DTVC can report/send the final result of digital twin simulation and verification to the DT APP.

Implementation Example 4: Simulation operation of service based DT application.

A digital Twin application serving communication service customers can have digital twin simulation requirements based on specific communication services (e.g., video service, voice service, conference service, etc. ) . The DTVC can have the capability to analyze the simulation operation request information of the digital twin application based on the specific communication service, and can decompose /parse/translate/interpret the simulation operation request information into at least one of, but not limited to, a specific service type of the network digital twin map, network digital twin map requirements, and/or digital twin application requirements and policy for digital twin simulation and/or verification. The DTVC can request/instruct the NDTMO to perform orchestration and/or life cycle management operations for the network digital twin map.

The NDTMO can check whether there is an existing digital twin map instance corresponding to the specific service type. If there is no existing digital twin map instance available, the NDTMO can obtain/access a network digital twin map model corresponding to the specific service type, from the KGS, and can configure the corresponding network digital twin map description file based on the network digital twin map requirements.

A digital twin management (DTM) can instantiate/establish a network digital twin map instance based on the network digital twin map description file. After the DTM creates the digital twin map instance, the digital twin verification control function (DTVC) can request/instruct/cause the DTM to perform the digital twin application simulation and/or verification operations on the network digital twin map instance in terms of the digital twin application requirements. The DTM can iteratively update and/or iterate the digital twin map instance according to the simulation and/or verification results, until the simulation and/or verification results meet the digital twin application requirements.

An example process of establishing a DT map according to service type as depicted in FIG. 8, is described as follows:

Step 301. The communication service based digital twin application can include, but is not limited to, innovative service deployment applications, service visualization applications, or service performance assurance applications. The communication service can be specified and can include but is not limited to E2E 1Gbps performance assurance for video service, innovative service deployment verification, etc.

The DT APP can send a request message to request a digital twin simulation and/or verification operation, by sending the information of the digital twin application requirements based on a specific communication service, to the digital twin verification control function (DTVC) . The DT APP can carry a communication service description information in the request message.

Step 302. The DTVC can parse/translate the information of the digital twin application simulation and/or verification requirements into the network digital twin map requirements, the digital twin simulation and/or verification requirements and policy, and/or a specific service type. The specific service type can be obtained from the communication service description information.

Step 303. The DTVC can initiate/generate an orchestration and/or management request of the network digital twin map, to send the NDTMO. The DTVC can carry the network digital twin map requirements and/or corresponding service type in the orchestration and/or management request.

Step 304. The NDTMO can receive a orchestration and management request of the network digital twin map from the DVTC, and can judge whether an existing digital twin map instance is associated with the corresponding service type. If none exists, the NDTMO can acquire/obtain/access a corresponding digital twin map model in terms of the specific service type, from the KGS. If the KGS cannot find a digital twin map model associated with this specific service type, the KGS can return a universal digital twin map model to the NDTMO with an indication of the cause/reason (e.g., that no suitable model is available) . The NDTMO can generate digital twin map configuration parameters based on the requirements of the network digital twin map.

Step 305. The NDTMO can define/establish a new network digital twin map object description profile based on the obtained digital twin map model and the digital twin map configuration parameters. The network elements, the network functions, and the network topology defined in the digital twin map model can be modified and tailored based on the orchestration requirements.

The orchestration for the digital twin map can (re) arrange, (re) organize, (re) program and/or (re) configure the components of the digital twin map based on the corresponding digital twin model and can include at least one of: the needed digital twin network elements, the network topology, the resource allocation for network elements and digital twin map, or the network function (s) and/or performance.

The new network digital twin map object description profile may include, but is not limited to, the needed digital twin network elements, the network topology, the resource allocation for network elements and digital twin map, the network function (s) and/or performance of the digital twin map, etc.

Step 306. The NDTMO can send a request message to request the DTM to instantiate the network digital twin map. The NDTMO can carry/include/convey the relevant network digital twin map object description profile in the request message.

Step 307. The DTM can acquire/access/receive the required/suitable NE model, function model, and/or topology model from the KGS, based on the received network digital twin map object description profile. The DTM can create the network digital twin map instance. The DTM, to meet the functional and performance requirements of the digital twin map, can allocate compute/storage/network resources for the instance and can configure the necessary/suitable service parameters on the network digital twin map instance.

Step 308. The DTM can inform the NDTMO that the network digital twin map instance is created.

Step 309. The DTVC can send a message to request the DTM to perform the digital twin simulation and/or verification operation on the created network digital twin map instance and can carry/convey the digital twin simulation and/or verification requirements and operation policy in the message.

Step 310. The DTM can perform the digital twin simulation and/or verification operation on the created network digital twin map instance based on the digital twin simulation and/or verification requirements and operation policy. The DTM can report the results of the digital twin simulation and/or verification (e.g., service performance assurance policy, new service deployment policy, etc. ) to the DTVC.

Step 311. If the simulation operation does not satisfy the requirements/specification of the digital twin application, the DTVC, NDTMO, and/or DTM can collaborate/interoperate to iteratively update the network digital twin instance and/or the simulation operation policy. The DTVC, NDTMO, and/or DTM can collaborate to perform the simulation and/or verification operation until the result satisfies the needs/specification/requirements of the digital twin application.

Step 312. The DTVC can report the final result of the digital twin simulation and/or verification to the DT APP.

Implementation Example 5: Simulation operation of intent based DT application

Digital Twin applications serving communication service customers can have digital twin simulation requirements expressed by intent. The digital twin verification control function (DTVC) can analyze the simulation operation request information of the digital twin application expressed by the intent. The DTVC can decompose the intent into, but not limited to, the specific intent object type (or intent type) of the network digital twin map, the network digital twin map requirements, and/or the digital twin application requirements and policy for digital twin simulation and/or verification. The DTVC can request the network digital map management and orchestration function (NDTMO) to perform orchestration and/or lifecycle management operations for the network digital twin map.

The NDTMO can check if there is an existing digital twin map instance corresponding to a specific intent object type. If no existing digital twin map instance is found, the NDTMO can obtain/access the network digital twin map model corresponding to that specific intent object type from the KGS, and can configure the corresponding network digital twin map description file based on the network digital twin map requirements.

The digital twin management (DTM) can instantiate/establish the network digital twin map instance based on the network digital twin map description file. After the digital twin map instance is created, the DTVC can request the DTM to perform the digital twin application simulation and/or verification operations on the network digital twin map instance in terms of the digital twin application requirements. The DTVC can iteratively update the digital twin map instance according to the simulation and/or verification results until the simulation and/or verification results meet the intent expectation of the digital twin application requirements.

An example simulation operation of intent based DT application as depicted in FIG. 9, is described as follows.

Step 401. The DT APP can send the intent to the DTVC. The intent expectation can express the requirements and/or policy of the digital twin simulation and/or verification operation and the information of the digital twin application requirements.

Step 402. The DTVC can analyze and translate the intent. The DTVC can parse the intent expectation into at least one of: network digital twin map requirements, digital twin simulation and/or verification requirements and policy, and can extract the intent object type (or intent type) from the intent.

Step 403. The DTVC can initiate/send an orchestration and management request of the network digital twin map to the NDTMO. The DTVC can carry the network digital twin map requirements and corresponding intent object type in the orchestration and management request.

Step 404. The NDTMO can receive the orchestration and management request of the network digital twin map. The NDTMO can judge/determine whether there is an existing digital twin map instance associated with the intent object type. If none exists, the NDTMO can obtain/access the digital twin map model for the specific intent object type from the KGS. If the KGS cannot find a model associated with this intent object type, the KGS can return/provide a universal/configurable digital twin map model to the NDTMO. The NDTMO can generate digital twin map configuration parameters based on the network digital twin map requirements.

Step 405. The NDTMO can define/generate a new network digital twin map object description profile based on the obtained digital twin map model and the configuration parameters. The network elements, functions, and/or topology can be modified based on orchestration requirements.

Step 406. The NDTMO can send a message to request the DTM to instantiate the network digital twin map. The NDTMO can carry the relevant description profile in the message.

Step 407. The DTM, using the received network digital twin map object description profile, can acquire/retrieve/receive the required/suitable NE model, function model, and/or topology model from the KGS. The DTM can create the network digital twin map instance. The DTM can allocate compute/storage/network resources for the network digital twin map instance, and can configure necessary/suitable service parameters on the network digital twin map instance.

Step 408. The DTM, after the network digital twin map instance corresponding to the intent object type is created, can inform the NDTMO that the network digital twin map instance is created.

Step 409. The DTVC can send a message to request the DTM to perform the operation (s) of digital twin simulation and/or verification on the created network digital twin map instance. The DTVC can carry the digital twin simulation and/or verification requirements and operation policy in the message.

Step 410. The DTM can perform the operation (s) of digital twin simulation and/or verification on the created network digital twin map instance based on the digital twin simulation and/or verification requirements and operation policy. The DTM can report the result of digital twin simulation and/or verification (e.g., Case 2 and Case 3) to the DTVC.

Step 411. If the simulation operation does not satisfy the requirements of the digital twin application, the DTVC, NDTMO, and/or DTM can collaborate/interoperate together to update iteratively the network digital twin instance and/or the simulation operation policy, and can perform the simulation and/or verification operation (s) until the result satisfies the needs/specification/requirement of the digital twin application.

Step 412. The DTVC can report the final intent report (or final result) of the simulation and/or verification to the DT APP, and can indicate if the intent expectation was fulfilled.

Implementation Example 6: Updating the digital twin map instance

An existing digital twin map instance can be updated for the new DT application requirements. When the digital twin verification control function requests the NDTMO for digital twin map orchestration and life cycle management operations based on new/updated/modified DT application requirements, the NDTMO can check if a corresponding idle/available network digital twin map instance exists. If the idle/available network digital twin map instance exists, the NDTMO can update the description profile of the existing digital twin map object to make it meet the new requirements of the digital twin map in the use case. The NDTMO can request the DTM to initiate an update operation of the existing digital twin map instance.

The DTM can update the existing digital twin map instance based on the update description file of the digital twin map object. The DTVC, after the digital twin map instance is updated, can request the DTM to perform simulation and/or verification operation (s) of the digital twin application on the network digital twin map instance, and may update the instance iteratively according to the simulation and/or verification results (e.g., until the final simulation validates the results as expected) .

An example for updating a digital twin map instance depicted in FIG. 10, is described as follows:

Step 501. The DT APP can send a message with a new request for digital twin simulation and/or verification operation (s) to the digital twin verification control function (DTVC) , and can carry the information of the digital twin application requirements in the message.

Step 502. The DTVC can analyze the simulation and/or verification requirements of the digital twin application and can parse the simulation and/or verification requirements of the digital twin application into at least one of: network digital twin map requirements, digital twin simulation and/or verification requirements and policy. The DTVC can parse the simulation and/or verification requirements of the digital twin application into a corresponding object type, like scenario/task type, service type, intent object type, etc.

Step 503. The DTVC can initiate/send an orchestration and/or management request of the network digital twin map to the NDTMO, and can carry the new network digital twin map requirements and corresponding object type in the orchestration and/or management request.

Step 504. The NDTMO can check if one of the current unused (or available/idle) network digital twin map instances is associated with the corresponding object type. If one of the current unused network digital twin map instances of the NDTMO is associated with the corresponding object type, the NDTMO can perform an update operation instead of an instantiation operation to minimize the use of allocated/required resources. The NDTMO can first update the description profile of the existing digital twin map object associated with this object type to make the digital twin map object meet the new requirements of the digital twin map in this use case. The NDTMO can request the DTM to initiate an update operation of the existing digital twin map instance.

Step 505. The NDTMO can send a request for the updating operation of the existing network digital twin map instance, with the map ID of the existing network digital twin map instance and/or the updated description profile of the new network digital twin map object.

Step 506. The DTM, based on the received updated description profile of the new network digital twin map object, can update the existing network digital twin map instance (e.g., update the NE resources and network topology) to satisfy the functional and/or performance requirements of the digital twin map. The DTM can allocate compute/storage/network resources for the instance and can configure updated service parameters on the updated digital twin map instance. After the network digital twin map instance is successfully updated, the DTM can inform the NDTMO that the network digital twin map instance is updated.

Step 507. The DTM, after the network digital twin map instance is updated, can inform the NDTMO that the network digital twin map instance is updated.

Step 508. The DTVC can send a message to request the DTM to perform operation (s) of digital twin simulation and/or verification on the updated network digital twin map instance, and can carry the digital twin simulation and/or verification requirements and operation policy in the message.

Step 509. The DTM can perform the operation (s) of digital twin simulation and/or verification on the created network digital twin map instance based on the digital twin simulation and/or verification requirements and operation policy. The DTM can report the result of digital twin simulation and/or verification (e.g., Case 2 and Case 3) to the DTVC.

Step 510. If the simulation operation does not satisfy the requirements/specification of the digital twin application, the DTVC, NDTMO, and/or DTM can collaborate/interoperate to iteratively update the network digital twin instance and the simulation operation policy. The DTVC, NDTMO, and/or DTM can perform the simulation and/or verification operation (s) until the result satisfies the needs/specification of the digital twin application.

Step 511. The DTVC can report the final result of digital twin simulation and/or verification to the DT APP.

FIG. 11 illustrates a flow diagram 1110 of an example method for establishing or updating a DT map, in accordance with one or more embodiments of the present disclosure. The method 1100 may be implemented using any one or more of the components and devices detailed herein in conjunction with FIGS. 1 to 10. The method 1100 may be performed by a NDTMO, a DTVC and/or a DTM, in some embodiments. Additional, fewer, or different operations may be performed in the method 1100 depending on the embodiment. At least one aspect of the operations is directed to a system, method, apparatus, or a computer-readable medium.

With regards to (1105) , and in some embodiments, a network digital twin map orchestration (NDTMO) can receive a request from a digital twin verification control (DTVC) to orchestrate a network digital twin (DT) map. The DTVC can send to the NDTMO a request to orchestrate the DT map. The DVTC can send/provide/transmit the request to the NDTMO. The request can be based on a first request from a digital twin application (DT APP) to perform simulation operation for instance. For example, the DVTC can receive the first request from the DT APP, which may be based on intent, service, scenario and/or task.

The DTVC can translate/parse/interpret the first request into at least one of: an object type (e.g., intent/service/scenario/task type) of the network digital twin map, network digital twin map requirements, and/or the digital twin application requirements and policy for digital twin simulation and/or verification. The DVTC can generate or form the request according to any one or more of the foregoing information. The request can be a request to the NDTMO to perform orchestration and/or lifecycle management operations for the network digital twin map. The DTVC and/or the request can cause the NDTMO to determine whether to acquire a model of the DT map corresponding to the request.

With regards to (1110) , and in some embodiments, the NDTMO can determine whether to acquire/access/retrieve a model of the DT map corresponding to the request. The NFTMO can determine whether to acquire a model of the DT map corresponding to the request from a KGS. The NDTMO can check if there is an existing digital twin map instance corresponding to the object type. If no such existing digital twin map instance is found, the NDTMO can obtain/access a model of the DT map (e.g., a network digital twin map model) corresponding to that object type, from the KGS. The NDTMO can configure/update a network digital twin map description file based on the network digital twin map requirements. The network digital twin map description file can indicate/describe/represent an arrangement or rearrangement of at least one component of a network DT map.

With regards to (1115) , and in some embodiments, the NDTMO can orchestrate the DT map. The NDTMO can orchestrate/design the DT map by generating or updating the network digital twin map description file. The orchestration of the DT map can comprise determining/designing/formulating by the NDTMO an arrangement or rearrangement of at least one component of the DT map, using the network digital twin map model from the KGS, and/or an existing instance of the DT map. The at least one component of the DT map can comprise at least one of: at least one network element of the model, at least one network function of the model, a network topology of the model, performance of the model, or at least one resource allocation for the at least one network element or the DT map.

In some implementations, the method 1100 can include a digital twin management (DTM) instantiating/establishing/updating a new or existing network digital twin map instance, e.g., based on the network digital twin map description file. The DTM may inform the DTVC upon successful instantiation/updating/establishment of the network digital twin map instance. After the digital twin map instance is created/instantiated/updated, the DTVC can request the DTM to perform digital twin application simulation and/or verification operations on the network digital twin map instance according to the digital twin application requirements and/or policy. The DTVC can incrementally, repeatedly or recursively update/modify the digital twin map instance according to the simulation and/or verification results until the simulation and/or verification results meet the specification/request/requirements/intent/needs of the digital twin application requirements.

While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand example features and functions of the present solution. Such persons would understand, however, that the solution is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

It is also understood that any reference to an element herein using a designation such as "first, " "second, " and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.

Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

A person of ordinary skill in the art would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software" or a "software module) , or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.

Furthermore, a person of ordinary skill in the art would understand that various illustrative logical blocks, modules, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.

If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In this document, the term "module" as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.

Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present solution. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.

Claims

A method comprising:

receiving, by a network digital twin map orchestration (NDTMO) from a digital twin verification control (DTVC) , a request to orchestrate a digital twin (DT) map;

determining, by the NDTMO, whether to acquire a model of the DT map corresponding to the request, from a knowledge graph system (KGS) ; and

orchestrating, by the NDTMO, the DT map.
The method of claim 1, wherein:

orchestrating the DT map comprises determining, by the NDTMO, an arrangement or rearrangement of at least one component of the DT map, using the model of the DT map or an existing instance of the DT map, and

the at least one component of the DT map comprises at least one of: at least one network element of the model, at least one network function of the model, a network topology of the model, performance of the model, or at least one resource allocation for the at least one network element or the DT map.
The method of claim 1, comprising:

determining, by the NDTMO, the model of the DT map to acquire, according to at least one of: a type of scenario, a type of task, a type of service, or a type of intent, indicated by the request.
The method of claim 1, wherein at least one of:

a DT application sends a request to the DTVC, the request indicating a request type; or

the DTVC determines, according to the request, at least one requirement for the DT map and the request type.
The method of claim 1, wherein the request to orchestrate the DT map comprises an indication of at least one of: a type of scenario, a type of task, a type of service, a type of intent, or at least one requirement for the DT map.
The method of claim 1, wherein determining whether to acquire the model of the DT map comprises at least one of:

determining, by the NDTMO according to a request type of the request, whether an instance of the DT map exists;

determining, by the NDTMO, to acquire the model of the DT map from the KGS, when the instance does not exist; or

determining, by the NDTMO, to reuse or update the instance of the DT map, when the instance exists.
The method of claim 2, wherein a digital twin management (DTM) at least one of:

acquires a network element (NE) model, a function model and a topology model from the KGS, according to the arrangement or rearrangement of the at least one component of the DT map;

establishes an instance of the DT map, according to the NE model, the function model and the topology model;

allocates at least one resource for the instance; or

configures or modifies at least one service parameter of the instance.
The method of claim 2, wherein a digital twin management (DTM) at least one of:

updates the existing instance of the DT map, according to the arrangement or rearrangement of the at least one component of the DT map;

allocates at least one resource for the instance; or

configures or modifies at least one service parameter of the instance.
The method of claim 7 or 8, wherein at least one of:

the DTVC sends a request message to the DTM to perform digital twin simulation and verification on the instance;

the DTM performs the digital twin simulation and verification on the instance, according to at least one requirement;

the DTM sends to the DTVC a report on the simulation and verification; or

the NDTMO operates with the DTVC and DTM to iteratively update the instance and perform the simulation and verification, until requirements of the DT application are satisfied.
The method of claim 8, wherein the DTVC sends to the DT application a final result of the simulation and verification.
A method comprising:

sending, by a digital twin verification control (DTVC) to a network digital twin map orchestration (NDTMO) from, a request to orchestrate a digital twin (DT) map;

causing the NDTMO to determine whether to acquire a model of the DT map corresponding to the request; and

causing the NDTMO to orchestrate the DT map.
A non-transitory computer readable medium storing instructions, which when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1 to11.
An apparatus comprising:

at least one processor configured to perform the method of any one of claims 1 to 11.