Data transmission method and device and medium

Abstract

The invention provides a data transmission method and device and a medium, and relates to the technical field of data transmission, and the data transmission method is applied to a vehicle end, and comprises the steps: obtaining a controller area network (CAN) signal collection template, and the CAN signal collection template is determined according to a collection service; and performing CAN data acquisition on the vehicle according to the CAN signal acquisition template and uploading the CAN data to the cloud platform. According to the invention, the bandwidth and storage occupation can be obviously reduced, and the problems of limited computing power, limited storage space, limited network bandwidth and the like are effectively relieved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data transmission, and in particular to a data transmission method, device and medium. BACKGROUND

[0002] With the rapid development of new energy vehicle technology, vehicle communication technology plays an increasingly important role in vehicle systems. As a widely used serial communication protocol in the automotive field, CAN (Controller Area Network) bus has become a key infrastructure for realizing data interaction between various electronic control units in the vehicle. In particular, in new energy vehicles, CAN bus not only serves basic communication functions, but also plays a crucial role in vehicle data collection, transmission and analysis.

[0003] Under the background of continuous evolution of Internet of Vehicles technology, new energy vehicles have higher requirements for vehicle data collection and uploading. These data are not only used for real-time vehicle state monitoring and fault diagnosis, but also support remote control, intelligent driving and big data analysis in various application scenarios. Therefore, vehicle data collection requirements are diverse, and vehicle terminals may face problems such as limited computing power, tight storage space and limited network bandwidth, which pose higher requirements on data collection. SUMMARY

[0004] Embodiments of the present application provide a data transmission method, device and medium to solve the problem that the prior art can meet the diversity of data collection requirements and alleviate problems such as limited computing power, tight storage space and limited network bandwidth.

[0005] In a first aspect, the present application provides a data transmission method applied to a vehicle end, the method comprising:

[0006] obtaining a CAN (Controller Area Network) signal collection template, the CAN signal collection template being determined according to a collection service;

[0007] collecting CAN data from the vehicle according to the CAN signal collection template and uploading the CAN data to a cloud platform.

[0008] In some embodiments of the present application, the CAN signal collection template includes at least service information, and the service information includes a service identifier and a signal list required by the service.

[0009] In some embodiments of the present application, the CAN signal collection template further includes data upload parameters, and the data upload parameters include at least one of a data upload period, an upload topic, an upload channel, a signal type or a QoS (Quality of Service) level;

[0010] After collecting the CAN data from the vehicle according to the CAN signal collection template, the method further comprises:

[0011] The plurality of CAN data is packaged according to the data uploading parameter to obtain a data packet, and the data packet is uploaded to the cloud platform according to the data uploading parameter.

[0012] In some embodiments of the present application, the data packet is uploaded to the cloud platform according to the data uploading parameter, including:

[0013] A target channel is determined from the plurality of data uploading channels according to the data uploading parameter, and the uploading channel indicates the target channel;

[0014] The data packet is uploaded to the cloud platform through the target channel.

[0015] In some embodiments of the present application, the CAN signal acquisition template further includes data compression information, and the data compression information includes at least one of a compression type, a compression level and a compression threshold;

[0016] After the CAN data of the vehicle is collected according to the CAN signal acquisition template, the method further includes:

[0017] The CAN data is compressed according to the data compression information.

[0018] In some embodiments of the present application, the data packet is uploaded to the cloud platform according to the data uploading parameter, including:

[0019] The data packet is error detected and / or retransmitted according to the QoS level.

[0020] In some embodiments of the present application, the data packet includes a relative timestamp and an absolute timestamp.

[0021] The CAN data of the vehicle is collected according to the CAN signal acquisition template, including:

[0022] During the vehicle-side initialization process, a plurality of frames of CAN data is recorded according to the relative timestamp.

[0023] After the initialization of the vehicle side is completed, a plurality of frames of CAN data is recorded according to the absolute timestamp.

[0024] In a second aspect, the present application also provides a data transmission method, applied to a cloud platform, including:

[0025] The controller area network (CAN) data from the vehicle side is received, the CAN data is collected by the vehicle side according to a CAN signal acquisition template, and the CAN signal acquisition template is determined according to a collection service.

[0026] In some embodiments of the present application, the CAN data from the vehicle side is received, including:

[0027] receive compressed CAN data, the compressed CAN data is obtained by the vehicle end according to data compression information, the data compression information includes at least one of a compression type, a compression level or a compression threshold;

[0028] decompress the compressed CAN data according to the data compression information.

[0029] In some embodiments of the present application, the CAN data includes an absolute timestamp and a relative timestamp, and the CAN data from the vehicle end is received, including:

[0030] receive a data packet, the data packet is obtained by the vehicle end according to data upload parameters, the data upload parameters include at least one of a data upload period, an upload topic, an upload channel, a signal type or a quality of service (QoS) level;

[0031] obtain CAN data corresponding to the service from the data packet according to the absolute timestamp and the relative timestamp.

[0032] In a third aspect, the present application also provides a data transmission device, applied to a vehicle end, the device comprising:

[0033] a template acquisition module, configured to acquire a controller area network (CAN) signal acquisition template, the CAN signal acquisition template being determined according to an acquisition service;

[0034] an acquisition and upload module, configured to acquire CAN data of the vehicle according to the CAN signal acquisition template and upload the CAN data to a cloud platform.

[0035] In a fourth aspect, the present application also provides a data transmission device, applied to a cloud platform, the device comprising:

[0036] a data receiving module, configured to receive controller area network (CAN) data from a vehicle end, the CAN data being acquired by the vehicle end according to a CAN signal acquisition template, the CAN signal acquisition template being determined according to an acquisition service.

[0037] In a fifth aspect, the present application also provides a storage medium, the storage medium storing a plurality of instructions, the instructions being adapted to be loaded by a processor to execute the data transmission method provided in the first aspect or the second aspect.

[0038] In a sixth aspect, the present application also provides a vehicle, comprising the data transmission device provided in the third aspect.

[0039] In a seventh aspect, the present application also provides a cloud platform, comprising the data transmission device provided in the fourth aspect.

[0040] In an eighth aspect, the present application also provides a computer program product comprising a computer program, which is loaded by a processor to execute the data transmission method provided in the first aspect or the second aspect.

