To obtain vehicle information and display the obtained vehicle information using code.

The infotainment system's menu-driven approach allows for rapid and efficient acquisition of vehicle information by generating embedded codes, addressing the limitations of evolving vehicle architectures in OBD systems.

JP7859534B2Active Publication Date: 2026-05-15TOYOTA JIDOSHA KK
View PDF 8 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
TOYOTA JIDOSHA KK
Filing Date
2025-01-06
Publication Date
2026-05-15

AI Technical Summary

Technical Problem

Current methods for acquiring vehicle information using on-board diagnostics (OBD) are difficult to use due to evolving vehicle architectures, limiting data generation and accessibility.

Method used

A method and system that utilizes a vehicle's infotainment system to present a menu for selecting vehicle information, generate a code embedding the information, and display it, allowing for rapid acquisition and sequential collection across multiple vehicles.

Benefits of technology

Enables efficient and rapid collection of vehicle information without needing to physically connect to each vehicle, facilitating quick generation and scanning of embedded codes for multiple vehicles.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007859534000001
    Figure 0007859534000001
  • Figure 0007859534000002
    Figure 0007859534000002
  • Figure 0007859534000003
    Figure 0007859534000003
Patent Text Reader

Abstract

To provide a method for acquiring vehicle information.SOLUTION: In a method for acquiring vehicle information, a menu is presented on a user interface of an infotainment system of a vehicle for acquiring the vehicle information. The vehicle information is selected via the menu for acquiring the vehicle information from a storage device related to at least one electronic control unit of the vehicle. The vehicle information acquired on the basis of the selection of the vehicle information can be received. A code having the embedded vehicle information is generated. The code having the embedded vehicle information is displayed.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] This specification relates to acquiring vehicle information, displaying the acquired vehicle information in code, and a method using the same.

[0002] To acquire vehicle information representing the state of a vehicle, sophisticated and expensive equipment is used. An electronic control unit (ECU), also known as an electronic control module (ECM), is an embedded system of automotive electronic devices that controls one or more of the electrical systems or subsystems of an automobile or other motor vehicle. Modern vehicles have many ECUs, which can include some or all of an engine control module (ECM), a powertrain control module (PCM), a transmission control module (TCM), a brake control module (BCM or EBCM), a central control module (CCM), a central timing module (CTM), a general electronic module (GEM), a body control module (BCM), and a suspension control module (SCM). As the shift continues from more mechanical types of vehicles to more electronically based vehicles, vehicles are having more and more ECUs.

[0003] On-board diagnostics (OBD) refers to the self-diagnostic and reporting capabilities of a vehicle. In the United States, OBD is used to comply with federal emission standards to detect faults that may increase emissions from a vehicle's tailpipe. The main advantage of this is that the OBD system gives vehicle owners or repair technicians access to the state of various vehicle subsystems. OBD enables technicians to connect to a vehicle to obtain useful information stored in a memory device. However, in new model vehicles, the architectures of different vehicles are different. In current solutions using OBD, data generation where the architecture evolves is not permitted. The current method is difficult to use to acquire vehicle information.

Summary of the Invention

[0004] In at least one embodiment, a method for acquiring vehicle information includes presenting a menu to the user interface of the vehicle's infotainment system for acquiring vehicle information; selecting vehicle information to be acquired from a storage device associated with at least one electronic control unit of the vehicle via the menu; receiving vehicle information acquired based on the selection of vehicle information; generating a code having the vehicle information embedded within it; and displaying the code having the vehicle information embedded within it.

[0005] In at least one embodiment, a system for acquiring vehicle information comprises a storage device for storing computer-readable instructions and a processor connected to the storage device, wherein the processor is configured to execute computer-readable instructions for performing actions such as presenting a menu of the vehicle's infotainment system for acquiring vehicle information, receiving a selection of vehicle information to acquire from a storage device associated with at least one electronic control unit via the menu, receiving vehicle information acquired based on the selection of vehicle information, generating a code having embedded vehicle information, and displaying the code having embedded vehicle information.

[0006] In at least one embodiment, a computer program causes a processor to perform operations including presenting a menu to the user interface of a vehicle infotainment system for acquiring vehicle information; selecting vehicle information to acquire from a storage device associated with at least one electronic control unit via the menu; receiving vehicle information acquired based on the selection of vehicle information; generating a code having embedded vehicle information; and displaying the code having embedded vehicle information.

[0007] The aspects of this disclosure will be best understood from the following detailed description when read in conjunction with the accompanying drawings. Note that, in accordance with industry practice, various features are not depicted to a fixed scale. In fact, the dimensions of various features may be increased or decreased for the sake of clarity in the discussion. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 shows a vehicle cockpit according to at least one embodiment. [Figure 2] Figure 2 shows a user interface with options for different menu selections according to at least one embodiment. [Figure 3] Figure 3 shows a user interface for initiating the generation of vehicle information according to at least one embodiment. [Figure 4] Figure 4 shows a menu for selecting options for generating vehicle information, according to at least one embodiment. [Figure 5] Figure 5 shows the transition to the preset menu in at least one embodiment. [Figure 6] Figure 6 shows the transition to a custom menu in at least one embodiment. [Figure 7] Figure 7 shows a status display according to at least one embodiment. [Figure 8] Figure 8 shows a software stack for acquiring vehicle information using generated code, according to at least one embodiment. [Figure 9] Figure 9 is a flowchart of a method for obtaining vehicle information according to at least one embodiment. [Figure 10] Figure 10 is a high-level functional block diagram of a processor-based system according to at least one embodiment. [Modes for carrying out the invention]

[0009] The embodiments described herein illustrate examples for implementing different features of the subject matter provided. Below, for the sake of brevity of this disclosure, examples of components, values, behaviors, materials, arrangements, etc., are described. These are, of course, examples and are not intended to be limiting. Other components, values, behaviors, materials, arrangements, etc., are possible. For example, the formation of a first feature on or above a second feature in the following description includes embodiments in which the first and second features are formed in direct contact, and embodiments in which an additional feature is formed between the first and second features so that the first and second features cannot directly contact. In addition, this disclosure repeats reference numbers and / or letters in various embodiments. This repetition is for simplicity and clarity and is not intended to indicate relationships between the various embodiments and / or configurations discussed.

[0010] Furthermore, spatially relative terms, such as "down," "below," "up," and "above," are used herein for the sake of clarity and to describe the relationship between one element or feature and another, as shown in the figures. Spatially relative terms are intended to encompass different orientations of the device in use or operation, in addition to the orientation shown in the drawings. The device may otherwise be oriented (rotated 90 degrees or in other orientations), and the spatially relative descriptors used herein shall be interpreted accordingly.

[0011] In at least one embodiment, a method for obtaining vehicle information includes presenting a menu to the user interface of the vehicle's infotainment system for obtaining vehicle information; selecting vehicle information to be obtained from a storage device associated with at least one electronic control unit of the vehicle via the menu; receiving vehicle information obtained based on the selection of vehicle information; generating a code in which the vehicle information is embedded and has the vehicle information; and displaying a code in which the vehicle information is embedded and has the vehicle information.

[0012] Embodiments described herein provide methods that offer one or more advantages. For example, an infotainment system provides a menu for the user to select vehicle information to acquire. A preset menu allows the user to acquire a collection of preset information. A custom menu allows the user to select from a list of parameters for the vehicle information to acquire. Once the information is acquired, a code is generated and presented on the display, the code containing the acquired vehicle information. Furthermore, the system can initiate operation on each of multiple vehicles, such as a group of vehicles, and the user does not need to wait for information on a first vehicle to be obtained before triggering the acquisition of vehicle information on subsequent vehicles. The information can then be collected rapidly and sequentially from each vehicle at once.

[0013] Figure 1 shows a vehicle cockpit 100 according to at least one embodiment.

[0014] In Figure 1, the vehicle cockpit includes a steering wheel 110, an accelerator pedal 112, a brake pedal 114, an instrument panel 120, an infotainment system 130, and a climate control system 140. The climate control system 140 is also called a heating, ventilation, and air conditioning (HVAC) system. The infotainment system 130 includes any type of infotainment system of the vehicle having an interactive display. The steering wheel is part of the steering system, which the driver operates to control the steering system and the direction of the vehicle. By operating the steering wheel 110, the driver directs the direction of the vehicle to the front wheels via the linkage system. The accelerator pedal 112 is used to control the supply of fuel and air to the engine by applying pressure. The accelerator pedal 112 is also called the throttle or gas pedal. The brake pedal 114 is pressed to apply the brakes, which slows down and / or stops the vehicle.

[0015] The instrument panel 120 is part of the dashboard located behind the steering wheel 110. The instrument panel 120 includes various gauges and lights that update the driver with information about the vehicle's status. For example, the instrument panel 120 often includes a traction control indicator, engine temperature, tachometer, fuel gauge, speedometer, odometer, turn indicators, gear display, and various warning lights. The tachometer displays the engine's crankshaft rotations in revolutions per minute (RPM). The speedometer displays the vehicle's speed. The odometer displays the total miles traveled since the car was started. The fuel gauge shows how much fuel remains in the vehicle. The temperature gauge shows the current engine temperature. Alternatively, designated lights may be included to warn of engine temperature issues, such as engine overheating. Turn signals are lights that flash on either side of the vehicle to communicate to other drivers the direction in which the driver intends to turn. The gear display or gear position indicator shows the currently engaged gear, such as park, neutral, or drive. Warning lights communicate different status items of a vehicle. Vehicles have various features, such as pre-installed ESC and ABS, as well as more standard components or elements. Warning lights illuminate briefly at startup to allow the vehicle to be inspected and to confirm that the systems are in a safe and drivable state. Occasionally, one warning light may illuminate, indicating a problem with the engine, headlights, temperature, etc.

