Embedded sim profile intelligent switching management system and method

Abstract

This invention discloses an embedded SIM profile intelligent handover management system and method, belonging to the field of communication technology. It includes: an event sensing module, a handover coordination module, a handover execution module, and a management module. The event sensing module identifies triggering events and constructs an event sensing queue. For the first pending triggering event, it determines the handover status, including cached state and ready state, through differentiated network sensing. The handover coordination module responds to the ready state, obtains a suggested execution time window, and constructs a coordination group. Through the handover scheduling of the coordination group, it constructs a handover execution command. The handover execution module receives the handover execution command to drive the terminal to activate the target profile. The management module stores the handover execution records reported by each terminal, configures the global parameters required for handover operation, and performs dynamic optimization, achieving a synergistic unity of terminal power consumption control, simplified signaling interaction, and improved network stability.

Description

Technical Field

[0001] This invention belongs to the field of communication technology and relates to an embedded SIM profile intelligent switching management system and method. Background Technology

[0002] A SIM card is a physical card based on an integrated circuit. It is physically inserted into a mobile terminal to assist the network in identifying the user. However, the pluggable physical SIM card has significant drawbacks, which not only cause great inconvenience to users, but also significantly increase the manpower cost for operators to replace it.

[0003] With technological advancements and the continuous development of communication technologies, embedded SIM (eSIM) has emerged as a new type of cardless solution, integrating the functions of a traditional SIM card directly into the device chip, eliminating the need for a separate physical card slot. This technology not only allows users to choose operator plans more flexibly and switch operators at any time without being restricted by network standards, but also saves on the manufacturing costs of physical SIM cards, while offering higher reliability than traditional SIM cards.

[0004] A patent application with publication number CN120434737A discloses an AI-based eSIM global operator dynamic OTA handover system, which includes an environmental data acquisition module that collects bandwidth, packet loss rate, network stability, and handover success rate on the device side to generate local network status data; a behavior and tariff modeling module that collects communication behavior and tariff information to generate user preference data; an AI strategy generation module that outputs OTA control commands based on graph neural networks and attention mechanisms; an OTA strategy synchronization module that issues and parses commands to generate execution parameter packets; and a dual-link handover execution module that completes handover and rollback configuration.

[0005] While existing technologies have enabled eSIM operators to achieve intelligent, low-latency, and highly reliable dynamic switching, there is still room for optimization in resource management during daily operation. Specifically, in order to maintain awareness of the optimal network, the terminal needs to periodically scan the surrounding network environment. This continuous scanning behavior will bring unnecessary signaling interaction and energy consumption burden. At the same time, traditional multi-network switching solutions often involve periodic attachment attempts when exploring alternative networks. In scenarios with a large number of concurrent devices, such indiscriminate attachment behavior may trigger signaling storms on the network side, leading to signaling congestion and affecting the overall stability of the network. Summary of the Invention

[0006] To address the shortcomings of existing technologies, the present invention aims to provide an embedded SIM profile intelligent handover management system and method. This system replaces periodic network scanning with a multi-level triggering mechanism, reduces redundant signaling and energy consumption, constructs a coordination group to achieve handover timing coordination, avoids signaling storms caused by indiscriminate attachment in concurrent scenarios, and solves existing resource management and network stability problems.

[0007] To achieve the above objectives, the present invention provides the following technical solution:

[0008] The embedded SIM profile intelligent handover management system includes: an event sensing module, a handover coordination module, a handover execution module, and a management module;

[0009] The event perception module is used to acquire the terminal's operating status data and network environment information in real time. It identifies triggering events through a multi-level triggering mechanism, sorts the triggering events according to their urgency, constructs an event perception queue, takes the first triggering event as the event to be processed, and performs switching status determination through differentiated network perception, including cached status and ready status.

[0010] The switching coordination module responds to the ready state, obtains the suggested execution time window, constructs a coordination group, allocates a switching execution timestamp to the current terminal through the switching scheduling of the coordination group, and matches the optimal target configuration file for the current terminal based on the terminal location and the scanning data of each terminal in the coordination group, and integrates the switching execution timestamp with the optimal target configuration file identifier to construct a switching execution instruction.

[0011] The switching execution module is used to receive switching execution instructions and drive the terminal to activate the target configuration file at a specified time according to the instructions;

[0012] The management module is used to store the handover execution records reported by each terminal. Through a global configuration mechanism, it configures the global parameters required for the handover operation and dynamically optimizes the global parameters by combining the stored handover execution records.

[0013] Specifically, the steps for identifying triggering events through a multi-level triggering mechanism include:

[0014] The runtime status data is denoised and standardized to generate a terminal dataset;

[0015] Based on global parameters, statistical analysis is used to initialize multi-level judgment thresholds for triggering events;

[0016] Read the location information in the terminal data set, calculate the displacement using Euclidean distance, and detect whether the area code has changed. Once a change in the area code is detected, calculate the duration of the area code change.

[0017] If the displacement is greater than the displacement threshold or the duration is greater than the duration threshold, it is determined to be a position-triggered event;

[0018] For signal triggering, read continuously. Calculate the signal attenuation rate based on the received parameters for each cycle;

[0019] If continuous If the received parameters for a sampling period are less than the threshold trigger threshold and the signal attenuation rate is greater than the attenuation threshold, then it is determined to be a signal trigger event.

[0020] For business triggers, read the business demand volume from the terminal dataset. If the business demand volume is greater than the business trigger threshold, it is determined to be a business trigger event.

[0021] Specifically, the steps for constructing an event-aware queue include:

[0022] Get the triggered events identified in the current sampling period, arrange them randomly and disordered, and generate an initial event queue;

[0023] For location-triggered events, calculate the location score and change score, and combine them with the location trigger weight set in the global parameters to calculate the location urgency.

[0024] For signal-triggered events, the reception score and attenuation score are calculated, and the signal urgency is calculated by combining the signal trigger weight set.

[0025] For business-triggered events, calculate the requirement score, and combine it with the business trigger weight to calculate the business urgency.

[0026] Based on the calculated urgency, the triggering events in the initial event queue are sorted in descending order to obtain the event-aware queue.

