A configuration file compatible processing method, device and equipment

Abstract

The application provides a configuration file compatible processing method, device and equipment, and relates to the technical field of Internet of Things. The method is applied to an eSIM card and comprises the following steps: after security check of a configuration file data packet is passed, each configuration file element is parsed according to a preset configuration file specification. In the case that parsing of any configuration file element is abnormal, the writing action of the configuration file element is suspended, and corresponding abnormal identification information is extracted. According to the abnormal identification information, a local configuration file element rule template library is queried to determine a corresponding repair scheme. The repair scheme is used for compatible repair to obtain a repaired configuration file element. The repaired configuration file element is re-parsed, and in the case that the re-parsing is successful, the repaired configuration file element is written into a file system of the eSIM card, so that the problems of insufficient security, poor Profile compatibility and low download success rate in the traditional configuration file download process can be solved.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, and in particular to a configuration file compatibility processing method, apparatus, and device. Background Technology

[0002] With the development of embedded subscriber identity card (eSIM) technology, terminal devices can remotely download and install operator profiles to enable user identification, network access, and related service configuration. The profile is typically generated by the embedded subscriber identity module (eSIM) remote provisioning (RSP) from different data preparation+ (DP+) platforms and then distributed to the eSIM. The eSIM then performs decryption, verification, parsing, and installation locally.

[0003] In practical applications, differences in the configuration files generated by different vendors' DP+ platforms mean that some configuration files may not fully comply with the Trusted Connectivity Alliance (TCA) / GSMA (GSM Association) specifications. This can lead to eSIM card failures during profile download, parsing, or installation. Traditional methods typically rely on strict specification verification, terminating the installation process upon detecting non-compliance. While this approach prevents the installation of abnormal configuration files, it significantly reduces the success rate of profile downloads, thus impacting the user experience.

[0004] Therefore, there is an urgent need for a configuration file compatibility processing method, device, and equipment to improve the security, profile compatibility, and download success rate during the configuration file download process. Summary of the Invention

[0005] The purpose of this application is to provide a method, apparatus, and device for compatibility processing of configuration files, which solves the problems of insufficient security, poor profile compatibility, and low download success rate in traditional configuration file download processes.

[0006] In a first aspect, embodiments of this application provide a configuration file compatibility processing method applied to an eSIM card. The method includes: after the configuration file data packet passes security verification, parsing each configuration file element in the configuration file data packet according to a preset configuration file specification. If an exception occurs during the parsing of any configuration file element, suspending the write operation of that configuration file element and extracting the exception identifier information corresponding to that configuration file element. Querying a local configuration file element rule template library based on the exception identifier information to determine a repair scheme corresponding to that configuration file element. Using the repair scheme to perform compatibility repair on the configuration file element, obtaining a repaired configuration file element. Re-parsing the repaired configuration file element, and if the re-parsing is successful, writing the repaired configuration file element to the file system of the eSIM card.

[0007] The configuration file compatibility processing method provided in this application provides a method that, after the configuration file data packet passes security verification, parses each configuration file element in the configuration file data packet one by one according to the preset configuration file specification. If an error occurs in the parsing of any configuration file element, the writing action of that configuration file element is suspended, and the error identification information corresponding to that configuration file element is extracted. This ensures that the abnormal configuration file element will not be written to the eSIM card's file system before compatibility repair and re-parsing are completed, thereby reducing the risk of abnormal configuration file elements affecting the eSIM card's file system.

[0008] Based on the anomaly identification information, the local profile element rule template library is queried to determine the corresponding repair solution for the profile element. This repair solution is then used to perform compatibility repair on the profile element, resulting in a repaired profile element. This allows the eSIM card to match corresponding repair solutions for different profile elements and different anomaly situations based on the rule template corresponding to the profile element, thereby achieving fine-grained compatibility processing of profile elements and improving profile compatibility. Finally, the repaired profile element is re-parsed, and if re-parsed successfully, the repaired profile element is written to the eSIM card's file system. This re-verification of the repaired profile element before writing improves the reliability of writing the profile element to the file system.

[0009] One possible implementation involves parsing each configuration file element in the configuration file data packet according to a preset configuration file specification. This includes: sequentially reading the configuration file elements to be parsed from the configuration file data packet according to the configuration file specification; parsing the field structure of the currently read configuration file element to determine the field information of each field; determining whether the currently read configuration file element meets the configuration file specification based on the field information; and identifying an anomaly in the parsing of the currently read configuration file element if it is determined that the currently read configuration file element does not meet the preset configuration file specification.

[0010] One possible implementation involves the exception identification information including one or more of the following: configuration file element identifier, parent field label, and error type. Based on the exception identification information, the local configuration file element rule template library is queried to determine the corresponding remediation plan for that configuration file element. This includes: determining candidate rule templates corresponding to the configuration file element from the local configuration file element rule template library based on the configuration file element identifier; determining the target rule template corresponding to the parent field label from the candidate rule templates based on the parent field label; determining the remediation strategy and remediation method corresponding to the configuration file element from the target rule template based on the error type; and determining the remediation plan corresponding to the configuration file element based on the remediation strategy and remediation method.

[0011] One possible implementation of the configuration file compatibility processing method provided in this application embodiment further includes: if no candidate rule template corresponding to the configuration file element is found, or a target rule template matching the parent field label is found, determining that the exception corresponding to the configuration file element is a serious exception, and terminating the installation process of the configuration file data package.

[0012] One possible implementation involves a repair scheme that includes a repair strategy and a repair method. The repair scheme is used to perform compatibility repair on the configuration file element, resulting in a repaired configuration file element. This includes: determining whether the configuration file element is suitable for compatibility repair based on the repair strategy; if the configuration file element is suitable for compatibility repair and the repair strategy is an automatic repair strategy, repairing the abnormal fields in the configuration file element according to the repair method, resulting in a repaired configuration file element; if the configuration file element is suitable for compatibility repair and the repair strategy is a restricted repair strategy, repairing the file attributes or access conditions in the configuration file element according to the repair method, resulting in a repaired configuration file element; if the configuration file element is not suitable for compatibility repair, terminating the configuration file data package installation process.

[0013] One possible implementation involves repairing the abnormal fields in the configuration file element according to the repair method, resulting in a repaired configuration file element. This includes: if the error type of the configuration file element is determined to be a missing field, supplementing the missing sub-field in the configuration file element according to the sub-field identifiers and default values ​​in the repair plan; if the error type of the configuration file element is determined to be an abnormal field length, truncating redundant data bytes in the configuration file element, or padding the end of the configuration file element with preset data to ensure the field length meets the configuration file specification; if the error type of the configuration file element is determined to be the presence of non-standard encoding, converting the abnormal field data containing the non-standard encoding in the configuration file element to a standard encoding format; and if the error type of the configuration file element is determined to be a process blockage caused by a non-critical field, deleting or masking the non-critical field in the configuration file element according to the sub-field identifier list in the repair plan.

[0014] One possible implementation involves repairing the file attributes or access conditions in the configuration file element according to the repair method to obtain the repaired configuration file element. This includes: if the error type of the configuration file element is determined to be an abnormal access condition or an abnormal file attribute, adjusting the access conditions or file attributes corresponding to the configuration file element according to the sub-field identifier and default value in the repair scheme.

