Vehicle information transmission method and device, electronic equipment and storage medium

Abstract

The invention provides a vehicle information transmission method and device, electronic equipment and a storage medium, the method is applied to a vehicle-mounted remote information processing terminal TBOX end of a vehicle, and the TBOX end comprises a Web service unit and an edge computing unit; comprising the following steps: interacting with each electronic control unit of a vehicle through an in-vehicle bus protocol to obtain at least one piece of state data; processing the state data through the edge calculation unit to obtain target data; based on a target communication network and a Web protocol of the Web service unit, transmitting the target data to a Web end of a user so as to display the target data on an interactive interface of a browser of the Web end; the Web end at least comprises a vehicle-mounted display terminal of the vehicle. Through the method, the development cost can be reduced.

Description

Technical Field

[0001] This application relates to the field of data transmission technology, and more specifically, to a vehicle information transmission method, apparatus, electronic device, and storage medium. Background Technology

[0002] The vehicle's onboard telematics terminal (TBOX) is a core intelligent terminal device in the vehicle networking system. It is responsible for the vehicle's communication connection with the outside world. Common communication methods include 4G / 5G networks, Wi-Fi, and Bluetooth. In addition, it also includes GNSS, CAN modules, Ethernet, etc., to realize the TBOX's core external and internal communication functions.

[0003] Traditional TBOX information display is limited by its tightly coupled communication architecture with the vehicle's underlying bus protocol. This architecture requires any display content to be predefined as a static signal and hard-coded into the firmware of both parties. This results in the need for deep software modifications and integration tests across systems to add or change display content. Furthermore, the low-bandwidth, high-determinism bus design cannot support the transmission of complex data formats, so it can only achieve limited, fixed, and simple information presentation.

[0004] On the other hand, since the development teams for different in-vehicle display terminals are usually not the same, changes in the requirements for displaying TBOX information on different in-vehicle display terminals will increase development costs significantly.

[0005] Therefore, an improvement solution is needed. Summary of the Invention

[0006] In view of this, embodiments of this application provide a vehicle information transmission method, apparatus, electronic device, and storage medium, which help reduce development costs.

[0007] In a first aspect, embodiments of this application provide a vehicle information transmission method, the method being applied to a vehicle's onboard telematics terminal (TBOX), the TBOX including: a Web service unit and an edge computing unit; The method includes: The system interacts with the various electronic control units of the vehicle via the in-vehicle bus protocol to obtain at least one status data item. The edge computing unit processes the state data to obtain the target data. Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the user's Web client for display on the interactive interface of the browser on the Web client; wherein, the Web client includes at least: the vehicle's in-vehicle display terminal.

[0008] In one feasible implementation, the target communication network includes at least Ethernet; Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the user's Web client, including: Based on the Ethernet and the Web protocol of the Web service unit, the target data is transmitted to the Web client connected to the Ethernet.

[0009] In one feasible implementation, the target communication network includes at least one of 4G, 5G, and WIFI; Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the user's Web client, including: Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the Web cloud platform, so that the target data can be forwarded to the Web terminal connected to the target communication network through the Web cloud platform; the Web terminal also includes at least one of mobile terminal, tablet terminal and computer terminal.

[0010] In one feasible implementation, the Web protocol includes at least one of the following: The WebSocket protocol is used to establish WebSocket connections for real-time command delivery and status updates. The MQTT protocol is used to establish MQTT connections for periodic or event-triggered data reporting.

[0011] The method further includes: Monitor the network status of the target communication network at the TBOX terminal; When the network status indicators meet the preset high-speed transmission conditions, the target data is transmitted through the WebSocket connection; When the network status indicators do not meet the high-speed transmission conditions, the target data is transmitted through the MQTT connection.

[0012] In one feasible implementation, the method further includes: Obtain the control command generated by the Web client; the control command is generated after being triggered by the user's interactive interface of the Web client browser, and the control command is directly transmitted from the Web client to the TBOX client, or sent from the Web client to the Web cloud platform and then forwarded to the TBOX client by the Web cloud platform; The control commands are sent to the corresponding electronic control unit via the in-vehicle bus protocol. The status data includes at least: data used to characterize the execution result of the control command.

[0013] In one feasible implementation, the TBOX terminal further includes: An encryption unit is used to establish a two-way encrypted communication channel for data transmission.

[0014] In one feasible implementation, the state data is processed to obtain target data, including: The state data is preprocessed; The preprocessed data is analyzed to obtain the analysis results; Compress the preprocessed data; The compressed data and / or the analysis results are used as the target data to be output.

[0015] Secondly, this application also provides a vehicle information transmission device, which is mounted on the vehicle's onboard telematics terminal TBOX, the TBOX including: a Web service unit and an edge computing unit; The device includes: The data acquisition module is used to interact with various electronic control units of the vehicle via the in-vehicle bus protocol to obtain at least one status data item. The processing module is used to process the state data through the edge computing unit to obtain target data; A transmission module is used to transmit the target data to the user's web terminal based on the target communication network and the web protocol of the web service unit, so as to display it on the interactive interface of the browser on the web terminal; wherein the web terminal includes at least the vehicle's in-vehicle display terminal.

[0016] In one feasible implementation, the target communication network includes at least Ethernet; The transmission module is used to transmit the target data to the user's web client based on the target communication network and the Web protocol of the Web service unit, for the following purposes: Based on the Ethernet and the Web protocol of the Web service unit, the target data is transmitted to the Web client connected to the Ethernet.

[0017] In one feasible implementation, the target communication network includes at least one of 4G, 5G, and WIFI; The transmission module is used to transmit the target data to the user's web client based on the target communication network and the Web protocol of the Web service unit, for the following purposes: Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the Web cloud platform, so that the target data can be forwarded to the Web terminal connected to the target communication network through the Web cloud platform; the Web terminal also includes at least one of mobile terminal, tablet terminal and computer terminal.

[0018] In one feasible implementation, the Web protocol includes at least one of the following: The WebSocket protocol is used to establish WebSocket connections for real-time command delivery and status updates. The MQTT protocol is used to establish MQTT connections for periodic or event-triggered data reporting.

[0019] The device further includes: The detection module is used to monitor the network status of the target communication network at the TBOX terminal; A high-speed transmission module is used to transmit the target data through the WebSocket connection when the network status indicators meet the preset high-speed transmission conditions; A low-speed transmission module is used to transmit the target data through the MQTT connection when the network status indicators do not meet the high-speed transmission conditions.

[0020] In one feasible implementation, the device further includes: The instruction acquisition module is used to acquire control instructions generated by the Web client; the control instructions are generated after being triggered by the user's interactive interface in the Web client browser, and the control instructions are either directly transmitted from the Web client to the TBOX client, or sent from the Web client to the Web cloud platform and then forwarded to the TBOX client by the Web cloud platform; The instruction sending module is used to send the control instruction to the corresponding electronic control unit via the in-vehicle bus protocol; the status data includes at least: data characterizing the execution result of the control instruction.

[0021] In one feasible implementation, the TBOX terminal further includes: An encryption unit is used to establish a two-way encrypted communication channel for data transmission.

[0022] In one feasible implementation, the processing module is used to process the state data to obtain target data, for: The state data is preprocessed; The preprocessed data is analyzed to obtain the analysis results; Compress the preprocessed data; The compressed data and / or the analysis results are used as the target data to be output.

[0023] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the vehicle information transmission method as described in any one of the first aspects.

[0024] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the vehicle information transmission method as described in any one of the first aspects.

[0025] This application provides a vehicle information transmission method, device, electronic device, and storage medium applied to a TBOX terminal. After interacting with various electronic control units of the vehicle via the in-vehicle bus protocol, the TBOX terminal can obtain the vehicle's status data. Then, by setting up its own Web service unit, it transmits the status data (target data) processed by the edge node to the user's Web terminal via the Web protocol and the target communication network. That is, display is completed through Web technology, transforming the development model from "deeply coupled embedded integration of software and hardware" to "front-end and back-end separated Web application development," thereby eliminating the costs of cross-team coordination, protocol alignment, and joint firmware upgrades. This achieves lightweight and agile iteration of display functions, significantly reducing development costs.

[0026] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0027] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 A flowchart of a vehicle information transmission method provided in an embodiment of this application is shown.

[0029] Figure 2 A flowchart of another vehicle information transmission method provided in an embodiment of this application is shown.

[0030] Figure 3 A schematic diagram of the structure of a vehicle information transmission device provided in an embodiment of this application is shown.

[0031] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0032] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0033] The vehicle's onboard telematics terminal (TBOX) is a core intelligent terminal device in the vehicle networking system. It is responsible for the vehicle's communication connection with the outside world. Common communication methods include 4G / 5G networks, Wi-Fi, and Bluetooth. In addition, it also includes GNSS, CAN modules, Ethernet, etc., to realize the TBOX's core external and internal communication functions.