[0041] The data transmission method, device and medium provided by the embodiments of the present application, wherein the data transmission method collects and uploads CAN data of the vehicle through a CAN signal collection template, the CAN signal collection template is set based on actual business requirements, different CAN signal collection templates can meet different data collection requirements, and the flexibility and adaptability of CAN data collection are improved. In addition, since the CAN signal collection templates corresponding to different businesses are different, the vehicle terminal only acquires signal data related to the current business when performing the collection task, avoiding indiscriminate collection of full-amount CAN signals, which can significantly reduce bandwidth and storage occupation, and effectively alleviate problems such as limited computing power, tight storage space, and limited network bandwidth. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0043] Figure 1 is a flowchart of the data transmission method applied to the vehicle terminal provided by some embodiments of the present application;

[0044] Figure 2 is a flowchart of the data transmission method applied to the cloud platform provided by some embodiments of the present application;

[0045] Figure 3 is a structural diagram of the data transmission system provided by some embodiments of the present application;

[0046] Figure 4 is a business segment diagram provided by some embodiments of the present application;

[0047] Figure 5 is a structural diagram of the data transmission device applied to the vehicle terminal provided by some embodiments of the present application;

[0048] Figure 6 is a structural diagram of the data transmission device applied to the cloud platform provided by some embodiments of the present application. DETAILED DESCRIPTION

[0049] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without making creative efforts are within the scope of protection of this application.

[0050] In the description of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more features. In the description of this application, "plurality" means two or more, unless otherwise specifically defined.

[0051] “A and / or B” includes the following three combinations: A only, B only, and a combination of A and B.

[0052] The use of "suitable for" or "configured to" in this application is intended to be open and inclusive language, and does not exclude devices that are adapted or configured to perform additional tasks or steps. In addition, the use of "based on" is intended to be open and inclusive, as a process, step, calculation, or other action that is "based on" one or more conditions or values ​​may, in practice, be based on additional conditions or values ​​beyond these.

[0053] In this application, the word "exemplary" is used to mean "serving as an example, illustration, or illustration." Any embodiment described in this application as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The following description is given to enable any person skilled in the art to implement and use the present application. In the following description, details are listed for the purpose of explanation. It should be understood that one of ordinary skill in the art can recognize that the present application can be implemented without using these specific details. In other instances, well-known structures and processes are not elaborated in detail to avoid obscuring the description of the present application with unnecessary details. Therefore, the present application is not intended to be limited to the embodiments shown, but is consistent with the widest scope consistent with the principles and features disclosed in this application.

[0054] Currently, vehicle data collection and uploading needs to meet the following core requirements:

[0055] First, data collection requirements are diverse. Different functional modules and application scenarios have varying requirements for data collection frequency and timeliness. For example, battery management systems require high-frequency data collection of battery voltage, current, temperature, and other parameters to ensure safety; whereas scenarios like remote control prioritize low latency and stable data transmission.

[0056] Secondly, the resource-constrained problem needs to be solved. The vehicle terminal of new energy vehicles usually faces problems such as limited computing power, tight storage space, and limited network bandwidth, which puts higher requirements on the efficiency and strategy of data collection and uploading.

[0057] However, the prior art still has many deficiencies in data collection and uploading:

[0058] The fixed configuration of the signal collection strategy leads to insufficient flexibility: the traditional scheme generally uses a hard-coded method to statically configure the collection range and collection frequency of the CAN signal, and any change needs to be implemented through OTA (Over-The-Air) upgrade of the vehicle terminal software. This method not only has high maintenance cost and complex operation, but also easily introduces software update risks, limiting the adaptability and expansion capability of the system. In the face of different application scenarios or sudden demands, this scheme is difficult to quickly respond and adjust, seriously restricting the flexible deployment capability of the system.

[0059] The lack of dynamic collection strategy leads to prominent problems of data redundancy and resource waste: most current schemes use full-quantity collection and fixed-period uploading mechanism, which cannot dynamically adjust the collection period and uploading frequency according to the importance of the business or the running state, resulting in a large amount of redundant data being uploaded without discrimination. This not only occupies valuable bandwidth resources, but also increases the backend storage and computing pressure, causing low overall resource utilization of the system, poor responsiveness, insufficient real-time performance, and inability to meet business scenarios (such as remote fault diagnosis, real-time control, etc.) that require high timeliness and efficiency.

[0060] The data structure design lacks optimization, and the transmission efficiency is low: the existing data uploading mechanism generally lacks compression and encoding optimization strategies, resulting in large volume of uploaded data, occupying a large amount of network traffic and storage space. At the same time, the CAN message is often traversed in cross-byte form to obtain values in the server analysis process through Java language, and some systems even need to call the underlying C++ library through JNI to extract data, which not only has low efficiency, but also seriously occupies server resources, affecting the overall performance and response speed of the system.

[0061] The link management mechanism is imperfect and the reliability is insufficient: the existing system mostly uses a single channel for data uploading, and the core business and non-core business are not effectively isolated, all data are transmitted through the same MQ (Message Queue) connection, lacking necessary QoS (Quality of Service) guarantee mechanism. In the case of network anomalies, data congestion, etc., data loss, delay, etc. are prone to occur, which affects the stability and user experience of the system, and may even cause abnormal response of critical business (such as remote control), increasing the system failure rate.

[0062] In summary, there is an urgent need for a data collection method that can achieve dynamic adjustment, efficient use of resources, and multi-channel data management capability, and meet the diversity of data collection needs.

[0063] Therefore, the embodiments of the present application provide a data transmission method, device and medium, wherein the data transmission method collects and uploads CAN data of a vehicle through a CAN signal collection template set based on actual business needs. Different CAN signal collection templates can meet different data collection needs, improving the flexibility and adaptability of CAN data collection. In addition, since the CAN signal collection templates corresponding to different businesses are different, the vehicle end only obtains signal data related to the current business when performing the collection task, avoiding indiscriminate collection of full-quantity CAN signals, which can significantly reduce bandwidth and storage occupation, effectively alleviate the problems of limited computing power, tight storage space, and limited network bandwidth, and thus can solve at least part of the above technical problems.

