Mobile Terminal Usage Record Display with Server Route Correlation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for displaying usage records on mobile terminals struggle to provide clear and up-to-date information, especially when new public transit routes are introduced, as they often rely solely on reading data from transportation cards without correlating this data with specific vehicle routes.
Innovation Solution
A method and system where a mobile terminal reads usage records from a transportation card, acquires a terminal number, and sends a route identifier query request to a server. The server, pre-stored with correspondence between terminal numbers and route identifiers, returns the associated route identifier, which the terminal then displays alongside the usage records, enabling users to understand the usage context.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the mobile terminal displays only the raw usage record from the transportation card, then the device complexity is low, but the information clarity and user understanding deteriorates
Solution Approach 1:
The patent introduces a server as an intermediary between the mobile terminal and the transportation card data. The server stores the correspondence between terminal numbers and route identifiers, and provides query services to the mobile terminal. This mediator resolves the contradiction by enabling rich information display without increasing the complexity of the mobile terminal itself.
Solution Approach 2:
The system is segmented into three independent components: the transportation card (data source), the server (data processing and storage), and the mobile terminal (display device). Each component has a specific function, which reduces the complexity of individual components while maintaining overall system capability to provide clear information.
2Adaptability or versatility
If the system uses only terminal numbers from transportation cards, then the data storage requirement is low, but the adaptability to new transit routes deteriorates
Solution Approach 1:
The server database is designed to store correspondence between terminal numbers and route identifiers for multiple routes. This universal storage structure can accommodate new transit routes by simply adding new entries to the database, without requiring changes to the system architecture or mobile terminal functionality. The server handles route-specific information centrally, enabling the system to adapt to various routes.
3Loss of information
If the mobile terminal queries route information for every usage record, then the information completeness is high, but the time consumption increases
Solution Approach 1:
The server pre-stores the correspondence between terminal numbers and route identifiers in its database. When the mobile terminal needs to display usage records, it queries the server for route identifiers based on terminal numbers. The server quickly retrieves pre-stored information and returns it to the terminal, avoiding time-consuming real-time analysis or complex calculations.
Data Source
AI summary
A method, apparatus, and system are provided for displaying usage records. The method includes: reading a usage record stored in a transportation card and acquiring a terminal number corresponding to the usage record; transmitting a route identifier query request to a server, the route identifier query request including the terminal number corresponding to the usage record; receiving a route identifier of a vehicle associated with the terminal number of the usage record; and displaying the usage record as well as the route identifier of a vehicle associated with the terminal number corresponding to the usage record.