JP4892933B2 - Multimedia equipment for vehicles - Google Patents

Description

  The present invention relates to a vehicular multimedia apparatus, and more particularly to a vehicular multimedia apparatus in which a plurality of functions constituting the multimedia can be easily implemented and changed.

  2. Description of the Related Art Multimedia devices in which car navigation, music, video playback devices, and the like are integrally mounted on a vehicle are provided. Each function installed in the multimedia device is provided by executing application software on the OS (see, for example, Patent Document 1).

  FIG. 1 shows a functional configuration diagram of a conventional car navigation apparatus. Developed in Java without depending on a specific CPU or OS by incorporating Java virtual machine (VM) software (Java is a registered trademark) with a CPU as hardware and an OS executed by this CPU as a basic platform. Program can be executed. JavaVM has a Java standard API, and various data processing can be executed by calling this API on the application side.

The navigation program that runs on JavaVM has the functions necessary for navigation, ie, route search function, guidance support function (such as guidance at the intersection of recommended routes and speed warning when entering a curved road), map data access function, screen / map The display functions are separated from each other in a single unit, and exist independently. Each function is interposed between an application program that provides various services to the user using map data and the Java virtual machine. When the application program uses the basic functions of navigation, these functions Call and use the function. The interface between the application and each function is standardized. Therefore, even if the application program has no knowledge of the format of the map data, for example, the map data can be easily obtained by using the standardized interface. It can be used. In addition, since the basic navigation functions exist separately and independently, for example, when it becomes necessary to improve a part of the route search function, the route search is performed without affecting other functions. Only the function program needs to be corrected, and the correction can be made in a short time.
JP 2001-235334 A

However, in the configuration as shown in FIG. 1, each functional module has an interface and a function mounting unit integrally, so even if only the interface with the application is modified without changing the logic of the function mounting unit. It becomes necessary to update the whole. When updating a functional module, the update module is often distributed using a public line. However, if the entire functional module is distributed, the communication cost becomes excessive.
In addition, in the case of a multimedia device having an application that provides functions such as voice as well as navigation, since there is no function for controlling a plurality of applications, the plurality of applications cannot be switched and executed.

  In addition, since a plurality of applications have complicated dependency relationships and a uniform specification for addition of applications has not been determined, it is difficult to add applications. In addition, depending on the dependency relationship between a plurality of applications, other applications need to be corrected.

  In view of the above problems, an object of the present invention is to provide a vehicular multimedia device in which each function of an application can be easily changed and corrected.

In view of the above problems, the present invention provides position information acquisition means for acquiring position information, media data acquisition means for acquiring media data, output means for outputting audio or video, and operation input means for receiving operations. A multimedia device for a vehicle in which an application component having a navigation function, a voice / video playback function, or a function of providing an external communication interface operates, and a program storage unit for storing a program A platform composed of hardware resources including a central processing unit and an operating system executed by the central processing unit, a virtual machine realized by the central processing unit on the platform, and a central processing unit realized by using the virtual machine A plurality of said application components In response to the call content from bets, the have a common application interface regardless of the function registration state, start state, stop state, the abnormal state and the operating state of the application components with each operating state of the updating state Control means for individually controlling the function, and a function implementation unit corresponding to each of the plurality of application components executed by the central processing unit on the platform, and the control means requests processing start from the application components. Is received, the operation state of the instructed application component is controlled to a start state, the application component in the start state starts processing by the function mounting unit corresponding to the function, and the function mounting unit Before processing result for Providing the application components, to provide a car multimedia apparatus, characterized in that.

  According to the present invention, since a plurality of application components can be independently changed, it is possible to provide a vehicular multimedia device in which each function of the application can be easily changed or corrected. The application component in the claims may include an interface component.

  In one embodiment of the present invention, the function implementation unit is realized by executing a program written in a language dependent on the platform, and the application component is a program written in a language executable by the virtual machine. It is realized by executing.

According to the present invention, the platform-independent portion is described in a hardware-independent language such as Java (registered trademark), so that high compatibility can be secured on various platforms, and the platform-dependent portion is optimal for the platform. Therefore, it is possible to improve processing contents and processing speed.

