Abstract: Techniques are described herein for transparently connecting to the same light weight machine-to-machine (LwM2M) server using both Internet Protocol (IP)-based and non-IP data delivery (NIDD)-based connectivity using all LwM2M functionality and security modes. The techniques include establishing a connection over a NIDD socket to communicate with an application server using NIDD binding to deliver a datagram destined for a target server. The datagram may be encapsulated in a serialized envelope including an application-level protocol metadata, wherein the metadata representing information corresponding to the target server. The datagram is delivered to the target server over NIDD-based transport.

Abstract: Intelligent network access technology (NAT) control is described herein. An event associated with a mobile computing device can be detected. Responsive to the event being detected, a subscriber identity module (SIM) associated with the mobile computing device can access location information associated with a location of the mobile computing device. The SIM can access a configuration table storing NAT data provided by a network for controlling which NATs the mobile computing device is permitted to use to access the network. The SIM can determine, based at least in part on the NAT data and the location information, that a requested NAT of the mobile computing device is not a permissible NAT for the mobile computing device in the location and the SIM can cause the mobile computing device to connect to the network via an alternate NAT.

Abstract: A system for routing Internet-of-Things (IoT) device notifications, or a method therefore are described. For example, a system includes a processor; and computer-readable instructions that, when executed by the processor, cause the system to perform operations including receiving, from a notification customer, preferences for a selection of notifications associated with IoT devices; storing each notification of the notifications in one or more message queues, the message queues being associated with the preferences; and transmitting the selection of the notifications to the notification customer, wherein the selection of notifications comprises a subset of the notifications.

Abstract: Telecommunication services are received at a user device using an embedded subscriber identity module (eSIM) profile stored on the user device while the user device is located in a first geographical area. A list of preferred remote SIM provisioning (RSP) platforms that provide eSIM profiles specific to a partner MNO of the MNO in a second geographical area is also received from an eSIM management platform of an MNO; The user device is then determined to have moved to a second geographical area based on a geolocation of the user device. Subsequently, an additional eSIM profile specific to the partner MNO of the MNO is downloaded to the user device from an RSP platform of one or more RSP platforms included in the list of preferred RSP platforms.

Abstract: Techniques and architecture are provided for preventing narrow band (NB) SIMs from being used in a non-NB devices, e.g., high bandwidth devices such as, for example, smartphones, tablets, etc. In configurations, a user device is provisioned based upon a NB international mobile subscriber identity (IMSI), a NB-indicator and a type allocation code (TAC) combination. An IMSI, NB-indicator and TAC mismatch helps prevent NB-SIMs from being used in a non-NB device. In configurations, when a user device attempts to access or register with a wireless communication network via a narrow band network of the wireless communication network, the wireless communication network will verify the IMSI, the NB-indicator and the NB-TAC combination for the user device in order to allow the user device to access the narrow band network of the wireless communication network.

Abstract: Techniques are described herein for transparently connecting to the same light weight machine-to-machine (LwM2M) server using both Internet Protocol (IP)-based and non-IP data delivery (NIDD)-based connectivity using all LwM2M functionality and security modes. The techniques include establishing a connection over a NIDD socket to communicate with an application server using NIDD binding to deliver a datagram destined for a target server. The datagram may be encapsulated in a serialized envelope including an application-level protocol metadata, wherein the metadata representing information corresponding to the target server. The datagram is delivered to the target server over NIDD-based transport.

