TECHNICAL FIELD
[0001] The present disclosure relates, in general, to middleware systems. In particular, the present disclosure relates to a vehicle infotainment processing system and a method for implementing the same.
BACKGROUND
[0002] Background description includes information that may be useful in understanding the present subject matter. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed subject matter, or that any publication specifically or implicitly referenced is prior art.
[0003] Automotive passenger vehicles are increasingly equipped with various electronic entertainment and information systems, generally referred to herein as infotainment systems. For example, the infotainment systems may include automotive computational components including, but not limited to, an entertainment system, monitoring an ambient (outdoor) weather sensor, an odometer reading sensor, a trip mileage reading sensor, a radar transmitter/receiver output, a brake wear sensor, an oxygen sensor, an ambient lighting sensor, a vision system sensor, a parking sensor, a heating, venting, and air conditioning (HVAC) system and/or sensor, a water sensor, an air-fuel ratio meter, a hall effect sensor, a microphone, a radio frequency (RF) sensor, and/or an infrared (IR) sensor.
[0004] Many infotainment systems typically include a human machine interface (HMI) for enabling a user to interact with the system and vehicle. For example, the HMI may include a display for viewing messages, navigational maps, and other information. In addition, the HMI may include input controls for manipulation by a user to input commands to the infotainment system.

[0005] However, the infotainment systems are generally preconfigured with a dedicated HMI based on variants of a particular vehicle model. A single-vehicle model is generally segregated into different variants including, say, base variant, middle variant, and top variant. Each of these variants has different computational components. For example, the top variant has all computational component such as an automatic air conditioner, but the other two variants would be missing this premium computational component. Accordingly, the preconfigured HMI of the infotainment system for a vehicle variant having manual air conditioner would be different from a vehicle variant having an automatic air conditioner.
[0006] By having different preconfigured HMIs of same infotainment system for different vehicle variants, the automobile manufacturers have to design different application programs for implementing different HMIs and have to dedicate a preconfigured infotainment system for a particular variant of a vehicle model. This not only burdens the automobile manufacturers to develop different application program for each variant of different models but also limits the scope of usage of the preconfigured infotainment systems.
[0007] Accordingly, there is a need for methods and systems for providing a mechanism that can allow a custom configuration of the infotainment system during the vehicle manufacturing line assembly.
OBJECTS OF THE DISCLOSURE
[0008] Some of the objects of the present disclosure, which at least one embodiment herein satisfy, are listed hereinbelow.
[0009] A general object of the present disclosure is to provide methods and systems for providing a mechanism that can allow a custom configuration of the infotainment system during the vehicle manufacturing line assembly.
[0010] An object of the present disclosure is to provide a vehicle infotainment processing system which can custom install human machine interface (HMI)

applications in a vehicle infotainment system based on the vehicle type and available computational components on the vehicle.
[0011] Another object of the present disclosure is to design a single base HMI application so as to reduce application development effort and save digital memory which would have been used by multiple HMI applications.
[0012] These and other objects and advantages of the present invention will be apparent to those skilled in the art after a consideration of the following detailed description taken in conjunction with the accompanying drawings in which a preferred form of the present invention is illustrated.
SUMMARY
[0013] This summary is provided to introduce concepts related to a vehicle infotainment processing system and a method for implementing the same. 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 it intended to be used to limit the scope of the claimed subject matter.
[0014] The present disclosure relates to a vehicle infotainment processing system. The system includes a non-transitory storage device having embodied therein one or more routines operable to custom install human machine interface (HMI) applications in a vehicle infotainment system for computational components implemented in a vehicle, and one or more processors coupled to the non-transitory storage device and operable to execute the one or more routines. The one or more routines include a vehicle communication network controller, which when executed by the one or more processors, receives vehicle network identification tags over a vehicle communication network for the computational components implemented in the vehicle. The one or more routines further include an HMI application installation supervisor, which when executed by the one or

