TWI539786B - Method of establishing links between contact information according to data validity of elementary files stored in smartcard - Google Patents

Description

According to the validity of the data of the smart card memory basic file between the contact information Method of establishing a link

A method for establishing a connection between contact information based on the validity of the data of the basic file of the smart card memory, in particular, a method for managing the correspondence between the basic file of the phone book and the basic file of the abbreviation dial number based on the smart card memory index. A method of establishing a link between people's information.

A Subscriber Identity Module (SIM) card is a smart card used to store user identification data for mobile phone services. It can also be used to store SMS messages and phone numbers. In terms of external hardware, the SIM card is composed of a central processing unit (CPU), a read-only memory (ROM), a random access memory (RAM), and an electronically smeared It consists 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). data of.

The basic file structure is divided into three types: transparent, linear fixed, and cyclic, to store data of different natures. A transparent basic file is a continuous data file in units of bytes. The access to the data is handled by specifying the offset position and the length of the accessed data. The linear fixed basic file and the cyclic basic file are continuous and fixed length data files in units of records, and the access of the data is in units of records.

According to the specification TS 31.102 developed by the 3rd Generation Partnership Project (3GPP), the proprietary file DF _PHONEBOOK contains all the basic files related to the phone book information, such as the phone book reference file. ) EF _PBR , the names and types of other basic files are as follows:

EF _AAS stands for the additional number Alpha string basic file and belongs to the Type 3 type. The EF _ADN stands for the abbreviated dialing numbers basic file and belongs to the Type 1 type. EF _ANR stands for an additional number basic file, which can be of Type 1 or Type 2. EF _EMAIL stands for email basic file and can be of Type 1 or Type 2 type. EF _EXT1 stands for extension (extension1) basic file and belongs to Type 3 type. EF _GAS stands for grouping information Alpha string basic file and belongs to Type 3. EF _GRP stands for grouping file basic file and belongs to Type 1. The EF _IAP stands for the index administration phone book basic file and belongs to the Type 1 type. EF _PBC stands for phone book control basic file and belongs to Type 1 type. EF _SNE stands for second name entry basic file and can belong to Type 1 or Type 2 type. The EF _UID stands for a unique identifier basic file and belongs to the Type 1 type. EF _CCP1 stands for the basic configuration file of the capability configuration parameters 1 and belongs to the Type 3 type.

In the phone book reference file basic 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 indicated by the label "A8" correspond to For the basic file of the Type 1 type, the data name indicated by the label "A9" corresponds to the basic file of the Type 2 type, and the data name indicated by the label "AA" corresponds to the basic file of the Type 3 type. The Type 1 type basic file and the main basic file contain the same number of data, and each piece of the Type 1 type basic file is mapped to a corresponding one in the main basic file in a one-to-one manner. The Type 2 type basic file contains less data than the main basic file, and each type of Type 2 basic file is linked to the main file through the Type 1 type index management phone book basic file EF _IAP. Corresponding pen data in the basic documents. Each type of data in the Type 3 basic file is linked to the corresponding data in the main basic file through the record identifier of the data contained in other basic files in the basic file EF _PBR .

Assume that the phone book in the SIM card has two contacts for a specific contact, wherein the contact person's phone number is a Type 1 type abbreviated dial number basic file EF _ADN , and the contact person's email is a Type 2 type of electronic device. The mail basic file EF _EMAIL and the Type 2 type email basic file EF _{EMAIL are} linked to the abbreviated dialing number basic file EF _ADN through the index management phone book basic file EF _IAP . In the prior art, when the user deletes the data of the specific contact, only the related materials in the basic files EF _ADN and EF _EMAIL are deleted, and the related information in the index management phone book basic file EF _IAP is not processed. After deleting the information of this particular contact, the relevant information in the basic file EF _IAP has become an invalid indicator. If this SIM card is inserted into another device, the invalid indicator of the index management phone book basic file EF_IAP may cause a blank contact information to be displayed in the phone book, so it is easy to confuse the user and affect the operation fluency.

The present invention provides a method for establishing a connection between contact information, comprising: installing a smart card to a mobile device; and reading in a first basic file of the smart card memory in a booting process of the mobile device Taking a first data; when the content of the first data corresponds to a valid indicator, reading a corresponding second data in a second basic file of the smart card memory according to the effective indicator; and when the first When the content of the second data corresponds to an invalid data, the content of the first data is updated to correspond to an invalid indicator. The first basic file includes at least one indicator for linking 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 one of the contacts First contact information; and the third basic file is used to store one of the contact's second contact information.

110~200‧‧‧Steps

11~17‧‧‧ fields

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

Figures 2 through 4 are schematic diagrams of basic files defined in accordance with the 3GPP specifications.

