Electronic device mounted on automated vehicle, electronic system and method of operating the same

Abstract

An electronic device configured to be mounted on an automated vehicle includes: a first interface circuit configured to communicate with a plurality of storage devices; a second interface circuit configured to communicate with a plurality of regions of the automated vehicle; an event detector configured to output an event signal in response to detecting event data received through the second interface circuit; an event manager configured to output a data division signal in response to the event signal; and an interface manager. The interface manager is configured to divide the event data into a plurality of data segments in response to the data division signal, allocate the plurality of data segments to two or more of the plurality of storage devices, respectively, and control the first interface circuit such that the plurality of data segments are transmitted to the allocated two or more storage devices, respectively.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Korean Patent Application No. 10-2023-0081409, filed on June 23, 2023, the disclosure of which is incorporated herein by reference. Technical Field

[0003] Embodiments of the present disclosure described herein relate to electronic devices, and more particularly, to electronic devices mounted on an automatic vehicle, electronic systems including the electronic devices, and methods of operating the automatic vehicle. Background Art

[0004] Nowadays, storage devices such as solid-state drives (SSDs) are widely used. Since this type of storage device does not include a mechanical drive unit, the storage device provides excellent stability and durability, and has the advantages of very fast access to information and relatively low power consumption.

[0005] When a vehicle has an accident, a function to record the data generated inside the vehicle is required, and an event data recorder (EDR) that can work as a "black box" of the vehicle can store the data generated in the vehicle within a given period of time before and after the accident. With the recent emergence of autonomous vehicles (e.g., self-driving vehicles), the amount of data that needs to be recorded / saved in the event of an accident has increased in order to fully study the safety of such vehicles and analyze the exact cause of an accident that may have occurred in the vehicle through cameras, light detection and radar (LIDAR) sensors, and any other radar (radio detection and ranging). In addition, when in-vehicle information (IVI), high-definition maps, ADAS, NPU, etc. are applied to the architecture of autonomous vehicles, the amount of data required for autonomous vehicles increases. Therefore, in the event that the data generated in the vehicle is not quickly stored in the event of an accident, the data required to analyze the cause of the accident may be lost due to vehicle failure. Therefore, it would be advantageous to quickly record a large amount of data in the event of an accident. Summary of the invention

[0006] Embodiments of the present disclosure provide an electronic device capable of quickly recording data while being mounted on an automatic vehicle, an electronic system including the electronic device, and an operating method thereof.

[0007] According to an embodiment, an electronic device installed on an automatic carrier may include: a first interface circuit that communicates with multiple storage devices, a second interface circuit that communicates with multiple areas of the automatic carrier, an event detector that outputs an event signal in response to detecting event data received through the second interface circuit, an event manager that outputs a data partitioning signal in response to the event signal, and an interface manager that divides the event data into multiple data segments in response to the data partitioning signal, distributes the multiple data segments to two or more storage devices among the multiple storage devices, and controls the first interface circuit so that the multiple data segments are sent in parallel to the two or more allocated storage devices.

[0008] According to an embodiment, an electronic system may include an electronic device installed on an automatic vehicle, a regional control unit corresponding to a plurality of regions of the automatic vehicle, and a plurality of first storage devices, each of which includes an event data space. The electronic device may divide the event data received from one of the regional control units into a plurality of data segments, may distribute the plurality of data segments to two or more first storage devices among the plurality of first storage devices, and may send the plurality of data segments to the two or more first storage devices in parallel. Each of the two or more first storage devices may write a corresponding data segment of the plurality of data segments into the event data space.

[0009] According to another embodiment, an operating method of an electronic device installed on an automatic vehicle may include detecting event data, outputting an event signal when the event data is detected, dividing the event data into multiple data segments in response to the event signal, allocating the multiple data segments to two or more storage devices, and sending the multiple data segments in parallel to the two or more storage devices so allocated. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other objects and features of the present disclosure will become apparent by describing in detail embodiments of the present disclosure with reference to the accompanying drawings.

[0011] Figure 1 is a block diagram illustrating an electronic device according to an embodiment of the present disclosure.

[0012] Figure 2 It is shown that Figure 1 Block diagram of the electronic system of an electronic device.

[0013] Figure 3 It is shown Figure 1 A block diagram of an example of one of multiple storage devices.

[0014] Figure 4 Is used to describe Figure 1 A diagram of the operation of an electronic device sending multiple data fragments in parallel to two or more storage devices.

[0015] Figure 5 is a diagram for describing a flow identifier according to an embodiment of the present disclosure.

[0016] Figure 6 is a diagram for describing an operation of storing combined event data according to an embodiment of the present disclosure.

[0017] Figure 7 is a diagram describing how to perform a data partitioning operation based on available capacity of each of a plurality of storage devices according to an embodiment of the present disclosure.

[0018] Figure 8 is a diagram describing how to perform a data partitioning operation based on states of multiple queues according to an embodiment of the present disclosure.

[0019] Fig. 9 is a diagram for describing an operation of transmitting data to each of a plurality of storage devices based on data priority according to an embodiment of the present disclosure.

[0020] Fig.10 is a diagram showing an Ethernet frame according to an embodiment of the present disclosure.

[0021] Fig.11 is a flowchart illustrating an operating method of an electronic device according to an embodiment of the present disclosure.

[0022] Fig.12 is a diagram illustrating a configuration of a plurality of storage devices according to another embodiment of the present disclosure.

[0023] Fig.13 Is used to describe Figure 2 A diagram of an example of a storage area of ​​a storage device.

[0024] Fig.14 is a schematic diagram showing the automotive partitioning and centralized architecture of an autonomous vehicle. DETAILED DESCRIPTION

[0025] Figure 1 is a block diagram showing an electronic device according to an embodiment of the present disclosure. Figure 1 According to an embodiment of the present disclosure, an electronic device 100 installed on an automatic vehicle may include a first interface circuit 110, a second interface circuit 120, a processor 130, a memory 140 and an event processing circuit 150.

[0026] The first interface circuit 110 may provide an interface for bidirectional communication with a plurality of storage devices 200. The first interface circuit 110 may include at least one switch. When the first interface circuit 110 includes a plurality of switches, the plurality of switches may constitute a switch structure. The first interface circuit 110 may send data to a plurality of storage devices 200 in parallel. In contrast, the second interface circuit 120 may provide an interface for receiving various data from outside the electronic device 100, and the various data may include event data ED.

[0027] The event data ED is data associated with the state of the vehicle or the passenger, and is recorded within a given time period before and after the time point when an event (e.g., a car collision) occurs. When a given trigger condition is met, the event data ED is sent from various devices including the electronic control device included in the vehicle to the electronic device 100 so as to be written to at least one of the storage devices 200. The event data ED is useful for analyzing accident situations occurring in an autonomous vehicle.

