A vehicle remote commissioning system and method

Abstract

The embodiment of the application provides a vehicle remote debugging system and method, and relates to the technical field of vehicle software debugging. The vehicle remote debugging system comprises a debugging device, a cloud server and a vehicle. The debugging device comprises at least a local agent port, is configured to access a controller service port in the vehicle through port mapping based on the local agent port or a server agent port, and the cloud server comprises at least a server agent port, is configured to map the controller service port to the server agent port and map the local agent port to the server agent port to form port mapping. The vehicle comprises at least a controller service port and a controller debugging tool service, is configured to access the corresponding controller debugging tool service through the controller service port, and realize remote debugging of the vehicle. Through the vehicle remote debugging system, the real-time performance and flexibility of vehicle remote debugging can be improved.

Description

Technical Field

[0001] This invention relates to the field of vehicle software debugging technology, and in particular to a vehicle remote debugging system and method. Background Technology

[0002] With the development of the automotive industry, the level of intelligence in vehicles is constantly increasing, and the number of vehicle-mounted controllers and software is also constantly growing. However, the occurrence of vehicle-mounted controller failures and software bugs is inevitable, causing great trouble for car owners and automakers. Traditional vehicle maintenance and troubleshooting require manual on-vehicle diagnosis and debugging, which has pain points such as long processing time, high labor costs, and high rates of user complaints.

[0003] To address this issue, remote vehicle diagnostics and debugging technology has gradually become a popular research direction in the automotive industry. Traditional remote vehicle diagnostics technologies require a connection to the public network, and the complexity of vehicle network environments, such as internal LANs and dynamic IP addresses, increases the difficulty of remote diagnostics. Furthermore, remote debugging methods that convert debugging commands into proprietary protocols are complex and diverse, their stability is difficult to guarantee, and adding new debugging command capabilities requires redevelopment. Therefore, improving the real-time performance and flexibility of remote vehicle debugging is a key technical problem that this invention aims to solve. Summary of the Invention

[0004] This invention provides a vehicle remote debugging system and method to improve the real-time performance and flexibility of vehicle remote debugging.

[0005] A first aspect of this invention provides a vehicle remote debugging system, the vehicle remote debugging system comprising: debugging equipment, a cloud server, and a vehicle;

[0006] The debugging device includes at least: a local proxy port; the debugging device is used to access the controller service port in the vehicle through port mapping based on the local proxy port or the server proxy port.

[0007] The cloud server includes at least: the server proxy port; the cloud server is used to map the controller service port to the server proxy port, and to map the local proxy port to the server proxy port, forming the port mapping;

[0008] The vehicle includes at least: the controller service port and the controller debugging tool service; the vehicle is used to access the corresponding controller debugging tool service through the controller service port to realize remote debugging of the vehicle.

[0009] Optionally, the vehicle further includes: a vehicle-side agent client; the cloud server further includes: a cloud-based agent service;

[0010] The vehicle is configured to establish a communication connection between the vehicle-side agent client and the cloud-based agent service after the vehicle-side agent client is started; establish a TCP / UDP traffic tunnel between the vehicle-side agent client and the cloud-based agent service based on the communication connection and the port mapping, and enable a remote debugging channel; and forward the TCP / UDP traffic of the controller service port and the server agent port to each other according to the port mapping.

[0011] Optionally, the debugging device further includes: a local agent client;

[0012] The debugging device is used to establish a communication connection between the local agent client and the cloud agent service after the local agent client is started; establish a TCP / UDP traffic tunnel between the local agent client and the cloud agent service based on the communication connection and the port mapping; and forward the TCP / UDP traffic of the local agent port and the server agent port to each other according to the port mapping, so as to realize the forwarding of the TCP / UDP traffic of the controller service port and the local agent port to each other according to the port mapping.

[0013] Optionally, the vehicle further includes: multiple vehicle-side controllers, multiple controller debugging tool services, the controller debugging tool services are integrated in the corresponding vehicle-side controllers, and the multiple vehicle-side controllers are connected to the vehicle Ethernet to form a vehicle local area network;

[0014] The vehicle-side proxy client is used to proxy and forward TCP / UDP traffic to each controller service port through the vehicle's local area network.

[0015] Optionally, the debugging equipment communicates with the cloud server via the Internet, and the vehicle accesses the Internet via onboard 4G, 5G, or WiFi, and communicates with the cloud server via the Internet.

[0016] Optionally, the vehicle-side agent client is integrated on any vehicle-side controller that has the ability to access the cloud server, and the controller debugging tool service is a debugging tool service based on the TCP / UDP transmission protocol.

[0017] Optionally, the vehicle further includes: a vehicle-side communication client; the cloud server further includes: a cloud-based communication service; and a communication connection is established between the vehicle-side communication client and the cloud-based communication service.

[0018] The vehicle communication client is used to start the vehicle-side agent client and the controller debugging tool service based on the debugging notification issued by the cloud communication service.

[0019] Optionally, the cloud server may further include: a remote server debugging service;

[0020] The server remote debugging service is used to provide remote debugging of HMI, and to provide at least one of the following functions by accessing the database and calling the cloud communication service: finding the vehicle to be debugged by the vehicle's unique identifier, remotely opening / closing the remote debugging channel of the vehicle to be debugged, displaying remote debugging information, displaying remote debugging shortcut operation commands, and displaying a web terminal.

[0021] Optionally, the debugging device is used to access the controller service port in the vehicle through the port mapping based on the server proxy port when remote debugging is performed via a web terminal;

[0022] The debugging device is used to access the controller service port in the vehicle through the port mapping based on the local proxy port when performing remote debugging via a local terminal.

[0023] Optionally, the cloud server further includes: server terminal services;

[0024] The server terminal service is used to deploy a specified terminal of the cloud server as the web terminal and share the debugging environment of the specified terminal.

[0025] Optionally, the cloud server may also include: a server debugging tool client;

[0026] The debugging device is used to access the server proxy port by calling the server debugging tool client through the web terminal, and to access the controller service port in the vehicle through the port mapping.

[0027] Optionally, the debugging device further includes: a local debugging tool client;

[0028] The debugging device is used to access the local proxy port by calling the local debugging tool client through the local terminal, and to access the controller service port in the vehicle through the port mapping.

