X-centric communication infrastructure for supporting "all-in-one service" service model

Abstract

A method, apparatus, and system for providing an open system architecture, referred to as an X-centric architecture, that provides, supports, or enables all services (Anthingas-a-service, XaaS), and that can be centered on a variety of roles, thereby supporting a variety of operating scenarios. The service supported by the X-centered architecture is called as the XaaS service. Embodiments of an X-centric architecture relate to scalable and adaptable modular designs. Embodiments provide new service modules or facilitate dynamic addition of new service modules to provide, support, or enable XaaS services without modifying or redesigning the system architecture.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. prior filed provisional patent application No. 63 / 347,365, filed on May 31, 2022, entitled “X-CENTRIC COMMUNICATION INFRASTRUCTURE FOR SUPPORTING ANYTHING-AS-A-SERVICE SERVICE MODEL,” the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] The present invention relates generally to the field of computerized communication systems, and more particularly to a communication infrastructure for enabling anything-as-a-service (XaaS) service delivery. Background Art

[0004] Current wireless communication systems (also called wireless systems), such as those developed by the Third Generation Partnership Project (3GPP), rd The fifth generation (5 th Future wireless systems (e.g., the 6th generation (6G) defined by 3GPP) are expected to provide connectivity services. th The 6th Generation (6G) system will go beyond connectivity to provide a variety of new services. It is also expected that future wireless systems may be operated by multiple parties, for example, different parties operate different parts of the wireless system to provide certain services. These services can be provided for internal use of the system (e.g., the operator) or can be provided to end customers.

[0005] However, current wireless systems and infrastructure need further development to support the above and similar scenarios. Such development is not simple and may require solving various technical and design issues.

[0006] Therefore, there is a need for a method, apparatus, and system for implementing XaaS service delivery that eliminates or alleviates one or more limitations in the prior art.

[0007] This background information is intended to provide information that may be relevant to the present disclosure. None of the above information is necessarily or should be construed as constituting prior art with respect to the present disclosure. Summary of the invention

[0008] Embodiments of the present disclosure provide an open system architecture for a wireless system that provides anything-as-a-service (XaaS) functionality. Embodiments may be centered around any of a variety of roles to support a variety of operating scenarios, a feature referred to as an X-centric architecture. In addition, embodiments may be provided as an open system architecture. Embodiments may be extensible, allowing unknown future services to be dynamically enabled or provided, substantially without modifying or redesigning the system architecture. To aid in this, an X-centric architecture may be provided using the modular design described herein. Services supported by an X-centric architecture may be referred to as XaaS services. The modular design may allow new service modules to be dynamically added to enable or provide or support associated new XaaS services.

[0009] According to an embodiment of the present disclosure, a system is provided, for example, the system is at least partially formed by a plurality of networked computing devices of a networked communication system, each networked computing device having at least a processor, a network interface and a memory. The system includes one or more infrastructure modules, one or more service modules and one or more management and control modules, each module being instantiated, for example, using one or more networked computing devices in the networked computing devices. The infrastructure modules each provide corresponding infrastructure resources as services. Each infrastructure resource may include a corresponding type of device for supporting the networked communication system. The service modules each provide corresponding functions as services and utilize at least one infrastructure resource in the infrastructure resources as a service. The management and control modules each provide corresponding management or control resources (also referred to as functions) as services. At least one or each management and control module in the management and control modules may utilize the services of at least one infrastructure module in the infrastructure module. At least one management and control module in the management and control modules may provide its corresponding management or control resources (or functions) as services to at least one of the infrastructure modules or the service modules.

[0010] In various embodiments, one or more (or more) service modules include a connection service module configured to provide connection services, one or more (or more) management and control modules include a task management module configured to provide task management services, or both.

[0011] In some embodiments, each of the service modules includes its own corresponding service management and control plane components, and each of the infrastructure modules includes its own corresponding infrastructure management and control plane components. The management and control modules, service management and control plane components, and infrastructure management and control plane components in these embodiments are operably coupled together via interconnections. The interconnections may form a fully meshed network.

[0012] In some embodiments, the management and control modules are operably coupled to each other via an interconnect. In some other embodiments, the service modules and infrastructure modules are operably coupled to each other and to the management and control modules via the interconnect. The interconnect may form a fully meshed network or a communication bus. The interconnect may be managed by a connection service module or a task management module.

[0013] In some embodiments, at least one of the service modules includes a service management and control plane component and a service data plane component operably coupled to the service management and control plane component. The service management and control plane component may be provided as a service using, at least in part, one or more of the management and control modules. The service data plane component may be provided as a service using, at least in part, two or more of the infrastructure modules. Two or more of the service data plane components of two or more of the service modules in the service modules may be communicatively coupled together via respective interconnections (e.g., tunnels). The interconnections may be managed by a connection service module, a task management module, or a combination thereof.

[0014] In some embodiments, two or more of the infrastructure modules are at least partially used to provide at least one of the service modules as a service. In some embodiments, the connection service module and the task management module are integrated together.

[0015] In some embodiments, each of the service modules includes its own corresponding service management and control plane components. In these embodiments, the service management and control plane components are operably coupled together, or the management and control modules are operably coupled together, or the service management and control plane components are operably coupled to the management and control modules, or a combination thereof.

[0016] In some embodiments, at least one of the infrastructure modules provides its corresponding infrastructure resources as a service to at least one of: another infrastructure module in the infrastructure modules; and one of the management and control modules. In some embodiments, at least one of the service modules provides its corresponding functions as a service to at least one of: another service module in the service modules; an infrastructure module in the infrastructure modules; and one of the management and control modules. In some embodiments, at least one of the management and control modules provides its corresponding management or control resources (or functions) as a service to another of the management and control modules.

[0017] In some embodiments (e.g., according to an infrastructure provider-centric scenario), the same party provides or operates at least one of the infrastructure modules and at least one of the management and control modules. In some embodiments (e.g., according to a third-party-centric scenario), the same party provides or operates multiple or all of the management and control modules. In some embodiments (e.g., according to a customer-centric scenario), the same party provides or operates at least one of the service modules and at least one of the management and control modules. In other embodiments, another party provides or operates at least one of the infrastructure modules, service modules, and management and control modules that is not provided or operated by the same party.

[0018] In some embodiments, at least one of the service modules includes a service management and control component and a service data plane operably coupled to the service management and control component. In some other embodiments, one or more of the management and control modules are used at least in part to provide the service management and control component as a service. Additionally or alternatively, one or more of the infrastructure modules may be used at least in part to provide the service data plane as a service. Additionally or alternatively, two or more of the service data planes may be communicatively coupled together via respective interconnects (e.g., tunnels).

[0019] In some implementations, two or more of the service modules are communicatively coupled together via an interconnect (eg, a tunnel).

[0020] In some embodiments, at least one of the infrastructure modules includes an infrastructure management and control component. The infrastructure management and control component may be provided as a service, at least in part, using one or more of the management and control modules.

[0021] In some embodiments, at least one of the service modules includes a corresponding service management and control component, at least one of the infrastructure modules includes a corresponding infrastructure management and control component, or both. The management and control modules, the service management and control components, and the infrastructure management and control components can be communicatively coupled together, for example, using a full mesh network or alternatively using a non-full mesh network.

[0022] In some embodiments, the infrastructure module includes one or more of the following: a ground communication module; a non-ground communication module; a cloud module; a cache module; a sensor module; a radio access network module; a core network module; a data center module; and a database module. In some embodiments, the service module includes one or more of the following: an artificial intelligence network module; a data network module; a blockchain network module; a data analysis and management module; a module that provides vertical services; a connection service module; and a digital world network module. In some embodiments, the management and control module includes one or more of the following: a resource management module; a protocol management module; a connection management module; a policy and customer service management module; a mission management module; a CONET module; a network security management module; a service provision management module; and a network security management module.

[0023] In various embodiments, at least one of the infrastructure module, the service module, and the management and control module operates according to an open systems architecture.

[0024] In various embodiments, the management and control module includes a task management module, which is configured to interoperate with one or more service modules in the service module to perform a specified task, the task including a set of specified tasks or operations. The task management module can interoperate with two or more service modules in the service module to perform the specified task, and the task management module can cause one or more interconnections to be established between the two or more service modules in the service module to support the specified task. One or more terminals, application servers, or both can be operably coupled to one or more service modules in the service module and operate to support the specified task.

[0025] According to an embodiment of the present disclosure, a method is provided, for example, a method performed by one or a series of networked computing devices. The method includes: using one or more corresponding infrastructure modules to provide one or more infrastructure resources as a service. Each infrastructure resource may include a corresponding type of device for supporting an associated networked communication system. The method also includes: using one or more corresponding service modules to provide one or more functions as a service. At least one service module utilizes at least one of the infrastructure resources as a service. The method also includes: using one or more corresponding management and control modules to provide one or more management or control resources (or functions) as a service. At least one of the management and control modules provides its corresponding management or control resources (or functions) as a service to at least one of the infrastructure modules or service modules. The method may include one or more other aspects, for example, as discussed above for the provided system.

[0026] According to an embodiment of the present disclosure, a computer program product is provided, including a (e.g., non-transitory) computer-readable medium having statements and instructions stored thereon, which, when executed by one or more computer processors, causes the computer processors to perform the method described above.

[0027] Embodiments are described above in conjunction with various aspects of the present invention, and these embodiments can be implemented based on these aspects. It will be appreciated by those skilled in the art that embodiments can be implemented in conjunction with the aspects in which they are described, but can also be implemented in conjunction with other embodiments of the aspect. When the embodiments are mutually exclusive or otherwise incompatible with each other, it will be apparent to those skilled in the art. Some embodiments can be described in conjunction with one aspect, but can also be applied to other aspects, which will be apparent to those skilled in the art. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Other features and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0029] Figure 1A A system according to an embodiment of the present disclosure is shown, the system comprising a service module, a management and control module, and an infrastructure module.

