CN116416705A

CN116416705A - Driving data transmission method and device

Info

Publication number: CN116416705A
Application number: CN202211249971.0A
Authority: CN
Inventors: 刘青海; 曹亮; 周国辉
Original assignee: Apollo Zhilian Beijing Technology Co Ltd
Current assignee: Apollo Zhilian Beijing Technology Co Ltd
Priority date: 2021-12-30
Filing date: 2021-12-30
Publication date: 2023-07-11
Also published as: CN114333104A; CN114333104B

Abstract

The disclosure provides a driving data transmission method and device, relates to the field of data processing, and particularly relates to the field of automatic driving. The specific implementation scheme is as follows: and carrying out pre-interaction processing with the vehicle-mounted equipment to determine that the vehicle-mounted equipment agrees to send first driving data to the data reading equipment, wherein the first driving data comprises N pieces of sub-data, and N is an integer greater than or equal to 1. N data transmission requests are respectively sent to the vehicle-mounted equipment, and N data transmission responses corresponding to the N data transmission requests are received; the ith data transmission request comprises an identification of the ith sub data, the ith data transmission response comprises the ith sub data, and i is an integer between 1 and N. And acquiring first driving data in the N data transmission responses. The technical scheme of the present disclosure can support a large amount of reading and transmission of the vehicle-capacity data.

Description

Driving data transmission method and device

The application is a divisional application of an invention patent application with the application number of 202111665154.9 and the invention name of driving data transmission method and device, which is filed on 12 months and 30 days of 2021.

Technical Field

The disclosure relates to the field of automatic driving in the field of data processing, and in particular relates to a driving data transmission method and device.

Background

With the continuous development of technology, automatic driving technology is gradually accepted by users, so that automatic driving is a great trend of future automobile development.

As the electrical and electronic architecture of vehicles becomes more complex, and the amount of data generated also increases exponentially, extraction and transmission of data on board the vehicle is also becoming more important. Currently, in the prior art, when transmitting and extracting vehicle-mounted data, a unified diagnostic service (Unified Diagnostic Services, UDS) protocol is relied on.

However, the UDS protocol only supports transmission of a small amount of data, and cannot be adapted to current extraction and transmission of vehicle-mounted data.

Disclosure of Invention

The disclosure provides a driving data transmission method and device.

According to a first aspect of the present disclosure, there is provided a driving data transmission method applied to a data reading device, the method including:

pre-interaction processing is carried out with vehicle-mounted equipment to determine that the vehicle-mounted equipment agrees to send first driving data to the data reading equipment, wherein the first driving data comprises N pieces of sub-data, and N is an integer greater than or equal to 1;

respectively sending N data transmission requests to the vehicle-mounted equipment, and receiving N data transmission responses corresponding to the N data transmission requests; the ith data transmission request comprises an identification of the ith sub data, and the ith data transmission response comprises the ith sub data, wherein i is an integer between 1 and N;

And acquiring the first driving data in the N data transmission responses.

According to a second aspect of the present disclosure, there is provided a driving data transmission method applied to a vehicle-mounted device, where the method includes:

pre-interaction processing is carried out with data reading equipment so as to determine to send first driving data to the data reading equipment, wherein the first driving data comprises N pieces of sub-data, and N is an integer greater than or equal to 1;

receiving N data transmission requests sent by the data reading equipment, and sending N data transmission responses corresponding to the N data transmission requests to the data reading equipment;

the ith data transmission request comprises an identification of ith sub data, and the ith data transmission response comprises the ith sub data, wherein i is an integer between 1 and N.

According to a third aspect of the present disclosure, there is provided a driving data transmission apparatus applied to a data reading device, the apparatus comprising:

the processing module is used for carrying out pre-interaction processing with the vehicle-mounted equipment so as to determine that the vehicle-mounted equipment agrees to send first driving data to the data reading equipment, wherein the first driving data comprises N pieces of sub-data, and N is an integer greater than or equal to 1;

The transmission module is used for respectively sending N data transmission requests to the vehicle-mounted equipment and receiving N data transmission responses corresponding to the N data transmission requests; the ith data transmission request comprises an identification of the ith sub data, and the ith data transmission response comprises the ith sub data, wherein i is an integer between 1 and N;

and the acquisition module is used for acquiring the first driving data in the N data transmission responses.

According to a fourth aspect of the present disclosure, there is provided a driving data transmission apparatus applied to a vehicle-mounted device, wherein the apparatus includes:

the processing module is used for carrying out pre-interaction processing with the data reading equipment so as to determine to send first driving data to the data reading equipment, wherein the first driving data comprises N pieces of sub-data, and N is an integer greater than or equal to 1;

the transmission module is used for receiving N data transmission requests sent by the data reading equipment and sending N data transmission responses corresponding to the N data transmission requests to the data reading equipment;

According to a fifth aspect of the present disclosure, there is provided an electronic device comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the first or second aspect.

According to a sixth aspect of the present disclosure, there is provided a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of the first or second aspect.

According to a seventh aspect of the present disclosure, there is provided a computer program product comprising: a computer program stored in a readable storage medium from which at least one processor of an electronic device can read, the at least one processor executing the computer program causing the electronic device to perform the method of the first or second aspect.

The technology according to the present disclosure solves the problem that extraction and transmission of a large amount of vehicle-mounted data cannot be achieved.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.

Drawings

The drawings are for a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

fig. 1 is a schematic view of a scenario of a driving data transmission method provided by the present disclosure;

fig. 2 is a schematic implementation diagram of a protocol layer structure provided in an embodiment of the disclosure;

fig. 3 is a flowchart of a driving data transmission method provided in an embodiment of the present disclosure;

fig. 4 is a second flowchart of a driving data transmission method provided in an embodiment of the present disclosure;

fig. 5 is a signaling interaction diagram of a driving data transmission method provided by an embodiment of the present disclosure;

fig. 6 is a schematic implementation diagram of a format of a request packet according to an embodiment of the disclosure;

fig. 7 is a schematic diagram of an implementation of a data transmission frame according to an embodiment of the disclosure;

FIG. 8 is a schematic diagram of an implementation of an absolute path included in a data read request provided by an embodiment of the present disclosure;

fig. 9 is a second schematic implementation diagram of a data transmission frame according to an embodiment of the disclosure;

fig. 10 is a schematic diagram of implementation of a format of a response message provided by an embodiment of the disclosure;

Fig. 11 is a flowchart III of a driving data transmission method provided in an embodiment of the present disclosure;

fig. 12 is a schematic structural diagram of a driving data transmission device according to an embodiment of the disclosure;

fig. 13 is a second schematic structural diagram of a driving data transmission device according to an embodiment of the disclosure;

fig. 14 is a block diagram of an electronic device for implementing a driving data transmission method of an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

For a better understanding of the technical solutions of the present disclosure, the related art to which the present disclosure relates is further explained in detail below.

With the continuous development of automatic driving technology, new four-way intelligent internet-connected automobiles which meet the requirements of dynamoelization, internet-connected technology, intellectualization and sharing are accelerating to people. However, with the landing of new technologies, various potential problems are also presented.

With the electric, networking and intelligent of vehicles and the sequential access of electric equipment such as cameras, ultrasonic radars, millimeter wave radars and laser radars to vehicle ends, the electric and electronic architecture of vehicles is increasingly complex, and the generated data volume is exponentially increased. In this context, vehicle fault diagnosis, accident responsibility determination, and accident inversion put higher demands on extraction of vehicle-mounted data.

