WO2024103334A1

WO2024103334A1 - Method and apparatus for can id distribution

Info

Publication number: WO2024103334A1
Application number: PCT/CN2022/132516
Authority: WO
Inventors: Rengui LUO; Yimiao ZHAO; Ling Yang
Original assignee: Analog Devices International Unlimited Company
Priority date: 2022-11-17
Filing date: 2022-11-17
Publication date: 2024-05-23

Abstract

Example implementations include a method, apparatus and computer-readable medium of network identification (ID) distribution by a host device in a network, comprising sending a host ID on a communication bus. The implementations further include receiving a device ID from a first node in a plurality of nodes on the communication bus. Additionally, the implementations further include distributing a first unique network ID value to the first node in the plurality of nodes on the communication bus. Additionally, the implementations further include repeating the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remaining node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value.

Description

METHOD AND APPARATUS FOR CAN ID DISTRIBUTION

BACKGROUND

Technical Field

The described aspects relate to bus networking architectures, and specifically to controller area network (CAN) identification (ID) distribution.

Introduction

Networking architectures have grown increasingly complex and have been designed for use in a wide variety of communications environments. Demand continues to rise among the subscriber base of end users, however, for network access across diverse network environments. In particular, configuring suitable network architecture for vehicular environments (e.g., automobiles, electric vehicles, airplanes, trains, boats, etc. ) presents unique difficulties. Vehicles can be mobile across a large geographical area, can travel at variable speeds, can have internal networks related to the vehicle itself, and can include more than one end user at a time. Providing the ability to conduct transactions in vehicular network environments in an optimized manner and providing a secure and flexible communication framework for various agents conducting the transactions present significant challenges to system designers, automobile manufacturers and the like. Networking architectures are also used in energy storage systems where a number of batteries are coupled together and the voltage and current of each battery cell are managed by one or more processors.

Electric vehicles have unique demands in that the battery power for the vehicle needs to be monitored and determined regularly, as problems with battery power availability may result stranded vehicles.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

An example aspect includes a method of network identification (ID) distribution by a host device in a network, comprising sending a host ID on a communication bus. The method further includes receiving a device ID from a first node in a plurality of nodes on the communication bus. Additionally, the method further includes distributing a first unique network ID value to the first node in the plurality of nodes on the communication bus. Additionally, the method further includes repeating the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remaining node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value.

Another example aspect includes an apparatus for network identification (ID) distribution by a host device in a network, comprising a memory and a processor communicatively coupled with the memory. The processor is configured to send a host ID on a communication bus. The processor is further configured to receive a device ID from a first node in a plurality of nodes on the communication bus. Additionally, the processor further configured to distribute a first unique network ID value to the first node in the plurality of nodes on the communication bus. Additionally, the processor further configured to repeat the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remaining node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value.

Another example aspect includes an apparatus for network identification (ID) distribution by a host device in a network, comprising means for sending a host ID on a communication bus. The apparatus further includes means for receiving a device ID from a first node in a plurality of nodes on the communication bus. Additionally, the apparatus further includes means for distributing a first unique network ID value to the first node in the plurality of nodes on the communication bus. Additionally, the apparatus further includes means for repeating the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remaining node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value.

Another example aspect includes a computer-readable medium having instructions stored thereon of network identification (ID) distribution by a host device in a network, wherein the instructions are executable by a processor to send a host ID on a communication bus. The instructions are further executable to receive a device ID from a first node in a plurality of nodes on the communication bus. Additionally, the instructions are further executable to distribute a first unique network ID value to the first node in the plurality of nodes on the communication bus. Additionally, the instructions are further executable to repeat the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remaining node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value.

An example aspect includes a method of network identification (ID) distribution by a slave device of a plurality of slave devices in a network, comprising receiving a first message including a host ID and a generic ID value on a communication bus, wherein the generic ID value is associated with the slave device. The method further includes sending a device ID on the communication bus. Additionally, the method further includes receiving a unique network ID value on the communication bus.

Another example aspect includes an apparatus for network identification (ID) distribution by a slave device of a plurality of slave devices in a network, comprising a state machine. The state machine may also be embodied with a processor and a memory if desired. The state machine is configured to receive a first message including a host ID and a generic ID value on a communication bus, wherein the generic ID value is associated with the slave device. The state machine is further configured to send a device ID on the communication bus. Additionally, the state machine may be further configured to receive a unique network ID value on the communication bus.

Another example aspect includes an apparatus for network identification (ID) distribution by a slave device of a plurality of slave devices in a network, comprising means for receiving a first message including a host ID and a generic ID value on a communication bus, wherein the generic ID value is associated with the slave device. The apparatus further includes means for sending a device ID on the communication bus. Additionally, the apparatus further includes means for receiving a unique network ID value on the communication bus.

Another example aspect includes a computer-readable medium having instructions stored thereon of network identification (ID) distribution by a slave device of a plurality of slave devices in a network, wherein the instructions are executable by a processor to receive a first message including a host ID and a generic ID value on a communication bus, wherein the generic ID value is associated with the slave device. The instructions are further executable to send a device ID on the communication bus. Additionally, the instructions are further executable to receive a unique network ID value on the communication bus.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed aspects will hereinafter be described in conjunction with the appended drawings, provided to illustrate and not to limit the disclosed aspects, wherein like designations denote like elements, wherein dashed lines may indicate optional elements, and in which:

FIG. 1 illustrates a bus architecture in accordance with an aspect of the present disclosure;

FIG. 2 illustrates a device coupled to the bus architecture in accordance with an aspect of the present disclosure;

FIG. 3 is a communications flow diagram in accordance with an aspect of the present disclosure;

FIG. 4 is a block diagram of an example of a computer device having components configured to perform a method of network identification (ID) distribution by a host device in a network;

FIG. 5 is a flowchart of an example of a method of network identification (ID) distribution by a host device in a network;

FIG. 6 is a flowchart of additional aspects of the method of FIG. 5;

FIG. 7 is a flowchart of additional aspects of the method of FIG. 5;

FIG. 8 is a flowchart of additional aspects of the method of FIG. 5;

FIG. 9 is a flowchart of additional aspects of the method of FIG. 5;

FIG. 10 is a block diagram of an example of a computer device having components configured to perform a method of network identification (ID) distribution by a slave device of a plurality of slave devices in a network;

FIG. 11 is a flowchart of an example of a method of network identification (ID) distribution by a slave device of a plurality of slave devices in a network;

FIG. 12 is a flowchart of additional aspects of the method of FIG. 11; and

FIG. 13 is a flowchart of additional aspects of the method of FIG. 11.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect (s) may be practiced without these specific details.

FIG. 1 illustrates a bus architecture in accordance with an aspect of the present disclosure.

An electric vehicle, or other network, may include a bus architecture 100, which may comprise a host 102 which has memory 103, a bus 104 (or network) , and one or more devices 106-112. A larger or smaller number of devices (also known as “nodes” ) 106-112 may be included in bus architecture 100 without departing from the scope of the present disclosure. Host 102 may be described as an apparatus, device, processor, or other network machine as part of the present disclosure.

In an aspect of the present disclosure, bus architecture 100 may be a Controller Area Network (CAN) . CAN networks are used in battery management systems, such as in automotive electric vehicles or in energy storage systems. Host 102 may be a processor or microcontroller, that communicates with various other devices through bus 104. In CAN networks, device 106, device 108, device 110, and device 112 may be battery packs. Device 106, device 108, device 110, and device 112 may be described as an apparatus, device, sensor, or other network machine as part of the present disclosure.

To use bus 104 as a common communications pathway, each device 106-112 connected to the bus 104 may have a unique identification (ID) number.

FIG. 2 illustrates a device coupled to the bus architecture in accordance with an aspect of the present disclosure.

FIG. 2 illustrates a device 106 coupled to bus 104. Although referred to as device 106, the device shown in FIG. 2 could be any device coupled to the bus 104 without departing from the scope of the present disclosure. Within device 106, a microcontroller unit (MCU) 200 is coupled to the bus 104, and an optional battery pack monitor 202 is coupled to MCU 200. Also coupled to MCU 200 are one or more battery cell monitors, which may include an analog front end (AFE) and/or cell monitor unit (CMU) 204, AFE/CMU 206, AFE/CMU 208, and batteries 210 are coupled in series to produce a voltage from device 106.

In an aspect of the present disclosure, host 102 may assign an ID number (or value) to each device 106 (e.g., devices 106-112) coupled to bus 104. When there are multiple devices coupled to bus 104, host 102 can control the assignment of ID number values to each device 106-112. In such an aspect, MCU 200, battery pack monitor 202, or other portions of device 106 may not contain non-volatile memory (NVM) storing the unique ID number for device 106, which may reduce costs and complexity for each device 106 coupled to the bus 104. Further, MCU 200 may be implemented as a state machine, e.g., an integrated circuit, rather than a processor, as host 102 may control the communications on bus 104. Processing power, non-volatile memory (NVM) , and/or other circuitry in MCU 200 may not be necessary, or may be reduced in nature, in accordance with an aspect of the present disclosure. Since host 102 is performing assignment of the network ID numbers, devices 106-112 can be reduced in complexity and may have reduced costs.

FIG. 3 is a communications flow diagram in accordance with an aspect of the present disclosure.

Flow 300 illustrates a communications flow between host 102 and devices 106-112 on bus 104. Each connection, or “node” to bus 104 has a logical number assigned to that connection. In an aspect of the present disclosure, bus 104 is a CAN bus, and host 102 is assigned to logical Node 0 on bus 104.

Host 102 may be a processor or other microcontroller that initiates and receives electrical signals ( “messages” ) over bus 104 to monitor the status of each of the devices 106-112 on the bus 104. However, to manage the electrical signals on bus 104, each device 106-112 on bus 104 may also be assigned a logical number as a node on bus 104. These nodes or logical number assignments may be referred to as node 1, node 2, etc., and may be referred to as “nodes 1-n” to denote “n” number of nodes on the bus 104. These nodes are given specific identifiers in the present disclosure.

Host 102 may be assigned to CAN node 0 and has a bus ID (also referred to as a CAN ID herein) of a specific value. For example, and not by way of limitation, host 102 may be assigned a bus ID of “XX” , although any device ID can be used without departing from the scope of the present disclosure.

Each of devices 106-112 may have a common or generic network ID as a default prior to bus 104 initialization. As such, the generic network ID for each device 106-112 may be referred to as “YY” herein. The network ID for each device 106-112 for a particular bus 104 may be assigned by host 102 as described herein.

During communication on the bus 104, an identifier, e.g., the device ID of the initiator (sender) of the recipient of the message may be referred to as the “data” of the message, and the intended recipient may be referred to as the “frame” of the message being sent.

In message 302, host 102 sends the host device ID (XX) , which is the CAN bus ID or CAN ID, to the devices 106-112 on bus 104. The data (XX) is sent to a frame ID of “YY” which each device 106-112 on bus 104 has as a generic frame ID. In some aspects, the CAN bus ID for host 102 will not be changed during operation of the bus architecture 100.

Although each device 106-112 will receive the host ID in operation 304, since the frame ID (the generic target or addressed bus node) is the same for each device 106-112, only one device 106-112 will be able to control the bus 104 to return a message on bus 104. Once one of the devices 106-112 acquires control over bus 104, e.g., the first device 106-112 to respond to host 102, the other devices on bus 104 will not be allowed to access the bus 104, e.g., those devices will have their bus 104 transmission communications “disabled” . The disabled devices on bus 104 can still receive messages from host 102 or other devices 106-112 on bus 104, but the disabled devices are in “listen” mode, which means the disabled devices 106-112 can still respond to a message with frame = YY (as a device ID) .

Whichever device 106-112 acquires control over bus 104, which will be referred to as “node X” , in message 306 node X will send a device ID to host 102 on bus 104. The device ID for the device 106-112 (node X) can be any unique identifier for that device.

