IP Library Granted Patent US 11,381,472
Granted Patent B2
US 11,381,472 · App. 15/719,921 · Granted Jul 5, 2022

Visualization of intra-vehicular communications networks

Inventors: Abhijit Bansal (Los Angeles, CA); Douglas D. Chidester (San Pedro, CA); Shan Deng (Arcadia, CA); Jana Mahen Fernando (Torrance, CA); Matthew K. Lubbers (Manhattan Beach, CA)
Assignee: Faraday & Future Inc.
H04L41/22H04L12/40H04L12/40013H04L41/082H04L41/0883H04L41/12H04L2012/40215H04L2012/40234H04L2012/40273
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,381,472
App. No.
15/719,921
Granted
Jul 5, 2022
Kind
B2
Abstract

Methods, systems, computer-readable media, and apparatuses are presented for computer-assisted visualization of network devices. One example involves receiving a plurality of standardized network description files describing a plurality of vehicular communication networks connecting a plurality of electronic control units (ECU) for a vehicle. Each of the plurality of standardized network description files may describe a vehicular communication network in the plurality of vehicular communication networks. Each vehicular communication network may comprise a subset of the plurality of ECUs and one or more network communications paths interconnecting the subset of ECUs. The example can further involve automatically generating, based on the standardized network description files, a visual topology representation of the plurality of vehicular communication networks connecting to the plurality of ECUs. The visual topology representation may include at least one ECU connected to at least two vehicular communication networks in the plurality of vehicular communication networks.

Claims (52)

1. A method for computer-assisted visualization of network devices, comprising:

receiving a plurality of standardized network description files (SND) describing a plurality of vehicular communication networks connecting a plurality of electronic control units (ECU) for a vehicle, each of the plurality of SND files describing a vehicular communication network in the plurality of vehicular communication networks, each vehicular communication network comprising a subset of the plurality of ECUs and one or more network communications paths interconnecting the subset of ECUs; and

automatically generating, based on the standardized network description files, a visual topology representation of the plurality of vehicular communication networks connecting to the plurality of ECUs, the visual topology representation including at least one ECU connected to at least two vehicular communication networks in the plurality of vehicular communication networks;

receiving an input from a user to select a network message defined by one or more of the plurality of SND files, the selected network message comprising a plurality of fields;

generating a visual signal path representation for the selected network message, the visual signal path representation illustrating (1) an originating ECU, (2) a destination ECU, (3) a plurality of routes connecting the originating ECU to the destination ECU through at least a portion of the plurality of vehicular communication networks, and (4) a plurality of intermediate ECUs traversed by one or more of the plurality of routes;

providing a screen illustrating both representations of the plurality of SND files that make up an entire communication system configuration of the vehicle and a window to enable a user to provide instructions to generate program code for the ECUs within the vehicle's communication system; and

modifying a route for the selected network message based on ECUs to which a first of the plurality of fields is destined, wherein the first of the plurality of fields is destined for an ECU other than the destination ECU;

wherein the plurality of routes connecting the originating ECU to the destination ECU includes (1) a current route and (2) one or more alternative routes; and

wherein a first portion of the intermediate ECUs are along the current route and are each illustrated to have a first characteristic, and a second portion of the intermediate ECUs are not along the current route but are suitable for use along the current route and are each illustrated to have a second characteristic.

2. The method of claim 1 , further comprising:

generating a visual message representation for the selected network message, the visual message representation illustrating a plurality of fields of the selected network message.

3. The method of claim 2 , further comprising:

receiving an input from the user to modify a particular field in the plurality of fields of the selected network message;

in response to the input from the user to modify the particular field, altering at least one route in the plurality of routes.

4. The method of claim 3 , further comprising:

automatically generating one or more modified standardized network description files, the modified standard network description files describing the at least one route in the plurality of routes altered in response to the input from the user to modify the particular field.

5. The method of claim 4 , further comprising:

automatically generating software code for one or more of the plurality of ECUs based on the one or more modified standardized network description files.

6. The method of claim 1 , wherein the plurality of vehicular communication networks includes at least one controller area network (CAN).

7. The method of claim 1 , wherein the plurality of vehicular communication networks includes at least one local interconnect network (LIN).

8. The method of claim 1 , wherein the visual signal path representation further illustrates a second destination ECU and a second plurality of routes connecting the originating ECU to the second destination ECU through at least a second portion of the plurality of vehicular communication networks.

9. The method of claim 1 wherein the illustrated second characteristic of the second portion of the one or more intermediate ECUs not along the current route but suitable for use along the current route includes hashed boundaries.

10. A non-transitory computer-readable memory storing a plurality of instructions executable by one or more processors, the plurality of instructions comprising:

instructions that cause the one or more processors to receive a plurality of standardized network description files describing a plurality of vehicular communication networks connecting a plurality of electronic control units (ECU) for a vehicle, each of the plurality of standardized network description files describing a vehicular communication network in the plurality of vehicular communication networks, each vehicular communication network comprising a subset of the plurality of ECUs and one or more network communications paths interconnecting the subset of ECUs; and

instructions that cause the one or more processors to automatically generate, based on the plurality of SND files, a visual topology representation of the plurality of vehicular communication networks connecting to the plurality of ECUs, the visual topology representation including at least one ECU connected to at least two vehicular communication networks in the plurality of vehicular communication networks;

instructions that cause the one or more processors to receive an input from a user to select a network message defined by one or more of the plurality of SND files, the selected network message comprising a plurality of fields;

instructions that cause the one or more processors to generate a visual signal path representation for the selected network message, the visual signal path representation illustrating (1) an originating ECU, (2) a destination ECU, (3) a plurality of routes connecting the originating ECU to the at least one destination ECU through at least a portion of the plurality of vehicular communication networks, and (4) a plurality of intermediate ECUs transversed by one or more of the plurality of routes;

instructions that cause the one or more processors to provide a screen illustrating both representations of the plurality of SND files that make up an entire communication system configuration of the vehicle and a window to enable a user to provide instructions to generate program code for the ECUs within the vehicle's communication system; and

instructions that modifies a route for the selected network message based on ECUs to which a first of the plurality of fields is destined, wherein the first of the plurality of fields is destined for an ECU other than the destination ECU;

wherein the plurality of routes connecting the originating ECU to the destination ECU includes (1) a current route and (2) one or more alternative routes; and

wherein a first portion of the intermediate ECU are along the current route and are each illustrated to have a first characteristic, and a second portion of the intermediate ECUs are not along the current route but are suitable for use along the current route and are each illustrated to have a second characteristic.

11. The non-transitory computer-readable memory of claim 10 , the plurality of instructions further comprising:

instructions that cause the one or more processors to generate a visual message representation for the selected network message, the visual message representation illustrating a plurality of fields of the selected network message.

12. The non-transitory computer-readable memory of claim 11 , the plurality of instructions further comprising:

instructions that cause the one or more processors to receive an input from the user to modify a particular field in the plurality of fields of the selected network message;

instructions that cause the one or more processors to, in response to the input from the user to modify the particular field, alter at least one route in the plurality of routes.

13. The non-transitory computer-readable memory of claim 12 , the plurality of instructions further comprising:

instructions that cause the one or more processors to automatically generate one or more modified standardized network description files, the modified standard network description files describing the at least one route in the plurality of routes altered in response to the input from the user to modify the particular field.

14. The non-transitory computer-readable memory of claim 13 , the plurality of instructions further comprising:

instructions that cause the one or more processors to automatically generate software code for one or more of the plurality of ECUs based on the one or more modified standardized network description files.

15. The non-transitory computer-readable memory of claim 10 , wherein the visual signal path representation further illustrates a second destination ECU and a second plurality of routes connecting the originating ECU to the second destination ECU through at least a second portion of the plurality of vehicular communication networks.

16. The non-transitory computer-readable memory of claim 10 wherein the illustrated second characteristic of the second portion of the one or more intermediate ECUs not along the current route but suitable for use along the current route includes hashed boundaries.

17. An apparatus for computer-assisted visualization of network devices, comprising:

at least one processor configured to receive a plurality of standardized network description SND files describing a plurality of vehicular communication networks connecting a plurality of electronic control units (ECU) for a vehicle, each of the plurality of SND files describing a vehicular communication network in the plurality of vehicular communication networks, each vehicular communication network comprising a subset of the plurality of ECUs and one or more network communications paths interconnecting the subset of ECUs,

wherein the at least one processor is further configured to automatically generate, based on the plurality of SND files, a visual topology representation of the plurality of vehicular communication networks connecting to the plurality of ECUs, the visual topology representation including at least one ECU connected to at least two vehicular communication networks in the plurality of vehicular communication networks;

wherein the at least one processor is further configured to receive an input from a user to select a network message defined by one or more of the plurality of SND files, the selected network message comprising a plurality of fields, and

wherein the at least one processor is further configured to generate a visual signal path representation for the selected network message, the visual signal path representation illustrating (1) an originating ECU, (2) a destination ECU, (3) a plurality of routes connecting the originating ECU to the destination ECU through at least a portion of the plurality of vehicular communication networks, and (4) a plurality of intermediate ECUs transversed by one or more of the plurality of routes;

wherein the at least one processor is further configured to provide a screen illustrating both representations of the plurality of SND files that make up an entire communication system configuration of the vehicle and a window to enable a user to provide instructions to generate program code for the ECUs within the vehicle's communication system; and

wherein the at least one processor is further configured to modify a route for the selected network message based on ECUs to which a first of the plurality of fields is destined, wherein the first of the plurality of fields is destined for an ECU other than the destination ECU;

wherein the plurality of routes connecting the originating ECU to the destination ECU includes (1) a current route and (2) one or more alternative routes; and

wherein a first portion of the intermediate ECUs are along the current route and are each illustrated to have a first characteristic, and a second portion of the intermediate ECUs are not along the current route but are suitable for use along the current route and are each illustrated to have a second characteristic; and

at least one data storage unit configured to communicate with the processor and to store data for the automatically generated visual topology representation.

Assignments (10)
SECURITY INTEREST Recorded Sep 25, 2024
From: FARADAY&FUTURE, INC.
To: SENYUN INTERNATIONAL LTD.
Reel/Frame 069048/0736 →
SECURITY INTEREST Recorded Aug 15, 2022
From: FARADAY&FUTURE INC.
To: FF SIMPLICY VENTURES LLC
Reel/Frame 061176/0756 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 050234/0069 Recorded Jun 8, 2022
From: ARES CAPITAL CORPORATION, AS SUCCESSOR COLLATERAL AGENT
To: CITY OF SKY LIMITED; EAGLE PROP HOLDCO LLC; FARADAY & FUTURE INC.; FARADAY FUTURE LLC; FF EQUIPMENT LLC; FF HONG KONG HOLDING LIMITED; FF INC.; FF MANUFACTURING LLC; ROBIN PROP HOLDCO LLC; SMART KING LTD.; SMART TECHNOLOGY HOLDINGS LTD.; FARADAY SPE, LLC
Reel/Frame 060314/0263 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 27, 2022
From: BANSAL, ABHIJIT; CHIDESTER, DOUGLAS D.; DENG, SHAN; FERNANDO, JANA MAHEN; LUBBERS, MATTHEW K.
To: FARADAY&FUTURE INC.
Reel/Frame 058791/0760 →
ACKNOWLEDGEMENT OF SUCCESSOR COLLATERAL AGENT UNDER INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Jul 29, 2021
From: BIRCH LAKE FUND MANAGEMENT, LP, AS RETIRING AGENT
To: ARES CAPITAL CORPORATION, AS SUCCESSOR AGENT
Reel/Frame 057019/0140 →
SECURITY INTEREST Recorded Oct 14, 2020
From: ROYOD LLC
To: BIRCH LAKE FUND MANAGEMENT, LP
Reel/Frame 054076/0157 →
ACKNOWLEDGEMENT OF SUCCESSOR COLLATERAL AGENT UNDER INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Mar 5, 2020
From: BIRCH LAKE FUND MANAGEMENT, LP, AS RETIRING AGENT
To: ROYOD LLC, AS SUCCESSOR AGENT
Reel/Frame 052102/0452 →
SECURITY INTEREST Recorded May 1, 2019
From: CITY OF SKY LIMITED; EAGLE PROP HOLDCO LLC; FARADAY FUTURE LLC; FE EQUIPMENT LLC; FF HONG KONG HOLDING LIMITED; FF INC.; FF MANUFACTURING LLC; ROBIN PROP HOLDCO LLC; SMART KING LTD.; SMART TECHNOLOGY HOLDINGS LTD.; FARADAY SPE, LLC; FARADAY & FUTURE INC.
To: BIRCH LAKE FUND MANAGEMENT, LP
Reel/Frame 050234/0069 →
RELEASE OF SECURITY INTEREST Recorded Jan 14, 2019
From: SEASON SMART LIMITED
To: FARADAY&FUTURE INC.
Reel/Frame 048069/0704 →
SECURITY INTEREST Recorded Dec 28, 2017
From: FARADAY&FUTURE INC.
To: SEASON SMART LIMITED
Reel/Frame 044969/0023 →