Note : Les descriptions sont présentées dans la langue officielle dans laquelle elles ont été soumises.
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 REDUNDANT FIBER OPTIC NETWORK AND PROCESSING SYSTEM FOR ELECTRIC
2 ENERGY SOURCE MANAGEMENT AND RELATED METHODS
3
4
CROSS-REFERENCE TO RELATED APPLICATIONS
6 [001] This application claims priority to United States Provisional
Patent Application No.
7 63/084,977, filed on September 29, 2020, and titled "Redundant Fiber
Optic Network And
8 Processing Systems For Electric Energy Source Management And Related
Methods", the
9 entire contents of which are herein incorporated by reference.
TECHNICAL FIELD
11 [002] The following generally relates to a redundant fiber optic
network and processing
12 system for electric energy source management and related methods.
13 DESCRIPTION OF THE RELATED ART
14
[003] Vehicles (e.g., trucks, buses, cars, marine vehicles, aircraft, etc.)
are becoming
16 more electrically driven. For example, electric motors are being used as
primary drivers or
17 secondary drivers for motive force instead of combustion engines. This
requires a larger
18 battery system to provide electrical power. Larger battery systems
typically include many
19 battery cells that are connected together to provide the current draw
and voltage levels used
by motors and other electrical devices (e.g., heating, cooling, braking,
actuators, etc.).
21 Battery management systems are used to manage the large number of
batteries. These
22 battery management systems are also used in power or utility grids, such
as for power
23 generators, power banks, buildings, and facilities.
24 [004] In vehicles and other battery applications mentioned above,
sets of battery cells
are managed by battery nodes. These battery nodes are managed by a command
node,
26 sometimes called an electronic control unit (ECU) or host node. Battery
nodes and the host
27 node are in data communication together via a wired network, typically
copper or some other
28 electrical conductor. It is herein recognized that if a wire breaks or
if an intermediate
29 communication component is damaged, then a battery node and its
corresponding set of
battery cells are cut off from the wired network.
31 [005] It is also herein recognized that wired battery management
systems require
32 specialized electronics, such as transformers, to provide isolation
between the battery nodes
33 and the battery cells. However, these isolation systems are prone to
failure due to the
34 windings or other types of isolation. These isolation systems also
increase costs. It is
further herein recognized that as a battery system becomes larger (e.g.,
hundreds or
36 thousands of cells), more battery cells will require individual
monitoring and control. This
- 1 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 means that more volume of data is being captured and sent in a battery
management
2 system, and that existing battery management systems may not be able to
accommodate
3 the desired bandwidth of data and desired data transfer speeds.
4 [006] Similar problems are experienced when coordinating other types
of electric
energy sources. For example, electric generators, fuel cells, solar cells,
etc. are used in
6 vehicles and electric energy management grids.
7 [007] It is therefore desirable to herein provide a reliable and fast
network to help the
8 electric energy management system to become safer and more responsive.
Disruption in
9 the transmission of data, or in the processing of the data, would hinder
the electric energy
management system's responsiveness and decrease the safety of the relying
vehicle or
11 relying electric energy management grid.
12 BRIEF DESCRIPTION OF THE DRAWINGS
13 [008] Embodiments will now be described by way of example only with
reference to
14 the appended drawings wherein:
[009] FIG. 1A is a schematic diagram of a fiber optic redundant electric
energy source
16 management system, according to an example embodiment.
17 [0010] FIG. 1B is a schematic diagram of a fiber optic redundant
battery management
18 system, according to an example embodiment.
19 [0011] FIG. 1C is a schematic diagram of a fiber optic redundant fuel
cell management
system, according to an example embodiment.
21 [0012] FIG. 1D is a schematic diagram of a fiber optic redundant
solar cell management
22 system, according to an example embodiment.
23 [0013] FIG. 2 is a schematic diagram of a fiber optic redundant
electric energy source
24 management system, including components of a redundancy module having a
software
Ethernet architecture, according to an example embodiment.
26 [0014] FIG. 3 is a schematic diagram of a fiber optic redundant
electric energy source
27 management system, including components of a redundancy module having a
hardware
28 Ethernet architecture, according to an example embodiment.
29 [0015] FIG. 4 is a schematic diagram of a fiber optic redundant
electric energy source
management system, including components of a redundancy module having a
hardware
31 architecture that is in alternative to Ethernet, according to an example
embodiment.
- 2 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [0016] FIG. 5 is a flow diagram of processor executable instructions
for detecting a
2 communication error in the fiber optic redundant electric energy source
management
3 system, according to an example embodiment.
4 [0017] FIG. 6 is a flow diagram of processor executable instructions
for a given node to
evaluate the redundancy status of a fiber optic redundant electric energy
source
6 management system, according to an example embodiment.
7 [0018] FIG. 7 is a flow diagram of processor executable instructions
for a command
8 node transmitting two instances of a message in both directions, and a
given node in the
9 fiber optic redundant electric energy source management system processing
one or both
instances of the message, according to an example embodiment.
11 [0019] FIG. 8 is a flow diagram of processor executable instructions
for a command
12 node transmitting a comm-check message and an electric energy source
node in a fiber
13 optic redundant battery management system processing the comm-check
message,
14 according to an example embodiment.
[0020] FIG. 9 is a flow diagram of processor executable instructions for a
command
16 node to transmit a comm-check message in a fiber optic redundant
electric energy source
17 management system and to process feedback results from the comm-check,
according to an
18 example embodiment.
19 [0021] FIG. 10 is a flow diagram of processor executable instructions
for a given node
in a fiber optic redundant electric energy source management system for
processing
21 emergency events, according to an example embodiment.
22 [0022] FIG. 11 is a schematic diagram of two daisy chain loops that
are connected
23 together using a quad-port redundancy module, forming a fiber optic
redundant electric
24 energy source management system, according to an example embodiment. One
of the
daisy chain loops includes a command node that controls electric energy source
nodes
26 across the entire system.
27 [0023] FIG. 12 is a schematic diagram of two daisy chain loops that
are connected
28 together using two quad-port redundancy modules, forming a fiber optic
redundant electric
29 energy source management system, according to an example embodiment.
Each of the
daisy chain loops includes a command node that controls electric energy source
nodes
31 across the entire system.
32 [0024] FIG. 13A is a schematic diagram of two control loops
connecting multiple electric
33 energy source node loops, which together form a fiber optic redundant
battery management
- 3 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 system, according to an example embodiment. Each of the control loops
includes a
2 command node that controls electric energy source nodes across the entire
system.
3 [0025] FIG. 13B is a schematic diagram of a control loop connecting
multiple electric
4 energy source node loops, which together form a fiber optic redundant
electric energy
source management system, according to an example embodiment. The control loop
6 includes a command node that controls electric energy source nodes across
the entire
7 system.
8 [0026] FIG. 14 is a schematic diagram of a quad-port redundancy
module, including
9 components for a fiber optic-based software Ethernet architecture,
according to an example
embodiment.
11 [0027] FIG. 15 is a schematic diagram of a quad-port redundancy
module, including
12 components for a fiber optic-based hardware Ethernet architecture,
according to an example
13 embodiment.
14 [0028] FIG. 16 is a schematic diagram of an electric energy source
node, including
components for a fiber optic-based multichannel software Ethernet architecture
for a
16 redundancy module, according to an example embodiment. In the example,
the redundancy
17 module has a symmetrical configuration.
18 [0029] FIG. 17 is a flow diagram showing the flow of data in an
example symmetrical
19 multichannel Ethernet architecture in a redundancy module, according to
an example
embodiment.
21 [0030] FIG. 18 is a flow diagram of processor executable instructions
for a redundancy
22 module with symmetrical multichannel Ethernet architecture, and in
particular for processing
23 data in a fiber optic electric energy source management system.
24 [0031] FIG. 19 is a schematic diagram of an electric energy source
node, including
components for an optic-based multichannel software Ethernet architecture for
a redundancy
26 module, according to an example embodiment. In the example, the
redundancy module has
27 an asymmetrical configuration.
28 [0032] FIG. 20 is a flow diagram of showing the flow of data in an
example
29 asymmetrical multichannel Ethernet architecture in a redundancy module,
according to an
example embodiment.
31 [0033] FIG. 21 is a flow diagram of processor executable instructions
for a redundancy
32 module with asymmetrical multichannel Ethernet architecture, and in
particular for
33 processing data in a fiber optic electric energy source management
system.
- 4 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [0034] FIG. 22 is a schematic diagram of a vehicle that includes an
electric energy
2 source management system, according to an example embodiment.
3 [0035] FIG. 23 is a schematic diagram of a power supply unit that
includes an electric
4 energy source management system, and that supplies power to an electric
load, according
to an example embodiment.
6 [0036] FIG. 24 is a schematic diagram of multiple power supply units
that each include
7 an electric energy source management system, and that are connected to an
electric
8 distribution grid, according to an example embodiment.
9
DETAILED DESCRIPTION
11 [0037] It will be appreciated that for simplicity and clarity of
illustration, where
12 considered appropriate, reference numerals may be repeated among the
figures to indicate
13 corresponding or analogous elements. In addition, numerous specific
details are set forth in
14 order to provide a thorough understanding of the example embodiments
described herein.
However, it will be understood by those of ordinary skill in the art that the
example
16 embodiments described herein may be practiced without these specific
details. In other
17 instances, well-known methods, procedures and components have not been
described in
18 detail so as not to obscure the example embodiments described herein.
Also, the
19 description is not to be considered as limiting the scope of the example
embodiments
described herein.
21 [0038] Within this specification, different structural entities
(which may variously be
22 referred to as "nodes", "units", "circuits", "systems", "processors",
"module", "interface", other
23 components, etc.) may be described or claimed as "configured" to perform
one or more
24 tasks or operations. This formulation ¨ [entity] configured to [perform
one or more tasks] ¨ is
used herein to refer to structure (i.e., something physical, such as an
electronic circuit).
26 More specifically, this formulation is used to indicate that this
structure is arranged to
27 perform one or more tasks during operation. A structure can be said to
be "configured to"
28 perform some task even if the structure is not currently being operated.
A "processor
29 configured to generate and transmit a message via a data port" is
intended to cover, for
example, an integrated circuit that has circuitry that performs this function
during operation,
31 even if the integrated circuit in question is not currently being used
(e.g., a power supply is
32 not powering it). Thus, an entity described or recited "configured to"
perform some task
33 refers to something physical, such as a device, circuit, memory storing
program instructions
34 executable to implement the task, etc. This phrase is not used herein to
refer to something
- 5 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 intangible. Thus, the "configured to" construct is not used herein refer
to a software entity,
2 such as an application programming interface (API).
3 [0039] The term "configured to" is not intended to mean "configurable
to." An
4 unprogrammed Field Programmable Gate Array (FPGA), for example, would not
be
considered to be "configured to" execute some specific operation, although it
may be
6 "configurable to" perform that specific operation and may be "configured
to" execute that
7 specific function after programming.
8 [0040] Reciting in the appended claims that a structure is "configured
to" perform one or
9 more tasks is intended not to be interpreted as having means-plus-
function elements.
[0041] Throughout the specification and the claims, the following terms
take at least the
11 meanings explicitly associated herein, unless the context clearly
dictates otherwise. The
12 term or is intended to mean an inclusive or. Further, the terms "a," an,
and the are
13 intended to mean one or more unless specified otherwise or clear from
the context to be
14 directed to a singular form.
[0042] In this specification, numerous specific details have been set
forth. It is to be
16 understood, however, that implementations of the disclosed technology
may be practiced
17 without these specific details. In other instances, well-known methods,
structures, and
18 techniques have not been shown in detail in order not to obscure an
understanding of this
19 description. References to "for example", some examples," "other
examples," one
example," "an example," "various examples," one embodiment," "an embodiment,"
some
21 embodiments," "example embodiment," "various embodiments," one
implementation," "an
22 implementation," "example implementation," "various implementations,"
some
23 implementations," etc., indicate that the implementation(s) of the
disclosed technology so
24 described may include a particular feature, structure, or
characteristic, but not every
implementation necessarily includes the particular feature, structure, or
characteristic.
26 Further, repeated use of the phrases in one example," "in one
embodiment," or in one
27 implementation" does not necessarily refer to the same example,
embodiment, or
28 implementation, although it may.
29 [0043] As used herein, unless otherwise specified the use of the
ordinal adjectives
"first," "second," "third," etc., to describe a common object, merely indicate
that different
31 instances of like objects are being referred to, and are not intended to
imply that the objects
32 so described must be in a given sequence, either temporally, spatially,
in ranking, or in any
33 other manner.
34 [0044] It is herein recognized that many of the communication systems
in energy
source management systems (e.g., battery cell management systems, fuel cell
management
- 6 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 systems, solar cell management systems, other energy cells, etc.) connect
nodes together
2 using copper wiring. However, copper wiring has slower data transfer
speeds than fiber
3 optic cables. Copper wires also require transformers or other isolating
devices, for example
4 optocouplers between nodes and the energy cells to isolate the circuitry
of a node from the
energy cells. Furthermore, battery cells, fuel cells, solar cells, electric
generators (e.g.,
6 powered by gas, wind, moving water, braking, etc.) can cause power spikes
that can
7 damage the control circuitry. It is herein recognized that some types of
isolating devices
8 slow down the processing and transmission of data, reduce reliability and
add costs to the
9 system. Slower data speeds and delays in processing can affect an
electric energy source
management system's operation, especially when reacting in emergency
situations where
11 timing can be critical.
12 [0045] It is also herein recognized that US Patent Application
Publication no.
13 2019/0006723 to Martin et al. describes multi-channel using different
frequency of electrical
14 signals. Martin et al. describes a transformer for isolating the battery
cells from the control
circuitry. This creates complexity, weight, in transferring signal data
between the battery
16 cells and the control circuitry. Martin et al. also describes sending
data in one direction in a
17 daisy chain first, and if the host detects the condition of a missing
signal from a client node,
18 then sending a second command in the second direction in the daisy
chain. This process
19 incurs significant delay. It is herein recognized that time sensitive
data that is not captured
or received on time leads to missed data windows. These missed data windows
(e.g., data
21 is received too late) can lead to dangerous results, such as in
emergency situations.
22 [0046] It is also herein recognized that existing communication
networks typically have
23 50 milliseconds to 30 seconds to recover from a failure or breakage. In
cases where no
24 packet loss is required, this delay is not acceptable.
[0047] It also herein recognized that more redundancy is better. Vehicles
that use
26 batteries or fuel cells, or both, are mobile, and it is desirable to
operate a battery cell
27 management system, or fuel cell management system, or both, in the field
with little
28 maintenance even if damaged. Therefore, a safe and robust electric
energy source
29 management system is desirable for vehicles.
[0048] The same issues arise for generator systems and power banks, which
can
31 sometimes operate in environmentally harsh and remote conditions.
Generator systems and
32 power banks can be damaged during shipping, setup and over time due to
environmental
33 events (e.g., accidents, weather, impacts from other objects, etc.).
Therefore, a safe and
34 robust electric energy source management system is desirable for
generator systems and
power banks.
- 7 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [0049] It is also herein recognized that more data is being captured
and processed as
2 battery cell management systems, solar cell management systems, fuel cell
management
3 systems, and combinations thereof, continue to advance. Examples of data
in battery cell
4 management systems include: pressure sensor data for batteries;
temperature sensor data
for batteries; humidity sensor data for batteries; volatile organic compound
(VOC) chemistry
6 presence sensor history logs of batteries; control and monitoring data of
cooling units or
7 heating units, or both, associated with batteries; control and monitoring
data of shock/force
8 absorbent systems associated with batteries; voltage data; current data;
state of charge
9 data; and other control data of devices associated with batteries
including but not limited to
pressure vents, circuit breakers, etc.
11 [0050] It will be appreciated that aspects of the battery data are
also applicable to other
12 types of electric energy cells. In an example embodiment, data in fuel
cell management
13 systems include: pressure sensor data; temperature sensor data; flow
rate data; valve
14 control data; state of charge; current data; voltage data; pump control
data; compressor
control data; etc. In an example embodiment, data in solar cell management
systems
16 include: temperature sensor data; light sensor data (e.g., solar
radiation); voltage data;
17 current data; etc.
18 [0051] Therefore, it is desirable to transfer this energy cell
related data faster and
19 without interruption.
[0052] Turning to FIG. 1A, an example of an electric energy source
management
21 system 100 is provided, which includes electric energy sources 101a
connected to an
22 energy source node 102a. Multiple electric energy source nodes 102a,
102b, 102n are
23 connected together in a fiber optic network with a command node 106, in
a daisy chain ring
24 topology, also called a daisy chain communication ring. In an example
aspect, electric
energy source nodes 102a, 102b, 102n are respectively connected to a set of
electric energy
26 sources 101a, 101b, 101n.
27 [0053] In an example aspect, the electric energy sources in the
system include: battery
28 cells, fuel cells, solar cells, electric generators, or a combination
thereof. It will be
29 appreciated that battery cells, fuel cells and solar cells are typical
examples of energy cells.
Electric energy sources, for example, generate electricity or store
electricity, or both.
31 Vehicles, power grids, and power banks typically include battery cells.
In some example
32 embodiments, vehicles, power grids, and power banks include an electric
energy source
33 management system that combines battery cells with one or more other
types of electric
34 energy sources (e.g., fuel cells, solar cells, electric generator,
etc.).
- 8 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [0054] Electric energy source node 102a includes a redundancy module
104a and an
2 electric energy source interface 103a. The redundancy module 104a
provides data
3 processing and redundant communication in the fiber optic network. The
electric energy
4 source interface 103a connects to the electric energy source 101a.
Similarly, electric energy
source node 102b includes a redundancy module 104b and electric energy source
interface
6 103b; and electric energy source node 102n includes a redundancy module
104n and
7 electric energy source interface 103n.
8 [0055] The term "electric energy source" is herein also referred to as
EES.
9 [0056] The EES interface, for example, includes circuitry that
connects to the EES.
[0057] The command node 106 includes a redundancy module 104e and an
Electronic
11 Control Unit (ECU) 105. In other example embodiments, the command node
includes a
12 Battery Control Unit (BCU), and the redundancy module 104e is instead
connected to the
13 BCU.
14 [0058] In the example shown, a fiber optic cable Fl connects between
the redundancy
module 104a of the EES node 102a and the redundancy module 104e of the command
node
16 106. Another fiber optic cable F2 connects between the redundancy module
104a of the
17 EES node 102a and the redundancy module 104b of the EES node 102b.
Another fiber
18 optic cable F3 connects between the redundancy module 104b of the EES
node 102b and
19 the redundancy module 104n of the EES node 102n. Another fiber optic
cable F4 connects
between the redundancy module 104n of the EES node 102n and the redundancy
module
21 104e of the command node 106. Data is transmitted in both directions at
the same time in a
22 given fiber optic cable. In other words, a redundancy module of a given
node transmits
23 duplicate instances of a message simultaneously in different directions
along the daisy chain
24 communication ring.
[0059] When referring a given node transmitting messages, the terms "at the
same
26 time", "at a same time", and "simultaneously" herein mean that the given
node initiates
27 transmission a first instance of a message through one data port and
initiates transmission
28 of a second instance of the same message through another data port of
the given node
29 within a same time frame. For example, a given node initiates
transmission of the first
instance of the message and the second instance of the same message within a 1-
second
31 time frame, or less, of each other. In another example, a given node
initiates transmission of
32 the first instance of the message and the second instance of the same
message within a 1-
33 millisecond time frame, or less, of each other. In another example, a
given node initiates
34 transmission of the first instance of the message and the second
instance of the same
message within a 100-microsecond time frame, or less, of each other. In
another example,
- 9 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 a given node initiates transmission of the first instance of the message
and the second
2 instance of the same message within a 10-microsecond time frame, or less,
of each other.
3 In another example, a given node initiates transmission of the first
instance of the message
4 and the second instance of the same message within a 1-microsecond time
frame, or less,
of each other. In another example, a given node initiates transmission of the
first instance of
6 the message and the second instance of the same message within a 100-
nanosecond time
7 frame, or less, of each other. In another example, a given node initiates
transmission of the
8 first instance of the message and the second instance of the same message
within a n-
9 second time frame of each other, whereby n is a number that is
appropriate for energy
management systems and the capability of the hardware or the software, or
both, used in
11 the given node.
12 [0060] Fiber optic cables carry data in the form of light between
nodes in the EES
13 management system 100. Each of the redundancy modules in the nodes
includes a
14 transmitting device that converts an electrical signal into a light
signal, and a receiver that
accepts a light signal and converts the light signal into an electrical
signal. Fiber optic cables
16 are galvanically isolated and provide a robust communication interface
at the nodes. In this
17 way, unlike electrically wired systems, transformers or other types of
electrical isolation
18 devices are not needed at the EES nodes. Fiber optic cables are also
intrinsically safe and
19 do not require shielding, which is typically a factor when running
cables around large battery
systems and electric motors that emit electromagnetic interference (EMI). In
particular, fiber
21 optic cables are immune to EMI, which maintains data integrity in the
battery management
22 system.
23 [0061] In an example aspect, the fiber optic cable transfers data at
and over 10
24 Megabytes per second (Mbps). In another example aspect, the fiber optic
cable transfers
data at approximately 100 Mbps or more. In another example aspect, the fiber
optic cable
26 transfers data at approximately 1 Gigabyte per second (Gbps) or more. In
another example
27 aspect, the fiber optic cable transfers data at approximately 10 Gbps or
more.
28 [0062] In an example aspect, a given fiber optic cable, such as F1,
includes one fiber
29 that transmits communication data in both directions. In other words, F1
includes one fiber;
F2 includes one fiber; F3 includes on fiber, and so forth.
31 [0063] In another example aspect, a given fiber optic cable, such as
F1, includes at
32 least a first fiber that transmits communication data in a first
direction, and a second fiber
33 that transmits communication data in a second direction. In other words,
F1 includes at least
34 two fibers; F2 includes at least two fibers; F3 includes at least two
fibers, and so forth.
- 10 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [0064] In an example aspect, the fiber optic cable to connect the
nodes is made of
2 glass optical fiber. In an example aspect, glass optical fiber has a
small diameter, is light
3 weight, and can be bent at a small radius. In another example aspect,
glass optical fiber can
4 withstand a wide temperature range.
[0065] In another example aspect, the fiber optic cable to connect the
nodes is made of
6 plastic optical fiber. In an example aspect, plastic optical fiber has a
large diameter, which
7 makes it easier for connector alignment.
8 [0066] The EES node 102a processes data in relation to the EES 101a,
and monitors
9 operational parameters of the EES 101a.
[0067] Examples of operational parameters for battery cells include the
status of
11 voltages, currents and temperatures with the battery cells, state of
charge (SOC), and state
12 of health (SOH). Other operations include monitoring and recording
history logs of when
13 and how many times the battery cells were charged and discharged,
temperature profiles,
14 cooling operations, heating operations, etc. The battery node may also
isolate the battery
cells, for example, in cases of emergency or for based on other conditions. It
will be
16 appreciated that the operational parameters will vary according to the
type of EES.
17 [0068] It will be appreciated that the EES node 102a can carry
various monitoring and
18 control operations in relation to the EES 101a. In an example aspect,
the EES node 102a
19 also sends status messages and warning messages to other nodes in the
EES management
system 100. In an example aspect, the EES node 102a also receives command
messages
21 and executes operations based on the command messages. In another
example aspect, the
22 EES node 102a also generates and sends command messages to other nodes
in the EES
23 management system 100. Other currently known and future known operations
performed by
24 EES nodes are applicable to the principles described herein. It will be
appreciated that the
other EES nodes 102b, 102n operate in a similar manner to EES node 102a.
26 [0069] The command node 106 receives data from the EES nodes in the
vehicle
27 system or the EES power grid. The command node also provides commands to
the EES
28 nodes. For example, the command messages include one or more of
adjusting current
29 settings, adjusting voltage settings, adjusting charge settings,
adjusting discharge settings,
adjusting load balancing, requesting status data, etc. In an example aspect,
command
31 messages sent by the command node also include one or more of:
activating cooling
32 operations, activating heating operations, activating isolation switches
to isolate or connect
33 EES devices, etc. Other currently known and future known operations
performed by a
34 command node are applicable to the principles described herein.
- 11 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [0070] The command node 106, for example, is also in data
communication (e.g., wired
2 or wireless) with an external data source 107. The external data source
can be another
3 device, another sensor, another ECU, another network, a server system,
etc.
4 [0071] In this EES management system, data travels in both directions
at the same
time across the fiber optic network amongst the nodes.
6 [0072] For example, when the command node 106 sends a command message
to a
7 EES node 102b, the command node duplicates the command message and then
sends one
8 instance of the command message along the fiber optic cable F1 and sends
the other
9 instance of the command message the fiber optic cable F4 at the same
time, or at
approximately the same time. The command message travels along F1; then to the
EES
11 node 101a, via the redundancy module 104a; then travels along F2; then
arrives at the EES
12 node 102b. The command message also travels along F4; then to the EES
node 102n, via
13 the redundancy module 104n; then travels along F3; then arrives at the
EES node 102b. In
14 this way, the redundancy module 104b of the EES node 102b, under nominal
redundancy
operations, receives the command message from both directions at approximately
the same
16 time, or within a predetermined time range considered to be acceptable,
of each other. If
17 one of the fiber optic cables or connections is broken or damaged (e.g.,
F1), then the EES
18 node 102b still receives the command message along another path (e.g.,
F4 and F3) with no
19 loss of data and with no time delay. Similarly, if one of the
intermediate EES nodes is
damaged (e.g., EES node 102a's redundancy module 104a is damaged), then the
EES
21 node 102b still receives the command message along another path (e.g.,
F4 and F3) with no
22 loss of data and with no time delay.
23 [0073] In another example aspect, a message from a given EES node is
transmitted by
24 its redundancy module in both directions at the same time, or
approximately the same time,
under nominal conditions. For example, EES node 102b, via its redundancy
module 104b,
26 transmits a message to the command node 106. The redundancy module 104b
duplicates
27 the message, and then transmits one instance of the message along the
fiber optic cable F2
28 and transmits another instance of the message along the fiber optic
cable F3 at the same
29 time, or approximately at the same time. Under nominal conditions, the
command node 106
receives two instances of the message originating from the EES node 102b, via
the fiber
31 optic cable F1 and the fiber optic cable F4. The message instances from
both directions are
32 received at the command node 106 at approximately the same time, or
within a
33 predetermined time range considered to be acceptable, of each other,
under nominal
34 conditions. However, if a fiber optic cable or connection fails, then
the command node still
receives at least one instance of the message without any loss of data and
without any time
- 12 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 delay. Similarly, if an intermediate node is damaged, then the command
node still receives
2 at least one instance of the message without any loss of data and without
any time delay.
3 [0074] In an example aspect, the redundancy module in the daisy chain
communication
4 ring topology provides 0 microsecond (Is) recovery time, no data delay,
and no data loss
(e.g., 0% data packet loss) in the event of a Network or node connection
failure. The EES
6 management system 100 provides high-availability seamless redundancy.
7 [0075] In another example aspect, each node on the fiber optic network
has at least two
8 optical network ports that are inserted into the network with a ring
topology. In another
9 example aspect, data packets (e.g., messages or portions of messages) are
transmitted by a
sender node in both directions of the ring at the same time, which is also
herein called
11 packet duplication. Intermediate nodes in the ring forward the data
packets in the ring. In
12 another example aspect, the receiver node removes the packets from the
ring. In another
13 example aspect, the sender node removes the packets (e.g., also called
packet filtering).
14 Under nominal conditions (e.g., no errors or failures), the destination
node receives two
copies of the packet and discards the duplicate.
16 [0076] In another example aspect, a cable break or a port failure at
a node is detected,
17 while data still is transmitted with no loss and with no delay in the
EES management system
18 100. In another example aspect, EES nodes emit comm-check or status
packets (e.g.,
19 messages), which include data about the port status; these status
packets are used to
update configuration information and detect broken links.
21 [0077] In another example aspect, the EES nodes and the one or more
command
22 nodes operate using a cut-through mode. For example, a given
intermediate node begins
23 transmitting a pass-through packet even before the whole packet is
received, once it has
24 been detected that destination address is not the given intermediate
node address, therefore
the packet is to be forwarded. In other words, this type of dynamic first-in-
first-out
26 processing, allows data to be more quickly transported through the fiber
optic network.
27 [0078] In another example aspect, the EES nodes and the one or more
command
28 nodes operate using a store-and-forward mode. For example, a given
intermediate node
29 receives and stores the whole packet, defines the destination address,
and then determines
whether to forward the packet or process the packet, or both.
31 [0079] It will be appreciated the nodes in the network can operate
using one or more
32 modes.
33 [0080] It will be appreciated that although three EES nodes 102a,
102b, 102n are
34 shown in FIG. 1A, there may be more or less EES nodes in implementation.
Furthermore,
- 13 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 other types of nodes (e.g., nodes for sensors, nodes for actuator
control, etc.) may be
2 connected to the same fiber optic network for EES management systems.
3 [0081] FIGs. 1B, 1C and 1D show different examples of an EES
management system,
4 which vary based on the one or more types of electric energy source.
[0082] Turning to FIG. 1B, an example embodiment of a battery management
system
6 110 is shown. The battery nodes 112a, 112b, 112n respectively include
battery cell
7 interfaces 113a, 113b, 113n. The battery cell interfaces 112a, 112b, 112n
are respectively
8 connected to the battery cells 111a, 111b, 111n. Each of the battery
nodes include a
9 redundancy module. The battery nodes are arranged in a daisy chain
configuration and are
in communication with a command node 106.
11 [0083] Turning to FIG. 1C, an example embodiment of a fuel cell
management system
12 120 is shown. The system 120 includes a fuel cell node 122, which
includes a fuel cell
13 interface 123, which in turn is connected to a fuel cell stack 121. The
system 120 also
14 includes a fuel supply node 125, which includes a fuel supply interface
126. The fuel supply
interface 126 is connected to the fuel supply (or fuel supplies) system 124.
For example, the
16 fuel supply system 124 includes the valves and pump system that control
the supply of fuel
17 and air to the fuel cell stack 121. The system 120 also includes a
battery node 128. The
18 battery node 128 includes a battery cell interface 129. The battery node
128, via the battery
19 cell interface 129, is connected to the battery cells 127. It will be
appreciated that there may
be multiple fuel cell nodes respectively managing multiple fuel cell stacks.
It will also be
21 appreciated there may be multiple fuel supply nodes respectively
managing multiple fuel
22 supply systems. It will also be appreciated there may be multiple
battery nodes respectively
23 managing multiple sets of battery cells. Each of the nodes in the
systems 120 includes
24 redundancy module.
[0084] Turning to FIG. 1D, an example embodiment of a solar cell management
system
26 130 is shown. The system 130 includes solar cell nodes 132a, 132b, which
respectively
27 include solar cell interfaces 133a, 133b. One or more solar panels 131a
are connected to
28 the solar cell interface 133a, and one or more solar panels 131b are
connected to the solar
29 cell interface 133b. The system 130 further includes a battery node 135
that is connected to
a set of battery cells 134. In particular, the battery node 135 includes a
battery cell interface
31 136 which connects to the battery cells 134. It will be appreciated
there may be multiple
32 battery nodes respectively managing multiple sets of battery cells. The
solar cell nodes, the
33 battery cell nodes, and the command node in the system 130 each include
a redundancy
34 module.
- 14 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [0085] It will be appreciated that the configuration of the EES
management system may
2 vary based on the type of device used to generate the electricity or
store the electricity, or
3 both.
4 [0086] Turning to FIG. 2, an example embodiment is provided that shows
a fiber optic
EES management system in which the redundancy modules have a software Ethernet
6 architecture. For simplicity, two EES nodes 102a, 102b and a command node
106 are
7 shown in a daisy chain ring topology connected via fiber optic cables. It
will be appreciated
8 that in other example embodiment, there may be more EES nodes or more
command nodes,
9 or both. Each of the nodes 102a, 102b, 106 respectively includes
redundancy modules
201a, 201b, 201c.
11 [0087] The redundancy modules in FIG. 2 include a micro controller
unit (MCU) 202, a
12 physical layer transceiver 1 (PHY1) 208, a physical layer transceiver 2
(PHY2) 209, a first
13 transmitter optical sub assembly (TOSA) and receiver optical sub
assembly (ROSA) (also
14 herein called TOSA/ROSA1), and a second TOSA and ROSA (also herein
called
TOSA/ROSA2). In an example aspect, the redundancy module includes a memory
device
16 203 that is in data communication with the MCU 202.
17 [0088] In an example aspect, the TOSA receives electrical signals,
converts electrical
18 signals to optical signals, and transmits the optical signals to the
network. The ROSA
19 receives optical signals from the network, converts optical signals to
electrical signals, and
outputs electrical signals. In another example embodiment, the TOSA and the
ROSA are
21 combined to form a bi-directional optical sub assembly (BOSA).
22 [0089] In an example aspect, PHY (e.g., PHY1 and PHY2 in the
redundancy module)
23 refer to the physical layer transceiver or physical medium, and is also
referred to as a PHY
24 chip. The PHY is an electronic circuit (e.g., an integrated circuit)
that converts MAC layer
data into a format suitable for transport over fiber optics.
26 [0090] The MCU 202 includes an analog to digital converter (ADC) port
204, general
27 purpose input output (GP10) port 205a, a media access control 1 (MAC1)
port 206, and a
28 media access control 2 (MAC2) port 207. The GPIO port 205a sends and
receives digital
29 data to and from the EES interface 103a. The ADC port 204 receives
analog data from the
EES interface and converts the analog data to digital data. Digital data is
sent or received
31 via the MAC1 port or the MAC2 port, or both.
32 [0091] In an example aspect, the MCU reads data about the electric
energy source,
33 checks data against limits, issues warnings, etc.
- 15 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [0092] In an example aspect, MAC1 206 is in data communication with
PHY1 208,
2 PHY1 208 is in data communication with TOSA/ROSA1 210, and TOSA/ROSA1 210
3 connected to a fiber optic cable F1. Data can be transmitted in both
directions along the
4 channel formed by F1, TOSA/ROSA1 210, PHY1 208 and MAC1 206.
[0093] In another example aspect, MAC2 207 is in data communication with
PHY2 209,
6 PHY2 209 is in data communication with TOSA/ROSA2 211, and TOSA/ROSA2 211
is
7 connected to a fiber optic cable F2. Data can be transmitted in both
directions along the
8 channel formed by F2, TOSA/ROSA2 211, PHY2 209 and MAC2 207.
9 [0094] In an example aspect, the data connection between MAC1 and PHY1
uses one
of a media-independent interface (MII), reduced media-independent interface
(RMII), and
11 reduced gigabit media-independent interface (RGMII). It will be
appreciated that other
12 currently known and future known interfaces between a MAC and PHY layer
can be used.
13 In another example aspect, the data connection between PHY1 and
TOSA/ROSA1 use Fast
14 Ethernet over fiber optics according to 100BASE-FX (e.g., 100 Mbps
Ethernet over fiber
optics) or 1000BASE-X (e.g., Gigabit Ethernet over fiber optics). Other types
of currently
16 known and future known Ethernet interfaces over fiber optics can be used
according the
17 principles described herein. These data connections also apply to the
second port formed
18 by TOSA/ROSA2 211, PHY2 209 and MAC2 207.
19 [0095] The redundancy module 201c at the command node 106 has a
similar
architecture. More generally, the MCU in the redundancy module 201c includes a
device
21 interface that is in data communication with the ECU 105, or some other
controller for the
22 overall EES management system.
23 [0096] Turning to FIG. 3, another example of an EES management system
is provided.
24 In particular, the redundancy modules are based on a hardware Ethernet
architecture. For
simplicity, two EES nodes 102a, 102b and a command node 106 are shown in a
daisy chain
26 ring topology connected via fiber optic cables. It will be appreciated
that in other example
27 embodiments, there may be more EES nodes or more command nodes, or both.
The nodes
28 102a, 102b, 106 respectively include redundancy modules 301a, 301b,
301c.
29 [0097] For example, the redundancy module in FIG. 3 includes a MCU
302, a
programmable hardware device 304 and TOSA/ROSA1 306 and TOSA/ROSA2 307. In an
31 example embodiment, the programmable hardware device 304 is a field
programmable gate
32 array (FPGA) device, or is an application-specific integrated circuit
(ASIC) device. The
33 programmable hardware device includes a MAC1 port 310, a MAC2 port 308
and a MAC3
34 port 309. The MAC2 port 308 of the device 304 is in data communication
with
- 16 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 TOSA/ROSA1 306. The MAC3 port 309 of the device 304 is in data
communication with
2 TOSA/ROSA2 307.
3 [0098] In an example aspect, a memory device 305 is in data
communication with the
4 programmable hardware device 304.
[0099] The MCU 302 includes a MAC1 port 311, a GPIO port 313, and an ADC
port
6 312. The MAC1 port 311 of the MCU 302 is in data communication with the
MAC1 port 310
7 of the programmable hardware device 304. The GPIO port 313 is in data
communication
8 with the EES interface 103a. The ADC port 312 is also in data
communication with the EES
9 interface 103a. The ADC port 312 receives analog data from the EES
interface 103a and
converts it to digital data.
11 [00100] In an example aspect, a memory device 303 is in data
communication with the
12 MCU 302.
13 [00101] In an example aspect, the data communication between the MAC1
port 311 of
14 the MCU 302 and the MAC1 port 310 of the programmable hardware device
304 uses MII,
or RMII, or RGMII, or serial gigabit media independent interface (SGMII). In
another
16 example aspect, the data communication between the MAC1 port 311of the
MCU 302 and
17 the MAC1 port 310 of the programmable hardware device 304 uses an
Ethernet interface of
18 100BASE-FX, or 1000BASE-X.
19 [00102] In an example aspect, the data connection between MAC2 308
and
TOSA/ROSA1 306 include 100BASE-FX or 1000BASE-X, or some other Ethernet fiber
optic
21 connection. The same type of data connection is implemented between MAC3
309 and
22 TOSA/ROSA2 307.
23 [00103] In alternative embodiment, each of TOSA/ROSA1 306 and
TOSA/ROSA2 307 is
24 bi-directional (e.g., called a bidirectional optical sub-assembly
(BOSA)). In an alternative
embodiment, each of TOSA/ROSA1 306 and TOSA/ROSA2 307 is a multi-channel
26 TOSA/ROSA device.
27 [00104] In an example aspect, using the hardware Ethernet
implementation allows for
28 fiber optic speed operation in the order of Gigabit per second
bandwidth. In another
29 example aspect, the EES management system in FIG. 3 has lower latencies
and higher
speeds.
31 [00105] Turning to FIG. 4, another example of an EES management
system is provided.
32 In particular, the redundancy modules have a software architecture that
transmits data using
33 a universal asynchronous receiver/transmitter (UART) device, or a
controller area network
34 (CAN) bus, or a serial peripheral interface (SPI) bus, over a fiber
optic cables. For simplicity,
- 17 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 two EES nodes 102a, 102b and a command node 106 are shown in a daisy
chain ring
2 topology connected via fiber optic cables. It will be appreciated that in
other example
3 embodiments, there may be more EES nodes or more command nodes, or both.
The nodes
4 102a, 102b, 102c respectively include redundancy modules 401a, 401b,
401c.
[00106] The redundancy module includes a MCU 402 with two data ports 409
and 410.
6 The data port 409 is in data communication with a transceiver 403, and a
transceiver 403 is
7 in data communication with a fiber optic line TOSA/ROSA1 405. Similarly,
the other data
8 port 402 is in data communication with another transceiver 404, and the
other transceiver
9 404 is in data communication with a fiber optic TOSA/ROSA2 406.
[00107] In an example aspect, the data ports 409 and 410 are UART data
ports and
11 receive and transmit data according to the UART protocol. In another
example aspect, the
12 data ports 409 and 410 are CAN data ports and receive and transmit data
using a CAN bus
13 architecture. In another example aspect, the data ports 409 and 410 are
SPI data ports and
14 receive and transmit data using a SPI protocol.
[00108] The MCU 402 also includes a GPIO port 408 that exchanges data with
the EES
16 interface. The MCU also includes an ADC port 407 to receive analog data
from the EES
17 interface and converts the same to digital data.
18 [00109] In an example embodiment, the transceivers 403 and 404 are
separate from the
19 MCU 402 as shown in FIG. 4. In an alternative embodiment, the MCU 402
has built-in
transceivers 403, 404.
21 [00110] In an example aspect, a memory device 411 is in data
communication with the
22 MCU 402.
23 [00111] In an example aspect, the communication lines between the
transceivers 403,
24 404 and the respective TOSA/ROSA1 and TOSA/ROSA2 405, 406 use RS-485, or
CAN, or
SPI. The TOSA/ROSA 406,406 are connected to the fiber optic cables.
26 [00112] Turning to FIG. 5, example executable instructions for a
command node and
27 other EES nodes in an EES management system for detecting a
communication redundancy
28 error.
29 [00113] At block 501, the command node duplicates a message and
transmits the two
instances of the message in both directions in a fiber optic network.
31 [00114] At block 502, each node (e.g., an EES node) in the fiber
optic network receives
32 the message from a given direction and, at least one of: processes the
message; transmits
33 the message along the same given direction; disregards the message; and
checks to see if it
34 received the same message from an opposite direction of the given
direction (e.g., nominal
- 18 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 condition), or not (e.g., error condition). The handling of the message
depends, for example,
2 on the type of message, whether or not the message is intended for a
given EES node, and
3 whether or not the message is intended for another EES node.
4 [00115] In an example aspect, the message is a comm-check message,
which is a type
of message that triggers a given node to check for communication redundancy.
For
6 example, if the given node detects that the message is a comm-check
message, the given
7 node checks to see if it received the same message from both directions
(e.g., nominal
8 condition), or not (e.g., error condition). If not, then a comm-check
error is detected as per
9 block 503. For example, the EES node detects that it only received one
instance of the
message, and not two instances of the same message.
11 [00116] At block 504, the given node generates and sends alert
message in one
12 direction or both directions in the fiber optic network, the alert
message indicating: its node
13 ID; the direction from which the message was received; and the direction
from which the
14 same message was not received. Other data can be included, such as a
time stamp.
[00117] At block 505, the command node receives one instance of the alert
message, or
16 receives two instances of the alert message from opposite directions.
17 [00118] In an example aspect, by identifying the direction from which
the message was
18 received (e.g., the first direction) and by identifying the direction
from which the message
19 was not received (e.g., the second direction), the command node
identifies which path in the
fiber optic network (e.g., along the first direction) is nominal and which
path (e.g., along the
21 second direction) has a breakage or failure.
22 [00119] In an example aspect, the given node that generates the alert
message,
23 duplicates the alert message and sends two instances of the alert
message in opposite
24 directions. If the command node receives both instances of the alert
messages, then the
command node identifies that the breakage or failure is intermittent or occurs
inconsistently.
26 On the other hand, if the command node receives only once instance of
the alert message
27 from the same path on which the message reached the given node (e.g.,
the first direction),
28 then the command node identifies that the breakage or failure is
definite and static.
29 [00120] In an example embodiment, a comm-check message is a specific
type of
message that tests the communication redundancy of the EES management system.
A
31 command node, for example, sends out a comm-check message based on
certain operating
32 events (e.g., start-up sequence, shut-down sequence, hibernate sequence,
charge
33 sequence, etc.). In another example aspect, a command node sends comm-
check
34 messages periodically. A command node, using its redundancy module,
sends two
- 19 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 instances of the comm-check message in both directions (e.g., via both of
its data ports) at
2 the same time.
3 [00121] In an example embodiment, a comm-check message is addressed to
all nodes
4 in the EES management system. In another example embodiment, a comm-check
message
is addressed to only one or more particular nodes in the EES management
system.
6 [00122] When a comm-check message is received by the given EES node,
it checks to
7 see if two instances of the comm-check message are received from both
directions.
8 [00123] In an example embodiment, the EES node does not check other
messages to
9 determine if a corresponding duplicate has been received. This saves on
processing time
and resources at the given node.
11 [00124] Turning to FIG. 6, another example embodiment of example
executable
12 instructions is provided for processing a comm-check message at a given
node in the EES
13 management system. In an example aspect, these instructions can be
executed by an EES
14 node. In an example aspect, these instructions are executed by a command
node.
[00125] At block 601, the node receives a comm-check message from a first
direction in
16 the fiber optic network. At block 602, the node processes the comm-check
message from
17 the first direction.
18 [00126] At block 603, the node determines: (a) if it received the
same message from a
19 second direction (e.g., nominal condition) within a predetermined or
expected time after
receiving the message from the first direction; (b) if the same message has
not been
21 received from a second direction within a first predetermined or
expected time (e.g., hard
22 error condition) (e.g., hard error condition); or (c) if the same
message was received from a
23 second direction within the first predetermined or expected time, but
beyond a second
24 predetermined or expected time (e.g., soft error condition). It will be
appreciated that the first
predetermined or expected time allows for more time to pass compared to the
second
26 predetermined or expected time.
27 [00127] If the condition (a) is detected, then the node records that
the redundancy
28 operation in the battery management system is nominal (block 604).
29 [00128] If the condition (b) is detected, then the node records a
hard error in the
redundancy operation (block 605). In other words, there is a failure or
breakage in one of
31 the data paths in the fiber optic network in the second direction
towards the node. At block
32 606, the node initiates a process to identify the location of the hard
error. For example, the
33 node transmits (or initiates another node to transmit) an alert message
to some or all the
- 20 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 nodes to send an alert message, and the results of the alert message will
indicate the
2 location of the error.
3 [00129] If the condition (c) is detected, then the node records a soft
error in the
4 redundancy operation (block 607). For example, two instances of the same
message were
received by the node. However, the second instance of the message was received
within
6 the first predetermined or expected time, but beyond a second
predetermined or expected
7 time. This could mean that one or more of the intermediary nodes caused a
delay in
8 transmitting the message to the node. At block 608, the node initiates a
process to identify
9 the location or locations that caused the delay of the second instance of
the message.
[00130] In an example embodiment, the given node does not check for a soft
error.
11 Instead, the given node only checks for a hard error (e.g., condition
(b)).
12 [00131] Turning to FIG. 7, example executable instructions are
provided for transmitting
13 and processing a message in an EES management system. The message, for
example, is a
14 non-comm-check message, and therefore, a given EES node discards the
duplicate instance
of the same non-comm-check message. For example, the non-comm-check message is
a
16 control message, or a status message, or a request for status message.
17 [00132] In an example aspect, the non-comm-check message is addressed
to a single
18 recipient. In an alternative example aspect, the non-comm-check message
is addressed to
19 multiple recipients.
[00133] The EES management system in this example embodiment includes a
21 command node 701, a first EES node 702 and a second EES node 703 that
are connected
22 to each other via a fiber optic network arranged in a daisy chain ring
topology. It will be
23 appreciated that there may be other nodes, and the complexity of the
ring topology can be
24 more complex. However, for the purposes of illustrating the computations
executed at given
battery node and a given command node, a more simplistic ring topology is used
in FIG. 7.
26 [00134] At block 704, the command node duplicates a message and
transmits two
27 instances of the message in both directions at the same time via its
separate data ports. In
28 other words, a first instance of the message is sent to the first EES
node 702 and a second
29 instance of the same message is sent to the second EES node 703.
[00135] At block 705, the first EES node 702 receives an instance of the
message from
31 the first direction. The first EES node then determines if the message
is for this node, or for
32 one or more other nodes, or both (block 706).
33 [00136] If the message is for the first EES node, then the first EES
node determines if
34 the message was previously received from the second direction (block
707). If not, then the
- 21 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 first EES node processes the message (block 708). In other words, the
instance of the
2 message received from the first direction is the first time the message
has been received at
3 the first EES node 702.
4 [00137] Otherwise, if the message was previously received from the
second direction,
then the first EES node 702 discards the duplicate message (block 709).
6 [00138] If the message is for one or more other nodes, then the first
EES node 702
7 transmits the message in the first direction (block 710), so that the
second EES node
8 receives the instance of the message from the first direction.
9 [00139] In an example embodiment, the message is addressed to a single
recipient. If
the message is addressed to a single recipient that is the first EES node 702,
then the block
11 707 is executed, but not block 710. If the message is addressed to a
single recipient that is
12 not the first EES node 702, then the block 710 is executed, but not
block 707.
13 [00140] In an example embodiment, the message is addressed to
multiple recipients. If
14 the message is addressed to multiple recipients, but does not include
the first EES node,
then the block 710 is executed, but not block 707. If the message is addressed
to multiple
16 recipients that includes the first EES node, then blocks 707 and 710 are
executed.
17 [00141] In an example embodiment, the first EES node determines if
the message
18 received from the first direction and the message received from the
second direction
19 occurred within a certain time period from each other (e.g., n seconds).
If a first message
from one of the two directions is received and processed, and the second
message from the
21 other one of the two directions is received after more than n seconds
starting from receipt of
22 the first message, then the second message is considered a new message
and is processed
23 by the first EES node.
24 [00142] In an example embodiment, the first EES node 702 receives the
instance of the
message from the second direction (block 711). For example, in a three node
system, the
26 command nodes sends an instance of the message in the second direction
to the second
27 EES node 703, and the second EES node 703 transmits the instance of the
message in the
28 second direction to the first EES node 702.
29 [00143] At block 712, the first EES node then determines if the
message is for this node,
or for one or more other nodes, or both.
31 [00144] If the message is for the first EES node, then the first EES
node determines if
32 the message was previously received from the first direction (block
713). If not, then the first
33 EES node processes the message (block 714). In other words, the instance
of the message
- 22 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 received from the second direction is the first time the message has been
received at the
2 first EES node 702.
3 [00145] Otherwise, if the message was previously received from the
first direction, then
4 the first EES node 702 discards the duplicate message (block 715).
[00146] If the message is for one or more other nodes, then the first EES
node 702
6 transmits the message in the second direction (block 716), so that the
command node
7 receives the instance of the message from the second direction.
8 [00147] It will be appreciated that the operations of blocks 711 to
716 can be executed in
9 alternative or in addition to the operations of blocks 705 to 710.
[00148] It will be appreciated that the operations executed by the first
EES node 702 are
11 also similarly executed by the second EES node 703. More generally, the
first EES node
12 702 represents a given node in an EES management system.
13 [00149] Turning to FIG. 8, example executable instructions are
provided for transmitting
14 and processing a comm-check message in an EES management system. In this
example
embodiment, the system includes a command node 801, a first EES node 802 and a
second
16 EES node 803 that are connected to each other via a fiber optic network
arranged in a daisy
17 chain ring topology. It will be appreciated that there may be other
nodes, and the complexity
18 of the ring topology can be more complex. However, for the purposes of
illustrating the
19 computations executed at given EES node and a given command node, a more
simplistic
ring topology is used in FIG. 8.
21 [00150] At block 804, the command node duplicates a comm-check
message and
22 transmits two instances of the comm-check message in both directions at
the same time. In
23 other words, a first instance of the comm-check message is sent in a
first direction to the first
24 EES node 802 and a second instance of the same comm-check message is
sent in a
second direction to the second EES node 803.
26 [00151] At block 805, the first EES node 802 receives the first
instance of the comm-
27 check message from a first direction. In particular, a first data port
at the redundancy
28 module of the first EES node receives the first instance of the message
via fiber optic cable
29 that connects between the command node 801 and the first EES node 802.
[00152] At block 806, the redundancy module of the first EES node 802
transmits the
31 first instance of the comm-check message in the first direction. In
other words, the first
32 instance of the comm-check message is transmitted using a second data
port of the
33 redundancy module via fiber optic cable that connects between the first
EES node 802 and
34 the second EES node 803.
- 23 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00153] At block 807, the first EES node 802 determines if the comm-
check message
2 was previously received from the second direction (e.g., via its second
data port). If not, the
3 process continues to block 808. If so, the process continues to block
812.
4 [00154] At block 808, the first EES node 802 processes the comm-check
message
received from the first direction. The first EES node 802 then determines if a
corresponding
6 comm-check message is received from the second direction (e.g., via the
second data port)
7 within a certain time period (block 809). If so, then the first EES node
802 records that the
8 redundancy system is active (block 810). If not, then the first EES node
802 transmits an
9 alert (block 811).
[00155] At block 812, the first EES node 802 determines if the comm-check
message
11 received from the first direction and the comm-check message previously
received from the
12 second direction are within a predetermined or expected time period. For
example, both
13 instances of the comm-check message should be received within a given
time value of each
14 other. If so, then the first EES node 802 records that the redundancy
system is active (block
810). If not, then the first EES node 802 transmits an alert (block 813).
16 [00156] In an example embodiment starting at block 814, the first EES
node 802
17 receives the second instance of the comm-check message from a second
direction. In
18 particular, a second data port at the redundancy module of the first EES
node receives the
19 second instance of the comm-check message via fiber optic cable that
connects between
the second EES node 803 and the first EES node 802.
21 [00157] At block 815, the redundancy module of the first EES node 802
transmits the
22 second instance of the comm-check message in the second direction. In
other words, the
23 second instance of the comm-check message is transmitted using a first
data port of the
24 redundancy module via fiber optic cable that connects between the first
EES node 802 and
the command node 801.
26 [00158] At block 816, the first EES node 802 determines if the comm-
check message
27 was previously received from the first direction (e.g., via its first
data port). If not, the
28 process continues to block 817. If so, the process continues to block
821.
29 [00159] At block 817, the first EES node 802 processes the comm-check
message
received from the second direction. The first EES node 802 then determines if
a
31 corresponding comm-check message is received from the first direction
(e.g., via the first
32 data port) within a certain time period (block 818). If so, then the
first EES node 802 records
33 that the redundancy system is active (block 819). If not, then the first
EES node 802
34 transmits an alert (block 820).
- 24 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00160] At block 821, the first EES node 802 determines if the comm-
check message
2 received from the second direction and the comm-check message previously
received from
3 the first direction are within a predetermined time period. For example,
both instances of the
4 comm-check message should be received within a given time value of each
other. If so,
then the first EES node 802 records that the redundancy system is active
(block 819). If not,
6 then the first EES node 802 transmits an alert (block 822).
7 [00161] It will be appreciated that the operations of blocks 814 to
822 can be executed in
8 alternative or in addition to the operations of blocks 805 to 813. Under
nominal redundancy
9 conditions, the first EES node receives an instance of the comm-check
message from the
first direction and receives an instance of the comm-check message from the
second
11 direction within a predetermined time frame of each other.
12 [00162] It will be appreciated that the operations executed by the
first EES node 802 are
13 also similarly executed by the second EES node 803. More generally, the
first EES node
14 802 represents a given node in an EES management system.
[00163] In the process of FIG. 8, the each EES node transmits an instance
of the comm-
16 check message right away, assuming there is not breakage or failure in
the system. Under
17 nominal conditions, the EES node receives a first instance of a comm-
check check message
18 from a first direction and transmits the first instance of the comm-
check message in the first
19 direction, and receives a second instance of the same comm-check message
from a second
direction and transmits the second instance of the comm-check message in the
second
21 direction.
22 [00164] In an example embodiment, an EES node sends one alert
message. For
23 example, the EES node detect that a comm-check message was received from
only one
24 direction, but it has not received a corresponding comm-check message
from the opposite
direction within a given time period. The alert message, for example, includes
the node ID
26 and, at least one of: (i) the direction from which it received the comm-
check message and (ii)
27 the direction from which it did not receive the corresponding comm-check
message. The
28 alert message also includes, for example, a time stamp. The EES node,
for example, sends
29 the duplicates the one alert message and transmits one instance of the
alert message in one
direction (via one data port) and the other instance of the alert message in
the other direction
31 (via the other data port).
32 [00165] In another example embodiment, an EES node sends two alert
messages. For
33 example, the EES node detect that a comm-check message was received from
only one
34 direction, but it has not receive a corresponding comm-check message
from the opposite
direction within a given time period. The EES node then transmits a first
alert message that
- 25 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 includes the node ID and, at least one of: (i) the direction from which
it received the comm-
2 check message and (ii) the direction from which it did not receive the
corresponding comm-
3 check message. The first alert message also includes, for example, a
first time stamp. If the
4 EES node later receives the corresponding comm-check message from the
opposite
direction but, after the given time period, then the EES node transmits a
second alert
6 message that includes the node ID and the direction from which it later
received the
7 corresponding comm-check message. The second alert message also includes,
for
8 example, a second time stamp. In this way, a command node can compare the
first time
9 stamp and the second time stamp to quantify the delay, as well as the
direction, of the
comm-check communication received at the given EES node. The command node uses
this
11 data to characterize the error in the redundancy operations of the EES
management system.
12 Furthermore, where a two-alert message system is expected, if the EES
node only sends
13 one alert message, then the command node can determine that there is a
hard failure or
14 break in the EES management system. Whereas, if the EES node sends a
first alert
message and then later sends a second alert message, then the command node can
16 determine that there is a soft failure in the EES management system. In
an example
17 embodiment, the EES node sends the first alert message in both
directions and sends the
18 second alert message in both directions.
19 [00166] Turning to FIG. 9, example executable instructions are
provided for a command
node to execute comm-check process. At block 901, the command node sends two
21 instances of a comm-check message in opposite directions. For example, a
first data packet
22 that includes a comm-check message is sent via a first data port of the
command node, and
23 a second data packet that includes the same comm-check message is sent
via a second
24 data port of the command node. In an example embodiment, the first data
packet and the
second data packet are transmitted at the same time in opposite directions.
26 [00167] At block 902, after some time after sending the data packets,
the command
27 node then checks if it has (i) received the first data packet via the
second data port and (ii)
28 received the second data packet via the first data port within a
predetermined time period.
29 [00168] If so, then the command node records that the redundancy
operation is nominal
(block 903). If not, then the command node records an error in the redundancy
operation
31 (block 904).
32 [00169] In this way, the command node can ascertain whether or not
there is an error in
33 the redundancy of the EES management system, even if it does not receive
an alert
34 message from one or more EES nodes. It will also be appreciated that the
command node
uses these operations to very quickly determine whether or not the redundancy
operation is
- 26 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 nominal, as each node in the system should, under nominal conditions,
very quickly pass
2 along the comm-check message in the daisy chain ring.
3 [00170] It will be appreciated that the command node can additionally
receive alert
4 messages from one or more EES nodes, which provides additional data to
characterize the
error in the redundancy of the EES management system.
6 [00171] It will be appreciated that other nodes in addition or in
alternative to the
7 command node can send a comm-check message.
8 [00172] In an example aspect, the EES management system has different
types of
9 messages that are transmitted and processed differently from each other.
For example, in
addition to the comm-check message described above, other types of messages
include
11 control messages, status messages, and emergency messages. It will be
appreciated that
12 other types of messages can be transmitted in the EES management system
described
13 herein.
14 [00173] Control messages, for example, are in most cases generated by
a command
node. A control message can have a single destination address or multiple
destination
16 addresses. For example, a command message includes one or more EES node
17 configuration parameters addressed to multiple EES nodes, so that upon
receipt, the
18 multiple EES nodes take action to adjust to the one or more
configuration parameters. In
19 another example, a command message is addressed to one EES node, so that
upon receipt,
the one EES node executes the control command in the control message. In an
example
21 aspect, the one or more EES nodes receiving and executing the command
message provide
22 a reply message back to the command node. In another example embodiment,
an EES
23 node generate a control message for one or more other EES nodes, and
sends a copy of the
24 message to the command node.
[00174] Status messages, for example, are generated in most cases by an EES
node.
26 In an example aspect, a status message reports one or more current
parameters associated
27 with the battery cells (e.g., state of charge, state of health, voltage,
current, temperature,
28 number of discharges, number of charges, etc.), or the EES node itself,
or both. Status
29 message can have a single destination address or multiple destination
addresses. For
example, in case of a single command node in the EES management system, a
status
31 message include the address of only the one command node. In another
example
32 embodiment that includes multiple command nodes in the EES management
system, a
33 status message includes the multiple destination addresses corresponding
to the multiple
34 command nodes.
- 27 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00175] In another example aspect, an EES node sends a status message
that includes
2 the destination addresses of one or more other EES nodes. In another
example aspect, an
3 EES node sends a status message that includes the destination addresses
of all the other
4 EES nodes in the EES management network (e.g., a type of broadcast
message).
[00176] In an example aspect, a status message is sent by an EES node in
response to
6 a command node's control message. For example, an EES node receives a
control
7 message, which triggers the EES node to generate and send a status
message. The status
8 message, for example, is generated and sent on-demand, also called a pull
message flow.
9 [00177] In another example aspect, a status message is sent by an EES
node based on
a pre-defined time base (e.g., a schedule). For example, on a periodic basis,
an EES node
11 sends a status message. This is a form of a push message flow.
12 [00178] In another example aspect, a status message is sent by an EES
node in
13 response to detecting an event or a condition. For example, when a
parameter has
14 exceeded a threshold, or a rate of change has exceeded a threshold, then
the EES nodes
sends a status message. This is another form of a push message flow.
16 [00179] In an example aspect, any message type (e.g., control
message, status
17 message, emergency message, comm-check message, etc.) is duplicated by
the originating
18 node and two instances of the same message are transmitted in both
directions in the fiber
19 optic network. In a further example aspect, if a given recipient node
does not receive the
two instances of the message, then an error is detected in the redundancy
operation of the
21 EES management system.
22 [00180] Emergency messages, for example, are sent by any of the nodes
in the EES
23 management system (e.g., a command node, a EES node, etc.).
24 [00181] Emergency messages are transmitted as top priority to provide
fast reaction time
to avoid or limit a potentially dangerous scenario. In an example aspect, a
message
26 prioritization architecture is provided that establishes the emergency
message with higher
27 priority assigned to it compared with other control and status messages.
Emergency
28 messages, for example, have a single destination address, multiple
destination addresses,
29 or a broadcast address. This is to allow fast reaction of physically
coupled EES nodes to
perform needed action as fast as possible without time delay. For example, an
EES node
31 generates and transmits an emergency message to one or more other EES
nodes and to the
32 command node. In this way, the one or more EES nodes can execute an
action based on
33 the emergency message, even before receiving a confirmation message or a
directing
34 message from a command node.
- 28 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00182] By contrast, it is recognized that in existing control
systems, emergency
2 messages are typically sent by a command node. In these configurations,
an emergency
3 event detected by an EES node or some other client nodes typically needs
to transmit a
4 message to a command node, then the affected EES nodes need to wait for
the command
node to generate and transmit an emergency message to them before taking
emergency
6 action. This centralized command incurs delay.
7 [00183] Turning to FIG. 10, example executable instructions are
provided for a node in
8 the EES management system to process an emergency message. The redundancy
module
9 in a node includes a queue of messages to transmit. The queue can include
no messages,
one message, or several messages at a given time. The executable instructions
shown in
11 FIG. 10 can be executed by an EES node or a command node, or both.
12 [00184] In FIG. 10, an initial queue of messages 1001 is shown, which
is stored in
13 memory on the given node. A condition (e.g., blocks 1002 or 1003) is
detected that leads to
14 transmitting an emergency message.
[00185] For example, at block 1002, the node detects a local emergency
event and
16 generates an emergency message. For example, an EES node detects a
voltage level that
17 exceeds an upper or a lower threshold. In another example, an EES node
detects a current
18 level that exceeds an upper or a lower threshold. In another example, an
EES node detects
19 a temperature level that exceeds an upper or a lower threshold. In
another example, an
EES node detects a pressure level that exceeds an upper or a lower threshold.
In another
21 example, an EES node detects a chemical level that exceeds an upper or a
lower threshold.
22 In another example, an EES node detects a pressure level that exceeds an
upper or a lower
23 threshold. In another example, an EES node detects an impact level or
force level that
24 exceeds an upper threshold. In another example, a given node (e.g., EES
node or a
command node) detects an electrical error (e.g., in the redundancy module, in
the EES
26 interface, in a sensor, in a power supply, etc.). In another example, a
given node (e.g., EES
27 node or a command node) detects a software error. It will be appreciated
that different types
28 of conditions can trigger a node to locally generate an emergency
message.
29 [00186] In another example, at block 1003, the given node receives an
emergency
message via the fiber optic network. For example, another node (e.g., an EES
node or a
31 command node) has generated the emergency message and has transmitted
the
32 emergency message to the given node.
33 [00187] At block 1004, either as a result of locally generating an
emergency message or
34 a result of receiving an emergency message, the node then moves the
emergency message
1005 to the front of its queue or pauses the transmission of the existing
queue.
- 29 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00188] An example of a modified queue 1006 is shown that includes the
emergency
2 message 1005 at the front of the queue. The node then transmits the
emergency message
3 at block 1007. In this way, a node expedites the transmission of
emergency messages. In
4 an example aspect, across an EES management system network of multiple
nodes, each
node expedites an emergency message. This results in the emergency message
being
6 transmitted to one or more intended recipient nodes in less time than
other messages
7 currently queued for transmission.
8 [00189] In an example aspect, the above process for transmitting an
emergency
9 message at a given node also applied to processing messages. For example,
a queue of
messages is to be processed by an EES node or a command node. For example, at
an
11 EES node, messages are processed at the EES interface. In another
example, at a
12 command node, messages are processed at the ECU or BCU. An emergency
message that
13 is locally generated or received via the fiber optic network, however,
is positioned at the front
14 of the queue for immediate processing.
[00190] In another example aspect, the emergency message can also be
expedited
16 using communication hardware that establish a separate data channel
amongst EES nodes.
17 [00191] Turning to FIGs. 11 to 13B, different example embodiments of
EES
18 management systems are provided that include two or more daisy chain
rings. The daisy
19 chain rings are connected to each other using a quad-port redundancy
module. Two or
more daisy chain rings help to limit the effect of a fault or breakage. For
example, the fault
21 or a breakage in one daisy chain ring would have less or no effect on
the nodes in another
22 daisy chain ring.
23 [00192] It will be appreciated that the features described with
respect to an EES
24 management system that has one daisy chain ring also apply to an EES
management
system that includes two or more daisy chain rings.
26 [00193] Turning to FIG. 11, an example embodiment of an EES
management system is
27 shown that includes two daisy chain rings 1109 and 1110 that are
connected together using
28 a quad-port redundancy module 1108. One ring 1109 includes the EES nodes
1104a,
29 1103a, 1102a that are respectively connected to EES devices 1104b,
1103b, 1102b.
Examples of EES devices include battery packs, fuel cell stacks, solar panels,
electric
31 generators, etc. The ring 1109 also include a command node 1101.
32 [00194] Another ring 1110 includes the EES nodes 1105a, 1106a, 1107a
that are
33 respectively connected to EES devices 1105b, 1106b, 1107b.
- 30 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00195] The command node 1101 transmits messages and receives messages
to the
2 nodes in the ring 1109 and to the nodes in the ring 1110. Messages
between a given node
3 in the ring 1110 and the command node 1101 are transmitted via the quad-
port redundancy
4 module 1108. Other messages from the ring 1109 may also be transmitted
via the quad-port
redundancy module 1108 to a given node in the ring 1110, and back to a given
node in the
6 ring 1109.
7 [00196] The nodes and the quad-port redundancy module are connected to
each other
8 using fiber optic cables. The quad-port redundancy module includes four
data ports that
9 respectively connect to four fiber optic cables. Two data ports connect
to one ring 1109 and
another two data ports connect to another ring 1110. In an example aspect,
there are two
11 quad-port redundancy modules that connects two rings.
12 [00197] In an example aspect, a quad-port redundancy module receives
a message via
13 one of its four data ports. The quad-port redundancy module then
replicates the message
14 and transmits the replicated instances of the message via its three
other data ports. In an
example aspect, the instances of the message are transmitted at the same time.
16 [00198] In an example aspect, a quad-port redundancy module receives
a message via
17 one of its four data ports. The quad-port redundancy module then
replicates the message
18 and transmits the replicated instances of the message via two other data
ports at the same
19 time. In an example aspect, the one data port that received the message
is connected to
one ring, and the two other data ports that transmit the messages are
connected to another
21 ring.
22 [00199] In an example aspect, a quad-port redundancy module receives
a message via
23 one of its four data ports. The quad-port redundancy module then
replicates the message
24 and transmits the replicated instances of the message via at least one
of the other data
ports. For example, the data port that received the message and the other data
port that
26 transmits the message are in the same ring. In another example, the data
port that received
27 the message and the other data port that transmits the message are in
different rings.
28 [00200] FIG. 12 shows another example embodiment of a battery
management system
29 that includes two rings 1109 and 1110 that are connected by two quad-
port redundancy
modules 1108 and 1202. In an example aspect, if one quad-port redundancy
module fails,
31 then the two rings 1109 and 1110 remain in data communication with each
other using the
32 working quad-port redundancy module.
33 [00201] In another example aspect, each of the rings 1109, 1110
respectively include
34 their own command nodes 1101, 1201. In an example aspect, if one of the
command nodes
fails or breaks, then the working command node can transmit and receive
messages to
- 31 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 control the battery nodes in both of rings 1109, 1110. In an example
aspect, one of the
2 command nodes (e.g., command node 1101) is a primary command node while
the other
3 command node (e.g., command node 1201) is a back-up command node. In the
event of
4 failure of the primary command node, the back-up command node continues
to make
decisions and send commands to the EES nodes. In an example aspect, the back-
up
6 command node stores a duplicate of all the actions executed and data
gathered by the
7 primary command node, so that transfer of command is seamless.
8 [00202] Turning to FIG. 13A, another example embodiment of an EES
management
9 system is shown that includes multiple EES node rings 1301a, 1301b, 1301n
that are each
connected to two separate command rings 1302, 1303. In particular, each EES
node ring is
11 connected to the command ring 1302 using its own quad-port redundancy
module 1304, and
12 each EES node ring is also connected to the other command ring 1303
using another quad-
13 port redundancy module 1304.
14 [00203] Each EES node ring includes one or more EES nodes 1306, and
each EES
node controls and interacts with EES devices 1307. Examples of EES devices
include
16 battery packs, fuel cell stacks, solar panels, electric generators, etc.
Each EES node ring
17 also includes two quad-port redundancy modules 1104. For example, in the
EES node ring
18 1301a, a first quad-port redundancy module has two data ports that
connect to the EES
19 node ring 1301a, and the other two data ports connect to the command
ring 1302. A second
quad-port redundancy module 1304 has two data ports that connect to the EES
node ring
21 1301a, and the other two data ports connect to the command ring 1303.
22 [00204] It will be appreciated that although three EES node rings are
shown, there may
23 be more rings or there may be less rings.
24 [00205] Each command ring 1302, 1303 includes one or more command
nodes 1305. In
an example embodiment, each command ring includes two or more command nodes
1305.
26 Each command ring also includes a quad-port redundancy module
corresponding to each
27 EES node ring with which it interacts. A command ring can also include
one or more EES
28 nodes 1306 that control EES devices 1107.
29 [00206] Messages from a command node in one command ring (e.g.,
command ring
1302) are sent to one or more EES node rings 1301a, 1301b, 1301n, which in
turn also
31 transmit the messages to the other command ring (e.g., command ring
1303). In this way,
32 command nodes on the other command ring (e.g., command ring 1303) also
receive a copy
33 of the message originating from the command ring 1302.
34 [00207] The network architecture in FIG. 13A provides multiple
redundant fiber optic
paths to route data between nodes. In other words, even if an entire command
ring (e.g.,
- 32 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 command ring 1302) is disabled or fails, the other command ring (e.g.,
command ring 1303)
2 remains operable to continue to seamlessly command the EES nodes 1306 in
the EES node
3 rings. Furthermore, even if an entire EES node ring fails, the other EES
nodes in the EES
4 management system are able to operate in a seamless manner.
[00208] FIG. 13B shows another example embodiment of an EES management
system
6 that includes one command ring 1303 that is connected to multiple EES
node rings 1301a,
7 1301b, 1301n via respective multiple quad-port redundancy module 1304.
8 [00209] Turning to FIG. 14, an example embodiment of a quad-port
redundancy module
9 1400 is shown using a software Ethernet implementation. It includes four
TOSA/ROSA data
ports 1401, 1402, 1415, 1416 that respectively connect to four fiber optic
cables.
11 [00210] TOSA/ROSA data ports 1401 and 1402 respectively connect to
PHYs 1403 and
12 1404, and PHYs 1403 and 1404 respectively connect to MAC ports 1406 and
1407 of a first
13 MCU 1405.
14 [00211] The first MCU 1405 includes MAC ports 1406 and 1407, and a
high-speed bus
port 1408.
16 [00212] A second MCU 1409 includes MAC ports 1411 and 1412, and a
high-speed bus
17 port 1410. The first MCU 1405 and the second MCU 1409 are in data
communication with
18 each other using high-speed bus ports 1408 and 1410.
19 [00213] MACs 1411 and 1412 of the second MCU 1409 are respectively
connected to
PHYs 1413 and 1414, and the PHYs 1413 and 1414 are respectively connected to
21 TOSA/ROSA data ports 1415 and 1416.
22 [00214] In an example aspect, one or both MCUs 1405, 1409 are in data
communication
23 with one or more memory devices 1417, 1418.
24 [00215] In an example aspect, connections between a PHY and a
TOSA/ROSA uses
100BASE-FX, or 1000BASE-X, or some other type of Ethernet interface over
optical fiber.
26 [00216] In an example aspect, connections between a PHY and a MAC
include MII,
27 RMII, RGMII, SGMII or some other interface.
28 [00217] In another example aspect, the high-speed bus between the
MCUs includes an
29 external bus, an Ethernet connection, a peripheral component
interconnect express (PCIE)
connection, or a universal serial bus (USB) connection, etc.
31 [00218] Turning to FIG. 15, an example embodiment of a quad-port
redundancy module
32 1501 is shown having a hardware Ethernet implementation. The module 1501
includes four
- 33 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 TOSA/ROSA data ports 1502, 1503, 1509, 1510 that respectively connect to
four fiber optic
2 cables.
3 [00219] TOSA/ROSA data ports 1502, 1503 are respectively connected to
MAC ports
4 1505, 1506 of the chip 1504. The chip 1504 is a FPGA device or an ASIC
device. It
includes the MAC ports 1505, 1506, 1507, 1508. The MAC ports 1507, 1508 are
6 respectively connected to TOSA/ROSA data ports 1509, 1510.
7 [00220] In an example aspect, chip 1504 is in data communication with
a memory device
8 1511.
9 [00221] In an example aspect, connections between a MAC port and a
TOSA/ROSA
uses 100BASE-FX, or 1000BASE-X, or some other type of Ethernet interface over
optical
11 fiber.
12 [00222] Turning to FIG. 16, another example embodiment of a
redundancy module 1603
13 is shown in context of an EES node 1601. The redundancy module 1603 has
a multichannel
14 fiber optic software Ethernet configuration that includes two MCUs 1604,
1605.
[00223] In another example embodiment, a command node includes a similar
16 multichannel Ethernet redundancy module 1603 that interacts with an ECU
or a BCU.
17 [00224] The EES node 1601 includes an EES interface 1602 that
connects to an EES
18 device, and a redundancy module 1603 that includes two TOSA/ROSA data
ports 1618,
19 1619.
[00225] The first MCU 1604 includes an ADC 1608, a GPIO 1609, and two MACs
1606,
21 1607. The second MCU 1605 includes an ADC 1612, a GPIO 1613, and two
MACs 1614,
22 1615. The ADC 1608 and GPIO 1609 of the first MCU, and the ADC 1612 and
GPIO 16130f
23 the second MCU, connect to the EES interface 1602.
24 [00226] MACs 1606 and 1607 of the first MCU respectively connect to
PHYs 1610 and
1611. PHYs 1610 and 1611 respectively connect to TOSA/ROSA data ports 1618 and
26 1619, and exchange data there between via optical signals at a first
optical wavelength.
27 [00227] MACs 1614 and 1615 of the second MCU respectively connect to
PHYs 1616
28 and 1617. PHYs 1616 and 1617 respectively connect to TOSA/ROSA data
ports 1618 and
29 1619, and exchange data therebetween via optical signals at a second
optical wavelength
that is different from the first optical wavelength.
31 [00228] In other words, data from both MCUs is transmitted via the
two data ports 1618,
32 1619, and data received via the data ports 1618, 1619 can be processed
by one or both of
33 the MCUs.
- 34 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00229] In an example embodiment, the first optical wavelength is 1310
nanometers and
2 the second optical wavelength is 850 nanometers. It will be appreciated
that other
3 wavelengths suitable for fiber optics can be used.
4 [00230] Each of the TOSA/ROSA devices 1618, 1619 include a built-in
optical filter that
can filter out different optical wavelengths. In an example aspect, the
optical filter system in
6 a ROSA filters out the first optical wavelength and the second optical
wavelength. In another
7 example aspect, the TOSA transmits a first set of data at the first
optical wavelength and
8 transmits a second set of data at the second optical wavelength via the
fiber optic cables.
9 More generally, each TOSA/ROSA device can receive data at different
optical wavelengths
and transmit data at different optical wavelengths. In an example aspect, the
transmission
11 or reception of data at different wavelengths occurs at the same time.
12 [00231] Similarly, the PHY devices 1610, 1611 of the first MCU 1604
send data over the
13 first optical wavelength to a given TOSA/ROSA device, and the PHY
devices 1616, 1617 of
14 the second MCU 16105 send data over the second optical wavelength to a
given
TOSA/ROSA device.
16 [00232] In an example aspect, a memory device 1620 is in data
communication with the
17 first MCU 1604, and a memory device 1621 is in data communication with
the second MCU
18 1605.
19 [00233] In an example aspect, the first MCU 1604 and the second MCU
1605 process
the same data in parallel to each other. In other words, when data is received
at a data port
21 1618 or 1619, the received data is sent to both MCUs 1604, 1605. Both
MCUs process the
22 data in the same way as each other and transmits the same commands or
data to the EES
23 interface 1602. Duplicate commands or data are deleted at the EES
interface. Similarly, the
24 same data from the EES interface is sent in two instances at the same
time; one instance of
data from the EES interface is sent to the first MCU and another instance of
the same data is
26 sent to the second MCU. In another example aspect, data to be
transmitted over the fiber
27 optic network is sent twice coming from a first MCU and from the second
MCU. In this way,
28 there is complete redundancy of the MCU within the redundancy node. If
one of the MCUs
29 fails, or if internal connections to one of the MCU fails, then the
other MCU seamlessly takes
over with zero packet data loss and without any delay. Furthermore, if one of
the data
31 channels (e.g., one of the optical wavelengths) fail in the redundant
network of the EES
32 management system, all nodes in the EES management system are able to
continue to
33 transmit, receive and process data with no data packet loss and with no
delay using the
34 other data channel (e.g., the other optical wavelength).
- 35 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00234] In an example aspect of processing the same data in parallel,
the first set of data
2 received by or transmitted by the redundancy node on the first optical
wavelength is the
3 same as the second set of data received by or transmitted by the
redundancy node on the
4 second optical wavelength. The first set of data and the second set of
data, which are
identical, are transmitted at the same time over the fiber optic cables
respectively using the
6 first and the second optical wavelengths.
7 [00235] In another example embodiment, the first MCU 1604 and the
second MCU 1605
8 process different data in parallel. In other words, the first data set is
different from the
9 second data set. This allows for faster data processing.
[00236] In another example embodiment, a quad-port redundancy module
includes a
11 similar multichannel Ethernet redundancy module 1603. However, for a
quad-port
12 redundancy module, it includes four MCUs, where two MCUs are dedicated
to a first optical
13 wavelength and two other MCUs are dedicated a second optical wavelength.
The quad-port
14 redundancy module also includes four TOSA/ROSA data ports that each
include an optical
filter.
16 [00237] FIG. 17 shows a schematic flow of a symmetric redundancy
module that
17 processes data using a first Ethernet channel and a second Ethernet
channel.
18 [00238] Blocks 1701, 1702 and 1703 show that certain messages (e.g.,
status
19 messages) are received, processed and outputted via the first Ethernet
channel using the
first MCU 1604. Blocks 1704, 1705, 1706 shows that certain other messages
(e.g., an
21 emergency message or a control message) are received, processed, and
outputted via the
22 second Ethernet channel using the second MCU 1605.
23 [00239] FIG. 18 shows a flow diagram of example executable
instructions for a
24 symmetric redundancy module, such as the one shown in FIG. 16.
[00240] At block 1801, the redundancy module detects a local event or
condition. At
26 block 1802, the redundancy module determines if the event or condition
should result in an
27 emergency message. If not, then the redundancy module generates a
message in Ethernet
28 form (block 1803) and transmits the message over the first Ethernet
channel (block 1804). If
29 the event or condition should result in an emergency message, then at
block 1805 the
redundancy module generates an emergency message in Ethernet from and
transmits the
31 emergency message over the second Ethernet channel (block 1806).
32 [00241] Turning to FIG. 19, another example embodiment of a
redundancy module 1903
33 is provided that includes components for multi-channel asymmetric
software Ethernet
34 architecture.
- 36 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00242] This redundancy module 1903 also includes two channels
corresponding to two
2 different optical wavelengths. For example, one channel operates at a
first optical
3 wavelength and another channel operates at a second optical wavelength.
Data can be
4 transmitted on both channels at the same time in a fiber optic cable.
[00243] An EES node 1901 includes an EES interface 1902 and a redundancy
module
6 1903. The redundancy module includes a MCU 1904, two transceivers 1913,
1914, two
7 PHY devices 1911, 1912, and two TOSA/ROSA devices 1915, 1916 that are the
two data
8 ports for EES node.
9 [00244] The TOSA/ROSA devices each include, for example, an optical
filter that filters
the first optical wavelength and the second optical wavelength.
11 [00245] In an example aspect, one of the optical wavelengths is 1310
nanometers and
12 the other one of the optical wavelengths is 850 nanometers. In another
example aspect, the
13 transceivers 1913, 1914 operate with a signal filtered at 1310
nanometers and the PHY
14 devices 1911, 1912 operate with a signal filtered at 850 nanometers. It
will be appreciated
that different wavelengths can be used for the optical channels.
16 [00246] In an example aspect the transceivers 1913 and 1914 are
respectively
17 connected to TOSA/ROSA devices 1915 and 1916 via UART TX/RX data links.
The
18 transceivers 1913 and 1914 are also respectively connected to UART ports
1909 and 1910
19 via TX/RX data links.
[00247] In another example aspect, the PHY devices 1911 and 1912 are
respectively
21 connected to TOSA/ROSA devices 1915 and 1916 via 100BASE-FX or other
optical
22 Ethernet interface data links. The PHY devices 1911 and 1912 are also
respectively
23 connected to MAC ports 1907 and 1908 via MII or RMII or other Ethernet
interface data
24 links.
[00248] The MCU 1904 includes the MAC ports 1907, 1908 and the UART ports
1909,
26 1910. The MAC ports receive and transmit Ethernet data on one optical
wavelength. The
27 UART ports receive and transmits UART data on another optical
wavelength.
28 [00249] The MCU 1904 also includes an ADC port 1905 and GPIO port
1906 to interact
29 with the EES interface 1902.
[00250] In another example aspect, the MCU 1904 is in data communication
with a
31 memory device 1917.
32 [00251] In an example aspect, the optical channel with the UART ports
1909, 1910 is
33 used for one set of messages, while the other optical channel with the
MAC ports 1907,
34 1908 is used for another set of messages. In another example aspect, the
optical channel
- 37 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 with the UART ports 1909, 1910 is used for emergency messages and control
messages. In
2 another example aspect, the other optical channel with the MAC ports
1907, 1908 is used for
3 status messages.
4 [00252] In an example aspect, instead of using the UART interface and
protocol, an SPI
interface and protocol are used. In another example aspect, instead of using
the UART
6 interface and protocol, a CAN interface and protocol are used.
7 [00253] UART is less complex than Ethernet and provides low latency.
The optical
8 channel that uses the UART ports, for example, is used for sending small
packets of data
9 quickly.
[00254] Ethernet provides storage at the nodes and is better suited for
transmitting large-
11 sized data packets very quickly. Ethernet is also better suited for
sending higher volume of
12 data more quickly.
13 [00255] In an example aspect, data packets that are sized at or
larger than a certain
14 threshold are sent via the Ethernet optical channel. Data packets that
are sized smaller than
the certain threshold are sent via the UART optical channel. In an example
embodiment,
16 certain threshold size is 80 bytes. In other example embodiments, other
threshold sizes are
17 used.
18 [00256] FIG. 20 shows a schematic flow of an asymmetric redundancy
module that
19 processes data using an Ethernet channel and a UART channel. In an
alternative
embodiment, a SPI channel or a CAN bus channel replaces the UART channel.
21 [00257] Blocks 2001, 2002 and 2003 show that certain messages (e.g.,
status
22 messages) are received, processed, and outputted via the Ethernet
channel. Blocks 2004,
23 2005, 2006 shows that certain other messages (e.g., an emergency message
or a control
24 message) are received, processed, and outputted via the UART channel.
[00258] FIG. 21 shows a flow diagram of example executable instructions for
an
26 asymmetric redundancy module, such as the one shown in FIG. 19.
27 [00259] At block 2101, the redundancy module detects a local event or
condition. At
28 block 2102, the redundancy module determines if the event or condition
should result in an
29 emergency message. If not, then the redundancy module generates a
message in Ethernet
form (block 2103) and transmits the message over the Ethernet channel (block
2104). If the
31 event or condition should result in an emergency message, then at block
2105 the
32 redundancy module generates an emergency message in UART from and
transmits the
33 emergency message over the UART channel (block 2106).
- 38 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00260] FIG. 22 shows an example embodiment of a vehicle 2200 that
includes an EES
2 management system 2201. For example, multiple sets of energy cells (e.g.,
battery cells,
3 fuel cells, etc.) are included in the vehicle and that are part of the
EES management system
4 2201. The EES management system 2201 provides electric power to different
subsystems
in the vehicle, including, for example, one or more electric motors for the
primary drive
6 system 2202 and the electric power system 2203. Although the vehicle 2200
is shown as a
7 car, it will be appreciated that other types of vehicles (e.g., trucks,
construction vehicles,
8 buses, transport vehicles, aircraft, drones, boats, submarines, trains,
etc.) can include the
9 EES management system 2201.
[00261] FIG. 23 shows an example embodiment of an EES management system
2301
11 providing electric power to one or more electric loads 2302. For
example, the EES
12 management system 2301 is part of a power supply unit that includes one
or more types of
13 electric energy sources. For example, the EES management system 2301
includes: battery
14 cells, fuel cells, solar cells, a generator, or a combination thereof.
Each set of energy
sources (e.g., energy cells) or, in another example aspect, each instance of
energy source,
16 is connected to a respective EES node. This power supply unit can be
setup, for example,
17 in remote locations. In another example, this power supply unit can also
be as a localized
18 power bank, such as for a building or equipment, or both. In another
example, this power
19 supply unit and the one or more loads 2302 are part of a machine. In
another example, an
additional electric source 2303 (e.g., additional electric generator,
additional wind turbine,
21 additional solar cells, etc.) supplies electric power to the mobile
power supply unit's EES
22 management system 2301. In an example embodiment, the power supply unit
is mobile so
23 that it can be transported. In another example embodiment, the power
supply unit is
24 stationary.
[00262] FIG. 24 shows an example embodiment of multiple instances of EES
26 management systems 2301a, 2301b, 2301n as power supply units that are
connected to an
27 electric distribution grid 2401. One or more additional electric sources
2303 and one or
28 more electric loads 2302 are connected to the electric distribution grid
2401. In an example
29 embodiment, each of the power supply units include an EES management
system that are in
data communication with each other using fiber optic cables F2402 to form a
large daisy
31 chain network. In other words, within each EES management systems 2301a,
2301b, 2301n
32 can include their own local daisy chain network loop(s), and these local
daisy chain network
33 loops are connected together in a larger using the fiber optic cables
F2402. In an example
34 embodiment, the system of components in FIG. 24 is called a microgrid.
[00263] In an example aspect, the devices and systems described herein
provide
36 redundant communications in battery management systems so that no single
point failure
- 39 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 can cause potential loss of life or damage, such in vehicle applications.
In another example
2 aspect, the devices and systems described herein take a different
approach to safety,
3 changing away from "fail-safe shutdown state". Instead, the devices and
operations
4 described herein facilitate a "fail-safe operation state" that would keep
communication alive
to support transition to a safe state.
6 [00264] Below are general example embodiments and example aspects.
7 [00265] EXAMPLE EMBODIMENT A: In an example embodiment, a redundant
fiber
8 optic EES management system includes: a command node and EES nodes
connected in a
9 daisy chain ring with fiber optic cables; the command node and the EES
nodes each
comprising a redundancy module; the redundancy module comprising a processor
and two
11 optical data ports; and the command node configured to duplicate a
message and transmit a
12 first and a second instance of the message in different directions at
the same time using two
13 optical data ports in a redundancy module of the command node.
14 [00266] In an example aspect, each of the EES nodes are configured to
duplicate a
given message and transmit a first and a second instance of the given message
in different
16 directions at the same time using their respective two optical data
ports in their respective
17 redundancy module.
18 [00267] In an example aspect, the message from the command node is
addressed to at
19 least one specific EES node and, under nominal redundancy operation, the
at least one
specific EES node receives the first instance of the message on one of the two
optical data
21 ports and receives the second instance of the message on the other one
of the two optical
22 data ports within an expected amount of time after receiving the first
instance of the
23 message.
24 [00268] In an example aspect, the message is addressed to at least
one specific EES
node, and wherein the daisy chain ring comprises a break and the at least one
specific EES
26 node receives only the first instance of the message via one of the two
optical data ports
27 with zero data packet loss. In an example aspect, the break comprises a
breakage in one of
28 the fiber optic cables or a failure in one of the EES nodes.
29 [00269] In an example aspect, the message is addressed to at least
one specific EES
node, and wherein the daisy chain ring comprises a break and the at least one
specific EES
31 node receives only the first instance of the message via one of the two
optical data ports
32 with zero second delay. In an example aspect, the break comprises a
breakage in one of
33 the fiber optic cables or a failure in one of the EES nodes.
- 40 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 [00270] In an example aspect, the redundancy module of a given EES
node is
2 configured to receive the first instance of the message via one of the
two optical data ports
3 on the given EES node and, after detecting that the second instance of
the message has not
4 been received via the other one of the two optical data ports on the
given EES node within a
predetermined time, the redundancy module of the given EES node is configured
to
6 generate an alert message. In an example aspect, the redundancy module of
the given EES
7 node duplicates the alert message and transmits a first instance of the
alert message via
8 one of the two optical data ports on the given EES node and, at the same
time, transmits a
9 second instance of the alert message via the other one of the two optical
data ports on the
given EES node.
11 [00271] In an example aspect, the processor of the redundancy module
is a micro
12 controller unit (MCU) that executes software to implement redundancy
over Ethernet. In an
13 example aspect, the MCU comprises two MAC ports and the redundancy
module further
14 comprise two PHY devices, and the two PHY devices respectively data link
the two MAC
ports to the two optical data ports.
16 [00272] In an example aspect, the processor of the redundancy module
is a field
17 programmable gate array (FPGA) hardware device that implements
redundancy over
18 Ethernet, and the FPGA hardware device is data linked to the two optical
data ports.
19 [00273] In an example aspect, the processor of the redundancy module
is an
application-specific integrated circuit (ASIC) hardware device that implements
redundancy
21 over Ethernet, and the ASIC hardware device is data linked to the two
optical data ports.
22 [00274] In an example aspect, the redundant fiber optic EES
management system is
23 integrated in a vehicle and the command node further comprises an
electronic control unit
24 (ECU) that is data linked to the redundancy module of the command node.
[00275] In an example aspect, the redundant fiber optic EES management
system is
26 integrated in an energy storage unit and the command node further
comprises a battery
27 control unit (BCU) that is data linked to the redundancy module of the
command node.
28 [00276] In an example aspect, the fiber optic cables comprise glass
optical fibers. In an
29 example aspect, the fiber optic cables comprise plastic optical fibers.
[00277] EXAMPLE EMBODIMENT B: In another example embodiment, a vehicle
31 includes: an electric drive powered by multiple sets of energy cells;
multiple energy nodes
32 respectively connected to the multiple sets of energy cells; the
multiple energy nodes
33 arranged in a daisy chain ring and connected to each other with fiber
optic cables; each of
34 the multiple energy nodes comprising a redundancy module, and the
redundancy module
- 41 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 comprises a processor, a first and a second optical data port; the
processor configured to
2 execute instructions to duplicate a message and transmit a first instance
of the message via
3 the first optical data port and at the same time transmit a second
instance of the same
4 message via the second optical data port.
[00278] In an example aspect, each of the multiple energy nodes further
comprises an
6 energy cell interface that connects the redundancy module to a
corresponding one of the
7 multiple sets of energy cells.
8 [00279] In an example aspect, the multiple sets of energy cells
comprise fuel cells. In an
9 example aspect, the multiple sets of energy cells comprise battery cells.
[00280] EXAMPLE EMBODIMENT C: In another example embodiment, a vehicle
11 includes: an electric drive powered by multiple sets of energy cells;
multiple energy nodes
12 respectively connected to the multiple sets of energy cells; the
multiple energy nodes
13 arranged in a daisy chain ring and connected to each other with fiber
optic cables; each of
14 the multiple energy nodes comprising a redundancy module, and the
redundancy module
comprises a processor, a first and a second optical data port; the processor
configured to
16 detect receipt of a first instance of a message via the first optical
data port and to detect
17 whether or not a second instance of the same message is received via the
second optical
18 data port within a predetermined time after the receipt of the first
instance of the message;
19 and the processor further configured to generate an alert message after
detecting that the
second instance of the same message has not been received via the second
optical data
21 port within the predetermined time.
22 [00281] In an example aspect, the processor duplicates the alert
message and sends a
23 first instance of the alert message via the first optical port and at
the same time sends a
24 second instance of the alert message via the second optical port.
[00282] In an example aspect, each of the multiple energy nodes further
comprises an
26 energy cell interface that connects the redundancy module to a
corresponding one of the
27 multiple sets of energy cells.
28 [00283] In an example aspect, the multiple sets of energy cells
comprise fuel cells. In an
29 example aspect, the multiple sets of energy cells comprise battery
cells.
[00284] EXAMPLE EMBODIMENT D: In another example embodiment, an EES node in
31 an EES management system is provided. The EES node includes: an EES
interface
32 connected to a redundancy module, the EES interface configured to
connect with an EES
33 device; the redundancy module comprising a first and a second optical
data ports that are
34 respectively connected to a first and a second PHY devices, and the
first and the second
- 42 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 PHY devices are respectively connected to a first and second media access
control (MAC)
2 ports; the redundancy module further comprising a micro controller unit
(MCU) that
3 comprises the first and the second MAC ports and a data port that is data
linked to the EES
4 interface.
[00285] In an example aspect, Ethernet interface over fiber optic data
links respectively
6 connect the first and the second PHY devices to the first and the second
optical data ports.
7 [00286] In an example aspect, under nominal redundancy operation, a
first instance of a
8 message is received at the first optical data port and, within an
expected time after receiving
9 the first instance of the message, a second instance of the same message
is received at the
second optical data port.
11 [00287] In an example aspect, the redundancy module discards the
second instance of
12 the same message.
13 [00288] In an example aspect, wherein the redundancy module processes
the first
14 instance of the message before receiving the second instance of the same
message.
[00289] In an example aspect, a first instance of a message is received at
the first optical
16 data port and, after detecting that a second instance of the same
message has not been
17 received at the second optical data port within an expected time after
receiving the first
18 instance of the message, the redundancy module generates and transmits
an alert
19 message. In an example aspect, the redundancy module duplicates the
alert message and
transmits a first instance of the alert message via the first optical data
port and at the same
21 time transmits a second instance of the alert message via the second
optical data port.
22 [00290] In an example aspect, the data port of the MCU comprises: a
general purpose
23 input output port that sends data to and receives data from the EES
interface; and an analog
24 to digital converter port that receives analog data from the EES
interface.
[00291] In an example aspect, the EES device comprises one or more a
battery cell
26 stack, a fuel cell stack, a solar cell system, and a fuel supply system.
27 [00292] EXAMPLE EMBODIMENT E: In another example embodiment, an EES
node in
28 an EES management system is provided, and the EES node includes: an EES
interface
29 connected to a redundancy module, the EES interface configured to
connect with an EES
device; the redundancy module comprising a first and a second optical data
ports that are
31 respectively connected to a first and second media access control (MAC)
ports of a chip
32 device, the chip device further comprising a third MAC port; the
redundancy module further
33 comprising a micro controller unit (MCU) that comprises a MAC port, the
MAC port of the
- 43 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 MCU data linked to the third MAC port of the chip device, and the MCU
further comprising a
2 data port that is data linked to the EES interface.
3 [00293] In an example aspect, Ethernet interface over fiber optic data
links respectively
4 connect the first and the second MAC ports to the first and the second
optical data ports.
[00294] In an example aspect, under nominal redundancy operation, a first
instance of a
6 message is received at the first optical data port and, within a
predetermined time after
7 receiving the first instance of the message, a second instance of the
same message is
8 received at the second optical data port.
9 [00295] In an example aspect, the redundancy module discards the
second instance of
the same message.
11 [00296] In an example aspect, the redundancy module processes the
first instance of the
12 message before receiving the second instance of the same message.
13 [00297] In an example aspect, a first instance of a message is
received at the first optical
14 data port and, after detecting that a second instance of the same
message has not been
received at the second optical data port within a predetermined time after
receiving the first
16 instance of the message, the redundancy module generates and transmits
an alert
17 message. In an example aspect, the redundancy module duplicates the
alert message and
18 transmits a first instance of the alert message via the first optical
data port and at the same
19 time transmits a second instance of the alert message via the second
optical data port.
[00298] In an example aspect, the data port of the MCU comprises: a general
purpose
21 input output port that sends data to and receives data from the EES
interface; and an analog
22 to digital converter port that receives analog data from the EES
interface.
23 [00299] In an example aspect, the chip device is a field programmable
gate array
24 (FPGA) device. In an example aspect, the chip device is an application-
specific integrated
circuit (ASIC) device.
26 [00300] In an example aspect, the EES device comprises one or more a
battery cell
27 stack, a fuel cell stack, a solar cell system, and a fuel supply system.
28 [00301] EXAMPLE EMBODIMENT F: In an example embodiment, an EES node
in an
29 EES management system is provided, and the EES node includes: an EES
interface
connected to a redundancy module, the EES interface configured to connect with
an EES
31 device; the redundancy module comprising a first and a second optical
data ports that are
32 respectively connected to a first and a second transceiver devices, and
the first and the
33 second transceiver devices are respectively connected to a first and a
second data port on a
34 micro controller unit (MCU), wherein the first and the second data ports
are one of a UART
- 44 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 interface, a CAN bus interface and an SPI interface; and the MCU further
a general purpose
2 input output data port and an analog-to-digital converter port that are
both data linked to the
3 EES interface.
4 [00302] EXAMPLE EMBODIMENT G: In an example embodiment, an EES
management
system includes: at least two daisy chain rings formed by multiple nodes that
are
6 interconnected using fiber optic cable, and the multiple nodes comprise
one or more EES
7 nodes and one or more command nodes; and a quad-port redundancy module
that
8 interconnects the two daisy chain rings, the quad-port redundancy module
comprising four
9 optical data ports and a processor, and two of the four optical data
ports are connected to
one of the two daisy chain rings and other two of the four optical data ports
are connected to
11 the other one of the two daisy chain rings.
12 [00303] In an example aspect, after receiving a message in one of the
four optical data
13 ports, the quad-port redundancy module duplicates the message and
transmits one or more
14 instances of the message respectively via a different one, two or three
of the four optical
data ports.
16 [00304] In an example aspect, each of the one or more EES nodes
comprises a
17 redundancy module, and the redundancy module comprises a first and a
second optical data
18 port and a processor; and, under nominal redundancy operation, the
redundancy module
19 receives a first instance of a message via the first optical data port
and, within an expected
amount of time after receiving the first instance of the message, receives a
second instance
21 of the same message via the second optical data port.
22 [00305] In an example aspect, each of the one or more command nodes
comprises a
23 redundancy module, and the redundancy module comprises a first and a
second optical data
24 port; and the redundancy module duplicates a message and transmits a
first instance of the
message via the first optical data port and at the same time transmits a
second instance of
26 the same message via the second optical data port.
27 [00306] In an example aspect, the quad-port redundancy module
comprises a chip
28 device that comprises four media access control (MAC) ports that
respectively connect to
29 the four optical data ports.
[00307] In an example aspect, the chip device is a field programmable gate
array
31 (FPGA) device. In an example aspect, the chip device is an application-
specific integrated
32 circuit (ASIC) device.
33 [00308] In an example aspect, the quad-port redundancy module
comprises a first
34 microcontroller unit (MCU) and a second MCU; the first MCU comprising a
first and a second
- 45 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 media access control (MAC) ports, the first and the second MAC ports
connected to a first
2 and a second PHY devices, and the first and the second PHY devices
connected to a first
3 and a second optical data ports; the second MCU comprising a third and a
fourth MAC ports,
4 the third and the fourth MAC ports connected to a third and a fourth PHY
devices, and the
third and the fourth PHY devices connected to a third and a fourth optical
data ports; and the
6 first MCU further comprising a first data port that connects to a second
data port of the
7 second MCU.
8 [00309] It will be appreciated that any module or component
exemplified herein that
9 executes instructions may include or otherwise have access to non-
transitory computer
readable media such as storage media, computer storage media, or data storage
devices
11 (removable and/or non-removable) such as, for example, memory chips,
magnetic disks,
12 optical disks. Computer storage media may include volatile and non-
volatile, removable and
13 non-removable media implemented in any method or technology for storage
of information,
14 such as computer readable instructions, code, processor executable
instructions, data
structures, program modules, or other data. Examples of computer storage media
include
16 random access memory (RAM), dynamic random access memory (DRAM), static
random
17 access memory (SRAM), read-only memory (ROM), solid-state ROM,
electrically erasable
18 programmable read-only memory (EEPROM), flash memory or other memory
technology, or
19 any other medium which can be used to store the desired information and
which can be
accessed by an application, module, or both. Any such computer storage media
may be
21 part of the servers or computing devices or nodes, or accessible or
connectable thereto.
22 Any application or module herein described may be implemented using
computer
23 readable/executable instructions that may be stored or otherwise held by
such computer
24 readable media.
[00310] It will be appreciated that different features of the example
embodiments of the
26 system and methods, as described herein, may be combined with each other
in different
27 ways. In other words, different devices, modules, operations,
functionality, and components
28 may be used together according to other example embodiments, although
not specifically
29 stated.
[00311] The steps or operations in the flow diagrams described herein are
just for
31 example. There may be many variations to these steps or operations
according to the
32 principles described herein. For instance, the steps may be performed in
a differing order, or
33 steps may be added, deleted, or modified.
34 [00312] It will also be appreciated that the examples and
corresponding system
diagrams used herein are for illustrative purposes only. Different
configurations and
- 46 -
Date Recue/Date Received 2022-02-07
Rendered by ePCT style sheet on 28 Sep 2021 at 15:44:46 CEST
NAC13
1 terminology can be used without departing from the principles
expressed herein. For
2 instance, components and modules can be added, deleted, modified, or
arranged with
3 differing connections without departing from these principles.
4 [00313] While certain example implementations of the disclosed
technology have been
described in connection with what is presently considered to be the most
practical and
6 various implementations, it is to be understood that the disclosed
technology is not to be
7 limited to the disclosed example implementations, but on the
contrary, is intended to cover
8 various modifications and equivalent arrangements included within
the scope of the claims
9 appended hereto.
- 47 -
Date Recue/Date Received 2022-02-07