[0030] Figure 1B A system according to other embodiments of the present disclosure is shown, the system including a service module, a management and control module, and an infrastructure module.

[0031] Figure 2AA system according to an embodiment of the present disclosure is shown wherein one or more infrastructure providers provide both the management and control module and the infrastructure module.

[0032] Figure 2B A system according to an embodiment of the present disclosure is shown, wherein a third party provides multiple management and control modules.

[0033] Figure 2C A system according to an embodiment of the present disclosure is shown, wherein one or more customers provide both a management and control module and a service module.

[0034] Figure 3A A system according to an embodiment of the present disclosure is shown, the system including a service module, a management and control module and an infrastructure module, as well as the contents and interconnections of these modules.

[0035] Figure 3B A system according to other embodiments of the present disclosure is shown, the system including a service module, a management and control module and an infrastructure module, as well as the contents and interconnections of these modules.

[0036] Figure 4 A computing device that can perform computing or related operations according to an embodiment of the present disclosure is shown.

[0037] It should be noted that throughout the Figures, like features are identified by like reference numerals. DETAILED DESCRIPTION

[0038] As used herein, the term "everything as a service" (i.e., "XaaS") may reflect the concept itself as proposed by the computer network industry. For example, XaaS may be conceptualized as a generalization of the software as a service concept or the infrastructure as a service concept. XaaS may utilize cloud computing and device virtualization concepts in combination with a service model to provide various functions. According to an embodiment of the present disclosure, XaaS may describe, for example, that the functionality of any module disclosed herein may be provided as a service to another module or an external entity such as a customer. The phrase "as a service" is used herein synonymously with "as a service."

[0039] Open systems architecture may refer to a design approach in which systems (e.g., modules) are interoperable and interconnected with each other, generally without the need for modification or redesign. Open systems architecture is a method for implementing modular design in which modules are configured to interoperate. An open systems architecture may include modules that respond to known inputs in a known manner, for example, performing an action or providing a response to a query, input, or stimulus in a predictable (and possibly standardized) manner. Modules in an open systems architecture may provide functionality as a service because the modules respond to inputs or stimuli in a specific manner to provide such functionality. Services may be provided by a server to a client, and thus an "as a service" model may involve a server-client model.

[0040] According to an embodiment of the present disclosure, a networked computing and communication system is provided, which includes multiple different types of modules in an open system architecture. On one layer, infrastructure modules each provide corresponding infrastructure resources as services. Infrastructure resources may include real computing, communication or data storage resources. On another layer, service modules each provide corresponding functions as services. Service module functions may be functions that can be used by end users or other modules. Service modules may use at least one of the infrastructure resources as a service. On another layer, management and control modules each provide corresponding management or control resources (or functions) as services. Management and control resources may be used to manage other modules, module tasks, module operations or other management or control tasks. At least one of the management and control modules may provide its corresponding management or control resources (or functions) as services to at least one of the service modules or infrastructure modules. Each module may provide its functions as services to one, part or all modules of the same layer or different layers as needed. Modules may be interconnected to provide services to each other in a configurable manner, depending on operational requirements. Different modules may be provided or operated by different participants to provide different X-centric configurations, which may be participant-centric configurations.

[0041] Figure 1A An (e.g., X-centric) architecture provided according to an exemplary embodiment of the present disclosure is shown. The architecture 100 includes a service layer 110, a management and control (M / C) layer 130, and an infrastructure layer 150. Different layers can provide different services. The services of each layer are examples of different types of XaaS services. Accordingly, an architecture with three different layers is provided, with XaaS modules in each layer, which may help with openness and scalability.

[0042] The service layer 110 includes one or more service modules. Depending on the needs of a specific operation scenario, a service module may or may not be included. As new service modules are developed, these new service modules may be included in the existing architecture or implementation of the network.

[0043] As an example, Figure 1A Various possible service modules are shown. These examples are not necessarily intended to be limiting. In fact, embodiments of the present disclosure are capable of hosting service modules that have not yet been conceptualized, and these modules can be added as they are developed or needed. Similarly, these modules can be omitted where they are not needed. The NET4AI module 112 provides NET4AI services; the NET4Data module 114 provides NET4Data services; the NET4BC module 116 provides NET4BC services; the DAM module 118 provides DAM services; one or more vertical modules 120 provide one or more associated vertical services; and the connection service module 122 provides connection services. A description of each of these modules is provided below. Each module can be provided by a different party (e.g., operation), or multiple modules can be provided by the same party (e.g., operation). A service module (e.g., any of the service modules mentioned above) can provide or supply services (e.g., NET4AI services, NET4Data services, NET4BC services, DAM services, vertical services, connection services) to end customers (users), one or more M / C modules in M / C layer 130, or other service modules in service layer 110, or a combination thereof. A service module can provide services to other service modules in essentially any interconnected chain or network. In various embodiments, any given service module can potentially be provided as a service to any other given service module (in the same layer or another layer) or to external users or customers.

[0044] The NET4AI service provided by the NET4AI module 112 can be described as follows. The NET4AI service provides some or all of the following: artificial intelligence (AI) model customization and management, AI model distribution and parallelization, AI model training, and inference optimization. The NET4AI module helps provide AI as a service. AI as a service can refer to a service through which AI or machine learning resources can be provided for use by end users or other service modules or any M / C module 130.