[0016] The infotainment system 130 is a combination of information and entertainment. The infotainment system 130 is a collection of hardware and software in a vehicle that provides audio and video entertainment / information. The infotainment system 130 includes any type of infotainment system in a vehicle having an interactive display. According to at least one embodiment, the infotainment system 130 presents a user interface for a menu that enables the user to generate vehicle-related information. The user interface may present a title bar 132 that provides an indicator of the current menu. Menu options 134, 136 are presented for selections to generate vehicle information that lead the user to different vehicle information generation operations. For example, menu options 134, 136 include a selector for selecting a preset menu and a selector for selecting a custom menu.

[0017] The climate control system 140 includes a control device for setting the temperature inside the vehicle and a control device for setting the operation of the climate control system 140, such as air conditioning, heating, defrosting, floor vents, defrosting vents, passenger vents, and combinations thereof. For example, there are vents located in different positions inside the vehicle, such as a vent 142 for providing central airflow, a vent 144 for providing airflow towards the driver, a vent 146 for providing airflow towards passengers, and a vent 148 at the top of the dashboard for defrosting the windshield 150. Additional vents may be located in different areas of the vehicle, such as the rear seat area, under the dashboard, etc.

[0018] Figure 2 shows a user interface 200 having options for different menu selections according to at least one embodiment.

[0019] The user interface 200 includes a title bar 210 that provides an indicator (label) of the current menu. In FIG. 2, the title bar 210 indicates the menu of vehicle XYZ. The user interface 200 includes a display area 220 for displaying additional menu options. The user interface 200 is provided, for example, as part of an infotainment system, which includes any type of infotainment system for a vehicle having an interactive display. Within the display area 220, a vehicle information generation menu 230 for selecting to generate vehicle information is displayed. The vehicle information is provided by a code such as a two-dimensional barcode (also referred to as a "QR code (registered trademark)") 232. The display area 220 can also display menu options 240 and other menu options 250.

[0020] FIG. 3 shows a user interface 300 for starting the generation of vehicle information according to at least one embodiment.

[0021] In FIG. 3, the user interface 300 includes a title bar 310 that provides an indicator of the current menu. The title bar 310 indicates the menu of vehicle XYZ. The user interface 300 again shows a display area 320 for displaying additional menu options. Within the display area 320, the vehicle information generation menu 330 is shown in a state where it is selected (as represented by the highlighted border) to start the generation of vehicle information. The vehicle information is provided by a code such as a two-dimensional barcode 332. Also, the display area 320 can display menu options 340 and other menu options 350.

[0022] FIG. 4 shows a menu 400 for selecting options for generating vehicle information according to at least one embodiment.

[0023] In FIG. 4, the menu 400 is displayed after selecting the vehicle information generation menu 330 as described above with reference to FIG. 3. The menu 400 includes a title bar 410 that provides an indicator of the current menu. The title bar 410 indicates the menu of vehicle XYZ. Within the display area 420, a preset generation menu 430 is displayed for user selection to generate vehicle information within a code such as a two-dimensional barcode based on preset parameters. A custom generation menu 440 is displayed for user selection and generates vehicle information in a code such as a two-dimensional barcode based on the selection of custom parameters. Here too, the display area 420 can display other menu options 450.

[0024] FIG. 5 shows the transition to a preset menu 500 according to at least one embodiment.

[0025] In FIG. 5, the preset generation menu 530 is selected and shown as represented by the border of the highlighted preset generation menu 530. The title bar 510 indicates the menu of vehicle XYZ. Within the display area 520, the preset generation menu 530 is shown as being selected to display a preset option menu 560. The display area 520 also shows an unselected custom generation menu selector 540, as well as other menu options 550.

[0026] Selecting the preset generation menu displays the preset options menu 560. The preset options menu 560 includes a title bar 562 that identifies navigation to a menu for selecting a preset. The preset options menu 560 includes a display area 520 that shows a set of pre-established information that the manufacturer considers to be of interest to a user, such as a mechanic or vehicle technician, for vehicle analysis and troubleshooting. For example, in at least one embodiment, the preset options menu 560 displays options for selecting tire information 570, options for selecting electric vehicle (EV) battery health information 580, and other menu options 590. The preset options menu 560 generates vehicle information using preset settings without the user having to select individual information.

[0027] Figure 6 shows the transition to the custom menu 600 in at least one embodiment.

[0028] In Figure 6, the custom generated menu 640 is selected and shown as represented by the highlighted border of the custom generated menu 640. The title bar 610 shows the vehicle XYZ menu. Within the display area 620, the preset generated menu 630 for displaying the preset options menu 560 is shown as unselected. The display area 620 also shows other menu options 650.

[0029] Selecting the custom generation menu 640 displays the custom options menu 660. The custom options menu 660 includes a title bar 662 that represents navigation to a menu for selecting custom information. The custom options menu 660 includes a display area 620 that shows individual pieces of information that can be selected for generating customized vehicle information.