Currently, in the prior art, when transmitting and extracting vehicle-mounted data, the UDS protocol is relied on, wherein the UDS protocol, i.e. ISO 14229, is a standardized standard for performing diagnostic services, such as what instruction should be given to an electronic control unit (Electronic Control Unit, ECU) by reading a fault code, and what instruction should be given by reading a data stream. The above-mentioned ISO standard refers to a standard made by the international organization for standardization (International Organization for Standardization, ISO).

However, the UDS protocol is mainly used for diagnostic services and is not a protocol dedicated for data transmission, so that the UDS protocol only supports transmission of a small amount of data, and cannot adapt to current extraction and transmission of vehicle-mounted data, so that extraction and transmission of a large amount of vehicle-mounted data cannot be realized, and further processing of the vehicle-mounted data is limited.

Aiming at the problems in the prior art, the present disclosure proposes the following technical ideas: in the standard formulation of data storage systems (Data storage system for automoted driving, DSSAD) for autonomous vehicles, a simple data management protocol is proposed for intelligent networked vehicle drive data, wherein the simple data management protocol is a protocol dedicated to support extraction and transmission of vehicle-mounted data, and preprocessing and fragment extraction and transmission are performed during the extraction process, so that extraction and transmission can be ensured for a large amount of vehicle-mounted data.

It should be noted that, the simple data management protocol (Simple Data Management Protocol, SDMP) in this embodiment is just a possibility, and with the development of technology, it may also exist in the remaining names, so long as the nature of the protocol is the technical solution introduced in this disclosure, and specific protocol names may be set according to actual requirements.

On the basis of the above description, the following describes in detail the driving data transmission method provided by the present disclosure with reference to specific embodiments, where the driving data transmission method is applied to a data reading device and a vehicle-mounted device, for example, an application scenario of the present disclosure may be understood with reference to fig. 1, and fig. 1 is a schematic scenario diagram of the driving data transmission method provided by the present disclosure.

As shown in fig. 1, fig. 1 includes a data reading device 101 and an in-vehicle device 102. Wherein the data reading device 101 can read in-vehicle data from the in-vehicle device 102.

The data reading device may be any device for reading vehicle-mounted data, which is external to the vehicle, and in one possible implementation, for example, may be a diagnostic device for diagnosing the vehicle, or may be any device for reading data, which is not limited in this embodiment, and may be selected and set according to actual requirements.

And, the in-vehicle apparatus may be understood as a vehicle, or may also be understood as an ECU in the vehicle, the present embodiment is not limited as well as long as in-vehicle data is stored in the in-vehicle apparatus, and the in-vehicle apparatus may supply the corresponding data to the data reading apparatus according to a request of the data reading apparatus.

Based on the scenario described in fig. 1, since data transmission in the present disclosure is implemented based on the simple data management protocol SDMP, the protocol layer structure of the simple data management protocol is described below with reference to fig. 2, and fig. 2 is a schematic implementation diagram of the protocol layer structure provided by an embodiment of the present disclosure.

As shown in fig. 2, the Simple Data Management Protocol (SDMP) is an application layer protocol located at the seventh layer of the open system interconnection communication reference model (Open System Interconnection Reference Model, OSI), and as shown in fig. 2, the universal transport layer is formed by reducing the dimension of the UDS-related protocol family of ISO 14229 and combining with the conventional transport layer/network layer protocols such as DoCan, doIP, LIN. I.e. the hatched portion in fig. 2, acts as a flood transport layer. Wherein the generic transport layer is used to support data transmission based on SDMP of the application layer.

Wherein DoCan is diagnosed (Diagnose over CAN) through CAN (Controller Area Network ), dop is diagnosed communication (Diagnostic communication over Internet Protocol) through network protocol, LIN is local interconnect network (Local Interconnect Network). It CAN be appreciated that the LIN bus is a low-cost serial communication network defined for the distributed electronic system of the automobile, is a supplement to other automobile multi-path networks such as CAN, and is suitable for applications without excessively high requirements on the bandwidth, performance or fault tolerance function of the network.

And, wherein the dimension reduction for the protocol family, that is, the native UDS protocol is the application layer protocol, the relevant protocol is now referred to as the protocol of the generic transport layer, i.e., the protocol family dimension reduction. It should be noted that, in fig. 2, ISO 14299-1 and ISO 14299-X (where X represents a possible value) are protocol numbers of the UDS protocol, ISO 15765-2 is a protocol number of the DoCan protocol, ISO 13400-2 is a protocol number of the DoIP protocol, and ISO 17987-2 is a protocol number of the LIN protocol, and for the rest of the protocol numbers in fig. 2, corresponding protocols exist, which are not described herein.

It can be understood that, based on the protocol layer structure provided in fig. 2, by aggregating related protocols into a generic transport layer, data transmission corresponding to a simple data transmission protocol can be effectively supported.

The following describes a driving data transmission method in the present disclosure with reference to specific embodiments, and first describes a driving data transmission method on one side of a data reading device. Fig. 3 is a flowchart of a driving data transmission method provided in an embodiment of the present disclosure.

As shown in fig. 3, the method includes:

s301, pre-interaction processing is carried out on the vehicle-mounted equipment so as to determine that the vehicle-mounted equipment agrees to send first driving data to the data reading equipment, wherein the first driving data comprises N pieces of sub-data, and N is an integer greater than or equal to 1.

In this embodiment, the data reading device may perform pre-interaction processing with the vehicle-mounted device, where the pre-interaction processing is to determine whether the vehicle-mounted device agrees to the data reading device to extract the first driving data.

It can be understood that if the vehicle-mounted device agrees to the data reading device to extract the first driving data, the data reading device may then extract the first driving data. Alternatively, if the vehicle-mounted device does not agree with the data reading device to extract the first vehicle data, the data reading device cannot perform the subsequent data extraction operation.

The first driving data in this embodiment includes N pieces of sub data, for example, the first driving data may be divided into N pieces of sub data according to a preset sub data size, or the first driving data may be further divided into N pieces of sub data according to a data structure of the first driving data, where specific division of the sub data may be selected and set according to actual requirements, which is not limited in this embodiment, as long as the first driving data may include N pieces of sub data.

S302, respectively sending N data transmission requests to the vehicle-mounted equipment, and receiving N data transmission responses corresponding to the N data transmission requests; the ith data transmission request comprises an identification of the ith sub data, the ith data transmission response comprises the ith sub data, and i is an integer between 1 and N.

The data reading device in this embodiment needs to acquire the first driving data, and based on the above-mentioned determination that N pieces of sub-data are included in the first driving data, the data reading device may send N data transmission requests to the vehicle-mounted device, respectively. Taking the ith data transmission request in the N data transmission requests as an example, the ith data transmission request may include a representation of the ith sub data, so as to inform the vehicle-mounted device of the data that needs to be specifically acquired by the current data acquisition request.

Correspondingly, the vehicle-mounted device can receive the N data transmission requests sent by the data reading device and send N data transmission responses corresponding to the N data transmission requests to the data reading device. The data reading device in this embodiment can thus receive N data transmission responses sent by the in-vehicle device. Taking the ith data transmission response as an example, the ith sub data is included in the ith data transmission response. I in this embodiment is an integer between 1 and N.

The N data transmission requests in this embodiment may be transmitted once, or may be transmitted in multiple times, which is not limited in this embodiment, as long as the data reading device may transmit the N data reading requests to the vehicle-mounted device to acquire the first driving data.

S303, acquiring first driving data in N data transmission responses.

The N data transmission responses in this embodiment include the first vehicle data in common, so after the N data transmission responses sent by the vehicle-mounted data are acquired, the first vehicle data can be acquired in the N data transmission responses.

It can be understood that the data transmission process described in this embodiment is the simple data management protocol described above, where the simple data management protocol can support the acquisition of the first vehicle data that needs to be acquired by the data reading device, so that extraction and transmission of a large amount of vehicle data can be effectively implemented.

