Transaction Data Processing Apparatus Using Universal Agent Program
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional transaction data processing apparatuses require different agent programs for generating electronic receipts, depending on the specifications of transaction data processing, which limits the adaptability and efficiency in transitioning to electronic receipt systems.
Innovation Solution
A transaction data processing apparatus that communicates with an electronic receipt server, extracts necessary information, identifies information types, generates exchange data in a standardized format, and transmits it to the server, using a common electronic receipt API and agent program to accommodate different transaction data processing specifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If different agent programs are prepared for different transaction data processing specifications, then the electronic receipt data can be generated accurately according to each specification, but the system complexity and development time increase
Solution Approach 1:
The patent creates a universal agent program that can handle multiple transaction data processing specifications through the use of a common template structure. The template includes standardized fields (transaction ID, timestamp, items, totals) that can accommodate different data formats by simply mapping incoming data to these standard fields, eliminating the need for multiple specialized agent programs while maintaining accurate electronic receipt generation across different POS terminal types
Solution Approach 2:
The patent changes the approach from creating multiple programs with different structures to creating a single program that adapts to different specifications by changing parameter mappings. The system uses configurable field mappings that allow the same agent program to work with various transaction data formats by adjusting how source fields are mapped to template fields, rather than creating entirely different programs for each specification
2Ease of manufacture
If a common agent program is used for all transaction data processing specifications, then the development time and system complexity are reduced, but the ability to accurately handle different specifications may be compromised
Solution Approach 1:
The patent designs a common agent program with universal template capabilities that can accurately handle different transaction data specifications. The template-based approach with configurable field mappings allows the single program to adapt to various POS terminal types and data formats while maintaining the accuracy needed for electronic receipt generation, thus achieving both ease of manufacture and reliability
3Manufacturing precision
If multiple agent programs are maintained for different specifications, then each specification can be optimized, but the maintenance effort and potential for errors increase
Solution Approach 1:
The patent consolidates multiple specialized agent programs into a single universal program with template-based processing. This eliminates the maintenance burden of updating multiple programs while maintaining optimization for different specifications through configurable field mappings and standardized template structures, thus improving ease of repair without sacrificing manufacturing precision
Solution Approach 2:
The patent merges multiple separate agent programs into a single unified program that handles all transaction data specifications. By combining the functionality of multiple programs into one with a common template engine and field mapping mechanism, the system reduces maintenance effort and potential for errors while preserving the ability to handle different specifications accurately
Data Source
AI summary
A transaction data processing apparatus, which communicates with an electronic receipt server, includes a communication interface and a processor configured to perform electronic receipt processing on transaction data having a first format, by (i) extracting, from the transaction data, information items required for generating an electronic receipt, (ii) identifying, for each extracted information item, an information type indicating a category of the extracted information item, (iii) generating exchange data based on the extracted information items and the corresponding information type, the generated exchange data having a second format different from the first format, and (iv) transmitting the generated exchange data to the electronic receipt server through the communication interface.