[0064] In one aspect, the embodiments of the present application provide a data transmission method, which is applied to a vehicle end and in communication connection with a cloud platform, as shown in Figure 1 The data transmission method applied to the vehicle end includes the following steps:

[0065] S101, obtaining a controller area network (CAN) signal collection template.

[0066] The CAN signal collection template is determined according to a collection business. The collection business refers to a set of data collection and processing tasks involved in a vehicle under a certain specific operating state or functional requirement. It is usually driven by one or more specific business objectives, such as remote monitoring, battery state analysis, fault diagnosis, driving behavior evaluation, etc. Each business scenario corresponds to a set of signals to be collected, collection frequency, upload rules, communication link, etc. For example, if data related to battery safety monitoring business needs to be collected, the CAN signal focuses on battery temperature, voltage, current, insulation state, and balance state, and the upload channel uses a data acquisition channel. If data related to fault diagnosis business needs to be collected, the CAN signal focuses on sensor values for monitoring whether a device has failed, diagnostic fault codes, electronic control unit status, etc., and the upload channel uses a diagnostic channel. Based on this, the CAN signal collection template is set based on the specific collection business, and the required CAN signal set is flexibly configured according to the differentiated needs of vehicle state monitoring, fault diagnosis, and function triggering in different business scenarios. Therefore, each collection business corresponds to an independent CAN signal collection template, so that the vehicle end can call the appropriate collection strategy under different business scenarios, realize customized and refined vehicle data collection and upload, avoid redundant signal processing and resource waste, and improve the overall performance and business adaptability of the system.

[0067] In some examples, the CAN signal collection template is configured and issued to the vehicle end by the management platform. The CAN signal collection template can be automatically configured according to actual business requirements, or configured by manual configuration. The CAN signal collection template at least includes business type information. The management platform can periodically issue the CAN signal collection template to the vehicle end, or issue the CAN signal collection template to the vehicle end according to a specific triggering mechanism (such as the platform detecting vehicle version upgrade, vehicle end strategy failure, business strategy update, fault diagnosis command issuance, etc.).

[0068] S102, collecting CAN data of the vehicle according to the CAN signal collection template and uploading to the cloud platform.

[0069] In some examples, the CAN signals in the vehicle are collected according to the CAN signal collection template. The collected CAN data corresponds to the business scenario, and the CAN data of different business scenarios contains different signals. The CAN data of multiple same businesses can be packaged and uploaded to the cloud platform according to the business type; or when the collection parameters between businesses are not completely consistent, or some signals have special transmission requirements (such as delay sensitivity or high reliability requirement), the data corresponding to different businesses can be encapsulated and uploaded independently.

[0070] It can be understood that the vehicle end can simultaneously collect CAN data of multiple different businesses according to the received multiple CAN signal collection templates, or sequentially collect CAN data of each business according to the business priority corresponding to the CAN signal collection template, etc., which is not limited.

[0071] The data transmission method provided by the embodiment of the application collects and uploads CAN data of the vehicle through the CAN signal collection template. The CAN signal collection template is set based on actual business requirements. Different CAN signal collection templates can meet different data collection requirements, and improve the flexibility and adaptability of CAN data collection. In addition, since the CAN signal collection templates corresponding to different businesses are different, the vehicle end only obtains signal data related to the current business when performing the collection task, avoiding indiscriminate collection of full-amount CAN signals, which can significantly reduce bandwidth and storage occupation, and effectively alleviate problems such as limited computing power, tight storage space, and limited network bandwidth.

[0072] In some embodiments of the application, the CAN signal collection template at least includes business information, and the business information includes a business identifier and a signal list required by the business.

[0073] In some examples, the CAN signal collection template mainly includes a business-level signal collection configuration field BizSignal, a CAN message collection configuration field CANSetting, and a signal collection item setting field SignalSetting.

[0074] The service level signal collection configuration field is used to indicate a specific service scenario, which can be remote monitoring, battery safety, driving behavior identification, etc. In the service level signal collection configuration field, the service identification bizld, signal collection and upload period rate, signal ID list signals required by the service, signal upload topic topic, specified MQ channel mqUrl (i.e., upload channel) used for signal upload, signal data collection type dataType, signal collection trigger condition trigger, trigger duration keepTime, quality of service QoS level, etc. can be included.

[0075] The service identification bizld is used to uniquely identify the service scenario to which the current CAN signal collection template belongs.

[0076] The signal collection and upload period rate is used to control the time interval of signal sampling, with the unit being milliseconds (ms).

[0077] The vehicle end matches and obtains the corresponding CAN signal from the CANSetting according to the signal ID list signals required by the current service.

[0078] The signal upload topic topic is used to indicate the topic path in the MQ protocol, which is used to guide the vehicle end to select the correct message channel to upload data.

[0079] The specified MQ channel mqUrl value used for signal upload is different, and the indicated channel is different. Illustratively, when the mqUrl value is 1, the data acquisition channel can be indicated; when the mqUrl value is 2, the vehicle control channel can be indicated. By setting mqUrl, multi-service data link separation and scheduling are achieved.

[0080] Different signal data collection types dataType correspond to different signal collection frequencies. Illustratively, when dataType is 1, it indicates that the signal is changed and uploaded (i.e., only value change upload); when dataType is 2, it indicates that the signal is snapshot uploaded (i.e., periodically upload full data); when dataType is 3, it indicates process data (i.e., upload in combination with event context).

[0081] The signal collection trigger condition trigger, such as state change, specific command, etc., is used to control the start of data collection when the trigger condition is met.

[0082] The trigger duration keepTime is the minimum duration that data collection should last after the trigger condition is met, which can be in seconds (s).

[0083] The quality of service (QoS) level can control the reliability of the message during transmission on the network. Illustratively, when the set QoS level is 0, it means that the message only needs to be sent once, and the cloud platform does not need to reply to the confirmation of receiving the message, and if the message is lost, it will not be retried. When the QoS level is 1, it indicates that the message is transmitted at least once in the network, and the message is ensured to be delivered through the confirmation mechanism, and if the cloud platform does not receive the confirmation, it will be repeatedly sent, and the cloud platform may therefore repeatedly receive the message. When the QoS level is 2, it indicates that the message is ensured to be received only once through a complex handshake protocol.

