Card locking data processing method, device and system and storage medium

Abstract

The invention provides a card locking data processing method, device and system and a storage medium, and relates to the technical field of terminals. The method comprises the steps that at least two kinds of card locking requirement configuration information of target software are obtained, the card locking types of the at least two kinds of card locking requirement configuration information are different, and the card locking types comprise a network lock, a sub-network lock, a service provider lock, a group lock and a user lock; the at least two kinds of card locking demand configuration information are used for jointly indicating a service range after card locking verification; and writing the target software and the at least two kinds of card locking demand configuration information into a specified position of the terminal. The scheme can be compatible with the card locking demand configuration information of at least two different card locking types, is used for indicating the service range after card locking verification, and can improve the flexibility and expandability of card locking limitation.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a method, device, system and storage medium for processing card lock data. Background Art

[0002] In the process of terminal technology advancement, in order to ensure the interests of operators are protected, terminal devices will be pre-loaded with card lock data when leaving the factory to impose restrictions on the device or its software at the national, network and other levels.

[0003] However, the existing technology often adopts a one-to-one deployment method when deploying card lock data, that is, each project that requires card lock corresponds to only one card lock information. In this case, when it is necessary to meet multiple card lock requirements, the flexibility and scalability of the existing solution are insufficient and it is difficult to adapt to the rapidly changing market needs. In the context of increasingly fierce market competition, the existing card lock technology is difficult to fully protect the interests of operators.

[0004] In view of this, how to improve the flexibility and scalability of lock card configuration has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] The present application provides a method, device, system and storage medium for processing lock card data, which can improve the efficiency and flexibility of lock card use and simplify the process of software development and system integration.

[0006] In a first aspect, a method for processing card lock data is provided, the method comprising: obtaining at least two types of card lock requirement configuration information of a target software, the card lock types of the at least two types of card lock requirement configuration information being different, the card lock types comprising: network lock, sub-network lock, service provider lock, group lock and user lock, the at least two types of card lock requirement configuration information being used to jointly indicate a service scope after the card lock is verified; writing the target software and the at least two types of card lock requirement configuration information into a designated location of a terminal.

[0007] Through the technical solution of the embodiment of the present application, firstly, by storing the card lock requirement in the form of configuration information, the card lock requirement can be configured separately, avoiding possible repeated custom development work. Secondly, the technical solution can achieve compatibility of at least two card lock requirements for one target software, broadening the scope of software restrictions at multiple levels, thereby meeting the urgent needs of operators for the flexibility and scalability of card lock software.

[0008] In some possible implementations, the card lock types of at least two types of card lock requirement configuration information are determined by network code information.

[0009] In some examples, the network code information includes: at least one of: a mobile country code, a mobile network code, a home location register information, and extended information, wherein the mobile country code is used to identify the country range used; the mobile network code is used to identify the mobile network used; the home location register information is used to identify the location information; and the extended information is used to identify the service information, group information, or the mobile user identification number.

[0010] Through the above implementation, the card lock type information can be specifically limited. Through the combination of these different network code information, the card lock range can be finely controlled to meet the complex and changing market needs and effectively improve the flexibility and security of the card lock solution.

[0011] In some possible implementations, at least two types of card lock requirement configuration information include first card lock type requirement configuration information and second card lock type requirement configuration information, the first card lock type requirement configuration information includes first network code information, the second card lock type requirement configuration information includes second network code information, and the first network code information and the second network code information are used to jointly indicate the service scope after the card lock is verified.

[0012] Through the above implementation, after the card lock verification, the use scope of the device can be flexibly indicated in more detail through the information of at least two card lock types. This solution enhances the flexibility and accuracy of the card lock function, so that the card lock verification can meet the diverse market needs and provide more detailed service restrictions.

