Vehicle terminal wireless debugging method and device, computer device and storage medium

Abstract

The present application belongs to the field of vehicle-mounted, and relates to a wireless debugging method and device for a vehicle-mounted terminal, computer equipment and a storage medium. The method comprises the following steps: obtaining SSH source code, integrating an executable program generated from the SSH source code into the vehicle-mounted terminal; authorizing and configuring the running and closing of the SSH executable program; authorizing the vehicle-mounted terminal to run the SSH executable program; opening a vehicle terminal hotspot of the vehicle-mounted terminal; debugging the vehicle-mounted terminal through an external electronic device connected to the vehicle terminal via the vehicle terminal hotspot; and when the debugging is completed, authorizing the vehicle-mounted terminal to stop running the SSH executable program. The method improves the debugging efficiency, enhances the system security, simplifies the operation process, and ensures the stable operation of the vehicle-mounted terminal. The embedded software can be wirelessly connected and debugged during the debugging stage to facilitate problem troubleshooting and effective encryption protection. Even when the upgrade cannot be realized after the sale, the terminal can be wirelessly entered at any time for upgrade, and the customer does not need to wait for a long time.

Description

Technical Field

[0001] This invention relates to the field of vehicle technology, and in particular to a wireless debugging method, apparatus, computer equipment, and storage medium for vehicle terminals. Background Technology

[0002] Using diagnostic equipment developed by the car manufacturer to access the terminal device via a wired connection, although it is not necessary to remove the terminal device for debugging, its debugging and access functions are limited (it can only perform read and write operations on the defined development content, and cannot fully access the terminal settings).

[0003] If an external party needs to check the internal operation of the terminal device every time, the terminal device must be disassembled and the problem investigated by directly connecting to the terminal hardware debugging interface. Otherwise, it is impossible to find out the specific cause of the problem and to solve it remotely on-site.

[0004] The path to access the terminal device via the diagnostic tool is: command input device (computer) -> diagnostic tool -> CAN or Ethernet -> terminal device.

[0005] The main drawbacks of existing technical solutions are: they rely entirely on the functions already defined and implemented on the terminal device, and can only be accessed by reading and writing through a diagnostic tool, which cannot troubleshoot other problems with the terminal device; they cannot access the terminal device wirelessly and securely, and if unexpected problems occur in the vehicle, they cannot analyze the problem remotely, but can only retrieve the terminal device for troubleshooting, resulting in high maintenance costs for the terminal device in the later stages. Summary of the Invention

[0006] To address the aforementioned technical problems, this invention provides a wireless debugging method for vehicle-mounted terminals, employing the following technical solution:

[0007] Obtain the SSH source code and integrate the executable program generated from the SSH source code into the vehicle terminal;

[0008] Configure permissions for running and shutting down SSH executables;

[0009] The vehicle-mounted terminal is authorized to run an SSH executable program;

[0010] Turn on the vehicle-mounted terminal's hotspot;

[0011] The vehicle terminal is debugged by connecting to an external electronic device that passes through the vehicle hotspot and is connected to the vehicle terminal.

[0012] Once debugging is complete, authorize the vehicle terminal to stop running the SSH executable program.

[0013] Preferably, the step of obtaining the SSH source code and integrating the executable program generated from the SSH source code into the vehicle terminal specifically includes:

[0014] Select the SSH version based on the hardware and software environment of the vehicle terminal;

[0015] Download the SSH source package according to the selected SSH version;

[0016] Extract the downloaded SSH source code package to the specified directory of the vehicle terminal;

[0017] Compile the SSH source code into an executable program;

[0018] The SSH executable program is integrated into the vehicle terminal.

[0019] Preferably, the step of configuring authorization for the running and shutting down of the SSH executable specifically includes:

[0020] Configure user or group permissions for the SSH executable file;

[0021] Configure the system log service to record SSH service startup and shutdown events.

[0022] Preferably, the step of authorizing the vehicle-mounted terminal to run the SSH executable program specifically includes:

[0023] Obtain the IP address of the vehicle terminal;

[0024] Using the SSH client on the debugging device, connect to the vehicle terminal via IP address with the authorized and configured permissions;

[0025] After successfully connecting to the vehicle terminal, the SSH executable program is authorized to run.

[0026] Preferably, the step of turning on the vehicle-mounted terminal's hotspot specifically includes:

[0027] Enable the Wi-Fi hotspot function of the vehicle terminal;

[0028] Set the network name and password for the vehicle terminal;

[0029] Save the network name and password of the vehicle terminal and select "Applicable".

[0030] Preferably, the step of debugging the vehicle terminal via an external electronic device connected to the vehicle terminal through the vehicle hotspot specifically includes:

[0031] Turn on the WiFi function of the external electronic device, search for and connect to the vehicle hotspot of the vehicle terminal;

[0032] Obtain the IP address of the vehicle terminal;

[0033] Establish communication with the vehicle-mounted terminal;

[0034] Send debugging instructions to the vehicle-mounted terminal;

[0035] Receive the response returned by the vehicle terminal and parse it;

[0036] Record debugging commands and response results.

[0037] Preferably, the step of authorizing the vehicle terminal to stop running the SSH executable program after debugging is completed specifically includes:

[0038] Verify debugging permissions to ensure you have permission to stop the SSH executable.

[0039] In the vehicle-mounted terminal, locate the running information and process of the SSH executable program;

