Data collection device and operation method thereof

Abstract

A data collection device mounted in a vehicle, according to one embodiment of the present disclosure, comprises: a memory storing at least one instruction; and a processor operatively connected to the memory, wherein the processor, by executing the at least one instruction, is capable of: calling a driver corresponding to a data storage medium connected to the data collection device; identifying an access request result for the data storage medium on the basis of the called driver; when access to the data storage medium is identified as completed, setting an operation mode for the data storage medium on the basis of the called driver; identifying a setting result of the operation mode; and outputting a result message on the basis of the identified setting result of the operation mode.

Description

Data collection device and its operating method

[0001] This application claims the benefit of priority to Republic of Korea Patent Application No. 10-2024-0120054, filed September 4, 2024, the entire contents of which are incorporated herein by reference.

[0002] The embodiments disclosed in this document relate to a data collection device and a method of operating the same.

[0003] Recently, research and development on secondary batteries has been actively conducted. Here, secondary batteries are rechargeable and include both conventional Ni / Cd and Ni / MH batteries, as well as recent lithium-ion batteries. Among secondary batteries, lithium-ion batteries have the advantage of having a much higher energy density than conventional Ni / Cd and Ni / MH batteries. Furthermore, lithium-ion batteries can be manufactured in a compact and lightweight form, making them suitable for use as power sources for mobile devices. Recently, their use has expanded to include power sources for electric vehicles, attracting attention as a next-generation energy storage medium.

[0004] As the applications of these secondary batteries expand, the importance of management systems for more efficient use and management of these batteries is increasing. The status and operation of secondary batteries can be managed and controlled by a battery management system (BMS). The BMS can be integrated with the battery within a single device.

[0005] Additionally, the battery management system can manage and control the battery while being separated from the device containing the battery. For example, the battery management system can be implemented as a separate server device. In this case, the battery management system can collect battery and vehicle data from a data collection device installed in the vehicle and utilize the collected data to manage and control the battery.

[0006] These data collection devices can be connected to hardware installed in the vehicle to collect data regarding the condition of the vehicle and battery. This data can then be transmitted to a server for analysis. For example, the data collection device can use Controller Area Network (CAN) communication to collect data from hardware installed in the vehicle, store it on a data storage medium, and then transmit the stored data to a server via a wireless network.

[0007] Meanwhile, if a data collection device fails to access the data storage medium, set the operating mode, or perform a mount operation, normal data collection may become difficult, potentially leading to issues with data stability and reliability. Furthermore, while SD cards have traditionally been used as data storage media connected to data collection devices, they are not suited to the in-vehicle environment (e.g., temperature, vibration, etc.), leading to functional failures due to intermittent data errors and insufficient data stability when physically connected.

[0008] According to one embodiment of the present disclosure, a data collection device and an operating method thereof can be provided that can ensure data stability and reliability by determining whether to recall a driver corresponding to a data storage medium based on a result of an access, operation mode setting, and / or mount operation for the data storage medium.

[0009] According to one embodiment of the present disclosure, a data collection device and an operating method thereof using an eMMC (Embedded Multi-Media Controller) suitable for an in-vehicle environment (e.g., temperature, vibration, etc.) as a data storage medium can be provided.

[0010] The technical problems to be solved by the embodiments of the present disclosure are not limited to the technical problems described above, and other technical problems can be inferred from the following embodiments.

[0011] According to one embodiment of the present disclosure, a data collection device mounted on a vehicle includes a memory storing at least one instruction, and a processor operatively connected to the memory, wherein the processor, by executing the at least one instruction, calls a driver corresponding to a data storage medium connected to the data collection device, identifies a result of an access request to the data storage medium based on the called driver, and when it is determined that access to the data storage medium is completed, sets an operating mode for the data storage medium based on the called driver, identifies a result of setting the operating mode, and outputs a result message based on the identified result of setting the operating mode.

[0012] In a data collection device mounted on a vehicle according to one embodiment of the present disclosure, the processor may recall the driver when it is identified that access to the data storage medium has failed.

