Data collection device and method of operation thereof

Abstract

According to one embodiment of this disclosure, a data collection device installed in a vehicle includes: a memory storing at least one instruction; and a processor operatively connected to the memory, wherein the processor is capable of performing the following operations by executing at least one instruction: invoking a driver corresponding to a data storage medium connected to the data collection device; identifying the result of an access request to the data storage medium based on the invoked driver; setting an operating mode for the data storage medium based on the invoked driver when it is identified that access to the data storage medium has been completed; identifying the setting result of the operating mode; and outputting a result message based on the identified setting result of the operating mode.

Description

Technical Field

[0001] This application claims the benefit of Korean Patent Application No. 10-2024-0120054, filed on September 4, 2024, with the Korean Intellectual Property Office, the disclosure of which is incorporated herein by reference in its entirety.

[0002] The exemplary implementations disclosed in this document relate to data collection devices and methods of operation thereof. Background Technology

[0003] In recent years, active research and development have been carried out in the field of rechargeable batteries. Here, rechargeable batteries refer to batteries capable of charging and discharging, including conventional Ni / Cd and Ni / MH batteries, as well as the more recent lithium-ion batteries. Compared with conventional Ni / Cd and Ni / MH batteries, lithium-ion batteries among rechargeable batteries have the advantage of higher energy density. Furthermore, lithium-ion batteries can be manufactured in a compact and lightweight form for use as a power source for mobile devices, and in recent years, their application has expanded to electric vehicles, gaining attention as a next-generation energy storage device.

[0004] As the use of such secondary batteries has expanded, technologies related to management systems for the more efficient use and management of these batteries have become increasingly important. The state and operation of a secondary battery can be controlled by a battery management system (BMS). A BMS can be incorporated into a single device containing the battery.

[0005] Furthermore, the BMS can manage and control the battery in a state separate from the device including the battery. For example, the BMS can be implemented as a standalone server device. In this case, the BMS can collect battery and vehicle data from data collection devices installed on the vehicle, and manage and control the battery using the collected data.

[0006] Data collection devices can connect to hardware installed in a vehicle to collect data related to the vehicle and battery, and send the collected data to a server, enabling analysis of the vehicle and battery status. For example, the data collection device can collect data from the hardware installed in the vehicle using CAN (Controller Area Network) communication, store the data in a storage medium, and then send the stored data to a server via a wireless network.

[0007] Furthermore, when the data collection device fails to access the data storage medium, operating mode settings, or installation operations, it struggles to collect data properly, leading to issues with data stability and reliability. Additionally, while Secure Digital (SD) cards are used as existing data storage media for connecting to data collection devices, they are unsuitable for in-vehicle environments (e.g., temperature and vibration), exhibiting drawbacks such as functional malfunctions due to intermittent data errors and insufficient data stability during physical connections. Summary of the Invention

[0008] Technical issues

[0009] According to an example embodiment of this disclosure, a data collection device and its operating method can be provided, which can ensure data stability and reliability by determining whether to reactivate the drive corresponding to the data storage medium based on the results of access to the data storage medium, operating mode settings, and / or installation operations.

[0010] According to an example embodiment of this disclosure, a data collection device and its operation method using an eMMC (embedded multimedia controller) suitable for automotive environments (e.g., temperature and vibration) as a data storage medium can be provided.

[0011] The technical tasks to be achieved by the exemplary embodiments of this disclosure are not limited to the technical tasks described above, and other technical tasks can be derived from the exemplary embodiments described below.

[0012] Technical solution

[0013] A data collection device installed on a vehicle according to an exemplary embodiment of the present disclosure may include a memory storing at least one instruction and a processor operatively connected to the memory. By executing at least one instruction, the processor may invoke a driver corresponding to a data storage medium connected to the data collection device; identify the result of an access request to the data storage medium based on the invoked driver; when it is identified that access to the data storage medium has been completed, set an operating mode for the data storage medium based on the invoked driver; identify the result of setting the operating mode; and output a result message based on the identified result of setting the operating mode.

[0014] For a data collection device installed in a vehicle according to an example embodiment of this disclosure, when the processor recognizes a failure to access the data storage medium, the driver can be recalled.

[0015] For a data collection device installed on a vehicle according to an example embodiment of the present disclosure, the processor can set the operating mode by setting the input / output mode for the data storage medium to SDIO (Secure Digital Input / Output) 1-bit mode.

