US-12619413-B2 - Method and system for installing an application in a vehicle

US12619413B2US 12619413 B2US12619413 B2US 12619413B2US-12619413-B2

Abstract

A method and system for installing an application in a mobility device are disclosed. The method of installing an application in a mobility device includes: securing data matched to the mobility device in a server based on application installation information included in an application installation request in response to the application installation request received from the mobility device; creating a metadata adapter of the application in the server based on the secured matching data; transmitting the created metadata adapter together with binary data of the application from the server to the mobility device; and installing the application in the mobility device using the metadata adapter transmitted from the server to the mobility device.

Inventors

Yocheol Jang
HeeJin RO
DuckYoung Kim
JONGBOK LEE
Donghee SEOK

Assignees

HYUNDAI MOTOR COMPANY
KIA CORPORATION

Dates

Publication Date: 20260505
Application Date: 20230714
Priority Date: 20221020

Claims (20)

1 . A method of installing an application in a mobility device, the method comprising: securing data matched to the mobility device in a server based on application installation information included in an application installation request in response to the application installation request received from the mobility device; creating a metadata adapter of the application in the server based on the secured matched data; transmitting the created metadata adapter together with binary data of the application from the server to the mobility device; and installing the application in the mobility device using the metadata adapter transmitted from the server to the mobility device, wherein creating the metadata adapter comprises recreating the metadata adapter by replacing metadata of a before market device of the mobility device with metadata of an after market device provided for the mobility device.
2 . The method according to claim 1 , wherein creating the metadata adapter is performed through a combination of a manifest of the application and a hardware information dictionary of the mobility device.
3 . The method according to claim 2 , wherein the hardware information dictionary of the mobility device comprises: unique identification information of the mobility device; and at least one characteristic value of the mobility device associated with the unique identification information.
4 . The method according to claim 3 , wherein the server, when the mobility device is unidentified, creates the metadata adapter based on a default hardware information dictionary predefined for a mobility device in which hardware information of the mobility device is unidentified.
5 . The method according to claim 1 , wherein creating the metadata adapter comprises overwriting existing metadata with updated metadata among metadata of the metadata adapter when the metadata of the metadata adapter and metadata already embedded in the mobility device do not match each other.
6 . The method according to claim 1 , wherein creating the metadata adapter comprises: storing frequently used data or instructions related to metadata of the metadata adapter in a metadata cache; invalidating or deleting cache data determined to be unusable among cache data of the metadata cache; and generating new data to update the metadata cache when a request to create a metadata adapter occurs.
7 . The method according to claim 6 , wherein criteria for determining that the cache data is unusable comprises when a structural change of the mobility device is made.
8 . The method according to claim 6 , wherein criteria for determining that the cache data is unusable comprises when contents of a maintenance-related database of the mobility device are changed.
9 . The method according to claim 6 , wherein criteria for determining that the cache data is unusable comprises when a change point occurs in at least one characteristic of the mobility device.
10 . The method according to claim 1 , wherein conditions for recreating the metadata adapter comprise when a failure occurs in the before-market device installed in the mobility device.
11 . The method according to claim 1 , wherein conditions for recreating the metadata adapter comprise when the before-market device installed in the mobility device is replaced with the after-market device.
12 . The method according to claim 1 , further comprising: storing frequently used data or instructions related to metadata of the metadata adapter in a metadata cache; and updating, through invalidation or deletion, cache data corresponding to replaced data or instructions among cache data of the metadata cache for recreation of the metadata.
13 . The method according to claim 1 , further comprising transmitting the created metadata adapter and the binary data of the application from the server to the mobility device through a piggyback method.
14 . A system for installing an application in a mobility device, the system comprising: the mobility device having at least one device driven by the application; and a server provided to create a metadata adapter for installation of the application in the mobility device, wherein the system is configured to secure data matched to the mobility device in the server based on application installation information included in an application installation request in response to the application installation request received from the mobility device, create a metadata adapter of the application in the server based on the secured matched data, transmit the created metadata adapter together with binary data of the application from the server to the mobility device, and install the application in the mobility device using the metadata adapter transmitted from the server to the mobility device, wherein creating the metadata adapter comprises recreating the metadata adapter by replacing metadata of a before market device of the mobility device with metadata of an after market device provided for the mobility device.
15 . The system according to claim 14 , wherein creating the metadata adapter is performed through combination of a manifest of the application and a hardware information dictionary of the mobility device.
16 . The system according to claim 15 , wherein the hardware information dictionary of the mobility device comprises: unique identification information of the mobility device; and at least one characteristic value of the mobility device associated with the unique identification information.
17 . The system according to claim 16 , wherein the server, when the mobility device is unidentified, creates the metadata adapter based on a default hardware information dictionary predefined for a mobility device in which hardware information of the mobility device is unidentified.
18 . The system according to claim 14 , wherein creating the metadata adapter comprises overwriting existing metadata with updated metadata among metadata of the metadata adapter when the metadata of the metadata adapter and metadata already embedded in the mobility device do not match each other.
19 . The system according to claim 14 , wherein creating the metadata adapter comprises: storing frequently used data or instructions related to metadata of the metadata adapter in a metadata cache; invalidating or deleting cache data determined to be unusable among cache data of the metadata cache; and generating new data to update the metadata cache when a request to create a metadata adapter occurs.
20 . The system according to claim 19 , wherein criteria for determining that the cache data is unusable comprises when a structural change of the mobility device is made.