The driving data transmission method provided by the embodiment of the disclosure comprises the following steps: and carrying out pre-interaction processing with the vehicle-mounted equipment to determine that the vehicle-mounted equipment agrees to send first driving data to the data reading equipment, wherein the first driving data comprises N pieces of sub-data, and N is an integer greater than or equal to 1. N data transmission requests are respectively sent to the vehicle-mounted equipment, and N data transmission responses corresponding to the N data transmission requests are received; the ith data transmission request comprises an identification of the ith sub data, the ith data transmission response comprises the ith sub data, and i is an integer between 1 and N. And acquiring first driving data in the N data transmission responses. After the data reading device performs pre-interaction processing with the vehicle-mounted device, after determining that the vehicle-mounted device agrees to read the first vehicle-mounted data, the data reading device respectively sends N data transmission requests for acquiring the first vehicle-mounted data to the vehicle-mounted device, and then acquires the first vehicle-mounted data from N data transmission responses sent by the vehicle-mounted data, so that the first vehicle-mounted data can be acquired in a fragmented manner, and a large number of reading and transmission of the vehicle-mounted data can be supported.

On the basis of the above embodiment, the following describes in further detail the driving data transmission method provided in the present disclosure with reference to fig. 3 to 10. Fig. 4 is a flowchart two of a driving data transmission method provided by an embodiment of the present disclosure, fig. 5 is a signaling interaction diagram of the driving data transmission method provided by the embodiment of the present disclosure, fig. 6 is an implementation schematic diagram of a format of a request packet provided by the embodiment of the present disclosure, fig. 7 is an implementation schematic diagram of a data transmission frame provided by the embodiment of the present disclosure, fig. 8 is an implementation schematic diagram of an absolute path included in a data reading request provided by the embodiment of the present disclosure, fig. 9 is an implementation schematic diagram two of the data transmission frame provided by the embodiment of the present disclosure, and fig. 10 is an implementation schematic diagram of a format of a response packet provided by the embodiment of the present disclosure.

As shown in fig. 4, the method includes:

s401, sending an expansion request to the vehicle-mounted equipment.

In this embodiment, when the data reading device performs the pre-interaction processing with the vehicle-mounted device, for example, an expansion request may be first sent to the vehicle-mounted device, where the expansion request in this embodiment is used to request the vehicle-mounted device to enter the expansion mode. It will be appreciated that the reading and transmission of data may only be performed if the vehicle-mounted device enters the extended mode, and therefore the data reading device needs to first request the vehicle-mounted device to enter the extended mode.

For a clearer understanding of the basic scheme of the present disclosure, the data interaction procedure between the data reading device and the in-vehicle device may be understood, for example, in connection with fig. 5.

Referring to fig. 5, the ECU therein may be the in-vehicle apparatus in the present disclosure, wherein the data reading apparatus may send the expansion request to the in-vehicle apparatus ECU. It will be appreciated that all information and data transmissions in this disclosure are implemented in accordance with the simple data management protocol described above, which is briefly described herein.

The protocol is actually a rule that is agreed upon in advance by both parties that interact. Such as how the data is packed, how the data is organized, which bytes represent what information, how the data is verified, and so forth. It will be appreciated that protocols are self-defining, and that certain protocols become generic after wide acceptance.

In this embodiment, the interaction of information and data is performed by means of a simple data management protocol, so that, for example, a specific byte representation extension request can be contracted. For example, referring to fig. 5, the data reading device may send "10 03" when sending the expansion request to the vehicle-mounted device, where "10 03" is a byte agreed in the present protocol and used to represent the expansion request, and "10 03" may be, for example, 16, and more specifically may be represented as 10 ₁₆ 03 ₁₆ 。

Then, for the data reading device, it may directly transmit "10" to the in-vehicle device ECU when it is necessary to transmit the expansion request to the in-vehicle device ECU, and the in-vehicle device ECU may determine that the instruction is for requesting the in-vehicle device to enter the expansion mode after receiving "10".

The above is an exemplary description of the contract representation of the expansion request in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to represent the expansion request, as long as it is contracted in the protocol.

S402, receiving an expansion response sent by the vehicle-mounted equipment, wherein the expansion response is used for indicating the vehicle-mounted equipment to enter an expansion mode.

After the data reading device transmits the expansion request to the in-vehicle device, referring to fig. 5, the in-vehicle device may receive the expansion request transmitted by the data reading device and enter the expansion mode according to the expansion request. And then sending an expansion response to the data reading device, wherein the expansion response is used for indicating the vehicle-mounted device to enter an expansion mode.

The data reading device may receive the extension response sent by the vehicle-mounted device, thereby determining that the vehicle-mounted device enters the extension mode.

Similar to the above description, since the present embodiment relies on a simple data management protocol for interaction of information and data, it is possible to agree on which bytes in particular represent the extended response, for example. For example, referring to fig. 5, when the in-vehicle apparatus transmits the extension response to the data reading apparatus, "50" 03 "may be transmitted, where" 50 "is a byte for representing the extension response, which is agreed in the present protocol, and it is understood that the remaining content may be further included after 50 03, so that the extension response is represented by a character string at the beginning of" 50 ". Wherein "50" may be, for example, 16-ary, more specifically 50 ₁₆ 03 ₁₆ XX ₁₆ XX ₁₆ XX ₁₆ XX ₁₆ Wherein XX may represent the remaining arbitrary character content.

Then it may be possible for the in-vehicle apparatus ECU to directly transmit the "50" head character string to the data reading apparatus when it is necessary to transmit the expansion response to the data reading apparatus, and the data reading apparatus may also determine that the instruction instructs the in-vehicle apparatus to enter the expansion mode after receiving the "50" head character string.

The above is an exemplary description of the contracted representation of the expanded response in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to represent the expanded response, as long as it is contracted in the protocol.

S403, sending an authentication request to the vehicle-mounted device.

After determining that the vehicle-mounted device enters the extended mode, it indicates that the response data can be acquired from the vehicle-mounted device, and in the simple data management protocol of this embodiment, in order to ensure the security of data transmission, the vehicle-mounted device is required to authenticate the data reading device, and after the authentication passes, the data is read and transmitted.

The data reading device can thus send an authentication request to the in-vehicle device, wherein the authentication request is for requesting the in-vehicle device to authenticate whether the data reading device is permitted to read the data.

Similar to the above description, since the interaction of information and data is performed depending on a simple data management protocol in the present embodiment, it is possible to make a contract as to which specific bytes represent the transmission of the authentication request, for example. For example, referring to fig. 5, the data reading apparatus may transmit "27.08" when the in-vehicle apparatus transmits the authentication request, where "27.08" is a byte agreed in the present protocol for representing transmission of the authentication request, and it is understood that the remaining content may be further included after 27.08, so that the transmission of the authentication request is represented by a character string at the beginning of "27.08". Wherein "27" may be, for example, 16-ary, more specifically expressed as

27 ₁₆ 08 ₁₆ XX ₁₆ XX ₁₆ Wherein XX may represent the remaining arbitrary character content.

Then, for the data reading device, when it is necessary to send an authentication request to the in-vehicle device ECU, it may directly send the character string of the head of "27" to the in-vehicle device ECU, and after receiving the character string of the head of "27" the in-vehicle device ECU may also determine that the instruction is for requesting authentication of the data reading device. It will be appreciated that content following 27 08 may represent, for example, information related to authentication.

The foregoing is an exemplary description of the agreed expression of the transmission of the authentication request in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to represent the transmission of the authentication request, as long as it is agreed in the protocol.

S404, receiving encryption information sent by the vehicle-mounted equipment.

After the data reading device transmits the authentication request to the in-vehicle device, the in-vehicle device needs to authenticate the data reading device in response to the authentication request. In one possible implementation manner, the authentication in this embodiment may be, for example, that the vehicle-mounted device sends an encrypted message to the data reading device, and if the data reading device can decrypt correctly, it indicates that the current data reading device is a trusted device, and because this indicates that the data reading device and the vehicle-mounted device agree on an encryption and decryption algorithm in advance, the data reading device can be trusted, that is, indicates that the data reading device has successfully authenticated.

Therefore, after receiving the authentication request sent by the data reading device, the vehicle-mounted device may send encrypted information to the data reading device according to the authentication request, where the encrypted information may also be referred to as a verification seed, and the verification seed is information after encryption, and the specific implementation of the encrypted information is not limited as long as the encrypted information is information encrypted according to a preset encryption algorithm.

Similar to the above description, since the interaction of information and data is performed depending on a simple data management protocol in the present embodiment, for example, a contract can be made as to which specific bytes represent the transmission of encrypted information. For example, referring to fig. 5, when transmitting the encrypted information to the data reading apparatus, the in-vehicle apparatus may transmit "67.," where "67.," is a byte agreed in the present protocol for representing transmission of the encrypted information, and it is understood that the remaining content may be included after 67 08, so that a character string at the beginning of "67 08" represents transmission of the encrypted information. Wherein "67 08" may be, for example, 16-ary, more specifically, represented as67 ₁₆ 08 ₁₆ XX ₁₆ XX ₁₆ XX ₁₆ XX ₁₆ Wherein XX may represent the remaining arbitrary character content.

Then it may be possible for the in-vehicle apparatus ECU to directly transmit the "67 08" head character string to the data reading apparatus when it is necessary to transmit the encrypted information to the data reading apparatus, and the data reading apparatus may also determine that the instruction indicates that the in-vehicle apparatus transmitted the encrypted information after receiving the "67 08" head character string. It will be appreciated that content following 67 08 may represent encrypted information, for example.

The above is an exemplary description of the agreed expression of the transmission of the encrypted information in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to represent the transmission of the encrypted information, as long as it is agreed in the protocol.

S405, decrypting the encrypted information to obtain the plaintext information.

After receiving the encrypted information, the vehicle-mounted device can adopt a pre-agreed decryption algorithm to decrypt the encrypted information, so as to obtain plaintext information. It will be understood that the plaintext information in this embodiment is information obtained by decrypting the encrypted information.

S406, sending the plaintext information to the vehicle-mounted equipment.

After the data reading device decrypts the plaintext information, the plaintext information may be transmitted to the in-vehicle device.

Similar to the above description, since the present embodiment relies on a simple data management protocol for interaction of information and data, a contract can be made as to which specific bytes represent the transmission of plaintext information, for example. For example, referring to fig. 5, the data reading apparatus may transmit "27 a.," when the in-vehicle apparatus transmits plaintext information to the in-vehicle apparatus, where "27 a.," is a byte agreed in the present protocol for representing transmission of plaintext information, and it is understood that the rest of the content may be included after 27 a, so that a character string at the beginning of "27 a" is provided Representing the transmission of plaintext information. Wherein "27A" may be, for example, 16-ary, more specifically 27 ₁₆ 0A ₁₆ XX ₁₆ XX ₁₆ Wherein XX may represent the remaining arbitrary character content.

Then, for the data reading device, when it is necessary to transmit the plain text information to the in-vehicle device ECU, it may directly transmit the "27 a" leading character string to the in-vehicle device ECU, and after receiving the "27 a" leading character string, the in-vehicle device ECU may also determine that the instruction is for instructing that the current data reading device transmits the plain text information after decryption. It will be appreciated that content after 27 a may represent, for example, plaintext information.

The above is an exemplary description of the agreed representation of the transmission of the plaintext information in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to represent the plaintext information, as long as it is agreed in the protocol.

S407, receiving an authentication result sent by the vehicle-mounted equipment, wherein the authentication result is determined according to the plaintext information.

After the data reading device sends the plaintext information, the corresponding vehicle-mounted device can receive the plaintext information corresponding to the encrypted information sent by the data reading device, and the authentication result is determined according to the plaintext information and preset information corresponding to the encrypted information. In one possible implementation manner, the preset information corresponding to the encrypted information is that the encrypted information is obtained by encrypting the preset information, and when the authentication result is determined according to the plaintext information and the preset information corresponding to the encrypted information, for example, whether the plaintext information and the preset information corresponding to the encrypted information are identical or not may be checked. If the authentication is the same, the authentication is determined to pass, and if the authentication is not the same, the authentication is determined to not pass.

After the in-vehicle apparatus determines the authentication result, the authentication result may be transmitted to the data reading apparatus. Accordingly, the data reading device may receive the authentication result sent by the vehicle-mounted device, and it may be determined based on the above description that the authentication result in this embodiment is determined according to the plaintext information.

Similar to the above description, since the present embodiment relies on a simple data management protocol for interaction of information and data, a convention can be made as to which bytes in particular represent the transmission of the authentication result, for example. For example, referring to fig. 5, when the in-vehicle apparatus transmits the authentication result to the data reading apparatus, "67 a.," where "67 a.," is a byte agreed in the present protocol for representing transmission of the authentication result, it is understood that the remaining content may be further included after 67 a, and thus a character string at the beginning of "67 a" represents transmission of the authentication result. Wherein "67 0A" may be, for example, 16-ary, more specifically 67 ₁₆ 0A ₁₆ XX ₁₆ XX ₁₆ XX ₁₆ XX ₁₆ Wherein XX may represent the remaining arbitrary character content.

Then it may be possible for the in-vehicle apparatus ECU to directly transmit the "67 a" leading character string to the data reading apparatus when it is necessary to transmit the authentication result to the data reading apparatus, and the data reading apparatus may also determine that the instruction is for instructing the in-vehicle apparatus that the authentication result is transmitted after receiving the "67 0a" leading character string. It will be appreciated that 67 and 0a may be followed by an authentication result, for example.

The foregoing is an exemplary description of the agreed expression of the transmission of the authentication result in the simple data management protocol in this embodiment, and in the actual implementation process, any data may be used to represent the transmission of the authentication result, as long as it is agreed in the protocol.

And S408, when the authentication result is that the authentication is successful, sending a data reading request to the vehicle-mounted equipment.

The authentication result in this embodiment may be authentication failure or authentication success. When the authentication result is authentication failure, the current data reading equipment is not allowed to read the data, and the data reading flow is ended.

Or when the authentication result is that the authentication is successful, the current data reading device is allowed to read data, and the data reading device may send a data reading request to the vehicle-mounted device, for example, where the data reading request in this embodiment is used to request to read the first vehicle-mounted device, it may be understood that the vehicle-mounted device needs to be informed about the first vehicle-mounted device to read, and specifically, what data is required to be read in the data reading request.

In one possible implementation, for example, the identities of the plurality of sub-data may be determined, after which a data read request is sent to the vehicle-mounted device, in which the identities of the plurality of sub-data are included. The identification of the sub-data may be, for example, a method identification of requesting to read, a parameter identification of requesting to read, etc., which is not limited in this embodiment.

In a simple data management protocol, for example, the request format of the data read request may be understood with reference to fig. 6, and as shown in fig. 6, the request format of the data read request may include a request method and n request parameters, where the request method and the request parameters are the sub data described above. The request format shown in fig. 6 can also be understood as a message format of the simple data management protocol SDMP.

The frame structure of the data read request is described in more detail below with reference to fig. 7. As shown in fig. 7, the SDMP request (i.e., the data read request) may be encapsulated in a payload (payload) portion of the DoIP frame, and a Header (DoIP Header), a Source Address (Source Address), and a destination Address (Target Address) of the DoIP frame are also included in the DoIP frame.

And, after encapsulating the DoIP frame, encapsulating the DoIP frame in an ethernet frame as a payload (payload) portion of the ethernet frame. Alternatively, the SDMP request (i.e., the data read request) may also be encapsulated directly in the payload (payload) portion of the ethernet frame in this embodiment. And as shown in fig. 7, the Ethernet frame further includes a frame Header (Ethernet Header), an IP frame Header, a TCP/UDP frame Header, and a frame check sequence (Frame Check Sequences, FCS).

Based on the frame structure, orderly data transmission can be performed between the data reading equipment and the vehicle-mounted equipment, so that unified management of vehicle-mounted data is realized.

The foregoing describes an implementation in which the request messages of the SDMP data read request are encapsulated independently in DoIP frames or ethernet frames. In another possible implementation, the request message of the SDMP protocol may also be converted to an absolute path based on the 04 subfunction of the 0x38 service of the UDS diagnostic protocol, and the absolute path included in the data read request. The absolute path in the present embodiment may be a storage address of the first driving data in the in-vehicle apparatus.

The data reading device may determine the memory address of the first vehicle data in the vehicle-mounted device and then send a data reading request to the vehicle-mounted device, wherein the memory capacity, i.e. the absolute path described above, may be included in the data reading request.

The data reading device may, for example, directly acquire the storage address of the first driving data in the vehicle-mounted device.

The following describes an implementation manner of determining the absolute address of the request packet in conjunction with fig. 8, as shown in fig. 8, for example, the request packet of the SDMP may be converted into an SDMP request absolute path, where an execution standard (protocol), a standard number (version), for example/GB/14299/XXXX, may be included in the SDMP request absolute path, and each request parameter and a description of each request parameter may be included in the SDMP request absolute path, where the description of the request parameter may be, for example, a storage location in the vehicle device.

The absolute path may then be encapsulated in a UDS frame, for example, referring to fig. 8, in which the absolute path may be encapsulated, and the UDS frame header, and 38 04 may be a preset byte content for representing the transmission of the data read request.

On the basis of fig. 8, 801 in fig. 8 may be considered as a UDS frame+sdmp frame, and referring to fig. 9, when transmitting a data read request including an absolute path, for example, the UDS frame+sdmp frame (i.e., a data read request including an absolute path) may be encapsulated in a payload (payload) portion of a DoIP frame, and a Header (DoIP Header), a Source Address (Source Address), and a destination Address (Target Address) of the DoIP frame may be further included in the DoIP frame.

And, after encapsulating the DoIP frame, encapsulating the DoIP frame in an ethernet frame as a payload (payload) portion of the ethernet frame. And as shown in fig. 9, the Ethernet frame further includes a frame Header (Ethernet Header), an IP frame Header, a TCP/UDP frame Header, and a frame check sequence (Frame Check Sequences, FCS).

The above describes the message format of the data read request and the frame format in which the data read request is transmitted. And similar to the above description, since the present embodiment relies on a simple data management protocol for interaction of information and data, a convention can be made as to which bytes specifically represent the transmission of a data read request, for example. For example, referring to fig. 5, the data reading apparatus may transmit "38 04.+ -. When the in-vehicle apparatus transmits the data reading request, where" 38 04..+ -. Is a byte agreed in the present protocol for representing transmission of the data reading request, and it is understood that the remaining content may be further included after 38 04, so that the transmission of the data reading request is represented by a character string at the beginning of "38 04". Wherein "38 04" may be, for example, 16-ary, more specifically 38 ₁₆ 04 ₁₆ XX ₁₆ ...XX ₁₆ Wherein XX ₁₆ …XX ₁₆ For example, the SDMP request message or the absolute path of the SDMP message described above may be represented.

Then, for the data reading device, when it is necessary to send a data reading request to the in-vehicle device ECU, it may directly send the character string at the beginning of "38" to the in-vehicle device ECU, and after receiving the character string at the beginning of "38 04", the in-vehicle device ECU may also determine that the instruction indicates that the current data reading device sent the data reading request. The content following 38 04 may represent, for example, an identification of the first drive data specifically requested by the data read request.

The above is an exemplary description of the agreed representation of the transmission of the data read request in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to represent the data read request, as long as it is agreed in the protocol.

S409, receiving a data reading response corresponding to the data reading request sent by the vehicle-mounted device.

After the data reading device sends the data reading request to the vehicle-mounted device, the vehicle-mounted device may correspondingly receive the data reading request sent by the data reading device, where the data reading request includes identifiers of a plurality of sub-data or a storage address of the first vehicle data in the vehicle-mounted device. The vehicle-mounted device may send a data read response to the data reading device according to the data read request, where the data read response is used to indicate that the first driving data is determined to be sent to the data reading device.

It should be noted that the data reading request and the data reading response of the current interaction are only that the data reading device requests to read the first driving data, and the vehicle-mounted device agrees that the data reading device reads the first driving data, but the transmission of the first driving data is not actually performed yet. And the vehicle-mounted device may perform preprocessing on the first driving data, for example, including data division, format conversion, and the like, while agreeing to the data reading device to read the first driving data.

Similar to the above description, since the present embodiment relies on a simple data management protocol for interaction of information and data, a convention can be made as to which specific bytes represent the transmission of the data read response, for example. For example, referring to fig. 5, when the in-vehicle apparatus transmits the data read response to the data read apparatus, "78 04.," where "78 04.," is a byte agreed in the present protocol for representing transmission of the data read response, it is understood that the remaining content may be further included after 78 04, and thus a character string at the beginning of "78 04" represents transmission of the data read response. Wherein "78 04" may be, for example, 16-ary, more specifically expressed as 78 ₁₆ 04 ₁₆ XX ₁₆ …XX ₁₆ Wherein XX may represent the remaining arbitrary character content.

Then it may be possible for the in-vehicle apparatus ECU to directly transmit the "78" leading character string to the data reading apparatus when it is necessary to transmit the data reading response to the data reading apparatus, and the data reading apparatus may also determine that the instruction is for instructing the in-vehicle apparatus that the data reading response is transmitted after receiving the "78 04" leading character string. It will be appreciated that content following 78 04 may represent, for example, a data read response.

The above is an exemplary description of the agreed expression of the transmission of the data read response in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to represent the transmission of the data read response, as long as it is agreed in the protocol.

S410, determining that the vehicle-mounted device agrees to send the first driving data to the data reading device according to the data reading response.

The data reading response in the present embodiment may indicate whether the in-vehicle apparatus agrees to transmit the first driving data to the data reading apparatus. For example, the data reading device may determine that the vehicle-mounted device agrees to send the first driving data to the data reading device according to the data reading response, and then read the data.

Or if the data reading device determines that the vehicle-mounted device does not agree to send the first driving data to the data reading device according to the data reading response, the data reading device may end the data reading flow, for example.

S411, respectively sending N data transmission requests to the vehicle-mounted equipment, and receiving N data transmission responses corresponding to the N data transmission requests; the ith data transmission request comprises an identification of the ith sub data, the ith data transmission response comprises the ith sub data, and i is an integer between 1 and N.

After the data reading device determines that the vehicle-mounted device agrees to send the first vehicle data to the data reading device according to the data reading response, the data reading device can respectively send N data transmission requests to the vehicle-mounted device, and then correspondingly receives N data transmission responses corresponding to the N data transmission requests sent by the vehicle-mounted device respectively.

In one possible implementation, when the data reading device sends N data transmission requests to the vehicle-mounted device, for example, the ith data transmission request may be sequentially sent to the vehicle-mounted device.

If i is 1, it indicates that the 1 st data transmission request is transmitted, and the 1 st data transmission request may be directly sent to the in-vehicle device.

If i is greater than 1, indicating that the transmission has not been the 1 st data transmission request, the i-1 st data transmission request may be sent to the in-vehicle apparatus after determining that the i-1 st data transmission response is received.

That is, in this embodiment, the data transmission request and the data transmission response may be that the data reading device sends a data transmission request to the vehicle-mounted device, and the corresponding vehicle-mounted device sends the data transmission response corresponding to the data transmission request to the data reading request, and sequentially executes the data transmission request and the data transmission response until all the N data transmission requests and the data transmission response are interactively completed, so that the data reading device may acquire N sub-data.

Similar to the above description, since the interaction of information and data is performed depending on a simple data management protocol in the present embodiment, for example, a contract can be made as to which specific bytes represent the transmission of the data transmission request. For example, referring to fig. 5, the data reading device may transmit "36" when the in-vehicle device transmits a data transmission request, where "36" is a byte agreed in the present protocol for representing transmission of the data transmission request, it will be appreciated that the remainder of the content may also be included after 36, so that a string beginning with "36" indicates the transmission of a data transmission request. Wherein "36" may be, for example, 16-ary, more specifically denoted 36 ₁₆ XX ₁₆ Wherein XX ₁₆ For example, the ith sub-data currently requested for transmission may be represented.

Then, for the data reading device, when it is necessary to send a data transmission request to the in-vehicle device ECU, it may directly send the "36" head character string to the in-vehicle device ECU, and after receiving the "36" head character string, the in-vehicle device ECU may also determine that the instruction indicates that the current data reading device sent the data transmission request. The content following 36 may for example represent an identification of the sub-data specifically requested by the data transfer request.

The above is an exemplary description of the agreed expression of the transmission of the data transmission request in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to represent the data transmission request, as long as it is agreed in the protocol.

Accordingly, similar to the description above, since the present embodiment relies on a simple data management protocol for interaction of information and data, a contract can be made as to which bytes specifically represent the transmission of the data transmission response, for example. For example, referring to fig. 5, when the in-vehicle apparatus transmits the data transmission response to the data reading apparatus, "76.," where "76.," is a byte agreed in the present protocol for representing the transmission of the data transmission response, it will be understood that the rest of the content may be included after 76, so that the transmission of the data transmission response is represented by a character string at the beginning of "76". Wherein "76" may be, for example, 16-ary, and more specifically may be denoted as 76 ₁₆ XX ₁₆ ...XX ₁₆ Wherein XX ₁₆ ...XX ₁₆ For example, the ith sub-data currently transmitted may be represented.

Then it may be possible for the in-vehicle apparatus ECU to directly transmit the "76" head character string to the data reading apparatus when it is necessary to transmit the data transmission response to the data reading apparatus, and the data reading apparatus may also determine that the instruction indicates that the in-vehicle apparatus transmitted the data transmission response after receiving the "76" head character string. It will be appreciated that content following 76 may represent, for example, specific sub-data content of the data transfer response.

The above is an exemplary description of the agreed expression of the transmission of the data transmission response in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to represent the transmission of the data transmission response, as long as it is agreed in the protocol.

Referring to fig. 5, after the data reading apparatus and the in-vehicle apparatus transmit one data slice (i.e., sub data) is completed, it may be determined whether N sub data in the current first driving data are read to be completed. If the reading is not completed, repeating the process of transmitting the sub-data until the reading and the transmission of the N sub-data in the first driving data are completed.

Further, the description of the message structure of the data transmission response returned by the vehicle-mounted device can be also described with reference to fig. 10. As shown in fig. 10, a response result, a response code, a response description, and data, which is the ith sub-data of the ith transmission, may be included in a response format of the data transmission response. The request format shown in fig. 10 can also be understood as a message format of the simple data management protocol SDMP.

And the transmission of the data transmission message can also follow the frame format of the DoIP frame and/or the ethernet frame described above, and the implementation manner is similar to that described above, and will not be repeated here.

S412, sending a transmission termination request to the vehicle-mounted equipment.

After the data reading device determines that the data reading is completed, a transmission termination request for requesting and the vehicle-mounted device to end the transmission of the data may be transmitted to the vehicle-mounted device.

Similar to the above description, in this embodiment, the interaction of information and data is performed by means of a simple data management protocol, and then, for example, a contract may be made as to which bytes in particular represent the termination of the transmission request. For example, referring to fig. 5, the data reading device may transmit "37" when transmitting the transmission termination request to the in-vehicle device, where "37" is a byte agreed in the present protocol for representing the transmission termination request, and "37" therein " For example, may be 16-ary, and more particularly may be represented as 37 ₁₆ 。

Then, for the data reading device, it may send "37" directly to the in-vehicle device ECU when it is necessary to send a transmission termination request to the in-vehicle device ECU, and the in-vehicle device ECU may determine that the instruction is for requesting the in-vehicle device to terminate transmission of data after receiving "37".

The above is an exemplary description of the manner in which the terminating transmission request is expressed in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to express the terminating transmission request, as long as it is agreed in the protocol.

S413, receiving a termination transmission response corresponding to the termination transmission request sent by the vehicle-mounted device.

After the data transmission device sends the transmission termination request to the vehicle-mounted device, correspondingly, the vehicle-mounted device can receive the transmission termination request sent by the data reading device, and the vehicle-mounted device can terminate sending data to the data reading device and send a transmission termination response to the data reading device according to the transmission termination request. Wherein the termination transmission response is used to instruct the in-vehicle device to determine to terminate transmission of the data.

Similar to the above description, since the present embodiment relies on a simple data management protocol for interaction of information and data, it is possible to make a contract as to which specific bytes represent the termination of the transmission response, for example. For example, referring to fig. 5, the in-vehicle apparatus may transmit "77" when transmitting the termination transmission response to the data reading apparatus, where "77" is a byte agreed in the present protocol for representing the termination transmission response. Wherein "77" may be, for example, 16-ary, more specifically indicated as 77 ₁₆ 。

Then it may be possible for the in-vehicle apparatus ECU to directly transmit "77" to the data reading apparatus when it is necessary to transmit the termination transmission response to the data reading apparatus, and the data reading apparatus may also determine the instruction for instructing the in-vehicle apparatus to determine termination of data transmission after receiving "77".

The above is an exemplary description of the agreed representation of the termination transmission response in the simple data management protocol in this embodiment, and in the actual implementation, any data may be used to represent the termination transmission response, as long as it is agreed in the protocol.

S414, acquiring first driving data in N data transmission responses.

After the data reading device receives the N data transmission responses, N pieces of sub data may be acquired, so that the first driving data may be acquired in the N data transmission responses.

According to the driving data transmission method, the pre-interaction processing is carried out on the vehicle-mounted equipment and the data reading equipment before the data reading and transmission are carried out, wherein the pre-interaction processing can comprise the steps of requesting the vehicle-mounted equipment to enter an expansion mode, authenticating the data reading equipment and judging whether the first driving data required to be read by the data reading equipment can be transmitted or not, so that the pre-interaction processing stage can be guaranteed, the preconditions for the subsequent data processing are effectively prepared, and further, whether the vehicle-mounted equipment determines to send the first driving data to the data reading equipment or not is determined, and the safety of the transmission of the vehicle-mounted data can be effectively guaranteed. Meanwhile, when the specific transmission is carried out on the first driving data, repeated requests and responses of sub-data are carried out so as to realize the fragmented transmission of the first driving data, thereby effectively ensuring that the effective transmission of the large-quantity vehicle-mounted data can be realized. In the method, the corresponding byte representation of each request and response can be predefined in a simple data management protocol, so that the vehicle-mounted equipment and the data reading equipment can be ensured to realize orderly and stable data transmission.

The foregoing description is a driving data transmission method on the side of the data reading device, and the following description is made on the driving data transmission method on the side of the vehicle-mounted device with reference to fig. 11, and fig. 11 is a flowchart III of the driving data transmission method provided in the embodiment of the disclosure.

As shown in fig. 11, the method includes:

s1101, performing pre-interaction processing with the data reading device to determine to send first driving data to the data reading device, wherein the first driving data comprises N pieces of sub-data, and N is an integer greater than or equal to 1.

S1102, receiving N data transmission requests sent by a data reading device, and sending N data transmission responses corresponding to the N data transmission requests to the data reading device;

the ith data transmission request comprises an identification of ith sub data, the ith data transmission response comprises the ith sub data, and i is an integer between 1 and N.

Various possible implementation manners of the driving data transmission method on the vehicle-mounted device side are similar to those on the data reading device side described in the above embodiment, and all the possible implementation manners of the driving data transmission method on the vehicle-mounted device side can refer to the description of the above embodiment, and are not repeated herein.

The driving data transmission method provided by the embodiment of the disclosure comprises the following steps: pre-interaction processing is carried out with the data reading device to determine that first driving data is sent to the data reading device, wherein the first driving data comprises N pieces of sub-data, and N is an integer greater than or equal to 1. Receiving N data transmission requests sent by data reading equipment, and sending N data transmission responses corresponding to the N data transmission requests to the data reading equipment; the ith data transmission request comprises an identification of ith sub data, the ith data transmission response comprises the ith sub data, and i is an integer between 1 and N. After the vehicle-mounted device performs pre-interaction processing on the data reading device, the vehicle-mounted device receives N data transmission requests sent by the data reading device for acquiring the first vehicle data after confirming that the vehicle-mounted device agrees to read the first vehicle data, and then sends the first vehicle data to the data reading device through N data transmission responses, so that the first vehicle data can be transmitted in a fragmented mode, and further the reading and the transmission of a large amount of data can be supported.

Fig. 12 is a schematic structural diagram of a driving data transmission device according to an embodiment of the disclosure. As shown in fig. 12, the driving data transmission apparatus 1200 of the present embodiment may include: a processing module 1201, a transmission module 1202, and an acquisition module 1203.

A processing module 1201, configured to perform pre-interaction processing with a vehicle-mounted device, so as to determine that the vehicle-mounted device agrees to send first driving data to the data reading device, where the first driving data includes N pieces of sub-data, and N is an integer greater than or equal to 1;

a transmission module 1202, configured to send N data transmission requests to the vehicle-mounted device, and receive N data transmission responses corresponding to the N data transmission requests, respectively; the ith data transmission request comprises an identification of the ith sub data, and the ith data transmission response comprises the ith sub data, wherein i is an integer between 1 and N;

an obtaining module 1203 is configured to obtain the first driving data in the N data transmission responses.

In a possible implementation manner, the transmission module 1202 is specifically configured to:

the method comprises the steps of sending an ith data transmission request to the vehicle-mounted equipment, and receiving an ith data transmission response corresponding to the ith data transmission request;

Wherein i is 1, 2, … … and N in sequence.

if the i is 1, an i-th data transmission request is sent to the vehicle-mounted equipment;

and if the i is greater than 1, sending an i-1 data transmission request to the vehicle-mounted equipment after the i is determined to receive the i-1 data transmission response.

In a possible implementation manner, the processing module 1201 is specifically configured to:

requesting the vehicle-mounted equipment to enter an expansion mode;

requesting the vehicle-mounted equipment to perform authentication processing on the data reading equipment to obtain an authentication result;

when the authentication result is that the authentication is successful, sending a data reading request to the vehicle-mounted equipment;

receiving a data reading response corresponding to the data reading request sent by the vehicle-mounted equipment;

and determining that the vehicle-mounted equipment agrees to send the first driving data to the data reading equipment according to the data reading response.

sending an expansion request to the vehicle-mounted equipment;

and receiving an expansion response sent by the vehicle-mounted equipment, wherein the expansion response is used for indicating the vehicle-mounted equipment to enter an expansion mode.

sending an authentication request to the vehicle-mounted equipment;

receiving encryption information sent by the vehicle-mounted equipment;

decrypting the encrypted information to obtain plaintext information;

transmitting the plaintext information to a vehicle-mounted device;

and receiving the authentication result sent by the vehicle-mounted equipment, wherein the authentication result is obtained according to the plaintext information.

determining the identifiers of the plurality of sub-data, and sending the data reading request to the vehicle-mounted equipment, wherein the data reading request comprises the identifiers of the plurality of sub-data; or alternatively, the process may be performed,

and determining a storage address of the first driving data in the vehicle-mounted equipment, and sending the data reading request to the vehicle-mounted equipment, wherein the data reading request comprises the storage address.

In a possible implementation manner, the processing module 1201 is further configured to:

after the first driving data is acquired from the N data transmission responses, a transmission termination request is sent to the vehicle-mounted equipment;

and receiving a termination transmission response corresponding to the termination transmission request sent by the vehicle-mounted equipment.

Fig. 13 is a second schematic structural diagram of a driving data transmission device according to an embodiment of the disclosure. As shown in fig. 13, the driving data transmission apparatus 1300 of the present embodiment may include: processing module 1301, transmission module 1302.

A processing module 1301, configured to perform pre-interaction processing with a data reading device, so as to determine to send first driving data to the data reading device, where the first driving data includes N pieces of sub-data, and N is an integer greater than or equal to 1;

a transmission module 1302, configured to receive N data transmission requests sent by the data reading device, and send N data transmission responses corresponding to the N data transmission requests to the data reading device;

In a possible implementation manner, the transmission module 1302 is specifically configured to:

the method comprises the steps of receiving an ith data transmission request sent by the data reading equipment, and sending an ith data transmission response corresponding to the ith data transmission request to the data reading equipment;

wherein i is 1, 2, … … and N in sequence.

if the i is 1, sending an ith data transmission response corresponding to the ith data transmission request to the data reading equipment;

and if the i is greater than 1, after the i-1 th data transmission response is determined to be sent to the data reading device, sending the i-1 th data transmission response to the data reading device.

In a possible implementation manner, the processing module 1301 is specifically configured to:

entering an expansion mode;

performing authentication processing on the data reading equipment to obtain an authentication result, and sending the authentication result to the data reading equipment;

when the authentication result is that the authentication is successful, receiving a data reading request sent by the data reading device, wherein the data reading request comprises identifiers of the plurality of sub-data or storage addresses of the first driving data in the vehicle-mounted device;

and sending a data reading response to the data reading device according to the data reading request, wherein the data reading response is used for indicating to determine to send the first driving data to the data reading device.

Receiving an expansion request sent by the data reading equipment;

and entering an expansion mode according to the expansion request, and sending an expansion response to the data reading device, wherein the expansion response is used for indicating the vehicle-mounted device to enter the expansion mode.

receiving an authentication request sent by the data reading equipment;

sending encryption information to the data reading equipment according to the authentication request;

receiving plaintext information corresponding to the encrypted information sent by the data reading equipment;

and determining the authentication result according to preset information corresponding to the plaintext information and the encrypted information.

In a possible implementation manner, the processing module 1301 is further configured to:

after the first driving data is acquired from the N data transmission responses, receiving a transmission termination request sent by the data reading equipment;

and according to the transmission termination request, terminating sending data to the data reading device, and sending a transmission termination response to the data reading device.

The disclosure provides a driving data transmission method and device, which are applied to the field of automatic driving in the field of data processing, so as to achieve the aim of realizing mass reading and transmission of vehicle-mounted data in automatic driving. And further, the requirements of future vehicle fault diagnosis, accident responsibility judgment, accident inversion, automatic driving algorithm tuning and the like on data diversified management can be met.

Note that, the head model in this embodiment is not a head model for a specific user, and cannot reflect personal information of a specific user. It should be noted that, the two-dimensional face image in this embodiment is derived from the public data set.

In the technical scheme of the disclosure, the related processes of collecting, storing, using, processing, transmitting, providing, disclosing and the like of the personal information of the user accord with the regulations of related laws and regulations, and the public order colloquial is not violated.

According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

According to an embodiment of the present disclosure, the present disclosure also provides a computer program product comprising: a computer program stored in a readable storage medium, from which at least one processor of an electronic device can read, the at least one processor executing the computer program causing the electronic device to perform the solution provided by any one of the embodiments described above.

Fig. 14 shows a schematic block diagram of an example electronic device 1400 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 14, the apparatus 1400 includes a computing unit 1401 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 1402 or a computer program loaded from a storage unit 1408 into a Random Access Memory (RAM) 1403. In the RAM 1403, various programs and data required for the operation of the device 1400 can also be stored. The computing unit 1401, the ROM 1402, and the RAM 1403 are connected to each other through a bus 1404. An input/output (I/O) interface 1405 is also connected to the bus 1404.

Various components in device 1400 are connected to I/O interface 1405, including: an input unit 1406 such as a keyboard, a mouse, or the like; an output unit 1407 such as various types of displays, speakers, and the like; a storage unit 1408 such as a magnetic disk, an optical disk, or the like; and a communication unit 1409 such as a network card, a modem, a wireless communication transceiver, and the like. The communication unit 1409 allows the device 1400 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunications networks.

The computing unit 1401 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 1401 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 1401 performs the respective methods and processes described above, for example, a driving data transmission method. For example, in some embodiments, the method of driving data transmission may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as the storage unit 1408. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 1400 via the ROM 1402 and/or the communication unit 1409. When the computer program is loaded into the RAM 1403 and executed by the computing unit 1401, one or more steps of the driving data transmission method described above may be performed. Alternatively, in other embodiments, the computing unit 1401 may be configured to perform the driving data transmission method by any other suitable means (e.g. by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the internet.

The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service ("Virtual Private Server" or simply "VPS") are overcome. The server may also be a server of a distributed system or a server that incorporates a blockchain.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel or sequentially or in a different order, provided that the desired results of the technical solutions of the present disclosure are achieved, and are not limited herein.

The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.

Claims

1. A driving data transmission method applied to a data reading device, the method comprising:

sending an authentication request to the vehicle-mounted device, wherein the authentication request is used for requesting the vehicle-mounted device to authenticate whether the data reading device is allowed to read data;

receiving an authentication result sent by the vehicle-mounted equipment;

when the authentication result is that the authentication is successful, sending a data transmission request to the vehicle-mounted equipment, and receiving a data transmission response corresponding to the data transmission request;

And acquiring first driving data in the data transmission response.

2. The method of claim 1, the method further comprising, prior to receiving the authentication result sent by the vehicle-mounted device:

receiving encryption information sent by vehicle-mounted equipment;

decrypting the encrypted information to obtain plaintext information;

the authentication result is obtained according to the plaintext information.

3. The method of claim 2, wherein the decrypting the encrypted information to obtain plaintext information comprises:

and carrying out decryption processing on the encrypted information according to a decryption algorithm to obtain the plaintext information, wherein the decryption algorithm is agreed in advance for the data reading equipment and the vehicle-mounted equipment.

4. A method according to any one of claims 1-3, the method further comprising, prior to sending the authentication request to the in-vehicle device:

sending an expansion request to the vehicle-mounted equipment;

5. A driving data transmission method applied to vehicle-mounted equipment, the method comprising:

Receiving an authentication request sent by a data reading device, wherein the authentication request is used for requesting the vehicle-mounted device to authenticate whether the data reading device is allowed to read data or not;

sending an authentication result to the data reading device;

and receiving a data transmission request sent by the data reading equipment, and sending a data transmission response corresponding to the data transmission request to the data reading equipment, wherein the data transmission response comprises first driving data.

6. The method of claim 5, the method further comprising, prior to sending the authentication result to the data reading device:

sending encryption information to the data reading device;

7. The method of claim 6, wherein the determining the authentication result according to the preset information corresponding to the plaintext information and the encrypted information comprises:

checking whether preset information corresponding to the plaintext information and the encrypted information is the same or not;

If the authentication result is the same, the authentication result is determined to be successful.

8. The method of any of claims 5-7, the method further comprising, prior to sending the encrypted information to the data reading device:

receiving an expansion request sent by the data reading equipment;

9. A driving data transmission device applied to a data reading apparatus, the device comprising:

a sending module, configured to send an authentication request to a vehicle-mounted device, where the authentication request is used to request the vehicle-mounted device to authenticate whether the data reading device is allowed to perform data reading;

the receiving module is used for receiving the authentication result sent by the vehicle-mounted equipment;

the sending module is further used for sending a data transmission request to the vehicle-mounted equipment and receiving a data transmission response corresponding to the data transmission request when the authentication result is that the authentication is successful;

and the processing module is used for acquiring the first driving data in the data transmission response.

10. The apparatus of claim 9, the receiving module further configured to receive encryption information sent by the vehicle-mounted device before receiving the authentication result sent by the vehicle-mounted device;

The processing module is further configured to: decrypting the encrypted information to obtain plaintext information;

the authentication result is obtained according to the plaintext information.

11. The apparatus of claim 10, wherein the processing module is specifically configured to:

12. The apparatus of any of claims 9-11, the sending module further to:

before sending an authentication request to the vehicle-mounted equipment, sending an expansion request to the vehicle-mounted equipment;

the receiving module is further configured to: and receiving an expansion response sent by the vehicle-mounted equipment, wherein the expansion response is used for indicating the vehicle-mounted equipment to enter an expansion mode.

13. A driving data transmission device applied to a vehicle-mounted device, the device comprising:

the vehicle-mounted device comprises a receiving module, a data reading device and a receiving module, wherein the receiving module is used for receiving an authentication request sent by the data reading device, and the authentication request is used for requesting the vehicle-mounted device to authenticate whether the data reading device is allowed to read data or not;

The sending module is used for sending an authentication result to the data reading equipment;

the receiving module is further configured to receive a data transmission request sent by the data reading device, and send a data transmission response corresponding to the data transmission request to the data reading device, where the data transmission response includes first driving data.

14. The apparatus of claim 13, the transmitting module further to: transmitting encryption information to the data reading device before transmitting an authentication result to the data reading device;

the receiving module is further configured to: receiving plaintext information corresponding to the encrypted information sent by the data reading equipment;

the apparatus further comprises: a processing module;

the processing module is used for determining the authentication result according to the plaintext information and preset information corresponding to the encrypted information.

15. The apparatus of claim 14, wherein the processing module is specifically configured to:

16. The apparatus of any of claims 13-15, the receiving module further to:

Before sending encryption information to the data reading equipment, receiving an expansion request sent by the data reading equipment;

the processing module is further configured to: and entering an expansion mode according to the expansion request, and sending an expansion response to the data reading device, wherein the expansion response is used for indicating the vehicle-mounted device to enter the expansion mode.

17. An electronic device, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-4 or claims 5-8.

18. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-4 or claims 5-8.

19. A computer program product comprising a computer program which, when executed by a processor, implements the steps of the method of any of claims 1-4 or claims 5-8.