[0029] A second aspect of this invention provides a method for remote vehicle debugging, applied to a remote vehicle debugging system. The remote vehicle debugging system includes: a debugging device, a cloud server, and a vehicle; the debugging device includes at least: a local proxy port; the cloud server includes at least: a server proxy port; the vehicle includes at least: a controller service port and a controller debugging tool service; the method includes:

[0030] Through the cloud server, the controller service port is mapped to the server proxy port, and the local proxy port is mapped to the server proxy port, thus forming a port mapping;

[0031] Through the debugging device, the controller service port in the vehicle can be accessed via the port mapping based on the local proxy port or the server proxy port.

[0032] Remote debugging of the vehicle can be achieved by accessing the corresponding controller debugging tool service through the controller service port.

[0033] Optionally, the vehicle further includes: a vehicle-side agent client; the cloud server further includes: a cloud-based agent service; the method further includes:

[0034] After the vehicle-side agent client is started, a communication connection is established between the vehicle-side agent client and the cloud-based agent service. Based on the communication connection and the port mapping, a TCP / UDP traffic tunnel is established between the vehicle-side agent client and the cloud-based agent service, and a remote debugging channel is opened. The TCP / UDP traffic of the controller service port and the server agent port is forwarded to each other according to the port mapping.

[0035] Optionally, the debugging device further includes: a local agent client; the method further includes:

[0036] Using the debugging device, after starting the local agent client, a communication connection is established between the local agent client and the cloud agent service; based on the communication connection and the port mapping, a TCP / UDP traffic tunnel is established between the local agent client and the cloud agent service; the TCP / UDP traffic of the local agent port and the server agent port is forwarded to each other according to the port mapping, so as to realize the mutual forwarding of TCP / UDP traffic of the controller service port and the local agent port according to the port mapping.

[0037] Optionally, the vehicle further includes: multiple vehicle-side controllers, multiple controller debugging tool services, the controller debugging tool services being integrated into the corresponding vehicle-side controllers, and the multiple vehicle-side controllers connecting to the vehicle Ethernet to form a vehicle local area network; the method further includes:

[0038] The vehicle-side proxy client uses the vehicle's local area network to proxy and forward TCP / UDP traffic to the service ports of each controller.

[0039] Optionally, the debugging equipment communicates with the cloud server via the Internet, and the vehicle accesses the Internet via onboard 4G, 5G, or WiFi, and communicates with the cloud server via the Internet.

[0040] Optionally, the vehicle-side agent client is integrated on any vehicle-side controller that has the ability to access the cloud server, and the controller debugging tool service is a debugging tool service based on the TCP / UDP transmission protocol.

[0041] Optionally, the vehicle further includes: a vehicle-side communication client; the cloud server further includes: a cloud-based communication service; a communication connection is established between the vehicle-side communication client and the cloud-based communication service; the method further includes:

[0042] Based on the debugging notification issued by the cloud communication service, the vehicle-side agent client and the controller debugging tool service are started through the vehicle communication client.

[0043] Optionally, the cloud server further includes: a server remote debugging service; the method further includes:

[0044] The server remote debugging service provides remote debugging HMI, and provides at least one of the following functions by accessing the database and calling the cloud communication service: finding the vehicle to be debugged by the vehicle's unique identifier, remotely opening / closing the remote debugging channel of the vehicle to be debugged, displaying remote debugging information, displaying remote debugging shortcut operation commands, and displaying a web terminal.

[0045] Optionally, accessing the controller service port in the vehicle via the debugging device, based on the local proxy port or the server proxy port, through the port mapping includes:

[0046] In the case of remote debugging via a web terminal, the debugging device accesses the controller service port in the vehicle through port mapping based on the server proxy port; or...

[0047] In the case of remote debugging via a local terminal, the debugging device accesses the controller service port in the vehicle through port mapping based on the local proxy port.

[0048] Optionally, the cloud server further includes: server terminal service; the method further includes:

[0049] The server terminal service enables the deployment of a specified terminal on the cloud server as the web terminal and the sharing of the debugging environment of the specified terminal.

[0050] Optionally, the cloud server further includes: a server debugging tool client; the above step "accessing the controller service port in the vehicle through the debugging device based on the server proxy port via the port mapping" includes:

[0051] Using the debugging device, the server debugging tool client is invoked via the web terminal to access the server proxy port, and the controller service port in the vehicle is accessed via the port mapping.

[0052] Optionally, the debugging device further includes: a local debugging tool client; the above step "accessing the controller service port in the vehicle through the local proxy port via the port mapping using the debugging device" includes:

[0053] Through the debugging device, the local terminal calls the local debugging tool client to access the local proxy port, and the port mapping accesses the controller service port in the vehicle.

[0054] The vehicle remote debugging system provided in this embodiment establishes port mapping between the controller service port, server proxy port, and local proxy port. The debugging device can directly access the vehicle's control server port via the port mapping through the local proxy port or server proxy port. This allows access to the corresponding vehicle-specific controller debugging tool service via the control server port, enabling remote vehicle debugging. Based on this system, the vehicle to be debugged does not require the development of customized software, such as custom protocols. Only the vehicle's native controller debugging tool service needs to be integrated; adding or removing the service only requires configuration modifications. Furthermore, the remote debugging experience is essentially the same as local debugging. Thus, the vehicle remote debugging system provided in this embodiment not only enhances the flexibility and scalability of remote vehicle debugging but also improves its real-time performance, increasing vehicle maintenance efficiency and reliability, and providing more convenient and efficient services for vehicle owners and manufacturers. Attached Figure Description

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

[0056] Figure 1 This is a structural block diagram of a vehicle remote debugging system according to an embodiment of the present invention;

[0057] Figure 2This is a block diagram of a vehicle remote debugging system according to an embodiment of the present invention;

[0058] Figure 3 This is an overall system architecture diagram of a vehicle remote debugging system according to an embodiment of the present invention;

[0059] Figure 4 This is a flowchart illustrating a method for remote vehicle debugging via a local terminal, as shown in one embodiment of the present invention.

[0060] Figure 5 This is a flowchart illustrating a method for remote vehicle debugging via a web terminal, as shown in one embodiment of the present invention.

[0061] Figure 6 This is a flowchart of the steps of a vehicle remote debugging method provided in an embodiment of the present invention. Detailed Implementation

[0062] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0063] refer to Figure 1 , Figure 1 This is a structural block diagram illustrating a remote vehicle debugging system according to an embodiment of the present invention. Figure 1 As shown, the vehicle remote debugging system 100 of this embodiment may include: debugging equipment 101, cloud server 102 and vehicle 103; wherein, the cloud server 102 includes at least: the server proxy port 1021; the cloud server 102 is used to map the controller service port 1031 to the server proxy port 1021, and to map the local proxy port 1011 to the server proxy port 1021, forming the port mapping.

[0064] In this embodiment, the cloud server can refer to the vehicle cloud platform of an automaker, providing remote communication capabilities with the vehicle. The cloud server in this embodiment also serves as a bridge for remote vehicle debugging. It enables intranet penetration of the vehicle's local area network (LAN), mapping the service ports of each controller within the LAN to the server proxy port, and mapping the local proxy port of the debugging equipment to the server port. Access to the debugging tool services of each vehicle controller can be achieved by accessing the server proxy port. In other words, this embodiment uses the cloud server to map controller service ports to the server proxy port, and also maps local proxy ports to the server proxy port, forming a port mapping between controller service ports, server proxy ports, and local proxy ports.

[0065] The debugging device 101 includes at least: a local proxy port 1011; the debugging device 101 is used to access the controller service port 1031 in the vehicle 103 through port mapping based on the local proxy port 1011 or the server proxy port 1021.

[0066] In this embodiment, the debugging device is used by technicians to remotely debug vehicles, such as a debugging computer or a debugging mobile phone. The debugging device has a local proxy port, which can be used to access the controller service port in the vehicle through port mapping, thereby initiating remote vehicle debugging.

[0067] The vehicle 103 includes at least: the controller service port 1031 and the controller debugging tool service 1032; the vehicle 103 is used to access the corresponding controller debugging tool service 1032 through the controller service port 1031 to realize remote debugging of the vehicle.

[0068] In this embodiment, the vehicle to be debugged can be any vehicle connected to the cloud server. During development, the vehicle in this embodiment integrates multiple controller debugging tool services for debugging vehicle functions. Each controller debugging tool service corresponds to a controller service port, which can be accessed to debug the corresponding controller debugging tool server. Therefore, this embodiment can access the controller service port based on a local proxy port or a server proxy port, thereby accessing the corresponding controller debugging tool service through the controller service port to achieve remote vehicle debugging.

[0069] In this embodiment, intranet penetration technology is used to map the service ports of each controller in the vehicle to the server proxy port of the cloud server and the local proxy port of the debugging device, establishing a port mapping. Based on the local proxy port or the server proxy port, the control server port in the vehicle can be directly accessed through the port mapping, thereby accessing the corresponding vehicle's own controller debugging tool service and realizing remote vehicle debugging. Based on this remote vehicle debugging system, only the vehicle's native controller debugging tool service needs to be integrated; adding or removing controller debugging tool services only requires modifying the configuration, enhancing the flexibility and scalability of remote vehicle debugging. Furthermore, the remote debugging experience of this system, which remotely calls the controller debugging tool service, is essentially the same as local debugging, improving the real-time performance of remote vehicle debugging, increasing vehicle maintenance efficiency and reliability, and providing more convenient and efficient services for vehicle owners and automobile manufacturers.

[0070] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the vehicle further includes a vehicle-side agent client; and the cloud server further includes a cloud-based agent service.

[0071] In this embodiment, the vehicle also includes a vehicle-side agent client, and the cloud server includes a cloud-side agent service. The vehicle-side agent client is vehicle-side software that serves as the client software for the cloud-side agent service. This software primarily performs the following functions with the cloud-side agent service: establishing a communication connection, synchronizing agent configuration, and creating a TCP / UDP traffic proxy link. The synchronized agent configuration can be based on the mapping relationship between the controller service port in the vehicle and the server proxy port in the cloud server, as well as authentication and security-related configurations. The vehicle-side agent client enables access to the controller service port on the vehicle. Through the vehicle-side agent client and the cloud-side agent service, a TCP / UDP traffic tunnel is established between the vehicle and the cloud server, forwarding TCP / UDP traffic between the controller service port and the server proxy port according to the mapping relationship.

[0072] The vehicle is configured to establish a communication connection between the vehicle-side agent client and the cloud-based agent service after the vehicle-side agent client is started; establish a TCP / UDP traffic tunnel between the vehicle-side agent client and the cloud-based agent service based on the communication connection and the port mapping, and enable a remote debugging channel; and forward the TCP / UDP traffic of the controller service port and the server agent port to each other according to the port mapping.

[0073] In this embodiment, the vehicle-side agent client and vehicle-side controller debugging tool services are not started by default. After starting the vehicle-side agent client, a communication connection can be established between the vehicle-side agent client and the cloud agent server. In an optional implementation, the established communication connection can be equipped with relevant mechanisms to ensure secure and stable communication, such as connection authentication, communication heartbeat, and error reconnection.

[0074] After establishing a communication connection, the vehicle can establish a TCP / UDP traffic tunnel between the vehicle agent client and the cloud agent service based on this communication connection and the established port mapping, thus creating a remote debugging channel. During remote debugging, the vehicle to be debugged is first located via the cloud server, then the remote debugging channel for the vehicle is opened via the cloud server, and remote debugging is performed. After debugging is complete, the remote debugging channel and the vehicle agent client are closed. The vehicle and cloud server can also forward TCP / UDP traffic between the controller service port and the server agent port according to the port mapping.

[0075] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the debugging device further includes a local agent client.

[0076] In this embodiment, the local proxy client is the client software of the cloud proxy service on the cloud server. This software primarily performs the following functions with the cloud proxy service: establishing a communication connection, synchronizing proxy configuration, and creating a TCP / UDP traffic proxy link. In an optional implementation, the communication connection between the local proxy client and the cloud proxy service can be enhanced with mechanisms to ensure secure and stable communication, such as connection authentication, communication heartbeats, and error reconnection. Synchronizing the proxy configuration can be based on the mapping relationship between the local proxy port on the debugging device and the server proxy port on the cloud server, as well as authentication and security-related configurations.

