A vehicle-mounted multi-system data interaction method and device and a vehicle

Abstract

The application provides a vehicle-mounted multi-system data interaction method and device and a vehicle. The method comprises the following steps: receiving a first data frame sent by a first data transceiver; the first data transceiver is any one of a plurality of data transceivers; splitting and recombining the first data frame into second data frames required by each second data transceiver; the second data transceiver is a data transceiver different from the first data transceiver in the plurality of data transceivers; and sending each second data frame to the corresponding second data transceiver. The application can not only realize data interaction between multiple data transceivers, but also accept control and processing of the flow direction and frame content of the data frame sent from the sending point in the middle of the way, so that the data is not forwarded to the data transceiver that does not need the data, and the efficiency of data receiving and processing of the receiving point is improved.

Description

Technical Field

[0001] This invention relates to the field of automotive technology, and in particular to a method, device, and vehicle for data interaction among multiple in-vehicle systems. Background Technology

[0002] Currently, with the development of automotive intelligence, the functions of in-vehicle systems are becoming increasingly rich, leading to more frequent data interactions between in-vehicle systems.

[0003] However, in existing in-vehicle systems, data processing during data interaction is handled by data transceiver nodes. For example, when data is transmitted to the master control unit, the entire frame of data is processed there; similarly, when data is transmitted to the slave control unit, the entire frame is processed there. This approach not only results in low efficiency for data reception and processing at the data receiving point but also makes it prone to receiving unwanted data. Consequently, it fails to meet the needs of rapid data interaction between multiple in-vehicle systems, potentially causing inconvenience to users. Summary of the Invention

[0004] This invention provides a method, apparatus, and vehicle for data interaction between multiple in-vehicle systems, in order to solve the problem that existing technologies cannot efficiently achieve data interaction between multiple in-vehicle systems.

[0005] In a first aspect, embodiments of the present invention provide a method for data interaction between multiple vehicle systems, the method comprising:

[0006] Receive a first data frame sent by a first data transceiver point; the first data transceiver point is any one of a plurality of data transceiver points;

[0007] The first data frame is split and reassembled into the second data frames required by each second data transceiver point. The second data transceiver point is a data transceiver point that is different from the first data transceiver point among the plurality of data transceiver points.

[0008] Each of the second data frames is sent to the corresponding second data transceiver point.

[0009] Optionally, in the data interaction method, splitting and reassembling the first data frame into the second data frames required by each second data transceiver point includes:

[0010] According to the control parameters, the first data frame is split into identifiable data units; wherein, the control parameters determine the identifiable data units corresponding to each data transmission and reception point;

[0011] Based on the control parameters, each of the identifiable data units is marked according to its corresponding data transmission and reception point;

[0012] Based on the marker, each of the identifiable data units is reassembled into each of the second data frames.

[0013] Optionally, in the data interaction method, marking each identifiable data unit according to its corresponding data transmission and reception point based on the control parameters includes:

[0014] According to the control parameters, each identifiable data unit is marked to the physical address matching the second data transceiver point according to its corresponding second data transceiver point.

[0015] Optionally, before the step of splitting and reassembling the first data frame into the second data frames required by each second data transceiver point, the method further includes:

[0016] Determine the validity of the first data frame;

[0017] If the first data frame is determined to be invalid, the first data frame is discarded.

[0018] If the first data frame is determined to be valid, the step of splitting the first data frame and reassembling it into the second data frames required by each second data transceiver point is performed.

[0019] Optionally, before determining the validity of the first data frame, the method further includes:

[0020] Based on the format of the data frame, calculate the first check data of the entire data content, frame header data and frame tail data in the first data frame, and compare it with the second check data carried by the first data frame to verify the first data frame.

[0021] After the first data frame passes verification, the step of determining the validity of the first data frame is executed.

[0022] Optionally, in the data interaction method, determining the validity of the first data frame includes:

[0023] If each data unit in the first data frame meets the validity determination criteria, then the first data frame is determined to be valid; the determination criteria include the definition format requirements of the real vehicle data, the space occupied by the data definition, and the value range;

[0024] If the data units in the first data frame do not meet the determination conditions, then the first data frame is determined to be invalid.

[0025] Secondly, embodiments of the present invention provide an in-vehicle multi-system data interaction device, the device comprising:

[0026] A data receiving unit is configured to receive a first data frame sent by a first data transceiver point; the first data transceiver point is any one of a plurality of data transceiver points.

[0027] The data processing unit is used to split the first data frame and reassemble it into second data frames required by each second data transceiver point, wherein the second data transceiver point is a data transceiver point that is different from the first data transceiver point among the plurality of data transceiver points;

