TECHNICAL FIELD
[0001] The present disclosure relates, in general, to electronic communications in a vehicle.
[0002] In particular, the present disclosure relates to methods and systems of communication among communication devices over a common control network during reconfiguration of the communication devices.
BACKGROUND
[0003] Background description includes information that may be useful in understanding the present subject matter.
[0004] In vehicles, electronic devices communicate with each other in a variety of ways, often based upon the requirements of a given context. One such context is that of control systems. Unlike simple communication systems where the system merely allows for communication among the devices communicating on the system, control systems communicate for the purpose of explicit control over devices connected to communicate over the control system. Such systems then allow other applications to run on various devices. Those applications in distributed embedded control systems, however, should work in synchronization.
[0005] To provide such group control, most distributed embedded control systems are built around a communication protocol standard, examples of which include, but not limited to, CAN (ISO 11898), SERCOS, FlexRay, EtherCAT, and sometimes even Ethernet among others. Higher layer protocols are embedded on top of the communication standard to provide rules for data exchange among participating applications at Electronic Control Units (ECUs) participating in the control network, timing rules, sequence rules, and the like to facilitate

communications between the distributed applications that are exchanging information.
[0006] Each protocol standard has its own strengths and weaknesses. The ideal communication would have infinite bandwidth, no latency, and full data integrity. In the example of CAN systems, CAN protocol provides a mechanism which is incorporated in hardware and software by which different Electronic Control Units (ECUs) can communicate with each other using a common cable (CAN bus), i.e., twisting-pair cables supporting half-duplex protocol and a Carrier Sense Multiple Access/Collision Detection with Arbitration on Message Priority (CSMA/CD+AMP) protocol. CAN protocol ensures high reliability, such as high noise immunity, error detection, and error correction.
[0007] In CAN protocol, a message can be defined as a packet of data which carries information. The data is organized in a specific structure called CAN frame and the information is carried in every byte of that CAN frame. That is, CAN frame is a defined structure, carrying a meaningful sequence of bit or bytes of data within the network.
[0008] CAN protocol is generally of two types: address-based and message-based. In the address based protocol, the data packets contain the address of a target device for which the message is intended. In the message-based protocol, every message is identified by a predefined unique CAN ID rather than the destination addresses. All communication devices connected with the CAN bus has access to read and write data (CAN frame) on the CAN bus. When a communication device is ready to send data, it checks availability of the CAN bus and writes a CAN frame onto the network. Each of the communication devices can receive the transmitted CAN frame and depending on the CAN ID, the CAN frame is accepted or not.
[0009] Due to the dependency on the CAN ID, during the reconfiguration of a transmitting communication device, the device transmits a separate CAN frame with dedicated CAN IDs to inform receiving communication devices to not store diagnostic trouble codes (DTCs), as reconfiguration of transmitting

communication device is taking place and received data may not be correct or reliable.
[0010] However, in some cases, during reconfiguration or update of a transmitting communication device, the transmitting communication device which is undergoing the configuration/update does not inform other receiving communication devices to not store diagnostic trouble codes (DTCs). This results in storage of DTCs, as data may go missing or wrong data is received, at the other receiving communication devices connected over CAN bus with the transmitting communication device which is undergoing the reconfiguration/update. Therefore, a separate deletion command needs to be sent to receiving communication devices in order to let them know to delete the stored DTCs. This require additional CAN IDs which is not generally desired.
[0011] Accordingly, there is a need for methods and systems for avoiding storage of DTCs in communication devices connected to the CAN bus, when one or more communication devices are undergoing reconfiguration, update, or resetting.
OBJECTS OF THE DISCLOSURE
[0012] Some of the objects of the present disclosure, which at least one embodiment herein satisfy, are listed hereinbelow.
[0013] A general object of the present disclosure is to provide methods and systems of communication among communication devices over a common control network during reconfiguration of the communication devices.
[0014] An object of the present disclosure is to avoid storage of diagnostic trouble codes (DTCs) in communication devices connected to the CAN bus when one or more communication devices are undergoing reconfiguration, update, or reset.
[0015] Another object of the present disclosure is to provide a method and a system to distinguish between valid and invalid CAN data frames transmitted by a

