Remote Vehicle Initialization via Off-Board Data Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current vehicle system initialization processes, particularly for rail vehicles using positive train control (PTC) systems, are lengthy and time-consuming, leading to delays and decreased average velocity due to manual data entry and review of mandatory directives on small displays with limited software configuration capabilities.
Innovation Solution
A method and system that utilize an off-board computer device to receive and communicate trip data, mandatory directives, and software configuration requirements to an onboard controller, enabling efficient data transfer and initialization through a web-based application, which reduces the need for manual data entry and ensures compatibility with back-office systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual initialization process is used with small display and limited keys, then crew members can review mandatory directives, but initialization time becomes excessively long
Solution Approach 1:
The system performs preliminary actions by automatically downloading and storing mandatory directives, route information, and software configuration requirements in the onboard database before the vehicle departs. This eliminates the need for manual data entry during initialization and allows the crew to review pre-fetched information, significantly reducing initialization time while maintaining completeness of directive review.
Solution Approach 2:
The patent introduces an onboard database as an intermediary between the wireless network and the initialization display system. The database stores mandatory directives and route information locally, allowing the crew to review complete information without real-time network connection or manual data entry, thus resolving the contradiction between comprehensive review and time efficiency.
2Loss of information
If mandatory directives are downloaded via wireless network or radio, then complete directive data can be obtained, but data transfer time increases significantly
Solution Approach 1:
The system downloads and stores complete mandatory directive data, route information, and software configuration requirements in the onboard database before vehicle departure or during idle periods. This preliminary data acquisition ensures that all necessary information is available locally without requiring time-consuming wireless transfers during critical initialization periods.
Solution Approach 2:
The patent creates local copies of mandatory directives and route information in the onboard database, eliminating the need for repeated wireless network access during initialization. The crew can review these locally stored copies immediately, ensuring information completeness while minimizing data transfer time.
3Ease of operation
If crew members manually enter route information and review directives onboard, then system initialization can be completed, but average vehicle velocity decreases due to delays
Solution Approach 1:
The system performs self-service by automatically acquiring trip data from back-office systems, downloading mandatory directives, verifying software configuration requirements, and populating the onboard database without requiring manual crew intervention. The crew retains the ability to review and confirm the automatically populated information, maintaining operational oversight while eliminating time-consuming manual data entry that reduces vehicle velocity.
Solution Approach 2:
All data acquisition, validation, and database population operations are performed in advance of vehicle departure during idle periods or automatically upon system startup. This preliminary processing allows the vehicle to depart promptly with complete initialization data already in place, thereby maintaining both ease of operation for crew review and high average vehicle velocity.
4Adaptability or versatility
If onboard segment performs all initialization tasks, then system can be self-sufficient, but initialization process becomes excessively lengthy
Solution Approach 1:
The onboard system performs preliminary data acquisition by automatically connecting to back-office systems, retrieving trip data, mandatory directives, and software configuration requirements before vehicle operation begins. This advance preparation maintains the self-sufficiency of the onboard system while dramatically reducing the time required for initialization during actual vehicle operation.
Solution Approach 2:
The system maintains continuous useful action by automatically performing data acquisition, validation, and database population operations during idle periods or background processes rather than requiring dedicated initialization time. This continuous background processing ensures the onboard system remains self-sufficient while minimizing the impact on vehicle operational timing.
Data Source
AI summary
A remote initialization system and method for a vehicle system receive trip data for an upcoming trip at an off-board device. Using the off-board device, the trip data is communicated to the different back-office systems, and one or more of mandatory directives or software configuration requirements are received at the off-board device from the different back-office systems. An initialization data set that includes at least some of the trip data and at least some of the one or more of the mandatory directives or the software configuration requirements is communicated from the off-board device to an onboard controller of the vehicle system. The initialization data set is configured to be used by the onboard controller to control movement of the vehicle system in the different sets of the routes.