In an aspect of the present disclosure, the device ID for a given device 106-112 may be a serial number of the device 106-112, e.g., a printed circuit board ID. Such a device ID may be sent in a CAN bus message schema in a CAN frame as an 11-bit identifier. The 11-bit identifier can be set by default or by host 102 assignment.

In an aspect of the present disclosure, the device ID for a given device 106-112 may be an extended ID (EID) of the device. The EID, in a CAN bus standard message schema, is the ID in the CAN extended message frame as a 29-bit identifier, which includes the 11-bit base identifier described above, and 18-bit extended identifier. The 29-bit identifier can be generated from the unique ID of an integrated circuit or other part on device 106-112.

In operation 308, the device 106-112 that acquired bus 104 (at node X) changes its device ID to a unique ID, as opposed to the “YY” identifier used to acquire the initial host ID. In an aspect of the present disclosure, node X may change the device ID to the EID of that device, although any unique device ID value, such as a unique part number, may be used without departing from the scope of the present disclosure.

In operation 310, host 102 receives the device ID from node X, which may be the EID of whichever device 106-112 is at node X over bus 104. Host 102 then configures (assigns) a network ID for node X, and in operation 312, sends this network ID to node X. Operation 312 may use an extended message frame on bus 104 to send the network ID back to node X. For ease of understanding, network IDs may be referred to as “Zn” where n is the number of the node on bus 104. In operation 312, network ID would be “Z1” as this is the first network ID assigned by host 102.

In operation 314, the device 106-112 at node X receives the network ID (Z1) from host 102 on bus 104. Upon receipt, operation 314 changes the device ID (e.g., the EID) to the network ID Z1.

Operation 316 starts the confirmation process for host 102 and node X. In operation 316, host 102 requests data from device 106-112 at node x by sending a frame ID of Z1 to bus 104. Only the device 106-112 at node X has that bus 104 address, so only that device will respond to host 102. If the operations 308-316 have gone correctly for node X, node X will receive the data request in operation 318 and will respond in operation 320 to host 102, which confirms that the device 106-112 at node X has completed the network ID assignment.

If one or more of the operations 308-314 have not been performed correctly, when host 102 attempts to confirm assignment of the network ID in operation 316, host 102 will not receive a response from node X in operation 320. This may result in a resetting of the device 106-112 at node X to the “YY” bus ID and that particular device may be assigned a new network ID later in the process.

If host 102 receives the confirmation message sent in operation 320, host 102 maps node X (and the device 106-112 at node X) to the ID sent to node X in operation 322. This mapping informs host 102 of the device 106-112 that is present at the bus 104 node assigned by host 102. The mapped network ID may be stored in memory 103 for use by host 102 on bus 104.

Operations

324 and 326 show a repetition of steps 302-320 for the additional devices 106-112 that are coupled to bus 104. Each device 106-112 will sequentially acquire the bus, send their device IDs to host 102, and go through the steps to have a network ID assigned by host 102.

Operation 328 illustrates host 102 sending the “generic” YY network ID message on bus 104, and each of the devices 106-112 (that have all been assigned nodes and network IDs) receiving this message at operation 330. Since all of the devices 106-112 have been assigned new network IDs by host 102, none of the devices 106-112 will respond. Either no response will occur in operation 332, or a timeout for response on bus 104 will occur, and operation 334 will indicate to host 102 that all network IDs have been distributed to the devices 106-112 on bus 104.

As shown in FIG. 3, host 102 distributes network IDs to device 106, device 108, device 110, and device 112, and stores the distributed network IDs for bus 104 communication purposes.

FIG. 4 is a block diagram of an example of a computer device having components configured to perform a method of network identification (ID) distribution by a host device in a network, and FIG. 5 is a flowchart of an example of a method of a method of network identification (ID) distribution by a host device in a network.

Referring to FIG. 4 and FIG. 5, in operation, host 102 device in a bus architecture 100 (or other network) may perform a method 500 of network identification (ID) distribution such as via execution of by host 102, processor 105 or memory 103.

