Bill service processing method and device based on intelligent agent

Abstract

The embodiment of the invention provides an agent-based bill service processing method and device, and the method comprises the steps: receiving interaction data transmitted by a user terminal after the user terminal enters a bill service in the operation process of the bill service, and calling a bill agent of the bill service based on the interaction data to carry out bill processing, inputting the interaction data into a task generation model corresponding to the intention category of the interaction data by the bill agent to generate a task sequence for carrying out bill processing, and executing the task sequence to obtain a bill processing result. And generating service response data according to a bill processing result returned by the bill intelligent agent, and sending the service response data to the user terminal, thereby helping the user to perform bill processing through the bill intelligent agent in the process of using the bill service by the user.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a method and device for processing ticket services based on an intelligent agent. Background Art

[0002] With the continuous development of Internet technology and the continuous improvement of computer technology, the application scope of online services is becoming wider and wider. More and more users are beginning to use corresponding functions through online services in their daily lives. For example, users can process electronic invoices through online services. However, as the number of electronic invoices continues to rise, how to better process electronic invoices through online services has become a key issue of concern to all parties. Summary of the invention

[0003] One or more embodiments of the present specification provide a method for processing a ticket service based on an agent, including: receiving interaction data sent by a user terminal after entering a ticket service. Based on the interaction data, calling the ticket agent of the ticket service to perform ticket processing. The ticket processing includes inputting the interaction data into a task generation model corresponding to the intent category of the interaction data to generate a task sequence for ticket processing, and executing the task sequence to obtain a ticket processing result. Obtaining the ticket processing result returned by the ticket agent, generating service response data based on the ticket processing result and sending it to the user terminal.

[0004] One or more embodiments of the present specification provide another agent-based ticket service processing method, including: obtaining interactive data submitted by a user on an interactive page of a ticket service. Sending the interactive data to a server to call a ticket agent to perform ticket processing. The ticket processing includes inputting the interactive data into a corresponding task generation model to obtain a task sequence for ticket processing and executing the task sequence to obtain a ticket processing result. Receiving service response data generated and sent by the server according to the ticket processing result, and displaying it on the interactive page.

[0005] One or more embodiments of the present specification provide a ticket service processing device based on an intelligent agent, including: an interactive data receiving module, configured to receive interactive data sent by a user terminal after entering a ticket service. A ticket agent calling module, configured to call the ticket agent of the ticket service to perform ticket processing based on the interactive data. The ticket processing includes inputting the interactive data into a task generation model corresponding to the intent category of the interactive data to generate a task sequence for ticket processing, and executing the task sequence to obtain a ticket processing result. A service response data generation module, configured to obtain the ticket processing result returned by the ticket agent, generate service response data based on the ticket processing result, and send it to the user terminal.

[0006] One or more embodiments of the present specification provide another agent-based ticket service processing device, including: an interactive data acquisition module, configured to acquire interactive data submitted by a user on an interactive page of a ticket service. An interactive data sending module, configured to send the interactive data to a server to call a ticket agent for ticket processing. The ticket processing includes inputting the interactive data into a corresponding task generation model to obtain a task sequence for ticket processing and executing it to obtain a ticket processing result. A service response data receiving module, configured to receive service response data generated and sent by the server according to the ticket processing result, and display it on the interactive page.

[0007] One or more embodiments of the present specification provide an agent-based ticket service processing device, including: a processor; and a memory configured to store computer-executable instructions, wherein when the computer-executable instructions are executed, the processor: receives interaction data sent by a user terminal after entering a ticket service. Based on the interaction data, the ticket agent of the ticket service is called to perform ticket processing. The ticket processing includes inputting the interaction data into a task generation model corresponding to the intent category of the interaction data to generate a task sequence for ticket processing, and executing the task sequence to obtain a ticket processing result. The ticket processing result returned by the ticket agent is obtained, and service response data is generated according to the ticket processing result and sent to the user terminal.

[0008] One or more embodiments of the present specification provide another agent-based ticket service processing device, including: a processor; and a memory configured to store computer executable instructions, wherein when the computer executable instructions are executed, the processor: obtains the interaction data submitted by the user on the interactive page of the ticket service. The interaction data is sent to the server to call the ticket agent to perform ticket processing. The ticket processing includes inputting the interaction data into the corresponding task generation model to obtain the task sequence for ticket processing and executing it to obtain the ticket processing result. The service response data generated and sent by the server according to the ticket processing result is received, and displayed on the interactive page.

[0009] One or more embodiments of the present specification provide a computer-readable storage medium for storing computer-executable instructions, which implement the following process when executed: receiving interaction data sent by a user terminal after entering a ticket service. Based on the interaction data, calling the ticket agent of the ticket service to perform ticket processing. The ticket processing includes inputting the interaction data into a task generation model corresponding to the intent category of the interaction data to generate a task sequence for ticket processing, and executing the task sequence to obtain a ticket processing result. Obtaining the ticket processing result returned by the ticket agent, generating service response data based on the ticket processing result and sending it to the user terminal.

[0010] One or more embodiments of the present specification provide another computer-readable storage medium for storing computer-executable instructions, which implement the following process when executed: obtaining interactive data submitted by a user on an interactive page of a ticket service. Sending the interactive data to a server to call a ticket agent to perform ticket processing. The ticket processing includes inputting the interactive data into a corresponding task generation model to obtain a task sequence for ticket processing and executing the task sequence to obtain a ticket processing result. Receive service response data generated and sent by the server according to the ticket processing result, and display it on the interactive page. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate one or more embodiments of the present specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present specification. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative labor. Figure 1 A schematic diagram of an implementation environment of an agent-based ticket service processing method provided for one or more embodiments of this specification; Figure 2 A processing flow chart of a ticket service processing method based on an intelligent agent provided in one or more embodiments of this specification; Figure 3 A schematic diagram of an interactive page of a first ticket service provided for one or more embodiments of this specification; Figure 4 A schematic diagram of an interactive page of a second ticket service provided in one or more embodiments of this specification; Figure 5 A schematic diagram of an interactive page of a third ticket service provided in one or more embodiments of this specification; Figure 6A schematic diagram of a code scanning page for a ticket service provided in one or more embodiments of this specification; Figure 7 A processing flow chart of an agent-based bill service processing method applied to a bill reimbursement scenario provided in one or more embodiments of this specification; Figure 8 A processing flow chart of an agent-based bill service processing method applied to a bill application scenario provided by one or more embodiments of this specification; Fig. 9 A processing flow chart of another agent-based ticket service processing method provided for one or more embodiments of this specification; Fig.10 A schematic diagram of an embodiment of an agent-based ticket service processing device provided for one or more embodiments of this specification; Fig.11 A schematic diagram of another embodiment of an agent-based ticket service processing device provided for one or more embodiments of the present specification; Fig.12 A schematic diagram of the structure of an agent-based ticket service processing device provided for one or more embodiments of this specification; Fig.13 A schematic diagram of the structure of another agent-based ticket service processing device provided for one or more embodiments of this specification. DETAILED DESCRIPTION

[0012] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0013] The agent-based ticket service processing method provided in one or more embodiments of this specification can be applied to the implementation environment of ticket service operation. Figure 1 , the implementation environment at least includes: User terminal 101 of the user, server 102 of the ticket service, ticket agent 103 of the ticket service; The user terminal 101 of the user is used to access the ticket service, send interaction data to the server 102, receive service response data sent by the server 102, and display the service response data; further, the user terminal 101 can also install a client of the ticket service, which can be an application, or a subroutine of the application, or a service module of the application; the user terminal 101 of the user can specifically be a mobile phone, a personal computer, a tablet computer, an e-book reader, a device for information interaction based on VR (Virtual Reality, virtual reality technology), a vehicle terminal, an IoT device, a wearable smart device, a laptop portable computer and a desktop computer, etc.; The server 102 of the bill service is used to receive the interactive data sent by the user terminal 101, call the bill agent 103 based on the interactive data, generate service response data according to the bill processing result returned by the bill agent 103, and send it to the user terminal 101. Specifically, the payment server 102 can be a server, or a server cluster composed of several servers, or one or more cloud servers in a cloud computing platform.

[0014] The bill agent 103 of the bill service is used to input the interaction data into the task generation model corresponding to the intention category of the interaction data to generate a task sequence, and execute the task sequence to obtain the bill processing result; multiple task generation models can be configured or connected to the bill agent 103, and the task sequence for bill processing is generated by the task generation model; the bill agent 103 can be deployed independently, and the server 102 interacts with the bill agent 103 by calling. The bill agent 103 can be deployed in a server, or in a server cluster composed of several servers, or in one or more cloud servers in a cloud computing platform. In addition, the bill agent 103 can also be deployed inside the server 102.

[0015] In this implementation environment, the user terminal 101 obtains the interaction data submitted by the user in the ticket service and sends it to the server 102. The server 102 calls the ticket agent 103 of the ticket service to perform ticket processing based on the interaction data. The ticket agent 103 generates a task sequence for ticket processing in response to the call to input the interaction data into the task generation model corresponding to the intention category of the interaction data, executes the task sequence to obtain the ticket processing result and returns it to the server 102. The server 102 generates service response data based on the ticket processing result and sends it to the user terminal 101. The user terminal 101 displays the service response data on the ticket service, thereby helping the user to process the ticket by calling the agent during the user's use of the ticket service.

[0016] One or more embodiments of a ticket service processing method based on an intelligent agent provided in this specification are as follows: Reference Figure 2 The present embodiment provides an agent-based ticket service processing method, which specifically includes steps S202 to S206.

[0017] Step S202, receiving interaction data sent by the user terminal after entering the ticket service.

[0018] The ticket service described in this embodiment may be a service related to electronic tickets. Users may access the ticket service to process tickets. The ticket service may be a ticket application. The ticket service may also be a ticket subroutine or a ticket service module of an application. Alternatively, the ticket service may be provided to users in the form of a ticket application, a subroutine of a ticket application, and / or a service module of a ticket application. In addition, the ticket service may also be provided through an application and / or a subroutine of an application. The ticket service may provide multiple different functions, and users may use these functions in the ticket service.

[0019] For example, users can use the bill application function in the bill service to apply for electronic bills, users can also use the bill collection function in the bill service to collect electronic bills, users can also use the bill sorting function in the bill service to sort or query electronic bills, and users can also use the bill reimbursement function in the bill service to reimburse electronic bills; in addition, users can also use the question and answer function in the bill service to ask bill-related questions.

[0020] Specifically, the ticket service can be configured with a ticket agent, and the ticket service can perform ticket processing through the ticket agent to cooperate with the implementation of the functions of the ticket service. The ticket agent can perform corresponding ticket processing based on the interaction data submitted by the user; the interaction data is the data submitted by the user in the ticket service to describe the user's needs for ticket processing, which can be used as the calling input of the ticket agent. The ticket agent can select a task generation model based on the intention category of the interaction data. The interaction data may include interaction data entered and submitted by the user, and may also include preset interaction data triggered and submitted by the user; optionally, the interaction data includes interaction text and / or interaction voice.

[0021] Among them, the bill agent refers to an agent connected to the bill service, or an agent configured in the bill service. The bill agent can cooperate with the bill service to realize the function of the bill service. The bill agent can be deployed outside the bill service or in the bill service. The bill agent can be configured with multiple task generation models, or the bill agent can be connected to multiple task generation models. The task generation model can generate a task sequence for bill processing. The task generation model can correspond to the intent category of the interaction data. The bill agent can determine the task generation model to be called based on the interaction data to generate a task sequence for bill processing. In addition, the task generation model can correspond to the function of the bill service to generate a task sequence for bill processing. Optionally, the intent category includes: bill reimbursement intent, bill sorting intent, bill collection intent and / or bill application intent.

