Vehicle information providing system, information providing method thereof, and vehicle including same

Abstract

The invention provides a vehicle information providing system, an information providing method thereof and a vehicle including the system. A vehicle information providing system, an information providing method thereof, and a vehicle including the same are implemented to synthesize and output data obtained by processing vehicle interface data and vehicle data on the basis of different system languages, thereby enhancing the security of the vehicle data. The vehicle information providing system may include: a first data receiving module for receiving vehicle data; the second data receiving module is used for receiving vehicle interface data and first metadata related to the vehicle data; and a processor for processing the vehicle data and the vehicle interface data based on system languages different from each other, and synthesizing the vehicle data into a user experience (UX) environment generated by processing the vehicle interface data based on the first metadata.

Description

Technical Field

[0001] The present application relates to a vehicle information providing system, an information providing method thereof, and a vehicle including the system, which are implemented to synthesize and output data obtained by processing vehicle interface (UX) data and vehicle data based on different system languages, thereby enhancing the security of vehicle data. Background Art

[0002] An infotainment system for providing information and entertainment is provided in a vehicle.

[0003] The infotainment system may manage and / or output infotainment information and vehicle data through an interface (UX: user experience) implemented based on a markup language such as HTML5.

[0004] When managing and / or outputting vehicle data through an interface implemented based on a markup language such as HTML5, the vehicle data may be leaked to the outside by a method such as script injection.

[0005] Therefore, a method configured to enhance security to prevent vehicle data from leaking to the outside during the process of managing and / or outputting vehicle data through an entertainment system is needed.

[0006] The information included in the background art of the present application is only intended to enhance the overall understanding of the present application, and should not be regarded as an admission or any form of implication that this information constitutes the prior art known to those skilled in the art. Summary of the Invention

[0007] Aspects of the present application are directed to providing a vehicle information providing system, an information providing method thereof, and a vehicle including the system, which are implemented to synthesize vehicle interface (UX) data and vehicle data processed based on different system languages, and output the synthesized data.

[0008] Furthermore, in an exemplary embodiment of the present application, another object of solving the technical problem is to provide a vehicle information providing system, an information providing method thereof, and a vehicle including the system, which are implemented to synthesize vehicle data processed by a processing module based on a vehicle programming language into a UX environment output by processing vehicle UX data by a processing module based on a markup language and output the result.

[0009] Furthermore, in an exemplary embodiment of the present application, another object of solving the technical problem is to provide a vehicle information providing system, an information providing method thereof, and a vehicle including the system, which are implemented to provide a vehicle data display area in a UX environment output from a processing module based on a markup language, and output vehicle data output from a processing module based on a vehicle programming language to the vehicle data display area.

[0010] The purpose of solving the technical problems of the present application is not limited to the above, and those skilled in the art to which the present application pertains will also clearly understand other purposes of the present application through the following description.

[0011] As a technical means for achieving the above technical problems, a vehicle information providing system, an information providing method thereof, and a vehicle including the system may be provided, which are implemented to enhance the security of vehicle data by processing vehicle interface (UX) data and vehicle data based on mutually different system languages.

[0012] According to an exemplary embodiment of the present application, a vehicle information providing system is provided, which includes: a first data receiving module for receiving vehicle data; a second data receiving module for receiving vehicle interface (UX: user experience) data and first metadata related to the vehicle data; and a processor for processing the vehicle data and the vehicle UX data based on mutually different system languages, and synthesizing the vehicle data into a UX environment generated by processing the vehicle UX data based on the first metadata.

[0013] According to an exemplary embodiment of the present application, the processor may include: a first data processing module for processing vehicle data in a vehicle programming language; a second data processing module for processing vehicle UX data based on a markup language to generate a UX environment; and a synthesizing module for synthesizing the vehicle data into the UX environment based on the first metadata.

[0014] According to an exemplary embodiment of the present application, the first data receiving module may receive identification data related to the vehicle data, and the first data processing module may be configured to process the vehicle data and the identification data, and generate vehicle data matching the identification data for storage in a memory.

