Vehicle-mounted software upgrading method in rail transit vehicle and related device

Abstract

The invention discloses a method for upgrading vehicle-mounted software in a rail transit vehicle and a related device, and relates to the technical field of rail transit. The method comprises the following steps: presetting a corresponding relationship among a compartment number, a vehicle-mounted equipment number and a vehicle-mounted equipment communication address; a corresponding relation among a compartment number, a vehicle-mounted equipment number and a storage address is preset. If the multiple pieces of vehicle-mounted equipment need to be uniformly updated, target vehicle-mounted equipment numbers corresponding to the multiple to-be-updated target compartment numbers respectively can be obtained; searching a target vehicle-mounted equipment communication address corresponding to the target compartment number and the target vehicle-mounted equipment number from the corresponding relation; searching a target storage address corresponding to the target compartment number and the target vehicle-mounted equipment number from the corresponding relationship; and controlling to display a vehicle-mounted software list corresponding to the target storage address. The user can determine a target version number from the vehicle-mounted software list; therefore, the purpose of uniformly sending the vehicle-mounted software corresponding to the target version number in the target storage address to the communication address of the target vehicle-mounted equipment is achieved.

Description

Technical Field

[0001] The present application relates to the field of rail transit technology, and in particular to a method and related device for upgrading on-board software in a rail transit vehicle. Background Art

[0002] With the continuous development of rail transit technology and the increasing number of rail transit vehicles, the demand for upgrading the onboard software in rail transit vehicles is increasing. A rail transit vehicle consists of multiple carriages, each of which has one or more onboard devices, each of which has corresponding onboard software.

[0003] In the related art, the on-board software upgrade method of multiple on-board devices in a rail transit vehicle usually relies on manual operation to upgrade one by one, which not only fails to meet the needs of real-time updates, but also fails to effectively guarantee the quality and efficiency of the on-board software upgrade. Summary of the Invention

[0004] In view of the above problems, this application provides a method and related device for upgrading on-board software in rail transit vehicles to achieve the purpose of uniformly upgrading on-board software in on-board devices. The specific solution is as follows:

[0005] A first aspect of the present application provides a method for upgrading on-board software in a rail transit vehicle, comprising:

[0006] Obtaining a software upgrade activation message, wherein the software upgrade activation message includes target vehicle-mounted device numbers corresponding to a plurality of target vehicle compartment numbers;

[0007] From the preset correspondence between the carriage number, the on-board device number and the on-board device communication address, searching for the target on-board device communication address corresponding to the target carriage number and the target on-board device number;

[0008] If the SU board successfully establishes a communication connection with the target vehicle-mounted device communication address, the target storage address corresponding to the target vehicle-mounted device number and the target vehicle-mounted device number is searched from the preset correspondence between the vehicle-mounted device number and the storage address;

[0009] Controlling display of an in-vehicle software list including a version number of the in-vehicle software stored at the target storage address;

[0010] In response to an operation of determining a target version number from the in-vehicle software list, the in-vehicle software corresponding to the target version number in the target storage address is sent to the target in-vehicle device communication address.

[0011] In a possible implementation, the method further includes:

[0012] Obtaining the upgrade progress of the vehicle software corresponding to the target version number;

[0013] Controls display of said upgrade progress.

[0014] In a possible implementation, the method further includes:

[0015] Acquire a software storage message, wherein the software storage message includes the target carriage number, the target vehicle-mounted device number corresponding to the target carriage number, and the vehicle-mounted software to be stored corresponding to the target vehicle-mounted device number;

[0016] From the preset correspondence between the carriage number, the vehicle-mounted device number and the storage address, searching for the target storage address corresponding to the target carriage number and the target vehicle-mounted device number;

[0017] The vehicle-mounted software to be stored is stored in the target storage address.

[0018] In a possible implementation, the method further includes:

[0019] The in-vehicle software list corresponding to the target in-vehicle communication address is updated.

[0020] In a possible implementation, the target storage address includes a target temporary address and a target software package address, and storing the vehicle-mounted software to be stored in the target storage address includes:

[0021] Storing the vehicle-mounted software to be stored in the target temporary address;

[0022] If the vehicle-mounted software to be stored passes the verification, the vehicle-mounted software to be stored is stored from the target temporary address to the target software package address.

[0023] In a possible implementation, the method further includes:

[0024] If the SU board fails to successfully establish a communication connection with the target vehicle-mounted device communication address within a preset time period, a prompt message indicating that the vehicle-mounted software upgrade has failed is displayed.

[0025] A second aspect of the present application provides an on-board software upgrade device for a rail transit vehicle, comprising:

[0026] A first acquisition module is configured to acquire a software upgrade activation message, wherein the software upgrade activation message includes target vehicle-mounted device numbers corresponding to a plurality of target vehicle compartment numbers;

[0027] A first search module is used to search for the target vehicle-mounted device communication address corresponding to the target vehicle-mounted device number and the target vehicle-mounted device number from the preset correspondence relationship between the vehicle-mounted device number, the vehicle-mounted device number and the vehicle-mounted device communication address;

[0028] The second search module is used to search for the target storage address corresponding to the target carriage number and the target on-board device number from the preset correspondence relationship between the carriage number, the on-board device number and the storage address if the SU board successfully establishes a communication connection with the target on-board device communication address;

[0029] a first control display module, configured to control the display of an in-vehicle software list including a version number of the in-vehicle software stored at the target storage address;

[0030] The sending module is used to respond to the operation of determining the target version number from the vehicle-mounted software list and send the vehicle-mounted software corresponding to the target version number in the target storage address to the target vehicle-mounted device communication address.

