Description:FIELD OF THE INVENTION
[001] The present invention relates to a vehicle. More particularly, the present invention relates to a system and method for connecting one or more accessories to a vehicle.

BACKGROUND OF THE INVENTION
[002] Prior arts discloses methods to attach wireless accessories onto a computing device by transacting protocol details device identifier with a host and the host deciding whether a wireless protocol connection must be made to the accessory. While this could hold good to some extent with personal computing devices, when such a method is taken to one or more accessories in an automotive domain, an additional layer of security must be ensured to avoid any chances of hacking or theft. In automotive accessories, unauthorized connected device can be fatal, since the connected device will get access to the vehicle network. Such unauthorized accessories can send unwanted commands to the vehicle network, which is a major security concern.
[003] Also, with an advent of new connectivity options, sensors and actuators, more meaningful and relevant accessories for automobiles are being made these days. However, such smart and connected accessories for automobiles ends up being a closed implementation and ends at being usable with a particular vehicle model or manufacturer alone. This also leads accessory manufacturers to come with additional fittings to integrate such smart accessories into a vehicle. Owing to such practices, the end-users cannot reuse their accessories across different models of vehicles and accessory manufacturers are unable to cater to a wider variety of customers and OEMs, which is undesirable.
[004] In view of the foregoing, there is a need-felt to overcome at least the above-mentioned disadvantages of the prior arts.

SUMMARY OF THE INVENTION
[005] In one aspect of the present invention, a system for connecting one or more accessories to a vehicle is disclosed. The system comprises a cluster, one or more accessories and a remote server. The cluster is disposed in the vehicle. The cluster is configured to receive a request from the one or more accessories to communicatively connect with the cluster. Upon receiving such request from the one or more accessories, the cluster is further configured to accept the request for connection if the one or more accessory related protocols are provided in the cluster. Upon such connection of the cluster with the one or more accessories, the cluster is further configured to transmit a first request to the remote server for identification details of the one or more accessories and perform a first set of pre-defined operations upon satisfaction of a first set of pre-defined conditions. Upon completion of the first set of operations, the cluster is further configured to transmit a second request to the remote server for service related details of the one or more accessories and perform a second set of pre-defined operations upon satisfaction of a second set of pre-defined conditions.
[006] In an embodiment, the first set of pre-defined conditions comprises identification details of the one or more accessories received by the remote server being same as the identification details received by the cluster from the one or more accessories. The first set of pre-defined operation comprises verification of the one or more accessories by the cluster.
[007] In an embodiment, the second set of pre-defined conditions comprises service details of the one or more accessories received by the remote server being same as the service details received by the cluster from the one or more accessories. The second set of pre-defined operations comprises enabling the one or more functions of the accessories by the cluster based on the service details.
[008] In an embodiment, upon non-satisfaction of the second set of pre-defined conditions, the cluster is configured to transmit a third request to the remote server for updated service related details of the one or more accessories and perform a third set of pre-defined operations upon satisfaction of a third set of pre-defined conditions. The third set of pre-defined conditions comprises updated service details of the one or more accessories received by the remote server being same as the service details received by the cluster from the one or more accessories. The third set of pre-defined operations comprises enabling the one or more functions of the accessories by the cluster based on the service details. Upon non-satisfaction of the third set of pre-defined conditions, the cluster is configured to reject the verification of the one or more accessories.
[009] In an embodiment, the one or more accessories are selected from a group comprising a tyre pressure monitoring system, a smart watch, a smart helmet and a smart band.
[010] In an embodiment, the cluster is connected to the remote server by means of a telematics control unit.
[011] In another aspect of the invention, a method for connecting one or more accessories to a vehicle is disclosed. The method comprises a step of receiving a request from the one or more accessories to communicatively connect with the cluster. The step of receiving the request is performed by a cluster disposed in the vehicle. The method further comprises a step of accepting the request for connection upon one or more accessory related protocols being provided in the cluster. The step of accepting the request is performed by the cluster. The method further comprises a step of transmitting a first request to the remote server for identification details of the one or more accessories and performing a first set of pre-defined operations upon satisfaction of a first set of pre-defined conditions. The step of transmitting the first requested is also performed by the cluster. Upon completion of the first set of pre-defined operations, the method further comprises a step of transmitting a second request to the remote server for service related details of the one or more accessories and performing a second set of pre-defined operations upon satisfaction of a second set of pre-defined conditions. The step of transmitting the second request is also performed by the cluster.
[012] In an embodiment, the first set of pre-defined conditions comprises identification details of the one or more accessories received by the remote server being same as the identification details received by the cluster from the one or more accessories. The first set of pre-defined operation comprises verification of the one or more accessories by the cluster.
[013] In an embodiment, the second set of pre-defined conditions comprises service details of the one or more accessories received by the remote server being same as the service details received by the cluster from the one or more accessories. The second set of pre-defined operations comprises enabling the one or more functions of the accessories by the cluster based on the service details.
[014] In an embodiment, the method further comprises rejecting verification of the one or more accessories upon non-satisfaction of the first set of pre-defined conditions. The step of rejecting is performed by the cluster.
[015] In an embodiment, the method further comprises a step of transmitting a third request to the remote server for updated service related details of the one or more accessories and performing a third set of pre-defined operations upon satisfaction of a third set of pre-defined conditions. The third request is transmitted by the cluster upon non-satisfaction of the second set of pre-defined conditions. The third set of pre-defined conditions comprises updated service details of the one or more accessories received by the remote server being same as the service details received by the cluster from the one or more accessories. The third set of pre-defined operations comprises enabling the one or more functions of the accessories by the cluster based on the service details.
[016] In an embodiment, the method step further comprises rejecting the verification of the one or more accessories upon non-satisfaction of the third set of pre-defined conditions. The step of rejecting is performed by the cluster.
[017] In an embodiment, the one or more accessories are selected from a group comprising a tyre pressure monitoring system, a smart watch, a smart helmet and a smart band.
[018] In an embodiment, the cluster is connected to the remote server by means of a telematics control unit.

