Cloud-based X-centric network implementation architecture

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. A cloud-based implementation of an X-centric network architecture is provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of prior filed U.S. provisional patent application No. 63 / 402,309, filed on August 30, 2022, and entitled “CLOUD BASED AND X-CENTRIC NETWORK IMPLEMENTATION ARCHITECTURE,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present invention generally relates 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 only. th The 6th Generation (6G) system will provide not only connectivity but also 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 used internally by the system (e.g., the operator) or by end customers.

[0005] Cloud-based technologies allow resources to be pooled and shared across the network using virtualization techniques. Cloud-based technologies are expected to become an important aspect of future networks in addition to the cellular network infrastructure deployed by traditional networks. New services, such as artificial intelligence or data services provided by third parties, are likely to become widely used, and cloud-based technologies and network implementation architectures that support multiple services are expected to become more important to support such services.

[0006] However, current wireless systems and infrastructure need to be further developed to support the above and similar scenarios. This development is not simple and may require solving various technical and design problems.

[0007] Therefore, a method, apparatus and system for network implementation is needed to eliminate or alleviate one or more limitations in the prior art.

[0008] This background information is intended to provide information that may be relevant to the present disclosure. It is not necessarily an admission, nor should it be construed, that any of the foregoing information constitutes prior art against the present disclosure. Summary of the invention

[0009] Embodiments of the present disclosure provide a cloud-based network implementation. Embodiments may also relate to 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 herein as an X-centric architecture. In addition, embodiments may be provided as an open system architecture. Embodiments may be scalable, allowing unknown future services to be dynamically enabled or provided, substantially without modifying or redesigning the system architecture. To facilitate 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. Modular design may allow new service modules to be dynamically added to enable or provide or support associated new XaaS services.

[0010] 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 of which has at least a processor, a network interface and a memory. The system includes one or more infrastructure modules, each of which provides corresponding infrastructure resources as a service. The system includes one or more service modules, each of which provides corresponding functions as a service and utilizes at least one of the infrastructure resources as a service. Each infrastructure resource may include a corresponding type of device for supporting the networked communication system. The system includes one or more control and management (C / M) modules, each of which provides corresponding management or control resources as a service, and at least one of the control and management modules provides the corresponding management or control resources (also referred to as functions) as a service to at least one of the infrastructure modules or the service modules. The system may also include one or more gateways, the one or more gateways providing a secure connection with the infrastructure module, the service module and some or all of the control and management modules, and facilitating the interaction between the infrastructure module, the service module and some or all of the control and management modules. Part or all of the infrastructure module, the service module, the control and management module, and the gateway may be implemented using virtualized resources provided by one or more clouds.

[0011] In some embodiments, the system includes a C / M-plane interface gateway (gateway, GW) or a trusted gateway (trustworthy gateway, TW-GW), which is configured as an intermediary for interconnecting the infrastructure modules, the service modules, and part or all of the control and management modules residing in the same cloud of the multiple clouds. The interconnection may include the interconnection of the control and management functions of the modules. In some other embodiments, part or all of the infrastructure modules, the service modules, and the control and management modules are implemented in multiple clouds. In these embodiments, the system also includes: a different corresponding C / M-plane interface gateway (gateway, GW) or a trusted gateway (trustworthy gateway, TW-GW) in each of the multiple clouds. Different corresponding C / M-plane interface gateways (gateway, GW) or trusted gateways (trustworthy gateway, TW-GW) are coupled together to interconnect the infrastructure modules, the service modules, and different modules in the control and management modules residing in different clouds of the multiple clouds. In other further embodiments, the C / M plane interface gateway (gateway, GW) or trusted gateway (trustworthy gateway, TW-GW) is configured to operate as a signal message forwarding function (with or without conversion) to facilitate an interface between one or more pairs of modules, each pair of modules is selected from the one or more infrastructure modules, the one or more service modules and the one or more control and management modules, and the interface is a direct logical interface. In other further embodiments, the C / M plane interface gateway (gateway, GW) or trusted gateway (trustworthy gateway, TW-GW) is configured to operate as a signal message converter to facilitate an interface between one or more pairs of modules, each pair of modules is selected from the one or more infrastructure modules, the one or more service modules and the one or more control and management modules. The signal message converter can change the content of the message forwarded between the one or more pairs of modules.

[0012] In some embodiments, the C / M plane interface gateway (gateway, GW) or trusted gateway (trustworthygateway, TW-GW) is also configured to communicatively couple the infrastructure module, the service module, and part or all of the control and management modules to a C / M plane connection, and the C / M plane connection is used for control plane message transmission between the client device, the server, and part or all of the infrastructure module, the service module, and the control and management module.

[0013] In some embodiments, the C / M plane interface GW or TW-GW is configured to control access to one or more of the infrastructure module, the service module, and the control and management module, and the aforementioned attempted access is performed by one or more other modules of the infrastructure module, the service module, and the control and management module or by another device. In some embodiments, the C / M plane interface gateway (gateway, GW) or trusted gateway (trustworthy gateway, TW-GW) is configured to: receive a request to a first module of the infrastructure module, the service module, and the control and management module to use a specified service; determine a second module of the infrastructure module, the service module, and the control and management module, the second module provides the specified service, and the first module is authorized to receive the specified service from the second module; forward the request to the second module.

[0014] In some embodiments, the system further includes a data plane interface gateway (gateway, GW) or a trusted gateway (trustworthy gateway, TW-GW), wherein the data plane interface GW or TW-GW is configured as an intermediary for interconnecting some or all of the service modules with a data plane connection, wherein the data plane connection is used for data transmission between a client device, a server, and some or all of the modules in the infrastructure module, the service module, and the control and management module. The data plane interface GW or TW-GW can interconnect the data processing functions of the modules. In some other embodiments, the aforementioned part or all of the service modules in the service module are implemented in multiple clouds, and the system further includes: a different corresponding data plane interface gateway (gateway, GW) or a trusted gateway (trustworthy gateway, TW-GW) in each of the multiple clouds. Different corresponding data plane interface gateways (gateway, GW) or trusted gateways (trustworthy gateway, TW-GW) are coupled together to interconnect different service modules residing in different clouds of the multiple clouds. In some further embodiments, one or more of the different corresponding data plane interface gateways (gateways, GW) or trusted gateways (trustworthy gateways, TW-GW) are used to provide a 6G data plane that interconnects one or more of the service modules with one or more client devices, and the interconnection uses the data plane connection. In some further embodiments, the 6G data plane is instantiated to support tasks involving one or more service modules of the interconnection. The task may require joint contributions from one or more service modules. In some further embodiments, the data plane interface GW or TW-GW is configured to control access to one or more modules in the infrastructure module, the service module, and the control and management module, and the attempted access is performed by one or more other modules in the infrastructure module, the service module, and the control and management module or by another device.

[0015] In some embodiments, the infrastructure module, the service module, and the control and management module include a first group of modules implemented using virtualized resources provided by a first cloud and a second group of modules implemented using virtualized resources provided by a second cloud, and the first group of modules are organized and interconnected in the same manner as the second group of modules.

[0016] In some embodiments, the system further includes a C / M plane interface GW or TW-GW and a data plane interface GW or TW-GW. The C / M plane interface GW or TW-GW is configured as an intermediary for interconnecting the infrastructure module, the service module, and the control and management module residing in the same cloud of the multiple clouds through a dedicated and secure connection. The data plane interface GW or TW-GW is configured as another intermediary for interconnecting the infrastructure module, the service module, and part or all of the control and management modules with the data plane connection through another dedicated and secure connection. The data plane connection is used for data transmission between client devices, servers, and part or all of the infrastructure modules, the service modules, and the control and management modules. The infrastructure module, the service module, the control and management module, the C / M plane interface GW or TW-GW, and the data plane interface GW or TW-GW together form part or all of the basic architecture structure (basic architecture structure, BAS). In some other embodiments, the system also includes one or more additional BASs having the same structure as the BAS, and the BAS is interconnected with the additional BAS. In some further embodiments, the same cloud of the multiple clouds and its physical infrastructure form part or all of the BAS domain. In some further embodiments, the system further comprises: another C / M plane interface gateway (gateway, GW) or a trusted gateway (trustworthy gateway, TW-GW), forming part of another BAS and connected to the C / M plane interface GW or TW-GW of the BAS; another data plane interface GW or TW-GW, forming part of the other BAS and connected to the data plane interface GW or TW-GW of the BAS.

[0017] In some embodiments, the system serves at least one device implemented at least in part using virtualized resources provided by the one or more clouds or provided by another cloud. Additionally or alternatively, the device can be configured to include: one or more additional infrastructure modules, each of which provides a corresponding infrastructure resource as a service; one or more additional service modules, each of which provides a corresponding function as a service and utilizes at least one of the infrastructure resources as a service; one or more additional control and management modules, each of which provides a corresponding additional management or control resource as a service, at least one of the additional control and management modules providing the corresponding additional management or control resource as a service to at least one of the additional infrastructure modules or the additional service modules.

[0018] According to an embodiment of the present disclosure, a method is provided, for example, 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 services; using one or more corresponding service modules to provide one or more functions as services, at least one service module uses at least one of the infrastructure resources as a service; using one or more corresponding control and management modules to provide one or more management or control resources as services, at least one of the control and management modules provides the corresponding management or control resources as services to at least one of the infrastructure modules or the service modules. The method may also include providing one or more gateways, the one or more gateways providing a secure connection with the infrastructure module, the service module, and some or all of the control and management modules, and facilitating the interaction between the infrastructure module, the service module, and some or all of the control and management modules. The infrastructure module, the service module, and some or all of the control and management modules can be implemented using virtualized resources provided by one or more clouds. Other aspects of the method are similar to the aspects of the system described above.

[0019] For example, the method may include providing a C / M plane interface gateway (gateway, GW) or a trusted gateway (trustworthy gateway, TW-GW) as one or more of the gateways, the C / M plane interface GW or the trusted gateway TW-GW being configured as an intermediary for interconnecting the infrastructure modules, the service modules, and part or all of the control and management modules (e.g., control and management functions thereof) residing in the same cloud of the multiple clouds. The method may include implementing the infrastructure modules, the service modules, and part or all of the control and management modules in multiple clouds, and the method further includes: providing a different corresponding C / M plane interface gateway (gateway, GW) or a trusted gateway (trustworthy gateway, TW-GW) in each of the multiple clouds, wherein the different corresponding C / M plane interface gateways (gateway, GW) or trusted gateways (trustworthy gateway, TW-GW) gateways are coupled together for interconnecting different modules of the infrastructure modules, the service modules, and the control and management modules residing in different clouds of the multiple clouds. The method may include: configuring the C / M plane interface gateway (gateway, GW) or trusted gateway (trustworthy gateway, TW-GW) to operate as a signal message forwarding function to facilitate an interface between one or more pairs of modules, each pair of modules is selected from the one or more infrastructure modules, the one or more service modules and the one or more control and management modules, and the interface is a direct logical interface. The method may include: configuring the C / M plane interface gateway (gateway, GW) or trusted gateway (trustworthy gateway, TW-GW) to operate as a signal message converter to facilitate an interface between one or more pairs of modules, each pair of modules is selected from the one or more infrastructure modules, the one or more service modules and the one or more control and management modules. The method may include configuring the C / M plane interface gateway (gateway, GW) or trusted gateway (trustworthy gateway, TW-GW) to communicatively couple the infrastructure module, the service module, and some or all of the control and management modules to a C / M plane connection, wherein the C / M plane connection is used for control plane message transmission between a client device, a server, and some or all of the infrastructure module, the service module, and the control and management module.The method may include providing a data plane interface gateway (gateway, GW) or a trustworthy gateway (TW-GW), wherein the data plane interface GW or TW-GW is configured as an intermediary for interconnecting part or all of the service modules (e.g., their data processing functions) with data plane connections, wherein the data plane connections are used for data transmission between client devices, servers, and part or all of the infrastructure modules, the service modules, and the control and management modules. The method may include: implementing the part or all of the service modules in multiple clouds, providing a different corresponding data plane interface gateway (gateway, GW) or a trustworthy gateway (TW-GW) in each of the multiple clouds, wherein different corresponding data plane interface gateways (gateway, GW) or trustworthy gateways (TW-GW) are coupled together to interconnect different service modules residing in different clouds. In some embodiments, one or more of the different corresponding data plane interface gateways (gateways, GW) or trusted gateways (trustworthy gateways, TW-GW) are used to provide a 6G data plane that interconnects one or more of the service modules with one or more client devices, and the interconnection uses the data plane connection. In some embodiments, the 6G data plane is instantiated to support tasks of one or more service modules involving the interconnection in the service module. In some embodiments, the infrastructure module, the service module, and the control and management module include a first group of modules implemented using virtualized resources provided by a first cloud and a second group of modules implemented using virtualized resources provided by a second cloud, wherein the first group of modules is organized and interconnected in the same manner as the second group of modules. The method may include serving at least one device that is at least partially implemented using virtualized resources provided by one or more of the clouds or provided by another cloud.

[0020] According to an embodiment of the present disclosure, a computer program product is provided, including a (eg, non-transitory) computer-readable medium storing statements and instructions, which, when executed by one or more computer processors, cause the computer processors to perform the above method. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0025] Figure 3 The 3GPP 5G network implementation architecture according to the prior art is shown.

[0026] Figures 4A to 4C A cloud-based X-centric network system according to an embodiment of the present disclosure is shown.

[0027] Figure 4D A unified Basic Architecture Structure (BAS) according to an embodiment of the present disclosure is shown.

[0028] Figure 4E The relationship between the system BAS and the XaaS BAS in the service layer according to an embodiment of the present disclosure is shown.

[0029] Figure 4F The relationship between the system BAS and the XaaS BAS in the C / M layer according to an embodiment of the present disclosure is shown.

[0030] Figure 4G The interconnections between BASs according to an embodiment of the present disclosure are shown.

[0031] Figure 4H Multiple interconnected BASs in different clouds are shown according to an embodiment of the present disclosure.

[0032] Fig. 4I An X-centric network architecture according to an embodiment of the present disclosure is shown.

[0033] Figure 5A A communication system including interconnected BASs and supporting backward compatibility according to an embodiment of the present disclosure is shown.

[0034] Figure 5B A communication system including interconnected BASs according to another embodiment of the present disclosure is shown.

[0035] Figure 5C A communication system including interconnected BASs according to another embodiment of the present disclosure is shown.

[0036] Figures 6A to 6C The 6G data plane is added according to an embodiment of the present disclosure. Figures 4A to 4C system.

[0037] Fig.6D for Figures 6A to 6C Another representation of .

[0038] Fig. 7A A C / M plane interface for a service based interface (SBI) according to an embodiment of the present disclosure is shown.

[0039] Figure 7B A C / M plane interface for a service based interface (SBI) according to another embodiment of the present disclosure is shown.

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

[0041] It should be noted that throughout the drawings, similar features are identified by similar reference numerals. DETAILED DESCRIPTION

[0042] As used herein, the term "everything as a service", or "XaaS", may reflect concepts that have been proposed in 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, and provide various functions in combination with a service model. According to an embodiment of the present disclosure, XaaS may describe that, for example, 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 as a synonym for "as a service".

[0043] Open systems architecture may refer to a design approach in which systems (e.g., modules) are interoperable and interconnectable, generally without modification or redesign. Open systems architecture is an approach to modular design in which modules are configured to interoperate. Open systems architecture may involve modules that respond to known inputs in known ways, for example, performing actions or providing responses to queries, inputs, or stimuli 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 way to provide such functionality. Services may be provided by servers to clients, so an "as a service" model may involve a server-client model.

[0044] According to an embodiment of the present disclosure, an X-centric network implementation is provided that is provided at least in part using cloud-based (e.g., virtualized and networked) resources. The cloud-based implementation can be viewed as a specific implementation of a more general X-centric network architecture, such as the X-centric network architecture described in the accompanying drawings. Figure 1A Described below. Figure 1A The X-centric architecture and related technologies are described in U.S. patent application No. 63 / 347,365 filed on May 31, 2022, the entire contents of which are incorporated herein by reference. Figure 1A The X-centric architecture in can be viewed separately from various implementation scenarios, such as the implementation scenario of the present disclosure. Figure 2 More details of the X-centric architecture are shown and described below.

[0045] The term "X-centric" may refer to the ability of embodiments to be reconfigured so that they are infrastructure provider-centric, third-party-centric, customer-centric, etc., or a combination thereof. Other types of configurations may also be supported. Thus, multiple possible mappings between parties and roles are supported, with different X-centric scenarios corresponding to different mappings. This promotes the openness of the architecture and supports multiple operational scenarios. A configuration may be entity-centric in that the configuration points to a certain goal related to that entity. An architecture may be X-centric in that the architecture may be configured into any of a variety of such configurations.

[0046] According to an embodiment, the unified interface is deployed in each of the radio access network (RAN), the core network (CN), and a third-party cloud-based network. In fact, each of these networks (e.g., RAN and CN) and other networks can be cloud-based networks. Due to the existence of such cloud-based networks, the traditional connection-centric network implementation architecture is adjusted to a cloud-centric implementation architecture. Therefore, an embodiment of the present disclosure provides a cloud-based X-centric implementation architecture. This can be compared with the following reference Figure 3The 5G implementation architecture described in the present disclosure is in contrast to, and may be built on top of, the architecture. The unified interface may be an inter-BAS interface, facilitating interactions between different BASs, e.g. in different clouds. In previous implementations, the RAN interface and the CN interface were defined based on their infrastructure-specific deployment and functionality. For a cloud-based implementation, the RAN, CN and possibly even the devices may use a similar “infrastructure”, e.g. a cloud infrastructure, even though the cloud may be deployed on top of the RAN, CN and the devices. In this way there is little difference, as all XaaS services may be implemented in these clouds regardless of where these clouds are deployed. Accordingly, a common basic architecture structure (BAS) may be defined, which defines the XaaS services and the GW that facilitates the interactions between these XaaS services.

[0047] As described above, various embodiments relate to cloud-based networks. Traditional cellular network portions, such as RAN and CN, can be implemented using multiple functions implemented in the cloud, such as using networked resources configured through virtualization technology. Basically universal networked resources can be provided, added, and configured as needed. These resources can be owned by one or more entities. Third-party cloud infrastructure can be part of the network. Even end-user devices can be partially or fully implemented in the cloud. In some embodiments, a first party can access, scale, and utilize virtualized resources provided by the cloud, while another one or more parties manage the cloud infrastructure itself. This can reduce the overhead requirements of the first party.

[0048] Embodiments of the present disclosure relate to a networked computing and communication system, which includes multiple different types of modules in an open system architecture. On one layer, infrastructure modules all provide corresponding infrastructure resources as services. Infrastructure resources may include actual computing, communication or data storage resources. On another layer, service modules all 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, control and management modules all provide corresponding management or control resources as services. Control and management resources may be used to manage other modules, module tasks, module operations, or other management or control tasks. At least one of the control and management modules may provide its corresponding management or control resources as services to at least one of the infrastructure modules or service modules. Each module may provide its functions as services to one, some or all modules of the same layer or different layers as needed. The modules may be interconnected to provide services to each other in a configurable manner according to operational requirements. Different modules may be provided or operated by different participants to provide different X-centric configurations, which may be participant-centric configurations.

[0049] 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 control and management (C / M) 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, wherein there are XaaS modules in each layer, which can promote openness and scalability.

[0050] The service layer 110 includes one or more service modules. Service modules may be included or excluded as required by a particular operational scenario. As new service modules are developed, they may be included in the existing architecture or implementation of the network.

[0051] As an example, Figure 1A Various possible service modules are shown. These examples are not necessarily limiting. In fact, embodiments of the present disclosure are capable of hosting service modules that have not yet been conceptualized, and such modules can be added when developed or needed. Similarly, these modules can be omitted when not needed. NET4AI module 112 provides NET4AI services; NET4Data module 114 provides NET4Data services; NET4BC module 116 provides NET4BC services; DAM module 118 provides DAM services; one or more vertical modules 120 provide one or more associated vertical services; connection service module 122 provides connection services. A description of each of these modules is provided below. Each module can be provided (e.g., operated) by a different participant, or multiple modules can be provided (e.g., operated) by the same participant. Service modules (e.g., any of the above service modules) 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 C / M modules in C / M layer 130, other service modules in service layer 110, or a combination thereof. Service modules can provide services to other service modules in substantially 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 external users or clients.

[0052] The NET4AI service provided by the NET4AI (network for artificial intelligence) module 112 can be described as follows. The NET4AI service provides some or all of the following functions: artificial intelligence (AI) model customization and management, AI model distribution and parallelization, AI model training, and inference optimization. The NET4AI module helps to 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 C / M module 130.