[0077] The cloud proxy service is the server side for the vehicle-side proxy client and the local proxy client for the debugging equipment. The port mapping is mainly implemented through the vehicle-side proxy client, the cloud proxy service, and the local proxy client. Through technologies such as intranet penetration and reverse proxy, a TCP / UDP traffic tunnel is opened between the vehicle, the cloud server, and the debugging equipment, and the TCP / UDP traffic of the controller service port, the server proxy port, and the local proxy port is forwarded to each other according to the mapping relationship.

[0078] The debugging device is used to establish a communication connection between the local agent client and the cloud agent service after the local agent client is started; establish a TCP / UDP traffic tunnel between the local agent client and the cloud agent service based on the communication connection and the port mapping; and forward the TCP / UDP traffic of the local agent port and the server agent port to each other according to the port mapping, so as to realize the forwarding of the TCP / UDP traffic of the controller service port and the local agent port to each other according to the port mapping.

[0079] In this embodiment, when remote vehicle debugging is required, the debugging device can activate the local agent client to establish a communication connection between the local agent client and the cloud agent service; and establish a TCP / UDP traffic tunnel between the local agent client and the cloud agent service based on the communication connection and the established port mapping; thereby forwarding the TCP / UDP traffic of the local agent port and the server agent port to each other according to the port mapping, so as to realize the forwarding of the TCP / UDP traffic of the controller service port and the local agent port to each other according to the port mapping.

[0080] In another optional implementation, encryption and compression technology can be used to encrypt and compress TCP / UDP traffic data between the vehicle-side agent client, the cloud agent service, and the local agent client, thereby ensuring the security of remote debugging and saving bandwidth. However, data compression consumes CPU resources; therefore, compression can be selected based on requirements.

[0081] The vehicle remote debugging system provided in this embodiment fully considers the security of remote debugging data. The communication data between the vehicle and the cloud server, and between the cloud server and the debugging equipment, must be encrypted and protected using encryption technology to ensure data security.

[0082] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the vehicle further includes: multiple vehicle-side controllers; multiple controller debugging tool services are provided, integrated within the respective vehicle-side controllers; and the multiple vehicle-side controllers are connected to an in-vehicle Ethernet network, forming a vehicle local area network.

[0083] In this embodiment, the vehicle includes multiple vehicle-side controllers. Each vehicle-side controller is connected to the vehicle's Ethernet network, forming a vehicle local area network. All vehicle-side controllers connected to the vehicle's Ethernet network can be used as remote debugging targets, such as TBOX controllers, cockpit controllers, driver controllers, and body controllers. In this embodiment, there are multiple controller debugging tool services, each integrated into its corresponding vehicle-side controller. There is a one-to-one correspondence between vehicle-side controllers and controller debugging tool services, which are used to perform relevant debugging on their corresponding vehicle-side controllers.

[0084] The vehicle-side proxy client is used to proxy and forward TCP / UDP traffic to each controller service port through the vehicle's local area network.

[0085] In this embodiment, the vehicle-side agent client can use the vehicle's local area network to proxy and forward TCP / UDP traffic to the vehicle's controller service port, thereby enabling remote debugging functionality based on accessing the controller service port to control the controller debugging tool service.

[0086] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the debugging equipment communicates with the cloud server via the Internet, and the vehicle accesses the Internet via onboard 4G, 5G, or WiFi, communicating with the cloud server through the Internet.

[0087] In this embodiment, the debugging equipment communicates with the cloud server via the Internet, while the vehicle accesses the Internet via in-vehicle 4G, 5G or WiFi, and then communicates with the cloud server via the Internet. Thus, through intranet penetration and reverse proxy technology, the vehicle's local area network can be penetrated, and the controller service port in the local area network can be mapped to the local proxy port and server proxy port on the Internet to achieve remote debugging.

[0088] In this embodiment, based on the vehicle remote debugging system, apart from the certain delay introduced by the Internet and the vehicle 4G / 5G network, the remote debugging experience is exactly the same as local debugging, which can greatly increase the flexibility and convenience of remote debugging of the vehicle controller.

[0089] In one implementation, such as Figure 2 As shown, Figure 2 This is a block diagram illustrating a vehicle remote debugging system according to one embodiment of the present invention. Figure 2 In this context, the debugging equipment can be a debugging computer or a debugging mobile phone. The debugging equipment communicates with the cloud server via the Internet. Vehicles 1 to N can access the Internet via onboard 4G / 5G, thereby communicating with the cloud server via the Internet.

[0090] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the vehicle-side agent client is integrated on any vehicle-side controller capable of accessing the cloud server, and the controller debugging tool service is a debugging tool service based on the TCP / UDP transport protocol.

[0091] In this embodiment, the controller debugging tool service on the vehicle-side supports all debugging tool services based on TCP / UDP transport protocols, such as Android debugging tool ADB service, Linux / QNX SSH service, etc. Therefore, this embodiment can support remote debugging of all vehicle-side controllers using Android, Linux, and QNX operating systems. Furthermore, in this embodiment, the vehicle-side agent client can theoretically be integrated into any vehicle-side controller capable of accessing a cloud server. In practical implementation, integrating the vehicle-side agent client into the TBOX controller or cockpit controller is more suitable. The TBOX controller can access the cloud server via 4G / 5G network, while the cockpit controller can access the cloud server not only via the 4G / 5G network provided by the TBOX controller but also via Wi-Fi connection.

[0092] In this embodiment, the vehicle remote debugging system can directly support remote debugging of all SOCs running Android, Linux, and QNX operating systems. In addition, by custom-developing vehicle-side debugging tools, it can indirectly support remote debugging of all MCUs running RTOS and AUTOSAR operating systems, thus making the scope of support in this embodiment extremely broad.

[0093] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the vehicle further includes a vehicle-side communication client; the cloud server further includes a cloud-based communication service; and a communication connection is established between the vehicle-side communication client and the cloud-based communication service.

[0094] In this embodiment, the vehicle also includes a vehicle-side communication client, and the cloud server includes a cloud-based communication service. The vehicle-side communication client is the client software of the cloud-based communication service on the cloud server. This client establishes a communication link with the cloud-based communication service to enable remote vehicle control. The vehicle-side agent client and the vehicle controller debugging tool service are not started by default, but can be remotely started and stopped through the aforementioned remote debugging channel. The cloud-based communication service is the server-side application of the vehicle-side communication client. The cloud server can remotely control the vehicle through this service. In this embodiment, the vehicle-side agent client and the controller debugging tool service are remotely started and stopped through this cloud-based communication service.