more processors, determines HMI applications stored in the non-transitory storage device based on the received vehicle network identification tags; retrieves the determined HMI applications from the non-transitory storage device; and installs the determined HMI applications to the vehicle infotainment system for the computational components implemented in the vehicle.
[0015] In an aspect, the vehicle communication network includes a controller area network (CAN).
[0016] In an aspect, the vehicle network identification tags are CAN message IDs.
[0017] In an aspect, the vehicle communication network controller receives a CAN message ID that identifies the vehicle type information.
[0018] In an aspect, the vehicle type information indicates a vehicle model and a particular variant of that vehicle model.
[0019] In an aspect, after initial installation of the HMI applications to the vehicle infotainment system and at an event of switching-on of an ignition switch of the vehicle, the vehicle communication network controller receives vehicle network identification tags over the vehicle communication network for the computational components implemented in the vehicle; and the HMI application installation supervisor compares the received network identification tags with the network identification tags received during the initial installation of the HMI applications; identifies a new computational component implemented in the vehicle based on the comparison; and determines and installs an HMI application to the vehicle infotainment system for the new computational component implemented in the vehicle.
[0020] The present disclosure further relates to a method for implementing a vehicle infotainment processing system. The method includes receiving, at a vehicle communication network controller, vehicle network identification tags

over a vehicle communication network for the computational components implemented in the vehicle; determining, by a human machine interface (HMI) application installation supervisor, HMI applications stored in the non-transitory storage device based on the received vehicle network identification tags; retrieving, by the HMI application installation supervisor, the determined HMI applications from the non-transitory storage device; and installing, by the HMI application installation supervisor, the determined HMI applications to the vehicle infotainment system for the computational components implemented in the vehicle.
[0021] In an aspect of the method, the vehicle communication network includes a controller area network (CAN).
[0022] In an aspect of the method, the vehicle network identification tags are CAN message IDs.
[0023] In an aspect of the method, the vehicle communication network controller receives a CAN message ID that identifies a vehicle type information.
[0024] In an aspect of the method, the vehicle type information indicates a vehicle model and a particular variant of that vehicle model.
[0025] In an aspect of the method, after initial installation of the HMI applications to the vehicle infotainment system and at an event of switching-on of an ignition switch of the vehicle, the method comprising receiving, at the vehicle communication network controller, vehicle network identification tags over the vehicle communication network for the computational components implemented in the vehicle; comparing, by the HMI application installation supervisor, the received network identification tags with the network identification tags received during the initial installation of the HMI applications; identifying, by the HMI application installation supervisor, a new computational component implemented in the vehicle based on the comparison; and determining and installing, by the

HMI application installation supervisor, an HMI application to the vehicle infotainment system for the new computational component implemented in the vehicle.
[0026] Various objects, features, aspects, and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components.
[0027] It is to be understood that the aspects and embodiments of the disclosure described above may be used in any combination with each other. Several of the aspects and embodiments may be combined to form a further embodiment of the disclosure.
[0028] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DESCRIPTION OF THE DRAWINGS
[0029] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and/or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and with reference to the accompanying figures, in which:
[0030] FIG. 1 illustrates exemplary components of a vehicle infotainment processing system, in accordance with an embodiment of the present disclosure;

[0031] FIG. 2 illustrates an exemplary block diagram depicting an exemplary implementation of an initial configuration of a vehicle infotainment system;
[0032] FIG. 3 illustrates an exemplary block diagram depicting an exemplary implementation of reconfiguration of the vehicle infotainment system;
[0033] FIG. 4 illustrates an exemplary vehicle infotainment system, in accordance with an embodiment of the present subject matter; and
[0034] FIG. 5 illustrates a method of implementing the vehicle infotainment processing system, in accordance with an embodiment of the present disclosure.
[0035] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in a computer-readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.
DETAILED DESCRIPTION
[0036] The detailed description of various exemplary embodiments of the disclosure is described herein with reference to the accompanying drawings. It should be noted that the embodiments are described herein in such details as to clearly communicate the disclosure. However, the amount of details provided herein is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the appended claims.
[0037] 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 present disclosure. Moreover, all statements herein reciting principles, aspects, and embodiments of the present disclosure, as well as specific examples, are intended to encompass equivalents thereof.
[0038] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "includes" and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and/or groups thereof.
[0039] It should also be noted that in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two figures shown in succession may, in fact, be executed concurrently or may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
[0040] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which example embodiments belong. It will be further understood that terms, e.g., those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
[0041] Embodiments and/or implementations described herein relate to methods and systems for installing human machine interface (HMI) applications in a vehicle infotainment system for one or more computational components