[0027] Specifically, the steps for switching states include:

[0028] Invoke the pre-stored event priority rules to obtain the perceived priority of the events to be processed, including high priority and low priority;

[0029] If the event to be processed is of high priority, a frequency band scanning strategy is adopted, including: obtaining the terminal's historical access operators, filtering commonly used operators for priority scanning, traversing the operators allowed to access in the geographical area where the terminal is located, obtaining the receiving parameters, and constructing a perception scanning set by operator classification based on the scanning time.

[0030] If the event to be processed is of low priority, the historical network environment data cached by the terminal is directly retrieved as the sensing scan set. If there is no cached data, a lightweight scan is performed to obtain the reception parameters of the surrounding operators that are allowed to access the network.

[0031] Specifically, the steps for switching state determination also include:

[0032] Based on the terminal's current network, obtain the actual received parameters;

[0033] Traverse the candidate networks in the sensing scan set and calculate the difference in reception parameters between each candidate network and the currently resident network.

[0034] Based on the preset filtering conditions, namely, if the difference in received parameters is greater than the filtering difference threshold in the global parameters, candidate networks that do not meet the filtering conditions are eliminated.

[0035] If no alternative network is found after filtering, the network is determined to be in a cached state, and the currently resident network is maintained.

[0036] If at least one candidate network exists after screening, the network is considered ready and a candidate network pool is constructed.

[0037] Specifically, the steps to obtain the suggested execution time window include:

[0038] Collect the channel occupancy rate of the currently hosted network within the geographical area of ​​the terminal, and construct a channel time series set by binding and sorting the sampling timestamps;

[0039] Retrieve the load judgment threshold and time parameters from the global parameters. The load judgment threshold is used to divide the network into three levels: idle, medium load, and high load. The time parameters include the base duration, minimum effective duration, and maximum allowed duration.

[0040] The channel occupancy rate of each sampling point in the channel time series is standardized to obtain the channel load coefficient corresponding to each sampling point, and the load sequence is obtained by the moving average method.

[0041] Obtain a load reference value based on the mean of the load sequence;

[0042] Using the time slot between any two adjacent sampling points as the dividing object, all time slots are divided into idle time slots, medium-load time slots, and high-load time slots by comparing the load determination threshold with the channel load coefficient;

[0043] All idle time slots are filtered out, and consecutive idle time slots are merged and idle time slots with a duration less than the minimum effective duration are removed to construct candidate idle intervals.

[0044] Specifically, the steps for obtaining the suggested execution time window also include:

[0045] The theoretical load in the global parameters is called, and the window adjustment coefficient is calculated by comparing the load reference value with the theoretical load. Combined with the base duration, the execution window duration is calculated.

[0046] For the idle time slots in the candidate idle interval, sort them in descending order of duration;

[0047] The sampling timestamp of the first idle time slot is selected as the window start time. Combined with the execution window duration, the window end time is obtained to construct candidate execution windows.

[0048] The candidate execution window is validated according to the preset validation rules.

[0049] If the verification fails, the sampling timestamp of the next idle time slot is selected based on the sorted candidate idle intervals to construct a candidate execution window and perform validity verification. This process is repeated until the verification passes, and finally a suggested execution time window containing the window start time and end time is generated.

[0050] Specifically, the allocation of the switch execution timestamp includes:

[0051] Based on the coordination group, the suggested execution time window for each terminal is obtained and mapped to a unified timeline;

[0052] Traverse the entire timeline to identify the current terminal's completely idle time period and define it as the global idle time period;

[0053] For each selected global idle time period, the validity of the global idle time period is determined. The global idle time period is considered valid only if the total duration of the global idle time period is greater than the minimum valid duration; otherwise, it is directly removed.

[0054] After screening and validity determination, if there are still global idle periods, target idle periods are screened, and the center timestamp of the target idle period is calculated as the switching execution timestamp.

[0055] If there is no global idle period, obtain the urgency of the event to be processed corresponding to the current terminal, and calculate the fallback offset in combination with the execution window duration. The switch execution timestamp is obtained by summing the window start time and the fallback offset.

[0056] The steps to match the optimal target configuration file for the current terminal include:

[0057] Read the candidate network pool and sort it in descending order by the difference in received parameters;

[0058] Iterate through the sorted pool of candidate networks and select the first candidate network as the scoring object;

[0059] Acquire scan data from all terminals within the coordination group and construct a group fusion dataset;

[0060] Sample data of candidate networks are selected from the group fusion dataset, the regional average load rate is calculated, and the maximum allowable load rate in the region is called to calculate the load adaptability of the candidate networks.

[0061] The adaptation threshold in the global parameters is called, and the adaptation is verified by comparing it with the load adaptability.

[0062] If the fit is greater than the fit threshold, it is determined that the candidate network meets the regional network access requirements, and the configuration file of the candidate network is called as the optimal target configuration file.

[0063] If the fit is not greater than the fit threshold, the next candidate network is selected as the scoring object, and so on, until the optimal target configuration file is selected.

[0064] The embedded SIM profile intelligent switching management method includes:

[0065] Real-time acquisition of terminal operating status data and network environment information; identification of triggering events through a multi-level triggering mechanism; sorting events in descending order of urgency; and construction of an event-aware queue.

[0066] Traverse the triggered events in the event awareness queue, and perform network environment detection through differentiated network awareness to determine the switching state of the current triggered event, including cached state and ready state;

[0067] In response to the ready state, based on the regional channel occupancy rate of the current camped network, a suggested execution time window is obtained, and a handover execution timestamp is allocated to the current terminal through coordinated group handover scheduling;

[0068] Based on the terminal location and the scanning data of each terminal in the coordination group, the optimal target configuration file is matched for the current terminal, and the switching execution instruction is constructed by combining the switching execution timestamp, and the terminal is driven to activate the target configuration file at the specified time.

[0069] Integrate the handover execution records reported by various terminals, construct the handover data package, configure the global parameters required for the handover operation, and perform dynamic optimization.

[0070] The beneficial effects of this invention are:

[0071] By real-time monitoring of terminal operation and network environment, and replacing traditional periodic network scanning with multi-level triggered events, redundant signaling interactions and additional energy consumption burdens caused by continuous scanning are eliminated. A perception queue is constructed based on the urgency of events, and differentiated network detection is performed only on the first high-priority event. This avoids resource waste caused by repeated detection of multiple events and indiscriminate full scanning. While maintaining accurate terminal perception of the optimal network, unnecessary energy consumption and signaling overhead are significantly reduced. Addressing the issue of signaling storms caused by massive concurrent device switching, ready-state terminals are grouped by geographical region to form a coordination group. Through group-level switching timing allocation and optimal configuration file matching for the adapted regional network, a new approach is adopted. This approach avoids the network signaling congestion caused by a large number of terminals simultaneously initiating handover requests, thus effectively ensuring the overall stability of network operation. Simultaneously, by driving the configuration file to activate and be stored at a specified time through handover execution instructions, coupled with the storage of handover execution records and a global parameter dynamic optimization mechanism, a closed-loop iterative optimization of the handover process is formed. While retaining the intelligent, low-latency, and highly reliable dynamic handover capabilities of eSIM operators, it achieves in-depth optimization of daily operational resource management, realizing the synergistic unity of terminal power consumption control, simplified signaling interaction, and improved network stability. This completely compensates for the application deficiencies of existing technologies in resource management and large-scale device concurrency scenarios. Attached Figure Description

[0072] Figure 1 Structure diagram of the intelligent switching management system for embedded SIM configuration files;

[0073] Figure 2 This is a flowchart illustrating the structure of the state switching determination in this invention;

[0074] Figure 3 This is a flowchart for obtaining the suggested execution time window in this invention;

[0075] Figure 4 Flowchart of intelligent switching management method for embedded SIM configuration files. Detailed Implementation

[0076] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments of the present invention and the specific features in the embodiments are detailed descriptions of the technical solution of the present invention, rather than limitations thereof. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments can be combined with each other.

[0077] Example 1

[0078] refer to Figures 1 to 3 As shown in the figure, this embodiment introduces an embedded SIM profile intelligent handover management system, including: an event sensing module, a handover coordination module, a handover execution module, and a management module;

[0079] The event awareness module is used to acquire terminal operating status data and network environment information in real time. It identifies trigger events through a multi-level triggering mechanism, sorts the trigger events according to their urgency, and builds an event awareness queue for the terminal. At the same time, it traverses the trigger events in the event awareness queue, takes the first trigger event as the event to be processed, and performs network environment detection through differentiated network awareness to obtain the corresponding network scan results. Based on the scan results, it determines the switching status of the event to be processed, including cached status and ready status.

[0080] The operational status data includes location information, signal information, and service information. Location information includes terminal coordinates, location area code, and tracking area code. Signal information includes reference signal received power and reference signal received quality. Service information includes the current operating service type, bandwidth requirements, and latency requirements. Network environment information includes the network identifiers of surrounding operators and frequency point information. Triggering events include location triggering events, signal triggering events, and service triggering events.

[0081] In response to the ready state, the handover coordination module sends a signaling coordination request to the core network equipment currently camped on the network. Based on the regional channel occupancy rate returned by the core network, it obtains a suggested execution time window. Simultaneously, it acquires all terminals within the geographical area where the current terminal is located, filters out terminals currently deemed ready, and constructs a coordination group for the current terminal. Through handover scheduling within the coordination group, it assigns a handover execution timestamp to the current terminal. Based on the terminal's location and the scan data of each terminal within the coordination group, it matches the optimal target profile for the current terminal and integrates the handover execution timestamp with the optimal target profile identifier. This allows for the construction of handover execution instructions to switch the target configuration file. The current camping network is the operator network where the terminal has successfully registered and is carrying data services. The coordination group uses the single location area code / tracking area code of the terminal's current camping network as the granularity for geographical area division. The maximum number of terminals in a single group is 200, and the group data update frequency is 100ms. The trigger condition for a terminal to join the group is that the terminal is in the current geographical area and is determined to be in the handover ready state. The trigger condition for a terminal to leave the group is that the terminal completes the handover, cancels the ready state, leaves the current geographical area, or has no data reported for more than 3 sampling periods.

[0082] The handover execution module is used to receive handover execution instructions and drive the terminal according to the instructions to activate the target configuration file at a specified time, complete the registration with the target operator's network and the service bearer handover, and ensure that the handover operation is implemented.

[0083] The management module stores the handover execution records reported by each terminal, including the handover success rate and the number of signaling interactions. Through a global configuration mechanism, it configures the global parameters required for handover operation, analyzes the handover effect in conjunction with the stored handover execution records, dynamically optimizes the global parameters, and feeds back the optimized global parameters to the event awareness module and the handover coordination module.

[0084] Furthermore, the steps for identifying triggering events through a multi-level triggering mechanism include:

[0085] The system performs noise reduction and standardization on operational status data and network environment information to remove abnormal data and generate standardized terminal datasets and network datasets.

[0086] Based on global parameters and through statistical analysis, multi-level judgment thresholds for triggering events are initialized, including location trigger thresholds, signal trigger thresholds, and service trigger thresholds. The location trigger threshold includes a displacement threshold and a duration threshold for area code changes (e.g., one sampling period). The signal trigger threshold includes a threshold triggering threshold (a single-sampling threshold for received power or received quality), an attenuation threshold, and the number of consecutive sampling periods. The service trigger thresholds include bandwidth determination thresholds and latency determination thresholds. The displacement threshold is determined based on terminal type, sampling period (default 1s), and displacement statistical analysis of typical mobile scenarios. It involves collecting displacement data for the target terminal type over 72 consecutive hours in corresponding typical mobile scenarios, extracting displacement distribution characteristics within a unit sampling period, and calculating the 95th percentile of the displacement data as the displacement threshold. For example, the default value is 100m for low-speed IoT terminals and 300m for mobile terminals. The displacement threshold increases by 100m for every 1s increase in the sampling period, with an upper limit of 500m. The duration threshold is determined based on statistical analysis of the signaling interaction cycle of location area code / tracking area code changes to avoid false triggering from a single area code change. The threshold triggering threshold is determined based on the mobile communication network measurement standards specified in the 3GPP TS 36.133 protocol, combined with statistical analysis of network coverage quality in different scenarios. The 36.133 protocol obtains the basic range of the receive power threshold and the basic range of the receive quality threshold. It collects network coverage measurement data for 7 consecutive days in the target application area (urban core area, suburbs, indoor). It statistically analyzes the handover success rate and false trigger rate under different threshold values ​​and selects the optimal value with a handover success rate ≥95% and a false trigger rate ≤0.5% as the threshold trigger threshold. For example, the receive power threshold is -120dBm~-100dBm, with a default of -110dBm, and the receive quality threshold is -14dB~-10dB, with a default of -12dB. The attenuation threshold is determined based on statistical analysis of typical scenarios of mobile communication network signal attenuation. Typical scenarios include the terminal entering the building obstruction area, moving quickly away from the base station, and sudden interference with the base station signal. The number of consecutive sampling periods is set based on the signal measurement anti-shake requirements specified by the 3GPP protocol. For example, if it is set to 3, the instantaneous signal fluctuation interference can be eliminated and false triggers can be avoided if the condition is met for 3 consecutive periods. The bandwidth judgment threshold and the latency judgment threshold are determined based on statistical analysis of the network requirements of typical services.

