WO2012092727A1 - 移动终端锁卡的方法、装置和系统 - Google Patents

移动终端锁卡的方法、装置和系统 Download PDF

Info

Publication number
WO2012092727A1
WO2012092727A1 PCT/CN2011/072449 CN2011072449W WO2012092727A1 WO 2012092727 A1 WO2012092727 A1 WO 2012092727A1 CN 2011072449 W CN2011072449 W CN 2011072449W WO 2012092727 A1 WO2012092727 A1 WO 2012092727A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile terminal
imsi
dongle
lock
lock data
Prior art date
Application number
PCT/CN2011/072449
Other languages
English (en)
French (fr)
Inventor
陈健
韩春元
李学军
傅曦平
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012092727A1 publication Critical patent/WO2012092727A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50Service provisioning or reconfiguring

Definitions

  • the present invention relates to the field of communications, and in particular to a method, apparatus, and system for a mobile terminal to lock a card.
  • BACKGROUND In recent years, with the rapid development of mobile phone technology and the global popularity of 3G networks and the intensification of competition among operators, wireless terminal devices are mostly customized by operators, and operators have also proposed higher customized services. Requirement, when operators customize mobile terminal products, for the needs of operators and user security, it is often required to require a mobile terminal to lock one or a batch of (U) SIM (Subscriber Identity Module). Lock system requirements such as cards (ie user identification cards). After the mobile terminal completes the operation of locking to a specific card, the terminal is required to use only this specific card, and other cards cannot be used normally on the terminal.
  • SIM Subscriber Identity Module
  • a primary object of the present invention is to provide a method, apparatus, and system for a mobile terminal to lock a card,
  • a method for locking a card of a mobile terminal including: when the mobile terminal is powered on, checking whether the boot condition is met according to the lock data in the dongle; if yes, the mobile terminal starts normally; , The mobile terminal failed to start.
  • the mobile terminal checks whether the boot condition is met according to the lock data in the dongle: the mobile terminal reads the lock data from itself; the mobile terminal compares whether the read lock data matches the lock data in the dongle; if matched, the mobile terminal Determine that the start condition is met; if it does not match, the mobile terminal determines that the start condition is not met.
  • the lock data includes: an international mobile device identifier IMEI and an international mobile subscriber identity IMSI; whether the mobile terminal compares the read lock data with the lock data in the dongle includes: the mobile terminal sends the read IMEI to the dongle After receiving the IMEI, the dongle checks whether the IMEI is stored in the database, and if so, sends the IMSI corresponding to the IMEI in the database to the mobile terminal; if not, disconnects the communication with the mobile terminal; the mobile terminal receives the IMSI from the dongle; Comparing whether the received IMSI matches the IMSI of the currently inserted subscriber identity card, and if so, the mobile terminal determines that the read lock data matches the lock data in the dongle; if not, the mobile terminal determines the read lock data and software The lock data in the dog does not match.
  • IMEI international mobile device identifier IMEI and an international mobile subscriber identity IMSI
  • the IMSI corresponding to the IMEI in the database is multiple; whether the mobile terminal compares the received IMSI with the IMSI of the currently inserted subscriber identity card includes: The mobile terminal compares whether the received IMSI has the same IMSI as the currently inserted subscriber identity card. The IMSI, if so, the mobile terminal determines that the received IMSI matches the IMSI of the currently inserted subscriber identity card, and if not, the mobile terminal determines that the received IMSI does not match the IMSI of the currently inserted subscriber identity card.
  • the method further includes: the software dog updates the lock data in the database by establishing communication with the computer PC.
  • a device for locking a card of a mobile terminal including: an checking module, configured to check whether the boot condition is met according to the lock data in the dongle when the mobile terminal is powered on; wherein the dongle is The device for checking the lock configured for the mobile terminal; the normal startup module, when the check result of the check module is set to Yes, the mobile terminal is allowed to start normally; the startup failure module is set to check if the check result of the module is no, the movement is set The terminal failed to start.
  • the checking module includes: a reading unit configured to read the locking data of the mobile terminal; a comparing unit configured to compare whether the read locking data matches the locking data in the dongle; if matching, determining that the mobile terminal meets the starting condition If there is no match, make sure the mobile terminal does not meet the start condition.
  • the reading unit comprises: a reading subunit, configured to read the locking data of the mobile terminal, the locking data comprises: an international mobile device identifier IMEI and an international mobile subscriber identity IMSI; the comparing unit comprises: a sending subunit, configured to Sending the read IMEI to the dongle; the receiving subunit is configured to receive the IMSI from the dongle, wherein, after the IMSI receives the IMEI, the IMSI stores the IMEI stored in the database, and sends the IMSI corresponding to the IMEI in the database to a comparison subunit, configured to compare whether the received IMSI matches the IMSI of the currently inserted subscriber identity card, and if so, determine that the lock data read by the mobile terminal matches the lock data in the dongle; if not, determine The lock data read by the mobile terminal does not match the lock data in the dongle.
  • a reading subunit configured to read the locking data of the mobile terminal, the locking data comprises: an international mobile device identifier IMEI and an international mobile subscribe
  • the comparison subunit includes: a matching subunit, configured to compare whether the IMSI received by the receiving subunit has an IMSI identical to the IMSI 4 of the currently inserted subscriber identity card when the IMSI corresponding to the IMEI in the database is multiple. 3 ⁇ 4. If so, the IMSI of the mobile terminal is determined to match the IMSI of the currently inserted subscriber identity card. If not, it is determined that the IMSI received by the mobile terminal does not match the IMSI of the currently inserted subscriber i card.
  • a system for a mobile terminal lock card including: a mobile terminal, the mobile terminal includes the above device, the system further includes a dongle; the dongle includes: a lock data providing module, It is arranged to provide the mobile terminal with the lock data corresponding to the mobile terminal.
  • the system further includes a computer PC, configured to write lock data to the dongle; the dongle further includes: a lock data update module, configured to establish communication with the PC, and update the lock data in the database.
  • the software dog is used to save the lock data, which overcomes the defect that the lock data saved by the mobile terminal in the related art is easily rewritten and erased, and solves the problem that the mobile terminal locks the (U)SIM card to have a safety hazard, and conforms to the movement.
  • the original intention of the terminal lock card service has greatly protected the interests of operators.
  • FIG. 1 is a flow chart of a method for locking a mobile terminal according to a first embodiment of the present invention
  • FIG. 2 is a flow chart of a software dog connecting a PC for data update according to Embodiment 1 of the present invention
  • 3 is a flowchart of a method for implementing a wireless terminal device lock (U) SIM card according to Embodiment 2 of the present invention
  • FIG. 4 is a structural block diagram of a device for locking a mobile terminal according to Embodiment 3 of the present invention
  • FIG. 6 is a structural block diagram of a mobile terminal according to Embodiment 4 of the present invention
  • FIG. 7 is a block diagram of another mobile terminal lock card according to Embodiment 4 of the present invention
  • the embodiment of the invention implements the locking of the (U)SIM card by the mobile terminal based on the software dog.
  • the solution is to save the locking data of each mobile terminal through the dongle, for example, the unique IMEI of the mobile terminal (International Mobile Equipment Identity, international mobile device identity) Code) and each (U)SIM card unique IMSI (International Mobile Subscriber Identifier), locked data stored in the dongle to implement the mobile terminal lock (U) SIM card.
  • FIG. 1 is a flowchart of a method for locking a card of a mobile terminal according to an embodiment of the present invention.
  • the mobile terminal in the method is configured with a dongle for checking a lock, and the set is pre-stored in the dongle.
  • Step S102 when the mobile terminal is powered on, according to the lock in the dongle Whether the data check is in compliance with the start condition; if yes, indicating that the mobile terminal is in a locked relationship with the currently inserted user identification card, that is, the two match, step S104 is performed; if not, the mobile terminal and the currently inserted user identification card are in an unlock relationship. , that is, the two do not match, step S 106 is performed; when the mobile terminal of the embodiment is powered on, the mobile terminal is connected to the dongle through a USB cable.
  • Checking whether the boot condition is met according to the lock data in the dongle of the embodiment may include: the mobile terminal reads the lock data from itself, and the mobile terminal compares whether the read lock data matches the lock data in the dongle, if matched, moves The terminal determines that the start condition is met; if not, the mobile terminal determines that the start condition is not met; wherein, the lock data includes: IMEI and IMSI; at this time, the mobile terminal compares whether the read lock data matches the lock data in the dongle includes: The mobile terminal sends the read IMEI to the dongle; after receiving the IMEI, the dongle checks whether the IMEI is stored in the database, and if so, sends the IMSI corresponding to the IMEI in the database to the mobile terminal; if not, disconnects and moves Communication of the terminal; the mobile terminal receives the IMSI from the dongle, compares whether the received IMSI matches the IMSI of the currently inserted subscriber identity card, and if so, the mobile terminal determines that the read
  • the mobile terminal reads its own lock data, which can be implemented by an AT command, and can store the read lock data in a temporary variable.
  • Step 4 gathers S 104, the mobile terminal starts normally;
  • Step 4 gathers S 106, and the mobile terminal fails to start.
  • the mobile terminal of this embodiment needs to connect the dongle by USB before booting.
  • the mobile terminal initializes, it reads the IMEI number of the machine and the IMSI number of the (U) SIM card, and then detects whether the dongle has been connected. If it is detected that it is not connected, please prompt to connect the dongle and it cannot be turned on. If it detects that it is connected, start the communication program and communicate with the dongle.
  • the IMEI number of the machine as the data and the software dog to carry out the risk communication. If the local IMEI number can be searched in the dongle, then the danger certificate is successful, the software dog is allowed to continue communication, otherwise the danger certificate fails, the software dog closes the communication, and the mobile terminal prompts that the danger certificate fails and cannot be turned on.
  • the dongle uses the mobile terminal IMEI
  • the index is searched in the dongle storage area, and the searched corresponding IMSI number is fed back to the mobile terminal, and the mobile terminal compares the IMSI number obtained by the feedback with the IMSI of the (U) SIM card currently inserted into the wireless terminal, if the local machine has been inserted If the IMSI number of the (U) SIM card matches the local IMEI number, the mobile mobile terminal starts normally. Otherwise, the lock (U) SIM card fails to be detected and cannot be turned on.
  • the lock data is saved by the dongle, which overcomes the defect that the lock data saved by the mobile terminal in the related art is easily rewritten and erased, and solves the problem that the mobile terminal locks the (U)SIM card to have a security risk, and conforms to the mobile terminal lock.
  • the original intention of the card service has greatly protected the interests of operators.
  • a batch lock (U) SIM card for example, a batch of (U) SIM cards can be normally used on any one of a batch of mobile phone terminals, and the batch terminal can also use any of the (U) SIM cards.
  • a certain operator and equipment manufacturer has customized a number of fixed stations.
  • the users of the fixed stations can only use certain numbers with specific offers.
  • a certain company has ordered a batch of mobile phones and sent them to employees. I hope these mobile phones only The ability to use a fixed number of fixed numbers to facilitate the development and tracking of the company's business, all of which have the need to batch lock (U) SIM cards.
  • the IMSI corresponding to the IMII in the database of the dongle in this embodiment may be multiple; for example, in the software of the dongle, the IMEI is used as an index to store each IMEI to match.
  • the IMSI number can match one IMSI to each IMEI, or it can match multiple IMSIs, providing a data foundation for implementing batch lock numbers.
  • whether the mobile terminal compares the received IMSI with the IMSI of the currently inserted subscriber identity card includes: the mobile terminal compares whether the received IMSI has the same IMSI as the IMSI of the currently inserted subscriber identity card, and if so, Describe that the mobile terminal obtains the IMSI returned by the dongle, and if compared with the IMSI of the currently inserted subscriber identity card, if the same, or the IMSI of the currently inserted subscriber identity card is a subset of the IMSI returned by the dongle, the mobile terminal determines the received The IMSI matches the IMSI of the currently inserted subscriber identity card; if not, the mobile terminal determines that the received IMSI does not match the IMSI of the currently inserted subscriber i card.
  • the lock data in the dongle needs to be written to the PC by the corresponding PC side software, and the data is also rewritable in the dongle for easy updating or deletion.
  • the (U) SIM card is damaged or the user needs to change the number, it is only necessary to update the matching data of the IMEI and the IMSI in the dongle, and it is not necessary to tamper with the data of the mobile terminal or the (U) SIM card side, which is greatly facilitated.
  • the customization of the operator or enterprise user can be updated by the authorized PC side software without obtaining the special mobile terminal burning software and mobile terminal version. Based on this, the above The method further includes: the software dog updates the lock data in its own database by establishing communication with the computer PC. As shown in FIG.
  • the dongle connects to the PC for data update.
  • the updated lock data in this embodiment includes IMEI and IMSI.
  • the updating process includes the following steps: Step S201, first detecting a port, starting a communication process, determining whether the dongle is connected to the PC, and if so, executing step S202, otherwise performing step S205.
  • Step S202 the PC side inputs the matching data of the IMEI and the IMSI (corresponding to the above-mentioned locking data), and can specify one or more IMSI matching for one IMEI, so that the operation of the 4-quantity locking (U) SIM card can be realized.
  • Step S203 the PC side starts the communication flow with the dongle, and transmits the matching data of the IMEI and the IMSI to the dongle through a predetermined protocol.
  • step S204 the dongle receives the matching data and saves it to the storage area. If the imported IMEI and the existing saved IMEI are duplicated, the original matching data is overwritten.
  • step S205 the software dog closes the update process after completing the data area update. If the PC side needs to update the data again, you need to restart the communication process to start the update.
  • This embodiment is directed to some existing lock (U) SIM card solutions, which can only lock a certain number on a mobile terminal for specific use. For some problems that cannot be satisfied in the case of batch locking, use multiple settings in the dongle.
  • U existing lock
  • Step S301 Determine whether the wireless terminal device is inserted.
  • (U) SIM card if yes, execute step M1 S302, if no, perform step 4 to gather S308.
  • Step S302, determining whether the wireless terminal device has connected the dongle if yes, executing step S303; if not, executing step S308.
  • Step S303 the wireless terminal device reads the IMEI of the local machine, and the IMSI of the currently inserted (U) SIM card; and saves the read IMEI and the IMSI to the temporary variable storage.
  • Step S304 the step of verifying whether the wireless terminal device is valid.
  • the dongle is initialized, and communication is established with the wireless terminal device after the initialization is completed.
  • the wireless terminal device sends the read local IMEI number to the dongle, and the software dog searches the internal storage database. If it finds that the IMEI number is stored internally and the received IMEI number is the same, the communication continues, otherwise, the wireless terminal device is turned off. For communication, step S308 is performed. Step S305, the software dog obtains the IMEI number saved before the wireless terminal device, uses the IMEI number as an index, searches the software dog internal storage database to obtain the corresponding IMSI number, and returns the obtained IMSI to the wireless terminal device. Step S306, the wireless terminal device acquires the IMSI number returned by the dongle, and compares with the previously saved IMSI temporary variable.
  • step S307 If the same, or a previously saved IMSI number, the subset of the IMSI number group returned by the dongle, step S307 is performed. Otherwise, step S308 is performed.
  • Step S307 the wireless terminal device is allowed to be used, and the remaining boot initialization process is executed.
  • the user interface (UI) of the wireless terminal device indicates that the currently inserted (U) SIM card is disabled on the wireless terminal device, and the communication with the dongle is interrupted at the same time, and the terminal needs to be restarted to re-establish the connection.
  • FIG. 4 is a structural block diagram of an apparatus for locking a mobile terminal according to an embodiment of the present invention.
  • the apparatus may be disposed on a mobile terminal, where the mobile terminal may be a fixed station, a mobile phone, a netbook, etc., and the device includes The following modules:
  • the checking module 42 is configured to check whether the mobile terminal is powered on, according to the lock data in the dongle, and check whether the boot condition is met; wherein the dongle is a device configured for the mobile terminal to check the lock; the dongle passes the USB cable and the
  • the mobile terminal is connected to the check module 42 and is connected to the check module 42.
  • the check result of the check module 42 is YES, the mobile terminal is allowed to start normally.
  • the startup failure module 46 is connected to the check module 42 and configured as the check module 42. When the check result is no, the setting of the mobile terminal fails to start.
  • the checking module 42 comprises: a reading unit configured to read the locking data of the mobile terminal; and a comparing unit configured to compare whether the locking data read by the reading unit matches the locking data in the software dog; Matching, determining that the mobile terminal meets the start condition; if not, determining that the mobile terminal does not meet the start condition.
  • the lock data of this embodiment includes: an IMEI and an IMSI; based on the above, the reading unit includes: a read subunit configured to read lock data of the mobile terminal, wherein the lock data includes: IMEI and IMSI;
  • the comparison unit includes: a sending subunit, configured to send the read IMEI to the dongle; and a receiving subunit, configured to receive the IMSI from the dongle, wherein the IMSI checks the database for storage after receiving the IMEI for the dongle
  • the IMEI sends the IMSI corresponding to the IMEI in the database to the mobile terminal; the comparison subunit is configured to compare whether the received IMSI matches the IMSI of the currently inserted subscriber identity card, and if so, determine the lock data read by the mobile terminal and The lock data in the dongle is matched; if not, it is determined that the lock data read by the mobile terminal does not match the lock data in the dongle.
  • the IMSI in the database of the dongle in this embodiment may be multiple; for example, in the database of the dongle, the IMEI is used as an index, and each IMEI is matched.
  • the IMSI number which can match one IMSI to each IMEI, can also match multiple IMSIs, providing a data foundation for implementing batch lock numbers.
  • the comparison subunit includes: a matching subunit, configured to compare whether the IMSI received by the receiving subunit is the same as the IMSI of the currently inserted subscriber identity card when the IMSI corresponding to the IMEI in the database is multiple.
  • the lock data is saved by the dongle, which overcomes the defect that the lock data saved by the mobile terminal in the related art is easily rewritten and erased, and solves the problem that the mobile terminal locks the (U)SIM card to have a security risk, and conforms to the mobile terminal lock.
  • the original intention of the card service has greatly protected the interests of operators.
  • FIG. 5 is a block diagram showing a system structure of a mobile terminal lock card according to an embodiment of the present invention.
  • the system includes a mobile terminal 40, wherein the mobile terminal includes a device for locking a mobile terminal in Embodiment 3, and the device
  • the structure of each module can be as shown in FIG. 4, and the functions and implementation manners of the modules are the same as those in Embodiment 3, and will not be described in detail herein.
  • the system further includes a dongle 50; the dongle 50 includes: a lock data providing module 52 configured to provide the mobile terminal 40 with lock data corresponding to the mobile terminal 40.
  • the lock data on the dongle 50 in this embodiment can also be updated as needed.
  • the system further includes a computer PC for writing the lock data to the dongle 50.
  • the dongle 50 further includes: Lock the data update module, set up to establish communication with the PC, and update the lock data in its own database. Another configuration diagram of the mobile terminal shown in FIG.
  • the mobile terminal includes: a determining module 61 configured to determine whether the software dog is connected to the wireless terminal device by detecting the port, and if yes, proceeding In one step, if it is not detected, the user is prompted to be unable to boot, and the dongle needs to be connected for verification.
  • the mobile phone side information reading unit 62 reads the IMEI and the insertion of the machine by means of an AT command or the like.
  • the software dog side information reading unit 63 the function of the unit is to communicate with the dongle through a serial port, using a predetermined protocol, and send the risk data (in the present embodiment, the above IMEI) to the dongle, and read the dongle feedback. IMSI data.
  • the verification unit 64 is configured to continue the next module operation if the dongle feedback verification is passed, and if the feedback verification fails, the process is stopped, prompting the user to fail to boot, and the verification fails.
  • the calculating unit 65 compares the IMSI data read by the software dog side information reading unit 63 with the IMSI of the currently inserted (U) SIM card read by the local device, if the same or the intra-dog matching A subset of the data results in a matching match, otherwise the output does not match.
  • the permission/inhibition use determining unit 66 according to the matching result of the calculating unit 65, allows the mobile terminal to be used if it matches, and if not, prohibits the mobile terminal from being used.
  • a software dog and its supporting PC end software tool are provided.
  • FIG. 7 is a block diagram of a system structure of another mobile terminal lock card provided by an embodiment of the present invention, as shown in FIG.
  • the system includes a PC device 70, a dongle 80, and a mobile terminal 90.
  • the PC device 70 includes a PC-side software tool module 72.
  • the dongle 80 includes a communication module 82, a data receiving module 84, a storage module 86, and a computing module 88.
  • the PC end software tool module 72 is configured to communicate with the dongle, and can transmit the IMSI corresponding to the IMEI in the lock (U) SIM card data to the data receiving module 84 of the dongle.
  • the module uses serial communication to communicate with the dongle 80 in accordance with a predetermined protocol.
  • the communication module 82 is configured to communicate with the mobile terminal, and verify whether the mobile terminal has communication authority according to a predetermined communication protocol through the serial port, and receive the lock (U) SIM card data (IMEI and IMSI) transmitted by the mobile terminal 90, and determine The validity of the data. If the data is valid, it is transmitted to the calculation module 88. Finally, the verification matching result fed back by the calculation module 88 is fed back to the mobile terminal 90.
  • the data receiving module 84 is configured to communicate with the PC end software tool module 72 and receive the IMEI/IMSI lock (U) SIM card matching data, and finally save to the storage module 86.
  • the calculation module 88 searches for the matching IMSI number in the storage module 86 by using the received IMEI and IMSI number transmitted by the communication module 82, and feeds back the result to the communication module 82.
  • the storage module 86 stores the matching data of the IMEI and the IMSI.
  • the lock data is saved by the dongle, which overcomes the defect that the lock data saved by the mobile terminal in the related art is easily rewritten and erased, and solves the problem that the mobile terminal locks the (U)SIM card to have a security risk, and conforms to the mobile terminal lock.
  • the original intention of the card service has greatly protected the interests of operators.
  • this embodiment only needs to add the initial ⁇ check part in the code processing of the mobile terminal, and does not need to save any lock/unlock information, even if the (U) SIM card and the terminal software version are replaced, there is no need to reconfigure, There is no possibility of being cracked and tampered with.
  • the embodiment of the present invention prevents the lock data saved by the mobile terminal from being easily rewritten and erased by storing the lock data of the mobile terminal in the dongle, and can update the dongle as needed.
  • the locking data facilitates the user to use the mobile terminal of the lock card function, which increases the flexibility of use.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

移动终端锁卡的方法、 装置和系统 技术领域 本发明涉及通信领域, 具体而言, 涉及一种移动终端锁卡的方法、 装置 和系统。 背景技术 近年来随着手机技术的迅猛发展和 3G网络在全球的普及以及运营商之 间竟争的加剧, 无线终端设备较多地由运营商定制, 运营商对定制服务也提 出了更高的要求, 运营商在定制移动终端产品时, 出于运营商的需求以及用 户安全等考虑, 往往会提出要求某个移动终端锁定一张或者一批 (U ) SIM ( Subscriber Identity Module , 用户识别模块)卡 (即用户识别卡) 等锁系统 需求。 当移动终端完成了锁定到某种特定卡的操作后, 要求此终端只能使用此 特定的卡, 其他卡无法在此终端上正常使用。 这样运营商就能够有效的解决 用户私自转网、 私自进行窜货、 以及客户群流失等问题。 从而使得运营商确 保在促销时购买的电话的消费者满足其协议条款, 只要消费者在相对长的时 间内使用特定的预定, 就可以以非常低的价格购买电话及其服务。 运营商对锁定 (U)SIM卡的安全性提出了很高的要求,但是, 目前还没有 能够有效保护锁定 (U)SIM卡相关的敏感数据,以及防止黑客破解锁定 (U)SIM 卡的安全有效机制。现有的一些锁定 (U)SIM卡的技术往往依赖于在终端或者 ( U ) SIM卡侧保存一些锁定 /解锁控制信息, 这就给破解和修改锁定带来了 漏洞。 比如, 有的锁定 (U)SIM卡方案需要在移动终端内, 以配置信息形式写 入所获取的锁定 /解锁控制信息, 比如保存在手机固件 Flash某个标志位或者 固定的一段存储, 由于这些控制信息保存在本地终端存储器, 这样一旦终端 被重新烧入版本, 或者该控制信息被破解或者改写,锁定 (U)SIM卡方案就会 失效。 针对相关技术中移动终端锁定 (U)SIM卡存在安全隐患的问题, 目前尚未 提出有效的解决方案。 发明内容 本发明的主要目的在于提供一种移动终端锁卡的方法、 装置和系统, 以
根据本发明的一个方面, 提供了一种移动终端锁卡的方法, 包括: 移动 终端通电开机时,根据软件狗中的锁定数据检查是否符合启动条件; 如果是, 该移动终端正常启动; 如果否, 该移动终端启动失败。 其中, 移动终端根据软件狗中的锁定数据检查是否符合启动条件包括: 移动终端从自身读取锁定数据; 移动终端比较读取的锁定数据是否与软件狗 中的锁定数据匹配; 如果匹配, 移动终端确定符合启动条件; 如果不匹配, 移动终端确定不符合启动条件。 其中, 锁定数据包括: 国际移动设备识别码 IMEI和国际移动用户识别 码 IMSI; 移动终端比较读取的锁定数据是否与软件狗中的锁定数据匹配包 括: 移动终端将读取的 IMEI发送给软件狗; 软件狗接收到 IMEI后, 检查数 据库中是否存储有 IMEI, 如果是, 将数据库中 IMEI对应的 IMSI发送给移 动终端;如果否,断开与移动终端的通讯;移动终端接收来自软件狗的 IMSI, 比较接收的 IMSI与当前插入的用户识别卡的 IMSI是否匹配, 如果是, 移动 终端确定读取的锁定数据和软件狗中的锁定数据匹配; 如果否, 移动终端确 定读取的锁定数据和软件狗中的锁定数据不匹配。 其中, 数据库中 IMEI对应的 IMSI为多个; 移动终端比较接收的 IMSI 与当前插入的用户识别卡的 IMSI是否匹配包括: 移动终端比较接收的 IMSI 中是否有与当前插入的用户识别卡的 IMSI相同的 IMSI, 如果是, 移动终端 确定接收的 IMSI与当前插入的用户识别卡的 IMSI匹配, 如果否, 移动终端 确定接收的 IMSI与当前插入的用户识别卡的 IMSI不匹配。 其中, 该方法还包括: 软件狗通过与电脑 PC建立通讯, 更新自身数据 库中的锁定数据。 根据本发明的另一方面, 提供了一种移动终端锁卡的装置, 包括: 检查 模块, 设置为移动终端通电开机时, 根据软件狗中的锁定数据检查是否符合 启动条件; 其中, 软件狗是为移动终端配置的用于检查锁定的设备; 正常启 动模块, 设置为检查模块的检查结果为是时, 允许移动终端正常启动; 启动 失败模块, 设置为检查模块的检查结果为否时, 设置移动终端启动失败。 其中, 检查模块包括: 读取单元, 设置为读取移动终端的锁定数据; 比 较单元, 设置为比较读取的锁定数据是否与软件狗中的锁定数据匹配; 如果 匹配, 确定移动终端符合启动条件; 如果不匹配, 确定移动终端不符合启动 条件。 其中, 读取单元包括: 读取子单元, 设置为读取移动终端的锁定数据, 锁定数据包括: 国际移动设备识别码 IMEI和国际移动用户识别码 IMSI; 比 较单元包括: 发送子单元, 设置为将读取的 IMEI发送给软件狗; 接收子单 元, 设置为接收来自软件狗的 IMSI, 其中, IMSI为软件狗接收到 IMEI后, 检查数据库中存储有 IMEI, 将数据库中 IMEI对应的 IMSI发送给移动终端 的; 比较子单元, 设置为比较接收的 IMSI与当前插入的用户识别卡的 IMSI 是否匹配, 如果是, 确定移动终端读取的锁定数据和软件狗中的锁定数据匹 配; 如果否, 确定移动终端读取的锁定数据和软件狗中的锁定数据不匹配。 其中, 比较子单元包括: 匹配子单元, 设置为当数据库中 IMEI对应的 IMSI为多个时, 比较接收子单元接收的 IMSI中是否有与当前插入的用户识 别卡的 IMSI 4目同的 IMSI, ¾。果是, 确定移动终端接) 的 IMSI与当前插入 的用户识别卡的 IMSI匹配, 如果否, 确定移动终端接收的 IMSI与当前插入 的用户 i只别卡的 IMSI不匹配。 才艮据本发明的又一方面, 提供了一种移动终端锁卡的系统, 包括: 移动 终端, 该移动终端包括上述装置, 该系统还包括软件狗; 该软件狗包括: 锁 定数据提供模块, 设置为向该移动终端提供该移动终端对应的锁定数据。 其中, 系统还包括电脑 PC, 设置为向软件狗中写入锁定数据; 软件狗还 包括: 锁定数据更新模块, 设置为与 PC建立通讯, 更新自身数据库中的锁 定数据。 通过本发明, 釆用软件狗来保存锁定数据, 克服了相关技术中移动终端 保存的锁定数据容易被改写和擦除的缺陷,解决了移动终端锁定 (U)SIM卡存 在安全隐患的问题, 符合移动终端锁卡艮务的初衷, 更大地保护了运营商的 利益。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部 分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的 不当限定。 在附图中: 图 1是才艮才艮据本发明实施例 1的移动终端锁卡的方法流程图; 图 2是根据本发明实施例 1的软件狗连接 PC进行数据更新的流程图; 图 3是才艮据本发明实施例 2的实现无线终端设备锁定 (U ) SIM卡的方 法流程图; 图 4是 居本发明实施例 3的移动终端锁卡的装置的结构框图; 图 5是 居本发明实施例 4的移动终端锁卡的系统的结构框图; 图 6是 居本发明实施例 4的移动终端的结构框图; 图 7是 居本发明实施例 4的另一种移动终端锁卡的系统的结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在 不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互组合。 本发明实施例基于软件狗实现移动终端对 (U)SIM卡的锁定,该方案是通 过软件狗保存每个移动终端的锁定数据, 例如移动终端唯一的 IMEI ( International Mobile Equipment Identity , 国际移动设备 别码) 和每张 (U)SIM卡唯一的 IMSI ( International Mobile Subscriber Identifier, 国际移动 用户识别码), 居软件狗中保存的锁定数据来实现移动终端锁定 (U)SIM卡。 整个过程中, 通过把锁定数据放置于软件狗中, 极大的提高了锁定的灵活性 和安全性。 基于此, 本发明实施例提供了一种移动终端锁卡的方法、 装置和 系统。 实施例 1 图 1示出了才艮据本发明实施例的移动终端锁卡的方法流程图, 该方法中 的移动终端配置有用于检查锁定的软件狗, 该软件狗中预先存入设定的用于 表示终端锁定 (U)SIM卡策略的锁定数据, 该移动终端可以是固定台, 手机, 上网本等, 该方法包括以下步 4聚: 步骤 S 102, 移动终端通电开机时, 根据软件狗中的锁定数据检查是否符 合启动条件; 如果是, 说明移动终端与当前插入的用户识别卡为锁定关系, 即二者匹配, 执行步骤 S 104; 如果否, 移动终端与当前插入的用户识别卡为 非锁定关系, 即二者不匹配, 执行步骤 S 106; 本实施例的移动终端开机时, 该移动终端通过 USB线与软件狗相连。本 实施例的根据软件狗中的锁定数据检查是否符合启动条件可以包括: 移动终 端从自身读取锁定数据, 移动终端比较读取的锁定数据是否与软件狗中的锁 定数据匹配, 如果匹配, 移动终端确定符合启动条件; 如果不匹配, 移动终 端确定不符合启动条件; 其中, 锁定数据包括: IMEI和 IMSI; 此时, 移动终端比较读取的锁定 数据是否与软件狗中的锁定数据匹配包括: 移动终端将读取的 IMEI发送给 软件狗; 软件狗接收到 IMEI后,检查数据库中是否存储有该 IMEI, 如果是, 将数据库中 IMEI对应的 IMSI发送给移动终端; 如果否, 断开与移动终端的 通讯; 移动终端接收来自软件狗的 IMSI, 比较接收的 IMSI与当前插入的用 户识别卡的 IMSI是否匹配, 如果是, 移动终端确定读取的锁定数据和软件 狗中的锁定数据匹配; 如果否, 移动终端确定读取的锁定数据和软件狗中的 锁定数据不匹配。 本实施例中, 移动终端读取自身的锁定数据, 可以通过 AT命令实现, 并可以将读取的锁定数据保存在临时变量中。 步 4聚 S 104, 该移动终端正常启动; 步 4聚 S 106, 该移动终端启动失败。 本实施例的移动终端在开机前需要通过 USB方式连接软件狗,移动终端 在初始化时, 读取本机的 IMEI号和 (U ) SIM卡的 IMSI号, 然后检测是否 已经连接了软件狗, 如果检测到未连接, 则提示请连接软件狗, 无法开机; 如果检测到已连接, 则启动通讯程序和软件狗进行通讯, 首先以本机 IMEI 号为-险证数据和软件狗进行 -险证通讯, 如果本机 IMEI号能够在软件狗内被 搜索到, 则 -险证成功, 软件狗允许继续通讯, 否则 -险证失败, 软件狗关闭通 讯,移动终端提示 -险证失败,无法开机。 -险证通过后,软件狗以移动终端 IMEI 号为索引在软件狗存储区搜索, 把搜索到对应的 IMSI 号反馈给移动终端, 移动终端把反馈获得的 IMSI号与当前插入无线终端的 (U ) SIM卡的 IMSI 比较, 若已插入本机的 ( U ) SIM卡的 IMSI号与本机 IMEI号匹配, 则移动 移动终端正常启动, 否则, 锁定 (U)SIM卡检查失败, 无法开机。 本实施例通过软件狗来保存锁定数据, 克服了相关技术中移动终端保存 的锁定数据容易被改写和擦除的缺陷 ,解决了移动终端锁定 (U)SIM卡存在安 全隐患的问题,符合移动终端锁卡服务的初衷, 更大地保护了运营商的利益。 本实施例为了实现批量锁定 (U ) SIM 卡, 例如一批 ( U ) SIM 卡能在 一批手机终端中任何一个上正常使用, 而这批终端也可以使用这批( U ) SIM 卡中任何一张。 例如某运营商和设备商定制了一批固定台, 同时希望用户这 批固定台只能使用某些具有特定优惠的号码, 又比如某某公司订购了一批手 机发给员工, 希望这些手机只能使用某一批固定的号码, 便于公司业务的开 展和追踪, 以上这些情况都有批量锁定 (U ) SIM卡的需求。 基于上述批量锁定 (U ) SIM 卡的需求, 本实施例软件狗的数据库中的 IMEI对应的 IMSI可以为多个; 例如, 在软件狗的数据库中, 以 IMEI为索 引,存储每个 IMEI相匹配的 IMSI号,即可以给每一个 IMEI匹配一个 IMSI, 也可以匹配多个 IMSI, 为实现批量锁定号码提供了数据基础。 这种情况下, 上述移动终端比较接收的 IMSI与当前插入的用户识别卡的 IMSI是否匹配包 括: 移动终端比较接收的 IMSI中是否有与当前插入的用户识别卡的 IMSI相 同的 IMSI, 如果是, 说明移动终端获取软件狗返回的 IMSI, 与当前插入的 用户识别卡的 IMSI相比较, 如果相同, 或者当前插入的用户识别卡的 IMSI 为软件狗返回的 IMSI的子集, 则移动终端确定接收的 IMSI与当前插入的用 户识别卡的 IMSI匹配; 如果否, 移动终端确定接收的 IMSI与当前插入的用 户 i只别卡的 IMSI不匹配。 优选地, 软件狗中的锁定数据需要通过连接 PC, 用相应的 PC侧软件写 入, 该数据在软件狗内也是可擦写的, 便于更新或者删除。 这样当 (U ) SIM 卡损坏或者用户需要更改号码时,只需要更新软件狗内的 IMEI和 IMSI的匹 配数据即可, 不需要重新爹改移动终端或者 (U ) SIM 卡侧的数据, 大大方 便了运营商或者企业用户的定制, 只要获得授权的 PC侧软件就可以自行更 新, 而不需要获取专门的移动终端烧录软件和移动终端版本。 基于此, 上述 方法还包括: 软件狗通过与电脑 PC建立通讯, 更新自身数据库中的锁定数 据。 如图 2所示的软件狗连接 PC进行数据更新的流程图, 本实施例中更新 的锁定数据包括 IMEI和 IMSI。 该更新过程包括以下步骤: 步骤 S201 , 首先检测端口, 开始通讯流程, 判断软件狗是否已经连接至 PC, 如果连接, 则执行步骤 S202, 否则执行步骤 S205。 步骤 S202, PC侧输入 IMEI和 IMSI的匹配数据(相当于上述锁定数据 ), 可以为一个 IMEI指定一个或者多个 IMSI匹配,这样的话就可以实现 4比量锁 定 (U)SIM卡的操作。 步骤 S203 , PC侧开始和软件狗的通讯流程, 通过预定的协议传输 IMEI 和 IMSI的匹配数据给软件狗。 步骤 S204,软件狗接收匹配数据后保存至存储区,如果导入的某个 IMEI 和现有保存的 IMEI重复, 则覆盖原有匹配数据。 步骤 S205 , 软件狗完成数据区更新后关闭这一更新流程。 如果 PC侧需 要再次更新数据, 则需要重新启动通讯流程开始更新。 本实施例针对现有的一些锁定 (U)SIM 卡方案只能锁定某一个号码在一 个移动终端上特定使用, 对于有些需要批量锁定的情况无法满足的问题, 釆 用在软件狗中设置多个 IMSI与 IMEI相对应, 同时, 还可以将这多个 IMSI 分别对应多个不同的 IMEI , 进而完成批量锁定 (U)SIM卡的需求。 本实施例的移动终端只需在代码处理中添加初始化检查部分即可, 无需 保存任何加锁 /解锁信息, 即使更换 (U ) SIM卡和终端软件版本, 也无需重 新配置, 也不存在被破解和爹改的可能。 实施例 2 图 3 示出了根据本发明实施例提供的实现无线终端设备锁定 (U ) SIM 卡的方法流程图, 在无线终端设备通电开机, 执行如下步骤: 步骤 S301 , 判断无线终端设备是否插入了 (U ) SIM卡, 若是, 执行步 Ml S302, 若否, 执行步 4聚 S308。 步骤 S302, 判断无线终端设备是否已经连接了软件狗, 若是, 执行步骤 S303; 若否, 执行步骤 S308。 步骤 S303 , 无线终端设备读取本机的 IMEI, 以及当前插入的 (U ) SIM 卡的 IMSI; 并将读取到 IMEI和 IMSI保存到临时变量存储。 步骤 S304, 软件狗验证无线终端设备是否有效的步骤。 软件狗初始化, 初始化完成后和无线终端设备建立通讯。无线终端设备把读取到的本机 IMEI 号发送给软件狗, 软件狗搜索内部存储数据库, 如发现内部存储有 IMEI号 和收到的 IMEI号相同, 则继续通讯, 否则, 关闭和无线终端设备的通讯, 执行步骤 S308。 步骤 S305 , 软件狗获取无线终端设备之前保存的 IMEI号, 以该 IMEI 号为索引, 到软件狗内部存储数据库搜索获取相对应 IMSI 号, 并将获取的 IMSI返回给无线终端设备。 步骤 S306,无线终端设备获取软件狗返回的 IMSI号,与之前保存的 IMSI 临时变量相比较, 如果相同, 或者之前保存的 IMSI号位软件狗返回的 IMSI 号组的子集, 则执行步骤 S307, 否则, 执行步骤 S308。 步骤 S307, 允许该无线终端设备被使用, 执行剩余开机初始化流程。 步骤 S308, 禁止该无线终端设备被使用, 该无线终端设备的开机启动失 败。 无线终端设备的用户界面 (UI ) 提示当前插入的 (U ) SIM卡被禁止在 本无线终端设备上, 同时中断和软件狗的通讯, 需要该终端重启才能重新建 立连接。 本发明实施例使用软件狗保存锁定数据, 在终端上不存在被破解和改写 锁定 /解锁数据的可能, 同时可以为一个 IMEI配置多个 IMSI数据, 实现了 锁定多个( U ) SIM卡的需求, 大大提高了锁定 (U)SIM卡的安全性和灵活性。 实施例 3 图 4示出了 居本发明实施例的移动终端锁卡的装置的结构框图, 该装 置可以设置于移动终端上, 这里的移动终端可以是固定台, 手机, 上网本等, 该装置包括以下模块: 检查模块 42 , 设置为移动终端通电开机时, 根据软件狗中的锁定数据检 查是否符合启动条件; 其中, 软件狗是为移动终端配置的用于检查锁定的设 备; 该软件狗通过 USB线与该移动终端相连; 正常启动模块 44 , 与检查模块 42相连, 设置为检查模块 42的检查结果 为是时, 允许该移动终端正常启动; 启动失败模块 46 , 与检查模块 42相连, 设置为检查模块 42的检查结果 为否时, 设置该移动终端启动失败。 优选地, 检查模块 42 包括: 读取单元, 设置为读取该移动终端的锁定 数据; 比较单元, 设置为比较该读取单元读取的锁定数据是否与上述软件狗 中的锁定数据匹配; 如果匹配, 确定该移动终端符合启动条件; 如果不匹配, 确定该移动终端不符合启动条件。 本实施例的锁定数据包括: IMEI和 IMSI; 基于此, 上述读取单元包括: 读取子单元,设置为读取该移动终端的锁定数据,其中,锁定数据包括: IMEI 和 IMSI; 相应地, 上述比较单元包括: 发送子单元, 设置为将读取的 IMEI发送给软件狗; 接收子单元, 设置为接收来自软件狗的 IMSI, 其中, 该 IMSI为软件狗 接收到 IMEI后, 检查数据库中存储有 IMEI, 将数据库中 IMEI对应的 IMSI 发送给移动终端的; 比较子单元, 设置为比较接收的 IMSI与当前插入的用户识别卡的 IMSI 是否匹配, 如果是, 确定移动终端读取的锁定数据和软件狗中的锁定数据匹 配; 如果否, 确定移动终端读取的锁定数据和软件狗中的锁定数据不匹配。 基于批量锁定(U ) SIM卡的需求, 本实施例软件狗的数据库中的 IMEI 对应的 IMSI可以为多个; 例如, 在软件狗的数据库中, 以 IMEI为索引, 存 储每个 IMEI相匹配的 IMSI号, 即可以给每一个 IMEI匹配一个 IMSI, 也可 以匹配多个 IMSI, 为实现批量锁定号码提供了数据基础。 这种情况下, 比较 子单元包括: 匹配子单元, 设置为当数据库中 IMEI对应的 IMSI为多个时, 比较上述接收子单元接收的 IMSI中是否有与当前插入的用户识别卡的 IMSI 相同的 IMSI, 如果是, 确定该移动终端接收的 IMSI与当前插入的用户识别 卡的 IMSI匹配, 如果否, 确定该移动终端接收的 IMSI与当前插入的用户识 别卡的 IMSI不匹配。 本实施例通过软件狗来保存锁定数据, 克服了相关技术中移动终端保存 的锁定数据容易被改写和擦除的缺陷 ,解决了移动终端锁定 (U)SIM卡存在安 全隐患的问题,符合移动终端锁卡服务的初衷, 更大地保护了运营商的利益。 同时, 本实施例只需在移动终端的代码处理中添加初始^ ^检查部分即可, 无 需保存任何加锁 /解锁信息, 即使更换 (U ) SIM卡和终端软件版本, 也无需 重新配置, 也不存在被破解和爹改的可能。 实施例 4 图 5示出了 居本发明实施例的移动终端锁卡的系统结构框图, 该系统 包括移动终端 40 ,其中,该移动终端包括实施例 3中的移动终端锁卡的装置, 该装置的结构可以为图 4所示, 各模块的功能与实现方式因与实施例 3中相 同, 这里不再详述。 另外, 该系统还包括软件狗 50; 该软件狗 50包括: 锁定数据提供模块 52 ,设置为向移动终端 40提供移动终端 40对应的锁 定数据。 同时, 本实施例软件狗 50 上的锁定数据还可以根据需要进行更新, 基 于此, 该系统还包括电脑 PC, 用于向软件狗 50中写入锁定数据; 相应地, 软件狗 50还包括: 锁定数据更新模块, 设置为与 PC建立通讯, 更新自身数 据库中的锁定数据。 如图 6所示的移动终端的另一结构 图,该实现方式中,移动终端包括: 判断模块 61 ,设置为通过检测端口的方式判断软件狗是否已经连接无线 终端设备, 如果是, 则进行下一步操作, 如果未检测到, 则提示用户无法开 机, 需要连接软件狗进行验证。 手机侧信息读取单元 62 , 通过 AT命令等方式读取本机的 IMEI和插入
( U ) SIM卡的 IMSI号, 并将其保存在临时变量中。 软件狗侧信息读取单元 63 , 该单元的作用是通过串口, 使用预定的协议 和软件狗进行通讯, 发送-险证数据(本实施例为上述 IMEI )给软件狗, 并读 取软件狗反馈的 IMSI数据。 验证单元 64 ,设置为如果软件狗反馈验证通过,则继续下一步模块操作, 如果反馈验证失败, 则停止流程, 提示用户无法开机, 验证失败。 计算单元 65 ,该单元 4巴通过软件狗侧信息读取单元 63读取的 IMSI数据 与本机之前读取的当前插入的( U ) SIM卡的 IMSI进行比较, 如果相同或者 为软件狗内匹配数据的一个子集, 则得到匹配正确的结果, 否则, 输出无法 匹配的结果。 允许 /禁止使用确定单元 66 , 根据计算单元 65的匹配结果, 如果匹配, 则允许该移动终端被使用, 如果不匹配, 则禁止该移动终端被使用。 根据本发明的实施例,提供了一种软件狗及其配套 PC端软件工具, 图 7 是 居本发明实施例提供的另一种移动终端锁卡的系统结构框图, 如图 7所 示, 该系统包括 PC设备 70、 软件狗 80和移动终端 90, 其中, PC设备 70 包括 PC端软件工具模块 72 , 软件狗 80包括: 通讯模块 82、 数据接收模块 84、 存储模块 86和计算模块 88。
PC端软件工具模块 72 , 设置为和软件狗通讯, 可以将锁定 (U)SIM卡数 据中的 IMEI对应的 IMSI传输给软件狗的数据接收模块 84。 该模块使用串 口通讯, 按照预定的协议与软件狗 80进行通讯。 通讯模块 82 , 设置为和移动终端的通讯, 通过串口, 按照预定的通讯协 议, 验证移动终端是否具有通讯权限, 接收移动终端 90传输的锁定 (U)SIM 卡数据( IMEI和 IMSI ), 并判断数据的有效性。 如果数据有效就传输给计算 模块 88。 最后根据计算模块 88反馈的验证匹配结果反馈给移动终端 90。 数据接收模块 84 , 设置为和 PC 端软件工具模块 72 通讯, 并接收 IMEI/IMSI的锁定 (U)SIM卡匹配数据, 最后保存到存储模块 86。 计算模块 88 , 通过接收到的通讯模块 82传过来的 IMEI和 IMSI号, 以 该 IMEI号为索引到存储模块 86中寻找匹配的 IMSI号, 并反馈结果给通讯 模块 82。 存储模块 86 , 保存 IMEI和 IMSI的匹配数据。 本实施例通过软件狗来保存锁定数据, 克服了相关技术中移动终端保存 的锁定数据容易被改写和擦除的缺陷 ,解决了移动终端锁定 (U)SIM卡存在安 全隐患的问题,符合移动终端锁卡服务的初衷, 更大地保护了运营商的利益。 同时, 本实施例只需在移动终端的代码处理中添加初始^ ^检查部分即可, 无 需保存任何加锁 /解锁信息, 即使更换 (U ) SIM卡和终端软件版本, 也无需 重新配置, 也不存在被破解和爹改的可能。 从以上的描述中可以看出, 本发明实施例通过将移动终端的锁定数据保 存在软件狗中, 防止了移动终端保存的锁定数据容易被改写和擦除, 同时, 可以根据需要更新软件狗中的锁定数据, 方便了用户使用锁卡功能的移动终 端, 增加了使用的灵活性。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 并 且在某些情况下, 可以以不同于此处的顺序执行所示出或描述的步骤, 或者 将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软件 结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的^"神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。

