CN105635198B - A kind of consistency management method and device - Google Patents
A kind of consistency management method and device Download PDFInfo
- Publication number
- CN105635198B CN105635198B CN201410584973.4A CN201410584973A CN105635198B CN 105635198 B CN105635198 B CN 105635198B CN 201410584973 A CN201410584973 A CN 201410584973A CN 105635198 B CN105635198 B CN 105635198B
- Authority
- CN
- China
- Prior art keywords
- card application
- consistency
- operated
- module
- information
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 30
- 238000000034 method Methods 0.000 claims abstract description 26
- 238000010586 diagram Methods 0.000 description 16
- 238000004590 computer program Methods 0.000 description 7
- 238000012217 deletion Methods 0.000 description 7
- 230000037430 deletion Effects 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 230000004044 response Effects 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 238000002372 labelling Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004091 panning Methods 0.000 description 1
Landscapes
- Storage Device Security (AREA)
Abstract
The embodiment of the invention discloses consistency management method and devices, this method comprises: obtaining card application operating information, the card application operating information includes at least the card application message and action type for needing to be operated；It determines there are when consistency problem, is determined whether according to preset consistency policy to the corresponding operation of action type described in the card application execution for needing to be operated.Technical solution described in the embodiment of the present invention, is controlled by consistency policy, be can be avoided card and is applied the situation inconsistent with terminal applies state, to improve system stability.
Description
Technical Field
The present invention relates to the field of data services, and in particular, to a method and an apparatus for consistency management.
Background
With the development of internet services and electronic commerce, the number of applications of intelligent terminals (APP) is infinite, and the applications of security chips (SE) corresponding to the terminal APP are increasingly abundant; more and more card applications (applets) are placed in the SE, but the capacity of the SE is limited; the appearance of the HCE satisfies the expansion of the SE capacity, but the open operation of the APP on the SE application under the HCE architecture causes the situation of the uncontrolled operation on the SE application.
There must be a scenario of shared use of applets for different application providers. For example, as shown in fig. 1, the identity authentication Applet may associate multiple terminal APPs (such as a membership card, an access card, an attendance card, an online application card, etc.) at the same time, that is, multiple terminal APPs may use the capability provided by the identity authentication Applet.
There may be an Applet, which provides an application capability for other APPs to use in addition to the association with the APP of the Applet itself, as shown in fig. 2, the bus card Applet provides the application capability to bind with the bus APP, and meanwhile, the bus card may perform operations of charging and inquiring balance through other APPs, that is, other terminal APPs may also use the bus card Applet.
In addition, the PBOC application of each bank is self-owned application at present, the space of SE is occupied, and with the increasing perfection of standard PBOC application, a scene that multiple banks share standard PBOC application is likely to be formed, and the operation control of the basic SE application capability is more important.
However, based on the prior art, when one Applet is associated with multiple terminal APPs, since a user can download and delete the Applet through the multiple terminal APPs, or download and delete the Applet through channels such as a card reader, a situation that the states of the Applet and the terminal APPs are inconsistent due to operations on the Applet by different channels may occur, which may cause system instability. For example: when the user deletes the online application APP and also deletes the identity authentication Applet, other terminal APPs (such as attendance and membership cards) associated with the identity authentication Applet can not use the identity authentication Applet; if the user deletes the bus Applet through the panning APP, the bus APP cannot use the bus Applet function.
Disclosure of Invention
In view of this, in order to solve the existing technical problems, embodiments of the present invention provide:
a consistency management method, comprising:
obtaining card application operation information, wherein the card application operation information at least comprises card application information needing to be operated and an operation type;
and when the consistency problem is determined, determining whether to allow the card application needing to be operated to execute the operation corresponding to the operation type according to a preset consistency strategy.
In one embodiment, determining whether a consistency problem exists includes:
judging whether the card application needing to be operated is in a sharing state, if so, determining that the consistency problem exists; otherwise, it is determined that no consistency issues exist.
In one embodiment, before determining whether a consistency problem exists, the method further comprises:
and judging whether consistency operation is carried out or not, and determining whether the consistency problem exists or not after the consistency operation is determined.
In an embodiment, the determining whether to perform the consistency operation includes:
judging whether to carry out consistency operation according to the operated card application information and a preset strategy, or,
and determining whether to perform consistency operation or not by judging whether the operated card application information contains a preset identifier or not.
In a specific embodiment, the method is applied to a secure chip SE and/or a multi-application open platform TSM, and the obtaining card application operation information includes:
card application operation information is received from a user terminal and/or card application operation information is received from an offline device.
An embodiment of the present invention further provides a consistency management apparatus, including: the device comprises an acquisition module, a first judgment module, a second judgment module and an execution module; wherein,
the acquisition module is used for acquiring card application operation information, wherein the card application operation information at least comprises card application information needing to be operated and an operation type;
the first judgment module is used for judging whether the consistency problem exists according to the card application operation information;
the second judging module is used for judging whether to allow the card application needing to be operated to execute the operation corresponding to the operation type according to a preset consistency strategy when the first judging module determines that the consistency problem exists;
the execution module is configured to execute the operation corresponding to the operation type on the card application that needs to be operated when the second determination module determines that the operation corresponding to the operation type is allowed to be executed on the card application that needs to be operated.
In a specific embodiment, the first determining module is specifically configured to determine whether the card application that needs to be operated is in a shared state, and if so, determine that a consistency problem exists; otherwise, it is determined that no consistency issues exist.
In one embodiment, the apparatus further comprises a third determining module,
and the third judging module is used for judging whether consistency operation is executed or not, and informing the first judging module to judge whether the consistency problem exists or not after the consistency operation is determined.
In a specific embodiment, the third determining module is specifically configured to determine whether to perform a consistency operation according to the operated card application information and a preset policy, or determine whether to perform the consistency operation by determining whether the operated card application information includes a preset identifier.
In one embodiment, the device is located in the SE and/or TSM,
the obtaining module is specifically configured to receive card application operation information from a user terminal, and/or receive card application operation information from an offline device.
The consistency management method and the device of the embodiment of the invention obtain the card application operation information, wherein the card application operation information at least comprises the card application information to be operated and the operation type; and when the consistency problem is determined, determining whether to allow the card application needing to be operated to execute the operation corresponding to the operation type according to a preset consistency strategy. According to the technical scheme, the situation that the states of the Applet and the terminal APP are inconsistent can be avoided through consistency policy control, and therefore system stability is improved.
Drawings
FIG. 1 is a schematic diagram of a scenario for sharing an Applet;
FIG. 2 is a schematic diagram of another scenario of sharing an Applet;
FIG. 3 is a flowchart illustrating a method for consistency management according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating another consistency management method according to an embodiment of the present invention;
FIG. 5 is a schematic structural diagram of a coherency management apparatus according to an embodiment of the present invention;
FIG. 6 is a schematic structural diagram of a coherency management apparatus according to another embodiment of the present invention;
FIG. 7 is a schematic structural diagram of a consistency management system according to embodiment 1 of the present invention;
fig. 8 is a schematic diagram of an Applet labeling process in embodiment 1 of the present invention;
fig. 9 is a flowchart illustrating a TSM performing consistency management according to embodiment 2 of the present invention;
fig. 10 is a flowchart illustrating the SE performing coherency management according to embodiment 3 of the present invention.
Detailed Description
In order to solve the problem that when one card application is associated with a plurality of terminal applications, the card application cannot be normally used due to inconsistent states caused by different terminal applications operating the same card application, an embodiment of the present invention provides a consistency management method, as shown in fig. 3, where the method includes:
step 31: obtaining card application operation information, wherein the card application operation information at least comprises card application information needing to be operated and an operation type;
step 32: and when the consistency problem is determined, determining whether to allow the card application needing to be operated to execute the operation corresponding to the operation type according to a preset consistency strategy.
It should be noted that, for APPs and applets with different association relationships, the consistency operation rules are different, for example, for an identity authentication Applet, the APPs associated with the identity authentication Applet need to be deleted and then deleted; if the bus Applet is needed, the bus APP directly related to the bus Applet is deleted; national mobile financial infrastructure applications, such as those introduced by the chinese people's bank, are not allowed to be deleted. These can all be set by a consistency policy.
Optionally, in an embodiment of the present invention, determining whether there is a consistency problem includes:
judging whether the card application needing to be operated is in a sharing state, if so, determining that the consistency problem exists; otherwise, it is determined that no consistency issues exist.
Optionally, as shown in fig. 4, in an embodiment of the present invention, before determining whether there is a consistency problem, the method further includes:
step 32': and judging whether consistency operation is carried out or not, and determining whether the consistency problem exists or not after the consistency operation is determined.
Optionally, in an embodiment of the present invention, the determining whether to perform the consistency operation includes:
judging whether to perform consistency operation according to the operated card application information and a preset strategy, wherein for example, a card application type list needing to perform the consistency operation can be configured locally, after the card application operation information is acquired, the card application type is acquired from the card application type list, and whether to perform the consistency operation is judged according to the locally configured list;
or, determining whether to perform a consistency operation by judging whether the operated card application information includes a preset identifier, where the network side needs to set a corresponding identifier for a card application that may perform a consistency operation to indicate whether the card application needs to perform a consistency operation.
Optionally, in an embodiment of the present invention, the method is applied to a secure chip SE and/or a multi-application open platform TSM, and the obtaining card application operation information includes:
card application operation information is received from a user terminal and/or card application operation information is received from an offline device.
The embodiment of the present invention further provides a consistency management apparatus, as shown in fig. 5, the apparatus includes: an acquisition module 51, a first judgment module 52, a second judgment module 53 and an execution module 54; wherein,
the obtaining module 51 is configured to obtain card application operation information, where the card application operation information at least includes card application information that needs to be operated and an operation type;
the first judging module 52 is configured to judge whether a consistency problem exists according to the card application operation information;
the second judging module 53 is configured to, when the first judging module 52 determines that the consistency problem exists, judge whether to allow the card application to be operated to execute the operation corresponding to the operation type according to a preset consistency policy;
the executing module 54 is configured to execute the operation corresponding to the operation type on the card application that needs to be operated when the second determining module determines that the operation corresponding to the operation type is allowed to be executed on the card application that needs to be operated.
Optionally, in an embodiment of the present invention, the first determining module 52 is specifically configured to determine whether the card application that needs to be operated is in a shared state, and if so, determine that a consistency problem exists; otherwise, it is determined that no consistency issues exist.
Optionally, as shown in fig. 6, in an embodiment of the present invention, the apparatus further includes a third determining module 55,
the third judging module 55 is configured to judge whether to execute a consistency operation, and after determining that the consistency operation is performed, notify the first judging module 52 to judge whether a consistency problem exists.
Optionally, in an embodiment of the present invention, the third determining module 55 is specifically configured to determine whether to perform a consistency operation according to the operated card application information and a preset policy, or determine whether to perform the consistency operation by determining whether the operated card application information includes a preset identifier.
Optionally, in an embodiment of the present invention, the device is disposed in the SE and/or TSM,
the obtaining module 51 is specifically configured to receive card application operation information from a user terminal, and/or receive card application operation information from an offline device.
The technical solution of the present invention is further described in detail by the following specific examples.
Example 1
Fig. 7 is a schematic structural diagram of a consistency management system in embodiment 1 of the present invention, and as shown in fig. 7, in this embodiment, a consistency management module (corresponding to the foregoing consistency management apparatus) is added to a TSM platform, and a consistency management module is added to a COS of an SE, so as to solve a problem of implementing consistency management by cooperation of a TSM rear end and an SE front end.
For an Applet, if the Applet is allowed to be used by multiple terminal APPs, the Applet needs to be marked (which may be identified by an extended AID or configuration parameter) as a basis for performing consistency management. Fig. 8 is a schematic diagram of an Applet labeling process in embodiment 1 of the present invention, and as shown in fig. 8, the process includes:
step 801: the multi-application open platform marks the Applet which needs to be managed once.
Step 802: the client/SE requests the Applet for download.
Step 803: the client/SE establishes a secure channel with the multi-application open platform.
Step 804: and the client/SE downloads the Applet from the multi-application open platform through the secure channel, wherein the Applet comprises an Applet mark.
Step 805: and after downloading is finished, installing the Applet.
Example 2
The present embodiment relates to a process of performing consistency management by a TSM based on the system shown in fig. 7, specifically, the present embodiment describes that when a user deletes an APP and an Applet through a mobile phone client, the TSM executes a consistency management process, as shown in fig. 9, the process includes:
step 901: the client sends an application deletion request to the TSM;
step 902: and the multi-application open platform executes the consistency management process and determines to delete the application.
For example, referring to the scenario shown in fig. 1, the user may use the capability provided by the identification Applet1 when downloading a membership card, a coupon, and an access card from a mobile phone, and when deleting any application, such as a membership card, the user can only delete the client of the membership card and the membership card Applet2, but cannot delete the identification Applet1 according to the deletion policy; the identification Applet1 can only be deleted if all the clients and card applications on the user's phone that use the identification Applet1 are deleted (i.e., the membership card, coupon, access card client, and Applet2-4 are deleted).
Step 903: the TSM establishes a secure channel with the SE through the client.
Step 904: the TSM sends a delete instruction to the client.
Step 905: the client forwards the delete instruction to the SE.
Step 906: the SE performs a delete operation and returns a response to the client.
Step 907: the client returns a response to the TSM.
Step 908: the deletion is successful.
Example 3
The present embodiment relates to a process of performing consistency management by an SE based on the system shown in fig. 7, and specifically, the present embodiment describes that when a user deletes an APP and an Applet through a card reader or other offline devices, the SE executes a consistency management process, as shown in fig. 10, the process includes:
step 1001: the SE receives an application delete instruction sent by a card reader or other offline device.
Step 1002: and the SE executes the consistency management process, and if the deletion is determined to be allowed, the operation of deletion is executed.
For example, referring to the scenario shown in fig. 2, a user downloads a client of a bus, a bank, a financial payment and a hectometer from a mobile phone, and may use the capability provided by the bus card Applet1, and when the user deletes any non-bus card application, the user can only delete the client and the card application of the user and cannot delete the bus card Applet1 according to a deletion policy; only when the client side and the application of the master control application bus card are deleted, the bus card Applet1 can be deleted according to the deletion strategy, and at the moment, the bus card Applet1 cannot be used by other client sides.
Step 1003: the SE returns a delete response.
The above embodiment of the invention has the following beneficial effects:
1. the method comprises the steps of providing an operation rule when an Applet is used by a plurality of terminals APP, and providing a technical means for SE application to provide basic capability;
2. the problems of limited SE capacity caused by NFC technology popularization and unordered operation of terminal APP caused by HCE application are solved;
3. a consistency strategy is provided for industrial application cooperation of NFC;
4. the operation confusion caused by the insensibility of the user to the SE application is solved, and the user experience is improved.
It should be noted that each module described in the embodiment of the present invention may be implemented by a Central Processing Unit (CPU), a Digital Signal Processor (DSP), or a Programmable logic Array (FPGA) in the electronic device.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (6)
1. A consistency management method is characterized in that the method is applied to a security chip SE and/or a multi-application open platform TSM, and comprises the following steps:
obtaining card application operation information, wherein the card application operation information at least comprises card application information needing to be operated and an operation type;
judging whether to carry out consistency operation according to the operated card application information and a preset strategy, or determining whether to carry out consistency operation by judging whether the operated card application information contains a preset identifier;
after the consistency operation is determined, whether the consistency problem exists is determined;
when the consistency problem is determined, determining whether to allow the card application needing to be operated to execute the operation corresponding to the operation type according to a preset consistency strategy; wherein the preset consistency policy is determined according to an association relationship between the card application and the applet of the card application.
2. The method of claim 1, wherein determining whether a consistency problem exists comprises:
judging whether the card application needing to be operated is in a sharing state, if so, determining that the consistency problem exists; otherwise, it is determined that no consistency issues exist.
3. The method according to claim 1 or 2, wherein the obtaining card application operation information comprises:
card application operation information is received from a user terminal and/or card application operation information is received from an offline device.
4. A consistency management device is characterized in that the device is arranged on a security chip SE and/or a multi-application open platform TSM, and the device comprises: the device comprises an acquisition module, a first judgment module, a second judgment module, a third judgment module and an execution module; wherein,
the acquisition module is used for acquiring card application operation information, wherein the card application operation information at least comprises card application information needing to be operated and an operation type;
the first judgment module is used for judging whether the consistency problem exists according to the card application operation information;
the second judging module is used for judging whether to allow the card application needing to be operated to execute the operation corresponding to the operation type according to a preset consistency strategy when the first judging module determines that the consistency problem exists; wherein the preset consistency policy is determined according to an association relationship between the card application and the applet of the card application;
the third judging module is used for judging whether to perform consistency operation according to the operated card application information and a preset strategy, or determining whether to perform consistency operation by judging whether the operated card application information contains a preset identifier; after the consistency operation is determined, whether the consistency problem exists is determined;
the execution module is configured to execute the operation corresponding to the operation type on the card application that needs to be operated when the second determination module determines that the operation corresponding to the operation type is allowed to be executed on the card application that needs to be operated.
5. The apparatus of claim 4,
the first judging module is specifically configured to judge whether the card application to be operated is in a shared state, and if yes, determine that a consistency problem exists; otherwise, it is determined that no consistency issues exist.
6. The apparatus according to claim 4 or 5, wherein the obtaining module is specifically configured to receive card application operation information from a user terminal and/or receive card application operation information from an offline device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410584973.4A CN105635198B (en) | 2014-10-27 | 2014-10-27 | A kind of consistency management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410584973.4A CN105635198B (en) | 2014-10-27 | 2014-10-27 | A kind of consistency management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105635198A CN105635198A (en) | 2016-06-01 |
| CN105635198B true CN105635198B (en) | 2019-09-13 |
Family
ID=56049684
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410584973.4A Active CN105635198B (en) | 2014-10-27 | 2014-10-27 | A kind of consistency management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105635198B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101231768A (en) * | 2008-01-25 | 2008-07-30 | 北京深思洛克数据保护中心 | Multi-application intelligent card and method for realizing intelligent card multi application |
| CN102591788A (en) * | 2011-12-23 | 2012-07-18 | 飞天诚信科技股份有限公司 | Method for recovering Java card garbage |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7127605B1 (en) * | 1999-05-10 | 2006-10-24 | Axalto, Inc. | Secure sharing of application methods on a microcontroller |
| US7140549B2 (en) * | 2004-02-24 | 2006-11-28 | Sun Microsystems, Inc. | Method and apparatus for selecting a desired application on a smart card |
| US8677101B2 (en) * | 2007-06-07 | 2014-03-18 | International Business Machines Corporation | Method and apparatus for cooperative software multitasking in a processor system with a partitioned register file |
| CN102023864A (en) * | 2010-12-13 | 2011-04-20 | 中国联合网络通信集团有限公司 | Method and system for processing OTA (over the air) message in universal USIM (subscriber identity module) |
| CN103093142B (en) * | 2012-12-26 | 2015-07-22 | 飞天诚信科技股份有限公司 | Java card object access control method |
-
2014
- 2014-10-27 CN CN201410584973.4A patent/CN105635198B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101231768A (en) * | 2008-01-25 | 2008-07-30 | 北京深思洛克数据保护中心 | Multi-application intelligent card and method for realizing intelligent card multi application |
| CN102591788A (en) * | 2011-12-23 | 2012-07-18 | 飞天诚信科技股份有限公司 | Method for recovering Java card garbage |
Non-Patent Citations (1)
| Title |
|---|
| Java智能卡安全运行环境的设计与实现;程恒;《中国优秀硕士学位论文全文数据库 信息科技辑》;20090715;正文第4.2.1小节 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105635198A (en) | 2016-06-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3337219A1 (en) | Carrier configuration processing method, device and system, and computer storage medium | |
| JP6923582B2 (en) | Information processing equipment, information processing methods, and programs | |
| US10387219B2 (en) | Enabling multiple secure elements in a card computing device | |
| US20160234340A1 (en) | Systems and methods for adaptive cloning of mobile devices | |
| CN111581994A (en) | Near Field Communication (NFC) communication method and device and electronic equipment | |
| CN112468409A (en) | Access control method, device, computer equipment and storage medium | |
| US9807595B2 (en) | Terminal read with smart card update list | |
| CN108810835B (en) | Method and device for associating one number with multiple terminals, terminal and storage medium | |
| CN102510391B (en) | Application management method and device and smart card | |
| CN103442012A (en) | Method and device for realizing subscription information transfer between devices of Internet of things | |
| US10531296B2 (en) | Method for loading a subscription into an embedded security element of a mobile terminal | |
| CN106412797B (en) | near Field Communication (NFC) -based service processing method and device | |
| CN111125744B (en) | Code branch merging method, system, computer device and readable storage medium | |
| CN105635198B (en) | A kind of consistency management method and device | |
| CN107872786B (en) | Control method and smart card | |
| CN108292393B (en) | Payment method and device based on NFC | |
| CN108667647A (en) | A kind of setting method of device parameter, equipment and server | |
| CN109219035B (en) | Configuration platform of embedded chip card and data change system, method and device | |
| CN106384231A (en) | Cross-screen payment method and system and client | |
| CN107688473B (en) | Method for realizing user-defined security domain in smart card and smart card | |
| US20150074105A1 (en) | Mobile application data storage allocation | |
| CN108063679B (en) | Method and device for upgrading cloud management platform | |
| CN115002218B (en) | Traffic distribution method, traffic distribution device, computer equipment and storage medium | |
| CN108664820B (en) | Electronization method of non-contact IC card, related equipment and system | |
| CN103856935B (en) | A kind of method for preventing soft SIM to be illegally used and its device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |