WO2015070824A2 - 电话号码标记方法及系统 - Google Patents

电话号码标记方法及系统 Download PDF

Info

Publication number
WO2015070824A2
WO2015070824A2 PCT/CN2015/070782 CN2015070782W WO2015070824A2 WO 2015070824 A2 WO2015070824 A2 WO 2015070824A2 CN 2015070782 W CN2015070782 W CN 2015070782W WO 2015070824 A2 WO2015070824 A2 WO 2015070824A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
phone number
information
database
tag information
Prior art date
Application number
PCT/CN2015/070782
Other languages
English (en)
French (fr)
Other versions
WO2015070824A3 (zh
Inventor
张瞰
张檬
任腾
王健
Original Assignee
上海触乐信息科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 上海触乐信息科技有限公司 filed Critical 上海触乐信息科技有限公司
Publication of WO2015070824A2 publication Critical patent/WO2015070824A2/zh
Publication of WO2015070824A3 publication Critical patent/WO2015070824A3/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/26—Devices for calling a subscriber
    • H04M1/27—Devices whereby a plurality of signals may be stored simultaneously
    • H04M1/274—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc
    • H04M1/2745—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc using static electronic memories, e.g. chips
    • H04M1/2753—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc using static electronic memories, e.g. chips providing data content
    • H04M1/2757—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc using static electronic memories, e.g. chips providing data content by data transmission, e.g. downloading
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42034—Calling party identification service
    • H04M3/42059—Making use of the calling party identifier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42034—Calling party identification service
    • H04M3/42059—Making use of the calling party identifier
    • H04M3/42068—Making use of the calling party identifier where the identifier is used to access a profile
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42085—Called party identification service
    • H04M3/42102—Making use of the called party identifier
    • H04M3/4211—Making use of the called party identifier where the identifier is used to access a profile
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/436—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2203/00—Aspects of automatic or semi-automatic exchanges
    • H04M2203/55—Aspects of automatic or semi-automatic exchanges related to network data storage and management
    • H04M2203/554—Data synchronization

Definitions

  • the present invention relates to the field of data processing, and more particularly to smart tag processing of mobile communication pair numbers.
  • the association of the telephone number with the calling party is the original intention of the telephone marking system.
  • the database is mostly local, and it is usually numbered in such a way; for example, when the user's calling/called is monitored, the telephone number data is matched with the telephone number in the database, if any The matching number displays the information related to the number in the mobile terminal. If there is no matching number, the tag information of the number is not displayed or "unknown number" is displayed.
  • the contact book in the phone is an example of this.
  • the traditional marking system can only be manually operated on the database side due to the update of its database content, so the recognition range is small.
  • a prior art telephone number marking system as shown in FIG. 1 shows three mobile terminals 102, 104 and 106, three local databases 108, 110 and 112 respectively adapted to three mobile terminals, respectively Three tagging device local terminals 120, 122 and 124, and a cloud database 118 are accommodated by the three mobile terminals.
  • the local terminal (not shown) of the mobile terminal 102 listens to its host/called number and triggers the marking device local end 120; the marking device local end 120 provides a marking interface for the mobile 102. The user marks it.
  • the number is Corresponding tag
  • uploading the tag information to the cloud server through the local device of the tag device thereby ensuring that when the user replaces the mobile phone or the phone card, the previously marked phone number and corresponding tag information can still be obtained.
  • the user can only mark the number that he has received, that is, the database of the number markings used by different users is relatively independent, and the number identification range is small. Moreover, for each number, the user needs to perform manual operations by himself, and the operation is cumbersome.
  • the user's identification needs are actually different. For some numbers, such as express delivery, if the mark is not marked, the user identification and contact are not convenient. If the identification is made, the user frequency is very low, and the express delivery is small. The mobility of the people is very large, and it is not realistic to mark each number.
  • the invention provides a method for marking a phone, comprising: acquiring a phone number of an incoming call or an outgoing call of the mobile terminal; matching the acquired phone number in at least one of a local or cloud database; according to the phone number Whether the local or cloud database matches successfully and whether it is a challenge number, displaying a different tag page to the user, prompting the user to mark the phone number or confirming the tag information of the number; obtaining the user according to the tag page Marking information of the phone number and verifying the tag; and updating the cloud database and the local database based on the result of the tag verification.
  • the phone number is successfully matched in the local database, displaying tag information corresponding to the phone number; if the phone number fails to match in the local database, displaying an initial tag page, The user is prompted to mark the phone number.
  • the phone number is successfully matched in the cloud database, further determining whether there is a correction mark instruction; if the correction mark is not needed, displaying the mark information corresponding to the phone number; if the correction mark is needed, Then the correction markup page is displayed. The user is prompted to select or confirm the marked tag information; if the phone number fails to match in the cloud database, the initial tag page is displayed, and the initial tag information of the user to the phone number is obtained.
  • the present invention further provides a telephone marking system, comprising: a plurality of mobile terminals for displaying a marked page and interacting with a user to obtain a telephone number marking information of a user for incoming or outgoing calls; and the plurality of mobiles
  • a local database adapted to the terminal for storing the telephone number and the tag information adapted to the telephone number
  • one or more cloud databases for storing the telephone number and the tag information corresponding to the telephone number, and synchronizing the corresponding tag information To the local database
  • one or more marking devices for dynamically providing associated tagged pages based on the matching of the incoming or outgoing phone numbers of the mobile terminal in the database, for example providing different or same tagged pages according to different matching situations Transmitting the acquired tag information to at least one of the local database and the cloud database
  • one or more verification devices for verifying the tag information of the user
  • the tagging device may also obtain the obtained
  • the tag information is first transmitted to the verification device, the verified tag letter And storing to the cloud database or the local database; where
  • the marking device may be disposed on the mobile terminal, may be disposed in the cloud, or may be configured by a portion disposed in the mobile terminal and a portion disposed in the cloud. If the phone number is successfully matched in the local database, displaying, by the mobile terminal, tag information that is compatible with the phone number; if the phone number fails to match in the local database, triggering the The marking device displays an initial tag page to the user through the mobile terminal, prompting the user to mark the phone number.
  • the phone number is successfully matched in the cloud database, further determining whether there is a correction mark instruction; if the correction mark is not needed, displaying the mark information corresponding to the phone number; if the correction mark is needed, the correction is displayed Marking the page, prompting the user to select or confirm the marked information to be verified; if the phone number fails to match in the cloud database, Then, the marking device is triggered and the initial marking page is displayed to the user through the mobile terminal, and the initial marking information of the user on the telephone number is obtained.
  • the present invention utilizes two-way data transmission between the end user and the cloud server.
  • the terminal user adjusts the telephone module of the system
  • the local monitoring system records the calling number/called number, and passes the local/cloud number.
  • the database identification module attempts to match the associated tag information to help the end user identify the identity and auxiliary information.
  • the database accepts and fully utilizes the tag information provided by each user, and collects, verifies, and summarizes the tag information to form a database with a large and high accuracy rate, and on the other hand, all the tags.
  • the information is shared with all mobile terminal users connected to the database, so that according to the tag information stored in the database, each end user can accurately obtain the unrelated number association tag information when facing a phone number completely unknown to the terminal user. Effectively help end users identify numbers and prevent or reduce users from unrelated phone harassment.
  • the invention also triggers the marking device in combination with the matching result, and displays different marking information interfaces to the user in different situations, such as whether there is no matching marking information, whether it is a questioning number, whether an active marking is required, or the like, or even different Even if the number dialed/received by the user is the same, the user will see different markup interfaces, so that the user's markup can be realized more efficiently, and the number data provided by the user to the database is more effective.
  • the present invention sets a plurality of number types. For some telephone numbers that do not need to be marked to a specific identity, such as express delivery, the user can directly mark the number as a corresponding number type, thereby satisfying the actual number of the user's unused number. Under the premise of marking requirements, the number of numbers that users need to mark is reduced.
  • Figure 1 shows a topological view of a prior art telephone marking system
  • FIG. 2 is a topological view of an embodiment of a telephone marking system provided by the present invention.
  • FIG. 3 is a topological view showing another embodiment of a telephone marking system provided by the present invention.
  • FIG. 4 is a flow chart showing a method of marking a phone according to a first embodiment of the present invention
  • FIG. 5 is a flow chart showing a method of marking a phone according to a second embodiment of the present invention.
  • FIG. 6 is a flow chart showing a method of marking a phone according to a third embodiment of the present invention.
  • FIG. 7 is a flow chart showing a method of marking a phone according to a fourth embodiment of the present invention.
  • Figure 8 is a diagram showing a basic telephone marking page in a specific embodiment of the present invention.
  • FIG. 9 is a schematic diagram showing a dynamic telephone marking page in another specific embodiment of the present invention.
  • Figure 10 is a diagram showing a dynamic phone markup page in still another embodiment of the present invention.
  • Figure 11 is a diagram showing a dynamic phone markup page in still another embodiment of the present invention.
  • Figure 2 shows a topological view of a telephone marking system provided by the present invention. Specifically, the figure shows three mobile terminals 202, 204 and 206, three local databases 208, 210 and 212 respectively adapted to three mobile terminals, three marking devices respectively adapted to three mobile terminals Local terminals 220, 222 and 224, a cloud database 218, a cloud tag device 226, and a verification device 214, wherein the verification device 214 may include a plurality of verification devices (not shown), and may also include one or more ( Third party server 216 is not shown.
  • the mobile terminal 202 is in communication with the local database 208 and the tag device local end 220, which communicates with the tag device local end 220.
  • Mobile terminal 202 The Internet communicates with the cloud tagging device 226 and the cloud database 218.
  • the tag device local end 220 and the cloud tag device 226 are in communication with the verification device 214 via the Internet.
  • the verification device 214 is in communication with the cloud database 218 via the Internet.
  • a third party system 216 communicates with the authentication device 214 and the cloud database 218 via the Internet, respectively.
  • Cloud database 218 is in communication with local database 208.
  • the mobile terminal 202 is taken as an example.
  • the mobile terminal 202 performs bidirectional data transmission with each device in the cloud.
  • the mobile terminal 202 picks up the telephone monitoring module of the telephone marking system (not shown)
  • the local monitoring module records the calling number/called number, and matches the number through the local database 208 or the cloud database 218. And query the identity of the number and related information to help the end user identify.
  • the tag information is triggered in conjunction with the tag device local end 220 or the cloud tag device 226, and different tag interfaces are displayed to different users. Even different users can see different tag interfaces even if the numbers dialed/received are the same.
  • the user provides more efficient number data to the verification device 214.
  • the number data is verified by the verification means 214, and the correct flag information is stored in the cloud database 218 and simultaneously transferred to the local database of the mobile terminal that dials/receives the number thereafter.
  • the phone data in the cloud database 218 can also be updated with the third party system 216.
  • the verification device 214 can also verify the number marked by the user by using the information of the third-party system 216, thereby forming a more accurate and faster end-user contribution telephone number system, and efficiently expanding the number database to help the terminal user to come and go. Identify non-contact tag information to prevent harassment by unrelated unfamiliar calls.
  • the present invention is not limited to the disclosed embodiments.
  • the above mobile terminal, local database, and marking device are not necessarily three as shown in FIG. 1, and the number thereof may be changed correspondingly, and the cloud database, the verification device, and The number of third-party systems can also be changed accordingly.
  • the verification device, the marking device, and the third-party system can run in the cloud, multiple cloud databases, multiple verification devices, multiple marking devices, and multiple third-party systems, etc.
  • the cloud device is managed by one or more cloud servers for task assignment.
  • the local device of the tag device is a sub-module of locally installed software for providing a tag page that triggers the tag locally.
  • the cloud tag device is a sub-module of the cloud server for providing a tag page that triggers a tag in the cloud.
  • the marking device does not distinguish between local and cloud, it may be installed locally only, or may be installed only in the cloud, or it may be a device that is independently installed locally or outside the cloud.
  • mobile terminal 302 is in communication with local database 308
  • mobile terminal 304 is in communication with local database 310
  • mobile terminal 306 is in communication with local database 312
  • mobile terminals 302, 304, 306 and local databases 308, 310, 312 are respectively Communication with the tagging device 326, the cloud database 318, and the verification device 314 is via the Internet.
  • the mobile terminal 302 is taken as an example.
  • the mobile terminal 302 records the calling number/called number, matches the number through the local database 308 or the cloud database 318, and queries the identification information of the number to help the terminal user identify; on the other hand, the marking device 320 is triggered according to the matching result. It also displays different tag interfaces for different users. Even different users will see different tag interfaces even if the numbers dialed/received are the same.
  • the tagging device 320 can prompt the user with an actively tagged interface instructing the user to actively initiate initial tagging of the number.
  • the tagging device 320 may prompt the user to correct the tagged interface, instructing the user to correct the tag information of the number.
  • the result of the user tag is recorded in the cloud database 318; when other mobile terminals make a query match for the number, the result of the tag marked by the user of the mobile terminal 302 is also pushed to the tag interface of other mobile terminals for users of other mobile terminals. Make a selection or confirmation.
  • the tag result marked by the mobile terminal 302 can also be verified by the verification device first, and the verified tag information is updated to the cloud database as a matching result of the number.
  • the tag information in the cloud database can be further updated to the local database, so that the user can perform query matching offline.
  • Fig. 4 is a flow chart showing a telephone marking method of the first embodiment of the present invention. Specifically, the figure shows eight steps.
  • step S101 the phone monitoring module monitors the calling/called number.
  • the phone monitoring module acquires the number dialed by the mobile terminal or the number of the incoming call.
  • step S102 it is determined whether the number matches the number in the local/cloud database.
  • step S103 If the number has a matching number or tag information in the local or cloud database, step S103 is performed, and if there is no matching number or tag information, step S105 is performed.
  • the query matching is performed in at least one of the local/cloud database according to the number acquired by the phone monitoring module.
  • the query matching of the numbers is directly performed in the local database.
  • the number matching query can be preferentially performed in the cloud database.
  • the networked bandwidth of the mobile terminal exceeds a threshold, the number matching query is performed in the cloud database. If the network bandwidth of the mobile terminal is lower than the above threshold, the number matching query is directly performed in the local database.
  • the number matching query is preferentially performed in the local database.
  • the matching fails, the user is prompted to be networked or directly executed in the cloud database. Inquire.
  • Step S103 if there is a matching number, the mobile terminal will directly display the tag information in the local/cloud database that matches the number.
  • the number type can be displayed. For example, it is displayed that the number is a "real estate agent" phone, or that the number is a "business promotion" phone. For some phones, the user does not actually need to tag it to a specific identity number, which is already for the user. enough. Among them, the user can also add, delete and edit the number type according to his own needs, so that the number type is more suitable for the user's usage habits.
  • the user-set number type can be saved only in the local database or saved to the cloud database; the user can also share the self-set number type to the user-specified contact object as needed. Or make it public through a user-specified social account.
  • the number information can also be displayed.
  • information such as the name, address, or business card of the contact or the merchant corresponding to the number is displayed; for example, the activity information of the merchant corresponding to the number, such as the recent preferential activity information, may be displayed.
  • the related prompt can also be displayed. For example, it may display "The number has been marked as a nuisance call by N users" or "The number has been marked as a real estate agent by N users", etc., thereby being able to alert the user to certain harassed or scam calls marked by other users. But the phone number that has not been verified is vigilant.
  • the user may also be prompted to confirm the tag result.
  • step S104 the user believes that the tag information does not match the fact, and then proceeds to step S105.
  • Step S105 After the user's phone hangs up, it is usually asked whether the user confirms the tag information, or asks the user whether the number needs to be actively marked. If the user thinks that the tag information is incorrect or thinks that the number needs to be actively marked, the user continues to execute. Step S105.
  • step S105 the marking device dynamically provides a phone number marking interface according to the matching result, prompting the user to mark the number.
  • the tag device when the local/cloud database does not have tag information matching the number, the tag device is triggered to display the initial tag interface.
  • the tagged page as shown provides the user with the option to mark the phone number as a number of types, for example, the number is "business promotion? real estate agent? harassing phone? fraud fishing? Sell? Other (manual input), the user can select one of them to complete the marking of the phone number.
  • the initial tag interface is also The user may be prompted to manually input and actively mark the number. In this case, preferably, after the user's phone hangs up, the marking device is triggered to pop up the initial marking interface.
  • the tag device displays a correction mark page, prompting the user to correct the number. mark.
  • the correction mark page may prompt the user to confirm the original matching mark information, that is, "Is 13XXXXXXX is a wind express".
  • the correction tag page after receiving an instruction of the user's active tag, the correction tag page prompts the user to select one or more tagged number types of the phone number, that is, the phone number is the default personnel headhunter or Other types.
  • the user directly inputs the phone number according to the displayed correction mark page, and actively marks the phone number.
  • the system in the process of matching the phone number in the local database, when the phone number has matching tag information in the local database, even if the phone number exists in the cloud database, For the tag information to be verified, the system does not actively prompt the correction tag page.
  • the tag information in the local database is used as the tag information matching the number. Only when the user issues a correction mark indication, that is, the user may think that the mark information of the phone number is inaccurate or untrustworthy, and the mark device is actively triggered, and the correction mark page is popped up for the user to correct the mark.
  • Step S106 interacting with the user to complete the marking.
  • the user completes the input through the keyboard, virtual keyboard, mouse, gamepad, handwriting input or ORC technology of the mobile terminal, and can also complete the initial mark or correction mark of the number through voice interaction, two-dimensional code recognition, and the like.
  • the method may further include the step S107, the verification device checks the marking information of the number certificate.
  • the verification device counts the number of marking a number as a certain tag information. If the tag information for a number exceeds a predetermined threshold, then the verification is passed. For example, when a number is marked as the number of real estate agents exceeding a predetermined threshold, such as 300 people, the number is verified as a real estate agent.
  • the verification device counts the number of a certain number marked as a certain tag information for a predetermined time.
  • the tag information for a number exceeds a predetermined threshold, it passes the verification. For example, for a fraudulent phone, it is often frequent to call multiple users for fraud for a period of time, and if the tagged information for the phone number exceeds a predetermined threshold within one day, it is verified as a fraudulent call.
  • the verification device assigns different tag information weights according to different credit levels of different users, and calculates the credibility of the tag information according to the weights.
  • the credibility of the tag information reaches a predetermined threshold, it passes the verification.
  • the user may set different credit levels according to the result of the user's past marking.
  • the tag information of a certain number is counted, the credit rating of the user who provides the corresponding tag information also participates in the calculation, and the calculated credibility and the reservation are compared.
  • the threshold value is judged based on the comparison result.
  • the verification device can record the device information of the user and use it as a unique identification code for marking the identity of the information provider.
  • the system only Accept the correction tag information once.
  • the verification device can also record the geographical location information of the user currently located.
  • the system automatically adds the geographical location information to the marked information, thereby enabling more For precise matching. For another example, it can be further verified in conjunction with a database of a third party system.
  • step S108 is continued, and the cloud/local database is updated according to the result of the verification.
  • the tag information of the number is verified, the verified tag information is used.
  • the tag information for this number is stored in the cloud/local database. If the number or tag information stored in the local/cloud number database is questioned, the user's correction flag information may be recorded and saved in the cloud number database, the number in the local database and the tag information of the number are deleted, and the cloud is The database is set to the challenge number.
  • the tag information of the number and the number in the local database is not deleted, the correction flag information of the user is recorded and saved in the cloud number database and the cloud database number is set as the challenge number.
  • the correction mark information of the challenged number is uploaded and saved in the cloud database, and the number in the cloud database and its correction mark information are verified, and the local database only saves the verified number and its mark information. .
  • the cloud database and the local database are updated according to the verification result, so that each user marks the initial tag information and the correction flag information and the cloud database and/or local before the verification.
  • the original tag information in the database can be used as the matching information of the numbers recorded on the mobile terminal operated by the user, thereby forming a large and accurate database.
  • the tag information of different user tags may be immediately uploaded to the cloud database as the to-be-verified tag information of the number, and then the users of other mobile terminals query and match the number through the cloud number library.
  • one or more to-be-verified flag information associated with the number previously provided by other different users can be known, and the tag page can prompt the user to select from the user, or can prompt the user to confirm it, or prompt the user to input it.
  • the tag is otherwise marked so that the user can know its associated tag information even if it faces a completely strange number.
  • Figure 5 is a flow chart showing a method of telephone marking in accordance with an embodiment of the present invention.
  • step S201 it is determined whether the incoming/outgoing number is a number in the mobile terminal's phone book, if not proceeding to step S202.
  • step S202 it is determined whether the mobile terminal is in a networked state. If the network terminal is not in the networked state, step S203 is continued, and if it is in the networked state, step S303 in FIG. 6 is performed.
  • step S203 it is determined whether the number matches the number in the local database. If there is no match, step S204 is continued, and if yes, step S404 of FIG. 7 is executed.
  • Step S204 triggering the marking device to dynamically provide the associated initial tag page and receive the tag information of the user.
  • the tag interface when there is no tag information matching the number locally, the tag interface prompts the user to perform an initial tag requesting the user to select the type of the incoming/outgoing number, for example, referring to FIG. 8, the phone is "Business Promotion? Real Estate Agents? Harassment Phones? Fraud Fishing? Courier Takeaway? Other (Manual Input)" options.
  • the initial markup interface can be triggered by the set user action, for example, when the user's phone hangs up, triggering the marking device to display the initial markup interface.
  • the initial markup interface can also be actively triggered by the user.
  • the tag information is transmitted to the verification device for tag verification.
  • the user tag information is preferably sent by the tag device to the verification device.
  • the marking device stores the user marking information in a local database and sends it to the verification device by the local database.
  • the number in the local database and the associated tag information are sent to the verification device in real time when the mobile terminal is detected to be connected to the network.
  • the user tag information stored in the local database is sent to the verification device at regular intervals in the local database.
  • the user tag information stored in the local database is transmitted to the verification device.
  • the verification device performs verification according to the tag information of the user.
  • the weight is determined, and the credibility of the tag information is calculated according to the weight.
  • the credibility of the tag information reaches a predetermined threshold, the verification is passed.
  • Step S207 update the local/cloud database, record the corresponding number and its tag information, and store it in the cloud database.
  • the local database is synchronized with the cloud database and updated in real time.
  • the local database is synchronized and updated with the cloud database at regular intervals.
  • the local database is synchronized with the cloud database and updated.
  • Fig. 6 is a flow chart showing a method of telephone marking according to a third embodiment of the present invention.
  • Step S301 determining whether the incoming/outgoing number is a number in the mobile terminal's phone book, and if not, proceeding to step S302.
  • Step S302 determining whether the mobile terminal is in a networked state, if the network is connected, proceeding to step S303, if not, performing step S203 of FIG.
  • Step S303 determining whether the number matches the number in the cloud database, if yes, proceeding to step S304, if not, executing step S204 of FIG.
  • Step S304 displaying the tag information of the number in the cloud database.
  • step S305 it is determined whether there is a question about the tag information of the number in the cloud database, and if yes, step S306 is performed.
  • Step S306 triggering the marking device, displaying the correction mark page through the mobile terminal, and receiving the correction mark information of the user.
  • the correction tag interface may list the plurality of to-be-identified accounts associated with the number stored in the cloud database at one time or one by one. Mark one or more of the information, mention Show the user to make a selection. Referring to FIG. 9 or FIG. 10, details are not described herein.
  • the correction mark interface may also prompt the user to perform a custom mark.
  • the correction mark interface can be triggered by the set user operation, for example, when the user's phone hangs up, the mark device is triggered to display the correction mark interface.
  • the correction mark interface can also be actively triggered by the user. For example, when the user challenges the matched mark information, the mark device can be actively triggered to display the mark interface.
  • step S307 the cloud database is updated, the number is set as the challenge number, and the associated tag information is saved.
  • Step S308 the phone number and the to-be-verified flag information are transmitted to the verification device.
  • the to-be-verified tag information is preferably sent by the tag device to the verification device.
  • the tagging device stores the user to be verified tag information in a cloud or local database and sends it to the verification device by the cloud or local database.
  • the to-be-verified tag information in the cloud or local database is sent to the verification device in real time when the mobile terminal is detected to be networked.
  • the to-be-verified flag information stored in the cloud or local database is sent to the verification device at regular intervals in the cloud or local database.
  • the to-be-verified flag information reaches a certain threshold, the to-be-verified tag information stored in the cloud or the local database is sent to the verification device.
  • the to-be-verified tag information may include initial tag information and correction tag information, and the uploading of the two may be uploaded in real time according to different manners, for example, the correction tag information, and the initial tag information is uploaded once for a period of time.
  • step S309 the verification device performs verification according to the tag information of the user.
  • different credit levels of different users are assigned different weights of the tag information, and the credibility of the tag information is calculated according to the weight.
  • the credibility of the tag information reaches a predetermined threshold, the verification is passed.
  • the initial tag information and the correction tag information may adopt different verification methods.
  • the initial tag information may be verified by: when a number is marked as the initial tag information reaches a predetermined threshold, the initial tag information is verified.
  • the correction mark information can be verified by different credit ratings of different users being assigned different weights of correction mark information, and calculating the credibility of the correction mark information according to the weight, when the credibility of the correction mark information reaches a predetermined threshold , then pass the verification.
  • Setting different verification methods for the initial tag information and the correction tag information is determined based on the respective characteristics of the initial tag information and the correction tag information, and the initial tag information is a pair of numbers when there is no data for the number in the local/cloud database.
  • the initial identification, and the correction mark information is a correction of the original matching mark information in the local/cloud database, and adopting different verification methods for the two can improve the efficiency of the verification result, so that more strange numbers are recognized by the user in time, and The numbers in the database are more accurate.
  • the initial tag information and the correction tag information may also take the same verification mode to simplify the computational complexity.
  • Step S310 when passing the verification, updating the cloud database and the local database.
  • the verified tag information in the cloud database and its corresponding phone number are synchronized to the local database.
  • the tag information of the challenge number is retained in the cloud database, but the tag information of the challenge number is deleted from the local database.
  • the local database is synchronized with the cloud database and updated in real time.
  • the local database is synchronized and updated with the cloud database at regular intervals.
  • the local database is synchronized with the cloud database and updated.
  • step S304 it is determined whether the number is a question number. If the number is not a challenge number, step S304 is continued. If the number is a challenge number, the marking device is triggered to display the correction mark page through the mobile terminal and receive the correction mark information of the user.
  • the correction mark interface in the similar figure may be listed once or sequentially.
  • the dynamic tag page preferably asks the user if the number is the tag information to be verified. For example, is the number a real estate agent? Or; or, the correction mark page asks the user if the number is a pending mark or other information, for example, "Is the number a real estate agent?" Or other (manual input).
  • the correction mark page preferably asks the user that the number is the first to-be-verified flag information, and the second to-be-checked Verify the tag information or other, for example, "Is the number a real estate agent? Business sales? Or other (manual input).
  • step S308 After receiving the correction flag information of the user, it is the same as step S308 to step S310, and specifically, details are not described.
  • Fig. 7 is a flow chart showing a telephone marking method of a fourth embodiment of the present invention.
  • Step S401 determining whether the incoming/outgoing number is a number in the mobile terminal's phone book, and if not, proceeding to step S402.
  • step S402 it is determined whether the mobile terminal is in a networked state, if it is not in the networked state, step S403 is continued, and if it is in a networked state, step S303 in Fig. 6 is performed.
  • Step S403 determining whether the number matches the number in the local database, if yes, proceeding to step S404, and if not, executing step S204 of FIG.
  • Step S404 displaying, on the mobile terminal, the tag stored in the local database by the number. information.
  • Step S405 detecting whether the user issues an instruction to correct the mark.
  • Step S406 is performed.
  • Step S406 triggering the marking device, displaying the correction mark page through the mobile terminal, and receiving the mark information of the user.
  • the correction markup interface asks the user to select the type of the incoming/outgoing number, for example, to give the call "business promotion? real estate agent? harassment call? fraud fishing? express takeaway? Other (manual input )"s Choice.
  • the user is prompted to confirm the original matching tag information or select a number type by a similarly labeled correction flag interface.
  • the correction mark interface may also prompt the user to make a custom mark.
  • step S407 the verification device performs verification according to the tag information of the user.
  • different credit levels of different users are assigned different weights of the tag information, and the credibility of the tag information is calculated according to the weight.
  • the credibility of the tag information reaches a predetermined threshold, the verification is passed.
  • Step S408 updating the cloud database and the local database according to the verification result, and The number and its tag information are stored in the cloud database and the local database.
  • the local database is synchronized with the cloud database and updated in real time.
  • the local database is synchronized and updated with the cloud database at regular intervals.
  • the local database is synchronized with the cloud database and updated.
  • Figure 8 shows a schematic diagram of an initial markup page in one embodiment of the invention.
  • the initial tag page popped up by the mobile terminal is as shown in FIG. 8 , wherein the initial tag page displays the common number type set by the system, such as business promotion, real estate agent. , harassing calls, fraud fishing, express delivery, etc., so that users can quickly provide the marking information of the number.
  • the tag information Preferably, there is also an option to share the tag information, store the number in the blacklist, and deposit the contact.
  • the correction mark interface popped up by the mobile terminal is also as shown in FIG. 8.
  • the corrections page gives the phone the option of "Business Promotion? Real Estate Agent? Harassment Phone? Fraud Fishing? Courier Takeout? Other (Manual Entry)", where the page displays the option to tag the number by a different user. Multiple pending tag information.
  • a correction mark page as shown in FIG. 9 can be displayed.
  • the correction mark page gives the question "138******** is the wind express?" and gives the "wrong", “right” and “I don't know” options, prompting the user Confirm the number of the pending verification of the number, ie “Wind Express”.
  • a correction mark page as shown in FIG. 9 can also be displayed.
  • the correction markup page gives the question "What is the phone number for 138********?” and gives the options for "Personnel Headhunter", “Other Types", and "OK”.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种电话标记方法和电话标记系统，所述方法包括：获取移动终端来电或者去电的电话号码；将所述获取的电话号码在本地或者云端数据库中至少一个进行匹配；根据所述电话号码在所述本地或者云端数据库是否匹配成功以及是否为质疑号码，向用户显示不同的标记页面，提示用户对所述电话号码进行标记或对所述号码的标记信息进行确认；获取用户根据所述标记页面对所述电话号码的标记信息并对其进行标记验证；以及根据所述标记验证的结果，更新所述云端数据库和所述本地数据库。本发明充分利用了每个用户向数据库所贡献的标记信息，形成庞大而精准的号码数据库，并将标记信息分享给连接数据库的其它移动终端用户，有效地帮助用户实现号码识别。

Description

电话号码标记方法及系统
本申请要求2013年11月15日提交中国专利局、申请号为201310574069.0、发明名称为“电话号码标记方法及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及数据处理领域，尤其涉及移动通讯对号码的智能标记处理。
背景技术
将电话号码与呼叫方建立关联是电话标记系统的设立初衷。传统的电话标记系统中数据库大多是本地的，其通常采用这样的方式进行号码标记；比如在监听到用户主叫/被叫时，对电话号码数据进行与数据库内的电话号码进行匹配，若有匹配的号码，则将与该号码相关的信息在移动终端中进行显示。若没有匹配的号码，则并不显示该号码的标记信息或者显示“未知号码”。手机中的联系人簿便是这样的例子。传统的标记系统由于其数据库内容的更新仅能够在数据库端进行人工操作，因此识别范围很小。
近年来，随着移动电话的普及以及云技术的不断发展，一些改进的电话标记系统应运而生。其中，用户在移动终端对号码进行标记了之后，还可以将标记的数据传输至云端服务器进行保存。
如图1所示的现有技术的电话号码标记系统，其示出了三个移动终端102、104以及106，分别与三个移动终端相适应的三个本地数据库108、110以及112，分别与三个移动终端相适应的三个标记装置本地端120、122以及124，和一个云端数据库118。其中，移动终端102本地电话监听(图中未示出)监听其主机/被叫号码，并触发与其相适应的标记装置本地端120；标记装置本地端120提供给移动中102一个标记界面，供用户进行标记。比如，在一个实施例中，用户接到某重要电话或者某银行的保险推销电话之后，将该号码进行了 对应的标记，并通过标记装置本地端将该标记信息上传至云端服务器，从而保证当用户更换移动电话或电话卡时，仍然能获取原先标记过的电话号码以及对应的标记信息。
然而，这种号码标记系统中，用户仍然仅能对自己曾经接听过的号码进行标记，也就是说，不同用户所采用的号码标记的数据库都是相对独立的，号码识别范围小。而且，对于每一个号码都需要用户自己进行手工操作，操作繁琐。
而且，对于不同号码，用户的标识需求事实上是不同的，对于有些号码，比如快递外卖，如果不进行标记，用户识别和联系都不方便，如果进行识别，用户使用频率很低，而且快递外卖人员流动性很大，对每一个号码都进行标记，并不现实。
发明内容
本发明提供一种电话标记方法，其特征在于，包括：获取移动终端来电或者去电的电话号码；将所述获取的电话号码在本地或者云端数据库中至少一个进行匹配；根据所述电话号码在所述本地或者云端数据库是否匹配成功以及是否为质疑号码，向用户显示不同的标记页面，提示用户对所述电话号码进行标记或对所述号码的标记信息进行确认；获取用户根据所述标记页面对所述电话号码的标记信息并对其进行标记验证；以及根据所述标记验证的结果，更新所述云端数据库和所述本地数据库。
优选地，若所述电话号码在所述本地数据库中匹配成功，则显示与所述电话号码相适应的标记信息；若所述电话号码在所述本地数据库中匹配失败，则显示初始标记页面，提示用户对所述电话号码进行标记。
优选地，若所述电话号码在所述云端数据库中匹配成功，则进一步判断是否存在更正标记指令；若不需要更正标记，则显示与所述电话号码相适应的标记信息；若需要更正标记，则显示更正标记页面， 提示用户对待验证的标记信息进行选择或确认；若所述电话号码在所述云端数据库中匹配失败，则显示初始标记页面，获取用户对所述电话号码的初始标记信息。
本发明还提供一种电话标记系统，其特征在于，包括：多个移动终端，用于显示标记页面并与用户交互以获取用户对来电或者去电的电话号码标记信息；与所述多个移动终端相适应的本地数据库，用于储存电话号码以及与电话号码相适应的标记信息；一个或多个云端数据库，用于储存电话号码以及与电话号码相适应的标记信息，并将相应标记信息同步至本地数据库中；一个或多个标记装置，用于根据移动终端来电或者去电的电话号码在数据库中的匹配情况动态提供关联的标记页面，例如根据不同的匹配情况提供不同或同一个标记页面，并将所获取的标记信息传输至所述本地数据库和所述云端数据库中至少一个；一个或多个验证装置，用于对用户的标记信息进行验证，；所述标记装置还可将获取的标记信息先传输至所述验证装置，经过验证的标记信息再存储至所述云端数据库或所述本地数据库；其中，所述移动终端与所述本地数据库，或所述云端数据库，或所述本地数据库以及所述云端数据库相互通信，所述移动终端还和所述标记装置相通信，所述标记装置还可和所述验证装置相通信，所述验证装置还可与所述云端数据库和所述本地数据库中至少一个相通信。
优选地，所述标记装置可设置于所述移动终端，可设置于云端，或者由设置于所述移动终端的部分与设置于云端的部分共同构成。若所述电话号码在所述本地数据库中匹配成功，则通过所述移动终端显示与所述电话号码相适应的标记信息；若所述电话号码在所述本地数据库中匹配失败，则触发所述标记装置并通过所述移动终端向用户显示初始标记页面，提示用户对所述电话号码进行标记。若所述电话号码在所述云端数据库中匹配成功，则进一步判断是否存在更正标记指令；若不需要更正标记，则显示与所述电话号码相适应的标记信息；若需要更正标记，则显示更正标记页面，提示用户对待验证的标记信息进行选择或确认；若所述电话号码在所述云端数据库中匹配失败， 则触发所述标记装置并通过所述移动终端向用户显示初始标记页面，获取用户对所述电话号码的初始标记信息。
相较于现有技术，本发明利用终端用户和云端服务器的双向数据传输，当终端用户调起系统的电话模块，本地监听系统会将主叫号码/被叫号码记录下来，通过本地/云端号码数据库识别模块尝试匹配出关联的标记信息，帮助终端用户辨识号码身份及辅助信息。在本发明的实施方式中，数据库一方面接纳并充分利用每个用户提供的标记信息，通过对标记信息进行收集、验证、汇总，形成庞大而准确率高的数据库，另一方面又将所有标记信息与所有连接至数据库的移动终端用户共享，从而使得根据数据库存储的标记信息，每个终端用户在面对对其而言完全陌生的电话号码时，能够精准的获取该陌生号码关联标记信息，有效帮助终端用户进行号码识别，防止或减少用户受到不相关的电话骚扰。
本发明还结合匹配结果触发标记装置，在不同的情况下，例如是否不存在匹配的标记信息、是否为质疑号码、是否需要主动标记等等，展示给用户不同的标记信息界面，甚至是不同的用户即使拨打/接收的号码相同，也会看到不同的标记界面，从而能够更加高效地实现用户的标记，也使用户向数据库所提供的号码数据更加有效。
进一步的，本发明设置了多种号码类型，对于一些无需标记到具体身份的电话号码，例如快递外卖等，用户可直接将号码标记为对应的号码类型，从而在满足了用户对不用号码的实际标记需求的前提下，减轻了用户需要标记的号码数量。
附图说明
通过参照附图详细描述其示例实施方式，本发明的上述和其它特征及优点将变得更加明显。
图1示出了现有技术中电话标记系统的拓扑图；
图2示出了本发明提供的电话标记系统一种实施方式的拓扑图；
图3示出了本发明提供的电话标记系统另一种实施方式的拓扑图；
图4示出了本发明第一实施例的电话标记方法的流程示意图；
图5示出了本发明第二实施例的电话标记方法的流程示意图；
图6示出了本发明第三实施例的电话标记方法的流程示意图；
图7示出了本发明第四实施例的电话标记方法的流程示意图；
图8示出了本发明一种具体实施例中基本电话标记页面的示意图；
图9示出了本发明另一种具体实施例中动态电话标记页面的示意图；
图10示出了本发明又一种具体实施例中动态电话标记页面的示意图；以及
图11示出了本发明又一种具体实施例中动态电话标记页面的示意图。
具体实施方式
现在将参考附图更全面地描述示例实施方式。
图2示出了本发明提供的电话标记系统的拓扑图。具体地，本图示出了三个移动终端202、204以及206，分别与三个移动终端相适应的三个本地数据库208、210以及212，分别与三个移动终端相适应的三个标记装置本地端220、222以及224，一个云端数据库218，一个云端标记装置226，验证装置214，其中，验证装置214可包括多个验证装置(图中未示出)，还可包括一个或多个(未示出)第三方服务器216。
移动终端202与本地数据库208以及标记装置本地端220相通信，本地数据库208与标记装置本地端220相通信。移动终端202通 过互联网与云端标记装置226以及云端数据库218相通信。标记装置本地端220以及云端标记装置226通过互联网与验证装置214相通信。验证装置214通过互联网与云端数据库218相通信。一第三方系统216分别通过互联网与验证装置214以及云端数据库218相通信。云端数据库218与本地数据库208相通信。移动终端204及其本地数据库210、标记装置本地端212，移动终端206及其本地数据库212、标记装置本地端224与其他各装置的通信关系和移动终端202及其本地数据库208、标记装置本地端220与其他各装置的通信关系相同。
具体地，以移动终端202为例。移动终端202与云端各装置进行双向数据传输。当移动终端202调起电话标记系统的电话监听模块(图中未示出)，本地监听模块会将主叫号码/被叫号码记录下来，通过本地数据库208或者云端数据库218对该号码进行匹配，并查询该号码身份以及相关信息，帮助终端用户辨识。同时结合标记信息触发标记装置本地端220或者云端标记装置226，并展示给不同用户不同的标记界面，甚至是不同的用户即使拨打/接收的号码相同，也会看到不同的标记界面。用户向验证装置214提供更有效的号码数据。号码数据经过验证装置214检验，将检验正确的标记信息存储到云端数据库218中，同时传递给在此之后拨打/接收该号码的移动终端的本地数据库中。其中，云端数据库218中的电话数据还可以与第三方系统216交互更新。验证装置214也可以借助第三方系统216的信息对用户标记的号码进行验证，进而形成一套更准确更迅速的终端用户贡献电话号码系统，高效扩充了号码数据库，帮助终端用户在来去电时识别非联系人标记信息，防止被不相关的陌生电话骚扰。
其中，图2具体地示出和描述了本发明的示例性实施方式。应该理解，本发明不限于所公开的实施方式，例如，上述移动终端、本地数据库、标记装置并不必须为于图1所示的三个，其数量可以相应变化，并且云端数据库、验证装置以及第三方系统的数量也可以有相应的变化。例如，验证装置、标记装置和第三方系统可运行在云端，多个云端数据库、多个验证装置、多个标记装置以及多个第三方系统等 云端的装置由一个或多个云端服务器进行任务的分配管理。
在其中一个变化例中，标记装置本地端是本地安装的软件的一个子模块，用于提供在本地触发标记的标记页面。云端标记装置是云端服务器的一个子模块，用于提供在云端触发标记的标记页面。
在另一个变化例中，标记装置并不区分本地和云端，其可以仅安装在本地，也可以仅安装在云端，或者还可以为独立设置于本地或者云端之外的装置。参考图3，移动终端302与本地数据库308相通信，移动终端304与本地数据库310相通信，移动终端306与本地数据库312相通信，移动终端302、304、306和本地数据库308、310、312分别通过互联网与标记装置326、云端数据库318以及验证装置314相通信。
具体地，以移动终端302为例。移动终端302记录主叫号码/被叫号码，通过本地数据库308或者云端数据库318对该号码进行匹配，查询该号码的标识信息，帮助终端用户辨识；另一方面，根据匹配结果触发标记装置320，并展示给不同用户不同的标记界面，甚至是不同的用户即使拨打/接收的号码相同，也会看到不同的标记界面。
例如，当电话号码在本地数据库308或者云端数据库318中不存在匹配结果时，标记装置320可提示给用户主动标记的界面，指示用户对该号码主动进行初始标记。当移动终端302的用户对电话号码原有匹配的标记信息存疑时，标记装置320可提示给用户更正标记的界面，指示用户对该号码的标记信息进行更正。
用户标记的结果被记录在云端数据库318中；当其它移动终端对该号码进行查询匹配时由移动终端302的用户进行标记的结果也会推送至其它移动终端的标记界面，供其它移动终端的用户进行选择或确认。
由移动终端302标记的标记结果也可先通过验证装置进行验证，并将验证后的标记信息更新至云端数据库，作为该号码的匹配结果。 云端数据库中的标记信息还可进一步更新至本地数据库，便于用户离线进行查询匹配。
图4示出了本发明第一实施例的电话标记方法的流程图。具体地，本图示出了8个步骤。
步骤S101，电话监听模块监听主叫/被叫号码。
具体地，当移动终端拨打号码或者接收来电时，电话监听模块获取移动终端拨打的号码或者来电的号码。
步骤S102，判断该号码是否与本地/云端数据库中的号码匹配。
若该号码在本地或云端数据库中存在匹配的号码或标记信息则执行步骤S103，若没有匹配的号码或标记信息则执行步骤S105。
具体地，根据电话监听模块获取的号码在本地/云端数据库中至少一个进行查询匹配。
优选地，若移动终端并没有处于联网状态，则直接在本地数据库中进行号码的查询匹配。若移动终端处于联网状态，可优先在云端数据库中进行号码的查询匹配。在一个变化例中，若移动终端的联网带宽超过一阈值时，则在云端数据库中进行号码的查询匹配。若移动终端的联网带宽低于上述阈值时，则直接在本地数据库中进行号码的查询匹配。
在另一个变化例中，还可根据用户的设置，无论移动终端是否处于联网状态，优先在本地数据库中进行号码的查询匹配，当匹配失败时，再提示用户联网或直接执行在云端数据库中的查询。
步骤S103，若有匹配号码，则移动终端将直接显示本地/云端数据库中与该号码匹配的标记信息。具体来说，当该电话号码匹配成功时，可显示其号码类型。例如，显示该号码为一“房产中介”的电话，或者显示该号码为一“业务推销”的电话。对于某些电话，用户事实上并不需要将其标记至具体身份的号码，号码类型对于用户而言已经 足够。其中，用户还可根据自身需要对号码类型进行增加、删除和编辑，使得号码类型更适合于用户的使用习惯。在一种具体实施例中，用户自设的号码类型可仅保存在本地数据库，也可保存至云端数据库；用户还可根据需要，将其自设的号码类型分享至用户指定的联系人对象，或通过用户指定的社交账户进行公开。
具体来说，当该电话号码匹配成功时，还可显示其号码信息。例如，当显示的是号码信息时，显示该号码对应的联系人或商户的名称、地址或者名片等信息；又例如，还可显示该号码对应的商户的活动信息，如近期的优惠活动信息等。
具体来说，当该电话号码匹配成功时，还可显示相关的提示语。例如，可显示“该号码已被N个用户标记为骚扰电话”或者“该号码已被N个用户标记为房产中介”等，从而能够提醒用户对某些被其他用户标记为骚扰电话或诈骗电话但尚未得以验证的电话号码加以警惕。
具体来说，当该电话号码匹配成功时，还可提示用户对标记结果加以确认。
步骤S104，用户认为该标记信息与事实不符，则继续执行步骤S105。
具体地，通常在用户的电话挂断后，询问用户是否确认该标记信息，或者询问用户是否需要主动标记该号码，若用户认为该标记信息有误或者认为需要主动标记该号码时，则继续执行步骤S105。
步骤S105，标记装置根据匹配结果动态的提供电话号码标记界面，提示用户对号码进行标记。
在一种实施方式，在本地/云端数据库没有与该号码相匹配的标记信息时，触发标记装置，显示初始标记界面。参考图8，如图所示的标记页面，提供给用户将该电话号码标记为若干号码类型的选项，例如该号码是“业务推销？房产中介？骚扰电话？诈骗钓鱼？快递外 卖？其他(手动输入)”，用户可以选择其中之一从而完成对该电话号码的标记。在另一种实施方式中，在本地/云端数据库没有与该号码相匹配的标记信息时，初始标记界面还可提示用户直接手动输入，主动对该号码进行标记。这种情况下，优选地，用户电话挂断后，触发标记装置，弹出初始标记界面。
在另一种实施方式中，在本地/云端数据库中有与该号码相匹配的标记信息，但用户认为该匹配的标记信息有误时，标记装置显示更正标记页面，提示用户对该号码进行更正标记。
例如，参考图9，更正标记页面可提示用户对原有的匹配的标记信息，即“13XXXXXXXXX是否是如风快递”，进行确认。又例如，参考图10，当接收到用户主动标记的指令后，更正标记页面提示用户对电话号码的一种或多种已标记的号码类型进行选择，即该电话号码为默认的人事猎头或是其它类型。又例如，参考图11，用户直接根据所显示的更正标记页面进行手动输入，主动对该电话号码进行标记。
在另一种变化例中，在本地数据库中对电话号码进行匹配的过程中，当该电话号码在本地数据库中存在相匹配的标记信息，此时，即使该电话号码在云端数据库中存在多个待验证的标记信息，系统也并不主动提示更正标记页面，默认将本地数据库中的标记信息作为该号码匹配的标记信息。只有当用户发出更正标记指示时，即用户有可能认为该电话号码的标记信息不准确或不可信，主动触发标记装置，此时才会弹出更正标记页面，供用户进行更正标记。
步骤S106，与用户交互完成标记。
其中，用户除了通过移动终端的键盘、虚拟键盘、鼠标、游戏手柄、手写输入或ORC技术完成输入外，还可以通过语音交互、二维码识别等完成号码的初始标记或更正标记。
此外，还可包括步骤S107，验证装置对号码的标记信息进行验 证。
具体地，可以有多种验证方式。
在一种实施例中，验证装置对将某号码标记为某一标记信息的数目进行统计。若对一号码的标记信息超过预定阈值时，则通过验证。例如，当将某号码标记为房产中介的数量超过预定阈值时，比如300人时，则将该号码验证为房产中介。
在另一种实施例中，验证装置对在一预定时间内将某号码标记为某一标记信息的数目进行统计。当对一号码的标记信息超过预定阈值时，则通过验证。例如，对于诈骗电话，其通常在一段时间内会频繁拨打多名用户实行诈骗，若在一天之内，对该电话号码的标记信息超过预定阈值，则将其验证为诈骗电话。
在又一种实施例中，验证装置根据不同用户的不同信用等级将其赋予不同的标记信息权重，并根据权重计算标记信息的可信度。当标记信息的可信度到达一预定阈值时，则通过验证。例如，可根据用户以往标记的结果设置该用户的不同信用等级，当对某号码的标记信息进行统计时，提供对应标记信息的用户的信用等级也参与计算，比较计算出来的可信度与预定阈值，根据比较结果判断是否通过验证。
在上述验证过程中，当用户标记时，验证装置可以记录用户的设备信息，并将其作为标记信息提供方身份的唯一标识码，当同一用户对同一个号码进行多次更正标记时，系统仅接受一次更正标记信息。此外，验证装置还可以记录用户当前所处的地理位置信息，当用户将某个电话号码标记为某个全国性商户时，则系统自动在该标记信息上添加其地理位置信息，从而能够实现更为精确的匹配。再例如，还可以结合第三方系统的数据库进一步验证。
在验证的基础上，继续执行步骤S108，根据验证的结果对云端/本地数据库进行更新。
具体地，若号码的标记信息通过验证，则将验证后的标记信息作 为该号码的标记信息存入云端/本地数据库。若本地/云端的号码数据库中所存储的号码或标记信息被质疑时，可将用户的更正标记信息记录并保存在云端号码数据库，删除本地数据库中该号码与该号码的标记信息，并将云端数据库该号码设为质疑号码。在一个变化例中，不删除本地数据库中该号码与该号码的标记信息，将用户的更正标记信息记录并保存在云端号码数据库并将云端数据库该号码设为质疑号码。在另一个变化例中，将被质疑的号码的更正标记信息上传并保存在云端数据库，对云端数据库中的号码及其更正标记信息进行验证，并且本地数据库仅保存通过验证的号码及其标记信息。
上述实施方式中，对用户标记信息进行验证之后，再根据验证的结果更新云端数据库和本地数据库，使得在验证之前，每个用户自己标记的初始标记信息和更正标记信息以及云端数据库和/或本地数据库中原有的标记信息均可作为该用户操作的移动终端上所记录号码的匹配信息，从而形成庞大而精准的数据库。在另一种实施方式中，也可先将不同用户标记的标记信息即时上传至云端数据库，作为该号码的待验证标记信息，此后当其他移动终端的用户通过云端号码库对该号码进行查询匹配时，即可获知此前由其他不同用户所提供的与该号码关联的一个或多个待验证标记信息，标记页面可提示用户从中进行选择，或可提示用户对其进行确认，或提示用户自行输入，对该号码进行其它标记，从而使得用户即使面对完全陌生的号码，也能获知其相关联的标记信息。
图5示出了本发明一种具体实施例的电话标记方法的流程图。
步骤S201，判断来电/去电号码是否是该移动终端电话簿中的号码，若不是继续执行步骤S202。
步骤S202，判断移动终端是否处于联网状态，若不处于联网状态继续执行步骤S203，若处于联网状态则执行图6步骤S303。
步骤S203，判断该号码与本地数据库中的号码是否匹配，若不匹配则继续执行步骤S204，若匹配则执行图7步骤S404。
步骤S204，触发标记装置，动态提供关联的初始标记页面，并接收用户的标记信息。
在一个实施例中，在本地没有与该号码相匹配的标记信息时，标记界面提示用户进行初始标记，请求用户对来电/去电号码的类型进行选择，例如参考图8，给出该电话是“业务推销？房产中介？骚扰电话？诈骗钓鱼？快递外卖？其他(手动输入)”的选择。
初始标记界面可由所设定的用户操作进行触发，例如，当用户电话挂断后，触发标记装置，显示初始标记界面。在另一种变化例中，初始标记界面也可由用户主动触发。
接收到用户的标记信息后，继续步骤S205，将所述标记信息传输至验证装置进行标记验证。
在一个实施例中，用户标记信息优选地由标记装置发送至验证装置。在一个变化例中，标记装置将用户标记信息存入本地数据库中，并由本地数据库发送至验证装置。
优选地，本地数据库中的号码及关联的标记信息在检测到移动终端联网时，实时向验证装置发送。在一个变化例中，本地数据库中每隔一定的时间，将储存在本地数据库中的用户标记信息发送至验证装置。在又一个变化例中，当用户标记信息达到一定阈值时，将储存在本地数据库中的用户标记信息发送至验证装置。步骤S206，验证装置根据用户的标记信息进行验证。
具体地，可以有多种验证方式。
例如，若将一号码标记为某一标记信息的数量超过预定阈值时，则通过验证。
又例如，在一预定时间内，将一号码标记为某一标记信息的数量超过预定阈值时，则通过验证。
再例如，不同用户的不同信用等级被赋有不同的标记信息的权 重，并根据权重计算标记信息的可信度，当标记信息的可信度到达一预定阈值时，则通过验证。
再例如，还可以结合第三方系统的数据库进一步验证。
步骤S207，根据验证结果，更新本地/云端数据库，记录对应的号码及其标记信息，并存入云端数据库。
优选地，在检测到移动终端联网时，实时的将本地数据库与云端数据库进行同步并更新。在一个变化例中，每隔一定的时间，将本地数据库与云端数据库进行同步并更新。在又一个变化例中，当更新的号码及其标记信息的数量达到一定阈值时，将本地数据库与云端数据库进行同步并更新。
图6示出了本发明第三实施例的电话标记方法的流程示意图。
步骤S301，判断来电/去电号码是否是该移动终端电话簿中的号码，若不是则继续执行步骤S302。
步骤S302，判断移动终端是否处于联网状态，若联网则继续执行步骤S303，若不联网则执行图5步骤S203。
步骤S303，判断该号码与云端数据库中的号码是否匹配，若匹配则继续执行步骤S304，若不匹配则执行图5步骤S204。
步骤S304，显示该号码在云端数据库中的标记信息。
步骤S305，判断是否对云端数据库中该号码的标记信息有质疑，如果是则执行步骤S306。
步骤S306，触发标记装置，通过移动终端显示更正标记页面，并接收用户的更正标记信息。
在一种实施方式中，在云端号码数据库中有不止一个与该号码相匹配的待验证标记信息，更正标记界面可一次性或逐次列出云端数据库所存储的与该号码关联的多个待验证标记信息中的一个或多个，提 示用户进行选择。参考图9或图10，在此不予赘述。
在另一种实施方式中，参考图11，更正标记界面还可提示用户进行自定义标记。
更正标记界面可由所设定的用户操作进行触发，例如，当用户电话挂断后，触发标记装置，显示更正标记界面。在另一种变化例中，更正标记界面也可由用户主动触发，例如当用户对所匹配的标记信息进行质疑时，可主动触发标记装置，显示标记界面。
步骤S307，更新云端数据库，将该号码设为质疑号码并保存关联的标记信息。
步骤S308，将电话号码及待验证标记信息传输至验证装置。
在一个实施例中，待验证标记信息优选地由标记装置发送至验证装置。在一个变化例中，标记装置将用户待验证标记信息存入云端或本地数据库中，并由云端或本地数据库发送至验证装置。
优选地，云端或本地数据库中的待验证标记信息在检测到移动终端联网时，实时向验证装置发送。在一个变化例中，云端或本地数据库中每隔一定的时间，将储存在云端或本地数据库中的待验证标记信息发送至验证装置。在又一个变化例中，当待验证标记信息达到一定阈值时，将储存在云端或本地数据库中的待验证标记信息发送至验证装置。在又一变化例中，待验证标记信息可包括初始标记信息以及更正标记信息，两者的上传可以根据不同方式，例如更正标记信息为实时上传，初始标记信息为一段时间上传一次。本领域技术人员可以结合现有技术实现更多的变化例，在此不予赘述。
步骤S309，验证装置根据用户的标记信息进行验证。
具体地，可以有多种验证方式。
例如，若将一号码标记为某一标记信息的数量超过预定阈值时，则通过验证。
又例如，在一预定时间内，将一号码标记为某一标记信息的数量超过预定阈值时，则通过验证。
再例如，不同用户的不同信用等级被赋有不同的标记信息的权重，并根据权重计算标记信息的可信度，当标记信息的可信度到达一预定阈值时，则通过验证。
再例如，还可以结合第三方系统的数据库进一步验证。
此外，初始标记信息和更正标记信息可采取不同的验证方式，例如，初始标记信息可通过如下方式验证：当将一号码标记为该初始标记信息达到一预定阈值时，该初始标记信息通过验证。更正标记信息可通过如下方式验证：不同用户的不同信用等级被赋有不同的更正标记信息的权重，并根据权重计算更正标记信息的可信度，当更正标记信息的可信度到达一预定阈值时，则通过验证。对初始标记信息和更正标记信息设置不同的验证方式正是基于初始标记信息和更正标记信息各自的特性决定的，初始标记信息是在本地/云端数据库中不存在对号码的任何数据时对号码的初次识别，而更正标记信息是对本地/云端数据库中原有匹配的标记信息的更正，对两者采取不同的验证方式能够提高验证结果的效率，使更多的陌生号码及时被用户识别，以及使得数据库中的号码具有更高的准确性。在其它实施例中，初始标记信息和更正标记信息也可采取相同的验证方式，以简化运算复杂度。
步骤S310，当通过验证时，更新云端数据库以及本地数据库。优选地，仅将云端数据库中通过验证的标记信息及其对应的电话号码同步至本地数据库。在一个变化例中，未通过验证时，在云端数据库保留该质疑号码的标记信息，但将该质疑号码的标记信息从本地数据库中删除。
优选地，在检测到移动终端联网时，实时的将本地数据库与云端数据库进行同步并更新。在一个变化例中，每隔一定的时间，将本地数据库与云端数据库进行同步并更新。在又一个变化例中，当更新的 信息达到一定阈值时，将本地数据库与云端数据库进行同步并更新。
在上述实施例的一个变化例中，步骤S304之前，判断该号码是否为质疑号码，若该号码不为质疑号码，则继续执行步骤S304。若该号码为质疑号码，则触发标记装置，通过移动终端显示更正标记页面，并接收用户的更正标记信息。
在一种实施方式中，在云端号码数据库中有不止一个与该号码相匹配的待验证标记信息，参考图9或图10，通过类似图示中的更正标记界面，可一次性或逐次列出云端数据库所存储的与该号码关联的多个待验证标记信息中的一个或多个，提示用户进行选择。例如，在一个变化例中，当一个号码只有一个待验证标记信息，则动态的标记页面优选地，询问用户该号码是否为该待验证标记信息。例如，该号码是否为房产中介？”；或者，更正标记页面询问用户该号码是某待验证标记信息或其他，例如，“该号码是房产中介？或者其他(手动输入)”。又例如，在另一个变化例中，一个号码有多个待验证标记信息，则更正标记页面优选地，询问用户该号码是第一待验证标记信息、第二待验证标记信息或者其他，例如，“该号码是房产中介？业务推销？或者其他(手动输入)”。
接收用户的更正标记信息后，同步骤S308至步骤S310相同，具体地，不予赘述。
图7示出了本发明第四实施例的电话标记方法的流程图。
步骤S401，判断来电/去电号码是否是该移动终端电话簿中的号码，若不是则继续执行步骤S402。
步骤S402，判断移动终端是否处于联网状态，若处于不联网状态则继续执行步骤S403，若处于联网状态则执行图6步骤S303。
步骤S403，判断该号码与本地数据库中的号码是否匹配，若匹配则继续执行步骤S404，若不匹配则执行图5步骤S204。
步骤S404，在移动终端显示该号码在本地数据库中储存的标记 信息。
步骤S405，检测用户是否发出更正标记的指令。
在一种实施方式中，可在用户的电话挂断后，询问用户是否确认该标记信息，也就是询问用户是否需要主动更正该号码的标记信息，当检测到用户发出更正标记的指令时，继续执行步骤S406。
步骤S406，触发标记装置，通过移动终端显示更正标记页面，并接收用户的标记信息。
在一个实施例中，更正标记界面请求用户对来电/去电号码的号码类型进行选择，例如，给出该电话是“业务推销？房产中介？骚扰电话？诈骗钓鱼？快递外卖？其他(手动输入)”的选择。在另一个实施例中，参考图9或图10，通过类似图示的更正标记界面，提示用户对原有匹配的标记信息进行确认或对号码类型进行选择。在又一种实施例中，参考图11，更正标记界面还可提示用户进行自定义标记。
步骤S407，验证装置根据用户的标记信息进行验证。
具体地，可以有多种验证方式。
例如，若将一号码标记为某一标记信息的数量超过预定阈值时，则通过验证。
又例如，在一预定时间内，将一号码标记为某一标记信息的数量超过预定阈值时，则通过验证。
再例如，不同用户的不同信用等级被赋有不同的标记信息的权重，并根据权重计算标记信息的可信度，当标记信息的可信度到达一预定阈值时，则通过验证。
再例如，还可以结合第三方系统的数据库进一步验证。
步骤S408，根据验证结果更新云端数据库和本地数据库，将该 号码及其标记信息存入云端数据库和本地数据库。
优选地，在检测到移动终端联网时，实时的将本地数据库与云端数据库进行同步并更新。在一个变化例中，每隔一定的时间，将本地数据库与云端数据库进行同步并更新。在又一个变化例中，当更新的信息达到一定阈值时，将本地数据库与云端数据库进行同步并更新。
图8示出了本发明一种具体实施方式中初始标记页面的示意图。具体地，在本地/云端数据库没有该号码的标记信息时，移动终端弹出的初始标记页面如图8所示，其中，初始标记页面中显示系统默认设置的常用号码类型，例如业务推销、房产中介、骚扰电话、诈骗钓鱼、快递外卖等，便于用户快速的提供号码的标记信息。优选地，还有分享标记信息、将该号码存入黑名单以及存入联系人等选项。
当号码的标记信息被质疑时，移动终端弹出的更正标记界面也如图8所示。该更正标记页面给出该电话是“业务推销？房产中介？骚扰电话？诈骗钓鱼？快递外卖？其他(手动输入)”的选择，其中，页面所显示的选项为由不同用户对该号码进行标注的多个待验证标记信息。另外，可显示如图9所示的更正标记页面。例如，该更正标记页面给出“138********是如风快递？”的问题，并给出“错了”、“对的”以及“我不知道”的选项，提示用户对该号码的待验证标记，即“如风快递”进行确认。在另一种方式中，还可显示如图9所示的更正标记页面。例如，该更正标记页面给出“138********是什么电话？”的问题，并给出“人事猎头”、“其他类型”以及“确定”的选项。
以上具体地示出和描述了本发明的示例性实施方式。应该理解，本发明不限于所公开的实施方式，相反，本发明意图涵盖包含在所附权利要求的精神和范围内的各种修改和等效布置。

Claims (15)

  1. 一种电话标记方法，其特征在于，包括：
    获取移动终端来电或者去电的电话号码；
    将所述获取的电话号码在本地或者云端数据库中至少一个进行匹配；
    根据所述电话号码在所述本地或者云端数据库是否匹配成功，向用户显示不同的标记页面，提示用户对所述电话号码进行标记或对所述号码的标记信息进行确认；
    获取用户根据所述标记页面对所述电话号码的标记信息并对所述标记信息进行标记验证；
    根据验证通过的标记信息，更新所述云端数据库和所述本地数据库。
  2. 根据权利要求1所述的电话标记方法，其特征在于，若所述电话号码在所述本地数据库和/或所述云端数据库中匹配成功，则显示与所述电话号码相适应的标记信息；
    若所述电话号码在所述本地数据库和/或所述云端数据库中匹配失败，则显示初始标记页面，提示用户对所述电话号码进行标记。
  3. 根据权利要求2所述的电话标记方法，其特征在于，所述显示与所述电话号码相适应的标记信息后，还进一步包括：
    检测是否存在更正标记的指令，当接收到更正标记的指令时，显示更正标记页面，提示用户对原有的验证后的标记信息或所述电话号码进行更正，将所获取的标记结果作为该号码的待验证标记信息；
    将该电话号码标记为质疑号码。
  4. 根据权利要求3所述的电话标记方法，其特征在于，在所述电话号码在所述本地数据库和/或所述云端数据库中匹配成功之后，所述显示与所述电话号码相适应的标记信息之前还包括：
    判断所述电话号码是否是所述质疑号码，
    若所述电话号码是所述质疑号码，则显示更正标记页面，提示用户对所述待验证的标记信息进行选择或确认；
    若所述电话号码不是所述质疑号码，则显示与所述电话号码相适应的标记信息。
  5. 根据权利要求1所述的电话标记方法，其特征在于，所述将获取的电话号码在本地或者云端数据库中至少一个进行匹配，包括按照以下至少一种方式根据所述移动终端联网情况选择本地或者云端数据库：
    若所述移动终端处于不联网状态，则选择本地数据库对所述电话号码进行匹配；
    若所述移动终端处于不联网状态，则检测所述移动终端的网络带宽，并根据网络带宽进行判断，选择本地数据库或者云端数据库对所述电话号码进行匹配；
    若所述移动终端处于联网状态，则直接选择云端数据库对所述电话号码进行匹配；
    若所述移动终端处于联网状态，则优先选择本地数据库对所述电话号码进行匹配，当匹配不成功时连接云端数据库对所述电话号码进行匹配。
  6. 根据权利要求5所述的电话标记方法，其特征在于，所述根据网络带宽进行判断选择本地数据库或者云端数据库对所述电话号码进行匹配包括：
    若所述移动终端的网络带宽小于第一阈值，则选择本地数据库对所述电话号码进行匹配；
    若所述移动终端的网络带宽不小于所述第一阈值，则选择云端数据库对所述电话号码进行匹配。
  7. 根据权利要求1-6中任一项所述的电话标记方法，其特征在于，对用户根据标记页面对电话号码的标记信息进行标记验证包括以下一项或组合：
    当包含待验证信息的电话号码的数量达到第二阈值时，对多个电话号码以及与所述多个电话号码对应的待验证标记信息进行验证；
    当距离前一次向所述验证装置传输的间隔为第一时间间隔时，对在所述第一间隔时间内获取的多个电话号码以及与所述多个电话号码对应的待验证标记信息进行验证；
    当检测到所述移动终端联网时，对获取的多个电话号码以及与所述多个电话号码对应的待验证标记信息进行验证；
    当检测到所述移动终端的网络带宽不小于第三阈值时，对获取的多个电话号码以及与所述多个电话号码对应的待验证标记信息进行验证；
    对用户通过所述移动终端显示的更正标记页面所输入的更正标记信息进行验证时，记录用户所使用的移动终端的设备信息，对于同一个设备信息所传输的同一电话号码进行更正的标记信息，仅接受一次并仅对所接受的标记信息进行验证；
    对用户通过所述移动终端显示的标记页面所输入的标记信息进行验证时，记录用户进行标记时的地理位置信息。
  8. 根据权利要求1所述的电话标记方法，其特征在于，所述对用户根据标记页面对电话号码的标记信息进行标记验证包括以下一项或其组合：
    同一电话号码所对应的具有相同内容的待验证标记信息的数量达到第四阈值时则该待验证标记信息通过验证；
    在第一参数时间内，同一电话号码所对应的具有相同内容的同一待验证标记信息的数量达到第五阈值时则该待验证标记信息通过验证；
    预先赋予不同用户不同的置信权重，根据不同用户提供的置信权重计算所述电话号码对应的具有相同内容的同一待验证标记信息的置信度，当所述置信度达到第六阈值时则该待验证标记信息通过验证；
    预先赋予不同用户不同的置信权重，根据不同用户提供的置信权重计算所述电话号码的相同内容的同一待验证标记信息的置信度，在第二参数时间内，所述置信度达到第七阈值时则该待验证标记信息通过验证；
    根据第三方系统中的电话号码以及标记信息的数据对每个电话号码的标记信息赋予优先级，当用户对电话号码对应的具有相同内容的同一待验证标记信息达到与所述优先级相适应的数量则该待验证标记信息通过验证。
  9. 根据权利要求1所述的电话标记方法，其特征在于，所述更新云端数据库和本地数据库包括以下一种或组合：
    将所述云端数据库中通过标记验证的电话号码及其适应的标记信息更新至所述本地数据库；
    将所述本地数据库中所有更新的电话号码或其标记信息更新至所述云端数据库。
  10. 根据权利要求1或9所述的电话标记方法，其特征在于，所述更新所述本地数据库或所述云端数据库包括以下一项或其组合：
    当需要更新的所述验证通过的标记信息的数量达到第八阈值时，将所述标记信息更新至所述本地数据库或所述云端数据库；
    在距离上一次更新的间隔为第二时间间隔时，在所述第二时间间隔内需要更新的所述验证通过的标记信息的数量达到第九阈值时，将所述标记信息更新至所述本地数据库或所述云端数据库；
    当检测到所述移动终端联网时，将所述验证通过的标记信息实时更新至所述本地数据库或所述云端数据库；
    当检测到所述移动终端的网络带宽不小于第十阈值时，将所述验证通过的标记信息实时更新至所述本地数据库或所述云端数据库。
  11. 一种电话标记系统，其特征在于，包括：
    多个移动终端，用于与用户交互，获取来电或去电的电话号码、显示标记页面并获取用户对所述电话号码的标记信息；
    与所述多个移动终端相适应的本地数据库，用于储存电话号码以及与电话号码相适应的标记信息；
    一个或多个云端数据库，用于储存电话号码以及与电话号码相适应的标记信息，并将相应的标记信息同步至本地数据库中；
    一个或多个标记装置，用于根据移动终端获取的电话号码在云端或者本地数据库中的匹配情况动态提供关联的标记页面，并将所获取的标记信息传输至所述本地数据库以及所述云端数据库中至少一个；以及
    一个或多个验证装置，用于对所述标记信息进行验证；
    其中，所述移动终端选择本地数据库或云端数据库中至少一个对所述电话号码进行匹配；所述云端数据库和所述本地数据库，根据所述标记验证的结果进行同步。
  12. 根据权利要求11所述的电话标记系统，其特征在于，还包括：若所述电话号码在所述本地数据库和/或所述云端数据库中匹配成功，则通过所述移动终端显示与所述电话号码相适应的标记信息；
    若所述电话号码在所述本地数据库和/或所述云端数据库中匹配失败，则触发所述标记装置并通过所述移动终端向用户显示初始标记页面，提示用户对所述电话号码进行标记。
  13. 根据权利要求11所述的电话标记系统，其特征在于，还包括：若所述电话号码在所述本地数据库和/或所述云端数据库中匹配成功，则所述标记装置进一步判断该号码是否是所述质疑号码；
    若所述电话号码是所述质疑号码，则所述标记装置提供更正标记页面，提示用户对所述待验证的标记信息进行选择或确认；
    若所述电话号码不是所述质疑号码，则所述标记装置提供与所述电话号码相适应的标记信息，并进一步检测是否存在所述更正标记的指令：
    当所述标记装置接收到所述更正标记的指令时，提供所述更正标记页面，提示用户对原有的验证后的标记信息或所述电话号码进行更 正，并接收用户反馈的标记结果，将所述标记结果作为该号码的待验证标记信息。
  14. 根据权利要求12所述的电话标记系统，其特征在于，所述通过移动终端显示与电话号码相适应的标记信息还进一步包括：检测用户是否存在更正标记的请求，当接收到用户更正标记的请求时，通过所述移动终端显示更正标记页面，提示用户对原有的标记信息或对所述电话号码进行更正。
  15. 根据权利要求12所述的电话标记系统，其特征在于，所述验证装置至少包括：
    计算器，用于根据用户的标记权重计算标记信息的可信度或者记录标记信息的数目；
    比较器，用于将所记录的标记信息的可信度或数目与预定阈值进行比较。
PCT/CN2015/070782 2013-11-15 2015-01-15 电话号码标记方法及系统 WO2015070824A2 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310574069.0 2013-11-15
CN201310574069.0A CN104378480B (zh) 2013-11-15 2013-11-15 电话号码标记方法及系统

Publications (2)

Publication Number Publication Date
WO2015070824A2 true WO2015070824A2 (zh) 2015-05-21
WO2015070824A3 WO2015070824A3 (zh) 2015-07-09

Family

ID=52557125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/070782 WO2015070824A2 (zh) 2013-11-15 2015-01-15 电话号码标记方法及系统

Country Status (3)

Country Link
US (1) US9509840B2 (zh)
CN (2) CN107743165A (zh)
WO (1) WO2015070824A2 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105554761A (zh) * 2015-12-09 2016-05-04 北京奇虎科技有限公司 下发号码标记信息的方法和装置

Families Citing this family (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104702762A (zh) * 2015-03-13 2015-06-10 小米科技有限责任公司 来电提醒方法和装置
CN104715055A (zh) * 2015-03-30 2015-06-17 北京奇虎科技有限公司 一种搜索结果中的电话号码处理方法和装置
CN104836924B (zh) * 2015-03-31 2017-11-17 小米科技有限责任公司 号码标记方法及装置
US9965525B2 (en) * 2015-04-09 2018-05-08 At&T Mobility Ii Llc Protecting personal data
CN106302938B (zh) 2015-05-22 2020-04-07 腾讯科技（深圳）有限公司 通信事件处理方法和装置
CN105141789B (zh) * 2015-07-28 2018-04-06 小米科技有限责任公司 陌生号码标记方法和装置
CN105162936A (zh) * 2015-08-04 2015-12-16 广东欧珀移动通信有限公司 一种陌生来电提醒方法及用户终端
CN105100513B (zh) * 2015-08-21 2019-04-23 小米科技有限责任公司 来电信息处理方法及装置、来电业务服务器
CN105282744B (zh) * 2015-09-02 2019-03-08 百度在线网络技术（北京）有限公司 用于众包号码标记的方法和装置
CN105120045A (zh) * 2015-09-10 2015-12-02 陈包容 根据新增联系人姓名的备注信息创建通讯录的方法及装置
CN106791230B (zh) * 2015-11-25 2021-08-03 小米科技有限责任公司 电话号码识别方法及装置
CN106792653B (zh) * 2015-11-25 2020-03-24 中国移动通信集团公司 一种通信号码信息处理方法、装置及系统
CN105407232A (zh) * 2015-12-09 2016-03-16 中国联合网络通信集团有限公司 来电提醒方法、装置及系统
CN105577880B (zh) * 2015-12-29 2018-12-18 小米科技有限责任公司 电话号码识别方法及装置
CN105704337B (zh) * 2016-01-19 2019-02-12 上海触乐信息科技有限公司 号码标记方法和系统
CN107295026A (zh) * 2016-03-30 2017-10-24 阿里巴巴集团控股有限公司 电话号码的变更校验方法、装置和系统
US20170302793A1 (en) * 2016-04-13 2017-10-19 Michael W. Starkweather Blocking unwanted communications for a subscriber pool
CN106713580B (zh) * 2016-06-17 2019-01-29 腾讯科技（深圳）有限公司 一种电话号码识别方法、安全服务器以及终端
WO2018023816A1 (zh) * 2016-08-05 2018-02-08 王志强 电话号码标记技术的数据采集方法以及标记系统
WO2018023815A1 (zh) * 2016-08-05 2018-02-08 王志强 电话号码标记的方法以及标记系统
WO2018023814A1 (zh) * 2016-08-05 2018-02-08 王志强 标记电话号码时的信息推送方法以及标记系统
CN106101156B (zh) * 2016-08-23 2019-12-10 北京安云世纪科技有限公司 一种电话查询方法、移动终端
CN108093119B (zh) * 2017-12-18 2020-06-02 维沃移动通信有限公司 一种陌生来电号码的标记方法及移动终端
CN108449482A (zh) * 2018-02-09 2018-08-24 北京泰迪熊移动科技有限公司 号码识别的方法和系统
CN108881593A (zh) * 2018-06-14 2018-11-23 北京奇虎科技有限公司 失信号码的显示方法及装置
CN108900687A (zh) * 2018-06-14 2018-11-27 北京奇虎科技有限公司 失信号码的显示方法及装置
CN108898167A (zh) * 2018-06-14 2018-11-27 北京奇虎科技有限公司 失信号码的显示方法及装置
CN109522063A (zh) * 2018-11-16 2019-03-26 深圳时空数字科技有限公司 一种展示设备启动方法、启动设备及存储设备
CN110278200A (zh) * 2019-06-06 2019-09-24 武汉晶众科技有限公司 一种智能桌面管理系统及方法
US11568030B1 (en) * 2019-09-30 2023-01-31 Snap Inc. Phone number based application authentication
CN113691681A (zh) * 2021-08-20 2021-11-23 北京琥珀创想科技有限公司 垃圾电话数据处理方法及系统
CN114172995A (zh) * 2021-11-11 2022-03-11 微位（深圳）网络科技有限公司 来电处理方法、装置、电子设备及可读存储介质
CN114258024B (zh) * 2021-12-03 2023-10-31 中国联合网络通信集团有限公司 停机处理方法、装置、电子设备及存储介质

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2359511A1 (en) * 2001-10-19 2003-04-19 Rejean Desrosiers Phone number internet identifier method and system
CN101257652A (zh) * 2007-12-28 2008-09-03 深圳市戴文科技有限公司 一种手机恶意来电与恶意短信的预警方法和系统
US8554835B1 (en) * 2010-06-11 2013-10-08 Robert Gordon Williams System and method for secure social networking
WO2012030678A2 (en) * 2010-08-30 2012-03-08 Tunipop, Inc. Techniques for facilitating on-line electronic commerce transactions relating to the sale of goods and merchandise
CN102231779A (zh) * 2011-07-13 2011-11-02 宇龙计算机通信科技(深圳)有限公司 信息获取方法、终端和服务器
CN102663106B (zh) * 2012-04-13 2017-11-24 北京搜狗科技发展有限公司 建立号码信息数据库的方法及系统
CN102665014A (zh) * 2012-04-13 2012-09-12 北京搜狗科技发展有限公司 号码信息提示方法及系统
US9160846B2 (en) * 2013-01-04 2015-10-13 Lead Technology Capital Management, Llc Electronic system and method for screening incoming communications
US20150117622A1 (en) * 2013-10-29 2015-04-30 Jan Fandrianto Multi-service analog telephone adapter
CN104349324B (zh) * 2013-11-15 2018-12-14 上海触乐信息科技有限公司 移动终端号码智能防护系统及方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105554761A (zh) * 2015-12-09 2016-05-04 北京奇虎科技有限公司 下发号码标记信息的方法和装置
CN105554761B (zh) * 2015-12-09 2019-08-23 北京奇虎科技有限公司 下发号码标记信息的方法和装置

Also Published As

Publication number Publication date
US9509840B2 (en) 2016-11-29
WO2015070824A3 (zh) 2015-07-09
CN104378480B (zh) 2017-10-27
US20160006868A1 (en) 2016-01-07
CN107743165A (zh) 2018-02-27
CN104378480A (zh) 2015-02-25

Similar Documents

Publication Publication Date Title
WO2015070824A2 (zh) 电话号码标记方法及系统
US10244105B2 (en) Methods and systems for real time display of caller location, profile, and trust relationship
KR101281882B1 (ko) 피싱 방지를 위한 발신자 인증 방법 및 시스템
US20170245234A1 (en) Adss enabled global roaming system
US20160078095A1 (en) Location-based updating of profile data
KR101970123B1 (ko) 듀얼 채널 신원 인증
CN109995929B (zh) 操作和账号信息的处理方法及装置
CN104579667B (zh) 一种账户密码的管理方法、相关装置及系统
KR20140016359A (ko) 콘택트 사진 제공 방법, 관리 플랫폼 및 사용자 단말기
US20140031003A1 (en) Methods and systems for providing emergency calling
US9081945B2 (en) Information processing device and method
CN105260870A (zh) 身份验证方法、身份验证系统和终端
KR101644936B1 (ko) 커뮤니티 정정들 및 궤적 검출에 기초한 위치 불일치 정정들
CN102984247A (zh) 一种移动终端推荐好友的方法及系统
US20150113381A1 (en) Techniques to leverage data from mobile headers
CN105704285A (zh) 移动终端通讯录更新方法
CN107341275A (zh) 校友信息的推送方法及装置
KR20160031769A (ko) 레터링 서비스 제공 장치 및 방법
CN110288272B (zh) 数据处理方法、装置、电子设备及存储介质
US9544426B2 (en) Method for transmitting data related to a call
KR101662715B1 (ko) 블루투스를 이용한 휴대 단말 간의 정보 교환 방법
US10848456B2 (en) Server device
EP3744059B1 (en) System and method for authenticating a message provider
US11601422B2 (en) Communication node, multi-hop network, equipment validity check method, and program
JP5735359B2 (ja) 情報配信装置、管理システム、及び情報配信方法

Legal Events

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

Ref document number: 15721525

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 07.10.2016)

122 Ep: pct application non-entry in european phase

Ref document number: 15721525

Country of ref document: EP

Kind code of ref document: A2