In one embodiment of the present invention, when the application component receives provision of the processing result from the function implementation unit, the application component notifies the control unit of identification information and an operation state of the application component, and the control unit Controls the notified application component to the notified operation state, and the function implementation unit provides the application component with a processing result for a processing request corresponding to the function from the application component. And

  According to the present invention, when executing some function, the control means controls the operation state of the application component, so that a plurality of applications can be switched and executed.

In one embodiment of the present invention, the plurality of application components have a common application interface for starting or stopping the application components, and the control means is configured to use the application components via the common application interface. It is characterized by controlling.

  According to the present invention, since the control unit controls each component through the common interface, the developer can create an application by describing the common interface without knowing the configuration of the function implementation unit.

In one embodiment of the present invention, the control unit applies a start process to the application component that is in a registered state after being installed, thereby transitioning to a start state and stopping the application component in the start state. It is characterized in that a transition is made to a stopped state by applying a process, and a transition to the started state is made by applying a start process to the application component in the stopped state .

  According to the present invention, the control unit can control the transition of the operation state such as the registration state, the start state, or the stop state of the application component, so that necessary components can be appropriately executed.

Further, in one aspect of the present invention, the control unit performs an update process on the application component in the stopped state, transitions to the updating state, and performs an uninstall process on the application component in the registered state. It is characterized by making a transition to an unregistered state .

  According to the present invention, the control unit controls start, stop, installation, uninstallation, and the like, so that the component can be dynamically installed or uninstalled.

  It is possible to provide a vehicular multimedia device in which each function of an application can be easily changed and corrected.

  The best mode for carrying out the present invention will be described below with reference to the drawings. FIG. 2 is a configuration diagram of the vehicle multimedia apparatus according to the present embodiment. The GPS 11 detects the current position of the vehicle based on a signal from a GPS satellite and supplies the detected position to the control device 10. The sensor 12 includes a vehicle speed sensor, a gyro sensor, and the like, and supplies a detection value to the control device 10. The disc player 13 reads out DVD or CD data, and outputs video and music from the output device 17. The television / radio unit 14 receives UHF and VHF television broadcast waves and terrestrial digital broadcasts, and outputs video and music from the output device 17. In addition, AM and FM broadcasts and terrestrial digital radio broadcasts are received, and music and the like are output from the output device 17. The television / radio unit 104 may receive radio waves from the quasi-zenith satellite. The communication unit connects to a base station or an access point by mobile communication such as a mobile phone or PHS, or a wireless LAN, and supplies information acquired from the network to the control device 10. Further, traffic jam information and other traffic information accumulated in the information center is acquired by a beacon or the like and supplied to the control device 10.

  The control device 10 is a control device for controlling the vehicle multimedia device, and includes a CPU, a ROM, a RAM, an NVRAM, and the like. The CPU executes an OS, Java VM, program, and the like stored in the storage device 16 to realize a multimedia function such as car navigation. The storage device 16 includes a hard disk drive, a rewritable optical disk, a flash memory, and the like, and stores the OS and the like, map data, files, programs, and the like.

  The output device 17 is composed of a speaker, a liquid crystal display, etc., and outputs voice guidance, music, etc. of the navigation system from the speaker, outputs map data, DVD, TV images on the display, and displays an operation menu for operation. To do. The operation device 22 includes a keyboard and a mouse, and is operated by a user to input a navigation destination and a waypoint, to select a television or radio, and to switch between a car navigation system and a television. A microphone may be provided and operated by voice.

  The control device 10 provides each function of the vehicle multimedia device by executing a predetermined program installed in the storage device 16. FIG. 3 shows an example of a system configuration diagram of the vehicle multimedia apparatus of the present embodiment. As shown in FIG. 3, the program of the vehicle multimedia apparatus is executed on a platform 21 including hardware and an OS.

  On the platform 21, first, a middleware function implementation unit (hereinafter simply referred to as a function implementation unit) 22 is executed. The function implementation unit 22 is a plurality of middleware modules that implement navigation, map / screen display, voice recognition / synthesis, music / video playback, communication, and other functions as a plurality of functions required for each in-vehicle device. The middleware module is a program that depends on the OS of the platform 21.

  A plurality of interface components (hereinafter referred to as I / F components) 24 converts the functions provided by the function implementation unit 22 into functions defined in a format independent of the platform 21 so that the functions can be used from a plurality of application components. .

  An application component (hereinafter referred to as an application component) 25 uses a function provided by the function implementation unit 22 converted by the I / F component 24, and functions requested by the application components and processes requested by user operations. Get the result.

  In FIG. 3, the application component 25 is described as one, but actually, the application component 25 is also composed of a plurality of I / F components corresponding to each function of the I / F component 24. As will be described later, when the component management framework 23 is called from the application component 25 or the I / F component 24, there is no clear distinction between the application component 25 and the I / F component 24.

  The component management framework (hereinafter referred to as component management FW) 23 is a control means for the vehicle multimedia device to use the functions provided by the function implementation unit 22, and the component management FW 23 is designated as the application component 25. The later-described component package is called to control its operation state. The component management FW 23 is configured not to depend on the platform 21.

  In this way, by adding a part that depends on the platform and a part that does not depend on the platform, and the component management FW 23 manages and controls the I / F component 24 and the application component 25, it is possible to easily add / update functions. it can.

  The system configuration will be described in detail. FIG. 4 is a system configuration diagram in which navigation functions are extracted from the system configuration of FIG. 4 that are the same as those in FIG. 3 are given the same reference numerals, and descriptions thereof are omitted.

  In FIG. 4, the platform 21 including hardware and OS is the same as that in FIG. 3, but a navigation function mounting unit 22 a corresponding to the function mounting unit 22 in the navigation function is described on the OS. Since the navigation function implementation unit 22a depends on (may be) the platform 21, for example, a program is described in the native code of the platform 21 such as C / C ++.

  On the other hand, the component management FW 23 and the I / F component 24 that do not depend on the platform 21 are preferably described in, for example, a Java language. Therefore, the component management FW 23 and the I / F component 24 operate the program on the Java virtual machine (Java VM). By describing in the Java language, the component management FW 23 and the I / F component 24 do not depend on the platform 21 and can be executed on other platforms on which the Java VM operates. The I / F component 24 in the navigation function is referred to as a navigation I / F 24a.

  The navigation application component 25a sends a “designated point information acquisition request” and a “route search request to the designated point” to the navigation I / F 24a. In addition, the point information and the route information acquired by the navigation function implementation unit 22a in response to these requests are received from the navigation I / F 24a.

  The navigation function implementation unit 22a and the navigation I / F 24a are connected by a JNI (Java Native Interface). JNI is an API (Application) for using a native code program (navigation function implementation unit 22a in FIG. 4) developed from a program developed in the Java language (navigation I / F 24a in FIG. 4). Interface). In this case, JNI is created by Java and C / C ++. The navigation function implementation unit 22a and the navigation I / F 24a can exchange data with each other via the JNI.

  The navigation function implementation unit 22a has a point information providing function 32 and a route search function 33 programmed with a native code. The point information providing function 32 is a function for converting latitude and longitude obtained by, for example, GPS into an address. The route search function 33 is a function for searching for routes of two points based on the map data.

  The navigation I / F 24 a includes a point information I / F 35 corresponding to the point information providing function 32 and a route search I / F 34 corresponding to the route search function 33. The point information I / F 35 converts the point information obtained by the point information providing function 32 into a format independent of the platform 21. Similarly, the route search I / F 34 converts the route information obtained by the route search function 33 into a format independent of the platform 21.

  The I / F component 24 and the function mounting unit 22 are thus divided into appropriate functional units. In FIG. 4, only the point information and the route search are described, but the same applies to other cases.

  With such a configuration, the function implementation unit 22 that depends on the platform 21 can provide high-speed and high-function functions with native code, and the application component 25 and the I / F component 24 do not depend on the platform 21. These updates and corrections can be easily performed.

  The transition of the operation state of the I / F component 24 will be described. The component management FW 23 controls these operation states and transitions when the I / F component 24 is started, stopped, installed, uninstalled, updated, or the like.

  FIG. 5 shows a transition diagram of the operation state of the I / F component 24 managed by the component management FW 23. FIG. 5 shows that the I / F component FW 23 can take an operation state of an unregistered state, a registered state, a start state, a stop state, an abnormal state, and an updating state.

  The unregistered state refers to a state where a predetermined I / F component is stored in the storage device 16 or a state where it is downloaded but not yet installed. Such a state occurs when an initial state of the vehicle or a desired I / F component is downloaded.

  The registered state refers to a state in which the vehicle multimedia device is installed, that is, a state that can be immediately executed by a request from the application component 25. The registered state and the unregistered state can transition in both directions.

  The start state indicates that the I / F component is being executed. Specifically, this is a state in which Start () of a common interface described later is called. For example, this is a case where the I / F component 24 requests the function mounting unit 22 for processing and waits for a processing result.

  The stopped state is, for example, a state in which the processing result of the function mounting unit 22 is received and returned to the application component 25, that is, a state in which a desired process is completed. Specifically, this is a state in which Stop () of a common interface described later is called.

  The stop state and the start state can be changed in both directions. For example, an I / F component in the stop state changes to an unregistered state by an uninstall instruction.

  The abnormal state refers to a state that occurs when the I / F component in the start state cannot execute normal processing. For example, exception processing has occurred such as when the processing result is not sent from the function implementation unit 22 (timeout) or when the operation state information itself is lost.

  The updating state is a state in which the I / F component is being updated. For example, a new function is being downloaded using the communication unit 15. If, for example, a communication error occurs in the updating state and updating is not completed normally, the state is changed to an abnormal state. In addition, the updating state and the stopped state can be changed in both directions.

  The component management FW 23 controls the operation state of each I / F component 24 and manages the operation state as shown in FIG. For example, if an installation instruction is issued to an unregistered I / F component, it is installed and transitions to a registered state. If an uninstall instruction is issued to the registered I / F component, it is uninstalled and transitions to an unregistered state. If a start instruction is issued to the registered I / F component, a transition is made to the start state. If a stop instruction is issued to the I / F component in the start state, a transition is made to the stop state. If a start instruction is issued to an I / F component in a stopped state, a transition is made to the start state. If an UPDATE instruction is issued to an I / F component in a stopped state, a transition is made to the updating state. If the update is completed normally, the state transits to the stopped state. If an exception process occurs in the start state or the updating state, the state transits to an abnormal state.

  Next, control of the operation state of the application component 25a or the navigation I / F 24a will be described.

  When any processing is requested from the application component 25a, first, the component management FW 23 receives the processing request. Then, the component management FW 23 designates the I / F component designated from the plurality of I / F components 24 based on the requested processing contents, and starts the processing.

  FIG. 6 shows an example of a component package showing the configuration of the I / F component 24. As described above, since the component package provides an interface to the application component 25, it can be used in common with the application component 25, and the component package may be expressed as the configuration of the application component 25.

  The component package has a component information file 41, a program code 43, and other data 42 required by the program. The component information file is information indicating component properties such as a component identifier, a component version, and a component creator. The component identifier is an identification number that is not duplicated in the I / F component 24.

  In addition, the program code has a start () and a stop () which are common interfaces (hereinafter simply referred to as a common I / F) common to all I / F components 24 as an essential configuration. The component management FW 23 controls the operation state of each I / F component by calling this common I / F.

  Since the common I / F (start () or stop ()) cannot be called from other than the component management FW 23, the operation state of each I / F component is controlled by the component management FW 23.

  The externally provided function interface of the program code 43 is, for example, an interface that allows a system administrator (manufacturer) to call the component package from other than the component management FW 23, and has an arbitrary configuration.

  The internal processing logic is a program code describing a function specific to the component package. If the navigation I / F 24a is used, the internal processing logic is a program code for passing a designated point information acquisition request to the navigation function mounting unit 22a.

  The other data has an arbitrary configuration in which data necessary for the component package, a still image to be displayed to the user, and the like are stored.

  The component management FW 23 controls the operation state of the I / F component 24 based on the configuration of the I / F component 24 as shown in FIG.

  The component management FW 23 will be described. FIG. 7 shows an example of the configuration of the component management FW 23. The component management FW 23 has a callable interface 44, a component management table 45, and a function interface management table 46.