(features) available/mounted on a vehicle, based on network IDs of a vehicle communication network.
[0042] In an aspect, the vehicle communication network can include, but not limited to, Controller Area Network (CAN), Local Interconnect Network (LIN), and the various networks by Original Equipment Manufacturer (OEM) among others.
[0043] Taking the CAN for example, although others can also be used, CAN bus is a serial network developed primarily for use with automotive applications. CAN bus allows devices and microcontrollers in a vehicle to communicate with each other without a host computer.
[0044] CAN protocol allows various devices and microcontrollers to be connected to a single CAN bus. According to the protocol, communication along the CAN bus is message-based to allow messages and data to be sent from one connected device to another.
[0045] To facilitate communication on the CAN bus without the need of a host computer, CAN feature an arbitration-free transmission mechanism. A CAN transmission includes an arbitration field (message ID) representing the priority of the message being transmitted. A dominant bit ('0') indicates a higher priority than a recessive bit (' 1')- F°r example, in a hypothetical two-bit ID CAN network, a device sending a '10' ID will have priority over a device sending a '11' ID on the CAN bus. In this example, both devices have a recessive bit in the first bit; however, the first device has a dominant second bit which could be used to arbitrate against a recessive second bit in the second device. The second device will back-off from transmitting over the bus upon this determination in favor of the second device and will attempt to retransmit a few clock cycles after the first device has finished transmitting.

[0046] It is recognized that each message ID transmitted must be unique over the CAN bus for this arbitration-free transmission mechanism. According to the CAN specification, standard CAN (version 2.0A) uses 11-bit IDs, and extended CAN (version 2.OB) uses 29-bit IDs. Considering this as the basis of the present disclosure, embodiments and/or implementations of the present disclosure proposes a vehicle infotainment processing system 100 as shown in FIG. 1.
[0047] The system 100 includes a processor(s) 102, an interface(s) 104, and a memory 106.
[0048] The processor(s) 102 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, logic circuitries, and/or any devices that manipulate data based on operational instructions.
[0049] Among other capabilities, the one or more processor(s) 102 are configured to fetch and execute computer-readable instructions and one or more routines stored in the memory 106. The memory 106 may store one or more computer-readable instructions or routines, which may be fetched and executed to custom install human machine interface (HMI) applications in a vehicle infotainment system for computational components implemented in a vehicle. The memory 106 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.
[0050] The interface(s) 104 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) 104 may facilitate communication of the system 100 with various devices coupled to the system 100. The interface(s) 104 may also provide a communication pathway for one or more components of the system 100. Examples of such components include, but are not limited to, processing unit(s) 108 and data 110.

[0051] The processing unit(s) 108 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit(s) 108. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing unit(s) 108 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing unit(s) 108 may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing unit(s) 108. In such examples, the system 100 may 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 system 100 and the processing resource. In other examples, the processing unit(s) 108 may be implemented by electronic circuitry.
[0052] In an aspect, the processing unit(s) 108 may include a vehicle communication network controller 112 and an HMI application installation supervisor 114. The processing unit(s) 108 may include other unit(s) which may implement functionalities that supplement applications or functions performed by the system 100 or the processing unit(s) 108.
[0053] Further, the data 110 may include data that is either stored or generated as a result of functionalities implemented by any of the components of the processing unit(s) 108. In some aspects, the data 110 may be stored in the memory 106 in the form of various data structures. Additionally, data 110 can be organized using data models, such as relational or hierarchical data models. The data 110 may store data, including temporary data and temporary files, generated by the processing unit(s) 108 for performing the various functions of the system 100.

