CN115208846B

CN115208846B - Session interaction method and system

Info

Publication number: CN115208846B
Application number: CN202210800197.1A
Authority: CN
Inventors: 李展鹏
Original assignee: Wuhan United Imaging Healthcare Co Ltd
Current assignee: Wuhan United Imaging Healthcare Co Ltd
Priority date: 2022-07-08
Filing date: 2022-07-08
Publication date: 2023-06-09
Anticipated expiration: 2042-07-08
Also published as: CN115208846A

Abstract

The embodiment of the specification provides a session interaction method and a session interaction system, wherein the method comprises the steps of responding to a session request input by a user through an interaction terminal, triggering the interaction terminal to present a session interface, and determining the display content of the session interface based on a message body, wherein the message body comprises a history message part, a system message part and a current session message part; acquiring an interaction instruction input by a user through an interaction terminal; updating a message body in response to the interaction instruction; and triggering the interactive terminal to update the session interface based on the updated message body.

Description

Session interaction method and system

Technical Field

The present disclosure relates to the field of man-machine interaction technologies, and in particular, to a session interaction method and system.

Background

To meet the needs of users, more and more platforms provide intelligent question-answering services to users. Through the intelligent question-answering service, a user can conduct a session with the question-answering robot at a terminal such as a mobile phone, a computer and the like, so that service requests, questions and the like are provided. The conventional question-answering platform generally stores different information, such as user information, system information, robot reply information and other single information, respectively, which results in complex data storage structure and low data management efficiency. Since the session interaction between the user and the question-answering robot determines the structure of the data stored in the question-answering platform, when the session interaction varies greatly, the data structure will need to be adjusted. When the data structure is complex, the process of adjusting the data structure is also extremely difficult, and repeated work exists.

Therefore, it is desirable to provide a session interaction method and system, which can uniformly process and manage related data of session interaction, and improve the storage and management efficiency of the data.

Disclosure of Invention

One of the embodiments of the present disclosure provides a session interaction method. The session interaction method comprises the following steps: responding to a session request input by a user through an interactive terminal, triggering the interactive terminal to present a session interface, wherein the display content of the session interface is determined based on a message body, and the message body comprises a history message part, a system message part and a current session message part; acquiring an interaction instruction input by the user through the interaction terminal; updating the message body in response to the interaction instruction; and triggering the interactive terminal to update the session interface based on the updated message body.

One of the embodiments of the present specification provides a session interaction system, including: the triggering module is used for responding to a session request input by a user through the interactive terminal, triggering the interactive terminal to present a session interface, wherein the display content of the session interface is determined based on a message body, and the message body comprises a history message part and/or a system message part and/or a current session message part; the acquisition module is used for acquiring an interaction instruction input by the user through the interaction terminal; an updating module, configured to respond to the interaction instruction, and update the message body; and the triggering module is used for triggering the interactive terminal to update the session interface based on the updated message body.

One of the embodiments of the present specification provides a computer-readable storage medium storing computer instructions that, when read by a computer in the storage medium, the computer performs a session interaction method.

In some embodiments of the present description, the message body may be utilized to store historical messages, system messages, current session messages, etc., involved in the user's session with the question-answering robot. Because various messages in the message body are stored based on a preset arrangement mode, various messages can be rapidly positioned, the display content of the session interface is determined based on the message body, and different types of messages do not need to be acquired from different sources. And the related data of the session interaction can be uniformly processed and managed based on the message body, so that the data structure can be flexibly adjusted, and the data storage and management efficiency is improved. In the conventional session interaction method, because different messages correspond to different message sources or categories, and the user questions and the system replies are stored separately, the associated messages need to be logically associated. In the session, different sources need to be used to retrieve different information, and logic judgment needs to be performed to find the associated data. Compared with the traditional session interaction method, the session interaction method based on the message body has higher data management and storage efficiency, and further can provide better session service.

Drawings

The present specification will be further elucidated by way of example embodiments, which will be described in detail by means of the accompanying drawings. The embodiments are not limiting, in which like numerals represent like structures, wherein:

FIG. 1 is a schematic illustration of an application scenario of a conversational interaction system according to some embodiments of the disclosure;

FIG. 2 is an exemplary block diagram of a conversational interaction system according to some embodiments of the disclosure;

FIG. 3 is an exemplary flow chart of a session interaction method shown in accordance with some embodiments of the present description;

FIG. 4 is an exemplary flow chart of a session interaction method according to some embodiments of the present description;

FIG. 5 is an exemplary diagram of a message body shown in accordance with some embodiments of the present description;

FIG. 6 is an exemplary diagram of a data body of a single message shown in accordance with some embodiments of the present description;

FIG. 7A is an exemplary diagram of a first session interface shown in accordance with some embodiments of the present description;

FIG. 7B is an exemplary diagram of a second type of session interface shown in accordance with some embodiments of the present description;

FIG. 7C is an exemplary diagram of a third type of session interface shown in accordance with some embodiments of the present description;

Fig. 7D is an exemplary diagram of a fourth session interface shown in accordance with some embodiments of the present description.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present specification, the drawings that are required to be used in the description of the embodiments will be briefly described below. It is apparent that the drawings in the following description are only some examples or embodiments of the present specification, and it is possible for those of ordinary skill in the art to apply the present specification to other similar situations according to the drawings without inventive effort. Unless otherwise apparent from the context of the language or otherwise specified, like reference numerals in the figures refer to like structures or operations.

It will be appreciated that "system," "apparatus," "unit" and/or "module" as used herein is one method for distinguishing between different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the words can be replaced by other expressions.

As used in this specification and the claims, the terms "a," "an," "the," and/or "the" are not specific to a singular, but may include a plurality, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that the steps and elements are explicitly identified, and they do not constitute an exclusive list, as other steps or elements may be included in a method or apparatus.

A flowchart is used in this specification to describe the operations performed by the system according to embodiments of the present specification. It should be appreciated that the preceding or following operations are not necessarily performed in order precisely. Rather, the steps may be processed in reverse order or simultaneously. Also, other operations may be added to or removed from these processes.

Fig. 1 is a schematic view of an application scenario of a session interaction system according to some embodiments of the present description. As shown in fig. 1, an application scenario 100 of a conversational interaction system may include one or more of a processing device 110, an interaction terminal 120, a storage device 130, and the like.

In some embodiments, the user may interact with the question and answer robot via the interactive terminal 120, for example, making a session request, making an interaction instruction, etc. The interactive instructions may be used to ask a query to answer, ask a history message to load, ask some service to be provided (e.g., an online inquiry), etc. The question-answering robot refers to a computer program which can perform a conversation with a user by using techniques such as artificial intelligence and natural language processing. In some embodiments, the question answering robot may be executed or implemented by the processing device 110.

The interactive terminal 120 may refer to one or more terminals used by a user, including but not limited to one or any combination of mobile devices, tablet computers, laptop computers, desktop computers, and other input and/or output enabled devices. In some embodiments, the interactive terminal 120 may include other smart terminals, such as a wearable smart terminal, and the like.

The interactive terminal 120 may include a session interface 121. The session interface 121 may display a record of interactions between the user and the question-answering robot, etc. In some embodiments, the user may enter a session request and/or an interaction instruction via the interaction terminal. The interactive terminal 120 may transmit the inputted session request and/or the interactive instruction to the processing device 110. The processing device 110 may process data related to the session request and the interaction instruction and trigger the interaction terminal 120 to update the session interface 121 based on the processing result. In some embodiments, the interactive terminal 120 may have installed thereon an applet, APP, etc. for the session. When the user opens the applet, APP, etc., the interactive terminal 120 may present the session interface 121. In some embodiments, the interactive terminal 120 may communicate data with the processing device 110 and the storage device 130 via the network 120. In some embodiments, the processing device 110 may be part of the interactive terminal 120.

In some embodiments, the interactive terminal 120 may be used by one or more users performing consultation or the like. Different users have respective unique identification numbers. The user may include multiple types of users, e.g., registered users, guests, etc. The processing device 110 may identify the type of user based on the unique identification number of the different user. In some embodiments, the user may also conduct a session with a human customer service using the interactive terminal 120. For example, when the question-answering robot cannot answer the user, the answer may be made by a human customer service. For another example, when the user needs to consult with a human customer service, a reply may be made by the human customer service. The above examples are only intended to illustrate the interactive terminal 120 and not to limit it.

The storage device 130 may be used to store data and/or instructions related to the application scenario 100 of the session interaction system. In some embodiments, the storage device 130 may store data and/or information obtained from the processing device 110, the interactive terminal 120, and/or the like. For example, the storage device 130 may store a message body as well as historical, system, and current session message portions of the message body, and the like.

In some embodiments, storage device 130 may include one or more storage components, e.g., one or more storage components may each correspond to a database, e.g., historical message database 131, question-answer database 132, etc. Alternatively, the historical message database 131 and the question database 132 may correspond to the same storage component, e.g., stored on different partitions of the same memory. In some embodiments, the storage device 130 may be disposed in the processing device 110. In some embodiments, the storage device 130 may include Random Access Memory (RAM), read Only Memory (ROM), mass storage, removable memory, volatile read-write memory, and the like, or any combination thereof. By way of example, mass storage may include magnetic disks, optical disks, solid state disks, and the like. In some embodiments, storage device 130 may be implemented on a cloud platform.

The historical message database 131 may be used to store historical messages in the conversational interaction system. For example, the history messages may include history questions issued by different users and history replies to those history questions by the question-and-answer robot. In some embodiments, the history messages in the history message database 131 may be stored in a one-to-one answer form. For example, in the history message database 131, a history question of the user and a history return of the corresponding question-answering robot are associated and stored together as a message record. A historical reply to the question-and-answer robot may include one or more pieces of information for the historical question. In some embodiments, only historical valid replies are stored in the historical message database 131, while invalid historical replies are not stored in the historical message database 131. For more on valid replies and invalid replies see the relevant description in fig. 4. In some embodiments, each history question and a history reply to the history question may be stored in the history message database 131. The historical reply is stored in the historical message database 131, whether or not it is valid. In some embodiments, the history messages in the history message database 131 may also be stored in other ways.

The question and answer database 132 may be used to store questions and corresponding answers. When a user asks, the processing device 110 may query through the question and answer database 132 whether there is a corresponding answer, and then reply to the user's question. In some embodiments, questions and corresponding solutions in question and answer database 132 may be stored in a question and answer form. In some embodiments, processing device 110 may update answer database 132, etc. For example, processing device 110 may pair a new question and its corresponding solution and add it to question and answer database 132 according to the instructions of the administrator of the question and answer platform. For another example, processing device 110 may update questions and corresponding solutions in the question and answer database (e.g., delete or alter certain solutions) according to actual needs, as instructed by the administrator of the question and answer platform.

In some embodiments, the processing device 110 may process information and/or data related to the application scenario 100 of the conversational interaction system to perform one or more of the functions described in this specification. For example, the processing device 110 may process a session request, an interaction instruction (e.g., ask a question, load a history message), etc., entered by a user via the interactive terminal 120, and trigger the interactive terminal 120 to present a corresponding session interface. For another example, processing device 110 may update historical message database 131 in storage device 130 based on the user's session record.

In some embodiments, the processing device 110 may utilize the message body to drive interactions between the user and the interactive terminal 120 (or question-answering robot). A message body may refer to a collection of a number of different messages, where the different messages are stored in a particular form. The content in the message body may be used to determine the display content of the session interface 121 of the interactive terminal 120. For example, at the beginning of a session, the content in the message body is empty. As the session progresses, one or more of the history messages, system messages, session messages, etc. may be updated into the message body. At the same time, the display content of the session interface 121 is continuously updated based on the message body.

For example only, as shown in fig. 5, the message body (msgpody) 500 includes a history message portion (msgchistore) 510, a system message portion (msgcystem) 520, and a current session message portion (msgCurrent) 530, among others. Different message parts of the message body display different content.

The history message part 510 is mainly used to store history messages between the user and the quiz robot. In some embodiments, the history message portion 510 may store a certain number of history messages, such as 10, 20 most recent history messages. In some embodiments, as described above, the user's and the question-and-answer robot's historical messages may be stored in the historical message database 131 in the form of message records, each message record including the user's historical questions and the question-and-answer robot's historical replies (or valid historical replies). The history message part 510 may be used to store a certain number of message records (i.e., a certain number of history question and history reply pairs). For example, the history message portion 510 may be used to store 10 pairs of history questions and history replies.

The system message section 520 may be used to store system messages sent by the question-answering robot, e.g., "Hi, i am an intelligent customer service small U. Please ask what can help to you? "," little U guesses you want to ask: 1. film print 2. Film print color difference … …', etc. In some embodiments, the system message portion 520 may only store system messages sent by the question-answering robot in the current session.

The current session message section 530 may be used to store messages of the current session between the user and the question-answering robot. In some embodiments, the content of the current session message portion may be updated in real-time based on interactions between the user and the question-answering robot.

In some embodiments, the history message part 510, the system message part 520, and the current session message part 530 may be arranged based on a preset order. The preset sequence may refer to a sequence of different message parts in the preset message body 500. For example, as shown in fig. 5, the history message part 510, the system message part 520, and the current session message part 530 are sequentially arranged in the message body 500. The system message portion 520 is located in the middle of the message body 500 and may separate the history message portion 510 from the current session message portion 530. By arranging the history message part 510, the system message part 520, and the current session message part 530 in a preset order, it is possible to help to quickly distinguish and locate messages, and to improve data management and control efficiency. For example, the history messages stored above the system messages and the current session messages stored below the system messages may be quickly located based on the system message portion 520.

It should be noted that the preset order shown in fig. 5 is provided for exemplary purposes only, and the history message part 510, the system message part 520, and the current session message part 530 may be arranged in other orders. For example, the preset order may be that the system message part 520, the history message part 510, and the current session message part 530 are sequentially arranged.

In some embodiments, data related to individual messages in the message body 500 may be stored based on the data body.

By way of example only, fig. 6 shows an exemplary schematic diagram of a data body of a single message. As shown in fig. 6, a data body (msgsignle) 600 may include userType610, uid 620, type 630, content 640, time 650, netError/loading 660, and the like.

In some embodiments, userType610 can be used to determine whether the data body corresponds to a system message or a non-system message. For example, when userType610 is "system," the data body is a system message. uid 620 may determine the sender of the message. For example, when uid 620 is "0", the data body corresponds to a message sent by the user; when uid 620 is "1", the data body corresponds to a message sent by the system. the type 630 may determine a message type, e.g., at least one of text message, picture, score, share content, etc.

content 640 may encapsulate message content. content 640 may include id, text, type, evaluate, etc. id is the identification number of the message corresponding to the data body, and the identification numbers corresponding to different data bodies are different. And text is the message content corresponding to the data body. type is the content category of the data body. The evaluation may be used to determine whether the message corresponding to the data body is an evaluation class message. For example, when the data volume is a message of the evaluation type, evaluation is "true". When the data volume is a non-evaluation type message, the evaluation is empty.

time 650 may record the message transmission time corresponding to the data volume. netError/loading 660 may determine message status. The message states may include a message network state and a message load state. The message network status may indicate network anomalies in the transmission of messages corresponding to the data volume. The message load state may indicate that the message corresponding to the data volume is being loaded. In some embodiments, a single data body will have only one of a message network state and a message load state.

In some embodiments, the data stored in a single data body may include both external state data and internal state data. The external state data may be used to determine associations of data volumes with other data volumes. The internal state data may represent the content of the message itself to which the data body corresponds. For example, content 640 in data body 600 belongs to inner state data, and other data belongs to outer state data.

In some embodiments, the data bodies of different types of messages (e.g., history messages, system messages, current session messages, etc.) may be the same or different. For example, the netError/loading 660 may be omitted from the message body corresponding to the system message. By setting the data body, the data related to the message can be stored in a more standard and unified form, which is beneficial to improving the efficiency of subsequent data management and processing.

In some embodiments, processing device 110 may include one or more processing engines (e.g., a single chip processing engine or a multi-chip processing engine). By way of example only, the processing device 110 may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), an Application Specific Instruction Processor (ASIP), a Graphics Processor (GPU), a Physical Processor (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), an editable logic circuit (PLD), a controller, a microcontroller unit, a Reduced Instruction Set Computer (RISC), a microprocessor, or the like, or any combination thereof.

It should be noted that the application scenario 100 of session interaction is provided for illustrative purposes only and is not intended to limit the scope of the present description. Many modifications and variations will be apparent to those of ordinary skill in the art in light of the present description. For example, the application scenario 100 of session interaction may implement similar or different functionality on other devices. However, such changes and modifications do not depart from the scope of the present specification.

For example, the message body 500 shown in fig. 5 and the data body 600 shown in fig. 6 are provided for exemplary purposes only, and the message body 500 and the data body 600 may be represented in other forms, or include other contents, or omit some of them. For example, the contents contained in the message body 500 are not limited to the history message part 510, the system message part 520, and the current session message part 530, and the processing device 110 may be configured according to actual needs.

As another example, the application scenario 100 of the session interaction system may also include a network or the like. The network may connect various components of the system and/or connect the system to external resource components. The network allows communication between the components, as well as with other components outside the system. For example, processing device 110 obtains the history message from storage device 130 over a network.

Fig. 2 is an exemplary block diagram of a conversational interaction system according to some embodiments of the disclosure.

In some embodiments, the session interaction system 200 may include a triggering module 210, an acquisition module 220, an updating module 230, and a determination module 240.

In some embodiments, the triggering module 210 may be configured to trigger the interactive terminal to present a session interface in response to a session request input by the user via the interactive terminal, where a display content of the session interface is determined based on a message body, and the message body includes a history message part and/or a system message part and/or a current session message part.

In some embodiments, the obtaining module 220 may be configured to obtain an interaction instruction input by a user via the interaction terminal.

In some embodiments, the update module 230 may be configured to update the message body in response to the interaction instruction.