The present invention provides a method for managing a link of contact information in a smart card, which can be applied to different types of mobile devices, including a mobile phone, a personal digital assistant (PDA), a handheld computer, and a tablet ( Tablet) A computer, a minitop computer, a laptop computer, or other device with communication capabilities. 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 a SIM card of a global system for mobile communications (GSM) system, and a universal mobile telecommunications system (universal mobile telecommunications system). UMTS) USIM card, code division multiple access (CDMA) system removable user identity module (R-UIM) card and CDMA user identification module (CSIM) card, etc. . Although the present invention has been described with reference to a SIM card, 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). However, the size of the smart card installed in the mobile device does not limit the scope of the present invention.

1 is a flow chart of a method for managing a link of contact information in a smart card according to the present invention, which includes the following steps: Step 110: In the boot process of the mobile device, determine whether the installed smart card supports other devices. Basic files to create specific types of links; if so, Step 120 is performed; if no, step 200 is performed.

Step 120: Read the i-th data in the smart card memory index management phone book basic file EF _IAP ; go to step 130.

Step 130: Determine whether the content of the ith data in the index management phone book basic file EF _IAP corresponds to the invalid indicator; if yes, go to step 170; if no, go to step 140.

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

Step 150: Update the content of the i-th data of the basic file EF _{IAP in} the index management phone book to correspond to the invalid indicator; and perform step 170.

Step 160: Link a corresponding one of the Type 2 type basic files specified by the i-th data in the index management phone book basic file EF _IAP to the i-th data in the abbreviation dialing number basic file EF _ADN ; and execute step 170 .

Step 170: Determine whether each data in the smart card memory index management phone book basic file EF _IAP has been read; if yes, go to step 190; if no, go to step 180.

Step 180: Add 1 to the value of i; perform step 130.

Step 190: Reset the value of i; perform step 200.

Step 200: Continue to perform other booting steps.

For convenience of explanation, it is assumed that the phone book in the smart card stores two contact forms of a specific contact person, wherein the contact person's phone number is a type 1 type abbreviated dial number basic file EF _ADN , and the contact person's e-mail exists in the type The type 2 email basic file EF _EMAIL , and the Type 2 type email basic file EF _EMAIL is linked to the abbreviated dialing number basic file EF _ADN through the index management phone book basic file EF _IAP . In subsequent operations, it is possible for the user to delete all contact details for this particular contact.

Figure 2 is a schematic diagram of the phone book reference file base file EF _PBR as defined by the 3GPP specification TS 31.102. As shown in field 11, the basic file EF _PBR uses a linear fixed data architecture. As indicated by field 12, bytes 1 through X are used to store tag length value (TLV) objects representing the basic files contained in the phone book structure. The definitions of other fields in the basic file EF _PBR are described in detail in the 3GPP specification TS 31.102, and are not described here.

In step 110, the present invention can read the phone book reference file basic file EF _{PBR of the} smart card memory in the boot process of the mobile device, and determine whether the smart card supports a specific type according to the TLV object represented by the byte groups 1 to X. data. In the embodiment of the present invention, the specific type of data may be a basic file of Type 2 type such as EF _ANR , EF _EMAIL or EF _SNE, and the index file management file basic file EF _{IAP is} required to be linked to the abbreviated dialing number basic file EF _ADN . However, the Type 2 type basic file used does not limit the scope of the present invention.

Figure 3 is a schematic diagram of an index management phonebook base file EF _IAP as defined by the 3GPP specification TS 31.102. As shown in field 13, the basic file EF _IAP uses a linear fixed data architecture. As indicated by field 14, bytes 1 through X are used to store the record numbers of the first to Xth objects after the label A9 is stored, respectively. The definitions of the other fields in the basic file EF _IAP are described in detail in the 3GPP specification TS 31.102, and are not described 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 phone book basic file EF _IAP . Where i is a positive integer between 1 and X, and its initial value can be set to 1.

In step 130, the present invention determines whether the content of the i-th data in the index management phone book basic file EF _IAP corresponds to an invalid indicator. According to the 3GPP specification TS 31.102, when the content of the ith data in the EF _IAP is "FF", it is an invalid indicator, which means that it is not necessary to link any type 2 data to the abbreviation dial number basic file EF _ADN in the ith data. At this time, the present invention executes steps 170 and 180 to perform the judgment flow of steps 120 and 130 for each piece of data in the index management phone book basic file EF _IAP . When the content of the ith data in the EF _IAP is not an invalid indicator of "FF", the present invention proceeds to step 140.

Figure 4 is a schematic diagram of the abbreviated dialing number basic file EF _ADN as defined by the 3GPP specification TS 31.102. As shown in field 15, the basic file EF _ADN uses a linear fixed data architecture. As indicated by field 16, bytes 1 through X are used to respectively identify the alpha identification codes of the first to Xth telephone numbers. As indicated by field 17, bytes X+3 through X+12 are used to store dialed numbers and supplementary service control (SSC) strings. The definitions of the other fields in the basic file EF _ADN are described in detail in the 3GPP specification TS 31.102, and are not described here.

As described above, each piece of data in the basic file EF _IAP of the Type 1 type is mapped in a one-to-one manner to a corresponding data in the main basic file EF _ADN . In step 140, the present invention determines whether the content of the i-th data in the abbreviated dialing number basic file EF _ADN corresponds to the invalid data.

According to the 3GPP specification TS 31.102, when the ith data content corresponding to the i-th bit in the EF _ADN is "FF", it means that the ith data of the EF _ADN is invalid (for example, the previously stored phone number has been deleted). ). At this time, the present invention can determine that the situation is an error link of the valid index of the EF _IAP corresponding to the invalid data of the EF _ADN , and therefore, the content of the i-th data of the index management phone book basic file EF _IAP is subsequently indexed in step 150. Update to "FF" to match the invalid indicator. After that, if the user uses the smart card on other devices, the error link of the EF _IAP valid indicator corresponding to the EF _ADN invalid data will not be read during the boot process, so only the phone book will be displayed when the phone book is opened. Effective contact information.

When the content of the i-th data corresponding to the i-th bit in the EF _ADN is not invalid data of "FF", the present invention can determine that the situation is the correct link of the valid index of the EF _IAP to the valid data of the EF _ADN , Then, in step 160, a corresponding one of the Type 2 type basic files specified by the i-th data in the index management phone book basic file EF _IAP is linked to the abbreviation dial number basic file EF _ADN . i pen data. After that, whether the user uses the smart card on the original device or other devices, all the contact information related to the specific contact person can be correctly seen when the phone book is opened (for example, the contact phone number in the EF _ADN exists). And the contact email in EF _EMAIL ).

In steps 170 and 180, the present invention may perform the determining step of step 130 or 140 for each piece of data in the index management phone book basic file EF _IAP to establish all the correct information of the valid data of the EF _IAP corresponding to the EF _ADN . Link and update the relevant content of the EF _IAP to the invalid indicator for all the error links of the EF _IAP effective indicator corresponding to the invalid data of the EF _ADN .

In summary, the present invention can update the data of the EF _IAP according to the validity of the corresponding data in the smart card memory index management phone book basic file EF _IAP and the abbreviated dial number basic file EF _ADN . When the user deletes the data of a specific contact, in addition to deleting the related data in the Type 1/Type 2 type basic file, the related information in the index management phone book basic file EF _IAP is also processed. By deleting the wrong link of the EF _IAP effective indicator to the invalid data of the EF _ADN , the smart card can be prevented from displaying a blank contact information after the other device is turned on, thereby improving the correctness and smoothness of the phone book data.

The above are only the preferred embodiments of the present invention, and all changes and modifications made to the scope of the present invention should be within the scope of the present invention.

110~200‧‧‧Steps

Claims (8)

A method for establishing a link between contact information based on data validity of a smart card memory basic file, comprising: installing the smart card to a mobile device; in the booting process of the mobile device, the smart Reading a first data in an elementary file of the card memory; when the content of the first data corresponds to a valid indicator, according to the effective indicator in a second basic file of the smart card memory Reading a corresponding second data; 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 indicator, wherein: the first basic file includes at least An indicator for linking 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 one of the contact first contact information; and the third The basic file is used to store one of the contact's second contact information. The method of claim 1, further comprising: when the content of the second data corresponds to a valid data, reading the corresponding third data in the third basic file according to the effective indicator; The third data is linked to the second material. The method of claim 1, further comprising: determining, in the booting process, whether the smart card supports the type of the third basic file according to a fourth basic file of the smart card memory. The method of claim 3, wherein the fourth basic file is a phone book reference file basic file defined by a 3rd Generation Partnership Project (3GPP) specification TS 31.102. . The method of claim 1, wherein the first basic file is an index administration phone book basic file defined by a 3GPP specification TS 31.102, and the second basic file is the 3GPP specification One of the basic documents of abbreviated dialing numbers defined in TS 31.102. The method of claim 1, wherein the third basic file is an additional number basic file defined by a 3GPP specification TS 31.102, an email basic file, or a second name input (second) Name entry) Basic file. The method of claim 1, wherein the first basic file and the second basic file are a first type (Type 1) basic file defined by a 3GPP specification TS 31.102, and the third basic file is the same The second type (Type 2) basic file defined by the 3GPP specification TS 31.102. The method of claim 1, wherein each of the first basic files is mapped to each of the corresponding data in the second basic file in a one-to-one manner.