WO2016173246A1 - 基于云名片的电话呼叫方法及装置 - Google Patents

基于云名片的电话呼叫方法及装置 Download PDF

Info

Publication number
WO2016173246A1
WO2016173246A1 PCT/CN2015/095162 CN2015095162W WO2016173246A1 WO 2016173246 A1 WO2016173246 A1 WO 2016173246A1 CN 2015095162 W CN2015095162 W CN 2015095162W WO 2016173246 A1 WO2016173246 A1 WO 2016173246A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
business card
cloud
cloud business
updated
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.)
Ceased
Application number
PCT/CN2015/095162
Other languages
English (en)
French (fr)
Inventor
牛坤
鲍协浩
赵振海
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Xiaomi Inc
Original Assignee
Xiaomi Inc
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 Xiaomi Inc filed Critical Xiaomi Inc
Priority to MX2016002128A priority Critical patent/MX363947B/es
Priority to JP2017514783A priority patent/JP2017518008A/ja
Priority to KR1020167001057A priority patent/KR101810514B1/ko
Priority to RU2016115694A priority patent/RU2645282C2/ru
Publication of WO2016173246A1 publication Critical patent/WO2016173246A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/57—Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set
    • H04M1/575—Means for retrieving and displaying personal data about calling party
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G06F16/2358—Change logging, detection, and notification
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G06F16/2365—Ensuring data consistency and integrity
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • 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/42042—Notifying the called party of information on the calling party
    • 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
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer

Definitions

  • the present disclosure relates to the field of network communication technologies, and in particular, to a cloud business card-based telephone call method and apparatus.
  • the cloud business card is an electronic business card created by the user and stored in the cloud server.
  • the cloud business card can be managed, for example, cloud business card classification, cloud business card sorting, cloud business card quick query, cloud business card sharing with friends, and time reminding function.
  • the user's cloud business card is updated, the user's contact identifies the user to be slower and the user experience is poor.
  • the disclosure provides a method and a device for calling a phone based on a cloud business card, so as to solve the problem that the user's contact identifies the user with a slower speed and a poor user experience after the user's cloud business card is updated in the prior art.
  • a cloud card-based telephone call method including:
  • the cloud business card corresponding to the first user is queried according to the user identifier of the first user, the cloud business card corresponding to the first user is updated according to the cloud business card information of the first user, and the first a cloud business card updated by a user;
  • the cloud card identifies the first user and displays the updated cloud card of the first user, and the second user is a user who stores the user identifier of the first user.
  • the cloud business card information of the first user includes various information and a version number included in the cloud business card corresponding to the first user; and the first The cloud business card corresponding to the user is updated, and the cloud business card updated by the first user is specifically included:
  • the comparison result indicates that the received cloud business card information is a locally saved cloud name corresponding to the first user
  • the cloud business card corresponding to the first user saved locally is updated by using the received cloud business card information, and the updated cloud business card of the first user is obtained.
  • the method further includes:
  • the cloud business card corresponding to the first user is not queried according to the user identifier of the first user, the cloud business card corresponding to the first user is created according to the cloud business card information of the first user, and the first User created cloud business card;
  • the communication between the first user and the second user includes at least one of the following communication modes:
  • the first user initiates a call to the second user by using the updated phone number
  • the updated phone number and the updated email address are stored in the business card information of the first user.
  • a cloud business card-based telephone call method comprising:
  • the first user When the first user communicates with the second user, the first user is identified according to the updated cloud business card of the first user, and the updated cloud business card of the first user is displayed, the second The user is a user who stores the user ID of the first user.
  • the method further includes:
  • the first user When the first user communicates with the second user, the first user is identified according to the cloud business card created by the first user, and the cloud business card created by the first user is displayed.
  • a cloud business card-based telephone call device comprising:
  • a receiving module configured to receive cloud business card information of the first user, where the cloud business card information carries a user identifier of the first user;
  • an update module configured to update the cloud business card corresponding to the first user according to the cloud business card information of the first user when the cloud business card corresponding to the first user is queried according to the user identifier of the first user Obtaining the updated cloud business card of the first user;
  • a first sending module configured to send, by the first user, the updated cloud business card to the second user, so that when the first user communicates with the second user, the second user is configured according to the Cloud business card identification after the first user update
  • the first user displays the updated cloud business card of the first user
  • the second user is a user who stores the user identifier of the first user.
  • the cloud business card information of the first user includes various information and a version number included in the cloud business card corresponding to the first user;
  • the update module includes:
  • a comparison submodule configured to compare the received version number with a version number of the cloud business card corresponding to the first user saved locally, to obtain a comparison result
  • a updating submodule configured to: when the comparison result indicates that the received cloud business card information is a locally updated updated version of the cloud business card corresponding to the first user, update the locally saved location by using the received cloud business card information.
  • the cloud business card corresponding to the first user is obtained, and the cloud business card updated by the first user is obtained.
  • the device further includes:
  • a creating module configured to create a cloud business card corresponding to the first user according to the cloud business card information of the first user, when the cloud business card corresponding to the first user is not queried according to the user identifier of the first user, Obtaining a cloud business card created by the first user;
  • a second sending module configured to send the cloud business card created by the first user to a second terminal corresponding to the second user, so that when the first user communicates with the second user, the The second user identifies the first user according to the cloud business card created by the first user, and displays the cloud business card created by the first user, where the second user is a user who stores the user identifier of the first user.
  • the communication between the first user and the second user includes at least one of the following communication modes:
  • the first user initiates a call to the second user by using the updated phone number
  • the updated phone number and the updated email address are stored in the business card information of the first user.
  • a cloud business card-based telephone call device comprising:
  • the first receiving module is configured to receive the updated cloud business card sent by the first user by the cloud server;
  • a first display module configured to: when the first user communicates with the second user, identify the first user according to the updated cloud business card of the first user, and display the updated content of the first user
  • the cloud business card, the second user is a user who stores the user identifier of the first user.
  • the device further includes:
  • a second receiving module configured to receive, by the cloud server, the cloud business card created by the first user
  • a saving module configured to save the cloud business card created by the first user in a local address book
  • a second display module configured to identify the first user according to the cloud business card created by the first user, and display the first user created when the first user communicates with the second user Cloud business card.
  • a cloud business card-based telephone call device comprising:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the cloud business card corresponding to the first user is queried according to the user identifier of the first user, the cloud business card corresponding to the first user is updated according to the cloud business card information of the first user, and the first a cloud business card updated by a user;
  • the cloud card identifies the first user and displays the updated cloud card of the first user, and the second user is a user who stores the user identifier of the first user.
  • a cloud business card-based telephone call device comprising:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the first user When the first user communicates with the second user corresponding to the second terminal, the first user is identified according to the updated cloud business card of the first user, and the updated first user is displayed.
  • the cloud business card, the second user is a user who stores the user identifier of the first user.
  • the cloud server can automatically update the cloud business card corresponding to the first user according to the cloud business card information, and send the updated cloud business card to the second user, so that the second user automatically Updating the cloud business card of the first user, and enabling the second user to automatically identify the first user when the first user communicates with the second user, thereby improving the rate and accuracy of the second user identifying the first user, and improving the The user experience of the second user.
  • the cloud server may directly determine whether the update is saved according to the version number. If the cloud business card of the first user is determined to be updated, the cloud business card information of the first user may be directly replaced by the received cloud business card information, so that the cloud server update speed is also faster.
  • the cloud server After receiving the cloud card information of the first user, the cloud server creates a cloud card of the first user according to the received information, and sends the created cloud card to the cloud card. a second user, causing the second user to save the first user's cloud business card, and when the first user and the second user communicate, enabling the second user to automatically identify the first user, thereby improving the second user's identification of the first user The rate and accuracy also improve the user experience of the second user.
  • the second terminal receives the updated cloud card of the first user that is sent by the cloud server, and the first user is the contact of the second user corresponding to the second terminal, and the local saved account is automatically updated according to the updated cloud business card of the first user.
  • the cloud business card corresponding to the first user when the first user communicates with the second user, identifies the first user according to the updated cloud business card of the first user, and displays the updated cloud business card of the first user, so that the first user
  • the second user can automatically identify the first user according to the updated cloud business card of the first user, thereby improving the rate and accuracy of the second user identifying the first user, and improving the user experience of the second user.
  • the second terminal receives the cloud business card created by the first user sent by the cloud server, and automatically saves the cloud business card created by the first user in the local communication record.
  • the cloud card created by the user identifies the first user, and displays the cloud business card created by the first user, so that the second user can automatically identify the first user according to the cloud business card created by the first user, thereby improving the second user to identify the first user.
  • the rate and accuracy also improve the user experience of the second user.
  • FIG. 1 is a flowchart of a cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure
  • FIG. 2 is a flowchart of another cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure
  • FIG. 3 is a flowchart of another cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure
  • FIG. 4 is a flowchart of another cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure
  • FIG. 5 is a flowchart of another cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure
  • FIG. 6 is an application scenario diagram of a cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure
  • FIG. 7 is a block diagram of a cloud business card based telephone call device according to an exemplary embodiment of the present disclosure.
  • FIG. 8 is a block diagram of another cloud business card-based telephone call device according to an exemplary embodiment of the present disclosure.
  • FIG. 9 is a block diagram of another cloud business card-based telephone call device according to an exemplary embodiment of the present disclosure.
  • FIG. 10 is a block diagram of another cloud business card-based telephone call device according to an exemplary embodiment of the present disclosure.
  • FIG. 11 is a block diagram of another cloud business card-based telephone call device according to an exemplary embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a cloud card-based telephone call device according to an exemplary embodiment of the present disclosure.
  • FIG. 13 is another schematic structural diagram of a cloud card-based telephone call device according to an exemplary embodiment of the present disclosure.
  • first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as second information without departing from the scope of the present disclosure.
  • second information may also be referred to as first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • FIG. 1 is a flowchart of a cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure.
  • the method may be used in a cloud server, and includes the following steps:
  • step 110 the cloud card information of the first user is received, where the cloud card information carries the user identifier of the first user.
  • the cloud card information of the first user may be sent by the first terminal used by the first user to the cloud server.
  • the cloud business card information may be information in the cloud business card that is created by the first user for the first time, or may be information that needs to be updated.
  • the cloud business card may be an electronic business card created by the first user and stored in the cloud server. After the first user uploads the cloud business card, the server may manage the first user's cloud business card. For example, the first user is user A, and the user's cloud business card includes user A's name, mobile phone number, and avatar.
  • the user identifier of the first user may be a username registered by the first user on the cloud server, or may be a mobile phone number of the first user.
  • the purpose is that the cloud server can query the cloud business card corresponding to the first user according to the user identifier.
  • step 120 when the cloud business card corresponding to the first user is queried according to the user identifier of the first user, the cloud business card corresponding to the first user is updated according to the cloud business card information of the first user, and the updated information is obtained by the first user.
  • Cloud business card
  • the cloud business card corresponding to the first user when the cloud business card corresponding to the first user is queried according to the user identifier of the first user, it indicates that the cloud server has saved the cloud business card corresponding to the first user, and then receives the cloud business card information of the first user. It is the first user who needs to update the original cloud business card.
  • the cloud business card information received by the cloud server includes the updated avatar of the first user, and the cloud server is updated according to the updated
  • the avatar updates the avatar stored in the local first user's cloud business card, and the updated cloud business card includes the latest updated avatar of the first user.
  • the cloud business card information received by the cloud server includes the updated mobile phone number or needs to be added.
  • the new mobile phone number the cloud server updates the mobile phone number stored in the local first user's cloud business card according to the updated mobile phone number or the new mobile phone number that needs to be added, and the updated cloud business card includes the first The user's updated mobile number or a new mobile number that needs to be added.
  • the first user updated cloud business card is sent to the second user, so that when the first user communicates with the second user, the second user identifies the first one according to the first user updated cloud business card.
  • User and display the updated cloud business card of the first user.
  • the second user is a user who stores the user identifier of the first user.
  • the second user may be a user who stores the user identifier of the first user, for example, the first user is the contact of the first user, and is located in the address book of the second user.
  • the cloud server sends the cloud card of the first user to the first terminal corresponding to the second user, and saves the address book of the second user.
  • the cloud server updates according to the updated cloud business card information of the first user, and obtains the updated cloud business card, and at the same time, the cloud of the first user in the second user's address book The business card will be automatically updated by the cloud server.
  • the second terminal used by user B is displayed on the phone receiving interface.
  • User A's latest cloud business card when user A sends a text message to user B through the updated mobile phone number or the added new mobile phone number, the second terminal used by user B displays the latest cloud business card of user A on the short message interface.
  • the cloud server can automatically update the cloud business card corresponding to the first user according to the cloud business card information, and send the updated cloud business card to the second user, so that the first
  • the second user automatically updates the cloud business card of the first user, and enables the second user to automatically identify the first user when the first user communicates with the second user, thereby improving the rate and accuracy of the second user identifying the first user.
  • the user experience of the second user is also improved.
  • FIG. 2 is a flowchart of another cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure, which may be used in a cloud server and built on the basis of FIG. Includes the following steps:
  • step 210 the cloud business card information of the first user is received, the cloud business card information of the first user carries the user identifier of the first user, and the cloud business card information of the first user may include the cloud business card corresponding to the first user.
  • the cloud business card information of the first user may include the cloud business card corresponding to the first user.
  • step 220 the received version number is compared with the version number of the cloud business card corresponding to the locally saved first user, and a comparison result is obtained.
  • the first user is user A
  • the cloud business card of user A saved by the cloud server includes user A's name, mobile phone number 1, and avatar 1, and the version number is 1.
  • the cloud business card information of the first user received by the cloud server includes the name of the user A, the mobile phone number 2, the avatar 2, and the version number. Is 2.
  • the cloud server compares the received version number 2 with the version number 1. The comparison result is that the cloud business card corresponding to the version number 2 is an updated version of the cloud business card corresponding to the version number 1.
  • step 230 when the comparison result indicates that the received cloud business card information is an updated version of the cloud card corresponding to the first user saved locally, the cloud information corresponding to the first saved user is updated by using the received cloud business card information.
  • the business card is obtained by the first user after the updated cloud business card.
  • the comparison result indicates that the received cloud business card information is not the updated version of the queried cloud business card corresponding to the first user, the update is not required.
  • the cloud server can directly determine whether the version number is based on the version number.
  • the cloud service card of the saved first user is updated. If the update is determined, the cloud business card information of the first user can be directly replaced by the received cloud business card information, so that the cloud server update speed is also faster.
  • FIG. 3 is a flowchart of another cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure, which may be used in a cloud server and built on the basis of FIG. Includes the following steps:
  • step 310 the cloud card information of the first user is received, where the cloud card information carries the user identifier of the first user.
  • the cloud business card information may be the information in the cloud business card that is created by the first user for the first time.
  • the cloud server may create the cloud business card information according to the cloud business card information.
  • the first user's cloud business card For example, the first user is user A, and the user's cloud business card includes user A's name, mobile phone number, and avatar.
  • step 320 when the cloud business card corresponding to the first user is not queried according to the user identifier of the first user, the cloud business card corresponding to the first user is created according to the cloud business card information of the first user, and the cloud business card created by the first user is obtained. .
  • the cloud business card corresponding to the first user when the cloud business card corresponding to the first user is not queried according to the user identifier of the first user, it indicates that the cloud server has not created the cloud business card corresponding to the first user, and may be based on the received cloud of the first user.
  • the business card information creates a cloud business card corresponding to the first user.
  • step 330 the cloud business card created by the first user is sent to the second user, so that when the first user communicates with the second user, the second user identifies the first user according to the cloud business card created by the first user. And display the cloud business card created by the first user.
  • the second user is a user who stores the user identifier of the first user.
  • the second user may be a user who stores the user identifier of the first user, for example, the first user is the contact of the first user, and is located in the address book of the second user. If the first user creates the cloud card of the first user, the cloud server sends the cloud card of the first user to the second terminal corresponding to the second user, and saves the address record of the second user, and is used for When the user communicates with the second user, the second terminal displays the cloud business card created by the first user, so that the second user identifies the first user according to the cloud business card created by the first user.
  • the cloud server receives the cloud business card information of the first user
  • the cloud business card of the first user is not created by itself
  • the cloud business card of the first user is created according to the received information, and the created cloud is created.
  • Sending the business card to the second user so that the second user saves the first user's cloud business card, and when the first user communicates with the second user, enables the second user to automatically identify the first user, thereby improving the second user identification
  • the rate and accuracy of a user also improves the user experience of the second user.
  • Manner 1 The first user initiates a call to the second user by using the updated phone number.
  • Method 2 The first user sends a short message to the second user by using the updated phone number.
  • Method 3 The first user sends an email to the second user by using the updated email address.
  • the updated phone number and the updated email address may be stored in the business card information of the first user.
  • FIG. 4 is a flowchart of another cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure.
  • the method may be used in a second terminal, where the second terminal is used by a second user.
  • Terminal including the following steps:
  • step 410 the first user updated cloud business card sent by the cloud server is received.
  • the first user may be a contact of the second user and located in the address book of the second user. If the first user needs to update its own cloud business card, the cloud server updates according to the updated cloud business card information of the first user, and obtains the updated cloud business card, and at the same time, the cloud of the first user in the second user's address book The business card will be automatically updated by the cloud server.
  • step 420 the cloud card corresponding to the first user is updated according to the updated cloud card of the first user.
  • step 430 when the first user communicates with the second user, the first user is identified according to the updated cloud business card of the first user, and the updated cloud business card of the first user is displayed.
  • the second user is a user who stores the user identifier of the first user.
  • the second terminal used by user B is displayed on the phone receiving interface.
  • User A's latest cloud business card when user A sends a text message to user B through the updated mobile phone number or the added new mobile phone number, the second terminal used by user B displays the latest cloud business card of user A on the short message interface, so that the second user is faster.
  • the identification of the first user improves the user experience of the second user.
  • the second terminal receives the updated cloud card of the first user sent by the cloud server, and the first user is the contact of the second user corresponding to the second terminal, and is automatically updated according to the updated cloud business card of the first user.
  • the cloud card corresponding to the first user saved locally, when the first user communicates with the second user, identifies the first user according to the updated cloud business card of the first user, and displays the updated cloud business card of the first user.
  • the second user can automatically identify the first user according to the updated cloud card of the first user, thereby improving the rate and accuracy of the second user to identify the first user, and improving the user experience of the second user.
  • FIG. 5 is a flowchart of another cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure.
  • the method may be used in a second terminal, where the second terminal is used by a second user.
  • the terminal, and based on Figure 4, includes the following steps:
  • step 510 the first user-created cloud business card sent by the cloud server is received.
  • the first user may be a contact of the second user and located in the address book of the second user. If the first user creates the cloud card of the first user, the cloud server sends the cloud card of the first user to the second terminal corresponding to the second user, and saves it in the address book of the second user.
  • step 520 the cloud business card created by the first user is saved in the local address book.
  • step 530 when the first user communicates with the second user, the first user is identified according to the cloud business card created by the first user, and the cloud business card created by the first user is displayed.
  • the second terminal receives the cloud business card created by the first user sent by the cloud server, and automatically saves the cloud business card created by the first user in the local communication record.
  • the first user communicates with the second user, Identifying the first user according to the cloud business card created by the first user, and displaying the cloud business card created by the first user, so that the second user can automatically identify the first user according to the cloud business card created by the first user, thereby improving the second user identification.
  • the rate and accuracy of the first user also improves the user experience of the second user.
  • FIG. 6 is an application scenario diagram of a cloud business card-based telephone call method according to an exemplary embodiment of the present disclosure.
  • the usage scenario includes a cloud server, a first terminal, and a second terminal.
  • the first user uses the first terminal, and the second user uses the second terminal.
  • the first terminal acquires the cloud business card information of the first user corresponding to the first user, and the cloud business card information carries the user identifier of the first user, and sends the cloud business card information to the cloud server, and the cloud server queries the first according to the user identifier of the first user.
  • the cloud business card corresponding to the user is used, the cloud business card corresponding to the first user is updated according to the cloud business card information of the first user, and the cloud business card updated by the first user is obtained, and the updated cloud business card of the first user is sent to the second user.
  • the second user is a user who stores the user identifier of the first user, and the second terminal updates the locally saved cloud business card corresponding to the first user according to the updated cloud business card of the first user, when the first user
  • the second terminal identifies the first user according to the updated cloud business card of the first user, and displays the updated cloud business card of the first user, so that the second user updates the cloud according to the first user.
  • the business card identifies the first user.
  • the second user can identify the first user according to the updated cloud business card of the first user, and improve the user experience of the second user.
  • the present disclosure also provides an embodiment of a cloud business card based telephone call device.
  • FIG. 7 is a block diagram of a cloud business card-based telephone call device, which is applied to a cloud server and used to execute the cloud-based system shown in FIG. 1 according to an exemplary embodiment.
  • the phone call method of the business card, the device comprises: a receiving module 71, an updating module 72 and a first sending module 73.
  • the receiving module 71 is configured to receive cloud business card information of the first user, where the cloud business card information carries the user identifier of the first user.
  • the update module 72 is configured to update the cloud business card corresponding to the first user according to the cloud business card information of the first user when the cloud business card corresponding to the first user is queried according to the user identifier of the first user. Obtaining the updated cloud business card of the first user.
  • the first sending module 73 is configured to send the updated cloud business card to the second user, so that when the first user communicates with the second user, the second user is configured according to the The first user updated by the first user identifies the first user, and displays the updated cloud business card of the first user, where the second user stores the first User of the user's user ID.
  • the cloud server can automatically update the cloud business card corresponding to the first user according to the cloud business card information, and send the updated cloud business card to the second user, so that the first
  • the second user automatically updates the cloud business card of the first user, and enables the second user to automatically identify the first user when the first user communicates with the second user, thereby improving the rate and accuracy of the second user identifying the first user.
  • the user experience of the second user is also improved.
  • FIG. 8 is a block diagram of another cloud business card-based telephone call device according to an exemplary embodiment, the device is applied to a cloud server, and the embodiment is in the foregoing embodiment shown in FIG. 7 .
  • the cloud card business card information of the first user includes the information and the version number included in the cloud business card corresponding to the first user;
  • the update The module includes 72 may include a comparison sub-module 81 and an update sub-module 82.
  • the comparison sub-module 81 is configured to compare the received version number with the version number of the cloud business card corresponding to the first user saved locally, to obtain a comparison result.
  • the update sub-module 82 is configured to update the locally saved location by using the received cloud business card information when the comparison result indicates that the received cloud business card information is a locally saved updated version of the cloud business card corresponding to the first user.
  • the cloud business card corresponding to the first user is obtained, and the cloud business card updated by the first user is obtained.
  • the cloud server can directly determine whether the version number is based on the version number.
  • the cloud service card of the saved first user is updated. If the update is determined, the cloud business card information of the first user can be directly replaced by the received cloud business card information, so that the cloud server update speed is also faster.
  • FIG. 9 is a block diagram of another cloud business card-based telephone call device according to an exemplary embodiment, and the device is applied to a cloud server.
  • the embodiment is in the foregoing embodiment shown in FIG. 7 .
  • the apparatus may further include: a creating module 91 and a second sending module 92.
  • the creating module 91 is configured to create a cloud corresponding to the first user according to the cloud card information of the first user when the cloud card corresponding to the first user is not queried according to the user identifier of the first user.
  • the business card is obtained from the cloud business card created by the first user.
  • the second sending module 92 sends the cloud business card created by the first user to the second terminal corresponding to the second user, so that when the first user communicates with the second user, the second The user identifies the first user according to the cloud business card created by the first user, and displays the cloud business card created by the first user, where the second user is a user who stores the user identifier of the first user.
  • the cloud server receives the cloud business card information of the first user
  • the cloud business card of the first user is not created by itself
  • the cloud business card of the first user is created according to the received information, and the created cloud is created.
  • Sending the business card to the second user so that the second user saves the first user's cloud business card, and when the first user communicates with the second user, enables the second user to automatically identify the first user, thereby improving the second user identification
  • the rate and accuracy of a user also Improve the user experience of the second user.
  • the first user when the first user communicates with the second user, at least one of the following communication modes may be included: the first user initiates a call to the second user by using the updated phone number; the first user The updated user's phone number is used to send a text message to the second user; the first user sends an email to the second user using the updated email address.
  • the updated phone number and the updated email address may be stored in the business card information of the first user.
  • FIG. 10 is a block diagram of another cloud business card-based telephone call device, which is applied to a second terminal used by a second user, for performing FIG. 4 according to an exemplary embodiment.
  • the apparatus may include a first receiving module 101, an update module 102, and a first display module 103.
  • the first receiving module 101 is configured to receive the updated cloud business card sent by the first user by the cloud server.
  • the update module 102 updates the locally saved cloud business card corresponding to the first user according to the updated cloud business card of the first user.
  • the first display module 103 is configured to: when the first user communicates with the second user, identify the first user according to the updated cloud business card of the first user, and display the updated The cloud business card, the second user is a user who stores the user identifier of the first user.
  • the second terminal receives the updated cloud card of the first user sent by the cloud server, and the first user is the contact of the second user corresponding to the second terminal, and is automatically updated according to the updated cloud business card of the first user.
  • the cloud card corresponding to the first user saved locally, when the first user communicates with the second user, identifies the first user according to the updated cloud business card of the first user, and displays the updated cloud business card of the first user.
  • the second user can automatically identify the first user according to the updated cloud card of the first user, thereby improving the rate and accuracy of the second user to identify the first user, and improving the user experience of the second user.
  • FIG. 11 is a block diagram of another cloud business card-based telephone call device, which is applied to a second terminal used by a second user, for performing FIG. 5 according to an exemplary embodiment.
  • the illustrated cloud card-based telephone call method the device may further include a second receiving module 111, a saving module 112, and a second display module 113.
  • the second receiving module 111 is configured to receive the cloud business card created by the first user that is sent by the cloud server.
  • the saving module 112 is configured to save the cloud business card created by the first user in a local address book.
  • the second display module 113 is configured to display the updated cloud business card of the first user when the first user communicates with the second user corresponding to the second terminal, so that the second user according to the The first user updated by the first user updates the cloud card.
  • the second terminal receives the cloud business card created by the first user sent by the cloud server, and automatically saves the cloud business card created by the first user in the local communication record.
  • the first user communicates with the second user, Identifying the first user according to the cloud business card created by the first user, and displaying the cloud business card created by the first user, so that the second user can automatically identify the first user according to the cloud business card created by the first user, thereby improving the second user identification.
  • the rate and accuracy of the first user also improves the user experience of the second user.
  • the present disclosure also provides another cloud business card-based telephone call device, which is applied to the cloud.
  • the server including:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the cloud business card corresponding to the first user is queried according to the user identifier of the first user, the cloud business card corresponding to the first user is updated according to the cloud business card information of the first user, and the first a cloud business card updated by a user;
  • the cloud card identifies the first user and displays the updated cloud card of the first user, and the second user is a user who stores the user identifier of the first user.
  • the present disclosure further provides another cloud business card-based telephone call device, where the device is applied to the second terminal, including:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the first user When the first user communicates with the second user corresponding to the second terminal, the first user is identified according to the updated cloud business card of the first user, and the updated first user is displayed.
  • the cloud business card, the second user is a user who stores the user identifier of the first user.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the modules described as separate components may or may not be physically separate, and the components displayed as modules may or may not be physical modules, ie may be located A place, or it can be distributed to multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present disclosure. Those of ordinary skill in the art can understand and implement without any creative effort.
  • FIG. 12 is a schematic structural diagram (cloud server side) for a cloud business card-based telephone call device 1900 according to an exemplary embodiment.
  • the device 1900 includes a processing component 1922, which further Included are one or more processors, and memory resources represented by memory 1932 for storing instructions executable by processing component 1922, such as an application.
  • An application stored in memory 1932 can include one or more modules each corresponding to a set of instructions.
  • processing component 1922 is configured to execute instructions.
  • Apparatus 1900 can also include a power supply component 1926 configured to perform power management of apparatus 1900, a wired or wireless network interface 1950 configured to connect apparatus 1900 to the network, and an input/output (I/O) interface 1958.
  • Device 1900 can operate based on an operating system stored in memory 1932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
  • FIG. 13 is another schematic structural diagram (terminal device side) for a cloud business card-based telephone call device 1300 according to an exemplary embodiment of the present disclosure.
  • device 1300 can be a mobile phone with routing functionality, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.
  • apparatus 1300 can include one or more of the following components: processing component 1302, memory 1304, power component 1306, multimedia component 1308, audio component 1310, input/output (I/O) interface 1312, sensor component 1313, And a communication component 1316.
  • Processing component 1302 typically controls the overall operation of device 1300, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 1302 can include one or more processors 1320 to execute instructions to perform all or part of the steps described above.
  • processing component 1302 can include one or more modules to facilitate interaction between component 1302 and other components.
  • processing component 1302 can include a multimedia module to facilitate interaction between multimedia component 1308 and processing component 1302.
  • Memory 1304 is configured to store various types of data to support operation at device 1300. Examples of such data include instructions for any application or method operating on device 1300, contact data, phone book data, messages, pictures, videos, and the like.
  • Memory 1304 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM erasable Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • Power component 1306 provides power to various components of device 1300.
  • Power component 1306 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 1300.
  • the multimedia component 1308 includes a screen between the device 1300 and the user that provides an output interface.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor may sense not only the boundary of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 1308 includes a front camera and/or a rear camera. When the device 1300 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 1310 is configured to output and/or input an audio signal.
  • the audio component 1310 includes a microphone (MIC) that is configured to receive an external audio signal when the device 1300 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal can be further stored in memory 1304 Or sent via communication component 1316.
  • the audio component 1310 also includes a speaker for outputting an audio signal.
  • the I/O interface 1312 provides an interface between the processing component 1302 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 1313 includes one or more sensors for providing device 1300 with a status assessment of various aspects.
  • sensor assembly 1313 can detect an open/closed state of device 1300, relative positioning of components, such as the display and keypad of device 1300, and sensor component 1313 can also detect a change in position of one component of device 1300 or device 1300. The presence or absence of contact by the user with the device 1300, the orientation or acceleration/deceleration of the device 1300 and the temperature change of the device 1300.
  • the sensor assembly 1313 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 1313 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 1313 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, a microwave sensor, or a temperature sensor.
  • Communication component 1316 is configured to facilitate wired or wireless communication between device 1300 and other devices.
  • the device 1300 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • communication component 1316 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • the communication component 1316 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • apparatus 1300 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 1304 comprising instructions executable by processor 1320 of apparatus 1300 to perform the above method.
  • the non-transitory computer readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephone Function (AREA)