[0084] The CAN message collection configuration field CANSetting includes a CAN frame ID, a physical channel number channel, a data byte sequence endian, a length msgLength of a CAN message data field, and the like.

[0085] The CAN frame ID is used to uniquely identify a CAN message. The data byte sequence endian is false, indicating the big end (Motorola) of the data; and the data byte sequence endian is true, indicating the small end (Intel). The signal collection item setting structure SignalSetting is used to describe the value taking manner and upload logic of a signal in the CAN message, and includes a signal ID, a starting bit start of the signal in the message, an effective bit length or offset length bigLength of the signal, a value change upload threshold range, a priority level level of the signal, and the like.

[0086] The starting bit start of the signal in the message is used to locate the position of the signal data. The effective bit length or offset length bigLength of the signal is used for data analysis. When the value change upload threshold range is set to 1, it means that the signal is uploaded as long as there is a change; and if it is set to other values, the signal is uploaded only when the absolute difference between the current value and the last value is greater than the range. The priority level level of the signal is used for business side processing, filtering or alarming according to the level, illustratively, if the level is 0, it indicates that the current signal is a key signal with the highest priority; and if the level is 1, it indicates that the current signal is a secondary signal.

[0087] The data transmission method provided by the embodiment of the application includes multiple types of business identification, data upload period, required signal list of the business, upload topic, upload channel, signal type, trigger condition, trigger duration or quality of service (QoS) level. The business identification and the required signal list of the business are used to indicate that the vehicle side currently collects the CAN data related to the business, and the collection and upload of redundant signals are reduced. The businesses corresponding to different CAN signal collection templates are different, the vehicle side collects the CAN data corresponding to different businesses according to different CAN signal collection templates, and the multi-business data isolation can be realized.

[0088] In some embodiments of the present application, after the vehicle is subjected to CAN data collection according to the CAN signal collection template, the method further comprises:

[0089] The plurality of CAN data is packaged according to the data upload parameter to obtain a data packet, and the data packet is uploaded to the cloud platform according to the data upload parameter; wherein the data upload parameter comprises at least one of a data upload period, an upload topic, an upload channel, a signal type, or a QoS level.

[0090] In some examples, the vehicle end can simultaneously collect CAN data of multiple different services, in order to further improve transmission efficiency and reduce communication and computing resource consumption, the CAN data corresponding to the multiple services can be packaged according to the data upload parameter to obtain a data packet. Then, the data packet is uploaded to the cloud platform according to the data upload parameter. It can be understood that, in the case that the data upload parameters in the CAN data are the same, the CAN data of different services can be packaged, for example, the data upload period, the upload topic, the upload channel, the signal type, or the QoS level in each CAN data can be the same, and the CAN data can be packaged. The data packet comprises multiple service segments, and each service segment comprises a service identifier and a signal required by the service.

[0091] The data transmission method provided by the embodiments of the present application packages multiple CAN data according to the data upload parameter, and uploads the data packet obtained by the packaging to the cloud platform according to the data upload parameter, thereby effectively reducing the number of connections and packaging required by the transmission protocol such as MQTT, reducing the risk of network jitter, and improving the overall bandwidth utilization. In addition, the packaging process reduces the frequent message packaging and sending operations in the transmission process, reduces the load of the computing resources and communication modules of the vehicle end, reduces the message processing frequency of the server end, and improves the scalability and stability of the platform.

[0092] In some embodiments of the present application, uploading the data packet to the cloud platform according to the data upload parameter comprises:

[0093] Determining a target channel from the multiple data upload channels according to the data upload parameter, and the upload channel indicates the target channel.

[0094] Uploading the data packet to the cloud platform through the target channel. That is, the CAN data corresponding to each service in the data packet is the same data upload channel, the target channel is determined from the multiple upload channels (such as data collection channels, vehicle control channels, diagnosis channels, etc.) connected between the cloud platform and the vehicle end according to the data upload channel indicated in the overall data packet, and the data packet is uploaded through the target channel.

[0095] The uploading channel is usually implemented based on the MQTT protocol and has independent connection configuration and quality assurance mechanism to support isolated transmission of different priority or type data. For example, when the uploading channel is specified as "1" (representing the data acquisition channel) in the data uploading parameter, the system uploads the corresponding data packet to the corresponding Topic of the cloud platform through the data acquisition dedicated MQ connection; if it is specified as "2" (representing the vehicle control channel), the uploading operation is performed using the vehicle control MQ connection.

[0096] The data transmission method provided by the embodiment of the application can realize classification and isolation of different service data, transmission path optimization and reasonable allocation of bandwidth resources by taking the uploading channel parameter as a decision basis for the data packet transmission path, thereby effectively improving the reliability and real-time performance of the data uploading process.

[0097] In some embodiments of the application, the CAN signal acquisition template further includes data compression information, and the data compression information includes at least one of a compression type, a compression level and a compression threshold.

[0098] The compression type cpType is used to indicate the type of compression algorithm adopted, such as zstd, gzip or other compression methods suitable for the vehicle-mounted edge computing environment. The compression level cpLevel is used to control the compression strength, and the higher the value, the higher the compression rate, but it may bring higher computational overhead. The compression threshold cpBytes is used to determine the minimum data volume threshold for enabling the compression operation, and when the data packet size is smaller than the threshold, the compression is skipped to avoid the problem of "volume increase after compression". For example, the compression threshold cpBytes = 1024 indicates that only when the data packet size is greater than or equal to 1 KB, the compression is performed; otherwise, the data packet is directly uploaded.

[0099] Illustratively, the compression type cpType is 0, indicating that no data compression is performed; the compression type cpType is 0, indicating that the Zstandard compression algorithm is used for data compression; the compression type cpType is 2, indicating that the gzip algorithm is used for data compression, and so on.

[0100] Taking the Zstandard compression algorithm as an example, the compression level cpLevel is generally between 1 and 22, and the larger the value, the higher the compression rate but the more computational resources required. For example, cpLevel = 3 indicates that the 3rd level compression method of the Zstandard algorithm is used.

[0101] After the CAN data of the vehicle is collected according to the CAN signal acquisition template, the method further includes:

[0102] The CAN data is compressed according to the data compression information.