BRIEF DESCRIPTION OF THE DRAWINGS
[019] Reference will be made to embodiments of the invention, examples of which may be illustrated in accompanying figures. These figures are intended to be illustrative, not limiting. Although the invention is generally described in context of these embodiments, it should be understood that it is not intended to limit the scope of the invention to these particular embodiments.
Figure 1 is a block diagram illustrating a system for connecting one or more accessories to a vehicle, in accordance with an embodiment of the present invention.
Figure 2 is a flow chart illustrating a method for connecting one or more accessories to a vehicle, in accordance with an embodiment of the present invention.
Figure 3 is a flow chart illustrating a method for connecting one or more accessories to a vehicle, in accordance with another embodiment of the present invention.
Figure 4 is a flow chart illustrating a method for certifying one or more accessories, in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION
[020] Various features and embodiments of the present invention here will be discernible from the following further description thereof, set out hereunder.
[021] Figure 1 is a block diagram illustrating a system 100 for connecting one or more accessories 102 to a vehicle 10, in accordance with an embodiment of the present invention
[022] For the purpose of the present invention, the term “vehicle” comprises any vehicle capable of communicating with one or more accessories 102 as well as one or more remote servers 106 such as, not being limited to, bicycles, scooters, motorcycles, rickshaws, cars, trucks, etc. The term “vehicle” also comprises, not being limited to, conventional internal combustion engine vehicles, electric vehicles and hybrid vehicles.
[023] As shown in Figure 1, the vehicle 10 comprises one or more accessories 102, a cluster 104 and a remote server 106. The cluster 104 is disposed in the vehicle 10. The cluster 104 is capable of being connected to the one or more accessories 102 as well as to the remote server 106. In a non-limiting example, the one or more accessories 102 are a tyre pressure monitoring system, a smart watch, a smart helmet and a smart band. However, this should not be construed as limiting and various now available or later developed accessories may connect with the cluster. The cluster 104 is capable of the connecting with the remote server 106 and the one or more accessories 102 over a network. The network include wireless networks, Ethernet AVB networks, or combinations thereof. The wireless network may be a cellular telephone network. Further, the network may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed. In a non-limiting example, the one or more accessories 102 connect with the cluster 104 by means Bluetooth connection, USB connection, Wi-Fi and mobile communication. In a non-limiting example, the cluster 104 is connected to the remote server 106 by means of a telematics control unit.
[024] When the one or more accessories 102 are to be connected to the vehicle 10, the one or more accessories 102 sends a request for connection to the cluster 104 of the vehicle 10. The cluster 104 will establish a connection with the one or more accessories 102 if the protocols for connection with the one or more accessories 102 are provided in the cluster 104. In case the protocols with respect to the one or more accessories 102 trying to connect with the vehicle 10 are not provided in the cluster 104, the cluster 104 will reject the request for connection with the one or more accessories 102. Upon cluster 104 accepting the request for connection with the one or more accessories 102, the cluster 104 transmits a first request to the remote server 106 for identification details of the one or more accessories 102 and perform a first set of pre-defined operations upon satisfaction of a first set of pre-defined conditions. The identification details refer to unique information that identifies the accessory. The remote server 106 stores various details of the one or more accessories 102. Such details are stored in the remote server 106 by the vehicle manufacturer and/or the accessory manufacturer. In a non-limiting example, the first set of pre-defined operation comprises verification of the one or more accessories 102 by the cluster 104. It is to be understood the cluster 104 verifies one or more accessories 102 only upon satisfaction of the first set of pre-defined conditions which includes identification details of the one or more accessories 102 received by the remote cluster 106 being same as the identification details of the one or more accessories 102 received by the one or more accessories 102 upon connection with the cluster 104. In a non-limiting example, the cluster 104 requests the one or more accessories 102 to share the identification details upon request of connection being accepted by the cluster 104. In a non-limiting example, the identification details are automatically shared by the one or more accessories 102 upon request for connection being accepted by the cluster 104. In case the first set of conditions are not satisfied i.e. identification details of the one or more accessories 102 received by the remote server 106 are not same as the identification details of the one or more accessories 102 received by the one or more accessories 102, the cluster 104 is configured to reject the verification of the one or more accessories.
[025] Upon completion of the first set of pre-defined operations i.e. verification of the one or more accessories 102 by the cluster 104, the cluster 104 is configured to transmit a second request to the remote server 106 for service details of the one or more accessories 102 and perform a second set of pre-defined operations upon satisfaction of the second set of pre-defined conditions. The service details pertain to functionalities or services offered by the accessory. In a non-limiting example, the second set of pre-defined operations comprises enabling the one or more functions of the accessories 102 by the cluster 104. The functions of the one or more accessories 102 are enabled only upon satisfaction of the second set of pre-defined conditions which include service details of the one or more accessories 102 received from the remote server 106 being same as the service details of the one or more accessories 102 being received by the one or more accessories 102. In a non-limiting example, the cluster 104 requests the one or more accessories 102 to share the service details after verification of the one or more accessories 102 by the cluster 104. In a non-limiting example, the identification details are automatically shared by the one or more accessories 102 after verification of the one or more accessories 102 by the cluster 104.
[026] In an embodiment, when the second set of conditions are not satisfied i.e. service details of the one or more accessories 102 received from the remote server 106 are different from the service details of the one or more accessories 102 received from the one or more accessories 102, the cluster 104 may be configured to transmit a request for updated server details from the remote server 106 and perform a third set of pre-defined operations upon satisfaction of a third set of pre-defined conditions. The third set of pre-defined operation comprises enabling the functions of the one or more accessories 102 upon satisfaction of the third set of pre-defined conditions. In a non-limiting example, the third set of pre-defined operations comprises enabling the one or more functions of the accessories 102 by the cluster 104. The functions of the one or more accessories 102 are enabled only upon satisfaction of the third set of pre-defined conditions which include updated service details of the one or more accessories 102 received from the remote server 106 being same as the service details of the one or more accessories 102 being received by the one or more accessories 102. It is to be understood that upon non-satisfaction of the one or more third pre-defined conditions, the cluster 104 is configured to reject the verification of the one or more accessories 102. The updated service details are required to be checked as there may be a scenario where the accessory firmware undergoes an upgrade and updates its service list. Due to the check where services provided by the accessory 102 is verified before connecting, this situation can be tackled by refreshing the services to be discovered from the remote server 106 when there is a service list mismatch of discovered services.
[027] In a non-limiting example, the identification details of the one or more accessories 102 comprises serial number, model number, manufacturer information, firmware version, access key etc. The serial number can be a unique alphanumeric code assigned to each accessory during manufacturing. The model number can be a code or name indicating the specific model of the accessory. The manufacturer information can be information about the company that manufactured the accessory including name and contact details. The firmware version is the version of software installed in the accessory. The access key is an encrypted key provided by the manufacturer for secure authentication of the accessory. However, this should not be construed as limiting and other identification details can also be provided with respect to the accessory. The identification details collectively ensure that the accessory can be uniquely identified by the vehicle's cluster and remote server.
[028] In a non-limiting example, the service details of the one or more accessories 102 relate to status of the accessory, communication features of the accessory, safety features of the accessory, health monitoring features of the accessory, navigation features of the accessory, battery status of the accessory, firmware update of the accessory etc. For example, in case of a smart helmet, the status of the accessory will indicate whether the smart helmet is properly fitted and secured. The communication features of smart helmet can be built-in microphone and speakers for hands-free communication. The safety features of the smart helmet can be impact sensors, emergency notification system or built in light for visibility. The health monitoring features of the smart helmet may include health monitoring means for determining health related parameters of the rider of the vehicle such as heart rate or temperature of rider of the vehicle. The navigation details of a smart helmet may include Built-in GPS or augmented reality display for navigation assistance. The battery status information in the smart helmet provides information on the battery level and estimated remaining usage time. The firmware update includes services indicating whether the smart helmet supports firmware updates and provides information on the latest available version. The service details essentially specifies the capabilities and functionalities of the accessory, allowing the cluster 104 to determine which features can be enabled and utilized during the connection process.
[029] It is to be understood that one or more accessories 102 are smart accessories which can be any additional fitting on the vehicle 10 that can achieve certain function to elevate the user experience and convenience by connecting to the cluster/smart cluster 104 of the vehicle 10. The one or more accessories 102 will be implementing a predefined approved protocol, so that it can communicate with any of the clusters 104 designed around the protocol.
[030] It is to be understood that the cluster/smart cluster 104 will be the mediator for the one or more accessories 102 and the remote server 106 (for example, Original Equipment Manufacturer (OEM’s) cloud) to onboard, authenticate and tag the one or more accessories/smart accessories 102 against the user’s vehicle. Cluster 104 takes care of identifying the one or more accessories/smart accessories 102 through different connection media, managing the connection to such discovered accessories 102 and be the gateway to the vehicle 10 for the accessory 102 to display or consume some information.
[031] It is further to be understood that remote server 106 takes care of storing and distributing the identification details and the service details including onboarded accessory certificates, authenticating attached accessories on the vehicle 10, onboarding accessory manufacturer into the system, and keeping track of the services supported by the one or more accessories 102. A generic protocol to govern the one or more accessories and their attachments to the vehicle 10 is not an obvious one as each vehicle has their own set of protocols and closed system of accessories.
[032] Figure 1, as discussed above, therefore shows an overall architecture of the system 100. The major parts of the system 100 are the cloud server/remote server 106 that manages the authentication, onboarding, and a central repository of the one or more enabled accessories 102. The cluster/smart cluster 104 is the mediator between the one or more accessories 102 and the remote/server 106 and the accessory’s gateway to the vehicle 10. As already stated in the preceding paragraphs, the cluster 104 may be enabled with a Telematics Control Unit (TCU) which connects it to the internet, and other connectivity options such as, but not limited to Bluetooth, Wi-Fi, Zigbee, USB etc.
[033] It is also to be understood that accessories 102 are the wider category of smart attachments that adds on to the functionality, aesthetics, and convenience to the user by providing certain services or data. The one or more accessories 102 can connect to the cluster 104 either through wires or wirelessly and the protocol shall be made in such a way to cover the accessories 102 irrespective of their connection media.
[034] In a non-limiting example, in case of a two wheeler, an accessory 102 identifies the presence of a cluster 104 enabled with TAP (Two wheeler Accessory Protocol) and tries to initiate connection with the cluster 104. The cluster 104, upon identifying it as a TAP enabled establishes a link to carry out authorization. The accessory 102 is denied of any data or control access at this stage, until authorized. The accessory 102 then shares its identification details with the cluster 104, and the cluster 104 uses this information to fetch the certificates from the server 106. If the received certification information is valid, cluster 104 then request for the services offered by the accessory 102 that is updated in the remote server 106. Once the remote server 106 responds back with the service details, cluster 104 will try to discover the services from the accessory 102. Once the discovered services match with the one updated from the server 106, the accessory 102 is now completely authorized and is then allowed the connection and cluster 104 enables the specified service handlers in it. The cluster 104 will force a disconnection from the accessory 102 if there is a mismatch observed in the services discovered. Onboarding a new accessory details to the server 106 is accomplished following the onboarding process for the accessory 102 by the accessory OEM with the remote server 106 as discussed in Figure 4 of the present invention.
[035] Figure 2 is a flow chart illustrating a method 200 for connecting one or more accessories 102 to a vehicle 10, in accordance with an embodiment of the present invention.
[036] At step 201, the method 200 comprises receiving a request from the one or more accessories 102 to communicatively connect with the cluster 104. The step 201 is performed by the cluster 104 disposed in the vehicle 10 and capable of being communicatively coupled with the one or more accessories 102 and the remote server 106. At step 202, the method 200 comprises accepting the request for connection upon one or more accessory related protocols being provided in the cluster 104. The step 202 is performed by the cluster 104. At step 203, the method 200 comprises transmitting a first request to the remote server 106 for identification details of the one or more accessories 102 and performing a first set of pre-defined operations upon satisfaction of a first set of pre-defined conditions. The step 203 is performed by the cluster 104. The first set of pre-defined operations comprises verification of the one or more accessories 102 by the cluster 104 upon satisfaction of the one or more first pre-defined conditions including identification details of the one or more accessories 102 received by the remote server 106 being same as the identification details received by the cluster 104 from the one or more accessories 102. At step 204, the method 200 comprises transmitting, upon completion of the first set of pre-defined operations, a second request to the remote server 106 for service related details of the one or more accessories 102 and performing a second set of pre-defined operations upon satisfaction of a second set of pre-defined conditions. The second set of pre-defined operations comprises enabling the one or more functions of the one or more accessories 102 by the cluster 104 upon satisfaction of the one or more second pre-defined conditions including service details of the one or more accessories 102 received by the remote server 106 being same as the service details received by the cluster 104 from the one or more accessories 102.
[037] In an embodiment, the method 200 further comprises rejecting the verification of the one or more accessories102 by the cluster 104 upon non-satisfaction of the first set of pre-defined conditions.
[038] In an embodiment, the method 200 comprises transmitting a third request to the remote server 106 for updated service related details of the one or more accessories 102 and performing a third set of pre-defined operations upon satisfaction of a third set of pre-defined conditions. The step of transmitting the third request is performed by the cluster 104 upon non-satisfaction of the second set of pre-defined conditions. The third set of pre-defined operations comprises enabling the one or more functions of the one or more accessories 102 by the cluster 104 upon satisfaction of the third set of pre-defined conditions including updated service details of the one or more accessories 102 received by the remote server 106 being same as the service details received by the cluster 104 from the one or more accessories 102.
[039] In an embodiment, the method 200 further comprises rejecting the verification of the one or more accessories 102 by the cluster 104 upon non-satisfaction of the third set of pre-defined conditions.
[040] In an embodiment, the cluster 104 is connected to the remote server 106 by means of a telematics control unit disposed in the vehicle 10.
[041] In an embodiment, the one or more accessories 102 include, not being limited to, a tyre pressure monitoring system, a smart watch, a smart helmet and a smart band.
[042] Figure 3 is a flow chart illustrating a method 300 for connecting one or more accessories 102 to a vehicle 10, in accordance with another embodiment of the present invention.
[043] As shown, at step 301, a request for connection is initiated by the one or more accessories 102. The request for connection is transmitted to the cluster 104 disposed in the vehicle 10.
[044] At step 302, upon protocol related to the one or more accessories 102 being provided in the cluster 104, the request for connection is accepted by the cluster 104 and the one or more accessories 102 are connected to the cluster 104.
[045] At step 303, upon connection between the cluster 104 and the one or more accessories 102, identification details of the one or more accessories 102 are shared by the one or more accessories 102 with the cluster 104.
[046] At step 304, the cluster 104 will determine if the accessory is already verified. If yes, the method will go to step 305. If not, the cluster 104 will transmit a request to the remote server 106 for sharing identification details of the one or more accessories 102 and upon determination of the identification details shared by the one or more accessories 102 being same as the identification details of the one or more accessories 102 shared by the remote server 106, the cluster 104 will verify the one or more accessories 102 and move to step 305.
[047] At step 306, for enabling one or more services/functions of the one or more accessories 102, the cluster 104 will transmit a request to the one or more accessories 102 to provide the service details.
[048] At step 307, the one or more service details are transmitted to the cluster 104 by the one or more accessories 102.
[049] At step 308, the one or more service details received at step 307 are compared with the one or more service details received from the remote server 106. In case the service details received from the remote server 106 matches the service details received from the one or more accessories 102, the method moves to step 309 and step 310 wherein a communication channel is established between the one or more accessories 102 and the cluster 104/vehicle 10. However, in case the service details received from the remote server 106 does not match the service details received from the one or more accessories 102, the method moves to step 311.
[050] At step 311, the cluster 104 transmits a request to the remote server 106 for updated service details of the one or more accessories 102.
[051] At step 312, the remote server 106 transmits the updated service details of the one or more accessories 102 to the cluster 104. In case the updated service details of the one or more accessories 102 received from the remote server 106 matches the service details received from the one or more accessories 102, the method moves to step 313. In case the updated service details of the one or more accessories 102 received from the remote server 106 does not match the service details received from the one or more accessories 102, the method moves to step 314.
[052] At step 313, a communication channel is established between the one or more accessories 102 and the cluster 104/vehicle 10.
[053] At step 314, the cluster 104 rejects the verification of the one or more accessories 102 and the one or more accessories 102 are disconnected from the vehicle 10.
[054] In case the one or more accessories 102 are not verified or rejected by the cluster 104, the accessory manufacturer can follow accessory onboarding procedure as discussed in Figure 4.
[055] In a non-limiting example with respect to a two-wheeled vehicle, one or more accessories 102 identifies presence of a cluster 104 enabled with TAP and tries to initiate connection with it. The cluster 104, upon identifying it as a TAP enabled establishes a link to carry out authorization. The one or more accessories 102 are denied of any data or control access at this stage, until authorized. The one or more accessories 102, thereafter, shares its identification details with the cluster 104, and the cluster 104 uses this information to fetch the certificates from the remote server 106. If the received certification information is valid, cluster 104 then request for the services offered by the one or more accessories 102 that are updated in the remote server 106. Once the remote server 106 responds back with the service details, the cluster 104 will try to discover the services from the one or more accessories 102. Once the discovered services match with the one updated from the remote server 106, the one or more accessories 102 are now completely authorized and are allowed the connection and cluster 104 enables the specified service handlers in it. The cluster 104 will force a disconnection from the accessory 102 if there is a mismatch observed in the services discovered.
[056] Figure 4 is a flow chart 400 illustrating a method for certifying one or more accessories 102, in accordance with an embodiment of the present invention.
[057] At step 401, the accessory manufacturer will apply for a certification with accessory details. In a non-limiting example, the accessory manufacturer will apply for an automotive accessory protocol such as TAP (two-wheeler accessory protocol).
[058] At step 402, the vehicle manufacturer assigns a unique accessory identification and manufacturer identification to the accessory.
[059] At step 403, the vehicle manufacturer provided necessary software developments kits.
[060] At step 404, accessory OEM (original equipment manufacturer) submits a demonstration of accessory on the manufacturer’s development platform.
[061] At step 405 and 406, the vehicle manufacturer evaluates the products and assess the predefined quality checks and determines if the product adhering to the manufacturer’s quality standards is compatible with automotive accessory protocol/ TAP enabled vehicles. In case the manufacturer’s quality standards are compatible with automotive accessory protocol/ TAP enabled vehicles, the method moves to step 408, else 407.
[062] At step 407, feedback is given to accessory manufacturer by the vehicle manufacturer on gaps to rework.
[063] At 408, the accessory manufacture is awarded an automotive accessory protocol/ TAP certification.
[064] It is to be understood that typical hardware configuration of the cluster 104 disclosed in the present invention can include a set of instructions that can be executed to cause the cluster 102 to perform the method disclosed in Figure 2 and Figure 3.
[065] The cluster 104 may include a processor which may be a central processing unit (CPU), a graphics processing unit (GPU), or both. The processor may be one or more general processors, digital signal processors, application specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analysing and processing data. The processor may implement a software program, such as code generated manually i.e. programmed.
[066] The cluster 104 may include a memory. The memory may be a main memory, a static memory, or a dynamic memory. The memory may include, but is not limited to computer readable storage media such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like. The memory is operable to store instructions executable by the processor. The functions, acts or tasks illustrated in the figures or described may be performed by the programmed processor executing the instructions stored in the memory.
[067] The cluster 104 may also include a disk or optical drive unit. The disk drive unit may include a computer-readable medium in which one or more sets of instructions, e.g. software, can be embedded. Further, the instructions may embody one or more of the methods or logic as described. In a particular example, the instructions may reside completely, or at least partially, within the memory or within the processor during execution by the telematics unit. The memory and the processor also may include computer-readable media as discussed above. The present invention contemplates a computer-readable medium that includes instructions or receives and executes instructions responsive to a propagated signal so that a device connected to a network can communicate data over the network. Further, the instructions may be transmitted or received over the network. The network include wireless networks, Ethernet AVB networks, or combinations thereof. The wireless network may be a cellular telephone network. Further, the network may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed.
[068] The cluster 104 may accept incoming content and send content to connected components via a communication channel such as Controller Area Network (CAN), Local Interconnect Network (LIN) and Bluetooth.
[069] The claimed features/method steps of the present invention as discussed above are not routine, conventional, or well understood in the art, as the claimed features/steps enable the following solutions to the existing problems in conventional technologies. Specifically, the technical problem of smart and connected accessories for automobiles being a closed implementation and being usable only with a particular vehicle model or manufacturer is solved by the present invention.
[070] The present invention aims to democratize the accessory market in a controlled way such that end-users can reuse their accessories across different models of vehicles and accessory manufacturers can cater to a wider variety of customers and OEMs with minimal additional fittings or changes to the vehicle.
[071] The present invention allows easy and safe connection of one or more accessories across different models of vehicles which can help rider diagnose or maintain their vehicle proactively, thus keeping the performance tuned.
[072] In the present invention, a decentralized accessory repository gives an owner/rider of the vehicle to choose from the best of the available accessories and improves aesthetics of the vehicle.
[073] In the present invention, a software based smart accessory will ensure that it is easy to mount and even easier to start with.
[074] In the present invention, a seamless plug and play mode of using the accessory will add to owner’s/rider’s comfort in using the product.
[075] In the present invention, a plug and play capable accessory and vehicle will increase the market attractiveness of the product.
[076] While the present invention has been described with respect to certain embodiments, it will be apparent to those skilled in the art that various changes and modification may be made without departing from the scope of the invention as defined in the following claims.