[0031] The third aspect of the present application provides a computer program product, including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the method for upgrading on-board software in a rail transit vehicle according to the first aspect or any implementation of the first aspect.

[0032] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:

[0033] The memory is used to store computer programs;

[0034] The processor is used to execute the computer program so that the electronic device can implement the method for upgrading on-board software in a rail transit vehicle according to the first aspect or any implementation of the first aspect.

[0035] In a fifth aspect, the present application provides a computer storage medium carrying one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement the method for upgrading on-board software in a rail transit vehicle according to the first aspect or any implementation of the first aspect.

[0036] By means of the above technical solution, the present application provides a method for upgrading on-board software in a rail transit vehicle, presetting the correspondence between the car number, the on-board device number and the on-board device communication address; presetting the correspondence between the car number, the on-board device number and the storage address, wherein the storage address is the storage address of the storage space located in the SU board. The on-board software is stored in the storage space of the SU board. If it is necessary to uniformly update multiple on-board devices, a software upgrade activation message can be obtained, and the software upgrade activation message includes target on-board device numbers corresponding to multiple target car numbers; from the preset correspondence between the car number, the on-board device number and the on-board device communication address, the target car number and the target on-board device communication address corresponding to the target on-board device number are searched; if a communication connection is successfully established with the target on-board device communication address, the target car number and the target on-board device number corresponding to the target storage address are searched from the preset correspondence between the car number, the on-board device number and the storage address; and the on-board software list containing the version number of the on-board software stored at the target storage address is controlled and displayed. This allows users to identify the target version number from the vehicle software list, thereby achieving the goal of sending the vehicle software corresponding to the target version number in the target storage address to the target vehicle device communication address. This eliminates the need for manual upgrade operations for multiple vehicle devices one by one. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale.

[0038] Figure 1 A schematic diagram of the system architecture provided for this application;

[0039] Figure 2 This is a schematic diagram of an optional hardware structure of an in-vehicle device 100 provided in this application;

[0040] Figure 3 A schematic diagram of a flow chart of a method for upgrading on-board software in a rail transit vehicle provided in an embodiment of the present application;

[0041] Figure 4 A schematic diagram of the correspondence between the carriage number, the on-board device number, and the storage address provided in an embodiment of the present application;

[0042] Figure 5 A schematic structural diagram of an on-board software upgrade device for a rail transit vehicle provided in an embodiment of the present application;

[0043] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] The following describes the embodiments of the present application in conjunction with the accompanying drawings. The terms used in the implementation methods of the present application are only used to explain the specific embodiments of the present application and are not intended to limit the present application.

[0045] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0046] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, and this is merely a way of distinguishing the objects of the same attributes when describing them in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0047] See also Figure 1 , Figure 1 A schematic diagram of a system architecture is shown. The system may include onboard equipment 100 deployed in a carriage, an SU (Software Upgrade) board 200, a communication network deployed in a rail transit vehicle, and a human-computer interaction device 300. It is understood that a rail transit vehicle includes multiple carriages, each of which is equipped with one or more onboard equipment 100; and a rail transit vehicle is equipped with an SU board 200.

[0048] It is understandable that the communication network deployed in the rail transit vehicle is used to connect the SU board 200 and the on-board equipment 100 deployed in different carriages.

[0049] The human-machine interaction device 300 may be an HMI (Human-Machine Interface), and the SU board 200 may be interacted with via the human-machine interaction device 300 .

[0050] Exemplarily, the on-board equipment includes but is not limited to: PIS (Passenger Information System), SMS (Safety Monitoring System), DCU (Door Control Unit), PIS (Passenger Information System), WTD (Wireless Transmission Device), traction system, auxiliary system, and air conditioning system.

[0051] For example, the SU board 200 can obtain the vehicle software to be upgraded from the hard disk or server, and then send it to multiple vehicle devices, thereby achieving a unified upgrade of multiple vehicle devices. There is no need for manual upgrading of the vehicle software of the vehicle devices in different compartments one by one.

[0052] Next describe Figure 1 The product form of the vehicle-mounted device 100;

[0053] The vehicle-mounted device 100 in the embodiment of the present application can be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc., and the embodiment of the present application does not impose any restrictions on this.

[0054] Figure 2 A schematic diagram of an optional hardware structure of the vehicle-mounted device 100 is shown.

[0055] refer to Figure 2 As shown, the vehicle-mounted device 100 may include a radio frequency unit 110, a memory 120, an input unit 130, a display unit 140, a camera 150 (optional), an audio circuit 160 (optional), a speaker 161 (optional), a microphone 162 (optional), an earphone jack 163 (optional), a processor 170, an external interface 180, a power supply 190 and other components. Those skilled in the art will understand that Figure 2 The foregoing is merely an example of an in-vehicle device and does not constitute a limitation on the in-vehicle device. The foregoing may include more or fewer components than shown in the figure, or may combine certain components, or may include different components.

[0056] The input unit 130 can be used to receive input digital or character information and generate key signal input related to user settings and function control of the vehicle-mounted device. Specifically, the input unit 130 may include a touch screen 131 (optional) and / or other input devices 132. The touch screen 131 can detect user touch operations on or near it (for example, operations performed on or near the touch screen using a finger, joint, stylus, or any other suitable object) and drive corresponding connected devices according to pre-set programs. The touch screen can detect user touch actions on the touch screen, convert the touch actions into touch signals and transmit them to the processor 170. It can also receive and execute commands sent by the processor 170; the touch signals include at least touch point coordinate information. The touch screen 131 can provide an input interface and an output interface between the vehicle-mounted device 100 and the user. In addition, touch screens can be implemented using various types, such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch screen 131, the input unit 130 may also include other input devices. Specifically, the other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, a joystick, and the like.