[0053] The NET4Data service provided by the NET4Data (network for data) module 114 can be described as follows. The NET4Data service provides some or all of the following functions: 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 an end user or the data of another service module 110 or any C / M module 130. The NET4Data service can store data in one or more computer memories, and can manage functions such as data integrity and backup, data redundancy, and data retrieval speed optimization. The NET4Data service can also provide data sharing functions.

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

[0055] The DAM services provided by the DAM (data analytics and management) module 118 can be described as follows. The DAM services provide some or all of the following functions: 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 functions.

[0056] 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. Processing data traffic of vertical (e.g., V2X, metaverse) customers. Vertical services can generally be described as services associated with vertical service providers. Vertical service providers can provide one or more professional products or services in a certain field. Examples of vertical service areas include banking, manufacturing, education, real estate, government, or legal industries.

[0057] The connection services provided by the connection service module 122 can help provide data connections between devices or endpoints. For example, data connections 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 traffic of the end user, such as voice traffic or application layer data. The connection service may include a 6G connection service. In some embodiments, the connection service module 122 is integrated with the task management module 140. 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.

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

[0059] 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) the included network function.

[0060] In various embodiments, the service has its own data process, which is implemented by some or all of the network functions in 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.

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

[0062] As an example, Figure 1AVarious possible C / M modules are shown. These examples are not necessarily limiting. Resource management (RM) module 132 provides RM services. Protocol management (PM) module 134 provides PM services. Connectivity management (C / M) module 136 provides connectivity services. Policy and customer service management (CSM) module 138 provides policy and CSM services. Mission management (MM) module 140 provides MM services, where the missions are 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 C / M module can be provided by a different participant. One or more C / M modules can be provided by the same participant. The C / M module (e.g., any of the above-mentioned C / M modules) can provide C / M 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 C / M modules in the C / M layer 130, etc. or a combination thereof.

[0063] 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. The 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.

[0064] 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 adjustment 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 predefined for selection on demand. The protocol stack can be designed on demand.

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