Claims

权 利 要 求 书
1. 一种移动终端锁卡的方法, 所述移动终端配置有用于检查锁定的软件 狗, 所述方法包括:
移动终端通电开机时, 根据所述软件狗中的锁定数据检查是否符 合启动条件;
如果是, 所述移动终端正常启动;
如果否, 所述移动终端启动失败。
2. 根据权利要求 1所述的方法, 其中, 所述移动终端根据所述软件狗中 的锁定数据检查是否符合启动条件包括:
所述移动终端从自身读取锁定数据;
所述移动终端比较读取的所述锁定数据是否与所述软件狗中的锁 定数据匹配;
如果匹配, 所述移动终端确定符合启动条件;
如果不匹配, 所述移动终端确定不符合启动条件。
3. 根据权利要求 2所述的方法, 其中, 所述锁定数据包括: 国际移动设 备识别码 IMEI和国际移动用户识别码 IMSI;
所述移动终端比较读取的所述锁定数据是否与所述软件狗中的锁 定数据匹配包括:
所述移动终端将读取的所述 IMEI发送给所述软件狗; 所述软件狗接收到所述 IMEI 后, 检查数据库中是否存储有所述 IMEI, 如果是, 将所述数据库中所述 IMEI对应的 IMSI发送给所述移 动终端; 如果否, 断开与所述移动终端的通讯;
所述移动终端接收来自所述软件狗的 IMSI,比较接收的所述 IMSI 与所述当前插入的用户识别卡的 IMSI是否匹配, 如果是, 所述移动终 端确定读取的所述锁定数据和所述软件狗中的锁定数据匹配;如果否 , 所述移动终端确定读取的所述锁定数据和所述软件狗中的锁定数据不 匹配。
4. 根据权利要求 3所述的方法, 其中, 所述数据库中所述 IMEI对应的 IMSI为多个;
所述移动终端比较接收的所述 IMSI 与所述当前插入的用户识别 卡的 IMSI是否匹配包括:
所述移动终端比较接收的所述 IMSI 中是否有与所述当前插入的 用户识别卡的 IMSI相同的 IMSI, 如果是, 所述移动终端确定接收的 所述 IMSI与所述当前插入的用户识别卡的 IMSI匹配, 如果否, 所述 移动终端确定接收的所述 IMSI与所述当前插入的用户识别卡的 IMSI 不匹配。
5. 根据权利要求 1所述的方法, 其中, 所述方法还包括: 所述软件狗通 过与电脑 PC建立通讯, 更新自身数据库中的锁定数据。
6. —种移动终端锁卡的装置, 所述装置包括:
检查模块, 设置为所述移动终端通电开机时, 根据软件狗中的锁 定数据检查是否符合启动条件; 其中, 所述软件狗是为所述移动终端 配置的用于检查锁定的设备;
正常启动模块, 设置为所述检查模块的检查结果为是时, 允许所 述移动终端正常启动;
启动失败模块, 设置为所述检查模块的检查结果为否时, 设置所 述移动终端启动失败。
7. 根据权利要求 6所述的装置, 其中, 所述检查模块包括:
读取单元, 设置为读取所述移动终端的锁定数据;
比较单元, 设置为比较读取的所述锁定数据是否与所述软件狗中 的锁定数据匹配; 如果匹配, 确定所述移动终端符合启动条件; 如果 不匹配, 确定所述移动终端不符合启动条件。
8. 根据权利要求 7所述的装置, 其中,
所述读取单元包括: 读取子单元, 设置为读取所述移动终端的锁 定数据, 所述锁定数据包括: 国际移动设备识别码 IMEI和国际移动用 户 i只别码 IMSI;
所述比较单元包括: 发送子单元, 设置为将读取的所述 IMEI发送给所述软件狗; 接收子单元,设置为接收来自所述软件狗的 IMSI,其中,所述 IMSI 为所述软件狗接收到所述 IMEI后, 检查数据库中存储有所述 IMEI, 将所述数据库中所述 IMEI对应的 IMSI发送给所述移动终端的;
比较子单元,设置为比较接收的所述 IMSI与所述当前插入的用户 识别卡的 IMSI是否匹配, 如果是, 确定所述移动终端读取的所述锁定 数据和所述软件狗中的锁定数据匹配; 如果否, 确定所述移动终端读 取的所述锁定数据和所述软件狗中的锁定数据不匹配。
9. 根据权利要求 8所述的装置, 其中, 所述比较子单元包括:
匹配子单元, 设置为当所述数据库中所述 IMEI对应的 IMSI为多 个时,比较所述接收子单元接收的所述 IMSI中是否有与所述当前插入 的用户识别卡的 IMSI相同的 IMSI, 如果是, 确定所述移动终端接收 的所述 IMSI与所述当前插入的用户识别卡的 IMSI匹配, 如果否, 确 定所述移动终端接收的所述 IMSI 与所述当前插入的用户识别卡的 IMSI不匹配。
10. —种移动终端锁卡的系统, 所述系统包括移动终端, 所述移动终端包 括所述权利要求 6-9中任一项所述的装置, 所述系统还包括软件狗; 所述软件狗包括:
锁定数据提供模块, 设置为向所述移动终端提供所述移动终端对 应的锁定数据。
11. 根据权利要求 10所述的系统, 其中, 所述系统还包括电脑 PC, 设置 为向所述软件狗中写入锁定数据;
所述软件狗还包括:
锁定数据更新模块, 设置为与所述 PC 建立通讯, 更新自身数据 库中的锁定数据。
PCT/CN2011/072449 2011-01-05 2011-04-02 移动终端锁卡的方法、装置和系统 WO2012092727A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110001289.5 2011-01-05
CN201110001289.5A CN102594972B (zh) 2011-01-05 2011-01-05 移动终端锁卡的方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2012092727A1 true WO2012092727A1 (zh) 2012-07-12