transmitting communication device which is undergoing reconfiguration, update or reset.
[0016] These and other objects and advantages of the present disclosure will be apparent to those skilled in the art after a consideration of the following detailed description taken in conjunction with the accompanying drawings in which a preferred form of the present invention is illustrated.
SUMMARY
[0017] This summary is provided to introduce concepts related to methods and systems of communication among communication devices over a common control network during reconfiguration of the communication devices. The concepts are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
[0018] The present disclosure relates to a method of communication among two or more communication devices over a common control network. The method includes receiving, at a communication device which is undergoing through a reconfiguration process, a message packet frame having at least an arbitration field, a control field, and a data field; setting at least a reserved bit (rO or rl) of the control field for using at least one reserved bit (rO or rl) as a validity flag for the message packet frame; and transmitting the message packet frame from the communication device over a control network.
[0019] In an aspect, the method step of setting includes setting the reserved bit (rO) to a recessive bit (1) when the communication device transmits an invalid data in the message packet frame.
[0020] In an aspect, the method step of setting includes setting the reserved bit (rO) to a dominant bit (0) when the communication device transmits a valid data in the message packet frame.

[0021] In an aspect, the communication devices are Electronic Control Units (ECUs).
[0022] In an aspect, the control network is Controller Area Network (CAN).
[0023] The present disclosure further relates to a Controller Area Network (CAN) controller (300) for communication among two or more Electronic Control Units (ECUs) over a Controller Area Network (CAN). The CAN controller includes one or more processors coupled to a memory and a reconfiguration unit. The reconfiguration unit is to set a reserved bit (rO) of a message packet frame, at an ECU undergoing through a reconfiguration process, for using the reserved bit (rO) as a validity flag for the message packet frame.
[0024] In an aspect, the reconfiguration unit is to set the reserved bit (rO) to a recessive bit (1) when the ECU, which is undergoing through the reconfiguration process, transmits an invalid data in the message packet frame.
[0025] In an aspect, the reconfiguration unit is to set the reserved bit (rO) to a dominant bit (0) when the ECU, which is undergoing through the reconfiguration process, transmits a valid data in the message packet frame.
[0026] In an aspect, the reconfiguration unit is to set the reserved bit (rO) to a recessive bit (1) when the ECU, which is undergoing through the reconfiguration process, receives an invalid data in the message packet frame.
[0027] Various objects, features, aspects, and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components.
[0028] It is to be understood that the aspects and embodiments of the disclosure described above may be used in any combination with each other. Several of the aspects and embodiments may be combined to form a further embodiment of the disclosure.
[0029] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features

described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DESCRIPTION OF THE DRAWINGS
[0030] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and/or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and with reference to the accompanying figures, in which:
[0031] Fig. 1 illustrates an exemplary CAN network, in accordance with an embodiment of the present disclosure
[0032] Fig. 2A and Fig. 2B illustrate the exemplary structures of a CAN data frame of CAN protocol, in accordance with an embodiment of the present disclosure;
[0033] Fig. 2C illustrates a standard CAN frame format, in accordance with an embodiment of the present disclosure;
[0034] Fig. 3 illustrates exemplary components of a CAN controller, in accordance with an embodiment of the present subject matter;
[0035] Fig. 4 illustrates a method of communication among two or more communication devices over a common control network, in accordance with an embodiment of the present disclosure; and
[0036] Fig. 5 illustrates a system of communication among two or more communication devices over a common control network, in accordance with an embodiment of the present disclosure.

[0037] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in a computer-readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.
DETAILED DESCRIPTION
[0038] The detailed description of various exemplary embodiments of the disclosure is described herein with reference to the accompanying drawings. It should be noted that the embodiments are described herein in such details as to clearly communicate the disclosure. However, the amount of details provided herein is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the scope of the present disclosure as defined by the appended claims.
[0039] It is also to be understood that various arrangements may be devised that, although not explicitly described or shown herein, embody the principles of the present disclosure. Moreover, all statements herein reciting principles, aspects, and embodiments of the present disclosure, as well as specific examples, are intended to encompass equivalents thereof.
[0040] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "includes" and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements and/or components, but do not preclude the presence