[0013] In some examples, the second network code information includes the first network code information, and when the terminal satisfies the second network code information, the second network code information is used to indicate that all communication services of the open target software are; when the terminal satisfies the first network code information but does not satisfy the second network code information, the first network code information and the second network code information are used to indicate that some communication services of the open target software are; when the terminal does not satisfy the first network code information, the first network code information is used to indicate that the communication services of the target software are not open.

[0014] In these examples, the second network code information includes the first network code information, that is, the second network code information is a further limitation of the first network code information. In these examples, by comparing the terminal situation with the ranges limited by the two types of card locks during card lock verification, different service ranges can be provided, making the card lock service provision more flexible.

[0015] In other examples, the first network code information and the second network code information include a first part and a second part, the first part is a mobile country code and a mobile network code, the first network code information is different from the second part of the second network code information, and when the terminal satisfies the first network code information and the second network code information, the first network code information and the second network code information are used to indicate all communication services of the open target software.

[0016] In these examples, the first network code information and the second network code information are different except for the mobile country code and the mobile network code, that is, the first network code information and the second network code information do not have further restrictions. In these examples, when both network code information are satisfied, all communication services of the target software can be opened. In this way, a more stringent restriction range for the card locking conditions can be provided, and a more secure service can be provided for scenarios with a high confidentiality level.

[0017] In some possible implementations, the target software and at least two types of card lock requirement configuration information are written into a specified location of the terminal, including: generating corresponding at least two types of target information based on at least two types of card lock requirement configuration information, the card lock requirement configuration information is in XML format, and the target information is in binary data bin format; writing the target software and at least two types of target information into a specified location of the terminal.

[0018] Through the above implementation, the card lock requirement configuration information is converted into a binary data format and then written into the specified location of the terminal. The bin format of the binary data can provide a higher security level than the XML format, avoiding malicious software or unauthorized visitors from tampering with or forging the card lock rules, thereby protecting the reliability and stability of the entire card lock system.

[0019] In some possible implementations, the target software and at least two types of card lock requirement configuration information are written to a specified location of the terminal, including: encrypting at least two types of card lock requirement configuration information using an encryption algorithm to obtain encrypted information; and writing the encrypted information to the specified location of the terminal.

[0020] Through the above implementation, the card lock requirement configuration information is encrypted, which improves the security of the card lock requirement configuration information, thereby improving the confidentiality of the card lock data during storage and use, preventing the risk of unauthorized access and data leakage, and providing operators and users with a more secure and reliable card lock management environment.

[0021] In some examples, the encryption algorithm is an RSA algorithm, and the method further includes: writing the RSA algorithm public key to a specified location of the terminal.

[0022] Through the above implementation, the RSA algorithm public key and the card lock requirement configuration information can be associated. During the unlocking verification process, the system will use the RSA algorithm private key to decrypt, thereby protecting the security of the card lock requirement configuration information.

[0023] In some possible implementations, the designated location of the terminal includes a non-volatile storage area of ​​a modem of the terminal.

[0024] Through the above implementation, it is ensured that the data remains valid after the device is restarted or shut down, so that the card lock function can work normally in various device usage scenarios.

[0025] In a second aspect, a device for processing lock card data is provided, comprising: a processor configured to call program instructions to execute the method in the first aspect; and a storage device for storing a computer program, wherein the computer program includes program instructions.

[0026] In a third aspect, a card locking requirement processing system is provided, comprising: a card locking device and a terminal; wherein the card locking device is used to execute the method in the first aspect to perform card locking configuration on the terminal.

[0027] In a fourth aspect, a computer-readable storage medium is provided, storing computer-executable instructions, which are used to implement the method in the first aspect when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 It is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0029] Figure 2 This is a flow chart of a method for processing card lock data provided by an embodiment of the present application;

[0030] Figure 3 This is a flow chart of a method for processing card lock data provided by an embodiment of the present application;

[0031] Figure 4 It is a schematic diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to be limiting of the present application. As used in the specification and appended claims of the present application, the singular expressions "a", "an", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context.

