Performing write operations at improved write speeds based on potential events
By detecting potential events in the vehicle DVR system, the background operation is paused, the writing speed is improved, and video data is written to the memory, which solves the problem of data loss when power is lost, and improves the reliability of data storage and system performance.
Patent Information
- Application Number
- CN202310513290.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-09
- Publication Date
- 2024-11-12
AI Technical Summary
In a vehicle DVR system, the captured video data cannot be successfully written to the nonvolatile memory in a timely manner when power is lost, resulting in data loss and affecting event investigation and system performance.
By detecting potential events (such as traffic accidents), pause the background operations of the memory device, such as defragmentation and refresh scans, prioritize writing operations to improve data writing speed, write video data to memory, and ensure that all savings are done before power interruption Possibly more data.
Improve data writing speed, ensures that as much video data as possible is successfully saved when an event occurs, reduces the risk of data loss, enhances the system's record integrity and customer experience, while avoiding the additional cost of power loss protection circuits and Complexity.
Smart Images

Figure CN118942513A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to memory devices, memory device operations, and, for example, to performing write operations at increased write speeds based on potential events. Background Art
[0002] Nonvolatile memory devices, such as NAND memory devices, can use circuitry to electrically enable programming, erasing, and storage of data even when power is not supplied. Nonvolatile memory devices can be used in various types of electronic devices, such as computers, mobile phones, or automotive computing systems, among other examples.
[0003] A nonvolatile memory device may include a memory cell array, a page buffer, and a column decoder. In addition, a nonvolatile memory device may include a control logic unit (such as a controller), a row decoder or an address buffer, among other examples. A memory cell array may include a string of memory cells connected to a bit line extending in a column direction.
[0004] A memory cell, which may be referred to as a "cell" or "data cell", of a nonvolatile memory device may include a current path formed between a source and a drain on a semiconductor substrate. The memory cell may further include a floating gate and a control gate formed between insulating layers on the semiconductor substrate. A programming operation (sometimes referred to as a write operation) of a memory cell is typically accomplished by grounding the source and drain regions of the memory cell and the semiconductor substrate of the bulk region and applying a high positive voltage, which may be referred to as a "programming voltage", "programming power voltage" or "VPP", to the control gate to generate Fowler-Nordheim tunneling (referred to as "FN tunneling") between the floating gate and the semiconductor substrate. When FN tunneling occurs, electrons in the bulk region accumulate on the floating gate by the electric field of VPP applied to the control gate to increase the threshold voltage of the memory cell.
[0005] The erase operation of the memory cells is performed concurrently in units of sectors (referred to as "blocks") that share a bulk region by applying a high negative voltage, which may be referred to as an "erase voltage" or "Vera," to the control gate and applying a configured voltage to the bulk region to generate FN tunneling. In this case, electrons accumulated on the floating gate are discharged to the source region, so that the memory cells have an erase threshold voltage distribution.
[0006] Each memory cell string may have a plurality of floating gate type memory cells connected in series with each other. An access line (sometimes referred to as a "word line") extends in a row direction, and a control gate of each memory cell is connected to a corresponding access line. A nonvolatile memory device may include a plurality of page buffers connected between the bit lines and a column decoder. The column decoder is connected between the page buffer and the data line. Summary of the invention
[0007] On the one hand, the present application provides a memory device comprising: a memory; and a controller configured to: receive a signal indicating a potential event from a host device; suspend background operations of the memory device based on the signal; and perform a write operation to write data to the memory while the background operation is suspended, wherein based on the background operation being suspended during the write operation, a write speed associated with the write operation is a write speed that is increased compared to a default write speed.
[0008] On the other hand, the present application provides a method, comprising: receiving, by a memory device and from a host device, a signal indicating a potential event; suspending, by the memory device and based on the signal, a background operation of the memory device; and performing, by the memory device, a write operation to write data to the memory while the background operation is suspended, wherein based on the background operation being suspended during the write operation, a write speed associated with the write operation is a write speed that is increased compared to a default write speed.
[0009] On the other hand, the present application provides a system comprising: a host device configured to: detect a potential event based on sensor information; and transmit a signal indicating the potential event; and a memory device configured to: receive the signal indicating the potential event from the host device; stop background operations of the memory device based on the signal; and perform a write operation to write data to the memory when the background operation is stopped, wherein based on the background operation being stopped during the write operation, a write speed associated with the write operation is a write speed that is increased compared to a default write speed. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 is a diagram illustrating an example system capable of performing write operations at an increased write speed based on a latent event.
[0011] Figure 2 is a diagram of example components included in a memory device.
[0012] Figure 3 is a diagram illustrating an example of performing a write operation at an increased write speed based on a potential event.
[0013] Figure 4 is a diagram illustrating an example of a vehicle digital video recorder (DVR) system capable of performing write operations at an increased write speed based on a latent event.
[0014] Figure 5is a flow chart of an example method associated with performing a write operation at an increased write speed based on a potential event. DETAILED DESCRIPTION
[0015] A vehicle digital video recorder (DVR) system (e.g., a dashboard camera or an event data recorder) may be an onboard camera (e.g., a camera mounted on a vehicle) that continuously records one or more views associated with a vehicle. The one or more views may include an external view of the vehicle, such as a front view, a rear view, and / or one or more side views. The one or more views may include an internal view of the vehicle, such as a view of a front passenger and / or a rear passenger in the vehicle. The vehicle DVR system may capture various types of information associated with the vehicle. For example, the vehicle DVR system may capture audio and / or video (audio / video) information associated with the one or more views. The vehicle DVR system may also capture acceleration data, speed data, positioning data, and / or other types of information associated with the vehicle. The vehicle DVR system may capture information associated with the vehicle while the vehicle is moving and / or while the vehicle is stationary or closed (e.g., stopped or parked at a red light).
[0016] The vehicle DVR system can provide captured information (e.g., audio / video information and / or image information) as evidence of an incident associated with a vehicle. The incident may include a road accident or vandalism (e.g., when the vehicle is parked). The vehicle DVR system can serve as an accurate eyewitness and provide reliable evidence associated with the incident, which helps resolve the issue of which party is at fault for causing the incident to occur.
[0017] In some cases, a vehicle DVR system may lose power based on an event. For example, a power supply associated with the vehicle DVR system may be damaged during a road accident, and power may no longer be provided to the vehicle DVR system, causing the operation of the vehicle DVR system to terminate. Some information captured by the vehicle DVR system, such as audio / video information, may not be successfully stored on the memory of the vehicle DVR system before the vehicle DVR system is terminated. For example, the last few seconds of captured video data may not be fully saved during a vehicle collision, especially when the power supply of the vehicle DVR system is affected. The vehicle DVR system may capture information, and the captured information may be buffered in a volatile memory, such as a dynamic random access memory (DRAM) buffer, but subsequent power loss may prevent the captured information buffered in the volatile memory from being written to the non-volatile memory. The captured information buffered in the volatile memory that was not written to the non-volatile memory before the power loss occurred may be permanently lost, thereby degrading the overall performance of the vehicle DVR system.
[0018] A power loss protection circuit, which may be a charging circuit with a capacitor, may provide additional power to the vehicle DVR system after the power supply is affected by an event. However, the power maintenance time associated with the power loss protection circuit may not be sufficient to save high definition (HD) video, ultra high definition (UHD) video, or footage files from a multi-channel camera sensor. Captured information already in the DRAM buffer may not be successfully refreshed to non-volatile memory before the power loss occurs even with the power loss protection circuit, and thus the captured information may be permanently lost. The captured information may be critical to solving problems associated with the event, and losing such captured information may be disadvantageous. In addition, the power loss protection circuit may incur additional costs.
[0019] In some embodiments described herein, a vehicle DVR system may include a host device and a memory device. The host device and the memory device may be associated with a vehicle. The host device may obtain video data, which may be captured via a camera sensor associated with the vehicle. The host device may collect information from one or more sensors associated with the vehicle (e.g., a motion sensor or a proximity sensor). The information may include target movement information associated with an object outside the vehicle, speed information associated with the vehicle, and / or location information associated with the vehicle. The host device may detect a potential event (e.g., a traffic accident) based on the sensor information. For example, the host device may detect a potential event based on target movement information indicating that an object is moving toward the vehicle at a relatively high speed. The host device may transmit a signal indicating a potential event to the memory device. The memory device may receive a signal from the host device. The memory device may suspend a background operation (or multiple background operations) associated with the memory device based on the signal. The background operation may be a defragmentation operation, a refresh scan operation, or a single-level cell (SLC) to a three-level cell (TLC) folding operation. The memory device may perform a write operation to write video data to the memory when the background operation is suspended. Based on the background operation being suspended during the write operation, the write speed associated with the write operation can be an increased write speed compared to a default write speed (e.g., which may occur when the background operation is not suspended). The default write speed may include a default range of write speeds that may occur when the background operation is not suspended. As a result, the video data is more likely to be successfully written to the memory before an event (e.g., a traffic accident) occurs that may terminate power to the vehicle DVR system and cause the video data to be lost.
[0020] In some embodiments, the memory device can successfully write the most recently captured video data (e.g., the last few seconds of recorded video data) to the memory before the event occurs. The host device can predict an upcoming traffic accident based on information collected by one or more sensors, and the host device can immediately notify the memory device of the predicted upcoming traffic accident. The memory device can use internal firmware manipulation (e.g., suspending defragmentation operations, suspending refresh scanning operations, and / or suspending SLC to TLC folding operations) to increase the data write speed, which can enable video data that can provide key information related to the traffic accident to be successfully written to the memory (or as much as possible) before the power interruption that causes the memory device to stop operating. The increased data write speed can be implemented based on the predicted upcoming traffic event. After the power interruption, any recently captured video data that has not been written will not be written to the memory and will be lost, so the increased data write speed allows as much video data as possible to be written to the memory before the power interruption.
[0021] In some embodiments, the ability to write recently captured video data to memory via increased data write speeds can ensure recorded data integrity and enhance customer experience. The memory device can increase vehicle DVR recording speeds to save as much data as possible in anticipation of traffic incidents. This approach can reduce memory design complexity (e.g., reducing the requirements for memory performance optimization, such as firmware algorithms or NAND performance tuning). In addition, this approach may not involve large capacitors for power loss protection circuit design, nor fast-tuned management NAND chips associated with relatively high costs, thereby providing a more advantageous solution.
[0022] Figure 1 1 is a diagram illustrating an example system 100 capable of performing write operations at an increased write speed based on a potential event. The system 100 may include one or more devices, apparatuses, and / or components for performing the operations described herein. For example, the system 100 may include a host device 110 and a memory device 120. The memory device 120 may include a controller 130 and a memory 140. The host device 110 may communicate with the memory device 120 (e.g., the controller 130 of the memory device 120) via a host interface 150. The controller 130 and the memory 140 may communicate via a memory interface 160.
[0023] System 100 may be any electronic device configured to store data in a memory. For example, system 100 may be a computer, a mobile phone, a wired or wireless communication device, a network device, a server, a device in a data center, a device in a cloud computing environment, a vehicle (such as a car or an airplane), and / or an Internet of Things (IoT) device. Host device 110 may include one or more processors configured to execute instructions and store data in memory 140. For example, host device 110 may include a central processing unit (CPU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and / or another type of processing component.
[0024] The memory device 120 may be any electronic device or apparatus configured to store data in a memory. In some implementations, the memory device 120 may be an electronic device configured to store data persistently in a non-volatile memory. For example, the memory device 120 may be a hard drive, a solid state drive (SSD), a flash memory device (e.g., a NAND flash memory device or a NOR flash memory device), a universal serial bus (USB) thumb drive, a memory card (e.g., a secure digital (SD) card), an auxiliary storage device, a non-volatile memory express (NVMe) device, and / or an embedded multimedia card (eMMC) device. In this case, the memory 140 may include a non-volatile memory configured to maintain the stored data after the memory device 120 is powered off. For example, the memory 140 may include a NAND memory or a NOR memory. In some implementations, memory 140 may include volatile memory, such as one or more latches and / or random access memory (RAM), such as DRAM and / or static RAM (SRAM), that requires power to maintain stored data and loses the stored data after power is removed from memory device 120. For example, volatile memory may cache data read from or to be written to nonvolatile memory, and / or may cache instructions to be executed by controller 130.
[0025] Controller 130 may be any device configured to communicate with a host device (e.g., via host interface 150) and memory 140 (e.g., via memory interface 160). Additionally or alternatively, controller 130 may be configured to control the operation of memory device 120 and / or memory 140. For example, controller 130 may include control logic, a memory controller, a system controller, an ASIC, an FPGA, a processor, a microcontroller, and / or one or more processing components. In some implementations, controller 130 may be a high-level controller that can communicate directly with host device 110 and can instruct one or more low-level controllers about memory operations to be performed in conjunction with memory 140. In some implementations, controller 130 may be a low-level controller that can receive instructions about memory operations from a high-level controller that directly interfaces with host device 110. As an example, the high-level controller may be an SSD controller, and the low-level controller may be a non-volatile memory controller (e.g., a NAND controller) or a volatile memory controller (e.g., a DRAM controller). In some embodiments, a set of operations described herein as being performed by controller 130 may be performed by a single controller (e.g., the entire set of operations may be performed by a single high-level controller or a single low-level controller). Alternatively, a set of operations described herein as being performed by controller 130 may be performed by more than one controller (e.g., a first subset of operations may be performed by a high-level controller, and a second subset of operations may be performed by a low-level controller).
[0026] The host interface 150 enables communication between the host device 110 and the memory device 120. The host interface 150 may include, for example, a small computer system interface (SCSI), a serial attached SCSI (SAS), a serial advanced technology attachment (SATA) interface, a peripheral component interconnect express (PCIe) interface, an NVMe interface, a USB interface, a universal flash storage (UFS) interface, and / or an embedded multimedia card (eMMC) interface.
[0027] The memory interface 160 enables communication between the memory device 120 and the memory 140. The memory interface 160 may include a non-volatile memory interface (e.g., for communicating with a non-volatile memory), such as a NAND interface or a NOR interface. Additionally or alternatively, the memory interface 160 may include a volatile memory interface (e.g., for communicating with a volatile memory), such as a double data rate (DDR) interface.
[0028] In some embodiments, Figure 1 One or more systems, devices, equipment, components and / or controllers may be configured to: receive a signal indicating a potential event from the host device 110; suspend background operations of the memory device 120 based on the signal; and perform a write operation to write data to the memory 140 while the background operation is suspended, wherein based on the background operation being suspended during the write operation, a write speed associated with the write operation is a write speed that is increased compared to a default write speed.
[0029] In some embodiments, Figure 1 One or more systems, devices, equipment, components and / or controllers may be configured to: detect a potential event based on sensor information; transmit a signal indicating a potential event; receive a signal indicating a potential event from a host device 110; suspend background operations of the memory device 120 based on the signal; and perform a write operation to write data to the memory 140 while the background operation is suspended, wherein based on the background operation being suspended during the write operation, a write speed associated with the write operation is a write speed that is increased compared to a default write speed.
[0030] As indicated above, Figure 1 are provided as examples. Other examples may differ from those regarding Figure 1 The content of the description.
[0031] Figure 2 is a diagram of example components included in memory device 120. Figure 1 As described above, the memory device 120 may include a controller 130 and a memory 140. Figure 2, the memory 140 may include one or more non-volatile memory arrays 205, such as one or more NAND memory arrays and / or one or more NOR memory arrays. Additionally or alternatively, the memory 140 may include one or more volatile memory arrays 210, such as one or more SRAM arrays and / or one or more DRAM arrays. The controller 130 may use a non-volatile memory interface 215 to transmit signals to and receive signals from the non-volatile memory array 205. The controller 130 may use a volatile memory interface 220 to transmit signals to and receive signals from the volatile memory array 210.
[0032] The controller 130 may control the operation of the memory 140, such as by executing one or more instructions. For example, the memory device 120 may store one or more instructions as firmware in the memory 140, and the controller 130 may execute the one or more instructions. Additionally or alternatively, the controller 130 may receive one or more instructions from the host device 110 via the host interface 150 and may execute the one or more instructions. In some implementations, a non-transitory computer-readable medium (such as a volatile memory and / or a non-volatile memory) may store a set of instructions (such as one or more instructions or codes) for execution by the controller 130. The controller 130 may execute a set of instructions to perform one or more operations or methods described herein. In some implementations, execution of a set of instructions by the controller 130 causes the controller 130 and / or the memory device 120 to perform one or more operations or methods described herein. In some implementations, hard-wired circuitry is used instead of one or more instructions to perform or in combination with one or more instructions to perform one or more operations or methods described herein. Additionally or alternatively, one or more components of the controller 130 and / or the one or more memory devices 120 may be configured to perform one or more operations or methods described herein.Instructions are sometimes referred to as "commands."
[0033] For example, the controller 130 may transmit signals to and / or receive signals from the memory 140 based on one or more instructions, such as transferring (e.g., writing or programming) data to all or a portion of the memory 140 (e.g., one or more memory cells, pages, sub-blocks, blocks, or planes of the memory 140), transferring (e.g., reading) data from all or a portion of the memory 140, and / or erasing all or a portion of the memory 140. Additionally or alternatively, the controller 130 may be configured to control access to the memory 140 and / or a translation layer between the host device 110 and the memory 140 (e.g., for mapping logical addresses of the memory array to physical addresses). In some implementations, the controller 130 may translate a host interface command (e.g., a command received from the host device 110) into a memory interface command (e.g., a command for performing an operation on the memory array).
[0034] like Figure 2 , the controller 130 may include a memory management component 225 and / or an enhanced write component 230. In some implementations, one or more of these components are implemented as one or more instructions (e.g., firmware) executed by the controller 130. Alternatively, one or more of these components may be implemented as an application specific integrated circuit distinct from the controller 130.
[0035] The memory management component 225 may be configured to manage the performance of the memory device 120. For example, the memory management component 225 may perform wear leveling, bad block management, block retirement, read disturb management, and / or other memory management operations. In some implementations, the memory device 120 may store (e.g., in the memory 140) one or more memory management tables. The memory management tables may store information that may be used or updated by the memory management component 225, such as information about the age of a memory block, a memory block erase count, and / or error information associated with a memory partition (e.g., a memory cell, a memory row, a memory block, or the like).
[0036] The enhanced write component 230 may be configured to receive a signal indicating a potential event from the host device 110. The enhanced write component 230 may be configured to suspend background operations of the memory device 120 based on the signal. The enhanced write component 230 may be configured to perform a write operation to write data to the memory 140 while the background operation is suspended, wherein based on the background operation being suspended during the write operation, a write speed associated with the write operation is a write speed that is increased compared to a default write speed.
[0037] Figure 2 One or more devices or components shown in the figure may be configured to perform the operations described herein, for example in conjunction with Figures 3 to 4For example, the controller 130, the memory management component 225, and / or the enhanced write component 230 may be configured to perform one or more operations and / or methods for the memory device 120.
[0038] Figure 2 The number and arrangement of components shown in FIG. are provided as examples. In practice, there may be Figure 2 Additional components other than the components shown in, fewer components than the components described, components different from the components described, or components arranged in a different manner than the components described. In addition, Figure 2 Two or more components shown in may be implemented in a single component, or Figure 2 A single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Figure 2 A set of components (e.g., one or more components) shown in Figure 2 One or more actions performed by another set of components shown in .
[0039] Figure 3 is a diagram of an example 300 of performing a write operation at an increased write speed based on a potential event. Figure 3 The operations described may be performed by host device 110 and / or memory device 120 and / or one or more components of memory device 120, such as controller 130 and / or one or more components of controller 130. Host device 110 and memory device 120 may be associated with a vehicle. For example, host device 110 and memory device 120 may be onboard a vehicle. Memory device 120 may be a non-volatile memory (NVM), such as a memory card, eMMC, UFS, or SSD.
[0040] In some aspects, the collision detection module, host device 110, and memory device 120 can be associated with a vehicle. For example, the collision detection module, host device 110, and memory device 120 can be onboard the vehicle.
[0041] In some embodiments, the vehicle may include a camera sensor (or multiple camera sensors). The camera sensor may capture video data of a scene associated with the vehicle. For example, the camera sensor may capture a scene of a front view associated with the vehicle. In some cases, multiple camera sensors may capture video data of multiple scenes associated with the vehicle (e.g., scenes associated with multiple views). The camera sensor may provide the video data to the host device 110 for storage. When the vehicle is involved in an event (e.g., a traffic accident), the video data may be crucial to evidence. For example, the video data may provide information about other parties or vehicles involved in the event. The video data may provide evidence about which party is the party at fault for causing the event to occur.
[0042] As shown by reference numeral 302, the collision detection module may collect sensor information. The collision detection module may include one or more sensors, such as accelerometers, gyroscopes, motion sensors, proximity sensors, and / or radar sensors. One or more sensors may be mounted on the exterior of a vehicle. The sensor information may include accelerometer data, which may be based on an accelerometer. The accelerometer data may indicate acceleration (or speed information) associated with the vehicle. The sensor information may include position data, which may be based on a gyroscope. The position information may indicate a position associated with the vehicle. The sensor information may include movement information, which may be based on a motion sensor. The movement information may indicate whether one or more objects around the vehicle are moving. The sensor information may include proximity information, which may be based on a proximity sensor. The proximity information may indicate whether one or more objects are located close to the vehicle. For example, the proximity information may indicate whether a particular object is within a particular distance from the vehicle. The proximity sensor may detect the presence of nearby objects. The sensor information may include radar information, which may be based on a radar sensor. The radar information may indicate the distance, angle, and / or speed of each of one or more nearby objects relative to the vehicle. In other words, the sensor information may include object movement information, which may indicate the movement of nearby objects. In some implementations, the sensor information may indicate objects that are relatively close to the vehicle and the speed and direction of each of the objects relative to the vehicle. In addition, the collision detection module may provide the sensor information to the host device 110.
[0043] As shown by reference numeral 304, host device 110 may detect a potential event based on sensor information. A potential event may be a traffic accident involving a vehicle. A potential event may be an event that potentially causes memory device 120 to lose power, which may prevent subsequent read-write operations for memory device 120. A traffic accident may involve an object detected by one or more sensors that is relatively close to the vehicle. Host device 110 may employ an artificial intelligence or machine learning (AI / ML) model associated with potential event prediction. Host device 110 may provide sensor information as input to the AI / ML model. The AI / ML model may output a value that may represent an event occurrence level (or event urgency level). The value may indicate the likelihood of a vehicle being involved in an event (e.g., a traffic accident) based on sensor information. For example, when there are no other vehicles positioned relatively close to the vehicle, the value may be relatively low, which may indicate that the vehicle is unlikely to be involved in the event. As another example, when another vehicle is accelerating directly toward the vehicle at a relatively high speed, based on sensor information, the value may be relatively high, which may indicate that the vehicle is likely to be involved in the event. In some implementations, host device 110 may calculate the value periodically (eg, every second) based on recent sensor information.
[0044] As shown by reference numeral 306, memory device 120 may receive a signal from host device 110, wherein the signal may indicate a potential event. Memory device 120 may receive the signal via a memory pin of memory device 120. The memory pin may be a pin reserved for future use (RFU). Host device 110 may signal memory device 120 via the memory pin to indicate that a potential event may occur. Alternatively, the signal may be associated with a predefined vendor user command conforming to a standard command set. Host device 110 may send the predefined vendor user command to memory device 120, wherein the predefined vendor user command may indicate that a potential event may occur.
[0045] As shown by reference numeral 308, the memory device 120 may suspend one or more background operations of the memory device 120 based on the signal. The background operations of the memory device 120 may include defragmentation. Defragmentation may involve reorganization (or fragmentation reduction) of data stored on the memory device 120, which may improve the performance of the memory device 120. The background operations of the memory device 120 may include refresh scanning. Refresh scanning may involve periodically reading information from the memory device 120 and rewriting that information to the memory device 120 without modification (e.g., for the purpose of preserving the information). The background operations of the memory device 120 may include SLC to TLC folding. SLC to TLC folding may involve combining separate SLC blocks into a single TLC block. In other words, when the memory device 120 receives a signal indicating a potential event, the memory device 120 may suspend one or more background operations of the memory device 120. In some implementations, the memory device 120 may suspend power state switching of the memory device 120 based on the signal. Thus, the memory device 120 may be prevented from switching between different power states (eg, from a standby state to a non-standby state).
[0046] As shown by reference numeral 310, the memory device 120 may perform a write operation of video data captured by the camera sensor to a memory of the memory device 120. The memory device 120 may perform the write operation when one or more background operations and / or power state switching are suspended. Based on the one or more background operations and / or power state switching being suspended during the write operation, the write speed associated with the write operation may be a write speed that is increased compared to the default write speed. In other words, when the one or more background operations and / or power state switching are not suspended, the memory device 120 may perform the write operation according to the default write speed. However, when the one or more background operations and / or power state switching are suspended, the memory device 120 may have additional resources that can be used to obtain the increased write speed, and thus may be able to perform the write operation of the video data using the increased write speed.
[0047] In some implementations, the memory device 120 may apply write optimization based on the signal to obtain an increased write speed for the write operation. The write optimization may be associated with writing video data to a trimmed memory cell of the memory device 120. The trimmed memory cell may have been processed so that a block of data no longer used in that memory cell has been erased, and thus the write speed may be increased. In other words, the memory device 120 may be able to achieve an increased write speed when writing video data to the trimmed memory cell. The write optimization may be associated with writing video data using a pseudo-SLC mode. The pseudo-SLC mode may be associated with an increased write speed compared to the TLC mode. The memory device 120 may be able to achieve an increased write speed when writing video data using the pseudo-SLC mode.
[0048] In some embodiments, the memory device 120 can achieve an increased write speed by suspending one or more background operations and / or power state switching, which can be an indication based on a potential event. The potential event can be associated with an event that affects the power supply of the memory device 120, and because the occurrence of the event can prevent the recently captured video data from being successfully written to the memory, the memory device 120 can suspend one or more background operations and / or power state switching to obtain an increased write speed. Compared with writing video data using the default write speed, the increased write speed can allow a larger amount of video data to be written to the memory before power is lost. Therefore, in the event that the memory device 120 loses power, less video data may be permanently lost because the video data that is in the process of being written when the power is disconnected may be permanently lost. The ability to save more video data can improve the overall performance of the memory device 120.
[0049] As shown by reference numeral 312, memory device 120 may resume one or more background operations and / or power state switching of memory device 120. Memory device 120 may determine that a condition has been met. For example, memory device 120 may determine that memory device 120 has remained powered on for a period of time after receiving a signal. In this case, memory device 120 may not actually have lost power due to the event. Alternatively, the potential event may be a false alarm, and the event may not actually have occurred. In these cases, memory device 120 may resume one or more background operations and / or power state switching of memory device 120. Memory device 120 may revert to a default write speed when writing video data to memory.
[0050] As indicated above, Figure 3 are provided as examples. Other examples may differ from those regarding Figure 3 The content of the description.
[0051] Figure 4is a diagram of an example 400 of a vehicle DVR system capable of performing write operations at an increased write speed based on a potential event. The vehicle DVR system may be onboard a vehicle.
[0052] In some implementations, the vehicle DVR system may include a collision prediction module, a camera sensor (or multiple camera sensors), a recorder system-on-chip (SOC) (or a host device), a volatile memory device (e.g., DRAM), and an NVM (or a memory device). The collision prediction module may be associated with traffic accident prediction and notification triggering. The volatile memory device may be associated with a video image buffer. The NVM may be associated with a video data storage device.
[0053] In some implementations, the camera sensor may capture video data. The video data may be associated with one or more views around the vehicle. For example, the video data may be associated with a front view of the vehicle, a rear video of the vehicle, and / or a side view of the vehicle. The video data may be provided as a video input to the recorder SOC. The camera sensor may provide the video data via a mobile industry processor interface (MIPI). The video data may be associated with a video codec (e.g., H.264 or H.265). The video data may initially be stored in a volatile memory buffer before being moved to the NVM.
[0054] In the first step, the collision prediction module can detect potential traffic accidents based on monitored information (such as speed, position and / or object movement). The collision prediction module can be associated with one or more sensors (such as proximity sensors, motion sensors, camera sensors, or any other suitable sensors) that can predict traffic accidents based on the movement of objects. One or more sensors can be distributed across different areas of the vehicle. The collision prediction module can deploy AI / ML models to predict potential traffic accidents depending on the monitored information. As long as the event urgency level meets the threshold, the collision prediction module can notify the recorder SOC of the potential traffic accident. The event urgency level can be based on the monitored information. The collision prediction module can transmit notifications to the recorder SOC via a controller area network (CAN) bus.
[0055] In a second step, the recorder SOC may receive a notification from the collision prediction module. The recorder SOC may signal the NVM with a high priority via a memory pin (e.g., an RFU pin), which may indicate a potential traffic accident to the NVM. The memory pin may be associated with a pre-aligned notification logic between the host SOC and the NVM. For example, a square wave with a specific number of pulses may be a viable option. Alternatively, the recorder SOC may signal the NVM using a predefined vendor user command with specific variables, wherein the predefined vendor user command may conform to the Joint Electronic Device Engineering Council (JEDEC) standard command set. In some embodiments, the recorder may signal a memory pin or a predefined vendor user command based on a notification received from the collision prediction module.
[0056] In a third step, the NVM may receive a signal from the recorder SOC. The signal may indicate a potential traffic accident. The NVM (via the NVM firmware and controller) may stop various background operations of the NVM, such as defragmentation, refresh scans, and / or SLC to TLC folding, based on the signal received from the recorder SOC. Defragmentation may involve reorganization (or fragmentation reduction) of data stored on the NVM. Refresh scans may involve periodically reading information from the NVM and rewriting that information to the NVM without modification (e.g., for the purpose of saving information). SLC to TLC folding may involve combining separate SLC blocks into a single TLC block. Such background operations may consume the read-write resources of the NVM. The NVM may stop power state switching based on a signal received from the recorder SOC. The power state switching may otherwise cause the NVM to recover from a standby mode, which may take additional time. By stopping background operations and / or stopping power state switching, the NVM (via firmware) may prioritize write operations to the NAND components. Furthermore, to improve write performance, write operations may be scheduled to use fast placement techniques, such as trimmed NAND cells (which may compromise NAND data retention) or pseudo-SLC mode. Trimmed NAND cells may have been processed so that data blocks that are no longer used have been erased, and thus write performance may be improved. By employing NAND cells, write operations may not involve erasing existing information, which may improve write performance. Furthermore, pseudo-SLC mode may be associated with increased write speeds compared to TLC mode.
[0057] In a fourth step, when such write performance optimization is applied (e.g., stopping background operations and stopping power state switching), the recorder SOC may move video data from the volatile memory device to the NVM at an increased write speed compared to when such performance optimization is not applied. Typically, the NVM may operate in a "dirty" state and may consume resources used for background operations, but when such resources are released based on receiving a signal associated with a potential traffic accident, the NVM may be able to increase the write speed when writing video data. Therefore, the NVM may be more likely to save critical video data associated with a traffic accident associated with a vehicle. The traffic accident may cause the NVM to lose power, and the loss of power may cause the video data in the volatile memory buffer to not be transferred to the NVM and be permanently lost. By increasing the write speed, the video data is more likely to be saved by the NVM and therefore can be accessed later even in the event of a power loss.
[0058] In the fifth step, the NVM may autonomously determine to resume normal operation. For example, the NVM may resume background operation, and the NVM may resume power state switching. The NVM may determine to resume normal operation when the NVM is powered on for a certain period of time after receiving a signal from the recorder SOC. The NVM being powered on for a certain period of time may indicate that a traffic accident did not occur, or that the traffic accident was not serious enough to cause a loss of power. In other words, the traffic accident may not be serious enough to damage the power system, so the NVM may resume normal operation (with a lower write speed). At the same time, the NVM may copy the video data programmed with the fast placement technology to other areas for better data retention.
[0059] As indicated above, Figure 4 are provided as examples. Other examples may differ from those regarding Figure 4 The content of the description.
[0060] Figure 5is a flow chart of an example method 500 associated with performing a write operation at an increased write speed based on a potential event. In some implementations, a memory device (e.g., memory device 120) may execute or may be configured to execute method 500. In some implementations, another device or group of devices (e.g., host device 110) that is separate from or includes the memory device may execute or may be configured to execute method 500. Additionally or alternatively, one or more components of the memory device (e.g., controller 130, memory management component 225, and / or enhanced write component 230) may execute or may be configured to execute method 500. Thus, means for executing method 500 may include a memory device and / or one or more components of a memory device. Additionally or alternatively, a non-transitory computer-readable medium may store one or more instructions that, when executed by a memory device (e.g., controller 130 of memory device 120), causes the memory device to execute method 500.
[0061] like Figure 5 As shown in FIG. 5 , method 500 may include receiving a signal indicating a potential event from a host device (block 510). Figure 5 As further shown in FIG. 5 , method 500 may include suspending background operations of the memory device based on the signal (block 520). Figure 5 As further shown in FIG. 5 , method 500 may include performing a write operation to write data to a memory while the background operation is suspended, wherein a write speed associated with the write operation is a write speed that is increased compared to a default write speed based on the background operation being suspended during the write operation (block 530).
[0062] Method 500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other methods or operational descriptions described elsewhere herein.
[0063] In a first aspect, the data written to the memory is video data obtained from one or more camera sensors.
[0064] In a second aspect, either alone or in combination with the first aspect, the signal is received via a memory pin of the memory device.
[0065] In a third aspect, either alone or in combination with the first aspect, the signal is associated with a predefined vendor user command conforming to a standard command set.
[0066] In a fourth aspect, either alone or in combination with the third aspect, the potential event is a traffic accident involving a vehicle associated with the memory device, wherein the potential event is based on information associated with one or more of the memory device or the vehicle, and wherein the information includes one or more of speed information, location information, or object movement information.
[0067] In a fifth aspect, alone or in combination with the fourth aspect, the background operation is one or more of: a defragmentation operation, a refresh scan operation, or an SLC to TLC folding operation.
[0068] In a sixth aspect, alone or in combination with the fifth aspect, the method 500 includes suspending power state switching of the memory device based on the signal.
[0069] In a seventh aspect, either alone or in combination with the sixth aspect, method 500 includes determining that a condition has been satisfied, wherein the condition is satisfied based on the memory device being powered on for a period of time after receiving the signal; and resuming the background operation of the memory device.
[0070] In an eighth aspect, alone or in combination with the first and seventh aspects, method 500 includes applying write optimization based on the signal to obtain the improved write speed for the write operation, wherein the write optimization is associated with writing the data to a trimmed memory cell of the memory device or writing the data using a pseudo-SLC mode.
[0071] In a ninth aspect, alone or in combination with the first and eighth aspects, the memory device is associated with a vehicle.
[0072] although Figure 5 An example block diagram of method 500 is shown, but in some embodiments, method 500 may include Figure 5 In some embodiments, the method 500 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than the blocks described in the method 500. Additionally or alternatively, two or more of the blocks of the method 500 may be executed in parallel. The method 500 is an example of a method that may be performed by one or more devices described herein. The one or more devices may perform or may be configured to perform one or more other methods based on the operations described herein.
[0073] In some embodiments, a memory device includes: a memory; and a controller configured to: receive a signal indicating a potential event from a host device; suspend background operations of the memory device based on the signal; and perform a write operation to write data to the memory while the background operation is suspended, wherein based on the background operation being suspended during the write operation, a write speed associated with the write operation is a write speed that is increased compared to a default write speed.
[0074] In some implementations, a method includes: receiving, by a memory device and from a host device, a signal indicating a potential event; suspending, by the memory device and based on the signal, background operations of the memory device; and performing, by the memory device, a write operation to write data to the memory while the background operation is suspended, wherein based on the background operation being suspended during the write operation, a write speed associated with the write operation is a write speed that is increased compared to a default write speed.
[0075] In some embodiments, a system includes: a host device, which is configured to: detect a potential event based on sensor information; and transmit a signal indicating the potential event; and a memory device, which is configured to: receive the signal indicating the potential event from the host device; stop background operations of the memory device based on the signal; and perform a write operation to write data to the memory when the background operation is stopped, wherein based on the background operation being stopped during the write operation, a write speed associated with the write operation is a write speed that is increased compared to a default write speed.
[0076] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed.Modifications and variations are possible in light of the above disclosure or may be acquired from practicing the embodiments described herein.
[0077] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, or the like, depending on the context.
[0078] Although the specific combination of features is quoted in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the embodiments described herein. Many of these features can be combined in a manner that is not clearly quoted in the claims and / or not clearly disclosed in the specification. For example, the disclosure includes each dependent claim in the claim set in conjunction with each individual single claim in that claim set and each combination of multiple claims in that claim set. As used herein, the phrase "at least one of" related to the list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and also covers any combination with multiple identical elements (such as a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c or any other ordering of a, b and c).
[0079] Elements, actions or instructions used herein should not be interpreted as key or necessary unless clearly described as such. Moreover, as used herein, the article "a / an" is intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items quoted in conjunction with the article "said" and can be used interchangeably with "one or more". In the case of only wishing one project, the phrase "only one", "single" or similar language is used. Moreover, as used herein, the term "has / have / having" or the like is intended to be an open term (for example, "an element with" A may also have B) that does not limit its modified elements. In addition, unless otherwise clearly stated, the phrase "based on" is intended to represent "based at least in part". As used herein, the term "multiple (multiple)" can be replaced with "plurality (aplurality of)", and vice versa. Also, as used herein, the term "or" when used in a series is intended to be inclusive and used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in combination with "either" or "only one of").
Claims
1. A memory device, comprising: Memory; and A controller configured to: receiving a signal indicative of a potential event from a host device; suspending background operations of the memory device based on the signal; and A write operation is performed to write data to the memory while the background operation is suspended, wherein a write speed associated with the write operation is a write speed that is increased compared to a default write speed based on the background operation being suspended during the write operation.
2. The memory device of claim 1, wherein the data written to the memory is video data obtained from one or more camera sensors.
3. The memory device of claim 1, wherein the signal is received via a memory pin of the memory device.
4. The memory device of claim 1, wherein the signal is associated with a predefined vendor user command conforming to a standard command set.
5. A memory device according to claim 1, wherein the potential event is a traffic accident involving a vehicle associated with the memory device, wherein the potential event is based on information associated with one or more of the memory device or the vehicle, and wherein the information includes one or more of speed information, location information, or object movement information.
6. The memory device of claim 1, wherein the background operation is one or more of: a defragmentation operation, a refresh scan operation, or a single-level cell (SLC) to triple-level cell (TLC) folding operation.
7. The memory device of claim 1, wherein the controller is configured to suspend power state switching of the memory device based on the signal.
8. The memory device of claim 1, wherein the controller is configured to: confirming that the conditions have been met; and The background operation of the memory device is resumed.
9. The memory device of claim 8, wherein the condition is satisfied based on the memory device being powered on for a period of time after receiving the signal.
10. The memory device of claim 1, wherein the controller is configured to: Write optimization is applied based on the signal to obtain the increased write speed for the write operation, wherein the write optimization is associated with writing the data to trimmed memory cells of the memory device or writing the data using a pseudo single level cell (SLC) mode.
11. The memory device of claim 1, wherein the memory device is associated with a vehicle.
12. A method comprising: receiving, by the memory device and from the host device, a signal indicative of a potential event; suspending, by the memory device and based on the signal, background operations of the memory device; and A write operation is performed by the memory device to write data to the memory while the background operation is suspended, wherein a write speed associated with the write operation is a write speed that is increased compared to a default write speed based on the background operation being suspended during the write operation.
13. The method according to claim 12, further comprising: Power state switching of the memory device is suspended based on the signal.
14. The method according to claim 12, further comprising: determining that a condition has been satisfied, wherein the condition is satisfied based on the memory device being powered on for a period of time after receiving the signal; and The background operation of the memory device is resumed.
15. The method according to claim 12, further comprising: Write optimization is applied based on the signal to obtain the increased write speed for the write operation, wherein the write optimization is associated with writing the data to trimmed memory cells of the memory device or writing the data using a pseudo single level cell (SLC) mode.
16. A system comprising: A host device configured to: Detect potential events based on sensor information; and transmitting a signal indicative of the potential event; and A memory device configured to: receiving the signal indicative of the potential event from the host device; stopping background operation of the memory device based on the signal; and A write operation is performed to write data to the memory while the background operation is stopped, wherein a write speed associated with the write operation is a write speed that is increased compared to a default write speed based on the background operation being stopped during the write operation.
17. The system of claim 16, wherein: The signal is received via a memory pin of the memory device; or The signals are associated with predefined vendor user commands that conform to a standard command set.
18. The system of claim 16, wherein the background operation is one or more of: a defragmentation operation, a refresh scan operation, or a single-level cell (SLC) to triple-level cell (TLC) folding operation.
19. The system of claim 16, wherein the memory device is configured to: determining that a condition has been satisfied, wherein the condition is satisfied based on the memory device being powered on for a period of time after receiving the signal; and The background operation of the memory device is resumed.
20. The system of claim 16, wherein the memory device is configured to: Write optimization is applied based on the signal to obtain the increased write speed for the write operation, wherein the write optimization is associated with writing the data to trimmed memory cells of the memory device or writing the data using a pseudo single level cell (SLC) mode.
Citation Information
Patent Citations
Suspension of memory operations for reduced read latency in memory arrays
CN102598141A
Member driving device possessing green energy data persisting mode
CN103995578A
Memory managing device and memory managing method
JP2012027806A
Automatic resumption of suspended write operation upon completion of higher priority write operation in a memory device
US10042587B1
Battery-less cache memory module with integrated backup
WO2010006301A1