or addition of one or more other features, integers, steps, operations, elements, components and/or groups thereof.
[0041] It should also be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may, in fact, be executed concurrently or may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
[0042] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which example embodiments belong. It will be further understood that terms, e.g., those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
[0043] Embodiments and/or implementations described herein relate to methods and systems of communication among communication devices over a common control network during reconfiguration of the communication devices.
[0044] Reference is made to Fig. 1 which schematically shows a common control network, such as controller area network (CAN) in accordance with an embodiment of the present disclosure. In the CAN network, a plurality of different communication devices, such as Electronic Control Units (ECUs) 102 (individually referred to as 102-1, 102-2, 102-3, 102-4, 102-5,..., 102-N, are communicated to each other through a CAN bus. The CAN bus comprises a CAN H signal line 104 and a CAN L signal line 106. The CAN bus is defined by these two signal lines which are used to transmit and receive CAN data frames.
[0045] As mentioned previously, the CAN system is typically used in the context of a vehicle. Accordingly, in this example, each CAN device may be an engine control unit ECU. However, it should be appreciated that this is by way of

example only and the CAN device may be any suitable device dependent on the context in which the CAN protocol is deployed.
[0046] Exemplary CAN data frames are schematically shown in Figs. 2A and 2B, in accordance with some embodiments of the present disclosure. Fig. 2A illustrates a CAN data frame with 11 bits identifier fields which is called as a standard CAN data frame, while Fig. 2B illustrates 29 bits identifier field which is called as extended CAN data frame.
[0047] Referring to Figs. 2A and 2B, a Start-Of-Frame (SOF) field indicates the start of message and used to synchronize the nodes on a bus. A dominant bit '0' in the field marks the start of frame.
[0048] 11-bit identifier field serves dual purpose, one, to determine which node has access to the bus and, second, to identify the type of message. A Remote Transmission Request (RTR) bit having a default value of '0'. When the RTR bit value is '0', a CAN message is a data frame. When the RTR bit value is '1', the CAN message means Remote Transmission Request (RTR). That is, the RTR bit value of' 1' means that the CAN message is not a data frame but a remote frame.
[0049] Identifier Extension (IDE) is used to specify the frame format. A dominant bit is for standard frame and recessive for extended frame.
[0050] rO and rl - Reserved bits - bits which are not generally used but are kept for future use.
[0051] DLC - Data Length Code - is 4-bit data length code that contains the number of bytes being transmitted.
[0052] DATA - used to store data bits of application data to be transmitted.
[0053] CRC - Cyclic Redundancy Check - is a 16-bit (15 bits plus delimiter) cyclic redundancy check (CRC) contains the checksum of the preceding application data for error detection.

[0054] ACK - Acknowledge (ACK) - comprises of the ACK slot and the ACK delimiter. When the data is received correctly the recessive bit in ACK slot is overwritten as dominant bit by the receiver.
[0055] EOF - End of Frame (EOF) - is a 7-bit field marks the end of a CAN frame (message) and disables Bit - stuffing, indicating a stuffing error when dominant.
[0056] IFS - Inter Frame Space - that specifies a minimum number of bits separating consecutive messages. It provides the intermission between two frames and consists of three recessive bits known as intermission bits. This time allows nodes for internal processing before the start of next frame.
[0057] Both the CAN data frames shown in Figs. 2A and 2B are composed of an arbitration field, a control field, and a data field or a cyclic redundancy check (CRC) field. In accordance with an implementation of the present disclosure, a reserved bit (rO) of the control field is used as a validity flag for the message packet frame, i.e., CAN data frame, transmitted by a communication device which is undergoing through a reconfiguration process. The reconfiguration process may include, but not limited to, a software update process, a factory reset process, a reprogramming process, and so forth.
[0058] Figs. 3 and 5 illustrate exemplary components of a CAN controller 300 and 600, in accordance with some embodiments of the present disclosure. The CAN controller 300 can work as a transmitter CAN node and as a receiver CAN Node in the CAN network. When the CAN controller work as a transmitter it can be referred as CAN controller 300 and when the CAN controller work as receiver it can be referred as CAN controller 600. The CAN controller 300 includes a processor(s) 302, an interface(s) 304, and a memory 306.
[0059] The processor(s) 302 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, logic circuitries, and/or any devices that manipulate data based on operational instructions.

[0060] Among other capabilities, the one or more processor(s) 302 are configured to fetch and execute computer-readable instructions and one or more routines stored in the memory 306. The memory 306 may store one or more computer-readable instructions or routines, which may be fetched and executed to implement reconfiguration of communication devices, say, ECUs. The memory 306 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0061] The interface(s) 304 may include a variety of interfaces, for example, interfaces for data input and output devices referred to as I/O devices, storage devices, and the like. The interface(s) 304 may facilitate communication of the CAN controller 300 with various devices coupled to the CAN controller 300. The interface(s) 304 may also provide a communication pathway for one or more components of the CAN controller 300. Examples of such components include, but are not limited to, processing unit(s) 308 and data 310.
[0062] The processing unit(s) 308 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit(s) 308. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing unit(s) 308 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing unit(s) 308 may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing unit(s) 308. In such examples, the CAN controller 300 may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions or the machine-readable storage medium may be separate but accessible to the CAN

controller 300 and the processing resource. In other examples, the processing unit(s) 308 may be implemented by electronic circuitry.
[0063] In an aspect, the processing unit(s) 308 may include a reconfiguration unit 312 and a determining unit 314. The processing unit(s) 308 may include other unit(s) which may implement functionalities that supplement applications or functions performed by the CAN controller 300 or the processing unit(s) 308.
[0064] Further, the data 310 may include data that is either stored or generated as a result of functionalities implemented by any of the components of the processing unit(s) 308. In some aspects, the data 310 may be stored in the memory 306 in the form of various data structures. Additionally, data 310 can be organized using data models, such as relational or hierarchical data models. The data 310 may store data, including temporary data and temporary files, generated by the processing unit(s) 308 for performing the various functions of the CAN controller 300.
[0065] In operation, when a communication device (ECU) is undergoing through a reconfiguration process, the reconfiguration unit 312 sets the reserved bit (rO) of the CAN data frame to a recessive bit, which is logical 1.
[0066] In case, a valid data is transmitted by the communication device (ECU) which is not under reconfiguration process, the reconfiguration unit 312 sets the reserved bit (rO) of the CAN data frame to a dominant bit, which is logical 0.
[0067] Now, in case a receiving communication device (ECU) 600 receives the invalid data with the CAN data frame having reserved bit (rO) set as a recessive bit (1), the receiving communication device (ECU) 600 will not use that CAN data frame. However, since the reserved bit (rO) is set with recessive bit (1), the receiving communication device (ECU) 600 will also not store diagnostic trouble code (DTC) for the invalid or unreliable data received over the CAN data frame. The receiving communication device (ECU) 600 will only use the CAN data frame when the reserved bit (rO) is set with a dominant bit (0).

[0068] Thus, during ECU reconfiguration or internal change, such as software update, factory setting change, reprogramming, etc., the transmitting communicating device ECU 300 will not stop transmitting CAN data frames. Rather, the transmitting communicating device ECU 300 will communicate to a receiving communication device or target ECU 600 that the data transmitted in the CAN data frames is invalid or unreliable due to some reconfiguration or internal change in the transmitting ECU or transmitting communication device 300.
[0069] Thus, with the implementation of the present disclosure, no extra CAN ID is required to let the other receiving communication devices 600 know that the received data is valid or invalid. Also, no transmission is stopped or paused due to software update in a transmitting ECU or a transmitting communication device 300, in order to prevent storing of DTCs by receiving ECUs or receiving communication devices 600.
[0070] In operation, the receiving communication device or receiving ECU or the CAN controller 600 having determining unit 314 determines whether the received data has dominant bit (0) or recessive bit (1) in the reserved bit space. Upon determining, the receiving communication device 600 uses the CAN data frame having reserved bit with dominant bit (0) and discard the CAN frame data with recessive bit (1) in the reserved bit. Accordingly, there is no need of any extra CAN IDs being sent by transmitting communication device 300 to let receiving communication device 600 know that invalid data is being sent, in order to prevent logging of any DTCs. Upon discarding the invalid CAN frame data based on recessive bit, the receiving communication device 600 does not store any DTC based on the existing CAN ID present on the CAN data frames and CAN bus.
[0071] Fig. 4 illustrates a method 400 of communication among two or more communication devices over a common control network, according to an embodiment of the present disclosure. The order in which the method 400 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any appropriate order to carry out