[0015] According to an exemplary embodiment of the present application, the second data receiving module may receive second metadata related to the vehicle UX data, and the second data processing module may be configured to process the vehicle UX data based on the second metadata and generate a UX environment.

[0016] According to an exemplary embodiment of the present application, the second data processing module may allocate a vehicle data display area in the UX environment based on the first metadata, and the synthesizing module may synthesize the vehicle data into the vehicle data display area.

[0017] According to an exemplary embodiment of the present application, the synthesizing module may search for vehicle data corresponding to the identification data included in the first metadata in the memory, and synthesize the searched vehicle data into the UX environment.

[0018] According to an exemplary embodiment of the present application, a vehicle information providing method is provided, which includes: receiving vehicle data; receiving vehicle interface (UX: user experience) data and first metadata related to the vehicle data; processing the vehicle data based on a first system language; processing the vehicle UX data based on a second system language; and synthesizing the vehicle data into a UX environment generated by processing the vehicle UX data based on the first metadata.

[0019] According to an exemplary embodiment of the present application, the first system language may be a vehicle programming language, and the second system language may be a markup language.

[0020] According to an exemplary embodiment of the present application, receiving vehicle data may further receive identification data related to the vehicle data, processing the vehicle data may include processing the vehicle data and the identification data, and generating vehicle data that matches the identification data for storage in a memory.

[0021] According to an exemplary embodiment of the present application, receiving vehicle UX data and first metadata related to the vehicle data may further receive second metadata related to the vehicle UX data, and processing the vehicle UX data based on the second system language may include processing the vehicle UX data based on the second metadata and generating a UX environment.

[0022] According to an exemplary embodiment of the present application, processing the vehicle UX data based on the second system language may include allocating a vehicle data display area in the UX environment based on the first metadata, and synthesizing the vehicle data into the user experience environment may include synthesizing the vehicle data into the vehicle data display area.

[0023] According to an exemplary embodiment of the present application, synthesizing the vehicle data into the user experience environment may include searching for vehicle data corresponding to the identification data included in the first metadata in a memory and synthesizing the searched vehicle data into the UX environment.

[0024] According to an exemplary embodiment of the present application, a vehicle is provided, which includes: a vehicle data providing device configured to provide vehicle data; a vehicle interface providing device configured to provide vehicle interface (UX: user experience) data and metadata related to the vehicle data; and a vehicle information providing system including a processor configured to process the vehicle data and the vehicle UX data based on different system languages and synthesize the vehicle data into a UX environment generated by processing the vehicle UX data based on the metadata.

[0025] Specific details of various examples according to the present application other than the means for solving the above problems are included in the following description and drawings.

[0026] According to an exemplary embodiment of the present application, vehicle interface (UX) data and vehicle data may be processed through different paths from each other.

[0027] Furthermore, the vehicle data processed by the vehicle programming language-based processing module may be synthesized into a UX environment output by processing the vehicle interface data by the markup language-based processing module and output.

[0028] Therefore, since the vehicle data is not processed by the markup language-based processing module, leakage of the vehicle data that may occur during the markup language-based processing can be prevented, and the security of the vehicle data can be enhanced.

[0029] Furthermore, since the vehicle data is displayed through a markup language-based UX environment as in a conventional method, the security of the vehicle data can be structurally enhanced while maintaining the advantages of the markup language-based UX environment.

[0030] The effects of the present application are not limited to the above-described effects, and those skilled in the art will clearly understand other effects not described above through the description of the appended claims.

[0031] Since the contents of the problems to be solved, solutions to the problems, and effects described above do not specifically describe the essential features of the claims, the scope of the claims is not limited by the contents described in the contents of this application.

[0032] The methods and apparatus of the present application have other features and advantages, which will be apparent from the drawings incorporated herein and the following specific embodiments, or will be described in more detail in the drawings incorporated herein and the following specific embodiments, which together serve to explain the specific principles of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 is a schematic diagram exemplarily showing a vehicle 1 including a vehicle information providing system 100 according to an exemplary embodiment of the present application.

[0034] Figure 2 is a diagram exemplarily showing a configuration of a vehicle information providing system 100 according to an exemplary embodiment of the present application.

[0035] Figure 3 1 is a diagram exemplarily illustrating an example of synthesizing vehicle data and a UX environment by the vehicle information providing system 100 according to the exemplary embodiment of the present application.

[0036] Figure 4 is a schematic diagram exemplarily illustrating an information providing method according to an exemplary embodiment of the present application.

[0037] It should be understood that the accompanying drawings are not drawn to scale and are merely simplified drawings suitable for illustrating the basic principles and various features of the present invention. The specific design features of the present invention disclosed herein, such as specific dimensions, directions, positions, and profile positions, as well as the profile, will be determined in part by the specific application and use environment.

[0038] In the multiple accompanying drawings, the same or equivalent components of the present application are labeled with the same reference numerals. Specific embodiments

[0039] Now, various embodiments of the present application will be described in detail. Examples of the various embodiments are illustrated in the accompanying drawings and are described as follows. Although the present application will be described in conjunction with the exemplary embodiments of the present application, it should be understood that this specification is not intended to limit the present application to those exemplary embodiments. On the other hand, the present application is intended to cover not only the exemplary embodiments of the present application but also various alternative embodiments, modified embodiments, equivalent embodiments, and other embodiments that may be included within the spirit and scope of the present application as defined by the appended claims.

[0040] Referring to the exemplary embodiments described in detail below and the accompanying drawings, the advantages and features of the present application and the methods for achieving its advantages and features will become apparent. However, the present application is not limited to the exemplary embodiments included below but will be implemented in various different forms. These exemplary embodiments are provided only to make the disclosure of the present application complete and to fully inform those skilled in the art of the scope of the present application. The present application is defined only by the scope of the claims.

[0041] The shapes, sizes, proportions, angles, quantities, etc. included in the accompanying drawings for describing the exemplary embodiments of the present application are merely examples, and the present application is not limited thereto. Throughout the present application, the same reference numerals generally denote the same components. In addition, when determining that a detailed description of related known technologies may unnecessarily obscure the subject matter of the present application, the detailed description thereof will be omitted. Terms such as "including", "having", and "comprising" used herein are generally intended to allow the addition of other components, unless these terms are used together with the term "only". Unless otherwise specifically stated, the case of representing a component in the singular form includes the case of the plural form.

[0042] When explaining a component, even if there is no clear description of a separate error range, it will be interpreted as including an error range.

[0043] When terms such as "after", "then", "subsequent to", and "before" are used to describe a relationship of temporal sequence, the sequence may not be continuous unless these terms are used in conjunction with the term "immediately" or "directly".

[0044] Although terms such as first, second, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are only used to distinguish one component from another. Thus, the first component described hereinafter may be the second component within the technical concept of the present application.

[0045] When describing the components of the present application, terms such as first, second, A, B, (a), or (b) may be used. Since these terms are provided only to distinguish the components from each other, the nature, sequence, order, or number of the corresponding components is not limited thereto. When a component is described as "connected", "coupled", or "interfaced" to another component, the component may be directly connected or interfaced to the other component, but it should be understood that unless otherwise specifically stated, other components may also be "inserted" between each component that is indirectly connected or interfaced.

[0046] "At least one" should be understood to include any combination of one or more related components. For example, "at least one of the first component, the second component, and the third component" means not only including the first component, the second component, or the third component, but also including any combination of two or more of the first component, the second component, and the third component.

[0047] The features of the various exemplary embodiments of this specification may be combined or combined with each other in part or in whole, and may operate and be technology-driven differently from each other. Each exemplary embodiment of the present application may also be executed independently of each other and may be executed in conjunction with an associated relationship.

[0048] For ease of description, the proportions of the components shown in the drawings have proportions different from the actual proportions, and thus the proportions of the components are not limited to the proportions shown in the drawings.

[0049] Hereinafter, a vehicle information providing system, an information providing method thereof, and a vehicle including the system according to an exemplary embodiment of the present application will be described with reference to the drawings.

[0050] Figure 1 is a schematic diagram exemplarily showing a vehicle 1 including a vehicle information providing system 100 according to an exemplary embodiment of the present application.