In some embodiments, the triggering module 210 may be further configured to trigger the interactive terminal to update the session interface based on the updated message body.

In some embodiments, the retrieval module 220 may also be configured to retrieve the target system message in response to the session request. In some embodiments, the update module 230 may also be configured to update the system message portion based on the target system message to cause the target system message to be displayed on the session interface.

In some embodiments, the determination module 240 may be used to determine whether a user has a history message.

In some embodiments, the triggering module 210 may also be configured to trigger the interactive terminal to display a history message loading hint in response to a determination that the user has a history message.

In some embodiments, the interaction instructions include a history message load instruction, and the retrieval module 220 may be further configured to retrieve the target history message based on the history message database in response to the history message load instruction. In some embodiments, the update module 230 may also be configured to update the history message portion based on the target history message to cause the target history message to be displayed on the session interface.

In some embodiments, the interactive instructions include user questions, and the acquisition module 220 may be further configured to acquire a question reply in response to the user questions. In some embodiments, the update module 230 may also be configured to update the current session message portion based on the challenge response such that the challenge response is displayed on the session interface.

In some embodiments, the determination module 240 may also be configured to determine whether a valid reply is included in the quiz reply; and in response to the judgment result that the questioning reply comprises the valid reply, storing the user questioning and questioning reply pairing in a historical message database.

In some embodiments, the acquisition module 220 may also be used to determine if the network is abnormal. In some embodiments, the triggering module 210 may be further configured to trigger the interactive terminal to display a message anomaly prompt in response to a determination of a network anomaly. In some embodiments, the obtaining module 220 may be further configured to obtain a challenge response in response to a determination that the network is normal.

It should be understood that the system shown in fig. 2 and its modules may be implemented in a variety of ways. For example, in some embodiments the system and its modules may be implemented in hardware, software, or a combination of software and hardware.

It should be noted that the above description of the system and its modules is for convenience of description only and is not intended to limit the present description to the scope of the illustrated embodiments. It will be appreciated by those skilled in the art that, given the principles of the system, various modules may be combined arbitrarily or a subsystem may be constructed in connection with other modules without departing from such principles. In some embodiments, the triggering module 210, the acquiring module 220, the updating module 230, and the determining module 240 disclosed in fig. 2 may be different modules in one system, or may be one module to implement the functions of two or more modules. For example, each module may share one memory module, or each module may have a respective memory module. Such variations are within the scope of the present description.

Fig. 3 is an exemplary flow chart of a session interaction method according to some embodiments of the present description. As shown in fig. 3, the process 300 includes the following steps. In some embodiments, the process 300 may be performed by the processing device 110.

In step 310, in response to a session request input by a user via the interactive terminal, the interactive terminal is triggered to present a session interface, and display content of the session interface is determined based on a message body, wherein the message body comprises a history message part, a system message part and a current session message part. In some embodiments, step 310 may be performed by the trigger module 210.

The session request may refer to a request sent by a user that a session needs to be performed. In some embodiments, the triggering module 210 may receive a session request input by a user through the interactive terminal. For example, the trigger module 210 may confirm that the user inputs a session request by opening a question-answering platform, a question-answering applet, a question-answering web page, etc. through the interactive terminal. The interactive terminal will automatically send the session request to the processing device 110. For another example, the question-answering platform, question-answering applet, question-answering web page, etc. have an option or button to send a session request, etc. When the user clicks on the option or button, the trigger module 210 may confirm that the user entered the session request.

The session interface may refer to an interface of a session between a user and the question-answering robot.

In some embodiments, the trigger module 210 may obtain the target system message in response to a session request entered by the user via the interactive terminal; and updating the system message portion of the message body based on the target system message to cause the target system message to be displayed on the session interface. For example, the target system message may be used to greet the user. As another example, the target system message may provide the user with some commonly used service options.

In some embodiments, the content of the target system message may be the same or different for different users. For example, the target system message may be a unified message for the hello user. As another example, the trigger module 210 may determine different targeted system messages based on user registered information (e.g., gender, age, past medical history, allergy history, etc.). For example, if the user is male, age 50, past medical history includes hypertension, the trigger module 210 may send a system message regarding consulting aspects of hypertension. For example, if the user is female, age 50, past medical history includes a stomach illness, the trigger module 210 may send a system message regarding consulting aspects of the stomach illness, etc. For another example, if the user is an old user, the trigger module 210 may determine the content of the system message portion based on the content of the user's historical message portion. Different target system messages are acquired aiming at different users, so that a session interface displays the target system messages, the users can acquire the required system messages, and the use physical examination of the users using the question-answering applet is improved.

In some embodiments, in response to a session request entered by a user, the trigger module 210 may determine whether a history message exists for the user. When the user has a history message, the triggering module 210 may trigger the interactive terminal to display a history message loading prompt. In some embodiments, the trigger module 210 may determine whether the user has a history message based on the message body or a history message database. For more on determining whether a user has a history message, see the relevant description of the section of fig. 4.

Step 320, obtaining an interaction instruction input by a user via the interaction terminal. In some embodiments, step 320 may be performed by the acquisition module 220.

The interactive instructions may be used to ask the question-answering robot to perform specific actions, such as replying to a query, loading a history message, providing some kind of service (on-line questioning, query reporting), etc. For example, as shown in fig. 7D, the interactive instructions may ask the question robot to answer a question "CT inspection result has come out? ". For another example, the interaction instructions may require the question-answering robot to load historical messages. In some embodiments, the user may input the interaction instruction through the interaction terminal by typing, voice, gesture operation, and the like.

In response to the interaction instruction, the message body is updated, step 330. In some embodiments, step 330 may be performed by update module 230.

In some embodiments, the update module 230 may update the message body based on the interaction instructions. For example, the update module 230 may obtain a reply to an interaction instruction corresponding to the interaction instruction via a database (e.g., the historical message database 131, the question-answer database 132, etc.) in the storage device 130 based on the interaction instruction entered by the user. The update module 230 may add the interaction instruction and the reply corresponding to the interaction instruction to the message body, and update the message body. In some embodiments, the update module 230 may update different portions of the message body based on different interaction instructions. For example, the interaction instruction is a history message loading instruction, and based on the target history message, the update module 230 may update the history message portion of the message body to cause the target history message to be displayed on the session interface, for details, see the relevant description of fig. 4. For another example, the interactive instruction may be a user question, and the update module 230 may update the current session message portion of the message body to cause a question reply to be displayed on the session interface, as described in detail with reference to fig. 4.

