T-mobile Usa, Inc.

Cristian Asandului

Phani Ramisetty

Mathew George

Kyeong Hun An

Ryan King

Tanmay Roy

Kevin Lau

Warren J McNeel

Yasmin Karimli

Shelby Seward

Thomas P Lucht

Ahmad O Alkabra

Hongliang Zhang

Senthil Kumar Mulluppadi Velusamy

Sergey Slovetskiy

Poornima Magadevan

Jeffrey Song

Jie Hui

Christopher Harvey Joul

Jean-Luc Rene Bouthemy

Nandita Sharma

Arturo Silis

Srinivas Meka

Kimberly Bylund

Sandesh Shetty

Warren J Mcneel

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.

Secure and transparent transport of application level protocols to non-IP data delivery communication channels

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.

Rsp platform selection for providing esim profiles to user devices

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.

Secure updating of telecommunication terminal configuration

A user device described herein suggests a change to a quality setting associated with the consumption of content from one or more content providers. The change is suggested based both on a user's data plan and on a service quality of content received by the user device. This user-selected quality setting is then provided to the telecommunication network, which reduces network resources available for transmission of the content based on the quality setting. Such reduced network resources cause the content providers to provide content at a service quality no greater than the quality setting. Also, the user may be presented with or defaulted to selecting an option for a program offering consumption of the video content free of charge when provided to the user at a limited service quality. When the user participates, consumption of video content is then conditionally excluded from a consumption metric of the data plan.

Data-plan-based quality setting suggestions and use thereof to manage content provider services

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.

Over the air provisioning of embedded subscriber identification module devices

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.

RSP platform selection for ESIM profile procurement

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.

Systems and methods for distributing Internet-of-Things messages

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.

Meta RSP interface platform for eSIM profile distribution

A request from a mobile operator network (MNO) is received at a Subscription Manager Secure Routing (SM-SR) associated with the MNO. The request is for deleting an embedded Subscriber Identity Module (eSIM) profile from an embedded Universal Integrated Circuit Card (eUICC) of a machine-to-machine (M2M) device. The eSIM profile is provided by a Subscription Manager Data Preparation (SM-DP) of a third-party partner of the MNO. A command is sent from the SM-SR to an application on the M2M device to delete the eSIM profile from the eUICC of the M2M device. An indication is then received from the application by the SM-SR indicating that the eSIM profile has been deleted. Accordingly, the SM-SR associated with the MNO may send a notification to the SM-DP of the third-party partner indicating that the eSIM profile has been deleted from the eUICC of the M2M device.

M2M SM-SR to SM-DP notification

A mobile network operator (MNO) may receive a request to provide an embedded Subscriber Identity Module (eSIM) profile to an embedded Universal Integrated Circuit Card (eUICC) of a user device. The user device is configured to receive telecommunication services from the MNO. Thus, if it is determined that a particular remote SIM provisioning (RSP) platform of a plurality of RSP platforms is able to provide the eSIM profile, the particular RSP platform is directed to provision the eUICC of the user device with the eSIM profile. However, if a condition that affects an ability of the particular RSP platform to provide the eSIM profile is detected, an alternative RSP platform may be directed to provide the eUICC of the user device with the eSIM profile.

Intelligent SIM profile procurement

A QoE (quality of experience) system utilizes QoS (quality of service) of a mobile network and specification of user device connected for providing a personalized metric (QoE) that represents an expected level of user experience at a geographic location. The personalized metric can be calculated based on the QoS of the mobile network at the geographic location and hardware/software characteristics of the user device to implement specific services at the user device using the mobile network. While QoS of the mobile network merely represents quality of network communication regardless of device characteristics, QoE can represent actual expectation of user experience at a user device using the mobile network.

Visualization of personalized quality of experience regarding mobile network

In some implementations, a telecommunications network can include a core network device communicatively connectable with user equipment (UE). The core network device can receive, via a network interface, an indication of a change to a user preference associated with the user device. The core network device can transmit a notification message including a pseudonymous identifier, the notification message based at least in part on the indication of the change. The UE can transmit, via a network interface, information of an account associated with the UE to a content provider. The information can include the pseudonymous identifier. The UE can then render content received from the content provider. The content provider can receive, via a network, the pseudonymous identifier and a request for content. The content provider can determine a quality setting associated with the pseudonymous identifier, and provide the content based at least in part on the quality setting.

Growing community of inventors

Snoqualmie, WA, United States of America

Cristian Asandului