[0013] In a data collection device mounted on a vehicle according to one embodiment of the present disclosure, the processor can set the operation mode by setting the data input / output mode for the data storage medium to SDIO (Secure Digital Input / Output) 1 Bit mode.

[0014] In a data collection device mounted on a vehicle according to one embodiment of the present disclosure, the processor may set the operation mode for the data storage medium, then perform a mount operation for the data storage medium, identify a result of performing the mount operation for the data storage medium, and identify a result of setting the operation mode when it is determined that the mount operation for the data storage medium is completed.

[0015] In a data collection device mounted on a vehicle according to one embodiment of the present disclosure, the processor may recall the driver if the mount operation for the data storage medium is identified as having failed.

[0016] In a data collection device mounted on a vehicle according to one embodiment of the present disclosure, when the processor is identified as having completed setting the operation mode for the data storage medium, the processor outputs a setting completion message, and when the processor is identified as having failed setting the operation mode for the data storage medium, the processor identifies whether the setting of the operation mode has been performed a specified number of times or more, and when the processor is identified as having performed the setting of the operation mode a specified number of times or more, the processor outputs a setting failure message, and when the processor is identified as having performed the setting of the operation mode less than the specified number of times, the processor can recall the driver.

[0017] In a data collection device mounted on a vehicle according to one embodiment of the present disclosure, the data storage medium may be an eMMC (Embedded Multi-Media Controller).

[0018] A method for operating a data collection device mounted on a vehicle according to one embodiment of the present disclosure may include an operation of calling a driver corresponding to a data storage medium connected to the data collection device, an operation of identifying a result of an access request for the data storage medium based on the called driver, an operation of setting an operation mode for the data storage medium based on the called driver when it is identified that access to the data storage medium is completed, an operation of identifying a result of setting the operation mode, and an operation of outputting a result message based on the result of setting the identified operation mode.

[0019] A method of operating a data collection device mounted on a vehicle according to one embodiment of the present disclosure may further include an operation of recalling the driver when access to the data storage medium is identified as having failed.

[0020] In a method of operating a data collection device mounted on a vehicle according to one embodiment of the present disclosure, the operation of setting the operating mode for the data storage medium may include an operation of setting the operating mode for the data storage medium by setting at least one of a data input / output mode, an input voltage, a communication path, and a communication frequency for the data storage medium.

[0021] In an operating method of a data collection device mounted on a vehicle according to one embodiment of the present disclosure, the operation of setting the operating mode for the data storage medium may include an operation of setting the operating mode by setting the data input / output mode for the data storage medium to SDIO (Secure Digital Input / Output) 1 Bit mode.

[0022] A method of operating a data collection device mounted on a vehicle according to one embodiment of the present disclosure may further include an operation of performing a mount operation for the data storage medium after setting the operation mode for the data storage medium, an operation of identifying a result of performing the mount operation for the data storage medium, and an operation of identifying a result of setting the operation mode when the mount operation for the data storage medium is identified as being completed.

[0023] A method of operating a data collection device mounted on a vehicle according to one embodiment of the present disclosure may further include an operation of re-calling the driver when the mounting operation for the data storage medium is identified as having failed.

[0024] In an operating method of a data collection device mounted on a vehicle according to an embodiment of the present disclosure, the operation of outputting the result message may include an operation of outputting a setting completion message when the setting of the operation mode for the data storage medium is identified as completed, an operation of identifying whether the setting of the operation mode has been performed a specified number of times or more when the setting of the operation mode for the data storage medium is identified as failed, and an operation of outputting a setting failure message when the setting of the operation mode is identified as being performed a specified number of times or more, and may further include an operation of recalling the driver when the setting of the operation mode is identified as being performed less than the specified number of times.

[0025] According to embodiments disclosed in this document, data stability and reliability can be secured by determining whether to recall a driver corresponding to a data storage medium based on the result of an access, operation mode setting, and / or mount operation for the data storage medium.

[0026] According to one embodiment of the present disclosure, by using an eMMC (Embedded Multi-Media Controller) suitable for an in-vehicle environment (e.g., temperature, vibration, etc.) as a data storage medium, problems such as functional failure due to data errors and insufficient data stability during physical connection can be prevented in advance.

[0027] The effects of the invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description of the claims.

[0028] FIG. 1 is a block diagram illustrating a system according to one embodiment of the present disclosure.

[0029] FIG. 2 is a block diagram of a data collection device according to an embodiment of the present disclosure.

[0030] FIG. 3 is a drawing for explaining an operation performed by a data collection device according to an embodiment of the present disclosure based on a driver corresponding to a data storage medium.

[0031] Figure 4 is a flowchart of the operation of a data collection device according to one embodiment of the present invention.

[0032] Figure 5 is a flowchart of the operation of a data collection device according to one embodiment of the present invention.

[0033] Figure 6 is a flowchart of the operation of a data collection device according to one embodiment of the present invention.

[0034] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0035] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0036] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0037] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can produce an article of manufacture that includes a command means for performing the functions described in the flowchart block(s). The computer program instructions can also be loaded onto a computer or other programmable data processing equipment, so that a series of operation steps are performed on the computer or other programmable data processing equipment to create a computer-executable process, so that the instructions that execute the computer or other programmable data processing equipment can provide steps for performing the functions described in the flowchart block(s).

[0038] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0039] Here, the term '~ unit' used in the present embodiment means a software or hardware component such as an FPGA or ASIC, and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to regenerate one or more processors. Therefore, for example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card.

[0040] The expression “at least one of a, b and c” described throughout the specification may encompass ‘a alone’, ‘b alone’, ‘c alone’, ‘a and b’, ‘a and c’, ‘b and c’, or ‘all of a, b and c’.

[0041] The "terminal" mentioned below may be implemented as a computer or portable terminal that can connect to a server or other terminal via a network. Here, the computer includes, for example, a notebook, desktop, laptop, etc. equipped with a web browser, and the portable terminal may include, for example, a wireless communication device that guarantees portability and mobility, and may include all types of handheld-based wireless communication devices such as communication-based terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), smartphones, tablet PCs, etc.

[0042] Below, embodiments of the present disclosure are described in detail with reference to the attached drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein.

[0043] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0044] FIG. 1 is a block diagram illustrating a system according to one embodiment of the present disclosure.

[0045] Referring to FIG. 1, the system may include a vehicle (100), a data collection device (200), a server (300), and a data storage medium (400).

[0046] The vehicle (100) may be an electric vehicle (EV) that receives driving power from a battery that stores electricity, but is not limited thereto, and the technical idea of ​​the present disclosure may be applied to other electric transportation means (e.g., electric scooter, etc.) other than the vehicle (100).

[0047] According to one embodiment, a vehicle (100) may include a battery pack (110), a vehicle controller (120), and a vehicle network (120).

[0048] According to one embodiment, the battery pack (110) may include a battery that stores power required to drive the vehicle (100) and a battery management system (BMS) for controlling the operation of the battery. The BMS may not only control charging and discharging of the battery, but may also transmit battery status data including at least one of data acquired by sensing the state of the battery (e.g., voltage, current, resistance, temperature, etc.) and data generated by processing the acquired data (e.g., state of charge (SOC), state of health (SOH), etc.) to the vehicle network (130).

[0049] According to one embodiment, the vehicle controller (120) may control the overall operation of the vehicle (100) by controlling at least one sensor (e.g., a radar sensor, a temperature sensor) and at least one control device (e.g., a driving device, a braking device, a steering device, an Automated Driving System (ADS), a Telematics Multimedia System (TMS)) provided in the vehicle (100), including the battery pack (110). According to another embodiment, the vehicle controller (120) may mean an Electronic Control Unit (ECU) for controlling some components of the vehicle (100).

[0050] According to one embodiment, the vehicle controller (120) may store vehicle identification information unique to the vehicle (100) and transmit the vehicle identification information in response to a request from an external source (e.g., a data collection device (200)). According to one embodiment, the vehicle identification information may include a vehicle identification number (VIN). The vehicle controller (120) may communicate with other devices located inside or outside the vehicle (100) via a vehicle network (130).