[0057] Among them, the input device 132 can receive input data and the like.

[0058] The display unit 140 can be used to display information input by the user or information provided to the user, various menus of the vehicle-mounted device 100, interactive interfaces, file display and / or playback of any multimedia file. In the embodiment of the present application, the display unit 140 can be used to display interfaces, processing results, etc.

[0059] Memory 120 can be used to store instructions and data. It primarily includes an instruction storage area and a data storage area. The data storage area can store various data, such as multimedia files and text. The instruction storage area can store software units such as the operating system, applications, and instructions required for at least one function, or subsets or extensions thereof. It may also include non-volatile random access memory (RAM). It provides processor 170 with management functions for the hardware, software, and data resources within the computing and processing device, supporting control software and applications. It is also used to store multimedia files and running programs and applications.

[0060] The processor 170 is the control center of the in-vehicle device 100. It connects the various components of the in-vehicle device 100 using various interfaces and circuits. By executing instructions stored in the memory 120 and accessing data stored in the memory 120, it performs various functions of the in-vehicle device 100 and processes data, thereby providing overall control of the in-vehicle device. Optionally, the processor 170 may include one or more processing units. Preferably, the processor 170 may integrate an application processor and a modem processor, with the application processor primarily handling the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into the processor 170. In some embodiments, the processor and memory may be implemented on a single chip; in other embodiments, they may be implemented on separate chips. The processor 170 may also generate corresponding operational control signals and send them to the corresponding components of the computing and processing device. It may also read and process data in the software, particularly the data and programs in the memory 120, to enable the various functional modules therein to perform their corresponding functions, thereby controlling the corresponding components to operate as instructed.

[0061] Among them, the memory 120 can be used to store software codes related to the vehicle-mounted software, the processor 170 can execute the steps of the method corresponding to the vehicle-mounted software, and can also dispatch other units (such as the above-mentioned input unit 130 and display unit 140) to implement corresponding functions.

[0062] The RF unit 110 (optional) can be used to send and receive information or receive and send signals during a call. For example, after receiving downlink information from the base station, it is sent to the processor 170 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (LNA), a duplexer, etc. In addition, the RF unit 110 can also communicate with network devices and other devices via wireless communication. This wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile Communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.

[0063] In this embodiment of the present application, the radio frequency unit 110 can send data to the server 200 and receive processing results sent by the server 200.

[0064] It should be understood that the radio frequency unit 110 is optional and can be replaced by other communication interfaces, such as a network port.

[0065] The vehicle-mounted device 100 also includes a power supply 190 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 170 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0066] The vehicle-mounted device 100 further includes an external interface 180 , which may be a standard Micro USB interface or a multi-pin connector, and may be used to connect the vehicle-mounted device 100 to other devices for communication, or to connect a charger to charge the vehicle-mounted device 100 .

[0067] Although not shown, the vehicle-mounted device 100 may also include a flashlight, a wireless fidelity (WiFi) module, a Bluetooth module, sensors with different functions, etc., which will not be described in detail here. Some or all of the methods described below can be applied to Figure 2 In the vehicle-mounted device 100 shown.

[0068] It should be understood that the above-mentioned vehicle-mounted device 100 can be a centralized or distributed device, and the processor in the above-mentioned vehicle-mounted device 100 can be a hardware circuit (such as an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), a microprocessor or a microcontroller, etc.), or a combination of these hardware circuits. For example, the processor can be a hardware system with an instruction execution function, such as a CPU, DSP, etc., or a hardware system without an instruction execution function, such as an ASIC, FPGA, etc., or a combination of the above-mentioned hardware systems without an instruction execution function and hardware systems with an instruction execution function.

[0069] Rail transit is experiencing rapid development, with the number of vehicles continuously increasing. However, in related technologies, onboard software updates for onboard equipment rely on after-sales personnel for each device to manually update the equipment on board. This not only presents numerous drawbacks but also hides management loopholes. High costs and lengthy upgrade cycles are particularly problematic when faced with the need to upgrade a large number of onboard devices. Related technology upgrade solutions not only fail to meet the demand for real-time updates, but also fail to effectively guarantee the quality and efficiency of onboard software upgrades. This situation increases the risk of serious operational failures after onboard software upgrades, posing a threat to the stable operation of rail transportation.

[0070] With today's information technology, a centralized one-click upgrade method for on-board software in rail transit vehicles can effectively prevent after-sales personnel from upgrading privately, incorrectly, or missing software, reduce the manpower and material resources consumed in on-board software updates, and reduce the difficulty of scheduling existing vehicles. Accordingly, research on a centralized one-click update design for on-board software has become a key focus of on-board software updates. The on-board software upgrade method for rail transit vehicles provided in this application can centrally control the upgrade of on-board software in a single on-board device or multiple on-board devices as needed, effectively shortening the time it takes to upgrade the system one by one.

[0071] Reference Figure 3 , Figure 3 A flow chart of a method for upgrading on-board software in a rail transit vehicle provided in an embodiment of the present application is shown as follows: Figure 3 As shown, an embodiment of the present application provides a method for upgrading on-board software in a rail transit vehicle, which may include steps S301 to S305. The method is applied to the SU board, and these steps are described in detail below.

[0072] Step S301: Obtain a software upgrade activation message, wherein the software upgrade activation message includes target vehicle-mounted device numbers corresponding to a plurality of target carriage numbers.

[0073] For example, a software upgrade activation message can be set via the human-computer interaction device 300. For example, the human-computer interaction device 300 can display a user interface that displays multiple car numbers and corresponding vehicle-mounted device numbers. A user can select one or more target car numbers from the multiple car numbers through the user interface, and then select one or more target vehicle-mounted device numbers from the multiple vehicle-mounted device numbers corresponding to each target car number. This can then result in a software upgrade activation message.

[0074] For example, the user can log in to the human-computer interaction device 300. For example, the user can log in to the human-computer interaction device 300 using a user name and password. The SU board stores a preset correspondence between the user name and password, thereby detecting whether the user can log in successfully. The user who logs in successfully can perform the upgrade operation.

[0075] Step S302: searching for the target vehicle-mounted device communication address corresponding to the target vehicle-mounted device number and the target vehicle-mounted device number from the preset correspondence relationship between the vehicle-mounted device number, the vehicle-mounted device number and the vehicle-mounted device communication address.

[0076] It is understood that a rail transit vehicle includes multiple carriages, each of which is equipped with one or more onboard devices; each carriage has a unique carriage number, each onboard device has a unique onboard device number, and each onboard device has a unique onboard device communication address.

[0077] The correspondence between the carriage number, the on-board device number and the on-board device communication address can be preset, and the on-board device communication address can be uniquely determined by the carriage number and the on-board device number.

[0078] Exemplarily, the vehicle-mounted device communication address is the communication address of the vehicle-mounted device. Exemplarily, the vehicle-mounted device communication address includes: an IP (Internet Protocol, Internet Protocol address) address and a MAC (Media Access Control, Media Access Control) address.

[0079] Step S303: If the SU board successfully establishes a communication connection with the target vehicle-mounted device communication address, the target storage address corresponding to the target vehicle-mounted device number and the target vehicle-mounted device number is searched from the preset correspondence between the vehicle-mounted device number, vehicle-mounted device number and storage address.

[0080] Exemplarily, the storage address is a storage address corresponding to a storage space in a memory in the SU board.

[0081] Exemplarily, if the SU board fails to successfully establish a communication connection with the target vehicle-mounted device communication address within a preset time period, a prompt message indicating that the vehicle-mounted software upgrade has failed is displayed.

[0082] Exemplarily, the preset duration may be determined based on actual conditions and is not limited here. For example, the preset duration is 30 seconds.

[0083] It is understood that after receiving the software upgrade activation message, the SU board will establish a communication connection with the onboard device with the target onboard device communication address. If the communication connection is not successfully established within the preset time, it may indicate the following problems: the onboard device with the target onboard device communication address is faulty; the communication protocol between the onboard device with the target onboard device communication address and the SU board may be mismatched or incorrect; the software upgrade activation message received by the SU board may contain an incorrect target onboard device communication address, resulting in an inability to find the correct onboard device for communication; the onboard device with the target onboard device communication address may reject the SU board's communication request due to permission settings issues. Therefore, a prompt message can be displayed on the human-computer interaction device.

[0084] For example, a prompt message "Software upgrade service activation failed" is displayed on the human-computer interaction device to inform the operator that the upgrade cannot continue. For example, the prompt message may include the specific cause of the error (such as "communication timeout" or "device not responding") to facilitate the operator's investigation.

[0085] Exemplarily, the target storage address stores vehicle-mounted software for upgrading the vehicle-mounted device having the target vehicle-mounted device communication address.

[0086] Exemplarily, the number of target carriage numbers may be one or more; the number of target vehicle-mounted device numbers may be one or more.

[0087] Exemplarily, the number of vehicle-mounted software stored in the storage space having the same storage address may be one or more, wherein different vehicle-mounted software have different versions.

[0088] It is understandable that each vehicle-mounted device corresponds to one storage address; however, one storage address may correspond to one or more vehicle-mounted devices.

[0089] Step S304: controlling the display of an in-vehicle software list including the version number of the in-vehicle software stored at the target storage address.

[0090] It can be understood that the number of vehicle-mounted software stored in the storage space of the same storage address can be one or more, wherein different vehicle-mounted software have different versions, and each storage address corresponds to a vehicle-mounted software list, which includes the version number of each vehicle-mounted software.

[0091] Step S305: In response to the operation of determining the target version number from the vehicle-mounted software list, the vehicle-mounted software corresponding to the target version number in the target storage address is sent to the target vehicle-mounted device communication address.

[0092] Exemplarily, before the SU board sends the in-vehicle software to the communication address of the target in-vehicle device, it may also send a version upgrade instruction to the communication address of the target in-vehicle device.

[0093] Exemplarily, the controller in the vehicle-mounted device having the communication address of the target vehicle-mounted device may update the vehicle-mounted software after receiving the vehicle-mounted software.

[0094] For example, the SU board can communicate with the vehicle-mounted device using either FTP (File Transfer Protocol) or UDP (User Datagram Protocol). FTP is based on TCP (Transmission Control Protocol), ensuring the integrity and reliability of file transfers. UDP is a connectionless protocol that does not require complex error checking and confirmation mechanisms, resulting in fast transmission speeds and low latency.

[0095] For example, the SU board can use the FTP protocol or the UDP protocol when communicating with the human-computer interaction device.

[0096] The combination of FTP and UDP leverages their respective strengths. FTP is used for file transfer, ensuring the integrity and reliability of software packages; UDP is used for real-time communication, ensuring the rapid transmission of commands and status information during the upgrade process. This protocol combination is compatible with a wide range of in-vehicle devices. The broad compatibility of FTP and UDP ensures smooth transfer of in-vehicle software across a wide range of devices.

