eSIM Profile Remote Deployment and Automatic Switching Systems, Methods, Devices, and Storage Media

Abstract

The application discloses an eSIM Profile remote delivery and automatic switching system, comprising: a terminal device, used for pre-setting a seed Profile, establishing a communication session with a cloud eSIM management platform through the seed Profile, reporting location data, network state and current Profile information, and completing target Profile receiving, installation, activation and failure fallback; the cloud eSIM management platform is used for obtaining relevant call and charging characteristic data and judging whether the switching condition is met, and when the switching condition is met, the target Profile remote delivery is applied; the operator interface is used for providing relevant call and charging characteristic data to the cloud eSIM management platform, and remotely delivering the Profile; the data layer is used for storing terminal device historical performance data, and analyzing operator cost and coverage data. The application also discloses an eSIM Profile remote delivery and automatic switching method, an electronic device and a computer readable storage medium. The application improves switching accuracy and automation level, and reduces communication cost.

Description

Technical Field

[0001] This invention belongs to the field of Internet of Things (IoT) technology, specifically an eSIM Profile remote distribution and automatic switching system, method, device, and storage medium. Background Technology

[0002] With the large-scale deployment of connected vehicles, cross-border logistics, industrial IoT, and shared terminals, an increasing number of terminal devices need to move continuously between multiple operators, multiple provinces, and even multiple countries / regions. Traditional single-operator profile (a set of operator network access configurations, typically including authentication parameters, network policies, access control information, and related operational data) solutions are prone to the following problems when operating across regions: 1. Insufficient network coverage currently leads to dropped connections, increased latency, or unstable services.

[0003] 2. Current operator tariffs are not favorable, leading to increased communication costs.

[0004] 3. Although the current profile can connect to the internet, it is not the optimal access configuration for the target area.

[0005] eSIM (embedded SIM) technology enables terminals to download, install, and activate multiple operator profiles, providing a foundation for dynamically adjusting network access configurations. However, simply having eSIM capabilities cannot solve practical problems such as "when to switch, which profile to switch to, how to ensure uninterrupted network access after a failed switch, and whether the switch result is truly better."

[0006] Current eSIM Profile management primarily employs the following models: 1. Static rule scheme: Pre-bind a certain operator profile according to country, province or administrative region, and perform fixed handover when the terminal arrives in the corresponding region.

[0007] 2. Location-based single-factor scheme: The scheme determines that the terminal has entered a certain area based solely on the location information or base station affiliation information, thereby triggering profile switching.

[0008] 3. Single-factor pricing plan: The decision to switch operator profiles is based solely on the tariff schedule, roaming policy, or package rules.

[0009] 4. Terminal local passive solution: The terminal attempts to reconnect or switch when the current network is unavailable, but it lacks the ability to orchestrate unified cloud policies and optimize regional global networks.

[0010] While the above solutions can achieve profile switching in some scenarios, they typically suffer from problems such as insufficient decision-making dimensions, lack of verification of switching results, lack of rollback handling for failures, and inability to self-optimize over the long term.

[0011] From a technical perspective, existing technologies have the following significant drawbacks: 1. Single decision-making basis: Using only one of the following factors, such as location, cost, or a single network metric, as the basis for switching can easily lead to erroneous switching.

[0012] 2. Insufficient automation: It still relies on manual configuration, manual review, or simplified logic on the terminal itself, which makes it difficult to support the large-scale management of a massive number of terminals.

[0013] 3. Lack of a closed-loop result: Whether the switch actually improves stability or reduces costs is often lacking in existing solutions due to a lack of verification and strategy feedback.

[0014] 4. Lack of failure protection: There is no standardized fallback path after a handover failure, which may cause the terminal to be temporarily disconnected from the network or even unavailable for a long time.

[0015] 5. Easy to switch frequently: It is easy to switch back and forth between multiple profiles in scenarios such as fence edges, high-speed movement, or network fluctuations.

[0016] Therefore, to address the above issues, a system, method, device, and storage medium for remote eSIM profile distribution and automatic switching are provided. Summary of the Invention

[0017] To address the aforementioned problems in the prior art, this invention provides a system, method, device, and storage medium for remote eSIM profile distribution and automatic handover, thereby improving handover accuracy and automation while reducing communication costs.

