Disclosed are various examples for determining an IT topology for an enterprise IT organization based on operational goals of the enterprise organization. Visual models that are designed to facilitate responses associated with the current IT topology and operational goals of an enterprise IT organization are displayed to an entity of the enterprise. The entity can provide enterprise profile data to an IT solutions system by interacting with user interfaces. The IT solutions system can generate the IT topology prescription and roadmap for implementing the IT topology prescription based on the operational goals identified in the responses. Statements of work can be dynamically generated that outline details and terms of implementing the IT topology prescription for the enterprise IT organization.

Various systems and methods for implementing a service-level agreement (SLA) apparatus receive a request from a requester via a network interface of the gateway, the request comprising an inference model identifier that identifies a handler of the request, and a response time indicator. The response time indicator relates to a time within which the request is to be handled indicates an undefined time within which the request is to be handled. The apparatus determines a network location of a handler that is a platform or an inference model to handle the request consistent with the response time indicator, and routes the request to the handler at the network location.

The disclosure relates to a framework for dynamic management of analytic functions such as data processors and machine learned (“ML”) models for an Internet of Things intelligent edge that addresses management of the lifecycle of the analytic functions from creation to execution, in production. The end user will be seamlessly able to check in an analytic function, version it, deploy it, evaluate model performance and deploy refined versions into the data flows at the edge or core dynamically for existing and new end points. The framework comprises a hypergraph-based model as a foundation, and may use a microservices architecture with the ML infrastructure and models deployed as containerized microservices.

A network slice managing entity, comprising means configured to obtain a service request for a network slice, the service request defining service requirements; request network slice descriptions from a database and selecting at least one network slice which support said service requirements according to the descriptions; generate a resource graph comprising nodes representing infrastructure resources and links representing connections between the nodes, the resource graph depicting resources needed for providing the service, wherein the generating is carried out based on a network slice description of the selected at least one network slice; transmit the resource graph to an infrastructure manager for mapping a topology of said network infrastructure onto said resource graph and determining at least one subset of said network infrastructure; and, receive a mapping result from said infrastructure manager containing said at least one subset of said network infrastructure.

Aspects of the subject disclosure may include, for example, detecting a first bootstrap profile on a first communication device, and detecting a second bootstrap profile on a second communication device. Further aspects can include determining the first bootstrap profile and the second bootstrap profile are a same bootstrap profile, and providing limited services to the second communication device according to the first communication device and the second communication device having the same bootstrap profile. Other embodiments are disclosed.

Adaptive ambient services are provided. In some embodiments, an adaptive ambient service includes providing an ambient service profile. In some embodiments, an ambient service includes implementing an ambient service profile for assisting control of the communications device use of an ambient service on a wireless network, in which the ambient service profile includes a plurality of service policy settings, and in which the ambient service profile is associated with an ambient service plan that provides for initial access to the ambient service with limited service capabilities prior to activation of a new service plan; monitoring use of the ambient service based on the ambient service profile; and adapting the ambient service profile based on the monitored use of the ambient service.

An example method may include receiving slice isolation policy for a network slice subnet (NSS) in a transport network (TN) domain, mapping the slice isolation policy to network resource isolation policy and traffic isolation policy, and mapping the network resource isolation policy and the traffic isolation policy to network resource allocation policy and data traffic forward policy, respectively. The network resource allocation policy and the data traffic forward policy may be applied in creation of the TN NSS.

Described are examples for providing end-to-end intent definition of network functions for network slice management. Intents are defined for each level of network constituent including slices, slice subnets, and management functions. A system of intent based network slice management includes a network slice management function (NSMF) configured to receive a service profile from a communication service management function (CSMF) and derive an intent for each desired network slice subnet for a network slice subnet management function (NSSMF). The NSSMF is configured to derive requirements for a plurality of network functions (NFs) and provide an intent defining the requirements of a respective NF to a network function management function (NFMF). The NFMF is configured to receive the intent for the respective NF via an intent-based interface for management of NFs and derive a network resource model (NRM) for the respective NF based on the intent.

A network connectivity system identifies potential connection mechanisms between datacenter entities (e.g., between service instances) on the cloud platform. The network connectivity system provides recommendations including one or more connectivity paths that are preferred with respect to one or more indicators, for example, cost, latency, or security. Specifically, the network connectivity system receives a request to configure a network connection between a first service instance and a second service instance on the cloud platform. The first service instance and the second service instance may reside within the same or different datacenters, different geographical locations, and the like. A network connectivity system identifies, from network connectivity information, one or more connectivity mechanisms for establishing connection between a first datacenter entity (e.g., first service instance) and a second datacenter entity (e.g., second service instance).

A resource orchestration entity is arranged to obtain an information element of service availability level in at least one descriptor for defining the service availability level requirements of the service flow from a network service (NS) management entity, and provide the information element of service availability level together with an identification reference in a NS to a resource management entity for assigning resources comprising network function nodes and their inter-connections in virtual network laying on the network hardware comprising networking nodes when instantiating the NS comprising service flows in the NS chain.