[0054] In operation, when HMI applications are to be custom installed on a vehicle infotainment system on a vehicle assembly line, the vehicle communication network controller 112, which when executed by the one or more processors 102, receives vehicle network identification tags over a vehicle communication network for the computational components implemented in the vehicle. In an aspect, not to be construed as a limitation, the vehicle communication network can be a controller area network (CAN), and the vehicle network identification tags can be CAN message IDs. Also, the computational components may include, but not limited to, an entertainment system, monitoring an ambient (outdoor) weather sensor, an odometer reading sensor, a trip mileage reading sensor, a road condition sensor, a radar transmitter/receiver output, a brake wear sensor, an oxygen sensor, an ambient lighting sensor, a vision system sensor, a ranging sensor, a parking sensor, a heating, venting, and air conditioning (HVAC) system and/or sensor, a water sensor, an air-fuel ratio meter, a microphone, a radio frequency (RF) sensor, and/or an infrared (IR) sensor.
[0055] Once the vehicle network identification tags or the CAN message IDs are received, the vehicle communication network controller 112 may receive a CAN message ID that identifies a vehicle type information 202. Based on the vehicle type information 202, a vehicle model and/or variant 204 can be ascertained by the vehicle communication network controller 112, as shown in FIG. 2
[0056] Following this, the vehicle communication network controller 112 triggers the HMI application installation supervisor 114. The HMI application installation supervisor 114, which when executed by the one or more processors 102, determines HMI applications, or vehicle model/variant-specific metadata, stored in the non-transitory storage device 106 based on the received vehicle network identification tags or the CAN message IDs.

[0057] Based on the determination, the HMI application installation supervisor 114 retrieves the determined HMI applications, or vehicle model/variant-specific metadata, in the data 110 from the non-transitory storage device 106.
[0058] Thereafter, as shown in FIG. 2, the HMI application installation supervisor 114 installs the HMI applications, specific to a particular vehicle model/variant, to a vehicle infotainment system 400 (FIG. 4) for the computational components implemented in the vehicle. As can be seen from FIG. 2, the HMI applications SW are loaded for component 1 and component N based on the determined presence of these computational components and determined vehicle model/variant.
[0059] Thus, with the implementation of the present disclosure, one base HMI software package with separate metadata for each model/variant can be loaded in the memory of the vehicle infotainment system 400. This will reduce the software development effort and saves digital memory.
[0060] Further, as and when new computational components (features/functionalities) are detected in the vehicle, the HMI application installation supervisor 114 will modify the HMI accordingly. For instance, in an aspect as shown in FIG. 3, after initial installation of the HMI applications to the vehicle infotainment system 400 and at every event of switching-on of an ignition switch of the vehicle, the vehicle communication network controller 112 receives vehicle network identification tags over the vehicle communication network for the computational components implemented in the vehicle. Thereafter, the HMI application installation supervisor 114 compares the received network identification tags with the (old) network identification tags received during the initial installation of the HMI applications. This step of comparison is performed for a specified number of times. In an example, this comparison step is performed for three times.

