IP Library Granted Patent US 12,470,526
Granted Patent B2
US 12,470,526 · App. 17/973,767 · Granted Nov 11, 2025

Data transmission method and apparatus

Inventors: Steven Yin Zhong (Singapore, SG); Xinxing Yin (Shanghai, CN); Mingming Zhang (Shanghai, CN)
Assignee: SHENZHEN YINWANG INTELLIGENT TECHNOLOGIES CO., LTD.
H04L63/0428H04L63/123H04L63/20H04L67/12H04L2212/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,470,526
App. No.
17/973,767
Granted
Nov 11, 2025
Kind
B2
Abstract

A data transmission method includes: a first electronic control unit (ECU) that obtains to-be-sent data. The first ECU determines a protection policy corresponding to the to-be-sent data from a plurality of protection policies, where the protection policies include a plurality of different encapsulation formats for the to-be-sent data and at least two protection policies with different calculation amounts for processing the to-be-sent data. The first ECU encapsulates the to-be-sent data according to the protection policy corresponding to the to-be-sent data to obtain an encapsulated packet. The first ECU sends the encapsulated packet to a second ECU, where the first ECU and the second ECU are any two ECUs in a vehicle.

Claims (48)

1 . A data transmission method, comprises:

obtaining, by a first electronic control unit (ECU) of a vehicle, to-be-sent data;

selecting, by the first ECU, a protection policy corresponding to the to-be-sent data from a plurality of protection policies based on a mapping relationship between an identifier comprised in the to-be-sent data and a security level of the to-be-sent data, wherein the identifier is of an ECU associated with a data type of the to-be-sent data, wherein the plurality of protection policies comprise a plurality of different encapsulation manners for the to-be-sent data, and wherein the plurality of protection policies comprise at least two protection policies with different calculation amounts for processing the to-be-sent data;

encapsulating, by the first ECU, the to-be-sent data according to the protection policy corresponding to the to-be-sent data, to obtain an encapsulated packet, wherein the encapsulated packet comprises a second identifier of the protection policy for the to-be-sent data, and wherein the second identifier is for identifying the security level for the to-be-sent data in the encapsulated packet; and

sending, by the first ECU, the encapsulated packet to a second ECU of the vehicle.

2 . The data transmission method of claim 1 , wherein the encapsulated packet comprises a second identifier of the protection policy corresponding to the to-be-sent data, and wherein the second identifier is for selecting a manner of parsing the encapsulated packet.

3 . The data transmission method of claim 1 , further comprising selecting, by the first ECU, the protection policy corresponding to the to-be-sent data from the plurality of protection policies based on the identifier comprised in the to-be-sent data comprises:

selecting, by the first ECU, a security level of the to-be-sent data based on the identifier and a second mapping relationship, wherein the second mapping relationship comprises a relationship between a third identifier of an ECU in the vehicle and a second security level, and wherein a security level corresponding to each ECU in the vehicle is based on a type of the each ECU in the vehicle; and

selecting, by the first ECU, the protection policy corresponding to the to-be-sent data from the plurality of protection policies based on the security level.

4 . The data transmission method of claim 1 , wherein each of the at least two protection policies comprises policies associated with at least one of no protection, anti-replay attack protection, integrity protection, or confidentiality protection, wherein the no protection indicates that no protection is performed on the to-be-sent data, wherein the anti-replay attack protection indicates that protection against a replay attack is performed on the to-be-sent data, wherein the integrity protection indicates that integrity check code is generated for the to-be-sent data, wherein the integrity check code is for checking whether the encapsulated packet is complete, and wherein the confidentiality protection indicates that encryption processing is performed on the to-be-sent data.

5 . The data transmission method of claim 1 , wherein the encapsulated packet is a Scalable service-Oriented MiddlewarE over IP (SOME/IP) packet.

6 . A data transmission method, comprising:

receiving, by a second electronic control unit (ECU) of a vehicle, an encapsulated packet from a first ECU of the vehicle;

obtaining, by the second ECU, a protection policy corresponding to the encapsulated packet, wherein the protection policy corresponding to the encapsulated packet comprises an encapsulation manner of the first ECU for obtaining the encapsulated packet, wherein the encapsulated packet comprises an identifier of the protection policy for the encapsulated packet, and wherein the identifier of the protection policy is used by the second ECU to identify the security level of data in the encapsulated packet and to identify a manner of parsing the encapsulated packet; and

parsing, by the second ECU, the encapsulated packet according to the protection policy, to obtain a parsing result.

7 . The data transmission method of claim 6 , wherein the protection policy corresponding to the encapsulated packet comprises at least one of no protection, anti-replay attack protection, integrity protection, or confidentiality protection, wherein the no protection indicates that no protection is performed on to-be-sent data, wherein the anti-replay attack protection indicates that protection against a replay attack is performed on the encapsulated packet, wherein the integrity protection indicates that integrity check code is added in the encapsulated packet, wherein the integrity check code for checking whether data obtained through parsing is complete when the encapsulated packet is parsed, and wherein the confidentiality protection indicates that encryption processing is performed on the encapsulated packet.

8 . A first electronic control unit (ECU), applied to a vehicle having the first ECU and a second ECU, wherein the first ECU comprises:

a memory configured to store program instructions; and

at least one processor coupled to the memory and configured to execute the program instructions to cause the first ECU to:

obtain to-be-sent data;

select a protection policy corresponding to the to-be-sent data from a plurality of protection policies based on a mapping relationship between an identifier in the to-be-sent data and a security level of the to-be-sent data, wherein the identifier is of an ECU associated with a data type of the to-be-sent data, wherein the plurality of protection policies comprise a plurality of different encapsulation manners for the to-be-sent data, and wherein the plurality of protection policies comprise at least two protection policies with different calculation amounts for processing the to-be-sent data;

encapsulate the to-be-sent data according to the protection policy corresponding to the to-be-sent data, to obtain an encapsulated packet, wherein the encapsulated packet comprises a second identifier of the corresponding to the to-be-sent data, and wherein the second identifier is for identifying the security level for the to-be-sent data in the encapsulated packet; and

send the encapsulated packet to the second ECU.

9 . The first ECU of claim 8 , wherein the encapsulated packet comprises a second identifier of the protection policy corresponding to the to-be-sent data, and wherein the second identifier is for selecting a manner of parsing the encapsulated packet.

10 . The first ECU of claim 8 , wherein the program instructions, when executed by the at least one processor, further causes the first ECU to:

select a security level of the to-be-sent data based on the identifier and a second mapping relationship, wherein the second mapping relationship comprises a relationship between a third identifier of an ECU in the vehicle and a second security level, and a security level corresponding to each ECU in the vehicle is determined based on a type of the each ECU in the vehicle; and

select the protection policy corresponding to the to-be-sent data from the plurality of protection policies based on the security level.

11 . The first ECU of claim 8 , wherein each of the at least two protection policies comprises policies associated with at least one of no protection, anti-replay attack protection, integrity protection, or confidentiality protection, wherein the no protection indicates that no protection is performed on the to-be-sent data, wherein the anti-replay attack protection indicates that protection against a replay attack is performed on the to-be-sent data, wherein the integrity protection indicates that integrity check code is generated for the to-be-sent data, wherein the integrity check code is for checking whether the encapsulated packet is complete, and wherein the confidentiality protection indicates that encryption processing is performed on the to-be-sent data.

12 . The first ECU of claim 8 , wherein the encapsulated packet is a Scalable service-Oriented MiddlewarE over IP (SOME/IP) packet.

13 . A second electronic control unit (ECU) of a vehicle having a first ECU and the second ECU, wherein the second ECU comprises:

a memory configured to store program instructions; and

at least one processor coupled to the memory and configured to execute the program instructions to cause the second ECU to:

receive an encapsulated packet from the first ECU;

obtain a protection policy corresponding to the encapsulated packet, wherein the protection policy corresponding to the encapsulated packet comprises an encapsulation manner of the first ECU for obtaining the encapsulated packet, wherein the encapsulated packet comprises an identifier of the protection policy for the encapsulated packet, and wherein the identifier of the protection policy is used by the second ECU to identify the security level of data in the encapsulated packet and to identify a manner of parsing the encapsulated packet; and

parse the encapsulated packet according to the protection policy, to obtain a parsing result.

14 . The second ECU of claim 13 , wherein the protection policy corresponding to the encapsulated packet comprises policies associated with at least one of no protection, anti-replay attack protection, integrity protection, or confidentiality protection, wherein the no protection indicates that no protection is performed on to-be-sent data, wherein the anti-replay attack protection indicates that protection against a replay attack is performed on the encapsulated packet, wherein the integrity protection indicates that integrity check code is added in the encapsulated packet, wherein the integrity check code is used to check whether data obtained through parsing is complete when the encapsulated packet is parsed, and wherein the confidentiality protection indicates that encryption processing is performed on the encapsulated packet.

15 . A vehicle comprising:

a first electronic control unit (ECU); and

a second ECU coupled to the second ECU, wherein the first ECU is configured to:

obtain to-be-sent data;

select a protection policy corresponding to the to-be-sent data from a plurality of protection policies based on a mapping relationship between an identifier in the to-be-sent data and a security level of the to-be-sent data, wherein the identifier is of an ECU associated with a data type of the to-be-sent data, wherein the plurality of protection policies comprise a plurality of different encapsulation manners for the to-be-sent data, and wherein the plurality of protection policies comprise at least two protection policies with different calculation amounts for processing the to-be-sent data;

encapsulate the to-be-sent data according to the protection policy corresponding to the to-be-sent data, to obtain an encapsulated packet, wherein the encapsulated packet comprises a second identifier of the protection policy for the to-be-sent data, and wherein the second identifier is for identifying the security level for the to-be-sent data in the encapsulated packet; and

send the encapsulated packet to the second ECU.

16 . The vehicle of claim 15 , wherein the encapsulated packet is a Scalable service-Oriented MiddlewarE over IP (SOME/IP) packet.

17 . The vehicle of claim 15 , wherein the first ECU is further configured to:

select a security level of the to-be-sent data based on the identifier and a second mapping relationship, wherein the second mapping relationship comprises a relationship between a third identifier of an ECU in the vehicle and a second security level, and a security level corresponding to each ECU in the vehicle is determined based on a type of the each ECU in the vehicle; and

select the protection policy corresponding to the to-be-sent data from the plurality of protection policies based on the security level.

18 . The vehicle of claim 15 , wherein each of the at least two protection policies comprises policies associated with at least one of no protection, anti-replay attack protection, integrity protection, or confidentiality protection, wherein the no protection indicates that no protection is performed on the to-be-sent data, wherein the anti-replay attack protection indicates that protection against a replay attack is performed on the to-be-sent data, wherein the integrity protection indicates that integrity check code is generated for the to-be-sent data, wherein the integrity check code is for checking whether the encapsulated packet is complete, and wherein and the confidentiality protection indicates that encryption processing is performed on the to-be-sent data.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2024
From: HUAWEI TECHNOLOGIES CO., LTD.
To: SHENZHEN YINWANG INTELLIGENT TECHNOLOGIES CO., LTD.
Reel/Frame 069336/0082 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 6, 2023
From: ZHONG, STEVEN YIN; YIN, XINXING; ZHANG, MINGMING
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 062601/0058 →