Description

CROSS-REFERENCE TO RELATED APPLICATION(S) This application is based on and claims priority under 35 U.S.C. § 119 to Korean Patent Application No. 10-2022-0135599, filed on Oct. 20, 2022, in the Korean Intellectual Property Office, the disclosure of which is incorporated by reference herein in its entirety. BACKGROUND 1. Technical Field The disclosure relates to a vehicle or mobility device, and more particularly to the installation of an application in a vehicle or mobility device. 2. Description of the Related Art Development of various applications for driving various devices of a mobility device (e.g., a vehicle or a moving object) is in progress. Such applications may be installed in a mobility device in the form of a Before Market device and may also be updated through an Over-the-Air (OTA). The range of mobility devices and updates of such applications are diverse. Various applications can be installed in an electronic system of these mobility devices in the form of a Before Market device at the production stage of manufacturing of the mobility devices or can be updated through Over-the-Air (OTA) after the mobility devices are sold. Individual binaries optimized for hardware specifications for each mobility device can be built and deployed. Building and deploying individual binaries like this means fragmentation of applications to achieve a common purpose. Additional inefficiency issues such as fragmented binary management may occur. Edge Intelligence (EI) means that data analysis and solution development are performed together at a site where the data is created. Implementation of edge intelligence at an application level has advantages such as relatively better response speed and security compared to implementation of edge intelligence in a cloud-based server. For example, compared to a method of calculating scores in a server based on characteristic data of mobility devices collected for usage-based insurance (UBI) service development, a method in which information collection and score calculation is performed in real-time in a mobility device itself may obtain better results in terms of data accuracy and processing speed. However, data analysis for implementing edge intelligence in a mobility device may require metadata for tuning individual codes. The requirement of metadata may depend on different hardware characteristics of each mobility device to obtain uniform data analysis and derivation of results. Metadata means one set of data accompanying another set of data to help analyze and classify structured information and add additional information (e.g., data of data). For example, metadata may be objects or items to be identified or controlled for integrated data management. SUMMARY In order to increase the utilization of an application installed in a mobility device by implementing edge intelligence in the mobility device, deployment of metadata optimized for the hardware of each mobility device must be performed. It is an aspect of the disclosure to provide a method and system for installing an application in a mobility device for efficient management/transmission of metadata in implementing edge intelligence in the mobility device. Additional aspects of the disclosure are set forth in part in the description that follows and, in part, should be more apparent from the description or may be learned by practice of the disclosure. In accordance with an aspect of the disclosure, a method of installing an application in a mobility device includes: securing data matched to the mobility device in a server based on application installation information included in an application installation request in response to the application installation request received from the mobility device; creating a metadata adapter of the application in the server based on the secured matching data; transmitting the created metadata adapter together with binary data of the application from the server to the mobility device; and installing the application in the mobility device using the metadata adapter transmitted from the server to the mobility device. The creating of the metadata adapter may be performed through combination of a manifest of the application and a hardware information dictionary of the mobility device. The hardware information dictionary of the mobility device may include unique identification information of the mobility device and may include at least one characteristic value of the mobility device associated with the identification information. The server, when the mobility device is unidentified, may create the metadata adapter based on a default hardware information dictionary predefined for a mobility device in which hardware information of the mobility device is unidentified. The creating of the metadata adapter may include overwriting existing metadata with updated metadata among metadata of the metadata adapter when the metadata of the metadata adapter and metadata already embedded in the mobili