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: A system dynamically assigns spaces to users. The system acquires scheduling information for users and identified times when one of the spaces should be assigned to a group of the users (e.g., when a meeting is scheduled). The system may select the space based on the size of the group. The users wear smart identifier (ID) badges that transmit short-range communications signals. A detector detects the signals and may forward a notification to the system identifying the users' locations. The system dynamically re-assigns the space to different users if more than a threshold portion of the group members are, based on the determined locations, not expected to reach the reserved space at the scheduled time. The system assigns a different space to the group that is closer to the determined locations and/or more appropriately sized for the number of available group members.

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: A status of an Internet of Things (IoT) device included in a local area cloud is identified. The local area cloud includes IoT devices that are connected in a wireless local area network (WLAN), and one IoT device functions as a leader of the local area cloud. A cloud server associated with the IoT device is identified and information identifying the status is forwarded to the cloud server via a wireless wide area network (WWAN). The cloud server selects an action to be performed by the IoT device and forwards data identifying the action. The leader receives and distributes information identifying the action to the IoT device via the local area cloud. The action may include actions by multiple IoT devices in the local area cloud or IoT devices included in multiple local area clouds. A user may input data to control the cloud server.

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: A method, a device, and a non-transitory storage medium provides to receive a packet from an Internet of Things (IoT) device; determine whether the packet carries IoT data; determine a type of linked data to obtain in response to a determination that the packet carries the IoT data, wherein a determination of the type of linked data is based on at least one of a source network address of the IoT device or a device identifier of the IoT device that correlates to an application programming interface (API) and corresponding type of linked data; obtain the type of linked data in response to the determination of the type of linked data; store the type of linked data and the IoT data; and grant access and use of the type of linked data and the IoT data to the API of a software application, when the software application is executed.

Abstract: A method, a device, and a non-transitory storage medium provides to receive a packet from an Internet of Things (IoT) device; determine whether the packet carries IoT data; determine a type of linked data to obtain in response to a determination that the packet carries the IoT data, wherein a determination of the type of linked data is based on at least one of a source network address of the IoT device or a device identifier of the IoT device that correlates to an application programming interface (API) and corresponding type of linked data; obtain the type of linked data in response to the determination of the type of linked data; store the type of linked data and the IoT data; and grant access and use of the type of linked data and the IoT data to the API of a software application, when the software application is executed.

Abstract: A first network device receives a token request from an application and, in response, generates a token that includes a time-stamp and a server identifier. The server identifier indicates a particular proxy server, of a group of proxy servers, in an API management layer. A second network device receives, from an application, an API call that includes the token and validates the token. The second network device routes the API call to the particular proxy server indicated by the token in response to successfully validating the token. The first network device or second network device provides a bypass uniform resource locator (URL), to the application, to bypass the API management layer, for one or more types of designated API calls.

Abstract: A method, a device, and a non-transitory storage medium provides to receive a packet from an Internet of Things (IoT) device, wherein the packet carries IoT data; determine whether the packet carries IoT data; determine a type of linked data to obtain in response to a determination that the packet carries the IoT data, wherein a determination of the type of linked data is based on an application programming interface (API) identifier that identifies an API and corresponding type of linked data; obtain the type of linked data in response to the determination of the type of linked data; store the type of linked data and the IoT data; and grant access and use of the type of linked data and the IoT data to the API of a software application, when the software application is executed.

Abstract: A system dynamically assigns spaces to users. The system acquires scheduling information for users and identified times when one of the spaces should be assigned to a group of the users (e.g., when a meeting is scheduled). The system may select the space based on the size of the group. The users wear smart identifier (ID) badges that transmit short-range communications signals. A detector detects the signals and may forward a notification to the system identifying the users' locations. The system dynamically re-assigns the space to different users if more than a threshold portion of the group members are, based on the determined locations, not expected to reach the reserved space at the scheduled time. The system assigns a different space to the group that is closer to the determined locations and/or more appropriately sized for the number of available group members.

Abstract: A status of an Internet of Things (IoT) device included in a local area cloud is identified. The local area cloud includes IoT devices that are connected in a wireless local area network (WLAN), and one IoT device functions as a leader of the local area cloud. A cloud server associated with the IoT device is identified and information identifying the status is forwarded to the cloud server via a wireless wide area network (WWAN). The cloud server selects an action to be performed by the IoT device and forwards data identifying the action. The leader receives and distributes information identifying the action to the IoT device via the local area cloud. The action may include actions by multiple IoT devices in the local area cloud or IoT devices included in multiple local area clouds. A user may input data to control the cloud server.

Abstract: A method, a device, and a non-transitory storage medium provides to receive a packet from an Internet of Things (IoT) device, wherein the packet carries IoT data; determine whether the packet carries IoT data; determine a type of linked data to obtain in response to a determination that the packet carries the IoT data, wherein a determination of the type of linked data is based on an application programming interface (API) identifier that identifies an API and corresponding type of linked data; obtain the type of linked data in response to the determination of the type of linked data; store the type of linked data and the IoT data; and grant access and use of the type of linked data and the IoT data to the API of a software application, when the software application is executed.

Abstract: A first network device receives a token request from an application and, in response, generates a token that includes a time-stamp and a server identifier. The server identifier indicates a particular proxy server, of a group of proxy servers, in an API management layer. A second network device receives, from an application, an API call that includes the token and validates the token. The second network device routes the API call to the particular proxy server indicated by the token in response to successfully validating the token. The first network device or second network device provides a bypass uniform resource locator (URL), to the application, to bypass the API management layer, for one or more types of designated API calls.