[0028] The event data ED can be classified into mandatory item data MDT and optional item data OPT. The mandatory item data MDT is the event data ED that needs to be recorded as mandatory and corresponds to data with relatively high importance. The optional item data OPT may be the event data ED whose recording is determined according to the setting and may correspond to data with relatively low importance even in the event of an accident.

[0029] The items of event data ED may include VRU (Vulnerable Road User) items, ACC (Adaptive Cruise Control) items, ACSF (Automatic Command Steering Function) items, Command Steering Function items, LDWS (Lane Departure Warning System) items, Advanced Emergency Braking System items, etc. Each item may be collected at a given time period.

[0030] The processor 130 may execute one or more instructions stored in the memory 140. The processor 130 may be implemented with hardware components that perform arithmetic, logic, and input / output operations and signal processing. For example, the processor 130 may be implemented with at least one of a central processing unit, a microprocessor, a graphics processing unit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), and a field programmable gate array (FPGA), but the present disclosure is not limited thereto. The processor 130 may control the overall operation of the electronic device 100 by executing instructions.

[0031] The memory 140 may include, for example, a nonvolatile memory, a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory, and at least one of volatile memory devices such as a random access memory (RAM) or a static random access memory (SRAM), the nonvolatile memory including a flash memory type, a hard disk type, a multimedia card micro or a card type memory (e.g., SD or XD memory).

[0032] Instructions, data structures, and program codes readable by the processor 130 may be stored in the memory 140. The processor 130 may execute the program instructions or codes stored in the memory 140. The event processing circuit 150 may store the received event data ED in part or all of the plurality of storage devices 200, and may include an event manager 151, an event detector 152, and an interface manager 153.

[0033] The event detector 152 may determine whether the second interface circuit 120 receives the event data ED. When it is determined that the event data ED is received through the second interface circuit 120, the event detector 152 may send an interrupt signal to the event manager 151. For example, the event detector 152 may detect the input of the event data ED based on a specific field of the packet received by the second interface circuit 120.

[0034] In response to the interrupt signal from the event detector 152, the event manager 151 may control the interface manager 153 to store the event data ED in part or all of the plurality of storage devices 200. For example, the event manager 151 may output a data division signal so that the interface manager 153 divides the event data ED.

[0035] Under the control of the event manager 151, the interface manager 153 may divide the received event data ED into a plurality of data segments. In the case of dividing the event data ED into a plurality of data segments, the interface manager 153 may divide the event data ED in consideration of the unit size of the data stored by the storage device 200. For example, the interface manager 153 may divide the event data ED into a plurality of data segments based on the mapping size applied to the storage device 200.

[0036] The interface manager 153 may control the first interface circuit 110 so that the plurality of data fragments are sent in parallel to two or more storage devices among the plurality of storage devices 200. Under the control of the interface manager 153, the first interface circuit 110 may send the plurality of data fragments to part or all of the plurality of storage devices 200, including sending in parallel. In this way, the time for storing the event data ED may be shortened.

[0037] As vehicle technology develops, various sensing information is collected from various cameras and various sensors including lidar, and as the driving automation level becomes higher, the size of event data ED is also increasing. The event processing circuit 150 can quickly write event data ED by sending the event data ED to some or all of the multiple storage devices 200 in parallel.

[0038] Figure 2 It is shown that Figure 1 A block diagram of the electronic system of an electronic device. Figure 2 According to an embodiment of the present disclosure, an electronic system 10 including an electronic device 100 mounted on an automatic carrier may also include area control units 301, 302, 303 and 304 corresponding to multiple areas Z1, Z2, Z3 and Z4 of the automatic carrier, respectively, multiple first storage devices 200-1, 200-2 and 200-3 and a central processor 400.

[0039] Nowadays, in the field of automotive zone and centralized architecture for controlling the electrical / electronic system of the vehicle, research is being conducted. According to the automotive zone and centralized architecture, the electrical / electronic system of the vehicle can be divided into smaller units that are easy to manage. A plurality of zones Z1 to Z4 can be determined for each physical location and zone of the vehicle. The vehicle to which the automotive zone and centralized architecture is applied can process specific functions within zones Z1 to Z4, and can also process specific functions through the central processor 400. The automotive zone and centralized architecture can reduce the complexity of the wiring harness and easily add various devices to the vehicle.

[0040] Various automotive devices DA, DB, and DC (such as sensors, actuators, cameras, and inertial measurement units (IMUs)) may be provided in each of the zones Z1 to Z4, and at least one regional control unit may be provided in each of the zones Z1 to Z4. For example, the regional control units 301 to 304 may be provided in the zones Z1 to Z4, respectively. For example, in the first zone Z1, the automotive devices DA to DC are connected to the regional control unit 301. For example, the automotive device DA may be a sensor, the automotive device DB may be an actuator, and the automotive device DC may be a camera. As an example, automotive devices DA to DC arranged in the first zone Z1 are provided. For example, in addition to the above-mentioned sensors, actuators, and cameras, various devices for driving a vehicle may also be provided therein. The regional control unit 301 may send the regional data ZD or event data ED generated in the first zone Z1 to the electronic device 100. For example, in the second zone Z2, the automotive devices DA to DC are connected to the regional control unit 302. The regional control unit 302 may send the regional data ZD or event data ED generated in the second zone Z2 to the electronic device 100. The zone control unit 303 may transmit the zone data ZD or event data ED generated in the third zone Z3 to the electronic device 100, and the zone control unit 304 may transmit the zone data ZD or event data ED generated in the fourth zone Z4 to the electronic device 100. Each of the zone control units 301 to 304 may transmit a control signal to the automobile devices DA to DC provided in a corresponding one of the zones Z1 to Z4, and may control the automobile devices DA to DC.

[0041] Each of the plurality of first storage devices 200-1, 200-2, and 200-3 may include a zone data space ZDS and an event data space EDS. The zone data space ZDS is a logical space for storing zone data ZD received from a plurality of zone control units 301 to 304 or a plurality of virtual machines VM1 to VM4. The event data space EDS is a logical space for storing event data ED received by the electronic device 100. The electronic device 100 may write segment data ZD into the segment data space ZDS, and may write event data ED into the event data space EDS. That is, the zone data space ZDS and the event data space EDS may be logically distinguished from each other.

[0042] The central processor 400 can execute multiple virtual machines VM1, VM2, VM3 and VM4. Multiple virtual machines VM1 to VM4 can control corresponding areas Z1 to Z4 respectively. For example, the virtual machine VM1 can control the electronic control device arranged in the first area Z1, and can receive the area data ZD generated from various sensors arranged in the first area Z1. The virtual machine VM1 can write data to the area data space ZDS, or can read data from the area data space ZDS. The electronic device 100 can provide an interface between the multiple virtual machines VM1 to VM4 and the multiple area control units 301 to 304. The central processor 400 can be an external computing device of the electronic device 100, or can correspond to the processor 130 included in the electronic device 100.