[0030] The custom options menu 660 allows the user to select individual information as desired, such as battery statistics 670, tire pressure statistics 680, and onboard system software information 690. Each of the options, for example, battery statistics 670, tire pressure statistics 680, and onboard system software information 690, includes respective toggle buttons 672, 682, and 692 for selecting each option. In Figure 6, toggle button 672 indicates that battery statistics 670 is not selected, toggle button 682 indicates that tire pressure statistics 680 is not selected, and toggle button 692 indicates that onboard system software information 690 is selected. When the generate button 698 is selected, vehicle information related to onboard system software information 690 is generated.

[0031] Figure 7 shows a status display 700 according to at least one embodiment.

[0032] The status display 700 appears after selecting to generate preset information, as shown in the preset options menu 560 in Figure 5, or after selecting the generate button 698 in the custom options menu 660. In Figure 7, the title bar 710 indicates that vehicle information is being acquired for vehicle XYZ. The display area 720 indicates that vehicle information generation is in progress. The indicator light and arrow 730 indicate that vehicle information generation is in progress. A partial code 732, such as a partial two-dimensional barcode, is displayed. The status display 700 indicates that vehicle information generation is enabled and vehicle information is being downloaded.

[0033] After the selected vehicle information is downloaded, status display 760 is displayed. Status display 760 includes a title bar 762 that identifies the vehicle information obtained for vehicle XYZ. Display area 720 uses code 772 to indicate that the vehicle data is available for scan 770. Code 772 is either a two-dimensional barcode that can be displayed with the vehicle information embedded, or any other code. The two-dimensional barcode is presented to the user in display area 720, and the user can take a screenshot of the two-dimensional barcode or scan the two-dimensional barcode.

[0034] Other features can also be implemented. For example, the user can select predetermined vehicle information on the input / output device or input vehicle information that the user wishes to obtain. The user is authenticated, and user requests from the authenticated user are accepted.

[0035] In response to users managing multiple vehicles, users can trigger the collection of information and the generation of 2D barcodes for different vehicles using preset option menu 560 or custom option menu 660, without waiting for 2D barcodes to be generated. Then, after the 2D barcodes are generated, the user can scan them individually without physically connecting to each vehicle to download the vehicle information.

[0036] Therefore, the infotainment system presents a user interface that allows the user to generate vehicle information. With the preset options menu 560, the user does not need to select individual information; instead, they receive preset information. The custom options menu 660 allows users to select individual types of information of interest to them. The generated vehicle information is a snapshot of the vehicle information and does not represent live data. In response to users managing many vehicles, users can trigger this process for different vehicles, and then collect the information one by one after the vehicle information has been generated for each vehicle.

[0037] Figure 8 shows a software stack 800 for acquiring vehicle information using code generated according to at least one embodiment.

[0038] In Figure 8, the infotainment system 810 includes user interfaces 200, 300, and 820. The infotainment system 810 includes any type of infotainment system in a vehicle with an interactive display. Newer vehicle models have different vehicle architectures. Current solutions using OBD do not allow for data generation that adapts to evolving architectures. A Software Development Kit (SDK) is provided to allow for evolution in response to architectural changes.

[0039] The user interacts with the user interface 820 of the infotainment system 810, and the user interface 820 interacts with the software. The software then interacts with the appropriate vehicle information source 890.

[0040] The software handles the communication mechanism with the ECU and also provides the user interface 820. The Software Developer Kit (SDK) provides a variety of software tools and mechanisms together. The user interface 820 operates in the background and interacts with a background service 830 that collects data from different ECUs. The user interface 820 interacts with API 840, which contains a list of API calls 842. The developer updates the user interface 820 to be relevant to each vehicle, identifies API calls 842, and groups information within the generated code 880, such as 2D barcodes. The developer refers to the collection of API calls 842 located within the SDK.

[0041] The software is a stack of different applications controlled via the user interface 820. Different background services 830 collect vehicle information from a vehicle information source 890. The user interface 820 communicates with the background services 830, which actually operate in the background. The background services 830 make different API calls 842 to different vehicle information sources 890, for example, at least one electronic control unit (ECU). While the background services 830 are generating vehicle information, the user interface 820 displays it on the status display 870. When different data is collected, the background services 830 respond to the user interface 820 on the status display 870 to communicate that the vehicle information has been collected and is available.

[0042] The user interface 820 acquires data and generates a two-dimensional barcode 880 that is displayed on the status display 870. The background service 830 communicates with the appropriate ECU or other component to retrieve relevant vehicle information. For example, the background service 830 can communicate with the appropriate ECU via an API call 842.

[0043] Each of the vehicle information sources 890, for example, an ECU, provides different information, and the generated two-dimensional barcode 880 has the actual information embedded within it. The vehicle information within the generated two-dimensional barcode 880 can be encrypted or decrypted. For example, vehicle information can be encrypted and arranged in a predetermined format. The system recognizes the information available for searching. The interface with the background service 830 provides an API call 842 to the vehicle information source 890. The API call 842 contains details about the available information. Developers can update the user interface 820 and the API call 842 to relate to the actual information available for each vehicle.

[0044] The developer creates a user interface 820 with different types of vehicle information and groups the types of vehicle information as presets selected in a preset options menu 850 or a custom options menu 860 by referencing a collection of API calls 842 within the SDK.