[0051] Refer to Figure 1, vehicle 1 may include a vehicle information providing system 100 according to an exemplary embodiment of the present application.

[0052] For example, vehicle 1 may include an electric vehicle (EV), a hybrid electric vehicle (HEV), a plug-in hybrid electric vehicle (PHEV), a hydrogen fuel cell electric vehicle (FCEV), etc., and the type of vehicle 1 is not limited thereto.

[0053] Vehicle 1 may be equipped with a data providing device for providing data required for the operation of the vehicle information providing system 100.

[0054] According to an exemplary embodiment of the present application, the data providing device may include a vehicle data providing device 10 for providing vehicle data, and a vehicle interface providing device 20 for providing vehicle interface data (hereinafter referred to as vehicle UX data), but the type of the data providing device is not limited thereto.

[0055] The vehicle data providing device 10 may provide identification data for identifying vehicle data and the vehicle data. For example, the vehicle data providing device 10 may include a sensor for sensing the internal or external temperature of the vehicle, a sensor for measuring the speed of the vehicle, a sensor for measuring the driving distance of the vehicle, etc.

[0056] According to an exemplary embodiment of the present application, when synthesizing vehicle data and vehicle UX data, identification data related to the vehicle data may be used.

[0057] For example, vehicle data may include data related to vehicle conditions, vehicle internal environment, vehicle external environment, etc. For example, vehicle data may include vehicle speed, vehicle mileage, vehicle internal temperature, vehicle external temperature, etc., but the types of data included in the vehicle data are not limited thereto.

[0058] For example, vehicle UX data may be data for defining the attributes of vehicle data. That is to say, vehicle UX data may refer to data that helps users understand what data the vehicle data is related to.

[0059] For example, in response to the vehicle data being speed, the vehicle UX data may include image data ("speed"), unit data ("km / h"), etc., to indicate that the vehicle data is related to speed.

[0060] For example, in response to the vehicle data being driving distance, the vehicle UX data may include image data ("driving length"), unit data ("km"), etc., to indicate that the vehicle data is related to driving distance.

[0061] For example, in response to the vehicle data being the temperature inside the vehicle, the vehicle UX data may include image data ("vehicle interior temperature"), unit data ("°C"), etc., to indicate that the vehicle data is data related to the temperature inside the vehicle.

[0062] In this way, the vehicle UX data may be data for providing a basic display environment required for the vehicle 1 to execute an information entertainment function, and when designing the information entertainment function in the vehicle 1, the vehicle UX data may be preset in the vehicle 1.

[0063] According to an exemplary embodiment of the present application, the vehicle interface providing device 20 may provide metadata related to the vehicle UX data. In addition, the vehicle interface providing device 20 may provide metadata related to the vehicle data. For example, the vehicle interface providing device 20 may include an information entertainment system.

[0064] For example, the metadata related to the vehicle UX data may include display position data, display format data, additional data, etc. of the vehicle UX data. In addition, the metadata related to the vehicle data may include identification data, display position data, display format data, additional data, etc. of the vehicle data.

[0065] The vehicle information providing system 100 may provide information based on the data provided by the data providing device.

[0066] According to an exemplary embodiment of the present application, the vehicle information providing system 100 may synthesize and provide the vehicle data provided by the vehicle data providing device 10 and the vehicle UX data provided by the vehicle interface providing device 20.

[0067] The vehicle information providing system 100 may be configured to process the vehicle data and the vehicle UX data based on different system languages.

[0068] The vehicle information providing system 100 may synthesize the vehicle data and the vehicle UX data processed based on different system languages for output through the display device.

[0069] The vehicle information providing system 100 may synthesize the vehicle data into the UX environment generated by processing the vehicle UX data and output it through the display device.

[0070] The vehicle information providing system 100 may synthesize the vehicle data into the UX environment based on the metadata related to the vehicle data.

[0071] For example, the vehicle information providing system 100 according to an exemplary embodiment of the present application may be configured as a part of the information entertainment system, and the information entertainment system may execute the information providing method according to an exemplary embodiment of the present application.

