WO2012094867A1

WO2012094867A1 - Method for starting up mobile terminal, mobile terminal and subscriber identity card thereof

Info

Publication number: WO2012094867A1
Application number: PCT/CN2011/075200
Authority: WO
Inventors: 王斌; 陈建国
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-01-13
Filing date: 2011-06-02
Publication date: 2012-07-19
Also published as: CN102082873B; CN102082873A

Abstract

A method for starting up a mobile terminal, a mobile terminal and a subscriber identity card thereof are provided in the present invention. Wherein, the method for starting up a mobile terminal includes: when a mobile terminal is being started up for initiation, loading the record with valid identification of the file in the subscriber identity card according to a pre-stored mapping relation of the file record; wherein, said file is the one needing to be loaded when initiating the mobile terminal, and the mapping relation of the file record, which is bound with the subscriber identity card, is used for indicating each file and its contained record in the user identity card and for indicating whether each record is valid. By the present invention, unnecessary system overhead is saved, the speed of starting up a mobile terminal is increased, and the performance of the mobile terminal is improved, thus enhancing the effect of using experience of a subscriber.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to the field of communications, and in particular to a booting method, a mobile terminal, and a user identification card. BACKGROUND OF THE INVENTION With the rapid development and popularization of mobile communication technologies, mobile terminals satisfy the basic communication needs of users, and the user body-risk of mobile terminal users when using mobile terminals has increasingly become the focus of attention. A better user experience makes it easier for users to use mobile terminals and improve the competitiveness of mobile terminal products. During the boot process, the mobile terminal needs to complete the necessary initialization operations before using the mobile terminal for normal services. For a mobile terminal such as a mobile phone with a separate card, the boot initialization process includes a mobile terminal reading a phone book, a short message, and a key parameter of a user identification card such as a SIM card or a UIM card. At present, when a mobile terminal loads a short message or a phone book, it usually traverses the phone book and the short message on the user identification card. This has a certain relationship with the specification of the SIM card or UIM card. The files on the card only have a file header indicating the file size, the single record size, and the entire file size, so that the mobile terminal can calculate the record that the file can store. The total number. However, the user identification card belongs to the peripheral device, and the access speed is relatively slow. The mobile terminal is initialized, traversing the entire file, and the entire indexing process according to the index number from small to large causes the mobile terminal to start up slowly and reduce the user experience. . Moreover, the performance of different cards is different. A large number of card reading operations will have a large negative impact on the performance of mobile terminals such as mobile phones, and will also cause the mobile terminal to be slow to boot and reduce the user experience. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a booting method, a mobile terminal, and a user identification card, so as to solve the problem that the mobile terminal has a slow booting speed and a low user experience. According to an aspect of the present invention, a booting method is provided, including: when a mobile terminal initializes at a booting time, loading a record in a file in the user identification card as a valid record according to a pre-stored file record mapping relationship; , the file initializes the file to be loaded for the mobile terminal, the file record