[0033] References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear at different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0034] The present application provides a card lock data processing method, device, system and storage medium, which can be used in the card lock data processing process.

[0035] The technical solution in the present application will be described below in conjunction with the accompanying drawings. It should be understood that the specific embodiments described here are only used to explain the present application and are not used to limit the present application.

[0036] Simlock is a restriction mechanism, usually set by mobile phone manufacturers or operators, which makes the target terminal / software only use communication services under the simlock conditions set by the mobile phone manufacturers or operators. This restriction is implemented in the baseband firmware of the mobile phone through software, ensuring that users can only connect to the bound communication services during the contract period, which is in the interests of the operator.

[0037] In related technologies, card lock solutions are usually designed for a single project or specific software, and each project or software needs to develop and customize the corresponding card lock function separately. With the continuous advancement of technology and the rapid changes in market demand, operators' demands for card lock functions are becoming increasingly diverse and complex. When it is necessary to meet multiple card lock requirements at the same time, the solutions in the existing technology are often difficult to achieve flexible adjustment, making it difficult for the existing technology to adapt to the current dynamic and changing market environment and evolving technical requirements.

[0038] Therefore, in view of these limitations, it is particularly important to propose a card locking method that is compatible with multiple demand information.

[0039] Figure 1 It is a schematic diagram of a lock card data processing system provided in an embodiment of the present application.

[0040] The system 100 includes but is not limited to a security module 110 , a processing module 120 , a writing module 130 , and a terminal 140 , and may also include other electronic devices.

[0041] The security module 110 , the processing module 120 , and the writing module 130 may be regarded as a card locking device.

[0042] In some implementations, the security module 110 is used to obtain the card lock requirement information and encrypt the card lock requirement information to prevent the card lock requirement information from being maliciously attacked and leaked.

[0043] In some examples, security module 110 may use an encryption algorithm, such as an RSA algorithm.

[0044] In some implementations, the processing module 120 obtains the encrypted information processed by the security module 110 and at least two types of card lock requirement configuration information.

[0045] In some examples, the card lock requirement configuration information is whitelist information including all card lock requirement information, and the whitelist information records a list of information on allowed access and specific card lock conditions. When the relevant information conditions are met, unlocking can be performed to use the relevant SIM card or software.

[0046] In some examples, in order to improve the security of the whitelist information, it will be converted into a file format with a higher security factor.

[0047] In some examples, the whitelist information is in XML format, and the processing module 120 may convert the whitelist information in XML format into binary format for subsequent processing, for example, the binary format data is in bin format.

[0048] In other examples, the processing module 120 may also perform other encryption or signature processing on the card lock requirement information.

[0049] In some implementations, the writing module 130 combines the target software and the card lock requirement configuration information into the card lock data, which is written into the terminal 140 through the writing module 130 .

[0050] In some examples, the card lock requirement configuration information written into the terminal 140 may be the card lock requirement configuration information that has not been converted and encrypted, the card lock requirement configuration information that has been converted but not encrypted, or the card lock requirement configuration information that has been converted and encrypted.

[0051] In some examples, terminal 140 includes but is not limited to a smart terminal, such as a mobile phone, a computer, a wearable device, etc.

[0052] To explain more clearly Figure 1 The process of the middle scene is now combined with Figure 2-Figure 3 Provide explanation.

[0053] Figure 2 1 is a flow chart of a method for processing card lock data provided by an embodiment of the present application. Figure 2As shown, the method 200 can be applied to include Figure 1 In the application scenario shown, the method may at least include steps 210 to 220.

[0054] 210 , obtaining card lock requirement configuration information of at least two different card lock types of the target software.

[0055] 220, write the target software and at least two card lock requirement configuration information of different card lock types into a designated location of the terminal.

[0056] The steps of method 200 are described in detail below.

[0057] 210 , obtaining card lock requirement configuration information of at least two different card lock types of the target software.

