HK1192978A - Automotive neural network - Google Patents

Abstract

The present invention is directed to an automotive neural network. Network node modules within a vehicle are arranged to form a reconfigurable automotive neural network. Each network node module includes one or more subsystems for performing one or more operations and a local processing module for communicating with the one or more subsystems. A switch coupled between the one or more subsystems and the processing module re-routes traffic from the one or more subsystems to an external processing module upon failure of the local processing module.

Description

Neural network for motor vehicle

Technical Field

The present invention relates generally to communications, and more particularly to communications within a vehicle.

Background

As is known, a vehicle (e.g., an automobile, truck, bus, farm vehicle, marine vessel, and/or aircraft) includes a vehicle communication network. The complexity of the vehicle communication network varies depending on the number of electronic devices within the vehicle. For example, many more advanced vehicles include electronic modules for engine control, transmission control, antilock braking, body control, emissions control, and the like. The automotive industry has produced numerous communication protocols to support the various electronic devices within a vehicle.

FIG. 1 is a schematic block diagram of a prior art vehicle communication network showing various bus protocols and electronic devices utilizing the protocols. These bus protocols include: (1) j1850 and/or OBDII, which are commonly used in vehicle diagnostic electronics; (2) intellibus, which is commonly used for electronic engine control, transmission control of other vehicle systems, such as air conditioning control, and which may also be used for line-driven Electronic Control Units (ECUs); (3) a high-speed Controller Area Network (CAN), which is generally used for a brake system and an engine management system; (4) distributed System Interface (DSI) and/or Bosch-Siemens-Temic (BST), which are commonly used for security related purposesThe electronic device of (1); (5) bytefly, which is commonly used for safety critical electronic device applications; (6) a Local Interconnect Network (LIN) typically used for smart actuators and/or smart sensors; (7) low speed Controller Area Network (CAN) and/orinterconnect (mi), which is commonly used for low speed electronics such as windows, mirrors, seating, and/or air conditioning control; (8) mobile Media Link (MML), national digital data (D2B), smartwire x, inter-device bus (IEBus), and/or Media Oriented System Transport (MOST), which are commonly used to support multimedia electronic devices within a vehicle, such as audio head units and amplifiers, CD players, DVD players, cellular connections, bluetooth connections, peripheral computer connections, Rear Seat Entertainment (RSE) units, radios, digital storage, and/or GPS navigation systems; (9) low Voltage Differential Signaling (LVDS), which is commonly used to support heads-up displays, instrument panel displays, other digital displays, driver-assisted digital video cameras, and (10) FlexRay, which may be used for safety critical features and/or line-by-wire applications.

In order to make it possible for electronic components using different bus protocols to communicate with one another, one or more bus gateways may be included in the vehicle network. For example, in a safety-related problem, the safety ECU may need to communicate with the brake ECU and the engine control ECU and/or the transmission control ECU. In this example, the bus gateway performs some degree of protocol conversion to facilitate communication between ECUs of different communication protocols.

In addition to providing multiple vehicle network protocols to support various electronic devices within the vehicle, most vehicle manufacturers are also striving to improve fuel efficiency. In this regard, a weight reduction of 400 pounds corresponds to a reduction of the sustained power consumption of about 100 watts. Therefore, fuel efficiency can be improved by removing weight from the vehicle. As is known, a typical vehicle includes 400 to 600 pounds of wiring, which is the second heavy component in the vehicle; the engine is the heaviest.

Disclosure of Invention

The invention provides a network node module in a vehicle, comprising: one or more subsystems to perform one or more operations; a processing module for communicating with the one or more subsystems; a switch coupled between the one or more subsystems and the processing module; a first vehicle network interface for coupling the processing module to a vehicle communication network; and a second vehicle network interface for coupling the switch to an external processing module within the vehicle communication network; wherein the switch reroutes traffic from the one or more subsystems to the external processing module upon failure of the processing module.

Preferably, the external processing module is directly coupled to the network node module via the switch.

Preferably, the external processing module is selected from a group of external processing modules.

Preferably, the external processing module is selected based on the one or more operations performed by the one or more subsystems.

Preferably, the external processing module is selected based on the respective locations of the network node module and the external processing module within the vehicle communication network.

Preferably, the external processing module is within an additional network node module comprising one or more additional subsystems.

Preferably, the network node module, the additional network node module and other network node modules within the vehicle communication network are coupled together in one or more hierarchical configurations.

Preferably, the vehicle communication network is an ethernet network.

Preferably, the switch is operable to switch ethernet packets from the one or more subsystems on the audiovisual bridge stream to the external processor via the second vehicle network interface.

Preferably, the processing module is configured to communicate ethernet packets with the one or more subsystems via the switch.

Preferably, the network node module further includes: a third vehicle network interface to couple the processing module to an additional switch of an additional network node module that includes one or more additional subsystems.

Preferably, the processing module is configured to communicate ethernet packets with the one or more additional subsystems via the third vehicle network interface and the additional switch.

Preferably, the processing module is further configured to assign a respective priority to each of the ethernet packets received from the one or more subsystems and the one or more additional subsystems, and to process each of the ethernet packets based on the respective priority.

Preferably, the processing module is further configured to communicate with the one or more additional subsystems using a secure mechanism.

Preferably, the switch is a three-port switch having a first port coupled to the processing module, a second port coupled to the second vehicle communication interface, and a third port coupled to an ethernet bus coupling the one or more subsystems to the switch.

Preferably, the switches include a central switch coupling the processing module to the one or more subsystems, and a selector switch coupling the one or more subsystems to a plurality of external processing modules, the selector switch selecting at least one of the plurality of external processing modules upon failure of the processing module.

Preferably, the one or more subsystems comprise at least one of a sensor, an actuator, an electronic control unit and an infotainment device.

Preferably, the network node module further includes: a redundant switch coupled between the one or more subsystems and the processing module and coupled to the second vehicle communication interface.

The invention also provides a motor vehicle neural network comprising: a plurality of Ethernet links forming a vehicle communication network; and a plurality of network node modules coupled via the plurality of ethernet links, wherein each of the plurality of network node modules comprises: one or more subsystems to perform one or more operations; a processing module for communicating with the one or more subsystems; a switch coupled between the one or more subsystems and the processing module; a first vehicle network interface for coupling the processing module to the vehicle communication network; and a second vehicle network interface for coupling the switch to an external processing module within another network node module of the vehicle communication network; wherein upon failure of the processing module, the switch reroutes traffic from the one or more subsystems to the external processing module.

The present invention also provides a network node module in a vehicle, comprising: one or more subsystems to perform one or more operations; a local processing module for communicating with the one or more subsystems; a first vehicle network interface for coupling the local processing module to the vehicle communication network; and a second vehicle network interface for coupling the local processing module to a switch of an additional network node module comprising one or more additional subsystems via the vehicle communication network; wherein the local processing module is configured to communicate with the one or more additional subsystems via the second vehicle network interface upon failure of an additional processing module associated with the additional network node module.

Drawings

FIG. 1 is a schematic block diagram of a prior art vehicle communication network;

FIG. 2 is a schematic block diagram of an embodiment of an automotive neural network according to the present invention;

FIG. 3 is a schematic block diagram of an exemplary embodiment of an automotive neural network in accordance with the present invention;

FIG. 4 is a schematic block diagram of an embodiment of a reconfigurable network node module within an automotive neural network in accordance with the present invention;

FIG. 5 is a schematic block diagram of an embodiment of a reconfigurable network node module within an automotive neural network in accordance with the present invention;

FIG. 6 is a schematic block diagram of another embodiment of a reconfigurable network node module within an automotive neural network in accordance with the present invention;

FIG. 7 is a schematic block diagram of another exemplary embodiment within an automotive neural network in accordance with the present invention;

FIG. 8 is a schematic block diagram of another embodiment of a reconfigurable network node module within an automotive neural network in accordance with the present invention;

FIG. 9 is a schematic block diagram of another embodiment of a reconfigurable network node module within an automotive neural network in accordance with the present invention;

FIG. 10 is a schematic block diagram of another reconfigurable network node module of an automotive neural network in accordance with the present invention;

FIG. 11 is a logic diagram of a network reconfiguration process for a motor vehicle neural network in accordance with the present invention.

Detailed Description

Fig. 2 is a schematic block diagram of an embodiment of an automotive neural network 10, the automotive neural network 10 including a vehicle communication system 20 (e.g., ethernet-based), a plurality of network node modules 30, a gateway 40, one or more communication links 50, a network manager 60, a power manager 70, and a memory 80. The communication link 50 may include a wired and/or wireless interface to support connection with cellular devices, bluetooth devices, infrared devices, and/or computer peripheral devices. For example, a bluetooth transceiver may be coupled to the vehicle communication network 20 to support bluetooth communications with portable audio/video units, headsets, and the like.

The vehicle communication network 20 includes a plurality of bridge routing modules and a plurality of switch modules (an example of which is shown in fig. 7). Within the vehicle communication network 20, the bridging routing module is redundantly coupled to one or more adjacent bridging routing modules, and the switch module is redundantly coupled to one or more bridging routing modules. The vehicle communication network 20 may be divided into sub-networks coupled together via data bridges. For example, the vehicle communication network 20 may include a data bridge, a first sub-network operatively coupled to a first subset of the network node modules 30, and a second sub-network operatively coupled to a second subset of the network node modules 30. The data bridge facilitates (e.g., initiates, instructs, executes, etc.) communication of a subset of packets between the first and second subnetworks.

The gateway 40 may include one or more wireless transceivers to support communication with one or more external networks, such as a cellular network or a home network, and/or to support a diagnostic port for communication with an automotive service provider, automotive manufacturer, or the like. The wireless transceiver includes a network interface that enables the wireless transceiver to be connected to the vehicle communication network 20.

The network node modules 30 may each include, for example, a network interface, a processing module, and at least one device. If the device is an analog device, the network node module 30 further comprises an analog-to-digital converter and/or a digital-to-analog converter. The device may include a sensor, an actuator, a smart sensor, a smart actuator, an Electronic Control Unit (ECU), and/or a control device. As another example, the network node module 30 may include vehicle components such as a switching circuit module, a plurality of network interfaces operatively coupled to the switching circuit module, one or more processing modules operatively coupled to the switching circuit module, and a plurality of devices operatively coupled to the one or more processing modules. Various examples of the network node module 30 will be discussed in more detail with reference to fig. 3-10.

The network manager 60 performs various functions to coordinate packet communications within the vehicle communication network and facilitate network resource management. For example, the network manager 60 may coordinate packet communications between the network node modules 30, the memory 80, and the gateway 40 via the vehicle communication network 20 based on the contents of each packet and according to a global vehicle network communication protocol. The global vehicle network communication protocol includes information about: such as packet formatting, packet transmission priority schemes (e.g., mission critical packets having a higher priority, infotainment (information and/or entertainment) packets having a lower priority, etc.), network management processing (e.g., vehicle communication network resources and devices coupled to the vehicle communication network), and vehicle network operating parameters (e.g., network configuration management).

As another example, the network manager 60 facilitates (e.g., initiates, instructs, executes, etc.) network resource management to support packet communications via the vehicle communication network 20 according to a global vehicle network communication protocol. For example, the network manager 60 performs access priority management, bandwidth allocation management, packet redundancy management, link redundancy management, data transmission delay management, link diagnostics, network security, virtual local area network setup, legacy packet/frame management, adding and/or deleting devices that access the network, and the like.

The power manager 70 operates in cooperation with the network manager 60 to optimize power consumption of the vehicle communication network 20 and/or devices coupled thereto. For example, the power manager 70 may manage devices individually, may manage and isolate devices, and/or may manage power to network interfaces. The power management includes a sleep wake-up mode, an on-off power mode, in-use power reduction techniques (e.g., reducing power supply voltage, reducing clock rate, current limiting, etc.), and/or utilizing a low power communication link at the physical layer.

The memory 80 may be a variety of memory devices such as non-volatile memory, disk drives, memory, solid state memory, and/or other types of memory. The memory 80 may be used to store multimedia files (e.g., video files, audio files, etc.), electronic control unit applications, multimedia applications, diagnostic data, performance data, and/or any other data related to vehicle use and/or performance.

In an example of operation, the network node module 30 (e.g., a sensor) generates a packet according to a global vehicle network communication protocol (e.g., formats the packet according to information regarding the formatting of the packet). The network node module 30 then transmits the packets via the vehicle communication network 20 according to the global vehicle network communication protocol. For example, the vehicle communication network 20 routes the packet to another network node module 30, and/or to the gateway 40 or communication link 50 based on the content type (and destination address) of the packet.

In an exemplary embodiment, the vehicle communication network 20 has an ethernet bus structure (or other packet/frame structure) that enables packet/frame-based communication between a plurality of electronic devices within the vehicle. Furthermore, the vehicle communication network 20 is a semi-static network, allowing pre-configured scan trees to be used for fast reconfiguration of the network; the vehicle communication network 20 has configured bandwidth allocations specific to at least some of the devices to ensure a particular level of data throughput for mission critical and some non-mission critical applications; the vehicle communication network 20 supports a virtual local area network; the vehicle communication network 20 supports a centralized and/or distributed bus monitoring system; the vehicle communication network 20 uses the new type of packet for vehicle control; the vehicle communication network 20 supports security and authentication of device replacement and/or installation of new devices; the vehicle communication network 20 supports lossless ethernet transmission over redundant paths; the vehicle communication network 20 supports low latency protocols for mission critical packets; and/or the vehicle communication network 20 supports fast link failure handling.

Fig. 3 is a schematic block diagram of an exemplary embodiment of an automotive neural network that includes a vehicle communication system 20, one or more communication links 50, a gateway 40, a network manager 60, a power manager 70, one or more multimedia processing modules 134, a plurality of user input and/or output interfaces 136 (e.g., seat adjustments, window controls, radio controls, mirror controls, GPS controls, cruise controls, etc.), and a plurality of network node modules. Each network node module includes a network interface for coupling to the vehicle communication network 20 and at least one device.

The apparatus may include an engine management electronic control unit 138, an engine management actuator 140, an engine management sensor 142, an engine control electronic control unit 144, an engine control actuator 146, an engine control sensor 148, a diagnostic electronic control unit 150, a diagnostic sensor 152, a diagnostic actuator 154, a window electronic control unit 156, a window actuator 158, a window sensor 160, a mirror electronic control unit 162, a mirror actuator 164, a mirror sensor 166, a seat electronic control unit 168, a seat actuator 170, a seat sensor 172, an air conditioning electronic control unit 174, an air conditioning actuator 176, an air conditioning sensor 178, a safety sensor electronic control unit 180, a safety actuator 182, a safety sensor 184, a safety critical application electronic control unit 186, a safety critical actuator 188, a safety critical sensor 190, a braking system electronic control unit 192, a safety critical actuator 188, a safety critical sensor 190, a braking system, One or more of each of brake actuator 194, brake sensor 196, application-by-wire electronic control unit 198, actuator-by-wire actuator 200, sensor-by-wire 202, transmission control electronic control unit 204, transmission sensor 206, transmission actuator 208, vehicle system electronic control unit 210, vehicle system actuator 212, vehicle system sensor 214, DVD player 216, cellular telephone interface 218, bluetooth interface 220, computer peripheral interface 222, rear seat entertainment interface and/or unit 224, radio 226, digital storage 228, CD player 230, camera 232, display 234, heads-up display 236, GPS navigation system 238, infrared sensor 240, radio frequency sensor 242, smart actuator 244, and/or smart sensor 246.

The multimedia processing module 134 provides audio, video, text, and/or graphics processing for the vehicle. For example, the multimedia processing module 134 may support a GPS navigation system, provide rendered video and/or graphical images to a display, process digital images received by a camera, and/or provide images to other audio/video devices within the vehicle. The multimedia processing module 134 may be a single processing device or a plurality of processing devices. The processing device may be a microprocessor, microcontroller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. Multimedia processing module 134 may further have associated memory and/or memory elements, which may be a single memory device, multiple memory devices, and/or embedded circuitry of the processing module. The memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. It should be noted that if the multimedia processing module 134 includes more than one processing device, the processing devices may be centrally disposed (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributed (e.g., cloud-computing via direct coupling via a local area network and/or a wide area network). It should further be noted that when multimedia processing module 134 implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory elements storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. It should be further noted that the memory elements store and the multimedia processing module 134 executes hard-coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the figures.

Since each network node module may include one or more of these vehicle devices, each network node module typically includes a local processing module that may communicate with the vehicle devices and the network manager 60. For example, the local processing module may send status and relay commands into the network manager 60. This decentralized local processing can affect the reliability of the vehicle. For example, the local processing module creates an additional single point of failure in the network, which can result in higher overall maintenance requirements. Further, if a processing module manages a plurality of vehicle devices, a failure of a processing module failure will result in a failure of each vehicle device managed by the processing module. Furthermore, as complexity increases with the demand for more intelligent vehicles, any additional nesting of local processing modules may make debugging and fault isolation even more difficult. While redundancy at the component level may improve reliability, the redundancy is expensive and requires more space and wiring.

In various implementations, the techniques described herein describe and provide a reconfigurable network node module that implements an automotive neural network. More specifically, the reconfigurable network node module utilizes a switch to reroute traffic from a vehicle device managed by the failed local processing module to another processing module within the vehicle communication network. This allows the functionality of the affected vehicle device to continue until the failed local processing module can be repaired. In addition, the motor vehicle neural network makes it possible to quickly and easily carry out debugging and fault isolation.

Fig. 4 is a schematic block diagram of an embodiment of a reconfigurable network node module 30, the network node module 30 comprising a processing module 310, a memory 312, a first network interface 330, one or more subsystems 340, a switch 360, and a second network interface 370. One or more subsystems 340 (subsystem a, subsystem B, and subsystem C) correspond to one or more vehicle devices as shown in fig. 3. For example, the subsystems 340 may be sensors and actuators, electronic control units, user input devices, user output devices, communication devices, infotainment (multimedia) devices, and the like.

The processing module 310 implements local area network node management functions (which may, for example, include a locally managed priority scheme). The memory 320 includes data utilized by the processing module 310 to perform various operations, such as data input/output, packet processing, and vehicle operations.

The processing module 310 is coupled to a vehicle communication network via a first network interface 330. The processing module 310 is further coupled to one or more subsystems 340 via a switch 360 and an ethernet bus 350. In an exemplary embodiment, the ethernet bus 350 includes a plurality of ethernet links (e.g., twisted pair, coaxial cable, category 5 cable, fiber, etc.) that couple one or more subsystems 340 to the processing module 310. For example, the ethernet bus 350 may daisy chain one or more subsystems 340 with the switch 360, or may couple one or more subsystems 340 to the switch 360 via a hub or switch. The switch 360 further couples the one or more subsystems 340 to an external processing module within a vehicle communication network (not shown) via a second network interface 370.

In an example of operation, one of the subsystems 340, such as subsystem a, generates an outgoing device packet (or frame). In this example, subsystem a provides packets to the processing module 310 via the ethernet bus 350. Although not shown, the buffer may receive the ethernet packet and temporarily store the ethernet packet for the processing module 310. The processing module 310 may further manage input and output of packets in a buffer (e.g., queue) based on a priority scheme. For example, the processing module 310 may interpret the packets to determine the source, destination, and type of the packets, and then determine a locally administered priority scheme based on the source, destination, and type of the packets (e.g., mission critical packets, network protocol packets, vehicle operation packets, and/or infotainment packets).

The processing module 310 may further translate between a global vehicle network communication protocol utilized by the vehicle communication network and a specific vehicle device communication protocol utilized by subsystem a (e.g., CAN, FlexRay, etc.). For example, the processing module 310 may convert the ethernet packet of the vehicle device communication protocol to an ethernet packet of the global area network communication protocol. Alternatively, the processing module 310 may encapsulate the vehicle device communication packet of subsystem a into a global vehicle network communication protocol packet.

In addition, the processing module 310 may further determine the level, priority, security, and/or privacy of the protection package. The processing module 310 may further determine, based on aspects of the package, whether any other specific processing is to be performed locally on the package, and if so, the processing module 310 performs the necessary processing. In some implementations, determining processing for the packet can include determining packet routing parameters based on the packet content type. Once the packet has been processed, the processing module 310 may invoke routing functionality to forward or route the packet to its destination (which may be internal within the network node module 30 or external within the vehicle communication network) according to the packet's priority and/or security level.

When the processing module 310 is operational, the switch 360 couples one or more subsystems 340 to the processing module 310. However, in accordance with an embodiment of the present invention, when a processing module 310 fails, the switch 360 reroutes traffic from one or more subsystems 340 to an external processing module via the network interface 370. For example, in embodiments where one or more of the subsystems 340 includes a multimedia device, the switch 360 may be operable to switch packets generated by the multimedia device on the audiovisual bridge stream to an external processing module. The external processing module may be a local processing module within another network node module (nearby or remote), a central processing module within a vehicle communication network (e.g., the network manager of fig. 2-3), a dedicated processing module (e.g., a redundant or backup processing module for multiple network node modules), or another external processing module.

The management system within the vehicle communication network reconfigures the subsystem 340 and/or the switch 360 to reroute the packets to the external processing module. In one embodiment, a central management system (e.g., central processing module) reconfigures the subsystem 340 when a local processing module 310 fails. For example, the central processing module may send a cycle control signal to the local processing module 310 and upon determining that the local processing module 310 has failed (e.g., receives no response from the processing module or determines that the processing module is unable to perform its assigned task), provide the MAC address of the external processing module to the subsystem 340 within the network node module 30, causing the packet to be rerouted from the subsystem 340 to the external processing module via the switch 360 and the interface 370.

In another embodiment, a distributed management system is utilized. For example, the management system may be distributed between subgroups of network node modules 30 or between the external processing modules themselves. In the latter example, the external processing module may send a cycle control signal to the local processing module 310 and, upon determining that the local processing module 310 is malfunctioning, provide its MAC address to the subsystem 340, causing the packet to be rerouted via the switch 360 and interface 370. In yet another embodiment, the local processing module 310 and the external processing module may be provided on a VLAN, and the management system may reconfigure the switch 360 such that packets are rerouted to the external processing module when the local processing module 310 fails. Many variations of reconfiguration of the network node module 30 are possible, and the invention is not limited to any particular type of reconfiguration.

In one embodiment, the switch 360 is a three-port switch having a first port coupled to the processing module 310, a second port coupled to the ethernet bus 350, and a third port coupled to the second network interface 370. In another embodiment, switch 360 includes a plurality of switches for coupling to two or more external processing modules.

The processing module 310 may be a single processing device or a plurality of processing devices. The processing device may be a microprocessor, microcontroller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module 310 may have associated memory and/or memory elements, which may be a single memory device, multiple memory devices, and/or embedded circuitry of the processing module. The memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. It should be noted that if the processing module 310 includes more than one processing device, the processing devices may be arranged centrally (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributed (e.g., cloud-computing by direct coupling via a local area network and/or a wide area network). It should further be noted that when the processing module 310 implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory elements storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. It should be further noted that the memory elements store and the processing module 310 executes hard-coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the figures.

FIG. 5 is a schematic block diagram of an embodiment of a reconfigurable network node module within an automotive neural network in accordance with the present invention. As shown in fig. 5, the two network node modules 30A and 30B may be reconfigured to provide fault handling protection for the respective local processing modules 310A and 310B within the network node modules 30A and 30B. Each network node module 310A and 310B includes a respective first network interface 330A and 330B, a second network interface 370A and 370B, a processing module 310A and 310B, a memory 320A and 320B, a switch 360A and 360B, an ethernet bus 350A and 350B, and a subsystem 340. For example, network node module 30A includes subsystem a, subsystem B, and subsystem C, while network node module 30B includes subsystem D and subsystem E.

The network node module 30A further comprises a third network interface 380 coupled to the second network interface 370B of the network node module 30B via an ethernet link 390. In one embodiment, the network node module 30A is directly coupled to the network node module 30B within the vehicle communication network (e.g., in the case of any intermediate device, router, component, or module). In another example, the network node module 30A is directly coupled to the network node module 30B within the vehicle communication network.

When processing module 310B within network node module 30B is operational, switch 360B couples subsystem D and subsystem E to processing module 310B. However, when processing module 310B fails, switch 360B reroutes traffic from subsystem D and subsystem E to processing module 310A within network node module 30A via network interface 370B and network interface 380.

Thus, when processing module 310B fails, processing module 310A manages traffic from subsystems A through E. In one embodiment, the processing module 310A may prioritize (priority) traffic received from different subsystems 340 and/or block traffic received from one or more subsystems 340 to ensure that the processing needs of critical applications are met. For example, if there is a limitation due to latency, available bandwidth of link 390, and/or processing power of processing module 310A, processing module 310A may instruct subsystem D and/or subsystem E to refrain from sending packets or only send high priority packets until the limitation is resolved. Rather than reducing the functional group of the affected network node module 310B, the processing module 310A may instead instruct the subsystems A, B and/or C to avoid sending packets or to send only high priority packets. In another embodiment, security techniques such as a private VPN for exclusive use and/or encryption may be utilized by processing module 310A in communication with subsystems D and E to allow control traffic to pass through other modules such as infotainment switches.

In an example of operation, when a packet is received at processing module 310A within network node module 30A from one of subsystems 340 (e.g., subsystem D) within network node module 30B, processing module 310A interprets the packet. The interpretation includes determining the type of the packet (e.g., mission critical (e.g., from brake/ABS sensors), network data, infotainment, vehicle operation, etc.), and may further include determining the destination of the packet. Determining the type of packet includes determining the type of content carried by the packet (i.e., the packet content type), and may further include determining the protection, security, and or privacy level of the packet.

Having identified the packet, the processing module 310A determines processing for the packet based on aspects of the packet and then processes the packet accordingly. In some implementations, determining processing for the packets includes determining a priority of the packets from the content of the packets and/or from the source of the packets. For example, processing module 310A may be configured to preferentially process packets received from subsystem a, subsystem B, or subsystem C relative to packets received from subsystem D or subsystem E. As another example, the processing module 310A may be configured to prioritize the packets received from subsystem D over the packets received from subsystem a or subsystem E for the packets received from subsystem B or subsystem C. There are many possible variations for the prioritization of packets for processing by the processing module 310A, and the present invention is not limited to any particular prioritization scheme.

As a specific example, when the processing module 310A determines that a package is relevant to mission critical operations (based on the content or source of the package), it assigns a high priority to the package and processes the package before other non-mission critical packages. This processing may involve, for example, accessing memory 320A to determine whether any particular processing is to be performed. If no particular processing is performed, processing module 310A may invoke routing functionality to forward or route the packet to a destination based on the packet's priority and/or security level. If the processing module 310A determines that the packet does have a particular performance requirement (e.g., stores data in the memory 320A, forwards to a gateway for transmission to an external device, converts between communication protocols, etc.), the processing module 310A processes the packet accordingly. For example, most communications within a vehicle communication network may use a default communication protocol (e.g., 100Mbps or 1Gbps ethernet), however, some communications within a vehicle communication network may deviate from the default communication protocol. For example, between two modules within a vehicle communication network, 10Gb Ethernet may be used or between particular modules, a non-standard speed such as 200Mbps or 2.5Gb Ethernet may be used.

After processing module 310A has processed the packet, processing module 310A may invoke a routing function to forward or route the processed packet to its destination according to its priority and/or security level. Since the packet is generated by a subsystem external to the network node module 30A, the processing module 310A may further access the network topology information in the memory 320A to forward or route the processed packet. The network topology information may include, for example, a list of preconfigured scan tree network topologies for packets received from network node 30B, or information for network reconfiguration due to a failure of processing module 310B.

FIG. 6 is a schematic block diagram of another embodiment of a reconfigurable network node module within an automotive neural network in accordance with the present invention. In fig. 6, two network node modules 30A and 30B are shown coupled via the vehicle communication network 20. In addition, a central processing module 400 (e.g., the network manager of fig. 2 and 3) is further coupled to the vehicle communication network 20. In this embodiment, the central processing module 400 controls the rerouting of traffic between the network node modules 30A and 30B when a local processing module within the network node modules 30A and 30B fails. In one embodiment, the central processing module 400 controls each network node module 30A and 30B within the vehicle communication network 20. In another embodiment, multiple distributed processing modules 400 may be employed, each controlling a subset of the network node modules 30A and 30B within the vehicle communication network 20.

In one example of operation, the central processing module 400 may send periodic control signals to the processing modules of each of the network node modules 30A and 30B, and upon determining that a processing module of one of the network node modules (e.g., network node module 30A) has failed (e.g., no response received by the processing module), the central processing module 400 may identify the other network node module 30B to manage traffic from the failed network node module 30A and reconfigure the failed network node module 30A to reroute traffic from one or more subsystems within the failed network node module 30A to the network node module 30B. For example, the network node module 30B may be selected based on the type of operations performed by one or more subsystems within the failed network node module 30A, and/or based on the location of the failed network node module 30A within the vehicle communication network. Traffic may be routed from the failed network node module 30A directly to the new network node module 30B (e.g., without passing through the central processing module 400) or through the central processing module 400. In the latter case, the central processing module 400 may have another switch coupled thereto to switch traffic received from the failed network node module 30A to the other network node module 30B.

Fig. 7 is a schematic block diagram of another exemplary embodiment of a vehicle communication network 20 within an automotive neural network in accordance with the present invention. The vehicle communication network 20 includes a plurality of network node modules 30, a plurality of bridge routing modules 420, a plurality of switch modules 410, and a central processing module 400. Each switch module 410 is coupled to one or more network node modules 30 and to at least one bridge routing module 420. Each bridge routing module 420 is further coupled to at least one other bridge routing module 420. The couplings between the bridge routing modules 420, between the bridge routing modules 420 and the central processing module 400, between the bridge routing modules 420 and the switch modules 410, and between the switch modules 410 and the network node modules 30 include ethernet links 390 (e.g., unshielded twisted pair, shielded twisted pair, coaxial cable, category 5 or category 6 cable, optical fiber, etc.).

It should be noted that more or fewer switch modules 410 and bridge routing modules 420 may be included in the vehicle communication network 20. Further, it should be noted that the respective connections between the switch module 410 and the bridge routing module 420 may each comprise two or more ethernet links, wherein one of the links is active and the other is used for fault handling or redundancy. It is further noted that the network node module 30 may be directly connected to the bridge routing module 420.

As discussed above, the central processing module 400 operates to determine whether the local processing module of one of the network node modules 30 has failed and, if so, to identify the other network node module 30 to manage traffic from the failed network node module 30. The central processing module 400 further operates to reconfigure the failed network node module 30 and the vehicle communication network 20 to reroute traffic from one or more subsystems within the failed network node module 30 to a new network node module 30. As discussed further above, the new network node module 30 may be selected based on the type of operations performed by one or more subsystems within the failed network node module 30, and/or based on the location of the failed network node module 30 within the vehicle communication network, for example.

As a specific example, the central processing module 400 may select another network node module 30 coupled to the same switch module 410 as the failed network node module 30 to manage traffic from the failed network node module 30 to minimize reconfiguration of the vehicle communication network 20. As another example, if the failed network node module 30 comprises an infotainment device, the central processing module 400 may select a new network node module without regard to the location of the new network node module within the vehicle communication network 20, thereby ensuring that local processing modules within the new network node module are able to process infotainment packets.

FIG. 8 is a schematic block diagram of another embodiment of a reconfigurable network node module within an automotive neural network in accordance with the present invention. In fig. 8, there are three network node modules 30A, 30B and 30C. Network node module 30C is shown to include a processing module 310, a switch 360, a plurality of subsystems 340 (subsystem a, subsystem B, and subsystem C), and network interfaces 370A and 370B. It should be noted that other network interfaces and components may also be included within network node module 30C, as shown in the previous figures.

Network interface 370A is coupled to network node module 30A via Ethernet link 390A, while network interface 370B is coupled to network node module 30B via Ethernet link 390B. Ethernet links 390A and 390B may provide respective direct couplings between network node modules 30A and 30C, as well as between network node modules 30B and 30C, or indirect couplings therebetween (e.g., via one or more switch modules and/or bridge routing modules, and/or via one or more additional network node modules, as shown in fig. 7).

The switch 360 includes a central switch 362 and a selector switch 364. The central switch 362 is coupled to the processing module 310, the subsystem 340, and the selector switch 364. Selector switch 364 is coupled to central switch 362, network interface 370A, and network interface 370B. When the processing module 310 is running, the central switch 362 operates to route traffic between the subsystem 340 and the processing module 310, and when the processing module 310 fails, the central switch 362 reroutes traffic from the subsystem 340 to the selector switch 364. The selector switch 364 operates to route traffic (i.e., packets from one of the subsystems 340) from the central switch 362 to one of the network interfaces 370A or 370B.

Thus, when a local processing module 310 within network node module 30C fails, selector switch 364 operates to select one of the other network node modules 30A or 30B (e.g., based on the destination MAC address of the packet generated by subsystem 340). For example, the network node module 30A or 30B may be selected based on the location of the network node modules 30A-30C within the vehicle communication network, the status of the ethernet links 390A and 390B (congested, malfunctioning, insufficient bandwidth available), the delay requirements of the traffic generated by the subsystem 340, the processing power and/or capacity of each network node module 30A and 30B, and other factors. The selector switch 364 may be further configured to select one network node module 30A for traffic generated by one or more subsystems 340 (e.g., subsystem a) and select the other network node modules 30B for traffic generated by other subsystems 340 (e.g., subsystem B and subsystem C).

FIG. 9 is a schematic block diagram of another embodiment of a reconfigurable network node module within an automotive neural network in accordance with the present invention. In fig. 9, Network Node Modules (NNMs) 30A-30E are coupled together in a hierarchical configuration such that NNM30C is coupled to NNM30A and NNM30B, and NNMs 30C and 30D are coupled to NNM 30E. Thus, local process modules within NNM30C serve as backup process modules for both NNMs 30A and 30B, while local process modules within NNM30E serve as backup process modules for both NNMs 30C and 30D. A multi-tier configuration may be used within a vehicle communication network to minimize wiring and/or provide efficient use of local processing resources. Further, configurations such as those shown in fig. 8 may also be extended to form hierarchical configurations and/or may be used with hierarchical configurations of the type shown in fig. 9.

Fig. 10 is a schematic block diagram of another reconfigurable network node module of an automotive neural network according to the present invention. In fig. 10, the network node module 30 includes a first network interface 330, a second network interface 370, a processing module 310A, a redundant processing module 310B, a switch 360A, a redundant switch 360B, an ethernet bus 350, and a subsystem 340 (subsystem a, subsystem B, and subsystem C). Processing module 310A and redundant processing module 310B are each coupled to first network interface 330 and to switch 360A and redundant switch 360B. The switch 360A and the redundant switch 360B are each further coupled to a second network interface 370 and the ethernet bus 350. It should be understood that the first network interface 330 and the second network interface 370 may each include a plurality of ports. For example, the first network interface 330 may include a separate port for each processing module 310A and 310B, while the second network interface 370 may include a separate port for each switch 360A and 360B. As another example, the first network interface 330 may include two ports each coupled to both processing modules 310A and 310B, while the second network interface 370 may include two ports each coupled to both switches 360A and 360B. It should be further understood that in embodiments utilizing a single processing module and/or a single switch, multiple ports may also be utilized.

In the event of a failure of the primary processing module 310A, the redundant processing module 310B and the redundant switch 360B further provide reliability by eliminating a single point of failure of the switch 360A and reducing network traffic. This redundancy may be beneficial, for example, in mission critical network node modules 30 and/or intensive processing network node modules 30. It should be noted that when redundancy is utilized within one or more network node modules 30 of the vehicle, the network node modules 30 may include only one of the redundancy processor 310B and the redundancy switch 360B, depending on the needs of the vehicle.

FIG. 11 is a logic diagram of a network reconfigurable process for an automotive neural network according to the present invention. The process begins at 500 with a local processing module within a network node module of a vehicle communication network communicating ethernet packets with one or more subsystems within the network node module. At 510, a determination is made whether the local processing module has failed. If so, then at 512, traffic is rerouted from one or more subsystems within the failed network node module to an external processing module within the vehicle communication network.

As used herein, the terms "substantially" and "about" provide an industry-accepted tolerance of relativity between their respective terms and/or items. The industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. The relativity between the objects ranges from a difference of a few percent to a difference of an order of magnitude. As also used herein, the terms "operatively coupled to," "coupled to," and/or "coupled to" include direct couplings between items and/or indirect couplings between items via intermediate items (e.g., items including, but not limited to, components, elements, circuits, and/or modules), where for indirect couplings, intermediate items do not modify signal information but may adjust their current levels, voltage levels, and/or power levels. As may be further used herein, references to coupling (i.e., where one element is referred to as being coupled to another element) include direct and indirect coupling between two items in the same manner as "coupled to". As used even further herein, the term "operatively" or "operatively coupled to" means that the item includes one or more of a power connection, input, output, etc. to perform one or more of its respective functions when activated, and may further include a referred coupling to one or more other items. As may be further used herein, the term "associated with … …" includes direct and/or indirect coupling of separate items and/or embedding of one item within another item.

The invention is also described above with the aid of method steps illustrating the performance of specified functions and their relationships. Boundaries and the order of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences may be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are therefore within the scope and spirit of the claimed invention.

The present invention has been described, at least in part, in terms of one or more embodiments. Embodiments of the invention are used herein to illustrate the invention, aspects of the invention, features of the invention, concepts of the invention and/or examples of the invention. Physical embodiments of devices, articles of manufacture, machines, and/or methods that practice the invention may include one or more of the aspects, features, concepts, examples, etc., described with reference to one or more embodiments discussed herein. Further, between the drawings, embodiments may combine functions, steps, modules, etc. of the same or similar names, which may use the same or different reference numerals, and thus these functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different functions, steps, modules, etc.

The invention has been described above with the aid of functional building blocks illustrating the performance of certain important functions. For ease of illustration, the boundaries of these functional building blocks have been artificially defined. Alternate boundaries may be defined so long as certain important functions are properly implemented. Similarly, flow diagram blocks are also artificially defined herein to illustrate certain important functions. To the extent used, the boundaries and sequence of the flow diagrams can be otherwise defined and still perform some important functions. This alternative definition and ordering of both functional building blocks and flowchart blocks is therefore within the scope and spirit of the claimed invention. Those of ordinary skill in the art will also appreciate that the functional building blocks and other illustrated blocks, modules, and components herein may be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software, etc., or any combination thereof.

Claims (10)

1. A network node module within a vehicle, comprising:

one or more subsystems to perform one or more operations;

a processing module for communicating with the one or more subsystems;

a switch coupled between the one or more subsystems and the processing module;

a first vehicle network interface for coupling the processing module to a vehicle communication network; and

a second vehicle network interface for coupling the switch to an external processing module within the vehicle communication network;

wherein the switch reroutes traffic from the one or more subsystems to the external processing module upon failure of the processing module.

2. The network node module of claim 1, wherein the external processing module is directly coupled to the network node module via the switch.

3. The network node module of claim 1, wherein the external processing module is selected from a group of external processing modules.

4. The network node module of claim 1, wherein the external processing module is within an additional network node module comprising one or more additional subsystems.

5. The network node module of claim 1, wherein the vehicle communication network is an ethernet network.

6. The network node module of claim 1, wherein the switch is a three-port switch having a first port coupled to the processing module, a second port coupled to the second vehicle communication interface, and a third port coupled to an ethernet bus coupling the one or more subsystems to the switch.

7. The network node module of claim 1, wherein the switch comprises: a central switch coupling the processing module to the one or more subsystems, and a selector switch coupling the one or more subsystems to a plurality of external processing modules, the selector switch selecting at least one of the plurality of external processing modules upon failure of the processing module.

8. The network node module of claim 1, wherein the one or more subsystems comprise at least one of sensors, actuators, electronic control units, and infotainment devices.

9. An automotive neural network, comprising:

a plurality of Ethernet links forming a vehicle communication network; and

a plurality of network node modules coupled via the plurality of Ethernet links, wherein each network node module of the plurality of network node modules comprises:

one or more subsystems to perform one or more operations;

a processing module for communicating with the one or more subsystems;

a switch coupled between the one or more subsystems and the processing module;

a first vehicle network interface for coupling the processing module to the vehicle communication network; and

a second vehicle network interface for coupling the switch to an external processing module within another network node module of the vehicle communication network;

wherein upon failure of the processing module, the switch reroutes traffic from the one or more subsystems to the external processing module.

10. A network node module within a vehicle, comprising:

one or more subsystems to perform one or more operations;

a local processing module for communicating with the one or more subsystems;

a first vehicle network interface for coupling the local processing module to a vehicle communication network; and

a second vehicle network interface for coupling the local processing module to a switch of an additional network node module comprising one or more additional subsystems via the vehicle communication network;

wherein the local processing module is configured to communicate with the one or more additional subsystems via the second vehicle network interface upon failure of an additional processing module associated with the additional network node module.