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. The network device transmits instructions to the at least one device for each of the at least two device platforms based on one of a rule or a request associated with the identified one or more contexts.
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.
Abstract:
A method includes receiving readings from a plurality of Internet of Things (IoT) devices. The method identifies rules associated with the readings from the IoT devices and determines a three dimensional (3D) dataset based on the plurality of IoT devices, the readings and rules associated with the readings from the plurality of IoT devices. The method includes determining policies to be applied to routing of the readings based on rules for dividing the readings into subsets of the 3D dataset, and routing processing for subsets of the readings to be processed in parallel by processing units based on the policies. The method further includes processing the readings to generate a list of actions, and resolving the conflicts in the list of actions based on a multi-phase queue. The method also includes executing the actions.
Abstract:
A system may receive from a mobile device, a uniform resource identifier (URI) for accessing secure content associated with a toll-free data campaign for secure content (“campaign”) from a content provider device. The system may identify traffic information included in the URI. The system may compare the traffic information with stored traffic information associated with the campaign and may determine that the traffic information is associated with the campaign if the traffic information matches the stored traffic information. The system may determine that an analysis of a transport layer socket (TLS) handshake, performed between the mobile device and the content provider device, was successful for the campaign. The system may provide information to cause data charges, for a traffic flow, to be charged to a content provider based on determining that the traffic information is associated with the campaign and that the TLS handshake analysis was successful.
Abstract:
A system may include one more devices to receive traffic information for a peer-to-peer communication, between a mobile device and a peer-to-peer client device via a peer-to-peer server, associated with a peer-to-peer network. The system may identify peer-to-peer server information associated with the peer-to-peer server and included in the traffic information and may compare the peer-to-peer server information with stored peer-to-peer server information associated with a toll-free data service campaign (“campaign”). The system may determine that the peer-to-peer server information is associated with the campaign if the peer-to-peer server information matches the stored peer-to-peer server information and may provide information to cause data charges, for the traffic flow, to be charged to a service provider associated with the campaign based on determining that the peer-to-peer server information provided in the traffic information is associated with the campaign.
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.
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. The network device transmits instructions to the at least one device for each of the at least two device platforms based on one of a rule or a request associated with the identified one or more contexts.
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 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.