The callable interface 44 is an interface for calling the component management FW 23 from the application component 25 or the I / F component 24. The component management FW 23 controls the operation state of the I / F component according to the called interface.
When the “start (component identifier)” interface is called, the component management FW 23 calls the start () interface of the component package specified by the component identifier.

  Similarly, when the “stop (component identifier)” interface is called, the component management FW 23 calls the stop () interface of the component package specified by the component identifier.

  When the “installation (component package)” interface is called, the component management FW 23 installs the specified component package in an unregistered state in the vehicle multimedia device.

  When the “Uninstall (component identifier)” interface is called, the component management FW 23 uninstalls the specified component package in the registered state from the vehicle multimedia device.

  When the “application list acquisition ()” interface is called, the component management FW 23 acquires a list of registered component packages.

  When the interface of “function interface list acquisition ()” is called, the component management FW 23 acquires a list of registered function I / Fs such as the route search I / F 34.

  When the “function interface registration (function interface)” interface is called, the component management FW 23 registers the specified function I / F in a predetermined component package.

  When the “function interface registration (function interface)” interface is called, the component management FW 23 registers the specified function I / F in a predetermined component package.

  If the interface is “Acquire function interface (interface name)”, the designated function I / F is acquired using the communication unit 15, for example. Thereby, the operation state of the component package is being updated.

  The component management table 45 is a table that holds a component identifier and its operation state in association with each other, and the function interface management table 46 is a table that holds a function interface in association with its operation state. Since the function interface is a function included in the I / F component, the structure of the function interface management table 46 is the same as that of the component management table 45. Hereinafter, the component management table 45 will be used for description.

  FIG. 8 shows an example of the component management table 45. In the component management table 45, the version, creator, and status are recorded in association with the component identifier. The version and creator are the same as those of the component information file described above.

  The state of FIG. 8 shows the operation state of each I / F component 24, and can take the operation state of the start state, stop state, registration state, abnormal state, and updating state in the state transition diagram of FIG. Since the unregistered state is a state that is not registered in the component management table 45, there is no operation state that is not registered in the component management table 45.

  A process in which the component management FW 23 controls the operation state of the I / F component 24 or the application component 25 using the above configuration will be described with reference to the flowchart of FIG.

  First, the application component 25 or the I / F component 24 (hereinafter simply referred to as a component) outputs a function request to the component management FW 23 (S1). For example, because a predetermined component uses another function by a user's operation, a component to be used is specified and output to the component management framework 23.

  The output to the component management FW 23 has the configuration shown in FIG. For example, if the request is for starting another component, a request such as “start (component identifier)” is output to the component management FW 23.

  The component management FW 23 analyzes the content of the output and refers to the component management table 45 to detect the current operation state of the component package (S2). When the request from the component is “start”, the component management FW 23 confirms that the designated component package is in a registration state or a stop state that can be in a start state. If it is not registered or stopped, an error may be returned to the component, or the component package may be controlled to be registered or stopped.

  In the case of the registration state or the stop state, the component management FW 23 calls the Start () interface of the designated component package. Thereby, a start process is performed (S3). The started component package is generated as a thread, and a plurality of threads are executed in parallel. The plurality of threads perform cooperative operations while communicating with each other and waiting for or waiting for the other party's processing. Specifically, the internal processing logic of the component package is executed, and the function implementation unit 22 is requested to provide a function via JNI.

  Next, the component management FW 23 updates the status of the component package in the component management table 45 to “start”, and the process ends (S4).

  As described above, the vehicle multimedia apparatus according to the present embodiment includes the component management FW 23 that controls the operation state of the I / F component 24 by making the function mounting unit 22, the I / F component 24, and the application component 25 independent. Thus, when only the interface of a predetermined function (for example, navigation) is updated, only the I / F component 24 (or including the application component 25) needs to be changed. Therefore, the communication cost can be reduced when the module is updated through the public line.

  The I / F component 24 and the application component 25 all have a common interface (Start (), Stop ()), and the component management FW 23 controls each component via the common interface. Can be executed. That is, necessary components can be executed as appropriate, and components can be installed or uninstalled dynamically.

  The platform-independent part is written in a hardware-independent language such as Java, so high compatibility can be secured on various platforms, and the platform-dependent part can be implemented in a form that is optimal for the platform. The processing speed can be improved. That is, it is possible to minimize the decrease in processing speed and improve the reusability of applications on different platforms.

