Configuration file management method, system, equipment and medium

Abstract

The invention discloses a configuration file management method, system and device and a medium, and relates to the technical field of the Internet of Things, and the method comprises the steps that a management server obtains a corresponding configuration file operation instruction from a configuration file management platform in response to a task query request sent by user equipment; based on the equipment performance parameters of the user equipment, performing message segmentation processing on the configuration file operation instruction to generate an instruction sequence matched with the user equipment; the instruction sequence is sent to the user equipment, so that the user equipment controls a secure element to execute the instruction sequence, and an execution result is collected and returned to a management server; and sending the execution result to a configuration file management platform. Accurate adaptation of the configuration file operation instruction is achieved according to the performance difference of different user equipment, the problem of execution failure or resource overload caused by mismatching of the instruction message and the equipment processing capacity is avoided, and orderliness and accuracy of configuration file operation are guaranteed.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) technology, and more specifically to a configuration file management method, system, device, and medium. Background Technology

[0002] In the field of profile management technology for embedded universal integrated circuit cards (eUICC), the GSMA's SGP.22 standard defines a technical solution with a Local Profile Assistant (LPA) as the core control module. Currently, there are two main implementation methods for LPA: one is to deploy the LPA on the device side (LPAd), and the other is to embed the LPA within the eUICC (LPAe). The LPAd solution requires device manufacturers to develop customized programs for different device operating environments, integrating complex functions such as HTTPS request processing, ASN.1 data parsing, and APDU instruction assembly, placing high demands on the device's storage space and computing power.

[0003] While the LPAe solution avoids on-device integration, it relies on the smart card's application toolkit, resulting in poor interoperability with external data and limitations imposed by carrier SMS services. The LPAd solution demands significant device storage and computing power, while the LPAe solution suffers from limitations in data interaction and service dependencies. Cloud-based LPA solutions, on the other hand, face challenges such as high device integration and adaptation costs, inconsistent capabilities of unadapted devices, insufficient resource optimization, lack of IoT platform compatibility, and weak device authentication mechanisms. These issues lead to difficulties in standardized integration across different manufacturers, malfunctions on low-computing-power devices, significant resource waste, increased system complexity, and the risk of identity theft, ultimately failing to meet the efficient, secure, and low-cost eUICC configuration file management requirements of IoT scenarios. Summary of the Invention

[0004] The main objective of this invention is to provide a configuration file management method, system, device, and medium. By centrally processing the adaptation of configuration file operation commands through a management server, precise adaptation of command types is achieved to address the performance differences of different user devices, avoiding execution failures or resource overload caused by mismatches between command messages and device processing capabilities. Simultaneously, relying on the command interaction and result feedback link between the management server and user devices, the effective execution of configuration file operations by the security element is ensured, realizing a closed-loop flow of operation commands and execution results among the configuration file management platform, management server, user devices, and security elements, guaranteeing the orderliness and accuracy of configuration file operations. Furthermore, through standardized command processing and interaction flows, the complex processing logic on the user device side is reduced, lowering resource consumption during configuration file management and improving overall configuration file management efficiency.

[0005] To achieve the above objectives, the embodiments of this application provide the following technical solutions: According to a first aspect of the embodiments of this application, a configuration file management method is provided, the method comprising: The management server responds to the task query request sent by the user device and obtains the corresponding configuration file operation instructions from the configuration file management platform; Based on the device performance parameters of the user equipment, the configuration file operation instructions are segmented to generate an instruction sequence that matches the user equipment. The instruction sequence is sent to the user equipment so that the user equipment controls the security element to execute the instruction sequence, collects the execution results and returns them to the management server; The execution result is sent to the configuration file management platform.

[0006] Optionally, the step of performing message segmentation processing on the configuration file operation instructions based on the device performance parameters of the user equipment to generate an instruction sequence matching the user equipment includes: Determine the configuration file operation type corresponding to the task query request. The configuration file operation type includes downloading, enabling, disabling, or deleting the configuration file. Extract the maximum processable message length of the user equipment from the pre-stored device performance parameters; Based on the maximum processable message length, the configuration file operation instructions are divided into several instruction blocks, wherein the length of each instruction block does not exceed the maximum processable message length; The instruction blocks are arranged in a preset execution order to generate an instruction sequence that matches the user equipment.

[0007] Optionally, before responding to a task query request sent by a user equipment, the method further includes: Receive an authentication request sent by the user equipment, the authentication request carrying the unique identifier of the user equipment, the unique identifier of the security element, and a digital signature generated by the user equipment using its own private key; Verify whether the unique identifier of the user equipment has been recorded in the pre-stored device registration information; verify the validity of the digital signature using the pre-stored public key; verify the legality of the security element and the binding relationship between the security element and the unique identifier of the user equipment using a preset security protocol; After all verifications are successful, the management server generates a first random number and sends it to the user equipment; the user equipment generates a second random number and sends it to the management server. The user equipment and the management server use the same key derivation algorithm to obtain the same communication encryption key and message authentication code key based on the first random number and the second random number.

[0008] Optionally, sending the instruction sequence to the user equipment includes: The instruction sequence is encrypted using the communication encryption key; The target communication protocol is determined based on the network protocol support information in the pre-stored device performance parameters; The encrypted instruction sequence is sent to the user equipment via the target communication protocol.

[0009] Optionally, the user equipment controls the security element to execute the instruction sequence, collects the execution results, and returns them to the management server; including: The user equipment uses the communication encryption key to decrypt the received encrypted instruction sequence and forwards the decrypted instruction sequence to the security element for execution. The user equipment obtains the execution result of the security element, and the execution result includes an operation success response code, an operation failure response code, or business data corresponding to the configuration file operation; The user equipment calculates the MAC value of the execution result using the message authentication code key, and encrypts the execution result and the corresponding MAC value before returning them to the management server; After receiving the message, the management server verifies the MAC value using the message authentication code key to complete the integrity verification of the execution result.

[0010] Optionally, before obtaining the corresponding configuration file operation instructions from the configuration file management platform, the method further includes: Obtain the operation type and real-time operating status of the user device corresponding to the task query request, wherein the real-time operating status includes device battery level and network signal strength; The task priority is determined based on the operation type and the real-time running status, and a task execution queue is established based on the task priority to schedule the order in which operation instructions are requested from the configuration file management platform. The data retransmission parameters are preset according to the real-time operating status; if the instruction sequence is determined to fail to be sent in the subsequent instruction transmission steps, a retransmission operation is triggered according to the preset data retransmission parameters.

[0011] Optionally, sending the execution result to the configuration file management platform includes: Generate a status notification message and call the interface of the configuration file management platform to send it, so as to notify the task execution result; The execution results and user device status information are synchronized to one or more external IoT platforms.

[0012] According to a second aspect of the embodiments of this application, a configuration file management system is provided, the system comprising: The instruction determination module is used to respond to the task query request sent by the user device and obtain the corresponding configuration file operation instructions from the configuration file management platform; The message processing module is used to perform message segmentation processing on the configuration file operation instructions based on the device performance parameters of the user equipment, so as to generate an instruction sequence that matches the user equipment. The instruction sending module is used to send the instruction sequence to the user equipment, so that the user equipment controls the security element to execute the instruction sequence, collects the execution results and returns them to the management server; The result sending module is used to send the execution result to the configuration file management platform.

[0013] According to a third aspect of the present application, an electronic device is provided, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in the first aspect above.

[0014] According to a fourth aspect of the embodiments of this application, a computer-readable storage medium is provided having computer-readable instructions stored thereon, the computer-readable instructions being executable by a processor to implement the method described in the first aspect above.

[0015] In summary, this application provides a configuration file management method, system, device, and medium. A management server responds to a task query request sent by a user device and obtains corresponding configuration file operation instructions from a configuration file management platform. Based on the user device's performance parameters, the configuration file operation instructions are segmented to generate an instruction sequence matching the user device. The instruction sequence is sent to the user device, enabling the user device to control a security element to execute the instruction sequence. The execution results are collected and returned to the management server. The execution results are then sent to the configuration file management platform. By centrally handling the adaptation of configuration file operation instructions through the management server, accurate adaptation of configuration file operation instructions is achieved for the performance differences of different user devices, avoiding execution failures or resource overload problems caused by mismatch between instruction messages and device processing capabilities. Simultaneously, relying on the instruction interaction and result feedback link between the management server and the user device, the effective execution of configuration file operations by the security element is ensured, realizing a closed-loop flow of operation instructions and execution results among the configuration file management platform, management server, user device, and security element, guaranteeing the orderliness and accuracy of configuration file operations. Furthermore, by standardizing command processing and interaction procedures, the complex processing logic on the user device side is reduced, the resource consumption of the user device in the configuration file management process is reduced, and the overall configuration file management efficiency is improved. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0017] The structures, proportions, sizes, etc. illustrated in this specification are only for the purpose of assisting those skilled in the art in understanding and reading the content disclosed herein, and are not intended to limit the conditions under which the present invention can be implemented. Therefore, they have no substantial technical significance. Any modifications to the structure, changes in the proportions, or adjustments to the size, without affecting the effects and objectives that the present invention can produce, should still fall within the scope of the technical content disclosed in the present invention.

[0018] Figure 1 A flowchart of a configuration file management method provided in this application embodiment; Figure 2 This is a schematic diagram of a two-layer interaction architecture between the cloud and the device side provided in an embodiment of this application; Figure 3 This is a schematic diagram of the multi-terminal interaction process provided in the embodiments of this application; Figure 4 This is a schematic diagram illustrating the specific interactive process of the download task provided in an embodiment of this application; Figure 5 This is a schematic diagram of instruction splitting and interaction provided in an embodiment of this application; Figure 6 A schematic diagram of the configuration file management system provided in this application embodiment; Figure 7 This paper shows a structural diagram of an electronic device provided in an embodiment of this application; Figure 8 A diagram of a computer-readable storage medium provided in an embodiment of this application is shown.