[0016] For a data collection device installed on a vehicle according to an example embodiment of the present disclosure, the processor can perform an installation operation on the data storage medium after setting an operating mode for the data storage medium; identify the result of performing the installation operation on the data storage medium; and identify the setting result of the operating mode when it is identified that the installation operation on the data storage medium has been completed.

[0017] For a data collection device installed on a vehicle according to an example embodiment of this disclosure, when the processor recognizes that the installation operation for the data storage medium has failed, the driver can be recalled.

[0018] For a data collection device installed on a vehicle according to an example embodiment of the present disclosure, the processor may output a setting completion message when it is identified that the setting of the operating mode for the data storage medium has been completed; when it is identified that the setting of the operating mode for the data storage medium has failed, it may identify whether the setting of the operating mode has been performed a predetermined number of times or more; when it is identified that the setting of the operating mode has been performed a predetermined number of times or more, it may output a setting failure message; and when it is identified that the setting of the operating mode has been performed less than a predetermined number of times, it may re-call the driver.

[0019] For a data collection device installed on a vehicle according to an example embodiment of the present disclosure, the data storage medium may be an eMMC (embedded multimedia controller).

[0020] An operation method of a data collection device installed on a vehicle according to an example embodiment of the present disclosure may include the following operations: invoking a driver corresponding to a data storage medium connected to the data collection device; identifying the result of an access request for the data storage medium based on the invoked driver; when it is identified that access to the data storage medium has been completed, setting an operating mode for the data storage medium based on the invoked driver; identifying the setting result of the operating mode; and outputting a result message based on the identified setting result of the operating mode.

[0021] The operation method of the data collection device installed on a vehicle according to the example embodiment of this disclosure may further include the following operation: re-calling the driver when an access failure to the data storage medium is detected.

[0022] For the operation method of the data collection device installed on a vehicle according to the exemplary embodiment of the present disclosure, the operation of setting the operating mode for the data storage medium may include the following operation: setting the operating mode for the data storage medium by setting at least one of the data input / output mode, input voltage, communication path and communication frequency for the data storage medium.

[0023] For the operation method of the data collection device installed on a vehicle according to the example embodiment of the present disclosure, the operation of setting the operating mode for the data storage medium may include the following operation: setting the operating mode by setting the input / output mode for the data storage medium to SDIO 1-bit mode.

[0024] The operation method of the data collection device installed on a vehicle according to the example embodiment of the present disclosure may further include the following operations: after setting an operation mode for a data storage medium, performing an installation operation for the data storage medium; identifying the result of performing the installation operation for the data storage medium; and when it is identified that the installation operation for the data storage medium has been completed, identifying the setting result of the operation mode.

[0025] The operation method of the data collection device installed on a vehicle according to the example embodiment of this disclosure may further include the following operation: re-calling the driver when it is identified that the installation operation for the data storage medium has failed.

[0026] For the operation method of the data collection device installed on a vehicle according to the example embodiment of the present disclosure, the operation of outputting the result message may include the following operations: when it is identified that the setting of the operating mode for the data storage medium has been completed, outputting a setting completion message; when it is identified that the setting of the operating mode for the data storage medium has failed, identifying whether the setting of the operating mode has been performed a predetermined number of times or more; when it is identified that the setting of the operating mode has been performed a predetermined number of times or more, outputting a setting failure message; and when it is identified that the setting of the operating mode has been performed less than a predetermined number of times, re-calling the driver.

[0027] Beneficial effects

[0028] According to the example implementations disclosed in this document, data stability and reliability can be ensured by determining whether to reactivate the driver corresponding to the data storage medium based on the results of access to the data storage medium, operating mode settings, and / or installation operations.

[0029] According to an example implementation of this disclosure, by using an eMMC (embedded multimedia controller) suitable for the vehicle environment (e.g., temperature and vibration) as the data storage medium, problems such as malfunctions due to data errors and insufficient data stability during physical connections can be prevented.

[0030] The effects of the present invention are not limited to those described above, and those skilled in the art can clearly understand other effects not explicitly described from the scope of the claims. Attached Figure Description

[0031] Figure 1 This is a block diagram of a system according to an exemplary embodiment of the present disclosure.

[0032] Figure 2 This is a block diagram of a data collection device according to an exemplary embodiment of the present disclosure.

[0033] Figure 3 This is a diagram used to describe the operations performed by a data collection device based on a drive corresponding to a data storage medium, according to an exemplary embodiment of this disclosure.

[0034] Figure 4 This is an operation flowchart of a data collection device according to an exemplary embodiment of the present disclosure.

[0035] Figure 5 This is an operation flowchart of a data collection device according to an exemplary embodiment of the present disclosure.

[0036] Figure 6 This is an operation flowchart of a data collection device according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0037] For the purpose of describing exemplary embodiments, descriptions of technical content that is well-known in the art to which this disclosure pertains and is not directly related to this disclosure will be omitted. This is to convey the subject matter of this disclosure more clearly without obscuring it by omitting unnecessary descriptions.

[0038] For the same reason, some components are enlarged, omitted, or schematically illustrated in the accompanying drawings. Additionally, the dimensions of each component do not perfectly reflect its actual size. Identical or corresponding components in each drawing are given the same reference numerals.

[0039] The advantages and features of this disclosure, as well as methods of implementing them, will become apparent from the following exemplary embodiments, which will be described in more detail with reference to the accompanying drawings. However, it should be noted that this disclosure is not limited to the following exemplary embodiments and can be implemented in various forms. Therefore, the exemplary embodiments are provided only to disclose this disclosure and to inform those skilled in the art of its scope, which is defined only by the scope of the claims. Throughout this specification, the same reference numerals or reference signs denote the same parts.

[0040] Here, it should be understood that each block and combination of blocks illustrated in the flowchart can be executed by computer program instructions. Since these computer program instructions can be mounted on a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, those instructions, which execute via the processor of the computer or other programmable data processing equipment, can create means for performing the functions described in the flowchart blocks. These computer program instructions can be stored in a computer-usable or computer-readable storage device that can be implemented in a particular manner for a computer or other programmable data processing equipment; therefore, the computer program instructions stored in a computer-usable or computer-readable storage device can produce an article of art containing instruction means for performing the functions described in the flowchart blocks. The computer program instructions can also be mounted on a computer or other programmable data processing equipment such that a series of operational steps can be performed on the computer or other programmable data processing equipment to create a computer-implemented process for creating computer or other programmable data. The instructions for executing the processing equipment can also provide steps for performing the functions described in the flowchart blocks.

[0041] Additionally, each box may represent a module, segment, or portion of code that includes one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in the boxes may occur out of order. For example, depending on the corresponding function, two boxes shown consecutively may actually execute substantially simultaneously, or these boxes may sometimes execute in reverse order.

[0042] Additionally, the term "unit" refers to software or hardware components such as FPGAs or ASICs. A "unit" performs certain functions. However, a "unit" is not limited to software or hardware. A "unit" can be configured to reside in addressable storage media or to reboot one or more processors. Thus, for example, a "unit" includes components such as software components, object-oriented software components, class components, and task components, and includes procedures, functions, properties, programs, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within components and "units" can be combined into a smaller number of components and "units," or can be further divided into additional components and "units." Furthermore, components and "units" can be implemented as one or more CPUs within a rebooting device or a secure multimedia card.

[0043] The expression “at least one of A, B and C” described in this specification may indicate the following meanings, including: only A; only B; only C; both A and B; both A and C; both B and C; or all three of A, B and C.

[0044] In this disclosure, a "terminal" can be implemented as a computer or portable terminal capable of accessing a server or another terminal via a network. Here, a computer can include, for example, a laptop, desktop computer, and laptop computer equipped with a web browser. A portable terminal can be a wireless communication device that ensures portability and mobility, and includes any type of handheld wireless communication device (e.g., tablet PC, smartphone, communication-based terminal such as IMT (International Mobile Telecommunications), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), and LTE (Long Term Evolution)).

[0045] In the following description, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings, enabling those skilled in the art to readily implement the present disclosure. However, the present disclosure may be embodied in many different forms and is not limited to the embodiments described herein.

[0046] In the following, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0047] Figure 1 This is a block diagram of a system according to an exemplary embodiment of the present disclosure.

[0048] Reference Figure 1 The system may include a vehicle 100, a data collection device 200, a server 300, and a data storage medium 400.

[0049] Vehicle 100 may be an electric vehicle (EV) that receives driving force from a battery that stores electricity, but is not limited thereto. The technical concepts disclosed herein can be applied to electric vehicles other than vehicle 100 (e.g., electric scooters).

[0050] According to an example implementation, vehicle 100 may include battery pack 110, vehicle controller 120, and vehicle network 120.