[0015] One possible implementation, the configuration file compatibility processing method provided in this application embodiment, further includes: skipping the negligible verification exception when it is determined that the error type of the configuration file element is a negligible verification exception.

[0016] One possible implementation, before querying the local configuration file element rule template library based on the anomaly identification information to determine the corresponding repair solution for the configuration file element, further includes: determining, based on the anomaly identification information, whether the field in the configuration file element that caused the anomaly matches a preset security constraint. The security constraint includes a set of security constraint fields. This set of security constraint fields records security control fields that are not applicable to compatibility repairs. If the field that caused the anomaly matches a security constraint, the installation process of the configuration file data package is terminated. If the field that caused the anomaly does not match a security constraint, the step of querying the local configuration file element rule template library based on the anomaly identification information to determine the corresponding repair solution for the configuration file element is executed.

[0017] One possible implementation, as provided in this application embodiment, of the configuration file compatibility processing method further includes: receiving a rule update package issued by the eSIM management platform. The rule update package includes one or more of the following: added rules, modified rules, or deleted rules. Each rule includes a version number and effective conditions. The rule update package undergoes integrity and legality verification. After successful verification, the local configuration file element rule template library is updated according to the rule update package.

[0018] Secondly, embodiments of this application provide a configuration file compatibility processing device applied to an eSIM card. The device includes a parsing module, an extraction module, a determination module, and a repair module.

[0019] The parsing module is used to parse each configuration file element in the configuration file data packet one by one according to the preset configuration file specifications after the security verification of the configuration file data packet has passed.

[0020] The extraction module is used to suspend the writing action of any configuration file element and extract the corresponding exception identification information when an exception occurs during the parsing of any configuration file element.

[0021] The determination module is used to query the local configuration file element rule template library based on the anomaly identification information to determine the repair solution corresponding to the configuration file element.

[0022] The repair module is used to perform compatibility repairs on the configuration file element using a repair solution, resulting in a repaired configuration file element.

[0023] The parsing module is also used to re-parse the repaired configuration file elements, and if the re-parsing is successful, write the repaired configuration file elements to the eSIM card's file system.

[0024] Thirdly, embodiments of this application provide a configuration file compatibility processing device, which has the function of implementing the configuration file compatibility processing method of the first aspect or any possible implementation thereof. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function.

[0025] Fourthly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a computer, enable the computer to perform the configuration file compatibility processing method described in the first aspect or any possible implementation thereof.

[0026] Fifthly, embodiments of this application provide a computer program product containing instructions that, when run on a computer, enable the computer to execute the configuration file compatibility processing method described in the first aspect or any possible implementation thereof.

[0027] The technical effects of any of the design methods in aspects two through five can be found in aspect one or in different possible implementations of aspect one, and will not be repeated here. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in the specific embodiments of this application or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0029] Figure 1 A schematic diagram of the structure of a terminal device provided in an embodiment of this application; Figure 2 A system architecture diagram of an eSIM remote configuration system provided in this application embodiment; Figure 3 A flowchart illustrating a configuration file compatibility processing method provided in this application embodiment; Figure 4 A specific example diagram of a configuration file compatibility processing method provided in this application embodiment; Figure 5 A specific example diagram of a configuration file compatibility processing method provided in this application embodiment; Figure 6 Another method flowchart for a configuration file compatibility processing method provided in this application embodiment; Figure 7 Another method flowchart of a configuration file compatibility processing method provided in this application embodiment; Figure 8 A schematic diagram of a configuration file compatibility processing device provided in this application embodiment; Figure 9 This is a system architecture diagram of a configuration file compatibility processing system provided in an embodiment of this application. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0031] Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0032] With the increasing adoption of eSIM in mobile terminals and IoT devices, profiles can be remotely generated and distributed to eSIM cards by different operators and DP+ platforms. Upon receiving the profile data packet, the eSIM card needs to perform decryption, security verification, parsing, and installation locally. Due to differences in the implementation details of the profile specification across different DP+ platforms, while some profile data packets may pass transport or security layer verification, some configuration file elements may deviate from the default configuration file specification.

[0033] In related technologies, the handling of the aforementioned deviation issues typically employs a strict specification verification method. This means that when the eSIM card parses the Profile data packet, if any field or configuration element does not meet the specification requirements, the Profile installation process is immediately terminated. While this method prevents obviously abnormal data from being written to the eSIM card file system, it is overly strict. For example, for anomalies that can be corrected through rule-based methods, such as missing fields, slightly abnormal field lengths, non-standard encoding, or non-critical fields causing process blockages, this method will still directly terminate the installation, preventing a properly functioning Profile from being installed successfully, thus reducing the Profile download success rate and cross-platform compatibility.

[0034] Based on this, embodiments of this application provide a configuration file compatibility processing method, apparatus, and device applied to an eSIM card. The method includes: after the configuration file data packet passes security verification, parsing each configuration file element in the configuration file data packet according to a preset configuration file specification. If an error occurs during the parsing of any configuration file element, suspending the write operation of that configuration file element and extracting the error identification information corresponding to that configuration file element. Querying a local configuration file element rule template library based on the error identification information to determine a repair scheme corresponding to that configuration file element. Using the repair scheme to perform compatibility repair on the configuration file element to obtain a repaired configuration file element. Re-parsing the repaired configuration file element, and if the re-parsing is successful, writing the repaired configuration file element to the file system of the eSIM card.

[0035] The configuration file compatibility processing method provided in this application provides a method that, after the configuration file data packet passes security verification, parses each configuration file element in the configuration file data packet one by one according to the preset configuration file specification. If an error occurs in the parsing of any configuration file element, the writing action of that configuration file element is suspended, and the error identification information corresponding to that configuration file element is extracted. This ensures that the abnormal configuration file element will not be written to the eSIM card's file system before compatibility repair and re-parsing are completed, thereby reducing the risk of abnormal configuration file elements affecting the eSIM card's file system.

[0036] Based on the anomaly identification information, the local profile element rule template library is queried to determine the corresponding repair solution for the profile element. This repair solution is then used to perform compatibility repair on the profile element, resulting in a repaired profile element. This allows the eSIM card to match corresponding repair solutions for different profile elements and different anomaly situations based on the rule template corresponding to the profile element, thereby achieving fine-grained compatibility processing of profile elements and improving profile compatibility. Finally, the repaired profile element is re-parsed, and if re-parsed successfully, the repaired profile element is written to the eSIM card's file system. This re-verification of the repaired profile element before writing improves the reliability of writing the profile element to the file system.

[0037] The methods provided in the embodiments of this application will now be described in conjunction with the specific accompanying drawings.

[0038] On the one hand, embodiments of this application provide a terminal device. For example... Figure 1 As shown, the terminal device 100 includes an eSIM card 101, and the eSIM card 101 includes a file system 102.

[0039] The terminal device 100 can be a mobile terminal, an Internet of Things device, or other electronic devices that support eSIM functionality.

[0040] The eSIM card 101 is used to receive configuration file data packets and, after receiving the configuration file data packets, to perform security verification on the configuration file data packets. The eSIM card 101 is also used to parse, repair, and write the configuration file data packets according to the configuration file compatibility processing method provided in this application embodiment after the security verification of the configuration file data packets passes.

[0041] The configuration file data package can be downloaded from different DP+ platforms to the eSIM card 101 in the terminal device 100 via remote subscription management. The configuration file data package may include multiple configuration file elements.

[0042] The file system 102 is used to store file data generated after the configuration file data package is installed. Specifically, when the eSIM card 101 parses the file system class configuration file element in the configuration file data package, it can create or update the corresponding file in the file system 102 according to the file identifier, file type, file attributes, access conditions and initial data carried in the configuration file element.

[0043] On the one hand, embodiments of this application provide an eSIM remote configuration system. For example... Figure 2 As shown, the eSIM remote configuration system 200 includes a terminal device 100, an eSIM subscription management platform 201, and an eSIM management platform 202.

[0044] The eSIM subscription management platform 201 generates a configuration file data package and distributes it to the terminal device 100 via a remote subscription management process. This configuration file data package includes multiple configuration file elements, which carry configuration data related to user identification, network access, file system, applications, security authentication, or remote management. For example, the eSIM subscription management platform 201 can be a DP+ platform.

[0045] The terminal device 100 is specifically used to receive the configuration file data packet issued by the eSIM subscription management platform 201, and to process the configuration file data packet locally to complete the download, parsing, and installation of the configuration file. The terminal device 100 is also used to repair the configuration file elements in the configuration file data packet based on the configuration file compatibility processing method provided in this application embodiment when there are compatibility issues, and to complete the installation when the repaired configuration file elements are successfully re-parsed.

[0046] The eSIM management platform 202 is used to manage the configuration file-related capabilities in the terminal device 100. For example, the eSIM management platform 202 can send rule update packages to the terminal device 100. The rule update package can include adding, modifying, or deleting rules, and each rule can include a version number and effective conditions. The terminal device 100 can perform integrity and legality checks on the rule update package, and after successful checks, update its local configuration file element rule template library according to the rule update package, so that the terminal device 100 can perform compatible processing of subsequent configuration file data packages based on the updated rule templates.

[0047] It should be noted that the eSIM subscription management platform 201 and eSIM management platform 202 mentioned above can be independent platforms, or they can be integrated into the same platform or server system according to actual deployment needs. This application embodiment does not limit this.

[0048] On the one hand, embodiments of this application provide a configuration file compatibility processing method, which can be provided by... Figure 1 The eSIM card 101 in the terminal device 100 shown can be used, or it can be executed by... Figure 2 The eSIM remote configuration system 200 shown is executed. For example... Figure 3 As shown, the method may include the following steps.

[0049] S301: After the security verification of the configuration file data packet passes, each configuration file element in the configuration file data packet is parsed one by one according to the preset configuration file specification.

[0050] The configuration file data package can be a Profile data package. The configuration file data package can be generated by the DP+ platform and distributed to the eSIM card through a remote subscription management process.

[0051] After receiving the configuration file data packet, the eSIM card first decrypts it and then performs a security verification. This security verification may include integrity verification. Upon receiving the configuration file data packet, the eSIM card can first perform an integrity verification on the message authentication code of the configuration file data packet to determine whether the configuration file data packet has been tampered with during transmission.

[0052] For example, the configuration file data packet may carry a message authentication code. After receiving the configuration file data packet, the eSIM card can extract the message authentication code from it and recalculate the message authentication code for the data to be verified in the configuration file data packet based on the security parameters corresponding to the current download session. The eSIM card compares the recalculated message authentication code with the message authentication code carried in the configuration file data packet. If the recalculated message authentication code matches the message authentication code carried in the configuration file data packet, it can be determined that the configuration file data packet has passed the integrity verification. If the recalculated message authentication code does not match the message authentication code carried in the configuration file data packet, it can be determined that the configuration file data packet may have been tampered with during transmission, and the installation process of the configuration file data packet will be terminated.

[0053] If the integrity verification of the configuration file data packet passes, the eSIM card can parse each configuration file element in the configuration file data packet one by one according to the preset configuration file specifications.

[0054] The preset configuration file specification can be the TCA specification.

[0055] The TCA specification defines the packaging and encoding format of eSIM configuration files. Various configuration data within the configuration file data package can be modularly organized according to configuration file elements. For example, configuration file elements can include header and control configuration file elements, file system configuration file elements, network access application configuration file elements, security and authentication configuration file elements, application configuration file elements, and extended and non-standard configuration file elements.

[0056] The header and control configuration file elements can include PE-Header and PE-End. PE-Header is the header of the configuration file, used to record profile version information, the minimum eUICC memory and feature requirements for parsing the profile. PE-End indicates the end of the profile package.

[0057] The File System configuration file element is used to create or write the corresponding file structure in the eSIM card 101. The File System configuration file element can include PE-MF, PE-CD, PE-TELECOM, and PE-GenericFileManagement. PE-MF is the main file and serves as the root directory of the file system. PE-CD and PE-TELECOM are standardized private directories. PE-GenericFileManagement is used to create generic file structures (DF, EF - basic files) and write initial data (such as SPN operator name, ICCID, etc.).

[0058] Network Access Applications (NAAs) configuration file elements are used to create applications that support network registration or communication services. These elements can include PE-USIM, PE-ISIM, and PE-CSIM. PE-USIM is used to create a general user identity module (for 3G / 4G / 5G network registration), and may contain key network data such as IMSI. PE-ISIM is used to create an IP Multimedia Service identity module (primarily for IMS-based voice and video calls such as VoLTE / VoNR). PE-CSIM is used to create CDMA applications (primarily for compatibility with older CDMA networks).

[0059] The Security & Authentication configuration file element stores the operator's encryption keys and security domain settings. This element can include PE-AKAParameter, PE-SecurityDomain, and PE-PINCodes. PE-AKAParameter contains parameters for the Authentication and Key Agreement (AKA) algorithm. It can carry the securely transmitted operator authentication key Ki and OPC (or OP) and be used to inject the corresponding authentication parameters into the eUICC during installation. PE-SecurityDomain is used to create security domains. In the Java Card system, security domains can be used to isolate different applications and manage OTA (Over-The-Air) update permissions, such as the Issuer Security Domain (ISD-P). PE-PINCodes defines the user's PIN code, PUK code, and their retries.

[0060] Applications configuration file elements are used to define, load, or instantiate corresponding applications. For example, an application class configuration file element can be a Java Card Applet class configuration file element. Operators can use this application class configuration file element to pre-install small programs (such as STK menus or special encryption programs for the Internet of Things) on the SIM card. Application class configuration file elements can include PE-Application, PE-Load, and PE-Instantiate. PE-Application is used to define a regular Java Card application. PE-Load can contain executable Java Card bytecode (CAP file data) used to load the Applet. PE-Instantiate is used to instantiate the loaded Applet, allocate memory, and initialize it.

[0061] Extensions and non-standard profile elements are used to configure vendor-specific data, remote file management parameters, or remote application management parameters. Extensions and non-standard profile elements can include PE-NonStandard, PE-RFM, and PE-RAM. PE-NonStandard allows operators or card manufacturers to insert non-standard, vendor-specific data or instructions. PE-RFM (Remote File Management) stores parameters for configuring remote file management, and PE-RAM (Remote Applet Management) stores parameters for remote application management. PE-RFM and PE-RAM ensure that even after the profile is installed, operators can still modify it via OTA.

[0062] Specifically, the eSIM card can sequentially read the configuration file elements to be parsed from the configuration file data packet according to the configuration file specification. For the currently read configuration file element, the eSIM card can parse the field structure in the configuration file element to determine the field information of each field in the currently read configuration file element. The field information may include one or more of the following: field label, field length, field value, field encoding format, field hierarchy, parent field label of the field, child field identifier of the field, and file attributes or access conditions of the field.

[0063] After determining the field information of each field in the currently read configuration file element, the eSIM card can determine whether the currently read configuration file element meets the configuration file specification based on the field information.

[0064] For example, the eSIM card can determine whether the field tags in the currently read configuration file element belong to the field tags allowed by the configuration file specification, whether the field length matches the actual data length of the field, whether the field encoding format conforms to the configuration file specification requirements, whether required fields are missing, and whether file attributes or access conditions conform to the configuration file specification requirements.

[0065] If the currently read configuration file element meets the configuration file specification, it can be determined that the parsing of the currently read configuration file element was successful. For successfully parsed configuration file elements, the eSIM card can continue to perform the installation process corresponding to that configuration file element according to the configuration file specification.

[0066] If it is determined that the currently read configuration file element does not meet the preset configuration file specification, it can be concluded that there is an error in parsing the currently read configuration file element.

[0067] S302, if an exception occurs during the parsing of any configuration file element, suspend the write operation of that configuration file element and extract the exception identifier information corresponding to that configuration file element.

[0068] During the process of parsing the configuration file elements in the configuration file data packet one by one by the eSIM card, if an error occurs in the parsing of any configuration file element, the eSIM card can suspend the writing operation of that configuration file element.

[0069] For example, the eSIM card can suspend the write operation of the configuration file element by pausing the instantiation of the data corresponding to the configuration file element into the eSIM card's file system. Alternatively, the eSIM card can keep the configuration file element in a cache area or a temporary processing area, awaiting subsequent rule matching and compatibility fixes.

[0070] After suspending the write operation of the configuration file element, the eSIM card extracts the abnormal identification information corresponding to the configuration file element.

[0071] This exception identification information can be used to characterize the location and type of the exception that occurred in the configuration file element. For example, the exception identification information may include one or more of the following: configuration file element identifier, parent field label, and error type. The configuration file element identifier uniquely identifies the configuration file element to which the exception occurred. The parent field label identifies the parent field to which the field that experienced the exception belongs.

[0072] Error types are used to indicate the type of exception for this configuration file element. For example, error types may include one or more of the following: missing field, abnormal field length, presence of non-standard encoding, process blockage caused by non-critical fields, abnormal access conditions or file attributes, and presence of negligible validation exceptions.

[0073] Among these, missing fields can be caused by a subfield required by the configuration file specification not appearing in the corresponding configuration file element. Abnormal field length can be caused by a mismatch between the defined field length and the actual data length. The presence of non-standard encoding can be caused by field data not using the encoding format required by the configuration file specification. Process blocking due to non-critical fields can be caused by redundant or unparseable fields in the configuration file element, which do not affect core functionality but block subsequent parsing. Abnormal access conditions or file attributes can be caused by file access conditions or file attributes corresponding to the configuration file element not conforming to the configuration file specification. Negligible validation anomalies can be validation anomalies that do not affect the core functionality corresponding to the configuration file element.

[0074] S303. Based on the anomaly identification information, query the local configuration file element rule template library to determine the repair solution corresponding to the configuration file element.

[0075] After extracting the anomaly identification information, the eSIM card can query the local configuration file element rule template library for a rule template that matches the anomaly based on the configuration file element identifier, parent field label, and error type in the anomaly identification information.

[0076] This local configuration file element rule template library can be pre-configured on the eSIM card. It stores rule templates corresponding to different configuration file elements. For each configuration file element defined in the TCA specification, a corresponding rule template can be pre-configured on the eSIM card or dynamically generated.

[0077] Specifically, each rule template can use structured data storage. A rule template may include one or more of the following: configuration file element identifiers, parent field definitions, processing schemes, hierarchical compatibility strategies, and security constraints.

[0078] The profile element identifier is used to uniquely identify the profile element currently being parsed. For example, the profile element identifier can be used to identify PE-USIM, PE-Header, or other profile elements.

[0079] The parent field definition is used to record the parent fields in the configuration file element that can be used as indexes for rule lookups. Specifically, when an anomaly occurs in a field of a configuration file element, the tag of the parent field to which that field belongs can be used as the parent field tag, and a matching processing rule can be found in the corresponding rule template based on the parent field tag.

[0080] The handling scheme records the repair or handling methods when a subfield under a parent field does not conform to the configuration file specifications. The handling scheme can be represented in TLV format. For example, 01 indicates that a default value is added when a field is missing, and its value carries the subfield ID and the default value. 02 indicates that the TLV length is abnormal, and a value of zero indicates automatic truncation or padding. 03 indicates that non-standard encoding is converted to standard format, and the value is zero. 04 indicates that non-critical fields are deleted or ignored, and the value is a list of subfield IDs to be deleted. 05 indicates that file attributes or access conditions are adjusted, and the value is the subfield ID and the default value. 06 indicates that error checking is ignored, and a value of zero means that the exception is skipped and the process continues.

[0081] Tiered compatibility policies define the handling levels for different anomalies. For example, a tiered compatibility policy can include Level 1, Level 2, Level 3, and Level 4 policies. Level 1 corresponds to full compliance, meaning that configuration file element fields are processed successfully according to standard procedures without triggering rule templates. Level 2 corresponds to minor anomalies and applies automatic repair processing. This level 2 policy can refer to format checks that do not affect functionality, such as handling schemes 01-04. Level 3 corresponds to moderate anomalies and applies limited repair processing, such as handling scheme 05. This level 3 policy can also be used to repair file attribute errors based on file type, without affecting functionality. Level 4 corresponds to severe anomalies, for which compatibility repair is not applicable, and the eSIM card terminates the Profile data package installation process.

[0082] Security constraints are used to record security control fields that are not suitable for compatibility repair. Security constraints can include a set of security constraint fields, which may record authentication key-related fields or other security-sensitive fields, such as the authentication key AKAParameter and other highly sensitive fields. When an abnormal field in a profile element matches the set of security constraint fields, the eSIM card will not perform compatibility repair on that field, but will instead terminate the Profile data packet installation process.

[0083] For example, such as Figure 4 and Figure 5As shown, taking the rule template corresponding to PE-USIM as an example, the rule template is: {0Xa1 (PE identification information, 0Xa1 represents the tag of PEUSIM, different PEs have different tag values), 0Xa13062 (field definition, a1 represents fileManagementCMD, 30 represents SEQUENCE OF, 62 represents createFCP), 020004018A (processing scheme, 0200 means if the tlv length under the parent field does not match, then modify the field length to the correct value; 04018A means that the lcsi field under createFCP is directly deleted or modified to the default value); 0x83 (security constraint, 0x83 represents the FileID field under createFCP, if this field check reports an error, then directly report an error, and the processing scheme is not supported)}.