[0043] The electronic system 10 may include at least one second storage device 200-4. The second storage device 200-4 may include only a spare space SS. The spare space SS is a space that does not store the regional data ZD but only stores the event data ED. The second storage device 200-4 may not store the regional data ZD from the multiple regional control units 301 to 304 or the multiple virtual machines VM1 to VM4, and may only store the event data ED from the multiple regional control units 301 to 304 or the multiple virtual machines VM1 to VM4. The second storage device 200-4 may be a spare storage device used only to store the event data ED.

[0044] The first storage devices 200-1 to 200-3 and the second storage device 200-4 may correspond to Figure 1 Meanwhile, the number of storage devices is not limited thereto and may be changed according to the capacity or bandwidth required in the electronic system 10.

[0045] Each of the first storage devices 200-1 to 200-3 and the second storage device 200-4 may include at least one non-volatile storage device among a flash memory type, a hard disk type, a multimedia card micro or a card type memory (e.g., an SD or XD memory), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), and a ferroelectric RAM (FRAM).

[0046] The electronic device 100 may write the received event data ED into the event data space EDS of the first storage device 200-1 to 200-3. After the event data ED is completely written, the electronic device 100 may store a copy of the event data ED stored in the event data space EDS in the spare space SS included in the second storage device 200-4. For the purpose of preventing data forgery, the event data ED stored in the event data space EDS or the spare space SS may be set to "read-only".

[0047] At the same time, the electronic device 100 may write the received event data ED into the spare space SS. After the event data ED is completely written, the electronic device 100 may store a copy of the event data ED stored in the spare space SS of the second storage device 200-4 in the event data space EDS included in the first storage devices 200-1 to 200-3. The electronic device 100 may ensure the reliability of the event data ED by distributing and storing the original and the copy of the event data ED in the first storage devices 200-1 to 200-3 and the second storage device 200-4.

[0048] Figure 3 It shows Figure 1 A block diagram of an example of one of the plurality of storage devices of FIG. Figure 1 and Figure 3 , the storage device 200 may include a storage controller 210 and a non-volatile storage device 220. The storage processor 211 may control the operation of the storage controller 210 in response to a command received from a host (e.g., an electronic device) through a host interface circuit 215. For example, the storage processor 211 may control each component by using firmware for driving the storage device 200.

[0049] The RAM 212 may store instructions executable by the storage processor 211 and data processed / to be processed by the storage processor 211. For example, the RAM 212 may be implemented with a volatile memory having a relatively small capacity and supporting fast speed, such as a static random access memory (SRAM) or a cache memory.

[0050] The error correction code (ECC) circuit 213 can perform ECC encoding and ECC decoding by using BCH (Bose-Chaudhuri-Hocquenghem) code, LDPC (Low Density Parity Check) code, Turbo code, Reed-Solomon code, convolutional code, RSC (Recursive System Code), coded modulation such as TCM (Trellis-Coded Modulation) or BCM (Block Coded Modulation), or any other error correction code.

[0051] Flash translation layer manager 214 may perform an address mapping operation. The address mapping operation refers to an operation of converting a logical address received from a host into a physical address for actually storing data in nonvolatile memory device 220. Flash translation layer manager 214 may perform a wear leveling operation for preventing excessive degradation of storage blocks BLK_1, BLK_2, ..., BLK_n, a garbage collection operation for ensuring available capacity in nonvolatile memory device 220, and the like. Flash translation layer manager 214 may perform an address mapping operation in units of a specific size. For example, flash translation layer manager 214 may map a logical address and a physical address in units of a specific size in which a reference data size is set to 4KB or 8KB.

[0052] The host interface circuit 215 can provide a physical connection between the host and the storage device 200. That is, the host interface circuit 215 can provide an interface with the storage device 200 according to the bus format of the host. In an embodiment, the bus format of the host can be SCSI or SAS. In another embodiment, the bus format of the host can be USB, Peripheral Component Interconnect Express (PCIe), ATA, PATA, SATA, NVMe, etc.

[0053] The nonvolatile memory interface circuit 216 may exchange data with the nonvolatile memory device 220. The nonvolatile memory interface circuit 216 may send data to the nonvolatile memory device 220 and may receive data read from the nonvolatile memory device 220. Those skilled in the art will appreciate that the nonvolatile memory device 220 may include a plurality of memory blocks BLK_1, BLK_2, . . . , BLK_n and a control logic 221.

[0054] A plurality of memory blocks BLK_1, BLK_2, ..., BLK_n may include a plurality of pages including a plurality of memory cells, and each of the plurality of memory cells may store at least one bit depending on the charge stored in the charge storage layer. The charge storage layer may be a conductive floating gate of a floating gate structure or a trapping layer of a charge trap flash (CTF) structure. The memory cells may be programmed in various schemes, such as a single-level cell (SLC) scheme, a multi-level cell (MCL) scheme, a triple-level cell (TLC) scheme, and a quad-level cell (QLC) scheme.

[0055] The control logic 221 may be implemented to receive a command and an address from the memory controller 210 and perform an operation (eg, a program operation, a read operation, or an erase operation) corresponding to the received command with respect to a memory cell corresponding to the received address.

[0056] The storage device 200 may receive the event data ED or the data fragments obtained by dividing the event data ED through the first interface circuit 110. The flash translation layer manager 214 may use various methods to distinguish the event data ED from any other data. The flash translation layer manager 214 may use a separate namespace to distinguish the event data ED from any other data. The logical space storing the event data ED may be specified separately and may be distinguished from the logical space storing any other data.

[0057] Figure 4 Is used to describe Figure 1 FIG. 1 is a diagram of an operation of an electronic device sending multiple data fragments to two or more storage devices in parallel. Figure 4 , the event detector 152 can detect event data ED received through the second interface circuit 120. The second interface circuit 120 can receive a packet PCK from outside the electronic device 100. The type field (TP) included in the packet PCK can indicate that the event data ED exists in the payload (or payload field) of the packet PCK. The event detector 152 can check the value of a specific field included in the packet PCK. For example, the event detector 152 can check the type field of the packet PCK and can detect that the event data ED is included in the packet PCK. The event detector 152 can output an event signal ES as an interrupt signal in response to detecting the event data ED.

[0058] The event manager 151 may output a data partition signal DDS in response to an event signal ES from the event detector 152. In contrast, the interface manager 153 may receive event data ED from the second interface circuit 120, and may receive a data partition signal DDS from the event manager 151. The interface manager 153 may partition the event data ED into a plurality of data segments DF1, DF2, and DF3 in response to the data partition signal DDS. The interface manager 153 may partition the event data ED in units of a reference data size (e.g., a data size set to 4KB or 8KB) applied to a storage device. The reference data size may be a unit size used in a mapping operation of a storage device. For example, assuming that the reference data size is set to 8KB, the event data ED may be partitioned so that the data segments have a data size corresponding to an integer multiple of 8KB. That is, each of the plurality of data segments DF1 to DF3 may have a size corresponding to an integer multiple of 8KB. Meanwhile, a reference data size is provided as an example. For example, the reference data size may be set to various sizes as well as 4KB and 8KB. The interface manager 153 may distribute the data segments DF1 to DF3 to two or more storage devices. For example, the interface manager 153 may allocate the first data segment DF1 to the first storage device 200 - 1 , may allocate the second data segment DF2 to the first storage device 200 - 2 , and may allocate the third data segment DF3 to the first storage device 200 - 3 .

