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 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 logs transmission control protocol (TCP) flow data for connections between registered devices that are registered for use of secure Internet of Things (IoT) application programming interfaces (APIs). The logging generates logged flow data. The network device receives, from a first registered device, a call validation request for an IoT API call directed to the first registered device from a second registered device. The call validation request includes packet information of the IoT API call. The network device compares the packet information with the logged TCP flow data. When the comparing indicates a match of the packet information and the logged TCP flow data, the network device sends a response to the first registered device to accept the IoT API call. Otherwise, the network device sends a response to the first registered device to reject the IoT API call.
Abstract:
A method, in a multiple modem device that includes a notification modem and a Wi-Fi modem, includes identifying data to be collected and rules for selecting an optimal modem for data transmission from the multiple modem device. The method also includes collecting the data, and determining whether the data is to be sent via the notification modem based on a payload size associated with the data and the rules. The method includes sending the data via a control channel of a cellular network associated with the notification modem in response to a determination that the data to be sent via the notification modem. A determination whether a Wi-Fi network is available is made in response to a determination that the data is not to be sent via the notification modem. The data is sent via the Wi-Fi modem over the Wi-Fi network.
Abstract:
Attributes of a session, between a source device and a verification device, for sending first verification data, such as a password and an account identifier, are determined. The verification device generates user device data based on an identifier, such as a mobile device number (MDN), for a user device associated with the account identifier. An identifier, such as an MDN, associated with the source device and an encryption key associated with the verification device are determined based on session attributes. Second verification data is generated based on the identifier associated with the source device. The second verification data is encrypted using the encryption key and forwarded to the verification device. The verification device decrypts the second verification data and compares the identifier for the user device to the identifier for the source device to determine whether the first verification data was sent from the user device.
Abstract:
A device includes an audio capture device for receiving an audio signal in an ultrasonic frequency range. The device includes a processor to determine whether the received audio signal corresponds to an ultrasonic message. The processor extracts a content of the ultrasonic message, when it is determined that the received audio signal corresponds to an ultrasonic message, automatically handles the ultrasonic message based on the extracted content, stores at least a portion of the content of the ultrasonic message, and displays the portion of the content of the ultrasonic message to a user of the mobile device at a time subsequent to a time of the receipt of the audio signal.