[0040] Send a stop command to the SSH executable;

[0041] Confirm that the SSH executable has stopped running;

[0042] The operation of stopping the SSH executable program is recorded in the system log and the log information is saved.

[0043] To address the aforementioned technical problems, the present invention also provides a vehicle-mounted terminal wireless debugging device, which employs the following technical solution, including:

[0044] An integration module is used to obtain SSH source code and integrate the executable program generated from the SSH source code into the vehicle terminal.

[0045] The configuration module is used to configure the authorization for running and shutting down SSH executables;

[0046] The authorization module is used to authorize the vehicle terminal to run SSH executable programs;

[0047] The module is opened to enable the vehicle-mounted terminal's hotspot.

[0048] The debugging module is used to debug the vehicle terminal via an external electronic device connected to the vehicle terminal through the vehicle hotspot;

[0049] The Stop Authorization module is used to authorize the vehicle terminal to stop running the SSH executable program when debugging is complete.

[0050] To address the aforementioned technical problems, the present invention also provides a computer device that employs the technical solution described below, comprising a memory and a processor. The memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the steps of the aforementioned vehicle-mounted terminal wireless debugging method.

[0051] To address the aforementioned technical problems, the present invention also provides a computer-readable storage medium, which employs the technical solution described below. The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the aforementioned vehicle-mounted terminal wireless debugging method.

[0052] Compared with existing technologies, the present invention has the following main advantages: it improves debugging efficiency, enhances system security, simplifies operation procedures, and ensures the stable operation of the vehicle terminal; it allows for wireless connection debugging of embedded software during the debugging phase, facilitating problem diagnosis and providing effective encryption protection; it also provides a convenient debugging method for after-sales rework and software troubleshooting, making it easier for after-sales personnel to analyze problems; embedded software often requires wireless troubleshooting or upgrades, and during the debugging phase before vehicle launch, upgrades can be performed on-site or remotely without relying on a server backend, requiring only a computer; even if after-sales service encounters server failure or diagnostic tools are unable to perform upgrades, wireless access to the terminal can be used for upgrades at any time, eliminating the need for customers to wait for extended periods. Attached Figure Description

[0053] To more clearly illustrate the solutions in this invention, the accompanying drawings used in the description of the embodiments of this invention will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0054] Figure 1 This is a flowchart of an embodiment of the vehicle-mounted terminal wireless debugging method of the present invention;

[0055] Figure 2 This is a schematic diagram of the structure of an embodiment of the vehicle-mounted terminal wireless debugging device of the present invention;

[0056] Figure 3 This is a schematic diagram of the structure of an embodiment of the computer device of the present invention. Detailed Implementation

[0057] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains; the terminology used herein in the specification is for the purpose of describing particular embodiments only and is not intended to limit the invention; the terms "comprising" and "having," and any variations thereof, in the specification, claims, and foregoing drawings are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the specification, claims, or foregoing drawings are used to distinguish different objects and not to describe a particular order.

[0058] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0059] To enable those skilled in the art to better understand the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings.

[0060] It should be noted that the vehicle-mounted terminal wireless debugging method provided in the embodiments of the present invention is generally executed by a server / terminal device, and correspondingly, the vehicle-mounted terminal wireless debugging device is generally set in the server / terminal device.

[0061] It should be understood that the number of terminal devices, networks, and servers is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be used.

[0062] SSH (Secure Shell) is a network protocol primarily used for securely transmitting data over insecure networks. Its full name is Secure Shell, meaning "secure shell protocol," and it ensures the confidentiality and integrity of data transmission by creating an encrypted tunnel within the network.

[0063] SSH is primarily used for remote login, remote command execution, file transfer, and port forwarding. For example, system administrators and developers often use the SSH protocol to remotely log in to servers to perform administrative tasks or development operations. SSH also supports the secure file transfer protocol (SFTP), allowing users to securely transfer files between local and remote computers.

[0064] The main advantage of SSH lies in the security it provides. It uses public and private keys for authentication, offering a higher level of security compared to traditional usernames and passwords. SSH also employs advanced encryption algorithms, such as symmetric encryption algorithms (like AES) and asymmetric encryption algorithms (like RSA), effectively preventing data from being eavesdropped on or tampered with during transmission.

[0065] Furthermore, SSH offers flexibility and broad support. It supports various authentication methods, including passwords, public keys, and certificates, allowing users to choose the most suitable method based on their needs. Additionally, SSH is an open standard, supported by mainstream operating systems and network devices, making it a standard for cross-platform remote access.

[0066] SSH, as a secure and reliable remote access protocol, plays an important role in the field of network security, providing secure and efficient remote communication services for system administrators, developers, and other users.

[0067] In modern automotive development, wireless debugging of in-vehicle terminals has become an important means of ensuring the stability and functionality of vehicle systems. SSH (Secure Shell), as a secure network protocol, can be used for remote login and management.

[0068] Example 1

[0069] Please refer to Figure 1 The flowchart illustrates an embodiment of the vehicle-mounted terminal wireless debugging method of the present invention. The vehicle-mounted terminal wireless debugging method includes the following steps:

[0070] Step S1: Obtain the SSH source code and integrate the executable program generated from the SSH source code into the vehicle terminal.