[0059] The interface manager 153 may control the first interface circuit 110 so that a plurality of data fragments DF1 to DF3 are transmitted in parallel to the first storage devices 200-1 to 200-3 assigned thereto. Under the control of the interface manager 153, a data path DP may be formed in the first interface circuit 110. For example, the first interface circuit 110 may form the data path DP by a switching operation of at least one switch. The interface manager 153 may transmit a plurality of data fragments DF1 to DF3 corresponding to the write data WD to the first interface circuit 110. The first interface circuit 110 may transmit a plurality of data fragments DF1 to DF3 corresponding to the write data WD and the write command in parallel to a plurality of first storage devices 200-1 to 200-3 corresponding thereto.

[0060] Meanwhile, the interface manager 153 may determine whether the event data ED corresponds to mandatory item data or optional item data based on a specific field of the packet PCK received through the second interface circuit 120. The interface manager 153 may divide the event data ED corresponding to the mandatory item data into a plurality of data fragments DF1 to DF3, and may not divide the event data ED corresponding to the optional item data. The interface manager 153 may divide the mandatory item data and the optional item data.

[0061] The plurality of first storage devices 200-1 to 200-3 may respectively receive write commands and data segments DF1 to DF3 corresponding to the write data WD through the first interface circuit 110. The first storage devices 200-1 to 200-3 may respectively store the data segments DF1 to DF3 allocated thereto. And, the interface manager 153 may set the name space NS of each of the plurality of data segments DF1 to DF3 as the event data space EDS.

[0062] The first storage device 200-1 may store the first data fragment DF1 corresponding to the write data WD in the event data space EDS depending on the set namespace NS. The first storage device 200-2 may store the second data fragment DF2 corresponding to the write data WD in the event data space EDS according to the set namespace NS. The first storage device 200-3 may store the third data fragment DF3 corresponding to the write data WD in the event data space EDS. A plurality of data fragments DF1 to DF3 may be stored in parallel in the event data space EDS. That is, when the first data fragment DF1 is stored in the event data space EDS of the first storage device 200-1, the second data fragment DF2 may be stored in the event data space EDS of the first storage device 200-2, and the third data fragment DF3 may be stored in the event data space EDS of the first storage device 200-3.

[0063] The interface manager 153 may control the first interface circuit 110 so as to form a data path for sending write data in parallel. In this way, a plurality of data fragments DF1 to DF3 may be sent in parallel. This may mean that the time taken to write the event data ED is shortened. At the same time, referring to Figure 4 The event data ED is described as being included in one packet PCK, but the event data ED may be data distributed and transmitted through a plurality of packets.

[0064] Figure 5 Detailed Description of the Invention FIG. 1 is a diagram for describing a flow identifier according to an embodiment of the present disclosure. Figure 5 , the first interface circuit 110 may add a stream identifier SID to the write data WD. The first storage device 200-1 may determine a storage block to which the write data WD will be written based on the stream identifier SID.

[0065] The first storage device 200-1 may support multiple streams. That is, the first storage device 200-1 may classify and process data depending on the stream identifier SID. For example, the first storage device 200-1 may allocate the same storage block for data having the same stream identifier SID. The data fragment DF22 and the data fragment DF23 may be data fragments divided from different event data ED. The first interface circuit 110 may add the stream identifier SID of S0 to the zone data ZD32, and may add the stream identifier SID of S1 to the data fragment DF22 and the data fragment DF23 obtained by dividing the event data ED.

[0066] The first storage device 200-1 may receive write data WD and a stream identifier SID. The flash translation layer manager 214-1 included in the storage controller 210-1 may map the logical address of the write data WD to a physical address based on the stream identifier SID. In this case, mapping may be performed so that write data corresponding to the same stream identifier SID is written to the same storage block among the plurality of storage blocks included in the non-volatile storage device 220-1. For example, the flash translation layer manager 214 may identify that the stream identifier SID of the region data ZD32 is S0. The region data ZD32 may be written into the storage block BLK_A of the non-volatile storage device 220-1, in which the region data ZD31 is pre-stored.

[0067] The flash translation layer manager 214 may recognize that the stream identifier SID of the data segment DF22 is S1, and may write the data segment DF22 into the storage block BLK_B that previously stored the data segment DF21. The flash translation layer manager 214 may recognize that the stream identifier SID of the data segment DF23 is S1, and may write the data segment DF23 into the storage block BLK_B that previously stored the data segments DF21 and DF22.

[0068] In the state where the storage block BLK_B is completely filled with data, when receiving the write data WD with the stream identifier SID being S1, the flash translation layer manager 214 may map the storage block BLK_C different from the storage block BLK_B to the logical address of the write data WD. Afterwards, the flash translation layer manager 214 may write the write data WD with the stream identifier SID being S1 into the storage block BLK_C.

[0069] When the first interface circuit 110 adds the same stream identifier SID to the data segments DF22 and DF23 of the event data ED, the physical space of the data segments DF22 and DF23 can be separated from the physical space of any other data. That is, the electronic device 100 can distinguish the event data from any other data so as to store them in different physical spaces. In this way, the storage device can effectively manage the stored data.

[0070] Figure 6 2 is a diagram for describing an operation of storing combined event data according to an embodiment of the present disclosure. Figure 4 and Figure 6 , the event manager 151 may read a plurality of data fragments DF1, DF2, and DF3 respectively stored in the event data space EDS of the plurality of first storage devices 200-1, 200-2, and 200-3. The event manager 151 may combine the plurality of data fragments DF1 to DF3 to generate event data ED_C. The event data ED_C is the event data divided into reference Figure 4 The data segments DF1 to DF3 described are the same data as the event data ED previously received through the second interface circuit 120 .

[0071] The event data ED_C combined by the event manager 151 can be stored in the spare space SS of the second storage device 200-4. The event data ED_C stored in the spare space SS can be set to "read-only data". That is, the event data ED_C stored in the spare space SS can be prevented from being forged (for example, deleted or modified). In this way, the reliability of the event data ED_C can be ensured.

[0072] The event manager 151 may combine the data fragments DF1, DF2, and DF3. The event manager 151 may generate combined event data ED_C through the data combination. The event manager 151 may send the combined event data ED_C to a spare storage device among the plurality of storage devices.

[0073] Figure 7 is a diagram describing how to perform a data partitioning operation based on the available capacity of each of a plurality of storage devices according to an embodiment of the present disclosure. Figure 7 , the event processing circuit 150 of the electronic device 100 may also include a workload analyzer 154.