[0045] The NET4Data service provided by the N data network (network for data, NET4Data) module 114 can be described as follows. The NET4Data service provides some or all of the following: data upload and data storage, data access control and data protection. The NET4Data module helps to provide data storage (e.g., cloud storage) as a service. Data storage as a service can be deployed to process the data of the end user, or another service module in the service module 110 or the data of any M / C module 130. The NET4Data service can store data in one or more computer memories, and can manage features such as data integrity and backup, data redundancy, data retrieval speed optimization, etc. The NET4Data service can also provide data sharing.

[0046] The NET4BC service provided by the NET4BC module 116 can be described as follows. The NET4BC service provides general management and control of blockchain operations. The NET4BC service processes block data and implements blockchain as a service.

[0047] The DAM services provided by the DAM module 118 can be described as follows. The DAM services provide some or all of the following: data collection and verification, data privacy protection, data analysis, and data delivery. The DAM services process all types of data and implement data analysis and management as a service. The DAM services can also provide data cleansing.

[0048] The vertical services provided by one or more vertical modules 120 may include vehicle to everything (V2X) services, Internet of Things (IoT) services, metaverse services, etc., and process data services for vertical (e.g., V2X, metaverse) customers. Vertical services can generally be described as services associated with vertical service providers. A vertical service provider can provide one or more specialized products or services in a particular field. Examples of vertical service areas include banking, manufacturing, education, real estate, government, or law.

[0049] The connection service provided by the connection service module 122 can help provide data connections between devices or endpoints. For example, a data connection can be provided between a device and a data network (DN), between two application services or servers, etc. The connection service can help provide data connection as a service. In various embodiments, the connection service can handle the data services of the end user, such as voice services or application layer data. The connection service may include a 6G connection service. In some embodiments, the connection service module 122 and the task management module 140 are integrated. For example, the connection service module 122 can be integrated into the task management module 140 so that the task management module 140 provides connection services.

[0050] As used herein, the service provided by the service module in the service layer 110 may be referred to as an XaaS service. Since the service is provided at the service layer 110, it is referred to as a service layer XaaS service.

[0051] The service module may include one or more network functions. The service module may use these network functions to provide associated services. When the service module includes only one network function, the service module may be equivalent to (or may be) this included network function.

[0052] In various embodiments, the service has its own data process, which is implemented by some or all of the one or more network functions of the service module. The data process may include calculation or data processing, data storage, block creation, data privacy protection operations, etc.

[0053] The M / C layer 130 (also referred to as a control and management (C / M) layer) includes one or more M / C modules.

[0054] As an example, Figure 1AVarious possible M / C modules are shown. These examples are not necessarily intended to be limiting. Resource management (RM) module 132 provides RM services. Protocol management (PM) module 134 provides PM services. Connection management (CM) module 136 provides connection services. Policy and customer service management (CSM) module 138 provides policy and CSM services. Mission management (MM) module 140 provides MM services, wherein the mission is as described elsewhere in this document. Confederation of networks (CONET) module 142 provides CONET services. Network security management (NSM) module 144 provides NSM services. Each M / C module can be provided by different participants. One or more M / C modules can be provided by the same participant. The M / C module (e.g., any of the M / C modules mentioned above) can provide M / C services (e.g., RM services, PM services, CM services, CSM services, CONET services, NSM services) to end customers (users) (which may be external customers or users), one or more infrastructure modules in the infrastructure layer 150, one or more service modules in the service layer 110, other M / C modules in the M / C layer 130, etc. or a combination thereof.

[0055] The RM service provided by the RM module 132 can be described as follows. The RM service can manage resources in a static or dynamic manner. Managed resources may include resources provided by the infrastructure layer, such as wireless resources, wired resources, computing resources, storage resources, and sensing resources. Managing resources may include managing and controlling network slices and data routing. The RM service may provide wireless devices with the ability to manage the lifecycle of one or more network slices and allocate air resources.

[0056] The PM services provided by the PM module 134 can be described as follows. The PM services can provide software defined protocol functions, such as message processing function chaining and configuration, protocol stack selection and configuration, protocol parameter tuning and optimization, etc. or a combination thereof. The PM services can also be referred to as software defined protocol (SDP) services. The PM services can provide the ability to customize the protocol stack for the identified interface design service. The protocol stack can be pre-defined so that it can be selected on demand. The protocol stack can be designed on demand.

[0057] The CM services provided by the CM module 136 can be described as follows: The CM services can provide connection management, mobility management, handover, path switching, registration management, paging, power saving management, etc. or a combination thereof.

[0058] The CSM services provided by the CSM module 138 can be described as follows. The CSM services can provide authentication, identification (ID) management, key management (business protection), authorization, service level agreement (SLA) management, SLA execution, policy / rule / regulatory assurance, installment payment (billing), etc. or a combination thereof. SLA can refer to a service level agreement between any two or more of the participants. For example, the SLA can be an SLA between a participant operating in the service layer, a participant operating in the M / C layer, a participant operating in the infrastructure, etc. or a combination thereof. Each of these participants can have one or more roles as described elsewhere in this document, for example, with respect to the described X-centric scenario.

[0059] The MM service provided by the MM module 140 can be described as follows. The MM service can convert the data process of one or more related service modules in the service layer into a task, for example, upon request. The MM service (more precisely, the MM module providing the MM service) can manage (for example, establish, modify and configure) the communication tunnel between the service data planes of the related service modules to support the task. In some embodiments, the MM service (more precisely, the MM module 140 providing the MM service) can call (i.e. use) the connection service (provided by the connection service module 122) to manage (for example, establish, modify and configure) the communication tunnel between the service data planes of the related service modules to support the task, and the connection service (more precisely, the connection service module 122 providing the connection service) manages the communication tunnel accordingly. For example, the task can be related to cross-layer interaction and cross-service interaction as described elsewhere in this document. The task can be a service provided to a customer. The task can be a service type provided by a single service, or a service type provided using contributions from multiple services. The MM service provides a capability to program the provision of XaaS services at the service layer to provide task services. In some implementations, the MM module 140 is integrated with the connection service module 122, for example, integrated within the connection service module 122, so that the connection service module 122 provides MM services.

[0060] The CONET service provided by the CONET module 142 can be described as follows. The CONET service can provide or contribute to the establishment of a trust alliance, the joining or leaving of alliance members, and the management of blockchains including creation, updating and deletion. The CONET service can also be referred to as a network blockchain (block chain for network, BC4NET) service. CONET refers to the alliance network. The CONET service can involve or contribute to the formation of alliances between partners, mutual authentication, mutual authorization, and agreement negotiation on recording and tracing the selected actions performed by these partners. This can be performed to provide a trusted environment for system operation.

[0061] The NSM services provided by the NSM module 144 can be described as follows. The NSM services can provide or facilitate equipment operation security risk detection, network operation security risk detection, network operation security risk prediction, etc. or a combination thereof. The NSM services can also be referred to as network security (SEC4NET) services. The NSM module 144 provides network security as a service. For example, this can provide infrastructure owners with the ability to detect potential security risks to their infrastructure assets.

[0062] In various implementations, the M / C service provided by the M / C module may be an XaaS service. Since the service is provided at the M / C layer, it may be referred to as an M / C layer XaaS service.

[0063] In various embodiments, the M / C module includes one or more network functions and uses these network functions to provide M / C services. When providing M / C services, the M / C module can utilize service layer XaaS services. When the M / C module includes only one network function, the M / C module can be equivalent to (or can be) this network function.

[0064] In various embodiments, the M / C service has its own signaling process, which is implemented by some network functions in one or more network functions of the M / C module. For example, the signaling process may include management signaling, control signaling, etc. or a combination thereof.

[0065] The infrastructure layer 150 includes one or more infrastructure modules. The infrastructure module may provide or supply a variety of infrastructure resources. The infrastructure module may include a ground communication module 152. Examples of ground communication modules include a radio access network (RAN) module, a reconfigurable intelligent surface (RIS) module, a zero energy device (ZED) module, and a transport network (TN) module. The infrastructure module may include a non-ground communication module 154, such as a satellite network communication module. The infrastructure module may include a cloud module 156, such as a data center network. The infrastructure module may include a cache module 158, such as a cache node. The infrastructure module may include a sensor module 160, such as a sensor node or a sensor network.