[0051] According to an example implementation, the battery pack 110 may include a battery for storing the power required to drive the vehicle 100 and a BMS (Battery Management System) for controlling the operation of the battery. The BMS may control the charging and discharging of the battery and also transmit battery state data to the vehicle network 130. This battery state data includes at least one of data acquired by sensing the state of the battery (e.g., voltage, current, resistance, and temperature) and data generated by processing the acquired data (e.g., SOC (State of Charge) and SOH (State of Health)).

[0052] According to an example embodiment, the vehicle controller 120 can control the overall operation of the vehicle 100 by controlling the battery pack 110, at least one sensor (e.g., a radar sensor and a temperature sensor) disposed in the vehicle 100, and at least one control device (e.g., a driving device, a braking device, a steering device, an ADS (Autonomous Driving System), and a TMS (Telematics Management System)). According to another example embodiment, the vehicle controller 120 may refer to an ECU (Electronic Control Unit) for controlling certain components of the vehicle 100.

[0053] According to an example implementation, vehicle controller 120 may store vehicle identification information unique to vehicle 100 and send the vehicle identification information in response to a request from an external source (e.g., data collection device 200). According to an example implementation, the vehicle identification information may include a VIN (Vehicle Identification Number). Vehicle controller 120 may communicate with another device located inside or outside vehicle 100 via vehicle network 130.

[0054] According to an example implementation, vehicle network 130 can provide a communication environment that enables components within vehicle 100 to send and receive data from each other. Vehicle network 130 may be a CAN (Controller Area Network) where components in vehicle 100 are connected in parallel and thus able to communicate with each other without a host, but is not limited to this. Vehicle network 130 can provide an environment that allows connection of external devices (e.g., data collection device 200) so that the external devices can communicate with another device (e.g., battery pack 110) via vehicle network 130. However, vehicle network 130 may have a communication protocol that varies depending on the type of vehicle 100, and only external devices equipped with firmware compatible with the communication protocol corresponding to the type of vehicle 100 can communicate normally by accessing vehicle network 130. Here, vehicle type information may refer to information such as brand, category, and year of manufacture used to identify the model of vehicle 100.

[0055] According to an example implementation, the data collection device 200 may be a device installed on vehicle 100 to connect to vehicle network 130. For example, the data collection device 200 may be an on-board diagnostic (OBD) port located in vehicle 100. The data collection device 200 may connect to vehicle network 130 and send and receive UDS (Unified Diagnostic Service) data to obtain vehicle status information related to the state of vehicle 100 from components in vehicle 100. Here, vehicle status information may include vehicle 100 speed data, driving distance data, driving time data, driving position data, and battery status data.

[0056] According to an example implementation, the data collection device 200 can send vehicle status information to the server 300 via connection 101. According to an example implementation, the connection 101 between the data collection device 200 and the server 300 can be a communication connection via a wired network and / or a wireless network. In an example implementation, the wired network can be based on LAN (Local Area Network) communication or powerline communication. In an example implementation, the wireless network can be based on a short-range communication network (e.g., Bluetooth, Wi-Fi, or IrDA (Infrared Data Association)) or a long-range communication network (e.g., a cellular network, a 4G network, or a 5G network).

[0057] According to the example implementation, server 300 can receive vehicle status information from data collection device 200 by sending data to data collection device 200 and receiving data from data collection device 200, and can provide management services for vehicle 100 or battery pack 110 by storing and analyzing vehicle status information.

[0058] According to an example embodiment, the data collection device 200 can store vehicle status information in the data storage medium 400 via connection 102. According to the example embodiment, the connection 102 between the data collection device 200 and the data storage medium 400 can be a data communication bus for connecting a memory interface provided in the data collection device 200 and the data storage medium 400. Here, the memory interface can be a component of the data collection device 200 that operates to provide mechanical and electrical connections to various memory media.

[0059] According to the example implementation, the data storage medium 400 may be an embedded memory. For example, the data storage medium 400 may be an eMMC (embedded multimedia controller).

[0060] Figure 2 This is a block diagram of a data collection device 200 according to an exemplary embodiment of the present disclosure. Figure 2 Data collection device 200 and Figure 2 The data collection device 200 has the same configuration, so redundant descriptions of the above can be omitted.