List of Reference Numerals
10- vehicle
100- system
102- accessories
104- cluster
106- remote server/server , Claims:WE CLAIM:

1. A system (100) for connecting one or more accessories (102) to a vehicle (10), the system (100) comprising: a cluster (104), the one or more accessories (102) and a remote server (106), wherein the cluster (104) being disposed in the vehicle (10) and the cluster (104) being configured to:
receive a request from the one or more accessories (102) to communicatively connect with the cluster (104);
accept the request for connection upon one or more accessory related protocols being provided in the cluster (104);
transmit a first request to the remote server (106) for identification details of the one or more accessories (102) and perform a first set of pre-defined operations upon satisfaction of a first set of pre-defined conditions; and
transmit, upon completion of the first set of pre-defined operations, a second request to the remote server (106) for service related details of the one or more accessories (102) and perform a second set of pre-defined operations upon satisfaction of a second set of pre-defined conditions.

2. The system (100) as claimed in claim 1, wherein the first set of pre-defined conditions comprises: identification details of the one or more accessories (102) received by the remote server (106) being same as the identification details received by the cluster (104) from the one or more accessories (102).

3. The system (100) as claimed in claim 2, wherein the first set of pre-defined operations comprises verification of the one or more accessories (102) by the cluster (104).

4. The system (100) as claimed in claim 1, wherein the second set of pre-defined conditions comprises: service details of the one or more accessories (102) received by the remote server (106) being same as the service details received by the cluster (104) from the one or more accessories (102).

