CN112383466A - Multi-scene chatting method and device - Google Patents
Multi-scene chatting method and device Download PDFInfo
- Publication number
- CN112383466A CN112383466A CN202011248186.4A CN202011248186A CN112383466A CN 112383466 A CN112383466 A CN 112383466A CN 202011248186 A CN202011248186 A CN 202011248186A CN 112383466 A CN112383466 A CN 112383466A
- Authority
- CN
- China
- Prior art keywords
- service
- chat
- user
- historical
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 230000004044 response Effects 0.000 claims abstract description 13
- 238000004590 computer program Methods 0.000 claims description 9
- 238000010586 diagram Methods 0.000 description 18
- 230000006870 function Effects 0.000 description 17
- 238000013461 design Methods 0.000 description 10
- 238000004891 communication Methods 0.000 description 8
- 230000008901 benefit Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000009877 rendering Methods 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/18—Commands or executable codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/216—Handling conversation history, e.g. grouping of messages in sessions or threads
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a multi-scene chatting method and device, and relates to the technical field of computers. One embodiment of the method comprises: in response to a request by a user to start a chat session: obtaining historical data for one or more business units associated with the user; acquiring service information of a current service, wherein the current service is associated with a current scene; presenting the acquired historical data in a chat session frame; wherein the one or more business units are associated with one or more scenarios. The embodiment reduces the complexity of the user facing a plurality of chat consultation entrances and improves the consultation efficiency.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a multi-scene chatting method and device.
Background
In a traditional business application scenario, chat consultation services are often single and are only used for sending and receiving messages under chat consultation, or only used for sending and receiving messages. This single approach is undoubtedly a drawback for systems with more and more complex business scenarios. It is possible that a set of systems may need to develop multiple similar functions, wasting resources.
In the prior art, in order to provide consulting services in different service scenes, a one-to-one session box technology bound with services is generally adopted, and a consulting session box needs to be created every time a service scene is met. In the case of similar services, fewer changes and changes can deal with service scene changes. However, when a large business difference is encountered, for example, when intelligent customer service is introduced, a set of chat consultation service scheme needs to be redesigned to meet business requirements. In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
In order to solve the multiplexing of multi-scenario service consultation, the invention provides a method suitable for multi-scenario service chat consultation.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for multi-scenario chat, which can adopt a technical means of associating a multi-scenario service module with a chat frame, can adapt to consultation of different service scenarios, and bind specific services and chat information; the information of multiple terminals is synchronous, and the chatting condition can be tracked in real time; the method has the advantages that the service chatting records in various scenes are quickly positioned, unread messages are checked in real time, and the method can be used as an intelligent question and answer inlet to provide various common question answers.
To achieve the above object, according to an aspect of the embodiments of the present invention, there is provided a method for multi-scenario chat, including:
in response to a request by a user to start a chat session:
obtaining historical data for one or more business units associated with the user;
acquiring service information of a current service, wherein the current service is associated with a current scene;
presenting the acquired historical data in a chat session frame;
wherein the one or more business units are associated with one or more scenarios.
The multi-scene chatting method according to the embodiment of the invention further comprises the following steps:
acquiring contact person information, wherein the contact person is a contact person associated with the current service; and/or
Acquiring service data of one or more service units associated with the user; and
and presenting the acquired contact information and the service data in the chat session box.
The multi-scene chatting method according to the embodiment of the invention further comprises the following steps:
and presenting the acquired service information of the current service in the chat session box.
The multi-scene chatting method according to the embodiment of the invention comprises the following steps:
the historical data includes at least one or more of:
a historical chat history associated with the historical scenario;
contacts associated with the history scenario.
According to the multi-scenario chat method provided by the embodiment of the invention, the service data comprises service basic information related to a service, and the service basic information at least comprises one or more of the following items:
a service scope of the service;
context information associated with the service.
According to the multi-scenario chat method in the embodiment of the present invention, the obtaining of the history data of one or more service units associated with the user includes:
transmitting the parameters of the service unit in a parameter format predefined by the one or more service units;
business data and/or historical data for the business unit is obtained via an interface associated with the business unit according to the incoming parameters.
According to the multi-scenario chat method in the embodiment of the present invention, the obtaining of the service data of one or more service units associated with the user includes:
transmitting the parameters of the service unit in a parameter format predefined by the one or more service units;
and acquiring the service data of the service unit through an interface associated with the service unit according to the transmitted parameters.
The method for multi-scenario chat according to the embodiment of the present invention, wherein the obtaining of the history data of one or more service units includes:
querying a list of all historical chat session records related to the user;
the historical chat session data and the contacts of the historical session are selected according to a first predetermined rule.
The method for multi-scenario chat according to the embodiment of the present invention, wherein the presenting a chat session box includes:
presenting all or a portion of a list of historical chat sessions associated with the user according to a second predetermined rule;
the unread messages in each conversation are displayed with a specific mark;
in response to the user clicking on any conversation, a historical chat log of the conversation is displayed and a new conversation is started.
The method for multi-scenario chat according to the embodiment of the present invention, wherein the presenting a chat session box includes:
starting a new session in a new session box; and/or
And switching to a new session in the current session frame.
The method for multi-scenario chat according to the embodiment of the present invention, wherein the first predetermined rule includes:
selecting all historical chat session data and contacts associated with the user; and/or
Selecting historical chat session data and contacts related to the current context and associated with the user.
The method for multi-scenario chat according to the embodiment of the present invention, wherein the second predetermined rule includes:
presenting a list of all historical chat sessions associated with the user; and/or
Presenting a list of historical chat sessions related to the current scene and associated with the user.
According to the multi-scenario chat method, the request of the user for starting the chat session is started from the entrance of the current service.
According to an aspect of the embodiment of the present invention, a device for multi-scenario chat is further provided, which is capable of implementing all methods described in the method embodiment of the present invention.
According to an aspect of the embodiments of the present invention, there is also provided a multi-scenario chat terminal, including: one or more processors; a storage device for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement any of the methods of the method embodiments of the present invention.
There is also provided, in accordance with an aspect of an embodiment of the present invention, a computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements any one of the methods described in the method embodiments of the present invention.
One embodiment of the above invention has the following advantages or benefits: because the technical means of associating the multi-scene service module with the chat frame is adopted, the method can adapt to the consultation of different service scenes and bind specific services and chat information; the information of multiple terminals is synchronous, and the chatting condition can be tracked in real time; the method has the advantages that the service chatting records in various scenes are quickly positioned, unread messages are checked in real time, and the method can be used as an intelligent question and answer inlet to provide various common question answers.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic view of a main flow of a method of multi-scenario chat according to an embodiment of the present invention;
FIG. 2 is a diagram of a dialog box design for multi-scenario chat, according to an embodiment of the invention;
FIG. 3 is a diagram of a dialog box design for multi-scenario chat, in accordance with an embodiment of the present invention;
FIG. 4 is a diagram of a dialog box design for multi-scenario chat, in accordance with an embodiment of the present invention;
FIG. 5 is a schematic diagram of the main flow of establishing a chat component template according to an embodiment of the invention;
fig. 6 is a schematic diagram of main modules of an apparatus for multi-scenario chatting according to an embodiment of the present invention;
FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 8 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
In a complex system such as an investor alliance platform, a variety of scenarios of services are involved, including bonds, equity, claims, investments, and the like. The responsible persons for different services in different scenarios may be different. The user hopes to contact with the related responsible person in the services of different scenes, and can bring the related service information into the chat page to clearly consult the services. Meanwhile, the user wants to reply to the chat information in real time in any terminal interface, such as app, web and the like, and the synchronization of the message records can be kept. Moreover, when a user establishes a session in many services, the user cannot remember which service the user has consulted at all times, where the portal is. At this time, a session entrance is needed to be provided for the user, so that the user can quickly locate the related services consulted by the user.
In addition, for new users of the system, a convenient and fast customer service entrance is generally desired, which can solve their own problems or doubts so as to quickly know the operations of the system.
How to adapt a conversation frame to consultation of different service scenes, bind service and chat information, keep message synchronization at a plurality of terminals, and quickly relocate all services consulted by the terminal after the conversation is established; meanwhile, intelligent customer service can be provided for the user, and the problem met by the user can be quickly responded. These are the problems to be solved by the present invention.
Fig. 1 is a flowchart of a multi-scenario chat according to an embodiment of the present invention, as shown in fig. 1, in response to a request from a user to start a chat session, steps S101, S102, S103 are entered.
Generally speaking, in one embodiment, first, a contact ID in specific service information is acquired through a general interface of a contact, the contact ID is used as a reference, a contact query interface is requested, and the acquired contact information is rendered in the interface. The contact information mainly comprises contact names and mobile phones or fixed phones.
There is one entry for each module's different services of bond, equity, bond, investment, etc. Through the entrance, different service parameters are transmitted to realize the adaptation of different services. Meanwhile, the private letter service module also designs a parameterized chat entrance, and positions the service-related chat scenes by transmitting the session id parameters to establish session connection. The consultation chat component is unified aiming at the parameter format of each entrance so as to adapt to the consultation function of each entrance.
Step S101: business data and/or historical data for one or more business units associated with a user is obtained.
In this step, the user opens a consult chat interface from a business portal such as bond, claim, equity, intermediary, research services, etc., triggering a chat session. When a chat session is triggered, rather than merely opening a dialog box as in existing chat software, it contains multiple steps to obtain information.
1) Obtaining historical chat records
The historical chat history described herein is a historical chat history associated with the service and the user. That is, when user a initiates a chat session, a session box of a displays a chat log in which a has participated, or a chat log in which a has participated and is associated with a current service. And no chat history is displayed for user B, independent of a. In one embodiment, the binding of chat records to services and contacts may be persisted to a database. When a user opens a conversation frame from a certain service entrance, calling an interface for searching historical message records in a historical data module, paging and inquiring the chat records, and rendering the chat records in a conversation frame content area. In one embodiment, more chat records may be viewed in the session content area. The user can click "add more" to query for more historical chat records. If there is no record, the top display is no more.
In another embodiment, if there are too many historical chat records, a first predefined rule may be predefined to filter the retrieved and presented historical records. The first predetermined rule may be defined in a variety of ways. For example, when the historical chat records do not exceed a first threshold N (N is an integer greater than or equal to 1), all the historical chat records are selected; and when the historical chat records exceed a first threshold value N, selecting a plurality of historical chat records with highest relevance with the current service scene, or selecting a plurality of historical chat records with the generation time closest to the current time. A second predetermined rule may also be predefined to select a historical chat history to be displayed. For example, chat logs selected according to a first predetermined rule need not all be presented on the dialog box interface. In one embodiment, it may be used only to determine relevance.
The history chat log may include the history contacts with which the history chat occurred.
In one embodiment, the history chat records can be obtained through parameter import, and the parameters for querying the history chat records are designed as shown in the following table:
TABLE 1
2) Preferably, service data of the service unit is acquired
Preferably, the method flow may further include acquiring historical service information related to the historical chat records, and may be presented in the session interface together with the historical chat records, or may not be presented, and is used to determine the correlation between the current service and the historical service. In one embodiment, after the user starts a chat session, the scene when the history chat occurs and the current traffic situation can be presented, preferably together with the history chat log. For example, if the historical chat history is about human consultation, then the current portal service module, human service module, and human information associated with the current situation may be presented along with the current chat.
3) Obtaining current service information to be consulted
When a user initiates consultation, the service information required to be consulted is displayed in the chat interface, and the user and the service contact person can conveniently communicate with each other in a targeted manner. The current service unit is associated with the current scene. For example, if the current scenario is that the user browses to a human-related policy has a question, the user initiates a chat consultation from the human resources service unit portal, at which step the current service "human resources" is associated with the "human resources policy" browsed by the user in the current scenario.
In one embodiment, the parameters for the service unit may be passed in a parameter format predefined by the service unit. Business data and/or historical data for the business unit is obtained via an interface associated with the business unit according to the incoming parameters. The main parameters for obtaining the service information are designed as shown in the following table:
TABLE 2
4) Preferably, the contact information is obtained
Preferably, the method of multi-scenario chatting may include the step of acquiring contact information. The contact person here refers to an opposite-end contact person that has a conversation with the user when the session is initiated. In case of each service unit having a person specializing in service consultation, the contact of the service can be found from the service portal at this step and a chat session can be initiated with it. In the case where, for example, a bot, or a unified customer service is responsible for consultation, a unified contact interface may be presented to the user, i.e., without the need to obtain information for each contact.
Under the condition that each business unit has a specific contact person to be responsible for business consultation, when a user opens a consultation chat interface from business entries such as bonds, equity, intermediaries, investment and the like, a contact person ID (contact person identification) in specific business information is obtained through a general interface of the contact person, the contact person ID is used as a reference, a contact person inquiry interface is requested, and the obtained contact person information is rendered in the interface. The contact information may include, for example, contact names, mobile or fixed phones, post, department, etc.
5) Sending messages
When the input content is empty, the send button is grayed out and is not usable. And when the input content is not empty, clicking to send, calling an interface, establishing a session, and transmitting the information to the back end. And the back end receives the parameters, binds the message, the service and the contact of the receiving party, and persists the message in a database to finish the sending and receiving of the message.
The main parameters of the message transmission interface are as follows:
TABLE 3
6) Unified private letter function
The user establishes a unique session for different services of different service units, and the unique session comprises the consultation content of the user for the service. When a user wants to initiate a session, a chat session can be initiated from each service unit separately, or from a separate chat portal for all service units. In this case, a portal is needed to quickly locate services and contents that have been consulted by the portal. In this embodiment, for example, it is referred to as a unified private mail function. The unified private letter function comprises private letter inquiry, state updating and the like.
1) Private letter query
Each history conversation is inquired in the private letter list, the number of unread conversations is displayed, and a user clicks any conversation, so that a chat conversation frame is popped up for consultation, the message record can be checked, and a new message can be sent. The consultation chat function is normally used.
2) Status update
When the user enters a session, which is equivalent to reading a message, a method is called to change the state to read.
TABLE 4
Fig. 2-4 are schematic diagrams of a multi-scenario chat session interface, according to an embodiment of the invention.
In one embodiment, the multi-scenario chat session interface may be based on a lightweight, high-performance, componentized MVVM library, enabling bi-directional binding of the interface and data to reduce DOM operations. For example, on the basis of an Element UI framework, the layout of a conversation box is realized, and the appearance of an interface is beautified by Sass. The session is established through mutual communication between the interface based on the HTTP protocol and the back end, and the instant chat function is realized. Different identifications are transmitted through conversation to distinguish services and contact persons in different scenes, chat information and the services are bound together and stored in a database, different terminal type recognition functions are added, and the instant chat consultation function which is suitable for different services in multiple scenes and synchronous data of multiple terminals is realized. And the information synchronization of multiple terminals is avoided, and the chat situation can be tracked in real time.
The layout of the layout UI layout is adopted, the layout of the following session box is formed by expanding the basic 1/24 columns, the flexible alignment of the columns is carried out through flex layout, and the response layout is designed by referring to Bootstrap response design. And the chat conversation box component is formed by nesting the Element popup component. The chat session can be opened in a new session or switched to the new session in the current session box.
Fig. 2 is a schematic diagram of a session box design of a WEB-side multi-scenario service. As shown in the example of fig. 2, the overall layout mainly includes a header area, a content transmission area, and a contact information area on the right. Based on the overall layout, the contents of each region can be freely laid out or combined. The dialog box design may also take any other design form.
Fig. 3 is a diagram illustrating contacts in a chat session box. As an example shown in fig. 3, the contact information area may contain contact avatars, contact names, contact phones, and the like. Any other contact information may also be included.
Fig. 4 is a schematic diagram of a chat session box at the app end. As an example shown in fig. 4, the title is a contact name. The top right phone icon may click to make a call. The middle is a content area, and the head of the content area is service related information. The bottom is an input box and a send button. The chat session box at the app end can also protect any other design as needed.
Fig. 5 is a schematic diagram of a main flow of establishing a chat component template according to an embodiment of the present invention.
Continuing with the example above, where the overall layout of the chat component is designed using the Element UI, the style is written in sass. The basic logic of the parsing component, around the lifecycle of vue, calls different hook functions, implements data management and DOM rendering.
S501: analyzing chat component input data
The overall logic of the chat component is analyzed. Parameters needing to be input by the component are called by considering services of different scenes, and data and types in the tips are defined.
In the parent component, the data required by the child component is imported, and the implementation example method is as follows:
< | A! Chat popup window
<chat
@closeDialog＝”closeDialog”:received＝”received”:show＝”chatDialog”ref＝”chat”></chat>
In the sub-components, example methods of reception and use are as follows:
s502: assembling chat component data output
The method to be exposed is designed according to the component logic, i.e. the data of the parent component is modified using the method that calls the parent component for $ emit. The method of the parent component is injected into the child component, as follows:
< | A! Chat popup window
<chat@closeDialog＝“closeDialog”:received＝“received”:show＝“chatDialog”ref＝“chat”></chat>
And then calling a parent component method at the subcomponent through $ emit to realize the data modification requirement of the parent component.
_sef.$emit(‘closeDialog’)；
S503: direct invocation of different module scenarios
After the assembly packaging is completed, the chat assembly can be directly called in different modules, and the calling method is as follows:
< | A! Chat popup window
<chat@closeDialog＝“closeDialog”:received＝“received”:show＝“chatDialog”ref＝“chat”></chat>
Under different service scenes, the chat component distinguishes different services by monitoring the parameter objects received by received. The component binds the service, the chat records and the contact persons through the parameter identifiers, and realizes the function of calling the unified chat consultation service by the multi-scene service.
It should be noted that the above-mentioned implementation manners are only examples, and do not constitute any limitation to the embodiments of the present invention.
Fig. 6 is a schematic diagram of main modules of a multi-scenario chat apparatus according to an embodiment of the present invention.
The module 601: a history module to obtain history data for one or more business units associated with a user in response to a request by the user to start a chat session;
a module 602: the system comprises a service module, a service module and a service module, wherein the service module is used for responding to a request of a user for starting a chat session to acquire service information of a current service, and the current service is associated with a current scene;
a module 603: the chat conversation frame module is used for presenting the acquired historical data in a chat conversation frame;
the multi-scenario chat apparatus further includes:
the contact module is used for acquiring contact information, and the contact is a contact associated with the current service;
a service data module for acquiring service data of one or more service units associated with the user;
a receiving module, configured to receive a request from a user to start a chat session; and
the chat conversation frame module is also used for presenting the acquired contact information and the service data in the chat conversation frame; and presenting the acquired service information of the current service in the chat session box.
Wherein,
the historical data includes at least one or more of:
a historical chat history associated with the historical scenario;
contacts associated with the history scenario.
The service data comprises service basic information related to a service, and the service basic information at least comprises one or more of the following items:
a service scope of the service;
context information associated with the service.
Obtaining historical data for one or more business units associated with the user comprises:
transmitting the parameters of the service unit in a parameter format predefined by the one or more service units;
business data and/or historical data for the business unit is obtained via an interface associated with the business unit according to the incoming parameters.
Obtaining service data for one or more service units associated with the user comprises:
transmitting the parameters of the service unit in a parameter format predefined by the one or more service units;
and acquiring the service data of the service unit through an interface associated with the service unit according to the transmitted parameters.
Obtaining historical data for one or more business units comprises:
querying a list of all historical chat session records related to the user;
the historical chat session data and the contacts of the historical session are selected according to a first predetermined rule.
The presenting a chat session box includes:
presenting all or a portion of a list of historical chat sessions associated with the user according to a second predetermined rule;
the unread messages in each conversation are displayed with a specific mark;
in response to the user clicking on any conversation, a historical chat log of the conversation is displayed and a new conversation is started.
The presenting a chat session box includes:
starting a new session in a new session box; and/or
And switching to a new session in the current session frame.
The first predetermined rule comprises:
selecting all historical chat session data and contacts associated with the user; and/or
Selecting historical chat session data and contacts related to the current context and associated with the user.
The second predetermined rule comprises:
presenting a list of all historical chat sessions associated with the user; and/or
Presenting a list of historical chat sessions related to the current scene and associated with the user.
The user's request to start a chat session is initiated from the entry of the current service.
The device class embodiments of the present invention are merely examples, which can be used to implement all of the methods in the method embodiments.
Fig. 7 illustrates an exemplary system architecture 700 of a multi-scenario chat method or multi-scenario chat apparatus to which embodiments of the present invention may be applied.
As shown in fig. 7, the system architecture 700 may include terminal devices 701, 702, 703, a network 704, and a server 705. The network 704 serves to provide a medium for communication links between the terminal devices 701, 702, 703 and the server 705. Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 701, 702, 703 to interact with a server 705 over a network 704, to receive or send messages or the like. The terminal devices 701, 702, 703 may have installed thereon various communication client applications, such as business system software capable of multi-scenario business consultation chat, private messaging service software, and the like (for example only).
The terminal devices 701, 702, 703 may be various electronic devices having display screens and supporting web browsing and APP, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 705 may be a server providing various services, such as a background management server (for example only) providing support for systems and chat session boxes browsed by users using the terminal devices 701, 702, 703. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back the processing result (e.g., chat information, contact information-examples only) to the terminal device.
It should be noted that the multi-scenario chat method provided by the embodiment of the present invention is generally executed by the server 705, and accordingly, the multi-scenario chat apparatus is generally disposed in the server 705.
It should be understood that the number of terminal devices, networks, and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program executes the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 801.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a receive module, a history module, a business data module, a chat session box module, and the like. Where the names of these modules do not in some cases constitute a limitation of the module itself, for example, the receiving unit may also be described as a "module receiving a request of a user to start a chat session".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise:
a method of multi-scenario chat, comprising:
in response to a request by a user to start a chat session:
obtaining historical data for one or more business units associated with the user;
acquiring service information of a current service, wherein the current service is associated with a current scene;
presenting the acquired historical data in a chat session frame;
wherein the one or more business units are associated with one or more scenarios.
Further comprising:
acquiring contact person information, wherein the contact person is a contact person associated with the current service; and/or
Acquiring service data of one or more service units associated with the user; and presenting the acquired contact information and the service data in the chat conversation frame.
Further comprising:
and presenting the acquired service information of the current service in the chat session box.
Wherein,
the historical data includes at least one or more of:
a historical chat history associated with the historical scenario;
contacts associated with the history scenario.
The service data comprises service basic information related to a service, and the service basic information at least comprises one or more of the following items:
a service scope of the service;
context information associated with the service.
Wherein obtaining historical data for one or more business units associated with the user comprises:
transmitting the parameters of the service unit in a parameter format predefined by the one or more service units;
business data and/or historical data for the business unit is obtained via an interface associated with the business unit according to the incoming parameters.
Wherein obtaining service data for one or more service units associated with the user comprises:
transmitting the parameters of the service unit in a parameter format predefined by the one or more service units;
and acquiring the service data of the service unit through an interface associated with the service unit according to the transmitted parameters.
Wherein the obtaining historical data of one or more service units comprises:
querying a list of all historical chat session records related to the user;
the historical chat session data and the contacts of the historical session are selected according to a first predetermined rule.
Wherein presenting the chat session box comprises:
presenting all or a portion of a list of historical chat sessions associated with the user according to a second predetermined rule;
the unread messages in each conversation are displayed with a specific mark;
in response to the user clicking on any conversation, a historical chat log of the conversation is displayed and a new conversation is started.
Wherein presenting the chat session box comprises:
starting a new session in a new session box; and/or
And switching to a new session in the current session frame.
Wherein the first predetermined rule comprises:
selecting all historical chat session data and contacts associated with the user; and/or
Selecting historical chat session data and contacts related to the current context and associated with the user.
Wherein the second predetermined rule comprises:
presenting a list of all historical chat sessions associated with the user; and/or
Presenting a list of historical chat sessions related to the current scene and associated with the user.
Wherein the request of the user to start the chat session is started from the entrance of the current service.
According to the technical scheme of the embodiment of the invention, because the technical means of associating the multi-scene service module with the chat frame is adopted, the consultation of different service scenes can be adapted, and the specific service and the chat information are bound; the information of multiple terminals is synchronous, and the chatting condition can be tracked in real time; the method has the advantages that the service chatting records in various scenes are quickly positioned, unread messages are checked in real time, and the method can be used as an intelligent question and answer inlet to provide various common question answers.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (19)
1. A method for multi-scenario chat, comprising:
in response to a request by a user to start a chat session:
obtaining historical data for one or more business units associated with the user;
acquiring service information of a current service, wherein the current service is associated with a current scene;
presenting the acquired historical data in a chat session frame;
wherein the one or more business units are associated with one or more scenarios.
2. The method of claim 1, further comprising:
acquiring contact person information, wherein the contact person is a contact person associated with the current service; and/or
Acquiring service data of one or more service units associated with the user; and
and presenting the acquired contact information and the service data in the chat session box.
3. The method of claim 1, further comprising:
and presenting the acquired service information of the current service in the chat session box.
4. The method of claim 1, comprising:
the historical data includes at least one or more of:
a historical chat history associated with the historical scenario;
contacts associated with the history scenario.
5. The method of claim 1, wherein the service data comprises service basic information related to a service, and wherein the service basic information comprises at least one or more of the following:
a service scope of the service;
context information associated with the service.
6. The method of claim 1, wherein obtaining historical data for one or more business units associated with the user comprises:
transmitting the parameters of the service unit in a parameter format predefined by the one or more service units;
business data and/or historical data for the business unit is obtained via an interface associated with the business unit according to the incoming parameters.
7. The method of claim 2, wherein obtaining service data for one or more service units associated with the subscriber comprises:
transmitting the parameters of the service unit in a parameter format predefined by the one or more service units;
and acquiring the service data of the service unit through an interface associated with the service unit according to the transmitted parameters.
8. The method of claim 6, the obtaining historical data for one or more business units comprising:
querying a list of all historical chat session records related to the user;
the historical chat session data and the contacts of the historical session are selected according to a first predetermined rule.
9. The method of claim 8, wherein presenting the chat session box comprises:
presenting all or a portion of a list of historical chat sessions associated with the user according to a second predetermined rule;
the unread messages in each conversation are displayed with a specific mark;
in response to the user clicking on any conversation, a historical chat log of the conversation is displayed and a new conversation is started.
10. The method of claim 1, wherein presenting the chat session box comprises:
starting a new session in a new session box; and/or
And switching to a new session in the current session frame.
11. The method of claim 8, wherein the first predetermined rule comprises:
selecting all historical chat session data and contacts associated with the user; and/or
Selecting historical chat session data and contacts related to the current context and associated with the user.
12. The method of claim 9, wherein the second predetermined rule comprises:
presenting a list of all historical chat sessions associated with the user; and/or
Presenting a list of historical chat sessions related to the current scene and associated with the user.
13. The method of claim 1, wherein the request from the user to start the chat session is from the entry of the current service.
14. An apparatus for multi-scenario chat, comprising:
a history module to obtain history data for one or more business units associated with a user in response to a request by the user to start a chat session;
the system comprises a service module, a service module and a service module, wherein the service module is used for responding to a request of a user for starting a chat session to acquire service information of a current service, and the current service is associated with a current scene; and
and the chat session box module is used for presenting the acquired historical data in a chat session box.
15. The apparatus of claim 14, wherein the apparatus further comprises:
the contact module is used for acquiring contact information, and the contact is a contact associated with the current service;
a service data module for acquiring service data of one or more service units associated with the user;
the chat conversation frame module is also used for presenting the acquired contact information and the service data in the chat conversation frame.
16. The apparatus of claim 14,
the chat session frame module is also used for presenting the acquired service information of the current service to the chat session frame.
17. The apparatus of claim 14, further comprising:
a receiving module, configured to receive a request for a user to start a chat session.
18. A multi-scenario chat terminal, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-13.
19. A computer-readable medium, having stored thereon a computer program,
the program when executed by a processor implementing the method of any one of claims 1 to 13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011248186.4A CN112383466B (en) | 2020-11-10 | 2020-11-10 | Multi-scene chatting method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011248186.4A CN112383466B (en) | 2020-11-10 | 2020-11-10 | Multi-scene chatting method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112383466A true CN112383466A (en) | 2021-02-19 |
| CN112383466B CN112383466B (en) | 2023-02-24 |
Family
ID=74578289
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011248186.4A Active CN112383466B (en) | 2020-11-10 | 2020-11-10 | Multi-scene chatting method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112383466B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103186534A (en) * | 2011-12-27 | 2013-07-03 | 腾讯科技（深圳）有限公司 | Prompt method and device for contact dynamic information |
| CN103634198A (en) * | 2012-08-29 | 2014-03-12 | 深圳市智慧宇宙科技有限公司 | Interface display method and device of instant messaging software |
| CN104468319A (en) * | 2013-09-18 | 2015-03-25 | 阿里巴巴集团控股有限公司 | A session content combining method and system |
| US20150172069A1 (en) * | 2013-12-18 | 2015-06-18 | Personify, Inc. | Integrating user personas with chat sessions |
| CN104765522A (en) * | 2014-01-08 | 2015-07-08 | 腾讯科技（深圳）有限公司 | Chat window display control method and system |
| CN106685793A (en) * | 2015-11-10 | 2017-05-17 | 深圳市云软信息技术有限公司 | Instant messaging method and system |
| CN106789551A (en) * | 2016-11-14 | 2017-05-31 | 北京小米移动软件有限公司 | Conversation message methods of exhibiting and device |
| CN107071181A (en) * | 2017-04-27 | 2017-08-18 | 长沙军鸽软件有限公司 | A kind of method of Auto-matching communication contact people |
| CN107404428A (en) * | 2017-06-06 | 2017-11-28 | 阿里巴巴集团控股有限公司 | A kind of method of servicing, device and electronic equipment based on chat group |
| CN107453977A (en) * | 2016-06-01 | 2017-12-08 | 腾讯科技（深圳）有限公司 | The method and server of a kind of session management |
| CN109981447A (en) * | 2019-03-27 | 2019-07-05 | 金瓜子科技发展（北京）有限公司 | A kind of message treatment method, device and equipment |
| US20200125632A1 (en) * | 2018-10-23 | 2020-04-23 | International Business Machines Corporation | Assisting users of chat session to participate in chat session |
-
2020
- 2020-11-10 CN CN202011248186.4A patent/CN112383466B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103186534A (en) * | 2011-12-27 | 2013-07-03 | 腾讯科技（深圳）有限公司 | Prompt method and device for contact dynamic information |
| CN103634198A (en) * | 2012-08-29 | 2014-03-12 | 深圳市智慧宇宙科技有限公司 | Interface display method and device of instant messaging software |
| CN104468319A (en) * | 2013-09-18 | 2015-03-25 | 阿里巴巴集团控股有限公司 | A session content combining method and system |
| US20150172069A1 (en) * | 2013-12-18 | 2015-06-18 | Personify, Inc. | Integrating user personas with chat sessions |
| CN104765522A (en) * | 2014-01-08 | 2015-07-08 | 腾讯科技（深圳）有限公司 | Chat window display control method and system |
| CN106685793A (en) * | 2015-11-10 | 2017-05-17 | 深圳市云软信息技术有限公司 | Instant messaging method and system |
| CN107453977A (en) * | 2016-06-01 | 2017-12-08 | 腾讯科技（深圳）有限公司 | The method and server of a kind of session management |
| CN106789551A (en) * | 2016-11-14 | 2017-05-31 | 北京小米移动软件有限公司 | Conversation message methods of exhibiting and device |
| CN107071181A (en) * | 2017-04-27 | 2017-08-18 | 长沙军鸽软件有限公司 | A kind of method of Auto-matching communication contact people |
| CN107404428A (en) * | 2017-06-06 | 2017-11-28 | 阿里巴巴集团控股有限公司 | A kind of method of servicing, device and electronic equipment based on chat group |
| US20200125632A1 (en) * | 2018-10-23 | 2020-04-23 | International Business Machines Corporation | Assisting users of chat session to participate in chat session |
| CN109981447A (en) * | 2019-03-27 | 2019-07-05 | 金瓜子科技发展（北京）有限公司 | A kind of message treatment method, device and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112383466B (en) | 2023-02-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9521255B1 (en) | Systems and methods for visual presentation and selection of IVR menu | |
| US10911565B2 (en) | Method, device and system for associating a service account | |
| US20130022181A1 (en) | Systems and methods for visual presentation and selection of ivr menu | |
| US20190082043A1 (en) | Systems and methods for visual presentation and selection of ivr menu | |
| JP2007149099A (en) | Service broker integration layer for supporting telecommunication client service request | |
| US20170289332A1 (en) | Systems and Methods for Visual Presentation and Selection of IVR Menu | |
| US20220366066A1 (en) | Display method, display device, and electronic device | |
| CA3061623C (en) | File sending in instant messaging applications | |
| CN115022262B (en) | Session processing method, device, equipment and medium | |
| CA2928357C (en) | Multi-channel delivery platform | |
| CN111881392A (en) | Page display method and device | |
| CN108549586B (en) | Information processing method and device | |
| US10079932B2 (en) | Method and system for logging and reporting call detail information | |
| WO2011051156A1 (en) | Systems and methods for networking across web based and telecommunication based portals | |
| CN114726914A (en) | Cross-service provider information sending method and device and electronic equipment | |
| US8345839B2 (en) | System and method for providing awareness of and context for phone conversations across multiple personal devices | |
| WO2022078397A1 (en) | Communication method and apparatus, device, and storage medium | |
| CN110442416B (en) | Method, electronic device and computer-readable medium for presenting information | |
| CN112256372A (en) | Information processing method and device and electronic equipment | |
| CN112383466B (en) | Multi-scene chatting method and device | |
| CN114979256B (en) | Message pushing method and device, electronic equipment and computer readable medium | |
| CN116112457A (en) | Method, device, computer equipment and storage medium for notifying message | |
| CN115174282A (en) | Information interaction method, device, equipment and medium | |
| CN112306596A (en) | Information interaction method and device and electronic equipment | |
| CN113448652A (en) | Request processing method and device |
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 |