CN104580635A - Method for Linking Contact Information Based on Basic Document Data Validity - Google Patents

Abstract

The invention discloses a method for establishing connection between contact person information according to data validity of a memory basic file of a smart card. In the starting process of the mobile device provided with the intelligent card, whether the link to be established in the basic file of the index management telephone directory is correct or not is judged according to the validity of each corresponding data in the basic file of the index management telephone directory and the basic file of the abbreviated dialing number. Therefore, by deleting the error connection of the invalid data corresponding to the basic abbreviated dialing number file from the effective index of the basic directory file of the index management, the invention can avoid displaying blank contact information after the intelligent card is started up in other devices, thereby improving the data correctness and the operation fluency of the directory.

Description

Method for Linking Contact Information Based on Basic Document Data Validity

technical field

The present invention relates to a method for establishing links between contact information according to the data validity of the basic file stored in the smart card, in particular to a method for managing the validity of the corresponding relationship between the basic file of the phone book and the basic file of abbreviated dial numbers according to the index stored in the smart card method to link contact information.

Background technique

A Subscriber Identity Module (SIM) card is a smart card used to store user identification data for mobile phone services, and can also be used to store SMS data and phone numbers. In terms of external hardware, the SIM card consists of a central processing unit (central process unit, CPU), a read-only memory (read-only memory, ROM), a random access memory (random access memory, RAM), and an electronic erasable programmed memory card. It is composed of components such as electrically erasable programmable read-only memory (EEPROM) and input/output (I/O) circuits. In terms of internal data, the SIM card adopts a hierarchical logical data structure, which includes three types: elementary file (EF), dedicated file (DF) and master file (MF). The data.

The basic file structure is divided into three types: transparent, linear fixed, and cyclic, which are used to store data of different nature. The transparent basic file is a continuous data file with the unit of byte (byte), and data access is handled by specifying the offset (offset) position and the access data length. The linear fixed basic file and the circular basic file are continuous and fixed-length data files with the unit of record (record), and the data access is based on the unit of record.

According to the specification TS31.102 formulated by the 3rd Generation Partnership Project (3GPP), the proprietary file DFPHONEBOOK includes all basic files related to phonebook information, such as the phonebook reference file (phonebook reference file) EFPBR, the name abbreviations and types of other basic files are shown in the table below:

EF _AAS stands for additional number Alphastring (additional number Alphastring) basic file, which belongs to the third type (Type3). EFADN stands for abbreviated dialing numbers (abbreviated dialing numbers) basic file, which belongs to the first type (Type1). EFANR stands for additional number (additional number) elementary file, which can belong to the first type or the second type (Type2). EFEMAIL stands for E-mail Elementary File, which can belong to the first type or the second type. EF _EXT1 stands for extension (extension1) basic file and belongs to the third type. EF _GAS stands for elementary file of grouping information Alphastring (grouping information Alphastring), and belongs to the third type. EF _GRP stands for grouping file (grouping file) basic file and belongs to the third type. EF _IAP stands for index administration phone book (indexadministration phone book) elementary file and belongs to the first type. EF _PBC stands for Phone Book Control Elementary File and belongs to the first type. EF _SNE stands for second name entry (second name entry) elementary file, which can belong to the first type or the second type. EF _UID stands for unique identifier (unique identifier) elementary file, and belongs to the first type. EF _CCP1 represents the basic file of capability configuration parameters (capability configuration parameters1), which belongs to the third type.

In the phonebook reference file elementary file EF _PBR , the first data name marked with the label "A8" corresponds to a main basic file (master EF), and the subsequent data names marked with the label "A8" correspond to the first Type of elementary files, the data names marked with the label "A9" correspond to the second type of elementary files, and the data names marked with the label "AA" correspond to the third type of elementary files. The first-type basic file and the main basic file include the same number of data items, and each data in the first-type basic file is mapped to a corresponding data in the main basic file in a one-to-one manner. The number of data items included in the second type basic file is less than the number of data items included in the main basic file, and each data item in the second type basic file is linked to by the index management phonebook basic file EF _IAP of the first type A corresponding piece of data in the main basic file. Each piece of data in the third type of primary file is linked to a corresponding piece of data in the main primary file through the data identifier (record identifier) of the data included in other basic files in the phonebook reference file primary file EF _PBR .