[0097] Exemplarily, the in-vehicle device having the target in-vehicle device communication address may actively obtain the in-vehicle software corresponding to the target version number from the target storage address.

[0098] Exemplarily, the SU board may proactively send the vehicle-mounted software corresponding to the target version number to the vehicle-mounted device having the target vehicle-mounted device communication address.

[0099] Exemplarily, after receiving the vehicle-mounted software, the vehicle-mounted device having the target vehicle-mounted device communication address may be upgraded immediately or after a designated upgrade time has been reached.

[0100] The embodiment of the present application provides a method for upgrading on-board software in a rail transit vehicle, presetting the correspondence between the car number, the on-board device number and the on-board device communication address; presetting the correspondence between the car number, the on-board device number and the storage address, wherein the storage address is the storage address of the storage space located in the SU board. The on-board software is stored in the storage space of the SU board. If multiple on-board devices need to be updated uniformly, a software upgrade activation message can be obtained, and the software upgrade activation message includes target on-board device numbers corresponding to multiple target car numbers; from the preset correspondence between the car number, the on-board device number and the on-board device communication address, the target car number and the target on-board device communication address corresponding to the target on-board device number are searched; if a communication connection is successfully established with the target on-board device communication address, the target car number and the target on-board device number corresponding to the target storage address are searched from the preset correspondence between the car number, the on-board device number and the storage address; and the on-board software list containing the version number of the on-board software stored at the target storage address is controlled and displayed. This allows users to identify the target version number from the vehicle software list, thereby achieving the goal of sending the vehicle software corresponding to the target version number in the target storage address to the target vehicle device communication address. This eliminates the need for manual upgrade operations for multiple vehicle devices one by one.

[0101] In an optional implementation, the above technical solution may further include the following method, which includes the following steps A1 to A2.

[0102] Step A1: Obtain the upgrade progress of the vehicle software corresponding to the target version number.

[0103] For example, if the SU board does not receive the upgrade progress of the vehicle software within a set period of time, it is determined that the upgrade has failed, and a prompt message indicating the upgrade failure is displayed.

[0104] It is understandable that if the SU board does not receive the upgrade progress of the on-board software within the set time, the following problems may exist: the communication link between the SU board and the on-board device may be interrupted due to hardware failure (such as cable damage, loose interface) or network problems (such as signal interference, network congestion); excessive network latency may cause the upgrade progress information to fail to reach the SU board within the set time; data packet loss in the network may cause the SU board to be unable to receive complete upgrade progress information; the on-board software on the on-board device may crash or freeze due to software errors, compatibility issues or insufficient resources; the current version of the on-board software of the on-board device may be incompatible with the upgrade package, resulting in the upgrade program failing to execute normally; the storage space of the on-board device may be insufficient to complete the download or installation of the on-board software.

[0105] Exemplarily, the set duration may be determined based on actual conditions and is not limited here. For example, the set duration may be 10 seconds.

[0106] For example, the vehicle-mounted device can feed back the upgrade progress to the SU board in real time or at regular intervals.

[0107] Step A2: Control and display the upgrade progress.

[0108] For example, after the vehicle software of the vehicle device is successfully upgraded, that is, after the upgrade reaches 100%, related operations such as restart can be performed, and the upgrade progress can be pushed to the SU board. The SU board controls the human-computer interaction device to display the upgrade progress.

[0109] For example, the restart operation for the vehicle-mounted device may be an automatic restart or a manual restart.

[0110] For example, the vehicle-mounted device can send a prompt of whether to restart to the SU board, and the SU board controls the human-computer interaction device to display the prompt information. If the user clicks "Confirm restart", the SU board will send the restart instruction to the vehicle-mounted device, so that the vehicle-mounted device will restart; if the user clicks "Prohibit restart", the SU board will send the prohibit restart instruction to the vehicle-mounted device, so that the vehicle-mounted device will not restart.

[0111] For example, after the vehicle software is updated, the software update service can be closed through the human-computer interaction device.

[0112] In an optional implementation, the above technical solution may further include the following method, which includes the following steps B1 to B3.

[0113] Step B1: Acquire a software storage message, wherein the software storage message includes the target car number, the target vehicle-mounted device number corresponding to the target car number, and the vehicle-mounted software to be stored corresponding to the target vehicle-mounted device number.

[0114] Exemplarily, the vehicle-mounted software to be stored may be obtained from a hard disk or from a server.

[0115] For example, the user can set the software to store the message through the user interface displayed by the human-computer interaction device. For example, the user interface can display multiple car numbers and multiple vehicle-mounted device numbers for the user to select.

[0116] Step B2: searching for the target storage address corresponding to the target car number and the target onboard device number from the preset correspondence between the car number, the onboard device number and the storage address.

[0117] Step B3: storing the vehicle-mounted software to be stored in the target storage address.

[0118] This achieves the purpose of storing the vehicle-mounted software in the corresponding storage address of the SU board.

[0119] Exemplarily, since the amount of vehicle-mounted software stored in the storage space corresponding to the target storage address increases, the vehicle-mounted software list corresponding to the target vehicle-mounted communication address needs to be updated.

[0120] Exemplarily, each vehicle-mounted device uses a dedicated PTU (Portable Test Unit) and a designated FTP account to upload the encrypted vehicle-mounted software to be updated to the corresponding storage path. Exemplarily, during the vehicle-mounted software upgrade process, the PTU serves as the vehicle-mounted software upload tool and is connected to the vehicle-mounted device's network interface (e.g., Ethernet port or USB port).

