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 framework for a machine-to-machine (M2M) application development is disclosed. The framework enables users to login and affect devices and applications that may interact with the devices by enabling M2M applications. The framework enables M2M application creation, management, and development of various profiled devices based on pre-defined data models associated with corresponding devices. Furthermore, the framework enables marketplace options to permit users to specify purchase options as well as to buy devices and applications.
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 device may determine a condition for providing customer information to a mobile device. The device may detect the mobile device, and may request, from the mobile device and based on detecting the mobile device, information that identifies a user communication preference associated with providing the customer information to the mobile device. The device may receive, from the mobile device and based on the request, the information that identifies the user communication preference. The device may determine whether the customer information is to be provided to the mobile device based on the user communication preference and the condition, and may selectively provide the customer information and an instruction to the mobile device based on determining whether the customer information is to be provided to the mobile device. The instruction may cause the mobile device to relay the customer information to a network storage device.
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.