CN105847361B

CN105847361B - Contact person information management method, server and terminal

Info

Publication number: CN105847361B
Application number: CN201610178386.4A
Authority: CN
Inventors: 张璐; 程佳斌
Original assignee: Nubia Technology Co Ltd
Current assignee: Nubia Technology Co Ltd
Priority date: 2016-03-25
Filing date: 2016-03-25
Publication date: 2020-01-07
Anticipated expiration: 2036-03-25
Also published as: CN105847361A

Abstract

The embodiment of the invention discloses a contact person information management method, a server and a terminal. The server includes: the device comprises a first communication unit, a first data processing unit and a first storage unit; the first communication unit is used for obtaining contact person information of a terminal; the terminal is also used for pushing the first contact information set to the terminal; the first data processing unit is used for generating a contact information set based on the contact information obtained by the first communication unit; the terminal is also used for counting a first contact person information set communicated with the terminal within a preset time range when the pushing condition is met, and enabling the first communication unit; the first storage unit is used for storing the contact person information obtained by the first communication unit and storing a contact person information set.

Description

Contact person information management method, server and terminal

Technical Field

The invention relates to an information processing technology, in particular to a contact person information management method, a server and a terminal.

Background

The current popularity of dual card dual standby handsets has made many people own more than one mobile number and as people move about their students and jobs, the numbers of each person are updated on a periodic basis, which makes it common for people to maintain a significant number of contact list entries in their daily lives, and this huge list update, add and delete operation is a problem that many people are at a premium. At present, two contact storage modes based on a mobile phone and an SIM card exist, storage based on a Subscriber Identity Module (SIM) card has a certain limitation on the number of contacts, and a situation that the contacts cannot be written in due to insufficient capacity of a storage space occurs. In addition, the two storage modes also require complicated operation steps for backup and recovery of the contact person when the mobile phone or the SIM card is replaced, which is very inconvenient, and meanwhile, the contact person information in the mobile phone and the SIM card has the risk of loss during equipment upgrading, daily use and equipment replacement. Therefore, the contact list is maintained and managed through the terminal, so that inconvenience is brought to user experience.

Disclosure of Invention

In order to solve the existing technical problem, embodiments of the present invention provide a method, a server, and a terminal for managing contact information, which can solve the problem of inconvenience caused by maintaining and managing a contact list through the terminal.

In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:

an embodiment of the present invention provides a server, where the server includes: the device comprises a first communication unit, a first data processing unit and a first storage unit; wherein the content of the first and second substances,

the first communication unit is used for obtaining contact person information of the terminal; the terminal is also used for pushing the first contact information set to the terminal;

the first data processing unit is used for generating a contact information set based on the contact information obtained by the first communication unit; the terminal is also used for counting a first contact person information set communicated with the terminal within a preset time range when the pushing condition is met, and enabling the first communication unit;

the first storage unit is used for storing the contact person information obtained by the first communication unit and storing a contact person information set.

In the above scheme, the first data processing unit is further configured to analyze a contact information set of the terminal and a second contact information set of other terminals; the contact information corresponding to the other terminals is contained in the contact information set; and establishing an incidence relation between the contact information set and the second contact information set to generate a third contact information set.

In the above scheme, the first data processing unit is further configured to update the contact information in the contact information set when a maintenance condition is met.

In the above scheme, the first data processing unit is configured to determine whether a duplicate contact identifier exists in the contact information set; when the judgment result shows that repeated contact person identifications exist in the contact person information set, respectively obtaining communication frequencies corresponding to the repeated contact person identifications; and when the contact person identification in the repeated contact person identifications is not communicated within a preset time range, determining that the contact person identification is invalid, and deleting the contact person information corresponding to the contact person identification.

An embodiment of the present invention further provides a terminal, where the terminal includes: the second communication unit, the second storage unit and the second data processing unit; wherein the content of the first and second substances,

the second communication unit is used for acquiring a first contact information set pushed by the server; the server is also used for sending the second query instruction to the server; the server is further used for obtaining a query result corresponding to the second query instruction;

the second storage unit is used for storing the first contact information set obtained by the second communication unit;

the second data processing unit is configured to, when a first query instruction including a first contact identifier is detected, determine whether the first contact information set includes the first contact identifier; and when the judgment result shows that the first contact person information set does not comprise the first contact person identification, generating a second query instruction comprising the first contact person identification, and enabling the second communication unit.

The embodiment of the invention also provides a method for managing the contact information, which comprises the following steps:

the server obtains and stores contact information of the terminal and generates a contact information set;

and when the pushing condition is met, counting a first contact information set communicated with the terminal within a preset time range, and pushing the first contact information set to the terminal.

In the above scheme, the method further comprises: the server analyzes a contact information set corresponding to the terminal and a second contact information set corresponding to other terminals; the contact information corresponding to the other terminals is contained in the contact information set;

and establishing an incidence relation between the contact information set and the second contact information set to generate a third contact information set.

In the above scheme, the method further comprises: and when the maintenance condition is met, the server updates the contact information in the contact information set.

In the above solution, the updating, by the server, the contact information in the contact information set includes: judging whether repeated contact person identifications exist in the contact person information set or not; when the judgment result shows that repeated contact person identifications exist in the contact person information set, respectively obtaining communication frequencies corresponding to the repeated contact person identifications;

and when the contact person identification in the repeated contact person identifications is not communicated within a preset time range, determining that the contact person identification is invalid, and deleting the contact person information corresponding to the contact person identification.

The embodiment of the invention also provides a method for managing the contact information, which comprises the following steps: the terminal obtains and stores a first contact information set pushed by the server;

when a first query instruction containing a first contact person identifier is detected, judging whether the first contact person information set comprises the first contact person identifier;

when the judgment result is that the first contact person identification is not included in the first contact person information set, generating a second query instruction including the first contact person identification, and sending the second query instruction to the server; and obtaining a query result corresponding to the second query instruction from the server.

The embodiment of the invention provides a contact person information management method, a server and a terminal, wherein the server comprises: the device comprises a first communication unit, a first data processing unit and a first storage unit; the first communication unit is used for obtaining contact person information of a terminal; the terminal is also used for pushing the first contact information set to the terminal; the first data processing unit is used for generating a contact information set based on the contact information obtained by the first communication unit; the terminal is also used for counting a first contact person information set communicated with the terminal within a preset time range when the pushing condition is met, and enabling the first communication unit; the first storage unit is used for storing the contact person information obtained by the first communication unit and storing a contact person information set. Therefore, by adopting the technical scheme of the embodiment of the invention, the contact information set of the terminal is managed through the server; the server pushes a small amount of contact information to the terminal every other pushing period, and the terminal does not need to locally store and maintain a complete contact information set (namely an address book), so that a terminal user does not need to maintain the contact information set (namely the address book), and the operation and maintenance burden of the user is reduced; in the second aspect, the storage space of the server is far larger than that of the terminal, so that the situation that the contact information cannot be written in due to insufficient storage space of the terminal is avoided; on the other hand, for the situations of terminal loss, equipment replacement or equipment upgrade, backup and recovery operations on the contact person information set (namely, the communication rate) are not needed, the risk of losing the contact person information set (namely, the communication rate) is also avoided, and the user experience is greatly improved.

