# US 2026/0230794 A1 · Embedded universal integrated circuit card, corresponding managing method and system architecture

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0230794 A1
- Document ID: US20260230794A1
- Status: Published application
- Kind: A1
- Application number: 19/456,916
- Filed: 2026-01-22
- Published: 2026-08-06
- Earliest claimed: 2025-01-24
- Assignees: STMicroelectronics International N.V.
- Applicants: STMicroelectronics International N.V.
- Inventors: Luigi Di Maggio
- Web page: https://patentgrep.com/patent/US20260230794A1

## CPC

- H04W 8/183: {Processing at user equipment or user record carrier}
- H04W 8/205: {Transfer to or from user equipment or user record carrier}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

An embedded Universal Integrated Circuit Card (eUICC) for an Internet of Things (IoT) device, configured to enable as active profile a fallback profile in place of a previously-enabled profile upon detection of a loss of connectivity with a communication network of the IoT device, wherein the eUICC comprises a stored application and set of Application Programming Interfaces (APIs) comprising a subset of APIs configured to perform profile managing operation comprising at least operations of enabling (FPD) and disabling (FPA) the fallback profile, the application configured to access the set of APIs of the eUICC, in order to perform the operations (FPD, FPA) of the subset of APIs.

## Claims

### Claim 1

An embedded Universal Integrated Circuit Card (eUICC) for an Internet of Things (IoT) device, the eUICC comprising:
a stored set of application programming interfaces (APIs) comprising a subset of APIs configured to perform profile managing operations comprising at least an enabling a fallback profile operation and a disabling the fallback profile operation; and
a stored application configured to access the stored set of APIs of the eUICC, in order to perform the enabling and disabling the fallback profile operations of the subset of APIs;
wherein the eUICC is configured to enable as an active profile a fallback profile in place of a previously-enabled profile upon detection of a loss of connectivity with a communication network of the IoT device.

### Claim 2 (depends on 1)

The eUICC of claim 1, wherein the stored set of APIs comprises at least a first API configured to enable the fallback profile, a second API configured to disable the fallback profile, and a third API configured to check whether a currently-enabled profile for operation corresponds to the fallback profile.

### Claim 3 (depends on 2)

The eUICC of claim 2, wherein the stored application is configured to check by the third API the currently-enabled profile and take an action to disable the fallback profile by the second API coming back to the previously-enabled profile, or enable the fallback profile by the first API depending on the currently-enabled profile corresponding to the fallback profile or the previously-enabled profile.

### Claim 4 (depends on 2)

The eUICC of claim 2, wherein the stored application is configured to, following an enabling of the fallback profile by a remote manager module upon the detection of the loss of connectivity, check that the currently-enabled profile corresponds to the fallback profile, and switch back from the fallback profile, enabling the previously-enabled profile and disabling by the second API the fallback profile.

### Claim 5 (depends on 4)

The eUICC of claim 4, wherein the stored application is configured to ignore action to enable and/or disable the fallback profile by the remote manager module.

### Claim 6 (depends on 4)

The eUICC of claim 4, wherein the remote manager module is a first IoT Profile Assistant in the IoT device or a second IoT Profile Assistant in the eUICC.

### Claim 7 (depends on 2)

The eUICC of claim 2, wherein the stored application is configured to, upon the detection of the loss of connectivity by the stored application, enable, through the first API, the fallback profile.

### Claim 8 (depends on 1)

The eUICC of claim 1, wherein the subset of APIs is configured to operate through native modules in an operating system of the eUICC that manage profiles installed on the eUICC.

### Claim 9

A method for managing an embedded Universal Integrated Circuit Card (eUICC) for an Internet of Things (IoT) device, the method comprising:
enabling a fallback profile in place of a previously-enabled profile upon detection of a loss of connectivity with a communication network of the IoT device;
managing, by an application stored in the eUICC, at least an enabling a fallback profile operation and a disabling the fallback profile operation; and
accessing, by the stored application, a set of stored application programming interfaces (APIs) of the eUICC comprising a subset of APIs configured to perform profile managing operations comprising at least the enabling and disabling the fallback profile operations.

### Claim 10 (depends on 9)

The method according to claim 9, wherein the stored set of APIs comprises at least a first API configured to enable the fallback profile, a second API configured to disable the fallback profile, and a third API configured to check whether a currently-enabled profile for operation corresponds to the fallback profile.

### Claim 11 (depends on 10)

The method according to claim 10, further comprising:
checking by the third API the currently-enabled profile and take an action to disable the fallback profile by the second API coming back to the previously-enabled profile, or enable the fallback Profile by the first API depending on the currently-enabled profile corresponding to the fallback profile or the previously-enabled profile.

### Claim 12 (depends on 10)

The method according to claim 10, further comprising:
following an enabling of the fallback profile by a remote manager module upon the detection of the loss of connectivity, checking by the stored application that the currently-enabled profile corresponds to the fallback profile, and switching back from the fallback profile, enabling the previously-enabled profile and disabling by the second API the fallback profile.

### Claim 13 (depends on 12)

The method according to claim 12, further comprising:
ignoring, by the stored application, action to enable and/or disable the fallback profile by the remote manager module.

### Claim 14 (depends on 12)

The method of claim 12, wherein the remote manager module is a first IoT Profile Assistant in the IoT device or a second IoT Profile Assistant in the eUICC.

### Claim 15 (depends on 10)

The method according to claim 10, further comprising:
upon detection of the loss of connectivity by the stored application, enabling by the stored application, through the first API, the fallback profile.

### Claim 16 (depends on 9)

The method according to claim 9, wherein the eUICC for the IoT device is operated according to a GSMA SGP.32 standard.

### Claim 17

An Internet of Things (IoT) device comprising:
an embedded Universal Integrated Circuit Card (eUICC) comprising:
a stored set of application programming interfaces (APIs) comprising a subset of APIs configured to perform profile managing operations comprising at least an enabling a fallback profile operation and a disabling the fallback profile operation; and
a stored application configured to access the stored set of APIs of the eUICC, in order to perform the enabling and disabling the fallback profile operations of the subset of APIs;
wherein the eUICC is configured to enable as an active profile a fallback profile in place of a previously-enabled profile upon detection of a loss of connectivity with a communication network of the IoT device; and
an IoT profile assistant (IPA) block configured to serve as a proxy between the eUICC and an embedded subscriber identity module IoT remote manager.

### Claim 18 (depends on 17)

The IoT device according to claim 17, wherein the eUICC further comprises:
an issuer security domain–root block configured to interface with the IPA block through a first IPA—eUICC interface for performing profile download and installation operations and handling profile discovery, and a second IPA—eUICC interface for performing generic eUICC package download and execution; and
an issuer security domain–profile block comprising a mobile network operator security domain block configured to interface with a mobile network operator.

### Claim 19 (depends on 18)

The IoT device of claim 18, wherein the stored set of APIs comprises at least a first API configured to enable the fallback profile, a second API configured to disable the fallback profile, and a third API configured to check whether a currently-enabled profile for operation corresponds to the fallback profile.

### Claim 20 (depends on 19)

The IoT device of claim 19, wherein the stored application is configured to check by the third API the currently-enabled profile and take an action to disable the fallback profile by the second API coming back to the previously-enabled profile, or enable the fallback profile by the first API depending on the currently-enabled profile corresponding to the fallback profile or the previously-enabled profile.
