Description:FIELD OF THE DISCLOSURE
[0001] This invention generally relates to a field of user vehicle registration systems and methods, and more specifically relates to an optimized user vehicle registration data management system and method configured to fulfil gaps in user vehicle registration data receiving and processing, and handling over registration numbers to Original Equipment Manufacturers (OEMs), or users digitally and managing end to end workflow.

BACKGROUND
[0002] 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.
[0003] Regional Transport Office (RTO) is a government organisation that is responsible to keep a track of all the vehicles on Indian roads. For this purpose, every vehicle in India should be registered in the nearby RTO Office. Every vehicle that is registered will be given a vehicle registration card. Apart from vehicle registration, RTO is responsible for issuing driving licences, inspect vehicle insurance, and keep a tab of pollution created by vehicles. The RTO assigns a permanent registration number to your vehicle that you will not be allowed to change under any circumstance. As soon as one buy the vehicle, the dealer will assign a temporary registration number which is usually valid for a month. Within one month, one should get a permanent registration number for their vehicle. Apart from the above reasons, registering a vehicle is a not a choice but a legal requirement in our country. The Motor Vehicles Act, 1988 makes vehicle registration mandatory in our country. Registration of vehicle falls under this Act. According to the Act, the person cannot drive a vehicle that is not registered, and the registration number should be displayed on the vehicle at all times.
[0004] In past, there have been many system models or applications developed to ease out the vehicle registration process. One of the system models involves interactive communication between the user and server to effectively result in a plate/document/article (e.g., license plate, sticker) order for production/distribution. Generally, a communication link is established between a user computer and a registration server. A user interface is presented on the user computer. The user interface provides the user with one or more options associated with the registration of a vehicle. Interactive communication of information associated with the registration of a vehicle between the user computer and the registration server is carried out. For example, user input related to one or more of the options presented to the user by the user interface regarding the registration of a vehicle is communicated by the user to the registration server. Information to the user is provided in response to the user information from the registration server via the user interface. The result of the interactive communication between the user and the registration server is a plate/document/article order associated with the registration of the vehicle. Thereafter, the order is provided to a plate/document/article production facility. But major drawback in this system model used for the vehicle registration is that it is not able to optimize all aspects related with the vehicle registration number issuance processes. Moreover, the system model as described above is unable to minutely capture each aspect of every available process related to the vehicle registration, in every state, as well as handle all state processes along with various business models.
[0005] The other current or existing system models used for the vehicle registration process are completely manual, where dealers do the run to RTO offices to complete the registration of the vehicle. The manual process is very time expensive and cumbersome. Moreover, these current or existing system models as described above are unable to utilize strength of online process set up by government bodies.
[0006] In view of the foregoing problems as mentioned above with respect to current or existing vehicle registration system models, there is a need of an optimized user vehicle registration data management system and method that optimizes all aspects related to vehicle registration process, without requiring any need or help of a third party dealer, and is cost-effective, and saves times and efforts of the user to a great extent, while applying for the registration of the vehicle, while buying a new vehicle or selling the new vehicle. Moreover, there is also an urgent demand for the optimized user vehicle registration data management system and method which is configured to fulfil gaps in user vehicle registration data receiving and processing, and handling over registration numbers to Original Equipment Manufacturers (OEMs), or users digitally and managing end to end workflow.

OBJECTIVES OF THE INVENTION
[0007] It is an objective of the invention to provide an optimized user vehicle registration data management system configured to optimize all aspects related to vehicle registration process.
[0008] It is an objective of the invention to provide the user vehicle registration data management system configured to fulfil gaps in user vehicle registration data receiving and processing, and handling over registration numbers to Original Equipment Manufacturers (OEMs), or users digitally and managing end to end workflow.
[0009] It is an objective of the invention to provide the optimized user vehicle registration data management system configured to minimize turnaround time (TAT) of the vehicle registration process significantly.
[0010] It is an objective of the invention to provide the optimized user vehicle registration data management system which eliminates chances of all manual errors, by putting a tight process in place for data receipt and processing for the vehicle registration.
[0011] It is an objective of the invention to provide the optimized user vehicle registration data management system which is configured to enable the users have live updates on their end to end vehicle registration process.
[0012] It is an objective of the invention to provide the optimized user vehicle registration data management system which is configured to minutely capture each aspect of every available process related to the vehicle registration, in every state.
[0013] It is an objective of the invention to provide the optimized user vehicle registration data management system which is configured to handle the vehicle registration process pertaining to all state processes along with various business models.
[0014] It is an objective of the invention to provide the user vehicle registration data management method configured to fulfil gaps in user vehicle registration data receiving and processing, and handling over registration numbers to Original Equipment Manufacturers (OEMs), or to users digitally and managing end to end workflow.
[0015] It is an objective of the invention to provide the user vehicle registration data management system and the user vehicle registration data management method which is cost effective.

SUMMARY
[0016] In accordance with some embodiments of present inventive concepts, an optimized user vehicle registration data management system is claimed, which is configured to optimize all aspects related with vehicle registration for the user. These aspects related with vehicle registration for the user includes, but not limited to, process like vehicle registration data receiving, vehicle registration data processing, handling over registration numbers to Original Equipment Manufacturers (OEMs) or users digitally, and managing end to end workflow. The optimized user vehicle registration data management system comprises of an application module and an electronic device. The application module is configured to process vehicle request by the user. The application module further comprises a vehicle registration module, a tracing module, a hypothecation module, a vehicle high security registration plate (HSRP) module, an imaging sensor module, and a billing module. The electronic device comprises of a memory and a processor. The memory is configured to store the application module. The processor is communicably coupled with the application module and configured for enabling, through the vehicle registration module, vehicle dealer to receive data related with the vehicle request and user information. The processor is further configured for verifying, through the vehicle registration module, the data related with the vehicle request and the user information. The processor is further configured for downloading, through the vehicle registration module, documents based on the data related with the vehicle request and user information for processing. The processor is further configured for sending, through the tracing module, appointment to the user for signature on relevant forms based on the processed documents. The processor is further configured for uploading, through the hypothecation module, all the relevant forms signed by the user on the application module for issuance of the vehicle registration number. The processor is further configured for receiving, through the vehicle HSRP generation module, the vehicle registration number to intimate the vehicle dealer about fixation of the HSRP on the vehicle. The processor is further configured for generating, through the vehicle HSRP generation module, a vehicle registration certificate based on the vehicle registration number and the HSRP fixed on the vehicle.
[0017] In an embodiment, the processor is further configured for capturing, through the imaging sensor module, an image of the vehicle registration certificate.
[0018] In another embodiment, the billing module is configured to generate tax invoice for finalizing the HSRP by the vehicle dealer.
[0019] In accordance with some embodiments of present inventive concepts, an optimized user vehicle registration data management method is claimed, which is configured to optimize all aspects related with vehicle registration for the user. The method comprises firstly enabling, through the vehicle registration module, vehicle dealer to receive data related with the vehicle request and user information. Based on receiving of the data related with the vehicle request and the user information, the data related with the vehicle request and the user information is verified. Post verification of the data related with the vehicle request and the user information, the documents are downloaded based on the data related with the vehicle request and user information to be processed. An appointment is sent to the user for signature on relevant forms based on the processed documents. Post sending of the appointment, all the relevant forms signed by the user are uploaded on the application module for issuance of a vehicle registration number. Based on the uploaded documents on the application module, the user receives, through the vehicle HSRP generation module, the vehicle registration number, and intimates the vehicle dealer about fixation of the HSRP on the vehicle. Lastly, the method further comprises generating, through the vehicle HSRP generation module, a vehicle registration certificate based on the vehicle registration number and the HSRP fixed on the vehicle.
[0020] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