And 340, triggering the interactive terminal to update the session interface based on the updated message body. In some embodiments, step 340 may be performed by the trigger module 210.

For example, as described above, in response to a user question entered by a user, a question reply may be obtained and the current session message portion in the message body updated based on the question reply. Based on the updated message body, the triggering module 210 may trigger the interactive terminal to display the question reply. For another example, in response to a user entered history message load instruction, a target history message may be obtained and the history message portion in the message body updated based on the target history message. Based on the updated message body, the triggering module 210 may trigger the interactive terminal to display the target history message.

In some embodiments of the present description, the message body may be utilized to store historical messages, system messages, current session messages, etc., involved in the user's session with the question-answering robot. Because the messages in the message body are stored based on the preset arrangement mode, the processing device 110 can quickly locate the messages and determine the display content of the session interface based on the message body, without acquiring the messages of different types from different sources. In addition, the processing device 110 can uniformly process and manage the related data of the session interaction, so that the data structure can be flexibly adjusted, and the storage and management efficiency of the data can be improved. In the conventional session interaction method, because different messages correspond to different message sources or categories, and the user questions and the system replies are stored separately, the associated messages need to be logically associated. In the session, different sources need to be used to retrieve different information, and logic judgment needs to be performed to find the associated data. Compared with the traditional session interaction method, the session interaction method based on the message body has higher data management and storage efficiency, and further can provide better session service.

Fig. 4 is an exemplary flow chart of a session interaction method according to some embodiments of the present description. As shown in fig. 4, the process 400 includes the following steps. In some embodiments, the process 400 may be performed by the processing device 110. In some embodiments, flow 400 may be an embodiment of flow 300.

In step 401, a target system message is acquired in response to a session request. In some embodiments, step 401 may be performed by the acquisition module 220.

The target system message may refer to a message automatically issued by the system for the session request. The targeted system messages may be used to greet the user, provide the user with some commonly used service options, etc. For more description of the target system message, reference may be made to step 310 in fig. 3.

Step 402, updating the system message part based on the target system message to cause the target system message to be displayed on the session interface. In some embodiments, step 402 may be performed by update module 230.

For example, as shown in fig. 7A, after a user inputs a session request via the interactive terminal, the system message portion of the message body may be updated, and the triggering module 210 may trigger the interactive terminal to present the session interface 121-1 based on the updated message body. The session interface 121-1 may display a target system message sent by the quiz robot small U, e.g., "Hi, i am an intelligent customer service small U. Please ask what can help to you? "," little U guesses you want to ask: 1. film print 2. Film print color difference … …', etc. The user can select corresponding requirements or send own requirements according to the system message part sent by the small question-answering robot U.

In step 403, in response to the session request, it is determined whether the user has a history message. In some embodiments, step 403 may be performed by determination module 240.

The history message may refer to a user's past interaction message with the question-answering robot. In some embodiments, in response to the session request, the determination module 240 may determine whether the user has a history message by determining whether the user is a newly registered user. In some embodiments, in response to the session request, the determination module 240 may determine whether the user has a history message via a history message database. For example, the determining module 240 may determine whether a history message of the user exists in the history message database 131 based on identity information of the user (e.g., an identification number, a social security number, a unique identification number of the user in the session interaction system, etc.), and further determine whether the history message exists for the user.

In some embodiments, in response to the session request, the determination module 240 may determine whether a user has a history message based on the data body. Illustratively, when a user begins a session, the determination module 240 may read the user's history message with the question and answer robot from the history message database 131 and update the history message part based on the read history message. Further, the determining module 240 may determine whether the user has a history message based on the current data body. For example, since the history message part, the system message part and the current session message part are arranged in sequence in the data body, if only the system message part is included in the message body or the first message is a system message, it is indicated that the user has no history message. The first message may be a first message ordered in the data volume, e.g., a first message appearing in the data volume.

Step 404 may be performed in response to a determination that the user has a history message. Step 407 may be performed in response to a determination that the user does not have a history message.

And step 404, triggering the interactive terminal to display a historical message loading prompt. In some embodiments, step 404 may be performed by the trigger module 210.

The history message loading hint may be a hint that prompts the user to choose whether to load the history message. In some embodiments, the historical message loading hints may be represented in a variety of ways, e.g., text, pictures, speech, etc. As shown in FIG. 7B, the text "drop-down load history message" is displayed in the session interface 121-2 as a history message load hint. The loading hints for a variety of different historical messages may be preset in advance for storage in storage device 130. In some embodiments, the form of the historical message loading hints corresponding to different users may be different. For example, when the user is the elderly over 60 years old, the triggering module 210 may trigger the interactive terminal to display a history message loading prompt with large text font or voice. And when the judging result of whether the historical message exists by the user is negative, the message loading prompt is not displayed on the session interface of the interactive terminal.

Step 405 may be performed when a user enters a history message load instruction. The history message load instruction may be entered in various ways. For example, when the history message loading hint is "pull down load history message", the user may input the history message loading instruction through the pull down screen. For another example, the user may issue a voice "load history message", "yes" or the like to input a history message load instruction. In some embodiments, the user may enter multiple historical message load instructions. For example, the user may pull down the screen 2 times to enter the history information load instruction twice.

In response to the history message load instruction, a target history message is obtained based on the history message database, step 405. In some embodiments, step 405 may be performed by the acquisition module 220.