[0074] The event manager 151 may output a monitoring signal MS in response to an event signal ES from the event detector 152. The workload analyzer 154 may monitor the state of each of the plurality of first storage devices 200-1 to 200-3 in response to the monitoring signal MS. In this way, the workload analyzer 154 may identify the state of the storage device including the available capacity for each of the plurality of first storage devices 200-1 to 200-3. For example, the workload analyzer 154 may identify the used capacity UC and the available capacity AC of each of the plurality of first storage devices 200-1 to 200-3. In an embodiment, the used capacity UC may refer to the capacity of previously stored data, and the available capacity AC may refer to the capacity capable of storing data.

[0075] The workload analyzer 154 may generate storage usage information SUI as status information of the plurality of first storage devices 200-1 to 200-3. The workload analyzer 154 may transmit the storage usage information SUI to the event manager 151. Then, the event manager 151 may transmit a data partition signal DDS to the interface manager 153 based on the storage usage information SUI.

[0076] The interface manager 153 may divide the event data ED into a plurality of data segments DF1 and DF2 based on the available capacity AC of each of the first storage devices 200-1 to 200-3. For example, the interface manager 153 may determine the number of data segments based on the number of storage devices whose available capacity AC is greater than the threshold capacity CTh. The available capacity AC of the first storage device 200-1 and the available capacity AC of the first storage device 200-2 are greater than the threshold capacity CTh, and the available capacity AC of the first storage device 200-3 is less than the threshold capacity CTh. Therefore, when dividing the event data ED, the interface manager 153 may determine that the number of data segments is two (2). The interface manager 153 may divide the event data ED into two data segments DF1 and DF2 depending on the number of data segments thus determined. An example in which the interface manager 153 divides the event data ED into two data segments DF1 and DF2 is described above, but the number of data segments may be determined to be suitable for data transmission, and is not limited to two (2).

[0077] The interface manager 153 may allocate the first data segment DF1 to the first storage device 200-1 and allocate the second data segment DF2 to the first storage device 200-2. The interface manager 153 may set a name space NS of each of the plurality of data segments DF1 and DF2 as an event data space EDS.

[0078] The interface manager 153 may send the data fragments DF1 and DF2 corresponding to the write data WD to the first storage device 200-1 and the first storage device 200-2 respectively through the first interface circuit 110. The interface manager 153 may control the first interface circuit 110 to form a data path for parallel transmission of the write data. The first interface circuit 110 may send the data fragments DF1 and DF2 to the first storage device 200-1 and the first storage device 200-2 in parallel along the formed data path DP. In this way, the time for storing the event data ED may be shortened.

[0079] The first storage device 200-1 may store the first data segment DF1 corresponding to the write data WD in the event data space EDS according to the set namespace NS. The first storage device 200-2 may store the second data segment DF2 corresponding to the write data WD in the event data space EDS depending on the set namespace NS.

[0080] A plurality of data segments DF1 and DF2 may be stored in parallel in the event data space EDS. That is, when the first data segment DF1 is stored in the event data space EDS of the first storage device 200-1, the second data segment DF2 may be stored in the event data space EDS of the first storage device 200-2.

[0081] Depending on the available capacity AC, the data input / output speed of the first storage devices 200-1 to 200-3 may be different. The threshold capacity CTh may be set to the capacity of the boundary of the speed reduction of the storage device. That is, the data fragment may not be allocated to the first storage device 200-3 where the speed reduction occurs, and the data fragments DF1 and DF2 may be sent to the first storage devices 200-1 and 200-2 where the speed reduction does not occur, respectively. In this way, the event data ED can be stored quickly.

[0082] In addition, since the interface manager 153 can appropriately allocate the available spaces of the first storage devices 200-1 to 200-3 by storing the data fragments DF1 and DF2 of the event data ED in the first storage devices 200-1 and 200-2 that ensure the available capacity AC.

[0083] Figure 8 FIG. 1 is a diagram describing how to perform a data partitioning operation based on the states of multiple queues according to an embodiment of the present disclosure. Figure 8 , the event manager 151 may output a monitoring signal MS in response to the event signal ES.

[0084] The workload analyzer 154 may monitor the status of the plurality of queues Q1, Q2, etc. in response to the monitoring signal MS. In this way, the workload analyzer 154 may identify the status of the plurality of queues Q1, Q2, etc. The plurality of queues Q1, Q2, etc. may be submission queues storing commands to be submitted to the first storage devices 200-1, 200-2, and 200-3, or may be completion queues storing information that commands submitted to the first storage devices 200-1, 200-2, and 200-3 have been completed.

[0085] Because commands that are not processed by the first storage devices 200-1 to 200-3 exist in part or all of the plurality of queues Q1, Q2, etc. The workload analyzer 154 may check the states of the plurality of queues Q1, Q2, etc. to identify the workload of the first storage devices 200-1 to 200-3. The workload analyzer 154 may transmit queue state information QSI about the states of the plurality of queues Q1, Q2, etc. to the event manager 151. The event manager 151 may transmit a data division signal DDS based on the queue state information QSI to the interface manager 153.

[0086] The interface manager 153 may divide the event data ED into a plurality of data segments DF1, DF2, and DF3 based on the workload of the first storage devices 200-1 to 200-3 according to the states of the plurality of queues Q1, Q2, etc. For example, the interface manager 153 may determine the sizes of the plurality of data segments DF1 to DF3 according to the workload of the plurality of first storage devices 200-1 to 200-3. As an example, the interface manager 153 may determine the size of the data segment to be inversely proportional to the workload of each of the plurality of first storage devices 200-1 to 200-3. Assuming that the workload of the first storage device 200-1 is the largest and the workload of the first storage device 200-2 is the largest, when dividing the event data ED into a plurality of data segments DF1 to DF3, the interface manager 153 may determine that the size of the data segment DF1 is smaller than the size of the remaining data segments DF2 and DF3, and may determine that the size of the data segment DF2 is larger than the remaining data segments DF1 and DF3.

[0087] For example, the interface manager 153 may allocate the first data segment DF1 to the first storage device 200-1, the second data segment DF2 to the first storage device 200-2, and the third data segment DF3 to the first storage device 200-3. The interface manager 153 may set the namespace NS of each of the plurality of data segments DF1 to DF3 as the event data space EDS.

[0088] The interface manager 153 may transmit the data segments DF1 to DF3 corresponding to the write data WD to the first storage device 200-1, the first storage device 200-2, and the first storage device 200-3 in parallel. The first storage device 200-1 may store the first data segment DF1 corresponding to the write data WD in the event data space EDS according to the set namespace NS. The first storage device 200-2 may store the second data segment DF2 corresponding to the write data WD in the event data space EDS depending on the set namespace NS. The first storage device 200-3 may store the third data segment DF3 corresponding to the write data WD in the event data space EDS depending on the set namespace NS.

