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: Systems and methods herein represent an IoT device as an endpoint of private cloud. A virtualization service receives an IoT identifier for an IoT device and a network address for a virtual endpoint for the IoT device. The virtual endpoint for the IoT device is included in a host cloud platform. The virtualization service maps the IoT identifier to the network address in a distributed data structure for the service provider network and provides instructions, for an edge node for the service provider network, to provide network-layer access controls based on the mapping. The edge node for the service provider network receives an access request from the IoT device, applies a network-layer access control for the IoT device based on the instructions, receive IoT data from the IoT device when the edge node permits access by the IoT device, and forwards the IoT data to the virtual endpoint.

Abstract: Systems and methods herein represent an IoT device as an endpoint of private cloud. A virtualization service receives an IoT identifier for an IoT device and a network address for a virtual endpoint for the IoT device. The virtual endpoint for the IoT device is included in a host cloud platform. The virtualization service maps the IoT identifier to the network address in a distributed data structure for the service provider network and provides instructions, for an edge node for the service provider network, to provide network-layer access controls based on the mapping. The edge node for the service provider network receives an access request from the IoT device, applies a network-layer access control for the IoT device based on the instructions, receive IoT data from the IoT device when the edge node permits access by the IoT device, and forwards the IoT data to the virtual endpoint.

Abstract: Systems and methods herein represent an IoT device as an endpoint of private cloud. A virtualization service receives an IoT identifier for an IoT device and a network address for a virtual endpoint for the IoT device. The virtual endpoint for the IoT device is included in a host cloud platform. The virtualization service maps the IoT identifier to the network address in a distributed data structure for the service provider network and provides instructions, for an edge node for the service provider network, to provide network-layer access controls based on the mapping. The edge node for the service provider network receives an access request from the IoT device, applies a network-layer access control for the IoT device based on the instructions, receive IoT data from the IoT device when the edge node permits access by the IoT device, and forwards the IoT data to the virtual endpoint.

Abstract: A network device stores capability designations associated with Internet-of-Things (IoT) devices and receives, from a customer device, one or more of the capability designations associated with a first type of IoT device. The network device receives event data generated by the first type of IoT device and maps the event data to the one or more of the capability designations. The mapping produces normalized IoT data for the first type of IoT device. The network device generates semantic information for the normalized IoT data and assembles a device model for the first type of IoT device. The device model includes the one or more of the capability designations and the semantic information.

Abstract: Systems and methods herein represent an IoT device as an endpoint of private cloud. A virtualization service receives an IoT identifier for an IoT device and a network address for a virtual endpoint for the IoT device. The virtual endpoint for the IoT device is included in a host cloud platform. The virtualization service maps the IoT identifier to the network address in a distributed data structure for the service provider network and provides instructions, for an edge node for the service provider network, to provide network-layer access controls based on the mapping. The edge node for the service provider network receives an access request from the IoT device, applies a network-layer access control for the IoT device based on the instructions, receive IoT data from the IoT device when the edge node permits access by the IoT device, and forwards the IoT data to the virtual endpoint.

Abstract: A network device stores capability designations associated with Internet-of-Things (IoT) devices and receives, from a customer device, one or more of the capability designations associated with a first type of IoT device. The network device receives event data generated by the first type of IoT device and maps the event data to the one or more of the capability designations. The mapping produces normalized IoT data for the first type of IoT device. The network device generates semantic information for the normalized IoT data and assembles a device model for the first type of IoT device. The device model includes the one or more of the capability designations and the semantic information.

Abstract: A mobile device may include first and second communication interfaces. The mobile device may receive, from another device, a dispatch message to receive data from an Internet of Things (IoT) device. The mobile device may send, to the other device and based on the dispatch message, a device key. The mobile device may receive, from the other device, a session ticket generated by the other device. The IoT device may have previously received a copy of the session ticket. The mobile device may send the session ticket to the IoT device. The mobile device may receive data, from the IoT device and via the first communication interface, based on the session ticket matching the copy of the session ticket. The mobile device may format the data for transmission via the second communication interface. The mobile device may send, via the second communication interface, the data to a network device.