[0084] The rule template includes the configuration file element identifier (0Xa1) corresponding to PE-USIM, the parent field definition (0Xa13062) corresponding to the fileManagementCMD field or createFCP field in PE-USIM, the handling scheme for TLV length exceptions or non-critical field exceptions (020004018A), and the security constraint (0x83) used to restrict the FileID field from being applicable to compatibility repair.

[0085] For example, when the eSIM card is parsing the PE-USIM, if an abnormal TLV length is detected under the createFCP field, the field length can be corrected according to the processing solution (0200) in the rule template, and the field length can be modified to the correct value; if a non-critical field (such as the lcsi field) that causes process blocking is detected under the createFCP field, the lcsi field can be deleted or the non-critical field can be blocked according to the processing solution (04018A) in the rule template; if an abnormality is detected in the FileID field and the field hits the security constraint (0x83), the installation process of the Profile data packet is terminated.

[0086] It should be noted that the above rule template is only an example of the local configuration file Yuan is a rule template library in the embodiments of this application, and is not a limitation.

[0087] Based on the rule templates described above, the eSIM card can determine the candidate rule template corresponding to the configuration file element from the local configuration file element rule template library according to the configuration file element identifier. The candidate rule template can be a rule template corresponding to the type of configuration file element that has encountered an anomaly. For example, if the configuration file element that encountered the anomaly is PE-USIM, the eSIM card can determine the candidate rule template corresponding to PE-USIM from the local configuration file element rule template library.

[0088] After determining the candidate rule templates, the eSIM card can identify the target rule template corresponding to the parent field label from the candidate rule templates. The parent field label can indicate the field hierarchy or position of the field that caused the exception within the configuration file element. For example, when the exception field is located in the createFCP field under the fileManagementCMD field in PE-USIM, the eSIM card can determine the target rule template from the candidate rule templates corresponding to PE-USIM based on the labels corresponding to the fileManagementCMD field and the createFCP field.

[0089] After determining the target rule template, the eSIM card can determine the corresponding repair strategy and repair method for the configuration file element based on the error type. The repair strategy indicates whether the configuration file element is suitable for compatibility repair, and if so, the corresponding compatibility handling level. The repair method indicates the specific processing action to be performed on the fields in the configuration file element where an exception occurred.

[0090] For example, if the error type is field missing and the processing scheme in the target rule template is 01, the eSIM card can determine that the repair strategy is an automatic repair strategy and the repair method is to supplement the missing sub-fields according to the sub-field ID and default value carried in the processing scheme.

[0091] When the error type is TLV length abnormality and the processing scheme in the target rule template is 02, the eSIM card can determine that the repair strategy is the automatic repair strategy and the repair method is to truncate or pad the field length.

[0092] When the error type is non-standard encoding and the processing scheme in the target rule template is 03, the eSIM card can determine that the repair method is to convert the abnormal field data into a standard encoding format.

[0093] If the error type is a non-critical field causing process blockage, and the processing solution in the target rule template is 04, the eSIM card can determine that the repair method is to delete or block the corresponding non-critical field.

[0094] If the error type is abnormal access condition or abnormal file attribute, and the processing solution in the target rule template is 05, the eSIM card can determine that the repair policy is a restricted repair policy and the repair method is to adjust the corresponding access condition or file attribute.

[0095] If the error type is an ignorable verification exception and the processing solution in the target rule template is 06, the eSIM card can determine that the repair method is to skip the ignorable verification exception.

[0096] After determining the repair strategy and repair method, the eSIM card can determine the repair scheme corresponding to the configuration file element based on the repair strategy and repair method. The repair scheme can include the repair strategy and repair method.

[0097] For example, the remediation scheme may include subfield identifiers and default values ​​for supplementing missing subfields, a list of subfield identifiers for deleting or masking non-critical fields, subfield identifiers and default values ​​for adjusting access conditions or file attributes, encoding conversion methods for encoding conversion, field length correction rules for length correction, or processing identifiers for skipping negligible validation exceptions.

[0098] Furthermore, if no candidate rule template corresponding to the configuration file element is found, or no target rule template matching the parent field label is found, the eSIM card can determine that the exception corresponding to the configuration file element is a serious exception and terminate the installation process of the configuration file data package.

[0099] It should be noted that terminating the installation process of the configuration file data package can mean stopping the parsing and installation of the configuration file data package, or it can mean rolling back the installation operations that have already been performed on the configuration file data package.

[0100] Rollback processing can restore the eSIM card to its state before the configuration file data package was installed. Specifically, if some configuration file elements in the configuration file data package have already been written to the eSIM card's file system, and subsequent configuration file elements are determined to be seriously abnormal, the eSIM card can delete files, directories, application data, security domain data, or management parameters created during the installation process, or restore file attributes, access conditions, initial data, or installation state modified during the installation process to their state before installation.

[0101] For example, if the eSIM card has already created the corresponding file structure in the file system based on PE-MF, PE-CD, PE-TELECOM, or PE-GenericFileManagement, the rollback process may include deleting the newly created file structure during this installation, or restoring the file attributes and access conditions modified during this installation. If the eSIM card has already written network access application data, security authentication data, or application instantiation data, the rollback process may include reversing the data newly written during this installation and clearing the temporary cache, error flags, and intermediate installation states corresponding to the current configuration file data packet.

[0102] S304. Use the repair solution to perform compatibility repair on the configuration file element to obtain the repaired configuration file element.

[0103] After determining the repair scheme corresponding to the configuration file element, the eSIM card can use the repair scheme to perform compatibility repair on the configuration file element, resulting in a repaired configuration file element. The repair scheme can include repair strategies and repair methods.

[0104] Specifically, the eSIM card can determine whether a profile element is suitable for compatibility repair based on the repair policy. If it is determined that the profile element is not suitable for compatibility repair, the eSIM card can terminate the profile data package installation process. If it is determined that the profile element is suitable for compatibility repair, the eSIM card can perform the corresponding compatibility repair processing on the profile element according to the repair policy and repair method.

[0105] One possible implementation is that, if it is determined that the configuration file element is suitable for compatibility repair and the repair strategy is automatic repair, the eSIM card can repair the abnormal fields in the configuration file element according to the repair method, resulting in a repaired configuration file element. The automatic repair strategy can be applied to minor anomalies. Minor anomalies refer to format-related anomalies that do not affect the functionality of the configuration file element, such as missing fields, abnormal field lengths, non-standard encoding, or non-critical fields causing process blockages.

[0106] Another possible implementation is that, if the error type of the configuration file element is determined to be a missing field, the eSIM card can supplement the missing sub-field in the configuration file element based on the sub-field identifier and default value in the repair scheme. Specifically, the eSIM card can locate the parent field corresponding to the missing sub-field in the cached data of the configuration file element, and insert the sub-field identifier and default value under the parent field to make the field structure of the configuration file element conform to the configuration file specification.