[0058] In some implementations, the at least two types of card lock requirement configuration information obtained include first information and second information.

[0059] In some examples, the first information and the second information are card lock requirement configuration information, which can also be called whitelist information. A whitelist refers to a set of conditions or identifiers that allow access or use of a device through a card lock mechanism, usually including allowed networks, operators, devices, or other related permission information.

[0060] In some examples, the first information and the second information exist in the form of configuration files of the software / device that needs to lock the card, that is, the first information and the second information are separate files and are not in the same code system as the software that needs to lock the card.

[0061] In this case, the card lock requirement information can be decoupled from the software itself, thereby avoiding the need to re-code the card lock requirement information for each software, thereby reducing the work cost of operators.

[0062] In some implementations, the card lock requirement may include multiple key elements, such as a specified card lock type, device identification, validity period or contract period, etc.

[0063] In some implementations, the lock type may be a network lock, a network subset lock, a service provider lock, a corporate lock, an IMSI lock, etc., which restricts the device / software to be used under specific lock rules, such as a specific country, registered network, subnet, corporate network, etc.

[0064] In some implementations, the above-mentioned restriction on the card lock type is implemented through network code information.

[0065] In some examples, the network code information may include: a mobile country code (MCC), which identifies the country code to which the mobile user belongs; a mobile network code (MNC), which is used to identify the mobile communication network to which the mobile user belongs; home location register (HLR) information, which is used to identify the operator and related location information; and extended information, which is used to store other information that needs to be restricted in addition to the above network codes, such as a mobile subscriber identification number (MSIN), service information, group information, etc.

[0066] In some examples, the network code information of the network lock is MCC and MNC; the network code information of the sub-network lock is MCC, MNC and HLR information; the network code information of the service provider lock is MCC, MNC and service information; the network code information of the group lock is MCC, MNC, service information and group information; the network code information of the user lock is MCC, MNC, MSIN.

[0067] In some specific implementations, the network lock can restrict the device or software that locks the card through MCC and MNC to access only the network of a certain operator in a certain country; the sub-network lock further includes HLR information on the basis of the network lock, thereby further limiting the geographical scope that can access the network; the service provider lock further includes service information on the basis of the network lock, thereby further limiting the ability to use a specific service; the group lock, on the basis of the service provider lock, also includes specific information of the group, limiting the use to within a certain group; the user lock, on the basis of the network lock, also locks the MSIN information, thereby limiting the device / software to be used only by the user.

[0068] According to the above implementation, it can be seen that there is a progressive relationship between different types of locks in terms of restrictions on network code information. For example, the sub-network lock includes MCC, MNC and HLR information, and the network lock includes MCC and MNC, that is, the network code information of the sub-network lock includes all network code information of the network lock, and on this basis, includes more HLR information; for another example, the service provider lock includes all network code information of the network lock, and on this basis, includes more specific service information.

[0069] For convenience, the network code information of the first card lock type of the first information is referred to as the first network code information, and the network code information of the second card lock type of the second information is referred to as the second network code information.

[0070] In some specific implementations, there is the above-mentioned progressive relationship in the scope of inclusion of the first network code information and the second network code information, that is, the second network code information includes the first network code information.

[0071] In some examples, when the second network code information includes the first network code information, the service scope after the lock card is verified can be indicated according to the first network code information and the second network code information.

[0072] In some specific embodiments, when the terminal satisfies the second network code information, the second network code information is used to indicate that all communication services of the target software are open; when the terminal satisfies the first network code information but does not satisfy the second network code information, the first network code information and the second network code information are used to indicate that some communication services of the target software are open; when the terminal does not satisfy the first network code information, the first network code information is used to indicate that the communication services of the target software are not open.

[0073] In some examples, all communication services may include network services, while some communication services may include only mobile calling capabilities.

[0074] In other examples, all communication services may include multiple functions such as data services, WIFI services, and Bluetooth services, while some communication services may be limited to WIFI services.