[0072] Figure 2 FIG. 1 is a schematic diagram exemplarily showing the configuration of a vehicle information providing system 100 according to an exemplary embodiment of the present application.

[0073] Referring to Figure 1 and Figure 2 , according to an exemplary embodiment of the present application, the vehicle information providing system 100 may include a first data receiving module 110, a second data receiving module 120, a memory 130, a display device 140, and a processor P, and the configuration of the vehicle information providing system 100 is not limited thereto.

[0074] The first data receiving module 110 may receive vehicle data provided by the vehicle data providing device 10.

[0075] The second data receiving module 120 may receive vehicle UX data provided by the vehicle interface providing device 20.

[0076] The vehicle data received through the first data receiving module 110 and the vehicle UX data received through the second data receiving module 120 may be provided to the processor P.

[0077] Each of the first data receiving module 110 and the second data receiving module 120 may include a module for performing in-vehicle communication (e.g., controller area network (CAN) communication, local interconnect network (LIN) communication, and local area network (LAN) communication).

[0078] The memory 130 may store various algorithms, data, etc. required for the operation of the processor P.

[0079] The memory 130 may include volatile memory and / or non-volatile storage. The volatile memory may include dynamic random access memory (DRAM), static random access memory (SRAM), synchronous dynamic random access memory (SDRAM), phase change random access memory (PRAM), magnetic random access memory (MRAM), resistive random access memory (RRAM), ferroelectric random access memory (FeRAM), etc. The non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory, etc.

[0080] According to an exemplary embodiment of the present application, the memory 130 may store an algorithm for implementing the information providing method according to an exemplary embodiment of the present application. For example, the memory 130 may store an algorithm for processing data, an algorithm for synthesizing data, etc., which are executed by the processor P.

[0081] The display device 140 can display the information provided by the processor P. For example, the display device 140 can be implemented with a liquid crystal display (LCD) module, an organic light emitting diode (OLED) module, etc., and the type of the display device 140 is not limited thereto.

[0082] For example, the display device 140 can include a head-up display, an audio video navigation (AVN) display, etc.

[0083] The processor P can execute the algorithms stored in the memory 130. For example, the processor P can be configured to process the received data and the data stored in the memory 130. The processor P can execute the computer-readable code (such as algorithms) stored in the memory 130 and the instructions triggered by the processor P.

[0084] The processor P can be a data processing device implemented in hardware, and the hardware includes a circuit having a physical structure for performing the required operations. For example, the required operations can include the code or instructions included in the program.

[0085] For example, the data processing device implemented in hardware can include a microprocessor, a central processing unit, a processor core, a multi-core processor, a multi-processor, an application specific integrated circuit (ASIC), and a field programmable gate array (FPGA).

[0086] According to an exemplary embodiment of the present application, the processor P can synthesize the vehicle data provided by the vehicle data providing device 10 and the vehicle UX data provided by the vehicle interface providing device 20, and provide the synthesized data.

[0087] The processor P can synthesize the vehicle data and the vehicle UX data processed based on different system languages from each other for output through the display device 140.

[0088] The processor P can synthesize the vehicle data into the UX environment generated by processing the vehicle UX data based on the metadata related to the vehicle data.

[0089] According to an exemplary embodiment of the present application, the processor P can include a first data processing module 150, a second data processing module 160, and a synthesis module 170.

[0090] The first data processing module 150 can receive the vehicle data provided by the vehicle data providing device 10 and the identification data related to the vehicle data, and can output the vehicle data matching the identification data.

[0091] For example, the vehicle data matching the identification data output by the first data processing module 150 can be stored in the memory 130.

[0092] According to an exemplary embodiment of the present application, the first data processing module 150 may be configured to process vehicle data and identification data based on a vehicle programming language.

[0093] The second data processing module 160 may receive vehicle UX data and metadata provided by the vehicle interface providing device 20. Here, the metadata may include metadata related to the vehicle UX data and metadata related to the vehicle data.

[0094] According to an exemplary embodiment of the present application, the second data processing module 160 may be configured to generate and output a UX environment based on the vehicle UX data and the metadata related to the vehicle UX data.