[0089] Multiple data segments DF1 to DF3 can be stored in parallel in the event data space EDS. That is, when the first data segment DF1 is stored in the event data space EDS of the first storage device 200-1, the second data segment DF2 can be stored in the event data space EDS of the first storage device 200-2, and the third data segment DF3 can be stored in the event data space EDS of the first storage device 200-3.

[0090] The interface manager 153 may control the first interface circuit 110 so as to form a data path for sending write data in parallel. In this way, a plurality of data fragments DF1 to DF3 may be sent in parallel. This may mean that the time taken to write the event data ED is shortened.

[0091] The workloads of the first storage devices 200-1 to 200-3 may be different. The first data fragment DF1 of a small size may be allocated to the first storage device 200-1 having a large workload, and the third data fragment DF3 of a large size may be allocated to the first storage device 200-3 having a small workload. In this way, the workloads of the first storage devices 200-1 to 200-3 may be balanced.

[0092] Meanwhile, the size of each data segment DF1 to DF3 may be determined based on the reference data size. For example, assuming that the reference data size is 8KB. In this case, the size of the first data segment DF1 may be 8KB, the size of the second data segment DF2 may be 24KB, and the size of the third data segment DF3 may be 16KB. That is, the event data ED may be divided into data segments DF1 to DF3, each of which has a size corresponding to an integer multiple of 8KB.

[0093] Fig. 9 is a diagram for describing an operation of sending data to each of a plurality of storage devices based on data priority according to an embodiment of the present disclosure. Fig. 9, the interface manager 153 may divide the event data ED into a plurality of data segments DF1, DF2, and DF3. The interface manager 153 may set the priority PR of the plurality of data segments DF1 to DF3 to the highest value. The interface manager 153 may allocate the first data segment DF1 to the first storage device 200-1, may allocate the second data segment DF2 to the first storage device 200-2, and may allocate the third data segment DF3 to the first storage device 200-3.

[0094] For example, the priority level PR applied to the first interface circuit 110 may be one of an emergency level "U", a high level "H", a medium level "M", and a low level "L". Among the priority levels PR set to one of the emergency level "U", the high level "H", the medium level "M", and the low level "L", the emergency level "U" may be the highest and the low level "L" may be the lowest. The interface manager 153 may set the priority levels PR of the plurality of data fragments DF1, DF2, and DF3 to the emergency level "U".

[0095] The processor 130 may execute a plurality of virtual machines VM1 to VM3. Each of the plurality of virtual machines VM1 to VM3 may control a corresponding region. The virtual machine VM1 may generate region data ZD1. The virtual machine VM1 may send the region data ZD1 to the first interface circuit 110 so as to be written into the first storage device 200-1. In this case, the virtual machine VM1 may set the priority PR to a high level "H" according to the importance of the region data ZD1. The virtual machine VM2 may generate region data ZD2. The virtual machine VM2 may send the region data ZD2 to the first interface circuit 110 so as to be written into the first storage device 200-2. In this case, the virtual machine VM2 may set the priority PR to a medium level "M" according to the importance of the region data ZD2. The virtual machine VM3 may generate region data ZD3. The virtual machine VM3 may send the region data ZD3 to the first interface circuit 110 so as to be written into the first storage device 200-3. In this case, the virtual machine VM3 may set the priority PR to a low level "L" depending on the importance of the region data ZD3.

[0096] The first interface circuit 110 may change the order of transmitting the data segments DF1 to DF3 and the regional data ZD1 to ZD3 to the plurality of first storage devices 200-1 to 200-3 depending on the priorities of the data segments DF1 to DF3 and the regional data ZD1 to ZD3. For example, the first interface circuit 110 may receive write data WD having a priority PR from the processor 130. The write data WD of the first storage device 200-1 is the regional data ZD1, the write data WD of the first storage device 200-2 is the regional data ZD2, and the write data WD of the first storage device 200-3 is the regional data ZD3.

[0097] Before the first interface circuit 110 transmits the regional data ZD1 to ZD3 to the plurality of first storage devices 200-1 to 200-3, the first interface circuit 110 may receive the plurality of data fragments DF1 to DF3 from the interface manager 153. In this case, the priority PR of the plurality of data fragments DF1 to DF3 corresponds to an emergency level "U", the priority of the regional data ZD1 corresponds to a high level "H", the priority of the regional data ZD2 corresponds to a medium level "M", and the priority of the regional data ZD3 corresponds to a low level "L".

[0098] Before the first interface circuit 110 transmits the region data ZD1 to ZD3 to the corresponding storage devices 200-1 to 200-3, the first interface circuit 110 may transmit the data fragments DF1 to DF3 to the corresponding storage devices 200-1 to 200-3, respectively. After the data fragments DF1 to DF3 are completely transmitted, the first interface circuit 110 may transmit the region data ZD1 to ZD3 to the corresponding storage devices 200-1 to 200-3, respectively.

[0099] In this way, the data segments DF1 to DF3 of the event data ED can be written to the first storage devices 200-1 to 200-3 before any other data. Because the event data ED is data that needs to be recorded quickly, the data segments DF1 to DF3 can be stored in the first storage devices 200-1 to 200-3 before any other data, and therefore, the reliability of the event data ED can be increased.

[0100] Meanwhile, in the event data ED, only the priority PR of the mandatory item data may be set to the highest value, and the priority PR of the optional item data may be set to a default value. The default value may be a value corresponding to the priority PR set in the packet including the event data ED.

[0101] Fig.10 is a diagram showing an Ethernet frame according to an embodiment of the present disclosure. Fig.10 , the Ethernet frame may include a VLAN tag field and a type field. The preamble field may be a field that notifies the Ethernet packet input and may be used for timing synchronization.

[0102] The Start Frame Indicator (SFD) field is a field indicating the start of an Ethernet frame, and the Indication Destination MAC Address field starts after the Start Frame Indicator (SFD).

[0103] The target MAC address field is a field indicating the physical address of the receiving side of the received packet. The second interface circuit 120 may include an Ethernet interface. Figure 1When the electronic device 100 receives the event data ED, the destination MAC address of the Ethernet packet received by the second interface circuit 120 may correspond to the physical address of the Ethernet interface included in the second interface circuit 120.

[0104] The source MAC address field is a field that indicates the physical address of the device that sent the Ethernet packet. Figure 2 When the electronic device 100 receives event data ED, the source MAC address of the Ethernet packet received by the electronic device 100 may be a physical address of a regional control unit that generates the Ethernet packet among the plurality of regional control units 301 , 302 , 303 , and 304 .

[0105] The VLAN tag field is a field indicating an identifier used in a virtual local area network. The VLAN tag field may include a priority code point (PCP) field indicating a priority. The type field may define the length of the data field or may indicate an Ethernet type.