[0121] For example, each in-vehicle device may be equipped with a dedicated PTU to ensure compatibility between the in-vehicle device and the in-vehicle software.

[0122] Exemplarily, the permission of each vehicle-mounted device is only to access the corresponding storage address divided by the SU board, that is, the vehicle-mounted device can access the storage address with the corresponding relationship in step S303.

[0123] For example, the PTU, as a vehicle software upload tool, can transfer the vehicle software to a temporary storage address (folder) assigned by default to the vehicle device. The temporary storage address is then saved to the corresponding software package address. After the vehicle device is restarted, the vehicle software in the temporary storage address is automatically deleted.

[0124] In an optional implementation, the target storage address includes a target temporary address and a target software package address, and the step of storing the vehicle-mounted software to be stored in the target storage address includes the following steps C1 to C2.

[0125] Step C1: storing the vehicle-mounted software to be stored in the target temporary address.

[0126] Step C2: If the vehicle-mounted software to be stored passes the verification, the vehicle-mounted software to be stored is stored from the target temporary address to the target software package address.

[0127] It is understandable that before storing the vehicle-mounted software to the target software package address, the vehicle-mounted software is first stored to the target temporary address. The purpose of this is to verify the vehicle-mounted software stored at the target temporary address. If the verification passes, step C2 is executed.

[0128] Exemplarily, the verification process includes but is not limited to: checking whether the size of the in-vehicle software is consistent with expectations; calculating the checksum of the in-vehicle software (such as MD5 checksum, SHA-256 checksum, SM3 checksum), and comparing it with the checksum during uploading; ensuring that the uploading and storage process of the in-vehicle software complies with the system's security policy.

[0129] In order to help those skilled in the art better understand the above-mentioned "correspondence between carriage number, on-board device number and storage address", and the relationship between the temporary address and the software package address, the following examples are given to illustrate.

[0130] like Figure 4 As shown, it is a schematic diagram of the relationship between the "correspondence between the carriage number, the on-board equipment number and the storage address" provided in the embodiment of the present application, the temporary address and the software package address.

[0131] Assume that the vehicle-mounted equipment includes: safety detection system SMS, door system DCU and other vehicle-mounted equipment. Then the "correspondence between car number, vehicle-mounted equipment number and storage address", temporary address and software package address can be used Figure 4 The directory structure representation in .

[0132] The following examples illustrate temporary addresses and software package addresses. Figure 4 As shown, the temporary address of the vehicle software "SMS_SW_V01.01.zip" is "Directory / Temporary Folder / Car Number 1 / SMS". The software package address of the vehicle software "SMS_SW_V01.01.zip" is "Directory / Software Package Storage Folder / Car Number 1 / SMS".

[0133] Figure 4 Where N is any positive integer greater than 1. M and P are any positive integers greater than or equal to 1.

[0134] For example, the present application sets up a file directory structure, such as Figure 4As shown, the SU board automatically performs encryption verification on the vehicle software uploaded to the temporary folder. Once the verification passes, the vehicle software is backed up to the software package storage folder. The software package storage folder stores all versions of the vehicle software corresponding to each vehicle device. Files in the software package storage folder can be deleted with superuser privileges. In principle, the contents stored in the software package storage folder will not be deleted or modified, ensuring the isolation of updated vehicle software versions.

[0135] The present invention provides a method for upgrading onboard software in a rail transit vehicle. First, the onboard device must have a data storage medium, such as a memory, for storing and backing up the onboard software. The onboard device may include naming format requirements for the onboard software. The onboard software may include a compressed software upgrade package and a verification information file for the compressed software upgrade package.

[0136] For example, the vehicle-mounted devices also have specific requirements for the vehicle software distribution, upgrade, and rollback mechanisms. The controller of each vehicle-mounted device or the SU board mentioned in this application can obtain the vehicle software via FTP or UDP; the SU board can distribute it to the vehicle-mounted device via FTP, UDP, or other methods.

[0137] Exemplarily, the vehicle-mounted device board may carry an operating system, in which case an independent management process must be designed for the vehicle-mounted device board; exemplary, the vehicle-mounted device board may not carry an operating system, in which case a hardware watchdog function and a boot program must be designed for the vehicle-mounted device board to execute the startup of the application and the reception of the vehicle-mounted software.

[0138] A hardware watchdog function is a hardware mechanism used to monitor and manage the operating status of in-vehicle equipment boards to prevent them from becoming locked or unable to recover due to software failures or anomalies. It typically consists of a timer and related circuitry, automatically triggering a reboot or other recovery actions when an in-vehicle equipment board experiences an anomaly.

[0139] The bootloader is the first software program that runs when an in-vehicle device board starts up. Its primary function is to initialize the hardware environment, load the operating system or application, and start it running. The bootloader is responsible for completing the initial steps of the in-vehicle device board startup.

[0140] For example, in the embodiment of the present application, after receiving the on-board software, the on-board device can automatically control the software upgrade operation, read its own software version in real time, and automatically check whether the version is updated successfully or failed after the upgrade is completed. When the on-board software update fails, it can automatically roll back according to the backed-up historical version of the on-board software. If the on-board device board starts abnormally due to the on-board software upgrade, the on-board device needs to be designed to restore the software version with the configuration of the last normal startup, and feedback the actual software version. In summary, the version control and fault isolation and other related measures of the on-board software protect the relevant functions of the upgrade process, support the old version fallback mechanism when the on-board software upgrade fails, and ensure the availability of the on-board software.