[0061] Reference Figure 2 The data collection device 200 may include a communication circuit 210, a memory 220, and a processor 230. According to an example embodiment, Figure 2 The data collection device 200 shown may also include, in addition to Figure 2 At least one component other than the components shown (e.g., a display, input device, or output device).

[0062] According to an example implementation, the communication circuit 210 can establish a wired communication channel and / or a wireless communication channel between the data collection device 200 and electronic devices (e.g., server 300 and data storage medium 400), and send and receive data with the electronic devices through the established communication channels.

[0063] According to an example implementation, memory 220 may include volatile memory and / or non-volatile memory.

[0064] According to an example implementation, memory 220 may store data used by at least one component of data collection device 200 (e.g., processor 230). For example, the data may include software (or related instructions), input data, or output data. In the example implementation, the instructions, when executed by processor 230, may enable data collection device 200 to perform operations defined by the instructions.

[0065] According to the example implementation, memory 220 may store a driver corresponding to data storage medium 400. For example, the driver may perform at least one of the following: access request to data storage medium 400, identification of access request result, setting of operating mode, and installation operation.

[0066] According to an example embodiment, processor 230 may be implemented as a computer or similar device, in hardware, software, or a combination thereof. In hardware, processor 230 may be implemented as electronic circuitry that processes electrical signals and performs control functions, and in software, it may be implemented as a program that drives the hardware processor 230. According to an example embodiment, processor 230 may be operatively connected to components (e.g., communication circuitry 210 and / or memory 220) included in data collection device 200 to control the connected components.

[0067] According to an example implementation, processor 230 may include a central processing unit, an application processor, a graphics processing unit, a neural network processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor.

[0068] In the following text, refer to Figure 3 This will describe the operations performed by the data collection device 200 by invoking a drive corresponding to the data storage medium 400 stored in the memory 220.

[0069] Figure 3 This is a diagram used to describe the operations performed by the data collection device 200 based on a drive corresponding to the data storage medium 400 according to an exemplary embodiment of this disclosure.

[0070] Reference Figure 3The processor 230 can invoke a driver 235 (e.g., an eMMC driver) corresponding to the data storage medium 400 stored in the memory 220, and perform various operations related to the data storage medium 400 based on the invoked driver 235.

[0071] According to the example implementation, the processor 230 can request access to the data storage medium 400 based on the driver 235. Additionally, the processor 230 can identify the result of the access request for the data storage medium 400 based on the driver 235.

[0072] According to the example implementation, when the processor 230 recognizes that access to the data storage medium 400 has been completed, the processor 230 can set the operating mode for the data storage medium 400 based on the driver 235. According to the example implementation, the processor 230 can set the operating mode for the data storage medium 400 by setting at least one of the input / output mode, input voltage, communication path, and communication frequency for the data storage medium 400. For example, the processor 230 can set the data input / output mode for the data storage medium 400 to SDIO (Secure Digital Input / Output) 1-bit mode. Additionally, the processor 230 can set the number of data buses used for communication with the data storage medium 400 and whether to apply pull-up resistors within the data buses.

[0073] According to an example implementation, when the processor 230 detects a failure to access the data storage medium 400, the processor 230 can re-call the driver 235 stored in the memory 220. In this case, the processor 230 can perform the operations described in this disclosure again based on the re-called driver 235.

[0074] According to the example implementation, processor 230 can perform an installation operation on data storage medium 400. For example, after setting an operating mode for data storage medium 400, processor 230 can perform an installation operation on data storage medium 400 based on driver 235. Here, the installation operation may be the processor 230 accessing data storage medium 400 as memory to perform data read and write processes. For example, processor 230 can connect processor 230 and a specific directory of data storage medium 400 through the installation operation.

[0075] According to the example implementation, the processor 230 can recognize the result of performing an installation operation on the data storage medium 400.

[0076] According to an example implementation, when the processor 230 detects a failure in the installation operation for the data storage medium 400, the processor 230 can re-call the driver 235 stored in the memory 220. In this case, the processor 230 can re-execute the operations described in this disclosure based on the re-called driver 235.

[0077] According to an example implementation, when the processor 230 recognizes that the installation operation for the data storage medium 400 has been completed, the processor 230 can identify the setting result of the operating mode for the data storage medium 400. According to another example implementation, the processor 230 can identify the setting result of the operating mode for the data storage medium 400, regardless of the execution result of the installation operation for the data storage medium 400.