1 P44144 The mapping relationship is bound to the user identification card. The file record mapping relationship is used to indicate that the user identifies each file in the card and the records it contains, and whether the records are valid. Preferably, the file record mapping relationship is pre-stored in the mobile terminal or the subscriber identity card. Preferably, the pre-stored file record mapping relationship is a file record mapping relationship table, where the file record mapping relationship table includes a file identification ID, a record identification ID, and a record valid flag bit, a file ID represents a file, and a record ID represents a record. The record valid flag indicates whether the record is valid. One file ID corresponds to one or more recorded IDs, and each recorded ID corresponds to a valid recorded flag. Preferably, the method further comprises: synchronously updating the file record mapping relationship when the user identifies the record update in the card. Preferably, if the file record mapping relationship is pre-stored in the mobile terminal, the method further includes: when the mobile terminal uses the user identification card for the first time, reading all files in the user identification card, establishing a file record mapping relationship, and recording the established file The mapping relationship is bound to the user identification card. Preferably, before the step of loading the record in the file in the user identification card as a valid record according to the pre-stored file record mapping relationship, the method further includes: the mobile terminal comparing the electronic serial number ESN with the user identification card Whether the ESNs of the stored terminals are consistent; if they are inconsistent, read all the files in the user identification card, establish a file record mapping relationship, and bind the established file record mapping relationship with the user identification card; if they are consistent, proceed according to the pre- The stored file record mapping relationship, the step of loading the identifier in the file in the user identification card as a valid record. Preferably, before the step of loading the record in the file in the user identification card as a valid record according to the pre-stored file record mapping relationship, the method further includes: the mobile terminal comparing the electronic serial number ESN with the currently used user Whether the ESNs of the terminals stored in the identification card are consistent; if they are inconsistent, read all the files in the currently used user identification card, establish a file record mapping relationship, and tie the established file record mapping relationship with the currently used user identification card. If the agreement is the same, the mobile terminal compares the unique identification information of the user identification card stored by itself with the unique identification information of the currently used user identification card; if not, reads all the files in the currently used user identification card, Establish a file record mapping relationship of the currently used user identification card, and bind the established file record mapping relationship with the currently used user identification card; if they are consistent, perform loading according to the pre-stored file record mapping relationship, and load the user identification card. The identifier in the file is valid for the record Sudden. Preferably, when the mobile terminal includes multiple card slots and multiple user identification cards are used at the same time, the file record mapping relationship includes a plurality of file record mapping relationships respectively bound to the user identification card; and the mapping relationship is recorded according to the pre-stored file. Before the step of loading the identifier in the file in the user identification card as a valid record, the method further includes: the mobile terminal comparing the electronic serial number ESN of the user with the ESN of the terminal stored in the plurality of user identification cards; if not, Read all the files in the inconsistent user identification card, establish a file record mapping relationship of the inconsistent user identification card, and bind the established file record mapping relationship to the inconsistent user identification card; if they are consistent, then according to the current The file record mapping relationship corresponding to the user identification card used is loaded, and the record in the file in the user identification card is loaded as a valid record. According to another aspect of the present invention, a mobile terminal is provided, including: an initialization module, configured to load an identifier in a file in a user identification card according to a pre-stored file record mapping relationship during boot initialization The file is a file that is loaded by the mobile terminal, and the file record mapping relationship is bound to the user identification card. The file record mapping relationship is used to indicate each file in the user identification card and the record it contains, and A mapping relationship in which each record is valid. Preferably, the pre-stored file record mapping relationship is a file record mapping relationship table, where the file record mapping relationship table includes a file identification ID, a record identification ID, and a record valid flag bit, a file ID represents a file, and a record ID represents a record. The record valid flag indicates whether the record is valid. One file ID corresponds to one or more recorded IDs, and each recorded ID corresponds to a valid recorded flag. According to still another aspect of the present invention, a user identification card is provided, including: a mapping relationship module, configured to provide a file record mapping relationship to a mobile terminal when the mobile terminal is powered on, so that the mobile terminal records the file record Relationship, loading the identifier in the file in the user identification card as a valid record; wherein, the file is a file that needs to be loaded for the mobile terminal to be initialized, the file record mapping relationship is bound to the user identification card, and the file record mapping relationship is used to indicate user identification The mapping between each file in the card and the records it contains, and whether each record is valid. Preferably, the pre-stored file record mapping relationship is a file record mapping relationship table, where the file record mapping relationship table includes a file identification ID, a record identification ID, and a record valid flag bit, a file ID represents a file, and a record ID represents a record. The record valid flag indicates whether the record is valid. One file ID corresponds to one or more recorded IDs, and each recorded ID corresponds to a valid recorded flag. According to the present invention, the pre-set file record mapping relationship is used, and when the mobile terminal is powered on, the valid record in the required file is loaded from the user identification card through the file record mapping relationship, instead of loading all the records, thereby causing the file to be loaded. Invalid records in are no longer loaded at boot time. Through this selective loading, the problem that the mobile terminal has a slow booting speed and a user experience is solved in the prior art, thereby achieving unnecessary system overhead and improving the booting speed of the mobile terminal and the performance of the mobile terminal. Improve the user experience. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a flow chart showing the steps of a booting method according to a first embodiment of the present invention; FIG. 2 is a flow chart showing the steps of a booting method according to a second embodiment of the present invention; FIG. 4 is a schematic diagram of a process of updating a file record mapping relationship table in the embodiment shown in FIG. 2; FIG. 5 is a schematic diagram of a booting process according to the third embodiment of the present invention; FIG. 6 is a flow chart showing the steps of a booting method according to Embodiment 4 of the present invention; FIG. 7 is a flow chart showing the steps of a booting method according to Embodiment 5 of the present invention; A block diagram of a mobile terminal according to a sixth embodiment of the present invention; and FIG. 9 is a structural block diagram of a subscriber identity card according to Embodiment 7 of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. Embodiment 1 Referring to FIG. 1 , a flow chart of steps of a booting method according to Embodiment 1 of the present invention is shown, which includes the following steps: Step 4: S102: The mobile terminal is powered on; Step S104: The mobile terminal pre-stores the file record mapping relationship when the power is initialized, and loads the identifier in the file in the user identification card as a valid record. The file in the user identification card is a file that needs to be loaded by the mobile terminal, and the file record mapping relationship is bound to the user identification card. The file record mapping relationship is used to indicate each file in the user identification card and the records it contains, and each Record whether the mapping is valid. If the mobile terminal is a single-card mobile terminal, that is, only one user identification card is generally used, the file record mapping relationship is bound to the user identification card, and the indication is located in the user identification card, and the mobile terminal needs to be loaded when booting initialization. The validity of the records in the file. If the mobile terminal is a multi-card mobile terminal, such as a mobile terminal using two different user identification cards, there are two different file record mapping relationships corresponding to two different user identification cards, respectively, correspondingly, each file The mapping relationship is associated with the corresponding user identification card, indicating the validity of the record in the file that needs to be loaded when the mobile terminal is initialized in the user identification card. In this embodiment, a data structure of a file record mapping relationship may be established on the user identification card or the mobile terminal, so as to effectively represent the usage of a single record on the user identification card. When the mobile terminal performs initial loading and loading related file records, first loading the file record mapping relationship, and then selectively accessing the records in the user identification card according to the corresponding relationship in the file record mapping relationship, and reading the valid records required for the initialization process. , can be ignored for invalid record files. The file record mapping relationship can be set in the mobile terminal or in the user identification card. The file record mapping relationship can exist in various appropriate manners, such as data tables, files, databases, etc., and can be appropriately set by a person skilled in the art according to actual conditions. In the mobile terminal of this embodiment, in the process of performing initialization during power-on, 40 pairs of record files such as a phone book and a short message on the user identification card are selectively loaded. When the mobile terminal is not initialized with a single record on the user identification card and whether it is valid, the entire file is traversed, and when the short message or the phone book is loaded, all the phone book and the short message on the card are traversed and loaded. Compared, in actual use, when the files on the user identification card are too large, they are not fully loaded, and the capacity of the user identification card is getting larger and larger. This invalid loading and traversal is wasted, which wastes a lot of time, especially mobile. The valuable time of the initialization phase of the terminal is turned on. In this embodiment, by setting the file record mapping relationship, the mobile terminal performs selective loading when loading the user identification card, thereby reducing unnecessary card reading operations and valuable. The initialization time is saved, which speeds up the initialization process of the mobile terminal and improves the user experience and product performance. Embodiment 2 Referring to FIG. 2, a flow chart of steps of a booting method according to Embodiment 2 of the present invention is shown. In this embodiment, the single-card mobile terminal first uses the user identification card to establish a file record mapping relationship, and then performs boot initialization loading as an example to explain the booting method of the present invention. The booting method of this embodiment includes the following steps: Step 4: S202: The mobile terminal is powered on. Step S204: The mobile terminal determines that the current subscriber identity card is the subscriber identity card used by the mobile terminal for the first time. In actual use, the mobile terminal needs to first determine whether the currently used user identification card is the user identification card used by the terminal for the first time, and then determine whether a file record mapping relationship needs to be established. In this embodiment, it is determined as the first use as an example. The following is an example of a mobile phone with a CDMA card separated as an example. The implementation principle of determining whether a subscriber identity card is used for a mobile terminal for the first time is described. Of course, the embodiment can also be applied to mobile terminals of other standards. In actual use, the field The technical staff can also use other methods to realize whether the user identification card is used for a certain mobile terminal for the first time. The present invention does not limit this. How to judge whether a user identification card is used by a mobile terminal for the first time, or the implementation process of the mobile terminal using a different user identification card is as follows: During the startup process of the mobile terminal, the mobile terminal will ^¹ ESN (Electronic Serial Number) / PESN (Pseudo-Electronic Serial Number) Information is written to the UIM card 6β8 file. This is the standard process for booting the mobile terminal. All CDMA phones must be followed. When judging whether a user identification card is used by a mobile terminal for the first time, or when the mobile terminal uses a different user identification card, the terminal can detect the 6β8 file at the time of booting, and store the ESN/PESN in the file. Compared with the ESN/PESN of the terminal itself, if it is inconsistent, it indicates that the user identification card has been used by another terminal, and the file record mapping relationship on the card needs to be re-established, that is, the process of establishing a mapping relationship is started, and the exhaustive traversal force is carried out. . For some complicated situations, for example, a mobile terminal uses two different user identification cards before and after, that is, the mobile terminal replaces the user identification card during use. At this time, the above method cannot complete the interlock of the mobile terminal and the subscriber identity card. This is because the ESN/PESN of the mobile terminal stored in the subscriber identity card is the same. At this point, you need to tamper with the process in the mobile terminal and add a record user identification card. The process of uniquely identifying information. That is, tampering with the booting process of the mobile terminal, the unique identification information of the user identification card is stored in the mobile terminal, such as the RUIMID, IMSI, ICCCID, etc. of the user identification card, and the mobile terminal can determine whether the same user identification is used before or after. card. The two processes of judging the ESN judgment and the unique identification information of the user identification card are combined, so that two or more user identification cards are used before and after a mobile terminal, that is, the same card when the same mobile terminal replaces different user identification cards. The lock further determines whether the mobile terminal uses the same user identification card twice before and after. As long as it is judged that the user has used a different subscriber identity card, the file mapping relationship stored by the mobile terminal is reconstructed. However, the construction of a mapping relationship is only a primitive file initialization loading process, and does not bring additional system overhead. Step 4: S206: Read all the files in the user identification card, establish a file record mapping relationship, and bind the user identification card. After determining that the user identification card currently used by the mobile terminal is the user identification card used by the mobile terminal for the first time, it is necessary to establish a file record mapping relationship. When a file record mapping relationship is established, all the files in the user identification card need to be read, and the mapping relationship is performed. After the mapping relationship is established, the user identification card is bound. File record mappings can exist in many forms, such as data tables, files, and so on. In this embodiment, the form of the data table is used, that is, the file record mapping relationship table is established. The establishment of the file record mapping relationship table can be implemented by the following two schemes: The first scheme is set to a user identification card such as a SIM card. Customize new files on the user identification card, or ^ ί 'tamper existing files, specifically for storing file record mapping tables. The record index is stored in the mapping relationship table, and whether the record is valid or not is bound to the related header file (ie, the correspondence is established). In this way, when the record header file is loaded, the mapping relationship table is loaded at the same time, and the mobile terminal performs the actual reading of the record according to the mapping relationship table. When the mobile terminal updates the record on the subscriber identity card, the mapping table is modified synchronously. If you want to use this method as a standard, you can specify the modified file, or the format of the custom file. You can force all mobile terminals to support it. When loading the record of the user identification card, you can use the mapping table to move. When the terminal modifies the record on the user identification card, the mapping table on the user identification card is updated synchronously. The implementation of the mapping relation table can be used in many ways, and the consumption is at most a single card reading operation, which has a great performance improvement compared to a large number of invalid readings. It can also be compatible for terminals that are already in use, without modifying any processes, and ignoring this mapping table. The second option is set to the mobile terminal file system. When the mobile terminal uses the user identification card for the first time, it reads all the files on the card and creates a file record mapping table. The mapping table on the mobile terminal is bound to the user identification card used by the user. The binding process is to establish the interlock process between the user identification card and the mobile terminal. After the interlock, the subscriber identity card and the mobile terminal have a corresponding relationship. When the mobile terminal performs the addition, deletion, and update recorded on the subscriber identity card, the content of the mapping relationship table is synchronously modified. The structure of a file record mapping relationship table of the present invention is as shown in FIG. 3. The file record mapping relationship table mainly has three parts: a file ID (identification): an original file ID of a file record mapping relationship table to be created; a record ID (Identification): Name of the record ID, single record identification information; Record valid identification: Record whether the valid identification bit. A file ID indicates a file, a record ID indicates a record, and a record valid flag indicates whether the record is valid. A file ID corresponds to one or more record IDs, and each record ID corresponds to a record valid flag. The update process of the file record mapping relationship table shown in FIG. 3 is as shown in FIG. 4. When the mobile terminal updates the record on the user identification card, including deleting the record, adding the record, and modifying the record, if the corresponding file establishes the file record mapping In the relational table, the file record mapping relationship table of the file is synchronously updated to ensure the correspondence between the file record mapping relationship table and the file record. It should be noted that it is not necessary for all the files in the user identification card to establish a mapping relationship table. According to the number and size of the content recorded by the file, the person skilled in the art can make appropriate trade-offs when the mobile terminal performs the process design. Step S208: The mobile terminal searches for the file record mapping relationship according to the established file, and loads the target i in the file in the user identification card to be only valid. In this embodiment, since the mobile terminal uses the user identification card for the first time, it is necessary to newly create a file record mapping relationship, and load the file according to the newly created mapping relationship. However, if the user identification card is not used for the first time, the file record mapping relationship of the user identification card should already exist in the mobile terminal, so that when the mobile terminal does not use the user identification card for the first time and performs boot initialization, it is not necessary to establish a mapping relationship. , you can directly establish the mapping relationship that has been established before, initialize and load the file. By establishing a data structure of a file record mapping relationship on the user identification card or the mobile terminal, the usage of a single record on the user identification card can be effectively represented, and the mobile terminal first loads the file record when performing initialization loading and loading related file records. The mapping relationship, and then the corresponding relationship, has the option to access the records in the user identification card, read the valid records required for the initialization process, and ignore the invalid records of the file. In this embodiment, by selectively loading the records of the files in the user identification card, unnecessary system overhead is saved, the performance of the mobile terminal is improved, and the user's experience of the booting speed is enhanced. Embodiment 3 Referring to FIG. 5, a flow chart of steps of a booting method according to Embodiment 3 of the present invention is shown. In this embodiment, the single-card mobile terminal and the file record mapping relationship table are stored on the user identification card as an example, and the booting method of the present invention is introduced. At the same time, it should be noted that, in this embodiment, the loading of a single file is taken as an example. The initialization process of a real mobile terminal may have multiple similar iterative processes. The booting method of this embodiment includes: Step 4: S502: The mobile terminal starts up and starts to read a single file in the user identification card. Step S504: The mobile terminal reads the file header information of the single file in the user identification card. Step S506: The mobile terminal detects whether the read file has a file record mapping relationship table. If not, step S508 is performed; if yes, step S514 is performed. Step S508: If there is no mapping relation table of the file, all the records corresponding to the file are overwritten by an exhaustive method. Step S510: determining whether it is necessary to establish a file record mapping relationship table of the file, if yes, executing step 4 S512; if not, executing step 4 S518; step S512: if necessary, establishing a file record mapping relationship of the file Table, complete the loading of the file, perform step 4 to gather S518. Step S514: If the mapping relationship table of the file is stored, the mapping relationship table of the file is read. Step S516, the mapping relationship table of the file has a selected loading file record. Step S518: Finish loading of the file. Embodiment 4 Referring to FIG. 6, a flow chart of steps of a booting method according to Embodiment 4 of the present invention is shown. In this embodiment, a single-card mobile terminal uses a replacement subscriber identification card, and a file record mapping relationship table is stored on the mobile terminal as an example to introduce the booting method of the present invention. At the same time, it should be noted that, in this embodiment, the loading of a single file is taken as an example. The initialization process of a real mobile terminal may have multiple similar iterative processes. The booting method of this embodiment includes: Step 4: S602: The mobile terminal starts up initially. Step S604: The mobile terminal writes the unique identification information ESN (PESN) into the UIM card, and determines whether the unique identification information of the mobile terminal stored in the UIM card is consistent with the written one. If not, the first identification bit is set. The first identifier is used to identify whether the mobile terminal is consistent with the ESN stored in the subscriber identity card. Step S606: The mobile terminal reads the unique identification information (such as UIMID, IMSI, or ICCCID) of the UIM card of the user identification card, and determines whether the read unique identification information is consistent with the unique identification information stored by the mobile terminal. Two identification bits. The second identifier is used to identify whether the unique identification information stored by the mobile terminal and the current subscriber identity card is consistent. The first identifier bit and the second flag bit may be set separately or in combination. When the settings are merged, if they are inconsistent, set the flag to 1 and if they match, set the flag to 0. In this case, if the ESN is inconsistent, the flag is set to 1. At this time, regardless of whether the unique identification information of the user identification card is consistent, once the flag is set to 1, the tampering is not performed until the end of the process. , to indicate that the file record mapping needs to be rebuilt. If the ESN is the same, the flag is 0. When the unique identification information of the user identification card is inconsistent, the flag is set to 1. When the unique identification information of the user identification card is consistent, the flag is still 0. Step S608: Load the file header information corresponding to the single file in the UIM card of the user identification card. Step 4: S610: The first and second identification bits are read, and it is determined whether the current startup is the same user identification card as that used in the previous startup. If not, step S612 is performed; if yes, step S616 is performed. Step S612: If not the same user identification card, use the exhaustive method to read all the records corresponding to the file. Step S614: Determine whether it is necessary to construct a file record mapping relationship table of the file, and reconstruct the mapping relationship table of the file if necessary, otherwise skip the mapping relationship table for constructing the file, and complete initialization of the file. Step S616: If it is the same user identification card, determine whether the file has a corresponding mapping relationship table, if there is a corresponding mapping relationship table, read the mapping relationship table, and select the selected user according to the mapping relationship table. Identify the record on the card, perform the actual card reading operation; if there is no corresponding mapping relationship table, use the exhaustive method to read all the records corresponding to the file, and determine whether it is necessary to construct the mapping relationship table of the file, if necessary Then reconstruct the file record mapping relationship table of the file, otherwise skip the build file record mapping relationship table. Step 4: S618: Complete the file loading of the file. Embodiment 5 Referring to FIG. 7, a flow chart of steps of a booting method according to Embodiment 5 of the present invention is shown. In this embodiment, the dual-card mobile terminal and the file record mapping relationship table are stored on the user identification card as an example, and the booting method of the present invention is introduced. In this embodiment, although only a dual-card mobile terminal including at least two card slots and two user identification cards is used as an example, a person skilled in the art may refer to this when using a multi-card mobile terminal with more than two cards. The embodiment implements the booting method of the present invention. At the same time, it should be noted that, in this embodiment, the loading of a single file is taken as an example. The initialization process of a real mobile terminal may have multiple similar iterative processes. The booting method of this embodiment includes: Step 4: S702: The mobile terminal is powered on initially. Step S704: The mobile terminal writes the ESN (PESN) into the two user identification cards, and determines whether the ESN (PESN) of the mobile terminal stored in the two user identification cards is consistent with the written one. If not, the identifier is set. Bit. The flag bits can be set separately or uniformly. When set separately, one identification bit corresponds to one user identification card; when setting uniformly, different bits can be used to indicate different meanings, such as "01" indicating the ESN (PESN) and movement of the mobile terminal stored in the user identification card A Inconsistent write of the terminal, "10" indicates that the ESN (PESN) of the mobile terminal stored in the subscriber identity card B is inconsistent with the write of the mobile terminal, and "11" indicates the ESN of the mobile terminal stored in the subscriber identity cards A and B ( PESN) is inconsistent with the writing of the mobile terminal, and "00" indicates the mobile terminal stored in the user identification cards A and B. The ESN (PESN) is consistent with the write of the mobile terminal, and the like, and can be appropriately set by the person skilled in the art according to the actual situation, which is not limited by the present invention. In this embodiment, the ESN (PESN) of the mobile terminal stored in the two subscriber identity cards is consistent with the write. Step S706: The mobile terminal separately loads file header information corresponding to a single file in the two user identification cards. The two user identification cards are respectively set as the user identification card A and the user identification card B. In this step, the mobile terminal loads the file header information of the single file in the user identification card A and the single file in the user identification card B. File header information. Step S708: The identifier bit is read to determine whether the current booting is the same user identification card as that used in the previous booting. If no, step S710 is performed; if yes, step S714 is performed. In this step, the result of the judgment may be that the two user identification cards are different from the one used in the previous power-on, or one of them may be the same and the other one is different. If the latter is used, step S710 may be performed on both cards. Alternatively, step M1 S710 may be performed only for the different cards, and step 4 S714 may be performed for the same card. Step S710: Read all the records corresponding to the loaded file by an exhaustive method. Step S712: Determine whether it is necessary to construct a file record mapping relationship table of the file, and reconstruct the mapping relationship table of the file if necessary, otherwise skip the mapping relationship table for constructing the file, and complete initialization of the file. Step S714: determining whether the file has a corresponding mapping relationship table, if there is a corresponding mapping relationship table, reading the mapping relationship table, and selectively reading the record on the user identification card according to the mapping relationship table, performing actual Card reading operation; if there is no corresponding mapping relationship table, then exhaustively read all the records corresponding to the file, and determine whether it is necessary to construct a mapping relationship table of the file, and reconstruct the file record of the file if necessary Map the relational table, otherwise skip the build file record mapping table. Step S716: Completing the record loading of the file. It should be noted that, in this embodiment, the order of boot initialization loading is not differentiated. In the case that the boot initial 4 loading has a sequence, the worker i or the technician can implement the booting method of the present invention by referring to the above multiple embodiments. . In this embodiment, the multi-card mobile terminal loads the file in the user identification card according to the file record mapping relationship corresponding to the currently used user identification card during the boot initialization process. Regardless of how many user identification cards are used by the mobile terminal, the quick start initialization force port can be performed according to the corresponding file record mapping relationship. Embodiment 6 Referring to FIG. 8, a structural block diagram of a mobile terminal according to Embodiment 6 of the present invention is shown, including: an initialization module 802, configured to pre-store a file record mapping relationship when the mobile terminal is powered on and initialized. Loading the identifier in the file in the user identification card as a valid record; wherein the file is a file that needs to be loaded by the mobile terminal, and the file record mapping relationship is bound to the user identification card, and the file record mapping relationship is used to indicate user identification. The mapping between each file in the card and the records it contains, and whether each record is valid. Preferably, the pre-stored file record mapping relationship is a file record mapping relationship table, and the file record mapping relationship table includes a file ID, a record ID, and a record valid flag bit, a file ID represents a file, and a record ID represents a record, and the record is valid. The flag bit indicates whether the record is valid, one file ID corresponds to one or more record IDs, and each record ID corresponds to one record valid flag bit. Preferably, the mobile terminal of this embodiment further includes: an updating module, configured to synchronously update the file record mapping relationship when the user identifies the record update in the card. Preferably, the mobile terminal of this embodiment further includes: an establishing module, configured to: if the file record mapping relationship is pre-stored in the mobile terminal, when the mobile terminal uses the user identification card for the first time, read all files in the user identification card, and create a file. Record the mapping relationship and bind the established file record mapping relationship with the user identification card. Preferably, the mobile terminal of this embodiment further includes: a first determining module, configured to: before the initialization module 802, according to the pre-stored file record mapping relationship, before loading the identifier in the file in the user identification card as a valid record, Comparing the ESN of the mobile terminal itself with the ESN of the terminal stored in the user identification card; if not, reading all the files in the user identification card, establishing a file record mapping relationship, and establishing the file record mapping relationship and user identification Card binding; if consistent, it is pre- The file record mapping relationship stored first, and the identifier in the file loaded in the user identification card is a valid record. Preferably, the first determining module is further configured to: pre-store the file record mapping relationship in the initialization module 802, and compare the electronic serial number ESN with the current use before loading the identifier in the file in the user identification card as a valid record. Whether the ESNs of the terminals stored in the user identification card are consistent; if they are inconsistent, read all the files in the currently used user identification card, establish a file record mapping relationship, and establish the file record mapping relationship with the currently used user identification. Card binding; if they are consistent, compare whether the unique identification information of the user identification card stored by itself is consistent with the unique identification information of the currently used user identification card; if not, read all the files in the currently used user identification card, Establishing a file record mapping relationship of the currently used user identification card, and binding the established file record mapping relationship with the currently used user identification card; if they are consistent, loading the user identification card according to the pre-stored file record mapping relationship The identifier in the file is a valid record. Preferably, when the mobile terminal of the embodiment includes multiple card slots and multiple user identification cards are used at the same time, the file record mapping relationship includes a plurality of file record mapping relationships respectively bound to the user identification card; The mobile terminal of the example further includes: a second determining module, configured to compare the ESN of the mobile terminal itself before the initialization module 802 records the mapping relationship in the file in the user identification card according to the pre-stored file record mapping relationship Whether the ESNs of the terminals stored in the multiple user identification cards are consistent; if they are inconsistent, all the files in the inconsistent user identification card are read, the file record mapping relationship of the inconsistent user identification card is established, and the established file record mapping relationship is established. Binding to the inconsistent user identification card; if they are consistent, the identifier in the file in the user identification card is loaded as valid according to the file record mapping relationship corresponding to the currently used user identification card. Embodiment 7 Referring to FIG. 9, a block diagram of a user identification card according to Embodiment 7 of the present invention is shown, including: a mapping relationship module 902, configured to provide a file record to a mobile terminal when the mobile terminal is powered on and initialized. Mapping the relationship, so that the mobile terminal loads the identifier in the file in the user identification card as a valid record according to the file record mapping relationship; wherein the file is a file that needs to be loaded for the mobile terminal to initialize, and the file record mapping relationship and the user Identification card binding, the file record mapping relationship is used to indicate that the user identifies each file in the card and the records it contains, and whether the records are valid. Preferably, the pre-stored file record mapping relationship is a file record mapping relationship table, and the file record mapping relationship table includes a file ID, a record ID, and a record valid flag bit, and a file ID indicates a A file, a record ID indicates a record, and a record valid flag indicates whether the record is valid. A file ID corresponds to one or more record IDs, and each record ID corresponds to a record valid flag. Preferably, the user identification card of this embodiment further includes: an update module, configured to synchronously update the file record mapping relationship when the record in the user identification card is updated. User identification cards include, but are not limited to, UIM cards for CDMA systems, SIM cards for GSM systems, PIM for PHS, USIM cards for WCDMA, and 3G cards for TD-SCDMA systems. From the above description, it can be seen that the present invention provides a technical solution for accelerating the optimization of the booting speed of the mobile terminal. By setting the file record mapping relationship of the file to be loaded by the mobile terminal to initialize the booting, the time for starting the initialization of the mobile terminal is reduced. , bringing a better user experience and improving the competitiveness of mobile terminals. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