[0019] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0020] 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 a part of the embodiments of the present invention, and not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0021] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0022] Furthermore, in this invention, descriptions involving "first," "second," etc., are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0023] In this invention, unless otherwise explicitly specified and limited, the terms "connection," "fixed," etc., should be interpreted broadly. For example, "fixed" can mean a fixed connection, a detachable connection, or an integral part; it can mean a mechanical connection or an electrical connection; it can mean a direct connection or an indirect connection through an intermediate medium; it can mean the internal communication of two components or the interaction between two components, unless otherwise explicitly limited. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0024] Furthermore, the technical solutions of the various embodiments of the present invention can be combined with each other, but only if they are based on the ability of those skilled in the art to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be considered that such combination of technical solutions does not exist and is not within the scope of protection claimed by the present invention.

[0025] Figure 1 This application illustrates a configuration file management method according to an embodiment of the present application. The method includes: Step 101: The management server responds to the task query request sent by the user device and obtains the corresponding configuration file operation instructions from the configuration file management platform; Step 102: Based on the device performance parameters of the user equipment, perform message segmentation processing on the configuration file operation instructions to generate an instruction sequence that matches the user equipment; Step 103: Send the instruction sequence to the user equipment so that the user equipment controls the security element to execute the instruction sequence, collects the execution results and returns them to the management server; Step 104: Send the execution result to the configuration file management platform.

[0026] This application embodiment uses a management server to handle the acquisition and adaptation of configuration file operation instructions, thereby achieving differentiated instruction adaptation for different user devices. This avoids execution anomalies caused by mismatch between instruction message specifications and user device performance, ensuring stable execution of configuration file operations by the security element.

[0027] Specifically, the management server obtains standardized operation instructions from the configuration file management platform, then segments the messages based on pre-stored user device performance parameters to generate an instruction sequence that matches the device's processing capabilities. This approach adapts to the operational needs of user devices with low computing power and limited storage, while also fully leveraging the processing advantages of high-performance devices, reducing the instruction parsing pressure on user devices. Simultaneously, it ensures the accurate distribution of configuration file operation instructions and the reliable feedback of execution results, guaranteeing the orderliness and accuracy of the entire configuration file management process and improving the overall execution efficiency of configuration file operations.

[0028] In one possible implementation, the method further includes, prior to responding to a task query request sent by a user equipment: The system receives an authentication request from the user equipment, the authentication request carrying the unique identifier of the user equipment, the unique identifier of the security element, and a digital signature generated by the user equipment using its own private key; verifies whether the unique identifier of the user equipment has been recorded in the pre-stored device registration information; verifies the validity of the digital signature using a pre-stored public key; verifies the legitimacy of the security element and the binding relationship between the security element and the unique identifier of the user equipment using a preset security protocol; after all verifications are successful, the management server generates a first random number and sends it to the user equipment; the user equipment generates a second random number and sends it to the management server; the user equipment and the management server respectively use the same key derivation algorithm to obtain the same communication encryption key and message authentication code key based on the first and second random numbers.

[0029] This implementation establishes a dual authentication mechanism between the management server, user devices, and security elements to ensure that all entities participating in configuration file management interactions are legitimate, preventing the risk of unauthorized devices or security elements accessing the system and laying a solid security foundation for the transmission and execution of subsequent configuration file operation commands. Specifically, the legitimacy of the user device is authenticated by verifying its unique registration status and the digital signature generated by its private key. The legitimacy of the security element is verified through a preset security protocol, and the binding relationship between the security element and the user device is verified to prevent the security element from being misused or mismatched. Based on this, after successful authentication, the management server and user device generate random numbers and exchange them bidirectionally. Then, using the same key derivation algorithm, they combine the two sets of random numbers to generate a consistent communication encryption key and message authentication code key. This provides end-to-end encryption and integrity verification capabilities for the transmission of subsequent command sequences and execution results, preventing data from being tampered with, stolen, or forged during transmission.

[0030] In one possible implementation, before obtaining the corresponding configuration file operation instructions from the configuration file management platform, the method further includes: The system obtains the operation type and real-time operating status of the user device corresponding to the task query request, including device battery level and network signal strength; determines the task priority based on the operation type and the real-time operating status, and establishes a task execution queue based on the task priority to schedule the order in which operation instructions are requested from the configuration file management platform; presets data retransmission parameters based on the real-time operating status; if the instruction sequence fails to be sent in a subsequent instruction transmission step, a retransmission operation is triggered according to the preset data retransmission parameters.

[0031] This implementation optimizes the execution efficiency of configuration file operations and reduces resource consumption of user devices during command interaction by introducing a task priority scheduling mechanism and a differentiated retransmission strategy. Specifically, this implementation determines task priorities based on the operation type corresponding to the task query request and the real-time operating status of the user device (device battery level, network signal strength). A task execution queue is then established based on these priorities to schedule the order in which operation commands are requested from the configuration file management platform, ensuring that urgent configuration file operations are executed first and preventing non-urgent tasks from consuming limited device resources. Simultaneously, this implementation presets data retransmission parameters based on the real-time operating status of the user device. During subsequent command transmission, if the command sequence is determined to have failed to send, a retransmission operation will be performed according to the preset parameters. This avoids wasting device power and bandwidth due to blind retransmission and ensures the reliability of command transmission when the device is in good condition.