Assume that the phone book in the SIM card stores two contact information of a specific contact person, wherein the contact person's phone number has the first type of abbreviated dial number basic file EF _ADN , and the contact person's email has the second type of email basic file The file EF _EMAIL , and the second type of email basic file EF _EMAIL needs to link to the basic file EF _ADN of the abbreviated dialing number through the index management phonebook basic file EF _IAP . In the prior art, when the user deletes the data of this specific contact, only the relevant data in the basic files EF _ADN and EF _EMAIL will be deleted, and the relevant data in the basic file EF _IAP of the index management phonebook will not be processed. After deleting the data of this particular contact, the relevant data in the basic file EF _IAP has become an invalid indicator. If this SIM card is inserted into other devices, the invalid index of the basic file EF _IAP of the index management phonebook may cause a blank contact information to be displayed in the phonebook, so it is easy to confuse the user and affect the smoothness of operation.

Contents of the invention

In view of the above-mentioned problems in the prior art, the purpose of the present invention is to provide a method for linking contact information according to the effectiveness of the corresponding relationship between the smart card memory index management phonebook basic file and the abbreviated dial number basic file, so as to improve the correctness of the phonebook data. performance and operational fluency.

To achieve the above object, the present invention discloses a method for linking contact information, which includes installing a smart card to a mobile device; during a boot process of the mobile device, a first basic file stored in the smart card Read a first data in; when the content of the first data corresponds to an effective index, read a corresponding second data in a second basic file in the memory of the smart card according to the effective index; and when the content of the second data corresponds to an invalid data, updating the content of the first data to correspond to an invalid index. Wherein, the first basic file includes at least one index, which is used to link a specific data in a third basic file to a specific data in the second basic file; the second basic file is used to store a link a first contact information of a person; and the third basic file is used to store a second contact information of the contact person.

Description of drawings

FIG. 1 is a flow chart of a method for managing links of contact information in a smart card according to the present invention.

2 to 4 are schematic diagrams of basic files defined according to the 3rd Generation Partnership Project specification.

Wherein, the reference signs are explained as follows:

110～200 steps

11～17 Fields

Detailed ways

The present invention provides a method for managing the connection of contact information in a smart card, which can be applied to different types of mobile devices, including mobile phones, personal digital assistants (personal digital assistants, PDAs), palm-sized (handheld) computers, tablet (tablet) ) computer, mini desktop (nettop) computer, notebook (laptop) computer, or other devices with communication functions. However, the type of mobile device does not limit the scope of the present invention.

In the mobile device to which the method of the present invention is applied, different types of smart cards can be installed therein, such as the SIM card of the Global System for Mobile Communications (GSM) system, the Universal Mobile Telecommunications System (UMTS) USIM card, code division multiple access (CDMA) system removable user identity module (removable user identity module, R-UIM) card and CDMA user identity module (CSIM) card, etc. Although the description of the present invention uses a SIM/USIM card to illustrate the embodiment, the type of smart card installed in the mobile device does not limit the scope of the present invention.

In the mobile device to which the method of the present invention is applied, smart cards of different sizes can be installed therein, such as a standard SIM card (Mini SIM), a micro SIM card (Micro SIM) or a nano SIM card (Nano SIM) and the like. However, the size of the smart card installed in the mobile device does not limit the scope of the present invention.

Fig. 1 is a flow chart of a method for managing contact information links in a smart card in the present invention, which includes the following steps:

Step 110: During the boot process of the mobile device, determine whether the installed smart card supports specific types of data that need to be linked through other basic files; if yes, perform step 120; if not, perform step 200.

Step 120: read the i-th data in the smart card memory index management phonebook basic file EF _IAP ; execute step 130.

Step 130: Determine whether the content of the i-th data in the basic file EF _IAP of the index management phonebook corresponds to an invalid index; if so, perform step 170; if not, perform step 140.

Step 140: Determine whether the content corresponding to the i-th data in the basic file EF _ADN of the abbreviated dialing number corresponds to invalid data; if yes, execute step 150; if not, execute step 160.

Step 150: update the content of the i-th data of the basic file EF _IAP in the index management phonebook to make it correspond to the invalid index; execute step 170.

Step 160: Link a corresponding piece of data in a second type basic file specified by the i-th data in the index management phonebook basic file EF _IAP to the i-th data in the abbreviated dialing number basic file EF _ADN ; Execute Step 170.

Step 170: Judging whether each piece of data in the smart card memory index management phonebook basic file EF _IAP has been read; if so, perform step 190; if not, perform step 180.

Step 180: add 1 to the value of i; execute step 130.

Step 190: reset the value of i; execute step 200.

Step 200: Continue to execute other booting steps.