[0034] Traditional TBOX information display is limited by its tightly coupled communication architecture with the vehicle's underlying bus protocol. This architecture requires any display content to be predefined as a static signal and hard-coded into the firmware of both parties. This results in the need for deep software modifications and integration tests across systems to add or change display content. Furthermore, the low-bandwidth, high-determinism bus design cannot support the transmission of complex data formats, so it can only achieve limited, fixed, and simple information presentation.

[0035] On the other hand, since the development teams for different in-vehicle display terminals are usually not the same, changes in the requirements for displaying TBOX information on different in-vehicle display terminals will increase development costs significantly.

[0036] Based on this, embodiments of this application provide a vehicle information transmission method, apparatus, electronic device, and storage medium, which are described below through embodiments.

[0037] To facilitate understanding of this embodiment, a vehicle information transmission method disclosed in this application will first be described in detail. This method is applied to a vehicle-mounted telematics terminal (TBOX) of a vehicle, which includes a Web service unit and an edge computing unit. The following description, in conjunction with... Figure 1 The method, described in detail, includes the following steps: Step 101: Interact with each electronic control unit of the vehicle via the in-vehicle bus protocol to obtain at least one status data.

[0038] The in-vehicle bus protocol, also known as the CAN bus, is the "central nervous system" of a vehicle. It ensures stable and orderly data interaction between hundreds of electronic control units (ECUs) inside the vehicle through a highly reliable and real-time deterministic communication mechanism.

[0039] In other words, this mechanism ensures that TBOX can act as a "listener" of the system, acquiring real-time status data transmitted by various key electronic control units. For example, TBOX can reliably obtain real-time speed and torque data from the engine control unit, precise charge status and temperature from the battery management system, the open / closed status of all doors, windows, and locks from the body controller, and directly receive real-time pressure and temperature readings for each tire from the tire pressure monitoring module.

[0040] These data streams are broadcast on the CAN bus at millisecond intervals, enabling TBOX to synchronously form a unified view of the vehicle's comprehensive, real-time operating status, providing a reliable data foundation for its subsequent data processing and remote transmission.

[0041] Step 102: The state data is processed by the edge computing unit to obtain the target data.

[0042] The edge computing unit is used to inject edge computing capabilities into the TBOX terminal, thereby ensuring that the state data obtained from step 101 is reliable and stable.

[0043] For example, such as Figure 2 As shown, the edge computing unit can perform the following processing on the state data: Step 201: Preprocess the state data.

[0044] The preprocessing here includes, but is not limited to: Data cleaning includes filtering invalid data (such as outliers with fluctuations exceeding thresholds), removing duplicate data, and repairing missing values.

[0045] Encapsulate data into a standardized format, such as encapsulating data into a standardized Web API (RESTful format).

[0046] Step 202: Analyze the preprocessed data to obtain the analysis results.

[0047] This step utilizes the edge computing capabilities of the edge computing unit to perform local judgments, thereby automatically identifying special situations without cloud intervention. For example, it can obtain the analysis result "tire pressure is below 1.8 bar" through status data analysis.

[0048] Step 203: Compress the preprocessed data.

[0049] Data compression can reduce the amount of data transmitted and increase transmission speed. For example, 100 bytes of status data (such as CAN format) can be compressed into 20-word JSON format.

[0050] Step 204: Use the compressed data and / or the analysis results as the target data to be output.

[0051] The analysis results can be early warning information, prompts, or status information; there are no restrictions here. In a feasible implementation plan, the target data includes both compressed data and the analysis results of the data.

[0052] Step 103: Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the user's Web client for display on the interactive interface of the browser on the Web client; wherein, the Web client includes at least the vehicle's in-vehicle display terminal.

[0053] This step defines the final transmission and display mechanism for the processed target data to be presented to the user. Its core lies in building a standardized pathway from the vehicle-side data source to the user interface, based on a standardized Web technology stack.

[0054] The target communication network refers to any path capable of carrying IP data packets, which can take the form of an in-vehicle local area network (such as in-vehicle Ethernet) or a wide area network (such as a cellular network). Web protocols, on the other hand, refer to application-layer communication specifications based on TCP / IP, such as HTTP, HTTPS, WebSocket, or MQTT. Adopting these widely compatible standardized protocols aims to avoid the development constraints and integration costs associated with proprietary communication formats.