[0032] In one possible implementation, in step 102, the step of performing message segmentation processing on the configuration file operation instructions based on the device performance parameters of the user equipment to generate an instruction sequence matching the user equipment includes: determining the configuration file operation type corresponding to the task query request, wherein the configuration file operation type includes configuration file download, enable, disable, or delete; extracting the maximum processable message length of the user equipment from the pre-stored device performance parameters; splitting the configuration file operation instructions into several instruction blocks according to the maximum processable message length, wherein the length of each instruction block does not exceed the maximum processable message length; and arranging the several instruction blocks in a preset execution order to generate an instruction sequence matching the user equipment.

[0033] This implementation method segments configuration file operation commands by precisely matching the message processing capabilities of the user equipment, ensuring that the commands can be stably received by the user equipment and forwarded to the secure element for execution, thus avoiding problems such as execution failure and lag caused by the command message length exceeding the device's processing limit.

[0034] Specifically, this implementation first clarifies the configuration file operation type (download, enable, disable, delete, etc.) corresponding to the task, and then extracts the core performance parameter of the maximum message length that the user device can process, based on which the complete configuration file operation instructions are broken down into several instruction blocks that match the device's processing capabilities. This segmentation method can adapt to the differences in hardware performance of different user devices. Whether it is a low-computing-power device that only supports small message processing or a high-performance device with large message processing capabilities, it can obtain matching instruction data, effectively reducing the instruction processing pressure on the user device. At the same time, by arranging the instruction blocks according to the preset execution order to generate the instruction sequence, the orderly execution of configuration file operations by the security element can be guaranteed, ensuring that the segmented instructions can accurately restore the original operation logic, avoiding configuration file operation anomalies caused by disordered instruction order, and further improving the reliability and accuracy of configuration file management.

[0035] In one possible implementation, step 103, sending the instruction sequence to the user equipment, includes: encrypting the instruction sequence using the communication encryption key; determining the target communication protocol based on network protocol support information in pre-stored device performance parameters; and sending the encrypted instruction sequence to the user equipment using the target communication protocol.

[0036] This implementation ensures the security of configuration file operation commands during transmission by encrypting the command sequence and precisely adapting the communication protocol. It also adapts to the protocol support capabilities of different user devices, improving the stability and compatibility of command transmission. Specifically, this implementation uses the communication encryption key generated during the authentication phase to encrypt the command sequence, effectively preventing commands from being stolen, tampered with, or forged during transmission, thus ensuring the secure transmission of configuration file operation commands. Furthermore, the management server determines the target communication protocol matching the user device based on the network protocol support information in the pre-stored user device performance parameters. This allows for the selection of appropriate protocols for high-performance devices supporting complex protocols such as HTTPS and MQTT, as well as lightweight protocols for low-computing-power devices supporting only basic protocols such as TCP. This avoids command transmission failures due to protocol incompatibility and reduces the protocol parsing burden on low-computing-power devices.

[0037] In one possible implementation, in step 103, the user equipment controls the security element to execute the instruction sequence, collects the execution result, and returns it to the management server; this includes: the user equipment decrypting the received encrypted instruction sequence using the communication encryption key, and forwarding the decrypted instruction sequence to the security element for execution; the user equipment obtaining the execution result of the security element, the execution result including an operation success response code, an operation failure response code, or business data corresponding to the configuration file operation; the user equipment calculating the MAC value of the execution result using the message authentication code key, and encrypting the execution result and the corresponding MAC value before returning it to the management server; the management server receiving the MAC value and verifying it using the message authentication code key to complete the execution result integrity verification.

[0038] This implementation ensures the accurate execution of the instruction sequence between the user equipment and the secure element, while also guaranteeing the security and integrity of the execution result transmission, further enhancing the reliability of the configuration file management process. Specifically, the user equipment first decrypts the received encrypted instruction sequence using a communication encryption key, and then forwards the complete instruction sequence to the secure element for execution. This process ensures that the instructions executed by the secure element are the original, unaltered, and compatible instructions, avoiding operational anomalies caused by instruction decryption failures or incompleteness. Simultaneously, the execution result explicitly includes an operation response code and corresponding business data, ensuring the traceability and integrity of the configuration file operation results. Based on this, the user equipment calculates the MAC value of the execution result using a message authentication code key, then encrypts the result and the MAC value before sending it back. The management server receives this and verifies the MAC value using the same key, effectively verifying whether the execution result has been tampered with or stolen during transmission. This ensures that the execution result obtained by the management server is authentic and reliable, providing an accurate basis for subsequent feedback to the configuration file management platform.

[0039] In one possible implementation, in step 104, sending the execution result to the configuration file management platform includes: generating a status notification message and calling the interface of the configuration file management platform to send it, so as to notify the task execution result; and synchronizing the execution result and user device status information to one or more external IoT platforms.

[0040] This implementation achieves a closed-loop feedback mechanism for the execution results of configuration file operation tasks, while simultaneously synchronizing data with external IoT platforms, enhancing the collaboration and controllability of the configuration file management process. Specifically, the management server generates standardized status notification messages and sends these messages via the corresponding interface of the configuration file management platform. This ensures timely feedback of task execution results to the platform, guaranteeing accurate understanding of the operational status of security elements and providing data support for subsequent configuration file lifecycle management. Simultaneously, synchronizing execution results and user device status information to one or more external IoT platforms meets the needs of multi-platform collaborative management in IoT scenarios. This allows device manufacturers or maintenance personnel to uniformly monitor device configuration file operations through IoT platforms without requiring the development of additional cross-platform data interaction modules, reducing system integration complexity.

