WO2017202020A1 - 一种通讯录联系人管理方法、装置及移动终端 - Google Patents

一种通讯录联系人管理方法、装置及移动终端 Download PDF

Info

Publication number
WO2017202020A1
WO2017202020A1 PCT/CN2016/112415 CN2016112415W WO2017202020A1 WO 2017202020 A1 WO2017202020 A1 WO 2017202020A1 CN 2016112415 W CN2016112415 W CN 2016112415W WO 2017202020 A1 WO2017202020 A1 WO 2017202020A1
Authority
WO
WIPO (PCT)
Prior art keywords
contact
label
tag
address book
instruction
Prior art date
Application number
PCT/CN2016/112415
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 WO2017202020A1 publication Critical patent/WO2017202020A1/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
    • 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
    • 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/27467—Methods of retrieving data

Definitions

  • the embodiments of the present invention relate to the field of computer technologies, and in particular, to a method, an apparatus, and a mobile terminal for managing address book contacts.
  • the user pre-stores the communication method of the contact in the address book of the mobile terminal.
  • the user When a call or a message needs to be sent to a contact in the address book, the user only needs to find the contact in the address book to call up the communication. the way. For example, if the user needs to talk to Zhang San, just enter “zhangsan” or “Zhang San” in the search box of the address book.
  • the communication method of Zhang San such as mobile phone number, landline number, mailbox, etc., will appear in Search results on the interface.
  • the embodiment of the present invention provides a method, a device, and a mobile terminal for managing an address book, which are used to solve the problem that the operation of calling multiple contacts in the prior art is complicated.
  • An embodiment of the present application provides a method for managing an address book contact, including: setting at least one label for a contact in the address book; receiving a user-triggered contact retrieval instruction, where the contact retrieval instruction is Carrying at least one tag; and extracting, from the address book, a contact that is provided with at least one tag carried in the contact retrieval instruction.
  • the setting is at least one for a contact in the address book.
  • the tag includes: creating a new tag; receiving a user-initiated add command, wherein the add command carries at least one contact; and the contact carried in the add command is associated with the new tag and stored.
  • the creating a new label includes: when the user is monitored to operate the preset label, generating the new label according to the preset label; or when the user is triggered to create a label instruction
  • the label creation interface is presented, and after the user inputs the label content through the input box in the label creation interface, the new label having the label content is generated; wherein the label content includes: a picture, a text, and/or Or voice.
  • the contact retrieving instruction when the contact retrieving instruction carries two or more tags, the retrieving from the address book is carried in the contact retrieving instruction.
  • the contact of the at least one tag includes: obtaining a contact stored in association with each of the tags; forming a group associated with the same tag to form a group; comparing all the groups, extracting the group Common contact.
  • the foregoing method further includes: when the contact record has a new contact, generating prompt information for setting the label for the newly added contact.
  • the label includes a picture label, a text label, and/or a voice label.
  • An embodiment of the present application provides an address book contact management apparatus, including: a setting module, configured to set at least one label for a contact in the address book; and a receiving module, configured to receive a user-triggered contact retrieval instruction,
  • the contact retrieving instruction carries at least one tag; the retrieving module is configured to retrieve, from the address book, a contact that is provided with at least one tag carried in the contact retrieving instruction.
  • the setting module includes: a creating unit, configured to create a new label, and a receiving unit, configured to receive a user-initiated adding instruction, where the adding instruction carries at least one contact a storage unit, configured to associate the contact carried in the adding instruction with the new tag.
  • the creating unit is specifically configured to: when the user is monitored to operate the preset label, generate the new label according to the preset label; or when the user is triggered to create a label instruction
  • the label creation interface is presented and created by the user through the label
  • the new label having the label content is generated; wherein the label content includes: a picture, a text, and/or a voice.
  • the retrieving module when the contact retrieving instruction carries two or more tags, the retrieving module includes: an obtaining unit, configured to acquire, associated with each tag The stored contact unit is configured to group the contacts stored in association with the same tag into a group, compare all the groups, and extract common contacts in the group.
  • the foregoing apparatus further includes: a generating module, configured to generate prompt information for setting a label for the newly added contact when the address book has a newly added contact.
  • a generating module configured to generate prompt information for setting a label for the newly added contact when the address book has a newly added contact.
  • the label includes a picture label, a text label, and/or a voice label.
  • the embodiment of the present invention provides a mobile terminal, including: an address book contact management device, where the address book contact management device is configured to: set at least one label for a contact in the address book; The contact retrieving instruction, wherein the contact retrieving instruction carries at least one tag; and the contact that is provided with at least one tag carried in the contact retrieving instruction is retrieved from the address book.
  • An embodiment of the present application provides a computer program comprising computer readable code that, when executed on an electronic device, causes the electronic device to perform the method described above.
  • the embodiment of the present application provides a computer readable medium in which the above computer program is stored.
  • An embodiment of the present application provides an electronic device, including: at least one processor; and a memory; wherein the memory stores a program executable by the at least one processor, the instruction being executed by the at least one processor So that the at least one processor is capable of performing the method of any of the above-mentioned embodiments of the present application.
  • the method, device and mobile terminal for managing contacts of the address book provided by the embodiment of the present invention realize labeling management of contacts by setting labels for contacts in the address book, and then need to call the same type of contact in the user.
  • you can quickly find the contacts by simply entering the same tags set by the contacts, which simplifies the steps for users to query multiple contacts and improves the efficiency of the address book query.
  • FIG. 1 is a flowchart of a method for managing an address book contact according to Embodiment 1 of the present application
  • Embodiment 2 is a schematic flowchart of a method for managing an address book contact provided by Embodiment 2 of the present application;
  • FIG. 3 is a schematic structural diagram of an address book contact management apparatus according to Embodiment 3 of the present application.
  • FIG. 4 is a schematic diagram of a hardware structure of an electronic device for performing an address book contact management method according to an embodiment of the present application.
  • FIG. 1 is a schematic flowchart diagram of a method for managing address book contacts provided in Embodiment 1 of the present application. As shown in FIG. 1 , the method provided in Embodiment 1 of the present application includes:
  • Step 101 Set at least one label for a contact in the address book.
  • the label may be: a picture label, a text label, or a voice label.
  • the picture tag can be a photo or an avatar;
  • the text tag can be a word, a phrase, or a phrase;
  • the voice tag can be an audio message of a word, phrase, or phrase.
  • the image tag set for a contact belonging to the same school alumni in the address book may be a photo taken by alumni, or a school photo, or a specific avatar;
  • the set text label may be the phrase "alumni";
  • the set voice tag may Is the audio information of the phrase "alumni".
  • There can be more than one label for a contact for example, a contact who is both alumni and colleague. You can set up two tabs for this contact, the Alumni tab and the Colleagues tab.
  • this step can be implemented by the following methods, including:
  • Step 1011 Create a new tag.
  • the new tag can be a user-defined tag or a system preset tag.
  • the user sets a custom label for the contact, and can use the custom label setting window to input or select a custom label for the specified contact, for example, if the specified contact is the user's colleague, the user enters or selects a custom for the contact.
  • the label is "colleagues.”
  • a user can set a custom label for a specified contact, either by adding a custom label to the contact or by replacing the contact's original custom label.
  • this step 1011 can be implemented by the following methods:
  • the new label is generated according to the preset label
  • the label creation interface is presented, and after the user inputs the label content through the input box in the label creation interface, the new label having the label content is generated.
  • the label content includes: a picture, a text, and/or a voice. If the content of the label is a picture, the user can import the photo from the local album, or download and import the avatar from the network side; if the label content is text, the user can input the corresponding text through the physical keyboard or the virtual keyboard; if the label content is voice The user can input the corresponding voice segment through the microphone.
  • the preset labels may be pre-set labels of the program personnel and displayed on the label creation interface, and the preset labels may be picture labels, text labels, and/or voice labels. In this way, the user does not need to import or input by himself; the preset label is used directly for the user to use.
  • the operations performed by the user on the preset label may be: a user's click operation on the preset label, or a user's drag operation on the preset label, etc., and these operations may be manually set, which is not specifically limited in this application.
  • Step 1012 Receive an add instruction triggered by a user.
  • the adding instruction carries at least one contact.
  • the user can trigger the add-on area on the user interface, that is, enter the address book.
  • the user selects the contact to be added in the address book, after the user adds the control button on the trigger interface, the user generates the The user selects the add instruction of the contact.
  • this step can also be implemented by the following method, specifically: entering the address book, at all Click on the contact's edit page in the contact's interface to add a label to the current contact in the contact's edit page.
  • Step 1013 Associate the contact carried in the adding instruction with the new tag.
  • Step 102 Receive a user-triggered contact retrieval instruction.
  • the contact retrieval instruction carries at least one label.
  • the tag carried by the retrieval instruction may be a picture, a text or a voice tag.
  • the picture label is displayed on the contact search interface, so that the user can click the picture label to perform the contact search at any time.
  • the text label or the voice label may be displayed on the contact search interface or not; if the text label or the voice label is displayed on the contact search interface, The user can directly click the text label or the voice label to perform contact search; if the text label or the voice label does not appear on the contact search interface, the user can input the text corresponding to the text label through the input box on the contact search interface, or The voice segment corresponding to the voice tag.
  • the contact retrieval instruction may be generated by a user triggering a label (a picture label, a text label, or a voice label) on the contact search interface; or an input box input by the user on the contact search interface (the text label corresponds to the The text, or the voice segment corresponding to the voice tag) is generated when the search control key is triggered.
  • a label a picture label, a text label, or a voice label
  • an input box input by the user on the contact search interface the text label corresponds to the The text, or the voice segment corresponding to the voice tag
  • Step 103 retrieve, from the address book, a contact that is provided with at least one label carried in the contact retrieval instruction.
  • the contact retrieval instruction when the contact retrieval instruction carries a label, the contact stored in association with the one label may be retrieved; when the contact retrieval instruction carries two or more labels
  • This step can be implemented as follows, including:
  • the contact retrieval instruction carries two labels of “colleague” and “alumni”.
  • This step 103 can be specifically as follows:
  • the contact A, the contact D, the contact E, and the contact F stored in association with the "colleague” tag are acquired; the contact A, the contact B, and the contact stored in association with the "alumni” tag are acquired. E and contact C.
  • the contact A, the contact D, the contact E, and the contact F are grouped into one; the contact A, the contact B, the contact E, and the contact C are grouped into two.
  • Contact A and Contact E are contacts who have both the Colleagues tab and the Alumni tab.
  • Embodiment 1 of the present application may further include the following steps:
  • Step 104 When the contact list has a new contact, generate prompt information for setting the label for the newly added contact.
  • the user can enter the label setting interface according to the prompt information, and the user can input the label content through the input box in the label creation interface, and generate the new label having the label content; then, the user adds the instruction to the label by triggering The added contact is selected; finally, the selected added contact is stored in association with the new tag.
  • the technical solution provided by the embodiment of the present application implements labeling management of contacts by setting labels for contacts in the address book, and then only needs to input the settings of the contacts when the user needs to call the same type of contacts.
  • the same label can quickly find the contact of the class, which simplifies the steps for the user to query multiple contacts, and improves the efficiency of the address book query.
  • FIG. 2 is a schematic flowchart diagram of a method for managing an address book contact provided by Embodiment 2 of the present application. As shown in FIG. 2, the method provided in the second embodiment includes:
  • Step 201 Create a new label.
  • the user can generate a new label by operating the preset label. After the label content is input in the input box in the label creation interface, a new label is generated according to the label content.
  • the new label is generated according to the preset label
  • the label creation interface is presented, and after the user inputs the label content through the input box in the label creation interface, the new label having the label content is generated;
  • the label content includes: a picture, a text, and/or a voice.
  • the user performs the preset label
  • the operation may be: a user clicks on a preset label, or a user drags a preset label, etc., and these operations may be manually set, which is not specifically limited in this application. If the content of the label input by the user is a picture, the photo can be imported from the local album, or the avatar can be downloaded and imported from the network side; if the label content is text, the user can input the corresponding text through the physical keyboard or the virtual keyboard; For voice, the user can input the corresponding voice clip through the microphone.
  • Step 202 Receive an add instruction triggered by a user.
  • the adding instruction carries at least one contact.
  • the user can trigger the add-on area on the user interface, that is, enter the address book.
  • the user selects the contact to be added in the address book, after the user adds the control button on the trigger interface, the user generates the The user selects the add instruction of the contact.
  • this step may also be implemented by the following method: specifically, entering the address book, clicking into the edit page of the contact in the interface of all contacts, and adding a label to the current contact in the edit page of the contact.
  • Step 203 Associate the contact carried in the adding instruction with the new tag.
  • Step 204 Receive a user-triggered contact retrieval instruction.
  • the contact retrieval instruction carries at least one label.
  • the tag carried by the retrieval instruction may be a picture, a text or a voice tag.
  • the picture label is displayed on the contact search interface, so that the user can click the picture label to perform the contact search at any time.
  • the text label or the voice label may be displayed on the contact search interface or not; if the text label or the voice label is displayed on the contact search interface, The user can directly click the text label or the voice label to perform contact search; if the text label or the voice label does not appear on the contact search interface, the user can input the text corresponding to the text label through the input box on the contact search interface, or The voice segment corresponding to the voice tag.
  • the contact retrieval instruction may be generated by a user triggering a label (a picture label, a text label, or a voice label) on the contact search interface; or an input box input by the user on the contact search interface (the text label corresponds to the The text, or the voice segment corresponding to the voice tag) is generated when the search control key is triggered.
  • a label a picture label, a text label, or a voice label
  • an input box input by the user on the contact search interface the text label corresponds to the The text, or the voice segment corresponding to the voice tag
  • Step 205 retrieve, from the address book, a contact that is provided with at least one label carried in the contact retrieval instruction.
  • the contact retrieval instruction carries a label
  • the identifier is retrieved
  • the contact can be associated with the stored contact; when the contact call instruction carries two or more tags, the step can be implemented as follows:
  • the technical solution provided by the embodiment of the present application implements labeling management of contacts by setting labels for contacts in the address book, and then only needs to input the settings of the contacts when the user needs to call the same type of contacts.
  • the same label can quickly find the contact of the class, which simplifies the steps for the user to query multiple contacts, and improves the efficiency of the address book query.
  • FIG. 3 is a schematic structural diagram of an address book contact management apparatus provided in Embodiment 3 of the present application.
  • the apparatus provided in the third embodiment includes: a setting module 10, a receiving module 20, and a calling module 30.
  • the setting module 10 is configured to set at least one label for a contact in the address book.
  • the receiving module 20 is configured to receive a user-triggered contact retrieving instruction, where the contact retrieving instruction carries at least one tag.
  • the retrieval module 30 is configured to retrieve, from the address book, a contact that is provided with at least one label carried in the contact retrieval instruction.
  • the technical solution provided by the embodiment of the present application implements labeling management of contacts by setting labels for contacts in the address book, and then only needs to input the settings of the contacts when the user needs to call the same type of contacts.
  • the same label can quickly find the contact of the class, which simplifies the steps for the user to query multiple contacts, and improves the efficiency of the address book query.
  • the above setting module can be implemented by the following structure.
  • the setting module includes: a creating unit, a receiving unit, and a storage unit.
  • the creation unit is used to create a new label.
  • the receiving unit is configured to receive a user-initiated add instruction, where the add command carries at least one contact.
  • the storage unit is configured to store the contact carried in the adding instruction in association with the new tag.
  • creation unit may be specifically used for:
  • the new label is generated according to the preset label
  • the label creation interface is presented, and after the user inputs the label content through the input box in the label creation interface, the new label having the label content is generated;
  • the label content includes: a picture, a text, and/or a voice.
  • the retrieving module may include: an obtaining unit and an extracting unit.
  • An obtaining unit configured to acquire a contact stored in association with each of the tags
  • an extracting unit configured to group the contacts stored in association with the same tag into a group, compare all the groups, and extract the group A common contact in the group.
  • the address book contact management device may further include: a generating module.
  • the generating module is configured to generate prompt information for setting a label for the newly added contact when the address book has a new contact.
  • the tag includes a picture tag, a text tag, and/or a voice tag.
  • the device provided in the third embodiment can implement the methods in the foregoing Embodiments 1 and 2, and the specific implementation principles can be referred to the corresponding parts in the foregoing embodiments, and details are not described herein again.
  • the mobile terminal provided in Embodiment 4 of the present application includes: an address book contact management device.
  • the address book contact management device is configured to:
  • the address book contact management device included in the mobile terminal provided in the fourth embodiment can be implemented by using the device provided in the foregoing embodiment 3.
  • the specific implementation structure and principle refer to the corresponding part in the foregoing embodiment. No longer.
  • the technical solution provided by the embodiment of the present application implements labeling management of contacts by setting labels for contacts in the address book, and then only needs to input the settings of the contacts when the user needs to call the same type of contacts.
  • the same label you can quickly find this type of contact, simplifying the user query
  • the steps of the contacts improve the efficiency of the address book query.
  • the address book contact management device may be an application located in the mobile terminal, or may be a plug-in or a software development kit (SDK) functional unit located in the application of the mobile terminal.
  • SDK software development kit
  • the embodiment is not particularly limited thereto.
  • the application may be an application (nativeApp) installed on the mobile terminal, or may be a web application (webApp) of the browser on the mobile terminal, which is not limited by the embodiment of the present application.
  • the various component embodiments of the present application can be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof.
  • a microprocessor or digital signal processor may be used in practice to implement some or all of the functionality of some or all of the components of a television set in accordance with embodiments of the present application.
  • the application can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein.
  • Such a program implementing the present application may be stored on a computer readable medium or may be in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.
  • the electronic device includes:
  • processors 410 and memory 420 One or more processors 410 and memory 420, one processor 410 is exemplified in FIG.
  • the apparatus that performs the processing method of the list item operation may further include: an input device 430 and an output device 440.
  • the processor 410, the memory 420, the input device 430, and the output device 440 may be connected by a bus or other means, as exemplified by a bus connection in FIG.
  • the memory 420 is used as a non-volatile computer readable storage medium, and can be used for storing a non-volatile software program, a non-volatile computer-executable program, and a module, as in the processing method of the list item operation in the embodiment of the present application.
  • Program instructions/modules for example, setting module 10, receiving module 20, and calling module 30 shown in FIG. 3.
  • the processor 410 executes various functional applications of the server by running non-volatile software programs, instructions, and modules stored in the memory 420 to And data processing, that is, a processing method for implementing the operation of the list item of the above method embodiment.
  • the memory 420 may include a storage program area and an storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created by use of the processing device operated according to the list item, and the like. .
  • memory 420 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • memory 420 can optionally include memory remotely located relative to processor 410, which can be connected to the processing device of the list item operation over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Input device 430 can receive input numeric or character information and generate key signal inputs related to user settings and function control of the processing device operating on the list item.
  • Output device 440 can include a display device such as a display screen.
  • the one or more modules are stored in the memory 420, and when executed by the one or more processors 410, perform a processing method of a list item operation in any of the above method embodiments.
  • the electronic device of the embodiment of the present application exists in various forms, including but not limited to:
  • Mobile communication devices These devices are characterized by mobile communication functions and are mainly aimed at providing voice and data communication.
  • Such terminals include: smart phones (such as iPhone), multimedia phones, functional phones, and low-end phones.
  • Ultra-mobile personal computer equipment This type of equipment belongs to the category of personal computers, has computing and processing functions, and generally has mobile Internet access.
  • Such terminals include: PDAs, MIDs, and UMPC devices, such as the iPad.
  • Portable entertainment devices These devices can display and play multimedia content. Such devices include: audio, video players (such as iPod), handheld game consoles, e-books, and smart toys and portable car navigation devices.
  • the server consists of a processor, a hard disk, a memory, a system bus, etc.
  • the server is similar to a general-purpose computer architecture, but because of the need to provide highly reliable services, processing power and stability High reliability in terms of reliability, security, scalability, and manageability.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without deliberate labor.