[0045] The generated vehicle information depends on the capacity of the generated code 880, for example, the two-dimensional barcode. For example, in at least one embodiment, the capacity of the two-dimensional barcode is 8 kilobytes. However, the embodiments described herein are not limited to such capacity. Other codes can also be used with different capacity capabilities. Different two-dimensional barcodes can be cached, and sequences of two-dimensional barcodes can be presented. Alternatively, the generated vehicle data can be compressed to increase capacity. Real-time information can also be collected in real time, for example, using a smartphone, according to at least one embodiment. The generated two-dimensional barcode 880 can be periodically updated or refreshed to represent current information.

[0046] For example, in response to displaying information on the smartphone, the smartphone interacts with the infotainment system 810, and continuous communication with the background service 830 is performed periodically to retrieve current information.

[0047] According to at least one embodiment, the vehicle can supply data to a local server, and a user can connect directly to the vehicle via a computer, for example, via a web browser. However, this raises security concerns due to the nature of Wi-Fi® and wired connections to computers.

[0048] In response to users who wish to collect data from a group of vehicles, advantages are offered. Information retrieval can be triggered on one vehicle at a time, but the collection and generation of 2D barcodes 880 can be obtained depending on the availability of 2D barcodes. In contrast, with OBD, the user plugs a cable into each individual vehicle and waits for the data to be transferred. Thus, according to at least one embodiment, operation can be started on each vehicle, and the user does not have to wait until the information is ready to start operation on the next vehicle. The information can then be collected quickly and sequentially all at once.

[0049] Figure 9 is a flowchart 900 of a method for obtaining vehicle information according to at least one embodiment.

[0050] In Figure 9, the method starts at S902, and a menu is presented to the user interface to acquire vehicle information (S910). Referring to Figure 2, the vehicle information generation menu 230 is displayed in the display area 220 for selecting to generate vehicle information. Referring to Figure 3, the vehicle information generation menu 330 is selected in the display area 320 to start generating vehicle information (as the boundary is highlighted).

[0051] Vehicle information is selected via a menu in the user interface to be retrieved from a storage device associated with the electronic control unit (S914). Referring to Figure 4, a preset generation menu 430 is displayed in the display area 420 for the user to select how to generate vehicle information in a code such as a two-dimensional barcode based on preset parameters. A custom generation menu 440 is displayed for the user to select how to generate vehicle information in a code such as a two-dimensional barcode based on the selection of custom parameters.

[0052] Referring to Figure 5, the display area 520 shows the preset generation menu 530, which has been selected to display the preset options menu 560. Selecting the preset generation menu 530 displays the preset options menu 560. The preset options menu 560 includes the display area 520 of the preset options menu 560 and shows a set of pre-established information that the manufacturer assumes a user, such as a mechanic or vehicle technician, would be interested in obtaining for vehicle analysis and troubleshooting. For example, in at least one embodiment, the preset options menu 560 displays options for selecting tire information 570, options for selecting electric vehicle (EV) battery health information, and options for selecting other menu options 590. The preset options menu 560 generates vehicle information using preset settings without the user having to select individual information.

[0053] Referring to Figure 6, the display area 620 shows the preset generation menu 630 for displaying the preset options menu 560 as unselected. Selecting the custom generation menu 640 displays the custom options menu 660. The custom options menu 660 includes a display area 620 for the custom options menu 660 that shows individual pieces of information that can be selected for generating customized vehicle information. The custom options menu 660 allows the user to select individual pieces of information as desired, such as menus for selecting battery statistics 670, tire pressure statistics 680, onboard system software information 690, etc. Each of the options, for example, battery statistics 670, tire pressure statistics 680, and onboard system software information 690, includes their respective toggle buttons 672, 682, and 692 for selecting each option. In Figure 6, toggle button 672 indicates that battery statistics 670 is unselected, toggle button 682 indicates that tire pressure statistics 680 is unselected, and toggle button 692 indicates that onboard system software information 690 is selected. When the generate button 698 is selected, vehicle information related to the onboard system software information 690 is generated.

[0054] A call to the electronic control unit is made to obtain vehicle information (S918). Referring to Figure 8, the user interface 820 interacts with a background service 830 that operates in the background and collects data from different ECUs. The user interface 820 interacts with API 840, which contains a list of API calls 842. The user interface 820 communicates with the background service 830, which operates in the background. The background service 830 makes different API calls 842 to different vehicle information sources 890. The interface with the background service 830 provides the API calls 842 to the vehicle information sources 890. The API calls 842 contain details about the available information. Developers can update the user interface 820 and API calls 842 to relate to the actual information available for each vehicle. The developer creates a user interface 820 with different types of vehicle information and groups the types of vehicle information as presets selected in a preset options menu 850 or a custom options menu 860 by referencing a collection of API calls 842 within the SDK.

