CN102316428B - Method for communication between mobile application client and intelligent card and device - Google Patents

Method for communication between mobile application client and intelligent card and device Download PDF

Info

Publication number
CN102316428B
CN102316428B CN201110293150.2A CN201110293150A CN102316428B CN 102316428 B CN102316428 B CN 102316428B CN 201110293150 A CN201110293150 A CN 201110293150A CN 102316428 B CN102316428 B CN 102316428B
Authority
CN
China
Prior art keywords
data
smart card
note
short message
module
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.)
Expired - Fee Related
Application number
CN201110293150.2A
Other languages
Chinese (zh)
Other versions
CN102316428A (en
Inventor
邹勇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BEIJING ZHONGQINGHE SCIENCE AND TECHNOLOGY CO., LTD.
Original Assignee
BEIJING ZHONGQINGHE SCIENCE AND TECHNOLOGY Co Ltd
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 BEIJING ZHONGQINGHE SCIENCE AND TECHNOLOGY Co Ltd filed Critical BEIJING ZHONGQINGHE SCIENCE AND TECHNOLOGY Co Ltd
Priority to CN201110293150.2A priority Critical patent/CN102316428B/en
Publication of CN102316428A publication Critical patent/CN102316428A/en
Application granted granted Critical
Publication of CN102316428B publication Critical patent/CN102316428B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a method for the data communication between a mobile application client and an intelligent card, which comprises the following processes of: a process of writing data into the intelligent card by the mobile application client, a process of reading the data in the intelligent card by the client through an address book management module, a process of writing data into the intelligent card by the mobile application client and a process of reading the data in the intelligent card by the client through a short message management module. When the method provided by the invention is utilized, the mobile application client can realize the data interaction and the data communication in any length with the intelligent card, the adoption of a third party storage medium with too high cost is avoided, the goal of cost reduction is reached, the private information in the mobile payment service transaction process can be completed in the mobile terminal, the outward information leakage is avoided, and the information security in the mobile payment service is further enhanced.

Description

Communication means between a kind of Mobile solution client and smart card and device
Technical field
The present invention relates to the information security technology of mobile terminal device and mobile payment service, particularly relate to the data communications method between a kind of applications client of mobile terminal device and smart card.
Background technology
At present, mobile terminal such as mobile phone carry out the development of third party's operation expanding very fast, such as, all have application in fields such as mobile payment, gate inhibition, ticket checking, ticketing, traffic, data interaction transmission, logistics, storages.This technology mainly adopts smart card as safe hardware unit, carries out encryption and decryption with the fail safe of the business of guaranteeing payment to data.
But but there is certain limitation in this application, due to the criteria limit by smart card, smart card can not receive the data that data length is long and send, and therefore cannot meet the reception of some large data and process and send, such as, to the process of special data (transaction data) digital signature.Want to solve this technical problem, mainly will solve the transmission problem of large data exactly, comprise and receive and send.
In addition, at existing mobile communication terminal (common as mobile phone), owing to being subject to the restriction of operator, adopt existing data transmission method cannot transmit ultra-long data in smart card, therefore, which also limits employing smart card to carry out data storage and carry out the practicality of the technology communicated with Mobile solution client.Here, described smart card, namely Subscriber Identity Module (SIM card), is commonly called as " kilocalorie ", is made up of one piece of large scale integrated chip, and it can ensure the versatility with credit card according to the standard size manufacture of credit card.
Summary of the invention
In view of this, main purpose of the present invention is to provide the data communications method between a kind of Mobile solution client and smart card and device, passes mutually with the data realizing carrying out between Mobile solution client and smart card random length, the transmission of especially large data.
For achieving the above object, technical scheme of the present invention is achieved in that
A data communications method between Mobile solution client and smart card, the method comprises:
A, when user needs to carry out business data processing by smart card, send business data processing instruction to Mobile solution client, the business data processing instruction that Mobile solution client receives from user generates data request information;
Operational order in request of data described in B, the identification of Mobile solution client, and judge the type of this operational order, if belong to type data being sent to smart card, then enter step C; If belong to the type reading data from smart card, then enter step e;
C, judging whether the need data length to be processed received exceedes the predetermined length of mobile terminal restriction, if exceed, then by needing Data Division to be processed to become some the data segments being less than or equal to predetermined length, and performing step D; Otherwise, before these data, add data length and hop count by mobile subscriber's client, then enter step D;
D, the data segment of all interpolation data lengths and hop count is assembled into the form of associated person information or note, and complete associated person information or note are sent to address list management module or short message managing module accordingly, then carry out generation and the process of transmitting of next associated person information or short message; Or after the generation completing all associated person informations or note, then unification is sent to address list management module or short message managing module; Associated person information or note are sent to smart card by system kernel by address list management module or short message managing module; Store in the mode of contact person or note after smart card processes;
E, Mobile solution client is utilized to send contact person or note read requests to address list management module or short message managing module, again by address list management module or short message managing module and system kernel module read in smart card associated person information or note, to be readly complete backward described Mobile solution client feedback information;
After the reading received from address list management module or short message managing module of F, Mobile solution client completes feedback information, judge the number of name of contact person or note; If be greater than one, then many name of contact persons or note are combined into one; Otherwise mobile subscriber's client obtains the result read.
Data request information described in steps A is HTML (Hypertext Markup Language) form, note request format, phone book contact form or user-defined format.
Described in step C, the need Data Division to be processed exceeding mobile terminal restriction is become some the data segments being less than or equal to predetermined length, comprises further:
Each data segment after C1, fractionation mainly comprises data length, hop count and real data;
If the described need of C2 data to be processed have multiple, then after Data Division completes, be every section by mobile subscriber's client and added data length and hop count by before the data that split.
The process described in step D, the data segment of all interpolation data lengths and hop count being assembled into associated person information comprises:
D1, a newly-built contact person, the field contents of contact person comprises name of contact person, telephone number;
D2, will add in the described newly-built name of contact person of data segment write of data length and hop count;
The number of the telephone number write agreement of D3, contact person, this number can be identified in smart card one end.
Comprise further after described step D:
Described smart card carries out data processing to the associated person information received or short message, stores, be convenient to by correct reading after having processed according to original fractionation rule.
Taking a step forward of step e comprises:
The measuring ability that Mobile solution client call mobile terminal provides, to detect address list management module or whether short message managing module normally works, if working properly, then gets the data after process by this module; Otherwise, then to Mobile solution client feedback read error.
The present invention also provides a kind of mobile terminal, comprises system kernel module, short message managing module and address list management module, also comprises Mobile solution client, and the communication process between described Mobile solution client and smart card is as follows:
A, when user needs to carry out business data processing by smart card, send business data processing instruction to Mobile solution client, the business data processing instruction that Mobile solution client receives from user generates data request information;
Operational order in request of data described in B, the identification of Mobile solution client, and judge the type of this operational order, if belong to type data being sent to smart card, then enter step C; If belong to the type reading data from smart card, then enter step e;
C, judging whether the need data length to be processed received exceedes the predetermined length of mobile terminal restriction, if exceed, then by needing Data Division to be processed to become some the data segments being less than or equal to predetermined length, and performing step D; Otherwise, before these data, add data length and hop count by mobile subscriber's client, then enter step D;
D, the data segment of all interpolation data lengths and hop count is assembled into the form of associated person information or note, and complete associated person information or note are sent to address list management module or short message managing module accordingly, then carry out generation and the process of transmitting of next associated person information or short message; Or after the generation completing all associated person informations or note, then unification is sent to address list management module or short message managing module; Associated person information or note are sent to smart card by system kernel by address list management module or short message managing module; Store in the mode of contact person or note after smart card processes;
E, Mobile solution client is utilized to send contact person or note read requests to address list management module or short message managing module, again by address list management module or short message managing module and system kernel module read in smart card associated person information or note, to be readly complete backward described Mobile solution client feedback information;
After the reading received from address list management module or short message managing module of F, Mobile solution client completes feedback information, judge the number of name of contact person or note; If be greater than one, then many name of contact persons or note are combined into one; Otherwise mobile subscriber's client obtains the result read.
Data communications method between Mobile solution client provided by the present invention and smart card, has the following advantages:
Mobile solution client of the present invention can send data by the address list management module of mobile device terminal, and receives data by address list management module; Or send data by the address list management module of mobile device terminal, and receive data by short message managing module; Or send data by the short message managing module of mobile device terminal, and receive data by short message managing module; Or send data by the short message managing module of mobile device terminal, and receive data by address list management module; Like this, coordinated by Mobile solution client, make Mobile solution client can and smart card between carry out data communication and the data interaction of random length, third party's storage medium that use cost is too high can either be avoided, reach the object reduced costs, the most important thing is, the security information in mobile payment service process of exchange can also be completed in mobile terminal, avoid information leakage, further enhancing the information security in mobile payment service.
Accompanying drawing explanation
Fig. 1 is the system configuration schematic diagram of the first embodiment of the present invention;
Fig. 2 is communication process schematic diagram between the Mobile solution client of the embodiment of the present invention one and address list management module;
Fig. 3 is the modular structure schematic diagram of second embodiment of the invention;
Fig. 4 is communication process schematic diagram between the Mobile solution client of the embodiment of the present invention two and address list management module, short message managing module.
[critical piece symbol description]
10: Mobile solution client
11: address list management module
12: system kernel module
121: cache management submodule
122: system monitoring submodule
13:SIM card (i.e. smart card)
14: short message managing module.
Embodiment
Below in conjunction with accompanying drawing and embodiments of the invention, method of the present invention is described in further detail.
Embodiment one:
In the present embodiment, mainly introduce Mobile solution client and send data by the address list management module of mobile communication terminal to smart card, after smart card carries out processing (as encryption), Mobile solution client reads the data after smartcard encrypts by short message managing module again.
Fig. 1 is the system configuration schematic diagram of the first embodiment of the present invention, as shown in Figure 1, functional module involved by data communications method between mobile client of the present invention and smart card or parts mainly comprise: mobile subscriber's client 10, address list management module 11, system kernel module 12 and SIM card 13.Described system kernel module 12 comprises again cache management submodule 121 and system monitoring submodule 122 further.Wherein, address list management module 11 and system kernel module 12 are existing module, and the present invention utilizes their work on hand principle to realize object of the present invention.
Described Mobile solution client 10, as the control module of the whole technical scheme of the present invention, be positioned at user's practical operation aspect, user utilizes this Mobile solution client 10 travel all over business, Mobile solution client 10 generates data request information according to the instruction of user, and data request information is sent to address list management module 11, if data length is beyond the limited length of mobile terminal, then the form being combined into address book contact after Data Division is sent, reconfigure after receiving all subsegment data after processing and split, obtain the data processed.
Described address list management module 11, is provided by mobile phone operating system, and this module comprises SIM address list and cell phone address book two large divisions further.
Described system monitoring submodule 122, the change update status of real-time monitoring system caching management module, then by monitoring situation notice cache management submodule 121, is upgraded the data of SIM card 13 by cache management submodule 121.In whole scheme, only have this module can read and write data directly to SIM card 13.
Described cache management submodule 121: actual is cell phone system database, for memory communicating record and note, address list management module carrys out dereference SIM card by this module.
Described SIM card 13, belong to hardware layer, be positioned at the data storage areas of this programme, also be the core component of whole scheme, for receiving the contact data from described Mobile solution client 10, row relax of going forward side by side, after analyzing, verify, contrast, splitting data, described data are indirectly transferred to Mobile solution client 10 process, also indirectly receive the data processed result of Mobile solution client 10 simultaneously.
With reference to figure 1, effect and the relation thereof of described modules are as follows:
Described Mobile solution client 10 sends to the data assemblies of smart card 13 to become the storage format of a phone book contact by needing, and sends to address list management module 11.Address list management module 11 belongs to conventional mobile device terminal inside and carries module, and its concrete structure and principle do not describe in detail at this.The data sent need combine in such a way:
Wherein, telephone number, available a succession of Arabic numerals are write, and length can be less than or equal to 8 usually, also can set flexibly.Effect is convenient to smart card 13 to identify this data field.As in program embodiment, identifier is 1234567.
Name of contact person: this part is further divided into hop count value indicating bit and real data section, real data section is for depositing actual data.Because this part is subject to the restriction of mobile device terminal length, different mobile device terminal requires not identical for length restriction.Therefore, if real data length exceedes restriction when requiring, then need Data Division to become multiple data segment, each data segment is made up of three parts: data length, hop count and real data.It is as follows that it splits rule:
Field Length Explanation
Data length 4 This segment data length, if first character joint highest order is 1, then represents that this section is final data section
Hop count 2 Hop count in these former data in segment data place, from 0x00
Real data N Actual data
Wherein, data length: this explanation of field actual data fields and hop count field are added up, total how many bytes, represent, as 0x01,0x0F, 0xFF with 1 16 system number.By this field, smart card 13 just can determine the size of data received.
Hop count: as mentioned above, can split because actual data fields is subject to the restriction of length, therefore, represent real data is that total data is by which section split by hop count field, represent with 1 16 system number, the real data as being split into is second segment, is so expressed as 0x02.By this field, smart card 13 can be distinguished this yellow pages contact person and belong to which section, and after all data all receive, smart card 13 will according to this field from small to large, combine data.
Real data: this field is the real data that Mobile solution client sends to smart card 13.
Described address list management module 11 after receiving the data, send the data to kernel module, kernel module in the present invention is exactly the system kernel module 12 of existing mobile communication terminal, do not need to make to change, this system kernel module 12 forms, as Fig. 1 primarily of cache management submodule 121 and system monitoring submodule 122 two parts.
The data that described address list management module 11 sends, be kept in cache management submodule 121, the data variation in described cache management submodule 121 is monitored by system monitoring submodule 122, when finding have data to write in cache management submodule 121, just the state of smart card 13 is judged by system monitoring submodule 122, as, judge in current mobile device, whether smart card 13 exists, whether this smart card 13 meets a series of information such as mobile phone standard, and its criterion and determination methods are determined by system monitoring submodule 122.In data write smart card 13, because system kernel module 12 is that existing cell phone system carries module, detailed determination methods, criterion is variant according to the difference of mobile device terminal, this module belongs to mobile device terminal scheme of the prior art, therefore does not describe in detail at this.
When the data received are kept in smart card 13 by system kernel module 12, after smart card 13 receives data, start to process data, if multiple segment data, first combine, obtain complete real data, judge class of service by this smart card 13 according to identifier, and according to different classs of service, corresponding process is done to the data received.
Such as: if the identifier of this segment data represents that needs are encrypted it by smart card 13, then smart card 13 is stored in after being encrypted in the memory of smart card 13; These data to be stored if the identifier of this segment data represents, then these data are stored in smart card 13 memory with the form of note.
After Mobile solution client 10 is sent completely all data, initiatively suspend a period of time of presetting, as 0.5 second, then the short message managing module 14 to mobile device terminal sends the request of reading smart card 13 enciphered data, request content is the note read requests of a standard, meaning is the specific note read out in smart card 13, and specific distinguishing identifier is gone to specify by the associated data field in asking.The contact number of the self-built telephone directory in example is inserted in this specific fields.Form and the encapsulation of note request have detailed Open Standard, can see GSM11.11 and GSM03.04 standard.
After short message managing module 14 receives request, this request is sent to system kernel module 12, according to above-mentioned note request condition, extract all enciphered datas processed by smart card 13 by system kernel module 12, and the data message extracted is sent to short message managing module 14 in the mode of short message.By short message managing module 14, the data received are assembled again, and the data of having assembled are sent to Mobile solution client 10.Here, the method for described data assembling is identical with step S1 with form.
Fig. 2 is communication process schematic diagram between the Mobile solution client of the embodiment of the present invention one and address list management module, and as shown in Figure 2, this process comprises:
Step T1: user is by Mobile solution client 10 browse service information, when user needs to carry out a certain business data processing by smart card 13, send business data processing instruction will to Mobile solution client 10, Mobile solution client 10 receives business data processing instruction from user (as the instruction be encrypted one piece of data, or store the instruction of one piece of data, or read the instruction of one piece of data) generate data request information, this data request information can be arbitrary format, as being HTTP(Hypertext Transport Protocol) form, also can be note request format, phone book contact form or user-defined format etc.
Step T2: the operational order in Mobile solution client 10 identification data solicited message, described operational order has two kinds, and one is that data are sent to SIM card, and another kind reads data from SIM card.If judge it is that data are sent to SIM card, then enter step T3; If judge to read data from SIM card, then enter step T8.
Step T3: judge whether the need data real data to be processed segment length received has exceeded the length of mobile terminal restriction, the length restriction of current mobile terminal is that each mobile terminal manufacturer makes by oneself.If exceed predetermined length, then enter step T4, otherwise, enter step T5.
Step T4: data to be processed need carry out deconsolidation process, handling process is as follows:
To Data Division to be processed be needed to become some the data segments being less than or equal to predetermined length, each data segment be made up of three parts: data length, hop count and real data.If described need data to be processed have multiple, then after data segment has split, Mobile solution client is every section and is added data length and skew by before the data that split, enters step T6; .
Step T5: Mobile solution client adds data length and hop count before data.
Step T6: successively following steps are carried out to the data segment of all interpolation data lengths and hop count, is assembled into the form of associated person information.
A. a newly-built contact person, contact field content comprises name of contact person, telephone number;
B. the data segment adding data length and hop count is write in newly-built name of contact person;
C. the telephone number of contact person writes the number of special agreement, as 9999999.The number of agreement can accurately identify in smart card 13 one end.
Step T7: full contact people information is sent to address list management module 11, then carries out generation and the transmission of next associated person information; Also after can completing the generation of all associated person informations, then unification is sent to address list management module 11.
Step T8: Mobile solution client sends contact person's read requests to address list management module.
Step T9: the contact person in address list management module 11 reading system kernel module 12; This contact person can be through the contact person after data processing, such as, encrypt, signature etc., or pure data store; After reading completes, feed back reading to Mobile solution client 10 and complete; All Contacts's name corresponding for particular number reads in a scratchpad area (SPA) by address list management module 11, and scratchpad area (SPA) is specified voluntarily by mobile device terminal, only need call the functional interface that mobile device terminal provides.
Step T10: Mobile solution client 10 judges the number of name of contact person, if be greater than 1, enters step T11 after receiving the feedback information that the reading from address list management module 11 completes; Otherwise, enter step 12;
T11: many name of contact persons are combined into 1;
T12: Mobile solution client obtains result.
In such scheme, if just data store, after step T7, after full contact people information is sent to SIM card 13 by address list management module 11, by SIM card 13 above-mentioned data is stored or the data processing such as encryption, again split after process and store; And All Contacts corresponding for jack per line when address list management module 11 reads this contact person, all can be able to read by the contact person after splitting.Guarantee that Mobile solution client 10 can data needed for complete acquisition.
Also comprised before described step T8: whether the measuring ability that Mobile solution client 10 calls mobile device terminal to be provided normally works to detect address list management module 11.Only when address list management module 11 is working properly, just get the data after encryption by this module, if abnormal, feed back read error to Mobile solution client 10.The measuring ability that mobile device terminal provides is according to different device ends, and the difference of system platform and different, by mobile device terminal by oneself, does not describe in detail at this.
Embodiment two:
In the embodiment of this programme, mainly introduce Mobile solution client and send data by the address list management module of mobile terminal, after being undertaken processing (signature, encryption or storage) by smart card, then by the data after short message managing module 14 reading process.
Fig. 3 is the modular structure schematic diagram of second embodiment of the invention, as shown in the figure, the functional module involved by data communications method between Mobile solution client of the present invention and smart card or parts mainly comprise: mobile subscriber's client 10, address list management module 11, short message managing module 14, system kernel module 12 and SIM card 13.Described system kernel module 12 comprises cache management submodule 121 and system monitoring submodule 122 further.Wherein, short message managing module 14 is prior art with address list management module 11 and system kernel module 12, and they do not make with the Principle of Communication between smart card and change.
Described Mobile solution client 10, as the control module of technical solution of the present invention, be positioned at user's practical operation aspect, user utilizes this Mobile solution client 10 travel all over business, Mobile solution client 10 generates data request information according to the instruction of user, and data request information is sent to address list management module 11, if data length is beyond the limited length of mobile terminal, then the form being combined into address book contact after Data Division is sent to address list management module 11, address list management module 11 is forwarded to SIM card 13 by system kernel module 12, after SIM card 13 processes, carry out splitting rear storage according to identical fractionation mode, Mobile solution client 10 reconfigures after reading all subsegment data after processing and split by short message managing module 14, obtain the data processed.
Described address list management module 11, is provided by mobile phone operating system, and this module comprises SIM address list and cell phone address book two large divisions further.
Described system monitoring submodule 122, the change update status of real-time monitoring system cache management submodule 122, then by monitoring situation notice cache management submodule 121, is upgraded the data of SIM card 13 by cache management submodule 121.In whole scheme, this module is only had to have the request read and write data directly to SIM card 13.Described cache management submodule 121, actual is cell phone system database, and for memory communicating record and note, short message managing module 14 and address list management module 11 all carry out dereference SIM card 13 by described cache management submodule 121.
Described SIM card 13, for receiving the contact data from described Mobile solution client 10, to go forward side by side row relax, after analyzing, verify, contrast, splitting data, described data are indirectly transferred to Mobile solution client 10 process, also indirectly receive the data processed result of Mobile solution client 10 simultaneously.
Described short message managing module 14 is existing module, comprises SMS and SIM card note two parts, communicates for same SIM card 13 in the mode reading and writing note.
With reference to figure 3, described modules effect and relation as follows:
Data assemblies is become the storage format of an address list by described Mobile solution client 10, and sends to address list management module 11.
Here, described address list management module 11 belongs to the conventional inner own module of mobile device terminal, and its concrete structure and principle do not describe in detail at this.The data sent need combine in such a way:
Wherein, telephone number: write with a succession of Arabic numerals, length can be less than or equal to 8 usually, also can set flexibly.Effect is convenient to smart card 13 to identify this data field.As in program embodiment, identifier is 1234567.
Name of contact person: this part is further divided into hop count value indicating bit and real data section, real data section is for depositing actual data.Because this part is subject to the restriction of mobile device terminal length, different mobile device terminal requires not identical for length restriction.Therefore, if real data length exceedes restriction when requiring, then need Data Division to become multiple sections, every segment data has three attributes: data length, hop count and real data.It is as follows that it splits rule:
Field Length Explanation
Data length 4 This segment data length, if first character joint highest order is 1, then represents that this section is final data section
Hop count 2 Hop count in these former data in segment data place, from 0x00
Real data N Actual data
Wherein, data length: this explanation of field actual data fields and hop count field are added up, total how many bytes, represent, as 0x01,0x0F, 0xFF with 1 16 system number.By this field, smart card 13 just can determine the size of data sending to smart card 13.
Hop count: as mentioned above, can split because actual data fields is subject to the restriction of length, therefore, represent real data is that total data is by which section split by hop count field, represent with 1 16 system number, the real data as being split into is second segment, is so expressed as 0x02.By this field, smart card 13 can be distinguished this yellow pages contact person and belong to which section, and after all data all receive, smart card 13 according to this field from little arrival, will combine data.
Real data: this field is the real data that Mobile solution client 10 sends to smart card 13.
Described address list management module 11 after receiving the data, send the data to kernel module, this kernel module is exactly the system kernel module 12 of existing mobile communication terminal, do not need to do any change, this kernel module 12 is primarily of cache management submodule 121 and system monitoring submodule 122 two parts composition.
The data that described address list management module 11 sends, be kept in cache management submodule 121, system monitoring submodule 122 is for monitoring the data variation in described cache management submodule 121 in real time, when finding have data to write in cache management submodule 121, then judge, and write data in smart card 13 and go.Because system kernel module 12 is that existing cell phone system carries module, detailed determination methods, criterion is variant according to the difference of mobile device terminal, and this module belongs to mobile device terminal scheme of the prior art, is not described in detail at this.
The data received are kept in smart card 13 by described system kernel module 12, after smart card 13 receives data, start to sign to data, the methods of data signature, different smart cards 13 is different, ciphering process and data preservation work complete voluntarily by smart card 13, are not also described in detail here.
After all data of Mobile solution client 10 are sent completely, according to above-mentioned flow process, smart card 13 can automatically to all data signatures, and in this embodiment, the data of having signed are preserved with the form of yellow pages contact person by smart card 13.So far, Mobile solution client 10 writes process from data to smart card 13 is completed.
After described Mobile solution client 10 is sent completely all data, initiatively suspend a period of time of presetting, as 0.5 second, then to the address list management module 11 of mobile device terminal send read smart card 13 sign after the request of enciphered data, the form of request and method are decided by smart card 13.
Described address list management module 11 upon receiving a request, request is sent to system kernel module 12, called data message after the signature in smart card 13 by system kernel module 12, the data message extracted sends to address list management module 11 in the mode of yellow pages contact person.Mobile solution client 10 is sent to again by address list management module 11.
Fig. 4 is communication process schematic diagram between the Mobile solution client of the embodiment of the present invention two and address list management module, short message managing module, and as shown in Figure 4, this process comprises:
Step T1: user is by Mobile solution client 10 browse service information, when user needs to carry out a certain business data processing by smart card 13, send business data processing instruction will to Mobile solution client, Mobile solution client 10 receives business data processing instruction from user (as the instruction be encrypted one piece of data, or store the instruction of one piece of data, or read the instruction of one piece of data) generate data request information, this data request information can be arbitrary format, as being HTTP(Hypertext Transport Protocol) form, also can be note request format, phone book contact form or user-defined format etc.
Step T2: the operational order in Mobile solution client 10 identification data solicited message, described operational order has two kinds, and one is that data are sent to SIM card 13, and another kind reads data from SIM card 13.If judge it is that data are sent to SIM card 13, then enter step T3; If judge to read data from SIM card 13, then enter step T8.
Step T3: judge whether the need data real data to be processed segment length received has exceeded the length of mobile terminal restriction, the length restriction of current mobile terminal is that each mobile terminal manufacturer makes by oneself.If exceed predetermined length, then enter step T4, otherwise, enter step T5.
Step T4: data to be processed need carry out deconsolidation process, handling process is as follows:
To Data Division to be processed be needed to become some the data segments being less than or equal to predetermined length, each data segment be made up of three parts: data length, hop count and real data.If described need data to be processed have multiple, then after data segment has split, Mobile solution client is every section and is added data length and skew by before the data that split, enters step T6; .
Step T5: Mobile solution client 10 adds data length and hop count before data.
Step T6: successively following steps are carried out to the data segment of all interpolation data lengths and hop count, is assembled into the form of associated person information.
A. a newly-built contact person, contact field content comprises name of contact person, telephone number;
B. the data segment adding data length and hop count is write in newly-built name of contact person;
C. the telephone number of contact person writes the number of special agreement, as 9999999.The number of agreement can accurately identify in smart card 13 one end.
Step T7: full contact people information is sent to address list management module 11, then carries out generation and the transmission of next associated person information; Also after can completing the generation of all associated person informations, then unification is sent to address list management module 11.Data are sent to smart card by system kernel module 12 by address list management module 11, and contact person's format conversion is that messaging format stores by smart card; Or after data processing, be converted to messaging format and store;
Step T8: Mobile solution client 10 sends note read requests to short message managing module.
Step T9: the note in short message managing module 14 reading system kernel module 12; This note can be through the note after data processing, such as, encrypt, signature etc., or pure data store; After reading completes, read to Mobile solution client feedback; All notes corresponding for particular number read in a scratchpad area (SPA) by short message managing module, and scratchpad area (SPA) is specified voluntarily by mobile device terminal, only need call the functional interface that mobile device terminal provides.
Step T10: Mobile solution client 10 judges the number of note, if be greater than 1, enters step T11 after receiving the feedback information that the reading from short message managing module completes; Otherwise, enter step 12.
T11: many notes are combined into 1.
T12: Mobile solution client obtains result.
In such scheme, if just data store, after step T7, after full contact people information is sent to SIM card 13 by administration module, by SIM card 13 above-mentioned data are stored or the data processing such as encryption, again split after process and store, and all notes corresponding for jack per line when short message managing module 14 reads this note, all can read by the note after splitting.Guarantee that Mobile solution client can data needed for complete acquisition.
Also comprised before described step T8: whether the measuring ability that Mobile solution client 10 calls mobile device terminal to be provided normally works to detect short message managing module 11.Only when short message managing module 14 is working properly, just get the data after encryption by this module, if abnormal, to Mobile solution client feedback read error.The measuring ability that mobile device terminal provides is according to different device ends, and the difference of system platform and different, by mobile device terminal by oneself, does not describe in detail at this.
Except above-mentioned two embodiments, can also be sent by short message managing module and read and be sent by short message managing module, be read by address list management module.Because principle is similar, can analogize, just repeat no longer one by one here.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.

Claims (3)

1. the data communications method between Mobile solution client and smart card, is characterized in that, the method comprises:
A, when user needs to carry out business data processing by smart card, send business data processing instruction to Mobile solution client, the business data processing instruction that Mobile solution client receives from user generates data request information; Described data request information is HTML (Hypertext Markup Language) form, note request format, phone book contact form or user-defined format;
Operational order in request of data described in B, the identification of Mobile solution client, and judge the type of this operational order, if belong to type data being sent to smart card, then enter step C; If belong to the type reading data from smart card, then enter step e;
C, judging whether the need data length to be processed received exceedes the predetermined length of mobile terminal restriction, if exceed, then by needing Data Division to be processed to become some the data segments being less than or equal to predetermined length, and performing step D; Otherwise, before these data, add data length and hop count by mobile subscriber's client, then enter step D; Described by exceed mobile terminal restriction need Data Division to be processed become some the data segments being less than or equal to predetermined length, comprising: C1, split after each data segment mainly comprise data length, hop count and real data; If the described need of C2 data to be processed have multiple, then after Data Division completes, be every section by mobile subscriber's client and added data length and hop count by before the data that split;
D, the data segment of all interpolation data lengths and hop count is assembled into the form of associated person information or note, and complete associated person information or note are sent to address list management module or short message managing module accordingly, then carry out generation and the process of transmitting of next associated person information or short message; Or after the generation completing all associated person informations or note, then unification is sent to address list management module or short message managing module; Associated person information or note are sent to smart card by system kernel by address list management module or short message managing module; Store in the mode of contact person or note after smart card processes; The process that the described data segment by all interpolation data lengths and hop count is assembled into associated person information comprises: D1, a newly-built contact person, and the field contents of contact person comprises name of contact person, telephone number; D2, will add in the described newly-built name of contact person of data segment write of data length and hop count; The number of the telephone number write agreement of D3, contact person, this number can be identified in smart card one end;
Described smart card carries out data processing to the associated person information received or short message, stores after having processed according to original fractionation rule, is convenient to by correct reading;
E, Mobile solution client is utilized to send contact person or note read requests to address list management module or short message managing module, read associated person information in smart card or note by address list management module or short message managing module and system kernel module again, to be readly complete backward described Mobile solution client feedback information;
After the reading received from address list management module or short message managing module of F, Mobile solution client completes feedback information, judge the number of name of contact person or note; If be greater than one, then many name of contact persons or note are combined into one; Otherwise mobile subscriber's client obtains the result read.
2. the data communications method between Mobile solution client according to claim 1 and smart card, is characterized in that, taking a step forward of step e comprises:
The measuring ability that Mobile solution client call mobile terminal provides, to detect address list management module or whether short message managing module normally works, if working properly, then gets the data after process by this module; Otherwise, then to Mobile solution client feedback read error.
3. a mobile terminal, comprises system kernel module, short message managing module and address list management module, it is characterized in that, also comprise Mobile solution client, and the communication process between described Mobile solution client and smart card is as follows:
A, when user needs to carry out business data processing by smart card, send business data processing instruction to Mobile solution client, the business data processing instruction that Mobile solution client receives from user generates data request information; Described data request information is HTML (Hypertext Markup Language) form, note request format, phone book contact form or user-defined format;
Operational order in request of data described in B, the identification of Mobile solution client, and judge the type of this operational order, if belong to type data being sent to smart card, then enter step C; If belong to the type reading data from smart card, then enter step e;
C, judging whether the need data length to be processed received exceedes the predetermined length of mobile terminal restriction, if exceed, then by needing Data Division to be processed to become some the data segments being less than or equal to predetermined length, and performing step D; Otherwise, before these data, add data length and hop count by mobile subscriber's client, then enter step D; Described by exceed mobile terminal restriction need Data Division to be processed become some the data segments being less than or equal to predetermined length, comprising: C1, split after each data segment mainly comprise data length, hop count and real data; If the described need of C2 data to be processed have multiple, then after Data Division completes, be every section by mobile subscriber's client and added data length and hop count by before the data that split;
D, the data segment of all interpolation data lengths and hop count is assembled into the form of associated person information or note, and complete associated person information or note are sent to address list management module or short message managing module accordingly, then carry out generation and the process of transmitting of next associated person information or short message; Or after the generation completing all associated person informations or note, then unification is sent to address list management module or short message managing module; Associated person information or note are sent to smart card by system kernel by address list management module or short message managing module; Store in the mode of contact person or note after smart card processes; The process that the described data segment by all interpolation data lengths and hop count is assembled into associated person information comprises: D1, a newly-built contact person, and the field contents of contact person comprises name of contact person, telephone number; D2, will add in the described newly-built name of contact person of data segment write of data length and hop count; The number of the telephone number write agreement of D3, contact person, this number can be identified in smart card one end;
Described smart card carries out data processing to the associated person information received or short message, stores after having processed according to original fractionation rule, is convenient to by correct reading;
E, Mobile solution client is utilized to send contact person or note read requests to address list management module or short message managing module, again by address list management module or short message managing module and system kernel module read in smart card associated person information or note, to be readly complete backward described Mobile solution client feedback information;
After the reading received from address list management module or short message managing module of F, Mobile solution client completes feedback information, judge the number of name of contact person or note; If be greater than one, then many name of contact persons or note are combined into one; Otherwise mobile subscriber's client obtains the result read.
CN201110293150.2A 2011-09-30 2011-09-30 Method for communication between mobile application client and intelligent card and device Expired - Fee Related CN102316428B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201110293150.2A CN102316428B (en) 2011-09-30 2011-09-30 Method for communication between mobile application client and intelligent card and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201110293150.2A CN102316428B (en) 2011-09-30 2011-09-30 Method for communication between mobile application client and intelligent card and device

Publications (2)

Publication Number Publication Date
CN102316428A CN102316428A (en) 2012-01-11
CN102316428B true CN102316428B (en) 2015-04-15

Family

ID=45429176

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201110293150.2A Expired - Fee Related CN102316428B (en) 2011-09-30 2011-09-30 Method for communication between mobile application client and intelligent card and device

Country Status (1)

Country Link
CN (1) CN102316428B (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103914712B (en) * 2012-12-29 2017-09-29 北京握奇数据系统有限公司 Realization method and system being applied a kind of contact type intelligent card more
CN105933363B (en) * 2016-07-14 2017-07-04 京东方科技集团股份有限公司 A kind of method for processing business, device and unidirectional digital television set-top box
CN110971315B (en) * 2019-12-06 2022-02-11 广东汇泰龙科技股份有限公司 Method and system for detecting communication signal between CPU (Central processing Unit) induction card and intelligent lock
CN112330452B (en) * 2020-11-17 2024-04-23 杭州大搜车汽车服务有限公司 Transaction data processing method, device, computer equipment and storage medium
CN114679752B (en) * 2022-03-29 2024-04-19 青岛海信移动通信技术有限公司 Method for sharing wireless communication capability by double systems and terminal equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101222333A (en) * 2007-12-24 2008-07-16 北京握奇数据系统有限公司 Data transaction processing method and apparatus
CN101594425A (en) * 2009-06-29 2009-12-02 钱袋网(北京)信息技术有限公司 Portable terminal
US7801883B2 (en) * 2005-01-19 2010-09-21 Samsung Electronics Co., Ltd. Method and apparatus for improving data processing speed through storage of record information of identity module
CN101977377A (en) * 2010-09-27 2011-02-16 宇龙计算机通信科技(深圳)有限公司 Method, system and mobile terminal for reading digital certificate in SIM (Subscriber Identity Module) card
CN102055833A (en) * 2009-10-31 2011-05-11 比亚迪股份有限公司 Method of event record storage for low-end mobile phone by using SIM card

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7801883B2 (en) * 2005-01-19 2010-09-21 Samsung Electronics Co., Ltd. Method and apparatus for improving data processing speed through storage of record information of identity module
CN101222333A (en) * 2007-12-24 2008-07-16 北京握奇数据系统有限公司 Data transaction processing method and apparatus
CN101594425A (en) * 2009-06-29 2009-12-02 钱袋网(北京)信息技术有限公司 Portable terminal
CN102055833A (en) * 2009-10-31 2011-05-11 比亚迪股份有限公司 Method of event record storage for low-end mobile phone by using SIM card
CN101977377A (en) * 2010-09-27 2011-02-16 宇龙计算机通信科技(深圳)有限公司 Method, system and mobile terminal for reading digital certificate in SIM (Subscriber Identity Module) card

Also Published As

Publication number Publication date
CN102316428A (en) 2012-01-11

Similar Documents

Publication Publication Date Title
CN102316428B (en) Method for communication between mobile application client and intelligent card and device
WO2020103559A1 (en) Payment processing method for offline scenario, server, and readable storage medium
CN110688662A (en) Sensitive data desensitization and inverse desensitization method and electronic equipment
CN107133830B (en) Method and system for issuing electronic invoice based on short message
CN112287372B (en) Method and apparatus for protecting clipboard privacy
CN102638446A (en) Secure smart poster
CN106788972A (en) A kind of train ticket self-help ticket-buying fetching system based on block chain authentication
CN110148014B (en) Information processing method, information processing device, blockchain node equipment and storage medium
KR101168272B1 (en) The system of issuing nfc ticket and method thereof
CN112600830B (en) Service data processing method and device, electronic equipment and storage medium
CN103544114B (en) Based on many M1 card control system and the control method thereof of single CPU card
CN104281272A (en) Password input processing method and device
CN102387255B (en) Method and device for utilizing intelligent card to process third-party expanded service data
CN111008325A (en) Data query method, device, electronic equipment and system
US11818116B2 (en) Network gateway messaging systems and methods
CN106559386A (en) A kind of authentication method and device
CN108833500B (en) Service calling method, service providing method, data transmission method and server
CN107872321A (en) The method and electronic identity terminal device of electronic identity authentication
CN107451301B (en) Processing method, device, equipment and storage medium for real-time delivery bill mail
CN105373918A (en) Multi-POS terminal integrated payment system and method
WO2018152978A1 (en) Method and device for prompting change of account-bound telephone number and computer storage medium
CN107203877A (en) The method and apparatus for closely realizing business between account
CN107172068A (en) Information sending control method, server, system, device and storage medium
CN101841806A (en) Service card information processing method, device and system and communication terminal
CN107705384B (en) Attendance checking method, system, electronic device and storage medium

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
ASS Succession or assignment of patent right

Owner name: BEIJING ZHONGQING YIHE TECHNOLOGY CO., LTD.

Free format text: FORMER OWNER: FUJIAN LIXIN (BEIJING) TECHNOLOGY CO., LTD.

Effective date: 20140212

COR Change of bibliographic data

Free format text: CORRECT: ADDRESS; FROM: 100094 HAIDIAN, BEIJING TO: 100086 HAIDIAN, BEIJING

TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20140212

Address after: 100086, room 12, building 47, hospital B, No. 317-1 West Third Ring Road, Haidian District, Beijing

Applicant after: BEIJING ZHONGQINGHE SCIENCE AND TECHNOLOGY CO., LTD.

Address before: Kim Fu No. 9 building, 100094 Beijing city Haidian District anningzhuang west room 609

Applicant before: Fuyuan Lixin (Beijing) Technology Co., Ltd.

C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20150415

Termination date: 20200930