Drawings

Fig. 1 is a schematic hardware configuration diagram of an alternative mobile terminal implementing various embodiments of the present invention;

FIG. 2 is a diagram of a wireless communication system for the mobile terminal shown in FIG. 1;

FIG. 3 is a schematic diagram of a system architecture of an application of a contact information management method according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of a server according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present invention;

fig. 6 is a first flowchart of a method for managing contact information according to an embodiment of the present invention;

fig. 7 is a second flowchart of a method for managing contact information according to an embodiment of the present invention;

fig. 8 is a third flowchart illustrating a method for managing contact information according to an embodiment of the present invention;

fig. 9 is a fourth flowchart illustrating a method for managing contact information according to an embodiment of the present invention;

fig. 10 is a schematic specific flowchart of a method for managing contact information according to an embodiment of the present invention;

fig. 11 is a fifth flowchart illustrating a method for managing contact information according to an embodiment of the present invention;

the implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

A mobile terminal implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.

The mobile terminal may be implemented in various forms. For example, the terminal described in the present invention may include a mobile terminal such as a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a navigation device, and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. In the following, it is assumed that the terminal is a mobile terminal. However, it will be understood by those skilled in the art that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal in addition to elements particularly used for moving purposes.

Fig. 1 is a schematic hardware structure of an alternative mobile terminal implementing various embodiments of the present invention.

The mobile terminal 100 may include a wireless communication unit 110, an a/V (audio/video) input unit 120, a user input unit 130, a sensing unit 140, an output unit 150, a memory 160, an interface unit 170, a controller 180, and a power supply unit 190, etc. Fig. 1 illustrates a mobile terminal having various components, but it is to be understood that not all illustrated components are required to be implemented. More or fewer components may alternatively be implemented. Elements of the mobile terminal will be described in detail below.

The wireless communication unit 110 typically includes one or more components that allow radio communication between the mobile terminal 100 and a wireless communication system or network. For example, the wireless communication unit may include at least one of a broadcast receiving module 111, a mobile communication module 112, a wireless internet module 113, a short-range communication module 114, and a location information module 115.

The broadcast receiving module 111 receives a broadcast signal and/or broadcast associated information from an external broadcast management server via a broadcast channel. The broadcast channel may include a satellite channel and/or a terrestrial channel. The broadcast management server may be a server that generates and transmits a broadcast signal and/or broadcast associated information or a server that receives a previously generated broadcast signal and/or broadcast associated information and transmits it to a terminal. The broadcast signal may include a TV broadcast signal, a radio broadcast signal, a data broadcast signal, and the like. Also, the broadcast signal may further include a broadcast signal combined with a TV or radio broadcast signal. The broadcast associated information may also be provided via a mobile communication network, and in this case, the broadcast associated information may be received by the mobile communication module 112. The broadcast signal may exist in various forms, for example, it may exist in the form of an Electronic Program Guide (EPG) of Digital Multimedia Broadcasting (DMB), an Electronic Service Guide (ESG) of digital video broadcasting-handheld (DVB-H), and the like. The broadcast receiving module 111 may receive a signal broadcast by using various types of broadcasting systems. In particular, the broadcast receiving module 111 may receive digital broadcasting by using a digital broadcasting system such as a data broadcasting system of multimedia broadcasting-terrestrial (DMB-T), digital multimedia broadcasting-satellite (DMB-S), digital video broadcasting-handheld (DVB-H), forward link media (MediaFLO @), terrestrial digital broadcasting integrated service (ISDB-T), and the like. The broadcast receiving module 111 may be constructed to be suitable for various broadcasting systems that provide broadcast signals as well as the above-mentioned digital broadcasting systems. The broadcast signal and/or broadcast associated information received via the broadcast receiving module 111 may be stored in the memory 160 (or other type of storage medium).

The mobile communication module 112 transmits and/or receives radio signals to and/or from at least one of a base station (e.g., access point, node B, etc.), an external terminal, and a server. Such radio signals may include voice call signals, video call signals, or various types of data transmitted and/or received according to text and/or multimedia messages.

The wireless internet module 113 supports wireless internet access of the mobile terminal. The module may be internally or externally coupled to the terminal. The wireless internet access technology to which the module relates may include WLAN (wireless LAN) (Wi-Fi), Wibro (wireless broadband), Wimax (worldwide interoperability for microwave access), HSDPA (high speed downlink packet access), and the like.

The short-range communication module 114 is a module for supporting short-range communication. Some examples of short-range communication technologies include bluetooth (TM), Radio Frequency Identification (RFID), infrared data association (IrDA), Ultra Wideband (UWB), zigbee (TM), and the like.

The location information module 115 is a module for checking or acquiring location information of the mobile terminal. A typical example of the location information module is a GPS (global positioning system). According to the current technology, the GPS module 115 calculates distance information and accurate time information from three or more satellites and applies triangulation to the calculated information, thereby accurately calculating three-dimensional current location information according to longitude, latitude, and altitude. Currently, a method for calculating position and time information uses three satellites and corrects an error of the calculated position and time information by using another satellite. In addition, the GPS module 115 can calculate speed information by continuously calculating current position information in real time.

The a/V input unit 120 is used to receive an audio or video signal. The a/V input unit 120 may include a microphone 122, and the microphone 122 may receive sounds (audio data) via the microphone in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the mobile communication module 112 in case of a phone call mode. The microphone 122 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.

The user input unit 130 may generate key input data according to a command input by a user to control various operations of the mobile terminal. The user input unit 130 allows a user to input various types of information, and may include a keyboard, dome sheet, touch pad (e.g., a touch-sensitive member that detects changes in resistance, pressure, capacitance, and the like due to being touched), scroll wheel, joystick, and the like. In particular, when the touch pad is superimposed on the display unit 151 in the form of a layer, a touch screen may be formed.

