The condition that e.Digital is pointing at for infringement is the cache and the initial wrapping of data prior to it being programmed(written) into the flash.

Another reason I have stayed here so long...it's easy for e.Digital to find products that consider the above and follow up on them in better detail to consider a product for infringement.

The cache(and they utilize various methods) has always been at the root for many of my posts in past years.... it's easy to spot and consider that data is being conditioned with a very skinny cache(SRAM) and not a typical OS / DRAM resource of significant size.

If the flash memory has a fast enough programming speed (write) to keep up with the SRAM data I/O the process in effect emulates a DRAM process having a significant RAM resource.

The SRAM (cache) is sized to the write block of the flash and nothing else is needed beyond that for I/O to the flash for audio / video type files…or any telemetry type data. With that, an application, other than video / audio / telemertry type data may require a RAM resource in conjunction with the cache I/O.

That said, to make all the parts fluid require much more in the way of background data management within the flash, however the upfront cache detail gives the implication of what a defendant is doing without having to go any deeper into a product than that.

doni