A self-service machine service method, data processing method and device

Abstract

The present disclosure relates to the field of computer technology and provides a self-service kiosk service method, a data processing method, and a device. The self-service kiosk service method includes a back-end system creating a transaction including a transaction number, a name of a business being handled, and a result of the business being handled based on an activation request received from a kiosk front-end system, and the kiosk front-end system sending an activation response including the transaction number; receiving a non-exit business request sent by the kiosk front-end system, replacing the name of the business being handled in the created transaction with a specific business request interface name using the transaction number; receiving a business operation response sent by a host, replacing the result of the business being handled in the created transaction with a status code of the business response; and after receiving an exit business request sent by the kiosk front-end system, returning an exit business response to complete the transaction represented by the transaction number. By introducing a transaction mechanism into business interactions and generating associated data between transactions and businesses, specific scenarios can be identified and the effect of self-service kiosk service improvement can be evaluated.

Description

Technical Field

[0001] The present disclosure belongs to the field of computer technology, and in particular relates 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, the types of services supported are diverse, including not only traditional check-in, baggage check-in, rescheduling, and itinerary booking, but also personalized airline services such as Wi-Fi sales and paid upgrades. These services are supported differently by different airlines and airports. The support level of self-service kiosk services for diverse needs varies, and airline satisfaction levels also vary. To improve customer satisfaction, we have been continuously improving and optimizing self-service kiosk services. However, the effectiveness of many optimizations cannot be objectively evaluated. The following two application scenarios are 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 kiosks is low, resulting in passengers' failure to swipe their passports. Many passengers do not want to understand the reason and go directly to the manual counter to handle the business. In order to improve passenger stickiness and increase the utilization rate of self-service kiosks, the business process has been improved, and passengers are guided to swipe their documents multiple times through animation instructions.

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

[0006] When booking some international tickets with foreign airlines, ID isn't a mandatory field. If a passenger used their passport to check in, the corresponding ticket information wouldn't be found in the backend, preventing the transaction from proceeding. This process has since been optimized, and when this error is identified, a dialog box will pop up, guiding the passenger to use other methods to find their ticket.

[0007] The optimization effects of the above two scenarios are difficult to evaluate using current statistical methods. Table 1 below shows the content recorded in the current daily statistical table:

[0008] Table 1

[0009]

[0010] Because backend system statistics are generally based on the number of successful and failed business interfaces, and because the number of passenger processing before and after the improvement varies, the number of failures and successes may increase or decrease, making it difficult to assess the relationship between the successful conversion rate and the improvement.

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

[0012] To solve the above problems, the present disclosure 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 the generated transactions and businesses can be identified, which can be used to evaluate the improvement effect of the self-service kiosk service.

[0013] In a first aspect, a self-service kiosk 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 it to a business log file and stores it in the database. The transaction includes: transaction number, business name, and business result.