The sensing unit 140 detects a current state of the mobile terminal 100 (e.g., an open or closed state of the mobile terminal 100), a position of the mobile terminal 100, presence or absence of contact (i.e., touch input) by a user with the mobile terminal 100, an orientation of the mobile terminal 100, acceleration or deceleration movement and direction of the mobile terminal 100, and the like, and generates a command or signal for controlling an operation of the mobile terminal 100. For example, when the mobile terminal 100 is implemented as a slide-type mobile phone, the sensing unit 140 may sense whether the slide-type phone is opened or closed. In addition, the sensing unit 140 can detect whether the power supply unit 190 supplies power or whether the interface unit 170 is coupled with an external device.

The interface unit 170 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The identification module may store various information for authenticating a user using the mobile terminal 100 and may include a User Identity Module (UIM), a Subscriber Identity Module (SIM), a Universal Subscriber Identity Module (USIM), and the like. In addition, a device having an identification module (hereinafter, referred to as an "identification device") may take the form of a smart card, and thus, the identification device may be connected with the mobile terminal 100 via a port or other connection means. The interface unit 170 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal and the external device.

In addition, when the mobile terminal 100 is connected with an external cradle, the interface unit 170 may serve as a path through which power is supplied from the cradle to the mobile terminal 100 or may serve as a path through which various command signals input from the cradle are transmitted to the mobile terminal. Various command signals or power input from the cradle may be used as signals for recognizing whether the mobile terminal is accurately mounted on the cradle. The output unit 150 is configured to provide output signals (e.g., audio signals, video signals, alarm signals, vibration signals, etc.) in a visual, audio, and/or tactile manner. The output unit 150 may include a display unit 151, an audio output module 152, an alarm unit 153, and the like.

The display unit 151 may display information processed in the mobile terminal 100. For example, when the mobile terminal 100 is in a phone call mode, the display unit 151 may display a User Interface (UI) or a Graphical User Interface (GUI) related to a call or other communication (e.g., text messaging, multimedia file downloading, etc.). When the mobile terminal 100 is in a video call mode or an image capturing mode, the display unit 151 may display a captured image and/or a received image, a UI or GUI showing a video or an image and related functions, and the like.

Meanwhile, when the display unit 151 and the touch pad are overlapped with each other in the form of a layer to form a touch screen, the display unit 151 may serve as an input device and an output device. The display unit 151 may include at least one of a Liquid Crystal Display (LCD), a thin film transistor LCD (TFT-LCD), an Organic Light Emitting Diode (OLED) display, a flexible display, a three-dimensional (3D) display, and the like. Some of these displays may be configured to be transparent to allow a user to view from the outside, which may be referred to as transparent displays, and a typical transparent display may be, for example, a TOLED (transparent organic light emitting diode) display or the like. Depending on the particular desired implementation, the mobile terminal 100 may include two or more display units (or other display devices), for example, the mobile terminal may include an external display unit (not shown) and an internal display unit (not shown). The touch screen may be used to detect a touch input pressure as well as a touch input position and a touch input area.

The audio output module 152 may convert audio data received by the wireless communication unit 110 or stored in the memory 160 into an audio signal and output as sound when the mobile terminal is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output module 152 may provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output module 152 may include a speaker, a buzzer, and the like.

The alarm unit 153 may provide an output to notify the mobile terminal 100 of the occurrence of an event. Typical events may include call reception, message reception, key signal input, touch input, and the like. In addition to audio or video output, the alarm unit 153 may provide output in different ways to notify the occurrence of an event. For example, the alarm unit 153 may provide an output in the form of vibration, and when a call, a message, or some other incoming communication (incomingmunication) is received, the alarm unit 153 may provide a tactile output (i.e., vibration) to inform the user thereof. By providing such a tactile output, the user can recognize the occurrence of various events even when the user's mobile phone is in the user's pocket. The alarm unit 153 may also provide an output notifying the occurrence of an event via the display unit 151 or the audio output module 152.

The memory 160 may store software programs and the like for processing and controlling operations performed by the controller 180, or may temporarily store data (e.g., a phonebook, messages, still images, videos, and the like) that has been or will be output. Also, the memory 160 may store data regarding various ways of vibration and audio signals output when a touch is applied to the touch screen.

The memory 160 may include at least one type of storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. Also, the mobile terminal 100 may cooperate with a network storage device that performs a storage function of the memory 160 through a network connection.

The controller 180 generally controls the overall operation of the mobile terminal. For example, the controller 180 performs control and processing related to voice calls, data communications, video calls, and the like. In addition, the controller 180 may include a multimedia module 181 for reproducing (or playing back) multimedia data, and the multimedia module 181 may be constructed within the controller 180 or may be constructed separately from the controller 180. The controller 180 may perform a pattern recognition process to recognize a handwriting input or a picture drawing input performed on the touch screen as a character or an image.

The power supply unit 190 receives external power or internal power and provides appropriate power required to operate various elements and components under the control of the controller 180.

The various embodiments described herein may be implemented in a computer-readable medium using, for example, computer software, hardware, or any combination thereof. For a hardware implementation, the embodiments described herein may be implemented using at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, a microprocessor, an electronic unit designed to perform the functions described herein, and in some cases, such embodiments may be implemented in the controller 180. For a software implementation, the implementation such as a process or a function may be implemented with a separate software module that allows performing at least one function or operation. The software codes may be implemented by software applications (or programs) written in any suitable programming language, which may be stored in the memory 160 and executed by the controller 180.

Up to this point, mobile terminals have been described in terms of their functionality. Hereinafter, a slide-type mobile terminal among various types of mobile terminals, such as a folder-type, bar-type, swing-type, slide-type mobile terminal, and the like, will be described as an example for the sake of brevity. Accordingly, the present invention can be applied to any type of mobile terminal, and is not limited to a slide type mobile terminal.

The mobile terminal 100 as shown in fig. 1 may be configured to operate with communication systems such as wired and wireless communication systems and satellite-based communication systems that transmit data via frames or packets.

A communication system in which a mobile terminal according to the present invention is operable will now be described with reference to fig. 2.

Such communication systems may use different air interfaces and/or physical layers. For example, the air interface used by the communication system includes, for example, Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), and Universal Mobile Telecommunications System (UMTS) (in particular, Long Term Evolution (LTE)), global system for mobile communications (GSM), and the like. By way of non-limiting example, the following description relates to a CDMA communication system, but such teachings are equally applicable to other types of systems.