[0066] Each infrastructure module can be provided by a different party, or multiple infrastructure modules can be provided by the same party. Providing can include providing and operating a module, or operating an already provided module. An infrastructure module (e.g., any of the infrastructure modules mentioned above) can provide infrastructure services (in the form of resources) to end customers (users), its service layer or module, its M / C layer or module, other infrastructure modules in the infrastructure layer, etc. or a combination thereof. The infrastructure services provided by the infrastructure modules can be referred to as infrastructure layer XaaS services. Each infrastructure module or multiple infrastructure modules can be provided by a single provider, or can be provided by multiple providers.

[0067] In addition, if Figure 1A As shown, each service module in the service layer 110 may include or be operatively coupled to its own corresponding service M / C-plane component 128. Similarly, each infrastructure module in the infrastructure layer 150 may include or be operatively coupled to its own corresponding infrastructure M / C-plane component 168. Figure 3A These M / C face components are described in more detail and in this regard it is noted that Figure 1A The components 128 and 168 can be respectively Figure 3AThe components 328, 368 of the M / C plane components 128, 168 can be the same. The M / C plane components 128, 168 can be dedicated control functions of the modules associated therewith. In various embodiments, each M / C plane component 128, 168 is connected to another M / C plane component 128, 168, and is also connected to each module of the M / C layer 130. The connection can be made through the XaaS interface. Each module of the M / C layer 130 can also be interconnected in this way. Therefore, the full mesh network can operably couple all modules of the M / C layer and all M / C plane components. In the full mesh network, each networked component in the networked component can be directly connected to each other networked component in the networked component, for example, through a separate dedicated communication link. Therefore, the M / C layer modules and the M / C plane components can be controlled in a coordinated manner. For example, the M / C layer can control the behavior of each service module through such a full mesh network. The M / C plane component 168 can be used for infrastructure management. Each of the infrastructure modules shown is a different type of infrastructure as a service provided.

[0068] Figure 1B According to one embodiment, a Figure 1A Specifically, in Figure 1B In the embodiment, the NET4DW service module 124 is included in the service layer 110, the service provision management module 146 is included in the M / C layer 130, and the core network (CN) infrastructure module 162, the data center infrastructure module 164 and the database infrastructure module 166 are provided in the infrastructure layer 150. The CM module can provide services to the digital world.

[0069] The RAN infrastructure module 152 and the core network (CN) infrastructure module 162 can interoperate as complementary parts of one or more wireless networks. The operation of the data center infrastructure module 164 can be similar to the operation of the cloud module 156 to provide data center or related capabilities. The database infrastructure module 166 can similarly provide database-specific capabilities, such as in the form of one or more databases responding to database queries or data storage operations.

[0070] The modules of the M / C layer 130 can be provided and deployed by using network slicing. These modules can also utilize resources provided by the infrastructure layer (e.g., through network slicing).

[0071] The service provision management module 146 provides the ability to control and manage the service access of the customer and provide the requested service. This capability can be provided using unified mutual authentication, authorization and policy, key management, QoS assurance, and billing between any pair of XaaS service providers and customers. Customers in this sense can include end customers in the physical world and digital representatives in the digital world or both.

[0072] In various embodiments, the XaaS service in the M / C layer 130 supports the control and management of the 6G system itself and provides support to the vertical domain when requested. An example is that the RM service 132 can serve the RAN for air resource management and can also provide services to the vertical domain so that the vertical domain allocates air resources to its end customers. The XaaS module in the M / C layer 130 can be deployed by using slicing technology.

[0073] The NET4DW service module 124 provides digital world functions and related services. Digital world functions and related services (referred to as digital world services) provide the ability to build, control and manage the digital world. The digital world is defined as the digital realization of the physical world. The digital world (e.g., the metaverse) provides an interactive multi-user environment that is intended to simulate various physical aspects of the real world. Sensors can be used to acquire digital world participant data, and the digital world can respond to the sensor input, for example, by providing corresponding outputs to participants or other remote participants, so as to immerse the user experience. The NET4DW service module can process digital world participant data to facilitate this experience, acquire and utilize network resources to help make the experience reach the desired quality, manage participation, guide the user experience, etc.

[0074] The services provided at the service layer 110 can be developed and deployed by using resources provided in the infrastructure and leveraging network function virtualization and slicing technologies. The capabilities of each service can be provided by its control and management functions and service-specific data processing functions.

[0075] In addition to supporting XaaS services at service layer 110, 6G implementations can also leverage 5G systems to provide vertical services (see also 120). The difference between 6G XaaS services and other verticals is that verticals are pure customers that require other XaaS services to support their operation, while each XaaS service in the XaaS service provides its capabilities to 6G customers.

[0076] In various embodiments, any pair of XaaS services of the 6G system can be common customers and providers of each other. The first service can use the second service as a direct or indirect customer, and the first service can also be a direct or indirect customer of the second service. The first service can directly or indirectly depend on other services, and other services can directly or indirectly depend on the first service. For example, an indirect customer is a customer of a customer. For example, an infrastructure owner can provide its resources to XaaS services in the service layer and C / M layer; the RM service can use the capabilities provided by NET4AI, DAM, and NET4DW for its resource management for vertical slicing; CONET services and NET4Data services can use the capabilities provided by NET4BC to perform their operations.

[0077] The use of modules such as service modules, M / C modules, and infrastructure modules can contribute to the customizability of the architecture disclosed herein. Modules can be provided on demand, leaving out unnecessary modules. This can streamline and simplify the implementation of the architecture. In addition, as future services become available, they can be encapsulated in new modules and added as needed. Each module can be essentially self-contained and interoperate with other modules or system components using defined interfaces or protocols. Therefore, adding modules or removing modules can be done without reconfiguring other modules. This contributes to the ready reconfigurability of the architecture.

[0078] Different system modules (e.g., service module, M / C module, infrastructure module) as described above can be provided by different participants. Participants can be business entities, "players", etc. Business entities can focus on providing one or more products or services, such as communication or computing infrastructure, software services, applications, utilities, consulting, government, etc., or a combination thereof. Three different roles that participants can assume include: service layer XaaS provider, M / C layer XaaS provider, and infrastructure layer XaaS provider. A participant who provides at least one service module at the service layer assumes the role of service layer XaaS provider. A participant who provides at least one M / C module at the M / C layer assumes the role of M / C layer XaaS provider. A participant who provides at least one infrastructure module assumes the role of infrastructure layer XaaS provider. A participant can provide modules at more than one layer, thereby assuming multiple roles.

[0079] like FIG. 2A to FIG. 2C As shown in Figure 2, three possible scenarios are shown, depending on the parties that assume the role of M / C layer XaaS provider. FIG. 2A to FIG. 2C In this example, the infrastructure provider is the infrastructure layer XaaS provider, the M / C XaaS provider is the M / C layer XaaS provider, the customer is the service layer XaaS provider, and the third party is neither a service layer XaaS provider nor an infrastructure layer XaaS provider. FIG. 2A to FIG. 2C The data plane interface is not shown.

[0080] Figure 2A An infrastructure provider-centric scenario according to an embodiment of the present disclosure is shown, wherein one or more parties 205 (infrastructure providers) that provide portions 210, 211 of the infrastructure layer also each provide at least one component (module) 215, 216 of the M / C layer. This may also be referred to as a "vertical M / C" scenario. In an infrastructure provider-centric scenario, the infrastructure layer XaaS provider also assumes the role of the M / C layer XaaS provider. Different infrastructure providers can interact with each other, as shown by horizontal arrows 225. Similarly, modules associated with a first infrastructure provider can interact with modules associated with a second, different infrastructure provider. One infrastructure provider may provide modules 210, 215, while another infrastructure provider may provide modules 211, 216. Customers 220 may provide modules in a service layer 222, or another entity may provide modules 222 for use by customers.

