FORM2
THE PATENTS ACT 1970
39 OF 1970
&
THE PATENT RULES 2003
COMPLETESPECIFICATION
(SEE SECTIONS 10 & RULE 13)
1. TITLEOF THE INVENTION
“METHODS AND SYSTEMS FOR DYNAMIC VEHICLE DATABASE INTEGRATION IN AN ELECTRONIC CONTROL UNIT”
2. APPLICANTS (S)
(a) Name: Varroc Engineering Limited
(b) Nationality: Indian
(c) Address: L-4, Industrial Area,
Waluj MIDC, Aurangabad-431136, Maharashtra, India
3. PREAMBLETOTHEDESCRIPTION
COMPLETESPECIFICATION
The following specification describes the invention.

METHODS AND SYSTEMS FOR DYNAMIC VEHICLE DATABASE INTEGRATION IN AN ELECTRONIC CONTROL UNIT
TECHNICAL FIELD
[0001] Present disclosure generally relates to an automobile. Particularly, but not exclusively, the present disclosure relates to a dynamic vehicle database integration in an electronic control unit (ECU).
BACKGROUND
[0002] Today’s vehicles may contain several electronic control units (ECUs) for controlling functions that ranges from the essential (such as engine and power steering control) to comfort (such as power windows, seats and heating, ventilation, and air conditioning (HVAC)), to security and access (such as door locks and keyless entry). The ECUs are one of the most important parts of a vehicle. The ECU manages and controls electronic systems of the vehicle based on multiple sensors that feed the ECU data. Each ECU typically contains a dedicated chip that runs its own software or firmware and requires power and data connections to operate.
[0003] The ECU receives inputs from different parts of the vehicle depending on the functionality to be performed. For example, a door lock ECU may receive input when a passenger pushes the door lock/unlock button on a car door or on a wireless key fob. An airbag ECU may receive inputs from crash sensors and from sensors that detect when someone is sitting in a particular seat. Further, an automatic emergency braking ECU may receive inputs from forward-facing radars that detect when the vehicle is approaching an obstacle too quickly.
[0004] Each ECU acts as node within the vehicle and communicates using different network protocols such as CAN/CANFD (label 4), J1939, LIN (label 3), Ethernet, etc. Presently, in vehicle integrated system each node is manually integrated with a respective communication database that helps the node to understand what

information is to be received or transmitted by each node. These databases may vary from one ECU to another.
[0005] However, integration of the database file into the ECU SW is a time taking and error prone job and is usually carried out by ECU supplier. As there are multiple variants of vehicle available in the market, it becomes difficult to manually integrate the database in the ECU based on the variant of the vehicle. After the ECU is manually integrated with the database of one vehicle, the ECU cannot be installed directly onto another vehicle without manually reimplementation of new communication database inside the ECU. Thus, the ECU configuration and reconfiguration is carried out only through manual intervention.
[0006] Therefore, there exists a need in the art to provide a solution which overcomes the above-mentioned problem and to provide a technique that dynamically integrates the communication database in the ECU based on the vehicle in which the ECU is installed without manual intervention.
SUMMARY
[0007] The present disclosure overcomes one or more shortcomings of the prior art and provides additional advantages discussed throughout the present disclosure. Additional features and advantages are realized through the techniques of the present disclosure. Other aspects of the disclosure are described in detail herein and are considered as a part of the claimed disclosure.
[0008] In one non-limiting aspect of the present disclosure, a method of dynamic vehicle database integration in an electronic control unit (ECU) is disclosed. Whenever the ECU is installed in new vehicle, ECU learns the unique identifier of vehicle and if it is new identifier, the method comprises determining a unique identifier associated with a vehicle, transmitting a request for network/communication database associated with the unique identifier to a server, retrieving the database from

the server and download it in a memory manager present inside the ECU, and configuring/reconfiguring one or more parameters of the ECU based on the retrieved network database. Thus, the method facilitates dynamic vehicle database integration in the ECU without any manual intervention, thereby eliminating the time of manually integrating the database in the ECU and avoiding errors in integrating the database in the ECU.
[0009] In another non-limiting aspect of the present disclosure, a method of dynamic vehicle database integration in an electronic control unit (ECU) is disclosed. The method comprises determining a unique identifier associated with the vehicle, transmitting a first request for network database associated with the unique identifier to a memory manager of the vehicle, receiving a negative acknowledgement from the memory manager, transmitting a second request for the network database associated with the unique identifier to a cloud server, retrieving the network database associated with the unique identifier from the cloud server, and configuring/reconfiguring one or more parameters of the ECU based on the retrieved network database. Thus, the method facilitates dynamic vehicle database integration in the ECU without any manual intervention, thereby eliminating the time of manually integrating the database in the ECU and avoiding errors in integrating the database in the ECU. Further, the method also facilitates remote storage of the network database at the server.
[0010] In yet another non-limiting aspect of the present disclosure, a system for dynamic vehicle database integration in an electronic control unit (ECU) is disclosed. The system comprises a vehicle identification unit operable to determine a unique identifier associated with a vehicle, a transceiver operable to transmit a request for network database associated with the unique identifier to a memory manager or a server, a processing unit operable to retrieve the network database associated with the unique identifier from the memory manager or the server, and a configuration unit operable to configure/reconfigure one or more parameters of the ECU based on the retrieved network database. Thus, the system facilitates dynamic vehicle database

integration in the ECU without any manual intervention, thereby eliminating the time of manually integrating the database in the ECU and avoiding errors in integrating the database in the ECU.
[0011] In yet another non-limiting aspect of the present disclosure, a cloud server for maintaining a plurality of vehicle database is disclosed. The cloud server may comprise a memory operable to store the plurality of vehicle database, a transceiver operable to receive, from an ECU, a request for network database associated with a unique identifier, a processing unit operable to identify a network database mapped with the unique identifier and transmit the network database to the ECU. Thus, the cloud server facilitates remote storage of the network database at the cloud server. Learning and updating the communication data is not limited to ECU which is connected to server, via same ECU it can update network database of other ECU on the same network or ECU connected on other network via gateway module
[0012] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, aspects, and features described above, further aspects, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
[0013] The features, nature, and advantages of the present disclosure will become more apparent from the detailed description set forth below when taken in conjunction with the drawings in which like reference characters identify correspondingly throughout. Some aspects of system and/or methods in accordance with aspects of the present subject matter are now described, by way of example only, and with reference to the accompanying figures, in which:
[0014] Fig. 1 illustrates an environment for dynamic vehicle database integration, in accordance with an aspect of the present disclosure;

[0015] Fig. 2(a) shows an exemplary communication block diagram illustrating dynamic vehicle database integration, in accordance with an aspect of the present disclosure;
[0016] Fig. 2(b) shows an exemplary communication block diagram illustrating dynamic vehicle database integration, in accordance with another aspect of the present disclosure;
[0017] Fig. 3 illustrates a block diagram of the system for dynamic vehicle database integration in electronic control unit (ECU), in accordance with an aspect of the present disclosure; and
[0018] Fig. 4 illustrates a flowchart of a method of dynamic vehicle database integration in electronic control unit (ECU), in accordance with an aspect of the present disclosure;
[0019] It should be appreciated by those skilled in the art that any block diagram herein represents conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.
DETAILED DESCRIPTION
[0020] The terms “comprise”, “comprising”, “include(s)”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, system or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or system or method. In other words, one or more elements in a system or apparatus proceeded by “comprises… a” does not, without more