5. The system (100) as claimed in claim 2, wherein the second set of pre-defined operations comprises enabling the one or more functions of the accessories by the cluster (104) based on the service details.

6. The system (100) as claimed in claim 1, wherein, upon non-satisfaction of the first set of pre-defined conditions, the cluster (104) is configured to reject the verification of the one or more accessories (102).

7. The system (100) as claimed in claim 1, wherein, upon non-satisfaction of the second set of pre-defined conditions, the cluster (104) is configured to transmit a third request to the remote server (106) for updated service related details of the one or more accessories (102) and perform a third set of pre-defined operations upon satisfaction of a third set of pre-defined conditions.

8. The system (100) as claimed in claim 7, wherein the third set of pre-defined conditions comprises: updated service details of the one or more accessories (102) received by the remote server (106) being same as the service details received by the cluster (104) from the one or more accessories (102).

9. The system (100) as claimed in claim 8, wherein the third set of pre-defined operations comprises enabling the one or more functions of the accessories (102) by the cluster (104) based on the service details.

10. The system (100) as claimed in claim 7, wherein, upon non-satisfaction of the third set of pre-defined conditions, the cluster (104) is configured to reject the verification of the one or more accessories (102).

11. The system (100) as claimed in claim 1, wherein the one or more accessories (102) being selected from a group comprising: a tyre pressure monitoring system, a smart watch, a smart helmet and a smart band.