[0081] Figure 2B A third-party-centric scenario according to one embodiment of the present disclosure is shown, wherein a third party 230 provides components 235, 236 (e.g., modules) of the M / C layer and thus assumes the role of an M / C layer XaaS provider. This may also be referred to as a "horizontal M / C" scenario. A third party may provide one or more or all of the components of the M / C layer. Components (e.g., modules) of the infrastructure layer may be provided by an infrastructure provider. Components (e.g., modules) of the service layer may be provided by a customer or other entity.

[0082] Figure 2C A customer-centric scenario according to one embodiment of the present disclosure is shown, wherein one or more customers 245 provide components 250, 255, 256 of the M / C layer and thus assume the M / C layer XaaS provider role. Such customers 245 also provide one or more components 255, 256 of the service layer. One customer may provide one or some components 250 (modules) of the M / C layer and one or some components 255 (modules) of the service layer, while another customer may provide other components 256 of the service layer (and optionally also of the M / C layer). Components (modules) of the infrastructure layer may be provided by an infrastructure provider.

[0083] It should be noted that FIG. 2A to FIG. 2CThe scenarios shown can occur as shown, or scenarios can be arbitrarily combined to produce hybrid scenarios. Scenarios can be configured as needed. Scenarios can be negotiated between the parties involved. Therefore, the implementation is X-centric. The term "X-centric" refers to the ability of the implementation to be reconfigurable so that the implementation is infrastructure provider-centric, third-party-centric, customer-centric, etc. or a combination thereof. Other types of configurations can also be supported. Therefore, multiple possible mappings between participants and roles are supported, where different X-centric scenarios correspond to different mappings. This contributes to the openness of the architecture and supports multiple operational scenarios. A configuration can be centered on a certain entity because the configuration points to a specific goal related to the entity. The architecture can be X-centric because the architecture can be configured into any of a variety of such configurations.

[0084] Implementations of the present disclosure also demonstrate cross-layer interactions, cross-service interactions, or both. Figure 3A One embodiment of the present disclosure is shown, in which a service module 310 includes, or is associated with, a service M / C plane component 328 and a service data plane 370. The service M / C plane component 328 can implement the functions of the M / C layer for managing and controlling the service data plane 370. Each service M / C plane component 328 and service data plane 370 can be dedicated to a single specific service module 310. The service M / C plane component 328 (or simply the service M / C plane, or M / C plane) can include one or more network functions (referred to as controllers). The service data plane 370 (or simply the data plane) can also include one or more network functions (referred to as processing functions). These network functions can be logical functions and can be dynamically deployed. The service module 310 can be connected to Figure 1A The service modules of the service layer 110 are the same.

[0085] In various embodiments, one or both of two types of processing functions may be included in the service data plane 370. The two types of processing functions are data processing functions and header processing functions. The data processing function implements service-specific logic and processes service data, for example, for purposes such as AI training, data cleansing, private data access control, integration of multiple streams for the metaverse, etc. The header processing function implements connection / communication logic and performs header processing, for example, for purposes such as routing, QoS processing, service detection, service gating, etc. Accordingly, the service data plane 370 can be further divided into a processing plane and a connection plane. The processing plane includes data processing functions. The connection plane includes header processing functions. In some embodiments, the service data plane 370 includes only data processing functions, and the connection plane is optional. In some embodiments, the service data plane 370 includes only header processing functions, and the processing plane is optional, for example, when the service module 310 is a connection service module such as the connection service module 122. The service data plane 370 can be dedicated to a specific host service and can process data required to provide the service.

[0086] The service module 310 may be provided using or supported by an infrastructure module 350, which may be provided with Figure 1A The infrastructure modules 350 may be the same as the infrastructure modules of the infrastructure layer 150 of the service module 310. For example, the infrastructure module 350 may be provided as a service for implementing the service module 310. Thus, according to the XaaS approach, the module may be implemented or supported at least in part using the infrastructure modules. The service module (or service layer XaaS) may use one, some, or all types of available infrastructure modules (or infrastructure layer XaaS).

[0087] In various embodiments, when the service module 310 provides XaaS services, one or more associated processing functions may receive service data from each other, or from other network functions (e.g., the service data plane of another service module). Such processing functions may process received data services that carry data (service data) related to the services provided by the service module. Such processing functions may additionally or alternatively send service data (which may be processed service data and may be included in the processed data services) to each other or to one or more other network functions. For example, a processing function may use one or more interconnects 372 to send service data to one or more processing functions of different service modules. Data services (whether received or sent) may include information indicating the type of service data, such as data to be processed, AI models, data before purification, data after purification, etc. Data services may also include information identifying how service data should be processed, such as processing codes or indexes. Data services may include information such as source entity IDs, destination IDs, path IDs, or processing orders, and the information may then be used by the processing functions to correctly (e.g., using the correct path) route the data services. The above information may be included in the data packet, for example, in the header of the data packet or in the payload field of the data packet (for example, as part of the service data). The data packet belongs to the data service.

[0088] In various embodiments, the service M / C component 328 includes one or more controllers, and the service data plane 370 includes one or more processing functions. One or more controllers use one or more XaaS internal interfaces 385 to manage or control one or more processing functions. The XaaS internal interface can facilitate the operable coupling between the service M / C surface component 328 and the service data plane 370. The service data plane 370 and the service M / C component 328 can belong to the same service module. Each of the one or more controllers can manage or control one or more processing functions in the one or more processing functions. Examples of such controllers managing or controlling such processing functions include: determining or configuring the location (network location) of the processing function, determining or configuring the interconnection between multiple processing functions, determining or configuring the operating parameters of the processing function, etc. This control can be performed to facilitate or ensure satisfactory or optimal performance of the XaaS service.

[0089] At least one infrastructure module 350 includes or is associated with an infrastructure M / C plane component 368 (also referred to as an infrastructure M / C plane), which can be connected to Figure 1AThe infrastructure M / C plane component 168 is the same as the infrastructure M / C plane component 168. The infrastructure module 350 can be located at the infrastructure layer 150. The infrastructure module 350 can be connected to the infrastructure M / C plane component 168. Figure 1A The infrastructure modules of the infrastructure layer 150 are the same. The services of one or more of the infrastructure modules can be used to provide M / C plane components, service M / C plane components, or both.

[0090] The infrastructure M / C plane component 368 can implement the functions of the M / C layer to manage and control the resources provided by its associated infrastructure module 350. The infrastructure M / C plane component 368 (or simply the M / C plane) includes one or more network functions (also called controllers). These network functions can be logical functions and can be dynamically deployed.

[0091] The service data planes 370 of one, some or all of the service modules 310 can be interconnected via interconnections 372. Interconnections 372 can be in the form of tunnels. Interconnections can be used to help provide the functionality of one service module as a service to another service module. Interconnections can be used to form multiple interconnected service modules, called a graph. Interconnections can be provided as a service by one or more of the infrastructure modules. Some service modules can be interconnected in this way, while others are not, thereby affecting the topology of the graph, for example, to support a given operating scenario as needed. Devices (terminals), application servers (AS), etc. can be attached or connected to the graph via other operational links as needed. For example, a terminal 393 can be connected to one service data plane 370, and an AS 395 can be connected to another service data plane 370. Multiple types of tunnels can pass through a subset of the service layer XaaS service data plane. Interconnections 372 can be managed (e.g., established, modified, configured) by MM services (provided by the task management module 140) or connection services (provided by the connection service module 122).