For the convenience of illustration, assume that the phone book in the smart card stores two contact information of a specific contact person, wherein the contact person's phone number exists in the first type of abbreviated dialing number basic file EF _ADN , and the contact person's email exists in the second type The email basic file EF _EMAIL , and the second type of email basic file EF _EMAIL needs to be linked to the abbreviated dialing number basic file EF _ADN through the index management phonebook basic file EF _IAP . In subsequent operations, the user may delete all contact information of this specific contact.

FIG. 2 is a schematic diagram of an elementary file EF _PBR defined according to the 3rd Generation Partnership Project specification TS31.102. As shown in field 11, the phonebook reference file elementary file EF _PBR adopts a linear fixed data structure. As shown in field 12, bytes 1 to X (X is a positive integer greater than 1) are used to store tag length value (TLV) objects representing basic files included in the phonebook structure. The definitions of other fields in the basic file EF _PBR of the phonebook reference file are detailed in the 3rd Generation Partnership Project specification TS31.102, and will not be repeated here.

In step 110, the present invention can read the basic phonebook reference file EF _PBR stored in the smart card during the boot process of the mobile device, and judge whether the smart card supports a specific type of data according to the tag length value objects represented by bytes 1 to X . In the embodiment of the present invention, the specific type of data can be an additional number basic file EF _ANR , an electronic mail basic file EF _EMAIL or a second name input basic file EF _SNE and other second-type basic files, which need to manage the basic phonebook through the index The file EF _IAP is required to be linked to the basic file EF _ADN for Abbreviated Dialing Numbers. However, the second type of elementary file used does not limit the scope of the present invention.

FIG. 3 is a schematic diagram of an index management phonebook elementary file EF _IAP defined according to the 3rd Generation Partnership Project specification TS31.102. As shown in field 13, the index management phonebook elementary file EF _IAP adopts a linear fixed data structure. As shown in field 14, bytes 1 to X are used to respectively store the record numbers of the first to Xth objects appearing after the tag A9. The definitions of other fields in the basic file EF _IAP for index management phonebook are detailed in the 3rd Generation Partnership Project specification TS31.102, and will not be repeated here.

In step 120, the present invention can read the i-th data stored in the i-th bit in the smart card memory index management phonebook elementary file EF _IAP . Wherein, i is a positive integer between 1 and X, and its initial value can be set to 1.

In step 130, the present invention judges whether the content of the i-th data in the basic file EF _IAP of the index management phonebook corresponds to an invalid index. According to the 3rd Generation Partnership Project specification TS31.102, when the content of the i-th data in the basic file EF _IAP of the index management phonebook is "FF", it is an invalid index, which means that there is no need to link any second type of data to For the i-th data in the basic file EF _ADN of the abbreviated dialing number, the present invention will execute steps 170 and 180 to execute the judgment process of steps 120 and 130 for each data in the basic file EF _IAP of the index management phonebook. When the content of the i-th item of data in the basic file EF _IAP of the index management phonebook is not an invalid indicator of "FF", the present invention will then execute step 140 .

FIG. 4 is a schematic diagram of an abbreviated dialed number elementary file EF _ADN defined according to the 3rd Generation Partnership Project specification TS31.102. As shown in field 15, the basic file EF _ADN for abbreviated dialed numbers adopts a linear fixed data structure. As shown in field 16, bytes 1 to X are alpha identifiers for the first to Xth phone numbers respectively. As shown in field 17, bytes X+3 to X+12 are used to store dial numbers and supplementary service control (SSC) strings. The definition of other fields in the basic file EF _ADN of the abbreviated dialed number is described in detail in the 3rd Generation Partnership Project specification TS31.102, and will not be repeated here.

As mentioned above, each item of data in the first type of index management phonebook basic file EF _IAP is mapped to a corresponding piece of data in the main abbreviated dialing number basic file EF _ADN in a one-to-one manner. In step 140, the present invention judges whether the content of the ith data in the basic file EF _ADN of the abbreviated dialing number corresponds to invalid data.

According to the 3rd Generation Partnership Project specification TS31.102, when the i-th data content corresponding to the i-th digit in the abbreviated dialing number basic file EF _ADN is "FF", it means that when the i-th data in the abbreviated dialing number basic file EF _ADN The record data is invalid (for example, the previously stored phone number has been deleted). At this moment, the present invention can judge that this situation is a wrong connection between the valid index of the index management phonebook basic file EF _IAP and the invalid data of the abbreviated dialing number basic file EF _ADN , so in step 150, the index management phonebook The content of the i-th data of the basic file EF _IAP is updated to "FF" so that it corresponds to an invalid index. Afterwards, if the user uses this smart card on other devices, during the booting process, the error link that the valid index of the above-mentioned index management phonebook basic file EF _IAP corresponds to the invalid data of the basic file EF _ADN of the abbreviated dialing number will not be read, Therefore, only valid contact information will be displayed when opening the phonebook.

