DESC: FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See Section 10 and Rule 13)
Title of invention:
METHOD FOR AUTOMATIC CONFIGURATION OF VEHICLE TO CLOUD SERVER

APPLICANT:
MICELIO MOTORS PRIVATE LIMITED
A Company incorporated in India
Having address:
No.58, 15th cross, 2nd phase JP Nagar, Bengaluru-560078, India

The following specification describes the invention and the manner in which it is to be performed.
CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY
The present application claim priority from Indian provisional patent application 202141057996 filed on 13 December 2021
TECHNICAL FIELD
The present disclosure relates to automatic device configuration to the cloud server for exchange of data. More particularly this invention relates to establishment of a secure communication between the device and the cloud server by providing security certificates.
BACKGROUND
The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also correspond to implementations of the claimed technology.
In the conventional art, the IOT devices are configured manually. Manual configuration of the devices is time and effort-consuming and can introduce errors. Generally, the device configuration onto the cloud needs to be done every-time the device is turned ON. Also, there are no systems available where on failed authentication in the middle of the configuration and gaining server access, the security certificates received during the process are discarded.
Therefore, there is an utmost need of an improved system for automatic configuration of the device securely, safely, and efficiently onto the server to enable the device to server communication to receive and send data securely. There is an utmost need of an advanced features system with improvised method of automatic onboarding of device onto the cloud server thereby making it more optimized efficiency system.
SUMMARY
This summary is provided to introduce concepts related to a system and method for operation of automatic device configuration to the cloud server and the concepts are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.
The present disclosure relates to a system and method for operation of automatic device configuration/configuration to the cloud server for data transmission and reception. More specifically, the present disclosure discloses a system for operation of Automatic device configuration to the cloud server for data transmission and reception.
In one implementation, an electric vehicle comprising an OTC unit for operation of automatic device configuration to the cloud server for data exchange is illustrated in accordance with an embodiment of the invention. The OTC unit is configured for transmitting a connection request using a secret key to the cloud server. The OTC unit is further configured for receiving a connection link generated from the cloud server, once the cloud server validates the secret key. Further the OTC unit is configured for transmitting an authentication request comprising a unique serial number associated with the electric vehicle. Upon receipt of the authentication request, the cloud server is configured to authenticate the unique serial number received from the OTC unit, and then generates ADP INFO RESPONSE comprising a unique cloud device ID and security certificates. The OTC unit is configured to receive this ADP INFO RESPONSE from the cloud server and reads it. Further the OTC unit is configured to validate security certificates comprising a CA certificate, a private key, and a public key. The OTC unit may obtain an access to the cloud server after a successful validation of security certificates based on the CA certificate, the private key, and the public key. Furthermore, the OTC unit may store the unique cloud device ID and Security certificates into an internal memory of the OTC, upon successful validation of security certificates. The electric vehicle is enabled to check whether the OTC unit is configured or not when the OTC unit is installed and turned ON for the first time, based on the details available on the internal memory. The electric vehicle is further enabled to use the configuration details received by the OTC unit to establish the communication with the cloud server, whenever/every-time the electric vehicle is powered ON.
In another implementation, a method, in an electric vehicle, for operation of automatic device configuration to the cloud server for data exchange comprising a number of steps is illustrated in accordance with an embodiment of the invention. The method comprises of one or more steps for registering and authenticating a device and to obtain Security certificates for establishing secure communication. The steps include transmitting, by an OTC unit of the electric vehicle, a connection request using a secret key to the cloud server. Further, receiving, by the OTC unit, a connection link from the cloud server, wherein the cloud server is configured to generate the connection link after validating the secret key. In the next step the OTC unit transmits an authentication request, wherein the authentication request comprises a unique serial number associated with the electric vehicle. In further step the OTC unit receives an ADP INFO RESPONSE from the cloud server, wherein the ADP INFO RESPONSE comprises of a unique cloud device ID and security certificates. Obtaining the unique cloud device ID, marks completion of registration of the electric vehicle with the cloud server. The cloud server is configured to generate the ADP INFO Response after authentication of the unique serial number. In the next step there is reading, by the OTC unit, the ADP INFO RESPONSE and validate security certificates, wherein the security certificates comprise of a CA certificate, a private key, and a public key. Further, the OTC unit, obtains access to the cloud server after a successful validation of security certificates based on the CA certificate, the private key, and the public key. The OTC unit further stores the unique cloud device ID and Security certificates into an internal memory of the OTC, upon successful validation of security certificates, otherwise upon a failed validation of security certificates, it discards them. Then step of making another attempt for getting configured to the cloud server is made. Further, the OTC unit of the electric vehicle sends the unique cloud device ID to the cloud server whenever the electric vehicle is turned ON, and the cloud server provides immediate access upon receiving a matched cloud device ID registered with it.