[0041] The configuration file management method provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0042] Figure 2 This diagram illustrates the two-layer interaction architecture of cloud and device adopted in the embodiments of this application. It mainly includes two core parts: cloud and device. The functions and interaction relationships of each module are as follows: I. Cloud The cloud platform uses a cloud agent as its core hub, integrating six functional modules: device management, identity authentication, task control, multi-protocol adaptation, security management, and profile task processing. It also enables data interaction with external systems such as the DP+ platform and IoT platforms of device manufacturers. 1. Device Management Module: Responsible for maintaining basic device information, including device SN, IMEI, device certificate, etc., to provide data support for subsequent identity verification and task scheduling; 2. Identity Authentication Module: This module is responsible for two-way authentication between the cloud and the device, as well as the secure element (eUICC). It also generates communication encryption keys and message verification code keys in a distributed manner, laying the foundation for secure communication. 3. Task Management Module: Supports dynamic scheduling of task priorities. Priority weights can be set based on task type (such as emergency profile switching, regular data synchronization) and device status (such as online / offline, power level) to ensure that high-priority tasks are executed first and avoid task congestion that leads to device response delays. 4. Multi-protocol adaptation module: Provides encapsulation and adaptation capabilities for multiple types of communication protocols. It supports native integration with standardized protocols such as HTTPS and MQTT, and can also encapsulate lightweight custom protocols based on TCP (simplifying the interaction process and message structure). At the same time, it supports automatic adaptation to the exclusive protocol specifications of various platforms to achieve seamless cross-protocol communication. 5. Security Management Module: Responsible for encryption / decryption of communication messages, calculation and verification of MAC values, and implementation of SCP02 / SCP03 and custom security protocols, which can effectively prevent data leakage, tampering and replay attacks; 6. Profile Task Processing Module: This module is responsible for parsing and splitting configuration file operation instructions. It can split instructions into appropriate instructions (APDUs) according to device capabilities, and at the same time complete data interaction with third-party systems such as DP+ and device manufacturer IoT platforms, and synchronize eUICC information to external systems.

[0043] II. Equipment End The device side is centered around the device agent, which acts as an interactive bridge between the device, eUICC, and the cloud agent. The core function of the device agent is to connect the device, eUICC, and the cloud agent. On the one hand, it completes the mutual authentication process between the device, eUICC, and the cloud agent. On the other hand, it participates in the decentralized generation of communication encryption keys and message verification code keys, and realizes the forwarding of instructions and data. It is a key intermediate layer for the interaction between the device side and the cloud agent.

[0044] III. Module Interaction Relationships As the interaction entry point on the device side, the device agent establishes a communication connection with the cloud agent, completes identity authentication and key negotiation, receives instructions issued by the cloud agent and forwards them to the eUICC for execution; the execution result of the eUICC is returned to the cloud agent through the device agent, and then synchronized by the cloud agent to external systems such as the DP+ platform and the device manufacturer's IoT platform, forming a closed-loop data chain of "device side-cloud-external system".

[0045] Figure 3 This embodiment illustrates the complete interaction sequence between the cloud agent, device agent, eUICC, and DP+ platform, covering aspects such as identity authentication, command adaptation, task execution, and result synchronization. The specific process is as follows: I. Identity Authentication Stage This phase includes two sub-processes: "Authentication Device" and "Authentication eUICC," which complete the legitimacy verification and key negotiation of the participants. 1. Authentication Device: The device agent initiates a device message request to the cloud agent. The cloud agent executes the device authentication process (verifies the registration status of the device's unique identifier and verifies the device's signature value) and returns the authentication device response to the device agent. After successful authentication, both parties enter the secure transmission preparation phase, generating a communication encryption key and a message authentication code key by exchanging random numbers (which will be used for message encryption and MAC integrity verification later).

[0046] 2. Authentication of eUICC: The cloud agent initiates a mutual authentication request (such as IPAc-eUICC) to the eUICC through the device agent. After the eUICC completes the verification, it returns the mutual authentication result, which is then sent back to the cloud agent through the device agent. This process can select SCP02 / SCP03 / custom protocol according to needs, and verifies the binding relationship between the eUICC's eID and the device's unique identifier to ensure the legitimate matching of the eUICC and the device.

[0047] II. Command Adaptation and Task Execution Phase After successful identity verification, the task execution command interaction process begins: 1. Task Query and Command Acquisition: The device agent initiates a task query request. The cloud agent obtains the corresponding Profile operation command (such as download, enable, etc.) from the DP+ platform, and splits and adapts the command based on the pre-stored device capability parameters (maximum message length, etc.) to generate a command sequence that the device agent can process.

[0048] 2. Command Issuance and Execution: The cloud agent distributes the adapted command sequence to the device agent. After receiving all the commands, the device agent decrypts them using the communication encryption key and forwards them to the eUICC for execution in sequence. After the eUICC completes the execution, it returns a command response, which is collected by the device agent and sent back to the cloud agent.

