Method and device for acquiring parameter state of equipment element of motor train unit

Abstract

The invention provides a method and a device for acquiring parameter states of equipment elements of a motor train unit, and relates to the technical field of rail transit industrial control. The method comprises the steps of generating a configuration file in response to an interface editing operation action triggered by a user; generating an interface file capable of representing a control structure, layout and an appearance style according to the configuration file; and updating a control display state in the interface file according to the real-time change information of the parameter data of the equipment element of the motor train unit by utilizing a pre-established communication connection relationship between the parameter of the equipment element of the motor train unit and the control. The device executes the method. According to the method and the device for acquiring the parameter state of the equipment element of the motor train unit provided by the embodiment of the invention, compiling of a large number of codes can be avoided through the configuration file, and personalized demand design of a user can be autonomously and flexibly realized by automatically generating the interface file capable of representing the structure, layout and appearance style of the control; and the parameter state of the equipment element of the motor train unit can be displayed efficiently and visually.

Description

Technical Field

[0001] This invention relates to the field of rail transit industrial control technology, specifically to a method and device for obtaining the parameter status of components in high-speed train equipment. Background Technology

[0002] Currently, high-speed rail displays are mainly used to show various real-time status data of the train, including parameters and statuses of various subsystems such as traction, braking, network communication, and safety monitoring. Most of this data is transmitted via the Train Control and Monitoring System (TCMS) using real-time communication protocols. In practical applications, the displays need to be able to quickly and accurately display the real-time status of different trains and carriages, while also requiring flexible interface layouts and efficient data interaction capabilities.

[0003] Traditional high-speed rail display screen development typically relies on a single development tool for designing controls and status displays for each interface. The design of each display interface, control, and status requires developers to manually write a large amount of code for interface layout and functionality implementation. In particular, the status displayed by each control is related to multiple variables, with different values ​​representing different meanings. Due to significant differences in equipment configurations between different carriages, the design workload for each display control is extremely large, resulting in long development cycles, massive amounts of code, and a high susceptibility to errors and poor maintainability.

[0004] In addition, existing technologies also have the following major problems:

[0005] Complex interface layout and control configuration, and a large amount of manual coding: Traditional development methods require developers to manually adjust the layout and property configuration of each control and write a lot of code to implement functionality. This development model is not only labor-intensive, but also prone to human error.

[0006] Data interaction and real-time updates are challenging: Existing technologies cannot achieve efficient binding and real-time updates between controls and backend data, resulting in poor synchronization between the interface and the data. This is especially problematic in scenarios requiring real-time display of train status, where data delays and inconsistencies can negatively impact the system's accuracy and reliability.

[0007] Managing multiple pages and controls is inconvenient: High-speed rail displays contain a large number of controls, states, and variables, making their management extremely complex. Especially in the case of equipment in multiple carriages and on multiple trains, existing technologies cannot provide an efficient management method, leading to increased difficulty in maintenance and expansion.

[0008] Personalized configuration is challenging: the status display requirements of different carriages and train equipment vary significantly, and existing configuration methods cannot flexibly meet the personalized needs of high-speed rail displays. Customized display requirements often cannot be effectively achieved through existing technical solutions.

[0009] Although some low-code platforms on the market support control configuration and interface generation, most of these platforms are designed for general application scenarios and lack dedicated functions for high-speed rail displays and real-time data monitoring. Specifically, existing technologies are insufficient in the following aspects:

[0010] Lack of dedicated support for high-speed rail displays: Existing low-code platforms often cannot adequately meet the specific requirements of high-speed rail displays for real-time data display, interactive controls, and customization.

[0011] Poor real-time interactivity between interface and data: Due to the lack of an efficient data communication mechanism, existing platforms struggle to achieve real-time interaction between the interface and backend data, resulting in delayed or inaccurate data updates.

[0012] Poor flexibility and difficult maintenance: The existing configuration and management methods cannot effectively support the scalability and flexibility of high-speed rail display systems, especially when dealing with multiple trains, multiple carriages and personalized needs, the maintenance is quite difficult. Summary of the Invention

[0013] In view of the problems in the prior art, the present invention provides a method and apparatus for obtaining the parameter status of EMU equipment components, which can at least partially solve the problems existing in the prior art.

[0014] On one hand, this invention proposes a method for obtaining the parameter status of components in high-speed train equipment, including:

[0015] Respond to user-triggered UI editing actions and generate configuration files;

[0016] Generate an interface file that represents the control structure, layout, and appearance style based on the configuration file;

[0017] The communication connection between the pre-established parameters of the EMU equipment components and the controls is utilized, and the display status of the controls in the interface file is updated according to the real-time changes in the EMU equipment component parameter data.

[0018] The step of generating a configuration file in response to a user-triggered interface editing action includes:

[0019] Respond to user editing actions triggered by the interface editor to obtain interface-related configuration information;

[0020] Respond to user actions that trigger variable editing based on the variable editor, and obtain variable association configuration information;

[0021] The configuration file is generated based on the interface association configuration information and the variable association configuration information.

[0022] The step of responding to user editing actions triggered by the interface editor to obtain interface-related configuration information includes:

[0023] Responding to the user's action of building a system structure tree triggered by the interface editor, the basic attributes of the interface and the categorized planning interface are obtained;

[0024] Responding to the user's action of configuring jump logic on the classification planning interface, the association between various related interfaces is realized, and the target related interface is determined from the related interfaces;

[0025] In response to the user's configuration action on the target associated interface based on the interface editor, the associated interface configuration information is obtained.

[0026] The method for obtaining the parameter status of the EMU equipment components further includes:

[0027] Responding to user actions that configure interface elements based on the interface editor, obtain interface association configuration information containing basic element attributes, interaction attributes, and text attributes.

[0028] The process of responding to a user's variable editing action triggered by the variable editor to obtain variable association configuration information includes:

[0029] In response to user actions triggered by the variable editor to configure variable mapping and variable protocol, the variable association configuration information is obtained.

