FIELD OF DISCLOSURE
[0001] The present disclosure generally relates to user authentication and
license management. In particular, the present disclosure discloses a system and 5 a
method for providing authenticated access of an application of a vehicle
manufacturer on an in-vehicle head unit coupled to a mobile device.
BACKGROUND OF THE DISCLOSURE
[0002] The background description includes information that may be
10 useful in understanding the present disclosure. It is not an admission that any of
the information provided herein is prior art or relevant to the invention claimed in
the present disclosure, or that any publication specifically or implicitly referenced
is prior art.
[0003] In the recent years, use of smart phones has become ubiquitous.
15 Smart phones or other mobile phones can download various application programs
(“applications”) that operate on the phones. A user can utilize a user interface of
the phone to control the application and/or utilize the application in some way
(such as watching the visual display or listening to the audio output). Extending
such applications from the phone to the in-vehicle head unit has become a popular
20 feature offered by various service providers and vehicle manufacturers.
[0004] However, some applications offered by the vehicle manufacturers
can only be accessed on in-vehicle head unit manufactured by the respective
vehicle manufacturers. Also, these applications can be accessed only by a phone
of a primary user of a manufacturer’s vehicle.
25 [0005] Accordingly, there is a need of having a system and a method
which may assist leveraging more universal options of accessing the applications
offered by the vehicle manufacturers.
SUMMARY
3
[0006] This summary is provided to introduce concepts related to
providing authenticated access of an application of a vehicle manufacturer on an
in-vehicle head unit coupled to a mobile device. The concepts are further
described below in the detailed description. This summary is not intended to
identify key features or essential features of the claimed subject matter, nor is 5 s it
intended to be used to limit the scope of the claimed subject matter.
[0007] In order to overcome the above problems and to technically fulfill
the expectations of the users, an objective of the present disclosure is to provide a
new, technically advanced and improved method and system that enables primary
10 users to have authenticated access of the application offered by the vehicle
manufacturers on to in-vehicle head unit.
[0008] According to an aspect of the present disclosure, a system is
described for providing authenticated access of an application of a vehicle
manufacturer on an in-vehicle head unit coupled to a mobile device. The system
15 includes a request receive engine, an authentication verification engine, and an
application management engine. The request receive engine receives a request
from a vehicle manufacturer application running on the mobile device to access
the application of the vehicle manufacturer on the in-vehicle head unit coupled to
the mobile device, where the request comprising a user identifier corresponds to a
20 primary user of the vehicle. Once the request is received, the authentication
verification engine verifies the user identifier received from the mobile device
against user identifiers maintained at a database management system (DMS).
Upon successful verification of the user identifier, the application management
engine transmits an instruction to the vehicle manufacturer application running on
25 the mobile device for allowing access of the application features offered by the
vehicle manufacturer on the in-vehicle head unit, upon successful verification of
the user identifier.
[0009] In another aspect of the present disclosure, a method is described
for providing authenticated access of an application of a vehicle manufacturer on
30 an in-vehicle head unit coupled to a mobile device. The method includes
4
receiving, from a vehicle manufacturer application running on the mobile device
at an application server of the vehicle manufacturer, a request to access the
application of the vehicle manufacturer on the in-vehicle head unit coupled to the
mobile device, wherein the request comprising a user identifier corresponding to a
primary user of the vehicle; verifying, at the application server, the user identifie5 r
received from the mobile device against user identifiers maintained at a database
management system (DMS); and transmitting, from the application server, an
instruction to the vehicle manufacturer application running on the mobile device
for allowing access of the application features offered by the vehicle manufacturer
10 on the in-vehicle head unit, upon successful verification of the user identifier.
[00010] Other and further aspects and features of the disclosure will be
evident from reading the following detailed description of the embodiments,
which are intended to illustrate, not limit, the present disclosure.
BRIEF DESCRIPTION OF DRAWINGS
15 [00011] The illustrated embodiments of the subject matter will be best
understood by reference to the drawings, wherein like parts are designated by like
numerals throughout. The following description is intended only by way of
example, and simply illustrates certain selected embodiments of devices, systems,
and processes that are consistent with the subject matter as claimed herein,
20 wherein:
[00012] FIG. 1 illustrates an exemplary environment, wherein various
embodiments of the present disclosure can be practiced;
[00013] FIG. 2 illustrates an exemplary view for registration of a new user
for creating an account with vehicle manufacturer system;
25 [00014] FIG. 3 illustrates a system block diagram illustrating various
components, according to an embodiment of the disclosure;
[00015] FIG. 4 illustrates a system block diagram illustrating a method of
accessing an application offered by vehicle manufacturer on to an in-vehicle head
unit; and
5
[00016] FIG. 5 illustrates a method of providing authenticated access of an
application of a vehicle manufacturer on an in-vehicle head unit coupled to a
mobile device, in accordance with an exemplary implementation of the present
disclosure.
DETAILED DESCRIPTIO5 N
[00017] A few inventive aspects of the disclosed embodiments are
explained in detail below with reference to the various figures. Embodiments are
described to illustrate the disclosed subject matter, not to limit its scope, which is
defined by the claims. Those of ordinary skill in the art will recognize a number of
10 equivalent variations of the various features provided in the description that
follows.
Non-limiting Definitions:
[00018] Definitions of one or more terms that will be used in this disclosure
are described below without limitations. For a person skilled in the art, it is
15 understood that the definitions are provided just for the sake of clarity, and are
intended to include more examples than just provided below.
[00019] “Primary user” refers to a user listed as a principal driver or
principal individual who operates a particular vehicle the most. The primary user
is rated as a full-time operator for a vehicle, and may be an owner registered with
20 vehicle manufacturer, registration department, and insurance department.
[00020] “Application features” refers to access to restricted phone
applications such as navigation, music, movies, weather forecasting, news, and so
forth.
[00021] “Vehicle manufacturer applications” refers to applications
25 facilitated and governed by a respective vehicle manufacturer to provide various
features, such as online service booking, running repair request, service
reminders, accessing paid features, and so forth.
[00022] The following detailed description is provided with reference to the
figures. Exemplary, and in some case preferred, embodiments are described to
6
illustrate the disclosure, not to limit its scope, which is defined by the claims.
Those of ordinary skill in the art will recognize a number of equivalent variations
in the description that follows.
Overview:
[00023] The primary aim of the disclosure is to enable primary users t5 o
have authenticated access of an application offered by the vehicle manufacturers
on to in-vehicle head unit of any manufacturer.
[00024] Thus, with the present disclosure, a system is provided for
facilitating an authenticated access of an application of a vehicle manufacturer on
10 an in-vehicle head unit coupled to a mobile device. In an aspect, the mobile device
is coupled to the in-vehicle head unit via at least one of a universal serial bus
(USB), high definition multimedia interface (HDMI), video graphics array
(VGA), Wi-Fi, and Bluetooth. In other aspect, the application features can be
navigation, music, movies, weather forecasting, news, and so forth.
15 [00025] The system includes a request receive engine to receive a request
from a vehicle manufacturer application running on the mobile device to access
the application of the vehicle manufacturer on the in-vehicle head unit coupled to
the mobile device. In an aspect, the request comprising a user identifier
corresponds to a primary user of the vehicle. The user identifier is a phone number
20 of the mobile device and a vehicle identification number of the primary user’s
vehicle.
[00026] Once the request is received, an authentication verification engine
of the system verifies the user identifier received from the mobile device against
user identifiers maintained at a database management system (DMS). Based on
25 successful verification of the user identifier, an application management engine
transmits an instruction to the vehicle manufacturer application running on the
mobile device for allowing access of the application features offered by the
vehicle manufacturer on the in-vehicle head unit, upon successful verification of
the user identifier.
7
[00027] Thus, with the implementation of the present disclosure, any brand
in-vehicle head unit can access the application offered by the vehicle
manufacturer if the mobile device of the primary user is authenticated by a system
of the vehicle manufacturer. The system can be an application server without
departing from the scope of the present disc5 losure.
Exemplary Embodiments:
[00028] Various embodiments are further described herein with reference
to the accompanying figures. It should be noted that the description and figures
10 relate to exemplary embodiments, and should not be construed as a limitation to
the subject matter of the present disclosure. It is also to be understood that various
arrangements may be devised that, although not explicitly described or shown
herein, embody the principles of the subject matter of the present disclosure.
Moreover, all statements herein reciting principles, aspects, and embodiments of
15 the subject matter of the present disclosure, as well as specific examples, are
intended to encompass equivalents thereof. Yet further, for the sake of brevity,
operation or working principles pertaining to the technical material that is known
in the technical field of the present disclosure have not been described in detail so
as not to unnecessarily obscure the present disclosure.
20 [00029] FIG. 1 illustrates an exemplary environment 100, in which various
embodiments of the present disclosure can be practiced. The environment 100
includes a primary user’s mobile device 102, an application server 104 of the
vehicle manufacturer, and a database management system (DMS) 106 of the
vehicle manufacturer. Various examples of the mobile device 102 may be
25 considered as any processor enabled device which performs one or more
functions. An example of such a mobile device 102 include, but are not limited to,
smart phone, touch pad, or other hand held devices. The present approaches may
also be implemented in other types of mobile devices which are not mentioned
herein without deviating from the scope of the present disclosure.
8
[00030] The mobile device 102 is coupled to the application server 104
through a communication over internet 108. The communication over internet 108
may include a mobile communication network, for example, 2G, 3G or 4G mobile
communication network. Although only one mobile device is shown coupled to
communication over internet 108, a typical network may have tens or 5 hundreds of
mobile devices coupled to one another. Furthermore, the communication over
internet 108 may be coupled to one or more other networks, thereby providing
coupling between a greater number of devices. Such can be the case, for example,
when networks are coupled together via the Internet.
10 [00031] Further, the application server 104 is coupled to the DMS 106
through a communication over protected network 110. The protected network 110
may be a wireless network, a wired network or a combination thereof. The
protected network 110 may be implemented as one of the different types of
networks, such as intranet, Local Area Network (LAN), Wide Area Network
15 (WAN), the Internet, and the like. The protected network 110 may either be a
dedicated network or a shared network. The shared network represents an
association of the different types of networks that use a variety of protocols, for
example, Hypertext Transfer Protocol (HTTP), Transmission Control
Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and
20 the like, to communicate with one another. Further, the protected network 110
may include a variety of network devices, including routers, bridges, servers,
computing devices, storage devices, and the like.
[00032] As shown, a primary user uses the mobile device 102 for creating
an account at the application server 104. The primary user uses the mobile device
25 102 for creating the account at the application server 104 via a vehicle
manufacturer application 112 running on the mobile device 102.
[00033] The vehicle manufacturer application 112 may be implemented as
a combination of hardware and programming (for example, programmable
instructions) to implement one or more functionalities of the vehicle manufacturer
30 application 112. In exemplary embodiments or implementations described herein,
9
such combinations of hardware and programming may be implemented in several
different ways. For example, the programming for the vehicle manufacturer
application 112 may be processor executable instructions stored on a nontransitory
machine-readable storage medium and the hardware for the vehicle
manufacturer application 112 may include a processing resource (5 for example,
one or more processors), to execute such instructions. In the present embodiments
or implementations, the machine-readable storage medium may store instructions
that, when executed by the processing resource, implement the vehicle
manufacturer application 112. In such examples, the mobile device 102 may
10 include the machine-readable storage medium storing the instructions and the
processing resource to execute the instructions, or the machine-readable storage
medium may be separate but accessible to the mobile device 102 and the
processing resource. In other examples, the vehicle manufacturer application 112
may be implemented by electronic circuitry. In context of the current disclosure,
15 the vehicle manufacturer application 112 manages the process of creation of the
account at the application server 104 and this will be discussed below in more
detail with reference to FIG. 2.
[00034] FIG. 2 illustrates an exemplary view of registering a new primary
user for creating an account with the application server 104. Referring now to
20 FIG. 2, the primary user submits, through an interface of the vehicle manufacturer
application 112 running on the mobile device 102, a request to create an account
with the application server 104. In an aspect, the request includes user
identification information including user name 202, user email address 204, user
date of birth 206, and comprises account creation information including user
25 phone number 208, vehicle identification number 210, and vehicle registration
number 212.
[00035] The submitted request is received by an application engine 114
running at the application server 104. Upon receipt of the request, the application
server 104 fetches details about the primary user from the vehicle manufacturer
30 application 112 and verifies with the DMS 106 as user identifiers.
10
[00036] After verification, the application engine 114 transmits a phone
number of the mobile device 102 along with a message to a short message service
(SMS) gateway to further transmit a New Account One Time Password (NAOTP)
to the mobile device 102. Then, the application engine 114 prompts the primary
user over user interface of the vehicle manufacturer application 112 running 5 unning on
the mobile device to submit the NAOTP received through SMS for proceeding
with registration process. Once the NAOTP is received and validated by the
vehicle manufacturer application 112, the vehicle manufacturer application 112
transmits an intimation to the application engine 114 running on the application
10 server to create a new account for the user.
[00037] Thereafter, based on the payment or subscription of the primary
user who has created account with the application server 104, the application
server 104 manages application offered by the vehicle manufacturer for that
primary user, as described in below with reference to FIGS. 3 and 4.
15 [00038] FIG. 3 is a system 300 illustrating various components for creating
account at the application server 104 or the system 300. In an example, the system
300 is in communication with the mobile device 102 and/or with the DMS 106
and is coupled through a communication network as discussed above. Although
the DMS 106 is shown as a separate system/device, but it can be implemented as a
20 part of the system 300, without departing from the scope of the present disclosure.
Further, the system 300 may be implemented in the application server 104.
[00039] The system 300 includes one or more processor(s) 302. The one or
more processor(s) 302 may be implemented as one or more microprocessors,
microcomputers, microcontrollers, digital signal processors, central processing
25 units, logic circuitries, and/or any devices that manipulate data based on
operational instructions.
[00040] Among other capabilities, the one or more processor(s) 302 are
configured to fetch and execute computer-readable instructions stored in a
memory 304 of the system 300 or the application server 104. The memory 304
30 may store one or more computer-readable instructions, which may be fetched and
11
executed to create an account with the application server 104. The memory 304
may include any non-transitory storage device including, for example, volatile
memory such as RAM, or non-volatile memory such as EPROM, flash memory,
and the like.
[00041] The system 300 also includes an electronic interface(s) 306, or5 ,
simply, interface(s) 306. The interface(s) 306 may include a variety of interfaces,
for example, interfaces for data input and output devices, referred to as I/O
devices, storage devices, and the like. The interface(s) 306 facilitate
communication of the system 300 or the mobile device 102 with various devices
10 coupled to the mobile device 102. The interface(s) 306 may also provide a
communication pathway for one or more components of the system 300 or the
application server 104. Examples of such components include, but are not limited
to, the application engine(s) 114.
[00042] In an implementation, the application engine(s) 114 further
15 includes a request receive engine(s) 308, an authentication verification engine(s)
310, an application management engine(s) 312, and a registration engine(s) 314.
[00043] It should be noted that although the present approach has been
described in the context of the system 300 implemented in the application server
104, it may also be implemented on any other device/system with a programmable
20 memory and a processor, without deviating from the scope of the present
disclosure.
[00044] In operation, when a primary user having an intention of creating
or registering an account using the system 300 interacts with the system 300, the
registration engine(s) 314 of the system 300 displays an electronic form or
25 application form on the interface of the vehicle manufacturer application 112
running on the mobile device 102, to receive a request to create an account with
the system 300 or the application server 104. In an aspect, the request includes
user identification information including user name 202, user email address 204,
user date of birth 206, and comprises account creation information including user
12
phone number 208, vehicle identification number 210, and vehicle registration
number 212.
[00045] Upon receipt of the request, an intimation is sent to the registration
engine(s) 314 running on the application server to create a new account for the
primary 5 user.
[00046] Referring to FIG. 4, once the user account is created with the
system 300 or the application server 104, the system 300 or the application server
104 fetches details about the payment or subscription of the primary user who has
created account with the system 300 or the application server 104. Based on the
10 fetched details, the application server 104 manages application offered by the
vehicle manufacturer for that primary user when the primary user places a request
to access the application of the vehicle manufacturer on an in-vehicle head unit
402 coupled to the mobile device 102. Such a request is received by the request
receive engine(s) 308 of the system 300. In an aspect, the request includes a user
15 identifier corresponding to a primary user of the vehicle. The user identifier can
be a phone number of the mobile device and a vehicle identification number of the
user’s vehicle. In another aspect, the mobile device is coupled to the in-vehicle
head unit via at least one of a universal serial bus (USB), high definition
multimedia interface (HDMI), video graphics array (VGA), Wi-Fi, and Bluetooth.
20 [00047] Upon receipt of the said request, the authentication verification
engine(s) 310 verifies the user identifier received from the mobile device 102
against user identifiers maintained at the DMS 106. Then, upon successful
verification of the user identifier, the application management engine(s) 312
transmits an instruction to the vehicle manufacturer application 112 running on
25 the mobile device 102 for allowing access of the application features offered by
the vehicle manufacturer on the in-vehicle head unit 402.
[00048] Following the successful verification of the user identifier, the
application management engine(s) 312 transmits the phone number and a message
to a short message service (SMS) gateway to further transmit a New account one
30 Time Password (NAOTP) to the mobile device 102. Then, the application
13
management engine(s) 312 prompts the primary user over the user interface of the
vehicle manufacturer application 112 running on the mobile device 102 to submit
the NAOTP received through SMS; and receives an intimation from the vehicle
manufacturer application 112 running on the mobile device 102 that whether the
NAOTP received by the mobile device 102 matches with the NAOTP received 5 ived by
the vehicle manufacturer application 112 running on the mobile device 102. Upon
successful validation of the OTP at the vehicle manufacturer application 112
running on the mobile device 102, the application management engine(s) 312
requests the DMS 106 for providing further registration information including at
10 least one of a vehicle identification number, a vehicle registration number,
division of privilege, audio serial number, and so forth. In return to the request,
the application management engine(s) 312 receives the identification information
from the DMS 106 to authenticate verification of the user identifier for allowing
access of the application of the vehicle manufacturer on the in-vehicle head unit
15 402. In an aspect, the application features can be navigation, music, movies,
weather forecasting, news, and so forth.
[00049] Accordingly, the system 300 described herein provides an
authentication of a non-networking in-vehicle head unit and allowing access to the
application through the mobile device of a primary user of a vehicle. This system
20 300 thus allows a universal access of the application accessible through the
mobile device of a primary user of a vehicle to all brands in-vehicle head unit.
[00050] However, in an alternative implementation, in case the verification
of the user identifier is found unsuccessful by the system 300, the application
management engine(s) 312 transmits, to the mobile device 102, a message
25 indicating failure status of the request.
[00051] The verification of the user identifier can be unsuccessful in case
the primary user is not registered with the system 300 or DMS 106. Accordingly,
the application management engine(s) 312 may activate the registration engine(s)
314 to prompt the primary user to register before accessing the application
30 features offered by the vehicle manufacturer. In case the primary user wants to
14
register with the system 300, the system 300 may follow the above mentioned
process and create an account for the primary user.
[00052] FIG. 5 illustrates a method 500 illustrates a method providing
authenticated access of an application of a vehicle manufacturer on an in-vehicle
head unit 402 coupled to a mobile device 102, in accordance with an exemp5 lary
implementation of the present disclosure. The order in which the method 500 is
described is not intended to be construed as a limitation, and any number of the
described method blocks can be combined in any appropriate order to carry out
the method 500 or an alternative method. Additionally, individual blocks may be
10 deleted from the method 500 without departing from the scope of the subject
matter described herein.
[00053] The method 500 can be performed by programmed computing
devices, for example, based on instructions retrieved from the non-transitory
computer-readable medium or non-transitory computer-readable media. The
15 computer-readable media can include machine-executable or computer-executable
instructions to perform all or portions of the described method. The computer
readable media may be, for example, digital memories, magnetic storage media,
such as magnetic disks and magnetic tapes, hard drives, or optically readable data
storage media.
20 [00054] Referring to FIG. 5, the method 500 may be performed by an
application server 104 of the vehicle manufacturer. However, as can be
appreciated by those skilled in the art, the method 500 can be implemented using
any other suitable device or system.
[00055] At block 502, the method 500 includes receiving, from a vehicle
25 manufacturer application 112 running on the mobile device 102 at the application
server 104 of the vehicle manufacturer, a request to access the application of the
vehicle manufacturer on the in-vehicle head unit 402 coupled to the mobile device
102. The request includes a user identifier corresponding to a primary user of the
vehicle. The user identifier can be a phone number of the mobile device and a
30 vehicle identification number of the user’s vehicle. In an aspect, the mobile device
15
is coupled to the in-vehicle head unit via at least one of a universal serial bus
(USB), high definition multimedia interface (HDMI), video graphics array
(VGA), Wi-Fi, and Bluetooth.
[00056] At block 504, the method 500 includes verifying, at the application
server 104, the user identifier received from the mobile device 102 against 5 ainst user
identifiers maintained at a database management system (DMS) 106.
[00057] At block 506, the method 500 includes transmitting, from the
application server 104, an instruction to the vehicle manufacturer application 112
running on the mobile device 102 for allowing access of the application features
10 offered by the vehicle manufacturer on the in-vehicle head unit 402, upon
successful verification of the user identifier.
[00058] Thus, with the implementation of the method 500, the present
disclosure provides an authentication of a non-networking in-vehicle head unit
and allowing access to the application accessible on the mobile device of a
15 primary user of a vehicle. This system 300 thus allows a universal access of the
application accessible on the mobile device of a primary user of a vehicle to all
brands in-vehicle head unit.
[00059] Further, the present subject matter is disclosed herein with
reference to a server-client architecture; however, the subject matter is equally
20 applicable to authentication systems, which are in direct communication with the
user’s mobile devices.
[00060] The above description does not provide specific details of the
manufacture or design of the various components. Those of skill in the art are
familiar with such details, and unless departures from those techniques are set out,
25 techniques, known, related art or later developed designs and materials should be
employed. Those in the art are capable of choosing suitable manufacturing and
design details.
[00061] Note that throughout the disclosure, numerous references may be
made regarding servers, services, engines, modules, interfaces, portals, platforms,
16
or other systems formed from computing devices. It should be appreciated that the
use of such terms are deemed to represent one or more computing devices having
at least one processor configured to or programmed to execute software
instructions stored on a computer-readable tangible, non-transitory medium or
also referred to as a processor-readable medium. For example, a server 5 erver can
include one or more computers operating as a web server, database server, or
another type of computer server in a manner to fulfil described roles,
responsibilities, or functions. Within the context of this document, the disclosed
devices or systems are also deemed to comprise computing devices having a
10 processor and a non-transitory memory storing instructions executable by the
processor that cause the device to control, manage, or otherwise manipulate the
features of the devices or systems.
[00062] It should be understood, however, that all of these and similar
terms are to be associated with the appropriate physical quantities and are merely
15 convenient labels applied to these quantities. Unless specifically stated otherwise,
as apparent from the discussion herein, it is appreciated that throughout the
description, discussions utilizing terms such as “receiving,” or “verifying,” or
“transmitting,” or the like, refer to the action and processes of a computer system,
or similar electronic computing device, that manipulates and transforms data
20 represented as physical (electronic) quantities within the computer system's
registers and memories into other data similarly represented as physical quantities
within the computer system memories or registers or other such information
storage, transmission or display devices.
[00063] The exemplary embodiment also relates to an apparatus for
25 performing the operations discussed herein. This apparatus may be specially
constructed for the required purposes, or it may comprise a general-purpose
computer selectively activated or reconfigured by a computer program stored in
the computer. Such a computer program may be stored in a computer-readable
storage medium, such as, but is not limited to, any type of disk including floppy
30 disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories
17
(ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or
optical cards, or any type of media suitable for storing electronic instructions, and
each coupled to a computer system bus.
[00064] Further, the terminology used herein is for the purpose of
describing particular embodiments only and is not intended to be limiting of 5 f the
disclosure. It will be appreciated that several of the above-disclosed and other
features and functions, or alternatives thereof, may be combined into other
systems or applications. Various presently unforeseen or unanticipated
alternatives, modifications, variations, or improvements therein may subsequently
10 be made by those skilled in the art without departing from the scope of the present
disclosure as encompassed by the following claims.
[00065] The claims, as originally presented and as they may be amended,
encompass variations, alternatives, modifications, improvements, equivalents, and
substantial equivalents of the embodiments and teachings disclosed herein,
15 including those that are presently unforeseen or unappreciated, and that, for
example, may arise from applicants/patentees and others.
[00066] It will be appreciated that variants of the above-disclosed and other
features and functions, or alternatives thereof, may be combined into many other
different systems or applications. Various presently unforeseen or unanticipated
20 alternatives, modifications, variations, or improvements therein may be
subsequently made by those skilled in the art which are also intended to be
encompassed by the following claims.

We claim:
1. A system (300) for providing authenticated access of an application of a
vehicle manufacturer on an in-vehicle head unit (402) coupled to a mobile
device (102), the system (300) comprising:
a request receive engine (308) to receive a request from a vehicl5 e
manufacturer application running on the mobile device (102) to access the
application of the vehicle manufacturer on the in-vehicle head unit (402)
coupled to the mobile device (102), wherein the request comprising a user
identifier corresponding to a primary user of the vehicle;
10 an authentication verification engine (310) to verify the user identifier
received from the mobile device (102) against user identifiers maintained at a
database management system (DMS) (106); and
an application management engine (312) to transmit an instruction to
the vehicle manufacturer application running on the mobile device (102) for
15 allowing access of the application features offered by the vehicle
manufacturer on the in-vehicle head unit (402), upon successful verification
of the user identifier.
2. The system (300) as claimed in claim 1, wherein the mobile device (102) is
coupled to the in-vehicle head unit (402) via at least one of a universal serial
20 bus (USB), high definition multimedia interface (HDMI), video graphics
array (VGA), Wi-Fi, and Bluetooth.
3. The system (300) as claimed in claim 1, wherein the user identifier is a phone
number of the mobile device (102) and a vehicle identification number of the
primary user’s vehicle.
25 4. The system (300) as claimed in claim 3, wherein after the successful
verification of the user identifier, the application management engine (312) is
to:
19
transmit the phone number and a message to a short message service
(SMS) gateway to further transmit a One Time Password (OTP) to the mobile
device (102);
prompt the primary user over a user interface of the vehicle
manufacturer application running on the mobile device (102) to submit 5 the
OTP received through SMS;
receive an intimation from the vehicle manufacturer application running
on the mobile device (102) that whether the OTP received by the mobile
device (102) matches with the OTP received by the vehicle manufacturer
10 application running on the mobile device (102);
upon successful validation of the OTP at the vehicle manufacturer
application running on the mobile device (102), request the DMS (106) for
providing further registration information including at least one of a vehicle
identification number, a vehicle registration number, division of privilege,
15 and audio serial number; and
receive the requested identification information from the DMS (106) to
authenticate verification of the user identifier for allowing access of the
application of the vehicle manufacturer on the in-vehicle head unit (402).
5. The system (300) as claimed in claim 1, wherein the application management
20 engine (312) is to transmit, to the mobile device (102), a message indicating
failure status of the request when the verification of the user identifier is
unsuccessful.
6. The system (300) as claimed in claim 5, further comprising a registration
engine (314) to:
25 receive, from the vehicle manufacturer application running on the
mobile device (102), a request to create an account with the system (300) of
the vehicle manufacturer, wherein the request comprises user identification
information including user name, user email address, user date of birth, and
20
comprises account creation information including user phone number, vehicle
identification number, and vehicle registration number;
transmit a phone number and a message to a short message service
(SMS) gateway to further transmit a New Account One Time Password
(NAOTP) to the mobile device 5 ice (102);
prompt the primary user over user interface of the vehicle manufacturer
application running on the mobile device (102) to submit the NAOTP
received through SMS for proceeding with registration process; and
upon successful validation of the NAOTP at the vehicle manufacturer
10 application running on the mobile device, create the account of the user with
the system of the vehicle manufacturer.
7. The system (300) as claimed in claim 1, wherein the system (300) is an
application server of a vehicle manufacturer.
8. The system (300) as claimed in claim 1, wherein the application features
15 include navigation, music, movies, weather forecasting, news features offered
by the vehicle manufacturer.
9. A method (500) for providing authenticated access of an application of a
vehicle manufacturer on an in-vehicle head unit (402) coupled to a mobile
device (102), the method (500) comprising:
20 receiving (502), from a vehicle manufacturer application running on the
mobile device (102) at an application server of the vehicle manufacturer, a
request to access the application features offered by the vehicle manufacturer
on the in-vehicle head unit (402) coupled to the mobile device (102), wherein
the request comprising a user identifier corresponding to a primary user of the
25 vehicle;
verifying (504), at the application server, the user identifier received
from the mobile device (102) against user identifiers maintained at a database
management system (DMS) (106); and
21
transmitting (506), from the application server, an instruction to the
vehicle manufacturer application running on the mobile device (102) for
allowing access of the application features offered by the vehicle
manufacturer on the in-vehicle head unit (402), upon successful verification
5 of the user identifier.
10. The method (500) as claimed in claim 9, wherein the mobile device (102) is
coupled to the in-vehicle head unit (402) via at least one of a universal serial
bus (USB), high definition multimedia interface (HDMI), video graphics
array (VGA), Wi-Fi, and Bluetooth.
10 11. The method (500) as claimed in claim 9, wherein the user identifier is a phone
number of the mobile device (102) and a vehicle identification number of the
user’s vehicle.
12. The method (500) as claimed in claim 9, wherein after the successful
verification of the user identifier, the method comprising:
15 transmitting, from the application server, the phone number and a
message to a short message service (SMS) gateway to further transmit a One
Time Password (OTP);
prompting the primary user over a user interface of the vehicle
manufacturer application running on the mobile device (102) to submit the
20 OTP received through SMS;
receiving, at the application server, an intimation from the vehicle
manufacturer application running on the mobile device that whether the OTP
received by the mobile device (102) matches with the OTP received by the
vehicle manufacturer application running on the mobile device (102);
25 upon successful validation of the OTP at the vehicle manufacturer
application running on the mobile device (102), requesting the DMS (106) for
providing further registration information including at least one of a vehicle
identification number, a vehicle registration number, division of privilege,
and audio serial number; and
22
receiving the requested identification information from the DMS (106)
to authenticate verification of the user identifier for allowing access of the
application features offered by the vehicle manufacturer on the in-vehicle
head unit (402).
13. The method (500) as claimed in claim 9, further comprising transmitti5 ng,
from an application server to the mobile device (102), a message indicating
failure status of the request when the verification of the user identifier is
unsuccessful.
14. The method (500) as claimed in claim 13, further comprising:
10 receiving, from the vehicle manufacturer application running on the
mobile device (102), a request to create an account with the system (300) of
the vehicle manufacturer, wherein the request comprises user identification
information including user name, user email address, user date of birth, and
comprises account creation information including user phone number, vehicle
15 identification number and vehicle registration number;
transmitting a phone number and a message to a short message service
(SMS) gateway to further transmit a One Time Password (OTP) to the mobile
device (102);
prompting the primary user over user interface of the vehicle
20 manufacturer application running on the mobile device (102) to submit the
NAOTP received through SMS for proceeding with registration process; and
upon successful validation of the NAOTP at the vehicle manufacturer
application running on the mobile device (102), creating the account of the
primary user with the system of the vehicle manufacturer.
25 15. The method (500) as claimed in claim 9, wherein the application features
include navigation, music, movies, weather forecasting, news features offered
by the vehicle manufacturer.