the method 400 or an alternative method. Additionally, individual blocks may be deleted from the method 400 without departing from the scope of the subject matter described herein.
[0072] At block 402, the method 400 includes initiating, at a communication device which is undergoing through a reconfiguration process, a message packet frame having at least an arbitration field, a control field, and a data field;
[0073] At block 404, the method 400 includes setting a reserved bit (rO) of the control field for using the reserved bit (rO) as an internal validity flag for the message packet frame; and
[0074] At block 406, the method 400 includes transmitting the message packet frame from the transmitting communication device over a control network.
[0075] In an aspect, the method step of setting includes setting the reserved bit (rO) to a dominant bit (0) when the communication device transmits a valid data in the message packet frame.
[0076] In an aspect, the method step of setting includes setting the reserved bit (rO) to a recessive bit (1) when the communication device receives invalid data in the message packet frame.
[0077] In an aspect, the communication devices are Electronic Control Units (ECUs).
[0078] In an aspect, the control network is Controller Area Network (CAN).
[0079] Referring to Fig. 5, which schematically shows a system 700 accordance with an embodiment of the present disclosure. In the CAN network, a plurality of different communication devices, such as Electronic Control Units (ECUs) 300, 600, 500 are communicating with each other through a CAN bus. The CAN bus is defined to transmit and receive CAN data frames. From the plurality of different communication devices, one device may act as a transmitter and another may act as a receiver at one time. To explain the present implementation in the system 600 where one CAN controller 300 is working as a transmitter and other CAN controller 600 is working as receiver. The system 700

comprises a plurality of CAN controllers (300, 600, 500) for transmitting and receiving message data frames over a Controller Area Network (CAN). The CAN controller 300 acting as transmitting device undergoing through a reconfiguration process transmits a message data frame with reserved bit (rO) as a validity flag. The CAN controller 600 acting as receiving device for receiving the message data frame with the reserved bit (rO) as the validity flag.
[0080] The CAN controller 300, 600 comprise one or more processors 302 coupled to a memory 306 and a reconfiguration unit 312 and a determining unit 314 as shown in figures 3 and 5. The reconfiguration unit (312) is configured to set the reserved bit (rO) to a recessive bit (1) when the ECU, which is undergoing through the reconfiguration process, transmits an invalid data in the message packet frame. The reconfiguration unit (312) sets the reserved bit (rO) to a dominant bit (0) when the ECU, which is not undergoing through the reconfiguration process, transmits a valid data in the message packet frame.
[0081] The CAN controller 600 is configured to receive the message frame data and determine the reserved bit (rO) of the message frame data and use the message frame data when reserved bit (rO) of message frame data is dominant bit (0). Further, the CAN controller 600 discards the message frame data with reserved bit (rO) as recessive bit (1) without logging any DTC.
[0082] The above description does not provide specific details of the manufacture or design of the various components. Those of skill in the art are familiar with such details, and unless departures from those techniques are set out, techniques, known, related art or later developed designs and materials should be employed. Those in the art can choose suitable manufacturing and design details.
[0083] It should be understood, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, as apparent from the discussion herein, it is appreciated that throughout the description, discussions utilizing terms such as "receiving," or "setting," or "transmitting," or the like, refer to the action and processes of an electronic

control unit, or similar electronic device, that manipulates and transforms data represented as physical (electronic) quantities within the control unit's registers and memories into other data similarly represented as physical quantities within the control unit memories or registers or other such information storage, transmission or display devices.
[0084] Further, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. It will be appreciated that several of the above-disclosed and other features and functions, or alternatives thereof, may be combined into other systems or applications. Various presently unforeseen or unanticipated alternatives, modifications, variations, or improvements therein may subsequently be made by those skilled in the art without departing from the scope of the present disclosure as encompassed by the following claims.
[0085] It will be appreciated that variants of the above-disclosed and other features and functions, or alternatives thereof, may be combined into many other different systems or applications. Various presently unforeseen or unanticipated alternatives, modifications, variations, or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the following claims.
[0086] The claims, as originally presented and as they may be amended, encompass variations, alternatives, modifications, improvements, equivalents, and substantial equivalents of the embodiments and teachings disclosed herein, including those that are presently unforeseen or unappreciated, and that, for example, may arise from applicants/patentees and others.