[0075] It is to be understood that the above examples are merely illustrative and not exhaustive.

[0076] This multi-level card lock rule design allows for more refined control over device usage permissions. Operators can set different levels of restrictions based on different users, contract types, or market strategies, which provides operators with more flexibility to adjust market strategies and meet business needs at different levels.

[0077] It can be understood that, further, at least two types of card lock requirement configuration information means that the obtainable card lock requirement information may include more than the first information and the second information, but includes multiple information, each of which includes different card lock requirement configuration information.

[0078] This scalable design enables the card lock mechanism to adapt to more complex rule configuration requirements, further improving the flexibility of the card lock mechanism.

[0079] In some embodiments, the first network code information and the second network code information include a first part and a second part, the first part is a mobile country code and a mobile network code, the first network code information is different from the second part of the second network code information, and when the terminal satisfies the first network code information and the second network code information, the first network code information and the second network code information are used to indicate all communication services of the open target software.

[0080] According to the above implementation, it can be known that in this case, there is no progressive relationship between the lock card types of the first information and the second information in the network code information, that is, the network code information of the first lock card type corresponding to the first information and the network code information of the second lock card type corresponding to the second information are different except for the mobile country code and the mobile network code.

[0081] For example, the first lock card type is a sub-network lock, and the corresponding first network code information is MCC, MNC, and HLR information. The second lock card type is a service provider lock, and the corresponding second network code information is MCC, MNC, and related information about the service in the extended information. In this case, the second part of the first network code information is the HLR information, and the second part of the second network code information is the extended information. At this time, there is no progressive relationship between the first network code information and the second network code information.

[0082] In some examples, in the card lock verification phase in this case, the card lock requirement conditions of the first information and the second information must be met at the same time for normal use.

[0083] As in the above example, the first lock card type is a subnetwork lock, and the second lock card type is a service provider lock. The first lock card type limits the geographical subnet used, and the second lock card type limits the specific service used. In this case, all services of the project can only be used when the service content limited by the second lock card type is used within the area limited by the first lock card.

[0084] In some examples, if only one of the lock card types' restriction conditions are met, such as only the regional restriction of the sub-network lock or only the service restriction of the service provider lock, the device will not be able to fully enjoy all the services of the project.

[0085] Through this design, stricter card lock requirement restrictions can be implemented on the same device, which can be used in scenarios with higher confidentiality levels to achieve effective management and control of device security.

[0086] 220, write the target software and at least two types of card lock requirement configuration information into a designated location of the terminal.

[0087] In some implementations, the first information and the second information are written simultaneously, and the specific card lock type of the written information is as described in step 210 .

[0088] In this way, different types of card lock requirements can be combined to flexibly control the scope of use of the equipment and meet more complex market demands.

[0089] In some implementations, before writing to the designated location of the terminal, the card lock requirement configuration information to be written can be encrypted or signed to protect the information security, so as to prevent the card lock information from being easily cracked and thus damaging the interests of operators and mobile phone manufacturers.

[0090] In some examples, the card lock requirement configuration information may be encrypted using an encryption algorithm, such as an RSA algorithm.

[0091] In some embodiments, the terminal-specified location includes a non-volatile storage area of ​​the terminal's modem.

[0092] Through the above implementation, it can be ensured that the configuration information remains valid after the device is powered off, further improving the reliability and adaptability of the system.

[0093] Figure 3 1 is a flow chart of a method for processing card lock data provided by an embodiment of the present application. Figure 3 As shown, the method 300 can be applied to include Figure 1 In the application scenario shown.

[0094] The method 300 includes steps 310 and 320 . Optionally, the method 300 includes steps 301 , 302 , and 311 .

[0095] 301. The security module generates encrypted information and sends the encrypted information to the processing module.

[0096] 302, the processing module presets the encryption information generated by the security module in a designated location of the software.

[0097] 310. The processing module obtains at least two card lock requirement configuration information of different card lock types.