[0141] For example, this application focuses on designing a communication protocol framework for the present invention, providing both standard (FTP) and non-standard (UDP) file transfer methods for different vehicle-mounted devices. The vehicle-mounted device and the human-computer interaction device, as well as the instructions and messages between the vehicle-mounted devices, use the UDP communication protocol for communication, while the vehicle-mounted software between the vehicle-mounted devices uses the FTP communication protocol for communication.

[0142] In summary, for different message and file types, a unified interaction protocol and upgrade strategy are built to be compatible with different operating systems and hardware formats and implemented uniformly to solve compatibility issues.

[0143] In summary, the method for upgrading onboard software in rail transit vehicles, provided by the embodiments of this application, has been designed to address the four key challenges of centralized, one-click upgrades of onboard software in rail transit vehicles: compatibility, security, efficiency, and usability. This application, in accordance with the plan, enables one-click upgrades of key devices, such as onboard equipment, in rail transit vehicles. Through methods such as permission allocation, onboard software version management, and interactive software upgrades, users are provided with intuitive, multi-dimensional software upgrade management, including historical versions, current versions, and upgraded versions.

[0144] In summary, compared with the related art, the advantages of this application are:

[0145] This application allows you to directly update the in-vehicle software in all in-vehicle devices with just one click, effectively avoiding issues such as suppliers privately upgrading in-vehicle software, incorrect upgrades, missed upgrades, and difficulties in coordinating with existing vehicles, thereby improving upgrade efficiency.

[0146] To meet the requirements of this application, the SU board has been designed with corresponding vehicle software storage rules. The storage location and storage name of the vehicle software are specified in a corresponding format. This effectively implements vehicle software version control and facilitates providing customers with an intuitive historical version.

[0147] Design vehicle-mounted software with encrypted digests, transmit them to the SU board via wired mode using a dedicated PTU, and perform national secret algorithm verification to ensure system security.

[0148] A communication protocol framework was designed based on the communication logic to specify the communication process and the scope of the two file transfer methods, UDP and FTP. Based on the communication protocol framework proposed in this application and combined with the vehicle software distribution strategy, it can effectively accommodate upgrade tasks between various system components.

[0149] Based on the unified upgrade method of the two interactive protocols and three types of protection measures contained in this application, after actual application testing on prototype vehicles, it was confirmed that this application can effectively ensure the high efficiency, high security, high compatibility and high availability of one-click upgrades of vehicle-mounted software.

[0150] The above describes a method for upgrading on-board software in a rail transit vehicle provided by an embodiment of the present application. The following describes a device for executing the above-mentioned method for upgrading on-board software in a rail transit vehicle.

[0151] See also Figure 5 , Figure 5 This is a schematic diagram of the structure of a vehicle-mounted software upgrade device in a rail transit vehicle provided by an embodiment of the present application. Figure 5 As shown, the on-board software upgrade device in the rail transit vehicle includes:

[0152] The first acquisition module 501 is used to acquire a software upgrade activation message, wherein the software upgrade activation message includes target vehicle-mounted device numbers corresponding to multiple target carriage numbers respectively;

[0153] The first search module 502 is used to search for the target vehicle-mounted device communication address corresponding to the target vehicle-mounted device number and the target vehicle-mounted device number from the preset correspondence relationship between the vehicle-mounted device number, the vehicle-mounted device number and the vehicle-mounted device communication address;

[0154] The second search module 503 is used to search for the target storage address corresponding to the target car number and the target on-board device number from the preset correspondence relationship between the car number, the on-board device number and the storage address if the SU board successfully establishes a communication connection with the target on-board device communication address;

[0155] A first control display module 504, configured to control the display of an in-vehicle software list including the version number of the in-vehicle software stored at the target storage address;

[0156] The sending module 505 is configured to respond to the operation of determining the target version number from the vehicle-mounted software list and send the vehicle-mounted software corresponding to the target version number in the target storage address to the target vehicle-mounted device communication address.

[0157] In an optional implementation, the method further includes:

[0158] A second acquisition module is used to obtain the upgrade progress of the vehicle software corresponding to the target version number;

[0159] The second control and display module is used to control and display the upgrade progress.

[0160] In an optional implementation, the method further includes:

[0161] A third acquisition module is used to acquire a software storage message, wherein the software storage message includes the target car number, the target vehicle-mounted device number corresponding to the target car number, and the vehicle-mounted software to be stored corresponding to the target vehicle-mounted device number;

[0162] A third search module is used to search for the target storage address corresponding to the target carriage number and the target on-board device number from the preset correspondence relationship between the carriage number, the on-board device number and the storage address;

[0163] A storage module is used to store the vehicle-mounted software to be stored in the target storage address.

[0164] In an optional implementation, the method further includes:

[0165] An updating module is used to update the vehicle-mounted software list corresponding to the target vehicle-mounted communication address.

[0166] In an optional implementation, the target storage address includes a target temporary address and a target software package address, and the storage module includes:

[0167] a first storage unit, configured to store the vehicle-mounted software to be stored in the target temporary address;

[0168] The second storage unit is configured to store the vehicle-mounted software to be stored from the target temporary address to the target software package address if the vehicle-mounted software to be stored passes verification.

[0169] In an optional implementation, the method further includes:

[0170] The third control display module is used to control the display of a prompt message indicating that the vehicle software upgrade has failed if the SU board fails to successfully establish a communication connection with the target vehicle device communication address within a preset time period.