At block 502, the method 500 includes sending a host ID on a communication bus. For example, in an aspect, host 102, memory 103, processor 105, communication component 115, and/or sending component 420 may be configured to or may comprise means for sending a host ID on a communication bus.

For example, the sending at block 502 may include sending electrical signals from host 102 to devices 106-112 on bus 104 to begin assignment of network IDs.

Further, for example, the sending at block 502 may be performed by host 102 to inform devices 106-112 of the host 102 network ID.

At block 504, the method 500 includes receiving a device ID from a first node in a plurality of nodes on the communication bus. For example, in an aspect, host 102, memory 103, processor 105, communication component 115, and/or receiving component 425 may be configured to or may comprise means for receiving a device ID from a first node in a plurality of nodes on the communication bus.

For example, the receiving at block 504 may include receiving electrical signals from one of devices 106-112 on bus 104 at host 102.

Further, for example, the receiving at block 504 may be performed to let host 102 know that one of devices 106-112 is able to communicate on bus 104.

At block 506, the method 500 includes distributing a first unique network ID value to the first node in the plurality of nodes on the communication bus. For example, in an aspect, host 102, memory 103, processor 105, communication component 115, and/or distributing component 430 may be configured to or may comprise means for distributing a first unique network ID value to the first node in the plurality of nodes on the communication bus.

For example, the distributing at block 506 may include determining a unique network ID at host 102 and assigning this to the responding node on bus 104.

Further, for example, the distributing at block 506 may be performed to begin communication with one of devices 106-112.

At block 508, the method 500 includes repeating the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remaining node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value. For example, in an aspect, host 102, memory 103, processor 105, communication component 115, and/or repeating component 435 may be configured to or may comprise means for repeating the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remaining node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value.

For example, the repeating at block 508 may include assigning unique network IDs to each of devices 106-112 on bus 104.

In an alternative or additional aspect, the network is a controller area network (CAN) .

In an alternative or additional aspect, the device ID is based on an extended ID (EID) .

FIG. 6 is a flowchart of additional aspects of the method of FIG. 5.

Referring to FIG. 6, in an alternative or additional aspect, at block 602, the sending at block 502 of the host ID comprises sending a message addressed to a generic device ID, wherein the generic device ID is common to each node in the plurality of nodes

FIG. 7 is a flowchart of additional aspects of the method of FIG. 5.

Referring to FIG. 7, in an alternative or additional aspect, at block 702, the method 500 may further include receiving a confirmation of receipt of the first unique device ID value and each respective unique network ID value from each node in the plurality of nodes.

FIG. 8 is a flowchart of additional aspects of the method of FIG. 5.

Referring to FIG. 8, in an alternative or additional aspect, at block 802, the method 500 may further include assigning the first unique network ID value as a new device ID value for the first node based on the EID.

FIG. 9 is a flowchart of additional aspects of the method of FIG. 5.

Referring to FIG. 9, in an alternative or additional aspect, at block 902, the method 500 may further include determining that each node in the plurality of nodes has been assigned the respective unique device ID value.

In this optional aspect, at block 904, the determining at block 902 that each node in the plurality of nodes has been assigned the respective unique device ID value comprises receiving a null response from each node in the plurality of nodes.

For example, either no response will be received, or a determined amount of time will transpire before a response is received at host 102, indicating that no other devices 106-112 have the original or generic device ID.

FIG. 10 is a block diagram of an example of a computer device having components configured to perform a method of network identification (ID) distribution by a slave device of a plurality of slave devices in a network, and FIG. 11 is a flowchart of an example of a method of a method of network identification (ID) distribution by a slave device of a plurality of slave devices in a network.

Referring to FIG. 10 and FIG. 11, in operation, device 106-112, such as a slave device in a network, may perform a method 1100 of network identification (ID) distribution such as via execution by device 106-112.