[0030] The step of generating an interface file representing the control structure, layout, and appearance style based on the configuration file includes:

[0031] Generate an appearance style file based on the style attributes in the basic interface attributes;

[0032] The configuration file is parsed to generate the original interface file; the original interface file contains the control structure and layout information.

[0033] The appearance style file is embedded into the original interface file to obtain the interface file.

[0034] On one hand, the present invention proposes a device for acquiring the parameter status of components of a high-speed train, comprising:

[0035] The first generation unit is used to generate configuration files in response to user-triggered interface editing actions.

[0036] The second generation unit is used to generate an interface file that can represent the control structure, layout and appearance style according to the configuration file;

[0037] The update unit is used to update the display status of the controls in the interface file by utilizing the pre-established communication connection relationship between the EMU equipment component parameters and the controls, and according to the real-time change information of the EMU equipment component parameter data.

[0038] In another aspect, embodiments of the present invention provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the following method:

[0039] Respond to user-triggered UI editing actions and generate configuration files;

[0040] Generate an interface file that represents the control structure, layout, and appearance style based on the configuration file;

[0041] The communication connection between the pre-established parameters of the EMU equipment components and the controls is utilized, and the display status of the controls in the interface file is updated according to the real-time changes in the EMU equipment component parameter data.

[0042] This invention provides a computer-readable storage medium, comprising:

[0043] The computer-readable storage medium stores a computer program that, when executed by a processor, implements the following method:

[0044] Respond to user-triggered UI editing actions and generate configuration files;

[0045] Generate an interface file that represents the control structure, layout, and appearance style based on the configuration file;

[0046] The communication connection between the pre-established parameters of the EMU equipment components and the controls is utilized, and the display status of the controls in the interface file is updated according to the real-time changes in the EMU equipment component parameter data.

[0047] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the following method:

[0048] Respond to user-triggered UI editing actions and generate configuration files;

[0049] Generate an interface file that represents the control structure, layout, and appearance style based on the configuration file;

[0050] The communication connection between the pre-established parameters of the EMU equipment components and the controls is utilized, and the display status of the controls in the interface file is updated according to the real-time changes in the EMU equipment component parameter data.

[0051] The method and apparatus for obtaining the status of EMU equipment component parameters provided in this embodiment of the invention respond to user-triggered interface editing operations to generate a configuration file; generate an interface file that can represent the structure, layout, and appearance of controls based on the configuration file; utilize the pre-established communication connection relationship between EMU equipment component parameters and controls, and update the display status of controls in the interface file according to the real-time change information of EMU equipment component parameter data. By using the configuration file, a large amount of code can be avoided. By automatically generating an interface file that can represent the structure, layout, and appearance of controls, the user's personalized design needs can be realized autonomously and flexibly, thereby efficiently and intuitively displaying the status of EMU equipment component parameters. Attached Figure Description

[0052] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0053] Figure 1 This is a flowchart illustrating a method for obtaining the status of components in a high-speed train according to an embodiment of the present invention.

[0054] Figure 2 This is a flowchart illustrating a method for obtaining the status of parameters of EMU equipment components according to another embodiment of the present invention.

[0055] Figure 3 This is a flowchart illustrating a method for obtaining the status of parameters of EMU equipment components according to another embodiment of the present invention.

[0056] Figure 4 This is a flowchart illustrating a method for obtaining the status of parameters of EMU equipment components according to another embodiment of the present invention.

[0057] Figure 5 This is a flowchart illustrating a method for obtaining the status of parameters of EMU equipment components according to another embodiment of the present invention.

[0058] Figure 6 This is a schematic diagram of the structure of a device for acquiring the status of parameters of EMU equipment components provided in an embodiment of the present invention.

[0059] Figure 7 This is a schematic diagram of the physical structure of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments and descriptions of the present invention are used to explain the present invention, but are not intended to limit the present invention. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other.

[0061] Figure 1 This is a flowchart illustrating a method for obtaining the status of components in a high-speed train according to an embodiment of the present invention. Figure 1 As shown, the method for obtaining the parameter status of EMU equipment components provided in this embodiment of the invention includes:

[0062] Step S1: Respond to user-triggered interface editing actions and generate a configuration file.

[0063] Step S2: Generate an interface file that represents the control structure, layout, and appearance style based on the configuration file.

[0064] Step S3: Utilize the pre-established communication connection between the EMU equipment component parameters and controls, and update the control display status in the interface file according to the real-time change information of the EMU equipment component parameter data.

[0065] In step S1 above, the device responds to the user-triggered interface editing operation and generates a configuration file. The device can be a computer device executing this method. The acquisition, storage, use, and processing of data in this application's technical solution all comply with relevant regulations.

[0066] The process of generating a configuration file in response to user-triggered interface editing actions includes:

[0067] Respond to user editing actions triggered by the interface editor to obtain interface-related configuration information;

[0068] Respond to user actions that trigger variable editing based on the variable editor, and obtain variable association configuration information;

[0069] The configuration file is generated based on the interface association configuration information and the variable association configuration information.

[0070] The response to user editing actions triggered by the interface editor yields interface-related configuration information, including:

[0071] Responding to the user's action of building a system structure tree triggered by the interface editor, the basic attributes of the interface and the categorized planning interface are obtained;

[0072] Responding to the user's action of configuring jump logic on the classification planning interface, the association between various related interfaces is realized, and the target related interface is determined from the related interfaces;

[0073] In response to the user's configuration action on the target associated interface based on the interface editor, the associated interface configuration information is obtained.

[0074] like Figure 2 As shown, users can use the interface editor to build a system structure tree. First, define the basic display attributes, including resolution, total number of pages, and default homepage ID. Then, categorize and plan the interfaces according to the train topology. For example, the traction system interface includes single-unit and multiple-unit interfaces, while the carriage monitoring interface is distinguished by carriage number (e.g., carriage 1, carriage 2, etc.). Simultaneously, configure the jump logic between interfaces; for example, clicking the "Multiple-Unit" button on the traction interface should jump to the corresponding multiple-unit interface ID.