[0095] According to an exemplary embodiment of the present application, the second data processing module 160 may be configured to process the vehicle UX data and the metadata related to the vehicle UX data based on a markup language.

[0096] According to an exemplary embodiment of the present application, the second data processing module 160 may allocate a vehicle data display area in the UX environment based on the metadata related to the vehicle data.

[0097] That is to say, the UX environment generated by the second data processing module 160 includes a vehicle data display area.

[0098] The second data processing module 160 may provide the UX environment and the metadata related to the vehicle data to the synthesis module 170.

[0099] According to an exemplary embodiment of the present application, the synthesis module 170 may synthesize the vehicle data into the UX environment based on the UX environment provided by the second data processing module 160 and the metadata related to the vehicle data, and display the synthesized data on the display device 140.

[0100] The synthesis module 170 may search for the vehicle data corresponding to the identification data of the vehicle data included in the metadata related to the vehicle data in the memory 130, and synthesize the searched vehicle data into the UX environment.

[0101] The synthesis module 170 may synthesize the vehicle data into the UX environment based on the display position data of the vehicle data included in the metadata related to the vehicle data.

[0102] The synthesis module 170 may synthesize the vehicle data into the UX environment based on the display format data of the vehicle data included in the metadata related to the vehicle data.

[0103] According to an exemplary embodiment of the present application, in response to the second data processing module 160 not successfully receiving the metadata required to implement the UX environment, the synthesis module 170 may display a default user interface (UI) pre-stored in the memory 130.

[0104] According to an exemplary embodiment of the present application, in response to the second data processing module 160 being in an abnormal state, the synthesis module 170 may display the default UI pre-stored in the memory 130.

[0105] Figure 3 FIG. is a schematic diagram exemplarily showing an example of synthesizing vehicle data and a UX environment by a vehicle information providing system 100 according to an exemplary embodiment of the present application, and shows a case of providing the speed of a vehicle.

[0106] As Figure 3 shown, the vehicle information providing system 100 may synthesize the speed (i.e., vehicle data) into the vehicle data display area in the UX environment including vehicle UX data.

[0107] Figure 4 FIG. is a schematic diagram exemplarily showing an information providing method according to an exemplary embodiment of the present application.

[0108] Figure 4 The step-by-step operations shown can be performed by referring to the vehicle information providing system 100 described in Figure 1 , Figure 2 and Figure 3 .

[0109] Referring to Figure 1 , Figure 2 , Figure 3 and Figure 4 , at step S400, the vehicle information providing system 100 may receive vehicle data and vehicle UX data.

[0110] At step S400, the vehicle information providing system 100 may receive the vehicle data provided by the vehicle data providing device 10 through the first data receiving module 110, and receive the vehicle UX data provided by the vehicle interface providing device 20 through the second data receiving module 120.

[0111] At step S400, the vehicle information providing system 100 may receive the identification data related to the vehicle data and the vehicle data from the vehicle data providing device 10.

[0112] At step S400, the vehicle information providing system 100 may receive the metadata related to the vehicle UX data, the metadata related to the vehicle data, and the vehicle UX data from the vehicle interface providing device 20.

[0113] Thereafter, in step S410, the vehicle information providing system 100 may be configured to process vehicle data and identification data using the first data processing module 150 to output vehicle data that matches the identification data.

[0114] In step S410, the first data processing module 150 may be configured to process vehicle data and identification data based on a vehicle programming language.

[0115] In addition, in step S420, the vehicle information providing system 100 may be configured to process vehicle UX data and metadata related to the vehicle UX data using the second data processing module 160 to output a UX environment including the vehicle UX data.

[0116] In step S420, the second data processing module 160 may be configured to process vehicle UX data and metadata related to the vehicle UX data based on a markup language.

[0117] In step S420, the second data processing module 160 may allocate a vehicle data display area in the UX environment based on metadata related to the vehicle data.