[0049] III. Results Notification and Status Synchronization Phase After the task is completed, the cloud agent will synchronize the results to the external system: the device agent will send the execution results of eUICC back to the cloud agent, and the cloud agent will organize the result notification message. On the one hand, it will call the HandleNotification interface of the DP+ platform to feed back the task results, and on the other hand, it can synchronize the execution results and device status to external systems such as the device manufacturer's IoT platform, so as to realize the state closed loop of the entire process of configuration file operation.

[0050] This sequence diagram illustrates the entire chain logic from identity authentication and command adaptation to task execution and result synchronization. Through layered interaction and security mechanisms, it not only ensures the security and adaptability of configuration file operations, but also realizes data collaboration between multiple systems.

[0051] Figure 4 This paper illustrates the specific interaction flow of the eUICC Profile download task in this embodiment of the application. Centered on "DP+Platform-Cloud Proxy-Device Proxy-eUICC", the download task completes security authentication, instruction execution, and result synchronization in stages. The specific flow is as follows: I. Pre-construction safety preparation phase Before the download task is executed, identity authentication and secure transmission mechanisms must be established: 1. Mutual authentication: A two-way identity authentication process is performed between the cloud agent, the device agent, and the eUICC (including device legitimacy verification, eUICC legitimacy verification, and verification of the binding relationship between the two) to ensure that all participants are legitimate entities; 2. Secure Transmission Configuration: After successful authentication, both parties will configure the encryption rules (encrypting message content) and integrity verification rules (calculating MAC value) for subsequent messages based on the negotiated communication encryption key and message authentication code key, laying the foundation for secure communication in the download process.

[0052] II. Download Task Execution Phase This stage uses a "looping execution of 4 steps" as its core logic to complete the organization, issuance, and execution of Profile instructions: 1. Task query and instruction organization: The device agent initiates a task query request to the cloud agent. The cloud agent organizes the corresponding operation instructions according to the Profile download requirements and sends them to the device agent through a secure transmission link. 2. Command forwarding and response: The device agent calls eUICC to execute the command. After eUICC completes the command processing, it returns the command response result, which is then sent back to the cloud agent through the device agent, completing the interaction loop of a single command. 3. Task Request and Profile Execution: The cloud agent initiates a task request to the DP+ platform, obtains the specific task instructions for Profile download, and then sends the task response to the device agent. The device agent calls eUICC to execute the Profile download instructions. After eUICC completes the download, it returns the "instruction execution result" and sends it back to the cloud agent through the device agent.

[0053] III. Results Notification Stage 4. After the Profile download command is executed, the cloud agent will synchronize the result to the DP+ platform: After receiving the download execution result of eUICC, the cloud agent will send a "result notification" request to the DP+ platform. The DP+ platform will return the "notification result", completing the status loop of the entire Profile download task.

[0054] This sequence diagram represents the specific business scenario of Profile download. Through the process design of "security preparation - loop command interaction - result synchronization", it not only ensures the security of the download process, but also adapts to the segmented transmission requirements of Profile data through the loop execution mechanism, ensuring that low computing power devices can stably complete the download task.

[0055] Figure 5 This document illustrates the specific interactive process of splitting, issuing, and installing the Profile command in an embodiment of this application, demonstrating the logic of "command splitting based on device capabilities" and "segmented execution - result concatenation." The specific process is as follows: I. Profile Command Package Acquisition and Splitting Stage This stage involves obtaining the Profile command package and splitting the commands based on device capabilities: 1. Obtain the instruction package: The cloud agent sends a Get Bound Profile Package request to the DP+ platform and receives the Get Bound Profile Package Response (i.e., the Profile instruction package) returned by the DP+ platform. 2. Command splitting: The cloud agent parses the DP+ response content and, in conjunction with pre-stored device capability parameters (such as the maximum processable message length), splits the complete Profile command package into multiple APDU command segments adapted to the device's processing capabilities, preparing for subsequent segmented distribution.

[0056] II. Segmented Instruction Issuance Phase The cloud agent gradually sends the split instruction segments to the device agent by executing the process in a loop: the cloud agent sends the split instruction to the device agent, the device agent receives and processes it, and then requests subsequent instructions from the cloud agent; the cloud agent continues to send the remaining instruction segments until all instruction segments have been sent, adapting to the device's message processing capabilities and avoiding resource overload caused by the device receiving excessive data.

[0057] III. Profile Installation and Result Assembly Stage After receiving all command segments, the device agent completes the installation of the Profile and the assembly of the results: 1. Segmented installation: The device agent executes the split instruction segments sequentially by calling eUICC to execute the Profile installation instruction through multiple loops. After eUICC completes the execution of each instruction segment, it returns the instruction execution result to the device agent. 2. Result Assembly and Feedback: The device agent assembles the execution results of multiple commands into a complete installation result and sends the command response result back to the cloud agent. After receiving the result, the cloud agent parses it and confirms the status of the entire Profile installation process.

[0058] By using the logic of instruction splitting, segmented issuance, and segmented execution, it not only adapts to the processing limitations of low-computing-power devices but also ensures the integrity and accuracy of Profile installation, serving as a key process support for achieving "reduced device-side resource consumption".