constraints, preclude the existence of other elements or additional elements in the system or apparatus.
[0021] In the following detailed description of the aspects of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific aspects in which the disclosure may be practiced. These aspects are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other aspects may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.
[0022] Fig. 1 illustrates an environment 100 for dynamic vehicle database integration, in accordance with an aspect of the present disclosure.
[0023] In an aspect of the present disclosure, the environment 100 shows a vehicle comprising a plurality of electronic control units (ECUs). Each ECU may be mapped with a respective functionality of the vehicle. In an exemplary aspect, an ECU 101 may be main or central control unit of the vehicle, ECU 103 may be mapped with an instrument cluster of the vehicle, ECU 105 may be mapped with steering wheel panel of the vehicle, ECU 107 may be mapped with at least one door of the vehicle, ECU 109 may be mapped with at least one seat of the vehicle, ECU 111 may be mapped with rear lighting of the vehicle, and ECU 113 may be mapped with rear trunk and rear wiper of the vehicle. In one non-limiting aspect, the plurality of ECUs are connected through at least one controller area network (CAN), local interconnect network (LIN), media-oriented system transport (MOST), Ethernet or any other vehicle network protocol. However, this mapping is exemplary, and a vehicle may have an ECU mapping and number of ECUs may be different from the one disclosed above.
[0024] The plurality of ECUs may perform one or more functionalities based on inputs received by the ECU. The ECU may generally require vehicle database integration for

ECU configuration/reconfiguration. The vehicle database integration helps the ECU to understand the input and output parameter of the ECU. In one non-limiting aspect of the present disclosure, other necessary parameters related to the ECU are also defined within the database file to be integrated in the ECU.
[0025] In an aspect of the present disclosure, the ECUs may be installed in the vehicle without manual database integration. Once the ECU is installed, the ECU may communicate with memory manager/database of the vehicle and retrieve the network database of the vehicle based on a unique identifier associated with the vehicle. The unique identifier may be the vehicle identification number. The ECU may then configure/reconfigure itself based on the retrieved network database.
[0026] In one non-limiting aspect, the network database may be stored at a cloud server and the ECU may communicate with the cloud server and retrieve the network database of the vehicle based on a unique identifier associated with the vehicle from the cloud server. The cloud server may comprise a repository of network database stored in the memory against the respective unique identifier. The cloud server may determine/identify the network database corresponding to a unique identifier received from the ECU and transmit the network database back to the ECU. The ECU may connect and communicate with the cloud server via medium of Cellular GSM connection, WI-FI or BT, Ethernet, and the like.
[0027] Thus, the dynamic vehicle database integration in the ECU is carried out without any manual intervention, thereby eliminating the time of manually integrating the database in the ECU and avoiding errors in integrating the database in the ECU. Further, the cloud server facilitates remote storage of the network database at the server.
[0028] Fig. 2(a) shows an exemplary communication block diagram 200a illustrating dynamic vehicle database integration, in accordance with an aspect of the present disclosure.

[0029] In an aspect of the present disclosure, the communication block diagram 200a comprises a cloud server 201, a vehicle main ECU 203, a memory manager 205, and an ECU 207 in communication with each other. The ECU 207 may require the network database to perform one or more functionalities of the ECU 207.
[0030] The ECU 207 may initially request the memory manager 205 of the vehicle for the network database for configuring the ECU 207. The request may comprise a unique identifier such as vehicle identification number. If the memory manager 205 comprise the network database corresponding to the unique identifier, the network database is transmitted back to ECU 207 for configuring/reconfiguring.
[0031] However, if the memory manager 205 does not have the network database corresponding to the unique identifier, the ECU 207 may then request the cloud server 201 for the network database through the vehicle main ECU 203 using the unique identifier associated with the vehicle. The cloud server 201 may identify the network database based on the unique identifier and provide the network database to the vehicle main ECU 203. The ECU 207 may receive the network database from the vehicle main ECU 203 and then the ECU 207 may configure/reconfigure one or more parameters of the ECU 207 based on the network database.
[0032] This facilitates dynamic integration of the vehicle database in the ECU, thereby eliminating the process of manual integration and also allowing the same ECU to be used anywhere inside the vehicle based on the requirement. Further, this also allows reusability of the ECU across different variants of the vehicle.
[0033] Fig. 2(b) shows an exemplary communication block diagram 200b illustrating dynamic vehicle database integration, in accordance with another aspect of the present disclosure.
[0034] In an aspect of the present disclosure, the communication block diagram 200b comprises a cloud server 201, a memory manager 205, and an ECU 207 in