[0055] Here, "web terminal" refers to any smart terminal device with a browser runtime environment. Its physical location can be integrated inside a vehicle (such as an integrated infotainment system) or outside the vehicle (such as a user's mobile phone or personal computer). As long as the device can establish a network connection and run a browser, it can open web pages and thus become a data receiver.

[0056] Once the target data arrives at the web terminal via the web protocol and target communication network, the browser loads and executes the corresponding web application (such as a single-page application). This application is responsible for rendering the structured target data into visual graphical user interface elements, such as mapping battery power data to a progress bar or drawing location information on a map control. This interactive interface also provides user interaction capabilities, allowing users to trigger feedback commands to the vehicle via touch or click.

[0057] Specifically, the Web client includes at least the vehicle's in-vehicle display terminal, emphasizing the direct application value of this solution in in-vehicle scenarios. It indicates that the vehicle's own display screen can become a native terminal of this method through an embedded browser component. This essentially transforms the functional development of the in-vehicle display system from the traditional model relying on hard coupling of underlying signals to a front-end development model based on network API calls. When display requirements change, only Web page resources need to be iterated, without coordinating firmware updates for multiple embedded controllers, thus significantly improving the flexibility and cost-effectiveness of functional updates.

[0058] In summary, this step, by setting up a Web service unit on the TBOX, decouples vehicle data from various display interfaces. It ensures that edge-processed information can be securely and stably delivered to various display media inside or outside the vehicle in a low-latency, highly flexible manner, ultimately completing a closed loop of data transmission from vehicle data to user perception.

[0059] In one feasible implementation, the target communication network includes at least Ethernet.

[0060] At this point, step 103, based on the target communication network and the Web protocol of the Web service unit, transmits the target data to the user's Web client, including: Based on the Ethernet and the Web protocol of the Web service unit, the target data is transmitted to the Web client connected to the Ethernet.

[0061] Taking the Web terminal as an example of an in-vehicle display terminal, both the Web terminal and the TBOX terminal are located within the vehicle's internal network environment. They are typically physically connected via a high-speed in-vehicle communication network (such as Ethernet) and achieve network layer interoperability based on a unified TCP / IP protocol stack. Under this architecture, the "transmission based on the target communication network and Web protocol" described in step 103 can be specifically manifested as: establishing a direct data interaction channel between the TBOX and the in-vehicle display terminal via in-vehicle Ethernet and using standard Web application layer protocols such as HTTP or WebSocket.

[0062] This implementation offers dual advantages: First, it ensures the stability and real-time performance of data transmission. The in-vehicle Ethernet provides a high-bandwidth, low-latency, deterministic internal communication link, reliably carrying structured data streams processed by edge computing and originating from the TBOX. This ensures the low latency and high refresh rate requirements for information display within the cockpit, such as the smooth presentation of dynamic information like real-time vehicle speed and battery power.

[0063] Secondly, it achieves lightweight and standardized development of the display interface. The in-vehicle display terminal only needs to run a compatible browser kernel or web view component to load and render the web application from TBOX. This means that the development of the vehicle information interface will completely shift to a common web front-end technology stack (such as HTML5, CSS, and JavaScript). Any changes to the display content or additions to the function that conform to the design specifications only need to be completed by updating the web resources provided by the TBOX service, without the need for underlying, customized native application development or firmware upgrades for different vehicle models or different versions of in-vehicle display terminals. This significantly reduces the complexity and cost of continuous iteration of the in-vehicle human-machine interface and improves the agility of function deployment.

[0064] In summary, this embodiment clearly demonstrates the application of step 103 in the in-vehicle local area network scenario: by integrating the high-speed network hardware inside the vehicle with the general Web software protocol, it not only meets the stringent requirements of automotive-grade applications for communication performance, but also, by leveraging the cross-platform characteristics of Web technology, completely solves the core pain points of high development costs and difficult updates caused by the tight coupling of traditional in-vehicle display systems with specific hardware and underlying protocols.

[0065] In one feasible implementation, the target communication network includes cellular mobile networks (such as 4G or 5G) or wireless local area networks (such as Wi-Fi). These networks constitute the main channels for vehicles to access the wide area Internet.

[0066] At this point, step 103, based on the target communication network and the Web protocol of the Web service unit, transmits the target data to the user's Web client, including: Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the Web cloud platform, so that the target data can be forwarded to the Web terminal connected to the target communication network through the Web cloud platform; the Web terminal also includes at least one of mobile terminal, tablet terminal and computer terminal.

[0067] At this point, the TBOX first uploads the processed target data to a web cloud platform deployed on the internet, based on the selected communication network (e.g., 5G) and its integrated web service unit (using protocols such as HTTPS and WebSocket). Subsequently, the web cloud platform acts as a data hub and router, responsible for forwarding the received vehicle data via the same internet to other web clients that are currently connected to the platform through the network.

[0068] Examples of other web-based applications include, but are not limited to: in-vehicle display terminals (connected to the target communication network), users' personal mobile devices such as smartphones, tablets, and desktop computers. As long as these devices have internet access and run a modern browser, they can access the corresponding web applications provided by the cloud platform to receive and view vehicle status-related data in real time and perform possible remote interactions.

[0069] The key value of this implementation plan lies in its ability to overcome the limitations of physical space by leveraging the ubiquitous public mobile internet and a mature cloud service architecture, enabling remote access to vehicle data. Users do not need to be near the vehicle to securely and conveniently obtain vehicle information or send control commands through their everyday smart devices, greatly expanding the application scenarios and user experience boundaries of vehicle connectivity. Simultaneously, centralized data processing and forwarding in the cloud also facilitates value-added services such as multi-terminal synchronization, historical data storage and analysis.

[0070] In one feasible implementation, the Web protocol includes at least one of the following: The WebSocket protocol is used to establish WebSocket connections for real-time command issuance and status push; the MQTT protocol is used to establish MQTT connections for periodic or event-triggered data reporting.

[0071] That is, the Web protocol can specifically be one or a combination of WebSocket and MQTT protocols, which are optimized and adapted for different data interaction scenarios.

[0072] Among them, the WebSocket protocol is suitable for scenarios requiring low-latency, full-duplex, continuous communication. Based on this protocol, the TBOX can establish a persistent WebSocket connection with the communication peer (such as an in-vehicle display terminal or a web cloud platform). This connection acts as a dedicated, always-on channel, particularly suitable for real-time command delivery (such as a user-initiated remote door unlocking request) and instantaneous vehicle status updates (such as a suddenly triggered collision alarm), ensuring the immediacy of critical interactions. The MQTT protocol is a lightweight publish / subscribe messaging protocol designed for unstable network environments and limited bandwidth. It is suitable for non-real-time data transmission that requires reliable delivery. The TBOX can utilize the MQTT connection to periodically report the vehicle's routine status (such as location and speed every few minutes) or report data when specific events are triggered (such as reporting charging statistics after a charging cycle).

[0073] At this point, the method further includes: Monitor the network status of the target communication network on the TBOX terminal; when the network status indicators meet the preset high-speed transmission conditions, transmit the target data through the WebSocket connection; when the network status indicators do not meet the high-speed transmission conditions, transmit the target data through the MQTT connection.

[0074] To further optimize communication quality and resource utilization, this implementation plan may introduce a network state adaptive connection management mechanism. This mechanism continuously monitors the status indicators (such as network latency, packet loss rate, or signal strength) of the target communication network used by the TBOX.

[0075] In this solution, a service quality switching threshold (preset threshold) is set in advance.

[0076] When network status indicators are detected as good (e.g., network latency is below a preset threshold), it is considered that the preset high-speed transmission conditions are met, meaning the current network environment is deemed sufficient to support high real-time interaction. Therefore, WebSocket connection is preferred for transmitting target data. This ensures that users receive the fastest response experience under high-quality network conditions.

[0077] Conversely, when network status indicators deteriorate (e.g., network latency rises to or exceeds a preset threshold), it is considered that the preset high-speed transmission conditions are not met, meaning the current network may not be able to stably maintain the low-latency characteristics required for a WebSocket connection. To avoid command loss or response lag, the data transmission channel will be automatically switched to the more robust MQTT connection. Although real-time performance is slightly reduced, the MQTT protocol's retry and acknowledgment mechanisms better ensure the eventual reliable delivery of data in weak network environments.

[0078] This strategy of intelligently switching between WebSocket and MQTT protocols based on real-time network conditions essentially endows the vehicle's data communication module with dynamic "resilience." This allows for prioritizing the interactive experience when network conditions are favorable, and prioritizing communication reliability when network conditions are poor. In complex mobile network environments, it intelligently balances real-time performance and robustness, improving overall service availability and user experience.

[0079] It is worth noting that by using WebSocket connections and edge computing modules to process state data, the problem of excessively high communication latency between the web client and the TBOX client can be solved.

[0080] In one feasible implementation, the method further includes: The system acquires control commands generated by the web client; these commands are generated after being triggered by the user's interactive interface in the web client's browser, and are either directly transmitted from the web client to the TBOX terminal, or sent from the web client to a web cloud platform and then forwarded to the TBOX terminal via the web cloud platform; the system sends the control commands to the corresponding electronic control unit via the in-vehicle bus protocol; the status data includes at least: data used to characterize the execution result of the control commands.

[0081] First, the control commands generated by the web application are acquired. These commands originate from user interactions such as touch and clicks within the browser interface of their device (e.g., an in-vehicle screen or a mobile phone). After receiving the user input, the interface converts it into machine-readable control commands with clear semantics (e.g., "turn on the air conditioning" or "unlock the car door").

[0082] Regarding the transmission path of the command, this implementation plan supports two typical modes. The first is the direct transmission mode, where the Web client sends the command directly to the TBOX terminal via the established in-vehicle network connection (such as Ethernet). The second is the cloud relay mode, where the Web client first sends the command to a remote Web cloud platform. The Web cloud platform performs necessary security authentication and protocol adaptation before forwarding the command to the target vehicle's TBOX terminal via a remote link such as a cellular network. These two path designs cater to the different scenario requirements of both in-vehicle local control and external remote control.

[0083] Upon receiving control commands, the TBOX plays a crucial role as a "protocol translator" and "command distributor." Using the in-vehicle bus protocol, it translates and encapsulates the high-level, standardized control commands into a specific bus message format that the target electronic control unit (ECU) can accurately recognize. The message is then sent to the corresponding ECU within the vehicle. For example, a command to "adjust the seat" would be translated into a dedicated CAN message sent to the seat control module.

[0084] Finally, to form an operational loop and provide clear feedback to the user, the status data continuously collected by the TBOX terminal must include at least data characterizing the execution result of the control command. This means that the status data stream subsequently reported or provided by the TBOX terminal through step 103 will explicitly include result information corresponding to the control action previously initiated by the user. For example, after the user sends the "lock door" command, the status data acquired and reported by the TBOX terminal will include the field "Door lock status: locked". This result data will ultimately be returned and displayed on the user's interactive interface via the same web channel, allowing the user to intuitively confirm that their command has been successfully executed by the vehicle, completing the full interaction cycle from "user-initiated control" to "user confirmation of result".

[0085] In one feasible implementation, the TBOX terminal further includes: An encryption unit is used to establish a two-way encrypted communication channel for data transmission.

[0086] The two-way encrypted communication channel here refers to two aspects: firstly, the channel through which the TBOX communicates directly with in-vehicle web terminals such as in-vehicle display terminals (or mobile terminals connected to the vehicle's Ethernet) via the in-vehicle Ethernet; secondly, the communication channel between the TBOX and the Web cloud platform via a remote network connection (such as 4G).

[0087] Encryption technologies such as TLS 1.3 or the national standard SM4 algorithm can be used here to encrypt transmitted data and prevent the target data from being stolen or tampered with.

[0088] Furthermore, in addition to establishing a two-way encrypted communication channel, the unique device ID built into the TBOX and the user's token can be used for additional dual authentication to prevent unauthorized access. When sensitive operations are involved, secondary verification (SMS verification code, and / or facial recognition) can also be introduced.

[0089] It is important to note that in this embodiment, due to the diverse types of web clients targeted, their usage scenarios, screen characteristics, and user interaction requirements vary significantly. Therefore, a scenario adaptation mechanism is introduced during the process of sending the processed target data to different web clients. The core objective of this process is to dynamically adjust the output content, structure, and even interface presentation of the data based on the specific terminal and its context to provide the optimal user experience. This adaptation logic can be deployed on the TBOX, which performs differentiated data preprocessing for different terminals according to preset rules; more typically, it is deployed on a web cloud platform, which acts as the data hub, and its powerful business logic capabilities handle the unified execution. The following description uses deployment on a web cloud platform as an example: Here, the core logic of scenario adaptation is to identify the source of the request—including terminal type (such as mobile phone, personal computer, in-vehicle screen or home screen) and user scenario (such as driving, parking and viewing or remote centralized management)—and dynamically adjust the data output strategy accordingly.

[0090] Taking several typical terminals as examples: For the mobile web interface, the core scenario is for users to temporarily view or urgently control information via mobile networks while on the go. Therefore, it outputs highly lightweight and core data, such as the current basic vehicle status, urgent emergency alerts, and the most commonly used remote control functions. The corresponding user interface is also specifically optimized for touch operation and small screen sizes on mobile devices to ensure fast loading and convenient operation.

[0091] For the PC management terminal, the core scenario is for fleet administrators or advanced users to perform data analysis, historical data review, and batch operations. In this case, it outputs comprehensive and detailed data, potentially including historical trajectory curves over long periods, detailed fault log statistics, in-depth battery health reports, etc., and supports complex data filtering, exporting, and batch command issuance to multiple vehicles. The interface design focuses on information density and operational efficiency, adapting to multi-window operation on large screens.

[0092] For in-vehicle web applications running on the vehicle's central control screen, the primary principle is to ensure driving safety. In driving scenarios, information will be strictly filtered, displaying only statuses highly relevant to driving safety or those the user needs to know immediately, such as critical fault alerts and ongoing OTA upgrade progress. The interface will adopt a minimalist design, using large fonts, large icons, and concise text to ensure the driver can obtain information in a very short glance, minimizing distractions from driving.

[0093] For home web-based applications (such as smart TVs), the scenario involves users checking vehicle status at home. The system will output information suitable for viewing from a distance and for casual interaction, such as dynamic visualization of the vehicle charging process and maintenance reminders. It can also support voice control, leveraging the characteristics of large-screen devices.

[0094] To achieve the aforementioned flexible and efficient scenario-based services and support the stability of massive concurrent access from users and vehicles, this solution's web cloud platform can be built and deployed using a microservice architecture. This architecture allows the cloud platform to break down different functions into independent service units, thereby possessing elastic scaling capabilities. For example, during peak travel times, when remote vehicle control requests surge, the number of service nodes handling this service can be automatically increased to avoid service congestion and ensure smooth user operation. Simultaneously, by deploying service nodes in different geographical regions (such as East China and North China), users can access the nearest node, effectively reducing network access latency and improving overall response speed.

[0095] In summary, while the multi-terminal web display serves as a unified user interaction portal, all relying on standardized APIs provided by the cloud platform to acquire data and accessing it through a browser without requiring the installation of native applications, the front-end and back-end collaborative scenario adaptation mechanism enables it to provide differentiated and optimized information services and control capabilities for various scenarios, from mobile individual users to professional management users, and from in-vehicle to out-of-vehicle environments. This demonstrates the high flexibility and practicality of this solution in meeting complex and diverse practical needs within a unified technical architecture.

[0096] Based on the same technical concept, this application embodiment also provides a vehicle information transmission device, which is mounted on the vehicle's onboard telematics terminal TBOX, the TBOX including: a Web service unit and an edge computing unit.

[0097] like Figure 3 As shown, the device includes: The data acquisition module 301 is used to interact with each electronic control unit of the vehicle via the in-vehicle bus protocol to obtain at least one status data.

[0098] The processing module 302 is used to process the state data through the edge computing unit to obtain the target data.

[0099] The transmission module 303 is used to transmit the target data to the user's web terminal based on the target communication network and the web protocol of the web service unit, so as to display it on the interactive interface of the browser on the web terminal; wherein, the web terminal includes at least the vehicle's in-vehicle display terminal.

[0100] In one feasible implementation, the target communication network includes at least Ethernet.

[0101] The transmission module is used to transmit the target data to the user's web client based on the target communication network and the Web protocol of the Web service unit, for the following purposes: Based on the Ethernet and the Web protocol of the Web service unit, the target data is transmitted to the Web client connected to the Ethernet.

[0102] In one feasible implementation, the target communication network includes at least one of 4G, 5G, and WIFI.

[0103] The transmission module is used to transmit the target data to the user's web client based on the target communication network and the Web protocol of the Web service unit, for the following purposes: Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the Web cloud platform, so that the target data can be forwarded to the Web terminal connected to the target communication network through the Web cloud platform; the Web terminal also includes at least one of mobile terminal, tablet terminal and computer terminal.

[0104] In one feasible implementation, the Web protocol includes at least one of the following: The WebSocket protocol is used to establish WebSocket connections for real-time command delivery and status updates.

[0105] The MQTT protocol is used to establish MQTT connections for periodic or event-triggered data reporting.

[0106] The device further includes: The detection module is used to monitor the network status of the target communication network at the TBOX terminal.

[0107] A high-speed transmission module is used to transmit the target data through the WebSocket connection when the network status indicators meet the preset high-speed transmission conditions.

[0108] A low-speed transmission module is used to transmit the target data through the MQTT connection when the network status indicators do not meet the high-speed transmission conditions.

[0109] In one feasible implementation, the device further includes: The instruction acquisition module is used to acquire control instructions generated by the Web client; the control instructions are generated after being triggered by the user's interactive interface in the Web client browser, and the control instructions are either directly transmitted from the Web client to the TBOX client, or sent from the Web client to the Web cloud platform and then forwarded to the TBOX client by the Web cloud platform.

[0110] The instruction sending module is used to send the control instruction to the corresponding electronic control unit via the in-vehicle bus protocol; the status data includes at least: data characterizing the execution result of the control instruction.

[0111] In one feasible implementation, the TBOX terminal further includes: An encryption unit is used to establish a two-way encrypted communication channel for data transmission.

[0112] In one feasible implementation, the processing module is used to process the state data to obtain target data, for: The state data is preprocessed.

[0113] The preprocessed data is analyzed to obtain the analysis results.

[0114] The preprocessed data is compressed.

[0115] The compressed data and / or the analysis results are used as the target data to be output.

[0116] Figure 4 A schematic diagram of an electronic device provided in this application embodiment includes: a processor 401, a storage medium 402, and a bus 403. The storage medium 402 stores machine-readable instructions executable by the processor 401. When the electronic device runs the vehicle information transmission method as described in the embodiment, the processor 401 communicates with the storage medium 402 via the bus 403, and the processor 401 executes the machine-readable instructions to perform the steps as described in the embodiment.

[0117] In this embodiment, the storage medium 402 may also execute other machine-readable instructions to perform other methods as described in the embodiment. For details on the specific execution steps and principles, please refer to the description of the embodiment, which will not be repeated here.

[0118] This application also provides a computer-readable storage medium storing a computer program that is executed by a processor to perform the steps as described in the embodiments.

[0119] In this embodiment, the computer program, when run by the processor, can also execute other machine-readable instructions to perform other methods as described in the embodiments. For details on the specific execution steps and principles, please refer to the description of the embodiments, which will not be repeated here.

[0120] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the coupling or direct coupling or communication connection shown or discussed may be through some communication interface; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0121] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0122] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0123] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0124] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for transmitting vehicle information, characterized in that, The method is applied to the vehicle's onboard telematics terminal TBOX, which includes a Web service unit and an edge computing unit. The method includes: The system interacts with the various electronic control units of the vehicle via the in-vehicle bus protocol to obtain at least one status data item. The edge computing unit processes the state data to obtain the target data. Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the user's Web client for display on the interactive interface of the browser on the Web client; wherein, the Web client includes at least: the vehicle's in-vehicle display terminal.

