Batch Linkage Configuration for Rail Transit Dispatch Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing comprehensive operation dispatching systems in rail transit face challenges in efficiently configuring and managing thousands of predefined linkage scenarios, which are cumbersome and time-consuming due to the need for individual configuration of each piece of information across multiple pages.

Innovation Solution

A method for batch configuration of linkages that involves loading linkage node data into a linkage table and an address space, retrieving data based on keywords representing linkage node types, and loading data into all relevant linkage nodes in batches, thereby simplifying the configuration process and reducing workload.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If each piece of linkage information is configured one by one in a data configuration tool, then the configuration can be performed with simple tools, but the workload becomes huge and time-consuming

Engineering Contradiction:
Improveconfiguration simplicityVSAvoidconfiguration time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent merges multiple configuration operations into a single batch configuration process. The data configuration tool allows users to select multiple linkage nodes and configure their information simultaneously in one operation, rather than configuring each node individually across multiple pages. This combining of operations directly addresses the contradiction by maintaining operational simplicity while dramatically reducing configuration time and workload.

Inventive Principle:
Principle #5Merging (Combining)

2Quantity of substance

If linkage data is distributed across different pages and positions, then the system can store comprehensive information, but it impedes maintenance and management

Engineering Contradiction:
Improveinformation completenessVSAvoidmaintenance ease
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

The patent segments the linkage data into a structured format where each linkage node is represented as a distinct entity with its own attributes. This segmentation allows the system to store comprehensive information while making it easier to manage, as each segment can be independently configured, searched, and modified through the batch configuration tool. The structured segmentation transforms the scattered information across pages into an organized, maintainable data structure.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If thousands of predefined linkage scenarios are defined, then the system can handle comprehensive events, but the configuration process becomes cumbersome

Engineering Contradiction:
Improveevent coverageVSAvoidconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal data configuration tool that can handle all types of linkage nodes and scenarios through a single interface. The batch configuration capability allows the same tool to manage thousands of predefined linkage scenarios without increasing operational complexity. The universal design enables users to configure different linkage types (triggering conditions, actions, attributes) using the same procedures, thereby maintaining event coverage while reducing configuration complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12321392B2Method for batch configuration of linkages, terminal, server, electronic device, and storage medium
Publication Date: 2025.06.03 BYD CO LTD
  • US12321392B2 patent drawing
  • US12321392B2 patent drawing
  • US12321392B2 patent drawing

AI summary

A method for batch configuration of linkages, a terminal, a server, an electronic device, and a storage medium are provided. The method for batch configuration of linkages includes the following steps. Data of linkage nodes configured in a linkage table and data of linkage nodes in an address space are loaded. Each of the linkage nodes configured in the linkage table includes a keyword representing a type of the linkage node. The data in the address space is retrieved based on the keywords representing the types of the linkage nodes. The data of the linkage nodes configured in the linkage table is loaded into all retrieved linkage nodes in batches.