[0051] According to one embodiment, the vehicle network (130) may provide a communication environment in which components inside the vehicle (100) can transmit and receive data to each other. The vehicle network (130) may be a Controller Area Network (CAN) in which components inside the vehicle (100) are connected in parallel and can communicate without a host, but is not limited thereto. The vehicle network (130) may allow connection of an external device (e.g., a data collection device (200)) to provide an environment in which the external device can communicate with another device (e.g., a battery pack (110)) through the vehicle network (130). However, the vehicle network (130) may have a communication standard that varies depending on the type of the vehicle (100), and only an external device that has firmware installed that is compatible with the communication standard corresponding to the type of the vehicle (100) can normally access and communicate with the vehicle network (130). Here, vehicle model information may refer to information for identifying the model, such as the brand, type, and year of the vehicle (100).

[0052] According to one embodiment, the data collection device (200) may be a device that is mounted on a vehicle (100) and can be connected to a vehicle network (130). For example, the data collection device (200) may be an OBD (On-Board Diagnostics) device that is connected to an OBD port provided in the vehicle (100). The data collection device (200) may obtain vehicle status information regarding the status of the vehicle (100) from components within the vehicle (100) by connecting to the vehicle network (130) and transmitting and receiving UDS (Unified Diagnostic Service) data. Here, the vehicle status information may include speed data, driving distance data, driving time data, driving location data, and battery status data of the vehicle (100).

[0053] According to one embodiment, the data collection device (200) can transmit vehicle status information to the server (300) via a connection (101). According to one embodiment, the connection (101) between the data collection device (200) and the server (300) can be a communication connection via a wired and / or wireless network. In one embodiment, the wired network can be based on a local area network (LAN) communication or a power line communication. In one embodiment, the wireless network can be based on a short-range communication network (e.g., Bluetooth, wireless fidelity (WiFi), or infrared data association (IrDA)), or a long-range communication network (cellular network, 4G network, 5G network).

[0054] According to one embodiment, the server (300) can provide a management service for a vehicle (100) or a battery pack (110) by transmitting and receiving data with the data collection device (200), receiving vehicle status information from the data collection device (200), and storing and analyzing the vehicle status information.

[0055] According to one embodiment, the data collection device (200) can store vehicle status information in a data storage medium (400) through a connection (102). According to one 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.

[0056] According to one embodiment, the data storage medium (400) may be an embedded memory. For example, the data storage medium (400) may be an eMMC (Embedded Multi-Media Controller).

[0057] FIG. 2 is a block diagram of a data collection device (200) according to an embodiment of the present disclosure. Since the data collection device (200) of FIG. 2 has the same configuration as the data collection device (200) of FIG. 2, any description that overlaps with the above may be omitted.

[0058] Referring to FIG. 2, the data collection device (200) may include a communication circuit (210), a memory (220), and a processor (230). According to an embodiment, the data collection device (200) illustrated in FIG. 2 may further include at least one component (e.g., a display, an input device, or an output device) other than the components illustrated in FIG. 2.

[0059] According to one embodiment, the communication circuit (210) can establish a wired communication channel and / or a wireless communication channel between a data collection device (200) and an electronic device (e.g., a server (300), a data storage medium (400)), and transmit and receive data with the electronic device through the established communication channel.

[0060] According to one embodiment, the memory (220) may include volatile memory and / or non-volatile memory.

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

[0062] According to one embodiment, the memory (220) may store a driver corresponding to a data storage medium (400). For example, the driver may perform at least one of an access request for the data storage medium (400), an access request result identification, an operation mode setting, and a mount operation.

[0063] According to one embodiment, the processor (230) may be implemented as a computer or similar device according to hardware, software, or a combination thereof. In terms of hardware, the processor (230) may be implemented in the form of an electronic circuit that processes electrical signals to perform a control function, and in terms of software, the processor (230) may be implemented in the form of a program that drives the hardware processor (230). According to one embodiment, the processor (230) may be operatively connected to components included in the data collection device (200) (e.g., a communication circuit (210) and / or a memory (220)) and control the connected components.