[0055] A status indicator associated with the status of the vehicle information being acquired is displayed (S922). Referring to Figure 7, the status display 700 is displayed after selecting to generate preset information as shown in the preset option menu 560 in Figure 5, or after selecting the generate button 698 in the custom option menu 660. The display area 720 indicates that the vehicle information is being generated. The indicator light and arrow 730 indicate that the vehicle information is being acquired. A partial code 732, such as a partial two-dimensional barcode, is displayed. The status display 700 indicates that the vehicle information is being generated and that the vehicle information is being downloaded. After the selected vehicle information has been downloaded, the status display 760 is displayed.

[0056] Vehicle information is received based on the selection of vehicle information via a menu in the user interface (S926). Referring to Figure 7, after the selected vehicle information is downloaded, a status display 760 is displayed. The status display 760 includes a title bar 762 representing the vehicle information obtained for vehicle XYZ. The display area 720 uses code 772 to indicate that the vehicle data is available for scan 770.

[0057] A code containing the returned vehicle information is generated and embedded within it (S930). Referring to Figure 8, the background service 830 makes different API calls 842 to different vehicle information sources 890, for example, one or more electronic control units (ECUs). While the background service 830 is generating vehicle information, the user interface 820 displays it on the status display 870. When different data is collected, the background service 830 responds to the user interface 820 on the status display 870 to communicate that the vehicle information has been collected and is available. The user interface 820 retrieves the data and generates a two-dimensional barcode 880 which is displayed on the status display 870.

[0058] A code containing the returned vehicle information is displayed (S934). Referring to Figure 7, the display area 720 uses code 772 to indicate that vehicle data is available for scanning 770. Code 772 is either a two-dimensional barcode or any other code that can be displayed with the vehicle information embedded. The two-dimensional barcode is presented to the user in the display area 720, and the user can take a screenshot of the two-dimensional barcode or scan the two-dimensional barcode.

[0059] The process then terminates (S940).

[0060] At least one embodiment of a method for obtaining vehicle information includes presenting a menu to the user interface of the vehicle's infotainment system for obtaining vehicle information; selecting vehicle information to be obtained from a storage device associated with at least one electronic control unit of the vehicle via the menu; receiving vehicle information obtained based on the selection of vehicle information; generating a code having the vehicle information embedded within it; and displaying the code having the vehicle information embedded within it.

[0061] Figure 10 is a high-level functional block diagram of a processor-based system 1000 according to at least one embodiment.

[0062] In at least one embodiment, the processing circuit 1000 acquires vehicle information and displays the acquired vehicle information as a code such as a two-dimensional barcode.

[0063] The processing circuit 1000 uses the processor 1002 to implement a method for acquiring vehicle information and displaying the acquired vehicle information in code. The processing circuit 1000 also includes a non-temporary computer-readable storage medium 1004 used to perform the acquisition of vehicle information and the display of the acquired vehicle information in code. The non-temporary computer-readable storage medium 1004 is, in particular, coded using instructions 1006, i.e., computer program code, which are executed by the processor 1002, causing the processor 1002 to perform operations for acquiring vehicle information and displaying the acquired vehicle information in code. The execution of instructions 1006 by the processor 1002 represents (at least in part) an application that implements at least a portion of the method described herein according to one or more embodiments (the processes and / or methods described below).

[0064] The processor 1002 is electrically coupled to a non-temporary computer-readable storage medium 1004 via a bus 1008. The processor 1002 is electrically coupled to an input / output (I / O) interface 1010 via the bus 1008. The network interface 1012 is also electrically connected to the processor 1002 via the bus 1008. The network interface 1012 is connected to a network 1014, thereby connecting the processor 1002 and the non-temporary computer-readable storage medium 1004 to external elements via the network 1014. The processor 1002 is configured to execute instructions 1006 encoded in the non-temporary computer-readable storage medium 1004, making the processing circuit 1000 available to execute at least a portion of a process and / or method. In one or more embodiments, the processor 1002 is a central processing unit (CPU), a multiprocessor, a distributed processing system, an application-specific integrated circuit (ASIC), and / or appropriate processing unit.

[0065] The processing circuit 1000 includes an I / O interface 1010. The I / O interface 1010 is coupled to an external circuit. In one or more embodiments, the I / O interface 1010 includes a keyboard, keypad, mouse, trackball, trackpad, touchscreen, and / or cursor directional keys for communicating information and commands to the processor 1002.

[0066] The processing circuit 1000 also includes a network interface 1012 coupled to the processor 1002. The network interface 1012 enables the processing circuit 1000 to communicate with a network 1014 to which one or more other computer systems are connected. The network interface 1012 includes wireless network interfaces such as Bluetooth®, Wi-Fi®, WiMAX (Worldwide Interoperability for Microwave Access: WiMAX®), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access (WCDMA®), or Ethernet®, Universal Serial Bus (USB®), or the Institute of Electrical and Electronics Engineers (IEICE) Network Interface Line network interface.

[0067] The processing circuit 1000 is configured to receive information via the I / O interface 1010. The information received via the I / O interface 1010 includes instructions, data, design rules, cell libraries, and / or other parameters for processing by the processor 1002. The network interface is transferred to the processor 1002 via the bus 1008. The processing circuit 1000 is configured to receive information related to the user interface (UI) 1022 via the I / O interface 1010. The information is stored as the UI 1022 in a non-temporary computer-readable storage medium 1004.