[0018] The technical solution to achieve the above objectives is: One of the present inventions provides a remote eSIM profile delivery and automatic handover system, comprising: The terminal device is used to pre-configure a seed profile, establish a communication session with the cloud eSIM management platform through the seed profile, report location data, network status and current profile information, and complete the reception, installation, activation and failure rollback of the target profile. The cloud-based eSIM management platform is used to obtain relevant call detail records and billing characteristic data and determine whether the handover conditions are met. When the handover conditions are met, it requests the remote issuance of the target profile. The operator interface is used to provide relevant call detail records and billing characteristic data to the cloud-based eSIM management platform and to remotely distribute profiles; The data layer is used to store historical performance data of terminal devices, analyze operator cost and coverage data, and provide real-time decision support to the cloud-based eSIM management platform.

[0019] Preferably, the terminal device includes: an eUICC unit, a local profile execution unit, a location acquisition unit, and a network status acquisition unit; The eUICC unit is used to store and switch profiles; The local profile execution unit is used to verify, install, and activate the target profile. The location acquisition unit is used to acquire location-related data, specifically including latitude and longitude, geofence, trajectory, dwell time, and direction of movement. The network status acquisition unit is used to monitor terminal status data, including current profile, signal strength, latency, packet loss rate, throughput, service type, and battery level.

[0020] Preferably, the cloud-based eSIM management platform includes: a device management service unit, a policy engine unit, a task orchestration service unit, and an audit trail service unit; The device management service unit is used for terminal registration and status management, and connects to terminal devices and the data layer. The strategy engine unit is used to generate handover decisions by integrating location, operator call detail records and terminal status data, and connects to the data layer and operator interface. The task orchestration service unit is used to schedule the Profile distribution process and connects with terminal devices and operator interfaces. The audit trail service unit is used to record switch operation logs and connects to the data layer.

[0021] Preferably, the operator interfaces include: the operator profile interface and the operator CDR / billing interface; The operator profile interface is used to remotely send profiles to the cloud-based eSIM management platform. The operator's CDR / billing interface is used to provide call detail records and tariff data to the cloud-based eSIM management platform, specifically including CDR call detail records, billing data, roaming costs, historical stability, and regional coverage performance.

[0022] Preferably, the data layer includes: a device profile library, a location trajectory library, a call detail record feature library, and a policy rule library; The device profile library is used to store long-term performance characteristics and historical behavior data of terminal devices, and is connected to the policy engine unit. The location trajectory library is used to store location-related data of terminal devices and is connected to the policy engine unit; The call detail record (CDR) feature library is used to store tariff and service quality analysis data provided by operators and is connected to the policy engine unit. The strategy rule base is used to store the constraints and business logic of switching decisions. It is connected to the strategy engine unit. The strategy constraint data includes minimum hold time, switching window, switching frequency limit, fallback threshold, and boundary suppression rules.

[0023] A second method of the present invention for remotely issuing eSIM profiles and automatically switching systems includes: Step S1: The terminal device establishes an initial connection with the cloud eSIM management platform through the preset seed profile, and completes device registration and authentication; Step S2: The terminal device periodically collects and reports its location, network status, and current profile information to the cloud-based eSIM management platform; Step S3: The cloud-based eSIM management platform obtains operator CDR call detail records and tariff data through the operator interface, and integrates terminal-reported data and policy constraint data in the policy rule base to generate candidate profile scores and sort them to determine whether the handover conditions are met. Step S4: If the target profile score meets the switching conditions, the cloud eSIM management platform generates a distribution task and distributes the target profile to the terminal device through the operator interface. Step S5: After receiving the target Profile, the terminal device performs integrity verification, security authentication and installation activation. If successful, the result is returned; otherwise, if it fails, times out or has a network error, it reverts to the original Profile. In step S6, the cloud-based eSIM management platform updates the device profile database and policy rule database parameters based on the returned results, and then proceeds to the next round of monitoring.

[0024] Preferably, in step S3, the switching conditions include: The target profile score is higher than the current profile score by a preset threshold; Currently in a time window where switching is allowed or a business idle window; The current profile meets the minimum retention time requirement; The terminal device has remained in the target area for the preset duration; The maximum number of switching attempts was not exceeded within the preset time window.