[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 business name 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 backend 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 processing in the created transaction with the business response status code, and prints the transaction to the business log file and stores it in the database;

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

[0022] The back-end system receives the exit service request sent by the cabinet front-end system, completes the transaction indicated 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 back-end 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 business name in the created transaction with the specific business request interface name, specifically including:

[0027] The backend system intercepts the non-exit business request through the interceptor, and uses the transaction number to replace the business name 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 processing in the created transaction with the status code of the business response, including:

[0029] The backend system intercepts non-exit business responses through an 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, comprising: a receiving module, a transaction management module, and a sending module; wherein:

[0033] The receiving module is used to receive an activation request sent by the cabinet front-end system, trigger the transaction management module to create a transaction; receive a non-exit service request sent by the cabinet front-end system, trigger the transaction management module to update the transaction, receive a service operation response sent by the host, receive an 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: a transaction number, a specific service request interface name, and service data corresponding to a specific service; the service operation response includes a service response status code and service response data; wherein the exit service request includes a 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. The transaction includes: transaction number, business name and result of the business; using the transaction number, the business name in the created transaction is replaced with the specific business request interface name; using the transaction number, the result of the business in the created transaction is replaced with the business response status code, 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 business response status code and the business response data; the exit business response includes: the exit business response status code.

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

[0037] The front-end system of the counter sends an activation request to the back-end system so that the back-end system of the counter 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 front-end system of the counter sends a non-exit service request to the back-end system of the counter, 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 front-end system of the counter receives the non-exit service response sent by the back-end system of the counter, so that the back-end system can use 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 business exit request to the cabinet back-end system, wherein the business 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 buffer 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 the 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, configured to receive an activation response sent by the back-end system; receive a non-exit service response sent by the cabinet back-end system; and receive an exit service response sent by the cabinet back-end system; wherein the activation response includes a transaction number, the non-exit service response includes: a transaction number, a service response status code, and service response data; and the exit service response includes an exit service response status code;

[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] In a fifth aspect, a data processing method is provided, 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 a business log file and writing the collected log content into the transaction content in the first index template to obtain an original log, wherein the business log file is generated during the process of performing the self-service kiosk service using the above-mentioned self-service kiosk service method;

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

[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 results into the template of the second index of the database.

[0056] Furthermore, the transaction also includes: kiosk configuration information and group identifier included in the activation request. The kiosk configuration information displays the hierarchical information of the kiosk: from top to bottom, the hierarchical information is airline, terminal, kiosk, and kiosk host name. The group identifier is obtained by applying a hash algorithm to the transaction number and taking the modulus of the generated hash value. The aggregate query condition also includes: group identifier;

[0057] Based on the aggregation query conditions and aggregation calculation template, call the database's aggregation interface to aggregate the original logs between the start and end times. Specifically, the following steps are performed:

[0058] Based on the aggregation query conditions and aggregation calculation template, the database's aggregation interface is called to aggregate the original logs within the start and end time, taking the cabinet's tier information as the aggregation calculation condition.

[0059] In a sixth aspect, a data processing device is provided, 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. The template for the first index is the transaction content, which includes: transaction number, business name, and business result; the template for the second index is the aggregated result;

[0061] A collection module, configured to collect business log files, wherein the business log files are generated during the process of performing self-service ATM services using the self-service ATM service device described above;

[0062] The aggregation module is used to call the database's aggregation interface to aggregate the original logs within the start and end time according to the aggregation query conditions and aggregation calculation template to obtain the aggregation results of the original logs. The aggregation query conditions include: start time, end time, and business name 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 to 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 for storing computer programs;

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

[0067] In an eighth aspect, a computer storage medium is provided, wherein the computer storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

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

[0069] 1. Introducing transactions, associating transactions with businesses in requests and responses, and generating business log files after the associated transactions. This allows for processing the log files and identifying specific scenarios, which can be used to evaluate the effectiveness of self-service kiosk improvements.

[0070] 2. Creating indexes for collected logs can effectively reduce data redundancy. Defining aggregations and grouping transactions by transaction number avoids the imbalanced transaction grouping that may be caused by fixed grouping methods, thereby improving aggregation efficiency and avoiding the 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 in part will become apparent from the description, or will be understood by practicing the present disclosure. The purposes and other advantages of the present disclosure can be realized and obtained by the structures indicated 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 following briefly introduces the drawings required for use in the embodiments or the description of the prior art. 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 components of a self-service kiosk service system according to an embodiment of the present disclosure is shown;

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

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

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

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

[0078] Figure 6 A business sequence diagram of a method for executing a self-service kiosk service 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] To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure more clear, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present disclosure without making any creative efforts shall fall 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 changes, itinerary printing, flight delay certificates, etc. is integrated to provide airlines with comprehensive passenger self-service kiosk services for passengers.

[0083] KIOSK: refers to the carrier equipment for self-service products in transportation places such as airports and train stations, also known as self-service equipment or "cabinets". 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] Back-end system: A back-end system that provides data and verification services to KIOSK and writes business records into the log system.