Referring to fig. 2, the CDMA wireless communication system may include a plurality of mobile terminals 100, a plurality of Base Stations (BSs) 270, Base Station Controllers (BSCs) 275, and a Mobile Switching Center (MSC) 280. The MSC280 is configured to interface with a Public Switched Telephone Network (PSTN) 290. The MSC280 is also configured to interface with a BSC275, which may be coupled to the base station 270 via a backhaul. The backhaul may be constructed according to any of several known interfaces including, for example, E1/T1, ATM, IP, PPP, frame Relay, HDSL, ADSL, or xDSL. It will be understood that a system as shown in fig. 2 may include multiple BSCs 275.

Each BS270 may serve one or more sectors (or regions), each sector covered by a multi-directional antenna or an antenna pointing in a particular direction being radially distant from the BS 270. Alternatively, each partition may be covered by two or more antennas for diversity reception. Each BS270 may be configured to support multiple frequency allocations, with each frequency allocation having a particular frequency spectrum (e.g., 1.25MHz,5MHz, etc.).

The intersection of partitions with frequency allocations may be referred to as a CDMA channel. The BS270 may also be referred to as a Base Transceiver Subsystem (BTS) or other equivalent terminology. In such a case, the term "base station" may be used to generically refer to a single BSC275 and at least one BS 270. The base stations may also be referred to as "cells". Alternatively, each sector of a particular BS270 may be referred to as a plurality of cell sites.

As shown in fig. 2, a Broadcast Transmitter (BT)295 transmits a broadcast signal to the mobile terminal 100 operating within the system. A broadcast receiving module 111 as shown in fig. 1 is provided at the mobile terminal 100 to receive a broadcast signal transmitted by the BT 295. In fig. 2, several Global Positioning System (GPS) satellites 300 are shown. The satellite 300 assists in locating at least one of the plurality of mobile terminals 100.

In fig. 2, a plurality of satellites 300 are depicted, but it is understood that useful positioning information may be obtained with any number of satellites. The GPS module 115 as shown in fig. 1 is generally configured to cooperate with satellites 300 to obtain desired positioning information. Other techniques that can track the location of the mobile terminal may be used instead of or in addition to GPS tracking techniques. In addition, at least one GPS satellite 300 may selectively or additionally process satellite DMB transmission.

As a typical operation of the wireless communication system, the BS270 receives reverse link signals from various mobile terminals 100. The mobile terminal 100 is generally engaged in conversations, messaging, and other types of communications. Each reverse link signal received by a particular base station 270 is processed within the particular BS 270. The obtained data is forwarded to the associated BSC 275. The BSC provides call resource allocation and mobility management functions including coordination of soft handoff procedures between BSs 270. The BSCs 275 also route the received data to the MSC280, which provides additional routing services for interfacing with the PSTN 290. Similarly, the PSTN290 interfaces with the MSC280, the MSC interfaces with the BSCs 275, and the BSCs 275 accordingly control the BS270 to transmit forward link signals to the mobile terminal 100.

Based on the above mobile terminal hardware structure and communication system, the present invention provides various embodiments of the method.

FIG. 3 is a schematic diagram of a system architecture of an application of a contact information management method according to an embodiment of the present invention; as shown in fig. 3, the system architecture for implementing the contact information management method according to the embodiment of the present invention includes a server 31 and a terminal 32. The server 31 may be a cloud server or a cloud server cluster; the terminal 32 may specifically be a terminal with a communication function, such as a mobile phone. In the embodiments of the present invention, the server 31 is configured to store and manage a contact information set (e.g., an address book) of the terminal 32, periodically push contact information that has recently communicated with the terminal to the terminal 32 and store the contact information locally in the terminal 32, that is, the terminal 32 only stores a certain amount of contact information locally, but not complete contact information. In addition, the server 31 regularly maintains the contact information of the terminal 32, and deletes the invalid contact information, so that a terminal user is not required to maintain a contact information set (namely an address list), and the operation and maintenance burden of the user is reduced; the backup and recovery operation of the contact person information set (namely the communication rate) is not needed, the risk of losing the contact person information set (namely the communication rate) is avoided, and the user experience is greatly improved.

Example one

The embodiment of the invention provides a server. FIG. 4 is a schematic diagram of a server according to an embodiment of the present invention; as shown in fig. 4, the server includes: a first communication unit 311, a first data processing unit 313, and a first storage unit 312; wherein the content of the first and second substances,

the first communication unit 311 is configured to obtain contact information of a terminal; the terminal is also used for pushing the first contact information set to the terminal;

the first data processing unit 313 is configured to generate a contact information set based on the contact information obtained by the first communication unit 311; the first communication unit 311 is further configured to count a first contact information set communicated with the terminal within a preset time range when the push condition is met, and enable the first communication unit;

the first storage unit 312 is configured to store the contact information obtained by the first communication unit 311, and store a contact information set.

Specifically, in this embodiment, the first communication unit 311 is configured to obtain contact information communicated with a terminal when the terminal performs communication; or obtaining the contact information input by the terminal.

As another embodiment, the first data processing unit 313 is further configured to analyze the contact information set of the terminal and the second contact information sets of other terminals; the contact information corresponding to the other terminals is contained in the contact information set; and establishing an incidence relation between the contact information set and the second contact information set to generate a third contact information set.

Based on the above embodiment, the first communication unit 311 is further configured to receive a second query instruction sent by the terminal; the second query instruction comprises a first contact person identifier; the terminal is also used for sending the query result to the terminal;

the first data processing unit 313 is further configured to query the contact information set, and determine whether the contact information set includes the first contact identifier; and when the judgment result is that the contact information set includes the first contact identifier, obtaining first contact information corresponding to the first contact identifier, generating a query result based on the first contact information, and enabling the first communication unit 311.

Further, the first data processing unit 313 is further configured to, when the determination result is that the first contact identifier is not included in the contact information set, query the third contact information set, and determine whether the first contact identifier is included in the third contact information set; when the judgment result is that the third contact information set includes the first contact identifier, obtaining first contact information corresponding to the first contact identifier, generating a query result based on the first contact information, and enabling the first communication unit 311;

the first communication unit 311 is further configured to send the query result to the terminal.

In another embodiment, the first data processing unit 313 is further configured to perform an update process on the contact information in the contact information set when the maintenance condition is satisfied.

Specifically, the first data processing unit 313 is configured to determine whether a duplicate contact identifier exists in the contact information set; when the judgment result shows that repeated contact person identifications exist in the contact person information set, respectively obtaining communication frequencies corresponding to the repeated contact person identifications; and when the contact person identification in the repeated contact person identifications is not communicated within a preset time range, determining that the contact person identification is invalid, and deleting the contact person information corresponding to the contact person identification.