Abstract

本公开是基于云名片的电话呼叫方法及装置，该方法包括：接收第一用户的云名片信息，云名片信息携带有第一用户的用户标识；当根据第一用户的用户标识查询到第一用户对应的云名片时，根据第一用户的云名片信息对第一用户对应的云名片进行更新，得到第一用户更新后的云名片；将第一用户更新后的云名片发送至第二用户，以使当第一用户与第二用户之间通信时，第二用户根据第一用户更新后的云名片识别第一用户，并展示第一用户更新后的云名片，第二用户为存储有所述第一用户的用户标识的用户。因此，本公开可以提高第二用户识别第一用户的速率和正确度，还可以提高第二用户的用户体验。

Description

基于云名片的电话呼叫方法及装置
本申请基于申请号为201510205370.3、申请日为2015年04月27日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及网络通信技术领域，尤其涉及基于云名片的电话呼叫方法及装置。
背景技术
随着网络通信技术的不断发展，普通的电子名片将会逐渐被云名片所代替。其中，云名片是用户创建并存储于云端服务器的电子名片。相关技术中，用户上传云名片后，可以对云名片进行管理，比如：对云名片进行云名片分类，云名片整理，云名片快速查询，云名片与朋友共享，以及定时提醒功能。但是，用户的云名片更新后，该用户的联系人识别该用户速度较慢，用户体验较差。
发明内容
本公开提供了基于云名片的电话呼叫方法及装置，以解决现有技术中用户的云名片更新后，该用户的联系人识别该用户速度较慢，用户体验较差的问题。
根据本公开实施例的第一方面，提供一种基于云名片的电话呼叫方法包括：
接收第一用户的云名片信息，所述云名片信息携带有所述第一用户的用户标识；
当根据所述第一用户的用户标识查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息对所述第一用户对应的云名片进行更新，得到所述第一用户更新后的云名片；
将所述第一用户更新后的云名片发送至第二用户，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
可选的，所述第一用户的云名片信息包括所述第一用户对应的云名片所包括的各项信息和版本号；所述根据所述第一用户的云名片信息对所述第一用户对应的云名片进行更新，得到所述第一用户更新后的云名片具体包括：
将接收到的版本号与本地已保存的所述第一用户对应的云名片的版本号进行比较，得到比较结果；
当所述比较结果指示接收到的云名片信息是本地已保存的所述第一用户对应的云名 片的更新版本时，利用接收到的云名片信息更新本地已保存的所述第一用户对应的云名片，得到所述第一用户更新后的云名片。
可选的，所述方法还包括：
当根据所述第一用户的用户标识没有查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息创建所述第一用户对应的云名片，得到所述第一用户创建的云名片；
将所述第一用户创建的云名片发送至第二用户对应的第二终端，以使当所述第一用户与所述第二用户之间通信时，所述第二用户对应的第二终端根据所述第一用户创建的云名片识别所述第一用户，并展示所述第一用户创建的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
可选的，所述第一用户与所述第二用户之间通信，包括如下通信方式中的至少一种：
所述第一用户采用更新后的电话号码向所述第二用户发起呼叫；
所述第一用户采用更新后的电话号码向所述第二用户发送短信；
所述第一用户采用更新后的邮箱地址向所述第二用户发送电子邮件；
其中，所述更新后的电话号码、所述更新后的邮箱地址存储于所述第一用户的名片信息中。
根据本公开实施例的第二方面，提供一种基于云名片的电话呼叫方法，所述方法包括：
接收云服务器发送的第一用户更新后的云名片；
根据所述第一用户更新后的云名片更新本地已保存的所述第一用户对应的云名片；
当所述第一用户与第二用户之间通信时，根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
可选的，所述方法还包括：
接收所述云服务器发送的所述第一用户创建的云名片；
将所述第一用户创建的云名片保存在本地通信录中；
当所述第一用户与所述第二用户之间通信时，根据所述第一用户创建的云名片识别所述第一用户，并展示所述第一用户创建的云名片。
根据本公开实施例的第三方面，提供一种基于云名片的电话呼叫装置，所述装置包括：
接收模块，用于接收第一用户的云名片信息，所述云名片信息携带有所述第一用户的用户标识；
更新模块，用于当根据所述第一用户的用户标识查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息对所述第一用户对应的云名片进行更新，得到所述第一用户更新后的云名片；
第一发送模块，用于将所述第一用户更新后的云名片发送至第二用户，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户更新后的云名片识别 所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
可选的，所述第一用户的云名片信息包括所述第一用户对应的云名片所包括的各项信息和版本号；所述更新模块包括：
比较子模块，用于将接收到的版本号与本地已保存的所述第一用户对应的云名片的版本号进行比较，得到比较结果；
更新子模块，用于当所述比较结果指示接收到的云名片信息是本地已保存的所述第一用户对应的云名片的更新版本时，利用接收到的云名片信息更新本地已保存的所述第一用户对应的云名片，得到所述第一用户更新后的云名片。
可选的，所述装置还包括：
创建模块，用于当根据所述第一用户的用户标识没有查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息创建所述第一用户对应的云名片，得到所述第一用户创建的云名片；
第二发送模块，用于将所述第一用户创建的云名片发送至第二用户对应的第二终端，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户创建的云名片识别所述第一用户，并展示所述第一用户创建的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
可选的，所述第一用户与所述第二用户之间通信，包括如下通信方式中的至少一种：
所述第一用户采用更新后的电话号码向所述第二用户发起呼叫；
所述第一用户采用更新后的电话号码向所述第二用户发送短信；
所述第一用户采用更新后的邮箱地址向所述第二用户发送电子邮件；
其中，所述更新后的电话号码、所述更新后的邮箱地址存储于所述第一用户的名片信息中。
根据本公开实施例的第四方面，提供一种基于云名片的电话呼叫装置，所述装置包括：
第一接收模块，用于接收云服务器发送的第一用户更新后的云名片；
更新模块，根据所述第一用户更新后的云名片更新本地已保存的所述第一用户对应的云名片；
第一展示模块，用于当所述第一用户与第二用户之间通信时，根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
可选的，所述装置还包括：
第二接收模块，用于接收所述云服务器发送的所述第一用户创建的云名片；
保存模块，用于将所述第一用户创建的云名片保存在本地通信录中；
第二展示模块，用于当所述第一用户与所述第二用户之间通信时，根据所述第一用户创建的云名片识别所述第一用户，并展示所述第一用户创建的云名片。
根据本公开实施例的第五方面，提供一种基于云名片的电话呼叫装置，所述装置包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收第一用户的云名片信息，所述云名片信息携带有所述第一用户的用户标识；
当根据所述第一用户的用户标识查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息对所述第一用户对应的云名片进行更新，得到所述第一用户更新后的云名片；
将所述第一用户更新后的云名片发送至第二用户，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
根据本公开实施例的第六方面，提供一种基于云名片的电话呼叫装置，所述装置包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收云服务器发送的第一用户更新后的云名片；
根据所述第一用户更新后的云名片更新本地已保存的所述第一用户对应的云名片；
当所述第一用户与所述第二终端对应的第二用户之间通信时，根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
本公开的实施例提供的技术方案可以包括以下有益效果：
本公开中云服务器接收到第一用户的云名片信息后，能够根据该云名片信息自动更新第一用户对应的云名片，并将更新后的云名片发送给第二用户，使得第二用户自动更新第一用户的云名片，并在第一用户和第二用户通信时，使得第二用户能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
本公开中云服务器接收到第一用户的云名片信息后，若该云名片信息包括第一用户对应的云名片所包括的各项信息和版本号，则可以直接根据版本号确定是否更新已保存的第一用户的云名片，若确定更新，则可以直接用接收到的云名片信息代替已保存的第一用户的云名片，使得云服务器更新速度也比较快。
本公开中云服务器接收到第一用户的云名片信息后，当自身没有创建第一用户的云名片时，则根据接收到的信息创建第一用户的云名片，并将创建的云名片发送至第二用户，使得第二用户保存第一用户的云名片，并在第一用户和第二用户通信时，使得第二用户能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
本公开中第二终端接收云服务器发送的第一用户更新后的云名片，第一用户是第二终端对应的第二用户的联系人，根据第一用户更新后的云名片自动更新本地已保存的第一用户对应的云名片，当第一用户与第二用户之间通信时，根据第一用户更新后的云名片识别第一用户，并展示第一用户更新后的云名片，以使第二用户根据第一用户更新后的云名片能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
本公开中第二终端接收云服务器发送的第一用户创建的云名片，将第一用户创建的云名片自动保存在本地通信录中，第一用户与第二用户之间通信时，根据第一用户创建的云名片识别第一用户，并展示第一用户创建的云名片，以使第二用户根据第一用户创建的云名片能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
图1是本公开根据一示例性实施例示出的一种基于云名片的电话呼叫方法流程图；
图2是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫方法流程图；
图3是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫方法流程图；
图4是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫方法流程图；
图5是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫方法流程图；
图6是本公开根据一示例性实施例示出的一种基于云名片的电话呼叫方法的应用场景图；
图7是本公开根据一示例性实施例示出的一种基于云名片的电话呼叫装置的框图；
图8是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫装置的框图；
图9是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫装置的框图；
图10是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫装置的框图；
图11是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫装置的框图；
图12是本公开根据一示例性实施例示出的一种用于基于云名片的电话呼叫装置的一结构示意图；
图13是本公开根据一示例性实施例示出的一种用于基于云名片的电话呼叫装置的另一结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
在本公开使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开。在本公开和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
如图1所示，图1是本公开根据一示例性实施例示出的一种基于云名片的电话呼叫方法流程图，该方法可以用于云服务器中，包括以下步骤：
在步骤110中，接收第一用户的云名片信息，该云名片信息携带有第一用户的用户标识。其中，该第一用户的云名片信息可以是第一用户使用的第一终端发送至云服务器的。
本公开实施例中，云名片信息可以是第一用户第一次创建的云名片中的信息，也可以是需要更新的信息。其中，云名片可以是第一用户创建并存储于云服务器的电子名片，当第一用户上传云名片后，服务器可以对第一用户的云名片进行管理。比如：第一用户为用户A，用户A的云名片包括用户A的姓名、手机号码、以及头像等。
另外，第一用户的用户标识可以是第一用户在云服务器注册的用户名，也可以是第一用户的手机号码等。其目的是云服务器根据该用户标识能够查询到第一用户对应的云名片。
在步骤120中，当根据第一用户的用户标识查询到第一用户对应的云名片时，根据第一用户的云名片信息对第一用户对应的云名片进行更新，得到第一用户更新后的云名片。
本公开实施例中，当根据第一用户的用户标识查询到第一用户对应的云名片时，表明云服务器已经保存有第一用户对应的云名片，再接收到第一用户的云名片信息，是第一用户需要对原有的云名片进行更新。
比如：当第一用户需要对原有的云名片中的头像进行更新时，云服务器接收到的第一用户的云名片信息中包括第一用户的更新后的头像，则云服务器根据更新后的头像对保存在本地的第一用户的云名片中的头像进行更新，更新后的云名片中包括第一用户最新更新的头像。
又比如：当第一用户需要对原有的云名片中的手机号码进行更新或者增加新的手机号码时，云服务器接收到的第一用户的云名片信息中包括更新后的手机号码或者需要增加的新的手机号码，则云服务器根据更新后的手机号码或者需要增加的新的手机号码对保存在本地的第一用户的云名片中的手机号码进行更新，更新后的云名片中包括第一用户更新后的手机号码或者需要增加的新的手机号码。
在步骤130中，将第一用户更新后的云名片发送至第二用户，以使当第一用户与第二用户之间通信时，第二用户根据第一用户更新后的云名片识别第一用户，并展示第一用户更新后的云名片。其中，第二用户为存储有第一用户的用户标识的用户。
本公开实施例中，第二用户可以为存储有第一用户的用户标识的用户，比如：第一用户为第一用户的联系人，并位于第二用户的通信录中。其中，若第一用户创建了第一用户的云名片，云服务器会将第一用户的云名片发送至第二用户对应的第一终端，并保存在第二用户的通信录。若第一用户需要更新自身的云名片时，云服务器会根据第一用户更新后的云名片信息进行更新，得到更新后的云名片，同时，第二用户的通信录中的第一用户的云名片会通过云服务器自动更新。
比如：第一用户为用户A，第二用户为用户B，用户A通过更新后的手机号码或者增加的新的手机号码呼叫用户B时，用户B使用的第二终端会在电话接听界面，显示用户A最新的云名片。或者，用户A通过更新后的手机号码或者增加的新的手机号码向用户B发送短信时，用户B使用的第二终端会在短信界面，显示用户A最新的云名片。
由上述实施例可见，云服务器接收到第一用户的云名片信息后，能够根据该云名片信息自动更新第一用户对应的云名片，并将更新后的云名片发送给第二用户，使得第二用户自动更新第一用户的云名片，并在第一用户和第二用户通信时，使得第二用户能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
如图2所示，图2是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫方法流程图，该方法可以用于云服务器中，并建立在图1的基础上，包括以下步骤：
在步骤210中，接收第一用户的云名片信息，该第一用户的云名片信息携带有第一用户的用户标识，并且该第一用户的云名片信息可以包括第一用户对应的云名片所包括的各项信息和版本号。
在步骤220中，将接收到的版本号与本地已保存的第一用户对应的云名片的版本号进行比较，得到比较结果。
比如：第一用户为用户A，云服务器保存的用户A的云名片包括用户A的姓名、手机号码1、以及头像1等，版本号为1。当用户A需要将手机号码1更新为手机号码2，头像1更新为头像2时，则云服务器接收到的第一用户的云名片信息包括用户A的姓名、手机号码2、头像2，版本号为2。云服务器将接收到的版本号2与版本号1进行比较，得到的比较结果为版本号2对应的云名片是版本号1对应的云名片的更新版本。
在步骤230中，当比较结果指示接收到的云名片信息是本地已保存的第一用户对应的云名片的更新版本时，利用接收到的云名片信息更新本地已保存的第一用户对应的云名片，得到第一用户更新后的云名片。
另外，当比较结果指示接收到的云名片信息不是查询到的第一用户对应的云名片的更新版本时，则不需要更新。
由上述实施例可见，云服务器接收到第一用户的云名片信息后，若该云名片信息包括第一用户对应的云名片所包括的各项信息和版本号，则可以直接根据版本号确定是否更新已保存的第一用户的云名片，若确定更新，则可以直接用接收到的云名片信息代替已保存的第一用户的云名片，使得云服务器更新速度也比较快。
如图3所示，图3是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫方法流程图，该方法可以用于云服务器中，并建立在图1的基础上，包括以下步骤：
在步骤310中，接收第一用户的云名片信息，该云名片信息携带有第一用户的用户标识。
本公开实施例中，本公开实施例中，云名片信息可以是第一用户第一次创建的云名片中的信息，当第一用户上传云名片信息后，云服务器可以根据该云名片信息创建第一用户的云名片。比如：第一用户为用户A，用户A的云名片包括用户A的姓名、手机号码、以及头像等。
在步骤320中，当根据第一用户的用户标识没有查询到第一用户对应的云名片时，根据第一用户的云名片信息创建第一用户对应的云名片，得到第一用户创建的云名片。
本公开实施例中，当根据第一用户的用户标识没有查询到第一用户对应的云名片时，表明云服务器还没有创建第一用户对应的云名片，可以根据接收到的第一用户的云名片信息创建第一用户对应的云名片。
在步骤330中，将第一用户创建的云名片发送至第二用户，以使当第一用户与第二用户之间通信时，第二用户根据第一用户创建的云名片识别第一用户，并展示第一用户创建的云名片。其中，第二用户为存储有第一用户的用户标识的用户。
本公开实施例中，第二用户可以为存储有第一用户的用户标识的用户，比如：第一用户为第一用户的联系人，并位于第二用户的通信录中。其中，若第一用户创建了第一用户的云名片，云服务器会将第一用户的云名片发送至第二用户对应的第二终端，并保存在第二用户的通信录，并用于当第一用户与第二用户之间通信时，第二终端展示第一用户创建的云名片，使得第二用户根据第一用户创建的云名片识别第一用户。
由上述实施例可见，云服务器接收到第一用户的云名片信息后，当自身没有创建第一用户的云名片时，则根据接收到的信息创建第一用户的云名片，并将创建的云名片发送至第二用户，使得第二用户保存第一用户的云名片，并在第一用户和第二用户通信时，使得第二用户能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
另外，上述图1至图4所示的基于云名片的电话呼叫方法中，当第一用户与第二用户之间通信时，可以包括如下通信方式中的至少一种：
方式一：第一用户采用更新后的电话号码向第二用户发起呼叫。
方式二：第一用户采用更新后的电话号码向第二用户发送短信。
方式三：第一用户采用更新后的邮箱地址向第二用户发送电子邮件。
其中，更新后的电话号码、更新后的邮箱地址可以存储于第一用户的名片信息中。
如图4所示，图4是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫方法流程图，该方法可以用于第二终端中，第二终端是第二用户使用的终端，包括以下步骤：
在步骤410中，接收云服务器发送的第一用户更新后的云名片。
本公开实施例中，第一用户可以为第二用户的联系人，并位于第二用户的通信录中。若第一用户需要更新自身的云名片时，云服务器会根据第一用户更新后的云名片信息进行更新，得到更新后的云名片，同时，第二用户的通信录中的第一用户的云名片会通过云服务器自动更新。
在步骤420中，根据第一用户更新后的云名片更新本地已保存的第一用户对应的云名片。
在步骤430中，当第一用户与第二用户之间通信时，根据第一用户更新后的云名片识别第一用户，并展示第一用户更新后的云名片。其中，第二用户为存储有第一用户的用户标识的用户。
比如：第一用户为用户A，第二用户为用户B，用户A通过更新后的手机号码或者增加的新的手机号码呼叫用户B时，用户B使用的第二终端会在电话接听界面，显示用户A最新的云名片。或者，用户A通过更新后的手机号码或者增加的新的手机号码向用户B发送短信时，用户B使用的第二终端会在短信界面，显示用户A最新的云名片，使得第二用户更快的识别第一用户，提高了第二用户的用户体验。
由上述实施例可见，第二终端接收云服务器发送的第一用户更新后的云名片，第一用户是第二终端对应的第二用户的联系人，根据第一用户更新后的云名片自动更新本地已保存的第一用户对应的云名片，当第一用户与第二用户之间通信时，根据第一用户更新后的云名片识别第一用户，并展示第一用户更新后的云名片，以使第二用户根据第一用户更新后的云名片能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
如图5所示，图5是本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫方法流程图，该方法可以用于第二终端中，第二终端是第二用户使用的终端，并建立在图4的基础上，包括以下步骤：
在步骤510中，接收云服务器发送的第一用户创建的云名片。
本公开实施例中，第一用户可以为第二用户的联系人，并且位于第二用户的通信录中。 若第一用户创建了第一用户的云名片，云服务器会将第一用户的云名片发送至第二用户对应的第二终端，并保存在第二用户的通信录中。
在步骤520中，将第一用户创建的云名片保存在本地通信录中。
在步骤530中，当第一用户与第二用户之间通信时，根据第一用户创建的云名片识别第一用户，并展示第一用户创建的云名片。
由上述实施例可见，第二终端接收云服务器发送的第一用户创建的云名片，将第一用户创建的云名片自动保存在本地通信录中，第一用户与第二用户之间通信时，根据第一用户创建的云名片识别第一用户，并展示第一用户创建的云名片，以使第二用户根据第一用户创建的云名片能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
如图6所示，图6是本公开根据一示例性实施例示出的一种基于云名片的电话呼叫方法的应用场景图。该用于场景包括云服务器、第一终端和第二终端。其中，第一用户使用第一终端，第二用户使用第二终端。
第一终端获取自身对应的第一用户的云名片信息，云名片信息携带有第一用户的用户标识，将云名片信息发送至云服务器，当云服务器根据第一用户的用户标识查询到第一用户对应的云名片时，根据第一用户的云名片信息对第一用户对应的云名片进行更新，得到第一用户更新后的云名片，将第一用户更新后的云名片发送至第二用户对应的第二终端，第二用户为存储有第一用户的用户标识的用户，第二终端根据第一用户更新后的云名片更新本地已保存的第一用户对应的云名片，当第一用户与第二用户之间通信时，第二终端根据第一用户更新后的云名片识别第一用户，并展示第一用户更新后的云名片，以使第二用户根据第一用户更新后的云名片识别第一用户。从而实现了第二用户能够根据第一用户更新后的云名片更快的识别第一用户，提高了第二用户的用户体验。
与前述基于云名片的电话呼叫方法实施例相对应，本公开还提供了基于云名片的电话呼叫装置的实施例。
如图7所示，图7是本公开根据一示例性实施例示出的一种基于云名片的电话呼叫装置的框图，所述装置应用于云服务器上，并用于执行图1所示的基于云名片的电话呼叫方法，所述装置包括：接收模块71、更新模块72和第一发送模块73。
其中，接收模块71用于接收第一用户的云名片信息，所述云名片信息携带有所述第一用户的用户标识。
更新模块72用于当根据所述第一用户的用户标识查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息对所述第一用户对应的云名片进行更新，得到所述第一用户更新后的云名片。
第一发送模块73用于将所述第一用户更新后的云名片发送至第二用户，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一 用户的用户标识的用户。
由上述实施例可见，云服务器接收到第一用户的云名片信息后，能够根据该云名片信息自动更新第一用户对应的云名片，并将更新后的云名片发送给第二用户，使得第二用户自动更新第一用户的云名片，并在第一用户和第二用户通信时，使得第二用户能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
如图8示，图8本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫装置的框图，所述装置应用于云服务器上，该实施例在前述图7所示实施例的基础上，并用于执行图2所示的基于云名片的电话呼叫方法，第一用户的云名片信息包括所述第一用户对应的云名片所包括的各项信息和版本号；所述更新模块包括72可以包括：比较子模块81和更新子模块82。
其中，比较子模块81用于将接收到的版本号与本地已保存的所述第一用户对应的云名片的版本号进行比较，得到比较结果。
更新子模块82用于当所述比较结果指示接收到的云名片信息是本地已保存的所述第一用户对应的云名片的更新版本时，利用接收到的云名片信息更新本地已保存的所述第一用户对应的云名片，得到所述第一用户更新后的云名片。
由上述实施例可见，云服务器接收到第一用户的云名片信息后，若该云名片信息包括第一用户对应的云名片所包括的各项信息和版本号，则可以直接根据版本号确定是否更新已保存的第一用户的云名片，若确定更新，则可以直接用接收到的云名片信息代替已保存的第一用户的云名片，使得云服务器更新速度也比较快。
如图9示，图9本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫装置的框图，所述装置应用于云服务器上，该实施例在前述图7所示实施例的基础上，并用于执行图3所示的基于云名片的电话呼叫方法，所述装置还可以包括：创建模块91和第二发送模块92。
其中，创建模块91用于当根据所述第一用户的用户标识没有查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息创建所述第一用户对应的云名片，得到所述第一用户创建的云名片。
第二发送模块92，将所述第一用户创建的云名片发送至第二用户对应的第二终端，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户创建的云名片识别所述第一用户，并展示所述第一用户创建的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
由上述实施例可见，云服务器接收到第一用户的云名片信息后，当自身没有创建第一用户的云名片时，则根据接收到的信息创建第一用户的云名片，并将创建的云名片发送至第二用户，使得第二用户保存第一用户的云名片，并在第一用户和第二用户通信时，使得第二用户能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还 提高了第二用户的用户体验。
另外，上述实施例中，当第一用户与第二用户之间通信时，可以包括如下通信方式中的至少一种：第一用户采用更新后的电话号码向第二用户发起呼叫；第一用户采用更新后的电话号码向第二用户发送短信；第一用户采用更新后的邮箱地址向第二用户发送电子邮件。其中，更新后的电话号码、更新后的邮箱地址可以存储于第一用户的名片信息中。
如图10示，图10本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫装置的框图，所述装置应用于第二用户使用的第二终端上，用于执行图4所示的基于云名片的电话呼叫方法，所述装置可以包括第一接收模块101、更新模块102和第一展示模块103。
其中，第一接收模块101用于接收云服务器发送的第一用户更新后的云名片。
更新模块102根据所述第一用户更新后的云名片更新本地已保存的所述第一用户对应的云名片。
第一展示模块103用于当所述第一用户与第二用户之间通信时，根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
由上述实施例可见，第二终端接收云服务器发送的第一用户更新后的云名片，第一用户是第二终端对应的第二用户的联系人，根据第一用户更新后的云名片自动更新本地已保存的第一用户对应的云名片，当第一用户与第二用户之间通信时，根据第一用户更新后的云名片识别第一用户，并展示第一用户更新后的云名片，以使第二用户根据第一用户更新后的云名片能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
如图11示，图11本公开根据一示例性实施例示出的另一种基于云名片的电话呼叫装置的框图，所述装置应用于第二用户使用的第二终端上，用于执行图5所示的基于云名片的电话呼叫方法，所述装置还可以包括第二接收模块111、保存模块112和第二展示模块113。
其中，第二接收模块111用于接收所述云服务器发送的所述第一用户创建的云名片。
保存模块112用于将所述第一用户创建的云名片保存在本地通信录中。
第二展示模块113用于当所述第一用户与所述第二终端对应的第二用户之间通信时，展示所述第一用户更新后的云名片，以使所述第二用户根据所述第一用户更新后的云名片识别所述第一用户。
由上述实施例可见，第二终端接收云服务器发送的第一用户创建的云名片，将第一用户创建的云名片自动保存在本地通信录中，第一用户与第二用户之间通信时，根据第一用户创建的云名片识别第一用户，并展示第一用户创建的云名片，以使第二用户根据第一用户创建的云名片能够自动识别第一用户，从而提高了第二用户识别第一用户的速率和正确度，还提高了第二用户的用户体验。
与图7相应的，本公开还提供另一种基于云名片的电话呼叫装置，所述装置应用于云 服务器上，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收第一用户的云名片信息，所述云名片信息携带有所述第一用户的用户标识；
当根据所述第一用户的用户标识查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息对所述第一用户对应的云名片进行更新，得到所述第一用户更新后的云名片；
将所述第一用户更新后的云名片发送至第二用户，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
与图10相应的，本公开还提供另一种基于云名片的电话呼叫装置，所述装置应用于第二终端上，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收云服务器发送的第一用户更新后的云名片；
根据所述第一用户更新后的云名片更新本地已保存的所述第一用户对应的云名片；
当所述第一用户与所述第二终端对应的第二用户之间通信时，根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
上述装置中各个模块的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本公开方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
如图12所示，图12是根据一示例性实施例示出的一种用于基于云名片的电话呼叫装置1900的一结构示意图(云服务器侧)，例如，装置1900包括处理组件1922，其进一步包括一个或多个处理器，以及由存储器1932所代表的存储器资源，用于存储可由处理部件1922的执行的指令，例如应用程序。存储器1932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件1922被配置为执行指令。
装置1900还可以包括一个电源组件1926被配置为执行装置1900的电源管理，一个有线或无线网络接口1950被配置为将装置1900连接到网络，和一个输入输出(I/O)接口1958。装置1900可以操作基于存储在存储器1932的操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM或类似。
如图13所示，图13是本公开根据一示例性实施例示出的一种用于基于云名片的电话呼叫装置1300的另一结构示意图(终端设备侧)。例如，装置1300可以是具有路由功能的移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图13，装置1300可以包括以下一个或多个组件：处理组件1302，存储器1304，电源组件1306，多媒体组件1308，音频组件1310，输入/输出(I/O)的接口1312，传感器组件1313，以及通信组件1316。
处理组件1302通常控制装置1300的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件1302可以包括一个或多个处理器1320来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1302可以包括一个或多个模块，便于处理组件1302和其他组件之间的交互。例如，处理组件1302可以包括多媒体模块，以方便多媒体组件1308和处理组件1302之间的交互。
存储器1304被配置为存储各种类型的数据以支持在装置1300的操作。这些数据的示例包括用于在装置1300上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1304可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1306为装置1300的各种组件提供电力。电源组件1306可以包括电源管理系统，一个或多个电源，及其他与为装置1300生成、管理和分配电力相关联的组件。
多媒体组件1308包括在所述装置1300和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1308包括一个前置摄像头和/或后置摄像头。当装置1300处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1310被配置为输出和/或输入音频信号。例如，音频组件1310包括一个麦克风(MIC)，当装置1300处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1304 或经由通信组件1316发送。在一些实施例中，音频组件1310还包括一个扬声器，用于输出音频信号。
I/O接口1312为处理组件1302和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1313包括一个或多个传感器，用于为装置1300提供各个方面的状态评估。例如，传感器组件1313可以检测到装置1300的打开/关闭状态，组件的相对定位，例如所述组件为装置1300的显示器和小键盘，传感器组件1313还可以检测装置1300或装置1300一个组件的位置改变，用户与装置1300接触的存在或不存在，装置1300方位或加速/减速和装置1300的温度变化。传感器组件1313可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1313还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1313还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器，微波传感器或温度传感器。
通信组件1316被配置为便于装置1300和其他设备之间有线或无线方式的通信。装置1300可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件1316经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件1316还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1300可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1304，上述指令可由装置1300的处理器1320执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (14)

  1. 一种基于云名片的电话呼叫方法，其特征在于，所述方法包括：
    接收第一用户的云名片信息，所述云名片信息携带有所述第一用户的用户标识；
    当根据所述第一用户的用户标识查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息对所述第一用户对应的云名片进行更新，得到所述第一用户更新后的云名片；
    将所述第一用户更新后的云名片发送至第二用户，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
  2. 根据权利要求1所述的方法，其特征在于，所述第一用户的云名片信息包括所述第一用户对应的云名片所包括的各项信息和版本号；所述根据所述第一用户的云名片信息对所述第一用户对应的云名片进行更新，得到所述第一用户更新后的云名片具体包括：
    将接收到的版本号与本地已保存的所述第一用户对应的云名片的版本号进行比较，得到比较结果；
    当所述比较结果指示接收到的云名片信息是本地已保存的所述第一用户对应的云名片的更新版本时，利用接收到的云名片信息更新本地已保存的所述第一用户对应的云名片，得到所述第一用户更新后的云名片。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    当根据所述第一用户的用户标识没有查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息创建所述第一用户对应的云名片，得到所述第一用户创建的云名片；
    将所述第一用户创建的云名片发送至第二用户对应的第二终端，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户创建的云名片识别所述第一用户，并展示所述第一用户创建的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述第一用户与所述第二用户之间通信，包括如下通信方式中的至少一种：
    所述第一用户采用更新后的电话号码向所述第二用户发起呼叫；
    所述第一用户采用更新后的电话号码向所述第二用户发送短信；
    所述第一用户采用更新后的邮箱地址向所述第二用户发送电子邮件；
    其中，所述更新后的电话号码、所述更新后的邮箱地址存储于所述第一用户的名片信息中。
  5. 一种基于云名片的电话呼叫方法，其特征在于，所述方法包括：
    接收云服务器发送的第一用户更新后的云名片；
    根据所述第一用户更新后的云名片更新本地已保存的所述第一用户对应的云名片；
    当所述第一用户与第二用户之间通信时，根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    接收所述云服务器发送的所述第一用户创建的云名片；
    将所述第一用户创建的云名片保存在本地通信录中；
    当所述第一用户与所述第二用户之间通信时，根据所述第一用户创建的云名片识别所述第一用户，并展示所述第一用户创建的云名片。
  7. 一种基于云名片的电话呼叫装置，其特征在于，所述装置包括：
    接收模块，用于接收第一用户的云名片信息，所述云名片信息携带有所述第一用户的用户标识；
    更新模块，用于当根据所述第一用户的用户标识查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息对所述第一用户对应的云名片进行更新，得到所述第一用户更新后的云名片；
    第一发送模块，用于将所述第一用户更新后的云名片发送至第二用户，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
  8. 根据权利要求7所述的装置，其特征在于，所述第一用户的云名片信息包括所述第一用户对应的云名片所包括的各项信息和版本号；所述更新模块包括：
    比较子模块，用于将接收到的版本号与本地已保存的所述第一用户对应的云名片的版本号进行比较，得到比较结果；
    更新子模块，用于当所述比较结果指示接收到的云名片信息是本地已保存的所述第一用户对应的云名片的更新版本时，利用接收到的云名片信息更新本地已保存的所述第一用户对应的云名片，得到所述第一用户更新后的云名片。
  9. 根据权利要求7所述的装置，其特征在于，所述装置还包括：
    创建模块，用于当根据所述第一用户的用户标识没有查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息创建所述第一用户对应的云名片，得到所述第一用户创建的云名片；
    第二发送模块，用于将所述第一用户创建的云名片发送至第二用户对应的第二终端，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户创建的云名片识别所述第一用户，并展示所述第一用户创建的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
  10. 根据权利要求7-9中任一项所述的装置，其特征在于，所述第一用户与所述第二 用户之间通信，包括如下通信方式中的至少一种：
    所述第一用户采用更新后的电话号码向所述第二用户发起呼叫；
    所述第一用户采用更新后的电话号码向所述第二用户发送短信；
    所述第一用户采用更新后的邮箱地址向所述第二用户发送电子邮件；
    其中，所述更新后的电话号码、所述更新后的邮箱地址存储于所述第一用户的名片信息中。
  11. 一种基于云名片的电话呼叫装置，其特征在于，所述装置包括：
    第一接收模块，用于接收云服务器发送的第一用户更新后的云名片；
    更新模块，根据所述第一用户更新后的云名片更新本地已保存的所述第一用户对应的云名片；
    第一展示模块，用于当所述第一用户与第二用户之间通信时，根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
  12. 根据权利要求11所述的装置，其特征在于，所述装置还包括：
    第二接收模块，用于接收所述云服务器发送的所述第一用户创建的云名片；
    保存模块，用于将所述第一用户创建的云名片保存在本地通信录中；
    第二展示模块，用于当所述第一用户与所述第二用户之间通信时，根据所述第一用户创建的云名片识别所述第一用户，并展示所述第一用户创建的云名片。
  13. 一种基于云名片的电话呼叫装置，其特征在于，所述装置包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    接收第一用户的云名片信息，所述云名片信息携带有所述第一用户的用户标识；
    当根据所述第一用户的用户标识查询到所述第一用户对应的云名片时，根据所述第一用户的云名片信息对所述第一用户对应的云名片进行更新，得到所述第一用户更新后的云名片；
    将所述第一用户更新后的云名片发送至第二用户，以使当所述第一用户与所述第二用户之间通信时，所述第二用户根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
  14. 一种基于云名片的电话呼叫装置，其特征在于，所述装置包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    接收云服务器发送的第一用户更新后的云名片；
    根据所述第一用户更新后的云名片更新本地已保存的所述第一用户对应的云名片；
    当所述第一用户与所述第二终端对应的第二用户之间通信时，根据所述第一用户更新后的云名片识别所述第一用户，并展示所述第一用户更新后的云名片，所述第二用户为存储有所述第一用户的用户标识的用户。
PCT/CN2015/095162 2015-04-27 2015-11-20 基于云名片的电话呼叫方法及装置 Ceased WO2016173246A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
MX2016002128A MX363947B (es) 2015-04-27 2015-11-20 Metodos y dispositivos para llamar basados en tarjeta de la nube.
JP2017514783A JP2017518008A (ja) 2015-04-27 2015-11-20 クラウドカードに基づく電話呼び出し方法、装置、プログラム及び記録媒体
KR1020167001057A KR101810514B1 (ko) 2015-04-27 2015-11-20 클라우드 카드에 기반한 전화 호출 방법, 장치, 프로그램 및 저장 매체
RU2016115694A RU2645282C2 (ru) 2015-04-27 2015-11-20 Способ и устройство для вызова по облачным визиткам

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510205370.3 2015-04-27
CN201510205370.3A CN104767857A (zh) 2015-04-27 2015-04-27 基于云名片的电话呼叫方法及装置

Publications (1)

Publication Number Publication Date
WO2016173246A1 true WO2016173246A1 (zh) 2016-11-03

Family

ID=53649449

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/095162 Ceased WO2016173246A1 (zh) 2015-04-27 2015-11-20 基于云名片的电话呼叫方法及装置

Country Status (8)

Country Link
US (1) US20160314164A1 (zh)
EP (1) EP3089436A1 (zh)
JP (1) JP2017518008A (zh)
KR (1) KR101810514B1 (zh)
CN (1) CN104767857A (zh)
MX (1) MX363947B (zh)
RU (1) RU2645282C2 (zh)
WO (1) WO2016173246A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104767857A (zh) * 2015-04-27 2015-07-08 小米科技有限责任公司 基于云名片的电话呼叫方法及装置
CN105163307A (zh) * 2015-07-31 2015-12-16 小米科技有限责任公司 分享云名片的方法及装置
CN105681399B (zh) * 2015-12-29 2019-11-08 魅族科技（中国）有限公司 名片获取方法和装置
CN108495301A (zh) * 2018-03-20 2018-09-04 苏州蜗牛数字科技股份有限公司 云卡服务器sim卡集群读卡通讯系统及方法
US10909359B2 (en) * 2018-05-29 2021-02-02 Jacqueline Marie Franklin Application for use with business cards
CN108810190A (zh) * 2018-07-17 2018-11-13 北京思源互联科技有限公司 一种数字名片的更新方法
CN110839048B (zh) * 2018-08-15 2022-07-15 北京思源理想控股集团有限公司 一种基于vcard文件实现移动门户数据更新的系统及方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110131504A1 (en) * 2009-11-30 2011-06-02 Xerox Corporation Method and system for storing and distributing social and business contact information online
CN102752392A (zh) * 2012-07-12 2012-10-24 北京灵创众和科技有限公司 一种用户联系方式的共享方法、装置及系统
CN103095829A (zh) * 2013-01-15 2013-05-08 上海交通大学 实现版本管理和权限管理的网络通讯录系统
US20130311892A1 (en) * 2012-05-16 2013-11-21 Meng-Feng Hsieh Digital business card management system for mobile devices
CN104378434A (zh) * 2014-11-20 2015-02-25 无锡悟莘科技有限公司 基于云平台的多终端联系人更新系统
CN104767857A (zh) * 2015-04-27 2015-07-08 小米科技有限责任公司 基于云名片的电话呼叫方法及装置

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11136280A (ja) * 1997-10-31 1999-05-21 Hitachi Ltd 電子メールシステムおよび方法
JP3654773B2 (ja) * 1998-07-08 2005-06-02 富士通株式会社 情報交換方法、情報管理流通装置、情報管理装置、情報流通装置、情報管理流通プログラムを記録したコンピュータ読み取り可能な記録媒体、情報管理プログラムを記録したコンピュータ読み取り可能な記録媒体及び情報流通プログラムを記録したコンピュータ読み取り可能な記録媒体
US20020087353A1 (en) * 2001-01-04 2002-07-04 Telefree Inc. Method of connecting calls between a business card transmitter and a business card receiver through the medium of a web business card sent by the business card transmitter and system for the same
KR100724975B1 (ko) * 2004-04-09 2007-06-04 삼성전자주식회사 프레전스 정보를 이용한 전자 명함 서비스 시스템 및 방법
JP2007066051A (ja) * 2005-08-31 2007-03-15 Matsushita Electric Ind Co Ltd メールアドレス変更通知システム
EP1819125A1 (en) * 2006-02-10 2007-08-15 Siemens S.p.A. Method and apparatus to deliver precustomized business card multimedia contents through IMS based PLMNs for improving the existing calling line identification service
CN101599974B (zh) * 2008-05-27 2012-05-30 苏州华脉通讯科技有限公司 移动多媒体名片实时更新的方法
CN102025838A (zh) * 2009-09-09 2011-04-20 中兴通讯股份有限公司 多媒体彩铃资源盒的展现方法与装置
CN101795260A (zh) * 2009-12-24 2010-08-04 宇龙计算机通信科技(深圳)有限公司 一种联系人头像显示方法及对应服务系统、服务器、终端
SG172508A1 (en) * 2010-01-04 2011-07-28 Smart Communications Inc System and method for a global directory service
JP5096524B2 (ja) * 2010-06-01 2012-12-12 株式会社Ｔｄモバイル アドレス帳更新プログラムおよびアドレス帳更新システム
KR20130012154A (ko) * 2011-06-09 2013-02-01 (주)네이미 인터넷 명함 관리 방법 및 시스템
CN103634445B (zh) * 2013-11-19 2016-08-17 云宏信息科技股份有限公司 来电显示方法及装置
CN104486748B (zh) * 2014-12-17 2018-01-16 广东欧珀移动通信有限公司 联系人号码更新方法及移动终端

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110131504A1 (en) * 2009-11-30 2011-06-02 Xerox Corporation Method and system for storing and distributing social and business contact information online
US20130311892A1 (en) * 2012-05-16 2013-11-21 Meng-Feng Hsieh Digital business card management system for mobile devices
CN102752392A (zh) * 2012-07-12 2012-10-24 北京灵创众和科技有限公司 一种用户联系方式的共享方法、装置及系统
CN103095829A (zh) * 2013-01-15 2013-05-08 上海交通大学 实现版本管理和权限管理的网络通讯录系统
CN104378434A (zh) * 2014-11-20 2015-02-25 无锡悟莘科技有限公司 基于云平台的多终端联系人更新系统
CN104767857A (zh) * 2015-04-27 2015-07-08 小米科技有限责任公司 基于云名片的电话呼叫方法及装置