BRIEF DESCRIPTION OF THE DRAWINGS
[0021] The accompanying drawings illustrate various embodiments of systems, methods, and embodiments of various other aspects of the disclosure. Any person with ordinary skills in the art will appreciate that the illustrated element boundaries (e.g. boxes, groups of boxes, or other shapes) in the figures represent one example of the boundaries. It may be that in some examples one element may be designed as multiple elements or that multiple elements may be designed as one element. In some examples, an element shown as an internal component of one element may be implemented as an external component in another, and vice versa. Furthermore, elements may not be drawn to scale. Non-limiting and non-exhaustive descriptions are described with reference to the following drawings. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating principles.
[0022] FIG. 1 illustrates a block diagram illustrating an optimized user vehicle registration data management system, according to an embodiment of the present invention;
[0023] FIG. 2 is a block diagram illustrating an optimized user vehicle registration data management system, according to an exemplary embodiment of the present invention;
[0024] FIG. 3 is a flowchart illustrating a user vehicle registration data management method for optimizing all aspects related with the vehicle registration for the user, according to an embodiment of the present invention; and
[0025] FIG. 4 is a flowchart illustrating a workflow pipeline for optimizing aspects like vehicle registration data receiving, vehicle registration data processing, handling over registration numbers to Original Equipment Manufacturers (OEMs) or users digitally, and managing end to end workflow, according to another embodiment of the present invention.