In the embodiment of the present invention, the first data Processing Unit 313 in the server may be implemented by a Central Processing Unit (CPU), a Digital Signal Processor (DSP), or a Programmable Gate Array (FPGA) in the server in practical applications; the first communication unit 311 in the server may be implemented by a transceiver antenna in the server in practical applications; the first storage unit 312 in the server can be implemented by a memory in the server in practical applications.

The description of each processing unit in the server of the present embodiment can be understood by referring to the related description of the subsequent method embodiments. Each processing unit in the server according to the embodiment of the present invention may be implemented by an analog circuit that implements the functions described in the embodiment of the present invention, or may be implemented by running software that executes the functions described in the embodiment of the present invention on an intelligent terminal.

Example two

The embodiment of the invention also provides the terminal. Fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present invention; as shown in fig. 5, the terminal includes: a second communication unit 321, a second storage unit 322, and a second data processing unit 323; wherein the content of the first and second substances,

the second communication unit 321 is configured to obtain a first contact information set pushed by a server; the server is also used for sending the second query instruction to the server; the server is further used for obtaining a query result corresponding to the second query instruction;

the second storage unit 322 is configured to store the first contact information set obtained by the second communication unit 321;

the second data processing unit 323 is configured to, when a first query instruction including a first contact identifier is detected, determine whether the first contact information set includes the first contact identifier; and when the determination result is that the first contact information set does not include the first contact identifier, generating a second query instruction including the first contact identifier, and enabling the second communication unit 321.

In this embodiment, the second data processing unit 323 is configured to, when an input operation representing the first contact identifier is detected, generate a first query instruction based on the input operation; or when a communication request corresponding to the first contact identification is detected, generating a first query instruction based on the communication request.

As another embodiment, the second data processing unit 323 is further configured to, when the terminal performs communication, obtain contact information corresponding to the communication; or detecting the input operation of the contact information to obtain the input contact information;

correspondingly, the second communication unit 321 is configured to send the contact information obtained by the second data processing unit 323 to the server.

In the embodiment of the present invention, the second data processing unit 323 in the terminal may be implemented by a CPU, a DSP, or an FPGA in the terminal in practical application; the second communication unit 321 in the terminal may be implemented by a transceiver antenna in the server in practical application; the second storage unit 322 in the terminal may be implemented by a memory in the server in practical applications.

The description of each processing unit in the terminal of the present embodiment can be understood by referring to the related description of the subsequent method embodiments. Each processing unit in the server according to the embodiment of the present invention may be implemented by an analog circuit that implements the functions described in the embodiment of the present invention, or may be implemented by running software that executes the functions described in the embodiment of the present invention on an intelligent terminal.

EXAMPLE III

The embodiment of the invention also provides a contact person information management method, which is applied to the server. Fig. 6 is a first flowchart of a method for managing contact information according to an embodiment of the present invention; as shown in fig. 6, the method includes:

step 601: the server obtains and stores the contact information of the terminal and generates a contact information set.

Step 602: and when the pushing condition is met, the server counts a first contact information set communicated with the terminal within a preset time range, and pushes the first contact information set to the terminal.

In this embodiment, the server may specifically be a cloud server. The server has a function of managing contact information of the terminal.

In this embodiment, the server obtains and stores contact information of the terminal. The method comprises the following steps: when a terminal communicates, the server obtains and stores contact information communicated with the terminal; or the server obtains and stores the contact information input by the terminal.

Step 601 is an adding process of the contact information of the terminal. As an embodiment, from the adding timing, the adding manner of the contact information of the terminal may include: the active input of the terminal and the active acquisition of the server when the terminal communicates. Specifically, when a terminal carries out a communication request (including an incoming call request or an outgoing call request), the terminal sends contact information corresponding to the communication request to a server; the contact information obtained by the server may be a phone number, or a phone number and a contact name, and specifically, whether the contact name corresponding to the phone number is stored locally in the terminal is checked. Or the terminal actively creates contact information and inputs the contact name and the corresponding telephone number; sending the input contact information to a server; and the server acquires and stores the contact information sent by the terminal.

As another embodiment, the adding manner of the contact information of the terminal may include: active input of the terminal and searching of the association mode. The active input mode of the terminal may refer to the foregoing description, and is not described herein again. For the searching method of the association method, the concept of hiding the contact is introduced first.

As an embodiment, the method further comprises: the server analyzes a contact information set corresponding to the terminal and a second contact information set corresponding to other terminals; the contact information corresponding to the other terminals is contained in the contact information set; and establishing an incidence relation between the contact information set and the second contact information set to generate a third contact information set. Specifically, the server manages contact information sets of a plurality of terminals, for example, a contact information set 1 of a terminal 1 including "zhangsan" and a contact information set 2 of a terminal 2 including "liquan"; when the 'Liquan' is used as a contact in the terminal 1 of the 'Zhang three', namely the telephone number of the 'Liquan' is stored in the contact information set 1, the server establishes the association relationship between the contact information set 1 and the contact information set 2, and generates a third contact information set, wherein the third contact information set is called a hidden contact. The hidden contact may be understood as a "contact of a contact".

Based on the above description, the search of the association manner is to search the third contact information set based on the obtained partial contact information (specifically, the phone number); and when the third contact information set comprises the partial contact information (such as the telephone number), acquiring complete contact information corresponding to the partial contact information and adding the complete contact information to a contact information set corresponding to the terminal.

In step 602 of this embodiment, the condition satisfying the pushing condition may be a condition satisfying a pushing period. Specifically, the server may pre-configure a push period, and when the push period is up, determine that a push condition is satisfied, and execute a subsequent push process.

Specifically, the server counts all contact information communicated with the terminal within a preset time range to generate a first contact information set; the communication with the terminal in the preset time range includes, but is not limited to, communication in a telephone mode, communication in a short message mode, and the like, and may also be communication through other communication tools. Wherein the preset time range is a time range between another time point before the time point to be pushed. The preset time range can be a fixed duration, namely the preset time range is fixed and unchangeable; for example, if N pieces of contact information can be accommodated in a first contact information set to be pushed, the N pieces of contact information can be obtained from near to far according to communication time to generate the first contact information set, and the preset time range corresponds to the time range of the N pieces of contact information; it is to be understood that, in the present embodiment, the preset time range is variable.