[0071] In this embodiment, the electronic device (e.g., a server / terminal device) running on the vehicle-mounted terminal wireless debugging method can receive the vehicle-mounted terminal wireless debugging request via a wired or wireless connection. It should be noted that the aforementioned wireless connection methods may include, but are not limited to, 3G / 4G / 5G connections, WiFi connections, Bluetooth connections, WiMAXX connections, Zigbee connections, UWB (ultra-wideband) connections, and other currently known or future-developed wireless connection methods.

[0072] In this embodiment, step S1, obtaining the SSH source code and integrating the executable program generated from the SSH source code into the vehicle terminal, may further include the following steps:

[0073] S11. Select the SSH version based on the hardware and software environment of the vehicle terminal.

[0074] First, it's necessary to determine the hardware module composition of the vehicle-mounted terminal, including the main control chip, CAN communication module, 4G communication module, positioning module, local storage module, and power supply module. By disassembling and analyzing the vehicle-mounted terminal, its hardware architecture and selection can be determined. Then, the software development environment it uses can be identified.

[0075] SSH versions include OpenSSH, etc. Ensure that the selected version is compatible with the vehicle terminal's operating system and has the required functionalities.

[0076] S12, download the SSH source package according to the selected SSH version.

[0077] You can download the SSH source code package from the official or trusted source code repository. Ensure that the downloaded source code package is complete and has not been tampered with.

[0078] S13, extract the downloaded SSH source code package to the specified directory of the vehicle terminal.

[0079] For example, you can use command-line tools (such as the tar command) to extract the source package: `tar -xzf openssh-<version number>.tar.gz`. The extracted directory should contain the complete file structure of the SSH source code.

[0080] S14 compiles the SSH source code into an executable program.

[0081] First, install the compilation tools. Ensure the vehicle terminal has the necessary toolchain (such as gcc, make, etc.) for compiling SSH source code. Install the compilation tools using a package manager (such as apt-get, yum, etc.). For example: `sudo apt-get install build-essential`. Note that the compilation tools should be compatible with the vehicle terminal's operating system version.

[0082] Next, configure the compilation options. Based on the requirements of the vehicle terminal, configure the compilation options for the SSH source code. For example, navigate to the extracted SSH source code directory and run the `. / configure` script to configure the compilation options. For instance: `. / configure --prefix= / usr / local / ssh`. It should be noted that the configuration options can be adjusted according to actual needs, such as specifying the installation path, enabling or disabling specific functions, etc.

[0083] Next, compile the source code to create an executable program from the SSH source code. For example, run the `make` command to start compiling the source code.

[0084] Finally, install the executable program by installing the compiled executable to the specified directory. Run the `make install` command to install the executable program. For example: `sudo make install`. It should be noted that the installation path must match the configuration options, and the vehicle terminal must have the appropriate permissions.

[0085] S15, integrate the SSH executable into the vehicle terminal.

[0086] First, prepare the in-vehicle terminal environment, ensuring it has the necessary software and hardware to run the SSH service. Confirm the operating system version and hardware specifications of the in-vehicle terminal. Install necessary dependencies and tools (such as libssh, openssl, etc.). The in-vehicle terminal environment should be compatible with the requirements of the SSH service.

[0087] Next, configure the SSH service on the vehicle terminal for remote login and management. Create an SSH configuration file to set the parameters and options for the SSH service. For example, create or edit an SSH configuration file on the vehicle terminal (e.g., ` / etc / ssh / sshd_config`). Set parameters according to your needs, such as Port, PermitRootLogin, PasswordAuthentication, etc. Start the SSH service, making it listen on the specified port and wait for remote connections. Use a system service manager (such as systemd, init.d, etc.) to start the SSH service. For example: `sudo systemctl startsshd`. Ensure that the SSH service runs automatically when the vehicle terminal starts (this can be configured to start automatically on boot).

[0088] Next, test the SSH connection to verify that the SSH service is functioning correctly and to test the remote connection functionality. Obtain the IP address of the vehicle terminal to determine its location on the network for remote connection. Use command-line tools (such as ifconfig, ip addr, etc.) to view the IP address of the vehicle terminal. Ensure that the vehicle terminal is connected to the network and has permission to access the external network. Connect to the vehicle terminal using an SSH client (such as PuTTY, ssh command, etc.). Enter the vehicle terminal's IP address, username, and password in the SSH client. For example: `ssh username@vehicle terminal IP address`. Ensure that the entered username and password are correct and that the vehicle terminal is configured to allow remote login.

[0089] Finally, integrate SSH into the vehicle terminal system, making it a part of the system. Configure it to start automatically on boot, ensuring the SSH service runs automatically when the vehicle terminal starts. Use the system service manager to configure the SSH service to start automatically on boot. For example: `sudo systemctl enablesshd`. Configure firewall rules to allow the SSH service on port 22 (usually 22) through the vehicle terminal's firewall. Use firewall management tools (such as ufw, iptables, etc.) to configure the rules. For example: `sudo ufw allow22 / tcp`. Ensure that the firewall rules do not affect other network services on the vehicle terminal.

[0090] Step S2: Configure the authorization for running and shutting down the SSH executable.

[0091] In this embodiment, step S2, configuring the authorization for running and shutting down the SSH executable program, may further include the following steps:

[0092] S21, Configure user or group permissions for the SSH executable.

[0093] Use the `chmod` command to set the permissions of the SSH executable file, ensuring that only specific users or groups can execute the file. For example: `chmod 700 / usr / sbin / sshd` (assuming the SSH executable file is located at ` / usr / sbin / sshd`).

[0094] In Linux systems using SELinux, access to SSH executables can be restricted by configuring SELinux policies. For example, a specific context can be configured for the SSH service, restricting access to SSH executables to only processes with that context.

[0095] In Linux systems, the `sudo` command can be used to grant specific users root privileges to execute specific commands. By editing the ` / etc / sudoers` file (or using the `visudo` command), permissions can be added to specific users, allowing them to execute commands to start and stop the SSH service. For example: `sshuser ALL=(ALL)NOPASSWD: / usr / sbin / systemctl start sshd.service, / usr / sbin / systemctl stop sshd.service` (Note: In practice, the `NOPASSWD` option should be used with caution to prevent security risks).

[0096] S22, Configure the system log service to record the startup and shutdown events of the SSH service.

[0097] To ensure effective monitoring and auditing of the SSH service's operation and shutdown, system logging services (such as `syslog`, `journalctl`, etc.) can be configured to record SSH service startup and shutdown events. This helps in tracing and investigating security incidents.

[0098] Due to the confidentiality requirements of car manufacturers, the execution and termination of SSH executable programs require authorization. Among the optional implementations, authorization can be achieved in two ways: through diagnostic tool commands defined by the car manufacturer; or, for in-vehicle terminal devices with SIM cards, through specific SMS messages.

[0099] Authorizing SSH executable programs through manufacturer-defined diagnostic commands relies on communication between the diagnostic tool and the vehicle's ECU (Engine Control Unit). The manufacturer defines a set of diagnostic commands for interaction with the vehicle system. When authorization for an SSH executable program is required, technicians use the diagnostic tool to send commands to the ECU. These commands include the data frame header, total data length, command format, communication address, valid data length, and the actual data content. Upon receiving these commands, the ECU parses them and executes corresponding operations, such as granting SSH service permissions. This process must ensure the integrity and accuracy of the commands to avoid unnecessary interference or damage to the vehicle system.

[0100] For vehicle-mounted terminal devices with SIM cards, authorization for SSH executable programs can be achieved via a specific SMS message. This method relies on SMS communication technology and the SMS receiving and processing capabilities of the vehicle-mounted terminal device. An SMS receiving module is configured on the vehicle-mounted terminal device and associated with the SSH service. When authorization for an SSH executable program is required, the user or administrator sends an SMS message containing authorization information to the SIM card of the vehicle-mounted terminal device. Upon receiving this SMS message, the vehicle-mounted terminal device parses the message content and extracts the authorization information. If the authorization information is correct and conforms to preset rules, the vehicle-mounted terminal device will perform the corresponding operation, such as granting specific permissions to the SSH service. This method has advantages such as ease of operation and no need for physical contact with the vehicle system, making it particularly suitable for remote management and maintenance scenarios.

[0101] Step S3: Authorize the vehicle terminal to run the SSH executable program.

[0102] In this embodiment, step S3, authorizing the vehicle terminal to run the SSH executable program, may further include the following steps:

[0103] S31, Obtain the IP address of the vehicle terminal.

[0104] To connect to the vehicle terminal via SSH, you need to know its IP address. Typically, the vehicle terminal's IP address can be obtained from the vehicle management system or network configuration tools.

[0105] For example, log in to the vehicle management system using an administrator account. Locate the IP address and related information of the vehicle terminal within the vehicle management system. Then, record the IP address of the vehicle terminal for later use.

[0106] S32, using the SSH client on the debugging device, connects to the vehicle terminal via IP address with the authorized configured permissions.

[0107] Open the SSH client software on the testing device. Enter the IP address and port number of the vehicle terminal (default is 22) in the SSH client. Enter the username and password set on the vehicle terminal to authenticate. If the username and password are correct, the SSH client will successfully connect to the vehicle terminal and display a command-line prompt.

[0108] S33, after successfully connecting to the vehicle terminal, authorizes the execution of the SSH executable program.

[0109] At the command prompt of the vehicle terminal, check the current user's permissions. If the current user does not have permission to run SSH executables, you need to use the `chmod` command to modify the permissions of the SSH executable file. For example, you can use the command `chmod +x / path / to / ssh` to grant execute permissions to the current user for the file ` / path / to / ssh`. After modifying the permissions, check the current user's permissions again to ensure that authorization has been successfully granted.

[0110] Modifying system permission settings ensures the current user has permission to run SSH executables. Verifying permissions ensures the modification was successful and prevents problems in subsequent operations.

[0111] Step S4: Turn on the vehicle-mounted terminal's hotspot.

[0112] To enable the in-vehicle hotspot function, a SIM card that supports data traffic can be used to provide network connectivity. Ensure the SIM card is correctly installed and has a valid data plan.

[0113] A vehicle-mounted hotspot refers to turning an in-vehicle system into a Wi-Fi hotspot, allowing other devices (such as mobile phones, tablets, and laptops) to connect to the system via Wi-Fi, thereby enabling data transmission and sharing. The in-vehicle hotspot provides convenient network connectivity while driving, supporting various functions such as navigation, music playback, and video viewing, greatly enhancing the driving and passenger experience.

[0114] In this embodiment, step S4, turning on the vehicle terminal hotspot, may further include the following steps:

[0115] S41, enable the Wi-Fi hotspot function of the vehicle terminal.