[0107] Another possible implementation is that, if the error type of the configuration file element is determined to be an abnormal field length, the eSIM card can truncate the extra data bytes in the configuration file element or pad the end of the configuration file element with preset data to ensure that the field length meets the configuration file specification. For example, if the defined field length is greater than the actual data length, 0x00, 0xFF, or other padding data specified in the rule template can be added to the end of the field. If the defined field length is less than the actual data length, data bytes exceeding the defined field length can be truncated.

[0108] Another possible implementation involves, if the error type of the configuration file element is determined to be the presence of non-standard encoding, the eSIM card can convert the abnormal field data containing the non-standard encoding in the configuration file element into a standard encoding format. For example, if the field data uses ASCII encoding, BCD encoding, or endianness that does not conform to the configuration file specification, the eSIM card can convert the abnormal field data into the standard encoding format required by the TCA or 3GPP specifications according to the encoding conversion method indicated in the remediation plan.

[0109] Another possible implementation is that, if the error type of the configuration file element is determined to be caused by a non-critical field blocking the process, the eSIM card can delete or disable the non-critical field in the configuration file element based on the sub-field identifier list in the repair plan. Deleting the non-critical field can be done by removing the corresponding sub-field from the cached data of the current configuration file element. Disabling the non-critical field can be done by marking the corresponding sub-field as not participating in subsequent parsing processes during the parsing process. This non-critical field can be a field that does not affect the core functionality of the configuration file element but causes the current parsing process to block.

[0110] Another possible implementation involves, if it is determined that the configuration file element is suitable for compatibility repair and the repair strategy is a restricted repair strategy, the eSIM card can repair the file attributes or access conditions in the configuration file element according to the repair method, resulting in a repaired configuration file element. The restricted repair strategy can be applied to moderate anomalies. Moderate anomalies can include file attribute anomalies or access condition anomalies.

[0111] Another possible implementation is that, if the error type of the configuration file element is determined to be an access condition anomaly or a file attribute anomaly, the eSIM card can adjust the access conditions or file attributes corresponding to the configuration file element based on the sub-field identifiers and default values ​​in the repair plan. Specifically, the eSIM card can locate the field in the configuration file element that represents the access condition or file attribute, and adjust the value of that field to the default value or standard value recorded in the repair plan, so that the adjusted access conditions or file attributes meet the configuration file specifications.

[0112] Another possible implementation is that, if the error type of the configuration file element is determined to be a negligible verification exception, the eSIM card can skip the negligible verification exception. Skipping the negligible verification exception can be achieved by clearing the error flag corresponding to the current parent or child field, or by not blocking the parsing process of the configuration file element based on the negligible verification exception in subsequent parsing processes.

[0113] After the above compatibility repair process is completed on the configuration file element, the eSIM card can obtain the repaired configuration file element. The repaired configuration file element can be a configuration file element based on the cached data of the original configuration file element, with field supplementation, field length correction, encoding conversion, deletion or masking of non-critical fields, file attribute adjustment, access condition adjustment, or error flag clearing.

[0114] S305 re-parses the repaired configuration file elements, and if the re-parse is successful, writes the repaired configuration file elements to the eSIM card's file system.

[0115] After obtaining the repaired configuration file elements, the eSIM card can re-parse the repaired configuration file elements according to the preset configuration file specifications.

[0116] It should be noted that the process of re-parses the repaired configuration file elements is the same as the process of parsing each configuration file element in the configuration file data packet according to the preset configuration file specification in the aforementioned S301, and this application will not elaborate on this.

[0117] One possible implementation is that, if re-parsing is successful, it can be determined that the repaired configuration file elements meet the configuration file specification. At this point, the eSIM card can write the repaired configuration file elements to the eSIM card's file system.

[0118] Another possible implementation is to determine if the repaired configuration file element still does not meet the configuration file specification if re-parsing fails. In this case, the eSIM card can determine that the exception corresponding to the configuration file element is a critical exception and terminate the configuration file data package installation process.

[0119] Through the above process, the eSIM card can complete rule matching, compatibility repair, re-parsing, and writing of abnormal profile elements locally, so that the flexible correction capability of the Profile format is set locally on the eSIM card, improving the compatibility and reliability of the profile data package installation process.

[0120] Furthermore, the method provided in this application embodiment may also include a security constraint determination process. This security constraint determination process may include steps S306-S308. For example... Figure 6 As shown, S306-S308 can be executed before S303.

[0121] S306, Based on the anomaly identification information, determine whether the field in the configuration file element that caused the anomaly hits the preset security constraint.

[0122] Specifically, the eSIM card can determine whether the field in the configuration file element that caused the anomaly matches a preset security constraint based on the anomaly identifier information. The security constraint can include a set of security constraint fields. This set of security constraint fields is used to record security control fields that are not applicable for compatibility fixes.

[0123] For example, security control fields may include authentication key-related fields or other security-sensitive fields. The authentication key-related fields may include key authentication parameter fields in PE-AKAParameter. Security control fields may also include fields configured in the rule template as not applicable to compatibility fixes, such as the FileID field in the PE-USIM corresponding rule template.

[0124] S307, If an abnormal field hits the security constraint, terminate the installation process of the configuration file data package.

[0125] Specifically, if an abnormal field hits a security constraint, the eSIM card can terminate the installation process of the configuration file data package. In this case, the eSIM card will not perform compatibility repair on the field, nor will it replace, delete, complete, or skip the processing of the field based on the processing solution.

[0126] S308, if an abnormal field does not match the security constraint, execute the step of querying the local configuration file element rule template library based on the abnormal identification information to determine the repair solution corresponding to the configuration file element.

[0127] Specifically, when an anomaly occurs and a security constraint is not matched, the eSIM card can query the local configuration file element rule template library based on the anomaly identifier information to determine the rule template corresponding to the configuration file element. By setting a security constraint judgment process before querying the rule template, compatibility repair can be limited to fields allowed by the security constraints.

[0128] Furthermore, the method provided in this application embodiment may also include an update process for a local configuration file element rule template library. For example... Figure 7 As shown, the method may include S309-S311.

[0129] S309 receives rule update packages issued by the eSIM management platform.

[0130] Specifically, the eSIM card can receive rule update packages from the eSIM management platform. Rule update packages can include one or more of the following: adding, modifying, or deleting rules. Each rule can include a version number and effective conditions. The version number identifies the rule's version. Effective conditions can be used to limit the configuration file elements, parent field tags, error types, or other applicable conditions to which the rule applies.

[0131] S310 performs integrity and legality checks on the rule update package.

[0132] Specifically, upon receiving a rule update packet, the eSIM card can perform integrity and validity checks on the packet. For example, digital signatures can be used for verification.

[0133] S311 After verification, the local configuration file element rule template library is updated according to the rule update package.

[0134] Specifically, after successful verification, the eSIM card can update its local configuration file element rule template library based on the rule update package. For example, for a new rule in the rule update package, the eSIM card can add the new rule to the local configuration file element rule template library. For a modified rule in the rule update package, the eSIM card can update existing rules in the local configuration file element rule template library based on the modified rule. For a deleted rule in the rule update package, the eSIM card can delete the corresponding rule from the local configuration file element rule template library or set the corresponding rule to an invalid state.

[0135] In the event of a power outage or an anomaly during the rule update process, the eSIM card can roll back to the previous stable version of the rule template library based on the backup mechanism.