In this embodiment, the server pushes the contact information set which is communicated with the terminal within a preset time range, which may be understood as that the server pushes the contact information which is recently contacted by the terminal to the terminal. In this embodiment, the contact information in the first contact information set may be sorted in multiple ways: the communication time with the terminal is sorted from near to far, the communication frequency with the terminal is sorted from high to low, or the communication duration with the terminal is sorted from high to low, and the like. Therefore, the server pushes a small amount of contact information to the terminal every other pushing period, the terminal does not need to locally store and maintain a complete contact information set (namely an address book), and the server is used for managing the contact information of the terminal user, so that the terminal user does not need to maintain the contact information set (namely the address book), and the operation and maintenance burden of the user is reduced; in the second aspect, the storage space of the server is far larger than that of the terminal, so that the situation that the contact information cannot be written in due to insufficient storage space of the terminal is avoided; on the other hand, for the situations of terminal loss, equipment replacement or equipment upgrade, backup and recovery operations on the contact person information set (namely, the communication rate) are not needed, the risk of losing the contact person information set (namely, the communication rate) is also avoided, and the user experience is greatly improved.

Example four

The embodiment of the invention also provides a contact person information management method, which is applied to the server. Fig. 7 is a second flowchart of a method for managing contact information according to an embodiment of the present invention; as shown in fig. 7, the method includes:

step 701: the server obtains and stores the contact information of the terminal and generates a contact information set.

Step 702: and when the pushing condition is met, the server counts a first contact information set communicated with the terminal within a preset time range, and pushes the first contact information set to the terminal.

Step 703: the server analyzes a contact information set corresponding to the terminal and a second contact information set corresponding to other terminals; and the contact information corresponding to the other terminals is contained in the contact information set.

Step 704: and establishing an incidence relation between the contact information set and the second contact information set to generate a third contact information set.

Step 701 is an adding process of the contact information of the terminal. As an embodiment, from the adding timing, the adding manner of the contact information of the terminal may include: the active input of the terminal and the active acquisition of the server when the terminal communicates. Specifically, when a terminal carries out a communication request (including an incoming call request or an outgoing call request), the terminal sends contact information corresponding to the communication request to a server; the contact information obtained by the server may be a phone number, or a phone number and a contact name, and specifically, whether the contact name corresponding to the phone number is stored locally in the terminal is checked. Or the terminal actively creates contact information and inputs the contact name and the corresponding telephone number; sending the input contact information to a server; and the server acquires and stores the contact information sent by the terminal.

As another embodiment, the adding manner of the contact information of the terminal may include: active input of the terminal and searching of the association mode. The active input mode of the terminal may refer to the foregoing description, and is not described herein again. For the searching method of the association method, the concept of hiding the contact, i.e. the description of step 703 and step 704, is introduced first. Specifically, the server manages contact information sets of a plurality of terminals, for example, a contact information set 1 of a terminal 1 including "zhangsan" and a contact information set 2 of a terminal 2 including "liquan"; when the 'Liquan' is used as a contact in the terminal 1 of the 'Zhang three', namely the telephone number of the 'Liquan' is stored in the contact information set 1, the server establishes the association relationship between the contact information set 1 and the contact information set 2, and generates a third contact information set, wherein the third contact information set is called a hidden contact. The hidden contact may be understood as a "contact of a contact".

In step 702 of this embodiment, the condition satisfying the pushing condition may be a pushing period condition satisfying. Specifically, the server may pre-configure a push period, and when the push period is up, determine that a push condition is satisfied, and execute a subsequent push process.

Based on the descriptions of the fourth to fifth embodiments, in combination with the application scenario of the contact information query, the method of this embodiment further includes: the server receives a second query instruction sent by the terminal; the second query instruction comprises a first contact person identifier;

inquiring the contact person information set, and judging whether the contact person information set comprises the first contact person identification;

and when the judgment result is that the contact information set comprises the first contact identification, obtaining first contact information corresponding to the first contact identification, generating a query result based on the first contact information, and sending the query result to the terminal.

Further, when the judgment result is that the first contact identifier is not included in the contact information set, the method further includes:

inquiring the third contact information set, and judging whether the third contact information set comprises the first contact identification;

and when the judgment result is that the third contact information set comprises the first contact identification, obtaining first contact information corresponding to the first contact identification, generating a query result based on the first contact information, and sending the query result to the terminal.

An application scenario of the contact information query in the embodiment of the present invention is specifically described in the following through an embodiment five.

EXAMPLE five

Based on the description of the fourth embodiment and the fifth embodiment, the embodiment of the invention further provides a contact information management method, and the method is applied to the server. Fig. 8 is a third flowchart illustrating a method for managing contact information according to an embodiment of the present invention; as shown in fig. 8, the method includes:

step 801: the server receives a second query instruction sent by the terminal; inquiring a contact information set; the second query instruction comprises a first contact identification.

Step 802: judging whether the contact person information set comprises the first contact person identification or not; when the judgment result is yes, step 803 is executed; if the determination result is negative, steps 804 to 807 are performed.

Step 803: and acquiring first contact person information corresponding to the first contact person identification, generating a query result based on the first contact person information, and sending the query result to the terminal.

Step 804: a third contact information set is queried.

Step 805: judging whether the third contact information set comprises the first contact identification or not; if yes, go to step 806; when the determination result is negative, step 807 is executed: and sending information representing the query failure to the terminal.

Step 806: and acquiring first contact person information corresponding to the first contact person identification, generating a query result based on the first contact person information, and sending the query result to the terminal.

In step 801 of this embodiment, the server receives a second query instruction of the terminal; the second query instruction is sent after the terminal queries the first contact information based on the first contact information set stored locally and does not query the first contact information, namely the terminal queries the first contact information based on the first contact information set stored locally and sends the second query instruction to the server after determining that the first contact information is not stored locally; the second query instruction comprises a first contact person identifier; the first contact identification may specifically be part of the first contact information, for example at least part of a telephone number, a contact name, or at least one word or letter of a contact name, etc.

In step 802 of this embodiment, the server maintains a complete contact information set corresponding to the terminal; after receiving the second query instruction, querying whether the contact information set includes the first contact identifier, that is, determining whether the first contact identifier exists in the maintained address book. When it is determined that the contact information set includes the first contact identifier, that is, the first contact identifier exists in the address book maintained in the server, step 803 is executed to directly obtain first contact information corresponding to the first contact identifier, and a query result is generated. When the first contact is identified as a partial phone number or a partial contact name, the contact information obtained by querying may include a plurality of pieces, and based on this, the obtained first contact information may be a contact information list. Further, the query result containing the first contact information is sent to the terminal.