[0064] According to one embodiment, the processor (230) may include a central processing unit, an application processor, a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor.

[0065] Below, with reference to FIG. 3, the operations performed by the data collection device (200) by calling a driver corresponding to the data storage medium (400) stored in the memory (220) are described.

[0066] FIG. 3 is a drawing for explaining an operation performed by a data collection device (200) according to an embodiment of the present disclosure based on a driver corresponding to a data storage medium (400).

[0067] Referring to FIG. 3, the processor (230) can call a driver (235) (e.g., an eMMC driver) corresponding to a data storage medium (400) stored in the memory (220), and perform various operations related to the data storage medium (400) based on the called driver (235).

[0068] According to one embodiment, the processor (230) may request access to the data storage medium (400) based on the driver (235). In addition, the processor (230) may identify the result of the access request to the data storage medium (400) based on the driver (235).

[0069] According to one embodiment, when the processor (230) determines that access to the data storage medium (400) is completed, the processor (230) may set an operating mode for the data storage medium (400) based on the driver (235). According to one embodiment, the processor (230) may set an operating mode for the data storage medium (400) by setting at least one of an input / output mode, an input voltage, a communication path, and a communication frequency for the data storage medium (400). As an example, the processor (230) may set the data input / output mode for the data storage medium (400) to a Secure Digital Input / Output (SDIO) 1 Bit mode. In addition, the processor (230) may set the number of data buses to be used for communication with the data storage medium (400) and whether to apply a pull-up resistor inside the data bus.

[0070] According to one embodiment, if the processor (230) identifies that access to the data storage medium (400) has failed, the processor (230) may recall the driver (235) stored in the memory (220). In this case, the processor (230) may re-perform the operations described in the present disclosure based on the recalled driver (235).

[0071] According to one embodiment, the processor (230) may perform a mount operation on the data storage medium (400). For example, the processor (230) may set an operating mode for the data storage medium (400) and then perform a mount operation on the data storage medium (400) based on the driver (235). Here, the mount operation may be a process of connecting the processor (230) to the data storage medium (400) so that the processor can read and write data as storage. For example, the processor (230) may connect a specific directory of the data storage medium (400) with the processor (230) through the mount operation.

[0072] According to one embodiment, the processor (230) can identify the result of performing a mount operation on a data storage medium (400).

[0073] According to one embodiment, if the processor (230) identifies that a mount operation for the data storage medium (400) has failed, the processor (230) may recall the driver (235) stored in the memory (220). In this case, the processor (230) may re-perform the operations described in the present disclosure based on the recalled driver (235).

[0074] According to one embodiment, the processor (230) may identify the result of setting the operating mode for the data storage medium (400) when it is determined that the mount operation for the data storage medium (400) has been completed. According to another embodiment, the processor (230) may also identify the result of setting the operating mode for the data storage medium (400) regardless of the result of performing the mount operation for the data storage medium (400).

[0075] According to one embodiment, when the processor (230) determines that the setting of the operating mode for the data storage medium (400) is completed, the processor (230) may output a setting completion message. For example, the processor (230) may 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) may transmit the setting completion message to an external device (e.g., a server (300)) using the communication circuit (210).

[0076] According to one embodiment, if the processor (230) identifies that the setting of the operating mode for the data storage medium (400) has failed, it can identify whether the setting of the operating mode for the data storage medium (400) has been performed a specified number of times (e.g., three times).

[0077] According to one embodiment, the processor (230) may output a setup failure message if it is determined that the setting of the operating mode for the data storage medium (400) has been performed a specified number of times or more. For example, the processor (230) may output the setup failure message through an output device (e.g., a display) provided in the data collection device (200). As another example, the processor (230) may transmit the setup failure message to an external device (e.g., a server (300)) using the communication circuit (210).