Further, even if the developer does not know the configuration of the function implementation unit 22, if the developer knows the functions of the I / F component 24 and the application component 25, an application can be created by describing a common interface.
[When the function implementation unit is connected via a network]
The system configuration of the present embodiment can also be suitably applied when the function mounting unit 22 provides a function via a network. FIG. 10 shows an example of a system configuration in which a platform dependent part and an independent part are connected via a network. 10, the same components as those in FIG. 4 are denoted by the same reference numerals, and the description thereof is omitted.

  In FIG. 10, the I / F component 24 and the function mounting unit 22 are mounted on separate hardware. The hardware part of the component unit 200 on which the I / F component 24 is mounted and the function unit 100 on which the function mounting unit 22 is mounted are connected via a network 150. The network 150 is a wireless LAN or the Internet that enables connection with an in-vehicle LAN that connects ECUs existing in a vehicle or a server outside the vehicle.

  In FIG. 10, the distributed object layer 210 is provided in the OS layer of the component unit 200, and the distributed object layer 110 is provided in the OS layer of the functional unit 100. The distributed object layers 210 and 110 are layers for exchanging messages between objects between different hardware, and are, for example, CORBA (Common Object Request Broker Architecture). The distributed object layers 110 and 210 may be DCOM (Distributed Component Object Model) as long as communication between different hardware is possible, and SOAP (Simple Object Access) can be created by creating messages that communicate with each other using XML. Protocol) may be used. In the system configuration of FIG. 10, since the distributed object layer absorbs the difference in hardware or programming language, JNI is not provided.

  With the system configuration as shown in FIG. 10, in addition to the above-described effects, the function unit 100 and the I / F component unit 200 can be separated from each other and mounted on the vehicle, so that the space of the vehicle can be used effectively.

