Railway Data Standardization via XML Schema
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Railway control systems face challenges in transmitting data in a format that all recipient computers can interpret correctly, as different systems require varying levels of precision for attributes like time and location, leading to operational inefficiencies and scalability issues when new data or systems are added.
Innovation Solution
A data collection and subscription server system utilizing a schema-defined XML document (DTD) to standardize data elements and attributes for train control operations, allowing all computers to access a single source for data interpretation rules, ensuring uniform data processing across the network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is transmitted in a format tailored to each computer's specific requirements, then each computer can process the data correctly, but the system complexity increases and scalability deteriorates when new systems are added
Solution Approach 1:
The patent implements a universal data format (XML schema) that can be interpreted by multiple different computer systems in the railway network. Instead of creating separate data formats for each system, a single standardized schema is defined that all systems must adhere to, enabling one format to serve multiple purposes across different platforms and devices.
Solution Approach 2:
The patent introduces an intermediary layer in the form of a schema definition that mediates between data producers and consumers. This schema acts as a common language or translation layer that converts various data sources into a unified format that all systems can understand, eliminating the need for direct point-to-point compatibility configurations.
2Adaptability or versatility
If different computers require different precision levels for time and location attributes, then each computer can process data according to its needs, but data transmission becomes complex and error-prone
Solution Approach 1:
The patent establishes a standardized schema that defines fixed parameter specifications for data elements such as time and location. Instead of allowing variable precision levels that cause formatting inconsistencies, the schema mandates specific precision requirements (e.g., time in HH:MM:SS format, location as decimal degrees) that all systems must follow, ensuring uniform data structure across the network.
Solution Approach 2:
The patent segments the data into distinct elements with clearly defined attributes and types according to the schema. Each data element (e.g., time, location, temperature) is separated and assigned specific formatting rules, making it easier to validate and process individually while maintaining overall consistency across the data structure.
3Adaptability or versatility
If a universal data format is adopted for all computer systems, then scalability improves and new systems can be integrated easily, but the risk of data misinterpretation increases if the format is not strictly enforced
Solution Approach 1:
The patent performs preliminary action by defining the complete data schema before any data transmission occurs. The schema specifies all allowed elements, their types, formats, and constraints in advance. This preliminary structuring ensures that when data is transmitted, all systems know exactly how to interpret it, preventing misinterpretation while enabling easy scalability.
Solution Approach 2:
The patent incorporates feedback mechanisms through schema validation that checks transmitted data against the defined schema requirements. Systems can validate received data to ensure it conforms to the expected format, and error handling mechanisms can provide feedback when data does not match the schema, ensuring reliable interpretation while maintaining scalability.
Data Source
AI summary
A train control operation system, the system comprising a data collection server for collecting data relating to one or more elements of trains, a network for distributing data relating to the elements to subscribers and a subscription server for hosting definitions of elements which is accessible by subscribers of the system, so as to enable each subscribers to access the definitions from a single source.