Abstract: Techniques are described herein for transparently connecting to the same light weight machine-to-machine (LwM2M) server using both Internet Protocol (IP)-based and non-IP data delivery (NIDD)-based connectivity using all LwM2M functionality and security modes. The techniques include establishing a connection over a NIDD socket to communicate with an application server using NIDD binding to deliver a datagram destined for a target server. The datagram may be encapsulated in a serialized envelope including an application-level protocol metadata, wherein the metadata representing information corresponding to the target server. The datagram is delivered to the target server over NIDD-based transport.

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 discussed herein are directed to handling the identity and authentication of server security certificates on SIMs, and establishing secure channels with cloud servers via a wireless communication network using the security certificates and Public Key Infrastructure (PKI) libraries on SIMs. A mechanism to manage the security certificates on SIMs using an Over-the-Air (OTA) platform of the wireless communication network and certificate authority network elements is provided. Multiple cloud systems and their cloud servers are supported by storing multiple cloud certificates on SIMs and enabling features of a dynamic selection of the appropriate server certificate by the OTA platform for secure communication. Accordingly, electronic devices may be used within the wireless communication network for exchanging data with multiple cloud servers without changing codes/software devices, SIMs, etc.

Abstract: Techniques for provisioning electronic devices that may not have a local provisioning agent (LPA), such as Internet of Things (IoT) devices, to a mobile network of a mobile network operator (MNO), are discussed herein. The IoT devices and/or the associated embedded subscriber identity module (eSIM) may have one or more device profile templates stored thereon, where individual ones of the device profile templates are associated with a particular MNO. A device provisioning system of an MNO may provision the IoT device in a machine-to-machine (M2M) manner over the air (OTA) by communicating, such as via a radio node, one or more configuration parameters to the IoT device. The IoT device may identify a device profile template associated with the MNO to which the IoT device is to be provisioned and configure that device profile template based at least in part on the configuration parameters received from the device provisioning system.

Abstract: The methods, systems, and computer readable media discussed herein are directed to enabling a fifth generation cellular-wireless access technology (5G) user equipment (UE) to receive 5G service using a fourth generation cellular-wireless access technology (4G) subscriber identity module (SIM). Upon powering on, the 5G UE may determine whether a mobile network operator (MNO) public key file exists in the 4G SIM. Upon determining that the MNO public key file exists in the 4G SIM, the 5G UE may retrieve a MNO public key value from the MNO public key file, read a subscription permanent identifier (SUPI) from the 4G SIM, generate a subscription concealed identifier (SUCI) based on the SUPI and the MNO public key value, send the SUCI to a 5G mobile network for registering the 5G UE, and begin receiving 5G services from the 5G mobile network.

Abstract: A 5G user equipment (UE) can register for 5G services with a telecommunication network in part using a Subscription Concealed Identifier (SUCI), an encrypted version of a subscriber identifier, so that the actual subscriber identifier is not exposed during network registration. Legacy SIMs originally deployed for 4G/LTE and other legacy wireless access technologies store an international mobile subscriber identity (IMSI), but do not store a network public key needed to generate a SUCI. However, a 5G UE can still use a legacy SIM to securely obtain 5G services by encrypting the IMSI from the legacy SIM using a network public key stored in the 5G UE's own memory to generate a SUCI, and then transmitting the generated SUCI to the telecommunication network during network registration. Accordingly, the IMSI on the legacy SIM is not exposed during network registration.

Abstract: Systems and methods discussed herein are directed to subscriber identity (SIM) cards that include multiple profiles. The SIM cards include logic, e.g., an application or an applet, configured to change profiles so that the correct profile is selected for use with the electronic device that includes such a SIM card within the appropriate wireless communication network. The ability to change profiles may be based on activity of the electronic device, e.g., events, within the wireless communication network.

Abstract: A system for routing Internet-of-Things (IoT) device notifications, or a method therefore are described. For example, a system includes a processor; and computer-readable instructions that, when executed by the processor, cause the system to perform operations including receiving, from a notification costumer, preferences for a selection of notifications associated with IoT devices; storing each notification of the notifications in one or more message queues, the message queues being associated with the preferences; and transmitting the selection of the notifications to the notification costumer, wherein the selection of notifications comprises a subset of the notifications.