[0171] An electronic device is also provided in an embodiment of the present application. Figure 6, which shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present application. The electronic device in the embodiments of the present application may include, but is not limited to, fixed vehicle-mounted devices such as mobile phones, laptops, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. Figure 6 The electronic device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0172] like Figure 6 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. When the electronic device is powered on, the RAM 603 also stores various programs and data required for the operation of the electronic device. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0173] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a memory card, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although Figure 6 The electronic device is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0174] An embodiment of the present application also provides a computer program product including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements any of the on-board software upgrade methods for rail transit vehicles provided in the embodiments of the present application.

[0175] A computer-readable storage medium is also provided in an embodiment of the present application. The storage medium carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any of the on-board software upgrade methods in rail transit vehicles provided in the embodiments of the present application.

[0176] It should also be noted that the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, in the drawings of the device embodiments provided in this application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.

[0177] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course can also be implemented by special hardware including application-specific integrated circuits, special CPUs, special memories, special components, etc. In general, all functions performed by computer programs can be easily implemented with corresponding hardware, and the specific hardware structures used to implement the same function can also be diverse, such as analog circuits, digital circuits or special circuits, etc. However, for the present application, software program implementation is a better implementation method in most cases. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer's floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., and includes a number of instructions to enable a computer device (which can be a personal computer, training equipment, or network equipment, etc.) to execute the methods described in each embodiment of the present application.

[0178] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0179] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, a computer, a training device or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website, a computer, a training device or a data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

Claims

1. A method for upgrading onboard software in a rail transit vehicle, characterized in that: Applicable to SU boards, including: Obtaining a software upgrade activation message, wherein the software upgrade activation message includes target vehicle-mounted device numbers corresponding to a plurality of target vehicle compartment numbers; From the preset correspondence between the carriage number, the on-board device number and the on-board device communication address, searching for the target on-board device communication address corresponding to the target carriage number and the target on-board device number; If the SU board successfully establishes a communication connection with the target vehicle-mounted device communication address, the target storage address corresponding to the target vehicle-mounted device number and the target vehicle-mounted device number is searched from the preset correspondence between the vehicle-mounted device number and the storage address; Controlling display of an in-vehicle software list including a version number of the in-vehicle software stored at the target storage address; In response to an operation of determining a target version number from the in-vehicle software list, the in-vehicle software corresponding to the target version number in the target storage address is sent to the target in-vehicle device communication address.

2. The method for upgrading on-board software in a rail transit vehicle according to claim 1, characterized in that: Also includes: Obtaining the upgrade progress of the vehicle software corresponding to the target version number; Controls display of said upgrade progress.

3. The method for upgrading on-board software in a rail transit vehicle according to claim 1, characterized in that: Also includes: Acquire a software storage message, wherein the software storage message includes the target carriage number, the target vehicle-mounted device number corresponding to the target carriage number, and the vehicle-mounted software to be stored corresponding to the target vehicle-mounted device number; From the preset correspondence between the carriage number, the vehicle-mounted device number and the storage address, searching for the target storage address corresponding to the target carriage number and the target vehicle-mounted device number; The vehicle-mounted software to be stored is stored in the target storage address.

4. The method for upgrading on-board software in a rail transit vehicle according to claim 3, characterized in that: Also includes: The in-vehicle software list corresponding to the target in-vehicle communication address is updated.

5. The method for upgrading on-board software in a rail transit vehicle according to claim 3, characterized in that: The target storage address includes a target temporary address and a target software package address, and storing the vehicle-mounted software to be stored in the target storage address includes: Storing the vehicle-mounted software to be stored in the target temporary address; If the vehicle-mounted software to be stored passes the verification, the vehicle-mounted software to be stored is stored from the target temporary address to the target software package address.

6. The method for upgrading on-board software in a rail transit vehicle according to any one of claims 1 to 5, characterized in that: Also includes: If the SU board fails to successfully establish a communication connection with the target vehicle-mounted device communication address within a preset time period, a prompt message indicating that the vehicle-mounted software upgrade has failed is displayed.

7. A vehicle-mounted software upgrade device in a rail transit vehicle, characterized in that: include: A first acquisition module is configured to acquire a software upgrade activation message, wherein the software upgrade activation message includes target vehicle-mounted device numbers corresponding to a plurality of target vehicle compartment numbers; A first search module is used to search for the target vehicle-mounted device communication address corresponding to the target vehicle-mounted device number and the target vehicle-mounted device number from the preset correspondence relationship between the vehicle-mounted device number, the vehicle-mounted device number and the vehicle-mounted device communication address; The second search module is used to search for the target storage address corresponding to the target carriage number and the target on-board device number from the preset correspondence relationship between the carriage number, the on-board device number and the storage address if the SU board successfully establishes a communication connection with the target on-board device communication address; a first control display module, configured to control the display of an in-vehicle software list including a version number of the in-vehicle software stored at the target storage address; The sending module is used to respond to the operation of determining the target version number from the vehicle-mounted software list and send the vehicle-mounted software corresponding to the target version number in the target storage address to the target vehicle-mounted device communication address.

8. A computer program product, characterized in that The method comprises computer-readable instructions, which, when executed on an electronic device, enable the electronic device to implement the method for upgrading on-board software in a rail transit vehicle as claimed in any one of claims 1 to 6.

9. An electronic device, characterized in that: comprising at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program so that the electronic device can implement the on-board software upgrading method in a rail transit vehicle as described in any one of claims 1 to 6.

10. A computer storage medium, characterized in that The storage medium carries one or more computer programs, which, when executed by an electronic device, enable the electronic device to implement the method for upgrading on-board software in a rail transit vehicle as described in any one of claims 1 to 6.

Images