Abstract: An Internet of Things (IoT) module adaptor application may be used to provide operational compatibility between a device application of an IoT device and multiple IoT modules. The IoT module adaptor application may detect that an IoT module is connected to the IoT device, in which the IoT module provides a network connectivity functionality to the IoT device. An identity of the IoT module is ascertained by the IoT module adaptor application based on identification information provided by the IoT module. The IoT module adaptor application may determine a specific combination of at least one of one or more ATtention (AT) commands or one or more application program interfaces (APIs) as stored in a software library that corresponds to the identity of the IoT module. Subsequently, the IoT module adaptor application may provide a device application of the IoT device with access to the specific combination for the device application to interact with the IoT module.

Abstract: A network terminal, e.g., a smartphone, can retrieve, from a datastore, a cryptographically-signed configuration record including a device identifier of the terminal. The terminal can transmit a request message comprising the configuration record and the device identifier. A network device can verify authenticity of the device identifier and a match between the identifier in the record and the identifier in the message. In response to confirmation of the request by a policy engine, the network device can determine a reply message comprising a cryptographically-signed second configuration record that includes a second device identifier. The terminal can verify that the signature is valid and that the second device identifier matches the device identifier. In response, the terminal can modify data in the datastore according to the second configuration record. The configuration record can lock or unlock the terminal, or determine permitted services or network peers.

Abstract: A NarrowBand-Internet of Things (NB-IoT) device is transitioned from using non-Internet Protocol (IP) communication to using IP communication for device management. A service capability server (SCS) of a core network may receive data from an NB-IoT device via non-IP communication. The SCS may send a command to the NB-IoT device via the non-IP communication to trigger the NB-IoT device to transition to using IP communication to communicate with the SCS. Subsequently, the SCS may command the NB-IoT device to perform one or more device management functions via the IP communication.

Abstract: Systems and methods for automatically and securely connecting internet of things (IoT) devices to one or more networks. The system can include a bootstrap server and a configuration database to enable configuration settings for a plurality of IoT devices to be stored and accessed. The bootstrap server can configure an appropriate digital security certificate for an IoT device requesting access to the network. The bootstrap server can then provide a bootstrapping message to the IoT device including the digital certificate and other data. A device management server can then provide a device management message to the IoT device to provide one or more of a final configuration, applications, and software or firmware updates. The system replaces the current system, which is substantially manual, with an essentially “touchless” system that requires little or no input from the user or service provider technicians.

Abstract: A NarrowBand-Internet of Things (NB-IoT) device is transitioned from using non-Internet Protocol (IP) communication to using IP communication for device management. A service capability server (SCS) of a core network may receive data from an NB-IoT device via non-IP communication. The SCS may send a command to the NB-IoT device via the non-IP communication to trigger the NB-IoT device to transition to using IP communication to communicate with the SCS. Subsequently, the SCS may command the NB-IoT device to perform one or more device management functions via the IP communication.

Abstract: A network terminal, e.g., a smartphone, can retrieve, from a datastore, a cryptographically-signed configuration record including a device identifier of the terminal. The terminal can transmit a request message comprising the configuration record and the device identifier. A network device can verify authenticity of the device identifier and a match between the identifier in the record and the identifier in the message. In response to confirmation of the request by a policy engine, the network device can determine a reply message comprising a cryptographically-signed second configuration record that includes a second device identifier. The terminal can verify that the signature is valid and that the second device identifier matches the device identifier. In response, the terminal can modify data in the datastore according to the second configuration record. The configuration record can lock or unlock the terminal, or determine permitted services or network peers.

Abstract: An Internet of Things (IoT) module adaptor application may be used to provide operational compatibility between a device application of an IoT device and multiple IoT modules. The IoT module adaptor application may detect that an IoT module is connected to the IoT device, in which the IoT module provides a network connectivity functionality to the IoT device. An identity of the IoT module is ascertained by the IoT module adaptor application based on identification information provided by the IoT module. The IoT module adaptor application may determine a specific combination of at least one of one or more ATtention (AT) commands or one or more application program interfaces (APIs) as stored in a software library that corresponds to the identity of the IoT module. Subsequently, the IoT module adaptor application may provide a device application of the IoT device with access to the specific combination for the device application to interact with the IoT module.

Abstract: This disclosure sets forth systems and techniques that automatically allocate and throttle back resource capacity to multiple campaign events, in real-time, based on campaign event priorities and a supply and demand of available resource capacity. For example, a campaign management system may re-allocate unused resource capacity to a particular campaign event based on the particular campaign event's real-time demand for additional resource capacity. Unused resource capacity may originate from a common pool of resource capacity, or from other campaign events that have an over-allocation of resource capacity that is being underutilized. Further, the techniques described herein also describe throttling back resource capacity of a particular campaign event in response to determining that an existing pool of available resource capacity is unable to serve the particular campaign event's requirements.

Abstract: A network terminal, e.g., a smartphone, can retrieve, from a datastore, a cryptographically-signed configuration record including a device identifier of the terminal. The terminal can transmit a request message comprising the configuration record and the device identifier. A network device can verify authenticity of the device identifier and a match between the identifier in the record and the identifier in the message. In response to confirmation of the request by a policy engine, the network device can determine a reply message comprising a cryptographically-signed second configuration record that includes a second device identifier. The terminal can verify that the signature is valid and that the second device identifier matches the device identifier. In response, the terminal can modify data in the datastore according to the second configuration record. The configuration record can lock or unlock the terminal, or determine permitted services or network peers.