At block 1102, the method 1100 includes receiving a first message including a host ID and a generic ID value on a communication bus, wherein the generic ID value is associated with the slave device. For example, in an aspect, device 106-112, state machine 107, (which may be embodied as an optional memory 111 and processor 113) , communication component 116, and/or receiving component 1020 may be configured to or may comprise means for receiving a first message including a host ID and a generic ID value on a communication bus, wherein the generic ID value is associated with the slave device.

For example, the receiving at block 1102 may include receiving an electrical signal indicating the generic ID from host 102.

Further, for example, the receiving at block 1102 may be performed by device 106-112 and allow one of devices 106-112 to acquire control over bus 104 for response to host 102.

At block 1104, the method 1100 includes sending a device ID on the communication bus. For example, in an aspect, device 106-112, state machine 107, (which may be embodied as an optional memory 111 and processor 113) , communication component 116, and/or sending component 1025 may be configured to or may comprise means for sending a device ID on the communication bus.

For example, the sending at block 1104 may include sending an electrical signal indicating the EID of that device 106-112 to host 102.

At block 1106, the method 1100 includes receiving a unique network ID value on the communication bus. For example, in an aspect, device 106-112, state machine 107, (which may be embodied as an optional memory 111 and processor 113) , communication component 116, and/or receiving component 1030 may be configured to or may comprise means for receiving a unique network ID value on the communication bus.

In an alternative or additional aspect, the device ID is based on an extended ID (EID) , wherein the unique network ID value is based on the device ID.

FIG. 12 is a flowchart of additional aspects of the method of FIG. 11.

Referring to FIG. 12, in an alternative or additional aspect, at block 1202, the method 1100 may further include changing the generic ID value to the device ID at each node in the plurality of nodes. For example, in an aspect, device 106-112, state machine 107, (which may be embodied as an optional memory 111 and processor 113) , communication component 116, and/or changing component 1035 may be configured to or may comprise means for changing the generic ID value to the device ID at each node in the plurality of nodes.

In this optional aspect, at block 1204, the receiving at block 1106 of the unique network ID value comprises receiving in a second message addressed to the device ID.

FIG. 13 is a flowchart of additional aspects of the method of FIG. 11.

Referring to Fig. 13, in an alternative or additional aspect, at block 1302, the method 1100 may further include sending a confirmation of receipt of the unique network ID value to a host node. For example, in an aspect, device 106-112, state machine 107, (which may be embodied as an optional memory 111 and processor 113) , communication component 116, and/or sending component 1040 may be configured to or may comprise means for sending a confirmation of receipt of the unique network ID value to a host node.

Additionally, implementations of the described may include one or more of the following clauses.

Clause 1. A method of network identification (ID) distribution by a host device in a network, comprising: sending a host ID on a communication bus; receiving a device ID from a first node in a plurality of nodes on the communication bus; distributing a first unique network ID value to the first node in the plurality of nodes on the communication bus; and repeating the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remaining node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value.

Clause 2. The method of clause 1, wherein the network is a controller area network (CAN) .

Clause 3. The method of any preceding clause, wherein the device ID is based on an extended ID (EID) .

Clause 4. The method of any preceding clause, wherein sending the host ID comprises sending a message addressed to a generic device ID, wherein the generic device ID is common to each node in the plurality of nodes.

Clause 5. The method of any preceding clause, wherein the EID is based on a part number.

Clause 6. The method of any preceding clause, further comprising receiving a confirmation of receipt of the first unique device ID value and each respective unique network ID value from each node in the plurality of nodes.

Clause 7. The method of any preceding clause, further comprising assigning the first unique network ID value as a new device ID value for the first node based on the EID.

Clause 8. The method of any preceding clause, further comprising determining that each node in the plurality of nodes has been assigned the respective unique device ID value.

Clause 9. The method of any preceding clause, wherein determining that each node in the plurality of nodes has been assigned the respective unique device ID value comprises receiving a null response from each node in the plurality of nodes.

Clause 10. An apparatus for network identification (ID) distribution by a host device in a network, comprising: a memory; and a processor communicatively coupled with the memory and configured to: send a host ID on a communication bus; receive a device ID from a first node in a plurality of nodes on the communication bus; distribute a first unique network ID value to the first node in the plurality of nodes on the communication bus; and repeat the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remain node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value.