[0098] 311. The processing module generates corresponding at least two types of target information according to at least two types of different card lock requirement configuration information.

[0099] 320, write the target software and at least two card lock requirement configuration information of different card lock types into a designated location of the terminal.

[0100] The steps of method 300 are described in detail below.

[0101] 301. The security module generates encrypted information and sends the encrypted information to the processing module.

[0102] In some implementations, the encrypted information is generated using an encryption algorithm to ensure the security of the lock card data during transmission and storage.

[0103] In some examples, the encryption algorithm used is the RSA encryption algorithm, that is, the processing module 120 uses the RSA key system to generate a set of independent key pairs for each card lock requirement configuration information. Each key pair includes a public key and a private key.

[0104] In some examples, before encryption is performed, a database file (such as a .db format file) needs to be generated to ensure that information is structured and easily accessible.

[0105] For example, a first database file corresponding to the first information and a second database file corresponding to the second information are generated. The correspondence here refers to the database files whose names and information match that need to be set on the production line, so that when writing the card lock requirement, the key information can match the whitelist information, thereby protecting the corresponding card lock requirement configuration information.

[0106] In some examples, the security module 110 sends the generated encrypted information to the processing module 120 for subsequent use.

[0107] 302, the processing module presets the encryption information generated by the security module in a designated location of the software.

[0108] In some examples, the key pair generated by the RSA algorithm, in which the generated public key can be deployed to the software that requires the lock card to verify the information at runtime, while the corresponding private key is retained for the subsequent decryption process to ensure that the information can only be accessed by authorized parties.

[0109] In this way, when the device, software or related system needs to verify the lock card information, it can be decrypted and verified through the preset public key to ensure the security and integrity of the information.

[0110] In some implementations, the designated location is a specific directory or file path of the software that needs to lock the card. This presetting operation enables the processing module 120 to automatically call the preset public key when the software is running, ensuring that the target software can interact with the processing module 120 correctly.

[0111] By presetting the public key to a specified location, the system can efficiently implement encryption operations, and also facilitate the subsequent verification and decryption process, thereby providing a stable guarantee for the operation of the card lock system. This method not only simplifies the operation process, but also improves the security and reliability of the system.

[0112] 310. The processing module obtains at least two card lock requirement configuration information of different card lock types.

[0113] For the specific implementation of step 310 , reference may be made to step 210 in method 200 .

[0114] 311. The processing module generates corresponding at least two types of target information according to at least two types of different card lock requirement configuration information.

[0115] In some examples, at least two types of card lock requirement configuration information include first information and second information, and corresponding at least two types of target information are generated according to the two types of card lock requirement configuration information, that is, first target information is generated according to the first information, and second target information is generated according to the second information.

[0116] In some examples, the process of generating the first target information and the second target information is to convert the first information and the second target information into a file type with a higher security level to further protect the data security of the first information and the second information.

[0117] For example, the first information and the second information are XML format files that record the card lock configuration and specific card lock rules. The data of the first target information and the second target information after conversion and encryption are usually saved in binary format (such as bin file), thereby effectively preventing malicious tampering or illegal reading.

[0118] This encryption process ensures the integrity and confidentiality of the card lock rules and configurations. Only systems or users with the correct decryption permissions can access and use this information. It is more difficult to crack than XML files, preventing malware or unauthorized visitors from tampering with or forging the card lock rules, thereby protecting the reliability and stability of the entire card lock system.

[0119] 320, write the target software and at least two card lock requirement configuration information of different card lock types into a designated location of the terminal.

[0120] In some implementations, when the method is executed and step 311 is included, what is written into the designated location of the terminal is the converted first target information and the converted second target information.

[0121] In this case, the written lock card requires configuration information with higher security.

[0122] In some examples, the writing module 130 (such as simba) is used to write the target software together with the first information and the second information (or the first target information and the second target information after step 311) into a designated location of the terminal 140.

[0123] In some examples, the designated location of terminal 140 refers to a non-volatile storage area of ​​a modem (modem side) of the terminal.

[0124] By writing the encrypted information into the non-volatile storage area on the modem side, the security and stability of the card lock related data can be guaranteed to prevent tampering or loss, and the configuration information can also be ensured to remain valid after the device is powered off.

[0125] It can be understood that the above process is to match the configuration file of the software to realize the card lock requirement configuration, and in actual application, the specific card lock requirement can be selected and used according to the specific needs, and the relevant processes of the information execution method 200 and 300 corresponding to the requirement can be configured, thereby avoiding the repetitive process of writing the card lock information into the code every time, and reducing the workload of technical personnel.

[0126] Figure 4 It is a schematic diagram of a device provided in an embodiment of the present application.

[0127] The data processing device 400 may include: a processor 410 and a memory 420 .

[0128] The processor 410 is configured to obtain at least two types and / or card lock requirement configuration information of different priorities.

[0129] In some examples, optionally, the processor 410 may also be configured to generate corresponding at least two types of target information according to card lock requirement configuration information of at least two different card lock types.

[0130] In some examples, optionally, the processor 410 may also use an encryption algorithm to encrypt the card lock requirement configuration information of at least two different card lock types to obtain encrypted information.

[0131] This process ensures that the card lock requirement configuration information can be protected at multiple levels to prevent data leakage or tampering, thereby improving the security of the system.

[0132] The memory 420 is used to write the target software and the card lock requirement configuration information processed by the processor 410 into the non-volatile memory of the device.

[0133] In some examples, the card lock requirement configuration information to be stored is the card lock requirement configuration information processed by an encryption algorithm and / or processed to generate target information.

[0134] The writing process of the memory 420 not only preserves the integrity of the encrypted data, but also ensures that the data is still valid after the device is restarted or shut down, so that the card lock function can work normally in various device usage scenarios. This design further enhances the stability and security of the system and effectively prevents the risk of loss or malicious modification of the card lock information.

[0135] The present application also provides a computer-readable storage medium. The provided computer-readable storage medium stores a computer program, and the provided computer program includes program instructions. When the provided program instructions are executed by the processor, the above-mentioned Figure 2-3 The data processing method shown, and the steps performed by the relevant implementation methods.

[0136] The above-mentioned computer-readable storage medium may be an internal storage unit of the security module, processing module, and writing module provided in any of the aforementioned embodiments, such as a hard disk or memory of the device. The provided computer-readable storage medium may also be an external storage device of the provided terminal device, deployment module, or security server, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc. equipped on the provided device. Further, the provided computer-readable storage medium may also include both the internal storage unit of the provided security module, processing module, and writing module and an external storage device. The provided computer-readable storage medium is used to store the provided computer program and other programs and data required by the provided security module, processing module, and writing module. The provided computer-readable storage medium may also be used to temporarily store data that has been output or is to be output. The provided computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more available media sets. The provided available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium. The semiconductor medium may be a solid-state hard disk.

[0137] The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination thereof. When implemented using software, the above embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means.

[0138] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0139] In the several embodiments provided in the present application, it should be understood that the disclosed methods, devices and systems can be implemented in other ways. For example, the device embodiments described above are merely schematic; for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0140] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0141] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0142] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform some steps of the method described in each embodiment of the present invention.

[0143] It should be understood that the specific examples in this article are only intended to help those skilled in the art better understand the embodiments of the present application, rather than to limit the scope of the embodiments of the present application.

[0144] It should also be understood that in the various embodiments of the present application, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0145] It should also be understood that the various implementation methods described in this specification can be implemented individually or in combination, and the embodiments of the present application are not limited to this.