communication with each other. The ECU 207 may require the network database to perform one or more functionalities of the ECU 207.
[0035] Once the ECU 207 is installed inside the vehicle, the ECU 207 may initially request the memory manager 205 of the vehicle for the network database for configuring the ECU 207. The request may comprise a unique identifier such as vehicle identification number. If the memory manager 205 comprise the network database corresponding to the unique identifier, the network database is transmitted back to ECU 207 for configuring/reconfiguring one or more parameters of the ECU 207.
[0036] However, if the memory manager 205 does not have the network database corresponding to the unique identifier, the ECU 207 may then directly request the cloud server 201 for the network database by transmitting the unique identifier associated with the vehicle. The cloud server 201 may identify the network database based on the unique identifier and provide the network database to the ECU 207. The ECU 207 may then configure/reconfigure one or more parameters of the ECU 207 based on the network database.
[0037] This facilitates dynamic integration of the vehicle database in the ECU, thereby eliminating the process of manual integration and also allowing the same ECU to be used anywhere inside the vehicle based on the requirement. Further, this also allows reusability of the ECU across different variants of the vehicle.
[0038] Fig. 3 illustrates a block diagram of the system 300 for dynamic vehicle database integration in Electronic Control Unit (ECU), in accordance with an aspect of the present disclosure.
[0039] In an aspect of the present disclosure, the system 300 may comprise an ECU 310 to be configured/reconfigured and a cloud server 320 in communication with each other. The communication may be done over the internet through networking protocol

such as wi-fi, ethernet, global system for mobile communications (GSM), etc. The ECU 310 may be one of, but not limited to, ECU 101, 103, 105, 107, 109, 111, and 113. The ECU 310 may be in connection with the cloud server 320 through the internet. In one non-limiting aspect, the ECU 310 may be connected to the cloud server 320 via a central or main ECU of the vehicle, as shown in fig. 2(a).
[0040] The ECU 310 may comprise a processing unit 301, a database/memory 302, a transceiver 303, input/output (I/O) interface 304, a vehicle identification unit 305, a configuration unit 306, and other units 307. The other units 307 may comprise the necessary hardware features of the ECU 310 required to carry out a specific functionality of the ECU 310 apart from the functionalities discussed in below aspects.
[0041] The cloud server 320 may comprise a database/memory 321 operable to store a plurality of network databases corresponding to a plurality of unique identifiers associated with different variants and types of vehicles. The cloud server 320 may further comprise a processing unit 323 and a transceiver 325 communicatively coupled to the database/memory 321.
[0042] The vehicle identification unit 305 may be operable to identify a unique identifier associated with the vehicle on which the ECU 310 is installed. In one non-limiting aspect, the unique identifier may be a vehicle identification number that varies from one variant of the vehicle to another.
[0043] In an aspect, the processing unit 301 may be then operable to request network database from a memory manager (not shown) of the vehicle. In response to receiving the network database from the memory manager, the configuration unit 306 may be operable to configure/reconfigure one or more parameters of the ECU 310 based on the network database. The one or more parameters may comprise one or more input/output parameters of the ECU 310.

[0044] In another aspect of the present disclosure, the processing unit 301 may be operable to transmit the request for network database to the cloud server 320 through the transceiver 303. The cloud server 320 may receive the request for the network database through the transceiver 325. The processing unit 323 of the cloud server 320 may be operable to identify the network database corresponding to the unique identifier present in the request. The processing unit 323 may be then operable to transmit the network database corresponding to the ECU 310 through the transceiver 325. The processing unit 301 may be operable to process and extract configuration files from the network database. The configuration unit 306 may be operable to configure/reconfigure one or more parameters of the ECU 310 based on the network database. The one or more parameters may comprise one or more input/output parameters of the ECU 310.
[0045] In one non-limiting aspect, the vehicle identification unit 305 and the configuration unit 306 may comprise a memory and one or more processors along with necessary hardware components required to carry out the above-mentioned functionalities of the ECU 310.
[0046] Thus, the system 300 facilitates dynamic vehicle database integration in the ECU without any manual intervention, thereby eliminating the time of manually integrating the database in the ECU and avoiding errors in integrating the database in the ECU. Further, the system 300 allows the same ECU to be used anywhere inside the vehicle based on the requirement. Furthermore, the system 300 facilitates reusability of the ECU across different variants of the vehicle.
[0047] Fig. 4 illustrates a flowchart of a method 400 of dynamic vehicle database integration in electronic control unit (ECU), in accordance with an aspect of the present disclosure.
[0048] At block 401, a unique identifier associated with a vehicle is determined. The unique identifier may be associated with a vehicle on which the ECU is installed. In