Clause 11. The apparatus of clause 10, wherein the network is a controller area network (CAN) .

Clause 12. The apparatus of any of clauses 10 to 11, wherein the device ID is based on an extended ID (EID) .

Clause 13. The apparatus of any of clauses 10 to 12, wherein the EID is based on a part number.

Clause 14. The apparatus of any of clauses 10 to 13, wherein to send the host ID comprises to send a message addressed to a generic device ID, wherein the generic device ID is common to each node in the plurality of nodes.

Clause 15. The apparatus of any of clauses 10 to 14, wherein the processor is further configured to receive a confirmation of receipt of the first unique device ID value and each respective unique network ID value from each node in the plurality of nodes.

Clause 16. The apparatus of any of clauses 10 to 15, wherein the processor is further configured to assign the first unique network ID value as a new device ID value for the first node based on the EID.

Clause 17. The apparatus of any of clauses 10 to 16, wherein the processor is further configured to determine that each node in the plurality of nodes has been assigned the respective unique device ID value.

Clause 18. The apparatus of any of clauses 10 to 17, wherein to determine that each node in the plurality of nodes has been assigned the respective unique device ID value comprises to receive a null response from each node in the plurality of nodes.

Clause 19. A method of network identification (ID) distribution by a slave device of a plurality of slave devices in a network, comprising: receiving a first message including a host ID and a generic ID value on a communication bus, wherein the generic ID value is associated with the slave device; sending a device ID on the communication bus; and receiving a unique network ID value on the communication bus.

Clause 20. The method of clause 19, wherein the network is a controller area network (CAN) .

Clause 21. The method of any of clauses 19 to 20, wherein the device ID is based on an extended ID (EID) , wherein the unique network ID value is based on the device ID.

Clause 22. The method of any of clauses 19 to 21, further comprising: changing the generic ID value to the device ID at each slave device in the plurality of slave devices; wherein receiving the unique network ID value comprises receiving in a second message addressed to the device ID.

Clause 23. The method of any of clauses 19 to 22, further comprising sending a confirmation of receipt of the unique network ID value to a host node.

Clause 24. An apparatus for network identification (ID) distribution by a slave device of a plurality of slave devices in a network, comprising: a state machine configured to: receive a first message including a host ID and a generic ID value on a communication bus, wherein the generic ID value is associated with the slave device; send a device ID on the communication bus; and receive a unique network ID value on the communication bus.

Clause 25. The apparatus of clause 24, wherein the network is a controller area network (CAN) .

Clause 26. The apparatus of any of clauses 24 to 25, wherein the device ID is based on an extended ID (EID) , wherein the unique network ID value is based on the device ID.

Clause 27. The apparatus of any of clauses 24 to 26, wherein the state machine is further configured to: change the generic ID value to the device ID at each slave device in the plurality of slave devices; wherein to receive the unique network ID value comprises receiving a second message addressed to the device ID.

Clause 28. The apparatus of any of clauses 24 to 27, wherein the state machine is further configured to send a confirmation of receipt of the unique network ID value to a host node.

Clause 29. The apparatus of any of clauses 24 to 28, wherein the state machine comprises a processor and a memory.

While the foregoing disclosure discusses illustrative aspects and/or embodiments, it should be noted that various changes and modifications could be made herein without departing from the scope of the described aspects and/or embodiments as defined by the appended claims. Furthermore, although elements of the described aspects and/or embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and/or embodiment may be utilized with all or a portion of any other aspect and/or embodiment, unless stated otherwise.

Claims

A method of network identification (ID) distribution by a host device in a network, comprising:

sending a host ID on a communication bus;

receiving a device ID from a first node in a plurality of nodes on the communication bus;

distributing a first unique network ID value to the first node in the plurality of nodes on the communication bus; and