[0103] The data transmission method provided by the embodiment of the application can compress CAN data according to data compression information before uploading, thereby greatly reducing the size of the data packet, significantly reducing the bandwidth resources required in the wireless communication process, shortening the time consumption of uploading, effectively improving the throughput efficiency of data in the transmission process, and reducing the transmission delay.

[0104] In some embodiments of the application, uploading the data packet to the cloud platform according to the data uploading parameter comprises:

[0105] Error detection and / or retransmission of the data packet according to the QoS level.

[0106] In some examples, when the QoS level is 0, the vehicle end publishes the data packet to the cloud platform directly through the MQTT protocol without waiting for confirmation feedback; if packet loss occurs at the physical layer or the transmission layer, no retransmission operation is performed.

[0107] When the QoS level is 1, the message ID is recorded after publishing the data packet, and the confirmation message is waited for from the cloud platform. If the confirmation is not received within a timeout, the vehicle end automatically retransmits, and the maximum number of retries can be configured.

[0108] When the QoS level is 2, the three-stage confirmation process of PUBREC / PUBREL / PUBCOMP is introduced. The cloud end confirms the data to be valid only after the complete handshake process is completed, thereby ensuring that each piece of data is processed only once.

[0109] The data transmission method provided by the embodiment of the application effectively improves the reliability in a complex network environment through the retransmission mechanism driven by the QoS level, especially in the scenarios of network disconnection, weak network, or time delay fluctuation. In addition, the CAN data corresponding to different services has different QoS levels, which avoids performing a redundant retransmission process for non-critical data and reduces the memory and bandwidth pressure.

[0110] In some embodiments of the application, the data packet includes a relative timestamp and an absolute timestamp.

[0111] CAN data of the vehicle is collected according to the CAN signal collection template, comprising:

[0112] In the vehicle end initialization process, multiple frames of CAN data are recorded according to the relative timestamp.

[0113] After the initialization of the vehicle end is completed, multiple frames of CAN data are recorded according to the absolute timestamp.

[0114] In some examples, in order to improve the timing accuracy of the CAN data of the vehicle end in the initial stage of collection and the time traceability in the whole life cycle, the relative timestamp and the absolute timestamp are introduced.

[0115] The timestamp configuration parameters in the data packet include a relative timestamp starting point (i.e., the reference UTC time at the vehicle start time), a relative timestamp precision, and an absolute time synchronization mode (e.g., GPS, NTP, etc.).

[0116] When the vehicle-side controller is powered on but has not completed absolute time synchronization (e.g., GPS is not locked or NTP is not connected), the system uses the start time as the starting point to enable a local counter to generate a relative timestamp. Each frame of CAN data records the time interval between the start time (e.g., 100 ms, 500 ms, etc.), ensuring that the data has correct timing information. This stage does not rely on external time sources, significantly shortening the delay from cold start to available state, and improving system startup efficiency.

[0117] After completing time synchronization (e.g., GPS obtains valid positioning or the network time source completes NTP time synchronization), the vehicle-side system records the absolute time and relative time value at that time as a switching anchor point. Subsequent data is collected by converting the relative time difference value and the anchor point to generate a unified absolute timestamp. This process ensures seamless connection between the relative time period and the absolute time period, achieving continuity of the data timeline.

[0118] The data transmission method provided by the embodiments of the present application continuously collects and records CAN signals through relative timestamps during the local time initialization completion stage, improving the data acquisition coverage rate during the cold start stage. Even if there is a lack of absolute time information in the early start stage, the historical data and current data can be unified on the time axis through retroactive correction of the absolute time anchor point in the later stage.

[0119] The embodiments of the present application also provide a data transmission method applied to a cloud platform, such as Figure 2 As shown in the figure, the data transmission method applied to the cloud platform includes the following steps:

[0120] S201, receiving controller area network (CAN) data from a vehicle-side controller.

[0121] The CAN data is collected by the vehicle-side according to a CAN signal collection template, and the CAN signal collection template is determined according to the collection business. The CAN signal collection template at least includes business information, and the business information includes a business identifier and a signal list required by the business. The CAN signal collection template can also include data upload period, upload topic, upload channel, data type, QoS level, etc. parameters, which are used to define the upload strategy and transmission reliability level of the collected data. In addition, in order to meet the needs of concurrent collection and differentiated data management of multiple businesses, the template supports signal configuration in different business scenarios.

[0122] The data transmission method provided by the embodiments of the present application, the CAN data received by the cloud platform is obtained through a CAN signal collection template, and the CAN data contains CAN signals of different business concerns, thereby avoiding data redundancy and transmission pressure caused by full-amount signal collection and improving system operation efficiency. In addition, after receiving the CAN data, the cloud platform classifies, routes and schedules the CAN data according to the business identifier, thereby avoiding complex logical judgment and redundant analysis operations caused by the traditional signal level data processing mode without business semantics.

[0123] In some embodiments of the present application, the CAN data from the vehicle end is received, including:

[0124] The compressed CAN data is received, and the compressed CAN data is obtained by compressing the CAN data according to data compression information by the vehicle end, and the data compression information includes at least one of a compression type, a compression level or a compression threshold.

[0125] The compressed CAN data is decompressed according to the data compression information.

[0126] On the basis of receiving the compressed CAN data from the vehicle end, further including:

[0127] In some examples, after the cloud platform receives the compressed CAN data uploaded by the vehicle end, the cloud platform performs integrity verification on the compressed CAN data, including protocol layer verification and application layer format verification. For example, in the uploading channel based on the MQTT protocol, the cloud platform ensures successful transmission of the data packet through the PUBACK confirmation mechanism; in the application layer, the cloud platform verifies whether the data is of a specific compression type by checking the compression identifier field in the data packet header. Subsequently, the cloud platform determines and initializes the corresponding decompression strategy according to the compression type field (cpType), the compression level field (cpLevel) and the compression threshold field (cpBytes) in the received data packet. For example, when cpType is 1, the gzip algorithm is used, and the cloud platform will decode the data based on the gzip protocol; when cpType is 2, the zlib algorithm is used, and a streaming decompression mode is used to adapt to large-capacity data; if cpType is 0 or the size of the data packet is less than the compression threshold cpBytes, it indicates that the data is not compressed, and the cloud platform can directly read the original CAN data.

[0128] Further, to ensure the safety and stability of data processing, the CAN data can also be subjected to abnormal processing. For example, when decompression fails, the compression information does not match or the data is damaged, the cloud platform can record abnormal logs, and according to the configuration strategy, request the vehicle end to resend the original data, or automatically fallback to the default compression parameters for trial decompression. If the decompression fails for several times, the system will mark the data as abnormal and store it separately, to prevent abnormal data from mixing into the analysis process.

[0129] The data transmission method provided by the embodiments of the present application is that the cloud platform performs corresponding decompression operations according to the compression information, without secondary matching or guessing the compression format, thereby improving the automation degree and processing efficiency of the decompression process. In addition, since the compression data carries explicit compression type identifiers (such as gzip, zlib, etc.) and compression level, threshold and other information, the cloud platform can accurately match the corresponding decompression algorithm, thereby ensuring that the decompression process is highly consistent with the vehicle-side compression process.

[0130] In some embodiments of the present application, the CAN data includes an absolute timestamp and a relative timestamp, and the CAN data received from the vehicle side includes:

[0131] The data packet is obtained by the vehicle side from a plurality of CAN data according to data upload parameters, and the data upload parameters include at least one of a data upload period, an upload topic, an upload channel, a signal type or a quality of service (QoS) level.

[0132] The CAN data corresponding to the service is obtained from the data packet according to the absolute timestamp and the relative timestamp.

[0133] In some examples, the cloud platform extracts the service type corresponding to the current data packet, the absolute timestamp of the sampling start time of the data packet, and the relative timestamp from the data packet. The cloud platform calculates an initialization reference time by using the first valid absolute timestamp and the relative timestamp corresponding thereto as a conversion anchor point for subsequent relative time. If the absolute timestamp in the data packet is the reliable sampling global time, the cloud platform directly uses the time for time alignment and data positioning.

[0134] The data transmission method provided by the embodiments of the present application restores the CAN data according to the relative timestamp and the absolute timestamp, adapts to the scene where the unsynchronized time and the synchronized time of the vehicle side exist in a mixed manner, and ensures the global time unification of the data.

[0135] The embodiments of the present application also provide a data transmission method, which is implemented by a data transmission system as shown in Figure 3 The data transmission system includes a vehicle side, a management platform, a TSP cloud platform, an application gateway, etc.

[0136] The vehicle side includes the following:

[0137] The HPC unit is one of the "brains" of the vehicle, responsible for high-level computing and other functions of the vehicle, and also generates or processes vehicle data.

[0138] The TSP cloud is a cloud service platform of the vehicle manufacturer, and the vehicle side interacts with the TSP cloud.

[0139] Data Gateway, which is a "data relay station" of the vehicle, is responsible for managing and forwarding data between different modules inside the vehicle, including CAN bus data.

[0140] Shared memory is a data sharing mechanism inside the vehicle, which is used for efficient data transmission between different modules (such as acquisition strategy, acquired signal data, etc.).

[0141] Signal Collect SDK is a software toolkit for CAN data acquisition on the vehicle side, which includes data acquisition SDK and remote control SDK. The data collected by the data acquisition SDK and the remote control SDK can be sent to the application gateway through protocols such as MQTT.

[0142] TSP cloud platform is the core of cloud business processing of the vehicle manufacturer, which is responsible for receiving data uploaded by the vehicle end, processing, analyzing, and finally storing, including business services and consumption services. Business services include CAN protocol management module and CAN signal acquisition template management module. Consumption services include signal data processing and signal data business.

[0143] In addition, the signal data processed by the TSP cloud platform is stored in the data storage module.

[0144] Based on the foregoing data transmission system, the data transmission method includes the following steps:

[0145] S301, formulating a CAN protocol to set a unique signal ID for each signal in the CAN protocol.

[0146] Illustratively, the standard signal ID definition template includes message name, message type, message identifier, message sending type, message cycle time, message length, signal name, signal description, initial value, invalid value, non-enabled value, unit, signal value description, fast cycle of message sending, number of times of fast sending of message, message delay time, national standard signal, change precision, upload type, standard ID, channel, etc.

[0147] Each signal field in the formulated CAN protocol is assigned a unique Signal ID, so that protocol analysis can be completed on the vehicle end when uploading data, and the cloud platform can directly locate the target signal data according to the Signal ID, skipping the original message parsing process, greatly reducing the parsing burden.

[0148] S302, the operator uploads the aforementioned formulated CAN protocol to the management platform, and configures the CAN signal acquisition template according to the business scenario of the vehicle model, which includes business identification, upload period, signal list, upload topic, upload channel, data type, trigger condition, trigger duration and QoS. The management platform sends the CAN signal acquisition template configured by the operator to the vehicle end.

[0149] S303, the vehicle-end SDK (Software Development Kit) queries the latest CAN signal collection template by vehicle model / year model at power-on, stores the local CAN signal collection template after querying the CAN signal collection template, and then sends the CAN protocol to be collected to the TSP Cloud.

[0150] S304, the TSP Cloud accesses the vehicle CAN bus through the data gateway Data Gateway according to the CAN signal collection template, and obtains the corresponding CAN frame and signal raw value. After obtaining the signal data, the signal data is transmitted to the vehicle-end SDK for subsequent processing in combination with the pre-defined unique signal ID.

[0151] S305, after the vehicle-end SDK receives the signal data from the TSP Cloud, the corresponding signal collection logic is executed according to the CAN signal collection template. If the upload period, topic, transmission channel, signal type and QoS level of multiple businesses are the same, the vehicle-end SDK can combine these businesses into a data packet containing multiple business segments. When uploading, the SDK selects the appropriate MQTT channel according to the configuration, and completes the assembly of the data packet according to the unified data upload structure.

[0152] Illustratively, the data packet includes an outermost container Message, basic information and business data SignalPack, a signal set SignalBytes, and signal data SignalData.

[0153] The outermost container Message is the top message type, which is used as the "package" of data transmission, and is used to batch encapsulate multiple independent SignalPacks.

[0154] The basic information and business data SignalPack are the smallest logical units of transmission, which include the following fields:

[0155] Business ID, used to identify the business scenario to which the data belongs, facilitating classification processing by the cloud platform.

[0156] Full packet absolute timestamp (usually in milliseconds or microseconds), recording the absolute time when the data packet is generated or collected, used for global time alignment.

[0157] Full packet relative timestamp (usually in milliseconds or microseconds), generally recording the offset of the data packet relative to a certain reference time (such as vehicle start time, TSP platform connection time), used to supplement the flexibility of absolute time.

[0158] Business segment data content, storing the serialized specific signal data.

[0159] The signal set SignalBytes is used to organize multiple signal data in the same data packet, and a Map structure is used to realize fast mapping of "signal ID to signal value", which includes the following fields:

[0160] The Map key is an int32 type signal ID, and the value is a SignalData type. Illustratively, in the HashMap data structure, the unique identifier (signal ID) of each signal is used as the Key of the HashMap, thereby avoiding the additional bandwidth overhead caused by repeated transmission of the signal ID and saving signal ID transmission traffic.

[0161] The corresponding HashMap Value is a signal object, which includes a timestamp difference value and a signal value difference value. The timestamp difference value represents the time difference of the current signal sampling time compared to the last frame of the signal (rather than the absolute time), thereby reducing the repeated transmission of redundant timestamp information. The signal value difference value represents the change amount of the current frame signal value compared to the last frame, thereby avoiding repeated uploading of unchanged static data.

[0162] Based on the above HashMap data structure, only when the signal value or time actually changes is the difference data transmitted, thereby significantly reducing the data packet size in the high-frequency signal or large-scale signal collection scenario, effectively alleviating the bandwidth occupation problem of the CAN signal upload link, while ensuring data integrity and analysis efficiency, and having good practicability and promotional value.

[0163] In some examples, two service segments are included in one data packet, as shown in Figure 4 The service segment 1 and the service segment 2 each correspond to different service IDs, and both include the following fields: standard signal length, timestamp, multiple types of CAN signals, etc. For example, the service segment 1 includes A signal and B signal, and the service segment 2 includes A signal and Y signal, both of which include n frames of CAN signals, and the absolute time of each frame of CAN signal is calculated according to the time of the first frame + cumulative time difference.

[0164] S306, after the TSP cloud platform receives the compressed data uploaded by the vehicle end, the data is first decompressed using a predetermined compression algorithm. The decompressed data is extracted according to the service ID to obtain the corresponding data segment, and then the data segment is deserialized in Protobuf format to obtain the Map structure data. Then, the corresponding signal list is located through the service signal ID, and finally the complete timestamp and signal value are restored to accurately reconstruct the data collected by the vehicle end.

[0165] It should be noted that when the local time of the vehicle end has not been initialized, the vehicle end will record the time information of each collected data by using a relative timestamp. The relative timestamp is incremented according to a collection period (for example, 500 milliseconds) starting from the power-on of the vehicle end, and is used to mark the relative time sequence of the data. After the absolute timestamp of the vehicle end is restored to normal, the cloud platform can calculate the accurate collection time of the historical data by using the method of "absolute timestamp + relative time difference", so as to effectively correct the time jump or inaccuracy caused by the unsynchronized time, and to guarantee the continuity and reliability of the data in the global time dimension.

[0166] The data transmission method provided by the embodiment of the application introduces a CAN signal collection template, which is flexibly defined and configured according to actual business requirements, and includes a business type, a CAN signal required by the business, a data upload period, an upload topic, an upload channel, a signal type or a QoS level. The CAN signal required by the business is collected according to the CAN signal collection template, which breaks through the inefficient mode of traditional "full-amount collection", significantly improves the adaptability and expansibility of the collection system, and effectively avoids the bandwidth waste and storage pressure caused by redundant data transmission.

[0167] In addition, in the data upload phase, the CAN data is also compressed, and the upload data packet structure is designed to be optimized, so as to realize the flattening of the data packet structure and the minimization of the redundant fields, and significantly reduce the network transmission load and storage occupation.

[0168] Furthermore, the application uploads data according to the upload channel indicated by the data packet, different business scenarios have corresponding upload channels and parameters, supports multi-channel data upload, and can realize data isolation. The QoS mechanism can realize error detection and retransmission, and improve the robustness and security of the data link.

[0169] In addition, the data transmission method provided by the embodiment of the application can also perform deduplication processing on cross-frame data of the same signal ID according to the time offset and the value difference. Specifically, the time difference (i.e., the relative timestamp) between the current frame and the previous frame is recorded, instead of transmitting the complete timestamp every frame, which significantly reduces the data length of the time field. Only the change amount (time difference) of the current signal value relative to the previous frame is transmitted, which avoids repeated data transmission in the scene where the numerical value changes little. The data transmission method provided by the embodiment of the application not only reduces the traffic consumption caused by signal repeated reporting, but also reduces the dependence of the system on network bandwidth and storage space, and has a significant performance advantage in the scene of multi-frame continuous sampling and high-frequency signal upload, which helps to improve the overall data processing efficiency and real-time performance of the vehicle networking system.

[0170] The embodiment of the application also provides a data transmission device, which is applied to a vehicle end, as shown in the figure, the device comprises: Figure 5 ​

[0171] The template acquisition module 501 is used to acquire a controller area network (CAN) signal acquisition template. The CAN signal acquisition template is determined according to the acquisition service.

[0172] The collection and upload module 502 is used to collect CAN data of the vehicle according to the CAN signal collection template and upload it to the cloud platform.

[0173] In some embodiments of the present application, the CAN signal acquisition template includes at least business information, and the business information includes a business identifier and a list of signals required by the business.

[0174] In some embodiments of the present application, the CAN signal acquisition template also includes data upload parameters, and the data upload parameters include at least one of a data upload cycle, an upload topic, an upload channel, a signal type, or a QoS level.

[0175] The data transmission device further includes a packaging module, which is configured to:

[0176] Pack multiple CAN data according to the data upload parameters to obtain data packets, and upload the data packets to the cloud platform according to the data upload parameters.

[0177] In some embodiments of the present application, the packaging module is specifically used to:

[0178] Determining a target channel from a plurality of data upload channels according to a data upload parameter, the upload channel indicating the target channel;

[0179] Upload the data packet to the cloud platform through the target channel.

[0180] In some embodiments of the present application, the CAN signal acquisition template further includes data compression information, and the data compression information includes at least one of a compression type, a compression level, and a compression threshold.