Abstract: Telecommunication services are received at a user device using an embedded subscriber identity module (eSIM) profile stored on the user device while the user device is located in a first geographical area. A list of preferred remote SIM provisioning (RSP) platforms that provide eSIM profiles specific to a partner MNO of the MNO in a second geographical area is also received from an eSIM management platform of an MNO; The user device is then determined to have moved to a second geographical area based on a geolocation of the user device. Subsequently, an additional eSIM profile specific to the partner MNO of the MNO is downloaded to the user device from an RSP platform of one or more RSP platforms included in the list of preferred RSP platforms.

Abstract: Processes and systems for locking a NB-IoT device to a NB-IoT SIM before connecting the NB-IoT device to a cellular network are discussed herein. The NB-IoT device may include a status flag that determines whether the NB-IoT device requires a NB-IoT SIM to access NB-IoT-specific functions provided by a cellular network. In one example, a Group Identifier Level 1 (GID1) of the IoT SIM may be queried and compared against a reference value to determine whether the IoT SIM is an NB-IoT SIM, and if confirmed, the NB-IoT device may connect to a cellular network and access the NB-IoT-specific functions. In an example, an NB-IoT device associated with a status flag indicating that the device does not require an NB-IoT SIM may connect to a cellular network, but may not access NB-IoT-specific functions.

Abstract: An eSIM management platform may receive service feature information on multiple remote SIM provisioning (RSP) platforms that are designated by a mobile network operator (MNO) to distribute embedded subscriber identity module (eSIM) profiles for a partner MNO of the MNO. The eSIM management platform may evaluate multiple RSP platforms based on one or more service features of each RSP platform to select one or more RSP platforms of the multiple RSP platforms for population into a list of preferred RSP platforms for the geographical area. The eSIM management profile may send the list of preferred RSP platforms to a user device to configure the user device to use an eSIM profile provided by an RSP platform of the one or more RSP platforms. The user device may use the eSIM profile to obtain telecommunication services from the partner MNO while the user device is in a geographical area.

Abstract: Systems and/or methods for distributing Internet-of-Things (IoT) can include a Service Capability Server (SCS) for facilitating an exchange of messages between an IoT device and an Application Server (AS). The SCS may store a priority value associated with the IoT device in a priority value database. The system may determine that a network condition has experienced a first change (e.g., an outage occurs), and may store incoming messages in a message database. Upon determining that the network has experienced a second change (e.g., the outage ends), the SCS may send the message to the IoT in a sequence of transmissions based, at least in part, on the priority value. In some instances, the priority value may be determined based on a registration process, the message, and/or one or more device parameter(s) of the IoT device.

Abstract: Techniques for provisioning electronic devices that may not have a local provisioning agent (LPA), such as Internet of Things (IoT) devices, to a mobile network of a mobile network operator (MNO), are discussed herein. The IoT devices and/or the associated embedded subscriber identity module (eSIM) may have one or more device profile templates stored thereon, where individual ones of the device profile templates are associated with a particular MNO. A device provisioning system of an MNO may provision the IoT device in a machine-to-machine (M2M) manner over the air (OTA) by communicating, such as via a radio node, one or more configuration parameters to the IoT device. The IoT device may identify a device profile template associated with the MNO to which the IoT device is to be provisioned and configure that device profile template based at least in part on the configuration parameters received from the device provisioning system.

Abstract: A user device may receive a list of remote SIM provisioning (RSP) platforms that are designated by a mobile network operator (MNO) to distribute eSIM profiles of a partner MNO of the MNO, in which the partner MNO provides telecommunication services in a geographical area. The user device may obtain one or more service features of individual RSP platforms in the list of RSP platforms from a meta RSP interface (MRI) platform when the user device is in the geographical area. Subsequently, the user device may determine a number of service parameters that are met by the one or more service features of the individual RSP platforms. In response to identifying a single RSP platform as meeting a highest number of service parameters, the user device may request a download of an eSIM profile from the single RSP platform to access the telecommunication services of the partner MNO.