WO2016145896A1 - 一种联系人信息管理方法及装置、终端 - Google Patents

一种联系人信息管理方法及装置、终端 Download PDF

Info

Publication number
WO2016145896A1
WO2016145896A1 PCT/CN2015/094818 CN2015094818W WO2016145896A1 WO 2016145896 A1 WO2016145896 A1 WO 2016145896A1 CN 2015094818 W CN2015094818 W CN 2015094818W WO 2016145896 A1 WO2016145896 A1 WO 2016145896A1
Authority
WO
WIPO (PCT)
Prior art keywords
field
type
smart card
contact information
stored
Prior art date
Application number
PCT/CN2015/094818
Other languages
English (en)
French (fr)
Inventor
王战锋
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016145896A1 publication Critical patent/WO2016145896A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/26—Devices for calling a subscriber
    • H04M1/27—Devices whereby a plurality of signals may be stored simultaneously
    • H04M1/274—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc
    • H04M1/2745—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc using static electronic memories, e.g. chips
    • H04M1/27453—Directories allowing storage of additional subscriber data, e.g. metadata
    • H04M1/27457—Management thereof, e.g. manual editing of data

Definitions

  • This document relates to, but is not limited to, the field of contact information management, and in particular, to a contact information management method and apparatus, a terminal, and a computer readable storage medium.
  • the frequency of mobile terminal users replacing mobile communication terminals is getting faster and faster; users are required to update their contacts to new mobiles when replacing mobile communication terminals.
  • this prompts many users to prefer to store their contacts in the phone book of the smart card inserted by the mobile communication terminal when using the mobile communication terminal, instead of being stored in the mobile communication terminal phone.
  • the benefit to the user is that when the user replaces the mobile communication terminal, the user can easily update his or her contacts to the new mobile communication terminal by simply inserting the smart card into the new mobile communication terminal.
  • the 3G smart card or the 4G smart card in the market some are 2G phone book, some are 3G phone book, if it is 3G phone book, then the smart card phone book allows the user to save a contact, can save a name, Two numbers, one email address.
  • the 3G phone book in the 3G or 4G card since the user can save the e-mail address in the 3G phone book, it is convenient for the mobile terminal user who needs to save many e-mail addresses to the smart card phone book.
  • the problem that the user terminal data transfer faced when the user replaces the mobile terminal when the mobile terminal user likes to frequently replace the mobile terminal and has many e-mail addresses stored in the smart card phone book is solved.
  • the current 3G phone book which is the 3G phone book of the 3G or 4G smart card currently on the market, which supports the maximum number of contacts that can be stored, that is, supports the number of contacts that can be stored, and supports contacts that can be stored.
  • the number of e-mail addresses is inconsistent, and specifically: the number of contacts that can be stored in the 3G phone book can be greater than the number of contact e-mail addresses that can be stored. In other words, not every contact stored in the 3G phone book can save an email address.
  • a phone book in a 3G or 4G smart card is a 3G phone book.
  • This phone book can store 500 contacts.
  • the mobile terminal user can save a name and two phone numbers for each contact in the phone book.
  • this smart card's 3G phone book supports saving 500 contacts, but not every one of the 500 contacts can save the email address. Only 100 of the 500 contacts can be saved.
  • E-mail address if the user has saved the e-mail address of 100 contacts in the phone book of the smart card, then when the user continues to save the 101st contact e-mail address, the contact e-mail storage will be prompted. The maximum number or contact email address storage area is full, or an error is reported directly.
  • the current status quo especially for users who have a large number of e-mail addresses to the smart card phone book, is very inconvenient.
  • the embodiment of the invention provides a method, a device and a terminal for managing contact information to improve the user experience.
  • a contact information management method comprising: dividing an information field into a first type field and a second type field according to a maximum number of storages supported by each information field in the contact information of the user smart card phone book;
  • the maximum number of memory blocks supported by the class field is equal to the maximum number of bytes that can be stored by the abbreviated dialing supported by the user's smart card phone.
  • the maximum number of memory blocks supported by the second type of field is less than User smart card phone. The maximum number of digits that can be stored by the abbreviated dialing; the first type of field is stored in the user's smart card phone book, and the second type of field is stored when the user smart card phone has an unoccupied number of corresponding fields.
  • the user smart card phone book when the user smart card phone has no corresponding number of corresponding fields, it is stored in the storage area of the mobile terminal; a storage area for storing the second type of field is opened in the mobile terminal; and the management user is received.
  • the management operation request of the contact information in the smart card phone book manages the contact information of the user smart card phone book according to the specific content of the second type field involved in the management operation request.
  • a storage area for storing the second type of field is opened in the mobile terminal, where the stored content includes: an ID field used to identify the tuple, and is used to distinguish different second type of fields.
  • the name field is used to identify the index field of the home contact, and is used to record the data field of the second type of field value, and is used to identify the user smart card identifier of the user smart card to which the contact belongs, and to identify the timestamp field of the creation time.
  • opening a storage area for storing the second type of field in the mobile terminal further includes: when there are multiple user smart cards, respectively setting a storage area for each user smart card, and/or setting a plurality of user smart card sharing Storage area.
  • the specific content management user smart card phone local contact information according to the second type field involved in the management operation request includes: when the newly added contact information includes only the first When a type of field is used, the newly added contact information is directly stored in the user smart card phone book; when the newly added contact information includes the second type of field, and the second type of field has the unoccupied number of corresponding fields in the user smart card phone book
  • the first type field and the second type field in the newly added contact information are stored in the user smart card phone book; when the newly added contact information includes the second type field, and the second type field is in the user smart card phone number
  • the first type field in the newly added contact information is stored in the phone book of the user smart card
  • the second type field in the newly added contact information is stored in the second type field storage area.
  • managing the contact information of the user smart card in the phone according to the specific content of the second type field involved in the management operation request includes: when the storage area of the mobile terminal is not stored When the second type of field of any contact information is used, the contact information is normally read; when the second type of field is stored in the storage area of the mobile terminal, the second type of field is used to store each tuple (ie, record) in the area. The index field is spelled with the first type of field in the user's smart card phone book. Then, the contact information formed by the splicing is read.
  • the mobile terminal needs to first read the card identifier ICCID of the smart card, and then compare the ICCID read by the mobile terminal with the ICCID value stored in the storage area of the mobile terminal: if the two are the same, the mobile terminal
  • the record in the storage area is a record corresponding to the second type of field of the smart card phone book, and needs to be spliced with the contact in the smart card phone book; if the two values are not the same, the record in the storage area of the mobile terminal is not the smart card.
  • the record of the second type of field in the phone book does not need to be spliced with the contacts in the smart card phone book.
  • the second class of the second type field storage area of the mobile terminal that is not spliced with the user smart card phone contact data needs to be spliced.
  • the records in the field table are deleted. If the mobile terminal supports multiple user smart cards, when the mobile terminal starts reading multiple card phone contacts, the mobile terminal needs to splicing the plurality of user smart card phonebook contact data inserted with the mobile terminal. Records in the second type of field table in the class field store are deleted.
  • the specific content management user smart card phone local contact information includes: the second category of the modified contact information The field is stored in the second type field storage area, and when the value is still modified, the modified second type field is stored in the second type field storage area; when the second type field of the modified contact information is stored in the first In the second type field storage area, and when there is no value after modification, the second type field of the modified contact information stored in the storage area of the second type field is deleted; when the second type field of the modified contact information is stored in the user smart card In the phone book, and after the modification still has a value, the modified second type field is stored in the user smart card phone book; when the second type field of the modified contact information is stored in the user smart card phone book, and no When the value is deleted, the second type field of the modified contact information stored in the user smart card phone book is deleted, and further determining whether other contacts are stored in the second type field area The second type of field of interest, if the second type of
  • the specific content management user smart card phone local contact information includes: when When the deleted contact information does not include the second type of field, the deleted contact information stored in the user smart card phone book is directly deleted; when the deleted contact information includes the second type field, and the second type field is stored in the user smart card In the phone book, the deleted contact information stored in the phone book of the user smart card is directly deleted, and further, whether the second type field of other contact information is stored in the second type field storage area, if the second type field is A second type of field in which other contact information is stored in the storage area, after deleting the deleted contact information stored in the user smart card phone book, according to the timestamp field, the other contact information stored in the second type field storage area is In the second type of field, the second type field of the contact with the earliest time is selected and moved to the user smart card phone book; when the deleted contact information includes the second type field, and the second type field is stored in the second type field In the storage area, the first
  • the embodiment of the present invention also provides a contact information management apparatus, including: a dividing module, configured to divide the information field into the first type field according to the number of storage fields of each information field of the contact information in the phone card of the user smart card;
  • the second type of field ; the number of storage of the first type of field is equal to the maximum number of stored in the abbreviated dialing supported by the user's smart card phone, and the number of stored in the second type of field is smaller than the abbreviated dialing supported by the user's smart card phone
  • the first type of field is stored in the user smart card phone book, and the second type of field is stored in the user smart card phone book when the user smart card phone has an unoccupied number of corresponding fields, in the user smart card
  • the phone book is not stored in the storage area of the mobile terminal;
  • the setting module is configured to open a storage area for storing the second type of field in the mobile terminal, and the storage area is defined as the second type.
  • a management module configured to receive a management operation request for managing contact information of a user smart card phone book, according to a management operation
  • the specific content of the second type of field involved in the request manages the contact information in the user's smart card phone book.
  • the setting module is configured to set a second type of field storage area in the storage area in the mobile terminal; wherein the content stored in the second type of field storage area includes: an ID field for identifying the record, used to distinguish different The name field of the second type of field is used to identify the index field of the home contact, and is used to record the data field of the second type of field, which is used to identify the user smart card identifier of the user smart card to which the contact belongs, and is used to identify the timestamp field of the creation time. .
  • the setting module is further configured to provide each user smart card when there are multiple user smart cards
  • the card can separately set the storage area, and/or set a plurality of user smart card shared storage areas.
  • the management module is configured to directly store the newly added contact information into the user smart card phone book when the newly added contact information includes only the first type of field;
  • the newly added contact information includes the second type of field, and the second type of field has an unoccupied number of corresponding fields in the user smart card phone
  • the first type field and the second type field in the contact information are newly added.
  • the user smart card phone book when the newly added contact information includes the second type of field, and the second type of field has no occupied number of corresponding fields in the user smart card phone book, the first category in the contact information is added.
  • the field is stored in the user smart card phone book, and the second type field in the newly added contact information is stored in the second type field storage area.
  • the management module when the management operation request is to read the contact information, is configured to normally read each contact information when the second type field of the contact information is not stored in the storage area of the mobile terminal;
  • the index field of each tuple in the storage area of the second type field is spliced with the first type field in the phone book of the user smart card, and the contact information formed by the splicing is read.
  • the mobile terminal needs to first read the card identifier ICCID of the smart card, and then compare the ICCID read by the mobile terminal with the ICCID value stored in the storage area of the mobile terminal: if the two are the same, the mobile terminal
  • the record in the storage area is a record corresponding to the second type of field of the smart card phone book, and needs to be spliced with the contact in the smart card phone book; if the two values are not the same, the record in the storage area of the mobile terminal is not the smart card.
  • the record of the second type of field in the phone book does not need to be spliced with the contacts in the smart card phone book.
  • the second class of the second type field storage area of the mobile terminal that is not spliced with the user smart card phone contact data needs to be spliced.
  • the records in the field table are deleted. If the mobile terminal supports multiple user smart cards, when the mobile terminal starts reading multiple card phone contacts, the mobile terminal needs to splicing the plurality of user smart card phonebook contact data inserted with the mobile terminal. Records in the second type of field table in the class field store are deleted.
  • the management module when the management operation is to modify the contact information, is configured to: when the second type field of the modified contact information is stored in the second type field storage area, and the value remains after the modification, modify The second type of field is stored in the second type field storage area; when the second type field of the modified contact information is stored in the second type field storage area, and there is no value after the modification, the second type field is deleted.
  • a second type of field of the modified contact information stored in the storage area when the second type of the modified contact information is stored in the user smart card phone book, and the value remains after the modification, the modified second type field Stored in the user smart card phone book; when the second type field of the modified contact information is stored in the user smart card phone book and has no value after modification, the second modified user information stored in the user smart card phone book is deleted.
  • the contact with the earliest deposit time is selected from the second type field of the other contact information stored in the second type field storage area according to the timestamp field.
  • the second type of field is moved to the user's smart card phone book.
  • the management module is configured to: when the deleted contact information does not include the second type of field, directly delete the deleted contact stored in the user smart card phone book. Information; when the deleted contact information includes the second type field, and the second type field is stored in the user smart card phone book, the deleted contact information stored in the user smart card phone book is directly deleted, and the second judgment is further determined. Whether the second type field of the other contact information is stored in the class field storage area, and if the second type field is stored in the second type field storage area, the deleted in the user smart card phone book is deleted.
  • the second type field of the contact with the earliest deposit time is selected from the second type field of the other contact information stored in the second type field storage area according to the timestamp field, and moved to the user smart card phone book;
  • the deleted contact information includes the second type of field, and the second type of field is stored in the second type of field storage area
  • the user's smart card is deleted phone book contact information of the first class and second class field field stored in the storage area of the second class field.
  • the embodiment of the present invention further provides a terminal, which includes the contact information management apparatus provided by the embodiment of the present invention.
  • the embodiment of the present invention further provides a computer readable storage medium, which stores program instructions, and when the program instructions are executed by the processor, can implement a contact information management method provided by an embodiment of the present invention.
  • the embodiment of the invention provides a contact information management method, which divides the contact information into a first type of field and a second type of field, and a storage area for the second type of field in the mobile communication terminal, so that the maximum number of entries of the second type of field and the first type of field can be supported in the end user smart card phone book
  • the maximum number of entries that can be stored is the same, that is, the maximum number of supported entries in the second type of fields and the maximum number of supported entries in the first type of fields are 1:1, which enhances the user experience.
  • FIG. 1 is a schematic structural diagram of a contact information management apparatus according to a first embodiment of the present invention
  • FIG. 2 is a flowchart of a contact information management method according to a second embodiment of the present invention.
  • FIG. 3 is a flowchart of a contact information management method according to a third embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a second type of field storage table in a third embodiment of the present invention.
  • a contact information management apparatus 1 which includes:
  • the dividing module 11 is configured to divide the information field into a first type field and a second type field according to the number of stored information fields of the contact information in the user's smart card phone book; the number of the first type of fields is equal to the user smart card phone number The maximum number of bytes that can be stored by the abbreviated dialing supported by the firm. The number of stored in the second type of field is smaller than the maximum number of stored in the abbreviated dialing supported by the user's smart card phone.
  • the first type of field is stored in the user's smart card phone.
  • the second type of field is stored in the user smart card phone book when the user smart card phone has an unoccupied number of corresponding fields, and is stored in the mobile terminal when the user smart card phone has no corresponding number of corresponding fields.
  • the first type of field in the user smart card phone book means that the number of entries of the field that the smart card can store is equal to the Abbreviated dialing number supported by the user smart card phone book.
  • the field that can store the maximum number of entries which is equal to the supported by the user's smart card phone book.
  • the field of the maximum number of entries stored in the name field; the second type of field in the user smart card phone book, that is, the data item refers to the number of entries of the field that the smart card supports, which is smaller than the ADN supported by the user's smart card phone book.
  • the field of the maximum number of entries that can be stored that is, the field smaller than the maximum number of entries stored in the name field supported by the user's smart card phone book; that is, the number of storage entries supported by the second type of field is generally smaller than the first
  • the 2G phonebook of the smart card is the ADN, including a name and a number.
  • the 3G phone book in the commercial card is ADN plus other fields, and the other fields have the same maximum support entry and ADN, and some are smaller than ADN;
  • the setting module 12 is configured to open a storage area for storing the second type of field in the mobile terminal
  • the management module 13 is configured to receive a management operation request for managing contact information of the user smart card phone book, and manage the contact information of the user smart card phone book according to the specific content of the second type field involved in the management operation request.
  • the setting module 12 in the foregoing embodiment is a second type field storage area set to be set in a storage area in the mobile terminal, which is a storage table, and is called a second type storage table;
  • the second type of field storage table includes: an ID field for identifying a tuple, a name field for distinguishing different second type of fields, an index field for identifying the home contact, and a timestamp field for identifying the creation time, A data field for recording a second type of field; a user smart card identifier for identifying a user smart card to which the contact belongs.
  • the setting module 12 in the foregoing embodiment is further configured to separately set a storage area for each user smart card when there are multiple user smart cards, and/or set a plurality of user smart card sharing. Storage area.
  • the management module 13 in the foregoing embodiment is configured to:
  • the newly added contact information includes only the first type of field, the newly added contact information is directly stored in the user smart card phone book;
  • the newly added contact information includes the second type of field, and the second type of field has an unoccupied number of corresponding fields in the user smart card phone, the first type field and the second type field in the contact information are newly added.
  • the user's smart card phone book In the user's smart card phone book;
  • the new contact information includes the second type of field
  • the second type of field is in the user smart card phone book
  • the first type field in the newly added contact information is stored in the user smart card phone book
  • the second type field in the newly added contact information is stored in the second type field storage table.
  • the management module 13 in the above embodiment is configured to:
  • each contact information is normally read
  • the index field of each tuple in the second type field storage table is spliced with the first type field in the phone book of the user smart card, and the contact information formed by the splicing is read.
  • the mobile terminal needs to first read the card identifier ICCID of the smart card, and then compare the ICCID read by the mobile terminal with the ICCID value stored in the storage area of the mobile terminal: if the two are the same, the mobile terminal
  • the record in the storage area is a record corresponding to the second type of field of the smart card phone book, and needs to be spliced with the contact in the smart card phone book; if the two values are not the same, the record in the storage area of the mobile terminal is not the smart card.
  • the record of the second type of field in the phone book does not need to be spliced with the contacts in the smart card phone book.
  • the second class of the second type field storage area of the mobile terminal that is not spliced with the user smart card phone contact data needs to be spliced.
  • the records in the field table are deleted. If the mobile terminal supports multiple user smart cards, when the mobile terminal starts reading multiple card phone contacts, the mobile terminal needs to splicing the plurality of user smart card phonebook contact data inserted with the mobile terminal. Records in the second type of field table in the class field store are deleted.
  • the management module 13 in the foregoing embodiment is configured to:
  • the modified second type field of the modified contact information is stored in the second type field storage table, and the value remains after the modification, the modified second type field is stored in the second type field storage table;
  • the modified second type field of the modified contact information is stored in the second type field storage table, and the value is not changed after the modification, deleting the second type field of the modified contact information stored in the second type field storage table;
  • the second type field of the modified contact information is stored in the user smart card phone book, and the value remains after the modification, the modified second type field is stored in the user smart card phone book;
  • the second type field of the modified contact information is stored in the user smart card phone book and has no value after modification, deleting the second type field of the modified contact information stored in the user smart card phone book; and further determining the second The class field stores whether a second type of field in which other contact information is stored in the table. If the second type of field stores a second type of field in which the other contact information is stored in the table, the deleted stored in the user's smart card phone book is modified. After the second type of the contact information field, the second type field of the contact with the earliest deposit time is selected from the second type field of the other contact information stored in the second type field storage table according to the timestamp field, and moved to the user. Smart card phone book.
  • the management module 13 in the foregoing embodiment is configured to:
  • the deleted contact information stored in the user smart card phone book is directly deleted;
  • the deleted contact information includes the second type field
  • the second type field is stored in the user smart card phone book
  • the deleted contact information stored in the user smart card phone book is directly deleted; and the second type field is further determined.
  • the second type field of the other contact information is stored in the storage table, and if so, after deleting the deleted contact information stored in the user smart card phone book, according to the timestamp field, the other contact stored in the second type field storage table is stored.
  • the second type field of the person information the second type field of the contact with the earliest deposit time is selected and moved to the user smart card phone book;
  • the deleted contact information includes the second type field and the second type field is stored in the second type field storage table
  • the first type field of the deleted contact information stored in the user smart card phone book is directly deleted and The second type of field stored in the second type of field storage table.
  • the second type of field storage area may also be implemented by using a file storage method, such as a text file, an XML (Extensible Markup Language) file, or the like, or other storage methods, not limited to the use of the present invention.
  • a file storage method such as a text file, an XML (Extensible Markup Language) file, or the like, or other storage methods, not limited to the use of the present invention.
  • XML Extensible Markup Language
  • the embodiment of the present invention further provides a terminal, which includes the contact information management apparatus 1 provided by the present invention.
  • the contact information management method provided by the present invention includes the following steps:
  • the information field is divided into a first type field and a second type field; the first type of field is equal to the user smart card phone number.
  • the number of stored in the second type of field is smaller than the maximum number of stored in the abbreviated dialing supported by the user's smart card phone.
  • the first type of field is stored in the user's smart card phone.
  • the second type of field is stored in the user smart card phone book when the user smart card phone has an unoccupied number of corresponding fields, and is stored in the mobile terminal when the user smart card phone has no corresponding number of corresponding fields.
  • S202 Open a storage area for storing a second type of field in the mobile terminal
  • S203 Receive a management operation request for managing contact information of the user smart card phone book, and manage contact information of the user smart card phone book according to the specific content of the second type field involved in the management operation request.
  • the storage area for storing the second type of field is opened in the mobile terminal, and the storage table is used, which is called a second type of field storage table, where the stored content includes: used to identify the tuple.
  • the ID field is used to identify the name field of the second type of field, and is used to identify the index field of the home contact, and is used to record the data field of the second type of field, and is used to identify the user smart card identifier of the user smart card to which the contact belongs.
  • the timestamp field that identifies the creation time.
  • the opening a storage area for storing the second type of field in the mobile terminal in the foregoing embodiment further includes: when there are multiple user smart cards, respectively setting a storage area for each user smart card, and/or , set up multiple user smart card shared storage area.
  • a storage area is set for the second type of field in the mobile terminal, which may be a new table in the database of the mobile phone's phone book application, when the second type field of the smart card 3G phone book is on the smart card. After the 3G phone book is full, the second type of field will be stored in this table.
  • the smart card 3G phonebook email address field as an example. For example, if the smart card's 3G phonebook supports up to 500 contacts and supports up to 100 email addresses, then the smart card 3G phonebook is used to store email addresses.
  • the smart card 3G phone book in the database of the terminal phone application has a second type field storage table including at least an ID field, a second type field name field, an index field, a smart card identification field, a data field, and a timestamp field, wherein , ID field: indicates the tuple (row) unique identifier of the table; the second type of field name field: indicates the name of the second type of field of the smart card 3G phonebook contact represented by the data of each row record in the table, different The second type of field has a different name; the index field: indicates the data of the second type of field in the table record, which is the data of which contact in the smart card 3G phone book, that is, the smart card 3G phone corresponding to the line record The ID value of the ADN of the contact; the smart card identification field: a unique identifier for storing the smart card, such as an ICCID, etc.; the data field: after the card file belonging to a second type of field of the smart card 3G phone book is full, The field
  • multiple tables can be designed according to different second-type fields in the phone book database. By associating these tables, the effect of designing only one table can be achieved; or, according to different smart card identification fields, , design multiple tables, achieve the effect of a table through multi-table association.
  • the specific content management user smart card phonebook contact information in the second type field according to the management operation request in the above embodiment includes:
  • the newly added contact information includes only the first type of field, the newly added contact information is directly stored in the user smart card phone book;
  • the newly added contact information includes the second type of field, and the second type of field has an unoccupied number of corresponding fields in the user smart card phone, the first type field and the second type field in the contact information are newly added.
  • the user's smart card phone book In the user's smart card phone book;
  • the first type field in the newly added contact information is stored in the user smart card phone book.
  • the second type of field in the newly added contact information is stored in the second type of field storage.
  • the second type of field is stored in the newly designed smart card 3G phone book second type field storage table in the database of the mobile terminal phone book application, and the contents of each field in the table are stored correspondingly according to the definition of the above field.
  • the specific content management user smart card phonebook contact information according to the second type field involved in the management operation request in the above embodiment includes:
  • each contact information is normally read
  • the index field of each tuple in the second type field storage table is spliced with the first type field in the phone book of the user smart card, and the contact information formed by the splicing is read. For example, using the index value of the corresponding card contact ADN record recorded in the second type field table of the smart card 3G phone book, that is, the ID number of the contact ADN record, and splicing and splicing with the first type field in the smart card 3G phone book; Form a complete smart card 3G phone book contact information;
  • the mobile terminal needs to first read the card identifier ICCID of the smart card, and then compare the ICCID read by the mobile terminal with the ICCID value stored in the storage area of the mobile terminal: if the two are the same, the mobile terminal
  • the record in the storage area is a record corresponding to the second type of field of the smart card phone book, and needs to be spliced with the contact in the smart card phone book; if the two values are not the same, the record in the storage area of the mobile terminal is not the smart card.
  • the record of the second type of field in the phone book does not need to be spliced with the contacts in the smart card phone book.
  • the second class of the second type field storage area of the mobile terminal that is not spliced with the user smart card phone contact data needs to be spliced.
  • the records in the field table are deleted. If the mobile terminal supports multiple user smart cards, when the mobile terminal starts reading multiple card phone contacts, the mobile terminal needs to splicing the plurality of user smart card phonebook contact data inserted with the mobile terminal. Records in the second type of field table in the class field store are deleted.
  • the specific content management user smart card phonebook contact information in the second type field according to the management operation request in the above embodiment includes:
  • the modified second type field of the modified contact information is stored in the second type field storage table, and the value remains after the modification, the modified second type field is stored in the second type field storage table;
  • the modified second type field of the modified contact information is stored in the user smart card phone book, and the value remains after the modification, the modified second type field is stored in the user smart card phone book;
  • the second type field of the modified contact information is stored in the user smart card phone book and has no value after modification, deleting the second type field of the modified contact information stored in the user smart card phone book; and further determining the second The class field stores whether the second type field of the other contact information is stored in the table. If the second type field storage table stores the second type field of the other contact information, the stored in the deleted user smart card phone book is modified. After the second type of the contact information field, the second type field of the contact with the earliest deposit time is selected from the second type field of the other contact information stored in the second type field storage table according to the timestamp field, and moved to the user. Smart card phone book.
  • the specific content management user smart card phonebook contact information in the second type field according to the management operation request in the above embodiment includes:
  • the deleted contact information stored in the user smart card phone book is directly deleted;
  • the deleted contact information includes the second type field
  • the second type field is stored in the user smart card phone book
  • the deleted contact information stored in the user smart card phone book is directly deleted; and the second type field is further determined.
  • the second type field of the other contact information is stored in the storage table, and if so, after deleting the deleted contact information stored in the user smart card phone book, according to the timestamp field, the other contact stored in the second type field storage table is stored.
  • the second type field of the person information the second type field of the contact with the earliest deposit time is selected and moved to the user smart card phone book;
  • the deleted contact information includes the second type field and the second type field is stored in the second type field storage table
  • the first type field of the deleted contact information stored in the user smart card phone book is directly deleted and The second type of field stored in the second type of field storage table.
  • the storage of the table from the second type of field according to the timestamp field in all of the above embodiments The second type of field in the second type field of the other contact information is selected to be moved to the user's smart card.
  • the phone book can be: the storage area set in the mobile terminal, ie the smart card 3G phone book second class field
  • the principle of selecting the second type of field record for selecting other contact information is performed in the order of the timestamps stored in the record, that is, the record selecting the earliest timestamp is moved to the smart card 3G phone book for storage, including corresponding
  • the modification of other auxiliary file records that is, the index management phone book IAP (Index Administration Phone book) file record is modified.
  • the second type of field storage area may also be implemented by using a file storage manner; or other storage manners are implemented, and are not limited to the manner of using the database storage table exemplified in the embodiment.
  • the user smart card phone book is a smart card 3G phone book and the email is a second type field as an example.
  • FIG. 3 is a flowchart of a contact information management method according to a third embodiment of the present invention. As shown in FIG. 3, in the embodiment, the contact information management method provided by the present invention includes the following steps:
  • S301 Classify different fields of the contact information.
  • the smart card 3G phonebook often stores a large number of fields such as a user name and a phone number, and the number of fields such as an email address is much less. This step is based on the number of stored cards for each field of the smart card 3G phone book.
  • the fields that can store the most number of rows are recorded as the first type of field, and the rest are recorded as the second type of field.
  • a storage area is opened in the mobile terminal for storing the second type of field.
  • the newly added table in the database of the phone book application on the mobile terminal is referred to as a smart card email address table.
  • the second type of field storage area may also be implemented by using a file storage manner; or other storage manners may be implemented by using the storage table exemplified in the embodiment.
  • the smart card email address in the phone book application database in the mobile terminal includes an ID field, an index field, an email address field, a timestamp field, and a smart card identification field.
  • the ID field is a tuple (row) unique identifier field of the table;
  • the index field is used to store the index value of the contact corresponding to the value of the email address field in the smart card phone book;
  • the email address field is used To save the e-mail address saved by the user after the phone book e-mail address file is full in the smart card;
  • the timestamp field indicates the time when the line record was created;
  • the smart card identification field is used to store the unique identifier of the smart card, such as ICCID.
  • there is only one second type field (email) and the storage table in the phonebook application database in the mobile terminal may not include the second type of field name.
  • two tables can also be designed in the phone book database:
  • Table 1 is used to store information of the smart card, for example, it can be designed as an ID field, a smart card identification field, and an ID number field of the smart card.
  • Table 2 includes an ID field, an index field, an email address field, a timestamp field, and a smart card ID number field.
  • S303 Receive a management operation request, and manage according to the type of the field involved.
  • the 500 contacts can store up to 100 email addresses as an example to illustrate the technical solution of the present invention.
  • the first type of field is a name and a number
  • the second type of field is an email address.
  • the phone book application will store the name and number field in the smart card's phone book, and then store the user's email address value in the new table of the mobile communication terminal's phone book database.
  • the ID field in the table stores the row number of the table
  • the index field stores the index number of the card phone contact of the card to which the email address belongs
  • the email address field stores the email address value input by the user.
  • the timestamp field indicates when the bar record was created, and the smart card identification field stores the unique identifier of the card inserted by the mobile terminal.
  • the phonebook application is initialized to read the smart card's association.
  • the card file used to store the e-mail address in the smart card 3G phone book is full, that is, the e-mail address storage of the smart card 3G phone book is already equal to 100, except for the original normal reading, if the smart card electronic is added
  • the email address stored in the newly designed smart card email address table needs to be spliced through the index field value of each record in the table and the data of the phonebook contact in the card.
  • the mobile terminal needs to first read the card identifier ICCID of the smart card, and then compare the ICCID read by the mobile terminal with the ICCID value stored in the storage area of the mobile terminal: if the two are the same, the mobile terminal
  • the record in the storage area is a record corresponding to the second type of field of the smart card phone book, and needs to be spliced with the contact in the smart card phone book; if the two values are not the same, the record in the storage area of the mobile terminal is not the smart card.
  • the record of the second type of field in the phone book does not need to be spliced with the contacts in the smart card phone book.
  • the second class of the second type field storage area of the mobile terminal that is not spliced with the user smart card phone contact data needs to be spliced.
  • the records in the field table are deleted. If the mobile terminal supports multiple user smart cards, when the mobile terminal starts reading multiple card phone contacts, the mobile terminal needs to splicing the plurality of user smart card phonebook contact data inserted with the mobile terminal. Records in the second type of field table in the class field store are deleted.
  • the current smart card storage is the earliest in the smart card e-mail address table of the mobile communication terminal phone book database.
  • E-mail address record, and the e-mail record found in the e-mail record The index number of the contact in the smart card to which the box belongs, and the value of the e-mail address are written into the card file of the current smart card 3G phone book for storing the e-mail address, and finally, after being written into the card file, the mobile communication terminal
  • the phone book application database card email address table indicates that the contact email address will be deleted.
  • the smart card stores the earliest email address record, and writes the index number of the contact in the smart card to which the email belongs, and the value of the email address in the found email record to the current smart card 3G phone book for storing the electronic
  • the card file of the email address and finally, after being written into the card file, the mobile communication terminal If this e-mail address card application database table records indicate the contact e-mail will be deleted.
  • Scenario 8 when the smart card 3G phone book is used to store the e-mail address file is full, that is, the e-mail address storage of the smart card 3G phone book is equal to 100, and when the user deletes the contact record in the smart card 3G phone book, and when When the deleted email address field of the contact has a value, and when the deleted email address of the contact is stored in the mobile phone terminal application database card email address table, when the user deletes the contact: first Delete the record of the contact in the smart card, and then the record of the contact email address in the email address table of the mobile communication terminal phone application database card will be deleted.
  • the embodiment of the present invention further provides a computer readable storage medium, which stores program instructions, and when the program instructions are executed by the processor, can implement a contact information management method provided by an embodiment of the present invention.
  • the terminal By dividing the contact information into the first type field and the second type field, and opening the storage area in the terminal for the second type field, the terminal stores the storage ratio of the first type field and the second type field to reach 1:1, enhance the user experience;
  • the invention expands the number of e-mail addresses that the smart card phone book can store on the one hand: it can satisfy each contact when the user stores the contact in the smart card.
  • anyone can store an e-mail address so that the number of contacts stored in the smart card and the number of contacts that can store contacts are less than 1:1. That is, when 500 contacts are stored in the smart card, the user can store 500 e-mails.
  • Mail has completely changed the disadvantages of the number of contacts in the smart card and the number of e-mail addresses that can be stored in the smart card when the existing user stores the contact to the smart card;
  • the user in the process of continuously using the 3G phone book in the smart card, the user can save the email address of the user contact to the card to the maximum extent, and support the user to conveniently put the contact data when replacing the mobile communication terminal. Transfer;
  • the contact backup and recovery application software of many current contacts can be matched, and the contact data in the phone book of the user smart card can be non-destructively transferred without loss.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • each device/function module/functional unit in the above embodiment When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the solution of the embodiment of the present invention divides the contact information into a first type field and a second type field, and opens a storage area in the terminal for the second type field, so that the terminal stores the storage of the first type field and the second type field.
  • the ratio is 1:1, which enhances the user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Library & Information Science (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例提供了一种联系人信息管理方法及装置、终端，该方法包括：根据用户智能卡电话本内联系人信息中每一个信息字段所支持的存储条数，将信息字段分为第一类字段及第二类字段；在移动终端内开辟用于存储第二类字段的存储区；接收管理用户智能卡电话本内联系人信息的管理操作请求，根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息。

Description

一种联系人信息管理方法及装置、终端 技术领域
本文涉及但不限于联系人信息管理领域，尤其涉及一种联系人信息管理方法及装置、终端、计算机可读存储介质。
背景技术
随着移动通讯终端技术及移动通信应用的发展，移动终端用户更换移动通讯终端的频率越来越快；用户由于在更换移动通讯终端时，涉及到用户需要把自己的联系人更新到新的移动终端中，这就促使许多用户在使用移动通讯终端时，更愿意选择把自己的联系人存储在移动通讯终端插入的智能卡的电话本中，而非存储在移动通讯终端电话机中，这样以来，给用户带来的好处是，当用户在更换移动通讯终端时，只要把智能卡插入到新的移动通讯终端中，用户就是可以非常便捷地把自己的联系人更新到新的移动通讯终端中。
随着无线通信技术的发展无线上网速度越来越快，固定办公变成了移动办公的趋势愈来愈快，越来越多的用户习惯使用移动通讯终端进行便捷地收发电子邮件；由于考虑到更换移动通讯终端时，用户的联系人需要便捷地更换到新的移动通讯终端中进行使用，因此，很多用户选择把联系人的电子邮箱地址存储在移动终端智能卡中，这种做法，也就成为了用户为了应对更换移动终端时，其联系人转移问题的更轻松的选择。
目前市场上的3G智能卡或4G智能卡中的电话本，有的是2G电话本，有的是3G电话本，如果是3G电话本，那么，这种智能卡的电话本支持用户保存联系人时，可以保存一个姓名、两个号码、一个电子邮箱地址。在使用这种3G或4G卡中的3G电话本时，由于用户可以在该3G电话本中保存电子邮箱地址，因而为有保存许多电子邮箱到智能卡电话本中需求的移动终端用户带来了方便，最终解决了移动终端用户对于喜欢频繁更换移动终端，且其智能卡电话本中存储有许多电子邮箱地址时，当用户更换移动终端时面临的用户联系人数据转移的问题。
但目前的3G电话本存在一个问题，就是目前市场上的3G或4G智能卡的3G电话本，支持可以存储的联系人最大数目，即支持可以存储联系人姓名的数目，和支持可以存储的联系人电子邮箱数目不一致，并且具体为：3G电话本中所支持可以存储联系人姓名的数目大于所支持可以存储的联系人电子邮箱数目。也就是说，并不是存储在3G电话本中的每个联系人都可以保存一个电子邮箱地址。
比如说：一个3G或4G智能卡中的电话本是3G电话本，这个电话本可以存储500个联系人，移动终端用户可以在这个电话本中为每个联系人保存一个姓名、两个电话号码，但这个智能卡的3G电话本虽然支持保存500个联系人，但并不是这500个联系人中的每个人都能够保存电子邮箱地址，这500个联系人中，只能有100个联系人可以保存电子邮箱地址，如果用户在这个智能卡的电话本中已经保存了100个联系人的电子邮箱地址，那么，当用户在继续保存第101个联系人电子邮箱地址时，就会提示联系人电子邮箱存储已达最大数目或联系人电子邮箱地址存储区已满，或者直接报错。
目前的这个现状，特别是对于有存储大量电子邮箱地址到智能卡电话本中需求的用户，带来了非常的不便
因此，如何提供一种提高用户使用用户智能卡电话本体验的联系人信息管理方法，是本领域技术人员亟待解决的技术问题。
发明内容
以下是对本文详细描述的主题的概述，本概述并非是为了限制权利要求的保护范围。
本发明实施例提供了一种联系人信息管理方法及装置、终端，以提高用户使用体验。
一种联系人信息管理方法，其包括：根据用户智能卡电话本内联系人信息中每一个信息字段所支持的最大存储条数，将信息字段分为第一类字段及第二类字段；第一类字段所支持的最大存储条数等于用户智能卡电话本所支持的缩位拨号所能存储的最大条数，第二类字段所支持的最大存储条数小于 用户智能卡电话本所支持的缩位拨号所能存储的最大条数；第一类字段存储于用户智能卡电话本内，第二类字段在用户智能卡电话本有对应字段的未占用条数时，存储于用户智能卡电话本内，在用户智能卡电话本无对应字段的未占用条数时，存储于移动终端的存储区内；在移动终端内开辟用于存储第二类字段的存储区；接收管理用户智能卡电话本内联系人信息的管理操作请求，根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息。
可选地，在移动终端内开辟用于存储第二类字段的存储区为第二字段存储区，其中存储的内容包括：用于标识元组的ID字段，用于区别不同第二类字段的名称字段，用于标识归属联系人的索引字段，用于记录第二类字段值的数据字段，用于标识联系人所属用户智能卡的用户智能卡标识，用于标识创建时间的时间戳字段。
可选地，在移动终端内开辟用于存储第二类字段的存储区还包括：当存在多个用户智能卡时，为每一个用户智能卡分别设置存储区，和/或，设置多个用户智能卡共用存储区。
可选地，当管理操作请求为新增联系人信息时，根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息包括：当新增联系人信息仅包括第一类字段时，直接将新增联系人信息存储到用户智能卡电话本内；当新增联系人信息包括第二类字段、且第二类字段在用户智能卡电话本有对应字段的未占用条数时，将新增联系人信息内的第一类字段及第二类字段存储于用户智能卡电话本内；当新增联系人信息包括第二类字段、且第二类字段在用户智能卡电话本无对应字段的未占用条数时，将新增联系人信息内的第一类字段存储到用户智能卡电话本内，将新增联系人信息内的第二类字段存储于第二类字段存储区内。
可选地，当管理操作请求为读取联系人信息时，根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息包括：当移动终端的存储区内未存储任何联系人信息的第二类字段时，正常读取各联系人信息；当移动终端的存储区内存储有第二类字段时，利用第二类字段存储区内各元组(即记录)的索引字段与用户智能卡电话本内第一类字段进行拼 接，读取拼接形成的联系人信息。需要说明的是，移动终端需要先读取到智能卡的卡标识符ICCID，然后把移动终端读取到的ICCID和移动终端存储区中存储记录的ICCID值进行比较：如果二者相同，说明移动终端存储区中的该记录是对应该智能卡电话本第二类字段的记录，需要和智能卡电话本中的联系人进行拼接；如果二者值不相同，说明移动终端存储区中的该记录不是该智能卡电话本中第二类字段的记录，无须和智能卡电话本中的联系人进行拼接。如果移动终端只支持一个用户智能卡，当移动终端开机读完这个卡电话本联系人完成后，需要把没有和用户智能卡电话本联系人数据进行拼接的移动终端第二类字段存储区中第二类字段表中的记录删除。如果移动终端支持多个用户智能卡，当移动终端开机读取完多个卡电话本联系人完成后，需要把没有和移动终端插入的多个用户智能卡电话本联系人数据进行拼接的移动终端第二类字段存储区中第二类字段表中的记录删除。
可选地，当管理操作请求为修改联系人信息时，根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息包括：当被修改联系人信息的第二类字段存储于第二类字段存储区内，且修改后仍有值时，修改后的第二类字段存储于第二类字段存储区内；当被修改联系人信息的第二类字段存储于第二类字段存储区内，且修改后无值时，删除第二类字段存储区内存储的被修改联系人信息的第二类字段；当被修改联系人信息的第二类字段存储于用户智能卡电话本内，且修改后仍有值时，修改后的第二类字段存储于用户智能卡电话本内；当被修改联系人信息的第二类字段存储于用户智能卡电话本内，且修改后无值时，删除用户智能卡电话本内存储的被修改联系人信息的第二类字段，并进一步判断第二类字段区内是否存储有其他联系人信息的第二类字段，如果第二类字段存储区内存储有其他联系人信息的第二类字段，则在删除用户智能卡电话本内存储的被修改联系人信息的第二类字段之后，根据时间戳字段从第二类字段存储区内存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段，移动到用户智能卡电话本内。
可选地，当管理操作请求为删除联系人信息时，根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息包括：当被 删除联系人信息不包括第二类字段时，则直接删除存储于用户智能卡电话本内的被删除联系人信息；当被删除联系人信息包括第二类字段、且第二类字段存储于用户智能卡电话本内时，则直接删除存储于用户智能卡电话本内的被删除联系人信息，并进一步判断第二类字段存储区内是否存储有其他联系人信息的第二类字段，如果第二类字段存储区内存储有其他联系人信息的第二类字段，则在删除用户智能卡电话本内存储的被删除联系人信息之后，根据时间戳字段从第二类字段存储区存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段，移动到用户智能卡电话本内；当被删除联系人信息包括第二类字段、且第二类字段存储于第二类字段存储区内时，则直接删除存储于用户智能卡电话本内的被删除联系人信息的第一类字段及存储于第二类字段存储区内的第二类字段。
本发明实施例也提供了一种联系人信息管理装置，其包括：划分模块，设置为根据用户智能卡电话本内联系人信息各信息字段的存储条数，将信息字段分为第一类字段及第二类字段；第一类字段的存储条数等于用户智能卡电话本所支持的缩位拨号所能存储的最大条数，第二类字段存储条数小于用户智能卡电话本所支持的缩位拨号所能存储的最大条数；第一类字段存储于用户智能卡电话本内，第二类字段在用户智能卡电话本有对应字段的未占用条数时，存储于用户智能卡电话本内，在用户智能卡电话本无对应字段的未占用条数时，存储于移动终端的存储区内；设置模块，设置为在移动终端内开辟用于存储第二类字段的存储区,该存储区定义为第二类字段存储区；管理模块，设置为接收管理用户智能卡电话本内联系人信息的管理操作请求，根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息。
可选地，设置模块是设置为在移动终端内的存储区设置第二类字段存储区；其中，第二类字段存储区存储的内容包括：用于标识记录的ID字段，用于区别不同第二类字段的名称字段，用于标识归属联系人的索引字段，用于记录第二类字段的数据字段，用于标识联系人所属用户智能卡的用户智能卡标识，用于标识创建时间的时间戳字段。
可选地，设置模块还设置为当存在多个用户智能卡时，为每一个用户智 能卡分别设置存储区，和/或，设置多个用户智能卡共用存储区。
可选地，当管理操作请求为新增联系人信息时，管理模块是设置为当新增联系人信息仅包括第一类字段时，直接将新增联系人信息存储到用户智能卡电话本内；当新增联系人信息包括第二类字段、且第二类字段在用户智能卡电话本有对应字段的未占用条数时，将新增联系人信息内的第一类字段及第二类字段存储于用户智能卡电话本内；当新增联系人信息包括第二类字段、且第二类字段在用户智能卡电话本无对应字段的未占用条数时，将新增联系人信息内的第一类字段存储到用户智能卡电话本内，将新增联系人信息内的第二类字段存储于第二类字段存储区内。
可选地，当管理操作请求为读取联系人信息时，管理模块是设置为当移动终端的存储区内未存储任何联系人信息的第二类字段时，正常读取各联系人信息；当移动终端的存储区内存储有第二类字段时，利用第二类字段存储区内各元组的索引字段与用户智能卡电话本内第一类字段进行拼接，读取拼接形成的联系人信息。需要说明的是，移动终端需要先读取到智能卡的卡标识符ICCID，然后把移动终端读取到的ICCID和移动终端存储区中存储记录的ICCID值进行比较：如果二者相同，说明移动终端存储区中的该记录是对应该智能卡电话本第二类字段的记录，需要和智能卡电话本中的联系人进行拼接；如果二者值不相同，说明移动终端存储区中的该记录不是该智能卡电话本中第二类字段的记录，无须和智能卡电话本中的联系人进行拼接。如果移动终端只支持一个用户智能卡，当移动终端开机读完这个卡电话本联系人完成后，需要把没有和用户智能卡电话本联系人数据进行拼接的移动终端第二类字段存储区中第二类字段表中的记录删除。如果移动终端支持多个用户智能卡，当移动终端开机读取完多个卡电话本联系人完成后，需要把没有和移动终端插入的多个用户智能卡电话本联系人数据进行拼接的移动终端第二类字段存储区中第二类字段表中的记录删除。
可选地，当管理操作为修改联系人信息时，管理模块是设置为：当被修改联系人信息的第二类字段存储于第二类字段存储区内，且修改后仍有值时，修改后的第二类字段存储于第二类字段存储区内；当被修改联系人信息的第二类字段存储于第二类字段存储区内，且修改后无值时，删除第二类字段存 储区内存储的被修改联系人信息的第二类字段；当被修改联系人信息的第二类字段存储于用户智能卡电话本内，且修改后仍有值时，修改后的第二类字段存储于用户智能卡电话本内；当被修改联系人信息的第二类字段存储于用户智能卡电话本内，且修改后无值时，删除用户智能卡电话本内存储的被修改联系人信息的第二类字段；并进一步判断第二类字段存储区内是否存储有其他联系人信息的第二类字段，如果第二类字段存储区内存储有其他联系人信息的第二类字段，则在删除用户智能卡电话本内存储的被修改联系人信息的第二类字段之后，根据时间戳字段从第二类字段存储区内存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到用户智能卡电话本内。
可选地，当管理操作为请求删除联系人信息时，管理模块是设置为：当被删除联系人信息不包括第二类字段时，则直接删除存储于用户智能卡电话本内的被删除联系人信息；当被删除联系人信息包括第二类字段、且第二类字段存储于用户智能卡电话本内时，则直接删除存储于用户智能卡电话本内的被删除联系人信息，并进一步判断第二类字段存储区内是否存储有其他联系人信息的第二类字段，如果第二类字段存储区内存储有其他联系人信息的第二类字段，则在删除用户智能卡电话本内存储的被删除联系人信息之后，根据时间戳字段从第二类字段存储区存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到用户智能卡电话本内；当被删除联系人信息包括第二类字段、且第二类字段存储于第二类字段存储区内时，则直接删除存储于用户智能卡电话本内的被删除联系人信息的第一类字段及存储于第二类字段存储区内的第二类字段。
本发明实施例还提供了一种终端，其包括本发明实施例提供的联系人信息管理装置。
本发明实施例还提供一种计算机可读存储介质，存储有程序指令，当该程序指令被处理器执行时可实现本发明实施例所提供的一种联系人信息管理方法。
本发明的有益效果：
本发明实施例提供了一种联系人信息管理方法，通过将联系人信息分为 第一类字段及第二类字段，并为第二类字段在移动通讯终端内开辟存储区，使得最终用户智能卡电话本中所能支持存储的第二类字段的最大条目数与第一类字段所能支持存储的最大条目数一致，即第二类字段最大支持条目数和第一类字段最大支持条目数比例达到1:1，增强了用户的使用体验。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为本发明第一实施例提供的联系人信息管理装置的结构示意图；
图2为本发明第二实施例提供的联系人信息管理方法的流程图；
图3为本发明第三实施例提供的联系人信息管理方法的流程图；
图4为本发明第三实施例中第二类字段存储表的示意图。
本发明的较佳实施方式
现通过具体实施方式结合附图的方式对本发明实施例做出进一步的诠释说明。
第一实施例：
图1为本发明第一实施例提供的联系人信息管理装置的结构示意图，由图1可知，在本实施例中，提供一种联系人信息管理装置1，其包括：
划分模块11，设置为根据用户智能卡电话本内联系人信息各信息字段的存储条数，将信息字段分为第一类字段及第二类字段；第一类字段的存储条数等于用户智能卡电话本所支持的缩位拨号所能存储的最大条数，第二类字段存储条数小于用户智能卡电话本所支持的缩位拨号所能存储的最大条数；第一类字段存储于用户智能卡电话本内，第二类字段在用户智能卡电话本有对应字段的未占用条数时，存储于用户智能卡电话本内，在用户智能卡电话本无对应字段的未占用条数时，存储于移动终端的存储区内；其中，用户智能卡电话本中第一类字段即数据项，是指智能卡所能存储的该字段的条目数等于用户智能卡电话本中所支持的缩位拨号ADN(Abbreviated dialing numbers)所能存储的最大条目数的字段，即等于用户智能卡电话本中所支持 的姓名字段存储的最大条目数的字段；用户智能卡电话本中的第二类字段即数据项，是指智能卡支持的所能存储的该字段的条目数，小于用户智能卡电话本中所支持的ADN所能存储的最大条目数的字段，即小于用户智能卡电话本中所支持的姓名字段存储的最大条目数的字段；也就是说，第二类字段所支持的存储条目数，一般都小于第一类字段所支持的存储条目数；智能卡的2G电话本就是ADN，包括一个姓名一个号码。目前商用卡中3G电话本是ADN加其他字段，而其他字段有的最大支持条目和ADN相同，有的小于ADN；
设置模块12，设置为在移动终端内开辟用于存储第二类字段的存储区；
管理模块13，设置为接收管理用户智能卡电话本内联系人信息的管理操作请求，根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息。
可选地，在一些实施例中，上述实施例中的设置模块12是设置为在移动终端内的存储区设置的第二类字段存储区为存储表的形式，称为第二类存储表；第二类字段存储表包括：用于标识元组的ID字段，用于区别不同第二类字段的名称字段，用于标识归属联系人的索引字段，用于标识创建时间的时间戳字段，用于记录第二类字段的数据字段；用于标识联系人所属用户智能卡的用户智能卡标识。
可选地，在一些实施例中，上述实施例中的设置模块12还设置为于当存在多个用户智能卡时，为每一个用户智能卡分别设置存储区，和/或，设置多个用户智能卡共用存储区。
可选地，在一些实施例中，当管理操作请求为新增联系人信息时，上述实施例中的管理模块13是设置为：
当新增联系人信息仅包括第一类字段时，直接将新增联系人信息存储到用户智能卡电话本内；
当新增联系人信息包括第二类字段、且第二类字段在用户智能卡电话本有对应字段的未占用条数时，将新增联系人信息内的第一类字段及第二类字段存储于用户智能卡电话本内；
当新增联系人信息包括第二类字段、且第二类字段在用户智能卡电话本 无对应字段的未占用条数时，将新增联系人信息内的第一类字段存储到用户智能卡电话本内，将新增联系人信息内的第二类字段存储于第二类字段存储表内。
可选地，在一些实施例中，当管理操作请求为读取联系人信息时，上述实施例中的管理模块13是设置为：
当移动终端的存储区内未存储任何联系人信息的第二类字段时，正常读取各联系人信息；
当移动终端的存储区内存储有第二类字段时，利用第二类字段存储表内各元组的索引字段与用户智能卡电话本内第一类字段进行拼接，读取拼接形成的联系人信息；
需要说明的是，移动终端需要先读取到智能卡的卡标识符ICCID，然后把移动终端读取到的ICCID和移动终端存储区中存储记录的ICCID值进行比较：如果二者相同，说明移动终端存储区中的该记录是对应该智能卡电话本第二类字段的记录，需要和智能卡电话本中的联系人进行拼接；如果二者值不相同，说明移动终端存储区中的该记录不是该智能卡电话本中第二类字段的记录，无须和智能卡电话本中的联系人进行拼接。如果移动终端只支持一个用户智能卡，当移动终端开机读完这个卡电话本联系人完成后，需要把没有和用户智能卡电话本联系人数据进行拼接的移动终端第二类字段存储区中第二类字段表中的记录删除。如果移动终端支持多个用户智能卡，当移动终端开机读取完多个卡电话本联系人完成后，需要把没有和移动终端插入的多个用户智能卡电话本联系人数据进行拼接的移动终端第二类字段存储区中第二类字段表中的记录删除。
可选地，在一些实施例中，当管理操作请求为修改联系人信息时，上述实施例中的管理模块13是设置为：
当被修改联系人信息的第二类字段存储于第二类字段存储表内，且修改后仍有值时，修改后的第二类字段存储于第二类字段存储表内；
当被修改联系人信息的第二类字段存储于第二类字段存储表内，且修改后无值时，删除第二类字段存储表内存储的被修改联系人信息的第二类字段； 当被修改联系人信息的第二类字段存储于用户智能卡电话本内，且修改后仍有值时，修改后的第二类字段存储于用户智能卡电话本内；
当被修改联系人信息的第二类字段存储于用户智能卡电话本内，且修改后无值时，删除用户智能卡电话本内存储的被修改联系人信息的第二类字段；并进一步判断第二类字段存储表内是否存储有其他联系人信息的第二类字段，如果第二类字段存储表内存储有其他联系人信息的第二类字段，则在删除用户智能卡电话本内存储的被修改联系人信息的第二类字段之后，根据时间戳字段从第二类字段存储表内存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到用户智能卡电话本内。
可选地，在一些实施例中，当管理操作请求为删除联系人信息时，上述实施例中的管理模块13是设置为：
当被删除联系人信息不包括第二类字段时，则直接删除存储于用户智能卡电话本内的被删除联系人信息；
当被删除联系人信息包括第二类字段、且第二类字段存储于用户智能卡电话本内时，则直接删除存储于用户智能卡电话本内的被删除联系人信息；并进一步判断第二类字段存储表内是否存储有其他联系人信息的第二类字段，若是，则在删除用户智能卡电话本内存储的被删除联系人信息之后，根据时间戳字段从第二类字段存储表存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到用户智能卡电话本内；
当被删除联系人信息包括第二类字段、且第二类字段存储于第二类字段存储表内时，则直接删除存储于用户智能卡电话本内的被删除联系人信息的第一类字段及存储于第二类字段存储表内的第二类字段。
在其他实施例中，第二类字段存储区还可以采用文件存储的方式实现，如文本文件、XML(可扩展标记语言，Extensible Markup Language)文件等；或者，其他存储方式实现，不限于采用本实施例所例举的数据库存储表的方式实现。
本发明实施例还提供了一种终端，其包括本发明提供的联系人信息管理装置1。
第二实施例：
图2为本发明第二实施例提供的联系人信息管理方法的流程图，由图2可知，在本实施例中，本发明提供的联系人信息管理方法包括以下步骤：
S201：根据用户智能卡电话本内联系人信息中每一个信息字段所支持的存储条数，将信息字段分为第一类字段及第二类字段；第一类字段的存储条数等于用户智能卡电话本所支持的缩位拨号所能存储的最大条数，第二类字段存储条数小于用户智能卡电话本所支持的缩位拨号所能存储的最大条数；第一类字段存储于用户智能卡电话本内，第二类字段在用户智能卡电话本有对应字段的未占用条数时，存储于用户智能卡电话本内，在用户智能卡电话本无对应字段的未占用条数时，存储于移动终端的存储区内；
S202：在移动终端内开辟用于存储第二类字段的存储区；
S203：接收管理用户智能卡电话本内联系人信息的管理操作请求，根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息。
在本实施例中的在移动终端内开辟用于存储第二类字段的存储区，采用存储表的方式，称为第二类字段存储表，其中，存储的内容包括：用于标识元组的ID字段，用于区别不同第二类字段的名称字段，用于标识归属联系人的索引字段，用于记录第二类字段的数据字段，用于标识联系人所属用户智能卡的用户智能卡标识，用于标识创建时间的时间戳字段。
在一些实施例中，上述实施例中的在移动终端内开辟用于存储第二类字段的存储区还包括：当存在多个用户智能卡时，为每一个用户智能卡分别设置存储区，和/或，设置多个用户智能卡共用存储区。
采用本发明技术方案，在移动终端内为第二类字段设置存储区，可以是是在移动终端的电话本应用的数据库中，新增一个表，当智能卡3G电话本的第二类字段在智能卡3G电话本中存储满了后，第二类字段将存储在这个表中。以智能卡3G电话本电子邮箱地址字段为例，比如：如果智能卡的3G电话本支持最多存储500个联系人，支持最多存储100个电子邮箱地址，那么当智能卡3G电话本中用于存储电子邮箱地址的文件存储满100个电子邮箱地 址后，如果用户还需要在智能卡中存储电子邮箱地址，那么这时，本发明技术方案突破现有技术，允许用户继续存储，把用户从应用界面输入的电子邮箱地址保存到移动终端电话本数据库中新增的这个表中。把在移动终端上电话本应用的数据库中新增的这个表称为智能卡3G电话本第二类字段存储表。终端的电话本应用的数据库中新增的这个智能卡3G电话本第二类字段存储表至少包括：ID字段、第二类字段名称字段、索引字段、智能卡标识字段、数据字段、时间戳字段，其中，ID字段：表示该表的元组(行)唯一标识；第二类字段名称字段：表示该表中每一行记录的数据所代表的智能卡3G电话本联系人的第二类字段的名称，不同的第二类字段有不同的名称；索引字段：表示该表记录中的第二类字段的数据，是属于智能卡3G电话本中哪个联系人的数据，即该行表记录所对应的智能卡3G电话本联系人的ADN的记录ID值；智能卡标识字段：用来保存智能卡的唯一标识符，比如ICCID等；数据字段：智能卡3G电话本的某个第二类字段所属的卡文件保存满了后，该字段保存到终端的电话本应用数据库新建的智能卡3G电话本第二类字段表中的该第二类字段的实际值；时间戳字段：表示创建表中该行记录的时间。在实际应用中，也可以在电话本数据库中按照不同的第二类字段，设计多个表，通过关联这些表，可以达到上面只设计一个表的效果；或者，也可以按照不同的智能卡标识字段，设计多个表，通过多表关联达到一个表的效果。
在一些实施例中，当管理操作请求为新增联系人信息时，上述实施例中的根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息包括：
当新增联系人信息仅包括第一类字段时，直接将新增联系人信息存储到用户智能卡电话本内；
当新增联系人信息包括第二类字段、且第二类字段在用户智能卡电话本有对应字段的未占用条数时，将新增联系人信息内的第一类字段及第二类字段存储于用户智能卡电话本内；
当新增联系人信息包括第二类字段、且第二类字段在用户智能卡电话本无对应字段的未占用条数时，将新增联系人信息内的第一类字段存储到用户智能卡电话本内，将新增联系人信息内的第二类字段存储于第二类字段存储 表内，即把第二类字段存储在移动终端电话本应用的数据库中新设计的智能卡3G电话本第二类字段存储表中，表中各个字段内容，按照上面字段的定义进行相应的存储。
在一些实施例中，当管理操作请求为读取联系人信息时，上述实施例中的根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息包括：
当移动终端的存储区内未存储任何联系人信息的第二类字段时，正常读取各联系人信息；
当移动终端的存储区内存储有第二类字段时，利用第二类字段存储表内各元组的索引字段与用户智能卡电话本内第一类字段进行拼接，读取拼接形成的联系人信息；例如，利用智能卡3G电话本第二类字段表中记录的对应的卡联系人ADN记录的索引值，即联系人ADN记录的ID号，与智能卡3G电话本内第一类字段进行拼接，拼接形成一条完整的智能卡3G电话本联系人信息；
需要说明的是，移动终端需要先读取到智能卡的卡标识符ICCID，然后把移动终端读取到的ICCID和移动终端存储区中存储记录的ICCID值进行比较：如果二者相同，说明移动终端存储区中的该记录是对应该智能卡电话本第二类字段的记录，需要和智能卡电话本中的联系人进行拼接；如果二者值不相同，说明移动终端存储区中的该记录不是该智能卡电话本中第二类字段的记录，无须和智能卡电话本中的联系人进行拼接。如果移动终端只支持一个用户智能卡，当移动终端开机读完这个卡电话本联系人完成后，需要把没有和用户智能卡电话本联系人数据进行拼接的移动终端第二类字段存储区中第二类字段表中的记录删除。如果移动终端支持多个用户智能卡，当移动终端开机读取完多个卡电话本联系人完成后，需要把没有和移动终端插入的多个用户智能卡电话本联系人数据进行拼接的移动终端第二类字段存储区中第二类字段表中的记录删除。
在一些实施例中，当管理操作请求为修改联系人信息时，上述实施例中的根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息包括：
当被修改联系人信息的第二类字段存储于第二类字段存储表内，且修改后仍有值时，修改后的第二类字段存储于第二类字段存储表内；
当被修改联系人信息的第二类字段存储于第二类字段存储表内，且修改后无值时，删除第二类字段存储表内存储的被修改联系人信息的第二类字段；
当被修改联系人信息的第二类字段存储于用户智能卡电话本内，且修改后仍有值时，修改后的第二类字段存储于用户智能卡电话本内；
当被修改联系人信息的第二类字段存储于用户智能卡电话本内，且修改后无值时，删除用户智能卡电话本内存储的被修改联系人信息的第二类字段；并进一步判断第二类字段存储表内是否存储有其他联系人信息的第二类字段，如果第二类字段存储表否存储有其他联系人信息的第二类字段，则在删除用户智能卡电话本内存储的被修改联系人信息的第二类字段之后，根据时间戳字段从第二类字段存储表内存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到用户智能卡电话本内。
在一些实施例中，当管理操作请求为删除联系人信息时，上述实施例中的根据管理操作请求所涉及的第二类字段的具体内容管理用户智能卡电话本内联系人信息包括：
当被删除联系人信息不包括第二类字段时，则直接删除存储于用户智能卡电话本内的被删除联系人信息；
当被删除联系人信息包括第二类字段、且第二类字段存储于用户智能卡电话本内时，则直接删除存储于用户智能卡电话本内的被删除联系人信息；并进一步判断第二类字段存储表内是否存储有其他联系人信息的第二类字段，若是，则在删除用户智能卡电话本内存储的被删除联系人信息之后，根据时间戳字段从第二类字段存储表存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到用户智能卡电话本内；
当被删除联系人信息包括第二类字段、且第二类字段存储于第二类字段存储表内时，则直接删除存储于用户智能卡电话本内的被删除联系人信息的第一类字段及存储于第二类字段存储表内的第二类字段。
可选地，上述所有实施例内的根据时间戳字段从第二类字段存储表存储 的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到用户智能卡电话本内可以是：在移动终端设置的存储区即智能卡3G电话本第二类字段表中，进行选择其他联系人信息的第二类字段记录的原则，是按照记录存储的时间戳的先后顺序进行，即挑选最早时间戳的记录移动到智能卡3G电话本中进行存储，包括进行相应的其他辅助文件记录的修改，即索引管理电话本IAP(Index Administration Phone book)文件记录进行修改。
在其他实施例中，第二类字段存储区还可以采用文件存储的方式实现；或者，其他存储方式实现，不限于采用本实施例所例举的数据库存储表的方式实现。
现结合具体应用场景对本发明实施例方案做进一步的诠释说明。
第三实施例：
在本实施例中，以用户智能卡电话本为智能卡3G电话本、电子邮件为第二类字段为例进行说明。
图3为本发明第三实施例提供的联系人信息管理方法的流程图，由图3可知，在本实施例中，本发明提供的联系人信息管理方法包括以下步骤：
S301：将联系人信息的不同字段进行分类。
在实际应用中，智能卡3G电话本往往将用户名、电话号码等字段设置的可以存储很多，而电子邮件地址等字段就少许多，本步骤根据智能卡3G电话本针对各字段的存储条数，将可以存储条数最多的字段记为第一类字段，其余的记为第二类字段。
S302：为第二类字段分配存储区。
在移动终端内开辟存储区，用于存储第二类字段，本实施例将移动终端上电话本应用的数据库中新增的表称为智能卡电子邮箱地址表。
在其他实施例中，第二类字段存储区还可以采用文件存储的方式实现；或者，其他存储方式实现，不限于采用本实施例所例举的存储表的方式实现。
如图4所示，移动终端内电话本应用数据库中这个智能卡电子邮箱地址 表包括ID字段、索引字段、电子邮箱地址字段、时间戳字段、智能卡标识字段。其中，ID字段是表的元组(行)唯一标识字段；索引字段是用来保存本行中电子邮箱地址字段的值在智能卡电话本中所对应的联系人的索引值；电子邮箱地址字段用来保存智能卡中电话本电子邮箱地址文件满了后，用户保存的电子邮箱地址；时间戳字段表示创建该行记录的时间；智能卡标识字段用来保存智能卡的唯一标识符，比如ICCID等。本实施例中，只有一个第二类字段(电子邮箱)，移动终端内电话本应用数据库中的存储表可以不包括第二类字段名称。
当然，在另外一些实施例中，也可以在电话本数据库中设计两个表：
表一用来存储智能卡的信息，比如可以设计为ID字段、智能卡标识字段、智能卡的ID号字段。
表二包含ID字段、索引字段、电子邮箱地址字段、时间戳字段、智能卡ID号字段。
如果是两个表，通过关联两个表，达到上面只设计一个表的效果。
S303：接收到管理操作请求，根据其所涉及的字段类型进行管理。
本步骤继续以智能卡3G电话本支持最多存储500个联系人，这500个联系人最多可以存储100个电子邮箱地址为例来说明本发明的技术方案。其中，第一类字段为姓名和号码，第二类字段为电子邮箱，其过程如下：
场景1，当智能卡3G电话本中存储的联系人数目没有达到卡电话本所支持的最高上限500时，但卡中电话本电子邮箱地址文件存储已满即已经达到100，如果用户在创建新联系人时电子邮箱字段有值，那么电话本应用将把姓名和号码字段先存储在智能卡的电话本中，然后再把用户的电子邮箱地址的值存储在移动通讯终端电话本数据库新增的表中，其中，表中ID字段存储该表的行号，索引字段存储该电子邮箱地址所属的卡电话本联系人在卡电话本中的索引编号，电子邮箱地址字段存储用户输入的电子邮箱地址值，时间戳字段表示创建条记录的时间，智能卡标识字段存储移动终端所插入的卡的唯一标识。
场景2，当移动通讯终端开机，电话本应用进行初始化读取智能卡的联 系人时，当智能卡3G电话本中用于存储电子邮箱地址的卡文件已满，即智能卡3G电话本的电子邮箱地址存储已经等于100，除了原来正常读取之外，如果新增的智能卡电子邮箱地址表中有有效记录，需要把这个新设计的智能卡电子邮箱地址表中存储的电子邮箱地址，通过这个表中每个记录的索引字段值，和卡中电话本联系人的数据进行拼接，组成智能卡电话本联系人的完整数据，并且设计两个标志，其中一个标志用来标识该联系人的电子邮箱地址存储在智能卡上还是存储在移动通讯终端电话本数据库的智能卡电子邮箱地址表中，另一个标志标识如果这个电子邮箱地址是存储在智能卡时，这个电子邮箱地址存储在哪个卡中；
需要说明的是，移动终端需要先读取到智能卡的卡标识符ICCID，然后把移动终端读取到的ICCID和移动终端存储区中存储记录的ICCID值进行比较：如果二者相同，说明移动终端存储区中的该记录是对应该智能卡电话本第二类字段的记录，需要和智能卡电话本中的联系人进行拼接；如果二者值不相同，说明移动终端存储区中的该记录不是该智能卡电话本中第二类字段的记录，无须和智能卡电话本中的联系人进行拼接。如果移动终端只支持一个用户智能卡，当移动终端开机读完这个卡电话本联系人完成后，需要把没有和用户智能卡电话本联系人数据进行拼接的移动终端第二类字段存储区中第二类字段表中的记录删除。如果移动终端支持多个用户智能卡，当移动终端开机读取完多个卡电话本联系人完成后，需要把没有和移动终端插入的多个用户智能卡电话本联系人数据进行拼接的移动终端第二类字段存储区中第二类字段表中的记录删除。
场景3，当智能卡3G电话本中用于存储电子邮箱地址的卡文件已满，即智能卡3G电话本的电子邮箱地址存储已经等于100，当用户修改智能卡3G电话本中联系人记录的电子邮箱地址字段的值时，如果被修改的该联系人电子邮件存储在移动通讯终端电话本数据库的智能卡电子邮箱地址表中，且用户修改后，该联系人电子邮箱地址还有值，那么用户完成修改保存时，该联系人修改后的新电子邮箱地址仍然被保存在移动通讯终端电话本数据库的智能卡电子邮箱地址表中。
场景4，当智能卡3G电话本中用于存储电子邮箱地址的卡文件已满，即 智能卡3G电话本的电子邮箱地址存储已经等于100，当用户修改智能卡3G电话本中联系人记录的电子邮箱地址字段的值时，如果被修改的该联系人电子邮件存储在移动通讯终端电话本数据库的智能卡电子邮箱地址表中，且用户修改后，该联系人电子邮箱地址没有值了，那么用户完成修改保存时，被保存在移动通讯终端电话本数据库的智能卡电子邮箱地址表中和该联系人相关的记录被删除。
场景5，当智能卡3G电话本中用于存储电子邮箱地址的卡文件已满，即智能卡3G电话本的电子邮箱地址存储已经等于100，且当用户修改智能卡3G电话本中联系人记录的电子邮箱地址字段的值时，且当被修改的该联系人电子邮件存储在智能卡上的3G电话本中用于存储电子邮箱地址的卡文件中，用户修改后，如果该联系人电子邮箱地址还有值，那么用户完成修改保存时，该联系人修改后的新电子邮箱地址仍然被保存在智能卡上的3G电话本中用于存储电子邮箱地址的卡文件中。
场景6，当智能卡3G电话本中用于存储电子邮箱地址的卡文件已满，即智能卡3G电话本的电子邮箱地址存储已经等于100，且当用户修改智能卡3G电话本中联系人记录的电子邮箱地址字段的值时，且当被修改的该联系人电子邮件存储在智能卡上的3G电话本中用于存储电子邮箱地址的卡文件中，用户修改后，如果该联系人电子邮箱地址没有值了，那么用户完成修改保存时：首先，智能卡上的3G电话本中用于存储电子邮件地址的卡文件中的该联系人电子邮件记录将被删除，然后，由于此时智能卡3G电话本用于存储电子邮箱地址的卡文件存储了99条电子邮件记录，意味这该卡文件还可以再存储一个电子邮件记录，因此，在移动通讯终端电话本数据库的智能卡电子邮箱地址表中寻找当前智能卡存储最早的电子邮箱地址记录，并且把找到的该电子邮箱记录中表示电子邮箱所属的智能卡中联系人的索引号，和电子邮箱地址的值，写入到当前智能卡3G电话本用于存储电子邮箱地址的卡文件中，最后当写入到卡文件中后，移动通讯终端电话本应用数据库卡电子邮箱地址表中表示该联系人电子邮箱的记录将被删除。
场景7，当智能卡3G电话本中用于存储电子邮箱地址的卡文件已满，即智能卡3G电话本的电子邮箱地址存储已经等于100，且当用户删除智能卡上 的3G电话本中联系人记录时，且当被删除的该联系人电子邮箱地址字段有值时，且当被删除的该联系人电子邮箱地址存储在智能卡3G电话本中用于存储电子邮箱地址的卡文件中，那么当用户删除该联系人时：首先，智能卡3G电话本中用于存储电子邮件地址的卡文件中的该联系人电子邮件记录将被删除，然后，由于此时智能卡3G电话本用于存储电子邮箱地址的卡文件存储了99条电子邮件记录，意味这该卡文件还可以再存储一个电子邮件记录，因此，在移动通讯终端电话本数据库的智能卡电子邮箱地址表中寻找当前智能卡存储最早的电子邮箱地址记录，并且把找到的该电子邮箱记录中表示电子邮箱所属的智能卡中联系人的索引号，和电子邮箱地址的值，写入到当前智能卡3G电话本用于存储电子邮箱地址的卡文件中，最后当写入到卡文件中后，移动通讯终端电话本应用数据库卡电子邮箱地址表中表示该联系人电子邮箱的记录将被删除。
场景8，当智能卡3G电话本中用于存储电子邮箱地址文件已满，即智能卡3G电话本的电子邮箱地址存储已经等于100，且当用户删除智能卡3G电话本中联系人记录时，且当被删除的该联系人电子邮箱地址字段有值时，且当被删除的该联系人电子邮箱地址存储在移动通讯终端电话本应用数据库卡电子邮箱地址表中，那么当用户删除该联系人时：首先，删除智能卡中该联系人的记录，然后，移动通讯终端电话本应用数据库卡电子邮箱地址表中表示该联系人电子邮箱的记录将被删除。
在实际应用中，对于单卡移动通讯终端，如果智能卡3G电话本中用于存储电子邮箱地址文件不满，即该卡文件存储的电子邮箱地址数目小于100，那么移动通讯终端电话本应用数据库卡电子邮箱地址表中必定没有电子邮箱地址记录，对于多卡系统也是同理。
本发明实施例还提供一种计算机可读存储介质，存储有程序指令，当该程序指令被处理器执行时可实现本发明实施例所提供的一种联系人信息管理方法。
通过上述实施例可知，通过本发明实施例方案至少具备以下有益效果：
通过将联系人信息分为第一类字段及第二类字段，并为第二类字段在终端内开辟存储区，使得终端存储第一类字段与第二类字段的存储比例达到 1:1，增强了用户的使用体验；
采用本发明的技术方案，与现有技术相比，本发明一方面为用户扩展了智能卡电话本可以存储的电子邮箱地址的数目：能够满足用户当把联系人存储在智能卡中时，每个联系人都可以存储一个电子邮箱地址，使智能卡中存储的联系人数目和能够存储联系人电子邮箱数目达不到1：1的关系，即智能卡中存储500个联系人时，用户可以存储500个电子邮件，彻底改变了现有技术用户把联系人存储到智能卡时，智能卡中联系人的数目和可以存储的电子邮箱地址的数目无法达到1：1的弊端；
采用本发明技术方案，在用户持续使用智能卡中3G电话本过程中，可以最大限度地动态把用户联系人的电子邮箱地址保存到卡中，支持用户在更换移动通讯终端时便捷地把联系人数据进行转移；
采用本发明技术方案，可以配合目前诸多的联系人备份与恢复应用软件，可以无丢失地把用户智能卡电话本中的联系人数据进行无损转移。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的各装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的各装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
本发明实施例的方案通过将联系人信息分为第一类字段及第二类字段，并为第二类字段在终端内开辟存储区，使得终端存储第一类字段与第二类字段的存储比例达到1:1，增强了用户的使用体验。

Claims (16)

  1. 一种联系人信息管理方法，包括：
    根据用户智能卡电话本内联系人信息中每一个信息字段所支持的最大存储条数，将所述信息字段分为第一类字段及第二类字段；所述第一类字段所支持的最大存储条数等于所述用户智能卡电话本所支持的缩位拨号所能存储的最大条数，所述第二类字段所支持的最大存储条数小于所述用户智能卡电话本所支持的缩位拨号所能存储的最大条数；所述第一类字段存储于所述用户智能卡电话本内，所述第二类字段在所述用户智能卡电话本有对应字段的未占用条数时，存储于所述用户智能卡电话本内，在所述用户智能卡电话本无对应字段的未占用条数时，存储于所述移动终端的存储区内；
    在移动终端内开辟用于存储所述第二类字段的存储区；
    接收管理所述用户智能卡电话本内联系人信息的管理操作请求，根据所述管理操作请求所涉及的所述第二类字段的具体内容管理所述用户智能卡电话本内联系人信息。
  2. 如权利要求1所述的联系人信息管理方法，其中，所述在移动终端内开辟用于存储所述第二类字段的存储区为第二类字段存储区，其中，存储的内容包括：用于标识每一个记录的ID字段，用于区别不同第二类字段的名称字段，用于标识归属联系人的索引字段，用于记录第二类字段的数据字段，用于标识联系人所属用户智能卡的用户智能卡标识字段，用于标识创建时间的时间戳字段。
  3. 如权利要求2所述的联系人信息管理方法，其中，所述在移动终端内开辟用于存储所述第二类字段的存储区还包括：当存在多个用户智能卡时，为每一个用户智能卡分别设置存储区，和/或，设置所述多个用户智能卡共用所述存储区。
  4. 如权利要求2或3所述的联系人信息管理方法，其中，当所述管理操作请求为新增联系人信息时，所述根据所述管理操作请求所涉及的所述第二类字段的具体内容管理所述用户智能卡电话本内联系人信息包括：
    当所述新增联系人信息仅包括第一类字段时，直接将所述新增联系人信 息存储到所述用户智能卡电话本内；
    当所述新增联系人信息包括第二类字段、且所述第二类字段在所述用户智能卡电话本有对应字段的未占用条数时，将所述新增联系人信息内的第一类字段及第二类字段存储于所述用户智能卡电话本内；
    当所述新增联系人信息包括第二类字段、且所述第二类字段在所述用户智能卡电话本无对应字段的未占用条数时，将所述新增联系人信息内的第一类字段存储到所述用户智能卡电话本内，将所述新增联系人信息内的第二类字段存储于所述第二类字段存储区内。
  5. 如权利要求2或3所述的联系人信息管理方法，其中，当所述管理操作请求为读取联系人信息时，所述根据所述管理操作请求所涉及的所述第二类字段的具体内容管理所述用户智能卡电话本内联系人信息包括：
    当移动终端的存储区内未存储任何联系人信息的第二类字段时，正常读取各联系人信息；
    当移动终端的存储区内存储有第二类字段时，利用所述第二类字段存储区内各元组的索引字段与所述用户智能卡电话本内第一类字段进行拼接，读取拼接形成的联系人信息。
  6. 如权利要求2或3所述的联系人信息管理方法，其中，当所述管理操作请求为修改联系人信息时，所述根据所述管理操作请求所涉及的所述第二类字段的具体内容管理所述用户智能卡电话本内联系人信息包括：
    当所述被修改联系人信息的第二类字段存储于所述第二类字段存储区内，且修改后仍有值时，修改后的第二类字段存储于所述第二类字段存储区内；
    当所述被修改联系人信息的第二类字段存储于所述第二类字段存储区内，且修改后无值时，删除所述第二类字段存储区内存储的所述被修改联系人信息的第二类字段；
    当所述被修改联系人信息的第二类字段存储于所述用户智能卡电话本内，且修改后仍有值时，修改后的第二类字段存储于所述用户智能卡电话本内；
    当所述被修改联系人信息的第二类字段存储于所述用户智能卡电话本内，且修改后无值时，删除所述用户智能卡电话本内存储的所述被修改联系人信息的第二类字段；并进一步判断所述第二类字段存储区内是否存储有其他联系人信息的第二类字段，如果所述第二类字段存储区内存储有其他联系人信息的第二类字段，则在删除所述用户智能卡电话本内存储的所述被修改联系人信息的第二类字段之后，根据时间戳字段从所述第二类字段存储区内存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到所述用户智能卡电话本内。
  7. 如权利要求2或3所述的联系人信息管理方法，其中，当所述管理操作请求为删除联系人信息时，所述根据所述管理操作请求所涉及的所述第二类字段的具体内容管理所述用户智能卡电话本内联系人信息包括：
    当所述被删除联系人信息不包括第二类字段时，则直接删除存储于所述用户智能卡电话本内的被删除联系人信息
    当所述被删除联系人信息包括第二类字段、且所述第二类字段存储于所述用户智能卡电话本内时，则直接删除存储于所述用户智能卡电话本内的被删除联系人信息；并进一步判断所述第二类字段存储区内是否存储有其他联系人信息的第二类字段，若是，则在删除所述用户智能卡电话本内存储的所述被删除联系人信息之后，根据时间戳字段从所述第二类字段存储区存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到所述用户智能卡电话本内；
    当所述被删除联系人信息包括第二类字段、且所述第二类字段存储于所述第二类字段存储区内时，则直接删除存储于所述用户智能卡电话本内的被删除联系人信息的第一类字段及存储于所述第二类字段存储区内的第二类字段。
  8. 一种联系人信息管理装置，包括：
    划分模块，设置为根据用户智能卡电话本内联系人信息中每一个信息字段所支持的最大存储条数，将所述信息字段分为第一类字段及第二类字段；所述第一类字段所支持的最大存储条数等于所述用户智能卡电话本所支持的缩位拨号所能存储的最大条数，所述第二类字段所支持的最大存储条数小于 所述用户智能卡电话本所支持的缩位拨号所能存储的最大条数；所述第一类字段存储于所述用户智能卡电话本内，所述第二类字段在所述用户智能卡电话本有对应字段的未占用条数时，存储于所述用户智能卡电话本内，在所述用户智能卡电话本无对应字段的未占用条数时，存储于所述移动终端的存储区内；
    设置模块，设置为在移动终端内开辟用于存储所述第二类字段的存储区；
    管理模块，设置为接收管理所述用户智能卡电话本内联系人信息的管理请求，根据所述管理请求所涉及的所述第二类字段的具体内容管理所述用户智能卡电话本内联系人信息。
  9. 如权利要求8所述的联系人信息管理装置，其中，所述设置模块是设置为在移动终端内开辟第二类字段存储区；所述第二类字段存储区存储的内容包括：用于标识每一个记录的ID字段，用于区别不同第二类字段的名称字段，用于标识归属联系人的索引字段，用于记录第二类字段的数据字段，用于标识联系人所属用户智能卡的用户智能卡标识，用于标识创建时间的时间戳字段。
  10. 如权利要求9所述的联系人信息管理装置，其中，所述设置模块还设置为：当存在多个用户智能卡时，为各用户智能卡分别设置存储区，和/或，设置所述多个用户智能卡共用所述存储区。
  11. 如权利要求9或10所述的联系人信息管理装置，其中，当所述管理操作为新增联系人信息时，所述管理模块是设置为：
    当所述新增联系人信息仅包括第一类字段时，直接将所述新增联系人信息存储到所述用户智能卡电话本内；
    当所述新增联系人信息包括第二类字段、且所述第二类字段在所述用户智能卡电话本有对应字段的未占用条数时，将所述新增联系人信息内的第一类字段及第二类字段存储于所述用户智能卡电话本内；
    当所述新增联系人信息包括第二类字段、且所述第二类字段在所述用户智能卡电话本无对应字段的未占用条数时，将所述新增联系人信息内的第一类字段存储到所述用户智能卡电话本内，将所述新增联系人信息内的第二类 字段存储于所述第二类字段存储区内。
  12. 如权利要求9或10所述的联系人信息管理装置，其中，当所述管理操作为读取联系人信息时，所述管理模块是设置为：
    当移动终端的存储区内未存储任何联系人信息的第二类字段时，正常读取各联系人信息；
    当移动终端的存储区内存储有第二类字段时，利用所述第二类字段存储区内各元组的索引字段与所述用户智能卡电话本内第一类字段进行拼接，读取拼接形成的联系人信息。
  13. 如权利要求9或10所述的联系人信息管理装置，其中，，当所述管理操作为修改联系人信息时，所述管理模块是设置为：
    当所述被修改联系人信息的第二类字段存储于所述第二类字段存储区内，且修改后仍有值时，修改后的第二类字段存储于所述第二类字段存储区内；
    当所述被修改联系人信息的第二类字段存储于所述第二类字段存储区内，且修改后无值时，删除所述第二类字段存储区内存储的所述被修改联系人信息的第二类字段；
    当所述被修改联系人信息的第二类字段存储于所述用户智能卡电话本内，且修改后仍有值时，修改后的第二类字段存储于所述用户智能卡电话本内；
    当所述被修改联系人信息的第二类字段存储于所述用户智能卡电话本内，且修改后无值时，删除所述用户智能卡电话本内存储的所述被修改联系人信息的第二类字段；并进一步判断所述第二类字段存储区内是否存储有其他联系人信息的第二类字段，若是，则在删除所述用户智能卡电话本内存储的所述被修改联系人信息的第二类字段之后，根据时间戳字段从所述第二类字段存储区内存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到所述用户智能卡电话本内。
  14. 如权利要求9或10所述的联系人信息管理装置，其中，当所述管理操作为删除联系人信息时，所述管理模块是设置为：
    当所述被删除联系人信息不包括第二类字段时，则直接删除存储于所述用户智能卡电话本内的被删除联系人信息；
    当所述被删除联系人信息包括第二类字段、且所述第二类字段存储于所述用户智能卡电话本内时，则直接删除存储于所述用户智能卡电话本内的被删除联系人信息；并进一步判断所述第二类字段存储区内是否存储有其他联系人信息的第二类字段，若是，则在删除所述用户智能卡电话本内存储的所述被删除联系人信息之后，根据时间戳字段从所述第二类字段存储区存储的其他联系人信息的第二类字段中选择存入时间最早的联系人的第二类字段移动到所述用户智能卡电话本内；
    当所述被删除联系人信息包括第二类字段、且所述第二类字段存储于所述第二类字段存储区内时，则直接删除存储于所述用户智能卡电话本内的被删除联系人信息的第一类字段及存储于所述第二类字段存储区内的第二类字段。
  15. 一种终端，包括如权利要求8至14任一项所述的联系人信息管理装置。
  16. 一种计算机可读存储介质，存储有程序指令，当该程序指令被处理器执行时实现权利要求1-7任一项所述的方法。
PCT/CN2015/094818 2015-09-08 2015-11-17 一种联系人信息管理方法及装置、终端 WO2016145896A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510568185.0A CN106506767A (zh) 2015-09-08 2015-09-08 一种联系人信息管理方法及装置、终端
CN201510568185.0 2015-09-08

Publications (1)

Publication Number Publication Date
WO2016145896A1 true WO2016145896A1 (zh) 2016-09-22

Family

ID=56918240

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/094818 WO2016145896A1 (zh) 2015-09-08 2015-11-17 一种联系人信息管理方法及装置、终端

Country Status (2)

Country Link
CN (1) CN106506767A (zh)
WO (1) WO2016145896A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6895428B2 (en) * 2001-01-21 2005-05-17 Ericsson Inc. Method of storing e-mail address information on a SIM card
CN102523328A (zh) * 2011-11-22 2012-06-27 中兴通讯股份有限公司 一种无线通信终端及其用户信息处理方法
CN102821188A (zh) * 2011-06-09 2012-12-12 中兴通讯股份有限公司 一种扩充卡上电话本的方法和装置
CN102938804A (zh) * 2012-10-15 2013-02-20 东莞宇龙通信科技有限公司 一种管理联系人信息的方法和装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651730B (zh) * 2009-06-30 2012-02-29 重庆重邮信科通信技术有限公司 一种电话簿条目快速读取方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6895428B2 (en) * 2001-01-21 2005-05-17 Ericsson Inc. Method of storing e-mail address information on a SIM card
CN102821188A (zh) * 2011-06-09 2012-12-12 中兴通讯股份有限公司 一种扩充卡上电话本的方法和装置
CN102523328A (zh) * 2011-11-22 2012-06-27 中兴通讯股份有限公司 一种无线通信终端及其用户信息处理方法
CN102938804A (zh) * 2012-10-15 2013-02-20 东莞宇龙通信科技有限公司 一种管理联系人信息的方法和装置

Also Published As

Publication number Publication date
CN106506767A (zh) 2017-03-15

Similar Documents

Publication Publication Date Title
US8886598B1 (en) Tag-based synchronization
CN101080056B (zh) 一种移动终端的网络浏览器收藏夹的管理方法及系统
US9507821B2 (en) Mail indexing and searching using hierarchical caches
CN107885804A (zh) 数据库同步方法、应用服务器及计算机可读存储介质
CN102214188A (zh) 通讯终端及其内容存储和管理方法
US10873552B2 (en) Large data management in communication applications through multiple mailboxes
US10855637B2 (en) Architecture for large data management in communication applications through multiple mailboxes
CN102984357B (zh) 一种联系人信息管理方法及装置
CN106407355A (zh) 一种数据存储方法及装置
CN107911799B (zh) 一种利用智能路由的方法
TWI566566B (zh) 電話薄管理方法
CN106897283A (zh) 多媒体信息的处理方法和装置
CN104657435A (zh) 一种应用数据的存储管理方法和网络管理系统
CN107577787A (zh) 关联数据信息入库的方法及系统
CN102999527A (zh) Sns网络中动态信息推送方法及系统
CN109903824A (zh) 一种数字化病案分类管理系统及其使用方法
CN102404242A (zh) 一种用户信息更新装置、电子设备及用户信息更新方法
US9195664B2 (en) Method and device based on android system for tracking imported file
US10007692B2 (en) Partition filtering using smart index in memory
US20140289336A1 (en) Migrating Social Connections from a First Profile to a Second Profile
US10200320B2 (en) Import content items from email
WO2016145896A1 (zh) 一种联系人信息管理方法及装置、终端
CN107526759A (zh) 信息处理设备和信息处理方法
CN106021129A (zh) 一种终端及终端清理缓存的方法
CN101710920B (zh) 移动通信终端消息管理方法和消息管理系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15885265

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15885265

Country of ref document: EP

Kind code of ref document: A1