[0061] As shown in FIG. 3, in case it is determined based on the comparison that the computational component 2, which was earlier not present, is not implemented in the system, the HMI application installation supervisor 114 retains the previous configuration of the vehicle infotainment system 400, and determines and installs an HMI application to the vehicle infotainment system 400 for the new computational component 2 implemented in the vehicle. For instance, as shown in FIG. 4, after installation, the HMI application of the vehicle infotainment system 400 can have a status bar 402, a home screen 404, and a status indication 406 indicating that an icon b is activated for the air conditioner (AC / New Component 2) implemented in the vehicle.
[0062] In this way, the present disclosure not only provides a solution for initial configuration of the vehicle infotainment system 400 but also provides a solution for reconfiguration of the vehicle infotainment system 400. Apart from these feature, the vehicle infotainment processing system 100 can allow the vehicle owner and/or manufacturer to upgrade and/or add further application engines, upgrade the in-vehicle networking capabilities, upgrade Internet connectivity, upgrade display capabilities, and migrate to high availability capabilities, all without radical changes to the basic software environment and/or for inter- and intra-model line differentiation.
[0063] FIG. 5 illustrates a method 500 for implementing a vehicle infotainment processing system, according to an embodiment 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 deleted from the method 500 without departing from the scope of the subject matter described herein.
[0064] At block 502, the method 500 includes receiving, at a vehicle communication network controller, vehicle network identification tags over a

vehicle communication network for the computational components implemented in the vehicle. In an aspect, the vehicle communication network can be a controller area network (CAN) and the vehicle network identification tags can be CAN message IDs. Also, the computational components may include, but not limited to, an entertainment system, monitoring an ambient (outdoor) weather sensor, an odometer reading sensor, a trip mileage reading sensor, a road condition sensor, a radar transmitter/receiver output, a brake wear sensor, an oxygen sensor, an ambient lighting sensor, a vision system sensor, a ranging sensor, a parking sensor, a heating, venting, and air conditioning (HVAC) system and/or sensor, a water sensor, an air-fuel ratio meter, a hall effect sensor, a microphone, a radio frequency (RF) sensor, and/or an infrared (IR) sensor.
[0065] In an aspect, the vehicle communication network controller receives a CAN message ID that identifies a vehicle type information. The vehicle type information indicates a vehicle model and a particular variant of that vehicle model. The vehicle type information may also correspond to Vehicle Identification Number (VIN).
[0066] At block 504, the method 500 includes determining, by a human machine interface (HMI) application installation supervisor, HMI applications stored in the non-transitory storage device based on the received vehicle network identification tags.
[0067] At block 506, the method 500 includes retrieving, by the HMI application installation supervisor, the determined HMI applications from the non-transitory storage device.
[0068] At block 508, the method 500 includes installing, by the HMI application installation supervisor, the determined HMI applications to the vehicle infotainment system for the computational components implemented in the vehicle.

[0069] Further, after initial installation of the HMI applications to the vehicle infotainment system and at an event of switching-on of an ignition switch of the vehicle, the method 500 further includes the steps of receiving, at the vehicle communication network controller, vehicle network identification tags over the vehicle communication network for the computational components implemented in the vehicle; comparing, by the HMI application installation supervisor, the received network identification tags with the network identification tags received during the initial installation of the HMI applications; identifying, by the HMI application installation supervisor, a new computational component implemented in the vehicle based on the comparison; and determining and installing, by the HMI application installation supervisor, an HMI application to the vehicle infotainment system for the new computational component implemented in the vehicle.
[0070] Thus, with the implementation of the present disclosure, the present disclosure not only provides a solution for initial configuration of the vehicle infotainment system 400 but also provides a solution for reconfiguration of the vehicle infotainment system 400. Apart from these feature, the vehicle infotainment processing system 100 can allow the vehicle owner and/or manufacturer to upgrade and/or add further application engines, upgrade the in-vehicle networking capabilities, upgrade Internet connectivity, upgrade display capabilities, and migrate to high availability capabilities, all without radical changes to the basic software environment and/or for inter- and intra-model line differentiation.
[0071] 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, techniques, known, related art or later developed designs and materials should be employed. Those in the art can choose suitable manufacturing and design details.

[0072] It should be understood, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely 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 "determining," or "retrieving," or "installing," or "comparing," or the like, refer to the action and processes of an electronic control unit, or similar electronic device, that manipulates and transforms data represented as physical (electronic) quantities within the control unit's registers and memories into other data similarly represented as physical quantities within the control unit memories or registers or other such information storage, transmission or display devices. [0073] Further, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of 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 be made by those skilled in the art without departing from the scope of the present disclosure as encompassed by the following claims.
[0074] 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 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.
[0075] 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, including those that are presently unforeseen or unappreciated, and that, for example, may arise from applicants/patentees and others.

