CN110383861B - Method and terminal for sharing information in call - Google Patents

Method and terminal for sharing information in call Download PDF

Info

Publication number
CN110383861B
CN110383861B CN201780087933.0A CN201780087933A CN110383861B CN 110383861 B CN110383861 B CN 110383861B CN 201780087933 A CN201780087933 A CN 201780087933A CN 110383861 B CN110383861 B CN 110383861B
Authority
CN
China
Prior art keywords
information
party
calling party
option
service
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.)
Active
Application number
CN201780087933.0A
Other languages
Chinese (zh)
Other versions
CN110383861A (en
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2017/075607 priority Critical patent/WO2018157389A1/en
Publication of CN110383861A publication Critical patent/CN110383861A/en
Application granted granted Critical
Publication of CN110383861B publication Critical patent/CN110383861B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices

Abstract

A method for sharing information during a call is disclosed. The method comprises the following steps: a first calling party and a second calling party establish calling connection; the first calling party receives a sharing request sent by the second calling party, wherein the sharing request is used for requesting to acquire information corresponding to the predefined required information option; the second party defining the desired information option; the required information option is used for representing information which the second calling party needs to obtain from the first calling party; the first calling party acquires information corresponding to the required information option; and the first calling party sends the information corresponding to the required information option to the second calling party. The scheme can improve the information sharing efficiency in the call.

Description

Method and terminal for sharing information in call
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and a terminal for sharing information during a call.
Background
With the rapid development of electronic communication technology, telephone conversation is a common information communication mode, and is relatively direct and efficient. Besides the telephone communication content, people also need to share other information in the call, such as the name card of the contact person.
At present, during a call, one party of the call can directly share information in a verbal way, for example, the party vocally speaks the related information of the name card of a contact to be shared, and the other party of the call can record the information in a manual way. Or, one party of the call can manually send a short message to the other party of the call, and the content of the short message is the shared information. The information sharing mode has low operation efficiency and is not suitable for information sharing of large data volume.
Particularly in the context of a telephone call for a hotline, a hotline worker (e.g., an agent) needs to consult some detailed information about the user in order to provide professional services to the user. For example, a hotline worker providing a cell phone service verbally asks the user about the cell phone version number, International Mobile Equipment Identity (IMEI), and other configuration parameters, etc. to analyze what the user's cell phone may have. For the query of the hotline staff, the user provides information required by the hotline staff by spoken answers. Meanwhile, the hotline staff needs to manually record the information provided by the user during the call. The conventional method for sharing information in a call involves a large number of manual operations and is low in efficiency.
Disclosure of Invention
The embodiment of the invention provides a method and a terminal for sharing information in a call, which can improve the efficiency of sharing information in the call.
In a first aspect, a method for sharing information in a call is provided, and is applied to a first party side, where the method may include: the first calling party and the second calling party establish calling connection, receive a sharing request sent by the second calling party and acquire information corresponding to the required information options. And finally, the first calling party sends the information corresponding to the required information option to the second calling party.
In a second aspect, a method for sharing information in a call is provided, and applied to a second party, the method may include: the second calling party and the first calling party establish calling connection, send a sharing request to the first calling party and receive information sent by the first calling party, wherein the information is acquired by the first calling party according to predefined required information options.
In this application, the second party defines the required information option, and the required information option is used to represent information that the second party needs to obtain from the first party. The sharing request is used for requesting to acquire information corresponding to the predefined required information option.
By implementing the method for sharing information in a call described in the first aspect and the second aspect, the efficiency of sharing information in a call can be improved.
Application scenarios to which the present application relates may include hotline scenarios and non-hotline scenarios.
First, a non-hotline phone scenario.
In a non-hotline scenario, the first party and the second party may both be user terminals. The following develops the implementation of the present application in a non-hotline telephony scenario.
In a non-hotline scenario, the second party may pre-define a plurality of required information options for different contacts, indicating which required information the second party needs to obtain from different contacts respectively. Thus, when the second party and the contact are talking, the second party may request that the contact share information according to the desired information options for the contact.
In some alternative embodiments, the different contacts may refer to different groups of contacts. That is, the second party may group contacts and define different desired information options for different groups of contacts.
Optionally, the second party may be grouped according to the degree of closeness between the second party and each contact, for example, a family group, a friend group, and a co-worker group. Generally, the desired information option corresponding to the contact group with higher intimacy degree may be a more private information option. Optionally, the second party may also be grouped according to a transaction cooperation type between the second party and each contact. In practical applications, the contacts may be grouped in other manners, which is not limited herein.
In a non-hotline scenario, the second party may send the first party a predefined desired information option for the first party. Correspondingly, the first party may receive the required information option for the first party sent by the second party, and cache the required information option for the first party.
In one implementation, the second party may send the required information option to the first party when establishing a communication with the first party. For example, when the second caller adds the first caller to a contact group "colleague group" in the phonebook for the first time, a predefined required information option for "colleague group" is sent to the first caller.
In another implementation, the second party may trigger sending of the desired information option to the first party by the second party user when the first party user and the second party user are facing, which may prompt the first party to receive the desired information option in person.
The method for sending the required information option to the first party by the second party may be implemented by the first party, and the method is not limited to the above two implementations.
Optionally, the second party may also upload the predefined required information option for the first party to a server, and then send the server address to the first party. In this way, the first party can download the predefined desired information options from the server according to the server address.
In a non-hotline phone scenario, the sharing request sent by the second caller may be used to request to acquire the required information that the second caller needs to acquire from the first caller, that is, information corresponding to a predefined required information option for the first caller. Accordingly, after receiving the sharing request, the first party may perform authority verification on the second party. If the authority verification is passed, the first calling party can acquire the information which the second calling party needs to acquire from the first calling party according to the predefined required information option aiming at the first calling party.
In a specific implementation, the sharing request may be actively triggered by the second talker. The sharing request may also be triggered automatically, for example, 10 seconds after the call starts, and the second party automatically sends the sharing request to the first party. The embodiment of the present invention does not limit the initiation manner of the sharing request.
In a specific implementation, the sharing request may carry an identity of the second party. Therefore, in a multi-person communication scene, the first communication party can judge that the communication party requesting information sharing is the second communication party according to the identity, and therefore information sharing is performed on the second communication party. Optionally, the sharing request may not carry the identity of the second party. In a two-party communication scenario between the first party and the second party, the first party may determine that the sharing request is initiated by the second party according to an incoming call number or an outgoing call number.
Second, a hotline scenario.
In a hotline scenario, the second party may be a hotline facilitator and the first party may be a user terminal. The implementation of the present application in a hotline scenario is described below.
In a hotline phone scenario, the second party may pre-define required information options corresponding to each service, and upload the defined required information options corresponding to each service to the cloud storage server. When the required information options corresponding to the services need to be updated, for example, the required information options are newly added, deleted, and changed, the second party may also upload the updated required information options to the cloud storage server.
In a hotline phone scenario, the first party may download and cache the required information options corresponding to the services from a cloud server. Optionally, the user terminal may download the required information option periodically, so as to update the required information option in time, so that the required information option stored at the user terminal side is consistent with the required information option on the cloud storage server.
In a hotline phone scenario, the sharing request sent by the second caller may be used to request to obtain the required information corresponding to the target service selected by the first caller. The target service is selected by the first party from the services. Correspondingly, the first calling party can acquire the required information corresponding to the target service according to the required information option corresponding to the target service.
In a hotline scenario, after establishing a call connection, the second party may send a service selection prompt to the first party to prompt the first party to select a service. Correspondingly, the first communication party can receive the service selection prompt sent by the second communication party, select the target service according to the service selection prompt, and send the identification information of the target service to the second communication party.
In one implementation, the selecting process of the target service may include:
1. the second party may voice prompt the first party to select the target service via a dial-up button. For example, the second party may use IVR to automatically play a voice prompt "welcome to use the after-sales service platform of company a" for selecting a service via a button on the dial pad. '1' is a telephone module maintenance service, '2' is a camera maintenance service, and '3' is a Wi-Fi module maintenance service. "examples" are intended only to illustrate embodiments of the invention and should not be construed as limiting.
2. The user of the first party may select a key representing the target service according to the voice prompt. The first party may send DTMF signals characterizing the target service to the second party after recognizing the key selected by the user. Therefore, the second calling party can analyze the key according to the DTMF signal, and further determine the target service selected by the first calling party according to the key.
In another implementation, the selecting process of the target service may include:
1. the second party may send a service selection page to the first party, where each service option provided by the second party is displayed in the service selection page.
2. The user of the first calling party can select the service option corresponding to the target service in the service selection page. After identifying and recording the service option corresponding to the target service selected by the user, the first party may send the service option corresponding to the target service selected by the user to the second party.
In a specific implementation, the first party may send the service name of the target service to the second party, and may also send the service ID of the target service to the second party. In practical applications, the first party and the second party may also agree with other ways to notify the target service, which is not limited herein.
In some optional embodiments, on the first caller side, the service selection page may be displayed in a call interface. In some optional embodiments, at the first calling party side, the service selection page may also be independently displayed above a calling interface, and may fully or partially cover the calling interface. The examples are merely some implementations of the embodiments of the present invention, and may be different in practical applications, and should not be construed as limiting.
Optionally, the above two target service selection processes may also be implemented in combination, and are not limited herein.
In combination with a non-hotline scenario and a hotline scenario, in an implementation, if the required information corresponding to the target service includes the required information maintained by the first party, the first party may directly acquire the required information maintained by the first party through a system interface. In another implementation manner, if the required information corresponding to the target service includes required information maintained by a third party, the first party needs to implement an API provided by the third party, and requests the third party to acquire the required information maintained by the third party by calling the API of the third party. It should be noted that the third party is not limited to the third party application, and may also be a third party service, a third party platform, and the like.
Combining a non-hotline telephone scene and a hotline telephone scene, after acquiring the required information corresponding to the target service, the first calling party can display the required information corresponding to the target service, and then according to user authorization, the required information to be shared is determined from the required information corresponding to the target service. Here, the user authorization may be used to select the required information to be shared, and authorize the sharing of the required information to be shared to the second party.
Specifically, the user operation corresponding to the user authorization may have various forms, such as a selection operation, a deletion operation, and the like, and the embodiment of the present invention is not limited. In some optional embodiments, the user authorization may also be obtained by the first party in advance. For example, when the first party installs a client provided by the second party, the client may ask the user to authorize the relevant operations (e.g., reading operation of operating system configuration information, etc.) involved in the client. The example is only one implementation manner of the embodiment of the present invention, and may also be different in practical applications, and should not be construed as a limitation.
In combination with the non-hotline scenario and the hotline scenario, the first party may send the required information to the second party over one or more of a TCP/IP data connection, a UDP/IP data connection, an SMS or an MMS. In practical applications, the first party and the second party may also use other data transmission methods, for example, a point-to-point transmission method, to send the required information, which is not limited herein.
In a third aspect, a terminal is provided for performing the method described in the first aspect. The terminal may include: a memory, and a processor, a communication module coupled with the memory, wherein: the communication module is configured to communicate with other terminals, the memory is configured to store implementation codes of the method for sharing information during a call described in the first aspect, and the processor is configured to execute the program codes stored in the memory, that is, to execute the method for sharing information during a call provided by the first aspect or any one of the possible implementations of the first aspect.
In a fourth aspect, a terminal is provided for performing the method described in the second aspect. The terminal may include: a memory, and a processor, a communication module coupled with the memory, wherein: the communication module is configured to communicate with other terminals, the memory is configured to store implementation codes of the method for sharing information during a call described in the second aspect, and the processor is configured to execute the program codes stored in the memory, that is, execute the method for sharing information during a call provided by the second aspect or any one of the possible implementations of the second aspect.
In a fifth aspect, a terminal is provided, which comprises a plurality of functional modules for performing the method provided in the first aspect or any one of the possible implementation manners of the first aspect.
In a sixth aspect, a terminal is provided, which comprises a plurality of functional modules for performing the method provided by the second aspect or any of the possible embodiments of the second aspect.
In a seventh aspect, a computer-readable storage medium is provided, where the computer-readable storage medium stores a program code implementing the method for sharing information in a call described in the first aspect, and the program code includes an execution instruction for executing the method for sharing information in a call described in the first aspect.
In an eighth aspect, a computer-readable storage medium is provided, where the computer-readable storage medium stores program code implementing the method for sharing information in a call described in the second aspect, and the program code includes instructions for executing the method for sharing information in a call described in the second aspect.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly introduced below.
FIG. 1 is a schematic diagram of a hotline application scenario to which embodiments of the present invention relate;
fig. 2 is a schematic flow chart illustrating information sharing during a call in a hotline scenario according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a method for sharing information during a call according to an embodiment of the present invention;
fig. 4A-4B are schematic diagrams of two types of target services selected in a call according to an embodiment of the present invention;
FIG. 5 is an exemplary diagram of a hotline voice prompt provided by an embodiment of the invention;
FIGS. 6A-6C are schematic diagrams of several service selection pages provided by embodiments of the present invention;
fig. 7 is a schematic diagram of another method for selecting a target service in a call according to an embodiment of the present invention;
FIGS. 8A-8C are diagrams of several options for sharing desired information provided by embodiments of the present invention;
FIG. 9 is a schematic diagram of a non-hotline phone application scenario in accordance with an embodiment of the present invention;
fig. 10 is a flowchart illustrating another method for sharing information during a call according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of a server according to an embodiment of the present invention;
fig. 12 is a schematic structural diagram of a terminal according to an embodiment of the present invention;
FIG. 13 is a schematic diagram of the internal collaboration interaction of the embodiment of FIG. 3 provided by an embodiment of the invention;
FIG. 14 is a schematic diagram of the internal collaboration interaction of the embodiment of FIG. 10 provided by an embodiment of the invention;
fig. 15 is a schematic structural diagram of a terminal according to an embodiment of the present invention;
fig. 16 is a schematic structural diagram of another terminal according to an embodiment of the present invention.
Detailed Description
The terminology used in the description of the embodiments section of the present application is for the purpose of describing particular embodiments of the invention only and is not intended to be limiting of the invention.
Aiming at the problems in the prior art, the application provides a method for sharing information in a call, which can improve the efficiency of sharing information in the call between two parties of the call.
The main principles involved in this application may include: the party to the call predefines which information needs to be obtained from the other party to the call. In this embodiment of the present invention, information that one party of the call needs to acquire from the other party of the call may be referred to as required information (required information). That is, the calling party has predefined the required information options. In a call, the party to the call may request the other party to the call to share the required information. The other party of the call can respond to the request, acquire the required information according to the required information option predefined by the one party of the call, and share the acquired required information to the one party of the call. This improves the efficiency of sharing information during a call.
The method for sharing information during a call provided by the present application is described in detail below from a hotline scenario and a non-hotline scenario, respectively.
Referring first to fig. 1, fig. 1 is a schematic view of a hotline phone service system according to the present invention. The hotline phone service system 100 shown in fig. 1 may support a corresponding hotline phone service provider to provide a plurality of services to a user, and the user terminal 20 may access the hotline phone service system 100 through telephone, sms, internet, and the like to obtain services provided by the hotline phone service provider. As shown in fig. 1, the hotline phone service system 100 may include: management server 101, storage server 102, and agent 103. Wherein:
the management server 101 is responsible for implementing functions of system running state management, authority management, agent management, data management and statistics, system security maintenance and the like. In a specific implementation, the management server 101 may support running a service management system, a customer management system, an agent management system, and the like. The service management system is responsible for various service management, including: defining and creating services, adding new services, counting service use conditions and the like. The customer management system is responsible for collecting and maintaining relevant data of customers, including displaying customer information and the like on the agent terminal. The seat management system is responsible for managing the seat personnel, including seat registration, seat authority management and the like.
The storage server 102 is responsible for providing functions such as data storage and data access of the system. Customer information, interactive data, business data, etc. are stored in the storage server 102 to provide support for the services of seat personnel and provide basis for the decision of management personnel. It can be understood that the data of the hotline phone service system 100 is accumulated over time, the data amount is very large, and thus the requirement for the data processing capability is quite high. In a specific implementation, a large database, such as SQL Server, Oracle, etc., is generally deployed on the storage Server 102. For particularly important data materials, the storage server 102 may generally use a dual-computer hot backup to ensure data security.
The seat 103 refers to a service representative (also called a seat person) and its working equipment, such as a telephone set, an earphone, a microphone, a Computer or a Computer terminal running Computer Telephony Integration (CTI) program, and the like. The agent 103 can complete the operations of answering, hanging up, transferring, dialing out and the like of the telephone through a mouse and a keyboard, and the agent 103 can be divided into a common agent, an expert agent, a management agent (a class and a chief agent) and the like according to the capability of processing services. It should be understood that a plurality of agents 103 may be generally configured in the hotline phone service system 100, and may provide business services for a plurality of users at the same time.
In particular implementations, the hotline telephone service system 100 may be implemented as a call center. The management server 101 may be integrated with or connected to a CTI server, an Interactive Voice Response (IVR) system, a switch, an Automatic Call Distributor (ACD), and the like. The CTI server is used to provide a communication interface for the exchange and the computer to communicate with each other, so that the computer can display the user data on the computer screen of the seat 103 while the telephone is connected according to the information such as the calling number provided by the exchange. IVR systems are used to provide automated voice navigation services, such as voice prompting a user to select a type of service, when the user accesses a call center. The ACD may be mainly configured to reasonably allocate the access phone of the user to the plurality of agents 103 according to a preset allocation policy.
It should be noted that fig. 1 is only one embodiment of the hotline phone service system 100, and in practical applications, the hotline phone service system 100 may include more or less components.
As shown in fig. 1, the hotline phone service system 100 may be a repair service system provided by a handset manufacturer for providing a variety of handset repair services to users.
The storage server 102 may be deployed with a database 30, and the database 30 may be used to record required information options corresponding to various maintenance services. Here, the required information (required information) corresponding to the service is that the service system 100 provides the user terminal information that the service needs to know. For example, the required information corresponding to the "phone module" service includes: handset model, operating system version, IMEI, etc. That is, the relevant maintenance personnel or the background maintenance system need to provide the "telephone module" maintenance service for the user according to several items of information such as the model of the mobile phone, the version of the operating system, the IMEI, etc., for example, to analyze the cause of the failure, to provide a solution, etc.
In one embodiment, the user terminal 20 may be accessed through a service switchboard number provided by the hotline telephone service system 100. For the access user, the hotline phone service system 100 may automatically play a prompt voice through the IVR to prompt the user to select a specific maintenance service through a button on the dial. For example, the prompt voice may be "welcome to use the mobile phone to repair the service, the key '1' is a phone module, the key '2' is a camera, and the key '3' is a Wi-Fi module". The examples are intended to illustrate embodiments of the invention and should not be construed as limiting. Assuming that the user presses the key "1" on the dial to select the "phone module" service, the hotline phone service system 100 assigns the seat 103 responsible for the "phone module" service to serve the user. It will be appreciated that the seat 103 responsible for the "phone module" service may typically be a service person proficient in the phone module service event.
At present, after the user's telephone is connected, the seat 103 responsible for the "telephone module" maintenance service can generally obtain several items of required information corresponding to the "telephone module" maintenance service from the user by means of oral inquiry, and then record the required information notified by the user in a manual manner. Alternatively, the agent 103 may record the required information notified by the user in a customer database. This way of sharing information in a hotline phone is less efficient.
Referring to fig. 2, in a hotline scenario, a general scheme of a method for sharing information during a call provided by the present application may be summarized as follows:
1. the hotline defines (or updates) the required information options for each service. For example, the hotline phone service provider may be the cell phone service provider in fig. 1, and may define the required information options corresponding to the "phone module" service include: mobile phone model, operating system version, IMEI, etc.
In a specific implementation, the hotline phone service provider may define a structural body for representing required information options, for example, the required information options corresponding to a "phone module" maintenance service may be represented as:
required_info{
String dev_id;
String version;
String IMEI;};
in a specific implementation, the hotline provider may further define a set of interfaces, for example, request _ info (int serv _ id), configured to request a user terminal to obtain required information corresponding to a service, where a return parameter of the function "request _ info" may be the structural required _ info, which represents the required information; the function input parameter "serv _ ID" represents the service ID of the service. It should be noted that the examples are only for explaining the embodiments of the present invention and should not be construed as limiting.
2. And uploading the required information options corresponding to the defined services to a cloud storage server by the hot line telephone service provider. When the required information options corresponding to each service need to be updated, for example, the required information options are newly added, deleted, and changed, the hotline phone service provider may also upload the updated required information options to the cloud storage server, so as to ensure that the required information options corresponding to each service stored on the cloud storage server are consistent with the required information options that have been updated by the hotline phone service provider last time.
3. The user terminal can download required information options corresponding to various services defined by the hotline telephone facilitator from the cloud storage server. Optionally, the user terminal may download the required information option periodically, so as to update the required information option in time, so that the required information option stored at the user terminal side is consistent with the required information option on the cloud storage server.
4. When the user terminal communicates with the hotline, for a target service (a service selected by the user), the user terminal may collect the required information corresponding to the target service according to the required information option (which has been downloaded in step 3) corresponding to the target service. Then, the user terminal can share the required information corresponding to the target service to the hot-line telephone service system, so that the hot-line seat can see the information shared by the user terminal on a computer screen, and the hot-line seat is convenient to further provide more professional services for the user.
In the embodiment of the present invention, the user terminal may be referred to as a first party, and the hotline provider may be referred to as a second party. In a specific implementation, the hotline phone service provider may be a server on the hotline phone service provider side, such as the management server 101 in the hotline phone service system 100 shown in fig. 1, or may be a terminal on the hotline phone service provider side, such as an agent terminal.
The method for sharing information during call provided by the embodiment of the invention in the hotline phone scenario is described in detail below with reference to fig. 3. As shown in fig. 3, the method may include:
S101-S103, the second party predefines the required information options corresponding to each service, and the first party downloads and caches the predefined required information options corresponding to each service, which may specifically refer to the description of fig. 2 and is not described herein again.
In a specific implementation, the first party may cache the downloaded required information option to a local. The first calling party can also cache the downloaded required information options to a corresponding remote storage position, for example, in a cloud office system, the terminal is not stored, and data of the terminal can be stored in a corresponding node on a cloud server. It should be noted that, the first party may also cache the downloaded required information option in the corresponding external storage. The embodiment of the present invention is not limited as to how the first party caches the downloaded required information option.
S104, the first calling party and the second calling party establish call connection.
In one implementation, the call connection may be established by the first party calling the second party, for example, the first party dialing a hotline number provided by the second party for hotline calling. In another implementation, the call connection may also be established by the second party calling the first party, for example, the second party dials a phone number of the first party for a customer return visit. The embodiment of the present invention is not limited to the establishment of the call connection.
S105, the first calling party selects a target service.
Specifically, after establishing the call connection, the second party may send a service selection prompt to the first party to prompt the first party to select a service. Correspondingly, the first communication party can receive the service selection prompt sent by the second communication party, select the target service according to the service selection prompt, and send the identification information of the target service to the second communication party.
Fig. 4A illustrates one implementation of the first party selecting a target service, which may include:
1. the second party may voice prompt the first party to select the target service via a dial-up button. For example, the second party may use IVR to automatically play a voice prompt "welcome to use the after-sales service platform of company a" for selecting a service via a button on the dial pad. '1' is a telephone module maintenance service, '2' is a camera maintenance service, and '3' is a Wi-Fi module maintenance service. "examples" are intended only to illustrate embodiments of the invention and should not be construed as limiting.
2. The user of the first party may select a key representing the target service according to the voice prompt. The first party may send DTMF signals characterizing the target service to the second party after recognizing the key selected by the user. Therefore, the second calling party can analyze the key according to the DTMF signal, and further determine the target service selected by the first calling party according to the key.
It should be understood that DTMF signals may be carried in the voice channel. In the embodiments of the present invention, the voice channel refers to voice transmission between a transceiver and a CS (Circuit Switch, CS) domain. That is, the implementation shown in fig. 4A can directly complete the selection of the target service through the voice channel without generating additional data overhead.
In practical application, when a target service is selected through voice prompt, the second calling party can provide multi-level voice prompt to gradually prompt the first calling party side to select the target service. For example, as shown in fig. 5, in the air ticket booking system, the voice prompt of the ticket booking service can be subdivided from top to bottom according to the service level. The voice prompt 1 is used for prompting the user to select a larger service category: the voice prompt 2 (or the voice prompt 3) prompts the user to select the ticket booking, the ticket returning or the ticket change service under the specific domestic service (or the foreign service), and the voice prompts 21-23 (or the voice prompts 31-33) are specifically used for prompting the user how to perform the ticket booking, the ticket returning or the ticket change of the domestic air ticket (or the foreign air ticket). The examples are intended to illustrate embodiments of the invention and should not be construed as limiting.
Fig. 4B illustrates another implementation of the first party selecting a target service, which may include:
1. the second party may send a service selection page to the first party, where each service option provided by the second party is displayed in the service selection page. For example, as shown in fig. 6A, the service selection page may include 4 service options of "call module", "camera", "Wi-Fi", and "touch screen". Optionally, the service selection page may also display additional information related to each service, for example, a common fault in fig. 6A, so that the user can know each service conveniently. The examples are intended to illustrate embodiments of the invention and should not be construed as limiting. In practical application, each service option may further correspond to a multi-hierarchy service structure, and the service selection page may further present the plurality of service options according to a service hierarchy.
In a specific implementation, each service option may be presented in the service selection page in a list form (as shown in fig. 5), a table form, or other interface layout forms. The interface layout form of the service selection page is not limited herein.
2. The user of the first calling party can select the service option corresponding to the target service in the service selection page. After identifying and recording the service option corresponding to the target service selected by the user, the first party may send the service option corresponding to the target service selected by the user to the second party.
In a specific implementation, the first party may send the service name of the target service to the second party, and may also send the service ID of the target service to the second party. In practical applications, the first party and the second party may also agree with other ways to notify the target service, which is not limited herein.
In some optional embodiments, on the first caller side, the service selection page may be displayed in a call interface. For example, as shown in FIG. 6B, the service selection page 40 is displayed in the call interface 50 along with the dial 60. In some optional embodiments, at the first calling party side, the service selection page may also be independently displayed above a calling interface, and may fully or partially cover the calling interface. For example, as shown in FIG. 6C, the service selection page 40 is displayed hovering above the telephony interface 50. The examples are merely some implementations of the embodiments of the present invention, and may be different in practical applications, and should not be construed as limiting.
It can be understood that in the implementation shown in fig. 4B, the service selection page needs to be carried in a data channel. In the embodiment of the present invention, the data channel refers to a data transmission Tunnel (Tunnel) established through an application layer session in data transmission between a transmitting end and a receiving end. The data channel may be a TCP data channel, a UDP data channel, or the like. The service selection page sent through the data channel can present richer information on the user side (refer to the common faults related to various maintenance services shown in fig. 6A), so that the user can select the service conveniently.
Optionally, the implementation shown in fig. 4A and the implementation shown in fig. 4B may also be combined. As shown in fig. 7, another implementation of the first party selecting the target service may include:
1. the second caller sends the service selection page to the first caller through a data channel, and the service selection page may prompt the user to select a target service through a key on a dial as shown in fig. 6. Specifically, the call module maintenance service is selected according to the expression of '1', the camera maintenance service is selected according to the expression of '2', the Wi-Fi maintenance service is selected according to the expression of '3', and the touch screen maintenance service is selected according to the expression of '4'.
2. Correspondingly, the user at the first calling party side can select the target service through a key on a dial plate. The first calling party can send the DTMF signal representing the target service to the second calling party through a voice channel. Therefore, the second calling party can analyze the key according to the DTMF signal and determine the target service selected by the first calling party according to the key.
The above shows several implementations of the first party selecting the target service. In some possible scenarios, the second party provides the extension number corresponding to each specific service, and the first party can directly access the specific service by dialing the extension number corresponding to the specific service without performing service selection. That is, the hotline number dialed by the first party may be used to indicate the target service selected by the first party.
For example, assume that the telephone number of the hotline telephone service provider in fig. 1 is "1000", the extension number corresponding to the telephone module "maintenance service is" 10001 ", the extension number corresponding to the camera" maintenance service is "10002", and the extension number corresponding to the Wi-Fi "maintenance service is" 10003 ". If the target service selected by the user is the 'telephone module' maintenance service, the user can directly dial '10001' to access the 'telephone module' maintenance service except that the 'telephone module' maintenance service is selected according to system prompts after dialing the switchboard number. The examples are intended to illustrate embodiments of the invention and should not be construed as limiting.
S106, after the first calling party selects the target service, the second calling party sends a sharing request to the first calling party. The sharing request can be used for requesting to acquire the required information corresponding to the target service.
In the call connection, the sharing request may be initiated by a hotline agent on the second party side, or may be initiated by a server background on the second party side. The embodiment of the present invention does not limit the initiation manner of the sharing request.
Optionally, the sharing request may include identification information of the target service, such as a service name or a service ID, for indicating that the second party wants to obtain required information corresponding to the target service. Optionally, the sharing request may not carry identification information of the target service, and the sharing request may be defaulted to the target service under the condition that the first party accesses the target service.
In a specific implementation, the second party may send the sharing request through a data channel or a voice channel. For the description of the data channel or the voice channel, reference is made to the foregoing description, and the description is omitted here.
S107, the first calling party receives the sharing request, responds to the sharing request, and obtains the required information corresponding to the target service according to the required information option corresponding to the target service.
In an implementation manner, if the required information corresponding to the target service includes the required information maintained by the first party, the first party may directly obtain the required information maintained by the first party through a system interface.
For example, assume that the target service is a "phone module" service in fig. 1, and its corresponding required information (handset model, operating system version, IMEI) is system configuration information of the user terminal (the first party). In a specific implementation, an Application Programming Interface (API) for reading the system configuration information may be provided for an operating system (e.g., an Android OS) on the user terminal, for example, get _ OS _ ver () may be an API for reading an operating system version provided by the operating system. The examples are intended to illustrate embodiments of the invention and should not be construed as limiting.
In another implementation manner, if the required information corresponding to the target service includes required information maintained by a third party, the first party needs to implement an API provided by the third party, and requests the third party to acquire the required information maintained by the third party by calling the API of the third party. It should be noted that the third party is not limited to the third party application, and may also be a third party service, a third party platform, and the like.
For example, assume that the target service is a book recommendation service, and the required information corresponding to the book recommendation service is a book purchase record of a user on a third-party application Amazon (Amazon). Then, the user terminal needs to implement and call an amazon (third party application) provided API for reading book purchase records of the user, such as get _ order _ info (int ID, string password), where ID is the user's account ID on amazon and password is the user's login password on amazon. In this way, after the amazon server authenticates that the account ID and the login password are legal, the book purchase record corresponding to the account ID can be returned to the user terminal. The examples are intended to illustrate embodiments of the invention and should not be construed as limiting.
It should be noted that, in the specific implementation, the required information corresponding to the target service may include the two situations: the required information maintained by the first party and the required information maintained by the third party.
S108-S110, after obtaining the required information corresponding to the target service, the first party may send the required information corresponding to the target service to the second party according to user authorization. Here, the required information transmitted to the second communication party may be all or part of the required information corresponding to the target service.
In a specific implementation, after receiving the sharing request, the first party may display the required information corresponding to the target service, and then determine the required information to be shared from the required information corresponding to the target service according to user authorization. Here, the user authorization may be used to select the required information to be shared, and authorize the sharing of the required information to be shared to the second party.
Specifically, the user operation corresponding to the user authorization may have various forms, such as a selection operation, a deletion operation, and the like, and the embodiment of the present invention is not limited.
For example, as shown in fig. 8A to 8C, after the user selects the "call module" maintenance service, for the sharing request, the first caller may select, according to the required information option corresponding to the "call module" maintenance service: the "mobile phone model", "operating system version", "IMEI", "supported mobile network", obtains the required information corresponding to the "call module" maintenance service: the mobile phone model is G6-C001, the operating system version is Android 6.0, the IMEI is 356235020006062, and the supported mobile network is cdma 2000/GSM. And, the first party may display various required information corresponding to the "call module" maintenance service, such as the required information display interface 70.
As shown in fig. 8A, a selection key 80 is provided in the desired information display interface 70 for receiving a selection operation by the user. Namely: the user operation corresponding to the user authorization may be a selection operation. The required information selected by the user, namely the required information to be shared which is authorized by the user to be shared to the second communication party.
As shown in fig. 8B, a delete key 80 is provided in the desired information display interface 70 for receiving a delete operation by the user. Namely: the user operation corresponding to the user authorization may be a deletion operation. The required information which is not deleted by the user is the required information which is authorized by the user to be shared by the second communication party and is to be shared.
As shown in fig. 8C, in the desired information display interface 70, each item of desired information can receive a long press operation and jump out of the operation menu 100 in response to the long press operation. The operation menu 100 may be provided with a "share" key and a "not share" key. The user may indicate that the corresponding desired information is shared by clicking a "share" button, or may indicate that the corresponding desired information is not shared by clicking a "not share" button. And finally, indicating one or more items of required information to be shared by the user, namely the required information to be shared.
It should be noted that the examples are only some implementation manners provided by the embodiment of the present invention, and the user operation authorized by the user may also include other user operations, such as a voice operation for authorization, a motion sensing operation, and the like, which is not limited herein.
In some optional embodiments, the user authorization may also be obtained by the first party in advance. For example, when a user terminal (the first party) installs a client provided by a hotline service provider (the second party), the client may ask the user to authorize a relevant operation (e.g., an operation of reading operating system configuration information, etc.) involved in the client. The example is only one implementation manner of the embodiment of the present invention, and may also be different in practical applications, and should not be construed as a limitation.
In the embodiment of the present invention, when the first party sends the required information corresponding to the target service to the second party, the first party may send the required information corresponding to the target service to the second party through one or more of TCP/IP data connection, UDP/IP data connection, SMS, or MMS. In practical applications, other data transmission modes, such as a point-to-point transmission mode, may also be used between the first party and the second party to transmit the required information corresponding to the target service, which is not limited herein.
S111, after receiving the required information to be shared sent by the first party, the second party may provide the required information to be shared to a hotline agent, so that the hotline agent can perform further processing according to the required information to be shared, for example, analyzing a failure cause, providing a solution, and the like.
Specifically, the management server of the hotline service provider receives the required information corresponding to the target service sent by the first calling party (user terminal), and pushes the required information corresponding to the target service to the hotline seat terminal providing the service of the target service for the first calling party. Finally, the hotline seat terminal can display the required information corresponding to the target service on a screen of the hotline seat terminal, so that an operator can provide the service related to the target service for the first calling party conveniently.
Next, referring to fig. 9, fig. 9 is a schematic diagram of a non-hotline phone scenario to which the present application relates. In the non-hotline telephone scenario shown in fig. 9, the user terminal 1 and the user terminal 2 may communicate by telephone, sms, internet, etc. The method for sharing information during call provided by the embodiment of the invention in the non-hotline telephone scenario is described in detail below with reference to fig. 10. In the embodiment of fig. 10, a calling party (hereinafter referred to as a second calling party) defines a plurality of required information options for different contacts in advance, and the required information options are used for indicating which required information the calling party needs to obtain from different contacts respectively. Thus, when the calling party and a contact are calling, the calling party can request the contact to share information according to the required information options aiming at the contact. The contact with which the party is talking may be referred to as the first party below. As shown in fig. 10, the method may include:
s201, the second calling party predefines required information options aiming at different contacts.
For example, assume that for 3 different contacts: the second calling party defines required information options for the 3 contacts in advance respectively, wherein the required information options for the contact A are address lists, the required information options for the contact B are albums and call records, and the required information options for the contact C are chat records of mails, short messages and instant messaging software. Then, these predefined desired information options may indicate: the second calling party needs to acquire an address book of the contact A, the second calling party needs to acquire an album and a call record of the contact B, and the second calling party needs to acquire an email, a short message and a chat record of instant messaging software of the contact C.
In some alternative embodiments, the different contacts may refer to different groups of contacts. That is, the second party may group contacts and define different desired information options for different groups of contacts.
For example, assume that the second party has set up 2 contact groups: group a and group B, wherein the predefined required information options for group a are: and the address book, and the predefined required information options for the group B are photo album and call records. The number of members included in each of the groups a and B is not limited. The predefined required information options for group a, group B, respectively, may then indicate: the second calling party can request the members of the group A to share the address book when the second calling party communicates with the members of the group A, and the second calling party can request the members of the group B to share the photo book and the call record when the second calling party communicates with the members of the group B. The example is only one implementation manner of the embodiment of the present invention, and may also be different in practical applications, and should not be construed as a limitation.
Optionally, the second party may be grouped according to the degree of closeness between the second party and each contact, for example, a family group, a friend group, and a co-worker group. Generally, the desired information option corresponding to the contact group with higher intimacy degree may be a more private information option. For example, the required information options for the family group may be email, sms, chat records of instant messaging software, and more private user information. The example is only one implementation manner of the embodiment of the present invention, and may also be different in practical applications, and should not be construed as a limitation.
Optionally, the second party may also be grouped according to a transaction cooperation type between the second party and each contact, for example, a product group, a quality group, and a research and development group. For example, the required information option for the product group may be a chat record corresponding to the product group in the instant messaging software, the required information option for the quality group may be a chat record corresponding to the quality group in the instant messaging software, and the required information option for the development group may be a chat record corresponding to the development group in the instant messaging software. The example is only one implementation manner of the embodiment of the present invention, and may also be different in practical applications, and should not be construed as a limitation.
It should be noted that, the method is not limited to the manner of defining the required information options in advance described above, and in practical applications, the second party may also define the required information options for different contacts in other manners. For example, all the required information options corresponding to all the contacts are defined in a unified manner as address lists. The examples are intended to illustrate embodiments of the invention and should not be construed as limiting.
S202, the second calling party sends the required information option aiming at the first calling party to the first calling party. In one implementation, the second party may send the required information option to the first party when establishing a communication with the first party. For example, when the second caller adds the first caller to a contact group "colleague group" in the phonebook for the first time, a predefined required information option for "colleague group" is sent to the first caller.
In another implementation, the second party may trigger sending of the desired information option to the first party by the second party user when the first party user and the second party user are facing, which may prompt the first party to receive the desired information option in person.
The method for sending the required information option to the first party by the second party may be implemented by the first party, and the method is not limited to the above two implementations.
Optionally, the second party may also upload the predefined required information option for the first party to a server, and then send the server address to the first party. In this way, the first party can download the predefined desired information options from the server according to the server address.
S203, the first calling party receives the required information option aiming at the first calling party and sent by the second calling party, and caches the required information option aiming at the first calling party.
Specifically, reference may be made to step S103 in the embodiment of fig. 1, which is not described herein again.
And S204, establishing communication connection between the second communication and the first communication party.
Here, the call connection may be triggered and established by the first party calling the second party, may also be triggered and established by the second party calling the first party, and may also be a group call initiated by a third party, which is not limited herein.
S205, when communicating with the first party, the second party sends a sharing request to the first party. The sharing request may be used to request to acquire the required information that the second party needs to acquire from the first party, that is, information corresponding to the predefined required information option for the first party.
In particular, the sharing request may be actively triggered by the second talker. The sharing request may also be triggered automatically, for example, 10 seconds after the call starts, and the second party automatically sends the sharing request to the first party. The embodiment of the present invention does not limit the initiation manner of the sharing request.
Optionally, the sharing request may carry an identity of the second party. Therefore, in a multi-person communication scene, the first communication party can judge that the communication party requesting information sharing is the second communication party according to the identity, and therefore information sharing is performed on the second communication party.
Optionally, the sharing request may not carry the identity of the second party. In a two-party communication scenario between the first party and the second party, the first party may determine that the sharing request is initiated by the second party according to an incoming call number or an outgoing call number.
S206, after the first calling party receives the sharing request, the authority of the second calling party is verified. If the authority verification is passed, step S207 is performed. Specifically, the sharing request may include identification information of the second party, for example, a phone number of the second party, for indicating the second party.
Specifically, the first party may set different permission requirements for different user information, and only the contact meeting the corresponding permission requirements may request to acquire the corresponding user information. Table 1 exemplarily shows the authority requirements set by the first party for user information.
TABLE 1
As can be seen from table 1, at the first party side, the permission requirements corresponding to the user information with different privacy degrees may be different. For example, the right requirement corresponding to the address book is: and the contact person in the address list, namely the contact person in the address list of the first calling party can request to obtain the address list of the first calling party. For another example, the authority requirements corresponding to the call records are: and the family group in the address book, namely only the family group contact in the address book of the first calling party can request to obtain the call record of the first calling party. It can be understood that, because the call record is more private than the address book, the permission requirement corresponding to the call record is stricter than that corresponding to the address book.
As can be seen from table 1, the authority requirements corresponding to different types of user information may be different at the first party side. For example, the right requirements corresponding to the chat records of the product group in the chat software are: and the product group in the address book, namely, only the product group contact person in the address book of the first calling party can request to obtain the chat record of the product group in the chat software of the first calling party. For another example, the permission requirements corresponding to the chat records of the quality group in the chat software are as follows: and requesting to obtain the chat records of the quality group in the chat software of the first calling party only by the quality group contact person in the address list of the first calling party.
It should be noted that the above-mentioned examples are only for explaining the embodiments of the present invention, and should not be construed as limiting.
Specifically, after receiving the sharing request, the first party may first determine, according to a required information option predefined by the second party and specific to the first party, an authority requirement corresponding to the required information that the second party needs to request to acquire. And then, the first calling party judges whether the second calling party meets the authority requirement, and if so, the second calling party is determined to pass the authority authentication.
For example, taking table 1 as an example, the required information options predefined by the second party for the first party are call records and short messages, that is, the required information that the second party needs to request to acquire is the call records and short messages of the first party. As can be seen from table 1, the permission requirements corresponding to the call records and the short messages are as follows: the family group in the address book. Aiming at the sharing request from the second calling party, the first calling party can judge whether the second calling party is a family group contact in an address book of the first calling party, if so, the second calling party is judged to meet the authority requirements corresponding to the call records and the short messages, otherwise, the second calling party is judged not to meet the authority requirements corresponding to the call records and the short messages. The examples are intended to illustrate embodiments of the invention and should not be construed as limiting.
Specifically, the second party may send the sharing request through a data channel or a voice channel. For the description of the data channel or the voice channel, reference is made to the foregoing description, and the description is omitted here.
And S207, if the authority verification of the second calling party passes, the first calling party can acquire the required information according to the required information option.
In one implementation, if the information corresponding to the required information option includes the required information maintained by the first party, the first party may directly acquire the required information maintained by the first party through a system interface.
In another implementation manner, if the information corresponding to the required information option includes required information maintained by a third party, the first calling party needs to implement an API provided by the third party, and requests the third party to acquire the required information maintained by the third party by calling the API of the third party. It should be noted that the third party is not limited to the third party application, and may also be a third party service, a third party platform, and the like.
Regarding the above two implementation manners, reference may be specifically made to step S107 in the embodiment in fig. 1, and details are not described here.
It should be noted that, in the specific implementation, the required information corresponding to the target service may include the two situations: the required information maintained by the first party and the required information maintained by the third party.
S208-S210, after obtaining the required information, the first party may send the required information to the second party according to user authorization. Here, the first party may send all or part of the acquired required information to the second party. Accordingly, the second party can receive the required information sent by the first party.
Specifically, the first calling party may display the acquired required information, and then determine the required information to be shared from the acquired required information according to user authorization. Here, the user authorization may be used to select the required information to be shared, and authorize the sharing of the required information to be shared to the second party.
Specifically, the user operation corresponding to the user authorization may have various forms, such as a selection operation, a deletion operation, and the like. For how to display the acquired required information and how to implement the user authorization, reference may be made to S108-S109 in the embodiment of fig. 1, which is not described herein again.
Specifically, the first party may send the required information to be shared to the second party through one or more of a TCP/IP data connection, a UDP/IP data connection, an SMS, or an MMS. In practical applications, the first party may also send the required information to be shared to the second party by using other data transmission methods, for example, a point-to-point transmission method, which is not limited herein.
Optionally, when the first party sends the required information to the second party through data connection such as TCP/IP, UDP/IP, etc., the method described in the embodiment of fig. 10 may be implemented as a client program and a server program. The client programs are installed on the first calling party side and the second calling party side and can be used for realizing the functions described in the steps. The client program may also be configured to send the received information, such as the required information, to a preset server. The preset server is configured with the server-side program, and can be used for caching the required information sent by the first calling party, and sending the required information to the second calling party when the second calling party is connected to the network. Here, the first or second party may be connected to the network through a Wi-Fi connection or a mobile data connection.
It is understood that when the first party sends the required information to the second party by SMS or MMS, the required information sent to the second party may be cached on a server of a short message service center SMSC, and when the second party is registered in a mobile operator network, the short message service center sends the cached required information to the second party.
In order to facilitate implementation of the embodiments of the present invention, the following describes related apparatuses provided in the embodiments of the present invention.
Referring to fig. 11, fig. 11 is a schematic diagram of a hardware architecture of a server according to an embodiment of the present invention. The server 200 may be the second calling party in the embodiment of fig. 3, that is, the server of the hotline service provider, for example, the management server 101 in the hotline telephone service system 100 shown in fig. 1.
As shown in fig. 11, the server 200 may include: a processor 201, a memory 203 (one or more computer-readable storage media), a communication module 205. These components may communicate over one or more communication buses 204. Specifically, the server 200 may be integrated with or connected to a CTI device, an Interactive Voice Response (IVR) device, a switch, an Automatic Call Distribution (ACD) device, and the like. In the embodiment of fig. 11, the server 200 is connected to the CTI device, the IVR device, the ACD device, and the like as an example. Wherein:
the communication module 205 may be used to receive and transmit signals, primarily integrating the receiver and transmitter of the server 200. In a specific implementation, the communication module 205 may include an ethernet communication module, a PSTN communication module, and a short message communication module. Wherein the Ethernet communication module can be used for communicating with other communication devices through the Internet. The PSTN communication module can be used for connecting a fixed telephone network and communicating with other communication equipment through the fixed telephone network. The Short Message communication module can be used for connecting a Short Message Service Center (Short Message Service Center) and sending Short messages to other equipment or receiving Short messages sent by other equipment. In some embodiments, the communication module 205 may be implemented on a separate chip.
The processor 201 may be integrated to include: one or more CPUs, a clock module, and a power management module. The clock module is mainly used for generating clocks required by data transmission and timing control for the processor 201. The power management module is mainly used to provide stable and high-precision voltage for the processor 201, the communication module 205, and the like.
A memory 203 is coupled to the processor 201 for storing various software programs and/or sets of instructions. In particular implementations, memory 203 may include high speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory 203 may store an operating system, such as an embedded operating system like ANDROID, IOS, WINDOWS, or LINUX. The memory 203 may also store communication programs that may be used to communicate with one or more communication devices, such as terminal devices.
In the hotline phone service system, the server 200 may be responsible for implementing functions such as system operation state management, authority management, seat management, data management and statistics, and system security maintenance. In a specific implementation, the server 200 may support running a service management system, a customer management system, an agent management system, and the like. The service management system is responsible for various service management, including: defining and creating services, adding new services, counting service use conditions and the like. The customer management system is responsible for collecting and maintaining relevant data of customers, including displaying customer information and the like on the agent terminal. The seat management system is responsible for managing the seat personnel, including seat registration, seat authority management and the like.
It should be noted that fig. 11 is only one implementation manner of the embodiment of the present invention, and in practical applications, the server 200 may further include more or less components, which is not limited herein.
Referring to fig. 12, fig. 12 is a schematic diagram of a hardware architecture of a terminal according to an embodiment of the present invention. The terminal 300 may be used as the first party, i.e. the user terminal in the embodiment of fig. 3. The terminal 300 may also be used as the first party in the embodiment of fig. 10, and may also be used as the second party in the embodiment of fig. 10.
As shown in fig. 12, the terminal 300 may include: a processor 301, a memory 302 (one or more computer-readable storage media), a communication module 303, an input-output system 304. These components may communicate over one or more communication buses 104.
The communication module 303 is used for receiving and transmitting signals, and mainly integrates a receiver and a transmitter of the terminal 300. In a specific implementation, the communication module 303 may include, but is not limited to: a Wi-Fi module 3031, a telecommunications module 3033, and a wired telephone communication module 3035. The Wi-Fi module 3031 can be used for accessing the Internet. The telecommunication module 3033 may be a GSM (2G) module, a WCDMA (3G) module or an LTE (4G) module, and may be used to establish a call connection with other devices through a telecommunication carrier network, and may also be used to access the internet through the telecommunication carrier network. The wired telephone communication module 3035 implements a wired telephone communication protocol that can be used to establish a call connection with other devices via a fixed telephone network. It should be noted that, not limited to the illustration in fig. 12, the communication module 303 may also include a bluetooth module or the like. In some embodiments, the communication module 303 may be implemented on a separate chip.
The input/output system 304 is mainly used for implementing an interactive function between the terminal 300 and a user/external environment, and mainly includes input/output devices of the terminal 300. In a specific implementation, the input/output system 304 may include a touch screen controller 3041, a camera controller 3043, an audio controller 3043, and a sensor controller 3047. Each controller may be coupled to a corresponding peripheral device (the touch screen 3051, the camera 3053, the audio circuit 3055, and the motion sensor 3057. in a specific implementation, the motion sensor 3057 may include an accelerometer, a gyroscope, a magnetometer, and the like, and is configured to monitor a motion state of a user and collect motion data of the user, such as a motion step number, a motion step frequency, and the like.
The processor 301 may be integrated to include: one or more CPUs, a clock module, and a power management module. The clock module is mainly used for generating clocks required by data transmission and timing control for the processor 301. The power management module is mainly used for providing stable and high-precision voltage for the processor 301, the communication module 303, the input/output system 304 and the like.
A memory 302 is coupled to the processor 301 for storing various software programs and/or sets of instructions. In particular implementations, memory 302 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 302 may store an operating system, such as an embedded operating system like ANDROID, IOS, WINDOWS, or LINUX. The memory 302 may also store network communication programs that may be used to communicate with one or more communication devices, such as the server 200 shown in fig. 11 or other terminal devices. The memory 302 may also store a user interface program, which may be used to vividly display the contents of the application program through a graphical operation interface, such as the user interfaces in fig. 6A-6C or fig. 8A-8C, and receive the control operation of the application program from the user through input controls such as menus, dialog boxes, and buttons.
In this embodiment of the present invention, the memory 302 may be configured to store a program for implementing the related functions of the first party in the embodiment of fig. 3, and the processor 301 may be configured to call the program code stored in the memory 302 to execute the related functions of the first party in the embodiment of fig. 3. At this time, the terminal 300 is implemented as the first party described in the embodiment of fig. 3.
In this embodiment of the present invention, the memory 302 may also be configured to store an implementation program of the related function of the first party in the embodiment shown in fig. 10, and the processor 301 may be configured to call the program code stored in the memory 302 to execute the related function of the first party in the embodiment shown in fig. 10. At this time, the terminal 300 is implemented as the first party described in the embodiment of fig. 10.
In this embodiment of the present invention, the memory 302 may be further configured to store an implementation program of the related function of the second party in the embodiment in fig. 10, and the processor 301 may be configured to call the program code stored in the memory 302 to execute the related function of the second party in the embodiment in fig. 10. At this time, the terminal 300 is implemented as the second party described in the embodiment of fig. 10.
It should be noted that fig. 12 is only one implementation manner of the embodiment of the present invention, and in practical applications, the terminal 300 may further include more or less components, which is not limited herein.
Based on the server 200 described in the embodiment of fig. 11 and the terminal 300 described in the embodiment of fig. 12, the following describes in detail the cooperation relationship between each component in the first party and each component in the second party in a hotline phone scenario (which may be shown in fig. 1), please refer to fig. 13. The server 200 defines the required information options corresponding to each service in advance, and the terminal 300 may periodically download the required information options corresponding to each service, which may specifically refer to the embodiment in fig. 3. The embodiment of fig. 13 is described below.
1-2. the touch screen of the terminal 300 detects a user's operation of dialing a hotline number, generates a dialing event, and transmits the dialing event to the processor of the terminal 300. Specifically, the dialing event may carry a hot-line number entered by the user to indicate the call destination.
3. The processor of the terminal 300 processes the dialing event reported by the touch screen, and instructs the communication module to call the hotline telephone facilitator represented by the hotline number. The communication module of the terminal 300 calls the server 200 in response to the instruction issued by the processor. The server 200, i.e. the server of the hotline facilitator for said hotline number, may be used to handle incoming calls.
4-5. the communication module of the server 200 detects an incoming call, generates an incoming call event, and reports the incoming call event to the processor of the server 200.
6. The processor of the server 200 processes the incoming call event reported by the communication module, and instructs the communication module to send a voice prompt to the terminal 300. Here, the voice prompt is used to prompt the user to select a target service from a plurality of services provided by the hotline service provider. In particular, the processor may instruct the IVR system to send the voice prompt to the terminal 300 via the communication module. For an example of the voice prompt, please refer to the embodiment of fig. 3, which is not described herein again.
7. The communication module of the server 200 responds to the instruction issued by the processor, and sends the voice prompt to the terminal 300 to prompt the user of the terminal 300 to select the target service.
8-10. the communication module of the terminal 300 detects the voice prompt sent by the server 200 and transmits the voice prompt to the processor of the terminal 300. The processor issues an audio play instruction to the audio circuit of the terminal 300, instructing the audio module to play the voice prompt. The audio circuit of the terminal 300 plays the voice prompt to prompt the user to select the target service.
11. The user of the terminal 300 presses the dial key corresponding to the target service on the virtual dial displayed on the touch screen according to the voice prompt played by the audio circuit.
12-14. the touch screen of the terminal 300 detects a key event on the dial and transmits the dial key information corresponding to the target service to the processor of the terminal 300. The processor processes the key event, and instructs the communication module to send the DTMF signal of the key corresponding to the target service to the server 200 in the voice channel. The communication module of the terminal 300 responds to the instruction issued by the processor and sends the DTMF signal to the server 200 in the voice channel.
15-16. the communication module of the server 200 detects the DTMF signal from the terminal 300 in the voice channel and transmits the DTMF signal to the processor. And the processor analyzes the key represented by the DTMF signal according to the DTMF signal and then determines the target service selected by the first calling party according to the key.
17-18. after determining the target service selected by the user of the terminal 300, the processor of the server 200 instructs the communication module to send a sharing request to the terminal 300, where the sharing request is used to request to obtain the required information corresponding to the target service. The communication module of the server 200 responds to the instruction issued by the processor and sends the sharing request to the terminal 300.
19-20. the communication module of the terminal 300 detects the sharing request from the server 200 and transmits the sharing request to the processor of the terminal 300. And the processor responds to the sharing request, determines a predefined required information option corresponding to the target service, and then acquires the required information corresponding to the target service according to the required information option corresponding to the target service. Please refer to the embodiment of fig. 3 for details, which are not repeated herein.
21-22, after acquiring the required information corresponding to the target service, the processor of the terminal 300 may instruct the touch screen to display the required information corresponding to the target service. The touch screen of the terminal 300 responds to the instruction issued by the processor and displays the required information corresponding to the target service. For specific implementation of displaying the required information corresponding to the target service, reference may be made to the embodiment in fig. 3, which is not described herein again.
23. The user of the terminal 300 selects desired information to be shared from among the desired information displayed on the touch screen. The authorization operation may be a variety of different user operations, and reference may be made to the embodiment in fig. 3 specifically, which is not described herein again.
24-27, the touch screen of the terminal 300 detects the authorization operation input by the user and reports the user authorization event to the processor. The processor of the terminal 300 processes the user authorization event, determines required information to be shared from the required information displayed on the touch screen according to the authorization operation, and instructs the communication module to transmit the required information to be shared to the server 200. The communication module of the terminal 300 responds to the instruction issued by the processor and sends the required information to be shared to the server 200.
28-29. the communication module of the server 200 detects the required information to be shared sent by the terminal 300 and transmits the required information to be shared to the processor of the server 200. The processor of the server 200 may send the required information to be shared to the agent, so that the agent can provide further professional services to the user of the terminal 300 according to the information to be shared.
It should be noted that fig. 13 only illustrates one embodiment of the present application from inside of the device, and details are not described here regarding the adaptable adjustment process of other embodiments of the present application.
Based on the terminal 300 described in the embodiment of fig. 12, the following describes in detail the cooperation relationship between each component in the first party and each component in the second party in a non-hotline telephone scenario (which may be shown in fig. 9), please refer to fig. 14. Wherein, terminal A is the first party (including touch screen A, processor A and communication module A), and terminal B is the second party (including touch screen B, processor B and communication module B). Both terminal a and terminal B may be implemented as the terminal 300 shown in fig. 12. The second party defines the required information options for different contacts in advance, and sends the required information options for the first party to the first party, which may refer to the embodiment in fig. 10. The embodiment of fig. 14 is described below.
1-2, the touch screen of the terminal A detects the operation of dialing the telephone number of the first calling party by the user, generates a dialing event and transmits the dialing event to the processor of the terminal A. Specifically, the dialing event may carry a telephone number of the first party input by the user, and is used to indicate a calling object.
3. And the processor of the terminal A processes the dialing event reported by the touch screen and instructs the communication module of the terminal A to call the terminal B. The communication module of terminal a calls terminal B in response to the instruction. Terminal B, the first party, may be used to handle the incoming call.
4-7. the communication module of terminal B detects an incoming call, generates an incoming call event, and reports the incoming call event to the processor of terminal B. And the processor of the terminal B processes the incoming call event reported by the communication module and instructs the touch screen to display the incoming call. And the touch screen of the terminal B responds to the instruction and displays the incoming call interface. Specifically, the incoming call interface may display an incoming call number, that is, a telephone number of the second party.
8-10, the user answers the incoming call. And the terminal B detects the telephone answering operation input by the user, generates a user answering event and reports the answering event to the processor. The processor of terminal B processes the answer event and instructs the communication module to return a connect response to terminal a. The communication module of the terminal B responds to the instruction and returns a connection response to the terminal A.
11-14. the communication module of the terminal A detects the connection response returned by the terminal B and reports the connection response to the processor. And the processor of the terminal A responds to the connection response reported by the communication module and instructs the communication module to send a sharing request to the terminal B so as to request to obtain the required information which needs to be obtained from the first calling party by the second calling party. And the communication module of the terminal A responds to the instruction sent by the processor and sends the sharing request to the terminal B.
15-16, the communication module of the terminal B detects the sharing request sent by the terminal a, and reports the sharing request to the processor, the processor of the terminal B responds to the sharing request, performs permission verification on the second calling party, and sends the required information required to be acquired by the terminal a to the terminal a if the permission verification is passed. Specifically, the sharing request may include identification information of the second party, for example, a phone number of the second party.
17. If the authority verification for the second calling party passes, the processor of the terminal B may obtain the required information that the second calling party needs to obtain according to the required information option predefined by the second calling party for the first calling party. For how to obtain the required information, please refer to the embodiment of fig. 10, which is not described herein.
18-19, after acquiring the required information required by the second calling party, the processor of terminal B may instruct the touch screen to display the acquired required information. And the touch screen of the terminal B responds to the instruction issued by the processor and displays the acquired required information. For specific implementation of displaying the acquired required information, reference may be made to the embodiment in fig. 10, which is not described herein again.
20. The user of the terminal 300 selects desired information to be shared from among the desired information displayed on the touch screen. The authorization operation may be a variety of different user operations, and reference may be made to the embodiment in fig. 10 specifically, which is not described herein again.
21-23, the touch screen of the terminal B detects the authorization operation input by the user and reports the user authorization event to the processor. And the processor of the terminal B processes the user authorization event, determines the required information to be shared from the required information displayed on the touch screen according to the authorization operation, and instructs the communication module to send the required information to be shared to the terminal A. And the communication module of the terminal B responds to the instruction sent by the processor and sends the required information to be shared to the terminal A. Please refer to the embodiment of fig. 10 for how to determine the required information to be shared according to the authorization operation, which is not described herein again.
The communication module of the 24-35 server 200 detects the required information to be shared transmitted by the terminal 300 and transmits the required information to be shared to the processor of the server 200. The processor of the server 200 may send the required information to be shared to the agent, so that the agent can provide further professional services to the user of the terminal 300 according to the information to be shared.
It should be noted that fig. 14 only illustrates one embodiment of the present application from inside of the device, and details are not described here regarding the adaptable adjustment process of other embodiments of the present application.
Referring to fig. 15, fig. 15 is a schematic structural diagram of a terminal according to an embodiment of the present invention. The terminal 400 may be the first party in the embodiment of fig. 3 (hotlining scenario) or may be the first party in the embodiment of fig. 10 (non-hotlining scenario). As shown in fig. 15, the terminal 400 may include: a call unit 401, a reception unit 403, an acquisition unit 405, and a transmission unit 407. Wherein:
a call unit 401, configured to establish a call connection with a second party;
a receiving unit 403, configured to receive a sharing request sent by the second talker, where the sharing request is used to request to acquire information corresponding to a predefined required information option;
an obtaining unit 405, configured to obtain information corresponding to the required information option;
a sending unit 407, configured to send the acquired required information to the second talker.
As can be seen with reference to the foregoing method embodiments, the second party may be configured to define the desired information option. The required information option is used for representing information which the second calling party needs to obtain from the first calling party.
Specifically, when the terminal 400 is implemented as the first party in the embodiment of fig. 3, the specific implementation of each functional unit included in the terminal 400 may be as follows:
a receiving unit 403, configured to receive a sharing request sent by the second party, where the sharing request is used to request to obtain required information corresponding to the target service selected by the first party. Referring to the embodiment of fig. 3, the second communication party may be configured to pre-define the required information options corresponding to the services.
The obtaining unit 405 may be configured to obtain the required information corresponding to the target service according to the required information option corresponding to the target service.
A sending unit 407, configured to send required information corresponding to the target service to the second talker.
It should be noted that, when the terminal 400 is implemented as the first party in the embodiment of fig. 3, specific implementation of each functional unit included in the terminal 400 may refer to the embodiment of fig. 3, and for brevity of description, no further description is given here.
Specifically, when the terminal 400 is implemented as the first party in the embodiment of fig. 10, the specific implementation of each functional unit included in the terminal 400 may be as follows:
a receiving unit 403, configured to receive a sharing request sent by the second party, where the sharing request is used to request to acquire information corresponding to a predefined required information option for the first party, that is, required information that the second party needs to acquire from the first party. As can be seen with reference to the embodiment of fig. 10, the second party is configured to pre-define the desired information options for different contacts.
An obtaining unit 405, configured to obtain, according to a predefined required information option for the first party, required information that the second party needs to obtain from the first party. As can be appreciated with reference to the fig. 10 embodiment, the second party may be used to predefine the desired information options for the different contacts.
A sending unit 407, configured to send the acquired required information to the second talker.
It should be noted that, when the terminal 400 is implemented as the first party in the embodiment of fig. 10, specific implementation of each functional unit included in the terminal 400 may refer to the embodiment of fig. 10, and for brevity of description, no repeated description is provided here.
Referring to fig. 16, fig. 16 is a schematic structural diagram of another terminal according to an embodiment of the present invention. Terminal 500 may be the second party in the embodiment of fig. 3 (hotline scenario) or may be the second party in the embodiment of fig. 10 (non-hotline scenario). As shown in fig. 16, the terminal 500 may include: a call unit 501, a sending unit 503 and a receiving unit 505, wherein:
a call unit 501, configured to establish a call connection with the first party;
a sending unit 503, configured to send a sharing request to the first party, where the sharing request is used to request to obtain information corresponding to a predefined required information option;
the receiving unit 505 may be configured to receive information corresponding to the required information option sent by the first party.
As can be seen from the foregoing method embodiments, the terminal 500 may be configured to define the required information option, where the required information option is used to characterize information that the second party needs to obtain from the first party.
Specifically, when the terminal 500 is implemented as the second party in the embodiment of fig. 3, the specific implementation of each functional unit included in the terminal 500 may be as follows:
a sending unit 503, configured to send a sharing request to the first party, where the sharing request is used to request to obtain required information corresponding to the target service selected by the first party.
A receiving unit 505, configured to receive required information corresponding to the target service sent by the first party. The required information corresponding to the target service is acquired by the first calling party according to the required information option corresponding to the target service.
Referring to the embodiment of fig. 3, when the terminal 500 is implemented as the second party in the embodiment of fig. 3, the terminal 500 may be used to pre-define the required information options corresponding to the services.
It should be noted that, when the terminal 500 is implemented as the second party in the embodiment of fig. 3, specific implementation of each functional unit included in the terminal 500 may refer to the embodiment of fig. 3, and for brevity of the description, no repeated description is given here.
Specifically, when the terminal 500 is implemented as the second party in the embodiment of fig. 10, the specific implementation of each functional unit included in the terminal 500 may be as follows:
a sending unit 503, configured to send a sharing request to the first party, where the sharing request is used to request to obtain information corresponding to a predefined required information option for the first party, that is, required information that the second party needs to obtain from the first party.
The receiving unit 505 may be configured to receive the required information sent by the first party, that is, information corresponding to a required information option for the first party.
As can be seen with reference to the fig. 3 embodiment, when the terminal 500 is implemented as the second party in the fig. 10 embodiment, the terminal 500 may be used to pre-define the required information options for different contacts.
It should be noted that, when the terminal 500 is implemented as the second party in the embodiment of fig. 10, specific implementation of each functional unit included in the terminal 500 may refer to the embodiment of fig. 10, and for brevity of the description, no repeated description is given here.
In addition, the embodiment of the invention also provides a communication system which comprises a first calling party and a second calling party.
In particular, the communication system may be a communication system in a hotline phone field as shown in fig. 1. In this case, the first party may be the server 200 shown in fig. 11, and the second party may be the terminal 300 shown in fig. 12, wherein the memory of the terminal 300 may be used to store the implementation program of the second party in the embodiment of fig. 3. The first and second parties may also be the first and second parties respectively described in the embodiment of fig. 3. Optionally, the first party may also be the terminal 400 shown in the embodiment of fig. 15, and the second party may also be the terminal 500 shown in the embodiment of fig. 16.
In particular, the communication system may be a communication system in a non-hotline phone arena as shown in fig. 9. At this time, the first party may be the terminal 300 shown in fig. 12, wherein the memory of the terminal 300 may be used to store the implementation program of the first party in the embodiment of fig. 10. The second party may be the terminal 300 shown in fig. 12, wherein the memory of the terminal 300 may be used to store the implementation program of the second party in the embodiment of fig. 10. The first and second parties may also be the first and second parties respectively described in the embodiment of fig. 10. Optionally, the first party may also be the terminal 400 shown in the embodiment of fig. 15, and the second party may also be the terminal 500 shown in the embodiment of fig. 16.
In summary, with the embodiments of the present invention, a calling party defines in advance what information needs to be obtained from another calling party. That is, the calling party has predefined the required information options. In a call, the party to the call may request the other party to the call to share the required information. The other party of the call can respond to the request, acquire the required information according to the required information option predefined by the one party of the call, and share the acquired required information to the one party of the call. This improves the efficiency of sharing information during a call.
One of ordinary skill in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the above method embodiments. And the aforementioned storage medium includes: various media capable of storing program codes, such as ROM or RAM, magnetic or optical disks, etc.

Claims (46)

1. A method for sharing information in a call, comprising:
a first calling party obtains a required information option predefined by a second calling party, wherein the required information option is a required information option corresponding to different services or a required information option aiming at the first calling party;
the first calling party and the second calling party establish calling connection;
the first calling party receives a sharing request sent by the second calling party, wherein the sharing request is used for requesting to acquire information corresponding to the predefined required information option; the required information option is used for representing information which the second calling party needs to obtain from the first calling party;
the first calling party acquires information corresponding to the required information option;
and the first calling party sends the information corresponding to the required information option to the second calling party.
2. The method of claim 1, wherein the second party defines a plurality of desired information options for different contacts;
the sharing request is specifically used for requesting to acquire information corresponding to a predefined required information option for the first calling party;
the first calling party acquires information corresponding to the required information option, and the information includes: and the first calling party acquires the information which the second calling party needs to acquire from the first calling party according to the predefined information option required by the first calling party.
3. The method of claim 2, wherein the plurality of desired information options for different contacts comprises desired information options for a plurality of different contact groups.
4. The method of claim 2, further comprising: and the first calling party receives the predefined required information options sent by the second calling party and caches the required information options.
5. The method of claim 3, further comprising: and the first calling party receives the predefined required information options sent by the second calling party and caches the required information options.
6. The method of claim 1, wherein the second party predefines the required information options corresponding to each service;
the sharing request is used for requesting to acquire required information corresponding to the target service selected by the first calling party; the target service is selected by the first party from the services;
the first calling party acquires the information which the second calling party needs to acquire from the first calling party according to the required information option, and the method comprises the following steps: and the first calling party acquires the required information corresponding to the target service according to the required information option corresponding to the target service.
7. The method of claim 6, further comprising: and the first calling party downloads the required information options predefined by the second calling party and caches the required information options.
8. The method of claim 6, further comprising: and the first communication party receives a service selection prompt sent by the second communication party, selects the target service according to the service selection prompt and sends the identification information of the target service to the second communication party.
9. The method of claim 7, further comprising: and the first communication party receives a service selection prompt sent by the second communication party, selects the target service according to the service selection prompt and sends the identification information of the target service to the second communication party.
10. The method of claim 7, wherein the first party receiving a service selection prompt sent by the second party, selecting the target service according to the service selection prompt, and sending identification information of the target service to the second party, comprises:
the service selection prompt is a voice prompt; the first calling party receives the voice prompt sent by the second calling party through a voice channel, selects a key for representing the target service according to the voice prompt, and returns a DTMF signal for representing the key for representing the target service to the second calling party through the voice channel;
alternatively, the first and second electrodes may be,
the service selection prompt is a service selection page; and the first calling party receives the service selection page sent by the second calling party through a data channel, selects the service option corresponding to the target service according to the service selection page, and returns the service option corresponding to the target service to the second calling party through the data channel.
11. The method of any one of claims 1-10, further comprising: the first calling party displays information corresponding to the required information option; the first calling party receives user authorization and determines information to be shared from the information corresponding to the required information option according to the user authorization;
the sending, by the first party to the second party, information corresponding to the required information option, including: and the first calling party sends the information to be shared to the second calling party.
12. The method according to any one of claims 1-10, wherein the first party obtaining information corresponding to the required information option comprises at least one of:
if the information corresponding to the required information option comprises the user information maintained by the first calling party, calling a preset system interface to acquire the user information maintained by the first calling party;
and if the information corresponding to the required information option comprises user information maintained by a third party, calling an interface provided by the third party to acquire the user information maintained by the third party.
13. The method of claim 9, wherein the first party obtaining information corresponding to the required information option comprises at least one of:
if the information corresponding to the required information option comprises the user information maintained by the first calling party, calling a preset system interface to acquire the user information maintained by the first calling party;
and if the information corresponding to the required information option comprises user information maintained by a third party, calling an interface provided by the third party to acquire the user information maintained by the third party.
14. The method according to any one of claims 1-10, wherein the sending, by the first party, the information corresponding to the required information option to the second party comprises: and the first calling party sends the information corresponding to the required information option to the second calling party through one or more of TCP/IP data connection, UDP connection, SMS or MMS.
15. The method of claim 11, wherein the sending, by the first party to the second party, the information corresponding to the required information option comprises: and the first calling party sends the information corresponding to the required information option to the second calling party through one or more of TCP/IP data connection, UDP connection, SMS or MMS.
16. The method of claim 12, wherein the sending, by the first party to the second party, the information corresponding to the required information option comprises: and the first calling party sends the information corresponding to the required information option to the second calling party through one or more of TCP/IP data connection, UDP connection, SMS or MMS.
17. A method for sharing information in a call, comprising:
the second calling party predefines the required information options, and the required information options are required information options corresponding to different services or required information options aiming at the first calling party; the predefined desired information option is obtained by the first party;
the second calling party and the first calling party establish calling connection;
the second communication party sends a sharing request to the first communication party, wherein the sharing request is used for requesting to acquire information corresponding to the predefined required information option; the second party defining the desired information option; the required information option is used for representing information which the second calling party needs to obtain from the first calling party;
and the second calling party receives information sent by the first calling party, wherein the information is acquired by the first calling party according to the predefined required information option.
18. The method of claim 17, wherein the second party is configured to predefine a plurality of information options for different contacts;
the sharing request is used for requesting to acquire information corresponding to predefined information options aiming at the first calling party;
the first calling party is used for acquiring the information which the second calling party needs to acquire from the first calling party according to the predefined information option aiming at the first calling party.
19. The method of claim 18, wherein the plurality of desired information options for different contacts comprises desired information options for a plurality of different contact groups.
20. The method of claim 17, wherein the second party is configured to predefine required information options corresponding to respective services;
the sharing request is used for requesting to acquire required information corresponding to the target service selected by the first calling party; the target service is selected by the first party from the services;
the first calling party is used for acquiring the required information corresponding to the target service according to the required information option corresponding to the target service.
21. The method of claim 20, further comprising: the second communication party sends a service selection prompt to the first communication party and receives the identification information of the target service sent by the first communication party; the service selection prompt is used for prompting the first calling party to select the target service.
22. The method of claim 21, wherein the second party sending a service selection alert to the first party and receiving identification information of the target service sent by the first party comprises:
the service selection prompt is a voice prompt; the second calling party sends the voice prompt to the first calling party through a voice channel and receives a DTMF signal which is sent by the first calling party and used for representing a key of the target service through the voice channel;
alternatively, the first and second electrodes may be,
the service selection prompt is a service selection page; and the second calling party sends the service selection page to the first calling party through a data channel and receives a service option corresponding to the target service sent by the first calling party through the data channel.
23. The method of any of claims 17-22, wherein the second party receiving the information sent by the first party comprises: and the second communication party receives the information sent by the first communication party through one or more of TCP/IP data connection, UDP connection, SMS or MMS.
24. A terminal, comprising: communication module, processor, wherein:
the communication module is used for obtaining a required information option predefined by a second calling party, wherein the required information option is a required information option corresponding to different services or a required information option aiming at a first calling party;
the communication module is used for establishing communication connection with a second communication party;
the communication module is further configured to receive a sharing request sent by the second party, where the sharing request is used to request to acquire information corresponding to a predefined required information option; the second party defining the desired information option; the required information option is used for representing information which needs to be acquired from the terminal by the second calling party;
the processor is used for acquiring information corresponding to the required information option;
the communication module is further configured to send information corresponding to the required information option to the second party.
25. The terminal of claim 24, wherein the second party defines a plurality of desired information options for different contacts; the sharing request is specifically used for requesting to acquire information corresponding to a predefined required information option for the first calling party;
the processor is specifically configured to obtain information that the second party needs to obtain from the first party according to a predefined required information option for the first party.
26. The terminal of claim 25, wherein the plurality of desired information options for different contacts comprises desired information options for a plurality of different contact groups.
27. The terminal of claim 25, wherein the communication module is further configured to receive the predefined information needed option sent by the second party and buffer the information needed option.
28. The terminal of claim 26, wherein the communication module is further configured to receive the predefined information needed option sent by the second party and buffer the information needed option.
29. The terminal of claim 24, wherein the second party predefines required information options corresponding to respective services; the sharing request is used for requesting to acquire required information corresponding to the target service selected by the first calling party; the target service is selected by the first party from the services;
the processor is specifically configured to obtain the required information corresponding to the target service according to the required information option corresponding to the target service.
30. The terminal of claim 29, wherein the communication module is further configured to download the desired information option predefined by the second party and cache the desired information option.
31. The terminal of claim 29, wherein the communication module is further configured to receive a service selection prompt sent by the second party, the service selection prompt being used to prompt a user to select the target service; the communication module is further configured to send the identification information of the target service to the second talker.
32. The terminal of claim 30, wherein the communication module is further configured to receive a service selection prompt sent by the second party, the service selection prompt being used to prompt a user to select the target service; the communication module is further configured to send the identification information of the target service to the second talker.
33. The terminal of claim 31, wherein if the service selection prompt is a voice prompt, the communication module is specifically configured to receive the voice prompt sent by the second party through a voice channel, select a key representing the target service according to the voice prompt, and return a DTMF signal of the key representing the target service to the second party through the voice channel; alternatively, the first and second electrodes may be,
if the service selection prompt is a service selection page, the communication module is specifically configured to receive the service selection page sent by the second calling party through a data channel, select a service option corresponding to the target service according to the service selection page, and return the service option corresponding to the target service to the second calling party through the data channel.
34. The terminal of any one of claims 24-33, further comprising: a touch screen, wherein:
the touch screen is used for displaying the information corresponding to the required information option;
the touch screen is also used for receiving user authorization;
the processor is used for determining information to be shared from the information corresponding to the required information option according to the user authorization;
the communication module is specifically configured to send the information to be shared to the second talker.
35. The terminal of any one of claims 24-33, wherein the processor is further configured to: if the information corresponding to the required information option comprises the user information maintained by the first calling party, calling a preset system interface to acquire the user information maintained by the first calling party; and if the information corresponding to the required information option comprises user information maintained by a third party, calling an interface provided by the third party to acquire the user information maintained by the third party.
36. The terminal of claim 34, wherein the processor is further configured to: if the information corresponding to the required information option comprises the user information maintained by the first calling party, calling a preset system interface to acquire the user information maintained by the first calling party; and if the information corresponding to the required information option comprises user information maintained by a third party, calling an interface provided by the third party to acquire the user information maintained by the third party.
37. The terminal according to any of claims 24-33, wherein the communication module is specifically configured to send the information corresponding to the required information option to the second party over one or more of a TCP/IP data connection, a UDP connection, an SMS or an MMS.
38. The terminal of claim 34, wherein the communication module is specifically configured to send the information corresponding to the desired information option to the second party over one or more of a TCP/IP data connection, a UDP connection, an SMS, or an MMS.
39. The terminal of claim 35, wherein the communication module is specifically configured to send the information corresponding to the required information option to the second party over one or more of a TCP/IP data connection, a UDP connection, an SMS, or an MMS.
40. A terminal, comprising: a communication module and a processor, wherein:
the processor is used for predefining required information options; the predefined required information option is used for representing information which needs to be acquired by the terminal from a first calling party; the predefined required information options are required information options corresponding to different services or required information options aiming at the first calling party; the predefined desired information option is obtained by the first party;
the communication module is used for establishing communication connection with the first communication party;
the communication module is further configured to send a sharing request to the first party, where the sharing request is used to request to acquire information corresponding to the predefined required information option;
the communication module is further configured to receive information sent by the first party, where the information is obtained by the first party according to the predefined required information option.
41. The terminal of claim 40, wherein the processor is specific to predefine a plurality of information options for different contacts; the sharing request is used for requesting to acquire information corresponding to predefined information options aiming at the first calling party;
the first calling party is used for acquiring information which needs to be acquired by a second calling party from the first calling party according to a predefined information option aiming at the first calling party.
42. The terminal of claim 41, wherein the plurality of desired information options for different contacts comprises desired information options for a plurality of different contact groups.
43. The terminal of claim 40, wherein the processor is specifically configured to predefine required information options corresponding to the services; the sharing request is used for requesting to acquire required information corresponding to the target service selected by the first calling party; the target service is selected by the first party from the services;
the first calling party is used for acquiring the required information corresponding to the target service according to the required information option corresponding to the target service.
44. The terminal of claim 43, wherein the communication module is configured to send a service selection prompt to the first party and receive identification information of the target service sent by the first party; the service selection prompt is used for prompting the first calling party to select the target service.
45. The terminal of claim 44, wherein if the service selection prompt is a voice prompt, the communication module is specifically configured to send the voice prompt to the first party through a voice channel, and receive, through the voice channel, a DTMF signal sent by the first party to characterize the key of the target service; alternatively, the first and second electrodes may be,
if the service selection prompt is a service selection page, the communication module is specifically configured to send the service selection page to the first calling party through a data channel, and receive a service option corresponding to the target service sent by the first calling party through the data channel.
46. The terminal of any of claims 40-45, wherein the communication module is specifically configured to receive the information sent by the first party over one or more of a TCP/IP data connection, a UDP connection, an SMS, or an MMS.
CN201780087933.0A 2017-03-03 2017-03-03 Method and terminal for sharing information in call Active CN110383861B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/075607 WO2018157389A1 (en) 2017-03-03 2017-03-03 Method for sharing information in call, and terminal

Publications (2)

Publication Number Publication Date
CN110383861A CN110383861A (en) 2019-10-25
CN110383861B true CN110383861B (en) 2021-05-18

Family

ID=63369594

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201780087933.0A Active CN110383861B (en) 2017-03-03 2017-03-03 Method and terminal for sharing information in call

Country Status (2)

Country Link
CN (1) CN110383861B (en)
WO (1) WO2018157389A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651760A (en) * 2008-08-14 2010-02-17 索尼爱立信移动通讯有限公司 Information sharing in communication process
CN102014335A (en) * 2010-10-14 2011-04-13 宇龙计算机通信科技(深圳)有限公司 Method, system and mobile terminal for sharing resources in communication process
CN104580272A (en) * 2013-10-10 2015-04-29 中国移动通信集团公司 Method and apparatus for sharing data of UE
WO2016040535A1 (en) * 2014-09-10 2016-03-17 Microsoft Technology Licensing, Llc Real-time sharing during a phone call

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102006001503B4 (en) * 2006-01-11 2016-09-15 Intel Deutschland Gmbh Method and system for transmitting additional data
JP2013115638A (en) * 2011-11-29 2013-06-10 Sanyo Electric Co Ltd Television telephone device
CN104301527A (en) * 2014-09-26 2015-01-21 小米科技有限责任公司 Information acquisition method, device and system
US9264461B1 (en) * 2015-01-16 2016-02-16 Stephen James Van de Wetering Methods and systems for a personal data sharing app

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651760A (en) * 2008-08-14 2010-02-17 索尼爱立信移动通讯有限公司 Information sharing in communication process
CN102014335A (en) * 2010-10-14 2011-04-13 宇龙计算机通信科技(深圳)有限公司 Method, system and mobile terminal for sharing resources in communication process
CN104580272A (en) * 2013-10-10 2015-04-29 中国移动通信集团公司 Method and apparatus for sharing data of UE
WO2016040535A1 (en) * 2014-09-10 2016-03-17 Microsoft Technology Licensing, Llc Real-time sharing during a phone call

Also Published As

Publication number Publication date
CN110383861A (en) 2019-10-25
WO2018157389A1 (en) 2018-09-07

Similar Documents

Publication Publication Date Title
US9294985B2 (en) Bridge line appearance for location-aware mobile devices
US7353016B2 (en) Call intercept methods, such as for customer self-support on a mobile device
RU2570899C2 (en) Attaching multiple telephone lines to single mobile or landline telephone
JP2006166428A (en) Hybrid call log
US20080139186A1 (en) Establishing Communications Sessions
CN102892094A (en) Systems and methods for determining a network relationship between mobile devices
KR101270420B1 (en) Wireless data exchange
MX2013002183A (en) Systems and methods of providing communications services.
US9473642B2 (en) Methods and systems for providing location sensitive conference calling
US8027444B1 (en) Ringback tones management for phones having a profile specifying both organizational and personal ringback tones
US20140113604A1 (en) Method and apparatus for providing caller information upon reception of an incoming call in a communication system supporting enterprise mobility communication
JP5823185B2 (en) Sender information providing apparatus and program
CN110383861B (en) Method and terminal for sharing information in call
US9007998B1 (en) VoIP application for a loyalty program
CA3120341A1 (en) Systems and methods for providing caller identification over a public switched telephone network
JP6749645B2 (en) Call system, call method and program
JP6927614B2 (en) Call system, call method and program
JP2019145972A (en) Telephone control device and telephone control method
US11032427B1 (en) Voice enabled IoT using second line service
US11115373B1 (en) Multi-channel engagement platform converter
US8611510B2 (en) System and method for guest voicemail box
JP2013251861A (en) Voice call control system, control device, and control method
JP2020047973A (en) Telephone system
JP5996567B2 (en) System and program
JP2010530697A (en) Speed dial using database on IP network

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant