Self-service cabinet service method and data processing method and device

Abstract

The invention relates to the technical field of computers, and provides a self-service cabinet service method and a data processing method and device.The self-service cabinet service method comprises the steps that a back-end system creates a transaction containing a transaction number, a transaction name and a transaction result based on a received activation request sent by a cabinet front-end system; the cabinet front-end system sends an activation response containing the transaction number; receiving a non-exit service request sent by the cabinet front-end system, and replacing a service name handled in the created transaction with a specific service request interface name by using the transaction number; receiving a service operation response sent by the host, and replacing a service handling result in the created transaction with a state code of the service response; and after receiving a service exit request sent by the cabinet front-end system, returning a service exit response, and completing the transaction represented by the transaction number. A transaction mechanism is introduced into business interaction, associated data of transactions and businesses are produced, a specific scene can be identified, and the service improvement effect of the self-service cabinet can be evaluated.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a self-service machine service method, a data processing method and a device. Background Art

[0002] With the continuous development of self-service kiosk services, a wide range of services are supported, including not only traditional check-in, baggage check-in, rescheduling, and itinerary, but also personalized services provided by airlines, such as WIFI sales, paid upgrades, etc. These services are supported differently by different airlines and terminals. The support provided by self-service kiosk services for diverse needs varies, and the satisfaction level of airlines also varies. In order to improve customer satisfaction, self-service kiosk services have been continuously improved and optimized, but the effects of many optimizations cannot be evaluated objectively. The following two application scenarios are used as examples:

[0003] Scenario 1: Guide passengers to scan their ID card multiple times until successful

[0004] As time goes by, the recognition rate of passport readers on some self-service kiosk machines is low, resulting in passengers' failure to swipe their passports. Many passengers do not want to know the reason and go directly to the manual counter to handle the business. In order to increase passenger stickiness and improve the utilization rate of self-service kiosk machines, the business process has been improved, and passengers are guided to swipe their documents multiple times through animated instructions.

[0005] Scenario 2: Guiding passengers to pick up tickets using flight numbers

[0006] When ordering some international tickets from foreign airlines, ID is not a mandatory item. If a passenger uses a passport to handle the transaction, the corresponding ticket information cannot be found in the background, resulting in the inability to handle the transaction. Later, this process was optimized. When this error is identified, a dialog box pops up to guide passengers to use other methods to find tickets.

[0007] The optimization effects of the above two scenarios are difficult to evaluate the effectiveness of the optimization process through current statistical means. Table 1 below is the content recorded in the current daily statistical table:

[0008] Table 1

[0009]

[0010] Because the statistics of the backend system are generally based on the number of successes and failures of the business interface. Since the number of passengers processed before and after the improvement is different, the number of failures and successes may increase or decrease. In this case, it is difficult to evaluate the relationship between the conversion rate of successful processing and the improvement.

[0011] In view of this, it is necessary to provide a self-service kiosk service method, a data processing method and a device, so that it is possible to evaluate the relationship between the successful conversion rate and the improvement. Summary of the invention

[0012] To solve the above problems, the present invention provides a self-service kiosk service method, a data processing method and a device. By introducing a transaction mechanism in business interaction, the associated data of transactions and businesses are generated, which can identify specific scenarios for evaluating the improvement effect of self-service kiosk services.

[0013] In a first aspect, a self-service machine service method is provided, the method comprising:

[0014] The back-end system receives the activation request sent by the cabinet front-end system;

[0015] The back-end system creates a transaction and prints the transaction to a business log file and stores it in the database, where the transaction includes: transaction number, name of the business being handled, and result of the business being handled;

[0016] The back-end system sends an activation response to the cabinet front-end system, wherein the activation response includes a transaction number;

[0017] The back-end system receives the non-exit service request sent by the cabinet front-end system, wherein the non-exit service request includes: a transaction number, a specific service request interface name and service data corresponding to the specific service;

[0018] The backend system uses the transaction number to replace the name of the business handled in the created transaction with the specific business request interface name, and sends a business operation request to the host based on the business data corresponding to the specific business;

[0019] The back-end system receives the business operation response sent by the host, wherein the business operation response includes a business response status code and business response data;

[0020] The back-end system uses the transaction number to replace the result of the business in the created transaction with the status code of the business response, and prints the transaction to the business log file and stores it in the database;

[0021] The backend system sends a non-exit business response to the frontend system, wherein the non-exit business response includes: a transaction number, a business response status code, and business response data;

[0022] The back-end system receives the exit service request sent by the cabinet front-end system, completes the transaction represented by the transaction number, and prints the transaction to the business log file and stores it in the database, wherein the exit service request includes the transaction number;

[0023] The back-end system sends an exit service response to the cabinet front-end system.

[0024] Furthermore, the backend system creates a transaction, including:

[0025] The backend system intercepts the activation request through the interceptor, creates a transaction, and prints the transaction to the business log file and stores it in the database;

[0026] The backend system uses the transaction number to replace the service name in the created transaction with the specific service request interface name, including:

[0027] The backend system intercepts the non-exit business request through the interceptor, and uses the transaction number to replace the business name handled in the created transaction with the specific business request interface name;

[0028] The backend system uses the transaction number to replace the result of the business in the created transaction with the status code of the business response, including:

[0029] The backend system intercepts the non-exit business response through the interceptor, and uses the transaction number to replace the result of the business in the created transaction with the status code of the business response;

[0030] Confirm the completion of the transaction indicated by the transaction number, including:

[0031] The back-end system intercepts the exit business request through the interceptor and confirms the completion of the transaction represented by the transaction number.

[0032] In a second aspect, a self-service machine service device is provided, the device comprising: a receiving module, a transaction management module and a sending module; wherein:

[0033] The receiving module is used to receive the activation request sent by the cabinet front-end system, trigger the transaction management module to create a transaction; receive the non-exit service request sent by the cabinet front-end system, trigger the transaction management module to update the transaction, receive the service operation response sent by the host, receive the exit service request sent by the cabinet front-end system, and complete the transaction represented by the transaction number, wherein the non-exit service request includes: the transaction number, the specific service request interface name and the service data corresponding to the specific service; the service operation response includes the service response status code and service response data; wherein the exit service request includes the transaction number;

[0034] The transaction management module is used to create transactions and print the transactions to the business log file and store them in the database, wherein the transaction includes: transaction number, name of the business to be handled and result of the business to be handled; using the transaction number, the name of the business to be handled in the created transaction is replaced with a specific business request interface name; using the transaction number, the result of the business to be handled in the created transaction is replaced with a status code of the business response, and the transaction is printed to the business log file and stored in the database;

[0035] The sending module is used to send an activation response, a non-exit business response or an exit business response to the front-end system, triggering the transaction management module to update the transaction using the non-exit business response, wherein the activation response includes: the transaction number; the non-exit business response includes: the transaction number, the status code of the business response and the business response data; the exit business response includes: the status code of the exit business response.

[0036] In a third aspect, a self-service machine service method is provided, comprising:

[0037] The cabinet front-end system sends an activation request to the back-end system so that the cabinet back-end system can create a transaction, wherein the transaction includes: transaction number, name of the business being handled and result of the business being handled;

[0038] The cabinet front-end system receives the activation response sent by the back-end system, wherein the activation response includes the transaction number;

[0039] The transaction number in the cabinet front-end system cache activation response;

[0040] The cabinet front-end system sends a non-exit service request to the cabinet back-end system, so that the back-end system can use the transaction number to replace the service name handled in the transaction with the specific service request interface name, wherein the non-exit service request includes: the cached transaction number, the specific service request interface name and the service data corresponding to the specific service;

[0041] The cabinet front-end system receives the non-exit service response sent by the cabinet back-end system, so that the back-end system uses the transaction number to replace the result of the service in the transaction with the status code of the service response; wherein the non-exit service response includes: the transaction number, the status code of the service response and the service response data;

[0042] The cabinet front-end system caches the transaction number in the non-exit business response;

[0043] The cabinet front-end system sends a service exit request to the cabinet back-end system, wherein the service exit request includes a transaction number;

[0044] The cabinet front-end system deletes the cached transaction number;

[0045] The cabinet front-end system receives the exit service response sent by the cabinet back-end system, wherein the exit service response includes a status code of the exit service response.

[0046] In a fourth aspect, a self-service machine service device is provided, comprising: a sending module, a cache management module and a receiving module; wherein:

[0047] The sending module is used to send an activation request to the back-end system so that the cabinet back-end system can create a transaction; send a non-exit service request to the cabinet back-end system so that the back-end system can use the transaction number to replace the service name handled in the transaction with a specific service request interface name; send a non-exit service request to the cabinet back-end system so that the cabinet back-end system can complete the transaction; wherein the transaction includes: the transaction number, the name of the service handled and the result of the service handled; the non-exit service request includes: the cached transaction number, the specific service request interface name and the service data corresponding to the specific service;

[0048] A receiving module, used to receive an activation response sent by a backend system; receive a non-exit service response sent by a cabinet backend system, and receive an exit service response sent by a cabinet backend system; wherein the activation response includes a transaction number, and the non-exit service response includes: a transaction number, a status code of the service response, and service response data; and the exit service response includes a status code of the exit service response;

[0049] The cache management module is used to cache the transaction number in the activation response when the receiving module receives the cache response; cache the transaction number in the non-exit service response when the receiving module receives the non-exit response; and delete the cached transaction number when the sending module sends an exit service request.

[0050] A fifth aspect provides a data processing method, the method comprising:

[0051] Creating a template for the first index of the database, wherein the template for the first index is transaction content, and the transaction content includes: transaction number, name of the business being handled, and result of the business being handled;

[0052] Collecting logs from the business log file, and writing the collected log content into the transaction content in the first index template to obtain the original log, wherein the business log file is generated in the process of performing the self-service machine service using the self-service machine service method described above;

[0053] According to the aggregation query conditions and aggregation calculation template, call the database aggregation interface to aggregate the original logs within the start time and end time to obtain the aggregation results of the original logs. The aggregation query conditions include: start time, end time and the name of the business handled; the aggregation calculation template includes: transaction number, business result handled, and business name handled;

[0054] Creating a template for a second index of the database, wherein the template for the second index is an aggregation result;

[0055] Write the aggregation result into the template of the second index of the database.

[0056] Furthermore, the transaction also includes: the cabinet configuration information and group identifier contained in the activation request, the cabinet configuration information displays the hierarchical information to which the cabinet belongs: from top to bottom, the hierarchical information is airline, terminal, self-service cabinet, and self-service cabinet host name, and the group identifier is obtained by using a hash algorithm on the transaction number and taking the modulus of the generated hash value; the aggregate query condition also includes: the group identifier;

[0057] According to the aggregation query conditions and aggregation calculation template, call the database aggregation interface to aggregate the original logs within the start time and end time, including:

[0058] According to the aggregation query conditions and aggregation calculation template, the level information of the cabinet is used as the aggregation calculation condition, and the aggregation interface of the database is called to aggregate the original logs within the start time and end time.

[0059] In a sixth aspect, a data processing device is provided, the device comprising: an index creation module, a collection module, an aggregation module and a writing module; wherein:

[0060] An index creation module is used to create a template for the first index and a template for the second index of the database, wherein the template for the first index is the transaction content, which includes: transaction number, name of the business handled and result of the business handled; the template for the second index is the aggregation result;

[0061] A collection module, used for collecting business log files, wherein the business log files are generated in the process of using the self-service machine service device to provide self-service machine services;

[0062] The aggregation module is used to call the aggregation interface of the database to aggregate the original logs within the start time and end time according to the aggregation query conditions and aggregation calculation templates to obtain the aggregation results of the original logs. The aggregation query conditions include: start time, end time and the name of the business handled; the aggregation calculation template includes: transaction number, business result handled, and business name handled;

[0063] The writing module is used to write the collected log content into the transaction content in the first index template, obtain the original log, and write the aggregation result into the template of the second index of the database.

[0064] In a seventh aspect, an electronic device is provided, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0065] Memory, used to store computer programs;

[0066] The processor is used to implement the steps of the above method when executing the program stored in the memory.

[0067] According to an eighth aspect, a computer storage medium is provided, wherein a computer program is stored in the computer storage medium, and the computer program implements the steps of the above method when executed by a processor.

[0068] Compared with the prior art, the present invention has the following advantages:

[0069] 1. Introduce transactions, associate transactions with businesses in requests and responses, and generate business log files after the associated transactions, so that the log files can be processed and specific scenarios can be identified, which can be used to evaluate the improvement effect of self-service counter services;

[0070] 2. Creating indexes for the collected logs can effectively reduce data redundancy; defining aggregation and grouping transactions by transaction number avoids the problem of unbalanced transaction grouping that may be caused by fixed grouping methods, thereby improving the efficiency of aggregation and avoiding the problems of long aggregation time and large data volume caused by excessive transaction data volume.

[0071] Other features and advantages of the present disclosure will be described in the following description, and partly become apparent from the description, or be understood by implementing the present disclosure. The purpose and other advantages of the present disclosure can be realized and obtained by the structures pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0073] Figure 1 A schematic diagram of a self-service kiosk service system component according to an embodiment of the present disclosure is shown;

[0074] Figure 2 A schematic diagram of a data processing method implementation path according to an embodiment of the present disclosure is shown;

[0075] Figure 3 A parent flow chart of a self-service machine service system according to an embodiment of the present disclosure is shown;

[0076] Figure 4 A sub-flow chart of a self-service machine service system according to an embodiment of the present disclosure is shown;

[0077] Figure 5 A technical architecture diagram of a self-service machine service method according to an embodiment of the present disclosure is shown;

[0078] Figure 6 A business sequence diagram of a self-service machine service method according to an embodiment of the present disclosure is shown;

[0079] Figure 7 A business sequence diagram of a data processing method based on a self-service kiosk service method according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0080] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0081] First, the nouns involved in the embodiments of the present disclosure are explained:

[0082] Self-service kiosk service: Based on the service interface of the passenger service system and the service interface provided by third-party systems such as airlines, the workflow of actual business scenarios such as passenger check-in, baggage delivery, additional service sales, ticket change, itinerary printing, flight delay certificate, etc. is integrated to provide airlines with comprehensive passenger self-service kiosk services for passengers.

[0083] KIOSK: refers to the carrier equipment of self-service products in transportation places such as airports and stations, that is, self-service equipment or "cabinet". Each KIOSK has a unique ID.

[0084] AKG front-end: A front-end application deployed on the KIOSK for passengers to use. It provides passengers with services such as ticket collection, rescheduling, and check-in.

[0085] Backend system: A backend system that provides data and verification services to KIOSK and writes business records into the log system.

[0086] KCMC: Human-machine intelligent collaborative management and control platform is a unified operation management system for KIOSK. It provides a graphical management and operation interface for airline staff and obtains valuable report information by reading the log system.

[0087] In the embodiment of the present disclosure, in view of the introduction of transactions in the self-service teller service system, the composition of the self-service teller service system introducing the transactions is first described, and then the transaction definition and transaction-related data processing are described. Then, the improvements made in the front-end system, back-end system, and database after the introduction of the transactions are described. Finally, through the business execution process after the associated transactions, the scheme of the embodiment of the present disclosure is described in detail.

[0088] 1. Introduce a self-service system for transactions

[0089] The self-service kiosk service modules consist of the following components Figure 1 As shown in the figure, it mainly consists of AKG, backend system, ElasticSearch database and KCMC. Among them, Elastic Search database is referred to as ES.

[0090] Passengers interact with AKG's UI, and the business process data is maintained by the transaction management module of the back-end system. When a passenger submits a request, such as printing a boarding pass, the business module of the back-end system will combine the AKG request parameters and the transaction management data to perform business processing, and then write the transaction number and business processing result (status code) to the business log stored in Elastic Search. In normal cases, the status code is 0, and in abnormal cases, there is a corresponding error code.

[0091] KCMC can check the business log to find out the status code of each interface, see Table 1 in the background technology. According to the above analysis, it is difficult to identify specific business scenarios with this table. In order to achieve the results in Table 2 above, a new aggregation module needs to be introduced. After the first step, the aggregation module reads the business log regularly. In the second step, the aggregation module writes the aggregation results into the aggregation log according to the format of Table 2. In the third step, the query module queries the business scenario from the aggregation log. In the fourth step, the operation and maintenance personnel can analyze the execution status of the specific business scenario according to Table 2, and then realize the identification of the specific business scenario.

[0092] The present disclosure introduces the dimension of "transaction" into the big data statistical table, successfully identifies specific scenarios, and evaluates the improvement effect of self-service kiosk services in a digital form.

[0093] Table 2

[0094]

[0095] In the above statistics, we can clearly see that for passengers with transaction 1, there were 2 abnormal document resolutions during the business process, and 1 successful document resolution and subsequent business was processed. For passengers with transaction 2, there were 2 abnormal ticket collection failures during the business process, and 1 successful ticket collection and re-printing business was processed. By introducing transactions, we can get a digital report on the improvement of the successful conversion rate brought about by the system upgrade.

[0096] 2. Transaction definition and transaction-related data processing

[0097] 1). Transaction definition. Define the transaction content, transaction unique identifier, and transaction life cycle.

[0098] The transaction content includes the transaction access time, transaction unique identifier (transaction number), self-service kiosk IP, self-service kiosk host name, the airline to which the application belongs, the station where the application is deployed, the current application version, the name of the business handled, the result of the business handled, and the group identifier.

[0099] The transaction unique identifier consists of three parts. The first part is the abbreviation of the software name, such as: APPNAME; the second part is the timestamp in the format of yyyyMMddHHmmss; the third part is an 8-digit random number. The complete transaction unique identifier is: APPNAME2024061714020108189789.

[0100] Transaction life cycle:

[0101] A. Initialization. When the passenger clicks on the AKG front-end screen for the first time, the AKG front-end sends the request to the Base interface of the back-end system through the http protocol. The protocol header includes the transaction unique identifier named "Txn", the self-service machine IP address of the transaction obtained in the current self-service machine application configuration file, the self-service machine host name, the airline to which the application belongs, the station where the application is deployed, and the current application version information. The Base interface of the back-end system obtains the transaction unique identifier named "Txn" from the protocol header. If it is not obtained, a transaction unique identifier is initialized according to the transaction unique identifier generation method, and the back-end system writes the transaction unique identifier to the AKG front-end again.

[0102] B. Storage and use. The AKG front-end caches the transaction unique identifier locally, and the back-end system caches the transaction locally. Each time the AKG front-end requests a different interface of the back-end system, it puts the transaction unique identifier in the http protocol header and transmits it to the back-end system. The back-end system obtains the transaction from the local cache of the back-end system based on the transaction unique identifier.

[0103] C. Destruction. The time of destruction is when the AKG front-end exits. Exit includes passengers actively clicking to exit or passengers not operating the AKG front-end for a long time, resulting in a timeout. When exiting, the AKG front-end sends the protocol header to the Quit interface of the back-end system through the http protocol. The Quit interface obtains the transaction unique identifier named "Txn" from the protocol header and deletes the corresponding transaction in the back-end system cache.

[0104] 2) Transactions and services are associated. Define a transaction interception layer to intercept the services handled by passengers and fill in the transaction content.

[0105] A. Transaction grouping. According to the transaction definition, it can be concluded that when each passenger visits different services, a transaction will be generated. The subsequent processing of transactions is to aggregate them once a day. The number of transaction records per day is very large, which leads to a long aggregation time and a large amount of data. It is necessary to group transactions to increase the aggregation success rate and efficiency. The hash code algorithm is used for the transaction unique identifier. The generated hash value is modulo the set value N such as 10 to obtain the group identifier. The formula is as follows: Group identifier = Hashcode (transaction unique identifier) / 10. This group identifier includes: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

[0106] B. Associated business. Use spring interceptor to intercept all http requests. The request includes the request interface name and the http protocol request header. Use the strategy pattern to fill in the name of the business to be handled according to the request interface name. Cache the transaction in the thread context of the backend system. Use spring interceptor to intercept all http responses. The response includes the result of handling the business. Take out the transaction corresponding to the request from the context and fill in the result of handling the business of the transaction. Package the transaction into a json string and use the log component to output the json string of the transaction to the log file. First, if the Base interface is requested, get the "Txn" transaction number from the request header. If it is not obtained, initialize the transaction. The AKG front end passes "Txn" to the backend system every time it requests, and the backend system writes this "Txn" into the local cache (Redis).

[0107] 3) Processing of data after transactions are associated with business

[0108] A. Transaction collection and storage. Use spring scheduled tasks to create the first ES index of the next day at 23:55 every day. The template of the first index is transaction content, and the index name is APPNAME. Use the open source component File Beat to collect business log files, and write the collected logs into the ES index through the Json Over Http protocol. This type of log is called a raw log.

[0109] B. Define aggregation. Aggregation is to bucket the data within the specified time period in the index and calculate the data in the bucket. Aggregation includes: aggregation query conditions and aggregation calculation templates. Aggregation query conditions include: start time, end time, name of the business handled, and group identifier. Aggregation calculation templates include: airlines, terminals, self-service machine IP, self-service machine host name, group identifier, transaction unique identifier, business results handled, and business name handled. The calculation conditions are in an ordered hierarchical relationship, that is, first bucket the airlines, then the terminals, then the self-service machine IP, and then the self-service machine host name, and so on to derive the template for the aggregation calculation conditions.

[0110] C. Fill in the aggregate query conditions. According to the requirements of the aggregate query conditions, use the preset business names and group identifiers to fill in the aggregate query conditions. For example: the business names include: certificate analysis, ticket service, adding peers, and the group identifiers include: 0, 1, 2, 3, 4. The start time and end time correspond to the 24h start and end time of the day before the aggregation operation time, respectively. The time format is: yyyy-MMdd 24hhmmss. For example: if the operation time is 2024-06-27-01:00:00, the start time is 2024-06-16 00:00:00, and the end time is: 2024-06-16 23:59:59.

[0111] D. Perform aggregation operations. According to the aggregation query conditions and aggregation calculation template, call the ES aggregation API to aggregate the original logs and wait for the aggregation calculation results.

[0112] E. Aggregation results are stored in the database. The aggregation calculation results are parsed in sequence according to the aggregation calculation template, and the parsing results are converted into aggregation results. The aggregation results are written into the second index of ES. The template of the second index is this aggregation result, and the index name is AGG.

[0113] The above definition of transactions and related information are processed as follows Figure 2 shown.

[0114] 3. Improvements made in the front-end system, back-end system, and database after the introduction of transactions:

[0115] 1) Improvement of the cabinet front-end system: The cabinet front-end system sends a request to the back-end and caches the transaction number of the back-end response.

[0116] A. The front-end system of the kiosk sends a non-exit service request. The interface names of non-exit service requests include Base, Tour, Seat, etc., excluding Quit. Every time a passenger clicks on the self-service kiosk, the front-end system of the self-service kiosk sends the request to the back-end system. The request includes a request header, a request interface name, and a request content. The request header includes the transaction number, the self-service kiosk IP, the self-service kiosk host name, the airline to which the application belongs, the station where the application is deployed, and the current application version information. The request interface names are: Base, Tour, Seat, etc., excluding Quit. The request content is business content such as the document number. The transaction number in the request header is obtained from the queue named txnQueue. The logic of storing the transaction number in txnQueue is as follows: The front-end system of the self-service kiosk initializes a temporary cache named txnQueue, which is stored in memory. The cache content is the transaction unique identifier, and the stored data structure is the queue. Each time the front-end system calls the back-end system, the "Txn" in the response header of the back-end system is written into the queue txnQueue. Each time a request is sent to the back-end system, the first Txn put in is obtained from the txnQueue. When the passenger clicks the self-service machine for the first time, that is, when the Base interface is used to interact with the back-end system, there is no transaction number in the queue txnQueue, so it is not transmitted, and the front-end system obtains Txn in FIFO mode. The creation of the queue is implemented using Java's ConcurrentLinkedQueue; the self-service machine IP, self-service machine host name, the airline to which the application belongs, the station where the application is deployed, and the current application version information are stored in the configuration file cfg.txt. Each time a request is sent to the back-end, the http protocol request header includes the content in the configuration file cfg.txt, and the http protocol content is transmitted to the back-end system through the network.

[0117] B. The front-end system of the self-service counter sends a request to exit the service. The interface name of the exit service is Quit. When the front-end system of the self-service counter exits (including the passenger actively clicking the exit button and the passenger's long-term inactivity causing the timeout exit), the self-service front-end system sends a Quit request to the back-end system. The request content is as above A. At the same time, the front-end system of the self-service counter clears the data in the queue txnQueue. The queue is cleared using Java's ConcurrentLinkedQueue.clear().

[0118] 2) Improvement of back-end system: The back-end system processes the request and responds to the transaction number

[0119] A. The backend system adds an interceptor module to intercept all requests from the frontend system. The request includes the request header, request interface name, and request content. The interceptor uses spring's Interceptor technology to intercept all http protocol requests sent by the frontend system. The request header includes the self-service machine IP, the self-service machine host name, the airline to which the application belongs, the station where the application is deployed, and the current application version. The transaction access time is the server time of the backend system when the interceptor receives the request from the frontend system. The request interface names include: Base, Tour, Seat, Quit, etc. The interceptor uses the strategy mode to process different requests from the frontend differently. The processing logic is as follows: First, the first interface Base that carries the request from the frontend system generates a transaction. The generation logic is as follows: The Base interface obtains the transaction unique identifier named "Txn" from the http protocol header. If it is not obtained, it is regenerated. Secondly, the backend system uses a key-value pair data structure to store transactions, where the key is the transaction unique identifier and the value is the transaction, named TxnMap. It is implemented using java's ConcurrentHashMap technology. The Quit interface that carries the front-end exit request is expanded again, and the corresponding transaction in TxnMap is deleted according to the txn in the http protocol request header. The back-end system fills in the name of the business to be handled according to the interface name of the http protocol request, fills this transaction into the thread context, and after the interceptor is executed, takes this transaction out of the thread context and fills in the result of the business after execution. The group identifier in the transaction is generated using the hash code algorithm based on the transaction unique identifier.

[0120] C. The backend system responds with the transaction number and prints the transaction. After the backend system processes the request, it writes the generated transaction unique identifier into the http protocol response header named Txn. Use spring's jackson component to package the transaction into a json format string and use spring's log4j2 component to output the string to the log file / opt / applog / appname / elk.log.

[0121] 3) Library improvements: transaction collection and transaction aggregation

[0122] Transaction collection:

[0123] A. The backend system creates a transaction collection module for transaction collection. First, create an index template and use the open source non-relational database cSearch7.5.0 as the log storage warehouse. Use the spring scheduled task to create the ES index for the next day at 23:55 every day. The index template is the content of the transaction, and the index name is APPNAME-${date}. The time filter field of the index uses the transaction access time, ${date} is tomorrow's date, and the format is yyyyMMdd. Use HttpClient to send a put request to ES to create the index.

[0124] B. Log collection. Use the open source FileBeat component to collect the logs in the log file / opt / applog / appname / elk.log into the index of the corresponding day of ES through the Json over http protocol. For example: if today's date is 20240617, the logs in the file elk.log will be collected into APPNAME-2j0240617. The logs in this index are called original logs.

[0125] Transaction Aggregation

[0126] A. Add a transaction aggregation module to the backend system. First, generate an aggregation operation script. The aggregation includes query conditions and aggregation calculation templates. The aggregation query conditions include: start time, end time, name of the business handled, and group identifier. The start and end time correspond to the 24h start and end time of the day before the aggregation operation time, respectively. The time format is: yyyy-MMdd24hhmmss. For example, if the current backend system time is 20240617, the start time is 2024-06-16 00:00:00, and the end time is: 2024-06-16 23:59:59. The names of the businesses handled are document analysis, ticket collection service, adding a companion, check-in, and re-printing. The group identifier is: 0. In order to improve the query and calculation performance of ES, the group identifier is increased by 1 each time through 10 queries. The valid value of the group identifier is 0-9. The aggregation calculation template includes: airline, terminal, self-service machine IP, self-service machine host name, group identifier, transaction unique identifier, business results handled, and business name handled. The calculation conditions are in an ordered hierarchical relationship, that is, first bucket the airlines, then the terminals, then the kiosk IPs, and then the kiosk host names, and so on to derive the template for the aggregate calculation conditions, that is, the airline node contains the terminal node, the terminal node contains the kiosk IP, and so on. This format is defined as the DSL language format.

[0127] B. Perform aggregation and store in the database. Based on the aggregation query conditions and aggregation calculation template, the ES Search API is called through the Java ElasticSearch Client component to aggregate the original logs. The parameter passed in by the Search API is DSL. The aggregation result of the original log is obtained, and the transaction result after this aggregation is written into the ES index again. The index template is this aggregation result, and the index name is AGG-20240616.

[0128] The above improvements are reflected in Figure 3 The parent flowchart shown and Figure 4 The technical architecture of the self-service machine service method for implementing the above improvement is as follows: Figure 5 shown. Figure 5 In Spring, Spring Boot is used to simplify the initial construction and development process of Spring applications. RestTemplate is an HTTP request tool supported since Spring 3.0. Filebeat is a tool that can collect and forward logs and files from various sources and supports Elasticsearch. EsClient is an ES query client and ES visualization tool. Interceptor is an interceptor. Qurta is a timer. log4j2 and Jackson are components in Spring.

[0129] 4. Business execution process after the associated transaction Specific implementation method:

[0131] 1) Prerequisites

[0132] Air China [CA] has two self-service devices with KIOSK products deployed at the Beijing Capital [PEK] terminal. The IP addresses are 172.26.1.2 and 172.26.1.3, and the self-service counters are CAPEK001 and CAPEK002. Of course, there are also KIOSKs of China Eastern Airlines [MU] and other airlines at the PEK terminal.

[0133] 2) Business execution process

[0134] Figure 6 The business sequence diagram of the self-service machine service method is shown. Figure 7 The business sequence diagram of the data processing method based on the self-service machine service method is shown in the figure. The specific execution steps are as follows:

[0135] Step 1: AKG sends an activation request. The front-end system AKG of the kiosk is activated by the passenger, and AKG sends an activation request to the back-end system. The request contains a request header, a request interface name, and a request content. The request header includes: transaction number, kiosk IP, kiosk host name, the airline to which the application belongs, the station where the application is deployed, and the current application version information, where the transaction number is empty. The request interface name is Base. The request content is empty. The kiosk IP, kiosk host name, the airline to which the application belongs, the station where the application is deployed, and the current application version information are stored in the configuration file cfg.txt. Each time a request is sent to the back-end, the http protocol request header includes the content in the configuration file cfg.txt, and the http protocol content is transmitted to the back-end system through the network.

[0136] Step 2: The back-end interface processes the activation request. The back-end system adds an interceptor module to intercept the front-end request. For the Base interface request, a transaction is created and a key-value pair (Map) data structure is used to store the transaction, where the key is the transaction unique identifier and the value is the transaction, named TxnMap. It is implemented using Java's Concurrent HashMap technology. The transaction includes: transaction access time (current time), transaction unique identifier (transaction number), self-service machine IP, self-service machine host name, the airline to which the application belongs, the station where the application is deployed, the current application version, the name of the business handled (Base), the result of the business handled, and the group identifier. The interceptor uses spring's Interceptor technology to intercept all http protocol requests sent by the front-end system.

[0137] Step 3-4: The backend interface responds to the activation request. The backend system returns the transaction number to AKG and prints the transaction to the log file. Use the jackson component of spring to package the transaction into a string in json format and use the log4j2 component of spring to output the string to the log file / opt / applog / appname / elk.log.

[0138] Step 5: AKG caches the transaction number. After receiving the response from the Base interface, AKG initializes a temporary cache named txnQueue. The cache is stored in memory. The cache content is the transaction unique identifier, and the stored data structure is a queue. The queue is created using Java's ConcurrentLinkedQueue.

[0139] Step 6: AKG sends a non-exit business request to the back-end system. The request header includes the transaction number, which is obtained from the queue txnQueue in FIFO mode. Each time the front-end system calls the back-end system, the "Txn" in the back-end system response header is written into the queue txnQueue. Each time AKG sends a request to the back-end system, it obtains the first Txn put in from txnQueue. The request interface name is the specific business name, such as: Tour, Seat, Checkin, etc., excluding the exit interface name Quit. The request content is the business data corresponding to the specific business, such as: the passenger's ID information transmitted by the Tour interface, the seat data selected by the passenger transmitted by the Seat interface, etc.

[0140] Step 7-8: The backend system processes non-exit business requests. After receiving the non-exit request, the backend system interceptor obtains the transaction corresponding to this transaction number from TxnMap according to the transaction number in the request header, and replaces the business name in the transaction with the specific business request interface name, such as: Tour, Seat, Checkin, etc.

[0141] Step 9-10: The backend system sends a request to the host and receives a response.

[0142] Steps 11-13: The backend system updates the transaction corresponding to this transaction number in TxnMap, and returns the transaction number, business response status code, and business response data to AKG. The transaction number is placed in the value corresponding to the response header name Txn.

[0143] Step 14: AKG caches the transaction number. AKG obtains the transaction number corresponding to the non-exit service request response header Txn and puts it into the txnQueue queue. AKG repeats steps 6-14 when it continues to send non-exit requests.

[0144] Step 15-16: AKG sends an exit request. The front-end system of the kiosk sends an exit request. The interface for exiting the service is called Quit. When the front-end system of the self-service kiosk exits (including passengers actively clicking the exit button and passengers exiting due to timeout due to long-term inactivity), the self-service front-end system sends a Quit request to the back-end system. The request header includes: transaction number, self-service kiosk IP, self-service kiosk host name, the airline to which the application belongs, the station where the application is deployed, and the current application version information. The request interface is called Quit. The request content is empty. At the same time, the front-end system of the self-service kiosk clears the data in the queue txnQueue, and clearing the queue is implemented using Java's ConcurrentLinkedQueue.clear().

[0145] Steps 17-18: Backend system management transactions. After AKG sends the exit request interface, the backend system first obtains the current transaction from TxnMap according to the txn in the http protocol request header, replaces the name of the business in the transaction with Quit, deletes the corresponding transaction in TxnMap, and prints the transaction after the name of the business is replaced to the log file.

[0146] Step 19: The backend system responds with a status code to the Quit request.

[0147] Then the log aggregation and query process from step 20 to step 25 is carried out.

[0148] Step 20: KCMC extracts the business log file containing the transaction number from ES.

[0149] Step 21: KCMC aggregates the business log files, generates Table 2, and submits it to ES.

[0150] Step 22: ES stores aggregated logs.

[0151] Step 23: The operation and maintenance personnel query Table 2 in KCMC.

[0152] Step 24: KCMC queries the aggregated logs from ES.

[0153] Step 25: ES returns the queried Table 2 to KCMC.

[0154] Advantages of this disclosure:

[0155] 1. Traditional operation and maintenance logs start from the statistics of interface calls. Although they can analyze the health of interfaces, they are not sufficient to analyze the handling status of various business scenarios. By introducing the transaction dimension, after the system is improved, it not only retains the key information of business scenarios, but also has a wider application and supports statistical analysis from multiple perspectives. By observing from the dimensions of transaction number and business name, the number of times various business scenarios are handled can be counted; by observing from the dimensions of transaction number and status code, the usage preferences of passengers can be counted; by observing from the dimensions of business name and status code, the health and popularity of the business can be counted.

[0156] 2. By introducing the transaction dimension, it can provide airlines with accurate passenger processing success rate and provide valuable data basis for business cooperation.

[0157] 3. Compared with existing technologies, this technical solution can optimize aggregation efficiency: by using the spring timer task to create the ES index for the next day at 23:55 every day, and using the open source component FileBeat to collect log files, the collected logs are written into the ES index through the Json Over Http protocol, which can effectively reduce data redundancy. By defining aggregation, dynamically adjusting transaction grouping according to actual needs, avoiding the problem of unbalanced transaction grouping that may be caused by fixed grouping, thereby improving the efficiency of aggregation and avoiding the problem of long aggregation time and large data volume caused by excessive transaction data volume.

[0158] In general, compared with the prior art, the present invention has higher aggregation efficiency, more accurate business association, and simpler aggregation logic, and has obvious advantages.

[0159] Based on the above method, the embodiment of the present disclosure also provides a device corresponding to the above method. The details are as follows:

[0160] A self-service machine service device comprises: a receiving module, a transaction management module and a sending module; wherein:

[0161] The receiving module is used to receive the activation request sent by the cabinet front-end system, trigger the transaction management module to create a transaction; receive the non-exit service request sent by the cabinet front-end system, trigger the transaction management module to update the transaction, receive the service operation response sent by the host, receive the exit service request sent by the cabinet front-end system, and complete the transaction represented by the transaction number, wherein the non-exit service request includes: the transaction number, the specific service request interface name and the service data corresponding to the specific service; the service operation response includes the service response status code and service response data; wherein the exit service request includes the transaction number;

[0162] The transaction management module is used to create transactions and print the transactions to the business log file and store them in the database, wherein the transaction includes: transaction number, name of the business to be handled and result of the business to be handled; using the transaction number, the name of the business to be handled in the created transaction is replaced with a specific business request interface name; using the transaction number, the result of the business to be handled in the created transaction is replaced with a status code of the business response, and the transaction is printed to the business log file and stored in the database;

[0163] The sending module is used to send an activation response, a non-exit business response or an exit business response to the front-end system, triggering the transaction management module to update the transaction using the non-exit business response, wherein the activation response includes: the transaction number; the non-exit business response includes: the transaction number, the status code of the business response and the business response data; the exit business response includes: the status code of the exit business response.

[0164] A self-service machine service device comprises: a sending module, a buffer management module and a receiving module; wherein:

[0165] The sending module is used to send an activation request to the back-end system so that the cabinet back-end system can create a transaction; send a non-exit service request to the cabinet back-end system so that the back-end system can use the transaction number to replace the service name handled in the transaction with a specific service request interface name; send a non-exit service request to the cabinet back-end system so that the cabinet back-end system can complete the transaction; wherein the transaction includes: the transaction number, the name of the service handled and the result of the service handled; the non-exit service request includes: the cached transaction number, the specific service request interface name and the service data corresponding to the specific service;

[0166] A receiving module, used to receive an activation response sent by a backend system; receive a non-exit service response sent by a cabinet backend system, and receive an exit service response sent by a cabinet backend system; wherein the activation response includes a transaction number, and the non-exit service response includes: a transaction number, a status code of the service response, and service response data; and the exit service response includes a status code of the exit service response;

[0167] The cache management module is used to cache the transaction number in the activation response when the receiving module receives the cache response; cache the transaction number in the non-exit service response when the receiving module receives the non-exit response; and delete the cached transaction number when the sending module sends an exit service request.

[0168] A data processing device comprises: an index creation module, a collection module, an aggregation module and a writing module; wherein:

[0169] An index creation module is used to create a template for the first index and a template for the second index of the database, wherein the template for the first index is the transaction content, which includes: transaction number, name of the business handled and result of the business handled; the template for the second index is the aggregation result;

[0170] A collection module, used for collecting business log files, wherein the business log files are generated in the process of using the self-service machine service device to provide self-service machine services;

[0171] The aggregation module is used to call the aggregation interface of the database to aggregate the original logs within the start time and end time according to the aggregation query conditions and aggregation calculation templates to obtain the aggregation results of the original logs. The aggregation query conditions include: start time, end time and the name of the business handled; the aggregation calculation template includes: transaction number, business result handled, and business name handled;

[0172] The writing module is used to write the collected log content into the transaction content in the first index template, obtain the original log, and write the aggregation result into the template of the second index of the database.

[0173] Based on the same inventive concept as the above disclosed content, the present disclosure also provides an electronic device accordingly. The electronic device of the present disclosure embodiment includes at least one electrically connected processor and only one memory, the memory is electrically connected to the processor, wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can perform the method as described above.

[0174] It should be noted that the electrical connection between the above-mentioned units does not necessarily mean the connection between lines. An indirect connection method can be applied to the embodiments of the present disclosure as long as the purpose of the present disclosure is achieved.

[0175] Based on the same inventive concept, the present disclosure also provides a computer storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of the above method are implemented.

[0176] Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure.

Claims

1. A self-service machine service method, characterized in that: The method comprises: The back-end system receives the activation request sent by the cabinet front-end system; The back-end system creates a transaction and prints the transaction to a business log file and stores it in the database, where the transaction includes: transaction number, name of the business being handled, and result of the business being handled; The back-end system sends an activation response to the cabinet front-end system, wherein the activation response includes a transaction number; The back-end system receives the non-exit service request sent by the cabinet front-end system, wherein the non-exit service request includes: a transaction number, a specific service request interface name and service data corresponding to the specific service; The backend system uses the transaction number to replace the name of the business handled in the created transaction with the specific business request interface name, and sends a business operation request to the host based on the business data corresponding to the specific business; The back-end system receives the business operation response sent by the host, wherein the business operation response includes a business response status code and business response data; The back-end system uses the transaction number to replace the result of the business in the created transaction with the status code of the business response, and prints the transaction to the business log file and stores it in the database; The backend system sends a non-exit business response to the frontend system, wherein the non-exit business response includes: a transaction number, a business response status code, and business response data; The back-end system receives the exit service request sent by the cabinet front-end system, completes the transaction represented by the transaction number, and prints the transaction to the business log file and stores it in the database, wherein the exit service request includes the transaction number; The back-end system sends an exit service response to the cabinet front-end system.

2. The self-service machine service method according to claim 1, characterized in that: The backend system creates a transaction, including: The backend system intercepts the activation request through the interceptor, creates a transaction, and prints the transaction to the business log file and stores it in the database; The backend system uses the transaction number to replace the service name in the created transaction with the specific service request interface name, including: The backend system intercepts the non-exit business request through the interceptor, and uses the transaction number to replace the business name handled in the created transaction with the specific business request interface name; The backend system uses the transaction number to replace the result of the business in the created transaction with the status code of the business response, including: The backend system intercepts the non-exit business response through the interceptor, and uses the transaction number to replace the result of the business in the created transaction with the status code of the business response; Confirm the completion of the transaction indicated by the transaction number, including: The back-end system intercepts the exit business request through the interceptor and confirms the completion of the transaction represented by the transaction number.

3. A self-service machine service device, characterized in that: The device comprises: a receiving module, a transaction management module and a sending module; wherein: The receiving module is used to receive the activation request sent by the cabinet front-end system, trigger the transaction management module to create a transaction; receive the non-exit service request sent by the cabinet front-end system, trigger the transaction management module to update the transaction, receive the service operation response sent by the host, receive the exit service request sent by the cabinet front-end system, and complete the transaction represented by the transaction number, wherein the non-exit service request includes: the transaction number, the specific service request interface name and the service data corresponding to the specific service; the service operation response includes the service response status code and service response data; wherein the exit service request includes the transaction number; The transaction management module is used to create transactions and print the transactions to the business log file and store them in the database, wherein the transaction includes: transaction number, name of the business to be handled and result of the business to be handled; using the transaction number, the name of the business to be handled in the created transaction is replaced with a specific business request interface name; using the transaction number, the result of the business to be handled in the created transaction is replaced with a status code of the business response, and the transaction is printed to the business log file and stored in the database; The sending module is used to send an activation response, a non-exit business response or an exit business response to the front-end system, triggering the transaction management module to update the transaction using the non-exit business response, wherein the activation response includes: the transaction number; the non-exit business response includes: the transaction number, the status code of the business response and the business response data; the exit business response includes: the status code of the exit business response.

4. A self-service machine service method, characterized in that: include: The cabinet front-end system sends an activation request to the back-end system so that the cabinet back-end system can create a transaction, wherein the transaction includes: transaction number, name of the business being handled and result of the business being handled; The cabinet front-end system receives the activation response sent by the back-end system, wherein the activation response includes the transaction number; The transaction number in the cabinet front-end system cache activation response; The cabinet front-end system sends a non-exit service request to the cabinet back-end system, so that the back-end system can use the transaction number to replace the service name handled in the transaction with the specific service request interface name, wherein the non-exit service request includes: the cached transaction number, the specific service request interface name and the service data corresponding to the specific service; The cabinet front-end system receives the non-exit service response sent by the cabinet back-end system, so that the back-end system uses the transaction number to replace the result of the service in the transaction with the status code of the service response; wherein the non-exit service response includes: the transaction number, the status code of the service response and the service response data; The cabinet front-end system caches the transaction number in the non-exit business response; The cabinet front-end system sends a service exit request to the cabinet back-end system, wherein the service exit request includes a transaction number; The cabinet front-end system deletes the cached transaction number; The cabinet front-end system receives the exit service response sent by the cabinet back-end system, wherein the exit service response includes a status code of the exit service response.

5. A self-service machine service device, characterized in that: include: A sending module, a buffer management module and a receiving module; wherein: The sending module is used to send an activation request to the back-end system so that the cabinet back-end system can create a transaction; send a non-exit service request to the cabinet back-end system so that the back-end system can use the transaction number to replace the service name handled in the transaction with a specific service request interface name; send a non-exit service request to the cabinet back-end system so that the cabinet back-end system can complete the transaction; wherein the transaction includes: the transaction number, the name of the service handled and the result of the service handled; the non-exit service request includes: the cached transaction number, the specific service request interface name and the service data corresponding to the specific service; A receiving module, used to receive an activation response sent by a backend system; receive a non-exit service response sent by a cabinet backend system, and receive an exit service response sent by a cabinet backend system; wherein the activation response includes a transaction number, and the non-exit service response includes: a transaction number, a status code of the service response, and service response data; and the exit service response includes a status code of the exit service response; The cache management module is used to cache the transaction number in the activation response when the receiving module receives the cache response; cache the transaction number in the non-exit service response when the receiving module receives the non-exit response; and delete the cached transaction number when the sending module sends an exit service request.

6. A data processing method, characterized in that: The method comprises: Creating a template for the first index of the database, wherein the template for the first index is transaction content, and the transaction content includes: transaction number, name of the business being handled, and result of the business being handled; Collecting logs from the business log file, and writing the collected log content into the transaction content in the first index template to obtain the original log, wherein the business log file is generated in the process of performing the self-service machine service using the self-service machine service method according to claim 1; According to the aggregation query conditions and aggregation calculation template, call the database aggregation interface to aggregate the original logs within the start time and end time to obtain the aggregation results of the original logs. The aggregation query conditions include: start time, end time and the name of the business handled; the aggregation calculation template includes: transaction number, business result handled, and business name handled; Creating a template for a second index of the database, wherein the template for the second index is an aggregation result; Write the aggregation result into the template of the second index of the database.

7. The data processing method according to claim 6, characterized in that: The transaction also includes: the cabinet configuration information and group identification included in the activation request, the cabinet configuration information shows the hierarchical information of the cabinet: from top to bottom, the hierarchy is airline, terminal, self-service cabinet, and self-service cabinet host name, and the group identification is obtained by using the hash algorithm to the transaction number and taking the modulus of the generated hash value; the aggregate query condition also includes: group identification; According to the aggregation query conditions and aggregation calculation template, call the database aggregation interface to aggregate the original logs within the start time and end time, including: According to the aggregation query conditions and aggregation calculation template, the level information of the cabinet is used as the aggregation calculation condition, and the aggregation interface of the database is called to aggregate the original logs within the start time and end time.

8. A data processing device, characterized in that: The device comprises: an index creation module, a collection module, an aggregation module and a writing module; wherein: An index creation module is used to create a template for the first index and a template for the second index of the database, wherein the template for the first index is the transaction content, which includes: transaction number, name of the business handled and result of the business handled; the template for the second index is the aggregation result; A collection module, used for collecting logs of business log files, wherein the business log files are generated in the process of performing self-service machine services using the self-service machine service device according to claim 3; The aggregation module is used to call the aggregation interface of the database to aggregate the original logs within the start time and end time according to the aggregation query conditions and aggregation calculation templates to obtain the aggregation results of the original logs. The aggregation query conditions include: start time, end time and the name of the business handled; the aggregation calculation template includes: transaction number, business result handled, and business name handled; The writing module is used to write the collected log content into the transaction content in the first index template, obtain the original log, and write the aggregation result into the template of the second index of the database.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory, used to store computer programs; A processor, for implementing the steps of any one of the methods of claims 1-2 and 4 when executing a program stored in a memory.

10. A computer storage medium, characterized in that: The computer storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method described in any one of claims 1-2 and 4 are implemented.

Images