[0106] The payload field is a variable length field and includes data to be sent through the Ethernet packet. When the length of the payload is shorter than the minimum length, a PAD field may be added, which is padding added to meet the minimum length of the payload. The CRC checksum field is a field filled in order to detect errors in Ethernet data packets. The CRC checksum is used to detect bit errors occurring in Ethernet frames through a cyclic redundancy check.

[0107] Figure 1 The electronic device 100 may receive an Ethernet packet including event data ED through the second interface circuit 120. The event detector 152 may detect the Ethernet packet, and may determine whether event data exists in the payload field, or may determine the type of the event data. For example, the event detector 152 may determine whether event data ED exists in the payload field based on a VLAN tag field or a type field included in the Ethernet packet. The event detector 152 may determine whether event data ED exists in the payload field based on a subfield included in the payload field. The event detector 152 may determine whether event data ED exists in the payload field based on a VLAN tag field, a type field, or a subfield of the payload field included in the Ethernet packet.

[0108] The interface manager 153 can determine whether the event data ED of the payload field is mandatory item data or optional item data based on the VLAN tag field or the type field included in the Ethernet packet. The interface manager 153 can determine whether the event data ED of the payload field is mandatory item data or optional item data based on the subfields included in the payload field.

[0109] Fig.11 is a flowchart showing an operating method of an electronic device according to an embodiment of the present disclosure. Fig.11 According to an embodiment of the present disclosure, the operating method of the electronic device 100 installed on the automatic vehicle may include detecting event data (S110). The operating method of the electronic device 100 installed on the automatic vehicle may include outputting an event signal when the event data is detected (S120).

[0110] The operating method of the electronic device 100 installed on the automatic carrier may include dividing the event data into a plurality of data segments in response to the event signal (S130). The operating method of the electronic device 100 installed on the automatic carrier may include allocating the plurality of data segments to two or more storage devices (S140). The operating method of the electronic device 100 installed on the automatic carrier may include sending the plurality of data segments to the allocated storage devices in parallel (S150).

[0111] Meanwhile, the operating method of the electronic device 100 mounted on the automatic carrier may include identifying the available capacity of each of the plurality of storage devices in response to the event signal. In this case, operation S130 may include determining the number of data segments based on the available capacity of each of the plurality of storage devices.

[0112] In an embodiment, the operating method of the electronic device 100 installed on the automatic carrier may further include identifying the status of multiple queues corresponding to the multiple storage devices respectively in response to the event signal. In this case, operation S130 may also include determining the size of each of the multiple data fragments based on the status of the multiple queues.

[0113] At the same time, the operating method of the electronic device 100 installed on the automatic carrier may also include identifying the type of event data, setting the priority of multiple data fragments to the highest value based on the event data being the first type, and changing the order of sending data to two or more storage devices based on the priority.

[0114] Fig.12 is a diagram showing a configuration of a plurality of storage devices according to another embodiment of the present disclosure. Fig.12 , an electronic system according to another embodiment of the present disclosure may include an electronic device 1000, a RAID (Redundant Array of Independent Disks) controller 1100, and a plurality of storage devices 2000-1, 2000-2, 2000-3, and 2000-4.

[0115] Storage device 2000-1, storage device 2000-2 and storage device 2000-3 can constitute a RAID storage system. That is, storage devices 2000-1 to 2000-3 can constitute a high-capacity storage device. In this way, electronic device 1000 can distribute and store regional data and event data to storage devices 2000-1 to 2000-3. In this case, even if a storage device fails, electronic device 1000 can also recover data. One of storage devices 2000-1 to 2000-3 constituting the RAID storage system can store RAID parity information. Each of some or all storage devices 2000-1 to 2000-3 can include an area for storing RAID parity information.

[0116] The RAID controller 3100 can control the storage devices 2000-1 to 2000-3 so that the storage devices 2000-1 to 2000-3 constitute a RAID storage system. The RAID controller 3100 can be implemented separately outside the electronic device 1000 as shown in the figure, or can be implemented inside the electronic device 1000. Each of the storage devices 2000-1 to 2000-3 may include a zone data space ZDS and an event data space EDS that are logically distinguished from each other, such as Figure 2 The first storage devices 200-1, 200-2 and 200-3. The storage device 200-4 may include a spare space SS, such as Figure 2 The second storage device 200-4. The storage device 2000-4 may store only a copy of the event data ED.

[0117] Fig.13 Is used to describe Figure 2 FIG. 1 is a diagram of an example of a storage domain of a storage device. Fig.13 , the storage device 200-1 may include an XLC domain XLCA and an SLC domain SLCA. The XLC domain XLCA is a domain in which a memory cell stores at least two bits or more. Data may be written to the XLC domain XLCA in the following schemes: 1) a multi-layer cell (MLC) scheme in which one memory cell stores two bits, 2) a triple-layer cell (TLC) scheme in which one memory cell stores three bits, or 3) a quad-layer cell (QLC) scheme in which one memory cell stores four bits. The XLC domain XLCA provides a relatively large capacity by using a small number of memory cells, and therefore, the XLC domain XLCA is suitable for storing a large amount of data. The storage device 200-1 may store data from the XLC domain XLCA. Figure 2 The electronic device 100 receives the zone data ZD.

[0118] The SLC domain SLCA is a domain in which a memory cell stores one bit. The SLC domain SLCA can store data faster than the XLC domain XLCA. In addition, because the distance between the threshold voltage distributions of the memory cells in the SLC domain SLCA is relatively large, the SLC domain SLCA may be advantageous in maintaining the data stored therein. The storage device 200-1 may store data fragments DF obtained by dividing the event data ED received from the electronic device 100. When the data fragments DF are written to the SLC domain SLCA, the storage device 200-1 may quickly store the event data ED if the trigger condition is met, and therefore, the reliability of the event data ED may be guaranteed.

[0119] Fig.14 is a schematic diagram showing the automotive area and centralized architecture of an autonomous vehicle. Fig.14 , the automatic vehicle 3000 may include a plurality of zones Z1, Z2, . . . , Z6. The automotive zone and centralized architecture, which is one of the electrical / electronic system architectures, may be applied to the automatic vehicle 3000.

[0120] The first area Z1 is an area corresponding to the right front of the automatic vehicle 3000, the second area Z2 is an area corresponding to the right side of the automatic vehicle 3000, and the third area Z3 is an area corresponding to the right rear of the automatic vehicle 3000. The fourth area Z4 is an area corresponding to the left front of the automatic vehicle 3000, the fifth area Z5 is an area corresponding to the left side of the automatic vehicle 3000, and the sixth area Z6 is an area corresponding to the left rear of the automatic vehicle 3000. Electronic control devices (such as various sensors, cameras, LIDAR, actuators and inertial measurement units, gateways) can be in multiple areas Z1, Z2, ..., Z6. The gateway GW can send the data generated in the corresponding area to the gateway GW or electronic device ELD adjacent to it. The electronic device ELD can receive data in multiple areas Z1, Z2, ..., Z6. For example, the regional data generated in the first area Z1 can be sent to the gateway GW of the first area Z1, and then can be sent to the electronic device ELD through the gateway GW of the second area Z2.