[0116] Only after the Wi-Fi hotspot function is turned on can the vehicle system broadcast Wi-Fi signals to the outside world as a hotspot.

[0117] In the network settings menu, find the "Wi-Fi hotspot" or similar option and turn it on.

[0118] To efficiently enable the in-vehicle Wi-Fi hotspot function, command-line operation can be used instead of manual operation. First, access permissions must be obtained through the in-vehicle system's developer mode or debugging interface. Then, import the preset command, such as `enable_wifi_hotspot` (the specific command varies depending on the vehicle model and system), into the terminal or command-line interface. This command will automatically activate the Wi-Fi hotspot, and parameters such as SSID and password can be configured as needed. This process not only improves operational efficiency but also reduces the possibility of human error, ensuring that the in-vehicle Wi-Fi hotspot function starts quickly and accurately.

[0119] S42, Set the network name and password of the vehicle terminal.

[0120] The network name is a unique identifier for the in-vehicle Wi-Fi hotspot; other devices search for this name to connect. The password protects the in-vehicle Wi-Fi hotspot, preventing unauthorized devices from connecting. Pre-set network names and passwords for in-vehicle devices can be imported.

[0121] S43, save the network name and password of the vehicle terminal and select applicable.

[0122] To ensure efficient and secure network configuration for vehicle terminals, command-line tools can be used for automatic configuration of the network name (SSID) and password. Scripts can be written via the command line to automatically set up the wireless network, avoiding the tediousness and errors of manual input. For example, by accessing the command-line interface through a terminal, the corresponding network configuration commands can be imported, such as `nmcli` (NetworkManager command-line tool) or `wpa_supplicant` configuration files, specifying the SSID and password. This method not only improves configuration efficiency but also enhances configuration accuracy and security.

[0123] The in-vehicle Wi-Fi hotspot configuration will only take effect after you save the settings and select "Apply".

[0124] Step S5: Debug the vehicle terminal by connecting it to an external electronic device that passes through the vehicle hotspot and is connected to the vehicle terminal.

[0125] It should be noted that before performing wireless debugging of the vehicle terminal, you need to ensure that the vehicle terminal supports wireless debugging, has been configured with a network and has obtained the necessary permissions, and has selected the debugging tool.

[0126] Ensure the vehicle terminal supports wireless debugging, check if the vehicle terminal has a wireless communication module, and confirm that it supports the SSH protocol.

[0127] Configure the network to ensure that the vehicle terminal and debugging equipment (such as external electronic devices such as computers and mobile phones) are on the same network, or to achieve remote connection through technologies such as VPN.

[0128] Obtain the necessary permissions to ensure that the debugging equipment has the authority to access and modify the vehicle terminal configuration.

[0129] The selection of debugging tools includes, but is not limited to, SSH clients, network debugging tools, and terminal emulation software for vehicle terminals.

[0130] SSH clients, such as PuTTY and SecureCRT, are used to establish SSH connections between debugging devices and in-vehicle terminals.

[0131] Network debugging tools, such as Wireshark, are used to analyze network communication data of in-vehicle terminals.

[0132] Terminal emulation software, such as Minicom and Tera Term, is used to simulate serial communication and interact with the vehicle terminal.

[0133] In this embodiment, step S5, debugging the vehicle terminal via an external electronic device connected to the vehicle terminal through the vehicle hotspot, may further include the following steps:

[0134] Wireless debugging of in-vehicle terminals involves establishing a hotspot in the vehicle and connecting external electronic devices (such as laptops and smartphones) to the in-vehicle terminal to enable remote debugging. This debugging method not only improves debugging efficiency but also reduces debugging costs, making it particularly suitable for in-vehicle systems that require frequent updates and optimizations.

[0135] S51, turn on the WiFi function of the external electronic device, search for and connect to the vehicle terminal's hotspot.

[0136] In your laptop or smartphone settings, find and turn on the Wi-Fi option. Search for available Wi-Fi networks, locate and connect to the car's hotspot you just set up. When connecting to the car's hotspot, you will need to enter the hotspot password you set earlier. Ensure the password is correct for a successful connection. Once connected, external electronic devices will be able to access the internet through the car's hotspot. You can verify the connection by opening a webpage or using other online applications.

[0137] S52, obtain the IP address of the vehicle terminal.

[0138] In the vehicle terminal's settings interface, locate the network settings or status information option. Check the vehicle terminal's IP address to enable communication during the debugging process.

[0139] S53, establish communication with the vehicle terminal.

[0140] Using the debugging tool, establish a connection based on the vehicle terminal's IP address and port number. Ensure the connection parameters are correct to ensure successful communication with the vehicle terminal.

[0141] S54, send debugging instructions to the vehicle terminal.

[0142] The debugging tool sends debugging commands to the vehicle terminal. These commands include reading system parameters, modifying configurations, and executing specific functions.

[0143] S55, receive the response returned by the vehicle terminal and parse it.

[0144] After receiving the debugging command, the vehicle-mounted terminal will execute the corresponding operation and return a response. Debugging tools are used to receive and parse these responses to understand the operating status and debugging results of the vehicle-mounted terminal.

[0145] S56 records debugging commands and response results.

[0146] During the debugging process, debugging commands, response results, and related information should be recorded. This information is crucial for subsequent analysis and optimization of the vehicle-mounted terminal.

[0147] Step S6: Once debugging is complete, authorize the vehicle terminal to stop running the SSH executable program.