In some embodiments, the target history message may include all or part of the user's history message. For example, the target history message may include N (e.g., 10, etc.) history messages closest to the current session, etc. The obtaining module 220 may set the value of N according to the actual requirement, for example, N is 10, 15, etc. In some embodiments, as described in part in FIG. 1, the history messages in the history message database 131 are stored in a one-to-one manner. The targeted history message may include a specific number of user history question and history reply pairs. For example, the targeted history message may include 10 pairs of history questions and history replies for the user. The obtaining module 220 obtains 10 pairs of history questions and history replies each time the user inputs a history message load instruction. Only a specific number of target history messages are loaded and/or the target history messages are loaded in batches, so that the response speed can be improved, and the loading requirement can be met. In some embodiments, the targeted history message may include at least one pair of a history question and a valid history reply. For example, the target history message will only include the history question and its corresponding valid history reply. The invalid replies, praise, click, evaluation, system messages and the like can not be loaded, invalid information can be filtered, and the consulting efficiency and the use experience of a user are improved.

In some embodiments, the target history message does not include the current session message. For example, each session of a user has a corresponding digital identification framework (openID) as an identification of the session. Let the openID of the current session be a. The obtaining module 220 may be configured to distinguish whether the different message belongs to the current session or the history session through the openID, and only select the history message contained in the history session with the openID not being a as the target history message. For the generated messages in the current session (e.g., user messages sent by the user, system replies, etc.), the user is already familiar with, and if the current session message reappears in the target history message, the user experience with the question-and-answer applet and the efficiency of querying the target history message are reduced.

In some embodiments, the retrieval module 220 may retrieve the target historical message by querying a historical message database. In some embodiments, the retrieval module 220 may retrieve the target history message based on the message body. For example, when a user begins a session, the acquisition module 220 may read a target history message for the user and the session robot from a history message database and update the history message portion based on the read target history message. When a subsequent user selects to load the history message, the retrieval module 220 may retrieve the target history message directly from the history message portion. By acquiring the history message in advance to update the message body and loading the target history message based on the updated message body, the efficiency of loading the history message can be improved.

In some embodiments, when the acquisition module 220 acquires the target history message, the session interface may be located to the last 1 of the target history messages (i.e., the 1 history message closest to the current point in time among the target history messages). The user may view other history messages in chronological order by scrolling up. The user is facilitated to review from the 1 historical message closest to the current point in time. Also, with this design, the scrolling height does not need to be calculated when the screen is positioned.

In some embodiments, the acquisition module 220 may have network anomalies in the process of acquiring the target history message. For example, the acquisition module 220 may determine whether the network is abnormal. In response to the determination result of the network anomaly, the triggering module 210 may trigger the interactive terminal to display an anomaly prompt describing the failure of the history message. Optionally, the triggering module 210 may confirm with the user whether to switch accounts. When the user selects to switch account operation, the system is initialized to resume the session. When the user refuses to switch the account, the session interaction is ended. Step 406 may be performed in response to a determination that the network is normal.

Step 406, based on the target history message, updating the history message portion to cause the target history message to be displayed on the session interface. In some embodiments, step 406 may be performed by update module 230.

In some embodiments, the update module 230 may add the target history message to the history message portion to cause the target history message to be displayed on the session interface. For example, as shown in FIG. 7C, the upper half of the session interface 121-3 may display a message including the target history. In some embodiments, when the user inputs the message load instruction multiple times, the obtaining module 220 may obtain the target history message multiple times, the updating module 230 may update the history message portion multiple times, and the target history message may be displayed multiple times on the session interface. For example, after the user performs the pull-down operation for the first time, the obtaining module 220 may obtain the 10-item target history message, and the session interface may display the 10-item target history message. After the 2 nd pull-down operation, the obtaining module 220 may obtain the 10-item target history message again, and the session interface may display the 20-item target history message in total. The 10-item target history message acquired again may be the 10-item target history message closest to the time point of the 10-item target history message acquired 1 st time.

Step 407 may be performed when the user does not input a history message load instruction, but rather a question. Step 407, in response to the user question, obtaining a question reply. In some embodiments, step 407 may be performed by the acquisition module 220.

The user question may refer to a question that the user presents to the question answering robot that requires consultation. For example, as shown in fig. 7D, the user question may be "CT check result is already out? ".

A question reply may refer to a reply to a user question. For example, as shown in fig. 7D, the question reply of the question answering robot to the user question may be "result out, is film printed? If print, please click the "film print" button, etc. In some embodiments, when the question answering robot is unable to answer the user's question, the question answer may be a system default answer, e.g., "no play, small U is still learning, temporarily unable to answer your question.

In some embodiments, the user questions and the questions replies in a one-to-one correspondence. The user question may have a first ID number and the corresponding question reply has a second ID number, the first and second ID numbers having a correspondence. Alternatively, the user question and the corresponding question reply may have the same ID number. Multiple user questions and multiple question replies may be included during a session interaction. The acquisition module 220 may associate these user questions and question replies one to one. In some embodiments, for a user to ask a question, the corresponding question reply may include 1 or more pieces of information. Each of the 1 or more pieces of information is a question reply to the user's question, and may have the same second ID number, for example. In some embodiments, the question reply to the user question may include a large amount of information that is not suitable for direct display to the conversation interface. The quiz response may be displayed in the form of a fold, link, etc. The user may click on the expand question reply or click on a link to jump to a new page to view the question reply.

In some embodiments, in response to a user question, the acquisition module 220 may acquire a question reply in a variety of ways. For example, the acquisition module 220 may acquire the questioning response via the questioning response database 132. For example, the obtaining module 220 may obtain the same or similar questions through the question and answer database based on the user questions, and determine replies corresponding to the same or similar questions as question replies. For another example, in response to a user question, the acquisition module 220 may acquire a question reply over a network. Illustratively, the user question is "CT check out result has come out? The acquiring module 220 may determine whether the user's inspection result exists among the inspection results of the CT apparatus through the network. When there is a check result of the user, the corresponding question reply may be "result out, is film printed? If print, please click the "film print" button. When the checking result of the user does not exist, the corresponding question reply can be "the checking result is not coming out temporarily, please wait for your patience". In some embodiments, the retrieval module 220 may query a question and answer database or search network to retrieve a question and answer based on the user question in a fuzzy matching manner. When a corresponding question reply is matched, the retrieval module 220 may mark the reply-type field tag, e.g., as a valid reply. When a quiz reply is not matched, the retrieval module 220 may flag the reply type field, e.g., as an invalid reply. The relevant content for valid replies and invalid replies may be found in the relevant description of step 409.