[0078] According to one embodiment, if the processor (230) determines that the setting of the operating mode for the data storage medium (400) has been performed less than a specified number of times, the processor (230) may recall the driver (235) stored in the memory (220). In this case, the processor (230) may re-perform the operations described in the present disclosure based on the recalled driver (235).

[0079] FIG. 4 is a flowchart illustrating the operation of a data collection device according to an embodiment of the present disclosure. Since the operation method of FIG. 4 can be performed by the data collection device (200) of FIGS. 1 and 2, any description overlapping with the above description may be omitted, and the method may be described using the configurations of FIGS. 1 and 2.

[0080] The embodiment illustrated in FIG. 4 is only one embodiment, and the order of operations according to various embodiments of the present disclosure may be different from that illustrated in FIG. 4, and some operations illustrated in FIG. 4 may be omitted, the order between operations may be changed, or operations may be merged.

[0081] Referring to FIG. 4, in operation 410, the data collection device (200) may call a driver corresponding to the data storage medium (400). Here, the driver may be stored in the memory (220) of the data collection device (200).

[0082] In operation 420, the data collection device (200) can identify the result of an access request to the data storage medium (400) based on the driver called in operation 410.

[0083] If it is identified that access to the data storage medium (400) has failed in operation 420, the data collection device (200) may return to operation 410 and recall the driver corresponding to the data storage medium (400).

[0084] If it is determined that access to the data storage medium (400) is completed in operation 420, in operation 430, the data collection device (200) can set an operating mode for the data storage medium (400) based on the driver called in operation 410. According to one embodiment, the data collection device (200) can set an operating mode for the data storage medium (400) by setting at least one of an input / output mode, an input voltage, a communication path, and a communication frequency for the data storage medium (400).

[0085] In operation 440, the data collection device (200) may also identify the result of setting the operating mode for the data storage medium (400) performed in operation 430.

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

[0087] The operations 440 and 450, in which the data collection device (200) identifies the result of setting the operation mode for the data storage medium (400) and outputs a result message based on the identified result, can be described in more detail with reference to FIG. 6, which will be described later.

[0088] FIG. 5 is a flowchart illustrating the operation of a data collection device according to an embodiment of the present disclosure. Since the operation method of FIG. 5 can be performed by the data collection device (200) of FIGS. 1 and 2, any description overlapping with the above description may be omitted, and the method may be described using the configurations of FIGS. 1 and 2.

[0089] The embodiment illustrated in FIG. 5 is only one embodiment, and the order of operations according to various embodiments of the present disclosure may be different from that illustrated in FIG. 5, and some operations illustrated in FIG. 5 may be omitted, the order between operations may be changed, or operations may be merged.

[0090] Referring to FIG. 5, in operation 510, the data collection device (200) may call a driver corresponding to the data storage medium (400). Here, the driver may be stored in the memory (220) of the data collection device (200).

[0091] In operation 520, the data collection device (200) can identify the result of an access request to the data storage medium (400) based on the driver called in operation 510.

[0092] If access to the data storage medium (400) is identified as failed in operation 520, the data collection device (200) may return to operation 510 and recall the driver corresponding to the data storage medium (400).

[0093] If it is determined that access to the data storage medium (400) is completed in operation 520, in operation 530, the data collection device (200) can set an operating mode for the data storage medium (400) based on the driver called in operation 510. According to one embodiment, the data collection device (200) can set an operating mode for the data storage medium (400) by setting at least one of an input / output mode, an input voltage, a communication path, and a communication frequency for the data storage medium (400).

[0094] In operation 540, the data collection device (200) may perform a mount operation on the data storage medium (400). Here, the mount operation may be a process of connecting the data collection device (200) to the data storage medium (400) so that it can read and write data as storage.

[0095] In operation 550, the data collection device (200) can identify the result of performing the mount operation of operation 540.

[0096] If the mount operation is identified as failed in operation 550, the data collection device (200) may return to operation 510 and recall the driver corresponding to the data storage medium (400).