BRIEF DESCRIPTION OF DRAWINGS
The detailed description is described with reference to the accompanying Figures. 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 drawings to refer like features and components.
Figure 1 illustrates a basic block diagram 100 of the system for operation of automatic device configuration to the cloud server 102, in accordance with an embodiment of the present subject matter.
Figure 2 illustrates a workflow diagram 200 of the automatic configuration between the OTC unit 101 and the cloud server 102, in accordance with an embodiment of the present subject matter.
Figure 3 illustrates a workflow diagram 300 of the method for operation of automatic configuration of the electric vehicle to the cloud server 102, in accordance with an embodiment of the present subject matter.

DETAILED DESCRIPTION
Reference throughout the specification to “various embodiments,” “some embodiments,” “one embodiment,” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in various embodiments,” “in some embodiments,” “in one embodiment,” or “in an embodiment” in places throughout the specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.
Now referring to Figure 1, the basic block diagram 100 of the system for operation of automatic device configuration to the cloud server 102 for data exchange is illustrated, in accordance with an embodiment of the present subject matter. As shown, the OTC of the device comprising a micro-controller and a GSM module may be enabled to get configured to the cloud server 102 for sending and receiving of the data.
Further referring to Figure 2, the system may be configured for a facility (ADP process) to initiate OTC unit 101 configuration to the cloud server 102 over a secured port and to obtain access to the cloud on successful configuration. To achieve this, the OTC unit 101 may be enabled to send ADP API call request 201 through a secret key to the cloud server 102 for initiating the configuration process. The cloud server 102 may be enabled to validate the secret key received from the OTC unit 101. The OTC unit 101 may be allowed to have connection with the cloud server 102 through a connection link 202 if the secret key is validated successfully, otherwise the connection request from the OTC unit 101 may be rejected. Further, after the successful validation of the secret key, the cloud server 102 may receive authentication request in the form of ADP HTTP POST REQUEST through the device unique serial number 203 associated with the electric vehicle. The cloud server 102 may perform authentication of the device unique serial number 203 and may be equipped to send ADP INFO RESPONSE 204 to the device upon successful authentication. The ADP INFO RESPONSE 204 may comprise of a unique cloud device ID 204-a and security certificates 204-b.
The OTC unit 101 may be configured for generating a unique cloud device id and sending it to the device along with security certificates 204-b once the device serial number 203 is been authorized, wherein as part of the security certificate 204-b, the server may send a CA certificate, private key, and public key.
The OTC unit 101 may be configured for reading of the ADP INFO RESPONSE 204 and validating the security certificates 204-b, wherein upon a successful validation, the unique cloud device ID 204-a and Security certificates 204-b may be stored onto the internal memory and the configuration process may be completed, whereas upon a failed validation, the OTC unit 101 may discard the security certificates 204-b and another attempt may be made to obtain the configuration details.
Now referring to Figure 3, the flowchart 300 of method for operation of automatic configuration of the electric vehicle to the cloud server 102 for data exchange is illustrated, in accordance with an embodiment of the present subject matter. For achieving this, a plurality of steps may be taken as follows:
At step 301, an ignition switch located on the electric vehicle is pressed to switch on the electric vehicle.
At step 302, the OTC unit 101 is configured to transmit a connection request using a secret key to the cloud server 102.
At step 303, the OTC unit 101 is configured to receive a connection link from the cloud server 102, wherein the cloud server 102 is configured to generate the connection link after validating the secret key.
At step 304, the OTC unit 101 is configured to transmit an authentication request. The authentication request may comprise of a unique serial number 203 associated with the electric vehicle.
At step 305, the OTC unit 101 is configured to receive an ADP INFO RESPONSE 204 from the cloud server 102. The cloud server 102 may be configured to generate the ADP INFO Response 204 after authentication of the unique serial number 203. Further, the ADP INFO RESPONSE 204 may comprise of a unique cloud device ID and security certificates. Upon receiving of the unique cloud device ID 204-a the registration of the electric vehicle to the cloud server 102 is complete.
At step 306, the OTC unit 101 is configured to read the ADP INFO RESPONSE 204 and may validate security certificates 204-b, wherein the security certificates 204-b may comprise of a CA certificate, a private key, and a public key.
At step 307, the OTC unit 101 is configured to obtain access to the cloud server 102 after a successful validation of security certificates 204-b based on the CA certificate, the private key, and the public key.
At step 308, the OTC unit 101 is configured to store the unique cloud device ID 204-a and Security certificates 204-b into an internal memory of the OTC unit 101, upon successful validation of security certificates 204-b. Further, upon a failed validation, the OTC unit 101 may discard the security certificates 204-b and another attempt may be made to obtain the configuration details.
The OTC unit 101 of the electric vehicle may send the unique cloud device ID 204-a to the cloud server 102 whenever the electric vehicle is turned ON. The cloud server 102 may provide immediate access to the electric vehicle, upon receiving a matched cloud device ID 204-a registered with it.
The aforementioned illustrated embodiments offer the following advantages over the conventional system of configuration of IOT device to the cloud server 102, which may include but are not limited to:
• The present disclosure solves need for an automatic configuration of the device securely, safely, and efficiently onto the server to enable the device (OTC) to server communication to receive and send data securely.
• The present disclosure provides a system where there are lesser or almost zero chance of introduction of errors in the system and thus, it may not be subject to security threats.
• The present disclosure also provides the system having Self and Automatic registration of the device thereby reducing consumption of time and efforts than the manual configuration systems.
• Further the present disclosure provides system validating the device and allowing only authenticated devices for cloud communication.
• Furthermore, the present disclosure provides device and cloud communication security.
Further, in one of the embodiments, the system may be enabled to check whether the device is provisioned or not when the device is installed and turned ON for the first time, based on the details available on internal memory.
In another embodiment of the present system, may be enabled to use the configuration details by the device to establish the communication with the cloud server 102, whenever/every-time the device is powered ON.
The embodiments, examples and alternatives of the preceding paragraphs or the description and drawings, including any of their various aspects or respective individual features, may be taken independently or in any combination. Features described in connection with one embodiment are applicable to all embodiments, unless such features are incompatible.
The foregoing description shall be interpreted as illustrative and not in any limiting sense. A person of ordinary skill in the art would understand that certain modifications could come within the scope of this disclosure. For limiting the scope of the invention, a subsequent Complete Specification will be filed to determine the true scope and content of this disclosure
Although implementations for the system and method for operation of device configuration to the cloud server for data exchange have been described in language specific to structural features and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations for the system and method for operation of device configuration to the cloud server for data exchange.
,CLAIMS:WE CLAIM:
1. An electric vehicle enabled for automatically getting configured to a cloud server 102, wherein the electric vehicle comprises:
an OTC unit 101 configured to
transmitting a connection request using a secret key to the cloud server 102;
receiving a connection link from the cloud server 102, wherein the cloud server 102 is configured to generate the connection link after validating the secret key;
transmitting an authentication request, wherein the authentication request comprises a unique serial number 203 associated with the electric vehicle;
receiving an ADP INFO RESPONSE 204 from the cloud server 102, wherein the cloud server 102 is configured to generate the ADP INFO Response 204 after authentication of the unique serial number 203, wherein the ADP INFO RESPONSE 204 comprises of a unique cloud device ID 204-a and security certificates 204-b;
reading the ADP INFO RESPONSE 204 and validate security certificates 204-b, wherein the security certificates 204-b comprise of a CA certificate, a private key, and a public key;
obtaining access to the cloud server 102 after a successful validation of security certificates based on the CA certificate, the private key, and the public key; and
storing the unique cloud device ID 204-a and Security certificates 204-b into an internal memory of the OTC, upon successful validation of security certificates 204-b.