one non-limiting aspect, the unique identifier may be a vehicle identification number that varies from one variant of the vehicle to another.
[0049] At block 403, a request for network database associated with the unique identifier is transmitted from the ECU. In one non-limiting aspect, the request may be transmitted to a memory manager of the vehicle. In one non-limiting aspect, the request for network database may be transmitted directly or indirectly to the cloud server as discussed in above aspects.
[0050] At block 405, the network database associated with the unique identifier may be retrieved. In one non-limiting aspect, the retrieving comprises receiving the network database from the memory manager. In another no-limiting aspect, the retrieving comprises receiving the network database corresponding to the unique identifier from the cloud server.
[0051] At block 407, one or more parameters of the ECU may be configured/reconfigured based on the retrieved network database. The one or more parameters may comprise one or more input/output parameters of the ECU.
[0052] Thus, the method 400 facilitates dynamic vehicle database integration in the ECU without any manual intervention, thereby eliminating the time of manually integrating the database in the ECU and avoiding errors in integrating the database in the ECU. Further, the method 400 allows the same ECU to be used anywhere inside the vehicle based on the requirement. Furthermore, the method 400 facilitates reusability of the ECU across different variants of the vehicle.
[0053] In another aspect of the present disclosure, the steps of method 400 may be performed in an order different from the order described above.
[0054] The illustrated steps are set out to explain the exemplary aspects shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for

purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed aspects.
[0055] Furthermore, one or more computer-readable storage media may be utilized in implementing aspects consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the aspects described herein. The term “computer- readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., are non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, nonvolatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.
[0056] Suitable processors include, by way of example, a processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.

We Claim:
1. A method for dynamic vehicle database integration in an electronic control unit
(ECU) comprising:
determining a unique identifier associated with a vehicle;
transmitting a first request for network database associated with the unique identifier to a memory manager present inside the vehicle, wherein the memory manager can be part of an ECU or a main ECU which is connected to a server or it can be separate ECU providing feature of memory manager;
retrieving the network database associated with the unique identifier from the memory manager; and
configuring/reconfiguring one or more parameters of the ECU based on the retrieved network database.
2. The method as claimed in claim 1, further comprising:
transmitting a second request for the network database associated with the unique identifier to a cloud server;
retrieving the network database associated with the unique identifier from the cloud server; and
configuring/reconfiguring one or more parameters of the ECU based on the retrieved network database from the cloud server.
3. The method as claimed in claim 1, wherein the unique identifier is a vehicle identification number.
4. The method as claimed in claim 1, wherein the network database is configured at a cloud server.

5. The method as claimed in claim 2, wherein the cloud server may comprise a repository of network database stored in the memory against the respective unique identifier.
6. A system for dynamic vehicle database integration in an electronic control unit (ECU) comprising:
a vehicle identification unit operable to determine a unique identifier associated with a vehicle;
a transceiver operable to transmit a request for network database associated with the unique identifier to a memory manager or a server;
a processing unit operable to retrieve the network database associated with the unique identifier from the memory manager or the server; and
a configuration unit operable to configure/reconfigure one or more parameters of the ECU based on the retrieved network database.
7. The system as claimed in claim 6, wherein the ECU is connected to the cloud server 320 via a vehicle main ECU.
8. The system as claimed in claim 6, further comprising:
a cloud server for maintaining a plurality of vehicle database;
the cloud server comprise a memory operable to store the plurality of vehicle database;
a transceiver operable to receive, from an ECU, a request for network database associated with a unique identifier; and
a processing unit operable to identify a network database mapped with the unique identifier and transmit the network database to the ECU.