Family

ID=46457194

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/072449 WO2012092727A1 (zh) 2011-01-05 2011-04-02 移动终端锁卡的方法、装置和系统

Country Status (2)

Country Link
CN (1) CN102594972B (zh)
WO (1) WO2012092727A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104735251A (zh) * 2015-03-17 2015-06-24 上海天奕达电子科技有限公司 一种解锁移动终端的方法及装置
CN106102082B (zh) * 2016-06-17 2019-08-02 中国联合网络通信集团有限公司 一种嫌疑号码确定方法、装置、系统
CN107889105B (zh) * 2017-09-12 2021-02-02 深圳市优购时代科技有限公司 手机的验证锁卡方法及其验证锁卡系统
CN112383913B (zh) * 2020-11-12 2024-05-14 深圳市锐尔觅移动通信有限公司 终端锁卡控制方法、装置、终端设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1596018A (zh) * 2004-06-29 2005-03-16 航天兰天达科技有限公司 防止移动通信终端被非法使用的方法和装置
CN101222698A (zh) * 2007-01-12 2008-07-16 展讯通信(上海)有限公司 一种基于硬件序列号的imei码保护方法
CN101616401A (zh) * 2009-07-21 2009-12-30 中兴通讯股份有限公司 实现无线终端设备锁定用户号码的方法、解锁方法及装置
CN101888448A (zh) * 2010-06-07 2010-11-17 中兴通讯股份有限公司 一种实现锁网锁卡的方法及移动终端

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100631594B1 (ko) * 2004-09-14 2006-10-09 엘지전자 주식회사 이동 통신 단말기의 장치정보 등록방법
KR100688212B1 (ko) * 2006-01-27 2007-03-02 엘지전자 주식회사 잠금 설정 기능이 구비된 이동통신 단말기 및 그 동작방법
CN101026834A (zh) * 2007-01-17 2007-08-29 中兴通讯股份有限公司 锁定方法和解锁方法
CN101800806A (zh) * 2009-12-29 2010-08-11 闻泰集团有限公司 一种手机锁定sim卡的方法
CN101860850B (zh) * 2010-05-07 2014-09-10 中兴通讯股份有限公司 一种利用驱动实现移动终端锁网或锁卡的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1596018A (zh) * 2004-06-29 2005-03-16 航天兰天达科技有限公司 防止移动通信终端被非法使用的方法和装置
CN101222698A (zh) * 2007-01-12 2008-07-16 展讯通信(上海)有限公司 一种基于硬件序列号的imei码保护方法
CN101616401A (zh) * 2009-07-21 2009-12-30 中兴通讯股份有限公司 实现无线终端设备锁定用户号码的方法、解锁方法及装置
CN101888448A (zh) * 2010-06-07 2010-11-17 中兴通讯股份有限公司 一种实现锁网锁卡的方法及移动终端