Abstract: Systems and methods for automatically and securely connecting internet of things (IoT) devices to one or more networks. The system can include a bootstrap server and a configuration database to enable configuration settings for a plurality of IoT devices to be stored and accessed. The bootstrap server can configure an appropriate digital security certificate for an IoT device requesting access to the network. The bootstrap server can then provide a bootstrapping message to the IoT device including the digital certificate and other data. A device management server can then provide a device management message to the IoT device to provide one or more of a final configuration, applications, and software or firmware updates. The system replaces the current system, which is substantially manual, with an essentially “touchless” system that requires little or no input from the user or service provider technicians.

Abstract: This disclosure sets forth systems and techniques that automatically allocate and throttle back resource capacity to multiple campaign events, in real-time, based on campaign event priorities and a supply and demand of available resource capacity. For example, a campaign management system may re-allocate unused resource capacity to a particular campaign event based on the particular campaign event's real-time demand for additional resource capacity. Unused resource capacity may originate from a common pool of resource capacity, or from other campaign events that have an over-allocation of resource capacity that is being underutilized. Further, the techniques described herein also describe throttling back resource capacity of a particular campaign event in response to determining that an existing pool of available resource capacity is unable to serve the particular campaign event's requirements.

Abstract: This disclosure sets forth systems and techniques that automatically allocate and throttle back resource capacity to multiple campaign events, in real-time, based on campaign event priorities and a supply and demand of available resource capacity. For example, a campaign management system may re-allocate unused resource capacity to a particular campaign event based on the particular campaign event's real-time demand for additional resource capacity. Unused resource capacity may originate from a common pool of resource capacity, or from other campaign events that have an over-allocation of resource capacity that is being underutilized. Further, the techniques described herein also describe throttling back resource capacity of a particular campaign event in response to determining that an existing pool of available resource capacity is unable to serve the particular campaign event's requirements.

Abstract: A network terminal, e.g., a smartphone, can retrieve, from a datastore, a cryptographically-signed configuration record including a device identifier of the terminal. The terminal can transmit a request message comprising the configuration record and the device identifier. A network device can verify authenticity of the device identifier and a match between the identifier in the record and the identifier in the message. In response to confirmation of the request by a policy engine, the network device can determine a reply message comprising a cryptographically-signed second configuration record that includes a second device identifier. The terminal can verify that the signature is valid and that the second device identifier matches the device identifier. In response, the terminal can modify data in the datastore according to the second configuration record. The configuration record can lock or unlock the terminal, or determine permitted services or network peers.

Abstract: This disclosure sets forth systems and techniques that automatically allocate and throttle back resource capacity to multiple campaign events, in real-time, based on campaign event priorities and a supply and demand of available resource capacity. For example, a campaign management system may re-allocate unused resource capacity to a particular campaign event based on the particular campaign event's real-time demand for additional resource capacity. Unused resource capacity may originate from a common pool of resource capacity, or from other campaign events that have an over-allocation of resource capacity that is being underutilized. Further, the techniques described herein also describe throttling back resource capacity of a particular campaign event in response to determining that an existing pool of available resource capacity is unable to serve the particular campaign event's requirements.

Abstract: This disclosure sets forth systems and techniques that automatically allocate and throttle back resource capacity to multiple campaign events, in real-time, based on campaign event priorities and a supply and demand of available resource capacity. For example, a campaign management system may re-allocate unused resource capacity to a particular campaign event based on the particular campaign event's real-time demand for additional resource capacity. Unused resource capacity may originate from a common pool of resource capacity, or from other campaign events that have an over-allocation of resource capacity that is being underutilized. Further, the techniques described herein also describe throttling back resource capacity of a particular campaign event in response to determining that an existing pool of available resource capacity is unable to serve the particular campaign event's requirements.

Abstract: This disclosure sets forth systems and techniques that automatically allocate and throttle back resource capacity to multiple campaign events, in real-time, based on campaign event priorities and a supply and demand of available resource capacity. For example, a campaign management system may re-allocate unused resource capacity to a particular campaign event based on the particular campaign event's real-time demand for additional resource capacity. Unused resource capacity may originate from a common pool of resource capacity, or from other campaign events that have an over-allocation of resource capacity that is being underutilized. Further, the techniques described herein also describe throttling back resource capacity of a particular campaign event in response to determining that an existing pool of available resource capacity is unable to serve the particular campaign event's requirements.

Abstract: Techniques for managing assignment and reassignment of short codes are described herein. One or more computing devices may assign a short code to a first messaging campaign for a first time period. After expiration of the first time period, the one or more computing devices may then reassign the short code to a second messaging campaign for a second time period.

Abstract: Techniques for managing assignment and reassignment of short codes are described herein. One or more computing devices may assign a short code to a first messaging campaign for a first time period. After expiration of the first time period, the one or more computing devices may then reassign the short code to a second messaging campaign for a second time period.