DETAILED DESCRIPTION
[0026] Some embodiments of the disclosure, illustrating all its features, will now be discussed in detail. The words “comprising,” “having,” “containing,” and “including,” and other forms thereof, are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise. Although any systems and methods similar or equivalent to those described herein can be used in the practice or testing of embodiments of the present disclosure, the preferred, systems and methods are now described. Embodiments of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings in which like numerals represent like elements throughout the several figures, and in which example embodiments are shown. Embodiments of the claims may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. The examples set forth herein are non-limiting examples and are merely examples among other possible examples.
[0027] While the present invention is described herein by way of example using embodiments, those skilled in the art will recognize that the invention is not limited to the embodiments described, and are not intended to represent the scale of the various components. It should be understood that the detailed description thereto is not intended to limit the invention to the particular form disclosed, but on the contrary, the invention is to cover all modifications, equivalents, and alternatives falling within the scope of the present invention as defined by the appended claim. As used throughout this description, the word "may" is used in a permissive sense (i.e. meaning having the potential to), rather than the mandatory sense, (i.e. meaning must). Further, the words "a" or "an" mean "at least one” and the word “plurality” means “one or more” unless otherwise mentioned. Furthermore, the terminology and phraseology used herein is solely used for descriptive purposes and should not be construed as limiting in scope. Language such as "including," "comprising," "having," "containing," or "involving," and variations thereof, is intended to be broad and encompass the subject matter listed thereafter, equivalents, and additional subject matter not recited, and is not intended to exclude other additives, components, integers, or steps. Likewise, the term "comprising" is considered synonymous with the terms "including" or "containing" for applicable legal purposes. Any discussion of documents, acts, materials, devices, articles, and the like is included in the specification solely for the purpose of providing a context for the present invention. It is not suggested or represented that any or all of these matters form part of the prior art base or were common general knowledge in the field relevant to the present invention.
[0028] The present invention is described hereinafter by various embodiments. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiment set forth herein. Rather, the embodiment is provided so that this disclosure will be thorough and complete and will fully convey the scope of the invention to those skilled in the art. In the following detailed description, numeric values and ranges are provided for various aspects of the implementations described. These values and ranges are to be treated as examples only, and are not intended to limit the scope of the claims. In addition, a number of materials are identified as suitable for various facets of the implementations. These materials are to be treated as exemplary, and are not intended to limit the scope of the invention.
[0029] The present invention discloses an optimized user vehicle registration data management system which is configured to optimize all aspects related with vehicle registration for a user. The optimized user vehicle registration data management system is further configured to minimize turnaround time (TAT) of the vehicle registration process significantly. The optimized user vehicle registration data management system is further configured to eliminate chances of all manual errors, by putting a tight process in place for the vehicle registration. The optimized user vehicle registration data management system is further configured to enable the users have live updates on their vehicle registration process. The optimized user vehicle registration data management system is further configured to minutely capture each aspect of every available process related to the vehicle registration, in every state.
[0030] Referring to FIG. 1 illustrating a block diagram of an optimized user vehicle registration data management system (100), according to an embodiment of the present invention, the optimized vehicle registration data management system (100) comprises of an application module (102) and an electronic device (104) having a memory (106) and a processor (108). The optimized vehicle registration data management system (100) is configured to optimize all aspects related with vehicle registration for the user. These aspects related with vehicle registration for the user includes, but not limited to, process like vehicle registration data receiving, vehicle registration data processing, handling over registration numbers to Original Equipment Manufacturers (OEMs) or users digitally, and managing end to end workflow. The application module (102) further comprises a vehicle registration module (110), a tracing module (112), a hypothecation module (114), a vehicle HSRP generation module (116), an imaging sensor module (118), and a billing module (120). The application module (102) is configured to process vehicle request by the user.
[0031] In an embodiment, the electronic device (104) is for example, but not limited to, a cellular phone, a mobile device, a laptop, a personal computer, a personal digital assistant (PDA), a tablet computer, a laptop computer, an Internet of Things (IoT), a smart watch, a virtual reality device, a multiple camera system, or any other handheld device.
[0032] The memory (106) is configured to store data related with the vehicle request initiated by the user. The memory (106) is further configured to store data related with the user information. The memory (106) is further configured to store data related with the vehicle registration number. The memory (106) is further configured to store data related with the HSRP. The memory (106) is further configured to store data related with vehicle registration certificate.
[0033] In an embodiment, the memory (106) is configured to store instructions to be executed by the processor (108). The memory (106) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable memories (EEPROM). In addition, the memory (106) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (106) is non-movable. In some examples, the memory (106) may be configured to store large amounts of data information. In certain examples, a non-transitory storage medium may store data that can, over time change in nature (e.g., in Random Access Memory (RAM) or Cached Memory).
[0034] The processor (108) is communicably coupled with the application module (102), and configured for enabling, through the vehicle registration module (110), a vehicle dealer to receive data related with the vehicle request and user information. The processor (108) is further configured for verifying, through the vehicle registration module (110), the data related with the vehicle request and the user information. The processor (108) is further configured for downloading, through the vehicle registration module (110), documents based on the data related with the vehicle request and user information for processing. The processor (108) is further configured for sending, through the tracing module (112), appointment to the user for signature on relevant forms based on the processed documents. The processor (108) is further configured for uploading, through the hypothecation module (114), all the relevant forms signed by the user on the application module (102) for issuance of the vehicle registration number. The processor (108) is further configured for receiving, through the vehicle HSRP generation module (116), the vehicle registration number to intimate the vehicle dealer about fixation of the HSRP on the vehicle. The processor (108) is further configured for generating, through the vehicle HSRP generation module (116), a vehicle registration certificate based on the vehicle registration number and the HSRP fixed on the vehicle.
[0035] In an embodiment, the processor (108) is further configured for capturing, through the imaging sensor module (118), an image of the vehicle registration certificate.
[0036] In another embodiment, the processor (108) is further configured to upload the image of the vehicle registration certificate along with the signed relevant forms on the application module (102), to confirm submission of the vehicle registration certificate and the signed relevant forms.
[0037] The vehicle registration module (110) is configured to enable the vehicle dealer to receive data related with the vehicle request. The vehicle registration module (110) is configured to enable the vehicle dealer to receive the data related with the user information. The vehicle registration module (110) is further configured to verify the data related with the vehicle request. The vehicle registration module (110) is configured to verify the data related with the user information.
[0038] The tracing module (112) is configured to send appointment to the user for the signature on the relevant forms based on the processed documents.
[0039] In an embodiment, the signed relevant forms are, but not limited to, a customer acknowledgement form, an Invoice form, or any other relevant document related with the vehicle request.
[0040] The hypothecation module (114) is configured to upload all the relevant forms signed by the user on the application module (102) for issuance of the vehicle registration number.
[0041] The vehicle HSRP generation module (116) is configured to enable the user to receive the vehicle registration number, in order to intimate the vehicle dealer about fixation of the HSRP on the vehicle. The vehicle HSRP generation module (116) is further configured to generate the vehicle registration certificate based on the vehicle registration number and the HSRP fixed on the vehicle.
[0042] In an embodiment, the HSRP generation module (116) is configured to enable the user to process vehicle registration online payment, the vehicle registration online payment linked with a HSRP unique ID.
[0043] The imaging sensor module (116) is configured to capture the image of the vehicle registration certificate.
[0044] In one embodiment, the system (100) further comprises the billing module (120) configured to generate tax invoice for finalizing the HSRP by the vehicle dealer.
[0045] In another embodiment, the system (100) further comprises a vehicle registration order database (122) configured to store data related with receiving of orders for vehicle registration. The vehicle registration order database (122) is further configured to store data related with the receiving of orders for vehicle requests. The vehicle registration order database (122) is further configured to store data related with the receiving of orders for fixation of the HSRP on the vehicle. The vehicle registration order database (122) is further configured to store data related with the receiving of orders for issuance of vehicle registration certificate to users.
[0046] The application module (102), the electronic device (104), and the vehicle registration order database (122) are connected to one another over a communications network (124).
[0047] The communications network (124) may facilitate a communication link among the components of the system (100). It can be noted that the communication network (124) may be a wired and/or a wireless network. The communication network (124), if wireless, may be implemented using communication techniques such as Visible Light Communication (VLC), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE), Wireless Local Area Network (WLAN), Infrared (IR) communication, Public Switched Telephone Network (PSTN), Radio waves, and other communication techniques, known in the art.
[0048] FIG. 2 is a block diagram illustrating an optimized user vehicle registration data management system (200), according to an exemplary embodiment of the present invention. The optimized user vehicle registration data management system (200) comprises of the application module (102), the electronic device (104), and an original equipment manufacturer (OEM) (202) connected to one another over the communications network (108). The processor of the electronic device (104) is communicably coupled with the application module (102), and the processor is configured to perform certain computing operations. The processor is configured to enable through the application module (102), the OEM (202) to receive data related with the vehicle request and data related with the user information. The data related with the vehicle request includes, but not limited to, the vehicle registration number, the vehicle registration certificate, and vehicle registration request order status. The data related with the user information includes, but not limited to, the user who initiated the vehicle request through the application module (102) and the OEM (202).
[0049] In an embodiment, the OEM (202) may also be, but not limited to, a vehicle dealer, an end user or any other manufacturing company. The terms “OEM” and the “Vehicle Dealer” are intended to have the same meaning and will be now be interchangeably used through the description.
[0050] For instance, the system (200) comprises of an application window (204) running on screen of the electronic device. The application window (204) is configured to display data through the screen of the electronic device. The data refers to the data related with the vehicle request and the data related with the user information. The data related with the vehicle request displays the vehicle registration number as “KR105G2314”. The data related with the vehicle request displays the vehicle registration request order status as “SUBMITTED AT REGIONAL TRANSPORT OFFICE (RTO)”, which clearly implies that the vehicle sell or purchase order request has been submitted to the regional transport office of a particular state for approval. In this way, the system (200) of the present invention is configured to achieve a technical advantage of providing clarity on each aspect of every available process related to the vehicle registration, in every state. The data related with the user information displays the name of the user or the customer name as “PETER ADAMS”, and the name of the vehicle dealer (202) as “SIVANANDA”.
[0051] After receiving the data related with the user request and the data related with the user information, the processor is further configured to verify, through the application module (112), the data related with the vehicle request and the data related with the user information. The processor is further configured to download, through the application module (102), documents based on the data related with the vehicle request and user information for processing. The processor is further configured to send, through the application module (102), appointment to the user for signature on relevant forms based on the processed documents. The processor is further configured to upload, through the application module (102), all the relevant forms signed by the user on the application module (102) for issuance of the vehicle registration number. The processor is further configured to receive, through the application module (102), the vehicle registration number to intimate the vehicle dealer (202) about fixation of the HSRP on the vehicle. The processor is further configured to generate, through the application module (102), a vehicle registration certificate based on the vehicle registration number and the HSRP fixed on the vehicle.
[0052] FIG. 3 is a flowchart illustrating a user vehicle registration data management method (300) for optimizing all aspects related with the vehicle registration for the user, according to an embodiment of the present invention. The vehicle registration facilitated using the user vehicle registration data management method (300) can be both: either a temporary vehicle registration (TR) or a permanent vehicle registration (PR). The user vehicle registration data management method (300) disclosed in FIG. 3 will now be explained in conjunction with the user vehicle registration data management system disclosed in the FIG. 1. The user vehicle registration data management method (300) starts at step (302) and ends at step (314). Firstly, the user vehicle registration data management method (300) comprises the step of enabling (302), through the vehicle registration module (110), the vehicle dealer to receive data related with the vehicle request and user information. After receiving of the data related with the vehicle request and the user information, the method (300) further comprises the step of verifying (304), through the vehicle registration module (110), the data related with the vehicle request and the user information. The method (300) further comprises the step of downloading (306), through the vehicle registration module (110), documents based on the data related with the vehicle request and user information for processing. The method (300) further comprises the step of sending (308), through the tracing module (112), appointment to the user for signature on relevant forms based on the processed documents. The method (300) further comprises the step of uploading (310), through the hypothecation module (114), all the relevant forms signed by the user on the application module (102) for issuance of the vehicle registration number. The method (300) further comprises the step of receiving (312), through a vehicle HSRP generation module (116), the vehicle registration number to intimate the vehicle dealer about fixation of the HSRP on the vehicle. Lastly, the method (300) further comprises the step of generating (314), through the vehicle HSRP generation module (116), the vehicle registration certificate based on the vehicle registration number and the HSRP fixed on the vehicle.
[0053] In an embodiment, the method (300) further comprises enabling, through the HSRP generation module (116), the user to process vehicle registration online payment, the vehicle registration online payment linked with the HSRP unique ID.
[0054] In one embodiment, the method (300) further comprises generating, through the billing module (120) , a tax invoice for finalizing the HSRP by the vehicle dealer.
[0055] In another embodiment, the method (300) disclosing the step of generating (314), through the vehicle HSRP generation module (116), a vehicle registration certificate based on the vehicle registration number and the HSRP fixed on the vehicle further comprises capturing, through an imaging sensor module (118), an image of the vehicle registration certificate. The method (300) further comprises uploading, through the HSRP generation module (116), the image of the vehicle registration certificate along with the signed relevant forms on the application module (102), to confirm the submission of the vehicle registration certificate and the signed relevant forms.
[0056] In yet another embodiment, the signed relevant forms are, but not limited to, a customer acknowledgement form, an Invoice form, or any other relevant document related with the vehicle request.
[0057] FIG. 4 is a flowchart illustrating a workflow pipeline (400) for optimizing aspects like vehicle registration data receiving, vehicle registration data processing, handling over registration numbers to Original Equipment Manufacturers (OEMs) or users digitally, and managing end to end workflow, according to another embodiment of the present invention. The workflow pipeline (400) begins with first step of receiving (402), by the OEM (202), the data related with the user information and the data related with the vehicle request. At this point, first stage of “FAME 2” flow starts. At step (404), manual data is read from page and the vehicle registration portal named “VAHAN” is updated. Post successful updation of the “VAHAN’ portal, documents are downloaded from the “VAHAN” portal for processing at step (406). Based on the downloaded documents, an appointment is sent to the customer for Form-20 and Form-34 signatures, at step (408). At step (410), the application module (102) is configured to detect if there is a change in request for the appointment. If it is detected that there is a change in the request for the appointment, the customer revises the schedule, at step (412). Further, if it is detected that there is no change in the appointment request, a rider is then allotted who is available for visiting the customer to get physical signature of the customer on the relevant forms, at step (414). At step (416), it is detected if the rider is available and allotted. If the rider is available and allotted, the rider visits the customer and gets signature of Form 20, Form 34, and FAME 2 acknowledgement letter, at step (418). At step (420), the rider scans and uploads signed forms using the application module (102). The signed forms inclusive of the Form 20 are combined and uploaded together to the “VAHAN” portal, at step (422). At step (424), a provisional registration certificate (RC) is generated from the “VAHAN” portal for different states. Based on the generated provisional RC, the vehicle registration number is received by the customer and posted to HSRP portal, at step (426). The information related with the vehicle registration number received by the customer from the HSRP portal is used to detect through the application module (102), if the plate on the vehicle is fixed or not, at step (428). If the plate is fixed on the vehicle, a picture of the fixation is captured and uploaded using the application module (102), at step (430). Based on the picture of the fixation uploaded on the application module (102), it is being detected through the application module (102), that if the registration certificate is received by the customer, at step (432). If the RC is received by the customer, an RC image is uploaded through the application module (102), at step (434). At this point, second stage of “FAME 2” flow starts. The transportation organization or any OEM downloads the relevant uploaded documents from the application module (102), at step (436).
[0058] In an embodiment, the workflow pipeline (400) of FIG. 4 is segregated into three flows namely: a tracing flow (438), a hypothecation flow (440), and a HSRP flow (442). The tracing flow (438) comprises initially downloading, by a hub tracer, the Form 20 and tracing chassis number on the Form 20, at step (444). The traced chassis number on the Form 20 is dispatched to Knowledge Processing Outsourcing (KPO), at step (446). Upon receiving the traced Form 20, the KPO uploads the traced Form 20 on the application module (102), at step (448).
[0059] In another embodiment, the hypothecation flow (440) comprises initially downloading signed Form 34 by the bank rider, at step (450). At step (452), the bank rider gets the Form 34 signed stamped from bank. The stamped Form 34 is then uploaded using the application module (102), at step (454).
[0060] In yet another embodiment, the OEM (202) may be, but not limited to, the vehicle dealer, the transport authority, or the end user.
[0061] The user vehicle registration data management system (100) of the present invention is configured to fulfil gaps in user vehicle registration data receiving and processing, and handling over registration numbers to Original Equipment Manufacturers (OEMs), or users digitally and managing end to end workflow. The user vehicle registration data management system (100) is further configured to minimize turnaround time (TAT) of the vehicle registration process significantly. The user vehicle registration data management system (100) is further configured to eliminate chances of all manual errors, by putting a tight process in place for the vehicle registration.
[0062] The optimized user vehicle registration data management system (100) of the present invention provides technical advantage over prior existing technologies, by making the vehicle registration process smoother which is achieved by enabling the users to have live updates on their vehicle registration process. The user vehicle registration data management system (100) is further configured to minutely capture each aspect of every available process related to the vehicle registration, in every state.
[0063] Moreover, the optimized user vehicle registration data management system (100) is configured to handle the vehicle registration process pertaining to all state processes along with various business models. The user vehicle registration data management method (300) of the present invention is used to fulfil gaps in the user vehicle registration data receiving and processing, and handling over registration numbers to the Original Equipment Manufacturers (OEMs), or the users digitally and managing the end to end workflow.
[0064] Several modifications and additions are introduced to make the optimized user vehicle registration data management system (100) more tolerant to variance like change in the vehicle registration data, or change in the user information, or change in the address or state of the user, etc. in the deployed environment. Moreover, entire pipeline of the optimized user vehicle registration data management system (100) comprises independent modules combined with each other in a manner, such that each independent module work seamlessly to create a face recognition solution suite that has not been achieved by past face recognition solutions or technologies.
[0065] Various modifications to these embodiments are apparent to those skilled in the art from the description. The principles associated with the various embodiments described herein may be applied to other embodiments. Therefore, the description is not intended to be limited to the embodiments but is to be providing broadest scope of consistent with the principles and the novel and inventive features disclosed or suggested herein. Accordingly, the invention is anticipated to hold on to all other such alternatives, modifications, and variations that fall within the scope of the present invention and appended claims.