[0075] In addition, the hierarchical relationship of the interface needs to be defined, such as the relationship between parent and child interfaces, to ensure that the entire interface structure conforms to the operation logic of the train monitoring system. Three special page IDs are marked: 001 as the public information display area (top of the page), 002 as the navigation bar (bottom of the page), and 003 as the fault pop-up (overlay). These three special pages are the target associated interfaces.

[0076] The method for obtaining the parameter status of the EMU equipment components also includes:

[0077] Responding to user actions triggering interface element configuration via the interface editor, the system obtains interface-related configuration information containing basic element attributes, interaction attributes, and text attributes. Users can configure interface elements using the interface editor. Within a single interface, each element's attributes can be defined in detail.

[0078] Regarding the basic attributes of the elements, the geometric position of the control is precisely determined by the top-left corner coordinates (x, y), width, and height. Style attributes such as background image URL, background color, border thickness, color, and rounded corners are also configured. For interactive attributes, the target page ID to which the control will redirect when clicked is set. For example, clicking the "Brake Interface" button will redirect to the brake system interface ID. Interactive feedback such as color changes and shadow effects when the mouse hovers over the control is also defined.

[0079] Regarding text attributes, clearly define static text content or dynamic variable references (such as "current speed: {{speed}}km / h"), and set styles such as font size, color, and alignment to ensure that the displayed content is clear and easy to read.

[0080] The response to a user's variable editing action triggered by the variable editor yields variable association configuration information, including:

[0081] In response to user actions triggered by the variable editor to configure variable mapping and variable protocol, the variable association configuration information is obtained.