We claim

1.A vehicle infotainment processing system (100) comprising:
a non-transitory storage device (106) having embodied therein one or more routines operable to custom install human machine interface (HMI) applications in a vehicle infotainment system (400) for computational components implemented in a vehicle; and
one or more processors (102) coupled to the non-transitory storage device (106) and operable to execute the one or more routines, wherein the one or more routines include:
a vehicle communication network controller (112), which when executed by the one or more processors (102), receives vehicle network identification tags over a vehicle communication network for the computational components implemented in the vehicle; and
an HMI application installation supervisor (114), which when executed by the one or more processors (102),
determines HMI applications stored in the non-transitory storage device (106) based on the received vehicle network identification tags;
retrieves the determined HMI applications from the non-transitory storage device (106); and
installs the determined HMI applications to the vehicle infotainment system (400) for the computational components implemented in the vehicle.
2. The system (100) as claimed in claim 1, wherein the vehicle communication
network includes a controller area network (CAN).

3. The system (100) as claimed in claim 2, wherein the vehicle network identification tags are CAN message IDs.
4. The system (100) as claimed in claim 3, wherein the vehicle communication network controller receives a CAN message ID that identifies a vehicle identification number (VIN).
5. The system (100) as claimed in claim 4, wherein the vehicle type information indicates a vehicle model and a particular variant of that vehicle model.
6. The system (100) as claimed in claim 1, wherein after initial installation of the HMI applications to the vehicle infotainment system (400) and at an event of switching-on of an ignition switch of the vehicle,
the vehicle communication network controller (112):
receives vehicle network identification tags over the vehicle communication network for the computational components implemented in the vehicle; and
the HMI application installation supervisor (114):
compares the received network identification tags with the network identification tags received during the initial installation of the HMI applications;
identifies a new computational component implemented in the vehicle based on the comparison; and
determines and installs an HMI application to the vehicle infotainment system (400) for the new computational component implemented in the vehicle.

7. A method (500) for implementing a vehicle infotainment processing system
(100), the method (500) comprising:
receiving, at a vehicle communication network controller (112), vehicle network identification tags over a vehicle communication network for the computational components implemented in the vehicle;
determining, by a human machine interface (HMI) application installation supervisor (114), HMI applications stored in the non-transitory storage device (106) based on the received vehicle network identification tags;
retrieving, by the HMI application installation supervisor (114), the determined HMI applications from the non-transitory storage device (106); and
installing, by the HMI application installation supervisor (114), the determined HMI applications to the vehicle infotainment system (400) for the computational components implemented in the vehicle.
8. The method (500) as claimed in claim 7, wherein the vehicle communication network includes a controller area network (CAN).
9. The method (500) as claimed in claim 8, wherein the vehicle network identification tags are CAN message IDs.
10. The method (500) as claimed in claim 9, wherein the vehicle communication network controller receives a CAN message ID that identifies a vehicle type information.
11. The method (500) as claimed in claim 10, wherein the vehicle type information indicates a vehicle model and a particular variant of that vehicle model.

12. The method (500) as claimed in claim 7, wherein after initial installation of the HMI applications to the vehicle infotainment system (400) and at an event of switching-on of an ignition switch of the vehicle, the method comprising:
receiving, at the vehicle communication network controller (112), vehicle network identification tags over the vehicle communication network for the computational components implemented in the vehicle;
comparing, by the HMI application installation supervisor (114), the received network identification tags with the network identification tags received during the initial installation of the HMI applications;
identifying, by the HMI application installation supervisor (114), a new computational component implemented in the vehicle based on the comparison; and
determining and installing, by the HMI application installation supervisor (114), an HMI application to the vehicle infotainment system (400) for the new computational component implemented in the vehicle.