CN100461800C - Method for maintaining telephone book entry information and content conformity - Google Patents
Method for maintaining telephone book entry information and content conformity Download PDFInfo
- Publication number
- CN100461800C CN100461800C CNB2006100782409A CN200610078240A CN100461800C CN 100461800 C CN100461800 C CN 100461800C CN B2006100782409 A CNB2006100782409 A CN B2006100782409A CN 200610078240 A CN200610078240 A CN 200610078240A CN 100461800 C CN100461800 C CN 100461800C
- Authority
- CN
- China
- Prior art keywords
- entries
- telephone directory
- content
- telephone
- phone book
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Telephone Function (AREA)
Abstract
The method comprises: according to the type of update operation for the GSM phone book in UICC, the terminal executes a relevant phone book update instruction, and makes update operation for the GSM phone book; the terminal decides if an operation for deleting the item of phone book has been executed in the update process; if yes, makes the content consistency maintenance operation for the phone book items.
Description
Technical field
The present invention relates to the 3G technology field, be meant a kind of method of maintaining telephone book entry information and content conformity especially.
Background technology
Can store three kinds of telephone directories among the UICC of portable terminal (UICC, Universal IC Cards, Universal Integrated Circuit Card), these telephone directories are stored in respectively under the catalogues different among the UICC.
First kind of telephone directory is kept at the DF of UICC
TELECOMUnder the catalogue, terminal is used down at GSM (GSM, global mobile communication) and (is referred to the terminal support and selected the DF of UICC
TELECOMCatalogue) can only visit this telephone directory, hereinafter to be referred as " GSM telephone directory ".
Second kind of telephone directory is kept at the DF of UICC
TELECOMDF
PHONEBOOKUnder the catalogue, terminal is used down at USIM (USIM, general Removable User Identity Module) and (is referred to the terminal support and selected the ADF of UICC
USIMCatalogue), no matter select which USIM to use, all can visit this telephone directory, hereinafter to be referred as " USIM universal telephone book ".
The third telephone directory is kept at certain ADF of UICC
USIMDF
PHONEBOOKUnder the catalogue, terminal has only and selects this USIM to use, and just can visit this telephone directory, hereinafter to be referred as " USIM telephone for special use book ".Above-mentioned " USIM universal telephone book " and " USIM telephone for special use book " can be referred to as " USIM telephone directory ".
Every kind of telephone directory all is made up of one group of telephone directory file, wherein, and the EF in every group of telephone directory file
ADNThe essential information of each entries of phone book (entries of phone book that refers to each user) in store this telephone directory of file.Show EF as following table 1
ADNThe essential information that file comprised, comprise: be used to fill in the entries of phone book main body of Name or Designation sign (Alpha Identifier) field, be used to length field of filling in telephone number and supplementary service control word etc., specifically see table the content shown in 1, wherein Alpha Identifier is the keyword in this essential information.
| Byte location | Title-note | M/O | |
|
| 1 to X | The sign of Alpha Identifier-entries of phone book main body | O | X | |
| X+1 | The length of Length of BCD number/SSC contents-telephone number and supplementary service control word | M | 1 | |
| X+2 | The TON and NPI-type of number | M | 1 | |
| X+3 to X+12 | Dialling Number/SSC String-telephone number | M | 10 | |
| X+13 | Capability/Configurationl Identifier-EF CCP1Record identification is illustrated in EF CCP1Whether preserve and corresponding ability of this entries of phone book and configuration information in certain record in the file | M | 1 | |
| X+14 | Extensionl Record Identifier-EF
EXT1Record identification represents to also have in this entries of phone book number information to be kept at EF
EXT1In certain record of | M | 1 |
Table 1
Out of Memory is kept in other file of this group telephone directory file (EF for example in the entries of phone book
EMAILFile is preserved the addresses of items of mail information of entries of phone book, and for example, and EF
ANRFile is preserved other numbers or the supplementary service control string of entries of phone book), these information depend on EF
ADNEssential information in the file and coming into force, and and EF
ADNIn information constitute complete entries of phone book together, if EF
ADNIn the information of essential information of certain entries of phone book deleted, then the information of this entries of phone book that writes down in other file in this group telephone directory file has also just lost the meaning that exists.
For make terminal under USIM uses with the entries of phone book of certain main body of visit under GSM uses in identical information the time content that obtains identical, UICC has set up mapping relations (below will be called for short " mapping telephone directory " with USIM universal telephone book/USIM telephone for special use book that " GSM telephone directory " have mapping relations) between the file of " GSM telephone directory " and " USIM universal telephone book/USIM telephone for special use book " corresponding file, be about to EF
ADNFile, EF
EXT1The file that file is shared as GSM telephone directory and mapping telephone directory, between relation specifically as shown in Figure 1.EF wherein
EXT1Theing contents are as follows shown in the table 2 in the file.
| Title | Note |
| Record type | The type of growth data: Called Party Subaddress or Additional data |
| Extension data | The number growth data of certain entries of phone book |
| Identifier | If the number growth data can not all be preserved, then point to the sign of next record in this record |
Table 2
Only comprise entries of phone book in " GSM telephone directory " and be kept at EF
ADNFile and EF
EXT1File (EF
EXT1The information that file comprises: for an entries of phone book, when the length of telephone number and supplementary service number surpasses 20 numerals---i.e. 10 bytes, though perhaps the length of telephone number and supplementary service number is no more than 20 numerals, but need under the situation of additional some public number, the remaining digit that exceeds maximum length just is kept at EF
EXT1In the record of file, EF
ADNThe equal corresponding entries of phone book of indication meaningful EF that is kept at whether in each record of file
EXT1File) information in, " mapping telephone directory " is kept at EF except comprising
ADN(Fig. 1 represents with AND) file and EF
EXT1Outside the information in (Fig. 1 represents with EXT1) file, also comprise the information that is kept in the alternative document, these files comprise: be used for realizing EF that phone directory is controlled
PBC(Fig. 1 represents with PBC) file, be used for the EF of recorded electronic addresses of items of mail
EMAIL(Fig. 1 represents with EMAIL) file, be used for writing down the EF of addition number
ANR(Fig. 1 represents with ANR) file, be used for writing down the EF of second name
SNE(Fig. 1 represents with SNE) file, be used for writing down uniquely identified EF
UID(Fig. 1 represents with UID) file, be used for the EF of recording user group
GRP(Fig. 1 represents with GRP) file, be used for the EF of record group information initial character
GAS(Fig. 1 represents with GAS) file, be used for writing down the EF of addition number initial character
AAS(Fig. 1 represents with AAS) files etc. specifically can describe in detail referring to 3G TS34.108 herein no longer one by one.Terminal can only be visited under GSM uses and be upgraded in the entries of phone book EF that is kept at " GSM telephone directory "
ADNAnd EF
EXT1Information in the file, and can not visit and renewal is kept at the EF of " mapping telephone directory "
EMAIL, EF
ANRWait the information in other file.
When terminal is upgraded the content of certain entries of phone book under GSM uses, for example, revise the telephone number (main body that is entries of phone book is constant) of original user's first in the telephone directory, or the entries of phone book that uses user's second is replaced the entries of phone book (being that former main body is replaced by new main body) of original user's first in the telephone directory, or delete the entries of phone book (being that former main body is deleted) of original user's first, then this entries of phone book is kept at " mapping telephone directory " interior EF
ADNAnd EF
EXT1The information content that writes down in other file in addition may still be mated with the keyword (Alpha Identifier) in the essential information, also may no longer mate or no longer valid.
Because when terminal is used " mapping telephone directory " (as under the situation of having selected USIM to use), can visit all information of entries of phone book, the harmful effect that brings for fear of the unmatched or invalid information content, requirement in the 3GPP standard at present, before using the USIM telephone directory, contain in each entries of phone book in the deletion telephone directory with the unmatched information content of main body or the invalid information content, the process of the unmatched or invalid information content is called maintaining telephone book entry information and content conformity in this deletion entries of phone book.Below maintaining telephone book entry information and content conformity process of the prior art is described:
According to existing 3GPP standard, " USIM universal telephone book " and " USIM telephone for special use book " all comprises an EF among the UICC
PBC(Fig. 1 represents with PBC) file, each record and EF in this document
ADNThe essential information of each entries of phone book in the file is corresponding one by one, and EF
PBCWhether the entries of phone book of B1 bit (hereinafter to be referred as B1) the mark correspondence of first byte of each record was upgraded under GSM uses by terminal recently in the file, and B1 is called first mark.B1=1 represents to be updated, and B1=0 represents not upgrade, referring to accompanying drawing 2.
When UICC detect terminal under GSM uses to " GSM telephone directory " in EF
ADNAnd EF
EXT1The record of certain entries of phone book in the file (can comprise that this entries of phone book is at EF
ADNAnd EF
EXT1Any content of corresponding record in the file) when upgrading, UICC is with the EF of " mapping telephone directory "
PBCB1 bit to first byte that should entries of phone book information in the file is set to 1.
In the prior art, when terminal is brought into use " USIM universal telephone book " or " USIM telephone for special use book " (under the situation of having selected the USIM application), terminal is checked the EF under this telephone directory catalogue
PBCIn B1 of each record whether equal 1, if the B1=1 in certain record then carries out the maintaining telephone book entry information and content conformity processing to the information content of the corresponding entries of phone book of this record, implementation comprises:
At first, terminal is with the EF under this telephone directory catalogue
CCIn counter add 1.Because the non-the present invention of this step pays close attention to content, repeats no more later on.
Then, deletion EF
ADNAnd EF
EXT1The content corresponding in other file in addition (promptly delete terminal in the entries of phone book and under GSM uses, can not visit content with updated information) with this entries of phone book;
At last, terminal is with EF
PBCIn the B1 of this record be re-set as 0.
Analyze foregoing, exist following shortcoming:
The user (promptly revises EF by terminal is revised certain entries of phone book in the USIM telephone directory under GSM uses the information content
ADNFile or EF
EXT1In information) time, the actual corresponding main body of this entries of phone book may be constant before and after revising, for example: correct the misspellings of name, or revise someone's number, or add a suffix so that other people's identical with name in the telephone directory entries of phone book is distinguished after giving name.The information content that is kept in " mapping telephone directory " of this entries of phone book that can not visit under GSM uses of terminal is still mated with essential information in this case, belong to the useful information content, the user do not wish these information contents to the information content of this entries of phone book to carry out maintaining telephone book entry information and content conformity deleted when handling.But in the scheme that the consistency maintenance of the existing entries of phone book information content is handled, will handle its maintaining telephone book entry information and content conformity of deleting formula as long as entries of phone book once is updated, and cause in the entries of phone book useful information content to be deleted automatically mistakenly.This will cause losing of user profile, and this has run counter to user's wish, even have to the content in the USIM telephone directory is added deleted information again, bring inconvenience for user's use.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of maintaining telephone book entry information and content conformity method, and the telephone directory of avoiding upgrading the GSM application causes the mistake of USIM phone book information to be deleted.
A kind of method of safeguarding telephone book entry information and content conformity provided by the invention comprises:
A, terminal are carried out corresponding telephone book update instruction according to the renewal action type of user to GSM telephone directory among the UICC, and the GSM telephone directory is upgraded operation;
B, judge that telephone directory upgrades the operation that certain GSM entries of phone book whether occurred deleting in the operating process; If then carry out the maintaining telephone book entry information and content conformity process;
Described maintaining telephone book entry information and content conformity process comprises: the record that is associated with described deleted GSM entries of phone book in other file in the deletion telephone directory beyond the GSM telephone directory file.
Wherein, the described renewal operation types of steps A and corresponding carry out telephone directory upgrade be operating as one of following:
Upgrade operation types and be existing certain entries of phone book in the deletion telephone directory; Corresponding execution telephone directory upgrades and is operating as: with content all is that a string byte of " FF " is updated in the record corresponding with this entries of phone book in the GSM telephone directory file;
Upgrade operation types for revising a certain content in existing certain entries of phone book in the telephone directory; Corresponding execution telephone directory upgrades and is operating as: the result that will revise is updated in the record of the correspondence of this entries of phone book in the GSM telephone directory file;
Upgrade operation types for adding certain entries of phone book; Corresponding execution telephone directory upgrades and is operating as: when the GSM telephone directory had clearance spaces, described entries of phone book content write in the entries of phone book vacant in the GSM telephone directory; When the GSM telephone directory does not have clearance spaces, carry out certain designated telephone book clauses and subclauses of deletion at EF
ADNIn corresponding record, on this basis the content of adding is write in the corresponding record of entries of phone book of the described appointment of GSM telephone directory.
Wherein, described renewal operation types is that described execution is deleted certain designated telephone book clauses and subclauses at EF when adding certain entries of phone book
ADNIn corresponding record, also comprise: delete certain designated telephone book clauses and subclauses place EF
EXT1In corresponding record.
Wherein, the described situation that deletion do not occur of step B comprises: the file that is updated is telephone directory file EF
EXT1Middle content; Or the file that is updated is telephone directory file EF
ADNIn content, and upgrade the process that this record does not appear deleting in operating process.
Wherein, among the step B, described execution maintaining telephone book entry information and content conformity process is carried out by UICC.
Wherein, before the described execution maintaining telephone book entry information and content conformity of the step B process, further comprise: deleted entries of phone book is provided with the once deleted mark of this entries of phone book of expression;
Described execution maintaining telephone book entry information and content conformity process also comprises: when terminal is selected the USIM telephone directory, and when judging the mark with described setting, carry out the pairing maintaining telephone book entry information and content conformity step of described mark; And the mark of the described setting of removing after executing the maintaining telephone book entry information and content conformity step;
The pairing maintaining telephone book entry information and content conformity step of described execution mark is:
Judge first of corresponding current entries of phone book record marks whether to be 1, when judgement first is labeled as 1, judge further then second marks whether to be 1, if second is labeled as 0, then terminal is not carried out the consistency maintenance processing to the information content of corresponding telephone book clauses and subclauses, do not delete the content of corresponding any record, the bit of first mark is changed to 0;
If second is labeled as 1, then EF in the terminal deletion telephone directory
ADNAnd EF
EXT1The content of the record that is associated with this entries of phone book in other file in addition, the bit with first mark and second mark all is set to 0 then.
Wherein, the once deleted mark of this entries of phone book of described expression can be arranged on the EF of mapping telephone directory
PBCIn the file.
Wherein, described USIM telephone directory comprises USIM universal telephone book, USIM telephone for special use book.
Wherein, described GSM telephone directory comprises telephone directory file EF
ADNAnd EF
EXT1The content that is write down.
By said method as can be seen; the present invention can not only be the same with prior art; the information content that guarantees each record in the entries of phone book all is the information content that belongs to current main body after consistency maintenance is handled; safeguarded the consistency and the matching of the information content in the entries of phone book; also overcome the shortcoming that may delete Useful Information content in the entries of phone book mistakenly that exists in the prior art simultaneously; guaranteed that the user does not wish that the information content of deleting can not deleted mistakenly in the entries of phone book; the integrality of the information content in the entries of phone book of safeguarding has been protected user's interests.
Specifically, this programme make UICC can identify the user by terminal under GSM uses to UICC in the renewal of entries of phone book be the information content of only having revised original main body, still deleted former EF
ADNCertain entries of phone book record in the file, judge thus for the entries of phone book that is updated, still whether the related information content that terminal can not be visited under GSM uses coupling or effective, thereby whether decision needs that the information content of the entries of phone book that is updated is carried out consistency maintenance handle, can not delete user in this entries of phone book mistakenly and not wish the information content of deleting.
Description of drawings
Fig. 1 is the schematic diagram that concerns of GSM telephone directory and mapping telephone directory;
Fig. 2 is expression entries of phone book updated bits schematic diagram whether;
Whether Fig. 3 needs to carry out the bit schematic diagram of the consistency maintenance of the information content for the expression entries of phone book;
Fig. 4 carries out for terminal in the consistency maintenance process scheme of the entries of phone book information content, the operational flowchart of UICC;
Fig. 5 carries out for terminal in the consistency maintenance process scheme of the entries of phone book information content, the operational flowchart of the consistency maintenance process that terminal is carried out;
The flow chart of the consistency maintenance process of the entries of phone book information content that Fig. 6 carries out for UICC;
In the consistency maintenance process scheme of the entries of phone book information content that Fig. 7 carries out for UICC, the flow chart of the operating process when terminal is used the mapping telephone directory.
Embodiment
Analyze prior art, when the user upgrades entries of phone book under GSM uses by terminal, UICC only can discern and renewal had once taken place this entries of phone book of mark, but can not identify particularly the renewal of being made revised former main body entries of phone book the information content or deleted former main body, therefore can't judge whether still coupling or effectively of terminal can not be visited in the entries of phone book that is updated related information content under GSM uses.
Below solution of the present invention is described.
The EF of the present invention's definition " mapping telephone directory "
PBCCertain reservation bit Bx in the file in first byte of each entries of phone book corresponding record (x can be 1 integer in 2 to 8, hereinafter to be referred as Bx) is " the consistency maintenance mode bit of the entries of phone book information content ", and Bx is called second mark.After UICC comes the mark terminal under GSM uses " GSM telephone directory " to be upgraded with Bx, whether needing that the information content of this entries of phone book is carried out consistency maintenance handles, for example, Bx=1 represents that need carry out information and content conformity to these clauses and subclauses safeguards processing, Bx=0 do not need to represent that these clauses and subclauses are carried out information and content conformity and safeguards processing, referring to accompanying drawing 3 (is example with x=2).
When terminal under GSM uses, when the arbitrary entries of phone book in " GSM telephone directory " is upgraded operation, identify by UICC and need carry out the entries of phone book that information and content conformity safeguard to be handled, and in " mapping telephone directory " mark, whether promptly determine will be with EF
PBCThe B1 bit and the Bx bit of middle corresponding record are set to 1.When terminal is being used " mapping telephone directory " (as having selected under the situation that USIM uses), by terminal according to EF among the UICC
PBCThe Bx bit decision of described entries of phone book correspondence whether to carry out consistency maintenance and handle the information content of entries of phone book.Carry out referring to the terminal shown in Fig. 4 in the consistency maintenance process scheme of the entries of phone book information content, the operational flowchart of UICC is elaborated to this process below:
Step 401: terminal receives under GSM uses upgrades operation types to " GSM telephone directory ", carries out according to described instruction and upgrades operation.
For example, when renewal is operating as deletion in the telephone directory during existing certain entries of phone book, all be that a string byte of " FF " is updated in the interior record corresponding with this entries of phone book of " GSM telephone directory " file and (comprises EF with content then by some UPDATE RECORD instructions
ADNAnd EF
EXT1In record).
When renewal is operating as when revising in the telephone directory a certain content in existing certain entries of phone book, the result that will revise by some UPDATE RECORD instructions is updated in the content of the corresponding record of this entries of phone book in " GSM telephone directory " file, for example is the EF of this entries of phone book correspondence
ADNOr EF
EXT1In certain content.
When renewal is operating as interpolation, have at telephone directory under the situation of clearance spaces, then add in the entries of phone book vacant in the telephone directory; Do not have at telephone directory under the situation of clearance spaces, then after the user selected one will be replaced entries of phone book from telephone directory, deletion was specified in the entries of phone book that will be replaced and is comprised EF
ADNIn corresponding record at interior record, promptly only the entries of phone book that is replaced of deletion at EF
ADNIn corresponding record, or the entries of phone book that is replaced of deletion is at EF
ADNIn corresponding record and at EF
EXT1In corresponding record (this is because judge in the mapping telephone directory that out of Memory is whether still effectively according to being to judge EF
ADNIn corresponding record whether deleted, so comprise EF as long as deletion is specified in the entries of phone book that will be replaced
ADNIn corresponding record at interior record, can think then that this user-phone book is invalid can be replaced), on this invalid entries of phone book, adding fresh content, when adding fresh content with content update in the content of described entries of phone book corresponding record.
Step 402: will shine upon telephone directory EF
PBCThe B1 bit of middle corresponding record is changed to 1.
Step 403: judge whether occurred deletion action in the renewal process, if then Bx is put 1, otherwise keep existing Bx constant.
Wherein, do not occur the deletion situation comprise following situation:
If the file that is updated is not EF
ADN(refer to revise EF
EXT1Content), the file that is updated is EF
ADNAnd update instruction is for upgrading the content in certain record rather than deleting this record (promptly the content that writes down not being changed to " FF " entirely).
Select the USIM telephone directory when (comprising " the USIM universal telephone book " or certain " USIM telephone for special use book " that use among the UICC) (under the situation of having selected the USIM application) when terminal, terminal is carried out the maintaining telephone book entry information and content conformity process.Carry out referring to the terminal shown in Fig. 5 in the consistency maintenance process scheme of the entries of phone book information content, the operational flowchart of the consistency maintenance process that terminal is carried out may further comprise the steps:
Step 501: terminal is checked the EF under this telephone directory catalogue earlier
PBCIn first record, whether to carry out consistency maintenance with decision and handle this information content that writes down corresponding telephone book clauses and subclauses;
Step 502: judge EF
PBCIn the B1 of corresponding current entries of phone book record whether be 1, if not, whether on inspection then judge all records, if then finish, do not return step 502, judge that whether next entries of phone book is needed to carry out information and content conformity is safeguarded and handle;
If be judged as B1=1, judge further then whether Bx is 1, if Bx=0, then terminal is not carried out the consistency maintenance processing to the information content of corresponding telephone book clauses and subclauses, the content of not deleting corresponding any record is changed to 0 with the B1 bit; Whether on inspection to judge all records then,, otherwise return step 502, judge that whether next entries of phone book is needed to carry out information and content conformity is safeguarded processing if then finish;
If Bx=1, then EF in the terminal deletion telephone directory
ADNAnd EF
EXT1The content of the record that is associated with this entries of phone book in other file in addition all is set to 0 with B1 and Bx bit then;
Whether on inspection to judge all records then,, otherwise return step 502, judge that whether next entries of phone book is needed to carry out information and content conformity is safeguarded processing if then finish.
Top scheme is that asynchronous maintaining telephone book entry information and content conformity is handled, and after promptly the GSM entries of phone book upgraded, terminal was carried out maintaining telephone book entry information and content conformity to " mapping telephone directory " and handled when selecting the USIM telephone directory.Be understood that, also can carry out synchronous maintaining telephone book entry information and content conformity and handle, promptly under GSM uses, upgraded entries of phone book information and just " mapping telephone directory " among the UICC handled, be described below by UICC:
When terminal is upgraded among the UICC " GSM telephone directory " clauses and subclauses under GSM uses, because UICC self can visit and upgrade the file that terminal can not be visited in " mapping telephone directory " under GSM uses, so UICC need carry out the information content of the entries of phone book that is updated directly this entries of phone book other corresponding related information content in " mapping telephone directory " being carried out the consistency maintenance processing after consistency maintenance handles identifying.The flow chart of the consistency maintenance process of the entries of phone book information content of carrying out referring to the UICC shown in Fig. 6 specifically describes as follows:
Step 601～602: identical with step 401～402;
Step 603: judge whether occurred deletion action in the renewal process, if then UICC deletes EF in " mapping telephone directory "
ADNAnd EF
EXT1The content of the record that is associated with this entries of phone book in other file in addition.If not, then finish active procedure.
Wherein, do not occur the deletion situation comprise following situation:
If the file that is updated is not EF
ADN(refer to revise EF
EXT1Content), the file that is updated is EF
ADN, and update instruction is for upgrading the content in certain record rather than deleting this record (promptly the content that writes down not being changed to " FF " entirely).
When terminal is selected USIM telephone directory (for example use among the UICC " USIM universal telephone book " or certain " USIM telephone for special use book " etc.), just no longer need to carry out the maintaining telephone book entry information and content conformity process, in the consistency maintenance process scheme of the entries of phone book information content of carrying out referring to the UICC shown in Fig. 7, the flow chart of the operating process when terminal is used the mapping telephone directory, specifically as following steps:
Step 701: terminal is checked the EF under this telephone directory catalogue earlier
PBCIn first record;
Step 702: judge whether B1 is 1, then returns step 702 if not, checks the EF under this telephone directory catalogue
PBCIn next record;
If B1=1, then terminal is not carried out consistency maintenance to the information content of corresponding telephone book clauses and subclauses and is handled, and does not delete the content of corresponding record, and the B1 bit is set to 0; Return step 702, check the EF under this telephone directory catalogue
PBCIn next record.
For first embodiment above-mentioned, in fact can only analyze Bx provided by the invention gets final product, and needn't be concerned about the value of B1, for example, when Bx is 0, then do not carry out the maintaining telephone book entry information and content conformity process, when Bx was 1 (occurring deletion action in other words), then carry out described maintaining telephone book entry information and content conformity processing procedure, and Bx is reverted to 0.That is to say that whether carrying out maintaining telephone book entry information and content conformity has no longer relied on B1, but rely on the value of Bx, rely in other words deletion action whether to occur.But there are certain relation in Bx and B1, and when Bx equaled 1, B1 also equaled 1 certainly.Because according to the 3GPP standard, B1 also has other effect, as be used for telephone directory synchronously (referring to the 4.4.2 joint of 3GPP TS31.102) between UICC and external equipment, so in above-mentioned two embodiment, do not change function and the associative operation of the B1 that defines in the 3GPP standard.
As seen from the above, the present invention program make UICC can identify the user by terminal under GSM uses to UICC in the renewal of entries of phone book be the information content of only having revised original main body, still deleted original main body, judge whether still coupling or effectively of related information content that terminal in the entries of phone book that is updated can not visit thus under GSM uses, thereby whether decision needs that the information content of the entries of phone book that is updated is carried out consistency handle, can not delete user in this entries of phone book mistakenly and not wish the information content of deleting.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being done, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (9)
1. a method of safeguarding telephone book entry information and content conformity is characterized in that, comprising:
A, terminal are carried out corresponding telephone book update instruction according to the renewal action type of user to GSM telephone directory in the Universal Integrated Circuit Card, and the GSM telephone directory is upgraded operation;
B, judge that telephone directory upgrades the operation that certain GSM entries of phone book whether occurred deleting in the operating process;
If then carry out the maintaining telephone book entry information and content conformity process;
Described maintaining telephone book entry information and content conformity process comprises: the record that is associated with described deleted GSM entries of phone book in other file in the deletion telephone directory beyond the GSM telephone directory file.
2. method according to claim 1 is characterized in that, the described renewal operation types of steps A and corresponding carry out telephone directory upgrade be operating as one of following:
Upgrade operation types and be existing certain entries of phone book in the deletion telephone directory; Corresponding execution telephone directory upgrades and is operating as: with content all is that a string byte of " FF " is updated in the record corresponding with this entries of phone book in the GSM telephone directory file;
Upgrade operation types for revising a certain content in existing certain entries of phone book in the telephone directory; Corresponding execution telephone directory upgrades and is operating as: the result that will revise is updated in the record of the correspondence of this entries of phone book in the GSM telephone directory file;
Upgrade operation types for adding certain entries of phone book; Corresponding execution telephone directory upgrades and is operating as: when the GSM telephone directory had clearance spaces, described entries of phone book content write in the entries of phone book vacant in the GSM telephone directory; When the GSM telephone directory does not have clearance spaces, carry out certain designated telephone book clauses and subclauses of deletion at EF
ADNIn corresponding record, on this basis the content of adding is write in the corresponding record of entries of phone book of the described appointment of GSM telephone directory.
3. method according to claim 2 is characterized in that, described renewal operation types is that described execution is deleted certain designated telephone book clauses and subclauses at EF when adding certain entries of phone book
ADNIn corresponding record, also comprise: delete certain designated telephone book clauses and subclauses place EF
EXT1In corresponding record.
4. according to claim 1,2 or 3 described methods, it is characterized in that the described situation that deletion do not occur of step B comprises:
The file that is updated is telephone directory file EF
EXT1Middle content; Or,
The file that is updated is telephone directory file EF
ADNIn content, and upgrade the process that this record does not appear deleting in operating process.
5. method according to claim 1 is characterized in that, among the step B, described execution maintaining telephone book entry information and content conformity process is carried out by Universal Integrated Circuit Card.
6. method according to claim 1 is characterized in that, before the described execution maintaining telephone book entry information and content conformity of the step B process, further comprises: deleted entries of phone book is provided with the once deleted mark of this entries of phone book of expression;
Described execution maintaining telephone book entry information and content conformity process also comprises: when terminal is selected general Removable User Identity Module telephone directory, and when judging mark, carry out the pairing maintaining telephone book entry information and content conformity step of described mark with described setting; And the mark of the described setting of removing after executing the maintaining telephone book entry information and content conformity step;
The pairing maintaining telephone book entry information and content conformity step of described execution mark is:
Judge first of corresponding current entries of phone book record marks whether to be 1, when judgement first is labeled as 1, judge further then second marks whether to be 1, if second is labeled as 0, then terminal is not carried out the consistency maintenance processing to the information content of corresponding telephone book clauses and subclauses, do not delete the content of corresponding any record, the bit of first mark is changed to 0;
If second is labeled as 1, then EF in the terminal deletion telephone directory
ADNAnd EF
EXT1The content of the record that is associated with this entries of phone book in other file in addition, the bit with first mark and second mark all is set to 0 then.
7. method according to claim 6 is characterized in that, the once deleted mark of this entries of phone book of described expression can be arranged on the EF of mapping telephone directory
PBCIn the file.
8. method according to claim 6 is characterized in that, described general Removable User Identity Module telephone directory comprises general Removable User Identity Module universal telephone book, general Removable User Identity Module telephone for special use book.
9. method according to claim 1 is characterized in that, described GSM telephone directory comprises telephone directory file EF
ADNAnd EF
EXT1The content that is write down.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100782409A CN100461800C (en) | 2006-05-18 | 2006-05-18 | Method for maintaining telephone book entry information and content conformity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100782409A CN100461800C (en) | 2006-05-18 | 2006-05-18 | Method for maintaining telephone book entry information and content conformity |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101076049A CN101076049A (en) | 2007-11-21 |
| CN100461800C true CN100461800C (en) | 2009-02-11 |
Family
ID=38976860
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006100782409A Active CN100461800C (en) | 2006-05-18 | 2006-05-18 | Method for maintaining telephone book entry information and content conformity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100461800C (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101741959B (en) * | 2008-11-10 | 2013-02-13 | 中国联合网络通信集团有限公司 | Method and device for realizing directory service |
| CN101901152A (en) * | 2009-06-01 | 2010-12-01 | 杨良海 | Method for updating contents in batch |
| CN102685304A (en) * | 2011-03-09 | 2012-09-19 | 中兴通讯股份有限公司 | Address book synchronizing method and device |
| US8804554B2 (en) * | 2011-04-28 | 2014-08-12 | Qualcomm Incorporated | Apparatus and method for arbitration of updates provided to a universal integrated circuit card |
| CN103369512B (en) * | 2012-03-29 | 2018-05-22 | 深圳富泰宏精密工业有限公司 | Phone book management method |
| CN105095201B (en) * | 2014-04-17 | 2019-11-26 | 阿尔派株式会社 | Electronic equipment and information processing method |
| CN106231591B (en) * | 2015-06-02 | 2019-08-30 | 宏碁股份有限公司 | The method that network individual is carried out to mobile device |
| CN108882185B (en) * | 2017-05-11 | 2021-04-23 | 展讯通信（上海）有限公司 | Configuration method and device of supplementary service and mobile terminal |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2004114640A1 (en) * | 2003-06-20 | 2004-12-29 | Thomson Licensing | Terminal and server for the synchronisation of contact data |
| CN1602100A (en) * | 2004-10-21 | 2005-03-30 | 康健 | Method of backup of cell phone note based on STK or UTK tech |
-
2006
- 2006-05-18 CN CNB2006100782409A patent/CN100461800C/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2004114640A1 (en) * | 2003-06-20 | 2004-12-29 | Thomson Licensing | Terminal and server for the synchronisation of contact data |
| CN1602100A (en) * | 2004-10-21 | 2005-03-30 | 康健 | Method of backup of cell phone note based on STK or UTK tech |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101076049A (en) | 2007-11-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100461800C (en) | Method for maintaining telephone book entry information and content conformity | |
| KR100287137B1 (en) | Method for managing version of portable information terminal | |
| KR100735341B1 (en) | Apparatus and method for improving speed of data reading from subscriber identity module | |
| KR100787861B1 (en) | Apparatus and method for verifying update data in portable communication system | |
| US20110167093A1 (en) | Address list system and implementation method thereof | |
| KR20060041737A (en) | Cross-pollination of multiple sync sources | |
| CN101651730B (en) | Method for quickly reading entries of phone book | |
| CN101763418A (en) | File resource access method and device | |
| US20020169004A1 (en) | Method of managing data stored in the memory of an SIM card of a mobile equipment | |
| US20070260638A1 (en) | Commands for the handling of large files | |
| CN102082873A (en) | Starting method, mobile terminal and user identification card | |
| KR101066384B1 (en) | Communication terminal device, access controlling method, and smart card | |
| CN101593175A (en) | Communication information system and contact person's thereof correlating method | |
| CN101827140A (en) | Method for writing data in user identification module card and mobile terminal | |
| KR102037556B1 (en) | Method and device for upgrading telephone number in wireless terminal self-adaptive network upgrade | |
| CN116150093A (en) | Method for realizing object storage enumeration of objects and electronic equipment | |
| CN101932133B (en) | Short message storage method and wireless communication terminal | |
| US20040249797A1 (en) | Background data storage | |
| US7788298B2 (en) | Method and mobile terminal for efficient file list creation | |
| US20090093271A1 (en) | Access To Contact Connectors Of A Mobile Terminal From Another Mobile Terminal | |
| KR101104700B1 (en) | Method for synchronizing the address book of mobile terminal | |
| TWI539786B (en) | Method of establishing links between contact information according to data validity of elementary files stored in smartcard | |
| KR100875742B1 (en) | Method for processing phone-book data of universal integrated circuit card and mobile terminal thereof | |
| GB2452534A (en) | Database updates in mobile radio communications device stored in a removable memory device | |
| TWI558157B (en) | Method of accessing contact features in smartcard |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: LIANXIN SCIENCE CO., LTD. Free format text: FORMER OWNER: DATANG MOBILE COMMUNICATION APPARATUS CO., LTD. Effective date: 20090508 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20090508 Address after: 41, No. 4, No. 333, No. 333, chin Jiang Road, zip code: 200233 Co-patentee after: Datang Mobile Communication Equipment Co., Ltd. Patentee after: Lian core technology Co., Ltd. Co-patentee after: Datang Mobile Communication Equipment Co., Ltd., Shanghai Address before: Beijing, Xueyuan Road, Haidian District No. 29: 100083 Co-patentee before: Datang Mobile Communication Equipment Co., Ltd., Shanghai Patentee before: Datang Mobile Communications Equipment Co |
|
| C56 | Change in the name or address of the patentee | ||
| CP02 | Change in the address of a patent holder |
Address after: 201206 Pudong New Area Mingyue Road, Shanghai, No. 1258 Co-patentee after: Datang Mobile Communication Equipment Co., Ltd. Patentee after: Leadcore Technology Co., Ltd. Co-patentee after: Datang Mobile Communication Equipment Co., Ltd., Shanghai Address before: 200233 Shanghai, Jiang Road, No. 41, building 4, building 333 Co-patentee before: Datang Mobile Communication Equipment Co., Ltd. Patentee before: Leadcore Technology Co., Ltd. Co-patentee before: Datang Mobile Communication Equipment Co., Ltd., Shanghai |
|
| ASS | Succession or assignment of patent right |
Free format text: FORMER OWNER: DATANG MOBILE COMMUNICATION EQUIPMENT CO., LTD. DATANG MOBILE COMMUNICATION EQUIPMENT CO., LTD., SHANGHAI Effective date: 20120129 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20120129 Address after: 201206 Pudong New Area Mingyue Road, Shanghai, No. 1258 Patentee after: Leadcore Technology Co., Ltd. Address before: 201206 Pudong New Area Mingyue Road, Shanghai, No. 1258 Co-patentee before: Datang Mobile Communication Equipment Co., Ltd. Patentee before: Leadcore Technology Co., Ltd. Co-patentee before: Datang Mobile Communication Equipment Co., Ltd., Shanghai |
|
| EE01 | Entry into force of recordation of patent licensing contract | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20071121 Assignee: Shanghai Li Ke Semiconductor Technology Co., Ltd. Assignor: Leadcore Technology Co., Ltd. Contract record no.: 2018990000159 Denomination of invention: Method for maintaining telephone book entry information and content conformity Granted publication date: 20090211 License type: Common License Record date: 20180615 |