[0025] Preferably, in step S6, the threshold, fallback strategy, and anti-shake rules are further adjusted based on the updated device profile library and strategy rule library parameters to form a closed-loop optimization process.

[0026] The third invention provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of remotely issuing and automatically switching eSIM profiles.

[0027] The fourth invention provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of a method for remotely issuing and automatically switching eSIM Profiles.

[0028] Compared with the prior art, the beneficial effects of the present invention are: 1) This invention no longer relies solely on location or tariff, but makes decisions by comprehensively considering location, CDR call detail records, and real-time network status, thereby improving handover accuracy; 2) This invention uses cloud-based unified orchestration, remote distribution, and switching of tasks, reducing manual intervention and improving automation levels; 3) This invention combines historical stability and a failure rollback mechanism to reduce the risk of network disconnection during handover and enhance network stability; 4) This invention allows for the selection of operator profiles with better tariffs and coverage in different regions, thereby reducing communication costs; 5) This invention further adjusts thresholds, fallback strategies, and anti-shake rules by continuously updating the device profile library and strategy rule library parameters, forming a continuous optimization capability and improving the handover success rate. Attached Figure Description

[0029] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used in conjunction with embodiments of the invention to explain the invention and do not constitute a limitation thereof. In the drawings: Figure 1 This is a block diagram of an eSIM Profile remote issuance and automatic switching system according to the present invention; Figure 2 This is a flowchart of a method for remotely issuing and automatically switching eSIM profiles according to the present invention; Figure 3 This is another flowchart of a method for remotely issuing and automatically switching eSIM profiles according to the present invention; Figure 4 This is a schematic diagram of the timing interaction between the terminal device, the cloud eSIM management platform, and the operator interface in this invention; Figure 5 This is a schematic diagram illustrating the state changes of the terminal device of the present invention throughout the entire switching process. Detailed Implementation

[0030] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0031] like Figure 1 , 4 As shown, an eSIM Profile remote distribution and automatic switching system includes: a terminal device 1, a cloud-based eSIM management platform 2, an operator interface 3, and a data layer 4.

[0032] Terminal device 1 is used to pre-configure a seed profile, establish a communication session with the cloud eSIM management platform 2 through the seed profile, report location data, network status and current profile information, and complete the reception, installation, activation and failure rollback of the target profile.

[0033] like Figure 1 As shown, terminal device 1 includes: eUICC unit 11, local profile execution unit 12, location acquisition unit 13 and network status acquisition unit 14; eUICC unit 11 is used to store and switch profiles; The local profile execution unit 12 is used to verify, install, and activate the target profile; Location acquisition unit 13 is used to acquire location data, specifically including latitude and longitude, geofence, trajectory, dwell time, and direction of movement. The network status acquisition unit 14 is used to monitor terminal status data, specifically including current profile, signal strength, latency, packet loss rate, throughput, service type, and battery level.

[0034] The cloud-based eSIM management platform 2 is used to obtain relevant call detail records and billing characteristic data and determine whether the handover conditions are met. When the handover conditions are met, it requests the remote issuance of the target profile.

[0035] like Figure 1 As shown, the cloud-based eSIM management platform 2 includes: a device management service unit 21, a policy engine unit 22, a task orchestration service unit 23, and an audit trail service unit 24; Device management service unit 21 is used for terminal registration and status management, and is connected to terminal device 1 and data layer 4; The strategy engine unit 22 is used to generate handover decisions by integrating location, operator call detail records and terminal status data, and is connected to the data layer 4 and the operator interface 3. Task orchestration service unit 23 is used to schedule the Profile distribution process and is connected to terminal device 1 and operator interface 3. Audit trail service unit 24 is used to record switch operation logs and is connected to data layer 4.

[0036] Operator interface 3 is used to provide relevant call detail records and billing feature data to the cloud eSIM management platform 2, and remotely send profiles.

[0037] like Figure 1 As shown, the operator interface 3 includes: operator profile interface 31 and operator CDR / billing interface 32; Operator Profile Interface 31 is used to remotely send Profiles to the cloud-based eSIM management platform; The operator's CDR / billing interface 32 is used to provide call detail records and tariff data to the cloud-based eSIM management platform, specifically including CDR call detail records, billing data, roaming costs, historical stability, and regional coverage performance.