2. The electric vehicle as claimed in claim 1, wherein connection request sent by the OTC unit 101 to the cloud server 102, is in form of ADP API CALL request.

3. The electric vehicle as claimed in claim 1, wherein the authentication request sent by the OTC unit 101 to the cloud server 102, is in form of ADP HTTP POST REQUEST through the connection link.

4. The electric vehicle as claimed in claim 1, wherein the OTC of the electric vehicle comprises a micro-controller and a GSM module which enable the electric vehicle to get configured to the cloud server 102 for sending and receiving of the data.

5. The electric vehicle as claimed in claim 1, wherein upon a failed validation of the security certificates, the OTC unit 101 discards the received security certificates and makes another attempt to obtain the configuration details.

6. The electric vehicle as claimed in claim 1, wherein the electric vehicle is enabled to check whether the OTC unit 101 is configured or not when the OTC unit 101 is installed and turned ON for the first time, based on the details available on the internal memory.

7. The electric vehicle as claimed in claim 1, wherein the electric vehicle is enabled to use the configuration details received by the OTC unit 101 to establish the communication with the cloud server 102, whenever/every-time the electric vehicle is powered ON.

8. A method for automatic configuration of an electric vehicle to a cloud server 102, comprises of steps:

switching on (301) the electric vehicle upon pressing an ignition switch located on the electric vehicle;
transmitting (302), by an OTC unit 101 of the electric vehicle, a connection request using a secret key to the cloud server 102;
receiving (303), by the OTC unit 101, a connection link from the cloud server 102, wherein the cloud server 102 is configured to generate the connection link after validating the secret key;
transmitting (304), by the OTC unit 101, an authentication request, wherein the authentication request comprises a unique serial number 203 associated with the electric vehicle;
receiving (305), by the OTC unit 101, an ADP INFO RESPONSE 204 from the cloud server 102, wherein the cloud server 102 is configured to generate the ADP INFO Response after authentication of the unique serial number 203, wherein the ADP INFO RESPONSE comprises of a unique cloud device ID 204-a and security certificates 204-b;
reading (306), by the OTC unit 101, the ADP INFO RESPONSE 204 and validate security certificates 204-b, wherein the security certificates 204-b comprise of a CA certificate, a private key, and a public key;
obtaining (307), by the OTC unit 101, access to the cloud server 102 after a successful validation of security certificates 204-b based on the CA certificate, the private key, and the public key; and
storing (308), by the OTC unit 101, the unique cloud device ID 204-a and Security certificates 204-b into an internal memory of the OTC, upon successful validation of security certificates 204-b.

9. The method for automatic configuration of an electric vehicle to a cloud server 102 as claimed in claim 8, wherein OTC unit 101 of the electric vehicle sends the unique cloud device ID 204-a to the cloud server 102 whenever the electric vehicle is turned ON, and the cloud server 102 provides immediate access upon receiving a matched cloud device ID 204-a registered with it.
Dated this 13th Day of December 2021

Priyank Gupta
Agent for the Applicant
IN/PA-1454