[0086] KCMC: The 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 that introduces transactions is first explained, followed by the transaction definition and transaction-related data processing. Then, the improvements made in the front-end system, back-end system, and database after the introduction of transactions are explained. Finally, through the business execution process after the associated transaction, the solution of the embodiment of the present disclosure is explained in detail.

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

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

[0090] Passengers interact with the AKG 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 back-end system's business module combines the AKG request parameters and transaction management data to perform business processing, and then writes the transaction number and business processing result (status code) to the business log stored in Elastic Search. Under normal circumstances, the status code is 0, and abnormal circumstances have corresponding error codes.

[0091] KCMC can check the business log to know 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 of 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 in 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, thereby realizing the identification of the specific business scenario.

[0092] This 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] The above statistics clearly show that for passengers with transaction number 1, two document resolution exceptions occurred during the transaction process, one successful document resolution occurred, and subsequent transactions were processed. For passengers with transaction number 2, two ticket collection failures occurred during the transaction process, and one successful ticket collection occurred, resulting in a reprint. By introducing transactions, we can generate numerical reports on the improvement in 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 lifecycle.

[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] A transaction unique identifier consists of three parts: the first part is the abbreviation of the software name, such as "APPNAME"; the second part is a timestamp in the format of "yyyyMMddHHmmss"; and the third part is an 8-digit random number. A complete transaction unique identifier is, for example: "APPNAME2024061714020108189789."

[0100] Transaction life cycle:

[0101] A. Initialization. When a passenger first clicks the AKG front-end screen, the AKG front-end sends a request to the back-end system's Base interface via HTTP. The protocol header includes a transaction unique identifier ("Txn"), the ATM machine IP address (from the ATM's application configuration file), the ATM host name, the airline to which the application belongs, the terminal where the application is deployed, and the current application version. The back-end system's Base interface retrieves the transaction unique identifier ("Txn") from the protocol header. If it doesn't retrieve the unique identifier, it initializes one using the transaction unique identifier generation method. The back-end system then writes the transaction unique identifier back to the AKG front-end.

[0102] B. Storage and Usage. The AKG frontend caches the transaction's unique identifier locally, and the backend system caches the transaction locally. Each time the AKG frontend requests a different interface from the backend system, it places the unique identifier in the HTTP header and transmits it to the backend system. The backend system retrieves the transaction from its local cache based on the unique identifier.

[0103] C. Destruction. Destruction occurs when the AKG frontend exits. This can occur when the passenger actively clicks "Exit" or when the passenger times out due to prolonged inactivity. Upon exit, the AKG frontend sends a protocol header to the backend system's Quit interface via HTTP. The Quit interface retrieves the unique transaction identifier ("Txn") from the protocol header and deletes the corresponding transaction from the backend system's 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 accesses 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 time and a large amount of data during aggregation. 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 interceptors to intercept all http requests. The requests include the request interface name and the http protocol request header. Use the strategy pattern to fill in the name of the business being handled according to the request interface name. Cache the transaction in the thread context of the backend system. Use spring interceptors to intercept all http responses. The response includes the result of the business being handled. Take out the transaction corresponding to the request from the context and fill in the result of the business being handled. 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, obtain the "Txn" transaction number from the request header. If it is not obtained, initialize the transaction. The AKG front end passes the "Txn" to the backend system every time it makes a request, and the backend system writes this "Txn" to the local cache (Redis).

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

[0108] A. Transaction collection and storage. A Spring scheduled task is used to create the first ES index for the next day at 11:55 PM daily. The template for the first index is transaction content, and the index name is APPNAME. The open-source component File Beat is used to collect business log files and write the collected logs to the ES index using the JSON over HTTP protocol. These logs are called raw logs.