[0038] Data layer 4 is used to store historical performance data of terminal devices, analyze operator cost and coverage data, and provide real-time decision support to the cloud eSIM management platform 2.

[0039] like Figure 1 As shown, data layer 4 includes: device profile library 41, location trajectory library 42, call detail record feature library 43, and policy rule library 44; Device profile library 41 is used to store the long-term performance characteristics and historical behavior data of terminal device 1, and is connected to the policy engine unit 22; Location trajectory library 42 is used to store location data of terminal device 1 and is connected to strategy engine unit 22; Call detail record feature library 43 is used to store tariff and service quality analysis data provided by operators and is connected to policy engine unit 22; The strategy rule base 44 is used to store the constraints and business logic of the switching decision and is connected to the strategy engine unit 22. The strategy constraint data includes minimum hold time, switching window, switching frequency limit, fallback threshold, and boundary suppression rules.

[0040] like Figure 2-5 As shown, a method for remotely issuing eSIM profiles and automatically switching systems includes: Step S1: Terminal device 1 establishes an initial connection with cloud eSIM management platform 2 through a pre-set seed Profile, and completes device registration and authentication.

[0041] Step S2: Terminal device 1 periodically collects and reports location, network status and current profile information to cloud eSIM management platform 2.

[0042] In step S3, the cloud-based eSIM management platform 2 obtains operator CDR call detail records and tariff data through operator interface 3, and integrates terminal-reported data and policy constraint data in the policy rule base to generate candidate profile scores and sort them to determine whether the handover conditions are met.

[0043] In this embodiment, the switching conditions include: The target profile score is higher than the current profile score by a preset threshold; Currently in a time window where switching is allowed or a business idle window; The current profile meets the minimum retention time requirement; The terminal device has remained in the target area for the preset duration; The maximum number of switching attempts was not exceeded within the preset time window.

[0044] In this embodiment, location data includes: latitude and longitude, geofence, trajectory, dwell time, and direction of movement; terminal status data includes: current profile, signal strength, latency, packet loss rate, throughput, service type, and battery level; call detail records (CDRs) and tariff data include: CDRs, billing data, roaming costs, historical stability, and regional coverage performance; and policy constraint data includes: minimum hold time, handover window, handover frequency limit, fallback threshold, and boundary suppression rules. The above data undergoes data standardization, time alignment, and feature extraction to generate candidate profile scores and rank them.

[0045] Step S4: If the target profile score meets the switching conditions, the cloud eSIM management platform 2 generates a task to send the target profile to the terminal device 1 through the operator interface 3.

[0046] Step S5: After receiving the target profile, terminal device 1 performs integrity verification, security authentication, and installation activation. If successful, it returns the result; otherwise, if it fails, times out, or experiences a network error, it reverts to the original profile. The specific process is as follows: Figure 5 As shown.

[0047] In step S6, the cloud-based eSIM management platform 2 updates the parameters of the device profile library 41 and the policy rule library 44 based on the feedback results, and then proceeds to the next round of monitoring.

[0048] Specifically, regarding the execution result of the switching task, if the execution is successful, metrics such as latency, packet loss, cost, and online rate under the new profile are collected and written into the successful sample library; if the execution fails, reasons for failure such as activation failure, timeout, or network deterioration are collected and written into the failure sample library; the cloud eSIM management platform 2 updates the regional coverage profile and scoring weight based on the successful and failed samples, and further adjusts the threshold, fallback strategy, and anti-shake rules to generate a better decision for the next round.

[0049] An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of a method for remotely issuing and automatically switching eSIM profiles.

[0050] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of a method for remotely issuing and automatically switching eSIM profiles.

[0051] Finally, it should be noted that the above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A system for remotely issuing and automatically switching eSIM profiles, characterized in that, include: The terminal device is used to pre-configure a seed profile, establish a communication session with the cloud eSIM management platform through the seed profile, report location data, network status and current profile information, and complete the reception, installation, activation and failure rollback of the target profile. The cloud-based eSIM management platform is used to obtain relevant call detail records and billing characteristic data and determine whether the handover conditions are met. When the handover conditions are met, it requests the remote issuance of the target profile. The operator interface is used to provide relevant call detail records and billing characteristic data to the cloud-based eSIM management platform and to remotely distribute profiles; The data layer is used to store historical performance data of terminal devices, analyze operator cost and coverage data, and provide real-time decision support to the cloud-based eSIM management platform.