[0136] The above primarily describes the solutions provided in the embodiments of this application from the perspective of the working principle of the device. It is understood that, in order to achieve the above functions, the configuration file compatible processing device includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0137] This application embodiment can divide the configuration file compatible processing device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module.

[0138] It should be noted that the module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. When dividing functional modules according to their respective functions, Figure 8 A schematic diagram of a possible configuration file compatibility processing device involved in the above and embodiments is shown. Figure 8 As shown, the configuration file compatibility processing device 800 may include: a parsing module 801, an extraction module 802, a determination module 803, and a repair module 804.

[0139] The parsing module 801 is used to support the execution of the configuration file compatibility processing device 800. Figure 3 S301 and S305 in the illustrative configuration file compatibility handling method.

[0140] Extraction module 802 is used to support the execution of configuration file compatible processing device 800. Figure 3 S302 in the schematic configuration file compatibility handling method.

[0141] Determine module 803, used to support the execution of configuration file compatible processing device 800. Figure 3 S303 in the schematic configuration file compatibility handling method.

[0142] Repair module 804 is used to support the execution of configuration file compatibility processing device 800. Figure 3 S304 in the schematic configuration file compatibility handling method.

[0143] One possible implementation involves a parsing module. When parsing each configuration file element in the configuration file data packet according to a preset configuration file specification, the module specifically performs the following: It reads the configuration file elements to be parsed sequentially from the configuration file data packet according to the specification. It then parses the field structure of the currently read configuration file element to determine the field information of each field. Based on the field information, it determines whether the currently read configuration file element meets the configuration file specification. If it is determined that the currently read configuration file element does not meet the preset configuration file specification, it indicates that an anomaly has occurred in the parsing of the currently read configuration file element.

[0144] One possible implementation is that the exception identification information includes one or more of the following: configuration file element identifier, parent field label, and error type. The determination module, used to query the local configuration file element rule template library based on the exception identification information, specifically determines the repair solution corresponding to the configuration file element by: determining candidate rule templates corresponding to the configuration file element from the local configuration file element rule template library based on the configuration file element identifier; determining the target rule template corresponding to the parent field label from the candidate rule templates based on the parent field label; determining the repair strategy and repair method corresponding to the configuration file element from the target rule template based on the error type; and determining the repair solution corresponding to the configuration file element based on the repair strategy and repair method.

[0145] In one possible implementation, the configuration file compatibility processing device provided in this application embodiment is further configured to: determine that the exception corresponding to the configuration file element is a serious exception and terminate the installation process of the configuration file data package when no candidate rule template corresponding to the configuration file element or a target rule template matching the parent field label is found.

[0146] One possible implementation involves a repair scheme that includes a repair strategy and a repair method. The repair module, used to perform compatibility repair on the configuration file element using the repair scheme, specifically performs the following steps when obtaining the repaired configuration file element: Based on the repair strategy, it determines whether the configuration file element is suitable for compatibility repair. If it is determined that the configuration file element is suitable for compatibility repair, and the repair strategy is an automatic repair strategy, it repairs the abnormal fields in the configuration file element according to the repair method, obtaining the repaired configuration file element. If it is determined that the configuration file element is not suitable for compatibility repair, the installation process of the configuration file data package is terminated.

[0147] One possible implementation involves a repair module, used to repair abnormal fields in the configuration file element according to a repair plan. Specifically, when the repaired configuration file element is obtained, it performs the following: If the error type of the configuration file element is determined to be a missing field, it adds the missing sub-field to the configuration file element based on the sub-field identifiers and default values ​​in the repair plan. If the error type of the configuration file element is determined to be an abnormal field length, it truncates redundant data bytes in the configuration file element or adds preset data to the end of the configuration file element to ensure the field length meets the configuration file specification. If the error type of the configuration file element is determined to be the presence of non-standard encoding, it converts the abnormal field data containing the non-standard encoding in the configuration file element to a standard encoding format. If the error type of the configuration file element is determined to be a process blockage caused by a non-critical field, it deletes or masks the non-critical field in the configuration file element based on the sub-field identifier list in the repair plan.

[0148] One possible implementation is a repair module, which is used to repair the file attributes or access conditions in the configuration file element according to the repair method. When the repaired configuration file element is obtained, it is specifically used to: if it is determined that the error type of the configuration file element is an abnormal access condition or an abnormal file attribute, adjust the access conditions or file attributes corresponding to the configuration file element according to the sub-field identifier and default value in the repair scheme.

[0149] In one possible implementation, the configuration file compatibility processing device provided in this application embodiment is further configured to: skip the negligible verification exception when it is determined that the error type of the configuration file element is a negligible verification exception.

[0150] In one possible implementation, before querying the local configuration file element rule template library based on the anomaly identification information to determine the repair scheme corresponding to the configuration file element, the configuration file compatibility processing device provided in this application embodiment is further configured to: determine, based on the anomaly identification information, whether the field in the configuration file element that is experiencing an anomaly hits a preset security constraint. The security constraint includes a set of security constraint fields. The set of security constraint fields is used to record security control fields that are not applicable to compatibility repair. If the field experiencing an anomaly hits a security constraint, the installation process of the configuration file data package is terminated. If the field experiencing an anomaly does not hit a security constraint, the step of querying the local configuration file element rule template library based on the anomaly identification information to determine the repair scheme corresponding to the configuration file element is executed.

[0151] In one possible implementation, the configuration file compatibility processing apparatus provided in this application embodiment is further configured to: receive a rule update package issued by the eSIM management platform. The rule update package includes one or more of the following: added rules, modified rules, or deleted rules. Each rule includes a version number and effective conditions. The rule update package is subjected to integrity and legality verification. After successful verification, the local configuration file element rule template library is updated according to the rule update package.

[0152] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0153] The configuration file compatibility processing device 800 provided in this application embodiment is used to execute the above-described configuration file compatibility processing device. Figure 3-7 The configuration file compatibility handling method shown can achieve the same effect as the configuration file compatibility handling method described above.

[0154] This application also provides a configuration file compatibility processing device, which can execute the configuration file compatibility processing method and related steps in the above method embodiments.

[0155] This application also provides a computer-readable storage medium storing instructions thereon, which, when executed, perform the configuration file compatibility processing method and related steps in the above method embodiments.

[0156] This application also provides a computer program product that, when run on a computer, causes the computer to execute the configuration file compatibility processing method and related steps described in the above method embodiments.

[0157] In some embodiments, the methods shown in this application can be implemented as computer program instructions encoded in a machine-readable format on a computer-readable storage medium or on other non-transitory media or articles of art.

[0158] This application also provides a configuration file compatibility processing system 900, such as... Figure 9 As shown, the configuration file compatible processing system 900 includes at least one processor 901 and at least one interface circuit 902.

[0159] As an example, when the configuration file is compatible with the processing system 900, which includes a processor and an interface circuit, then the processor can be... Figure 9 The processor 901 shown in the solid box (or the processor 901 shown in the dashed box) can be an interface circuit. Figure 9The interface circuit 902 is shown in the solid box (or the dashed box). When the configuration file compatible processing system 900 includes two processors and two interface circuits, the two processors include... Figure 9 The processor 901 shown in the solid box and the processor 901 shown in the dashed box, these two interface circuits include Figure 9 Interface circuit 902 is shown in both solid and dashed boxes. No limitations are imposed on this.