[0146] Unless otherwise specified, all technical and scientific terms used in the embodiments of the present application are the same as those generally understood by technicians in the technical field of the present application. The terms used in this application are only for the purpose of describing specific embodiments and are not intended to limit the scope of the present application. In the description of the present application, it should be noted that, unless otherwise specified, the meaning of "multiple" is more than two; the orientation or positional relationship indicated by the terms "upper", "lower", "left", "right", "inside", "outside", etc. is only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation to the present application. The term "and / or" used in this application includes any and all combinations of one or more related listed items. In addition, the terms "first", "second", "third", etc. are only used for description purposes and cannot be understood as indicating or implying relative importance.

[0147] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for processing card lock data, characterized in that: The method comprises: Acquire at least two types of card lock requirement configuration information of the target software, wherein the at least two types of card lock requirement configuration information are different, and the card lock types include: network lock, sub-network lock, service provider lock, group lock and user lock, and the at least two types of card lock requirement configuration information are used to jointly indicate the service scope after the card lock is verified; The target software and the at least two types of card lock requirement configuration information are written into a designated location of the terminal.

2. The method according to claim 1, characterized in that The card locking types of the at least two card locking requirement configuration information are determined by the network code information.

3. The method according to claim 2, characterized in that The network code information includes: at least one of: a mobile country code, a mobile network code, a home location register information and extended information, wherein the mobile country code is used to identify the country range of use; the mobile network code is used to identify the mobile network used; the home location register information is used to identify location information; and the extended information is used to identify service information, group information, or a mobile user identification number.

4. The method according to claim 3, characterized in that: The at least two types of card lock requirement configuration information include first card lock type requirement configuration information and second card lock type requirement configuration information, the first card lock type requirement configuration information includes first network code information, the second card lock type requirement configuration information includes second network code information, the first network code information and the second network code information are used to jointly indicate the service scope after the card lock is verified.

5. The method according to claim 4, characterized in that The second network code information includes the first network code information, In the case where the terminal satisfies the second network code information, the second network code information is used to indicate opening all communication services of the target software; In a case where the terminal satisfies the first network code information but does not satisfy the second network code information, the first network code information and the second network code information are used to indicate opening of part of the communication services of the target software; In a case where the terminal does not satisfy the first network code information, the first network code information is used to indicate that the communication service of the target software is not open.

6. The method according to claim 4, characterized in that The first network code information and the second network code information include a first part and a second part, the first part is the mobile country code and the mobile network code, and the second part of the first network code information is different from the second network code information. In a case where the terminal satisfies the first network code information and the second network code information, the first network code information and the second network code information are used to indicate that all communication services of the target software are opened.

7. The method according to any one of claims 1 to 6, characterized in that Writing the target software and the at least two types of card lock requirement configuration information into a designated location of the terminal includes: Generate corresponding at least two kinds of target information according to the at least two kinds of card lock requirement configuration information, wherein the card lock requirement configuration information is in XML format and the target information is in binary data bin format; The target software and the at least two types of target information are written into a designated location of the terminal.

8. The method according to any one of claims 1 to 6, characterized in that Writing the target software and the at least two types of card lock requirement configuration information into a designated location of the terminal includes: Encrypt the at least two types of card lock requirement configuration information using an encryption algorithm to obtain encrypted information; The encrypted information is written into a designated location of the terminal.

9. The method according to claim 8, characterized in that The encryption algorithm includes: RSA algorithm, and the method further includes: The RSA algorithm public key is written into a designated location of the terminal.

10. The method according to any one of claims 1 to 6, characterized in that The designated location of the terminal includes a non-volatile storage area of ​​a modem of the terminal.

11. A card lock data processing device, characterized in that: include: A processor configured to call program instructions to execute the method according to any one of claims 1 to 10; The storage device is used to store a computer program, wherein the computer program includes the program instructions.

12. A card lock requirement processing system, characterized in that: include: Card locking devices and terminals; The card locking device is used to execute the method as claimed in any one of claims 1 to 10 to perform card locking configuration on the terminal.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 10 when executed by a processor.

Images