2. The eSIM Profile remote issuance and automatic switching system according to claim 1, characterized in that, The terminal device includes: an eUICC unit, a local profile execution unit, a location acquisition unit, and a network status acquisition unit; The eUICC unit is used to store and switch profiles; The local profile execution unit is used to verify, install, and activate the target profile. The location acquisition unit is used to acquire location-related data, specifically including latitude and longitude, geofence, trajectory, dwell time, and direction of movement. The network status acquisition unit is used to monitor terminal status data, including current profile, signal strength, latency, packet loss rate, throughput, service type, and battery level.

3. The eSIM Profile remote issuance and automatic switching system according to claim 1, characterized in that, The cloud-based eSIM management platform includes: a device management service unit, a policy engine unit, a task orchestration service unit, and an audit trail service unit; The device management service unit is used for terminal registration and status management, and connects to terminal devices and the data layer. The strategy engine unit is used to generate handover decisions by integrating location, operator call detail records and terminal status data, and connects to the data layer and operator interface. The task orchestration service unit is used to schedule the Profile distribution process and connects with terminal devices and operator interfaces. The audit trail service unit is used to record switch operation logs and connects to the data layer.

4. The eSIM Profile remote issuance and automatic switching system according to claim 3, characterized in that, The carrier interfaces include: the carrier profile interface and the carrier CDR / billing interface; The operator profile interface is used to remotely send profiles to the cloud-based eSIM management platform. The operator's CDR / billing interface is used to provide call detail records and tariff data to the cloud-based eSIM management platform, specifically including CDR call detail records, billing data, roaming costs, historical stability, and regional coverage performance.

5. The eSIM Profile remote issuance and automatic switching system according to claim 4, characterized in that, The data layer includes: device profile library, location trajectory library, call detail record feature library, and policy rule library; The device profile library is used to store long-term performance characteristics and historical behavior data of terminal devices, and is connected to the policy engine unit. The location trajectory library is used to store location-related data of terminal devices and is connected to the policy engine unit; The call detail record (CDR) feature library is used to store tariff and service quality analysis data provided by operators and is connected to the policy engine unit. The strategy rule base is used to store the constraints and business logic of switching decisions. It is connected to the strategy engine unit. The strategy constraint data includes minimum hold time, switching window, switching frequency limit, fallback threshold, and boundary suppression rules.

6. A method for remotely issuing and automatically switching eSIM profiles according to claims 1-5, characterized in that, include: Step S1: The terminal device establishes an initial connection with the cloud eSIM management platform through the preset seed profile, and completes device registration and authentication; Step S2: The terminal device periodically collects and reports its location, network status, and current profile information to the cloud-based eSIM management platform; Step S3: The cloud-based eSIM management platform obtains operator CDR call detail records and tariff data through the operator interface, and integrates terminal-reported data and policy constraint data in the policy rule base to generate candidate profile scores and sort them to determine whether the handover conditions are met. Step S4: If the target profile score meets the switching conditions, the cloud eSIM management platform generates a distribution task and distributes the target profile to the terminal device through the operator interface. Step S5: After receiving the target Profile, the terminal device performs integrity verification, security authentication and installation activation. If successful, the result is returned; otherwise, if it fails, times out or has a network error, it reverts to the original Profile. In step S6, the cloud-based eSIM management platform updates the device profile database and policy rule database parameters based on the returned results, and then proceeds to the next round of monitoring.

7. The method for remotely issuing and automatically switching eSIM profiles according to claim 6, characterized in that, In step S3, the switching conditions include: The target profile score is higher than the current profile score by a preset threshold; Currently in a time window where switching is allowed or a business idle window; The current profile meets the minimum retention time requirement; The terminal device has remained in the target area for the preset duration; The maximum number of switching attempts was not exceeded within the preset time window.

8. The method for remotely issuing and automatically switching eSIM profiles according to claim 6, characterized in that, In step S6, the threshold, fallback strategy, and anti-shake rules are further adjusted based on the updated device profile library and strategy rule library parameters to form a closed-loop optimization process.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes a computer program, it implements the steps of the eSIM Profile remote delivery and automatic handover method as described in claim 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the eSIM Profile remote delivery and automatic switching method as described in claim 6.

Images