[0121] The event data may be in a plurality of zones Z1, Z2, ..., Z6, and may be transmitted to the electronic device ELD in the same scheme as the zone data. Meanwhile, the plurality of zones Z1, Z2, ..., Z6 may be set in a variety of schemes.

[0122] The automatic vehicle 3000 may include one or more central processors CP. The central processor CP may execute a virtual machine to control multiple zones Z1, Z2, ..., Z6. Fig.14As shown, the central processor CP can be implemented independently of the electronic device ELD. However, the present disclosure is not limited thereto. For example, the central processor CP can be implemented in the electronic device ELD. In this case, the central processor CP can correspond to the processor of the electronic device ELD.

[0123] The automatic vehicle 3000 may include multiple storage devices SD. The multiple areas Z1, Z2, ..., Z6 may be stored in the multiple storage devices SD via the electronic device ELD. The area data generated in the central processor CP may also be stored in the multiple storage devices SD via the electronic device ELD.

[0124] According to an embodiment of the present disclosure, an electronic device installed on an automatic vehicle, an electronic system including the electronic device, and an operation method thereof can divide event data associated with a vehicle accident into multiple data segments, and write the multiple data segments in parallel to multiple storage devices. In this way, the event data can be recorded quickly and the loss of the event data can be prevented.

[0125] The amount of data generated in autonomous vehicle architectures is increasing. In the event of an accident, if the data generated in the vehicle is not quickly stored, the data required to analyze the cause of the accident may be lost due to vehicle failure. Therefore, a method is needed to quickly store the data generated when an accident occurs.

[0126] While the present invention has been described with reference to the embodiments thereof, it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as described in the following claims.

Claims

1. An electronic device configured to be mounted on an automatic vehicle, comprising: a first interface circuit configured to communicate with a plurality of storage devices; a second interface circuit configured to communicate with a plurality of regions of the automated vehicle; an event detector configured to output an event signal in response to detecting event data received through the second interface circuit; an event manager configured to output a data partition signal in response to the event signal; as well as The interface manager is configured to: in response to a data partitioning signal, divide the event data into multiple data segments, respectively allocate the multiple data segments to two or more storage devices among the multiple storage devices, and control the first interface circuit so that the multiple data segments are respectively sent to the allocated two or more storage devices.

2. The electronic device according to claim 1, wherein: The plurality of data segments are divided in units of reference data size and are respectively written in event data spaces included in the two or more storage devices.

3. The electronic device according to claim 2, wherein: The first interface circuit adds a same stream identifier to each of the plurality of data fragments.

4. The electronic device according to claim 2, wherein: The event manager is also configured to: generating combined event data by combining the data fragments stored in the event data space; and The combined event data is sent to a spare storage device among the plurality of storage devices.

5. The electronic device according to claim 1, in, The event manager is configured to output a monitoring signal based on the event signal; wherein the electronic device further comprises a workload analyzer configured to identify an available capacity of each of the plurality of storage devices in response to the monitoring signal; and The interface manager divides the event data into the plurality of data segments based on available capacity of each of the plurality of storage devices.

6. The electronic device according to claim 5, in, The workload analyzer is further configured to identify, in response to the monitoring signal, states of a plurality of queues respectively corresponding to the plurality of storage devices; as well as The interface manager is configured to divide the event data into the plurality of data segments based on available capacity of each of the plurality of storage devices.

7. The electronic device according to claim 1, wherein: The interface manager is configured to identify a type of the event data, and when the event data is identified as a first type, set the priority of the plurality of data segments to a highest value.

8. The electronic device according to claim 7, wherein: The first interface circuit is configured to change an order of data to be sent to each of the plurality of storage devices based on the priority level.

9. The electronic device according to claim 1, wherein: The second interface circuit includes an Ethernet interface.

10. The electronic device according to claim 9, wherein: The event detector is configured to identify event data based on at least one field included in a packet received through the second interface circuit.

11. An electronic system comprising: Electronic equipment configured to be mounted on an automated vehicle; A regional control unit corresponding to a plurality of regions of the automatic vehicle; as well as a plurality of first storage devices, each first storage device comprising an event data space, Wherein, the electronic device is configured as follows: dividing event data received from one of the regional control units into a plurality of data segments; allocating the plurality of data segments to two or more first storage devices among the plurality of first storage devices; and sending the plurality of data segments to corresponding first storage devices among the two or more first storage devices; and Wherein, each of the two or more first storage devices is configured to write a corresponding data segment among the plurality of data segments into the event data space.

12. An electronic system according to claim 11, wherein the electronic device is configured to add the same stream identifier to each of the multiple data fragments; and wherein each of the two or more first storage devices is configured to write the corresponding data fragment into the same storage block based on the stream identifier.

13. The electronic system according to claim 11, further comprising: at least one second storage device; as well as The electronic device is configured as follows: generating combined event data by writing a combination of the plurality of data fragments in respective event data spaces of the two or more first storage devices; as well as The combined event data is written to a second storage device.

14. The electronic system according to claim 11, wherein the electronic device is configured as: identifying an available capacity of each of the plurality of first storage devices; and The event data is divided into the plurality of data segments based on an available capacity of each of the plurality of first storage devices.

15. The electronic system according to claim 14, wherein the electronic device is configured to: identifying states of a plurality of queues respectively corresponding to the plurality of first storage devices; and The event data is divided into the plurality of data segments based on the states of the plurality of queues.

16. An electronic system according to claim 11, wherein the electronic device is configured to: identify the type of event data; when the event data is identified as a first type, set the priority of the multiple data fragments to a highest value; and change the order of sending the multiple data fragments to the two or more first storage devices based on the priority.

17. A method of operating an electronic device configured to be mounted on an automated vehicle, comprising: Detection event data; outputting an event signal in response to detection of the event data; dividing the event data into a plurality of data segments in response to the event signal; distributing the plurality of data segments to two or more storage devices; as well as The plurality of data segments are sent to the allocated two or more storage devices.

18. The method according to claim 17, further comprising: identifying available space in each of the plurality of storage devices in response to the event signal; wherein the partitioning comprises determining the number of the plurality of data segments based on available space of each of the plurality of storage devices; and The sending includes sending the multiple data fragments to the two or more storage devices in parallel.

19. The method according to claim 18, further comprising: In response to the event signal, identifying states of a plurality of queues respectively corresponding to the plurality of storage devices; as well as The dividing includes determining a size of each of the plurality of data fragments based on states of the plurality of queues.

20. The method of claim 17, further comprising: Identify the type of event data; Based on the event data being identified as the first type, setting the priorities of the plurality of data segments to a highest value; as well as An order in which the plurality of data segments are sent to the two or more storage devices is changed based on the priority.

Images