[0109] B. Define aggregation. Aggregation is to bucket the data within a specified time period in the index and perform calculations on the data in the buckets. 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: airline, terminal, kiosk IP, kiosk host name, group identifier, transaction unique identifier, business result handled, and business name handled. The calculation conditions are an ordered hierarchical relationship, that is, first bucket the airline, then the terminal, then the kiosk IP, and then the kiosk host name, and so on to derive the template for the aggregation calculation conditions.

[0110] C. Fill in the aggregate query conditions. Based on the requirements of the aggregate query conditions, use the preset service names and group identifiers to fill in the aggregate query conditions. For example, the service names include: document resolution, ticket collection service, and adding peers. The group identifiers include: 0, 1, 2, 3, and 4. The start time and end time correspond to the 24-hour start and end time of the day before the aggregate 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. Based on the aggregation query conditions and the 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. The aggregation calculation results are parsed by sequentially parsing the results according to the aggregation calculation template, converting the parsed results into aggregation results, and writing these aggregation results into the ES secondary index. The template of the secondary index is this aggregation result, and the index name is AGG.

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

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

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

[0116] A. The kiosk front-end system sends a non-exit service request. Interface names for non-exit service requests include Base, Tour, Seat, etc., but do not include Quit. Each time a passenger clicks a kiosk, the kiosk front-end system sends a request to the back-end system. The request includes a request header, a request interface name, and request content. The request header includes the transaction number, kiosk IP address, kiosk host name, the airline to which the application belongs, the station where the application is deployed, and the current application version. Request interface names include Base, Tour, Seat, etc., but do not include Quit. The request content includes service details such as the document number. The transaction number in the request header is obtained from a queue named txnQueue. The logic for storing transaction numbers in txnQueue is as follows: The kiosk front-end system initializes a temporary cache named txnQueue, which is stored in memory. The cache content contains the unique transaction identifier, and the data structure stored is a queue. Each time the front-end system calls the back-end system, it writes the "Txn" in the back-end system's response header to the queue txnQueue. Each time a request is sent to the back-end system, the first Txn inserted is retrieved from the txnQueue. When a passenger first clicks the kiosk, i.e., when interacting with the back-end system using the Base interface, if there is no transaction number in the queue txnQueue, the transaction is not transmitted, and the front-end system uses the FIFO mode to obtain Txn. The queue is created using Java's ConcurrentLinkedQueue implementation; the kiosk IP address, kiosk host name, application airline, application deployment terminal, and 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 contents of the configuration file cfg.txt, and the HTTP protocol content is transmitted to the back-end system via the network.

[0117] B. The kiosk front-end system sends a request to exit the service. The exit interface is called Quit. When the self-service kiosk front-end system exits (including when the passenger actively clicks the exit button or when the passenger times out due to inactivity), the self-service front-end system sends a Quit request to the back-end system. The request content is as described in A above. Simultaneously, the self-service kiosk front-end system clears the data in the queue txnQueue. This is implemented using Java's ConcurrentLinkedQueue.clear() method.

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

[0119] A. Add an interceptor module to the backend system to intercept all requests from the frontend system. Requests include request headers, request interface names, 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 kiosk IP address, kiosk host name, the airline to which the application belongs, the site 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 frontend system request. Request interface names include: Base, Tour, Seat, Quit, etc. The interceptor uses the strategy pattern to handle different frontend requests differently. The processing logic is as follows: First, a transaction is generated for the first interface Base that carries the frontend system request. 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. It is called TxnMap. This is implemented using Java's ConcurrentHashMap technology. The Quit interface, which handles front-end exit requests, is further extended. Based on the txn in the HTTP request header, the corresponding transaction in the TxnMap is deleted. The back-end system populates the name of the service being handled based on the interface name in the HTTP request and inserts this transaction into the thread context. After the interceptor executes, the transaction is retrieved from the thread context and populated with the result of the service being handled. The group identifier in the transaction is generated using a hash code algorithm based on the transaction's unique identifier.