[0181] The data transmission device further includes a compression module, which is configured to:

[0182] Compress CAN data according to data compression information.

[0183] In some embodiments of the present application, the collection and upload module is specifically used to:

[0184] Perform error detection and / or retransmission of packets based on QoS level.

[0185] In some embodiments of the present application, the data packet includes a relative timestamp and an absolute timestamp.

[0186] The collection and upload module is specifically used for:

[0187] In the vehicle end initialization process, multiple frames of CAN data are recorded according to the relative time stamp;

[0188] After the initialization is completed at the vehicle end, multiple frames of CAN data are recorded according to the absolute time stamp.

[0189] The embodiment of the application further provides a data transmission device, which is applied to a cloud platform, as shown in the figure, the device comprises: Figure 6

[0190] The data receiving module 601 is configured to receive the controller area network (CAN) data from the vehicle end, the CAN data being collected by the vehicle end according to a CAN signal collection template, and the CAN signal collection template being determined according to a collection service.

[0191] In some embodiments of the application, the data receiving module B01 is specifically configured to:

[0192] receive the compressed CAN data, the compressed CAN data being obtained by compressing the CAN data according to data compression information, and the data compression information comprising at least one of a compression type, a compression level or a compression threshold.

[0193] decompress the compressed CAN data according to the data compression information.

[0194] In some embodiments of the application, the CAN data comprises an absolute time stamp and a relative time stamp, and the data receiving module 601 is specifically configured to:

[0195] receive a data packet, the data packet being obtained by packing multiple CAN data according to data upload parameters, and the data upload parameters comprising at least one of a data upload period, an upload topic, an upload channel, a signal type or a quality of service (QoS) level.

[0196] obtain the CAN data corresponding to the service from the data packet according to the absolute time stamp and the relative time stamp.

[0197] Correspondingly, the embodiment of the application further provides a computer readable storage medium. The computer readable storage medium stores computer instructions, and the computer instructions are used to make the processor execute the data transmission method of the embodiment of the application.

[0198] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0199] ​The above describes in detail the data transmission method, device and medium provided by the embodiments of the application. The principles and implementation manners of the application are described by applying specific examples. The above description of the embodiments is only used to help understand the method of the application and its core idea. Meanwhile, for those skilled in the art, the specific implementation manners and application ranges will be changed according to the idea of the application. In conclusion, the content of the specification should not be understood as a limitation of the application.

Claims

1. A data transmission method, characterized in that: Applied to the vehicle side, the method includes: Obtaining a controller area network (CAN) signal acquisition template, wherein the CAN signal acquisition template is determined based on the acquisition service; The vehicle CAN data is collected according to the CAN signal acquisition template and uploaded to the cloud platform.

2. The data transmission method according to claim 1, wherein: The CAN signal acquisition template includes at least business information, and the business information includes a business identifier and a list of signals required by the business.

3. The data transmission method according to claim 1 or 2, wherein: The CAN signal acquisition template further includes data upload parameters, wherein the data upload parameters include at least one of a data upload cycle, an upload topic, an upload channel, a signal type, or a QoS level; After collecting CAN data from the vehicle according to the CAN signal collection template, the method further includes: Packing multiple CAN data according to the data upload parameters to obtain a data packet, and uploading the data packet to the cloud platform according to the data upload parameters.

4. The data transmission method according to claim 3, wherein: The uploading of the data packet to the cloud platform according to the data upload parameters includes: determining a target channel from a plurality of data upload channels according to the data upload parameter, the upload channel indicating the target channel; Upload the data packet to the cloud platform through the target channel.

5. The data transmission method according to claim 2, wherein: The CAN signal acquisition template further includes data compression information, wherein the data compression information includes at least one of a compression type, a compression level, and a compression threshold; After collecting CAN data from the vehicle according to the CAN signal collection template, the method further includes: The CAN data is compressed according to the data compression information.

6. The data transmission method according to claim 3, wherein: The uploading of the data packet to the cloud platform according to the data upload parameters includes: Error detection and / or retransmission are performed on the data packet according to the QoS level.

7. The data transmission method according to claim 3, wherein: The data packet includes a relative timestamp and an absolute timestamp; The step of collecting CAN data from a vehicle according to the CAN signal collection template includes: During the vehicle-side initialization process, recording multiple frames of CAN data according to the relative timestamp; After the vehicle end completes initialization, multiple frames of CAN data are recorded according to the absolute timestamp.

8. A data transmission method, characterized in that: Applied to a cloud platform, the method includes: Receive controller area network (CAN) data from the vehicle side, where the CAN data is collected by the vehicle side according to a CAN signal collection template, and the CAN signal collection template is determined according to the collection business.

9. The data transmission method according to claim 8, wherein: The receiving of CAN data from the vehicle side includes: receiving compressed CAN data, where the compressed CAN data is obtained by the vehicle end compressing the CAN data according to data compression information, where the data compression information includes at least one of a compression type, a compression level, or a compression threshold; The compressed CAN data is decompressed according to the data compression information.

10. The data transmission method according to claim 8, wherein: The CAN data includes an absolute timestamp and a relative timestamp, and the CAN data received from the vehicle includes: receiving a data packet, where the data packet is obtained by the vehicle side packaging a plurality of CAN data according to data upload parameters, where the data upload parameters include at least one of a data upload period, an upload topic, an upload channel, a signal type, or a quality of service (QoS) level; CAN data corresponding to the service is acquired from the data packet according to the absolute timestamp and the relative timestamp.

11. A data transmission device, characterized in that: Applied to the vehicle side, the device includes: A template acquisition module is used to acquire a controller area network CAN signal acquisition template, wherein the CAN signal acquisition template is determined according to the acquisition business; The acquisition and uploading module is used to collect CAN data of the vehicle according to the CAN signal acquisition template and upload it to the cloud platform.

12. A data transmission device, characterized in that: Applied to a cloud platform, the device includes: The data receiving module is used to receive controller area network (CAN) data from the vehicle side. The CAN data is collected by the vehicle side according to a CAN signal collection template, and the CAN signal collection template is determined according to the collection business.

13. A storage medium, characterized in that: The storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the data transmission method according to any one of claims 1 to 10.

Images