CN110505225B - Terminal card locking method and device and computer readable storage medium - Google Patents
Terminal card locking method and device and computer readable storage medium Download PDFInfo
- Publication number
- CN110505225B CN110505225B CN201910772579.6A CN201910772579A CN110505225B CN 110505225 B CN110505225 B CN 110505225B CN 201910772579 A CN201910772579 A CN 201910772579A CN 110505225 B CN110505225 B CN 110505225B
- Authority
- CN
- China
- Prior art keywords
- card locking
- card
- terminal
- locking
- target terminal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Abstract
The application provides a terminal card locking method, a terminal card locking device and a computer readable storage medium, which are used for judging whether card locking operation needs to be carried out on a target terminal or not; when the target terminal is determined to need to perform card locking operation, sending a card locking data request to a card locking server; and receiving card locking data responded by the card locking server based on the card locking data request, and performing card locking operation on the target terminal through the card locking data. Through the implementation of this application scheme, when needing to lock the card to the terminal, to lock the card server request and save the lock card data on locking the card server, fully guaranteed lock card security to and all directly lock the card to the terminal of different states, effectively improved lock card efficiency and accuracy.
Description
Technical Field
The present application relates to the field of electronic technologies, and in particular, to a terminal card locking method and apparatus, and a computer-readable storage medium.
Background
The communication function is the most basic and important function of the terminal, and great convenience is brought to the work and life of a terminal user. However, in practical applications, in order to obtain more client resources, a communication operator usually cooperates with a terminal manufacturer to produce an operator customized terminal, that is, before the terminal leaves a factory, the terminal is ensured to be normally used only by using a Subscriber Identity Module (SIM) card of the operator in a locking manner.
At present, when a terminal manufacturer locks a card for an operator of a terminal, it is usually necessary to distinguish whether the terminal is in an unlocked state or a card-locked state, and when the terminal is in the unlocked state, card-locking data is directly written into an SFS partition or an NV partition of the terminal through a card-locking tool, while the terminal in the card-locked state needs to firstly swipe an original operator software to unlock, and then rewrite current card-locking data. On the one hand, because all need carry out the state to the terminal and distinguish before locking the card to the terminal at every turn to it is limited to lock card efficiency and accuracy, on the other hand, because it is local with the terminal of writing in of locking card data through locking the card instrument directly, thereby is cracked by lawbreakers easily, and it is lower to lock the card security.
Disclosure of Invention
The embodiment of the application provides a terminal card locking method, a terminal card locking device and a computer readable storage medium, which can at least solve the problems that in the related art, when an operator locks a card on a terminal, the card locking efficiency and accuracy are limited, and the card locking safety is low.
A first aspect of the embodiments of the present application provides a terminal card locking method, including:
judging whether a target terminal needs to be locked or not;
when the target terminal is determined to need to perform card locking operation, sending a card locking data request to a card locking server;
and receiving card locking data responded by the card locking server based on the card locking data request, and performing card locking operation on the target terminal through the card locking data.
A second aspect of the embodiments of the present application provides a terminal card locking device, including:
the judging module is used for judging whether card locking operation needs to be carried out on the target terminal or not;
the request module is used for sending a card locking data request to a card locking server when the target terminal is determined to need to perform card locking operation;
and the card locking module is used for receiving card locking data responded by the card locking server based on the card locking data request and performing card locking operation on the target terminal through the card locking data.
A third aspect of embodiments of the present application provides an electronic apparatus, including: the terminal card locking method includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the terminal card locking method provided in the first aspect of the embodiments of the present application when executing the computer program.
A fourth aspect of the present embodiment provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the steps in the terminal card locking method provided in the first aspect of the present embodiment are implemented.
In view of the above, according to the terminal card locking method, device and computer readable storage medium provided by the scheme of the application, whether card locking operation needs to be performed on the target terminal is judged; when the target terminal is determined to need to perform card locking operation, sending a card locking data request to a card locking server; and receiving card locking data responded by the card locking server based on the card locking data request, and performing card locking operation on the target terminal through the card locking data. Through the implementation of this application scheme, when needing to lock the card to the terminal, to lock the card server request and save the lock card data on locking the card server, fully guaranteed lock card security to and all directly lock the card to the terminal of different states, effectively improved lock card efficiency and accuracy.
Drawings
Fig. 1 is a schematic basic flow chart of a terminal card locking method according to a first embodiment of the present application;
fig. 2 is a schematic basic flow chart of a terminal factory monitoring method according to a first embodiment of the present application;
fig. 3 is a schematic basic flow chart of a terminal unlocking method according to a first embodiment of the present application;
fig. 4 is a schematic detailed flow chart of a terminal card locking method according to a second embodiment of the present application;
fig. 5 is a schematic diagram of program modules of a terminal card locking device according to a third embodiment of the present application;
fig. 6 is a schematic diagram of program modules of another terminal card locking device according to a third embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present disclosure.
Detailed Description
In order to make the objects, features and advantages of the present invention more apparent and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In order to solve the defects of limited card locking efficiency and accuracy and low card locking safety when an operator locks a card for a terminal in the related art, a first embodiment of the present application provides a card locking method for a terminal, which is applied to a card locking tool, for example, fig. 1 is a basic flow chart of the card locking method for a terminal provided in this embodiment, and the card locking method for a terminal includes the following steps:
Specifically, in this embodiment, it is first necessary to determine whether the terminal needs to be locked by the operator, and there are two cases for the operator to lock the card, where one is to lock the card for the first time for the terminal in the unlocked state that has never been locked, and the other is to lock the card again for the terminal in the card locked state to the operator.
It should be noted that, in the embodiment, in the related art, the card locking state and the card unlocking state are currently distinguished by a software version, that is, the software versions adopted for card locking and card unlocking are different, if the terminal has locked the card, the terminal needs to be transferred to the operator to lock the card again, and the original operator software needs to be swiped to remove the existing card locking data. However, different from the related art, the card locking function of the embodiment is adapted to all software versions, so that the embodiment does not need to distinguish whether the terminal is in a card locking state, and even if the terminal is in the card locking state, the card locking data can be directly written to overwrite the original card locking data. Operation logic in the terminal card locking process is optimized, and card locking efficiency is improved.
Optionally, before determining whether the card locking operation needs to be performed on the target terminal, the method further includes: acquiring terminal identification information of a target terminal; and calling an operation index table maintained by the card locking server, and inquiring an operation instruction corresponding to the terminal identification information of the target terminal.
Specifically, in this embodiment, the terminal manufacturer is configured with a card locking server, and then an operation index table including a corresponding relationship between the terminal identification information and the operation instruction is maintained on the card locking server, so that the operation instruction for indicating the operation type can be queried based on the terminal identification information. It should be noted that, in this embodiment, the terminal identification information is used to uniquely identify the terminal, and may include a PCBA number and/or a special case number of the terminal, and in other embodiments, the terminal identification information may also be used to send a query request carrying the terminal identification information to the card lock server, and request a corresponding query result from the card lock server maintaining the operation index table to obtain the operation instruction of the target terminal.
Correspondingly, in this embodiment, the manner of determining whether the card locking operation needs to be performed on the target terminal is as follows: judging whether the operation type indicated by the operation instruction is the card locking operation or not according to the inquired operation instruction; when the operation type indicated by the operation instruction is a card locking operation, the card locking operation needs to be performed on the target terminal.
Optionally, before determining whether the card locking operation needs to be performed on the target terminal, the method further includes: judging whether the target terminal supports a card locking function or not; and when the target terminal is determined to support the card locking function, executing a step of judging whether the card locking operation is required to be carried out on the target terminal.
Specifically, in this embodiment, since card locking requires support of a new software version, but the software version of the terminal may be an old version and does not support the card locking function, based on this, in this embodiment, the terminal card locking process of this embodiment is executed only on the terminal that supports the card locking function. It should be understood that, whether the terminal supports the card locking function may be determined by obtaining a model of the terminal, and then querying a card locking function flag corresponding to the model through data maintained by the card locking server, where the card locking function flag is used to indicate whether the terminal supports the card locking function.
And 102, when the target terminal is determined to need to perform card locking operation, sending a card locking data request to a card locking server.
Specifically, in this embodiment, when it is determined that the terminal needs to lock the card, since the card locking operation of this embodiment is applicable to all software versions, the card locking server directly requests the card locking data. It should be understood that the card locking data of the embodiment is stored in the card locking server and is only issued when requested by the card locking tool, so that the security of the card locking data is ensured, and the card locking operation of the terminal is prevented from being cracked.
And 103, receiving card locking data responded by the card locking server based on the card locking data request, and performing card locking operation on the target terminal through the card locking data.
Specifically, in this embodiment, the card locking tool writes the card locking data into the terminal, and the terminal locks the card according to the card locking logic indicated by the card locking data, and does not record the card locking data itself, so that in this embodiment, after the card is locked, the card locking state cannot be unlocked by swiping the machine, and the card locking safety is fully ensured.
Optionally, after the card locking operation is performed on the target terminal through the card locking data, the method further includes: receiving a card locking result sent by a target terminal after the target terminal executes the card locking operation; and associating the card locking result with the terminal identification information of the target terminal, and uploading the association relationship between the card locking result and the terminal identification information to a card locking server.
Specifically, in this embodiment, after the terminal performs the card locking operation, a card locking result is generated, where the card locking result includes a card locking success result or a card locking failure result, and after receiving the card locking result, the card locking tool associates the card locking result with the terminal identification information of the corresponding terminal, and then uploads the association to the card locking server, so that the card locking server monitors the terminal.
As shown in fig. 2, which is a flowchart of the terminal factory monitoring method provided in this embodiment, optionally, after the association relationship between the card locking result and the terminal identification information is uploaded to the card locking server, the method further includes the following steps:
and 203, outputting a factory-allowed instruction corresponding to the terminal to be factory when the card locking result is successful card locking.
Specifically, in practical applications, instead of successfully locking a card (for example, the card is not locked or the card is locked incorrectly) after each terminal is subjected to a card locking operation, if a communication operator requires that a card-locking machine leaves a factory without successfully locking the card, a negative impact is caused to a terminal manufacturer, and based on this, whether the terminal successfully locks the card needs to be monitored before the terminal requiring the card locking leaves the factory. At present, in the related art, when factory monitoring is performed, verification is performed by manually inserting an SIM card, which is troublesome to operate and low in efficiency. However, in this embodiment, a correspondence between the terminal identifier and the card locking result is maintained on the card locking server, so that before the terminal leaves a factory, the terminal identifier is used to query the corresponding card locking result, and only the terminal whose card locking result is successful is subjected to a factory permission instruction; correspondingly, for the terminal which is not successfully locked, the factory-leaving prohibition instruction can be output. In the embodiment, by calling the card locking server for inquiry before leaving the factory, the risk that the terminal which does not successfully lock the card flows out can be avoided, and the efficiency, the safety and the accuracy are greatly improved compared with manual card plugging and unplugging for factory monitoring.
Optionally, before associating the card locking result with the terminal identification information of the target terminal, the method further includes: when the card locking result is unsuccessful, repeatedly locking the target terminal, and receiving the card locking result sent by the target terminal; and when the card locking result is that the times of unsuccessful card locking reach a preset time threshold value continuously, executing a step of associating the card locking result with the terminal identification of the target terminal.
Specifically, in practical application, for objective reasons, it may be that the card locking data cannot be guaranteed to be successfully written once, based on this, in this embodiment, when the card locking result is unsuccessful card locking, the card locking operation is repeatedly performed on the target terminal, where the card locking data used for re-locking may be previous card locking data or redetermined card locking data, and the card locking result responded by the terminal is continuously received, if the card locking result is still unsuccessful card locking, the operation is continuously repeated until the number of times of continuous unsuccessful card locking is accumulated to a preset number threshold, the continued card locking operation is terminated, the card locking result of the unsuccessful card locking is formally associated with the terminal identifier, and then the result is reported to the server.
As shown in fig. 3, which is a flowchart of the terminal unlocking method provided in this embodiment, optionally, after determining whether the card locking operation needs to be performed on the target terminal, the method further includes the following steps:
and 303, unlocking the target terminal in the card locking state through the unlocking data.
Specifically, in this embodiment, the card locking tool is not limited to lock the card of the terminal, and the card locking server is not limited to provide the card locking related service. And when the terminal does not need to lock the card, the terminal is determined as the card-locked terminal, and the card locking tool requests unlocking data from the card locking server to unlock the terminal.
It should be noted that, in practical applications, if the terminal does not support the card locking function, the card locking attribute of the terminal may be obtained, so as to determine whether the terminal has locked the card according to the obtained card locking attribute, and if it is determined that the terminal is the card locked terminal, the above steps 302 to 303 are also performed to unlock the terminal. In addition, it should be noted that, similar to the card locking operation, after the terminal is unlocked, the unlocking result fed back by the terminal may also be obtained, and then the unlocking result is reported to the card locking server.
Based on the technical scheme of the embodiment of the application, whether the target terminal needs to be locked or not is judged; when the target terminal is determined to need to perform card locking operation, sending a card locking data request to a card locking server; and receiving card locking data responded by the card locking server based on the card locking data request, and performing card locking operation on the target terminal through the card locking data. Through the implementation of this application scheme, when needing to lock the card to the terminal, to lock the card server request and save the lock card data on locking the card server, fully guaranteed lock card security to and all directly lock the card to the terminal of different states, effectively improved lock card efficiency and accuracy.
The method in fig. 4 is a detailed terminal card locking method provided in a second embodiment of the present application, and is applied to a card locking tool, where the terminal card locking method includes:
In this embodiment, a terminal manufacturer is configured with a card locking server, and then an operation index table including a correspondence between terminal identification information and operation instructions is maintained on the card locking server, so that operation instructions for indicating operation types can be queried based on the terminal identification information.
And step 403, when the operation type indicated by the operation instruction is a card locking operation, sending a card locking data request to a card locking server.
In this embodiment, when it is determined that the terminal needs to lock the card by the operator, the card locking server is requested for card locking data, and since the card locking operation of this embodiment is applicable to all software versions, the card locking data is directly requested from the card locking server without distinguishing whether the terminal is in a card locking state, and even if the terminal is in the card locking state, the card locking data can be directly written to cover the original card locking data.
It should be understood that the card locking data of the embodiment is stored in the card locking server and is only issued when requested by the card locking tool, so that the security of the card locking data is ensured, and the card locking operation of the terminal is prevented from being cracked.
And step 404, receiving card locking data responded by the card locking server based on the card locking data request, and performing card locking operation on the target terminal through the card locking data.
In this embodiment, the card locking tool writes the card locking data into the terminal, and the terminal locks the card according to the card locking logic indicated by the card locking data, and does not record the card locking data itself, so that the card locking state cannot be unlocked even if the card is swiped after the card is locked, and the card locking safety is fully ensured.
And 406, associating the card locking result with the terminal identification information of the target terminal, and uploading the association relationship between the card locking result and the terminal identification information to a card locking server.
In this embodiment, after the terminal performs the card locking operation, a card locking result is generated, where the card locking result includes a card locking success result or a card locking failure result, and after receiving the card locking result, the card locking tool associates the card locking result with the terminal identification information of the corresponding terminal, and then uploads the association to the card locking server, so that the card locking server monitors the terminal.
And step 408, outputting a factory-allowed instruction corresponding to the terminal to be factory when the card locking result is successful card locking.
In this embodiment, a correspondence between the terminal identifier and the card locking result is maintained on the card locking server, so that before the terminal leaves a factory, the terminal identifier is used to query the corresponding card locking result, and only the terminal with the card locking result being successful is subjected to a factory permission instruction; correspondingly, for the terminal which is not successfully locked, the factory-leaving prohibition instruction can be output. According to the method, the risk that the terminal which does not successfully lock the card flows out can be avoided by calling the card locking server for inquiring before leaving the factory, and the efficiency, the safety and the accuracy are improved to a great extent compared with the manual card plugging and unplugging for carrying out factory monitoring.
It should be understood that, the size of the serial number of each step in this embodiment does not mean the execution sequence of the step, and the execution sequence of each step should be determined by its function and inherent logic, and should not be limited uniquely to the implementation process of the embodiment of the present application.
The embodiment of the application discloses a terminal card locking method, when a terminal needs to be locked, card locking data stored on a card locking server is requested to the card locking server, the card locking safety is fully ensured, and the card locking is directly performed aiming at terminals in different states, the card locking efficiency and accuracy are effectively improved.
Fig. 5 is a terminal card locking device according to a third embodiment of the present application. The terminal card locking device can be used for realizing the terminal card locking method in the foregoing embodiment. As shown in fig. 5, the terminal card locking device mainly includes:
a judging module 501, configured to judge whether a card locking operation needs to be performed on a target terminal;
a request module 502, configured to send a card locking data request to a card locking server when it is determined that a target terminal needs to perform a card locking operation;
and the card locking module 503 is configured to receive card locking data responded by the card locking server based on the card locking data request, and perform a card locking operation on the target terminal through the card locking data.
As shown in fig. 6, another terminal card locking device provided in this embodiment is an alternative implementation manner of this embodiment, where the terminal card locking device further includes: the query module 504 is configured to obtain terminal identification information of the target terminal before determining whether a card locking operation needs to be performed on the target terminal; and calling an operation index table maintained by the card locking server, and inquiring an operation instruction corresponding to the terminal identification information of the target terminal. Correspondingly, the determining module 501 is specifically configured to determine, according to the queried operation instruction, whether the operation type indicated by the operation instruction is a card locking operation; when the operation type indicated by the operation instruction is a card locking operation, the card locking operation needs to be performed on the target terminal.
In an optional implementation manner of this embodiment, the determining module 501 is specifically configured to determine whether the target terminal supports a card locking function; and when the target terminal is determined to support the card locking function, judging whether the card locking operation needs to be carried out on the target terminal.
With reference to fig. 6, in an alternative implementation manner of this embodiment, the terminal card locking device further includes: the unlocking module 505 is configured to determine that the target terminal is in a locked state when it is determined that the target terminal does not need to perform the card locking operation after determining whether the target terminal needs to be subjected to the card locking operation; sending an unlocking data request to a card locking server, and receiving unlocking data responded by the card locking server based on the unlocking data request; and unlocking the target terminal in the card-locked state through the unlocking data.
With reference to fig. 6, in an alternative implementation manner of this embodiment, the terminal card locking device further includes: the association module 506 is configured to receive a card locking result sent by the target terminal after the card locking operation is performed on the target terminal through the card locking data; and associating the card locking result with the terminal identification information of the target terminal, and uploading the association relationship between the card locking result and the terminal identification information to a card locking server.
Further, in an optional implementation manner of this embodiment, the query module 504 is further configured to obtain the terminal identification information of the terminal to be shipped from the factory after uploading the association relationship between the card locking result and the terminal identification information to the card locking server; calling the association relationship maintained by the card locking server, and inquiring a card locking result corresponding to the terminal to be delivered from a factory; and when the card locking result is successful card locking, outputting a factory-allowed instruction corresponding to the terminal to be factory.
With reference to fig. 6, in an alternative implementation manner of this embodiment, the terminal card locking device further includes: the operation module 507 is configured to repeatedly perform the card locking operation on the target terminal when the card locking result is that the card is not successfully locked, and receive the card locking result sent by the target terminal. Correspondingly, when the card locking result is that the number of times of unsuccessful card locking reaches the preset number threshold, the association module 506 executes the function of associating the card locking result with the terminal identifier of the target terminal.
It should be noted that, the terminal card locking methods in the first and second embodiments can be implemented based on the terminal card locking device provided in this embodiment, and it can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the terminal card locking device described in this embodiment may refer to the corresponding process in the foregoing method embodiment, and details are not described here again.
According to the terminal card locking device provided by the embodiment, whether card locking operation needs to be performed on a target terminal is judged; when the target terminal is determined to need to perform card locking operation, sending a card locking data request to a card locking server; and receiving card locking data responded by the card locking server based on the card locking data request, and performing card locking operation on the target terminal through the card locking data. Through the implementation of this application scheme, when needing to lock the card to the terminal, to lock the card server request and save the lock card data on locking the card server, fully guaranteed lock card security to and all directly lock the card to the terminal of different states, effectively improved lock card efficiency and accuracy.
Referring to fig. 7, fig. 7 is an electronic device according to a fourth embodiment of the present disclosure. The electronic device can be used for realizing the terminal card locking method in the embodiment. As shown in fig. 7, the electronic device mainly includes:
a memory 701, a processor 702, a bus 703 and a computer program stored on the memory 701 and executable on the processor 702, the memory 701 and the processor 702 being connected by the bus 703. When the processor 702 executes the computer program, the terminal card locking method in the foregoing embodiment is implemented. Wherein the number of processors may be one or more.
The Memory 701 may be a high-speed Random Access Memory (RAM) Memory or a non-volatile Memory (non-volatile Memory), such as a disk Memory. A memory 701 is used to store executable program code and a processor 702 is coupled to the memory 701.
Further, an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium may be an electronic device provided in the foregoing embodiments, and the computer-readable storage medium may be a memory in the foregoing embodiment shown in fig. 7.
The computer-readable storage medium has a computer program stored thereon, and the program realizes the terminal card locking method in the foregoing embodiment when executed by a processor. Further, the computer-readable storage medium may be various media that can store program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a RAM, a magnetic disk, or an optical disk.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a readable storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned readable storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
It should be noted that, for the sake of simplicity, the above-mentioned method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to the related descriptions of other embodiments.
In view of the above description of the terminal card locking method, the electronic device and the computer readable storage medium provided by the present application, those skilled in the art will recognize that there are variations from the foregoing description to the following description in terms of the embodiments of the present application.
Claims (9)
1. A terminal card locking method is characterized by being applied to a card locking tool and comprising the following steps:
acquiring terminal identification information of a target terminal;
calling an operation index table maintained by a card locking server, and inquiring an operation instruction corresponding to the terminal identification information of the target terminal;
judging whether the operation type indicated by the operation instruction is card locking operation or not according to the inquired operation instruction; when the operation type indicated by the operation instruction is a card locking operation, the card locking operation needs to be performed on the target terminal;
when the target terminal is determined to need to perform card locking operation, sending a card locking data request to the card locking server;
and receiving card locking data responded by the card locking server based on the card locking data request, and writing the card locking data into the target terminal so that the target terminal locks the card according to the card locking logic of the card locking data, and the target terminal does not record the card locking data.
2. The terminal card locking method according to claim 1, wherein the determining whether the operation type indicated by the operation indication is before card locking operation further comprises:
judging whether the target terminal supports a card locking function or not;
and when the target terminal is determined to support the card locking function, executing the step of judging whether the card locking operation is required to be carried out on the target terminal.
3. The terminal card locking method according to claim 1, wherein after determining whether the operation type indicated by the operation indication is a card locking operation, the method further comprises:
when the target terminal is determined not to need to be locked, confirming that the target terminal is in a locked state;
sending an unlocking data request to the card locking server, and receiving unlocking data responded by the card locking server based on the unlocking data request;
and unlocking the target terminal in the locked state through the unlocking data.
4. A terminal card-locking method according to any one of claims 1 to 3, wherein after writing the card-locking data into the target terminal, the method further comprises:
receiving a card locking result sent by the target terminal after the card locking operation is executed;
and associating the card locking result with the terminal identification information of the target terminal, and uploading the association relationship between the card locking result and the terminal identification information of the target terminal to the card locking server.
5. The terminal card locking method according to claim 4, wherein after the uploading the association relationship between the card locking result and the terminal identification information to the card locking server, further comprising:
acquiring terminal identification information of a terminal to be delivered from a factory;
calling the incidence relation maintained by the card locking server, and inquiring a card locking result corresponding to the terminal to be delivered from the factory;
and when the card locking result is successful card locking, outputting a factory-allowed instruction corresponding to the terminal to be factory.
6. The terminal card locking method according to claim 4, wherein before associating the card locking result with the terminal identification information of the target terminal, the method further comprises:
when the card locking result is unsuccessful card locking, repeating the card locking operation of the target terminal, and receiving the card locking result sent by the target terminal;
and when the card locking result is that the number of times of unsuccessful card locking reaches a preset number threshold value, executing the step of associating the card locking result with the terminal identification information of the target terminal.
7. The terminal card locking device is characterized by being applied to a card locking tool and comprising:
the judging module is used for acquiring the terminal identification information of the target terminal; calling an operation index table maintained by a card locking server, and inquiring an operation instruction corresponding to the terminal identification information of the target terminal; judging whether the operation type indicated by the operation instruction is card locking operation or not according to the inquired operation instruction; when the operation type indicated by the operation instruction is a card locking operation, the card locking operation needs to be performed on the target terminal;
the request module is used for sending a card locking data request to the card locking server when the target terminal is determined to need to perform card locking operation;
and the card locking module is used for receiving card locking data responded by the card locking server based on the card locking data request and writing the card locking data into the target terminal so that the target terminal locks the card according to the card locking logic of the card locking data, and the target terminal does not record the card locking data.
8. An electronic device, comprising: memory, processor and computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any one of claims 1 to 6 when executing the computer program.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910772579.6A CN110505225B (en) | 2019-08-21 | 2019-08-21 | Terminal card locking method and device and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910772579.6A CN110505225B (en) | 2019-08-21 | 2019-08-21 | Terminal card locking method and device and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110505225A CN110505225A (en) | 2019-11-26 |
| CN110505225B true CN110505225B (en) | 2022-05-17 |
Family
ID=68588662
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910772579.6A Active CN110505225B (en) | 2019-08-21 | 2019-08-21 | Terminal card locking method and device and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110505225B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112073961B (en) * | 2020-09-08 | 2023-07-04 | Oppo广东移动通信有限公司 | SIM card state updating method and device, terminal and readable storage medium |
| CN112738789B (en) * | 2020-12-21 | 2024-01-05 | 深圳酷派技术有限公司 | SIM card locking method and device, storage medium and electronic equipment |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101437067A (en) * | 2008-12-05 | 2009-05-20 | 中兴通讯股份有限公司 | Mobile terminal and method for implementing network and card locking |
| CN101778375A (en) * | 2009-12-25 | 2010-07-14 | 中兴通讯股份有限公司 | Method for managing terminal lock card/lock network, communication system and terminal |
| CN101800986A (en) * | 2010-02-26 | 2010-08-11 | 华为终端有限公司 | Method and device for realizing network locking and unlocking of terminal |
| CN102300204A (en) * | 2011-08-26 | 2011-12-28 | 中兴通讯股份有限公司 | Wireless terminal and lockup method and system thereof |
| CN104469736A (en) * | 2014-11-05 | 2015-03-25 | 中兴通讯股份有限公司 | Data processing method, server and terminal |
| EP3093802A1 (en) * | 2006-12-20 | 2016-11-16 | Lenovo Innovations Limited (Hong Kong) | Mobile terminal and control program thereof |
| CN106211203A (en) * | 2015-04-29 | 2016-12-07 | 中兴通讯股份有限公司 | Lock network data updating method and device |
| CN106791171A (en) * | 2017-01-16 | 2017-05-31 | 北京奇虎科技有限公司 | A kind of card-locking method of mobile terminal, device and mobile terminal |
| WO2018076148A1 (en) * | 2016-10-25 | 2018-05-03 | 深圳市佳润鑫信息技术有限公司 | Cracking preventing method for network locking information of terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2007148999A (en) * | 2005-11-30 | 2007-06-14 | Fujitsu Ltd | Portable apparatus, id card function lock control program, and ic card function lock control method |
-
2019
- 2019-08-21 CN CN201910772579.6A patent/CN110505225B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3093802A1 (en) * | 2006-12-20 | 2016-11-16 | Lenovo Innovations Limited (Hong Kong) | Mobile terminal and control program thereof |
| CN101437067A (en) * | 2008-12-05 | 2009-05-20 | 中兴通讯股份有限公司 | Mobile terminal and method for implementing network and card locking |
| CN101778375A (en) * | 2009-12-25 | 2010-07-14 | 中兴通讯股份有限公司 | Method for managing terminal lock card/lock network, communication system and terminal |
| CN101800986A (en) * | 2010-02-26 | 2010-08-11 | 华为终端有限公司 | Method and device for realizing network locking and unlocking of terminal |
| CN102300204A (en) * | 2011-08-26 | 2011-12-28 | 中兴通讯股份有限公司 | Wireless terminal and lockup method and system thereof |
| CN104469736A (en) * | 2014-11-05 | 2015-03-25 | 中兴通讯股份有限公司 | Data processing method, server and terminal |
| CN106211203A (en) * | 2015-04-29 | 2016-12-07 | 中兴通讯股份有限公司 | Lock network data updating method and device |
| WO2018076148A1 (en) * | 2016-10-25 | 2018-05-03 | 深圳市佳润鑫信息技术有限公司 | Cracking preventing method for network locking information of terminal |
| CN106791171A (en) * | 2017-01-16 | 2017-05-31 | 北京奇虎科技有限公司 | A kind of card-locking method of mobile terminal, device and mobile terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110505225A (en) | 2019-11-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106453415B (en) | Block chain-based equipment authentication method, authentication server and user equipment | |
| CN110309125B (en) | Data verification method, electronic device and storage medium | |
| CN109815291B (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN109684347B (en) | Account checking method, account checking device, computer equipment and storage medium | |
| CN110505225B (en) | Terminal card locking method and device and computer readable storage medium | |
| CN111130602B (en) | Near field communication card data writing system, method, device and medium | |
| CN109165175B (en) | Equipment identifier generation method and device | |
| CN105260639A (en) | Face recognition system data update method and device | |
| CN105072608B (en) | A kind of method and device of administrative authentication token | |
| CN107566518B (en) | Method and device for managing equipment information in file installation process | |
| CN107844305A (en) | The method for upgrading software and embedded device of embedded device | |
| CN110175833B (en) | Computer device, method, system and medium for binding bank card information | |
| US20090271449A1 (en) | Work support apparatus for information processing device | |
| CN108491466B (en) | Electronic device, access instruction information acquisition method, and storage medium | |
| CN111027984A (en) | Business order processing method and system, electronic equipment and computer storage medium | |
| CN108121774B (en) | Data table backup method and terminal equipment | |
| CN108133026B (en) | Multi-data processing method, system and storage medium | |
| CN113112266A (en) | Multi-card processing method and system based on 5G message and block chain | |
| CN115878338A (en) | Market situation task processing method and device, computer equipment and readable storage medium | |
| CN112131180B (en) | Data reporting method, device and storage medium | |
| CN114691397A (en) | Disk repairing method and device, electronic equipment and storage medium | |
| CN114186976A (en) | Workflow transfer method and device, computer equipment and storage medium | |
| CN110677378B (en) | Control method of MAC address, intelligent terminal and storage medium | |
| CN111258808B (en) | Method, apparatus, device and medium for data automation management | |
| CN111767299A (en) | Database operation method, device and system, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |