Controller area network early wake-up pulse

Abstract

The invention provides a controller area network early wake-up pulse. The gateway software is initialized in response to receiving a data frame to a first vehicle bus of a plurality of vehicle buses, the data frame configured to be routed to a second vehicle bus of the plurality of vehicle buses. During completion of the initialization of the gateway software, a WUP generator is used to send a WUP along the second vehicle bus. In response to the completion of the initialization of the gateway software, the gateway software is used to route the data frame through the second vehicle bus.

Description

Technical Field

[0001] Aspects of the present disclosure are generally directed to a controller area network (CAN) early wake-up pulse that can be used to reduce electrical system startup time. Background Art

[0002] CAN is a vehicle bus standard designed to allow microcontrollers and devices to communicate with each other. A CAN frame is a unit of data transmitted on the CAN bus. Aspects of the physical and electrical layers of the CAN bus are defined in the International Organization for Standardization (ISO) standard 11898-1. Aspects of the data link layer of the CAN bus are defined in ISO 11898-2. Aspects of the application layer of the CAN bus are defined in ISO 11898-3. Summary of the invention

[0003] In one or more illustrative examples, a system for implementing an early wake-up pulse for a vehicle network includes a networking device that communicates with a plurality of electronic control units (ECUs) via a plurality of vehicle buses, the networking device including gateway software configured to route data frames between the plurality of vehicle buses and a wake-up pulse (WUP) generator configured to generate a WUP when the gateway software is initialized.

[0004] In one or more illustrative examples, a method for implementing an early wake-up pulse for a vehicle network includes initializing gateway software of a networked device in response to receiving a data frame to a first vehicle bus among a plurality of vehicle buses, the data frame being configured to be routed to a second vehicle bus among the plurality of vehicle buses; using a WUP generator to send a WUP along the second vehicle bus before completing the initialization of the gateway software; and routing the data frame through the second vehicle bus in response to the completion of the initialization of the gateway software.

[0005] In one or more illustrative examples, a non-transitory computer-readable medium includes instructions for implementing an early wake-up pulse for a vehicle network, which when executed by one or more processors of a networked device causes the networked device to perform operations, the operations including: initializing gateway software in response to receiving a data frame to a first vehicle bus among a plurality of vehicle buses, the data frame being configured to be routed to a second vehicle bus among the plurality of vehicle buses; using a WUP generator to send a WUP along the second vehicle bus before completing the initialization of the gateway software; and routing the data frame through the second vehicle bus in response to the completion of the initialization of the gateway software. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 An exemplary system including a central gateway configured to implement a CAN early wakeup pulse is shown;

[0007] Figure 2A It shows that the first electronic control unit sends an activity frame to the central gateway via the first CAN bus;

[0008] Figure 2B It shows that the central gateway sends a wake-up pulse via a second CAN bus to which the second electronic control unit is connected;

[0009] Figure 2C The central gateway is shown forwarding an activity frame to a second electronic control unit;

[0010] Figure 3 shows an exemplary simplified diagram of a wake-up pulse; and

[0011] Figure 4 An exemplary process for implementing a CAN early wake-up pulse is shown. DETAILED DESCRIPTION

[0012] Embodiments of the present disclosure are described herein. However, it should be understood that the disclosed embodiments are merely examples, and other embodiments may take on various forms and alternative forms. The drawings are not necessarily drawn to scale; some features may be enlarged or minimized to show the details of a particular component. Therefore, the specific structural details and functional details disclosed herein should not be interpreted as limiting, but only as a representative basis for teaching those skilled in the art to adopt the embodiments in different ways. As will be understood by those of ordinary skill in the art, the various features shown and described with reference to any one of the drawings may be combined with the features shown in one or more other drawings to produce embodiments that are not explicitly shown or described. The combination of features shown provides representative embodiments for typical applications. However, various combinations and modifications of features consistent with the teachings of the present disclosure may be desired for specific applications.

[0013] The vehicle may implement a data architecture with a central gateway connected to multiple ECUs through various vehicle buses. Since a vehicle may include more than one CAN bus, the central gateway may act as a CAN frame and signal gateway router to ensure that ECUs on different CAN buses can wake up and communicate with each other.

[0014] The user can provide input to the vehicle to wake up the vehicle electrical system. The input can trigger the vehicle to wake up the ECU. In turn, the awakened ECU can activate the CAN bus to which it is connected to communicate with other ECUs. For example, if the user presses the brake pedal, the vehicle can perform a power mode state change, a safety check, a high-voltage contactor closure, and / or indicate that propulsion power is available. Alternatively, if the user approaches the vehicle with a key, the vehicle can activate exterior and interior lighting, cause mirrors and power running boards to move, and / or activate exterior speakers. Alternatively, if the user presses an interior hard switch to release the rear door, the door latch can be released. Each of these operations may require communication across the chain of vehicle ECUs that must be awakened. Therefore, the communication can involve passing information through a central gateway.

[0015] Some use cases may require triggering to reaction time within a maximum time budget. In one example, this budget may be less than 250ms. These reaction times may involve a CAN gateway as part of a sequence, especially due to the trend towards central computing and regional architecture network topologies. However, due to the added software content of the gateway and the number of CAN buses in the overall CAN network topology, the CAN gateway functional readiness time from a sleep state may increase. Longer readiness times mean that there may be less margin for other ECUs to wake up and respond, which may increase the difficulty of meeting the use case time expectations for responding to user input.

[0016] One possibility to increase wake-up speed is to add a hardwired wake-up line by connecting a specific wake-up line from one ECU to another to bypass the CAN gateway ready time. However, such additional hardware adds physical expense and can only address latency on a case-by-case basis.

[0017] As discussed in detail herein, a simple software approach can be used to create excitation pulses into a designated vehicle bus while the central gateway is still completing its wake-up sequence. These pulses are referred to herein as early wake-up pulses. This solution not only achieves the timing goals, but also does not require hard wiring or any additional hardware changes within the central gateway and / or other ECUs on the CAN network.

[0018] Figure 1 An exemplary system 100 is shown including a central gateway 110 configured to implement a CAN early wakeup pulse. The central gateway 110 may be connected to a plurality of ECUs 104 via one or more vehicle buses 106. The central gateway 110 may also include one or more diagnostic ports 108. The central gateway 110 may include a processor 112, a memory 114, and a computer-readable storage medium 116 for gateway software 118 and / or data 120. Although Figure 1An exemplary system 100 is shown in FIG. 1 , but the exemplary components shown are not intended to be limiting. In practice, the system 100 may have more or fewer components, and additional or alternative components and / or implementations may be used.

[0019] Vehicle 102 may include various types of automobiles, crossover utility vehicles (CUVs), sport utility vehicles (SUVs), trucks, recreational vehicles (RVs), boats, airplanes, or other mobile machinery for transporting people or goods. In many cases, vehicle 102 may be powered by an internal combustion engine. As another possibility, vehicle 102 may be a hybrid electric vehicle (HEV) powered by both an internal combustion engine and one or more electric motors. In another example, vehicle 102 may be a pure electric vehicle driven only by an electric motor.

[0020] The vehicle 102 may include multiple ECUs 104 configured to execute and manage various vehicle 102 functions under the power of the vehicle battery and / or drive train. As depicted, exemplary vehicle ECUs 104 are represented as discrete ECUs 104-A through 104-H. However, the vehicle ECUs 104 may share physical hardware, firmware, and / or software so that functionality from multiple ECUs 104 may be integrated into a single ECU 104 or distributed across multiple ECUs 104. The vehicle ECUs 104 may include various vehicle 102 components configured to receive updates to associated software, firmware, or configuration settings.

[0021] As examples of some non-limiting vehicle ECUs 104: a powertrain control module (PCM) 104-A may be configured to control engine and transmission components; an anti-lock braking system (ABS) 104-B controller configured to control braking and traction control components; an electric power steering (EPAS) 104-C controller configured to control steering assist and adjust traction or drift compensation functions; an advanced driver assistance system (ADAS) 104-D, such as adaptive cruise control or automated braking; and a headlight control module (HCM) 104-E configured to control light on / off settings. The ECU 104 may also include other powertrain 104-F or chassis 104-G components, an infotainment system 104-H configured to support voice commands and Bluetooth interface with the driver and devices carried by the driver (e.g., the SYNC system provided by Ford Motor Company of Dearborn, Michigan), a connectivity controller 104-I configured to access networked devices outside the vehicle 102 using an embedded modem (such as a telematics control unit (TCU)), mechatronic body controllers 104-J (such as window or lock actuators), and trailer controller 104-K components (such as light control and sensor data to support a connected trailer).

[0022] The vehicle bus 106 may include various communication methods available between the vehicle ECUs 104. The vehicle bus 106 may also support communication between the central gateway 110 and the vehicle ECU 104. These vehicle buses 106 may be implemented as a series of wiring segments. For example, the vehicle bus 106 may include multiple wiring segments from the central gateway 110 to the end location. As some non-limiting examples, the vehicle bus 106 may be a vehicle CAN, an Ethernet network, or a media-oriented system transmission (MOST) network. One or more CAN networks may be of various types, including but not limited to high-speed CAN (HS-CAN) with a data capacity of up to 500kbps, medium-speed CAN (MS-CAN) with a data capacity of up to 125kbps, and / or CAN flexible data rate (FD-CAN) with a data capacity of up to 2000kbps or more. It should be noted that the bus topology shown is only an example, and other numbers and arrangements of vehicle buses 106 may be used.

[0023] The vehicle 102 may also include a diagnostic port 108 that may be used by an external device to monitor the status of the vehicle 102. In one example, the diagnostic port 108 may be an on-board diagnostic (OBD) port connected to the vehicle bus 106. A user may connect a dongle, barcode reader, or other scanning device to the diagnostic port 108 and may use the connection provided by the diagnostic port 108 to gain access to messages traversing the vehicle bus 106. Once connected, the user may utilize the connected scanning device to capture diagnostic codes, monitor vehicle health, or in some cases adjust vehicle settings.

[0024] The central gateway 110 may be configured to provide an electrical interface between vehicle buses 106 for communicating within the vehicle 102. In one example, the central gateway 110 may be configured to route signals from one CAN bus to another CAN bus. In another example, the central gateway 110 may be configured to convert signals and commands between CAN and / or onboard Ethernet vehicle buses 106 connected to the central gateway 110.

[0025] As a specific detailed non-limiting example, the central gateway 110 can be connected to the powertrain 104-F components via the HS-CAN vehicle bus 106; to the chassis components 104-G, drive system and instrument cluster via the second HS-CAN vehicle bus 106; to the infotainment system 104-H via the third HS-CAN vehicle bus 106; to the connectivity 104-I and Ethernet safety backup system via the fourth HS-CAN vehicle bus 106; to the mechatronic body controller 104-J via the first MS-CAN bus; to the trailer controller 104-K and / or nodes easily accessible from the outside of the vehicle 102 via the second MS-CAN vehicle bus 106; to the diagnostic port 108 via the first and second diagnostic data vehicle bus 106 connections; to the PCM 104-A, ABS104-B, EPAS104-C and other controllers via the first FD-CAN vehicle bus 106; and to the ADAS104-D, HCM 104-E and other controllers via the second FD-CAN vehicle bus 106. For example, infotainment 104-H, connectivity 104-I, instrument cluster 104-L, heads-up display 104-M, and ADAS 104-D are each connected to the central gateway 110 via a separate 2-wire 100 Mbps Ethernet vehicle bus 106. In yet another example, the heads-up display 104-M may be integrated with the instrument cluster 104-L.

[0026] The central gateway 110 may also be configured to provide computing functions that support domain CAN messaging of the vehicle 102. For example, the central gateway 110 may include one or more processors 112 configured to execute instructions, commands, and other routines that support the processes described herein. In one example, the central gateway 110 may be configured to execute instructions of a gateway software 118 loaded from a computer-readable storage medium 116 of the central gateway 110 to a memory 114 of the central gateway 110. The computer-readable storage medium 116 (also referred to as a processor-readable medium or storage device) includes any non-transitory medium (e.g., tangible medium) that participates in providing instructions or other data that can be read by the processor 112 of the central gateway 110. Computer-executable instructions can be compiled or interpreted according to a computer program created using various programming languages ​​and / or technologies, including but not limited to the following alone or in combination: Java, C, C++, C#, Objective C, Fortran, Pascal, Java Script, Python, Perl, etc.

[0027] The gateway software 118 may include software code programmed to support the operation of the central gateway 110 discussed in detail herein. For example, the gateway software 118 may include software code for routing information between the various vehicle buses 106 connected to the central gateway 110. The data 120 may include information for supporting the operation of the gateway software 118. In one example, the data 120 may include a mapping of which ECU 104 is located on or addressable from which vehicle bus 106.

[0028] In one example, the central gateway 110 may also be configured to execute instructions of a wakeup pulse generator 122. The WUP generator 122 includes dedicated software to facilitate waking up the ECU 104 during a wakeup sequence of the gateway software 118 of the central gateway 110. The WUP generator 122 software may be executed before the gateway software 118 completes its initialization.

[0029] FIG. 2A to FIG. 2C An exemplary wake-up operation is collectively shown. In this non-limiting example, an active first ECU 104-A activates a first CAN bus 106-A and desires to wake up a second ECU 104-B on a second CAN bus 106-B.

[0030] In a conventional CAN wake-up sequence, the central gateway 110 identifies an active first CAN bus 106-A. Once the gateway software 118 is awakened, the central gateway 110 applies its CAN gateway functionality in its gateway software 118 to route the CAN data frame 202 from the first CAN bus 106-A to the second CAN bus 106-B. The dormant second ECU 104-B on the second CAN bus 106-B identifies the data frame 202 and thus begins waking up its internal electrical system. However, this approach requires the central gateway 110 to fully wake up before the data frame 202 can be sent from the central gateway 110 to the second ECU 104-B.

[0031] exist FIG. 2A to FIG. 2C In the enhanced CAN wake-up sequence shown in , the central gateway 110 identifies an active first CAN bus 106 -A, and when the gateway software 118 initializes, the wake-up pulse generator 122 causes the second ECU 104 -B to begin waking up.

[0032] Figure 2A An example 200A is shown of a first ECU 104-A sending a data frame 202 to a central gateway 110 via a first CAN bus 106-A. The data frame 202 may be sent by the first ECU 104-A in response to the first ECU 104-A waking up. Such waking up may occur, for example, in response to user input as discussed above, such as a user approaching the vehicle 102, depressing a brake pedal, pressing a door open button, etc.

[0033] Figure 2B An example 200B of the central gateway 110 sending a WUP 204 via a second CAN bus 106-B to which a second ECU 104-B is connected is shown. It is worth noting that a sleeping ECU 104 does not require a complete CAN frame to wake up; instead, the ECU 104 only requires a signal that can be identified as a WUP 204. Therefore, data frame 202 identification can be achieved by the CAN transceiver of the ECU 104 and / or the central gateway 110 by sensing a specific predefined CAN bus signal logic transition pattern of the WUP 204.

[0034] Figure 3 An example 300 of a simplified diagram of a WUP 204 is shown. As shown, a specific mode of the WUP 204 involves a predefined transition pattern. The pattern is defined as a dominant-implicit-dominant pulse sequence with certain time constraints. Further details of these transition patterns are described in detail in the ISO 11898-2:2016 wake-up mode specification, which is incorporated herein by reference in its entirety.

[0035] It is worth noting that these pulses do not contain valid data required for a complete CAN frame. Therefore, the central gateway 110 can be programmed to generate WUP 204 without having to load and initialize the complete CAN gateway software 118. For example, the WUP generator 122 of the central gateway 110 can utilize the input of the CAN transceiver, which drives the message from the central gateway 110 to the vehicle bus 106 on the CANH and CANL pins. The WUP generator 122 can set the CAN TXD pin mode to a general input / output (GPIO) in the output direction, and then switch the TXD pin to send the signal to the vehicle bus 106 through the CAN transceiver. The TXD pin operates by feeding the signal into a comparator, which determines whether the signal is low or high based on a reference threshold. Based on the result, the comparator controls the bus driver circuit to drive CANH and CANL (for a low level on TXD) or not drive and keep the CAN bus at a recessive level (e.g., a high level on TXD).

[0036] It should be noted that while the dominant-recessive-dominant pulse sequence is used for CAN, the WUP generator 122 can be configured to generate different types of WUPs 204 to wake up different types of vehicle buses 106 other than CAN. In another example, for an Ethernet bus, the central gateway 110 can instead generate a wake-on-LAN (WOL) pulse to allow an ECU 104 connected via Ethernet to initiate a wakeup, such as via magic packet detection, custom pattern detection, etc.

[0037] Return to Figure 2B And continue to refer to Figure 3 , the WUP 204 may be sent by the WUP generator 122 of the central gateway 110 in response to the central gateway 110 receiving the data frame 202. Since the WUP generator 122 involves simple software code, the WUP generator 122 may be activated and smoothly generate the WUP 204 before the full boot of the gateway software 118. Therefore, the WUP 204 may allow the second ECU 104-B to wake up to be ready to receive the data frame 202 forwarded by the central gateway 110. Therefore, the receiving second ECU 104-B is able to start its wake-up process earlier, rather than waiting for the actual routed CAN data frame 202 from the central gateway 110. Notably, this early wake-up may be performed without changing the CAN physical layer or peripheral hardware.

[0038] Figure 2CThe central gateway 110 is shown forwarding a data frame 202 to the second ECU 104-B. Once the central gateway 110 wakes up, and the second ECU 104-B is awakened via the WUP 204, the data frame 202 may be sent over the second CAN bus 106-B to be received and processed by the second ECU 104-B.

[0039] Figure 4 An exemplary process 400 for implementing a CAN early wakeup pulse is shown. In one example, in the context of the system 100 discussed in detail herein, the process 400 can be performed by a central gateway 110. For example, the central gateway 110 can communicate with multiple ECUs 104 via multiple vehicle buses 106 and can include gateway software 118 configured to route data frames 202 between the multiple vehicle buses 106 and a WUP 204 generator configured to generate a WUP 204 before and / or while the gateway software 118 is initialized.

[0040] At operation 402, the central gateway 110 receives a data frame 202. In one example, the data frame 202 may be received from a first vehicle bus 106 of the plurality of vehicle buses 106, wherein the data frame 202 is configured to be routed to a second vehicle bus 106 of the plurality of vehicle buses 106. For example, the data frame 202 may be received from a first ECU 104-A of the plurality of ECUs 104 and addressed to a second ECU 104-B of the plurality of ECUs 104. The first ECU 104-A may be connected to the central gateway 110 via a first CAN bus 106-A, and the second ECU 104-B may be connected to the central gateway 110 via a second CAN bus 106-B.

[0041] At operation 404, the central gateway 110 initializes the gateway software 118. The initialization of the gateway software 118 may allow the central gateway 110 to route the data frames 202 between the various vehicle buses 106 connected to the central gateway 110. The gateway software 118 may utilize the data 120 to map which ECU 104 is located in (or addressable from) which of the vehicle buses 106.

[0042] At operation 406, the central gateway 110 uses the WUP generator 122 to send the WUP 204. For example, during or before the completion of initialization of the gateway software 118, the central gateway 110 may utilize the WUP generator 122 to send the WUP 204 along the second vehicle bus 106. In one example, the WUP generator 122 may generate the WUP 204 over the CAN vehicle bus 106 using the TXD pin of the transceiver of the central gateway 110. As one possibility, the WUP generator 122 may toggle the TXD pin to generate a dominant-recessive-dominant pulse sequence of the WUP 204 in accordance with the ISO 11898-2:2016 wake-up pattern specification.

[0043] At operation 408, the central gateway 110 routes the data frame 202. For example, in response to completion of initialization of the gateway software 118, the central gateway 110 may send the data frame 202 over the second vehicle bus 106. After operation 408, the process 400 ends.

[0044] Thus, the central gateway 110 can create a specific excitation pulse that can be identified as a WUP 204 on the CAN bus at an early stage of the wake-up sequence while the complete gateway software 118 stack is still being loaded and the CAN gateway functionality is not yet available. The dormant ECU 104 can recognize the pulse and begin waking up the internal electrical system, rather than waiting for the data frame 202 to be routed and arrive.

[0045] The implementation and software involved in the WUP generator 122 is simple and independent of other software stacks, so it can be executed much faster than the actual CAN gateway function. Compared with the added hardwired wake-up line solution (e.g., ignition line, accessory line), no hardwired wake-up line or any physical ECU or network hardware changes are required. For CAN, this approach can be based on the ISO 11898-2:2016 specification, so the generated WUP 204 can be recognized by any off-the-shelf CAN transceiver (e.g., embedded in the ECU 104 or otherwise) with WUP 204 recognition capabilities.

[0046] Although exemplary embodiments are described above, these embodiments are not intended to describe all possible forms covered by the claims. The words used in the specification are descriptive words rather than restrictive words, and it should be understood that various changes can be made without departing from the spirit and scope of the present disclosure. As previously described, the features of various embodiments can be combined to form other embodiments of the present invention that may not be explicitly described or shown. Although various embodiments may have been described as providing advantages or being superior to other embodiments or prior art implementations in terms of one or more desired characteristics, it should be recognized by those of ordinary skill in the art that one or more features or characteristics can be compromised to achieve the desired overall system properties, depending on the specific application and implementation. These properties may include, but are not limited to, strength, durability, life cycle, marketability, appearance, packaging, size, serviceability, weight, manufacturability, ease of assembly, etc. For this reason, in terms of one or more characteristics, to the extent that any embodiment is described as less than other embodiments or prior art implementations are ideal, these embodiments are not outside the scope of the present disclosure and may be desired for specific applications.

[0047] According to the present invention, a system for implementing an early wake-up pulse of a vehicle network is provided, comprising: a networking device, the networking device communicating with a plurality of electronic control units (ECUs) via a plurality of vehicle buses, the networking device comprising gateway software, the gateway software being configured to route data frames between the plurality of vehicle buses and a wake-up pulse (WUP) generator, the WUP generator being configured to generate a WUP when the gateway software is initialized.

[0048] According to an embodiment, a networking device is configured to: start initializing gateway software in response to receiving a data frame to a first vehicle bus among a plurality of vehicle buses, the data frame being configured to be routed to a second vehicle bus among the plurality of vehicle buses; utilize a WUP generator to send a WUP along the second vehicle bus before completing the initialization of the gateway software; and route the data frame through the second vehicle bus in response to the completion of the initialization of the gateway software.

[0049] According to an embodiment, the data frame is received from a first ECU of the plurality of ECUs and is addressed to a second ECU of the plurality of ECUs.

[0050] According to an embodiment, after the gateway software is initialized, the networking device is configured to utilize the mapping of the ECU to the vehicle bus to determine to which vehicle bus of the plurality of vehicle buses the data frame is to be routed.

[0051] According to an embodiment, the WUP generator is configured to generate the WUP via a controller area network (CAN) bus using a TXD pin of a transceiver of the networked device.

[0052] According to an embodiment, the WUP generator is configured to switch the TXD pin to generate a dominant-recessive-dominant pulse sequence of the WUP according to a wake-up mode specification as defined in the International Organization for Standardization (ISO) 11898-2:2016.

[0053] According to an embodiment, the networking device is a central gateway of the vehicle.

[0054] According to an embodiment, the plurality of vehicle buses comprises one or more Controller Area Network (CAN) buses.

[0055] According to the present invention, a method for implementing an early wake-up pulse of a vehicle network includes: initializing gateway software of a networked device in response to receiving a data frame to a first vehicle bus among multiple vehicle buses, wherein the data frame is configured to be routed to a second vehicle bus among the multiple vehicle buses; before completing the initialization of the gateway software, using a WUP generator to send a WUP along the second vehicle bus; and in response to the completion of the initialization of the gateway software, routing the data frame through the second vehicle bus.

[0056] In one aspect of the invention, the data frame is received from a first ECU of a plurality of ECUs and is addressed to a second ECU of the plurality of ECUs.

[0057] In one aspect of the present invention, after the gateway software is initialized, the mapping of the ECU to the vehicle bus is used to determine to which vehicle bus of the plurality of vehicle buses the data frame is to be routed.

[0058] In one aspect of the invention, the method includes generating the WUP using the WUP generator via a controller area network (CAN) bus using a TXD pin of a transceiver of the networked device.

[0059] In one aspect of the invention, the method includes switching, by the WUP generator, the TXD pin to generate a dominant-recessive-dominant pulse sequence of the WUP according to a wake-up mode specification as defined in International Standards Organization (ISO) 11898-2:2016.

[0060] In one aspect of the invention, the networking device is a central gateway of the vehicle.

[0061] According to the present invention, a non-transitory computer-readable medium is provided, which has instructions for implementing an early wake-up pulse of a vehicle network, and when the instructions are executed by one or more processors of a networked device, the networked device performs operations, the operations including: initializing gateway software in response to receiving a data frame to a first vehicle bus among multiple vehicle buses, the data frame being configured to be routed to a second vehicle bus among the multiple vehicle buses; before completing the initialization of the gateway software, using a WUP generator to send a WUP along the second vehicle bus; and in response to the completion of the initialization of the gateway software, routing the data frame through the second vehicle bus.

[0062] According to an embodiment, the data frame is received from a first ECU of a plurality of ECUs and is addressed to a second ECU of the plurality of ECUs.

[0063] According to an embodiment, the medium also includes instructions that, when executed by one or more processors of the networking device, cause the networking device to perform the following operations: after initializing the gateway software, use the mapping of the ECU to the vehicle bus to determine which vehicle bus among the multiple vehicle buses to route the data frame.

[0064] According to an embodiment, the medium further comprises instructions that, when executed by one or more processors of a networked device, cause the networked device to perform operations comprising: using the WUP generator to generate the WUP via a controller area network (CAN) bus using a TXD pin of a transceiver of the networked device.

[0065] According to an embodiment, the medium also includes instructions that, when executed by one or more processors of the networking device, cause the networking device to perform operations including the following: the WUP generator switches the TXD pin to generate a dominant-implicit-dominant pulse sequence of the WUP according to the wake-up mode specification as defined in the International Organization for Standardization (ISO) 11898-2:2016.

[0066] According to an embodiment, the networking device is a central gateway of the vehicle.

Claims

1. A system for implementing an early wake-up pulse of a vehicle network, comprising: A networking device that communicates with a plurality of electronic control units (ECUs) via a plurality of vehicle buses, the networking device comprising gateway software configured to route data frames between the plurality of vehicle buses and a wake-up pulse (WUP) generator configured to generate a WUP when the gateway software is initialized.

2. The system of claim 1, wherein the networking device is configured to: Beginning to initialize the gateway software in response to receiving a data frame to a first vehicle bus of the plurality of vehicle buses, the data frame being configured to be routed to a second vehicle bus of the plurality of vehicle buses; before completing the initialization of the gateway software, utilizing the WUP generator to send the WUP along the second vehicle bus; as well as Responsive to the completion of the initialization of the gateway software, the data frame is routed over the second vehicle bus. 3 . The system of claim 2 , wherein the data frame is received from a first ECU of the plurality of ECUs and is addressed to a second ECU of the plurality of ECUs.

4. The system of claim 2, wherein after the gateway software is initialized, the networking device is configured to utilize the mapping of the ECU to the vehicle bus to determine to which of the plurality of vehicle buses the data frame is to be routed.

5. The system of claim 1, wherein the WUP generator is configured to generate the WUP via a controller area network (CAN) bus using a TXD pin of a transceiver of the networked device.

6. The system of claim 5, wherein the WUP generator is configured to toggle the TXD pin to generate a dominant-recessive-dominant pulse sequence of the WUP according to a wake-up mode specification as defined in International Standards Organization (ISO) 11898-2:2016.

7. The system of claim 1, wherein the networking device is a central gateway of the vehicle.

8. The system of claim 1, wherein the plurality of vehicle buses comprises one or more controller area network (CAN) buses.

9. A method for implementing an early wake-up pulse of a vehicle network, comprising: initializing gateway software of the networking device in response to receiving a data frame to a first vehicle bus of a plurality of vehicle buses, the data frame being configured to be routed to a second vehicle bus of the plurality of vehicle buses; before completing the initialization of the gateway software, using a WUP generator to send a WUP along the second vehicle bus; as well as Responsive to the completion of the initialization of the gateway software, the data frame is routed over the second vehicle bus.

10. The method of claim 9, wherein the data frame is received from a first ECU of a plurality of ECUs and is addressed to a second ECU of the plurality of ECUs.

11. The method of claim 10, wherein after the gateway software is initialized, a mapping of the ECU to the vehicle bus is used to determine which vehicle bus among the plurality of vehicle buses to route the data frame to.

12. The method of claim 9, further comprising using the WUP generator to generate the WUP over a controller area network (CAN) bus using a TXD pin of a transceiver of the networked device.

13. The method of claim 12, further comprising switching, by the WUP generator, the TXD pin to generate a dominant-recessive-dominant pulse sequence of the WUP in accordance with a wake-up mode specification as defined in International Standards Organization (ISO) 11898-2:2016.

14. The method of claim 9, wherein the networked device is a central gateway of the vehicle.

15. A non-transitory computer-readable medium comprising instructions for implementing an early wake-up pulse of a vehicle network, the instructions, when executed by one or more processors of a network-connected device, causing the network-connected device to perform operations comprising: initializing gateway software in response to receiving a data frame to a first vehicle bus of a plurality of vehicle buses, the data frame being configured to be routed to a second vehicle bus of the plurality of vehicle buses; before completing the initialization of the gateway software, using a WUP generator to send a WUP along the second vehicle bus; as well as Responsive to the completion of the initialization of the gateway software, the data frame is routed over the second vehicle bus.

Images