[0066] 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 (traffic protection), authorization, service level agreement (SLA) management, SLA execution, policy / rule / regulatory guarantees, installment payments (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 C / M layer, a participant operating in the infrastructure, etc. or a combination thereof. These participants can all have one or more roles as described elsewhere in this document, for example, regarding the described X-centric scenario.

[0067] The MM service provided by the MM module 140 can be described as follows. The MM service (or the MM module providing the MM service) can, for example, convert the data processing of one or more related service modules in the service layer into a task according to a request. The MM service can manage (e.g., establish, modify and configure) the communication tunnels between the service data planes of the related service modules to support the task. The task can be, as described elsewhere in this document, for example, related to cross-layer interaction and cross-service interaction. 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 (e.g., establish, modify and configure) the communication tunnels 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. A task can be a service provided to a customer. A task can be a service type provided by a single service or provided using contributions from multiple services. The MM service provides the ability to configure the provision of XaaS services at the service layer to provide task services. In some embodiments, 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.

[0068] The CONET services provided by the CONET module 142 can be described as follows. The CONET service can provide or facilitate the establishment of a trust alliance, the joining or leaving of alliance members, and blockchain management including creation, updating, and deletion. The CONET service can also be referred to as a network blockchain (BC4NET) service. CONET refers to an alliance network. The CONET service can involve or facilitate the formation of an alliance, mutual authentication and mutual authorization between partners, and negotiation of agreements on recording and tracing selected actions performed by these partners. The purpose of this is to provide a trusted environment for system operations.

[0069] 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 or for their infrastructure assets.

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

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

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

[0073] 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, for example, a satellite network communication module. The infrastructure module may include a cloud module 156, for example, a data center network. The infrastructure module may include a cache module 158, for example, a cache node. The infrastructure module may include a sensor module 160, for example, a sensor node or a sensor network.

[0074] 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 modules, or operating modules that have been provided. An infrastructure module (for example, any of the above-mentioned infrastructure modules) can provide infrastructure services (in the form of resources) to end customers (users), the service layer or its modules, the C / M layer or its modules, 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.

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

[0076] Figure 1B The embodiment shown has Figure 1A The same components and some additional components are described in detail. 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 C / M 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.

[0077] 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 data center infrastructure module operates similarly to the cloud module 156 to provide data center or related capabilities. The database infrastructure module can similarly provide, for example, database-specific capabilities in the form of one or more databases responding to database queries or data storage operations.

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

[0079] The service provision management module 146 in the C / M layer can provide 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 strategy, key management, QoS guarantee and billing between any pair of XaaS service providers and customers. Customers in this sense can include end customers in the physical world, digital representatives in the digital world, or both.

[0080] In various embodiments, the XaaS service in the C / M layer 130 supports the control and management of the 6G system itself, and also provides support to vertical domains upon request. An example is that the RM service 132 can provide air resource management services for the RAN, and can also provide services to vertical domains so that the vertical domains can allocate air resources to their end customers. The XaaS module in the C / M layer 130 can be deployed using slicing technology.

[0081] The NET4DW service module 124 in the service layer provides digital world functions and related services. Digital world functions and related services (i.e., digital world services for short) provide the ability to build, control and manage the digital world. The digital world is defined as the digital realization of the physical world. Digital worlds such as the metaverse provide interactive multi-user environments designed to simulate the 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 to provide users with an immersive experience. The NET4DW service module can process digital world participant data to facilitate this experience, acquire and utilize network resources so that the experience reaches the desired quality, manage participation, guide user experience, etc.

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

[0083] In addition to supporting XaaS services at service layer 110, 6G embodiments 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 enable their operations, while each XaaS service provides its capabilities to 6G customers.

[0084] In various embodiments, any pair of XaaS services of the 6G system can be mutual customers and providers of each other. A first service can have a second service as a direct or indirect customer, and the first service can also be a direct or indirect customer of the second service. A first service can directly or indirectly depend on other services, which in turn 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 to perform its resource management for vertical slices; CONET services and NET4Data services can use the capabilities provided by NET4BC to perform their operations.

[0085] The use of modules such as service modules, C / M modules, and infrastructure modules can promote the customizability of the architecture disclosed in this article. Modules can be provided as needed, leaving out unnecessary modules. This can streamline and simplify the implementation of the architecture. In addition, when 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 promotes the reconfigurability of the architecture at any time.

[0086] Different system modules (e.g., service module, C / M module, infrastructure module) as described above can be provided by different participants. Participants can be business entities, "participants", 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. The three different roles that participants can assume include: service layer XaaS provider, C / M layer XaaS provider, and infrastructure layer XaaS provider. A participant that provides at least one service module at the service layer assumes the role of a service layer XaaS provider. A participant that provides at least one C / M module at the C / M layer assumes the role of a C / M layer XaaS provider. A participant that provides at least one infrastructure module assumes the role of an infrastructure layer XaaS provider. Participants can provide modules at more than one layer, thereby assuming multiple roles.

[0087] Embodiments of the present disclosure also demonstrate cross-layer interaction, cross-service interaction, or both. Figure 2 An embodiment of the present disclosure is shown, in which a service module 210 includes a service C / M plane component 228 and a service data plane 270 (or is associated therewith). The service C / M plane component 228 can implement the functions of the C / M layer for managing and controlling the service data plane 270. Each service C / M plane component 228 and service data plane 270 can be dedicated to a single specific service module 210. The service C / M plane component 228 (or simply the service C / M plane, or C / M plane) can include one or more network functions (referred to as controllers). The service data plane 270 (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 210 can be associated with Figure 1A The service modules of the service layer 110 are the same.

[0088] In various embodiments, one or both of two types of processing functions may be included in the service data plane 270. 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, traffic detection, traffic gating, etc. Accordingly, the service data plane 270 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 270 includes only data processing functions, and the connection plane is optional. In some embodiments, the service data plane 270 includes only header processing functions, and the processing plane is optional, for example, when the service module 210 is a connection service module such as the connection service module 122.

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

[0090] In various embodiments, when the service module 210 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 traffic, which carries data related to the service provided by the service module (service data). Such processing functions may additionally or alternatively transmit service data (which may be processed service data and may be included in the processed data traffic) to each other or to one or more other network functions. For example, a processing function may use one or more interconnects 272 to transmit service data to one or more processing functions of a different service module. Data traffic (whether received or transmitted) may include information indicating the type of service data, such as data for processing, AI models, data before cleansing, data after cleansing, etc. Data traffic may also include information identifying how the service data should be processed, such as a processing code or index. Data traffic may include information such as a source entity ID, a destination ID, a path ID, or a processing order, and this information may then be used by the processing function to route the data traffic correctly (e.g., using the correct path). The above information may be included in the data packet, for example, in a header of the data packet or in a payload field of the data packet (for example, as a part of service data). The data packet belongs to data traffic.

[0091] In various embodiments, the service C / M component 228 includes one or more controllers, and the service data plane 270 includes one or more processing functions. The one or more controllers use one or more XaaS internal interfaces 285 to manage or control the one or more processing functions. The XaaS internal interface can promote the operable coupling between the service C / M surface component 228 and the service data plane 270. The service data plane 270 and the service C / M component 228 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. Executing such control can promote or ensure satisfactory or optimal performance of the XaaS service.

[0092] At least one infrastructure module 250 includes (or is associated with) an infrastructure C / M plane component 268 (also referred to as an infrastructure C / M plane) that can be used with Figure 1A The infrastructure module 250 may be located at the infrastructure layer 150. The infrastructure module 250 may be located at the infrastructure layer 150. Figure 1A The infrastructure modules of the infrastructure layer 150 in the same. The service provision C / M plane components, the service C / M plane components, or both of one or more of the infrastructure modules can be used.

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

[0094] The service data planes 270 of one, some or all of the service modules in the service module 210 can be interconnected via interconnection 272. Interconnection 272 can be in the form of a tunnel. Interconnection can be used to facilitate providing the functionality of one service module as a service to another service module. Interconnection can be used to constitute multiple interconnected service modules, called a graph. Interconnection 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 cannot, 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 connected or connected to the graph via other operable links as needed. For example, terminal 295 can be connected to one service data plane 270, and AS297 can be connected to another service data plane 270. Multiple types of tunnels can pass through a subset of the service layer XaaS service data plane.

[0095] 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 helps to achieve flexible data plane connections.

[0096] In various embodiments, service data is transmitted 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, 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 customer or its C / M layer or C / M 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 allows 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 specified tasks, such as tasks managed by an MM module and involving one, two, or more service modules.

[0097] For example, refer again to Figure 2 , a task may involve multiple service modules 210. Related data processing may span the service data plane 270 of these multiple service modules. Interconnect 272 may facilitate communication between these multiple service modules to facilitate data processing.

[0098] In various embodiments, a service layer (e.g., Figure 1A The C / M plane 228 of the service module 210 in the service layer 110 in the infrastructure layer (e.g., Figure 1A The C / M plane 268 of the infrastructure module 250 in the infrastructure layer 150 in the example, and the C / M layer (e.g., Figure 1A The C / M modules 230 in the C / M layer 130 in the C / M layer 130 are communicatively coupled to each other. The communicative coupling can be provided in a fully meshed form so that any two entities (C / M plane, C / M module) can communicate directly. This fully meshed interconnection can involve entities connected to a communication bus, which (or its components) can be referred to as an inter-XaaS interface 290. 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 290 between modules potentially forms a fully meshed structure, allowing any two system modules to interact at the C / M level to facilitate making optimal decisions, consistent C / M 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, or by using the services of one or more infrastructure modules.

[0099] The C / M module 230 can provide information about network dynamics to the controller. This information can include, for example, indications of device access or departure from a task, changes in task requirements, changes in resource availability, etc. This information can affect or control the service C / M 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 C / M plane can make such a decision based at least in part on information received from the C / M layer. Therefore, the C / M 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.

[0100] Figure 3 A 5G implementation architecture is shown on which embodiments of the present disclosure may be provided. For example, it should be noted that Figures 4A to 4C The embodiment is superimposed on Figure 3 ’s overall architecture and can therefore coexist with it.

[0101] Figure 3 UE, RAN, CN and servers accessed via the Internet are shown. 5G networks provide connectivity as a service (CaaS). In this way, 5G networks provide connectivity between customer UEs and the services of service providers. 5G networks include three planes: a user plane (or data plane) for user-related traffic, a control plane for carrying traffic for controlling the user plane, and a management plane for performing tasks such as user-related QoS control and charging control. Typically, RAN and CN are owned by a single operator. RAN and CN are generally implemented using specific equipment, and the cloud infrastructure for RAN and CN implementation is very limited (if any).

[0102] according to Figure 3 , the UE communicates with the server to support applications that run partially on the UE and partially on the server. The communication is carried out through the CaaS service provided by the 5G network. C / M modules can be set up in the RAN and CN to support this connection. The communication includes 5G user plane communication. In order to control the user plane, 5G control plane communication is also supported. The UE communicates with the RAN via an air (e.g., wireless) link. The RAN communicates with the CN via another communication link (Transmission 1), which can be a wired link or a wireless link. The CN communicates with the server via the Internet or other network connection. Figure 3 Various aspects are also presented in Figures 4A to 4C middle.

[0103] Figure 4A , 4B4C shows a cloud-based X-centric network according to an embodiment of the present disclosure. RAN cloud 410, CN cloud 411 and another cloud 412 are shown, for example, another RAN cloud, CN cloud or third-party cloud. However, there may be more or fewer clouds. Each cloud represents a collection of devices that are communicatively coupled and implemented, for example, using virtualization technology. Different devices may be owned by different entities, and the communication infrastructure connecting the devices may also be owned by one or more different entities. The wireless device may also be considered to have a cloud-based structure. For example, the wireless device may have: one or more additional infrastructure modules; one or more additional service modules, each of which provides a corresponding function as a service and utilizes at least one of the infrastructure resources as a service; and one or more additional control and management modules, each of which provides a corresponding management or control resource as a service. At least one of the additional control and management modules may provide a corresponding management or control resource as a service to at least one of the additional infrastructure modules or additional service modules. Other functions, gateways, etc. may also be included in the wireless device. It should be noted that, for the sake of uniformity and simplicity, each cloud has a similar architectural structure.

[0104] Figures 4A to 4C N service XaaS modules 414 and N C / M XaaS modules 416 for each of the RAN cloud, CN cloud, and other clouds are illustrated. These XaaS modules are located at the service layer and are provided through a cloud-based infrastructure. For example, these XaaS modules can be Figure 2 Module 210. In addition, the service XaaS module can be Figure 1A The service layer module 110 in the C / M XaaS module can be Figure 1A 4G 5 . The C / M layer module 130 in the C / M layer module 130. The C / M XaaS module can be a C / M layer service. Each XaaS module 414, 416 is coupled to the C / M plane interface gateway (GW) 402 of the same cloud through the C / M plane interface 6G1, and different C / M plane interface GWs 402 are coupled together through the data plane interface 6G2. The C / M plane interface GW 402 is also coupled to the 6G data plane connection 6G6 through the C / M module 418 of the Net4Con function 419. The service XaaS module 414 is coupled to the data plane interface GW 404 of the same cloud through the corresponding data plane interface 6G4. The data plane interface GWs 404 of different clouds are coupled together through another data plane interface 6G5. The data plane interface GW 404 is communicatively coupled to the 6G data plane connection 6G6.

[0105] For clarity, Figures 4A to 4C The intra-XaaS module sub-functions and the intra-XaaS module interfaces (interfaces between multiple entities of the XaaS module) are not shown.

[0106] Moreover, in Figures 4A to 4C In 5G, connectivity as a service (CaaS) (see Figure 3 ) is extended to NET4Connectivity (NET4Con) service 419 to support all types of connections. For example, the NET4Con service not only supports wireless devices (e.g., UE) and servers (e.g., Figure 3 ), but also supports connections between all XaaS modules in the X-centric architecture (e.g., C / M XaaS module, service XaaS module, and infrastructure XaaS module), as well as connections between XaaS modules and other devices such as wireless devices and servers.

[0107] The Net4Con modules of the radio and each cloud are coupled together via 5G user plane and 5G control plane connections as well as 6G C / M plane connections / interfaces 6G3 and 6G data plane connections / interfaces 6G6. Thus, in addition to 5G C-plane support, NET4Con provides a new type of connection for 6G C / M plane. Note that the 5G control plane can also be extended to support 6G C / M plane connection 6G3. Furthermore, in addition to 5G user plane support, the NET4Con module provides a new type of connection for 6G data plane. Also, note that the 5G user plane can also be extended to support 6G data plane connection 6G6.

[0108] Embodiments of the present disclosure provide a 6G C / M plane trusted gateway (C / M TW-GW / proxy) in part or all of the cloud. The C / M TW-GW / proxy provides a C / M plane interface GW as described above. The gateway can be trusted in the sense that it is provided by a trusted party, protected by a trusted system (e.g., a blockchain system), etc.

[0109] Embodiments of the present disclosure provide a 6G data plane trusted gateway (6G data TW-GW / proxy) in part or all of the cloud. The data TW-GW / proxy provides the data plane interface GW as described above.

[0110] In various embodiments, the interaction or signaling messages between all XaaS modules in the X-centric architecture are transmitted through the C / M plane interface 6G3 of the NET4Con module.

[0111] In various embodiments, data transfer between XaaS modules in the service layer of the X-centric architecture is performed through the 6G data plane interface 6G6 of the NET4Con module. These service layers may include, for example, NET4AI, NET4Data, NET4BlockChain, DAM, NET4DigitalWorld, or, for example, Figure 1A Other service layer modules such as those service layer modules of the service layer 110 in the example.

[0112] As described above, different XaaS modules in the X-centric architecture may be controlled or managed by different entities. There may be at least two different entities, each controlling or managing at least one of the XaaS modules which may be a service or C / M XaaS module.

[0113] In various embodiments, the implementation architecture is unified and cloud-based. The architecture design includes functions and interfaces implemented in the cloud, such as using computing devices to provide functions through virtualization technology to implement these functions and interfaces in the cloud. The implementation architecture can be applicable to all types of clouds.

[0114] In various embodiments, the X-centric implementation architecture is implemented on top of a 5G network. This approach can fully support backward compatibility. Therefore, the X-centric implementation architecture can coexist with 5G users and networks.

[0115] In various embodiments, a single cloud may include multiple C / M plane interface GWs, multiple data plane interface GWs, or both. However, for clarity, only a single C / M plane interface GW 402 and a single data plane interface GW 404 per cloud are shown.

[0116] Embodiments of the present disclosure provide a unified Basic Architecture Structure (BAS). The BAS includes C / M plane functions, data plane functions, and (e.g., trusted) GWs in both the C / M plane and the data plane, as well as interfaces between these functions. The BAS structure can be a building block that can be reused multiple times, for example, in different infrastructures (or clouds).

[0117] Figure 4D A unified BAS 450 according to an embodiment of the present disclosure is shown. This embodiment may have limited or minimal impact on existing 5G architecture and operations, and may therefore be backward compatible. Figure 4D The BAS 450 in the embodiment can support indirect interaction between various XaaS services. When the interface 6G-C / MC / M, 6G-Data-Data or both are included, Figure 4D The BAS in the XaaS can support direct interaction between various XaaS services.

[0118] Reference Figure 4D , a C / M-plane trusted GW (C / M-TW-GW) 452 is provided to facilitate indirect communication between C / M functions 453 in different XaaS services. The C / M-TW-GW also facilitates connectivity between different BAS domains. A BAS domain may include or refer to the infrastructure that implements the BAS (e.g., a cloud-based infrastructure). The BAS may include a TW-GW and interconnections with these TW-GWs and between these TW-GWs. Potential advantages of implementing a C / M-TW-GW include a simplified SBI interface and enabling anonymous interaction between XaaS services, thereby better managing privacy protection for XaaS service providers. The C / M-TW-GW can be used with Figures 4A to 4C The C / M plane interface GW 402 is the same.

[0119] The data plane trusted GW (data-TW-GW) 454 enables indirect communication between the data plane functions 455 of the XaaS service in the service layer. It can provide similar advantages to those of the C / M-TW-GW. The data-TW-GW can communicate with Figures 4A to 4C The data plane interface GW 404 in the same. The C / M-TW-GW and the Data-TW-GW may be owned by the infrastructure owner.

[0120] C / M function 453 and data plane function 455 may be components of an XaaS service, for example, Figure 1A Or one of the service modules in the service layer 110 in 1B. The XaaS service may include both the C / M function 453 and the data plane function 455.

[0121] exist Figure 4D In the BAS 450 in FIG. 4 , the C / M plane function 453 of the XaaS service to be interacted with other XaaS services establishes a secure connection with the C / M-TW-GW. Similarly, the data plane function of the XaaS service to be interacted with other XaaS services establishes a secure connection with the data-TW-GW. Therefore, indirect interaction between the XaaS services becomes possible. This may help anonymous service provision, improve trust management, or simplify SBI.

[0122] It should be noted that Figure 4DThe BAS 450 in defines the interfaces between the inter-XaaS services and the inter-BAS domain. The interfaces between the inter-XaaS services may include interfaces 6G-C / M-1, 6G-C / M-2, 6G-Data-1, and 6G-Data-2. 6G-C / M-1 defines the interface between the C / M function in the XaaS service and the C / M-TW-GW. For example, XaaS service 1 may require the service of XaaS2. Therefore, XaaS service 1 uses the 6G-C / M-1 interface to send a signaling message to the C / M-TW-GW, and the C / M-TW-GW uses the 6G-C / M-1 interface to send the signaling message to XaaS service 2 after processing. Therefore, these interfaces are used for interaction between XaaS services through the C / M-TW-GW. The interfaces of the inter-BAS domain may include 6G-C / M-3 and 6G-Data-3. It is also important to note that vertical domains can also interact indirectly with 6G XaaS services through these GWs.

[0123] Figure 4D The BAS 450 in the 6G-C / M-1 interface provides C / M-plane message exchange between the C / M-TW-GW and the C / M functions in each XaaS service in the C / M layer, service layer, and infrastructure layer. The 6G-C / M-1 interface can be used with Figures 4A to 4C The 6G-C / M-2 interface provides message exchange between different C / M-TW-GWs in the same BAS domain. The 6G-C / M-3 interface provides message exchange between C / M-TW-GWs in different BAS domains. The 6G-C / M-3 interface can be used with Figures 4A to 4C The 6G-Data-1 interface provides 6G data plane traffic transmission between the Data-TW-GW and the data processing functions defined in each XaaS service in the service layer. The 6G-Data-1 interface can be used with Figures 4A to 4C The 6G-Data-2 interface provides 6G data plane traffic transmission between different data-TW-GWs in the same BAS domain. The 6G-Data-3 interface provides 6G data plane traffic transmission between data-TW-GWs in different BAS domains. The 6G-Data-3 interface can be used with Figures 4A to 4C The 6G5 interface of the Data-TW-GW is the same as that of the C / M-TW-GW. The Data-TW-GW can interface with the C / M-TW-GW through the interface 6G-C / M-Data-1.

[0124] When the 6G-C / MC / M interface is included, the 6G-C / MC / M interface provides C / M plane message exchange between different C / M functions in each XaaS service in the C / M layer, service layer and infrastructure layer. The 6G-C / MC / M interface is used for message exchange between each C / M function of different XaaS services. When the 6G-data-data interface is included, the 6G-data-data interface provides data plane traffic transmission between different data processing functions defined in each XaaS service in the service layer. The 6G-data-data interface is used for data traffic transmission between each data processing function of different XaaS services.

[0125] Figure 4D The BAS 450 in the embodiment includes 6G-C / MC / M and 6G-data-data, which define the interfaces between XaaS services and BAS domains. In this embodiment, the C / M plane function of the XaaS service to be interacted with the C / M plane function of other XaaS services establishes a secure connection with each of these C / M functions. Similarly, the data plane function of the XaaS service to be interacted with the data function of other XaaS services establishes a secure connection with each of these functions. A BAS that supports direct interconnection between different XaaS services may be more suitable for deployment scenarios where only a small number of XaaS services are deployed. The C / M-TW-GW452 in this embodiment may only perform the function of supporting message exchange between BAS domains. The data-TW-GW 454 in this embodiment may only perform the function of supporting data traffic transmission between BAS domains. The 6G system can also support direct interaction between XaaS services without the introduction of a trusted GW. Interfaces 6G-C / MC / M and 6G-Data-Data can be used for interaction between different XaaS services.

[0126] In some embodiments, the 6G system can be configured to support 5G services by introducing 5G as a service and integrating 5G service provision into the 6G system architecture. In some embodiments, the 5G system can be supported as 5G as a service (5GaaS) and can be developed and deployed using slicing technology. These interfaces are Figure 4D The interfaces in the 5G CP are the same, supporting backward compatibility. The 6G data plane functions shown may include 5GaaS UP-m, and the 6G C / M plane functions shown may include 5GaaS CP-m. 5GaaS CP-m and 5GaaS UP-m represent modified CP and UP of the 5G system. Some examples include: authentication, authorization, and key management in the 5G CP may be provided by the 6G SPM service; the mobility management function of the AMF may be provided by the 6G CM service; the UPF in the 5G UP may interface with the data-TW-GW, depending on implementation preferences.

[0127] The 6G system BAS can also be used as an intra-XaaS service BAS in some or all XaaS services. The BAS of XaaS services is denoted as XaaS BAS. The relationship between the 6G system BAS (indirect interaction) and the XaaS BAS of XaaS services in the service layer and C / M layer is shown in Figure 4E and 4F Shown in.

[0128] The BAS of each XaaS service and the relationship between the 6G system BAS 450 and the XaaS BAS 460 are as follows: Figure 4E 4, which applies to the above alternatives (i.e., with or without 5GaaS services). Thus, inter-XaaS service interactions between functions within an XaaS service may define a BAS 460. Thus, the principles of a BAS may be implemented for such inter-XaaS service interactions.

[0129] The XaaS services at the service layer include internal data plane functions, one or more of which interface with the Data-TW-GW 454 for interaction with other XaaS services. The internal data plane traffic of the XaaS services may or may not pass through the Data-TW-GW when crossing BAS domains, such as the BAS domains between the RAN and the CN, depending on the implementation.

[0130] The XaaS services at the service layer also include internal C / M plane functions, one or more of which interface with the C / M-TW-GW 452 for interaction with other XaaS services. Similar to processing data plane traffic, the internal C / M plane messages of the XaaS services may or may not pass through the C / M-TW-GW when crossing BAS domains, for example, between RAN domains and CNs. The internal interfaces of the XaaS services may or may not be standardized, depending on the implementation.

[0131] In addition to omitting the data plane functions and Data-TW-GW, Figure 4F and Figure 4E Similarly. XaaS services in the C / M layer and infrastructure layer include internal C / M functions, one or part of which interfaces with the 6G system C / M-TW-GW 452. Such internal C / M plane messages of XaaS services may or may not pass through the 6G system C / M-TW-GW when crossing domains / infrastructures. The internal interfaces of XaaS services in the C / M layer may or may not be standardized, depending on the implementation.

[0132] Figure 4G The interconnection between two BAS domains, Domain A and Domain B, according to an embodiment is shown. The configuration of each domain is similar to Figure 4DSimilarly, the C / M-TW-GW 452 in the two BAS domains 450 performs message exchange between the BAS domains via the 6G-C / M-3 interface. The Data-TW-GW 454 in the two BAS domains performs data traffic transmission between the two BAS domains via the 6G-Data-3 interface.

[0133] Figure 4H A plurality of BASs 450 are shown interconnected together. Each BAS (or BAS domain) shown can be implemented in a given cloud infrastructure (e.g., RAN cloud, CN cloud, or third-party cloud) and interconnected with one or more other BASs in the same cloud infrastructure, different cloud infrastructures, or a combination thereof, or interconnected in a wireless device. Each BAS can be a complete BAS or a partial BAS (subset).

[0134] Fig. 4I An X-centric network architecture according to an embodiment is shown. Each basic XaaS service can provide unique capabilities, can include multiple functions, and can be deployed in the underlying infrastructure. A 6G data plane and a C / M plane can be implemented. The infrastructure includes multiple different service layer XaaS modules 494, which can be interconnected, for example, by tunnels. The modules 494 can include modules of a first type 495 and modules of a second type 496. The first type 495 can be composed of C / M layer modules, and the second type 496 can be composed of service layer modules. The C / M layer modules can have a BAS structure 497, which is in Figure 4F The C / M layer module may have a BAS structure 498, which is shown in more detail in FIG. Figure 4E BAS 499 is also shown for context, which is shown in Figure 4D is shown in more detail in .

[0135] The 6G system described in this article can be developed along any of a variety of development paths. For example, the above-mentioned 6G system XaaS service can be used, and the 5G system can be used as the basic access system to develop the 6G system. Such a 6G system can support backward compatibility and can be limited to not affecting 5G service access. As another example, the above-mentioned 6G system XaaS service can be used, and the 5G system can be supported as a 5G System as a Service (5G System as a Service, 5GaaS) to develop a 6G system. As another example, a 6G system can be developed as the 5G system evolves to support 6G services.

[0136] According to various embodiments, the 6G system architecture design incorporates a collection of BASs, for example, uniformly implementing BASs in the infrastructure of the 6G system. The BAS approach can be used in any open path in the above-mentioned development paths. The BAS structures in different infrastructures or clouds and the connections (e.g., interfaces) between these BASs can constitute the 6G system architecture.

[0137] Based on the capabilities, capacities and specific needs of the infrastructure, a complete BAS or a subset of the BAS can be deployed in the infrastructure. A subset of the BAS may enable only a subset of XaaS services to be implemented in the BAS domain. As an example, the RAN may be a BAS domain, and due to possible capacity limitations, the RAN may only implement some 6G XaaS services. As another example, a subset of the BAS may be a subset of the functionality of the XaaS service. As a further example, if all XaaS services are provided by a single provider in the BAS domain, the TW-GW in the C / M plane and the data plane may perform its forwarding function only in that domain. The BAS can be applied to wireless devices with a selected subset of the BAS. It should be noted that the wireless device may be a robot, a drone, or an advanced device with enhanced capacity and capabilities.

[0138] In various embodiments, the adaptation of the BAS to different infrastructure networks may be accomplished while maintaining the same overall structure and interfaces defined above for the BAS. In various embodiments, the functions defined by the 6G XaaS service may be implemented as software-defined virtualized functions, or using dedicated or function-specific hardware to speed up processing where applicable.

[0139] Figure 5A A communication system supporting backward compatibility according to an embodiment is shown. Communications are described using a (e.g., 6G) system architecture reference model as shown. The model includes BASs 510 and their interconnections, which are implemented in multiple domains of the infrastructure. These domains may include a RAN domain 502, a CN domain 504, and a third-party infrastructure domain 506. One or more BASs 510 may also be implemented in a wireless device domain (e.g., in the wireless device itself), which may be simplified. Accordingly, each domain may include one or more BASs. Each BAS can be coupled to various aspects of a 5G system (e.g., a 5G control plane and a 5G user plane). Each BAS can be connected to other BASs in the same domain, BASs in other domains, or both. When expanded in detail, Figure 5A The system in can be similar to Fig.6D The system in.

[0140] The 6G system architecture leverages the service based architecture (SBA) concept and the virtual network and slicing technologies developed for the 5G system. In this reference model, the 5G system is supported by retaining and using the 5G system architecture. To support the provision of 6G services to end customers, end customers can directly access 6G services. Alternatively, customers can access 6G services through the 5G system via the interface between the 5G CP (e.g., AMF) and the 6G C / M plane provided by the C / M-TW-GW.

[0141] Figure 5B A communication system according to another embodiment is shown, as Figure 5A An alternative to Figure 5A Compared with the system in Figure 5B The systems in are less backwards compatible (or not backwards compatible). Figure 5B The system and Figure 5A , omitting the 5G components, with the possible exception of the 5G-N6 link between CN and DN.

[0142] Figure 5B The 6G system architecture in the reference model utilizes the SBA concept as well as the virtual network and slicing technology developed for the 5G system. In this reference model, the 5G system is supported as a service of the 6G system (5G as a service). The 6G system allows 6G UEs to access both 5G services and 6G services. In order to support the provision of 5G services to end customers, end customers can access 5G services through the 6G system C / M functions.

[0143] According to other embodiments, the 6G system described herein may be defined as an evolution of a 5G system. Following this evolution path, the 5G system may be enhanced to support 6G services. Some examples of enhancements to the 5G system are as follows. The session management function (SMF) may be enhanced to enable mission management (MM) functions to support 6G data plane interactions for 6G services. The access and mobility function (AFM) may be enhanced to enable connectivity management (CM) functions to manage the mobility of physical users (UEs) and digital users (UEs). The authentication, authorization, and key management functions may be enhanced to enable service provisioning management (SPM) functions for unified authentication, authorization, and key management between any pair of service providers and consumers (including 6G system customers and all 6G XaaS service providers). The Service Communication Proxy (SPC) and the network repository function (NRF) can be enhanced to enable a trusted GW and leverage the BAS architecture to simplify the service-based interface (SBI) and better manage the privacy protection of both parties of any interaction in the 6G C / M plane. The user plane can be enhanced to provide a 6G data plane. A 6G data plane trusted GW can be provided, and the BAS architecture can be leveraged to simplify the 6G data plane SBI and better manage the privacy protection of both parties of any interaction in the 6G data plane. All of the above 6G system development paths may follow basically the same design principles.

[0144] Figure 5CThe service interface within XaaS according to an embodiment is shown. The service connection within XaaS can cross BAS domains. Such a connection may or may not pass through C / M-TW-GW and data-TW-GW, depending on the implementation. As shown, there are multiple BAS domains 550, each of which uses a different infrastructure (e.g., RAN, CN or other cloud infrastructure, also referred to as 6G system integration infrastructure). Each BAS domain 550 may include multiple C / M layer XaaS modules 595, service layer XaaS modules 596, or both. Each BAS domain 550 may also include a data plane GW or TW-GW 555 and a C / M plane GW or GW-GW 557. GW or TW-GW 555, 557 may be associated with a Net4Con XaaS module, or may also be included in a Net4Con XaaS module. The data plane GW or TW-GW 555 is interconnected with the XaaS modules of the same BAS domain, for example, through a tunnel interconnection 560. In some embodiments, the tunnel interconnect 560 is limited to the service layer XaaS module 596 and does not extend to the C / M layer XaaS module 595. The control plane GW or TW-GW 557 is interconnected with the XaaS modules of the same BAS domain, for example, via the tunnel interconnect 562. In addition, in some embodiments, the XaaS modules of different BAS domains 550 can communicate directly with each other, for example, via the link 570 (option A). Additionally or alternatively, the XaaS modules of different BAS domains 550 can communicate indirectly with each other, for example, via the link 572 between different Net4Con XaaS modules (option B). In this case, the first XaaS module communicates with the Net4Con module of the same BAS domain, which passes the communication to the Net4Con module of another BAS domain, which in turn passes the communication to the second XaaS module of the other BAS domain.

[0145] Various XaaS modules including the service XaaS module can run together to support tasks. According to an example embodiment, Figures 6A to 6C Shown with Figures 4A to 4C The same infrastructure, and specific interconnections (thick, dark arrows 610) between multiple modules of multiple clouds to support such tasks. Multiple service XaaS modules of different clouds can be interconnected. Multiple service XaaS modules of the same cloud can be interconnected. The interconnection can be through one or more data plane interfaces GW. Such interconnection also involves the application of wireless devices. These interconnections form a 6G data plane or data processing plane. The 6G data plane includes data plane processing functions in each service layer XaaS module and a 6G data plane (or data processing plane) connection 610. Each supported task service can similarly have its own associated customized 6G data plane (or data processing plane) topology.

[0146] To better illustrate the connections 610 that form the 6G data plane, Fig.6D Show all at once Figures 6A to 6C .

[0147] The interfaces 6G1, 6G2, 6G3, 6G4, 6G5, 6G6 and 6G7 introduced above are now discussed in more detail.

[0148] Interface 6G1 is the intra-cloud interface between the C / M functions of all XaaS modules and the C / M plane interface GW (e.g., C / M TR-GW / proxy). This interface carries signaling messages between the C / M functions of each XaaS module. This interface can be called the 6G C / M service based interface (SBI).

[0149] Interface 6G2 is an interface between clouds (e.g., between C / M interface GWs of different clouds) to carry C / M signaling messages between C / M functions of XaaS modules in different clouds. This interface can be between two or more different C / MTW-GWs / agents.

[0150] Interface 6G3 is an (e.g., air) interface for carrying C / M signaling messages between each cloud (e.g., RAN cloud) and the C / M functions of each XaaS module in each cloud of the 6G wireless device. Interface 6G3 may exist between each cloud for C / M plane connection.

[0151] Interface 6G4 is the intra-cloud interface between the data functions of all XaaS modules and the data plane interface GW (e.g., data TR-GW / proxy). This interface is used for data transmission between the XaaS modules in the service layer. This interface can be called 6G data plane SBI.

[0152] Interface 6G5 is an interface between clouds (e.g., between data plane interface GWs of different clouds) and is used to transmit data between XaaS modules in service layers in different clouds. This interface can be between two or more different data TW-GWs / agents.

[0153] Interface 6G6 is an (e.g., air) interface for carrying 6G data between clouds, for example, between a RAN cloud and a 6G wireless device.

[0154] Interface 6G7 is the interface between the 6G C / M plane and the 6G data plane, facilitating C / M control and management in the 6G data plane.

[0155] The above interfaces can be applied to all types of clouds. It should be noted that the direct interfaces between the XaaS modules are not shown. The two end point communications (signaling and data) between the XaaS modules can be directly coupled or indirectly coupled through the TW-GW / agent. Only indirect coupling is shown.

[0156] According to various embodiments, the implementation architecture is unified and cloud-based. That is, the architecture design (e.g., including functions and interfaces) within each cloud is the same or similar. Figures 4A to 4C This is obvious. This cloud-based unified architecture can contribute to the simple and rapid implementation of 6G networks. Interface design is simplified. Logical functions and interfaces can be unified in some or all types of clouds (including RAN cloud, CN cloud, third-party cloud, and user equipment cloud). For example, the structure of one cloud (e.g., RAN cloud) is repeated in the CN cloud and the third-party cloud. In other words, there may be multiple groups of modules (e.g., service modules, C / M modules, and infrastructure modules), each group of modules provided by a different cloud. Each group of modules in each cloud can be organized and interconnected in the same or similar manner, thereby providing the repeated structure shown.

[0157] According to various embodiments, a cloud architecture may be used to provide user equipment (e.g., wireless devices, UEs). The components of the cloud architecture may all be located within the same physical device, or different components may be located in different physical devices. The cloud architecture may also be the same or similar to the cloud architecture of other clouds (e.g., RAN clouds). That is, the structure and interface within the device cloud may be the same as the structure and interface of other types of clouds. In such an embodiment, multiple XaaS modules may be downloaded to the device by different XaaS module owners.

[0158] In various embodiments, the unified interface can be applied to devices, RAN cloud, core network cloud, and other third-party clouds to facilitate interoperability of various components of the entire multi-cloud system.

[0159] As shown, the RAN is associated with a single cloud. Alternatively, different components of the RAN may be provided, each associated with its own cloud. For example, the RAN may be implemented using a centralized unit (CU) and one or more distributed units (DU). Each CU and DU may be implemented using its own cloud. Each cloud may have a structure and architecture similar to that of the RAN cloud.

[0160] In various embodiments, such as regarding Fig. 7A and 7B As described, Figure 2The inter-XaaS interface 290 in the example may be implemented in a specific manner using a C / M TW-GW. The C / M TW-GW (or other similar C / M plane interface GW) may act as an intermediary or relay for coupling different XaaS C / M functions (C / M layer XaaS modules), different service layer XaaS modules, different infrastructure layer XaaS modules, or a combination thereof. For example, the C / M TW-GW may be Figures 4A to 4C The C / M plane interface GW 402 in the C / MTW-GW can be as follows Figures 4D to 4G shown.

[0161] Fig. 7A A C / M plane interface of a service based interface (SBI) according to an embodiment of the present disclosure is shown. In this embodiment, the TW-GW acts as a signaling message forwarding function. The forwarding can occur without converting the signaling message. Alternatively, the signal message forwarding function may include a conversion operation. As shown, all C / M functions are interconnected in a full mesh structure. The C / M TW-GW 702 receives signaling messages from each source XaaS module 704 and forwards such signaling messages to the specified destination XaaS module 704. Therefore, the TW-GW acts as an intermediary for such signaling messages. The forwarding action generates an inter-XaaS C / M interface 706 shown with a dotted line. These interfaces can be direct logical interfaces viewed by each XaaS module. Fig. 7A An example in a cloud 700 (e.g., a RAN cloud, a CN cloud, or any other third-party cloud) is shown. Fig. 7A The connections from C / M layer XaaS module 1 to other C / M layer XaaS modules, infrastructure layer XaaS modules, and service layer XaaS modules are shown. As shown, C / M layer XaaS module 1 is directly (logically) connected to all other C / M layer XaaS modules, all infrastructure layer XaaS modules, and all service layer XaaS modules. All other C / M functions (modules) have similar structures and connections, but these connections are not shown in the figure. Fig. 7A Shown in.

[0162] Figure 7BA C / M surface interface of a service based interface (SBI) according to another embodiment of the present disclosure is shown. In this embodiment, TW-GW 702 acts as a signaling message converter. That is, C / M TW-GW 702 acts as an interface converter and isolates XaaS producers from XaaS consumers. It should also be noted that one or more C / M TW-GWs can be provided within a single cloud. C / M TW-GW receives signaling messages from each source XaaS module 704 (in the C / M layer, infrastructure layer, and service layer), converts such signaling messages, and forwards them to the specified destination XaaS module (in the C / M layer, infrastructure layer, and service layer). Therefore, TW-GW again acts as an intermediary for such signaling messages. This forwarding action generates a C / M interface 707 between XaaS as shown in the figure and connected to the module by a dotted line. Figure 7B An example in a cloud 700 (e.g., a RAN cloud, a CN cloud, or any other third party cloud) is shown. Figures 4A to 4C , where the C / M-TW-GW (e.g., C / M plane interface GW) interconnects different service XaaS modules and C / M XaaS modules, thereby providing an inter-XaaS C / M interface, which may correspond to interface 6G1. The C / M-TW-GW may facilitate (possibly anonymous) interactions between XaaS services. The C / M-TW-GW may receive a signaling message requesting a service from an XaaS service (consumer), encrypt the message, find the provider of the requested service, and send a signaling message to the provider. The signaling message received by the C / M-TW-GW may be different from the signaling message sent by the C / M-TW-GW. That is, when the GW receives a message of a request type, the GW does not necessarily just forward the message to the selected target, but may instead convert the received message into another new request message with different message content.

[0163] Various embodiments of the present disclosure support multiple operating modes. Various embodiments implement or promote an open environment to allow multiple partners to 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, the provider of each XaaS service is defined as a role. The system allows flexible mapping between partners and roles of the 6G system. Infrastructure providers can use their infrastructure (including network infrastructure, data centers, and storage infrastructure) to assume all roles of the 6G system. Infrastructure providers may only assume some of these roles and allow 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.

[0164] 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 such as data processing or data storage, the module also includes communication functions and utilizes the communication network infrastructure. A module that provides functions as a service can provide the entire function to one or more of its clients without requiring the client to perform other management tasks. Instead, for example, the function 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 maintain its functionality, etc. Modules can rely on each other by providing services to each other, for example in a closed interdependent system.

[0165] 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 using only the modules needed, and the modules can be expanded or contracted according to demand.

[0166] According to various embodiments, modules are provided at a certain level of granularity. This may be another case in which modules are divided into three types - service modules, C / M modules and infrastructure modules. The level of granularity is such that there are neither too many different modules (which would lead to higher complexity) nor too few modules (which would lead to higher commonality of each module type). Accordingly, in various embodiments, each module is configured to provide one and only one overall common functionality as a service. The functionality is unique and is completely provided by the module (the module relies on other modules to provide services to it as needed). Therefore, from the perspective of a client using the module to access the services provided, the module is self-contained.

[0167] According to an embodiment, a service module (for example) includes all subcomponents required for it to receive and respond to service requests (from clients) by performing the requested service. For example, a service module may include components in a service C / M 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 such submodules.

[0168] In view of the above, embodiments of the present disclosure provide for both inter-XaaS interfaces and intra-XaaS interfaces. These two types of interfaces may be independent of each other and may be distinguished from each other in one or more ways. Inter-XaaS interfaces may be standardized, while intra-XaaS interfaces are not necessarily standardized. These interfaces may have well-defined functions, and their structure and functionality may be independent of their deployment scenarios. Therefore, these interfaces may promote a modular design approach.

[0169] In some embodiments, the C / M interface gateway (gateway, GW) or the trusted gateway (trustworthygateway, TW-GW) is configured to perform authorization functions, selection or search functions, etc. Therefore, the C / M-GW or TW-GW can perform the selection function. The C / M-GW can be pre-configured to hold or access one or more authorization profiles (authorization profiles), which indicate which XaaS services are authorized to use which other XaaS services. In this way, after receiving a service request from the XaaS service, the C / M GW checks the authorization profile to determine another XaaS service that can provide the service specified in the request. Then, the C / M-GW can forward the request to such another XaaS service. The XaaS service can be an infrastructure module, a service module, or a C / M module. Therefore, the C / M-GW can receive a request for a first module in the infrastructure module, the service module, and the control and management module to use a specified service. In response to the request, the C / M-GW can determine (for example, by consulting the provided authorization profile) the second module in the infrastructure module, the service module, and the control and management module. The second module provides the specified service. In addition, the first module is authorized to receive the specified service from the second module (e.g., according to the authorization profile). The C / M-GW can then start providing the service, for example, by forwarding the received request to the second module.

[0170] In some embodiments, a C / M plane interface gateway (gateway, GW) or a trusted gateway (trustworthy gateway, TW-GW), a data plane interface gateway (gateway, GW) or a trusted gateway (trustworthygateway, TW-GW) or both within a BAS domain are configured and used to control access of XaaS services, devices, or both to the BAS domain. The above-mentioned authorization function can be used for this purpose. Therefore, the GW or TW-GW can be configured to perform access control based on predetermined authorization parameters, and identification or authentication can also be used for this purpose. When the GW or TW-GW determines that the XaaS service or device is authorized to access some or all resources in the BAS domain, access to such resources can be allowed, otherwise access will be blocked. For example, the authorization can be pre-configured.

[0171] Figure 8 Schematic diagram of a computing device 800 according to different embodiments of the present disclosure, the computing device can perform any or all operations and features of the methods explicitly or implicitly described herein. For example, a computer equipped with network functions can be configured as a computing device 800. 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 (e.g., in the same or separate data centers) can be coupled together to provide one, two or more such computing devices. When a device provides an infrastructure module, the device can mainly include associated resources. For example, a computing module can mainly include a computer processor, and a storage module can mainly include a computer memory.

[0172] As shown, the device 800 may include: a processor 810, such as a central processing unit (CPU), or a dedicated processor such as a graphics processing unit (GPU), or other such processor unit; a memory 820, a non-transient mass storage 830, an input and output interface 840, a network interface 850, and a transceiver 860, all of which are communicatively coupled via a bidirectional bus 870. According to certain embodiments, any or all of the described elements may be utilized, or only a subset of these elements may be utilized. In addition, the device 800 may include multiple instances of certain elements, such as multiple processors, memories, or transceivers. Moreover, elements of a hardware device may be directly coupled to other elements without the need for a bidirectional bus. In addition to or in place of a processor and memory, other electronic components such as integrated circuits may be used to perform the required logical operations.

[0173] The memory 820 may include any type of non-transient memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or any combination thereof. The mass storage element 830 may include any type of non-transient 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 820 or the mass storage 830 may record thereon statements and instructions executable by the processor 810 to perform any of the aforementioned method operations described above.

[0174] Embodiments of the present disclosure may be implemented using electronic hardware, software, or a combination thereof. In some embodiments, the present disclosure is implemented by one or more computer processors that execute 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 (FPGA) or application specific integrated circuits (ASIC) to quickly perform processing operations to implement.

[0175] 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, it is within the scope of the present disclosure to provide a computer program product or program element for storing machine-readable signals, or a program storage or memory device such as a magnetic wire, tape, disk or light, optical tape or optical disk, for controlling the operation of a computer according to the method of the present disclosure and / or constructing some or all of its components according to the system of the present disclosure.

[0176] The operations associated with the methods described herein may be implemented as coded instructions in a computer program product. In other words, a computer program product is a computer-readable medium on which software codes are recorded to perform the method when the computer program product is loaded into a memory and executed on a microprocessor of a wireless communication device.

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

[0178] Through the description of the above embodiments, the present disclosure can be implemented only by using hardware, or 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, which 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 may correspond to a simulation of the logical operation described herein. 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 according to an embodiment of the present disclosure.

[0179] 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 the one or more inventions. Therefore, the specification and drawings are to be regarded only as illustrations of embodiments of the present disclosure, such as those defined in 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 system comprising: One or more infrastructure modules, each of the infrastructure modules providing corresponding infrastructure resources as a service; one or more service modules, each of the service modules providing a corresponding function as a service and utilizing at least one of the infrastructure resources as a service; One or more control and management modules, each of the control and management modules providing corresponding management or control resources as a service, and at least one of the control and management modules providing the corresponding management or control resources as a service to at least one of the infrastructure modules or the service modules; One or more gateways provide secure connections with the infrastructure module, the service module, and some or all of the control and management modules, and facilitate interactions between the infrastructure module, the service module, and some or all of the control and management modules.

2. The system according to claim 1, wherein: Part or all of the infrastructure module, the service module, the control and management module, and the one or more gateways are implemented using virtualized resources provided by multiple clouds.

3. The system according to claim 2, wherein: The one or more gateways include a C / M-plane interface gateway (GW) or a trusted gateway (TW-GW), and the C / M-plane interface GW or TW-GW is configured as an intermediary for interconnecting the infrastructure module, the service module, and the control and management functions of the control and management module residing in the same cloud of the multiple clouds.

4. The system according to claim 3, wherein: The C / M plane interface GW or TW-GW is configured to control the access of one or more of the infrastructure module, the service module, and the control and management module to one or more other modules among the infrastructure module, the service module, and the control and management module, or the access of another device to one or more of the infrastructure module, the service module, and the control and management module.

5. The system according to claim 3 or 4, wherein: The infrastructure module, the service module, and some or all of the modules in the control and management module are implemented using virtualized resources in the multiple clouds, and the system also includes: a different corresponding C / M plane interface gateway (GW) or trusted gateway (TW-GW) in each of the multiple clouds, wherein different corresponding C / M plane interface gateways (GW) or trusted gateways (TW-GW) are coupled together to interconnect different modules in the infrastructure module, the service module, and the control and management module residing in different clouds of the multiple clouds.

6. A system according to any one of claims 3 to 5, wherein: The C / M plane interface gateway (GW) or trusted gateway (TW-GW) is configured to operate as a signal message forwarding function to facilitate an interface between one or more pairs of modules, each pair of modules being selected from the one or more infrastructure modules, the one or more service modules and the one or more control and management modules, the interface being a direct logical interface.

7. A system according to any one of claims 3 to 5, wherein: The C / M plane interface gateway (GW) or trusted gateway (TW-GW) is configured to operate as a signal message converter to facilitate an interface between one or more pairs of modules, each pair of modules being selected from the one or more infrastructure modules, the one or more service modules and the one or more control and management modules, and the signal message converter changes the content of messages forwarded between the one or more pairs of modules.

8. A system according to any one of claims 3 to 7, wherein: The C / M plane interface gateway (GW) or trusted gateway (TW-GW) is also configured to communicatively couple the infrastructure module, the service module, and part or all of the control and management modules to a C / M plane connection, and the C / M plane connection is used for control plane message transmission between the client device, the server, and part or all of the infrastructure module, the service module, and the control and management module.

9. A system according to any one of claims 3 to 8, wherein: The C / M-plane interface gateway (GW) or trusted gateway (TW-GW) is configured as: receiving a request to a first module among the infrastructure module, the service module, and the control and management module for using a specified service; Determine a second module among the infrastructure module, the service module, and the control and management module, the second module provides the designated service, and the first module is authorized to receive the designated service from the second module; The request is forwarded to the second module.

10. The system according to any one of claims 1 to 9, further comprising: A data plane interface gateway (GW) or a trusted gateway (TW-GW), wherein the data plane interface GW or TW-GW is configured as an intermediary for interconnecting the data processing functions of some or all of the service modules with data plane connections, and the data plane connections are used for data transmission between client devices, servers, and some or all of the infrastructure modules, the service modules, and the control and management modules.

11. The system according to claim 10, wherein: The data plane interface GW or TW-GW is configured to control the access of one or more of the infrastructure module, the service module, and the control and management module to one or more other modules among the infrastructure module, the service module, and the control and management module, or the access of another device to one or more of the infrastructure module, the service module, and the control and management module.

12. The system according to claim 10 or 11, wherein: Some or all of the service modules are implemented in multiple clouds, and the system also includes: a different corresponding data plane interface gateway (GW) or trusted gateway (TW-GW) in each of the multiple clouds, wherein different corresponding data plane interface gateways (GW) or trusted gateways (TW-GW) are coupled together to interconnect different service modules residing in different clouds of the multiple clouds.

13. The system according to claim 12, wherein: One or more of the different corresponding data plane interface gateways (GW) or trusted gateways (TW-GW) are used to provide a 6G data plane that interconnects one or more of the service modules with one or more client devices, and the interconnection uses the data plane connection.

14. The system according to claim 13, wherein: The 6G data plane is instantiated to support tasks involving one or more service modules of the interconnect and requiring joint contributions from the one or more service modules.

15. The system according to any one of claims 1 to 14, wherein: The infrastructure module, the service module, and the control and management module include a first group of modules implemented using virtualized resources provided by a first cloud and a second group of modules implemented using virtualized resources provided by a second cloud, wherein the first group of modules are organized and interconnected in the same manner as the second group of modules.

16. The system of claim 1, further comprising: A C / M-plane interface gateway (GW) or a trusted gateway (TW-GW), the C / M-plane interface GW or TW-GW being configured as an intermediary for interconnecting the infrastructure module, the service module, and the control and management module residing in the same cloud of the multiple clouds through a dedicated and secure connection; a data plane interface GW or TW-GW configured as another intermediary for interconnecting part or all of the service modules with a data plane connection through another dedicated and secure connection, the data plane connection being used for data transmission between a client device, a server, and part or all of the infrastructure module, the service module, and the control and management module, Among them, the infrastructure module, the service module, the control and management module, the C / M plane interface GW or TW-GW and the data plane interface GW or TW-GW together form part or all of the basic architecture structure (BAS). 17 . The system of claim 16 , further comprising one or more additional BASs having the same structure as the BAS, the BAS and the additional BASs being interconnected.

18. The system of claim 16, wherein: The same cloud among the multiple clouds and its physical infrastructure form part or all of the BAS domain.

19. The system of claim 16, further comprising: another C / M-plane interface gateway (GW) or trusted gateway (TW-GW) forming part of another BAS and connected to the C / M-plane interface GW or TW-GW of the BAS; Another data plane interface GW or TW-GW, which forms part of the other BAS and is connected to the data plane interface GW or TW-GW of the BAS.

20. The system according to any one of claims 1 to 19, wherein: The system serves at least one device, and the at least one device is configured to include: one or more further infrastructure modules, each of said infrastructure modules providing a respective infrastructure resource as a service; one or more further service modules, each of said service modules providing a corresponding function as a service and utilizing at least one of said infrastructure resources as a service; One or more additional control and management modules, each of which provides corresponding additional management or control resources as a service, and at least one of the additional control and management modules provides the corresponding additional management or control resources as a service to at least one of the additional infrastructure modules or the additional service modules.

21. A method comprising: providing one or more infrastructure resources as a service using one or more corresponding infrastructure modules; providing one or more functions as a service using one or more corresponding service modules, at least one service module utilizing at least one of said infrastructure resources as a service; providing one or more management or control resources as a service using one or more corresponding control and management modules, at least one of the control and management modules providing the corresponding management or control resources as a service to at least one of the infrastructure modules or the service modules; One or more gateways are provided, which provide secure connections with the infrastructure module, the service module, and some or all of the control and management modules, and facilitate interactions between the infrastructure module, the service module, and some or all of the control and management modules.

22. The method according to claim 21, wherein: Part or all of the infrastructure module, the service module, the control and management module, and the one or more gateways are implemented using virtualized resources provided by multiple clouds.

23. The method according to claim 21, wherein: The one or more gateways include a C / M-plane interface gateway (GW) or a trusted gateway (TW-GW), and the C / M-plane interface GW or TW-GW is configured as an intermediary for interconnecting the infrastructure module, the service module, and the control and management functions of the control and management module residing in the same cloud of the multiple clouds.

24. The method according to claim 23, further comprising: The C / M plane interface GW or TW-GW controls the access of one or more of the infrastructure module, the service module, and the control and management module to one or more other modules among the infrastructure module, the service module, and the control and management module, or the access of another device to one or more of the infrastructure module, the service module, and the control and management module.

25. The method according to claim 23 or 24, further comprising: The infrastructure module, the service module, and some or all of the modules in the control and management module are implemented using virtualized resources in the multiple clouds. The method also includes: providing a different corresponding C / M plane interface gateway (GW) or trusted gateway (TW-GW) in each of the multiple clouds, wherein different corresponding C / M plane interface gateways (GW) or trusted gateways (TW-GW) are coupled together to interconnect the infrastructure modules, the service modules, and different modules in the control and management modules that reside in different clouds of the multiple clouds.

26. The method according to any one of claims 23 to 25, further comprising: The C / M plane interface gateway (GW) or trusted gateway (TW-GW) is operated as a signal message forwarding function to facilitate an interface between one or more pairs of modules, each pair of modules being selected from the one or more infrastructure modules, the one or more service modules and the one or more control and management modules, and the interface is a direct logical interface.

27. The method according to any one of claims 23 to 25, further comprising: The C / M plane interface gateway (GW) or trusted gateway (TW-GW) is operated as a signal message converter to facilitate the interface between one or more pairs of modules, each pair of modules is selected from the one or more infrastructure modules, the one or more service modules and the one or more control and management modules, and the signal message converter changes the content of the messages forwarded between the one or more pairs of modules.

28. The method according to any one of claims 23 to 27, further comprising: Using the C / M plane interface gateway (GW) or trusted gateway (TW-GW), part or all of the infrastructure module, the service module, and the control and management module are communicatively coupled to the C / M plane connection, and the C / M plane connection is used for control plane message transmission between the client device, the server, and part or all of the infrastructure module, the service module, and the control and management module.

29. The method according to any one of claims 21 to 26, further comprising: The C / M interface gateway (GW) or trusted gateway (TW-GW): receiving a request to a first module among the infrastructure module, the service module, and the control and management module for using a specified service; Determine a second module among the infrastructure module, the service module, and the control and management module, the second module provides the designated service, and the first module is authorized to receive the designated service from the second module; The request is forwarded to the second module.

30. The method according to any one of claims 21 to 29, further comprising: A data plane interface gateway (GW) or a trusted gateway (TW-GW) is used as an intermediary for interconnecting the data processing functions of some or all of the service modules with data plane connections, and the data plane connections are used for data transmission between client devices, servers, and some or all of the infrastructure modules, the service modules, and the control and management modules.

31. The method of claim 30, further comprising: The data plane interface GW or TW-GW controls the access of one or more of the infrastructure module, the service module, and the control and management module to one or more other modules among the infrastructure module, the service module, and the control and management module, or the access of another device to one or more of the infrastructure module, the service module, and the control and management module.

32. The method according to claim 30 or 31, further comprising: Implement part or all of the service modules in multiple clouds, and provide a different corresponding data plane interface gateway (GW) or trusted gateway (TW-GW) in each of the multiple clouds, wherein different corresponding data plane interface gateways (GW) or trusted gateways (TW-GW) are coupled together to interconnect different service modules residing in different clouds of the multiple clouds.

33. The method of claim 32, wherein: One or more of the different corresponding data plane interface gateways (GW) or trusted gateways (TW-GW) are used to provide a 6G data plane that interconnects one or more of the service modules with one or more client devices, and the interconnection uses the data plane connection.

34. The method of claim 33, wherein: The 6G data plane is instantiated to support tasks involving one or more service modules of the interconnect and requiring joint contributions from the one or more service modules.

35. The method according to any one of claims 21 to 34, wherein: The infrastructure module, the service module, and the control and management module include a first group of modules implemented using virtualized resources provided by a first cloud and a second group of modules implemented using virtualized resources provided by a second cloud, wherein the first group of modules are organized and interconnected in the same manner as the second group of modules.

36. The method according to any one of claims 22 to 35, further comprising: At least one device is served that is implemented at least in part using virtualized resources provided by the plurality of clouds or provided by another cloud.

37. The method of claim 21, further comprising: Providing a C / M plane interface gateway (GW) or a trusted gateway (TW-GW), wherein the C / M plane interface GW or TW-GW is configured to be an intermediary for the infrastructure module, the service module, and the control and management module residing in the same cloud of the multiple clouds through a dedicated and secure connection; providing a data plane interface GW or TW-GW, the data plane interface GW or TW-GW being configured as another intermediary for interconnecting part or all of the service modules with a data plane connection through another dedicated and secure connection, the data plane connection being used for data transmission between a client device, a server, and part or all of the infrastructure module, the service module, and the control and management module, Among them, the infrastructure module, the service module, the control and management module, the C / M plane interface GW or TW-GW, and the data plane interface GW or TW-GW together form part or all of the basic architecture structure (BAS).

38. The method of claim 37, further comprising: One or more additional BASs having the same structure as the BAS are provided, and the BAS and the additional BASs are interconnected.

39. The method of claim 37, wherein: The same cloud of the multiple clouds and its physical infrastructure form part or all of a BAS domain.

40. The method of claim 37, further comprising: providing another C / M plane interface gateway (GW) or trusted gateway (TW-GW), the another C / M plane interface GW or TW-GW forming part of another BAS and connected to the C / M plane interface GW or TW-GW of the BAS; A further data plane interface GW or TW-GW is provided, which forms part of the further BAS and is connected to the data plane interface GW or TW-GW of the BAS.

41. A computer program product comprising a non-transitory computer readable medium storing 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 21 to 40.

Images