[0095] The vehicle communication client is used to start the vehicle-side agent client and the controller debugging tool service based on the debugging notification issued by the cloud communication service.

[0096] Specifically, in this embodiment, when remote vehicle debugging is required, the cloud server's cloud communication service sends a debugging notification to the vehicle's in-vehicle communication client. Based on the received debugging notification, the in-vehicle communication client starts the vehicle-side agent client and the controller debugging tool server.

[0097] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the cloud server further includes: a server remote debugging service; the server remote debugging service is used to provide a remote debugging HMI, and, by accessing a database and calling the cloud communication service, to provide at least one of the following functions: finding the vehicle to be debugged using a unique vehicle identifier, remotely opening / closing the remote debugging channel of the vehicle to be debugged, displaying remote debugging information, displaying remote debugging shortcut operation commands, and displaying a web terminal.

[0098] In this embodiment, the cloud server also includes a remote server debugging service. This remote server debugging service serves as both the front-end and back-end services for remote vehicle debugging. For the front-end, the remote server debugging service primarily provides a remote debugging HMI: since remote debugging can be initiated through a webpage, this involves a front-end interface. This front-end interface needs to provide capabilities such as locating the vehicle to be debugged using its unique identifier; this is provided by the remote server debugging service.

[0099] For the backend, the server remote debugging service mainly provides the following functions by accessing the database and calling cloud communication service capabilities: 1. Locating the vehicle to be debugged by the vehicle's unique identifier; 2. Remotely opening / closing the remote debugging channel for the vehicle to be debugged; 3. Displaying remote debugging information, such as remote debugging channel port mapping information; 4. Displaying quick operation commands for remote debugging; 5. Displaying the web terminal, etc.

[0100] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the debugging device is used to access the controller service port in the vehicle through port mapping based on the server proxy port when remote debugging is performed via a web terminal.

[0101] In this embodiment, the debugging device can perform remote vehicle debugging in two ways: the debugging device can perform remote vehicle debugging based on a web terminal, and when performing remote debugging through a web terminal, the debugging device accesses the controller service port in the vehicle through a pre-established port mapping based on a server proxy port.

[0102] The debugging device is used to access the controller service port in the vehicle through the port mapping based on the local proxy port when performing remote debugging via a local terminal.

[0103] In this embodiment, the debugging device can also perform remote vehicle debugging based on a local terminal. The local terminal is debugging software on the debugging device, capable of setting commands, etc. When performing remote debugging via the local terminal, the debugging device accesses the controller service port in the vehicle through a pre-established port mapping via a local proxy port. Preferably, debugging can be performed remotely on a computer via a local terminal or a web browser; debugging can be performed remotely on a mobile phone via a web browser.

[0104] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the cloud server further includes: a server terminal service; the server terminal service is used to deploy a designated terminal of the cloud server as the web page terminal and share the debugging environment of the designated terminal.

[0105] In this embodiment, the cloud server also includes a server terminal service. This server terminal service deploys a designated terminal on the cloud server as a web browser terminal, sharing the designated terminal environment with technicians for remote debugging. Technicians can perform remote debugging by using a web browser on a computer or mobile phone, without needing to deploy a local debugging environment.

[0106] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the cloud server further includes a server debugging tool client.

[0107] In this embodiment, the cloud server also includes a server debugging tool client, which is a client corresponding to the controller debugging tool service in the vehicle. For example, the debugging tool client of the Android ADB debugging service is the ADB Client tool.

[0108] The debugging device is used to access the server proxy port by calling the server debugging tool client through the web terminal, and to access the controller service port in the vehicle through the port mapping.

[0109] In this embodiment, the server debugging tool client is a debugging tool deployed on a cloud server. Technicians can access the server proxy port via a local browser's web terminal using the debugging equipment. Through established port mapping, they can access the controller server port in the vehicle, enabling remote debugging of the vehicle controller. The local browser is the basic software on the debugging equipment. Technicians can access the remote debugging HMI and the web terminal through the local browser, thus initiating and completing remote vehicle debugging via the web terminal.

[0110] In this embodiment, a terminal service is deployed on a cloud server. The debugging device accesses the web terminal deployed on the cloud server through a local browser. By using the server debugging tool client through the web terminal to access the server proxy port, the device can access the controller debugging tool service corresponding to the vehicle controller. This method does not rely on the debugging tool client on the remote debugging device. It only requires installing and deploying the relevant server debugging tool client on the cloud server. The debugging device can then remotely debug the vehicle controller through a browser.

[0111] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle remote debugging system. In this vehicle remote debugging system, the debugging equipment further includes a local debugging tool client.

[0112] In this embodiment, the local debugging tool client is the client corresponding to the controller debugging tool service in the vehicle. For example, the debugging tool client of the Android ADB debugging service is the ADB Client tool.

[0113] The debugging device is used to access the local proxy port by calling the local debugging tool client through the local terminal, and to access the controller service port in the vehicle through the port mapping.

[0114] In this embodiment, the local debugging tool client is a debugging tool deployed locally on the debugging device. Technicians can access the local proxy port by calling the local debugging tool client through the local terminal of the debugging device, and access the controller server port in the vehicle through the established port mapping. This allows access to the controller debugging tool service corresponding to the vehicle controller, enabling remote debugging of the vehicle controller on the local terminal of the debugging device.

[0115] In another embodiment, such as Figure 3 As shown, Figure 3This is an overall system architecture diagram of a vehicle remote debugging system shown in one embodiment of the present invention.

[0116] exist Figure 3 In the vehicle remote debugging system, the debugging computer / mobile phone is the debugging device. The debugging device includes a local browser, a local terminal, a local debugging tool client, and a local agent client. The local browser is the basic software on the debugging computer or mobile phone, allowing technicians to access the remote debugging HMI and web terminal. The local terminal is debugging software on the debugging computer or mobile phone, capable of outputting commands. The local debugging tool client is the client corresponding to the vehicle-side controller debugging tool service; for example, the debugging tool client for the Android ADB debugging service is the ADB Client tool. The local debugging tool client is the debugging tool deployed locally on the debugging device. Technicians can remotely debug the vehicle-side controller by calling the local debugging tool client through the local terminal to access the local agent port. The local agent client is the client software for the cloud server's cloud agent service. This software mainly performs the following functions with the cloud agent service: establishing a communication connection, synchronizing agent configuration, creating a TCP / UDP traffic proxy link, establishing a TCP / UDP traffic tunnel between the vehicle, cloud server, and debugging device, and forwarding TCP / UDP traffic between the controller service port and the local agent port according to the mapping relationship.