Abstract: A device may receive device information and operation information relating to an Internet of Things (IoT) device type corresponding to IoT devices that are configured to perform a particular operation based on receiving a particular command message. The device information may identify IoT devices of the IoT device type, and the operation information may identify operations that the IoT devices are capable of performing. The device may generate an application programming interface (API) based on the operation information. The API may associate the operations with one or more respective instructions, and may permit a client device to control operation of the IoT devices. An instruction, of the one or more respective instructions, when received by the device, may cause the device to cause a corresponding command message to be transmitted to an IoT device of the IoT devices. The device may store or provide the API.

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 network device receives a definition for a data product of consumer Internet-of-Things (IoT) data and registers multiple machine-type communications (MTC)-devices for collection of consumer IoT data. The MTC devices provide the consumer IoT data with heterogeneous formats. The registering identifies a profile for each MTC device and particular data types authorized for collection. The network device receives consumer IoT data generated by the multiple MTC devices and extracts the particular data types from the IoT data. The network device normalizes the extracted data to include a uniform data format, and aggregates the normalized IOT data into clusters that exclude device identifiers. The network device constructs the clusters into a data portfolio that meets the definition for the data product.

Abstract: A network device receives a definition for a data product of consumer Internet-of-Things (IoT) data and registers multiple machine-type communications (MTC)-devices for collection of consumer IoT data. The MTC devices provide the consumer IoT data with heterogeneous formats. The registering identifies a profile for each MTC device and particular data types authorized for collection. The network device receives consumer IoT data generated by the multiple MTC devices and extracts the particular data types from the IoT data. The network device normalizes the extracted data to include a uniform data format, and aggregates the normalized IOT data into clusters that exclude device identifiers. The network device constructs the clusters into a data portfolio that meets the definition for the data product.

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 mobile device may include first and second communication interfaces. The mobile device may receive, from another device, a dispatch message to receive data from an Internet of Things (IoT) device. The mobile device may send, to the other device and based on the dispatch message, a device key. The mobile device may receive, from the other device, a session ticket generated by the other device. The IoT device may have previously received a copy of the session ticket. The mobile device may send the session ticket to the IoT device. The mobile device may receive data, from the IoT device and via the first communication interface, based on the session ticket matching the copy of the session ticket. The mobile device may format the data for transmission via the second communication interface. The mobile device may send, via the second communication interface, the data to a network device.

Abstract: A method for processing media content is described. The method includes steps of receiving via a wireless network and at a content processing server media content of an activity captured by a mobile device; identifying a location of the mobile device and a location of the activity; and identifying a point of view characteristic of the received media content based on the location of the mobile device and the location of the activity. It is then determined whether the point of view characteristic of the received media content corresponds to a desired point of view of the activity. Upon determining the point of view characteristic of the received media content corresponds to the desired point of view, the content processing server selects to perform at least one of uploading and/or distributing of the media content via the content processing server to a user display device.

Abstract: A method for processing media content is described. The method includes steps of receiving via a wireless network and at a content processing server media content of an activity captured by a mobile device; identifying a location of the mobile device and a location of the activity; and identifying a point of view characteristic of the received media content based on the location of the mobile device and the location of the activity. It is then determined whether the point of view characteristic of the received media content corresponds to a desired point of view of the activity. Upon determining the point of view characteristic of the received media content corresponds to the desired point of view, the content processing server selects to perform at least one of uploading and/or distributing of the media content via the content processing server to a user display device.

Abstract: A device may receive device information and operation information relating to an Internet of Things (IoT) device type corresponding to IoT devices that are configured to perform a particular operation based on receiving a particular command message. The device information may identify IoT devices of the IoT device type, and the operation information may identify operations that the IoT devices are capable of performing. The device may generate an application programming interface (API) based on the operation information. The API may associate the operations with one or more respective instructions, and may permit a client device to control operation of the IoT devices. An instruction, of the one or more respective instructions, when received by the device, may cause the device to cause a corresponding command message to be transmitted to an IoT device of the IoT devices. The device may store or provide the API.

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: 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.