[0148] In this embodiment, step S6, when debugging is complete, authorizing the vehicle terminal to stop running the SSH executable program, may further include the following steps:

[0149] S61, verify debugging permissions, and ensure you have permission to stop the SSH executable.

[0150] Before remote debugging, technicians need to enter a username and password, or verify their debugging privileges through other authentication methods (such as digital certificates, biometrics, etc.). This verification information is typically stored in the database of the vehicle terminal management system or the remote debugging device. If the verification is successful, the technician is allowed access to the management system; if the verification fails, access is denied.

[0151] First, verify debugging permissions to prevent unauthorized personnel from performing illegal operations and ensure the security of the vehicle terminal.

[0152] S62, in the vehicle terminal, search for the running information and process of the SSH executable program.

[0153] Use the system's built-in Task Manager or command-line tools (such as ps, top, etc.) to find SSH-related processes. View system configuration files (such as / etc / ssh / sshd_config) to understand the SSH service configuration information. Use system logs (such as / var / log / auth.log, / var / log / secure, etc.) to view SSH connection records.

[0154] In the vehicle terminal management system, locate the running information and processes of the SSH executable program. The purpose of this is to understand the running status and related information of the SSH executable program, preparing for its eventual shutdown.

[0155] S63 sends a stop command to the SSH executable.

[0156] For example, use command-line tools (such as kill, systemctl stop, etc.) to terminate the SSH process. Alternatively, disable the SSH service in the management system so that it does not start automatically. When sending a stop command, ensure the command is correct and secure to avoid affecting other functions of the vehicle terminal.

[0157] After the management system sends a stop command to the SSH executable program, the vehicle terminal will perform the corresponding operation to stop the SSH executable program from running.

[0158] S64 confirms that the SSH executable has stopped running.

[0159] Use Task Manager or a command-line tool again to check if the SSH-related processes have disappeared. Check the system logs to confirm that there are no new SSH connection records. Verify the status of the SSH service to ensure that it has stopped running or has been disabled.

[0160] Verify that the SSH executable has stopped running in the management system. This can be done by checking the process list or system logs. Ensure the SSH executable has stopped successfully to avoid any unclosed SSH connections remaining after debugging.

[0161] S65 records the action of stopping the SSH executable in the system log and saves the log information.

[0162] Configure the management system to record operations in a specified log file or database. Regularly check the log file to ensure accuracy and completeness. If necessary, export the log file to other formats (such as CSV, PDF, etc.) for archiving or analysis.

[0163] The operation of stopping the SSH executable program is logged in the system log, and relevant log information is saved. This facilitates subsequent auditing and tracing, ensuring that the operation complies with specifications and security requirements.

[0164] Embedded systems generally refer to embedded systems, which are devices composed of hardware and software that can operate independently. The hardware component includes an Ethernet PHY, SIM card, memory, signal processor, communication module, etc., while the software component is a Linux operating system running on top of different CPU software environments.

[0165] Wireless debugging of in-vehicle terminals plays a crucial role in the development and debugging of new car models. It allows developers to debug functionalities without disassembling the corresponding terminal equipment, and effectively protects the terminal from unauthorized access, tampering, and hacking, meeting the safety requirements of car manufacturers. The main benefits are as follows:

[0166] (1) It can provide security protection.

[0167] Wireless access can be enabled or disabled using diagnostic equipment developed by the car manufacturer, effectively ensuring access when needed and preventing unauthorized access to the terminal and tampering with information.

[0168] (2) Facilitates debugging for developers

[0169] When a vehicle malfunctions, the terminal device can be accessed wirelessly without needing to be removed, facilitating troubleshooting.

[0170] (3) Devices can be connected via Ethernet.

[0171] The above operations can be performed by connecting the terminal devices of each vehicle via Ethernet.

[0172] The beneficial effects of implementing this embodiment are:

[0173] First, we obtained the SSH source code, compiled and linked it to generate an executable program suitable for the vehicle terminal, and seamlessly integrated it into the vehicle system. This ensured the nativeness and compatibility of the SSH tool, laying a solid foundation for subsequent debugging work.

[0174] Next, detailed configuration of the run and stop permissions of the SSH executable is performed to ensure that only authorized operations can start or stop the program, thereby effectively improving system security.

[0175] Subsequently, it was officially authorized to run the SSH executable program through the vehicle terminal, enabling the vehicle system to respond to SSH connection requests from external devices;

[0176] Enabling the vehicle hotspot function of the vehicle terminal provides a stable and reliable wireless network environment for external electronic devices, facilitating subsequent connection and debugging operations. By connecting to the vehicle hotspot, external electronic devices can establish communication with the vehicle terminal using the SSH protocol, thereby enabling in-depth debugging work. This method not only simplifies the debugging process but also greatly improves debugging efficiency.

[0177] Once the debugging task is completed, the vehicle terminal will stop running the SSH executable program and close unnecessary network ports in a timely manner through the corresponding authorized operation, further strengthening the system's security protection.

[0178] It improved debugging efficiency, enhanced system security, simplified operation procedures, and ensured the stable operation of the vehicle terminal;

[0179] It can facilitate troubleshooting by wirelessly connecting embedded software during the debugging phase, and provides effective encryption protection; at the same time, it also provides a convenient debugging method during after-sales rework and after-sales software troubleshooting, making it easier for after-sales personnel to analyze problems.