[0022] For example, the task generation model corresponding to the bill reimbursement intent can generate a task sequence for bill reimbursement, and the bill agent executes the task sequence to generate a reimbursement form for the electronic bill; the task generation model corresponding to the bill sorting intent can generate a task sequence for bill sorting, and the bill agent executes the task sequence to query the bill information of the electronic bill; the task generation model corresponding to the bill collection intent can generate a task sequence for bill collection, and the bill agent executes the task sequence to add the electronic bill to the user's bill collection; the task generation model corresponding to the bill application intent can generate a task sequence for bill application, and the bill agent executes the task sequence to apply for the user's electronic bill.

[0023] In addition, the bill agent can also be connected to the large language model to cooperate with the bill service to realize the question and answer function of the bill service; optionally, the bill processing includes inputting the interaction data into the large language model for bill processing to obtain the bill processing result; for example, when the user asks questions related to the bill, the bill agent can call the large language model to generate a reply text.

[0024] In specific implementation, when a user accesses the ticket service, the user can interact in the ticket service by submitting interactive data to use the functions of the ticket service. For this purpose, a preset interactive text can be configured in the ticket service, and the user can trigger and submit the preset interactive text to be sent through the user terminal, thereby improving the convenience of interaction. In an optional implementation manner provided in this embodiment, the interactive data is obtained in the following manner: The preset interactive text triggered and submitted by the user on the interactive page of the ticket service is obtained, and the preset interactive text is used as the interactive data. Optionally, the preset interactive text is generated according to the ticket information of the electronic ticket to be reimbursed in the user's ticket collection.

[0025] Specifically, the user can trigger the interface corresponding to the preset interactive text on the interactive page of the ticket service, and submit the preset interactive text after triggering the interface, so that the user terminal sends the preset interactive text as interactive data to the server. Figure 3 As shown, the user can trigger the button 301 corresponding to "Help me sort out the tickets for [X month X city]", and after triggering the button 301, submit "Help me sort out the tickets for [X month X city]" as the interaction data. Optionally, the interaction data includes a preset interaction text triggered and submitted by the user on the interaction page of the ticket service.

[0026] In addition, when a user accesses the ticket service, the user may also enter and submit interactive data in the ticket service to be sent to the server through the user terminal; in another optional implementation provided by this embodiment, the interactive data is submitted after the user enters it on the interactive page of the ticket service. Optionally, the interactive data includes the interactive data entered by the user on the interactive page of the ticket service. For example, Figure 3 As shown, the user can input interactive text in the input box 302 and submit the interactive text after triggering the "Send" button.

[0027] In addition, before receiving the interactive data, a preset interactive text can be generated in advance according to the bill information of the electronic bill to be reimbursed in the user's bill collection, so that the user can trigger the interface of the preset interactive text and submit the interactive data, thereby improving the convenience of interaction; in an optional implementation provided by this embodiment, before receiving the interactive data, it also includes: generating a preset interactive text according to the bill information of the electronic bill to be reimbursed in the user's bill collection. Specifically, the user's intention category can be predicted according to the bill information of the electronic bill to be reimbursed in the user's bill collection, and the preset interactive text can be generated according to the predicted intention category and the bill information.

[0028] In specific implementation, the interactive data submitted by the user on the interactive page of the ticket service is obtained through the user terminal. After the interactive data is obtained, the user terminal sends the interactive data. Correspondingly, the interactive data sent by the user terminal after entering the ticket service is received here.

[0029] Step S204: Calling the ticket agent of the ticket service to perform ticket processing based on the interaction data.

[0030] In a specific implementation, the ticket agent of the ticket service is called based on the interaction data sent by the user terminal to perform ticket processing. Accordingly, the ticket agent of the ticket service determines the intent category of the interaction data in response to the agent call, selects a task generation model corresponding to the intent category, inputs the interaction data into the task generation model to generate a task sequence for ticket processing, and executes the task sequence to obtain the ticket processing result. Optionally, the ticket processing includes inputting the interaction data into the task generation model corresponding to the intent category of the interaction data to generate a task sequence for ticket processing, and executing the task sequence to obtain the ticket processing result.

[0031] Specifically, in the process of calling the bill intelligent body, the interactive data can be used as the calling input of the bill intelligent body to call the bill intelligent body. Specifically, the application programming interface (Application Programming Interface, API) of the bill intelligent body can be called based on the interactive data to send the interactive data to the bill intelligent body.

[0032] After the above-mentioned ticket agent is called based on the interactive data sent by the user terminal, the ticket agent of the ticket service responds to the call and performs ticket processing. During the specific execution process, the corresponding task generation model can be called according to the interactive data to obtain the task sequence for ticket processing and execute it, and obtain the ticket processing result, so as to use the ticket processing result as the return result of the agent call; optionally, the ticket processing includes inputting the interactive data into the corresponding task generation model to obtain the task sequence for ticket processing and execute it, and obtain the ticket processing result.

[0033] Specifically, in the process of determining the task generation model, the bill intelligent agent can extract the intention category of the interaction data, and select the task generation model corresponding to the intention category from the multiple connected task generation models. Specifically, the intention category can be preset for the task generation model in advance, and the intention category obtained based on the intention recognition of the interaction data is matched with the preset intention category, and the task generation model is determined according to the matching result; alternatively, the task generation model can also correspond to the interaction data, and the bill intelligent agent determines the task generation model according to the interaction data.

[0034] The bill processing result is the execution result of the bill agent after executing the task sequence for bill processing, which is used to characterize the result of bill processing; the task generation model can also correspond to different functions of the bill service, and accordingly, the generated task sequence can also correspond to different functions, and the bill processing result can also correspond to different functions. Specifically, the bill processing result can include different data. Optionally, the bill processing result includes: reimbursement form data of the reimbursement form, bill information of the electronic bill and / or bill data of the bill; in addition, the bill processing result can also include a reply text.

[0035] For example, corresponding to the bill reimbursement function, the bill processing result may include a reimbursement form constructed based on the bill information of the electronic invoice and the bill data of the associated bill; corresponding to the bill sorting function, the bill processing result may include the bill information of the queried electronic invoice; corresponding to the bill collection function, the bill processing result may include the bill information of the collected electronic invoice; corresponding to the bill application function, the bill processing result may include the bill information of the applied electronic invoice.

[0036] Specifically, in the process of generating a task sequence, the task generation model can determine the tasks to be configured in the preset task sequence according to the interaction data, and configure the keywords in the interaction data in the corresponding tasks to be configured to obtain a task sequence; in an optional implementation manner provided in this embodiment, generating a task sequence includes: Extract multiple keywords from the interaction data, and select tasks to be configured that match the keywords from the preset task set; Each keyword is configured in its corresponding task to be configured to obtain a plurality of bill processing tasks, and a task sequence is constructed based on the preset execution relationship of the task to be configured and each bill processing task.

[0037] Specifically, during the execution of the task sequence, the bill processing tasks in the task sequence may be read and each bill processing task may be executed according to the execution relationship to obtain the bill processing result; in an optional implementation manner provided by this embodiment, executing the task sequence includes: Read multiple bill processing tasks contained in the task sequence and the execution relationship between the bill processing tasks; Execute each bill processing task according to the execution relationship to obtain the bill processing result.

[0038] In actual scenarios, the task generation model may correspond to different intent categories, or, corresponding to different functions of the bill service, the bill processing required for different intent categories and / or functions may be different, and accordingly, the task sequence generated by the task generation model and the bill processing results obtained by the bill agent executing the task sequence may also be different. For example: the preset task sequence of the task generation model corresponding to the bill reimbursement function may include a query task to be configured, a verification task to be configured, and a reimbursement form generation task to be configured, then the generated task sequence can be expressed as: [query task → verification task → reimbursement form generation task]; the preset task sequence of the task generation model corresponding to the bill application function may include a bill query task to be configured, a bill application task to be configured, and a bill collection task to be configured, then the generated task sequence can be expressed as: [bill query task → bill application task → bill collection task].

[0039] In view of this, specifically during the execution of the task sequence, the task sequence may be executed according to the bill processing task in the task sequence. The following specifically describes the execution process of the task sequences generated by the above four task generation models.

[0040] (1) Execution of the task sequence for bill reimbursement generated by the task generation model corresponding to the bill reimbursement intention In the specific execution process, the task sequence for bill reimbursement may include a query task, a verification task, and a reimbursement form generation task. The query task may be executed to query the electronic bills and bills for reimbursement, the verification task may be executed to verify the electronic bills and bills, and the reimbursement form generation task may be executed to obtain the reimbursement form, which may be used as the bill reimbursement result. In the first optional implementation manner provided in this embodiment, the task sequence is executed, including: Execute the query task in the task sequence to query the electronic receipts matching the keywords in the interaction data in the user's receipt collection and query the bills associated with the electronic receipts; Execute the verification tasks in the task sequence to verify and process electronic receipts and bills according to the reimbursement verification rules; If the verification passes, the reimbursement form generation task in the task sequence is executed to write the bill information of the electronic invoice and the bill data of the bill into the reimbursement form to be configured to obtain the reimbursement form.

[0041] Specifically, firstly, the query task is executed, the keywords contained in the interactive data are extracted, and the electronic invoices matching the keywords in the interactive data are searched in the user's invoice collection, and the bills associated with the electronic invoices are searched in the bill data, and the bill information of the electronic invoice and the bill data of the bill are used as the task execution input of the verification task, and each electronic invoice and bill are verified and processed according to the preset reimbursement verification rules. If the verification fails, no processing is performed, and if the verification passes, the reimbursement form generation task is executed, and the bill information and bill data are written into the reimbursement form to be configured to obtain the reimbursement form; wherein, the electronic invoice matching the keyword can be an electronic invoice matching any keyword, or an electronic invoice matching two or more keywords at the same time. Optionally, the keywords include time keywords, regional keywords and / or merchant keywords.

[0042] For example, execute the query task in the task sequence, query the electronic invoices with an issue time within X months and in X city in the user's invoice collection, and the bills associated with the electronic invoices, execute the verification task to verify each electronic invoice and bill according to the amount verification rules of the user's institution, and execute the reimbursement form generation task after the verification is passed, write the invoice information and bill data of the electronic invoice into the reimbursement form to be configured to obtain the reimbursement form.

[0043] In addition, if the verification fails, the reimbursement form generation task in the task sequence may not be executed, and the message generation task in the task sequence may be executed to generate a verification failure message based on the ticket information and bill data as the ticket reimbursement result; further, the ticket processing result and / or the ticket reimbursement result may also include the reimbursement form and the verification failure message; for example, if the verification passes, the reimbursement form generation task is executed to generate a reimbursement form based on the electronic ticket and bill that have passed the verification; if the verification fails, the message generation task is executed to generate a verification failure message based on the electronic ticket and bill that have failed the verification, and the reimbursement form and the verification failure message are used as the ticket reimbursement result.

[0044] Among them, during the execution of the task sequence for bill reimbursement generated by the task generation model corresponding to the bill reimbursement intention, the subsequent tasks in the task sequence can also be executed directly according to the verification results. For example: after the verification task is executed, the reimbursement form generation task in the task sequence can be executed to write the bill information of the verified electronic invoice and the bill data of the bill into the reimbursement form to be configured to obtain the reimbursement form; or, after the verification task is executed, the message generation task in the task sequence can be executed to generate a verification failure message based on the bill information of the electronic invoice that failed the verification.

[0045] (2) Execution of the task sequence for bill sorting generated by the task generation model corresponding to the bill sorting intention In the specific execution process, the task sequence for bill sorting may include a query task and a sorting task. The query task may be executed to query the electronic bill, and the sorting task may be executed to sort the electronic bill to obtain bill information of the sorted electronic bill, which may be used as the bill sorting result. In the second optional implementation manner provided in this embodiment, the task sequence is executed, including: Execute the query task in the task sequence to query the user's ticket collection for an electronic ticket whose ticket information matches the time information, area information and / or merchant information configured in the query task; Execute the sorting task in the task sequence to sort the electronic invoices obtained by the query according to the sorting method configured by the sorting task, and obtain the invoice information of the sorted electronic invoice.

[0046] Specifically, firstly, the query task in the task sequence is executed, the query keywords in the configuration information of the query task are read, such as time information, area information and / or merchant information, and the electronic receipts matching the keywords are searched in the user's receipt collection, and the sorting task is executed to sort the electronic receipts obtained by the query according to the sorting method configured by the sorting task, and the receipt information of the sorted electronic receipts is obtained; wherein, the electronic receipts matching the keywords may be electronic receipts matching any keyword, or may be electronic receipts matching two or more keywords at the same time. Optionally, the sorting method includes a time sorting method, an amount sorting method and / or a consumption type sorting method.

[0047] For example, execute the query task in the task sequence, read the time information, area information and merchant information in the configuration information of the query task, query the electronic invoices matching the time information, the electronic invoices matching the area information and the electronic invoices matching the merchant information in the user's ticket collection, execute the sorting task to sort the above three electronic invoices obtained by the query according to time, and obtain the ticket information of the sorted electronic invoices.

[0048] (3) Execution of the task sequence for bill application generated by the task generation model corresponding to the bill application intention In the specific execution process, the task sequence for bill application may include a bill query task, a bill application task and a bill collection task. The bill query task may be executed to query the bill, the bill application task may be executed to apply for the electronic bill corresponding to the bill, and the bill collection task may be executed to add the received electronic bill to the bill collection, so as to use the bill information of the electronic bill as the bill application result. In the third optional implementation mode provided in this embodiment, the task sequence is executed, including: Execute the bill query task in the task sequence to query the bill data of the user for the bill corresponding to the merchant information and / or time information in the interaction data; Execute the bill application task in the task sequence to call the merchant's bill application interface to apply for a bill based on the bill application information and bill data pre-configured by the user in the bill service; Execute the ticket collection task in the task sequence to add the electronic ticket returned by the interface call to the user's ticket collection.

[0049] Specifically, execute the bill query task in the task sequence, extract the merchant information and / or time information in the interactive data, query the bill data of the bill corresponding to the merchant information and / or time information in the user's bill data, execute the bill application task, call the merchant's bill application interface to apply for a bill based on the bill data and the user's preset bill application information, execute the bill collection task, and add the electronic invoice returned by the interface call to the user's bill collection.

[0050] For example, execute a bill query task, query the bill data for the bill corresponding to the merchant information within the time range, execute a bill application task, call the merchant's bill application interface to apply for a bill based on the bill data of the bill and the user's bill application information, and execute the bill application task to add the electronic invoice returned by the merchant to the user's bill collection.

[0051] In addition, in actual applications, there are situations where merchants need to respond to bill applications, and users still do not receive electronic bills after applying for bills, or they receive electronic bills after a period of time. In this regard, after executing the bill application task, if the bill application is successful, the above-mentioned bill collection task can be executed; if the bill application fails, the message generation task is executed to generate an application failure message; if the bill application is not responded to, the message generation task is executed to generate an application waiting message; in addition, there are situations where multiple electronic bills are applied for at one time, and the successfully applied electronic bills can be added to the user's bill collection, and an application failure message is generated for failed applications, and an application waiting message is generated for unresponsive applications. Optionally, the bill processing result includes: bill information of the electronic bill, application failure message and / or application waiting message.

[0052] (4) Execution of the task sequence for bill collection generated by the task generation model corresponding to the bill collection intention In the specific execution process, the task sequence for collecting bills may include a query task and a collection task. The query task may be executed to query the undownloaded bills in the user's bill mailbox, and the collection task may be executed to download the undownloaded bills and add them to the user's bill collection, so that the bill information of the added electronic bill is used as the bill collection result. In the fourth optional implementation mode provided in this embodiment, the task sequence is executed, including: Execute the query task in the task sequence and query the user's ticket mailbox for undownloaded tickets; Execute the collected tasks in the task sequence, download the undownloaded tickets and add them to the user's ticket collection.

[0053] It should be noted that, among the four implementation methods of executing the task sequence provided above, any one of the implementation methods can be selected for implementation according to actual needs during the specific implementation process. It should be noted that the four implementation methods can also be combined as a whole with any two or more of them according to actual needs, and corresponding technical means can also be selected from the four implementation methods according to actual needs to combine and form a new implementation method; taking the execution of the task sequence for bill reimbursement generated by the task generation model corresponding to the bill reimbursement intention as an example, for example: executing the query task in the task sequence to query the electronic bills and bills associated with the electronic bills that match the keywords in the interactive data in the user's bill collection; executing the verification task in the task sequence to verify the electronic bills and bills; executing the reimbursement form generation task in the task sequence to obtain the reimbursement form; for example: executing the bill application task in the task sequence to call the merchant's bill application interface for bill application based on the bill application information pre-configured by the user in the bill service and the bill data of the selected bill; executing the reimbursement form generation task in the task sequence to write the obtained electronic bill information and bill data of the bill into the reimbursement form to be configured to obtain the reimbursement form.

[0054] In actual applications, there are also situations where there are multiple intent categories in the interaction data submitted by users, for example: the intent categories corresponding to the interaction data are bill application intent and bill reimbursement intent; in response to this, the bill agent can select multiple task generation models based on the multiple intent categories of the interaction information to generate multiple task sequences, and execute multiple task sequences according to the preset execution relationship of the task sequences to obtain the bill processing results.

[0055] For example, if the interactive data is "Help me apply for last month's invoice and reimburse it", the bill agent can call the task generation model corresponding to the bill application intention to generate a task sequence for bill application and execute it to obtain the bill application result, call the task generation model corresponding to the bill reimbursement intention to generate a task sequence for bill reimbursement and execute it to obtain the bill reimbursement result, and use the bill reimbursement result as the bill processing result; For another example, the interactive data is "Help me organize the invoices applied for last month and reimburse them". The bill agent can call the task generation model corresponding to the bill organization intention to generate a task sequence for bill organization, and call the task generation model corresponding to the bill reimbursement intention to generate a task sequence for bill reimbursement, execute the task sequence for bill organization to obtain the bill organization result, execute the task sequence for bill reimbursement to obtain the bill reimbursement result, and use the bill reimbursement result as the bill processing result.

[0056] Step S206, obtaining the bill processing result returned by the bill agent, generating service response data according to the bill processing result and sending it to the user terminal.

[0057] In specific implementation, the bill intelligent agent performs bill processing to obtain the bill processing result, and returns the bill processing result. Correspondingly, the bill processing result obtained by the bill intelligent agent is obtained, and service response data is generated according to the bill processing result, and the service response data is sent to the user terminal. Specifically, the data contained in the bill processing result can be parsed, and the service response data is generated based on the data.

[0058] The service response data refers to the response data in response to the interactive data sent by the user terminal. The user terminal can display the service response data in the ticket service, and specifically can display the service response data on the interactive page of the ticket service. Specifically, the service response data can be displayed in the form of a message, rich text and / or a waistband. Optionally, the service response data includes: ticket information of the electronic ticket, text data and / or configuration information of the service interface.

[0059] Specifically, in the process of generating service response data, a service response message corresponding to the interaction data can be generated according to the bill processing result, a message template corresponding to the data type of the data contained in the bill processing result can be selected, and the data in the bill processing result is written into the message template to obtain a service response message; in an optional implementation manner provided by this embodiment, generating service response data according to the bill processing result includes: Determine the data type of the data contained in the bill processing result, select the corresponding message template based on the data type; write the data contained in the bill processing result into the message template to obtain a service response message. Optionally, the message template configures the service interface corresponding to the data type; the service interface includes: reimbursement submission interface, viewing interface, bill adding interface and / or bill export interface.

[0060] Specifically, the reimbursement form can be submitted after the reimbursement submission interface is triggered, the electronic invoice and / or reimbursement form can be viewed after the viewing interface is triggered, the electronic invoice selected by the user can be added to the reimbursement item after the invoice adding interface is triggered, and the electronic invoice can be exported after the invoice export interface is triggered.

[0061] For example, Figure 4 As shown, the bill processing result includes a reimbursement form, a message template corresponding to the reimbursement form is selected and the reimbursement form is written into the message template to obtain a service response message 401; for example, Figure 5 As shown, the bill processing result includes the bill information of the electronic bill, a message template corresponding to the bill information is selected and the bill information is written into the message template to obtain a service response message 501.

[0062] After the service response data is sent to the user terminal, during the specific execution process, the user can also submit interactive data for interactive processing, which can be done by submitting preset interactive data or by inputting interactive data; for example, the user can trigger the preset interactive text submission "Help me analyze the bill expenses" to obtain the analysis results of the bill expenses; In view of this, the bill agent can be called to detect whether the intent category corresponding to the interactive text is the above-mentioned preset intent category through the bill agent. If not, the bill information corresponding to the interactive text and the bill processing result can be input into the large language model to generate a service text, so as to send the service text to the user terminal to improve the user's interactive perception. In an optional implementation manner provided by this embodiment, after sending the service response data to the user terminal, it also includes: Based on the interactive text submitted by the user terminal, the bill agent is called for service processing; the service text returned by the bill agent is sent to the user terminal. Optionally, the interactive text is submitted after the interface configured on the interactive page of the bill service is triggered.

[0063] Optionally, the service processing includes: detecting whether the intent category corresponding to the interaction text is a preset intent category; if not, inputting the interaction text and the bill information in the bill processing result into the large language model for service processing to obtain the service text; if so, no processing is performed.

[0064] For example, Figure 4 As shown, after the user triggers button 403, the interactive text of "Help me analyze the expenses" is submitted, and the bill agent is called based on the interactive text. Accordingly, the bill agent detects the intent category of the interactive text and deploys it in the preset intent category. The interactive text and bill information are input into the large language model for service processing to obtain the service text and return it, and the service text returned by the bill agent is obtained and sent to the user terminal.

[0065] In addition, when the bill agent detects that the intent category of the interactive text belongs to the preset intent category, it can also input the interactive text into the task generation model corresponding to the intent category to generate a task sequence, execute the task sequence to obtain the bill processing result and return it, and accordingly, generate service response data based on the bill processing result and respond to the user terminal to send it; in addition, it can also directly input the interactive text and bill information into the large language model to generate service text without performing detection operations.

[0066] In actual applications, after obtaining the service response data, the user can also interact through the service response data, for example: after triggering the service interface configured by the service response data, the electronic invoice is exported and / or the expense report is submitted to improve the convenience of operation; in this regard, the user terminal can submit a bill processing request after the user triggers the service interface configured by the service response data, and accordingly, the service processing is performed in response to the bill processing request, and the service processing result is sent to the user terminal after it is obtained; in an optional implementation manner provided in this embodiment, after sending the service response data, it also includes: Obtain the bill processing request submitted by the user terminal; perform service processing on the user's electronic bill according to the bill processing method corresponding to the bill processing request, and send the service processing result to the user terminal. Optionally, the bill processing request is generated after the user triggers the service interface configured by the service response data.

[0067] The service processing result may be a service result corresponding to the bill processing request, and specifically, may be sent to the user terminal in the form of a message for display on the user terminal. For example, the service processing result of the bill export request may be an export success message and / or an export failure message, and the service processing result of the bill reimbursement request may be a submission success message and / or a submission failure message. Optionally, the service processing result includes a service processing message.

[0068] During the specific execution process, the reimbursement form corresponding to the service response data, or the reimbursement form included in the bill processing result, may also be submitted to the reimbursement service corresponding to the user according to the configuration information of the reimbursement submission interface in the bill processing request; in another optional implementation manner provided by this embodiment, service processing is performed according to the bill processing method, including: Get the reimbursement form included in the bill processing result, and query the data transmission interface of the reimbursement service associated with the user; The reimbursement form is used as the interface call input to call the data transmission interface for data transmission, so that the reimbursement service can process the reimbursement based on the electronic receipt in the reimbursement form.

[0069] For example, Figure 4 As shown, the user triggers the reimbursement submission interface 402 on the interactive page of the bill service to submit a bill processing request through the user terminal. After receiving the bill processing request, the reimbursement form in the bill processing result is obtained, and the data transmission interface of the reimbursement service associated with the user is queried. The data transmission interface is called based on the reimbursement form for data transmission, so that the user can perform reimbursement processing based on the electronic bill in the reimbursement form in the reimbursement service.

[0070] Alternatively, the electronic invoice selected by the user may be sent to the invoice recipient according to the configuration information of the invoice export interface in the invoice processing request; in an optional implementation manner provided by this embodiment, service processing is performed according to the invoice processing method, including: Filter out the electronic invoice corresponding to the invoice information in the invoice processing request from the user's invoice collection, generate a invoice link for the electronic invoice; send the invoice link to the invoice recipient included in the invoice processing request, so that the invoice recipient can download the electronic invoice through the invoice link.

[0071] For example, Figure 5 As shown, after the user selects an electronic invoice on the interactive page of the invoice service, the invoice export interface 502 is triggered to submit a invoice processing request through the user terminal. After receiving the invoice processing request, the electronic invoice is selected from the user's invoice collection based on the invoice information in the invoice processing request, and a invoice link of the electronic invoice is generated and sent to the invoice recipient, so that the invoice recipient can download the electronic invoice through the invoice link.

[0072] In addition, the bill service can also provide the function of scanning the merchant's bill code to apply for a bill. Specifically, the user can trigger the bill application interface on the service page of the bill service to submit a bill application instruction. The user terminal generates and submits a bill application based on the bill application instruction. Correspondingly, according to the bill application submitted by the user terminal, a scan code page is sent to the user terminal, so that the user scans the merchant's bill code to enter the merchant's bill service window to fill in the bill application information. Optionally, the bill application interface includes: a scan code billing interface; the bill application instruction includes a scan code billing instruction; the bill application includes a scan code billing request.

[0073] In actual applications, users need to fill in lengthy bill application information during the bill application process, and different merchants may access different bill service providers, and the bill application information pre-stored by users in the bill service provider is usually not shared; in response to this, the bill intelligent body can be called to fill in the application information after the user terminal enters the merchant's bill service window. The bill intelligent body fills in the bill application information of the bill applicant selected by the user on the code scanning page in the merchant's bill service window, avoiding the user from searching for bill application information and improving convenience; an optional implementation method provided by this embodiment also includes: sending a code scanning page to the user terminal according to the bill application submitted by the user terminal; calling the bill intelligent body to fill in the application information after the user terminal enters the merchant's bill service window. Specifically, after the user terminal enters the merchant's bill service window, the bill intelligent body is called to fill in the application information based on the application information of the bill applicant selected by the user on the code scanning page.

[0074] Specifically, the ticket agent can respond to the call and write the ticket information pre-selected by the user into the ticket service window to realize the automatic filling of the ticket application information; in an optional implementation provided by this embodiment, the application information filling includes: performing element recognition on the ticket service window to obtain the text element corresponding to the ticket application; writing the user's ticket application information into the text area corresponding to the text element in the ticket service window. Optionally, the ticket application information is determined according to the ticket application party selected by the user on the code scanning page.

[0075] For example, after a user triggers the ticket application interface on the ticket service page, the user can enter Figure 6 In the scan code page shown, the user triggers interface 601 on the scan code page to select institution A as the billing party, and triggers interface 602 to add the applied bill to project A.

[0076] Based on the above process of the user applying for a bill by scanning the code through the user terminal, after submitting the bill application to the merchant, the user can also return to the bill service from the bill service window. Correspondingly, after receiving the page return instruction submitted by the user terminal, the page to be issued can be determined according to the bill application result; specifically, if the bill application is successful, the interactive page of the bill service is generated and issued to the user terminal so that the user terminal returns to the interactive page; if the bill application fails, the service page of the bill service is generated and issued to the user terminal so that the user terminal returns to the service page. For example, after applying for a bill and obtaining an electronic bill, the user can return to the interactive page of the bill service to process the bill obtained.

[0077] In summary, the agent-based ticket service processing method provided in this embodiment can be applied to the server. When a user accesses the ticket service, the server receives the interaction data sent by the user terminal, calls the ticket agent to process the ticket based on the interaction data, generates service response data according to the ticket processing result returned by the ticket agent, and sends it to the user terminal. The service response efficiency is improved by the agent call method, and the user's interaction perception is improved by the service response data. Furthermore, the bill agent can input the interaction data into the corresponding task generation model to generate a task sequence for bill processing, execute the task sequence to obtain the bill processing result, and improve the reliability of the bill processing result by calling the task generation model to generate the task sequence.

[0078] The above steps S202 to S206 provided in this embodiment can be executed by the server of the ticket service. It should be noted that the above steps S202 to S206 executed by the server and the steps S902 to S906 executed by the user terminal in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding contents of steps S902 to S906 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding contents of steps S202 to S206 provided in this embodiment.

[0079] The following takes the application of an agent-based bill service processing method provided in this embodiment in a bill reimbursement scenario as an example, combined with Figure 7 , further describes the agent-based ticket service processing method provided in this embodiment, see Figure 7 , an agent-based bill service processing method applied to bill reimbursement scenarios specifically includes the following steps.

[0080] Step S706: receiving interaction data sent by the user terminal.

[0081] Step S708: Call the bill agent of the bill service to perform bill processing based on the interaction data.

[0082] Here, the bill processing includes: inputting the interaction data into the task generation model corresponding to the intention category of the interaction data to generate a task sequence for bill reimbursement, executing the query task in the task sequence to query the electronic bills and invoices for reimbursement, executing the verification task in the task sequence to verify the electronic bills and invoices, executing the reimbursement form generation task in the task sequence to obtain the reimbursement form, and using the reimbursement form as the bill reimbursement result.

[0083] Step S710, obtaining a message template corresponding to the reimbursement form in the bill reimbursement result.

[0084] Step S712: Write the reimbursement form into the message template to obtain a service response message and send it to the user terminal.

[0085] Step S718, query the data transmission interface of the reimbursement service associated with the user.

[0086] Step S720, using the reimbursement form as an interface call input to call a data transmission interface to transmit the reimbursement form.

[0087] Among them, executing the query task in the task sequence includes: searching the user's ticket collection for electronic tickets and bills associated with the electronic tickets that match the keywords in the interactive data; executing the verification task in the task sequence includes: verifying and processing the electronic tickets and bills in accordance with the reimbursement verification rules of the user's institution; executing the reimbursement form generation task in the task sequence includes: writing the ticket information of the verified electronic ticket and the bill data of the bill into the reimbursement form to be configured to obtain the reimbursement form.

[0088] It should be noted that any one or any combination of steps S706 to S712, and steps S718 to S720, can be combined with any one or any combination of steps S202 to S206 to form a new implementation method according to the needs of implementation deployment; in addition, according to the needs of actual deployment, any one or any combination of technical features in steps S706 to S712, and steps S718 to S720 can be selected and combined with any one or more technical features provided by steps S202 to S206 to form a new implementation method; or, any one or any combination of technical features in steps S706 to S712, and steps S718 to S720 can be replaced with any one or more technical features provided by steps S202 to S206 to form a new implementation method according to the needs of actual deployment, which will not be repeated here.

[0089] In addition, it should be noted that the above steps S706 to S712, and steps S718 to S720 provided in this embodiment can be executed by the server. It should be noted that the above steps S706 to S712, and steps S718 to S720 executed by the server and steps S702 to S704 and steps S714 to S716 executed by the user terminal in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding contents of steps S702 to S704 and steps S714 to S716 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding contents of steps S706 to S712, and steps S718 to S720 provided in this embodiment.

[0090] The following takes the application of an agent-based bill service processing method provided in this embodiment in a bill application scenario as an example, combined with Figure 8 , further describes the agent-based ticket service processing method provided in this embodiment, see Figure 8 , an agent-based bill service processing method applied to bill application scenarios specifically includes the following steps.

[0091] Step S806: receiving the interactive text sent by the user terminal.

[0092] Step S808, calling the bill agent of the bill service to perform bill processing based on the interactive text.

[0093] Here, the bill processing includes: inputting the interactive text into the task generation model corresponding to the intention category of the interactive text to generate a task sequence for bill application, executing the bill query task in the task sequence to query the bill, executing the bill application task in the task sequence to apply for the electronic invoice corresponding to the bill, executing the bill collection task in the task sequence to add the received electronic invoice to the bill collection, so as to use the bill information of the electronic invoice as the bill application result.

[0094] Step S810, obtaining a message template corresponding to the electronic invoice in the invoice application result.

[0095] Step S812: Write the bill information of the electronic bill into the message template to obtain a service response message and send it to the user terminal.

[0096] Step S818, receiving a bill export request, and filtering out electronic bills corresponding to the bill information in the bill export request from the user's bill collection.

[0097] Step S820: Generate a bill link for the electronic bill and send it to the bill recipient included in the bill export request.

[0098] Among them, executing the bill query task in the task sequence includes: querying the bill data of the bill corresponding to the merchant information in the interactive text in the user's bill data; executing the bill application task in the task sequence includes: calling the merchant's bill application interface to apply for a bill based on the bill application information and bill data pre-configured by the user in the bill service; executing the bill collection task in the task sequence includes: adding the electronic invoice returned by the interface call to the user's bill collection, and using the bill information of the returned electronic invoice as the bill application result.

[0099] It should be noted that any one or any combination of steps S806 to S812 and steps S818 to S820 can be combined with any one or any combination of steps S202 to S206 to form a new implementation method according to the needs of implementation deployment; in addition, according to the needs of actual deployment, any one or any combination of technical features in steps S806 to S812 and steps S818 to S820 can be selected and combined with any one or more technical features provided by steps S202 to S206 to form a new implementation method; or, any one or any combination of technical features in steps S806 to S812 and steps S818 to S820 can be replaced with any one or more technical features provided by steps S202 to S206 to form a new implementation method according to the needs of actual deployment, which will not be repeated here.

[0100] In addition, it should be noted that the above-mentioned steps S806 to S812 and steps S818 to S820 provided in this embodiment can be executed by the server. It should be noted that the above-mentioned steps S806 to S812 and steps S818 to S820 executed by the server and steps S802 to S804 and steps S814 to S816 executed by the user terminal in the following embodiment can cooperate with each other during the execution process. Therefore, when reading this embodiment, please refer to the corresponding contents of steps S802 to S804 and steps S814 to S816 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding contents of steps S806 to S812 and steps S818 to S820 provided in this embodiment.

[0101] One or more embodiments of another agent-based ticket service processing method provided in this specification are as follows: Reference Fig. 9 The present embodiment provides an agent-based ticket service processing method, which specifically includes steps S902 to S906.

[0102] Step S902, obtaining the interaction data submitted by the user on the interaction page of the ticket service.

[0103] The ticket service described in this embodiment may be a service related to electronic tickets. Users may access the ticket service to process tickets. The ticket service may be a ticket application. The ticket service may also be a ticket subroutine or a ticket service module of an application. Alternatively, the ticket service may be provided to users in the form of a ticket application, a subroutine of a ticket application, and / or a service module of a ticket application. In addition, the ticket service may also be provided through an application and / or a subroutine of an application. The ticket service may provide multiple different functions, and users may use these functions in the ticket service.

[0104] For example, users can use the bill application function in the bill service to issue electronic bills, users can also use the bill collection function in the bill service to collect electronic bills, users can also use the bill sorting function in the bill service to sort or query electronic bills, and users can also use the bill reimbursement function in the bill service to reimburse electronic bills; in addition, users can also use the question and answer function in the bill service to ask bill-related questions, and users can also export electronic bills in the bill service.

[0105] Specifically, the ticket service can be configured with a ticket agent, and the ticket service can perform ticket processing through the ticket agent to cooperate with the implementation of the functions of the ticket service. The ticket agent can perform corresponding ticket processing based on the interaction data submitted by the user; the interaction data is the data submitted by the user in the ticket service to describe the user's needs for ticket processing, which can be used as the calling input of the ticket agent. The ticket agent can select a task generation model based on the intention category of the interaction data. The interaction data may include interaction data entered and submitted by the user, and may also include preset interaction data triggered and submitted by the user; optionally, the interaction data includes interaction text and / or interaction voice.

[0106] Among them, the bill agent refers to an agent connected to the bill service, or an agent configured in the bill service. The bill agent can cooperate with the bill service to realize the function of the bill service. The bill agent can be deployed outside the bill service or in the bill service. The bill agent can be configured with multiple task generation models, or the bill agent can be connected to multiple task generation models. The task generation model can generate a task sequence for bill processing. The task generation model can correspond to the intent category of the interaction data. The bill agent can determine the task generation model to be called based on the interaction data to generate a task sequence for bill processing. In addition, the task generation model can correspond to the function of the bill service to generate a task sequence for bill processing. Optionally, the intent category includes: bill reimbursement intent, bill sorting intent, bill collection intent and / or bill application intent.

[0107] For example, the task generation model corresponding to the bill reimbursement intent can generate a task sequence for bill reimbursement, and the bill agent executes the task sequence to generate a reimbursement form for the electronic bill; the task generation model corresponding to the bill sorting intent can generate a task sequence for bill sorting, and the bill agent executes the task sequence to query the bill information of the electronic bill; the task generation model corresponding to the bill collection intent can generate a task sequence for bill collection, and the bill agent executes the task sequence to add the electronic bill to the user's bill collection; the task generation model corresponding to the bill application intent can generate a task sequence for bill application, and the bill agent executes the task sequence to apply for the user's electronic bill.

[0108] In addition, the bill agent can also be connected to the large language model to cooperate with the bill service to realize the question and answer function of the bill service; optionally, the bill processing includes inputting the interaction data into the large language model for bill processing to obtain the bill processing result; for example, when the user asks questions related to the bill, the bill agent can call the large language model to generate a reply text.

[0109] In a specific implementation, when a user accesses a ticket service, the user can use the functions of the ticket service by submitting interactive data in the ticket service. For this purpose, a preset interactive text can be configured in the ticket service, and the user can trigger and submit the preset interactive text to be sent through the user terminal, thereby improving the convenience of interaction. In an optional implementation manner provided in this embodiment, obtaining interactive data includes: The interactive data triggered and submitted by the user on the interactive page of the ticket service is obtained. Optionally, the interactive data includes preset interactive text; the preset interactive text is generated according to the ticket information of the electronic ticket to be reimbursed in the user's ticket collection.

[0110] Specifically, the user can trigger the interface corresponding to the preset interactive text on the interactive page of the ticket service, and submit the preset interactive text after triggering the interface, so that the user terminal sends the preset interactive text as interactive data to the server.

[0111] In addition, when a user accesses the ticket service, the user may also enter interactive data in the ticket service and submit it to be sent to the server through the user terminal; in another optional implementation provided by this embodiment, the interactive data is submitted after the user enters it on the interactive page of the ticket service. Optionally, the interactive data includes the interactive data entered by the user on the interactive page of the ticket service.

[0112] In a specific implementation, the user submits interaction data after interacting on the interaction page of the ticket service during access to the ticket service, and accordingly, the interaction data submitted by the user on the interaction page of the ticket service is obtained.

[0113] It should be noted that the user may not interact and submit interaction data on the interaction page, and the ticket service may also provide a floating window, a window and / or run in the background to interact with the user through voice interaction; step S902 may be replaced by: obtaining the interaction data submitted by the user on the ticket service.

[0114] Step S904: sending the interaction data to a server.

[0115] In a specific implementation, the interaction data is sent to the server so that the server calls the ticket agent of the ticket service to perform ticket processing. Correspondingly, the ticket agent of the ticket service determines the intent category of the interaction data in response to the agent call, selects a task generation model corresponding to the intent category, inputs the interaction data into the task generation model to generate a task sequence for ticket processing, and executes the task sequence to obtain the ticket processing result. Optionally, the ticket processing includes inputting the interaction data into the task generation model corresponding to the intent category of the interaction data to generate a task sequence for ticket processing, and executing the task sequence to obtain the ticket processing result.

[0116] Specifically, in the process of calling the bill intelligent body, the interactive data can be used as the calling input of the bill intelligent body to call the bill intelligent body. Specifically, the application programming interface (Application Programming Interface, API) of the bill intelligent body can be called based on the interactive data to send the interactive data to the bill intelligent body.

[0117] After the above-mentioned server calls the ticket agent based on the interactive data sent by the user terminal, the ticket agent of the ticket service responds to the call and performs ticket processing. During the specific execution process, the corresponding task generation model can be called according to the interactive data to obtain the task sequence for ticket processing and execute it to obtain the ticket processing result, so as to use the ticket processing result as the return result of the agent call; optionally, the ticket processing includes inputting the interactive data into the corresponding task generation model to obtain the task sequence for ticket processing and execute it to obtain the ticket processing result.

[0118] Specifically, in the process of determining the task generation model, the bill intelligent agent can extract the intent category of the interaction data, and select the task generation model corresponding to the intent category from the multiple connected task generation models. Specifically, the intent category can be preset for the task generation model in advance, and the intent category obtained based on the intent recognition of the interaction data is matched with the preset intent category, and the task generation model is determined according to the matching result; alternatively, the task generation model can also correspond to the interaction data, and the bill intelligent agent determines the task generation model according to the interaction data.

[0119] The bill processing result is the execution result of the bill agent after executing the task sequence for bill processing, which is used to characterize the result of bill processing; the task generation model can also correspond to different functions of the bill service, and accordingly, the generated task sequence can also correspond to different functions, and the bill processing result can also correspond to different functions. Specifically, the bill processing result can include different data. Optionally, the bill processing result includes: reimbursement form data of the reimbursement form, bill information of the electronic bill and / or bill data of the bill; in addition, the bill processing result can also include a reply text.

[0120] For example, corresponding to the bill reimbursement function, the bill processing result may include a reimbursement form constructed based on the bill information of the electronic invoice and the bill data of the associated bill; corresponding to the bill sorting function, the bill processing result may include the bill information of the queried electronic invoice; corresponding to the bill collection function, the bill processing result may include the bill information of the collected electronic invoice; corresponding to the bill application function, the bill processing result may include the bill information of the applied electronic invoice.

[0121] Specifically, in the process of generating a task sequence, the task generation model can determine the tasks to be configured in the preset task sequence according to the interaction data, and configure the keywords in the interaction data in the corresponding tasks to be configured to obtain a task sequence; in an optional implementation manner provided in this embodiment, generating a task sequence includes: Extract multiple keywords from the interaction data, and select tasks to be configured that match the keywords from the preset task set; Each keyword is configured in its corresponding task to be configured to obtain a plurality of bill processing tasks, and a task sequence is constructed based on the preset execution relationship of the task to be configured and each bill processing task.

[0122] Specifically, during the execution of the task sequence, the bill processing tasks in the task sequence may be read and each bill processing task may be executed according to the execution relationship to obtain the bill processing result; in an optional implementation manner provided by this embodiment, executing the task sequence includes: Read multiple bill processing tasks contained in the task sequence and the execution relationship between the bill processing tasks; Execute each bill processing task according to the execution relationship to obtain the bill processing result.

[0123] In actual scenarios, the task generation model corresponds to different intent categories, or corresponds to different functions of the bill service. The bill processing required for different intent categories and / or functions may be different. Accordingly, the task sequence generated by the task generation model and the bill processing results obtained by the bill agent executing the task sequence may also be different. For example: the preset task sequence of the task generation model corresponding to the bill reimbursement function may include a query task to be configured, a verification task to be configured, and a reimbursement form generation task to be configured. The generated task sequence can be expressed as: [query task → verification task → reimbursement form generation task]; the preset task set of the task generation model corresponding to the bill application function may include a bill query task to be configured, a bill application task to be configured, and a bill collection task to be configured. The generated task sequence can be expressed as: [bill query task → bill application task → bill collection task].

[0124] Based on this, specifically during the execution of the task sequence, the task sequence can be executed according to the bill processing tasks and execution relationships in the task sequence. The execution process of the task sequences generated by the above four task generation models is specifically described below.

[0125] (1) Execution of the task sequence for bill reimbursement generated by the task generation model corresponding to the bill reimbursement intention In the specific execution process, the task sequence for bill reimbursement may include a query task, a verification task, and a reimbursement form generation task. The query task may be executed to query the electronic bills and bills for reimbursement, the verification task may be executed to verify the electronic bills and bills, and the reimbursement form generation task may be executed to obtain the reimbursement form, which may be used as the bill reimbursement result. In the first optional implementation manner provided in this embodiment, the task sequence is executed, including: Execute the query task in the task sequence to query the user's ticket collection for electronic tickets and bills associated with the electronic tickets that match the keywords in the interaction data; Execute the verification tasks in the task sequence to verify and process electronic receipts and bills according to the reimbursement verification rules; If the verification passes, the reimbursement form generation task in the task sequence is executed to write the bill information of the electronic invoice and the bill data of the bill into the reimbursement form to be configured to obtain the reimbursement form.

[0126] Specifically, firstly, the query task is executed, the keywords contained in the interactive data are extracted, and the electronic invoices matching the keywords in the interactive data are searched in the user's invoice collection, and the bills associated with the electronic invoices are searched in the bill data, and the bill information of the electronic invoice and the bill data of the bill are used as the task execution input of the verification task, and each electronic invoice and bill are verified and processed according to the preset reimbursement verification rules. If the verification fails, no processing is performed, and if the verification passes, the reimbursement form generation task is executed, and the bill information and bill data are written into the reimbursement form to be configured to obtain the reimbursement form; wherein, the electronic invoice matching the keyword can be an electronic invoice matching any keyword, or an electronic invoice matching two or more keywords at the same time. Optionally, the keywords include time keywords, regional keywords and / or merchant keywords.

[0127] For example, execute the query task in the task sequence, query the electronic invoices with an issue time within X months and in X city in the user's invoice collection, and the bills associated with the electronic invoices, execute the verification task to verify each electronic invoice and bill according to the amount verification rules of the user's institution, and execute the reimbursement form generation task after the verification is passed, write the invoice information and bill data of the electronic invoice into the reimbursement form to be configured to obtain the reimbursement form.

[0128] In addition, if the verification fails, the reimbursement form generation task in the task sequence may not be executed, and the message generation task in the task sequence may be executed to generate a verification failure message based on the ticket information and bill data as the ticket reimbursement result; further, the ticket processing result and / or the ticket reimbursement result may also include the reimbursement form and the verification failure message; for example, if the verification passes, the reimbursement form generation task is executed to generate a reimbursement form based on the electronic ticket and bill that have passed the verification; if the verification fails, the message generation task is executed to generate a verification failure message based on the electronic ticket and bill that have failed the verification, and the reimbursement form and the verification failure message are used as the ticket reimbursement result.

[0129] Among them, during the execution of the task sequence for bill reimbursement generated by the task generation model corresponding to the bill reimbursement intention, the subsequent tasks in the task sequence can also be executed directly according to the verification results. For example: after the verification task is executed, the reimbursement form generation task in the task sequence can be executed to write the bill information of the verified electronic invoice and the bill data of the bill into the reimbursement form to be configured to obtain the reimbursement form; or, after the verification task is executed, the message generation task in the task sequence can be executed to generate a verification failure message based on the bill information of the electronic invoice that failed the verification.

[0130] (2) Execution of the task sequence for bill sorting generated by the task generation model corresponding to the bill sorting intention In the specific execution process, the task sequence for bill sorting may include a query task and a sorting task. The query task may be executed to query the electronic bill, and the sorting task may be executed to sort the electronic bill to obtain bill information of the sorted electronic bill, which may be used as the bill sorting result. In the second optional implementation manner provided in this embodiment, the task sequence is executed, including: Execute the query task in the task sequence to query the user's ticket collection for an electronic ticket whose ticket information matches the time information, area information and / or merchant information configured in the query task; Execute the sorting task in the task sequence to sort the electronic invoices obtained by the query according to the sorting method configured by the sorting task, and obtain the invoice information of the sorted electronic invoice.

[0131] Specifically, firstly, the query task in the task sequence is executed, the query keywords in the configuration information of the query task are read, such as time information, area information and / or merchant information, and the electronic receipts matching the keywords are searched in the user's receipt collection, and the sorting task is executed to sort the electronic receipts obtained by the query according to the sorting method configured by the sorting task, and the receipt information of the sorted electronic receipts is obtained; wherein, the electronic receipts matching the keywords may be electronic receipts matching any keyword, or may be electronic receipts matching two or more keywords at the same time. Optionally, the sorting method includes a time sorting method, an amount sorting method and / or a consumption type sorting method.

[0132] For example, execute the query task in the task sequence, read the time information, area information and merchant information in the configuration information of the query task, query the electronic invoices matching the time information, the electronic invoices matching the area information and the electronic invoices matching the merchant information in the user's ticket collection, execute the sorting task to sort the above three electronic invoices obtained by the query according to time, and obtain the ticket information of the sorted electronic invoices.

[0133] (3) Execution of the task sequence for bill application generated by the task generation model corresponding to the bill application intention In the specific execution process, the task sequence for bill application may include a bill query task, a bill application task and a bill collection task. The bill query task may be executed to query the bill, the bill application task may be executed to apply for the electronic bill corresponding to the bill, and the bill collection task may be executed to add the received electronic bill to the bill collection, so as to use the bill information of the electronic bill as the bill application result. In the third optional implementation mode provided in this embodiment, the task sequence is executed, including: Execute the bill query task in the task sequence to query the bill data of the user for the bill corresponding to the merchant information and / or time information in the interaction data; Execute the bill application task in the task sequence to call the merchant's bill application interface to apply for a bill based on the bill application information and bill data pre-configured by the user in the bill service; Execute the ticket collection task in the task sequence to add the electronic ticket returned by the interface call to the user's ticket collection.

[0134] Specifically, execute the bill query task in the task sequence, extract the merchant information and / or time information in the interactive data, query the bill data of the bill corresponding to the merchant information and / or time information in the user's bill data, execute the bill application task, call the merchant's bill application interface to apply for a bill based on the bill data and the user's preset bill application information, execute the bill collection task, and add the electronic invoice returned by the interface call to the user's bill collection.

[0135] For example, execute a bill query task, query the bill data for the bill corresponding to the merchant information within the time range, execute a bill application task, call the merchant's bill application interface to apply for a bill based on the bill data of the bill and the user's bill application information, and execute the bill application task to add the electronic invoice returned by the merchant to the user's bill collection.

[0136] In addition, in actual applications, there is a process in which merchants need to respond to bill applications, and there is a situation where the electronic bill is not obtained after the bill application, or the electronic bill is obtained after a period of time. In this regard, after executing the bill application task, if the bill application is successful, the above-mentioned bill collection task is executed; if the bill application fails, the message generation task is executed to generate an application failure message; if the bill application is not responded to, the message generation task is executed to generate an application waiting message; further, there is a situation where multiple electronic bills are applied for at one time, and the successfully applied electronic bills can be added to the user's bill collection, and an application failure message is generated for failed applications, and an application waiting message is generated for unresponsive applications.

[0137] (4) Execution of the task sequence for bill collection generated by the task generation model corresponding to the bill collection intention In the specific execution process, the task sequence for collecting bills may include a query task and a collection task. The query task may be executed to query the undownloaded bills in the user's bill mailbox, and the collection task may be executed to download the undownloaded bills and add them to the user's bill collection, so that the bill information of the added electronic bill is used as the bill collection result. In the fourth optional implementation mode provided in this embodiment, the task sequence is executed, including: Execute the query task in the task sequence and query the user's ticket mailbox for undownloaded tickets; Execute the collected tasks in the task sequence, download the undownloaded tickets and add them to the user's ticket collection.

[0138] It should be noted that, among the four implementation methods of executing the task sequence provided above, any one of the implementation methods can be selected for implementation according to actual needs during the specific implementation process. It should be noted that the four implementation methods can also be combined as a whole with any two or more of them according to actual needs, and corresponding technical means can also be selected from the four implementation methods according to actual needs to combine and form a new implementation method; taking the execution of the task sequence for bill reimbursement generated by the task generation model corresponding to the bill reimbursement intention as an example, for example: executing the query task in the task sequence to query the electronic bills and bills associated with the electronic bills that match the keywords in the interactive data in the user's bill collection; executing the verification task in the task sequence to verify the electronic bills and bills; executing the reimbursement form generation task in the task sequence to obtain the reimbursement form; for example: executing the bill application task in the task sequence to call the merchant's bill application interface for bill application based on the bill application information pre-configured by the user in the bill service and the bill data of the selected bill; executing the reimbursement form generation task in the task sequence to write the obtained electronic bill information and bill data of the bill into the reimbursement form to be configured to obtain the reimbursement form.

[0139] In actual applications, there are also situations where there are multiple intent categories in the interaction data submitted by users, for example: the intent categories corresponding to the interaction data are bill application intent and bill reimbursement intent; in response to this, the bill agent can select multiple task generation models based on the multiple intent categories of the interaction information to generate multiple task sequences, and execute multiple task sequences according to the preset execution relationship of the task sequences to obtain the bill processing results.

[0140] Step S906, receiving service response data generated and sent by the server according to the ticket processing result, and displaying it on the interactive page.

[0141] In specific implementation, the bill agent performs bill processing to obtain the bill processing result, and returns the bill processing result to the server. The server obtains the bill processing result obtained by the bill agent, generates service response data according to the bill processing result and sends it. Correspondingly, the service response data generated and sent by the server according to the bill processing result is obtained and displayed on the interactive page. Among them, the service response data can be generated based on the data contained in the bill processing result.

[0142] The service response data refers to the response data in response to the interactive data sent by the user terminal. The user terminal can display the service response data in the ticket service, and specifically can display the service response data on the interactive page of the ticket service. Specifically, the service response data can be displayed in the form of a message, rich text and / or a waistband. Optionally, the service response data includes: ticket information of the electronic ticket, text data and / or configuration information of the service interface.

[0143] Specifically, in the process of generating service response data, a service response message corresponding to the interaction data can be generated according to the bill processing result, a message template corresponding to the data type of the data contained in the bill processing result can be selected, and the data in the bill processing result is written into the message template to obtain a service response message; in an optional implementation manner provided by this embodiment, generating service response data according to the bill processing result includes: Determine the data type of the data contained in the bill processing result, select the corresponding message template based on the data type; write the data contained in the bill processing result into the message template to obtain a service response message. Optionally, the message template configures the service interface corresponding to the data type; the service interface includes: reimbursement submission interface, viewing interface, bill adding interface and / or bill export interface.

[0144] Specifically, the reimbursement form can be submitted after the reimbursement submission interface is triggered, the electronic invoice and / or reimbursement form can be viewed after the viewing interface is triggered, the electronic invoice selected by the user can be added to the reimbursement item after the invoice adding interface is triggered, and the electronic invoice can be exported after the invoice export interface is triggered.

[0145] After receiving the service response data, during the specific execution process, the user may also submit interactive data for interactive processing, which may be performed by submitting preset interactive data or by inputting interactive data; in this regard, the interactive text triggered and submitted by the user may be submitted to the server, and the service text sent by the server may be obtained and displayed; in an optional implementation manner provided by this embodiment, after displaying the service response data, it also includes: After detecting that the user triggers the interface corresponding to the interactive text configured on the interactive page, submit the interactive text to the server; or submit the interactive text triggered and submitted by the user to the server; The service text generated by the server calling the ticket agent for service processing based on the interactive text is obtained, and the service text is displayed on the interactive page. Optionally, the service processing includes calling a large language model based on the interactive text to generate the service text.

[0146] For example, Figure 4 As shown, after the user triggers button 403, he submits the interactive text "Help me analyze the cost", and obtains the service text returned by the server and displays it on the interactive page.

[0147] Correspondingly, the server can call the ticket intelligent body to perform service processing. The specific execution process can refer to the execution process provided in the above embodiment, which will not be repeated in this embodiment.

[0148] In actual applications, after receiving the service response data, the user can also interact through the service response data, for example, exporting electronic receipts and / or submitting expense reports after triggering the service interface configured by the service response data, so as to improve the convenience of operation; In view of this, after the user triggers the service interface configured by the service response data, a ticket processing request can be submitted, and the service processing result sent by the server can be received; in an optional implementation manner provided by this embodiment, after displaying the service response data, it also includes: If it is detected that the user triggers the service interface configured by the service response data, a ticket processing request is generated according to the configuration information of the service interface and submitted to the server; or, a ticket processing request is generated according to the configuration information of the service interface triggered by the user and submitted to the server; The receiving server performs service processing on the user's electronic receipt according to the receipt processing method corresponding to the receipt processing request and displays the service processing result sent.

[0149] The service processing result may be a service result corresponding to the bill processing request, and specifically, may be sent to the user terminal in the form of a message for display on the user terminal; the optional service processing result includes a service processing message. For example, the service processing result of the bill export request may be an export success message and / or an export failure message, and the service processing result of the bill reimbursement request may be a submission success message and / or a submission failure message.

[0150] For example, Figure 4 As shown, the user triggers the reimbursement submission interface 402 on the interactive page of the bill service to submit a bill processing request through the user terminal. After processing, the server sends a submission success message to the user terminal and displays it on the interactive page; For example, Figure 5 As shown, after the user selects an electronic invoice on the interactive page of the invoice service, the invoice export interface 502 is triggered to submit an invoice processing request through the user terminal. After processing, the server sends an export success message to the user terminal and displays it on the interactive page.

[0151] In addition, the bill service may also provide a function of scanning the bill code of the merchant to apply for a bill. Specifically, the user may trigger the bill application interface on the service page of the bill service to submit a bill application instruction. The user terminal generates and submits a bill application based on the bill application instruction. Optionally, the bill application interface includes: a code scanning billing interface; the bill application instruction includes a code scanning billing instruction; the bill application includes a code scanning billing request; an optional implementation method provided in this embodiment also includes: After the user triggers the ticket application interface configured on the service page of the ticket service, a ticket application is generated and submitted to the server; or, a ticket application is generated according to the ticket application instruction submitted by the user and sent to the server; Receive and display the code scanning page sent by the server, and enter the merchant's bill service window to fill in the application information after scanning the merchant's bill code; submit the billing request to the merchant according to the confirmation instruction submitted by the user.

[0152] After submitting the invoicing request, the electronic invoice returned by the merchant can be obtained and added to the reimbursement item selected by the user on the code scanning page. Optionally, the application information is filled in by calling the invoice agent on the server.

[0153] For example, Figure 6 As shown, after the user triggers the bill application interface configured on the service page of the bill service, he will jump to the scanning page, and trigger interface 601 to select institution A as the issuer, and trigger interface 602 to add the applied bill to project A. According to the scanning result of the bill code, he will enter the merchant's bill service window, and submit a billing request to the merchant after filling in the form to obtain an electronic bill.

[0154] Based on the above process of the user applying for a ticket through the user terminal, after submitting the ticket application to the merchant, the user can also return to the ticket service from the ticket service window, and can submit a page return instruction to the server so that the server returns a page according to the ticket application result; in an optional implementation manner provided by this embodiment, after submitting the ticket request, it also includes: Send the page return instruction submitted by the user to the server; if the ticket application is successful, obtain the interactive page returned by the server and display it; if the ticket application fails and / or the ticket application is not responded to, no processing is required. In addition, in the case of a ticket application failure and / or a ticket application is not responded to, you can return to the service page of the ticket service; after submitting the invoicing request, it also includes: sending the page return instruction submitted by the user to the server; if the ticket application fails and / or the ticket application is not responded to, obtain the service page returned by the server and display it.

[0155] In actual applications, users need to fill in lengthy bill application information during the bill application process, and different merchants may access different bill service providers, and the bill application information pre-stored by users in the bill service provider is usually not shared; in response to this, the bill intelligent body can be called to fill in the application information after the user terminal enters the merchant's bill service window. The bill intelligent body fills in the bill application information of the bill applicant selected by the user on the code scanning page in the merchant's bill service window, avoiding the user from searching for bill application information and improving convenience; an optional implementation method provided by this embodiment also includes: sending a code scanning page to the user terminal according to the bill application submitted by the user terminal; calling the bill intelligent body to fill in the application information after the user terminal enters the merchant's bill service window. Specifically, after the user terminal enters the merchant's bill service window, the bill intelligent body is called to fill in the application information based on the application information of the bill applicant selected by the user on the code scanning page.

[0156] Specifically, the ticket agent can respond to the call and write the ticket information pre-selected by the user into the ticket service window to realize the automatic filling of the ticket application information; in an optional implementation provided by this embodiment, the application information filling includes: performing element recognition on the ticket service window to obtain the text element corresponding to the ticket application; writing the user's ticket application information into the text area corresponding to the text element in the ticket service window. Optionally, the ticket application information is determined according to the ticket application party selected by the user on the code scanning page.

[0157] In summary, another agent-based ticket service processing method provided in this embodiment can be applied to a user terminal. When a user accesses a ticket service, the method obtains the interaction data submitted by the user in the ticket service, sends the interaction data to the server, receives the service response data generated and sent by the server, and displays it on the interaction page. The ticket processing is performed in an interactive manner, thereby improving the user convenience in the ticket processing process and improving the user's interaction perception. Furthermore, the server can call the ticket agent for service processing based on the interactive data, and improve the service response efficiency by calling the agent; Furthermore, the bill agent can input the interaction data into the corresponding task generation model to generate a task sequence for bill processing, execute the task sequence to obtain the bill processing result, and improve the stability of the bill processing result by calling the task generation model.

[0158] The following takes the application of an agent-based bill service processing method provided in this embodiment in a bill reimbursement scenario as an example, combined with Figure 7 , further describes the agent-based ticket service processing method provided in this embodiment, see Figure 7 , an agent-based bill service processing method applied to bill reimbursement scenarios specifically includes the following steps.

[0159] Step S702, obtaining the interaction data entered by the user on the interaction page of the ticket service.

[0160] Step S704: sending the interaction data to the server.

[0161] Step S714, receiving a service response message sent by the server and displaying it on the interactive page.

[0162] Step S716: Generate and send a bill reimbursement request based on the configuration information of the reimbursement submission interface configured by the service response message triggered by the user.

[0163] After step S716 is executed, the following may also be performed: jumping to the reimbursement service according to the user's instruction to perform reimbursement processing based on the electronic receipt in the reimbursement form.

[0164] It should be noted that any one or any combination of steps S702 to S704 and steps S714 to S716 can be combined with any one or any combination of steps S902 to S906 to form a new implementation method according to the needs of implementation deployment; in addition, according to the needs of actual deployment, any one or any combination of technical features in steps S702 to S704 and steps S714 to S716 can be selected and combined with any one or more technical features provided by steps S902 to S906 to form a new implementation method; or, any one or any combination of technical features in steps S702 to S704 and steps S714 to S716 can be replaced with any one or more technical features provided by steps S902 to S906 to form a new implementation method according to the needs of actual deployment, which will not be repeated here.

[0165] The following takes the application of an agent-based bill service processing method provided in this embodiment in a bill application scenario as an example, combined with Figure 8 , further describes the agent-based ticket service processing method provided in this embodiment, see Figure 8 , an agent-based bill service processing method applied to bill application scenarios specifically includes the following steps.

[0166] Step S802: Obtain the interactive text triggered and submitted by the user.

[0167] Here, the interactive text is determined by the server and / or the bill agent according to the bill information of the electronic bill to be reimbursed in the user's bill collection.

[0168] Step S804: sending the interactive text to the server.

[0169] Step S814: receiving a service response message sent by the server and displaying it on the interactive page.

[0170] Step S816: Generate and send a bill export request based on the configuration information of the bill export interface configured by the service response message triggered by the user.

[0171] It should be noted that any one or any combination of steps in steps S802 to S804 and steps S814 to S816 can be combined with any one or any combination of steps S902 to S906 to form a new implementation method according to the needs of implementation deployment; in addition, according to the needs of actual deployment, any one or any combination of technical features in steps S802 to S804 and steps S814 to S816 can be selected and combined with any one or more technical features provided in steps S902 to S906 to form a new implementation method; or, any one or any combination of technical features in steps S802 to S804 and steps S814 to S816 can be replaced with any one or more technical features provided in steps S902 to S906 to form a new implementation method according to the needs of actual deployment, which will not be repeated here.

[0172] An embodiment of a ticket service processing device based on an intelligent agent provided in this specification is as follows: In the above-mentioned embodiment, a method for processing ticket services based on an intelligent agent is provided, and correspondingly, a device for processing ticket services based on an intelligent agent is also provided, which will be described below in conjunction with the accompanying drawings.

[0173] Reference Fig.10 , which shows a schematic diagram of an embodiment of a ticket service processing device based on an intelligent agent provided in this embodiment.

[0174] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0175] This embodiment provides a ticket service processing device based on an intelligent agent, comprising: The interactive data receiving module 1002 is configured to receive the interactive data sent by the user terminal after entering the ticket service; The ticket agent calling module 1004 is configured to call the ticket agent of the ticket service to perform ticket processing based on the interaction data; the ticket processing includes inputting the interaction data into a task generation model corresponding to the intention category of the interaction data to generate a task sequence for ticket processing, and executing the task sequence to obtain a ticket processing result; The service response data generation module 1006 is configured to obtain the bill processing result returned by the bill agent, generate service response data according to the bill processing result, and send it to the user terminal.

[0176] Another embodiment of a ticket service processing device based on an intelligent agent provided in this specification is as follows: In the above-mentioned embodiment, another agent-based ticket service processing method is provided, and correspondingly, another agent-based ticket service processing device is also provided, which is described below with reference to the accompanying drawings.

[0177] Reference Fig.11 , which shows a schematic diagram of an embodiment of a ticket service processing device based on an intelligent agent provided in this embodiment.

[0178] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0179] This embodiment provides a ticket service processing device based on an intelligent agent, the device comprising: The interactive data acquisition module 1102 is configured to acquire the interactive data submitted by the user on the interactive page of the ticket service; The interactive data sending module 1104 is configured to send the interactive data to the server to call the bill agent to perform bill processing; the bill processing includes inputting the interactive data into the corresponding task generation model to obtain a task sequence for bill processing and executing it to obtain a bill processing result; The service response data receiving module 1106 is configured to receive the service response data generated and sent by the server according to the ticket processing result, and display it on the interactive page.

[0180] An embodiment of a ticket service processing device based on an intelligent agent provided in this specification is as follows: Corresponding to the above-described agent-based ticket service processing method, based on the same technical concept, one or more embodiments of this specification further provide an agent-based ticket service processing device, the agent-based ticket service processing device is used to execute the above-described agent-based ticket service processing method. Fig.12 A schematic diagram of the structure of an agent-based ticket service processing device provided for one or more embodiments of this specification.

[0181] The present embodiment provides an agent-based ticket service processing device, comprising: like Fig.12As shown, the agent-based ticket service processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 1201 and memory 1202, and the memory 1202 may store one or more storage applications or data. Among them, the memory 1202 may be a short-term storage or a persistent storage. The application stored in the memory 1202 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the agent-based ticket service processing device. Furthermore, the processor 1201 may be configured to communicate with the memory 1202, and execute a series of computer executable instructions in the memory 1202 on the agent-based ticket service processing device. The agent-based ticket service processing device may also include one or more power supplies 1203, one or more wired or wireless network interfaces 1204, one or more input / output interfaces 1205, one or more keyboards 1206, etc.

[0182] In a specific embodiment, the agent-based ticket service processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the agent-based ticket service processing device, and the one or more programs are configured to be executed by one or more processors, including computer-executable instructions for performing the following: Receiving interactive data sent by the user terminal after entering the ticket service; Based on the interaction data, the ticket agent of the ticket service is called to perform ticket processing; the ticket processing includes inputting the interaction data into a task generation model corresponding to the intention category of the interaction data to generate a task sequence for ticket processing, and executing the task sequence to obtain a ticket processing result; The bill processing result returned by the bill agent is obtained, service response data is generated according to the bill processing result, and is sent to the user terminal.

[0183] Another embodiment of a ticket service processing device based on an intelligent agent provided in this specification is as follows: Corresponding to the another agent-based ticket service processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another agent-based ticket service processing device, which is used to execute the another agent-based ticket service processing method provided above. Fig.13 A schematic diagram of the structure of another agent-based ticket service processing device provided for one or more embodiments of this specification.

[0184] The present embodiment provides an agent-based ticket service processing device, comprising: like Fig.13 As shown, the agent-based ticket service processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 1301 and memory 1302, and the memory 1302 may store one or more storage applications or data. Among them, the memory 1302 may be a temporary storage or a permanent storage. The application stored in the memory 1302 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the agent-based ticket service processing device. Furthermore, the processor 1301 may be configured to communicate with the memory 1302, and execute a series of computer executable instructions in the memory 1302 on the agent-based ticket service processing device. The agent-based ticket service processing device may also include one or more power supplies 1303, one or more wired or wireless network interfaces 1304, one or more input / output interfaces 1305, one or more keyboards 1306, etc.

[0185] In a specific embodiment, the agent-based ticket service processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the agent-based ticket service processing device, and the one or more programs are configured to be executed by one or more processors, including computer-executable instructions for performing the following: Obtain the interaction data submitted by the user on the interactive page of the ticket service; The interactive data is sent to the server to call the bill agent to process the bill; the bill processing includes inputting the interactive data into the corresponding task generation model to obtain the task sequence for bill processing and executing it to obtain the bill processing result; Receive the service response data generated and sent by the server according to the ticket processing result, and display it on the interactive page.

[0186] An embodiment of a computer-readable storage medium provided in this specification is as follows: Corresponding to the above-described agent-based ticket service processing method, based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0187] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions. When the computer-executable instructions are executed, the following process is implemented: Receiving interactive data sent by the user terminal after entering the ticket service; Based on the interaction data, the ticket agent of the ticket service is called to perform ticket processing; the ticket processing includes inputting the interaction data into a task generation model corresponding to the intention category of the interaction data to generate a task sequence for ticket processing, and executing the task sequence to obtain a ticket processing result; The bill processing result returned by the bill agent is obtained, service response data is generated according to the bill processing result, and is sent to the user terminal.

[0188] It should be noted that an embodiment of a computer-readable storage medium in this specification and an embodiment of an intelligent-based ticket service processing method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0189] Another computer-readable storage medium embodiment provided in this specification is as follows: Corresponding to the other agent-based ticket service processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another computer-readable storage medium.

[0190] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions. When the computer-executable instructions are executed, the following process is implemented: Obtain the interaction data submitted by the user on the interactive page of the ticket service; Sending the interactive data to the server to call the bill agent to process the bill; the bill processing includes inputting the interactive data into the corresponding task generation model to obtain the task sequence for bill processing and executing it to obtain the bill processing result; Receive the service response data generated and sent by the server according to the ticket processing result, and display it on the interactive page.

[0191] It should be noted that the embodiment of another computer-readable storage medium in this specification and the embodiment of another agent-based ticket service processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0192] An embodiment of a computer program product provided in this specification is as follows: Corresponding to the above-described agent-based ticket service processing method, based on the same technical concept, one or more embodiments of this specification also provide a computer program product.

[0193] A computer program product, comprising a computer program / instruction, which, when executed by a processor, implements the following steps: Receiving interactive data sent by the user terminal after entering the ticket service; Based on the interaction data, the ticket agent of the ticket service is called to perform ticket processing; the ticket processing includes inputting the interaction data into a task generation model corresponding to the intention category of the interaction data to generate a task sequence for ticket processing, and executing the task sequence to obtain a ticket processing result; The bill processing result returned by the bill agent is obtained, service response data is generated according to the bill processing result, and is sent to the user terminal.

[0194] It should be noted that an embodiment of a computer program product in this specification and an embodiment of an intelligent agent-based ticket service processing method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0195] Another computer program product embodiment provided in this specification is as follows: Corresponding to the other agent-based ticket service processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another computer program product.

[0196] A computer program product, comprising a computer program / instruction, which, when executed by a processor, implements the following steps: Obtain the interaction data submitted by the user on the interactive page of the ticket service; The interactive data is sent to the server to call the bill agent to process the bill; the bill processing includes inputting the interactive data into the corresponding task generation model to obtain the task sequence for bill processing and executing it to obtain the bill processing result; Receive the service response data generated and sent by the server according to the ticket processing result, and display it on the interactive page.

[0197] It should be noted that an embodiment of another computer program product in this specification and an embodiment of another agent-based ticket service processing method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned corresponding method, and the repeated parts will not be repeated.

[0198] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. For example, the device embodiment, equipment embodiment, computer-readable storage medium embodiment, and computer program product embodiment are similar to the method embodiment, so the description is relatively simple. To read the relevant contents of the device embodiment, equipment embodiment, computer-readable storage medium embodiment, and computer program product embodiment, please refer to the partial description of the method embodiment.

[0199] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0200] In the 1930s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements to method flows). However, with the development of technology, many of today's method flow improvements can be regarded as direct improvements to hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using hardware entity modules. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask chip manufacturers to design and produce dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0201] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0202] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0203] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0204] It should be understood by those skilled in the art that one or more embodiments of the present specification may be provided as a method, system or computer program product. Therefore, one or more embodiments of the present specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present specification may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0205] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable agent-based ticket service processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable agent-based ticket service processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0206] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable agent-based ticket service processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0207] These computer program instructions may also be loaded onto a computer or other programmable agent-based ticket service processing device, so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0208] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0209] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0210] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer-readable storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0211] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of further restrictions, the elements defined by the sentence "includes at least one ..." do not exclude the presence of other identical elements in the process, method, commodity or device including the elements.

[0212] One or more embodiments of the present specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0213] The above are only embodiments of this document and are not intended to limit this document. For those skilled in the art, this document may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this document should be included in the scope of the claims of this document.

Claims

1. A method for processing ticket services based on an intelligent agent, comprising: Receiving interactive data sent by the user terminal after entering the ticket service; Calling the ticket agent of the ticket service to process the ticket based on the interaction data; The bill processing includes inputting the interaction data into a task generation model corresponding to the intention category of the interaction data to generate a task sequence for bill processing, and executing the task sequence to obtain a bill processing result; The bill processing result returned by the bill agent is obtained, service response data is generated according to the bill processing result, and is sent to the user terminal.

2. According to the agent-based ticket service processing method of claim 1, the step of generating a task sequence for ticket processing comprises: Extracting multiple keywords from the interaction data, and selecting tasks to be configured that match the keywords in a preset task sequence; The keywords are configured in the corresponding tasks to be configured to obtain a plurality of bill processing tasks, and the task sequence is constructed based on the preset execution relationship of the tasks to be configured and the bill processing tasks.

3. According to the agent-based ticket service processing method of claim 1, the step of executing the task sequence to obtain the ticket processing result comprises: Reading a plurality of bill processing tasks included in the task sequence and the execution relationship between the bill processing tasks; The bill processing results are obtained by executing each bill processing task according to the execution relationship.

4. According to the agent-based ticket service processing method of claim 1, the step of executing the task sequence to obtain the ticket processing result comprises: Executing the query task in the task sequence to query the electronic receipts matching the keywords in the interaction data in the user's receipt collection and querying the bills associated with the electronic receipts; Executing the verification task in the task sequence to verify the electronic receipt and the bill according to the reimbursement verification rules; If the verification is passed by executing the reimbursement form generation task in the task sequence, the bill information of the electronic bill and the bill data of the bill are written into the reimbursement form to be configured to obtain the target reimbursement form.

5. According to the agent-based ticket service processing method of claim 1, the step of executing the task sequence to obtain the ticket processing result comprises: Executing the query task in the task sequence to query the user's ticket collection for an electronic ticket whose ticket information matches the time information, area information and / or merchant information configured in the query task; The sorting task in the task sequence is executed to sort the electronic bills obtained by the query according to the sorting method configured by the sorting task, and obtain the bill information of the sorted electronic bills.

6. The agent-based ticket service processing method according to claim 1, further comprising: A code scanning page is sent to the user terminal according to the bill application submitted by the user terminal, so that the bill agent is called to fill in the application information after the user terminal enters the bill service window of the merchant.

7. According to the agent-based ticket service processing method of claim 6, the application information filling comprises: Performing element recognition on the ticket service window to obtain text elements for ticket application; The user's ticket application information is written into the text area corresponding to the text element in the ticket service window; the ticket application information is determined according to the ticket application party selected by the user on the code scanning page.

8. According to the agent-based ticket service processing method of claim 1, the interaction data is obtained in the following manner: Acquire a preset interactive text triggered and submitted by a user on the interactive page of the ticket service, and use the preset interactive text as the interactive data; in, The preset interactive text is generated according to the bill information of the electronic bill to be reimbursed in the bill collection of the user.

9. According to the agent-based ticket service processing method of claim 1, after the steps of obtaining the ticket processing result returned by the ticket agent, generating service response data according to the ticket processing result and sending it to the user terminal are performed, the method further comprises: Calling the ticket agent to perform service processing based on the interactive text submitted by the user terminal; The interactive text is submitted after the interface configured on the interactive page of the ticket service is triggered; Sending the service text returned by the ticket agent to the user terminal; Among them, the service processing includes: detecting whether the intention category of the interactive text is a preset intention category; if not, inputting the interactive text and the bill information in the bill processing result into a large language model for service processing to obtain a service text.

10. The agent-based ticket service processing method according to claim 1, wherein generating service response data according to the ticket processing result comprises: Determine the data type of the data included in the bill processing result, and select a corresponding message template based on the data type; Writing the data contained in the bill processing result into the message template to obtain a service response message; Among them, the message template configures the service interface corresponding to the data type; the service interface includes: a reimbursement submission interface and / or a bill export interface.

11. The agent-based ticket service processing method according to claim 1, after the steps of obtaining the ticket processing result returned by the ticket agent, generating service response data according to the ticket processing result and sending it to the user terminal, further comprises: Obtaining a ticket processing request submitted by the user terminal; The ticket processing request is generated after the user triggers the service interface configured by the service response data; The electronic ticket of the user is service processed according to the ticket processing method corresponding to the ticket processing request, and the service processing result is sent to the user terminal.

12. The agent-based ticket service processing method according to claim 11, wherein the service processing of the user's electronic ticket according to the ticket processing method corresponding to the ticket processing request comprises: Filtering out the electronic invoice corresponding to the invoice information in the invoice processing request from the invoice collection of the user, and generating a invoice link for the electronic invoice; The bill link is sent to the bill recipient included in the bill processing request, so that the bill recipient downloads the electronic bill through the bill link.

13. The agent-based ticket service processing method according to claim 11, wherein the service processing of the user's electronic ticket according to the ticket processing method corresponding to the ticket processing request comprises: Obtain the reimbursement form included in the bill processing result, and query the data transmission interface of the reimbursement service associated with the user; The reimbursement form is used as an interface call input to call the data transmission interface for data transmission, so that the reimbursement service performs reimbursement processing based on the electronic receipt in the reimbursement form.

14. A method for processing ticket services based on an intelligent agent, comprising: Obtain the interaction data submitted by the user on the interactive page of the ticket service; Sending the interactive data to the server to call the bill agent for bill processing; The bill processing includes inputting the interaction data into a corresponding task generation model to obtain a task sequence for bill processing and executing the task sequence to obtain a bill processing result; Receive the service response data generated and sent by the server according to the ticket processing result, and display it on the interactive page.

15. The agent-based ticket service processing method according to claim 14, further comprising: After the user triggers the ticket application interface configured on the service page of the ticket service, a ticket application is generated and submitted to the server; Receive and display the code scanning page sent by the server, and enter the merchant's bill service window to fill in the application information after scanning the merchant's bill code; The application information is filled in by the server calling the bill intelligent entity; Submit a bill application to the merchant according to the confirmation instruction submitted by the user to obtain the electronic bill returned by the merchant and add it to the reimbursement item selected by the user on the code scanning page.

16. According to the agent-based ticket service processing method of claim 15, after the sub-step of submitting a ticket application to the merchant according to the confirmation instruction submitted by the user to obtain the electronic ticket returned by the merchant and add it to the reimbursement item selected by the user on the code scanning page is executed, it also includes: Sending the page return instruction submitted by the user to the server, so that the server returns a page based on the ticket application result; If the ticket application is successful, the interactive page of the ticket service returned by the server is obtained and displayed.

17. According to the agent-based ticket service processing method of claim 14, the interaction data is obtained in the following manner: Acquire the preset interaction text triggered and submitted by the user on the interaction page, and use the preset interaction text as the interaction data; in, The preset interactive text is generated according to the bill information of the electronic bill to be reimbursed in the bill collection of the user.

18. The agent-based ticket service processing method according to claim 14, wherein the receiving of the service response data generated and sent by the server according to the ticket processing result and after the interactive page display step is performed, further comprises: After detecting that the user triggers the interface corresponding to the interactive text configured on the interactive page, submitting the interactive text to the server; The service text issued by the server after calling the bill intelligent body for service processing based on the interactive text is obtained and displayed on the interactive page; the service processing includes calling a large language model based on the interactive text to generate service text.

19. The agent-based ticket service processing method according to claim 14, wherein the receiving of the service response data generated and sent by the server according to the ticket processing result and after the interactive page display step is performed, further comprises: If it is detected that the user triggers the service interface configured by the service response data, a ticket processing request is generated according to the configuration information of the service interface and submitted to the server; Receive and display the service processing result sent by the server after performing service processing on the user's electronic ticket according to the ticket processing method corresponding to the ticket processing request.

20. A ticket service processing device based on an intelligent agent, comprising: An interactive data receiving module, configured to receive interactive data sent by a user terminal after entering the ticket service; A bill agent calling module is configured to call the bill agent of the bill service to perform bill processing based on the interaction data; the bill processing includes inputting the interaction data into a task generation model corresponding to the intention category of the interaction data to generate a task sequence for bill processing, and executing the task sequence to obtain a bill processing result; The service response data generation module is configured to obtain the bill processing result returned by the bill agent, generate service response data according to the bill processing result and send it to the user terminal.

21. A ticket service processing device based on an intelligent agent, comprising: An interactive data acquisition module is configured to acquire interactive data submitted by a user on an interactive page of a ticket service; The interactive data sending module is configured to send the interactive data to the server to call the bill agent to perform bill processing; the bill processing includes inputting the interactive data into the corresponding task generation model to obtain a task sequence for bill processing and executing it to obtain a bill processing result; The service response data receiving module is configured to receive the service response data generated and sent by the server according to the ticket processing result, and display it on the interactive page.

22. A ticket service processing device based on an intelligent agent, comprising: processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: Receiving interactive data sent by the user terminal after entering the ticket service; Based on the interaction data, the ticket agent of the ticket service is called to perform ticket processing; the ticket processing includes inputting the interaction data into a task generation model corresponding to the intention category of the interaction data to generate a task sequence for ticket processing, and executing the task sequence to obtain a ticket processing result; The bill processing result returned by the bill agent is obtained, service response data is generated according to the bill processing result, and is sent to the user terminal.

23. A ticket service processing device based on an intelligent agent, comprising: processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: Obtain the interaction data submitted by the user on the interactive page of the ticket service; The interactive data is sent to the server to call the bill agent to process the bill; the bill processing includes inputting the interactive data into the corresponding task generation model to obtain the task sequence for bill processing and executing it to obtain the bill processing result; Receive the service response data generated and sent by the server according to the ticket processing result, and display it on the interactive page.

24. A computer-readable storage medium for storing computer-executable instructions, which implement the steps of the method of claim 1 or 14 when executed.

Images