[0118] Thereafter, in step S430, the vehicle information providing system 100 may use the synthesis module 170 to synthesize the vehicle data into the UX environment and output the synthesized image through the display device 140. The vehicle information providing system 100 synthesizes and outputs the vehicle data processed based on the vehicle programming language, so that it is possible to prevent the leakage of vehicle data that may occur when processing vehicle data based on a markup language, thereby enhancing the security of vehicle data.

[0119] In step S430, the synthesis module 170 may synthesize the vehicle data in the vehicle data display area allocated in the UX environment.

[0120] In step S430, the synthesis module 170 may search for vehicle data corresponding to the identification data of the vehicle data included in the metadata related to the vehicle data in the memory 130, and synthesize the searched vehicle data into the UX environment.

[0121] In step S430, the synthesis module 170 may synthesize the vehicle data into the UX environment based on the display position data of the vehicle data included in the metadata related to the vehicle data.

[0122] [[ID=2N]]The control device may be at least one microprocessor operated by a predetermined program, and the predetermined program may include a series of commands for executing the methods included in the foregoing various exemplary embodiments of the present application. "

[0123] In various exemplary embodiments of the present application, each of the above operations may be performed by a control device, and the control device may be configured by a plurality of control devices or an integrated single control device.

[0124] In various exemplary embodiments of the present application, the memory and the processor may be provided as one chip or as separate chips.

[0125] In various exemplary embodiments of the present application, the scope of the present application includes software or machine-executable commands (e.g., operating systems, applications, firmware, programs, etc.) for enabling the operations of the methods according to the various embodiments to be executed on a device or computer, and non-transitory computer-readable media storing and executable on the device or computer the software or commands.

[0126] In various exemplary embodiments of the present application, the control device may be implemented in the form of hardware or software, or may be implemented in a combination of hardware and software.

[0127] In addition, terms such as "unit" and "module" included in the specification refer to units for processing at least one function or operation, which may be implemented by hardware, software, or a combination thereof.

[0128] In an exemplary embodiment of the present application, a vehicle may be based on a concept and include various transportation means. In some cases, a vehicle may be interpreted based on the concept to include not only various land transportation means traveling on roads, such as cars, motorcycles, large trucks, and buses, but also various transportation means such as airplanes, drones, and ships.

[0129] For the convenience of explanation and accurate definition of the appended claims, the terms "above", "below", "inside", "outside", "upper", "lower", "upward", "downward", "front", "rear", "back", "inner side", "outer side", "inward", "outward", "internal", "external", "internal of", "external of", "forward", and "backward" are used to describe the features of the exemplary embodiments with reference to the positions of these features shown in the drawings. It will be further understood that the term "connected" or its derivatives refers to both direct and indirect connections.

[0130] The term "and / or" may include combinations of multiple related recited items or any one of multiple related recited items. For example, "A and / or B" includes three cases: "A", "B", and "A and B".

[0131] In an exemplary embodiment of the present application, "at least one of A and B" may refer to "at least one of A or B" or "at least one of a combination of at least one of A and B". Further, "one or more of A and B" may refer to "one or more of A or B" or "one or more of a combination of one or more of A and B".

[0132] In this specification, unless otherwise specified, singular expressions also include plural expressions.

[0133] In an exemplary embodiment of the present application, it should be understood that terms such as "including" or "having" are intended to indicate the presence of the features, values, steps, operations, elements, components, or combinations thereof described in the specification, without precluding the possibility of adding or the presence of one or more other features, values, steps, operations, elements, components, or combinations thereof.

[0134] According to an exemplary embodiment of the present application, components may be combined with each other to form one, or some components may be omitted.

[0135] As used herein, hardware being operably coupled may include establishing a direct and / or indirect connection, wired and / or wirelessly, between the hardware.

[0136] The foregoing description of specific exemplary embodiments of the present application has been presented for purposes of illustration and description. The foregoing description is not intended to be exhaustive or to limit the present application to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teachings. The exemplary embodiments were chosen and described in order to explain certain principles of the invention and its practical application so as to enable others skilled in the art to implement and utilize the various exemplary embodiments of the present application, as well as various alternatives and modifications thereof. The scope of the present application is defined by the appended claims and their equivalents.

Claims

