IP Library Granted Patent US 11,743,366
Granted Patent B1
US 11,743,366 · App. 17/500,838 · Granted Aug 29, 2023

Communication of sensor data in a motor vehicle communication network

Inventors: Amir Bar-Niv (Sunnyvale, CA); Dance Wu (Palo Alto, CA)
Assignee: Marvell Asia Pte Ltd
H04L69/22H04L12/4645H04L65/65H04N21/85403H04N21/85406H04W4/40
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 11,743,366
App. No.
17/500,838
Granted
Aug 29, 2023
Kind
B1
Abstract

A processor receives data corresponding to a sensor, and generates a frame having a header and a payload. A data type value is selected from a set of multiple data type values corresponding to different respective types of data, the set of multiple data type values including at least i) a first data type value corresponding to video data from a camera, and ii) a second data type value corresponding to non-video data. The header is generated to include one or more fields set to the selected data type value to indicate a type of data included in the payload, and the payload is generated to include the data received from the sensor. The processor provides the frame to an Ethernet network interface. The Ethernet network interface encapsulates the frame in an Ethernet packet, and transmits the Ethernet packet via an Ethernet link.

Claims (102)

1. A method for communicating in a vehicular communication network, the method comprising:

receiving, at a processor, a packet that includes data corresponding to a sensor, the packet being in the first format defined by a camera serial interface (CSI) protocol of the Mobile Industry Processor Interface (MIPI) Alliance;

reformatting, at the processor, the packet in the first format defined by the CSI protocol to a second format that does not conform to any CSI protocol of the MIPI alliance, the reformatting including generating a frame that does not include the packet in the first format, the frame being generated to include a header in the second format and a payload in the second format, wherein generating the frame includes:

selecting, based on a data identifier (ID) field in the packet in the first format, a data type value from a set of multiple data type values corresponding to different respective types of data, the set of multiple data type values including at least i) a first data type value corresponding to video data from a camera, and ii) a second data type value corresponding to non-video data,

generating the header in the second format to include one or more fields set to the selected data type value to indicate a type of data included in the payload, and

generating the payload to include the data corresponding to the sensor;

providing, by the processor, the frame to an Ethernet network interface;

encapsulating, at the Ethernet network interface, the frame in an Ethernet packet; and

transmitting, by the Ethernet network interface, the Ethernet packet via an Ethernet link.

2. The method of claim 1 , wherein:

the processor is communicatively coupled to the sensor via multiple communication links;

the method further comprises determining, at the processor, a communication link, among the multiple communication via which the data corresponding to the sensor was received; and

the selecting the data type value from the set of multiple data type values comprises: selecting the data type value further based on the determined communication link, among the multiple communication link, via which the data corresponding to the sensor was received.

3. The method of claim 1 , wherein the frame is a first frame and the Ethernet packet is a first Ethernet packet, and wherein the method further comprises:

receiving, at the processor, one of i) general purpose input/output (GPIO) data corresponding to the sensor, ii) diagnostic data corresponding to the sensor, and iii) Operation and Management (OAM) data corresponding to the sensor;

generating, at the processor, a second frame to include a header in the second format and a payload in the second format, wherein generating the second frame includes:

selecting a data type value for the second frame from the set of multiple data type values, including selecting the data type value to be a value corresponding to the one of i) GPIO data, ii) diagnostic data, and iii) OAM data,

generating the header of the second frame in the second format to include one or more fields set to the selected data type value to indicate a type of data included in the payload of the second frame, and

generating the payload of the second frame to include the one of i) the GPIO data corresponding to the sensor, ii) the diagnostic data corresponding to the sensor, and iii) the OAM data corresponding to the sensor;

providing, by the processor, the second frame to the Ethernet network interface;

encapsulating, at the Ethernet network interface, the second frame in a second Ethernet packet; and

transmitting, by the Ethernet network interface, the second Ethernet packet via the Ethernet link.

4. The method of claim 1 , wherein the frame is a first frame and the Ethernet packet is a first Ethernet packet, and wherein the method further comprises:

receiving, at the processor, data corresponding to the sensor in a user-defined format;

generating, at the processor, a second frame to include a header in the second format and a payload in the second format, wherein generating the second frame includes:

selecting a data type value for the second frame from the set of multiple data type values, including selecting the data type value to be a value indicating the payload includes user-defined data,

generating the header of the second frame in the second format to include one or more fields set to the selected data type value to indicate a type of data included in the payload of the second frame, and

generating the payload of the second frame to include the data corresponding to the sensor in a user-defined format;

providing, by the processor, the second frame to the Ethernet network interface;

encapsulating, at the Ethernet network interface, the second frame in a second Ethernet packet; and

transmitting, by the Ethernet network interface, the second Ethernet packet via the Ethernet link.

5. The method of claim 1 , wherein:

the receiving the data corresponding to the sensor comprises receiving video data;

the selecting the data type value from the set of multiple data type values comprises selecting the first data type value; and

the method further comprises:

selecting, based on the video data, a data subtype value from a set of multiple video data subtype values corresponding to different respective subtypes of video data, and

generating the header to include a data subtype field set to the selected data subtype value to indicate a subtype of video data included in the payload.

6. The method of claim 1 , further comprising:

generating, at the processor, the header to include routing information.

7. The method of claim 6 , wherein:

the generating the header to include routing information comprises generating the header to include a source identifier and a destination identifier.

8. The method of claim 6 , wherein:

the generating the header to include routing information comprises generating the header to include virtual local area network (VLAN) information.

9. The method of claim 8 , further comprising:

generating, by the Ethernet network interface, an IEEE 802.1Q tag for the Ethernet packet using the VLAN information in the header of the frame.

10. The method of claim 8 , further comprising:

selecting the VLAN information to be included in the frame using flow information included within a virtual channel field of the packet in the first format.

11. The method of claim 1 , further comprising:

selecting, by the processor, virtual local area network (VLAN) information using flow information included within a virtual channel field of the packet in the first format; and

generating, by the Ethernet network interface, an IEEE 802.1Q tag for the Ethernet packet using the VLAN information.

12. A communication device, comprising:

a processor configured to:

receive a packet that includes data corresponding to a sensor in a motor vehicle, the packet being in a first format defined by a camera serial interface (CSI) protocol of the Mobile Industry Processor Interface (MIPI) Alliance,

reformat the packet in the first format defined by the CSI protocol to a second format that does not conform to any CSI protocol of the MIPI alliance, the reformatting including generating a frame that does not include the packet in the first format, the frame being generated to include a header in the second format and a payload in the second format, wherein generating the frame includes:

selecting, based on a data identifier (ID) field in the packet in the first format, a data type value from a set of multiple data type values corresponding to different respective types of data, the set of multiple data type values including at least i) a first data type value corresponding to video data from a camera, and ii) a second data type value corresponding to non-video data,

generating the header in the second format to include one or more fields set to the selected data type value to indicate a type of data included in the payload, and

generating the payload to include the data corresponding to the sensor;

an Ethernet network interface configured to:

receive the frame from the processor,

encapsulate the frame in an Ethernet packet, and

transmit the Ethernet packet via an Ethernet link.

13. The communication device of claim 12 , wherein:

the processor is communicatively coupled to the sensor via multiple communication links; and

the processor is further configured to:

determine a communication link, among the multiple communication links, via which the data corresponding to the sensor was received, and

select the data type value further based on the communication link, among the multiple communication link, via which the data corresponding to the sensor was received.

14. The communication device of claim 12 , wherein the frame is a first frame and the Ethernet packet is a first Ethernet packet, and wherein the processor is further configured to:

receive one of i) general purpose input/output (GPIO) data corresponding to the sensor, ii) diagnostic data corresponding to the sensor, and iii) Operation and Management (OAM) data corresponding to the sensor;

generate a second frame to include a header in the second format and a payload in the second format, wherein generating the second frame includes selecting the data type value to be a value corresponding to the one of i) GPIO data, ii) diagnostic data, and iii) OAM data;

generate the header of the second frame in the second format to include one or more fields set to the selected data type value to indicate a type of data included in the payload of the second frame; and

generate the payload of the second frame to include the one of i) the GPIO data corresponding to the sensor, ii) the diagnostic data corresponding to the sensor, and iii) the QAM data corresponding to the sensor;

wherein the Ethernet network interface is further configured to:

receive the second frame from the processor,

encapsulate the second frame in a second Ethernet packet, and

transmit the second Ethernet packet via the Ethernet link.

15. The communication device of claim 12 , wherein the frame is a first frame and the Ethernet packet is a first Ethernet packet, wherein the processor is further configured to:

receive data corresponding to the sensor in a user-defined format;

generate a second frame to include a header in the second format and a payload in the second format, wherein generating the second frame includes selecting the data type value to be a value indicating the payload includes user-defined data;

generate the header of the second frame in the second format to include one or more fields set to the selected data type value to indicate a type of data included in the payload of the second frame; and

generate the payload of the second frame to include the data corresponding to the sensor in the user-defined format;

wherein the Ethernet network interface is further configured to:

receive the second frame from the processor,

encapsulate the second frame in a second Ethernet packet, and

transmit the second Ethernet packet via the Ethernet link.

16. The communication device of claim 12 , wherein the processor is configured to:

receive video data corresponding to the sensor;

select the first data type value based on the data ID field in the packet in the first format;

select, based on receiving the video data, a data subtype value from a set of multiple video data subtype values corresponding to different respective subtypes of video data; and

generate the header to include a data subtype field set to the selected data subtype value to indicate a subtype of video data included in the payload.

17. The communication device of claim 12 , wherein the processor is further configured to:

generate the header to include routing information.

18. The communication device of claim 17 , wherein the processor is further configured to:

generate the header to include a source identifier and a destination identifier.

19. The communication device of claim 17 , wherein the processor is further configured to:

generate the header to include virtual local area network (VLAN) information.

20. The communication device of claim 19 , wherein the Ethernet network interface is further configured to:

generate an IEEE 802.1Q tag for the Ethernet packet using the VLAN information in the header of the frame.

21. The communication device of claim 19 , wherein the processor is further configured to:

select the VLAN information to be included in the frame using flow information included within a virtual channel field of the packet in the first format.

22. The communication device of claim 12 , wherein:

the processor is further configured to select virtual local area network (VLAN) information using flow information included within a virtual channel field of the packet in the first format; and

the Ethernet network interface is further configured to generate an IEEE 802.1Q tag for the Ethernet packet using the VLAN information.

Assignments (4)
MERGER Recorded Sep 5, 2025
From: INFINEON TECHNOLOGIES US NEWCO LLC
To: INFINEON TECHNOLOGIES AMERICAS CORP.
Reel/Frame 072563/0971 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 22, 2025
From: MARVELL ASIA PTE LTD
To: INFINEON TECHNOLOGIES US NEWCO LLC
Reel/Frame 072558/0700 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 21, 2025
From: BAR-NIV, AMIR; WU, DANCE
To: MARVELL SEMICONDUCTOR, INC.
Reel/Frame 071782/0246 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 21, 2025
From: MARVELL SEMICONDUCTOR, INC.
To: MARVELL ASIA PTE LTD
Reel/Frame 071782/0298 →
Continuity (1)
Provisional Application 63091282 · Oct 13, 2020
Cited By (1)
US 12,413,656