[0180] Embedded software often requires wireless troubleshooting or upgrades. When a vehicle is in the debugging phase before its market launch, there is no need to rely on a server backend for upgrades. Only a computer is needed to complete the on-site or remote control upgrades. Even if the after-sales service encounters server failures or diagnostic tools that cannot perform upgrades, upgrades can be performed wirelessly at any time without requiring customers to wait for a long time.

[0181] This invention can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This invention can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This invention can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0182] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing related hardware with computer-readable instructions. These computer-readable instructions can be stored in a computer-readable storage medium. When executed, the program can include the processes of the embodiments of the above methods. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, optical disk, or read-only memory (ROM), or random access memory (RAM).

[0183] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0184] Example 2

[0185] Further reference Figure 2 As a response to the above Figure 1 The present invention provides an embodiment of a vehicle-mounted terminal wireless debugging device, which is implemented in accordance with the method shown. Figure 1 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0186] like Figure 2 As shown, the vehicle-mounted terminal wireless debugging device 70 described in this embodiment includes: an integration module 71, a configuration module 72, a running authorization module 73, an opening module 74, a debugging module 75, and a stopping authorization module 76. Wherein:

[0187] Integration module 71 is used to obtain SSH source code and integrate the executable program generated from the SSH source code into the vehicle terminal;

[0188] Configuration module 72 is used to configure the authorization for running and shutting down SSH executable programs;

[0189] The authorization module 73 is used to authorize the vehicle terminal to run the SSH executable program;

[0190] Module 74 is opened to enable the vehicle-mounted terminal's hotspot.

[0191] The debugging module 75 is used to debug the vehicle terminal through an external electronic device connected to the vehicle terminal via the vehicle hotspot;

[0192] The authorization module 76 is used to authorize the vehicle terminal to stop running the SSH executable program when debugging is complete.

[0193] The beneficial effects of implementing this embodiment are: improved debugging efficiency, enhanced system security, simplified operation process, and stable operation of the vehicle terminal; wireless connection debugging of embedded software during the debugging phase facilitates troubleshooting and provides effective encryption protection; at the same time, it provides a convenient debugging method during after-sales rework and after-sales software troubleshooting, facilitating after-sales problem analysis; embedded software will frequently undergo wireless troubleshooting or upgrades, and during the debugging phase before vehicle launch, upgrades do not require reliance on a server backend, only a computer is needed to complete on-site or remote control upgrades; even if after-sales encounters server failure or diagnostic tools are unable to perform upgrades, wireless access to the terminal can be performed at any time for upgrades, without requiring customers to wait for a long time.

[0194] Example 3

[0195] To address the aforementioned technical problems, embodiments of the present invention also provide a computer device. Please refer to [link / reference needed]. Figure 3 , Figure 3 This is a basic structural block diagram of the computer device in this embodiment.

[0196] The aforementioned computer device 8 includes a memory 81, a processor 82, and a network interface 83 that are interconnected via a system bus. It should be noted that only the computer device 8 with components 81, 82, and 83 is shown in the figure; however, it should be understood that it is not required to implement all the shown components, and more or fewer components can be implemented alternatively. Those skilled in the art will understand that the computer device described herein is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0197] The aforementioned computer devices can be desktop computers, laptops, handheld computers, and cloud servers, among other computing devices. These devices can facilitate human-computer interaction with users through keyboards, mice, remote controls, touchpads, or voice-activated devices.

[0198] The aforementioned memory 81 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the aforementioned memory 81 may be an internal storage unit of the aforementioned computer device 8, such as the hard disk or memory of the computer device 8. In other embodiments, the aforementioned memory 81 may also be an external storage device of the aforementioned computer device 8, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 8. Of course, the aforementioned memory 81 may also include both the internal storage unit and its external storage device of the aforementioned computer device 8. In this embodiment, the aforementioned memory 81 is typically used to store the operating system and various application software installed on the aforementioned computer device 8, such as computer-readable instructions for vehicle terminal wireless debugging methods, etc. In addition, the aforementioned memory 81 can also be used to temporarily store various types of data that have been output or will be output.

[0199] In some embodiments, the processor 82 described above may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 82 is typically used to control the overall operation of the computer device 8. In this embodiment, the processor 82 is used to execute computer-readable instructions stored in the memory 81 or to process data, for example, to execute computer-readable instructions for the aforementioned vehicle-mounted terminal wireless debugging method.

[0200] The network interface 83 may include a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the computer device 8 and other electronic devices.

[0201] The beneficial effects of implementing this embodiment are: improved debugging efficiency, enhanced system security, simplified operation process, and stable operation of the vehicle terminal; wireless connection debugging of embedded software during the debugging phase facilitates troubleshooting and provides effective encryption protection; at the same time, it provides a convenient debugging method during after-sales rework and after-sales software troubleshooting, facilitating after-sales problem analysis; embedded software will frequently undergo wireless troubleshooting or upgrades, and during the debugging phase before vehicle launch, upgrades do not require reliance on a server backend, only a computer is needed to complete on-site or remote control upgrades; even if after-sales encounters server failure or diagnostic tools are unable to perform upgrades, wireless access to the terminal can be performed at any time for upgrades, without requiring customers to wait for a long time.

[0202] Example 4

[0203] The present invention also provides another embodiment, namely, a computer-readable storage medium storing computer-readable instructions that can be executed by at least one processor to cause the at least one processor to perform the steps of the vehicle terminal wireless debugging method described above.