1. A vehicle information providing system, the system comprising: A first data receiving module configured to receive vehicle data; A second data receiving module configured to receive vehicle interface data and first metadata related to the vehicle data; And A processor operatively connected to the first data receiving module and the second data receiving module, and configured to process the vehicle data and the vehicle interface data based on different system languages, and synthesize the vehicle data into a user experience environment generated by processing the vehicle interface data based on the first metadata.

2. The vehicle information providing system according to claim 1, wherein, The processor is further configured to output the synthesized data through a display device.

3. The vehicle information providing system according to claim 1, wherein The different system languages include a vehicle programming language and a markup language, The processor includes: A first data processing module configured to process vehicle data based on the vehicle programming language; A second data processing module configured to process vehicle interface data based on the markup language to generate a user experience environment; and A synthesis module configured to synthesize vehicle data into the user experience environment based on the first metadata.

4. The vehicle information providing system according to claim 3, wherein The first data receiving module is further configured to receive identification data related to the vehicle data, The first data processing module is further configured to process the vehicle data and the identification data, and generate vehicle data matching the identification data for storage in a memory.

5. The vehicle information providing system according to claim 3, wherein The second data receiving module is further configured to receive second metadata related to the vehicle interface data, The second data processing module is further configured to process the vehicle interface data based on the second metadata and generate a user experience environment.

6. The vehicle information providing system according to claim 3, wherein The second data processing module is further configured to allocate a vehicle data display area in the user experience environment based on the first metadata, The synthesis module is further configured to synthesize the vehicle data into the vehicle data display area.

7. The vehicle information providing system according to claim 6, wherein, The synthesis module is further configured to output the synthesized vehicle data on a display device.

8. The vehicle information providing system according to claim 4, wherein, The synthesis module is further configured to search for vehicle data corresponding to the identification data included in the first metadata in a memory, and synthesize the searched vehicle data into the user experience environment.

9. A vehicle information providing method, the method comprising: Receiving vehicle data; Receiving vehicle interface data and first metadata related to the vehicle data; Processing the vehicle data by a processor based on a first system language; Processing the vehicle interface data by the processor based on a second system language; Synthesizing the vehicle data into a user experience environment generated by processing the vehicle interface data by the processor based on the first metadata.

10. The method according to claim 9, further comprising: Outputting the synthesized data by the processor through a display device.

11. The method according to claim 9, wherein The first system language is a vehicle programming language, The second system language is a markup language.

12. The method according to claim 9, wherein, receiving vehicle data includes receiving identification data related to the vehicle data, processing vehicle data includes processing the vehicle data and the identification data, and generating vehicle data that matches the identification data for storage in a memory.

13. The method according to claim 9, wherein, receiving vehicle interface data and first metadata related to the vehicle data includes receiving second metadata related to the vehicle interface data, processing the vehicle interface data based on a second system language includes processing the vehicle interface data based on the second metadata, and generating a user experience environment.

14. The method according to claim 9, wherein, processing the vehicle interface data based on a second system language includes allocating a vehicle data display area in the user experience environment based on the first metadata, synthesizing the vehicle data into the user experience environment includes synthesizing the vehicle data into the vehicle data display area.

15. The method according to claim 14, further comprising: outputting the synthesized vehicle data on a display device.

16. The method according to claim 12, wherein, Synthesizing the vehicle data into the user experience environment includes searching in the memory for vehicle data corresponding to the identification data included in the first metadata, and synthesizing the searched vehicle data into the user experience environment.

17. A vehicle, comprising: a vehicle data providing device configured to provide vehicle data; a vehicle interface providing device configured to provide vehicle interface data and metadata related to the vehicle data; and a vehicle information providing system including a first data receiving module, a second data receiving module, and a processor, the first data receiving module being configured to receive vehicle data, the second data receiving module being configured to receive vehicle interface data and the metadata, the processor being operably connected to the first data receiving module and the second data receiving module, and being configured to process the vehicle data and the vehicle interface data based on different system languages, synthesize the vehicle data into a user experience environment generated by processing the vehicle interface data based on the metadata, and output the synthesized data through a display unit.

Images