[0087] For location-triggered events, the system reads the terminal's location information from the terminal dataset, calculates the displacement between the terminal's current location and the location in the previous sampling period using Euclidean distance, and detects whether the area code has changed. Once a change in the area code is detected, the system calculates the duration of the area code change using the first detection time and the latest detection time.

[0088] If the displacement is greater than the displacement threshold or the duration is greater than the duration threshold, it is determined to be a location-triggered event, and the event identifier, displacement, and area code change information are associated.

[0089] For signal triggering, read continuously from the terminal dataset. The receiving parameters for each cycle, including received power and received quality, are used to calculate the signal attenuation rate based on the ratio of the difference in received power between adjacent sampling cycles to the time difference.

[0090] If continuous If, during a sampling period, a received parameter (i.e., any parameter value of received power or received quality) is less than the threshold triggering threshold and the signal attenuation rate is greater than the attenuation threshold, then it is determined to be a signal triggering event, and the event identifier, current signal information, and signal attenuation rate are associated.

[0091] For service triggers, read the service demand from the terminal dataset, including bandwidth demand and latency demand. If the service demand is greater than the service trigger threshold, it is determined to be a service trigger event, and the event representation, service type, and service demand are associated.

[0092] Furthermore, since the terminal performs continuous, real-time, and uninterrupted monitoring of the operating status data, the trigger event identification is an immediate response mechanism. Within the same collection period, the terminal may generate multiple types of trigger events. In order to immediately perform network environment detection, the highest priority trigger event must be selected immediately.

[0093] The steps to build an event-aware queue include:

[0094] The triggered events identified in the current sampling period are obtained, randomly arranged, and an initial event queue is generated.

[0095] For location-triggered events, a location score is calculated by the ratio of displacement to a displacement threshold. Based on preset area change rules, a corresponding change score is obtained. The location score and change score are weighted and summed using the location trigger weight set in the global parameters to obtain the location urgency. The change score is a standardized score that quantifies the impact of terminal location changes on the necessity of network handover. It is determined based on statistical analysis of handover risks and business impacts in different location change scenarios. Terminal location changes are categorized as having area code changes or not having area code changes. Full handover time data for the target terminal type in the corresponding scenario for 30 consecutive days is obtained, and statistical indicators are extracted, including handover trigger rate, average service interruption duration, and handover failure rate in different scenarios. These statistical indicators are weighted and summed. Since the handover trigger rate directly reflects the inherent probability of triggering handover in a location change scenario and is the core indicator of handover necessity, it is assigned the highest weight. The service interruption duration and handover failure rate reflect the impact on service experience and network operation risk, respectively, and their impact is relatively equal. Therefore, equal weights are assigned, with weights of 0.4, 0.3, and 0.3 respectively, to obtain the switching necessity index for different scenarios. The switching necessity index is linearly mapped to a score range of 0 to 100 points to obtain the change score for different scenarios. For example, the area change rules include: when there is an area code change, the switching necessity index is 0.4 and the change score is 40 points; when there is no area code change, the switching necessity index is 0.2 and the change score is 20 points. Since the displacement is the basic judgment condition for the location trigger event and directly reflects the terminal's movement range, it has a higher impact on the switching necessity. Therefore, the weight of the location score is higher than the weight of the change score. Historical switching data is obtained, and the initial value of the objective weight is calculated using the entropy weight method. It is determined whether the initial value of the objective weight meets the setting basis, that is, the weight of the location score is higher than the weight of the change score. If it meets the basis, the initial value of the objective weight is used as the location trigger weight set; if it does not meet the basis, the benchmark weight set is used as the location trigger weight set. The benchmark weight set includes a weight of 0.6 for the location score and a weight of 0.4 for the change score.

[0096] For signal-triggered events, the received power score and received quality score are obtained by the absolute value of the deviation rate between the received parameters and the threshold triggering threshold. The received score is obtained by averaging the received power score and received quality score. The attenuation score is calculated based on the ratio of the signal attenuation rate to the attenuation threshold. The received score and attenuation score are weighted and summed using the signal triggering weight set in the global parameters to obtain the signal urgency. The signal triggering weight set is designed based on the core risk of signal-triggered events. A sample dataset is constructed by acquiring full signal triggering handover event data for 30 consecutive days in the target scenario. Using hierarchical analysis, the influence of the received score and attenuation score on each criterion is compared using the handover success rate, false trigger rate, and service interruption duration as evaluation criteria. A pairwise comparison judgment matrix is ​​constructed, and the judgment matrix is ​​normalized. The eigenvector corresponding to the largest eigenvalue is calculated to obtain the weights of the received score and attenuation score. For example, the received score weight is 0.7 and the attenuation score weight is 0.3.