[0059] In summary, this application addresses the pain point of limited eUICC device capabilities in IoT scenarios by proposing a two-layer lightweight architecture of "device-side proxy + cloud proxy," and simultaneously constructing a technical system for dynamic adaptation, multi-protocol integration, and dual security authentication, as detailed below: The architecture adopts a layered structure of "device-side agent + cloud agent": the device-side agent is designed to be lightweight and only needs to implement the basic functions of "device capability collection - data forwarding - response feedback". It supports OTA remote deployment and does not need to integrate complex modules such as protocol parsing and data encoding, which greatly reduces the complexity of device integration; the cloud agent integrates core capabilities such as protocol adaptation, security authentication and platform docking, and acts as the interaction hub to work with the device-side agent through two-way verification and encrypted links.

[0060] The device-side agent collects capability parameters such as the device's maximum message length and battery level. The cloud-side agent then generates Profile data splitting rules (segmented according to the device's maximum supported length) to prevent the device from overloading its resources due to processing excessive data. At the same time, it dynamically controls the number of retransmissions based on the device's real-time status (such as signal strength and battery level) to reduce unnecessary communication consumption.

[0061] The cloud agent has built-in interfaces such as MQTT and CoAP, which can directly connect to various platforms to achieve data synchronization and command coordination. At the same time, it dynamically selects the communication protocol according to the device's capabilities: HTTPS / MQTT protocol is used for high-computing-power devices, and TCP or a custom lightweight protocol is used for low-computing-power devices to adapt to the resource limitations of different devices.

[0062] A dual security authentication mechanism of "device + eUICC" is constructed: the device's legitimacy is verified through pre-installed certificates and challenge-response verification, and the card's legitimacy is verified through the binding relationship between the eUICC's EID and public key; at the same time, the TLS1.3 encrypted link and SCP series security protocols are combined to ensure communication security and prevent identity spoofing, data leakage and tampering.

[0063] The technical solution of this application embodiment is applicable to IoT scenarios with low device capability requirements. It can realize efficient and secure interaction between eUICC and SM-DP+, while reducing device integration complexity and resource consumption, and reducing the workload of IoT device manufacturers in terms of modification.

[0064] In summary, this application provides a configuration file management method. A management server responds to a task query request sent by a user device and obtains corresponding configuration file operation instructions from a configuration file management platform. Based on the device performance parameters of the user device, the configuration file operation instructions are segmented to generate an instruction sequence matching the user device. The instruction sequence is sent to the user device, enabling the user device to control a security element to execute the instruction sequence. The execution results are collected and returned to the management server. The execution results are then sent to the configuration file management platform. By centrally handling the adaptation of configuration file operation instructions through the management server, accurate adaptation of configuration file operation instructions is achieved for the performance differences of different user devices, avoiding execution failures or resource overload problems caused by mismatch between instruction messages and device processing capabilities. Simultaneously, relying on the instruction interaction and result feedback link between the management server and the user device, the effective execution of configuration file operations by the security element is ensured, realizing a closed-loop flow of operation instructions and execution results among the configuration file management platform, management server, user device, and security element, guaranteeing the orderliness and accuracy of configuration file operations. Furthermore, by standardizing command processing and interaction procedures, the complex processing logic on the user device side is reduced, the resource consumption of the user device in the configuration file management process is reduced, and the overall configuration file management efficiency is improved.

[0065] Based on the same technical concept, embodiments of this application also provide a configuration file management system, such as... Figure 6 As shown, the system includes: The instruction determination module 601 is used to obtain the corresponding configuration file operation instruction from the configuration file management platform in response to the task query request sent by the user equipment. The message processing module 602 is used to perform message segmentation processing on the configuration file operation instructions based on the device performance parameters of the user equipment, so as to generate an instruction sequence that matches the user equipment. The instruction sending module 603 is used to send the instruction sequence to the user equipment, so that the user equipment controls the security element to execute the instruction sequence, collects the execution results and returns them to the management server; The result sending module 604 is used to send the execution result to the configuration file management platform.

[0066] This application also provides an electronic device corresponding to the method provided in the foregoing embodiments. Please refer to... Figure 7The diagram illustrates an electronic device provided by some embodiments of this application. The electronic device 20 may include: a processor 200, a memory 201, a bus 202, and a communication interface 203, wherein the processor 200, the communication interface 203, and the memory 201 are connected via the bus 202; the memory 201 stores a computer program that can run on the processor 200, and when the processor 200 runs the computer program, it executes the method provided by any of the foregoing embodiments of this application.

[0067] The memory 201 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one physical port (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc.

[0068] Bus 202 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 201 is used to store programs. After receiving an execution instruction, the processor 200 executes the program. The method disclosed in any of the foregoing embodiments of this application can be applied to the processor 200, or implemented by the processor 200.

[0069] The processor 200 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of the processor 200 or by instructions in software form. The processor 200 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 201. The processor 200 reads the information in memory 201 and, in conjunction with its hardware, completes the steps of the above method.

[0070] The electronic devices and methods provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods they employ, operate, or implement.

[0071] This application also provides a computer-readable storage medium corresponding to the method provided in the foregoing embodiments. Please refer to... Figure 8 The computer-readable storage medium shown is an optical disc 30, on which a computer program (i.e., a program product) is stored, which, when run by a processor, executes the methods provided in any of the foregoing embodiments.

[0072] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0073] The computer-readable storage medium provided in the above embodiments of this application and the method provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the application stored therein.