When the i-th data content corresponding to the i-th digit in the abbreviated dialing number basic file EF _ADN is not invalid data of "FF", the present invention can judge that this situation is the effective index corresponding to the index management phone book basic file EF _IAP To the correct connection of the effective data of the basic file EF _ADN of the abbreviated dialing number, this moment can then be carried out in step 160, and then will index management telephone book basic file EF _IAP in the specified second type basic file of the i-th data. The corresponding item data is linked to the i-th item data in the basic file EF _ADN of the abbreviated dialing number. Afterwards, regardless of whether the user is using this smart card on the original device or other devices, all contact information about this particular contact can be seen correctly when opening the phonebook (for example, the contacts in the basic file EF _ADN of the abbreviated dialing number phone number and contact email stored in the email element file EF _EMAIL ).

In steps 170 and 180, the present invention can execute the judgment step of step 130 or 140 for each piece of data in the basic file EF _IAP of the index management phonebook, so as to establish the corresponding abbreviation of the effective index of the basic file EF _IAP of the index management phonebook All correct linkages of valid data of Dial Number Basic File EF _ADN and update Index Management Phonebook Basic for all incorrect linkages of valid indicators of Index Management Phonebook Basic File EF _IAP to invalid data of Abbreviated Dial Number Basic File EF _ADN The relevant content of the file EF _IAP makes it correspond to an invalid indicator.

In summary, the present invention can update the index management phonebook basic file EF IAP according to the validity of each piece of data corresponding in the smart card memory index management phonebook basic file EF _IAP and the abbreviated dial number basic _file EF _ADN . data. When the user deletes the data of a specific contact, in addition to deleting the relevant data in the first type/second type basic file, the relevant data in the index management phonebook basic file EF _IAP will also be processed. By deleting the erroneous link between the effective index of the basic file EF _IAP of the index management phonebook and the invalid data of the basic file EF _ADN of the abbreviated dialing number, it is possible to prevent the smart card from displaying a blank contact information after other devices are powered on, thereby improving the telephone Book data correctness and operation fluency.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (8)

1. one kind links coordinator's letter according to the data validity of smart card memory constituent instruments

The method of breath, it comprises:

Described smart card is mounted to a running gear;

In a starting procedure of described running gear, in one first constituent instruments of described smart card memory, read one first data;

When the content of described first data corresponds to an efficiency index, in one second constituent instruments of described smart card memory, read one second corresponding data according to described efficiency index; And

When the content of described second data corresponds to an invalid data, the content upgrading described first data makes it correspond to an invalid index, wherein:

Described first constituent instruments comprise at least one index, are used for a particular data in one the 3rd constituent instruments to be linked to a particular data in described second constituent instruments;

Described second constituent instruments are used to one first contact information of storage one coordinator; And

Described 3rd constituent instruments are used to one second contact information storing described coordinator.

2. the method for claim 1, is characterized in that, separately comprises:

When the content of described second data corresponds to valid data, in described 3rd constituent instruments, read one the 3rd corresponding data according to described efficiency index; And

By described 3rd data link to described second data.

3. the method for claim 1, is characterized in that, comprising:

In described starting procedure, judge whether described smart card supports the type of described 3rd constituent instruments according to one the 4th constituent instruments of described smart card memory.

4. method as claimed in claim 3, is characterized in that, the telephone directory reference file constituent instruments that described 4th constituent instruments define for a third generation partner program specification.

5. the method for claim 1, it is characterized in that, the index management telephone directory constituent instruments that described first constituent instruments define for a third generation partner program specification, and the abbreviation dialed number constituent instruments that described second constituent instruments define for described third generation partner program specification.

6. the method for claim 1, is characterized in that, the additional number constituent instruments that described 3rd constituent instruments define for a third generation partner program specification, Email constituent instruments, or one second title input constituent instruments.

7. the method for claim 1, it is characterized in that, the first kind constituent instruments that described first constituent instruments and described second constituent instruments define for a third generation partner program specification, and the Second Type constituent instruments that described 3rd constituent instruments define for described third generation partner program specification.

8. the method for claim 1, is characterized in that, in described first constituent instruments, each data to be videoed each data corresponding to described second constituent instruments in mode one to one.