Order query method and device, computer equipment and storage medium

Abstract

The invention relates to an order query method and device, computer equipment and a storage medium. The method comprises the steps of obtaining a data query request for an order, wherein the data query request carries an entity tag; determining a data query interface corresponding to the entity tag from a data query interface set; obtaining entity content corresponding to the entity label through the data query interface; and generating a query result of the order according to the entity content. By adopting the method, the order query efficiency can be improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to an order query method, apparatus, computer device, and storage medium. Background Art

[0002] In the existing order query process, developers need to perform interface customization development according to specific functional requirements, then obtain data entities from the database through the customized interface, and then assemble the data entities and return them through the interface.

[0003] In the above order query process, each data query interface can only be used for a specific function, and the function reuse rate is extremely low, resulting in a reduction in order query efficiency. Summary of the Invention

[0004] Based on this, it is necessary to provide an order query method, apparatus, computer device, and storage medium that can improve query efficiency for the above technical problems.

[0005] On the one hand, an order query method is provided. The method includes:

[0006] Obtain a data query request for an order, where the data query request carries an entity tag;

[0007] Determine a data query interface corresponding to the entity tag from a data query interface set;

[0008] Obtain entity content corresponding to the entity tag through the data query interface;

[0009] Generate a query result for the order according to the entity content.

[0010] In one embodiment, before the step of determining a data query interface corresponding to the entity tag from a data query interface set, the method further includes:

[0011] Classify the order data of the order;

[0012] Set corresponding candidate entity tags for each category of order data, and encapsulate corresponding candidate data query interfaces for each category of order data, where the candidate data query interfaces form the data query interface set;

[0013] Establish an association relationship between candidate entity tags and candidate data query interfaces corresponding to order data of the same category.

[0014] In one embodiment, the step of determining a data query interface corresponding to the entity tag from a data query interface set includes:

[0015] Determine a target entity label that matches the entity label from the candidate entity labels;

[0016] Set the candidate data query interface corresponding to the target entity label as the data query interface corresponding to the entity label.

[0017] In one embodiment, the step of obtaining the entity content corresponding to the entity label through the data query interface includes:

[0018] Obtain the order data of the corresponding category encapsulated by the data query interface;

[0019] Set the order data of the corresponding category as the entity content corresponding to the entity label.

[0020] In one embodiment, the step of generating the query result of the order according to the entity content includes:

[0021] Parse the entity content;

[0022] Assemble the parsed entity content according to a preset structure to generate the query result.

[0023] In one embodiment, the step of generating the query result of the order according to the entity content further includes:

[0024] Obtain the page display requirements of the terminal;

[0025] Filter the entity content according to the page display requirements to generate the query result.

[0026] On the other hand, an order query device is provided, and the device includes:

[0027] A request acquisition module, configured to acquire a data query request for an order, where the data query request carries an entity label;

[0028] An interface acquisition module, configured to determine the data query interface corresponding to the entity label from a set of data query interfaces;

[0029] A content acquisition module, configured to obtain the entity content corresponding to the entity label through the data query interface;

[0030] A result generation module, configured to generate a query result of the order according to the entity content.

[0031] In one embodiment, the order query device further includes:

[0032] A classification module, configured to classify the order data of the order;

[0033] A setting module, configured to set corresponding candidate entity tags for each category of order data, and encapsulate corresponding candidate data query interfaces for each category of order data, wherein the candidate data query interfaces form the data query interface set;

[0034] An establishment module, configured to establish an association relationship between the candidate entity tags corresponding to the order data of the same category and the candidate data query interfaces.

[0035] In one embodiment, the interface acquisition module includes:

[0036] A tag acquisition sub-module, configured to determine a target entity tag that matches the entity tag from the candidate entity tags;

[0037] A setting sub-module, configured to set the candidate data query interface corresponding to the target entity tag as the data query interface corresponding to the entity tag.

[0038] In one embodiment, the content acquisition module includes:

[0039] An order data acquisition sub-module, configured to acquire the order data of the corresponding category encapsulated by the data query interface;

[0040] A content setting sub-module, configured to set the order data of the corresponding category as the entity content corresponding to the entity tag.

[0041] In one embodiment, the result generation module includes:

[0042] An analysis sub-module, configured to analyze the entity content;

[0043] A first query result generation sub-module, configured to assemble the analyzed entity content according to a preset structure to generate the query result.

[0044] In one embodiment, the result generation module includes:

[0045] A requirement acquisition sub-module, configured to acquire the page display requirements of the terminal;

[0046] A second query result generation sub-module, configured to screen the entity content according to the page display requirements to generate the query result.

[0047] On the other hand, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the above method are implemented.

[0048] In another aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0049] For the above order query method, device, computer device and storage medium, first determine the data query interface through the entity tag, and then directly obtain the entity content through the data query interface to generate the query result of the order, so as to improve the efficiency of order query by increasing the reuse rate of the data query interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 It is an application environment diagram of the order query method provided by an embodiment of the present invention;

[0051] Figure 2 It is another application environment diagram of the order query method provided by an embodiment of the present invention;

[0052] Figure 3 It is a schematic flowchart of the order query method provided by an embodiment of the present invention;

[0053] Figure 4 It is another schematic flowchart of the order query method provided by an embodiment of the present invention;

[0054] Figure 5 It is a schematic diagram of the scenario of the order query method provided by an embodiment of the present invention;

[0055] Figure 6 It is a structural block diagram of the order query device provided by an embodiment of the present invention;

[0056] Figure 7 It is an internal structure diagram of the computer device provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0057] In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0058] The order query method provided by the present application can be applied to, for example Figure 1In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The user operates on the interface of the terminal 102 to generate a data query request for the order, and the data query request carries an entity tag. The terminal 102 sends the data query request to the server 104. After obtaining the data query request for the order, the server 104 first determines the data query interface corresponding to the entity tag from the data query interface set, then obtains the entity content corresponding to the entity tag through the data query interface, and finally generates a query result for the order according to the entity content.

[0059] Among them, the terminal 102 can be but is not limited to various personal computers, laptop computers, smart phones, tablet computers, and portable wearable devices, and the server 104 can be implemented by an independent server or a server cluster composed of multiple servers. As Figure 2 shown, when the server 104 includes the server 1041 and the server 1042, the terminal 102 sends the data query request to the server 1041. After obtaining the data query request for the order, the server 1041 determines the data query interface corresponding to the entity tag from the data query interface set, and then requests the server 1042 to obtain the entity content corresponding to the entity tag through the data query interface. After receiving the acquisition request, the server 1042 sends the entity content to the server 1041. After receiving the entity content, the server 1041 generates a query result for the order according to the entity content.

[0060] In one embodiment, as Figure 3 shown, a method for querying an order is provided. Taking the server in Figure 1 as an example, the method includes the following steps:

[0061] Step S101, obtain a data query request for the order, and the data query request carries an entity tag;

[0062] Each order includes a large amount of order data, such as order classification, order number, commodity type, commodity detailed information, and order time, etc. In the embodiment of the present application, entity tags are used to represent orders and order data. For example, the entity tag of a certain order is set to "insurance order" to represent that the classification of this order is an insurance order. The entity tag of a certain insurance order is set to "order data" to represent all the order data corresponding to this insurance order.

[0063] Different order tags can be set for different categories of order data. Taking insurance orders as an example, order tags such as insurance type information "risk", customer information "custom", claim information "claim", endorsement information "edor", and renewal information "renewal" can be set. For example, the entity tag of a certain insurance order is set to "risk" to represent the order related to the insurance type in this insurance order.

[0064] Trigger and generate an order query request according to the functional requirements. This order query request can be set in the format of a message as follows:

[0065]

[0066] After parsing the above data query request, entity tags "risk", "customer", and "claim" can be obtained.

[0067] Step S102, determine the data query interface corresponding to the entity tag from the data query interface set;

[0068] The data query interface set includes multiple data query interfaces. Each data query interface encapsulates a category of order data. Since entity tags are also used to represent different categories of order data, an association relationship between the data query interface and the entity tag can be established in advance based on the order data of the same category. In this way, the purpose of determining the data query interface according to the entity tag can be achieved subsequently.

[0069] Step S103, obtain the entity content corresponding to the entity tag through the data query interface;

[0070] The order data encapsulated by the data query interface can be obtained through the data query interface. In one embodiment, the order data can be directly set as the entity content corresponding to the entity tag.

[0071] Step S104, generate a query result of the order according to the entity content.

[0072] In one embodiment, the entity content can be parsed, and then the parsed entity content can be assembled according to a preset structure to generate a query result. Suppose the entity content corresponding to the entity tag "RISK" is: CONTNO: 18200000000001, RISKNAME: a certain annuity insurance, STARTDATE: 2023-01-01, ENDDATE: 2099-01-01, INSUYEAR: lifetime, CVALIDATE: 2023-01-01. The entity content corresponding to the entity tag "CUSTOMER" is: APPNTNO: A0000001, INSUREDNO: I000001, APPNTNAME: applicant, INSUREDNAME: insured, APPNTADDRESS: No. 2, Changjiang Road, a certain county, a certain city, a certain province, INSUREDADDRESS: No. 4, Zhujiang Road, a certain county, a certain city, a certain province. The entity content corresponding to the entity tag "CLAIM" is: CLAIMNO: E000001, REASON: disability due to a car accident, GETMONEY: 12500, CLAIMCVALIDATE: 2023-05-01. Assembling the above entity content into a message according to the format of the standard message can generate the following query result:

[0073]

[0074] In one embodiment, it is also possible to obtain the page display requirements of the terminal, and screen the entity content according to the page display requirements to generate a query result. For example, when the page display requirement is to only display a part of the entity content, the parts of the entity content that do not need to be displayed can be deleted according to this page display requirement.

[0075] The order query method of the present application first determines the data query interface through the entity tag, and then directly obtains the entity content through the data query interface to generate the query result of the order, thereby improving the efficiency of order query by increasing the reuse rate of the data query interface.

[0076] Furthermore, as Figure 4 shown, the present application also provides an order query method, including the following steps:

[0077] Step S201, classify the order data of the order.

[0078] Step S202, set corresponding candidate entity tags for each category of order data, and encapsulate corresponding candidate data query interfaces for each category of order data, wherein the candidate data query interfaces form a data query interface set;

[0079] Step S203, establish an association relationship between the candidate entity labels corresponding to the order data of the same category and the candidate data query interfaces.

[0080] Step S204, obtain a data query request for the order, where the data query request carries an entity label;

[0081] Step S205, determine a target entity label that matches the entity label from the candidate entity labels;

[0082] Step S206, set the candidate data query interface corresponding to the target entity label as the data query interface corresponding to the entity label.

[0083] Step S207, obtain the order data of the corresponding category encapsulated by the data query interface;

[0084] Step S208, set the order data of the corresponding category as the entity content corresponding to the entity label.

[0085] Step S209, generate a query result for the order according to the entity content.

[0086] The order data can be classified according to features. For example, classifying the order data of an insurance order by features can be divided into insurance type information, customer information, claim information, endorsement information, renewal information, withdrawal information, and liability information, etc. Among them, the insurance type information includes the policy number, insurance type name, insurance start date, and insurance end date. The customer information includes the name of the applicant and the name of the insured. The claim information includes the claim number, cause of loss, and indemnity amount. The endorsement information includes the endorsement number and endorsement type. The renewal information includes the number of renewals.

[0087] As Figure 5 shown, the order data of an insurance order is divided into five categories. One category is the order data related to the insurance type, one category is the order data related to renewal, one category is the order data related to endorsement, one category is the order data related to the customer, and the last category is the order data related to claims.

[0088] For each category of order data, corresponding candidate entity labels are set, which are: "insurance type information", "renewal information", "endorsement information", "customer information", and "claim information". Among them, "insurance type information" represents the order data related to the insurance type, "renewal information" represents the order data related to renewal, "endorsement information" represents the order data related to endorsement, "customer information" represents the order data related to the customer, and "claim information" represents the order data related to claims.

[0089] For each type of order data, a corresponding candidate data query interface is encapsulated. When it is necessary to call this type of order data, it can be obtained by accessing the corresponding candidate data query interface. Among them, the candidate data query interfaces include data query interfaces 1 - 5. Data query interface 1 is used to encapsulate order data related to insurance types, data query interface 2 is used to encapsulate order data related to renewal, data query interface 3 is used to encapsulate order data related to policy maintenance, data query interface 4 is used to encapsulate order data related to customers, and data query interface 5 is used to encapsulate order data related to claims.

[0090] In summary, since each type of order data corresponds to a candidate entity tag and a candidate data query interface, an association relationship can be established between the candidate entity tag and the candidate data query interface corresponding to the order data of the same category, as Figure 5 shown.

[0091] When a data query request for an order is obtained, the data query request is parsed to obtain the entity tag it carries. Then, a target entity tag that matches this entity tag is determined from the candidate entity tags. Next, the candidate data query interface corresponding to the target entity tag is set as the data query interface corresponding to the entity tag. Then, the order data of the corresponding category encapsulated by the data query interface is obtained. The order data of the corresponding category is set as the entity content corresponding to the entity tag.

[0092] Assume the entity tag is "Renewal Information". After comparing this entity tag with the Figure 5 candidate entity tags, the matching target entity tag can be obtained as "Renewal Information". The candidate data query interface corresponding to the target entity tag "Renewal Information" is: Data Query Interface 4. Since Data Query Interface 4 encapsulates the order data related to renewal "Policy Number: 18200000000001 Renewal Premium: 15000 Renewal Times: 1", the above order data can be used as the entity content corresponding to the entity tag.

[0093] Finally, the entity content can be combined and assembled into a message in the format of a standard message to obtain the query result of the order.

[0094] In the above order query method, first, the data query interface is determined through the entity tag, and then the entity content is directly obtained through the data query interface to generate the query result of the order, thereby improving the efficiency of order query by increasing the reuse rate of the data query interface.

[0095] It should be understood that although Figure 3-4The steps in the flowchart are shown in sequence according to the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise clearly stated in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 3-4 at least a portion of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a portion of other steps or sub-steps or stages of other steps.

[0096] In one embodiment, as Figure 6 shown, an order query device 60 is provided, including: a request acquisition module 601, an interface acquisition module 602, a content acquisition module 603, and a result generation module 604, where: the request acquisition module 601 is configured to acquire a data query request for an order, and the data query request carries an entity tag; the interface acquisition module 602 is configured to determine a data query interface corresponding to the entity tag from a set of data query interfaces; the content acquisition module 603 is configured to acquire entity content corresponding to the entity tag through the data query interface; and the result generation module 604 is configured to generate a query result for the order according to the entity content.

[0097] In one embodiment, the order query device 60 further includes: a classification module, a setting module, and an establishment module. Among them, the classification module is configured to classify the order data of the order; the setting module is configured to set a corresponding candidate entity tag for each category of order data, and encapsulate a corresponding candidate data query interface for each category of order data, where the candidate data query interfaces form the set of data query interfaces; and the establishment module is configured to establish an association relationship between the candidate entity tags and the candidate data query interfaces corresponding to the order data of the same category.

[0098] In one embodiment, the interface acquisition module 602 includes: a tag acquisition sub-module and a setting sub-module. Among them, the tag acquisition sub-module is configured to determine a target entity tag that matches the entity tag from the candidate entity tags; and the setting sub-module is configured to set the candidate data query interface corresponding to the target entity tag as the data query interface corresponding to the entity tag.

[0099] In one embodiment, the content acquisition module 603 includes: an order data acquisition sub-module and a content setting sub-module. Among them, the order data acquisition sub-module is configured to acquire the order data of the corresponding category encapsulated by the data query interface; and the content setting sub-module is configured to set the order data of the corresponding category as the entity content corresponding to the entity tag.

[0100] In one embodiment, the result generation module 604 includes: a parsing sub-module and a first query result generation sub-module. Among them, the parsing sub-module is used to parse the entity content; the first query result generation sub-module is used to assemble the parsed entity content according to a preset structure to generate the query result.

[0101] In one embodiment, the result generation module 604 includes: a requirement acquisition sub-module and a second query result generation sub-module. Among them, the requirement acquisition sub-module is used to acquire the page display requirements of the terminal; the second query result generation sub-module is used to screen the entity content according to the page display requirements to generate the query result.

[0102] For the specific limitations of the order query device, reference can be made to the limitations on the order query method in the foregoing text, which will not be elaborated here. Each module in the above order query device can be implemented in whole or in part by software, hardware, and their combination. The above modules can be embedded in the processor of the computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above modules.

[0103] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 7 shown. The computer device includes a processor, a memory, a network interface, and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store order data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it implements an order query method.

[0104] Those skilled in the art can understand that Figure 7 the structure shown in

[0105] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the following steps are implemented:

[0106] Obtain a data query request for an order, where the data query request carries an entity tag; determine the data query interface corresponding to the entity tag from a set of data query interfaces; obtain the entity content corresponding to the entity tag through the data query interface; generate a query result for the order according to the entity content.

[0107] In one embodiment, when the processor executes a computer program, the following steps are further implemented:

[0108] Classify the order data of the order; set corresponding candidate entity tags for each category of order data, and encapsulate corresponding candidate data query interfaces for each category of order data, where the candidate data query interfaces form the set of data query interfaces; establish an association relationship between the candidate entity tags and the candidate data query interfaces corresponding to the order data of the same category.

[0109] In one embodiment, when the processor executes a computer program, the following steps are further implemented:

[0110] Determine a target entity tag that matches the entity tag from the candidate entity tags; set the candidate data query interface corresponding to the target entity tag as the data query interface corresponding to the entity tag.

[0111] In one embodiment, when the processor executes a computer program, the following steps are further implemented:

[0112] Obtain the order data of the corresponding category encapsulated by the data query interface; set the order data of the corresponding category as the entity content corresponding to the entity tag.

[0113] In one embodiment, when the processor executes a computer program, the following steps are further implemented:

[0114] Parse the entity content; assemble the parsed entity content according to a preset structure to generate the query result.

[0115] In one embodiment, when the processor executes a computer program, the following steps are further implemented:

[0116] Obtain the page display requirements of the terminal; screen the entity content according to the page display requirements to generate the query result.

[0117] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0118] Obtain a data query request for an order, where the data query request carries an entity tag; determine the data query interface corresponding to the entity tag from a set of data query interfaces; obtain the entity content corresponding to the entity tag through the data query interface; generate a query result for the order based on the entity content.

[0119] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0120] Classify the order data of the order; set corresponding candidate entity tags for each category of order data, and encapsulate corresponding candidate data query interfaces for each category of order data, where the candidate data query interfaces form the set of data query interfaces; establish an association relationship between the candidate entity tags and the candidate data query interfaces corresponding to the order data of the same category.

[0121] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0122] Determine a target entity tag that matches the entity tag from the candidate entity tags; set the candidate data query interface corresponding to the target entity tag as the data query interface corresponding to the entity tag.

[0123] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0124] Obtain the order data of the corresponding category encapsulated by the data query interface; set the order data of the corresponding category as the entity content corresponding to the entity tag.

[0125] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0126] Parse the entity content; assemble the parsed entity content according to a preset structure to generate the query result.

[0127] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented:

[0128] Obtain the page display requirements of the terminal; filter the entity content according to the page display requirements to generate the query result.

[0129] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0130] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0131] The above-described embodiments merely represent several implementation manners of the present application. The description is relatively specific and detailed, but it should not be construed as a limitation on the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application should be subject to the appended claims.

Claims

1. An order query method, characterized in that, it includes: Obtain a data query request for the order, and the data query request carries an entity label; Determine the data query interface corresponding to the entity label from the data query interface set; Obtain the entity content corresponding to the entity label through the data query interface; Generate a query result for the order according to the entity content.

2. The order query method according to claim 1, characterized in that, Before the step of determining the data query interface corresponding to the entity label from the data query interface set, it further includes: Classify the order data of the order; Set corresponding candidate entity labels for each category of order data, and encapsulate corresponding candidate data query interfaces for each category of order data, wherein the candidate data query interfaces form the data query interface set; Establish an association relationship between the candidate entity labels and the candidate data query interfaces corresponding to the order data of the same category.

3. The order query method according to claim 2, characterized in that, The step of determining the data query interface corresponding to the entity label from the data query interface set includes: Determine a target entity label that matches the entity label from the candidate entity labels; Set the candidate data query interface corresponding to the target entity label as the data query interface corresponding to the entity label.

4. The order query method according to claim 2, characterized in that, The step of obtaining the entity content corresponding to the entity label through the data query interface includes: Obtain the order data of the corresponding category encapsulated by the data query interface; Set the order data of the corresponding category as the entity content corresponding to the entity label.

5. The order query method according to claim 1, characterized in that, The step of generating the query result for the order according to the entity content includes: Parse the entity content; Assemble the parsed entity content according to a preset structure to generate the query result.

6. The order query method according to claim 1, characterized in that, The step of generating the query result for the order according to the entity content further includes: Obtain the page display requirements of the terminal; Filter the entity content according to the page display requirements to generate the query result.

7. An order query device, characterized in that, the device includes: A request acquisition module, configured to obtain a data query request for the order, and the data query request carries an entity label; An interface acquisition module, configured to determine the data query interface corresponding to the entity label from the data query interface set; A content acquisition module, configured to obtain the entity content corresponding to the entity label through the data query interface; A result generation module, configured to generate a query result for the order according to the entity content.

8. The order query device according to claim 7, characterized in that, it further includes: A classification module, configured to classify the order data of the order; A setting module, configured to set corresponding candidate entity tags for each type of order data and encapsulate corresponding candidate data query interfaces for each type of order data, wherein the candidate data query interfaces form the data query interface set; An establishing module, configured to establish an association relationship between the candidate entity tags corresponding to the order data of the same category and the candidate data query interfaces.

9. A computer device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, when the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium, on which a computer program is stored, wherein, when the computer program is executed by the processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images