[0078] According to the example implementation, when the processor 230 recognizes that the setting of the operating mode for the data storage medium 400 has been completed, the processor 230 can output a setting completion message. For example, the processor 230 can output the setting completion message through an output device (e.g., a display) provided in the data collection device 200. As another example, the processor 230 can send the setting completion message to an external device (e.g., a server 300) using the communication circuit 210.

[0079] According to the example implementation, when the setting of the operating mode for the data storage medium 400 fails, the processor 230 can identify whether the setting of the operating mode for the data storage medium 400 has been executed a predetermined number of times (e.g., three times) or more.

[0080] According to an example implementation, when the processor 230 recognizes that the setting of the operating mode for the data storage medium 400 has been performed a predetermined number of times or more, the processor 230 may output a setting failure message. For example, the processor 230 may output the setting failure message through an output device (e.g., a display) provided in the data collection device 200. Alternatively, the processor 230 may send the setting failure message to an external device (e.g., a server 300) using communication circuitry 210.

[0081] According to an example implementation, when the processor 230 detects that the settings for the operating mode of the data storage medium 400 have been executed less than a predetermined number of times, the processor 230 may recall the driver 235 stored in the memory 220. In this case, the processor 230 may perform the operations described in this disclosure again based on the recalled driver 235.

[0082] Figure 4 This is an operation flowchart of a data collection device according to an exemplary embodiment of the present disclosure. Because... Figure 4The operation method can be provided by Figure 1 and Figure 2 The data collection device 200 performs the operation, therefore redundant descriptions of the above content can be omitted, and it can be performed by using... Figure 1 and Figure 2 It is described by its components.

[0083] Figure 4 The illustrated embodiments are merely examples. The order of operations according to the various illustrated embodiments of this disclosure may differ. Figure 4 The operation sequence shown can be omitted. Figure 4 Some of the operations shown can be changed in order or combined.

[0084] Reference Figure 4 In operation 410, the data collection device 200 can invoke a drive corresponding to the data storage medium 400. Here, the drive can be stored in the memory 220 of the data collection device 200.

[0085] In operation 420, data collection device 200 can identify the result of an access request for data storage medium 400 based on the driver invoked in operation 410.

[0086] In operation 420, when an access failure to the data storage medium 400 is detected, the data collection device 200 can return to operation 410 and re-call the drive corresponding to the data storage medium 400.

[0087] In operation 420, when it is recognized that access to the data storage medium 400 has been completed, in operation 430, the data collection device 200 can set the operating mode for the data storage medium 400 based on the driver invoked in operation 410. According to an example embodiment, the data collection device 200 can set the operating mode for the data storage medium 400 by setting at least one of the following: input / output mode, input voltage, communication path, and communication frequency.

[0088] In operation 440, the data collection device 200 can identify the setting results of the operating mode for the data storage medium 400 executed in operation 430.

[0089] In operation 450, the data collection device 200 can output a result message based on the setting results of the operating mode for the data storage medium 400 identified in operation 440.

[0090] This will be described below. Figure 6To describe in more detail the operations 440 and 450, which involve the data collection device 200 identifying the settings for the operating mode of the data storage medium 400 and outputting result messages based on the identified results.

[0091] Figure 5 This is an operation flowchart of a data collection device according to an exemplary embodiment of the present disclosure. Because... Figure 5 The operation method can be provided by Figure 1 and Figure 2 The data collection device 200 performs the operation, therefore redundant descriptions of the above content can be omitted, and it can be performed by using... Figure 1 and Figure 2 It is described by its components.

[0092] Figure 5 The illustrated embodiments are merely examples. The order of operations according to the various illustrated embodiments of this disclosure may differ. Figure 5 The operation sequence shown can be omitted. Figure 5 Some of the operations shown can be changed in order or combined.

[0093] Reference Figure 5 In operation 510, the data collection device 200 can invoke the drive corresponding to the data storage medium 400. Here, the drive can be stored in the memory 220 of the data collection device 200.

[0094] In operation 520, the data collection device 200 can identify the result of an access request for the data storage medium 400 based on the invoked drive.

[0095] In operation 520, when an access failure to the data storage medium 400 is detected, the data collection device 200 can return to operation 510 and re-call the drive corresponding to the data storage medium 400.

[0096] In operation 520, when it is recognized that access to the data storage medium 400 has been completed, in operation 530, the data collection device 200 can set the operating mode for the data storage medium 400 based on the driver invoked in operation 510. According to an example embodiment, the data collection device 200 can set the operating mode for the data storage medium 400 by setting at least one of the following: input / output mode, input voltage, communication path, and communication frequency.

