Abstract: A network device receives, from a node in an Internet-of-Things (IoT) network, an access request for a user authenticated via the node and identifies the access request as from either of a trusted node or an untrusted node in the IoT network. When the access request is from an untrusted node, the network device identifies a hash key for the access request, wherein the hash key is derived from an access list for the IoT network; broadcasts the hash key to other trusted nodes in the IoT network; and validates the access request based on a solution consensus from the other trusted nodes. When the access request is from a trusted node, the network device confirms mutual trust with the trusted node via an encrypted key exchange, and validates the access request based on the mutual trust with the trusted node.

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 device may receive data, to be provided to a second device, and an application identifier. The data and application identifier may be received from a third device. The first device may be associated with a first network, and the second device may be associated with a second network. The first network may be a different network than the second network. The application identifier may be associated with the second device. The first device may determine that the data is destined to the second device based on the application identifier. The first device may cause a secure session to be established with the second device. The secure session may allow the data to be securely transmitted from the third device to the second device. The first device may provide the data to the second device via the secure session.

Abstract: A device may receive traffic flow information that includes user device identifiers. The device may receive, from a user device accessing an application associated with a third party service, an authentication request to authenticate the user device with a third party device that provides the third party service. The request may include a session token that identifies a session, an application identifier that identifies the application, and a user device identifier that identifies the user device. The device may determine to authenticate the user device based on whether the user device identifier matches one of the user device identifiers included in the traffic flow information. The device may provide, to the third party device, the session token and an indication of whether the user device has been authenticated to permit the third party device to allow or deny access to the third party service.

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 device receives, via a Public Land Mobile Network (PLMN), a manifest file associated with streaming content, wherein the manifest file includes a sequence of multiple Uniform Resource Identifiers (URIs) that identify network storage locations of multiple content segments of the streaming content, and wherein a sponsorship signature of multiple sponsorship signatures is appended to at least one of the multiple URIs of the manifest file. The device retrieves the multiple URIs, and the sponsorship signature, from the manifest file; sends the sponsorship signature to a charging node in the PLMN for controlling the charging of data delivery associated with the streaming content to one of a user of the media playing device or a sponsor of the streaming content based on the sponsorship signature; and engages, via the PLMN using the multiple URIs, in a content streaming session to receive the streaming content.

Abstract: A device can receive a request to determine a set of navigational directions, and can obtain a set of traffic objects associated with a first map layer. The set of traffic objects can include nodes to identify one or more geographic locations and one or more links to identify one or more geographic areas between the nodes. The device can determine a shortest-path tree by analyzing the set of traffic objects, the shortest-path tree being associated with a static data structure. The device can generate a dynamic data structure that includes the shortest-path tree and a set of additional traffic objects associated with a second map layer. The device can determine a shortest path by analyzing traffic objects associated with the shortest-path tree and the set of additional traffic objects. The device can provide the set of navigational directions to indicate the shortest path.

Abstract: A network device receives, from a node in an Internet-of-Things (IoT) network, an access request for a user authenticated via the node and identifies the access request as from either of a trusted node or an untrusted node in the IoT network. When the access request is from an untrusted node, the network device identifies a hash key for the access request, wherein the hash key is derived from an access list for the IoT network; broadcasts the hash key to other trusted nodes in the IoT network; and validates the access request based on a solution consensus from the other trusted nodes. When the access request is from a trusted node, the network device confirms mutual trust with the trusted node via an encrypted key exchange, and validates the access request based on the mutual trust with the trusted node.

Abstract: A server device may determine content prediction parameters associated with multiple items of content; generate respective content prediction aggregate scores for each of the multiple items of content based on the content prediction parameters. A particular content prediction aggregate score, associated with a particular content, may be generated based on content prediction parameters associated with the particular content. The server device may generate a content prediction instruction; and may provide the content prediction instruction to cause the user device to receive and store a portion of the particular item of content.

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 provide for receiving data that indicates programs available to users, wherein the programs include linear television programs, video-on-demand programs, and pay-per-view programs; determining, by the network device, a popularity value for each program; comparing, by the network device, each popularity value with a threshold popularity value; determining, by the network device, whether each popularity value satisfies the threshold popularity value; assigning, by the network device, each program associated with each popularity value that satisfies the threshold popularity value to multicast delivery based on the determining, wherein one or more programs assigned to multicast delivery include one or more of a video-on-demand program or a pay-per-view program; and multicasting each program assigned to multicast delivery.

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 and system relate to receiving first comments, associated with first digital content, that are submitted by a first user, and determining an opinion of the first user with respect to the first digital content based on the one or more first comments. Determining the opinion of the first user with respect to the first digital content includes parsing the one or more first comments to determine a term included in the one or more first comments, and determining the opinion based on the term. The first user is clustered with second users who share the first users opinion regarding the first digital content. Second digital content, liked by at least one of the second users and have accessed by the first user, are identified, and a recommendation identifying the second digital content is presented for display to the first user.

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 network device receives a plurality of framework definitions corresponding to a respective plurality of device platforms, wherein each of the device platforms comprises at least one device. The network device generates a plurality of generalized framework definitions for each of the plurality of device platforms, wherein the plurality of generalized framework definitions comprise basic linguistic components corresponding to elements in the respective plurality of framework definitions. The network device receives data from the at least one device for each of the device platforms. The network device extracts data from the received data based on the plurality of generalized framework definitions. The network device automatically identifies contexts that include at least one device for each of the at least two device platforms based on the extracted data.

Abstract: Methods, systems, and computer program products for providing location based services are provided. Embodiments may include storing locations for a plurality of users of a telecommunication environment and contact lists of associated users for the plurality of users. Embodiments may also include providing the locations of the associated users for a first user based on a request from the first user. The request may further include providing locations for associated users who are located within an area of interest. The area of interest may be defined by a particular distance from the first user or by a point of interest of the first user. The locations of the users may be determined based on the locations of communication devices of the users including an identified receiving communication device for each user.

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 first device may receive a request from a second device. The request may include a device identifier associated with the second device. The request may be transmitted by the second device to obtain a signature, based on which to access a third device. The first device may determine that the device identifier is associated with a secure authentication service. The first device may generate a signature based on determining that the device identifier is associated with the secure authentication service. The first device may provide the signature to the third device. The signature may permit the third device to selectively permit or deny access by the second device based on a result of authenticating the signature. Access may be permitted when the third device successfully authenticates the signature, and access may be denied when the third device fails to authenticate the signature.

Abstract: A system may receive tag information, associated with media content, that includes a tag and a tag time. The system may generate, based on the tag information, clip information that includes a start time and an end time for a media content clip associated with the media content. The system may determine, based on the tag information, advertisement information that identifies an advertisement to be displayed with the media content clip, and indicates how the advertisement is to be displayed. The system may provide the tag information for display via a social media application, and may receive, via the social media application, an indication that the media content clip is to be provided for display to a user. The system may provide the advertisement information and the clip information such that the advertisement and the media content clip are provided for display to the user based on the advertisement information.

Abstract: A network device enables browsing of a plurality of pre-defined VMs associated with IoT devices. The network device receives, from a user device, selection of a first pre-defined VM from the plurality of pre-defined VMs, wherein the first pre-defined VM includes at least one first device state and at least one first sensor type, and receives, from the user device, instructions to modify the first pre-defined VM, by adding an additional device state or an additional sensor type to the first pre-defined VM or by removing the at least one first device state or the at least one first sensor type from the first pre-defined VM, to create a first customized VM associated with a first physical IoT device. The network device stores the first customized VM in a database, and uses the first customized VM for accessing or controlling the first physical IoT device.