, C , Claims:We Claim:
1. An optimized user vehicle registration data management system (100) to optimize all aspects related to vehicle registration, the optimized user vehicle registration data management system (100) comprising:
an application module (102) configured to process vehicle request by a user; and
an electronic device (104) having a memory (106) and a processor (108), the memory storing the application module (102), wherein the processor (108) is communicably coupled with the application module (102), the processor (108) configured for:
enabling, through a vehicle registration module (110), vehicle dealer (202) to receive data related with the vehicle request and user information;
verifying, through the vehicle registration module (110), the data related with the vehicle request and the user information;
downloading, through the vehicle registration module (110), documents based on the data related with the vehicle request and user information for processing;
sending, through a tracing module (112), appointment to the user for signature on relevant forms based on the processed documents;
uploading, through a hypothecation module (114), all the relevant forms signed by the user on the application module (102) for issuance of the vehicle registration number:
receiving, through a vehicle HSRP generation module (116), the vehicle registration number to intimate the vehicle dealer (202) about fixation of the HSRP on the vehicle; and
generating, through the vehicle HSRP generation module (116), a vehicle registration certificate based on the vehicle registration number and the HSRP fixed on the vehicle.

2. The optimized user vehicle registration data management system (100) as claimed in claim 1, wherein the processor (108) is further configured for capturing, through an imaging sensor module (118), an image of the vehicle registration certificate.