We claim

1.A method of communication among two or more communication devices
over a Controller Area Network (CAN), the method comprising:
initiating (402), at a communication device, a message packet frame having at least an arbitration field, a control field, and a data field;
setting (404) a reserved bit (rO) of the control field for using the reserved bit (rO) as a validity flag for the message packet frame; and
transmitting (406) the message packet frame from the communication device over the CAN.
2. The method as claimed in claim 1, wherein the setting (404) comprises setting the reserved bit (rO) to a recessive bit (1) when the communication device undergoing reconfiguration transmits an invalid data in the message packet frame.
3. The method as claimed in claim 1, wherein the setting (404) comprises setting the reserved bit (rO) to a dominant bit (0) when the communication device transmits a valid data in the message packet frame.
4. The method as claimed in claim 1, wherein the communication devices are Electronic Control Units (ECUs) having a CAN controller (300, 600, 500).
5. A Controller Area Network (CAN) controller (300) for communication among two or more Electronic Control Units (ECUs) over a Controller Area Network (CAN) and transmitting message packet frames, the CAN controller (300) comprising:
one or more processors (302) coupled to a memory (306) and a reconfiguration unit (312), the reconfiguration unit (312) is to:

set a reserved bit (rO) of a message packet frame, at an ECU, for using the reserved bit (rO) as a validity flag for the message packet frame.
6. The CAN controller (300) as claimed in claim 7, wherein the reconfiguration unit (312) is to set the reserved bit (rO) to a recessive bit (1) when the ECU, which is undergoing through the reconfiguration process, transmits an invalid data in the message packet frame.
7. The CAN controller (300) as claimed in claim 7, wherein the reconfiguration unit (312) is to set the reserved bit (rO) to a dominant bit
(0) when the ECU, which is not undergoing through the reconfiguration
process, transmits a valid data in the message packet frame.
8. The CAN controller (300) as claimed in claim 7, wherein the
reconfiguration unit (312) is to set the reserved bit (rO) to a recessive bit
(1) when the ECU, which is undergoing through the reconfiguration
process, initiates an invalid data in the message packet frame.
9. A CAN controller (300, 600) for communication among two or more
Electronic Control Units (ECUs) over a Controller Area Network (CAN)
and receiving a message packet frame, the CAN controller (300, 600)
comprising:
one or more processors (302) coupled to a memory (306) and a determining unit (314), the determining unit (314) is to:
receive the message packet frame from an ECU undergoing through a reconfiguration process;
determine reserved bit (rO) of the message packet frame; and
use the message packet frame when reserved but (rO) is dominant bit
(0).

10. A system (700) having a plurality of CAN controllers (300, 600, 500) for
transmitting and receiving message data frames over a Controller Area
Network (CAN), the system (700) comprising:
a CAN controller (300), at an ECU undergoing through a reconfiguration process, for transmitting a message data frame with reserved bit (rO) as a validity flag; and
a CAN controller (600) for receiving the message data frame with the reserved bit (rO) as the validity flag.
11. The system (700) as claimed in claim 10, wherein the CAN controller
(300) comprising:
one or more processors (302) coupled to a memory (306) and a reconfiguration unit (312), the reconfiguration unit (312) is to:
set the reserved bit (rO) to a recessive bit (1) when the ECU, which is undergoing through the reconfiguration process, transmits an invalid data in the message packet frame; and
set the reserved bit (rO) to a dominant bit (0) when the ECU, which is not undergoing through the reconfiguration process, transmits a valid data in the message packet frame.
12. The system (700) as claimed in claim 10, wherein the CAN controller
(600) configured to:
receive the message frame data and determine the reserved bit (rO) of the message frame data; and
use the message frame data when reserved bit (rO) of message frame data is dominant bit (0).