2. The method according to claim 1, characterized in that, The target communication network includes at least Ethernet; Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the user's Web client, including: Based on the Ethernet and the Web protocol of the Web service unit, the target data is transmitted to the Web client connected to the Ethernet.

3. The method according to claim 1, characterized in that, The target communication network includes at least one of 4G, 5G, and WIFI; Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the user's Web client, including: Based on the target communication network and the Web protocol of the Web service unit, the target data is transmitted to the Web cloud platform, so that the target data can be forwarded to the Web terminal connected to the target communication network through the Web cloud platform; the Web terminal also includes at least one of mobile terminal, tablet terminal and computer terminal.

4. The method according to claim 1, characterized in that, The Web protocol includes at least one of the following: The WebSocket protocol is used to establish WebSocket connections for real-time command delivery and status updates. The MQTT protocol is used to establish MQTT connections for periodic or event-triggered data reporting. The method further includes: Monitor the network status of the target communication network at the TBOX terminal; When the network status indicators meet the preset high-speed transmission conditions, the target data is transmitted through the WebSocket connection; When the network status indicators do not meet the high-speed transmission conditions, the target data is transmitted through the MQTT connection.

5. The method according to claim 1, characterized in that, The method further includes: Obtain the control command generated by the Web client; the control command is generated after being triggered by the user's interactive interface of the Web client browser, and the control command is directly transmitted from the Web client to the TBOX client, or sent from the Web client to the Web cloud platform and then forwarded to the TBOX client by the Web cloud platform; The control commands are sent to the corresponding electronic control unit via the in-vehicle bus protocol. The status data includes at least: data used to characterize the execution result of the control command.

6. The method according to claim 1, characterized in that, The TBOX terminal also includes: An encryption unit is used to establish a two-way encrypted communication channel for data transmission.

7. The method according to claim 1, characterized in that, The state data is processed to obtain target data, including: The state data is preprocessed; The preprocessed data is analyzed to obtain the analysis results; Compress the preprocessed data; The compressed data and / or the analysis results are used as the target data to be output.

8. A vehicle information transmission device, characterized in that, The device is mounted on the vehicle's onboard telematics terminal TBOX, which includes a Web service unit and an edge computing unit. The device includes: The data acquisition module is used to interact with various electronic control units of the vehicle via the in-vehicle bus protocol to obtain at least one status data item. The processing module is used to process the state data through the edge computing unit to obtain target data; A transmission module is used to transmit the target data to the user's web terminal based on the target communication network and the web protocol of the web service unit, so as to display it on the interactive interface of the browser on the web terminal; wherein the web terminal includes at least the vehicle's in-vehicle display terminal.

9. An electronic device, characterized in that, include: The device includes a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the vehicle information transmission 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 a computer program that, when executed by a processor, performs the steps of the vehicle information transmission method as described in any one of claims 1 to 7.

Images