12. The system (100) as claimed in claim 1, wherein the cluster (104) being connected to the remote server (106) by means of a telematics control unit.

13. A method (200) for connecting one or more accessories (102) to a vehicle (10), the method comprising:
receiving, by a cluster (104) disposed in the vehicle (10), a request from the one or more accessories (102) to communicatively connect with the cluster (104);
accepting, by the cluster (104), the request for connection upon one or more accessory related protocols being provided in the cluster (104);
transmitting, by the cluster (104), a first request to the remote server (106) for identification details of the one or more accessories (102) and performing a first set of pre-defined operations upon satisfaction of a first set of pre-defined conditions; and
transmitting, by the cluster (104) upon completion of the first set of pre-defined operations, a second request to the remote server (106) for service related details of the one or more accessories (102) and performing a second set of pre-defined operations upon satisfaction of a second set of pre-defined conditions.

14. The method (200) as claimed in claim 13, wherein the first set of pre-defined conditions comprises: identification details of the one or more accessories (102) received by the remote server (106) being same as the identification details received by the cluster (104) from the one or more accessories (102).

15. The method (200) as claimed in claim 14, wherein the first set of pre-defined operations comprises verification of the one or more accessories (102) by the cluster (104).

16. The method (200) as claimed in claim 15, wherein the second set of pre-defined conditions comprises: service details of the one or more accessories (102) received by the remote server (106) being same as the service details received by the cluster (104) from the one or more accessories (102).