Landscapes

  • Engineering & Computer Science (AREA)
  • Library & Information Science (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephone Function (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请实施例提供一种通讯录联系人管理方法、装置及移动终端，涉及计算机技术领域。其中，所述方法包括：为所述通讯录中的联系人设置至少一个标签；接收用户触发的联系人调取指令，其中，所述联系人调取指令中携带有至少一个标签；从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。本申请实施例提供的技术方案通过为通讯录中的联系人设置标签，实现了对联系人的标签化管理，进而在用户需调取同一类联系人时，只需输入该类联系人所设置的相同标签，即可快速找到该类联系人，简化了用户查询多个联系人的步骤，提高了通讯录查询效率。

Description

一种通讯录联系人管理方法、装置及移动终端
本申请要求在2016年5月26日提交到中国国家知识产权局、申请号为201610363965.6、发明名称为“一种通讯录联系人管理方法、装置及移动终端”的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及计算机技术领域，尤其涉及一种通讯录联系人管理方法、装置及移动终端。
背景技术
目前，移动终端已成为人们必不可少的通讯工具。用户将联系人的通讯方式预先存储在移动终端的通讯录中，当需要与通讯录中的某个联系人通话或发信息时，只需在通讯录中查找该联系人即可调出其通讯方式。例如，用户需要与张三通话，只需在通讯录的搜索框中输入“zhangsan”或“张三”即可，张三的通讯方式，如手机号码、座机号码、邮箱等，就会呈现在搜索结果界面上。
发明人在实现本申请的过程中，发现现有技术存在如下缺陷：当用户想要同时群发消息时，用户仍然需要一个一个的采用上述方式进行搜索，操作复杂，且浪费时间。
发明内容
本申请实施例提供一种通讯录联系人管理方法、装置及移动终端，用以解决现有技术中调取多个联系人的操作复杂的问题。
本申请实施例提供一种通讯录联系人管理方法，包括：为所述通讯录中的联系人设置至少一个标签；接收用户触发的联系人调取指令，其中，所述联系人调取指令中携带有至少一个标签；从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。
可选的，上述的方法中，所述为所述通讯录中的联系人设置至少一个 标签，包括：创建新标签；接收用户触发的添加指令，其中，所述添加指令中携带有至少一个联系人；将所述添加指令中携带的联系人与所述新标签进行关联存储。
可选的，上述的方法中，所述创建新标签，包括：当监听到用户对预置标签进行操作时，根据所述预置标签生成所述新标签；或者当监听到用户触发创建标签指令时，展现标签创建界面，并在用户通过所述标签创建界面中的输入框输入标签内容后，生成具有所述标签内容的所述新标签；其中，所述标签内容包括：图片、文字和/或语音。
可选的，上述的方法中，当所述联系人调取指令携带有两个或两个以上的标签时，所述从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人，包括：获取与各所述标签关联存储的联系人；将与同一标签关联存储的联系人组成一个群组；将所有所述群组进行比对，提取群组中共同的联系人。
可选的，上述的方法，还包括：当所述通讯录有新增联系人时，生成为所述新增联系人设置标签的提示信息。
可选的，上述的方法中，所述标签包括图片标签、文字标签和/或语音标签。
本申请实施例提供一种通讯录联系人管理装置，包括：设置模块，用于为所述通讯录中的联系人设置至少一个标签；接收模块，用于接收用户触发的联系人调取指令，其中，所述联系人调取指令中携带有至少一个标签；调取模块，用于从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。
可选的，上述的装置中，所述设置模块，包括：创建单元，用于创建新标签；接收单元，用于接收用户触发的添加指令，其中，所述添加指令中携带有至少一个联系人；存储单元，用于将所述添加指令中携带的联系人与所述新标签进行关联存储。
可选的，上述的装置中，所述创建单元具体用于：当监听到用户对预置标签进行操作时，根据所述预置标签生成所述新标签；或者当监听到用户触发创建标签指令时，展现标签创建界面，并在用户通过所述标签创建 界面中的输入框输入标签内容后，生成具有所述标签内容的所述新标签；其中，所述标签内容包括：图片、文字和/或语音。
可选的，上述的装置中，当所述联系人调取指令中携带有两个或两个以上的标签时，所述调取模块，包括：获取单元，用于获取与各所述标签关联存储的联系人；提取单元，用于将与同一标签关联存储的联系人组成一个群组，将所有所述群组进行比对，提取群组中共同的联系人。
可选的，上述的装置，还包括：生成模块，用于当所述通讯录有新增联系人时，生成为所述新增联系人设置标签的提示信息。
可选的，上述的装置中，所述标签包括图片标签、文字标签和/或语音标签。
本申请实施例提供一种移动终端，包括：通讯录联系人管理装置；其中，所述通讯录联系人管理装置，用于：为所述通讯录中的联系人设置至少一个标签；接收用户触发的联系人调取指令，其中，所述联系人调取指令中携带有至少一个标签；从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。
本申请实施例提供一种计算机程序，其包括计算机可读代码，当所述计算机可读代码在电子设备上运行时，导致所述电子设备执行上述的方法。
本申请实施例提供一种计算机可读介质，其中存储了上述的计算机程序。
本申请实施例提供一种电子设备，包括：至少一个处理器；以及存储器；其中，所述存储器存储有可被所述至少一个处理器执行的程序，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行本申请上述任一项的方法。
本申请实施例提供的一种通讯录联系人管理方法、装置及移动终端，通过为通讯录中的联系人设置标签，实现了对联系人的标签化管理，进而在用户需调取同一类联系人时，只需输入该类联系人所设置的相同标签，即可快速找到该类联系人，简化了用户查询多个联系人的步骤，提高了通讯录查询效率。
上述说明仅是本申请技术方案的概述，为了能够更清楚了解本申请的技术手段，而可依照说明书的内容予以实施，并且为了让本申请的上述和其它目的、特征和优点能够更明显易懂，以下特举本申请的具体实施方式。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例一提供的通讯录联系人管理方法的流程图；
图2为本申请实施例二提供的通讯录联系人管理方法的流程示意图；
图3为本申请实施例三提供的通讯录联系人管理装置的结构示意图。
图4是本申请实施例提供的执行通讯录联系人管理方法的电子设备的硬件结构示意图。
具体实施例
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图1示出了本申请实施例一提供的通讯录联系人管理方法的流程示意图。如图1所示，本申请实施例一提供的所述方法，包括：
步骤101、为所述通讯录中的联系人设置至少一个标签。
其中，所述标签可以是：图片标签、文字标签或语音标签。图片标签可以是照片或头像；文字标签可以字、词组或短语；语音标签可以是字、词组或短语的音频信息。例如，为通讯录中属于同一学校校友的联系人设置的图片标签可以是校友合影的照片、或是学校照片，或是特定头像；设置的文字标签可以是词组“校友”；设置的语音标签可以是词组“校友”的音频信息。为联系人设置的标签可以不止一个，例如对于既是校友又是同事的联系人， 就可以为该联系人设置两个标签，分别为“校友”标签和“同事”标签。
在具体实施例时，本步骤可采用如下方法实现，包括：
步骤1011、创建新标签。
其中，新标签可以是用户自定义标签，也可以是系统预置标签。用户为联系人设置自定义标签，可利用自定义标签设置窗口中为指定联系人输入或选择自定义标签，例如若该指定联系人为用户的同事，则用户为该联系人输入或选择的自定义标签为“同事”。用户为指定联系人设置自定义标签既可以是为联系人新增自定义标签，也可以是对联系人原有的自定义标签进行替换。
具体的，本步骤1011可采用如下方法实现：
当监听到用户对预置标签进行操作时，根据所述预置标签生成所述新标签；或者
当监听到用户触发创建标签指令时，展现标签创建界面，并在用户通过所述标签创建界面中的输入框输入标签内容后，生成具有所述标签内容的所述新标签。
其中，所述标签内容包括：图片、文字和/或语音。若标签内容为图片，用户可从本地的相册中导入照片，也可从网络侧下载并导入头像等；若标签内容为文字，用户可通过实体键盘或虚拟键盘输入对应文字；若标签内容为语音，用户可通过麦克风输入对应的语音片段。此外，上述的预置标签可以是程序人员预先设置好的标签，并展现在标签创建界面上的，这些预置标签可以是图片标签、文字标签和/或语音标签。这样用户就无需自己导入或输入；直接使用预置标签，方便用户使用。用户对预置标签进行的操作可以是：用户对预置标签的点击操作，或用户对预置标签的拖动操作等等，这些操作可人为设定，本申请对此不作具体限定。
步骤1012、接收用户触发的添加指令。
其中，所述添加指令中携带有至少一个联系人。新标签创建完成后，用户可触发用户界面上的添加区域，即进入通讯录，用户在通讯录中选中需添加的联系人后，待用户触发界面上“添加”控键后，即生成携带有用户选中联系人的添加指令。
或者，本步骤还可采用如下方法实现，具体为：进入通讯录，在所有联 系人的界面中点击进入联系人的编辑页面，在联系人的编辑页面中为当前联系人添加标签。
步骤1013、将所述添加指令中携带的联系人与所述新标签进行关联存储。
步骤102、接收用户触发的联系人调取指令。
其中，所述联系人调取指令中携带有至少一个标签。所述调取指令携带的标签可以是图片、文字或语音标签。在具体实施时，当通讯录中的联系人设置的标签为图片标签时，该图片标签即展现在联系人搜索界面上，方便用户随时点击该图片标签进行联系人搜索。当通讯录中的联系人设置的标签为文字或语音标签时，该文字标签或语音标签可以展现在联系人搜索界面上也可不展现；若文字标签或语音标签展现在联系人搜索界面上，则用户可直接点击该文字标签或语音标签进行联系人搜索；若文字标签或语音标签不展现在联系人搜索界面上，则用户可通过联系人搜索界面上的输入框输入文字标签对应的文字，或语音标签对应的语音片段。
所述联系人调取指令可以是用户在联系人搜索界面上触发标签(图片标签、文字标签或语音标签)生成的；或者是用户在联系人搜索界面上的输入框输入标签(文字标签对应的文字，或语音标签对应的语音片段)后触发搜索控键时生成的。
步骤103、从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。
具体的，当所述联系人调取指令中携带有一个标签时，调取与该一个标签关联存储的联系人即可；当所述联系人调取指令携带有两个或两个以上的标签时，本步骤可采用如下方法实现，包括：
首先，获取与各所述标签关联存储的联系人。
然后，将与同一标签关联存储的联系人组成一个群组。
最后，将所有所述群组进行比对，提取群组中共同的联系人。
例如，联系调取指令携带有“同事”和“校友”两个标签，本步骤103可具体为：
首先，获取与“同事”标签关联存储的联系人A、联系人D、联系人E和联系人F；获取与“校友”标签关联存储的联系人A、联系人B、联系人 E和联系人C。
然后，将联系人A、联系人D、联系人E和联系人F组成群组一；将联系人A、联系人B、联系人E和联系人C组成群组二。
最后，将群组一和群组二进行比对，提取群组中共同的联系人：联系人A和联系人E。
联系人A和联系人E即为同时设置了“同事”标签和“校友”标签的联系人。
进一步的，本申请实施例一提供的所述方法，还可包括如下步骤：
步骤104、当所述通讯录有新增联系人时，生成为所述新增联系人设置标签的提示信息。
用户可根据该提示信息进入标签设置界面，用户可通过所述标签创建界面中的输入框输入标签内容后，生成具有所述标签内容的所述新标签；然后，用户通过触发添加指令为该标签选定添加的联系人；最后将选定添加的联系人与所述新标签进行关联存储。
本申请实施例提供的技术方案通过为通讯录中的联系人设置标签，实现了对联系人的标签化管理，进而在用户需调取同一类联系人时，只需输入该类联系人所设置的相同标签，即可快速找到该类联系人，简化了用户查询多个联系人的步骤，提高了通讯录查询效率。
图2示出了本申请实施例二提供的一种通讯录联系人管理方法的流程示意图。如图2所示，本实施例二提供的所述方法包括：
步骤201、创建新标签。
其中，用户可通过对预置标签进行操作来生成新标签；也可通过在标签创建界面中的输入框输入标签内容后，根据所述标签内容生成新标签。具体的：
当监听到用户对预置标签进行操作时，根据所述预置标签生成所述新标签；或者
当监听到用户触发创建标签指令时，展现标签创建界面，并在用户通过所述标签创建界面中的输入框输入标签内容后，生成具有所述标签内容的所述新标签；
其中，所述标签内容包括：图片、文字和/或语音。用户对预置标签进行 的操作可以是：用户对预置标签的点击操作，或用户对预置标签的拖动操作等等，这些操作可人为设定，本申请对此不作具体限定。用户输入的标签内容若为图片，可从本地的相册中导入照片，也可从网络侧下载并导入头像等；若标签内容为文字，用户可通过实体键盘或虚拟键盘输入对应文字；若标签内容为语音，用户可通过麦克风输入对应的语音片段。
步骤202、接收用户触发的添加指令。
其中，所述添加指令中携带有至少一个联系人。新标签创建完成后，用户可触发用户界面上的添加区域，即进入通讯录，用户在通讯录中选中需添加的联系人后，待用户触发界面上“添加”控键后，即生成携带有用户选中联系人的添加指令。或者，本步骤还可采用如下方法实现，具体为：进入通讯录，在所有联系人的界面中点击进入联系人的编辑页面，在联系人的编辑页面中为当前联系人添加标签。
步骤203、将所述添加指令中携带的联系人与所述新标签进行关联存储。
步骤204、接收用户触发的联系人调取指令。
其中，所述联系人调取指令中携带有至少一个标签。所述调取指令携带的标签可以是图片、文字或语音标签。在具体实施时，当通讯录中的联系人设置的标签为图片标签时，该图片标签即展现在联系人搜索界面上，方便用户随时点击该图片标签进行联系人搜索。当通讯录中的联系人设置的标签为文字或语音标签时，该文字标签或语音标签可以展现在联系人搜索界面上也可不展现；若文字标签或语音标签展现在联系人搜索界面上，则用户可直接点击该文字标签或语音标签进行联系人搜索；若文字标签或语音标签不展现在联系人搜索界面上，则用户可通过联系人搜索界面上的输入框输入文字标签对应的文字，或语音标签对应的语音片段。
所述联系人调取指令可以是用户在联系人搜索界面上触发标签(图片标签、文字标签或语音标签)生成的；或者是用户在联系人搜索界面上的输入框输入标签(文字标签对应的文字，或语音标签对应的语音片段)后触发搜索控键时生成的。
步骤205、从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。
具体的，当所述联系人调取指令中携带有一个标签时，调取与该一个标 签关联存储的联系人即可；当所述联系人调取指令携带有两个或两个以上的标签时，本步骤可采用如下方法实现，包括：
首先，获取与各所述标签关联存储的联系人。
然后，将与同一标签关联存储的联系人组成一个群组。
最后，将所有所述群组进行比对，提取群组中共同的联系人。
本申请实施例提供的技术方案通过为通讯录中的联系人设置标签，实现了对联系人的标签化管理，进而在用户需调取同一类联系人时，只需输入该类联系人所设置的相同标签，即可快速找到该类联系人，简化了用户查询多个联系人的步骤，提高了通讯录查询效率。
需要说明的是：对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本申请所必须的。
图3示出了本申请实施例三提供的通讯录联系人管理装置的结构示意图。如图3所示，本实施例三提供的所述装置包括：设置模块10、接收模块20和调取模块30。其中，设置模块10用于为所述通讯录中的联系人设置至少一个标签。接收模块20用于接收用户触发的联系人调取指令，其中，所述联系人调取指令中携带有至少一个标签。调取模块30用于从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。
本申请实施例提供的技术方案通过为通讯录中的联系人设置标签，实现了对联系人的标签化管理，进而在用户需调取同一类联系人时，只需输入该类联系人所设置的相同标签，即可快速找到该类联系人，简化了用户查询多个联系人的步骤，提高了通讯录查询效率。
进一步的，上述的设置模块可采用如下结构实现。具体的，所述设置模块，包括：创建单元、接收单元和存储单元。其中，创建单元用于创建新标签。接收单元用于接收用户触发的添加指令，其中，所述添加指令中携带有至少一个联系人。存储单元用于将所述添加指令中携带的联系人与所述新标签进行关联存储。
进一步的，上述的创建单元可具体用于：
当监听到用户对预置标签进行操作时，根据所述预置标签生成所述新标签；或者
当监听到用户触发创建标签指令时，展现标签创建界面，并在用户通过所述标签创建界面中的输入框输入标签内容后，生成具有所述标签内容的所述新标签；
其中，所述标签内容包括：图片、文字和/或语音。
进一步的，当所述联系人调取指令中携带有两个或两个以上的标签时，所述调取模块可包括：获取单元和提取单元。其中，获取单元，用于获取与各所述标签关联存储的联系人；提取单元，用于将与同一标签关联存储的联系人组成一个群组，将所有所述群组进行比对，提取群组中共同的联系人。
进一步的，所述通讯录联系人管理装置还可包括：生成模块。其中，生成模块，用于当所述通讯录有新增联系人时，生成为所述新增联系人设置标签的提示信息。
进一步的，所述标签包括图片标签、文字标签和/或语音标签。
这里需要说明的是：本实施例三提供的所述装置可实现上述实施例一和实施例二所述的方法，具体实现原理可参见上述各实施例中的相应部分，此处不再赘述。
本申请实施例四提供的移动终端，其包括：通讯录联系人管理装置。其中，所述通讯录联系人管理装置，用于：
为所述通讯录中的联系人设置至少一个标签；
接收用户触发的联系人调取指令，其中，所述联系人调取指令中携带有至少一个标签；
从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。
具体的，本实施例四提供的移动终端中包含的通讯录联系人管理装置可采用上述实施例三提供的装置来实现；具体的实现结构和原理可参见上述实施例中的相应部分，此处不再赘述。
本申请实施例提供的技术方案通过为通讯录中的联系人设置标签，实现了对联系人的标签化管理，进而在用户需调取同一类联系人时，只需输入该类联系人所设置的相同标签，即可快速找到该类联系人，简化了用户查询多 个联系人的步骤，提高了通讯录查询效率。
这里需要说明的是：通讯录联系人管理装置可以是位于移动终端的应用，或者还可以为位于移动终端的应用中的插件或软件开发工具包(Software Development Kit，SDK)等功能单元，本申请实施例对此不进行特别限定。可以理解的是：所述应用可以是安装在移动终端上的应用程序(nativeApp)，或者还可以是移动终端上的浏览器的一个网页程序(webApp)，本申请实施例对此不进行限定。
本申请的各个部件实施例可以以硬件实现，或者以在一个或者多个处理器上运行的软件模块实现，或者以它们的组合实现。本领域的技术人员应当理解，可以在实践中使用微处理器或者数字信号处理器(DSP)来实现根据本申请实施例的电视机中的一些或者全部部件的一些或者全部功能。本申请还可以实现为用于执行这里所描述的方法的一部分或者全部的设备或者装置程序(例如，计算机程序和计算机程序产品)。这样的实现本申请的程序可以存储在计算机可读介质上，或者可以具有一个或者多个信号的形式。这样的信号可以从因特网网站上下载得到，或者在载体信号上提供，或者以任何其他形式提供。
图4是本申请实施例提供的用于执行通讯录联系人管理方法的电子设备的硬件结构示意图，如图4所示，该电子设备包括：
一个或多个处理器410以及存储器420，图4中以一个处理器410为例。
执行列表项操作的处理方法的设备还可以包括：输入装置430和输出装置440。
处理器410、存储器420、输入装置430和输出装置440可以通过总线或者其他方式连接，图4中以通过总线连接为例。
存储器420作为一种非易失性计算机可读存储介质，可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块，如本申请实施例中的列表项操作的处理方法对应的程序指令/模块(例如，附图3所示的设置模块10、接收模块20和调取模块30)。处理器410通过运行存储在存储器420中的非易失性软件程序、指令以及模块，从而执行服务器的各种功能应用以 及数据处理，即实现上述方法实施例列表项操作的处理方法。
存储器420可以包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需要的应用程序；存储数据区可存储根据列表项操作的处理装置的使用所创建的数据等。此外，存储器420可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实施例中，存储器420可选包括相对于处理器410远程设置的存储器，这些远程存储器可以通过网络连接至列表项操作的处理装置。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
输入装置430可接收输入的数字或字符信息，以及产生与列表项操作的处理装置的用户设置以及功能控制有关的键信号输入。输出装置440可包括显示屏等显示设备。
所述一个或者多个模块存储在所述存储器420中，当被所述一个或者多个处理器410执行时，执行上述任意方法实施例中的列表项操作的处理方法。
上述产品可执行本申请实施例所提供的方法，具备执行方法相应的功能模块和有益效果。未在本实施例中详尽描述的技术细节，可参见本申请实施例所提供的方法。
本申请实施例的电子设备以多种形式存在，包括但不限于：
(1)移动通信设备：这类设备的特点是具备移动通信功能，并且以提供话音、数据通信为主要目标。这类终端包括：智能手机(例如iPhone)、多媒体手机、功能性手机，以及低端手机等。
(2)超移动个人计算机设备：这类设备属于个人计算机的范畴，有计算和处理功能，一般也具备移动上网特性。这类终端包括：PDA、MID和UMPC设备等，例如iPad。
(3)便携式娱乐设备：这类设备可以显示和播放多媒体内容。该类设备包括：音频、视频播放器(例如iPod)，掌上游戏机，电子书，以及智能玩具和便携式车载导航设备。
(4)服务器：提供计算服务的设备，服务器的构成包括处理器、硬盘、内存、系统总线等，服务器和通用的计算机架构类似，但是由于需要提供高可靠的服务，因此在处理能力、稳定性、可靠性、安全性、可扩展性、可管理性等方面要求较高。
(5)其他具有数据交互功能的电子装置。
以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性的劳动的情况下，即可以理解并实施。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到各实施方式可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
最后应说明的是：以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (16)

  1. 一种通讯录联系人管理方法，其特征在于，包括：
    为所述通讯录中的联系人设置至少一个标签；
    接收联系人调取指令，其中，所述联系人调取指令中携带有至少一个标签；
    从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。
  2. 根据权利要求1所述的方法，其特征在于，所述为所述通讯录中的联系人设置至少一个标签，包括：
    创建新标签；
    接收添加指令，其中，所述添加指令中携带有至少一个联系人；
    将所述添加指令中携带的联系人与所述新标签进行关联存储。
  3. 根据权利要求2所述的方法，其特征在于，所述创建新标签，包括：
    当监听到用户对预置标签进行操作时，根据所述预置标签生成所述新标签；或者
    当监听到用户触发创建标签指令时，展现标签创建界面，并在用户通过所述标签创建界面中的输入框输入标签内容后，生成具有所述标签内容的所述新标签；
    其中，所述标签内容包括：图片、文字和/或语音。
  4. 根据权利要求2所述的方法，其特征在于，当所述联系人调取指令携带有两个或两个以上的标签时，所述从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人，包括：
    获取与各所述标签关联存储的联系人；
    将与同一标签关联存储的联系人组成一个群组；
    将所有所述群组进行比对，提取群组中共同的联系人。
  5. 根据权利要求1～4中任一项所述的方法，其特征在于，还包括：
    当所述通讯录有新增联系人时，生成为所述新增联系人设置标签的提示信息。
  6. 根据权利要求1～4中任一项所述的方法，其特征在于，所述标签包括图片标签、文字标签和/或语音标签。
  7. 一种通讯录联系人管理装置，其特征在于，包括：
    设置模块，用于为所述通讯录中的联系人设置至少一个标签；
    接收模块，用于接收联系人调取指令，其中，所述联系人调取指令中携带有至少一个标签；
    调取模块，用于从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。
  8. 根据权利要求7所述的装置，其特征在于，所述设置模块，包括：
    创建单元，用于创建新标签；
    接收单元，用于接收添加指令，其中，所述添加指令中携带有至少一个联系人；
    存储单元，用于将所述添加指令中携带的联系人与所述新标签进行关联存储。
  9. 根据权利要求8所述的装置，其特征在于，所述创建单元具体用于：
    当监听到用户对预置标签进行操作时，根据所述预置标签生成所述新标签；或者
    当监听到用户触发创建标签指令时，展现标签创建界面，并在用户通过所述标签创建界面中的输入框输入标签内容后，生成具有所述标签内容的所述新标签；
    其中，所述标签内容包括：图片、文字和/或语音。
  10. 根据权利要求8所述的装置，其特征在于，当所述联系人调取指令中携带有两个或两个以上的标签时，所述调取模块，包括：
    获取单元，用于获取与各所述标签关联存储的联系人；
    提取单元，用于将与同一标签关联存储的联系人组成一个群组，将所有所述群组进行比对，提取群组中共同的联系人。
  11. 根据权利要求7～10中任一项所述的装置，其特征在于，还包括：
    生成模块，用于当所述通讯录有新增联系人时，生成为所述新增联系 人设置标签的提示信息。
  12. 根据权利要求7～10中任一项所述的装置，其特征在于，所述标签包括图片标签、文字标签和/或语音标签。
  13. 一种移动终端，其特征在于，包括：上述权利要求7～12中任一项所述的通讯录联系人管理装置。
  14. 一种计算机程序，包括计算机可读代码，当所述计算机可读代码在电子设备上运行时，导致所述电子设备执行根据权利要求1-6中的任一个所述的通讯录联系人管理方法。
  15. 一种计算机可读介质，其中存储了如权利要求14所述的计算机程序。
  16. 一种电子设备，其特征在于，包括：
    至少一个处理器；以及
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有能够被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够：
    为所述通讯录中的联系人设置至少一个标签；
    接收联系人调取指令，其中，所述联系人调取指令中携带有至少一个标签；
    从所述通讯录中调取设置有所述联系人调取指令中携带的至少一个标签的联系人。
PCT/CN2016/112415 2016-05-26 2016-12-27 一种通讯录联系人管理方法、装置及移动终端 WO2017202020A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610363965.6 2016-05-26
CN201610363965.6A CN105933495A (zh) 2016-05-26 2016-05-26 一种通讯录联系人管理方法、装置及移动终端

Publications (1)

Publication Number Publication Date
WO2017202020A1 true WO2017202020A1 (zh) 2017-11-30

Family

ID=56842404

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/112415 WO2017202020A1 (zh) 2016-05-26 2016-12-27 一种通讯录联系人管理方法、装置及移动终端

Country Status (2)

Country Link
CN (1) CN105933495A (zh)
WO (1) WO2017202020A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109067975A (zh) * 2018-06-28 2018-12-21 维沃移动通信有限公司 一种联系人信息管理方法及终端设备
CN111065094A (zh) * 2019-12-16 2020-04-24 Oppo广东移动通信有限公司 通讯录传输方法、装置、存储介质及电子设备
CN111953722A (zh) * 2019-05-16 2020-11-17 武汉海康存储技术有限公司 一种终端通讯录的同步方法及装置
CN112702462A (zh) * 2020-12-21 2021-04-23 上海连尚网络科技有限公司 一种添加分组的方法与设备
CN112764700A (zh) * 2020-12-31 2021-05-07 维沃移动通信有限公司 图像显示处理方法、装置、电子设备和存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105933495A (zh) * 2016-05-26 2016-09-07 乐视控股（北京）有限公司 一种通讯录联系人管理方法、装置及移动终端
CN108449480A (zh) * 2018-04-18 2018-08-24 易胜燕 一种通讯录管理方法及系统
CN110888701B (zh) * 2018-09-06 2023-02-21 上海伴我科技有限公司 一种对软件资源进行远程配置的方法、电子设备和介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101431486A (zh) * 2008-12-12 2009-05-13 中国移动通信集团北京有限公司 一种即时通信中会话参与人选择方法和装置
US20090215486A1 (en) * 2008-02-25 2009-08-27 Batni Ramachendra P Dynamic generation of group lists for a communication device using tags
EP2375707A1 (en) * 2010-03-29 2011-10-12 Giga-Byte Technology Co., Ltd. Method and Human-to-Machine Interface apparatus for managing contact data with multiple labels
CN105933495A (zh) * 2016-05-26 2016-09-07 乐视控股（北京）有限公司 一种通讯录联系人管理方法、装置及移动终端

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101513616B1 (ko) * 2007-07-31 2015-04-20 엘지전자 주식회사 이동 단말기 및 그 영상정보 관리방법
CN101489199A (zh) * 2009-02-18 2009-07-22 宇龙计算机通信科技(深圳)有限公司 一种信息发送方法、装置以及移动终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090215486A1 (en) * 2008-02-25 2009-08-27 Batni Ramachendra P Dynamic generation of group lists for a communication device using tags
CN101431486A (zh) * 2008-12-12 2009-05-13 中国移动通信集团北京有限公司 一种即时通信中会话参与人选择方法和装置
EP2375707A1 (en) * 2010-03-29 2011-10-12 Giga-Byte Technology Co., Ltd. Method and Human-to-Machine Interface apparatus for managing contact data with multiple labels
CN105933495A (zh) * 2016-05-26 2016-09-07 乐视控股（北京）有限公司 一种通讯录联系人管理方法、装置及移动终端

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109067975A (zh) * 2018-06-28 2018-12-21 维沃移动通信有限公司 一种联系人信息管理方法及终端设备
CN111953722A (zh) * 2019-05-16 2020-11-17 武汉海康存储技术有限公司 一种终端通讯录的同步方法及装置
CN111953722B (zh) * 2019-05-16 2023-06-30 武汉海康存储技术有限公司 一种终端通讯录的同步方法及装置
CN111065094A (zh) * 2019-12-16 2020-04-24 Oppo广东移动通信有限公司 通讯录传输方法、装置、存储介质及电子设备
CN111065094B (zh) * 2019-12-16 2023-08-25 Oppo广东移动通信有限公司 通讯录传输方法、装置、存储介质及电子设备
CN112702462A (zh) * 2020-12-21 2021-04-23 上海连尚网络科技有限公司 一种添加分组的方法与设备
CN112702462B (zh) * 2020-12-21 2023-03-14 上海连尚网络科技有限公司 一种添加分组的方法与设备
CN112764700A (zh) * 2020-12-31 2021-05-07 维沃移动通信有限公司 图像显示处理方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
CN105933495A (zh) 2016-09-07

Similar Documents

Publication Publication Date Title
WO2017202020A1 (zh) 一种通讯录联系人管理方法、装置及移动终端
CN106570100B (zh) 信息搜索方法和装置
WO2017215270A1 (zh) 一种信息展示方法、装置及电子设备
WO2022052749A1 (zh) 一种消息处理方法、装置、设备及存储介质
WO2017177630A1 (zh) 个性化信息推荐方法及装置
CN108369600B (zh) web浏览器扩展
CN105550252B (zh) 一种文件定位方法、装置及电子设备
CN104079696A (zh) 联系人名片的生成方法及装置
US20170277526A1 (en) Software categorization method and electronic device
CN105794155B (zh) 一种显示消息的方法、装置及设备
CN109460265A (zh) 一种激活应用程序的方法、用户终端和服务器
WO2017185652A1 (zh) 实现分享文件的方法及电子设备
WO2022063123A1 (zh) 界面显示方法、装置及电子设备
CN106325889A (zh) 数据处理方法及装置
CN106060220B (zh) 一种联系人信息创建方法和移动终端
CN104380768B (zh) 通讯录信息服务系统及用于通讯录信息服务的方法和装置
CN116527619A (zh) 信息处理方法、装置、电子设备及存储介质
CN104980807B (zh) 一种用于多媒体互动的方法及终端
US20130151605A1 (en) Call-Termination-Triggered Social Interface
CN105786834A (zh) 一种社交类网页结构化摘要的生成方法和系统
CN113253903A (zh) 操作方法及操作装置
CN110232267B (zh) 名片显示方法、装置、电子设备及存储介质
CN113179207B (zh) 消息处理方法和电子设备
CN113239212B (zh) 信息处理方法、装置和电子设备
WO2023030116A1 (zh) 显示方法及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16903004

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16903004

Country of ref document: EP

Kind code of ref document: A1