[0097] In operation 540, the data collection device 200 can perform an installation operation on the data storage medium 400. Here, the installation operation may involve the data collection device 200 accessing the data storage medium 400 as a memory to perform data reading and writing processes.

[0098] In operation 550, the data collection device 200 can identify the execution result of the installation operation in operation 540.

[0099] In operation 550, when an installation failure is detected, the data collection device 200 can re-call the drive corresponding to the data storage medium 400.

[0100] In operation 550, when it is recognized that the installation operation has been completed, in operation 560, the data collection device 200 can recognize the setting results of the operating mode for the data storage medium 400 executed in operation 530.

[0101] In operation 570, the data collection device 200 can output a result message based on the setting results of the operating mode for the data storage medium 400 identified in operation 560.

[0102] This will be described below. Figure 6 To describe in more detail the operations 560 and 570, which involve the data collection device 200 identifying the settings for the operating mode of the data storage medium 400 and outputting result messages based on the identified results.

[0103] Figure 6 This is an operation flowchart of a data collection device according to an exemplary embodiment of the present disclosure. Because... Figure 6 The operation method can be provided by Figure 1 and Figure 2 The data collection device 200 performs the operation, therefore redundant descriptions of the above content can be omitted, and it can be performed by using... Figure 1 and Figure 2 It is described by its components.

[0104] Figure 6 The illustrated embodiments are merely examples. The order of operations according to the various illustrated embodiments of this disclosure may differ. Figure 6 The operation sequence shown can be omitted. Figure 6 Some of the operations shown can be changed in order or combined.