When it is determined that the first contact identifier is not included in the contact information set, that is, the first contact identifier does not exist in the address book maintained in the server, steps 804 to 807 are executed, and a process of querying a hidden contact and obtaining first contact information corresponding to the first contact identifier is performed. Specifically, a third contact information set serving as a "hidden contact" is queried based on the first contact identifier, and the third contact information set may refer to the descriptions in embodiment four and embodiment five, which are not described herein again. It is understood that in steps 804 to 805, the server queries "contact of contact", and determines whether the first contact identifier is in "address book of contact". When it is determined that the third contact information set includes the first contact identifier, that is, the first contact identifier is in the "address book of a contact", step 806 is executed to obtain the first contact information corresponding to the first contact identifier from the third contact information set, generate a query result, and send the query result to the terminal. When it is determined that the third contact information set does not include the first contact identifier, that is, the first contact identifier is not in the "address book of a contact", indicating that the contact information corresponding to the first contact identifier is not found, step 806 is executed, and information of a query failure is sent to the terminal.

By adopting the technical scheme of the embodiment of the invention, the server pushes a small amount of contact information to the terminal every other pushing period, the terminal does not need to locally store and maintain a complete contact information set (namely an address book), and the server is used for managing the contact information of the terminal user, so that the terminal user does not need to maintain the contact information set (namely the address book), and the operation and maintenance burden of the user is reduced; in the second aspect, the storage space of the server is far larger than that of the terminal, so that the situation that the contact information cannot be written in due to insufficient storage space of the terminal is avoided; on the other hand, for the situations of terminal loss, equipment replacement or equipment upgrade, backup and recovery operations on the contact person information set (namely, the communication rate) are not needed, the risk of losing the contact person information set (namely, the communication rate) is also avoided, and the user experience is greatly improved.

EXAMPLE six

The embodiment of the invention also provides a contact person information management method, which is applied to the server. Fig. 9 is a fourth flowchart illustrating a method for managing contact information according to an embodiment of the present invention; as shown in fig. 9, the method includes:

step 901: the server obtains and stores the contact information of the terminal and generates a contact information set.

Step 902: and when the pushing condition is met, the server counts a first contact information set communicated with the terminal within a preset time range, and pushes the first contact information set to the terminal.

Step 903: and when the maintenance condition is met, the server updates the contact information in the contact information set.

Step 901 is an adding process of the contact information of the terminal. As an embodiment, from the adding timing, the adding manner of the contact information of the terminal may include: the active input of the terminal and the active acquisition of the server when the terminal communicates. Specifically, when a terminal carries out a communication request (including an incoming call request or an outgoing call request), the terminal sends contact information corresponding to the communication request to a server; the contact information obtained by the server may be a phone number, or a phone number and a contact name, and specifically, whether the contact name corresponding to the phone number is stored locally in the terminal is checked. Or the terminal actively creates contact information and inputs the contact name and the corresponding telephone number; sending the input contact information to a server; and the server acquires and stores the contact information sent by the terminal.

In step 902 of this embodiment, the condition satisfying the pushing condition may be a pushing period condition. Specifically, the server may pre-configure a push period, and when the push period is up, determine that a push condition is satisfied, and execute a subsequent push process.

In this embodiment, the server periodically updates the stored contact information set, that is, executes the process of step 903. However, in the present embodiment, the execution condition of step 903 is not limited to be after step 902 when the maintenance condition is actually satisfied.

In this embodiment, the updating, by the server, the contact information in the contact information set includes: judging whether repeated contact person identifications exist in the contact person information set or not;

when the judgment result shows that repeated contact person identifications exist in the contact person information set, respectively obtaining communication frequencies corresponding to the repeated contact person identifications;

Specifically, the server may configure a maintenance period in advance, and when the configured maintenance period is up, it is determined that the maintenance condition is satisfied. When the maintenance cycle time is up, the server checks a contact information set corresponding to the terminal and inquires whether repeated contact identification exists; here, the repeated contact identification of the query may be a contact name, or a phone number, or the like. When the contact information set is checked to have repeated contact identifications, the contact information set indicates that the stored contact information may be repeated or different telephone numbers of the same stored contact. Based on this, in this embodiment, the corresponding contact information is updated based on the communication frequency corresponding to the contact identifier. For example, within a preset time range, the communication frequency corresponding to the repeated contact identifier is zero, that is, when the contact identifier does not perform any communication within the preset time range, it indicates that the phone number corresponding to the contact identifier may have failed, and then the contact information corresponding to the contact identifier may be deleted. If the contact person identification in the repeated contact person identifications is communicated within a preset time range, the contact person identification can be determined to be valid, and the contact person information corresponding to the contact person identification is reserved. The preset time range can be set according to personal conditions.

Fig. 10 is a schematic specific flowchart of a method for managing contact information according to an embodiment of the present invention; referring to fig. 10, a manner of processing the update of the stored contact information set by the server may be shown, where the method includes:

step 1001: the server sets a maintenance period timer Tw and a push period Ts; when the maintenance period timer is up, the server checks and updates the stored contact information set; and when the pushing period Ts is up, the server pushes the first contact information set which is communicated recently to the terminal.

Step 1002: determining whether maintenance is due based on the maintenance period timer Tw; if yes, executing step 1003 to step 1007; if the result of the determination is negative, the maintenance process is skipped and the push process from step 1008 to step 1012 is directly performed.

Step 1003: judging whether a contact person with a repeated mark exists in a contact person information set stored by the server, namely judging whether the contact person with the repeated mark exists in the contact person information set; if yes, executing steps 1004 to 1007; when the result of the determination is negative, step 1008 is performed.

Step 1004: inquiring the latest incoming call time of each repeatedly marked contact person, namely inquiring the latest communication time of each repeatedly marked contact person; step 1005 is further performed.

Step 1005: reading overdue clearing time S set by a user; the overdue clearing time S shows that if the latest incoming call time of the contact exceeds the overdue clearing time S, the contact is determined to be not contacted for a long time, and the contact is determined to be a failed contact; correspondingly, if the latest incoming call time of the contact does not exceed the overdue clearing time S, the contact can be determined to be still a valid contact. Step 1006 is further performed: judging whether the time interval is greater than S, and executing the step 1007 when the judgment result is yes; when the result of the determination is negative, step 1008 is performed.

Step 1007: the repeatedly marked contact is cleared. The regular update process of the contact information set by the server is completed.

The following is a process in which the server periodically pushes the first set of contact information that was recently contacted to the terminal.

Step 1008: judging whether the pushing is due or not, and if so, executing the step 1009; when the result of the judgment is negative, no operation is performed. Judging whether the pushing is due or not, and judging whether the pushing period Ts is up or not; when the pushing period Ts is judged to be up, determining due pushing; when it is determined that the push period Ts time is not up, it is determined that push has not expired.

Step 1009: and acquiring the length L of the user-defined common contact and the recent contact list. Here, the length L of the list may be set in advance by a user; the length L of the list indicates the number of the contact information in the contact information set to be pushed to the terminal by the server.