[0074] It should be noted that the above embodiments are illustrative of this application and not restrictive, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. This application can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names.

[0075] The above description is merely a preferred embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0076] The above description is only a preferred embodiment of the present invention and does not limit the patent scope of the present invention. All equivalent structural transformations made under the concept of the present invention using the contents of the present invention specification and drawings, or direct / indirect applications in other related technical fields, are included within the patent protection scope of the present invention.

Claims

1. A configuration file management method, characterized in that, The method includes: The management server responds to the task query request sent by the user device and obtains the corresponding configuration file operation instructions from the configuration file management platform; Based on the device performance parameters of the user equipment, the configuration file operation instructions are segmented to generate an instruction sequence that matches the user equipment. The instruction sequence is sent to the user equipment so that the user equipment controls the security element to execute the instruction sequence, collects the execution results and returns them to the management server; The execution result is sent to the configuration file management platform.

2. The method as described in claim 1, characterized in that, The step of segmenting the configuration file operation instructions based on the device performance parameters of the user equipment to generate an instruction sequence matching the user equipment includes: Determine the configuration file operation type corresponding to the task query request. The configuration file operation type includes downloading, enabling, disabling, or deleting the configuration file. Extract the maximum processable message length of the user equipment from the pre-stored device performance parameters; Based on the maximum processable message length, the configuration file operation instructions are divided into several instruction blocks, wherein the length of each instruction block does not exceed the maximum processable message length; The instruction blocks are arranged in a preset execution order to generate an instruction sequence that matches the user equipment.

3. The method as described in claim 1, characterized in that, Before responding to a task query request sent by a user equipment, the method further includes: Receive an authentication request sent by the user equipment, the authentication request carrying the unique identifier of the user equipment, the unique identifier of the security element, and a digital signature generated by the user equipment using its own private key; Verify whether the unique identifier of the user equipment has been recorded in the pre-stored device registration information; verify the validity of the digital signature using the pre-stored public key; verify the legality of the security element and the binding relationship between the security element and the unique identifier of the user equipment using a preset security protocol; After all verifications are successful, the management server generates a first random number and sends it to the user equipment; the user equipment generates a second random number and sends it to the management server. The user equipment and the management server use the same key derivation algorithm to obtain the same communication encryption key and message authentication code key based on the first random number and the second random number.

4. The method as described in claim 3, characterized in that, Sending the instruction sequence to the user equipment includes: The instruction sequence is encrypted using the communication encryption key; The target communication protocol is determined based on the network protocol support information in the pre-stored device performance parameters; The encrypted instruction sequence is sent to the user equipment via the target communication protocol.

5. The method as described in claim 4, characterized in that, The user equipment controls the security element to execute the instruction sequence, collect the execution results, and return them to the management server; including: The user equipment uses the communication encryption key to decrypt the received encrypted instruction sequence and forwards the decrypted instruction sequence to the security element for execution. The user equipment obtains the execution result of the security element, and the execution result includes an operation success response code, an operation failure response code, or business data corresponding to the configuration file operation; The user equipment calculates the MAC value of the execution result using the message authentication code key, and encrypts the execution result and the corresponding MAC value before returning them to the management server; After receiving the message, the management server verifies the MAC value using the message authentication code key to complete the integrity verification of the execution result.

6. The method as described in claim 1, characterized in that, Before obtaining the corresponding configuration file operation instructions from the configuration file management platform, the process also includes: Obtain the operation type and real-time operating status of the user device corresponding to the task query request, wherein the real-time operating status includes device battery level and network signal strength; The task priority is determined based on the operation type and the real-time running status, and a task execution queue is established based on the task priority to schedule the order in which operation instructions are requested from the configuration file management platform. The data retransmission parameters are preset according to the real-time operating status; if the instruction sequence is determined to fail to be sent in the subsequent instruction transmission steps, a retransmission operation is triggered according to the preset data retransmission parameters.

7. The method as described in claim 1, characterized in that, Sending the execution result to the configuration file management platform includes: Generate a status notification message and call the interface of the configuration file management platform to send it, so as to notify the task execution result; The execution results and user device status information are synchronized to one or more external IoT platforms.

8. A configuration file management system, characterized in that, The system includes: The instruction determination module is used to respond to the task query request sent by the user device and obtain the corresponding configuration file operation instructions from the configuration file management platform; The message processing module is used to perform message segmentation processing on the configuration file operation instructions based on the device performance parameters of the user equipment, so as to generate an instruction sequence that matches the user equipment. The instruction sending module is used to send the instruction sequence to the user equipment, so that the user equipment controls the security element to execute the instruction sequence, collects the execution results and returns them to the management server; The result sending module is used to send the execution result to the configuration file management platform.

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 the processor executes the computer program to implement the method as claimed in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, It stores computer-readable instructions that can be executed by a processor to implement the method as described in any one of claims 1-7.

Images