1. A boot method, including:

When the mobile terminal initializes, it pre-stores the file record mapping relationship, and loads the identifier in the file in the user identification card as a valid record;

The file is a file to be loaded by the mobile terminal, and the file record mapping relationship is bound to the user identification card, where the file record mapping relationship is used to indicate each file in the user identification card and The records included, and the mapping relationship between each of the records.

The method according to claim 1, wherein the file record mapping relationship is pre-stored in the mobile terminal or the user identification card.

The method according to claim 1, wherein the pre-stored file record mapping relationship is a file record mapping relationship table, and the file record mapping relationship table includes a file identification ID, a record identification ID, and a record valid flag bit. One of the file IDs represents a file, one of the record IDs represents a record, the record valid flag bit indicates whether the record is valid, the one file ID corresponds to one or more record IDs, and each record ID corresponds to one record. Valid flag.

4. The method according to claim 1, 2 or 3, wherein the method further comprises:

When the record in the subscriber identity card is updated, the file record mapping relationship is updated synchronously.

The method according to claim 2, wherein, if the file record mapping relationship is pre-stored in the mobile terminal, the method further includes:

When the mobile terminal uses the user identification card for the first time, it reads all the files in the user identification card, establishes the file record mapping relationship, and binds the established file record mapping relationship to the user identification card. set.