[0097] For service-triggered events, the bandwidth score and latency score are obtained by comparing the service demand with the service trigger threshold. The demand score is obtained by averaging the bandwidth score and latency score. The service urgency is obtained by multiplying the demand score using the service trigger weight in the global parameters. The service trigger weight is set based on the historical switching benefit ratio statistics of the target service. Switching data for each service type is collected within 30 days. The switching benefit ratio is calculated by comparing the improvement in service quality after switching with the service interruption duration during the switching process. When the benefit ratio is not less than 2, it indicates that the service is in a low-latency service, such as real-time voice and video calls, and the service trigger weight is set to 1.0. When 1 ≤ benefit ratio < 2, it indicates that the service is in a normal data service, such as web browsing and instant messaging, and the service trigger weight is set to 0.9. When the benefit ratio < 1, it indicates that the service is in a non-real-time service, such as background downloads and firmware updates, and the service trigger weight is set to 0.8.

[0098] Based on the calculated urgency, the triggering events in the initial event queue are sorted in descending order to obtain the event-aware queue.

[0099] Furthermore, determining the state transition of the event to be processed includes:

[0100] The pre-stored event priority rules are invoked to obtain the perceived priority of the events to be processed, including high priority and low priority. The event priority rules are set by those skilled in the art based on the terminal operating scenario and network requirements. For example, signal-triggered events are judged as high priority, while location-triggered events and service-triggered events are judged as low priority.

[0101] If the event to be processed is of high priority, in order to quickly and accurately obtain the current network environment and avoid network interruption, a frequency band scanning strategy is adopted, including: frequency band scanning follows the public network mobile communication frequency band allocation standard defined by the 3GPP TS 36.101 protocol, obtains the terminal's historical access operators and the corresponding access counts, takes the operator with the most access counts as the commonly used operator, and prioritizes scanning the frequency bands corresponding to the commonly used operator. The single frequency band scanning time is fixed at 20ms, and the remaining scanning order is arranged in descending order according to the historical access counts. The total scanning time of the entire process is capped at 200ms. It traverses the operators allowed to access in the geographical area where the terminal is located, obtains the receiving parameters, and constructs a perception scanning set according to operator classification based on the scanning time. At the same time, if a candidate network that meets the screening conditions is detected during the scanning process, the scanning is terminated in advance.

[0102] If the event to be processed is of low priority, the historical network environment data cached by the terminal is directly retrieved as the perception scan set. If there is no cached data, a lightweight scan is performed to obtain the reception parameters of the surrounding allowed operators. The lightweight scan only targets the mainstream frequency bands of the operators that the terminal has historically accessed. The number of frequency bands scanned does not exceed 3, the scan duration of a single frequency band is 15ms, and the total scan duration is capped at 80ms. Only the reception parameters of the alternative networks are collected. The full system broadcast message is not read, and the pre-synchronization process is not initiated.

[0103] Based on the terminal's current network, the actual received parameters are obtained and used as a comparison benchmark.

[0104] Traverse the candidate networks in the sensing scan set and calculate the difference in reception parameters between each candidate network and the currently resident network, including the difference in reception power and the difference in reception quality.

[0105] Based on the preset screening conditions, namely, the difference in received parameters is greater than the screening difference threshold in the global parameters, all candidate networks are screened to eliminate candidate networks that do not meet the screening conditions. The screening difference threshold is set based on the same-frequency / different-frequency handover measurement event standard specified by the 3GPP protocol. When the difference reaches the standard, it can ensure that the signal of the candidate network is significantly better than that of the currently camped network, thus avoiding ping-pong handover.

[0106] If no alternative network is found after filtering, that is, no alternative network meets the filtering conditions, it indicates that the current resident network is still the optimal choice and there is no need to switch. Then, the switching state corresponding to the event to be processed is determined to be the cache state, and the current resident network is maintained. At the same time, if the constructed perception scan set is a frequency band scan or a lightweight scan, a cache update instruction is generated to update the terminal cache.

[0107] If at least one alternative network exists after screening, meaning there is an alternative network that meets the screening criteria, it indicates that the signal of the alternative network is significantly better than the currently resident network and has switching value. In this case, the switching state corresponding to the event to be processed is determined to be ready, and an alternative network pool is constructed.

[0108] Furthermore, the steps to obtain the suggested execution time window include:

[0109] Based on continuous data collection, the channel occupancy rate of the currently camped network in the geographical area where the terminal is located is collected. Each channel occupancy rate is bound to the corresponding sampling timestamp and arranged in chronological order of sampling time to construct a channel time series set.

[0110] Retrieve the load judgment threshold and time parameters from the global parameters. The load judgment threshold includes a two-level load threshold, which is used to divide the network into three levels: idle, medium load, and high load. The time parameters include the base duration, minimum effective duration, and maximum allowed duration.

[0111] The channel occupancy rate of each sampling point in the channel time series is normalized using a min-max method to obtain the channel load coefficient corresponding to each sampling point. ;in, The sampling point number, , This represents the total number of sampling points within the channel timing set.

[0112] Considering that instantaneous load fluctuations can affect the accuracy of load determination, such as a sudden increase in occupancy caused by a burst of traffic from a single terminal, a moving average method is used to smooth the load coefficients of all channels, resulting in a smoothed load sequence that eliminates instantaneous fluctuation interference and reflects the true load trend of the regional channels.

[0113] Obtain a load reference value based on the mean of the load sequence;

[0114] Using the time slot between any two adjacent sampling points as the dividing object, all time slots are divided into idle time slots, medium-load time slots, and high-load time slots by comparing the load judgment threshold with the channel load coefficient. For example, the secondary load threshold values ​​for the load judgment threshold are 0.3 and 0.7. When the channel load coefficient is ≤0.3, it is an idle time slot; when 0.3 < channel load coefficient ≤0.7, it is a medium-load time slot; and when the channel load coefficient is >0.7, it is a high-load time slot.

[0115] All idle time slots are filtered out, consecutive idle time slots are merged, and idle time slots with a duration less than the minimum effective duration are removed. All idle time slots after merging and removal are integrated to construct a candidate idle interval.

[0116] The theoretical load from the global parameters is used to calculate the window adjustment factor by comparing the load reference value with the theoretical load. Combined with the base duration, the execution window duration is calculated. The expression is as follows:

[0117]

[0118] In the formula, The base duration is set based on the total time consumed throughout the entire process, including eSIM profile activation, target network registration, and service handover. This is a load reference value. The theoretical load is determined based on statistical analysis of the optimal operating load range of the mobile communication network. For example, the theoretical load is set at 50%, taking into account both access performance and resource utilization.

[0119] For the idle time slots in the candidate idle interval, they are sorted in descending order by the duration of a single idle time slot. The sampling timestamp of the first idle time slot is selected as the window start time. Combined with the execution window duration, the window end time is obtained, thereby constructing the candidate execution window.

[0120] Based on preset verification rules, the candidate execution window is validated. If the validation fails, the sampling timestamp of the next idle time slot is selected based on the sorted candidate idle intervals to construct the candidate execution window and perform validation. This process is repeated until the validation passes, and finally, a suggested execution time window containing the window start time and end time is generated. The validation rule is that all time slots in the candidate execution window are idle time slots and the window duration is less than the maximum allowed duration. The maximum allowed duration is determined based on the statistical analysis of the entire process of eSIM configuration file handover. For example, if the maximum allowed duration is set to 3 seconds, the normal handover time is 500ms~800ms. The 3-second duration can completely cover the entire handover process and avoid timing conflicts caused by excessively long windows.

[0121] Furthermore, the allocation of the switch execution timestamp includes:

[0122] Since the coordination group gathers terminals by geographical region, and the mainstream networks of each terminal in the group are different, the matching suggestion execution time windows are different. Based on the coordination group, the suggestion execution time window corresponding to each terminal is obtained. Combined with the suggestion execution time window of the current terminal, it is mapped to a unified time axis. Traversing the entire time axis, the pure idle time period is identified where the suggestion execution time windows of the current terminal and other terminals in the coordination group are not covered or overlapped. That is, in the pure idle time period, there is no suggestion execution time window of any terminal. This is defined as the global idle time period.

[0123] For each selected global idle time period, the validity of the global idle time period is determined. The global idle time period is considered valid only if the total duration of the global idle time period is greater than the minimum valid duration. Otherwise, the corresponding global idle time period is directly removed.

[0124] After screening and validity assessment, if there are still global idle periods, the global idle period with the longest total duration is selected first as the target idle period to ensure that the handover has sufficient time to complete and reduce the risk of timeout. If there are global idle periods with the same total duration, the one closest to the current time is selected to continue screening, which improves the handover timeliness, adapts to the dynamic changes in network load, and calculates the center timestamp of the target idle period as the handover execution timestamp of the current terminal to ensure that the handover execution falls in the middle of the period and avoids load fluctuations that may occur at the edge of the period.

[0125] If there is no global idle period, a fallback allocation is performed based on urgency. The urgency of the event to be processed corresponding to the current terminal is obtained. The fallback offset is calculated by the ratio of the execution window duration to the urgency. The switching execution timestamp of the current terminal is obtained by summing the window start time and the fallback offset, thus realizing differentiated fallback scheduling based on urgency priority.

[0126] For example, there are 3 terminals to be switched in the coordination group, including terminal 1, terminal 2 and terminal 3. Terminal 1 is the current terminal, residing on network A, with a window of 100-200ms and an urgency of 5. Terminal 2 is residing on network B, with a window of 120-150ms. Terminal 3 is residing on network C, with a window of 160-180ms.

[0127] By aggregating all terminal windows, mapping them to a unified timeline, and marking the position of each window, the global idle time periods within terminal 1 window are identified as 100-120ms (duration 20ms), 150-160ms (duration 10ms), and 180-200ms (duration 20ms). The minimum effective duration is 15ms. Therefore, 150-160ms (duration 10ms < 15ms) is removed. Since the retained global idle time periods are of consistent duration, the 100-120ms period closest to the current time (if the current time is 95ms) is selected, and the center timestamp is calculated to be 110ms. Therefore, the execution timestamp of terminal 1 is 110ms.

[0128] If the window of terminal 1 is 130-170ms (duration 40ms), the window of terminal 2 is 120-150ms, and the window of terminal 3 is 140-200ms, and the window of terminal 1 is completely covered by the windows of other terminals, then the fallback offset is calculated as follows: The corresponding execution timestamp is 130 + 8 = 138ms.

[0129] Furthermore, the steps for matching the optimal target configuration file for the current terminal include:

[0130] Read the candidate network pool and obtain the difference in the receiving parameters of each candidate network. Sort the candidate networks in descending order by the sum of the difference in the receiving parameters. The higher the ranking, the greater the advantage of the network signal relative to the current network.

[0131] Iterate through the sorted pool of candidate networks and select the first candidate network as the scoring object;

[0132] Obtain the scan data of all terminals in the coordination group, construct the group fusion dataset in the form of a sample matrix, with each row being the scan sample of one terminal and each column being network parameters, including network identifier, load rate, signal strength, frequency band, and operator identifier;

[0133] Sample data for candidate networks are selected from the ensemble dataset. The network where the terminal resides is the scan data for candidate networks. The average load rate of the region is calculated by averaging the load rates of the sample data. At the same time, the maximum allowable load rate in the region is called to calculate the load fit of the candidate network. The normalized load is calculated by the ratio of the average load rate of the region to the maximum allowable load rate. The load fit is obtained by subtracting the normalized load from 1.

[0134] The adaptation threshold in the global parameters is called and compared with the load adaptability to perform adaptation verification. The adaptation threshold is determined by statistical analysis based on the high load threshold (i.e., 0.7 in the secondary load threshold) of the mobile communication network. In order to reserve sufficient access safety margin and avoid congestion caused by sudden load surge due to sudden business, the safety margin coefficient is set to 0.5. That is, only the load range below 50% of the high load threshold is used as the safe access range. The normalized load is obtained by multiplying the high load threshold and the safety margin coefficient and then dividing by the maximum allowable load rate. The adaptation threshold is obtained by subtracting the normalized load from 1. For example, if the adaptation threshold is set to 0.6, since the load adaptability and the network load rate are inversely related, the higher the adaptability, the lower the actual network load rate and the better the access conditions.

[0135] If the fit is greater than the fit threshold, it is determined that the candidate network meets the regional network access requirements. At this time, the configuration file of the candidate network is called and used as the optimal target configuration file.