Also Published As

Publication number Publication date
EP3089436A1 (en) 2016-11-02
MX2016002128A (es) 2017-01-18
MX363947B (es) 2019-04-08
CN104767857A (zh) 2015-07-08
JP2017518008A (ja) 2017-06-29
US20160314164A1 (en) 2016-10-27
RU2016115694A (ru) 2017-10-26
KR101810514B1 (ko) 2017-12-19
KR20160137936A (ko) 2016-12-02
RU2645282C2 (ru) 2018-02-19

Similar Documents

Publication Publication Date Title
US9953212B2 (en) Method and apparatus for album display, and storage medium
WO2016192326A1 (zh) 云名片的发送方法和装置
WO2016173246A1 (zh) 基于云名片的电话呼叫方法及装置
WO2017201861A1 (zh) Zigbee设备的升级方法和装置
CN109600303B (zh) 内容分享方法、装置及存储介质
WO2017016148A1 (zh) 基于图像的通信方法及装置
WO2017088247A1 (zh) 输入处理方法、装置及设备
CN106777016B (zh) 基于即时通信进行信息推荐的方法及装置
WO2017045307A1 (zh) 接听扩展功能显示方法及装置
CN105610700A (zh) 群组创建方法、装置及电子设备
WO2017035992A1 (zh) 消息的发送方法、装置、终端及路由器
CN107094094B (zh) 应用程序的连网方法、装置及终端
CN105847111A (zh) 添加好友的方法及装置
WO2017080205A1 (zh) 一种锁屏壁纸相关信息获取方法及装置
CN106095465A (zh) 设置身份图像的方法及装置
CN105704016A (zh) 一种群消息屏蔽处理方法、装置及终端
CN107423386A (zh) 生成电子卡片的方法及装置
WO2017088380A1 (zh) 界面显示方法和装置
CN105791097A (zh) 一种群消息接收处理方法、装置及终端
WO2017054350A1 (zh) 一种提醒方法及装置
WO2017035995A1 (zh) 联系人记录处理方法及装置
CN104881342A (zh) 终端测试方法及装置
CN105843894A (zh) 信息推荐方法及装置
CN105095296B (zh) 文件管理方法及装置
CN106572003A (zh) 用户信息推荐方法和装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 20167001057

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017514783

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2016/002128

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 2016115694

Country of ref document: RU

Kind code of ref document: A

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

Ref document number: 15890621

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112016009406

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112016009406

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20160427

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15890621

Country of ref document: EP

Kind code of ref document: A1