It is a functional block diagram of the conventional car navigation apparatus. It is an example of the block diagram of the multimedia apparatus for vehicles. It is an example of the system block diagram of the multimedia apparatus for vehicles. It is the system block diagram which extracted the function of navigation. It is a transition diagram of the operation state of the I / F component managed by the component management FW. It is an example of the component package which shows the structure of an I / F component. It is an example of a structure of component management FW. It is an example of a component management table. It is a flowchart figure of the process which the component management FW controls the operation state of an I / F component or an application component. It is an example of a system configuration in which a platform dependent part and an independent part are connected via a network.

Explanation of symbols

DESCRIPTION OF SYMBOLS 15 Communication unit 16 Storage device 21 Platform 22 Middleware function implementation part 23 Component management framework 24 Interface component 25 Application component 31 Java VM
100 Function unit 110, 210 Distributed object layer 150 Network 200 Component unit

Claims (6)

Position information acquisition means for acquiring position information;
Media data acquisition means for acquiring media data;
Output means for outputting audio or video;
An operation input means for accepting an operation, and a multimedia device for a vehicle on which an application component having a navigation function, an audio / video playback function, or a function of providing an external communication interface operates,
Program storage means for storing a program;
A platform comprising hardware resources including a central processing unit and an operating system executed by the central processing unit ;
A virtual machine that the central processing unit realizes on the platform;
The central processing unit is realized by using the virtual machine, in response to a call content from the plurality of application components, registration state have a common application interface regardless of the function, start state, stop state, the abnormal state And control means for individually controlling the operation state of the application component having each operation state in the updating state ;
A function processing unit corresponding to each of the plurality of application components executed by the central processing unit on the platform;
Upon receiving a processing start request from the application component, the control unit controls the operation state of the instructed application component to a start state, and the application component in the start state performs processing on the function implementation unit corresponding to the function. Start,
The said function implementation part is a multimedia apparatus for vehicles which provides the said application component with the process result with respect to the said process. The function implementation unit is realized by executing a program described in a language dependent on the platform,
The application component is realized by executing a program described in a language executable by the virtual machine.
The multimedia device for a vehicle according to claim 1. When the application component receives the processing result from the function implementation unit,
The application component notifies the control means of the identification information and operation state of the application component,
The control means controls the notified application component to the notified operating state,
The function implementation unit provides the application component with the processing result for a processing request corresponding to the function from the application component;
The multimedia device for a vehicle according to claim 1 or 2, wherein The plurality of application components have a common application interface for starting or stopping the application components;
The control means controls the application component via the common application interface ;
The multimedia device for a vehicle according to claim 3 . The control means includes
By applying a start process to the application component that is in the registered state by being installed, the transition is made to the start state,
By applying stop processing to the application component in the start state, it is transited to the stop state,
Transition to the start state by applying start processing to the application component in the stop state,
The multimedia device for a vehicle according to claim 4 . The control means includes
By performing an update process on the application component in the stopped state, transition to the updating state,
Transition to the unregistered state by performing an uninstall process on the application component in the registered state.
The multimedia device for a vehicle according to claim 5 .

Images