Hybrid protocol gateway for unified management of mixed fleets
An IoT management system may be configured to provide unified remote SIM provisioning across mixed Internet-of-Things (IoT) device fleets while simultaneously ensuring resilient profile delivery over satellite links. A hybrid protocol gateway interfaces with both modern SGP.32 (Secure Global Platform 3.2) and legacy SGP.02 (Secure Global Platform 2.0) devices, translating management commands and performing on-the-fly profile format transcoding to accommodate heterogeneous endpoints. A delay-tolerant networking (DTN) gateway may be configured to ensure reliable profile delivery over intermittent satellite connections by fragmenting profile payloads into bundles, scheduling transmissions based on satellite visibility windows, and supporting multi-pass delivery for enhanced reliability.
1 . A method of managing a SIM profile on a legacy IoT device using a hybrid protocol gateway, the method comprising, by the hybrid protocol gateway:
receiving a remote provisioning command over an IP control interface from a remote provisioning module, the command specifying a target identifier associated with a secure chip of a device;
determining a device type and current state of the device;
mapping the command to a corresponding legacy command;
generating legacy code compatible with an eSIM card of the device;
generating an SMS message including the legacy code; and
transmitting the SMS message to the device, wherein the device is configured to execute the legacy code to implement the remote provisioning command.
2 . The method of claim 1 , wherein the remote provisioning command complies with SGP.32 standard.
3 . The method of claim 1 , wherein the generated legacy code complies with SGP.02 standard.
4 . The method of claim 1 , wherein the legacy code comprises one or more application protocol data unit (APDU) commands.
5 . The method of claim 1 , further comprising:
encrypting the legacy code prior to generating the SMS message.
6 . The method of claim 1 , wherein said transmitting is over a cellular network.
7 . The method of claim 1 , wherein the IP control interface comprises ESipa carried over HTTP or CoAP.
8 . The method of claim 1 , wherein the device type and the current state are determined based on an internal state database.
9 . The method of claim 1 , wherein the command comprises a device-centric disable-profile operation and the legacy code comprises an ES5 disable-profile operation.
10 . The method of claim 1 , wherein the command comprises a device-centric enable-profile operation and the legacy code implements an ES5 enable-profile operation.
11 . The method of claim 1 , wherein the command comprises a device-centric delete-profile operation and the legacy code implements an ES5 delete-profile operation.
12 . The method of claim 1 , wherein the command comprises a device-centric trigger-profile-download operation and the legacy code implements an ES5 download-profile operation including INSTALL/LOAD and STORE DATA messages.
13 . The method of claim 1 , wherein the command comprises a device-centric query-profile-state operation and the legacy code implements an ES5 profile-information operation including SELECT and GET STATUS messages directed to a profile security domain.
14 . The method of claim 1 , wherein the command comprises a device-centric list-profiles operation and the legacy code implements an ES5 enumeration operation to identify available profile security domains on the secure chip.
15 . The method of claim 1 , wherein the command comprises a device-centric set-active-profile operation and the legacy code implements an ES5 operation that enables a target profile security domain and disables a currently active profile according to a policy.