[0160] Processor 901 and interface circuit 902 can be interconnected via a line. For example, interface circuit 902 can be used to receive signals. Alternatively, interface circuit 902 can be used to send signals to other devices (e.g., processor 901). For instance, interface circuit 902 can read computer instructions stored in memory and send those instructions to processor 901. Processor 901 executes the instructions and, in conjunction with input / output devices, implements the various steps in the above embodiments, such as implementing... Figures 3-7 The methods illustrated are the steps performed in the embodiments shown. Of course, this configuration file compatibility processing system may also include other discrete components, and this application embodiment does not specifically limit this.

[0161] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0162] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0163] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0164] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0165] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0166] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions 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.

Claims

1. A configuration file compatibility processing method, characterized in that, Applied to an eSIM card, the method includes: After the security verification of the configuration file data packet passes, each configuration file element in the configuration file data packet is parsed one by one according to the preset configuration file specification; If an error occurs during the parsing of any of the configuration file elements, the write operation of that configuration file element is suspended, and the error identification information corresponding to that configuration file element is extracted. Based on the anomaly identification information, query the local configuration file element rule template library to determine the repair solution corresponding to the configuration file element; The aforementioned repair scheme is used to perform compatibility repair on the configuration file element, resulting in a repaired configuration file element. The repaired configuration file elements are re-parsed, and if the re-parse is successful, the repaired configuration file elements are written to the file system of the eSIM card.

2. The method according to claim 1, characterized in that, The step of parsing each configuration file element in the configuration file data packet according to the preset configuration file specification includes: According to the configuration file specification, read the configuration file elements to be parsed sequentially from the configuration file data packet; The field structure of the currently read configuration file element is parsed to determine the field information of each field in the currently read configuration file element; Based on the field information, determine whether the currently read configuration file element meets the configuration file specification; If it is determined that the currently read configuration file element does not meet the preset configuration file specification, it is determined that the parsing of the currently read configuration file element has failed.

3. The method according to claim 1, characterized in that, The exception identification information includes one or more of the following: configuration file element identifier, parent field label, and error type; The step of querying the local configuration file element rule template library based on the anomaly identification information to determine the repair solution corresponding to the configuration file element includes: Based on the configuration file element identifier, determine the candidate rule template corresponding to the configuration file element from the local configuration file element rule template library; Based on the parent field label, determine the target rule template corresponding to the parent field label from the candidate rule templates; Based on the error type, determine the repair strategy and repair method corresponding to the configuration file element from the target rule template; Based on the repair strategy and the repair method, determine the repair scheme corresponding to the modified configuration file element.

4. The method according to claim 3, characterized in that, The method further includes: If no candidate rule template corresponding to the configuration file element is found, or no target rule template matching the parent field label is found, the exception corresponding to the configuration file element is determined to be a serious exception, and the installation process of the configuration file data package is terminated.

5. The method according to claim 1, characterized in that, The repair scheme includes a repair strategy and a repair method; the process of using the repair scheme to perform compatibility repair on the configuration file element to obtain the repaired configuration file element includes: Based on the repair strategy, determine whether the configuration file element is suitable for the compatibility repair; If it is determined that the configuration file element is suitable for the compatibility repair and the repair strategy is an automatic repair strategy, the abnormal fields in the configuration file element are repaired according to the repair method to obtain the repaired configuration file element. If it is determined that the configuration file element is suitable for the compatibility repair and the repair strategy is a restricted repair strategy, the file attributes or access conditions in the configuration file element are repaired according to the repair method to obtain the repaired configuration file element. If it is determined that the compatibility fix is ​​not applicable to the configuration file element, the installation process of the configuration file data package is terminated.

6. The method according to claim 5, characterized in that, The abnormal fields in the configuration file element are repaired according to the repair method to obtain the repaired configuration file element, including: If the error type of the configuration file element is determined to be a missing field, the missing sub-field is added to the configuration file element according to the sub-field identifier and default value in the repair scheme. If the error type of the configuration file element is determined to be an abnormal field length, the extra data bytes in the configuration file element are truncated, or preset data is added to the end of the configuration file element to make the field length meet the configuration file specification. If the error type of the configuration file element is determined to be the presence of non-standard encoding, the exception field data containing the non-standard encoding in the configuration file element is converted to the standard encoding format; If the error type of the configuration file element is determined to be a process blockage caused by the presence of a non-critical field, the non-critical field is deleted or masked in the configuration file element according to the sub-field identifier list in the repair scheme.

7. The method according to claim 5, characterized in that, The file attributes or access conditions in the configuration file element are repaired according to the repair method to obtain the repaired configuration file element, including: If the error type of the configuration file element is determined to be an abnormal access condition or an abnormal file attribute, the access condition or file attribute corresponding to the configuration file element shall be adjusted according to the sub-field identifier and default value in the repair scheme.

8. The method according to claim 5, characterized in that, The method further includes: If the error type of the configuration file element is determined to be an ignorable validation exception, then skip the ignorable validation exception.

9. The method according to claim 1, characterized in that, Before querying the local configuration file element rule template library based on the anomaly identifier information to determine the repair scheme corresponding to the configuration file element, the method further includes: Based on the anomaly identification information, determine whether the field in the configuration file element that caused the anomaly hits a preset security constraint; the security constraint includes a set of security constraint fields; the set of security constraint fields is used to record security control fields that are not applicable to compatibility repair. If an abnormal field hits the security constraint, the installation process of the configuration file data package is terminated. If an abnormal field fails to match the security constraint, the step of querying the local configuration file element rule template library based on the abnormal identification information to determine the repair solution corresponding to the configuration file element is executed.

10. The method according to claim 1, characterized in that, The method further includes: Receive rule update packages issued by the eSIM management platform; the rule update package includes one or more of the following: adding rules, modifying rules, or deleting rules; each rule includes a version number and effective conditions; The rule update package is subjected to integrity and legality checks. After successful verification, the local configuration file element rule template library is updated according to the rule update package.

11. A configuration file compatible processing device, characterized in that, Applied to an eSIM card, the device includes: The parsing module is used to parse each configuration file element in the configuration file data packet one by one according to the preset configuration file specification after the security verification of the configuration file data packet has passed. The extraction module is used to suspend the writing action of any configuration file element and extract the corresponding exception identification information when an exception occurs during the parsing of any of the configuration file elements. The determination module is used to query the local configuration file element rule template library based on the anomaly identification information and determine the repair scheme corresponding to the configuration file element. The repair module is used to perform compatibility repair on the configuration file element using the repair scheme, and obtain the repaired configuration file element. The parsing module is also used to re-parse the repaired configuration file elements, and if the re-parsing is successful, write the repaired configuration file elements into the file system of the eSIM card.

12. A configuration file compatible processing device, characterized in that, The configuration file compatibility processing device includes a processor and a memory, the memory storing machine-executable instructions that can be executed by the processor, and the processor executing the machine-executable instructions to implement the configuration file compatibility processing method according to any one of claims 1 to 10.

Images