[0028] The data transmission unit is used to send each of the second data frames to the corresponding second data transceiver point.

[0029] Optionally, in the data interaction device, the data processing unit includes:

[0030] The sub-unit is used to split the first data frame into identifiable data units according to the control parameters; wherein the control parameters determine the identifiable data units corresponding to each data transmission and reception point.

[0031] The marking subunit is used to mark each of the identifiable data units according to the corresponding data transmission and reception points based on the control parameters.

[0032] An assembly subunit is used to reassemble each of the identifiable data units into each of the second data frames according to the marker.

[0033] Optionally, the marking subunit is specifically used to mark each of the identifiable data units to the physical address matching the second data transceiver point according to the control parameters.

[0034] Optionally, in the data interaction device, the data processing unit further includes:

[0035] The determination subunit is used to determine the validity of the first data frame before reassembling the first data frame into the second data frames required by each second data transceiver point after splitting the first data frame;

[0036] A discard subunit is configured to discard the first data frame if it is determined that the first data frame is invalid.

[0037] The first execution subunit is configured to, when it is determined that the first data frame is valid, execute the step of splitting the first data frame and reassembling it into the second data frames required by each second data transceiver point.

[0038] Optionally, in the data interaction device, the data processing unit further includes:

[0039] The verification subunit is used to calculate the first verification data of the entire data content, frame header data and frame tail data in the first data frame according to the format of the first data frame before determining the validity of the first data frame, and compare it with the second verification data carried by the first data frame to verify the first data frame.

[0040] The second execution subunit is used to perform the step of determining the validity of the first data frame after the first data frame has passed the verification.

[0041] Optionally, the determining subunit is specifically used to determine that the first data frame is valid if each data unit in the first data frame meets the validity determination conditions; the determination conditions include the definition format requirements of the real vehicle data, the space occupied by the data definition, and the value range; if the data units in the first data frame do not meet the determination conditions, the first data frame is determined to be invalid.

[0042] Thirdly, embodiments of the present invention provide an electronic device, including: a processor, a communication interface, a memory, and a communication bus; wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0043] Memory, used to store computer programs;

[0044] When the processor executes the program stored in the memory, it implements the steps in the vehicle-mounted multi-system data interaction method described in the first aspect above.

[0045] Fourthly, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the in-vehicle multi-system data interaction method described in the first aspect.

[0046] Fifthly, embodiments of the present invention provide a vehicle, the vehicle including multiple data transceiver points, and the vehicle further including the in-vehicle multi-system data interaction device as described in the second aspect above.

[0047] Compared with prior art, the present invention has the following advantages:

[0048] In this embodiment of the invention, a first data frame sent by a first data transceiver point is received; the first data transceiver point is any one of a plurality of data transceiver points; the first data frame is split and reassembled into second data frames required by each of the second data transceiver points, the second data transceiver point being a different data transceiver point from the first data transceiver point among the plurality of data transceiver points; each second data frame is sent to its corresponding second data transceiver point. Upon receiving a data frame sent from a data transceiver point, according to forwarding rules, the data frame is split and reassembled into new data frames and forwarded to the corresponding data transceiver point. This not only enables data interaction between multiple data transceiver points but also ensures that the flow and content of data frames sent from the sending point are controlled and processed midway, preventing data from being forwarded to data transceiver points that do not need the data, thus improving the efficiency of data reception and processing at the receiving point.

[0049] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0050] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0051] Figure 1 This is a schematic diagram of a vehicle-mounted multi-system data interaction method provided in an embodiment of the present invention;

[0052] Figure 2 This is a block diagram of the multi-system master-slave unit data interaction structure provided in an embodiment of the present invention;

[0053] Figure 3 This is a flowchart illustrating the data interaction and sharing process between multiple system master and slave units in an embodiment of the present invention.

[0054] Figure 4 A general flowchart of data frame splitting, assembly, and distribution provided in an embodiment of the present invention.

[0055] Figure 5 A flowchart of data frame splitting provided in an embodiment of the present invention;

[0056] Figure 6 A general flowchart for data frame splitting and re-framing distribution provided in an embodiment of the present invention;

[0057] Figure 7 A flowchart of a control unit sending data frames to an Android system is provided as an embodiment of the present invention;

[0058] Figure 8A flowchart illustrating how an Android system sends data frames to an instrument system, as provided in this embodiment of the invention;

[0059] Figure 9 A flowchart of an Android system sending data frames to a slave control unit is provided as an embodiment of the present invention;

[0060] Figure 10 A schematic diagram of an in-vehicle multi-system data interaction device provided in an embodiment of the present invention;

[0061] Figure 11 A block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0062] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the invention and to fully convey the scope of the invention to those skilled in the art.

[0063] Figure 1 This is a schematic diagram of a vehicle-mounted multi-system data interaction method provided by an embodiment of the present invention, including:

[0064] Step 101: Receive the first data frame sent by the first data transceiver point; the first data transceiver point is any one of a plurality of data transceiver points.

[0065] The in-vehicle multi-system data interaction method provided in this embodiment of the invention is applied to the main control unit of the in-vehicle terminal. The main control unit specifically refers to the central processing unit. The main control unit includes multiple data transceiver points, each of which corresponds to a system object. There are multiple system objects, including at least two operating systems and at least one slave control unit. Accordingly, the data transceiver points can be operating system transceiver points and slave control unit transceiver points.

[0066] Optionally, the aforementioned at least two operating systems may include an Android system and an instrument cluster system. The aforementioned slave control unit specifically refers to the microprocessor that connects the actual vehicle environment and the main chip. The aforementioned instrument cluster system is the system that runs the instruments.

[0067] Please see Figure 2 This diagram illustrates a multi-system master-slave unit data interaction structure block diagram provided by an embodiment of the present invention. Figure 2 As shown, the Android system and instrument system are connected to the central processing unit, and the central processing unit is connected to the microprocessor through the slave control unit transceiver point and the slave control unit data transceiver device.

[0068] In this step, since the first data transceiver point will send the first data frame to be sent when it needs to interact with other data transceiver points, receiving the first data frame indicates that the first data transceiver point needs to interact with other data transceiver points using the first data frame.

[0069] Step 102: After splitting the first data frame, reassemble it into the second data frames required by each second data transceiver point. The second data transceiver point is a data transceiver point that is different from the first data transceiver point among the plurality of data transceiver points.

[0070] In this step, since the first data frame may include data required by multiple second data transceivers, or may include only data required by one second data transceiver, or may not include data required by any second data transceiver, after receiving the first data frame sent by the first data transceiver, it is split according to the prescribed splitting and forwarding rules, and the data frame is reassembled to obtain the second data frame actually required by each second data transceiver.

[0071] Step 103: Send each of the second data frames to the corresponding second data transceiver point.

[0072] In this step, since each second data frame is obtained by splitting and reassembling the first data frame according to each second data transceiver point, each second data frame is first sent to the second data receiving point corresponding to the second data transceiver point according to the sending rules, so that it can be transmitted to the second data transceiver point that actually needs the second data frame, thereby efficiently realizing the data interaction between the first data transceiver point and the second data transceiver point.

[0073] The above implementation process, after receiving a data frame sent from a data transceiver point, splits and reassembles the data frame into a new data frame according to the forwarding rules and forwards it to the corresponding data transceiver point. This not only enables data interaction between multiple data transceiver points, but also ensures that the flow and content of the data frame sent from the sending point are controlled and processed midway, preventing data from being forwarded to data transceiver points that do not need the data, thus improving the efficiency of data reception and processing at the receiving point.

[0074] The data interaction method provided in this embodiment of the invention is applicable to multi-system vehicle terminals including Android systems and instrument systems, and the forwarding of data frames is flexibly controlled by forwarding rules.

[0075] Optionally, in the data interaction method provided in the embodiments of the present invention, step 102 includes steps 201 to 203.

[0076] Step 201: According to the control parameters, the first data frame is divided into identifiable data units; wherein, the control parameters determine the identifiable data units corresponding to each data transmission and reception point.

[0077] In this step, the identifiable units included in the data frame contain information ID, information data length, specific information content, etc. The size of each unit is determined by the information length information, and the information ID represents the specific meaning of the actual vehicle information, such as the current vehicle speed.

[0078] In this step, the control parameters determine the identifiable data units corresponding to each data transceiver point. Specifically, the control parameters include actual vehicle functional requirements and information control rules. The actual vehicle functional requirements specify the identifiable data units for the functional implementation of each data transceiver point. The information control rules include several constraint data tables, each table corresponding to a different constraint rule. The constraint rule specifies the identifiable data units for each data transceiver point. Therefore, the first data frame can be divided into identifiable data units according to the control parameters.

[0079] For example, if the data marked in Table 1 is required by the instrument system, the data will be sent to the instrument system when the data to be processed is included in Table 1; if the data marked in Table 2 is to be sent to the central control host, the data will be sent to the central control host when the data to be processed is included in Table 2.

[0080] In practical applications, before splitting the first data frame, the valid data units in the first data frame are extracted according to the data frame format. The data IDs of the data units and the data corresponding to the data IDs are identified, so that subsequent steps can determine the data transmission and reception points corresponding to each data unit. Among them, the valid data units conform to the definition format requirements of real vehicle data, and conform to the space occupation size and value range defined by the data definition.

[0081] Step 202: According to the control parameters, mark each of the identifiable data units according to the corresponding data transmission and reception points.

[0082] In this step, the information control rules specify the data transmission and reception points corresponding to each identifiable data unit. Therefore, according to the information control rules, each identifiable data unit separated from the first data frame is marked according to the data transmission and reception points. That is, identifiable data units corresponding to the same data transmission and reception point use the same mark, while identifiable data units corresponding to different data transmission and reception points use different marks.

[0083] Optionally, step 202 above specifically includes: according to the control parameters, marking each of the identifiable data units to the physical address matching the second data transceiver point according to the corresponding second data transceiver point.

[0084] In this step, the marking is to mark the data required by different data transmission and reception points according to the rules and assign them to the specific physical address corresponding to the data transmission and reception point for marking, thereby realizing the distinguishing and marking of each identifiable data unit.

[0085] Step 203: Based on the marker, reassemble each of the identifiable data units into each of the second data frames.

[0086] In this step, according to the markings made on the identifiable data units, identifiable data units with the same markings are reassembled into a second data frame, thereby obtaining multiple second data frames, each of which corresponds to a data transmission and reception point.

[0087] In the above implementation, according to the actual vehicle functional requirements and information control rules, the first data frame is split and reassembled according to the data transmission and reception points to obtain multiple second data frames. Subsequently, each second data frame can be sent to the corresponding data transmission and reception point, so as to realize data interaction between the first data transmission and reception point and the second data transmission and reception point quickly and efficiently.

[0088] Optionally, the method provided in this embodiment of the invention further includes steps 111 to 113 before step 102.

[0089] Step 111: Determine the validity of the first data frame;

[0090] Step 112: If the first data frame is determined to be invalid, discard the first data frame;

[0091] Step 113: If the first data frame is determined to be valid, perform the step of splitting the first data frame and reassembling it into the second data frames required by each second data transceiver point.

[0092] In this embodiment, before splitting and reassembling the received data frame, the validity of the data frame is first determined using validity determination conditions, which are the determination conditions for valid data units.

[0093] In this embodiment, after receiving a data frame sent by the data transceiver point, the validity of the received data is first determined by the validity judgment condition. Only valid data frames will continue to be processed, while invalid data frames will be discarded directly, thereby avoiding the processing of invalid data frames and affecting the data interaction efficiency between the data transceiver points.

[0094] Optionally, in one specific implementation, step 111 above includes: if each data unit in the first data frame meets the validity determination conditions, then the first data frame is determined to be valid; the determination conditions include the definition format requirements of the real vehicle data, the space occupied by the data definition, and the value range; if the data unit in the first data frame does not meet the determination conditions, then the first data frame is determined to be invalid.

[0095] In this specific implementation, if each data unit in the data frame meets the requirements of the defined format of the real vehicle data, the space occupied by the data, and the value range of the data definition, then the data frame is determined to be valid; if any data unit does not meet the requirements of the defined format of the real vehicle data, the space occupied by the data, and the value range of the data definition, then the data frame is determined to be invalid.

[0096] Optionally, the method provided in this embodiment of the invention further includes steps 121 to 122 before step 111.

[0097] Step 121: According to the format of the data frame, calculate the first check data of the data content, frame header data and frame tail data in the entire first data frame, and compare it with the second check data carried by the first data frame to verify the first data frame.

[0098] In this step, based on the data format of the first data frame, first checksum data is calculated, generated from the entire data content, frame header, and frame trailer of the first data frame. The checksum data carried by the first data frame, i.e., the aforementioned second checksum data, is then extracted and compared with the first checksum data. If the first checksum data and the second checksum data match, the first data frame is determined to have passed checksum verification; if the first checksum data and the second checksum data do not match, the first data frame is determined to have failed checksum verification.

[0099] Step 122: After the first data frame passes the verification, perform the step of determining the validity of the first data frame.

[0100] In this step, if the first data frame passes the verification, the subsequent steps continue; otherwise, the subsequent steps are not executed.

[0101] In this step, the received data frame is first verified. After the verification is successful, the validity of the data frame is then judged. Only after it is determined that valid data has been received is the subsequent splitting and reassembly step performed. This avoids processing erroneous or invalid data and ensures the efficiency of data interaction between data sending and receiving points.

[0102] Optionally, the data interaction method provided in this embodiment of the invention is applied to a master control unit. The master control unit includes a slave control unit data transceiver device. The slave control unit data transceiver device has a custom communication interface for connecting to the slave control unit. The custom communication interface has a status marking module and an interaction request module. The status marking module is used to mark the actual state of the slave control unit so that it can interact with the master control unit when it is in an idle state. The interaction request module is used to allow the slave control unit to send an interaction request to the master control unit when it needs to interact with the master control unit.

[0103] In this embodiment of the invention, the aforementioned status marking module can mark the actual status of the slave control unit. Since the slave control unit can instantly set its occupied or idle status, and the slave control unit is connected to the aforementioned slave control unit data transceiver device, its current status can be obtained through the slave control unit data transceiver device and marked by the status marking module. Specifically, after the master control unit receives a data frame that the data transceiver point needs to send to the slave control unit, it first queries the specific status of the slave control unit. If the slave control unit is currently in an idle state, the data frame is sent to the slave control unit; if the slave control unit is currently in an occupied state, the data frame is not sent to the slave control unit initially.

[0104] When a slave control unit needs to send a data frame to another data transceiver point via the master control unit, the slave control unit first assembles a data frame destined for the target data transceiver point, then sets a flag indicating that it is currently in an idle state, and then sends an interaction request to the master control unit through the aforementioned interaction request module. After receiving the interaction request, the master control unit first checks whether the slave control unit is in an idle state through the aforementioned status flag module. If the slave control unit is in an idle state, the master control unit starts sending and receiving data frames from the slave control unit, and then splits and reassembles the data frames before sending them to the target data transceiver point, thereby realizing data interaction between the slave control unit and other data transceiver points.

[0105] In this embodiment of the invention, by upgrading and modifying the original data transmission interface between the master control unit and the slave control unit, a status flag module and an interaction request module are added. This achieves the high data transmission rate, good stability and full-duplex data interaction characteristics of the SPI interface, and also meets the proactive requirements of data interaction between master and slave devices. In other words, it effectively enhances the data transmission rate, stability and efficiency, while possessing the advantages of UART interface, SPI interface and I2C interface for data transmission, thus better meeting the needs of vehicle data interaction.

[0106] In this embodiment of the invention, a data processing unit is added to the main control unit to execute the in-vehicle multi-system data interaction method. The data processing unit can split, assemble and distribute data frames. The data processing unit is located in the middle of each data transmission and reception point.

[0107] The data processing unit initializes simultaneously with the data transceiver points such as the Android system, instrument system, and slave control unit. Before each data transceiver point sends data, it prepares the data frames to be processed. After initialization, the data processing unit continuously queries each data transceiver point to see if any data frames have been sent.

[0108] Specifically, please refer to Figure 3 This illustrates a flowchart of a multi-system master-slave unit data interaction and sharing process in an embodiment of the present invention. Figure 3 As shown, the data processing unit has three data transceiver points, each of which has the function of sending and receiving data frames. Since the Android system data transceiver point and the instrument system data transceiver point run on the same CPU, there is no slave control unit data transceiver device between the Android system transceiver node and the instrument system transceiver node, similar to the slave control unit between the master control unit and the slave control unit.

[0109] Data interaction between the Android system and the slave control unit requires data frames to pass through the data processing unit, the slave control unit's transceiver point, and the slave control unit's data transceiver device. Similarly, data interaction between the instrument system and the slave control unit also requires data frames to pass through the data processing unit, the slave control unit's transceiver point, and the slave control unit's data transceiver device. The data processing unit, located between the Android system's data transceiver point, the instrument system's data transceiver point, and the slave control unit's data transceiver point, cyclically receives data frames from these three points. It then splits and reassembles the data frames according to prescribed splitting and forwarding rules, and finally sends the reassembled data frames to the corresponding destination receiving node according to the transmission rules.

[0110] For example, after the Android system sends a data frame to the data processing unit, if the data frame contains data needed by both the slave control unit and the instrument system, the data frame will be split into two data frames. One data frame is sent to the instrument system, and is reassembled from the data content needed by the instrument extracted from the original data frame. The other data frame is assembled from the data needed by the slave control unit extracted from the original data frame. In this case, the original data frame changes from one data frame to two data frames, which are sent to the instrument system data receiving point and the slave control unit data receiving point, respectively. After receiving the data frame from the data splitting and reassembly unit, the slave control unit sends it to the slave control unit through the slave control unit data transceiver device.

[0111] Please see Figure 4The diagram illustrates an overall flowchart of a data frame splitting, assembly, and distribution method provided by an embodiment of the present invention.

[0112] like Figure 4 As shown, in step 401, the data processing unit initializes simultaneously with the initialization phases of the Android system, the instrument system, and the slave control unit system, and prepares the data frame for processing before the Android system, the instrument system, and the slave control unit system send data.

[0113] In step 402, after the data processing unit is initialized, it continuously queries the Android system, the instrument system, and the control unit system to see if any data frames have been sent out.

[0114] In step 403, after the data processing unit receives a data frame from the Android system, the instrument system, or the control unit, it determines the validity of the received data. If the received data frame is valid, it continues processing; otherwise, it discards the invalid data frame.

[0115] In step 404, after the data processing unit receives a valid data frame sent by the Android system, the instrument system, or the slave control unit, it will split the data frame into smaller identifiable data units and mark these identifiable data units according to the rules.

[0116] In step 405, after the data frame is split, the data processing unit reassembles the split identifiable data units into new data frames according to predetermined rules based on the tags, and distributes the reassembled data frames to the designated target receiving points, thereby completing the distribution of the data frames.

[0117] Please see Figure 5 The diagram illustrates a data frame splitting flowchart provided by an embodiment of the present invention.

[0118] like Figure 5 As shown, in step 501, after receiving a valid data frame, the data frame is format checked to identify the valid data units in the data frame.

[0119] In step 502, according to the format of the data frame, the check data of the data content, frame header and frame tail data in the entire data frame are calculated and compared with the check data in the data frame to verify the authenticity of the data frame.

[0120] In step 503, valid data units in the data frame are extracted according to the data frame format, and the data ID and the data corresponding to the data ID in the data unit are identified.

[0121] In step 504, it is determined whether the data unit is required by the Android system. If yes, proceed to step 505; otherwise, proceed directly to step 506.

[0122] In step 505, the data unit is marked as a data unit required by the Android system, and then the process proceeds to step 506.

[0123] In step 506, it is determined whether the data unit is required by the instrument system. If yes, proceed to step 507; otherwise, proceed directly to step 508.

[0124] In step 507, the data unit is marked as a data unit required by the instrument system.

[0125] In step 508, it is determined whether the data unit is required by the control unit. If so, proceed to step 509; otherwise, proceed to step 510.

[0126] In step 509, the data unit is marked as a data unit required from the control unit.

[0127] In step 510, it is determined whether there are any unmarked data units in the frame. If so, step 503 is executed again until all data units are marked according to steps 504 to 509.

[0128] In step 510, it is determined whether the data frame has been processed. If it has been processed, the process proceeds to step 511 to reassemble the data units and distribute the data frame. Otherwise, the process returns to step 503.

[0129] Please see Figure 6 The diagram illustrates the overall flowchart of a data frame splitting and re-framing distribution provided by an embodiment of the present invention.

[0130] like Figure 6 As shown, in step 601, after the data frame is split and marked, the data frames are reassembled and forwarded.

[0131] In step 602, the data frames marked as needed by the Android system are framed and forwarded to the Android system.

[0132] In step 603, the data frames marked as needed by the instrument system are framed and forwarded to the instrument system.

[0133] In step 604, the data frames marked as needed by the slave control unit are framed and forwarded to the slave control unit.

[0134] Please see Figure 7 The diagram illustrates a flowchart of a process for a control unit to send data frames to an Android system, as provided in an embodiment of the present invention.

[0135] like Figure 7 As shown, in step 701, the slave control unit assembles a data frame to be sent to the Android system.

[0136] In step 702, the slave control unit sets a flag indicating that it is currently in an idle state.

[0137] In step 703, the slave control unit requests the master control unit to send and receive data frames.

[0138] In step 704, the master control unit receives a request from the control unit to send and receive data frames.

[0139] In step 705, the master control unit checks whether the current slave control unit is in an idle state; if so, it proceeds to step 706.

[0140] In step 706, the master control unit begins to send and receive data frames from the slave control unit.

[0141] In step 707, the data processing unit of the main control unit forwards the processed data frame to the Android system.

[0142] Please see Figure 8 The diagram illustrates a flowchart of an Android system sending data frames to an instrument system, according to an embodiment of the present invention.

[0143] like Figure 8 As shown, in step 801, the Android system prepares a frame of data, which is then sent to the instrument system.

[0144] In step 802, the Android system sends the data frame to the main control unit for data frame splitting and reassembly.

[0145] In step 803, the main control unit splits and reassembles the data frame into a new data frame, and sends the data frame required by the instrument to the data frame receiving buffer of the instrument system.

[0146] In step 804, the instrument system extracts the new data frame from the receiving buffer, thereby completing the transmission of the Android system's data frame to the instrument system.

[0147] Please see Figure 9 The diagram illustrates a flowchart of an Android system sending data frames to a slave control unit, as provided in an embodiment of the present invention.

[0148] like Figure 9 As shown, in step 901, the Android system prepares a frame of data, which is then sent to the slave control unit.

[0149] In step 902, the Android system sends the data frame to the main control unit for splitting and extracts the data frames required by the slave control unit.

[0150] In step 903, the main control unit queries whether the slave control unit is currently in an idle state; if so, it means that the slave control unit can receive data frames.

[0151] In step 904, the main control unit sends the data frame to the slave control unit, thereby completing the process of the Android system sending the data frame to the slave control unit.

[0152] Figure 10 This is a schematic diagram of an in-vehicle multi-system data interaction device provided in an embodiment of the present invention. The device includes:

[0153] Data receiving unit 11 is used to receive a first data frame sent by a first data transceiver point; the first data transceiver point is any one of a plurality of data transceiver points;

[0154] Data processing unit 12 is used to split the first data frame and reassemble it into second data frames required by each second data transceiver point, wherein the second data transceiver point is a data transceiver point that is different from the first data transceiver point among the plurality of data transceiver points;

[0155] The data sending unit 13 is used to send each of the second data frames to the corresponding second data transceiver point.

[0156] Optionally, in the data interaction device, the data processing unit 12 includes:

[0157] The sub-unit is used to split the first data frame into identifiable data units according to the control parameters; wherein the control parameters determine the identifiable data units corresponding to each data transmission and reception point.

[0158] The marking subunit is used to mark each of the identifiable data units according to the corresponding data transmission and reception points, based on the information control rules.

[0159] An assembly subunit is used to reassemble each of the identifiable data units into each of the second data frames according to the marker.

[0160] Optionally, the marking subunit is specifically used to mark each of the identifiable data units to the physical address matching the second data transceiver point according to the control parameters.

[0161] Optionally, in the data interaction device, the data processing unit 12 further includes:

[0162] The determination subunit is used to determine the validity of the first data frame before reassembling the first data frame into the second data frames required by each second data transceiver point after splitting the first data frame;

[0163] A discard subunit is configured to discard the first data frame if it is determined that the first data frame is invalid.

[0164] The first execution subunit is configured to, when it is determined that the first data frame is valid, execute the step of splitting the first data frame and reassembling it into the second data frames required by each second data transceiver point.

[0165] Optionally, in the data interaction device, the data processing unit 12 further includes:

[0166] The verification subunit is used to calculate the first verification data of the entire data content, frame header data and frame tail data in the first data frame according to the format of the first data frame before determining the validity of the first data frame, and compare it with the second verification data carried by the first data frame to verify the first data frame.

[0167] The second execution subunit is used to perform the step of determining the validity of the first data frame after the first data frame has passed the verification.

[0168] Optionally, the determining subunit is specifically used to determine that the first data frame is valid if each data unit in the first data frame meets the validity determination conditions; the determination conditions include the definition format requirements of the real vehicle data, the space occupied by the data definition, and the value range; if the data units in the first data frame do not meet the determination conditions, the first data frame is determined to be invalid.

[0169] This invention also provides a vehicle that includes multiple data transceiver points, each including at least two operating systems and at least one slave control unit. The vehicle also includes the in-vehicle multi-system data interaction device described above.

[0170] For the above-described device and vehicle embodiments, since they are basically similar to the vehicle-mounted multi-system data interaction method embodiments, the relevant parts can be referred to in the description of the method embodiments.

[0171] The in-vehicle multi-system data interaction device and vehicle provided in this embodiment of the invention, after receiving a data frame sent from a data transceiver point, splits and reassembles the data frame into a new data frame according to the forwarding rules and forwards it to the corresponding data transceiver point. This not only enables data interaction between multiple data transceiver points, but also ensures that the flow direction and frame content of the data frame sent from the sending point are controlled and processed midway, preventing data from being forwarded to data transceiver points that do not need the data, thereby improving the efficiency of data reception and processing at the receiving point.

[0172] This invention also provides an electronic device, such as... Figure 11 As shown, it includes a processor 1101, a communication interface 1102, a memory 1103, and a communication bus 1104, wherein the processor 1101, the communication interface 1102, and the memory 1103 communicate with each other through the communication bus 1104.

[0173] Memory 1103 is used to store computer programs.

[0174] When processor 1101 executes a program stored in memory 1103, it performs the following steps:

[0175] Receive a first data frame sent by a first data transceiver point; the first data transceiver point is any one of a plurality of data transceiver points;

[0176] The first data frame is split and reassembled into the second data frames required by each second data transceiver point. The second data transceiver point is a data transceiver point that is different from the first data transceiver point among the plurality of data transceiver points.

[0177] Each of the second data frames is sent to the corresponding second data transceiver point.

[0178] The processor 1101 can also perform other steps in the above-mentioned vehicle multi-system data interaction method, which will not be described in detail here.

[0179] The communication bus mentioned in the above electronic devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0180] The communication interface is used for communication between the aforementioned electronic devices and other devices.

[0181] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0182] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0183] In another embodiment of the present invention, a computer-readable storage medium is also provided, which stores instructions that, when executed on a computer, cause the computer to perform the OTA upgrade failure handling method described in the above embodiments.

[0184] In another embodiment of the present invention, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute the OTA upgrade failure handling method described in the above embodiments.

[0185] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

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

[0187] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. For embodiments of devices, electronic devices, computer-readable storage media, and computer program products containing instructions, the descriptions are relatively simple because they are basically similar to the method embodiments; relevant parts can be referred to the descriptions of the method embodiments.

[0188] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention are included within the scope of protection of the present invention.

Claims

1. A method for data interaction between multiple vehicle systems, characterized in that, The method includes: Receive a first data frame sent by a first data transceiver point; the first data transceiver point is any one of a plurality of data transceiver points; The first data frame is split and reassembled into the second data frames required by each second data transceiver point. The second data transceiver point is a data transceiver point that is different from the first data transceiver point among the plurality of data transceiver points. Each of the second data frames is sent to the corresponding second data transceiver point; The first data frame is split and reassembled into the second data frames required by each second data transceiver point, including: According to the control parameters, the first data frame is divided into identifiable data units; wherein, the control parameters determine the identifiable data units corresponding to each data transmission and reception point; Based on the control parameters, each of the identifiable data units is marked according to its corresponding data transmission and reception point; Based on the marker, each of the identifiable data units is reassembled into each of the second data frames.

2. The data interaction method according to claim 1, characterized in that, Based on the control parameters, each identifiable data unit is marked according to its corresponding data transmission and reception point, including: According to the control parameters, each identifiable data unit is marked to the physical address matching the second data transceiver point according to its corresponding second data transceiver point.

3. The data interaction method according to claim 1, characterized in that, Before the step of splitting and reassembling the first data frame into the second data frames required by each second data transceiver point, the method further includes: Determine the validity of the first data frame; If the first data frame is determined to be invalid, the first data frame is discarded. If the first data frame is determined to be valid, the step of splitting the first data frame and reassembling it into the second data frames required by each second data transceiver point is performed.

4. The data interaction method according to claim 3, characterized in that, Before the step of determining the validity of the first data frame, the method further includes: Based on the format of the first data frame, calculate the first check data of the entire data content, frame header data and frame tail data in the first data frame, and compare it with the second check data carried by the first data frame to verify the first data frame. After the first data frame passes verification, the step of determining the validity of the first data frame is executed.

5. The data interaction method according to claim 3, characterized in that, Determining the validity of the first data frame includes: If each data unit in the first data frame meets the validity determination criteria, then the first data frame is determined to be valid; the determination criteria include the definition format requirements of the real vehicle data, the space occupied by the data definition, and the value range; If the data units in the first data frame do not meet the determination conditions, then the first data frame is determined to be invalid.

6. A vehicle-mounted multi-system data interaction device, characterized in that, The device includes: A data receiving unit is configured to receive a first data frame sent by a first data transceiver point; the first data transceiver point is any one of a plurality of data transceiver points. The data processing unit is used to split the first data frame and reassemble it into second data frames required by each second data transceiver point, wherein the second data transceiver point is a data transceiver point that is different from the first data transceiver point among the plurality of data transceiver points; A data transmission unit is used to send each of the second data frames to the corresponding second data transceiver point; The data processing unit includes: The sub-unit is used to split the first data frame into identifiable data units according to the control parameters; wherein the control parameters determine the identifiable data units corresponding to each data transmission and reception point. The marking subunit is used to mark each of the identifiable data units according to the corresponding data transmission and reception points based on the control parameters. An assembly subunit is used to reassemble each of the identifiable data units into each of the second data frames according to the marker.

7. An electronic device, characterized in that, include: The system includes a processor, a communication interface, a memory, and a communication bus; the processor, communication interface, and memory communicate with each other via the communication bus. Memory, used to store computer programs; When executing a program stored in memory, the processor implements the steps of the in-vehicle multi-system data interaction method as described in any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps in the in-vehicle multi-system data interaction method as described in any one of claims 1 to 5.

9. A vehicle, characterized in that, The vehicle includes multiple data transceiver points, and the vehicle also includes the in-vehicle multi-system data interaction device as described in claim 6.

Images