[0097] If the mount operation is identified as completed in operation 550, in operation 560, the data collection device (200) may also identify the result of setting the operating mode for the data storage medium (400) performed in operation 530.

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

[0099] The operations 560 and 570, in which the data collection device (200) identifies the result of setting the operation mode for the data storage medium (400) and outputs a result message based on the identified result, can be described in more detail with reference to FIG. 6, which will be described later.

[0100] FIG. 6 is a flowchart illustrating the operation of a data collection device according to an embodiment of the present disclosure. Since the operation method of FIG. 6 can be performed by the data collection device (200) of FIGS. 1 and 2, any description overlapping with the above description may be omitted, and the method may be described using the configurations of FIGS. 1 and 2.

[0101] The embodiment illustrated in FIG. 6 is only one embodiment, and the order of operations according to various embodiments of the present disclosure may be different from that illustrated in FIG. 6, and some operations illustrated in FIG. 6 may be omitted, the order between operations may be changed, or operations may be merged.

[0102] Referring to FIG. 6, in operation 610, the data collection device (200) can identify the result of setting the operating mode for the data storage medium (400) performed in operation 430 (or operation 530) of FIG. 4 (or FIG. 5).

[0103] If it is determined that the setting of the operation mode for the data storage medium (400) is completed in operation 610, the data collection device (200) may output a setting completion message in operation 620. For example, the data collection device (200) may output the setting completion message through an output device (e.g., a display) provided in the data collection device (200). As another example, the data collection device (200) may transmit the setting completion message to an external device (e.g., a server (300)) using a communication circuit (210).

[0104] If it is determined that the setting of the operating mode for the data storage medium (400) has failed in operation 610, then in operation 630, the data collection device (200) can determine whether the setting of the operating mode for the data storage medium (400) has been performed a specified number of times (e.g., 3 times).

[0105] If it is determined that the setting of the operation mode for the data storage medium (400) has been performed a specified number of times or more in operation 630 ('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) provided in the data collection device (200). As another example, the data collection device (200) may transmit the setting failure message to an external device (e.g., a server (300)) using a communication circuit (210).

[0106] If it is determined that the setting of the operating mode for the data storage medium (400) in operation 630 has been performed less than a specified number of times ('NO'), in operation 650, the data collection device (200) may recall the driver corresponding to the data storage medium (400).

[0107] The data collection device according to the above-described embodiments may include a processor, a memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, a user interface device such as a touch panel, a key, an icon, etc. The methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable codes or program commands that can be executed on the processor. Here, the computer-readable recording medium includes a magnetic storage medium (e.g., read-only memory (ROM), random-access memory (RAM), floppy disk, hard disk, etc.) and an optical reading medium (e.g., CD-ROM, DVD: Digital Versatile Disc)). The computer-readable recording medium may be distributed to computer systems connected to a network, so that the computer-readable code can be stored and executed in a distributed manner. The medium is readable by a computer, stored in a memory, and executed by a processor.

[0108] Various embodiments of the present disclosure may be represented by functional block configurations and various processing steps. These functional blocks may be implemented by various hardware and / or software components that perform specific functions. For example, embodiments may employ direct circuit components, such as memory, processing, logic, look-up tables, etc., that may perform various functions under the control of one or more microprocessors or other control devices. Similarly, the present embodiments may be implemented in a programming or scripting language, such as C, C++, Java, or an assembler, including various algorithms implemented as a combination of data structures, processes, routines, or other programming components. Functional aspects may be implemented as algorithms that execute on one or more processors. Furthermore, the present embodiments may employ conventional techniques for electronic configuration, signal processing, and / or data processing. Terms like "mechanism," "element," "means," and "composition" can be used broadly and are not limited to mechanical or physical components. These terms can also encompass a series of software routines, such as those associated with a processor.

[0109] The above-described embodiments are merely examples, and other embodiments may be implemented within the scope of the claims set forth below.

Claims