repeating the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remaining node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value.
The method of claim 1, wherein the network is a controller area network (CAN) .
The method of claim 1, wherein the device ID is based on an extended ID (EID) .
The method of claim 3, wherein sending the host ID comprises sending a message addressed to a generic device ID, wherein the generic device ID is common to each node in the plurality of nodes.
The method of claim 3, wherein the EID is based on a part number.
The method of claim 1, further comprising receiving a confirmation of receipt of the first unique device ID value and each respective unique network ID value from each node in the plurality of nodes.
The method of claim 3, further comprising assigning the first unique network ID value as a new device ID value for the first node based on the EID.
The method of claim 1, further comprising determining that each node in the plurality of nodes has been assigned the respective unique device ID value.
The method of claim 8, wherein determining that each node in the plurality of nodes has been assigned the respective unique device ID value comprises receiving a null response from each node in the plurality of nodes.
An apparatus for network identification (ID) distribution by a host device in a network, comprising:

a memory; and

a processor communicatively coupled with the memory and configured to:

send a host ID on a communication bus;

receive a device ID from a first node in a plurality of nodes on the communication bus;

distribute a first unique network ID value to the first node in the plurality of nodes on the communication bus; and

repeat the sending of the host ID on the communication bus, the receiving of a respective device ID from each remaining node in the plurality of nodes, and the distributing of a unique network ID value to each remain node in the plurality of nodes until each node in the plurality of nodes has been assigned a respective unique network ID value.
The apparatus of claim 10, wherein the network is a controller area network (CAN) .
The apparatus of claim 10, wherein the device ID is based on an extended ID (EID) .
The apparatus of claim 12, wherein the EID is based on a part number.
The apparatus of claim 12, wherein to send the host ID comprises to send a message addressed to a generic device ID, wherein the generic device ID is common to each node in the plurality of nodes.
The apparatus of claim 10, wherein the processor is further configured to receive a confirmation of receipt of the first unique device ID value and each respective unique network ID value from each node in the plurality of nodes.
The apparatus of claim 12, wherein the processor is further configured to assign the first unique network ID value as a new device ID value for the first node based on the EID.
The apparatus of claim 10, wherein the processor is further configured to determine that each node in the plurality of nodes has been assigned the respective unique device ID value.
The apparatus of claim 17, wherein to determine that each node in the plurality of nodes has been assigned the respective unique device ID value comprises to receive a null response from each node in the plurality of nodes.
A method of network identification (ID) distribution by a slave device of a plurality of slave devices in a network, comprising:

receiving a first message including a host ID and a generic ID value on a communication bus, wherein the generic ID value is associated with the slave device;

sending a device ID on the communication bus; and

receiving a unique network ID value on the communication bus.
The method of claim 19, wherein the network is a controller area network (CAN) .
The method of claim 19, wherein the device ID is based on an extended ID (EID) , wherein the unique network ID value is based on the device ID.
The method of claim 21, further comprising:

changing the generic ID value to the device ID at each slave device in the plurality of slave devices; wherein receiving the unique network ID value comprises receiving in a second message addressed to the device ID.
The method of claim 21, further comprising sending a confirmation of receipt of the unique network ID value to a host node.
An apparatus for network identification (ID) distribution by a slave device of a plurality of slave devices in a network, comprising:

a state machine configured to:

receive a first message including a host ID and a generic ID value on a communication bus, wherein the generic ID value is associated with the slave device;

send a device ID on the communication bus; and

receive a unique network ID value on the communication bus.
The apparatus of claim 24, wherein the network is a controller area network (CAN) .
The apparatus of claim 24, wherein the device ID is based on an extended ID (EID) , wherein the unique network ID value is based on the device ID.
The apparatus of claim 24, wherein the state machine is further configured to:

change the generic ID value to the device ID at each slave device in the plurality of slave devices; wherein to receive the unique network ID value comprises receiving a second message addressed to the device ID.
The apparatus of claim 27, wherein the state machine is further configured to send a confirmation of receipt of the unique network ID value to a host node.
The apparatus of claim 24, wherein the state machine comprises a processor and a memory.