[0136] If the fit is not greater than the fit threshold, the next candidate network is selected as the scoring object, and so on, until the optimal target configuration file is selected. If, after traversing all candidate networks in the candidate network pool, the load fit of all networks is not greater than the fit threshold, the fit threshold is automatically reduced in steps of 10%, up to a maximum of 2 times, and the candidate network pool is re-verified for fit. If there is a network that meets the conditions, its corresponding configuration file is directly matched for a first-level retry. If there is still no candidate network that meets the conditions after the retry, it is determined that there is no available switching network that meets the access requirements in the current area, the current resident network is maintained, and a cache update instruction for the scanned data is generated to update the terminal's local cache for a second-level fallback. The abnormal event and the regional network load data are simultaneously reported to the management module to trigger the dynamic optimization process of global parameters.

[0137] Example 2

[0138] Please see Figure 4 Another embodiment of the present invention provides a method for intelligent switching management of embedded SIM profiles, comprising the following steps:

[0139] The system acquires real-time terminal operating status data and network environment information, identifies triggering events through a multi-level triggering mechanism, sorts triggering events by urgency, and builds an event-aware queue for the terminal.

[0140] Traverse the triggered events in the event awareness queue, take the first pending triggered event as the processing object, perform network environment detection through differentiated network awareness to obtain the corresponding network scan results, and determine the switching status of the current triggered event based on the scan results, including cached status and ready status;

[0141] In response to the ready state, based on the regional channel occupancy rate of the current camped network, a suggested execution time window is obtained. A coordination group is constructed for all terminals in the geographical area where the current terminal is located that are currently determined to be in the ready state. The terminals in the coordination group that are determined to be in the ready state are the coordination objects. Through the handover scheduling of the coordination group, a handover execution timestamp is allocated.

[0142] Based on the terminal location and the scanning data of each terminal in the coordination group, the optimal target configuration file is matched for the current terminal. The switching execution timestamp and the optimal target configuration file identifier are integrated to construct the switching execution command and drive the terminal to activate the target configuration file at the specified time.

[0143] The system integrates handover execution records reported by various terminals, constructs handover data packets, configures the global parameters required for handover operation, and performs dynamic optimization. Dynamic optimization utilizes an incremental PID algorithm to perform closed-loop optimization of global parameters, using handover success rate, average terminal energy consumption, and signaling interaction counts as core control variables. Based on preset target values, parameters such as thresholds, weights, and durations are incrementally adjusted to avoid system instability caused by large parameter fluctuations. The regular optimization cycle is 24 hours, with statistical analysis of all handover execution records from the previous day performed daily at midnight, followed by parameter optimization. If more than 10 consecutive handover failures or regional signaling congestion events occur, an emergency optimization process is immediately triggered. If, after parameter adjustment, the handover success rate improves, terminal energy consumption decreases, and the number of signaling interactions decreases, it is considered effective optimization, and the parameter adjustment results are retained. If the handover success rate drops by more than 2 percentage points, or a handover anomaly occurs, the system immediately reverts to the parameters before adjustment, and optimization analysis is conducted again.

[0144] Working principle and effects:

[0145] The system acquires terminal operating status and network environment information in real time. It identifies triggering events through a multi-level triggering mechanism and constructs an event awareness queue based on urgency. It only performs differentiated network detection on the first pending event to determine its handover status. In the ready state, it requests a channel data acquisition time window from the core network, gathers ready terminals in the same area to build a coordination group, allocates timestamps through group coordination, matches the optimal configuration file, integrates and generates handover instructions to drive the terminal to complete the configuration handover, and stores handover records and dynamically optimizes them in combination with global parameters to reduce energy consumption and signaling overhead, avoid signaling storms in concurrent scenarios, ensure network stability, realize closed-loop optimization of the handover process, and balance the intelligence of eSIM handover with resource management efficiency.

[0146] The above description is merely a preferred embodiment of the present invention. The scope of protection of the present invention is not limited to the above embodiments. All technical solutions falling within the scope of the present invention's concept are within the scope of protection of the present invention. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principles of the present invention should also be considered within the scope of protection of the present invention.

Claims

1. An embedded SIM profile intelligent switching management system, characterized in that, include: Event awareness module, switching coordination module, switching execution module; The event perception module is used to acquire the terminal's operating status data and network environment information in real time, identify triggering events through a multi-level triggering mechanism, construct an event perception queue, and determine the switching status through differentiated network perception, including cached status and ready status. The switching coordination module responds to the ready state, obtains the suggested execution time window, allocates a switching execution timestamp to the current terminal and matches the optimal target configuration file through the switching scheduling of the coordination group, and generates a switching execution instruction. The switching execution module is used to receive and execute the switching execution instruction.

2. The embedded SIM profile intelligent switching management system according to claim 1, characterized in that, The steps for identifying triggering events through a multi-level triggering mechanism include: The runtime status data is denoised and standardized to generate a terminal dataset; Based on global parameters, statistical analysis is used to initialize multi-level judgment thresholds for triggering events; Read the location information in the terminal data set, calculate the displacement using Euclidean distance, and detect whether the area code has changed. Once a change in the area code is detected, calculate the duration of the area code change. If the displacement is greater than the displacement threshold or the duration is greater than the duration threshold, it is determined to be a position-triggered event; For signal triggering, read continuously. Calculate the signal attenuation rate based on the received parameters for each cycle; If continuous If the received parameters for a sampling period are less than the threshold trigger threshold and the signal attenuation rate is greater than the attenuation threshold, then it is determined to be a signal trigger event. For business triggers, read the business demand volume from the terminal dataset. If the business demand volume is greater than the business trigger threshold, it is determined to be a business trigger event.

3. The embedded SIM profile intelligent switching management system according to claim 2, characterized in that, The steps to build an event-aware queue include: Get the triggered events identified in the current sampling period, arrange them randomly and disordered, and generate an initial event queue; For location-triggered events, calculate the location score and change score, and combine them with the location trigger weight set in the global parameters to calculate the location urgency. For signal-triggered events, the reception score and attenuation score are calculated, and the signal urgency is calculated by combining the signal trigger weight set. For business-triggered events, calculate the requirement score, and combine it with the business trigger weight to calculate the business urgency. Based on the calculated urgency, the triggering events in the initial event queue are sorted in descending order to obtain the event-aware queue.