1. In a data collection device mounted on a vehicle, memory that stores at least one instruction; and comprising a processor operatively connected to said memory, The processor, by executing the at least one instruction, Calling a driver corresponding to the data storage medium connected to the above data collection device, Based on the above-mentioned called driver, identify the result of an access request to the data storage medium, When it is identified that access to the data storage medium has been completed, an operating mode for the data storage medium is set based on the called driver, Identify the setting results of the above operation mode, A data collection device that outputs a result message based on the setting result of the above-identified operation mode.

2. In paragraph 1, The above processor, A data collection device that re-invokes the driver when it is identified that access to the data storage medium has failed.

3. In paragraph 1, The above processor, A data acquisition device that sets the operation mode for the data storage medium by setting at least one of a data input / output mode, an input voltage, a communication path, and a communication frequency for the data storage medium.

4. In paragraph 3, The above processor, A data collection device that sets the operation mode by setting the data input / output mode for the above data storage medium to SDIO (Secure Digital Input / Output) 1 Bit mode.

5. In paragraph 1, The above processor, After setting the operation mode for the data storage medium, a mount operation for the data storage medium is performed, Identify the result of performing the mount operation on the data storage medium, A data collection device that identifies the result of setting the operating mode when the mount operation for the data storage medium is identified as completed.

6. In paragraph 5, The above processor, A data collection device that re-invokes the driver when the mount operation for the data storage medium is identified as having failed.

7. In paragraph 1, The above processor, When it is identified that the setting of the above operation mode for the above data storage medium is completed, a setting completion message is output, If it is identified that the setting of the above operation mode for the above data storage medium has failed, it is identified that the setting of the above operation mode has been performed more than a specified number of times, If it is identified that the setting of the above operation mode has been performed more than the specified number of times, a setting failure message is output, A data collection device that recalls the driver when it is identified that the setting of the above operation mode has been performed less than the specified number of times.

8. In paragraph 1, A data collection device wherein the above data storage medium is an eMMC (Embedded Multi-Media Controller).

9. In the operating method of a data collection device mounted on a vehicle, An action of calling a driver corresponding to a data storage medium connected to the above data collection device; An operation of identifying a result of an access request to the data storage medium based on the driver called above; When it is identified that access to the data storage medium has been completed, an operation of setting an operating mode for the data storage medium based on the called driver; An operation for identifying the result of setting the above operation mode; and An operating method of a data collection device, comprising an operation of outputting a result message based on the setting result of the above-identified operation mode.

10. In paragraph 9, A method of operating a data collection device, further comprising an action of re-invoking the driver when access to the data storage medium is identified as having failed.

11. In paragraph 9, The operation of setting the above operation mode for the above data storage medium is: An operating method of a data acquisition device, comprising an operation of setting the operating mode for the data storage medium by setting at least one of a data input / output mode, an input voltage, a communication path, and a communication frequency for the data storage medium.

12. In paragraph 11, The operation of setting the above operation mode for the above data storage medium is: An operating method of a data collection device, comprising an operation of setting the operation mode by setting the data input / output mode for the data storage medium to SDIO (Secure Digital Input / Output) 1 Bit mode.

13. In paragraph 9, An operation of performing a mount operation on the data storage medium after setting the operation mode for the data storage medium; An operation for identifying the result of performing the mount operation on the data storage medium; and An operating method of a data collection device, further comprising an operation of identifying a result of setting the operating mode when the mount operation for the data storage medium is identified as being completed.

14. In paragraph 13, A method of operating a data collection device, further comprising an operation of re-invoking the driver when the mount operation for the data storage medium is identified as having failed.

15. In paragraph 9, The action of printing the above result message is: When it is identified that the setting of the above operation mode for the above data storage medium is completed, an action of outputting a setting completion message; If it is identified that the setting of the operation mode for the data storage medium has failed, an operation of identifying whether the setting of the operation mode has been performed a specified number of times or more, and If it is identified that the setting of the above operation mode has been performed more than the specified number of times, an action is included to output a setting failure message. A method of operating a data collection device, further comprising an operation of re-calling the driver if it is determined that the setting of the above operation mode has been performed less than the specified number of times.

Images