Step 1010: and ordering the contacts according to the activity degree from high to low. The server acquires contact information communicated with the terminal within a preset time range, sorts the acquired contact information according to the activity degree, and acquires a common contact list after sorting; the active procedure may be defined as a communication frequency, i.e., a number of communications. The preset time range can be a time range from the current time point to the last pushing period; of course, the preset time range may be set to any value.

Step 1011: and sorting the contacts according to the last contact time interval from short to long. Sequencing the acquired contact information communicated with the terminal within the preset time range according to contact time intervals, and obtaining a recent contact list after sequencing; the contact time interval may be a communication duration.

Step 1012: and pushing the common contact and the recent contact list to the user.

EXAMPLE seven

The embodiment of the invention also provides a contact person information management method, which is applied to the terminal. Fig. 11 is a fifth flowchart illustrating a method for managing contact information according to an embodiment of the present invention; as shown in fig. 11, the method includes:

step 1101: the terminal obtains and stores the first contact information set pushed by the server.

Step 1102: when a first query instruction containing a first contact person identifier is detected, whether the first contact person identifier is included in the first contact person information set is judged.

Step 1103: and when the judgment result shows that the first contact person information set does not comprise the first contact person identification, generating a second query instruction comprising the first contact person identification, and sending the second query instruction to the server.

Step 1104: and obtaining a query result corresponding to the second query instruction from the server.

In this embodiment, the terminal may specifically be a mobile phone or other terminal. The terminal can run an application; the application provides an interface for searching and displaying contacts; the application stores a certain amount of contact information locally, namely an address list in the application, so that time delay caused by network access when a user accesses the contact is reduced; the contact information stored locally by the application is pushed by the server. The application provides a communication interface; accessing a server through the communication interface to inquire the contact person; meanwhile, the server also pushes the contact information set through the communication interface.

Based on the above description, in step 1101, the terminal periodically receives the first set of contact information pushed by the server and stores the first set of contact information locally. The contact information in the first set of contact information may be the most recently used contact information.

In step 1102 of this embodiment, the detecting a first query instruction including a first contact identifier includes: when an input operation representing the first contact person identification is detected, generating a first query instruction based on the input operation; or when a communication request corresponding to the first contact identification is detected, generating a first query instruction based on the communication request.

Specifically, as an embodiment, when a user inputs a first contact identifier (for example, a contact name, at least one word of the contact name, or a mobile phone number) for query, the terminal queries a first locally stored contact information set. As another embodiment, when the user makes a communication of the first contact identification (e.g., receives an incoming call request or requests an outgoing call), the terminal queries a locally stored first set of contact information.

In this embodiment step 1103, it is determined whether a first contact information set stored locally includes the first contact identifier; and when the judgment result is that the first contact person information set stored locally comprises the first contact person identification, directly obtaining the first contact person information corresponding to the first contact person identification. And when the judgment result is that the first contact person identification is not included in the locally stored first contact person information set, generating a second query instruction, and sending the second query instruction to the server so as to query the first contact person information corresponding to the first contact person identification through the contact person information set stored in the server. Further, step 1104 is performed: and obtaining a query result corresponding to the second query instruction from the server.

In this embodiment, after the terminal obtains the query result from the first contact information set stored locally or the terminal obtains the query result from the server, the terminal displays the query result, that is, the terminal displays the first contact information obtained by the query.

As another embodiment, the method further comprises: when the terminal communicates, acquiring contact person information corresponding to the communication, and sending the contact person information to the server; or the terminal detects the input operation of the contact information, obtains the input contact information and sends the input contact information to the server.

Specifically, the above embodiment is an adding process of the contact information of the terminal. Specifically, when a terminal carries out a communication request (including an incoming call request or an outgoing call request), the terminal sends contact information corresponding to the communication request to a server; the contact information may be a phone number, or a phone number and a contact name, and specifically, whether the contact name corresponding to the phone number is stored locally in the terminal is checked. Or the terminal actively creates contact information and inputs the contact name and the corresponding telephone number; and sending the input contact information to a server.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Alternatively, the integrated unit of the present invention may be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as a separate product. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic or optical disk, or various other media that can store program code.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims

1. A server, characterized in that the server comprises: the device comprises a first communication unit, a first data processing unit and a first storage unit; wherein the content of the first and second substances,

the first communication unit is used for acquiring contact information of the terminal when the terminal carries out communication or receives input operation; the terminal is also used for pushing a first contact information set to the terminal;

2. The server according to claim 1, wherein the first data processing unit is further configured to analyze the contact information set of the terminal and the second contact information sets of other terminals; the contact information corresponding to the other terminals is contained in the contact information set; and establishing an incidence relation between the contact information set and the second contact information set to generate a third contact information set.

3. The server according to claim 1, wherein the first data processing unit is further configured to perform update processing on the contact information in the contact information set when a maintenance condition is satisfied.

4. The server according to claim 3, wherein the first data processing unit is configured to determine whether there is a duplicate contact identifier in the contact information set; when the judgment result shows that repeated contact person identifications exist in the contact person information set, respectively obtaining communication frequencies corresponding to the repeated contact person identifications; and when the contact person identification in the repeated contact person identifications is not communicated within a preset time range, determining that the contact person identification is invalid, and deleting the contact person information corresponding to the contact person identification.

5. A terminal, characterized in that the terminal comprises: the second communication unit, the second storage unit and the second data processing unit; wherein the content of the first and second substances,

the second communication unit is used for acquiring a first contact information set which is pushed by the server and is communicated with the terminal within a preset time range; the server is also used for sending a second query instruction to the server; the server is further used for obtaining a query result corresponding to the second query instruction;

6. A method for managing contact information, the method comprising:

when a terminal communicates or receives input operation, a server obtains and stores contact information of the terminal to generate a contact information set;

7. The method of claim 6, further comprising: the server analyzes a contact information set corresponding to the terminal and a second contact information set corresponding to other terminals; the contact information corresponding to the other terminals is contained in the contact information set;

8. The method of claim 6, further comprising: and when the maintenance condition is met, the server updates the contact information in the contact information set.

9. The method of claim 8, wherein the server performs an update process on the contact information in the contact information set, comprising:

judging whether repeated contact person identifications exist in the contact person information set or not;

10. A method for managing contact information, the method comprising:

the method comprises the steps that a terminal obtains and stores a first contact information set which is pushed by a server and is communicated with the terminal within a preset time range;

when the judgment result is that the first contact person identification is not included in the first contact person information set, generating a second query instruction including the first contact person identification, and sending the second query instruction to the server;

and obtaining a query result corresponding to the second query instruction from the server.