[0105] Reference Figure 6 In operation 610, the data collection device 200 can identify... Figure 4 (or Figure 5 The result of setting the operating mode for data storage medium 400 in operation 430 (or operation 530).

[0106] In operation 610, when it is recognized that the setting of the operating mode for the data storage medium 400 has been completed, in operation 620, the data collection device 200 can output a setting completion message. For example, the data collection device 200 can output the setting completion message through an output device (e.g., a display) provided in the data collection device 200. Alternatively, the data collection device 200 can send the setting completion message to an external device (e.g., a server 300) using communication circuitry 210.

[0107] In operation 610, when it is identified that the setting of the operating mode for the data storage medium 400 has failed, in operation 630, the data collection device 200 may identify whether the setting of the operating mode for the data storage medium 400 has been performed a predetermined number of times (e.g., three times) or more.

[0108] In operation 630, when it is identified that the setting for the operating mode of the data storage medium 400 has been performed a predetermined number of times or more (“Yes”), in operation 640, the data collection device 200 may output a setting failure message. For example, the data collection device 200 may output the setting failure message through an output device (e.g., a display) configured in the data collection device 200. Alternatively, the data collection device 200 may send the setting failure message to an external device (e.g., server 300) using communication circuitry 210.

[0109] In operation 630, if it is identified that the settings for the operating mode of the data storage medium 400 have been executed less than a predetermined number of times ("No"), in operation 650, the data collection device 200 may re-call the drive corresponding to the data storage medium 400.

[0110] The data collection device according to the above example embodiments may include a processor, a memory for storing and executing program data, a permanent memory such as a disk drive, a communication port for communicating with external devices, and a user interface device such as a touch panel, keys, and icons. Methods implemented as software modules or algorithms can be stored as computer-readable code or program instructions executable by a processor in a computer-readable recording medium. Here, the computer-readable recording medium may include magnetic storage media (e.g., ROM (Read-Only Memory), RAM (Random Access Memory), floppy disks, hard disks) and optical reading media (e.g., CD-ROMs, DVDs). The computer-readable recording medium may be distributed across a computer system connected via a network, and the computer-readable code may be stored and executed in a distributed manner. The medium can be read by a computer, stored in memory, and executed by a processor.

[0111] This example implementation can be represented by functional blocks and various processing steps. These functional blocks can be implemented by various numbers of hardware and / or software configurations that perform specific functions. For example, this example implementation can employ integrated circuit configurations such as memory, processors, logic circuits, and lookup tables that can perform various functions by controlling one or more microprocessors or other control devices. Similar to components that can be executed by software programming or software components, this example implementation can be implemented by programming or scripting languages ​​such as C, C++, Java, and assembly languages, including various algorithms implemented by combinations of data structures, procedures, routines, or other programming configurations. Functional aspects can be implemented by algorithms executed by one or more processors. In addition, this example implementation can employ related techniques for electronic environment setup, signal processing, and / or data processing. The terms “mechanism,” “component,” “means,” and “configuration” are used broadly and are not limited to mechanical and physical elements. These terms can include the meaning of a series of software routines associated with a processor.

[0112] The above-described exemplary embodiments are merely examples, and other exemplary embodiments may be implemented within the scope of the appended claims.

Claims

1. A data collection device installed on a vehicle, the device comprising: A memory configured to store at least one instruction; as well as A processor, operatively connected to the memory, The processor is configured to perform the following operations by executing the at least one instruction: Call the drive corresponding to the data storage medium connected to the data collection device; The result of the access request for the data storage medium is identified based on the invoked driver; When it is determined that access to the data storage medium has been completed, the operating mode for the data storage medium is set based on the invoked driver; Identify the setting result of the operating mode; and The result message is output based on the settings result of the identified operating mode.

2. The device according to claim 1, wherein, The processor is configured to re-invoke the driver when it detects a failure to access the data storage medium.

3. The device according to claim 1, wherein, The processor is configured to set the operating mode for the data storage medium by setting at least one of the following: data input / output mode, input voltage, communication path, and communication frequency.

4. The device according to claim 3, wherein, The processor is configured to set the operating mode by setting the input / output mode for the data storage medium to Secure Digital Input / Output SDIO 1-bit mode.

5. The device according to claim 1, wherein, The processor is configured to: After setting the operating mode for the data storage medium, the installation operation for the data storage medium is performed; Identify the result of performing the installation operation on the data storage medium; as well as When it is determined that the installation operation for the data storage medium has been completed, the setting result of the operating mode is identified.

6. The device according to claim 5, wherein, The processor is configured to re-call the driver when it is detected that the installation operation for the data storage medium has failed.

7. The device according to claim 1, wherein, The processor is configured to: When it is identified that the settings for the operating mode of the data storage medium have been completed, a settings completion message is output; When it is identified that the setting of the operating mode for the data storage medium has failed, it is identified whether the setting of the operating mode has been executed a predetermined number of times or more. When the setting of the identified operating mode is executed the predetermined number of times or more, a setting failure message is output; as well as When it is identified that the settings of the operating mode have been executed less than the predetermined number of times, the driver is called again.

8. The device according to claim 1, wherein, The data storage medium is an embedded multimedia controller (eMMC).

9. A method of operating a data collection device installed on a vehicle, the method comprising the following operations: Call the drive corresponding to the data storage medium connected to the data collection device; The result of the access request for the data storage medium is identified based on the invoked driver; When it is determined that access to the data storage medium has been completed, the operating mode for the data storage medium is set based on the invoked driver; Identify the setting result of the operating mode; as well as The result message is output based on the settings result of the identified operating mode.

10. The method of claim 9, further comprising: when an access failure to the data storage medium is detected, resuming the driver.

11. The method according to claim 9, wherein, Setting the operating mode for the data storage medium includes the following operations: setting the operating mode for the data storage medium by setting at least one of the data input / output mode, input voltage, communication path, and communication frequency for the data storage medium.

12. The method according to claim 11, wherein, Setting the operating mode for the data storage medium includes the following operation: setting the operating mode by setting the input / output mode for the data storage medium to Secure Digital Input / Output SDIO 1-bit mode.

13. The method according to claim 9, further comprising the following operations: After setting the operating mode for the data storage medium, the installation operation for the data storage medium is performed. Identify the result of performing the installation operation on the data storage medium; as well as When it is determined that the installation operation for the data storage medium has been completed, the setting result of the operating mode is identified.

14. The method of claim 13, further comprising: when it is identified that the installation operation for the data storage medium has failed, resuming the drive.

15. The method according to claim 9, wherein, The operations for outputting the result message include the following: When it is identified that the settings for the operating mode of the data storage medium have been completed, a settings completion message is output; When it is identified that the setting of the operating mode for the data storage medium has failed, it is identified whether the setting of the operating mode has been executed a predetermined number of times or more. When the setting of the identified operating mode is executed the predetermined number of times or more, a setting failure message is output; as well as The driver is reactivated when the settings of the identified operating mode are executed less than the predetermined number of times.

Images