[0120] C. The backend system responds with a transaction number and prints the transaction. After processing the request, the backend system writes the generated unique transaction identifier into the HTTP response header named "Txn." Spring's Jackson component is used to package the transaction into a JSON-formatted string and Spring's log4j2 component is used 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. Create a transaction collection module in the backend system to collect transactions. First, create an index template and use the open-source non-relational database cSearch 7.5.0 as the log storage repository. Use a Spring scheduled task to create an ES index for the next day at 11:55 PM every day. The index template is based on the transaction content, and the index name is APPNAME-${date}. The index's time filter field uses the transaction access time, and ${date} is tomorrow's date in the format of 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 / opt / applog / appname / elk.log file into the ES index for the corresponding day using the JSON over HTTP protocol. For example, if today's date is 20240617, the logs in the elk.log file will be collected into the index APPNAME-2j0240617. Logs in this index are called raw logs.

[0125] Transaction Aggregation

[0126] A. A new transaction aggregation module has been added to the backend system. First, an aggregation operation script is generated. The aggregation includes query conditions and an aggregation calculation template. The aggregation query conditions include: start time, end time, service name, and group identifier. The start and end times correspond to the 24-hour start and end times of the day before the aggregation operation, respectively, in the format of 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 service names are document resolution, ticket collection, adding a companion, check-in, and re-issuing. The group identifier is 0. To improve ES query and calculation performance, the group identifier is incremented by 1 each time after 10 queries. Valid values ​​for the group identifier are 0-9. The aggregation calculation template includes: airline, terminal, kiosk IP address, kiosk host name, group identifier, transaction unique identifier, service result, and service name. The calculation conditions are organized in a hierarchical order, first bucketing by airline, then by terminal, then by kiosk IP address, and finally by kiosk host name. This continues in this order, resulting in a template for aggregate calculation conditions: airline nodes contain terminal nodes, terminal nodes contain kiosk IP addresses, and so on. This format is defined as a DSL language.

[0127] B. Aggregate and store the data. Based on the aggregation query conditions and the aggregation calculation template, the Java ElasticSearch Client component calls the ES Search API to aggregate the original logs. The Search API passes in a DSL parameter. The aggregation results of the original logs are obtained and the aggregated transaction results are written to 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 for implementing the above improved self-service machine service method is shown in the sub-flow chart. Figure 5 shown. Figure 5 In Spring, Spring Boot is used to simplify the initial setup and development of Spring applications. RestTemplate is an HTTP request tool supported since Spring 3.0. Filebeat is a tool that collects and forwards logs and files from various sources and supports Elasticsearch. EsClient is an Elasticsearch query client and visualization tool. Interceptor is an interceptor. Qurta is a timer. Log4j2 and Jackson are Spring components.

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

[0131] 1) Preconditions

[0132] Air China [CA] has two self-service kiosks deployed at its Beijing Capital [PEK] terminal. The IP addresses are 172.26.1.2 and 172.26.1.3, and the kiosk names are CAPEK001 and CAPEK002. Of course, kiosks operated by other airlines, such as China Eastern Airlines [MU], are also located at the PEK terminal.

[0133] 2) Business execution process

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

[0135] Step 1: AKG sends an activation request. The kiosk front-end system AKG is activated by the passenger, and AKG sends an activation request to the back-end system. The request includes 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. 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 being handled (Base), the result of the business handling, and the group identifier. The interceptor uses spring's Interceptor technology to intercept all http protocol requests sent by the front-end system.

[0137] Steps 3-4: The backend interface responds to the activation request. The backend system returns the transaction number to AKG and logs the transaction to a log file. Spring's Jackson component wraps the transaction into a JSON string and uses Spring's log4j2 component 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's unique identifier, and the stored data structure is a queue. Java's ConcurrentLinkedQueue is used to create the queue.