During the interactive session between the user and the question-answering robot, there may be a network anomaly. In some embodiments, the acquisition module 220 may determine whether the network is abnormal. And further, different processing methods are determined according to different judging results (such as abnormal and normal) of the network. In response to the determination of the network anomaly, the triggering module 210 may trigger the interactive terminal to display a message anomaly prompt. In response to the determination that the network is normal, the obtaining module 220 may obtain a challenge response.

Message anomaly prompting may refer to a message prompting a user that the network is currently anomalous. For example, a message anomaly is presented as a word of "network anomaly", or the like. For another example, a red exclamation mark may be displayed near a message box corresponding to a question sent by the user, indicating that the message was sent failed, and the question answering robot will not answer the question. When the user clicks the text or icon of "network anomaly", the corresponding "network anomaly" disappears, and the current session message part deletes the question. When the network is restored, the trigger module 210 may re-add the user question at the forefront of the message portion of the current session.

When the network is normal, the triggering module 210 may trigger the interactive terminal to display a word or icon of "in-process" in the session interface, etc. The acquisition module 220 may acquire the questioning response via the questioning response database 132 or the like. When the acquiring module 220 acquires the corresponding question reply, the text or icon of "in input" disappears.

In some embodiments, the acquisition module 220 may determine whether the network is abnormal by asking if the robot is asking for a reply within a time threshold. The time threshold may refer to the maximum time for which the quiz robot replies to the user's quiz. For example, the time threshold is 3 seconds, etc. When the user asks, the question-answering robot does not answer the question within the time threshold, and the obtaining module 220 may determine a determination result of the network abnormality. In some embodiments, the acquisition module 220 may analyze the connection state of the interactive terminal 120 and the processing device 110, thereby determining whether the network is abnormal.

Based on the questioning reply, the current session message portion is updated to cause the questioning reply to be displayed on the session interface, step 408. In some embodiments, step 408 may be performed by update module 230.

In some embodiments, the update module 230 may add the challenge reply to the current session message portion to cause the challenge reply to be displayed on the session interface. For example, as shown in FIG. 7D, the session interface 121-4 may display a question reply.

Step 409, determining whether the questioning reply includes a valid reply. In some embodiments, step 409 may be performed by determination module 240.

In some embodiments, the question replies may include valid replies or invalid replies, etc. A valid reply may refer to a reply that can solve a user's question. In some embodiments, the determination module 240 may determine whether it is a valid reply or an invalid reply based on the type of the questioning reply. If the questioning reply is a reply obtained by a search on a questioning reply database or network, the questioning reply is a valid reply. If the quiz reply is a default system reply, such as "little U is still learning, temporarily unable to answer your question," the quiz reply is an invalid reply. If the questioning reply is praise, click, evaluation, etc., the questioning reply is an invalid reply.

In some embodiments, the determination module 240 may determine whether a valid response is included in the questioning response based on the user's feedback of the questioning response. For example, an evaluation option may be displayed on the session interface for the user to evaluate for the validity of the quiz response. If the user provides a positive evaluation of the questioning reply, the questioning reply may be judged to be a valid reply. For another example, if the user sends a reply message such as "good, clear", "know", etc. after receiving the quiz reply, the determination module 240 may determine the quiz reply as a valid reply. If the user's reply message is "I am not this," "does not understand your meaning," etc., the determination module 240 may determine the quiz reply as an invalid reply.

In step 410, in response to the determination that the questioning response includes a valid response, the user questioning and questioning response pair is stored in the history message database. In some embodiments, step 410 may be performed by determination module 240.

By matching the user question and the effective question reply and storing the matched user question and the effective question reply in the historical message database, the invalid data can be prevented from occupying the storage space, so that the storage space of the data is saved, and the management and retrieval efficiency of the follow-up data can be improved. For example, when a subsequent user selects to load the history information, the user question and the corresponding effective question reply can be quickly searched from the history database, so that the efficiency of the user for referring to the history information and the experience of the user for using the question-answering robot can be improved.

Possible benefits of embodiments of the present description include, but are not limited to: (1) In some embodiments of the present description, the message body may be utilized to store historical messages, system messages, current session messages, etc., involved in the user's session with the question-answering robot. Because the messages in the message body are stored based on the preset arrangement mode, the processing device 110 can quickly locate the messages and determine the display content of the session interface based on the message body, without acquiring the messages of different types from different sources. In addition, the processing device 110 can uniformly process and manage the related data of the session interaction, so that the data structure can be flexibly adjusted, and the storage and management efficiency of the data can be improved. In the conventional session interaction method, because different messages correspond to different message sources or categories, and the user questions and the system replies are stored separately, the associated messages need to be logically associated. In the session, different sources need to be used to retrieve different information, and logic judgment needs to be performed to find the associated data. Compared with the traditional session interaction method, the session interaction method based on the message body has higher data management and storage efficiency, and further can provide better session service. (2) Different target system messages are acquired aiming at different users, so that a session interface displays the target system messages, the users can acquire the required system messages, and the use physical examination of the users using the question-answering applet is improved. (3) By arranging the history message part 510, the system message part 520, and the current session message part 530 in a preset order, it is possible to help to quickly distinguish and locate messages, and to improve data management and control efficiency. (4) In some embodiments, the targeted history message will include only the history question and its corresponding valid history reply. The invalid replies, praise, click, evaluation, system messages and the like can not be loaded, invalid information can be filtered, and the consulting efficiency and the use experience of a user are improved. (5) The user may view other history messages in chronological order by scrolling up. The user is facilitated to review from the 1 historical message closest to the current point in time. Also, with this design, the scrolling height does not need to be calculated when the screen is positioned. (6) By matching the user question and the effective question reply and storing the matched user question and the effective question reply in the historical message database, the invalid data can be prevented from occupying the storage space, so that the storage space of the data is saved, and the management and retrieval efficiency of the follow-up data can be improved. For example, when a subsequent user selects to load the history information, the user question and the corresponding effective question reply can be quickly searched from the history database, so that the efficiency of the user for referring to the history information and the experience of the user for using the question-answering robot can be improved.

It should be noted that the above description of the flow is only for the purpose of illustration and description, and does not limit the application scope of the present specification. Various modifications and changes to the flow may be made by those skilled in the art under the guidance of this specification. However, such modifications and variations are still within the scope of the present description.

While the basic concepts have been described above, it will be apparent to those skilled in the art that the foregoing detailed disclosure is by way of example only and is not intended to be limiting. Although not explicitly described herein, various modifications, improvements, and adaptations to the present disclosure may occur to one skilled in the art. Such modifications, improvements, and modifications are intended to be suggested within this specification, and therefore, such modifications, improvements, and modifications are intended to be included within the spirit and scope of the exemplary embodiments of the present invention.

Meanwhile, the specification uses specific words to describe the embodiments of the specification. Reference to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic is associated with at least one embodiment of the present description. Thus, it should be emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various positions in this specification are not necessarily referring to the same embodiment. Furthermore, certain features, structures, or characteristics of one or more embodiments of the present description may be combined as suitable.

Furthermore, the order in which the elements and sequences are processed, the use of numerical letters, or other designations in the description are not intended to limit the order in which the processes and methods of the description are performed unless explicitly recited in the claims. While certain presently useful inventive embodiments have been discussed in the foregoing disclosure, by way of various examples, it is to be understood that such details are merely illustrative and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover all modifications and equivalent arrangements included within the spirit and scope of the embodiments of the present disclosure. For example, while the system components described above may be implemented by hardware devices, they may also be implemented solely by software solutions, such as installing the described system on an existing server or mobile device.

Likewise, it should be noted that in order to simplify the presentation disclosed in this specification and thereby aid in understanding one or more inventive embodiments, various features are sometimes grouped together in a single embodiment, figure, or description thereof. This method of disclosure, however, is not intended to imply that more features than are presented in the claims are required for the present description. Indeed, less than all of the features of a single embodiment disclosed above.

In some embodiments, numbers describing the components, number of attributes are used, it being understood that such numbers being used in the description of embodiments are modified in some examples by the modifier "about," approximately, "or" substantially. Unless otherwise indicated, "about," "approximately," or "substantially" indicate that the number allows for a 20% variation. Accordingly, in some embodiments, numerical parameters set forth in the specification and claims are approximations that may vary depending upon the desired properties sought to be obtained by the individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and employ a method for preserving the general number of digits. Although the numerical ranges and parameters set forth herein are approximations that may be employed in some embodiments to confirm the breadth of the range, in particular embodiments, the setting of such numerical values is as precise as possible.

Each patent, patent application publication, and other material, such as articles, books, specifications, publications, documents, etc., referred to in this specification is incorporated herein by reference in its entirety. Except for application history documents that are inconsistent or conflicting with the content of this specification, documents that are currently or later attached to this specification in which the broadest scope of the claims to this specification is limited are also. It is noted that, if the description, definition, and/or use of a term in an attached material in this specification does not conform to or conflict with what is described in this specification, the description, definition, and/or use of the term in this specification controls.

Finally, it should be understood that the embodiments described in this specification are merely illustrative of the principles of the embodiments of this specification. Other variations are possible within the scope of this description. Thus, by way of example, and not limitation, alternative configurations of embodiments of the present specification may be considered as consistent with the teachings of the present specification. Accordingly, the embodiments of the present specification are not limited to only the embodiments explicitly described and depicted in the present specification.

Claims

1. A method of session interaction, the method comprising:

responding to a session request input by a user through an interactive terminal, triggering the interactive terminal to present a session interface, wherein the display content of the session interface is determined based on a message body, and the message body comprises a history message part, a system message part and a current session message part;

responding to the session request, and acquiring a target system message; and

updating the system message portion based on the target system message to cause the target system message to be displayed on the session interface;

acquiring an interaction instruction input by the user through the interaction terminal;

updating the message body in response to the interaction instruction;

and triggering the interactive terminal to update the session interface based on the updated message body.

2. The session interaction method according to claim 1, characterized in that the method further comprises:

responding to the session request, judging whether the user has a history message or not;

and responding to the judging result of the historical information of the user, and triggering the interactive terminal to display a historical information loading prompt.

3. The session interaction method according to claim 2, wherein the interaction instruction comprises a history message loading instruction, the method further comprising:

responding to the history message loading instruction, and acquiring a target history message based on a history message database;

and updating the history message part based on the target history message so as to display the target history message on the session interface.

4. A session interaction method according to claim 3, wherein the target history message comprises at least one pair of a history question and a valid history reply.

5. The session interaction method according to claim 1, wherein the interaction instruction includes a user question, the method further comprising:

responding to the user question, and acquiring a question reply; and

and updating the current session message part based on the questioning reply so as to display the questioning reply on the session interface.

6. The session interaction method according to claim 5, characterized in that the method further comprises:

judging whether the questioning reply comprises a valid reply or not;

and responding to the judging result that the questioning reply comprises the effective reply, and storing the user questioning and the questioning reply pairing in a historical message database.

7. The session interaction method according to claim 1, wherein the history message part, the system message part and the current session message part are arranged based on a preset order.

8. A conversational interaction system, the system comprising:

the system comprises a triggering module, a display module and a display module, wherein the triggering module is used for responding to a session request input by a user through an interactive terminal, triggering the interactive terminal to present a session interface, and determining the display content of the session interface based on a message body, wherein the message body comprises a history message part, a system message part and a current session message part;

the acquisition module is used for responding to the session request and acquiring a target system message;

an updating module, configured to update the system message part based on the target system message, so that the target system message is displayed on the session interface;

The acquisition module is further used for acquiring an interaction instruction input by the user through the interaction terminal;

the updating module is further used for responding to the interaction instruction and updating the message body;

and the triggering module is used for triggering the interactive terminal to update the session interface based on the updated message body.

9. A computer readable storage medium storing computer instructions which, when executed by a processor, implement the session interaction method of any of claims 1 to 7.