4. The embedded SIM profile intelligent switching management system according to claim 3, characterized in that, The steps for switching state determination include: The first triggered event is taken as the event to be processed. The pre-stored event priority rules are invoked to obtain the perceived priority of the event to be processed, including high priority and low priority. If the event to be processed is of high priority, a frequency band scanning strategy is adopted, including: obtaining the terminal's historical access operators, filtering commonly used operators for priority scanning, traversing the operators allowed to access in the geographical area where the terminal is located, obtaining the receiving parameters, and constructing a perception scanning set by operator classification based on the scanning time. If the event to be processed is of low priority, the historical network environment data cached by the terminal is directly retrieved as the sensing scan set. If there is no cached data, a lightweight scan is performed to obtain the reception parameters of the surrounding operators that are allowed to access the network.

5. The embedded SIM profile intelligent switching management system according to claim 4, characterized in that, The steps for switching state determination also include: Based on the terminal's current network, obtain the actual received parameters; Traverse the candidate networks in the sensing scan set and calculate the difference in reception parameters between each candidate network and the currently resident network. Based on the preset filtering conditions, namely, if the difference in received parameters is greater than the filtering difference threshold in the global parameters, candidate networks that do not meet the filtering conditions are eliminated. If no alternative network is found after filtering, the network is determined to be in a cached state, and the currently resident network is maintained. If at least one candidate network exists after screening, the network is considered ready and a candidate network pool is constructed.

6. The embedded SIM profile intelligent switching management system according to claim 5, characterized in that, The steps to obtain the suggested execution time window include: Collect the channel occupancy rate of the currently hosted network in the geographical area where the terminal is located, and construct a channel time series set by sorting the sampling timestamps; Retrieve the load judgment threshold and time parameters from the global parameters. The load judgment threshold is used to divide the network into three levels: idle, medium load, and high load. The time parameters include the base duration, minimum effective duration, and maximum allowed duration. The channel occupancy rate at each sampling point is standardized to obtain the channel load coefficient, and the load sequence is obtained by using the moving average method. Obtain a load reference value based on the mean of the load sequence; Using the time slot between any two adjacent sampling points as the dividing object, all time slots are divided into idle time slots, medium-load time slots, and high-load time slots by comparing the load determination threshold with the channel load coefficient; All idle time slots are filtered out, and consecutive idle time slots are merged and idle time slots with a duration less than the minimum effective duration are removed to construct candidate idle intervals.

7. The embedded SIM profile intelligent switching management system according to claim 6, characterized in that, The steps to obtain the suggested execution time window include: The theoretical load in the global parameters is called, and the window adjustment coefficient is calculated by comparing the load reference value with the theoretical load. Combined with the base duration, the execution window duration is calculated. For the idle time slots in the candidate idle interval, sort them in descending order of duration; The sampling timestamp of the first idle time slot is selected as the window start time. Combined with the execution window duration, the window end time is obtained to construct candidate execution windows. The candidate execution window is validated according to the preset validation rules. If the verification fails, the sampling timestamp of the next idle time slot is selected based on the sorted candidate idle intervals to construct a candidate execution window and perform validity verification. This process is repeated until the verification passes, and finally a suggested execution time window containing the window start time and end time is generated.

8. The embedded SIM profile intelligent switching management system according to claim 7, characterized in that, The timestamp for assigning a switchover execution includes: Based on the coordination group, the suggested execution time window for each terminal is obtained and mapped to a unified timeline; Traverse the entire timeline to identify the current terminal's completely idle time period and define it as the global idle time period; For each selected global idle time period, the validity of the global idle time period is determined. The global idle time period is considered valid only if the total duration of the global idle time period is greater than the minimum valid duration; otherwise, it is directly removed. After screening and validity determination, if there are still global idle periods, target idle periods are screened, and the center timestamp of the target idle period is calculated as the switching execution timestamp. If there is no global idle period, obtain the urgency of the event to be processed corresponding to the current terminal, and calculate the fallback offset in combination with the execution window duration. The switch execution timestamp is obtained by summing the window start time and the fallback offset.

9. The embedded SIM profile intelligent switching management system according to claim 8, characterized in that, The steps for matching the optimal target configuration file include: Read the candidate network pool and sort it in descending order by the difference in received parameters; Iterate through the sorted pool of candidate networks and select the first candidate network as the scoring object; Acquire scan data from all terminals within the coordination group and construct a group fusion dataset; Sample data of candidate networks are selected from the group fusion dataset, the regional average load rate is calculated, and the maximum allowable load rate in the region is called to calculate the load adaptability of the candidate networks. The adaptation threshold in the global parameters is called, and the adaptation is verified by comparing it with the load adaptability. If the fit is greater than the fit threshold, it is determined that the candidate network meets the regional network access requirements, and the configuration file of the candidate network is called as the optimal target configuration file. If the fit is not greater than the fit threshold, the next candidate network is selected as the scoring object, and so on, until the optimal target configuration file is selected.

10. An embedded SIM profile intelligent switching management method, implemented based on the embedded SIM profile intelligent switching management system as described in any one of claims 1-9, characterized in that, include: Real-time acquisition of terminal operating status data and network environment information; identification of triggering events through a multi-level triggering mechanism; sorting events in descending order of urgency; and construction of an event-aware queue. Traverse the triggered events in the event awareness queue, and perform network environment detection through differentiated network awareness to determine the switching state of the current triggered event, including cached state and ready state; In response to the ready state, based on the regional channel occupancy rate of the current camped network, a suggested execution time window is obtained, and a handover execution timestamp is allocated to the current terminal through coordinated group handover scheduling; Based on the terminal location and the scanning data of each terminal in the coordination group, the optimal target configuration file is matched for the current terminal, and the switching execution instruction is constructed by combining the switching execution timestamp, and the terminal is driven to activate the target configuration file at the specified time. Integrate the handover execution records reported by various terminals, construct the handover data package, configure the global parameters required for the handover operation, and perform dynamic optimization.

Images