[0117] The cloud server includes: remote server debugging service, cloud communication service, server terminal service, server debugging tool client, and cloud proxy service. The cloud proxy service serves as the server for both the vehicle-side proxy client and the local proxy client on the debugging equipment. Through technologies such as intranet penetration and reverse proxy, it establishes a TCP / UDP traffic tunnel between the vehicle, the cloud server, and the debugging computer, forwarding TCP / UDP traffic between the controller service port, server proxy port, and local proxy port according to a mapping relationship. The cloud communication service serves as the server for the vehicle-side communication client. This service enables remote control of the vehicle from the cloud. In this embodiment, it is used to remotely control the startup and shutdown of the vehicle-side proxy client and the vehicle-side controller debugging tool service. The remote server debugging service is the front-end and back-end service for remote vehicle debugging. The front-end provides a remote debugging HMI, and the back-end, through database access and cloud communication service capabilities, allows functions such as locating the vehicle to be debugged and remotely enabling or disabling the remote debugging channel. The server terminal service deploys a designated terminal of the server as a web browser terminal, sharing the server terminal environment with technicians for remote debugging. Technicians can perform remote debugging via a computer or mobile browser without needing to deploy a local debugging environment. The server debugging tool client is the client corresponding to the vehicle controller debugging tool service. For example, the debugging tool client for the Android ADB debugging service is the ADB Client tool. The server debugging tool client is a debugging tool deployed on a cloud server. Technicians can access the server proxy port through a web browser terminal to remotely debug the vehicle controller.

[0118] The vehicle includes: vehicle-side controllers 1, 2…, vehicle-side communication clients, controller debugging tool servers, and vehicle-side agent clients. Each vehicle-side controller is connected to the vehicle's Ethernet network, forming a vehicle local area network (LAN). All controllers connected to the vehicle's Ethernet network can be used for remote debugging, such as TBOX controllers, cockpit controllers, driver controllers, and body controllers. The vehicle-side agent client is vehicle-side software that serves as the client software for the cloud server's proxy service. This software primarily performs the following functions with the cloud proxy service: establishing communication connections, synchronizing proxy configurations, and creating TCP / UDP traffic proxy links. The vehicle-side agent client accesses the service ports of each vehicle-side controller through the vehicle's LAN. Through the vehicle-side agent client and the cloud proxy service, a TCP / UDP traffic tunnel is established between the vehicle and the cloud server, forwarding TCP / UDP traffic between the controller service ports and the server proxy ports according to a mapping relationship. The vehicle-side controller needs to integrate corresponding controller debugging tool services. This embodiment supports all debugging tool services based on TCP / UDP transport protocols, such as Android debugging tool ADB service, Linux / QNX SSH service, etc. Therefore, this invention is applicable to all vehicle-side controllers using Android, Linux, and QNX operating systems. The vehicle-side communication client is the client software of the cloud server's cloud communication service. This software establishes a communication link with the cloud communication service to realize the remote vehicle control function. The vehicle-side agent client and the vehicle-side controller debugging tool service are not started by default, but can be remotely started and stopped through the aforementioned remote control link.

[0119] This embodiment enables direct access to the debugging tools and services of various vehicle-side controllers on the local terminal of the debugging device or a web browser terminal. It is applicable to various debugging scenarios and needs. The vehicle-side debugging tools and services include all debugging services based on TCP / UDP transport protocols, such as Android debugging tool ADB service and Linux / QNX SSH service. Therefore, the system provided in this embodiment can also support remote debugging of all vehicle-side controllers using Android, Linux, and QNX operating systems. Except for some latency introduced by the internet and in-vehicle 4G / 5G networks, remote debugging is identical to local debugging, greatly increasing the flexibility and convenience of remote debugging of vehicle-side controllers. Furthermore, this embodiment applies mature internet intranet penetration technology to automobiles. For the debugging channel, the vehicle-side controller to be debugged does not need to develop and integrate custom software; it only needs to integrate the system's native debugging services. Therefore, this solution can be quickly deployed and applied, significantly shortening the processing time for remote vehicle debugging, improving the efficiency of software problem handling, reducing user complaint rates, and saving significant manpower costs.

[0120] In another embodiment, such as Figure 4 As shown, Figure 4 This is a flowchart illustrating a method for remote vehicle debugging via a local terminal, as shown in one embodiment of the present invention. Figure 4 First, technicians can access the remote debugging interface via a local browser on their computer / mobile phone. This interface, a front-end provided by the server's remote debugging service, offers a UI that allows them to locate vehicles using vehicle identifiers and access the remote debugging channel for those vehicles. Based on this, the cloud service's remote debugging service returns a page to the front-end. Technicians use the vehicle's unique identifier to locate the vehicle, prompting the cloud server to search its database for vehicle information. The local browser then remotely opens the vehicle's remote debugging channel, enabling the cloud server to notify the vehicle's communication client to launch its agent client via cloud communication services. Upon receiving this notification, the vehicle launches its agent client and the vehicle controller debugging tool service. The agent client and the cloud agent service establish a connection and TCP / UDP tunnel. The cloud server updates the vehicle's remote debugging channel status, and the local browser's remote debugging interface displays the remote debugging channel status and the server agent ports for each vehicle controller's debugging service.

[0121] The local agent client is launched via a local terminal. The local agent client establishes a connection and TCP / UDP traffic tunnel with the cloud agent service. The local agent client displays the local agent port for each vehicle controller's debugging service. The local terminal uses the local debugging client to connect to the local agent port and begin remote debugging. Once remote debugging is complete, the local agent client is closed, at which point the cloud agent service disconnects from the local agent server. The remote debugging channel is then remotely closed via the local browser's debugging interface. The cloud communication service notifies the debugging vehicle to close the vehicle agent client and the debugging tool services for each vehicle controller. The vehicle closes its vehicle agent client, disconnecting it from the cloud agent server. The cloud server updates the vehicle's remote debugging channel status, which is then displayed on the local debugging interface of the debugging device, ending the process.

