Abstract: Examples herein involve a multi-access edge computing (MEC) environment. An example process may include receiving a tenant application that is to be hosted in a MEC environment. The MEC environment may be situated between a user device and an external platform. The process may include assigning an edge service identifier (ESID) to the tenant application. The ESID may be used to indicate that a message, associated with the user device, involves the tenant application. The process may include assigning a host identifier to the tenant application. The host identifier may be used to indicate that report data, associated with execution of the tenant application within the MEC environment, is to be provided to the external platform. The process may include routing communications associated with the tenant application using the ESID and the host identifier.

Abstract: An internet-of-things (IoT) distribution hub enables delivery of formatted IoT data to any of multiple hosting platforms as dynamically configurable by an IoT device owner. A service node in a distributed network provides, to an IoT device, a device key for accessing an IoT distribution network. The service node receives a selection of a hosting platform for the IoT device, wherein the selected hosting platform is one from a group of available hosting platforms available through the IoT distribution network. The service node maps the IoT device to a virtual device proxy for the selected hosting platform and receives a request from the IoT device to forward IoT data. The request includes the device key. The service node forwards the IoT data to the selected hosting platform via the virtual device proxy.

Abstract: Examples herein involve a multi-access edge computing (MEC) environment. An example process may include receiving a tenant application that is to be hosted in a MEC environment. The MEC environment may be situated between a user device and an external platform. The process may include assigning an edge service identifier (ESID) to the tenant application. The ESID may be used to indicate that a message, associated with the user device, involves the tenant application. The process may include assigning a host identifier to the tenant application. The host identifier may be used to indicate that report data, associated with execution of the tenant application within the MEC environment, is to be provided to the external platform. The process may include routing communications associated with the tenant application using the ESID and the host identifier.

Abstract: An internet-of-things (IoT) distribution hub enables delivery of formatted IoT data to any of multiple hosting platforms as dynamically configurable by an IoT device owner. A service node in a distributed network provides, to an IoT device, a device key for accessing an IoT distribution network. The service node receives a selection of a hosting platform for the IoT device, wherein the selected hosting platform is one from a group of available hosting platforms available through the IoT distribution network. The service node maps the IoT device to a virtual device proxy for the selected hosting platform and receives a request from the IoT device to forward IoT data. The request includes the device key. The service node forwards the IoT data to the selected hosting platform via the virtual device proxy.

Abstract: Examples herein involve a multi-access edge computing (MEC) environment. An example process may include receiving a tenant application that is to be hosted in a MEC environment. The MEC environment may be situated between a user device and an external platform. The process may include assigning an edge service identifier (ESID) to the tenant application. The ESID may be used to indicate that a message, associated with the user device, involves the tenant application. The process may include assigning a host identifier to the tenant application. The host identifier may be used to indicate that report data, associated with execution of the tenant application within the MEC environment, is to be provided to the external platform. The process may include routing communications associated with the tenant application using the ESID and the host identifier.

Abstract: An internet-of-things (IoT) distribution hub enables delivery of formatted IoT data to any of multiple hosting platforms as dynamically configurable by an IoT device owner. A service node in a distributed network provides, to an IoT device, a device key for accessing an IoT distribution network. The service node receives a selection of a hosting platform for the IoT device, wherein the selected hosting platform is one from a group of available hosting platforms available through the IoT distribution network. The service node maps the IoT device to a virtual device proxy for the selected hosting platform and receives a request from the IoT device to forward IoT data. The request includes the device key. The service node forwards the IoT data to the selected hosting platform via the virtual device proxy.

Abstract: An internet-of-things (IoT) distribution hub enables delivery of formatted IoT data to any of multiple hosting platforms as dynamically configurable by an IoT device owner. A service node in a distributed network provides, to an IoT device, a device key for accessing an IoT distribution network. The service node receives a selection of a hosting platform for the IoT device, wherein the selected hosting platform is one from a group of available hosting platforms available through the IoT distribution network. The service node maps the IoT device to a virtual device proxy for the selected hosting platform and receives a request from the IoT device to forward IoT data. The request includes the device key. The service node forwards the IoT data to the selected hosting platform via the virtual device proxy.

Abstract: An internet-of-things (IoT) distribution hub enables delivery of formatted IoT data to any of multiple hosting platforms as dynamically configurable by an IoT device owner. A service node in a distributed network provides, to an IoT device, a device key for accessing an IoT distribution network. The service node receives a selection of a hosting platform for the IoT device, wherein the selected hosting platform is one from a group of available hosting platforms available through the IoT distribution network. The service node maps the IoT device to a virtual device proxy for the selected hosting platform and receives a request from the IoT device to forward IoT data. The request includes the device key. The service node forwards the IoT data to the selected hosting platform via the virtual device proxy.

Abstract: Examples herein involve a multi-access edge computing (MEC) environment. An example process may include receiving a tenant application that is to be hosted in a MEC environment. The MEC environment may be situated between a user device and an external platform. The process may include assigning an edge service identifier (ESID) to the tenant application. The ESID may be used to indicate that a message, associated with the user device, involves the tenant application. The process may include assigning a host identifier to the tenant application. The host identifier may be used to indicate that report data, associated with execution of the tenant application within the MEC environment, is to be provided to the external platform. The process may include routing communications associated with the tenant application using the ESID and the host identifier.

Abstract: An internet-of-things (IoT) distribution hub enables delivery of formatted IoT data to any of multiple hosting platforms as dynamically configurable by an IoT device owner. A service node in a distributed network provides, to an IoT device, a device key for accessing an IoT distribution network. The service node receives a selection of a hosting platform for the IoT device, wherein the selected hosting platform is one from a group of available hosting platforms available through the IoT distribution network. The service node maps the IoT device to a virtual device proxy for the selected hosting platform and receives a request from the IoT device to forward IoT data. The request includes the device key. The service node forwards the IoT data to the selected hosting platform via the virtual device proxy.

Abstract: An exemplary method includes a computer-implemented cloud service brokering system that provides a cloud service brokering service 1) registering a plurality of cloud services with the cloud service brokering service, the plurality of cloud services provided by a plurality of cloud service providers and configured to provide distinct sets of cloud computing resources as a service, 2) receiving, from a customer of the cloud service brokering service, cloud service request information, 3) selecting, based on the cloud service request information, a cloud computing resource from the distinct sets of cloud computing resources provided by the plurality of cloud services registered with the cloud service brokering service, and 4) allocating the selected cloud computing resource for use by the customer. In certain examples, the allocating may be supported by the system configuring a customer network to support implicit and/or explicit transport requirements. Corresponding systems and methods are also described.