3. The optimized user vehicle registration data management system (100) as claimed in claim 2, wherein the processor (108) is further configured to upload the image of the vehicle registration certificate along with the signed relevant forms on the application module (102), to confirm submission of the vehicle registration certificate and the signed relevant forms.

4. The optimized user vehicle registration data management system (100) as claimed in claim 3, wherein the signed relevant forms are, but not limited to, a customer acknowledgement form, an Invoice form, or any other relevant document related with the vehicle request.

5. The optimized user vehicle registration data management system (100) as claimed in claim 1, wherein the system (100) further comprises a billing module (120) configured to generate tax invoice for finalizing the HSRP by the vehicle dealer (202).

6. The optimized user vehicle registration data management system (100) as claimed in claim 1, wherein the vehicle HSRP generation module (116) is configured to enable the user to process vehicle registration online payment, the vehicle registration online payment linked with a HSRP unique ID.

7. The optimized user vehicle registration data management system as claimed in claim 1, further comprising a vehicle registration order database (122) configured to store data related to receiving order for fixation of the HSRP on the vehicle.

8. An optimized user vehicle registration data management method (300) for optimizing all aspects related to vehicle registration, comprising:
enabling (302), through a vehicle registration module (110), vehicle dealer (202) to receive data related with the vehicle request and user information;
verifying (304), through the vehicle registration module (110), the data related with the vehicle request and the user information;
downloading (306), through the vehicle registration module (110), documents based on the data related with the vehicle request and user information for processing;
sending (308), through a tracing module (112), appointment to the user for signature on relevant forms based on the processed documents;
uploading (310), through a hypothecation module (114), all the relevant forms signed by the user on the application module (102) for issuance of the vehicle registration number:
receiving (312), through a vehicle HSRP generation module (116), the vehicle registration number to intimate the vehicle dealer (202) about fixation of the HSRP on the vehicle; and
generating (314), through the vehicle HSRP generation module (116), a vehicle registration certificate based on the vehicle registration number and the HSRP fixed on the vehicle.

9. The method (300) as claimed in claim 11, wherein the step of the generating (316), through the vehicle HSRP generation module (116), the vehicle registration certificate based on the vehicle registration number and the HSRP fixed on the vehicle further comprises:
capturing, through an imaging sensor module (118), an image of the vehicle registration certificate; and
uploading, through the HSRP generation module (116), the image of the vehicle registration certificate along with the signed relevant forms on the application module (102), to confirm submission of the vehicle registration certificate and the signed relevant forms.

10. The method (300) as claimed in claim 9, wherein the signed relevant forms are, but not limited to, a customer acknowledgement form, an Invoice form, or any other relevant document related with the vehicle request.

11. The method (300) as claimed in claim 9, wherein the method further comprises a generating, through a billing module (120) , a tax invoice for finalizing the HSRP by the vehicle dealer (202).

12. The method (300) as claimed in claim 1, wherein the method (300) further comprises enabling, through the HSRP generation module (116), the user to process vehicle registration online payment, the vehicle registration online payment linked with a HSRP unique ID.

13. The method (300) as claimed in claim 1, further comprising storing, by a vehicle registration database (122), data related to receiving order for fixation of the HSRP on the vehicle.