Management Server Card Authorization Fare Data Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Card authorization systems face challenges in managing and storing varying attribute information for numerous cards, leading to increased storage needs and slower transmission speeds due to the generation of excessive fare information.
Innovation Solution
A method where a management server receives attribute information from a card issuer server, compares it with stored information, and generates fare information only when the ticket type level of the first attribute information is higher than the second, reducing unnecessary fare information generation and storage, and allowing rapid fare application changes by updating attribute information directly on the card authorization terminal.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the card authorization system stores and manages all attribute information corresponding to the total number of issued cards, then complete fare management is achieved, but large storage area is required
Solution Approach 1:
The patent extracts only the necessary attribute information from cards into a separate attribute information table, rather than storing all card data. This selective extraction reduces storage requirements while maintaining the ability to manage fare information effectively for billing purposes
Solution Approach 2:
The system segments card information into multiple tables: card information table storing card numbers, attribute information table storing ticket type attributes, and fare information table storing billing data. This segmentation allows efficient storage and retrieval of specific fare-related attributes without storing redundant data across all tables
2Reliability
If fare information is generated for all cards, then accurate billing is achieved, but transmission speed decreases
Solution Approach 1:
The system extracts and stores only the ticket type attribute information in a separate attribute information table, which is then used to generate fare information. This extraction approach reduces the amount of data that needs to be transmitted while ensuring accurate billing based on cardholder attributes
Solution Approach 2:
The system performs preliminary extraction and storage of attribute information in the attribute information table before fare calculation. This preliminary action allows rapid retrieval of ticket type attributes during fare generation, improving transmission speed without compromising billing accuracy
3Reliability
If fare information is generated for all cards, then complete billing coverage is achieved, but the amount of fare information increases
Solution Approach 1:
The system extracts only the essential ticket type attributes from card information and stores them in the attribute information table. This extraction reduces the quantity of fare information that needs to be generated and transmitted, while maintaining complete billing coverage through the use of card number as a unique identifier to link back to full card details when needed
Solution Approach 2:
The system segments billing data into separate tables, storing only fare calculation attributes in the attribute information table and generating fare information on-demand using the fare information table. This segmentation reduces the amount of stored fare information while ensuring complete billing coverage through efficient data retrieval and generation
Data Source
AI summary
A card authorization method of a management server includes receiving first attribute information corresponding to a unique card number of a card from a card issuer server, extracting second attribute information corresponding to the unique card number of the card from a database, comparing the second attribute information with the first attribute information, generating fare information for billing to the card based on the comparison result, and transmitting the fare information to a card authorization terminal.