17. The method (200) as claimed in claim 16, wherein the second set of pre-defined operations comprises enabling the one or more functions of the one or more accessories (102) by the cluster (104).

18. The method (200) as claimed in claim 13, comprising:
rejecting, by the cluster (104) upon non-satisfaction of the first set of pre-defined conditions, the verification of the one or more accessories (102).

19. The method (200) as claimed in claim 13, comprising:
transmitting, by the cluster (104) upon non-satisfaction of the second set of pre-defined conditions, a third request to the remote server (106) for updated service related details of the one or more accessories (102) and performing a third set of pre-defined operations upon satisfaction of a third set of pre-defined conditions.

20. The method (200) as claimed in claim 19, wherein the third set of pre-defined conditions comprises: updated service details of the one or more accessories (102) received by the remote server (106) being same as the service details received by the cluster (104) from the one or more accessories (102).

21. The method (200) as claimed in claim 20, wherein the third set of pre-defined operations comprises enabling the one or more functions of the one or more accessories (102) by the cluster (104).

22. The method as claimed in claim 19, comprising: rejecting, by the cluster (104) upon non-satisfaction of the third set of pre-defined conditions, the verification of the one or more accessories (102).

23. The method as claimed in claim 13, wherein the one or more accessories (102) being selected from a group comprising: a tyre pressure monitoring system, a smart watch, a smart helmet and a smart band.

24. The method as claimed in claim 13, wherein the cluster (104) being connected to the remote server (106) by means of a telematics control unit.

Dated this 05th day of March 2024
TVS MOTOR COMPANY LIMITED
By their Agent & Attorney

(Nikhil Ranjan)
of Khaitan & Co
Reg No IN/PA-1471