[0139] Step 6: AKG sends a non-exit service request to the backend system. The request header includes a transaction number, which is retrieved from the txnQueue queue using FIFO mode. Each time the frontend system calls the backend system, the "Txn" in the backend system's response header is written to the txnQueue queue. Each time AKG sends a request to the backend system, it retrieves the first Txn entered from the txnQueue. The request interface name is the specific service name, such as Tour, Seat, Checkin, etc., and does not include the exit interface name Quit. The request content contains the business data corresponding to the specific service, such as the passenger's ID information transmitted through the Tour interface and the passenger's seat selection data transmitted through the Seat interface.

[0140] Step 7-8: The back-end system processes the non-exit business request. After receiving the non-exit request, the back-end 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] Steps 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 named Txn.

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

[0144] Steps 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 the passenger actively clicking the exit button and the passenger 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: Back-end system management transaction. After AKG sends the exit request interface, the back-end system first obtains the current transaction from the TxnMap based on the txn in the HTTP protocol request header, replaces the business name in the transaction with Quit, deletes the corresponding transaction in the TxnMap, and prints the transaction after the replaced business name to the log file.

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

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

[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 are based on 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 system improvements, key information of business scenarios is retained, the application scope is wider, and statistical analysis from multiple perspectives is supported. 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, passenger usage preferences can be counted; and by observing from the dimensions of business name and status code, business health and popularity can be counted.

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

[0157] 3. Compared with existing technologies, this technical solution optimizes aggregation efficiency: by using a spring-timed task to create the next day's ES index at 11:55 PM daily, and using the open-source component FileBeat to collect log files, the collected logs are written to the ES index via the JSON over Http protocol, effectively reducing data redundancy. By defining aggregations and dynamically adjusting transaction groupings based on actual needs, this avoids the imbalanced transaction grouping that can occur with fixed grouping methods, thereby improving aggregation efficiency and avoiding the long aggregation times and large data volumes caused by excessive transaction data volumes.

[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 teller machine service device includes: a receiving module, a transaction management module and a sending module; wherein:

[0161] The receiving module is used to receive an activation request sent by the cabinet front-end system, trigger the transaction management module to create a transaction; receive a non-exit service request sent by the cabinet front-end system, trigger the transaction management module to update the transaction, receive a service operation response sent by the host, receive an 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: a transaction number, a specific service request interface name, and service data corresponding to a specific service; the service operation response includes a service response status code and service response data; wherein the exit service request includes a 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. The transaction includes: transaction number, business name and result of the business; using the transaction number, the business name in the created transaction is replaced with the specific business request interface name; using the transaction number, the result of the business in the created transaction is replaced with the business response status code, 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 business response status code and the business response data; the exit business response includes: the exit business response status code.

[0164] A self-service machine service device includes: 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 the 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, configured to receive an activation response sent by the back-end system; receive a non-exit service response sent by the cabinet back-end system; and receive an exit service response sent by the cabinet back-end system; wherein the activation response includes a transaction number, the non-exit service response includes: a transaction number, a service response status code, and service response data; and the exit service response includes an exit service response status code;

[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 includes: 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. The template for the first index is the transaction content, which includes: transaction number, business name, and business result; the template for the second index is the aggregated result;

[0170] A collection module for collecting business log files, wherein the business log files are generated during the process of performing self-service ATM services using the self-service ATM service device;

[0171] The aggregation module is used to call the database's aggregation interface to aggregate the original logs within the start and end time according to the aggregation query conditions and aggregation calculation template to obtain the aggregation results of the original logs. The aggregation query conditions include: start time, end time, and business name 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 to 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 disclosure, the present disclosure also provides an electronic device. The electronic device of the present disclosure embodiment includes at least one electrically connected processor and at least one memory, the memory being electrically connected to the processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method 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 further provides a computer storage medium, wherein the computer storage medium stores a computer program, and 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 cause the essence of the corresponding technical solutions to 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 it to a business log file and stores it in the database. The transaction includes: transaction number, business name, and business result. 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 business name 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 backend 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 processing in the created transaction with the business response status code, and prints the transaction to the business log file and stores it in the database; The backend system sends a non-exit service response to the frontend system, where the non-exit service response includes: transaction number, service response status code, and service response data; The back-end system receives the exit service request sent by the cabinet front-end system, completes the transaction indicated 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 back-end system creates a transaction, including: The back-end 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 business name in the created transaction with the specific business request interface name, specifically including: The backend system intercepts the non-exit business request through the interceptor, and uses the transaction number to replace the business name 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 processing in the created transaction with the status code of the business response, including: The backend system intercepts non-exit business responses through an 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 includes: a receiving module, a transaction management module and a sending module; wherein: The receiving module is used to receive an activation request sent by the cabinet front-end system, trigger the transaction management module to create a transaction; receive a non-exit service request sent by the cabinet front-end system, trigger the transaction management module to update the transaction, receive a service operation response sent by the host, receive an 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: a transaction number, a specific service request interface name, and service data corresponding to a specific service; the service operation response includes a service response status code and service response data; wherein the exit service request includes a 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. The transaction includes: transaction number, business name and result of the business; using the transaction number, the business name in the created transaction is replaced with the specific business request interface name; using the transaction number, the result of the business in the created transaction is replaced with the business response status code, 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 business response status code and the business response data; the exit business response includes: the exit business response status code.

4. A self-service machine service method, characterized in that: include: The front-end system of the counter sends an activation request to the back-end system so that the back-end system of the counter 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 front-end system of the counter sends a non-exit service request to the back-end system of the counter, 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 front-end system of the counter receives the non-exit service response sent by the back-end system of the counter, so that the back-end system can use 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 business exit request to the cabinet back-end system, wherein the business 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: Sending module, cache management module and 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 the 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, configured to receive an activation response sent by the back-end system; receive a non-exit service response sent by the cabinet back-end system; and receive an exit service response sent by the cabinet back-end system; wherein the activation response includes a transaction number, the non-exit service response includes: a transaction number, a service response status code, and service response data; and the exit service response includes an exit service response status code; 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 a business log file and writing the collected log content into the transaction content in the first index template to obtain an original log, wherein the business log file is generated during the process of performing a self-service kiosk service using the self-service kiosk service method according to claim 1; Based on the aggregation query conditions and aggregation calculation template, call the database aggregation interface to aggregate the original logs within the start and end time to obtain the aggregation results of the original logs. The aggregation query conditions include: start time, end time, and business name; the aggregation calculation template includes: transaction number, business result, and business name. Creating a template for a second index of the database, wherein the template for the second index is an aggregation result; Write the aggregation results into the template of the second index of the database.

7. The data processing method according to claim 6, wherein: The transaction also includes: the kiosk configuration information and group identifier included in the activation request. The kiosk configuration information shows the hierarchical information of the kiosk: from top to bottom, the hierarchical information is airline, terminal, kiosk, and kiosk host name. The group identifier is obtained by applying a hash algorithm to the transaction number and taking the modulus of the generated hash value. The aggregate query condition also includes: the group identifier; Based on the aggregation query conditions and aggregation calculation template, call the database's aggregation interface to aggregate the original logs between the start and end times. Specifically, the following steps are performed: Based on the aggregation query conditions and aggregation calculation template, the database's aggregation interface is called to aggregate the original logs within the start and end time, taking the cabinet's tier information as the aggregation calculation condition.

8. A data processing device, characterized in that: The device includes: 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. The template for the first index is the transaction content, which includes: transaction number, business name, and business result; the template for the second index is the aggregated result; a collection module for collecting business log files, wherein the business log files are generated during the process of performing self-service ATM service using the self-service ATM service device according to claim 3; The aggregation module is used to call the database's aggregation interface to aggregate the original logs within the start and end time according to the aggregation query conditions and aggregation calculation template to obtain the aggregation results of the original logs. The aggregation query conditions include: start time, end time, and business name 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 to 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 for storing computer programs; A processor, configured to implement the steps of the method according to any one of claims 1 to 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 according to any one of claims 1 to 2 and 4 are implemented.

Images