[0068] In one or more embodiments, one or more non-temporary computer-readable storage media 1004 storing instructions 1006 (in compressed or uncompressed form) that can be used to program a computer, processor, or other electronic device to perform the processes or methods described herein. The one or more non-temporary computer-readable storage media 1004 include one or more of the following: electronic storage media, magnetic storage media, optical storage media, quantum storage media, etc.

[0069] For example, non-temporary computer-readable storage media 1004 may include, but are not limited to, hard drives, floppy diskettes, optical discs, read-only memory (ROM), random access memory (RAM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, magnetic or optical cards, solid-state memory devices, or other types of physical media suitable for storing electronic instructions. In one or more embodiments using optical discs, one or more non-temporary computer-readable storage media 1004 may include CompactDisc® Read-Only Memory (CD-ROM), CompactDisc® Read / Write (CD-R / W), and / or Digital Video Disc (DVD®).

[0070] In one or more embodiments, the non-temporary computer-readable storage medium 1004 stores instructions 1006 configured to cause the processor 1002 to execute at least part of a process and / or method for acquiring vehicle information and representing the acquired vehicle information in code. In one or more embodiments, the non-temporary computer-readable storage medium 1004 also stores information such as algorithms that facilitate the execution of at least part of a process and / or method for acquiring vehicle information and representing the acquired vehicle information in code.

[0071] Accordingly, in at least one embodiment, the processor 1002 executes instructions 1006 stored on one or more non-temporary computer-readable storage media 1004 to perform vehicle information acquisition and display of the acquired vehicle information in code. The processor 1002 implements a user interface 1020 for an infotainment system 1030. The infotainment system 1030 includes any type of infotainment system for a vehicle having an interactive display. The processor 1002 is configured to provide a vehicle information generation menu 1022 within the user interface 1020. The processor 1002 is further configured to provide a preset generation menu 1024 and a custom generation menu 1026 to the vehicle information generation menu 1022. The processor 1002 receives vehicle information and displays a code display 1028 (e.g., a two-dimensional barcode) on the user interface 1020. The processor 1002 implements a vehicle information generation menu 1032 for selecting to acquire vehicle information, and when vehicle information is received, it presents a code such as a two-dimensional barcode on the code display 1028. The processor 1002 implements a preset generation menu 1034 for presenting a preset option menu 1050 for user selection to generate vehicle information in a code such as a two-dimensional barcode based on preset parameters. The processor 1002 implements a custom generation menu 1036 for presenting a custom option menu 1060, and generates vehicle information in a code such as a two-dimensional barcode based on the user's selection of custom parameters. The processor 1002 implements a preset option menu 1050 that shows a set of pre-established information that the user is interested in acquiring for vehicle analysis and troubleshooting. The preset option menu 1050 includes tire information 1052, electric vehicle (EV) battery health information 1054, and other menu options 1056. The processor 1002 implements a custom option menu 1060 to display individual pieces of information that can be selected for generating customized vehicle information.The custom options menu 1060 includes battery statistics 1062, tire pressure statistics 1064, onboard system software information 1066, and toggle buttons 1068 for selecting each of the options 1062, 1064, and 1066. The processor 1002 implements a status display 1038 to indicate the ongoing generation of vehicle information. The processor 1002 implements a background service 1072 that interacts with vehicle information sources to collect vehicle information from different vehicle information sources. The processor 1002 implements an API 1040 for API calls 1042 made by the background service 1072 to different sources of vehicle information to retrieve vehicle information according to the selection of a preset generation menu 1034 or a custom selection of a custom generation menu 1036. Once vehicle information is obtained, the processor 1002 presents a code on the code display 1070 (e.g., a two-dimensional barcode), where the code contains the retrieved vehicle information. The processor 1002 presents a user interface 1082 using the display 1080. The user interface 1082 presents a vehicle information generation menu 1084, allowing the user to select vehicle information to be obtained from a vehicle data source. The vehicle information generation menu 1084 further includes a preset generation menu 1086 and a custom generation menu 1088. The preset generation menu 1086 presents preset parameters that generate vehicle information in a code, such as a two-dimensional barcode, based on the preset parameters. The custom generation menu 1088 presents a custom options menu for the user to select custom parameters, and generates vehicle information in a code, such as a two-dimensional barcode, based on the selection of custom parameters. Once vehicle information is obtained, the code display 1090 presents a code, such as a two-dimensional barcode, which contains the obtained vehicle information.

[0072] Embodiments described herein provide methods that offer one or more advantages. For example, an infotainment system provides a menu for the user to select vehicle information to acquire. A preset menu allows the user to acquire a collection of preset information. A custom menu allows the user to select from a list of parameters for the vehicle information to acquire. Once the information is acquired, a code is generated and presented on the display, the code containing the acquired vehicle information. Furthermore, the system can initiate operation on each of multiple vehicles, such as a group of vehicles, and the user does not need to wait for information on a first vehicle to be obtained before triggering the acquisition of vehicle information on subsequent vehicles. The information can then be collected rapidly and sequentially from each vehicle at once.

[0073] Separate instances of these programs may run on any number of separate computer systems or be distributed across multiple computer systems. Therefore, while certain steps are described as being performed by a specific device, software program, process, or entity, this is not necessarily required. Various alternative implementations will be understood by those skilled in the art.

[0074] In addition, those skilled in the art will readily recognize that the above-described technology can be used in a variety of devices, environments, and situations. While the embodiments are described in language specific to structural features or methodological actions, the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described. Rather, specific features and actions are disclosed as exemplary forms for implementing the claims.

Claims

1. In order to obtain vehicle information, a menu is presented on the user interface of the vehicle's infotainment system, Selecting the vehicle information to be obtained from a storage device associated with at least one electronic control unit of the vehicle via the menu, Acquiring the vehicle information obtained based on the selection of the vehicle information, while displaying an indicator light, an arrow, and a partial code indicating that the vehicle information is being acquired, To generate a code having the embedded vehicle information, Displaying the code having the embedded vehicle information, including displaying a status indicator that the vehicle information is available for scanning, A method for obtaining vehicle information, which is executed by the processor.

2. The method according to claim 1, wherein presenting the menu includes the processor presenting a preset menu having a batch of pre-prepared information for which to choose to download.

3. The method according to claim 1, wherein presenting the menu includes the processor presenting a custom menu having the at least one selectable vehicle information type for selecting to download the vehicle information associated with the at least one selectable vehicle information type.

4. The method according to claim 3, wherein presenting the custom menu includes the processor presenting toggle buttons associated with each of the at least one selectable vehicle information types for selecting one or more of the at least one selectable vehicle information types.

5. The method according to claim 1, wherein presenting the menu includes the processor presenting a status indicator associated with the progress of the acquired vehicle information.

6. The method according to claim 1, wherein the code includes a two-dimensional barcode.

7. The method according to any one of claims 1 to 6, wherein selecting the vehicle information to be retrieved from the storage device associated with the at least one electronic control unit via the menu in the user interface includes presenting a status indicator associated with the status of the retrieved vehicle information.

8. A system for acquiring vehicle information, A memory device that stores computer-readable instructions, A processor connected to the aforementioned storage device, Equipped with, The aforementioned processor, The system displays the menu of the vehicle's infotainment system for obtaining vehicle information. The system receives a selection of vehicle information to be obtained from the storage device associated with at least one electronic control unit via the menu, The process involves acquiring the vehicle information obtained based on the selection of the vehicle information, while displaying an indicator light, an arrow, and a partial code to indicate that the vehicle information is being acquired. A code having the embedded vehicle information is generated, Displaying the code having the embedded vehicle information, including displaying a status indicator that the vehicle information is available for scanning, A system configured to execute computer-readable instructions for performing an action.

9. The system according to claim 8, wherein the menu is a preset menu that presents a batch of pre-prepared information for which to choose to download.

10. The system according to claim 8, wherein the menu is a custom menu that presents the at least one selectable vehicle information type for the selection of downloading the vehicle information associated with the at least one selectable vehicle information type.

11. The system according to claim 10, wherein the custom menu includes a toggle button associated with each of the at least one selectable vehicle information type for selecting one or more of the at least one selectable vehicle information type.

12. The system according to claim 8, wherein the menu presents a status indicator associated with the status of the acquired vehicle information.

13. The system according to claim 8, wherein the code includes a two-dimensional barcode.

14. The system according to any one of claims 8 to 13, wherein the processor is configured to present a status indicator associated with the status of the acquired vehicle information.

15. To present a menu on the user interface of the vehicle's infotainment system for acquiring vehicle information, Select the vehicle information to be obtained from a storage device associated with at least one electronic control unit via the menu, Acquiring the vehicle information obtained based on the selection of the vehicle information, while displaying an indicator light, an arrow, and a partial code indicating that the vehicle information is being acquired, To generate a code having the embedded vehicle information, Displaying the code having embedded vehicle information, including displaying a status indicator that the vehicle information is available for scanning, A computer program that causes a processor to perform an action that includes [a specific action].

16. The computer program according to claim 15, wherein presenting the menu includes presenting a preset menu having a batch of pre-prepared information for which to choose to download.

17. The computer program according to claim 15, wherein presenting the menu includes presenting a custom menu having at least one selectable vehicle information type for the selection of downloading the vehicle information associated with at least one selectable vehicle information type, and presenting toggle buttons associated with each of the at least one selectable vehicle information type for selecting one or more of the at least one selectable vehicle information type.

18. The computer program according to claim 15, wherein the presentation of the menu includes presenting a status indicator associated with the progress of the acquired vehicle information.

19. The computer program according to claim 15, wherein the code includes a two-dimensional barcode.

20. A computer program according to any one of claims 15 to 19, wherein selecting the vehicle information to be retrieved from the storage device associated with the at least one electronic control unit via the menu in the user interface includes presenting a status indicator associated with the status of the retrieved vehicle information.