[0204] The beneficial effects of implementing this embodiment are: improved debugging efficiency, enhanced system security, simplified operation process, and stable operation of the vehicle terminal; wireless connection debugging of embedded software during the debugging phase facilitates troubleshooting and provides effective encryption protection; at the same time, it provides a convenient debugging method during after-sales rework and after-sales software troubleshooting, facilitating after-sales problem analysis; embedded software will frequently undergo wireless troubleshooting or upgrades, and during the debugging phase before vehicle launch, upgrades do not require reliance on a server backend, only a computer is needed to complete on-site or remote control upgrades; even if after-sales encounters server failure or diagnostic tools are unable to perform upgrades, wireless access to the terminal can be performed at any time for upgrades, without requiring customers to wait for a long time.

[0205] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods of the various embodiments of the present invention.

[0206] Obviously, the embodiments described above are merely some embodiments of the present invention, not all embodiments. The accompanying drawings show preferred embodiments of the present invention, but do not limit the patent scope of the present invention. The present invention can be implemented in many different forms; rather, these embodiments are provided to provide a more thorough and complete understanding of the disclosure of the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or make equivalent substitutions for some of the technical features. Any equivalent structures made using the content of this specification and drawings, directly or indirectly applied to other related technical fields, are similarly within the patent protection scope of this invention.

Claims

1. A method for wireless debugging of a vehicle-mounted terminal, characterized in that, Includes the following steps: Obtain the SSH source code and integrate the executable program generated from the SSH source code into the vehicle terminal; Configure permissions for running and shutting down SSH executables; The vehicle-mounted terminal is authorized to run an SSH executable program; Turn on the vehicle-mounted terminal's hotspot; The vehicle terminal is debugged by connecting to an external electronic device that passes through the vehicle hotspot and is connected to the vehicle terminal. Once debugging is complete, authorize the vehicle terminal to stop running the SSH executable program.

2. The vehicle-mounted terminal wireless debugging method according to claim 1, characterized in that, The steps of obtaining the SSH source code and integrating the executable program generated from the SSH source code into the vehicle terminal specifically include: Select the SSH version based on the hardware and software environment of the vehicle terminal; Download the SSH source package according to the selected SSH version; Extract the downloaded SSH source code package to the specified directory of the vehicle terminal; Compile the SSH source code into an executable program; The SSH executable program is integrated into the vehicle terminal.

3. The vehicle-mounted terminal wireless debugging method according to claim 1, characterized in that, The steps for configuring the authorization to run and shut down SSH executable programs specifically include: Configure user or group permissions for the SSH executable file; Configure the system log service to record SSH service startup and shutdown events.

4. The vehicle-mounted terminal wireless debugging method according to claim 1, characterized in that, The steps of authorizing the vehicle terminal to run the SSH executable program specifically include: Obtain the IP address of the vehicle terminal; Using the SSH client on the debugging device, connect to the vehicle terminal via IP address with the authorized and configured permissions; After successfully connecting to the vehicle terminal, the SSH executable program is authorized to run.

5. The vehicle-mounted terminal wireless debugging method according to claim 1, characterized in that, The specific steps for turning on the vehicle-mounted terminal's hotspot include: Enable the Wi-Fi hotspot function of the vehicle terminal; Set the network name and password for the vehicle terminal; Save the network name and password of the vehicle terminal and select "Applicable".

6. The vehicle-mounted terminal wireless debugging method according to claim 1, characterized in that, The step of debugging the vehicle terminal via an external electronic device connected to the vehicle terminal through the vehicle hotspot specifically includes: Turn on the WiFi function of the external electronic device, search for and connect to the vehicle hotspot of the vehicle terminal; Obtain the IP address of the vehicle terminal; Establish communication with the vehicle-mounted terminal; Send debugging instructions to the vehicle-mounted terminal; Receive the response returned by the vehicle terminal and parse it; Record debugging commands and response results.

7. The vehicle-mounted terminal wireless debugging method according to any one of claims 1 to 6, characterized in that, The step of authorizing the vehicle terminal to stop running the SSH executable program after debugging is completed specifically includes: Verify debugging permissions to ensure you have permission to stop the SSH executable. In the vehicle-mounted terminal, locate the running information and process of the SSH executable program; Send a stop command to the SSH executable; Confirm that the SSH executable has stopped running; The operation of stopping the SSH executable program is recorded in the system log and the log information is saved.

8. A vehicle-mounted terminal wireless debugging device, characterized in that, include: An integration module is used to obtain SSH source code and integrate the executable program generated from the SSH source code into the vehicle terminal. The configuration module is used to configure the authorization for running and shutting down SSH executables; The authorization module is used to authorize the vehicle terminal to run SSH executable programs; The module is opened to enable the vehicle-mounted terminal's hotspot. The debugging module is used to debug the vehicle terminal via an external electronic device connected to the vehicle terminal through the vehicle hotspot; The Stop Authorization module is used to authorize the vehicle terminal to stop running the SSH executable program when debugging is complete.

9. A computer device comprising a memory and a processor, wherein the memory stores computer-readable instructions, and the processor, when executing the computer-readable instructions, implements the steps of the vehicle-mounted terminal wireless debugging method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the vehicle terminal wireless debugging method as described in any one of claims 1 to 7.

Images