[0122] In another embodiment, such as Figure 5 As shown, Figure 5 This is a flowchart illustrating a method for remote vehicle debugging via a web terminal, as shown in one embodiment of the present invention. Figure 5First, technicians can access the remote debugging interface via a local browser on their computer / mobile phone. Based on this, the cloud service's remote debugging server responds to the request and returns a front-end page. Technicians can then locate the vehicle for debugging using its unique identification information, prompting the cloud server's remote debugging service to search for vehicle information in its database. The local browser remotely opens the vehicle's remote debugging channel, enabling the cloud server to notify the vehicle's communication client to launch the vehicle's agent client via cloud communication services. Based on this notification, the vehicle to be debugged launches the vehicle's agent client and vehicle controller debugging tool services. The vehicle's agent client and the cloud agent service establish a connection and a TCP / UDP traffic tunnel. The cloud server updates the vehicle's remote debugging channel status, and the local browser's remote debugging interface displays the vehicle's remote debugging channel status and the server agent ports for each vehicle controller debugging service.

[0123] Open a web terminal in a local browser. The terminal server responds to the request. Use the web terminal to connect to the server proxy port using the server debugging client. The terminal server then calls the server debugging client to connect to the server proxy port, initiating remote debugging. Once remote debugging is complete, close the remote debugging channel through the debugging interface. Notify the debugging vehicle via cloud communication service to close the vehicle-side agent client and the debugging tool services for each vehicle-side controller. The vehicle closes its vehicle-side agent client, disconnecting it from the cloud proxy server. The cloud server updates the vehicle's remote debugging channel status, which is then displayed on the local debugging interface of the debugging device, ending the process.

[0124] Based on the same inventive concept, one embodiment of the present invention provides a method for remote vehicle debugging. (Reference) Figure 6 , Figure 6 This is a flowchart illustrating the steps of a remote vehicle debugging method according to an embodiment of the present invention. Figure 6 As shown, this method is applied to a vehicle remote debugging system, which includes: debugging equipment, a cloud server, and a vehicle; the debugging equipment includes at least: a local proxy port; the cloud server includes at least: a server proxy port; the vehicle includes at least: a controller service port and a controller debugging tool service; the method may include the following steps:

[0125] Step S61: Through the cloud server, map the controller service port to the server proxy port, and map the local proxy port to the server proxy port to form a port mapping;

[0126] Step S62: Using the debugging device, access the controller service port in the vehicle through the port mapping based on the local proxy port or the server proxy port;

[0127] Step S63: Through the vehicle, access the corresponding controller debugging tool service based on the controller service port to realize remote debugging of the vehicle.

[0128] Optionally, the vehicle further includes: a vehicle-side agent client; the cloud server further includes: a cloud-based agent service; the method further includes:

[0129] After the vehicle-side agent client is started, a communication connection is established between the vehicle-side agent client and the cloud-based agent service. Based on the communication connection and the port mapping, a TCP / UDP traffic tunnel is established between the vehicle-side agent client and the cloud-based agent service, and a remote debugging channel is opened. The TCP / UDP traffic of the controller service port and the server agent port is forwarded to each other according to the port mapping.

[0130] Optionally, the debugging device further includes: a local agent client; the method further includes:

[0131] Using the debugging device, after starting the local agent client, a communication connection is established between the local agent client and the cloud agent service; based on the communication connection and the port mapping, a TCP / UDP traffic tunnel is established between the local agent client and the cloud agent service; the TCP / UDP traffic of the local agent port and the server agent port is forwarded to each other according to the port mapping, so as to realize the mutual forwarding of TCP / UDP traffic of the controller service port and the local agent port according to the port mapping.

[0132] Optionally, the vehicle further includes: multiple vehicle-side controllers, multiple controller debugging tool services, the controller debugging tool services being integrated into the corresponding vehicle-side controllers, and the multiple vehicle-side controllers connecting to the vehicle Ethernet to form a vehicle local area network; the method further includes:

[0133] The vehicle-side proxy client uses the vehicle's local area network to proxy and forward TCP / UDP traffic to the service ports of each controller.

[0134] Optionally, the debugging equipment communicates with the cloud server via the Internet, and the vehicle accesses the Internet via onboard 4G, 5G, or WiFi, and communicates with the cloud server via the Internet.

[0135] Optionally, the vehicle-side agent client is integrated on any vehicle-side controller that has the ability to access the cloud server, and the controller debugging tool service is a debugging tool service based on the TCP / UDP transmission protocol.

[0136] Optionally, the vehicle further includes: a vehicle-side communication client; the cloud server further includes: a cloud-based communication service; a communication connection is established between the vehicle-side communication client and the cloud-based communication service; the method further includes:

[0137] Based on the debugging notification issued by the cloud communication service, the vehicle-side agent client and the controller debugging tool service are started through the vehicle communication client.

[0138] Optionally, the cloud server further includes: a server remote debugging service; the method further includes:

[0139] The server remote debugging service provides remote debugging HMI, and provides at least one of the following functions by accessing the database and calling the cloud communication service: finding the vehicle to be debugged by the vehicle's unique identifier, remotely opening / closing the remote debugging channel of the vehicle to be debugged, displaying remote debugging information, displaying remote debugging shortcut operation commands, and displaying a web terminal.

[0140] Optionally, step S62 may specifically include:

[0141] In the case of remote debugging via a web terminal, the debugging device accesses the controller service port in the vehicle through port mapping based on the server proxy port; or...

[0142] In the case of remote debugging via a local terminal, the debugging device accesses the controller service port in the vehicle through port mapping based on the local proxy port.

[0143] Optionally, the cloud server further includes: server terminal service; the method further includes:

[0144] The server terminal service enables the deployment of a specified terminal on the cloud server as the web terminal and the sharing of the debugging environment of the specified terminal.

[0145] Optionally, the cloud server further includes: a server debugging tool client; the above step "accessing the controller service port in the vehicle through the debugging device based on the server proxy port via the port mapping" includes:

[0146] Using the debugging device, the server debugging tool client is invoked via the web terminal to access the server proxy port, and the controller service port in the vehicle is accessed via the port mapping.

[0147] Optionally, the debugging device further includes: a local debugging tool client; the above step "accessing the controller service port in the vehicle through the local proxy port via the port mapping using the debugging device" includes:

[0148] Through the debugging device, the local terminal calls the local debugging tool client to access the local proxy port, and the port mapping accesses the controller service port in the vehicle.

[0149] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0150] As the method embodiments are basically similar to the system embodiments, the description is relatively simple, and relevant parts can be found in the description of the system embodiments.

[0151] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0152] Although preferred embodiments of the present invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present invention.

[0153] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0154] The above provides a detailed description of the vehicle remote debugging system and method provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A vehicle remote debugging system, characterized in that, The vehicle remote debugging system includes: debugging equipment, cloud server, and vehicle; The debugging device includes at least: a local proxy port; the debugging device is used to access the controller service port in the vehicle through port mapping based on the local proxy port or the server proxy port. The cloud server includes at least: the server proxy port and the cloud proxy service; the cloud server is used to map the controller service port to the server proxy port and the local proxy port to the server proxy port, forming the port mapping; The vehicle includes at least: the controller service port, the controller debugging tool service, and the vehicle-side agent client; the vehicle is used to access the corresponding controller debugging tool service through the controller service port to realize remote debugging of the vehicle; after starting the vehicle-side agent client, a communication connection is established between the vehicle-side agent client and the cloud agent service; based on the communication connection and the port mapping, a TCP / UDP traffic tunnel is established between the vehicle-side agent client and the cloud agent service to open the remote debugging channel; the TCP / UDP traffic of the controller service port and the server agent port is forwarded to each other according to the port mapping.

2. The vehicle remote debugging system according to claim 1, characterized in that, The debugging equipment also includes: a local agent client; The debugging device is used to establish a communication connection between the local agent client and the cloud agent service after the local agent client is started; establish a TCP / UDP traffic tunnel between the local agent client and the cloud agent service based on the communication connection and the port mapping; and forward the TCP / UDP traffic of the local agent port and the server agent port to each other according to the port mapping, so as to realize the forwarding of the TCP / UDP traffic of the controller service port and the local agent port to each other according to the port mapping.

3. The vehicle remote debugging system according to claim 1, characterized in that, The vehicle also includes: multiple vehicle-end controllers, multiple controller debugging tool services, the controller debugging tool services are integrated in the corresponding vehicle-end controllers, and the multiple vehicle-end controllers are connected to the vehicle Ethernet to form a vehicle local area network; The vehicle-side proxy client is used to proxy and forward TCP / UDP traffic to each controller service port through the vehicle's local area network.

4. The vehicle remote debugging system according to claim 1, characterized in that, The debugging equipment communicates with the cloud server via the Internet, and the vehicle accesses the Internet via onboard 4G, 5G or WiFi, and communicates with the cloud server via the Internet.

5. The vehicle remote debugging system according to claim 3, characterized in that, The vehicle-side agent client is integrated on any vehicle-side controller that has the ability to access the cloud server, and the controller debugging tool service is a debugging tool service based on the TCP / UDP transmission protocol.

6. The vehicle remote debugging system according to claim 1, characterized in that, The vehicle also includes a vehicle-side communication client; the cloud server also includes a cloud-based communication service; and a communication connection is established between the vehicle-side communication client and the cloud-based communication service. The vehicle-side communication client is used to start the vehicle-side agent client and the controller debugging tool service based on the debugging notification issued by the cloud communication service.

7. The vehicle remote debugging system according to claim 6, characterized in that, The cloud server also includes: server remote debugging service; The server remote debugging service is used to provide a remote debugging human-machine interface, and to provide at least one of the following functions by accessing the database and calling the cloud communication service: finding the vehicle to be debugged by the vehicle's unique identifier, remotely opening / closing the remote debugging channel of the vehicle to be debugged, displaying remote debugging information, displaying remote debugging shortcut operation commands, and displaying a web terminal.

8. The vehicle remote debugging system according to claim 1, characterized in that, The debugging device is used to access the controller service port in the vehicle through port mapping based on the server proxy port when performing remote debugging via a web terminal. The debugging device is used to access the controller service port in the vehicle through the port mapping based on the local proxy port when performing remote debugging via a local terminal.

9. The vehicle remote debugging system according to claim 8, characterized in that, The cloud server also includes: server terminal services; The server terminal service is used to deploy a specified terminal of the cloud server as the web terminal and share the debugging environment of the specified terminal.

10. The vehicle remote debugging system according to claim 8, characterized in that, The cloud server also includes: a server debugging tool client; The debugging device is used to access the server proxy port by calling the server debugging tool client through the web terminal, and to access the controller service port in the vehicle through the port mapping.

11. The vehicle remote debugging system according to claim 8, characterized in that, The debugging device also includes: a local debugging tool client; The debugging device is used to access the local proxy port by calling the local debugging tool client through the local terminal, and to access the controller service port in the vehicle through the port mapping.

12. A method for remote vehicle debugging, characterized in that, An application is made to a vehicle remote debugging system, the vehicle remote debugging system comprising: debugging equipment, a cloud server, and a vehicle; the debugging equipment includes at least: a local proxy port; the cloud server includes at least: a server proxy port and a cloud proxy service; the vehicle includes at least: a controller service port, a controller debugging tool service, and a vehicle-side proxy client; the method includes: Through the cloud server, the controller service port is mapped to the server proxy port, and the local proxy port is mapped to the server proxy port, thus forming a port mapping; Through the debugging device, the controller service port in the vehicle can be accessed via the port mapping based on the local proxy port or the server proxy port. Remote debugging of the vehicle is achieved by accessing the corresponding controller debugging tool service through the controller service port. After starting the vehicle-side agent client, a communication connection is established between the vehicle-side agent client and the cloud-side agent service. Based on the communication connection and the port mapping, a TCP / UDP traffic tunnel is established between the vehicle-side agent client and the cloud-side agent service to open the remote debugging channel. The TCP / UDP traffic of the controller service port and the server agent port is forwarded to each other according to the port mapping.

13. The vehicle remote debugging method according to claim 12, characterized in that, The step of accessing the controller service port in the vehicle via the debugging device, based on the local proxy port or the server proxy port through the port mapping, includes: In the case of remote debugging via a web terminal, the debugging device accesses the controller service port in the vehicle through port mapping based on the server proxy port; or... In the case of remote debugging via a local terminal, the debugging device accesses the controller service port in the vehicle through port mapping based on the local proxy port.

Images