The method of claim 1, wherein the pre-stored file record mapping relationship, before the step of loading the identifier in the file in the user identification card is a valid record, further includes: Whether the mobile terminal compares its own electronic serial number ESN with the ESN of the terminal stored in the user identification card;

If they are inconsistent, read all the files in the user identification card, establish the file record mapping relationship, and bind the established file record mapping relationship with the user identification card; The step of loading the identifier in the file in the user identification card as a valid record according to the pre-stored file record mapping relationship. The method according to claim 1, wherein before the step of recording the mapping relationship of the pre-stored file and loading the identifier in the file in the user identification card as a valid record, the method further comprises:

Whether the mobile terminal compares its own electronic serial number ESN with the ESN of the terminal stored in the currently used user identification card;

If not, read all the files in the currently used user identification card, establish the file record mapping relationship, and bind the established file record mapping relationship with the currently used user identification card;

If they are consistent, the mobile terminal compares the unique identification information of the user identification card stored by itself with the unique identification information of the currently used user identification card; if not, reads the currently used user identification card. All the files, the file record mapping relationship of the currently used user identification card is established, and the established file record mapping relationship is bound to the currently used user identification card; if they are consistent, the pre-existing The stored file record mapping relationship, the step of loading the identifier in the file in the user identification card as a valid record. According to the method of claim 1, wherein when the mobile terminal includes a plurality of card slots and a plurality of user identification cards are used at the same time, the file record mapping relationship includes a plurality of respectively associated with the user identification card. Fixed file record mapping relationship;

Before the step of loading the identifier in the file in the user identification card into a valid record according to the pre-stored file record mapping relationship, the method further includes:

Whether the mobile terminal compares its own electronic serial number ESN with the ESN of the terminal stored in the plurality of user identification cards;

If they are inconsistent, read all the files in the inconsistent user identification card, establish a file record mapping relationship of the inconsistent user identification card, and establish the file record mapping relationship with the inconsistent user identification card. Corresponding binding If they are consistent, the record in the file in the user identification card is loaded as valid according to the file record mapping relationship corresponding to the currently used user identification card.

9. A mobile terminal, comprising:

The initialization module is configured to record a mapping relationship in a pre-stored file during boot initialization, and load the identifier in the file in the user identification card as a valid record;

The mobile terminal of claim 9, wherein the pre-stored file record mapping relationship is a file record mapping relationship table, and the file record mapping relationship table includes a file identification ID, a record identification ID, and a record valid flag bit. And a file ID represents a file, and the record ID represents a record, the record valid flag indicates whether the record is valid, and the file ID corresponds to one or more record IDs, and each record ID corresponds to one Record the valid flag.

11. A user identification card, including:

a mapping relationship module, configured to provide a file record mapping relationship to the mobile terminal when the mobile terminal is powered on, so that the mobile terminal loads the identifier in the file in the user identification card according to the file record mapping relationship. record of;

12. The user identification card according to claim 11, wherein the pre-stored file record mapping relationship is a file record mapping relationship table, and the file record mapping relationship table includes a file identification ID, a record identification ID, and a record valid flag. Bit, one of the file IDs represents a file, one of the record IDs represents a record, the record valid flag bit indicates whether the record is valid, and the one file ID corresponds to one or more record IDs, and each record ID corresponds to A record valid flag.