[0082] Users use the variable editor to map variables to the display dictionary. Each variable is assigned a unique ID and name, such as "traction motor status" or "train speed." A display dictionary is built, defining the mapping relationship between variable values ​​and displayed content. For example, a variable value of 1 displays "Online" in green (#00FF00), and a variable value of 0 displays "Offline" in red (#FF0000). The unit of the variable is also configured, such as speed unit "km / h" or pressure unit "kPa." Variables are bound to interface elements, specifying the variable ID associated with each element and defining rules for converting variable values ​​to displayed content, supporting numerical range mapping (e.g., displaying different colors for different temperature ranges).

[0083] Users should use the variable editor to configure the protocol and data parsing. For each variable, configure the relevant TRDP protocol parameters. Set the COMID to specify the communication channel, such as COM101, COM102, etc.; determine the byte offset (e.g., 0x0010) and bit offset (e.g., 2) to accurately locate the data position in the message; select appropriate data types, including uint8, int16, float32, etc., for example, setting the traction status variable to uint8 type and the train speed variable to float32 type. Ensure that the protocol configuration is consistent with the communication requirements of the Train Control and Monitoring System (TCMS) to guarantee the accuracy and real-time performance of data transmission.

[0084] The following explains the process of "responding to the user's configuration action on the target associated interface based on the interface editor and obtaining the interface association configuration information":

[0085] Users configure the public information display area (ID=001) using the interface editor. Set fixed position parameters to place it at the top of the page (e.g., y=0, height 80 pixels), with a width matching the screen resolution. Add a speed display element, bind it to a train speed variable, set the font size to 36px, color to white, and right-aligned. Add a time display element, bind it to a system time variable, format it as "YYYY-MM-DDHH:MM:SS", font size to 24px, color to white, and center-aligned. Add an alarm status indicator, bind it to an alarm variable, set it to a circular icon, initially gray (#CCCCCC), turning red (#FF0000) and flashing when an alarm occurs. Add a warning status indicator, bind it to a warning variable, set it to a triangle icon, initially gray, turning yellow (#FFFF00) and flashing when a warning occurs. Configure the background color to dark blue (#00008B) to ensure differentiation from the main interface.

[0086] Users configure the navigation bar (ID=002) using the interface editor. Set fixed position parameters to place it at the bottom of the page (e.g., y=1000, height 80 pixels), with a width matching the screen resolution. Generate navigation buttons for each main page based on the page list in the system structure tree. The buttons have evenly distributed width, a height of 60 pixels, and are centered. Configure a click event for each button to navigate to the corresponding page ID; for example, clicking the "Traction System" button navigates to the traction interface ID. Set the button's default style to a light blue background (#ADD8E6), black text, and a dark blue background (#1E90FF) on hover. Add a current page indicator, displaying the current page name above the navigation bar with a 28px font size, white color, and centered alignment.

[0087] Configure the fault pop-up (ID=003) using the interface editor. Set the overlay properties: width and height should match the screen resolution, initial opacity to 0 (completely transparent), and maximum z-index value (e.g., 9999) to ensure it covers the entire page. Add a background overlay layer, black in color, with an opacity of 0.7, to reduce the brightness of the underlying page and highlight the pop-up content. Design three pop-up templates based on the fault type (warning, alarm, video linkage): warning pop-ups use a yellow border (#FFFF00) with the title "Warning Information"; alarm pop-ups use a red border (#FF0000) with the title "Alarm Information"; and video linkage pop-ups use a blue border (#00BFFF) with the title "Video Linkage". Add a content display area in the center of the pop-up to show fault details, handling suggestions, and other text information, with a font size of 24px and a white color. Add a confirmation button; clicking it closes the pop-up and restores the page to normal display.

[0088] Generate a configuration file in JSON format. For example... Figure 2 As shown, the first level is "systemStructure", which includes the basic attributes of the display screen and the page tree structure. Each node in the page tree records information such as interface ID, name, topology type, and parent-child page relationship. The functions and hierarchical relationships of the three special pages 001, 002, and 003 are specially marked.

[0089] Secondly, using "pageElements" as the second level, grouping by interface ID, each interface contains the configuration of all elements, including element ID, type, position, style, interaction actions, etc., to ensure that the element configuration of special pages is complete.

[0090] Then, the "variableMappings" level records the variable ID, name, unit, display dictionary, and element binding relationships, covering variable references across all pages. The "protocolSettings" level corresponds to the variable's COMID, byte offset, bit offset, and data type. After integration, the system automatically verifies data consistency, such as checking if the variables bound to elements exist and if the protocol parameters are valid, while compressing redundant data to optimize file size.

[0091] In step S2 above, the device generates an interface file representing the control structure, layout, and appearance style according to the configuration file. Generating the interface file representing the control structure, layout, and appearance style according to the configuration file includes:

[0092] Generate an appearance style file based on the style attributes in the basic interface attributes;

[0093] The configuration file is parsed to generate the original interface file; the original interface file contains the control structure and layout information.

[0094] The appearance style file is embedded into the original interface file to obtain the interface file.

[0095] like Figure 3 As shown, a CSS style file, i.e., an appearance style file, is generated. Based on the style properties in the element configuration, basic styles are generated. The positioning, size, and display status class of the page container are defined (e.g., the `.active` class is used to display the current page); general styles for elements are defined, including positioning methods; and specific styles are generated for different types of elements, such as buttons and indicator lights, such as background images and hover effects for buttons, and circular border styles for indicator lights. Dedicated styles are generated for special pages: a fixed top position and background color are set for the public information display area; a fixed bottom position and background color are set for the navigation bar; and overlay styles, background mask styles, and border styles for three types of faults are set for fault pop-ups. Based on the color configuration in the variable display dictionary, status classes are generated (e.g., `.status-online{color:#00FF00}`), facilitating dynamic switching of element styles. Simultaneously, background color, font size, and other styles are parameterized, supporting dynamic adjustment via configuration files.

[0096] Parse JSON to generate the HTML structure, i.e., the original interface file. Read the "pageTree" information from the JSON and generate a corresponding HTML structure for each interface. The container is configured with a `data-page-id` attribute to identify the page ID, and its size is set according to the screen resolution. Inside the page container, an `elements-container` container is created, and a corresponding `data-page-id` is generated for each element based on the element configuration in `pageElements`. The `<data-element-id>` tag sets the `data-element-type` and `data-element-id` attributes, and defines the element's position (left, top), size (width, height), background image, background color, etc., through inline styles or class names. Special handling is provided for special pages: a fixed top position is set for the public information display area (ID=001); a fixed bottom position is set for the navigation bar (ID=002); and an absolute position is set for the error pop-up (ID=003), initially hiding it.

[0097] In step S3 above, the device utilizes the pre-established communication connection between the EMU equipment component parameters and the controls, and updates the control display status in the interface file according to the real-time change information of the EMU equipment component parameter data.

[0098] Write JavaScript interaction logic. Implement page navigation functionality, iterate through all button elements, bind click events, and switch the page display state (hide the current page, show the target page) by retrieving the `data-target-page` attribute value. Establish a WebSocket connection to communicate with the backend TCMS system and receive real-time data packets. After parsing the data, find the corresponding element ID based on the binding relationship in "variableMappings" and call the update function. The update function converts the data value into display text and color based on the variable's display dictionary, dynamically modifying the element's background color, text content, and other styles to achieve real-time updates of the interface data. Specially handle the interaction logic of special pages: update the speed, time, alarm status, etc. in the public information display area in real time; highlight the corresponding button in the navigation bar based on the current page ID; monitor fault data, and display the corresponding fault pop-up when a warning, alarm, or video linkage signal is received.

[0099] Integrate a WebSocket data communication module. Initialize a WebSocket instance in JavaScript, connect to the backend server address (e.g., ws: / / localhost:8080), and set callback functions for successful connection, data reception, and connection errors. In the data reception callback, parse the JSON-formatted message, extract variable IDs and corresponding values, and call the element update function. Special handling for fault data: When receiving warning or alarm data, construct pop-up content based on the fault type, set the pop-up title, details text, and border color, and then display the pop-up; when receiving a video linkage signal, obtain the video source address, embed a video player in the pop-up, and display it. Simultaneously, handle disconnection and reconnection logic to ensure communication stability, avoid data update interruptions due to network fluctuations, and ensure that the train's display screen reflects the train's status in real time.

[0100] Optimize front-end code performance. Compress generated HTML, CSS, and JavaScript code to reduce file size and improve loading speed. Optimize DOM manipulation by using event delegation to handle click events of similar elements, avoiding performance degradation caused by excessive event binding. Batch render real-time updated elements to reduce repaints and reflows, ensuring smooth interface response. For multi-page scenarios, implement a lazy loading mechanism, initially loading only the default page and special pages (public information display area, navigation bar), with other pages dynamically loaded as needed, improving overall system efficiency. Add animation effects to error pop-ups, such as fade-in / fade-out and sliding displays, to enhance user experience without impacting system performance.

[0101] like Figure 4 As shown, a Qt-based WebSocket server framework is set up. A WebSocket server instance is initialized in the Qt application, bound to a specified port (e.g., 8080), and frontend connection requests are monitored. When a client (frontend page) initiates a connection, the server creates a corresponding WebSocket client connection object and maintains a connection list to manage concurrent requests from multiple pages. A connection timeout mechanism and reconnection logic are configured to ensure stable communication.

[0102] Request routing and distribution mechanism. After receiving a request from the frontend, the server parses the page ID (such as 001 for public information area, or ID for ordinary business page) or request type (data retrieval, interface configuration update) in the request message, and distributes the request to the corresponding processing module according to the preset routing rules. For example, when requesting page data with ID=001, it is routed to the public information processing module; when requesting data for the traction system interface, it is routed to the traction processing module.

[0103] Implement the business logic layer of the processing modules. Each processing module is responsible for handling requests from its corresponding business domain, receiving parameters (such as page ID and control number) from the front end, and calling underlying service modules for data processing. For example, the public information processing module calls the time service module to obtain the system time, the speed service module to obtain the train speed, and the alarm service module to obtain the warning status, and then integrates the data and encapsulates it into a response message. Another example is the traction processing module, which, based on the requested single-unit / multi-unit interface ID, calls the TRDP data service module to obtain parameters such as traction motor status, voltage, and current, and then organizes the data according to the interface element binding relationships.

[0104] Construct a TRDP service module. The TRDP service module encapsulates the underlying data acquisition and processing logic: First, it connects to the train control network using a TRDP protocol stack implemented in Qt, and reads real-time data according to the protocol configuration (COMID, byte offset, bit offset). For example, it reads traction status data from byte 0x0012 of COM101 channel and parses it into a uint8 type value.

[0105] Construct a TCP / UDP service module. TCP / UDP is used to receive TCP / UDP packets from various devices in the PIS network, and to perform data cleaning, transformation, and correlation calculations.

[0106] The service module generates a response message and pushes it to the front end. After processing the data, the service module returns it to the processing module, which encapsulates the data into a JSON message (containing variable IDs, values, display status, etc.) according to the format agreed upon by the front end. Data is then pushed to the corresponding front end page via a WebSocket connection. For example, when traction status data is updated, an update message containing var001 (traction motor status) is pushed to all clients with the traction interface open. The front end updates the indicator light color and text according to the display dictionary. Another example is when alarm data is received from the TCMS; the processing module calls the alarm service module to generate pop-up content, which is then pushed to all clients to trigger the display of a fault pop-up (ID=003).

[0107] Implement data caching and asynchronous processing mechanisms. In the Qt server, a separate QThread is used to create a data cache pool. A cache expiration time is set for all TRDP data, and the TRDP data is updated continuously within this thread. This prevents the main thread from blocking and ensures the server's real-time response capability to frontend requests.

[0108] Integrate error handling and logging systems. Add an exception handling mechanism to the processing and service module layers. When TRDP data reading fails (e.g., communication timeout) or protocol parsing errors occur (e.g., data type mismatch), an error response message is generated and returned to the front end, while simultaneously logging the error (including time, module, error code, and original data). The logging system supports tiered output (debugging, warning, error), facilitating problem tracing during subsequent maintenance, such as pinpointing the specific cause of an anomaly in the update of a train door's status data.

[0109] The final architecture shown in this invention is as follows Figure 5 As shown.

[0110] The method for obtaining the status of EMU equipment components provided in this embodiment of the invention, based on modularity, is described below:

[0111] The method for implementing this invention comprises five core modules: a configuration module, a page generation module, a real-time data communication module, a control management module, and a style generation module. These modules work closely together to ensure that the development of the high-speed rail display screen interface can proceed efficiently and smoothly.

[0112] The configuration module is the starting point of the low-code platform, responsible for receiving user interface configuration requests and generating configuration files. The configuration module provides a page editor, or interface editor, which consists of four parts: all pages, all controls within a page, page editing, and all properties of each control. Developers use this page editor to design pages. This module provides a graphical interface that allows users to configure the type, position, style, and associated variables of pages and controls through drag-and-drop, input, and other methods. After configuration, the system saves these configurations as a standard JSON file for use by the subsequent page generation module.

[0113] The configuration file contains basic page attributes (such as pageid, title, etc.), attributes for each control (such as top-left x-coordinate, y-coordinate, width, height, color, font, control type, control ID, control name, etc.), and the binding relationships between controls and data variables. Users can easily adjust the layout and style of controls, and even the association between controls and specific data, through the interface. The flexibility of the configuration module means that interface development is no longer limited to writing large amounts of code, but can quickly generate the target interface through simple configuration.

[0114] The page generation module parses the JSON file generated by the configuration module, producing an HTML div for each page. This div consists of the page ID and the number of elements. Under this div, further divs for various controls are generated, each control element defining geometric positioning parameters and data binding identifier attributes. Based on this method, the JSON file automatically generates the corresponding HTML, JavaScript, and CSS files. The HTML file describes the structure and layout of the controls, the CSS file handles the appearance and style of the controls, and the JavaScript file is responsible for the interaction and updates between the controls and real-time data. Through this module, developers can easily generate pages and controls that meet requirements without manually writing front-end code.

[0115] The core advantage of this module lies in its highly automated functionality: whether it's a simple text box or a complex chart control, everything can be automatically generated through a configuration file. Developers only need to focus on the overall interface structure and data binding, reducing tedious front-end development work and greatly improving development efficiency and flexibility.

[0116] The real-time data communication module is one of the core modules in the low-code platform, responsible for real-time data interaction with backend systems (such as the TCMS system for high-speed trains). The frontend communicates with the backend Qt WebSocket server via WebSocket. The Qt-implemented real-time data communication module can periodically obtain train status data (such as traction status, braking status, axle temperature data, etc.) from the TCMS system, and automatically update the controls displayed on the page via JavaScript when the data changes.

[0117] This system implements train control network communication based on the Qt framework, incorporating MVB (Multi-Function Vehicle Bus), TRDP (Train Real-Time Data Protocol), and TSN (Time-Sensitive Networking) technologies. It displays video data using the RTSP protocol and communicates with devices in the PIS network via TCP / UDP protocols. Qt parses and processes the received data, handling multi-source heterogeneous data. Based on the corresponding control numbers sent from the front end, it pushes the data processing results back to the front end. For example, when the status data of a train door changes, the real-time data communication module receives the new data and updates the color and status of the door status control on the page using JavaScript, ensuring the interface remains synchronized with the train's real-time status. This real-time update not only ensures the system's timeliness but also enhances the user experience, allowing train operators to monitor the train's status in real time.

[0118] The control management module manages various controls on the display page. Controls can include buttons, status indicators, numeric boxes, charts, etc. Each control is associated with a specific variable (such as the status of a train door, temperature, pressure value, etc.) and updates its display content based on real-time data changes. When background data changes, the control management module automatically updates the display status of the corresponding controls based on the real-time data. For example, when the train door status in the data source updates to "closed," the control management module will automatically change the color of the door status control to black, indicating that the door is closed. In this way, the system can keep the interface synchronized with the actual train status, ensuring that operators receive the latest status information.

[0119] The style generation module is responsible for automatically generating corresponding CSS files based on the style information provided by the configuration module. This style information includes attributes such as the color, font, border, and size of controls. The style generation module converts these attributes into standard CSS code and embeds it into the HTML page. The advantage of the style generation module lies in its flexibility: users can dynamically adjust the styles of controls by modifying the configuration file, such as changing the font, color, size, and border, to fully meet the needs of different trains and carriages. In this way, the platform can not only quickly adapt to different display requirements, but also personalize the interface according to specific application scenarios.

[0120] The relationships between the modules are explained below:

[0121] The relationship between the configuration module and the page generation module: The configuration module collects user-inputted interface layout information through a graphical interface and saves this information as a JSON-formatted configuration file. The page generation module automatically generates HTML, JavaScript, and CSS files based on these configuration files. Both modules exchange data via JSON files to ensure that the generated page content matches the user's requirements.

[0122] The relationship between the real-time data communication module and the control management module: The real-time data communication module obtains real-time train data (such as door status, traction status, etc.) from the TCMS system via WebSocket or other communication technologies and transmits this data to the control management module. The control management module updates the display status of the corresponding controls based on the received data. For example, when the train door status data is 1 (indicating the door is closed), the control management module automatically updates the door status control color to black. The real-time data communication module and the control management module exchange data through a predefined interface to ensure real-time interface updates.

[0123] The relationship between the style generation module and the page generation module: The style generation module generates corresponding CSS style code based on the style information in the configuration file. The page generation module embeds this style code into the HTML page, ensuring that controls are displayed according to the user-defined styles. The style generation module and the page generation module share the configuration file to pass style information, ensuring the accuracy and consistency of the interface styles.

[0124] The method for obtaining the status of high-speed train equipment components provided in this invention can automatically generate display screen pages and controls, simplifying the development workflow. In specific implementation, users only need to perform simple interface configuration, and the platform can generate a high-speed train display screen interface that meets the requirements based on these configurations. The combination of the real-time data communication module and the control management module ensures real-time synchronous updates of data and interface, while the style generation module ensures personalized customization of display controls.

[0125] During implementation, developers do not need to write tedious front-end code; they can focus solely on configuration and data binding, greatly improving development efficiency and reducing the risk of errors. This allows the platform to quickly adapt to different display needs, meeting the display requirements of different carriages and devices on high-speed trains, and providing a flexible foundation for subsequent functional expansion.

[0126] The method for obtaining the parameter status of EMU equipment components provided in this embodiment of the invention has the following beneficial technical effects:

[0127] 1. Significantly improve development efficiency:

[0128] This invention significantly improves development efficiency through a low-code development approach. Traditional display development typically requires developers to manually write large amounts of complex interface layout and data interaction code. However, using the low-code platform of this invention, developers only need to configure the system through a graphical interface or configuration files, and the system will automatically generate the corresponding pages and controls based on the configuration. This not only reduces the amount of coding and shortens the development cycle, but also significantly improves work efficiency, especially when developing multiple pages and multiple controls. The platform can automatically generate page structures and control layouts, avoiding the tedious process of manually writing large amounts of code, allowing developers to focus on business logic and interface customization, and quickly implement complex interfaces and functions.

[0129] 2. Reduce error rate and improve maintainability:

[0130] Traditional manual coding is prone to human error, especially in complex interface layouts and data interactions. By adopting a low-code platform, all configurations are managed in a file-based manner, eliminating the need for developers to manually manipulate interface elements and significantly reducing human error. All interface and control configuration information is centralized in a JSON file, greatly improving system maintainability. Developers only need to modify the configuration file, without needing to modify large amounts of source code, which greatly simplifies the maintenance and expansion process. The platform's maintainability advantage is particularly prominent when facing complex requirements such as multiple carriages, multiple trains, and multiple status displays; any updates or changes can be easily implemented by adjusting the configuration file, reducing direct modifications to the source code.

[0131] 3. Real-time data synchronization with the interface enhances data interaction capabilities:

[0132] High-speed rail displays need to show real-time train status data to ensure accuracy and timeliness. This platform enables real-time data interaction between the front-end and back-end. It supports real-time communication with the train's TCMS system, receiving and displaying various train status data in real time. Using WebSocket technology, front-end and back-end data can be seamlessly connected, ensuring real-time synchronization between the interface data and the back-end system. The platform guarantees that relevant display content is updated immediately when data changes, ensuring the timeliness, accuracy, and consistency of information. This efficient data interaction mechanism allows the displays to accurately show the train's current status and promptly reflect various status changes, providing accurate real-time data support for maintenance personnel and staff.

[0133] 4. Flexible personalization:

[0134] The low-code platform of this invention boasts powerful customization capabilities, allowing for flexible customization of the display interface based on the equipment configuration requirements of different trains and carriages. Through the platform's configuration module, developers can freely define the page layout, control positions, control styles, and other attributes of the display screen. Furthermore, the platform supports dynamically generating matching code, enabling personalized configuration according to the needs of different carriages and trains. Developers can quickly adjust the arrangement and display methods of interface elements to meet diverse display requirements. This flexible customization function allows the platform to quickly adapt to the needs of different customers and scenarios, further enhancing the adaptability and flexibility of the high-speed rail display system.

[0135] 5. Reduce development difficulty and adapt to the needs of intelligent high-speed rail:

[0136] As the intelligence level of high-speed rail continues to increase, the complexity of display screen styles, interactions, and data presentations is also growing. Traditional development models struggle to respond quickly to these rapidly changing demands. This invention's low-code platform easily implements complex interface displays through configuration files, supports dynamic updates across different states, significantly reduces development difficulty, and improves developer efficiency and creative freedom. Developers only need to focus on data interaction and interface layout, without delving into the underlying code, thus reducing their workload. With the rapid development of intelligent high-speed rail requirements, this platform can quickly adapt to changing needs and can be flexibly expanded according to new requirements.

[0137] 6. Supports management and updates of multiple pages and controls:

[0138] This platform supports not only the configuration and management of a single page but also the simultaneous configuration of multiple pages. Each page can contain multiple controls, and the display content, style, and position of these controls can be dynamically changed according to requirements. In high-speed rail displays, the number of pages and controls is enormous, and their states change frequently, making efficient management and updates difficult using traditional development methods. However, with this platform, the configuration and management of all controls are centralized in a unified configuration file. The platform can automatically update the states of multiple controls, ensuring the timely display of different state information on the screen. Through real-time data interaction, the platform can update the content of multiple pages and controls in real time, ensuring accurate information transmission and improving the management efficiency of large-scale multi-page, multi-control applications.

[0139] 7. Significantly improves the scalability of the interface:

[0140] This invention defines page content, control styles, and data interaction methods through JSON configuration files, offering strong scalability. For any new page or control requirements, developers only need to modify the configuration file to implement it, without rewriting the interface and data interaction code. This allows the platform to easily expand, supporting various new interface and control types to meet ever-changing needs. Furthermore, the platform supports real-time data updates, enabling flexible functional expansion without modifying existing code. New functional modules or controls can be quickly deployed through simple configuration and integration, significantly improving the system's scalability and flexibility.

[0141] 8. Optimize maintenance costs:

[0142] With a low-code platform, all controls, pages, and styles are centrally managed through configuration files, and data communication and display logic are implemented through standardized interfaces, making system maintenance much simpler. In traditional development models, modifying the display style or function of a control often requires modifying a large amount of source code and performing tedious testing. However, in a low-code platform, updating the style or function of controls can be done simply by modifying configuration files, eliminating the tedious steps of manually modifying code. Through standardized interfaces and centralized configuration management, the platform significantly reduces maintenance complexity, enabling easy updates and optimizations while ensuring system stability, thus significantly improving system maintainability and long-term operational efficiency.

[0143] The method for obtaining the status of EMU equipment component parameters provided in this embodiment of the invention responds to user-triggered interface editing operations and generates a configuration file; generates an interface file that can represent the control structure, layout, and appearance style according to the configuration file; utilizes the pre-established communication connection relationship between EMU equipment component parameters and controls, and updates the control display status in the interface file according to the real-time change information of EMU equipment component parameter data. By using the configuration file, a large amount of code can be avoided. By automatically generating an interface file that can represent the control structure, layout, and appearance style, the method can flexibly and autonomously realize the user's personalized design needs, thereby efficiently and intuitively displaying the status of EMU equipment component parameters.

[0144] Furthermore, the step of generating a configuration file in response to a user-triggered interface editing action includes:

[0145] The interface-related configuration information is obtained in response to the user's editing operation triggered by the interface editor; the above embodiments can be referred to for explanation, and will not be repeated here.

[0146] In response to a user's variable editing action triggered by the variable editor, variable association configuration information is obtained; this can be referred to the above embodiment for explanation, and will not be repeated here.

[0147] The configuration file is generated based on the interface association configuration information and the variable association configuration information. This can be referred to the above embodiments for further explanation, and will not be repeated here.

[0148] Furthermore, the process of responding to user editing actions triggered by the interface editor to obtain interface-related configuration information includes:

[0149] In response to the user's action of building a system structure tree triggered by the interface editor, the basic attributes of the interface and the category planning interface are obtained; the above embodiments can be referred to for explanation, and will not be repeated here.

[0150] The system responds to the user's action of configuring jump logic on the classification planning interface, realizes the association between various related interfaces, and determines the target related interface from the related interfaces; the above embodiments can be referred to for explanation, and will not be repeated here.

[0151] In response to the user's configuration action on the target associated interface based on the interface editor, the interface association configuration information is obtained. This can be described with reference to the above embodiments and will not be repeated here.

[0152] Furthermore, the method for obtaining the parameter status of the EMU equipment components also includes:

[0153] In response to user actions that configure interface elements based on the interface editor, the system obtains interface association configuration information containing basic element attributes, interaction attributes, and text attributes. This can be referred to the above embodiments for further explanation and will not be repeated here.

[0154] Furthermore, the response to the user's variable editing action triggered by the variable editor to obtain variable association configuration information includes:

[0155] In response to user actions triggering variable mapping and variable protocol configuration based on the variable editor, the variable association configuration information is obtained. This can be described with reference to the above embodiments and will not be repeated here.

[0156] Furthermore, the step of generating an interface file representing the control structure, layout, and appearance style based on the configuration file includes:

[0157] An appearance style file is generated based on the style attributes in the basic interface properties; this can be referred to the above embodiments for explanation, and will not be repeated here.

[0158] The configuration file is parsed to generate the original interface file; the original interface file contains the control structure and layout information; please refer to the above embodiments for further explanation, and will not be repeated here.

[0159] The appearance style file is embedded into the original interface file to obtain the interface file. This can be referred to the above embodiments for explanation, and will not be repeated here.

[0160] Figure 6 This is a schematic diagram of the structure of a device for acquiring the parameter status of EMU equipment components according to an embodiment of the present invention, as shown below. Figure 6 As shown, the device for acquiring the parameter status of EMU equipment components provided in this embodiment of the invention includes a first generation unit 601, a second generation unit 602, and an update unit 603, wherein:

[0161] The first generation unit 601 is used to generate a configuration file in response to the user-triggered interface editing operation; the second generation unit 602 is used to generate an interface file that can represent the control structure, layout and appearance style according to the configuration file; the update unit 603 is used to update the control display status in the interface file by utilizing the pre-established communication connection relationship between the EMU equipment component parameters and the controls, and according to the real-time change information of the EMU equipment component parameter data.

[0162] Specifically, the first generation unit 601 in the device is used to generate a configuration file in response to the user-triggered interface editing operation; the second generation unit 602 is used to generate an interface file that can represent the control structure, layout and appearance style according to the configuration file; the update unit 603 is used to update the control display status in the interface file by utilizing the pre-established communication connection relationship between the EMU equipment component parameters and the controls, and according to the real-time change information of the EMU equipment component parameter data.

[0163] The device for acquiring the status of EMU equipment component parameters provided in this embodiment of the invention responds to user-triggered interface editing operations and generates a configuration file; generates an interface file that can represent the structure, layout, and appearance of controls based on the configuration file; utilizes the pre-established communication connection relationship between EMU equipment component parameters and controls, and updates the display status of controls in the interface file according to the real-time change information of EMU equipment component parameter data. By using the configuration file, a large amount of code can be avoided. By automatically generating an interface file that can represent the structure, layout, and appearance of controls, the device can flexibly and autonomously realize the user's personalized design needs, thereby efficiently and intuitively displaying the status of EMU equipment component parameters.

[0164] The embodiments of the present invention provide a device for obtaining the status of parameters of components of EMU equipment, which can be used to execute the processing flow of the above method embodiments. Its function will not be repeated here, but can be referred to the detailed description of the above method embodiments.

[0165] Figure 7 This is a schematic diagram of the physical structure of a computer device provided in an embodiment of the present invention, such as... Figure 7 As shown, the computer device includes: a memory 701, a processor 702, and a computer program stored in the memory 701 and executable on the processor 702. When the processor 702 executes the computer program, it implements the following method:

[0166] Respond to user-triggered UI editing actions and generate configuration files;

[0167] Generate an interface file that represents the control structure, layout, and appearance style based on the configuration file;

[0168] The communication connection between the pre-established parameters of the EMU equipment components and the controls is utilized, and the display status of the controls in the interface file is updated according to the real-time changes in the EMU equipment component parameter data.

[0169] This embodiment discloses a computer program product, which includes a computer program that, when executed by a processor, implements the following method:

[0170] Respond to user-triggered UI editing actions and generate configuration files;

[0171] Generate an interface file that represents the control structure, layout, and appearance style based on the configuration file;

[0172] The communication connection between the pre-established parameters of the EMU equipment components and the controls is utilized, and the display status of the controls in the interface file is updated according to the real-time changes in the EMU equipment component parameter data.

[0173] This embodiment provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the following method:

[0174] Respond to user-triggered UI editing actions and generate configuration files;

[0175] Generate an interface file that represents the control structure, layout, and appearance style based on the configuration file;

[0176] The communication connection between the pre-established parameters of the EMU equipment components and the controls is utilized, and the display status of the controls in the interface file is updated according to the real-time changes in the EMU equipment component parameter data.

[0177] Compared with existing technical solutions, the method for obtaining the status of EMU equipment components provided in this invention responds to user-triggered interface editing operations and generates a configuration file; generates an interface file representing the control structure, layout, and appearance based on the configuration file; utilizes pre-established communication connections between EMU equipment component parameters and controls, and updates the control display status in the interface file according to real-time changes in EMU equipment component parameter data. By using the configuration file, a large amount of code can be avoided. Through the automatic generation of an interface file representing the control structure, layout, and appearance, the method can flexibly and autonomously realize personalized user design needs, thereby efficiently and intuitively displaying the status of EMU equipment component parameters.

[0178] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0179] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0180] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0181] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0182] In the description of this specification, references to terms such as "an embodiment," "a specific embodiment," "some embodiments," "for example," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0183] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for obtaining the parameter status of components in a high-speed train, characterized in that, include: Respond to user-triggered UI editing actions and generate configuration files; Generate an interface file that represents the control structure, layout, and appearance style based on the configuration file; The communication connection between the pre-established parameters of the EMU equipment components and the controls is utilized, and the display status of the controls in the interface file is updated according to the real-time changes in the EMU equipment component parameter data.