Also Published As

Publication number Publication date
CN102594972A (zh) 2012-07-18
CN102594972B (zh) 2015-01-28

Similar Documents

Publication Publication Date Title
US8751824B2 (en) Method and apparatus for protecting software of mobile terminal
US9530027B2 (en) Device lock for transit
US20090260088A1 (en) System and Method for Data Destruction
CN106020875B (zh) 嵌入式终端的固件更新管理方法和装置
US8467531B2 (en) Mobile terminal with encryption chip and related network locking/unlocking method
JP2017513123A (ja) セキュアエレメント管理方法及び端末
WO2013182119A1 (zh) 屏幕解锁的方法、装置及终端
CN105975850B (zh) 一种基于移动终端的软件下载方法及系统
US8458448B2 (en) Method of installing a wireless network
CN107623907B (zh) eSIM卡锁网方法、终端及锁网认证服务器
CN109496443B (zh) 移动认证方法和用于其的系统
WO2012024851A1 (zh) 空口引导设置处理方法及系统
WO2012122752A1 (zh) 一种将终端与智能卡锁定或解锁的方法及装置
WO2012092727A1 (zh) 移动终端锁卡的方法、装置和系统
CN104348616A (zh) 一种访问终端安全组件的方法、装置及系统
US20120225692A1 (en) Control device and control method
US11722307B2 (en) Electronic device for processing digital key, and operation method therefor
CN102752754A (zh) 用户识别卡锁数据进行安全认证的方法及移动终端
US20220038439A1 (en) Network provisioning and tokenization using a remote terminal
CN102067147A (zh) 验证密钥处理
CN106330950B (zh) 加密信息的访问方法、系统及适配器
US20190297504A1 (en) Terminal device, registration-processing method, and non-transitory computer-readable recording medium storing program
CN109842600B (zh) 一种实现移动办公的方法、终端设备及mdm设备
US8185941B2 (en) System and method of tamper-resistant control
KR101206639B1 (ko) 이동통신 단말기의 펌웨어 업데이트 서버 및 그 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11854826

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11854826

Country of ref document: EP

Kind code of ref document: A1