[0092] In various embodiments, at least one service module in the service layer may have its own data plane. In some embodiments, each service module may have its own data plane. The data planes of the service modules in the service layer may be connected together through an interconnect, which may be any type of tunnel. This facilitates flexible data plane connections.

[0093] In various embodiments, service data is sent on the graph and processed by one or more service data planes of one or more service modules to achieve the purpose of data processing. The purpose of data processing is called a task. Examples of tasks include training AI models, and collecting and analyzing data. Different tasks may involve different service modules. Two or more service modules may collaborate to complete a task. In some embodiments, a task may involve only one service module. Tasks may be created or requested by a terminal client or its M / C layer or M / C module. The use of tasks can potentially support complex processing logic, openness, and scalability. Terminals, ASs, or both can participate in the data processing of tasks. This enables terminal devices and ASs to contribute to computing and processing tasks occurring in the network. For example, a terminal device or AS may operate to support a specified task, such as a task managed by an MM module and involving one, two, or more service modules.

[0094] For example, refer again to Figure 3A , a task may involve multiple service modules 310. Related data processing may span the service data plane 370 of these multiple service modules. Interconnect 372 may facilitate communication between these multiple service modules to facilitate data processing.

[0095] In various embodiments, a service layer (e.g., Figure 1A The M / C plane 328 of the service module 310 in the service layer 110 of the infrastructure layer (e.g., Figure 1A The M / C plane 368 of the infrastructure module 350 in the infrastructure layer 150 of the embodiment of the present invention, and the M / C layer (e.g., Figure 1A The M / C modules 330 in the M / C layer 130 of the system are communicatively coupled to each other. The communicative coupling can be provided in a fully meshed form so that any two entities (M / C plane, M / C module) can communicate directly. This fully meshed interconnection can involve an entity connected to a communication bus, which (or its components) can be referred to as an inter-XaaS interface 390. Alternatively, the interconnection can be a partial interconnection, so some entities may have to communicate with each other through another entity used as a relay. The inter-XaaS interface 390 between modules potentially forms a fully meshed structure, so that any two system modules interact at the M / C level to help make optimal decisions, consistent M / C decisions, or a combination thereof. The inter-XaaS interface or associated communication bus can be provided as a service by one or more infrastructure modules in the infrastructure module, or by using the services of one or more infrastructure modules. The communication bus can directly connect components through common and shared links (buses).

[0096] The M / C module 330 can provide information about network dynamics to the controller. For example, the information can include indications of devices accessing or leaving tasks, changes in task requirements, changes in resource availability, etc. This information can influence or control the service M / C plane's decision about managing or controlling corresponding processing functions in the service data plane of the service module on a per-task basis. For example, a controller in the service M / C plane can make such a decision based at least in part on information received from the M / C layer. Thus, the M / C layer can manage, control, or coordinate the behavior of each service module in the service layer according to network dynamics so that the service layer can provide ideal good or optimal overall performance for each task.

[0097] In addition to the fact that the size of M / C modules 330 is expanded to emphasize that these modules can utilize the resources of one, some, or all of infrastructure modules 350 in their operation (provided as a service), Figure 3B and Figure 3A The same. More generally, as already explained above, each module may utilize resources (provided as services) of one, some or all of the other modules. Similarly, components of the service M / C plane 328, components of the service data plane 370, or other components may utilize resources (provided as services) of one or more other modules in the operation of these components. Similarly, a tunnel, an interface, or an interconnect may utilize resources (provided as services) of one or more other modules in its operation.

[0098] According to various embodiments, there may be many different types of business in the system. These business types can be carried by the data plane (e.g., service data plane 370), the M / C plane (e.g., service M / C plane 328), or both. One, some or all of the different modules (including service modules, M / C modules, and infrastructure modules) can carry one or more different business types. The business type can be specific to the type of module, or it can be a common type for two or more types of modules. For example, the NET4AI service module can carry data business for training AI models. The DAM service module can carry the business of raw collected data, purified data, and analyzed data. The NET4Data service can carry various data of data owners. Data owners can include end customers and providers of other XaaS services. The NET4DW service can carry data between points in the digital world. The NET4BC service can carry data blocks of blockchains.

[0099] According to various embodiments, the data plane (e.g., service data plane 370) may include a series of data processing functions for XaaS services in the service layer. These data processing functions may be new functions for 6G services in the service layer, and at least some functions may be different from 5G user plane functions (UPF).

[0100] According to various embodiments, the M / C plane (eg, the service M / C plane 328 ) may include a series of M / C functions of the XaaS service.

[0101] Various embodiments of the present disclosure support multiple operating modes. Various embodiments support or contribute to an open environment so that multiple partners jointly provide XaaS services. Partners can be providers of 6G system infrastructure and third parties that are neither customers nor infrastructure providers. In various embodiments, each provider of XaaS services is defined as a role. The system allows flexible mapping between partners and 6G system roles. Infrastructure providers can use their infrastructure (including network infrastructure, data centers, and storage infrastructure) to assume all roles of the 6G system. Infrastructure providers can only assume some of the roles and enable third parties to provide other XaaS services. Infrastructure providers can provide infrastructure as a service, and at the same time, providers can be vertical customers of the system. The flexible mapping between partners and roles enables the 6G system to adapt to various 6G system operating modes to meet different business capabilities and interests.

[0102] According to various embodiments, a module that provides functions as a service to other modules is part of a communication network. Thus, in addition to providing other potential functions (e.g., data processing or data storage), the module includes communication functions and utilizes the communication network infrastructure. A module that provides functions as a service can provide the entire functionality to one or more of its clients without requiring the client to perform additional management tasks. Instead, for example, the functionality is provided in response to a request message. A module that provides a first service can rely on other modules that provide other services to deliver the first service or to maintain its functionality, etc. Modules can rely on each other by providing services to each other (e.g., in a closed interdependent system).

[0103] In an embodiment, the XaaS model facilitates network customization and reconfiguration. New modules can be added without reconfiguring existing modules. The network can be deployed with only the modules that are needed, and the modules can be scaled up or down as needed.

[0104] According to various embodiments, modules are provided at a certain level of granularity. Again, this can be three types of modules: service modules, M / C modules, and infrastructure modules. The level of granularity is such that: there are neither too many different modules (which would lead to a high degree of complexity) nor too few modules (which would lead to a high degree of versatility for each module type). Accordingly, in various embodiments, each module is configured to provide one and only one overall common function as a service. This function is unique and is completely provided by the module (the module relies on other modules as needed to provide services for it). Therefore, from the perspective of a client using the module to access the services provided, the module is self-contained.

[0105] According to an embodiment, a service module (for example) includes all subcomponents necessary for it to receive and respond to service requests (from clients) by performing the requested services. For example, a service module may include components in a service M / C plane and components in a service data plane, which together perform all operations required by the service module. The service data plane may include submodules (e.g., computer processor submodules, data storage modules, real-world interface modules, etc.) that perform various functions required by the service module. The service data plane may also include interfaces or interconnections between these submodules.

[0106] Figure 4 It is a schematic diagram of a computing device 400 according to different embodiments of the present disclosure, and the computing device 400 can perform any or all operations of the methods and features described explicitly or implicitly herein. For example, a computer equipped with a network function can be configured as a computing device 400. One, two or more such computing devices can be coupled together to provide an embodiment of the present disclosure. A plurality of physically separated devices (for example, in the same or separate data centers) can be coupled together to provide one, two or more of such computing devices. When a device provides an infrastructure module, the device can be mainly composed of associated resources. For example, a computing module can be mainly composed of a computer processor, and a storage module can be mainly composed of a computer memory.

[0107] As shown, the device 400 may include a processor 410, such as a central processing unit (CPU) or a special processor, such as a graphics processing unit (GPU) or other such processor unit, a memory 420, a non-transient mass storage device 430, an input-output interface 440, a network interface 450, and a transceiver 460, all of which are coupled to each other by a bidirectional bus 470. According to some embodiments, any or all of the elements depicted may be utilized, or only a subset of these elements may be utilized. In addition, the device 400 may include multiple instances of certain elements, such as multiple processors, memories, or transceivers. In addition, the elements of the hardware device may be directly coupled to other elements without the need for a bidirectional bus. In addition to the processor and memory or as an alternative to the processor and memory, other electronic components such as integrated circuits may be used to perform the required logical operations.

[0108] The memory 420 may include any type of non-transitory memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), any combination thereof, etc. The mass storage element 1130 may include any type of non-transitory storage device, such as a solid-state drive, a hard disk drive, a disk drive, an optical drive, a USB drive, or any computer program product configured to store data and machine executable program code. According to some embodiments, the memory 420 or the mass storage device 430 may have recorded thereon statements and instructions that can be executed by the processor 410 to perform any of the aforementioned method operations described above.

[0109] The embodiments of the present disclosure can be implemented using electronic hardware, software or a combination thereof. In some embodiments, the present disclosure is implemented by one or more computer processors executing program instructions stored in a memory. In some embodiments, the present disclosure is implemented in part or in whole in hardware, for example, using one or more field programmable gate arrays (field programmable gate array, FPGA) or application specific integrated circuits (application specific integrated circuit, ASIC) to quickly perform processing operations.

[0110] It should be understood that although specific embodiments of the present disclosure have been described herein for illustrative purposes, various modifications may be made without departing from the scope of the present disclosure. Therefore, the specification and drawings are only to be regarded as an illustration of the present disclosure as defined by the appended claims, and are intended to cover any and all modifications, variations, combinations or equivalents falling within the scope of the present disclosure. Specifically, within the scope of the present disclosure, a computer program product or program element for storing machine-readable signals, or a program storage device or memory device such as a magnetic wire, tape, disk or light, optical tape or optical disk, etc. is provided, the signal being used to control the operation of a computer according to the method of the present disclosure, and / or to construct part or all of its components according to the system of the present disclosure.

[0111] The actions associated with the methods described herein may be implemented as coded instructions in a single computer program product. In other words, the computer program product is a computer-readable medium having software code recorded thereon, which, when loaded into a memory and executed on a microprocessor of a wireless communication device, performs the method.

[0112] Furthermore, each operation of the method may be performed on any computing device such as a personal computer, server, PDA, etc., and according to one or more or a portion of one or more program elements, modules, or objects generated from any programming language such as C++, Java, etc. Furthermore, each operation or a file or object that implements each operation, etc. may be performed by dedicated hardware or a circuit module designed for this purpose.

[0113] Through the description of the above-mentioned embodiments, the present disclosure can be implemented only by using hardware, or can be implemented by using software and necessary general hardware platforms. Based on this understanding, the technical solution of the present disclosure can be embodied in the form of a software product. The software product can be stored in a non-volatile or non-transient storage medium, and the non-volatile or non-transient storage medium can be a compact disc read-only memory (CD-ROM), a USB flash drive, or a removable hard disk. The software product includes many instructions that enable a computer device (a personal computer, a server, or a network device) to execute the method provided in the embodiment of the present disclosure. For example, such execution can correspond to the simulation of the logical operation described herein. According to the embodiment of the present disclosure, the software product may additionally or alternatively include many instructions that enable a computer device to perform operations for configuring or programming a digital logic device.

[0114] Although the present disclosure and one or more inventions associated therewith have been described with reference to specific features and embodiments, it is apparent that various modifications and combinations may be made thereto without departing from these inventions. Therefore, the specification and drawings are to be regarded only as illustrations of embodiments of the present disclosure as defined by the appended claims, and are intended to cover any and all modifications, variations, combinations or equivalents falling within the scope of the present disclosure and one or more inventions thereof.

Claims

1. A networked communication system, characterized in that: include: one or more infrastructure modules, each infrastructure module providing a corresponding infrastructure resource as a service, each infrastructure resource comprising a corresponding type of equipment for supporting the networked communication system; one or more service modules, each service module providing a corresponding function as a service and utilizing a service of at least one of the infrastructure modules; as well as one or more management and control modules, each management and control module providing a corresponding management or control function as a service and utilizing the service of at least one of the infrastructure modules, at least one of the management and control modules providing the corresponding management or control function as a service to at least one of the infrastructure modules, at least one of the service modules, or both, The one or more service modules include a connection service module for providing connection services, and / or the one or more management and control modules include a task management module for providing task management services.

2. The system according to claim 1, characterized in that Each of the service modules includes its own corresponding service management and control plane components, each of the infrastructure modules includes its own corresponding infrastructure management and control plane components, and wherein the management and control modules, the service management and control plane components and the infrastructure management and control plane components are operably coupled together via interconnection.

3. The system according to claim 2, characterized in that The interconnection forms a fully meshed network in which each of the management and control modules, the service management and control plane components, and the infrastructure management and control plane components are directly connected to each of the other of the management and control modules, the service management and control plane components, and the infrastructure management and control plane components.

4. The system according to claim 2 or 3, characterized in that: The interconnect comprises a tunnel.

5. The system according to any one of claims 2 to 4, characterized in that The interconnection is managed by the connection service module or the task management module.

6. The system according to any one of claims 1 to 5, characterized in that The management and control modules are operatively coupled to each other via an interconnect.

7. The system according to claim 6, characterized in that The service module and the infrastructure module are operably coupled to each other and to the management and control module via the interconnect.

8. The system according to claim 6 or 7, characterized in that: The interconnection forms a fully meshed network, wherein each of the service modules, the infrastructure modules, and the management and control modules involved in the interconnection is directly connected to each other of the service modules, the infrastructure modules, and the management and control modules involved in the interconnection through a separate corresponding communication link; or the interconnection forms a communication bus, in which each of the service modules, the infrastructure modules, and the management and control modules involved in the interconnection is directly connected to each other of the service modules, the infrastructure modules, and the management and control modules involved in the interconnection through the communication bus.

9. The system according to any one of claims 1 to 8, characterized in that At least one of the service modules includes a service management and control plane component and a service data plane component operatively coupled to the service management and control plane component.

10. The system according to claim 9, characterized in that The service management and control plane components are provided as a service using, at least in part, one or more of the management and control modules.

11. The system according to claim 9 or 10, characterized in that: The service data plane component is provided as a service using, at least in part, two or more of the infrastructure modules.

12. The system according to any one of claims 9 to 11, characterized in that Two or more of the service data plane components in two or more of the service modules are communicatively coupled together via respective interconnects.

13. The system according to claim 12, characterized in that The interconnection is managed by the connection service module or the task management module or a combination thereof.

14. The system according to claim 12 or 13, characterized in that The interconnect is a tunnel.

15. The system according to any one of claims 1 to 14, characterized in that At least one of the service modules is provided as a service using, at least in part, two or more of the infrastructure modules.

16. The system according to any one of claims 1 to 15, characterized in that The connection service module and the task management module are integrated together.

17. The system according to claim 1, characterized in that Each of the service modules includes its own corresponding service management and control plane component, and wherein the service management and control plane components are operably coupled together, or the management and control modules are operably coupled together, or the service management and control plane components are operably coupled to the management and control modules, or a combination thereof.

18. The system according to any one of claims 1 to 17, characterized in that At least one of the infrastructure modules provides the corresponding infrastructure resource as a service to at least one of: another of the infrastructure modules; and one of the management and control modules.

19. The system according to any one of claims 1 to 18, characterized in that At least one of the service modules provides the corresponding function as a service to at least one of: another service module of the service modules; one of the infrastructure modules; and one of the management and control modules.

20. The system according to any one of claims 1 to 19, characterized in that At least one of the management and control modules provides the corresponding management or control function as a service to another management and control module of the management and control modules.

21. The system according to any one of claims 1 to 20, characterized in that The same party provides or operates at least one of the infrastructure modules and at least one of the management and control modules, or wherein the same party provides or operates multiple or all of the management and control modules, or wherein the same party provides or operates at least one of the service modules and at least one of the management and control modules.

22. The system according to any one of claims 1 to 21, characterized in that The infrastructure module includes one or more of the following: a ground communication module; a non-ground communication module; a cloud module; a cache module; a sensor module; a radio access network module; a core network module; a data center module; and a database module.

23. The system according to any one of claims 1 to 22, characterized in that The service module includes one or more of the following: an artificial intelligence network module; a data network module; a blockchain network module; a data analysis and management module; a module providing vertical services; and a digital world network module.

24. The system according to any one of claims 1 to 23, characterized in that The management and control module includes one or more of the following: resource management module; protocol management module; connection management module; strategy and customer service management module; CONET module; Network security management module; service provision management module; And network security management module.

25. The system according to any one of claims 1 to 24, characterized in that The infrastructure module, the service module, and at least one of the management and control modules operate according to an open system architecture in which the at least one module responds to inputs in a standardized manner that is common across multiple modules of the system or implementations of the system.

26. The system according to any one of claims 1 to 25, characterized in that The management and control module includes a task management module configured to interoperate with one or more of the service modules to perform a task, the task including a set of tasks or operations.

27. The system according to claim 26, characterized in that The task management module interoperates with two or more of the service modules to perform the task, and wherein the task management module causes one or more interconnections to be established between the two or more of the service modules to support the task.

28. A system according to any one of claims 26 to 27, characterized in that One or more terminals, application servers, or both are operatively coupled to the one or more of the service modules and operate to support the tasks.

29. A method, characterized in that include: providing one or more infrastructure resources as a service using the corresponding one or more infrastructure modules, each infrastructure resource comprising a corresponding type of equipment for supporting the networked communication system; providing one or more functions as services using corresponding one or more service modules, at least one service module utilizing services of at least one of the infrastructure modules; as well as providing one or more management or control functions as a service using one or more management and control modules, at least one of the management and control modules providing the corresponding management or control function as a service to at least one of the infrastructure modules, at least one of the service modules, or both, The one or more service modules include a connection service module for providing connection services, and the one or more management and control modules include a task management module for providing task management services, or both.

30. The method according to claim 29, characterized in that Each of the service modules includes its own corresponding service management and control plane components, each of the infrastructure modules includes its own corresponding infrastructure management and control plane components, and wherein the management and control modules, the service management and control plane components and the infrastructure management and control plane components are operably coupled together via interconnection.

31. The method according to claim 30, characterized in that The interconnection forms a fully meshed network in which each of the management and control modules, the service management and control plane components, and the infrastructure management and control plane components are directly connected to each of the other management and control modules, the service management and control plane components, and the infrastructure management and control plane components.

32. The method according to claim 30 or 31, characterized in that The interconnect comprises a tunnel.

33. The method according to any one of claims 30 to 32, characterized in that The interconnection is managed by the connection service module or the task management module.

34. The method according to any one of claims 29 to 33, characterized in that The management and control modules are operatively coupled to each other via an interconnect.

35. The method according to claim 34, characterized in that The service module and the infrastructure module are operably coupled to each other and to the management and control module via the interconnect.

36. The method according to claim 34 or 35, characterized in that The interconnection forms a full mesh network, in which each of the service modules, the infrastructure modules, and the management and control modules involved in the interconnection is directly connected to each other of the service modules, the infrastructure modules, and the management and control modules involved in the interconnection through a separate corresponding communication link; or the interconnection forms a communication bus, in which each of the service modules, the infrastructure modules, and the management and control modules involved in the interconnection is directly connected to each other of the service modules, the infrastructure modules, and the management and control modules involved in the interconnection through the communication bus.

37. The method according to any one of claims 29 to 36, characterized in that At least one of the service modules includes a service management and control plane component and a service data plane component operatively coupled to the service management and control plane component.

38. The method according to claim 37, characterized in that The service management and control plane components are provided as a service using, at least in part, one or more of the management and control modules.

39. The method according to claim 37 or 38, characterized in that The service data plane component is provided as a service using, at least in part, two or more of the infrastructure modules.

40. The method according to any one of claims 37 to 39, characterized in that Two or more of the service data plane components in two or more of the service modules are communicatively coupled together via respective interconnects.

41. The method according to claim 40, characterized in that The interconnection is managed by the connection service module or the task management module or a combination thereof.

42. The method according to claim 40 or 41, characterized in that The interconnect is a tunnel.

43. The method according to any one of claims 29 to 42, characterized in that At least one of the service modules is provided as a service using, at least in part, two or more of the infrastructure modules.

44. A method according to any one of claims 29 to 43, wherein: The connection service module and the task management module are integrated together.

45. The method according to claim 29, characterized in that Each of the service modules includes its own corresponding service management and control plane component, and wherein the service management and control plane components are operably coupled together, or the management and control modules are operably coupled together, or the service management and control plane components are operably coupled to the management and control modules, or a combination thereof.

46. ​​The method according to any one of claims 29 to 45, characterized in that At least one of the infrastructure modules provides the corresponding infrastructure resource as a service to at least one of: another of the infrastructure modules; and one of the management and control modules.

47. The method according to any one of claims 29 to 46, characterized in that At least one of the service modules provides the corresponding function as a service to at least one of: another service module of the service modules; one of the infrastructure modules; and one of the management and control modules.

48. The method according to any one of claims 29 to 47, characterized in that At least one of the management and control modules provides the corresponding management or control function as a service to another management and control module of the management and control modules.

49. The method according to any one of claims 29 to 48, characterized in that The same party provides or operates at least one of the infrastructure modules and at least one of the management and control modules, or wherein the same party provides or operates multiple or all of the management and control modules, or wherein the same party provides or operates at least one of the service modules and at least one of the management and control modules.

50. The method according to any one of claims 29 to 49, characterized in that The infrastructure module includes one or more of the following: a ground communication module; a non-ground communication module; a cloud module; a cache module; a sensor module; a radio access network module; a core network module; a data center module; and a database module.

51. The method according to any one of claims 29 to 50, characterized in that The service module includes one or more of the following: an artificial intelligence network module; a data network module; a blockchain network module; a data analysis and management module; a module providing vertical services; and a digital world network module.

52. The method according to any one of claims 29 to 51, characterized in that The management and control module includes one or more of the following: resource management module; protocol management module; connection management module; strategy and customer service management module; CONET module; Network security management module; service provision management module; And network security management module.

53. The method according to any one of claims 29 to 52, characterized in that The infrastructure module, the service module, and at least one of the management and control modules operate according to an open system architecture in which the at least one module responds to inputs in a standardized manner that is common across multiple modules of the system or implementations of the system.

54. The method according to any one of claims 29 to 53, characterized in that The management and control module includes a task management module configured to interoperate with one or more of the service modules to perform a task, the task including a set of tasks or operations.

55. The method according to claim 54, characterized in that The task management module interoperates with two or more of the service modules to perform the task, and wherein the task management module causes one or more interconnections to be established between the two or more of the service modules to support the task.

56. The method according to any one of claims 54 to 55, characterized in that One or more terminals, application servers, or both are operatively coupled to the one or more of the service modules and operate to support the tasks.

57. A computer program product, characterized in that A non-transitory computer-readable medium having stored thereon statements and instructions which, when executed by one or more computer processors, cause the computer processors to perform the method of any one of claims 29 to 56.

Images