2. The method for obtaining the parameter status of EMU equipment components according to claim 1, characterized in that, The process of generating a configuration file in response to user-triggered interface editing actions includes: Respond to user editing actions triggered by the interface editor to obtain interface-related configuration information; Respond to user actions that trigger variable editing based on the variable editor, and obtain variable association configuration information; The configuration file is generated based on the interface association configuration information and the variable association configuration information.

3. The method for obtaining the parameter status of EMU equipment components according to claim 2, characterized in that, The response to user editing actions triggered by the interface editor yields interface-related configuration information, including: Responding to the user's action of building a system structure tree triggered by the interface editor, the basic attributes of the interface and the categorized planning interface are obtained; Responding to the user's action of configuring jump logic on the classification planning interface, the association between various related interfaces is realized, and the target related interface is determined from the related interfaces; In response to the user's configuration action on the target associated interface based on the interface editor, the associated interface configuration information is obtained.

4. The method for obtaining the parameter status of EMU equipment components according to claim 3, characterized in that, The method for obtaining the parameter status of the EMU equipment components also includes: Responding to user actions that configure interface elements based on the interface editor, obtain interface association configuration information containing basic element attributes, interaction attributes, and text attributes.

5. The method for obtaining the parameter status of EMU equipment components according to claim 2, characterized in that, The response to a user's variable editing action triggered by the variable editor yields variable association configuration information, including: In response to user actions triggered by the variable editor to configure variable mapping and variable protocol, the variable association configuration information is obtained.

6. The method for obtaining the parameter status of EMU equipment components according to claim 3, characterized in that, The step of generating an interface file that represents the control structure, layout, and appearance style according to the configuration file includes: Generate an appearance style file based on the style attributes in the basic interface attributes; The configuration file is parsed to generate the original interface file; the original interface file contains the control structure and layout information. The appearance style file is embedded into the original interface file to obtain the interface file.

7. A device for acquiring the parameter status of components in a high-speed train, characterized in that, include: The first generation unit is used to generate configuration files in response to user-triggered interface editing actions. The second generation unit is used to generate an interface file that can represent the control structure, layout and appearance style according to the configuration file; The update unit is used to update the display status of the controls in the interface file by utilizing the pre-established communication connection relationship between the EMU equipment component parameters and the controls, and according to the real-time change information of the EMU equipment component parameter data.

8. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 6.

Images