Abstract: The described technology is generally directed towards implementing a cloud intelligent controller (CIC) system at the O-Cloud platform/infrastructure to enable automated and fast (e.g., near-RT) implementation/coordination between the O-Cloud CIC and radio access network (RAN) controllers. O-Cloud-applications (cApps) are configured for implementation at the CIC, such that a workload received at the O-Cloud can be accompanied with a cApp, wherein the cApp defines the respective resources, functionality, etc., required to process the workload. Hence, rather than relying on information provided by other platforms in the RAN (e.g., service management and orchestration (SMO), non-RT RAN intelligent controller (RIC), near-RT RIC, and associated rApps and xApps), implementing a CIC with cApps enables inherent processing latency of conventional RAN configurations to be reduced, further enabling improved power control, resource management, and the like, to be performed locally at the CIC/O-Cloud.

Abstract: The described technology is generally directed towards implementing one or more shared resources on an Open-Radio Access Network (O-RAN), whereby the shared resources are physically located at a first portion of the RAN and able to be virtually implemented at a second part of the RAN. A shared resource can be identified as available for sharing, whereupon the shared resource can be implemented at the second portion of the RAN. Resource sharing enables a resource, currently under-utilized at the first portion of the RAN to be implemented to enable an operational condition present at the second portion of the RAN to be addressed. A sharing application (a.k.a., a SharApp) can be utilized to monitor operation of the RAN, identify a resource to implement, and/or control implementation of the resource. Resources can be shared across disparate MNOs, O-Clouds, with systems external to the RAN, and such.

Abstract: The described technology is generally directed towards implementing a cloud intelligent controller (CIC) system at the O-Cloud platform/infrastructure to enable automated and fast (e.g., near-RT) implementation/coordination between the O-Cloud CIC and radio access network (RAN) controllers. O-Cloud-applications (cApps) are configured for implementation at the CIC, such that a workload received at the O-Cloud can be accompanied with a cApp, wherein the cApp defines the respective resources, functionality, etc., required to process the workload. Hence, rather than relying on information provided by other platforms in the RAN (e.g., service management and orchestration (SMO), non-RT RAN intelligent controller (RIC), near-RT RIC, and associated rApps and xApps), implementing a CIC with cApps enables inherent processing latency of conventional RAN configurations to be reduced, further enabling improved power control, resource management, and the like, to be performed locally at the CIC/O-Cloud.

Abstract: A system can identify an application package of an application that is configured to execute via a computing platform, wherein the application package comprises a deployment manifest. The system can model respective capabilities of respective computing platforms to produce capability models. The system can, based on determining to execute the application via a selected computing platform of the computing platforms, determine a capability of capabilities of the selected computing platform based on the capability models and the deployment manifest, modify the deployment manifest based on the capability to produce a modified deployment manifest, configure the capability corresponding to specifications of the application identified in the modified deployment manifest, and instantiate the application via the selected computing platform with the modified deployment manifest.

Abstract: A first access interface (100) of a an access control system provides access to computational resources (150). At least one access role of a user and at least one access target associated with the access role of the user are determined. Based on the at least one access role of the user and the associated at least one access target, a subset of the computational resources (150) is determined. A second access interface (110, 120) is defined which is limited to the subset of the computational resources (150). Through the second access interface (110, 120) the user is provided with access to the subset of the computational resources (150).

Abstract: A first access interface (100) of a an access control system provides access to computational resources (150). At least one access role of a user and at least one access target associated with the access role of the user are determined. Based on the at least one access role of the user and the associated at least one access target, a subset of the computational resources (150) is determined. A second access interface (110, 120) is defined which is limited to the subset of the computational resources (150). Through the second access interface (110, 120) the user is provided with access to the subset of the computational resources (150).