A method for providing performance guarantees for using microservices in a cloud-native architecture is provided. A network service controller specifies a set of performance characteristics for a particular service that is accessible by a network. The network service controller identifies a particular path in the network for the particular service having a performance guarantee that meets the specified set of performance characteristics. The network service controller configures a host machine running virtualization software with forwarding information for the particular path. The forwarding information is used to tag the packet with a list of transit nodes associated with the particular path when a packet is to be forwarded for the particular service.

The autonomous cloud design system may determine a design that may appropriately mix emerging technologies and operations to provide a versatile and cost-effective or efficient solution for a given cloud site.

Systems and methods include provisioning a default slice having a default subdomain corresponding to a set of resources that are any of physical and virtual components in a network; decomposing the default subdomain into a first set of one or more subdomains, wherein collectively the first set of one or more subdomains include all of the set of resources; provisioning one or more application slices as children from the default slice that inherit capabilities of the default slice; and assigning one or more subdomains from the first set of the one or more subdomains to the respective one or more application slices.

The disclosure relates to a method, executed by an NFV-MANO, for providing a requested Service Availability Level (SAL) for a Network Service (NS). The method comprises at each of a plurality of layers of the NFV-MANO, mapping the requested SAL to a SAL that needs to be provided by a lower layer of the NFV-MANO. The method comprises propagating the mapped requested SAL through interfaces between layers of the NFV-MANO, from an NFVO towards a VIM. The method comprises receiving an estimated SAL′ for the NS based on virtual resources (VR) allocated by the VIM for satisfying the requested SAL. The method comprises, upon determining that the estimated SAL′ does not satisfy the requested SAL, taking actions to meet the requested SAL, or upon determining that the estimated SAL′ satisfies the requested SAL taking no further actions.

The disclosure relates to a method, executed by an NFV-MANO, for providing a requested Service Availability Level (SAL) for a Network Service (NS). The method comprises at each of a plurality of layers of the NFV-MANO, mapping the requested SAL to a SAL that needs to be provided by a lower layer of the NFV-MANO. The method comprises propagating the mapped requested SAL through interfaces between layers of the NFV-MANO, from an NFVO towards a VIM. The method comprises receiving an estimated SAL′ for the NS based on virtual resources (VR) allocated by the VIM for satisfying the requested SAL. The method comprises, upon determining that the estimated SAL′ does not satisfy the requested SAL, taking actions to meet the requested SAL, or upon determining that the estimated SAL′ satisfies the requested SAL taking no further actions.

An IoT electronic device executes services distributed by an IoT service orchestration device. A Lightweight Machine-to-Machine (LwM2M) request message is received. The LwM2M request message contains a LwM2M object identifying hardware resources of the IoT electronic device for which characteristics are requested. A LwM2M command is executed that accesses a LwM2M interface identified based on content of the LwM2M object to determine the characteristics of the hardware resources of the IoT electronic device which are identified by the LwM2M object. A response message contains information identifying the characteristics of the hardware resources of the IoT electronic device. The response message is communicated toward the IoT service orchestrator device. A service image is received for execution which is adapted by the IoT service orchestrator device, responsive to the information in the response message identifying the characteristics of the hardware resources of the IoT electronic device.

An IoT electronic device executes services distributed by an IoT service orchestration device. A Lightweight Machine-to-Machine (LwM2M) request message is received. The LwM2M request message contains a LwM2M object identifying hardware resources of the IoT electronic device for which characteristics are requested. A LwM2M command is executed that accesses a LwM2M interface identified based on content of the LwM2M object to determine the characteristics of the hardware resources of the IoT electronic device which are identified by the LwM2M object. A response message contains information identifying the characteristics of the hardware resources of the IoT electronic device. The response message is communicated toward the IoT service orchestrator device. A service image is received for execution which is adapted by the IoT service orchestrator device, responsive to the information in the response message identifying the characteristics of the hardware resources of the IoT electronic device.

The described technology is directed towards locating and using a template for processing data item data from a general form into a client-specific form for returning in response to a client request. A client request includes a data item identifier and client-specific information. The data item's identifier is processed into a data type and/or identifier, e.g., a string. The client-specific information is used to determine a device class, device type and/or client platform software version. The template is found in a hierarchy of templates based upon the client-specific information and the data type or data ID string, e.g., the client-specific information may be used to determine a subset of template folders that is evaluated to find a file with a filename matching the string. The folders may be ordered from most-specific to least-specific, so as to locate the most specific template file that applies.

The described technology is directed towards locating and using a template for processing data item data from a general form into a client-specific form for returning in response to a client request. A client request includes a data item identifier and client-specific information. The data item's identifier is processed into a data type and/or identifier, e.g., a string. The client-specific information is used to determine a device class, device type and/or client platform software version. The template is found in a hierarchy of templates based upon the client-specific information and the data type or data ID string, e.g., the client-specific information may be used to determine a subset of template folders that is evaluated to find a file with a filename matching the string. The folders may be ordered from most-specific to least-specific, so as to locate the most specific template file that applies.

In general, techniques are described for providing user nomadicity in wireline broadband networks. A network device positioned in a wireline broadband network comprising a processor and an interface may be configured to perform the techniques. The processor may be configured to execute a first virtual customer premises equipment to provide, to a first subscriber, access to the wireline broadband network from a first subscription point in accordance with a first subscription. The processor may also be configured to provide, to a second subscriber, access to the wireline broadband network from the first subscription point in accordance with a second subscription. The interface may be configured to forward, in accordance with the first subscription, traffic received from the first subscription point and associated with the first subscriber, and forward, in accordance with the second subscription, traffic received from the first subscription point and associated with the second subscriber.