CN104580637A - Telephone number marking method, terminal and cloud server - Google Patents
Telephone number marking method, terminal and cloud server Download PDFInfo
- Publication number
- CN104580637A CN104580637A CN201410840035.6A CN201410840035A CN104580637A CN 104580637 A CN104580637 A CN 104580637A CN 201410840035 A CN201410840035 A CN 201410840035A CN 104580637 A CN104580637 A CN 104580637A
- Authority
- CN
- China
- Prior art keywords
- phone numbers
- phone number
- destination
- phone
- contact
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Landscapes
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a telephone number marking method, a terminal and a cloud server, and belongs to the field of internet. The method comprises the following steps: receiving prompt information carrying a target telephone number, wherein the prompt information is generated by the cloud server based on validity states of telephone numbers of a plurality of contact persons stored in the terminal, and the target telephone number is an invalid telephone number; searching the target telephone number from the telephone numbers of the contact persons; marking the target telephone number based on the prompt information. According to the telephone number marking method disclosed by the invention, the target telephone number is marked to prompt a user to delete or update the target telephone number, thereby improving the accuracy of the stored telephone numbers.
Description
Technical field
The disclosure relates to internet arena, particularly relates to a kind of telephone number labeling method, terminal and Cloud Server.
Background technology
Along with the fast development of the Internet, user can the telephone number of storing contact in the address list list in terminal.Communicated with this contact person by the telephone number stored.
And once the telephone number of contact person changes, and contact person does not notify this user in time, or after contact person notifies user, user forgets the telephone number of the contact person stored in more new terminal, especially for the contact person that contact frequency is lower, user is difficult to find that the telephone number of this contact person is incorrect, causes the telephone number accuracy that stores in address list list lower.
Summary of the invention
For overcoming Problems existing in correlation technique, present disclose provides a kind of telephone number labeling method, terminal and Cloud Server.Described technical scheme is as follows:
According to the first aspect of disclosure embodiment, provide a kind of telephone number labeling method, described method comprises:
Receive the information of carrying destination phone numbers, the state of validity of multiple contact phone numbers that described information is stored based on terminal by Cloud Server generates, and described destination phone numbers is inactive phone number;
Described destination phone numbers is searched from described multiple contact phone number;
Based on described information, described destination phone numbers is marked.
Alternatively, described inactive phone number is discarded telephone number or the old telephone number needing replacing.
Alternatively, described based on described information, described destination phone numbers is marked, comprising:
When described information is for discarded telephone number information, the first mark is carried out to described destination phone numbers.
Alternatively, described based on described information, described destination phone numbers is marked, comprising:
When described information also carries new phone number corresponding to described destination phone numbers, based on described new phone number, the second mark is carried out to described destination phone numbers.
Alternatively, described based on described new phone number, after the second mark is carried out to described destination phone numbers, also comprise:
When receive to described second mark check instruction time, described new phone number is shown;
When receiving the replacement instruction to described destination phone numbers, described destination phone numbers is replaced with described new phone number.
Alternatively, described method also comprises:
When receiving the renewal instruction of subscriber directory number, number update request corresponding to subscriber directory number is sent to described Cloud Server, user's new phone number and user account is carried in described number update request, make described Cloud Server based on described user account, the described subscriber directory number stored is replaced with described user's new phone number.
According to the second aspect of disclosure embodiment, provide a kind of telephone number labeling method, described method comprises:
Obtain the address list that each user account is corresponding;
Judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that described user account is corresponding, described destination phone numbers is inactive phone number;
When described multiple contact phone number comprises destination phone numbers, generate the information comprising described destination phone numbers;
Send described information to described terminal, make described terminal based on described information, described destination phone numbers is marked.
Alternatively, described inactive phone number is discarded telephone number or the old telephone number needing replacing.
Alternatively, describedly judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that described user account is corresponding, comprising:
According to the operator belonging to the multiple contact phone numbers stored in the address list that described user account is corresponding, described multiple contact phone number is classified, obtains multiple collection for phone numbers;
For each collection for phone numbers in described multiple collection for phone numbers, judge whether comprise inactive phone number in described collection for phone numbers;
When described collection for phone numbers comprises inactive phone number, determine that described multiple contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in described multiple contact phone number.
Alternatively, describedly judge whether comprise inactive phone number in described collection for phone numbers, comprising:
The carrier server corresponding to described collection for phone numbers sends inquiry request, and described inquiry request carries described collection for phone numbers;
When receiving the Query Result that described carrier server sends, if described Query Result comprises inactive phone number record, then determine that described collection for phone numbers comprises inactive phone number, otherwise, determine not comprise inactive phone number in described collection for phone numbers.
Alternatively, describedly judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that described user account is corresponding, comprising:
For the arbitrary contact phone number in the multiple contact phone numbers stored in the address list that described user account is corresponding, judge whether described contact phone number is changed;
When described contact phone number is changed, determine that described multiple contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in described multiple contact phone number.
Alternatively, describedly judge whether described contact phone number is changed, comprising:
When receiving number update request corresponding to described contact phone number, new phone number corresponding to described contact phone number and contact person's account is carried in described number update request, based on described contact person's account, described contact phone number is replaced with described new phone number, and described contact person's account is the account that described contact person registers in Cloud Server;
Determine that described contact phone number is changed;
When not receiving number update request corresponding to described contact phone number, determine that described contact phone number is not changed.
According to the third aspect of disclosure embodiment, provide a kind of terminal, described terminal comprises:
Receiver module, for receiving the information of carrying destination phone numbers, the state of validity of multiple contact phone numbers that described information is stored based on terminal by Cloud Server generates, and described destination phone numbers is inactive phone number;
Search module, for searching the destination phone numbers of carrying in the information of described receiver module reception from described multiple contact phone number;
Mark module, for the information received based on described receiver module, marks described destination phone numbers of searching module searches.
Alternatively, described inactive phone number is discarded telephone number or the old telephone number needing replacing.
Alternatively, described mark module comprises:
First mark submodule, for when the information that described receiver module receives is for discarded telephone number information, carries out the first mark to described destination phone numbers of searching module searches.
Alternatively, described mark module comprises:
Second mark submodule, during for also carrying new phone number corresponding to described destination phone numbers when the information of described receiver module reception, based on described new phone number, carries out the second mark to described destination phone numbers of searching module searches.
Alternatively, described mark module also comprises:
Display sub-module, for when receive to described second mark submodule in second mark check instruction time, described new phone number is shown;
Replacement module, for when receiving the replacement instruction to described destination phone numbers, replaces with the new phone number of described display sub-module display by described destination phone numbers.
Alternatively, described terminal also comprises:
Sending module, for when receiving the renewal instruction of subscriber directory number, number update request corresponding to subscriber directory number is sent to described Cloud Server, user's new phone number and user account is carried in described number update request, make described Cloud Server based on described user account, the described subscriber directory number stored is replaced with described user's new phone number.
According to the fourth aspect of disclosure embodiment, provide a kind of Cloud Server, described Cloud Server comprises:
Acquisition module, for obtaining address list corresponding to each user account;
Judge module, for judging whether comprise destination phone numbers in multiple contact phone numbers of storing in the address list that user account that described acquisition module obtains is corresponding, described destination phone numbers is inactive phone number;
Generation module, during for judging that described multiple contact phone number comprises destination phone numbers when described judge module, generates the information comprising described destination phone numbers;
Sending module, for sending the information that described generation module generates to described terminal, makes described terminal based on described information, marks described destination phone numbers.
Alternatively, described inactive phone number is discarded telephone number or the old telephone number needing replacing.
Alternatively, described judge module comprises:
Classification submodule, for according to the operator belonging to the multiple contact phone numbers stored in address list corresponding to described user account, classifies to described multiple contact phone number, obtains multiple collection for phone numbers;
First judges submodule, for each collection for phone numbers in multiple collection for phone numbers of obtaining for described classification submodule, judges whether comprise inactive phone number in described collection for phone numbers;
First determines submodule, for when described first judges that submodule judges that described collection for phone numbers comprises inactive phone number, determine that described multiple contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in described multiple contact phone number.
Alternatively,
Described first judges submodule, for:
The carrier server corresponding to described collection for phone numbers sends inquiry request, and described inquiry request carries described collection for phone numbers;
When receiving the Query Result that described carrier server sends, if described Query Result comprises inactive phone number record, then determine that described collection for phone numbers comprises inactive phone number, otherwise, determine not comprise inactive phone number in described collection for phone numbers.
Alternatively, described judge module comprises:
Second judges submodule, for for the arbitrary contact phone number in the multiple contact phone numbers stored in address list corresponding to described user account, judges whether described contact phone number is changed;
Second determines submodule, for when described second judges that submodule judges that described contact phone number is changed, determine that described multiple contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in described multiple contact phone number.
Alternatively,
Described second judges submodule, for:
When receiving number update request corresponding to described contact phone number, new phone number corresponding to described contact phone number and contact person's account is carried in described number update request, based on described contact person's account, described contact phone number is replaced with described new phone number, and described contact person's account is the account that described contact person registers in Cloud Server;
Determine that described contact phone number is changed;
When not receiving number update request corresponding to described contact phone number, determine that described contact phone number is not changed.
According to the 5th aspect of disclosure embodiment, provide a kind of terminal, described terminal comprises:
Processor;
For the memory of storage of processor executable instruction;
Wherein, described processor is configured to:
Receive the information of carrying destination phone numbers, the state of validity of multiple contact phone numbers that described information is stored based on terminal by Cloud Server generates, and described destination phone numbers is inactive phone number;
Described destination phone numbers is searched from described multiple contact phone number;
Based on described information, described destination phone numbers is marked.
According to the 6th aspect of disclosure embodiment, provide a kind of Cloud Server, described Cloud Server comprises:
Processor;
For the memory of storage of processor executable instruction;
Wherein, described processor is configured to:
Obtain the address list that each user account is corresponding;
Judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that described user account is corresponding, described destination phone numbers is inactive phone number;
When described multiple contact phone number comprises destination phone numbers, generate the information comprising described destination phone numbers;
Send described information to described terminal, make described terminal based on described information, described destination phone numbers is marked.
The technical scheme that embodiment of the present disclosure provides can comprise following beneficial effect: in the disclosed embodiments, when Cloud Server determines that the multiple contact phone numbers stored comprise destination phone numbers, sends information to terminal.When terminal receives information, can mark destination phone numbers, incorrect with reminding user destination phone numbers, user upgraded or deletes destination phone numbers, improve the accuracy of the telephone number stored in address list list.
Should be understood that, it is only exemplary and explanatory that above general description and details hereinafter describe, and can not limit the disclosure.
Accompanying drawing explanation
Accompanying drawing to be herein merged in specification and to form the part of this specification, shows embodiment according to the invention, and is used from specification one and explains principle of the present invention.
Fig. 1 is the flow chart of a kind of telephone number labeling method according to an exemplary embodiment.
Fig. 2 is the flow chart of the another kind of telephone number labeling method according to an exemplary embodiment.
Fig. 3 is the flow chart of another the telephone number labeling method according to an exemplary embodiment.
Fig. 4 is the block diagram of a kind of terminal according to an exemplary embodiment.
Fig. 5 is the block diagram of the another kind of terminal according to an exemplary embodiment.
Fig. 6 is the block diagram of a kind of Cloud Server according to an exemplary embodiment.
Fig. 7 is the block diagram of a kind of judge module according to an exemplary embodiment.
Fig. 8 is the block diagram of the another kind of judge module according to an exemplary embodiment.
Fig. 9 is the block diagram of another terminal according to an exemplary embodiment.
Figure 10 is the block diagram of the another kind of Cloud Server according to an exemplary embodiment.
Embodiment
Here will be described exemplary embodiment in detail, its sample table shows in the accompanying drawings.When description below relates to accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawing represents same or analogous key element.Execution mode described in following exemplary embodiment does not represent all execution modes consistent with the present invention.On the contrary, they only with as in appended claims describe in detail, the example of apparatus and method that aspects more of the present invention are consistent.
Before disclosure embodiment being carried out to detailed explanation explanation, first the application scenarios of disclosure embodiment is introduced.User can storing contact telephone number in the address list in terminal, and is communicated with this contact person by the contact phone number stored.And when contact phone number changes, contact person does not notify this user, or, after notifying this user, this user forget by store this contact phone number upgrade, when causing user to communicate with this contact person, the situation easily occurring spacing or misdial; In addition, for the contact person that contact frequency ratio is lower, before user does not communicate with this contact person, user is difficult to find that this contact phone number is incorrect, causes the accuracy of the contact phone number stored in address list lower.Therefore, disclosure embodiment provides a kind of telephone number labeling method, the contact phone number changed in address list can be marked, make the contact phone number that user's Timeliness coverage changes, and upgrade in time or delete the contact phone number changed, improve the accuracy of telephone number in address list.
Fig. 1 is a kind of telephone number labeling method flow chart according to an exemplary embodiment.See Fig. 1, the method is used for, in terminal, comprising the following steps.
In a step 101, receive the information of carrying destination phone numbers, the state of validity of multiple contact phone numbers that this information is stored based on terminal by Cloud Server generates, and destination phone numbers is inactive phone number.
In a step 102, from the plurality of contact phone number, destination phone numbers is searched.
In step 103, based on this information, destination phone numbers is marked.
In the disclosed embodiments, when receiving the information that Cloud Server generates based on the destination phone numbers in multiple contact phone numbers of terminal storage, destination phone numbers is marked, incorrect with reminding user destination phone numbers, user upgraded or deletes destination phone numbers, improve the accuracy of the telephone number stored in address list list.
Alternatively, inactive phone number is discarded telephone number or the old telephone number needing replacing.
Alternatively, based on this information, destination phone numbers is marked, comprising:
When this information is for discarded telephone number information, the first mark is carried out to destination phone numbers.
Alternatively, based on this information, destination phone numbers is marked, comprising:
When this information also carries new phone number corresponding to destination phone numbers, based on new phone number, the second mark is carried out to destination phone numbers.
Alternatively, based on this new phone number, after the second mark is carried out to destination phone numbers, also comprise:
When receive to second mark check instruction time, new phone number is shown;
When receiving the replacement instruction to destination phone numbers, destination phone numbers is replaced with new phone number.
Alternatively, the method also comprises:
When receiving the renewal instruction of subscriber directory number, number update request corresponding to subscriber directory number is sent to Cloud Server, user's new phone number and user account is carried in this number update request, make Cloud Server based on this user account, the subscriber directory number of storage is replaced with user's new phone number.
Above-mentioned all alternatives, all can form embodiment of the present disclosure according to combining arbitrarily, disclosure embodiment repeats no longer one by one to this.
Fig. 2 is the another kind of telephone number labeling method flow chart according to an exemplary embodiment.See Fig. 2, the method is used for, in Cloud Server, comprising the following steps.
In step 201, address list corresponding to each user account is obtained.
In step 202., judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that this user account is corresponding, destination phone numbers is inactive phone number.
In step 203, when the plurality of contact phone number comprises destination phone numbers, generate the information comprising destination phone numbers.
In step 204, send information to terminal, make terminal based on this information, destination phone numbers is marked.
In the disclosed embodiments, when Cloud Server determines that the multiple contact phone numbers stored comprise destination phone numbers, information is sent to terminal.When terminal receives information, can mark destination phone numbers, incorrect with reminding user destination phone numbers, user upgraded or deletes destination phone numbers, improve the accuracy of the telephone number stored in address list list.
Alternatively, inactive phone number is discarded telephone number or the old telephone number needing replacing.
Alternatively, judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that this user account is corresponding, comprising:
According to the operator belonging to the multiple contact phone numbers stored in the address list that this user account is corresponding, the plurality of contact phone number is classified, obtain multiple collection for phone numbers;
For each collection for phone numbers in the plurality of collection for phone numbers, judge whether comprise inactive phone number in this collection for phone numbers;
When this collection for phone numbers comprises inactive phone number, determine that the plurality of contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in the plurality of contact phone number.
Alternatively, describedly judge whether comprise inactive phone number in this collection for phone numbers, comprising:
The carrier server corresponding to this collection for phone numbers sends inquiry request, and this inquiry request carries this collection for phone numbers;
When receiving the Query Result that carrier server sends, if this Query Result comprises inactive phone number record, then determine that this collection for phone numbers comprises inactive phone number, otherwise, determine not comprise inactive phone number in this collection for phone numbers.
Alternatively, judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that this user account is corresponding, comprising:
For the arbitrary contact phone number in the multiple contact phone numbers stored in the address list that this user account is corresponding, judge whether this contact phone number is changed;
When this contact phone number is changed, determine that the plurality of contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in the plurality of contact phone number.
Alternatively, describedly judge whether this contact phone number is changed, comprising:
When receiving number update request corresponding to this contact phone number, new phone number corresponding to this contact phone number and contact person's account is carried in this number update request, based on this contact person's account, this contact phone number is replaced with new phone number, and contact person's account is the account that this contact person registers in Cloud Server;
Determine that this contact phone number is changed;
When not receiving number update request corresponding to this contact phone number, determine that this contact phone number is not changed.
Above-mentioned all alternatives, all can form embodiment of the present disclosure according to combining arbitrarily, disclosure embodiment repeats no longer one by one to this.
Fig. 3 is another the telephone number labeling method flow chart according to an exemplary embodiment.See Fig. 3, the method comprises the following steps:
In step 301, Cloud Server obtains address list corresponding to each user account, and whether comprises destination phone numbers in the multiple contact phone numbers stored in judging the address list that user account is corresponding, and destination phone numbers is inactive phone number.
In the disclosed embodiments, in order to mark the telephone number stored in address list in terminal, user needs registered user's account in Cloud Server in advance, afterwards, terminal is based on this user account, be synchronized in Cloud Server by the multiple contact phone numbers stored in address list, now, this user account and this address list are stored in the corresponding relation between user account and address list by Cloud Server.Further, user after registered user's account, also needs in Cloud Server to store the corresponding relation between this user account and subscriber directory number in Cloud Server.Afterwards, Cloud Server can directly from the corresponding relation between this user account and address list, obtain the address list that each user account is corresponding, and for address list corresponding to each user account, judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that this user account is corresponding, and in the disclosed embodiments, the mode judging whether to comprise in the plurality of contact phone number destination phone numbers can comprise two kinds, specific as follows.
First kind of way, Cloud Server, according to the operator belonging to the plurality of contact phone number, is classified to the plurality of contact phone number, obtains multiple collection for phone numbers; For each collection for phone numbers in the plurality of collection for phone numbers, judge whether comprise inactive phone number in this collection for phone numbers; When this collection for phone numbers comprises inactive phone number, determine that the plurality of contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in the plurality of contact phone number.
Wherein, Cloud Server is according to the operator belonging to the plurality of contact phone number, the plurality of contact phone number is classified, the concrete operations obtaining multiple collection for phone numbers can be: Cloud Server is from the plurality of contact phone number, obtain the number segment of each contact phone number, and the number segment of each contact phone number and the corresponding relation between the operator name of storage and number segment are compared, contact phone number number segment being belonged to same operator is divided in a collection for phone numbers, obtain multiple collection for phone numbers.
Wherein, Cloud Server can obtain the number segment of the telephone number that each operator comprises in advance, and stores the corresponding relation between operator name and number segment.Such as, the operator of current telephone number comprises China Mobile, CHINAUNICOM and China Telecom; The number segment of China Mobile comprises: 139,138,137,136,135,134,150,151,158,159,152,188; The number segment of CHINAUNICOM comprises: 130,131,132,156,186,185; The number segment of China Telecom comprises: 133,153,189,180; Afterwards, the number segment of the title of each operator and each operator can be stored in the corresponding relation between operator name as shown in table 1 below and number segment by Cloud Server.
Table 1
Operator name | Number segment |
China Mobile | 139、138、137、136、135、134、150、151、158、159、152、188 |
CHINAUNICOM | 130、131、132、156、186、185 |
China Telecom | 133、153、189、180 |
Suppose, it is 13912454565,13849864556,15812454653,13415566245,13416265225,13032215623,13312455615,18612275245,15612306032,1531545663,18912245445 that Cloud Server obtains the multiple contact phone numbers stored in address list corresponding to user account.Cloud Server is from the plurality of contact phone number, the number segment obtaining each contact phone number is: 139,138,158,134,134,130,133,186,156,153,189, the number segment of each contact phone number and the corresponding relation between the operator name of storage and number segment are compared, number segment 139,138,158,134 and 134 belongs to China Mobile of operator; 130,186 and 156 belong to CHINAUNICOM of operator; 133,153 and 189 belong to China Telecom of operator, contact phone number number segment being belonged to same operator is divided in a collection for phone numbers, obtain 3 collection for phone numbers, be respectively [13912454565,13849864556,15812454653,13415566245,13416265225], [13032215623,18612275245,15612306032], [13312455615,1531545663,18912245445].
It should be noted that, in disclosure embodiment, be only described for the corresponding relation between the operator name stored in above-mentioned table 1 and number segment, the corresponding relation between operator name and number segment do not limited.
When the plurality of contact phone number is classified by above-mentioned steps by Cloud Server, after obtaining multiple collection for phone numbers, Cloud Server can judge whether comprise inactive phone number in each collection for phone numbers by following step, comprise: Cloud Server sends inquiry request to the carrier server that this collection for phone numbers is corresponding, and this inquiry request carries this collection for phone numbers; When carrier server receives this inquiry request, this carrier server obtains the state of validity of each contact phone number in this collection for phone numbers, and based on the state of validity of each contact phone number, generated query result, this Query Result is sent to Cloud Server by this carrier server.When the Query Result that cloud server sends to this carrier server, if this Query Result comprises inactive phone number record, then determine that this collection for phone numbers comprises inactive phone number, otherwise, determine not comprise inactive phone number in this collection for phone numbers.
Wherein, this carrier server obtains the state of validity of each contact phone number in this collection for phone numbers, and based on the state of validity of each contact phone number, the concrete operations of generated query result can be: for each contact phone number in this collection for phone numbers, this contact phone number compares with the inactive phone number set stored and effective telephone-number set by this carrier server respectively, if inactive phone number set comprises this contact phone number, then determine that this contact phone number is inactive phone number, the state of validity of this contact phone number is invalid, if effective telephone-number set comprises this contact phone number, then determine that this telephone number is effective telephone-number, the state of validity of this contact phone number is effective.After the state of validity determining each contact phone number, the state of validity of each contact phone number and each contact phone number is stored in the corresponding relation between telephone number and telephone number the state of validity, and using this corresponding relation as Query Result, in this Query Result the state of validity be invalid contact phone number place be recorded as inactive phone number record, the state of validity be effective contact phone number place be recorded as effective telephone-number record.
It should be noted that, in the disclosed embodiments, inactive phone number can be discarded telephone number or the old telephone number needing replacing, that is to say, inactive phone number can comprise sky telephone number, suspend the non-telephone numbers used such as the telephone number of use, effective telephone-number can for the telephone number used, and disclosure embodiment is not specifically limited this.
For first kind of way, Cloud Server is the telephone number whether comprising target in the multiple contact phone numbers stored in the address list that inquiring user account is corresponding on one's own initiative, without the need to the intervention of user, operates fairly simple.
The second way, for the arbitrary contact phone number in the plurality of contact phone number, judges whether this contact phone number upgrades; When this contact phone number upgrades, determine that the plurality of contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in the plurality of contact phone number.
For the second way, when contact person's terminal receives the renewal instruction of this contact phone number, contact person's terminal can send number update request corresponding to this contact phone number to Cloud Server, new phone number corresponding to contact phone number and contact person's account is carried in this number update request, when the number update request that cloud server sends to contact person's terminal, based on contact person's account, this contact phone number stored in Cloud Server is replaced with this new phone number, this contact person's account is the account that this contact person registers in Cloud Server, afterwards, Cloud Server determines that this contact phone number is changed, determines that the plurality of contact phone number comprises destination phone numbers.
Further, when Cloud Server does not receive number update request corresponding to this contact phone number, determine that this contact phone number is not changed, determine not comprise destination phone numbers in the plurality of contact phone number.
Mention terminal corresponding to user above in Cloud Server after registered user's account, need in Cloud Server to store the corresponding relation between subscriber directory number and user account, and for contact person also in like manner, namely, after contact person's terminal registers contact person's account in Cloud Server, Cloud Server also needs the corresponding relation between storing contact telephone number and contact person's account, afterwards, when cloud server is to number update request corresponding to contact phone number, can based on contact person's account, obtain contact phone number, and contact phone number is replaced with the new phone number carried in this number update request.
Wherein, the renewal instruction of contact phone number can be that this contact person triggers, and can also be that contact person's terminal triggers.When this renewal instruction triggers for this contact person, this contact person can be triggered by the renewing button clicked in contact person's terminal, certainly, whether this contact person's terminal also can detect the phonecard installed in this contact person's terminal and change, when the phonecard installed is changed, determine that contact phone number is changed, to this contact person's display update information, make this contact person's Trigger update instruction.When this renewal instruction triggers for contact person's terminal, when this contact person's terminal detects that the phonecard installed in this contact person's terminal is changed, determine that contact phone number is changed, Trigger update instruction.Disclosure embodiment is not specifically limited this.
Wherein, the phonecard mark of current installation can be stored in contact person's terminal, when contact person's terminal detects that contact person pulls up phonecard, and when again installing phonecard, contact person's terminal can detect the phonecard mark of again installing, and the phonecard of storage mark and the phonecard mark of again installing is compared, if both are identical, then determine that the phonecard installed in contact person's terminal is not changed, otherwise, determine that the phone installed in contact person's terminal is changed.Phonecard mark can be telephone number etc., and disclosure embodiment is not specifically limited this.
In the second way, when contact phone number is changed, the contact phone number stored in Cloud Server can be replaced, for user, when subscriber directory number is changed, when user terminal receives the renewal instruction of subscriber directory number, user terminal also can send number update request corresponding to subscriber directory number to Cloud Server, user's new phone number and user account is carried in this number update request, make Cloud Server based on this user account, the subscriber directory number of storage is replaced with user's new phone number.
Because first kind of way gets involved without the need to user, can only determine whether contact phone number is inactive phone number, the new phone number of contact person can not be got, and the second way is carried out alternately without the need to Cloud Server and carrier server, reduce the expense of telephone number mark, but the second way needs the intervention of user, the new phone number of contact person just can be got.Two kinds of modes are not conflicted mutually, can adopt simultaneously, to improve the result of use of disclosure embodiment.
In step 302, when the plurality of contact phone number comprises destination phone numbers, Cloud Server, according to destination phone numbers, sends information to terminal, carries destination phone numbers in this information.
Destination phone numbers is inactive phone number, when inactive phone number is for discarded telephone number, Cloud Server sends discarded telephone number information to terminal, when inactive phone number is the old telephone number needing to change, Cloud Server sends to terminal and changes telephone number information, changes in telephone number information and also carries new phone number corresponding to destination phone numbers.
In step 303, when terminal receives the information of Cloud Server transmission, terminal searches destination phone numbers from the multiple contact phone numbers stored.
No matter information still changes telephone number information for discarding telephone number information, and all carry destination phone numbers in this information, now, terminal can search destination phone numbers from the multiple contact phone numbers stored.
It should be noted that, in the disclosed embodiments, when terminal receives the information of Cloud Server transmission, this information can not be shown to user by terminal, directly can search destination phone numbers from the multiple contact phone numbers stored, avoid bothering user.
In step 304, when this information is for discarded telephone number information, terminal carries out the first mark to destination phone numbers.
First mark can be: to destination phone numbers carry out overstriking, highlighted, destination phone numbers position add exclamation mark or destination phone numbers position add text prompt, disclosure embodiment is not specifically limited this.
In step 305, when this information also carries new phone number corresponding to destination phone numbers, based on this new phone number, the second mark is carried out to destination phone numbers.
When this information also carries new phone number corresponding to destination phone numbers, determine that this information is for changing telephone number information.In addition, the mode of destination phone numbers being carried out to the second mark can be identical with the mode that first marks, and just do not comprise new phone number corresponding to destination phone numbers in the first mark, the second mark comprises new phone number corresponding to destination phone numbers.When terminal receive to second mark check instruction time, this new phone number is shown, when terminal receives the replacement instruction to destination phone numbers, destination phone numbers in address list is replaced with this new phone number, improve the accuracy of the telephone number stored in address list.
In the disclosed embodiments, when Cloud Server determines that the multiple contact phone numbers stored comprise destination phone numbers, information is sent to terminal.When terminal receives information, can mark destination phone numbers, incorrect with reminding user destination phone numbers, user upgraded or deletes destination phone numbers, improve the accuracy of the telephone number stored in address list list.
Fig. 4 is the block diagram of a kind of terminal according to an exemplary embodiment.See Fig. 4, this terminal comprises:
Receiver module 401, for receiving the information of carrying destination phone numbers, the state of validity of multiple contact phone numbers that this information is stored based on terminal by Cloud Server generates, and destination phone numbers is inactive phone number;
Search module 402, for searching the destination phone numbers of carrying in the information of receiver module 401 reception from the plurality of contact phone number;
Mark module 403, for the information received based on receiver module 401, marks searching the destination phone numbers that module 402 searches.
Alternatively, inactive phone number is discarded telephone number or the old telephone number needing replacing.
Alternatively, see Fig. 5, mark module 403 comprises:
First mark submodule 4031, for being when discarding telephone number information when the information that receiver module 401 receives, carries out the first mark to searching the destination phone numbers that module 402 searches.
Alternatively, as shown in Figure 5, mark module 403 comprises:
Second mark submodule 4032, during for also carrying new phone number corresponding to destination phone numbers when the information that receiver module 401 receives, based on new phone number, carries out the second mark to searching the destination phone numbers that module 402 searches.
Alternatively, mark module 403 also comprises:
Display sub-module, for when receive to second mark submodule in second mark check instruction time, this new phone number is shown;
Replacement module, for when receiving the replacement instruction to destination phone numbers, replaces with the new phone number of display sub-module display by destination phone numbers.
Alternatively, this terminal also comprises:
Sending module, for when receiving the renewal instruction of subscriber directory number, number update request corresponding to subscriber directory number is sent to Cloud Server, user's new phone number and user account is carried in this number update request, make Cloud Server based on this user account, the subscriber directory number of storage is replaced with user's new phone number.
In the disclosed embodiments, when receiving the information that Cloud Server generates based on the destination phone numbers in multiple contact phone numbers of terminal storage, destination phone numbers is marked, incorrect with reminding user destination phone numbers, user upgraded or deletes destination phone numbers, improve the accuracy of the telephone number stored in address list list.
Fig. 6 is the block diagram of a kind of Cloud Server according to an exemplary embodiment.See Fig. 6, this Cloud Server comprises:
Acquisition module 601, for obtaining address list corresponding to each user account;
Judge module 602, for judging whether comprise destination phone numbers in multiple contact phone numbers of storing in the address list that user account that acquisition module 601 obtains is corresponding, destination phone numbers is inactive phone number;
Generation module 603, for when judge module 601 judges that the plurality of contact phone number comprises destination phone numbers, generates the information comprising destination phone numbers;
Sending module 604, for sending the information that generation module 603 generates to this terminal, makes this terminal based on this information, marks destination phone numbers.
Alternatively, inactive phone number is discarded telephone number or the old telephone number needing replacing.
Alternatively, see Fig. 7, judge module 602 comprises:
Classification submodule 6021, for according to the operator belonging to the multiple contact phone numbers stored in address list corresponding to this user account, classifies to the plurality of contact phone number, obtains multiple collection for phone numbers;
First judges submodule 6022, for for each collection for phone numbers in multiple collection for phone numbers of obtaining of classification submodule 6021, judges whether comprise inactive phone number in this collection for phone numbers;
First determines submodule 6023, for when first judges that submodule 6022 judges that this collection for phone numbers comprises inactive phone number, determine that the plurality of contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in the plurality of contact phone number.
Alternatively,
First judges submodule 6012, for:
The carrier server corresponding to this collection for phone numbers sends inquiry request, and this inquiry request carries this collection for phone numbers;
When receiving the Query Result that carrier server sends, if this Query Result comprises inactive phone number record, then determine that this collection for phone numbers comprises inactive phone number, otherwise, determine not comprise inactive phone number in this collection for phone numbers.
Alternatively, see Fig. 8, judge module 602 comprises:
Second judges submodule 6024, for for the arbitrary contact phone number in the multiple contact phone numbers stored in address list corresponding to this user account, judges whether this contact phone number is changed;
Second determines submodule 6025, for when second judges that submodule 6024 judges that this contact phone number is changed, determine that the plurality of contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in the plurality of contact phone number.
Alternatively,
Second judges submodule 6024, for:
When receiving number update request corresponding to this contact phone number, new phone number corresponding to this contact phone number and contact person's account is carried in this number update request, based on this contact person's account, this contact phone number is replaced with new phone number, and contact person's account is the account that this contact person registers in Cloud Server;
Determine that this contact phone number is changed;
When not receiving number update request corresponding to this contact phone number, determine that this contact phone number is not changed.
In the disclosed embodiments, when Cloud Server determines that the multiple contact phone numbers stored comprise destination phone numbers, information is sent to terminal.When terminal receives information, can mark destination phone numbers, incorrect with reminding user destination phone numbers, user upgraded or deletes destination phone numbers, improve the accuracy of the telephone number stored in address list list.
About the device in above-described embodiment, wherein the concrete mode of modules executable operations has been described in detail in about the embodiment of the method, will not elaborate explanation herein.
Fig. 9 is a kind of block diagram for telephone number marked terminal 900 according to an exemplary embodiment.Such as, terminal 900 can be mobile phone, computer, digital broadcast terminal, messaging devices, game console, flat-panel devices, Medical Devices, body-building equipment, personal digital assistant etc.
With reference to Fig. 9, terminal 900 can comprise following one or more assembly: processing components 902, memory 904, power supply module 906, multimedia groupware 908, audio-frequency assembly 910, the interface 912 of I/O (I/O), sensor cluster 914, and communications component 916.
The integrated operation of the usual control terminal 900 of processing components 902, such as with display, call, data communication, camera operation and record operate the operation be associated.Treatment element 902 can comprise one or more processor 920 to perform instruction, to complete all or part of step of above-mentioned method.In addition, processing components 902 can comprise one or more module, and what be convenient between processing components 902 and other assemblies is mutual.Such as, processing unit 902 can comprise multi-media module, mutual with what facilitate between multimedia groupware 908 and processing components 902.
Memory 904 is configured to store various types of data to be supported in the operation of terminal 900.The example of these data comprises for any application program of operation in terminal 900 or the instruction of method, contact data, telephone book data, message, picture, video etc.Memory 904 can be realized by the volatibility of any type or non-volatile memory device or their combination, as static RAM (SRAM), Electrically Erasable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory EPROM (EPROM), programmable read only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, disk or CD.
The various assemblies that electric power assembly 906 is terminal 900 provide electric power.Electric power assembly 906 can comprise power-supply management system, one or more power supply, and other and the assembly generating, manage and distribute electric power for terminal 900 and be associated.
Multimedia groupware 908 is included in the screen providing an output interface between described terminal 900 and user.In certain embodiments, screen can comprise liquid crystal display (LCD) and touch panel (TP).If screen comprises touch panel, screen may be implemented as touch-screen, to receive the input signal from user.Touch panel comprises one or more touch sensor with the gesture on sensing touch, slip and touch panel.Described touch sensor can the border of not only sensing touch or sliding action, but also detects the duration relevant to described touch or slide and pressure.In certain embodiments, multimedia groupware 908 comprises a front-facing camera and/or post-positioned pick-up head.When terminal 900 is in operator scheme, during as screening-mode or video mode, front-facing camera and/or post-positioned pick-up head can receive outside multi-medium data.Each front-facing camera and post-positioned pick-up head can be fixing optical lens systems or have focal length and optical zoom ability.
Audio-frequency assembly 910 is configured to export and/or input audio signal.Such as, audio-frequency assembly 910 comprises a microphone (MIC), and when terminal 900 is in operator scheme, during as call model, logging mode and speech recognition mode, microphone is configured to receive external audio signal.The audio signal received can be stored in memory 904 further or be sent via communications component 916.In certain embodiments, audio-frequency assembly 910 also comprises a loud speaker, for output audio signal.
I/O interface 912 is for providing interface between processing components 902 and peripheral interface module, and above-mentioned peripheral interface module can be keyboard, some striking wheel, button etc.These buttons can include but not limited to: home button, volume button, start button and locking press button.
Sensor cluster 914 comprises one or more transducer, for providing the state estimation of various aspects for terminal 900.Such as, sensor cluster 914 can detect the opening/closing state of terminal 900, the relative positioning of assembly, such as described assembly is display and the keypad of terminal 900, the position of all right sense terminals 900 of sensor cluster 914 or terminal 900 1 assemblies changes, the presence or absence that user contacts with terminal 900, the variations in temperature of terminal 900 orientation or acceleration/deceleration and terminal 900.Sensor cluster 914 can comprise proximity transducer, be configured to without any physical contact time detect near the existence of object.Sensor cluster 914 can also comprise optical sensor, as CMOS or ccd image sensor, for using in imaging applications.In certain embodiments, this sensor cluster 914 can also comprise acceleration transducer, gyro sensor, Magnetic Sensor, pressure sensor or temperature sensor.
Communications component 916 is configured to the communication being convenient to wired or wireless mode between terminal 900 and other equipment.Terminal 900 can access the wireless network based on communication standard, as WiFi, 2G or 3G, or their combination.In one exemplary embodiment, communication component 916 receives from the broadcast singal of external broadcasting management system or broadcast related information via broadcast channel.In one exemplary embodiment, described communication component 916 also comprises near-field communication (NFC) module, to promote junction service.Such as, can based on radio-frequency (RF) identification (RFID) technology in NFC module, Infrared Data Association (IrDA) technology, ultra broadband (UWB) technology, bluetooth (BT) technology and other technologies realize.
In the exemplary embodiment, terminal 900 can be realized, for performing said method by one or more application specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing appts (DSPD), programmable logic device (PLD), field programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic components.
In the exemplary embodiment, additionally provide a kind of non-transitory computer-readable recording medium comprising instruction, such as, comprise the memory 904 of instruction, above-mentioned instruction can perform said method by the processor 920 of terminal 900.Such as, described non-transitory computer-readable recording medium can be ROM, random access memory (RAM), CD-ROM, tape, floppy disk and optical data storage devices etc.
A kind of non-transitory computer-readable recording medium, when the instruction in described storage medium is performed by the processor of mobile terminal, make mobile terminal can perform a kind of telephone number labeling method, described method comprises:
Receive the information of carrying destination phone numbers, the state of validity of multiple contact phone numbers that this information is stored based on terminal by Cloud Server generates, and destination phone numbers is inactive phone number.
Destination phone numbers is searched from the plurality of contact phone number.
Based on this information, destination phone numbers is marked.
Alternatively, inactive phone number is discarded telephone number or the old telephone number needing replacing.
Alternatively, based on this information, destination phone numbers is marked, comprising:
When this information is for discarded telephone number information, the first mark is carried out to destination phone numbers.
Alternatively, based on this information, destination phone numbers is marked, comprising:
When this information also carries new phone number corresponding to destination phone numbers, based on new phone number, the second mark is carried out to destination phone numbers.
Alternatively, based on this new phone number, after the second mark is carried out to destination phone numbers, also comprise:
When receive to second mark check instruction time, new phone number is shown;
When receiving the replacement instruction to destination phone numbers, destination phone numbers is replaced with this new phone number.
Alternatively, the method also comprises:
When receiving the renewal instruction of subscriber directory number, number update request corresponding to subscriber directory number is sent to Cloud Server, user's new phone number and user account is carried in this number update request, make Cloud Server based on this user account, the subscriber directory number of storage is replaced with user's new phone number.
In the disclosed embodiments, when receiving the information that Cloud Server generates based on the destination phone numbers in multiple contact phone numbers of terminal storage, destination phone numbers is marked, incorrect with reminding user destination phone numbers, user upgraded or deletes destination phone numbers, improve the accuracy of the telephone number stored in address list list.
Figure 10 is the block diagram of a kind of Cloud Server 1000 for telephone number mark according to an exemplary embodiment.With reference to Figure 10, Cloud Server 1000 comprises processing components 1022, and it comprises one or more processor further, and the memory resource representated by memory 1032, can such as, by the instruction of the execution of processing unit 1022, application program for storing.The application program stored in memory 1032 can comprise each module corresponding to one group of instruction one or more.In addition, processing components 1022 is configured to perform instruction, and to perform the method for following telephone number mark, the method comprises:
Obtain the address list that each user account is corresponding;
Judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that this user account is corresponding, destination phone numbers is inactive phone number;
When the plurality of contact phone number comprises destination phone numbers, generate the information comprising destination phone numbers;
Send information to terminal, make terminal based on this information, destination phone numbers is marked.
Alternatively, inactive phone number is discarded telephone number or the old telephone number needing replacing.
Alternatively, judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that this user account is corresponding, comprising:
According to the operator belonging to the multiple contact phone numbers stored in the address list that this user account is corresponding, the plurality of contact phone number is classified, obtain multiple collection for phone numbers;
For each collection for phone numbers in the plurality of collection for phone numbers, judge whether comprise inactive phone number in this collection for phone numbers;
When this collection for phone numbers comprises inactive phone number, determine that the plurality of contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in the plurality of contact phone number.
Alternatively, describedly judge whether comprise inactive phone number in this collection for phone numbers, comprising:
The carrier server corresponding to this collection for phone numbers sends inquiry request, and this inquiry request carries this collection for phone numbers;
When receiving the Query Result that carrier server sends, if this Query Result comprises inactive phone number record, then determine that this collection for phone numbers comprises inactive phone number, otherwise, determine not comprise inactive phone number in this collection for phone numbers.
Alternatively, judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that this user account is corresponding, comprising:
For the arbitrary contact phone number in the multiple contact phone numbers stored in the address list that this user account is corresponding, judge whether this contact phone number is changed;
When this contact phone number is changed, determine that the plurality of contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in the plurality of contact phone number.
Alternatively, describedly judge whether this contact phone number is changed, comprising:
When receiving number update request corresponding to this contact phone number, new phone number corresponding to this contact phone number and contact person's account is carried in this number update request, based on this contact person's account, this contact phone number is replaced with new phone number, and contact person's account is the account that this contact person registers in Cloud Server;
Determine that this contact phone number is changed;
When not receiving number update request corresponding to this contact phone number, determine that this contact phone number is not changed.
Cloud Server 1000 can also comprise the power management that a power supply module 1026 is configured to perform Cloud Server 1000, a wired or wireless network interface 1050 is configured to Cloud Server 1000 to be connected to network, and input and output (I/O) interface 1058.Cloud Server 1000 can operate the operating system based on being stored in memory 1032, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or similar.
Those skilled in the art, at consideration specification and after putting into practice invention disclosed herein, will easily expect other embodiment of the present invention.The application is intended to contain any modification of the present invention, purposes or adaptations, and these modification, purposes or adaptations are followed general principle of the present invention and comprised the undocumented common practise in the art of the disclosure or conventional techniques means.Specification and embodiment are only regarded as exemplary, and true scope of the present invention and spirit are pointed out by claim below.
Should be understood that, the present invention is not limited to precision architecture described above and illustrated in the accompanying drawings, and can carry out various amendment and change not departing from its scope.Scope of the present invention is only limited by appended claim.
Claims (26)
1. a telephone number labeling method, is characterized in that, described method comprises:
Receive the information of carrying destination phone numbers, the state of validity of multiple contact phone numbers that described information is stored based on terminal by Cloud Server generates, and described destination phone numbers is inactive phone number;
Described destination phone numbers is searched from described multiple contact phone number;
Based on described information, described destination phone numbers is marked.
2. the method for claim 1, is characterized in that, described inactive phone number is discarded telephone number or the old telephone number needing replacing.
3. method as claimed in claim 1 or 2, is characterized in that, described based on described information, marks, comprising described destination phone numbers:
When described information is for discarded telephone number information, the first mark is carried out to described destination phone numbers.
4. method as claimed in claim 1 or 2, is characterized in that, described based on described information, marks, comprising described destination phone numbers:
When described information also carries new phone number corresponding to described destination phone numbers, based on described new phone number, the second mark is carried out to described destination phone numbers.
5. method as claimed in claim 4, is characterized in that, described based on described new phone number, after carrying out the second mark, also comprises described destination phone numbers:
When receive to described second mark check instruction time, described new phone number is shown;
When receiving the replacement instruction to described destination phone numbers, described destination phone numbers is replaced with described new phone number.
6. the method for claim 1, is characterized in that, described method also comprises:
When receiving the renewal instruction of subscriber directory number, number update request corresponding to subscriber directory number is sent to described Cloud Server, user's new phone number and user account is carried in described number update request, make described Cloud Server based on described user account, the described subscriber directory number stored is replaced with described user's new phone number.
7. a telephone number labeling method, is characterized in that, described method comprises:
Obtain the address list that each user account is corresponding;
Judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that described user account is corresponding, described destination phone numbers is inactive phone number;
When described multiple contact phone number comprises destination phone numbers, generate the information comprising described destination phone numbers;
Send described information to described terminal, make described terminal based on described information, described destination phone numbers is marked.
8. method as claimed in claim 7, is characterized in that, described inactive phone number is discarded telephone number or the old telephone number needing replacing.
9. as claimed in claim 7 or 8 method, is characterized in that, describedly judges whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that described user account is corresponding, comprising:
According to the operator belonging to the multiple contact phone numbers stored in the address list that described user account is corresponding, described multiple contact phone number is classified, obtains multiple collection for phone numbers;
For each collection for phone numbers in described multiple collection for phone numbers, judge whether comprise inactive phone number in described collection for phone numbers;
When described collection for phone numbers comprises inactive phone number, determine that described multiple contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in described multiple contact phone number.
10. method as claimed in claim 9, is characterized in that, describedly judges whether comprise inactive phone number in described collection for phone numbers, comprising:
The carrier server corresponding to described collection for phone numbers sends inquiry request, and described inquiry request carries described collection for phone numbers;
When receiving the Query Result that described carrier server sends, if described Query Result comprises inactive phone number record, then determine that described collection for phone numbers comprises inactive phone number, otherwise, determine not comprise inactive phone number in described collection for phone numbers.
11. methods as claimed in claim 7, is characterized in that, describedly judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that described user account is corresponding, comprising:
For the arbitrary contact phone number in the multiple contact phone numbers stored in the address list that described user account is corresponding, judge whether described contact phone number is changed;
When described contact phone number is changed, determine that described multiple contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in described multiple contact phone number.
12. methods as claimed in claim 11, is characterized in that, describedly judge whether described contact phone number is changed, comprising:
When receiving number update request corresponding to described contact phone number, new phone number corresponding to described contact phone number and contact person's account is carried in described number update request, based on described contact person's account, described contact phone number is replaced with described new phone number, and described contact person's account is the account that contact person registers in Cloud Server;
Determine that described contact phone number is changed;
When not receiving number update request corresponding to described contact phone number, determine that described contact phone number is not changed.
13. 1 kinds of terminals, is characterized in that, described terminal comprises:
Receiver module, for receiving the information of carrying destination phone numbers, the state of validity of multiple contact phone numbers that described information is stored based on terminal by Cloud Server generates, and described destination phone numbers is inactive phone number;
Search module, for searching the destination phone numbers of carrying in the information of described receiver module reception from described multiple contact phone number;
Mark module, for the information received based on described receiver module, marks described destination phone numbers of searching module searches.
14. terminals as claimed in claim 13, is characterized in that, described inactive phone number is discarded telephone number or the old telephone number needing replacing.
15. terminals as described in claim 13 or 14, it is characterized in that, described mark module comprises:
First mark submodule, for when the information that described receiver module receives is for discarded telephone number information, carries out the first mark to described destination phone numbers of searching module searches.
16. terminals as described in claim 13 or 14, it is characterized in that, described mark module comprises:
Second mark submodule, during for also carrying new phone number corresponding to described destination phone numbers when the information of described receiver module reception, based on described new phone number, carries out the second mark to described destination phone numbers of searching module searches.
17. terminals as claimed in claim 16, it is characterized in that, described mark module also comprises:
Display sub-module, for when receive to described second mark submodule in second mark check instruction time, described new phone number is shown;
Replacement module, for when receiving the replacement instruction to described destination phone numbers, replaces with the new phone number of described display sub-module display by described destination phone numbers.
18. terminals as claimed in claim 13, it is characterized in that, described terminal also comprises:
Sending module, for when receiving the renewal instruction of subscriber directory number, number update request corresponding to subscriber directory number is sent to described Cloud Server, user's new phone number and user account is carried in described number update request, make described Cloud Server based on described user account, the described subscriber directory number stored is replaced with described user's new phone number.
19. 1 kinds of Cloud Servers, is characterized in that, described Cloud Server comprises:
Acquisition module, for obtaining address list corresponding to each user account;
Judge module, for judging whether comprise destination phone numbers in multiple contact phone numbers of storing in the address list that user account that described acquisition module obtains is corresponding, described destination phone numbers is inactive phone number;
Generation module, during for judging that described multiple contact phone number comprises destination phone numbers when described judge module, generates the information comprising described destination phone numbers;
Sending module, for sending the information that described generation module generates to described terminal, makes described terminal based on described information, marks described destination phone numbers.
20. Cloud Servers as claimed in claim 19, is characterized in that, described inactive phone number is discarded telephone number or the old telephone number needing replacing.
21. Cloud Servers as claimed in claim 19, it is characterized in that, described judge module comprises:
Classification submodule, for according to the operator belonging to the multiple contact phone numbers stored in address list corresponding to described user account, classifies to described multiple contact phone number, obtains multiple collection for phone numbers;
First judges submodule, for each collection for phone numbers in multiple collection for phone numbers of obtaining for described classification submodule, judges whether comprise inactive phone number in described collection for phone numbers;
First determines submodule, for when described first judges that submodule judges that described collection for phone numbers comprises inactive phone number, determine that described multiple contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in described multiple contact phone number.
22. Cloud Servers as claimed in claim 21, is characterized in that,
Described first judges submodule, for:
The carrier server corresponding to described collection for phone numbers sends inquiry request, and described inquiry request carries described collection for phone numbers;
When receiving the Query Result that described carrier server sends, if described Query Result comprises inactive phone number record, then determine that described collection for phone numbers comprises inactive phone number, otherwise, determine not comprise inactive phone number in described collection for phone numbers.
23. Cloud Servers as claimed in claim 19, it is characterized in that, described judge module comprises:
Second judges submodule, for for the arbitrary contact phone number in the multiple contact phone numbers stored in address list corresponding to described user account, judges whether described contact phone number is changed;
Second determines submodule, for when described second judges that submodule judges that described contact phone number is changed, determine that described multiple contact phone number comprises destination phone numbers, otherwise, determine not comprise destination phone numbers in described multiple contact phone number.
24. Cloud Servers as claimed in claim 23, is characterized in that,
Described second judges submodule, for:
When receiving number update request corresponding to described contact phone number, new phone number corresponding to described contact phone number and contact person's account is carried in described number update request, based on described contact person's account, described contact phone number is replaced with described new phone number, and described contact person's account is the account that contact person registers in Cloud Server;
Determine that described contact phone number is changed;
When not receiving number update request corresponding to described contact phone number, determine that described contact phone number is not changed.
25. 1 kinds of terminals, is characterized in that, described terminal comprises:
Processor;
For the memory of storage of processor executable instruction;
Wherein, described processor is configured to:
Receive the information of carrying destination phone numbers, the state of validity of multiple contact phone numbers that described information is stored based on terminal by Cloud Server generates, and described destination phone numbers is inactive phone number;
Described destination phone numbers is searched from described multiple contact phone number;
Based on described information, described destination phone numbers is marked.
26. 1 kinds of Cloud Servers, is characterized in that, described Cloud Server comprises:
Processor;
For the memory of storage of processor executable instruction;
Wherein, described processor is configured to:
Obtain the address list that each user account is corresponding;
Judge whether comprise destination phone numbers in the multiple contact phone numbers stored in the address list that described user account is corresponding, described destination phone numbers is inactive phone number;
When described multiple contact phone number comprises destination phone numbers, generate the information comprising described destination phone numbers;
Send described information to described terminal, make described terminal based on described information, described destination phone numbers is marked.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201410840035.6A CN104580637B (en) | 2014-12-30 | 2014-12-30 | Telephone number labeling method, terminal and Cloud Server |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201410840035.6A CN104580637B (en) | 2014-12-30 | 2014-12-30 | Telephone number labeling method, terminal and Cloud Server |
Publications (2)
Publication Number | Publication Date |
---|---|
CN104580637A true CN104580637A (en) | 2015-04-29 |
CN104580637B CN104580637B (en) | 2018-05-18 |
Family
ID=53095782
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201410840035.6A Active CN104580637B (en) | 2014-12-30 | 2014-12-30 | Telephone number labeling method, terminal and Cloud Server |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN104580637B (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105120086A (en) * | 2015-07-31 | 2015-12-02 | 小米科技有限责任公司 | Method, device and system for processing marked information |
CN105162956A (en) * | 2015-07-31 | 2015-12-16 | 小米科技有限责任公司 | Communication information transmission method, equipment and system |
CN105376382A (en) * | 2015-10-13 | 2016-03-02 | 惠州Tcl移动通信有限公司 | Mobile terminal and method of mobile terminal for processing telephone numbers |
CN105577879A (en) * | 2015-12-22 | 2016-05-11 | 广东欧珀移动通信有限公司 | Address book management method and mobile terminal |
CN106303099A (en) * | 2015-05-12 | 2017-01-04 | 中国移动通信集团公司 | A kind of verify the method for telex network number effectiveness, Apparatus and system |
CN106792653A (en) * | 2015-11-25 | 2017-05-31 | 中国移动通信集团公司 | A kind of communicating number information processing method, apparatus and system |
CN106851026A (en) * | 2017-01-23 | 2017-06-13 | 北京奇虎科技有限公司 | Inactive phone number is recognized and method for cleaning, device and mobile terminal |
CN106888446A (en) * | 2015-12-15 | 2017-06-23 | 中国电信股份有限公司 | For the methods, devices and systems of checking information recipient's property right identity |
CN107249067A (en) * | 2017-07-27 | 2017-10-13 | 深圳市泰衡诺科技有限公司 | The address list method for cleaning and address list cleaning plant of a kind of intelligent terminal |
CN108390986A (en) * | 2018-03-01 | 2018-08-10 | 广东欧珀移动通信有限公司 | Telephone number method for pushing, device, system and computer readable storage medium |
CN109660648A (en) * | 2017-10-10 | 2019-04-19 | 中兴通讯股份有限公司 | A kind of processing method of telephone number, network address book server, terminal, carrier server and computer storage medium |
CN110166637A (en) * | 2018-02-12 | 2019-08-23 | 深圳市六度人和科技有限公司 | A kind of spacing recognition methods and device |
CN110493307A (en) * | 2019-07-05 | 2019-11-22 | 上海创蓝文化传播有限公司 | Number condition detecting system and detection method |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040052357A1 (en) * | 2002-07-31 | 2004-03-18 | Xpherix Corporation | Method and apparatus for processing phone numbers |
CN101521705A (en) * | 2009-03-23 | 2009-09-02 | 候万春 | System and method for realizing communication based on on-line telephone book mode |
CN101572879A (en) * | 2008-04-28 | 2009-11-04 | 鸿富锦精密工业(深圳)有限公司 | Communication system, communication terminal and method for updating electronic address list thereof |
CN102420852A (en) * | 2011-11-11 | 2012-04-18 | 宇龙计算机通信科技(深圳)有限公司 | Server, mobile terminal and data synchronizing method |
CN102821142A (en) * | 2012-07-24 | 2012-12-12 | 东莞宇龙通信科技有限公司 | Mobile network management server, mobile terminal and method for updating contact list |
CN102882949A (en) * | 2012-09-14 | 2013-01-16 | 东莞宇龙通信科技有限公司 | Method for completing contact information and server |
CN103248655A (en) * | 2012-02-10 | 2013-08-14 | 腾讯科技(深圳)有限公司 | Method and device for business card information updating |
CN103249020A (en) * | 2012-02-14 | 2013-08-14 | 宇龙计算机通信科技(深圳)有限公司 | Cloud-service-based emergency call processing method and system, and mobile terminal |
CN103369097A (en) * | 2012-03-26 | 2013-10-23 | 富泰华工业(深圳)有限公司 | Mobile communication terminal and method for managing telephone numbers |
-
2014
- 2014-12-30 CN CN201410840035.6A patent/CN104580637B/en active Active
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040052357A1 (en) * | 2002-07-31 | 2004-03-18 | Xpherix Corporation | Method and apparatus for processing phone numbers |
CN101572879A (en) * | 2008-04-28 | 2009-11-04 | 鸿富锦精密工业(深圳)有限公司 | Communication system, communication terminal and method for updating electronic address list thereof |
CN101521705A (en) * | 2009-03-23 | 2009-09-02 | 候万春 | System and method for realizing communication based on on-line telephone book mode |
CN102420852A (en) * | 2011-11-11 | 2012-04-18 | 宇龙计算机通信科技(深圳)有限公司 | Server, mobile terminal and data synchronizing method |
CN103248655A (en) * | 2012-02-10 | 2013-08-14 | 腾讯科技(深圳)有限公司 | Method and device for business card information updating |
CN103249020A (en) * | 2012-02-14 | 2013-08-14 | 宇龙计算机通信科技(深圳)有限公司 | Cloud-service-based emergency call processing method and system, and mobile terminal |
CN103369097A (en) * | 2012-03-26 | 2013-10-23 | 富泰华工业(深圳)有限公司 | Mobile communication terminal and method for managing telephone numbers |
CN102821142A (en) * | 2012-07-24 | 2012-12-12 | 东莞宇龙通信科技有限公司 | Mobile network management server, mobile terminal and method for updating contact list |
CN102882949A (en) * | 2012-09-14 | 2013-01-16 | 东莞宇龙通信科技有限公司 | Method for completing contact information and server |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106303099A (en) * | 2015-05-12 | 2017-01-04 | 中国移动通信集团公司 | A kind of verify the method for telex network number effectiveness, Apparatus and system |
CN105162956B (en) * | 2015-07-31 | 2018-09-18 | 小米科技有限责任公司 | Transmission method, equipment and the system of communication information |
CN105162956A (en) * | 2015-07-31 | 2015-12-16 | 小米科技有限责任公司 | Communication information transmission method, equipment and system |
CN105120086A (en) * | 2015-07-31 | 2015-12-02 | 小米科技有限责任公司 | Method, device and system for processing marked information |
CN105376382A (en) * | 2015-10-13 | 2016-03-02 | 惠州Tcl移动通信有限公司 | Mobile terminal and method of mobile terminal for processing telephone numbers |
CN106792653B (en) * | 2015-11-25 | 2020-03-24 | 中国移动通信集团公司 | Communication number information processing method, device and system |
CN106792653A (en) * | 2015-11-25 | 2017-05-31 | 中国移动通信集团公司 | A kind of communicating number information processing method, apparatus and system |
CN106888446A (en) * | 2015-12-15 | 2017-06-23 | 中国电信股份有限公司 | For the methods, devices and systems of checking information recipient's property right identity |
CN105577879B (en) * | 2015-12-22 | 2019-06-25 | Oppo广东移动通信有限公司 | A kind of book management method and mobile terminal |
CN105577879A (en) * | 2015-12-22 | 2016-05-11 | 广东欧珀移动通信有限公司 | Address book management method and mobile terminal |
CN106851026A (en) * | 2017-01-23 | 2017-06-13 | 北京奇虎科技有限公司 | Inactive phone number is recognized and method for cleaning, device and mobile terminal |
CN107249067A (en) * | 2017-07-27 | 2017-10-13 | 深圳市泰衡诺科技有限公司 | The address list method for cleaning and address list cleaning plant of a kind of intelligent terminal |
CN109660648A (en) * | 2017-10-10 | 2019-04-19 | 中兴通讯股份有限公司 | A kind of processing method of telephone number, network address book server, terminal, carrier server and computer storage medium |
CN110166637A (en) * | 2018-02-12 | 2019-08-23 | 深圳市六度人和科技有限公司 | A kind of spacing recognition methods and device |
CN110166637B (en) * | 2018-02-12 | 2021-07-23 | 深圳市六度人和科技有限公司 | Empty number identification method and device |
CN108390986A (en) * | 2018-03-01 | 2018-08-10 | 广东欧珀移动通信有限公司 | Telephone number method for pushing, device, system and computer readable storage medium |
CN110493307A (en) * | 2019-07-05 | 2019-11-22 | 上海创蓝文化传播有限公司 | Number condition detecting system and detection method |
Also Published As
Publication number | Publication date |
---|---|
CN104580637B (en) | 2018-05-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN104580637A (en) | Telephone number marking method, terminal and cloud server | |
CN104159275B (en) | Method for connecting network and device | |
CN108496317B (en) | Method and device for searching public resource set of residual key system information | |
CN104660685A (en) | Method and device for obtaining equipment information | |
CN104853336A (en) | Method for discovering intelligent equipment, method for accessing to internet and devices thereof | |
CN106254467A (en) | Sharing files method and device | |
CN105511907A (en) | Application program upgrade method, device and system | |
CN104836924A (en) | Number marking method and device | |
CN104320774A (en) | Updating method, device and facility | |
CN104539789A (en) | Method and device for prompting call request | |
CN110945883B (en) | Paging signaling receiving method and device and paging signaling sending method and device | |
CN104767857A (en) | Telephone calling method and device based on cloud name cards | |
CN105554064A (en) | Method and device for setting head portrait | |
CN105100513A (en) | Incoming call information processing method, device, and incoming call business server | |
CN104158854B (en) | Resource share method and device | |
CN105491518A (en) | Method and device for social reminding based on wearable devices | |
CN105634920A (en) | Message withdrawing method and device | |
CN104407869A (en) | Notice column updating method and device | |
CN105515923A (en) | Equipment control method and device | |
CN104639739A (en) | Call intercepting method and device | |
CN104135512B (en) | Service registry update method, device, server and client | |
CN105095296A (en) | File management method and device | |
CN104158938B (en) | Incoming display method, server and terminal | |
CN104158851B (en) | A kind of dissemination system of Network, method and apparatus | |
CN105634928A (en) | Social reminding method and device based on wearable device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |